Hi Wook Bong,
I am only suggesting we need to set the value of the PPDU Type and Compression Mode subfield of the U-SIG to a specific value.
I am suggesting that we use one of the current Validate (Reserved) values so that we can easily distinguish this EHT Ranging NDP from another EHT PPDU type.
I updated the presentation slides and added the relevant tables to Slide 33-35 of the presentation.
https://mentor.ieee.org/802.11/dcn/23/11-23-0040-02-00bk-proposal-on-320-mhz-ranging-ndp.pptx
We can discuss this more on the 11bk call.
Regards,
Steve
From: Wook Bong Lee <wookbong.lee@xxxxxxxxx>
Sent: Tuesday, April 4, 2023 8:41 AM
To: Steve Shellhammer <sshellha@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBK@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBK] TGbk Apr. 4th Telecon - Call for submissions
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Steve,
Thanks for the contribution.
In slide 15, you proposed to signal Ranging NDP in Preamble for third party receiver.
If the third party STA receives the NDP, then what is a corresponding action if it knows it is Ranging NDP?
If we define a new PPDU format, then we need to have more text for ranging NDP related text in section 36, e.g. how to set EHT-SIG MCS field, the Number Of EHT-SIG Symbols field, etc.
If there is no use case, in my opinion, it is better not to create new signaling.
One item we have not yet decided about the EHT Ranging NDP and the EHT TB Ranging NDP is whether we will signal in the U-SIG that it is a EHT (TB) Ranging NDP, and if so how. This was discussed in January in document 23/40r1
and there are several straw polls we discussed but did not finalize related to this (SP 9-11). It would be good to discuss this further and see what values we want to set in the U-SIG for both the EHT Ranging NDP and the EHT TB Ranging NDP.
Please put this on the agenda after Yanjun’s presentation.
WARNING: This
email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Thank you Yanjun, I will add to the agenda for Apr. 4th, please make sure its available on mentor prior to the telecon.
Could you help add 390r1 (PDT on NDPA) to the queue? We’re updating the PDT based on inputs from the march meeting and will upload it later this week. It’ll need ~45 min.
WARNING: This
email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
- TGbk is scheduled to meet Apr. 4th 10:00 am PT / 13:00 ET.
- This is a call for submissions, if you have a submission and would like to allocate agenda time please let me know
- Note that teleconferences are bounded by the conditions stipulated by the documentation below.
Please review and bring up any questions/concerns you may have before proceeding with the teleconference:
Cell (WhatsApp): +1-408-203-3337
To unsubscribe from the STDS-802-11-TGBK list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBK&A=1
To unsubscribe from the STDS-802-11-TGBK list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBK&A=1
To unsubscribe from the STDS-802-11-TGBK list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBK&A=1
To unsubscribe from the STDS-802-11-TGBK list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBK&A=1
|