CONFIGURATION OF BEAM FAILURE RECOVERY SEARCH SPACE SET FOR PHYSICAL DOWNLINK CONTROL CHANNEL REPETITION

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive information configuring a first search space (SS) set and a second SS set, wherein the first SS set is linked with the second SS set for physical downlink control channel (PDCCH) repetition, and wherein the first SS set is a recovery search space identifier configured SS set. The UE may monitor for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response downlink control information (DCI). Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for configuration of beam failure recovery synchronization signal.

BACKGROUND

A wireless network may include one or more network entities that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the base station to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the base station.

SUMMARY

Some communications systems may allow physical downlink control channel (PDCCH) repetition with linked PDCCH candidates across linked search space (SS) sets. However, behavior of a user equipment (UE) and a network node (e.g., a base station) may not be deterministic, which may result in a loss of synchronization between the UE and the network node, such as when the UE is provided by a first operator and has a first behavior and the network node is provided by a second operator and has a second behavior. As a result, some messages may be dropped and/or poor communication performance may be experienced. Some aspects described herein provide for configuration of an SS set associated with beam failure recovery (e.g., the recoverySearchSpacelD SS set) when linked SS sets are enabled for a UE. For example, in a first case, the beam failure recovery SS set may not be permitted to be linked with any other search space set, and PDCCH repetition may be disabled for a beam failure recovery response PDCCH. In a second case, a first SS set (e.g., the beam failure recovery SS set) may be linked with a second SS set when the first SS set and the second SS set share a common configuration, such as sharing the same CORESET. In a third case, a first SS set (e.g., the beam failure recovery SS set) may be linked with a second SS set even when the first SS set and the second SS set do not share a common configuration, such as a common CORESET. In each case, behavior of a UE is defined, thereby enabling the UE to operate with linked PDCCH candidates enabled without ambiguity in the UE's behavior resulting in dropped communications or failure to complete a beam failure recovery procedure.

Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the UE to receive, in a recovery search space identifier message, configuration information identifying a configuration of a first search space (SS) set, wherein the first SS set is configured for beam failure recovery monitoring. The instructions may be executable by the one or more processors to cause the UE to monitor, in a first monitoring occasion, the first SS set. The instructions may be executable by the one or more processors to cause the UE to monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring. The apparatus may include means for monitoring, in a first monitoring occasion, the first SS set. The apparatus may include means for monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication. The set of instructions, when executed by one or more processors of a UE, may cause the UE to receive, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring. The set of instructions, when executed by one or more processors of a UE, may cause the UE to monitor, in a first monitoring occasion, the first SS set. The set of instructions, when executed by one or more processors of a UE, may cause the UE to monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, in a recovery search space identifier message (e.g., a message associated with a recovery search space identifier), configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring. The method may include monitoring, in a first monitoring occasion, the first SS set. The method may include monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set.

Some aspects described herein relate to a UE for wireless communication. The UE may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the UE to monitor, in a first monitoring occasion, a first SS set. The instructions may be executable by the one or more processors to cause the UE to monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set.

Some aspects described herein relate to a UE for wireless communication. The UE may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the UE to receive information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for physical downlink control channel (PDCCH) repetition, and wherein the first SS set is a recovery search space identifier configured SS set. The instructions may be executable by the one or more processors to cause the UE to monitor for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response downlink control information (DCI).

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include monitoring, in a first monitoring occasion, a first SS set. The method may include monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for PDCCH repetition, and wherein the first SS set is a recovery search space identifier configured SS set. The method may include monitoring for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI.

Some aspects described herein relate to a non-transitory computer-readable medium that stores one or more instructions for wireless communication by a UE. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to monitor, in a first monitoring occasion, a first SS set. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set.

Some aspects described herein relate to a non-transitory computer-readable medium that stores one or more instructions for wireless communication by a UE. The one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to receive information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for PDCCH repetition, and wherein the first SS set is a recovery search space identifier configured SS set. The one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors of the UE to monitor for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for monitoring, in a first monitoring occasion, a first SS set. The apparatus may include means for monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for PDCCH repetition, and wherein the first SS set is a recovery search space identifier configured SS set. The apparatus may include means for monitoring for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI.

DETAILED DESCRIPTION

FIG.1is a diagram illustrating an example of a wireless network100, in accordance with the present disclosure. The wireless network100may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network100may include one or more network entities110(shown as a network node (NN)110a, a NN110b, a NN110c, and a NN110d), a user equipment (UE)120or multiple UEs120(shown as a UE120a, a UE120b, a UE120c, a UE120d, and a UE120e), and/or other network entities. A network entity110is an entity that communicates with UEs120. A network entity110(sometimes referred to as a base station or BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP). Each network entity110may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network entity110and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.

A network entity110may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs120with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs120with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs120having association with the femto cell (e.g., UEs120in a closed subscriber group (CSG)). A network entity110for a macro cell may be referred to as a macro base station. A network entity110for a pico cell may be referred to as a pico base station. A network entity110for a femto cell may be referred to as a femto base station or an in-home base station. In the example shown inFIG.1, the NN110amay be a macro base station for a macro cell102a, the NN110bmay be a pico base station for a pico cell102b, and the NN110cmay be a femto base station for a femto cell102c. A base station may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network entity110that is mobile (e.g., a mobile base station). In some examples, the network entities110may be interconnected to one another and/or to one or more other network entities110or network nodes (not shown) in the wireless network100through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.

The wireless network100may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a network entity110or a UE120) and send a transmission of the data to a downstream station (e.g., a UE120or a network entity110). A relay station may be a UE120that can relay transmissions for other UEs120. In the example shown inFIG.1, the NN110d(e.g., a relay base station) may communicate with the NN110a(e.g., a macro base station) and the UE120din order to facilitate communication between the NN110aand the UE120d. A network entity110that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.

The wireless network100may be a heterogeneous network that includes network entities110of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of network entities110may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller130may couple to or communicate with a set of network entities110and may provide coordination and control for these network entities110. The network controller130may communicate with the network entities110via a backhaul communication link. The network entities110may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may monitor, in a first monitoring occasion, a first search space (SS) set; and monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set. Additionally, or alternatively, the communication manager140may receive information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for PDCCH repetition, wherein the first SS set is a recovery search space identifier configured SS set; and monitor for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI. Additionally, or alternatively, the communication manager140may receive, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring; monitor, in a first monitoring occasion, the first SS set; and monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

FIG.2is a diagram illustrating an example200of a network entity110in communication with a UE120in a wireless network100, in accordance with the present disclosure. The network entity110may be equipped with a set of antennas234athrough234t, such as T antennas (T≥1). The UE120may be equipped with a set of antennas252athrough252r, such as R antennas (R≥1).

The network controller130may include a communication unit294, a controller/processor290, and a memory292. The network controller130may include, for example, one or more devices in a core network. The network controller130may communicate with the network entity110via the communication unit294.

In some aspects, a UE (e.g., the UE120) includes means for monitoring, in a first monitoring occasion, a first SS set; and/or means for monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set. In some aspects, the UE includes means for receiving information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for PDCCH repetition, wherein the first SS set is a recovery search space identifier configured SS set; and/or means for monitoring for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI. In some aspects, the UE includes means for receiving, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring; means for monitoring, in a first monitoring occasion, the first SS set; and means for monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set. The means for the UE to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

FIG.3is a diagram illustrating an example300of physical channels and reference signals in a wireless network, in accordance with the present disclosure. As shown inFIG.3, downlink channels and downlink reference signals may carry information from a network entity110to a UE120, and uplink channels and uplink reference signals may carry information from a UE120to a network entity110.

As shown, a downlink channel may include a physical downlink control channel (PDCCH) that carries DCI (e.g., DCI may be received in a PDCCH candidate that UE120monitors in a search space (SS) set and decodes using blind decoding), a physical downlink shared channel (PDSCH) that carries downlink data, or a physical broadcast channel (PBCH) that carries system information, among other examples. PDSCH communications may be scheduled by PDCCH communications. The UE120may monitor for downlink communications in a monitoring occasion (MO). For example, the UE120may monitor for a PDCCH candidate in a PDCCH MO. Each PDCCH candidate may be defined in connection with SS set configuration. For example, the UE120may receive configuration information identifying a control resource set (CORESET), an associated active transmission configuration indicator (TCI) state, or an associated SS set, among other examples, as described in more detail herein. A configuration for the CORESET (e.g., which the UE120may receive via radio resource control (RRC) signaling) may include a configuration for a quantity of resource blocks in a CORESET, a frequency domain configuration, or a quantity of symbols in the CORESET, among other examples.

The SS set may be configured for a bandwidth part and associated with the CORESET. For example, up to 10 SS sets may be configured in a bandwidth part of a component carrier, and the UE120may receive signaling identifying an SS set that is associated with a configured CORESET. In this case, SS set configuration information (e.g., which the UE120may receive via RRC signaling) may include information identifying an associated CORESET, a monitoring slot periodicity and offset (e.g., information identifying which PDCCH MOs are associated with the SS set), an SS set type (e.g., whether a configured SS set is a common search space (CSS) or a UE-specific search space (USS)), a set of DCI formats to monitor in the PDCCH MOs, or a quantity of PDCCH candidates associated with a particular aggregation level (e.g., a quantity of control channel elements (CCEs)), among other examples.

As further shown, an uplink channel may include a physical uplink control channel (PUCCH) that carries uplink control information (UCI), a physical uplink shared channel (PUSCH) that carries uplink data, or a physical random access channel (PRACH) used for initial network access, among other examples. The UE120may transmit acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK/NACK feedback or ACK/NACK information) in UCI on the PUCCH and/or the PUSCH.

As further shown, a downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (RS) (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), among other examples. As also shown, an uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, among other examples.

An SSB may carry information used for initial network acquisition and synchronization, such as a PSS, an SSS, a PBCH, and a PBCH DMRS. An SSB is sometimes referred to as a synchronization signal/PBCH (SS/PBCH) block. The network entity110may transmit multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

A CSI-RS may carry information used for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other examples. The network entity110may configure a set of CSI-RSs for the UE120, and the UE120may measure the configured set of CSI-RSs. Based at least in part on the measurements, the UE120may perform channel estimation and may report channel estimation parameters to the network entity110(e.g., in a CSI report), such as a CQI, a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or an RSRP, among other examples. The network entity110may use the CSI report to select transmission parameters for downlink communications to the UE120, such as a number of transmission layers (e.g., a rank), a precoding matrix (e.g., a precoder), an MCS, or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

A DMRS may carry information used to estimate a radio channel for demodulation of an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of a DMRS may be specific to a physical channel for which the DMRS is used for estimation. DMRSs are UE-specific, can be beamformed, can be confined in a scheduled resource (e.g., rather than transmitted on a wideband), and can be transmitted only when necessary. As shown, DMRSs are used for both downlink communications and uplink communications.

A PTRS may carry information used to compensate for oscillator phase noise. Typically, the phase noise increases as the oscillator carrier frequency increases. Thus, PTRS can be utilized at high carrier frequencies, such as millimeter wave frequencies, to mitigate phase noise. The PTRS may be used to track the phase of the local oscillator and to enable suppression of phase noise and common phase error (CPE). As shown, PTRSs are used for both downlink communications (e.g., on the PDSCH) and uplink communications (e.g., on the PUSCH).

A PRS may carry information used to enable timing or ranging measurements of the UE120based on signals transmitted by the network entity110to improve observed time difference of arrival (OTDOA) positioning performance. For example, a PRS may be a pseudo-random Quadrature Phase Shift Keying (QPSK) sequence mapped in diagonal patterns with shifts in frequency and time to avoid collision with cell-specific reference signals and control channels (e.g., a PDCCH). In general, a PRS may be designed to improve detectability by the UE120, which may need to detect downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Accordingly, the UE120may receive a PRS from multiple cells (e.g., a reference cell and one or more neighbor cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRSs received from the multiple cells. The network entity110may then calculate a position of the UE120based on the RSTD measurements reported by the UE120.

An SRS may carry information used for uplink channel estimation, which may be used for scheduling, link adaptation, precoder selection, or beam management, among other examples. The network entity110may configure one or more SRS resource sets for the UE120, and the UE120may transmit SRSs on the configured SRS resource sets. An SRS resource set may have a configured usage, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operations, uplink beam management, among other examples. The network entity110may measure the SRSs, may perform channel estimation based at least in part on the measurements, and may use the SRS measurements to configure communications with the UE120.

FIG.4is a diagram illustrating examples400of carrier aggregation, in accordance with the present disclosure.

Carrier aggregation is a technology that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., into a single channel) for a single UE120to enhance data capacity. As shown, carriers can be combined in the same or different frequency bands. Additionally, or alternatively, contiguous or non-contiguous carriers can be combined. A network entity110may configure carrier aggregation for a UE120, such as in an RRC message, downlink control information (DCI), and/or another signaling message.

As shown by reference number405, in some aspects, carrier aggregation may be configured in an intra-band contiguous mode where the aggregated carriers are contiguous to one another and are in the same band. As shown by reference number410, carrier aggregation may be configured in an intra-band non-contiguous mode where the aggregated carriers are non-contiguous to one another and are in the same band. As shown by reference number415, carrier aggregation may be configured in an inter-band non-contiguous mode where the aggregated carriers are non-contiguous to one another and are in different bands.

In carrier aggregation, a UE120may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). The primary carrier, which may be referred to as a “primary component carrier” (PCC), may carry control information (e.g., downlink control information and/or scheduling information) for scheduling data communications on one or more secondary carriers (which may be referred to as a “secondary component carrier” (SCC)). This scenario may be referred to as “cross-carrier scheduling”. A carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.

FIG.5is a diagram illustrating an example500of using beams for communications between a base station and a UE, in accordance with the present disclosure. As shown inFIG.5, a network entity110and a UE120may communicate with one another.

The network entity110may transmit to UEs120located within a coverage area of the network entity110. The network entity110and the UE120may be configured for beamformed communications, where the network entity110may transmit in the direction of the UE120using a directional BS transmit beam, and the UE120may receive the transmission using a directional UE receive beam. Each BS transmit beam may have an associated beam ID, beam direction, or beam symbols, among other examples. The network entity110may transmit downlink communications via one or more BS transmit beams505.

The UE120may attempt to receive downlink transmissions via one or more UE receive beams510, which may be configured using different beamforming parameters at receive circuitry of the UE120. The UE120may identify a particular BS transmit beam505, shown as BS transmit beam505-A, and a particular UE receive beam510, shown as UE receive beam510-A, that provide relatively favorable performance (for example, that have a best channel quality of the different measured combinations of BS transmit beams505and UE receive beams510). In some examples, the UE120may transmit an indication of which BS transmit beam505is identified by the UE120as a preferred BS transmit beam, which the network entity110may select for transmissions to the UE120. The UE120may thus attain and maintain a beam pair link (BPL) with the network entity110for downlink communications (for example, a combination of the BS transmit beam505-A and the UE receive beam510-A), which may be further refined and maintained in accordance with one or more established beam refinement procedures.

A downlink beam, such as a BS transmit beam505or a UE receive beam510, may be associated with a TCI state. A TCI state may indicate a directionality or a characteristic of the downlink beam, such as one or more quasi-co-location (QCL) properties of the downlink beam. A QCL property may include, for example, a Doppler shift, a Doppler spread, an average delay, a delay spread, or spatial receive parameters, among other examples. In some examples, each BS transmit beam505may be associated with an SSB, and the UE120may indicate a preferred BS transmit beam505by transmitting uplink transmissions in resources of the SSB that are associated with the preferred BS transmit beam505. A particular SSB may have an associated TCI state (for example, for an antenna port or for beamforming). The network entity110may, in some examples, indicate a downlink BS transmit beam505based at least in part on antenna port QCL properties that may be indicated by the TCI state. A TCI state may be associated with one downlink reference signal set (for example, an SSB and an aperiodic, periodic, or semi-persistent CSI-RS) for different QCL types (for example, QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial receive parameters, among other examples). In cases where the QCL type indicates spatial receive parameters, the QCL type may correspond to analog receive beamforming parameters of a UE receive beam510at the UE120. Thus, the UE120may select a corresponding UE receive beam510from a set of BPLs based at least in part on the network entity110indicating a BS transmit beam505via a TCJ indication.

The network entity110may maintain a set of activated TCJ states for downlink shared channel transmissions and a set of activated TCJ states for downlink control channel transmissions. The set of activated TCJ states for downlink shared channel transmissions may correspond to beams that the network entity110uses for downlink transmission on a PDSCH. The set of activated TCJ states for downlink control channel communications may correspond to beams that the network entity110may use for downlink transmission on a PDCCH or in a CORESET. The UE120may also maintain a set of activated TCJ states for receiving the downlink shared channel transmissions and the CORESET transmissions. If a TCJ state is activated for the UE120, then the UE120may have one or more antenna configurations based at least in part on the TCJ state, and the UE120may not need to reconfigure antennas or antenna weighting configurations. In some examples, the set of activated TCJ states (for example, activated PDSCH TCJ states and activated CORESET TCJ states) for the UE120may be configured by a configuration message, such as an RRC message.

Similarly, for uplink communications, the UE120may transmit in the direction of the network entity110using a directional UE transmit beam, and the network entity110may receive the transmission using a directional BS receive beam. Each UE transmit beam may have an associated beam ID, beam direction, or beam symbols, among other examples. The UE120may transmit uplink communications via one or more UE transmit beams515.

The network entity110may receive uplink transmissions via one or more BS receive beams520. The network entity110may identify a particular UE transmit beam515, shown as UE transmit beam515-A, and a particular BS receive beam520, shown as BS receive beam520-A, that provide relatively favorable performance (for example, that have a best channel quality of the different measured combinations of UE transmit beams515and BS receive beams520). In some examples, the network entity110may transmit an indication of which UE transmit beam515is identified by the network entity110as a preferred UE transmit beam, which the network entity110may select for transmissions from the UE120. The UE120and the network entity110may thus attain and maintain a BPL for uplink communications (for example, a combination of the UE transmit beam515-A and the BS receive beam520-A), which may be further refined and maintained in accordance with one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam515or a BS receive beam520, may be associated with a spatial relation. A spatial relation may indicate a directionality or a characteristic of the uplink beam, similar to one or more QCL properties, as described above.

FIG.6is a diagram illustrating examples600/600′ of linked PDCCH candidates, in accordance with the present disclosure.

In some communications systems, linking of PDCCH candidates may be enabled in connection with PDCCH repetition. When a first PDCCH candidate is linked with a second PDCCH candidate, the first PDCCH candidate and the second PDCCH candidate may have the same aggregation level (e.g., the same quantity of CCEs) and may convey the same DCI payload. In this case, a UE may be configured with information identifying the linking between the first PDCCH candidate and the second PDCCH candidate, and may individually decode each PDCCH candidate or use soft-combining to decode the two PDCCH candidates together.

The UE may receive RRC configuration information identifying the linking between SS sets that include the PDCCH candidate. For example, the UE may identify a first SS set with a first one or more PDCCH candidates and a second SS set with a second one or more PDCCH candidates. In this case, first MOs of the first SS set are one-to-one mapped to second MOs of the second SS set. For example, as shown by example600, in intra-slot PDCCH repetition, a UE may be configured to monitor first PDCCH candidates in MO1 of the first SS set and second PDCCH candidates in MO1 of the second SS set, which may be linked SS sets. Similarly, as shown in example600′, in intra-slot PDCCH repetition, the UE may be configured to monitor linked PDCCH candidates in respective MO1s of the first SS set and the second SS set, and to monitor linked PDCCH candidates in respective MO2s of the first SS set and the second SS set. Although the aforementioned examples are described in terms of intra-slot PDCCH repetition, inter-slot PDCCH repetition is also contemplated.

FIG.7is a diagram illustrating an example700of beam failure recovery, in accordance with the present disclosure. As shown inFIG.7, example700includes a UE705and a network node710. Network node710may be associated with a PCell or a primary secondary cell (PScell).

As further shown inFIG.7, and by reference numbers750and755, UE705may detect a beam failure based at least in part on attempting to receive a beam failure detection (BFD) reference signal (RS). For example, network node710may transmit BFD RSs associated with periodic CSI-RS resources configured for UE705using RRC signaling (e.g., an RRC parameterfailureDetectionResources). At a physical layer, UE705may assess a radio link quality associated with a BFD RS set against a threshold quality level (e.g., a parameter Q-_out). In this case, if the radio link quality does not satisfy the threshold quality level, the physical layer of UE705may pass a beam failure detection indication to a higher layer (e.g., a medium access control (MAC) layer, an RRC layer, an application (APP) layer, etc.) indicating a beam failure.

As further shown inFIG.7, and by reference number760, UE705may initiate a random access channel (RACH) procedure to initiate beam recovery. For example, UE705may perform candidate beam detection (CBD) based at least in part on a periodic CSI-RS resource or SSB resource (e.g., which network node710may configure for UE705using RRC signaling, such as an RRC parameter canddiateBeamRSList). UE705may identify an RS index (q_new) for beams with an RSRP that satisfies a threshold (e.g., a parameter Q_in). UE705initiates a contention-free RACH procedure based at least in part on a random access resource (e.g., a parameter ra-preamble-index) associated with the identified RS index (e.g., which may be represented by the parameter q_new).

As further shown inFIG.7, and by reference number765, UE705may monitor for a beam failure recovery response from network node710. For example, UE705may monitor for a PDCCH in an SS set indicated by a parameter recoverySearchSpacefD to detect DCI with a DCI format associated with a beam failure recovery response. A CORESET associated with the recoverySearchSpacefD may be unique to the SS set for beam failure recovery (e.g., the CORESET may not be used by other SS sets). UE705may use QCL parameters associated with q_new for PDCCH monitoring in the SS set and for receiving a corresponding PDSCH. Alternatively, when UE705receives configuration information activating a TCI state or one or more parameters associated therewith, UE705may use QCL parameters associated with the TCI state for monitoring in an SS set or for a corresponding PDSCH. The DCI format may have a cyclic redundancy check (CRC) that is scrambled based at least in part on a cell-specific radio network temporary identifier (C-RNTI) or an MCS C-RNTI (MCS-C-RNTI). If UE705receives a PDCCH with DCI including a beam failure recovery response within a configured window, beam failure recovery is complete for UE705.

As described above, some communications systems may allow PDCCH repetition with linked PDCCH candidates across linked SS sets. Some aspects described herein provide for configuration of an SS set associated with beam failure recovery (e.g., the recoverySearchSpacefD SS set) when linked SS sets are enabled for a UE. For example, in a first case, the beam failure recovery SS set may not be permitted to be linked with any other search space set, and PDCCH repetition may be disabled for a beam failure recovery response PDCCH. The first case reduces a processing, monitoring, and/or decoding complexity for the UE relative to allowing PDCCH repetition and SS set linking, thereby reducing a utilization of UE resources, such as processing resources or energy resources. In a second case, a first SS set (e.g., the beam failure recovery SS set) may be linked with a second SS set when the first SS set and the second SS set share a common configuration, such as sharing the same CORESET. The second case allows PDCCH repetition and SS set linking under a constraint (e.g., having the same configuration), which enables greater flexibility than the first case (e.g., in which PDCCH repetition and SS set liking is not permitted) with reduced processing, monitoring, and/or decoding complexity relative to allowing PDCCH repetition and SS set linking without the constraint. In a third case, a first SS set (e.g., the beam failure recovery SS set) may be linked with a second SS set even when the first SS set and the second SS set do not share a common configuration, such as a common CORESET. The third case enables PDCCH repetition and SS set linking without the constraint of sharing a common configuration, thereby providing greater flexibility than the first case and the second case. In each case, behavior of a UE is defined, thereby enabling the UE to operate with linked PDCCH candidates enabled without ambiguity in the UE's behavior resulting in dropped communications or failure to complete a beam failure recovery procedure.

FIG.8is a diagram illustrating an example800associated with configuration of a beam failure recovery SS set for PDCCH repetition, in accordance with the present disclosure. As shown inFIG.8, example800includes communication between a network node802and a UE120. In some aspects, network node802and UE120may be included in a wireless network, such as wireless network100. Network node802and UE120may communicate via a wireless access link, which may include an uplink and a downlink.

As further shown inFIG.8, and by reference number810, UE120may receive configuration information (e.g., information associated with configuring a first SS set and/or a second SS set). For example, UE120may receive configuration information associated with configuring a beam failure recovery SS set. In this case, as described above, UE120may receive configuration information including a recoverSearchSpaceID parameter that identifies parameters of a beam failure recovery SS set for monitoring for PDCCH candidates (e.g., for detection of DCI with a CRC scrambled with a C-RNTI or MCS-C-RNTI as a beam failure recovery response). In some aspects, UE120may be configured for PDCCH repetition with linked PDCCH candidates across a plurality of linked SS sets.

In some aspects, UE120may receive configuration information that does not link the beam failure recovery SS set with another SS set. For example, network node802may enforce a rule that the beam failure recovery SS set is not to be linked with other SS sets (even when linked SS sets is enabled). For example, when the UE120receives the configuration information, the UE120may be configured with a recovery search space identifier (recoverySearchSpaceId) parameter. In this case, a second SS (e.g., the other SS sets) set may not be linked with a first SS (e.g., the beam failure recovery SS set) based at least in part on a recovery search space identifier message conveying a configuration of the first SS set. Alternatively, the other SS sets may not be linked with the beam failure recovery SS set based at least in part on a static rule (e.g., without configuration information indicating away from a linkage). Although the other SS sets may not be linked with the beam failure recovery SS set, the other SS sets may be linked with each other in some aspects. In another words, one of the other SS sets may be linked with another of the SS sets. The beam failure recovery set not being linked with another SS set may include the UE120, when configured with the recovery search space identifier, not expecting the beam failure recovery SS space (configured with the recovery search space identifier) to be linked with any other SS set. In this case, if the UE120is configured with a first SS set for beam failure recovery, the first SS set is not linked with a second SS set (e.g., PDCCH repetition is configured for the first SS set, but the first SS set is not linked with the second SS set). In other words, when the UE120receives configuration information, the UE120may be configured with different DCIs. For example, when the UE120receives configuration information that does not link the beam failure recovery SS set with another SS set, the UE120may be receiving first DCI for the beam failure recovery SS set and second DCI (that is different from the first DCI) for the other SS set. In this case, based at least in part on the first DCI being different from the second DCI, the first SS set is not linked with the second SS set (for PDCCH repetition). By avoiding linking the SS sets, decoding, monitoring, and/or processing complexity is reduced, and the network node110may have greater flexibility in configuring the first SS set differently from the second SS set. In this case, the UE120may receive configuration information linking other SS sets (e.g., the aforementioned second SS set to a third SS set), but not the SS set for beam failure recovery. As a result, network node802may not use, and UE120may not monitor for, PDCCH repetition when monitoring for PDCCH candidates associated with the beam failure recovery SS set. In other words, the UE120may monitor for a first SS set and may separately monitor for a second SS set. In this way, the UE120can use different monitoring configurations for the first SS set and the second SS set, which may increase a flexibility in UE operation, thereby enabling reduced power consumption or processing power.

In some aspects, UE120may receive configuration information that links the beam failure recovery SS set with another SS set with a commonality condition satisfied. For example, network node802may link a first SS set for beam failure recovery with a second SS set (not explicitly configured for beam failure recovery) when the first SS set and the second SS set are associated with the same CORESET. In some aspects, the configuration information that links the beam failure recovery SS set with another SS set may include QCL information or a CORESET parameter. For example, the UE120may receive information identifying a QCL parameter for the beam failure recovery SS set and another SS set or information identifying a QCL relationship between the beam failure recovery SS set and another SS set. By linking SS sets, an effective aggregation level (AL) for the SS sets is increased. In other words, two linked aggregation level 16 (AL16) PDCCH candidates results in an effective AL of aggregation level 32 (AL32), which increases communication performance and/or a likelihood of successful reception. As another example, network node802may link a first SS set with a second SS set, and configure both the first SS set and the second SS set for beam failure recovery, when the first SS set and the second SS set are associated with the same CORESET. Network node802may use PDCCH repetition to transmit and UE120may monitor for PDCCH repetition when monitoring PDCCH candidates associated with the first SS set and the second SS set. In some aspects, UE120may use a common QCL parameter for monitoring for PDCCH candidates in the first SS set and the second SS set. For example, network node802may configure the first SS set and the second SS set with a common QCL assumption. In this case, the common QCL assumption may have the same QCL parameters as the q_new RS identified in connection with the beam failure recovery procedure, as described above. Further, in this case, a CORESET associated with the beam failure recovery SS set (e.g., the first SS set) may be used for another SS set (e.g., the second SS set) provided that the other SS set is linked with the beam failure recovery SS set for PDCCH repetition.

In some aspects, UE120may receive configuration information (e.g., a CORESET parameter, a QCL parameter, or a QCL relationship, among other examples) that links the beam failure recovery SS set with another SS set without the commonality condition satisfied. For example, network node802may link a first SS set for beam failure recovery, which associated with a first CORESET, with a second SS set (not for beam failure recovery), which is associated with a second CORESET that is different from the first CORESET. As another example, network node802may link a first SS set with a second SS set, and configure both the first SS set and the second SS set for beam failure recovery, where the first SS set and the second SS set are associated with different CORESETs. PDCCH candidates of the first SS set may have a first QCL parameter (e.g., a first QCL assumption and associated beam) and PDCCH candidates of the second SS set may have a second QCL parameter (e.g., a second QCL assumption and associated beam). In some aspects, when linked SS sets have different CORESETs, network node802and UE120may apply a newly identified beam of the beam recovery procedure, q_new, only to PDCCH candidates in the beam failure recovery SS set (e.g., the first SS set). In other words, UE120may apply q_new to the first SS set, and the UE120may continue using the second QCL assumption and associated beam for the second SS set (e.g., which may not be reset to q_new after PRACH transmission).

Alternatively, when linked SS sets have different CORESETs, UE120may identify a pair of beams in the beam recovery procedure, q_new_1 and q_new_2, and US 120 may apply the pair of beams to the respective SS sets's PDCCH candidates. In other words, network node802and UE120may apply q_new_1 to PDCCH candidates of the first SS set and q_new_2 to PDCCH candidates of the second SS set. In some aspects, UE120may indicate the pair of beams to network node802during PRACH transmission of the beam failure recovery procedure (e.g., rather than indicating a single beam, q_new, as described with regard to reference number760inFIG.7). In some aspects, UE120may determine whether to apply a single beam q_new or a pair of beams q_new_1 and q_new_2 based at least in part on a PRACH occasion configuration. For example, when UE120is configured with a PRACH occasion or preamble associated with one candidate beam, UE120may report q_new and may apply q_new to the first SS set (and leave the second SS set unchanged). In contrast, when UE120is configured with a PRACH occasion or preamble associated with two candidate beams, UE120may report q_new_1 and q_new_2 and may apply q_new_1 to the first SS set and q_new_2 to the second SS set. Additionally, or alternatively, UE120may be configured with two PRACH occasions or preambles, each configured for a single candidate beam, and may report q_new_1 via a first PRACH occasion (and apply q_new_1 to the first SS set) and q_new_2 via a second PRACH occasion (and apply q_new_2 to the second SS set).

As further shown inFIG.8, and by reference number820, UE120may monitor for PDCCH candidates. For example, UE120may monitor for PDCCH candidates in accordance with a configuration for linking PDCCH candidates across SS sets. For example, when the beam failure recovery SS set may not be linked with another SS set (based at least in part on the UE120having the beam failure recovery SS set configured based at least in part on receiving a recoverySearchSpaceId parameter), UE120may monitor for PDCCH candidates associated with the beam failure recovery SS set and may not monitor for any other PDCCH candidates, in another SS set, that are linked to the PDCCH candidates associated with the beam failure recovery SS set. In this way, the UE120may reduce a monitoring, decoding, and/or processing complexity, which reduces processing utilization or energy resource utilization. Moreover, PDCCH repetition may not be used for a beam failure recovery response PDCCH.

Additionally, or alternatively, when the beam failure recovery SS set is linked with another SS set with the same CORESET, the UE120may monitor for PDCCH candidates of a first SS set (e.g., the beam failure recovery SS set) and PDCCH candidates of a second SS set (e.g., another SS set that is linked to the beam failure recovery SS set). Similarly, when the beam failure recovery SS set is linked with another SS set with a different CORESET UE120may monitor a first CORESET for PDCCH candidates of a first SS set and a second CORESET for PDCCH candidates of a second SS set. In these cases, by linking SS sets, an effective AL is increased by combining PDCCH candidates of the linked SS sets, thereby improving communication performance and/or a likelihood of successful reception.

In some aspects, UE120may monitor for a scheduled PDSCH associated with linked PDCCH candidates in two linked SS sets (e.g., the beam failure recovery SS set and another SS set). For example, UE120may monitor for the scheduled PDSCH using the same QCL assumption (beam) as is identified for the beam failure recovery SS set (the first SS set) (e.g., q_new or q_new_1). Additionally, or alternatively, UE120may monitor for the scheduled PDSCH using QCL assumptions (beams) identified for the first SS set and the second SS set (e.g., q_new or both q_new_1 and q_new_2). In some aspects, the PDSCH may be associated with two beams applied to different sets of symbols (e.g., in time division multiplexing), different sets of resource blocks (e.g., in frequency division multiplexing), different sets of layers (e.g., in spatial division multiplexing) with respect to each DMRS port and data layer (e.g., system frame number (SFN)) of the PDSCH.

FIG.9is a diagram illustrating an example process900performed, for example, by a UE, in accordance with the present disclosure. Example process900is an example where the UE (e.g., UE120) performs operations associated with configuration of a beam failure recovery SS set for PDCCH repetition.

As shown inFIG.9, in some aspects, process900may include monitoring, in a first monitoring occasion, a first SS set (block910). For example, the UE (e.g., using communication manager140and/or monitoring component1208, depicted inFIG.12) may monitor, in a first monitoring occasion, a first SS set, as described above.

As further shown inFIG.9, in some aspects, process900may include monitoring, in a second monitoring occasion, a second SS set (block920). For example, the UE (e.g., using communication manager140and/or monitoring component1208, depicted inFIG.12) may monitor, in a second monitoring occasion, a second SS set, as described above. In some aspects, the first SS set is independent of the second SS set. In some aspects, PDCCH repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set, as described above.

In an aspect, the first SS set is a recovery search space identifier configured SS set.

FIG.10is a diagram illustrating an example process1000performed, for example, by a UE, in accordance with the present disclosure. Example process1000is an example where the UE (e.g., UE120) performs operations associated with configuration of a beam failure recovery SS set for PDCCH repetition.

As shown inFIG.10, in some aspects, process1000may include receiving information configuring a first SS set and a second SS set (block1010). For example, the UE (e.g., using communication manager140and/or reception component1202, depicted inFIG.12) may receive information configuring a first SS set and a second SS set, as described above. In some aspects, the first SS set is linked with the second SS set for PDCCH repetition. In some aspects, the first SS set is a recovery search space identifier configured SS set.

As further shown inFIG.10, in some aspects, process1000may include monitoring for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set (block1020). For example, the UE (e.g., using communication manager140and/or monitoring component1208, depicted inFIG.12) may monitor for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, as described above. In some aspects, the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI.

In a first aspect, the first SS set and the second SS set are associated with a common CORESET.

In a second aspect, alone or in combination with the first aspect, the first one or more PDCCH candidates and the second one or more PDCCH candidates are associated with a common QCL parameter.

In a third aspect, alone or in combination with one or more of the first and second aspects, a QCL parameter of the common CORESET is based at least in part on a corresponding QCL parameter of a reference signal associated with a new identified beam after beam failure recovery detection.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the common CORESET is not associated with a third SS set that is different from the first SS set and the second SS set.

In a fifth aspect, the first SS set is associated with a first CORESET and the second SS set is associated with a second CORESET that is different from the first CORESET.

In a sixth aspect, alone or in combination with the fifth aspect, the first one or more PDCCH candidates are associated with a first QCL parameter and the second one or more PDCCH candidates are associated with a second QCL parameter that is different from the first QCL parameter.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a beam failure recovery identified beam is applied to the first one or more PDCCH candidates in the first SS set and not the second one or more PDCCH candidates in the second SS set.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a first beam failure recovery identified beam is applied to the first one or more PDCCH candidates in the first SS set and a second beam failure recovery identified beam is applied to the second one or more PDCCH candidates in the second SS set, and wherein the first beam failure recovery identified beam is different from the second beam failure recovery identified beam.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, a quantity of indicated beam failure recovery identified beams is based at least in part on a quantity of beams associated with a physical random access channel communication. For example, the quantity of beam failure recovery identified beams, which are indicated to the network node, is based at least in part on the quantity of beams associated with the physical random access channel communication.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a quantity of indicated beam failure recovery identified beams is based at least in part on a quantity of physical random access channel communications that are configured. For example, the quantity of beam failure recovery identified beams, which are indicated to the network node, is based at least in part on the quantity of physical random access channel communications that are configured.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process1000includes receiving a physical downlink shared channel using a quasi-co-location parameter associated with the first one or more PDCCH candidates in the first SS set.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process1000includes receiving a physical downlink shared channel using quasi-co-location parameters associated with the first one or more PDCCH candidates in the first SS set and the second one or more PDCCH candidates in the second SS set.

FIG.11is a diagram illustrating an example process1100performed, for example, by a UE, in accordance with the present disclosure. Example process1100is an example where the UE (e.g., the UE120) performs operations associated with configuration of a beam failure recovery SS set for PDCCH repetition.

As shown inFIG.11, in some aspects, process1100may include receiving, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring (block1110). For example, the UE (e.g., using communication manager140and/or reception component1202, depicted inFIG.12) may receive, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring, as described above.

As further shown inFIG.11, in some aspects, process1100may include monitoring, in a first monitoring occasion, the first SS set (block1120). For example, the UE (e.g., using communication manager140and/or monitoring component1208, depicted inFIG.12) may monitor, in a first monitoring occasion, the first SS set, as described above.

As further shown inFIG.11, in some aspects, process1100may include monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set (block1130). For example, the UE (e.g., using communication manager140and/or monitoring component1208, depicted inFIG.12) may monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set, as described above.

In a first aspect, process1100includes receiving first DCI associated with the first SS set, and receiving second DCI associated with the second SS set, wherein the second DCI is different from the first DCI.

In a second aspect, alone or in combination with the first aspect, the first SS set is disabled for physical downlink control channel repetition.

In a third aspect, alone or in combination with one or more of the first and second aspects, the second SS set is not linked with the first SS set based at least in part on the recovery search space identifier message conveying the configuration of the first SS set.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the second SS set is not linked to the first SS set for physical downlink control channel repetition.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the second SS set is linked to a third SS set for physical downlink control channel repetition.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the first SS set is a recovery search space identifier configured SS set.

FIG.12is a diagram of an example apparatus1200for wireless communication. The apparatus1200may be a UE, or a UE may include the apparatus1200. In some aspects, the apparatus1200includes a reception component1202and a transmission component1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1200may communicate with another apparatus1206(such as a UE, a base station, or another wireless communication device) using the reception component1202and the transmission component1204. As further shown, the apparatus1200may include the communication manager140. The communication manager140may include a monitoring component1208, among other examples.

The monitoring component1208may monitor, in a first monitoring occasion, a first SS set. The monitoring component1208may monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set.

The reception component1202may receive information configuring a first SS set and a second SS set, wherein the first SS set is linked with the second SS set for PDCCH repetition, and wherein the first SS set is a recovery search space identifier configured SS set. The monitoring component1208may monitor for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response DCI.

The reception component1202may receive a physical downlink shared channel using a quasi-co-location parameter associated with the first one or more PDCCH candidates in the first SS set. The reception component1202may receive a physical downlink shared channel using quasi-co-location parameters associated with the first one or more PDCCH candidates in the first SS set and the second one or more PDCCH candidates in the second SS set.

The reception component1202may receive, in a recovery search space identifier message, configuration information identifying a configuration of a first SS set, wherein the first SS set is configured for beam failure recovery monitoring. The monitoring component1208may monitor, in a first monitoring occasion, the first SS set. The monitoring component1208may monitor, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set. The reception component1202may receive first DCI associated with the first SS set. The reception component1202may receive second DCI associated with the second SS set, wherein the second DCI is different from the first DCI.

FIG.13is a diagram illustrating an example1300of an open radio access network (O-RAN) architecture, in accordance with the present disclosure. As shown inFIG.13, the O-RAN architecture may include a control unit (CU)1310that communicates with a core network1320via a backhaul link. Furthermore, the CU1310may communicate with one or more distributed units (DUs)1330via respective midhaul links. The DUs1330may each communicate with one or more radio units (RUs)1340via respective fronthaul links, and the RUs1340may each communicate with respective UEs120via radio frequency (RF) access links. The DUs1330and the RUs1340may also be referred to as O-RAN DUs (O-DUs)1330and O-RAN RUs (O-RUs)1340, respectively.

In some aspects, the DUs1330and the RUs1340may be implemented according to a functional split architecture in which functionality of a network entity110(e.g., an eNB or a gNB) is provided by a DU1330and one or more RUs1340that communicate over a fronthaul link. Accordingly, as described herein, a network entity110may include a DU1330and one or more RUs1340that may be co-located or geographically distributed. In some aspects, the DU1330and the associated RU(s)1340may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, to exchange non-real-time management information via an LLS management plane (LLS-M) interface, and/or to exchange user plane information via an LLS user plane (LLS-U) interface.

Accordingly, the DU1330may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs1340. For example, in some aspects, the DU1330may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and/or modulation and demodulation) based at least in part on a lower layer functional split. Higher layer control functions, such as a packet data convergence protocol (PDCP), radio resource control (RRC), and/or service data adaptation protocol (SDAP), may be hosted by the CU1310. The RU(s)1340controlled by a DU1330may correspond to logical nodes that host RF processing functions and low-PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and/or physical random access channel (PRACH) extraction and filtering) based at least in part on the lower layer functional split. Accordingly, in an O-RAN architecture, the RU(s)1340handle all over the air (OTA) communication with a UE120, and real-time and non-real-time aspects of control and user plane communication with the RU(s)1340are controlled by the corresponding DU1330, which enables the DU(s)1330and the CU1310to be implemented in a cloud-based RAN architecture.

As indicated above,FIG.13is provided as an example. Other examples may differ from what is described with regard toFIG.13.

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: monitoring, in a first monitoring occasion, a first search space (SS) set; and monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is independent of the second SS set, and wherein physical downlink control channel repetition is disabled for beam failure recover response messaging in connection with the first SS set being independent of the second SS set. For example, the first SS set is not linked with the second SS set, thereby making the first SS set independent of the second SS set.

Aspect 2: The method of Aspect 1, wherein the first SS set is a recovery search space identifier configured SS set.

Aspect 3: A method of wireless communication performed by a user equipment (UE), comprising: receiving information configuring a first search space (SS) set and a second SS set, wherein the first SS set is linked with the second SS set for physical downlink control channel (PDCCH) repetition, and wherein the first SS set is a recovery search space identifier configured SS set; and monitoring for a first one or more PDCCH candidates in the first SS set and a second one or more PDCCH candidates in the second SS set, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are occurrences of a beam failure recovery response downlink control information (DCI).

Aspect 4: The method of Aspect 3, wherein the first SS set and the second SS set are associated with a common control resource set (CORESET).

Aspect 5: The method of Aspect 4, wherein the first one or more PDCCH candidates and the second one or more PDCCH candidates are associated with a common quasi-co-location (QCL) parameter.

Aspect 6: The method of any of Aspect 4, wherein a quasi-co-location (QCL) parameter of the common CORESET is based at least in part on a corresponding QCL parameter of a reference signal associated with a new identified beam after beam failure recovery detection.

Aspect 7: The method of Aspect 4, wherein the common CORESET is not associated with a third SS set that is different from the first SS set and the second SS set.

Aspect 8: The method of any of Aspects 3 to 7, wherein the first SS set is associated with a first control resource set (CORESET) and the second SS set is associated with a second CORESET that is different from the first CORESET.

Aspect 9: The method of Aspect 8, wherein the first one or more PDCCH candidates are associated with a first quasi-co-location (QCL) parameter and the second one or more PDCCH candidates are associated with a second QCL parameter that is different from the first QCL parameter.

Aspect 10: The method of Aspect 8, wherein a beam failure recovery identified beam is applied to the first one or more PDCCH candidates in the first SS set and not the second one or more PDCCH candidates in the second SS set.

Aspect 11: The method of Aspect 8, wherein a first beam failure recovery identified beam is applied to the first one or more PDCCH candidates in the first SS set and a second beam failure recovery identified beam is applied to the second one or more PDCCH candidates in the second SS set, and wherein the first beam failure recovery identified beam is different from the second beam failure recovery identified beam.

Aspect 12: The method of any of Aspects 3 to 11, wherein a quantity of indicated beam failure recovery identified beams is based at least in part on a quantity of beams associated with a physical random access channel communication.

Aspect 13: The method of any of Aspects 3 to 12, wherein a quantity of indicated beam failure recovery identified beams is based at least in part on a quantity of physical random access channel communications that are configured.

Aspect 14: The method of any of Aspects 3 to 13, further comprising: receiving a physical downlink shared channel using a quasi-co-location parameter associated with the first one or more PDCCH candidates in the first SS set.

Aspect 15: The method of any of Aspects 3 to 13, further comprising: receiving a physical downlink shared channel using quasi-co-location parameters associated with the first one or more PDCCH candidates in the first SS set and the second one or more PDCCH candidates in the second SS set.

Aspect 16: A method of wireless communication, comprising: receiving, in a recovery search space identifier message, configuration information identifying a configuration of a first search space (SS) set, wherein the first SS set is configured for beam failure recovery monitoring; monitoring, in a first monitoring occasion, the first SS set; and monitoring, in a second monitoring occasion, a second SS set, wherein the first SS set is not linked to the second SS set.

Aspect 17: The method of Aspect 16, further comprising: receiving first downlink control information (DCI) associated with the first SS set; and receiving second DCI associated with the second SS set, wherein the second DCI is different from the first DCI.

Aspect 18: The method of any of Aspects 16 to 17, wherein the first SS set is disabled for physical downlink control channel repetition.

Aspect 19: The method of any of Aspects 16 to 18, wherein the second SS set is not linked with the first SS set based at least in part on the recovery search space identifier message conveying the configuration of the first SS set.

Aspect 20: The method of any of Aspects 16 to 19, wherein the second SS set is not linked to the first SS set for physical downlink control channel repetition.

Aspect 21: The method of any of Aspects 16 to 20, wherein the second SS set is linked to a third SS set for physical downlink control channel repetition.

Aspect 22: The method of any of Aspects 16 to 21, wherein the first SS set is a recovery search space identifier configured SS set.

Aspect 24: A device for wireless communication, comprising memory, and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the device to perform the method of one or more of Aspects 1-2.

Aspect 30: A device for wireless communication, comprising memory, and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the device to perform the method of one or more of Aspects 3-15.

Aspect 36: A device for wireless communication, comprising memory, and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the device to perform the method of one or more of Aspects 16-22.