correctly received and the bit in the SRG Partial BSSID Bitmap field which corresponds to the numerical value of BSSID[39:44] is set to 1." Please specify how to determine the BSSID information from the received MPDU. For example, When the MPDU is a Data or Management frame, the BSSID information is obtained from the BSSID field. When the MPDU is a Control frame, the BSSID information is obtained from the TA field if the RA field is set to a broadcast address. When the MPDU is a Control frame, the BSSID information is obtained from the RA field if the RXVECTOR parameter UPLINK_FLAG is present and set to 1. When the MPDU is a Control frame having the TA field, the BSSID information is obtained from the TA field if the RXVECTOR parameter UPLINK_FLAG is present and set to 0. When the MPDU is a Control frame having the TA field, the BSSID information is obtained from the TA field if the RXVECTOR parameter GROUP_ID is present and set to 63. frame, the BSSID information is obtained from the BSSID field. When the MPDU is a Control frame, the BSSID information is obtained from the TA field if the RA field is set to a broadcast address. When the MPDU is a Control frame, the BSSID information is obtained from the RA field if the RXVECTOR parameter UPLINK_FLAG is present and set to 1. When the MPDU is a Control frame having the TA field, the BSSID information is obtained from the TA field if the RXVECTOR parameter UPLINK_FLAG is present and set to 0. When the MPDU is a Control frame having the TA field, the BSSID information is obtained from the TA field if the RXVECTOR parameter GROUP_ID is present and set to 63." commenter that only a portion of what is requested is valid, as the value of group_id 63 is also used for TDLS and therefore cannot be used as a definitive determinant. The uplink == 0 cases are similar. The broadcast RA cases do not seem worth bothering with. The uplink ==1 cases are valid and now included.
13886 Seok 27.2.3 223.13 "An HE STA that has not received a Spatial Reuse Parameter Set element from its associated AP with a value of 1 in the SRG Information Present subfield shall not classify any received PPDUs as an SRG PPDU." An HE AP STA that has transmitted a Spatial Reuse Parameter Set element is missed. Change as the following: "An HE STA that has not transmitted and not received a Spatial Reuse Parameter Set element to/from its BSS with a value of 1 in the SRG Information Present subfield shall not classify any received PPDUs as an SRG PPDU." Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 13886 SR Behavior Overview CIDs 12716 Mark 27.9 "legacy portion of the PPDU" is not a defined concept, nor is "legacy portion of the DSRP_PPDU" Define portions as the L-STF, and L-SIG fields Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12716 Myles 27.9 289.00 802.11ax includes two spatial resue methods. Both methods are relatively complex and there are doubts about how well they work. It appears both are included because of these doubts.. Presumably the hope is that one mechanism does actually work. However, standards are supposed to be generally about standardising proven mechanisms (preferably one to reduce complexity and risk) or mechanims that are known to work rather than standardising experiments. The 802.11ax draft should be modified to remove at least one of the SR mechanisms. The TG should be confident that the remaiing mechanism actually works. If not then both mechanisms shoukd be removed. Reject – There is no doubt that the SRP SR mechanism is effective when an opportunity to use it is identified. The SRP mechanism relies on measured information that might be subject to some error, but engineering always must include margin for error. The OBSS PD SR mechanism has been proven, in various situations, through simulation, to be effective in producing good outcomes. The standard of quality of the evidence presented in support of the OBSS PD SR mechanism is no different than the standard that has been applied to various features and functions which have been included in previously
11770 Smith 27.9.1 290.01 What a long winded way to describe a possible way to find out the of neighboring APs and of APs that are hidden form the originating AP. I can see that the AP might like to chose a color that none of its STAs sees but in this case the STA is straying from the network area. If you want to do this simply say words to the effect that "an AP may use a Beacon request to establish the color of neighnboring networks." Delete P290 L1 to L16. See 11-17-LLLLrY 11771 Smith 27.9.1 290.21 "A non-AP HE STA that performs spatial reuse operation shall respond to a Beacon request from its associated AP with a Beacon report as described in 11.11 (Radio measurement procedures)." In the sentence aboive this says that an HE AP may use the Beacon report for spatial reuse,, but here it says that a HE STA shall respond to a Beacon request. Hence a STA must support it, but an AP need not. Why can't the AP simply use a STA that does support it? Delete Delete cited text See 11-17-LLLLrY 13151 Qi Xue 27.9.1 290.21 Change this to a 'should' requirement: "A non-AP HE STA that performs spatial operation shall respond to a Beacon request..." As in the comment See 11-17-LLLLrY 14113 Yuichi 27.9.1 290.22 The spec should allow the option for HE STAs to report the utilization of the medium where the HE STAs can not hear the beacon from the OBSS AP. The commenter is willing to provide further details if the group is willing to go in this direction. See 11-17-YYYYrY
OBSS_PD SR Behavior CIDs 12304 27.9.2 290.25 OBSS_PD based spatial reuse operation is defining specific rules and equations when applied to an SRG (SR group). In some managed environments, the definition and settlement of SRG can be done in a proprietary way within an ESS. In less managed environments, such SRG formation would require a specific protocol and specific frame exchanges. The spec should define such protocol to extend the usability of the SRG OBSS_PD SR mode Define the protocol and frame exchanges needed to establish an SRG among neighboring APs. See 11-17-TTTTrY 14091 Guo 27.9.2.1 290.31 There is no "RXSTART.indication" defined in the SPEC change to See 11-17-LLLLrY 13062 27.9.2.1 290.32 The two actions on page 290, it is not if it is (a) and (b) as in line 32 or (a) or (b) as in line 60. Need to make it clear. as in comment See 11-17-LLLLrY 11742 27.9.2.1 290.38 When an AP hosts multiple BSSs, but does not support Multi-BSSID feature (for various reasons), the STAs that are associated to one of the BSS of the AP would not know what other BSSs are that are hosted by the same AP. Hence the STA may perform SR over those packets for other BSSs hosted by the same AP. Fix it. As in the comment. May need some indication from the AP.
11556 27.9.2.1 290.40 regarding "or the received PPDU contains a CTS and a transition from BUSY to IDLE occurred within the PIFS time immediately preceding the received CTS and that transition corresponded to the end of an inter-BSS PPDU that contained an RTS that was ignored following this procedure.", this was predicated on PHY of STA issues with a value equal to BUSY. Is this trying to say that you can't ignore an RTS/CTS? as in comment See 11-17-LLLLrY 14114 Yuichi 27.9.2.1 290.40 "the received PPDU is not a non HT PPDU carrying a response frame...". The recipient only knows the content of the PPDU at the end of the PPDU, which contradicts with line 32 "a) issue a primitive before the end of the PPDU" Remove part that "carrying a response frame" See 11-17-LLLLrY 12188 Lv 27.9.2.1 290.51 An HE STA with should follow the OBSS_PD level based on 27.9.4 Change the following condition to "(defined in 27.9.2.2 (Adjustment of OBSS_PD and transmit power) or 27.9.4 (Interaction of OBSS_PD and SRP-based spatial reuse)). See 11-17-LLLLrY 14213 Yunbo Li 27.9.2.1 290.53 HE PPDU should not be excluded in the first three sub bullets. delete "non-HE" in all the sub bullets. See 11-17-LLLLrY 13152 Qi Xue 27.9.2.1 290.58 Change to "An NDP As in the comment See 11-17-LLLLrY 11257 Albert 27.9.2.1 290.60 Text states "A STA that takes actions (a) or (b) under the conditions ...." Actions (a) or (b) not defined, need more clarity. Sentence needs to be rewritten. What are actions (a) or (b) See 11-17-LLLLrY
11774 Smith 27.9.2.2 291.41 "Adjusting the OBSS_PD and transmit power can improve the system level performance and the utilization of the spectrum." It has been shown that this is not true, 17/0582 shows pretty clearly that this does not work. If the lobby insists on retaining this feature, then at least avoid alternative truths. Delete Delete "Adjusting the OBSS_PD level and transmit power can improve the system level performance and the utilization of the spectrum." See 11-17-LLLLrY 14280 41 291.41 First sentence describes advantages of adjusting the OBSS_PD level and transmit power from the view of system level. However a STA itself can't be aware of system level improvement but can be aware of only the STA's performance by itself. Advantages from the view of the STA should be added, otherwise there is no incentive or motivation for the STA to take adjusting the OBSS_PD level and transmit power. Add description about advantage form the view of the STA like follows; The STA which adjusts the OBSS_PD level and transmit power can ignore transmitted signals received from outside the range which it intends to execute communication and gain opportunity to comunicate with intended partner. See 11-17-LLLLrY 13063 27.9.2.2 291.46 This clause provides the for adjusting OBSS_PD value. However it doesn't state when this change is requested, i.e. what event does trigger this adjustment? as in comment See 11-17-LLLLrY 11777 Smith 27.9.2.2 291.47 Equation 27-3 indicates that the TX power may be less than the simple rule and could, in fact, be set to zero. Seems pretty dumb to me to have the < sign there as it is bad enough already and can one really see devices using less than the permitted power if they were dumb enough to do this anyway? Replace ╘δ± with = See 11-17-LLLLrY
14285 27.9.2.3 294.04 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 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. See 11-17-LLLLrY 11942 June Wang 27.9.2.3 294.06 Should have a maximum (such as maximum allowable TXOP duration) for OBSS_PD SR transmit power restriction period regardless when STA gains TXOP its backoff reaches zero. Since it might take a long time for backoff to reach zero in some cases. Recommend to change to --- This OBSS_PD SR transmit power restriction period shall be terminated at the end of the TXOP that the STA gains once its backoff reaches zero or TBD duration whichever is sooner". See 11-17-LLLLrY 11940 June Wang 27.9.2.3 294.07 Note 1 and Note 2 should be nomative text. Change to nomative text See 11-17-LLLLrY 11781 Smith 27.9.2.3 294.11 "TXP-Wrmax" should not have the "-" Delete "-" See 11-17-LLLLrY
Required subfield set to 0)" 12540 Chu 27.9.2.3 294.27 the notes are too weak. Transferring them to normative requirement. Fix the issue mentioned in comment. See 11-17-LLLLrY 13155 Qi Xue 27.9.2.3 294.27 Add a normative text to cover the following two notes: NOTE 1--The STA can increase but not decrease the chosen SRG OBSS_PD level or non-SRG OBSS_PD level during an OBSS_PD SR transmit power restriction period. NOTE 2--The STA's power is always equal or lower than the minimum TXPWRmax among all TXPWRmax from ongoing OBSS_PD SR transmit power restriction periods. As in the comment See 11-17-LLLLrY 11812 Li 27.9.2.3 294.29 Note 1 is unnecessary. STA should be allowed to decrease its OBSS_PD level to be more conservative. This restriction does not not seem necessary. Remove NOTE 1. See 11-17-LLLLrY 13065 27.9.2.3 295.01 Figure 27-10 is an enigma to me. It needs some explanation and those S1 and D1. as in comment See 11-17-LLLLrY 14216 Yunbo Li 27.9.2.3 295.01 Since restriction period 1, 2 and 3 terminated at the same time, why do we need to introduce multiple restriction periods in the mechanism? Can we keep only single restriction period during the OBSS_PD_SR? See 11-17-LLLLrY June Wang 27.9.2.3 295.10 In Figure 27-10 "S2 max is equal to max (..." should be change to "min (... " as indicated See 11-17-LLLLrY
As a result, the MAC may not be able to determine whether continue backoff countdown because there seems no clear indication from the PHY saying the medium is BUSY/IDLE 14119 Yuichi 27.9.2.4 295.58 There is no requirement on when the STA that issued the primitive during the PPDU re-issues the BUSY indication. If there is no such requirement, multiple SR transmissions will just collide with one another. Define requirement on how the HE STA issues the BUSY indication when a) the inter-BSS is still being sent and b)another HE STA starts an SR PPDU transmission. See 11-17-LLLLrY 12542 Liwen Chu 27.9.2.4 303.01 Add the rule that the AIFS rule still needs to be respected. As in comment See 11-17-LLLLrY SRP Behavior CIDs
11816 Li 27.9.3 296.18 According to definition of SRP PPDU, it is the PPDU that contains trigger frame, so it has to be a DL PPDU. However, in this sentence "ensuing uplink SRP_PPDU", it is referred to as uplink PPDU. This is consistent. I think this "PPDU" is meant to say the trigger-based PPDU. If so, please correct the wording. change to PPDU" Revise – TGax editor to make changes as in 11-18/0026r2 that are marked with CID 11816 Lv 27.9.3 296.18 Only HE SU or HE EXT SU PPDU can set the SPATIAL_REUSE field in HE SIGA to SR_DELAY. Is it necessary to specify that the SR field in the Common Info field of the trigger frame shall not be set to SR_DELAY? If so, what about SR_RESTRICTED? Remove the sentence "An AP sending a trigger shall not set the SR field in the Common Info field of the trigger frame to SR_DELAY." Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12192 13560 LEE 27.9.3 296.18 No clear description and/or defination is provided what SRP_PPDU is. Please provide the description and definition of SRP_PPDU Revise – TGax editor to make changes as in 11-18/0026r2 that are marked with CID 13560 13937 Seok 27.9.3 296.18 "...from performing SR transmission during the ensuing uplink SRP_PPDU duration." Definition of the SRP_PPDU is missed. Include the definition of the SRP_PPDU in clause 3.2. Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 13937 27.9.3.0 296.24 If the STA received a Trigger frame carried in HE MU PPDU with SR_RESTRICTED indication, DSRP_PPDU-based spatial reuse can not initiate? Clarify. If so add a exception rule into the conditions below. Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 14291
13563 LEE 27.9.3.1 297.01 By definition in Clause 3, SR_PPDU with underscore (not SR PPDU) is the correct description Change SR PPDU to SR_PPDU Accept 12075 Jing Ma 27.9.3.2 297.21 Even an HE STA identifies an SRP opportunity, SRP_PPDU-based SR transmission may not work because of the specification of the interaction between the MAC and PHY is not clear enough. Here, the HE STA may not be able to continue the backoff countdown within the HE TB PPDU duration because the medium condition may indicated as BUSY until the end of the ongoing HE TB PPDU. Based on the PHY receive procedure (see 28.3.21 HE receive procedure), when signals come, the PHY measures signal power and issues channellist) to the MAC. After successfully receiving the HE-SIG-A, the PHY issues then set due to No Matched BSS color in case of spatial reuse here. Then the PHY may maintain channellist) until the end of the current PPDU duration unless received. However, the MAC only ignores 27.9.3.1 DSRP_PPDU ) which means that the Add the specification that the MAC issues to make the PHY recheck the status of the medium which is similar with OBSS-based SR operation(see 27.9.2.1 General) Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12075 which effectively change the phrase “may ignore the to “may issue a which causes the discard of the incoming PPDU. Note that despite the name of the SAP, the entire PHY is reset to an end of RX state. The PHY then reverts to a search mode with sensitivity at -82 dBm, but meanwhile, the energy of the discarded PPDU continues to arrive – this energy will not cause a new detection event at -82 dBm because the preamble has passed. The discarded PPDU can only trigger BUSY medium now based on ED, which is -62 dBm, and above that, no SR can take place. So the interaction between MAC and PHY is completely specified in such a manner that the SR mechanism will operate correctly, provided that the PPDU being discarded is not at a level > -62 dBm.
measured path information and the SRP parameter information together have already indicated that an SR transmission is safe. The generic PD levels no longer matter in this case. 12196 Lv 27.9.4 298.53 The OBSS_PD level should be set to positive infinity when an SRP opportunity is identified based on the reception of the PPDU. Remove "or lower". As comment Reject – a STA may choose to use a lower value if it desires. There is no need to restrict the choices to simply positive infinity and the other values of OBSS_PD that are determined according to the other rules in 27.9 12544 Liwen Chu 27.9.4 298.53 "positive infinity or lower" change "positive infinity or lower" to "positive or higher"??? This contradict with the further detecting DSRP frame during SRP opportunity. Fix the issue mentioned in comment. Reject – the reader has failed to notice the additional qualifier of “as it applies to this PPDU” 12198 Lv 27.9.4 298.65 SR_DELAY is not a value in the Common Info field SPATIAL_REUSE of a Trigger frame Remove "or SR_DELAY" Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12198 12200 Lv 27.9.4 299.02 Remove "or lower" As comment Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12200, which modify the applicability of the OBSS_PD level in question, but do not acquiesce to the commenter’s request for removal of “lower” 12202 Lv 27.9.4 299.03 Add the following sentence at the end of the paragraph "and may use a value equal to the receive power of the HE TB PPDU plus 1 dB for the level for the duration of this HE TB PPDU" As comment Revise – TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12202 12543 Liwen Chu 27.9.4 299.08 a of negative infinity for the OBSS_Pdlevel contradicts with As in comment Reject – the reader has failed to notice the additional qualifier of “as it applies to this PPDU”
12204 Lv 27.9.4 299.09 Remove "and shall use a value equal to the receive power of this PPDU minus 1 dB for the ED level for the duration of this PPDU" As comment Accept SPATIAL_REUSE parameter of the TXVECTOR CIDs Liwen Chu 27.11.6 307.36 why OBSS PD is excluded? Fix the mentioned in comment. Reject – the condition is HESRP implemented, so this only relates to the SRP case. 12546 Liwen Chu 27.11.6 307.39 HE MU, HE SU have no of four values? Clarify it Reject – see the definition of the for each of the HE PPDU types. 11932 June Wang 27.11.6 307.58 "when permitted by other conditions," is vague provide references such as "as permitted by other conditions in ... subclauses." Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 11932 12269 Lv 27.11.6 307.58 The subfield in the SR Control field indicates whether non-AP STAs that are associated with the AP that transmitted this element may set the TXVECTOR parameter SPATIAL_ REUSE to SR transmissions.So here should be "may" not "shall". as comment Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12269 11868 Li 27.11.6 307.59 There should be a reference section for the "other conditions". Either add a section number as a reference for the "other conditions", or list the conditions when this field is set to and when it is se to SRP_DISALLOWE Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 11868
12271 Lv 27.11.6 307.59 change "when permitted by other conditions" to "when the sub- field of the SR Control field of the most recently received Spatial Reuse Parameter Set element from its associated AP is equal to 1." as comment Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12271 14308 27.11.6 307.60 Need to clarify "other conditions". As commented. Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 14308 Liwen Chu 27.11.6 308.01 even if the SRP Disallowed announced by the AP is 0??? Clarify it Reject – yes, the AP is free to do what it desires, despite any instructions it might have given to the associated STAs. 13945 Seok 27.11.6 308.12 "An HE STA shall set the TXVECTOR parameter SPATIAL_REUSE to for a PPDU containing an FTM or NDP Announcement frame." In a same logic, an HE STA shall set the TXVECTOR parameter SPATIAL_REUSE to for a PPDU containing the ACK frame of an FTM frame. As in comment. Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 13945 June Wang 27.11.6 308.15 "An HE STA that transmits an HE SU PPDU or an HE ER SU PPDU that contains a Trigger frame should set the TXVECTOR parameter SPATIAL_REUSE to SR_DELAY." It is not clear when to set SR_DELAY provide reference such as 27.9.2.1. Reject – this subclause is the one that sets out the and limitations for the value of the SPATIAL_REUSE parameter within the TXVECTOR. There are no further limitations other than what is described here. If the commenter is uncomfortable with the allowed freedom of choice on the part of the transmitter, he should offer a specific rule that he wishes to include in the draft.
11935 June Wang 27.11.6 308.50 ... if the STA is an HE non-AP STA and the SR Disallowed subfield of the SR Control field of the most recently received Spatial Reuse Parameter Set element..." This should be "SRP Disallowed subfield" instead of "SR Disallowed subfield". as indicated Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 11935 11936 June Wang 27.11.6 308.50 "or, if permitted, to this is redudant since the condition for setting is already described in preceding paragragh in line 39-48 delete "or, if permitted, to Reject – the condition is not redundant, but additive. The paragraph at L39-48 offers an option of setting remains an option even if the condition in the paragraph at L50-54 is met. If the text is deleted from L50-54, then when the condition of L50-54 is met, the option given in L39-48 is not allowed, but the draft wants to allow that option, even under the condition of L50-54. 12273 Lv 27.11.6 308.50 There is no "SR Disallowed subfield " in the SR control field. The SRP Disallowed subfield in the SR Control field indicates whether SR transmissions are allowed or not at non-AP STAs that are associated with the AP. So, only TXVECTOR parameter SPATIAL_REUSE of an HE PPDU shall be set to SRP_DISALLOW if the HE PPDU does not contain a trigger frame and the subfield of the SR Control field of the most recently received Spatial Reuse Parameter Set element from its associated AP is equal to 0. please clarify it Revise - TGax editor to make changes as shown in 11-18/0026r2 that are marked with CID 12273
Ryu 27.11.6 308.50 One more condition to set the TXVECTOR parameter SPATIAL_REUSE to should be added. Modify the text as: A STA shall set the TXVECTOR parameter SPATIAL_REUSE of an HE PPDU to SRP_DISALLOW or, if permitted, to if the STA is an HE STA and the SR Disallowed subfield of the SR Control field of the most recently received Spatial Reuse Parameter Set element from its associated AP is equal to 1 or if the STA has not received a Spatial Reuse Parameter Set element from its associated AP. Reject – the default condition is that the STA has a choice on the setting, and is only restricted in its choice if the AP this restriction by sending the element. In the absence of the AP sending the element, the AP is allowing the STA to have the choice, rather than directing the choice of the STA. 14310 27.11.6 308.50 This paragraph defines for only non-AP STA, but rules for AP should be defined. Add the following condition at the end. "if the STA is an HE AP and the SR Disallowed subfield of the SR Control field of the most recently transmitted Spatial Reuse Parameter Set element is equal to 1" Reject – the sixth paragraph of the subclause already gives the AP permission to make this setting. There is not and does not need to be a correspondence or dependenct with regard to the setting that the AP imposes upon its member STAs through the SRP Disallowed field value. 14311 27.11.6 308.50 If non-AP STA has not received a Spatial Reuse Parameter Set element from its associated AP, the STA shall set the TXVECTOR parameter SPATIAL_REUSE to SRP_DISALLOW. As commented. Reject – the default condition is that the STA has a choice on the setting, and is only restricted in its choice if the AP makes this restriction by sending the element. In the absence of the AP sending the element, the AP is allowing the STA to have the choice, rather than directing the choice of the STA.