Power savings after beam failure recovery requests

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a mobile station may detect a beam failure associated with a beam used to communicate with a network node. The mobile station may send a beam failure recovery (BFR) request to the network node based at least in part on the beam failure. The mobile station may prevent monitoring of one or more control channels associated with the beam failure after sending the BFR request. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus associated with power conservation following a beam failure recovery (BFR) request. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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 set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include detecting, by the mobile station, a beam failure associated with a beam used to communicate with a network node. The method may include sending, by the mobile station, a beam failure recovery (BFR) request to the network node based at least in part on the beam failure. The method may include refraining, by the mobile station from monitoring one or more control channels associated with the beam failure after sending the BFR request.

[0006] Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to detect a beam failure associated with a beam used to communicate with a network node. The one or more processors may be configured to send a BFR request to the network node based at least in part on the beam failure. The one or more processors may be configured to refrain from monitoring one or more control channels associated with the beam failure after sending the BFR request.

[0007] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a mobile station. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to detect a beam failure associated with a beam used to communicate with a network node. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to send a BFR request to the network node based at least in part on the beam failure. The instruction set, when executed by one or more processors of the mobile station, may cause the mobile station to refrain from monitoring one or more control channels associated with the beam failure after sending the BFR request.

[0008] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for detecting a beam failure associated with a beam used to communicate with a network node. The apparatus may include means for sending a BFR request to the network node based at least in part on the beam failure. The apparatus may include means for refraining from monitoring one or more control channels associated with the beam failure after sending the BFR request.

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

[0010] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

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

[0012] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

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

[0016] Figure 4 is a diagram illustrating an example resource structure for wireless communication according to the present disclosure.

[0017] Figure 5 is a diagram illustrating an example of transmit reception point (TRP) differentiation at a UE based at least in part on a control resource set (CORESET) pool index according to the present disclosure.

[0018] Figure 6 is a diagram illustrating an example of a beam management procedure based on downlink reference signal transmission according to the present disclosure.

[0019] Figure 7 is a diagram illustrating an example associated with power saving after a beam failure recovery (BFR) request according to the present disclosure.

[0020] Figure 8 is a diagram illustrating an example process associated with power conservation following a BFR request according to the present disclosure.

[0021] Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0022] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

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

[0024] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or 5G and beyond (e.g., 6G) RATs.

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

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

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

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

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

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

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

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

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

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

[0035] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. 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, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0036] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0037] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the characteristics of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as 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.

[0038] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may 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. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0039] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, communication manager 140 may detect a beam failure associated with a beam used to communicate with network node 110; send a beam failure recovery (BFR) request to network node 110 based at least in part on the beam failure; and, after sending the BFR request, refrain from monitoring one or more control channels associated with the beam failure. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0040] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

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

[0042] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may 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 signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

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

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

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

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

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

[0048] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the BFR request may perform one or more techniques associated with power saving after the BFR request, as described in more detail elsewhere herein. In some aspects, the mobile station described herein is a UE 120, is included in a UE 120, or includes Figure 2 One or more components of the UE 120 shown. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 800 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion and / or interpretation), may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0049] In some aspects, the mobile station includes means for detecting a beam failure associated with a beam used to communicate with the network node 110; means for sending a BFR request to the network node 110 based at least in part on the beam failure; and / or means for refraining from monitoring one or more control channels associated with the beam failure after sending the BFR request. In some aspects, means for the mobile station to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

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

[0051] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0052] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

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

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

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

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

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

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

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

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

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

[0063] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0064] Figure 4 4 is a diagram illustrating an example resource structure 400 for wireless communication according to the present disclosure. Resource structure 400 shows examples of various resource groups described herein. As shown, resource structure 400 may include subframe 405. Subframe 405 may include multiple time slots 410. Although resource structure 400 is shown as including 2 time slots per subframe, a different number of time slots (e.g., 4 time slots, 8 time slots, 16 time slots, 32 time slots, or another number of time slots) may be included in a subframe. In some aspects, different types of transmit time intervals (TTIs) may be used in addition to subframes and / or time slots. Time slot 410 may include multiple symbols 415, such as 14 symbols per time slot.

[0065] The potential control region of the time slot 410 may be referred to as a control resource set (CORESET) 420, and may be configured to support efficient use of resources, such as by flexibly configuring or reconfiguring the resources of the CORESET 420 using a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH). In some aspects, the CORESET 420 may occupy the first symbol 415 of the time slot 410, the first two symbols 415 of the time slot 410, or the first three symbols 415 of the time slot 410. Thus, the CORESET 420 may include multiple resource blocks (RBs) in the frequency domain, and one, two, or three symbols 415 in the time domain. In a 5G network, the number of resources included in the CORESET 420 may be flexibly configured (such as by using RRC signaling to indicate the frequency domain region (e.g., the number of RBs) and / or the time domain region (e.g., the number of symbols) of the CORESET 420).

[0066] As illustrated, a symbol 415 including a CORESET 420 may include one or more control channel elements (CCEs) 425 (shown as two CCEs 425 in the illustrated example) across a portion of the system bandwidth. The CCEs 425 may include downlink control information (DCI) for providing control information for wireless communications. A network node may include multiple CCEs 425 (such as Figure 4 ), where the number of CCEs 425 used for DCI transmission represents the aggregation level (AL) used by the network node for DCI transmission. Figure 4 4, an aggregation level of two is shown as an example, which corresponds to two CCEs 425 in time slot 410. In some aspects, a different aggregation level may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

[0067] Each CCE 425 may include a fixed number of resource element groups (REGs) 430 (shown as 6 REGs 430), or may include a variable number of REGs 430. In some aspects, the number of REGs 430 included in a CCE 425 may be specified by a REG cluster size. A REG 430 may include one RB, which may include 12 resource elements (REs) 435 within a symbol 415. A RE 435 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0068] The search space may include all possible locations where the PDCCH may be located (e.g., in the time domain and / or frequency domain). CORESET 420 may include one or more search spaces, such as a UE-specific search space, a group common search space, a common search space, and / or a BFR search space, etc. The search space may indicate a set of CCE positions in which the UE may find a PDCCH that may potentially carry control information sent to the UE. The possible locations of the PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group common PDCCH (e.g., for multiple UEs), and / or the aggregation level being used. The possible locations of the PDCCH (e.g., in the time domain and / or frequency domain) may be referred to as PDCCH candidates, and the set of all possible PDCCH locations at the aggregation level may be referred to as a search space. For example, the set of all possible PDCCH locations for a specific UE may be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH locations for all UEs may be referred to as a common search space. The set of all possible PDCCH locations for a specific UE group may be referred to as a group common search space. One or more search spaces across aggregation levels may be referred to as a search space (SS) set.

[0069] The CORESET 420 may be interleaved or non-interleaved. An interleaved CORESET 420 may have a CCE to REG mapping such that adjacent CCEs are mapped to scattered REG bundles in the frequency domain (e.g., adjacent CCEs are not mapped to continuous REG bundles of the CORESET 420). A non-interleaved CORESET 420 may have a CCE to REG mapping such that all CCEs are mapped to continuous REG bundles of the CORESET 420 (e.g., in the frequency domain).

[0070] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0071] Figure 5 5 is a diagram illustrating an example 500 of TRP differentiation at a UE based at least in part on a CORESET pool index in accordance with the present disclosure. In some aspects, a CORESET pool index (or CORESETPoolIndex) value may be used by a UE (e.g., UE 120) to identify a TRP associated with an uplink grant received on a PDCCH. Additionally or alternatively, in some aspects, a UE may use a CORESET group or CORESET list value to identify a TRP associated with an uplink grant received on a PDCCH.

[0072] like Figure 5As illustrated, UE 120 may be configured to have multiple CORESETs in a given serving cell. Each CORESET configured for UE 120 may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for UE 120 may be associated with CORESET ID 1, a second CORESET configured for UE 120 may be associated with CORESET ID 2, a third CORESET configured for UE 120 may be associated with CORESET ID 3, and a fourth CORESET configured for UE 120 may be associated with CORESET ID 4.

[0073] like Figure 5 As further illustrated, two or more (e.g., up to five) CORESETs may be grouped into CORESET pools. Each CORESET pool may be associated with a CORESET pool index. For example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP (mTRP) configuration, each CORESET pool index value may be associated with a particular TRP 505. For example, and as Figure 5 As illustrated, a first TRP 505 (TRP A) (or a first network node 110, such as a first RU or a first DU associated with a CU) may be associated with a CORESET pool index of 0, and a second TRP 505 (TRP B) (or a second network node 110, such as a second RU or a second DU associated with a CU) may be associated with a CORESET pool index of 1. The UE 120 may be configured with information identifying an association between the TRP 505 and the CORESET pool index value assigned to the TRP 505 through a higher layer parameter, such as a PDCCH-Config. Thus, the UE 120 may identify the TRP 505 that sent the DCI message carrying the uplink grant by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI message was sent, determining the CORESET pool index value associated with the CORESET pool in which the CORESET ID is included, and identifying the TRP 505 associated with the CORESET pool index value.

[0074] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0075] Figure 6600, 610, and 620 are diagrams illustrating examples of beam management procedures based on downlink reference signal transmission according to the present disclosure. Figure 6 As shown, examples 600, 610, and 620 include UE 120 communicating with network node 110 in a wireless network (eg, wireless network 100). Figure 6 The devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and TRP, DU or RU, between mobile terminal nodes and control nodes, between IAB child nodes and IAB parent nodes, and / or between scheduled nodes and scheduling nodes). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., RRC connected state) when performing beam management procedures.

[0076] like Figure 6 As shown, example 600 may include network node 110 and UE 120 communicating to perform beam management using synchronization signal block (SSB) transmission or channel state information reference signal (CSI-RS) transmission. Example 600 depicts a first beam management procedure (e.g., P1 beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam scanning procedure, a cell search procedure, and / or a beam search procedure. Figure 6 As shown in example 600, during the first beam management procedure, the SSB and / or CSI-RS may be configured to be sent from the network node 110 to the UE 120. For example, the SSB sent by the network node 110 is a single-rank (rank 1) periodic reference signal that is always sent by the network node 110 to enable initial network acquisition and synchronization in addition to beam selection and beam management. For example, an identifier associated with the SSB may have a one-to-one mapping to a transmit beam used by the network node 110, and the one-to-one mapping may not change over time (e.g., be static). Additionally or alternatively, in the case where the CSI-RS is sent for the first beam management procedure, the CSI-RS for beam selection or beam management may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using MAC control element (MAC-CE) signaling) and / or aperiodic (e.g., using DCI).

[0077] The first beam management procedure may include the network node 110 performing beam scanning on multiple transmit (Tx) beams. The network node 110 may transmit an SSB or CSI-RS using each transmit beam used for beam management. In order to enable the UE 120 to perform receive (Rx) beam scanning, the network node 110 may transmit each SSB or CSI-RS multiple times within the same reference signal resource set (e.g., using repetition) using the transmit beam, so that the UE 120 may perform beam scanning on multiple receive beams in multiple transmit instances. For example, in a situation where the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the SSB or CSI-RS may be transmitted M times on each of the N transmit beams, so that the UE 120 may receive M instances of the SSB or CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam scanning on the receive beam of the UE 120. Thus, the first beam management procedure may enable UE 120 to measure SSB or CSI-RS on different transmit beams using different receive beams to support selection of one or more transmit / receive beam pairs (e.g., pairings between transmit beams of network node 110 and receive beams of UE 120). UE 120 may report the measurements to network node 110 to enable network node 110 to select one or more beam pairs for communication between network node 110 and UE 120.

[0078] like Figure 6 As shown, example 610 may include network node 110 and UE 120 communicating to perform beam management using SSB transmission or CSI-RS transmission. Example 610 depicts a second beam management procedure (e.g., P2 beam management). The second beam management procedure may be referred to as a beam refinement procedure, a base station beam refinement procedure, a network node beam refinement procedure, and / or a transmit beam refinement procedure, etc. Figure 6As shown in example 610, SSBs and / or CSI-RSs may be configured to be sent from the network node 110 to the UE 120. The SSBs may be periodic, and the CSI-RSs may be configured to be aperiodic (e.g., using DCI). The second beam management procedure may include the network node 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (e.g., determined based at least in part on measurements reported by the UE 120 in conjunction with the first beam management procedure). The network node 110 may transmit the SSB or CSI-RS using each of the one or more transmit beams used for beam management. The UE 120 may measure each SSB or CSI-RS using a single (e.g., identical) receive beam (e.g., determined based at least in part on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable the network node 110 to select the best transmit beam based at least in part on measurements of SSB and / or CSI-RS reported by the UE 120 (eg, measured by the UE 120 using a single receive beam).

[0079] like Figure 6 As shown, example 620 depicts a third beam management procedure (e.g., P3 beam management). The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, a receive beam refinement procedure, and / or a UE beam management procedure, etc. Figure 6As shown in example 620, one or more SSBs or CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The SSBs may be configured to be periodic, and the CSI-RSs may be configured to be aperiodic (e.g., using DCI). The third beam management procedure may include the network node 110 transmitting the one or more SSBs or CSI-RSs using a single transmit beam (e.g., determined at least in part based on measurements reported by the UE 120 in conjunction with the first beam management procedure and / or the second beam management procedure). In order to enable the UE 120 to perform receive beam scanning, the network node 110 may transmit the SSBs or CSI-RSs multiple times in the same reference signal resource set (e.g., using repetition) using the transmit beam, so that the UE 120 may scan the one or more receive beams one by one in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure and / or the second beam management procedure). The third beam management procedure may enable UE 120 to select the best receive beam based at least in part on measurements of the SSB or CSI-RS, and / or may enable network node 110 to select the best receive beam for UE 120 based at least in part on reported measurements received from UE 120 (e.g., measurements of the SSB and / or CSI-RS using the one or more receive beams).

[0080] In some cases, the UE 120 and the network node 110 may use beamforming to improve the performance associated with downlink and / or uplink communications over millimeter wave (mmW) channels. For example, mmW channels (e.g., in FR2 and / or FR4) may suffer from high propagation losses because mmW signals have higher frequencies and shorter wavelengths than various other radio waves used for communication (e.g., communications below 6 GHz in FR1). Therefore, mmW signals generally have shorter propagation distances, may suffer from atmospheric attenuation, and / or may be more easily blocked and / or suffer from penetration losses through objects or other obstacles, etc. For example, mmW signals may be reflected by lamp posts, vehicles, glass / windows, and / or metal objects, may be diffracted by the edges or corners of buildings and / or walls, and / or may be scattered via irregular objects such as walls and / or human bodies (e.g., a hand blocking an antenna module when the device is operating in a gaming mode). Therefore, beamforming may be used at both the UE 120 and the network node 110 to combat propagation losses in mmW channels and thereby improve the performance of mmW communications. For example, to achieve beamforming gain on the downlink, network node 110 may generate a downlink transmit beam steered in a particular direction, and UE 120 may generate a corresponding downlink receive beam. Similarly, to achieve beamforming gain on the uplink, UE 120 may generate an uplink transmit beam steered in a particular direction, and network node 110 may generate a corresponding uplink receive beam. In some cases, UE 120 may be permitted to select a downlink receive beam to optimize reception of downlink transmissions from network node 110, and / or may be permitted to select an uplink transmit beam to optimize reception of uplink transmissions made by UE 120 at network node 110.

[0081] However, in some cases (e.g., when the UE 120 is indoors or moving), the radio link between the UE 120 and the network node 110 may be susceptible to blocking and / or degradation, which may result in a sudden interruption resulting in a beam failure. For example, a radio link failure (RLF) occurs in a multi-beam scenario when a radio problem within a cell cannot be resolved by a recovery procedure, or when the UE 120 cannot find any suitable beam to initiate a random access procedure and successfully recover a failed connection between the UE 120 and the network node 110. On the other hand, a beam failure occurs when the UE 120 has lost a link via a current serving beam (e.g., based on a measurement associated with the current serving beam failing to meet a threshold), but the UE 120 is able to perform a successful random access procedure using another beam to reestablish a (temporarily lost) connection with the network node 110. Therefore, in some aspects, the UE 120 may be configured with one or more resources to enable beam failure detection, whereby the UE 120 may measure or detect sudden and rapid changes in the communication link and simultaneously recover the communication link to continue service. For example, UE 120 may be configured to initiate a BFR procedure to select or otherwise configure a new serving beam based on processing at the PHY layer and the MAC layer without requiring any higher layer (eg, RRC) signaling.

[0082] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0083] Figure 7 is a diagram illustrating an example 700 associated with power conservation following a BFR request according to the present disclosure. Figure 7As shown, a UE (e.g., UE 120) may be connected to one or more cells, such as a first TRP and a second TRP in an mTRP operation, a primary cell (PCell) and a secondary cell (SCell) using dual connectivity or carrier aggregation, and the like. For example, as described herein, a PCell may be a cell in which a UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. For example, a PCell may process signaling associated with a UE, such as RRC signaling. In some aspects, a PCell may be a cell indicated as a primary cell during a handover procedure. A PCell may also be referred to as a special cell (SpCell). An SCell may be a cell that may be configured to provide additional radio resources to a UE. In some aspects, a PCell and the one or more SCells may each be considered a serving cell. Similarly, different TRPs may each be considered a serving cell (e.g., a first TRP may provide a PCell and a second TRP may provide an SCell). In some aspects, one SCell in a group of SCells may also process signaling associated with a UE, and such an SCell may be referred to as a primary secondary cell (PSCell). A PSCell may be considered a SpCell. Therefore, SpCell may refer to PCell of a primary cell group or PSCell of a secondary cell group. SpCell is a cell on which a UE may send or receive control signaling, a random access channel message, etc.

[0084] In example 700, a UE is associated with a first cell (shown as cell 1) and a second cell (shown as cell 2). For example, in some aspects, the first cell may be a SpCell (e.g., a PCell or a PSCell) and the second cell may be a SCell, the first cell may be a first SpCell (e.g., a PCell) and the second cell may be a second SpCell (e.g., a PSCell), etc. In some aspects, the first cell may be in a first frequency range (FR) (e.g., FR1), and the second cell may be in a second FR (e.g., FR2). In some other aspects, the first cell and the second cell may be in the same FR. In some aspects, the first cell may be provided by a first network node (e.g., a first TRP), and the second cell may be provided by a second network node (e.g., a second TRP). In some other aspects, the first cell and the second cell may be provided by the same network node (e.g., a DU controlling multiple RUs, a CU controlling multiple DUs, etc.). In other words, example 700 is an example of a BFR procedure for the first cell and the second cell, regardless of whether the first cell and the second cell are provided by the same network node or by different network nodes. Furthermore, while example 700 depicts a BFR procedure in which the UE communicates using multiple cells, it should be understood that similar techniques may be applied when the UE experiences beam failure in a single cell scenario (e.g., where the UE sends a BFR request in a serving cell associated with the beam failure rather than a different serving cell).

[0085] like Figure 7 As shown by reference numeral 710, the UE may detect a beam failure associated with a serving cell (e.g., cell 2 in the illustrated example). For example, the UE may detect that one or more downlink control beams for a second cell have failed, such as based at least in part on counting beam failure instances associated with the downlink control beams. Detecting that the one or more downlink control beams have failed may be referred to as beam failure detection (BFD). The UE (e.g., a MAC entity of the UE) may be configured via RRC signaling to trigger a BFR procedure when BFD occurs. For example, in some aspects, when a beam failure is detected on a serving beam (e.g., a serving SSB or a serving CSI-RS), the BFR procedure may be configured for each serving cell and may be used to indicate a new SSB or CSI-RS to a serving network node, such as via candidate beam information. For SpCell BFR, the UE may initiate a random access channel (RACH) procedure for BFR.

[0086] As indicated by reference numeral 720, the UE may send a BFR request (e.g., a scheduling request (SR) or a link recovery request (LRR)) on a first cell. Alternatively, in some aspects, a BFR request may be sent in a second cell associated with a detected beam failure (e.g., when there are one or more feasible beams that can be used to communicate with a cell associated with the same beam failure). In some aspects, the BFR request may request a grant of uplink resources on which the UE may send a BFR MAC-CE carrying beam failure information. For example, in some aspects, the beam failure information carried in the BFR MAC-CE may indicate an identifier of the second cell (e.g., a failed serving cell instance), an indication of one or more beams that have failed, candidate beam information (e.g., information indicating one or more new candidate beams for BFR on the second cell), etc. In some aspects, as described in more detail below, the UE may monitor one or more control channels after sending the BFR request. For example, as indicated by reference numeral 730, the UE may receive an uplink grant on one or more control channels based at least in part on the BFR request, whereby the UE may monitor the one or more control channels to enable receipt of a PDCCH carrying the uplink grant.

[0087] As indicated by reference numeral 740, the UE may send a BFR MAC-CE after receiving an uplink grant. For example, the UE may send the BFR MAC-CE on uplink resources indicated by the uplink grant. In some aspects, the UE may send the BFR MAC-CE based at least in part on an evaluation of candidate beams for a second cell. For example, if the UE determines that at least one BFR has been triggered and not canceled for a serving cell for which evaluation of candidate beams has been completed, and if uplink shared channel (UL-SCH) resources are available for new transmissions, and if the UL-SCH resources can accommodate a BFR MAC-CE plus a subheader of the BFR MAC-CE due to logical channel prioritization (LCP), the UE (e.g., via a multiplexing and assembly procedure of the UE) may generate a BFR MAC CE. If the UL-SCH resource cannot accommodate the BFR MAC-CE plus the subheader, the UL-SCH resource can be used for a new transmission, and the UL-SCH resource can accommodate a truncated BFR MAC-CE plus the subheader of the truncated BFR MAC-CE due to the LCP, the UE (e.g., via the UE's multiplexing and assembly procedures) can generate a truncated BFR MAC CE. If none of the above conditions are met, the UE can trigger a scheduling request for beam failure recovery for each serving cell, for which BFR has been triggered, not cancelled, and the evaluation of candidate beams has been completed. When a MAC protocol data unit (PDU) is transmitted and the MAC PDU includes a BFR MAC-CE or a truncated BFR MAC-CE containing beam failure information for a serving cell associated with a beam failure, all BFRs triggered for the serving cell can be cancelled. As shown by reference numeral 750, the UE can receive a BFR response, which can confirm the receipt of the BFR MAC-CE.

[0088] As described above, after a UE sends a BFR request for recovering from a beam failure detected in a serving cell (e.g., to a serving cell associated with the beam failure or a different serving cell), the UE may monitor one or more control channels to enable reception of a PDCCH carrying an uplink grant indicating uplink resources for sending BFR information (e.g., in a BFR MAC-CE). However, in some cases, the UE may continue to monitor one or more control channels associated with the failed beam after the beam failure has been detected. For example, in some cases, the UE may detect a beam failure in a serving cell (e.g., for a serving beam used to communicate with a TRP, SCell, PCell, or PSCell) and may continue to monitor one or more control channels associated with the serving cell even after the beam failure has been detected. However, continuing to monitor control channels associated with a beam that has failed may result in wasteful power consumption at the UE. Therefore, some aspects described herein relate to techniques by which a UE may prevent monitoring one or more control channels after a BFR request has been sent to recover from a beam failure, thereby saving power. For example, as indicated by reference numeral 760, the UE may refrain from monitoring PDCCH reception on one or more control channels in a cell associated with the beam failure after sending a BFR request associated with the beam failure.

[0089] For example, in the event that a beam failure is detected in a serving cell provided by a TRP, the UE may be configured to refrain from monitoring one or more CORESETs corresponding to the TRP in a cell associated with the beam failure based at least in part on the BFR request not indicating a new candidate beam to be used for communication with the TRP. For example, when the UE is configured to communicate with one or more TRPs (e.g., in an mTRP scenario), each TRP may provide a serving cell associated with a beam failure detection resource set (e.g., resources that the UE is configured to measure to detect a beam failure), which may be represented as (where i is the index associated with the TRP) and a set of candidate beam identification resources, which can be represented by Accordingly, when the UE detects that the serving beam associated with the TRP has a radio link quality (e.g., RSRP measurement or other suitable measurement) that fails to meet a threshold, the UE may attempt to identify a new candidate beam from one or more CORESETs associated with the candidate beam identification resource set, which may be represented by . In general, when the UE is able to identify a new candidate beam that satisfies applicable beam selection or beam recovery conditions, the UE may indicate the new candidate beam in the BFR request and may assume that antenna port quasi co-location (QCL) parameters correspond to the new candidate beam 28 symbols after the last symbol received from a PDCCH with a DCI format scheduled for a physical uplink shared channel (PUSCH) transmission that satisfies certain conditions (e.g., having the same hybrid automatic repeat request (HARQ) process number as the second PUSCH transmission and having a switched new data indicator (NDI) field value). However, in some cases, the UE may not be able to identify a resource set from the candidate beam. Identify any new candidate beams , which is associated with the TRP for which the beam failure was detected. In this case, because there is no suitable beam to recover communication with the TRP for which the beam failure was detected, when the UE cannot indicate a new candidate beam in the BFR request, the UE may prevent (e.g., not need to monitor) PDCCH reception in the CORESET set associated with the TRP for which the beam failure was detected. In some examples, for the TRP associated with and Sets associated with and having and set and has a ratio Q out,LR For a serving cell with poor radio link quality, after 28 symbols from the last symbol received of the first PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number as the PUSCH transmission of the MAC-CE carrying the beam failure request and with a switched NDI field value, the UE assumes antenna port QCL parameters: 1) for the first CORESET, corresponding to of (if any); 2) For the second CORESET, corresponding to of (if any), where the subcarrier spacing (SCS) configuration of 28 symbols is the smallest of the SCS configurations of the active downlink bandwidth part used for PDCCH reception and the active downlink bandwidth part of the serving cell. If the UE is unable to provide of , the UE does not need to monitor PDCCH on the first CORESET. of , the UE does not need to monitor PDCCH on the second CORESET.

[0090] Additionally or alternatively, in the event that a beam failure is detected in the SCell, the UE may be configured to refrain from monitoring one or more CORESETs in the SCell associated with the beam failure based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell. For example, when the UE detects that a beam used for communication in the SCell has a radio link quality that fails to meet a threshold, the UE may provide an indication of the presence of a new candidate beam for the SCell and / or an index of a periodic CSI-RS configuration or SSB for the corresponding SCell in a first PUSCH transmission (e.g., a BFR request). In such a case, after a duration (e.g., 28 symbols) from the last symbol received of a PDCCH in a DCI format with a scheduled PUSCH transmission (whose HARQ process number is the same as the first PUSCH transmission and has a switched NDI field value), the UE may monitor the PDCCH in all CORESETs associated with the SCell using the same antenna port QCL parameters as the new candidate beams. However, in the event that the UE is unable to identify any new candidate beams, the UE may monitor the PDCCH in all CORESETs associated with the SCell using the same antenna port QCL parameters as the new candidate beams. In the case of a BFR request, in order to reestablish communication with the SCell (e.g., the BFR request does not indicate a new candidate beam for the SCell), the UE may prevent monitoring (e.g., not need to monitor) the PDCCH reception in the one or more CORESETs associated with the SCell (e.g., to save power). For example, the UE may provide the following information for at least one corresponding SCell in the first PUSCH MAC-CE index: out,LR The radio link quality of the corresponding SCell, an indication of the presence of the new SCell, and the periodic CSI-RS configuration of the corresponding SCell or the index of the synchronization signal / physical broadcast channel (SS / PBCH) block provided by the higher layer After 28 symbols from the last symbol received of a PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number as the first PUSCH transmission and with a switched NDI field value, the UE uses the index corresponding to the same The UE shall monitor the PDCCH in all CORESETs on the SCell indicated by the MAC-CE with the same antenna port QCL parameters as the UE’s antenna port QCL parameters, if any. , the UE does not need to monitor PDCCH on CORESET.

[0091] Additionally or alternatively, in the event that a beam failure is detected in a SpCell, which may include a PCell or a PSCell, the UE may be configured with a BFR CORESET (e.g., provided by a recoverySearchSpaceId parameter) via a link to a search space set for monitoring the PDCCH in the BFR CORESET. In general, in the event that the UE is provided or otherwise configured with a BFR CORESET (e.g., via a search space set provided for BFR), the UE does not expect to be provided with another search space set for monitoring the PDCCH in the BFR CORESET associated with the search space set provided for BFR. After a BFR request, the UE does not need to monitor other CORESETs other than the CORESET associated with the recoverySearchSpaceId parameter. Therefore, when a beam failure is detected in a PCell or a PSCell, the UE may monitor only the BFR CORESET after sending a BFR request, and the UE may refrain from monitoring (e.g., not need or require monitoring) CORESETs other than the BFR CORESET associated with the search space set provided for BFR in order to save power.

[0092] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0093] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a mobile station in accordance with the present disclosure. Example process 800 is an example in which a mobile station (eg, UE 120) performs operations associated with power saving following a BFR request.

[0094] like Figure 8 As shown, in some aspects, process 800 may include detecting a beam failure associated with a beam used to communicate with a network node (block 810). For example, a mobile station (e.g., using Fig. 9 The depicted communication manager 140 and / or beam failure detection component 908) can detect a beam failure associated with a beam used to communicate with a network node, as described above.

[0095] like Figure 8 As further shown, in some aspects, process 800 may include sending a BFR request to a network node based at least in part on the beam failure (block 820). Fig. 9 The depicted communication manager 140 and / or transmitting component 904) can transmit a BFR request to a network node based at least in part on a beam failure, as described above.

[0096] like Figure 8 As further shown, in some aspects, process 800 may include, after sending the BFR request, refraining from monitoring one or more control channels associated with the beam failure (block 830). Fig. 9 The depicted communications manager 140 and / or control channel monitoring component 910) can refrain from monitoring one or more control channels associated with a beam failure after sending a BFR request, as described above.

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

[0098] In a first aspect, the beam associated with the beam failure is a beam used to communicate with a TRP associated with the same network node.

[0099] In a second aspect, either alone or in combination with the first aspect, the one or more control channels include a CORESET associated with the TRP based at least in part on the BFR request not indicating a new candidate beam to be used for communicating with the TRP.

[0100] In a third aspect, alone or in combination with one or more of the first and second aspects, the beam associated with the beam failure is a beam used for communicating with a network node in the SCell.

[0101] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the one or more control channels include a CORESET associated with the SCell based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell.

[0102] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the beam associated with the beam failure is a beam used to communicate with a network node in a PCell or a PSCell.

[0103] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more control channels include a CORESET associated with a PCell or a PSCell, and do not include a CORESET associated with a BFR search space set.

[0104] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 800 includes, after sending the BFR request, monitoring, by the mobile station, a CORESET associated with the BFR search space set.

[0105] although Figure 8An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0106] Fig. 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. The apparatus 900 may be a UE, or the UE may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication apparatus) using the receiving component 902 and the transmitting component 904. As further shown, the apparatus 900 may include a communication manager 140. The communication manager 140 may include one or more of a beam failure detection component 908 or a control channel monitoring component 910, among others.

[0107] In some aspects, the apparatus 900 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

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

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

[0110] A beam failure detecting component 908 can detect a beam failure associated with a beam used to communicate with a network node. A sending component 904 can send a BFR request to the network node based at least in part on the beam failure. A control channel monitoring component 910 can refrain from monitoring one or more control channels associated with the beam failure after sending the BFR request.

[0111] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The assembly of (one or more) components shown may be described as being executable by Fig. 9 Another collection of components shown performs one or more functions.

[0112] The following provides an overview of some aspects of the disclosure:

[0113] Aspect 1: A method of wireless communication performed by a mobile station, the method comprising: detecting, by the mobile station, a beam failure associated with a beam used to communicate with a network node; sending, by the mobile station, a BFR request to the network node based at least in part on the beam failure; and after sending the BFR request, preventing, by the mobile station, monitoring one or more control channels associated with the beam failure.

[0114] Aspect 2: The method according to Aspect 1, wherein the beam associated with the beam failure is a beam used to communicate with a TRP associated with the network node.

[0115] Aspect 3: A method according to Aspect 2, wherein the one or more control channels include a CORESET associated with the TRP based at least in part on the BFR request not indicating a new candidate beam to be used for communicating with the TRP.

[0116] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the beam associated with the beam failure is a beam used to communicate with the network node in an SCell.

[0117] Aspect 5: The method according to aspect 4, wherein the one or more control channels include a CORESET associated with the SCell based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell.

[0118] Aspect 6: The method according to any one of Aspects 1 to 3, wherein the beam associated with the beam failure is a beam used to communicate with the network node in a PCell or a PSCell.

[0119] Aspect 7: The method according to aspect 6, wherein the one or more control channels include a CORESET associated with the PCell or the PSCell, and do not include a CORESET associated with a BFR search space set.

[0120] Aspect 8: The method according to aspect 7, further comprising: after sending the BFR request, monitoring, by the mobile station, the CORESET associated with the BFR search space set.

[0121] Aspect 9: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 8.

[0122] Aspect 10: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 8.

[0123] Aspect 11: An apparatus for wireless communication, the apparatus comprising at least one component, the at least one component being configured to perform the method according to one or more of aspects 1 to 8.

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

[0125] Aspect 13: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 1 to 8.

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

[0127] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

[0129] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0130] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A may also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A method of wireless communication performed by a mobile station, the method comprising: detecting, by the mobile station, a beam failure associated with a beam used for communicating with a network node; sending, by the mobile station, a beam failure recovery (BFR) request to the network node based at least in part on the beam failure; as well as After sending the BFR request, monitoring of one or more control channels associated with the beam failure is refrained by the mobile station. 2 . The method of claim 1 , wherein the beam associated with the beam failure is a beam used for communicating with a transmit receive point (TRP) associated with the network node.

3. The method of claim 2, wherein the one or more control channels include a control resource set (CORESET) associated with the TRP based at least in part on the BFR request not indicating a new candidate beam to be used for communicating with the TRP. 4 . The method of claim 1 , wherein the beam associated with the beam failure is a beam used to communicate with the network node in a secondary cell (SCell).

5. The method of claim 4, wherein the one or more control channels include a control resource set (CORESET) associated with the SCell based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell. 6 . The method of claim 1 , wherein the beam associated with the beam failure is a beam used to communicate with the network node in a primary cell (PCell) or a primary secondary cell (PSCell). 7 . The method of claim 6 , wherein the one or more control channels include a control resource set (CORESET) associated with the PCell or the PSCell, excluding a CORESET associated with a BFR search space set.

8. The method according to claim 7, further comprising: After sending the BFR request, the CORESET associated with the BFR search space set is monitored by the mobile station.

9. A mobile station for wireless communication, the mobile station comprising: Memory; and and one or more processors coupled to the memory and, based at least in part on the information stored in the memory, configured to: detecting a beam failure associated with a beam used for communicating with a network node; sending a beam failure recovery (BFR) request to the network node based at least in part on the beam failure; as well as After sending the BFR request, monitoring of one or more control channels associated with the beam failure is refrained.

10. The mobile station of claim 9, wherein the beam associated with the beam failure is a beam used for communicating with a transmit receive point (TRP) associated with the network node.

11. The mobile station of claim 10, wherein the one or more control channels include a control resource set (CORESET) associated with the TRP based at least in part on the BFR request not indicating a new candidate beam to be used for communicating with the TRP. 12 . The mobile station of claim 9 , wherein the beam associated with the beam failure is a beam used to communicate with the network node in a secondary cell (SCell).

13. The mobile station of claim 12, wherein the one or more control channels include a control resource set (CORESET) associated with the SCell based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell.

14. The mobile station of claim 9, wherein the beam associated with the beam failure is a beam used to communicate with the network node in a primary cell (PCell) or a primary secondary cell (PSCell). 15 . The mobile station of claim 14 , wherein the one or more control channels include a control resource set (CORESET) associated with the PCell or the PSCell, excluding a CORESET associated with a BFR search space set.

16. The mobile station of claim 15, wherein the one or more processors are further configured to: After sending the BFR request, the CORESET associated with the BFR search space set is monitored.

17. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a mobile station, cause the mobile station to: detecting a beam failure associated with a beam used for communicating with a network node; sending a beam failure recovery (BFR) request to the network node based at least in part on the beam failure; as well as After sending the BFR request, monitoring of one or more control channels associated with the beam failure is refrained.

18. The non-transitory computer-readable medium of claim 17, wherein the beam associated with the beam failure is a beam used for communicating with a transmit receive point (TRP) associated with the network node.

19. The non-transitory computer-readable medium of claim 18, wherein the one or more control channels include a control resource set (CORESET) associated with the TRP based at least in part on the BFR request not indicating a new candidate beam to be used for communicating with the TRP.

20. The non-transitory computer-readable medium of claim 17, wherein the beam associated with the beam failure is a beam used to communicate with the network node in a secondary cell (SCell).

21. The non-transitory computer-readable medium of claim 20, wherein the one or more control channels include a control resource set (CORESET) associated with the SCell based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell.

22. The non-transitory computer-readable medium of claim 17, wherein the beam associated with the beam failure is a beam used to communicate with the network node in a primary cell (PCell) or a primary secondary cell (PSCell).

23. The non-transitory computer-readable medium of claim 22, wherein the one or more control channels include a control resource set (CORESET) associated with the PCell or the PSCell, excluding a CORESET associated with a BFR search space set.

24. The non-transitory computer readable medium of claim 23, wherein the one or more instructions further cause the mobile station to: After sending the BFR request, the CORESET associated with the BFR search space set is monitored.

25. An apparatus for wireless communication, the apparatus comprising: means for detecting a beam failure associated with a beam used for communicating with a network node; means for sending a beam failure recovery (BFR) request to the network node based at least in part on the beam failure; and means for refraining from monitoring one or more control channels associated with the beam failure after transmitting the BFR request.

26. The apparatus of claim 25, wherein the beam associated with the beam failure is a beam used for communicating with a transmit reception point (TRP) associated with the network node.

27. The apparatus of claim 26, wherein the one or more control channels include a control resource set (CORESET) associated with the TRP based at least in part on the BFR request not indicating a new candidate beam to be used for communicating with the TRP.

28. The apparatus of claim 25, wherein the beam associated with the beam failure is a beam used to communicate with the network node in a secondary cell (SCell).

29. The apparatus of claim 28, wherein the one or more control channels comprise a control resource set (CORESET) associated with the SCell based at least in part on the BFR request not indicating a new candidate beam to be used for communication in the SCell.

30. The apparatus of claim 25, wherein the beam associated with the beam failure is a beam used to communicate with the network node in a primary cell (PCell) or a primary secondary cell (PSCell).

31. The apparatus of claim 30, wherein the one or more control channels include a control resource set (CORESET) associated with the PCell or the PSCell, excluding a CORESET associated with a BFR search space set.

32. The apparatus according to claim 31, further comprising: means for monitoring the CORESET associated with the BFR search space set after sending the BFR request.

Images