Beam failure recovery via relay node

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send a beam failure recovery (BFR) message regarding a failed link, where the failed link is one of an indirect link with a network node via a relay node or a direct link with the network node, where the BFR message is sent on one of the indirect link or the direct link that is not the failed link. The UE may receive an updated beam configuration for the failed link on the selected beam indicated by the BFR message. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 380,476, entitled "BEAM FAILURE RECOVERY VIA RELAY NODE", filed on October 21, 2022, and U.S. Non - Provisional Patent Application No. 18 / 464,791, entitled "BEAM FAILURE RECOVERY VIA RELAY NODE", filed on September 11, 2023, and assigned to the assignee of this application. The disclosures of these prior applications are considered to be part of this patent application and are incorporated herein by reference. Field of the Disclosure

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatus for beam failure recovery (BFR) via a relay node. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access techniques include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single - carrier frequency division multiple access (SC - FDMA) systems, time - division synchronous code division multiple access (TD - SCDMA) systems, and Long Term Evolution (LTE). LTE / Advanced LTE is an enhanced collection of the Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device - to - device communication, such as via a local link (e.g., sidelink (SL), wireless local area network (WLAN) link, and / or wireless personal area network (WPAN) link, etc.).

[0006] The above multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global levels. New Radio (NR) (which may be referred to as 5G) is an enhanced collection of LTE mobile standards promulgated by 3GPP. NR is designed to better support mobile broadband Internet access in the following ways: improving spectral efficiency; reducing costs; improving services; leveraging new spectrums; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation. With the continuous increase in the demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies are still useful. SUMMARY OF THE INVENTION

[0007] Some aspects described herein relate to a method of wireless communication performed by a User Equipment (UE). The method may include transmitting a Beam Failure Recovery (BFR) message regarding a failed link, where the failed link is either an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is transmitted on a link other than the failed link among the indirect link or the direct link. The method may include receiving an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on a link other than the failed link among the indirect link or the direct link. The method may include transmitting an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to send a beam failure recovery (BFR) message regarding a failed link, where the failed link is one of an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on one of the indirect link or the direct link that is not the failed link. The one or more processors may be configured to receive an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include: a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a BFR message regarding a failed link, where the failed link is one of an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on one of the indirect link or the direct link that is not the failed link. The one or more processors may be configured to send an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to send a beam failure recovery (BFR) message regarding a failed link, where the failed link is one of an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on one of the indirect link or the direct link that is not the failed link. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive a BFR message regarding a failed link, where the failed link is one of an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on one of the indirect link or the direct link that is not the failed link. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a BFR message regarding a failed link, where the failed link is one of an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on one of the indirect link or the direct link that is not the failed link. The apparatus may include means for receiving an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a BFR message regarding a failed link, where the failed link is one of an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on one of the indirect link or the direct link that is not the failed link. The apparatus may include means for sending an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0015] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and illustrated in the drawings.

[0016] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both as to their organization and method of operation, as well as associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the drawings provided is for the purpose of illustration and description and not as a definition of the limits of the claims.

[0017] While aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and constitutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To enable a more detailed understanding of the above features of the present disclosure, a more specific description of what was briefly outlined above can be obtained by reference to aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings only illustrate certain typical aspects of the present disclosure and are therefore not considered to limit its scope, as the specification may admit other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example beamforming architecture supporting beamforming for millimeter wave (mmW) communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating examples of a channel state information reference signal (CSI-RS) beam management process according to the present disclosure.

[0024] Figure 6Is a diagram illustrating an example of beam failure detection and beam failure recovery (BFR) according to the present disclosure.

[0025] Figure 7 Is a diagram of an example according to the present disclosure associated with a BFR process via a relay node.

[0026] Figure 8 Is a diagram of an example according to the present disclosure associated with a BFR process via a relay node.

[0027] Figure 9 Is a diagram illustrating an example process, such as performed by a UE, according to the present disclosure.

[0028] Figure 10 Is a diagram illustrating an example process, such as performed by a network node, according to the present disclosure.

[0029] Figure 11 Is a diagram of an example apparatus for wireless communication according to the present disclosure.

[0030] Figure 12 Is a diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Description

[0031] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of the present disclosure is intended to cover such an apparatus or method practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0032] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0033] Although terms that are generally associated with 5G or New Radio (NR) radio access technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0034] Figure 1 FIG. is an example diagram illustrating a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, network nodes 110b, network nodes 110c, and network nodes 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, UEs 120b, UEs 120c, UEs 120d, and UEs 120e), and / or other entities. The network nodes 110 are network nodes that communicate with the UEs 120. As shown, the network nodes 110 may include one or more network nodes. For example, the network nodes 110 may be aggregated network nodes, which means that the aggregated network nodes are configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network nodes 110 may be disaggregated network nodes (sometimes referred to as disaggregated base stations), which means that the network nodes 110 are configured to utilize a protocol stack that is physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0035] In some examples, network node 110 is a network node that communicates with UE 120 via a radio access link, such as an RU, or includes a network node that communicates with UE 120 via a radio access link, such as an RU. In some examples, network node 110 is a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU, or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, network node 110 is a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU, or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission and reception point (TRP), a DU, an RU, a CU, a mobility element of the network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network node 110 may be interconnected with each other or with one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0036] In some examples, network node 110 may provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographical area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographical area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macrocell may be referred to as a macro network node. The network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femtocell may be referred to as a femto network node or a home network node. In Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographical area of a cell may move according to the location of a moving network node 110 (e.g., a mobile network node).

[0037] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more of its components. For example, in some aspects, the "base station" or "network node" may refer to a CU, a DU, an RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a single device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat at least a portion of the execution of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

[0038] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., network node 110 or UE 120) and transmit the data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 capable of relaying a transmission for other UEs 120. In Figure 1 the example shown, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node that relays communication may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0039] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmission power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmission power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmission power levels (e.g., 0.1 watt to 2 watts).

[0040] The network controller 130 may be coupled to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0041] UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. The UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, UE functionality of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0042] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. The MTC UE and / or eMTC UE may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premise equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0043] Generally, any number of wireless networks 100 may be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequency may be referred to as a carrier, a frequency channel, etc. Each frequency in a given geographical area may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network may be deployed.

[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., communicate with each other without using the network node 110 as an intermediate device). For example, the UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, the UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the network node 110.

[0045] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands falls within the EHF band.

[0047] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" etc. is used in this document, the term can generally represent frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" etc. is used in this document, the term can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band. It is envisioned that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein apply to those modified frequency ranges.

[0048] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may perform the following operations: send a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on the one of the indirect link or the direct link that is not the failed link; and receive an updated beam configuration for the failed link on a selected beam indicated by the BFR message. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0049] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may perform the following operations: receive a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on the one of the indirect link or the direct link that is not the failed link; and send an updated beam configuration for the failed link on a selected beam indicated by the BFR message. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1 is provided as an example. Other examples may differ from what is Figure 1 described.

[0051] Figure 2 FIG. 200 is a diagram illustrating Example 200 of communication between a network node 110 and a UE 120 in a wireless network 100 in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of Example 200 includes one or more radio frequency components, such as antennas 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0052] At network node 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 at least in part based on one or more channel quality indicators (CQIs) received from the UE 120. Network node 110 may process (e.g., encode and modulate) the data for the UE 120 at least in part based on the MCS selected for the UE 120 and may provide data symbols for the UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may process the corresponding output symbol stream (e.g., for OFDM) using the corresponding modulator component to obtain a stream of output samples. Each modem 232 may also process the stream of output samples (e.g., convert to analog, amplify, filter, and / or up-convert) using the corresponding modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal using the corresponding demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. The MIMO detector 256 may obtain the received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide the decoded data for the UE 120 to the data sink 260, and may provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, etc. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. The antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 one or more components in

[0056] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 4 to 12 )Aspects of any of the methods described herein.

[0057] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 12 )Aspects of any of the methods described herein.

[0058] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other component of may perform one or more techniques associated with beam failure recovery, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other component of may perform or direct, for example, Figure 9 procedure 900 of, Figure 10 procedure 1000 of, and / or the operation of other procedures as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication (e.g., code and / or program code). For example, when the one or more instructions are executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or after compilation, conversion, and / or interpretation), the one or more processors, UE 120, and / or network node 110 may be caused to perform or direct, for example, Figure 9 procedure 900 of, Figure 10 procedure 1000 of, and / or the operation of other procedures described herein. In some examples, executing the instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, and so on.

[0059] In some aspects, a UE (e.g., UE 120) includes: means for sending a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on one of the indirect link or the direct link that is not the failed link; and / or means for receiving an updated beam configuration for the failed link on a selected beam indicated by the BFR message. The means for a UE to perform the operations described herein may include, for example, communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, memory 282, or Figure 4 one or more of the components of.

[0060] In some aspects, a network node (e.g., network node 110) includes: components for receiving a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on a link that is not the failed link among the indirect link or the direct link; and / or components for transmitting an updated beam configuration for the failed link on a selected beam indicated by the BFR message. The components for the network node to perform the operations described herein may include a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, a scheduler 246, or Figure 4 one or more of one or more components of

[0061] Although Figure 2 the boxes in are illustrated as different components, the functions described above for these boxes may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described for a transmit processor 264, a receive processor 258, and / or a TX MIMO processor 266 may be performed by or under the control of a controller / processor 280.

[0062] As indicated above, Figure 2 is provided as an example. Other examples may be different from what is described regarding Figure 2 is described.

[0063] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in various ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) performing base station functionality may be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a disaggregated base station. A "network entity" or "network node" may refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0064] A centralized base station (e.g., a centralized network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A split base station (e.g., a split network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), etc.

[0065] Base station types of operations or network designs may consider the aggregation characteristics of base station functionality. For example, a split base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A split base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can achieve flexibility in network design. Each unit of a split base station may be configured for wired or wireless communication with at least one other unit of the split base station.

[0066] Figure 3 FIG. is an illustration of an example split base station architecture 300 in accordance with the present disclosure. The split base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more split control units (such as a near RT RIC 325 via an E2 link, or a non-RTRIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as through an F1 interface). Each DU in the DUs 330 may communicate with one or more RUs 340 via a respective fronthaul link. Each RU in the RUs 340 may communicate with one or more UEs 120 via a respective radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0067] Each unit in the unit (including CU 310, DU 330, RU 340) and the near RT RIC 325, non-RT RIC 315, and SMO framework 305 may include one or more interfaces or be coupled to one or more interfaces, and the one or more interfaces are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit in the unit or the associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more units in other units via the transmission medium. In some examples, each unit in the unit may include a wired interface and a wireless interface. The wired interface is configured to receive signals or transmit signals to one or more units in other units via a wired transmission medium. The wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), and the wireless interface is configured to receive signals or transmit signals to one or more units in other units via a wireless transmission medium or perform both.

[0068] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some embodiments, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0069] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host, at least in part, one or more of the radio link control (RLC) layer, the MAC layer, and one or more high physical (PHY) layers according to a functional split such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, which may be implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0070] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based on a functional split (e.g., a functional split defined by 3GPP), such as a lower layer functional split. In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some embodiments, the real-time and non-real-time aspects of the control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0071] The SMO framework 305 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can directly communicate with each RU in one or more RUs 340 via the corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0072] The non-RT RIC 315 can be configured to include a logical function that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and update, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (such as via the A1 interface). The near-RT RIC 325 can be configured to include a logical function that can enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface (such as via the E2 interface) connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near-RT RIC 325.

[0073] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or at the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0074] As indicated above, Figure 3 is provided as an example. Other examples may be different from what is Figure 3 described with respect to

[0075] Figure 4 FIG. is an illustration of an example beamforming architecture 400 that supports beamforming for millimeter wave (mmW) communications in accordance with aspects of the present disclosure. In some aspects, the architecture 400 may implement aspects of the wireless network 100. In some aspects, the architecture 400 may be implemented in a transmitting device (e.g., a first wireless communication device, a UE, or a network node) and / or a receiving device (e.g., a second wireless communication device, a UE, or a network node), as described herein.

[0076] Broadly, Figure 4 FIG. is an illustration of example hardware components of a wireless communication device in accordance with certain aspects of the present disclosure. The illustrated components may include those components that can be used for antenna element selection and / or for beamforming to transmit wireless signals. There are numerous architectures for antenna element selection and for implementing phase shifts, and only one example is illustrated herein. The architecture 400 includes a modem (modulator / demodulator) 402, a digital-to-analog converter (DAC) 404, a first mixer 406, a second mixer 408, and a splitter 410. The architecture 400 also includes a plurality of first amplifiers 412, a plurality of phase shifters 414, a plurality of second amplifiers 416, and an antenna array 418 that includes a plurality of antenna elements 420. In some examples, the modem 402 may be one or more of the modems 232 or 254 described in conjunction with Figure 2 the above.

[0077] Shows the transmission lines or other waveguides, wires, and / or traces connecting various components to illustrate how the signals to be transmitted travel between the components. Reference numerals 422, 424, 426, and 428 indicate regions in architecture 400 where different types of signal travel or are processed. Specifically, reference numeral 422 indicates the region where digital baseband signals travel or are processed, reference numeral 424 indicates the region where analog baseband signals travel or are processed, reference numeral 426 indicates the region where analog intermediate frequency (IF) signals travel or are processed, and reference numeral 428 indicates the region where analog RF signals travel or are processed. The architecture also includes local oscillator A 430, local oscillator B 432, and controller / processor 434. In some aspects, controller / processor 434 corresponds to the controller / processor 240 of network node 110 described above in connection with Figure 2 and / or the controller / processor 280 of UE 120 described above in connection with Figure 2 the UE 120.

[0078] Each antenna element 420 may include one or more sub-elements for radiating or receiving RF signals. For example, a single antenna element 420 may include a first sub-element that is cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna element 420 may include a patch antenna, a dipole antenna, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements 420 may be such that signals with a desired wavelength transmitted individually by antenna elements 420 can interact or interfere with each other (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, a half wavelength, or other fractional wavelengths of the spacing between adjacent antenna elements 420 to allow interaction or interference of signals transmitted by individual antenna elements 420 within that desired range.

[0079] The modem 402 processes and generates a digital baseband signal and may also control the operation of the DAC 404, the first mixer 406, and the second mixer 408, the splitter 410, the first amplifier 412, the phase shifter 414, and / or the second amplifier 416 to transmit a signal via one or more or all of the antenna elements 420. The modem 402 may process signals and control operations according to a communication standard, such as the wireless standards discussed herein. The DAC 404 may convert the digital baseband signal received from (and to be transmitted by) the modem 402 into an analog baseband signal. The first mixer 406 uses the local oscillator A 430 to up-convert the analog baseband signal to an analog IF signal within the IF. For example, the first mixer 406 may mix the signal with the oscillating signal generated by the local oscillator A 430 to "shift" the baseband analog signal to the IF. In some cases, some processing or filtering (not shown) may occur at the IF. The second mixer 408 uses the local oscillator B 432 to up-convert the analog IF signal to an analog RF signal. Similar to the first mixer, the second mixer 408 may mix the signal with the oscillating signal generated by the local oscillator B 432 to "shift" the IF analog signal to the RF or to the frequency of the transmitted or received signal. The modem 402 and / or the controller / processor 434 may adjust the frequencies of the local oscillator A 430 and / or the local oscillator B 432 such that the desired IF and / or RF frequencies are generated and used to facilitate signal processing and transmission within the desired bandwidth.

[0080] In the illustrated architecture 400, the signal up-converted by the second mixer 408 is separated or replicated into multiple signals by the splitter 410. The splitter 410 in the architecture 400 separates the RF signal into multiple identical or nearly identical RF signals. In other examples, the separation may occur for any type of signal, including baseband signals, baseband analog or IF analog signals. Each of these signals may correspond to an antenna element 420, and the signal travels through the amplifiers 412, 416, the phase shifter 414, and / or other elements corresponding to the respective antenna element 420 and is processed by these components to be provided to and transmitted by the corresponding antenna element 420 of the antenna array 418. In one example, the splitter 410 may be an active splitter connected to a power source and providing some gain such that the RF signal leaving the splitter 410 is at a power level equal to or greater than the signal entering the splitter 410. In another example, the splitter 410 is a passive splitter not connected to a power source, and the RF signal leaving the splitter 410 may be at a power level lower than the RF signal entering the splitter 410.

[0081] After being separated by the separator 410, the resulting RF signal may enter an amplifier, such as the first amplifier 412, or the phase shifter 414 corresponding to the antenna element 420. The first amplifier 412 and the second amplifier 416 are illustrated in dashed lines because in some aspects, one or both of them may not be necessary. In some aspects, both the first amplifier 412 and the second amplifier 416 are present. In some aspects, neither the first amplifier 412 nor the second amplifier 416 is present. In some aspects, one of the two amplifiers 412, 416 is present, but the other is not. By way of example, if the separator 410 is an active separator, the first amplifier 412 may not be used. By another example, if the phase shifter 414 is an active phase shifter that can provide gain, the second amplifier 416 may not be used.

[0082] The amplifiers 412, 416 may provide a desired level of positive or negative gain. Positive gain (positive dB) can be used to increase the amplitude of the signal radiated by a particular antenna element 420. Negative gain (negative dB) can be used to reduce the amplitude of the signal by a particular antenna element and / or suppress the radiation of the signal. Each of the amplifiers 412, 416 can be independently controlled (e.g., by the modem 402 or the controller / processor 434) to provide independent control of the gain for each antenna element 420. For example, the modem 402 and / or the controller / processor 434 may have at least one control line connected to each of the separator 410, the first amplifier 412, the phase shifter 414, and / or the second amplifier 416, and the at least one control line can be used to configure the gain to provide a desired amount of gain for each component and thus for each antenna element 420.

[0083] The phase shifter 414 may provide a configurable phase shift or phase offset to the corresponding RF signal to be transmitted. The phase shifter 414 can be a passive phase shifter that is not directly connected to a power source. A passive phase shifter may introduce some insertion loss. The second amplifier 416 can enhance the signal to compensate for the insertion loss. The phase shifter 414 can be an active phase shifter connected to a power source, such that the active phase shifter provides a certain amount of gain or prevents insertion loss. The settings of each phase shifter in the phase shifter 414 are independent, meaning that each phase shifter can be independently set to provide a desired amount of phase shift, or the same amount of phase shift, or some other configuration. The modem 402 and / or the controller / processor 434 may have at least one control line connected to each phase shifter in the phase shifter 414, and the at least one control line can be used to configure the phase shifter 414 to provide a desired amount of phase shift or phase offset between the antenna elements 420.

[0084] In the illustrated architecture 400, the RF signals received by the antenna elements 420 are provided to one or more first amplifiers 456 to enhance the signal strength. The first amplifiers 456 can be connected to the same antenna array 418 (e.g., for time division duplex (TDD) operation). The first amplifiers 456 can be connected to different antenna arrays 418. The enhanced RF signals are input into one or more phase shifters 454 to provide configurable phase shifts or phase offsets for the respective received RF signals to enable reception via one or more Rx beams. The phase shifters 454 can be active phase shifters or passive phase shifters. The settings of the phase shifters 454 are independent, meaning that each phase shifter can be independently set to provide a desired amount of phase shift or the same amount of phase shift or some other configuration. The modem 402 and / or the controller / processor 434 can have at least one control line connected to each of the phase shifters 454, and the at least one control line can be used to configure the phase shifters 454 to provide a desired amount of phase shift or phase offset between the antenna elements 420 to enable reception via one or more Rx beams.

[0085] The output of the phase shifters 454 can be input into one or more second amplifiers 452 for signal amplification of the phase-shifted received RF signals. The second amplifiers 452 can be individually configured to provide a configured amount of gain. The second amplifiers 452 can be individually configured to provide a certain amount of gain to ensure that the signals input into the combiner 450 have the same amplitude. The amplifiers 452 and / or 456 are illustrated in dashed lines because in some aspects, they may not be required. In some aspects, both the amplifier 452 and the amplifier 456 are present. In another aspect, both the amplifier 452 and the amplifier 456 are absent. In other aspects, one of the amplifiers 452, 456 is present, but the other is absent.

[0086] In the illustrated architecture 400, the signals output by the phase shifters 454 (via the amplifiers 452 when present) are combined in the combiner 450. The combiner 450 in the architecture 400 combines the RF signals into one signal. The combiner 450 can be a passive combiner (e.g., not connected to a power source), which may result in some insertion loss. The combiner 450 can be an active combiner (e.g., connected to a power source), which may result in some signal gain. When the combiner 450 is an active combiner, it can provide different (e.g., configurable) amounts of gain for each input signal such that the input signals have the same amplitude when combined. When the combiner 450 is an active combiner, the combiner 450 may not require the second amplifier 452 because the active combiner can provide signal amplification.

[0087] The output of combiner 450 is input into mixers 448 and 446. Mixers 448 and 446 typically use inputs from local oscillators 472 and 470 respectively to down-convert the received RF signals to produce intermediate or baseband signals carrying the encoded and modulated information. The outputs of mixers 448 and 446 are input into an analog-to-digital converter (ADC) 444 for conversion to digital signals. The digital signals output from ADC 444 are input into modem 402 for baseband processing such as decoding, de-interleaving, or similar operations.

[0088] Architecture 400 is given by way of example only to illustrate an architecture for transmitting and / or receiving signals. In some cases, architecture 400 and / or each part of architecture 400 may be repeated multiple times within the architecture to accommodate or provide any number of RF chains, antenna elements, and / or antenna panels. Additionally, numerous alternative architectures are possible and contemplated. For example, although only a single antenna array 418 is shown, two, three, or more antenna arrays may be included, each having one or more of its own corresponding amplifiers, phase shifters, splitters, mixers, DACs, ADCs, and / or modems. For example, a single UE may include two, four, or more antenna arrays for transmitting or receiving signals at different physical locations or in different directions on the UE.

[0089] Furthermore, mixers, splitters, amplifiers, phase shifters, and other components may be located in different signal type regions (e.g., represented by different reference numerals among reference numerals 422, 424, 426, 428) in different implemented architectures. For example, in different examples, separating the signal to be transmitted into multiple signals may occur at analog RF, analog IF, analog baseband, or digital baseband frequencies. Similarly, amplification and / or phase shifting may also occur at different frequencies. For example, in some aspects, one or more of splitter 410, amplifiers 412, 416, or phase shifter 414 may be located between DAC 404 and first mixer 406 or between first mixer 406 and second mixer 408. In one example, the functions of one or more components may be combined into one component. For example, phase shifter 414 may perform amplification to include or replace first amplifier 412 and / or second amplifier 416. By another example, phase shifting may be implemented by second mixer 408 to eliminate the need for a separate phase shifter 414. This technique is sometimes referred to as local oscillator (LO) phase shifting. In some aspects of this configuration, there may be multiple IF-to-RF mixers (e.g., for each antenna element chain) within second mixer 408, and local oscillator B 432 may supply different local oscillator signals (with different phase offsets) to each IF-to-RF mixer.

[0090] The modem 402 and / or the controller / processor 434 may control one or more of the other components 404 to 472 to select one or more antenna elements 420 and / or to form a beam for transmitting one or more signals. For example, the antenna elements 420 may be independently selected or deselected for transmitting a signal (or signals) by controlling the amplitude of one or more corresponding amplifiers, such as the first amplifier 412 and / or the second amplifier 416. Beamforming includes generating a beam using multiple signals on different antenna elements, where one or more or all of the multiple signals are shifted in phase relative to each other. The formed beam may carry a physical or higher layer reference signal or information. Since each of the multiple signals is radiated from a corresponding antenna element 420, the radiated signals interact, interfere (constructively and destructively), and amplify each other to form the resulting beam. The shape (such as amplitude, width, and / or the presence of sidelobes) and direction (such as the angle of the beam relative to the surface of the antenna array 418) may be dynamically controlled by modifying the phase shift or phase offset applied by the phase shifter 414 and the amplitudes applied by the amplifiers 412, 416 of the multiple signals relative to each other. The controller / processor 434 may be partially or fully located within one or more of the other components of the architecture 400. For example, in some aspects, the controller / processor 434 may be located within the modem 402.

[0091] As indicated above, Figure 4 is provided as an example. Other examples may be different from what Figure 4 is described.

[0092] Figure 5 FIGS. 500, 510, and 520 are diagrams illustrating examples of CSI-RS beam management procedures in accordance with the present disclosure. As Figure 5 shown, examples 500, 510, and 520 include a UE 120 communicating with a network node 110 in a wireless network (e.g., wireless network 100). However, Figure 5 the devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between a UE 120 and a network node 110 or a TRP, between a mobile terminal node and a control node, between an IAB sub-node and an IAB parent node, and / or between a scheduled node and a scheduling node). In some aspects, the UE 120 and the network node 110 may be in a connected state (e.g., RRC connected state).

[0093] As Figure 5As shown, Example 500 may include a network node 110 (e.g., one or more network node devices such as RU, DU, and / or CU, etc.) communicating with a UE 120 to perform beam management using CSI-RS. Example 500 depicts a first beam management process (e.g., P1 CSI-RS beam management). The first beam management process may be referred to as a beam selection process, an initial beam acquisition process, a beam scanning process, a cell search process, and / or a beam search process. As Figure 5 As shown in Example 500, the CSI-RS may be configured to be sent from the network node 110 to the UE 120. The CSI-RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using Medium Access Control (MAC) Control Element (MAC-CE) signaling), and / or aperiodic (e.g., using Downlink Control Information (DCI)).

[0094] The first beam management process may include the network node 110 performing beam scanning on multiple transmit (Tx) beams. The network node 110 may use each transmit beam for beam management to send the CSI-RS. To enable the UE 120 to perform receive (Rx) beam scanning, the network node may send each CSI-RS multiple times (e.g., with repetitions) within the same RS resource set using the transmit beam, such that the UE 120 can sweep through receive beams in multiple transmit instances. For example, in a case where the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be sent M times on each of the N transmit beams, such that the UE 120 can receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam scanning of the receive beams of the UE 120. Thus, the first beam management process may enable the UE 120 to measure the CSI-RS on different transmit beams using different receive beams to support the selection of a transmit beam / UE 120 receive beam beam pair. The UE 120 may report the measurements to the network node 110 so that the network node 110 can select one or more beam pairs for communication between the network node 110 and the UE 120. Although Example 500 has been described in conjunction with CSI-RS, the first beam management process may also use Synchronization Signal Block (SSB) to perform beam management in a similar manner as described above.

[0095] As Figure 5As shown, Example 510 may include a network node 110 and a UE 120 communicating to perform beam management using CSI-RS. Example 510 depicts a second beam management process (e.g., P2 CSI-RS beam management). The second beam management process may be referred to as a beam refinement process, a network node beam refinement process, a TRP beam refinement process, and / or a transmit beam refinement process. As Figure 5 shown in Example 510, the CSI-RS may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RS may be configured to be aperiodic (e.g., using DCI). The second beam management process may include the network node 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (e.g., determined at least in part based on measurements reported by the UE 120 in connection with the first beam management process). The network node 110 may transmit the CSI-RS using each of the one or more transmit beams used for beam management. The UE 120 may measure each CSI-RS using a single (e.g., the same) receive beam (e.g., determined at least in part based on measurements performed in connection with the first beam management process). The second beam management process may enable the network node 110 to select an optimal transmit beam at least in part based on measurements of the CSI-RS reported by the UE 120 (e.g., measured by the UE 120 using a single receive beam).

[0096] As Figure 5 shown, Example 520 depicts a third beam management process (e.g., P3 CSI-RS beam management). The third beam management process may be referred to as a beam refinement process, a UE beam refinement process, and / or a receive beam refinement process. As Figure 5As shown in Example 520, one or more CSI-RSs may be configured to be sent from network node 110 to UE 120. The CSI-RS may be configured to be aperiodic (e.g., using DCI). The third beam management process may include network node 110 sending one or more CSI-RSs using a single transmit beam (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management process and / or the second beam management process). To enable UE 120 to perform receive beam scanning, the network node may send (e.g., with repetition) the CSI-RS multiple times within the same RS resource set using the transmit beam, such that UE 120 may sweep over one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first beam management process and / or the second beam management process). The third beam management process may enable network node 110 and / or UE 120 to select an optimal receive beam at least in part based on the reported measurements received from UE 120 (e.g., the reported measurements of the CSI-RS for the transmit beam using the one or more receive beams).

[0097] As indicated above, Figure 5 is provided as an example of a beam management process. Other examples of beam management processes may differ from what is described with respect to Figure 5 For example, UE 120 and network node 110 may perform the third beam management process before performing the second beam management process, and / or UE 120 and network node 110 may perform a similar beam management process to select a UE transmit beam.

[0098] Figure 6 FIG. 600 is a diagram illustrating an example 600 of beam failure detection and beam failure recovery in accordance with the present disclosure. The beam failure detection (BFD) process is shown by reference numerals 612 to 620, and the beam failure recovery (BFR) process is shown by reference numerals 622 to 634.

[0099] Example 600 includes operations performed by a network node (e.g., network node 110) and a UE (e.g., UE 120). The operations performed by the network node are shown by reference numeral 602 at the top of Figure 6 and the operations performed by the UE are shown by reference numeral 604 at the bottom of Figure 6 The actions of the UE performed by the PHY layer of the UE are shown in the row indicated by reference numeral 606, and the actions of the UE performed by higher layers (e.g., MAC, RLC, PDCP, RRC, non-access stratum (NAS), Internet protocol (IP), etc.) are shown in the row indicated by reference numeral 608.

[0100] As shown by reference numeral 610, a network node may transmit beam set q0. Beam set q0 may include one or more beams each associated with a corresponding reference signal. Thus, the set of reference signals for beam set q0 may be referred to as a set of BFD reference signals (BFD-RS). The reference signals may include SSB, channel state information reference signals (CSI-RS), etc.

[0101] As shown by reference numeral 612, a UE may perform layer 1 (L1) measurements on the reference signals of beam set q0. For example, the UE may determine measurements for each reference signal of beam set q0. The measurements may include RSRP, RSRQ, signal to interference plus noise ratio (SINR), etc. As further shown in the figure, the UE (e.g., PHY layer) may determine that the L1 measurement (e.g., radio link quality) does not meet a first threshold called Qout. As shown in the figure, the UE (e.g., PHY layer) may provide a Out-of-Service (OOS) indication to a higher layer of the UE.

[0102] As shown by reference numeral 614, the UE (e.g., higher layer) may start a BFD timer at least in part based on the beam not meeting Qout and may increment a Beam Failure Indication (BFI) count. In the case where the BFI count meets a threshold (shown as a maximum count in conjunction with reference numeral 618) before the BFD timer expires, the UE may determine a beam failure. In the case where the BFD timer expires before the BFI count meets the threshold, the UE may reset the BFI count and thus does not determine a beam failure.

[0103] As shown by reference numeral 616, the UE (e.g., PHY layer) may perform a second L1 measurement on the reference signals of beam set q0. As further shown in the figure, the UE may provide an OOS indication to a higher layer of the UE indicating that the second L1 measurement does not meet Qout. In the case where the second L1 measurement has met Qout, the BFD timer may expire, and UE 120 may not identify a beam failure.

[0104] As shown by reference numeral 618, the UE may reset the BFD timer and may increment the BFI count at least in part based on the second L1 measurement not meeting the threshold. As further shown in the figure, the BFI count now meets the maximum count threshold. Thus, as shown by reference numeral 620, the UE determines that a beam failure has been detected.

[0105] As shown by reference numeral 622, a UE (e.g., a higher layer) may request to measure reference signals on beam set q1 to identify one or more beams in beam set q1 that meet a second threshold (e.g., Qin, which may be referred to as a BFR threshold). For example, beam set q1 may be a set of candidate beams for a BFR process or a new beam. Thus, the set of reference signals for beam set q1 may be referred to as a set of new beam identification reference signals (NBI-RS).

[0106] As shown by reference numeral 624, a UE (e.g., a PHY layer) may provide (e.g., in accordance with a request from a higher layer) measurement information of L1 measurements of reference signals that identify beam set q1. In example 600, the measurement information indicates that a particular reference signal associated with a particular beam meets Qin. For example, the UE may provide a reference signal index and an L1 measurement (e.g., RSRP) for each reference signal in the reference signals associated with L1 measurements that meet the threshold Qin. In Figure 6 which, a particular beam is illustrated by diagonal hatching. In the case where the measurement information indicates that a particular reference signal associated with a particular beam meets Qin, the UE may select the particular beam as the selected beam and may attempt to access the selected beam or a cell associated with the selected beam. For example, as shown by reference numeral 626, a UE (e.g., a higher layer) may trigger (e.g., initiate) a random access channel (RACH) process to access the selected beam, and as shown by reference numeral 628, a UE (e.g., a PHY layer) may perform the RACH process. For example, the UE may provide a RACH message 1 (e.g., the first message of the RACH process) to a network node to access the selected beam. Some of the techniques described herein provide signaling of the selected beam via a non-RACH component (such as a BFR MAC-CE), which may be sent via an indirect link with a relay node for relaying to a network node, or sent via a direct link with a network node.

[0107] In one example, the UE may use a random access resource (e.g., a random access preamble index) associated with a specific reference signal (e.g., a specific reference signal that satisfies Qin) to initiate a random access procedure, starting with contention-free random access (CFRA). In the case where the RACH procedure (e.g., CFRA) is successful, the network node 110 may provide a physical downlink control channel (PDCCH) on the selected beam, as shown by reference numeral 630a. In some examples, this response may be a response to a RACH message 1 (such as a RACH message 2, a random access response (RAR), etc.). As further shown in the figure, the cyclic redundancy check (CRC) of the DCI of the PDCCH may be scrambled using a radio network temporary identifier (RNTI) (e.g., a cell RNTI (C-RNTI), an MCS cell RNTI (MCS-C-RNTI), or another type of RNTI).

[0108] In the case where the UE receives the PDCCH within the CFRA response window, the BFR is successful. As shown by reference numeral 632a, the UE may stop the BFR timer at least in part based on the success of the BFR. In the case where the CFRA is not successful in the CFRA response window, the UE may perform contention-based random access (CBRA). The UE may use the same selected beam or a different selected beam used for performing the CFRA to perform the CBRA. In the case where the RACH procedure (e.g., CBRA) is successful, the network node 110 may provide the PDCCH on the selected beam in a similar manner as described above, as shown by reference numeral 630b. In the case where the UE receives the PDCCH within the CBRA response window, the BFR is successful. As shown by reference numeral 632b, the UE may stop the BFR timer at least in part based on the success of the BFR.

[0109] In the case where the RACH procedure is not successful (e.g., when the CFRA response window and / or the CBRA response window expires), the UE 120 may determine a radio link failure (RLF) after the BFR timer expires, as shown by reference numeral 634. In this case, the UE 120 may enter the idle mode, may report the RLF, may search for a new cell, etc.

[0110] As indicated above, Figure 6 is provided as an example. Other examples may be different from what is described with respect to Figure 6 what is described.

[0111] Some BFD procedures and BFR procedures, especially those that mainly rely on RACH communication, may cause the UE to consume a large amount of power and resources, increase latency, and delay or interrupt communication. For example, BFD procedures and BFR procedures that rely on RACH messages (e.g., messages on a single signaling path) must wait for the next RACH opportunity before the RACH message can be transmitted.

[0112] Some of the techniques described herein provide the UE with the transmission of BFR messages regarding a failed link, which is associated with a direct link to a network node and an indirect link via a relay node and the network node. In some aspects, the UE may send a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to the network node or a direct link to the network node. The BFR message may be sent on the remaining links of the indirect link and the direct link other than the failed link. The UE may receive an updated beam configuration for the failed link on a selected beam indicated by the BFR message. In this way, the remote UE does not mainly rely on RACH messages for BFD procedures and BFR procedures, resulting in reduced power consumption. In addition, the UE does not need to wait for the next RACH opportunity of the network node to start establishing a new beam configuration, thus reducing the amount of time to establish a new beam configuration. In addition, these techniques are applicable to the case where the failed link is an indirect link and the case where the failed link is a direct link.

[0113] In one aspect, a method of wireless communication performed by a network node includes: receiving a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a remote UE or a direct link to the remote UE, and the BFR message is received on the remaining links of the indirect link and the direct link other than the failed link; and sending an updated beam configuration for the failed link on a selected beam indicated by the BFR message. In this aspect, the network node learns about the failed link faster than in the case where the remote UE would wait for the next RACH opportunity. Thus, the network node can establish a new beam configuration with the remote UE more quickly.

[0114] Due to, for example, the time delay between beam measurements, the multi-path BFR process may result in ambiguity regarding the selected beam. That is, the BFR message on the direct link may identify one selected beam, while the BFR message on the indirect link may identify another selected beam. In particular, depending on the configuration of the BFR process and the timer thresholds in some aspects of the BFR process, the network node may receive multiple BFR messages (e.g., multiple BFR MAC-CEs, BFR MAC-CEs, and RACH messages) indicating different selected beams. For example, during BFD, the UE may measure candidate beams and may use BFR MAC-CE via the relay link to select and indicate b1 as the best beam. After a delay of x ms, the next RACH opportunity may arrive. The UE may measure the candidate beams again and may select and indicate b2 as the best beam via the RACH on beam b2. This ambiguity may result in a delay before an updated beam configuration can be established. For example, due to the uncontrollable value of the delay x and the different delays on the direct path and the relay path, it may be difficult for the network node to tell which beam is the latest best candidate beam (e.g., the selected beam) for the UE.

[0115] Some of the techniques described herein use techniques such as selecting a beam based on the latest BFR message sent, transmitting on multiple beams until the ambiguity is resolved, or having the remote UE and the relay node send BFR messages identifying the same selected beam to provide such resolution of ambiguity. Using one or more of these techniques, the network node and the remote UE can resolve or avoid the ambiguity caused by the multi-path BFR process more quickly.

[0116] Figure 7 FIG. 700 is a diagram of an example 700 associated with the BFR process via relay node 705 in accordance with the present disclosure. As Figure 7As shown, a remote UE (e.g., UE 120) can communicate with a network node (e.g., network node 110) via a direct link (e.g., a radio access link associated with the Uu interface, etc.). The remote UE can communicate with the network node via an indirect link through a relay node 705 (e.g., a different network node 110, a different UE 120, a repeater, a relay). The indirect link can include a link between the remote UE and the relay node 705 (e.g., a sidelink, a local link, etc., which may or may not utilize beamforming) and / or a link between the relay node 705 and the network node (e.g., a Uu link). In some aspects, the link between the remote UE and the relay node 705 and the link between the relay node 705 and the network node can be collectively referred to as a relay link. In some aspects, the remote UE can have a direct link to a first RU of the network node, and the relay node 705 can have a direct link to a second RU of the network node. In some aspects, the remote UE, the network node, and the relay node 705 can be part of a wireless network (e.g., wireless network 100). The remote UE, the network node, and the relay node 705 can have established a wireless connection before Figure 7 the operations shown. Example 700 assumes a failure on the direct link (e.g., the direct link is a failed link). As used herein, a "failed link" includes a link on which the remote UE has detected a beam failure. The failed link can be a direct link (in the case where the beam between the remote UE and the network node has failed) or an indirect link (in the case where the beam between the remote UE and the relay node has failed).

[0117] As shown by reference numeral 710, the remote UE can send a BFR message (also referred to as a first BFR message) on the direct link, and the network node can receive the BFR message on the direct link. The BFR message can include a BFR message sent on the RACH or a BFR message sent via a MAC-CE (e.g., BFR MAC-CE). The BFR message can be created after the remote UE detects a beam failure on the direct link. The beam failure can be detected via a BFD process (such as the BFD process shown at reference numerals 612 to 620 and discussed above with reference to Figure 6 ). The result of the BFD process can include the remote UE determining that a beam failure has been detected. Additionally, the result of the BFD process can include the measurement of beam set q1 discussed above with reference to reference numeral 622 and shown in Figure 6 and the measurement of the beam set q2 discussed above with reference to reference numeral 624 and shown in Figure 6Selection of a selected beam as shown. In one aspect, the BFR message may identify the first beam as the selected beam. In one aspect, the first BFR message may include a first timestamp. In one aspect, the first timestamp may indicate the time when the first BFR message is generated. In one aspect, the first timestamp may indicate the time when the first BFR message is sent. In one aspect, the first timestamp may indicate the time when beam measurement occurs.

[0118] As shown by reference numeral 715, the remote UE may send a second BFR message on the indirect link, and the relay node may receive the second BFR message on the indirect link. The second BFR message may include a BFR message sent on the RACH or a BFR message sent via a MAC-CE (e.g., BFR MAC-CE). In one aspect, at reference numeral 710, the second BFR message may be the same as the first BFR message sent on the direct link (e.g., may have the same content). For example, the second BFR message sent on the indirect link may identify the first beam as the selected beam. In this case, even if the first BFR message is sent via the RACH and the second BFR message is sent via a MAC-CE (or vice versa), the first BFR message and the second BFR message may be considered "the same". On the other hand, the second BFR message may be different from the first BFR message sent on the direct link at reference numeral 710. For example, the second BFR message may identify the second beam as the selected beam. The remote UE may send the second BFR message to the relay node via the indirect link (such as via the sidelink PC5 interface). In one aspect, the second BFR message may include a second timestamp. In one aspect, the second timestamp may indicate the time when the second BFR message is generated, the time when the second BFR message is sent, or the time when beam measurement occurs. In one aspect, the remote UE may send the first BFR message on both the indirect link and the direct link (e.g., in each FR message until the BFR process is completed) to avoid ambiguity, which will be discussed in more detail below with reference to reference numeral 725.

[0119] As shown by reference numeral 720, the relay node 705 may send the second BFR message (including the second timestamp if the second timestamp is included in the second BFR message) via the direct link (through the air interface) or the indirect link (via the sidelink interface) between the relay node and the network node, and the network node may receive the second BFR message. The relay node 705 may use any suitable relay technology to relay the communication between the remote UE and the network node, such as layer 2 UE-to-network relay (which is completed using the layer 2 identifier of the remote UE), layer 3 UE-to-network relay (which is completed using the layer 3 (e.g., IP) identifier of the remote UE), or another form of relay.

[0120] As indicated by reference numeral 725, the network node may resolve one or more beam ambiguities in the first BFR message and the second BFR message (if there are beam ambiguities). Example beam ambiguities may occur in cases where the first BFR message identifies a first beam as the selected beam and the second BFR message identifies a second beam as the selected beam. In one aspect, the network node may select as the selected beam a beam associated with a later timestamp (e.g., at least in part based on comparing the first timestamp with the second timestamp). In another aspect, the network node may resolve the beam ambiguity by transmitting on both the first beam and the second beam until the BFR process is complete. In another aspect, if the BFR messages transmitted on the direct link and the indirect link are the same (e.g., the first BFR message identifying the first beam as the selected beam is transmitted to the network node on the direct link and to the relay node on the indirect link, and the relay node forwards the first BFR message to the network node), beam ambiguity may be avoided.

[0121] As indicated by reference numeral 730, the network node may transmit a BFR response with an updated beam configuration (e.g., RACH message 2, RAR, RACH message B, or another form of signaling), and the remote UE may receive (e.g., monitor) the BFR response with the updated beam configuration. In some aspects, the updated beam configuration may carry information about the beam to be used by the remote UE. In some aspects, the updated beam configuration may be an indication that the selected beam has been accepted by the network node. The updated beam configuration may be transmitted on the direct link on the selected beam. In cases where the network node cannot resolve the beam ambiguity or where resolving the beam ambiguity involves transmitting the updated beam configuration on multiple beams, the network node may transmit the updated beam configuration on the first beam and the second beam. In cases where the first BFR message and the second BFR message each include a timestamp, the UE may monitor the selected beam indicated by the BFR message with the later timestamp. For example, the UE may only monitor the response from the network node to the most recently selected beam indicated by the UE's BFR report (transmitted via BFR MAC-CE or RACH).

[0122] In some aspects, Figure 7The order of the operations shown may be different. For example, the transmissions indicated by reference numerals 710 and 715 / 720 may occur in parallel (e.g., at the same time, at substantially the same time). In other respects, the remote UE may be configured to wait for a period of time (e.g., the transmission of the first BFR message may be separated from the transmission of the second BFR message by this period of time) after transmitting the first BFR message at reference numeral 710 and before transmitting the second BFR message shown at reference numeral 715. In some respects, the remote UE may be configured to transmit the second BFR message if a BFR response is not received from the network node within this period of time.

[0123] In some respects, the remote UE may transmit the second BFR message at reference numeral 715 before transmitting the first BFR message at reference numeral 710. In some respects, the remote UE may be configured to wait for a period of time after transmitting the second BFR message at reference numeral 715 and before transmitting the first BFR message shown at reference numeral 710. In some respects, the remote UE may be configured to transmit the first BFR message if a BFR response is not received from the network node within this period of time.

[0124] In some respects, the network node may respond to each BFR message (including the first BFR message and the second BFR message) until the BFR process is complete. The network node may respond to the first BFR message on a direct link and respond to the second BFR message on a relay link (e.g., a direct link to a relay node and an indirect link between the relay node and the remote UE).

[0125] In some respects, the network node may configure the remote UE to apply the techniques discussed above (e.g., via RRC signaling or another form of signaling). For example, the network node may configure the UE to transmit the first BFR message on a direct link and the second BFR message on an indirect link in parallel, transmit the first BFR message on a direct link before transmitting the second BFR message on an indirect link, transmit the second BFR message on an indirect link before transmitting the first BFR message on a direct link, the period of time between transmitting the first BFR message and the second BFR message, etc. The network node may configure the remote UE to apply these different techniques based on various characteristics such as quality of service (QoS), UE capabilities, UE capacity, etc. In some respects, the network node may configure multiple different configurations and may indicate the selected configuration from the multiple different configurations via subsequent signaling (e.g., MAC signaling or DCI).

[0126] Example 700 improves latency and reduces the power consumption of the UE after detecting a beam failure. Example 700 also allows the network node and the remote UE to resolve or avoid the ambiguity caused by the multipath BFR process more quickly.

[0127] As indicated above, Figure 7 is provided as an example. Other examples may be different from what is Figure 7 described.

[0128] Figure 8 is a diagram of Example 800 associated with the BFR procedure via relay node 805 according to the present disclosure. As Figure 8 shown, a first UE (e.g., UE 120) may communicate with nodes (e.g., network node 110, second UE 120) on an indirect link and communicate with relay node 805 (e.g., network node 110 or a different UE different from UE 120) on a direct link or an indirect link. In some aspects, the first UE, the nodes, and relay node 805 may be part of a wireless network (e.g., wireless network 100). The first UE, the nodes, and relay node 805 may have established a wireless connection before the Figure 8 operations shown. Example 800 assumes a failure on the indirect link (e.g., the indirect link is a failed link).

[0129] As indicated by reference numeral 810, the first UE may send a BFR message (also referred to as a first BFR message) on an indirect link (e.g., a sidelink), and the nodes may receive the BFR message on the indirect link. The BFR message may be created after the first UE detects a beam failure on the indirect link. In one aspect, the BFR message may identify the first beam as the selected beam. In one aspect, the first BFR message may include a first timestamp. In one aspect, the first timestamp may indicate the time when the first BFR message is generated, the time when the first BFR message is sent, or the time when beam measurement occurs. In some aspects, the first BFR message may be sent via RACH communication.

[0130] As shown by reference numeral 815, the first UE may send a second BFR message on a direct link, and the relay node may receive the second BFR message on the direct link. In one aspect, the second BFR message may be the same as the first BFR message sent on the indirect link at reference numeral 810. That is, the second BFR message sent on the direct link may identify the first beam as the selected beam. On the other hand, the second BFR message may be different from the first BFR message sent on the indirect link at reference numeral 810. Thus, the second BFR message may identify the second beam as the selected beam. The first UE may send the second BFR message to the relay node via the direct link. In one aspect, the second BFR message may include a second timestamp. In one aspect, the second timestamp may indicate the time when the second BFR message was generated, the time when the second BFR message was sent, or the time when beam measurement occurred. In one aspect, the first UE may send the first BFR message on both the direct link and the indirect link to avoid ambiguity, which will be discussed in more detail below with reference to reference numeral 825.

[0131] As shown by reference numeral 820, the relay node may send the second BFR message via an indirect link (through the sidelink PC5 interface) or a direct link (via an air interface, such as a radio access link) between the relay node and the node, and the node may receive the second BFR message.

[0132] As shown by reference numeral 825, the node may resolve one or more beam ambiguities in the first BFR message and the second BFR message. Example beam ambiguity may occur when the first BFR message identifies the first beam as the selected beam and the second BFR message identifies the second beam as the selected beam. In one aspect, the node may compare the first timestamp with the second timestamp and select the beam associated with the later of the two timestamps as the selected beam. On the other hand, the node may resolve the beam ambiguity by transmitting on both the first beam and the second beam until the BFR process is complete. On the other hand, if the BFR messages sent on the direct link and the indirect link are the same (i.e., the first BFR message that identifies the first beam as the selected beam is sent to the node on the direct link and to the relay node on the indirect link, and the relay node forwards the first BFR message to the node), then beam ambiguity may be avoided.

[0133] As shown by reference numeral 830, the node may send a BFR response with an updated beam configuration, and the first UE may receive the BFR response. The updated beam configuration may be sent on a direct link on a selected beam. In cases where the node cannot resolve beam ambiguity or where resolving beam ambiguity involves sending the updated beam configuration on multiple beams, the node may send the updated beam configuration on a first beam and a second beam.

[0134] In some aspects, Figure 8 the order of the operations shown may be different. For example, the transmissions shown by reference numerals 810 and 815 / 820 may occur in parallel. In other aspects, the first UE may be configured to wait for a period of time after transmitting the first BFR message at reference numeral 810 and before transmitting the second BFR message at reference numeral 815. In some aspects, the first UE may be configured to: transmit the second BFR message in cases where a BFR response is not received from the node within the period of time.

[0135] In some aspects, the node may respond to each BFR message (including the first message and the second message) from the first UE until the BFR process is complete. The node may respond to the first BFR message on an indirect link and respond to the second BFR message on a relay link (e.g., a direct or indirect link to a relay node and a direct or indirect link between the relay node and the remote UE).

[0136] Alternatively, in some aspects, the first UE may transmit the second BFR message at reference numeral 815 before transmitting the first BFR message at reference numeral 810. In some aspects, the first UE may be configured to wait for a period of time after transmitting the second BFR message at reference numeral 815 and before transmitting the first BFR message at reference numeral 810. In some aspects, the first UE may be configured to: transmit the first BFR message in cases where a BFR response is not received from the node within the period of time.

[0137] Example 800 improves latency and reduces power consumption of the first UE after detecting a beam failure. Example 700 also allows the first UE and the node to more quickly resolve or avoid ambiguity caused by a multipath BFR process.

[0138] As indicated above, Figure 8 is provided as an example. Other examples may be different from what is Figure 8 described.

[0139] Figure 9 is a diagram illustrating an example process 900 performed by a UE, such as a UE 120, according to the present disclosure. Example process 900 is a UE (e.g., UE 120, Figure 7And Figure 8 Example of a remote UE) performing operations related to beam failure recovery through a relay node.

[0140] As Figure 9 shown, in some aspects, process 900 may include sending a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on one of the indirect link or the direct link that is not the failed link (block 910). For example, a UE (e.g., using Figure 11 the communication manager 140 and / or the sending component 1104 depicted in

[0141] As Figure 9 further shown, in some aspects, process 900 may include receiving an updated beam configuration for the failed link on a selected beam indicated by the BFR message (block 920). For example, a UE (e.g., using Figure 11 the communication manager 140 and / or the receiving component 1102 depicted in

[0142] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0143] In a first aspect, process 900 includes waiting for a period of time for a BFR response on the indirect link after sending the BFR message.

[0144] In a second aspect, either alone or in combination with the first aspect, process 900 includes: in the case where a BFR response is not received on the indirect link during the period of time, sending a second BFR message on the direct link.

[0145] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 900 includes: sending a previous BFR message on the direct link before sending the BFR message on the indirect link.

[0146] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 900 includes: waiting for a period of time for a BFR response on a direct link, and due to no BFR response to a previous BFR message received within the period, the BFR message is sent on an indirect link.

[0147] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the BFR message includes a first BFR message sent on a direct link and indicating a first beam and a second BFR message sent on an indirect link and indicating a second beam, where one of the first beam or the second beam is a selected beam.

[0148] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the first BFR message and the second BFR message are sent in parallel.

[0149] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, at least one of the first BFR message or the second BFR message includes a timestamp.

[0150] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 900 includes: selecting a selected beam from one of the first beam or the second beam at least partially based on the timestamp.

[0151] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 900 includes: monitoring the first beam and the second beam for communications from a network node before receiving an updated beam configuration.

[0152] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, monitoring the first beam and the second beam until an updated beam configuration from the network node is received on the selected beam.

[0153] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, both the first BFR message and the second BFR message indicate the selected beam.

[0154] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 900 includes: reporting the selected beam in each BFR message until the BFR process is completed.

[0155] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the BFR message is sent on an indirect link via sidelink communication.

[0156] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the direct link is a failed link.

[0157] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the BFR message is sent on the direct link via the RACH.

[0158] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the indirect link is a failed link.

[0159] Although Figure 9 example blocks of process 900 are shown, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to those depicted. Additionally or alternatively, two or more blocks of process 900 may be executed in parallel. Figure 9

[0160] Figure 10 FIG. is an illustration of an example process 1000 performed, for example, by a network node in accordance with the present disclosure. Example process 1000 is an example where a network node (e.g., network node 110, Figure 8 a node of Figure 7 a network node of ) performs operations associated with beam failure recovery via a relay node.

[0161] As Figure 10 shown, in some aspects, process 1000 may include receiving a BFR message regarding a failed link, where the failed link is one of an indirect link with a remote UE via a relay node or a direct link with the remote UE, and where the BFR message is received on one of the indirect link or the direct link that is not the failed link (block 1010). For example, a network node (e.g., using Figure 12 the communication manager 150 and / or the receiving component 1202 depicted in Figures 7 to 8 ) may receive a BFR message regarding a failed link, where the failed link is one of an indirect link with a remote UE (e.g.,

[0162] As Figure 10 further shown, in some aspects, process 1000 may include sending an updated beam configuration for the failed link on a selected beam indicated by the BFR message (block 1020). For example, a network node (e.g., using Figure 12The communication manager 150 and / or the transmitting component 1204 depicted in [description] may transmit an updated beam configuration for a failed link on a selected beam indicated by a BFR message, as described above.

[0163] Procedure 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other procedures described elsewhere herein.

[0164] In a first aspect, procedure 1000 includes: receiving a BFR message on a direct link before receiving a BFR message on an indirect link.

[0165] In a second aspect, either alone or in combination with the first aspect, the BFR message includes a first BFR message on the direct link indicating a first beam and a second BFR message on the indirect link indicating a second beam, where one of the first beam or the second beam is the selected beam.

[0166] In a third aspect, either alone or in combination with one or more of the first aspect and the second aspect, at least one of the first BFR message or the second BFR message includes a timestamp.

[0167] In a fourth aspect, either alone or in combination with one or more of the first aspect to the third aspect, procedure 1000 includes: selecting the selected beam from one of the first beam or the second beam at least partially based on the timestamp.

[0168] In a fifth aspect, either alone or in combination with one or more of the first aspect to the fourth aspect, both the first BFR message and the second BFR message indicate the selected beam.

[0169] In a sixth aspect, either alone or in combination with one or more of the first aspect to the fifth aspect, the updated beam configuration is transmitted on the first beam and the second beam.

[0170] In a seventh aspect, either alone or in combination with one or more of the first aspect to the sixth aspect, procedure 1000 includes: responding to each BFR message from a remote UE until the BFR procedure is complete.

[0171] In an eighth aspect, either alone or in combination with one or more of the first aspect to the seventh aspect, the BFR message is received on the indirect link via sidelink communication.

[0172] In a ninth aspect, either alone or in combination with one or more of the first aspect to the eighth aspect, the direct link is the failed link.

[0173] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a BFR message is received over a direct link sent via a RACH.

[0174] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the indirect link is a failed link.

[0175] Although Figure 10 example boxes of a process 1000 are shown, in some aspects, process 1000 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted. Additionally or alternatively, two or more of the boxes of process 1000 may be performed in parallel. Figure 10

[0176] Figure 11 is a diagram of an example apparatus 1100 for wireless communication in accordance with the present disclosure. Apparatus 1100 may be a UE (e.g., a remote UE), or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 140. Communication manager 140 may include one or more of a beam management component 1108 or a monitoring component 1110, among others.

[0177] In some aspects, apparatus 1100 may be configured to perform one or more operations described herein in connection with Figures 7 to 8 what is described. Additionally or alternatively, apparatus 1100 may be configured to perform one or more processes described herein (such as Figure 9 process 900) or a combination thereof. In some aspects, Figure 11 apparatus 1100 and / or one or more components shown may include one or more components of a UE described in connection with Figure 2 what is described. Additionally or alternatively, Figure 11 one or more components shown may be implemented within one or more components described in connection with Figure 2 what is described. Additionally or alternatively, one or more components of a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0178] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to the one or more other components of the device 1100. In some aspects, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 The one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described.

[0179] The transmitting component 1104 may send communications to the device 1106, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may send the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 The one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described. In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0180] The transmitting component 1104 may send a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is sent on a link other than the failed link among the indirect link or the direct link. The receiving component 1102 or the beam management component 1108 may receive an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0181] After sending the BFR message, the receiving component 1102 may wait for a period of time for a BFR response on the indirect link.

[0182] In the case where no BFR response is received on the indirect link during this period of time, the transmitting component 1104 may send a second BFR message on the direct link.

[0183] The transmitting component 1104 may send a previous BFR message on the direct link before sending the BFR message on the indirect link.

[0184] The receiving component 1102 may wait for a period of time for a BFR response on a direct link.

[0185] The beam management component 1108 may select a selected beam from one of the first beam or the second beam at least partially based on a timestamp.

[0186] The monitoring component 1110 may monitor the first beam and the second beam for communications from a network node before receiving an updated beam configuration.

[0187] The transmitting component 1104 may report the selected beam in each BFR message until the BFR process is complete.

[0188] Figure 11 The number and arrangement of the components shown are provided as an example. In implementation, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 11 those shown. Additionally, Figure 11 two or more of the components shown may be implemented within a single component, or Figure 11 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 11 a set of the (one or more) components shown may perform one or more functions described to be performed by Figure 11 another set of the components shown.

[0189] Figure 12 is a diagram of an example apparatus 1200 for wireless communication in accordance with the present disclosure. The apparatus 1200 may be a network node, or a network node may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, the apparatus 1200 may include a communication manager 150. The communication manager 150 may include one or more of a beam management component 1208 or a selection component 1210, etc.

[0190] In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figures 7 to 8 Additional or alternative, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 10 process 1000 or combinations thereof. In some aspects, Figure 12The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0191] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0192] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0193] The receiving component 1202 can receive a BFR message regarding a failed link, where the failed link is either an indirect link via a relay node to a remote UE or a direct link to the remote UE, and where the BFR message is received on a link other than the failed link among the indirect link or the direct link. The transmitting component 1204 can transmit an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0194] The receiving component 1202 can receive the BFR message on the direct link before receiving the BFR message on the indirect link.

[0195] The selecting component 1210 can select the selected beam from among the first beam or the second beam at least partially based on a timestamp.

[0196] The beam management component 1208 can respond to each BFR message from the remote UE until the BFR process is complete.

[0197] Figure 12 The number and arrangement of the components shown are provided as an example. In an implementation, there may be additional components, fewer components, different components, or components arranged in a different manner compared to those shown. Additionally, Figure 12 compared to those shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Additionally, Figure 12 two or more of the components shown can be implemented within a single component, or Figure 12 a single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 a set of the (one or more) components shown can perform one or more functions described as being performed by Figure 12 another set of the components shown.

[0198] Some aspects of the present disclosure are outlined below:

[0199] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: transmitting a beam failure recovery (BFR) message regarding a failed link, where the failed link is either an indirect link via a relay node to a network node or a direct link to the network node, and where the BFR message is transmitted on a link other than the failed link among the indirect link or the direct link; and receiving an updated beam configuration for the failed link on a selected beam indicated by the BFR message.

[0200] Aspect 2: The method according to aspect 1, the method further comprising: waiting for a period of time for a BFR response on the indirect link after transmitting the BFR message.

[0201] Aspect 3: The method according to aspect 2, the method further comprising: in the case where no BFR response is received on the indirect link during the time period, sending a second BFR message on the direct link.

[0202] Aspect 4: The method according to any one of aspects 1 to 3, the method further comprising: before sending the BFR message on the indirect link, sending a previous BFR message on the direct link.

[0203] Aspect 5: The method according to aspect 4, the method further comprising: waiting for a time period for a BFR response on the direct link, and wherein due to no BFR response to the previous BFR message received during the time period, the BFR message is sent on the indirect link.

[0204] Aspect 6: The method according to any one of aspects 1 to 5, wherein the BFR message includes a first BFR message sent on the direct link and indicating a first beam and a second BFR message sent on the indirect link and indicating a second beam, wherein one of the first beam or the second beam is the selected beam.

[0205] Aspect 7: The method according to aspect 6, wherein the first BFR message and the second BFR message are sent in parallel.

[0206] Aspect 8: The method according to aspect 6, wherein at least one of the first BFR message or the second BFR message includes a timestamp.

[0207] Aspect 9: The method according to aspect 8, the method further comprising: selecting the selected beam from one of the first beam or the second beam at least partially based on the timestamp.

[0208] Aspect 10: The method according to aspect 6, the method further comprising: monitoring the first beam and the second beam for communication from the network node before receiving the updated beam configuration.

[0209] Aspect 11: The method according to aspect 10, wherein monitoring the first beam and the second beam until the updated beam configuration from the network node is received on the selected beam.

[0210] Aspect 12: The method according to aspect 6, wherein both the first BFR message and the second BFR message indicate the selected beam.

[0211] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: reporting the selected beam in each BFR message until the BFR process is completed.

[0212] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the BFR message is sent on the indirect link via sidelink communication.

[0213] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the direct link is the failed link.

[0214] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the BFR message is sent on the direct link via a random access channel (RACH).

[0215] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the indirect link is the failed link.

[0216] Aspect 18: A method of wireless communication performed by a network node, the method comprising: receiving a beam failure recovery (BFR) message regarding a failed link, wherein the failed link is one of an indirect link via a relay node to a remote user equipment (UE) or a direct link to the remote UE, wherein the BFR message is received on the one of the indirect link or the direct link that is not the failed link; and sending an updated beam configuration for the failed link on the selected beam indicated by the BFR message.

[0217] Aspect 19: The method according to Aspect 18, the method further comprising: receiving the BFR message on the direct link before receiving the BFR message on the indirect link.

[0218] Aspect 20: The method according to any one of Aspects 18 to 19, wherein the BFR message includes a first BFR message on the direct link and indicating a first beam and a second BFR message on the indirect link and indicating a second beam, wherein one of the first beam or the second beam is the selected beam.

[0219] Aspect 21: The method according to Aspect 20, wherein at least one of the first BFR message or the second BFR message includes a timestamp.

[0220] Aspect 22: The method according to Aspect 21, the method further comprising: selecting the selected beam from one of the first beam or the second beam at least partially based on the timestamp.

[0221] Aspect 23: The method according to aspect 20, wherein both the first BFR message and the second BFR message indicate the selected beam.

[0222] Aspect 24: The method according to aspect 20, wherein the updated beam configuration is sent on the first beam and the second beam.

[0223] Aspect 25: The method according to any one of aspects 18 to 24, the method further comprising: responding to each BFR message from the remote UE until the BFR process is completed.

[0224] Aspect 26: The method according to any one of aspects 18 to 25, wherein the BFR message is received on the indirect link via sidelink communication.

[0225] Aspect 27: The method according to any one of aspects 18 to 26, wherein the direct link is the failed link.

[0226] Aspect 28: The method according to any one of aspects 18 to 27, wherein the BFR message is received on the direct link via a random access channel (RACH) transmission.

[0227] Aspect 29: The method according to any one of aspects 18 to 28, wherein the indirect link is the failed link.

[0228] Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 29.

[0229] Aspect 31: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 29.

[0230] Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 29.

[0231] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 29.

[0232] Aspect 34: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the methods according to one or more of Aspects 1 to 29.

[0233] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure, or may be obtained from practice of the aspects.

[0234] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. Whether called software, firmware, middleware, microcode, hardware description language, or other name, "software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented by different forms of hardware and / or combinations of hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods does not limit the aspects. Accordingly, the operation and behavior of the systems and / or methods are not described herein with reference to specific software code, as those skilled in the art will understand that the software and hardware may be designed at least in part based on the description herein to implement the systems and / or methods.

[0235] As used herein, depending on the context, "meeting a threshold" may refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0236] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of the various aspects includes each dependent claim in combination with every other claim in the set of claims. As used herein, the phrase referring to a list of items “at least one of” refers to any combination of these items (including a single member). By way of example, “at least one of a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0237] Any element, act, or instruction used herein should not be construed as critical or essential unless explicitly so described. Additionally, as used herein, the article “a” is intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include the one or more items mentioned in connection with the article “the” and may be used interchangeably with “one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” If only intending to refer to a single item, the phrase “only one” or similar language will be used. Additionally, as used herein, the terms “has,” “owns,” “possesses,” etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that “has” A may also have B). Further, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” when used in a series is intended to be open-ended and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either” or “only one”).

[0238] When a "processor" or "one or more processors" (or another device or component, such as a "controller" or "one or more controllers") is described or claimed (within a single claim or across multiple claims) as performing multiple operations or being configured to perform multiple operations, that language is intended to broadly cover a variety of processor architectures and environments. For example, unless otherwise expressly stated (e.g., by using "a first processor" and "a second processor" or other language in the claim that differentiates processors), that language is intended to cover a single processor that performs or is configured to perform all of the operations, a group of processors that jointly perform or are configured to perform all of the operations, a first processor that performs or is configured to perform a first operation and a second processor that performs or is configured to perform a second operation, or any combination of processors that perform or are configured to perform the operations. For example, when a claim has the form: "One or more processors are configured to: perform X; perform Y; and perform Z", the claim should be interpreted to mean "One or more processors are configured to perform X; one or more (possibly different) processors are configured to perform Y; and one or more (also possibly different) processors are configured to perform Z."

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) include: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors being individually or collectively configured to: sending a beam failure recovery (BFR) message about a failed link, wherein the failed link is one of an indirect link with a network node via a relay node or a direct link with the network node, wherein the BFR message is sent on one of the indirect link or the direct link that is not the failed link; as well as An updated beam configuration for the failed link is received on the selected beam indicated by the BFR message.

2. The UE of claim 1, wherein the one or more processors are further configured, individually or collectively, to: wait for a time period for a BFR response on the indirect link after sending the BFR message.

3. The UE of claim 2, wherein the one or more processors are further configured, individually or collectively, to: send a second BFR message on the direct link if no BFR response is received on the indirect link within the time period.

4. The UE of claim 1, wherein the one or more processors are further configured, individually or collectively, to: send a previous BFR message on the direct link before sending the BFR message on the indirect link.

5. The UE of claim 4, wherein the one or more processors are further configured, individually or collectively, to: wait for a time period for a BFR response on the direct link, and wherein the BFR message is on the indirect link due to no BFR response to the previous BFR message within the time period.

6. The UE of claim 1, wherein the BFR message includes a first BFR message on the direct link and indicating a first beam and a second BFR message on the indirect link and indicating a second beam, wherein one of the first beam or the second beam is the selected beam.

7. The UE of claim 6, wherein the first BFR message and the second BFR message are parallel.

8. The UE of claim 6, wherein at least one of the first BFR message or the second BFR message includes a timestamp.

9. The UE of claim 8, wherein the one or more processors are further individually or collectively configured to: select the selected beam from one of the first beam or the second beam based at least in part on the timestamp.

10. The UE of claim 6, wherein the one or more processors are further configured, individually or collectively, to monitor the first beam and the second beam for communications from the network node before receiving the updated beam configuration.

11. The UE of claim 10, wherein the one or more processors for monitoring the first beam and the second beam are configured to monitor the first beam and the second beam until the updated beam configuration is received from the network node on the selected beam.

12. The UE of claim 6, wherein the first BFR message and the second BFR message both indicate the selected beam.

13. The UE of claim 1, wherein the one or more processors are further configured, individually or collectively, to report the selected beam in each BFR message until a BFR process is completed.

14. The UE of claim 1, wherein the BFR message is communicated over the indirect link via a side link.

15. The UE according to claim 1, wherein the direct link is the failed link.

16. The UE of claim 1, wherein the BFR message is sent on the direct link via a random access channel (RACH).

17. The UE of claim 1, wherein the indirect link is the failed link.

18. A network node for wireless communication, the network node include: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors being individually or collectively configured to: receiving a beam failure recovery (BFR) message regarding a failed link, wherein the failed link is one of an indirect link with a remote user equipment (UE) via a relay node or a direct link with the remote UE, wherein the BFR message is received on one of the indirect link or the direct link that is not the failed link; as well as An updated beam configuration for the failed link is sent on the selected beam indicated by the BFR message.

19. The network node of claim 18, wherein the one or more processors are further configured, individually or collectively, to receive the BFR message on the direct link before receiving the BFR message on the indirect link.

20. The network node of claim 18, wherein the BFR message comprises a first BFR message on the direct link and indicating a first beam and a second BFR message on the indirect link and indicating a second beam, wherein one of the first beam or the second beam is the selected beam.

21. The network node of claim 20, wherein at least one of the first BFR message or the second BFR message comprises a timestamp.

22. The network node of claim 21, wherein the one or more processors are further individually or collectively configured to: select the selected beam from one of the first beam or the second beam based at least in part on the timestamp.

23. The network node of claim 20, wherein the first BFR message and the second BFR message both indicate the selected beam.

24. The network node of claim 20, wherein the updated beam is configured on the first beam and the second beam.

25. The network node of claim 18, wherein the one or more processors are further configured, individually or collectively, to respond to each BFR message from the remote UE until a BFR process is completed.

26. The network node of claim 18, wherein the BFR message is communicated over the indirect link via a side link.

27. The network node of claim 18, wherein the direct link is the failed link.

28. The network node of claim 18, wherein the BFR message is sent on the direct link via a random access channel (RACH).

29. The network node of claim 18, wherein the indirect link is the failed link.

Images