Beam fault detection reference signal set update

By receiving and processing instructions of the beam fault detection reference signal set in the user equipment (UE) of the wireless communication system, the problems of configuration conflicts and inefficiency during the beam fault detection process in the prior art are solved, and more efficient and reliable beam fault detection is achieved.

CN119895746APending Publication Date: 2025-04-25QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380066654.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-09-30
Filing Date
2023-09-26
Publication Date
2025-04-25

AI Technical Summary

Technical Problem

During the beam fault detection process of existing wireless communication systems, the update method of beam fault detection reference signal set has problems of configuration conflicts and inefficiency.

Method used

By receiving an indication of the beam fault detection reference signal set corresponding to the component carrier list in a user equipment (UE), it is determined whether the component carrier is included in the list or whether the beam fault detection reference signal set in the set is applicable to the component carrier, and selects an appropriate beam fault detection reference signal set for monitoring according to its type (single or multiple beam fault detection reference signal sets) .

Benefits of technology

It effectively avoids configuration conflicts, improves communication speed and reliability, and ensures the accuracy and efficiency of the beam fault detection process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119895746A_ABST
    Figure CN119895746A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive an indication of one or more sets of beam fault detection reference signals corresponding to a list of component carriers. Whether a component carrier is included in the list or whether a set of beam fault detection reference signals in the one or more sets of beam fault detection reference signals is applicable to the component carrier or both may be based on whether the component carrier belongs to a first type configured for a single set of beam fault detection reference signals or configured for use with the component carrier and detecting a second type of the reference signal set in the plurality of beam faults. The UE may monitor one or more component carriers included in the list for beam faults using one or more indicated sets of beam fault detection reference signals.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 958,050, entitled “BEAM FAILUREDETECTION REFERENCE SIGNAL SET UPDATE,” filed by Bai et al. on September 30, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including beam failure detection reference signal set updating. Background Art

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

[0005] In some wireless communication systems, a wireless device may use a set of beam failure detection reference signals for a beam failure detection process. However, such methods may be improved. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting beam failure detection reference signal set updates. A user equipment (UE) may receive an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers. Whether a component carrier is included in the list or whether a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, may be based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The UE may use the one or more indicated beam failure detection reference signal sets to monitor one or more component carriers included in the list for beam failures.

[0007] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; and using the one or more indicated beam failure detection reference signal sets to monitor one or more component carriers included in the list for beam failure.

[0008] An apparatus for wireless communication is described. The apparatus may include: a memory; a transceiver; and at least one processor of a user equipment, the at least one processor being coupled to the memory and the transceiver. The at least one processor may be configured to: receive an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether a component carrier is included in the list or whether a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; and use the one or more indicated beam failure detection reference signal sets to monitor one or more component carriers included in the list for beam failures.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; and means for monitoring one or more component carriers included in the list for beam failure using the one or more indicated beam failure detection reference signal sets.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; and use the one or more indicated beam failure detection reference signal sets to monitor one or more component carriers included in the list for beam failures.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of one or more beam failure detection reference signal sets indicates multiple beam failure detection reference signal sets corresponding to the list of component carriers, and the methods, apparatuses, and non-transitory computer-readable media may include further operations, features, components, or instructions for performing the following actions: based on the multiple beam failure detection reference signal sets indicated by the indication, identifying the multiple beam failure detection reference signal sets as applicable to each component carrier of the second type included in the list that may belong to the configured multiple beam failure detection reference signal sets, wherein the monitoring includes: based on the multiple beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list that may belong to the second type, using each beam failure detection reference signal set in the multiple beam failure detection reference signal sets to monitor each component carrier of the second type included in the list that may belong to the second type.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying the indication of the multiple beam failure detection reference signal sets as not applicable to each component carrier of the first type included in the list that may belong to the configured single beam failure detection reference signal set.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of one or more beam failure detection reference signal sets indicates a single beam failure detection reference signal set corresponding to the list of component carriers, and the method, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for performing the following actions: based on the single beam failure detection reference signal set being indicated by the indication, identifying the single beam failure detection reference signal set as applicable to each component carrier of the first type included in the list that may belong to the configured single beam failure detection reference signal set, wherein the monitoring includes monitoring each component carrier of the first type included in the list using the single beam failure detection reference signal set based on the single beam failure detection reference signal set being applicable to each component carrier of the first type included in the list.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: based on the single beam failure detection reference signal set being indicated by the indication, identifying the indication for the single beam failure detection reference signal set as not applicable to each component carrier included in the list that may belong to the second type configured for multiple beam failure detection reference signal sets.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of one or more beam failure detection reference signal sets indicates multiple beam failure detection reference signal sets corresponding to the list of component carriers, and the methods, apparatuses, and non-transitory computer-readable media may include further operations, features, components, or instructions for performing the following actions: based on the multiple beam failure detection reference signal sets indicated by the indication, identifying that a first beam failure detection reference signal set in the multiple beam failure detection reference signal sets is applicable to each component carrier of the first type configured for a single beam failure detection reference signal set, wherein the monitoring includes: based on the first beam failure detection reference signal set being applicable to each component carrier included in the list that may belong to the second type, using the first beam failure detection reference signal set to monitor each component carrier included in the list that may belong to the first type.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying that both the first beam failure detection reference signal set and the second beam failure detection reference signal set in the multiple beam failure detection reference signal sets are applicable to each component carrier of the second type configured for the multiple beam failure detection reference signal sets, wherein the monitoring includes monitoring each component carrier of the second type included in the list using both the first beam failure detection reference signal set and the second beam failure detection reference signal set based on the first beam failure detection reference signal set and the second beam failure detection reference signal set being applicable to each component carrier of the second type included in the list.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the list includes only component carriers of the first type configured for the single beam failure detection reference signal set or only component carriers of the second type configured for multiple beam failure detection reference signal sets, and the component carriers of the second type that may be included in the list are each configured for the same number of beam failure detection reference signal sets.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the component carrier of the first type includes a component carrier configured for per-cell beam failure recovery, and wherein the component carrier of the second type includes a component carrier configured for per-transmit and receive point (TRP) beam failure recovery.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the list of component carriers includes a list of component carriers for beam indication.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second indication of one or more second beam failure detection reference signal sets corresponding to a second list of component carriers, wherein the second list of component carriers does not include any component carrier that can be included in the list of component carriers.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a capability message indicating that the UE supports reception of beam failure detection reference signal set indications corresponding to multiple component carriers, that the UE supports a maximum number of applicable component carriers for which the beam failure detection reference signal set indication is supported, that the UE supports a maximum number of lists of component carriers for which the beam failure detection reference signal set indication is supported, or any combination thereof.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: detecting a beam failure within a component carrier among the one or more component carriers included in the list based on monitoring the beam failure; receiving a beam failure recovery response message in response to sending a beam failure recovery request; and resetting one or more power control parameters for uplink transmission to corresponding default values ​​based on receiving the beam failure recovery response message.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more power control parameters for uplink transmissions are applied to sounding reference signal transmissions, physical uplink control channel transmissions, physical uplink shared channel transmissions, or any combination thereof associated with the transmit and receive points for which the beam failure was detected.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving an indication of multiple new beam indicator sets; and selecting the multiple beam fault detection reference signal sets for monitoring based on the multiple new beam indicator sets, wherein each beam fault detection reference signal set in the multiple beam fault detection reference signal sets corresponds to a corresponding transmission and reception point, a corresponding control resource set pool, or both. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 An example of a wireless communication system supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0026] Figure 2 An example of a wireless communication system supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0027] Figure 3A , Figure 3B and Figure 3C An example of a BFD-RS set update scheme supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0028] Figure 4 An example of a process flow supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0029] Figure 5 and Figure 6 A block diagram of an apparatus supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0030] Figure 7 A block diagram of a communication manager supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0031] Figure 8 A diagram of a system including a device supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated.

[0032] Figures 9 to 12 A flow chart showing a method of supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. DETAILED DESCRIPTION

[0033] During wireless communication, a user equipment (UE) may participate in a beam failure detection (BFD) process to detect when one or more transmit beams (e.g., from a network entity) fail based on one or more conditions. To perform this operation, the UE may measure one or more BFD reference signals (BFD-RS). These BFD-RS may be indicated to the UE in control signaling (e.g., medium access control control element (MAC-CE) signaling or other control signaling), and the control signaling may indicate multiple sets of BFD-RS. The control signaling may apply the BFD-RS set to all CCs in the CC list, as this may be done based on the beam indication. However, some CCs on the CC list may not be configured for multiple transmit and receive points (TRPs) or per-TRP BFR schemes. Therefore, if the control signaling activates two BFD-RS sets and the CCs on the CC list indicated in the control signaling may be configured for a single BFD-RS set, a configuration conflict may occur.

[0034] The subject matter described herein includes techniques for resolving such configuration conflicts. In some examples, configuration conflicts can be avoided by configuring the CC list to include CCs that are all of the same type (e.g., configured for multiple BFD-RS sets or for a single BFD-RS set). In other examples, the UE may apply multiple BFD-RS sets only to applicable CCs in the CC list. For example, if the control signaling indicates multiple BFD-RS sets, the multiple BFD-RS sets will be applied to CCs configured for multiple BFD-RS sets. Similarly, if the control signaling indicates a single BFD-RS set, the single BFD-RS set will be applied to CCs configured for a single BFD-RS set. In other examples, if the control signaling indicates multiple BFD-RS sets, the multiple BFD-RS sets will be applied to CCs configured for multiple BFD-RS sets, and the first BFD-RS set in the multiple BFD-RS sets will be applied to CCs configured for a single BFD-RS set. In at least these ways, configuration conflicts can be avoided, and communication speed and reliability can be improved due to reduced configuration conflicts.

[0035] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are then described with reference to a wireless communication system, a BFD-RS set update scheme, and a process flow. Various aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flow diagrams related to beam failure detection reference signal set update, and various aspects of the present disclosure are described with reference to these diagrams.

[0036] Figure 1An example of a wireless communication system 100 supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0037] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

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

[0039] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0040] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

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

[0042] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

[0044] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0045] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

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

[0047] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the IAB node 104 via the F1 interface that the communication link is established, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0048] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support beam failure detection reference signal set updates as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0049] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0050] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

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

[0052] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0053] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0054] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0055] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0056] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0057] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0058] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0060] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0061] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

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

[0063] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0064] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0065] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0066] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

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

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

[0069] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0070] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communication, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0071] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

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

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

[0074] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0075] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports of multiple rows and columns that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

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

[0077] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0078] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

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

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

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

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

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

[0084] In some implementations, a UE may participate in a BFD process that may involve cross-CC indications on a list of CCs. The UE may receive control signaling (e.g., MAC-CE signaling) that may indicate one or more BFD-RS sets to be used for the BFD process. In some examples, the list of CCs may be of a single type, such as a CC type configured for a single BFD-RS set or a CC type configured for multiple BFD-RS sets (e.g., two BFD-RS sets). In other examples, the MAC-CE may apply only to CCs in the list that are configured for the same number of BFD-RS sets as indicated by the MAC-CE. In yet other examples, if the MAC-CE indicates multiple BFD-RS sets, the CC configured for a single BFD-RS set may use the first BFD-RS set of the multiple BFD-RS sets indicated in the MAC-CE.

[0085] Figure 2An example of a wireless communication system 200 supporting beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The wireless communication system 200 may include a UE 115-a and a network entity 105-a, and the UE 115-a may operate within a coverage area 110-a associated with the network entity 105-a.

[0086] During wireless communication, the wireless communication system 200 may participate in a beam failure recovery process (e.g., reestablishing communication using a new beam after communication using another beam has failed). In some examples, the beam failure recovery process may include various operations. The UE 115-a may measure one or more BFD-RS sets and may determine whether a beam failure is detected based on one or more conditions. Such BFD-RS sets may be configured in control signaling (e.g., RRC signaling) or may be identified by the UE 115-a (e.g., based on one or more CORESET beams).

[0087] The UE 115-a may (e.g., after detecting a beam failure) send a beam failure recovery (BFR) request (BFRQ) (e.g., to the network entity 105-a). In an example involving primary cell (PCell) BFR, the BFRQ may be sent using a random access procedure (e.g., a contention-free random access channel (RACH) procedure). The UE may send random access procedure signaling in a new beam (e.g., q_new beam). In an example involving secondary cell BFR, the UE 115-a may send the BFRQ in the Pcell (e.g., via a scheduling request in a physical uplink control channel (PUCCH) transmission). The network entity 105-a may then respond with an uplink grant, and the UE 115-a may send BFR control signaling (e.g., BFR MAC-CE) using scheduled uplink resources (e.g., physical uplink shared channel (PUSCH) resources). Such control signaling may include an indication of a replacement beam for the failed beam (e.g., a q_new beam indication). In some examples, q_new may be identified from a defined reference signal set (e.g., a new beam indicator (NBI) set of reference signals). In some examples, the NBI-RS may be configured in control signaling (e.g., RRC signaling).

[0088] The network entity 105-a may respond with a BFR response (BFRR), and the UE 115-a may begin communicating using the new beam (e.g., q_new beam) (e.g., at a time point 28 symbols after receiving the BFRR).

[0089] In some examples, the BFR process may be performed for individual transmit and receive points (TRPs) or on a per-TRP basis. For example, a cell may include different beam groups, and each group may correspond to a TRP. In some examples, a cell may include or be associated with multiple TRPs (or another number of TRPs). The beams from each TRP, the transmit configuration indication (TCI) state, or both may be configured with different identifiers (e.g., CORESETpool ID).

[0090] UE 115-a may identify a TRP association based on such an identifier (e.g., CORESETpool ID), and UE115-a may be configured with BFD-RS, NBI-RS, or both on a per-TRP or per-beam group basis. Multiple BFD-RS sets, NBI-RS sets, or both may be configured in a cell, and one or more such sets may each correspond to a TRP. UE 115-a may monitor BFD resources per TRP, and upon detecting a per-TRP beam failure, a per-TRP BFR may be triggered. The UE may select a new beam (e.g., q_new) from the corresponding NBI-RS set of the failed TRP. However, not all beams in a cell always fail. Therefore, UE 115-a may still send a BFR request (e.g., via PUCCH or PUSCH). The wireless communication system 200 may employ a Scell ​​BFRQ mechanism, which may include a two-step approach in which the UE 115-a first sends a scheduling request to the network entity 105-a, and then the UE 115-a may send control signaling (e.g., MAC-CE) for attaching BFR information. In some examples, the BFD-RS set may be explicitly configured by the network entity 105-a, or may be implicitly identified by the UE 115-a. For example, the UE 115-a may implicitly identify one or more BFD-RS sets by identifying one or more reference signals that are quasi-co-located (QCL) with one or more associated CORESET beams or TCI states.

[0091] In some examples, one or more BFD-RS sets may be configured or updated via control signaling (e.g., MAC-CE control signaling). For example, MAC-CE control signaling may be used to configure multiple BFD-RS sets (e.g., two or more BFD-RS sets for each TRP BFR). Additionally or alternatively, a single BFD-RS set (e.g., a single BFD-RS set for cell-level BFR) may be configured. Such a MAC-CE may include a field for an identifier (such as a cell identifier or a BWP identifier), and the update may apply only to the indicated cell or BWP. In some examples, such updates may still be performed on a per component carrier (CC) basis.

[0092] In some examples, beam indication for CCs on a CC (e.g., including using MAC-CE to activate TCI for PDSCH, using MAC-CE to update beams for PUCCH, or other beam indications) may be performed on a cross-CC basis (e.g., across different CCs on a CC list that may be predefined or configured in control signaling (such as RRC signaling). For example, the MAC-CE may apply to multiple CCs or all CCs on the CC list that are the same as the CCs indicated in the MAC-CE.

[0093] In some examples, indication of BFD-RS may be performed by MAC-CE on a similar cross-CC basis (e.g., a MAC-CE for BFD-RS configuration may be applied to all CCs on the same CC list of the indicated CCs). The CC list used for BFD-RS set indication may be the same CC list used for beam indication. However, in some cases, some CCs on the CC list may not be configured for multiple TRPs or per-TRP BFRs. For example, if the MAC-CE activates two sets of BFD-RS, and CCs on the same list of indicated CCs are configured with a single TRP or cell-level BFR (e.g., resulting in the CC being configured with a single BFD-RS set), a configuration conflict may occur. Therefore, the various techniques described herein allow such conflicts to be avoided or resolved.

[0094] For example, UE 115-a may receive (e.g., from network entity 105-a) a BFD-RS set indication 220 indicating one or more BFD-RS sets (e.g., a first BFD-RS set 225 and a second BFD-RS set 230) corresponding to a list of one or more CCs 235. In some examples, a unified CC list may be used in which all CCs are of the same type (e.g., a type indicating the number of BFD-RS sets for which CC 235 is configured). For example, a determination or identification of whether a CC 235 is to be included in the list may be based on whether the CC 235 is of a first type configured for a single BFD-RS set or a second type configured for multiple BFD-RS sets. Additionally or alternatively, the BFD-RS set indication 220 may be applicable to a subset of CCs 235 in the list, and the determination or identification of which CCs 235 the first BFD-RS set 225, the second BFD-RS set 230, or both may apply to is based on whether the CCs 235 in the list are of a first type configured for a single BFD-RS set or a second type configured for multiple BFD-RS sets. In some examples, once the UE 115-a determines which BFD-RS sets are applicable to which CCs 235 in the CC list, the UE 115-a may use one or more indicated BFD-RS sets to monitor one or more CCs in the CC 235 included in the beam failure monitoring list for one or more of the beams 240 associated with the CC 235.

[0095] In at least these ways, configuration conflicts between control signaling and CCs in the CC list for BFD may be reduced or eliminated. This may also increase communication reliability and speed because the BFR process may not be affected by errors caused by incorrect configuration, and the BFR process may be performed more quickly.

[0096] In some examples, the CC list for BFD-RS update can be the same list used for beam indication. Additionally or alternatively, the CC list for BFD-RS update can be a separate list configured in control signaling (e.g., RRC signaling) dedicated to BFD-RS update.

[0097] In some examples, multiple CC lists may be configured in the control signaling, and in some examples, such CC lists may be non-overlapping (eg, a given CC may appear in only one CC list of the multiple CC lists).

[0098] In some examples, UE 115-a may report whether it supports cross-CC BFD-RS set updates, the maximum supported number of CCs on a CC list, the maximum supported number of CC lists, one or more other BFD-RS set update capabilities, or any combination thereof.

[0099] In some examples, if one or more BFD-RS sets are not configured, it may not be clear which or how many BFD-RS sets are to be identified or determined for the BFR process. Therefore, UE 115-a may use one or more rules to implicitly identify or determine one or more BFD-RS sets. For example, if a second NBI set is configured, UE 115-a may identify two sets of BFD-RS and each set of BFD-RS may correspond to a TRP or a CORESETpool. For example, UE 115-a may select a BFD-RS set for each CORESETpool as a periodic channel state information reference signal (P-CSI-RS) for defining the TCI of a CORESET in the corresponding CORESETpool. In some examples, a one-to-one mapping between TRP and CORESETpool may be used. However, if a second NBI set is not configured, UE 115-a may identify or determine a single BFD-RS set to be used for BFD-RS updating. For example, UE 115-a may select a BFD RS set for P-CSI-RS that defines the TCI of a CORESET in a cell.

[0100] In some examples, after receiving the BFRR, the uplink beam and downlink beam used for communication may be reset to another beam (e.g., the q_new beam). However, for uplink communications, the power control parameters applicable to the previous beam may not be applicable or may be less applicable to the new beam. Therefore, the power control parameters may be reset (e.g., by UE 115-a or network entity 105-a) to one or more default values. Such power control parameters may include closed-loop power control parameters for PUCCH, sounding reference signal (SRS), PUSCH, other uplink transmissions, or any combination thereof. In addition, different default values ​​may be used for different channels or reference signals. Additionally or alternatively, the resetting of power control parameters in the case of per-TRP BFR may be applied to SRS, PUCCH, PUSCH, or any combination thereof associated with a failed TRP or failed beam.

[0101] Figure 3AAn example of a BFD-RS set update scheme 301 supporting beam failure detection reference signal set updates according to one or more examples as disclosed herein is illustrated. In the BFD-RS set update scheme 301, all CCs on the same CClist that share the same BFD-RS update (e.g., performed via MAC-CE) are configured with the same BFR mode (e.g., per-cell BFR mode or per-TRP BFR mode) or belong to the same type (e.g., single BFD-RS set type or dual BFD-RS set type). For example, each CC in CC list 320-a belongs to a single BFD-RS set type, and each CC in CC list 320-b belongs to a dual BFD-RS set type. For example, each CC in CC list 320-a may be configured for a single BFD-RS set. Such a unified CC list may avoid configuration conflicts because MAC-CE may be configured for a single type (e.g., single BFD-RS set or dual BFD-RS set) used in the CC list. Although dual BFD-RS set types or patterns are discussed, it should be understood that such techniques are applicable to any number of BFD-RS sets.

[0102] Figure 3B An example of a BFD-RS set update scheme 302 supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The BFD-RS set update scheme 302 includes a cc list 320-c to which a MAC-CE 325-a or MAC-CE 325-b may be applied. The MAC-CE 325-a includes or indicates a single BFD-RS set, and the MAC-CE 325-b includes or indicates a dual BFD-RS set.

[0103] In some examples, a BFD-RS MAC-CE (e.g., MAC-CE 325-a or MAC-CE 325-b) may be applicable to applicable CCs on the list and may not be applicable to inapplicable CCs. For example, when the BFD-RS MAC-CE includes two BFD-RS sets, as in MAC-CE 235-b, the applicable CCs may be CCs configured with per-TRP BFR (e.g., via control signaling such as RRC signaling) or CCs configured with two NBI sets or BFD-RS sets. CC1, CC2, CC4, and CC6 may be examples of such applicable CCs in the case involving MAC-CE 325-b. Correspondingly, inapplicable CCs may be CCs configured with cell-level BFR or CCs that are not configured with CORESETpool, do not have activated TCI code points with more than 1 TCI, are configured with a single NBI set or BFD-RS set, or are not configured with any NBI or BFD-RS set. CC0, CC3, CC5, and CC7 may be examples of CCs that are not applicable where MAC-CE 325-b is involved.

[0104] Additionally or alternatively, when the BFD-RS MAC-CE includes one BFD-RS set, such as MAC-CE 235-a, the applicable CC may be a CC that is not configured with CORESETpool, does not have activated TCI code points with more than 1 TCI, is configured with a single NBI set or BFD-RS set, or is not configured with any NBI or BFD-RS set. CC0, CC3, CC5, and CC7 may be examples of applicable CCs in the case involving MAC-CE 325-a. Correspondingly, inapplicable CCs for MAC-CE 235-a may include (e.g., in control signaling such as RRC signaling) CCs configured with per-TRP level BFR or configured with two NBI sets or BFD-RS sets. CC1, CC2, CC4, and CC6 may be examples of such inapplicable CCs in the case involving MAC-CE 325-a.

[0105] In some examples, control signaling (e.g., RRC signaling) may indicate whether the CC is used for cell-level BFR or for per-TRP BFR via one or more bits in the control signaling.

[0106] Figure 3CAn example of a BFD-RS set update scheme 303 supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. In the BFD-RS set update scheme 303, a MAC-CE 325-c may indicate both a first BFD-RS set 330-a and a second BFD-RS set 330-b, and the MAC-CE 325-c may be applicable to a CC list 320-d.

[0107] In some examples, when a BFD-RS MAC-CE (such as MAC-CE 325-c) includes 2 BFD-RS sets (e.g., a first BFD-RS set 330-a and a second BFD-RS set) and a CC on the CC list is used for per-cell BFR (e.g., the CC is configured for only one BFD-RS set), one of the two BFD-RS sets in the MAC-CE is activated for the per-cell BFR CC. For example, the first BFD-RS set 330-a may be activated for all CCs. However, the second BFD-RS set 330-b may be activated only for CCs that belong to a dual BFD-RS set type and are configured for a dual BFD-RS set (such as CC1, CC2, CC4, and CC6). CC0, CC3, CC5, and CC7 are configured only for the first BFD-RS set 330-a. In this manner, configuration conflicts between the MAC-CE 325 - c and CCs in the CC list 320 - d that are otherwise incompatible with the MAC-CE 325 - c are reduced or eliminated.

[0108] Figure 4 An example of a process flow 400 for supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The process flow 400 may implement aspects of the present disclosure described herein. The elements described in the process flow 400 (e.g., the network entity 105-b and the UE 115-b) may be examples of similarly named elements described herein.

[0109] In the following description of process flow 400, operations between various entities or elements may be performed in different orders or at different times. Some operations may also be excluded from process flow 400, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 400, some aspects of some operations may also be performed by other entities or elements of process flow 400 or by entities or elements not depicted in the process flow, or any combination thereof.

[0110] At 420, UE 115-b may send a capability message that may indicate that the UE supports reception of beam failure detection reference signal set indications corresponding to multiple component carriers, the maximum number of applicable component carriers for which the UE supports the beam failure detection reference signal set indication, the maximum number of a list of component carriers for which the UE supports the beam failure detection reference signal set indication, or any combination thereof.

[0111] At 425, UE 115-b may receive an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, and whether the component carrier is included in the list or whether a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets.

[0112] In some examples, the indication of one or more beam failure detection reference signal sets may indicate multiple beam failure detection reference signal sets corresponding to the list of component carriers. Additionally or alternatively, in some examples, the indication of one or more beam failure detection reference signal sets may indicate a single beam failure detection reference signal set corresponding to the list of component carriers.

[0113] In some examples, the list may include only the component carriers of the first type configured for the single beam failure detection reference signal set or only the component carriers of the second type configured for multiple beam failure detection reference signal sets, and the component carriers of the second type included in the list are each configured for the same number of beam failure detection reference signal sets. In some examples, the component carriers of the first type include component carriers configured for per-cell beam failure recovery, and wherein the component carriers of the second type include component carriers configured for per-transmission and reception point (TRP) beam failure recovery. In some examples, the list of component carriers may include a list of component carriers for beam indication.

[0114] At 430, UE 115-b may receive an indication of a plurality of new beam indicator sets.

[0115] At 435, UE 115-b may select the multiple beam failure detection reference signal sets for the monitoring based on the multiple new beam indicator sets, and each beam failure detection reference signal set in the multiple beam failure detection reference signal sets corresponds to a corresponding transmitting and receiving point, a corresponding control resource set pool, or both.

[0116] At 440, UE 115-b may receive a second indication of one or more second beam failure detection reference signal sets corresponding to a second list of component carriers, and the second list of component carriers does not include any component carrier included in the list of component carriers.

[0117] At 445, UE 115-b may, based on the multiple beam failure detection reference signal sets indicated by the indication, identify the multiple beam failure detection reference signal sets as applicable to each component carrier of the second type configured for the multiple beam failure detection reference signal sets included in the list. Additionally or alternatively, UE 115-b may, based on the single beam failure detection reference signal set indicated by the indication, identify the single beam failure detection reference signal set as applicable to each component carrier of the first type configured for the single beam failure detection reference signal set included in the list. Additionally or alternatively, UE 115-b may, based on the multiple beam failure detection reference signal sets indicated by the indication, identify the first beam failure detection reference signal set in the multiple beam failure detection reference signal sets as applicable to each component carrier of the component carrier of the first type configured for the single beam failure detection reference signal set. Additionally or alternatively, UE 115-b may, based on the multiple beam failure detection reference signal sets indicated by the indication, identify that both the first beam failure detection reference signal set and the second beam failure detection reference signal set in the multiple beam failure detection reference signal sets are applicable to each component carrier of the second type configured for the multiple beam failure detection reference signal sets.

[0118] At 450, UE 115-b may, based on the multiple beam failure detection reference signal sets being indicated by the indication, identify the indication of the multiple beam failure detection reference signal sets as not applicable to each component carrier of the first type included in the list that is configured for the single beam failure detection reference signal set. Additionally or alternatively, UE 115-b may, based on the single beam failure detection reference signal set being indicated by the indication, identify the indication of the single beam failure detection reference signal set as not applicable to each component carrier of the second type included in the list that is configured for the multiple beam failure detection reference signal sets.

[0119] At 455, UE 115-b may monitor one or more component carriers included in the list for beam failure using one or more indicated beam failure detection reference signal sets. In some examples, the monitoring includes: based on the multiple beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list, using each beam failure detection reference signal set in the multiple beam failure detection reference signal sets to monitor each component carrier of the second type included in the list. In some examples, the monitoring includes: based on the single beam failure detection reference signal set being applicable to each component carrier of the first type included in the list, using the single beam failure detection reference signal set to monitor each component carrier of the first type included in the list. In some examples, the monitoring includes: based on the first beam failure detection reference signal set and the second beam failure detection reference signal set being applicable to each component carrier of the second type included in the list, using both the first beam failure detection reference signal set and the second beam failure detection reference signal set to monitor each component carrier of the second type included in the list.

[0120] At 460 , the UE 115 - b may detect a beam failure within a component carrier of the one or more component carriers of the component carriers included in the list based on monitoring for beam failure.

[0121] At 465, UE 115 may receive a beam failure recovery response message in response to sending the beam failure recovery request.

[0122] At 470, UE 115-b may reset one or more power control parameters for uplink transmissions to corresponding default values ​​based on receiving the beam failure recovery response message. In some examples, the one or more power control parameters for uplink transmissions are applied to sounding reference signal transmissions, physical uplink control channel transmissions, physical uplink shared channel transmissions, or any combination thereof associated with the transmission and reception points for which the beam failure was detected.

[0123] Figure 5 A block diagram 500 of a device 505 supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0124] The receiver 510 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to beam failure detection reference signal set updates), user data, control information, or any combination thereof. The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

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

[0126] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of beam failure detection reference signal set updating as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0127] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

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

[0130] Additionally or alternatively, according to examples as disclosed herein, the communication manager 520 may support wireless communication at the UE. For example, the communication manager 520 may be configured to or otherwise support a component for receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The communication manager 520 may be configured to or otherwise support a component for monitoring one or more component carriers included in the list for beam failure using the one or more indicated beam failure detection reference signal sets.

[0131] By including or configuring a communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) may support techniques for reducing processing, reducing power consumption, more efficiently utilizing communication resources, or any combination thereof.

[0132] Figure 6A block diagram 600 of a device 605 supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0133] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to beam failure detection reference signal set updates), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0134] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to beam failure detection reference signal set updates), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0135] The device 605 or its various components may be examples of components for performing various aspects of beam failure detection reference signal set updates as described herein. For example, the communication manager 620 may include a BFD-RS set indication component 625, a CC monitoring component 630, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0136] According to examples as disclosed herein, the communication manager 620 may support wireless communication at a UE. The BFD-RS set indication component 625 may be configured to or otherwise support means for receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier or both based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The CC monitoring component 630 may be configured to or otherwise support means for monitoring one or more component carriers included in the list for beam failure using the one or more indicated beam failure detection reference signal sets.

[0137] Figure 7 A block diagram 700 of a communication manager 720 supporting beam failure detection reference signal set updates according to one or more examples as disclosed herein is illustrated. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of beam failure detection reference signal set updates as described herein. For example, the communication manager 720 may include a BFD-RS set indication component 725, a CC monitoring component 730, a BFD-RS set applicability component 735, a unified CC list component 740, a beam indication component 745, a UE capability component 750, a BFD component 755, a BFD recovery component 760, an NBI component 765, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0138] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communication at the UE. The BFD-RS set indication component 725 may be configured to or otherwise support means for receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier or both based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The CC monitoring component 730 may be configured to or otherwise support means for monitoring one or more component carriers included in the list for beam failure using the one or more indicated beam failure detection reference signal sets.

[0139] In some examples, the indication of one or more beam failure detection reference signal sets indicates a plurality of beam failure detection reference signal sets corresponding to the list of component carriers, and the BFD-RS set applicability component 735 may be configured to or otherwise support components for identifying the plurality of beam failure detection reference signal sets as applicable to each component carrier of the second type included in the list configured for the plurality of beam failure detection reference signal sets based on the plurality of beam failure detection reference signal sets being indicated by the indication. In some examples, the CC monitoring component 730 may be configured to or otherwise support components for monitoring each component carrier of the second type included in the list using each of the plurality of beam failure detection reference signal sets based on the plurality of beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list.

[0140] In some examples, the BFD-RS set applicability component 735 may be configured to or otherwise support identifying the indication of the multiple beam failure detection reference signal sets as not applicable to each component carrier of the first type included in the list that is configured for a single beam failure detection reference signal set based on the multiple beam failure detection reference signal sets being indicated by the indication.

[0141] In some examples, the indication of one or more beam failure detection reference signal sets indicates a single beam failure detection reference signal set corresponding to the list of component carriers, and the BFD-RS set applicability component 735 may be configured to or otherwise support components for identifying the single beam failure detection reference signal set as applicable to each component carrier of the first type included in the list configured for the single beam failure detection reference signal set based on the single beam failure detection reference signal set being indicated by the indication. In some examples, the CC monitoring component 730 may be configured to or otherwise support components for monitoring each component carrier of the first type included in the list using the single beam failure detection reference signal set based on the single beam failure detection reference signal set being applicable to each component carrier of the first type included in the list.

[0142] In some examples, the BFD-RS set applicability component 735 may be configured to or otherwise support identifying the indication for the single beam failure detection reference signal set as not applicable to each component carrier of the second type included in the list that is configured for multiple beam failure detection reference signal sets based on the single beam failure detection reference signal set being indicated by the indication.

[0143] In some examples, the indication of one or more beam failure detection reference signal sets indicates a single beam failure detection reference signal set corresponding to the list of component carriers, and the BFD-RS set applicability component 735 may be configured to or otherwise support components for identifying, based on the multiple beam failure detection reference signal sets indicated by the indication, that a first beam failure detection reference signal set in the multiple beam failure detection reference signal sets is applicable to each component carrier of the first type configured for the single beam failure detection reference signal set. In some examples, the CC monitoring component 730 may be configured to or otherwise support components for monitoring each component carrier of the first type included in the list using the first beam failure detection reference signal set based on the first beam failure detection reference signal set being applicable to each component carrier of the first type included in the list.

[0144] In some examples, the BFD-RS set applicability component 735 may be configured to or otherwise support components for identifying, based on the multiple beam failure detection reference signal sets indicated by the indication, that both the first beam failure detection reference signal set and the second beam failure detection reference signal set in the multiple beam failure detection reference signal sets are applicable to each component carrier of the second type configured for the multiple beam failure detection reference signal sets. In some examples, the CC monitoring component 730 may be configured to or otherwise support components for monitoring each component carrier of the second type included in the list using both the first beam failure detection reference signal set and the second beam failure detection reference signal set based on both the first beam failure detection reference signal set and the second beam failure detection reference signal set being applicable to each component carrier of the second type included in the list.

[0145] In some examples, the list includes only component carriers of the first type configured for the single beam failure detection reference signal set or only component carriers of the second type configured for multiple beam failure detection reference signal sets, and the component carriers of the second type included in the list are each configured for the same number of beam failure detection reference signal sets.

[0146] In some examples, the component carrier of the first type includes a component carrier configured for per-cell beam failure recovery, and wherein the component carrier of the second type includes a component carrier configured for per-transmission and reception point (TRP) beam failure recovery.

[0147] In some examples, the list of component carriers includes a list of component carriers for beam indication.

[0148] In some examples, the BFD-RS set indication component 725 may be configured to or otherwise support components for receiving a second indication of one or more second beam failure detection reference signal sets corresponding to a second list of component carriers, wherein the second list of component carriers does not include any component carrier included in the list of component carriers.

[0149] In some examples, the UE capability component 750 may be configured as or otherwise support components for sending a capability message that may indicate that the UE supports reception of beam failure detection reference signal set indications corresponding to multiple component carriers, the maximum number of applicable component carriers for which the UE supports beam failure detection reference signal set indications, the maximum number of lists of component carriers for which the UE supports beam failure detection reference signal set indications, or any combination thereof.

[0150] In some examples, the BFD component 755 may be configured or otherwise support means for detecting a beam failure within a component carrier of the one or more component carriers in the component carriers included in the list based on monitoring for beam failure. In some examples, the BFD recovery component 760 may be configured or otherwise support means for receiving a beam failure recovery response message in response to sending a beam failure recovery request. In some examples, the BFD recovery component 760 may be configured or otherwise support means for resetting one or more power control parameters for uplink transmission to corresponding default values ​​based on receiving the beam failure recovery response message.

[0151] In some examples, the one or more power control parameters for uplink transmissions are applied to sounding reference signal transmissions, physical uplink control channel transmissions, physical uplink shared channel transmissions, or any combination thereof associated with the transmit and receive points for which the beam failure was detected.

[0152] In some examples, the NBI component 765 can be configured to or otherwise support components for receiving indications of multiple new beam indicator sets. In some examples, the BFD-RS set applicability component 735 can be configured to or otherwise support components for selecting the multiple beam failure detection reference signal sets for the monitoring based on the multiple new beam indicator sets, wherein each beam failure detection reference signal set in the multiple beam failure detection reference signal sets corresponds to a corresponding transmission and reception point, a corresponding control resource set pool, or both.

[0153] Figure 8 A diagram of a system 800 including a device 805 supporting a beam failure detection reference signal set update according to one or more examples as disclosed herein is illustrated. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

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

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

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

[0157] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) so that the device 805 performs various functions (e.g., functions or tasks that support updating of a beam fault detection reference signal set). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0158] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured to or otherwise support a component for receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The communication manager 820 may be configured to or otherwise support a component for monitoring one or more component carriers included in the list for beam failure using the one or more indicated beam failure detection reference signal sets.

[0159] By including or configuring a communication manager 820 according to the examples described herein, the device 805 may support techniques for improving communication reliability, reducing latency, improving user experience related to reduced processing, reducing power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, improving utilization of processing power, or any combination thereof.

[0160] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. For example, the communication manager 820 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 815. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that are executable by the processor 840 to cause the device 805 to perform various aspects of the beam failure detection reference signal set update as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0161] Fig. 9 A flowchart illustrating a method 900 for supporting a beam failure detection reference signal set update according to one or more examples disclosed herein is illustrated. The operations of the method 900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 900 may be implemented by a UE or a component thereof as described herein. Figures 1 to 8The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0162] At 905, the method may include: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The operations of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by as described in reference Figure 7 The described BFD-RS set indicates that the component 725 is executed. Additionally or alternatively, the means for executing 905 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0163] At 910, the method may include: using one or more indicated beam failure detection reference signal sets to monitor one or more component carriers included in the list for beam failure. The operations of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed as described in reference to Figure 7 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0164] Fig.10 A flowchart illustrating a method 1000 for supporting a beam failure detection reference signal set update according to one or more examples disclosed herein is illustrated. The operations of the method 1000 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1000 may be implemented by a UE or a component thereof as described herein. Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0165] At 1005, the method may include: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by as described in reference Figure 7 The described BFD-RS set indicates that the component 725 is executed. Additionally or alternatively, the means for performing 1005 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0166] At 1010, the method may include: based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying the multiple beam failure detection reference signal sets as applicable to each component carrier of the second type included in the list that is configured for the multiple beam failure detection reference signal sets. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figure 7 The BFD-RS set applicability component 735 described above is performed. Additionally or alternatively, the means for performing 1010 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0167] At 1015, the method may include: based on the multiple beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list, using each beam failure detection reference signal set in the multiple beam failure detection reference signal sets to monitor each component carrier of the second type included in the list. The operation of 1015 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1015 may be performed by Figure 7 1015 is performed by the CC monitoring component 730 described above. Additionally or alternatively, the means for performing 1015 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, a processor 840, or any combination thereof.

[0168] Fig.11A flowchart illustrating a method 1100 for supporting a beam failure detection reference signal set update according to one or more examples disclosed herein is illustrated. The operations of the method 1100 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a UE or a component thereof as described herein. Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0169] At 1105, the method may include: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The operations of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed by as described in reference to Figure 7 The described BFD-RS set indicates that the component 725 is executed. Additionally or alternatively, the means for executing 1105 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0170] At 1110, the method may include: based on the single beam failure detection reference signal set being indicated by the indication, identifying the single beam failure detection reference signal set as applicable to each component carrier of the first type included in the list that is configured for the single beam failure detection reference signal set. The operations of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed as described in reference to Figure 7 The BFD-RS set applicability component 735 described above is performed. Additionally or alternatively, the means for performing 1110 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0171] At 1115, the method may include: based on the single beam failure detection reference signal set being applicable to each component carrier of the first type included in the list, using the single beam failure detection reference signal set to monitor each component carrier of the first type included in the list. The operation of 1115 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1115 may be performed as described in reference to Figure 7 1115 is performed by the CC monitoring component 730 described above. Additionally or alternatively, the means for performing 1115 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, a processor 840, or any combination thereof.

[0172] Fig.12 A flowchart illustrating a method 1200 for supporting a beam failure detection reference signal set update according to one or more examples disclosed herein is illustrated. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described herein. Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0173] At 1205, the method may include: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether the component carrier is included in the list or whether the beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by as described in reference to Figure 7 The described BFD-RS set indicates that the component 725 is executed. Additionally or alternatively, the means for performing 1205 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0174] At 1210, the method may include: based on the plurality of beam failure detection reference signal sets being indicated by the indication, identifying that a first beam failure detection reference signal set in the plurality of beam failure detection reference signal sets is applicable to each component carrier of the component carrier of the first type configured for a single beam failure detection reference signal set. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference Figure 7 The BFD-RS set applicability component 735 described above is performed. Additionally or alternatively, the means for performing 1210 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, a processor 840, or any combination thereof.

[0175] At 1215, the method may include: based on the first beam failure detection reference signal set being applicable to each component carrier of the first type included in the list, using the first beam failure detection reference signal set to monitor each component carrier of the first type included in the list. The operation of 1215 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1215 may be performed as described in reference to Figure 7 1215 is performed by the CC monitoring component 730 described above. Additionally or alternatively, the means for performing 1215 may include, for example, a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, a processor 840, or any combination thereof.

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

[0177] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether a component carrier is included in the list or whether a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, is based at least in part on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; and using one or more indicated beam failure detection reference signal sets to monitor one or more component carriers included in the list for beam failures.

[0178] Aspect 2: A method according to Aspect 1, wherein the indication of one or more beam failure detection reference signal sets indicates multiple beam failure detection reference signal sets corresponding to the list of component carriers, and the method further includes: at least partially based on the multiple beam failure detection reference signal sets indicated by the indication, identifying the multiple beam failure detection reference signal sets as applicable to each component carrier of the second type included in the list and configured for multiple beam failure detection reference signal sets, wherein: the monitoring includes: at least partially based on the multiple beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list, using each beam failure detection reference signal set in the multiple beam failure detection reference signal sets to monitor each component carrier of the second type included in the list.

[0179] Aspect 3: According to the method described in Aspect 2, the method also includes: at least in part based on the fact that the multiple beam failure detection reference signal sets are indicated by the indication, identifying the indication of the multiple beam failure detection reference signal sets as not applicable to each component carrier of the first type included in the list and configured for a single beam failure detection reference signal set.

[0180] Aspect 4: A method according to any one of Aspects 2 to 3, wherein the indication of one or more beam failure detection reference signal sets indicates a single beam failure detection reference signal set corresponding to the list of component carriers, and the method further includes: at least partially based on the single beam failure detection reference signal set indicated by the indication, identifying the single beam failure detection reference signal set as applicable to each component carrier of the first type included in the list and configured for the single beam failure detection reference signal set, wherein: the monitoring includes: at least partially based on the single beam failure detection reference signal set being applicable to each component carrier of the first type included in the list, using the single beam failure detection reference signal set to monitor each component carrier of the first type included in the list.

[0181] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: at least in part based on the single beam fault detection reference signal set being indicated by the indication, identifying the indication of the single beam fault detection reference signal set as not applicable to each component carrier of the second type included in the list and configured for multiple beam fault detection reference signal sets.

[0182] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the indication of one or more beam failure detection reference signal sets indicates multiple beam failure detection reference signal sets corresponding to the list of component carriers, and the method further includes: at least partially based on the multiple beam failure detection reference signal sets indicated by the indication, identifying that a first beam failure detection reference signal set in the multiple beam failure detection reference signal sets is applicable to each component carrier of the first type configured for a single beam failure detection reference signal set, wherein: the monitoring includes: at least partially based on the first beam failure detection reference signal set being applicable to each component carrier of the second type included in the list, using the first beam failure detection reference signal set to monitor each component carrier of the first type included in the list.

[0183] Aspect 7: According to the method described in Aspect 6, the method further includes: at least partially based on the multiple beam failure detection reference signal sets indicated by the indication, identifying that both the first beam failure detection reference signal set and the second beam failure detection reference signal set in the multiple beam failure detection reference signal sets are applicable to each component carrier of the second type configured for multiple beam failure detection reference signal sets, wherein: the monitoring includes: at least partially based on the first beam failure detection reference signal set and the second beam failure detection reference signal set being applicable to each component carrier of the second type included in the list, using both the first beam failure detection reference signal set and the second beam failure detection reference signal set to monitor each component carrier of the second type included in the list.

[0184] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the list includes only component carriers of the first type configured for the single beam fault detection reference signal set or only component carriers of the second type configured for multiple beam fault detection reference signal sets, and the component carriers of the second type included in the list are each configured for the same number of beam fault detection reference signal sets.

[0185] Aspect 9: A method according to Aspect 8, wherein the component carrier of the first type includes a component carrier configured for per-cell beam failure recovery, and wherein the component carrier of the second type includes a component carrier configured for per-transmit and receive point (TRP) beam failure recovery.

[0186] Aspect 10: The method according to any one of aspects 1 to 9, wherein the list of component carriers comprises a list of component carriers for beam indication.

[0187] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a second indication of one or more second beam failure detection reference signal sets corresponding to a second list of component carriers, wherein the second list of component carriers does not include any component carrier included in the list of component carriers.

[0188] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: sending a capability message indicating that the UE supports the reception of beam failure detection reference signal set indications corresponding to multiple component carriers, the maximum number of applicable component carriers supported by the UE for the beam failure detection reference signal set indication, the maximum number of lists of component carriers supported by the UE for the beam failure detection reference signal set indication, or any combination thereof.

[0189] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method further includes: detecting a beam failure within a component carrier among the one or more component carriers included in the list based at least in part on monitoring of the beam failure; receiving a beam failure recovery response message in response to sending a beam failure recovery request; and resetting one or more power control parameters used for uplink transmission to corresponding default values ​​based at least in part on receiving the beam failure recovery response message.

[0190] Aspect 14: A method according to Aspect 13, wherein the one or more power control parameters for uplink transmission are applied to the sounding reference signal transmission, physical uplink control channel transmission, physical uplink shared channel transmission, or any combination thereof associated with the transmission and receiving points for which the beam failure is detected.

[0191] Aspect 15: According to the method described in any one of Aspects 1 to 14, the method further includes: receiving an indication of multiple new beam indicator sets; and selecting the multiple beam fault detection reference signal sets for the monitoring based at least in part on the multiple new beam indicator sets, wherein each beam fault detection reference signal set in the multiple beam fault detection reference signal sets corresponds to a corresponding transmitting and receiving point, a corresponding control resource set pool, or both.

[0192] Aspect 16: An apparatus comprising: a memory; a transceiver; and at least one processor, the at least one processor being coupled to the memory and the transceiver, the at least one processor being configured to execute the method according to any one of Aspects 1 to 15.

[0193] Aspect 17: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 15.

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

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

[0196] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0197] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

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

[0199] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0200] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer programs from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used to carry or store desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0201] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0202] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0203] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.

[0204] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0205] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether a component carrier is included in the list or a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, is based at least in part on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; as well as One or more component carriers included in the list are monitored for beam failure using the one or more indicated sets of beam failure detection reference signals.

2. The method of claim 1 , wherein the indication of one or more beam failure detection reference signal sets indicates a plurality of beam failure detection reference signal sets corresponding to the list of component carriers, the method further comprising: identifying the plurality of beam failure detection reference signal sets as applicable to each component carrier of the second type included in the list and configured for the plurality of beam failure detection reference signal sets based at least in part on the plurality of beam failure detection reference signal sets being indicated by the indication, wherein: The monitoring includes monitoring each component carrier of the second type included in the list using each beam failure detection reference signal set in the multiple beam failure detection reference signal sets based at least in part on the multiple beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list.

3. The method according to claim 2, further comprising: At least in part based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying the indication of the multiple beam failure detection reference signal sets as not applicable to each component carrier of the first type included in the list that is configured for a single beam failure detection reference signal set.

4. The method of claim 1 , wherein the indication of one or more beam failure detection reference signal sets indicates a single beam failure detection reference signal set corresponding to the list of component carriers, the method further comprising: identifying the single beam failure detection reference signal set as applicable to each component carrier of the first type included in the list that is configured for the single beam failure detection reference signal set based at least in part on the single beam failure detection reference signal set being indicated by the indication, wherein: The monitoring includes: at least partly based on the single beam failure detection reference signal set being applicable to each component carrier of the first type included in the list, and using the single beam failure detection reference signal set to monitor each component carrier of the first type included in the list.

5. The method according to claim 4, further comprising: At least in part based on the single beam failure detection reference signal set being indicated by the indication, identifying the indication for the single beam failure detection reference signal set as not applicable to each component carrier of the second type included in the list that is configured for multiple beam failure detection reference signal sets.

6. The method of claim 1 , wherein the indication of one or more beam failure detection reference signal sets indicates a plurality of beam failure detection reference signal sets corresponding to the list of component carriers, the method further comprising: identifying, based at least in part on the plurality of beam failure detection reference signal sets being indicated by the indication, that a first beam failure detection reference signal set in the plurality of beam failure detection reference signal sets is applicable to each of the component carriers of the first type configured for a single beam failure detection reference signal set, wherein: The monitoring includes: at least partly based on the first beam failure detection reference signal set being applicable to each component carrier of the first type included in the list, using the first beam failure detection reference signal set to monitor each component carrier of the first type included in the list.

7. The method according to claim 6, further comprising: At least in part based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying that both the first beam failure detection reference signal set and the second beam failure detection reference signal set in the multiple beam failure detection reference signal sets are applicable to each component carrier of the component carriers belonging to the second type configured for the multiple beam failure detection reference signal sets, wherein: The monitoring includes: at least partially based on the fact that both the first beam failure detection reference signal set and the second beam failure detection reference signal set are applicable to each component carrier of the second type included in the list, and using both the first beam failure detection reference signal set and the second beam failure detection reference signal set to monitor each component carrier of the second type included in the list.

8. The method according to claim 1, wherein the list includes only component carriers of the first type configured for the single beam failure detection reference signal set or only component carriers of the second type configured for multiple beam failure detection reference signal sets, and the component carriers of the second type included in the list are each configured for the same number of beam failure detection reference signal sets.

9. The method of claim 1, wherein the component carrier of the first type comprises a component carrier configured for per-cell beam failure recovery, and wherein the component carrier of the second type comprises a component carrier configured for per-transmit and receive point (TRP) beam failure recovery.

10. The method of claim 1, wherein the list of component carriers comprises a list of component carriers for beam indication.

11. The method according to claim 1, further comprising: A second indication of one or more second sets of beam failure detection reference signals corresponding to a second list of component carriers is received, wherein the second list of component carriers does not include any component carrier included in the list of component carriers.

12. The method according to claim 1, further comprising: Send a capability message, wherein the capability message indicates that the UE supports reception of beam failure detection reference signal set indications corresponding to multiple component carriers, the maximum number of applicable component carriers supported by the UE for the beam failure detection reference signal set indication, the maximum number of a list of component carriers supported by the UE for the beam failure detection reference signal set indication, or any combination thereof.

13. The method according to claim 1, further comprising: detecting a beam failure within a component carrier of the one or more of the component carriers included in the list based at least in part on monitoring for beam failure; In response to sending a beam failure recovery request, receiving a beam failure recovery response message; as well as One or more power control parameters for uplink transmissions are reset to corresponding default values ​​based at least in part on receiving the beam failure recovery response message.

14. A method according to claim 13, wherein the one or more power control parameters for uplink transmissions are applied to sounding reference signal transmissions, physical uplink control channel transmissions, physical uplink shared channel transmissions, or any combination thereof associated with the transmission and reception points for which the beam failure is detected.

15. The method according to claim 1, further comprising: receiving an indication of a plurality of new beam indicator sets; as well as The multiple beam failure detection reference signal sets for the monitoring are selected at least in part based on the multiple new beam indicator sets, wherein each beam failure detection reference signal set in the multiple beam failure detection reference signal sets corresponds to a corresponding transmission and reception point, a corresponding control resource set pool, or both.

16. An apparatus for wireless communication, the apparatus comprising: Memory; Transceiver; and At least one processor of a user equipment (UE), the at least one processor coupled to the memory and the transceiver, and the at least one processor configured to: receiving, via the transceiver, an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether a component carrier is included in the list or a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, based at least in part on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for a plurality of beam failure detection reference signal sets; as well as One or more component carriers included in the list are monitored for beam failure using the one or more indicated sets of beam failure detection reference signals.

17. The apparatus of claim 16, wherein the indication of one or more beam failure detection reference signal sets indicates a plurality of beam failure detection reference signal sets corresponding to the list of component carriers, and the at least one processor is further configured to: identifying the plurality of beam failure detection reference signal sets as applicable to each component carrier of the second type included in the list and configured for the plurality of beam failure detection reference signal sets based at least in part on the plurality of beam failure detection reference signal sets being indicated by the indication, wherein: In order to monitor the one or more component carriers, the at least one processor is configured to: monitor each component carrier of the second type included in the list using each beam failure detection reference signal set in the multiple beam failure detection reference signal sets, at least in part based on the multiple beam failure detection reference signal sets being applicable to each component carrier of the second type included in the list.

18. The apparatus of claim 17, wherein the at least one processor is further configured to: At least in part based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying the indication of the multiple beam failure detection reference signal sets as not applicable to each component carrier of the first type included in the list that is configured for a single beam failure detection reference signal set.

19. The apparatus of claim 17, wherein the indication of one or more beam failure detection reference signal sets indicates a single beam failure detection reference signal set corresponding to the list of component carriers, the at least one processor being further configured to: and identifying, based at least in part on the single beam failure detection reference signal set being indicated by the indication, the indication for the single beam failure detection reference signal set as not applicable to each component carrier included in the list and belonging to the second type configured for multiple beam failure detection reference signal sets, wherein: In order to monitor the one or more component carriers, the at least one processor is configured to monitor each component carrier of the first type included in the list using the single beam failure detection reference signal set based at least in part on the fact that the single beam failure detection reference signal set is applicable to each component carrier of the first type included in the list.

20. The apparatus of claim 19, wherein the at least one processor is further configured to: At least in part based on the single beam failure detection reference signal set being indicated by the indication, identifying the indication for the single beam failure detection reference signal set as not applicable to each component carrier of the second type included in the list that is configured for multiple beam failure detection reference signal sets.

21. The apparatus of claim 16, wherein the indication of one or more beam failure detection reference signal sets indicates a plurality of beam failure detection reference signal sets corresponding to the list of component carriers, the at least one processor being further configured to: identifying, based at least in part on the plurality of beam failure detection reference signal sets being indicated by the indication, that a first beam failure detection reference signal set in the plurality of beam failure detection reference signal sets is applicable to each of the component carriers of the first type configured for a single beam failure detection reference signal set, wherein: In order to monitor the one or more component carriers, the at least one processor is configured to: use the first beam failure detection reference signal set to monitor each component carrier of the first type included in the list based at least in part on the first beam failure detection reference signal set being applicable to each component carrier of the first type included in the list.

22. The apparatus of claim 21 , wherein the at least one processor is further configured to: At least in part based on the multiple beam failure detection reference signal sets being indicated by the indication, identifying that both the first beam failure detection reference signal set and the second beam failure detection reference signal set in the multiple beam failure detection reference signal sets are applicable to each component carrier of the component carriers belonging to the second type configured for the multiple beam failure detection reference signal sets, wherein: In order to monitor the one or more component carriers, the at least one processor is configured to: monitor each component carrier of the second type included in the list using both the first beam failure detection reference signal set and the second beam failure detection reference signal set, at least in part based on the fact that both the first beam failure detection reference signal set and the second beam failure detection reference signal set are applicable to each component carrier of the second type included in the list.

23. An apparatus according to claim 16, wherein the list includes only component carriers of the first type configured for the single beam failure detection reference signal set or only component carriers of the second type configured for multiple beam failure detection reference signal sets, and the component carriers of the second type included in the list are each configured for the same number of beam failure detection reference signal sets.

24. The apparatus of claim 16, wherein the list of component carriers comprises a list of component carriers for beam indication.

25. The apparatus of claim 16, wherein the at least one processor is further configured to: A second indication of one or more second sets of beam failure detection reference signals corresponding to a second list of component carriers is received via the transceiver, wherein the second list of component carriers does not include any component carrier included in the list of component carriers.

26. The apparatus of claim 16, wherein the at least one is further configured to: A capability message is sent via the transceiver, the capability message indicating that the UE supports reception of beam failure detection reference signal set indications corresponding to multiple component carriers, the maximum number of applicable component carriers supported by the UE for the beam failure detection reference signal set indication, the maximum number of a list of component carriers supported by the UE for the beam failure detection reference signal set indication, or any combination thereof.

27. The apparatus of claim 16, wherein the at least one processor is further configured to: detecting a beam failure within a component carrier of the one or more of the component carriers included in the list based at least in part on monitoring for beam failure; receiving, via the transceiver, a beam failure recovery response message in response to transmitting the beam failure recovery request; and One or more power control parameters for uplink transmissions are reset to corresponding default values ​​based at least in part on receiving the beam failure recovery response message.

28. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving, via the transceiver, an indication of a plurality of new beam indicator sets; and The multiple beam failure detection reference signal sets for the monitoring are selected at least in part based on the multiple new beam indicator sets, wherein each beam failure detection reference signal set in the multiple beam failure detection reference signal sets corresponds to a corresponding transmission and reception point, a corresponding control resource set pool, or both.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether a component carrier is included in the list or a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, is based at least in part on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for a plurality of beam failure detection reference signal sets; and Means for monitoring one or more component carriers included in the list for beam failure using one or more indicated sets of beam failure detection reference signals.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: receiving an indication of one or more beam failure detection reference signal sets corresponding to a list of component carriers, wherein whether a component carrier is included in the list or a beam failure detection reference signal set in the one or more beam failure detection reference signal sets is applicable to the component carrier, or both, is based at least in part on whether the component carrier belongs to a first type configured for a single beam failure detection reference signal set or a second type configured for multiple beam failure detection reference signal sets; and One or more component carriers included in the list are monitored for beam failure using the one or more indicated sets of beam failure detection reference signals.