| Hi Eunsung,
Thank you for your email. I think option 1 is more general and can cover all the scheduling possibilities.
For example, AP only wants to schedule 2 STAs in 80 MHz TB PPDU for DRU, one STA is 20 MHz only STA, one STA is 80 MHz STA. The 20 MHz only STA has to be scheduled to a 20 MHz subchannel, and 80 MHz STA can be scheduled to 40 MHz subchannel using DBW40 MHz, then it will leave one 20 MHz subchannel unallocated even there is no preamble puncturing.
Thanks Yan
On Apr 21, 2025, at 11:09 PM, Eunsung Park <esung.park@xxxxxxx> wrote:
Hi All, I suggest two options to resolve the CID below. - Option 1: change “preamble puncturing” to “unallocated” - Option 2: Reject the CID based on the current motion. I’d like to hear which option you would prefer. Also, I am open to other options and please let me know if you have any. Best regards, Eunsung Hi All, I am sending this email to discuss the following CID. 2689 | Youhan Kim | No | 38.3.4 | 110 | 14 | T | 38.3.4 | 110.14 | I don't think we use the term 'preamble puncturing' for TB PPDU. | Don't have a specific suggestion, but please check whether the term 'preamble puncturing' is appropriate for TB PPDUs. | PHY |
The following is the spec text that Youhan mentions. <image001.jpg> Basically, I agree that preamble puncturing is not generally used for TB PPDU but in the motions for DBW modes, we used this term. At first, to resolve this CID, I suggested to use “unallocated” which is used in 11be but finally decided to defer it. I’d like to members’ opinion on this CID. Any suggestions are welcome. Best regards, Eunsung
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|