44 Ahmadreza 25.5.2 It seems with the same logic Revise; "All HE Reject. Allowing a Hedayat CTS should be included in this based PPDU(s) solicited mix of legacy CTS list: "All HE trigger-based by the Trigger frame response and UL PPDU(s) solicited by the containing ACK/BA or Mu PPDU reponse Trigger frame containing CTS and the length of woud be yeat ACK/BA and the length of the the HE trigger-based another new PHY HE trigger-based PPDU is PPDU is below a TBD mode. below a TBD threshold.". This threshold." is useful when an AP sends data frame to a set of STAs and solicits ACK/BA in response, and sends or MU-RTS to another set of STAs and solicits CTS in one or more 20MHz sub-channels. 170 Alfred 25.5.2.2.1 Some clarifications are needed As in comment. Revised. Asterjadhi in this itemized list: Clear Used AID=0 for indication when Trigger random access. frame(s) or UL MU Response Clarified the order Scheduling in the HE variant of the trigger and HT Control fields are present in BA. the DL PPDU that solicits a It is not necessary Trigger-based PPDU. For to instruct the AP recipient STAs that are not on how to avoid all associated with the AP a possible erroneous random access RU can be settings of the allocated, as such the AID trigger infromation value in this particular case across STAs, such should be 0. Also if the Trigger as different frame is the first frame in the duration. Given the then we need to clarify PHY limitations, that BA/Ack frames are the any AP should second ones (baseline dictates know what to do. them to be the first ones), and last but not least, the information contained in Trigger frames or UL MU See resolution in Response Scheduling (which is doc 16/929r1 the correct terminology to use rather than "Trigger Information field in MAC Header TBD") do not conflict with eath other (or with same signaling in different RUs of the same DL PPDU). Perform the same changes to the 3rd paragraph of 25.5.2.3 as well (those that apply of course).
44 Ahmadreza Hedayat 25.5.2 It seems with the same logic CTS should be included in this list: "All HE trigger-based PPDU(s) solicited by the Trigger frame containing ACK/BA and the length of the HE trigger-based PPDU is below a TBD threshold.". This is useful when an AP sends data frame to a set of STAs and solicits ACK/BA in response, and sends or MU-RTS to another set of STAs and solicits CTS in one or more 20MHz sub-channels. Revise; "All HE PPDU(s) solicited by the Trigger frame containing ACK/BA or CTS and the length of the HE trigger-based PPDU is below a TBD threshold." Reject. Allowing a mix of legacy CTS response and UL Mu PPDU reponse woud be yeat another new PHY mode. 170 Alfred Asterjadhi 25.5.2.2.1 Some clarifications are needed in this itemized list: Clear indication when Trigger frame(s) or UL MU Response Scheduling in the HE variant HT Control fields are present in the DL PPDU that solicits a Trigger-based PPDU. For recipient STAs that are not associated with the AP a random access RU can be allocated, as such the AID value in this particular case should be 0. Also if the Trigger frame is the first frame in the then we need to clarify that BA/Ack frames are the second ones (baseline dictates them to be the first ones), and last but not least, the information contained in Trigger frames or UL MU Response Scheduling (which is the correct terminology to use rather than "Trigger Information field in MAC Header TBD") do not conflict with eath other (or with same signaling in different RUs of the same DL PPDU). Perform the same changes to the 3rd paragraph of 25.5.2.3 as well (those that apply of course). As in comment. Revised. Used AID=0 for random access. Clarified the order of the trigger and BA. It is not necessary to instruct the AP on how to avoid all possible erroneous settings of the trigger infromation across STAs, such as different duration. Given the PHY limitations, any AP should know what to do. See resolution in doc 16/929r1 based
11-16-0929-02-00ax-cr-ul-mu-operation.docx