CID Commenter Clause Page/Line Comment Proposed Change Resolution Chunyu Hu 28.3.10.8.6 432.32 There is no definition of load balancing before usage. Load balancing is a general term in network, but is complete new in this new context of HE SIG-B. It's not clear what it means in this section. Please define it before using it in the text of behavior description. as in the comment Revised Editor please make changes shown in document under comment 11496 11530 Dorothy Stanley 28.3.10.8.5 426.48 something is weird with the formatting. Its seems like "Use the same value in both HE-SIG-B content channels." should be part of the 80 MHz description, but its looks like its in the paragraph with the 160 MHz section. Please clarify. as in comment Revised. Editor: remove the gap above that sentence and add a gap below it. Also change that sentence as follows: Use The same value is applied to in both content channels 11636 Dorothy Stanley 28.3.10.7.2 405.25 The title of Table 28-18 is field of an HE SU PPDU and HE ER SU PPDU", so why would B0 of HE-SIG-A1 ever be "set to 0 for HE TB PPDU"? You probably just want to say "set to 1 for HE SU PPDU and HE ER SU PPDU", and not say anything about HE TB PPDU. as in comment Revised. Editor please make changes shown in document under comment 11636
13371 ron 28.3.10.8.5 428.00 To cover certain legal allocation in 80, 160 or 80+80 OFDMA cases when for a particular content channel, one 996-tone RU Allocation subfield has non-zero number of users while the other 996-tone RU allocation subfiled has no users, change to RU with no User fields indicated by this RU Allocation subfield". Revise as suggested Accepted modified See resolution for comment 13407 Rui Cao 28.3.10.8.3 424.04 When RU=996 is allocated, the setting of the RU Allocation Bits is not clearly defined. The totally number of users in one 996RU will be split in two content channels with load balancing. However, each 996RU will have 16 RU Allocation bits, and 8-bit RU Allocation 11010yyy can already clearly specify the number of users signaled in the corresponding content channel. How to set the second 8 bits is not specified in current text. Propose to add the following to the paragraph, "If RU equals 996, the first 8 RU Allocation bits will use entry 11010yyy as in Table with yyy indicating the number of users signaled in the corresponding content channel, while the second 8 RU Allocation bits will be set to 01110011". In addition, change the description of entry "01110011" in Table 28-24 to "996-tone RU with zero User indicated in this RU Allocation subfield of the HE-SIG-B content channel". Accepted modified Editor please add this paragraph in 424.07: If RU size equals 996, the first 8-bit RU Allocation subfield will use entry 11010y2y1y0 as in Table 28-24 with y2y1y0 indicating the number of User fields signaled in the corresponding content channel, while the second 8-bit RU Allocation subfield will be set to 01110011". In addition, change the description of entry "01110011" in Table 28-24 to "996-tone RU with zero User fields indicated in this RU Allocation subfield of the content channel".
11531 Dorothy Stanley 28.3.10.8.5 428.01 What does "Number of entries" mean for cases that are "Reserved" in Table 28-24? as in comment Rejected: It simply means the number of reserved entries 11532 Dorothy Stanley 28.3.10.8.5 428.41 Table 28-24, Regarding "10y2y1y0z2z1z0", how do you multiplex 64 users together in three RUs? as in comment Rejected: The number 64 indicates the combinatorial options of multiplexing up to 8 users on each 106RU using DL MU-MIMO. It is not indicating 64 users are being multiplexed 13239 Robert Stacey 9.4.2.237.3 140.62 The only difference between class A and class B devices is power control accuracy. The terminology is thus misleading not aligned with other capability naming. Change the field name to "Tx Power/RSSI Accuracy" (or even "Power Control Accuracy") with enumerated values High and Low. Change the middle column heading in Table 28-43 to "Tx Power/RSSI Accuracy subfield" with sub-columns "High" and "Low". Updated the places where Class A and Class B are used appropriately. Accepted Editor please make your proposed changes 13305 Robert Stacey 28.3.10.7.2 405.40 The description is not accurate -- see 27.11.2. Also, there is nothing in the PHY that links it to UPLINK_FLAG. You don't need any shall statements here - they are in the MAC section. Change the desciption so that it references TX/RXVECTOR parameter UPLINK_FLAG. Accepted Editor – please replace the description with “Indicates whether the PPDU is sent UL or DL as described by the TX/RXVECTOR parameter UPLINK_FLAG”