Hi, all:
This email is to invite questions and discuss the SP3 in contribution
11-20/1046r12.
For convenience the SP text is as follows:
Do you agree to add to the TGbe SFD (in R1):
- Restricted TWT schedule may be announced by the AP for peer-to-peer communication.
Discussion:
Here the peer-to-peer communication is intended to cover cases where both STAs in the peer-to-peer link are associated to the infra AP, and the case where only one STA in the peer-to-peer link is associated to the AP. The motivation and scenarios are explained in 11-20/1046r12 slide 5 and slide 9.
The establishment of peer-to-peer link(s) can be either TDLS, which is covered by IEEE 802.11 spec, or other ways out of scope of 802.11 (but feasible and used in practice, e.g. mobile AP and client, or P2P-GO/GCs.)
It's assumed here in the above scenarios, one of the STAs (either a nominated STA in the TDLS case, or the AP role in the other cases) can learn the application/traffic requirement and characterizes the traffic requirement. This can be done using either TWT setup procedure or any in-band or out-of-band/application mechanism. This STA, associated with the infra AP, can set up the restricted TWT session subsequently.
-- Hope this answered the question about the traffic requirement from Qi.
Please note that, TDLS can set up a TWT agreement already. See subclauses 9.6.12.2 and 9.6.12.3 (page 233-234) in Draft P802.11ax D7.0.
In the rTWT mechanism that is to be further developed, I see the need that the aforementioned STA needs to register the peer-to-peer communication for low latency at AP to benefit from whatever protection/resource available per rTWT rule(s). This can be done through extension to the TWT setup frame; and also can use the traffic signaling under discussion proposed by various contributions (TSPEC-lite or alike).
There might be other pieces missing and we can continue to develop details.
But the first step is the proposed SP so the setup procedure can be initiated.
Qi, Hanseul, all, let me know if you have further questions.
Thanks.
Chunyu
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