Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Liangxiao,
Thanks for initiating the email discussion.
My observations on the SPs are as follows:
SP1: It proposes a change in the RTS-CTS mechanism, which is a widely used legacy mechanism. The AP not sending a CTS response (as is proposed) can harm legacy non-AP performance as well as performance of EHT non-APs that do not implement rTWT. For example, the non-AP can try RTS again, fail to receive CTS again and continue in a loop. This will not only lead to a high CW, it can also make typical rate control algorithms at the non-AP to reduce the MCS for any subsequent data transmission that eventually follows a successful RTS-CTS exchange.
SP2: Proposes “reverse TXOP sharing” i.e. allowing a non-AP to share its TXOP with the AP.
This procedure can lead to more efficient channel access and so is a useful procedure in principle. For example, in a 1 AP and N non-AP system, currently the single AP has to win the channel and schedule data to/from N non-APs. With non-AP to AP TXOP sharing, any of the N non-APs can win the TXOP and share it with the AP for its triggered transmissions. Further, this prevents CCA blocking, say in case the AP is an exposed node, as any of the N spatially diverse non-APs can win the TXOP and share it with its AP. This procedure is also present in NR-Unlicensed.
However, my concerns are as follows:
Why restrict this procedure to only rTWT non-APs? If this is so restricted, it will again lead to poor relative performance of non-rTWT non-APs. This poor performance will occur not only for non-rTWT non-APs within the same BSS, but in an adjacent BSS too.
It is a major change and needs more careful discussion, also given that it is quite late into 11be standardization.
Regards,
Shubho
Hi All,
Thank you for the comments and questions during my presentation DCN0894r4 today. I am sending this email to start offline discussion here. Due to the time limit, I was not able to hear the questions from all of you. Would appreciate if you can post your questions here or send questions to me. Thank you so much!
Regards,
Liangxiao
________________________________________________________________________
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
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature