Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Jarkko, Thanks for your comments. Please see my responses inline.
[MKH]: Proposed text in 1224r6 (SC 35.7.4.1) specifies: "If Trigger frame(s) are addressed to an r-TWT
scheduled STA by an r-TWT scheduling AP in a restricted TWT service period with
Broadcast TWT Recommendation field equal to 5, then at least one Trigger frame
shall be an MU RTS TXS Trigger frame with TXOP Sharing Mode subfield equal to
2(#4778).” This provision is specifically for accommodating STA’s p2p traffic and does not apply to r-TWT SP with Recommendation Value 4. Another advantage is that such a distinction allows AP to advertise specific schedules in which it is willing to accommodate p2p traffic. For schedules with Recommendation Value 4, the AP will accommodate r-TWT requests for UL/DL traffic only.
Using rTWT for p2p does not require clock level synchronization or time synchronization. The peer-to-peer link would have to manage its schedule (which can be done at large granularity level) to benefit from the AP assisted approach. If the schedule doesn’t fit, STA can choose not to setup r-TWT for its p2p.
UL/DL TID bitmaps identify which traffic is deemed latency sensitive, which is desired to be delivered with higher priority and is the key reason an r-TWT is setup. I fail to see how prioritizing this traffic in r-TWT would degrade overall QoS? Regarding your concern about poor SP utilization, current r-TWT spec does not limit/restrict transmissions within an r-SP to latency sensitive TIDs only. How traffic is prioritized within an r-SP is ongoing discussion in the group (21/1115); however, that is beyond the scope of this doc (setup). Moreover, the UL and DL TID bitmaps are not strictly dictated by the AP. These are indicated during r-TWT setup for latency sensitive traffic identification and a STA can also indicate these TIDs in the r-TWT Request. Regards, Kumail.
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |