zilongwang/ReadingBank huggingface dataset:
IEEE P802.11 Wireless LANs Beamforming Training for CB & CA Date: 2017-05-09 Author(s): Name Affiliation Address Phone email SungJin Park LG Electronics Yangjae-daero 11gil, Seocho-gu, Seoul, 137-893, Korea allean.park@lge.com JinMin Kim LG Electronics jinmin1230.kim@lge.com Saehee Bang LG Electronics saehee.bang@lge.com SunWoong Yun LG Electronics sunwoong.yun@lge.com Jinsoo Choi LG Electronics js.choi@lge.com Sanggook Kim LG Electronics San /California/US sanggook.kim@lge.com
case where the CTS response is non-HT, this must mean the HE-Trigger_based PPDU requirements on CFO/SFO/Power/Timing do not apply here. Is this good enough for demodulation by sender of MU-RTS? TGax editor makes changes as shown in the as specified in 986 45 "the previous not clear. Suggest to change to "the previous MU-RTS frame" Revised. Agree in principal. TGax editor makes changes as shown in the as specified in 734 45 5 What is a previous MU-RTS Is it a frame that the STA has previously transmitted? How long ago? Or is it a frame that the STA has previously received? Or something else? Please clarify what is meant with previous Revised. in principal. TGax editor makes changes as shown in the as specified in 10.3.2.8a MU RTS/CTS procedure 10.3.2.8a.3 CTS Repsonse to MU-RTS TGax Editor: change the 3rd paragraph as following(863, 219, 411, 2380, 2609): The Scrambler Initialization in the SERVICE field of the CTS sent in response to an MU-RTS frame shall be copied from the Scrambler Initialization in the SERVICE field of the MU-RTS frame. TGax Editor: Add the following paragraph at the end of 10.3.2.8a.3(2115): 10.7.6.5.2 Selection of a rate or MCS TGax Editor: remove the following paragraph from subclause 10.7.6.5.2(863, 219, 411, 2380, 2609): 9.3.1.23.2 MU-RTS variant TGax Editor: add the following paragraph from subclause 10.7.6.5.2(863, 219, 411, 2380, 2609): 17.2.2 TXVECTOR parameters 17.2.2.1 General
843 Abstract ii 3 E Grammer mistake in "at around 60 GHz" and "at around 45 GHz" Change to "around 60 GHz" and "around 45 GHz" Discussion: Do as the suggested remedy. Proposed resolution: Accept Change"at around 60 GHz" and "at around 45 GHz" to " around 60 GHz" and "around 45 GHz". CID Clause Page Line Type Comment Proposed Change 844 24.3.6.1 170 65 E Typo in letter "F" Delete the letter "F" Discussion: Do as the suggested remedy. Proposed resolution: Accept 24.3.6.1 General Change the first paragraph as follows: …The format of the preamble consists of a Short Training field followed by a Channel Estimation field. Figure 24-2 (CDMG SC mode preamble) illustrates the SC packet preamble. CID Clause Page Line Type Comment Proposed Change 845 9.4.2.132 42 50 E typo in "Figure field format" Change to "Figure Control format". So does P43L9. Discussion: .
AOB None. Adjournment Meeting adjourned at 20:35 (ET). List of Attendees – following people were on the call. Name Affiliation 1 Aboul-Magd Huawei Technologies 2 Woojin Ahn WILUS Institute 3 Alfred Asterjadhi Qualcomm 4 Liwen Chu Marvell 5 Yasuhiko NTT 6 Suhwook Kim LG Electronics 7 Kaiying Lv ZTE 8 Jing Ma NICT 9 Abhishek Patil Qualcomm 10 Albert Petrick InterDigital 11 Shoko Shinohara NTT 12 Huizhao Wang Qualntenna 13 James Wang MediaTek 14 15
IEEE P802.11 Wireless LANs Minutes – July 2017 Berlin Date: 2017-07-14 Author(s): Name Affiliation Address Phone email Jon Rosdahl Qualcomm Technologies, Inc. 10871 N 5750 W Highland, UT 84003 801-492-4023 Monday PM1: TGmd called to order at 1:32pm CEST by the chair, Dorothy STANLEY (HPE) Review Patent Slides: Call for Potentially Essential Patents – No response Participation Slide was reviewed. Review Agenda: Monday PM1 Chair’s Welcome, Policy & patent reminder Approve agenda, previous minutes Status, Review of Objectives Draft schedule 11-17-920r2 – Editor Report – Emily QI 11-17-1089 - Mike MONTEMURRO Tuesday PM1 11-17-989 – Graham SMITH – Obsolete comments 11-17-1078 – Ganesh VENKATESAN () Wednesday PM1 11-17-939, 11-17-940 Stephen MCCANN 11-17-970, 971 – James YEE 11-17-1030; 11-17-906 – Jouni MALINEN Thursday PM1 11-17-959 – Adrian STEPHENS 11-17-987, 988 – Graham 11-17-928 – Jon ROSDAHL Thursday PM2 11-17-956; 11-17-1056; Emily QI 11-17-906 – Jouni MALINEN 11-17-xxx Marc EMMELMAN Approve initial schedule AOB Plans for July-Sept Adjourn Discussion on agenda – move to Thursday, Concern on getting a discussion when all interested parties are available. Discussion on getting all the documents listed Motion B1: Motion to approve agenda passed without Objection. Motion B2: Motion to approve TGmd Minutes
Motion #1: CID 331 Resolve CID 331 as “Accepted”. Note this incorporates the changes in 11-17/0871r0 <> as agreed on the 2017-05-30 teleconference Moved: Jouni MALINEN 2nd: Mike MONTEMURRO Results: Motion #1: 18-0-0 Motion #1 passes Motion #2: July session and Telecon CIDs Approve the comment resolutions on the “PHY Motion A” tab in doc <> and the “Comments for approving” tab in doc <> except CID 123 “Motion MAC-A” tab in 11-17/0927r4 <> Moved: Stephen MCCANN 2nd: Emily QI Results Motion #2: 17-0-0 Motion #2 Passes Motion #3 LC TIG Comments Resolve CIDs 332, 333, 334, 335 as “Rejected” with a resolution of Comment is for the LC TIG Comment review not the REVmd Comment Collection. Moved: Jon ROSDAHL 2nd: Mike MONTEMURRO Results: Unanimous – Motion #3 Passes Motion #4: – 11ai editorial CIDs Resolve CIDs 8, 9, 10, 11, 12, 16, 347, and 348, as “Revised” with a resolution of “Incorporate the text changes in 11-17/1076r2 <> . These changes resolve the comment in the direction suggested by the commenter.” Moved: Emily QI 2nd: Stephen MCCAAN Results Motion #4: Unanimous – Motion #4 Passes Review Schedule Based on the discussion from Monday, Updated Timeline January 2018 – Initial WGLB September 2018 –D2.0 WGLB Recirculation LB February 2019 – Form SB Pool 2019 – MEC/MDR done April 2019 – Initial SB October 2019 – Recirculation SB July 2020 – Final WG/EC approval September 2020 – RevCom/SASB approval Will require off-month ad-hoc meetings Motion – Editor Motion Editor_2 Comments A Motion will be prepared, but need to do later in the day and then we can consider a motion on Jouni’s submission as well. Return to Submission 11-17-906r3 – Jouni MALINEN Continue the review where we left off about page 7. Figure 9-328 should have been 9-320. After review, some minor changes were captured and an R4 was posted for motion.
IEEE P802.11 Wireless LANs Minutes REVmd – July 2017 Berlin Date: 2017-07-14 Author(s): Name Affiliation Address Phone email Jon Rosdahl Qualcomm Technologies, Inc. 10871 N 5750 W Highland, UT 84003 801-492-4023 jrosdahl@ieee.org Monday PM1: TGmd called to order at 1:32pm CEST by the chair, Dorothy STANLEY (HPE) Review Patent Slides: Call for Potentially Essential Patents – No response Participation was reviewed. Review Agenda: Monday PM1 Welcome, Policy & patent reminder Approve agenda, previous minutes Status, Review of Objectives Draft schedule 11-17-920r2 – Editor Report – Emily QI 11-17-1089 - Mike MONTEMURRO Tuesday PM1 11-17-989 – Graham SMITH – Obsolete comments 11-17-1078 – Ganesh VENKATESAN () Wednesday PM1 11-17-939, 11-17-940 Stephen MCCANN 11-17-970, 971 – YEE 11-17-1030; 11-17-906 – Jouni MALINEN Thursday PM1 11-17-959 – Adrian STEPHENS 11-17-987, 988 – Graham 11-17-928 – Jon ROSDAHL Thursday PM2 11-17-956; 11-17-1056; QI 11-17-906 – Jouni MALINEN 11-17-xxx Marc EMMELMAN Approve initial schedule AOB Plans for July-Sept Adjourn Discussion on agenda – move Emily to Thursday, Concern on getting a discussion when all interested parties are available. Discussion on getting all the documents listed Motion B1: Motion to approve agenda passed without Objection. Motion B2: Motion to approve prior TGmd Minutes
IEEE P802.11 Wireless LANs P802.11ax PAR Modification Date: 2017-07-12 Author(s): Name Affiliation Address Phone email Rich Kennedy HP Enterprise 7305 Napier Trail Austin, TX 78729 +1737-202-7014 rich.kennedy@hpe.com P802.11ax Submitter Email: osama53@rogers.com Type of Project: Amendment to IEEE Standard 802.11-2012 PAR Request Date: 24-Jan-2014 PAR Approval Date: 27-Mar-2014 PAR Expiration Date: 31-Dec-2018 Status: PAR for an Amendment to an existing IEEE Standard Root Project: 802.11-2012 1.1 Project Number: P802.11ax 1.2 Type of Document: Standard 1.3 Life Full Use 2.1 Title: Standard for Information technology--Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment Enhancements for High Efficiency WLAN 3.1 Working Group: Wireless LAN Working Group (C/LM/WG802.11) Contact Information for Working Group Chair Name: Adrian Stephens Email Address: adrian.p.stephens@intel.com +44 1954 204610 Contact Information for Working Vice-Chair Name: Jon Rosdahl Email Address: jrosdahl@ieee.org Phone: 801-492-4023 3.2 Sponsoring Society and Committee: IEEE Computer Society/LAN/MAN Standards Committee (C/LM) Contact Information for Sponsor Name: Paul Nikolich Email Address: p.nikolich@ieee.org Phone: 857.205.0050 Contact Information for Standards Representative Name: James Gilb
46 69 12 "In the SU-MIMO subphase, based on the SNRs of the transmit sectors collected from the responder in the SISO Feedback subphase of the SISO phase, the initiator may select a subset of candidate transmit sectors per DMG antenna to reduce the initiator SMT training time. " This whole paragraph describes non normative behavior that is irrelevant to the fileds Repalce the text with normative behavior on what is sent by the inititor and what is replied by the respodner. It is not necessary for the initiator to inidcate the sectors it will use in advance, only their numbe, or the MID extension may be used. Revised- TGay editor to make the changes shown in under all headings that include CID 46. 47 69 28 "the candidate transmit sectors" The list does not have to be know in advance, possilby it length may be required, the sector ID is transmitted inside each packet. Remove the list of sectros, it is too long. Accepted- TGay editor to make the changes shown in under all headings that include CID 47. 185 70 30 NI undefined, used further as N_I (N_I) instead of NI Revised- TGay editor to make the changes shown in under all headings that include CID 185. 51 72 32 "the order if which transmit sectors are trained" - why is this necessary, besides being long, this has no effect on reponders behavior Remove this from the list Accepted- TGay editor to make the changes shown in under all headings that include CID 51. 52 72 34 "the number of receive training fields based on the feedback from responders received at the SISO phase" - its receive training and the L-RX field in the responses shall be mentioned Replace with "the number of receive TRN-Units based on the L-RX field in feedback from responders received at the SISO pahse" Revised- TGay editor to make the changes in under all headings that include CID 52. 395 72 34 It is not clear how does initiator determine the number of rx training fields needed at responder, based on the change the sentence to 'To reduce the training time, the initiator may select a subset of TX sectors Revised- TGay editor to make the changes shown in under all MIMO
IEEE P802.11 Wireless LANs HE-LTF –26.3.10.3 Date: 2016-04-17 Author(s): Name Affiliation Address Phone email Ming Gan Huawei F1-17, Huawei Base, Bantian, Shenzhen ming.gan@huawei.com Xiaogang Chen; Intel Corporation 2111 NE 25th Ave, Hillsboro, OR, 97124 xiaogang.c.chen@intel.com Abstract This submission proposes resolutions for multiple comments related to TGax D0.1 with the following CIDs (18 CIDs): 1865 323 481 517 537 920 319 1059 2559 2551 2552 2553 2554 2555 2556 2557 2558 923 Revisions: Rev 0: Initial version of the document. Interpretation of a Motion to Adopt A motion to approve this submission that the editing instructions and any changed or added material are actioned in the TGax Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGax Editor: Editing instructions preceded by “TGax Editor” are instructions to the TGax editor to modify existing material in the TGax draft. As a result of adopting the changes, the TGax editor will execute the instructions rather than copy them to the TGax Draft. CID Commenter P.L Comment Proposed Change Resolution 319 Bin Add a new optional combiniation 2x LTF+ 3.2usCP to support outdoor channel. Since 2x LTF is the only mode suppoted in sounding NDP, this new 2x LTF+3.2up CP is useful for outdoor channel sounding as in comment Rejected The reason is that 2x LTF+ already can support ourdoor channel Youhan Make (1xHE-LTF, TGI2,Data) and (1xHE-LTF, TGI4,Data) mandatory for non-OFDMA, MU-MIMO HE_TRIG PPDU. Make (1xHE-LTF, TGI2,Data) and TGI4,Data) mandatory for MU-MIMO HE_TRIG PPDU. Rejected The reason is that the commenter failed to provide sufficient reason 2
FORMAT Determines the format of the PPDU. Enumerated type: NON_HT indicates Clause 18 (Orthogonal frequency division multiplexing (OFDM) PHY specification) or non-HT duplicate PPDU format. In this case, the modulation is determined by the NON_HT_MODULATION parameter. HT_MF indicates HT-mixed format. HT_GF indicates HT-greenfield format. VHT indicates VHT format. HE_SU indicates HE SU PPDU format. HE_MU indicates HE MU PPDU format HE_EXT_SU indicates HE extended range SU PPDU format HE_TRIG indicates HE trigger-based PPDU format Y Y PE_DURATION FORMAT is HE_SU or HE_MU or or HE_TRIG. Determines the duration of PE field in an HE PPDU. Possible values are 0 µs, 4 µs, 8 µs, 12 µs and 16 µs. BEAM_CHANGE FORMAT is HE_SU NOTE—BEAM_CHANGE shall be set to 1 if NSS > 2 or the PPDU is the first PPDU in a TXOP. Otherwise Set to 1 (To be added) FORMAT is HE_SU or HE_MU or Set to a value of the AP’s choosing within the range 0 to TBD (see 25.11 (STA ID, Uplink Flag and BSS Color in HE PPDUs)). Y Y
922 9.6.30.6 78 65 T "Figure 9-740c (Channel Splitting Request frame Action field format)." Wrong filed name. It should be "Figure 9-740c (CDMG Allocation Request frame Action field format)" Change to "Figure (CDMG Allocation Request frame Action field format)" Proposed resolution: Accepted.
I would lean towards b). Proposed resolution: REJECT If no frame is available, then the normative behavior is the “Do nothing” case at 1487.24. CID Commenter Clause Line Comment Proposed 364 Woojin Ahn 10.22.2.2 1486.8 When an AP updates EDCA parameter set, associated STAs only update MIB attributes and their current CW[AC] will remain the same. Therefore, when a STA enters the "otherwise" condition, it might have CW[AC] less than CWmin[AC] or greater than CWmax[AC] if its EDCA parameter set had been updated by the associated AP. It is necessary to keep STAs' CW values within the intended range [CWmin, CWmax]. - Otherwise, - If CW[AC] is less than CWmax[AC], CW[AC] shall be set to the value max(CWmin[AC], (CW[AC] + ├ù 2 - 1). - If CW[AC] is equal to or greater than CWmax[AC], CW[AC] shall be set to CWmax[AC]. Discussion: Text in question is 1486.8 — Otherwise, — If CW[AC] is less than CWmax[AC], CW[AC] shall be set to the value (CW[AC] + 1) × 2 – 1. — If CW[AC] is equal to CWmax[AC], CW[AC] shall be left unchanged. Proposal is to change the second bullet to account for CW[AC] > CWmax[AC] Proposed resolution: REVISED 1486.8 to read — Otherwise, — If CW[AC] is less than CW[AC] shall be set to the value (CW[AC] + 1) × 2 – 1. — Else CW[AC] shall be set to CWmax[AC].
1549.60 delete “and/or be separated by RIFS” 1550.37 delete “a) The RIFS Mode field of the HT Operation element equal to 1” Delete clause 10.26.3.3 “RIFS protection”. (Note this is for HT) 1551.12 delete “and RIFS” 1551.28 delete “and RIFS” 1551.31 delete “or RIFS” 1551.33 delete “and RIFS” 1562.50 delete “and 10.26.3.3 (RIFS protection)” 1565.11 delete “and 10.26.3.3 (RIFS protection)” 1565.34 delete “unless the use of RIFS is permitted, as defined in 10.26.3.3 (RIFS protection)” 1565.37 delete RIFS” and “The use of RIFS is limited as defined in 10.3.2.3.2 (RIFS) and 10.26.3.3 (RIFS protection).” Figure 10-44 1567.143 delete “RIFS or” 2026.41 delete “A VHT AP shall set the RIFS Mode field in the HT Operation element to 0.” 2581.8 delete 19.3.19.7 At 2588.25 DON’T KNOW maybe delete from line 22 or just this line “This sequence occurs when signal-extended PPDUs are transmitted while separated by a RIFS. 2970.28 delete HTM6.1 and HTM6.2 2987.19 delete HTP2.13 3263.15 Delete dot11RMNeighborReportHTInfoRIFSMode
10048 yujin noh 314.32 In order to reduce misunderstanding on the cencept of PHY padding, "applied on" could be replaced with proper text such as "appended right after or appended to" . As in the comment. Revised. Change to as in the resolution of CID10048 in doc Discussions: “a post-FEC PHY padding” is refered to post-FEC PHY padding process in the context. It does not refer to PHY padding bits. So it is correct to use “applied on” instead of “appended to” as commentor suggest. To eliminate the confusion of the text, “padding” should be replaced by “padding process” in the following paragraph. ax editor: please make the changes in D1.3 Clause 28.3.11.2 On P402L29 (CID A two-step padding process is applied on all HE PPDUs. A pre-FEC padding both MAC and PHY padding is applied before conducting coding, and a post-FEC PHY padding is applied on the FEC encoded bits. 8994 Sigurd Schelstraete 315.31 Delete the word "excess" from "excess bits in the last OFDM symbol". These are simply the bits in the last OFDM symbol. See comment Revised. Change to as in the resolution of CID8994 in doc ax editor: please make the following changes in D1.3 Clause 28.3.11.2: On P403L33 (CID #8994): In an HE SU PPDU transmission, the transmitter first computes the number of bits in the last OFDM symbol(s) based on Equation (28-54). 8995 Sigurd Schelstraete 316.52 "the MAC delivers a PSDU that fills the available octets ...". Add reference to A-MPDU padding (27.10.2 & 27.10.3). See comment Revised. Change to as in the resolution of CID8995 in doc ax editor: please make the following changes in D1.3 Clause 28.3.11.2:
9082 Sriram 28.3.9 263.51 The statement "The total power of the time domain HE modulated signals summed over all transmit chains should not exceed the total power of the time domain pre-HE modulated field signals summed over all transmit chains." may not be true for extended range PPDUs with boosted LTFs etc. If this line does not hold for all cases, please give proper qualifications (or delete it if the spec specifies these powers clearly in other places and the line is redundant) Rejected. It is resolved by the resolution of CID4990 in doc.: IEEE 9173 SUNGEUN LEE 270.14 The GI parameter in Eq (28-10) based on P802.11ax D1.0 is wrong. It should be TGI,L-LTF Change to in L-LTF equation for is 0, i.e., Eq. (28-10) based on P802.11ax D1.0 Rejected. It is resolved by the resolution of CID4907 in doc 9176 SUNGEUN LEE 272.05 The summation range for iBW should be from 0 to N_20MHz-1 Change summation upper bound of iBW from N20MHz to N20MHz-1 for equation, ie.g., Eq (28-13) Rejected. It is resolved by the resolution of CID10403 in doc yujin noh 314.01 clarify the setence below how to recommended. "When a 1x, 2x or 4x is transmitted, it is recommended that the spatial mapping matrix applied to HE-STF and beyond is chosen such that it preserves the smoothness of the physical channel, achieved by limiting the variation of each element's real and imaginary values in the spatial mapping matrix As in the comment. Rejected. It is resolved by the resolution of CID8990 in doc
IEEE P802.11 Wireless LANs 11ax Comment Resolutions on Data Field Date: 2017-07-07 Author(s): Name Affiliation Address Yan Zhang Marvell , Clara, CA 95054 408-222-0975 Hongyuan Zhang Marvell Rui Cao Marvell Abstract: This document contains proposed resolutions for comments in Clauses 28.3.9, 28.3.10.4, 28.3.10.5, 28.3.10.10 and 28.3.11 from 11ax D1.3 with the CIDs below. Clause 28.3.9 5255,9169,9170,9171,9082 Clause 28.3.10.4 9173 Clause 28.3.10.5 9176 Clause 28.3.10.10 10163 Clause 28.3.11.2 Clause 28.3.11.4 8996 Clause 28.3.11.10 9013 7433 Lei Huang 28.3.11.2 314.20 Strictly speaking, the PSDU contains MAC pad bits. Change "When BCC encoding is used, the Data field shall Revised. Change to as in the resolution of FEC
domain HE modulated field signals summed over all transmit chains should not exceed the total power of the time domain pre-HE modulated field signals summed over all transmit chains." may not be true for extended range PPDUs with boosted LTFs etc. qualifications (or delete it if the spec specifies these powers clearly in other places and the line is redundant) IEEE 9173 SUNGEUN LEE 270.14 The GI parameter in Eq (28-10) based on P802.11ax D1.0 is wrong. It should be TGI,L-LTF Change to in L-LTF equation for is 0, i.e., Eq. (28-10) based on P802.11ax D1.0 It is resolved by the resolution of CID4907 in doc 9176 SUNGEUN LEE 272.05 The summation for iBW should be from 0 to N_20MHz-1 Change summation bound of iBW from N20MHz to N20MHz-1 for equation, ie.g., Eq (28-13) It is resolved by the resolution of CID10403 in doc noh 314.01 clarify the setence below how to recommended. "When a 1x, 2x or 4x is transmitted, it is recommended that the spatial mapping matrix applied to HE-STF and beyond is chosen such that it preserves the smoothness of the physical channel, achieved by limiting the variation of each element's real and imaginary values in the spatial mapping matrix across successive within one RU." As in the comment. It is resolved by the resolution of CID8990 in doc
On P404L50 (CID #8995): Among the pre-FEC padding bits, the MAC delivers a PSDU that fills the available octets in the Data field of the HE PPDU, toward the desired pre-FEC padding boundary, represented by ainit value, in the last OFDM symbol(s). 8996 Sigurd Schelstraete 317.21 Change "PHY padding" to "pre-FEC PHY padding"padding (27.10.2 & 27.10.3). See comment Revised. Change to as in the resolution of CID8996 in doc ax editor: please make the following changes in D1.3 Clause 28.3.11.4: On P405L20 (CID #8996): The SERVICE field, PSDU, and PHY padding of the Data field shall be scrambled by the scrambler defined in 17.3.5.5 (PHY DATA scrambler and descrambler). 9013 Sigurd Schelstraete 327.51 First sentence not needed. Delete "This subclause ... using STBC coding" See comment Accepted. Please delete the first sentence of 28.3.11.10 (P415L47). 9169 SUNGEUN LEE 28.3.9 266.03 TGI,HE-LTF1 parameter is defined in the specification. In addition, GI duration is depending on LTF+CP combination, which is not one-to-one mapping from HE-LTF mode. Moreover, the parameter TGI,HE-LTF is already described in Table constants (P802.11ax D1.0). Therefore, TGI,HE-LTF1 would be replaced as TGI,HE-LTF Replace TGI,HE-LTF1 to TGI,HE-LTF Revised. Change to as in the resolution of CID8996 in doc 9170 SUNGEUN LEE 28.3.9 266.06 TGI,HE-LTF2 parameter is never defined in the specification. In addition, GI duration is depending on LTF+CP combination, which is Replace TGI,HE-LTF2 to TGI,HE-LTF Revised. Change to as in the resolution of CID8996 in doc
IEEE P802.11 Wireless LANs Doppler Comment Resolution Date: 2017-09-12 Author(s): Name Affiliation Address Phone Hongyuan Zhang Yan Zhang Hua Mu Rui Cao Marvell , Santa Clara, CA 95054 408-222-1837 hongyuan@marvell.com Bin Tian Lochan Verma Youhan Kim Qualcomm Jianhan Liu Mediatek Ron Porat Broadcom Xiaogang Chen Qinghua Li Intel Ross Jian Yu Ming Gan David Xun yang Shimi Shilo Huawei Abstract: This document contains the comment resolution for Doppler bit, including the proposed spec text for midamble based on 11ax D1.4 Related PHY CIDs: 3320, 3403, 5141, 5418, 5419, 7986, 8416, 8674, 9509, 10350, 4953, 8417, 8775, 10351, 10364, 5246, 5753 5301, 5303, 5413, 5414, 5415, 5416, 5787, 5792, 6123, 7236, 8079, 8418, 8419, 8567, 8912, 9552, 9553, 10210, 10408, 10410. Related MAC CIDs: 3319, 3321, 3401, 3405, 3672, 5089, 5131, 5417, 6084, 8022, 8420, 8657, 9995, 5090
CIDs on Doppler PHY Capabilities 3320 83.41 9.4.2.218.3 Table 9-262aa defines Capabilities Information field. Doppler subfield makes reference to Doppler Procedure. There is no text on "Doppler procedure" procedure needs to be defined. Add technical detail content or remove "Doppler subfield from Table 262aa 3403 83.41 9.4.2.218.3 Table 9-262aa defines Capabilities Information field. Doppler subfield makes reference to Doppler Procedure. There is no text on "Doppler procedure" procedure needs to be defined. Add technical detail content or remove "Doppler subfield from Table 262aa 5141 83.46 9.4.2.218.3 I couldn't find "Doppler procedure" defined anywhere. Either define the procedure or delete the field. As in comment 5418 83.41 9.4.2.218.3 "Doppler procedure" not defined Define "Doppler procedure" or remove it from the text 5419 83.43 9.4.2.218.3 "Doppler procedure" not defined Define "Doppler procedure" or remove it from text 7986 83.40 9.4.2.218.3 The "Doppler procedure" is not defined in this draft. Either add its definition or referred to its definition if it is already defined in another amendment. As in comment. 8416 83.40 9.4.2.218.3 No "Doppler procedure" has been defined so it is not possible to determine how this bit should be set. Return bit to the pool of reserved bits 8674 83.41 9.4.2.218.3 What is "Doppler procedure"? Clarify 9509 83.40 9.4.2.218.3 "Doppler" in Table of the HE PHY Capabilities Information field: "B20 indicates transmitting STA supports transmitting HE PPDUs with Doppler procedure B21 indicates transmitting STA supports receiving HE PPDUs with Doppler procedure" Doppler procedure is not defined. Define the Doppler procedure.
IEEE P802.11 Wireless LANs Proposed resolution for CID 122, 576, 972, 2598 Date: 2016-09-xx Author(s): Name Affiliation Address Phone Email Sigurd Schelstraete Quantenna 3450 W. Warren Avenue Fremont, CA 94538, USA +1 sigurd@quantenna.com Huizhao Wang Quantenna 3450 W. Warren Avenue Fremont, CA USA +1 hwang@quantenna.com Evgeny Khorov IITP RAS Bolshoy Karetny per. 19, build.1, Moscow 127051 Russia +7 495- 650- 4225 khorov@iitp.ru Anton Kiryanov IITP RAS Bolshoy Karetny per. 19, Moscow 127051 Russia +7 495- 650- 4225 kiryanov@iitp.ru Introduction CID Clause Number(C) Page(C) Line(C) Comment Proposed Change 576 10.3.2.4 39 52 The mechanism to configure the use of RTS/CTS is not defined Revised – TGax editor to make the changes shown in CID Commenter PP.LL Comment Proposed changes Resolution 972 Kaiying 39.52 The mechanism for HE AP to configure Comment resolution and supporting Revised – TGax editor to make the changes shown in
the use of RTS/CTS initiated by non-AP STA is still TBD. PPT will be provided 576 EVGENY KHOROV 39.52 The mechanism to configure the use of RTS/CTS is not defined Define the mechanism Revised – TGax editor to make the changes in 122 Alfred Asterjadhi 57.52 The AP may use a TBD mechanism to configure the use of RTS/CTS frames initiated by non-AP STAs. This mechanism should be defined. As in comment. Revised – TGax editor to make the changes shown in 2598 Young Hoon Kwon 39,51 Added text has no technical meaning unless TBD mechanism is described. Delete the sentence or specify the TBD mechanism. Revised – TGax editor to make the changes shown in The 11ax Specification Framework document reorded the following agreement: The amendment define a mechanism to allow the AP to configure the use of RTS/CTS initiated by non-AP STA [MAC Motion #1, January 2015] CID 576 points out that no mechanism has been defined. This submission provides a text proposal for such a mechanism. Text proposal Text changes and additions are shown below. Changes are relative to Draft P802.11-REVmc/D7.0 and IEEE P802.11ax/D0.3. Editor instructions are highlighted in red.
An HE PPDU may have a Packet Extension (PE) field appended at the end of the PPDU, with possible durations being 0 μs, 4 μs, 8 μs, 12 μs, or 16 μs. The PE field provides additional receive processing time at the end of the HE PPDU. The PE field, when present, shall be transmitted with the same average power as the Data field and shall not cause significant power leakage outside of the spectrum used by the Data field. Other than that, and its content is arbitrary. References [1] Discussion of CID 9021, IEEE 802.11/2017-0678
IEEE P802.11 Wireless LANs Resolution for CIDs on UL OFDMA-based Random Access Date: 2016-09-12 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 CID Page Number Line Number Comment Proposed Change Resolution 47 60 34 Is it OCWmi or "For an initial UL PPDU transmission, when an HE STA obtains the value of OCWmin from the HE AP, it shall set the value of OCW to the OCWmin and shall initialize its OBO counter to a random value in the range of 0 and OCWmin." "For an initial UL PPDU transmission, when an HE STA obtains the of OCWmin from the HE AP, it shall set the value of OCW to the OCWmin and shall initialize its OBO counter to a random value in the range of 0 and OCWmin-1." Rejected Since the OCWmin and OCWmax values are by 2^(EOCWmin) – 1 and 2^(EOCWmax) – 1 values, the OBO counter will draw a random number in the range of 0 and OCWmin. 48 60 34 Clarify other situations that a STA initializes its OCW to OCWmin? "For an initial UL PPDU transmission, when an HE STA obtains As in the comment Revised Agree in principle and mentioned about the other case of a successful transmission of an HE PPDU TGax Editor to make the changes as in based
different from the current trigger frame format defined in 9.3.1.23 TGax Editor to make the changes as in 820 60 34 According to text, an HE STAs reset its OBO couter every time when it obtains the value of OCW from HE AP. Althogh it provides immediate congestion control, it cannot provide higher priority for long waiting STAs unlike conventinal 802.11 channel access. Change the followings "For an initial UL PPDU transmission, when an HE STA obtains the value of OCWmin from the HE AP, it shall set the value of OCW to the OCWmin and shall 'get new random value in the range of 0 and OCWmin, an HE STA sets OBO counter to the random value if it is smaller than the original OBO counter.'(initialize its OBO counter to a random value in the range of 0 and OCWmin.") Rejected The proposed change from the commenter does not provide a mechanism to support his comment. Moreover, for fairness among users, such priority in UL OFDMA-based random access is not beneficial, since the control is on the AP in scheduling a trigger frame for random access (different from channel access). 988 60 44 The illustration of the UL random access procedure in Figure 25-1 should be consistent with the following description "If the OBO counter for an HE STA is smaller than the number of RUs assigned to AID value TBD in a Please make the illustration simple and consistent with the description "If the OBO counter for an HE STA is smaller than the number of RUs assigned to AID value TBD in a Trigger frame, then the HE STA shall decrement its OBO counter to zero. Otherwise, the HE STA decrements its OBO counter by a value equal to Revised Agreed in principle and re-drew the figure for improved consistency. TGax Editor to make the changes as in based
Table 24 —EDMG-Header-B field structure and definition Field Number of bits Start bit Description Scrambler Seed 7 0 PSDU Length 22 7 Length of the PSDU field in octets. 5 29 Indicates the modulation and coding scheme for the first spatial stream. If the IsSCPSDU field in the L-Header is equal to 1, this field contains a SC MCS index. If the IsSCPSDU field in the L-Header is equal to 0, this field contains an OFDM MCS index. 5 34 Indicates the modulation and coding scheme for the second spatial stream and is reserved if the number of spatial streams is 1. If the IsSCPSDU field in the L-Header is equal to 1, this field contains a SC MCS index. If the IsSCPSDU field in the L-Header is equal to 0, this field contains an OFDM MCS index.
Additional EDMG PPDU 1 94 A value of 1 indicates that this EDMG PPDU is immediately followed by another EDMG PPDU with no IFS or preamble in between the PPDUs. A value of 0 indicates that no additional EDMG PPDU follows this EDMG PPDU. Reserved 17 95 Set to 0 by the transmitter and ignored by the receiver. CRC 16 112 Header Check sequence. Calculation of the header check sequence is defined in 20.3.7. CID Clause Comment Proposed Change 520 30.3.3.3.5.1 NUC applied signaling restricts NUC usage. Assume NUC support for then is would not be possible to have two spatial streams with 16-QAM and 64-NUC Change description to "If this is set to 1, NUC is applied at the transmitter for the MCSs indicated by EDMG-MCS1 field or EDMG-MCS2 field if supported. If an indicated MCS does not support NUC, uniform constellation is applied for this particular MCS. If set to 0, uniform constellation was applied for both MCSs signaled in EDMG-MCS1 field and EDMG-MCS2 field." Proposed resolution: Accept. Table 24 - EDMG-Header-B field structure and definition Field Number of bits Start bit Description Scrambler Seed 7 0 PSDU Length 22 7 Length of the PSDU field in octets.
Revised for CID 5384 per discussion and editing instructions in 11-17/1077r1 TGax editor: Modify 27.2.3 as the following: 27.2.3 Updating two NAVs …(existing texts)…. A STA, that is not a TXOP holder, shall update the intra-BSS NAV with the duration information indicated by the received frame in a PSDU if and only if all the following conditions are met: The is identified as intra-BSS according to the rule described in 27.2.1 (Intra-BSS and interBSS frame determination(#8111)). The indicated duration is greater than the current intra-BSS NAV value. he RA of the received frame is not the STA's MAC address or the PPDU carrying the frame does not solicit an immediate response from the STA.(#7568)
data traffic that if the AP knows the AC categories of the buffered traffic of the addressed STAs, it should use the lowest AC reported for sending a PPDU that contains such Trigger frame 8275 167 38 It is stated that "An AP may send the Trigger frame using any access category and follows the rules defined in 10.22.2". This is not applicable at all because AP does not know which AC to use. For Data or Ack frames, the AC is determined by examining the TID field of MSDU packet (TID is linked to UPs of MSDU from higher layer as refer to 5.1.1.3). For a Management frame, the AC is AC_VO. What is the procedure for a Trigger Frame, as it is a control frame (which by essence has no TID)? Procedure can envisage a mapping between the priority of the TF and the Access Categories AC0 - AC3 to insert the trigger frame. As example, by following sentence: " the trigger may be conveyed in the AC that corresponds to the type of uplink traffic that the HE STAs are requested to send in response to the trigger frame. If different ACs are requested to STAs, the HE AP may select an Access Category for the trigger frame corresponding to the AC with the highest priority among the requested Access Categories." Additionally, upon emergency for sending a Trigger Frame (BSR reports inform of an important amount of pending data), then " The AP may select one AC queue with the Rejected Please see resolution to CID 7394
IEEE P802.11 Wireless LANs Comment Resolution on retransmission of OFDMA random access Date: 2017-07-13 Author(s): Name Affiliation Address Phone email Jing Ma NICT majing@nict.go.jp Yunbo Li Huawei Introduction Interpretation of a Motion to Adopt A motion to approve this submission means that the editing instructions and any changed or added material are actioned in the TGax Draft. The introduction and the explanation of the proposed changes are not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax Draft (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGax Editor: Editing instructions preceded by “TGax Editor” are instructions to the TGax editor to modify existing material in the TGax draft. As a result of adopting the changes, the TGax editor will execute the instructions rather than copy them to the TGax Draft. CID Page Line Comment Proposed Change Resolution 6139 174 17 Clarify whether the short & long retry counter should be updated or not for every retransmission in random access operation as the comment Revised Agree in principle with the comment. Revised as described in doc.: IEEE 802.11-17/1139r0 7425 174 16 The retransmission procedure for random access is not clearly defined. 1.Define a MIB variable indicates the maximum number of successive retransmission attempts. 2. Change the sentence in L52-L54 of P172 as follows: "The non-AP STA which Rejected We do not need to define separate retry counters or retry limit for UORA case, because D1.3 has already clarified retransmit procedures of HE TB PPDU in 10.22.2.11 (Retransmit procedure) which covers UORA case as well.
IEEE P802.11 Wireless LANs TGax Teleconference Minutes from July to August 2017 Date: 2017-08-10 Author(s): Name Affiliation Address Phone email Yasuhiko Inoue NTT 1-1 Hikaro-no-oka, Yokosuka, Kanagawa 239-0847 ++81-46-859-5097 Osama Huawei Canada Co. Ltd. 303 Terry Fox Drive Ottawa, ONT, CANADA K2K-3J1 Teleconference on Thursday, July 20th, 2017, 10:00 – 12:00 (ET) Meeting called to order by Osama Aboul-Magd (Huawei Technologies), the chairperson of TGax @ 10:05 (ET). Introduction of the chairperson. Agenda Setting Proposed Agenda Call the meeting to order IEEE 802 and 802.11 IPR Policy and Procedure Attendance (Please send an e.mail to Yasuhiko Inoue (inoue.yasuhiko@lab.ntt.co.jp) and/or Osama Aboul-Magd (osama.aboulmagd@huawei.com)) Announcements September ad hoc meeting ePoll: Presentation , “LB225 11ax D1.0 Comment Resolution OMI and Operation Mode,” Liwen Chu (Marvell Semiconductors) , “Proposed Resolutions to CID 5011, 6900, 6998, and 9056,” Osama Aboul-Magd (Huawei Technologies) , “Clauses 3.2, 3.3, and 3.4 Comment Resolution,” Osama Aboul-Magd (Huawei Technologies) , “LB225 11ax D1.0 Comment Resolution 27.10.4 Part 1,” Mark Rison (Samsung Electronics) based on Liwen’s document. AOB Adjourn Approval of the agenda asked if there is any item to add to the agenda. No item to add to the agenda. Chair asked if there is any objection to approve the agenda. No objection. The agenda was approved. IEEE 802 and 802.11 IPR Policy and Procedure Chair mentioned that we are operating under the IEEE 802 and 802.11 Policy and Procedure.
Most comments are related to the abbreviations and their use Added few more abbreviations. Discussion Clarified the meaning of SRP and DSRP_PPDU Add definitions for SRP and DSRP_PPDU and generate new revision Next Step Ready for motion AoB None. Adjournment TGax teleconference adjourned upon completion of all the items on the agenda. List of Attendees – following people were on the call. Name Affiliation 1 Osama Aboul-Magd Huawei Technologies 2 Woojin Ahn WILUS Institute 3 Jarkko Kneckt 4 Jing Ma NICT 5 Abhishek Patil Qualcomm 6 Al Petrick InterDigital 7 Manish Kumar Marvell 8 Shoko Shinohara ?? 9 Chu Marvell 10 Peter ?? 11 Andrew McGarry octoScope, Inc. 12 Sigurd Schelstraete Quantenna 13 Yongho Seok Mediatek 14 Alfred Asterjadhi Qualcomm 15 Po-Kai Huang Intel 16 Kaiying Lv ZTE Teleconference on Thursday, August 3rd, 2017, 10:00 – 12:00 (ET) Meeting called to order by Osama Aboul-Magd (Huawei Technologies), the chairperson of TGax @ 10:05 (ET). Introduction of the chairperson and secretary. Agenda Setting Proposed Agenda Call the meeting to order IEEE 802 and 802.11 IPR Policy and Procedure Attendance (Please send an e.mail to Yasuhiko Inoue (inoue.yasuhiko@lab.ntt.co.jp) and/or Osama Aboul-Magd (osama.aboulmagd@huawei.com)) Announcements September ad hoc meeting Presentation 11-17-0949-01, “,” Mark Rison (Samsung Electronics) 11-17-1220-00, “,” Osama Aboul-Magd (Huawei Technologies) 11-17-1144-00, “,” Robert Stacy (Intel) AOB Adjourn
IEEE P802.11 Wireless LANs TGax Teleconference Minutes from July to August 2017 Date: 2017-08-28 Author(s): Name Affiliation Address Phone email Yasuhiko Inoue NTT 1-1 Hikaro-no-oka, Yokosuka, Kanagawa 239-0847 Japan ++81-46-859-5097 inoue.yasuhiko@lab.ntt.co.jp Huawei Technologies Canada Co. Ltd. 303 Terry Fox Drive Ottawa, ONT, CANADA K2K-3J1 Teleconference on Thursday, July 20th, 2017, 10:00 – 12:00 (ET) Meeting called to order by Osama Aboul-Magd (Huawei Technologies), the chairperson of TGax @ 10:05 AM (ET). Introduction of the chairperson. Agenda Setting Proposed Agenda Call the meeting to IEEE 802 and 802.11 IPR Policy and Procedure Attendance (Please send an e.mail to Yasuhiko (inoue.yasuhiko@lab.ntt.co.jp) and/or Osama Aboul-Magd (osama.aboulmagd@huawei.com)) Announcements September ad hoc meeting ePoll: Presentation , “LB225 11ax D1.0 Comment Resolution OMI and Operation Mode,” Liwen Chu (Marvell Semiconductors) , “Proposed Resolutions to CID 5011, 6900, 6998, and 9056,” Osama Aboul-Magd (Huawei Technologies) , “Clauses 3.2, 3.3, and 3.4 Comment Resolution,” Osama Aboul-Magd (Huawei Technologies) , “LB225 11ax D1.0 Comment Resolution 27.10.4 Part 1,” Mark Rison (Samsung Electronics) based on Liwen’s document. AOB Adjourn Approval of the agenda asked if there is any item to add to the agenda. No item to add to the agenda. Chair asked if there is any objection to approve the agenda. No objection. The agenda was approved. IEEE 802 and 802.11 IPR Policy and Procedure Chair mentioned that we are operating under the IEEE 802 and 802.11 Policy and Procedure.
Discussion Many editorial and technical suggestions were provided. Use symbol for “floor” Extend Table 9-74 to the new equation Cross reference to the new equation TF maybe transmitted on different BW. Does this limit the Nss a transmitter can use? Wording is all about PPDU bandwidth not channel bandwidth\The case where the first transmission is HE and the second transmission is not HE is not covered “Valid 20 MHz” what does it mean? Next Step Liwen to include the changes and generate a new revision. Osama Aboul-Magd (Huawei Technologies) presented “Clauses 3.2, 3.3, and 3.4 Comment Resolution,” based on the submission 11-17-1174-00. Summary Resolutions for CIDs 5308, 6070, 6914, 6915, 6916, 6922 (Editor group), and 6920, 7222 (MAC) are proposed. Abbreviations of BQRP, BSRP, MU-BAR, MU EDCA, SRP and DSRP_PPDU are provided. Discussion Next Step Mark (Samsung Electronics) presented “LB225 11ax D1.0 Comment Resolution 27.10.4 Part 1,” based on the submission 11-17-0949-01. Summary Mark has made further modification to the 17/0949 (Re: Multi-TID A-MPDU) and created rev.1 of the document. Discussion Next Step AOB None. Adjournment No time to go through the rest of the agenda items. Meeting adjourned at 12:00 (ET). List of Attendees – following people were on the call. Name Affiliation 1 Osama Aboul-Magd Huawei Technologies 2 Woojin Ahn WILUS Institute 3 Jarkko Kneckt Apple 4 Jing Ma NICT 5 Abhishek Patil Qualcomm 6 Albert Petrick InterDigital 7 Kiseon Ryu LG Electronics 8 Yongho Seok Mediatek 9 Xiaofei Wang InterDigital 10 Sungeun Lee Cypress
– • Antitrust and Competition Policy – • IEEE-SA Patent Policy – – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Guidelines (Approved 17 Mar 2017) – as updated in • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 17 Mar 2017) – July 28th telecon: Editor Report: Submissions: August 4, 2017: Submissions August 11, 2017: Submissions: August 18, 2017: Submissions:
CID Clause Page Comment Proposed change 196 53.20 20 It is not clear how the secondary channel is defined for EDMG BSS, especially considering there are two types of communication modes: channel bonding and channel aggregation. Define the secondary channels for channel bonding supported STAs and channel aggregation supported STAs. Define the related indications for the sencondary channel. 450 10.01 Figure 3 --The channel-list parameter element for 4.32 GHz, 6.48 GHz and 8.64 GHz channel illustrates cases with primary channel on the edge. The primary channel may reside in the middle as well. Add few more figures to illustrate missed or provide relevant text to make it clear. Discussion: Contribution 11-17/0865 adopted in D0.4 addresses those two comments. With new definition, the issue raised by the comment is resolved as follow: The location of the Secondary, Secondary1, Secondary2 channels depends the location of the Primary channel which is diffrenciate by the EDMG Primary Channel Offset indication. Below are diagram that shows the locations of secondaries channgels in case of channel bonding. The channel-list parameter for 4.32 GHz, 6.48 GHz and 8.64 GHz channel width for EDMG Primary Channel Offset=0 The channel-list parameter for 4.32GHz, 6.48GHz and 8.64GHz channel width when EDMG Primary Channel Offset=1 The channel-list parameter element for 2.16+2.16 GHz and 4.32+4.32 GHz channel width Proposed resolution: Reject CID Clause Page Comment Proposed change 212 12.00 9.3.1.3.1 Since the subfield is not used by other BA Types, then why not leave it as reserved in those cases. Replace last sentence with "This subfield is reserved if the BlockAck variant used is not EDMG Multi-TID BlockAck variant" 449 12.04 "The Management ACK subfield is set to one to indicate that frames of type Management that are not Action No Ack are acknowledged. Otherwise, it is set to zero. If "In EDMG Multi-TID BlockAck variant the Management ACK subfield is set to one to
to Per User Info instead: For MU-BAR, it needs to carry several BARs targeted to several STAs. The current mapping is wrong. Instead, for MU-BAR, its Common info field's Tigger Dependent Common Info field can be omitted, or defined for other purpose. And map the current defined Trigger Dependent Common Info field into each STAs' Per User Info fields, and hence map the BAR Control & BAR Information subfields into Per User Info's Trigger Dependent Per User Info subfield. (A technical contribution will be followed later) Figure into Per User Info's Trigger Dependent Per User Info subfield instead. And fix the subclause 9.3.1.23.1 text to describe the new mapping (a technical contribution will be followed later) mapping is wrong and therefore the text needs to be modified. Proposed resolution is to specify that the Type depended common info field’s length is 0. The BAR Control information and BAR Information is mapped to Type depended Per User Info subfield. 2220 Tomoko Adachi 22.01 The explanation of the variant needs to be reconsidered. Figure 9-51d is completely the same with Figure Correct the explanation of the variant. Revised. Current text in section 9.3.1.23.1 is removed and text as specified in current
The title of Figure 9-51e is completely the same with Figure This should explain the Trigger Dependent Per User Info field. document added. 2586 Young Hoon Kwon 22.20 Wrong figure. It should be Figure 9-51e. Modify the text from "... defined in Figure to "... defined in Figure Revised. Current text in section 9.3.1.23.1 is removed and text as specified in current document added. TGax Editor: Insert the following at the end of subclause 25.4.5: An HE STA that receives a BAR or a MU BAR variant Trigger frame that contains a Compressed BlockAckReq variant in the Per User Info field addressed to the STA shall respond with a BlockAck frame as defined in 10.24.7 (HT-immediate block ack extensions) or a Multi-STA BlockAck frame as defined in 25.4 (Block acknowledgment). An HE STA that receives a Multi-TID BAR frame or a MU BAR variant Trigger frame that contains a Multi-TID BlockAckReq variant in the Per User Info field addressed to the STA shall respond with a Multi-STA BlockAck frame that contains a Per STA Info subfield with Block Ack Bitmap subfield for each of the TIDs (with values less than 8) contained in the blockackreq frame and the length of each Block Ack Bitmap subfields shall be equal to the solicited Bitmap length ( i.e., FN subfields in solicited Block Ack Request Starting Sequence Control and responding Block Ack Starting Sequence Control for the same TID are equal).