IEEE P802.11 Wireless LANs Resolution for CID 1589, 1590, 2668, and 2669 on Multi-TID Aggregation in Sub-clause 25.10.4 Date: 2016-06-18 Author(s): Name Affiliation Address Phone email Chittabrata Ghosh Intel Corporation 3600 Juliette Lane, Santa Clara, CA-94054 +1-415-244-8904 chittabrata.ghosh@intel.com Guoqing Li Apple guoqing_li@apple.com Alfred Asterjadhi Qualcomm aasterja@qti.qualcomm.com CID Clause Page No. Line No. Comment Proposed Change Resolution 2669 25.10.3 65 8 In case a STA supports multiple TIDs within an A-MPDU, it is not clear what is the rule for aggregating multiple TIDs in an A-MPDU. For example, it is not clear if a STA can aggregate any MPDUs in any TID, or if there's any specific rule in aggregating MPDUs from different TID to better support QoS. Clarify rules for aggregating multiple TIDs in an A-MPDU as mentioned in the comment. Revised Agreed in principle; please refer to the following draft text in document for the proposed resolution The recipient indicates the maximum number of TIDs of the MPDUs that the originator can aggregate in a multi-TID A-MPDU in MU PPDU. [MAC Motion 68, March 2016, see 16/362r1] Within a single A-MPDU containing MPDUs with different value of TIDs, the MPDUs with the same TID value are not required to be in contiguous A-MPDU subframes. [MAC Motion 69, 2016, see 16/362r1] The maximum number of TIDs of QoS data frames that an originator can aggregate in a multi-TID is indicated in the HE Capabilities element sent by the recipient A nonzero value also indicates that the recipient supports reception of multi-TID A-MPDUs Note: A multi-TID A-MPDU allows the aggregation of an Action Ack frame as well
Fragmentation Support field value Meaning 0 No support for HE fragmentation(#1336) 1 Support for fragments that are contained within a VHT single MPDU, no support for fragments within an A-MPDU 2 Support for up to one fragment per MSDU within a single A-MPDU 3 Support for multiple fragments per MSDU within an A-MPDU The format of the PPE Thresholds field is defined in Figure 9-ax3 (PPE Thresholds field format)(#2834). B0 B1 B2 B3 NSS M1 RU Count PPE Threshold Info PPE Pad Bits: 3 2 variable variable PPE Thresholds field format The NSS M1 subfield contains an unsigned integer that is equal to the number of NSS values minus one for which PPE threshold information is included in the PPE Thresholds field.(#1334) The RU Count subfield contains an unsigned integer that is equal to the number of RU allocation values for which HE PPE threshold information is included in the PPE Thresholds field. The value of zero for this field is reserved. The value of three for this field is reserved. The PPE Threshold Info field is (NSS M1 + 1)  RU Count  6 bits(#1337) in length. The format of the PPE Threshold Info field is defined in Figure 9-ax4 (PPE Thresholds Info field format)(#2835).
PPET16 for NSS1 for RU1 for NSS1 for RU1 ... PPET16 for NSS1 for RUm PPET8 for NSS1 for RUm ... PPET16 for NSSn for RUm PPET8 for NSSn for RUm Bits: 3 3 3 3 3 3 PPE Thresholds Info field format Each PPET8 for NSSn for RUm subfield and PPET16 for NSSn for RUm subfield contains a constellation index as defined in Table 9-ax14 (Constellation index).(#1349)(#619). index Constellation Corresponding Transmission Constellation 0 BPSK 1 QPSK 2 16-QAM 3 64-QAM 4 256-QAM 5 1024-QAM 6 Reserved 7 None All the PPET8 for NSSn for RUm subfield and PPET16 for NSSn for RUm subfield values are combined to encode the minimum duration of the post-FEC padding and packet extension for HE PPDUs that are transmitted to the STA sending this field, for each value of NSS and RU specified by the field and implicitly, for values of NSS and RU not explicitly indicated in the field. The encoding is described in Table 9-ax15 (PPET8 and PPET16 encoding). and PPET16 encoding