If there is no non-HT duplicate frame exchange in a TXOP, the TXOP holder shall set the TXVECTOR parameter CH_BANDWIDTH of a non-initial PPDU to be the same or narrower than the TXVECTOR parameter CH_BANDWIDTH of the preceding PPDU that it has transmitted in the same TXOP. 9600 "If there is no non-HT As per comment. Revised- duplicate frame exchange Agree in principle. in a TXOP, the TXOP When an HE AP holder shall set the transmits multiple HE DL TXVECTOR parameter MU PPDUs with CH_BANDWIDTH of a preamble puncture in a non-initial PPDU to be the same TXOP, additional same or narrower than constraint for the RU the TXVECTOR allocation is needed. parameter CH_BANDWIDTH of the TGax editor makes preceding PPDU that it changes as shown in the has transmitted in the as specified in same TXOP." When an HE AP transmits an HE DL MU PPDU with preamble puncture, the TXVECTOR parameter CH_BANDWIDTH selection rule should be seperately defined. Because the above current rule does not cover it. 5969 Please clarify can an HE Please add clarification are Revised- MU PPDU contain a Trigger frames or UL MU Agree in principle. response scheduling Trigger frame or UL MU Add the missing case of fields to solicit UL Response scheduling HE multiple HE trigger-based BAs allowed in HE MU DL Variant HT Control field to PPDU transmissions in a PPDUs when the TXOPLimit allocate resources for UL TXOP with the TXOP is 0. MU acknowledgements limit equal to 0. transmission. In consequence, multiple Trigger frames (or UL MU response scheduling A-Control fields) to solicit multiple UL BAs are allowed in HE DL MU PPDU when the TXOPLimit is 0.
If there is no non-HT duplicate frame exchange in a TXOP, the TXOP holder shall set the TXVECTOR parameter CH_BANDWIDTH of a non-initial PPDU to be the same or narrower than the TXVECTOR parameter CH_BANDWIDTH of the preceding PPDU that it has transmitted in the same TXOP. 9600 "If there is no non-HT duplicate frame exchange in a TXOP, the TXOP holder shall set the TXVECTOR parameter CH_BANDWIDTH of a non-initial PPDU to be the same or narrower than the TXVECTOR parameter CH_BANDWIDTH of the preceding PPDU that it has transmitted in the same TXOP." When an HE AP transmits an HE DL MU PPDU with preamble puncture, the TXVECTOR parameter CH_BANDWIDTH selection rule should be seperately defined. Because the above current rule does not cover it. As per comment. Revised- Agree in principle. When an HE AP transmits multiple HE DL MU PPDUs with preamble puncture in a same TXOP, additional constraint for the RU allocation is needed. TGax editor makes changes as shown in the as specified in 5969 Please clarify can an HE MU PPDU contain a Trigger frame or UL MU Response scheduling HE Variant HT Control field to allocate resources for UL MU acknowledgements transmission. Please add clarification are Trigger frames or UL MU response scheduling fields to solicit UL BAs allowed in HE MU DL PPDUs when the TXOPLimit is 0. Revised- Agree in principle. Add the missing case of multiple HE trigger-based PPDU transmissions in a TXOP with the TXOP limit equal to 0. In consequence, multiple Trigger frames (or UL MU response scheduling A-Control fields) to solicit multiple UL BAs are allowed in HE DL MU PPDU when the TXOPLimit is 0.
11-17-0210-02-00ax-lb225-cr-10-22-2-7-and-10-22-2-8.docx