Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi all, The group now merges to option A. Below are the remaining issues: Regarding up to four or three 20 Mhz subchannels punctured in S80, this issue is not part of the comment I received. I may either modify it this
time or correct it in the next round of comment and resolution. But I’d like to hear more comments about this, about the preference and when to resolve it. I also see people have preference to not mention it at all, about whether to clearly mention up to three or four 20 MHz subchannels in S80, please
share your comment. regards 于健 Ross Yu Huawei Technologies 发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx]
代表
Mark RISON OK, I think I'm hearing consensus emerging around option a), i.e.: 4) -x-- 5) --x- or ---x 6) -x--???? including -x--xxxx 7) --x-???? including --x-xxxx, or ---x???? including ---xxxxx, or --xx???? including --xxxxxx Here then are the changes I propose to resolve the comment (the stuff in green is the stuff that would have to be changed (to "three") if we decide that it should not be allowed to puncture the entire S80 after all): Table 9-321b—Subfields of the HE PHY Capabilities Information field,
Punctured Preamble Rx field definition B0 indicates support for the reception of an 80 MHz preamble where the only punctured subchannel is the secondary 20 MHz
B1 indicates support for the reception of an 80 MHz preamble where the only punctured subchannel is
one of the two 20 MHz subchannels in the secondary 40 MHz channel B2 indicates support for the reception of a 160 MHz or 80+80 MHz preamble where
the only punctured subchannels are the secondary 20 MHz channel B3 indicates support for the reception of a 160 MHz or 80+80 MHz preamble where the
only punctured subchannels are one or both of the 20 MHz subchannels in the secondary 10.23.2.5 EDCA channel access in a VHT, HE or TVHT BSS [Note for group discussion: text highlighted in yellow should probably be changed to something like “all of the 20 MHz subchannels that are not punctured
were idle”.] i) Transmit an
80 MHz HE MU PPDU j) Transmit an
80 MHz HE MU PPDU k) Transmit a l) Transmit a Table 27-1—TXVECTOR and RXVECTOR parameters, CH_BANDWIDTH value
if FORMAT is HE_MU HE-CBW-PUNC80-PRI for preamble puncturing in 80 MHz, where in the preamble
the only HE-CBW-PUNC80-SEC for preamble puncturing in 80 MHz, where in the preamble
the only punctured subchannel is one of the two 20 MHz subchannels in
the secondary 40 MHz channel HE-CBW-PUNC160-PRI20 for preamble puncturing in 160 MHz, where in
HE-CBW-PUNC80+80-PRI20 for preamble puncturing in 80+80 MHz, where in
HE-CBW-PUNC160-SEC40 for preamble puncturing in 160 MHz HE-CBW-PUNC80+80-SEC40 for preamble puncturing in 80+80 MHz, where in
Table 27-3— Interpretation of FORMAT, NON_HT Modulation and CH_BANDWIDTH parameters,
CH_BANDWIDTH rows as shown HE-CBW-PUNC80-PRI: The STA transmits an
80 MHz HE PPDU HE-CBW-PUNC80-SEC: The STA transmits an
80 MHz HE PPDU HE-CBW-PUNC160-PRI20: The STA transmits a HE-CBW-PUNC80+80-PRI20: The STA transmits an 80+80 MHz HE PPDU
HE-CBW-PUNC160-SEC40: The STA transmits a HE-CBW-PUNC80+80-SEC40: The STA transmits an 80+80 MHz HE PPDU
Table 27-4— Interpretation of CH_BANDWIDTH and INACTIVE_SUBCHANNELS parameters when FORMAT is equal to NON_HT and NON_HT_MODULATION is equal to NON_HT_DUP_OFDM,
CH_BANDWIDTH rows as shown, for punctured PPDUs CBW80: The bit corresponding to the primary 20 MHz channel set to 0 and
CBW160: The bit corresponding to the primary 20 MHz channel set to 0 and
CBW80+80: The bit corresponding to the primary 20 MHz channel set to 0 and
Table 27-20—HE-SIG-A field of an HE MU PPDU, Bandwidth field Set to 4 for preamble puncturing in 80 MHz, where in the preamble
the only punctured subchannel is the secondary 20 MHz channel Set to 5 for preamble puncturing in 80 MHz, where in the preamble
the only punctured subchannel is one of the two 20 MHz subchannels in
the secondary 40 MHz channel Set to 6 for preamble puncturing in 160 MHz or 80+80 MHz, where in
Set to 7 for preamble puncturing in 160 MHz or 80+80 MHz, where in
C.3 MIB Detail dot11HEPuncturedPreambleRxImplemented OBJECT-TYPE SYNTAX OCTET STRING(SIZE( MAX-ACCESS read-only STATUS current DESCRIPTION "This is a capability variable. Its value is determined by device capabilities. This attribute is a bitmap that indicates the preamble p where bit
an 80 MHz preamble where the secondary 20 MHz
bit
one of the two 20 MHz subchannels in the secondary 40 MHz channel is punctured, bit
a 160 MHz or 80+80 MHz preamble where
bit
a 160 MHz or 80+80 MHz preamble where one or both of the 20 MHz subchannels in the secondary 40 MHz channel are punctured.
::= { dot11PhyHEEntry
2 } Change “MHz is” to “MHz channel is” at 274.59.
[MR1]Or
just “all of the 20 MHz subchannels that are not punctured were idle”? Thanks, Mark On Thu, 9 Apr 2020 at 18:41, Mark RISON <m.rison@xxxxxxxxxxx> wrote:
Mark RISON, Standards Architect, WLAN English/Esperanto/Français To unsubscribe from the STDS-802-11-TGAX list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 |