legacy PPDU behaviour that is described in the baseline. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 4801. 4802 Alfred Asterjadhi It seems BQR Trigger frame is not allowed in the A-MPDU content (See 9.7.3). I don't think it is the case. Please amend to fix the inconsistency. As in comment. Rejected- The purpose of BQR is for AP to learn the channel availability of the STAs to help the following DL or UL data transmission. Aggregating BQR with data doesn’t provide benefits while complicating the implementation. TGax editor makes no changes on CID 4802. 4803 Alfred Asterjadhi This is a way to say that reception of the BQR Trigger frames is optional. Find a less weird way to say the same. As in comment. Revised- in principle. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 4803 4804 Alfred Asterjadhi QoS Data cannot be added because the BQR variant Trigger frame does not have TID AGG limit and MU Minimum Start Spacing indications, etc. Please remove QoS Data from the sentence. Also no need to indicate that "when the AP has indicated its support in the A-BQR Support... because the AP sends the BQR variant Trigger frame only if it supports Rx of the info. As in comment. Revised- Agree in principle TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 4804. 5179 Dorothy Stanley Regarding "Downlink MU-MIMO On Partial Bandwidth Rx", Figure 9-589cl and Table 9-262aa have "DL MUMIMO On Partial Bandwidth" make field naming consistent Revised- Agree in principle. Per proposed resolution of CID 4804, this sentence will be removed. TGax editor makes changes as shown in 11-17/1286r1
that are marked with CID 5179 5180 Dorothy Stanley Regarding "An AP shall not transmit to a STA an HE MU PPDU with the allocating spatial streams to more than one recipient STA, unless the STA sets the Downlink MU-MIMO On Partial Bandwidth Rx subfield of the HE Capabilities element to 1.", what is the intent of not allowing DL MU-MIMO w/ HE MU PPDU if the STAs only support full bandwidth? Is the intent to use VHT PPDU? I would think in the future when all the devices are HE, we would not want a mix of VHT and HE PPDU's Allow DL with HE MU PPDU to HE STAs that do not support partial bandwidth. Revised- Agree in principle. Agree in principle. Per proposed resolution of CID 4804, this sentence will be removed. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 5180 5181 Dorothy Stanley I can't find a definition for "DL OFDMA With PPDU". I can't find an HE Capabilities element with "DL OFDMA With MIMO Support" field. Define the terms so the paragraph makes sense. Revised- Agree in principle. Per proposed resolution of CID 4804, this sentence will be removed. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 5181. 5182 Dorothy Stanley Regarding "The STA that receives a BQRP variant Trigger shall follow the rules defined in 27.5.2.3 (STA behavior) to generate the HE trigger-based PPDU when the Trigger frame contains the STA's AID in any of the Per User Info fields; otherwise the STA shall follow the as in comment Revised- in principle. A non-AP STA can use UL random access only if it claims the capability (i.e. set OFDMA RA Supports bit in HE MAC Capabilites to 1). Proposes to add a qualifier in the sentence to clarify. TGax editor makes changes as shown in 11-17/1286r1 MIMO 56
5980 Jarkko Kneckt It is unclear whether BQRP Trigger variant that allocates RUs for random access requires that a HE trigger-based PPDU transmitted in the RU for random access contains a BQR information in the field. Please clarify is a STA that detects RUs for random access required to transmit BQR reports in a PPDU in a RU allocated for random access. Please clarify is the same requirement used for other Trigger variants as well? Rejected- A STA who detects RU that is allocated for OFDMA random access in BQRP Trigger variant doesn’t have to use OFDMA random access if it has been named in other RUs. TGax editor no changes on CID 5980. 5981 Jarkko Kneckt The non-AP STA should not be forced to perform random access. The use of random access for the BQR transmission should be voluntary for the STAs. If all STAs are required to transmit BQR in random access when a Trigger contains random access RUs, the power consumption of hte STA increases unnecessarily and transmisison overhead in random access becomes high. The non-AP STAs transmission in the RUs allocated for random access should be optional. Change the wording to say that if RUs for random access are included a non-AP STA may respond... Revised- Agree in principle. Per resolution of CID 5182, add qualifier to regulate when a STA can use OFDMA random access to report the BQR. TGax editor makes no changes on CID 5981. 5982 Jarkko Kneckt The BQR support in AP and STA is already described in 35 -39. The second bullet has a lot of repetition. delete the end of hte sentence. Delete:"when the AP has indicated...". Rejected- BQR is optional function for AP and STA, it is necessary to have these sentence to clarify the condition that BQR can be used. TGax makes no changes on CID 5982. Control
7089 Junichi Iwatani There is no definition for "broadcast RU" Define or explain Revised- Adding definition of broadcast RU in section 3.2. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 7089. 7226 Katsuo Yunoki STA behavior after receiving MU DL PPDU should be explained. (e.g. how to respond ACK, Block ACK) STA behavior after receiving MU DL PPDU should be explained. (e.g. how to respond ACK, Block ACK) Rejected- The ACK/BA procedure for the DL MU is defined in section 27.4. There is no need to repeat same information in two places of the spec. 7385 Laurent Cariou It is not mentioned on which bandwidth the report is provided, while the bitmap depends on the bandwidth Clarify Rejected- It is already defined in section 9.2.4.6.4.7. TGax editor makes no changes on CID 7385. 7571 Liwen Chu The channel can be used by both UL and DL MU. Move the subclause outside of DL MU subclause and change the title accordingly. As in comment Revised- Per proposed resolution for CID 6165, move 27.5.1.3 to 27.5.6 making it general to both UL and DL operation. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 7571. 7572 Chu Add management frame after QoS Null, QoS Data frames As in comment revised- in principle. Not management frame but rather Action No Ack frame. There is a table that we call out explicitly for these types. See suggestion TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 7572. 1 11
8495 Robert Stacey DL With MIMO PPDU is not defined. There is no such thing as a DL OFDMA With MIMO Support field. The capability that most closely resembles this is the DL On Partial Bandwidth field. Describe in terms of TXVECTOR parameters. Revised- Agree in principle. There is no definition of DL OFDMA with MIMO PPDU. DL OFDMA with MIMO is a feature defined in Table 9-262aa. TGax editor changes as shown in 11-17/1286r1 that are marked with CID 8495. 8496 Robert Stacey "The Type and Subtype subfields ... may be different... ": Meaningless statement. Remove statement Rejected- The sentence helps to clarify the Type and Subtype settings of MPDUs transmitted in different RU of the same HE MU PPDU TGax editor makes no changes on CID 8496. 8497 Robert Stacey "Two STA-ID fields in HE-SIG_B..." We hide the PHY details behind the PHY service interface so this statement should be made in terms of the TXVECTOR parameter STA_ID_LIST. Since STA_ID_LIST has a subclause of its own (27.11.1) might as well do it there. Define in terms of TXVECTOR parameters: "An AID shall appear only once in the TXVECTOR parameter array A statement regarding the 2046 entry can be made in the PHY clause itself. The TXVECTOR just needs to identify the used resources. HE-SIG-B is then built (in the PHY) using this infomation and "2046" entries added as needed. Revised- Agree in principle. Propose to modify the following sentence for consistency. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 8697. 56
8593 Sheng Sun what does "channel availability" mean? clarify Rejected- Kindly refer to section 9.2.4.6.4.7 Bandwidth Query Report (BQR) Control for the per 20MHz CCA info. TGax editor makes no changes on CID 8593. 8696 Sigurd Schelstraete "The transmission of each RU in an HE MU PPDU shall be padded to end at the same time". This requirement is already covered by the various decriptions of PHY and MAC padding. Since there is no further information on how to implement the padding here, it is better to change this to an informative statement. Change to "The transmission of each RU in an HE MU PPDU are padded to end at the same time" Rejected- Padding is a mandatory behavior for DL MU operation. The current sentence provides just sufficient information. TGax editor no changes on CID 8696. 8697 Sigurd Schelstraete is no "DL OFDMA With MIMO Support field" in HE Capabilities. Should this be "DL MUMIMO On Partial Bandwidth" field? Clarify Revised- Agree in principle. The right HE Capabilities bit should be refered. Per proposed resolution of CID 4804, this sentence will be removed. The corresponding sentence in to 59 is modified correspondingly. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 8697. 8699 Sigurd Schelstraete "allocating DL MU and UL MU resources". Section 27.5.1.3 is called "HE bandwidth query report operation for DL MU". Should the title be changed or should UL MU resources be deleted? Clarify Revised- Per CID 6165, move 27.5.1.3 to 27.5.6. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 8699.
9467 xun yang "A non-AP STA with A-BQR Support subfield of its HE Capabilities element equal to 1 delivers bandwidth query reports (BQRs) to assist the AP in allocating DL MU and UL MU resources in an efficient way." "Asist" here is not clear. How does BQR information "asist" AP allocate the MU resources? Please clarify. Rejected- The commentor asked for clarification of “asist”. Once the AP received the channel availability information from STAs, it is up to the AP to utilize the information. So “asist” here is really implementation dependent. Implementation details should not be present in the spec text. TGax editor no changes on CID 9467. 9468 xun yang Can AP solicit BQR more than one time by sending BQRP variant trigger frame? Consider the case that the availabe channels at the triggered STAs are few or the primary 20MHz is not available at all the triggered STAs, is it allowed that AP sending trigger to other STAs to know channel availability of them? Please clarify. Rejected- It is really an implementation choice as described by the commentor. The current spec text already allows such usage. TGax editor makes no changes on CID 9468. 9526 Yasuhiko Inoue There is no field named "DL OFDMA With MIMO Support" in HE Capabilities. Assign one reserved bit in the HE PHY Capabilities Information field of HE Capabilities element to indicate this capability. Revised- Agree in principle. Per proposed resolution of CID 4804, this sentence will be removed. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 9526. 9587 Yongho Kim If a non-AP STA has no capabilities on some channels, what value need to be set? And, If a non-AP STA's channel bandwidth is regulated by OMI procedure, what value need to be set? Define it. Rejected- How to obtain the channel availability information is defined already in section 28.3.17.6.5 and referred in this section. If the STA is not capable of determining the interference level with 90% probability, then the bit will be set to 0. TGax editor makes no changes on CID 9587. 56
9891 Young Hoon Kwon DL OFDMA With MIMO Support field is not defined in HE Capabilities element. Need definition for it. As in the comment. Revised- Agree in principle. The right HE Capabilities bit should be refered. Per proposed resolution of CID 4804, this sentence will be removed. The corresponding sentence in 56 to 59 is modified correspondingly. TGax editor changes as shown in 11-17/1286r1 that are marked with CID 9891. 9892 Young Hoon Kwon It is not clear how to obtain the channel availability information for each 20MHz, especially for unsolicited BQR case. For example, how to measure and when to measure the channel availability for each 20MHz is not clear. It needs further clarification. As in the comment. Rejected- Please refer to section 9.2.4.6.4.7 and 28.3.17.6.5 for further details. All these information has been defined. TGax editor makes no changes on CID 9892. 9893 Young Hoon Kwon When a STA receives a BQRP variant Trigger frame which does not schedule an RU for the STA, it is not clear if the STA shall participate random access or not. Need further clarification. As in the comment. Revised- A STA only to send BQR when it has indicates its capabilities in HE Capabilies. TGax editor makes changes as shown in 11-17/1286r1 that are marked with CID 9893. Discussion: Clarifying the language as suggested.