Beam suspension or link recovery for fault events

Abstract

Various aspects of this disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can determine that a beam or link failure event between the UE and a base station is occurring or will occur, and send a message to the base station instructing the UE to avoid performing a beam or link recovery procedure for a period of time. Many other aspects are provided.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 985,830, filed March 5, 2020, entitled “SUSPENSION OF BEAM OR LINK RECOVERY FOR A FAILURE EVENT,” and U.S. Non-Provisional Patent Application No. 17 / 249,394, filed March 1, 2021, entitled “SUSPENSION OF BEAM OR LINK RECOVERY FOR A FAILURE EVENT,” which are expressly incorporated herein by reference. Background Technology

[0003] This disclosure generally relates to wireless communication and techniques and apparatus for suspending beams or restoring links.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies 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 / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] Wireless communication networks may include multiple base stations capable of supporting communication between multiple user devices. UEs can communicate with the BS via downlink and uplink. "Downlink" or "forward link" refers to the communication link from the BS to the UE, and "uplink" or "backward link" refers to the communication link from the UE to the BS. As will be described in more detail herein, the BS may be referred to as NodeB, gNB, Access Point (AP), Radio Head, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] The aforementioned multiple access technologies have been adopted by various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the municipal, national, regional, and even global levels. NR, also known as 5G, is a collection of enhancements to the LTE mobile standard issued by 3GPP. NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. However, with the increasing demand for mobile broadband access, LTE and NR technologies require further improvement. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0007] In some aspects, methods for wireless communication performed by a user equipment (UE) may include determining that a beam or link failure event between the UE and a base station is occurring or is about to occur. This method may include sending a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0008] In some aspects, a method of wireless communication performed by a base station may include receiving from a UE a message indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event. The method may include avoiding abandoning or reallocating the beam or link during that duration.

[0009] In some aspects, a method for wireless communication performed by a UE may include determining that one or more failure events of a beam or link between the UE and a base station have occurred. This method may include sending a message to the base station indicating information associated with one or more failure events.

[0010] In some aspects, a method of wireless communication performed by a base station may include receiving from a UE a message indicating information associated with one or more failure events occurring in a beam or link between the UE and the base station. The method may include reconfiguring the UE's recovery process based at least in part on the information associated with the one or more failure events.

[0011] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory. The memory and the one or more processors can be configured to determine that a beam or link failure event between the UE and the base station is occurring or will occur, and to send a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0012] In some aspects, a base station for wireless communication includes a memory and one or more processors coupled to the memory. The memory and one or more processors can be configured to receive messages from a UE indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event, and avoids abandoning or reallocating the beam or link during that duration.

[0013] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory. The memory and the one or more processors can be configured to determine that one or more failure events of a beam or link between the UE and a base station have occurred, and to send a message to the base station indicating information associated with the one or more failure events.

[0014] In some aspects, a base station for wireless communication includes a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to receive messages from the UE indicating information associated with one or more failure events occurring in the beam or link between the UE and the base station, and to reconfigure the UE's recovery process based at least in part on the information associated with the one or more failure events.

[0015] In some respects, a non-transitory computer-readable medium may store a set of instructions for wireless communication, which includes one or more instructions that, when executed by one or more processors of the UE, cause the UE to determine that a beam or link failure event between the UE and the base station is occurring or is about to occur, and send a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0016] In some respects, a non-transitory computer-readable medium may store a set of instructions for wireless communication, including one or more instructions that, when executed by one or more processors of a base station, cause the base station to receive a message from a UE indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event, and avoids abandoning or reallocating the beam or link during that duration.

[0017] In some respects, a non-transitory computer-readable medium may store a set of instructions for wireless communication, which includes one or more instructions that, when executed by one or more processors of the UE, cause the UE to determine that one or more failure events of a beam or link between the UE and the base station have occurred, and send a message to the base station indicating information associated with the one or more failure events.

[0018] In some aspects, a non-transitory computer-readable medium may store a set of instructions for wireless communication, including one or more instructions that, when executed by one or more processors of a base station, cause the base station to receive from the UE a message indicating information associated with one or more failure events occurring in a beam or link between the UE and the base station, and to reconfigure the UE's recovery process based at least in part on the information associated with the one or more failure events.

[0019] In some aspects, an apparatus for wireless communication may include components for determining that a beam or link failure event is occurring or will occur between the apparatus and a base station, and components for sending a message to the base station instructing the apparatus to avoid performing a beam or link recovery process for a period of time.

[0020] In some aspects, an apparatus for wireless communication may include components for receiving from a UE a message indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event, and components for avoiding abandoning or reallocating the beam or link during that period of time.

[0021] In some aspects, an apparatus for wireless communication may include components for determining that one or more failure events of a beam or link between the apparatus and a base station have occurred, and components for sending a message to the base station indicating information associated with one or more failure events.

[0022] In some aspects, the apparatus for wireless communication may include components for receiving from the UE a message indicating information associated with one or more fault events occurring in the beam or link between the UE and the apparatus, and components for reconfiguring the recovery process of the UE based at least in part on the information associated with the one or more fault events.

[0023] In some aspects, wireless communication methods performed by the UE may include determining that the UE is experiencing or is about to experience a beam or link failure event, and sending a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0024] In some aspects, a method of wireless communication performed by a base station may include receiving a message from a UE that instructs the UE to avoid performing a recovery process after a beam or link failure event and to avoid abandoning or reallocating the beam or link.

[0025] In some aspects, wireless communication methods performed by the UE may include determining that the UE has experienced one or more failure events of a beam or link, and sending a message to the base station indicating information associated with one or more failure events.

[0026] In some aspects, a method of wireless communication performed by a base station may include receiving from a UE a message indicating information associated with one or more failure events related to a beam or link experienced by the UE, and reconfiguring the UE's recovery process based at least in part on the information associated with the one or more failure events.

[0027] In some aspects, a UE for wireless communication may include a memory and one or more processors coupled to the memory. The memory and one or more processors may be configured to determine that the UE is experiencing or is about to experience a beam or link failure event and send a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0028] In some aspects, a base station for wireless communication may include a memory and one or more processors coupled to the memory. The memory and one or more processors may be configured to receive messages from the UE instructing the UE to avoid performing a recovery process after a beam or link failure event and to avoid abandoning or reallocating the beam or link.

[0029] In some aspects, a UE for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to determine that the UE has experienced one or more beam or link failure events and send a message to the base station indicating information associated with the one or more failure events.

[0030] In some aspects, a base station for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to receive messages from the UE indicating information associated with one or more failure events related to a beam or link experienced by the UE, and to reconfigure the UE's recovery process based at least in part on the information associated with the one or more failure events.

[0031] In some respects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of the UE, the one or more instructions may cause the one or more processors to determine that the UE is experiencing or is about to experience a beam or link failure event, and send a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0032] In some respects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause one or more processors to receive a message from the UE instructing the UE to avoid performing a recovery process after a beam or link failure event and to avoid abandoning or reallocating the beam or link.

[0033] In some respects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of the UE, the one or more instructions may cause the one or more processors to determine that the UE has experienced one or more beam or link failure events and send a message to the base station indicating information associated with the one or more failure events.

[0034] In some respects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to receive from the UE a message indicating information associated with one or more failure events related to a beam or link experienced by the UE, and to reconfigure the UE's recovery process based at least in part on the information associated with the one or more failure events.

[0035] In some aspects, an apparatus for wireless communication may include components for determining whether the apparatus is experiencing or is about to experience a beam or link failure event, and components for sending a message to a base station instructing the apparatus to avoid performing a beam or link recovery process for a period of time.

[0036] In some aspects, the apparatus for wireless communication may include components for receiving from the UE a message instructing the UE to avoid performing a recovery process after a beam or link failure event, and components for avoiding abandoning or reallocating the beam or link.

[0037] In some aspects, a device for wireless communication may include components for determining that the device has experienced one or more failure events of a beam or link, and components for sending a message to a base station indicating information associated with one or more failure events.

[0038] In some aspects, the apparatus for wireless communication may include components for receiving from the UE a message indicating information associated with one or more failure events related to a beam or link experienced by the UE, and components for reconfiguring the UE’s recovery process based at least in part on the information associated with the one or more failure events.

[0039] Aspects typically include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, as described substantially with reference to and illustrated by the accompanying drawings and description.

[0040] The features and technical advantages of the examples according to this disclosure have been outlined quite extensively above to facilitate a better understanding of the detailed description that follows. Other features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures to achieve the same purpose as this disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and operation, and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims. Attached Figure Description

[0041] To gain a more detailed understanding of the features of this disclosure, reference can be made to various aspects briefly summarized above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as the description can be recognized to other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0042] Figure 1 This is a diagram illustrating an example of a wireless communication network according to this disclosure.

[0043] Figure 2 This is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network according to this disclosure.

[0044] Figures 3A-3C This is a diagram illustrating an example of a failure event according to this disclosure.

[0045] Figure 3D This is a diagram illustrating an example of a suspended beam or link recovery process according to this disclosure.

[0046] Figure 4 This is a diagram illustrating an example of a suspended beam or link recovery process according to this disclosure.

[0047] Figure 5This is a diagram illustrating an example process performed by a UE according to this disclosure.

[0048] Figure 6 This is a diagram illustrating an example process performed by a base station, for example, according to this disclosure.

[0049] Figure 7 This is a diagram illustrating an example process performed by a UE according to this disclosure.

[0050] Figure 8 This is a diagram illustrating an example process performed by a base station, for example, according to this disclosure.

[0051] Figure 9 This is a block diagram of an example device for wireless communication according to the present disclosure.

[0052] Figure 10 This is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system according to the present disclosure.

[0053] Figure 11 This is a diagram illustrating an example of an implementation of the code and circuitry for a device according to the present disclosure.

[0054] Figure 12 This is a block diagram of an example device for wireless communication according to the present disclosure.

[0055] Figure 13 This is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system according to the present disclosure.

[0056] Figure 14 This is a diagram illustrating an example of an implementation of the code and circuitry for a device according to the present disclosure.

[0057] Figure 15 This is a diagram illustrating an example process performed by a UE according to this disclosure.

[0058] Figure 16 This is a diagram illustrating an example process performed by a base station, for example, according to this disclosure.

[0059] Figure 17 This is a diagram illustrating an example process performed by a UE according to this disclosure.

[0060] Figure 18 This is a diagram illustrating an example process performed by a base station, for example, according to this disclosure.

[0061] Figure 19 This is a diagram illustrating an example of beam suspension or link recovery for a failure event according to this disclosure.

[0062] Figure 20This is a diagram illustrating an example of beam suspension or link recovery for a failure event according to this disclosure. Detailed Implementation

[0063] For example, a user equipment (UE) may have its transmission beam blocked due to an obstruction event caused by a building, a truck in an adjacent lane, or some other object; this obstruction event can be more generally referred to as a failure event. A failure event may be temporary. For example, a failure event may be temporary because the UE may be in a vehicle that will eventually pass the truck. The UE may be able to wait for the failure event, but unfortunately, the failure event may have already caused the UE to initiate a recovery process, which could be the process of restoring the link between the UE and the base station. That is, even if the truck has moved on, the recovery process may initiate a random access channel (RACH) procedure, which involves additional signaling. In one or more examples, the RACH procedure may not be successful initially due to the failure event, even if the failure event may end after a certain period of time (e.g., the large truck no longer blocks the transmission beam). In other words, the RACH procedure may cause the UE to waste processing and signaling resources.

[0064] Based on the various aspects described herein, the UE can notify the base station that it will avoid following the beam fault recovery (BFR) procedure (or the radio link recovery procedure) for a period of time. By suspending the recovery procedure, the UE can save processing and signaling resources by avoiding one or more unnecessary RACH procedures when the condition leading to the fault event may end.

[0065] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully communicate the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method that uses other structures, functions, or structures and functions practiced outside of or in addition to the aspects of this disclosure described herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0066] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in the detailed description below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, and / or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the entire system.

[0067] It should be noted that while the terms commonly associated with 5G or NR radio access technology (RAT) may be used to describe the aspects herein, the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0068] Figure 1 This diagram illustrates an example of a wireless network 100 according to this disclosure. Wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, among other examples. Wireless network 100 may include multiple base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a UE and may also be referred to as an NR BS, Node B, gNB, 5G node B (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​the BS and / or BS subsystem serving that coverage area, depending on the context in which the term is used.

[0069] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow UEs unrestricted access via a service subscription. A picocell can cover a relatively small geographic area and allow UEs unrestricted access via a service subscription. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access for UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1In the example shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “nodeB,” “5G NB,” and “cell” are used interchangeably herein.

[0070] In some examples, the cell may not be fixed, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some examples, the BS may use any suitable transmitting network to interconnect with each other or to one or more other BSs or network nodes (not shown) in the access wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0071] The wireless network 100 may also include relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, BS110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, and / or relay.

[0072] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs), such as macro BSs, pico BSs, femto BSs, and / or relay BSs. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0073] Network controller 130 can be coupled to a set of Base Stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly via wireless or wired backhaul.

[0074] UEs 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), 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, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0075] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses components of UE 120, such as processor components and / or memory components. In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0076] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Platform (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology or air interface. A frequency can also be referred to as a carrier or frequency channel. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0077] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidechain channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In some aspects, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110. In one example, there may be an object 122 obstructing the radio link 124 (e.g., transmission beam) from UE 120c to BS 110a.

[0078] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the Extremely High Frequency (EHF) band (30GHz-300GHz) recognized as a "millimeter wave" (mmWave) band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0079] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating frequency bands for these mid-band frequencies as the frequency range designation FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the characteristics of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0080] In light of the foregoing, unless otherwise specified, it should be understood that if the term "sub-6GHz" or similar terms are used herein, it can broadly refer to frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, it should be understood that if the term "millimeter wave" or similar terms are used herein, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or may be within the EHF band.

[0081] like Figure 1 As shown, UE 120 may include communication manager 140. As described in more detail elsewhere herein, communication manager 140 may determine that UE 120 is experiencing or is about to experience a beam or link failure event, or that a beam or link failure event between UE 120 and the base station is occurring or will occur. UE 120 may experience a failure event by detecting the failure event (e.g., obtaining a measurement, comparing the measurement to a signal threshold or time threshold, receiving information associated with the failure event, etc.). Communication manager 140 may send a message to the base station instructing UE 120 to avoid (e.g., has already avoided and is continuing to avoid) performing a beam or link recovery procedure for a period of time. Communication manager 140 may determine that UE 120 has experienced one or more beam or link failure events, or that one or more beam or link failure events between UE 120 and the base station have occurred. Communication manager 140 may send a message to the base station indicating information associated with one or more failure events. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0082] In some aspects, base station 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive messages from the UE instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery procedure after a beam or link failure event, and to avoid abandoning or reassigning the beam or link. Communication manager 150 may receive messages from the UE indicating information associated with one or more failure events experienced by the UE or occurring with respect to the beam or link, and reconfigure the UE's recovery procedure based at least in part on the information associated with one or more failure events. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0083] As shown above, it provides Figure 1 This is just an example. Other examples may be related to... Figure 1 The descriptions are different.

[0084] Figure 2This is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein typically T ≥ 1 and R ≥ 1.

[0085] At base station 110, transmitting processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and decoding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE, process the data for each UE (e.g., encoding and modulation) based at least in part on the selected MCS(s) for the UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, authorizations, upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0086] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., with OFDM) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine the Reference Signal Received Power (RSRP) parameter, the Received Signal Strength Indicator (RSSI) parameter, the Reference Signal Received Quality (RSRQ) parameter, and / or the CQI parameter. In some aspects, one or more components of the UE 120 may be included in a housing.

[0087] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include, for example, one or more devices in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0088] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may be included or may be contained within one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, among other examples. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements coupled to one or more transmission and / or reception components (such as...) Figure 2 One or more antenna elements (one or more components).

[0089] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can also generate reference symbols for one or more reference signals. If applicable, the symbols from the transmitting processor 264 can be pre-encoded by the TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM), and transmitted to base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of UE 120 can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0090] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 if applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule UE 120 for downlink and / or uplink communication. In some aspects, modulators and demodulators (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes transceivers. The transceiver may include any combination of antenna(s) 234, modulator and / or demodulator 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 aspects of any of the methods described herein.

[0091] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any and more other components may perform one or more techniques associated with beam pausing or link restoration procedures in response to a failure event, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component (or multiple components) can perform or direct, for example... Figure 5 Process 500 Figure 6 Process 600 Figure 7 The process 700 Figure 8 The operation of process 800 and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. Scheduler 246 may schedule the UE to transmit data on the downlink and / or uplink.

[0092] In some aspects, UE 120 may include components for determining whether the UE is experiencing or is about to experience a beam or link failure event, components for determining whether a beam or link failure event between UE 120 and the base station is occurring or will occur, and / or components for sending a message to the base station instructing UE 120 to avoid performing a beam or link recovery process for a period of time. Additionally or alternatively, UE 120 may include components for performing one or more other operations described herein. In some aspects, such components may include a communication manager 140. Additionally or alternatively, such components may include components combining... Figure 2 One or more components of the UE 120 described.

[0093] In some aspects, UE 120 may include components for determining that UE 120 has experienced one or more beam or link failure events, components for determining that one or more beam or link failure events between UE 120 and the base station have occurred, and / or components for sending a message to the base station indicating information associated with one or more failure events. Additionally or alternatively, UE 120 may include components for performing one or more other operations described herein. In some aspects, such components may include a communication manager 140. Additionally or alternatively, such components may include components combining... Figure 2 One or more components of the described UE 120.

[0094] In some aspects, base station 110 may include components for receiving from the UE a message instructing the UE to avoid (e.g., have already avoided or will avoid) performing a recovery procedure after a beam or link failure event, and / or components for avoiding abandoning or reallocating the beam or link. Additionally or alternatively, base station 110 may include components for performing one or more other operations described herein. In some aspects, such components may include a communication manager 150. In some aspects, such components may include combinations of... Figure 2 One or more components of the described base station 110.

[0095] In some aspects, base station 110 may include components for receiving from the UE a message indicating information associated with one or more failure events experienced by the UE or occurring with respect to a beam or link, and / or components for reconfiguring the UE's recovery process at least in part based on the information associated with one or more failure events. Additionally or alternatively, base station 110 may include components for performing one or more other operations described herein. In some aspects, such components may include a communication manager 150. In some aspects, such components may include combinations of... Figure 2 One or more components of the described base station 110.

[0096] As shown above, it provides Figure 2 This is just an example. Other examples may be related to... Figure 2 The descriptions are different.

[0097] The UE may lose its beam connection to the base station. This loss of beam connection can be termed a beam failure instance, and the UE can receive an indication of a beam failure instance from a lower layer. The UE can start or restart a beam failure detection timer and increment the beam failure counter. Starting the beam failure detection timer can reset the beam failure counter or set it to start from 1 again. If the beam failure counter reaches the maximum number of beam failure instances, the UE can determine that it is experiencing or about to experience a failure event, or that a beam or link failure event is occurring or will occur.

[0098] Failure events may be caused by large objects or objects placed in the path of beam connections. Such objects can be buildings, natural structures, and / or large vehicles (e.g., large truck trailers in adjacent lanes). As part of the Maximum Permissible Exposure (MPE) limit, failure events may also involve people or parts of people.

[0099] A failure event can cause the UE to perform a recovery procedure. The recovery procedure may include initiating a RACH procedure with the base station. The RACH procedure involves additional processing and signaling for the UE. Due to the failure event, the RACH procedure may not succeed immediately, thus potentially wasting processing and signaling resources, especially if the failure event is temporary. For example, the UE might be in a vehicle that is eventually passing a building or a truck.

[0100] Based on the aspects described herein, the UE can notify the base station that it will avoid performing a recovery procedure, which is typically required when a fault event is detected. By not performing the recovery procedure, the UE can save processing and signaling resources that would otherwise be used to perform one or more unnecessary RACH procedures when the conditions leading to the fault event may disappear. While some aspects are described in the context of Beam Failure Detection (BFD) and BFR, the aspects described herein also apply to Radio Link Failure (RLF) in the context of Radio Link Monitoring (RLM).

[0101] Figures 3A-3C The diagram illustrates examples 300, 302, and 304 of the failure events according to this disclosure. Figures 3A-3C The diagram shows BS 310s that can communicate with each other (e.g., Figure 1 and Figure 2 The BS 110 and UE 320 (as depicted in the text) Figure 1 and Figure 2 UE 120 as depicted in the text.

[0102] exist Figure 3A In Example 300, BS 310 and UE 320 may have already established a connection via beam 306 (or radio link). However, UE 320 can detect a fault event caused by a large object in the connected beam path. The large object could be, for example, a large truck. Beam 306 might be blocked by the large truck.

[0103] As shown by reference numeral 315 in the attached figure, UE 320 can perform a beam recovery procedure. For example, the recovery procedure can be a default recovery procedure. The default recovery procedure can be the procedure that UE 320 uses by default to recover lost connections (e.g., beams, links). The recovery procedure may include a RACH procedure for re-establishing a connection or establishing a new connection. UE 320 can perform the RACH procedure even if the truck may soon leave the beam's path.

[0104] While examples for beams are provided, the aspects described in this article also apply to other links. Figure 3B Example 302 illustrates that a failure event may occur due to a building blocking the path of radio link 308.

[0105] Figure 3C Example 304 illustrates a failure event that may occur due to an MPE event. For example, a person or a part of a person's body may be in the path of beam 306. UE 320 may operate with an MPE limit that restricts the amount of human exposure in the path of beam 306. UE 320 may reduce the transmit power of beam 306 to meet the MPE limit. Due to the lower transmit power, transmission may fail, and a failure event may occur.

[0106] Figure 3D This is a diagram illustrating example 330 of a suspended beam or link recovery process according to this disclosure. Figure 3D It shows Figure 3A A large truck blocked beam 306 from UE 320 to BS 310.

[0107] BS 310 and UE 320 may have already established a connection via beam 306. However, as indicated by reference numeral 335, UE 320 may determine, at least in part, that UE 320 is experiencing or about to experience a fault event, or that a fault event is about to occur, based on the number of beam fault instances during the beam fault timer.

[0108] As shown by reference numeral 340 in the attached figure, UE 320 may send a message instructing UE 320 to avoid performing the beam recovery procedure of beam 306 for a period of time (e.g., Radio Resource Control (RRC) message, Media Access Control Element (MAC-CE), Downlink Control Information (DCI)). For example, UE 320 may avoid performing... Figure 3A The RACH procedure is shown in the diagram. UE 320 can pause or cancel the recovery procedure entirely. In some aspects, UE 320 can modify the parameters used for the recovery procedure, at least in part, based on the configuration from BS 310. For example, UE 320 can increase the maximum value of the beam instance counter, increase the duration of the beam failure timer, and / or adjust the combination of the maximum value and duration.

[0109] In some aspects, UE 320 may send messages only for certain conditions. For example, UE 320 may send messages based at least in part on determining that a fault event (or potential fault event) is a specific type of fault event. UE 320 may obtain information about the type of fault event from stored configuration information and / or RRC messages. In some aspects, UE 320 may learn various types of fault events. For example, UE 320 may learn that the obstruction of a passing truck trailer lasted for a certain amount of time and / or that certain characteristics of the fault event exist that could identify it as a vehicle-type fault event rather than a building-type fault event. UE 320 may determine the type of fault event based at least in part on the number, interval, or velocity of beam fault instances during a specific duration. UE 320 may use other sensor or signaling feedback (e.g., signal strength, signal variance, signal reflection) to determine the type of fault event.

[0110] In some respects, UE 320 may dynamically notify BS 310 signaling (e.g., Physical Uplink Control Channel messages) that UE 320 will suspend the recovery process. For example, UE 320 may send a message for each fault event that is occurring or about to occur. In some respects, UE 320 may notify BS 310 signaling (e.g., RRC, MAC-CE) that UE 320 may suspend the recovery process if a prolonged blocking event occurs in the future. For example, if UE 320 determines that the blocking event will not last for a long time, or if UE 320 determines, at least in part, based on measurements of candidate beams continuously measured by UE 320 for BFR purposes, that there is a stronger alternative beam or multiple beams to replace the currently serving beam 306, then UE 320 may follow the regular BFR or RLF recovery process. If UE 320 determines that the blocking event will last longer than a threshold duration and there is no suitable candidate beam with good reception that can be switched to, UE 320 may decide to avoid performing the regular recovery process for a period of time.

[0111] In some respects, UE 320 may send a message to the base station based at least in part on a determination of the probability that UE 320 will meet the threshold for maintaining beam 306. This determination may be based at least in part on the internal state of an algorithm used to find another beam or another link. For example, UE 320 may send a message when it determines (or has reasonable confidence) that beam 306 will survive a failure event that would typically trigger a BFD / RLF. UE 320 may have an advanced search algorithm (e.g., based on a neural network), and the confidence level may be based at least in part on the internal state of that algorithm (e.g., UE 320 has just received some new data and / or is about to generate a new proposed receive beam).

[0112] As shown by reference numeral 345 in the attached figure, BS 310 can avoid abandoning or reallocating beam 306 for a period of time, at least in part, based on the receipt of a message. For example, BS 310 may have already disconnected on the beam after signal loss, allowing beam 306 to be reallocated to another connection. Instead, BS 310 can decide to wait for the fault event to end and resume the same connection later, without undergoing a RACH procedure during that duration. Note that while a RACH procedure may not occur immediately, there may be a later RACH procedure to satisfy the needs of another connection. In particular, if BS 310 does not receive an acknowledgment or negative acknowledgment from UE 320, BS 310 can also avoid sending data to UE 320 during that duration. If UE 320 recovers, or if BS receives a RACH message from UE 320, BS 310 can resume data transmission. As a result of the above operations, BS 310 and UE 320 can save processing and signaling resources by avoiding one or more potentially unnecessary RACH procedures.

[0113] As shown above, Figures 3A-3D Some examples are provided. Other examples may be related to... Figures 3A-3D The descriptions are different.

[0114] Figure 4 This is a diagram illustrating an example 400 of a suspended beam or link recovery process according to this disclosure. Figure 4 The diagram shows BS 410s that can communicate with each other (e.g., Figure 1 and Figure 2 BS 110 depicted in Figure 3, BS 310 depicted in Figure 3, and UE 420 (e.g., Figure 1 and Figure 2 (UE 120 depicted in Figure 1, UE 320 depicted in Figure 3).

[0115] BS 410 and UE 420 can establish a connection via a beam or link. As shown by reference numeral 430, UE 420 can determine that UE 420 has experienced one or more fault events. UE 420 can collect information about the fault events (e.g., blocking duration, number of failed instances of blocking duration) or statistics about multiple fault events.

[0116] As shown by reference numeral 435 in the attached figure, UE 420 can send a message containing this information. In some aspects, UE 420 can send a message after each failure event. Alternatively or additionally, UE 420 can send a message after multiple failure events.

[0117] As indicated by reference numeral 440 in the attached figure, BS 410 can reconfigure the recovery procedure of UE 420 at least in part based on this information. For example, BS 410 can extend or shorten the duration of the beam fault detection timer, increase or decrease the maximum number of beam instances, and / or adjust the combination of duration and maximum value. While some aspects are described in the context of BFD and BFR, the aspects described herein can also be applied to RLF in the context of RLM. For both BFD and RLM, BS 410 and UE 420 can save processing and signaling resources by not performing more RACH procedures than might be required.

[0118] In some respects, UE 420 can send information to BS 410, and BS 410 can send a reconfiguration for the recovery procedure. UE 420 can modify the parameters used for the recovery procedure, at least in part, based on the reconfiguration from BS 410. For example, UE 420 can increase the maximum value of the beam instance counter, increase the duration of the beam failure timer, and / or adjust the combination of the maximum value and the duration.

[0119] As shown above, it provides Figure 4 This is just an example. Other examples may be related to... Figure 4 The descriptions are different.

[0120] Figure 5 This is a diagram illustrating an example process 500 performed by a UE according to this disclosure. Example process 500 is where the UE (e.g., Figure 1 and Figure 2 The UE 120 depicted in Figure 1 and the UE 320 depicted in Figure 3 are shown in Figure 3. Figure 4 The example depicted is a UE 420 performing operations associated with beam suspension or link restoration in response to a fault event.

[0121] like Figure 5 As shown, in some aspects, process 500 may include determining that the UE is experiencing or is about to experience a beam or link failure event (block 510). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282) may determine that the UE is experiencing or is about to experience a beam or link failure event, as described above.

[0122] like Figure 5As further shown, in some aspects, process 500 may include sending a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time (block 520). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282) may send a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time, as described above.

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

[0124] In the first aspect, the recovery process is the default recovery process.

[0125] In the second aspect, either alone or in combination with the first aspect, the recovery process includes initiating the RACH process.

[0126] In the third aspect, alone or in combination with one or more of the first and second aspects, the duration is based at least in part on the duration of one or more conditions that lead to the failure event.

[0127] In the fourth aspect, alone or in combination with one or more of the first to third aspects, process 500 includes canceling the recovery process.

[0128] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 500 includes modifying parameters used for the recovery process.

[0129] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the message is one of an RRC message, a MAC-CE message, or a Physical Uplink Control Channel (PUCCH) message.

[0130] In the seventh aspect, sending a message to a base station, either alone or in combination with one or more of the first to sixth aspects, includes determining the type of the fault event based at least in part on information associated with the fault event, and sending the message based at least in part on the type of the fault event.

[0131] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the parameters include one or more of the following: the duration of the beam fault detection timer, the duration of the link fault detection timer, the maximum value of the beam fault indication counter, or the maximum value of the link fault indication counter.

[0132] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending a message to the base station includes sending the message based at least in part on a determination of the probability that the UE will meet a threshold for maintaining a beam or link, the determination being based at least in part on the internal state of an algorithm for finding another beam or another link.

[0133] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, sending a message includes sending a message based at least in part on the determination that the UE is about to experience a fault event.

[0134] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the message instructs the UE to avoid performing a recovery process for the duration of each of the multiple failure events of the beam or link.

[0135] although Figure 5 An example box of process 500 is shown, but in some aspects, process 500 may include more than Figure 5 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 500 may be executed in parallel.

[0136] Figure 6 This is a diagram illustrating an example process 600 performed, for example, by a base station according to this disclosure. Example process 600 is where the base station (e.g., Figure 1 and Figure 2 BS 110 depicted in Figure 2, BS 310 depicted in Figure 3, Figure 4 The example depicted in the text is of a BS 410 performing operations associated with beam suspension or link restoration in response to a failure event.

[0137] like Figure 6 As shown, in some aspects, process 600 may include receiving from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery procedure after a beam or link failure event (block 610). For example, a base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may receive from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery procedure after a beam or link failure event, as described above.

[0138] like Figure 6 As further shown, in some aspects, process 600 may include avoiding abandoning or reallocating beams or links (block 620). For example, a base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may avoid abandoning or reallocating beams or links as described above.

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

[0140] In the first respect, the recovery process is the default process.

[0141] In the second aspect, either alone or in combination with the first aspect, the recovery process includes initiating the RACH process.

[0142] In the third aspect, alone or in combination with one or more of the first and second aspects, the message is one of an RRC message, a MAC-CE message, or a PUCCH message.

[0143] although Figure 6 An example box of process 600 is shown, but in some aspects, process 600 may include more than Figure 6 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 600 may be executed in parallel.

[0144] Figure 7 This is a diagram illustrating an example process 700 performed by a UE according to this disclosure. Example process 700 is where the UE (e.g., Figure 1 and Figure 2 The UE 120 depicted in Figure 1 and the UE 320 depicted in Figure 3 are shown in Figure 3. Figure 4 The example depicted is a UE 420 performing operations associated with beam suspension or link restoration in response to a fault event.

[0145] like Figure 7 As shown, in some aspects, process 700 may include determining that the UE has experienced one or more beam or link failure events (block 710). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282) may determine that the UE has experienced one or more beam or link failure events, as described above.

[0146] like Figure 7 As further shown, in some aspects, process 700 may include sending a message to the base station indicating information associated with one or more fault events (block 720). For example, the UE (e.g., using a receive processor 258, a transmit processor 264, a controller / processor 280, and a memory 282) may send a message to the base station indicating information associated with one or more fault events, as described above.

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

[0148] In the first aspect, one or more failure events are a single failure event, and the information includes the duration of the single failure event.

[0149] In the second aspect, alone or in combination with the first aspect, one or more fault events include multiple fault events, and the information is fault statistics information of multiple fault events.

[0150] although Figure 7 An example box of process 700 is shown, but in some aspects, process 700 may include more than Figure 7 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 700 may be executed in parallel.

[0151] Figure 8 This is a diagram illustrating an example process 800 performed, for example, by a base station according to this disclosure. Example process 800 is where the base station (e.g., Figure 1 and Figure 2 BS 110 depicted in Figure 2, BS 310 depicted in Figure 3, Figure 4 The example depicted in the text is of a BS 410 performing operations associated with beam suspension or link restoration in response to a failure event.

[0152] like Figure 8 As shown, in some aspects, process 800 may include receiving from the UE a message indicating information associated with one or more fault events experienced by the UE (block 810). For example, a base station (e.g., using a transmitting processor 220, a receiving processor 238, a controller / processor 240, and a memory 242) may receive from the UE a message indicating information associated with one or more fault events experienced by the UE, as described above.

[0153] like Figure 8 As further shown, in some aspects, process 800 may include reconfiguring the UE's recovery process at least in part based on information associated with one or more fault events (block 820). For example, a base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may reconfigure the UE's recovery process at least in part based on information associated with one or more fault events, as described above.

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

[0155] In the first aspect, the reconfiguration recovery process includes updating one or more of the following: a fault timer, the maximum number of fault instances for the UE, or a combination of a fault timer and the maximum number of fault instances.

[0156] In the second aspect, alone or in combination with the first aspect, one or more failure events include a single failure event, and the information is the duration of the single failure event.

[0157] In the third aspect, alone or in combination with one or more of the first and second aspects, one or more fault events include multiple fault events, and the information is fault statistics information of multiple fault events.

[0158] In the fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes accelerating the RLF timer based at least in part on beam fault indication.

[0159] although Figure 8 An example box of process 800 is shown, but in some aspects, process 800 may include more than Figure 8 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 800 may be executed in parallel.

[0160] Figure 9 This is a block diagram of an example device 900 for wireless communication. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (e.g., a UE (e.g., UE 120e, and others), a base station (e.g., BS110a, BS 110d, and others) or another wireless communication device). As further shown, device 900 may include a determining component 908, and others.

[0161] In some respects, device 900 can be configured to perform the functions described herein. Figure 1-4 The described one or more operations. Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as... Figure 5 Process 500 Figure 7 The process 700 or a combination thereof. In some respects, Figure 9 The device 900 and / or one or more components shown may include the above-described combination. Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 9One or more components shown can be combined on top. Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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 function or operation of the component.

[0162] Receiver 902 can receive communications such as reference signals, control information, data communications, or combinations thereof from device 906. Receiver 902 can provide the received communications to one or more other components of device 900. In some aspects, receiver 902 can perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and can provide the processed signal to one or more other components of device 906. In some aspects, receiver 902 can include the above-described combinations... Figure 2 The network node described includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0163] Transmission component 904 can transmit communications such as reference signals, control information, data communications, or combinations thereof to device 906. In some aspects, one or more other components of device 906 can generate communications and provide the generated communications to transmission component 904 for transmission to device 906. In some aspects, transmission component 904 can perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 906. In some aspects, transmission component 904 can include the combinations described above. Figure 2 The described network node includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in the transceiver.

[0164] The determining component 908 can determine that the UE is experiencing or is about to experience a beam or link failure event, or determine that a failure event between the UE and the base station is about to occur. The transmitting component 904 can send a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0165] The determining component 908 can determine that the UE has experienced one or more beam or link failure events, or determine that one or more failure events have occurred between the UE and the base station. The transmitting component 904 can send a message to the base station indicating information associated with one or more failure events.

[0166] Figure 9 The number and arrangement of components shown are provided as an example. In practice, there may be additional components, fewer components, different components, or components similar to those shown. Figure 9 The components are shown in different arrangements. Furthermore... Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown can perform actions described as being performed by Figure 9 The other set of components shown performs one or more functions.

[0167] Figure 10 This is a diagram illustrating an example 1000 of a hardware implementation of a device 1005 employing a processing system 1010. The device 1005 may be a UE.

[0168] Processing system 1010 can be implemented using a bus architecture, generally represented by bus 1015. Depending on the specific application and overall design constraints of processing system 1010, bus 1015 may include any number of interconnect buses and bridges. Bus 1015 links together various circuits including one or more processors and / or hardware components represented by processor 1020, the illustrated components, and computer-readable medium / memory 1025. Bus 1015 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, power management circuits, etc.

[0169] Processing system 1010 may be coupled to transceiver 1030. Transceiver 1030 is coupled to one or more antennas 1035. Transceiver 1030 provides components for communicating with various other devices via a transmission medium. Transceiver 1030 receives signals from one or more antennas 1035, extracts information from the received signals, and provides the extracted information to processing system 1010, specifically receiving component 902. Furthermore, transceiver 1030 receives information from processing system 1010, particularly transmission component 904, and generates signals to be applied to one or more antennas 1035 based at least in part on the received information.

[0170] Processing system 1010 includes a processor 1020 coupled to a computer-readable medium / memory 1025. Processor 1020 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1025. When executed by processor 1020, the software causes processing system 1010 to perform the various functions described herein for any particular device. Computer-readable medium / memory 1025 can also be used to store data manipulated by processor 1020 during software execution. Processing system 1010 also includes at least one of the components shown. These components may be software modules running in processor 1020, residing in / stored on computer-readable medium / memory 1025, one or more hardware modules coupled to processor 1020, or combinations thereof.

[0171] In some aspects, the processing system 1010 may be a component of base station 110 (e.g., BS 110a, BS 110d, and other examples) and may include memory 242 and / or at least one of TX MIMO processor 230, RX processor 238, and / or controller / processor 240. In some aspects, the processing system 1010 may be a component of UE 120 (e.g., UE 120e, and other examples) and may include controller / processor 280, TX processor 264, TX MIMO processor 266, and / or RX processor 258. In some aspects, the apparatus 1005 for wireless communication includes components for determining whether a beam or link failure event is being experienced or is about to be experienced by the UE, components for determining whether a beam or link failure event between the UE and the base station is occurring or will occur, and / or components for sending a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time. In some aspects, apparatus 1005 may include components for determining that the UE has experienced one or more beam or link failure events, components for determining that one or more beam or link failure events between the UE and the base station have occurred, and / or components for sending a message to the base station indicating information associated with one or more failure events. The aforementioned components may be one or more of the aforementioned components of apparatus 900 and / or processing system 1010 of apparatus 1005 configured to perform the functions described herein. As described elsewhere herein, processing system 1010 may include TX MIMO processor 230, receive processor 238, and / or controller / processor 240. In one configuration, the aforementioned components may be TX MIMO processor 230, receive processor 238, and / or controller / processor 240 configured to perform the functions and / or operations described herein.

[0172] supply Figure 10 As an example. Other examples may be combined with... Figure 10 The descriptions are different.

[0173] Figure 11 This is a diagram illustrating an example 1100 of the implementation of code and circuitry for device 1105. Device 1105 may be a UE.

[0174] like Figure 11 As further shown, the apparatus may include circuitry (circuit 1120) for determining whether the UE is experiencing or is about to experience a beam or link failure event. For example, the apparatus may include circuitry that enables the apparatus to determine whether the UE is experiencing or is about to experience a beam or link failure event.

[0175] like Figure 11 As further shown, the apparatus may include circuitry (circuit 1125) for determining whether a beam or link failure event between the UE and the base station is occurring, about to occur, or has already occurred. For example, the apparatus may include circuitry that enables the apparatus to determine whether a beam or link failure event between the UE and the base station is occurring, about to occur, or has already occurred.

[0176] like Figure 11 As further shown, the apparatus may include circuitry (circuit 1130) for sending a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time. For example, the apparatus may include circuitry enabling the apparatus to send a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time.

[0177] like Figure 11 As further shown, the apparatus may include circuitry (circuit 1135) for sending a message to a base station indicating information associated with one or more fault events. For example, the apparatus may include circuitry enabling it to send a message to a base station indicating information associated with one or more fault events.

[0178] like Figure 11 As further shown, the device may include code (code 1140) stored in the computer-readable medium 1025 for determining whether the UE is experiencing or about to experience a beam or link failure event. For example, the device may include code that, when executed by the processor 1020, enables the processor 1020 to determine whether the UE is experiencing or about to experience a beam or link failure event.

[0179] like Figure 11As further shown, the apparatus may include code (code 1145) stored in computer-readable medium 1025 for determining whether a beam or link failure event between the UE and the base station is occurring, about to occur, or has already occurred. For example, the apparatus may include code that, when executed by processor 1020, enables processor 1020 to determine whether a beam or link failure event between the UE and the base station is occurring, about to occur, or has already occurred.

[0180] like Figure 11 As further shown, the apparatus may include code (code 1150) stored in computer-readable medium 1025 for sending a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time. For example, the apparatus may include code that, when executed by processor 1020, causes processor 1020 to cause transceiver 1030 to send a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time.

[0181] like Figure 11 As further shown, the apparatus may include code (code 1155) stored in computer-readable medium 1025 for sending a message to a base station indicating information associated with one or more fault events. For example, the apparatus may include code that, when executed by processor 1020, causes processor 1020 to cause transceiver 1030 to send a message to the base station indicating information associated with one or more fault events.

[0182] supply Figure 11 As an example. Other examples may be combined with... Figure 11 The descriptions are different.

[0183] Figure 12 This is a block diagram of an example device 1200 for wireless communication. Device 1200 may be a base station, or a base station may include device 1200. In some aspects, device 1200 includes a receiving component 1202 and a transmitting component 1204, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1200 can use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1206 (e.g., a UE (e.g., UE 120e, and others), a base station (e.g., BS 110a, BS 110d, and others) or another wireless communication device). As further shown, device 1200 may include a recovery component 1208, and others.

[0184] In some respects, device 1200 can be configured to perform the functions described herein. Figure 1-4 The one or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as... Figure 6 Process 600 Figure 8 The process 800 or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include the above-described combination. Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 12 One or more components shown can be combined on top. Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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 function or operation of the component.

[0185] Receiver 1202 can receive communications such as reference signals, control information, data communications, or combinations thereof from device 1206. Receiver 1202 can provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 can perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and can provide the processed signal to one or more other components of device 1206. In some aspects, receiver 1202 may include the above-described combinations... Figure 2 The network node described includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

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

[0187] The receiving component 1202 can receive a message from the UE instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery procedure for a period of time following a beam or link failure event. The recovery component 1208 can avoid abandoning or reallocating the beam or link during this duration.

[0188] The receiving component 1202 can receive messages from the UE indicating information associated with one or more fault events experienced by the UE or occurring in a beam or link between the UE and the base station. The recovery component 1208 can reconfigure the UE's recovery process based at least in part on the information associated with the one or more fault events.

[0189] Figure 12 The number and arrangement of components shown are provided as an example. In practice, there may be additional components, fewer components, different components, or components similar to those shown. Figure 12 The components are shown in different arrangements. Furthermore... Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown can perform actions described as being performed by Figure 12 The other set of components shown performs one or more functions.

[0190] Figure 13 This is a diagram illustrating an example 1300 of a hardware implementation of a device 1305 employing a processing system 1310. Device 1305 may be a base station.

[0191] Processing system 1310 can be implemented using a bus architecture, generally represented by bus 1315. Depending on the specific application and overall design constraints of processing system 1310, bus 1315 may include any number of interconnect buses and bridges. Bus 1315 links together various circuits including one or more processors and / or hardware components represented by processor 1320, the illustrated components, and computer-readable medium / memory 1325. Bus 1315 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, power management circuits, etc.

[0192] Processing system 1310 may be coupled to transceiver 1330. Transceiver 1330 is coupled to one or more antennas 1335. Transceiver 1330 provides components for communicating with various other devices via a transmission medium. Transceiver 1330 receives signals from one or more antennas 1335, extracts information from the received signals, and provides the extracted information to processing system 1310, specifically receiving component 1202. Furthermore, transceiver 1330 receives information from processing system 1310, particularly transmission component 1204, and generates signals to be applied to one or more antennas 1335 based at least in part on the received information.

[0193] Processing system 1310 includes a processor 1320 coupled to a computer-readable medium / memory 1325. Processor 1320 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1325. When executed by processor 1320, the software causes processing system 1310 to perform the various functions described herein for any particular device. Computer-readable medium / memory 1325 can also be used to store data manipulated by processor 1320 during software execution. Processing system 1310 also includes at least one of the components shown. These components may be software modules running in processor 1320, residing in / stored on computer-readable medium / memory 1325, one or more hardware modules coupled to processor 1320, or combinations thereof.

[0194] In some aspects, the processing system 1310 may be a component of base station 110 (e.g., BS 110a, BS 110d, and other examples) and may include memory 242 and / or at least one of TX MIMO processor 230, RX processor 238, and / or controller / processor 240. In some aspects, the processing system 1310 may be a component of UE 120 (e.g., UE 120e, and other examples) and may include controller / processor 280, TX processor 264, TX MIMO processor 266, and / or RX processor 258. In some aspects, the apparatus 1305 for wireless communication includes components for receiving from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery process for a period of time following a beam or link failure event, and / or components for avoiding abandoning or reallocating the beam or link during that duration, and other examples. In some aspects, apparatus 1305 may include components for receiving from the UE a message indicating information associated with one or more failure events experienced by the UE or occurring in a beam or link between the UE and a base station, and / or components for reconfiguring a recovery process of the UE based at least in part on the information associated with one or more failure events. The aforementioned components may be one or more of the aforementioned components of apparatus 1200 and / or processing system 1310 of apparatus 1305 configured to perform the functions described herein. As described elsewhere herein, processing system 1310 may include TX MIMO processor 230, receiver processor 238, and / or controller / processor 240. In one configuration, the aforementioned components may be TX MIMO processor 230, receiver processor 238, and / or controller / processor 240 configured to perform the functions and / or operations described herein.

[0195] supply Figure 13 As an example. Other examples may be combined with... Figure 13 The descriptions are different.

[0196] Figure 14 This is a diagram illustrating an example 1400 of the implementation of code and circuitry for device 1405. Device 1405 may be a base station.

[0197] like Figure 14 As further shown, the apparatus may include circuitry (circuit 1420) for receiving from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery process for a period of time following a beam or link failure event. For example, the apparatus may include circuitry enabling the apparatus to receive from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery process for a period of time following a beam or link failure event.

[0198] like Figure 14 As further shown, the apparatus may include circuitry (circuit 1425) for receiving from the UE a message indicating information associated with one or more fault events experienced by the UE or occurring in a beam or link between the UE and the base station. For example, the apparatus may include circuitry enabling the apparatus to receive from the UE a message indicating information associated with one or more fault events experienced by the UE or occurring in a beam or link between the UE and the base station.

[0199] like Figure 14 As further shown, the device may include circuitry (circuit 1430) for avoiding abandoning or reallocating a beam or link for a period of time. For example, the device may include circuitry that causes the device to avoid abandoning or reallocating a beam or link during that duration.

[0200] like Figure 14 As further shown, the apparatus may include circuitry (circuit 1435) for reconfiguring the recovery process of the UE based at least in part on information associated with one or more fault events. For example, the apparatus may include circuitry that enables the apparatus to reconfigure the recovery process of the UE based at least in part on information associated with one or more fault events.

[0201] like Figure 14 As further shown, the apparatus may include code (code 1440) stored in computer-readable medium 1325 for receiving from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery procedure for a period of time following a beam or link failure event. For example, the apparatus may include code, when executed by processor 1320, that causes processor 1320 to cause transceiver 1330 to receive from the UE a message instructing the UE to avoid (e.g., has already avoided or will avoid) performing a recovery procedure for a period of time following a beam or link failure event.

[0202] like Figure 14 As further shown, the apparatus may include code (code 1445) stored in computer-readable medium 1325 for receiving from the UE a message indicating information associated with one or more fault events experienced by the UE or with a beam or link between the UE and the base station. For example, the apparatus may include code, when executed by processor 1320, that causes processor 1320 to cause transceiver 1330 to receive from the UE a message indicating information associated with one or more fault events experienced by the UE or with a beam or link between the UE and the base station.

[0203] like Figure 14As further shown, the apparatus may include code (code 1450) stored in computer-readable medium 1325 for avoiding abandoning or reallocating beams or links during the duration configuration. For example, the apparatus may include code that, when executed by processor 1320, enables processor 1320 to avoid abandoning or reallocating beams or links during the duration.

[0204] like Figure 14 As further shown, the apparatus may include code (code 1455) stored in computer-readable medium 1325 for reconfiguring the recovery process of the UE based at least in part on information associated with one or more fault events. For example, the apparatus may include code, when executed by processor 1320, that enables processor 1320 to reconfigure the recovery process of the UE based at least in part on information associated with one or more fault events.

[0205] supply Figure 14 As an example. Other examples may be combined with... Figure 14 The descriptions are different.

[0206] Figure 15 This is a diagram illustrating an example process 1500 performed by a UE according to this disclosure. Example process 1500 is where the UE (e.g., Figure 1 and Figure 2 UE 120 depicted in Figure 1, UE 320 depicted in Figure 3, Figure 4 The example depicted is a UE 420 performing operations associated with beam suspension or link restoration in response to a fault event.

[0207] like Figure 15 As shown, in some aspects, process 1500 may include determining that a beam or link failure event between the UE and the base station is occurring or is about to occur (block 1510). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282) may determine that a beam or link failure event between the UE and the base station is occurring or is about to occur, as described above.

[0208] like Figure 15 As further shown, in some aspects, process 1500 may include sending a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time (block 1520). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282) may send a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time, as described above.

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

[0210] In the first aspect, the duration is based at least in part on the duration of one or more conditions that lead to the failure event.

[0211] In the second aspect, alone or in combination with the first aspect, one or more conditions leading to a failure event include one or more of the maximum permissible exposure limits for an object blocking the path of a beam or link and / or a person or part of a person in the path of a beam or link.

[0212] In the third aspect, either alone or in combination with one or more of the first and second aspects, the recovery process is the default recovery process.

[0213] In the fourth aspect, alone or in combination with one or more of the first to third aspects, the recovery process includes initiating the RACH process.

[0214] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1500 includes a cancellation recovery process.

[0215] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1500 includes modifying one or more parameters used for the recovery process.

[0216] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, one or more parameters include one or more of the following: the duration of the beam fault detection timer, the duration of the link fault detection timer, the maximum value of the beam fault indication counter, or the maximum value of the link fault indication counter.

[0217] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the message is one of an RRC message, a MAC-CE message, or a PUCCH message.

[0218] In the ninth aspect, sending a message to a base station, either alone or in combination with one or more of the first to eighth aspects, includes determining the type of the fault event based at least in part on information associated with the fault event, and sending the message based at least in part on the type of the fault event.

[0219] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, sending a message to the base station includes sending the message based at least in part on a determination of the probability that the UE will meet a threshold for maintaining a beam or link, the determination being based at least in part on the internal state of an algorithm for finding another beam or another link.

[0220] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, sending a message includes sending a message based at least in part on the determination that a failure event is about to occur.

[0221] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the message instructs the UE to avoid performing a recovery process for the duration of each of multiple failure events of the beam or link.

[0222] although Figure 15 An example box of process 1500 is shown, but in some aspects, process 1500 may include more than Figure 15 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 1500 may be executed in parallel.

[0223] Figure 16 This is a diagram illustrating an example process 1600 performed, for example, by a base station according to this disclosure. Example process 1600 is where a base station (e.g., Figure 1 and Figure 2 BS 110 depicted in Figure 2, BS 310 depicted in Figure 3, Figure 4 The example depicted in the text is of a BS 410 performing operations associated with beam suspension or link restoration in response to a failure event.

[0224] like Figure 16 As shown, in some aspects, process 1600 may include receiving from the UE a message indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event (block 1610). For example, the base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may receive from the UE a message indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event, as described above.

[0225] like Figure 16 As further shown, in some aspects, process 1600 may include avoiding abandoning or reallocating beams or links during this duration (block 1620). For example, a base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may avoid abandoning or reallocating beams or links during this duration, as described above.

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

[0227] In the first aspect, process 1600 includes avoiding sending data to the UE during the duration.

[0228] In the second aspect, either alone or in combination with the first aspect, the recovery process is the default process.

[0229] In the third aspect, either alone or in combination with one or more of the first and second aspects, the recovery process includes initiating a RACH process.

[0230] In the fourth aspect, alone or in combination with one or more of the first to third aspects, the message is one of an RRC message, MAC-CE, or PUCCH.

[0231] although Figure 16 An example box of process 1600 is shown, but in some aspects, process 1600 may include more than Figure 16 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 1600 may be executed in parallel.

[0232] Figure 17 This is a diagram illustrating an example process 1700 performed, for example, by a UE according to this disclosure. Example process 1700 is where the UE (e.g., Figure 1 and Figure 2 UE 120 depicted in Figure 1, UE 320 depicted in Figure 3, Figure 4 The example depicted is a UE 420 performing operations associated with beam suspension or link restoration in response to a fault event.

[0233] like Figure 17 As shown, in some aspects, process 1700 may include determining that one or more failure events of the beam or link between the UE and the base station have occurred (block 1710). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282) may determine that one or more failure events of the beam or link between the UE and the base station have occurred, as described above.

[0234] like Figure 17 As further shown, in some aspects, process 1700 may include sending a message to the base station indicating information associated with one or more fault events (block 1720). For example, the UE (e.g., using a receive processor 258, a transmit processor 264, a controller / processor 280, and a memory 282) may send a message to the base station indicating information associated with one or more fault events, as described above.

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

[0236] In the first aspect, one or more failure events are a single failure event, and the information includes the duration of the single failure event.

[0237] In the second aspect, either alone or in combination with the first aspect, one or more fault events are multiple fault events, and the information includes fault statistics for the multiple fault events.

[0238] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1700 includes modifying one or more parameters used for the recovery process after receiving the recovery process from the base station and then reconfiguring it.

[0239] although Figure 17 An example box of process 1700 is shown, but in some aspects, process 1700 may include more than Figure 17 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 1700 may be executed in parallel.

[0240] Figure 18 This is a diagram illustrating an example process 1800 performed, for example, by a base station according to this disclosure. Example process 1800 is where a base station (e.g., Figure 1 and Figure 2 BS 110 depicted in Figure 2, BS 310 depicted in Figure 3, Figure 4 The example depicted in the text is of a BS 410 performing operations associated with beam suspension or link restoration in response to a failure event.

[0241] like Figure 18 As shown, in some aspects, process 1800 may include receiving from the UE a message indicating information associated with one or more failure events occurring in a beam or link between the UE and the base station (block 1810). For example, the base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may receive from the user equipment (UE) a message indicating information associated with one or more failure events occurring in a beam or link between the UE and the base station, as described above.

[0242] like Figure 18As further shown, in some aspects, process 1800 may include reconfiguring the UE's recovery process at least in part based on information associated with one or more fault events (block 1820). For example, a base station (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242) may reconfigure the UE's recovery process at least in part based on information associated with one or more fault events, as described above.

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

[0244] In the first aspect, the reconfiguration recovery process includes updating one or more of the following: a fault timer, the maximum number of fault instances for the UE, or a combination of a fault timer and the maximum number of fault instances.

[0245] In the second aspect, alone or in combination with the first aspect, one or more failure events are a single failure event, and the information includes the duration of the single failure event.

[0246] In the third aspect, either alone or in combination with one or more of the first and second aspects, one or more fault events are multiple fault events, and the information includes fault statistics information of multiple fault events.

[0247] In the fourth aspect, alone or in combination with one or more of the first to third aspects, process 1800 includes accelerating a radio link failure timer based at least in part on beam failure indication.

[0248] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1800 includes sending a reconfiguration of the recovery process to the UE after receiving the message.

[0249] although Figure 18 An example box of process 1800 is shown, but in some aspects, process 1800 may include more than Figure 18 The boxes depicted may be more boxes, fewer boxes, different blocks, or boxes with different arrangements. Alternatively, two or more boxes of process 1800 may be executed in parallel. Figure 19 This is a diagram illustrating example 1900 of beam suspension or link restoration in response to a failure event according to this disclosure. Figure 19 As shown, a UE (e.g., UE 120, UE 320, UE 420) can communicate with a base station (e.g., BS 110, BS 310, BS 410) (e.g., sending uplink transmissions and / or receiving downlink transmissions). The UE and the base station can be part of a wireless network (e.g., wireless network 100) and can follow... Figure 5 Process 500 Figure 6 Process 600 Figure 7 Process 700 and Figure 8 The process described in process 800.

[0250] As shown by reference numeral 1905 in the attached figure, the base station can determine that the UE is experiencing or is about to experience a beam or link failure event. In some aspects, the UE can detect the failure event or receive information about the failure event.

[0251] As shown by reference numeral 1910 in the attached figure, the UE can send a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time. For example, the UE can send a message instructing the UE not to initiate a RACH procedure. As shown by reference numeral 1915 in the attached figure, the UE can avoid abandoning or reallocating beams or links.

[0252] As shown by reference numeral 1920 in the attached figure, the UE can determine that it has experienced one or more beam or link failure events. The UE may have avoided performing a recovery procedure. In some respects, if the failure event extends beyond that duration, the UE may perform a recovery procedure later.

[0253] As shown by reference numeral 1925 in the attached figure, the UE may send a message indicating information associated with one or more fault events. For example, the UE may collect information about fault events (e.g., blocking duration, number of failed instances of blocking duration) or statistical information about multiple fault events.

[0254] As shown by reference numeral 1930 in the attached figure, the base station may send a message to the UE to reconfigure the UE's recovery process based at least in part on information associated with one or more fault events. For example, the base station may adjust timers or counters associated with beam failures or radio link failures.

[0255] As mentioned above, providing Figure 19 As an example. Other examples may be related to... Figure 19 The descriptions are different.

[0256] Figure 20 This is a diagram illustrating an example 2000 of beam suspension or link restoration in response to a failure event according to this disclosure. (See diagram 2000) Figure 20 As shown, a UE (e.g., UE 120, UE 320, UE 420) can communicate with a base station (e.g., BS 110, BS 310, BS 410) (e.g., sending uplink transmissions and / or receiving downlink transmissions). The UE and the base station can be part of a wireless network (e.g., wireless network 100) and can follow... Figure 15 Process 1500 Figure 16Process 1600 Figure 17 Process 1700 and Figure 18 The process described in 1800.

[0257] As shown in the attached figure 2005, the base station can determine that a beam or link failure event between the UE and the base station is occurring or about to occur. In some aspects, the UE can detect the failure event or receive information about the failure event.

[0258] As shown in the attached figure 2010, the UE can send a message to the base station instructing the UE to avoid performing beam or link recovery procedures for a period of time. For example, the UE can send a message instructing the UE not to initiate a RACH procedure.

[0259] As shown in the attached figure 2015, the UE can avoid abandoning or reallocating a beam or link. For example, the UE can time a timer, stop the counter, or perform another action for another UE instead of discarding the beam or link to the UE.

[0260] As indicated by reference numeral 2020 in the attached figure, the UE can determine that one or more failure events of the beam or link between the UE and the base station have occurred. The UE may have avoided performing a recovery procedure. In some respects, if the failure event extends beyond this duration, the UE may perform a recovery procedure later.

[0261] As indicated by reference numeral 2025 in the accompanying drawings, the UE may send a message indicating information associated with one or more fault events. For example, the UE may collect information about fault events (e.g., blocking duration, number of failed instances of blocking duration) or statistical information about multiple fault events.

[0262] As shown by reference numeral 2030 in the attached figure, the base station may send a message to the UE reconfiguring the UE's recovery process based at least in part on information associated with one or more fault events. For example, the base station may adjust timers or counters associated with beam failures or radio link failures. The base station may also adjust the duration for which the UE avoids performing the recovery process.

[0263] As mentioned above, providing Figure 20 As an example. Other examples may be related to... Figure 20 The descriptions are different.

[0264] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from practice in these aspects.

[0265] The following provides an overview of some aspects of this disclosure:

[0266] Aspect 1: A method for wireless communication performed by a user equipment (UE), comprising: determining that the UE is experiencing or is about to experience a beam or link failure event; and sending a message to a base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0267] Aspect 2: According to the method of aspect 1, wherein the duration is based at least in part on the duration of one or more conditions that lead to the failure event.

[0268] Aspect 3: According to the method of aspect 1 or 2, one or more conditions leading to a failure event include one or more of the maximum permissible exposure limits of an object blocking the path of a beam or link or a person or part of a person in the path of a beam or link.

[0269] Aspect 4: Based on the method of any one of Aspects 1-3, where the recovery process is the default recovery process.

[0270] Aspect 5: According to the method of any one of Aspects 1-4, wherein the recovery process includes initiating a random access channel procedure.

[0271] Aspect 6: According to the methods of any one of Aspects 1-4, it also includes canceling the recovery process.

[0272] Aspect 7: According to the method of any one of Aspects 1-6, it also includes modifying the parameters used for the recovery process.

[0273] Aspect 8: According to the method of aspect 7, wherein the parameters include one or more of the following: the duration of the beam fault detection timer, the duration of the link fault detection timer, the maximum value of the beam fault indication counter, or the maximum value of the link fault indication counter.

[0274] Aspect 9: According to the method of any one of Aspects 1-8, wherein the message is one of a radio resource control message, a media access control element, or a physical uplink control channel message.

[0275] Aspect 10: The method according to any one of Aspects 1-9, wherein sending a message to the base station includes determining the type of the fault event based at least in part on information associated with the fault event, and sending the message based at least in part on the type of the fault event.

[0276] Aspect 11: The method according to any one of Aspects 1-10, wherein sending a message to the base station includes sending the message based at least in part on a determination of the probability that the UE will meet a threshold for maintaining a beam or link, the determination being based at least in part on the internal state of an algorithm for finding another beam or another link.

[0277] Aspect 12: The method according to any one of Aspects 1-11, wherein sending a message includes sending the message based at least in part on the determination that the UE is about to experience a fault event.

[0278] Aspect 13: The method according to any one of aspects 1-12, wherein the message indicates that the UE may avoid performing the recovery process for the duration of each of a plurality of failure events of the beam or link.

[0279] Aspect 14: A method of wireless communication performed by a base station, comprising: receiving a message from a user equipment (UE) instructing the UE to avoid performing a recovery process for a period of time following a beam or link failure event; and avoiding abandoning or reallocating the beam or link during the duration of such duration.

[0280] Aspect 15: The method according to aspect 14 also includes avoiding sending data to the UE during the duration.

[0281] Aspect 16: According to the method of Aspect 14 or 15, the recovery process is the default process.

[0282] Aspect 17: According to the method of any one of Aspects 14-16, the recovery process includes initiating a random access channel procedure.

[0283] Aspect 18: According to the method of any one of Aspects 14-17, the message is one of a radio resource control message, a media access control element, or a physical uplink control channel message.

[0284] Aspect 19: A method of wireless communication performed by a user equipment (UE), comprising: determining that the UE has experienced one or more failure events of a beam or link; and sending a message to a base station indicating information associated with the one or more failure events.

[0285] Aspect 20: According to the method of aspect 19, wherein the one or more fault events are a single fault event, and the information is the fault duration of the single fault event.

[0286] Aspect 21: According to the method of aspect 19, wherein the one or more fault events are multiple fault events, and the information is fault statistics information of the multiple fault events.

[0287] Aspect 22: A method of wireless communication performed by a base station, comprising: receiving from a user equipment (UE) a message indicating information associated with one or more failure events of the UE for a beam or link; and reconfiguring a recovery process of the UE based at least in part on the information associated with the one or more failure events.

[0288] Aspect 23: According to the method of aspect 22, the reconfiguration recovery process includes updating one or more of the following: a fault timer, a maximum fault instance count of the UE, or a combination of a fault timer and a maximum fault instance count.

[0289] Aspect 24: According to the method of aspect 22 or 23, wherein the one or more fault events are a single fault event, and the information is the fault duration of the single fault event.

[0290] Aspect 25: According to the method of aspect 22 or 23, wherein the one or more fault events are multiple fault events, and the information is fault statistics information of the multiple fault events.

[0291] Aspect 26: The method according to any one of aspects 22-25 further includes determining whether to accelerate the radio link failure timer based at least in part on beam failure indication.

[0292] Aspect 27: An apparatus for wireless communication at a device, 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 one or more of the methods of aspects 1-26.

[0293] Aspect 28: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 1-26.

[0294] Aspect 29: An apparatus for wireless communication, comprising at least one component for performing the methods of one or more aspects of aspects 1-26.

[0295] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more aspects of aspects 1-26.

[0296] Aspect 31: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 1-26.

[0297] The following provides an overview of some other aspects of this disclosure:

[0298] Aspect 32: A method for wireless communication performed by a user equipment (UE), comprising: determining that a beam or link failure event between the UE and a base station is occurring or is about to occur; and sending a message to the base station instructing the UE to avoid performing a beam or link recovery process for a period of time.

[0299] Aspect 33: According to the method of aspect 32, wherein the duration is based at least in part on the duration of one or more conditions that lead to the failure event.

[0300] Aspect 34: According to the method of Aspect 32 or 33, the recovery process is the default recovery process.

[0301] Aspect 35: According to the method of any one of aspects 32-34, the recovery process includes initiating a random access channel procedure.

[0302] Aspect 36: According to the methods of any of Aspects 32-34, the recovery process can also be cancelled.

[0303] Aspect 37: The method according to any one of aspects 32-36 also includes modifying the parameters used in the recovery process.

[0304] Aspect 38: The method according to aspect 37, wherein the parameters include one or more of the following: the duration of the beam fault detection timer, the duration of the link fault detection timer, the maximum value of the beam fault indication counter, or the maximum value of the link fault indication counter.

[0305] Aspect 39: According to the method of any one of Aspects 32-38, the message is one of a radio resource control message, a media access control element (MAC-CE) or a physical uplink control channel message.

[0306] Aspect 40: The method according to any one of aspects 32-39, wherein sending a message to the base station includes determining the type of the fault event based at least in part on information associated with the fault event, and sending the message based at least in part on the type of the fault event.

[0307] Aspect 41: The method according to any one of aspects 32-40, wherein sending a message to the base station includes sending the message based at least in part on a determination of the probability that the UE will meet a threshold for maintaining a beam or link, the determination being based at least in part on the internal state of an algorithm for finding another beam or another link.

[0308] Aspect 42: The method according to any one of aspects 32-41, wherein sending a message includes sending the message based at least in part on the determination that a failure event is about to occur.

[0309] Aspect 43: The method according to any one of aspects 32-42, wherein the message indicates that the UE may avoid performing a recovery procedure for the duration of each of a plurality of failure events of the beam or link.

[0310] Aspect 44: A method of wireless communication performed by a base station, comprising: receiving a message from a user equipment (UE) indicating that the UE has avoided or will avoid performing a recovery process for a period of time following a beam or link failure event; and avoiding abandoning or reallocating the beam or link during the duration of such duration.

[0311] Aspect 45: The method according to aspect 44 also includes avoiding sending data to the UE during the duration.

[0312] Aspect 46: According to the method of Aspect 44 or 45, the recovery process is the default process.

[0313] Aspect 47: According to the method of any one of aspects 44-46, the recovery process includes initiating a random access channel procedure.

[0314] Aspect 48: According to the method of any one of Aspects 44-47, the message is one of a radio resource control message, a media access control element (MAC-CE) or a physical uplink control channel message.

[0315] Aspect 49: A method of wireless communication performed by a user equipment (UE), comprising: determining that one or more failure events of a beam or link between the UE and a base station have occurred; and sending a message to the base station indicating information associated with the one or more failure events.

[0316] Aspect 50: According to the method of aspect 49, one or more failure events are a single failure event, and the information includes the failure duration of the single failure event.

[0317] Aspect 51: According to the method of aspect 49, one or more fault events are multiple fault events, and the information includes fault statistics information of multiple fault events.

[0318] Aspect 52: The method according to any one of aspects 49-51 further includes modifying one or more parameters used for the recovery process after receiving the reconfiguration of the recovery process from the base station.

[0319] Aspect 53: A method of wireless communication performed by a base station, comprising: receiving from a user equipment (UE) a message indicating information associated with one or more failure events occurring in a beam or link between the UE and the base station; and reconfiguring a recovery process of the UE based at least in part on the information associated with the one or more failure events.

[0320] Aspect 54: According to the method of aspect 53, the reconfiguration recovery process includes updating one or more of the following: a fault timer, a maximum fault instance count of the UE, or a combination of a fault timer and a maximum fault instance count.

[0321] Aspect 55: According to the method of Aspect 53 or 54, one or more failure events are a single failure event, and the information includes the failure duration of the single failure event.

[0322] Aspect 56: According to the method of Aspect 53 or 54, one or more fault events are multiple fault events, and the information includes fault statistics of multiple fault events.

[0323] Aspect 57: The method according to any one of aspects 53-56 further includes at least in part an accelerated radio link failure timer based on beam failure indication.

[0324] Aspect 58: The method according to any one of aspects 53-57 further includes sending a reconfiguration of the recovery procedure to the UE after receiving the message.

[0325] Aspect 59: An apparatus for wireless communication at a device, 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 one or more of the methods of aspects 32-58.

[0326] Aspect 60: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 32-58.

[0327] Aspect 61: An apparatus for wireless communication, comprising at least one component for performing the methods of one or more aspects of aspects 32-58.

[0328] Aspect 62: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more aspects of aspects 32-58.

[0329] Aspect 63: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 32-58.

[0330] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented as a combination of hardware, firmware, and / or hardware and software.

[0331] It is evident that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to any specific software code—it should be understood that software and hardware can be designed to implement the systems and / or methods, at least in part, based on the descriptions herein.

[0332] As used in this article, depending on the context, a threshold can refer to a value that is 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, and / or not equal to the threshold.

[0333] Even if a specific combination of features is recited in the claims and / or specification, such combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or not disclosed in the specification. Although each dependent claim listed below may depend directly on only one claim, the disclosure of aspects includes every dependent claim in combination with every other claim in the claim set. As used herein, the phrase “at least one” in the list of items refers to any combination of those items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0334] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more referenced items in relation to the article “the” and is interchangeable with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items) and are interchangeable with “one or more.” Figure 1In cases involving items, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms. Additionally, unless explicitly stated otherwise, the phrase “based on” means “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be included when used in a series and may be used interchangeably with “and / or” unless explicitly stated otherwise (e.g., if used in combination with “any” or “only one of them”).

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors are coupled to the memory, said one or more processors being configured to: Determine whether a beam or link failure event between the UE and the network entity is occurring or about to occur; as well as Send a message to the network entity instructing the UE to avoid performing the recovery process of the beam or the link for a period of time.

2. The UE of claim 1, wherein the time period is at least in part based on the duration of one or more conditions associated with the fault event.

3. The UE of claim 2, wherein the one or more conditions associated with the fault event include one or more of the maximum permissible exposure limits for an object associated with the path of the beam or the link, or for a person or part of a person in the path of the beam or the link.

4. The UE according to claim 1, wherein the recovery process is a default recovery process.

5. The UE of claim 1, further comprising: A transceiver, wherein the recovery process includes the initiation of a random access channel procedure.

6. The UE of claim 1, wherein the one or more processors are further configured to cancel the recovery process.

7. The UE of claim 1, wherein the one or more processors are further configured to modify one or more parameters for the recovery process.

8. The UE of claim 7, wherein the one or more parameters include one or more of the following: the duration of a beam fault detection timer, the duration of a link fault detection timer, the maximum value of a beam fault indication counter, or the maximum value of a link fault indication counter.

9. The UE according to claim 1, wherein the message is one of a radio resource control message, a media access control element MAC-CE, or a physical uplink control channel message.

10. The UE of claim 1, wherein, To send the message to the network entity, the one or more processors are configured to: The type of the failure event is determined at least in part based on information associated with the failure event; as well as The message is sent based at least in part on the type of the failure event.

11. The UE of claim 1, wherein, To send the message to the network entity, the one or more processors are configured to: The message is sent at least in part based on a determination that the UE will meet a threshold probability of maintaining the beam or the link, the determination being at least in part based on the internal state of an algorithm for finding another beam or another link.

12. The UE of claim 1, wherein, for sending the message, the one or more processors are configured to: The message is sent based at least in part on the determination that the failure event is about to occur.

13. The UE of claim 1, wherein the message indicates that the UE is able to avoid the execution of the recovery process for each of a plurality of failure events of the beam or the link during the time period.

14. The UE according to claim 1, The fault event is specific to the beam, and The recovery process described therein is for the beam.

15. The UE according to claim 1, The fault event is specific to the link, and The recovery process described therein is for the link.

16. A network entity for wireless communication, comprising: Memory; as well as One or more processors are coupled to the memory, said one or more processors being configured to: Receive a message indicating that the user equipment (UE) has avoided or will avoid performing a recovery procedure for a period of time following a beam or link failure event; and Avoid abandoning or redistributing the beam or the link during the specified period.

17. The network entity of claim 16, wherein the one or more processors are further configured to avoid sending data to the UE during the said time period.

18. The network entity of claim 16, wherein the recovery process is a default process.

19. The network entity of claim 16, wherein the recovery process includes initiating a random access channel procedure.

20. The network entity of claim 16, wherein the message is one of a radio resource control message, a media access control element MAC-CE, or a physical uplink control channel message.

21. The network entity of claim 16, wherein, The fault event is specific to the beam.

22. The network entity of claim 16, wherein, The fault event is specific to the link.

23. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as One or more processors, coupled to the memory, are configured to cause the UE to: Determine the occurrence of one or more failure events of the beam or link between the UE and the network entity; as well as Send a message to the network entity, the message indicating: The recovery process will be paused for a period of time, and Information associated with the one or more failure events, wherein the information associated with the one or more failure events includes one of the following: Information about the number of failed instances during the blocking duration, or One or more statistical information on multiple fault events, wherein the multiple fault events include the one or more fault events; as well as The receiving recovery process is reconfigured based on information associated with the one or more fault events, and includes a first adjustment to the duration of the beam fault detection timer, a second adjustment to the maximum value of the beam instance counter, or a first adjustment to the duration of the beam fault detection timer and a second adjustment to the maximum value of the beam instance counter.

24. The apparatus of claim 23, wherein the information associated with the one or more fault events includes one or more statistical information of the plurality of fault events.

25. The apparatus of claim 23, wherein the message is sent after each of the plurality of fault events.

26. The apparatus of claim 23, wherein the message is sent after the plurality of fault events have occurred.

27. The apparatus of claim 23, wherein the one or more processors are further configured to cause the UE to: A connection to the network entity is established via a beam or link.

28. The apparatus of claim 23, wherein the information associated with the one or more fault events further includes information identifying the duration of the obstruction.

29. The apparatus of claim 23, wherein, in order to receive the reconfiguration, the one or more processors are configured to cause the UE to: Receive the reconfiguration from the network entity.

30. The apparatus of claim 23, wherein the one or more processors are further configured to cause the UE to: The parameters used for the recovery process are modified, at least in part, based on the reconfiguration.

31. The apparatus of claim 30, wherein, in order to modify parameters for the recovery process, the one or more processors are configured to cause the UE to: Increase the maximum value of the beam instance counter, or / and Increase the duration of the beam fault detection timer.

32. A network entity for wireless communication, comprising: Memory; as well as One or more processors are coupled to the memory, said one or more processors being configured to: Receive a message from the user equipment (UE) indicating information associated with one or more failure events of a beam or link between the UE and the network entity; as well as The recovery process of the UE is reconfigured at least in part based on the information associated with the one or more failure events. The one or more failure events are single failure events, and the information includes the duration of the single failure event.

33. The network entity of claim 32, wherein, When the recovery process is reconfigured, the memory and the one or more processors are configured to update one or more of the fault timer, the maximum number of fault instances of the UE, or a combination of the fault timer and the maximum number of fault instances.

34. The network entity of claim 32, wherein the one or more fault events are multiple fault events, and the information includes fault statistics information of the multiple fault events.

35. The network entity of claim 32, wherein the memory and the one or more processors are further configured to accelerate a radio link failure timer based at least in part on a beam failure indication.

36. The network entity of claim 32, wherein the memory and the one or more processors are configured to send a reconfiguration of the recovery process to the UE after receiving the message.

37. A method for wireless communication performed at a user equipment (UE), comprising: Determine whether a beam or link failure event between the UE and the network entity is occurring or about to occur; as well as A message is sent to the network entity instructing the UE to avoid performing the beam or link recovery process for a period of time.

38. The method of claim 37, wherein the time period is at least in part based on the duration of one or more conditions associated with the failure event.

39. The method of claim 38, wherein the one or more conditions associated with the failure event include one or more of the maximum permissible exposure limits for objects associated with the path of the beam or the link, or for people or parts of people in the path of the beam or the link.

40. The method of claim 37, wherein the recovery process includes initiating a random access channel procedure.

41. The method of claim 37, wherein, The message instructs the UE to avoid performing the recovery process for each of the multiple failure events of the beam or the link within the specified time period.

42. The method of claim 37, wherein the recovery process is a default recovery process.

43. The method of claim 37, further comprising: Cancel the recovery process.

44. The method of claim 37, further comprising: Modify one or more parameters of the recovery process.

45. The method of claim 44, wherein, The one or more parameters include one or more of the following: the duration of the beam fault detection timer, the duration of the link fault detection timer, the maximum value of the beam fault indicator counter, or the maximum value of the link fault indicator counter.

46. The method of claim 37, wherein, The message is one of the following: a radio resource control message, a media access control element MAC-CE, or a physical uplink control channel message.

47. The method of claim 37, wherein sending the message to the network entity comprises: The type of the failure event is determined at least in part based on information associated with the failure event; as well as The message is sent based at least in part on the type of the failure event.

48. The method of claim 37, wherein sending the message to the network entity comprises: The message is sent at least in part based on a determination that the UE will meet a threshold probability of maintaining the beam or the link, the determination being at least in part based on the internal state of an algorithm for finding another beam or another link.

49. The method of claim 37, wherein sending the message comprises: The message is sent based at least in part on the determination that a failure event is about to occur.

50. The method of claim 37, The fault event is specific to the beam, and The recovery process described therein is for the beam.

51. The method of claim 37, The fault event is specific to the link, and The recovery process described therein is for the link.

52. A method for wireless communication performed at a user equipment (UE), comprising: Determine the occurrence of one or more failure events of the beam or link between the UE and the network entity; Send a message to the network entity, the message indicating: The recovery process will be paused for a period of time, and Information associated with one or more failure events, wherein the information associated with said one or more failure events includes one of the following: Information about the number of failed instances during the blocking duration, or One or more statistical information on multiple fault events, wherein the multiple fault events include the one or more fault events; as well as The receiver reconfigured the recovery process, the reconfiguration being based on information associated with the one or more fault events, and including a first adjustment to the duration of the beam fault detection timer, a second adjustment to the maximum value of the beam instance counter, or a first adjustment to the duration of the beam fault detection timer and a second adjustment to the maximum value of the beam instance counter.

53. The method of claim 52, wherein the information associated with the one or more fault events includes one or more statistical information of the plurality of fault events.

54. The method of claim 52, wherein the message is sent after each of the plurality of fault events.

55. The method of claim 52, wherein the message is sent after the plurality of fault events have occurred.

56. The method of claim 52, further comprising: A connection to the network entity is established via the beam or link.

57. The method of claim 52, wherein the information associated with the one or more fault events further includes information identifying the duration of the blockage.

58. The method of claim 52, wherein receiving the reconfiguration comprises: Receive the reconfiguration from the network entity.

59. The method of claim 52, further comprising: The parameters used for the recovery process are modified, at least in part, based on the reconfiguration.

60. The method of claim 59, wherein modifying the parameters used in the recovery process includes one or more of the following: Increase the maximum value of the beam instance counter, or Increase the duration of the beam fault detection timer.

61. A method for wireless communication performed at a network entity, comprising: Receive a message indicating that the user equipment (UE) has avoided or will avoid performing a recovery process for a period of time after a beam or link failure event; as well as Avoid abandoning or redistributing beams or links during the specified period.

62. The method of claim 61, wherein, The recovery process includes initiating a random access channel procedure.

63. The method of claim 61, wherein, The message is one of the following: a radio resource control message, a media access control element MAC-CE, or a physical uplink control channel message.

64. The method of claim 61, further comprising: Data is avoided being sent to the UE during the specified period.

65. The method of claim 61, wherein, The recovery process described is the default process.

66. The method of claim 61, wherein the fault event is directed at the beam.

67. The method of claim 61, wherein the fault event is specific to the link.

68. An apparatus for wireless communication, comprising: Components for performing the steps of the method according to any one of claims 37-60.

69. An apparatus for wireless communication, comprising: Components for performing the steps of the method according to any one of claims 61-67.

70. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform the method according to any one of claims 37-60.

71. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a network entity, cause the network entity to perform the method according to any one of claims 61-67.

72. A computer product comprising instructions which, when executed by a processor of a user equipment (UE), cause the UE to perform the method according to any one of claims 37-60.

73. A computer product comprising instructions which, when executed by a processor of a network entity, cause the network entity to perform the method according to any one of claims 61-67.

Images