| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Yan, You are correct. What I wanted to say is that 20us actual TPE Tx/Rx should be mandatory regardless of capabilities. regards 于健 Ross Jian Yu Huawei Technologies 发件人: Yan(msi) Zhang [mailto:yan.zhang_5@xxxxxxx]
Hi Ross, I want to clarify what you mean all types of PE are Tx/Rx mandatory. Do you mean the actual TPE value? Then I think the STAs claim 16us NOMINAL_PACKET_PADDING value for all modes do not need to support 0 us PE duration.
For STA claims 16 μs for all modes with constellation ≤ 1024, NSS ≤ 8 and RU ≤ 2×996, and 20 µs for all other modes the STA supports, even with pre-FEC padding factor set to 1, TPE duration is 8us when the EHT transmission covers one of the modes (4096QAM,
RU > 2x996 or Nss > 8), then the STA does not have to support 0us and 4us TPE values. That’s why I think it is optional for STA to support all PE durations. Thanks Yan From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>
Hi Yan, In 11ax, I think all types of PE are Tx/Rx mandatory and may be transmitted (larger than nominal packet padding announced by the AP/STA). Seems now people have some different understanding
of 20us PE. That’s why I asked the previous questions. I also agree we should have some discussion. regards 于健 Ross Jian Yu Huawei Technologies 发件人: Yan(msi) Zhang [mailto:yan.zhang_5@xxxxxxx]
Hi Youhan, If your example holds, then there seems little advantage to separate Nominal packet padding support as in “Set to 3 if the nominal packet padding is 16 μs for
all modes with constellation ≤ 1024, NSS ≤ 8 and RU ≤
2×996, and 20 µs for all other modes the STA supports.”, or claim Nominal packet padding support < 20us. If one of the participating EHT TB PPDU transmit
at MCS 13/14, or one RU is assigned with more than 8 spatial streams, or transmission BW is 320MHz, AP can choose PE = 20us with pre-FEC padding factor set to 4. Those qualified modes will cover many EHT TB PPDU transmissions.
We probably need some discussions on if AP should have some restrictions on scheduling non-AP STAs depending on their
Nominal Packet Padding value support.
From: Youhan Kim <youhank@xxxxxxxxxxxxxxxx>
Caution: EXT Email
Thanks, Yan. Suppose an AP schedules 20 MHz EHT UL OFDMA, with user1 assigned to RU106+26, and user2 to RU106. The user1 is assigned 1SS MCS7, and user2 is assigned 1SS MCS13. Since AP is the receiver, the “RX” PPE declaration from user1 or user2 does not matter in this case. And the AP can choose to send a Trigger frame asking for the EHT TB PPDU to have pre-FEC padding factor = 4 and PE = 20 usec in this case. So, even user1 needs to transmit 20 usec PE even though the PPDU BW is not 320 MHz, Nss is < 8SS and MCS < 12. Or, are you suggesting an AP cannot send a Trigger frame such as above? Regards, Youhan From: Yan(msi) Zhang <yan.zhang_5@xxxxxxx>
CAUTION: This email
originated from outside of the organization. Hi Youhan, I am not propose any new capability. Maybe my wording is not accurate for this statement” I don’t think the statement above indicates every non-AP STA has to support
20us PE duration since AP can schedule the non-AP STAs in EHT MU PPDU or EHT TB PPDU according to their PE support indications”. What I mean is Nominal packet padding value support. Regards Yan From: Youhan Kim <youhank@xxxxxxxxxxxxxxxx>
Caution: EXT Email
Hi, Yan. Thanks for the update.
It sounds like you are proposing that 11be adds capabilities through which non-AP STAs declare what PE duration they support in “transmission”, and AP has the responsibility not to send Trigger frames w/ PE duration which
the non-AP STA declares not to support (i.e., non-AP STAs with different PE TX capabilities cannot be grouped in the same UL OFDMA/MU-MIMO). Is this correct? There was no such capability in 11ax. If that is your proposal, why do we need such new capability
in 11be? Regards, Youhan From: Yan(msi) Zhang <yan.zhang_5@xxxxxxx>
CAUTION: This email
originated from outside of the organization. Hi Ross, It is optional feature for both transmit/receive.
The duration of the PE field in EHT MU PPDU may take value of 20 µs for any modes with constellation > 1024 or NSS > 8 or RU > 2×996.
[Motion 137, #SP268, [3] and [139]] The EHT Nominal Packet Padding has two capability bits that are defined as follows.
[Motion 137, #SP269,
[3] and [139]] BR Yan From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>
Hi Yan, Could you remind me if we have any conclusion or discussion about the M/O of 20us PE reception or transmission? Thanks. regards 于健 Ross Jian Yu Huawei Technologies 发件人: Yan(msi) Zhang [mailto:yan.zhang_5@xxxxxxx]
Hi all, Based on the comments raised regarding the allowed transmission modes with 20us PE duration. My modifications are highlighted in yellow.
A PE field of duration 20
µs is only allowed in
an EHT PPDU with at least one participating STA being modulated with 4096-QAM, or in an EHT PPDU with more than 8 spatial streams transmitted on at least one RU/MRU, or in a 320 MHz EHT MU PPDU if
the size of the one of the allocated RU or MRU is greater than 2x996, or in a 320MHz (TBD) EHT TB PPDU.
I don’t think we need to talk about non-AP STA support of 20us transmit/receive in this section. Non-AP STA support of transmit/receive 20us PE duration should be described in HE PHY capabilities subfield “Nominal
Packet Padding”, and PPE Thresholds field section, as in 11ax. Besides, I don’t think the statement above indicates every non-AP STA has to support 20us PE duration since AP can schedule the non-AP STAs in EHT MU PPDU or EHT TB PPDU according to their PE support
indications. In this section, we just clarify what the specific properties are required for an EHT PPDU to be allowed to transmit with 20us PE duration. The statement
“an EHT PPDU with at least
one participating STA being modulated with 4096-QAM, or in an EHT PPDU with more than 8 spatial streams transmitted on at least one RU/MRU”
covers EHT MU PPDU with OFDMA, or MU-MIMO, and EHT TB PPDU with OFDMA, or MU-MIMO, and EHT MU PPDU with only one STA. Please let me know if you have other concerns. Thanks Yan 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 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
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 |