wants to set AC Preference level to 0 then it could as well set Preferred AC to 3 and allow the STA to send any type of traffic. This frees up one bit. the AP does not have a recommendation for preferred AC then Preferred AC level is set to 3. [TGax editor to make changes as shown in doc xxx under all heading that contain 3018, 8190] 8190 Osama 49.06 AC Preference level seems to be useless. Wouldn't Preferred AC be sufficient? delete AC Preference level Accepted Modified [TGax editor to make changes as shown in doc xxx under all heading that contain 3018, 8190] Discussion: None. TGax Editor: Make the following changes in section 9.3.1.23.1, D1.1 p49.l27 (#CID 3018, 8190): If the Trigger frame is a Basic Trigger variant, the Trigger Dependent Common Info field is not present and the Trigger Dependent User Info field is defined in Figure 9-52g (Trigger Dependent User Info field for the Basic Trigger variant). B0 B1 B2 B4 B5 B6 B7 MPDU MU Spacing Factor TID Aggregation Limit Preferred AC Bits: 2 3 1 2 Dependent User Info field for the Basic Trigger variant TGax Editor: Make the following changes in section 9.3.1.23.1, p50.l6 (#CID 3018, 8190): . The Preferred AC subfield indicates the AC that is recommended for aggregation of MPDUs of ACs belonging to the same AC as indicated or higher priority AC(s) within a multi-TID A-MPDU sent as a response to the Trigger frame (see 9.3.1.23 (Trigger frame format)). The encoding of the Preferred AC subfield is shown in Table 9-25i (Preferred AC subfield encoding). Preferred AC subfield encoding Value Description 0 AC_VO 1 AC_VI 2 AC_BE 3 AC_BK
performance. 11ax is designed to work under high dense environment with large number of STAs which have diverse application demands. When BSRP variant Trigger frame triggers random access BSRs, the BSR from the STA with high priority AC shall not contend with low priority AC BSR. Need to reuse the AC-aware design in Basic Trigger variant. Trigger variant. B0-B4 bits are discarded and reserved. recommended to transmit from in the Trigger-based PPDU; from the BSR delivery perspective it is of outmost importance for the AP to have knowledge of as many queues as possible from the STA. And from the STA perspective the STA can decide which of its queues it deems whith higher priority. The current design enabled both, 9645 Yongho Seok 46.27 "B12 is set to 0 for a 20 MHz, 40 MHz and 80 MHz PPDU. For the 2x996-tone RU case, B12 is set to 1." An interpretation of B12 shown in above is different with the previous paragraph. Probably, it may be for a case when the triggered PPDU is a non-OFDMA PPDU. But, even though it is a non-OFDMA case, current B12 definition is useless. Because has a complete information for indicating a 20/40/80/160/80+80MHz non-OFDMA PPDU. Please explain how current B12 encoding is utilized by a non-AP STA. Otherwise, change it as the following: "When a non-OFDMA PPDU is triggered, B12 is reserved and set to 0." As per comment. Rejected. There is no inconsistency in the definition of Bit 12. Bit 12 indicates if Bit19-Bit 13 refer to the primary 80 MHz, 0 for primary or for the non-primary 80, 1 for non-primary. For 2x996 when both Primary 80 and non primary-80 is used then Bit 12 is set to 1. CID Commenter P.L Comment Proposed Change Resolution 6082 Jian Yu For OFDMA PPDUs, the number of HE-LTFs should be greater or equal As in comment Rejected The spec text already says “For OFDMA PPDUs, the number of