| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Wook Bong, Thanks for the detailed response. Please see my comments
inline. regards 于健 Ross Yu Huawei Technologies 发件人: Wook Bong Lee [mailto:wookbong.lee@xxxxxxxxxxx]
Hi Ross, Thanks for question. FILS/unsolicited probe response for 6GHz was an example of broadcast frame for unassociated STA. In 11ax, the FILS/unsolicited probe response for 6GHz is sent using non-HT or HE format. But can we assume there is no broadcast frame(s) for unassociated STA in EHT or EHT+ format? Ross: that’s something I wonder. So I am asking if you or someone else has any examples/motivations now. Frames
for OBSS/unassociated STAs are for discovery as far as I know, which should aim for legacy STAs too. The interpretation of SP is puncturing information without knowledge of primary channel information.
Alternative choice will be puncturing information which requires primary channel information. But this option does not save much overhead while it is partial information which requires additional information (even for 80MHz PPDU, e.g. compressed)
in EHT SIG. Ross: for OFDMA case, the alternative choice can save 1 or 2 bit. For non-OFDMA case, I agree with you additional
info is required in EHT even for 80MHz PPDU. Each option has pro and con. Do you want to have a puncturing information in U-SIG (separate from BW field) which requires primary channel information? Ross: I am still evaluating. If there is no good motivation to have broadcast RUs for unassociated/OBSS STAs.
Saving 1 or 2 bit in U-SIG is a good option. Best regards, Wook Bong Lee From: Yujian (Ross Yu) [mailto:ross.yujian@xxxxxxxxxx]
Hi Wook Bong, For SP28, I remember the motivation is for the OBSS/unassociated device to decode FILS/unsolicited probe response for 6GHz in-band discovery as shown
in your slide 8. However after a second thought, I wonder why those information will be likely sent in EHT format. As there are HE STAs in 6GHz also, so most time, the AP would use: Assuming there is (incumbent) interference in some non-primary channel:
1)
HE SU in 20MHz
2)
Punctured non-HT duplicate
3)
HE MU PPDU assuming the Rx only decodes one CC only in the detected channel or has received the beacon in advance
Assuming there is no (incumbent) interference:
1)
HE SU >=20MHz
2)
HE MU PPDU w/o puncturing Seems there is no strong motivation to let non-associated/OBSS STAs decode EHT PPDU. How do you think? Do you or anyone else has any better motivations? Straw poll #28 802.11be signaling in U-SIG for BW/puncturing information in every non-punctured
20 MHz of an 80 MHz segment shall allow even an OBSS or unassociated device to decode the puncturing pattern of at least the specific 80 MHz that contains the 20 MHz. [#SP28] [20/0606r2 (Further discussion on bandwidth and puncturing information, Wook Bong Lee, Samsung), SP#1, Y/N/A:
34/10/8]
regards 于健 Ross Yu Huawei Technologies 发件人: Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
Hello all, Our TGbe Editor has prepared the Rev 26 of the compendium of SPs and potential changes to the SFD, which can be found below: This is a call for members to review the new SFD text contributions (which are highlighted in yellow and identified by tags listed as [DCN (Presentation, Author, Affiliation), ...]
SP#X, ...) in the compenidum of SPs document. Please do send an e-mail in response to this Call For Review if you would like to identify any of these "new SFD text contributions" as contributions that need further discussion. The deadline for sending these e-mails
is June 10th 2020 @10:00am ET. A list of these requested contributions will be queued for discussion and run as a separate motion (Motions >=113) during the Joint conference call scheduled on June 11th 2020. New SFD text contributions that have not received a request for further discussions will be part of the cumulative motion (Motion 112) that will be run at the same Joint conference call.
For more information please refer to the subclause "Guideline-Building Consensus and Populating the TGbe SFD" in the TGbe teleconference agendas: https://mentor.ieee.org/802.11/dcn/20/11-20-0735-15-00be-2020-mar-may-tgbe-teleconference-agendas.docx. If you have any comments and/or questions please let me know. 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 |