Hi Qi,
Your question is related to further detailed designs. There are several ways to do that, for example:
(The implicit ways)
1,We can define the behavior of EHT AP like this: if an EHT AP want to use a quiet interval in conjunction with a restricted SP, quiet intervals
should completely overlap with a restricted SP. An EHT STA would ignore the quiet intervals that overlap with any restricted SPs.
2,if SPs are also announce in the same management frame(e.g. beacon), we can restricted the order of appearance like: if Quiet elements show before
the element defining restricted SPs, those elements are for DFS; if Quiet elements show after the element defining restricted SPs, those elements are for restricted SP protection and can be ignored by EHT STAs.
(The explicit way)
3, An EHT AP can add a bit when setting up restricted SPs to indicate whether those SPs are protected by quiet intervals. EHT STAs would only follow
the rules of low latency prioritization within the SPs and ignore quiet intervals if the bit indicates the existence of protected quiet intervals. Otherwise, EHT STAs should stop EDCA transmission during quiet intervals.
Of course, more work and detailed designs are needed under this general agreement
Regards
Boyce
发件人: Qi Wang [mailto:qi_wang2@xxxxxxxxx]
发送时间: 2020年12月11日
11:12
收件人: Yangbo (Boyce, 2012 NT Lab) <yangbo59@xxxxxxxxxx>
抄送: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBE]
答复: [STDS-802-11-TGBE] Question on Quiet element / 1046r10
Hi Yangbo,
Thanks very much for trying to address my concerns. However, as I stated during the 11be call today, the existing element is to quiet ALL STAs, without making exception for some STAs (e.g., STAs with low-latency traffic).
Using Quite element to selectively allow channel access by some STAs is new, and is a significant departure of the original purpose of Quiet element. How does a STA distinguish the purpose of a Quite element (i.e., for restricted TWT or otherwise) to decide
whether to ignore it or not?
I want to help to response to your and Qi’s question about Quiet element.
I think a reasonable way is to include multiple Quiet elements if there are more than one restricted SPs per Beacon interval. An AP should not protect
the medium outside restricted SPs with quiet element.
Quiet element is already defined in the spec and the spec doesn’t forbid an AP to use Quiet element to mute non-AP STAs for purposes other than channel
measurement. So we are not trying to allow an EHT AP to use Quiet element(in conjunction with SP). The spec has already allowed to do that. What we are trying to do is to let EHT STAs understand an AP’s intention if it announce a quiet interval that completely
overlaps with a restricted SP and EHT STAs can ignore the quiet element(if a EHT STA does not support low latency features, it would also ignore the restricted SP).
Hope that answers your question.
There was a long queue of questions to 1046r10 and I was not able to ask my question.
I am wondering how to use Quiet element to protect real time traffic.
Quiet element was designed to measure channel especially in DFS channels to detect radars.
The Quiet Period is given in units of Beacon periods. Low latency traffic likely transmits more often than once per Beacon period.
I am wondering how you are planning to use the Quiet elements to protect the low latency traffic? Are you planning to include multiple Quiet elements to Beacon or just protect
all time for restricted TWT?
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
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
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