information from an MPDU of the PPDU is 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. 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." that are marked with CID 13885, noting to the 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 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/0026r5 that are marked with CID 13886 SR Behavior Overview CIDs 11360 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 other features and functions which have been included in previously approved 802.11 standard amendments, and there are other features that have been included in the past that
have been included with a much lower bar of quality of evidence. Alfred 27.9 289.54 It is difficult to understand what values of the SIG-A related to which of the features. Similar for the terminologies, in certain cases they are not consistent. SRP, SR, DSRP, etc. Suggest to revew carefully so that there is no inconsistencies. Similar observation for the normative behavior. Not all cases are covered from the AP side and also in some cases from the STA side. As in comment. Revise – TGax editor to make changes as shown in 11-18/0026r5 that are marked with CID 11357, with a note to the commenter that other changes presented in in response to other CIDs provide additional improvements in clarity and consistency beyond those marked with CID 11357. Any additional changes needed to satisfy the commenter would require more specificity accompanying the otherwise rather general comment. 13009 Lalam 27.9 289.54 I don't see any technical reason to support two versions of the spatial reuse (OBSS_PD and SRP), while it is not even clear if one version A58brings any gain (especially in heterogeneous deployment with legacy devices present in the network). At least add some pros and cons for each of the two methods and why one should apply one instead of the other. As in comment 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 which requires additional complexity within an implementation and in this case, as if often the case within 802.11, the choice between complexity and performance is left to the implementer. A similar argument is made for the OBSS PD SR mechanism, which likely has a simpler implementation, but is also likely to have a less exacting outcome, hence matching the
13930 Seok 27.9.2.1 291.07 Similar to the spatial reuse, If an HE STA receives a CTS frame immediately after an RTS (e.g., frame) that is a SRG frame, the spatial reuse can be applied to the CTS frame. Insert the following sentence: "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 SRG PPDU that contained an RTS (including a that was ignored following this procedure." See 11-17-LLLLrY 12541 Liwen Chu 27.9.2.1 291.08 I assume that AP also follows trhe same Fix the issue mentioned in comment. See 11-17-LLLLrY 12189 Lv 27.9.2.1 291.15 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 Yuichi 27.9.2.1 291.17 There is no way for HE STA to know that the non-HT PPDU does not carry a certain frame before the end of the PPDU. Remove conditions that will not be known to the receiving STA until the end of the PPDU. See 11-17-LLLLrY 14214 Li 27.9.2.1 291.18 HE PPDU should not be excluded in the first three sub bullets. delete "non-HE" in all the sub bullets. See 11-17-LLLLrY Jinjing Jiang 27.9.2.1 291.20 Public Action frame includes the FTM frame, duplicate items in the bullets? Remove "or an FTM frame" See 11-17-LLLLrY 11741 27.9.2 291.30 Currently, SR_DELAY and SR_RESTRICTED is applicable for both SRP & OBSS-PD. Remove the applicability of SR_DELAY and SR_RESTRICTED for OBSS-PD As in the comment See 11-17-LLLLrY
11736 Ko 27.9.2.1 291.37 According to the subclass 27.11.6 (SPATIAL_REUSE), when a STA transmits a Trigger frame, it is recommended to set the TXVECTOR parameter SPATIAL_REUSE to SR_DELAY or SR_RESTRICTED. Since a Trigger frame is allowed to be sent in a HT or VHT PPDU, there may be other frames aggregated to the Trigger frame in the same PPDU. If an STA transmits a frame based on the OBSS_PD-based SR on the PPDU, STAs solicited by the Trigger frame may not be able to respond to the Trigger frame after the CCA. Therefore, we can define the operation for a STA which received a Trigger frame, for example, the similar operation when the Spatial Reuse field is set to SR_DELAY or SR_RESTRICTED. Add "If the primitive is issued before the end of the PPDU, and a TXOP is initiated within the duration of the PPDU, then the TXOP should be limited to the duration of the PPDU if a Trigger frame is in the PPDU." See 11-17-LLLLrY t BSS
11831 Li 27.9.2.2 293.15 In Table 27-6, the use of 0 and 1 is understood, but this is not setting a value for a particular field. Change 0 and 1 to "yes" or "no". Change 0 and 1 to "yes" or "no". See 11-17-LLLLrY 13855 Fang 27.9.2.2 293.24 Is the value of Non-SRG OBSS PD Max -82 or for the case of OBSS_PD_SR Disallowed = 1? See 11-17-LLLLrY 11829 Li 27.9.2.2 293.41 In Table 27-7, The use of "Spatial Reuse Paraeter Set element not received" set to 0 is not a natural way to say this paramemeter set is receive. Change the wording to "Spatial Reuse parameter set element received" and change the "0" and "1" in this table accordingly. Change the wording to "Spatial Reuse parameter set element received" and change the "0" and "1" in this table accordingly. See 11-17-LLLLrY 11832 Li 27.9.2.2 293.41 In Table 27-7, the use of 0 and 1 is understood, but this is not setting a value for a particular field. Change 0 and 1 to "yes" or "no". Change 0 and 1 to "yes" or "no". See 11-17-LLLLrY 11558 27.9.2.2 293.56 regarding not perform SRP-based SR transmissions", why is this in the section? as in comment See 11-17-LLLLrY 11559 27.9.2.3 294.03 the grammar in the paragraph is undecipherable as in comment See 11-17-LLLLrY 14118 Yuichi 27.9.2.3 294.03 What happens to the case where the HE STA ignores an inter-BSS PPDU but does not initiate countdown because it has nothing to send? The power restriction period should not start in this case. Add description that the power restriction period only starts when the STA starts countdown. See 11-17-LLLLrY
14285 27.9.2.3 294.04 We should consider the case a STA 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. See 11-17-LLLLrY 11942 June Wang 27.9.2.3 294.06 Should have a maximum value (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
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 Liwen Chu 27.9.2.4 303.01 Add the rule that the AIFS rule 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 shown in 11-18/0026r5 that are marked with CID 11816 12192 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 frame 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/0026r5 that are marked with CID 12192 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 shown in 11-18/0026r5 that are marked with CID 13560 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/0026r5 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 in 11-18/0026r5 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, 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 in 11-18/0026r5 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 should be set to positive infinity when an SRP opportunity is identified based on the reception of the PPDU. Remove "or lower". As comment Revise – TGax editor to make changes as shown in 11-18/0026r5 that are marked with CID 12196, note that a STA may choose to use a lower value if it desires. 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/0026r5 that are marked with CID 12198 Lv 27.9.4 299.02 Remove "or As comment Revise – TGax editor to make changes as in 11-18/0026r5 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/0026r5 that are marked with CID 12202 12543 Liwen Chu 27.9.4 299.08 a value 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 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 12545 Liwen Chu 27.11.6 307.36 why OBSS PD is excluded? Fix the issue 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 array 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/0026r5 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/0026r5 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/0026r5 that are marked with CID 11868
12271 Lv 27.11.6 307.59 change "when permitted by 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/0026r5 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/0026r5 that are marked with CID 14308 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 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 in 11-18/0026r5 that are marked with CID 13945 11933 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 rules 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.
12291 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 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. 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 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. 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.