Control resource block set search space design

Apparatuses, methods and storage media associated with components and implementations of wireless communication networks, and/or portions thereof, are disclosed herein. In embodiments, an apparatus for a next generation NodeB (gNB) may include processing circuitry to determine a number of resource element groups (REGs) to be included in a resource element group bundle (REGB) for a new radio physical downlink control channel (NR-PDCCH), and generate a signal that indicates the number of the REGs. The gNB may further include encoding circuitry, coupled with the processing circuitry, to encode the signal for transmission to a user equipment (UE). Other embodiments may be disclosed throughout.

TECHNICAL FIELD

The present disclosure relates to the field of electronic circuits. More particularly, the present disclosure relates to the components and implementations of wireless communication networks, and/or portions thereof.

BACKGROUND

In wireless communication networks, physical downlink control channel may perofrm downlink data scheduling and uplink data assignment. Each user equipment within a wireless communication network may be configured with one or more control channel search spaces, in which physical downlink control channel blind decoding candidates are defined. Inefficient configuration of the control channel search spaces may lead to increased blocking probability and/or high levels of computational complexity.

DETAILED DESCRIPTION

Apparatuses, methods and storage media associated with components and implementations of wireless communication networks, and/or portions thereof, are disclosed herein. In embodiments, an apparatus for a next generation NodeB (gNB) may include processing circuitry to determine a number of resource element groups (REGs) to be included in a resource element group bundle (REGB) for a new radio physical downlink control channel (NR-PDCCH), and generate a signal that indicates the number of the REGs. The gNB may further include encoding circuitry, coupled with the processing circuitry, to encode the signal for transmission to a user equipment (UE).

Aspects of the disclosure are disclosed in the accompanying description. Alternate embodiments of the present disclosure and their equivalents may be devised without parting from the spirit or scope of the present disclosure. It should be noted that like elements disclosed below are indicated by like reference numbers in the drawings.

As used herein, the terms “control channel element,” “blind decoding candidate,” and “new radio physical downlink control channel candidate” may be interchangeably used, wherein each of the terms may refer to a same construct.

The examples provided herein may refer to the configuration of a configured control channel resource set (CORESET). However, it is to be understood that the same approaches may be applied to search spaces and/or on a search space-by-search space basis, wherein a CORESET may include more than one search space.

The new radio physical downlink control channel (NR-PDCCH) may be utilized to schedule downlink and uplink data packets in a third generation partnership project (3GPP) fifth generation (5G) system. A resource element group (REG) that includes 12 consecutive resource elements in frequency domain of one orthogonal frequency division multiplexing (OFDM) symbol may be the basic building block of NR-PDCCH. A single antenna port (AP) based transmission for an REG may be supported. For example, all resource elements (REs) of the REG may experience the same effective channel by applying the same precoding transmission, if any. Moreover, to improve channel estimation performance, a concept called “REG bundling,” in which several adjacent REGs in a bundle may apply the same precoding operation so that channel estimates over an REG bundle (REGB) can be averaged out, may be implemented. In addition, interleaving based REGB numbering may support distributed NR-PDCCH transmission.

Certain interleaver designs based on a straightforward REGB numbering scheme (such as frequency-first numbering) may not lead to a desired distributed NR-PDCCH transmission. A more deliberate interleaver design for REGB numbering may be utilized to achieve the desired distributed NR-PDCCH transmission.

In some embodiments, a configurable REGB design may cope with different potential scenarios. Moreover, an enhanced two-dimensional (2D)/2-level interleaving based REGB numbering design may maximize the possible time-frequency diversity of distributed NR-PDCCH and avoid the undesired localized transmission caused by conventional interleaving based REGB numbering design.

A configurable REGB may enable user equipment (UE)-specific channel-aware REGB configuration. Specifically, the REGB construction, in terms of number of REGs in an REGB and bundling direction (for example, time-first order or frequency-first order), can be configured as part of search space configuration by high layer signaling. Supported REGB construction options may be defined in the specification. For example, an REGB with two or three REGs in consecutive OFDM symbols or resource blocks corresponding to bundling in time and frequency, respectively, can be supported. Then the search space (SS) configuration can indicate which particular REGB construction is to be employed by the NR-PDCCH. To realize better distributed NR-PDCCH transmission, enhanced two-dimensional interleaving based REGB numbering in the configured control channel resource set (CORESET) (which may also be referred to as “control resource resource block set”) may avoid undesired localized REGB allocation and achieve better time-frequency diversity.

Configurable REGB design may enable NR-PDCCH transmission to be optimized according to the UE-specific channel condition. Moreover, enhanced 2D-interleaver based REGB numbering in CORESET to support distributed NR-PDCCH transmission may be employed. The enhanced 2D-interleaver based REGB numbering may achieve better distributed NR-PDCCH transmission than conventional one-dimensional (1D) interleaver based REGB numbering scheme.

In the configuration of UE-specific SS of NR-PDCCH, the network may configure the way of REGB construction in terms of the number of REGs in the REGB, the bundling direction, or some combination thereof. The number of REGs in the REGB may range from 1 to N_REG_per_REGB, wherein N_REG_per_REGB may be predefined, such as being defined in the specification. The bundling direction may include time-first order or frequency-first order when multiple symbols are configured for the CORESET of the SS.

The number of REGs in the REGB and/or the bundling direction can be part of the radio resource control (RRC) signaling message for SS or CORESET (re)configuration. In some embodiments, the REGB can be defined on a CORESET or SS level so that all NR-PDCCHs in an SS share the same way of REGB construction. In other embodiments, REGB configuration can be configured on aggregation level so that NR-PDCCH of different aggregation levels (ALs) may have different ways of REGB construction. For example, for high AL NR-PDCCH, the size of an REGB can be larger than that of smaller AL NR-PDCCH so that in a low signal-to-noise ratio (SNR) situation, better channel estimation performance can be obtained from a larger REGB size.

REGBs with different sizes and bundling directions can be configurable according to a UE-specitic channel condition including channel selectivity in time, frequency at the UE receiver, and/or SNR at the UE receiver. For example, for a slow fading channel with high frequency selectivity, REGB in time may be beneficial; on the other hand, REGB in frequency may be better for a frequency-flat and fast fading channel.

FIG. 1illustrates graphical representations of example control channel resource set (CORESET) configurations, according to various embodiments. In particular,FIG. 1illustrates a graphical representation of a two-REG configured REGB CORESET configuration3800, a three-REG configured REGB CORESET configuration3830, and a one-REG configured REGB CORESET configuration3870. The CORESET configuration3800, the CORESET configuration3830, and the CORESET configuration3870may each be implemented via a 2D/Enhanced 2D/2-level interleaver-based REGB number for distributed NR-PDCCH. The illustrated embodiments of the CORESET3800, the CORESET3830, and the CORESET3870may be configurations for user equipment of aggregation level1(AL1). User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The CORESET configuration3800may be configured with REGBs having two REGs per REGB. In particular, an REGB may be represented inFIG. 1by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB3802may include first REG3804and second REG3806, which are both numbered ‘1’ in the illustrated embodiment.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of control channel elements (CCEs) in the CORESET configuration3800, wherein the numbering may define the CCE index for each REG. The CCEs may also be referred to as blind decoding (BD) candidates and/or NR-PDCCH candidates. The REGs may be numbered in a frequency-first order (which may also be referred to as a “frequency increase order”) or in a time-first order. The CORESET configuration3800is illustrated with eight CCEs and with the REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG3804and continue to the next REG in the frequency domain, which is the second REG3806.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET3800and the number of REGs to be included in the REGB are labeled with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the numbering may start at the first REG3804and proceed to the second REG3806in the frequency-first order, numbering the first REG3804and the second REG3806with ‘1’. The numbering may then increment and proceed to a third REG3808and a fourth REG3810, numbering the third REG3808and the fourth REG3810with ‘2’, thereby generating a second REGB3812. The numbering may continue to generation of an eighth REGB3814that includes a fifth REG3816and a sixth REG3818, which are both numbered ‘8’. The number of CCEs in the CORESET3800is eight in the illustrated embodiment, which may cause the numbering to cycle back to ‘1’ after numbering of the eighth REGB3814. Accordingly, a seventh REG3822and an eighth REG3824, which are included in a ninth REGB3820, may be numbered with ‘1’. The numbering may continue as described until all the REGs in the CORESET of the CORESET configuration3800have been numbered.

The CORESET configuration3830may be configured with REGBs having three REGs per REGB. In particular, an REGB may be represented inFIG. 1by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB3832may include first REG3834, second REG3836, and third REG3838, which are all numbered ‘1’ in the illustrated embodiment.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration3830, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET configuration3830is illustrated with eight CCEs and with the REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG3834and continue to the next REG in the frequency domain, which is the second REG3836.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET3830and the number of REGs to be included in the REGB are numbered with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the numbering may start at the first REG3834, proceed to the second REG3836, then to the third REG3838in the frequency-first order, numbering the first REG3834, the second REG3836, and the third REG3838with ‘1’. The numbering may then increment and proceed to a fourth REG3840, a fifth REG3842, and a sixth REG3844, numbering the fourth REG3840, the fifth REG3842, and the sixth REG3844with ‘2’, thereby generating a second REGB3846. The numbering may continue to generation of an eighth REGB3848that includes a seventh REG3850, an eighth REG3852, and a ninth REG3854, which are all numbered ‘8’. The number of CCEs in the CORESET configuration3830is eight in the illustrated embodiment, which may cause the numbering to cycle back to ‘1’ after numbering of the eighth REGB3848. Accordingly, a tenth REG3856, an eleventh REG3858, and a twelfth REG3860, which are included in a ninth REGB3862, may be numbered with ‘1’.

The CORESET configuration3870may be configured with REGBs having one REG per REGB. In particular, an REGB may be represented inFIG. 1by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB3872may include first REG3874, which is numbered ‘1’ in the illustrated embodiment. Embodiments having one REG per REGB may also be referred to as “REG based” embodiments or “unbundled embodiments” since each REGB includes only a signal REG.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration3870, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET3870is illustrated with eight CCEs and with the REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG3874and continue to the next REG in the frequency domain, which is a second REG3876.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of RECis to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET configuration3870and the number of REGs to be included in the REGB are numbered with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the numbering may start at the first REG3874, numbering the first REG3874with ‘1’. The numbering may then increment and proceed to the second REG3876, numbering the second REG3876with ‘2’, thereby generating a second REGB3878. The numbering may continue to generation of an eighth REGB3880that includes a third REG3882, which is numbered ‘8’. The number of CCEs in the CORESET configuration3870is eight in the illustrated embodiment, which may cause the numbering to cycle back to ‘1’ after numbering of the eighth REGB3880. Accordingly, a fourth REG3884, which is included in a ninth REGB3886, may be numbered with ‘1’.

The CORESET configuration3800, the CORESET configuration3830, and the CORESET configuration3870all include a single OFDM symbol. In these embodiments, non-shifted REGB numbering can ensure a good REGB distribution over the CORESET. In particular, the CORESET configuration3800, the CORESET configuration3830, and the CORESET configuration3870may have same numbered REGs distributed at multiple, non-contiguous frequencies, which may lead to a distributed NR-PDCCH. However, non-shifted REGB numbering may not ensure distributed transmission in CORESET configurations having multiple OFDM symbols.

FIG. 2illustrates a graphical representation of another CORESET configuration200, according to various embodiments. The CORESET configuration200may include two OFDM symbols (as illustrated by the two columns, wherein each column represents an OFDM symbol). The CORESET configuration200may be configured with REGBs having two REGs per REGB. In particular, an REGB may be represented inFIG. 2by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB202may include first REG204and second REG206, which are both numbered ‘1’ in the illustrated embodiment. The illustrated embodiment of the CORESET configuration200may be for user equipment of AL1. User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration200, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET configuration200is illustrated with eight CCEs and with REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG204and continue to the next REG in the frequency domain, which is the second REG206.

The bundling direction of the REGBs within the CORESET configuration200may be in a frequency-first order or a time-first order. The bundling direction may be the same direction as the REG numbering or a different direction than the REG numbering. The bundling direction may refer to a direction in which a subsequent REGB is numbered after completion of numbering of a current REGB. For example, after the first REG204and the second REG206, of the first REGB202, have been numbered ‘1’ in the frequency-first order, numbering of the REGs may progress in time-first order (which is the bundling direction of the CORESET configuration200) and number a third REG208, followed by a fourth REG210with ‘2’ in the frequency-first order to generate a second REGB212.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET configuration200and the number of REGs to be included in the REGB are numbered with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the numbering may start at the first REG204and proceed to the second REG206in the frequency-first order, numbering the first REG204and the second REG206with ‘1’. The numbering may then increment and proceed, in the time-first order, to a third REG208and then, in a frequency-first order to a fourth REG210, numbering the third REG208and the fourth REG210with ‘2’, thereby generating a second REGB212. After numbering the third REG208and the fourth REG210with ‘2’, the numbering may increment and may attempt to proceed in the time-first order. However, as the CORESET does not include any more REGs in the time-first order from the second REGB212, the numbering may wrap around to the next available REGs in the first OFDM symbol214, which may be a fifth REG216. The numbering may then continue in the frequency-first order, numbering the fifth REG216and the sixth REG218with ‘3’ and generating a third REGB220. The numbering may continue to generation of an eighth REGB222that includes a seventh REG224and an eighth REG226, which are both numbered ‘8’. The number of CCEs in the CORESET configuration200is eight in the illustrated embodiment, which may cause the numbering to cycle back to ‘1’ after numbering of the eighth REGB222. Accordingly, a ninth KEG228and a tenth REG230, which are included in a ninth REGB232, may be numbered with ‘1’. The numbering may continue as described until all the REGs in the CORESET have been numbered.

As may be noticed from CORESET200, any NR-PDCCH candidate of AL1is only transmitted within one of the OFDM symbols. For example, REGs numbered ‘1’ comprise an NR-PDCCH candidate within the CORESET configuration200. All the REGs of CORESET numbered ‘1’ are located within the first OFDM symbol214. Accordingly, the NR-PDCCH candidates of AL1may not benefit from the possible time diversity available by utilizing different OFDM symbols.

FIG. 3illustrates a graphical representation of another example CORESET configuration300, according to various embodiments. The CORESET may include two OFDM symbols (as illustrated by the two columns, wherein each column represents an OFDM symbol). The CORESET configuration300may be configured with REGBs having two REGs per REGB. In particular, an REGB may be represented inFIG. 3by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB302may include first REG304and second REG306, which are both numbered ‘1’ in the illustrated embodiment. The illustrated embodiment of the CORESET configuration300may be for user equipment of AL1. User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration300, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET300is illustrated with eight CCEs and with REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG304and continue to the next REG in the frequency domain, which is the second REG306.

The bundling direction of the REGBs within the CORESET configuration300may be in a frequency-first order or a time-first order. The bundling direction may be the same direction as the REG numbering or a different direction than the REG numbering. The bundling direction may refer to a direction in which a subsequent REGB is numbered after completion of numbering of a current REGB. For example, after the first REG304and the second REG306, of the first REGB302, have been numbered ‘1’ in the frequency-first order, numbering of the REGs may progress in time-first order (which is the bundling direction of the CORESET configuration300) and number a third REG308, followed by a fourth REG310with ‘2’ in the frequency-first order to generate a second REGB312.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET configuration300and the number of REGs to be included in the REGB are numbered with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the configuration of the CORESET configuration300may include a time-first order cyclic shift applied when the numbering cycles back to ‘1’. In the illustrated embodiment, after numbering of a fifth REG314and a sixth REG316, both included in an eighth REGB318, with ‘8’, a cyclic shift may be applied in the time-first order, which may cause the numbering order to be cyclically shifted in the time-first order. Accordingly, the numbering may proceed to a seventh REG320and an eighth REG322, both included in a ninth REGB324, located within a second OFDM symbol326. After generating the ninth REGB324, the numbering may proceed in the time-first order to a ninth REG327and a tenth REG328, both included in a tenth REGB330, within a first OFDM symbol332. The CORESET configuration300may continue to apply a time-first order cyclic shift each time the numbering cycles back to ‘1’ throughout the CORESET300. In other embodiments, the cyclic shift may be applied in a frequency-first order.

As may be noticed from CORESET300, any NR-PDCCII candidate of AL1may be transmitted within more than one OFDM symbol. In particular, each NR-PDCCH candidate of AL1may be transmitted within two OFDM symbols. For example, REGs numbered ‘1’ comprise an NR-PDCCH candidate within the CORESET300. The first REG304and the second REG306numbered ‘1’ are located within a first OFDM symbol332, whereas the seventh REG320and the eighth REG322numbered ‘1’ are located within the second OFDM symbol326. Accordingly, the CORESET300may employ an enhanced 2D/2-level of REGB numbering, which may be performed to enhance the time diversity of each NR-PDCCH candidate of AL1.

FIG. 4illustrates a graphical representation of another example CORESET configuration400, according to various embodiments. The CORESET may include two OFDM symbols (as illustrated by the two columns, wherein each column represents an OFDM symbol). The CORESET configuration400may be configured with REGBs having three REGs per REGB. In particular, an REGB may be represented inFIG. 4by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB402may include first REG404, second REG406, and third REG408, which are all numbered ‘1’ in the illustrated embodiment. The illustrated embodiment of the CORESET configuration400may be utilized for user equipment of AL1. User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration400, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET configuration400is illustrated with eight CCEs and with REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG404and continue to the next REG in the frequency domain, which is the second REG406.

The bundling direction of the REGBs within the CORESET configuration400may be in a frequency-first order or a time-first order. The bundling direction may be the same direction as the REG numbering or a different direction than the REG numbering. The bundling direction may refer to a direction in which a subsequent REGB is numbered after completion of numbering of a current REGB. For example, after the first REG404, the second REG406, and the third REG408, of the first REGB402, have been numbered ‘1’ in the frequency-first order, numbering of the REGs may progress in time-first order (which is the bundling direction of the CORESET configuration400) and number a fourth REG410, followed by a fifth REG412and a sixth REG414with ‘2’ in the frequency-first order to generate a second REGB416.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET configuration400and the number of REGs to be included in the REGB are numbered with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the numbering may start at the first REG404and and proceed to the second REG406and the third REG408in the frequency-first order, numbering the first REG404, the second REG406, and the third REG408with ‘1’. The numbering may then increment and proceed, in the time-first order, to a fourth REG410and then, in a frequency-first order to a fifth REG412and a sixth REG414, numbering the fourth REG410, the fifth REG412, and the sixth REG414with ‘2’, thereby generating a second REGB416. After numbering the fourth REG410, the fifth REG412, and the sixth REG414with ‘2’, the numbering may increment and may attempt to proceed in the time-first order. However, as the CORESET does not include any more REGs in the time-first order from the second REGB416, the numbering may wrap around to the next available REGs in the first OFDM symbol418, which may be a seventh REG420. The numbering may then continue in the frequency-first order, numbering the seventh REG420, an eighth REG422, and a ninth REG424with ‘3’ and generating a third REGB426. The numbering may continue to generation of an eighth REGB428that includes a tenth REG430, an eleventh REG432, and a twelfth REG434, which are all numbered ‘8’. The number of CCEs in the CORESET configuration400is eight in the illustrated embodiment, which may cause the numbering to cycle back to ‘1’ after numbering of the eighth REGB428. Accordingly, a thirteenth REG436, a fourteenth REG438, and a fifteenth REG440, which are included in a ninth REGB442, may be numbered with ‘1’. The numbering may continue as described until all the REGs in the CORESET have been numbered.

As may be noticed from CORESET configuration400, any NR-PDCCH candidate of AL1is only transmitted within one of the OFDM symbols. For example, REGs numbered ‘1’ comprise an NR-PDCCH candidate within the CORESET400. All the REGs of CORESET400numbered ‘1’ are located within the first OFDM symbol418. Accordingly, the NR-PDCCH candidates of AL1may not benefit from the possible time diversity available by utilizing different OFDM symbols.

FIG. 5illustrates a graphical representation of another example CORESET configuration500, according to various embodiments. The CORESET may include two OFDM symbols (as illustrated by the two columns, wherein each column represents an OFDM symbol). The CORESET configuration500may be configured with REGBs having three REGs per REGB. In particular, an REGB may be represented inFIG. 5by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB502may include first REG504, second REG506, and third REG508, which are all numbered ‘1’ in the illustrated embodiment. The illustrated embodiment of the CORESET configuration500may be for user equipment of AL1. User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration500, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET configuration500is illustrated with eight CCEs and with REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG504and continue to the next REG in the frequency domain, which is the second REG506.

The bundling direction of the REGBs within the CORESET configuration500may be in a frequency-first order or a time-first order. The bundling direction may be the same direction as the REG numbering or a different direction than the REG numbering. The bundling direction may refer to a direction in which a subsequent REGB is numbered after completion of numbering of a current REGB. For example, after the first REG504, the second REG506, and the third REG508, of the first REGB502, have been numbered ‘1’ in the frequency-first order, numbering of the REGs may progress in time-first order (which is the bundling direction of the CORESET500) and number a fourth REG510, followed by a fifth REG512and sixth REG514with ‘2’ in the frequency-first order to generate a second REGB516.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET500and the number of REGs to be included in the REGB are numbered with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the CORESET configuration500may include a time-first order cyclic shift applied when the numbering cycles back to ‘1’. In the illustrated embodiment, after numbering of a seventh REG518, an eighth REG520, and a ninth REG522, all included in an eighth REGB524, with ‘8’, a cyclic shift may be applied in the time-first order, which may cause the numbering order to be cyclically shifted in the time-first order. Accordingly, the numbering may proceed to a tenth REG526, an eleventh REG528, and a twelfth REG530, all included in a ninth REGB532located within a second OFDM symbol534. After generating the ninth REGB532, the numbering may proceed in the time-first order to a thirteenth REG536, a fourteenth REG538, and a fifteenth REG540, all included in a tenth REGB542, within a first OFDM symbol544. The configuration of the CORESET500may continue to apply a time-first order cyclic shift each time the numbering cycles back to ‘1’ throughout the CORESET500. In other embodiments, the cyclic shift may be applied in a frequency-first order.

As may be noticed from CORESET configuration500, any NR-PDCCH candidate of AL1may be transmitted within more than one OFDM symbol. In particular, each NR-PDCCH candidate of AL1may be transmitted within two OFDM symbols. For example, REGs numbered ‘1’ comprise an NR-PDCCH candidate within the CORESET configuration500. The first REG504, the second REG506, and the third REG508numbered ‘1’ are located within the first OFDM symbol544, whereas the tenth REG526, the eleventh REG528, the twelfth REG530numbered ‘1’ are located within the second OFDM symbol534. Accordingly, the CORESET configuration500may employ an enhanced 2D/2-level of REGB numbering, which may be performed to enhance the time diversity of each NR-PDCCH candidate of AL1.

FIG. 6illustrates a graphical representation of another example CORESET configuration600, according to various embodiments. The CORESET may include two OFDM symbols (as illustrated by the two columns, wherein each column represents an OFDM symbol). The CORESET configuration600may be configured with REGBs having three REGs per REGB. In particular, an REGB may be represented inFIG. 6by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB602may include first REG604, second REG606, and third REG608, which are all numbered ‘1’ in the illustrated embodiment. The illustrated embodiment of the CORESET configuration600may be for user equipment of AL1. User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration600, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET configuration600is illustrated with eight CCEs and with REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG604and continue to the next REG in the frequency domain, which is the second REG606.

The bundling direction of the REGBs within the CORESET configuration600may be in a frequency-first order or a time-first order. The bundling direction may be the same direction as the REG numbering or a different direction than the REG numbering. The bundling direction may refer to a direction in which a subsequent REGB is numbered after completion of numbering of a current REGB. For example, after the first REG604, the second REG606, and the third REG608, of the first REGB602, have been numbered ‘1’ in the frequency-first order, numbering of the REGs may progress in frequency-first order (which is the bundling direction of the CORESET configuration600) and number a fourth REG610, followed by a fifth REG612and a sixth REG614with ‘2’ in the frequency-first order to generate a second REGB616.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET configuration600and the number of REGs to be included in the REGB are labeled with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the numbering may start at the first REG604and proceed to the second REG606and the third REG608in the frequency-first order, numbering the first REG604, the second REG606, and the third REG608with ‘1’. The numbering may then increment and proceed, in the frequency-first order, to a fourth REG610and then, in a frequency-first order to a fifth REG612and a sixth REG614, numbering the fourth REG610, the fifth REG612, and the sixth REG614with ‘2’, thereby generating a second REGB616. After numbering the fourth REG610, the fifth REG612, and the sixth REG614with ‘2’, the numbering may increment and may proceed in the frequency-first order.

The numbering may continue to generation of an eighth REGB618that includes a seventh REG620, an eighth REG622, and a ninth REG624, which are all numbered ‘8’. The number of CCEs in the CORESET configuration600is eight in the illustrated embodiment, which may cause the numbering to cycle back to ‘1’ after numbering of the eighth REGB618. Further, after numbering the seventh REG620, the eighth REG622, and the ninth KEG624with ‘8’, the numbering may attempt to proceed in the frequency-first order. However, as the CORESET600does not include any more REGs in the frequency-first order from the eighth REGB618, the numbering may wrap around to the next available REGs in the next OFDM symbol (in this case, second OFDM symbol626), which may be a tenth REG628. The numbering may then continue in the frequency-first order, numbering the tenth REG628, an eleventh REG630, and a twelfth REG632with ‘1’ and generating a ninth REGB634. The numbering may continue as described until all the REGs in the CORESET have been numbered.

As may be noticed from CORESET configuration600, any NR-PDCCH candidate of AL1is only transmitted within three frequencies. For example, REGs numbered ‘1’ comprise an NR-PDCCH candidate within the CORESET configuration600. All the REGs of CORESET configuration600numbered ‘1’ are located within a first frequency position636, a second frequency position638, or a third frequency position640. This resultant arrangement of NR-PDCCH candidates of AL1may be an unwanted localized transmission arrangement, whereas a distributed transmission arrangement may be preferred.

FIG. 7illustrates a graphical representation of another example CORESET configuration700, according to various embodiments. The CORESET may include two OFDM symbols (as illustrated by the two columns, wherein each column represents an OFDM symbol). The CORESET configuration700may be configured with REGBs having three REGs per REGB. In particular, an REGB may be represented inFIG. 7by consecutive REGs (represented by squares in the graphical representation) that have been assigned the same number. For example, a first REGB702may include first REG704, second REG706, and third REG708, which are all numbered ‘1’ in the illustrated embodiment. The illustrated embodiment of the CORESET configuration700may be for user equipment of AL1. User equipment of higher aggregation levels may aggregate the REGBs, as is described further throughout this disclosure.

The REGs within the CORESET may be cyclically numbered from ‘1’ to a number of CCEs in the CORESET configuration700, wherein the numbering may define the CCE index for each REG. The REGs may be numbered in a frequency-first order or in a time-first order. The CORESET configuration700is illustrated with eight CCEs and with REGs numbered in frequency-first order. In particular, the numbering may begin at the first REG704and continue to the next REG in the frequency domain, which is the second REG706.

The bundling direction of the REGBs within the CORESET configuration700may be in a frequency-first order or a time-first order. The bundling direction may be the same direction as the REG numbering or a different direction than the REG numbering. The bundling direction may refer to a direction in which a subsequent REGB is numbered after completion of numbering of a current REGB. For example, after the first REG704, the second REG706, and the third REG708, of the first REGB702, have been numbered ‘1’ in the frequency-first order, numbering of the REGs may progress in frequency-first order (which is the bundling direction of the CORESET configuration700) and number a fourth REG710, followed by a fifth REG712and sixth REG714with ‘2’ in the frequency-first order to generate a second REGB716.

The numbering may begin at ‘1’ and may remain at ‘1’ until the number of REGs to be included in an REGB are assigned that number, at which point the number may be incremented. Once the numbering reaches the number of CCEs in the CORESET configuration700and the number of REGs to be included in the REGB are labeled with the number equal to the number of CCEs, the numbering may cycle back to ‘1’ for numbering the next REG in the CORESET.

In the illustrated embodiment, the CORESET configuration700may include a frequency-first order cyclic shift applied when the numbering cycles back to ‘1’. In particular, the frequency-first order cyclic shift may shift by half of the number of REGs in the frequency domain in the illustrated embodiment, although the shift amount may be different in other embodiments. In the illustrated embodiment, after numbering of a seventh REG718, an eighth REG720, and a ninth REG722, all included in an eighth REGB724, with ‘8’, a cyclic shift may be applied in the time-first order, which may cause the numbering order to be cyclically shifted in the time-first order. Accordingly, the numbering may proceed to a tenth REG726, an eleventh REG728, and a twelfth REG730, all included in a ninth REGB732located within a second OFDM symbol734. After generating the ninth REGB732, the numbering may proceed in the frequency-first order to a thirteenth REG736, a fourteenth REG738, and a fifteenth REG740, all included in a tenth REGB742, within the second OFDM symbol734. The CORESET configuration700may continue to apply a frequency-first order cyclic shift each time the numbering cycles back to ‘1’ throughout the CORESET. In other embodiments, the cyclic shift may be applied in a time-first order.

As may be noticed from CORESET configuration700, each NR-PDCCH candidate of AL1may be transmitted at different frequency locations within a first OFDM symbol744. In particular, each NR-PDCCH candidate of AL1may be transmitted within two OFDM symbols. For example, REGs numbered ‘1’ comprise an NR-PDCCH candidate within the CORESET configuration700. The first REG704, the second REG706, and the third REG708numbered ‘1’ are located within a first frequency position746, a second frequency position748, and a third frequency position750, respectively. Whereas the tenth REG726, the eleventh REG728, the twelfth REG730numbered ‘1’ are located within the a fourth frequency position752, a fifth frequency position754, and a sixth frequency position756, respectively. Accordingly, the CORESET configuration700may employ enhanced 2D/2-level interleaver based REGB numbering, which may address the unwanted localized transmission arrangement presented inFIG. 6. In particular, applying the cyclically shifted REGB numbering, illustrated inFIG. 7, in the second OFDM symbol734, or the second REGB counting cycle, may convert the localized NR-PDCCH candidate transmission of AL1illustrated inFIG. 6to the distributed NR-PDCCH candidate transmission of AL1in both time and frequency domains in the CORESET.

Based onFIGS. 2-7, it may be observed that enhanced 2D/2-level of interleaver based REGB numbering may improve the time and frequency diversity of distributed NR-PDCCH.

FIG. 8illustrates an example procedure800of resource element group bundle numbering, according to various embodiments. In particular, the procedure800may be utilized for enhanced 2D/2-level interleaver based REGB numbering. The procedure800may be performed by a next generation NodeB (gNB), with signaling between the gNB and a UE to coordinate NR-PDCCH transmissions between the gNB and the UE. In other embodiments, the procedure800may be performed by a UE, with signaling between the UE and a gNB to coordinate NR-PDCCH transmissions between the gNB and the UE. In some embodiments, the signaling may be high layer signaling and/or RRC signaling.

In stage802, REGs may be numbered within REGBs according to a certain defined/configured order, as described throughout this disclosure. In particular, numbering of the REGs may begin at an initial REG within the CORESET, may proceed with REG numbering in a time-first order or a frequency-first order, and may proceed with bundling direction in a time-first order or a frequency-first order. The direction of the REG numbering and/or the bundling direction may be defined in the specification, signaled in a configuration message from a next generation NodeB to a UE, or some combination thereof. Stage802may include REG numbering of a first level of REGBs, wherein the first level may include numbering from the initial REG to a last REG at which the REG numbering cycles back to ‘1’ the first time. It is to be understood that the second level of REGB may include numbering from the REG following the first level to the second time the REG number cycles back to ‘1’, and so on.

In stage804, a cyclic shift of each REGB numbering cycle may be determined. AN REGB numbering cycle may refer to a level of the REG numbering. For example, a first REGB numbering cycle may refer to the numbering of the first level of REGBs.

The cyclic shift of each REGB numbering cycle may be determined to maximize the time diversity and/or the frequency diversity for each CCE. For example, the cyclic shift may be determined such that a total number of REGBs of a particular NR-PDCCH may be evenly distributed in both time domain and frequency. In cases where a number of OFDM symbols in a CORESET is greater than a number of REGBs of an NR-PDCCH, a subset of OFDM symbols of the CORESET may be chosen for REGBs of the NR-PDCCH. In some embodiments, a cyclic shift of the REGB number cycles may not be required for all of the REGB numbering cycles to achieve maximum time-frequency diversity of the NR-PDCCH. Further, in some embodiments (including some of the embodiments where the cyclic shift of the REGB number cycles may not be required for all REGB numbering cycles), a first level of REGB numbering may be enough. The cyclic shift of each REGB numbering cycle may be determined prior to numbering any of the REGs, at the conclusion of the numbering of each of the numbering cycles, or some combination thereof.

In stage806, the cyclic shift may be performed for each REGB numbering cycle. In particular, upon completion of an REGB numbering cycle, the cyclic shift corresponding to the next REGB numbering cycle may be performed. The numbering for the next REGB numbering cycle may be performed after the cyclic shift has been performed. In particular, numbering in a certain defined/configured order may be performed for the next REGB numbering cycle. Stage802, stage804, and stage806may be repeated for each REGB numbering cycle of a CORESET.

Further, in long term evolution (LTE), physical downlink control channel (PDCCH) may perform downlink data scheduling and uplink data assignment. Each UE may be configured with one or more control channel SS, where a number of PDCCH blind decoding (BD) candidates within the SS may be defined. To support link adaptation, several ALs of CCE targeting at different link quality or coverage may be employed for the control channel. For example, LTE PDCCH may support AL1,2,4and8, and a PDCCH at AL×INCLUDES×CCEs, accordingly. A control channel SS may include multiple BD candidates at every supported AL. For instance, in LTE, a UE-specific SS may include 6 AL1BD candidates, 6 aggregation level2(AL2) BD candidates, 2 aggregation level4(AL4) candidates and 2 aggregation level8(AL8) candidates. The number of BD candidates may be chosen to achieve good trade-off between desired control channel blocking probability and UE BD computation complexity. The UE in the cell may monitor the configured SSes in every transmit time interval (TTI) by performing blind decoding attempts. Once a transmitted PDCCH is correctly decoded by a UE, the UE may further demodulate the scheduled downlink data channel or transmit the assigned uplink data. These fundamental functions of PDCCH may be adopted in 5G new radio (NR) as well. However, due to the minimization of “always-on” signal, i.e., absence of cell-specific reference signal (CRS) in NR, unlike LTE PDCCH which makes use of CRS for channel estimation and coherence demodulation, the NR-PDCCH may employ UE-specific demodulation reference signal (DMRS). Moreover, each NR UE may be configured with one or more control resource sets that include a number of resource blocks (RB), on which the NR-PDCCTI SS may be defined.

Embodiments herein may relate to various approaches to design the NR-PDCCH SS to optimize different performance criteria/targets. The described approaches may aim to provide good trade-off among provisioned NR-PDCCH link budget coverage, UE blind decoding complexity and resulted blocking probability of multiple UEs served by same gNB.

Embodiments herein may relate to one or more of three categories of SS design, namely localized NR-PDCCH SS (LSS), distributed NR-PDCCH SS (DSS), and hierarchical NR-PDCCH SS (HSS). In LSS, each localized NR-PDCCH BD candidate within a configured CORESET may be transmitted in a frequency localized manner. Further, each localized NR-PDCCH BD candidate may include consecutive REGs, which may be numbered in a time-first order. A gNB may schedule the localized NR-PDCCH to benefit from potential frequency selective scheduling gain, better beamforming gain, possible enhanced channel estimation with less DMRS overhead, or some combination thereof.

In DSS, each distributed NR-PDCCH BD candidate within a configured CORESET may be transmitted in a distributed manner in both the time domain and the frequency domain. Further, each distributed NR-PDCCH BD candidate may include REGS which are evenly distributed in both time and frequency domain to maximize the achievable time-frequency diversity. A gNB may configure the distributed NR-PDCCH to benefit from the maximum available time-frequency diversity, provided that the gNB is not able to perform more advanced scheduling due to a lack of accurate channel state information (CSI) knowledge.

In HSS, the NR-PDCCH within a CORESET at the lowest aggregation level (which may be AL1) may be formed by a localized NR-PDCCH or a distributed NR-PDCCH. The NR-PDCCH of higher ALs may include several NR-PDCCHs of lower ALs. such that the demodulated REs for NR-PDCCH BD candidates of lower ALs can be reused for BD candidate of higher ALs.

The HSS may include one or more hierarchical SS structures. The hierarchical SS structures may define characteristics of the SS and/or CORESET to which the hierarchical SS structures are to be applied. The characteristics may include whether the AL1BD candidates are to be bundled, a bundling direction (either time-first order or frequency-first order), whether the AL1BD candidates are to be REG based localized NR-PDCCH or REG based distributed NR-PDCCH, a numbering direction of the AL1BD candidates, an aggregation direction (either in the time domain or in the frequency domain) of the BD candidates in higher ALs, or some combination thereof.

In some embodiments, the HSS may include 12 hierarchical structures. A first hierarchical SS structure (H1) may include AL1BD candidates that are REG based localized NR-PDCCH. The AL1BD candidates of HI may be numbered in a time-first order. Further, the BD candidates of higher ALs of HI may aggregate the BD candidates of lower ALs in the time domain.

A second hierarchical SS structure (H2) may include AL1BD candidates that are REG based distributed NR-PDCCH. The AL1BD candidates of H2may be numbered in a time-first order. Further, the BD candidates of higher ALs of H2may aggregate the BD candidates of lower ALs in the time domain.

A third hierarchical SS structure (H3) may include REGBs that have a bundling direction of time-first order. The REGBs may include two or more consecutive REGs in the time domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H3may include REGBs based localized NR-PDCCH. The AL1BD candidates of H3may be numbered in a time-first order. Further, the BD candidates of higher ALs of H3may aggregate the BD candidates of lower ALs in the time domain.

A fourth hierarchical SS structure (H4) may include REGBs that have a bundling direction of time-first order. The REGBs may include two or more consecutive REGs in the time domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H4may include REGBs based distributed NR-PDCCH. The AL1BD candidates of H4may be numbered in a time-first order. Further, the BD candidates of higher ALs of H4may aggregate the BD candidates of lower ALs in the time domain.

A fifth hierarchical SS structure (H5) may include REGBs that have a bundling direction of frequency-first order. The REGBs may include two or more consecutive REGs in the frequency domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H5may include REGBs based localized NR-PDCCH. The AL1BD candidates of H5may be numbered in a time-first order. Further, the BD candidates of higher ALs of H5may aggregate the BD candidates of lower ALs in the time domain.

A sixth hierarchical SS structure (H6) may include REGBs that have a bundling direction of frequency-first order. The REGBs may include two or more consecutive REGs in the frequency domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H6may include REGBs based distributed NR-PDCCH. The AL1BD candidates of H6may be numbered in a time-first order. Further, the BD candidates of higher ALs of H6may aggregate the BD candidates of lower ALs in the time domain.

A seventh hierarchical SS structure (H7) may include AL1BD candidates that are REG based localized NR-PDCCH. The AL1BD candidates of H7may be numbered in a frequency-first order. Further, the BD candidates of higher ALs of H7may aggregate the BD candidates of lower ALs in the frequency domain.

An eighth hierarchical SS structure (H8) may include AL1BD candidates that are REG based distributed NR-PDCCH. The AL1BD candidates of H8may be numbered in a frequency-first order. Further, the BD candidates of higher ALs of H8may aggregate the BD candidates of lower ALs in the frequency domain.

A ninth hierarchical SS structure (H9) may include REGBs that have a bundling direction of time-first order. The REGBs may include two or more consecutive REGs in the time domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H9may include REGBs based localized NR-PDCCH. The AL1BD candidates of H9may be numbered in a frequency-first order. Further, the BD candidates of higher ALs of H9may aggregate the BD candidates of lower ALs in the frequency domain.

A tenth hierarchical SS structure (H10) may include REGBs that have a bundling direction of time-first order. The REGBs may include two or more consecutive REGs in the time domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H10may include REGBs based distributed NR-PDCCH. The AL1BD candidates of H10may be numbered in a frequency-first order. Further, the BD candidates of higher ALs of H10may aggregate the BD candidates of lower ALs in the frequency domain.

An eleventh hierarchical SS structure (H11) may include REGBs that have a bundling direction of frequency-first order. The REGBs may include two or more consecutive REGs in the frequency domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H11may include REGBs based localized NR-PDCCH. The AL1BD candidates of H11may be numbered in a frequency-first order. Further, the BD candidates of higher ALs of H11may aggregate the BD candidates of lower ALs in the frequency domain.

A twelfth hierarchical SS structure (H12) may include REGBs that have a bundling direction of frequency-first order. The REGBs may include two or more consecutive REGs in the frequency domain. In some embodiments, the number of REGs in the REGBs may be defined by RRC signaling, as described above. The AL1BD candidates of H12may include REGBs based distributed NR-PDCCH. The AL1BD candidates of H12may be numbered in a frequency-first order. Further, the BD candidates of higher ALs of H12may aggregate the BD candidates of lower ALs in the frequency domain.

FIG. 9illustrates a tree diagram900for the example hierarchical SS structures H1-H12, according to various embodiments. In particular, the segmentation tree900may include branches that include characteristics corresponding to the hierarchical SS structures, wherein the hierarchical SS structures are indicated as leaves at the right side of the tree diagram900.

As an example, H1may be represented at a first leaf902on a first root904of the tree diagram900. The route from the first root904to the first leaf902may traverse a first branch906. The first root904may include the characteristic of the BD candidates of the higher ALs aggregating the BD candidates of the lower ALs in the time domain, The first branch906may include the characteristic of the AL1BD candidates being single REGs. The first leaf902may include the characteristic of the AL1BD candidates being REG based localized NR-PDCCH. H1may include all the characteristics of the first root904, the first branch906, and the first leaf902.

As another example, H12may be represented at a second leaf908on a second root910of the tree diagram900. The route from the second root910to the second leaf908may traverse a second branch912and a third branch914. The second root910may include the characteristic of the BD candidates of the higher ALs aggregating the BD candidates of the lower ALs in the frequency domain. The second branch912may include the characteristic of the AL1BD candidates being REGBs. The third branch914may include the characteristic of the REGs within each REGB having a bundling direction of frequency-first order. The second leaf908may include the characteristic of the AL1BD candidates being REG based distributed NR-PDCCH. H12may include all the characteristics of the second root910, the second branch912, the third branch914, and the second leaf908.

The LSS may achieve the best frequency selective scheduling gain and beamforming gain if required CSI feedback is available at gNB, so that the best control channel spectrum efficiency may be potentially achieved. The DSS may achieve the maximum time-frequency diversity for the control channel when no CSI feedback is available at gNB.

The HSS, via the hierarchical SS structures H1-H12, may provide different advantages according to different design targets, channel conditions and CSI knowledge. For example, the hierarchical SS structures based on aggregation of AL1candidates in time domain (which include H1-H6) may be suitable to UEs with less time-varying channels, so that front-loaded DMRS can be shared by different REGs in the same RB. On the other hand, the hierarchical SS structures based on aggregation of AL1candidates in frequency domain (which include H7-H12) may be more feasible to UEs with less frequency-selective channels, so that REGs in consecutive RBs may apply same precoding and better channel estimation performance may be achieved. Similar reasoning may also be valid to a different way of creating a cluster of REGs, i.e., in time domain (which include H3, H4, H9and H10) and frequency domain (which include H5, H6, H11and H12).

The following description may refer to multiple symbols. NRBmay be a number of physical resource blocks (PRBs) configured for a particular NR-PDCCH set. The value of NRBmay allow at least one BD candidate with supported maximum AL.

K ∈ {1, 2, 4, . . . } may be a number of OFDM symbols configured for a particular NR-PDCCH set.

L ∈ {1, 2, 4, 8, 16} may be a number of aggregation levels in terms of number of CCEs per NR-PDCCII transmission.

Q ∈ {4, 6} may be a number of REGs per CCE, which can be dependent on DMRS overhead.

nRBLmay be a number of PRBs spanned by a candidate of aggregation level L.

nBDLmay be a number of blind decoding candidates of aggregation level L.

ñBDLmay be a high layer configured maximum number of BD candidates of aggregation level L, e.g., legacy LTE, e.g., 6, 6, 2, 2 for AL1,2,4,8, respectively. In some embodiments, 8, 4, 2, and 1 may be used to enable nested structure of BD candidates in the current TTI/slot/mini-slot.

In some embodiment, L may be 1, 2, 4, and 8, and may correspond to nBDLof 8, 4, 2, and 1, respectively.

In some embodiments where Q=4, K may be 1, 2, or 4. In embodiments where K is 1, NRB, min may be 32. In embodiments where K is 2, NRB, minmay be 16. In embodiments where K is 4, NRB, minmay be 8.

In some embodiments where Q=6, K may be 1, 2, or 3. In embodiments where K is 1, NRB, minmay be 48. In embodiments where K is 2, NRB, minmay be 24. In embodiments where K is 3, NRB, minmay be 16.

FIG. 10illustrates a graphical representation of another example CORESET configuration1000, according to various embodiments. In particular, each box of the graphical representation represents a subcarrier of the CORESET, wherein numbering of the subcarriers is shown directly to the left of the boxes. Further, the subcarriers may be organized into REGs and PRBs. Each column of subcarriers may correspond to an REG, wherein the number of the REG is shown above the column. Each group of subcarriers shown together may correspond to a PRB, wherein the number of the PRB is shown to the far left of the group.

The CORESET may include eight PRBs. For simplicity, a first PRB1002, a second PRB1004, and an eighth PRB1006are shown, and it is to be understood that the third PRB through the seventh PRB have the same arrangement as the first PRB1002, the second PRB1004, and the eighth PRB1006. The CORESET may further include four OFDM symbols. The four OFDM symbols are represented by the four columns of subcarriers in each of the PRBs. The subcarriers of the CORESET may be scheduled for transmission via two DMRS antenna ports (APs). In the illustrated embodiment, subcarriers are labeled with ‘0’ and ‘1’ to indicate the DMRS AP for which the subcarrier is scheduled.

The REGs in the CORESET may be numbered in a time-first order. In particular, the numbering may begin at REG01008of the first PRB1002. From REG01008, the numbering may proceed in the time-first order to the next REG in time in the CORESET, which is REG11010. The numbering may proceed in time-first order to REG31012, which is the last REG in the time domain in the first PRB1002having the same frequency as REG01008. The numbering may then proceed to the first REG in the time domain within the next PRB in the frequency domain, which is REG41014. The numbering of REGs may proceed in the same fashion until all of the REGs in the CORESET have been numbered.

The configuration of LSS may be defined by a formula. In particular, the ithBD candidates of aggregation level, L, may include REGs with the indexes formulated by

rL,i={rmL,i⁢:⁢⁢m=0,1,…⁢,QL-1,i=0,1,…⁢⁢nBDL},where⁢⁢rmL,i=mod⁡(r0L,i+m,NRB⁢K),nRBL=⌈QLK⌉,nBDL=min⁢{⌊NRBnRBL⌋,n~BDL},r0L,i=mod⁡(f⁡(nTTI,nUE)+i⁢⌊NRBnBDL⌋,NRB-nRBL)⁢K,and⁢⁢i=0,1,…⁢,nBDL-1.⁢⁢f⁡(nTTI,nUE)
may be a pseudorandom value generation with function with a range of (0, 1, . . . , NRB−nRBL−1). nTTImay denote the index of TTI in a frame. nUEmay denote a UE identity allocated by a network.

FIG. 11illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration1100may be utilized for UEs of AL1within a network. A second CORESET configuration1150may be related to CORESET configuration1100and may be utilized for UEs of AL2within the network. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration1100may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration1100includes eight PRBs, wherein each of the PRBs are represented by a row within the graphical representation. The CORESET of the CORESET configuration1100may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration1100includes four OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration1100may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes32REGs based on the eight PRBs and the four OFDM symbols.

The CORESET configuration1100may support one or more BD candidates. The BD candidates may also be referred to as CCEs or NR-PDCCH candidates. In the illustrated embodiment, the CORESET configuration1100includes eight BD candidates. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include four REGs, based on the 32 REGs within the CORESET and the eight BD candidates supported.

The graphical representation may include a number within each of the boxes. The number may indicate a BD candidate of which the REG corresponding to the box is included within. The numbering may be from ‘1’ to ‘8’ to indicate each of the BD candidates. The numbering of the REGs, as represented by the boxes, illustrated may be generated in accordance with the description that follows.

The CORESET configuration1100may include localized BD candidates, localized in either a frequency localized manner or a time localized manner. In the illustrated embodiment, the CORESET configuration1100includes localized BD candidates, localized in a frequency localized manner. In particular, all the REGs within a BD candidate may be located within a same frequency within the frequency domain.

Each of the localized BD candidates may include consecutive REGS, which are numbered in a time-first order or a frequency-first order. In the illustrated embodiment, the CORESET configuration1100includes localized BD candidates numbered in the time-first order.

The numbering of the REGs in CORESET configuration1100may begin at a first REG in the time domain and the frequency domain of the CORESET. In particular, in the illustrated embodiment, the numbering may begin at a first REG1102. The first REG1102may be numbered ‘1’, which corresponds to a first RD candidate.

After numbering the first REG1102, the numbering may implement the localization of the BD candidates. In the illustrated embodiment, the remaining REGs within the first BD candidate may be numbered in a frequency localized manner. In particular, the next three REGs with the same frequency as the first REG1102may be numbered ‘1’, which corresponds to the first BD candidate. Accordingly, a second REG1104, a third REG1106, and a fourth REG1108, which are the next three REGs with the same frequency as the first REG1102, are numbered ‘1’, which corresponds to the first BD candidate.

After implementation of the localization of the BD candidates for the first BD candidate, the numbering may proceed to the next REG in the time-first order after the fourth REG1108. As the fourth REG1108is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is the fifth REG1110. The numbering may have been incremented after completion of the numbering in the frequency localized manner, resulting in the fifth REG1110being numbered ‘2’. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1100are numbered.

The second CORESET configuration1150may be related to CORESET configuration1100and may be utilized for UEs of AL2within the network. The CORESET configuration1150may support half as many BD candidates as the CORESET configuration1100based on being for the UEs of AL2. Accordingly, the CORESET configuration1150may support four BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include eight REGs, based on the 32 REGs within the CORESET and the four BD candidates supported.

The numbering of the REGs in CORESET configuration1150may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1150. In particular, in the illustrated embodiment, the numbering may begin at a first REG1152. The first REG1152may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1152, the numbering may implement the localization of the BD candidates. In the illustrated embodiment, the remaining REGs within the first BD candidate may be numbered in a frequency localized manner. In particular, the next seven REGs in the time-first order may be numbered ‘1’, which corresponds to the first BD candidate. Accordingly, the first REG1152through the fourth REG1154may be numbered ‘1’. As the fourth REG1154is the last REG of the frequency, the numbering in the frequency localized manner may proceed to the first REG, in time, of the next frequency, which is fifth REG1156. The numbering in the frequency localized manner may then number the fifth REG1156through an eighth REG1158with the number ‘1’. Accordingly, eight REGs may be assigned to a first BD candidate within the CORESET configuration1150after completion of the numbering in the frequency localized manner.

After implementation of the localization of the BD candidates for the first BD candidate, the numbering may proceed to the next REG in the time-first order after the eighth REG1158. As the eighth REG1158is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is a ninth REG1160. The numbering may have been incremented after completion of the numbering in the frequency localized manner, resulting in the ninth REG1160being numbered ‘2’. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1150are numbered.

FIG. 12illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a third CORESET configuration1200may be related to the CORESET configuration1100(FIG. 11) and may be utilized for UEs of AL4within a network. A fourth CORESET configuration1250may be related to CORESET configuration1100and may be utilized for UEs of AL8within the network.

The third CORESET configuration1200may be related to CORESET configuration1100and may be utilized for UEs of AL4within the network. The CORESET configuration1200may support a quarter as many BD candidates as the CORESET configuration1100based on being for the UEs of AL4. Accordingly, the CORESET configuration1200may support two BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include 16 REGs, based on the 32 REGs within the CORESET and the two BD candidates supported.

The numbering of the REGs in CORESET configuration1200may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1200. In particular, in the illustrated embodiment, the numbering may begin at a first REG1202. The first REG1202may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1202, the numbering may implement the localization of the BD candidates. In the illustrated embodiment, the remaining REGs within the first BD candidate may be numbered in a frequency localized manner. In particular, the next 15 REGs in the time-first order may be numbered ‘1’, which corresponds to the first BD candidate. Accordingly, the first REG1202through the fourth REG1204may be numbered ‘1’. As the fourth REG1204is the last REG of the frequency, the numbering in the frequency localized manner may proceed to the first REG, in time, of the next frequency, which is fifth REG1206. The numbering in the frequency localized manner may proceed to number the REGs in the time-first order until 16 REGs have been numbered with ‘1’. In particular, the numbering may number the first REG1202through a sixteenth REG1208with the number ‘1’.

After implementation of the localization of the BD candidates for the first BD candidate, the numbering may proceed to the next REG in the time-first order after the sixteenth REG1208. As the sixteenth REG1208is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is a seventeenth REG1210. The numbering may have been incremented after completion of the numbering in the frequency localized manner, resulting in the seventeenth REG1210being numbered ‘2’. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1200are numbered.

The fourth CORESET configuration1250may be related to CORESET configuration1100and may be utilized for UEs of AL8within the network. The CORESET configuration1250may support an eighth as many BD candidates as the CORESET configuration1100based on being for the UEs of AL8. Accordingly, the CORESET configuration1250may support one BD candidate in the illustrated embodiment. As the CORESET configuration1250includes only one BD candidate, all the REGs within the CORESET may be assigned to the first BD candidate and numbered with ‘1’, which corresponds to the first candidate.

FIG. 13illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration1300may be utilized for UEs of AL1within a network. A second CORESET configuration1350may be related to CORESET configuration1300and may be utilized for UEs of AL2within the network. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration1300may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration1300includes 16 PRBs, wherein each of the PRBs are represented by a row within the graphical representation. The CORESET of the CORESET configuration1300may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration1300includes two OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration1300may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes 32 REGs based on the 16 PRBs and the two OFDM symbols.

The CORESET configuration1300may support one or more BD candidates. In the illustrated embodiment, the CORESET configuration1300includes eight BD candidates. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include four REGs, based on the 32 REGs within the CORESET and the eight BD candidates supported.

The graphical representation may include a number within each of the boxes. The number may indicate a BD candidate of which the REG corresponding to the box is included within. The numbering may be from ‘1’ to ‘8’ to indicate each of the BD candidates. The numbering of the REGs, as represented by the boxes, illustrated may be generated in accordance with the description that follows.

The CORESET configuration1300may include localized BD candidates, localized in either a frequency localized manner or a time localized manner. In the illustrated embodiment, the CORESET configuration1300includes localized BD candidates, localized in a frequency localized manner. In particular, all the REGs within a BD candidate may be located within a same frequency within the frequency domain, or within adjacent frequencies where less REGs exist at a frequency than threre are REGs within the BD candidate.

Each of the localized BD candidates may include consecutive REGS, which are numbered in a time-first order or a frequency-first order. In the illustrated embodiment, the CORESET configuration1300includes localized BD candidates numbered in the time-first order.

The numbering of the REGs in CORESET configuration1300may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1300. In particular, in the illustrated embodiment, the numbering may begin at a first REG1302. The first REG1302may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1302, the numbering may implement the localization of the BD candidates. In the illustrated embodiment, the remaining REGs within the first BD candidate may be numbered in a frequency localized manner. In particular, the next three REGs in time-first order may be numbered ‘1’, which corresponds to the first BD candidate. Accordingly, a second REG1304, which is the next REG in the time-first order from the first REG1302, is numbered ‘1’. As the second REG1304is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is a third REG1306. The REGs may continue to be numbered in the time-first order until four REGs have been assigned to the first BD candidate, resulting in a fourth REG1308being numbered ‘1’.

After implementation of the localization of the BD candidates for the first BD candidate, the numbering may proceed to the next REG in the time-first order after the fourth REG1308. As the fourth REG1308is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is a fifth REG1310. The numbering may have been incremented after completion of the numbering in the frequency localized manner, resulting in the fifth REG1310being numbered ‘2’. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1300are numbered.

The second CORESET configuration1350may be related to CORESET configuration1300and may be utilized for UEs of AL2within the network. The CORESET configuration1350may support half as many BD candidates as the CORESET configuration1300based on being for the UEs of AL2. Accordingly, the CORESET configuration1350may support four BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include eight REGs, based on the 32 REGs within the CORESET and the four BD candidates supported.

The numbering of the REGs in CORESET configuration1350may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1350. In particular, in the illustrated embodiment, the numbering may begin at a first REG1352. The first REG1352may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1352, the numbering may implement the localization of the BD candidates. In the illustrated embodiment, the remaining REGs within the first BD candidate may be numbered in a frequency localized manner. In particular, the next seven REGs in the time-first order may be numbered ‘1’, which corresponds to the first BD candidate. Accordingly, the first REG1352through the second REG1354may be numbered ‘1’. As the second REG1354is the last REG of the frequency, the numbering in the frequency localized manner may proceed to the first REG, in time, of the next frequency, which is third REG1356. The numbering in the frequency localized manner may then number the third REG1356through an eighth REG1358with the number ‘1’. Accordingly, eight REGs may be assigned to a first BD candidate within the CORESET configuration1350after completion of the numbering in the frequency localized manner.

After implementation of the localization of the BD candidates for the first BD candidate, the numbering may proceed to the next REG in the time-first order after the eighth REG1358. As the eighth REG1358is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is a ninth REG1360. The numbering may have been incremented after completion of the numbering in the frequency localized manner, resulting in the ninth REG1360being numbered ‘2’. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1350are numbered.

FIG. 14illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a third CORESET configuration1400may be related to the CORESET configuration1300(FIG. 13) and may be utilized for UEs of AL4within a network. A fourth CORESET configuration1450may be related to CORESET configuration1300and may be utilized for UEs of AL8within the network.

The third CORESET configuration1400may be related to CORESET configuration1300and may be utilized for UEs of AL4within the network. The CORESET configuration1400may support a quarter as many BD candidates as the CORESET configuration1300based on being for the UEs of AL4. Accordingly, the CORESET configuration1400may support two BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include 16 REGs, based on the 32 REGs within the CORESET and the two BD candidates supported.

The numbering of the REGs in CORESET configuration1400may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1400. In particular, in the illustrated embodiment, the numbering may begin at a first REG1402. The first REG1402may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1402, the numbering may implement the localization of the BD candidates. In the illustrated embodiment, the remaining REGs within the first BD candidate may be numbered in a frequency localized manner. In particular, the next 15 REGs in the time-first order may be numbered ‘1’, which corresponds to the first BD candidate. Accordingly, the first REG1402and a second REG1404may be numbered ‘1’. As the second REG1404is the last REG of the frequency, the numbering in the frequency localized manner may proceed to the first REG, in time, of the next frequency, which is third REG1406. The numbering in the frequency localized manner may proceed to number the REGs in the time-first order until 16 REGs have been numbered with ‘1’. In particular, the numbering may number the first REG1402through a sixteenth REG1408with the number ‘1’.

After implementation of the localization of the BD candidates for the first BD candidate, the numbering may proceed to the next REG in the time-first order after the sixteenth REG1408. As the sixteenth REG1408is the last REG of the frequency, the numbering may proceed to the first REG, in time, within the next frequency, which is a seventeenth REG1410. The numbering may have been incremented after completion of the numbering in the frequency localized manner, resulting in the seventeenth REG1410being numbered ‘2’. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1400are numbered.

The fourth CORESET configuration1450may be related to CORESET configuration1300and may be utilized for UEs of AL8within the network. The CORESET configuration1450may support an eighth as many BD candidates as the CORESET configuration1300based on being for the UEs of AL8. Accordingly, the CORESET configuration1450may support one BD candidate in the illustrated embodiment. As the CORESET configuration1450includes only one BD candidate, all the REGs within the CORESET may be assigned to the first BD candidate and numbered with ‘1’, which corresponds to the first BD candidate.

FIG. 15illustrates a graphical representation of another example CORESET configuration1500, according to various embodiments. The CORESET configuration1500may illustrate a frequency-first order numbering approach. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration1500may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration1500includes 8 PRBs, wherein each of the PRBs are represented by a row within the graphical representation. Two of the rows are omitted from the figure for simplicity; however, the numbering approach described below is to be understood to continue with the two omitted rows. The CORESET of the CORESET configuration1500may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration1500includes four OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration1500may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes 32 REGs based on the eight PRBs and the four OFDM symbols.

The CORESET configuration1500may illustrate a frequency-first order numbering approach. The numbering of the CORESET configuration1500may begin at a first REG in the time domain and the frequency domain, which is a first REG1502. In the illustrated embodiment, the count of the numbering may increment after each REG is numbered. The numbering may proceed from the first REG1502to the next REG in frequency, which is the second REG1504. The numbering may proceed in the frequency-first order to the numbering of an eighth REG1506. As the eighth REG is the last REG of the time, the numbering may proceed to a first REG, in frequency, of the next time, which is a ninth REG1508. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1500are numbered.

FIG. 16illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration1600may be utilized for UEs of AL1within a network. A second CORESET configuration1650may be related to CORESET configuration1600and may be utilized for UEs of AL2within the network. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration1600may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration1600includes eight PRBs, wherein each of the PRBs are represented by a row within the graphical representation. The CORESET of the CORESET configuration1600may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration1600includes four OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration1600may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes32REGs based on the eight PRBs and the four OFDM symbols.

The CORESET configuration1600may support one or more BD candidates. In the illustrated embodiment, the CORESET configuration1600includes eight BD candidates. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include four REGs, based on the 32 REGs within the CORESET and the eight BD candidates supported.

The graphical representation may include a number within each of the boxes. The number may indicate a BD candidate of which the REG corresponding to the box is included within. The numbering may be from ‘1’ to ‘8’ to indicate each of the BD candidates. The numbering of the REGs, as represented by the boxes, illustrated may be generated in accordance with the description that follows.

The CORESET configuration1600may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration1600, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be two shifts based on the BD candidates including four REGs and the CORESET including eight PRBs, the two shifts providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration1600may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1600. In particular, in the illustrated embodiment, the numbering may begin at a first REG1602. The first REG1602may be numbered ‘1’, which corresponds to a first BD candidate. The count of the numbering may be incremented after each REG is numbered. Further, the count may cycle back to ‘1’ after an REG has been assigned the maximum number, which is ‘8’ in the illustrated embodiment.

After numbering the first REG1602, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is the second REG1604. The second REG1604may be numbered ‘2’. The numbering may proceed in the frequency-first order until an eighth REG1606is numbered with ‘8’. The numbering may cycle back to ‘1’ after numbering the eighth REG1606with ‘8’.

As the eighth REG1606is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a ninth REG1608. Rather than numbering the ninth REG1608, the cyclic shift may be applied, shifting the numbering by two REGs in the frequency domain to an eleventh REG1610. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the eleventh REG1610are numbered. The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1600have been numbered.

The second CORESET configuration1650may be related to CORESET configuration1600and may be utilized for UEs of AL2within the network. The CORESET configuration1650may support half as many BD candidates as the CORESET configuration1600based on being for the UEs of AL2. Accordingly, the CORESET configuration1650may support four BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include eight REGs, based on the 32 REGs within the CORESET and the four RD candidates supported.

The CORESET configuration1650may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration1650, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be one shift based on the BD candidates including eight REGs and the CORESET including eight PRBs, the one shift providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration1650may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1650. In particular, in the illustrated embodiment, the numbering may begin at a first REG1652. The first REG1652may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the First REG1652, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is the second REG1654. The second REG1654may be numbered ‘2’. The numbering may proceed in the frequency-first order until a fourth REG1658is numbered with ‘4’. The numbering may cycle back to ‘1’ after numbering the fourth REG1658with ‘4’. The numbering may proceed to the next REG in the frequency, which is a fifth REG1659. The fifth-REG1659may be numbered ‘1’ based on the numbering being cycled back to ‘1’ after the fourth REG1658. The numbering may proceed to an eighth REG1660, which is numbered with ‘4’.

As the eighth REG1660is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a ninth REG1662. Rather than numbering the ninth REG1662, the cyclic shift may be applied, shifting the numbering by one REG in the frequency domain to a tenth REG1664. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the tenth REG1664are numbered, The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1650have been numbered.

FIG. 17illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a third CORESET configuration1700may be related to the CORESET configuration1600(FIG. 16) and may be utilized for UEs of AL4within a network. A fourth CORESET configuration1750may be related to CORESET configuration1600and may be utilized for UEs of AL8within the network. Each box shown within the graphical representations represents an REG.

The third CORESET configuration1700may be related to CORESET configuration1600and may be utilized for UEs of AL4within the network. The CORESET configuration1700may support a quarter as many BD candidates as the CORESET configuration1600based on being for the UEs of AL4. Accordingly, the CORESET configuration1700may support two BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include 16 REGs, based on the 32 REGs within the CORESET and time two BD candidates supported.

The CORESET configuration1700may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration1700, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be one shift based on the BD candidates including 16 REGs and the CORESET including eight PRBs, the one shift providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration1700may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1700. In particular, in the illustrated embodiment, the numbering may begin at a first REG1702. The first REG1702may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1702, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is a second REG1704. The second REG1704may be numbered ‘2’. The numbering may cycle back to ‘1’ after numbering the second REG1704with ‘2’. The numbering may proceed to the next REG in the frequency, which is a third REG1706. The third REG1706may be numbered ‘1’ based on the numbering being cycled back to ‘1’ after the second REG1704. The numbering may proceed to an eighth REG1708, which is numbered with ‘2’.

As the eighth REG1708is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a ninth REG1710. Rather than numbering the ninth REG1710, the cyclic shift may be applied, shifting the numbering by one REG in the frequency domain to a tenth REG1712. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the tenth REG1712are numbered. The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1700have been numbered.

The fourth CORESET configuration1750may be related to CORESET configuration1600and may be utilized for UEs of AL8within the network. The CORESET configuration1750may support an eighth as many BD candidates as the CORESET configuration1600based on being for the UEs of AL8. Accordingly, the CORESET configuration1750may support one BD candidate in the illustrated embodiment. As the CORESET configuration1750includes only one BD candidate, all the REGs within the CORESET may be assigned to the first BD candidate and numbered with ‘1’, which corresponds to the first BD candidate.

FIG. 18illustrates a graphical representation of another example CORESET configuration, according to various embodiments. In particular, a CORESET configuration1800may be utilized for UEs of AL1within a network. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration1800may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration1800includes 16 PRBs, wherein each of the PRBs are represented by a row within the graphical representation. The CORESET of the CORESET configuration1800may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration1800includes four OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration1800may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes 32 REGs based on the 16 PRBs and the two OFDM symbols. The CORESET configuration1800may support one or more BD candidates. In the illustrated embodiment, the CORESET configuration1800includes eight BD candidates. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include four REGs, based on the 32 REGs within the CORESET and the eight BD candidates supported.

The graphical representation may include a number within each of the boxes. The number may indicate a BD candidate of which the REG corresponding to the box is included within. The numbering may be from ‘1’ to ‘8’ to indicate each of the BD candidates. The numbering of the REGs, as represented by the boxes, illustrated may be generated in accordance with the description that follows.

The CORESET configuration1800may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration1800, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be four shifts based on the BD candidates including four REGs and the CORESET including sixteen PRBs, the four shifts providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration1800may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1800. In particular, in the illustrated embodiment, the numbering may begin at a first REG1802. The first REG1802may be numbered ‘1’, which corresponds to a first BD candidate. The count of the numbering may be incremented after each REG is numbered. Further, the count may cycle back to ‘1’ after an REG has been assigned the maximum number, which is ‘8’ in the illustrated embodiment.

After numbering the first REG1802, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is a second REG1804. The second REG1804may be numbered ‘2’. The numbering may proceed in the frequency-first order until an eighth REG1806is numbered with ‘8’. The numbering may cycle back to ‘1’ after numbering the eighth REG1806with ‘8’. The numbering may proceed from the eighth REG1806in the frequency-first order to a ninth REG1808, and may number the ninth REG1808with ‘1’. The numbering may proceed to a sixteenth REG1810, and may number the sixteenth REG1810with ‘8’.

As the sixteenth REG1810is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a seventeenth REG1812. Rather than numbering the seventeenth REG1812, the cyclic shift may be applied, shifting the numbering by four REGs in the frequency domain to a twenty-first REG1814. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the twenty-first REG1814are numbered. The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1800have been numbered.

FIG. 19illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a second CORESET configuration1900may be related to the CORESET configuration1800(FIG. 18) and may be utilized for UEs of AL2within a network. A third CORESET configuration1950may be related to CORESET configuration1800and may be utilized for UEs of AL4within the network. Each box shown within the graphical representations represents an REG.

The second CORESET configuration1900may be related to CORESET configuration1800and may be utilized for UEs of AL2within the network. The CORESET configuration1900may support half as many BD candidates as the CORESET configuration1800based on being for the UEs of AL2. Accordingly, the CORESET configuration1900may support four BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include eight REGs, based on the 32 REGs within the CORESET and the four BD candidates supported.

The CORESET configuration1900may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration1900, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be two shifts based on the BD candidates including eight REGs and the CORESET including 16 PRBs, the two shifts providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration1900may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1900. In particular, in the illustrated embodiment, the numbering may begin at a first REG1902. The first REG1902may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1902, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is the second REG1904. The second REG1904may be numbered ‘2’. The numbering may proceed in the frequency-first order until a fourth REG1908is numbered with ‘4’. The numbering may cycle back to ‘1’ after numbering the fourth REG1908with ‘4’. The numbering may proceed to the next REG in the frequency, which is a fifth REG1909. The fifth REG1909may be numbered ‘1’ based on the numbering being cycled back to ‘1’ after the fourth REG1908. The numbering may proceed to a sixteenth REG1910, which is numbered with ‘4’.

As the sixteenth REG1910is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a seventeenth REG1912. Rather than numbering the seventeenth REG1912, the cyclic shift may be applied, shifting the numbering by two REGs in the frequency domain to a nineteenth REG1914. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the nineteenth REG1914are numbered. The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1900have been numbered.

The third CORESET configuration1950may be related to CORESET configuration1800and may be utilized for UEs of AL4within the network. The CORESET configuration1950may support a quarter as many BD candidates as the CORESET configuration1800based on being for the UEs of AL4. Accordingly, the CORESET configuration1950may support two BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include 16 REGs, based on the 32 REGs within the CORESET and the two BD candidates supported.

The CORESET configuration1950may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration1950, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be one shift based on the BD candidates including 16 REGs and the CORESET including eight PRBs, the one shift providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration1950may begin at a first REG in the time domain and the frequency domain of the CORESET configuration1950. In particular, in the illustrated embodiment, the numbering may begin at a first REG1952. The first REG1952may be numbered ‘1’, which corresponds to a first BD candidate.

After numbering the first REG1952, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is a second REG1954. The second REG1954may be numbered ‘2’. The numbering may cycle back to ‘1’ after numbering the second REG1954with ‘2’. The numbering may proceed to the next REG in the frequency, which is a third REG1956. The third REG1956may be numbered ‘1’ based on the numbering being cycled back to ‘1’ after the second REG1954. The numbering may proceed to a sixteenth REG1958, which is numbered with ‘2’.

As the sixteenth REG1958is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a seventeenth REG1960. Rather than numbering the seventeenth REG1960, the cyclic shift may be applied, shifting the numbering by one REG in the frequency domain to an eighteenth REG1962. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the eighteenth REG1962are numbered. The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration1950have been numbered.

FIG. 20illustrates graphical representations of another example CORESET configuration2000, according to various embodiments. The fourth CORESET configuration2000may be related to CORESET configuration1800(FIG. 18) and may be utilized for UEs of AL8within the network. The CORESET configuration2000may support an eighth as many BD candidates as the CORESET configuration1800based on being for the UEs of AL8. Accordingly, the CORESET configuration2000may support one BD candidate in the illustrated embodiment. As the CORESET configuration2000includes only one BD candidate, all the REGs within the CORESET may be assigned to the first BD candidate and numbered with ‘1’, which corresponds to the first BD candidate.

FIG. 21illustrates a tabular representation2100of example correspondence between HSS approaches and HSS structures, according to various embodiments. In particular, some of the HSS structures may lead to a same HSS mapping approach/result. Tabular representation2100illustrates the correspondence between the HSS approaches and the HSS structures.

The tabular representation2100includes a first column2102that lists some approaches that may result from the HSS structures. The tabular representation2100includes a second column2104that lists the HSS structures that may correspond to each of the approaches. For example, a first approach2106within the first column2102may correspond to H1, H3, H7, and H9HSS structures, as shown in the second column2104.

This section only provides the SS formulation for the “Method 6” associated HSS structure H8highlighted in Table 1. The SS formulation for other HSS structures may be obtained by similar principle.

A sixth approach2108may correspond to H8. The sixth approach may be formulated for frequency-first REG numbering applied in distributed NR-PDCCH SS. Based on frequency-first REG numbering applied in distributed NR-PDCCH SS, the ith BD candidate of aggregation level L may include REGs with the following indexes, rL,i=

FIG. 22illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, the CORESET configurations ofFIG. 22may be associated with H8. A first CORESET configuration2200may be utilized for UEs of AL1within a network. A second CORESET configuration2250may be related to CORESET configuration2200and may be utilized for UEs of AL2within the network. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration2200may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration2200includes eight PRBs, wherein each of the PRBs are represented by a row within the graphical representation. The CORESET of the CORESET configuration2200may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration2200includes four OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration2200may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes32REGs based on the eight PRBs and the four OFDM symbols.

The CORESET configuration2200may support one or more BD candidates. In the illustrated embodiment, the CORESET configuration2200includes eight BD candidates. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include four REGs, based on the 32 REGs within the CORESET and the eight BD candidates supported.

The graphical representation may include a number within each of the boxes. The number may indicate a BD candidate of which the REG corresponding to the box is included within. The numbering may be from ‘1’ to ‘8’ to indicate each of the BD candidates. The numbering of the REGs, as represented by the boxes, illustrated may be generated in accordance with the description that follows.

The CORESET configuration2200may include BD candidates that are REG based distributed NR-PDCCH candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration2200, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be two shifts based on the BD candidates including four REGs and the CORESET including eight PRBs, the two shifts providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration2200may begin at a first REG in the time domain and the frequency domain of the CORESET configuration2200. In particular, in the illustrated embodiment, the numbering may begin at a first REG2202. The first REG2202may be numbered ‘1’, which corresponds to a first BD candidate. The count of the numbering may be incremented after each REG is numbered. Further, the count may cycle back to ‘1’ after an REG has been assigned the maximum number, which is ‘8’ in the illustrated embodiment.

After numbering the first REG2202, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is the second REG2204. The second REG2204may be numbered ‘2’. The numbering may proceed in the frequency-first order until an eighth REG2206is numbered with ‘8’. The numbering may cycle back to ‘1’ after numbering the eighth REG2206with ‘8’.

As the eighth REG2206is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a ninth REG2208. Rather than numbering the ninth REG2208, the cyclic shift may be applied, shifting the numbering by two REGs in the frequency domain to an eleventh REG2210. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the eleventh REG2210are numbered. The numbering may again perform a cyclic shift after completion of the numbering of the REGs within the time. The numbering may proceed in the disclosed fashion until all the REGs within the CORESET of the CORESET configuration2200have been numbered.

The second CORESET configuration2250may be related to CORESET configuration2200and may be utilized for UEs of AL2within the network. The CORESET configuration2250may support half as many BD candidates as the CORESET configuration2200based on being for the UEs of AL2. Accordingly, the CORESET configuration2250may support four BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include eight REGs, based on the 32 REGs within the CORESET and the four BD candidates supported.

The CORESET configuration2250may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

Further, the CORESET configuration2250may have an aggregation direction. The aggregation direction may be in the frequency domain or in the time domain. The configuration of higher AL CORESET configurations may aggregate the REGs of the CORESET configuration2200based on the aggregation direction. In particular, each BD candidate in the higher ALs may be aggregated to include a number of BD candidates of the CORESET configuration2200equal to the AL, wherein the BD candidates of the CORESET configuration2200are combined in the aggregation direction to produce the BD candidates of the higher ALs. In the illustrated embodiment, the CORESET configuration2250may have an aggregation direction in the frequency domain, causing the adjacent BD candidates in the frequency domain of the CORESET configuration2200to be combined to produce a BD candidate of CORESET configuration2250.

In the illustrated embodiment, the CORESET configuration2250has an AL of two and an AL direction in the frequency domain. As shown in the CORESET configuration2200, the first BD candidate may include the first REG2202and the second BD candidate, which is adjacent to the first BD candidate in the frequency domain, may include the second REG2204. In the CORESET configuration2250, the first BD candidate and the second BD candidate of the CORESET configuration2200may be combined to produce a first BD candidate of the CORESET configuration2250based on the AL of the CORESET configuration2250being two. Accordingly, the first REG2252and the second REG2254may be numbered with ‘1’, which corresponds to the first BD candidate of the CORESET configuration2250. Further, a third BD candidate and a fourth BD candidate of the CORESET configuration2200may be combined to produce a second BD candidate of the CORESET configuration2250. Accordingly, a third REG2256and a fourth REG2258may be numbered with ‘2’, which corresponds to the second BD candidate of the CORESET configuration2250. The aggregation procedure may be applied to all the REGs within the CORESET configuration2200to produce the CORESET configuration2250.

FIG. 23illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a third CORESET configuration2300may be related to the CORESET configuration2200(FIG. 22) and may be utilized for UEs of AL4within a network. A fourth CORESET configuration2350may be related to CORESET configuration2200and may be utilized for UEs of AL8within the network. Each box shown within the graphical representations represents an REG.

The third CORESET configuration2300may be related to CORESET configuration2200and may be utilized for UEs of AL4within the network. The CORESET configuration2300may support a quarter as many BD candidates as the CORESET configuration2200based on being for the UEs of AL4. Accordingly, the CORESET configuration2300may support two BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include 16 REGs, based on the 32 REGs within the CORESET and the two BD candidates supported.

The CORESET configuration2300may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

Further, the CORESET configuration2300may have an aggregation direction. The aggregation direction may be in the frequency domain or in the time domain. The configuration of higher AL CORESET configurations may aggregate the REGs of the CORESET configuration2200based on the aggregation direction. In particular, each BD candidate in the higher ALs may be aggregated to include a number of BD candidates of the CORESET configuration2200equal to the AL, wherein the BD candidates of the CORESET configuration2200are combined in the aggregation direction to produce the BD candidates of the higher ALs. In the illustrated embodiment, the CORESET configuration2300may have an aggregation direction in the frequency domain, causing the adjacent BD candidates in the frequency domain of the CORESET configuration2200to be combined to produce a BD candidate of CORESET configuration2300.

In the illustrated embodiment, the CORESET configuration2300has an AL of four and an AL direction in the frequency domain. As shown in the CORESET configuration2200, the first BD candidate may include the first REG2202(FIG. 22), the second BD candidate may include the second REG2204(FIG. 22), a third BD candidate may include a third REG2212(FIG. 22), and a fourth BD candidate may include a fourth REG2214(FIG. 22), all of which are adjacent in the frequency domain. In the CORESET configuration2300, the first BD candidate, the second BD candidate, the third BD candidate, and the fourth BD candidate of the CORESET configuration2200may be combined to produce a first BD candidate of the CORESET configuration2300based on the AL of the CORESET configuration2300being four. Accordingly, a first REG2302, a second REG2304, a third REG2306, and a fourth REG2308may be numbered with ‘1’, which corresponds to the first BD candidate of the CORESET configuration2300. Further, a fifth BD candidate, a sixth BD candidate, a seventh BD candidate, and an eighth BD candidate of the CORESET configuration2200may be combined to produce a second BD candidate of the CORESET configuration2300. Accordingly, a fifth REG2310, a sixth REG2312, a seventh REG2314, and an eighth REG2316may be numbered with ‘2’, which corresponds to the second BD candidate of the CORESET configuration2300. The aggregation procedure may be applied to all the REGs within the CORESET configuration2200to produce the CORESET configuration2300.

The fourth CORESET configuration2350may be related to CORESET configuration2200and may be utilized for UEs of AL8within the network. The CORESET configuration2350may support an eighth as many BD candidates as the CORESET configuration2200based on being for the UEs of AL8. Accordingly, the CORESET configuration2350may support one BD candidate in the illustrated embodiment. As the CORESET configuration2350includes only one BD candidate, all the REGs within the CORESET may be assigned to the first BD candidate and numbered with ‘1’, which corresponds to the first BD candidate.

FIG. 24illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, the CORESET configurations ofFIG. 24may be associated with H8. A first CORESET configuration2400may be utilized for UEs of AL1within a network. A second CORESET configuration2450may be related to CORESET configuration2400and may be utilized for UEs of AL2within the network. Each box shown within the graphical representations represents an REG.

The CORESET of the CORESET configuration2400may include one or more PRBs. In the illustrated embodiment, the CORESET of the CORESET configuration2400includes 16 PRBs, wherein each of the PRBs are represented by a row within the graphical representation. The CORESET of the CORESET configuration2400may further include one or more OFDM symbols. In the illustrated embodiment, the CORESET of the CORESET configuration2400includes two OFDM symbols, wherein each of the OFDM symbols are represented by a column within the graphical representation. The CORESET of the CORESET configuration2400may include a number of REGs based on the number of PRBs and the number of OFDM symbols in the CORESET. In particular, there may be an REG for each combination of the PRBs and the OFDMs symbols. The illustrated embodiment includes 32 REGs based on the 16 PRBs and the two OFDM symbols.

The CORESET configuration2400may support one or more BD candidates. In the illustrated embodiment, the CORESET configuration2400includes eight BD candidates. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include four REGs, based on the32REGs within the CORESET and the eight BD candidates supported.

The graphical representation may include a number within each of the boxes. The number may indicate a BD candidate of which the REG corresponding to the box is included within. The numbering may be from ‘1’ to ‘8’ to indicate each of the BD candidates. The numbering of the REGs, as represented by the boxes, illustrated may be generated in accordance with the description that follows.

The CORESET configuration2400may include BD candidates that are REG based distributed NR-PDCCH candidates. Tn particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

In embodiments where the number of REGs outnumber the number of OFDM symbols, there may be more than one REG assigned to a certain BD candidate within a single OFDM symbol. Tn these embodiments, the REGs assigned to the certain BD candidate may be adjacent to each other in the numbering direction. For example, the number of REGs outnumber the number of OFDM symbols in the illustrated embodiment, and there may be more than one REG assigned to the BD candidates within a single OFDM symbol. In the illustrated embodiment, the REGs assigned to the same BD candidate within an OFDM symbol are located adjacent to each other in the frequency-first order.

In order to facilitate the distribution, a cyclic shift may be applied to the count of the numbering after completion of the numbering of the REGs within a time. The cyclic shift may be determined to provide equal distribution in the time domain and/or the frequency domain between the REGs assigned to a BD candidate. The cyclic shift may be determined based on the number of BD candidates supported by the CORESET configuration2400, the number of REGs to be assigned to each of the BD candidates, the number of PRBs within the CORESET, the number of REGs within the CORESET, or some combination thereof. For example, the cyclic shift may be determined to be eight shifts based on the BD candidates including four REGs and the CORESET including 16 PRBs, the eight shifts providing the greatest distribution of the REGs within the BD candidates.

The numbering of the REGs in CORESET configuration2400may begin at a first REG in the time domain and the frequency domain of the CORESET configuration2400. In particular, in the illustrated embodiment, the numbering may begin at a first REG2402. The first REG2402may be numbered ‘1’, which corresponds to a first BD candidate. Further, the count may cycle back to ‘1’ after an REG has been assigned the maximum number, which is ‘8’ in the illustrated embodiment.

After numbering the first REG2402, the numbering may proceed in the frequency-first order to the next REG in the frequency domain, which is the second REG2404. The second REG2404may be numbered ‘1’ based on two REGs being included in a first OFDM symbol2406and the REGs of the same number to be adjacent to each other in the first OFDM symbol2406.

The count of the numbering may increment after the second REG2404has been numbered. The numbering may proceed in the frequency-first order to a third REG2408and may number the third REG2408with ‘2’. The numbering may proceed in the frequency-first order until a sixteenth REG2410is numbered with ‘8’. The numbering may cycle back to ‘1’ after numbering the sixteenth REG2410with ‘8’.

As the sixteenth REG2410is the last REG of the time, the numbering may proceed to the next group of REGs in the time domain. Further, the cyclic shift may be applied to the numbering as the numbering proceeds to the next group of REGs in the time domain. In particular, the numbering may proceed to the REG adjacent in time to the REG at which the numbering began in the current group of REGs in the time domain, which is a seventeenth REG2412. Rather than numbering the seventeenth REG2412, the cyclic shift may be applied, shifting the numbering by eight REGs in the frequency domain to a twenty-fifth REG2414. The numbering may proceed in the frequency-first order until all the REGs in the time within the same group of REGs in the time domain with the twenty-fifth REG2414are numbered.

The second CORESET configuration2450may be related to CORESET configuration2400and may be utilized for UEs of AL2within the network. The CORESET configuration2450may support half as many BD candidates as the CORESET configuration2400based on being for the UEs of AL2. Accordingly, the CORESET configuration2450may support four BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include eight REGs, based on the 32 REGs within the CORESET and the four BD candidates supported.

The CORESET configuration2450may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

Further, the CORESET configuration2450may have an aggregation direction. The aggregation direction may be in the frequency domain or in the time domain. The configuration of higher AL CORESET configurations may aggregate the REGs of the CORESET configuration2400based on the aggregation direction. In particular, each BD candidate in the higher ALs may be aggregated to include a number of BD candidates of the CORESET configuration2400equal to the AL, wherein the BD candidates of the CORESET configuration2400are combined in the aggregation direction to produce the BD candidates of the higher ALs. In the illustrated embodiment, the CORESET configuration2450may have an aggregation direction in the frequency domain, causing the adjacent BD candidates in the frequency domain of the CORESET configuration2400to be combined to produce a BD candidate of CORESET configuration2450.

In the illustrated embodiment, the CORESET configuration2450has an AL of two and an AL direction in the frequency domain. As shown in the CORESET configuration2400, the first BD candidate may include the first REG2402and the second REG2404, and the second BD candidate may include the third REG2408and a fourth REG2416, all of which are adjacent in the frequency domain. In the CORESET configuration2450, the first BD candidate and the second BD candidate of the CORESET configuration2400may be combined to produce a first BD candidate of the CORESET configuration2450based on the AL of the CORESET configuration2450being two. Accordingly, a first REG2452, a second REG2454, a third REG2456, and a fourth REG2458may be numbered with ‘1’, which corresponds to the first BD candidate of the CORESET configuration2450. Further, a third BD candidate and a fourth BD candidate of the CORESET configuration2400may be combined to produce a second BD candidate of the CORESET configuration2450. Accordingly, a fifth REG2460, a sixth REG2462, a seventh REG2464, and an eighth REG2466may be numbered with ‘2’, which corresponds to the second BD candidate of the CORESET configuration2450. The aggregation procedure may be applied to all the REGs within the CORESET configuration2400to produce the CORESET configuration2450.

FIG. 25illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a third CORESET configuration2500may be related to the CORESET configuration2400(FIG. 24) and may be utilized for UEs of AL4within a network. A fourth CORESET configuration2550may be related to CORESET configuration2400and may be utilized for UEs of AL8within the network. Each box shown within the graphical representations represents an REG.

The third CORESET configuration2500may be related to CORESET configuration2400and may be utilized for UEs of AL4within the network. The CORESET configuration2500may support a quarter as many BD candidates as the CORESET configuration2400based on being for the UEs of AL4. Accordingly, the CORESET configuration2500may support two BD candidates in the illustrated embodiment. Each of the BD candidates may include an equal number of REGs. In the illustrated embodiment, each of the BD candidates may include 16 REGs, based on the 32 REGs within the CORESET and the two BD candidates supported.

The CORESET configuration2500may include distributed BD candidates. In particular, each of the BD candidates may include REGs that are distributed in both the time domain and the frequency domain. Accordingly, each of the REGs within each of the BD candidates may be of different frequency and/or different time from other REGs within the same BD candidate.

Further, the CORESET configuration2500may have an aggregation direction. The aggregation direction may be in the frequency domain or in the time domain. The configuration of higher AL CORESET configurations may aggregate the REGs of the CORESET configuration2400based on the aggregation direction. In particular, each BD candidate in the higher ALs may be aggregated to include a number of BD candidates of the CORESET configuration2400equal to the AL, wherein the BD candidates of the CORESET configuration2400are combined in the aggregation direction to produce the BD candidates of the higher ALs. In the illustrated embodiment, the CORESET configuration2500may have an aggregation direction in the frequency domain, causing the adjacent BD candidates in the frequency domain of the CORESET configuration2400to be combined to produce a BD candidate of CORESET configuration2500.

In the illustrated embodiment, the CORESET configuration2500has an AL of four and an AL direction in the frequency domain. As shown in the CORESET configuration2400, the first BD candidate may include the first REG2402(FIG. 24) and the second REG2404(FIG. 24), the second BD candidate may include the third REG2408(FIG. 24) and the fourth REG2416(FIG. 24), a third BD candidate may include a fifth REG2418(FIG. 24) and a sixth REG2420(FIG. 24), and a fourth BD candidate may include a seventh REG2422(FIG. 24) and an eighth REG2424(FIG. 24), all of which are adjacent in the frequency domain. In the CORESET configuration2500, the first BD candidate, the second BD candidate, the third BD candidate, and the fourth BD candidate of the CORESET configuration2400may be combined to produce a first BD candidate of the CORESET configuration2500based on the AL of the CORESET configuration2500being four. Accordingly, a first REG2502through an eighth REG2504may be numbered with ‘1’, which corresponds to the first BD candidate of the CORESET configuration2500. Further, a fifth BD candidate, a sixth BD candidate, a seventh BD candidate, and an eighth BD candidate of the CORESET configuration2400may be combined to produce a second BD candidate of the CORESET configuration2500. Accordingly, a ninth REG2506through an eighteenth REG2508may be numbered with ‘2’, which corresponds to the second BD candidate of the CORESET configuration2500. The aggregation procedure may be applied to all the REGs within the CORESET configuration2400to produce the CORESET configuration2500.

The fourth CORESET configuration2550may be related to CORESET configuration2400and may be utilized for UEs of AL8within the network. The CORESET configuration2550may support an eighth as many BD candidates as the CORESET configuration2400based on being for the UEs of AL8. Accordingly, the CORESET configuration2550may support one BD candidate in the illustrated embodiment. As the CORESET configuration2550includes only one BD candidate, all the REGs within the CORESET may be assigned to the first BD candidate and numbered with ‘1’, which corresponds to the first BD candidate.

FIG. 26illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration2600and a second CORESET configuration2650may be produced by applying the characteristics of H1, H3, H7, or H9, described above, to a CORESET. The first CORESET configuration2600may be utilized for UEs of AL1within a network. The second CORESET configuration2650may be related to the first CORESET configuration2600and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration2600and the second CORESET configuration2650may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration2600and the second CORESET configuration2650may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 27illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration2700and a second CORESET configuration2750may be produced by applying the characteristics of H2, described above, to a CORESET. The first CORESET configuration2700may be utilized for UEs of AL1within a network. The second CORESET configuration2750may be related to the first CORESET configuration2700and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration2700and the second CORESET configuration2750may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration2700and the second CORESET configuration2750may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 28illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration2800and a second CORESET configuration2850may be produced by applying the characteristics of H4, described above, to a CORESET. The first CORESET configuration2800may be utilized for UEs of AL1within a network. The second CORESET configuration2850may be related to the first CORESET configuration2800and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration2800and the second CORESET configuration2850may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration2800and the second CORESET configuration2850may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 29illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration2900and a second CORESET configuration2950may be produced by applying the characteristics of H5or H11, described above, to a CORESET. The first CORESET configuration2900may be utilized for UEs of AL1within a network. The second CORESET configuration2950may be related to the first CORESET configuration2900and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration2900and the second CORESET configuration2950may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration2900and the second CORESET configuration2950may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 30illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration3000and a second CORESET configuration3050may be produced by applying the characteristics of H6, described above, to a CORESET. The first CORESET configuration3000may be utilized for UEs of AL1within a network. The second CORESET configuration3050may be related to the first CORESET configuration3000and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration3000and the second CORESET configuration3050may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration3000and the second CORESET configuration3050may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 31illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration3100and a second CORESET configuration3150may be produced by applying the characteristics of H10, described above, to a CORESET. The first CORESET configuration3100may be utilized for UEs of AL1within a network. The second CORESET configuration3150may be related to the first CORESET configuration3100and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration3100and the second CORESET configuration3150may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration3100and the second CORESET configuration3150may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 32illustrates graphical representations of example CORESET configurations, according to various embodiments. In particular, a first CORESET configuration3200and a second CORESET configuration3250may be produced by applying the characteristics of H12, described above, to a CORESET. The first CORESET configuration3200may be utilized for UEs of AL1within a network. The second CORESET configuration3250may be related to the first CORESET configuration3200and may be utilized for UEs of AL2within a network.

The CORESET illustrated for the first CORESET configuration3200and the second CORESET configuration3250may include eight physical resource blocks, illustrated as rows within the graphical representations. Further, the CORESET illustrated for the first CORESET configuration3200and the second CORESET configuration3250may include four OFDM symbols, illustrated as columns within the graphical representations.

FIG. 33illustrates an architecture of a system XS00of a network in accordance with some embodiments. The system XS00is shown to include a user equipment (UE) XS01and a UE XS02. The UEs XS01and XS02are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

The UEs XS01and XS02may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) XS10—the RAN XS10may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs XS01and XS02utilize connections XS03and XS04, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections XS03and XS04are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs XS01and XS02may further directly exchange communication data via a ProSe interface XS05. The ProSe interface XS05may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

The UE XS02is shown to be configured to access an access point (AP) XS06via connection XS07. The connection XS07can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP XS06would comprise a wireless fidelity (WiFi®) router. In this example, the AP XS06is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). The RAN XS10can include one or more access nodes that enable the connections XS03and XS04. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN XS10may include one or more RAN nodes for providing macrocells, e.g., macro RAN node XS11, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node XS12.

Any of the RAN nodes XS11and XS12can terminate the air interface protocol and can be the first point of contact for the UEs XS01and XS02. In some embodiments, any of the RAN nodes XS11and XS12can fulfill various logical functions for the RAN XS10including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In accordance with some embodiments, the UEs XS01and XS02can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes XS11and XS12over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

The physical downlink shared channel (PDSCH) may early user data and higher-layer signaling to the UEs XS01and XS02. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs XS01and XS02about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UEs XS01and XS02within a cell) may be performed at any of the RAN nodes XS11and XS12based on channel quality information fed back from any of the UEs XS01and XS02. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs XS01and XS02.

The RAN XS10is shown to be communicatively coupled to a core network (CN) XS20—via an S1 interface XS13. In embodiments, the CN XS20may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface XS13is split into two parts: the S1-U interface XS14, which carries traffic data between the RAN nodes XS11and XS12and the serving gateway (S-GW) XS22, and the S1-mobility management entity (MME) interface XS15, which is a signaling interface between the RAN nodes XS11and XS12and MMEs XS21.

In this embodiment, the CN XS20comprises the MMEs XS21, the S-GW XS22. the Packet Data Network (PDN) Gateway (P-GW) XS23, and a home subscriber server (HSS) XS24. The MMEs XS21may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs XS21may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS XS24may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN XS20may comprise one or several HSSs XS24, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS XS24can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

The S-GW X522may terminate the S1 interface XS13towards the RAN XS10, and routes data packets between the RAN XS10and the CN XS20. In addition, the S-GW XS22may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The P-GW XS23may terminate an SGi interface toward a PDN. The P-GW XS23may route data packets between the CN XS20and external networks such as a network including the application server XS30(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface XS25. Generally, the application server XS30may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW XS23is shown to be communicatively coupled to an application server XS30via an IP communications interface XS25. The application server XS30can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs XS01and XS02via the CN XS20.

The P-GW XS23may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) XS26is the policy and charging control element of the CN XS20. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF XS26may be communicatively coupled to the application server XS30via the P-GW XS23. The application server XS30may signal the PCRF XS26to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF XS26may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCT), which commences the QoS and charging as specified by the application server XS30.

The UEs XS01and XS02and/or the RAN nodes XS11and XS12may implement one or more of the CORESETs and/or CORESET configurations, and/or approaches to generate the CORESETs and/or CORESET configurations, described herein. In particular, signaling may occur between the UEs and the RAN nodes to define the approaches, CORESETs, and/or CORESET configurations to be implemented by the UEs and the RAN nodes. For example, the RAN node XS11may transmit one or more signals to the UE XS01that indicate whether REGBs are to be implemented in the CORESETS, the number of REGs within each REGB, a bundling direction, a cyclic shift, whether LSS, DSS, or HSS is to be implemented, which HSS structure is to be implemented, a numbering direction, an aggregation direction, or some combination thereof. In other embodiments, the UE XS01may transmit the one or more signals, or the UE XS01may transmit a portion of the signals and the RAN node XS11may transmit another portion of the signals. Further, the UE XS01may transmit one or more signals that indicate an AL of the UE XS01. In some embodiments, the signaling may be transmitted via higher layers and/or RRC signaling.

Based on the signaling, the UEs XS01and XS02, and/or the RAN nodes XS11and XS12, may implement the indicated characteristics for SS and/or CORESET transmissions. Accordingly, the UEs XS01and XS02, and/or the RAN nodes XS11and X12may transmit and/or receive SS and/or CORESET transmissions of the same configuration, allowing the transmissions to be interpreted by both components. In some embodiments, the SS and/or CORESET transmissions may be transmitted vian NR-PDCCH.

FIG. 34illustrates, for one embodiment, example components of an electronic device100. In embodiments, the electronic device100may be, implement, be incorporated into, or otherwise be a part of a user equipment (UE), an evolved NodeB (eNB), and/or some other electronic device. In some embodiments, the electronic device100may include application circuitry102, baseband circuitry104, Radio Frequency (RF) circuitry106, front-end module (FEM) circuitry108and one or more antennas110, coupled together at least as shown. In embodiments where the electronic device100is implemented in or by an eNB, the electronic device100may also include network interface circuitry (not shown) for communicating over a wired interface (for example, an X2 interface, an S1 interface, and the like). In particular, the electronic device100may be implemented in or by the UEs XS01and XS02(FIG. 33), and/or the RAN nodes XS11and XS12(FIG. 33).

The application circuitry102may include one or more application processors. For example, the application circuitry102may include circuitry such as, but not limited to, one or more single-core or multi-core processors102a.The processor(s)102amay include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors102amay be coupled with and/or may include computer-readable media102b(also referred to as “CRM102b”, “memory102b”, “storage102b”, or “memory/storage102b”) and may be configured to execute instructions stored in the CRM102bto enable various applications and/or operating systems to run on the system.

The baseband circuitry104may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry104may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry106and to generate baseband signals for a transmit signal path of the RF circuitry106. Baseband circuity104may interface with the application circuitry102for generation and processing of the baseband signals and for controlling operations of the RF circuitry106. For example, in some embodiments, the baseband circuitry104may include a second generation (2G) baseband processor104a,third generation (3G) baseband processor104b,fourth generation (4G) baseband processor104c,and/or other baseband processor(s)104dfor other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry104(e.g., one or more of baseband processors104a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, modulation/demodulation circuitry of the baseband circuitry104may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry104may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry104may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU)104eof the baseband circuitry104may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP)104f.The audio DSP(s)104fmay include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. The baseband circuitry104may further include computer-readable media104g(also referred to as “CRM104g”, “memory104g”, “storage104g”, or “CRM104g”). The CRM104gmay be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry104. CRM104gfor one embodiment may include any combination of suitable volatile memory and/or non-volatile memory. The CRM104gmay include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc. The CRM104gmay be shared among the various processors or dedicated to particular processors. Components of the baseband circuitry104may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry104and the application circuitry102may be implemented together, such as, for example, on a system on a chip (SOC).

RF circuitry106may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry106may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry106may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry108and provide baseband signals to the baseband circuitry104. RF circuitry106may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by the baseband circuitry104and provide RF output signals to the FEM circuitry108for transmission.

In some embodiments, the RF circuitry106may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry106may include mixer circuitry106a,amplifier circuitry106band filter circuitry106c.The transmit signal path of the RF circuitry106may include filter circuitry106cand mixer circuitry106a.RF circuitry106may also include synthesizer circuitry106dfor synthesizing a frequency for use by the mixer circuitry106aof the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry106aof the receive signal path may be configured to down-convert RF signals received from the FEM circuitry108based on the synthesized frequency provided by synthesizer circuitry106d.The amplifier circuitry106bmay be configured to amplify the down-converted signals and the filter circuitry106cmay be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry104for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry106aof the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry106aof the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry106dto generate RF output signals for the FEM circuitry108. The baseband signals may be provided by the baseband circuitry104and may be filtered by filter circuitry106c.The filter circuitry106cmay include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry106dmay be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry106dmay be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. The synthesizer circuitry106dmay be configured to synthesize an output frequency for use by the mixer circuitry106aof the RF circuitry106based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry106dmay be a fractional N/N+1 synthesizer.

FEM circuitry108may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas110, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry106for further processing. FEM circuitry108may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry106for transmission by one or more of the one or more antennas110. In some embodiments, the FEM circuitry108may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry108may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry108may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry106). The transmit signal path of the FEM circuitry108may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas110).

In some embodiments, the electronic device100may include additional elements such as, for example, a display, a camera, one or more sensors, and/or interface circuitry (for example, input/output (I/O) interfaces or buses) (not shown). In embodiments where the electronic device is implemented in or by an eNB, the electronic device100may include network interface circuitry. The network interface circuitry may be one or more computer hardware components that connect electronic device100to one or more network elements, such as one or more servers within a core network or one or more other eNBs via a wired connection. To this end, the network interface circuitry may include one or more dedicated processors and/or field programmable gate arrays (FPGAs) to communicate using one or more network communications protocols such as X2 application protocol (AP), SI AP, Stream Control Transmission Protocol (SCTP), Ethernet, Point-to-Point (PPP), Fiber Distributed Data Interface (FDDI), and/or any other suitable network communications protocols.

FIG. 35illustrates example components of a device XT00in accordance with some embodiments. In some embodiments, the device XT00may include application circuitry XT02, baseband circuitry XT04, Radio Frequency (RF) circuitry XT06, front-end module (FEM) circuitry XT08, one or more antennas XT10, and power management circuitry (PMC) XT12coupled together at least as shown. The components of the illustrated device XT00may be included in a UE or a RAN node, such as one or more of the UE XS01, the UE XS02, the RAN node XS11, and/or the RAN node XS12. In some embodiments, the device XT00may include less elements (e.g., a RAN node may not utilize application circuitry XT02, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device XT00may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

The application circuitry XT02may include one or more application processors. For example, the application circuitry XT02may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device XT00. In some embodiments, processors of application circuitry XT02may process IP data packets received from an EPC.

The baseband circuitry XT04may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry XT04may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry XT06and to generate baseband signals for a transmit signal path of the RF circuitry XT06. Baseband processing circuity XT04may interface with the application circuitry XT02for generation and processing of the baseband signals and for controlling operations of the RF circuitry XT06. For example, in some embodiments, the baseband circuitry XT04may include a third generation (3G) baseband processor XT04A, a fourth generation (4G) baseband processor XT04B, a fifth generation (5G) baseband processor XT04C, or other baseband processor(s) XT04D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry XT04(e.g., one or more of baseband processors XT04A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry XT06. In other embodiments, some or all of the functionality of baseband processors XT04A-D may be included in modules stored in the memory XT04G and executed via a Central Processing Unit (CPU) XT04E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry XT04may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry XT04H of the baseband circuitry XT04may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry XT04may include one or more audio digital signal processor(s) (DSP) XT04F. The audio DSP(s) XT04F may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry XT04may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry XT04and the application circuitry XT02may be implemented together such as, for example, on a system on a chip (SOC).

RF circuitry XT06may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry XT06may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry XT06may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry XT08and provide baseband signals to the baseband circuitry XT04. RF circuitry XT06may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry XT04and provide RF output signals to the FEM circuitry XT08for transmission.

In some embodiments, the mixer circuitry XT06aof the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry XT06dto generate RF output signals for the FEM circuitry XT08. The baseband signals may be provided by the baseband circuitry XT04and may be filtered by filter circuitry XT06c.

The synthesizer circuitry XT06dmay be configured to synthesize an output frequency for use by the mixer circuitry XT06aof the RF circuitry XT06based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry XT06dmay be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry XT04or the application circuitry XT02depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry XT02.

FEM circuitry XT08may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas XT10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry XT06for further processing. FEM circuitry XT08may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry XT06for transmission by one or more of the one or more antennas XT10. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry XT06, solely in the FEM XT08, or in both the RF circuitry XT06and the FEM XT08.

In some embodiments, the FEM circuitry XT08may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry XT08may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry XT08may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry XT06). The transmit signal path of the FEM circuitry XT08may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry XT06), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas XT10).

In some embodiments, the PMC XT12may manage power provided to the baseband circuitry XT04. In particular, the PMC XT12may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC XT12may often be included when the device XT00is capable of being powered by a battery, for example, when the device is included in a UE. The PMC XT12may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

FIG. 35shows the PMC XT12coupled only with the baseband circuitry XT04. However, in other embodiments, the PMC XT12may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry XT02, RF circuitry XT06, or FEM XT08.

In some embodiments, the PMC XT12may control, or otherwise be part of, various power saving mechanisms of the device XT00. For example, if the device XT00is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device XT00may power down for brief intervals of time and thus save power.

If there is no data traffic activity for an extended period of time, then the device XT00may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device XT00goes into a very low power stale and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device XT00may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.

FIG. 36illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry XT04ofFIG. 35may comprise processors XT04A-XT04E and a memory XT04G utilized by said processors. Each of the processors XT04A-XT04E may include a memory interface, XU04A-XU04E, respectively, to send/receive data to/from the memory XT04G.

The baseband circuitry XT04may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface XU12(e.g., an interface to send/receive data to/from memory external to the baseband circuitry XT04), an application circuitry interface XU14(e.g., an interface to send/receive data to/from the application circuitry XT02ofFIG. 35), an RF circuitry interface XU16(e.g., an interface to send/receive data to/from RF circuitry XT06ofFIG. 35), a wireless hardware connectivity interface XU18(e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface XU20(e.g., an interface to send/receive power or control signals to/from the PMC XT12.

FIG. 37is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,FIG. 37shows a diagrammatic representation of hardware resources XZ00including one or more processors (or processor cores) XZ10, one or more memory/storage devices XZ20, and one or more communication resources XZ30, each of which may be communicatively coupled via a bus XZ40. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor XZ02may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources XZ00.

The communication resources XZ30may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices XZ04or one or more databases XZ06via a network XZ08. For example, the communication resources XZ30may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

Instructions XZ50may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors XZ10to perform any one or more of the methodologies discussed herein. The instructions XZ50may reside, completely or partially, within at least one of the processors XZ10(e.g., within the processor's cache memory), the memory/storage devices XZ20, or any suitable combination thereof. Furthermore, any portion of the instructions XZ50may be transferred to the hardware resources XZ00from any combination of the peripheral devices XZ04or the databases XZ06. Accordingly, the memory of processors XZ10, the memory/storage devices XZ20, the peripheral devices XZ04, and the databases XZ06are examples of computer-readable and machine-readable media.

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.

Some examples of embodiments that are to be understood to be disclosed herein are provided below.

Example 1 may include the network shall be able to configure the way of REGB construction in terms of following characteristics: Number of REGs in the REGB, where the number ranges from 1 to N_REG_per_REGB which is defined in the specification; and Bundling direction: time or frequency when multiple symbols are configured for the CORESET of the SS.

Example 2 may include the above configuration parameters can be part of the RRC signaling message for SS or CORESET (re)configuration.

Example 3 may include one option, the REGB can defined on a CORESET or SS level so that all NR-PDCCHs in an SS share the same way of REGB construction.

Example 4 may include another option, REGB configuration can be configured on each aggregation level so that NR-PDCCH of different ALs may have different way of REGB construction.

Example 5 may include for high AL NR-PDCCH, the size of REGB can be larger than that of smaller AL so that in low SNR situation, better channel estimation performance can be obtained from larger REGB size.

Example 6 may include REGB with different sizes and bundling direction can be configurable according to UE specific channel condition including channel selectivity in time and/or frequency and SNR at the UE receiver.

Example 7 may include for slow fading channel with high frequency selectivity, REGB in time may be configured, and REGB in frequency may be configured for frequency-flat and fast fading channel.

Example 8 may include first level of REGB numbering is performed so that each REGB is numbered according to certain order, e.g., time-first or frequency-first, defined in specification or signaled in the configuration message.

Example 9 may include cyclic shift determination of each REGB numbering cycle is performed so that cyclic shift of each REGB numbering cycle is determined so as to maximize the time and frequency diversity of each CCE.

Example 10 may include the total number of REGBs of a particular NR-PDCCH should be evenly distributed both in time and frequency.

Example 11 may include case of number of symbols in CORESET is greater than number of REGBs of an NR-PDCCH. A subset of OFDM symbols of CORESET can be chosen for REGBs of the NR-PDCCH.

Example 12 may include it can be also possible that no additional cyclic shift is required for all REGB numbering cycle to achieve maximum time-frequency diversity of NR-PDCCH.

Example 13 may include based on the determined cyclic shifts in step 2, cyclic shift is performed for each REGB numbering cycle.

Example 14 may include the method of example 1 or some other example herein, where CORESET of 2 OFDM symbols. REGB of 2 REGs in frequency and REGB numbered in time-first order. REGB numbered in time-first order in 1stand 3rdcycle of REGB numbering, and cyclically shifted time-first order in the 2ndcycle of REGB numbering shown inFIG. 3.

Example 15 may include the method of example 2 or some other example herein, where CORESET of 2 OFDM symbols. REGB of 3 REGs in frequency and REGB numbered in time-first order. REGB numbered in time-first order in 1stcycle of REGB numbering, and cyclically shifted time-first order in the 2ndcycle of REGB numbering shown inFIG. 5.

Example 16 may include the method of example 3 or some other example herein, where CORESET of 2 OFDM symbols. REGB of 3 REGs in frequency and REGB numbered in frequency-first order. REGB numbered in time-first order in 1stcycle of REGB numbering, and cyclically shifted frequency-first order in the 2ndcycle of REGB numbering shown inFIG. 7.

Example 17 may include Localized SS (LSS), wherein: given a configured control resource resource block (RB) set, each localized new radio physical downlink control channel (NR-PDCCH) blind decoding (BD) candidate is transmitted in frequency localized manner; each localized NR-PDCCH BD candidate is comprised of consecutive resource element groups (REGs) which are numbered in a time-first order; and localized NR-PDCCH is scheduled by a fifth generation NodeB (gNB) to benefit from potential frequency selective scheduling gain, better beamforming gain, and possible enhanced channel estimation with less demodulation reference signal (DMRS) overhead.

Example 18 may include Distributed SS (DSS), wherein: given a configured control resource RB set, each distributed NR-PDCCH BD candidate is transmitted in a distributed manner in both time and frequency domain; each distributed NR-PDCCH BD candidate is comprised of REGs which are evenly distributed in both time and frequency domain to maximize the achievable time-frequency diversity; and distributed NR-PDCCH is configured by gNB to benefit from the maximum available time-frequency diversity provided that gNB is not able to perform more advanced scheduling due to the lack of accurate channel state intormation (CSI) knowledge.

Example 19 may include Hierarchical SS (HSS), wherein given a configured control resource RB set, the NR-PDCCH at lowest aggregation level (AL), i.e. AL1, can be formed by a localized or distributed NR-PDCCH; the NR-PDCCII of higher AL is comprised of several NR-PDCCHs of lower AL so that the demodulated REs for NR-PDCC BD candidates of lower AL can be reused for the BD candidates of higher AL; and according to the key structures of HSS, there are 12 hierarchical SS structures, namely H1to H12, wherein H1includes the AL1BD candidate is REG based localized NR-PDCCH; the AL1BD candidates are numbered in time-first order; and BD candidates of higher AL aggregates the BD candidates in time domain; H2includes the AL1BD candidate is REG based distributed NR-PDCCH; the AL1BD candidates are numbered in time-first order; and BD candidates of higher AL aggregates the BD candidates in time domain; H3includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in time domain; the AL1BD candidate is cluster of REGs based localized NR-PDCCH; the AL1BD candidates are numbered in time-first order; and BD candidates of higher AL aggregates the BD candidates in time domain; H4includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in time domain; the AL1BD candidate is cluster of REGs based distributed NR-PDCCH; the AL1BD candidates are numbered in time-first order; and BD candidates of higher AL aggregates the BD candidates in time domain; H5includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in frequency domain; the AL1BD candidate is cluster of REGs based localized NR-PDCCH; the AL1BD candidates are numbered in time-first order; and BD candidates of higher AL aggregates the BD candidates in time domain; H6includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in frequency domain; the AL1BD candidate is cluster of REGs based distributed NR-PDCCH; the AL1BD candidates are numbered in time-first order; and BD candidates of higher AL aggregates the BD candidates in time domain; H7includes the AL1BD candidate is REG based localized NR-PDCCH; the AL1BD candidates are numbered in frequency-first order; and BD candidates of higher AL aggregates the BD candidates in frequency domain; H8includes the AL1BD candidate is REG based distributed NR-PDCCH; the AL1BD candidates are numbered in frequency-first order; and BD candidates of higher AL aggregates the BD candidates in frequency domain; H9includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in time domain; the AL1BD candidate is cluster of REGs based localized NR-PDCCH; the AL1BD candidates are numbered in frequency-first order; and BD candidates of higher AL aggregates the BD candidates in frequency domain; H10includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in time domain; the AL1BD candidate is cluster of REGs based distributed NR-PDCCH; the AL1BD candidates are numbered in frequency-first order; and BD candidates of higher AL aggregates the BD candidates in frequency domain; H11includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in frequency domain; the AL1BD candidate is cluster of REGs based localized NR-PDCCH; the AL1BD candidates are numbered in frequency-first order; and BD candidates of higher AL aggregates the BD candidates in frequency domain; H12includes the cluster of REGs is comprised of several, e.g., 2, consecutive REGs in frequency domain; the AL1BD candidate is cluster of REGs based distributed NR-PDCCH; the AL1BD candidates are numbered in frequency-first order; and BD candidates of higher AL aggregates the BD candidates in frequency domain.

Example 20 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-19, or any other method or process described herein.

Example 22 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-19, or any other method or process described herein.

Example 23 may include a method, technique, or process as described in or related to any of examples 1-19, or portions or parts thereof.

Example 25 may include a method of communicating in a wireless network as shown and described herein.

Example 26 may include a system for providing wireless communication as shown and described herein.

Example 27 may include a device for providing wireless communication as shown and described herein.

Example 28 may include an apparatus for a next generation NodeB (gNB), comprising first circuitry to determine a number of resource element groups (REGs) to be included in a resource element group bundle (REGB) for a new radio physical downlink control channel (NR-PDCCH), and generate a signal that indicates the number of the REGs, and second circuitry, coupled with the first circuitry, to encode the signal for transmission to a user equipment (UE).

Example 29 may include the apparatus of example 28 or any other example herein, wherein the first circuitry is further to determine a bundling direction for the REGs to be included in the REGB, wherein the signal further indicates the bundling direction.

Example 30 may include the apparatus of example 29 or any other example herein, wherein the bundling direction is a time-first order or a frequency-first order.

Example 31 may include the apparatus of any of examples 28-30 or any other example herein, wherein the first circuitry is further to determine whether a search space (SS) is to be configured in a localized manner, a distributed manner, or a hierarchical manner, wherein the signal further indicates that the SS is to be configured in the localized manner, the distributed manner, or the hierarchical manner based on the determination.

Example 32 may include the apparatus of example 31 or any other example herein, wherein the first circuitry is to determine that the SS is to be configured in the hierarchical manner, wherein the first circuitry is further to determine a hierarchical SS structure for the UE based on channel conditions associated with the UE or channel state information associated with the UE, wherein the signal further indicates the hierarchical SS structure.

Example 33 may include the apparatus of example 32 or any other example herein, wherein the hierarchical SS structure indicates whether the UE is to aggregate blind decoding (BD) candidates of the SS in the time domain or in the frequency domain.

Example 34 may include the apparatus of any of examples 28-30 or any other example herein, wherein the signal is to be transmitted via higher layer signaling.

Example 35 may include the apparatus of any of examples 28-30 or any other example herein, wherein the signal is to be transmitted via radio resource control (RRC) signaling.

Example 36 may include the apparatus of any of any of examples 28-30 or any other example herein, wherein the second circuitry comprises a baseband processor or encoding circuitry that is separate from the bascband proccssor.

Example 37 may include the apparatus of any of examples 28-30 or any other example herein, wherein the first circuitry is further to generate a transmission for transmission via the NR-PDCCH, and configure the transmission based on the number of the REGs to be included in the REGB for transmission via the NR-PDCCH, and the second circuitry is further to encode the transmission for transmission to the UE via the NR-PDCCH.

Exmple 38 may include an apparatus for a user equipment (UE), comprising first circuitry to identify an indication of a number of resource element groups (REGs) to be included in a resource element group bundle (REGB) for a new radio physical downlink control channel (NR-PDCCH), the indication received from a next generation NodeB (gNB), and determine a configuration of a search space (SS) of the UE based on the number of the REGs to be included in the REGB.

Example 39 may include the apparatus of example 38 or any other example herein, wherein the first circuitry is further to identify an indication of a bundling direction for the REGs to be included in the REGB, the indication of the bundling direction received from the gNB, and wherein the configuration of the SS is further determined based on the bundling direction.

Example 40 may include the apparatus of any of examples 38-39 or any other example herein, wherein the first circuitry is further to identify an indication of a localized manner, a distributed manner, or a hierarchical manner, the indication received from the gNB, and wherein the configuration of the SS is further determined based on the indication.

Exaple 41 may include the apparatus of example 40 or any other example herein, wherein the indication is of the hierarchical manner, wherein the first circuitry is further to identify an indication of a hierarchical SS structure for the UE, wherein the indication of the hierarchical SS structure is received from the gNB, and wherein the configuration of the SS is further determined based on the hierarchical SS structure.

Example 42 may include one or more computer-readable media having instructions stored thereon, wherein the instructions, in response to execution by a next generation NodeB (gNB), cause the gNB to determine whether a search space (SS) tor a user equipment (UE) is to be configured in a localized manner, a distributed manner, or a hierarchical manner, generate a signal that indicates that the SS is to be configured in the localized manner, the distributed manner, or the hierarchical manner based on the determination, and encode the signal for transmission to the UE.

Example 43 may include the one or more computer-readable media of example 42 or any other example herein, wherein the gNB is to determine that the SS for the UE is to be configured in the hierarchical manner, and wherein the instructions further cause the gNB to determine a hierarchical SS structure for the UE based on channel conditions associated with the UE or channel state information associated with the UE, wherein the signal further indicates the hierarchical SS structure.

Example 44 may include the one or more computer-readable media of example 43 or any other example herein, wherein the hierarchical SS structure indicates whether the UE is to aggregate blind decoding (BD) candidates of the SS in the time domain or in the frequency domain.

Example 45 may include the one or more computer-readable media of example 42 or any other example herein, wherein the instructions further cause the gNB to determine a numbering direction for blind decoding (BD) candidates of the SS, the numbering direction being a time-first order or a frequency-first order, and wherein the signal further indicates the numbering direction.

Example 46 may include the one or more computer-readable media of any of examples 42-45 or any other example herein, wherein the instructions further cause the gNB to determine a number of resource element groups (REGs) to be included in a resource element group bundle (REGB), and wherein the signal further indicates the number of the REGs.

Example 47 may include the one or more computer-readable media of example 46 or any other example herein, wherein the instructions further cause the gNB to determine a bundling direction for the REGs to be included in the REGB, and wherein the signal further indicates the bundling direction.

Example 48 may include the one or more computer-readable media of any of examples 42-45 or any other example herein, wherein the instructions further cause the gNB to transmit the signal via radio resource control (RRC) signaling.

Example 49 may include one or more computer-readable media having instructions stored thereon, wherein the instructions, in response to execution by a user equipment (UE), cause the UE to identify an indication of a localized manner, a distributed manner, or a hierarchical manner, the indication received from a next generation NodeB (gNB), and determine a configuration of a search space (SS) of the UE based on the indication.

Example 50 may include the one or more computer-readable media of example 49 or any other example herein, wherein the indication is of the hierarchical manner, wherein the instructions further cause the UE to identify an indication of a hierarchical SS structure, the indication of the hierarchical SS structure received from the gNB, and wherein the configuration of the SS is further determined based on the hierarchical SS structure.

Example 51 may include the one or more computer-readable media of example 50 or any other example herein, wherein the hierarchical SS structure indicates whether the UE is to aggregate blind decoding (BD) candidates of the SS in the time domain or the frequency domain.

Example 52 may include the one or more computer-readable media of example 49 or any other example herein, wherein the instructions further cause the UE to identify an indication of a numbering direction for blind decoding (BD) candidates of the SS, the indication of the numbering direction received from the gNB and the numbering direction being a time-first order or a frequency-first order, and wherein the configuration of the SS is further determined based on the numbering direction.

Example 53 may include the one or more computer-readable media of any of examples 49-52 or any other example herein, wherein the instructions further cause the UE to identify an indication of a number of resource element groups (REGs) to be included in a resource element group bundle (REGB), the indication of the number of the REGs received from the gNB, and wherein the configuration of the SS is further determined based on the number of the REGS.

Example 54 may include a method for a next generation NodeB (gNB), comprising determining a number of resource element groups (REGs) to be included in a resource element group bundle (REGB) for a new radio physical downlink control channel (NR-PDCCH), generating a signal that indicates the number of the REGs, and encoding the signal for transmission to a user equipment (UE).

Example 55 may include the method of example 54 or any other example herein, further comprising determining a bundling direction for the REGs to be included in the REGB, wherein the signal further indicates the bundling direction.

Example 56 may include the method of example 55 or any other example herein, wherein the bundling direction is a time-first order or a frequency-first order.

Example 57 may include the method of any of examples 54-56 or any other example herein, further comprising determining whether a search space (SS) is to be configured in a localized manner, a distributed manner, or a hierarchical manner, wherein the signal further indicates that the SS is to be configured in the localized manner, the distributed manner, or the hierarchical manner based on the determination.

Example 58 may include the method of example 57 or any other example herein, further comprising determining that the SS is to be configured in the hierarchical manner, and determining a hierarchical SS structure for the UE based on channel conditions associated with the UE or channel state information associated with the UE, wherein the signal further indicates the hierarchical SS structure.

Example 59 may include the method of example 58 or any other example herein, wherein the hierarchical SS structure indicates whether the UE is to aggregate blind decoding (BD) candidates of the SS in the time domain or in the frequency domain.

Example 60 may include the method of any of examples 54-56 or any other example herein, wherein the signal is to be transmitted via higher layer signaling.

Example 61 may include the method of any of examples 54-56 or any other example herein, wherein the signal is to be transmitted via radio resource control (RRC) signaling.

Example 62 may include the method of any of examples 54-56 or any other example herein, further comprising generating a transmission for transmission via the NR-PDCCH, configuring the transmission based on the number of the REGs to be included in the REGB for transmission via the NR-PDCCH, and encoding the transmission for transmission to the UE via the NR-PDCCH.

Exmple 63 may include an method for a user equipment (UE), comprising identifying an indication of a number of resource element groups (REGs) to be included in a resource element group bundle (REGB) for a new radio physical downlink control channel (NR-PDCCH), the indication received from a next generation NodeB (gNB), and determining a configuration of a search space (SS) of the UE based on the number of the REGs to be included in the REGB.

Example 64 may include the method of example 63 or any other example herein, further comprising identifying an indication of a bundling direction for the REGs to be included in the REGB, the indication of the bundling direction received from the gNB, and wherein the configuration of the SS is further determined based on the bundling direction.

Example 65 may include the method of any of examples 63-64 or any other example herein, further comprising identifying an indication of a localized manner, a distributed manner, or a hierarchical manner, the indication received from the gNB, and wherein the configuration of the SS is further determined based on the indication.

Exaple 66 may include the method of example 65 or any other example herein, wherein the indication is of the hierarchical manner, wherein the method further comprises identifying an indication of a hierarchical SS structure for the UE, wherein the indication of the hierarchical SS structure is received from the gNB, and wherein the configuration of the SS is further determined based on the hierarchical SS structure.

Example 67 may include a method comprising determining whether a search space (SS) for a user equipment (UE) is to be configured in a localized manner, a distributed manner, or a hierarchical manner, generating a signal that indicates that the SS is to be configured in the localized manner, the distributed manner, or the hierarchical manner based on the determination, and encoding the signal for transmission to the UE.

Example 68 may include the method of example 67 or any other example herein, further comprising determining that the SS for the UE is to be configured in the hierarchical manner, and determining a hierarchical SS structure for the UE based on channel conditions associated with the UE or channel state information associated with the UE, wherein the signal further indicates the hierarchical SS structure.

Example 69 may include the method of example 68 or any other example herein, wherein the hierarchical SS structure indicates whether the UE is to aggregate blind decoding (BD) candidates of the SS in the time domain or in the frequency domain. Example 70 may include the method of example 67 or any other example herein, further comprising determining a numbering direction for blind decoding (BD) candidates of the SS, the numbering direction being a time-first order or a frequency-first order, and wherein the signal further indicates the numbering direction.

Example 71 may include the method of any of examples 67-70 or any other example herein, further comprising determining a number of resource element groups (REGs) to be included in a resource element group bundle (REGB), and wherein the signal further indicates the number of the REGs.

Example 72 may include the method of example 71 or any other example herein, further comprising determining a bundling direction for the REGs to be included in the REGB, and wherein the signal further indicates the bundling direction.

Example 73 may include the method of any of examples 67-70 or any othcr example herein, further comprising transmitting the signal via radio resource control (RRC) signaling.

Example 74 may include a method, comprising identifying an indication of a localized manner, a distributed manner, or a hierarchical manner, the indication received from a next generation NodeB (gNB), and determining a configuration of a search space (SS) of the UE based on the indication.

Example 75 may include the method of example 74 or any other example herein, wherein the indication is of the hierarchical manner, wherein the method further comprises identifying an indication of a hierarchical SS structure, the indication of the hierarchical SS structure received from the gNB, and wherein the configuration of the SS is further determined based on the hierarchical SS structure.

Example 76 may include the method of example 75 or any other example herein, wherein the hierarchical SS structure indicates whether the UE is to aggregate blind decoding (BD) candidates of the SS in the time domain or the frequency domain.

Example 77 may include the method of example 74 or any other example herein, further comprising identifying an indication of a numbering direction for blind decoding (BD) candidates of the SS, the indication of the numbering direction received from the gNB and the numbering direction being a time-first order or a frequency-first order, and wherein the configuration of the SS is further determined based on the numbering direction.

Example 78 may include the method of any of examples 74-77 or any other example herein, further comprising identifying an indication of a number of resource element groups (REGs) to be included in a resource element group bundle (REGB), the indication of the number of the REGs received from the gNB, and wherein the configuration of the SS is further determined based on the number of the REGS.

Example 79 may include an apparatus to perform the method of any of examples 54-78.

Example 80 may include one or more means to perform the method of any of the examples 54-78.

Example 81 may include a one or more computer-readable media having instructions stored thereon, wherein the instructions, in response to execution by an apparatus, cause the apparatus to perform the method of any of the examples 54-78.