mechanism rather than mechanisms. 723 27 55 The TWT may be signaled to contain at least one RU for random access. The clause 25.13.2 is not using TWTs to specify when the UL MU Random access is in use. Please harmonize the both clauses to use the same mechanism. Harmonize clause 25.13.2 and this clause to use the same power save mechanisms for the random access. Revised Agreed in principle and revised the text to provide the details of signalling in the TWT element. TGax Editor to make the changes as in v0.docx 779 67 3 The power save mechanism for UL OFDMA looks very similar to TWT mechanism. Why two similar mechanisms are needed? Combine the power save mechanisms for OFDMA random access and the TWT. The random access is used by the STAs, so it coudl make sense if there are two separate Cascaded bits, one for random access and other for the TWT SPs and trigger frames. Revised There is no need for 2 separate Cascaded bits as proposed by the Commenter. The save mechanism need not be differentiated for associated and unassociated STAs with respect to random access procedure. The value in the TWT Flow Identifier subfield in the TWT element distinguishes the TWT SP for random access operation or for scheduled operation. This subclause is mainly needed to illustrate the power save for random access, while reference is made to TWT element for signalling of start time of Trigger frames for random access. TGax Editor to make the changes as in access_v0.docx 780 67 43 The power save rules when an HE STA may go Clarify more clearly when the STA should or Revised TGax Editor to make the changes as in
to doze are not clear. Clarify what is the preferred operation instead of two MAY statement on alternative signaling. even shall stay awake. And when it may go to Doze. access_v0.docx 1087 67 9 Trigger frame start time in a Beacon frame can be indicated by TWT element Replace "Trigger frame start time(s)" with "TWT parameter sets" Revised Modified the Trigger frame start times by “start times of Trigger frames” TGax Editor to make the changes as in access_v0.docx 1088 67 31 Trigger start time in a Beacon frame can be indicated by TWT element Replace the tex: "When an HE STA receives a Beacon with the value of Trigger frame start time for random access, it may enter the doze state till expiration of the value indicated in the Beacon." with the text: "When an HE STA receives a TWT element in a Beacon with the TWT Flow Identifier set to 2, it may enter the doze state till the Target Wake Revised Accepted the text with inclusion of the additional text value of 1 in the Broadcast subfield along with the in the TWT Flow Identifier TGax Editor to make the changes as in v0.docx
field is set to 0. Also, Cascade indication of 0 only implies that there will not be any further UL MU transmission, and it does not give any information on DL transmission. Therefore, the STA cannot go to doze state unless it is clear that there's no DL traffic for the STA. procedure in a Trigger frame with Cascade Indication field set to 0 and More Data (MD) subfield of the most recently received downlink frame intended to it is set to 0, it may enter the doze state immediately until the end of the TWT SP." Therefore, entering to the doze state is completely dependent only on the OBO count itself for transmission of UL PPDU. Revision History: Rev 0: Initial version of the document