| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Dmitry, inline again. 发件人: Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx>
Hi Chaoming, Please see below From:
罗朝明(Chaoming Luo) <luochaoming@xxxxxxxx>
Hi Dmitry, For 24/2007r6, I have questions on the following text: A P-EDCA eligible STA that successfully (as defined in 10.23.2.2 EDCA Backoff procedure) delivered one or more pending MPDUs in
a TXOP obtained using P-EDCA contention shall not use the P-EDCA mechanism until TBD conditions are satisfied and
EDCAF[VO] shall update the AIFSN, CWmin, and CWmax with the values in dot11EDCATable. [cm] When does this
EDCAF[VO] update occur? Does it occur when
the TXOP ends, which means the STA always goes back to EDCA whenever it completes an P-EDCA TXOP?
[Akhmetov, Dmitry] Technically yes. In the case you are referring to, STA started P-EDCA, updated CW and AIFSN values with P-EDCA values, performed contention , initialized TXOP by sending RTS
frame, get CTS back, transmitted data and received ack -> successful use of P-EDCA, data delivered. STA no longer need to use P-EDCA, it return back to the normal EDCA operations -> it update CW and AIFSN values with values from dot11EDCATable and invoke new
backoff as in 10.23.2.2. For 25/0627r3, I don’t agree with your resolution to CID 1778. In order to have the balance, I think we should
let the STA to start MUEDCATimer[VO] if it has successfully obtained one or a limited number of TXOPs using P-EDCA contention. [Akhmetov, Dmitry] I do not think MU EDCA is the right mechanism for that. MU EDCA was designed to compensate for the “unexpected” TXOP provided to the STA outside of STA’s own contention. In the
case of P-EDCA STA obtained TXOP on its own. MU EDCA assume that AP will continue to use triggering mechanism to provide TXOPs to the STA and for that STA “give up“ own freedom in terms of contention capabilities. With P-EDCA we cannot make such assumption. [cm] As you said MU EDCA is a mechanism to “compensate”, which was considered from fairness perspective. In the case of P-EDCA, if a STA has obtained TXOP use P-EDCA,
in the successive limited period, to be fair to other STAs, it should “give up” its own freedom of contention and let AP to use triggering to provide TXOPs.
BR, Chaoming 发件人: Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx>
Hello everyone, I’ve uploaded r3 of the document that incorporates comments received during Monday MAC call. https://mentor.ieee.org/802.11/dcn/25/11-25-0627-03-00bn-cc50-cr-for-p-edca.docx Please let me know if you have any questions or comments preferable by EOD of Thursday April 17th Dmitry From: Akhmetov, Dmitry
Hello everyone, I’ve uploaded r1 version of CC50 resolution document for P-EDCA clause Please review and let me know if you any comments.
The document is scheduled for presentation in Monday April 14th MAC call Dmitry From: Akhmetov, Dmitry
Dear all, I uploaded two documents: 11-24-2007r6 - Latest revision of PDT for P-EDCA https://mentor.ieee.org/802.11/dcn/24/11-24-2007-06-00bn-pdt-mac-p-edca.docx And 11-25-0627r0 – CC50 CR for the P-EDCA clause.
That document uses 2007r6 as a baseline. https://mentor.ieee.org/802.11/dcn/25/11-25-0627-00-00bn-cc50-cr-for-p-edca.docx Please review and let me know if you have any question/comments. Thanks, Dmitry 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 |