CONTROL RESOURCE SET PUNCTURING

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive signaling identifying a control resource set (CORESET) puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The UE may decode downlink control information in accordance with the CORESET puncturing pattern. 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 puncturing.

BACKGROUND

SUMMARY

Some aspects described herein relate to a user equipment (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 individually or collectively configured to receive signaling identifying a control resource set (CORESET) puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The one or more processors may be individually or collectively configured to decode downlink control information in accordance with the CORESET puncturing pattern.

Some aspects described herein relate to a network node for wireless communication. The network node 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 individually or collectively configured to output signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The one or more processors may be individually or collectively configured to configure a UE to decode downlink control information in accordance with the CORESET puncturing pattern.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The method may include decoding downlink control information in accordance with the CORESET puncturing pattern.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include outputting signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The method may include configuring a UE to decode downlink control information in accordance with the CORESET puncturing pattern.

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 individually or collectively executed by one or more processors of the UE, may cause the UE to receive signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The set of instructions, when executed by one or more processors of the UE, may cause the UE to decode downlink control information in accordance with the CORESET puncturing pattern.

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 individually or collectively executed by one or more processors of the network node, may cause the network node to output signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The set of instructions, when individually or collectively executed by one or more processors of the network node, may cause the network node to configure a UE to decode downlink control information in accordance with the CORESET puncturing pattern.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The apparatus may include means for decoding downlink control information in accordance with the CORESET puncturing pattern.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for outputting signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The apparatus may include means for configuring a UE to decode downlink control information in accordance with the CORESET puncturing pattern.

DETAILED DESCRIPTION

A control resource set (CORESET) addresses challenges associated with managing and controlling data transmission on a diverse range of frequency bands. The CORESET is a predefined set of physical resource blocks (PRBs) within the frequency domain and slots in the time domain that are reserved for control channel transmission, including scheduling assignments, system control information, and other network instructions. CORESETs enable the network to communicate control signals to a user equipment (UE) in a consistent and structured manner while also providing a mechanism for scheduling transmissions dynamically on a per-UE basis. Moreover, the flexibility of the CORESET configuration contributes to more efficient spectrum utilization and improved capacity. Accordingly, CORESETs allow the network to maintain robust and reliable communications and optimize the user experience, particularly in high-demand wireless communication environments.

CORESET “puncturing” refers to a technique where the control signals, specifically transmitted through CORESETs, are intentionally left blank or “punctured” in certain circumstances to restrict the transmission within a limited bandwidth, or in other circumstances to allow for the transmission of other, potentially higher priority data. CORESET puncturing facilitates the allocation of resources in a dynamic and flexible way, where the specific requirements or demands of the network can be prioritized as needed. For example, if the network has limited transmission bandwidth in a carrier bandwidth, the CORESET could be designed to puncture a legacy CORESET of a minimum bandwidth to a CORESET with a limited transmission bandwidth, such as puncturing legacy minimum 24-resource block (RB) CORESET into a 15-RB CORESET within a 3 MHz channel bandwidth, or puncturing the legacy minimum 24-RB CORESET into a 20-RB CORESET within a 5 MHz channel bandwidth. For example, if a network is experiencing a high demand for data traffic, the CORESET could be punctured to make room for the transmission of additional data, effectively improving network efficiency and capacity. Excessive or inappropriate CORESET puncturing, however, can negatively impact network performance and quality of service since CORESETs carry control information used for network operation. Therefore, CORESET puncturing must be performed with care and diligence.

Various aspects relate generally to CORESET puncturing. Some aspects more specifically relate to CORESET puncturing patterns for certain bandwidths and/or numbers of PRBs. Some aspects more specifically relate to CORESET puncturing patterns for certain RBs offset relative a synchronization signal block (SSB). Some aspects further relate to control channel element (CCE)-to-resource element group (REG) mapping based, at least in part, on the CORESET puncturing. In some examples, a UE receives signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and decodes downlink control information (DCI) in accordance with the CORESET puncturing pattern. In some examples, a network node outputs signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and configures a UE to decode DCI in accordance with the CORESET puncturing pattern.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by receiving signaling identifying a CORESET puncturing pattern, the described techniques can be used to allow the UE to communicate in accordance with a CORESET puncturing pattern from a legacy CORESET (e.g., a legacy CORESET0) to a CORESET (e.g., CORESET0) transmitted in a limited bandwidth. For the CORESET0 indicated by a physical broadcast channel (PBCH)/master information block (MIB) for the UE to detect system information block (SIB) signaling, the legacy CORESET0 has minimum of 24 RBs transmitted in a 5 MHz channel bandwidth. In order to enable CORESET0 transmitted in less than 5 MHz within a 5 MHz channel bandwidth or even in a 3 MHz channel bandwidth, CORESET puncturing can be indicated to puncture from legacy 24-RB CORESET0 to a CORESET0 (e.g., 20-RB) with 3.6 MHz within a 5 MHz channel bandwidth, or to a CORESET0 (e.g., 15-RB) with 2.7 MHz in a 3 MHz channel bandwidth. In some examples, by receiving signaling identifying a CORESET puncturing pattern, the described techniques can be used to allow the UE to communicate in accordance with a CORESET puncturing pattern that improves network operation without significantly sacrificing quality of service. In some examples, by configuring a UE to decode downlink control information in accordance with the CORESET puncturing pattern, the described techniques can be used to communicate control information even in instances where high priority data must be transmitted.

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and decode downlink control information in accordance with the CORESET puncturing pattern. 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 output signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and configure a UE to decode downlink control information in accordance with the CORESET puncturing pattern. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

In some aspects, the UE120includes means for receiving signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and/or means for decoding downlink control information in accordance with the CORESET puncturing pattern. 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, the network node110includes means for outputting signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and/or means for configuring a UE to decode downlink control information in accordance with the CORESET puncturing pattern. The means for the network node to 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.

FIG.4is a diagram illustrating an example resource structure400for wireless communication, in accordance with the present disclosure. Resource structure400shows an example of various groups of resources described herein. As shown, resource structure400may include a subframe405. Subframe405may include multiple slots410. While resource structure400is shown as including 2 slots per subframe, a different number of slots may be included in a subframe (e.g., 4 slots, 8 slots, 16 slots, 32 slots, or another quantity of slots). In some aspects, different types of transmission time intervals (TTIs) may be used, other than subframes and/or slots. A slot410may include multiple symbols415, such as 14 symbols per slot.

The potential control region of a slot410may be referred to as a CORESET420and may be structured to support an efficient use of resources, such as by flexible configuration or reconfiguration of resources of the CORESET420for one or more physical downlink control channels (PDCCHs) and/or one or more physical downlink shared channels (PDSCHs). In some aspects, the CORESET420may occupy the first symbol415of a slot410, the first two symbols415of a slot410, or the first three symbols415of a slot410. Thus, a CORESET420may include multiple resource blocks (RBs) in the frequency domain, and either one, two, or three symbols415in the time domain. In 5G, a quantity of resources included in the CORESET420may be flexibly configured, such as by using radio resource control (RRC) signaling to indicate a frequency domain region (e.g., a quantity of resource blocks) and/or a time domain region (e.g., a quantity of symbols) for the CORESET420.

As illustrated, a symbol415that includes CORESET420may include one or more CCEs425, shown as two CCEs425as an example, that span a portion of the system bandwidth. A CCE425may include downlink control information (DCI) that is used to provide control information for wireless communication. A base station may transmit DCI during multiple CCEs425(as shown), where the quantity of CCEs425used for transmission of DCI represents the aggregation level (AL) used by the BS for the transmission of DCI. InFIG.4, an aggregation level of two is shown as an example, corresponding to two CCEs425in a slot410. In some aspects, different aggregation levels may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

Each CCE425may include a fixed quantity of REGs430, shown as 6 REGs430, or may include a variable quantity of REGs430. In some aspects, the quantity of REGs430included in a CCE425may be specified by a REG bundle size. A REG430may include one resource block, which may include 12 resource elements (REs)435within a symbol415. A resource element435may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

A search space may include all possible locations (e.g., in time and/or frequency) where a PDCCH may be located. A CORESET420may 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) and/or an aggregation level being used. 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 at an aggregation level 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. The set of all possible PDCCH locations for a particular group of UEs may be referred to as a group-common search space. One or more search spaces across aggregation levels may be referred to as a search space (SS) set.

A CORESET420may be interleaved or non-interleaved. An interleaved CORESET420may have CCE-to-REG mapping such that adjacent CCEs are mapped to scattered REG bundles in the frequency domain (e.g., adjacent CCEs are not mapped to consecutive REG bundles of the CORESET420). A non-interleaved CORESET420may have a CCE-to-REG mapping such that all CCEs are mapped to consecutive REG bundles (e.g., in the frequency domain) of the CORESET420.

FIG.5is a diagram illustrating an example500associated with a CORESET puncturing pattern, in accordance with the present disclosure.

As shown in the example500ofFIG.5, for a 3 MHz channel bandwidth with maximum RF transmission bandwidth of 15 RBs using subcarrier spacing of 15 kHz, a synchronization signal block (SSB) puncturing pattern505A-B to reduce the number of resource blocks (RBs) from legacy 20-RB SSB to a 12-RB SSB may include puncturing the first four RBs (RBs 0-3) and the last four RBs (RBs 16-19) of every PBCH symbol. In some aspects, a first puncturing pattern510A for CORESET (e.g., CORESET0 indicated by a PBCH/MIB) to reduce the number of RBs from a legacy 24-RB CORESET to a 15-RB CORESET may include applying offset of 0 RB between the legacy 24-RB CORESET and the legacy 20-RB SSB without puncturing. As shown in the example500, the first three RBs (RBs 0-2) and the last 6 RBs (RBs 18-23) of the first puncturing pattern510A are punctured in every CORESET symbol. With an offset of 0, the puncturing pattern may be predefined as puncturing 3 RBs at lower frequencies and 6 RBs at higher frequencies. Therefore, with an offset of ORB between a lowest RB of the legacy CORESET without puncturing relative to the lowest RB of legacy SSB without puncturing, the 12-RB SSB (RBs 4-15) after puncturing and 15-RB CORESET (RBs 3-17) after puncturing are both transmitted within the 3 MHz channel bandwidth. With an offset, such as an offset of 2 RBs between legacy 24-RB CORESET and the legacy 20-RB SSB without puncturing shown in the example500, the first puncturing pattern510B for CORESET may be predefined as puncturing 6 RBs at lower frequencies and 3 RBs at higher frequencies in every CORESET symbol. Therefore, with an offset of 2 RBs between the lowest RB of the legacy CORESET without puncturing relative to the lowest RB of legacy SSB without puncturing, the 12-RB SSB (RBs 4-15) after puncturing and 15-RB CORESET (RBs 6-20) after puncturing are both transmitted within the 3 MHz channel bandwidth in every CORESET symbol. Regardless of the offset, in some aspects, such as when the REG bundle size is a 6, partial CCEs may be punctured at higher frequencies or lower frequencies. For example, according to the first puncturing pattern510A, the first 3 RBs (RBs 0-2) and the last 6 RBs (RBs 18-23) of the legacy 24-RB CORESET are punctured respectively, resulting in 1.5 CCEs and 3 CCEs punctured in lower and higher frequency in the case of a 3-symbol CORSET, where each CCE has 6 RBs in total with 2 RBs in the frequency domain and 3 symbols in the time domain. Similarly, according to the first puncturing pattern510B, the first 6 RBs (RBs 0-5) and the last 3 RBs (RBs 21-23) of the legacy 24-RB CORESET are punctured respectively, resulting in 3 CCEs and 1.5 CCEs punctured in lower and higher frequency in case of 3-symbol CORESET. On the other hand, if the first 4 RBs (RBs 0-3) and the last 5 RBs (RBs 19-23) of the legacy 24-RB CORESET are punctured respectively, resulting in 2 CCEs and 2.5 CCEs punctured in case of 3-symbol CORESET but 1.3 CCEs and 2.6 CCEs punctured in lower and higher frequency in case of 2-symbol CORSET, where each CCE has 6 RBGs bundled together with 3 RBs in the frequency domain and 2 symbols in the time domain. In order to minimize the partial CCE puncturing, at least one of puncturing an RB number in a lower or higher frequency should be a multiple of RBG-bundle size6.

In a second puncturing pattern515A-B, the RB offset, if any, may be relative to the 12-RB SSB after puncturing with the puncturing pattern505A-B. For example, as shown in the second puncturing pattern515A-B, no RBs are punctured at the lower frequencies, which leaves 9 RBs (RBs 15-23) to be punctured at the higher frequencies. In the second puncturing pattern515A-B, partial CCEs may be punctured at the higher frequencies depending on the number of RBs in an REG bundle and the number of RBs to be punctured. Further, as shown in the example500, the second puncturing pattern515B may have an offset of 2 relative to the 12-RB SSB after puncturing with puncturing pattern505B. Thereafter, with an offset of 0 or 2 RBs between lowest RB of the legacy CORESET before puncturing relative to lowest RB of the SSB after puncturing, the 12-RB SSB (RBs 4-15) after puncturing and 15-RB CORESET (RBs 0-14) after puncturing are both transmitted within the 3 MHz channel bandwidth in every CORESET symbol.

In some aspects, the offset for the puncturing pattern may be zero RBs (e.g., the SSB puncturing pattern505A or the CORESET puncturing pattern510A) or 2 RBs (e.g., the SSB puncturing pattern505B or the CORESET puncturing pattern510B) for a CORESET with 15 RBs punctured from a 24 RB legacy CORESET. Other offsets may be possible so long as the CORESET and SSB are within a max bandwidth relative to the number of RBs and the channel bandwidth. For example, an offset of 4 may not be applicable for 15 RBs with a 3 MHz channel bandwidth, because the SSB and CORESET cannot be transmitted together within a 3 MHz channel bandwidth.

FIGS.6-11are diagrams illustrating examples600-1100associated with different CORESET puncturing patterns, in accordance with the present disclosure.

The example600ofFIG.6illustrates a two-symbol CORESET. Each REG bundle includes 6 REGs bundled together with three RBs in the frequency domain and 2 symbols in the time domain, and the example600shows a total of eight REG bundles in the legacy 24-RB CORESET. A CCE shift (shown as nshift) is shown for each REG bundle. Moreover, the example600illustrates one option with interleaving (e.g., interleaver size of 2) and one option without interleaving. In the example600, the puncturing pattern may be defined as puncturing 3 RBs at lower frequencies and 6 RBs at higher frequencies in every CORESET symbol. There are no partial CCEs punctured at both lower and higher frequencies. Accordingly, as shown, RBs 0-2 and 18-23 are punctured in the options shown in example600.

The example700ofFIG.7illustrates a three-symbol CORESET. Each REG bundle includes 6 REGs bundled together with two RBs in the frequency domain and 3 symbols in the time domain, and the example700shows a total of 12 REG bundles in the legacy 24-RB CORESET. A CCE shift is shown for each REG bundle. Moreover, the example700illustrates one option with interleaving (e.g., interleaver size of 2) and one option without interleaving. Like the example600, in the example700, the puncturing pattern may be defined as puncturing 3 RBs at lower frequencies and 6 RBs at higher frequencies in every CORESET symbol. There is one partial CCE punctured at lower frequency but no partial CCEs punctured at higher frequency. Accordingly, as shown, RBs 0-2 and 18-23 are punctured in the options shown in example700, which results in partial CCE puncturing with respect to REG bundle 2 (with interleaving) or REG bundle 1 (without interleaving), which both include punctured RB 2.

The example800ofFIG.8illustrates a two-symbol CORESET. Each REG bundle includes 6 REGs bundled together with three RBs in the frequency domain and 2 symbols in the time domain, and the example800shows a total of eight REG bundles in the legacy 24-RB CORESET. A CCE shift is shown for each REG bundle. Moreover, the example800illustrates one option with interleaving (e.g., interleaver size of 2) and one option without interleaving. In the example800, the puncturing pattern may be defined as puncturing 6 RBs at lower frequencies and 3 RBs at higher frequencies in every CORESET symbol. Partial CCEs may be punctured at higher frequencies. There are no partial CCEs punctured at both the lower and higher frequencies. Accordingly, as shown, RBs 0-5 and 21-23 are punctured in the options shown in example800.

The example900ofFIG.9illustrates a three-symbol CORESET. Each REG bundle includes 6 REGs bundled together with two RBs in the frequency domain and 3 symbols in the time domain, and the example900shows a total of 12 REG bundles in the legacy 24-RB CORESET. A CCE shift is shown for each REG bundle. Moreover, the example900illustrates one option with interleaving (e.g., interleaver size of 2) and one option without interleaving. Like the example800, in the example900, the puncturing pattern may be defined as puncturing 6 RBs at lower frequencies and 3 RBs at higher frequencies. Partial CCEs may be punctured at higher frequencies. There is one partial CCE punctured at the higher frequency but no partial CCEs punctured at the lower frequency. Accordingly, as shown, RBs 0-5 and 21-23 are punctured in the options shown in example900, which results in partial CCE puncturing with respect to REG bundle 9 (with interleaving) or REG bundle 10 (without interleaving), both of which include the punctured RB 21.

The example1000ofFIG.10illustrates a two-symbol CORESET. Each REG bundle includes 6 REGs bundled together with three RBs in the frequency domain and 2 symbols in the time domain, and the example1000shows a total of eight REG bundles in the legacy 24-RB CORESET. A CCE shift is shown for each REG bundle.

Moreover, the example1000illustrates one option with interleaving (e.g., interleaver size of 2) and one option without interleaving. In the example1000, the puncturing pattern may be defined as puncturing 9 RBs at higher frequencies. There are no partial CCE punctured at both higher and lower frequencies. Accordingly, as shown, RBs 15-23 are punctured in the options shown in example1000.

The example1100ofFIG.11illustrates a three-symbol CORESET. Each REG bundle includes 6 REGs bundled together with two RBs in the frequency domain and 3 symbols in the time domain, and the example1100shows a total of 12 REG bundles in the legacy 24-RB CORESET. A CCE shift is shown for each REG bundle. Moreover, the example1100illustrates one option with interleaving (e.g., interleaver size of 2) and one option without interleaving. Like the example1000, in the example1100, the puncturing pattern may be defined as puncturing 9 RBs at higher frequencies. There is only one partial CCE punctured at a higher frequency and no partial CCEs at a lower frequency. Accordingly, as shown, RBs 15-23 are punctured in the options shown in example1100, which results in one partial CCE puncturing with respect to REG bundle 3 (with interleaving) or REG bundle 7 (without interleaving), both of which include punctured RB15.

For legacy CORESETs, a CCE shift may be a cell identifier used for CCE-to-REG mapping. For CORESETs punctured from, e.g., a legacy 24-RB CORESET to a 15-RB CORESET, a large aggregation level (such as an aggregation level of 8) may not be supported for a CORESET with 15 RBs in certain circumstances, such as if more than two CCEs are punctured, there is a minimal performance gain than smaller AL, e.g., AL of 4, due to puncturing. In the case of a 2-symbol CORESET, more than two CCEs among a legacy 8 CCEs of legacy 24-RB CORESET are punctured with or without interleaving. In the case of a 3-symbol CORESET, more than two CCEs among a legacy 12 CCEs of legacy 24-RB CORESET may be punctured if the puncturing is with interleaving and for an aggregation level of 8. Without interleaving, fewer than two CCEs are punctured for an aggregation level of 8 when the CCE shift is equal to 0, 1, or 2. Otherwise, more than two CCEs are punctured if the aggregation level is 8.

In some aspects, to achieve a desired aggregation level, the CCE-to-REG mapping of the CORESET may be modified based, at least in part, on a CORESET puncturing pattern and configuration parameters for a particular channel bandwidth, such as a 3 MHz channel bandwidth. For a CORESET with 15 RBs, 3 symbols, and no interleaving, the CCE shift may be equal to a variable Y plus the cell identifier mod X. The value for X may be a constant such as, e.g.,3, which may be based, at least in part, on cell randomization and the number of punctured CCEs for a desired aggregation level (e.g.,8). The variable Y may be the number of the CORESET CCEs (before puncturing) minus the number of RBs to be punctured in the lower frequencies. The variable Y may also be equal to the result of the total number of RBs (e.g., 24 RBs) minus the number of RBs to be punctured in the lower frequencies multiplied by the number of symbols for the CORESET and divided by the REG bundle size L. An example equation for Y is shown below.

In another example, such as for a 20-RB CORESET associated with a 5 MHz channel bandwidth, if four RBs are to be punctured from the legacy 24-RB CORESET, there may be up to two CCEs to be punctured and the CCE shift may be equal to the cell identifier. In another example, such as for a CORESET associated with a 3 MHz channel bandwidth, if there are no RBs to be punctured (i.e., CCE-to-REG mapping is directly based on the indicated number of RBs for every symbol of the CORESET), the CCE shift may be equal to the cell identifier.

As indicated above,FIGS.6-11are provided as examples. Other examples may differ from what is described with respect toFIGS.6-11.

FIG.12is a diagram of an example1200associated with decoding DCI signals, in accordance with the present disclosure. As shown inFIG.12, a network node (e.g., network node110, a CU, a DU, and/or an RU) may communicate with a UE (e.g., UE120). In some aspects, the network node and the UE may be part of a wireless network (e.g., wireless network100). The UE and the network node may have established a wireless connection prior to operations shown inFIG.12.

In some aspects, the configuration information may indicate one or more candidate configurations and/or communication parameters. In some aspects, the one or more candidate configurations and/or communication parameters may be selected, activated, and/or deactivated by a subsequent indication. For example, the subsequent indication may select a candidate configuration and/or communication parameter from the one or more candidate configurations and/or communication parameters. In some aspects, the subsequent indication (e.g., an indication described herein) may include a dynamic indication, such as one or more MAC CEs and/or one or more DCI messages, among other examples.

In some aspects, the configuration information may indicate that the UE is to receive signaling identifying a CORESET puncturing pattern. As discussed above, the CORESET puncturing pattern may be based, at least in part, on the number of RBs available before and after a CORESET puncturing process and on the number of symbols of the CORESET.

The UE may configure itself based at least in part on the configuration information. In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the configuration information.

As shown by reference number1210, the UE may transmit, and the network node may receive, a capabilities report. The capabilities report may indicate whether the UE supports a feature and/or one or more parameters related to the feature. For example, the capability information may indicate a capability and/or parameter for CORESET puncturing. As another example, the capabilities report may indicate a capability and/or parameter for decoding DCI signals in accordance with the CORESET puncturing. One or more operations described herein may be based on capability information of the capabilities report. For example, the UE may perform a communication in accordance with the capability information, or may receive configuration information that is in accordance with the capability information. In some aspects, the capabilities report may indicate UE support for applying a CORESET puncturing pattern, CCE-to-REG mapping, modifying CCE shifts, and decoding DCI according to the CORESET puncturing pattern, CCE-to-REG mapping, and modified CCE shifts.

In some aspects, the configuration information described in connection with reference number1205and/or the capabilities report may include information transmitted via multiple communications. Additionally, or alternatively, the network node may transmit the configuration information, or a communication including at least a portion of the configuration information, before and/or after the UE transmits the capabilities report. For example, the network node may transmit a first portion of the configuration information before the capabilities report, the UE may transmit at least a portion of the capabilities report, and the network node may transmit a second portion of the configuration information after receiving the capabilities report.

As shown by reference number1215, the UE may receive, and the network node may transmit, downlink control information in accordance with the CORESET puncturing pattern.

As shown by reference number1220, the UE may configure itself, based at least in part on receiving the indication described in connection with reference number1215, to decode the DCI.

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

FIG.13is a diagram illustrating an example process1300performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process1300is an example where the apparatus or the UE (e.g., UE120) performs operations associated with CORESET puncturing.

As shown inFIG.13, in some aspects, process1300may include receiving signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET (block1310). For example, the UE (e.g., using communication manager1506, depicted inFIG.15) may receive signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET, as described above.

As further shown inFIG.13, in some aspects, process1300may include decoding downlink control information in accordance with the CORESET puncturing pattern (block1320). For example, the UE (e.g., using communication manager1506, depicted inFIG.15) may decode downlink control information in accordance with the CORESET puncturing pattern, as described above.

In a first aspect, the CORESET puncturing pattern is further based, at least in part, on a resource block offset between a starting resource block of the CORESET before the CORESET puncturing process and a starting resource block of a SSB communication after the CORESET puncturing process.

In a second aspect, alone or in combination with the first aspect, the CORESET puncturing pattern includes puncturing a first number of resource blocks at a first frequency or a second number of resource blocks at a second frequency.

In a third aspect, alone or in combination with one or more of the first and second aspects, the CORESET puncturing pattern includes partial puncturing of a single CCE.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the partial puncturing of the single CCE occurs with respect to resource blocks associated with the first frequency or resource blocks associated with the second frequency.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the CORESET puncturing pattern is based, at least in part, on a REG bundle size.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process1300includes determining, based, at least in part, on signaling identifying the CORESET, a CCE-to-REG mapping associated with the CORESET puncturing pattern.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, an aggregation level is based, at least in part, on the CORESET puncturing pattern and the CCE-to-REG mapping.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the CCE-to-REG mapping is based, at least in part, on a CCE shift.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the CCE shift for the CCE-to-REG mapping is based, at least in part, on a cell identifier and a maximum number of CCEs to be punctured for an aggregation level.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the CCE shift for the CCE-to-REG mapping is based, at least in part, on a number of CCEs associated with the CORESET before puncturing and a number of CCEs to be punctured in a first frequency.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the CCE shift is based, at least in part, on a number of resource blocks associated with the CORESET after puncturing, or on a number of symbols associated with the CORESET.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the CCE shift is based, at least in part, on whether REG-bundles for the CORESET are interleaved.

FIG.14is a diagram illustrating an example process1400performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process1400is an example where the apparatus or the network node (e.g., network node110) performs operations associated with CORESET puncturing.

As shown inFIG.14, in some aspects, process1400may include outputting signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET (block1410). For example, the network node (e.g., using transmission component1604and/or communication manager1606, depicted inFIG.16) may output signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET, as described above.

As further shown inFIG.14, in some aspects, process1400may include configuring a UE to decode downlink control information in accordance with the CORESET puncturing pattern (block1420). For example, the network node (e.g., using communication manager1606, depicted inFIG.16) may configure a UE to decode downlink control information in accordance with the CORESET puncturing pattern, as described above.

In a first aspect, the CORESET puncturing pattern is further based, at least in part, on a resource block offset between a starting resource block of the CORESET before the CORESET puncturing process and a starting resource block of a SSB communication after the CORESET puncturing process.

In a second aspect, alone or in combination with the first aspect, the CORESET puncturing pattern includes puncturing a first number of resource blocks at a first frequency or a second number of resource blocks at a second frequency.

In a third aspect, alone or in combination with one or more of the first and second aspects, the CORESET puncturing pattern includes partial puncturing of a single CCE.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the partial puncturing of the single CCE occurs with respect to resource blocks associated with the first frequency or resource blocks associated with the second frequency.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the CORESET puncturing pattern is based, at least in part, on a REG bundle size.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process1400includes configuring the UE to determine, based, at least in part, on signaling identifying the CORESET, a CCE-to-REG mapping associated with the CORESET puncturing pattern.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, an aggregation level is based, at least in part, on the CORESET puncturing pattern and the CCE-to-REG mapping.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the CCE-to-REG mapping is based, at least in part, on a CCE shift.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the CCE shift for the CCE-to-REG mapping is based, at least in part, on a cell identifier and a maximum number of CCEs to be punctured for an aggregation level.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the CCE shift for the CCE-to-REG mapping is based, at least in part, on a number of CCEs associated with the CORESET before puncturing and a number of CCEs to be punctured in a first frequency.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the CCE shift is based, at least in part, on a number of resource blocks associated with the CORESET after puncturing, or on a number of symbols associated with the CORESET.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the CCE shift is based, at least in part, on whether REG-bundles for the CORESET are interleaved.

AlthoughFIG.14shows example blocks of process1400, in some aspects, process1400may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.14. Additionally, or alternatively, two or more of the blocks of process1400may be performed in parallel.

FIG.15is a diagram of an example apparatus1500for wireless communication, in accordance with the present disclosure. The apparatus1500may be a UE, or a UE may include the apparatus1500. In some aspects, the apparatus1500includes a reception component1502, a transmission component1504, and/or a communication manager1506, 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 manager1506is the communication manager140described in connection withFIG.1. As shown, the apparatus1500may communicate with another apparatus1508, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component1502and the transmission component1504.

The transmission component1504may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1508. In some aspects, one or more other components of the apparatus1500may generate communications and may provide the generated communications to the transmission component1504for transmission to the apparatus1508. In some aspects, the transmission component1504may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1508. In some aspects, the transmission component1504may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection withFIG.2. In some aspects, the transmission component1504may be co-located with the reception component1502in one or more transceivers.

The communication manager1506may support operations of the reception component1502and/or the transmission component1504. For example, the communication manager1506may receive information associated with configuring reception of communications by the reception component1502and/or transmission of communications by the transmission component1504. Additionally, or alternatively, the communication manager1506may generate and/or provide control information to the reception component1502and/or the transmission component1504to control reception and/or transmission of communications.

The communication manager1506may receive signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The communication manager1506may decode downlink control information in accordance with the CORESET puncturing pattern.

The communication manager1506may determine, based, at least in part, on signaling identifying the CORESET, a CCE-to-REG mapping associated with the CORESET puncturing pattern.

The number and arrangement of components shown inFIG.15are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.15. Furthermore, two or more components shown inFIG.15may be implemented within a single component, or a single component shown inFIG.15may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.15may perform one or more functions described as being performed by another set of components shown inFIG.15.

FIG.16is a diagram of an example apparatus1600for wireless communication, in accordance with the present disclosure. The apparatus1600may be a network node, or a network node may include the apparatus1600. In some aspects, the apparatus1600includes a reception component1602, a transmission component1604, and/or a communication manager1606, 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 manager1606is the communication manager150described in connection withFIG.1. As shown, the apparatus1600may communicate with another apparatus1608, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component1602and the transmission component1604.

The reception component1602may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus1608. The reception component1602may provide received communications to one or more other components of the apparatus1600. In some aspects, the reception component1602may 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 apparatus1600. In some aspects, the reception component1602may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node described in connection withFIG.2. In some aspects, the reception component1602and/or the transmission component1604may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus1600via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

The transmission component1604may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1608. In some aspects, one or more other components of the apparatus1600may generate communications and may provide the generated communications to the transmission component1604for transmission to the apparatus1608. In some aspects, the transmission component1604may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1608. In some aspects, the transmission component1604may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node described in connection withFIG.2. In some aspects, the transmission component1604may be co-located with the reception component1602in one or more transceivers.

The communication manager1606may support operations of the reception component1602and/or the transmission component1604. For example, the communication manager1606may receive information associated with configuring reception of communications by the reception component1602and/or transmission of communications by the transmission component1604. Additionally, or alternatively, the communication manager1606may generate and/or provide control information to the reception component1602and/or the transmission component1604to control reception and/or transmission of communications.

The transmission component1604may output signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET. The communication manager1606may configure a UE to decode downlink control information in accordance with the CORESET puncturing pattern.

The communication manager1606may configure the UE to determine, based, at least in part, on signaling identifying the CORESET, a CCE-to-REG mapping associated with the CORESET puncturing pattern.

The number and arrangement of components shown inFIG.16are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.16. Furthermore, two or more components shown inFIG.16may be implemented within a single component, or a single component shown inFIG.16may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.16may perform one or more functions described as being performed by another set of components shown inFIG.16.

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a UE, comprising: receiving signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and decoding downlink control information in accordance with the CORESET puncturing pattern.Aspect 2: The method of Aspect 1, wherein the CORESET puncturing pattern is further based, at least in part, on a resource block offset between a starting resource block of the CORESET before the CORESET puncturing process and a starting resource block of a SSB communication after the CORESET puncturing process.Aspect 3: The method of any of Aspects 1-2, wherein the CORESET puncturing pattern includes puncturing a first number of resource blocks at a first frequency or a second number of resource blocks at a second frequency.Aspect 4: The method of Aspect 3, wherein the CORESET puncturing pattern includes partial puncturing of a single CCE.Aspect 5: The method of Aspect 4, wherein the partial puncturing of the single CCE occurs with respect to resource blocks associated with the first frequency or resource blocks associated with the second frequency.Aspect 6: The method of any of Aspects 1-5, wherein the CORESET puncturing pattern is based, at least in part, on a REG bundle size.Aspect 7: The method of any of Aspects 1-6, further comprising determine, based, at least in part, on signaling identifying the CORESET, a CCE-to-REG mapping associated with the CORESET puncturing pattern.Aspect 8: The method of Aspect 7, wherein an aggregation level is based, at least in part, on the CORESET puncturing pattern and the CCE-to-REG mapping.Aspect 9: The method of Aspect 7, wherein the CCE-to-REG mapping is based, at least in part, on a CCE shift.Aspect 10: The method of Aspect 9, wherein the CCE shift for the CCE-to-REG mapping is based, at least in part, on a cell identifier and a maximum number of CCEs to be punctured for an aggregation level.Aspect 11: The method of Aspect 9, wherein the CCE shift for the CCE-to-REG mapping is based, at least in part, on a number of CCEs associated with the CORESET before puncturing and a number of CCEs to be punctured in a first frequency.Aspect 12: The method of Aspect 11, wherein the CCE shift is based, at least in part, on a number of resource blocks associated with the CORESET after puncturing, or on a number of symbols associated with the CORESET.Aspect 13: The method of Aspect 11, wherein the CCE shift is based, at least in part, on whether REG-bundles for the CORESET are interleaved.Aspect 14: The method of any of Aspects 1-14, wherein the CORESET is a CORESET0.Aspect 15: A method of wireless communication performed by a network node, comprising: outputting signaling identifying a CORESET puncturing pattern, the CORESET puncturing pattern being based, at least in part, on a number of resource blocks available before and after a CORESET puncturing process and a number of symbols of the CORESET; and configuring a UE to decode downlink control information in accordance with the CORESET puncturing pattern.Aspect 16: The method of Aspect 15, wherein the CORESET puncturing pattern is further based, at least in part, on a resource block offset between a starting resource block of the CORESET before the CORESET puncturing process and a starting resource block of a SSB communication after the CORESET puncturing process.Aspect 17: The method of any of Aspects 15-16, wherein the CORESET puncturing pattern includes puncturing a first number of resource blocks at a first frequency or a second number of resource blocks at a second frequency.Aspect 18: The method of Aspect 17, wherein the CORESET puncturing pattern includes partial puncturing of a single CCE.Aspect 19: The method of Aspect 18, wherein the partial puncturing of the single CCE occurs with respect to resource blocks associated with the first frequency or resource blocks associated with the second frequency.Aspect 20: The method of any of Aspects 15-19, wherein the CORESET puncturing pattern is based, at least in part, on a REG bundle size.Aspect 21: The method of any of Aspects 15-20, further comprising configuring the UE to determine, based, at least in part, on signaling identifying the CORESET, a CCE-to-REG mapping associated with the CORESET puncturing pattern.Aspect 22: The method of Aspect 21, wherein an aggregation level is based, at least in part, on the CORESET puncturing pattern and the CCE-to-REG mapping.Aspect 23: The method of Aspect 21, wherein the CCE-to-REG mapping is based, at least in part, on a CCE shift.Aspect 24: The method of Aspect 23, wherein the CCE shift for the CCE-to-REG mapping is based, at least in part, on a cell identifier and a maximum number of CCEs to be punctured for an aggregation level.Aspect 25: The method of Aspect 23, wherein the CCE shift for the CCE-to-REG mapping is based, at least in part, on a number of CCEs associated with the CORESET before puncturing and a number of CCEs to be punctured in a first frequency.Aspect 26: The method of Aspect 25, wherein the CCE shift is based, at least in part, on a number of resource blocks associated with the CORESET after puncturing, or on a number of symbols associated with the CORESET.Aspect 27: The method of Aspect 25, wherein the CCE shift is based, at least in part, on whether REG-bundles for the CORESET are interleaved.Aspect 28: The method of any of Aspects 15-27, wherein the CORESET is a CORESET0.Aspect 29: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-28.Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-28.Aspect 31: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-28.Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to individually or collectively perform the method of one or more of Aspects 1-28.Aspect 33: 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-28.Aspect 34: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-28.