the condition is not a requirement. Yuichi Morioka In order to allow efficient use of SR resource, STA should be allowed to subtract the time it took to determine that the received PPDU is an inter-BSS PPDU from its BO timer. This is especially important to effectively utilize the SR resource, because by the time the BO expires in many cases the OBSS PPDU would be already be finished. Add "If the PHYCCARESET.request primitive is issued before the end of the PPDU, the Backoff counter of the STA may be decremented by the time it took from the beginning of the PPDU the PHYCCARESET.request primitive was issued" Rejected – the concept is interesting, but the proposed resolution is incomplete because it creates a new problem – i.e. the simple subtraction proposed will cause all STAs with a backoff count less than the the determination time to hit zero at the same time causing a collision – a complete proposal needs to deal with this problem. Yuichi Morioka Even if the TXOP is limited to the duration of the PPDU, the STA is allowed to send an SR PPDU that extends beyond the end of the TXOP. This SR PPDU will collide with the response of the MU transmission. Add description as to how the SR PPDU will not collide with response to MU transmission. Revise – see resolution for CID 14278 which adds further restriction. Yusuke Tanaka This rule limits the TXOP obtained by the OBSS_PD mechanism to the duration of the HE MU PPDU to prevent interfering. According to IEEE802.11 2016, start of PPDU shall be within TXOP but end of PPDU could exceed the end of TXOP so limitation of TXOP is not enough and the duration of PPDU must be limited as well. Add "and the duration of transmitting PPDU not exceed the end of the PPDU" after "the TXOP shall be limited to the duration of the PPDU" Revised – agree with the commenter. Apply the changes as proposed in doc . Albert Petrick Missing periods add missing periods the end of all subbullet text in this clause Revised – agree with the comment. Apply the changes as in doc . 8
restrictions because it declared the medium to be IDLE on SR. In the non-zero count case with an empty queue, the countdown begins anyway, because if you have a count and you have what is indicated to be an idle medium, you count down, regardless of your TX queue condition. Graham Smith "If a STA ignores an inter-BSS PPDU following the procedure in 27.9.2.1 (General), using a chosen SRG OBSS_PD level, or a chosen OBSS_PD level shall start an OBSS_PD SR transmit power restriction period." Does not read right. . Replace cited text with "If a STA ignores an inter-BSS PPDU following the procedure in 27.9.2.1 (General), using a chosen SRG OBSS_PD level, or a chosen non-SRG OBSS_PD level, then the STA shall start an OBSS_PD SR transmit power restriction period. " Revised – agree with the comment. Apply the changes proposed in doc . Yusuke Tanaka We should consider the case a STA whose queue is empty ignored an inter-BSS PPDU for receiving opportunity. The STA does not intend transmission which would cause interference, so the OBSS_PD SR transmit power restriction period should not be applied to the STA. Otherwise the restriction period for such a STA, e.g. a light traffic device, is going to be unreasonably long. Two suggestion. 1. OBSS_PD SR transmit power restriction period shall be applied to only a STA which starts countdown of backoff. 2. Define upper limit of OBSS_PD SR transmit power restriction period. Rejected – commenter does not state how the STA would know that it will not cause interference, without this, the proposed change is incomplete. As for applying only when there is a non-zero count, see the resolution for CID 14118. Regarding the proposal for an upper bound, there is no clear answer as to what that upper bound should be, especially given that the EDCA parameters are dynamic. A STA can choose to not use OBSS_PD and thereby avoid the risk of a long restriction period.
what is "Non-OBSS_PD SR Disallowed"? as in comment Revised – agree with the comment. Apply the changes as proposed in doc what are the values of as in comment Revised – Reference normative text for clarification. Apply the changes as proposed in doc Lv Change " to " as comment Revised – agree with the comment. Apply the changes as proposed in doc Mark " set the TXVECTOR parameter SPA- TIAL_REUSE to SR transmissions." – garbled Deleted "SRP-based SR transmissions" in the cited text Revised – agree with the comment. Apply the changes as proposed in doc Mark is a very odd field name Change to Allowed" throughout Rejected – this is set by the AP to allow its STAs to set the bit in SIG-A for their PPDU to the value which is SRP and non-SRG OBSS_PD. Otherwise, its STAs can not set the SIG-A SR value to 15. The proposed new name is therefore less clear than the current one. Propose yoReject unless there is a better proposed name. Yusuke This element also provides information needed by STAs when performing SRP-based spatial reuse. Add SRP-based spatial reuse. Revised – agree with the comment. Apply the changes as proposed in doc Yusuke Delete "SRP-based SR transmissions". As commented. Revised – agree with the comment. Apply the changes as proposed in doc CIDs for clause 27.11.6