| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Wook bong, Thanks for your comment. I agree with you about the non-OFDMA case. However for the OFDMA case, I think that currently it is
too early to decide whether there will not be any capability required regarding preamble puncturing. I think that not all decisions were made, for example supporting preamble puncturing in OFDMA is currently mandatory for non-AP STAs and not for AP-STAs
(AP may be a receiver in e.g. multi-AP schemes) or supporting preamble puncturing where parking mechanism (e.g. SST) is applied. In any case, if we realize that there will be no need to define capabilities for preamble puncture, we may omit this later. BR, Oded
From: Wook Bong Lee [mailto:wookbong.lee@xxxxxxxxxxx] Hi Oded, Thanks. I think multi-RU transmission and reception including non-OFDMA (which is preamble puncturing case) are mandatory in 11be. And thus, we may be not need to have capability. Best regards, Wook bong Lee
From: Oded Redlich (TRC) [mailto:oded.redlich@xxxxxxxxxx]
Dear preamble puncture TTTs, Preamble puncture text is suggested to be inserted in a new sub-section 34.3.10.10 “Preamble Puncture”. Also new text in section 9.4.2.xxx (“EHT Capabilities Element”) will probably be added to define the sub-field “EHT PHY Capabilities Information field”. We need to define the preamble puncture Rx capabilities within this sub-field (similar
to how it is defined in 9.4.2.247 in 11axD6.0) Thus I suggest the following list of sub clauses to be added: Under 34.3.10.10 – Preamble Puncture
o
34.3.10.10.1 – General
o
34.3.10.10.2 – Preamble Puncture for PPDUs transmitted to a single user
o
34.3.10.10.3 – Preamble Puncture for PPDUs transmitted to multiple users Under 9.4.2.xxx.yyy – EHT PHY Capabilities Information field
o
Punctured Preamble Rx Please feel free to volunteer to write a specific section In addition, please let me know if you have any comments or if I have missed something BR, Oded Redlich 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 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 |