Patent Description:
<NPL>, discusses issues on multi-beam operation for <NPL>, further builds on the TCI framework. <NPL>, discusses the PDCCH blind decoding dropping candidates dropping rule in USS if number of blind decodes is met. <NPL>, provides further considerations on rate matching.

In some aspects, a method of wireless communication, performed by a user equipment (UE), may include receiving an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and selectively performing, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate.

In some aspects, a UE for wireless communication may include memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and selectively perform, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to receive an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and selectively perform, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate.

In some aspects, an apparatus for wireless communication may include means for receiving an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and means for selectively performing, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate.

In some aspects, a method of wireless communication, performed by a base station, may include transmitting an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and selectively transmitting, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate.

In some aspects, a base station for wireless communication may include memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to transmit an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and selectively transmit, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a base station, may cause the one or more processors to transmit an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and selectively transmit, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate.

In some aspects, an apparatus for wireless communication may include means for transmitting an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; and means for selectively transmitting, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, transmit receive point (TRP), wireless communication device, and processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with downlink control for multiple transmit receive point (TRP) configurations, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively.

In some aspects, UE <NUM> may include means for receiving an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; means for selectively performing, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate; and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>.

In some aspects, base station <NUM> may include means for transmitting an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states; means for selectively transmitting, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate; and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>.

<FIG> illustrates an example logical architecture of a distributed RAN <NUM>, according to various aspects of the present disclosure.

The ANC <NUM> may be a central unit (CU) of the distributed RAN <NUM>. The backhaul interface to the next generation core network (NG-CN) <NUM> may terminate at the ANC <NUM>. The backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC <NUM>. The ANC <NUM> may include one or more TRPs <NUM> (which may also be referred to as BSs, NR BSs, Node Bs, <NUM> NBs, APs, gNB, or some other term). As described above, a TRP <NUM> may be used interchangeably with "cell. " In some aspects, multiple TRPs <NUM> may be included in a single base station <NUM>. Additionally, or alternatively, different TRPs <NUM> may be included in different base stations <NUM>.

A TRP <NUM> may be a distributed unit (DU). A TRP <NUM> may be connected to a single ANC <NUM> or multiple ANCs <NUM>. For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, a TRP <NUM> may be connected to more than one ANC <NUM>. A TRP <NUM> may include one or more antenna ports. The TRPs <NUM> may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE <NUM>.

The architecture may be defined that supports fronthauling solutions across different deployment types. The architecture may enable coordination between and among TRPs <NUM>. For example, coordination may be preset within a TRP <NUM> and/or across TRPs <NUM> via the ANC <NUM>.

The packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC) protocol may be adaptably placed at the ANC <NUM> or TRP <NUM>. According to various aspects, a base station <NUM> may include a central unit (CU) (e.g., ANC <NUM>) and/or one or more distributed units (e.g., one or more TRPs <NUM>).

The C-CU <NUM> may be centrally deployed. Functionality of the C-CU may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. The C-RU 404may have distributed deployment. The C-RU <NUM> may be closer to the network edge. A distributed unit (DU) <NUM> may host one or more TRPs <NUM>. The DU <NUM> may be located at edges of the network with radio frequency (RF) functionality.

<FIG> illustrates an example resource structure <NUM> for wireless communication, in accordance with various aspects of the present disclosure. Resource structure <NUM> shows an example of various groups of resources described herein. As shown, resource structure <NUM> may include a subframe <NUM>. Subframe <NUM> may include multiple slots <NUM>. While resource structure <NUM> is shown as including <NUM> slots per subframe, a different number of slots may be included in a subframe (e.g., <NUM> slots, <NUM> slots, <NUM> slots, <NUM> slots, and/or the like). In some aspects, different types of transmission time intervals (TTIs) may be used, other than subframes and/or slots. A slot <NUM> may include multiple symbols <NUM>, such as <NUM> symbols or <NUM> symbols per slot.

The potential control region of a slot <NUM> may be referred to as a control resource set (CORESET) <NUM>, and may be structured to support an efficient use of resources, such as by flexible configuration or reconfiguration of resources of the CORESET <NUM> for one or more physical downlink control channels (PDCCHs), one or more physical downlink shared channels (PDSCHs), and/or the like. In some aspects, the CORESET <NUM> may occupy the first symbol <NUM> of a slot <NUM>, the first two symbols <NUM> of a slot <NUM>, or the first three symbols <NUM> of a slot <NUM>. Thus, a CORESET <NUM> may include multiple resource blocks in the frequency domain, and either one, two, or three symbols <NUM> in the time domain. In <NUM>, a number of resources included in the CORESET <NUM> may be flexibly configured, such as by using radio resource control (RRC) signaling to indicate a frequency domain region (e.g., a number of resource blocks) and/or a time domain region (e.g., a number of symbols) for the CORESET <NUM>.

As illustrated, a symbol <NUM> that includes CORESET <NUM> may include one or more control channel elements (CCEs) <NUM>, shown as two CCEs <NUM> as an example, that span a portion of the system bandwidth. A CCE <NUM> may include downlink control information (DCI) that is used to provide control information for wireless communication. A base station may transmit DCI during multiple CCEs <NUM> (as shown), where the number of CCEs <NUM> used for transmission of DCI represents the aggregation level used by the base station for the transmission of DCI. In <FIG>, an aggregation level of two is shown as an example, corresponding to two CCEs <NUM> in a slot <NUM>. In some aspects, different aggregation levels may be used, such as <NUM>, <NUM>, <NUM>, <NUM>, and/or the like.

Each CCE <NUM> may include a fixed number of resource element groups (REGs) <NUM>, shown as four REGs <NUM>, or may include a variable number of REGs <NUM>. In some aspects, the number of REGs <NUM> included in a CCE <NUM> may be specified by a REG bundle size. A REG <NUM> may include one resource block, which may include <NUM> resource elements (REs) <NUM> within a symbol <NUM>. A resource element <NUM> may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

A CORESET <NUM> may include one or more search spaces, such as a UE-specific search space, a group-common search space, and/or a common search space. A search space may indicate a set of CCE locations where a UE may find PDCCHs that can potentially be used to transmit control information to the UE. The possible locations for a PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group-common PDCCH (e.g., for multiple UEs), an aggregation level being used, and/or the like. A possible location (e.g., in time and/or frequency) for a PDCCH may be referred to as a PDCCH candidate, and the set of all possible PDCCH locations may be referred to as a search space. For example, the set of all possible PDCCH locations for a particular UE may be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH locations across all UEs may be referred to as a common search space. Similarly, the set of all possible PDCCH locations for a particular group of UEs may be referred to as a group-common search space.

As shown by reference number <NUM>, multiple TRPs (shown as TRP A and TRP B) may communicate with the same UE in a coordinated manner (e.g., using coordinated multipoint transmissions and/or the like) to improve reliability, increase throughput, and/or the like. The TRPs may coordinate such communications via a backhaul, which may have a smaller delay when the TRPs are co-located at the same base station (e.g., different antenna arrays of the same base station), or may have a larger delay when the TRPs are located at different base stations. As shown, different TRPs may communicate control information to the UE using different CORESETs <NUM>. Some techniques and apparatuses described herein provide diversity gain using non-coherent joint transmissions from multiple TRPs, and permit a UE to selectively combine joint transmission from multiple TRPs with relatively low complexity.

<FIG> is a diagram illustrating an example <NUM> relating to downlink control for multiple TRP configurations, in accordance with various aspects of the present disclosure.

As shown in <FIG>, a UE <NUM> may communicate with a first TRP <NUM> (shown as TRP A) and a second TRP <NUM> (shown as TRP B), such as in a coordinated multipoint communication scheme. As described elsewhere herein, a TRP <NUM>, <NUM> may correspond to a base station <NUM>, an antenna array of a base station <NUM>, and/or the like. In some aspects, the first TRP <NUM> and the second TRP <NUM> may be part of the same base station <NUM> and/or cell (e.g., different antenna arrays of the same base station <NUM>). In some aspects, the first TRP <NUM> and the second TRP <NUM> may be separate base stations <NUM> and/or cells.

As shown by reference number <NUM>, a TRP (e.g., shown as the first TRP <NUM>, but which could be the second TRP <NUM>) may transmit, and the UE <NUM> may receive, an indication of multiple pairs of corresponding PDCCH candidates. In some aspects, the indication is included in an RRC message. A pair of PDCCH candidates may include a first PDCCH candidate included in a first CORESET (shown as CORESET A) and a corresponding second PDCCH candidate included in a second CORESET (shown as CORESET B). In some aspects, the first CORESET may be associated with the first TRP <NUM> (e.g., may be used by the first TRP <NUM> to transmit DCI), and the second CORESET may be associated with the second TRP <NUM> (e.g., may be used by the second TRP <NUM> to transmit DCI). Additionally, or alternatively, the first CORESET and the second CORESET may have different transmission configuration indication (TCI) states that indicate different quasi-colocation assumptions, different beamforming states, and/or different beamforming parameters between the first CORESET and the second CORESET.

For example, as shown by reference number <NUM>, the indication may indicate that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another, that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another, that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another, and that that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another. In this example, the PDCCH candidates in CORESET A and CORESET B are associated with the same aggregation level (e.g., four), and CORESET A and CORESET B include the same number of PDCCH candidates (e.g., four). In this case, each PDCCH candidate from CORESET A maps to one respective PDCCH candidate from CORESET B, and each PDCCH candidate from CORESET B maps to one respective PDCCH candidate from CORESET A. In other words, there is a one-to-one mapping of PDCCH candidates between CORESET A and CORESET B. In some aspects, and as shown, PDCCH candidates with matching indices from both CORESETs may be included in the same PDCCH candidate pair.

As another example, as shown by reference number <NUM>, the indication may indicate that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another, that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another, that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another, and that that PDCCH candidate <NUM> from CORESET A and PDCCH candidate <NUM> from CORESET B correspond to one another. In this example, the PDCCH candidates in CORESET A and CORESET B are associated with different aggregation levels (e.g., four and two, respectively), and CORESET A and CORESET B include a different number of PDCCH candidates (e.g., four and two, respectively). In this case, one or more PDCCH candidates from CORESET A map to multiple PDCCH candidates from CORESET B. In other words, there is a one-to-many mapping of PDCCH candidates between CORESET A and CORESET B. In some aspects, and as shown, after all of the PDCCH candidates from the CORESET with the smaller aggregation level have been paired with a PDCCH candidate from the CORESET with the larger aggregation level, the pairing of PDCCH candidates may wrap around to a first PDCCH candidate of the CORESET with the smaller aggregation level.

In some aspects, the same aggregation level may be used for PDCCHs in both CORESETs because some aggregation levels and DCI size candidates are not combinable. For example, if a first aggregation level is used for a first PDCCH, and a second aggregation level is used for a second PDCCH, a particular DCI size and/or format may not be compatible with both aggregation levels. In some aspects, the TRP(s) may configure the PDCCHs across CORESETs to use the same aggregation level, thereby eliminating such incompatibility. Additionally, or alternatively, the TRP(s) may select a DCI size and/or format that is compatible with both aggregation levels.

By indicating corresponding PDCCH candidates for joint transmissions on different CORESETs, as described above, decoding complexity may be reduced as compared to permitting any combination of PDCCH candidates for joint transmissions on the different CORESETs. For example, if CORESET A includes M PDCCH candidates and CORESET B includes N PDCCH candidates (e.g., where M > N), then M × N pairs of PDCCH candidates may exist, as compared to M pairs of PDCCH candidates when the techniques described herein are used.

As shown by reference number <NUM>, the first TRP <NUM> may communicate with the UE <NUM> using CORESET A. For example, the first TRP <NUM> may identify a PDCCH candidate, on CORESET A, to be used for a PDCCH, and for transmission of DCI on the PDCCH. The four PDCCH candidates of example <NUM> are shown in CORESET A as 1A, 2A, 3A, and 4A. Similarly, as shown by reference number <NUM>, the second TRP <NUM> may communicate with the UE <NUM> using CORESET B. For example, the second TRP <NUM> may identify a PDCCH candidate, on CORESET B, to be used for a PDCCH, and for transmission of DCI on the PDCCH. The four PDCCH candidates of example <NUM> are shown in CORESET B as 1B, 2B, 3B, and 4B.

The PDCCH candidates on CORESET A and CORESET B may be selected such that DCI for a joint transmission is transmitted on a pair of corresponding PDCCH candidates, indicated to the UE <NUM> as described above in connection with reference numbers <NUM>-<NUM>. In this way, complexity for the UE <NUM> may be reduced by reducing a number of pairs of PDCCH candidates to be blindly decoded by the UE <NUM>. In some aspects, the DCI transmitted on the pair of corresponding PDCCH candidates may be the same. For example, the same information bits of DCI (but possibly different parity bits for different redundancy versions) may be transmitted on the pair of corresponding PDCCH candidates. By using joint transmission of DCI on different CORESETs with different TCI states (e.g., for non-coherent joint transmission), spatial diversity may be increased, thereby increasing a likelihood of successful reception of the DCI by the UE <NUM>, which may improve reliability, reduce latency, increase throughput, and/or the like.

In some aspects, the first TRP <NUM> and/or the second TRP <NUM> may coordinate whether to transmit only on a PDCCH candidate on CORESET A, only on a corresponding PDCCH candidate on CORESET B, on both the first PDCCH candidate and the second PDCCH candidate, or on neither of the first PDCCH candidate or the second PDCCH candidate (e.g., when there is no DCI and/or data to transmit for the UE <NUM>, when a different PDCCH candidate pair is selected, and/or the like). For example, the determination of which PDCCH candidates to be used to transmit DCI on a PDCCH may be based at least in part on radio conditions (e.g., determined by performing radio link monitoring of a radio link between the UE <NUM> and the first TRP <NUM>, a radio link between the UE <NUM> and the second TRP <NUM>, and/or the like). For example, if radio conditions are good on the link between the UE <NUM> and the first TRP <NUM> and are also good on the link between the UE <NUM> and the second TRP <NUM>, then the TRPs may jointly transmit DCI. However, if radio conditions are good on only one of the links, then the TRP associated with that link may transmit DCI, and the other TRP may not transmit DCI.

One or both TRPs transmit a decoding configuration that indicates whether the UE <NUM> is to independently decode the first PDCCH candidate, independently decode the second PDCCH candidate, jointly decode the first PDCCH candidate and the second PDCCH candidate, or some combination thereof. In some aspects, the decoding configuration may be semi-statically configured (e.g., via RRC). Additional details are described below in connection with <FIG>.

As shown by reference number <NUM>, the UE <NUM> selectively performs at least one of independent decoding of a first PDCCH candidate of a PDCCH candidate pair, independent decoding of a second PDCCH candidate of a PDCCH candidate pair, or joint decoding of both the first PDCCH candidate and the second PDCCH candidate. The UE <NUM> determines which of these decoding options to perform based at least in part on the decoding configuration, as described in more detail below in connection with <FIG>.

In some aspects, resources of a physical uplink control channel (PUCCH) may be implicitly indicated and/or determined based at least in part on one of the PDCCHs corresponding to one of the PDCCH candidates in a pair of PDCCH candidates. For example, a timing of a PUCCH may depend on a timing of a corresponding PDCCH (e.g., a particular number of slots after the PDCCH). However, when multiple PDCCHs are used, the timings of the multiple PDCCHs may differ. In some cases, the PDCCH to be used for PUCCH timing may be the PDCCH corresponding to the PDCCH candidate that is indicated first in the PDCCH candidate pair. For example, if PDCCH candidate 1A is indicated before PDCCH candidate 1B in an RRC message, then the PDCCH corresponding to PDCCH candidate 1A may be used to determine resources for the PUCCH. In some aspects, the PDCCH that occurs earlier in time may be used to determine resources for the PUCCH. In some aspects, the PDCCH that occurs later in time may be used to determine resources for the PUCCH. In this way, hybrid automatic repeat request (HARQ) acknowledgement (ACK) ambiguities between the UE <NUM> and a base station <NUM> regarding PUCCH timing may be reduced or eliminated.

Although some operations are described herein in connection with a pair of corresponding PDCCH candidates, similar operations may be performed in connection with a set of corresponding PDCCH candidates, such as <NUM> PDCCH candidates from <NUM> different CORESETs (e.g., corresponding to <NUM> different TRPs), <NUM> PDCCH candidates from <NUM> different CORESETs (e.g., corresponding to <NUM> different TRPs), and/or the like. Additionally, or alternatively, although the indication of example <NUM> shows multiple pairs of corresponding PDCCH candidates, similar operations may be performed in connection with a single pair of corresponding PDCCH candidates (e.g., for an aggregation level of <NUM>).

<FIG> is a diagram illustrating an example <NUM> relating to downlink control for multiple TRP configurations, in accordance with various aspects of the present disclosure. <FIG> provides additional details of the operations of <FIG>. For example, a configuration described in connection with <FIG> is used by the UE <NUM> to determine one or more decoding operations to be performed on a pair of PDCCH candidates, as described above in connection with reference number <NUM> of <FIG>.

As shown by reference number <NUM>, the first TRP <NUM> (and/or the second TRP <NUM>) transmits a configuration to the UE <NUM>. This configuration is referred to as a decoding configuration because the configuration indicates a manner in which the UE <NUM> is to attempt blind decoding of pairs of PDCCH candidates. In some aspects, the decoding configuration may be semi-statically configured, and/or may be indicated in an RRC message.

In some aspects, the decoding configuration may indicate that the UE <NUM> is to independently decode a first PDCCH candidate on CORESET A, independently decode a second PDCCH candidate on CORESET B, and jointly decode the first PDCCH candidate and the second PDCCH candidate. In this case, the UE <NUM> may attempt <NUM> blind decoding operations per PDCCH candidate pair. As shown, this decoding configuration may be indicated using a bitmap of <NUM>, where the first bit indicates whether to independently decode a PDCCH candidate on CORESET A, the second bit indicates whether to independently decode a PDCCH candidate on CORESET B, and the third bit indicates whether to jointly decode both PDCCH candidates of the PDCCH candidate pair.

In some aspects, the decoding configuration may indicate that the UE <NUM> is to only jointly decode the first PDCCH candidate on CORESET A and the second PDCCH candidate CORESET B without independently decoding the first PDCCH candidate on CORESET A or independently decoding the second PDCCH candidate on CORESET B. In this case, the UE <NUM> may attempt <NUM> blind decoding operation per PDCCH candidate pair. As shown, this decoding configuration may be indicated using a bitmap of <NUM>, using the bit indications described above.

In some aspects, the decoding configuration may indicate that the UE <NUM> is to independently decode the first PDCCH candidate on CORESET A and jointly decode the first PDCCH candidate on CORESET A and the second PDCCH candidate on CORESET B without independently and separately decoding the second PDCCH candidate on CORESET B. For example, CORESET A may be a primary CORESET, and CORESET B may be an assisting CORESET. In this case, the UE <NUM> may attempt <NUM> blind decoding operations per PDCCH candidate pair. As shown, this decoding configuration may be indicated using a bitmap of <NUM>, using the bit indications described above.

As shown by reference number <NUM>, the UE <NUM> may selectively perform at least one of independent decoding of a first PDCCH candidate of a PDCCH candidate pair, independent decoding of a second PDCCH candidate of a PDCCH candidate pair, or joint decoding of both the first PDCCH candidate and the second PDCCH candidate based at least in part on the decoding configuration, in a similar manner as described above in connection with <FIG>. In this way, multi-TRP communications (e.g., coordinated multi-point communications) may be dynamically configured with fewer errors due to reduced ambiguity between the UE <NUM> and the TRPs.

As shown by reference number <NUM>, in some aspects, a PDSCH rate matching configuration may be dynamically configured. The PDSCH rate matching configuration may be used to identify and/or resolve errors, such as when the TRPs transmit DCI on both CORESETs, but the UE <NUM> only receives DCI on one of the CORESETs. For example, the PDSCH rate matching configuration may be explicitly indicated in DCI, may be implicitly indicated (e.g., using a PDSCH configuration relating to multiple TRPs), and/or the like. As shown, the first TRP <NUM> (and/or the second TRP <NUM>) may transmit the PDSCH rate matching configuration to the UE <NUM>. The PDSCH rate matching configuration may indicate that DCI was transmitted on a PDCCH candidate only on CORESET A (e.g., using a bitmap of <NUM>), that DCI was transmitted on a PDCCH candidate only on CORESET B (e.g., using a bitmap of <NUM>), or that DCI was jointly transmitted on the corresponding PDCCH candidates on both CORESETs (e.g., using a bitmap of <NUM>). In some aspects, the PDSCH rate matching configuration may be indicated using a bitmap, such as a <NUM>-bit bitmap, as shown. The PDSCH rate matching configuration may be used to determine a manner in which the PDSCH is to be rated matched around the PDCCH, as described in more detail below in connection with <FIG>.

Although some operations are described herein in connection with a pair of corresponding PDCCH candidates, similar operations may be performed in connection with a set of corresponding PDCCH candidates, such as <NUM> PDCCH candidates from <NUM> different CORESETs (e.g., corresponding to <NUM> different TRPs), <NUM> PDCCH candidates from <NUM> different CORESETs (e.g., corresponding to <NUM> different TRPs), and/or the like. For example, different bitmap sizes and/or decoding configurations may be indicated for different sized sets of corresponding PDCCH candidates, so as to indicate a manner in which all of the corresponding PDCCH candidates, in a set, are to be decoded.

<FIG> is a diagram illustrating an example <NUM> relating to downlink control for multiple TRP configurations, in accordance with various aspects of the present disclosure. <FIG> shows example dropping rules that may be applied by a UE <NUM> when a blind decoding (BD) and/or control channel element (CCE) limit is satisfied and/or exceeded for the UE <NUM>. In some aspects, the BD and/or CCE limit may be configured for a primary cell (PCell) and/or a primary secondary cell (PSCell), and not for a secondary cell (SCell).

As shown by reference number <NUM>, the UE <NUM> may determine that a BD or CCE limit, configured for the UE <NUM>, is exceeded. For example, the UE <NUM> may calculate a number of BD attempts to be performed, a number of CCEs to be decoded, and/or the like, and may determine that the number exceeds a BD or CCE limit configured for the UE <NUM>. In some aspects, the BD or CCE limit may be larger when the UE <NUM> is configured to monitor multiple CORESETs for multi-TRP communications (e.g., according to techniques described herein) as compared to a BD or CCE limit configured for the UE <NUM> when the UE is not configured to monitor multiple CORESETs for multi-TRP communications (e.g., when the UE <NUM> is configured to monitor a single CORESET and/or is configured for communication with a single TRP and/or base station <NUM>).

When the calculated number exceeds the BD or CCE limit, then the UE <NUM> may identify one or more particular pairs of PDCCH candidates to be dropped so that the BD or CCE limit is not exceeded. The UE <NUM> may apply a dropping rule to identify the pairs of PDCCH candidates to be dropped, as described below. The dropping rule may be preconfigured or predetermined for the UE <NUM> (e.g., based at least in part on a 3GPP standard), and/or may be indicated to the UE <NUM> by a base station <NUM> (e.g., a TRP and/or the like). In some aspects, the dropping rule may be based at least in part on a search space identifier (SSID), which may be used to determine which PDCCH candidate pair(s) are to be dropped.

For example <NUM>, four PDCCH candidate pairs exist (e.g., continuing with the example from reference number <NUM> of <FIG>), shown as a first pair of candidate 1A and candidate 1B, a second pair of candidate 2A and 2B, a third pair of candidate 3A and 3B, and a fourth pair of candidate 4A and 4B.

As shown by reference number <NUM>, in some aspects, the dropping rule may indicate that when a smallest SSID, corresponding to one of the PDCCH candidates in the pair, matches a particular SSID, then that pair is to be dropped. For example, a pair of PDCCH candidates may be dropped if the smallest SSID associated with the pair matches an SSID of <NUM>. In this case, and as shown by reference number <NUM>, the second pair (with SSIDs of <NUM> and <NUM>) and the fourth pair (with SSIDs of <NUM> and <NUM>) may be dropped, and the first pair and the third pair may be decoded. Although the third pair includes a PDCCH candidate associated with an SSID of <NUM>, there is a smaller SSID associated with the third pair (SSID <NUM>), and so the third pair is not dropped. In this case, the TRP(s) may apply a similar dropping rule, and may not transmit using PDCCH candidates from the second pair or the fourth pair to avoid wasting resources.

As shown by reference number <NUM>, in some aspects, the dropping rule may indicate that when a first SSID, corresponding to the PDCCH candidate indicated first in the pair (e.g., indicated and/or listed before the other PDCCH candidate in the indication described above in connection with reference number <NUM> of <FIG>), matches a particular SSID, then that pair is to be dropped. For example, a pair of PDCCH candidates may be dropped if the first SSID associated with the pair matches an SSID of <NUM>. In this case, and as shown by reference number <NUM>, the second pair (with SSIDs of <NUM> and <NUM>) and the third pair (with SSIDs of <NUM> and <NUM>) may be dropped, and the first pair and the fourth pair may be decoded. Although the fourth pair includes a PDCCH candidate associated with an SSID of <NUM>, this SSID is associated with the PDCCH candidate that is listed second in the indication (e.g., candidate 4B, where candidate 4A is listed first, before candidate 4B), and so the fourth pair is not dropped. In this case, the TRP(s) may apply a similar dropping rule, and may not transmit using PDCCH candidates from the second pair or the third pair to avoid wasting resources.

In some aspects, the dropping rule may be based at least in part on a priority associated with an SSID. For example, a smaller SSID may have a higher priority. For pairs (or sets) of PDCCH candidates, the smallest SSID among the pair may indicate the priority for the pair. Alternatively, the first SSID listed in the indication may indicate the priority for the pair. In this way, a single SSD may be selected for the pair to determine a dropping priority associated with the pair.

For example, when the smallest SSID in the pair indicates the priority for the pair, the priority, from highest to lowest, may be the third pair (with a smallest SSID of <NUM>, and a next smallest of <NUM>), the first pair (with a smallest SSID of <NUM> and a next smallest of <NUM>), the fourth pair (with a smallest SSID of <NUM> and a next smallest of <NUM>), and the second pair (with a smallest SSID of <NUM> and a next smallest of <NUM>). Alternatively, the first and third pairs may have a same higher priority (e.g., due to the same smallest SSID), and the second and fourth pairs may have a same lower priority (e.g., due to the same smallest SSID).

As another example, when the first SSID in the pair indicates the priority for the pair, the priority, from highest to lowest, may be the first pair (with a first SSID of <NUM>), the third pair (with a first SSID of <NUM>, and a second SSID of <NUM>), the second pair (with a first SSID of <NUM> and a second SSID of <NUM>), and the fourth pair (with a first SSID of <NUM>). Alternatively, the second and third pairs may have a same priority (e.g., due to the same first SSID).

As shown by reference number <NUM>, in some aspects, the dropping rule may indicate that joint decoding of one or more PDCCH candidate pairs is to be dropped before independent decoding of the PDCCH candidates included in those pair(s). For example, the UE <NUM> may independently decode each PDCCH candidate (e.g., 1A through 4B) from the PDCCH candidate pairs without applying joint decoding of any of the PDCCH candidate pairs. This may reduce the number of BD and/or CCE attempts by the number of PDCCH candidate pairs to be decoded. In this case, the TRP(s) may apply a similar dropping rule, and may not jointly transmit when the BD and/or CCE limit is exceeded to avoid wasting resources.

In some aspects, the joint decoding dropping rule described in connection with reference number <NUM> may be applied in combination with one of the dropping rules described in connection with reference numbers <NUM>-<NUM> (e.g., using SSID matching) to drop joint decoding for some, but not all, of the PDCCH candidate pairs. In this case, the TRP(s) may apply a similar dropping rule, and may not jointly transmit for those PDCCH candidate pairs to avoid wasting resources.

Although some operations are described herein in connection with a pair of corresponding PDCCH candidates, similar operations may be performed in connection with a set of corresponding PDCCH candidates, such as <NUM> PDCCH candidates from <NUM> different CORESETs (e.g., corresponding to <NUM> different TRPs), <NUM> PDCCH candidates from <NUM> different CORESETs (e.g., corresponding to <NUM> different TRPs), and/or the like. For example, the dropping rule may apply to the smallest SSID associated with the set (e.g., when the set is not a pair), the first SSID listed in the indication, and/or the like.

<FIG> is a diagram illustrating an example <NUM> relating to downlink control for multiple TRP configurations, in accordance with various aspects of the present disclosure. <FIG> shows examples of how a PDSCH may be rate matched around one or more PDCCHs (e.g., for flexible reconfiguration of one or more CORESETs that include the one or more PDCCHs).

As shown by reference number <NUM>, a CORESET may include a first PDCCH that includes DCI for scheduling a PDSCH, and the first PDCCH may be quasi co-located with the PDSCH. As shown by reference number <NUM>, a CORESET may include a second PDCCH that includes DCI for scheduling the PDSCH, and the second PDCCH may not be quasi co-located with the PDSCH. As shown by reference number <NUM>, a CORESET may include a third PDCCH that does not include DCI for scheduling the PDSCH. When two channels (or beams) are quasi co-located, one or more properties of one of the channels (or beams) can be used to infer the corresponding one or more properties of the other channel (or beam), such as a delay spread, a Doppler spread, a frequency shift, an average gain, an average delay, an average received power, a received timing, and/or the like.

As shown by reference number <NUM>, in some aspects, the PDSCH may be rate matched around all PDCCHs that include DCI with scheduling information for the PDSCH. In this case, the PDSCH may be rate matched around the first PDCCH and the second PDCCH, both of which include DCI with scheduling information for the PDSCH. In some aspects, the third PDCCH may be reconfigured to carry the PDSCH.

In some aspects, the PDSCH is rate matched around a first PDCCH, corresponding to a first PDCCH candidate of a PDCCH candidate pair, and a second PDCCH corresponding to a second PDCCH candidate of the PDCCH candidate pair. In some aspects, rate matching may be performed in this manner regardless of a decoding outcome (e.g., regardless of whether joint decoding succeeds or fails, regardless of whether each independent decoding succeeds or fails, and/or the like) when joint decoding is configured for the UE. Additionally, or alternatively, rate matching may be performed in this manner regardless of whether the first PDCCH and the second PDCCH carry DCI with scheduling information for the PDSCH, regardless of whether the first PDSCH and the second PDCCH are both quasi co-located with the PDSCH, and/or the like. In this way, ambiguities and/or mismatches between the UE <NUM> and the base station <NUM> (e.g., TRP), with regard to rate matching, may be reduced.

As shown by reference number <NUM>, in some aspects, the PDSCH may be rate matched around all PDCCHs that include DCI with scheduling information for the PDSCH and that are quasi co-located with the PDSCH. In this case, the PDSCH may be rate matched around the first PDCCH, which includes DCI with scheduling information for that PDCCH and which is quasi co-located with the PDSCH. Additionally, or alternatively, the PDSCH may not be rate matched around the second PDCCH, which includes DCI with scheduling information for that PDCCH, but which is not quasi co-located with the PDSCH. In some aspects, the second PDCCH and the third PDCCH may be reconfigured to carry the PDSCH.

In some aspects, if the CORESET includes one or more wideband reference signals (e.g., a wideband demodulation reference signal (DMRS) and/or the like), the PDSCH may be rate matched around one or more PDCCHs (e.g., using a technique described above) and the one or more wideband reference signals. In some aspects, the PDSCH may be rate matched around one or more wideband reference signals corresponding to the one or more PDCCHs around which the PDSCH is to be rate matched.

In some aspects, the UE <NUM> may determine the PDSCH rate matching scheme based at least in part on a decoding configuration indicated in DCI (e.g., explicitly or implicitly), as described above in connection with reference number <NUM> of <FIG>. For example, the decoding configuration may indicate which PDCCHs and/or PDCCH candidates carry DCI for the PDSCH, and the UE <NUM> may rate match the PDSCH around one or more of those PDCCHs according to a rate matching scheme described above. In this way, ambiguities and/or mismatches between the UE <NUM> and the base station <NUM> (e.g., TRP), with regard to rate matching, may be reduced by indicating the PDCCHs with DCI in case the UE <NUM> does not correctly receive DCI in one or more of the PDCCHs (e.g., due to propagation loss and/or the like).

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM> and/or the like) performs operations relating to downlink control for multiple TRP configurations.

As shown in <FIG>, in some aspects, process <NUM> may include receiving an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states (block <NUM>). For example, the UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive an indication of a set of corresponding PDCCH candidates that includes at least a first PDCCH candidate included in a first CORESET and a corresponding second PDCCH candidate included in a second CORESET, as described above in connection with <FIG>. In some aspects, the first CORESET and the second CORESET have different TCI states.

As further shown in <FIG>, in some aspects, process <NUM> may include selectively performing, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate (block <NUM>). For example, the UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may selectively perform, based at least in part on a configuration, at least one of: independent decoding of the first PDCCH candidate, independent decoding of the second PDCCH candidate, or joint decoding of the first PDCCH candidate and the second PDCCH candidate, as described above in connection with <FIG>.

In a first aspect, the indication identifies multiple sets of corresponding PDCCH candidates, wherein each set of corresponding PDCCH candidates includes a PDCCH candidate, from the first CORESET, that corresponds to another PDCCH candidate from the second CORESET.

In a second aspect, alone or in combination with the first aspect, each set of corresponding PDCCH candidates includes only a pair of corresponding PDCCH candidates.

In a third aspect, alone or in combination with one or more of the first and second aspects, downlink control information is the same for a first PDCCH corresponding to the first PDCCH candidate and a second PDCCH corresponding to the second PDCCH candidate.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first PDCCH candidate and the second PDCCH candidate are associated with a same aggregation level.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first PDCCH candidate and the second PDCCH candidate are associated with different aggregation levels.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of the set of corresponding PDCCH candidates is received via a radio resource control (RRC) message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the configuration is indicated via a radio resource control (RRC) message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the configuration indicates that the UE is to independently decode the first PDCCH candidate, independently decode the second PDCCH candidate, and jointly decode the first PDCCH candidate and the second PDCCH candidate.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the configuration indicates that the UE is to only jointly decode the first PDCCH candidate and the second PDCCH candidate without independently decoding the first PDCCH candidate or independently decoding the second PDCCH candidate.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the configuration indicates that the UE is to independently decode the first PDCCH candidate and jointly decode the first PDCCH candidate and the second PDCCH candidate without independently decoding the second PDCCH candidate.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the first CORESET and the second CORESET include a same number of PDCCH candidates.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, each PDCCH candidate from the first CORESET maps to one respective PDCCH candidate from the second CORESET, and wherein each PDCCH candidate from the second CORESET maps to one respective PDCCH candidate from the first CORESET.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the first CORESET and the second CORESET include a different number of PDCCH candidates.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, at least one PDCCH candidate from the first CORESET maps to multiple PDCCH candidates from the second CORESET, or wherein at least one PDCCH candidate from the second CORESET maps to multiple PDCCH candidates from the first CORESET.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, a blind decoding (BD) or control channel element (CCE) limit, configured for the UE, is larger when the UE is configured to monitor multiple CORESETs as compared to a BD or CCE limit configured for the UE when the UE is configured to monitor a single CORESET.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, a particular set of corresponding PDCCH candidates is dropped based at least in part on a blind decoding (BD) or control channel element (CCE) limit and a determination that a particular PDCCH candidate, included in the particular set, is associated with a search space identifier of a search space for which PDCCH candidates are to be dropped.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the particular PDCCH candidate is associated with a smallest search space identifier among PDCCH candidates in the particular set of corresponding PDCCH candidates.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the particular PDCCH candidate is indicated, in the indication of the set of corresponding PDCCH candidates, before all other PDCCH candidates in the particular set of corresponding PDCCH candidates.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, joint decoding of one or more sets of corresponding PDCCH candidates is dropped before independent decoding of the one or more sets of corresponding PDCCH candidates based at least in part on a blind decoding (BD) or control channel element (CCE) limit.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, a blind decoding (BD) or control channel element (CCE) limit is configured for the UE for at least one of a primary cell (PCell) or a primary secondary cell (PSCell), and not for a secondary cell (SCell).

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, a physical downlink shared channel (PDSCH) is rate matched around all PDCCHs that include downlink control information (DCI) with scheduling information for the PDSCH.

In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, a physical downlink shared channel (PDSCH) is rate matched around a first PDCCH corresponding to the first PDCCH candidate and a second PDCCH corresponding to the second PDCCH candidate.

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the PDSCH is rate matched around the first PDCCH and the second PDCCH regardless of a decoding outcome when joint decoding is configured for the UE.

In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, a physical downlink shared channel (PDSCH) is rate matched around all PDCCHs that include downlink control information (DCI) with scheduling information for the PDSCH and that are quasi co-located with the PDSCH.

In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, a physical downlink shared channel (PDSCH) is rate matched around one or more PDCCHs and one or more corresponding wideband demodulation reference signals.

In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the configuration is explicitly indicated in downlink control information (DCI).

In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the configuration is determined based at least in part on a physical downlink shared channel (PDSCH) configuration.

In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, resources of a physical uplink control channel (PUCCH) are determined based at least in part on one or more of: a PDCCH corresponding to a PDCCH candidate that is indicated first in the indication of the set of corresponding PDCCH candidates, a timing of an earliest PDCCH associated with the set of corresponding PDCCH candidates, a timing of a latest PDCCH associated with the set of corresponding PDCCH candidates, or a combination thereof.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a base station (e.g., base station <NUM>, TRP <NUM>, TRP <NUM>, and/or the like) performs operations relating to downlink control for multiple TRP configurations.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting an indication of a set of corresponding physical downlink control channel (PDCCH) candidates that includes at least a first PDCCH candidate included in a first control resource set (CORESET) and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication (TCI) states (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit an indication of a set of corresponding PDCCH candidates that includes at least a first PDCCH candidate included in a first CORESET and a corresponding second PDCCH candidate included in a second CORESET, as described above in connection with <FIG>. In some aspects, the first CORESET and the second CORESET have different TCI states.

As further shown in <FIG>, in some aspects, process <NUM> may include selectively transmitting, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may selectively transmit, based at least in part on a configuration, on the first PDCCH candidate, on the second PDCCH candidate, or on both the first PDCCH candidate and the second PDCCH candidate, as described above in connection with <FIG>.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first PDCCH candidate the second PDCCH candidate are associated with a same aggregation level.

In a sixth aspect, alone or in combination with one or more of the first through seventh aspects, the indication of the set of corresponding PDCCH candidates is transmitted via a radio resource control (RRC) message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the configuration is transmitted to a user equipment (UE) via a radio resource control (RRC) message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the configuration indicates that a user equipment (UE) is to independently decode the first PDCCH candidate, independently decode the second PDCCH candidate, and jointly decode the first PDCCH candidate and the second PDCCH candidate.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the configuration indicates that a user equipment (UE) is to only jointly decode the first PDCCH candidate and the second PDCCH candidate without independently decoding the first PDCCH candidate or independently decoding the second PDCCH candidate.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the configuration indicates that a user equipment (UE) is to independently decode the first PDCCH candidate and jointly decode the first PDCCH candidate and the second PDCCH candidate without independently decoding the second PDCCH candidate.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, a blind decoding (BD) or control channel element (CCE) limit is larger when the base station is configured for multiple CORESETs as compared to a BD or CCE limit configured when the base station is configured for a single CORESET.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, a blind decoding (BD) or control channel element (CCE) limit is configured for at least one of a primary cell (PCell) or a primary secondary cell (PSCell), and not for a secondary cell (SCell).

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the PDSCH is rate matched around the first PDCCH and the second PDCCH when joint decoding is configured.

In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the configuration is explicitly indicated to a user equipment (UE) in downlink control information (DCI).

In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the configuration is indicated to a user equipment (UE) using a physical downlink shared channel (PDSCH) configuration.

In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, resources of a physical uplink control channel (PUCCH) are indicated based at least in part on one or more of: a PDCCH corresponding to a PDCCH candidate that is indicated first in the indication of the set of corresponding PDCCH candidates, a timing of an earliest PDCCH associated with the set of corresponding PDCCH candidates, a timing of a latest PDCCH associated with the set of corresponding PDCCH candidates, or a combination thereof.

Claim 1:
A method (<NUM>) of wireless communication performed by a user equipment, UE, comprising:
receiving (<NUM>) an indication of a set of corresponding physical downlink control channel, PDCCH, candidates that includes at least a first PDCCH candidate included in a first control resource set, CORESET, and a corresponding second PDCCH candidate included in a second CORESET, wherein the first CORESET and the second CORESET have different transmission configuration indication, TCI, states; and
characterized by receiving a decoding configuration that indicates whether the UE is to independently decode the first PDCCH candidate, whether the UE is to independently decode the second PDCCH candidate and whether the UE is to jointly decode the first PDCCH candidate and the second PDCCH candidate; and
selectively performing (<NUM>), based at least in part on the decoding configuration, at least one of:
independent decoding of the first PDCCH candidate,
independent decoding of the second PDCCH candidate, or
joint decoding of the first PDCCH candidate and the second PDCCH candidate.