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

Re: [STDS-802-11-TGBE] Agendas for TGbe March plenary sessions

Hi Alice,

I was just intended to clarify which option that paragraph want to propose, because it’s not clear to me. Your modified text "In addition to that PPDU Type And Compression Mode being set to 1" looks better.

 

Since you referred to the motion, I want to clarify that when that motion passed, there was another agreement that NDP will be derived same as 11ax. Then later on there was a new agreement that NDP is identified by EHT-MCS + EHT-SIG. With this new agreement, the motion you referred to actually doesn’t need to include NDP because there is a new way to identify NDP. I think this was something we missed in the development.

 

For your 2nd question, if opt.1 is used, PPDU Type And Compression Mode Subfield can be reserved and repurposed in future which is a benefit of option 1.

 

I don’t have strong intension to really promote option 1 but just to point out the disconnection here.

 

BRs,

Xiaogang.

 

From: Alice Jialing Li <jialing.li.phd2@xxxxxxxxx>
Sent: Wednesday, March 17, 2021 4:25 PM
To: Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Agendas for TGbe March plenary sessions

 

Hi Xiaogang,

 

Thanks for your question.

 

Firstly, per Motion 137, #SP291, SU/SU DUP/NDP are indicated by the PPDU Type And Compression Mode field being set to 1. This is Option 2. We follow it.

 

Secondly, spec writing needs to be clear for people to follow. For argument purpose, assume Option 1. What if the UL/DL field being set to 0, PPDU Type And Compression Mode being set to 0, EHT-SIG MCS being set to 0, and Number of EHT-SIG symbols being set to 0 in the same U-SIG of an EHT PPDU? Is it a DL OFDMA transmission, or an EHT sounding NDP? So far, there is no rule (in passed SP or spec text) to support the value of the PPDU Type And Compression Mode field being overwritten by other signaling.

 

Lastly, let me clarify about the 2nd sentence in the highlighted paragraph. "In addition" means "In addition to that PPDU Type And Compression Mode being set to 1" based on the context in the paragraph. If you or anyone else think that "In addition" is not clear enough, I'm more than happy to  improve the wording by replacing it with "In addition to that PPDU Type And Compression Mode being set to 1". The highlighted paragraph is option 2, instead of option 1.

 

Regards,

Alice Chen

Qualcomm

 

 

On Wed, Mar 17, 2021 at 2:04 PM Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx> wrote:

Hi Alice, all

I still have concern about the highlighted paragraph below. To me, this is a technical issue on NDP indication. We have two options below:

Opt.1) Rely only on EHT-SIG MCS = 0 and Number of EHT-SIG symbol =0;

Opt.2) Rely only on EHT-SIG MCS = 0 and Number of EHT-SIG symbol =0 and PPDU Type And Compression Mode = 1.

 

To me, option 2 is not necessary given that opt.1 can already get the job done. Also IMO the paragraph below leaning toward option 1 because 1st sentence is just repeating the table with no additional information on NDP identification. No matter which option to go, it’s better to make it clear.

 

If PPDU Type And Compression Mode is set to 1, the EHT MU PPDU can be an EHT SU transmission or an EHT sounding NDP regardless of the value of the UL/DL field. In addition, if EHT-SIG MCS is set to 0 and Number of EHT-SIG Symbols is set to 0, it indicates an EHT sounding NDP.

 

 

BRs,

Xiaogang.

 

From: Alice Jialing Li <jialing.li.phd2@xxxxxxxxx>
Sent: Wednesday, March 10, 2021 10:44 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Agendas for TGbe March plenary sessions

 

Alfred, Sigurd and Tianyu,

 

We just uploaded updated versions of U-SIG Comment Resolution Part 1 (21/325r7), Part 2 (21/353r2), and Part 3 (21/354r1).

 

Best regards,

Alice Chen

Qualcomm

 

 

On Mon, Mar 8, 2021 at 1:56 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hello all,

 

The agendas for the TGbe sessions during the march plenary can be found below:

 

The list of contributions are being maintained in the document below:

https://mentor.ieee.org/802.11/dcn/21/11-21-0385-01-00be-mar-may-tgbe-teleconference-agenda.docx

Please let me know if I have missed any requests. 

 

The dial in details for the teleconferences can be found below:

 

Last but not least the motions that we plan to run during the Joint conf calls of this plenary (will) appear below:

Authors of PDTs and CR documents listed in Motions 153 through 157: Please ensure that revision numbers, list of CIDs are reflected correctly.

All members, please let me know if any of the CIDs and/or PDTs needs further discussion.Plan is to run Motions 153 through 157 during the second half of Wednesday's Joint session.

 

Best Regards,

 

Alfred

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302

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