CONTROL RESOURCE SET AND PHYSICAL DOWNLINK CONTROL CHANNEL PUNCTURING

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a control resource set (CORESET) configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of resource blocks in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of physical downlink control channel (PDCCH) symbols in the CORESET, a resource element group (REG)-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The UE may receive the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration. 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 control resource set (CORESET) and physical downlink control channel (PDCCH) puncturing.

BACKGROUND

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a control resource set (CORESET) configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of resource blocks (RBs) in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of physical downlink control channel (PDCCH) symbols in the CORESET, a resource element group (REG)-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The method may include receiving the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The method may include transmitting the CORESET in the transmission bandwidth based at least in part on the puncturing configuration.

Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The one or more processors may be configured to receive the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

Some aspects described herein relate to a network node for wireless communication. The network node may include a one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The one or more processors may be configured to transmit the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The apparatus may include means for receiving the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, where the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The apparatus may include means for transmitting the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

DETAILED DESCRIPTION

A wireless communication system may be designed with a minimum transmission bandwidth that can be used for transmission and reception of a communication. However, it may be desirable to support transmission and reception of communications using a comparatively smaller transmission bandwidth. For example, a New Radio (NR) system may be designed with a minimum transmission bandwidth of 5 megahertz (MHz) with 24 resource blocks (RBs) in frequency range 1 (FR1) (e.g., with 15 kilohertz (kHz) subcarrier spacing). In such a system, it may be desirable to support wireless communication using a transmission bandwidth in FR1 that is smaller than 5 MHz, such as 3 MHz (e.g., to reduce radio resource usage, improve network efficiency, or the like).

However, with the comparatively smaller transmission bandwidth (e.g., maximum transmission bandwidth of 15 RBs or 16 RBs for a 3 MHz channel bandwidth), larger aggregation levels (ALs) associated with communication of a physical downlink control channel (PDCCH) may not be supported when using legacy control channel element (CCE)-to-resource element group (REG) mapping, which can result in PDCCH detection performance loss.

Some techniques and apparatuses described herein enable CORESET and PDCCH puncturing. In some aspects, a network node may transmit, and a UE may receive, a puncturing configuration associated with a CORESET to be received in a transmission bandwidth. In some aspects, the puncturing configuration may indicate, for example, a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The network node may then transmit, and the UE may receive, the CORESET in the transmission bandwidth based at least in part on the puncturing configuration.

In this way, the CORESET (e.g., a PDCCH transmitted in the CORESET) may be punctured so that the CORESET is within the transmission bandwidth, thereby improving PDCCH performance detection and, more generally, improving reliability of PDCCH communication. Additional details are provided below.

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive a control resource set (CORESET) configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of physical downlink control channel (PDCCH) symbols in the CORESET, a resource element group (REG)-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET; and receive the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, the network node110may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET; and transmit the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

In some aspects, a UE120includes means for receiving a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET; and/or means for receiving the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration. The means for the UE120to 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.

In some aspects, a network node110includes means for transmitting a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET; and/or means for transmitting the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration. The means for the network node110to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

A wireless communication system may be designed with a minimum transmission bandwidth that can be used for transmission and reception of a communication. However, it may be desirable to support transmission and reception of communications using a comparatively smaller transmission bandwidth. For example, an NR system may be designed with a minimum transmission bandwidth of 5 megahertz (MHz) with 24 resource blocks (RBs) in frequency range 1 (FR1) (e.g., with 15 kilohertz (kHz) subcarrier spacing). In such a system, it may be desirable to support wireless communication using a transmission bandwidth in FR1 that is smaller than 5 MHz, such as 3 MHz (e.g., to reduce radio resource usage, improve network efficiency, or the like). Such a communication may be referred to as a narrowband communication.

However, with the comparatively smaller transmission bandwidth (e.g., maximum transmission bandwidth of 15 RBs or 16 RBs for a 3 MHz channel bandwidth), larger aggregation levels (ALs) associated with communication of a PDCCH may not be supported when using legacy control channel element (CCE)-to-REG mapping, which results in PDCCH detection performance loss.

FIG.4is a diagram illustrating an example of an impact of the use of a comparatively smaller transmission bandwidth on communication of a PDCCH. The example shown inFIG.4is for a transmission bandwidth with a maximum transmission bandwidth of 15 RBs in a 3 MHz channel bandwidth. Thus, a CORESET (e.g., a set of resources in which a PDCCH communication is to be communicated) in this example can be communicated using a maximum transmission bandwidth of 15 RBs in the 3 MHz channel bandwidth. Further, the example shown inFIG.4is for a 3-symbol (S0, S1, S2) PDCCH, with an REG-bundle size of 6 (e.g., 6 REGs per REG-bundle). In the 3 MHz channel bandwidth, a legacy synchronization signal (SS)/physical broadcast channel (PBCH) block with 20 RBs may be punctured into 15 RBs. The offset from the smallest RB index (e.g., RB index 0) of the CORESET to the smallest RB index of the common RB overlapping with the first RB of the corresponding SS/PBCH block after puncturing is equal to zero.

However, as illustrated inFIG.4, a quantity of RBs in the CORESET may be configured such that the quantity of RBs in the CORESET is larger than the transmission bandwidth. This may be the case because one REG-bundle with a size L is the basic unit for PDCCH interleaving and precoding, with a CCE comprising a quantity of REG-bundles equal to 6/L. As a result, as shown inFIG.4, an RB or an REG-bundle may be at least partially outside of the transmission bandwidth. Therefore, a network node that is to transmit the CORESET, and a UE that is to receive the CORESET, should be configured such that the RB or REG-bundle that is at least partially outside of the transmission bandwidth is handled in a way so as to reduce PDCCH detection performance loss.

Some techniques and apparatuses described herein enable CORESET and PDCCH puncturing. In some aspects, a network node may transmit, and a UE may receive, a puncturing configuration associated with a CORESET to be received in a transmission bandwidth. In some aspects, the puncturing configuration may indicate, for example, a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The network node may then transmit, and the UE may receive, the CORESET in the transmission bandwidth based at least in part on the puncturing configuration. In this way, the CORESET (e.g., a PDCCH transmitted in the CORESET) may be punctured so that the CORESET is within the transmission bandwidth, thereby improving PDCCH performance detection and, more generally, improving reliability of PDCCH communication. Additional details are provided below.

FIGS.5A-5Eare diagrams illustrating examples associated with CORESET and PDCCH puncturing, in accordance with aspects of the present disclosure. As shown inFIG.5A, an example500includes communication between a network node110and a UE120. In some aspects, the network node110and the UE120may be included in a wireless network, such as a wireless network100. The network node110and the UE120may communicate via a wireless access link, which may include an uplink and a downlink.

As shown at reference502in example500, the network node110may transmit, and the UE120may receive, a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth. The CORESET configuration indicating puncturing is a configuration that indicates a manner in which the CORESET is to be punctured (e.g., such that the information is carried in the punctured portion of the CORESET). Such a CORESET configuration is herein referred to as a puncturing configuration. In some aspects, the CORESET configuration may be, for example, a configuration for CORESET 0 (e.g., such that CORESET 0 is to be punctured according to the puncturing indicated by the CORESET configuration).

In some aspects, the puncturing configuration indicates that RB-level puncturing is to be applied to the CORESET. That is, the puncturing configuration may in some aspects indicate that one or more RBs of the CORESET that are at least partially outside of the transmission bandwidth are to be punctured. Alternatively, the puncturing configuration may indicate that REG-bundle-level puncturing is to be applied to the CORESET. That is, the puncturing configuration may indicate that one or more REG-bundles of the CORESET that are at least partially outside of the transmission bandwidth are to be punctured. Thus, if a configured quantity of RBs (e.g., in a frequency domain) in the CORESET is greater than a quantity of RBs in the transmission bandwidth, then the puncturing configuration may be used in association with puncturing of the CORESET, with the puncturing configuration indicating that an RB or an REG-bundle of the CORESET that is at least partially outside of the transmission bandwidth is to be punctured.

FIG.5Billustrates examples of CORESET puncturing. In the examples shown inFIG.5B, a 3-symbol PDCCH with an REG-bundle size of 6 is to be transmitted in a 3 MHz channel bandwidth with maximum transmission bandwidth of 15 RBs. The left diagram inFIG.5Billustrates an example of RB-level puncturing. As shown in the left diagram, an RB with RB index 15 is outside of the transmission bandwidth and, therefore, may be punctured according to the puncturing configuration (when the puncturing configuration indicates RB-level puncturing). In some aspects, RB-level puncturing may be applied when PDCCH precoding is performed across REGs, which enables an REG-bundle to be partially punctured, as shown in the left diagram ofFIG.5B. The right diagram inFIG.5Billustrates an example of REG-bundle-level puncturing. As shown in the right diagram, an REG-bundle with index 7 in RB index 14 and 15 is partially outside of the transmission bandwidth and, therefore, may be punctured according to the puncturing configuration (when the puncturing configuration indicates REG-bundle-level puncturing). In some aspects, if REG-bundle-level puncturing is applied, then a total quantity of RBs after puncturing is an integer number of REG-bundles.

In some aspects, the puncturing configuration may indicate one or more parameters based at least in part on which the CORESET is punctured. For example, the puncturing configuration may indicate a quantity of RBs in the frequency domain allocated for the CORESET. As another example, the puncturing configuration may indicate an index of one or more punctured RBs in the frequency domain. As another example, the puncturing configuration may indicate a quantity of PDCCH symbols in the CORESET. As another example, the puncturing configuration may indicate an REG-bundle size associated with the CORESET. As another example, the puncturing configuration may indicate a PDCCH precoding configuration associated with the CORESET. As another example, the puncturing configuration may indicate whether the CORESET is to be interleaved or non-interleaved. Thus, in some aspects, a manner in which the CORESET is to be punctured may depend on, for example, a quantity of PDCCH symbols in the CORESET, an REG-bundle size, or a PDCCH precoding configuration, among other examples.

FIG.5Cis an example of a table associated with indication of the puncturing configuration. In the example shown inFIG.5C, each row corresponds to a set of parameters for a different puncturing configuration. Here, the network node110may indicate the puncturing configuration to the UE120by transmitting an indication of a puncturing configuration index corresponding to a puncturing configuration to be applied to a CORESET to be communicated in the transmission bandwidth.

In some aspects, a frequency resource allocation granularity associated with the CORESET may be smaller than 6 RBs in the frequency domain, and may be a greatest common factor with a quantity of RBs in the frequency domain in the CORESET. For example, a frequency resource allocation granularity (e.g., an RB group) for the CORESET may be smaller than 6 RBs, and may be set as the greatest common factor of a CORESET with less than 5 MHz (e.g., 1 RB for a CORESET with a size of 15 RBs or 16 RBs).

As shown inFIG.5Aat reference504, the network node110may transmit, and the UE120may receive, the CORESET in the transmission bandwidth based at least in part on the puncturing configuration.

In some aspects, when transmitting the CORESET, the network node110may transmit with zero power in an RB or an REG-bundle that is at least partially outside of the transmission bandwidth. For example, the network node110may apply legacy CCE-to-REG mapping, but may zero out transmission power for the punctured RB or the REG-bundle.

In some aspects, in association with transmitting the CORESET, the network node110may apply PDCCH precoding across all REGs of the CORESET in association with applying resource-block-level puncturing. Thus, in some aspects, puncturing may be based at least in part on PDCCH precoding across all REGs. In some aspects, example, for legacy CORESET 0, precoding is within an REG bundle, but for CORESET 0 with a transmission bandwidth of less than 5 MHz, the network node110may apply precoding across all REGs (e.g., to reduce a quantity of punctured RBs). In some aspects, if a PDCCH precoding is to be applied across all REGs (e.g., if a precoder granularity is set to allContiguousRBs), then the same precoding is used across all the REGs in the CORESET and RB-level puncturing is supported.

Alternatively, in association with transmitting the CORESET, the network node110may in some aspects apply PDCCH precoding within each REG of the CORESET in association with applying REG-bundle-level puncturing. Thus, in some aspects, puncturing may be based at least in part on PDCCH precoding within each REG-bundle. In some aspects, if PDCCH precoding is applied within each REG-bundle (e.g., if a precoder granularity is set to sameAsREG-bundle), then the same precoding is used with an REG-bundle and REG-bundling-level puncturing is supported (e.g., when partial REG-bundle precoding is not permitted).

In some aspects, in association with receiving the CORESET, the UE120may perform PDCCH detection within a search space, and may set a log-likelihood ratio (LLR) of an RB or an REG-bundle that is at least partially outside of the transmission bandwidth to zero. That is, when performing PDCCH detection in association with receiving the CORESET, the UE120may in some aspects zero out the one or more punctured RBs or REG-bundles. In such an aspect, the UE120may perform decoding as if no RB is punctured.

In some aspects, in association with receiving the CORESET, the UE120may perform PDCCH channel estimation, and a DMRS within an RB or an REG-bundle that is at least partially outside of the transmission bandwidth is ignored. That is, when performing PDCCH channel estimation in association with receiving the CORESET, the UE120may in some aspects ignore a DMRS within a punctured RB or REG-bundle. However, if PDCCH precoding is applied within each REG-bundle, then the UE120may in some aspects process the DMRS within the same REG-bundle together (and partial DMRS channel estimation may be not supported).

In some aspects, the network node110may enable one or more AL candidates based at least in part on a code rate after puncturing. Here, the code rate may depend on a ratio of punctured RB(s) or REG-bundle(s) to a total quantity of RBs or REG-bundles in the CORESET. An AL candidate is a PDCCH candidate associated with a given AL, with the PDCCH candidate being a set of resources in which the UE120is to perform blind decoding in association with receiving the CORESET. Here, a comparatively larger ratio of punctured RBs or REG-bundles for a given AL candidate would degrade PDCCH performance. Thus, the PDCCH loss due to puncturing may need to be controlled. For example, if a puncturing threshold of 15% is used (e.g., 15% of a total quantity of RBs or REG-bundles), then RB-level puncturing for an AL candidate associated with AL of 4 or 8 with 1 RB punctured, or for an AL candidate associated with an AL of 8 with 1 REG-bundle punctured, may be enabled. Conversely, for puncturing that exceeds the puncturing threshold, an AL may not be enabled. For example, if a puncturing threshold of 15% is used, then RB-level puncturing for an AL candidate associated with an AL of 2 or 1 with 1 RB punctured, or for an AL candidate associated with an AL of 4 or 2 with 1 REG-bundle punctured, may not be enabled.

In some aspects, whether to enable a given AL candidate for the CORESET with one or more punctured RBs or REG-bundles may be determined based at least in part on a CORESET configuration, a search space set configuration, or using RRC signaling. For example, for a PDCCH in CORESET 0 or in a common search space (CSS), enabled AL candidates for the CORESET with one or more punctured RBs or REG-bundles can be predefined (e.g., preconfigured on the network node110or the UE120). As another example, for a PDCCH in a UE-specific search space (USS) for an RRC-connected UE120, enabled AL candidates for the CORESET with one or more punctured RBs or REG-bundles may be determined by the network node110and configured on the UE120via, for example, a unicast RRC communication. Thus, in some aspects, the network node110or the UE120may determine one or more enabled AL candidates associated with transmitting/receiving the CORESET. In some aspects, the network node110may transmit the CORESET based at least in part on an enabled AL candidate of the one or more enabled AL candidates. The UE120, in association with receiving the CORESET, may perform blind decoding on one or more PDCCH candidates associated with the one or more enabled AL candidates.

In some aspects, a quantity of PDCCH candidates per enabled AL candidate is based at least in part on a quantity of RBs (e.g., in a frequency domain) in the CORESET, the quantity of PDCCH symbols in the CORESET, or the REG-bundle size associated with the CORESET. That is, a quantity of PDCCH candidates per AL can in some aspects be adjusted based on the quantity of RBs in the CORESET, a quantity of symbols in the CORESET, or the REG-bundle size. In some aspects, a quantity of PDCCH candidates per enabled AL candidate for one or more enabled AL candidates is based at least in part on a quantity of CCEs of the CORESET before puncturing.FIG.5Dis an example of a table associated with determination of the quantity of the CCEs in the CORESET and the corresponding enabled AL candidates. The number of CCEs NCCEis equal to the quantity of RBs times a quantity of symbols in the CORESET and divided by 6. The maximum number of PDCCH candidates per AL is equal to └NCCE/AL┘. In the example shown inFIG.5D, each row corresponds to a set of parameters associated with a different set of enabled AL candidates. In some aspects, the network node110or the UE120may be configured with a table such as that shown inFIG.5Din order to enable determination of enabled AL candidates associated with transmission of a given CORESET.

In some aspects, the network node110may transmit, and the UE120may receive, an indication of an AL that is to be applied in association with communicating the CORESET. For example, an AL that enables the CCE to be mapped within the transmission bandwidth may be supported. As one example, as illustrated inFIG.5E, an AL of 7 may be used (e.g., rather than an AL of 8). In some aspects, whether to support such an AL may be depend on a ratio of CCEs that fall outside of the transmission bandwidth. For example, an AL of 3 may not be supported because 25% of CCEs would be punctured. In some such aspects, in association with transmitting the CORESET, the network node110may transmit the CORESET based at least in part on the indicated AL. The UE120may, in association with receiving the CORESET, perform blind decoding for one or more PDCCH candidates associated with the indicated AL.

As indicated above,FIGS.5A-5Eare provided as examples. Other examples may differ from what is described with respect toFIG.5A-5E.

FIG.6is a diagram illustrating an example process600performed, for example, by a UE, in accordance with the present disclosure. Example process600is an example where the UE (e.g., UE120) performs operations associated with CORESET and PDCCH puncturing.

As shown inFIG.6, in some aspects, process600may include receiving a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET (block610). For example, the UE (e.g., using reception component802and/or communication manager806, depicted inFIG.8) may receive a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET, as described above.

As further shown inFIG.6, in some aspects, process600may include receiving the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration (block620). For example, the UE (e.g., using reception component802and/or communication manager806, depicted inFIG.8) may receive the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration, as described above.

In a first aspect, the puncturing indicates that resource-block level puncturing is to be applied to the CORESET.

In a second aspect, alone or in combination with the first aspect, the puncturing indicates that REG-bundle-level puncturing is to be applied to the CORESET.

In a third aspect, alone or in combination with one or more of the first and second aspects, a configured quantity of RBs in a frequency domain in the CORESET is greater than a quantity of RBs in the transmission bandwidth, and an RB or an REG-bundle of the CORESET that is at least partially outside of the transmission bandwidth is punctured.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, receiving the CORESET comprises performing PDCCH detection within a search space, wherein an LLR of a resource block or an REG-bundle that is at least partially outside of the transmission bandwidth is set to zero.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, receiving the CORESET comprises performing PDCCH channel estimation, and a demodulation reference signal within a resource block or an REG-bundle that is at least partially outside of the transmission bandwidth is ignored.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, a frequency resource allocation granularity associated with the CORESET is smaller than 6 RBs in a frequency domain and is a greatest common factor with a quantity of RBs in the frequency domain in the CORESET.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process600includes determining one or more enabled aggregation level candidates associated with receiving the CORESET, wherein receiving the CORESET comprises performing blind decoding on one or more PDCCH candidates associated with the one or more enabled aggregation level candidates.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more enabled aggregation level candidates are determined based at least in part on the CORESET configuration, a search space set configuration, or an indication received via radio resource control signaling.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with receiving the CORESET is based at least in part on at least one of a quantity of resource blocks in a frequency domain in the CORESET, the quantity of PDCCH symbols in the CORESET, or the REG-bundle size associated with the CORESET.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process600includes receiving an indication of an aggregation level that is to be applied in association with receiving the CORESET, wherein receiving the CORESET comprises performing blind decoding for one or more PDCCH candidates associated with the aggregation level.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with receiving the CORESET is based at least in part on a quantity of CCEs of the CORESET before puncturing.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the CORESET configuration indicates whether the CORESET is to be interleaved or non-interleaved.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, PDCCH precoding within each REG of the CORESET is applied in association with REG-bundle-level puncturing.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the CORESET is CORESET 0.

FIG.7is a diagram illustrating an example process700performed, for example, by a network node, in accordance with the present disclosure. Example process700is an example where the network node (e.g., network node110) performs operations associated with CORESET and PDCCH puncturing.

As shown inFIG.7, in some aspects, process700may include transmitting a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET (block710). For example, the network node (e.g., using transmission component904and/or communication manager906, depicted inFIG.9) may transmit a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET, as described above.

As further shown inFIG.7, in some aspects, process700may include transmitting the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration (block720). For example, the network node (e.g., using transmission component904and/or communication manager906, depicted inFIG.9) may transmit the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration, as described above.

In a first aspect, the puncturing indicates that resource-block-level puncturing is to be applied to the CORESET.

In a second aspect, alone or in combination with the first aspect, the puncturing indicates that REG-bundle-level puncturing is to be applied to the CORESET.

In a third aspect, alone or in combination with one or more of the first and second aspects, a configured quantity of RBs in a frequency domain in the CORESET is greater than a quantity of RBs in the transmission bandwidth, and an RB or an REG-bundle of the CORESET that is at least partially outside of the transmission bandwidth is punctured.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the CORESET comprises transmitting with zero power in a resource block or an REG-bundle that is at least partially outside of the transmission bandwidth.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, transmitting the CORESET comprises applying PDCCH precoding across all REGs of the CORESET in association with applying resource-block-level puncturing.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, transmitting the CORESET comprises applying PDCCH precoding within each REG of the CORESET in association with applying REG-bundle-level puncturing.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a frequency resource allocation granularity associated with the CORESET is smaller than 6 RBs in a frequency domain and is a greatest common factor with a quantity of RBs in the frequency domain in the CORESET.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process700includes determining one or more enabled aggregation level candidates associated with transmitting the CORESET, wherein the CORESET is transmitted based at least in part on an enabled aggregation level candidate of the one or more enabled aggregation level candidates.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the one or more enabled aggregation level candidates are determined based at least in part on the CORESET configuration, a search space set configuration, or an indication transmitted via radio resource control signaling.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with receiving the CORESET is based at least in part on at least one of a quantity of resource blocks in a frequency domain in the CORESET, the quantity of PDCCH symbols in the CORESET, or the REG-bundle size associated with the CORESET.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process700includes transmitting an indication of an aggregation level that is to be applied in association with transmitting the CORESET, wherein the CORESET is transmitted based at least in part on the aggregation level.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with transmitting the CORESET is based at least in part on a quantity of CCEs of the CORESET before puncturing.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the CORESET configuration indicates whether the CORESET is interleaved or is non-interleaved.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the CORESET is CORESET 0.

FIG.8is a diagram of an example apparatus800for wireless communication, in accordance with the present disclosure. The apparatus800may be a UE, or a UE may include the apparatus800. In some aspects, the apparatus800includes a reception component802, a transmission component804, and/or a communication manager806, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager806is the communication manager140described in connection withFIG.1. As shown, the apparatus800may communicate with another apparatus808, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component802and the transmission component804.

The communication manager806may support operations of the reception component802and/or the transmission component804. For example, the communication manager806may receive information associated with configuring reception of communications by the reception component802and/or transmission of communications by the transmission component804. Additionally, or alternatively, the communication manager806may generate and/or provide control information to the reception component802and/or the transmission component804to control reception and/or transmission of communications.

The reception component802may receive a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The reception component802may receive the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

The communication manager806may determine one or more enabled aggregation level candidates associated with receiving the CORESET, wherein receiving the CORESET comprises performing blind decoding on one or more PDCCH candidates associated with the one or more enabled aggregation level candidates.

The reception component802may receive an indication of an aggregation level that is to be applied in association with receiving the CORESET, wherein receiving the CORESET comprises performing blind decoding for one or more PDCCH candidates associated with the aggregation level.

FIG.9is a diagram of an example apparatus900for wireless communication, in accordance with the present disclosure. The apparatus900may be a network node, or a network node may include the apparatus900. In some aspects, the apparatus900includes a reception component902, a transmission component904, and/or a communication manager906, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager906is the communication manager150described in connection withFIG.1. As shown, the apparatus900may communicate with another apparatus908, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component902and the transmission component904.

The reception component902may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus908. The reception component902may provide received communications to one or more other components of the apparatus900. In some aspects, the reception component902may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus900. In some aspects, the reception component902may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection withFIG.2. In some aspects, the reception component902and/or the transmission component904may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus900via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

The communication manager906may support operations of the reception component902and/or the transmission component904. For example, the communication manager906may receive information associated with configuring reception of communications by the reception component902and/or transmission of communications by the transmission component904. Additionally, or alternatively, the communication manager906may generate and/or provide control information to the reception component902and/or the transmission component904to control reception and/or transmission of communications.

The transmission component904may transmit a CORESET configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of RBs in a frequency domain allocated for the CORESET, an index of one or more punctured RBs in the frequency domain, a quantity of PDCCH symbols in the CORESET, an REG-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET. The transmission component904may transmit the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.

The communication manager906may determine one or more enabled aggregation level candidates associated with transmitting the CORESET, wherein the CORESET is transmitted based at least in part on an enabled aggregation level candidate of the one or more enabled aggregation level candidates.

The transmission component904may transmit an indication of an aggregation level that is to be applied in association with transmitting the CORESET, wherein the CORESET is transmitted based at least in part on the aggregation level.

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a control resource set (CORESET) configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of resource blocks in a frequency domain allocated for the CORESET, an index of one or more punctured resource blocks in the frequency domain, a quantity of physical downlink control channel (PDCCH) symbols in the CORESET, a resource element group (REG)-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET; and receiving the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.Aspect 2: The method of Aspect 1, wherein the puncturing indicates that resource-block level puncturing is to be applied to the CORESET.Aspect 3: The method of any of Aspects 1-2, wherein the puncturing indicates that REG-bundle-level puncturing is to be applied to the CORESET.Aspect 4: The method of any of Aspects 1-3, wherein a configured quantity of resource blocks (RBs) in a frequency domain in the CORESET is greater than a quantity of RBs in the transmission bandwidth, and an RB or an REG-bundle of the CORESET that is at least partially outside of the transmission bandwidth is punctured.Aspect 5: The method of any of Aspects 1-4, wherein receiving the CORESET comprises performing PDCCH detection within a search space, wherein a log-likelihood ratio (LLR) of a resource block or an REG-bundle that is at least partially outside of the transmission bandwidth is set to zero.Aspect 6: The method of any of Aspects 1-5, wherein receiving the CORESET comprises performing PDCCH channel estimation, and wherein a demodulation reference signal within a resource block or an REG-bundle that is at least partially outside of the transmission bandwidth is ignored.Aspect 7: The method of any of Aspects 1-6, wherein a frequency resource allocation granularity associated with the CORESET is smaller than 6 resource blocks (RBs) in a frequency domain and is a greatest common factor with a quantity of RBs in the frequency domain in the CORESET.Aspect 8: The method of any of Aspects 1-7, further comprising determining one or more enabled aggregation level candidates associated with receiving the CORESET, wherein receiving the CORESET comprises performing blind decoding on one or more PDCCH candidates associated with the one or more enabled aggregation level candidates.Aspect 9: The method of Aspect 8, wherein the one or more enabled aggregation level candidates are determined based at least in part on a CORESET configuration, a search space set configuration, or an indication received via radio resource control signaling.Aspect 10: The method of any of Aspects 1-9, wherein a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with receiving the CORESET is based at least in part on at least one of a quantity of resource blocks in a frequency domain in the CORESET, the quantity of PDCCH symbols in the CORESET, or the REG-bundle size associated with the CORESET.Aspect 11: The method of any of Aspects 1-10, further comprising receiving an indication of an aggregation level that is to be applied in association with receiving the CORESET, wherein receiving the CORESET comprises performing blind decoding for one or more PDCCH candidates associated with the aggregation level.Aspect 12: The method of any of Aspects 1-11, wherein a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with receiving the CORESET is based at least in part on a quantity of control channel elements (CCEs) of the CORESET before puncturing.Aspect 13: The method of any of Aspects 1-12, wherein the CORESET configuration indicates whether the CORESET is to be interleaved or non-interleaved.Aspect 14: The method of any of Aspects 1-13, wherein PDCCH precoding within each REG of the CORESET is applied in association with REG-bundle-level puncturing.Aspect 15: The method of any of Aspects 1-14, wherein the CORESET is CORESET 0.Aspect 16: A method of wireless communication performed by a network node, comprising: transmitting a control resource set (CORESET) configuration indicating puncturing associated with a CORESET to be received in a transmission bandwidth, wherein the puncturing indicates at least one of a quantity of resource blocks in a frequency domain allocated for the CORESET, an index of one or more punctured resource blocks in the frequency domain, a quantity of physical downlink control channel (PDCCH) symbols in the CORESET, a resource element group (REG)-bundle size associated with the CORESET, or a PDCCH precoding configuration associated with the CORESET; and transmitting the CORESET in the transmission bandwidth based at least in part on the puncturing indicated by the CORESET configuration.Aspect 17: The method of Aspect 16, wherein the puncturing indicates that resource-block-level puncturing is to be applied to the CORESET.Aspect 18: The method of any of Aspects 16-17, wherein the puncturing indicates that REG-bundle-level puncturing is to be applied to the CORESET.Aspect 19: The method of any of Aspects 16-18, wherein a configured quantity of resource blocks (RBs) in a frequency domain in the CORESET is greater than a quantity of RBs in the transmission bandwidth, and an RB or an REG-bundle of the CORESET that is at least partially outside of the transmission bandwidth is punctured.Aspect 20: The method of any of Aspects 16-19, wherein transmitting the CORESET comprises transmitting with zero power in a resource block or an REG-bundle that is at least partially outside of the transmission bandwidth.Aspect 21: The method of any of Aspects 16-20, wherein transmitting the CORESET comprises applying PDCCH precoding across all REGs of the CORESET in association with applying resource-block-level puncturing.Aspect 22: The method of any of Aspects 16-21, wherein transmitting the CORESET comprises applying PDCCH precoding within each REG of the CORESET in association with applying REG-bundle-level puncturing.Aspect 23: The method of any of Aspects 16-22, wherein a frequency resource allocation granularity associated with the CORESET is smaller than 6 resource blocks (RBs) in a frequency domain and is a greatest common factor with a quantity of RBs in the frequency domain in the CORESET.Aspect 24: The method of any of Aspects 16-23, further comprising determining one or more enabled aggregation level candidates associated with transmitting the CORESET, wherein the CORESET is transmitted based at least in part on an enabled aggregation level candidate of the one or more enabled aggregation level candidates.Aspect 25: The method of Aspect 24, wherein the one or more enabled aggregation level candidates are determined based at least in part on a CORESET configuration, a search space set configuration, or an indication transmitted via radio resource control signaling.Aspect 26: The method of Aspect any of aspects 16-25, wherein a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with receiving the CORESET is based at least in part on at least one of a quantity of resource blocks in a frequency domain in the CORESET, the quantity of PDCCH symbols in the CORESET, or the REG-bundle size associated with the CORESET.Aspect 27: The method of any of Aspects 16-26, further comprising transmitting an indication of an aggregation level that is to be applied in association with transmitting the CORESET, wherein the CORESET is transmitted based at least in part on the aggregation level.Aspect 28: The method of any of Aspects 16-27, wherein a quantity of PDCCH candidates per enabled aggregation level candidate for one or more enabled aggregation level candidates associated with transmitting the CORESET is based at least in part on a quantity of control channel elements (CCEs) of the CORESET before puncturing.Aspect 29: The method of any of Aspects 16-28, wherein the CORESET configuration indicates whether the CORESET is interleaved or is non-interleaved.Aspect 30: The method of any of Aspects 16-29, wherein the CORESET is CORESET 0.Aspect 31: An apparatus for wireless communication at a device, comprising a processor; one or more memories coupled with the processor; and instructions stored in the one or more memories and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-30.Aspect 32: A device for wireless communication, comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to perform the method of one or more of Aspects 1-30.Aspect 33: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-30.Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-30.Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-30.