Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Pooya,
I have one question about MU EDCA parameters you mentioned here "Mainly the intention of the text
is that strictly MU EDCA parameters be used for unmapped TIDs." What about mapped TIDs? Do you mean that MU EDCA parameters are not used for mapped
TIDs?
Thanks,
Kiseon
From: Pooya Monajemi <00000ef0b9e0aff7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, May 10, 2022 7:15 PM To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx> Subject: Re: [STDS-802-11-TGBE] Discussion on 1793 TID Mapping Enhancements Hello and thanks for your question here. Mainly the intention of the text is that strictly MU EDCA parameters be used for unmapped TIDs. The proposed text is silent about when the STA should decide to update its MU EDCA
parameters. There may be a number of possible times to update these parameters:
- At association time (e.g. a mapping scheme was advertised by the AP and the MU EDCA parameters were received during association procedure)
- After a mapping negotiation is completed (post-association), the STA may listen for MU EDCA parameters in a Beacon
- (longer time) after a negotiation is complete
- ...
Best
Pooya
On Monday, May 9, 2022, 01:49:50 PM PDT, L. S. <lsun2005@xxxxxxxxx> wrote:
Hi Pooya,
Sorry a clarification question:
"The STA affiliated with the non-AP MLD associated to an AP MLD and operating on the enabled link may transmit MSDUs or AMSDUs with a TID not mapped to that link to the AP operating on that link and
affiliated with its associated AP MLD if the affiliated AP does not include the MU EDCA Parameters Set element in the Beacon frames, or if the affiliated AP includes the MU EDCA Parameters Set element in the Beacon frames that the affiliated AP transmits and
the non-AP STA has updated
its CWmin[AC], CWmax[AC], AIFSN[AC] and MUEDCATimer[AC] state variables to the values contained in the dot11MUEDCATable
for the AC of that TID following 26.2.7 (EDCA operation using MU EDCA parameters). The non-AP STA's operation follows 26.2.7 (EDCA operation using MU EDCA parameters) except that the non-AP STA does not count
down the MUEDCATimer[AC] timer for the AC of that TID."
What makes the non-AP STA update its EDCA parameters prior to transmitting MSDUs with a TIDx not mapped to the link?
Is it because the non-AP STA previously was triggered on the link and sent an MSDU (in the responding TB-PPDU) with a TIDy belonging to the same AC as TIDx? TIDy is mapped to the link but TIDx is not?
Sorry if you have already explained it and i did not catch that!
Thanks!
On Mon, Apr 18, 2022 at 5:17 PM Pooya Monajemi <00000ef0b9e0aff7-dmarc-request@xxxxxxxxxxxxxxxxx>
wrote:
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 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 |