Re: [STDS-802-11-TGBE] about the spec. text on DCM and DCM+DUP

[Edward Au <edward.ks.au@xxxxxxxxx>]

Hello Jianhan,

Thanks for bringing out this issue.  

For SFD:  actually, there are quite a number of motions in the SFD that are potentially conflict or overlapped with one another, especially on the PHY.    It would be great if members would prepare a submission to clean up these conflicts/overlaps.

For D0.1,  as per Chair's guidance, we need to prepare PDT text or PDT-TBD text to resolve any missing or incorrect text.  Some of the motions you identified below are (partially) covered by the PDT-TBD texts prepared by Bin and Wook Bong (e.g., 20/1783r0, 20/1793r0).   May I know if you or other members would prepare a submission?

Regards,

Edward

On Wed, Nov 11, 2020 at 10:43 AM Jianhan Liu <jianhanliu@xxxxxxxxx> wrote:

Hi Edward, 

In the current draft 11be 0.1, there are no or incorrect text to reflect the passed motions related to DCM and DCm+DUP (as follows).

I am wondering about the plan for the spec. text of these motions. 

Thanks,

Jianhan

The following MCSs are defined:

·       MCS14: BPSK + ½ rate coding + DCM + Dup

·       MCS15: BPSK + ½ rate coding + DCM

NOTE – These MCSs are only applicable to Nss = 1. 

[Motion 137, #SP250, [3] and [56]]

 

The followings are the requirements to support DCM+MCS0:

·       Mandatory in

o   RU 26, 52, 106, and 242 for 20 MHz-only STAs.

o   RU 26, 52, 106, 242, 484, and 996 for non 20 MHz-only STAs.

·       Conditional mandatory in 

o   RU 2×996 when STA supports 160 MHz

o   RU 2×996 and 4×996 when STA supports 320 MHz

·       Optional in

o   MRU 52+26, 106+26, 484+242, 996+484, 996+484+242, and 3×996

·       Not supported in

o   MRU 2×996+484, 3×996+484

[Motion 137, #SP279, [3] and [42]]

 

802.11be agrees to define a DUP mode for non-punctured 80 MHz, 160 MHz and 320 MHz PPDUs transmitted to a single user, limited to {MCS0+DCM, Nss=1}.

·       80 DUP = 40 (RU 484) duplicated.

·       160 DUP = 80 (RU 996) duplicated.

·       320 DUP = 160 (RU 2×996) duplicated.

·       PAPR reduction scheme is TBD.

·       Additional diversity scheme is TBD.

·       This is an R1 feature.

The mode defined above is limited to 6 GHz.

·       NOTE – Whether to further limit this to LPI mode is TBD.

The duplication in the mode defined above is done only on the data tones of the payload portion and that EHT-STF/LTF are based on the total BW.

In this mode,

·       For 80 MHz PPDU, the EHT-STF, EHT-LTF and pilot are same as transmitting both RU1 and RU2 of 484-tone RU.

·       For 160/320 MHz PPDU, the EHT-STF, EHT-LTF and pilot are same as the non-OFDMA 160/320 MHz PPDU.

PAPR reduction scheme is TBD.

NOTE – pre-EHT modulated fields are TBD.

[Motion 122, #SP162, [12] and [57]]

[Motion 122, #SP163, [12] and [57]]

[Motion 122, #SP170, [12] and [58]]

 

The optional Dup+DCM mode for 6 GHz band LPI channel is supported. 

[Motion 137, #SP280, [3] and [42]]

 

The PAPR reduction scheme for the DUP mode consists of flipping the sign of data tones only, as shown in red as follows:

·       BW80 and BW160 PPDU data-tone processing:

o   Pre-DCM freq-domain signal:  𝒙

o   DCM-encoded freq-domain signal:   𝒚 = [𝒙   𝒙_𝐷𝐶𝑀 ]

o   DUP freq-domain signal: [𝒚   −𝒙   𝒙_𝐷𝐶𝑀 ]

·       BW320 PPDU data-tone processing:

o   Pre-DCM freq-domain signal split into two halves:

§  𝒙_𝐿 over lower 𝑁_𝑆𝐷/2 sub-carriers, 𝒙_𝑈 over upper 𝑁_𝑆𝐷/2 sub-carriers.

o   DCM-encoded freq-domain signal: 𝒚 = [𝒙_𝐿   𝒙_{𝐿,𝐷𝐶𝑀}   𝒙_𝑈   𝒙_{𝑈,𝐷𝐶𝑀}]

o   DUP freq-domain signal: [𝒚   −𝒙_𝐿   −𝒙_{𝐿,𝐷𝐶𝑀}   𝒙_𝑈   𝒙_{𝑈,𝐷𝐶𝑀} ] 

[Motion 135, #SP210, [25] and [59]]

---

To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1