CIDs Spatial Reuse CIDs. 15646 27.11.6 365.51 Fix inconsistency between the following two sentences: pp356LL51 "An AP with set to true that transmits an HE ER SU PPDU should set the TXVECTOR parameter SPATIAL_REUSE to SRP_DISALLOW" Vs pp357LL16 "An HE AP that transmits an HE SU PPDU or an HE ER SU PPDU that contains a Trigger should set the TXVECTOR parameter SPATIAL_REUSE to SR_DELAY." As in the comment Revise – TGax editor to make changes as in 11-18/1410r4 that are marked with CID 15646, which add a qualifier to the first citation that excludes triggers and the commenter to note that there is not an actual contradiction, as both statements are recommendations and not requirements. 15705 James June Wang 348.20 Does the statement means the restriction of TXOP limit related SR_RESTRICTED in the above paragraph shall follow the conditions of 10.22.2.8 TXOP limits ? Please make the statement easier to read. "The restriction, in addition to the TXOP limit, of the PPDU duration within the TXOP is included in the above paragraph related to SR_RESTRICTED as there are conditions where the TXOP limit Please clarify. Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 15705, which delete the note, as the note does not seem to add any useful information. 2
addressesd to the STA, at least one MPDU is correctly received, etc. To change the language, for example, to “unless all outstanding” sort of makes the language sound like if this one condition in this location is met, then the other conditions found throughout the standard can be ignored, but this is not true. John Coffey 346.06 This section discusses continuing an existing backoff procedure even though another PPDU has been detected. By 'continuing' a backoff procedure, the STA (it seems) performs CCA in each new slot, including preamble detect. But the CCA requirements for preamble detect assume (for good reason) an 'otherwise idle' channel (that is, other than the new PPDU arriving), and that's important for the STA to be able to achieve the required 90% detection probability within aCCATime. What are the requirements for CCA when an existing backoff procedure is continued? I.e., though there may be an 'SRP opportunity', permitting the STA to 'eschew' updating the NAV, does that mean that the channel is considered to be 'otherwise idle' for purposes of CCA, or not? There are several possibilities, of which the proposed change is just one, but at the very least the spec Add after first sentence "For purposes of the countdown of an existing backoff procedure, the channel shall not be considered "otherwise idle" for the duration of the SRP opportunity"; for purposes of the countdown, the HE STA should detect the beginning of a PPDU at a received power level of or greater within aCCATime with probability at least 90%." Reject – if the ignored signal is anything above -82 dBm, then the detection of a signal at -82 dBm will be impossible, so the proposed requirement cannot be added. The group does not see the need for a performance requirement, as the receiver will naturally view any incoming signal with sufficient SINR, where the noise component of that SINR will include the signal that is being ignored, as decodable and will decode it. - 3
needs to define something, and not leave implementers to guess. 15796 Segev 27.11.6 357.00 Section 27.11.6 SPATIAL_REUSE describes a TXVector in the occurance its an FTM frame. Spatial reuse special consideration should not consider FTM frames as part of the Tx Vector because these are not frames but are management frames used for negotiation. HE format for FTM can be used as part of negotiation but not beyond that, using HE format for FTM measurement is not backward compatible and will make existing devices non-standard compliant. "An HE STA shall set the TXVECTOR parameter SPATIAL_REUSE to PROHIBITED for a PPDU containing an FTM or NDP Announcement frame and in any frame that is transmitted as a response to an FTM or NDP Announcement frame." P. 357, (D3.0). Remove the special consideration (L.10-13) for SPATIAL_REUSE of FTM negotiation frames as FTM frame used for negotiation does not require special consideration for spatial reuse, furthermore an FTM frame used for measurement cannot be transmitted in HE format: "An HE STA shall set the TXVECTOR parameter SPATIAL_REUSE to PROHIBITED for a PPDU containing an FTM or NDP Announcement frame and in any frame that is transmitted as a response to an FTM or NDP Announcement frame." P. 357, L.10-13 (D3.0). Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 15796, which removes the mention of the FTM frame, as appropriate. Segev 27.11.6 357.00 Section 27.11.6 SPATIAL_REUSE describes a TXVector in the occurance its an FTM frame. Spatial reuse special consideration should not consider FTM frames as part of the Tx Vector because Remove the special consideration (L.10-13) for SPATIAL_REUSE of FTM negotiation frames as FTM frame used for negotiation does not require special consideration for Revise – TGax editor to make changes as in 11-18/1410r4 that are marked with CID 15796, which removes the mention of the FTM frame, as appropriate. Note that CID 15797 text changes are
these are not frames but are management frames used for negotiation. Using HE format for FTM measurement frames will make 802.11-2016 STA none standard compliant. "An HE STA with set to false may set the TXVECTOR parameter SPATIAL_ REUSE to SRP_DISALLOW for any PPDU that is not an HE TB PPDU or an NDP PPDU or a PPDU containing an FTM or NDP Announcement frame and that is not a frame that is transmitted as a response to an FTM or NDP Announcement frame" P.357 L.36,37 spatial reuse, furthermore an FTM frame used for measurement cannot be transmitted in HE format: "An HE STA with set to false may set the TXVECTOR parameter SPATIAL_ REUSE to SRP_DISALLOW for any PPDU that is not an HE TB PPDU or an NDP PPDU or a PPDU containing an FTM or NDP Announcement frame and that is not a frame that is transmitted as a response to an FTM or NDP Announcement frame" redundant to the text changes for CID 15796. 15798 Segev 27.11.6 357.00 Using HE format for FTM measurement frames will make 802.11-2016 STAs implementing FTM non standard compliant, using HE format for FTM negotiation does not require special Spatial Reuse considerations "of any HE PPDU to PROHIBITED, unless the HE PPDU contains an NDP, an FTM or an NDP Announcement frame or is a frame that is transmitted as a response to an FTM or NDP Announcement frame." P.357 L48,49 of any HE PPDU to PROHIBITED, unless the HE PPDU contains an NDP, an FTM or an NDP Announcement frame or is a frame that is transmitted as a response to an FTM or NDP Announcement frame." Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 15796, which removes the mention of the FTM frame, as appropriate. Note that CID 15798 text changes are redundant to the text changes for CID 15796.
16937 Xiaofei Wang 27.2.3 255.38 Not sure what function this following sentence serves "An HE AP that has not transmitted a Spatial Reuse Parameter Set element with a value of in the SRG Information Present subfield may classify received PPDUs as SRG PPDUs using information that it has not transmitted." There is no normative behavior or interactions with other devices and seems to be only implementation, which should be removed remove the sentence "An HE AP that has not transmitted a Spatial Reuse Parameter Set element with a value of 1 in the SRG Information Present subfield may classify received PPDUs as SRG PPDUs using information that it has not transmitted." Reject – the sentence allows an AP to implement SRG SR without requiring its associated STAs to also implement SRG SR. Without this sentence, it is not if an AP would be allowed to do this. Seok 27.11.6 357.12 "An HE STA shall set the TXVECTOR parameter SPATIAL_REUSE to for a PPDU containing an FTM or NDP Announcement frame and in any frame that is transmitted as a response to an FTM or NDP Announcement frame." The Format And Bandwidth field (Table 9-272 (Format And Bandwidth field)) in the FTM Parameters element indicates the requested or allocated PPDU format and bandwidth that can be used by Fine Timing Measurement frames in an FTM session. Because Table 9-272 does not have the HE PPDU, the HE PPDU can't be used by Fine Timing Measurement frames in an FTM session. Please remove the "an FTM or" from the sentence. Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 15796, which removes the mention of the FTM frame, as appropriate. Note that CID 17020 text changes are redundant to the text changes for CID 15796.
Seok 27.11.6 357.36 "An HE STA with set to false may set the TXVECTOR parameter SPATIAL_ REUSE to SRP_DISALLOW for any PPDU that is not an HE TB PPDU or an NDP PPDU or a PPDU containing an FTM or NDP Announcement frame and that is not a frame that is transmitted as a response to an FTM or NDP Announcement frame." The Format And Bandwidth field (Table 9-272 (Format And Bandwidth field)) in the FTM Parameters element indicates the requested or allocated PPDU format and bandwidth that can be used by Fine Timing Measurement frames in an FTM session. Because Table 9-272 does not have the HE PPDU, the HE PPDU can't be used by Fine Timing Measurement frames in an FTM session. Please remove the "an FTM or" from the cited sentence. Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 15796, which removes the mention of the FTM frame, as appropriate. Note that CID 17021 text changes are redundant to the text changes for CID 15796. 17022 Seok 27.11.6 357.48 "If the subfield of the SR Control of the most recently received Spatial Reuse Parameter Set element from its associated AP is equal to 0, or if STA has not received a Spatial Reuse Parameter Set element from its associated AP, the STA shall not set the TXVECTOR parameter SPATIAL_REUSE of any HE PPDU to Please remove the "an FTM" from the cited sentence. Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 15796, which removes the mention of the FTM frame, as appropriate. Note that CID 17022 text changes are redundant to the text changes for CID 15796.
TB PPDU is used for determine the SRP value instead of the Trigger frame in the SRP PPDU, the STA may issue a as well. There are two more "due to the receipt of a SRP PPDU" in the same paragraph (P345L35 and L45) and they seems to be redundant too. Yoshio Urabe 346.50 The meaning of "Acceptable Receiver Interference Level_AP" seems to be wrong. The sentence says, in short, Acceptable Receiver Interference Level = Recent (N+I) + Requred SNR (except the margin), which seems to be a required RSSI, not an acceptable interference level. It should be: (Acceptable Receiver Interference Level + Recent (N+I)) = Received Signal Power - Required SNR, where the sum in the left term is performed in true value, not in dB. This can be rewritten as: Acceptable Receiver Interference Level (dB) = Signal Power - Required SNR) / 10) - 10^((Recent (N+I) / 10)). The "Received Signal Power" above should be derived from UL Target RSSI for each user. So we should calculate Acceptable Receiver Interference Replace "should be set to the ambient noise plus interference power level observed at the AP immediately prior to the transmission of the Trigger frame plus the minimum SNR value that yields ... ensuing uplink HE TB PPDU, minus a safety margin value ..." with "should be set to the minimum value among the values of (the value of UL Target RSSI minus the minimum SNR value that yields ... ensuring uplink HE TB PPDU) for each User Info field assigned within the bandwidth corresponding to the SRP field of the Trigger frame, minus a safety margin value ...". Revise – TGax editor to make changes as shown in 11-18/1410r4 that are marked with CID 17083, which remove the noise plus interference term and substitute UL Target RSSI which should already have been calculated to account for the N+I term and changes plus to minus to get a noise limit, which might very well be equal to N+I, while leaving the safety margin adjustment in place. Note that the equation could just state that the Acceptable interference is N+I minus safety margin, but this does not account for a case when the AP might suggest a target RSSI that includes a safety margin already.