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!