Patent Description:
The present disclosure is generally related to wireless communications and, more particularly, to optimization of distributed-tone resource unit (dRU) and distributed-tone multi-resource unit (dMRU) designs for transmission in a <NUM> low-power indoor (LPI) system.

Under current regulations by the Federal Communications Commission (FCC) regarding wireless communications in the <NUM> and <NUM> bands, the equivalent isotropically radiated power (EIRP) of a power spectral density (PSD) limit is capped at <NUM> dBm for <NUM> transmission and the transmission (Tx) power limit is capped at <NUM> dBm. With a reasonable Tx power assumption, the FCC requirement would not limit Tx power for narrow-bandwidth transmissions. On the other hand, the FCC requirement regarding <NUM> LPI applications is far more stringent than PSD requirement for the <NUM> and <NUM> bands. For instance, the EIRP limit is at <NUM> dBm/MHz for an access point (AP) station (STA) in <NUM> LPI versus an EIRP limit of <NUM> dBm/MHz for APs in the <NUM> band. Similarly, the EIRP limit is at -<NUM> dBm/MHz for a non-AP STA in <NUM> LPI versus an EIRP limit of <NUM> dBm/MHz for APs in the <NUM> band.

Distributed-tone RUs (dRUs) and distributed-tone multi-RUs (dMRUs) have been proposed to spread subcarriers or tones over a wider bandwidth to boost transmit power and extend coverage range. However, how the subcarriers or tones are distributed in constructing dRUs of different sizes in an optimized way have yet to be defined. Therefore, there is a need for a solution for optimization of dRU/dMRU designs for transmission in a <NUM> LPI system.

The following documents constitute relevant prior art under Article <NUM>(<NUM>) EPC: <CIT> and <CIT>. And the following documents constitute prior art under Article <NUM>(<NUM>) EPC: <CIT>, <CIT>, and <CIT>.

The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

An objective of the present disclosure is to provide schemes, concepts, designs, techniques, methods and apparatuses pertaining to optimization of dRU/dMRU designs for transmission in a <NUM> LPI system. A method according to the invention is defined in independent claim <NUM>. Dependent claim <NUM> defines a preferred embodiment thereof. An apparatus according to the invention is defined in dependent claim <NUM>.

In one aspect that is not according to the present invention, a method may involve distributing a plurality of subcarriers of a RU to generate a dRU or a distributed-tone multi-RU (dMRU) on an <NUM> frequency segment or subblock. The method may also involve communicating with a communication entity using the dRU or the dMRU.

In yet another aspect that is not according to the present invention, an apparatus may include a transceiver configured to transmit and receive wirelessly. The apparatus may also include a processor coupled to the transceiver. The processor may distribute a plurality of subcarriers of RU to generate a dRU or a dMRU on an <NUM> frequency segment or subblock. The processor may also communicate, via the transceiver, with a communication entity (e.g., an AP STA or non-AP STA) using the dRU or the dMRU.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as, Wi-Fi, the proposed concepts, schemes and any variation(s)/derivative(s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, Bluetooth, ZigBee, 5th Generation (<NUM>)/New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT), Industrial loT (IIoT) and narrowband loT (NB-loT). Thus, the scope of the present disclosure is not limited to the examples described herein.

In the following, each of the described examples, designs, schemes and implementations is according to the present invention when it refers to a distributed resource unit (dRU) having a tone distribution pattern that is generated according to the formula disclosed in paragraph <NUM>, and comprising a <NUM>-tone dRU shown in <FIG>, and is not according to the present invention otherwise.

Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to optimization of dRU/dMRU designs for transmission in a <NUM> LPI system. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

It is noteworthy that, in the present disclosure, a <NUM>-tone regular RU (rRU) may be interchangeably denoted as RU26 (or rRU26), a <NUM>-tone regular RU may be interchangeably denoted as RU52 (or rRU52), a <NUM>-tone regular RU may be interchangeably denoted as RU106 (or rRU106), a <NUM>-tone regular RU may be interchangeably denoted as RU242 (or rRU242), and so on. Moreover, an aggregate (<NUM>+<NUM>)-tone regular multi-RU (MRU) may be interchangeably denoted as MRU78 (or rMRU78), an aggregate (<NUM>+<NUM>)-tone regular MRU may be interchangeably denoted as MRU132 (or rMRU132), and so on. Furthermore, in the present disclosure, a <NUM>-tone distributed-tone RU may be interchangeably denoted as dRU26, a <NUM>-tone distributed-tone RU may be interchangeably denoted as dRU52, a <NUM>-tone distributed-tone RU may be interchangeably denoted as dRU106, a <NUM>-tone distributed-tone RU may be interchangeably denoted as dRU242, and so on. Additionally, an aggregate (<NUM>+<NUM>)-tone distributed-tone MRU may be interchangeably denoted as dMRU78, an aggregate (<NUM>+<NUM>)-tone distributed-tone MRU may be interchangeably denoted as dMRU132, and so on. Since the above examples are merely illustrative examples and not an exhaustive listing of all possibilities, the same applies to regular RUs, distributed-tone RUs, MRUs, and distributed-tone MRUs of different sizes (or different number of tones). It is also noteworthy that, in the present disclosure, a bandwidth of <NUM> may be interchangeably denoted as BW20 or BW20M, a bandwidth of <NUM> may be interchangeably denoted as BW40 or BW40M, a bandwidth of <NUM> may be interchangeably denoted as BW80 or BW80M, a bandwidth of <NUM> may be interchangeably denoted as BW160 or BW160M, a bandwidth of <NUM> may be interchangeably denoted as BW240 or BW240M, and a bandwidth of <NUM> may be interchangeably denoted as BW320 or BW320M. It is further noteworthy that, in the present disclosure, a <NUM>-tone interleaved-tone or interlaced-tone RU may be interchangeably denoted as iRU26, a <NUM>-tone interleaved-tone or interlaced-tone RU may be interchangeably denoted as iRU52, a <NUM>-tone interleaved-tone or interlaced-tone RU may be interchangeably denoted as iRU106, a <NUM>-tone interleaved-tone or interlaced-tone RU may be interchangeably denoted as iRU242, and a <NUM>-tone interleaved-tone or interlaced-tone RU may be interchangeably denoted as iRU484. Additionally, the term "frequency segment" is interchangeably referred to as "frequency subblock" herein. Furthermore, for simplicity in notation, the term "dRU" herein may represent both dRU and dMRU.

Referring to <FIG>, network environment <NUM> may involve a communication entity <NUM> and a communication entity <NUM> communicating wirelessly (e.g., in a wireless local area network (WLAN) in accordance with one or more Institute of Electrical and Electronics Engineers (IEEE) <NUM> standards). For instance, communication entity <NUM> may be a first STA and communication entity <NUM> may be a second STA, with each of the first STA and second STA functioning as either an AP STA or a non-AP STA. Under various proposed schemes in accordance with the present disclosure, communication entity <NUM> and communication entity <NUM> may be configured to communicate wirelessly with optimization of dRU/dMRU designs for transmission in a <NUM> LPI system under various proposed schemes of the present disclosure, as described herein.

Under various proposed schemes in accordance with the present disclosure, a <NUM>-tone dRU (or dRU26) may be used as a basic building block to generate or otherwise construct dRUs and dMRUs of different sizes based on a similar hierarchical structure as that for regular RUs (rRUs). For instance, one <NUM>-tone dRU (or dRU52) may be built from two <NUM>-tone dRUs, one <NUM>-tone dRU (or dRU106) may be built from two <NUM>-tone dRUs (or four <NUM>-tone dRUs plus two extra tones), one <NUM>-tone dRU may be built from two <NUM>-tone dRUs and one <NUM>-tone dRU plus four extra tones (or nine <NUM>-tone dRUs plus eight extra tones, and so on), one <NUM>-tone dRU may be built from two <NUM>-tone dRUs.

In the present disclosure, Np denotes a periodicity or repetition period (e.g., in number of tones). Under the various proposed schemes, the aforementioned dRU design may be updated or further optimized. For instance, Np = <NUM> may be extended to Np = <NUM> with several different options for the tone distribution pattern. Additionally, the tone distribution pattern may be optimized with Np = <NUM> to achieve optimal power boost gain for dRUs and dMRUs of all sizes. Moreover, the table of dRU subcarrier indices for Np = <NUM> is proposed herein for each option of tone distribution pattern with different tone-alignment methods such as, for example and without limitation, an edge-aligned and direct current (DC)-symmetric tone distribution pattern or a center-aligned and DC-symmetric tone distribution pattern. Furthermore, tables of dRU subcarrier indices are updated under the various proposed schemes.

<FIG> illustrates an example design <NUM> with respect to logical RU indices for BW80 in accordance with the present disclosure. In design <NUM>, for consistency with labeling of regular RU indices, the <NUM>-tone RU index <NUM> may be also assumed as "not defined" for a <NUM>-tone dRU. Moreover, according to the invention, given a distribution bandwidth and a logical RU size, the tone distribution pattern of a dRU is generated based on a formula as follows: <MAT>.

Here, Np denotes a periodicity or repetition period (e.g., in number of tones); l(i) denotes a tone distribution pattern within one repetition period (e.g., every two or three tones, and so on); i = mod(k, L) = <NUM>, <NUM>, <NUM>,. , L - <NUM>; j = <NUM>, <NUM>, <NUM>,. , <MAT> ; k = <NUM>, <NUM>, <NUM>,. , Nst_ru - <NUM>; r = <NUM>, <NUM>,. , Nru, with r being the logical RU index. Moreover, l(i) ∈ Ωru = { l(<NUM>), l(<NUM>),. , I(L-<NUM>)}; L = | Ωru | ; Nst_ru = <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> for RU26, RU52, RU106, RU242, RU484, RU996, respectively. Additionally, RUstart(r) represents the first or starting tone index for dRUr; l(i) represents the tones within one repetition distance or one repetition period; Np represents the repetition distance or repetition period; L represents the number of tones within one repetition distance or one repetition period; Nst_ru represents the number of subcarriers (or tones) for a dRU; and Nru represents the number of dRUs for a given dRU size in a given bandwidth.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme (Option <NUM>) in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstart(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52, dRU106, dRU242 and dRU484) with Np = <NUM> on BW80 under design <NUM>. It is believed that design <NUM> may achieve optimal power boost gains for all dRUs/dMRUs and that each dRU/dMRU may have a repeatable pattern. It is noteworthy that RUstart(r) for dRU26 may also be calculated as mod(<NUM>:<NUM>:<NUM>*<NUM>-<NUM>,<NUM>). Also, for simplicity in notation, RUstart(r) for dRU26 may be with logical RU index r = <NUM>, <NUM>,. In case that r = <NUM> is considered the "reserved" or "not defined" index, then RUstart(r) = {<NUM>,<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, NA, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} by inserting some value like "NA" or "-<NUM>" or others to reserve that position. This may be applied to other tables in various designs in accordance with the present disclosure. The tone distribution patterns of dRU52, dRU106 and dRU242 with Np = <NUM> on BW80 are shown in parts (A), (B) and (C) of <FIG>, respectively.

Under the proposed scheme, the formula and parameters described above may be utilized to define the fundamental rules and methods for generation of dRU subcarrier indices. Based on the proposed design rules and parameters, there may be several alternative ways to represent the dRU subcarrier indices. In a first alternative way, dRU(r,k) = Ω(Ktd(r,k)), where Ω denotes the tone mapping range which may be predefined. For instance, Ω = [-<NUM>:-<NUM>, <NUM>:<NUM>] or [-<NUM>:-<NUM>, <NUM>: <NUM>] or [-<NUM>:-<NUM>, <NUM>:<NUM>] for dRU on BW20; Ω = [-<NUM>:-<NUM>, <NUM>:<NUM>] or [-<NUM>:-<NUM>, <NUM>:<NUM>] or others for dRU on BW40; Ω = [-<NUM>:-<NUM>, <NUM>:<NUM>] or [-<NUM>:-<NUM>, <NUM>:<NUM>] or others for dRU on BW80. Moreover, Ktd(r,k) may be calculated by using formula and parameters described above, with r being the dRU index and k being the dRU natural subcarrier orders, k = <NUM>, <NUM>,. , Nst - <NUM>.

In a second alternative way, Ktd = Ktd + Nguard,left, with Nguard,left = <NUM> for BW20 and Nguard,left = <NUM> for BW40, BW80 and BW160, Nguard,left denotes the number of guard tones on the left side of the tone distribution pattern. Moreover: <MAT>.

Here, NDC = <NUM> for BW20 and NDC = <NUM> for BW40, BW80 and BW160, and NDC denotes the number of DC tones. Then, Ktd = Ktd - (Nfft / <NUM> + <NUM>) to map the positive integer numbers to the frequency-domain tone index.

In a third alternative way, similar to regular RU, the dRU subcarrier indices may be generated and represented as shown in <FIG>.

Under the proposed scheme, with respect to the dMRU of <NUM>-tone dMRU(<NUM>+<NUM>) and <NUM>-tone dMRU(<NUM>+<NUM>), the distribution tone indices for dMRU78 may include corresponding dRU26 and dRU52 distribution subcarrier indices, and the distribution tone indices for dMRU132 may include corresponding dRU26 and dRU106 distribution subcarrier indices.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is edge-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> extremely-high-throughput (EHT) trigger-based (TB) physical-layer protocol data unit (PPDU) for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is edge-aligned but DC-asymmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is center-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is center-aligned but DC-asymmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme (Option <NUM>) in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstart(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52, dRU106, dRU242 and dRU484) with Np = <NUM> on BW80 under design <NUM>. It is believed that design <NUM> may achieve optimal power boost gains for all dRUs/dMRUs (except for dMRU132), that each dRU/dMRU may have a repeatable pattern, and that dRU242 and dRU484 may be uniformly distributed. Part (A) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. Part (B) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is not supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. The tone distribution patterns of dRU52, dRU106, dRU242 and dRU484 with Np = <NUM> on BW80 are shown in parts (A), (B), (C) and (D) of <FIG>, respectively. In the tone distribution patterns of dRU52 and dRU106, the four right-most columns may correspond to the subcarrier indices of four middle dRU26. It is noteworthy that the same procedures described above with respect to Option <NUM> may be followed to generate the dRU subcarrier indices table for the tone distribution pattern under Option <NUM>.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme (Option <NUM>) in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstart(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52, dRU106, dRU242 and dRU484) with Np = <NUM> on BW80 under design <NUM>. It is believed that design <NUM> may achieve optimal power boost gains for all dRUs/dMRUs (except for dMRU132) and that each dRU/dMRU may have a repeatable pattern. Moreover, dRU242 may have two distribution patterns and dRU484 may have one distribution pattern. Part (A) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. Part (B) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is not supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. The tone distribution patterns of dRU52, dRU106, dRU242 and dRU484 with Np = <NUM> on BW80 are shown in parts (A), (B), (C) and (D) of <FIG>, respectively. In the tone distribution patterns of dRU52 and dRU106, the encircled two middle columns and the two right-most columns may correspond to the subcarrier indices of four middle dRU26. It is noteworthy that the same procedures described above with respect to Option <NUM> may be followed to generate the dRU subcarrier indices table for the tone distribution pattern under Option <NUM>.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme (Option <NUM>) in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstary(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52, dRU106, dRU242 and dRU484) with Np = <NUM> on BW80 under design <NUM>. It is believed that design <NUM> may achieve optimal power boost gains for all dRUs/dMRUs (except for dMRU132), that each dRU/dMRU may have a repeatable pattern, and that dRU242 and dRU484 may have different distribution patterns. Part (A) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. Part (B) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is not supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. The tone distribution patterns of dRU52, dRU106, dRU242 and dRU484 with Np = <NUM> on BW80 are shown in parts (A), (B), (C) and (D) of <FIG>, respectively. In the tone distribution patterns of dRU52 and dRU106, four encircled individual columns may correspond to the subcarrier indices of four middle dRU26. It is noteworthy that the same procedures described above with respect to Option <NUM> may be followed to generate the dRU subcarrier indices table for the tone distribution pattern under Option <NUM>.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme (Option <NUM>) in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstary(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52, dRU106, dRU242 and dRU484) with Np = <NUM> on BW80 under design <NUM>. It is believed that design <NUM> may achieve optimal power boost gains for all dRUs/dMRUs (except for dMRU132), that each dRU/dMRU may have a repeatable pattern, and that dRU242 and dRU484 may have different distribution patterns. Part (A) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. Part (B) of <FIG> shows one aspect of design <NUM> that may be implemented when dRU484 is not supported, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. The tone distribution patterns of dRU52, dRU106, dRU242 and dRU484 with Np = <NUM> on BW80 are shown in parts (A), (B), (C) and (D) of <FIG>, respectively. In the tone distribution patterns of dRU52 and dRU106, four encircled individual columns may correspond to the subcarrier indices of four middle dRU26.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is edge-aligned and DC-symmetric, with Np = <NUM>, in which <NUM>-tone and <NUM>-tone dRUs subcarrier indices are represented in <NUM>-tone dRU subcarrier indices based on the dRU hierarchical structure, for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is edge-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is edge-aligned but DC-asymmetric, with Np = <NUM>, in which <NUM>-tone and <NUM>-tone dRUs subcarrier indices are represented in <NUM>-tone dRU subcarrier indices based on the dRU hierarchical structure , for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is center-aligned and DC-symmetric, with Np = <NUM>, in which <NUM>-tone and <NUM>-tone dRUs subcarrier indices are represented in <NUM>-tone dRU subcarrier indices based on the dRU hierarchical structure, for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under Option <NUM> in accordance with the present disclosure. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is center-aligned but DC-asymmetric, with Np = <NUM>, in which <NUM>-tone and <NUM>-tone dRUs subcarrier indices are represented in <NUM>-tone dRU subcarrier indices based on the dRU hierarchical structure for dRUs of different sizes in an <NUM> EHT TB PPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstary(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52, dRU106, dRU242 and dRU484) with Np = <NUM> and V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>] on BW80 under design <NUM>. It is believed that design <NUM> may achieve optimal power boost gains for all dRUs/dMRUs and that each dRU/dMRU may have a repeatable pattern. Moreover, same-size dRU (e.g., dRU26/<NUM>/<NUM>/<NUM>/<NUM>) may have the same tone distribution pattern. The tone distribution patterns of dRU52, dRU106, dRU242 and dRU484 with Np = <NUM> on BW80 are shown in parts (A), (B), (C) and (D) of <FIG>, respectively.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under the proposed scheme described above with respect to design <NUM>. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is edge-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TBPPDU for <NUM> LPI.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under the proposed scheme described above with respect to design <NUM>. More specifically, subcarrier indices in the table shown in <FIG> and <FIG> may be generated with a tone distribution pattern that is center-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TBPPDU for <NUM> LPI.

Under certain proposed schemes in accordance with the present disclosure, for BW80, the dRU subcarrier indices table may be generated for dRU/dMRU over an orthogonal frequency-division multiple-access (OFDMA) tone plan based on the optimized dRU designs described above. For BW40, the dRU subcarrier indices table may be updated. For BW20, the dRU subcarrier indices table may be updated and, additionally, alternative dRU design parameters may be utilized and the dRU subcarrier indices tables may be generated according to proposed schemes described below. It is noteworthy that, in the dRU subcarrier indices tables, four <NUM>-tone dRUs may be equivalent to two <NUM>-tone dRUs (e.g., <NUM>-tone dRU1 ~ dRU4 may be deemed to be the same as <NUM>-tone dRU1 ~ dRU2, <NUM>-tone dRU6 ~ dRU9 may be deemed to be the same as <NUM>-tone dRU3 ~ dRU4, and so on. Thus, the dRU subcarrier indices for <NUM>-tone dRUs may be represented either in four <NUM>-tone dRUs or two <NUM>-tone dRUs with two extra tones.

<FIG> illustrates an example design <NUM> under a proposed scheme in accordance with the present disclosure. For BW80 in IEEE <NUM>. 11be, the tone distribution range for an OFDMA tone plan range may be [-<NUM>:-<NUM>, -<NUM>:-<NUM>, <NUM>:<NUM>, <NUM>:<NUM>], and [-<NUM>:-<NUM>, -<NUM>:<NUM>, <NUM>:<NUM>] may be considered as null subcarriers or DC tones. Additionally, the tone distribution range for a non-OFDMA tone plan or <NUM>-tone RU tone plan for BW80 in IEEE <NUM>. 11be may be [-<NUM>:-<NUM>, <NUM>:<NUM>], and five tones of [-<NUM>:<NUM>] may be used for DC tones. As mentioned above, dRU subcarrier indices tables for BW80 may be generated for dRU distributed over a non-OFDMA tone plan. Under the proposed schemes described below, the optimal dRU designs (Options <NUM> ~ <NUM>) with Np = <NUM> may distribute tones over either an OFDMA tone plan or non-OFDMA tone plan, and dRU subcarrier indices table may be generated accordingly.

<FIG>, <FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. More specifically, subcarrier indices in the table shown in <FIG>, <FIG> and <FIG> may be generated with an OFDMA tone distribution pattern that is edge-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TBPPDU for <NUM> LPI.

<FIG>, <FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. More specifically, subcarrier indices in the table shown in <FIG>, <FIG> and <FIG> may be generated with an OFDMA tone distribution pattern that is center-aligned and DC-symmetric, with Np = <NUM>, for dRUs of different sizes in an <NUM> EHT TBPPDU for <NUM> LPI.

<FIG> illustrates an example scenario <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. More specifically, scenario <NUM> shows tone distribution of dRU242 on BW80 with a non-OFDMA tone plan that is center-aligned and DC-symmetric, with Np = <NUM>.

<FIG> illustrates an example scenario <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. More specifically, scenario <NUM> shows a tone distribution of dRU242 on BW80 with an OFDMA tone plan that is center-aligned and DC-symmetric, with Np = <NUM>.

<FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. In particular, <FIG> illustrates an updated dRU data and pilot subcarrier indices table for BW40 with a tone distribution pattern that is center-aligned and DC-symmetric. Moreover, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW40 with a tone distribution pattern that is center-aligned and DC-symmetric.

<FIG>, <FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. In particular, <FIG> illustrates an updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is center-aligned and DC-symmetric, and more DC tones (e.g., seven DC tones) are reserved. Moreover, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is center-aligned and DC-symmetric, and more DC tones (e.g., five DC tones) are reserved. Furthermore, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is edge-aligned and DC-symmetric with a first left tone = -<NUM> and five DC tones.

<FIG> and <FIG> each illustrates a respective portion of an example design <NUM> under a proposed scheme in accordance with the present disclosure. <FIG> shows a table listing the parameters RUstary(r) and l(i) for dRUs of different sizes (e.g., dRU26, dRU52 and dRU106) with Np = <NUM> on BW20 under design <NUM>. The tone distribution patterns of dRU26, dRU52 and dRU106 on BW20 are shown in parts (A), (B) and (C) of <FIG>, respectively.

<FIG>, <FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. In particular, <FIG> illustrates an updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is edge-aligned and DC-symmetric with a first left tone = -<NUM> and three DC tones. Moreover, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is edge-aligned and DC-symmetric with a first left tone = -<NUM> and five DC tones. Furthermore, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is edge-aligned and DC-symmetric with a first left tone = -<NUM> and seven DC tones.

<FIG>, <FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. In particular, <FIG> illustrates an updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is center-aligned and DC-symmetric with three DC tones. Moreover, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is center-aligned and DC-symmetric with five DC tones. Furthermore, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is center-aligned and DC-symmetric with seven DC tones.

<FIG> and <FIG> each illustrates a diagram of a respective portion of an example design <NUM> under a proposed scheme in accordance with an implementation of the present disclosure. In particular, <FIG> illustrates an updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is edge-aligned and DC-symmetric with a first left tone = -<NUM> and three DC tones. Moreover, <FIG> illustrates another updated dRU data and pilot subcarrier indices table for BW20 with a tone distribution pattern that is center-aligned and DC-symmetric with three DC tones.

<FIG> illustrates an example system <NUM> having at least an example apparatus <NUM> and an example apparatus <NUM> in accordance with an implementation of the present disclosure. Each of apparatus <NUM> and apparatus <NUM> may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to optimization of dRU/dMRU designs for transmission in a <NUM> LPI system, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above as well as processes described below. For instance, apparatus <NUM> may be an example implementation of communication entity <NUM>, and apparatus <NUM> may be an example implementation of communication entity <NUM>.

Each of apparatus <NUM> and apparatus <NUM> may be a part of an electronic apparatus, which may be a STA or an AP, such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus <NUM> and apparatus <NUM> may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus <NUM> and apparatus <NUM> may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, each of apparatus <NUM> and apparatus <NUM> may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus <NUM> and/or apparatus <NUM> may be implemented in a network node, such as an AP in a WLAN.

In some implementations, each of apparatus <NUM> and apparatus <NUM> may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. In the various schemes described above, each of apparatus <NUM> and apparatus <NUM> may be implemented in or as a STA or an AP. Each of apparatus <NUM> and apparatus <NUM> may include at least some of those components shown in <FIG> such as a processor <NUM> and a processor <NUM>, respectively, for example. Each of apparatus <NUM> and apparatus <NUM> may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device), and, thus, such component(s) of apparatus <NUM> and apparatus <NUM> are neither shown in <FIG> nor described below in the interest of simplicity and brevity.

In one aspect, each of processor <NUM> and processor <NUM> may be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors or one or more CISC processors. That is, even though a singular term "a processor" is used herein to refer to processor <NUM> and processor <NUM>, each of processor <NUM> and processor <NUM> may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor <NUM> and processor <NUM> may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor <NUM> and processor <NUM> is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including those pertaining to optimization of dRU/dMRU designs for transmission in a <NUM> LPI system in accordance with various implementations of the present disclosure. For instance, each of processor <NUM> and processor <NUM> may be configured with hardware components, or circuitry, implementing one, some or all of the examples described and illustrated herein.

In some implementations, apparatus <NUM> may also include a transceiver <NUM> coupled to processor <NUM>. Transceiver <NUM> may be capable of wirelessly transmitting and receiving data. In some implementations, apparatus <NUM> may also include a transceiver <NUM> coupled to processor <NUM>. Transceiver <NUM> may include a transceiver capable of wirelessly transmitting and receiving data.

Each of apparatus <NUM> and apparatus <NUM> may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus <NUM>, as communication entity <NUM>, and apparatus <NUM>, as communication entity <NUM>, is provided below. It is noteworthy that, although the example implementations described below are provided in the context of WLAN, the same may be implemented in other types of networks. Thus, although the following description of example implementations pertains to a scenario in which apparatus <NUM> functions as a transmitting device and apparatus <NUM> functions as a receiving device, the same is also applicable to another scenario in which apparatus <NUM> functions as a receiving device and apparatus <NUM> functions as a transmitting device.

Under a proposed scheme in accordance with the present disclosure with respect to optimization of dRU/dMRU designs for transmission in a <NUM> LPI system, processor <NUM> of apparatus <NUM> may distribute a plurality of subcarriers of a RU to generate a dRU or a dMRU on an <NUM> frequency segment or subblock. Moreover, processor <NUM> may communicate, via transceiver <NUM>, with a communication entity (e.g., apparatus <NUM>) using the dRU or the dMRU.

In some implementations, a repetition period of a plurality of tones of the dRU or the dMRU may be <NUM>. In such a case, the plurality of tones of the dRU or the dMRU may be distributed over ether an OFDMA tone plan or a non-OFDMA tone plan. Alternatively, the repetition period of the plurality of tones of the dRU or the dMRU may be <NUM>. In such a case, the plurality of tones of the dRU or the dMRU may be distributed over a non-OFDMA tone plan.

In some implementations, the dRU or the dMRU may be generated based on a subcarrier indices table with parameters RUstary(r) and l(i). In such a case, RUstart(r) may denote a first or starting tone index for the dRU or the dMRU; l(i) may denote one or more tones of the dRU or the dMRU within one repetition distance or one repetition period; r may denote a dRU index; i = mod(k, L) = <NUM>, <NUM>, <NUM>,. , L - <NUM>; k = <NUM>, <NUM>,. , Nst - <NUM>; L may denote a number of tones of the dRU or the dMRU within one repetition distance or one repetition period; and Nst may denote a number of subcarriers associated with the dRU or the dMRU.

In some implementations, a <NUM>-tone dRU may be supported in the subcarrier indices table. In some implementations, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {V, V+<NUM>} and the l(i) = {<NUM>}, with V = [<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>]. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>}. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>}. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>:<NUM>:<NUM>}. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>} and the l(i) = {<NUM>:<NUM>:<NUM>}.

In some implementations, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>}. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>} for dRU1, dRU4, dRU5, dRU7, dRU9, dRU10, dRU11, dRU12, dRU14, dRU15 and dRU16 or /(i) = {<NUM>, <NUM>} for dRU2, dRU3, dRU6, dRU8 and dRU13. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for dRU1, dRU3 and dRU4, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for dRU2 and dRU7, or l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for dRU5, dRU6 and dRU8. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU1, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU2, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU3, or l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU4. Still alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU1, or l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU2.

In some implementations, a tone distribution pattern of the dRU or the dMRU may be center-aligned and DC-symmetric. Alternatively, the tone distribution pattern of the dRU or the dMRU may be center-aligned and DC-asymmetric. Alternatively, the tone distribution pattern of the dRU or the dMRU may be edge-aligned and DC-symmetric. Still alternatively, the tone distribution pattern of the dRU or the dMRU may be edge-aligned and DC-asymmetric.

<FIG> illustrates an example process <NUM> in accordance with an implementation of the present disclosure. Process <NUM> may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process <NUM> may represent an aspect of the proposed concepts and schemes pertaining to optimization of dRU/dMRU designs for transmission in a <NUM> LPI system in accordance with the present disclosure. Process <NUM> may include one or more operations, actions, or functions as illustrated by one or more of blocks <NUM> and <NUM>. Although illustrated as discrete blocks, various blocks of process <NUM> may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process <NUM> may be executed in the order shown in <FIG> or, alternatively in a different order. Furthermore, one or more of the blocks/sub-blocks of process <NUM> may be executed repeatedly or iteratively. Process <NUM> may be implemented by or in apparatus <NUM> and apparatus <NUM> as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process <NUM> is described below in the context of apparatus <NUM> as communication entity <NUM> (e.g., a transmitting device whether a STA or an AP) and apparatus <NUM> as communication entity <NUM> (e.g., a receiving device whether a STA or an AP) of a wireless network such as a WLAN in accordance with one or more of IEEE <NUM> standards. Process <NUM> may begin at block <NUM>.

At <NUM>, process <NUM> may involve processor <NUM> of apparatus <NUM> distributing a plurality of subcarriers of a RU to generate a dRU or a dMRU on an <NUM> frequency segment or subblock. Process <NUM> may proceed from <NUM> to <NUM>.

At <NUM>, process <NUM> may involve processor <NUM> communicating, via transceiver <NUM>, with a communication entity (e.g., apparatus <NUM>) using the dRU or the dMRU.

In some implementations, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>}. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>} for dRU1, dRU4, dRU5, dRU7, dRU9, dRU10, dRU11, dRU12, dRU14, dRU15 and dRU16 or l(i) = {<NUM>, <NUM>} for dRU2, dRU3, dRU6, dRU8 and dRU13. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for dRU1, dRU3 and dRU4, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for dRU2 and dRU7, or l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for dRU5, dRU6 and dRU8. Alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU1, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU2, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU3, or l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU4. Still alternatively, the dRU may include a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU1, or l(i) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} for dRU2.

Claim 1:
A method, comprising:
distributing a plurality of subcarriers of a resource unit, RU, to generate a distributed-tone RU, dRU, on an <NUM> frequency segment or subblock (<NUM>); and
communicating with a communication entity using the dRU (<NUM>);
characterized in that
the dRU is generated based on a tone indices table generated with a tone distribution pattern Ktd(r, k) of the dRU based on a formula as follows: <MAT>
wherein RUstart(r) denotes a first or starting tone index for the dRU,
Np denotes a repetition period of a plurality of tones of the dRU,
l(i) denotes a tone distribution pattern within one repetition period,
r denotes a logical RU index,
i = mod(k, L) = <NUM>, <NUM>, <NUM>, ..., L - <NUM>,
k = <NUM>, <NUM>, ..., Nst - <NUM>,
L denotes a number of tones within one repetition period,
Nst denotes a number of tones associated with the dRU, and
j = <NUM>, <NUM>, <NUM>, ..., | Nst/L | - <NUM>,
wherein the dRU comprises a <NUM>-tone dRU with the RUstart(r) = {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} and the l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for the logical RU index being equal to <NUM>, <NUM> or <NUM>, l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for the logical RU index being equal to <NUM> or <NUM>, and l(i) = {<NUM>, <NUM>, <NUM>, <NUM>} for the logical RU index being equal to <NUM>, <NUM> or <NUM>.