EP4677769A1 - Beam failure recovery for full duplex communication - Google Patents

Abstract

Various aspects of the present disclosure relate to beam failure recovery for full duplex (FD) communication. A network entity transmits a configuration message to a user equipment (UE) that supports FD communication. The configuration message includes an indication of a configuration for radio link monitoring that includes one or more RS resources for measuring various quality metrics, such as a downlink radio link quality metric, a self-interference (SI) quality metric, or a cross-link interference (CLI) quality metric. The UE determines, based on the configuration, when a beam failure occurs and transmits a beam failure indication to the network entity. The network entity determines a beam failure handling strategy and transmits an indication to the UE or at least one of the one or more nearby UEs of one or more actions to take to recover from the beam failure.

Description

BEAM FAILURE RECOVERY FOR FULL DUPLEX COMMUNICATION

RELATED APPLICATION

[0001] This application claims priority to U.S. Patent Application Serial No. 63/489,293 filed March 9, 2023 entitled “BEAM FAILURE RECOVERY FOR FULL DUPLEX COMMUNICATION,” the disclosure of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to beam failure recovery for full duplex (FD) communication.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a nextgeneration NodeB (gNB), or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0004] Communication between devices in the wireless communications system maybe be preformed in various manners, such as using half duplex (HD) communication or FD communication. Given the various network communication devices and user communication devices in a wireless communication system, situations can arise where these devices interfere with one another when communicating using HD or FD. SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support beam failure recovery for FD communication. A UE that supports FD communication receives, from a network entity (e.g., a base station), an indication of a configuration for radio link monitoring that includes one or more reference signal (RS) resources for measuring various quality metrics, such as a downlink radio link quality metric, a self-interference (SI) quality metric, or a cross-link interference (CLI) quality metric. In response to a beam failure criterion being met, a beam failure recovery procedure is triggered and the UE transmits, to the network entity, an indication that a beam failure is due to at least one of, for example, degradation in the downlink radio link, SI, or CLI from one or more nearby UEs. The network entity decides a beam failure handling strategy and transmits an indication to the UE or at least one of the one or more nearby UEs of one or more actions to take to recover from the beam failure. By configuring the UE to monitor for these various metrics, such as a SI quality metric or a CLI quality metric, the UE is able to account for different types of interference that may arise when performing FD communications, and detect a beam failure instance (BFI) and trigger a beam failure recovery (BFRQ) procedure when such interference occurs.

[0006] Some implementations of the method and apparatuses described herein may further include to: receive, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; transmit, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more UEs; and receive, from the network entity, a third signaling indicating a configuration for handling a beam failure.

[0007] In some implementations of the method and apparatuses described herein, the method and apparatuses are further to trigger, in response to a beam failure criterion being met, a beam failure recovery procedure in accordance with the configuration for handling the beam failure; and transmit the second signaling as part of the beam failure recovery procedure. Additionally or alternatively, the first signaling is a part of a radio resource control RadioLinkMonitoringConfig- informationelement. Additionally or alternatively, the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-informationelement. Additionally or alternatively, the one or more RS resources for measuring downlink radio link quality level comprise at least one of synchronization signal block (SSB) or channel state information-RS resources; and the one or more RS resources for measuring a self-interference level or a cross-link interference level comprise at least one of sounding reference or demodulation-RS resources, or a dedicated RS for selfinterference and cross-link interference probing of a full-duplex transceiver. Additionally or alternatively, the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets. Additionally or alternatively, the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention-free random-access or a contention-based randomaccess procedure. Additionally or alternatively, the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message. Additionally or alternatively, the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels. Additionally or alternatively, the third signaling includes a first uplink transmit power value dedicated for overlapped uplinkdownlink (UL-DL) physical resource blocks (PRBs) and a second uplink transmit power value dedicated for non-overlapped UL-DL PRBs. Additionally or alternatively, the third signaling includes an indication to increase or to decrease an uplink transmit power over overlapped and nonoverlapped UL-DL PRBs by indicating a row index corresponding to a preconfigured uplink power control lookup table. Additionally or alternatively, the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi-persistently scheduled overlapped UL-DL PRBs, or mute uplink transmission over semi-persistently scheduled non-overlapped UL-DL PRBs. Additionally or alternatively, the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a new uplink transmit power for overlapped UL- DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a modulation coding scheme (MCS) order, or a release time. Additionally or alternatively, the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a power difference and a MCS order difference the apparatus may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for nonoverlapped UL-DL PRBs, or a current MCS order. Additionally or alternatively, a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table. Additionally or alternatively, the beam failure criterion for a full-duplex beam failure includes at least one of downlink radio link quality level, self-interference quality level, or cross-link interference quality level. Additionally or alternatively, the beam failure criterion include at least one of a signal-to-interference-plus-noise ratio, a signal-to-interference ratio, or a block-error-rate (BLER). Additionally or alternatively, the apparatus comprises a UE.

[0008] Some implementations of the method and apparatuses described herein may further include to: transmit, to a first UE, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; receive, from the first UE, a second signaling that indicates that a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more second UEs; and transmit, to the first UE, a third signaling indicating a configuration for handling a beam failure.

[0009] In some implementations of the method and apparatuses described herein, the method and apparatus are further to transmit, to one or more network entities, a fourth signaling indicating a request for uplink beam failure handling. Additionally or alternatively, the method and apparatuses described herein, the method and apparatus are further to receive, from one of the one or more network entities, a fifth signaling indicating whether the request is accepted or not accepted. Additionally or alternatively, the fourth signaling indicates to at least one of the one or more network entities to decrease a downlink transmit power over an indicated time-frequency resources by an indicated level. Additionally or alternatively, the fourth signaling indicates to at least one of the one or more network entities to mute a downlink transmission over an indicated time-frequency resources. Additionally or alternatively, the fourth signaling indicates to at least one of the one or more network entities to switch an active downlink beam index to an indicated beam index from a candidate beam set coordinated between the apparatus and the at least one of the one or more network entities. Additionally or alternatively, the fifth signaling indicates at least one of an acknowledgment response message or a negative acknowledgment response message. Additionally or alternatively, a negative acknowledgment response to the request is indicated by a lack of a fifth signaling from at least one of the one or more network entities indicating that the request is not accepted. Additionally or alternatively, the method and apparatus are further to receive the second signaling as part of a beam failure recovery procedure. Additionally or alternatively, the first signaling is a part of a radio resource control RadioLinkMonitoringConfig-information element. Additionally or alternatively, the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-information element. Additionally or alternatively, the one or more RS resources for measuring downlink radio link quality level comprise at least one of SSB or channel state information-RS resources; and the one or more RS resources for measuring a selfinterference level or a cross-link interference level comprise at least one of sounding reference or demodulation-RS resources, or a dedicated RS for self-interference and cross-link interference probing of a full-duplex transceiver. Additionally or alternatively, the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets. Additionally or alternatively, the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention-free random-access or a contention-based random-access procedure. Additionally or alternatively, the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message. Additionally or alternatively, the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels. Additionally or alternatively, the third signaling includes a first uplink transmit power value dedicated for overlapped uplink- downlink physical resource blocks and a second uplink transmit power value dedicated for non-overlapped uplink-downlink physical resource blocks. Additionally or alternatively, the third signaling includes an indication to increase or to decrease uplink transmit power over overlapped and non-overlapped UL-DL PRBs by indicating a row index corresponding to a preconfigured uplink power control lookup table. Additionally or alternatively, the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi- persistently scheduled overlapped uplink-downlink physical resource blocks, or mute transmission over semi-persistently scheduled non-overlapped uplink-downlink physical resource blocks. Additionally or alternatively, the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates a new uplink transmit power for overlapped UL-DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a modulation coding scheme order, and a release time. Additionally or alternatively, the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates a power difference and a MCS order difference the apparatus may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for non-overlapped UL-DL PRBs, and a current MCS order. Additionally or alternatively, a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table. Additionally or alternatively, a beam failure criterion for a full-duplex beam failure includes at least one of a downlink radio link quality level, a self-interference level, or a cross-link interference level. Additionally or alternatively, the beam failure criterion for a full-duplex beam failure includes at least one of a signal-to-interference- plus-noise ratio, a signal-to-interference ratio, or a block-error-rate. Additionally or alternatively, the apparatus comprises a network entity.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 illustrates an example of a wireless communications system that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0011] FIG. 2 illustrates examples of FD communication when using beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0012] FIG. 3 illustrates examples of different FD scenarios when using beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0013] FIG. 4 illustrates examples of additional interference scenarios in FD communications.

[0014] FIG. 5 illustrates an example of DL beam failure monitoring and detection at a UE for

HD communications.

[0015] FIG. 6 illustrates an example of signaling that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. [0016] FIG. 7 illustrates an example of a DL beam failure detection stage at a FD-capable UE that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0017] FIG. 8 illustrates an example of quality measurements at a UE using one or more candidate beams that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0018] FIG. 9 illustrates an example of quality measurements at a network entity using one or more candidate beams that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0019] FIGs. 10A and 10B illustrate an example of a RadioLinkMonitoringConfig information element (IE) that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0020] FIGs. 11 A and 1 IB illustrate an example of a BeamFailureRecoveryConfig IE that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0021] FIGs. 12 and 13 illustrate examples of block diagrams of devices that support beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0022] FIGs. 14 through 19 illustrate flowcharts of methods that support beam failure recovery for FD communication in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0023] Beam failure detection and recovery procedure is an important step for maintaining a good communication link between a transmitter and a receiver, which is a combination of Physical (PHY) layer and Medium Access Control (MAC) layer features that are used to monitor the radio link quality, detect a BFI, and trigger a BFRQ procedure when a specified criteria is met. In HD communications, a BFI may occur due to quality degradation in the downlink (DL) radio link or due to quality degradation in the uplink (UL) radio link. Differently, in FD communications, a BFI may also occur due to SI or CLI at the transmitter or at the receiver. [0024] The techniques discussed herein enable a FD-capable UE to account for SI or CLI sources when monitoring the radio link quality and triggering a BFRQ procedure. Depending on the scenario and the main reason causing the beam failure with its level, the serving network entity (e.g., a base station) and the FD-capable UE may use different solutions and signaling to successfully overcome the beam failure, e.g., by switching one or more active beams to one or more newly identified beams from a beam candidate set, by reducing or increasing the transmit power of a direct downlink radio communication link, by or muting or canceling one or more of the interference sources.

[0025] Classical beam failure detection and recovery, such as used in HD communications, does not account for SI or CLI causing a beam failure in FD communications. The techniques discussed herein describe actions that a node (e.g., a network entity (e.g., a base station) or a UE) may take to perform a BFRQ procedure depending on the scenario and the reason causing the beam failure (e.g., SI or CLI). By accounting for SI and CLI in FD communications, higher quality communication links between transmitters and receivers can be obtained for FD communications.

[0026] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts.

[0027] FIG. 1 illustrates an example of a wireless communications system 100 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0028] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0029] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0030] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet- of-Everything (loE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

[0031] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

[0032] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0033] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an SI, N2, N6, or another network interface). The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs). [0034] In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, 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, a network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0035] An RU 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 transmission reception point (TRP). One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0036] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3), a layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (LI) (e.g., physical (PHY) layer) or an 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. [0037] Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs). In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU).

[0038] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., Fl, Fl-c, Fl-u), and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface). In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

[0039] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P- GW), a user plane function (UPF)), or a location management function (LMF), which is a control plane entity that manages location services. In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

[0040] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an SI, N2, N6, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0041] In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) to perform various operations (e.g., wireless communications). In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0042] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. The first numerology (e.g., /r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., /r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0043] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0044] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0045] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short- range, high data rate capabilities.

[0046] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0047] The network entity 102 transmits a configuration message 120 to a UE 104 that supports FD communications. The configuration message includes an indication of a configuration for radio link monitoring that includes one or more RS resources for measuring various quality metrics, such as a downlink radio link quality metric, a SI quality metric, or a CLI quality metric. The beam failure detection 122 monitors these various quality metrics and detects when a beam failure criterion is satisfied. In response to a beam failure criterion being satisfied, the beam failure recovery 124 of the UE 104 transmits, to the network entity 102, a beam failure indication 126 that indicates a beam failure is due to at least one of, for example, degradation in the downlink radio link, SI, or CLI from one or more nearby UEs. The network entity 102 decides a beam failure handling strategy and transmits an indication to the UE 104 or at least one of the one or more nearby UEs of one or more actions to take to recover from the beam failure.

[0048] Communication between devices discussed herein, such as between UEs 104 and network entities 102, is performed using any of a variety of different signaling. For example, such signaling can be any of various messages, requests, or responses, such as triggering messages, configuration messages, and so forth. By way of another example, such signaling can be any of various signaling mediums or protocols over which messages are conveyed, such as any combination of radio resource control (RRC), downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI), medium access control element (MAC-CE), sidelink positioning protocol (SLPP), PC5 radio resource control (PC5-RRC) and so forth.

[0049] The wireless communications system 100 can support one or more of HD communications or FD communications. In HD communications, one communication direction, e.g., UL or DL, is allowed at any time resource (e.g., symbol, slot, subframe, frame), where some time-resources are reserved for DL only communications and some other time-resources are reserved for UL only communications. Differently, FD communications allow the UL and the DL communications to occur at the same time resources over some DL and UL subbands that can be fully overlapped, partially overlapped over some PRBs, or fully non-overlapped. [0050] FIG. 2 illustrates examples 200 of FD communication when using beam failure recovery for FD communication in accordance with aspects of the present disclosure. FIG. 2 illustrates fully overlapped, partially overlapped, and fully non-overlapped DL and UL subbands. Fully overlapped DL and UL subbands are illustrated at 202. Partially overlapped DL and UL subbands are illustrated at 204. Fully non-overlapped DL and UL subbands are illustrated at 206.

[0051] FD can have advantages over HD. Compared to HD communications, FD communications can provide, e.g., latency reduction and more efficient resource utilization. For example, a network entity in the FD operation mode does not need to wait for the next available DL slot to transmit a DL message to the served UE, which reduces the latency of the DL transmission. Similarly, a UE in the FD operation mode does not need to wait for the next available UL slot to transmit UL message to the serving network entity, which reduces the latency of the UL transmission. On the other hand, a network entity may utilize the same time-frequency resources to concurrently transmit and receive messages, which improves the time-frequency resources utilization.

[0052] Various different FD scenarios are supported.

[0053] FIG. 3 illustrates examples 300 of different FD scenarios when using beam failure recovery for FD communication in accordance with aspects of the present disclosure. Examples 300 show different implementation scenarios for FD communications. In some scenarios, a FD-capable node, e.g., (gNB or UE) may be equipped with, at least, two antenna array panels or two radioheads (RHs), where one panel (or RH) is used for DL communications and another for UL communications.

[0054] At 302, a UE supporting FD communications and a network entity (e.g., a base station) supporting FD communications are shown.

[0055] At 304, a UE supporting FD communications, a first network entity (e.g., a base station) supporting HD or FD communications, and a second network entity (e.g., a base station) supporting HD or FD are shown. The UE receives DL communications from the first network entity and transmits UL communications to the second network entity.

[0056] At 306, a first UE supporting HD communications, a second UE supporting HD communications, and a network entity (e.g., a base station) supporting FD communications are shown. The first UE receives DL communications from the network entity, and the second UE transmits UL communications to the network entity.

[0057] FD additional interference scenarios: In addition to the classical intra-cell and inter-cell co-channel interference (CCI), a FD-capable device may experience self-interference (SI) and cross-link interference (CLI).

[0058] FIG. 4 illustrates examples 400 of additional interference scenarios in FD communications. For example, a FD-capable network entity 402 may experience SI at its UL reception due to its own DL transmissions. Moreover, the FD-capable network entity 402 may experience a CLI at its UL reception due to DL transmissions from one or more of nearby network entities 404. Similarly, a FD-capable UE 406 may experience SI at its DL reception due to its own UL transmissions, as well as CLI due to UL transmissions from one or more of nearby UEs 408.

[0059] Beam Failure refers to the case when the quality of a certain radio link formed by a beam-pair (e.g., one transmit (Tx) beam and one receive (Rx) beam) falls below a certain threshold, but there is still at least one another beam-pair that may be used to reestablish the connection successfully between the communicating nodes, e.g., UE and network entity.

[0060] Radio Link Failure refers to the case when the quality of a certain radio link formed by a beam-pair (e.g., one Tx beam and one Rx beam) falls below a certain threshold, but there no other beam-pairs that may be used to reestablish the connection successfully between the communicating nodes, e.g., UE and network entity. This implies that the network entity cannot provide connectivity to the UE. Therefore, cell reselection and RRC connection reestablishment is performed.

[0061] Beam failure detection and recovery procedure for HD communications is specified in 3GPP TS 38.321 Section 5.17 version 17.0.0 Release 17 (2022-05), which uses a combination of LI and L2, i.e., Physical (PHY) layer and medium access control (MAC) layer.

[0062] FIG. 5 illustrates an example 500 of DL beam failure monitoring and detection at a UE for HD communications. The example 500 summarizes a DL-based Beam failure detection and recovery procedure. Specifically, once a connected-mode is established, the serving network entity (e.g., a base station) may transmit a RadioLinkMonitoringConfig-IE and a BeamFailureRecoveryConfig-IE to a UE to specify some DL reference signals (RSs) resources, e.g., SSBs or CSLRSs and some parameters the UE may use to monitor the radio link quality, to detect a BFI and to trigger a BFRQ procedure when a specified criteria is met via, e.g., a contention- free random-access (CFRA) procedure with the specified parameters within the BeamFailureRecoveryConfig-IE.

[0063] A similar procedure can be used for a UL based beam failure detection and recovery procedure, with the main difference being that the serving network entity (e.g., a base station) monitors the UL RSs, e.g., SRSs transmitted by the UE to measure some radio link quality metric, e.g., RSRP (Reference Signal Received Power) and uses that to trigger a BFRQ procedure when a specified criteria is met.

[0064] In HD communications, a BFI may occur due to quality degradation in the DL radio link or due to quality degradation in the UL radio link. This may happen due to various reasons, e.g., Tx- Rx beams misalignment due to at least one of UE mobility, rotations, signal blockage from an object in the environment (e.g., a car), or the user body or hand grip.

[0065] In FD communications, on the other hand, a BFI may occur due to one or both of SI or CLI, at one or both of the network entity (e.g., a base station) or the UE, in addition to at least one of quality degradation in the DL radio link or quality degradation in the UL radio link, as exemplified in FIG. 4. For example, in some scenarios, even though the DL radio link have a good quality, e.g., a good RSRP, but a BFI may occur due to one or both of the high SI or high CLI received from one or more of nearby UEs. This can be similarly observed by a network entity (e.g., a base station), where the UL radio link may have a good quality, e.g., a good RSRP, but a BFI may occur due to one or both of a high SI or high CLI received from one or more of nearby network entities (e.g., base stations).

[0066] Accordingly, the techniques discussed herein enhance a beam failure detection and recovery procedure (e.g., as summarized in FIG. 5) to account for the additional reasons causing the beam failure in FD communications, e.g., SI and CLI. Discussed herein are methods and procedures that a node (a network entity (e.g., a base station) or a UE) may take to detect a beam failure and to perform a beam recovery depending on the scenario and the reason causing the beam failure.

[0067] The techniques discussed herein enable a FD-capable UE (also referred to as a UE node) to account for one or both of SI or CLI sources when monitoring the radio link quality and triggering a BFRQ procedure. Depending on the scenario and the main reason causing the beam failure with its level, the serving network entity (e.g., a base station) and the FD-capable node may use different solutions and signaling to successfully overcome the beam failure, e.g., by at least one of switching one or more of active beams to one or more of newly identified beams from a beam candidate set, reducing or increasing the transmit power of a direct downlink radio communication link, or muting or canceling one or more of the interference sources.

[0068] In one or more implementations, a FD-capable target UE node receives from its serving network entity (e.g., a base station) a first configuration message that specifies the time-frequency resources of one or more of a DL-RS resources set, a SI-RS resources set, and/or a CLI-RS resources that can be used by the FD-capable target UE for measuring and monitoring, respectively. This measuring and monitoring may be based on the strength of a received DL link formed by a DL Tx beam at the serving network entity (e.g., a base station) and a DL Rx beam at the target UE. This strength may be the DL-power (PWR), e.g., DL-RSRP or DL-RS SI. Additionally or alternatively, this measuring and monitoring may be based on the strength of a SI link formed by an UL Tx beam at the target UE and a DL Rx beam at the target UE. This strength may be the SI-PWR, e.g., SI- RSRP or SI-RS SI. Additionally or alternatively, this measuring and monitoring may be based on the strength of a CLI link formed by a CLI UL Tx beam at a nearby UE and a DL Rx beam at the target UE. This strength may be the CLI-PWR, e g., CLI-RSRP or CLI-RSSI.

[0069] The target UE may trigger a FD BFRQ procedure, where the UE may identify one or more of DL Tx new beams, DL Rx new beams, UL Tx new beams, or CLI Tx new beams for a nearby UE from one or more of DL Tx candidate beams, DL Rx candidate beams, UL Tx candidate beams, or CLI Tx candidate beams. The target UE may also transmit an indication to the serving network entity (e.g., a base station), e.g., via one or more of a CFRA procedure, a contention-based random-access (CBRA) procedure, or an Uplink Control Information (UCI) one or more of: the one or more of the newly selected beams indices or the quality measurements of the newly selected beams; the main reason causing the beam failure, e.g., indicating whether the beam failure is due to 1) a degradation in the DL link, 2) a SI, 3) a CLI from a nearby second UE, or 4) a SI and a CLI from a nearby UE; a UE recommendation of a beam failure recovery action by the network or by the UE (examples of such recovery actions include Tx/Rx beam switching, power adjustments, resource muting, and so forth), where the possible actions of beam failure recovery is pre-indicated to the UE. [0070] The target UE may receive a second configuration message from the serving network entity (e.g., a base station) that specifies at least one of one or more of random-access channel (RACH) preamble indices, one more of root sequence indices, or one or more of preamble indices sets.

[0071] In the CFRA procedure, in some examples, the target UE may use a first RACH preamble index or a first root sequence index to indicate that the beam failure is due to degradation in the DL link and a second RACH preamble index or a second root sequence index to indicate that the beam failure is due to SI, and so on.

[0072] In the CBRA procedure, in some other examples, the target UE may select a preamble index from a first preamble indices set to indicate that the beam failure is due to degradation in the DL link and select a preamble index from a second preamble indices set to indicate that the beam failure is due to SI, and so on.

[0073] In yet another examples, the target UE may transmit a measurement report to the serving network entity (e.g., a base station) via an UL data/control channel that may include an indication of the reason causing the beam failure with or without its level, e.g., indicating whether the beam failure is mainly due to at least one of a low/high degradation of the DL link, a low/high SI, a low/high CLI, or a low/high SI and a low/high CLI. The indicated level may be used by the serving network entity (e.g., a base station) when deciding on the beam failure handling strategy. In some examples, the UE may be configured by the serving network entity (e.g., a base station) with a lookup table, where the UE may indicate to the network entity (e.g., a base station) the reason causing the beam failure with its level by selecting a row index. Table 1 is an example of such a lookup table. The table can be flexibly designed to include or to remove one or more of levels.

Table 1: Table for indicating reason causing the beam failure with its level [0074] In one or more implementations, upon detection of a DL beam failure at the UE, the UE may determine to utilize the UL data/control channel to indicate at least one of the beam failure, the beam failure reason, or beam failure recovery action recommendation.

[0075] In one or more implementations, upon reception of the UL signaling by the network, the UE receives a DL signaling (e.g., one or more of information or RS) from the network and the UE utilizes, at least in part, the configuration parameters of the UL transmission for the reception of the DL signaling. For example, the UE utilizes the Rx beam with qCL type D relation with the Tx beam of the UL channel. By way of another example, the DL signaling is done at a known time-occasion and frequency domain resource in relation to the UE UL indication of the beam failure. The UE may receive the DL signaling at the same frequency band resources of the UL transmission, or at a first symbol of the next slot/subframe relative to the UL transmission for beam failure indication.

[0076] In one or more implementations, the DL signaling includes an indication that the UL beam failure has not occurred at the serving network entity (e.g., a base station).

[0077] In one or more implementations, one or more of the CBRA or CFRA procedure for the beam failure indication, beam failure reason indication, or beam failure recovery action recommendation indication takes place upon not receiving the DL signaling by the UE according to the pre- indicated time-frequency pattern.

[0078] The UE may receive a beam failure handling indication from the serving network entity (e.g., a base station), e.g., via a RACH response message or via a DL control message, depending on the scenario. For example, the serving network entity (e.g., a base station) may indicate to the UE to reduce or to increase its UL transmit power for one or more of an indicated beam index resources, an overlapped UL-DL PRBs, or a non-overlapped UL-DL PRBs to an indicated level or levels and to reduce or to increase its MCS (Modulation Coding Scheme) order to an indicated order for some indicated or unindicated release time. The UE may assume that it can go back to the original UL transmit power level and the MCS order after the expiration of the indicated release time. Otherwise, the UE may monitor a DL control channel for a release indication to go back to the original UL transmit power level and MCS order. By way of another example, the serving network entity (e.g., a base station) may indicate to the UE to mute its UL transmission over one or more of semi-persistently scheduled overlapped UL-DL PRBs or semi-persistently scheduled non- overlapped UL-DL PRBs for some indicated or unindicated release time. The UE may assume that the UL transmission to the serving network entity (e.g., a base station) may resume after the expiration of the indicated release time. Otherwise, the UE may monitor a DL control channel for an activation message indicating that the UL transmission to the serving network entity (e.g., a base station) may resume.

[0079] In one or more implementations, the UE may be preconfigured with a lookup table, where the network entity (e.g., a base station) may select a row index to indicate to the UE the new UL transmit power it may use on the overlapped DL-UL PRBs and on the non-overlapped DL-UL PRBs, the new MCS order, and the release time. Additionally or alternatively, the release time may be indicated separately using a DL control channel. The lookup table can be flexibly designed such that it considers the minimum and the maximum allowable values of UL transmit power of overlapped PRBs and non-overlapped PRBs, with rationale that the UL transmit power for overlapped PRBs may be smaller than that for non- overlapped PRBs. Additionally or alternatively, the lookup table may consider the minimum and the maximum allowable values of MCS order.

[0080] For example, the lookup table may be designed as shown in Table 2 below, where every row index indicates to the UE the new UL transmit power for overlapped PRBs, the new UL transmit power for non-overlapped PRBs, the new MCS order, and the release time. An empty entry in the release time column implies an unindicated release time. In some examples, the lookup table may include a row where the UL transmit power values are set to zeros to indicate to the UE to mute its UL transmission.

Table 2 A lookup table for new transmit power and new MCS order values and release time

[0081] In some other examples, the lookup table may be designed as shown in Table 3 below, where every row index may indicate to the UE a value that it may use to increase or to decrease its currently used UL transmit power or MCS order. For example, if the row index 0 of Table 3 is indicted by the network entity (e.g., a base station) to the UE, the UE may increase its current UL Tx power P_ui as P_ui = P_ui + P_{o o}, for overlapped PRBs, and as P_ui = P_ui + P_{1 0}, for nonoverlapped PRBs. Similarly, if the row index 1 of Table 3 is indicted by network entity (e.g., a base station) to the UE, the UE may decrease its current UL Tx power P_ui as P_ui = P_ui — P_{0 1}, for overlapped PRBs, and as P_ui = P_ui — P_1:1, for the non-overlapped PRBs.

Table 3 Power and MCS difference

[0082] In some other examples, the modification of the power level of the overlapped and nonoverlapped bands are done such that the total transmission power is not changed, as shown in Table 4. As such, the power increase or decrease at the non-overlapped band is determined at the UE, based on the power difference at the overlapped part.

Table 4 Power and MCS difference with constant total power

[0083] In one or more implementations, the values of Tables 2, 3, and 4 are interpreted in the decibel (dB) scale. Additionally or alternatively, the values of Tables 2, 3, and 4 are interpreted in the linear scale. [0084] FIG. 6 illustrates an example of signaling 600 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. FIG. 6 illustrates a serving network entity (e.g., a base station) 602 (e.g., a network entity 102 of FIG. 1), a target UE 604 (e.g., a UE 104 of FIG. 1), and a nearby UE 606 (e.g., another UE 104 of FIG. 1). Although a single nearby UE 606 is illustrated it is to be appreciated that the serving network entity 602 can communicate with any number of nearby UEs. The serving network entity 602 provides one or more configuration messages 608 to the target UE 604 to configure the target UE 604, and provides one or more configuration messages 610 to the nearby UE 606 to configure the nearby UE 606.

[0085] After the receiving the configuration messages from the serving network entity 602, the target UE 604 enters the beam failure detection stage 612.

[0086] FIG. 7 illustrates an example 700 of a DL beam failure detection stage at a FD-capable UE that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The FD-capable UE is, for example, the UE 604 of FIG. 6. At 702, the target UE may receive one or more of DL-RSs, SI-RSs, or CLI-RSs on their corresponding time-frequency resources and measure the strength, e.g., RSRP or received signal strength indication (RSSI) of each RS, e g., DL PWR, DL_SI_PWR, and DL CLI PWR, where PWR may be RSRP or RSSI. At 704, the UE 604 may calculate a DL quality metric, e.g., the signal to interference plus noise ratio (DL SINR), which may be defined as

DL_PWR DL-^SINR - _{D L-SI-PWR +} DL_CLI_PWR + A_o’ if the noise power N_o is known (note that, in some scenarios, the N_o may also include the other interference sources, e.g., the intra-cell and/or the inter-cell interference), or the signal to interference ratio (DL SIR), which may be defined as if N_o is unknown. Using the measured quality metric (DL SINR or DL SIR), at 706 and 708 the target UE may indicate a BFI, e.g., if the measured quality metric falls below the defined threshold, and send it to the MAC layer. Moreover, the target UE may trigger a DL beam failure once a specified criteria is met, e.g., when the number of BFIs counted by the MAC layer reaches the specified number (e.g., beamFailurelnstanceMaxCount) within the specified time (e.g., beamF ailureDetectionT imer) .

[0087] For example, at 710 the MAC layer receives the BFI from the PHY layer. At 712 and 714, the timer counter (e.g., Timer COUNTER) and the BFI counter (e.g., BFI COUNTER) are set to 0 if the BFI is the first BFI received. At 716, the BFI counter is incremented after the BFI counter is set (at 714) or if at 712 the BFI is not the first BFI received. At 718, if the timer counter equals or exceeds a maximum timer value MaxTimer (e.g., beamFailureDetectionTimer) the timer counter and the BFI counter are reset to 0. At 720 and 722, the target UE triggers a DL beam failure if the BFI counter equals or exceeds a maximum count value MaxCount (e.g., beamF ailurelnstanceMaxCount) .

[0088] Returning to FIG. 6, the target UE may identify the reason causing the DL beam failure, e.g., the target UE may identify that the DL beam failure is mainly due to one of four different reasons. Different beam failure criterion (e.g., different RSs, different thresholds) may be used for these different reasons. Additionally or alternatively, other beam failure criterion may be used, such as an error rate (e.g., a BLER).

[0089] In one case, the DL beam failure is mainly due to a degradation of the DL link. For example, if DL_PWR < ^Threshold, but both DL SL PWR and DL CLI PWR are very low, e.g., DL_SI_PWR < N_o and DL_CLI_PWR < N_o.

T 1 1 T T 1 n , ~_T > . . „ DL_PWR

[0090] In another case, the DL beam tailure is mainly due to SI. For example, it -

’ ^{J 1} ’ DL SI PWR

[0091] In another case, the DL beam failure is mainly due to CLI. For example, if

’ ^{J 1} ’ DL ^D _^L CL ^P I_^W PW^R R

^Threshold but R ~ ^Threshold-

[0092] In another case, the DL beam failure is mainly due to SI and CLI. For example, if

DL PWR m ci PWD Threshold [0093] Additionally, the target UE may identify the level of the reason causing the DL beam failure. Table 5 shows an example of identifying the reason causing the DL beam failure, where percentile(a, 6) = ^ * 100.

Table 5: An example for calculating a level of a reason causing the DL beam failure

[0094] In one or more implementations, the quality threshold ^Threshold may be the same threshold for every case, while in some other implementations, the quality threshold ^Threshold may be different for each case.

[0095] In one or more implementations, the measurement of CLI-PWR further includes the inter- or intra-cell interference (DL-DL interference paths). Additionally or alternatively, the UE obtains contribution of the CLI PWR separated from the contribution of the inter- or intra-cell interference, from the SI, or a combination thereof. In some implementations, the UE indicates to the network the capability to report on the type of the measured interference power, e.g., SI-PWR, CLI-PWR, SI-PWR + CLI-PWR.

[0096] In one or more implementations, when the UE is indicated with the measurement of the CLI PWR, the network one or more of mutes the DL transmissions coexisting with the same CLI- RS resources or indicates to the UE the RS-defining parameters (time- frequency resources, RS sequence, etc.) associated with the CLI measurements. Additionally or alternatively, the CLI PWR measurements are conducted at the UE at an indicated time-frequency resources, where the network mutes the DL transmissions at the indicated resources. The obtained CLI PWR is then measured at the UE after the SI measurement and reduction, as the collected power measurements at the indicated resources (RSSI of the remaining signal after the SI cancellation). Additionally or alternatively, the CLI PWR is measured as an RSRP value after the reduction of the SI, where the RSRP value is measured upon indication of the RS-defining parameters by the network.

[0097] If a DL beam failure is detected, the target UE may trigger a BFRQ procedure 614, where the target UE 604 may perform some quality measurements using at least one of one or more of the DL Tx candidate beams, one or more of the DL Rx candidate beams, one or more of the UL Tx candidate beams, or one or more of the CLI Tx candidate beams.

[0098] FIG. 8 illustrates an example 800 of quality measurements at a UE using one or more candidate beams that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. Illustrated in the example 800 are a DL Tx candidate beam n 802, a DL Rx candidate beam k 804, a UL Tx candidate beam j 806, and a CLI Tx candidate beam i 808.

[0099] For every measurement scenario, the UE 604 may calculate a quality metric, e.g.,

DL SINR or DL SIR as where, e.g., DLp’^,_R denotes the signal strength between n^th DL Tx candidate beam and k^th DL Rx candidate beam.

[0100] Returning to FIG. 6, given the quality measurements above, the UE 604 may select at least one of one or more of new DL Tx beams, one or more of new DL Rx beam, one or more of new UL Tx beam, or one or more of new CLI Tx beams for one or more of its nearby UEs. This selection may be based, for example, on the ones corresponding to the maximum DL_SIN ^Threshold measurement scenario. By way of another example, this selection may be based on the ones corresponding to a DL_SIN measurement scenario that does not involve, e.g., a CLI Tx beam switching, an UL Tx or DL Tx beam switching, or any other desired selection criteria.

[0101] The target UE 604 after that may transmit a beam failure indication 616 to the serving network entity 602, e.g., via one or more of a CFRA procedure, a CBRA procedure, or a UCI carried by physical uplink control channel (PUCCH)/ physical uplink shared channel (PUSCH) indicating one or more of: at least one of the one or more of the newly selected beam indices or their quality measurements; the main reason causing the beam failure with or without its level; a UE recommendation of a beam failure recovery action by the network or by the UE (examples of such actions include Tx/Rx beam switching, power adjustments, resource muting, etc.), where the possible actions of beam failure recovery are pre-indicated to the UE.

[0102] The serving network entity 602 performs beam failure handling 618 and may decide on and indicate the best beam failure handling strategy to the target UE 604 considering the indicated new beam indices or measurements, the reason of the DL beam failure with its level, and the known priority levels of target UE DL and UL traffics, and nearby UEs CLI traffics. The serving network entity 602 transmits one or more of a beam failure handling indication 620 to the target UE 604 or a beam failure handling indication 622 to the nearby UE 606.

[0103] In one or more implementations, in a case that at least one of the measurement quality metrics (e.g., DL_SINR_{n k ;} satisfies the quality threshold, (e.g., DL_SIN , the beam failure may be resolved by switching one or more of the active beams to one or more of the beams indicated by the target UE 604.

[0104] Additionally or alternatively, such as if none of the quality measurement scenarios above satisfies the quality threshold (e.g., DL_SIN k,j, i), the beam failure may still be resolved by improving the quality of the DL link or by reducing or eliminating one or more of the interference sources.

[0105] In a case where DL beam failure is due to a degradation in the DL link (case 1), the serving network entity 602 may decide on increasing its DL Tx power by some level depending on, e.g., the indicated DL degradation level, such as by increasing its Tx power by, e.g., 1 decibel (dB), if the indicated DL degradation level is low. For other scenarios, e.g., if the indicated DL degradation level is high, the serving network entity 602 may indicate a radio link failure and the target UE 604 may enter a cell reselection procedure.

[0106] In a case where DL beam failure is mainly due to SI (case 2), the serving network entity 602 may indicate to the target UE, in the case of low SI level, to reduce its UL transmit power for an indicated beam index resources, overlapped UL-DL PRBs, or non-overlapped UL-DL PRBs by some level and to reduce its MCS by some order for some indicated release time, e.g., by selecting and indicating a row index from Table 2, Table 3, or Table 4 above. Differently, in the case of high SI level, the serving network entity 602 may indicate to the target UE 604 to mute its UL transmission over semi-persistently scheduled overlapped UL-DL PRBs, or over semi-persistently scheduled non-overlapped UL-DL PRBs, or both for some indicated release time, e.g., by selecting and indicating a row index from Table 2, Table 3, or Table 4 above, such as if the UL traffic has lower priority than the DL traffic.

[0107] In a case where beam failure is mainly due to the CLI (case 3), the serving network entity 602 may indicate to a nearby UE 606, in the case of low CLI level, to reduce its UL (e.g., CLI) transmit power for an indicated beam index resources, overlapped UL-DL PRBs, or nonoverlapped UL-DL PRBs by some level and to reduce its MCS by some order for some indicated release time, e.g., by selecting and indicating a row index from Table 2, Table 3, or Table 4 above. Differently, in the case of high CLI level, the serving network entity 602 may indicate to a nearby UE 606 to mute its UL transmission over semi-persistently scheduled overlapped UL-DL PRBs, or over semi-persistently scheduled non-overlapped UL-DL PRBs, or both for some indicated release time, e.g., by selecting and indicating a row index from Table 2, Table 3, or Table 4 above, such as if the DL traffic of the target UE 604 has higher priority than the UL traffic of the nearby UE 606. The list of the nearby UEs causing low/high CLI may be indicated by the target UE 604 to its serving network entity 602, where the target UE 604 may identify these nearby UEs during its beam failure detection stage, or the network entity 602 may identify these nearby UEs based on some metrics, e.g., based on their distance to the target UE 604 or based on the time- frequency resources allocated to the nearby UEs.

[0108] In a case where beam failure is due to the SI and the CLI (case 4), the serving network entity 602 may use some combination of the above solution methods for Case 2 and Case 3 to recover the connection with the target UE 604.

[0109] Additionally or alternatively, a FD-capable first network entity (e.g., a base station) node may send a request to a nearby second network entity (e.g., a base station) for uplink beam failure handling, e.g., via a backhaul connection or via an OTA (Over the Air) transmission, for example, to decrease its downlink transmit power over an indicated time-frequency resources by an indicated level, to mute its downlink transmission over an indicated time-frequency resources, or to switch an active CLI Tx beam index to an indicated CLI Tx beam index identified from a candidate beam set coordinated between the two network entities.

[0110] The first network entity may receive a response back from the nearby second network entity indicating whether the request is accepted or not. The response may be explicit, via for example, an acknowledgement (ACK)/ no acknowledgement (NACK) response message or implicit, where, for example, the NACK message is indicated by not sending (or receiving) a response.

[0111] FIG. 9 illustrates an example 900 of quality measurements at a network entity using one or more candidate beams that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. Illustrated in the example 900 are a target network entity 902 making the uplink quality measurements, a UE 904 served by the target network entity 902, and a nearby network entity 906. Also illustrated are a CLI Tx candidate beam i 908, a DL Tx candidate beam j 910, a UL Rx candidate beam & 912, and a UL Tx candidate beam n 914.

[0112] In one or more implementations, the IE RadioLinkMonitoringConfig is used to configure radio link monitoring for detection of beam- and/or cell radio link failure.

[0113] FIGs. 10A and 10B illustrate an example 1000 of a RadioLinkMonitoringConfig information element that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0114] An additionalPCI field indicates the physical cell IDs (PCI) of the SSBs in the failureDetectionSet2. If candidateBeamRS-List2 is configured in IE BeamFailureRecoveryRSConfig the field indicates the physical cell IDs (PCI) of the SSBs in the candidateBeamRS-List2.

[0115] A beamFailureDetectionTimer field indicates a timer for beam failure detection. Value in number of "Qout,LR reporting periods of Beam Failure Detection" Reference Signal. Value pbfdl corresponds to 1 Qout,LR reporting period of Beam Failure Detection Reference Signal, value pbfd2 corresponds to 2 Qout,LR reporting periods of Beam Failure Detection Reference Signal and so on. [0116] A beamFailurelnstanceMaxCount field determines after how many beam failure events the UE triggers beam failure recovery. Value nl corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on.

[0117] A failureDetectionResourcesToAddModList field indicates a list of reference signals for detecting beam failure and/or cell level radio link failure (RLF). The limits of the reference signals that the network can configure are specified in 3rd Generation Partnership Project (3GPP) technical specification (TS) 38.213 [13], table 5-1. The network configures at most two detectionResources per bandwidth part (BWP) for the purpose beamFailure or both. If no RSs are provided for the purpose of beam failure detection, the UE performs beam monitoring based on the activated TCI- State for physical downlink control channel (PDCCH )as described in 3 GPP TS 38.213 [13], clause 6. If no RSs are provided in this list for the purpose of RLF detection, the UE performs Cell-RLM based on the activated TCI-State of PDCCH as described in 3GPP TS 38.213 [13], clause 5. The network ensures that the UE has a suitable set of reference signals for performing cell-RLM. If failureDetectionSetl-rl7 and failureDetectionSet2-rl7 are present, the purpose of RadioLinkMonitoringRS in failureDetectionResourcesToAddModList may be set to rlf.

[0118] FailureDetectionSetl and failureDetectionSet2 fields configure parameters for beamfailure detection towards beam failure detection resources configured in the set. If additional PCIs are configured using additionalPCI-ToAddModList for the serving cell, each RS in one set can be associated a single PCI. Network always configures the failureDetectionSetl and failureDetectionSet2 together. When a failureDetectionSetN is present, after the reconfiguration, the UE shall consider all the reference signals for this failure detection set as activated if at most maxBFD-RS-resourcesPerSetPerBWP-rl7 reference signals are configured for each failure detection set, otherwise the UE shall consider all the reference signals in this failure detection set as deactivated.

[0119] A detectionResource field indicates a reference signal that the UE shall use for radio link monitoring or beam failure detection (depending on the indicated purpose). Periodic 1-port CSI-RS can be configured on SCell for beam failure detection purpose. [0120] A purpose filed determines whether the UE shall monitor the associated reference signal for the purpose of cell- and/or beam failure detection. For SCell, network configures the value to beamFailure.

[0121] In one or more implementations, the IE BeamFailureRecoveryConfig is used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection.

[0122] FIGs. 11 A and 1 IB illustrate an example 1100 of a BeamFailureRecoveryConfig information element that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure.

[0123] The following fields are included in BeamFailureRecoveryConfig.

[0124] A beamFailur eRecovery Timer field indicates a timer for beam failure recovery timer.

Upon expiration of the timer the UE does not use CFRA for BFR. Value in ms. Value mslO corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on.

[0125] CandidateBeamRSList and candidateBeamRSListExt-vl610 fields indicate a set of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters. This set includes all elements of CandidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-vl610. The UE maintains CandidateBeamRSList and candidateBeamRSListExt-vl610 separately: Receiving candidateBeamRSListExt-vl610 set to release releases the entries that were configured by candidateBeamRSListExt-vl610, and receiving candidateBeamRSListExt-vl610 set to setup replaces the entries that were configured by candidateBeamRSListExt-vl610 with the newly signalled entries. The network configures these reference signals to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided.

[0126] A msg 1 -SubcarrierSpacing field indicates a subcarrier spacing for contention free beam failure recovery (see 3GPP TS 38.211 [16], clause 5.3.2). The following values are applicable depending on the used frequency: FR1 : 15 or 30 kHz; FR2-1 : 60 or 120 kHz; FR2-2: 120, 480, or 960 kHz. [0127] A rsrp-ThresholdSSB field indicates a Ll-RSRP threshold used for determining whether a candidate beam may be used by the UE to attempt contention free random access to recover from beam failure (see 3GPP TS 38.213 [13], clause 6).

[0128] A ra-prioritization field indicates parameters which apply for prioritized random access procedure for BFR (see 3GPP TS 38.321 [3], clause 5.1.1).

[0129] A ra-PrioritizationTwoStep field indicates parameters which apply for prioritized 2-step random access procedure for BFR (see 3GPP TS 38.321 [3], clause 5.1.1).

[0130] A ra-ssb-OccasionMasklndex field indicates an explicitly signalled physical random access channel (PRACH) Mask Index for RA Resource selection in 3GPP TS 38.321 [3], The mask is valid for all SSB resources.

[0131] A rach-ConfigBFR field indicates a configuration of random access parameters for BFR.

[0132] A recoverySearchSpaceld field indicates a search space to use for BFR random access response (RAR). The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the

BeamFailureRecoveryConfig is provided. The CORESET associated with the recovery search space cannot be associated with another search space. Network always configures the UE with a value for this field when contention free random access resources for BFR are configured.

[0133] A roots equencelndex-BFR field indicates a PRACH root sequence index (see 3GPP TS

38.211 [16], clause 6.3.3.1) for beam failure recovery.

[0134] A spCell-BFR-CBRA field indicates that UE is configured to send BFR MAC CE for SpCell BFR as specified in 3GPP TS38.321 [3],

[0135] A ssb-perRACH-Occasion field indicates a number of SSBs per RACH occasion for CF- BFR, see 3GPP TS 38.213 [13], clause 8.1.

[0136] The following fields are included in BFR-CSIRS-Resource.

[0137] A csi-RS field indicates the ID of a NZP-CSI-RS-Resource configured in the CSI- MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR). [0138] A ra-OccasionList field indicates RA occasions that the UE shall use when performing BFR upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-Configurationlndex and msgl-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots. If the field is absent the UE uses the RA occasion associated with the SSB that is QCLed with this CSI-RS.

[0139] A ra-Preamblelndex field indicates the RA preamble index to use in the RA occasions associated with this CSI-RS. If the field is absent, the UE uses the preamble index associated with the SSB that is QCLed with this CSI-RS.

[0140] The following fields are included in BFR-SSB-Resource.

[0141] A ra-Preamblelndex indicates the preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB.

[0142] A ssb field indicates the ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR).

[0143] The following fields are included in RadioLinkMonitoringConfig.

[0144] An additionalPCI field indicates the physical cell IDs (PCI) of the SSBs in the failureDetectionSet2. If candidateBeamRS-List2 is configured in IE BeamFailureRecoveryRSConfig the field indicates the physical cell IDs (PCI) of the SSBs in the candidateBeamRS-List2.

[0145] A beamFailureDetectionTimer field indicates a timer for beam failure detection (see 3GPP TS 38.321 [3], clause 5.17). See also the BeamFailureRecoveryConfig IE. Value in number of "Qout,LR reporting periods of Beam Failure Detection" Reference Signal (see 3GPP TS 38.213 [13], clause 6). Value pbfdl corresponds to 1 Qout,LR reporting period of Beam Failure Detection Reference Signal, value pbfd2 corresponds to 2 Qout,LR reporting periods of Beam Failure Detection Reference Signal and so on. [0146] A beamFailurelnstanceMaxCount field determines after how many beam failure events the UE triggers beam failure recovery (see 3GPP TS 38.321 [3], clause 5.17). Value nl corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on.

[0147] A failureDetectionResourcesToAddModList field indicates a list of reference signals for detecting beam failure and/or cell level radio link failure (RLF). The limits of the reference signals that the network can configure are specified in 3GPP TS 38.213 [13], table 5-1. The network configures at most two detectionResources per BWP for the purpose beamFailure or both. If no RSs are provided for the purpose of beam failure detection, the UE performs beam monitoring based on the activated TCI-State for PDCCH as described in 3GPP TS 38.213 [13], clause 6. If no RSs are provided in this list for the purpose of RLF detection, the UE performs Cell-radio link monitoring (RLM) based on the activated TCI-State of PDCCH as described in 3GPP TS 38.213 [13], clause 5. The network ensures that the UE has a suitable set of reference signals for performing cell-RLM. If failureDetectionSetl-rl7 and failureDetectionSet2-rl7 are present, the purpose of RadioLinkMonitoringRS in failureDetectionResourcesToAddModList can be set to rlf.

[0148] A failureDetectionSetl, failureDetectionSet2 field configures parameters for beamfailure detection towards beam failure detection resources configured in the set. If additional PCIs are configured using additionalPCI-ToAddModList for the serving cell, each RS in one set can be associated with one PCI. Network always configures the failureDetectionSetl and failureDetectionSet2 together. When a failureDetectionSetN is present, after the reconfiguration, the UE shall consider all the reference signals for this failure detection set as activated if at most maxBFD-RS-resourcesPerSetPerBWP-rl7 reference signals are configured for each failure detection set, otherwise the UE shall consider all the reference signals in this failure detection set as deactivated.

[0149] Beamforming, antenna panel, antenna port, quasi-collocation, transmission configuration indicator (TCI) state, and spatial relation are discussed herein. Various implementation discussed herein refer to beamforming-related terms such as beam, antenna, and so on. Despite frequent reference to such plain terms in the present disclosure, the terminology adopted in the 3 GPP specification makes use of a range of other terms. Some of these terms are described below. [0150] The terms beam and beamforming may refer to applying a spatial filter, in analog or digital domains, when transmitting or receiving a signal by one or multiple antennas, antenna panels, antenna elements, or the like. Therefore, the term beam may refer to a spatial filter in the analog domain on a transmitting antenna or a receiving antenna, a spatial filter in the digital domain, a reference signal transmitted while applying a spatial filter, a resource associated with the reference signal, or the like. Similarly, a beam index may refer to an index or ID associated with a spatial filter, a reference signal, or a reference signal resource.

[0151] In one or more implementations, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel may be a hardware that is used for transmitting and/or receiving radio signals at frequencies lower than 6GHz, e.g., frequency range 1 (FR1), or higher than 6GHz, e.g., frequency range 2 (FR2) or millimeter wave (mmWave). In some implementations, an antenna panel may include an array of antenna elements, where each antenna element is connected to a hardware such as a phase shifter that allows a control module to apply spatial parameters for transmission and/or reception of signals. The resulting radiation pattern may be called a beam, which may or may not be unimodal and may allow the device (e.g., UE, node) to amplify signals that are transmitted or received from one or multiple spatial directions.

[0152] In one or more implementations, an antenna panel may or may not be virtualized as an antenna port. An antenna panel may be connected to a baseband processing module through a radio frequency (RF) chain for each of transmission (egress) and reception (ingress) directions. A capability of a device in terms of the number of antenna panels, their duplexing capabilities, their beamforming capabilities, and so on, may or may not be transparent to other devices. In some implementations, capability information may be communicated via signaling or, in some implementations, capability information may be provided to devices without a need for signaling. In the case that such information is available to other devices such as a CU, it can be used for signaling or local decision making.

[0153] In one or more implementations, an antenna panel may be a physical or logical antenna array including a set of antenna elements or antenna ports that share a common or a significant portion of an RF chain (e.g., in-phase/quadrature (I/Q) modulator, analog-to-digital (A/D) converter, local oscillator, phase shift network). The antenna panel may be a logical entity with physical antennas mapped to the logical entity. The mapping of physical antennas to the logical entity may be up to implementation. Communicating (receiving or transmitting) on at least a subset of antenna elements or antenna ports active for radiating energy (also referred to herein as active elements) of an antenna panel involves biasing or powering on of the RF chain which results in current drain or power consumption in the device (e.g., node) associated with the antenna panel (including power amplifier/low noise amplifier (LNA) power consumption associated with the antenna elements or antenna ports). The phrase "active for radiating energy," as used herein, is not meant to be limited to a transmit function but also encompasses a receive function. Accordingly, an antenna element that is active for radiating energy may be coupled to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, either simultaneously or sequentially, or may be coupled to a transceiver in general, for performing its intended functionality. Communicating on the active elements of an antenna panel enables generation of radiation patterns or beams.

[0154] In one or more implementations, depending on implementation, a “panel” can have at least one of the following functionalities as an operational role of Unit of antenna group to control its Tx beam independently, Unit of antenna group to control its transmission power independently, Unit of antenna group to control its transmission timing independently. The “panel” may be transparent to another node (e.g., next hop neighbor node). For certain condition(s), another node or network entity can assume the mapping between device's physical antennas to the logical entity “panel” may not be changed. For example, the condition may include until the next update or report from device or comprise a duration of time over which the network entity assumes there will be no change to the mapping. Device may report its capability with respect to the “panel” to the network entity. The device capability may include at least the number of “panels”. In one implementation, the device may support transmission from one beam within a panel; with multiple panels, more than one beam (one beam per panel) may be used for transmission. In another implementation, more than one beam per panel may be supported/used for transmission.

[0155] In one or more implementations, an antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. Two antenna ports are said to be quasi colocated (QCL) if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. Two antenna ports may be quasilocated with respect to a subset of the large-scale properties and different subset of large-scale properties may be indicated by a QCL Type. The QCL Type can indicate which channel properties are the same between the two reference signals (e.g., on the two antenna ports). Thus, the reference signals can be linked to each other with respect to what the device can assume about their channel statistics or QCL properties. For example, QCL-Type may take one of the following values. Other QCL Types may be defined based on combination of one or large-scale properties:

'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

'QCL-TypeB': {Doppler shift, Doppler spread}

'QCL-TypeC: {Doppler shift, average delay} 'QCL-TypeD': {Spatial Rx parameter}.

[0156] Spatial Rx parameters may include one or more of: angle of arrival (AoA), dominant AoA, average AoA, angular spread, Power Angular Spectrum (PAS) of AoA, average angle of departure (AoD), PAS of AoD, transmit/receive channel correlation, transmit/receive beamforming, spatial channel correlation, etc.

[0157] The QCL-TypeA, QCL-TypeB and QCL-TypeC may be applicable for all carrier frequencies, but the QCL-TypeD may be applicable in higher carrier frequencies (e.g., mmWave, FR2 and beyond), where essentially the device may not be able to perform omni-directional transmission, i.e., the device would need to form beams for directional transmission. A QCL-TypeD between two reference signals A and B, the reference signal A is considered to be spatially colocated with reference signal B and the device may assume that the reference signals A and B can be received with the same spatial filter (e.g., with the same Rx beamforming weights).

[0158] An “antenna port” according to one or more implementations may be a logical port that may correspond to a beam (resulting from beamforming) or may correspond to a physical antenna on a device. In some implementations, a physical antenna may map directly to a single antenna port, in which an antenna port corresponds to an actual physical antenna. Additionally or alternatively, a set or subset of physical antennas, or antenna set or antenna array or antenna sub-array, may be mapped to one or more antenna ports after applying complex weights, a cyclic delay, or both to the signal on each physical antenna. The physical antenna set may have antennas from a single module or panel or from multiple modules or panels. The weights may be fixed as in an antenna virtualization scheme, such as cyclic delay diversity (CDD). The procedure used to derive antenna ports from physical antennas may be specific to a device implementation and transparent to other devices.

[0159] In one or more implementations, a TCI-state (Transmission Configuration Indication) associated with a target transmission can indicate parameters for configuring a quasi-collocation relationship between the target transmission (e.g., target RS of DM-RS ports of the target transmission during a transmission occasion) and a source reference signal(s) (e.g., SSB/CSI- RS/SRS) with respect to quasi co-location type parameter(s) indicated in the corresponding TCI state. The TCI describes which reference signals are used as QCL source, and what QCL properties can be derived from each reference signal. A device can receive a configuration of a plurality of transmission configuration indicator states for a serving cell for transmissions on the serving cell (e.g., between a serving gNB and a smart repeater). In some of the implementations described, a TCI state comprises at least one source RS to provide a reference (device assumption) for determining QCL and/or spatial filter.

[0160] In one or more implementations, a UL TCI state is provided if a device is configured with separate DL/UL TCI by RRC signaling. The UL TCI state may comprise a source reference signal which provides a reference for determining UL spatial domain transmission filter for the UL transmission (e.g., dynamic-grant/configured-grant based PUSCH, dedicated PUCCH resources) in a CC or across a set of configured CCs/BWPs.

[0161] In one or more implementations, a joint DL/UL TCI state is provided if the device is configured with joint DL/UL TCI by RRC signaling (e.g., configuration of joint TCI or separate DL/UL TCI is based on RRC signaling). The joint DL/UL TCI state refers to at least a common source reference RS used for determining both the DL QCL information and the UL spatial transmission filter. The source RS determined from the indicated joint (or common) TCI state provides QCL Type-D indication (e.g., for device-dedicated PDCCH/physical downlink shared channel (PDSCH)) and is used to determine UL spatial transmission filter (e.g., for UE-dedicated PUSCH/PUCCH) for a CC or across a set of configured CCs/BWPs. In one example, the UL spatial transmission filter is derived from the RS of DL QCL Type D in the joint TCI state. The spatial setting of the UL transmission may be according to the spatial relation with a reference to the source RS configured with qcl-Type set to 'typeD' in the joint TCI state.

[0162] In one or more implementations, a spatial relation information associated with a target transmission can indicate parameters for configuring a spatial setting between the target transmission and a reference RS (e.g., SSB/CSI-RS/SRS). For example, the device may transmit the target transmission with the same spatial domain filter used for reception the reference RS (e.g., DL RS such as SSB/CSI-RS). In another example, the device may transmit the target transmission with the same spatial domain transmission filter used for the transmission of the reference RS (e.g., UL RS such as SRS). A device can receive a configuration of a plurality of spatial relation information configurations for a serving cell for transmissions on the serving cell.

[0163] In one or more implementations, a UL TCI state is provided if a device is configured with separate DL/UL TCI by RRC signaling. The UL TCI state may comprise a source reference signal which provides a reference for determining UL spatial domain transmission filter for the UL transmission (e.g., dynamic-grant/configured-grant based PUSCH, dedicated PUCCH resources) in a CC or across a set of configured CCs/BWPs.

[0164] In one or more implementations, a joint DL/UL TCI state is provided if the device is configured with joint DL/UL TCI by RRC signaling (e.g., configuration of joint TCI or separate DL/UL TCI is based on RRC signaling). The joint DL/UL TCI state refers to at least a common source reference RS used for determining both the DL QCL information and the UL spatial transmission filter. The source RS determined from the indicated joint (or common) TCI state provides QCL Type-D indication (e.g., for device-dedicated PDCCH/PDSCH) and is used to determine UL spatial transmission filter (e.g., for UE-dedicated PUSCH/PUCCH) for a CC or across a set of configured CCs/BWPs. In one example, the UL spatial transmission filter is derived from the RS of DL QCL Type D in the joint TCI state. The spatial setting of the UL transmission may be according to the spatial relation with a reference to the source RS configured with qcl-Type set to 'typeD' in the joint TCI state.

[0165] Accordingly, enhancing the classical beam failure detection and recovery procedure of half-duplex devices to account for the additional SI and CLI experience in full-duplex capable devices is discussed herein. Furthermore, enhancing the measurement report to include the main reason causing the beam failure at a FD-capable node with its level is discussed herein. Additionally, a flexible codebook-based uplink power control is introduced to facilitate the network entity (e.g., a base station) to UE indications to increase or to decrease its uplink power or to mute its uplink transmission over overlapped and non-overlapped PRBs.

[0166] FIG. 12 illustrates an example of a block diagram 1200 of a device 1202 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The device 1202 may be an example of a UE 104 as described herein. The device 1202 may also be referred to as an apparatus. The device 1202 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1202 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1204, a memory 1206, a transceiver 1208, and an I/O controller 1210. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0167] The processor 1204, the memory 1206, the transceiver 1208, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 1204, the memory 1206, the transceiver 1208, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0168] In some implementations, the processor 1204, the memory 1206, the transceiver 1208, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 1204 and the memory 1206 coupled with the processor 1204 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1204, instructions stored in the memory 1206). [0169] For example, the processor 1204 may support wireless communication at the device 1202 in accordance with examples as disclosed herein. Processor 1204 may be configured as or otherwise support to: receive, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; transmit, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more UEs; and receive, from the network entity, a third signaling indicating a configuration for handling a beam failure.

[0170] Additionally or alternatively, the processor 1204 may be configured to or otherwise support: to: trigger, in response to a beam failure criterion being met, a beam failure recovery procedure in accordance with the configuration for handling the beam failure; and transmit the second signaling as part of the beam failure recovery procedure; where the first signaling is a part of a radio resource control RadioLinkMonitoringConfig-informationelement; where the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-informationelement; where: the one or more RS resources for measuring downlink radio link quality level comprise at least one of synchronization signal block (SSB) or channel state information-RS resources; and the one or more RS resources for measuring a self-interference level or a cross-link interference level comprise at least one of sounding reference or demodulation-RS resources, or a dedicated RS for selfinterference and cross-link interference probing of a full-duplex transceiver; where the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets; where the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention-free random-access or a contention-based random-access procedure; where the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message; where the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels; where the third signaling includes a first uplink transmit power value dedicated for overlapped UL-DL PRBs and a second uplink transmit power value dedicated for non-overlapped UL-DL PRBs; where the third signaling includes an indication to increase or to decrease an uplink transmit power over overlapped and nonoverlapped UL-DL PRBs by indicating a row index corresponding to a preconfigured uplink power control lookup table; where the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi-persistently scheduled overlapped UL-DL PRBs, or mute uplink transmission over semi-persistently scheduled non-overlapped UL-DL PRBs; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a new uplink transmit power for overlapped UL-DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a MCS order, or a release time; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a power difference and a MCS order difference the apparatus may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for non-overlapped UL-DL PRBs, or a current MCS order; where a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table; where the beam failure criterion for a full-duplex beam failure includes at least one of downlink radio link quality level, self-interference quality level, or cross-link interference quality level; where the beam failure criterion include at least one of a signal-to-interference-plus-noise ratio, a signal-to- interference ratio, or a BLER; where the apparatus comprises a UE.

[0171] For example, the processor 1204 may support wireless communication at the device 1202 in accordance with examples as disclosed herein. Processor 1204 may be configured as or otherwise support a means for receiving, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; transmitting, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more UEs; and receiving, from the network entity, a third signaling indicating a configuration for handling a beam failure.

[0172] Additionally or alternatively, the processor 1204 may be configured to or otherwise support: triggering, in response to a beam failure criterion being met, a beam failure recovery procedure in accordance with the configuration for handling the beam failure; and transmitting the second signaling as part of the beam failure recovery procedure; where the first signaling is a part of a radio resource control RadioLinkMonitoringConfig-informationelement; where the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-informationelement; where: the one or more RS resources for measuring downlink radio link quality level comprise at least one of SSB or channel state information-RS resources; and the one or more RS resources for measuring a self-interference level or a cross-link interference level comprise at least one of sounding reference or demodulation-RS resources, or a dedicated RS for self-interference and cross-link interference probing of a full-duplex transceiver; where the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets; where the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention-free random-access or a contention-based random-access procedure; where the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message; where the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels; where the third signaling includes a first uplink transmit power value dedicated for overlapped UL-DL PRBs and a second uplink transmit power value dedicated for non-overlapped UL-DL PRBs; where the third signaling includes an indication to increase or to decrease an uplink transmit power over overlapped and non-overlapped UL-DL PRBs by indicating a row index corresponding to a preconfigured uplink power control lookup table; where the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi-persistently scheduled overlapped UL-DL PRBs, or mute uplink transmission over semi-persistently scheduled non-overlapped UL- DL PRBs; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a new uplink transmit power for overlapped UL- DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a MCS order, or a release time; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a power difference and a MCS order difference an apparatus implementing the method may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for non-overlapped UL-DL PRBs, or a current MCS order; where a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table; where the beam failure criterion for a full-duplex beam failure includes at least one of downlink radio link quality level, self-interference quality level, or cross-link interference quality level; where the beam failure criterion include at least one of a signal-to-interference-plus-noise ratio, a signal-to-interference ratio, or a BLER; where the method is implemented in a UE.

[0173] The processor 1204 of the device 1202, such as a UE 104, may support wireless communication in accordance with examples as disclosed herein. The processor 1204 includes at least one controller coupled with at least one memory, and is configured to or operable to cause the processor to receive, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more reference signal (RS) resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; transmit, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more UEs; and receive, from the network entity, a third signaling indicating a configuration for handling a beam failure.

[0174] The processor 1204 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 implementations, the processor 1204 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 1204. The processor 1204 may be configured to execute computer- readable instructions stored in a memory (e.g., the memory 1206) to cause the device 1202 to perform various functions of the present disclosure.

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

[0176] The I/O controller 1210 may manage input and output signals for the device 1202. The I/O controller 1210 may also manage peripherals not integrated into the device 1202. In some implementations, the I/O controller 1210 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1210 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 1210 may be implemented as part of a processor, such as the processor 1204. In some implementations, a user may interact with the device 1202 via the I/O controller 1210 or via hardware components controlled by the I/O controller 1210.

[0177] In some implementations, the device 1202 may include a single antenna 1212. However, in some other implementations, the device 1202 may have more than one antenna 1212 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1208 may communicate bi-directionally, via the one or more antennas 1212, wired, or wireless links as described herein. For example, the transceiver 1208 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1208 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1212 for transmission, and to demodulate packets received from the one or more antennas 1212.

[0178] FIG. 13 illustrates an example of a block diagram 1300 of a device 1302 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The device 1302 may be an example of a network entity 102 as described herein. The device 1302 may also be referred to as an apparatus. The device 1302 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1302 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1304, a memory 1306, a transceiver 1308, and an I/O controller 1310. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0179] The processor 1304, the memory 1306, the transceiver 1308, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 1304, the memory 1306, the transceiver 1308, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0180] In some implementations, the processor 1304, the memory 1306, the transceiver 1308, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 1304 and the memory 1306 coupled with the processor 1304 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1304, instructions stored in the memory 1306).

[0181] For example, the processor 1304 may support wireless communication at the device 1302 in accordance with examples as disclosed herein. Processor 1304 may be configured as or otherwise support to: transmit, to a first UE, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; receive, from the first UE, a second signaling that indicates that a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more second UEs; and transmit, to the first UE, a third signaling indicating a configuration for handling a beam failure.

[0182] Additionally or alternatively, the processor 1304 may be configured to or otherwise support: to transmit, to one or more network entities, a fourth signaling indicating a request for uplink beam failure handling; to receive, from one of the one or more network entities, a fifth signaling indicating whether the request is accepted or not accepted; where the fourth signaling indicates to at least one of the one or more network entities to decrease a downlink transmit power over an indicated time-frequency resources by an indicated level; where the fourth signaling indicates to at least one of the one or more network entities to mute a downlink transmission over an indicated time- frequency resources; where the fourth signaling indicates to at least one of the one or more network entities to switch an active downlink beam index to an indicated beam index from a candidate beam set coordinated between the apparatus and the at least one of the one or more network entities; where the fifth signaling indicates at least one of an acknowledgment response message or a negative acknowledgment response message; where a negative acknowledgment response to the request is indicated by a lack of a fifth signaling from at least one of the one or more network entities indicating that the request is not accepted; where the processor is further configured to cause the apparatus to receive the second signaling as part of a beam failure recovery procedure; where the first signaling is a part of a radio resource control RadioLinkMonitoringConfig-information element; where the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-information element; where: the one or more RS resources for measuring downlink radio link quality level comprise at least one of SSB or channel state information-RS resources; and the one or more RS resources for measuring a self-interference level or a cross-link interference level comprise at least one of sounding reference or demodulation- RS resources, or a dedicated RS for self-interference and cross-link interference probing of a full- duplex transceiver; where the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets; where the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention-free random-access or a contention-based random-access procedure; where the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message; where the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels; where the third signaling includes a first uplink transmit power value dedicated for overlapped uplinkdownlink physical resource blocks and a second uplink transmit power value dedicated for non- overlapped uplink-downlink physical resource blocks; where the third signaling includes an indication to increase or to decrease uplink transmit power over overlapped and non-overlapped UL-DL PRBs by indicating a row index corresponding to a preconfigured uplink power control lookup table; where the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi-persistently scheduled overlapped uplink-downlink physical resource blocks, or mute transmission over semi-persistently scheduled non-overlapped uplink-downlink physical resource blocks; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates a new uplink transmit power for overlapped UL-DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a modulation coding scheme order, and a release time; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates a power difference and a MCS order difference the apparatus may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for non-overlapped UL-DL PRBs, and a current MCS order; where a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table; where a beam failure criterion for a full-duplex beam failure includes at least one of a downlink radio link quality level, a self-interference level, or a cross-link interference level; where the beam failure criterion for a full-duplex beam failure includes at least one of a signal-to- interference-plus-noise ratio, a signal-to-interference ratio, or a block-error-rate; where the apparatus comprises a network entity.

[0183] For example, the processor 1304 may support wireless communication at the device 1302 in accordance with examples as disclosed herein. Processor 1304 may be configured as or otherwise support a means for transmitting, to a first UE, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; receiving, from the first UE, a second signaling that indicates that a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more second UEs; and transmitting, to the first UE, a third signaling indicating a configuration for handling a beam failure. [0184] Additionally or alternatively, the processor 1304 may be configured to or otherwise support: transmitting, to one or more network entities, a fourth signaling indicating a request for uplink beam failure handling; receiving, from one of the one or more network entities, a fifth signaling indicating whether the request is accepted or not accepted; where the fourth signaling indicates to at least one of the one or more network entities to decrease a downlink transmit power over an indicated time-frequency resources by an indicated level; where the fourth signaling indicates to at least one of the one or more network entities to mute a downlink transmission over an indicated time- frequency resources; where the fourth signaling indicates to at least one of the one or more network entities to switch an active downlink beam index to an indicated beam index from a candidate beam set coordinated between an apparatus implementing the method and the at least one of the one or more network entities; where the fifth signaling indicates at least one of an acknowledgment response message or a negative acknowledgment response message; where a negative acknowledgment response to the request is indicated by a lack of a fifth signaling from at least one of the one or more network entities indicating that the request is not accepted; receiving the second signaling as part of a beam failure recovery procedure; where the first signaling is a part of a radio resource control RadioLinkMonitoringConfig-information element; where the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-information element; where: the one or more RS resources for measuring downlink radio link quality level comprise at least one of SSB or channel state information-RS resources; and the one or more RS resources for measuring a self-interference level or a cross-link interference level comprise at least one of sounding reference or demodulation-RS resources, or a dedicated RS for self-interference and crosslink interference probing of a full-duplex transceiver; where the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets; where the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention- free random-access or a contention-based random-access procedure; where the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message; where the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels; where the third signaling includes a first uplink transmit power value dedicated for overlapped uplink-downlink physical resource blocks and a second uplink transmit power value dedicated for non-overlapped uplink-downlink physical resource blocks; where the third signaling includes an indication to increase or to decrease uplink transmit power over overlapped and nonoverlapped UL-DL PRBs by indicating a row index corresponding to a preconfigured uplink power control lookup table; where the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi-persistently scheduled overlapped uplink- downlink physical resource blocks, or mute transmission over semi-persistently scheduled non-overlapped uplink-downlink physical resource blocks; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates a new uplink transmit power for overlapped UL-DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a modulation coding scheme order, and a release time; where the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates a power difference and a MCS order difference an apparatus implementing the method may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for non-overlapped UL-DL PRBs, and a current MCS order; where a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table; where a beam failure criterion for a full-duplex beam failure includes at least one of a downlink radio link quality level, a selfinterference level, or a cross-link interference level; where the beam failure criterion for a full- duplex beam failure includes at least one of a signal-to-interference-plus-noise ratio, a signal-to- interference ratio, or a block-error-rate; where the method is implemented in a network entity.

[0185] The processor 1304 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 implementations, the processor 1304 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 1304. The processor 1304 may be configured to execute computer- readable instructions stored in a memory (e.g., the memory 1306) to cause the device 1302 to perform various functions of the present disclosure. [0186] The memory 1306 may include random access memory (RAM) and read-only memory (ROM). The memory 1306 may store computer- readable, computer-executable code including instructions that, when executed by the processor 1304 cause the device 1302 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 1304 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1306 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0187] The I/O controller 1310 may manage input and output signals for the device 1302. The I/O controller 1310 may also manage peripherals not integrated into the device 1302. In some implementations, the I/O controller 1310 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1310 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 1310 may be implemented as part of a processor, such as the processor 1304. In some implementations, a user may interact with the device 1302 via the I/O controller 1310 or via hardware components controlled by the I/O controller 1310.

[0188] In some implementations, the device 1302 may include a single antenna 1312. However, in some other implementations, the device 1302 may have more than one antenna 1312 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1308 may communicate bi-directionally, via the one or more antennas 1312, wired, or wireless links as described herein. For example, the transceiver 1308 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1308 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1312 for transmission, and to demodulate packets received from the one or more antennas 1312.

[0189] FIG. 14 illustrates a flowchart of a method 1400 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a device or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 104 as described with reference to FIGs. 1 through 13. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0190] At 1405, the method may include receiving, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more (RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric. The operations of 1405 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1405 may be performed by a device as described with reference to FIG. 1.

[0191] At 1410, the method may include transmitting, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, selfinterference, or cross-link interference from one or more UEs. The operations of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1410 may be performed by a device as described with reference to FIG. 1.

[0192] At 1415, the method may include receiving, from the network entity, a third signaling indicating a configuration for handling a beam failure. The operations of 1415 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1415 may be performed by a device as described with reference to FIG. 1.

[0193] FIG. 15 illustrates a flowchart of a method 1500 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a device or its components as described herein. For example, the operations of the method 1500 may be performed by a UE 104 as described with reference to FIGs. 1 through 13. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware. [0194] At 1505, the method may include triggering, in response to a beam failure criterion being met, a beam failure recovery procedure in accordance with the configuration for handling the beam failure. The operations of 1505 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1505 may be performed by a device as described with reference to FIG. 1.

[0195] At 1510, the method may include transmitting the second signaling as part of the beam failure recovery procedure. The operations of 1510 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1510 may be performed by a device as described with reference to FIG. 1.

[0196] FIG. 16 illustrates a flowchart of a method 1600 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a device or its components as described herein. For example, the operations of the method 1600 may be performed by a UE 104 as described with reference to FIGs. 1 through 13. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0197] At 1605, the method may include the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention-free random-access or a contention-based random-access procedure. The operations of 1605 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1605 may be performed by a device as described with reference to FIG. 1.

[0198] FIG. 17 illustrates a flowchart of a method 1700 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The operations of the method 1700 may be implemented by a device or its components as described herein. For example, the operations of the method 1700 may be performed by a UE 104 as described with reference to FIGs. 1 through 13. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0199] At 1705, the method may include the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message. The operations of 1705 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1705 may be performed by a device as described with reference to FIG. 1.

[0200] FIG. 18 illustrates a flowchart of a method 1800 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The operations of the method 1800 may be implemented by a device or its components as described herein. For example, the operations of the method 1800 may be performed by a network entity 102 as described with reference to FIGs. 1 through 13. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0201] At 1805, the method may include transmitting, to a first UE, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more RS resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric. The operations of 1805 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1805 may be performed by a device as described with reference to FIG. 1.

[0202] At 1810, the method may include receiving, from the first UE, a second signaling that indicates that a beam failure is due to at least one of degradation in the downlink radio link, selfinterference, or cross-link interference from one or more second UEs. The operations of 1810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1810 may be performed by a device as described with reference to FIG. 1.

[0203] At 1815, the method may include transmitting, to the first UE, a third signaling indicating a configuration for handling a beam failure. The operations of 1815 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1815 may be performed by a device as described with reference to FIG. 1.

[0204] FIG. 19 illustrates a flowchart of a method 1900 that supports beam failure recovery for FD communication in accordance with aspects of the present disclosure. The operations of the method 1900 may be implemented by a device or its components as described herein. For example, the operations of the method 1900 may be performed by a network entity 102 as described with reference to FIGs. 1 through 13. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0205] At 1905, the method may include transmitting, to one or more network entities, a fourth signaling indicating a request for uplink beam failure handling. The operations of 1905 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1905 may be performed by a device as described with reference to FIG. 1.

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

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

[0208] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0209] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0210] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0211] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such 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). Similarly, 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). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0212] The terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity, may refer to any portion of a network entity (e.g., a base station, a CU, a DU, a RU) of a RAN communicating with another device (e.g., directly or via one or more other network entities).

[0213] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0214] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more reference signal (RS) resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a crosslink interference quality metric; transmit, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more UEs; and receive, from the network entity, a third signaling indicating a configuration for handling a beam failure.

2. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: trigger, in response to a beam failure criterion being met, a beam failure recovery procedure in accordance with the configuration for handling the beam failure; and transmit the second signaling as part of the beam failure recovery procedure.

3. The UE of claim 1, wherein the first signaling is a part of a radio resource control RadioLinkMonitoringConfig-informationelement.

4. The UE of claim 1, wherein the first signaling is a part of a radio resource control BeamFailureRecoveryConfig-informationelement.

5. The UE of claim 1, wherein: the one or more RS resources for measuring downlink radio link quality level comprise at least one of synchronization signal block (SSB) or channel state information-RS resources; and the one or more RS resources for measuring a self-interference level or a cross-link interference level comprise at least one of sounding reference or demodulation-RS resources, or a dedicated RS for self-interference and cross-link interference probing of a full-duplex transceiver.

6. The UE of claim 1, wherein the first signaling indicates at least one of one or more of random-access channel preamble indices, one or more root sequence indices, or one or more preamble indices sets.

7. The UE of claim 1, wherein the second signaling indicates a main reason for the beam failure by an index of a selected preamble, by an index of a selected root sequence, or by an index of a selected preamble indices set via a contention- free random-access or a contention-based random-access procedure.

8. The UE of claim 1, wherein the second signaling indicates a main reason for the beam failure and a level of the main reason by indicating a row index corresponding to a preconfigured lookup table via an uplink control information message.

9. The UE of claim 8, wherein the lookup table is preconfigured with two or more rows and each row indicates a reason for the downlink beam failure accompanied by one of multiple levels.

10. The UE of claim 2, wherein the beam failure criterion for a full-duplex beam failure includes at least one of downlink radio link quality level, self-interference quality level, or crosslink interference quality level.

11. The UE of claim 2, wherein the beam failure criterion include at least one of a signal-to- interference-plus-noise ratio, a signal-to-interference ratio, or a block-error-rate (BLER).

12. A base station for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: transmit, to a first user equipment (UE), a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more reference signal (RS) resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; receive, from the first UE, a second signaling that indicates that a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more second UEs; and transmit, to the first UE, a third signaling indicating a configuration for handling a beam failure.

13. A method performed by a user equipment (UE), the method comprising: receiving, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more reference signal (RS) resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a cross-link interference quality metric; transmitting, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more UEs; and receiving, from the network entity, a third signaling indicating a configuration for handling a beam failure.

14. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a network entity, a first signaling indicating a configuration for radio link monitoring that includes at least one of one or more reference signal (RS) resources for measuring a downlink radio link quality metric, a self-interference quality metric, or a crosslink interference quality metric; transmit, to the network entity, a second signaling that indicates a beam failure is due to at least one of degradation in the downlink radio link, self-interference, or cross-link interference from one or more user equipments (UEs); and receive, from the network entity, a third signaling indicating a configuration for handling a beam failure.

15. The processor of claim 14, wherein the third signaling includes a first uplink transmit power value dedicated for overlapped uplink-downlink (UL-DL) physical resource blocks (PRBs) and a second uplink transmit power value dedicated for non-overlapped UL-DL PRBs.

16. The processor of claim 14, wherein the third signaling includes an indication to increase or to decrease an uplink transmit power over overlapped and non-overlapped uplink-downlink (UL- DL) physical resource blocks (PRBs) by indicating a row index corresponding to a preconfigured uplink power control lookup table.

17. The processor of claim 14, wherein the third signaling includes a row index corresponding to a preconfigured uplink power control lookup table as an indication to at least one of mute uplink transmission over semi-persistently scheduled overlapped uplink- downlink (UL-DL) physical resource blocks (PRBs), or mute uplink transmission over semi-persistently scheduled nonoverlapped UL-DL PRBs.

18. The processor of claim 16, wherein the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a new uplink transmit power for overlapped UL-DL PRBs, a new uplink transmit power for non-overlapped UL-DL PRBs, a modulation coding scheme (MCS) order, or a release time.

19. The processor of claim 16, wherein the preconfigured uplink power control lookup table is preconfigured with two or more rows and each row indicates one or more of a power difference and a modulation coding scheme (MCS) order difference the processor may use to update a current uplink transmit power for overlapped UL-DL PRBs, a current uplink transmit power for nonoverlapped UL-DL PRBs, or a current MCS order.

20. The processor of claim 16, wherein a mute indication is associated with a zero-power value in the preconfigured uplink power control lookup table.