Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBE] [PDT] On MU-RTS

Hi Lei and all,

 

Thank you for your understanding and prompt confirmation!

 

As there is no new comment received, I’ve just uploaded r1 (has the same spec text with the latest version in this email thread) to https://mentor.ieee.org/802.11/dcn/21/11-21-0991-01-00be-pdt-on-mu-rts.docx.

 

Thank you,

Yanjun

 

From: HUANG LEI <huang.lei1@xxxxxxxx>
Sent: Wednesday, June 23, 2021 12:37 AM
To: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [PDT] On MU-RTS

 

CAUTION: This email originated from outside of the organization.

Hi Yanjun,

 

I get your point. Thanks.

 

Best regards,

Lei

 

From: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>
Sent: Wednesday, June 23, 2021 3:21 PM
To: HUANG LEI <huang.lei1@xxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [PDT] On MU-RTS

 

Hi Lei,

 

Thank you for the clarification. If I may paraphrase:

On the transmitter side:

  • We’re aligned that an EHT AP is required to set the PS160 subfield to 1 for 320 MHz RU indication.

On the receiver side:

  • Your preference is to allow a non-AP EHT STA to ignore the PS160 subfield only for the 320 MHz RU if the Trigger frame is an MU-RTS, is my understanding correct?
    • If so, the technical advantage of such approach is unclear to me. In fact, this approach would increase the complexity at the receiver side due to the need to handle MU-RTS and Basic Trigger differently in RU decoding. In addition, it would make the 2nd reserved row in the EHT RU allocation table (below) unavailable for future use.

 

If your concern is mainly about backward compatibility with HE, we’re aligned and the current PDT doesn’t require change of HE behavior. To achieve that, the validation of the PS160 subfield is only required for an EHT variant User Info field addressed to an EHT STA in the PDT.

 

Please let me know if you have any other comments/suggestions.

 

Thanks,

Yanjun   

 

From: HUANG LEI <huang.lei1@xxxxxxxx>
Sent: Tuesday, June 22, 2021 11:35 PM
To: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [PDT] On MU-RTS

 

CAUTION: This email originated from outside of the organization.

Hi Yanjun,

 

I agree that the PS160 subfield is set to 1 for 320 MHz indication. My point is that the way of processing the PS160 subfield for 320 MHz indication by an EHT non-AP STA should be similar to the way of processing B0 of the RU Allocation subfield for 160/80+80 MHz indication by a HE non-AP STA. According to the current text, a HE non-AP STA ignores B0 of the RU Allocation subfield for 160/80+80 MHz indication. Similarly, an EHT non-AP STA can ignore the PS160 subfield for 320 MHz indication.

 

Best regards,

Lei

 

From: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>
Sent: Wednesday, June 23, 2021 11:27 AM
To: HUANG LEI <huang.lei1@xxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [PDT] On MU-RTS

 

Hi Lei,

 

Thank you for the prompt review and fixing the typo!

 

It’s a good question on whether to require the PS160 subfield set to 1 when decoding the 320 MHz RU. It looks better to keep the current PDT text (i.e., require PS160=1) from the following 3 aspects and please let me know if you have additional concerns/suggestions:

  • The existing EHT RU table in D1.0 (snapshot below) requires the PS160 subfield set to 1 when decoding the 320 MHz RU, so the current PDT is more aligned with D1.0.
  • The current PDT avoids multiple ways of indicating the 320 MHz RU, which simplifies and avoids ambiguity in transmitter/receiver design.
  • By requiring the PS160 subfield set to 1, the 2nd row in the existing EHT RU table below can be saved as a reserved combination for future use as in D1.0.

 

 

Thanks,

Yanjun

 

From: HUANG LEI <000013c45bbec18b-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, June 22, 2021 5:34 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [PDT] On MU-RTS

 

CAUTION: This email originated from outside of the organization.

Hi Yanjun,

 

Thanks. Attached please find some additional comments.

 

Best regards,

Lei

 

From: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>
Sent: Wednesday, June 23, 2021 6:52 AM
To: HUANG LEI <huang.lei1@xxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [PDT] On MU-RTS

 

Hi Lei and all,

 

Thank you for the constructive inputs and I’ve adopted most of them.

 

All the changes are tagged with “R1” in the attached based on Lei’s suggestions and offline inputs: added description on the PS160 subfield; added text to disallow MU-RTS in an EHT MU PPDU; revised text and illustration.

 

Please let me know if you have any additional comments/suggestions. I’m going to upload this as r1 if no further input is received by tomorrow’s meeting.

 

Thanks,

Yanjun

 

From: HUANG LEI <huang.lei1@xxxxxxxx>
Sent: Monday, June 21, 2021 9:20 PM
To: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [PDT] On MU-RTS

 

CAUTION: This email originated from outside of the organization.

Hi Yanjun,

 

Thank you for preparing this PDT. Attached please find my comments.

 

Best regards,

Lei

 

From: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>
Sent: Tuesday, June 22, 2021 9:57 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] [PDT] On MU-RTS

 

Hi folks,

 

I’ve uploaded the document at https://mentor.ieee.org/802.11/dcn/21/11-21-0991-00-00be-pdt-on-mu-rts.docx

 

Please let me know if you have any comments/suggestions.

 

Thanks,

Yanjun

 

From: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>
Sent: Thursday, June 17, 2021 3:34 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] [PDT] On MU-RTS

 

CAUTION: This email originated from outside of the organization.

Hi Alfred,

 

Could you help add the document 21/0991r0 on MU-RTS to the queue for joint calls?

 

I’ll upload the document once it’s ready.

 

Thanks,

Yanjun

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

OPPO

 

本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人使用（包含个人及群组）。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，请立即以电子邮件通知发件人并删除本邮件及其附件。

This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

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