zilongwang/ReadingBank huggingface dataset:
IEEE P802.11 Wireless LANs A-BFT Date: 2016-12-22 Author(s): Name Affiliation Address Phone email Yan Xin Huawei Technologies Co., Ltd. Suite 400, 303 Terry Fox Drive, Kanata, ON Canada K2K 3J1 +1-613-979-1792 yan.xin@huawei.com Sang G. Kim LG Electronics 10225 Willow Creek Rd, San Diego CA 92131 +1-858-635-5294 sanggook.kim@lge.com Carlos Cordeiro Intel +1-503-712-9356 carlos.cordeiro@intel.com Kerstin Johnsson Intel kerstin.johnsson@intel.com Xiao (Tony) Han Huawei Technologies Co., Ltd. tony.hanxiao@huawei.com A-BFT 3.2.1.1 A-BFT over multiple channels in TGay Modification to “802.11-2016” 10.38.5 Beamforming in A-BFT 10.38.5.1 Allocation of A-BFT Insert the following paragraph after the third paragraph of 10.38.5.1 An EDMG PCP or AP may schedule an A-BFT that spans more than one channel. An EDMG STA that supports this type of A-BFT may access the A-BFT over the different channels where the A-BFT is scheduled. 10.38.5.2 Operation during the A-BFT Insert the following subclause 10.38.5.2a (including Figure 10-69 and Figure 10-70) after the last paragraph of 10.38.5.2 10.38.5.2a A-BFT over multiple channels
The number of additional SSW slots in a beacon interval shall be equal to the value of the A-BFT Length subfield multiplied by the value of the A-BFT Multiplier subfield, where both of these subfields are present in the DMG Beacon frame, and the A-BFT Multiplier subfield is indicated using reserved bits from the Beacon Interval Control field of the DMG Beacon frame. Figure 10-71 depicts how non-EDMG STAs interpret the insertion of the added SSW slots in the beacon interval. Figure 10-71: Additional SSW slots for use by EDMG STAs in relation to the legacy A-BFT When Next A-BFT is equal to 0 and A-BFT Multiplier is greater than 0, the value of the Duration field within all DMG Beacons shall be increased by A-BFT Length multiplied by A-BFT Multiplier plus the length of an MBIFS to accommodate the additional SSW slots. This guarantees that non-EDMG STAs calculate the correct start time for the legacy A-BFT.
of Short Scrambled BSSID field The process starts by using the BSSID to generate the scrambled BSSID. The BSSID is divided into three words, wordi (0 ≤ i ≤ 2), of 16 bits each, where word0 is the 16 MSB of the BSSID and word2 is the 16 LSB of the BSSID. For each wordi, a scrambled_wordi is created as follows: where: wordi is the corresponding 16 bit word from the BSSID. scramble_pattern is ((0x5795×seed_value) mod 215), where seed_value is the value of the Scrambler Initialization field in the L-Header of the PPDU carrying the Short SSW packet. The scrambled BSSID is generated by the consecutive concatenation of scrambled_word0, scrambled_word1 and scrambled_word2. Finally, the Short Scrambled BSSID field is generated by taking the 10 MSBs of CRC-16-CCITT computed over the scrambled BSSID. References: 11-15-1358-09-00ay-11ay Spec Framework
[12] T. Borogovac et al., “Lights-off Visible Light Communications”, IEEE Global Communications Conference (GLOBECOM) 2015, 5 – 9 December 2011. [13] Philips Lighting - [14] M. Sufyian and H. Haas, “Modulation Techniques for Li-Fi”, ZTE Communications, April 2016, vol. 14 No. 2. Available at:
6144 Jing Ma 174.24 Clarify more details NDP feedback report procedure such as which kind of trigger frame and how to solicit NDP feedback report. as the comment Revised = agree in principle with the comment. Modify the spec with the proposed changes in this document. 7386 Laurent Cariou 174.24 NDP feedback report procedure must be detailed Provide a description of NDP feedback report procedure for the AP side and the STA side Revised = agree in principle with the comment. Modify the spec with the proposed changes in this document. 7387 Laurent Cariou 174.24 NDP feedback report are sent in response to a trigger frame. The specification must define a new trigger type soliciting NDP feedback report from multiple STAs. Define a new trigger type soliciting NDP feedback report Revised = agree in principle with the comment. Modify the spec with the proposed changes in this document. 8304 Patrice Nezou 174.24 "The NDP feedback report is a mechanism for an HE AP to collect short feedbacks from a very high number of HE STAs, in an efficient manner. The feedbacks (e.g. resource requests) are sent without data payloads in response to a Trigger frame. The feedbacks are not for channel sounding. This mechanism is Precise the NDP feedback procedure Revised = agree in principle with the comment. Modify the spec with the proposed changes in this document.
CID Clause Page Line Type Comment Proposed Change 606 9.2.4.6a 27 44 T Your table 9-18e RDG/More PPDU is identical (with one minor difference) to an existing baseline table 9-11 RDG/More PPDU - wow! You cannot copy something completely and then have two references to the same name! simply change the reference in the text paragraph from table 9-18e to table 9-11 and remove your table 9-18e, i.e. you should simply refer to the existing field with the same name, since the definitions are identical, unless the thing about Duration is needed, but I doubt it Proposed resolution: Revised Remove the copied definition in 11aj and refer to the existing subfield in IEEE 802.11 spec as follows: “The RDG/More PPDU subfield of the CMMG Control field is defined in Table 9-11. The RDG/More PPDU subfield of the CMMG Control field is interpreted differently depending on whether it is transmitted by an RD initiator or an RD responder, as defined in Table9-18e (RDG/More PPDU subfield values) ” CID Clause Page Line Type Comment Proposed Change 607 33 42 T Again, I think that you should be pointing to the existing subfields in the baseline that have the same definitions and names. As stated in the comment. Someone should make an official enquery to the 802.11 editor in chief as to whether it is ok to reuse names like this. Proposed resolution: Rejected TGaj consulted WG editor on this issue. The result is as follows: “Where a field has an individual entry in 9.4.1, there would not create something with the same name and a different definition.
Discussion: The comment is pointing out that the TOMI should allocate the channels starting form the primary channel. It is true that the allocated channel should be in primary channel. The comment is similar to CID6017. Proposed Resolution: Revised. The Primary is to the Channel Width field definition to ensure that transmission is within the primary channel of the STA. Please adopt the changes shown in the normative text of the submission 11-17-0115-07-00ax-comment-resolutions-27_8
Management and Extension frame body components Fields that are not elements Action TGax Editor: Please add a new row to table 9-47 as follows: Change Table 9-47 as follows (insert new row and updated reserved row): Category values Code Meaning See subclause Robust Group addressed privacy ... <ANA> HE 9.6.28 (HE Action frame details) No No <ANA> Quiet Time Period 9.6.23a (Quiet Time Period Action frame details) No No 21<ANA>–125 Reserved — — — ... HE Action frame details HE Action field TGax Editor: Please modify table 9-421z (pg 106, line 13 in D1.1) as follows: Action field values Meaning 0 HE Compressed Beamforming And CQI 1 HE BSS Color Change Announcement 2-255 Reserved TGax Editor: Please add a new section as follows:
guide –Edward Au MIB style and compiles with no extra warnings–Yongho Seok ANA check –Robert Stacey Actions arising Correct for findings. Donald to review, effect draft change where necessary and markup this document with changes made. There are assigned numbers required and one instance where an allocated number needs renaming in the ANA database. Donald to submit ANA allocation and rename request. There are some changes required to the MIB to get it to compile. Donald to effect draft change. Findings Findings from Edward Au: 2.1 Frames 2.1.1 Frame Format Figures (10) Figure 9-53. The drawing of the Data frame does not follow the bit-aligned figure format as shown in Figure 9-53a. The font type and font size of the figure do not follow the bit-aligned figure format as shown in 11-09/1034r11. Figure 9-53b. The font type and font size of the figure do not follow the bit-aligned figure format as shown in 11-09/1034r11. Figure 9-68. The drawing of the figure does not follow the bit-aligned figure format as shown in Figure 9-69. The drawing of the figure does not follow the bit-aligned figure format as shown in Figure 9-504. The font type of the figure do not follow the bit-aligned figure format as shown in Figure 9-589co. The font type and font size of the figure do not follow the bit-aligned figure format as shown in 11-09/1034r11. Figure 9-589cp. The font type and font size of the figure do not follow the bit-aligned figure format as shown in 11-09/1034r11. Figure 9-589cq. The font type and font size of the figure do not follow the bit-aligned figure format as shown in 11-09/1034r11. Figure The font type and font size of the figure do not follow the bit-aligned figure format as shown in 11-09/1034r11. 2.1.1.1 Optional Fields (0) No findings.
EPC – Evolved Core IEEE – of and Electronic Engineers IMT-2020 – International Mobile Telecommunications System for 2020 and beyond LAN – local area network LWA – LTE WLAN Aggregation LWIP – LTE WLAN Radio Level with IPsec Tunnel LTE – Long-Term Evolution MAN – metropolitan area network NBIFOM – Network based IP Flow Mobility NR – New Radio QoS – Quality of Service RAN – Access Network RAT – Radio Access Technology SA – Service and WG – Working Group WI – Work Item WLAN – wireless local area network
4745 Alfred Asterjadhi 114.13 What is the expectation when the AP wants to not use MU EDCA Parameters anymore? Does it decide to not include the MU EDCA Parameter Set in the Beacon, or does it continue including it and always specify the same values in the MU and normal EDCA Parameter Set elements? Clarify (noting that the second option requires to keep 16 redundant octets in the Beacon). As in comment Revised – agree with the comment. Clarification is added that if the MU EDCA parameter element was not received, the procedure does not apply, as described in the proposed changes in doc . Include the following in section 3.4 Abbreviations and acronyms Modify 9.4.2.221 MU EDCA parameter set element as follows: MU EDCA Parameter Set element The format of the MU EDCA Parameter Set element is defined in Figure 9-589cv (MU EDCA Parameter Set element). Element ID Length Element ID Extension MU QoS Info MU AC_BE Parameter Record MU AC_BK Parameter Record MU AC_VI Parameter Record MU Parameter Record Octets: 1 1 1 1 3 3 3 3 MU EDCA Parameter Set element The Element ID, Length, and Element ID Extension fields are defined in 9.4.2.1 (General). For an infrastructure BSS, the MU EDCA Parameter Set element is used by the AP to The most recent MU EDCA Parameter Set element received by a STA is used to update the appropriate MIB values. The format of the MU QoS Info field is the same as the field defined in 9.4.1.17 (QoS Info field). The MU QoS Info field contains the EDCA Parameter Set Update Count subfield, which is initially set to 0 and is incremented each time any of
¾ 672 1344 504 1008 13/16 672 1344 546 1092 7/8 672 1344 588 1176 29.5.7.27.5 Parity check matrices See 29.3.7. 29.5.7.27.6 LDPC encoding for SISO transmission This subcluse defines a SC PHY PSDU encoding process for SISO transmission. The EDMG encoding process includes the following steps. employ steps a) – c) as defined in subclause 20.6.3.2.3.3 for DMG encoding, assuming that LCW can be equal to 672 or 1344 bits and R = 7/8 code shall use the b.1) encoding procedure. The number of SC symbol blocks, NBLKS, and the number of symbol block padding bits, NBLK_PAD, are calculated as follows: where: NCBPB is the number of coded bits per block transmitted over the 2.16 GHz channel NCB defines the number of 2.16 GHz channels, NCB (1 ≤ NCB ≤ 4), that make up the signal bandwidth of the EDMG PPDU The values of NCBPB for different types of GI are provided in. The coded bit stream is concatenated with NBLK_PAD zeros. They are scrambled using the continuation of the scrambler sequence that scrambled the PSDU input bits. of NCBPB for different types of GI Symbol mapping Short GI Normal GI Long GI π/2-BPSK 480 448 384 π/2-QPSK 960 896 768 π/2-16QAM 1920 1792 1536 π/2-64QAM 2880 2688 2304 29.5.7.27.7 LDPC encoding for MIMO transmission
8406 Can be used in A-MPDU carried in PPDU such as VHT PPDU, HT PPDU, and non-HT PPDU? From the sentence, it may be implied that the restriction exists. Directly specify if multi-TID can be carried in PPDU. From commenter's point of view, the answer is yes as long as the recipient supports A-MPDU. Rejected- Currently, the multi-TID A-MPDU can’t be transmitted in an HT PPDU or a VHT PPDU. I think that there is no technical problem when the multi-TID A-MPDU is transmitted in an HT PPDU or a VHT PPDU. But, such flexibility can makes additional implementation complexity. 6484 Instead of "(all) HE trigger-based PPDUs addressed to the same AP", it would be more precise to write "HE trigger-based PPDUs transmitted simultaneously to the same AP", or in response to the same HE trigger frame, or something. HE trigger-based PPDUs transmitted at different times do not have to carry the same value, even if they are addressed to the same AP. Change "all HE trigger-based PPDUs addressed to the same AP" to "HE PPDUs transmitted simultaneously to the same AP". Revised- Agree in principal. Change to “the same HE trigger-based PPDU” TGax editor changes as shown in the as specified in 11-17/0226r. 9611 The TXVECTOR parameter TXOP_DURATION of an HE PPDU is based on the Duration/ID field in the MAC header. If the Duration/ID fields of one or more HE PPDUs addressed to same AP are not identical, the TXVECTOR parameter TXOP_DURATIONs of those HE trigger-based PPDUs can be different. In such case, 3rd party HE STA can't obtain the TXOP_DURATION value from the HE-SIG-A of the received HE trigger-based PPDU. Please clearly specify how the Duration/ID field in the MAC header of an As per comment. Revised- Agree in principal. It is necessary to cleary specify how the Duration/ID field in the MAC header of an HE trigger-based PPDU is calculated. TGax editor changes as shown in the as specified in 11-17/0226r.
of an HE variant HT Control field carried in a QoS Data, QoS Null, or Management frame. field. Set to 0 otherwise. TWT Requester Support Indicates support by an HE STA for the role of TWT requesting STA as described in (TWT). Set to 1 if dot11TWTOptionActivated is true and the STA supports TWT requester STA functionality (see (TWT)). Set to 0 otherwise. TWT Responder Support Indicates support by an HE STA for the role of TWT responder STA as described in (TWT). Set to 1 if dot11TWTOptionActivated is true and the STA supports TWT responder STA functionality (see (TWT)). Set to 0 otherwise. … Broadcast TWT Support Indicates support by an HE non-AP STA for the role of TWT scheduled STA and by an AP for the role of TWT scheduling STA as described in 27.7.3 (Broadcast TWT operation). Set to 1 when the STA supports broadcast TWT functionality. Set to 0 otherwise. …
B19 indicates support for the reception of HE PPDUs having bandwidth less than or equal to 80 MHz and (#8381) using STBC with one spatial stream. TGax Editor: Please add the following to the end of the Table9-262aa in section 9.4.2.218.3 (CIDs: 8381) STBC Tx And Rx For 80 MHz (#8381) B62 indicates support for the transmission of HE PPDUs having bandwidth greater than 80 MHz and (#8381) using STBC with one spatial stream. B63 indicates support for the reception of HE PPDUs having bandwidth greater than 80 MHz and (#8381) using STBC with one spatial stream. B62 set to 1 if supported by the STA. Set to 0 otherwise. B63 set to 1 if supported by the the STA. Set to 0 otherwise. References: IEEE P802.11axTM/D1.0, Nov 2016.
3196 190.22 27.9.1 In "... not update its NAV timers based on frames carried in the PPDU ...", for consistency, it should be stated that the STA may not update its NAV based on TXOP field in the HE SIG-A if present As in the comment Rejected – may not update its NAV is valid for all possible NAV updates, be there with TxOP field in HE-SIG-A or with MAC frame. 6025 190.36 27.9.2.1 The spatial reuse rules are not easy-to-understand. Is the reuse allowed only for the PPDU duration when HE MU PPDU is transmitted and in all other cases the channel may be considered as IDLE and there is no limitation of the duration when the spatial reuse may be performed? Please clarify. Revised – clarify the rules for the transmission of the SR PPDU by defining an OBSS_PD SR opportunity, as in the proposed changes in doc xxxrx. 7823 190.24 27.9.2.1 Inconsistency in NAV operation. At P150L36, P151L1 and P151L28, a frame (matching the other criteria) that is "cannot be identified as intra-BSS or inter-BSS" will update the basic NAV. But at P190L24, does not include the "cannot be determined" case. Add "or cannot be identified as or inter-BSS" to the first bullet. Rejected – the SR operation only applies to PPDUs that can be identified as inter-BSS. If they can not be classified, then the SR conditions are not met and SR is not possible. 8233 190.24 27.9.1 The starting on line 24 are not clear. Does it mean that both of the NAV timers are not going to be updated if the PPDU is an inter-BSS PPDU? It seems there is a contradiction with the rules for updating the two NAV timers Clarify Rejected – The rules in SR are orthogonal to the NAV timers. SR simply allows to not update the NAV if specific conditions are met. If those conditions are not met, the NAV rules apply. BSS
based Starting spatial stream should be -1. 3165 9.3.1.23 47.07 is no descripton of the subfields within SS Allocation. Add the description and encoding of the two subfields within SS Allocation subfiield. Revised- in principle 7487 9.3.1.23 47.15 There is no description about the Starting Spatial Stream subfield and the Number of Spatial Streams subfield in the SS Alocation subfield Add the following description after Figure "The Starting Spatial Stream subfield indicates the stream index of the first spatial stream of the HE PPDU response of the STA identified by the AID12 subfield. The Number of Spatial Streams subfield indicates the number of spatial streams of the HE trigger-based PPDU response of the STA identified by the AID12 subfield Revised- Agree in principle 8660 9.3.1.23 47.15 Is it allowed to choose "Starting Spatial Stream" such that there are gaps in the total number of streams. E.g: Starting Spatial Stream=0, N_SS=1 and Starting Spatial Stream=2, N_SS=1. Specify that there should be no gaps in the numbering of all the streams in an UL transmission. Revised- Agree in principle 8661 9.3.1.23 47.15 Should "Starting Spatial Stream" value always be 0 for RU's that use "pure" OFDMA? Clarify Revised- Agree in principle 9262 9.3.1.23 47.07 Encoding of the Starting Spatial Stream subfield should be specified. Add the following sentence and table after Figure 9-52f: The encoding of the Starting Spatial Stream subfield is defined in Table 9-xx (Starting Spatial Stream subfield encoding). Table 9-xx - Starting Spatial Stream subfield encoding Value | Description 0 | 1st spatial stream 1 | 2nd spatial stream 2 | 3rd spatial stream 3 | 4th spatial stream 4 | 5th spatial stream 5 | 6th spatial stream 6 | 7th spatial stream 7 | 8th spatial stream Revised- Agree in principle 9263 9.3.1.23 47.07 Encoding of the Number Of Spatial Streams subfield should be specified. Add the following sentence and table after Figure 9-52f: The encoding of the Number Of Spatial Streams subfield is defined in Table 9-xy (Number Of Spatial Streams subfield encoding). Table 9-xy - Number Of Revised- Agree in principle
IEEE P802.11 Wireless LANs TGax Teleconference Minutes from August to September, 2016 Date: 2016-09-05 Author(s): Name Affiliation Address Phone email Yasuhiko Inoue NTT 1-1 Hikaro-no-oka, Yokosuka, Kanagawa 238-0847 Japan Teleconference on Thursday, August 4th, 2016, 20:00 – 22:00 (ET) Meeting called to by Osama Aboul-Magd (Huawei Technologies) @ 20:03 (ET). Agenda Setting Proposed Agenda Call the meeting to order IEEE 802 and 802.11 IPR Policy and Procedure Annoucement Attendance (Please send an e.mail to Yasuhiko Inoue (inoue.yasuhiko@lab.ntt.co.jp) and/or Osama Aboul-Magd (osama.aboulmagd@huawei.com)) Presentation , “EDCA rules – follow up 1,” Jing Ma (NICT) , “EDCA rules – follow up 2,” Jing Ma (NICT) , “Considerations on MAC-PHY interactions during SR operations,” Jing Ma (NICT) , “AP access procedure for UL MU operation ,” Jinsoo Ahn (Yonsei Univ.) , “11ax D0.1 Comment Resolution for NAV Setting of Single and Multiple Protection and Control Response,” Po-Kai Huang (Intel) AOB Adjourn Approval of the agenda Chair asked if there is any discussion on the agenda. 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. Relevant documents IEEE Patent Policy - Patent FAQ - LoA Form - Affiliation FAQ - Anti-Trust FAQ - Ethics - IEEE 802.11 Working Group Operartions Manual - Chair asked if there is any potentially essential patent that people are aware of. No potentially essential patent reported. Announcement Chair asked the attendees to state name and affiliation when speaking for the first tme.
5 David Bagby Calypso Ventures 6 Stephane Canon 7 Rojan Chitrakar Panasonic 8 Jinsoo Choi LG Electronics 9 Amal Ekbal NI 10 Reza Hedayat Newracom 11 Hanseul Hong Yonsei Univ. 12 Po-Kai Huang Intel 13 Yasu Inoue NTT 14 Junichi Iwatani NTT 15 Geonjung Ko WILUS Institute 16 Daewon Lee Newracom 17 Jae Seung Lee ETRI 18 Sungeun Lee Cypres 19 Jing Ma NICT 20 Narendar Madhavan Toshiba 21 Eunsung Park LG Electronics 22 Al Petrick J & P Associates 23 Kiseon Ryu LG Electronics 24 Sigurd Schelstraete Quantenna Communications 25 Shoko Shinohara NTT 26 John Son WILUS Institute 27 L. Sun IDCC 28 Xiaofei Wang InterDigital
CID P.L Comment Proposed Change Resolution 5272 What does "default mode" mean? This implies other types of modes, but I don't see other types of modes described. Please clarify. as in comment Revised Agreed in principle. The default mode is not necessary here separately because the SIGB Compression field in HE-SIG-A field of an HE MU PPDU can be used to indicate this mode. The following text "In the default mode when the SIGB Compression field in the HE-SIG-A field of an HE MU PPDU is set to 0, for a 20 MHz and a 40 MHz PPDU, each HE-SIG-B content channel ..." changes to "When the SIGB Compression field in the HE-SIG-A field of an HE MU PPDU is set to 0 for a 20 MHz and a 40 MHz PPDU, each HE-SIG-B content channel ..." TGax Editor: make changes according to this document 11-17-0288-02-00ax CRs on HE-SIG-B 28.3.10.8.4-5. 8958 Change "assignment to the user" to "assignment to each user" See comment Revised TGax Editor: make changes according to this document 11-17-0288-02-00ax CRs on HE-SIG-B 28.3.10.8.4-5. 8959 Change "assignment to the user" to "assignment to each user" See comment Revised TGax Editor: make changes according to this document 11-17-0288-02-00ax CRs on HE-SIG-B 28.3.10.8.4-5. 8960 Change "Use Specific" to "User Specific" See comment Revised TGax Editor: make changes according to this document 11-17-0288-02-00ax CRs on HE-SIG-B 28.3.10.8.4-5. Discussion The modifications improve the wording and correct typos. Changes to Section 28.3.10.8.4 To TGax editor: P293L33 replace the current text with the proposed changes ------------- Begin Text Changes ---------------
5 David Bagby Calypso Ventures 6 Stephane Baron Canon 7 Rojan Chitrakar Panasonic 8 Jinsoo Choi LG Electronics 9 Amal NI 10 Reza Hedayat Newracom 11 Hanseul Hong Yonsei Univ. 12 Po-Kai Huang Intel 13 Yasu Inoue NTT 14 Junichi Iwatani NTT 15 Geonjung Ko Institute 16 Daewon Lee Newracom 17 Jae Seung Lee ETRI 18 Sungeun Lee Cypres 19 Jing Ma NICT 20 Narendar Madhavan Toshiba 21 Eunsung Park LG Electronics 22 Al Petrick J & P Associates 23 Kiseon Ryu LG Electronics 24 Sigurd Schelstraete Quantenna Communications 25 Shinohara NTT 26 John Son WILUS Institute 27 L. Sun IDCC 28 Xiaofei Wang InterDigital Teleconference on Thursday, September 8th, 2016, 10:00 – 12:00 (ET) The teleconference on September 8th was cancelled due to low attendance.
our own modulation should be specified. Receiver selectivity with AWGN should be specified. sensitivity. Specify with AWGN interfering signal of bandwidth W MHz. guard bandwith comparing to HT and VHT signal of the same bandwith thus more chanllenging for testing. 8330 347 6 As the frequency bands are shared, receiver performance where the interfering signal is not our own modulation should be specified. Receiver selectivity with AWGN should be specified. The interfering signal should not be the same signal as is used in 28.3.17.2 receiver sensitivity. Specify with AWGN interfering signal of bandwidth W MHz. Rejected Duplicated CID as 8329. 9032 345 64 Unknown reference: xx-a Replace with correct reference Revised. Agree with comment. TGax editor: please make the changes in 11-17/0317r1 for CID 9032. 7833 346 63 Use proper normative verbs Change sentence to, "If the regulatory domain permits a 160 MHz band plan, then the STA shall be measured for adjacent channel rejection for 160 MHz operation, otherwise such measurement is optional." Similarly for nonadjacent channel, at P347L47. Rejected The same text is used for the VHT receiver specification. Keep the same text for consistency 9033 346 2 "of the frequency segment lower in the frequency of the desired signal." is not clear. Replace with "of the frequency segment of the desired signal that is lowest in frequency" See comment Rejected The text is clear. The same text is also to describe the VHT adjacent channel rejection testing procedure. 8330 347 6 As the frequency bands are shared, receiver performance where the interfering signal is not our own modulation should be specified. Receiver selectivity with AWGN should be specified. The interfering signal should not be the same signal as is used in 28.3.17.2 receiver sensitivity. Specify with AWGN interfering signal of bandwidth W MHz. Rejected HE signal is chosen as the interference signal for testing HE signal has less guard bandwith comparing to HT and VHT signal of the same bandwith thus more chanllenging for testing. To TGax editor: Please make the following changes to 28.3.17.3 (#CID 9032)
IEEE P802.11 Wireless LANs 11ax D1.0 MAC Comment Resolution for 10.3.2.4 and 27.2.2 Part I Date: 2017-03-06 Author(s): Name Affiliation Address Phone email Po-Kai Huang Intel Corporation 2200 Mission College Blvd, Santa Clara, CA 950542200 po-kai.huang@intel.com 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 D1.0 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D1.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 Commenter P.L Clause Comment Proposed Change Resolution Yusuke Tanaka 152.56 27.2.2 Two NAVs is defined in this spec but the current RA field of CF-END is broadcast and an HE STA can not decide which NAV should be reset when it receives CF-END. Define a new CF-END frame whose RA is the address of the intended STA. Rejected – Currently, the TA field of the CF-End is always set to the BSSID. As a result, the STA can always classify the frame as Intra-BSS or based on the BSSID. Hence, there is no need to define a new CF-End Frame. Zhou Lan 150.25 27.2.2 "An HE non-AP STA shall maintain two NAV timers. An HE AP STA may maintain two NAV timers." clarify the different requirement between AP and Non-AP STA per comment Rejected – One of the main motivation for maintiatning two NAV timers is for the non-AP STA to be able to ignore the NAV and considers the basic NAV in response to Trigger frame. Since AP STA will never receive a Trigger frame. Maintaining two NAV timers is then optional for AP STA. BSS 0
3028 Abhishek Patil 67.57 Either TIM frame or FILS Discovery frame will included at the beginning of a broadcast TWT - replace and with or replace 'and' with 'or' Revised – agree in principle with the comment. 3029 Abhishek Patil 68.02 The operation applies to current TWT SP - the sentence doesn't need to discuss about what happens outside the current TWT SP Remove: "and before the next TWT SP" and make reference to "current" TWT SP. Change sentence as following: "Bit number N in the traffic indication virtual bitmap is 0 if the AP does not intend to transmit to the STA or to trigger the STA for an UL MU transmission during the current TWT SP." 4452 Albert Petrick 68.60 Period missing at end of sentence Add period at the of sentence after "reserved" 4460 Albert Petrick 68.62 Period missing at end of sentence Add period at the of sentence after "reserved" 4686 Albert Petrick 68.60 Period missing at end of sentence Add period at the of sentence "reserved" 4697 Albert Petrick 68.62 Period missing at end of sentence Add period at the of sentence after "reserved" 7918 Mark RISON 67.60 The field names are not referred to correctly Change to "DTIM Count field" and "DTIM Period field" 7919 Mark RISON 68.01 " the AP does not intend to transmit to the STA or to trigger the STA for an UL MU transmission" -- triggering is done by transmitting to the STA Delete "or trigger the STA for an UL MU transmission"
Working Name (Affiliation) Position Contact Details Adrian Stephens (Intel Corporation UK Ltd.) IEEE 802.11 Working Group Chair +44 1793 404825 (office) Jon Rosdahl (Qualcomm) 1st Vice Chair (Policies and Procedures) Treasurer +1 (801) 492-4023 Dorothy V. Stanley (HPE) 2nd Vice Chair (Rules and reflectors) IEEE 802 (LMSC) EC delegate +1 (630) 363-1389 Stephen McCann (BlackBerry Ltd.) Secretary Publicity ad-hoc Chair +44 1753 667099 Peter Ecclesine (Cisco Systems, Inc.) Co-Technical Editor +1 (408) 527-0815 Robert Stacey Corporation) Co-Technical Editor 802.11 Assigned Numbers Authority +1 (503) 712 4447 Standing Committees Name (Affiliation) Position Contact Details Jim Lansford (CSR Technologies Inc. a Qualcomm Company) Wireless Next Generation (WNG) Chair +1-719-286-8660 Mark Hamilton (Ruckus Wireless) Architecture (ARC) +1 (303) 441-7553 Andrew Myles (Cisco Systems, Inc.) ISO/IEC/JTC1/SC6 shadow committee (JTC1) +61 2 84461010 Rich Kennedy (Unlicensed Spectrum Advocates) Regulatory Chair +1 (832) 298-1114 Jon Rosdahl (Qualcomm ) Project Authorization Request (PAR) review Chair +1 (801) 492-4023 Task Groups Name (Affiliation) Position Contact Details Dorothy V. Stanley (HPE) TGmc (Revision mc) +1( 630) 363-1389 Yongho Seok (Self) TGah Chair (Sub 1 GHz Operation) +82-10-7581-0828 Hiroshi Mano (Koden Techno Info K.K.) TGai Chair (Fast Initial Link Setup) +81-3-5436-8350 Xiaoming Peng TGaj Chair +65-64082429
(Institute for Infocomm Research) (China Millimeter Wave) Donald Eastlake, 3rd (Huawei Technologies) TGak Chair (General Link) +1 508-333-2270 Stephen McCann (BlackBerry Ltd.) TGaq Chair (Pre-association Discovery) +44 1753 667099 Osama Aboul-Magd (Huawei) TGax Chair (pro-tem) (High Efficiency WLAN) +1 (613) 287-1405 Edward Au (Huawei) TGay Chair (Next Generation 60 GHz) +1 773 782 6875 Jonathan Segev (Intel Corporation) TGaz Chair (Next Generation Positioning) +972-54-2403587 Study Groups Name (Affiliation) Position Contact Details Topic Interest Groups Name (Affiliation) Position Contact Details Tim Godfrey (Electric Power Research Institute) Long Low Power (LRLP) TIG +1 (650) 855-8584 (office) Liaison Officials to non IEEE 802 organizations Name (Affiliation) Position Contact Details Stephen McCann (BlackBerry Ltd.) Liaison to 3GPP (3rd Generation Partnership Project) +44 1753 667099 Dorothy V. Stanley (Aruba Networks) Liaison to IESTF (Internet Engineering Task Force) +1( 630) 363-1389 Ian Sherlock (Texas Instruments Inc.) Liaison to WFA (Wi-Fi Alliance) +1-972-995-2011 Liaison Officials to IEEE 802 organizations Name (Affiliation) Position Contact Details Clint Chaplin (Samsung Electronics) Liaison to IEEE 802.15 +1 (408) 768-0827 Rich Kennedy (Unlicensed Spectrum Advocates) Liaison to IEEE 802.18 +1 (832) 298-1114 Tim Godfrey (Electric Power Research Institute) Liaison to IEEE 802.24 +1 (650) 855-8584 (office)
Patil Presence of TIM Element in FILS Discovery can have wider application, and doesn't have to be tied to TWTOperation only Remove the restriction, as in the comment Peter Keep Vendor Specific element as order 6 in FILS Discovery frame format as it is in 11ax baseline, do not delete it. Do not change order 6 text Modify section 3.2 Definitions specific to IEEE 802.11: Modify section 9.4.2.6 TIM element as follows:
Clause 9.4.2.219, CIDs: 7997, 9562, 9563, 5393 CID Comment Proposed Change Resolution 7997 It seems to me that the Dual Beacon subfield does not "indicate" the TBTT offset of the Beacon frame in HE extended range SU PPDU format. This offset is fixed and defined in subclause 11.1.3.10. Delete the sentence "The Dual Beacon subfield also indicates the TBTT offset of Beacon frame in HE extended range SU PPDU in 11.1.3.10 (Beacon generation in an HE BSS)." Add the sentence "The TBTT offset of Beacon frame in HE extended range SU PPDU is defined in 11.1.3.10 (Beacon generation in an HE BSS)." after "The subfield is set to 1 if the HE AP transmits beacons in an HE extended range SU PPDU and a non-HE PPDU.". Revised. As “HE dual beacon” is changed to “ Beacon”, and transmitted independently from non-HT Beacon frame, it is not necessary to bundle them together. Proposed resolution is to remove the sentence. See CID [#7978] 9562 In order to improve the deployment flexibility, it may require to independently control legacy beacon and HE beacon transmission. Increase the size Dual Beacon field to 2 bits. as in the comment Revised – As “HE dual beacon” is changed to “ Beacon”, and transmitted independently from non-HT Beacon, there is no need independently control legacy beacon and beacon transmissions. 9563 Modify the definition of Dual Beacon field. 00: Legacy Beacon only, 01: HE beacon only, 10: L+HE beacon with duplicated system info. 11: L+HE with non-duplicated system info Revised – See CID #9562. TGax Editor: Change the subclauses below as follows: 9.4.2.219 HE Operation element …… B0 B5 B6 B8 B9 B10 B19 B20 B21 B22 B27 B28 B29 B30 B31 BSS Default PE TWT HE Duration Based RTS BSS Color VHT Operation Present BSSID AP Tx BSSID BSS
address uses the same address value. It means that, if the first frame of the TXOP holder is transmitted with a common address, all other frames transmitted from the TXOP holder shall have the TA field set to a common address. 2450 802.11 base specification is saying the following: "A TXOP limit of 0 indicates that the TXOP holder may transmit or cause to be transmitted (as responses) the following within the current TXOP:" When the TXOP limit is equal to 0, the HE MU PPDU or HE PPDU can be transmitted. Change 3rd paragraph of sub-clause 10.22.2.8 (TXOP limits) as the following: ... a) One of the following at any rate, subject to the rules in 10.7 (Multirate support) 1) One or more SU PPDUs carrying fragments of a single MSDU or MMPDU 2) An SU PPDU or a VHT MU PPDU or a HE MU PPDU or a HE PPDU carrying a single MSDU, a single MMPDU, a single or a single 3) A VHT MU PPDU or a HE MU PPDU carrying to different users (a single A-MPDU to each user) 4) A QoS Null frame or PS-Poll frame ... c) Any frames required for protection, including one of the following: 1) An RTS/CTS or As per comment Revised- Agreen in principal. When the TXOP limit is equal to 0, the HE MU PPDU or HE PPDU can be transmitted. Change 3rd paragraph of sub-clause 10.22.2.8 (TXOP limits) as suggested by the commenter. TGax editor makes changes as shown in the as specified in based
17 Ganming (Ming) Huawei Technolgies 18 Chittabrata 19 Qiang Guo Huawei Technologies 20 Reza Hedayat Newracom 21 Frank Hsu MediaTek 22 Chunyu Hu Broadcom 23 Po-Kai Intel 24 Russel Huang MediaTek 25 Yasuhiko Inoue NTT 26 Jeongki Kim LG Electronics 27 Suhwook Kim LG Electronics 28 Youhan Kim Qualcomm 29 Jarkko Kneckt 30 Geonjung Ko Wilus 31 Young Hoon Kwon Newracom 32 Zhou Lan Broadcom 33 Guoqing Li Apple 34 Yunbo Li Huawei Technologies 35 Dongguk Lim LG Electronics 36 Jianhan Liu MediaTek 37 Peter Loc Huawei Technologies 38 Kaiying Lv ZTE 39 Jing Ma NICT 40 Narendar Madhavan Toshiba 41 Simone Merlin Qualcomm 42 Saishankar Nandagopalan Cypress 43 Patrice Nezou Canon 44 Yujin Noh Newracom 45 Robert Olesen InterDigital 46 Oghenekome Oteri InterDigital 47 Eunsung Park LG Electronics 48 Viger Pascal Canon 49 Abhishek Patil Qualcomm 50 Al Petrick InterDigital 51 Ron Porat Broadcom 52 Zhigang Rong Huawei Technologies 53 Kiseon Ryu LG Electronics 54 Sigurd Schelstaete Quantenna 55 Yongho Seok Newracom 56 John Son 57 Junghoon Suh Huawei Technologies 58 Bo Sun ZTE 59 Robert Stacey Intel 60 Yusuke Tanaka Sony 61 Bin Tian Qualcomm 62 Tao Tian Spreadtrum 63 Lochan Verma Qualcomm 64 Huizhao Wang Quantenna 65 Wang MediaTek 66 Xiaofei Wang InterDigital 67 Lisa Ward Rhode & Schwartz 68 Xun Yang (David) Huawei Technologies 69 Jian Yu (Ross) Huawei Technologies 70 Hongyuan Marvell 71 Yan Zhang Marvell 72 Yuval Har Zion Celeno
SIFS after the Trigger frame. The BlockAck frames report the HE STA's reception status of the block of group addressed frames requested by the frame." BlockAck, or frame carried in the HE trigger-based PPDU sent as a response SIFS after the Trigger frame. The BlockAck frames report the HE STA's reception status of the block of group addressed frames requested by the variant Trigger frame or the GCR variant Trigger frame." 3209 Ahmadreza Hedayat 135.35 "After completing the BlockAckReq or and BlockAck frame exchanges ..." "After completing the BlockAckReq frame, MU-BAR variant Trigger frame, or GCR MU-BAR variant Trigger frame and BlockAck frame exchanges ..." Revised - The mention of GCR MU-BAR Trigger frame is added to the referred text. TGax editor to make the changes shown in 11-16/8888r0 under all headings that include this CID. 3210 Ahmadreza Hedayat 135.53 "An originator may also send an MU-BAR frame with AID12 fields set to AIDs of HE STAs that transmit the BlockAck frames and the Block Ack Starting Sequence Control subfield set to the Sequence Number field of the earliest of the GCR stream that has not been acknowledged by all group members and has not expired due to lifetime limits, in order to minimize buffering latency at receivers in the GCR group." "An originator may also send an MU-BAR variant Trigger frame or a GCR MU-BAR variant Trigger frame with the AID12 fields set to the AIDs of HE STAs that are expected to transmit the BlockAck frames and the Block Ack Starting Sequence Control subfield set to the Sequence Number field of the earliest A-MSDU of the GCR stream that has not been acknowledged by all group members and has not expired due to lifetime limits, in order to minimize buffering latency at receivers in the GCR group." Revised - The mention of GCR MU-BAR Trigger frame is added to the referred text. TGax editor to make the changes shown in 11-16/8888r0 under all headings that include this CID. MSDU A-
STA is associated when the Partial BSS Color field in the most recently received[7071] HE Operation element is 1. An HE AP receives either a VHT MU PPDU or an HE MU PPDU with the RXVECTOR parameter UL_FLAG set to 0[5686,6152,6582,7022,8693,9380]. If the received detected [5167]frame satisfies both intra-BSS and inter-BSS conditions, the detcted frame is an inter-BSS frame the decision made by using the MAC address takes precedence over the decision made by using the RXVECTOR parameter BSS_COLOR. [6176,6574,6576,6583,9727] If the received detected[5167] frame does not satisfy any of the intra-BSS and inter-BSS conditions, then the frame cannot be determined as intra-BSS or inter-BSS frame.
TGax Editor: Please add the subsection 27.5.2.6.4 (Acknowledgement for random access) of 11ax Draft 1.0 as follows (#5036, 7254, 7546, 8140, 8520, 8527 8157 9332 9119 9120):
TGax Editor: Please add the subsection 27.5.2.6.4 (Acknowledgement for random access) of 11ax Draft 1.0 as follows (#5036, 7254, 7546, 8140, 8520, 8157 9332 9119 9120):
IEEE P802.11 Wireless LANs 11ax D1.0 MAC Comment Resolution for Date: 2017-02-28 Author(s): Name Affiliation Address Phone email Chao-Chun Wang MediaTek Inc 2840 Junction Ave, San Jose, CA 95134, USA Chaochun.wang @mediatek.com 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 D1.0 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D1.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 4782 144.32 11.49.1 The case of Partial BSS Color is 0 is missing. Specify that when that bit is 0 then the AP uses the AID assignment rules of baseline. As in comment. Rejected. P91, L39-42 has the description. “ The BSS Color field is an unsigned integer whose value is the BSS color of the BSS corresponding to the AP which transmitted this element, except that a value of 0 in this field indicates that there is no BSS color for this BSS.” 5975 144.32 11.49.1 Where is the Partial BSS Color field? Please provide the name of the frame and other details. Please clarify where is the Partial BSS Color field. Rejected: The Partial BSS Color field indicates whether or not the BSS applies an AID assignment rule using the partial BSS color bits. If the Partial
TX DMG antenna ID for SS8 2 93 This field indicates the DMG antenna that the transmitter of this control trailer uses for SS8. Reserved if SISO/MIMO is set to 0. RX DMG antenna ID for SS8 2 95 This indicates the DMG antenna that the recipient of this control trailer uses for SS8. Reserved if SISO/MIMO is set to 0. Reserved 30 Set to 0 by the transmitter and ignored by the receiver. Insert the following tables at the end of the subclause,after the Table 30 9.4.2.134 DMG TSPEC element Change Figure 9-521 as follows Eelement ID Length DMG Allocation Info BF Control Allocation Period Minimum Allocation Maximum Allocation Octets: 1 1 1 4 2 2 2
IEEE P802.11 Wireless LANs Date: 2017-03-13 Author(s): Name Affiliation Address Phone email Suhwook Kim LG Electronics 19, Yangjae-daero 11gil, Seocho-gu, Seoul 137-130, Korea suhwook.kim@lge.com Kiseon Ryu LG Electronics 19, Yangjae-daero 11gil, Seocho-gu, Seoul 137-130, Korea kiseon.ryu@lge.com Abhishek Patil Qualcomm Inc. appatil@qti.qualcomm.com Abstract This submission proposes resolutions for multiple comments related to TGax D1.1 with the following CIDs: CIDs: 7103,7106,7412,8152,8221,9103,9533 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. This introduction is 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. OFDMA based Random Access (27.5.2.6) CID Page Clause Comment Proposed Change Resolution 7103 27.5.2.6.2 Regarding Figure of the UL random access procedure, 1) The meaning of the location of the arrows is not clear. 2) The differences between "before" and "after" the decrement is not explained and unclear. 3) Only one "SIFS" is written. This should be added to other places. Modify Figure 27-1 for clarification. Revised Added text and Figure 27-1 to explain more precisely TGax editor please make the changes as shown in 11-17/0443r2 0 Illustration
Definitions FTM Initiator – the STA initiating the FTM procedure. FTM Responder – the STA responding to the FTM Procedure establishment request IFTM – Initial FTM IFTMR – Initial FTM Request frame. Type A Adversary – The attacker is assumed to have response time to standard-specified OTA events or scenario dependent fields of 1 msec or longer. Type B Adversary - The attacker is assumed to have response time to known OTA events or known pre-defined fields of 1usec or longer (up to 1msec). [2017/0120r2] Abbreviations and acronyms MU – Multi User SU – Single User NDP – Null Data Packet NDPA – NDP Announcement VHT NDP Sounding-based .11az SU protocol (VHTz) HEW NDP Sounding-based .11az MU protocol (HEWz) TOF – Time Of Flight BRP – Beam Refinement Protocol Positioning Protocol for Improved Accuracy and Coverage over 2.4 and 5 GHz bands General The .11az protocol extend the REVmc iFTMR/iFTM for .11az ToF measurement parameter negotiation The .11az protocol shall define the following phases
Definitions FTM Initiator – the STA initiating the FTM procedure. FTM Responder – the STA responding to the FTM Procedure establishment request IFTM – Initial FTM frame. IFTMR – Initial FTM Request frame. Type A Adversary – The attacker is assumed to have response time to standard-specified OTA events or scenario dependent fields of 1 msec or longer. Type B Adversary - The attacker is assumed to have response time to known OTA events or known pre-defined fields of 1usec or longer (up to 1msec). [2017/0120r2] Abbreviations and acronyms MU – Multi User SU – Single User NDP – Null Data Packet NDPA – NDP Announcement
TGax Editor: Update D1.1 P382L13 as below: The value of the PSDU_LENGTH parameter for user u returned in the PLME-TXTIME.confirm primitive for an HE MU PPDU is calculated using Equation (28-131). NSYM,init is given by Equation (28-78) NDBPS,last,init,u is given by Equation (28-79) [End of File]