175 Alfred 25.5.2.3 There are many missing items As in comment. Revised. Asterjadhi in the setting of the TXVECTOR parameters for the Agree. See HE trigger-based PPDU. changes in this Ensure that the list is complete document for the for the Trigger frame Ttrigger frame (according to the fields response and in specified by the trigger frame) document 16-776 and for the UL MU Response fro the UL MU Scheduling (according to the reponse Scheduling fields specified in the HE HE control field variant HT Control field, and default (from DL MU PPDU?) values for those not specified in the field). 176 Alfred 25.5.2.3 When the Trigger Type is not As in comment. Revised Asterjadhi equal to 0 (means MU RTS, MU BAR, MU BRP variants) See resolution in we need to specify that the doc STA shall not solicit an immediate response from the AP to the trigger-based PPDU (e.g., the QoS Null frame if added shall have the Ack Policy to No Ack). 432 Hart 25.5.2.2.1 "AP AP shall not send ... unles For 11ax to be relevant, Revised. the STA is UL MU Capable" all non-APs need to be Removed reference UL MU Capable (e.g. UL to capability OFDMA) See resolution in doc 16/929r1 436 Hart 25.5.2.2.3 Definition of successful is Insert xref Revised unclear Definition of successful is linked to the 460 Daewon Lee 25.5.2.1 How the AP obtains the Add a new section under medium access for DL MU and MU operation regarding Reject. UL MU operation is not EDCA for DL MU and defined. It is not whether EDCA for UL MU either the AP may use DL MU EDCA operation is in chaper 10.22.2 HCF any AC to send the same as 11ac DL MU EDCA contention based trigger frame operation or not. Given that channel access (EDCA) trigger frame is control frame, it or chapter 25.5 MU is not clear what the AC of the operation. Define the trigger frame should be, and details of medium how it would content for access operation for MU. medium (e.g. using which backoff window size, etc)
175 Alfred Asterjadhi 25.5.2.3 There are many missing items in the setting of the TXVECTOR parameters for the HE trigger-based PPDU. Ensure that the list is complete for the Trigger frame (according to the fields specified by the trigger frame) and for the UL MU Response Scheduling (according to the fields specified in the HE variant HT Control field, and default (from DL MU PPDU?) values for those not specified in the field). As in comment. Revised. Agree. See changes in this document for the Ttrigger frame response and in document 16-776 fro the UL MU reponse Scheduling HE control field 176 Alfred Asterjadhi 25.5.2.3 When the Trigger Type is not equal to 0 (means MU RTS, MU BAR, MU BRP variants) we need to specify that the STA shall not solicit an immediate response from the AP to the trigger-based PPDU (e.g., the QoS Null frame if added shall have the Ack Policy to No Ack). As in comment. Revised See resolution in doc 432 Hart 25.5.2.2.1 "AP AP shall not send ... unles the STA is UL MU Capable" For 11ax to be relevant, all non-APs need to be UL MU Capable (e.g. UL OFDMA) Revised. Removed reference to capability See resolution in doc 16/929r1 436 Hart 25.5.2.2.3 Definition of successful is unclear Insert xref Revised Definition of successful is linked to the 460 Daewon Lee 25.5.2.1 How the AP obtains the medium access for DL MU and UL MU operation is not defined. It is not whether DL MU EDCA operation is same as 11ac DL MU EDCA operation or not. Given that trigger frame is control frame, it is not clear what the AC of the trigger frame should be, and how it would content for medium (e.g. using which backoff window size, etc) Add a new section under MU operation regarding EDCA for DL MU and EDCA for UL MU either in chaper 10.22.2 HCF contention based channel access (EDCA) or chapter 25.5 MU operation. Define the details of medium access operation for MU. Reject. the AP may use any AC to send the trigger frame
11-16-0929-02-00ax-cr-ul-mu-operation.docx