[STDS-802-11-TGAX] 答复: [STDS-802-11-TGAX] Allowed puncturing patterns

["Yujian (Ross Yu)" <ross.yujian@xxxxxxxxxx>]

Hi Mark and all,

 

Thanks for bringing the updated proposal.

 

I have the following high level comments:

1.       The first comment is related with previous SP3 (9/5/15). From implementation point of view, there is no reasoning to restrict for case 7, there must exist one punctured subchannel in P80. What’s the technical problem if the P80 is not punctured? The Tx only needs to ensure the Rx can find one CC1 and one CC2 in HE-SIG-B. In other words, if p80 is empty, the Tx needs to puncture one subchannel and lose 1/(5~8) Tput efficiency, just to meet the making-no-sense requirement?

2.       The second comment is related with SP4 (19/5/8). The puncture pattern in 11be is not finalized. I see people also show interests in 1xx1 pattern in P80 in 11be. Contributions in 20-129r0 shows a very good example on the Tput loss when a less flexible preamble puncture is supported. I hear Youhan also says he is ok to not make any changes regarding the stage of 11ax spec. I share similar opinion on that. So I prefer to not make changes regarding the puncture pattern at this stage. Maybe adjust the spectrum mask or regulatory rule is a good choice.

3.       Last but not least, I also have concern that currently few PHY people join the call, it is a risky we make big technical changes regarding preamble puncture.

 

I will join Thur call, we may further discuss it during the call.

 

regards

 

于健 Ross Yu

Huawei Technologies

 

发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] 代表 Mark RISON
发送时间: 2020年4月27日 4:55
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Based on the SPs last week, here is my updated proposal on spec wording for preamble puncturing:

 

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 subchannel is punctured.

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 is punctured.

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 in the primary 80 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across a 160 MHz preamble.

[Do we want a "NOTE—No more than two adjacent 20 MHz channels are available to be punctured across an 80+80 MHz preamble."?]

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 secondaryprimary 40 MHz channel and zero to two of the 20 MHz subchannels in the secondaryprimary 80 MHz channel is present. If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across a 160 MHz preamble.

 

10.23.2.5 EDCA channel access in a VHT, HE or TVHT BSS

 

[Note for group discussion: condition highlighted in yellow should probably be changed to something like “if all of the 20 MHz subchannels that are not punctured were idle”, because the current wording is not specific enough (e.g. for k) and l) it’s not just any one of the four 20 MHz subchannels in S80 that needs to be idle).]

 

i) Transmit an 80 MHz HE MU PPDU with preamble puncturing in 80 MHz where in the preamble only the only punctured subchannel is the secondary 20 MHz channel is punctured, if the secondary 40 MHz channel was idle during an interval of PIFS immediately preceding the start of the TXOP.

 

j) Transmit an 80 MHz HE MU PPDU with 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 is punctured, if the secondary 20 MHz channel, and one of the two 20 MHz subchannels ofin the secondary 40 MHz channel werewas idle during an interval of PIFS immediately preceding the start of the TXOP.

 

k) Transmit an 160 MHz or 80+80 MHz HE MU PPDU with preamble puncturing in 160 MHz or 80+80 MHz where in the primary 80 MHz of the preamble the only punctured subchannels are the secondary 20 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel, if the secondary 40 MHz channel, and at least one of the four 20 MHz subchannels in the secondary 80 MHz channel were idle during an interval of PIFS immediately preceding the start of the TXOP.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across a 160 MHz preamble.

 

l) Transmit an 160 MHz or 80+80 MHz HE MU PPDU with preamble puncturing in 160 MHz or 80+80 MHz where in the primary 80 MHz of the preamble the only the primary 40 MHz is present punctured subchannels are one or both of the 20 MHz subchannels in the secondary 40 MHz channel and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel, if the secondary 20 MHz channel, and at least one of the four 20 MHz subchannels in the secondary 80 MHz channel were idle during an interval of PIFS immediately preceding the start of the TXOP.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across a 160 MHz preamble.

 

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 the punctured subchannel is the secondary 20 MHz channelis punctured.

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 channelis punctured.

HE-CBW-PUNC160-PRI20 for preamble puncturing in 160 MHz, where in the primary 80 MHz of the preamble the only punctured subchannels are the secondary 20 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across the 160 MHz preamble.

HE-CBW-PUNC80+80-PRI20 for preamble puncturing in 80+80 MHz, where in the primary 80 MHz of the preamble the only punctured subchannels are the secondary 20 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.

HE-CBW-PUNC160-SEC40 for preamble puncturing in 160 MHz or 80+80 MHz, where in the primary 80 MHz of the preamble the only punctured subchannels are primary 40 MHz is present, and at least one or both of the 20 MHz subchannels that is not in the secondaryprimary 40 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across the 160 MHz preamble.

HE-CBW-PUNC80+80-SEC40 for preamble puncturing in 80+80 MHz, where in the primary 80 MHz of the preamble the only punctured subchannels are primary 40 MHz is present, and at least one or both of the 20 MHz subchannels that is not in the secondaryprimary 40 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.

 

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 on the punctured 80 MHz bandwidth where the only punctured subchannel is the secondary 20 MHz channelis punctured.

HE-CBW-PUNC80-SEC: The STA transmits an 80 MHz HE PPDU on the punctured 80 MHz bandwidth where the only punctured subchannel is one of the two 20 MHz subchannels in the secondary 40 MHz channelis punctured.

HE-CBW-PUNC160-PRI20: The STA transmits an 160 MHz HE PPDU on the punctured 160 MHz bandwidth where the only punctured subchannels are the secondary 20 MHz channel in the primary 80 MHz is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across the 160 MHz preamble.

HE-CBW-PUNC80+80-PRI20: The STA transmits an 80+80 MHz HE PPDU on the punctured 80+80 MHz bandwidth where the only punctured subchannels are the secondary 20 MHz channel in the primary 80 MHz is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.

HE-CBW-PUNC160-SEC40: The STA transmits an 160 MHz HE PPDU on the punctured 160 MHz bandwidth where the only punctured subchannels are primary 40 MHz in the primary 80 MHz is present, and at least one or both of the 20 MHz subchannels that is not in the secondaryprimary 40 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across the 160 MHz preamble.

HE-CBW-PUNC80+80-SEC40: The STA transmits an 80+80 MHz HE PPDU on the punctured 80+80 MHz bandwidth where the only punctured subchannels are primary 40 MHz in the primary 80 MHz is present, and at least one or both of the 20 MHz subchannels that is not in the secondaryprimary 40 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.

 

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

 

[Note for group discussion: are we OK with the vague “any”?]

 

CBW80: The bit corresponding to the primary 20 MHz channel set to 0 and one or two other bits set to 0 that correspond to any other subchannels in the primary 80 MHz, all other bits set to 1

CBW160: The bit corresponding to the primary 20 MHz channel set to 0 and onethree to six other bits set to 0 that correspond to any other subchannels in the 160 MHz, all other bits set to 1

CBW80+80: The bit corresponding to the primary 20 MHz channel set to 0 and onethree to six other bits set to 0 that correspond to any other subchannels in the 80+80 MHz, all other bits set to 1

 

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 is punctured.

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 is punctured.

Set to 6 for preamble puncturing in 160 MHz or 80+80 MHz, where in the primary 80 MHz of the preamble the only punctured subchannels are the secondary 20 MHz channel is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across 160 MHz.

Set to 7 for preamble puncturing in 160 MHz or 80+80 MHz, where in the primary 80 MHz of the preamble the only punctured subchannels are one or both of the 20 MHz subchannels in the secondaryprimary 40 MHz channel is present, and at least one 20 MHz subchannel that is not in the primary 40 MHz is punctured and zero to two of the 20 MHz subchannels in the secondary 80 MHz channel.  If two of the 20 MHz subchannels in the secondary 80 MHz channel are punctured, these are either the lower two or the higher two.  No more than two adjacent 20 MHz subchannels are punctured across 160 MHz.

 

C.3 MIB Detail

 

[Note for group discussion: I think the changes below are enough and it’s necessary to be quite so specific as above here, but I can be so if the group so desires.]

 

dot11HEPuncturedPreambleRxImplemented OBJECT-TYPE

SYNTAX OCTET STRING(SIZE(21))

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 prunctured channeling support,

where bit equal to 0 is set to 1 to indicate support for the reception of

an 80 MHz preamble where the secondary 20 MHz subchannel is punctured,

bit equal to 1 is set to 1 to indicate support for the reception of an 80 MHz preamble where

one of the two 20 MHz subchannels in the secondary 40 MHz channel is punctured,

bit equal to 2 is set to 1 to indicate support for the reception of

a 160 MHz or 80+80 MHz preamble where in the pri-

mary 80 MHz of the preamble only the secondary 20 MHz channel is punctured, and

bit equal to 3 is set to 1 to indicate support for the reception of

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.

in the primary 80 MHz of the preamble, the primary 40 MHz is present."

::= { dot11PhyHEEntry 2 }

 

Change “MHz is” to “MHz channel is” at 274.59.

 

For cross-checking purposes, I think the following gives all the

permitted puncturings for 80+80/160; please tell me if you spot

and mistakes or omissions:

 

6 where P20 is lowest (reversed pattern where P20 is highest):

 

-x--xx--

-x----xx

-x--x---

-x---x--

-x----x-

-x-----x

-x------

 

6 where P20 is second lowest (reversed pattern where P20 is second highest):

 

x---xx--

x-----xx

x---x---

x----x--

x-----x-

x------x

x-------

 

6 where P20 is third lowest (reversed pattern where P20 is third highest):

 

---xxx-- [80+80 only]

---x--xx

---xx---

---x-x--

---x--x-

---x---x

---x----

 

6 where P20 is fourth lowest (reversed pattern where P20 is fourth highest):

 

--x-xx--

--x---xx

--x-x---

--x--x--

--x---x-

--x----x

--x-----

 

7 where P40 is lowest (reversed pattern where P40 is highest):

 

--x-xx--

--x---xx

--x-x---

--x--x--

--x---x-

--x----x

--x-----

 

--xxxx-- [80+80 only]

--xx--xx

--xxx--- [80+80 only]

--xx-x--

--xx--x-

--xx---x

--xx----

 

---xxx-- [80+80 only]

---x--xx

---xx---

---x-x--

---x--x-

---x---x

---x----

 

7 where S40 is lowest (reversed pattern where S40 is highest):

 

x---xx--

x-----xx

x---x---

x----x--

x-----x-

x------x

x-------

 

xx--xx--

xx----xx

xx--x---

xx---x--

xx----x-

xx-----x

xx------

 

-x--xx--

-x----xx

-x--x---

-x---x--

-x----x-

-x-----x

-x------

 

Thanks,

 

Mark

 

--

Mark RISON, Standards Architect, WLAN   English/Esperanto/Français
Samsung Cambridge Solution Centre       Tel: +44 1223  434600
Innovation Park, Cambridge CB4 0DS      Fax: +44 1223  434601
ROYAUME UNI                             WWW: http://www.samsung.com/uk

 

On Fri, 17 Apr 2020 at 00:25, Osama Aboul-Magd <oamagd@xxxxxxxxx> wrote:

Thanks Ross.

 

Regards;

Osama.

 

From: "*** 802.11 TGax - HEW - High Efficiency WLAN ***" <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> on behalf of "Yujian (Ross Yu)" <ross.yujian@xxxxxxxxxx>
Reply-To: "Yujian (Ross Yu)" <ross.yujian@xxxxxxxxxx>
Date: Thursday, April 16, 2020 at 7:22 PM
To: <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Hi Osama, 

Per request, please defer the preamble puncture related stuff in the next call. Thanks. 

--------------------------------------------------
regards
于健 Ross Yu
Sent from Great Huawei Mate 20X

发件人：Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>

收件人：Osama Aboul-Magd <oamagd@xxxxxxxxx>;STDS-802-11-TGAX <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>

时 间：2020-04-16 08:17:00

主 题：答复: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Hi all,

 

If possible, I would like to present in this week’s CC. I am also ok to choose a time that all interested parties can participate if there are further requests.

 

regards

于健 Ross Yu

Huawei Technologies

 

发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] 代表 Osama Aboul-Magd
发送时间: 2020年4月16日 8:04
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Hi Lili,

 

Yes, we can arrange it. I am not sure when Ross is presenting. Also Mark has asked to run a number of SPs. I prefer to schedule the discussion during a time when all interested individuals are available.

 

Regards;

Osama.

 

From: "*** 802.11 TGax - HEW - High Efficiency WLAN ***" <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> on behalf of Lili Hervieu <L.Hervieu@xxxxxxxxxxxxx>
Reply-To: Lili Hervieu <L.Hervieu@xxxxxxxxxxxxx>
Date: Wednesday, April 15, 2020 at 6:43 PM
To: <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Hello Osama,

 

I have a submission, 618r0 (CID 24101), that is related to puncturing patterns and SP2. This is complementary to CID 24106 handled by Ross. It has also been briefly addressed last week while Ross presented his submission.   

It would be beneficial to review these CIDs in the same session. So I would like to ask if I can present my submission right after Ross’s one.

 

Thanks,

Lili.

 

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Osama AboulMagd
Sent: Tuesday, April 14, 2020 7:02 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Ok. Thanks Ross.

 

Regards;

Osama.

 

From: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] On Behalf Of Yujian (Ross Yu)
Sent: Tuesday, April 14, 2020 4:22 AM
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGAX] 答复: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Hi Mark and all,

 

I am to run SP1. For SP2, that is not part of my CID. Maybe Lili or somebody else later can request a SP.

 

Hi Osama,

 

It would be good if put the contribution 497r2 back in the queue to have some discussion first, before I run the motions according to the discussion.

 

regards

于健 Ross Yu

Huawei Technologies

 

发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] 代表 Mark RISON
发送时间: 2020年4月13日 21:09
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGAX] Allowed puncturing patterns

 

Based on the subsequent discussions on the reflector, I think we need to

run the following two SPs to make progress:

 

SP1) For 160M/80+80M, should having all the 20M subchannels in the secondary 80M channel punctured be allowed?

 

SP2) For 160M/80+80M, should having more than two adjacent 20M subchannels punctured be allowed?

Note: for 160M this includes channels adjacent between the primary and secondary 80M channels, e.g. the ---xxx-- pattern

 

Thanks,

 

Mark

 

On Thu, 9 Apr 2020 at 18:41, Mark RISON <m.rison@xxxxxxxxxxx> wrote:

This is the follow-up to the teleconf discussion just now, to

attempt to reach consensus on which puncturing patterns are and

are not allowed.

 

STRAWMAN PROPOSAL:

 

If the primary 20 MHz channel is the leftmost one, and x means

punctured, - means not punctured and ? means can be punctured,

then these correspond to only allowing the following patterns

in each case (obviously the patterns will get rearranged if the

P20 is not the leftmost one) for the value of the Bandwidth

field in the HE-SIG-A field of an HE MU PPDU:

 

4) -x--

5) --x- or ---x

6) -x--???? but not -x--xxxx

7) --x-???? but not --x-xxxx, or

   ---x???? but not ---xxxxx, or

   --xx???? but not --xxxxxx

 

During the teleconf I think I heard some variants proposed (calling

the one above z):

 

a) Allow full puncturing of S80, 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

 

b) Don't allow any puncturing of S80 (maybe the D1.0 wording?), i.e.:

 

4) -x--

5) --x- or ---x

6) -x------

7) --x----- or

   ---x---- or

   --xx----

 

c) Allow "any 2" puncturing for the 7 case (I think I heard something

like that?), i.e.:

 

4) -x--

5) --x- or ---x

6) -x--???? [all x for ? TBD]

7) --x-???? where exactly one of the ?s is a x, or

   ---x???? where exactly one of the ?s is a x, or

   ----???? where exactly two of the ?s are an x, or

   --xx----

 

d) Or was it "at least 2" puncturing for the 7 case, i.e.:

 

4) -x--

5) --x- or ---x

6) -x--???? [all x for ? TBD]

7) --x-???? where between 1 and 3 (4 TBD) of the ?s are xs, or

   ---x???? where between 1 and 3 (4 TBD) of the ?s are xs, or

   ----???? where between 2 and 3 (4 TBD) of the ?s are xs, or

   --xx???? where between 0 and 3 (4 TBD) of the ?s are xs

 

Plus a variant to any of the above:

 

e) For any/all of the above, don't allow more than 2 adjacent xs

for the 160M case (obviously N/A for 80 and I think also for 80+80)

 

Please select your option (z or a-d, plus e) or otherwise describe

your understanding.

 

Happy Easter, and best wishes to you, your colleagues and your families,

 

Mark

 

---

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