zilongwang/ReadingBank huggingface dataset:
14339 20 limiting 20MHz only STA on the primary 20MHz may cause the poor network performance. Enable 20MHz only STA on secondary channel. as in the comment Revised- Agree in principle. The baseline TWT mechanism defined in 802.11ah already supports a secondary channel operation of a non-AP STA. Also, since 802.11ax supports the TWT mechanism, we can enable a 20MHz-only non-AP HE STA on a secondary channel with a minimal change. TGax editor changes as shown in the as specified in 11-18/0. 11834 The spec should allow the TWT channel to be negotiated between AP and the STA The spec should the TWT channel to be negotiated between AP and the STA Revised- Agree in principle. By allowing the TWT channel to be negotiated between an AP and a STA, we can enable a 20MHz-only non-AP HE STA on a secondary channel with a minimal change. Please refer a benefit of a 20MHz-only non-AP HE STA on a secondary channel from document. TGax editor makes changes as shown in the as specified in 11-18/0. 11837 Different channels should be allowed to maximize the utlization of the medium and reducing the consumption for the STAs Remove the contstraint that HE STA cannot use TWT channel field Revised- Agree in principle. By allowing the TWT channel to be negotiated between an AP and a STA, we can enable a 20MHz-only non-AP HE STA on a secondary 0
Parameters listed in Table 28-13 not only apply to Data field but aslo apply to other HE-modulated fields in a non-OFDMA HE PPDU. It is more accurate to rename Table 28-13 to “Tone allocation related constants for the HE-mdoulated fields in a non-OFDMA HE PPDU” ax editor: please replace Table 28-13 title “Tone allocation related constants for the Data field in a HE PPDU” with “Tone allocation related constants for the HE-modulated fields in a HE PPDU” and change the corresponding references throughout the draft. 11383 Bin Tian 28.3.9 397.13 Remove "and HE TB PPDU" since alpha_r doesn't apply to TB PPDU in eq 28-4 as in the comment Revised. Change to as in the resolution of CID11383 in doc ax editor: please make the following change in D2.0 Clause 28.3.9 On P397L13 (CID #11383): For an HE SU PPDU HE ER SU PPDU, is always set to 1. 11384 Bin Tian 28.3.9 397.23 In equation (28-5), it should be |Kr Field| instead of Kr Field as in the comment Revised. Change to as in the resolution of CID11383 in doc ax editor: please make the following change in D2.0 Clause 28.3.9 On P397L23 (CID #11384): replace “, for HE modulated fields in an HE TB PPDU” with “, for HE modulated fields in an HE TB PPDU” in Equation (28-5). 11385 Bin Tian 28.3.9 398.43 It's better to add a subscript r (i.e. RU id) to the spatial mapping matrix Q_k_(iseg) and Q_k,u_(iseg) since its dimension depends on Nsts_r,total which varies per RU. as in the comment Rejected. Subcarrier index k is a function of RU index r. RU index r can be inferred from subcarrier index k.
Parameters listed in 28-13 not only apply to Data field but aslo apply to other HE-modulated fields in a non-OFDMA HE PPDU. It is more accurate to rename Table 28-13 to “Tone allocation related constants for the HE-modulated fields in a non-OFDMA HE PPDU” ax editor: please replace Table 28-13 title “Tone allocation related constants for the Data field in a HE PPDU” with “Tone allocation related constants for the HE-modulated fields in a HE PPDU” and change the corresponding references throughout the draft. 11383 Bin Tian 28.3.9 397.13 Remove "and HE TB PPDU" since alpha_r doesn't apply to TB PPDU in eq 28-4 as in the comment Revised. Change to as in the resolution of CID11383 in doc ax editor: please make the following change in D2.0 Clause 28.3.9 On P397L13 (CID #11383): For an HE SU PPDU HE ER SU PPDU, is always set to 1. 11384 Bin Tian 28.3.9 397.23 In equation (28-5), it should be |Kr Field| instead of Kr Field as in the comment Revised. Change to as in the resolution of CID11383 in doc ax editor: please make the following change in D2.0 Clause 28.3.9 On P397L23 (CID #11384): replace “, for HE modulated fields in an HE TB PPDU” with “, for HE modulated fields in an HE TB PPDU” in Equation (28-5). 11385 Bin Tian 28.3.9 398.43 It's better to add a subscript r (i.e. RU id) to the spatial mapping matrix Q_k_(iseg) and Q_k,u_(iseg) since its dimension depends on Nsts_r,total which varies per RU. as in the comment Rejected. Subcarrier index k is a function of RU index r. RU index r can be inferred from subcarrier index k.
11895 Hongyuan Zhang 248.1 For accurate timing synchronization at each STA responding a trigger frame, the legacy part preamble (L-STF, L-LTF, ...) of the PPDU carrying trigger frame shall not be beamformed. There are existing implementations that may beamform the legacy preamble or the whole non-HT PPDU, but it is better to be disallowed if the PPDU is carrying a trigger frame. Add a note: "Beamforming the non-HT preamble of the PPDU carrying a Trigger Frame is not Revised. Change to as in the resolution of CID11895 in doc ax editor: please make the following change in D2.0 Clause 27.5.3.2.3 On P248L1 (CID #11895): Please add the following sentence on P248L3. An HE AP shall not use STBC encoding for a PPDU that carries a Trigger frame. Dorothy Stanley 142.47 I can't find a definition or equation for N_STS,total as in comment Revised. Change to as in the resolution of CID11545 in doc 11546 Dorothy Stanley 142.56 I can't find a definition or equation for N_STS,total as in comment Revised. Change to as in the resolution of CID11546 in doc ax editor: please make the following change in D2.0 Clause 9.4.2.237.3 On P142L47 (CID #11545): replace with “the total number of space-time streams” On P142L56 (CID #11546): replace with “the total number of space-time streams” ax editor: please make the following change in D2.0 Clause 9.3.1.23
set the TXVECTOR parameters as follows" in 27.5.3.3, add a "NOTE---The number of symbols (N_SYM) contained in the HE TB PPDU is derived from the Length subfield in the Common Info field of the Trigger frame according to Equation (re)number the NOTEs in 27.5.3.3 13393 Ron 459.60 "The AP indicates the common NSYM, padding factor, STBC indication and LDPC Extra Symbol Segment fields in the Trigger frame." AP doesn't indicate NSYM but LENGTH. Also missing is the PE disambiguity bit. (in the trigger frame the Packet Extension Subfield contain both pre-FEC Padding factor and PE Disambiguity). Change to: "The AP indicates the common LENGTH, pre-FEC padding factor, PE disambiguity, STBC indication and LDPC Symbol Segment fields in the Trigger frame." Revised. Change to as in the resolution of CID13393 in doc 13394 Ron porat 459.60 The text says that the AP indicates certain common parameters for the HE TB PPDU, but it does not explicitly mention that the AP is free to select these independent of the rules for other PPDU types. In particular, the selection of LDPC extra symbol, and the amount of packet extension (T_PE), may be selected by the AP in a way that is unique insert a note: "Note: The AP may at its own discretion select a (0, 8, 16), pre-FEC padding factor (1,2,3,4) and a LDPC symbol (0, 1) for the HE TB PPDU. Revised. Change to as in the resolution of CID13394 in doc
Next Step document 11-18-0079 is ready for motion.. Oghenekome Oteri (InterDigital) presented “Comment Resolutions on Clause 9.4.1.63 D2.0 (HE Compressed Beamforming Report field),” based on the submission 11-18-0080-01. Summary document 11-18-0079-01 was revisited. Kome explained the document highlighting the changes. CIDs: 12683, 12702, and 13697. Discussion resolutions for the above CIDs are REJECTED. discussion. Straw Poll: Do you agree with the resolutions to CIDs 12702, 13697 in doc 11-17/0080r1? Accepted with no objection Next Step document 11-18-0080 is ready for motion.. Abhishek Patil (Qualcomm) presented “CIDs related to Random Access – Part 1,” based on the submission 11-17-1849-01. Summary for the following CIDs on OFDMA Random Access and changes to the spec text are proposed. CIDs: 11033, 13196, 11992, 14208, 12224, 14210, 13198, 11001, 11364, 12178, 11731, 11732, 12179, 11045, 13796, 11379 (16 CIDs). Discussion #11001: People discussed about the Trigger Dependent User Info field which did not get to a consensus. proposed text in 27.5.5.2 was updated based on the comment from a member. also discussed about the CID 12179.. Recess @ 15:00 Break Meeting reconvened @ 15:30. Comment Resolutions Abhishek Patil (Qualcomm) continued presentation of “CIDs related to Random Access – Part 1,” based on the submission 11-17-1849-01. Discussion #12179: Reached consensus by the offline discussion during the break. Poll: Do you agree with the resolutions to CIDs 11033, 13196, 11992, 14208, 12224, 14210, 13198, 11001, 11364, 12178, 11731, 11732, 12179, 11045, 13796, 11379 in doc No objection to the resolution of the CIDs written in black
The number of HE-LTF symbols for NDP Feedback Report is 2, so the indicated value in Common Info field of the Trigger frame should be 1 (minus 1 principle). In addition, it is clear do describe the terminology of HE-LTF as 4x Change 'is set to 2 for 2 symbols' to 'is set to 1 for two 4x HE-LTF symbols' Is "User Info field" for the NDP Feedback Report Poll Trigger frame meant to replace the "User Info" field in the Trigger frame? Or is this really the Trigger Dependent User Info? Please clarify. as in comment NDP feedback currently doesn't provide an opportunity for non-associated STAs to request a probe response, which means a large amount of probe requests and probe response messages. Add 1 bit from 'reserved' for 'Request for Probe Response'. Change Eq. 9-ax1 to Given the "encoded value" and "its definition" of Multiplexing Flag as shown in "The Multiplexing Flag subfield indicates the number of STAs that are multiplexed with codes on the same set of tones in the same RU, and is encoded as the number of STAs minus 1", "Multiplexing Flag" needs to be replaced with "Multiplexing Flag+1" in Equation 9-ax1 as in comment Is the Multiplexing Flag subfield really the number of STAs that are multiplexed with P-matrix codes on the same set of tones in the same RU minus 1? Then it seems that the Multiplexing Flag subfield may become 0 resulting in no STAs. Delete "minus 1". Incorrect section reference Fix section reference to 27.5.6 misspelling "Ressource" "Ressource" in exponent should be "Resource" 7
where is defined in Table 32-1(Timing-related constants) is defined in Table 32-1(Timing-related constants) 32.4.3 Table of time and length characteristics Characteristics Value aCCAMidTime 25 µs [do we need this part?] aPPDUMaxTime 5.484 ms aPSDUMaxLength 166 octets (see NOTE 1) aRxPHYStartDelay 88 µs (see NOTE 2) NOTE 1-This is the maximum length in octets for a WUR PPDU with MCS1, single stream, and limited by 1332 possible data symbols in aPPDUMaxTime. This is the maximum PSDU length a WUR PHY could support assuming no restrictions in MAC. NOTE 2-This value arises from the time to the end of WUR-SF with MCS1. Parameters for WUR-MCSs The rate-dependent parameters for 62.5 kb/s and 250 kb/s are given in Table 32-5-xxx1. Manchester code shall be used for all of the data rates for the Data field of the WUR PPDU. Table 32-5-xxx1—Wake-up PPDU-MCS MCS Index Modulation Symbol Structure Symbol Duration NSPDB NSPCB NCBPDB Data rate (kb/s) 0 OOK Information 0 4 µs ON+4 µs OFF+ 4 µs ON+4 µs OFF 16 µs 4 1 4 62.5 Information 1 4 µs OFF+4 µs ON+ 4 µs OFF+4 µs ON 1 OOK Information 0 2 µs ON+2 µs OFF 4µs 2 1 2 250 Information 1 2 µs OFF+2 µs ON
Data field TSYM0,OFF 4 µs OFF duration of WUR MCS0 OOK symbol in WUR Data field TSYM0 4 µs = TSYM0,ON = TSYM0,OFF Duration of WUR MCS0 OOK symbol in WUR Data field TSYM1,ON 2 µs ON duration of WUR MCS1 OOK symbol in WUR Data field TSYM1,OFF 2 µs OFF duration of WUR MCS1 OOK symbol in WUR Data field 2 µs = TSYM1,ON = TSYM1,OFF Duration of WUR MCS1 OOK symbol in WUR Data field TSYM TSYM0 or TSYM1 depending on WUR MCS Duration of OOK symbol in WUR Data field TSync TBD Duration of OOK symbol in WUR-Sync field TL-STF 8 µs = 10 × TDFT,WUR /4 Non-HT Short Training field duration TL-LTF 8 µs = 2 × TDFT,WUR + TGI,L-LTF Non-HT Long Training field duration TL-SIG 4 µs Non-HT SIGNAL field duration TWUR-Mark 4 µs WUR-Mark field duration TWUR-Sync0 128 µs WUR-Sync field duration for WUR MCS0 64 µs WUR-Sync field duration for WUR MCS1
Frequently used parameters defines parameters used frequently in Clause 32. Frequently used parameters Symbol Explanation NSPDB Number of OOK symbols per data bit. For WUR MCS0, NSPDB =4. For WUR MCS1, NSPDB =2. NSPCB Number of OOK symbols per encoded bit. NSPCB =1. NCBPDB Number of coded bits per data bit. For WUR MCS0, NCBPDB =4. For WUR MCS1, NCBPDB =2. NTX Number of transmit chains NWUR-Sync Number of OOK symbols in the field Mathematical description of signals The transmitted signal is described in complex baseband signal notation. The actual transmitted signal on transmit chain, , is related to the complex baseband signal by the relation shown in Equation (32-xx). (32-xx) Where Re{.} Represents the real part of a complex variable is the center frequency is the baseband WUR signal on transmit chain . The transmitted RF signal is derived by up-converting the complex baseband signal, which consists of several fields. The timing boundaries for the various fields are shown in Figure 32-1 where NWUR-Sync is the number of WUR-Sync symbols and is defined in Table 32-xx. The time offset, , determines the starting time of the corresponding relative to the start of L-STF (t = 0).
where is defined in Table 32-1(Timing-related constants) is defined in Table 32-1(Timing-related constants) 32.4.3 Table of time and length characteristics Characteristics Value aCCAMidTime 25 µs [do we need this part?] aPPDUMaxTime 5.484 ms aPSDUMaxLength 166 octets (see NOTE 1) aRxPHYStartDelay 88 µs (see NOTE 2) NOTE 1-This is the maximum length in octets for a WUR PPDU with MCS1, single stream, and limited by 1332 possible data symbols in aPPDUMaxTime. This is the maximum PSDU length a WUR PHY could support assuming no restrictions in MAC. NOTE 2-This value arises from the time to the end of WUR-SF with MCS1. Parameters for WUR-MCSs The rate-dependent parameters for 62.5 kb/s and 250 kb/s are in Table 32-5-xxx1. Manchester code shall be used for all of the data rates for the Data field of the WUR PPDU. Table 32-5-xxx1—WUR PPDU-MCS MCS Index Modulation Symbol Structure Symbol Duration NSPCB NCBPDB Data rate (kb/s) 0 OOK Information 0 4 µs ON+4 µs OFF+ 4 µs ON+4 µs OFF 16 µs 4 1 4 62.5 Information 1 4 µs OFF+4 µs ON+ 4 µs OFF+4 µs ON 1 OOK Information 0 2 µs ON+2 µs OFF 4µs 2 1 2 250 Information 1 2 µs OFF+2 µs ON
FORMAT Determines the format of the PPDU. Enumerated type: WUR indicate WUR PPDU format Y Y LLENGTH FORMAT is WUR Indicates the length of the PSDU in octets in the range of 1 to TBD. This value is used by the PHY to determine the number of octet transfers that occur between the MAC and the PHY. Y N Otherwise TBD LDATARATE FORMAT is WUR Indicates the value representing 6 Mb/s in the 20 MHz channel. Y N Otherwise TBD CHANNELCENTERFREQUENCY FORMAT is WUR TBD Y N Otherwise TBD CHANNEL BANDWIDTH FORMAT is WUR TBD Y N Otherwise TBD N N WUR_DATARATE FORMAT is WUR Determines the transmission bandwidth of the WUR PPDU. Enumerated type: LDR indicates WUR Low Data Rate for the data rate 62.5 kb/s HDR indicates WUR High Data Rate for the data rate 250 kb/s Y Y Otherwise TBD N N
32.4.3 Table of time and length characteristics Table 32-K—WUR PPDU Time and Length Characteristics Characteristics Value aCCAMinTime 25 µs aPPDUMaxTime 5.484 ms aPSDUMaxLength 166 octets (see NOTE 1) aRxPHYStartDelay 88 µs (see NOTE 2) NOTE 1-This is the maximum length in octets for a WUR PPDU with HDR, single stream, and limited by 1332 possible data symbols in aPPDUMaxTime. This is the maximum PSDU length a WUR PHY support assuming no restrictions in MAC. NOTE 2-This value arises from the time to the end of WUR-Sync with HDR. Parameters for WUR-Data Rates The rate-dependent parameters for 62.5 kb/s and 250 kb/s are given in Table 32-L. Manchester-based encoding shall be used for all the data rates for the Data field of the WUR PPDU. Table 32-L—WUR PPDU-Data Rates Data Rate Modulation Symbol Structure Equivalent Information Bit Duration NSPDB Data rate (kb/s) LDR OOK Information 0 4 µs ON+4 µs OFF+ 4 µs ON+4 µs OFF 16 µs 4 62.5 Information 1 4 µs OFF+4 µs ON+ 4 µs OFF+4 µs ON HDR OOK Information 0 2 µs ON+2 µs OFF 4µs 2 250 Information 1 2 µs OFF+2 µs ON
extended BSS load element further provides the the spatial stream underutilization given the busy channel such that unassociated STA with MU-MIMO capability can choose the proper AP. Now 11ax introduce OFDMA, there is the probability of frequence underutilization given the busy channel. spatial/frequency underutilization to solve load unbalancing problem in 802.11ax TGax editor makes changes as shown in the as specified in Discussion: … Load balancing problem were considered 802.11-2016[1] includes Channel utilization in time domain was proposed in 9.4.2.28 BSS Load element Spatial stream underutilization in space domain was proposed in 9.4.2.160 Extended BSS Load element STAs use it for implementation-specific AP selection, in to obtain more transmission opportunities. 802.11ax introduced and MU-MIMO two key features where partial bandwidth MU-MIMO is allowed which is different from the downlink full bandwidth MU-MIMO in 802.11ac, but these two key features are not reflected in traffic load for HE BSSs Frequency underutilization regarding and spatial stream underutilization regarding (including both full bandwidth MU-MIMO and partial bandwidth MU-MIMO) were first present in [2] and [3] The concept of frequency and spatial stream underutilization for OFDMA/MU-MIMO was agreed in 2017 Korea IEEE MAY F2F meeting [4]. We discusse frequency underutilization and spatial stream underutilization three aspects, including OFDMA only transmission, partial bandwidth MU-MIMO transmission and full bandwidth MU-MIMO transmission. We assume that the maximum supported streams on AP side is 8 and the bandiwth is 20 MHz in the following discussion. 1. Regarding OFDMA only transmission, each RU will be selected to assign to some STA according to frequency selective. However, in some case, some RU is not assigned because that this RU is deep fading for the scheduled STA which have traffic or non-contiguous RUs are not allowed to assigned to one STA as shown in the following figure. According to the following figure, AP has underutilized frequency domain resource (52 tone RU is available) for given busy time of the medium which is not reflected in BSS Load element and extended BSS Load element.
The Inactivity Interval is 4 octets long and contains an unsigned integer that specifies the minimum amount of time, in microseconds, that can elapse without arrival or transfer of an MPDU belonging to the TS before this TS is deleted by the MAC entity at the HC. uspension Interval field is 4 octets long and contains an unsigned integer that specifies the minimum amount of time, in microseconds, that can elapse without arrival or transfer of an MSDU belonging to the TS before the generation of successive QoS(+)CF-Poll is stopped for this TS. A value of 4 294 967 295 (= 232 – 1) disables the suspension interval, indicating that polling for the TS is not to be interrupted based on inactivity. The value of the suspension interval is always less than or equal to the inactivity interval. TGax editor: modify Table 9-18a as follows: Control ID subfield values Control ID value Meaning Length of the Control Information subfield (bits) Content of the Control Information subfield 0 UL MU response scheduling (UMRS)(#4727) 26 See 9.2.4.6.4.2 (UMRS Control) 1 Operating mode (OM)(#4727) 12 See 9.2.4.6.4.3 (OM Control) 2 HE link adaptation (HLA)(#4727) 26(#4786) See 9.2.4.6.4.4 (HLA Control) 3 Buffer status report (BSR) 26 See 9.2.4.6.4.5 (BSR Control) 4 UL power headroom (UPH)(#4727) 8 See 9.2.4.6.4.6 (UPH Control) 5 Bandwidth query report (BQR) 10 See 9.2.4.6.4.7 (BQR Control) 6 Command Control Indication(#8087) 8 See 9.2.4.6.4.8 (CAS Control))(#5025, #7471) -15 Reserved TGax editor: Add a subclause 9.2.4.6.4.9 as follows:
Control ID subfield values Control ID value Meaning Length of the Control Information subfield (bits) Content of the Control Information subfield 0 UL MU response scheduling (UMRS)(#4727) 26 See 9.2.4.6.4.2 (UMRS Control) 1 Operating mode (OM)(#4727) 12 See 9.2.4.6.4.3 (OM Control) 2 HE link adaptation (HLA)(#4727) 26(#4786) See 9.2.4.6.4.4 (HLA Control) 3 Buffer status report (BSR) 26 See 9.2.4.6.4.5 (BSR Control) 4 UL power headroom (UPH)(#4727) 8 See 9.2.4.6.4.6 (UPH Control) 5 Bandwidth query report (BQR) 10 See 9.2.4.6.4.7 (BQR Control) 6 Command Control Indication(#8087) 8 See 9.2.4.6.4.8 (CAS Control))(#5025, #7471) -15 Reserved TGax editor: Add a subclause 9.2.4.6.4.9 as follows:
IEEE P802.11 Wireless LANs 11ax D2.0 MAC Comment Resolution for CID 18555 Date: 2018-01-14 Author(s): Name Affiliation Address Phone email Guoqing Li Apple Inc. 1 Infinity Loop, Cupertino, CA 95014 Guoqing_li@apple.com Pooya Monajemi Cisco 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 D2.0 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D2.0 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 P.L Clause Comment Proposed Change Resolution Guoqing Li 194.21 10.22.1 As 11ax is transitioning into a scheduling-based system, there is a need for AP to collect more info on STA's traffic and QoS requirement for efficient scheduling, which is what TSEPC is for. Currently, TSPEC is closely tied to HCCA which is Modify the text on TSPEC to make sure that HE STA can use it efficiently and correctly. Revised – The description does not any specific sounding procedure. It simply says that a STA always uses multiple protection in a TXOP that includes HE NDP Announcement or HE BRP Trigger
IEEE P802.11 Wireless LANs Comment resolution on Space-Time Block Coding Date: 2017-01-15 Author(s): Name Affiliation Address Phone email Thomas Handte Sony Europe Ltd. Heldelfinger Strasse 61 +49 711 5858 236 thomas.handte @ sony.com Dana Ciochina Sony Europe Ltd. dana.ciochina @ sony.com Comments CID Clause Comment Proposed Change 1617 30.5.9.5.3 Space-time block coding is limited to one spatial stream only. It can be beneficial to generalize to more spatial streams comment resolution will be provided 2029 30.5.3.1 The text is too restrictive as STBC can be applied to multple spatial streams Relax the text and complete the STBC descritption 2030 30.5.3.3.2 STBC can be applied to multiple spatial streams, thus the description: if stbc is applied, a single spatial stream is mapped to 2 space time streams is too restrictive. Replace "single" with "each" and complete the multiple STBC description for the SU-MIMO case 2034 30.6.2.1 OFDM mode should multiple STBC with multiple spatial streams Please extend to N_ss>=1 Discussion Commenters propose to extend current 11ay STBC encoding to multiple streams for SC (1617, 2029, 2030) and OFDM (2034). Motivation STBC can exploit MIMO features of AP in asymmetric MIMO APs typically have more MIMO features than STAs STBC provides transmit diversity in this case which can be used to increase throughput, i.e. higher channel gain, higher modulation order provide redundancy, i.e. more robust communication in case of shadowing or blockage As of today, 11ay STBC encoding is limited to a single spatial stream (NSS=1) Benefits of STBC in MIMO are too versatile to be limited to a single spatial stream STBC in CA is not possible as even NSS is prerequisite Often effective channels can get block diagonal i.e. channels have this structure means negligible interference each can either be occupied or be block diagonal matrix Appropriate beamforming and/or reordering (spatial mapping) may be required to achieve block diagonal shape diagonalization can even be an objective function for beamforming
IEEE P802.11 Wireless LANs Comment Resolution on OFDM data rate Date: 2018-1-15 Author(s): Name Affiliation Address Phone Hiroyuki Motozuka Panasonic 600 Saedo-cho, Yokohama, Kanagawa, Japan motozuka.hiroyuki@jp.panasonic.com Takenori Sakamoto sakamoto.takenori@jp.panasonic.com Yutaka Murakami murakami.ytk@jp.panasonic.com Lei Huang lei.huang@sg.panasonic.com Gaius Wee yaohuang.wee@sg.panasonic.com Kazu Takahashi takahashi.kazu@jp.panasonic.com CID Clause Page Comment Proposed Change Proposed Resolution 1527 30.6.7 347.01 Typo in Table 78, N_SD=336, MCS3, Normal GI: "094.20" should be "1094.20"; or more acculately, "1094.21" As per comment Accepted TGay editor to make the changes shown in under all headings that include CID 1527. 1528 30.6.7 347.01 The second decimals of the data rates look inaccurate in Table 78 and Table 79. For example, for N_SD=366, MCS 5 and Normal GI, the data rate is 1276.578..., then it should be denoted as 1276.58 instead of 1276.60. Correct the values Revised TGay editor to make the changes shown in under all headings that include CID 1528. Discussion The data rate tables for the DMG SC mode in IEEE802.11-2016 and the EDMG SC mode in P802.11ay D1.0 have resolution of 0.01 Mbps. We propose to align the vanues in the table for EDMG OFDM mode with the above mentioned resolution. The current values are accurate only on the first 5 digits, and may be inaccurate in case the rate exceeds 1000 Mbps. Proposed changes to D1.0
IEEE P802.11 Wireless LANs Draft Text for OFDM Feedback Request Date: 2018-01-10 Author(s): Name Affiliation Address Phone email Kome Oteri InterDigital 9710 Scranton Road, #250, San CA, 92121 +1 858 210 4826 Kome.oteri@interidigital.com Alphan Sahin Rui Yang Dana Ciochina Sony Jinsoo Choi LG Electronics SunWoong Yun LG Electronics Make the following changes on D1.0: 9.4.2.255 EDMG BRP Request element The EDMG BRP Request element provides BRP configuration in addition to the BRP configuration provided in the BRP Request field. The EDMG BRP Request element is defined in Figure 45. B0 B7 B8 B15 B16 B23 B24 B31 B32 B39 B40 B50 B51 B52 B53 B56 B57 B58 Element ID Length Element ID Extension TX Sector ID EDMG P EDMG M EDMG N Bits: 8 8 8 8 8 11 2 4 2
Resolution: Revised. Editor: change the text as below, page X, line Y, [2] For 2.16+2.16 GHz and 4.32+4.32 GHz PPDU transmission, the total number of transmit chains, NTX, shall be an even number. he first NTX/2 transmit chains shall be used for transmission on the primary channel and the second NTX/2 transmit chains shall be used for transmission on the secondary channel. CID 2083 Comment: Table 34: PSDU Length is missing the range of octets Proposed change: Specify that the Length of the PSDU field ranges from 14 - 1023 octets Resolution: Accepted. Editor: change the text as below, page 246, line 1, [2] 34—EDMG-Header-A1 subfield definition Field Number of bits Start bit Description BW 8 0 See Table 36 Primary Channel Number 3 8 See Table 36 PSDU Length 10 11 Length of the PSDU field in octets EDMG TRN Length 8 21 See Table 36 RX per Each TX 8 29 See Table 36 EDMG P 2 37 See Table 36 EDMG M 4 39 See Table 36 EDMG N 2 43 See 36
SS Descriptor Set 4 9 51 Describes the SS assignment to the fifth STA addressed within the MU PPDU. This field is formatted as described in Table 39. SS Descriptor Set 5 9 60 Describes the SS assignment to the sixth STA addressed within the MU PPDU. This field is formatted as described in Table 39. SS Descriptor Set 6 9 69 Describes the SS assignment to the seventh STA addressed within the MU PPDU. This is formatted as described in Table 39. SS Descriptor Set 7 9 78 Describes the SS assignment to the STA addressed within the MU PPDU. This field is formatted as described in Table 39. EDMG TRN Length 8 87 See Table 36 RX per Each TX TRN-Unit 8 95 See Table 36 EDMG TRN-Unit P 2 103 See Table 36
The rSTA sends a new PMF protected LMR frame with a new SAC and new sequence generation information (measurements results included in the LMR are invalid only for the immediate VHTz case). The iSTA may come back to the channel and initiate a new sounding sequence minToaReady time Results Y: 18, N: 0, A: 0. Converted to a motion. Motion #3 Move to adopt the following SFD text, instruct the editor to include it in the 11az SFD, and grant editorial license to the editor: “For secure VHTz ranging measurement (LMR error recovery operation): –The LMR is an Action No ACK –If the LMR was not correctly received: The iSTA comes back to the channel and transmit an NDPA indicating “New LTF generation information is needed”. The previous LTF generation information is invalidated. For UL NDP the iSTA uses a known UL NDP LTF sequence (not suitable for measurement). For DL NDP the rSTA may use the secured DL NDP LTF sequence (not suitable for measurement). The rSTA sends a new PMF protected LMR frame with a new SAC and new sequence generation information (measurements results included in the LMR are invalid only for the immediate VHTz case). The iSTA may come back to the channel and initiate a new sounding sequence minToaReady time after.” Mover: Chitto Ghosh, Seconder: Yongho Seok Results: Y: 14, N: 0, A: 1; motion passes Strawpoll #4 • Do you support the following SFD texts for secure HEz ranging measurement (general operation)? –For normal operation of secure HEz ranging, –Secure HEz ranging measurement procedure is limited to a single ISTA (extension to multiple ISTA is TBD): –The delayed sequence generation where sequence generation information is carried in the previous sounding sequence instance. –The keys or cipher sequence (if needed) for LTF sequence generation are the result of the FTM negotiation. –LTF sequence generation information for the first measurement instance is a part of an IFTM, the measurement phase only commences once the negotiation is successful. –The frame used to deliver subsequent LTF sequence generation information is the protected LMR frame. Results: Y: 17, N: 0, A: 1. Converted to a Motion.
12044 Jarkko Kneckt 156.56 The SRG OBSS PD Min Offset can allow associated STAs to transmit with full transmission power even when they detect WLAN signal from an SRG BSS at -62 dBm energy. The spatial reuse is targetted to organise higher transmission density by lowering the transmission power when the sensitivity requirement is relaxed. An ill behaving AP can get benefit by misconfiguring SRG OBSS PD MIN value. In this case the non-AP STAs may transmit with full transmission power during the transmissions of the SRG OBSSs. The 802.11 should ensure fairness between STAs and not allow such behaviour. In worst case, this operation may be used against the WLAN, for instance It may be difficult to explain to the FCC and other regulators why WLAN allows such interfering transmissions and why it cannot control WLAN BSSs and STAs. Lack of control may prevent WLAN use in new spectrum and cause changes in the current regulation. Please delete all instances of the SRG OBSS PD Min Offset and its use in the spec. Please allow only to control the OBSS PD MaxOffset[CL1] . Revise – Tgax editor to make changes in 12304 Laurent Cariou 27.9.2 290.25 OBSS_PD based spatial reuse operation is defining specific rules and equations when applied to an SRG (SR group). In some managed environments, the definition and settlement of SRG can be done in a proprietary way within an ESS. In less managed environments, such SRG formation would require a specific protocol and specific frame exchanges. Define the protocol and frame exchanges needed to establish an SRG among neighboring APs. Revise – Tgax editor to make changes found in 11-18-0225r4
Proposed Changes to Draft Text of TGax D2.3: CID 12044, 12304 TGax editor: modify TGax D2.3 subclause 27.9.2.3 as follows: 27.9.2.3 General Operation with SRG OBSS_PD level Add the following new text at the end of Section 27.9.2.3 General Operation with SRG OBSS_PD level: An HE AP may define a Spatial Group (SRG) that applies to OBSS_PD Spatial Reuse operation by an associated STA in the AP’s BSS and indicate that SRG to the associated STA using the Spatial Reuse Parameter Set element by setting the SRG Information Present field to 1 and including the SRG OBSS PD Min Offset, SRG OBSS Max Offset, SRG BSS Color Bitmap and SRG Partial BSSID Bitmap fields. TGax editor: modify TGax D2.3 subclause 27.9.2.4 as follows: 27.9.2.4 Adjustment of OBSS_PD and transmit power TGax editor: Modify the following tables: Determining Non-SRG OBSS PD Min and Non-SRG OBSS PD Max values OBSS_PD SR Disallowed Non-SRG Offset Present of Non-SRG OBSS PD Min Value of Non-SRG OBSS PD Max Spatial Reuse Parameter Set element not received Spatial Parameter Set element not received 82 Non-AP STA: 62 AP: 82 + 0 0 82 62
IEEE P802.11 Wireless LANs Comment Resolution on OFDM DC relative shift Date: 2018-2-27 Author(s): Name Affiliation Address Phone email Hiroyuki Motozuka Panasonic 600 Saedo-cho, Yokohama, Kanagawa, Japan motozuka.hiroyuki@jp.panasonic.com Takenori Sakamoto sakamoto.takenori@jp.panasonic.com Yutaka Murakami murakami.ytk@jp.panasonic.com Lei lei.huang@sg.panasonic.com Gaius Wee yaohuang.wee@sg.panasonic.com Kazu Takahashi takahashi.kazu@jp.panasonic.com CID Clause Page Comment Proposed Change Proposed Resolution 2092 30.6.1.3 329.10 Unclear why DC needs to be shifted, please add a note to explain to the reader the reason for the shift Add text to explain why the DC needs be shifted relative to the carrier frequency Revised TGay editor to make the changes shown in 11-18/0275r0 under all headings that include CID 2092. 1520 30.6.1.3 329.11 Dc relative shift should be applied to the TRN field as well since the TRN field for the OFDM PPDU consists of OFDM symbols. "The DC relative frequency shift is applied in digital domain for EDMG-CEF, Data and TRN fields of an EDMG OFDM mode PPDU." Accepted TGay editor to make the changes shown in 11-18/0275r0 under all headings that include CID 1520. 1521 30.6.1.3 329.11 There's no text to mention or define the parameter F_DC, which appears in Table 72. Mention it in the text. e.g. "The DC relative shift, F_DC, is frequency channel dependent and defined in Table 72." Revised TGay editor to make the changes shown in 11-18/0275r0 under all headings that include CID 1521. 2138 30.6.1.3 330.07 FCC only approved up to 71 GHz, we should remove rows 7 and 8 from NCB=1 category from Table 72. Similar action As in comment Accepted TGay editor to make the changes shown in 11-18/0275r0 under all headings that include CID 2138.
DC relative shift to carrier frequency The DC relative frequency shift is applied in digital domain EDMG-STF, EDMG-CEF, Data field of an EDMG OFDM mode PPDU. The DC relative shift is frequency channel dependent and defined in Table 72. NOTE—In all cases, the relative shift between DC and frequency does not exceed half of the subcarrier spacing. —DC relative to carrier frequency Number of contiguous 2.16 GHz channels (NCB) Channel number , GHz , GHz (), MHz 1 1 58.32 64.8 - ∆F×3×419 -1.4063 2 60.48 64.8 - ∆F×2×419 -0.9375 3 62.64 64.8 - ∆F×419 -0.4688 4 64.8 64.8 0 5 66.96 64.8 + ∆F×419 0.4688 6 69.12 64.8 + ∆F×2×419 0.9375
7 71.28 64.8 + ∆F×3×419 1.4063 8 73.44 64.8 + ∆F×4×419 1.8750 2 9 59.4 64.8 – ∆F×1047 1.4062 10 61.56 64.8 – ∆F×628 1.8750 11 63.72 64.8 – ∆F×209 2.3438 12 65.88 64.8 + ∆F×209 -2.3437 13 68.04 64.8 + ∆F×628 -1.8750 14 70.2 64.8 + ∆F×1047 -1.4063 15 72.36 64.8 + ∆F×1466 -0.9375 3 17 60.48 64.8 – ∆F×2×419 -0.9375 18 62.64 64.8 – ∆F×419 -0.4688 19 64.8 64.8 0 20 66.96 64.8 + ∆F×419 0.4688 21 69.12 64.8 + ∆F×2×419 0.9375 22 71.28 64.8 + ∆F×3×419 1.4063 4 25 61.56 64.8 – ∆F×628 1.8750 26 63.72 64.8 – ∆F×209 2.3438 27 65.88 64.8 + ∆F×209 -2.3437 28 68.04 64.8 + ∆F×628 -1.8750 29 70.2 64.8 + ∆F×1047 -1.4063 EDMG preamble, Data and TRN fields transmission Editor: modify the 3rd paragraph of subclause 30.6.9.3.3 of D1.0 as follows: (P365L25-P366L2) (CID #1539) The EDMG OFDM mode SU PPDU waveform for the iTXth transmit chain concatenates the pre-EDMG, EDMG preamble, Data field and TRN field and shall be defined as follows: where:
1735 115.38 10.24.2 Inconsistent on MSDU/MPDU Modulo subfield lengths. Here it says MPDU <= 12 and (MPDU+MSDU) = 14. In P85L7 it says only (MPDU+MSDU) <= 14. Change P85L7 to match the rules at P115L38. Proposal: Revise TGay Editor: modify in P85L7 as follows The sum of the values of the MSDU Modulo subfield and the MPDU Modulo subfield fourteen. 1765 115.06 10.24.1 If the STA uses segmentation and reassembly, parameters for SAR need to be added to MLME-ADDBA primitives. Add parameters relating to SAR to MLME-ADDBA primitives in 6.3.29. Proposal: Revise Discussion: Solution is provided in reference to [2] IEEE Std 802.11-2016. In addition, EDMG Flow control parameters are added TGay Editor modify as follows In P362, in MLME-ADDBA.request(, In P363, in MLME-ADDBA.confirm( In P364, in In P365, in MLME-ADDBA.response( after ADDBA Extension, insert: EDMG Flow Control Extension Configuration SAR Configuration In P362, P364, P365, and P366 insert two lines in the tables after ADDBA Extension EDMG Flow Control Extension Configuration EDMG Flow Control Extension Configuration element As defined in 9.4.2.263 Specifies EDMG Flow Control parameters SAR Configuration SAR Configuration element As defined in 9.4.2.266 Specifies segmentation parameters in relation to SAR 1767 Kazuyuki Sakoda 119.23 10.24.6 If the STA uses Multi-TID BA, parameters for Multi-TID need to be added to primitives. Add parameters relating to Multi-TID to MLME-ADDBA primitives in 6.3.29. Proposal: Reject Discussion: There are no Multi-TID specific parameters to be added ADDBA
2208 120.07 10.24.7.1 What is the point of the sentence: "That is, a block ack agreement with segmentation and reassembly is an block ack agreement." It doesn't seem to provide any useful information as this whole section is related to block ack. delete: "That is, a block ack agreement with segmentation and reassembly is an block ack agreement." Proposal: Accept 2209 121.19 10.24.7.3 I think it would be cleaner and less confusing if the various cases were separated. Hence, I think 10.24.7.3 would become Scoreboard context control during full-state operation without segmentation and reassembly. And 10.24.7.4 would also state it is without segmentation and reassembly. A new sections 10.24.73a and 10.24.7.4a could be added for the case with segmentation and reassembly. Remove the changes to 10.24.7.3 and 10.24.7.4 and move them to new clauses 10.24.7.3a and 10.24.7.4a which define the operation when segmentation and reassembly are present. 2210 121.39 10.24.7.4 I think it would be cleaner and less confusing if the various cases were separated. Hence I think 10.24.7.3 would become Scoreboard context control during full-state operation without segmentation and reassembly. And 10.24.7.4 would also state it is without segmentation and reassembly. A new sections 10.24.73a and 10.24.7.4a could be added for the case with segmentation and reassembly. Remove the changes to 10.24.7.3 and 10.24.7.4 and move them to new clauses 10.24.7.3a and 10.24.7.4a which define the operation when segmentation and reassembly are present. Proposal: Reject
IEEE P802.11 Wireless LANs Comment resolution Date: 2018-01-24 Author(s): Name Affiliation Address Phone email Solomon Trainin Qualcomm strainin@qti.qualcomm.com CID Page Clause Comment Proposed Change 1101 130.04 10.24.12.5 The buffered MSDUs in the receive reordering buffer control can be flushed when the STA stops receiving from the <TA, TID> pair the statement "Stop receiving" need to be better defined Flushing the buffer can be done when the Duration time indicated in the last received MPDU has elapsed Proposal: Revise Discussion: The proposed change is not adequate in relation to the intention of the feature as it is presented “…ability of the recipient to flush the buffers when it starts receiving from a different originator or TID.” that the transmission with no need to flush the buffer may be longer than single TXOP or SP. Proposed change resolves the commented issue and aligns the normative text with the text at start of the sub clause. TGay Editor: Modify the text in P130L4 as follows: The buffered in the receive reordering buffer control can be flushed when the STA receiving from different <TA, TID> pair. 1645 115.35 10.24.2 SAR is an optional feature as indicated by this paragraph, so it is necessary for the upper layer to do the segmentation if SAR is not supported. Should SAR be a mandatory one to truly reflect the design purpose? Please clarify Proposal: Reject Discussion:
2208 120.07 10.24.7.1 What is the point of the sentence: "That is, a block ack agreement with segmentation and reassembly is an block ack agreement." It doesn't seem to provide any useful information as this whole section is related to block ack. delete: "That is, a block ack agreement with segmentation and reassembly is an block ack agreement." Proposal: Accept 2209 121.19 10.24.7.3 I it would be cleaner and less confusing if the various cases were separated. Hence, I think 10.24.7.3 would become Scoreboard context control during full-state operation without segmentation and reassembly. And 10.24.7.4 would also state it is without segmentation and reassembly. A new sections 10.24.73a and 10.24.7.4a could be added for the case with segmentation and reassembly. Remove the changes to 10.24.7.3 and 10.24.7.4 and move them to new clauses 10.24.7.3a and 10.24.7.4a which define the operation when segmentation and reassembly are present. 2210 121.39 10.24.7.4 I think it would be cleaner and less confusing if the various cases were separated. Hence I think 10.24.7.3 would become Scoreboard context control during full-state operation without segmentation and reassembly. And 10.24.7.4 would also state it is without segmentation and reassembly. A new sections 10.24.73a and 10.24.7.4a could be added for the case with segmentation and reassembly. Remove the changes to 10.24.7.3 and 10.24.7.4 and move them to new clauses 10.24.7.3a and 10.24.7.4a which define the operation when segmentation and reassembly are present. Proposal: Reject
feedback procedure, it should be the same procedure as described in 10.38.6.4.1 requesting TXSS sector list. However, there are some minor differences between here and what was described in 10.38.6.4.1. For example, the requirement of setting Sector ID Order Requested to 1 is not in 10.38.6.4.1, the IFS between 2 BRP packets is SIFS in this cause but in 10.38.6.4.1 it is within MBIFS. Minimum 16 sector feedback are required in 10.38.6.4.1 but there is no such requirement in this clause same comment applies to 10.38.9.2.3.2 refer to 10.38.6.4.1 for consistency with the additional requirement that the 1st BRP frame should contain the feeback to the responder in addition to the agreed that MBIFS shall be used between two BRP frames instead of SIFS for the SISO feedback procedure. Also agreed that minimum feedback requirement for both SISO and MIMO BF should keep consistency. For this purpose, it is proposed that feedback of minimum 16 sectors per TX/RX antenna pair is required for MIMO BF. TGay editor to make the changes shown in 11-18/0281r0 under all headings that include CID 2306. 1133 165 Figure 98 is not very informative and can be removed or modified to include more details on the SISO procedure, in addition its title need to be fixed The SISO feedback procedure of the beamforming Figure 98 --The SISO feedback procedure of the beamforming Revised- Agreed in principle that Figure 98 is not very informative and should be removed. TGay editor to make the changes shown in 11-18/0281r0 under all headings that include CID 1133. 1143 165 4 "are" shall be removed from "The BRP shall have all the subfields within the FBCK-REQ field are set to 0" as per comment Accepted- TGay editor to make the changes shown in 11-18/0281r0 under all headings that include CID 1143. 1144 165 22 "per TX antenna" should be "per TX DMG antenna" as per comment Accepted- TGay editor to make the changes shown in 11-18/0281r0 under all headings that include CID 1144.
IEEE P802.11 Wireless LANs Comment Resolution on MIMO BF Misc Date: 2018-2-12 Author(s): Name Affiliation Address Phone Email Lei Huang Panasonic lei.huang@sg.panasonic.com CID Page Number Line Number Comment Proposed Change Resolution 1145 75 1 The MIMO Setup Control element transmitted by initiator comprises setup info for initiator link and responder link. Therefore, the Link Type field does not make sense. "Link Type" field shall be replaced by "Initiator" field, which indicates whether the sender is the initiator. Accepted- TGay editor to make the changes in under all headings that include CID 1145. 1498 75 1 The SU/MU field of the MIMO Setup Control element is set to 1 in case of SU, while the SU/MU format field in the field is set to 0 in that case. The MAC and PHY have different rules, and it is confusing and inconvinient. Use the same rule as PHY: 0/1 for SU/MU, instead of 1/0. Additionally, the field name can be changed to "MU mode" for example. Revised- Agreed to use the same rule for SU/MU field as PHY. But it is unnecessary to rename the SU/MU field to the MU mode field. Similar change should be made on the SU/MU field in the MIMO Poll Control element and the MIMO Feedback Control element. TGay editor to make the changes shown in 11-18/0299r0 under all headings that include CID 1498. 1752 75 14 "Aggregation Requested field" should be defined to be "Channel Aggregation Requested field" to make this field name more intuitive. Replace "Aggregation Requested with "Channel Aggregation Requested field", and change all references to the field accordingly. Accepted- Similar change should also be made on the Aggregation Present subfield of the MIMO FBCK-TYPE field in the MIMO Feedback Control element. TGay editor to make the changes shown in 11-18/0299r0 under all
Table 9—MIMO Setup Control element format Field Size (bits) Meaning Element ID 8 Length 8 Element ID Extension 8 SU/MU 1 to to indicate SU-MIMO beamforming and set to to indicate beamforming. MIMO Phase 1 to to indicate the MIMO phase and set to to indicate the reciprocal MIMO phase. EDMG Group ID 8 Indicates the EDMG Group ID of target MU group. This field is reserved when the SU/MU field is set to . Group User Mask 32 L-TX-RX 8 Indicates the requested number of consecutive TRN-Units in which the same AWV is used in the transmission of the last M TRN subfields of each This field is reserved when the SU/MU field is set to .
Table 12—MIMO Selection Control element format Field Size (bits) Meaning ID 8 8 ID 8 ID 8 Indicates the EDMG group ID of target MU group. of 3 Indicates the number of MU-MIMO transmission configurations, Nconf. Type 1 et to to indicate the MU-MIMO transmission configurations obtained from the BF training; and to to indicate the transmission configurations obtained from MU-MIMO BF training. … 10.38.9.2.2.3 MIMO 10.38.9.2.2.3.2 Non-reciprocal MIMO phase Replace Figure 99 by the following figure (CID 1244): Figure 99—The non-reciprocal MIMO phase of the SU-MIMO beamforming