Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
There were no motions during the teleconference yesterday.
The discussion will continue during the Sept 17 teleconference. Regards; Osama. From:
*** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx]
On Behalf Of Ganming (Ming) Hello Tomo Thanks for this info. Does this pass the motion? in which the AP, within a single PPDU, acknowledges one or more frames in an UL transmission from a STA, and triggers the STA for a further UL transmission->where the AP transmits a PPDU which contains Ack
or BlockAck frame and triggering frame. However, this is normative behavior as we discussed before. So it is redundant compared with the second paragraph. The MU cascading sequence may include one or more QoS Data frames with ack policy HTPE Ack and/or Management frame soliciting acknowledgement together with a triggering frame.
Actually, this is typical case in MU cascading. Best wishes Ming Gan 发件人:
*** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx]
代表 Tomo Adachi Hi all, We had a discussion on the MU cascading sequence on today’s TGax call.
The final direction there was as follows:
-
Change the first sentence in 26.5.3 MU cascading sequence to
“An MU cascading sequence is a frame exchange sequence between an AP and one or more non-AP STAs in which the AP, within a single PPDU, acknowledges one or more frames in an UL transmission from a STA, and triggers the STA for a further
UL transmission."
-
Add a sentence,
“The MU cascading sequence may include one or more QoS Data frames with ack policy HTPE Ack and/or Management frame soliciting acknowledgement together with a triggering frame.”, at the beginning of the paragraph that starts with
“The MU cascading sequence may have a different set of transmitters in HE TB PPDUs
…” in 26.5.3. The latter modification was added due to Liwen’s request.
And there were no further comments during the call.
Comments are welcome, especially from those that didn’t attend the call today.
It will be on the agenda again on Sept. 17 call.
Best regards, tomo To unsubscribe from the STDS-802-11-TGAX list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 To unsubscribe from the STDS-802-11-TGAX list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 |