5032 Chittabrata Ghosh 6.18 It is specified that a STA that receives a Basic Trigger frame with its AID in Per User Info field shall update MU EDCA parameters. However, there is no STA behavior mentioned with respect to MU EDCA parameter update when a STA accesses a random access RU with AID 0 assigned in Basic Trigger frame; Suggest to provide STA behavior when a STA accesses an RU assigned for random access indicated by AID 0 in Basic Trigger frame; Revised – agree in principle with the comment. Add a note as described in the proposed changes in doc 204r0 5172 Dorothy Stanley what's an "OMI A-Control field"? Change to "Operating Mode subfield in A-Control subfield" in all locations "OMI A-Control field" is used, or define "OMI field" Rejected - the OMI A-control field will be defined as part of other CR. 5684 Guoqing Li what does "updating its EDCA access" mean when UL MU is disabled? What happens to the counters in this case? Regenerate according to new EDCA parameters? Or down to zero then start using the new EDCA parameters? Clarify Revised – Clarify NOTE1 so that when UL MU is disabled, the STA is exempt from updating its EDCA access parameters. 5853 Hyunhee Park Basically, the HE STA enters the doze state outside TWT SPs. In this case, HEMUEDCATimer doesn't need to countdown. Add below sentence in P152P20 for clarification of HEMUEDCATimer. "The HEMUEDCATimer[AC] should not countdown outside trigger-enabled TWT SPs." Rejected – TWT SPs is not the only period where UL MU operation is possible, so there are no reasons to define such rules. Plus, this MU EDCA parameters mechanism is defined so that it is orthogonal to other mechanisms, including TWT. That means that the MU EDCA rules apply the same way with and without TWT. enabled
8213 Osama Aboulmagd The parameter HEMUEDCATimer[AC] seems to appear for the first time in the draft on page No proper definition was given and its role in channel acces wasn't explained. Introduce definition and describe its use including how to set its value Revised – add a sentence to clarify that it is set to the value in the MU EDCA Timer subfield in MU EDCA parameter set element 8214 Osama Aboulmagd Clause 27.2.3 doesn specify clearly when an EDCA for UL MU Capable STAs is obtained. It focuses on the different parameter settings. explain which counters are involved in obtaining the TXOP. Does HEMUEDCATimer[AC] only used to contrl the values of Cwmin, Cwmax, etc as implied in the last paragarph of this clause. Need to be clear Revised – in principle with the comment. Clarify the spec by changing the spec text as in the proposed changes in doc 204r0. 8264 Pascal VIGER HEMUEDCATimer[AC] uniformly count down to 0. Is this countdown continuously performed along time, or is the countdown suspended in between each medium access (that means only counting down during contention procedure periods) ? Please clarify when countdown is executed. Revised – Clarify that there can not be any suspensions. Modify the sentence as defined in the proposed changes in fdoc 204r0. 8295 Patrice Nezou When a STA is in MU EDCA mode, how the QoS data are selected from the ACs ? Proposal: "The HE PPDU is built based on the current backoff values of ACs. The backoff values must be updated after the transmission". Rejected – this comment does not refer to this section, but to subclause 27.10.4 A-MPDU with multiple TIDs where these rules are already defined. 8296 Patrice Nezou When a STA switches from MU EDCA to EDCA, how the backoff are restored ? Proposal: "The backoff values must be resetted and CW is set to CWmin when switching from MU EDCA to EDCA." Rejected – the spec currently says that only the CWmin,max and AIFSN values are updated, not the backoff nor the CW. The backoff and CW are updated based on legacy procedures, using the updated parameters. The intent is not to reset CW and backoff values.
4745 Alfred Asterjadhi 114.13 What is the expectation when the AP wants to not use MU EDCA Parameters anymore? Does it decide to not include the MU EDCA Parameter Set in the Beacon, or does it continue including it and always specify the same values in the MU and normal EDCA Parameter Set elements? Clarify (noting that the second option requires to keep 16 redundant octets in the Beacon). As in comment Revised – agree with the comment. Clarification is added that if the MU EDCA parameter element was not received, the procedure does not apply, as described in the proposed changes in doc 204r0. Include the following in section 3.4 Abbreviations and acronyms Modify 9.4.2.221 MU EDCA parameter set element as follows: MU EDCA Parameter Set element The MU EDCA Parameter Set element provides information needed by non-AP STAs that are UL MU capable for proper operation of the QoS facility during the CP. The format of the MU EDCA Parameter Set element is defined in Figure (MU EDCA Parameter Set element). Element ID Length Element ID Extension MU QoS Info MU Parameter Record MU AC_BK Parameter Record MU AC_VI Parameter Record MU AC_VO Parameter Record Octets: 1 1 1 1 3 3 3 3 MU EDCA Parameter Set element The Element ID, Length, and Element ID Extension fields are defined in 9.4.2.1 (General). For an infrastructure BSS, the MU EDCA Parameter Set element is used by the AP to The most recent MU EDCA Parameter Set element received by a STA is used to update the appropriate MIB values.