zilongwang/ReadingBank huggingface dataset:
6.3.117.4 MLME-TDD-BF-TRAINING.indication 6.3.117.4.1 Function This primitive indicates that TDD beamforming training with a peer STA, and at the request of that peer, has completed . 6.3.117.4.2 Semantics of the service primitive The primitive parameters are as follows: MLME-BF-TRAINING.indication ( PeerSTAAddress, NumberOfTDDFeedbacks, , ResultCode ) Name Type Valid range Description PeerSTAAddress MACAddress Any individual MAC address Specifies the address of the peer MAC entity with which TDD beamforming training was performed or attempted. Integer 0 – 1024 Indicates the number of TDD Feedbacks included. TxBeamFeedback Set of Tx Beam Feedback fields As defined in 9.4.2.269 (TDD Route element) One or more Tx Beam Feedback fields are present. ResultCode Enumeration SUCCESS, FAILURE Indicates the result of the TDD beamforming procedure. 6.3.117.4.3 When generated This primitive is generated by the MLME to result of TDD procedure was initiated by the peer STA. 6.3.117.4.4 Effect on receipt The SME is notified of the result of the procedure.
9. Frame formats 9.2 MAC frame formats 9.2.4 fields 9.2.4.1 Frame Control field 9.2.4.1.3 Type and Subtype subfields Change 9-2 as follows Type value B3 B2 Subtype B7 B6 B5 B4 Control Frame Extension value B11 B10 B9 B8 Description 01 0110 0000 Sector Ack 01 0110 0001 Ack Schedule 01 0110 0010 Poll 01 0110 0011 SPR 01 0110 0100 Grant 01 0110 0101 DMG CTS 01 0110 0110 DMG DTS 01 0110 0111 Grant Ack 01 0110 1000 SSW 01 0110 1001 SSW-Feedback 01 0110 1010 SSW-Ack 01 0110 1011 TDD Beamforming 01 0110 1100 – 1111 Reserved Add below sections as follows 9.3.1.24 TDD Beamforming frame format 9.3.1.24.1 Overview The frame format for the TDD Beamforming frame is defined in Figure 12. Frame Control Duration RA TA TDD Beamforming Control TDD Beamforming Information FCS Octets : 2 2 6 6 1 6 4 Figure 12—TDD Beamforming frame format The Duration field is set to the time until the end of the current TDD Slot (see 10.36.6.2.2). The RA field the MAC address of the intended receiver of the TDD Beamforming frame. The TA field the MAC address of the transmitter STA of the TDD Beamforming frame. The TDD Beamforming Control field is defined as shown in Figure 13. TDD Beamforming Frame Type End of Training Reserved Bits: 2 1 Figure 13—TDD Beamforming Control subfield format
STA behavior ASTA is scheduled to respond to the NDP Feedback Report Poll Trigger if its AID is greater than or equal to the starting AID and less than starting AID + NSTA, using the Starting AID subfield in the eliciting Trigger frame, and with NSTA the total number of STAs that are scheduled to respond to the NDP Feedback Report Poll Trigger frame. NSTA is calculated by the following equation, with BW subfield and Multiplexing Flag subfield from the eliciting Trigger frame: NSTA = 18  2BW  (Multiplexing Flag)(#7108)
IEEE P802.11 Wireless LANs Text Dynamic OBSS_PDlevel `Date: 2018 - 03 Author(s): Name Affiliation Address Phone email Graham SR Technologies Davie, FL, USA 916 799 9563 Gsmith@srtrl.com Lauren Cariou Intel Lautrent.cariiou@intel.com CID 166 Suggested changes for DSC to 802.11 Standard BACKGROUND The following text edits are based upon D2.2. At P157.43, Figure 9-589cx Add “OBSS PD Margin field Element ID 255 Length Element ID Extension SR Control OBSS PD Max Offset SRG OBSS PD Min Offset SRG BSS PD Max offset SRG BSS Color Bitmap SRG Partial BSSID Bitmap OBSS PD Margin Octets 1 1 1 1 0 or1 0 or 1 0 or 1 0 or 8 0 or 8 0 or 1 Figure 9-589cx – Spatial Reuse Parameter Set element At P158.5 Figure Add “OBSS PD Margin Present” subfield Non-
– – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Guidelines (Approved 09 Mar 2018) – • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 10 Nov 2017) – References:
IEEE P802.11 Wireless LANs TGmd 2018-04 teleconference and ad-hoc agenda Date: 2018-04-09 Author(s): Name Affiliation Address Phone email Dorothy Stanley Hewlett Packard Enterprise 3333 Scott Blvd, Santa Clara CA 95054 +1 630-363-1389 2018 Teleconference Agendas TGmd will hold 2 (2-hour) teleconferences before the May 2018 session: April 6th and 27th at 10am Eastern for comment collection comment resolution and presentations. We’ll use the bridge: , see for more detailed instructions. The agenda for the April 6th and 27th teleconferences is below: 1. Call to order, attendance, and patent policy a. Call for potentially essential patents: If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: i. Either speak up now or ii. Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or iii. Cause an LOA to be submitted b. 2. Editor report – Emily QI a. Editor report document, b. Comments received LB 232 are here: : 3. Comment resolution. 2018-04-06 Edward AU - Editor 2 CIDs: ; Any comments on proposed resolutions, reminder to review, plan to motion in May Edward AU - Editor 2 CIDs – Direction of resolution for 24 similar comments: 1196, 1197, 1198, 1199, 1200, 1201, 1202, 1203, 1204, 1205, 1206, 1207, 1208, 1209, 1210, 1211, 1212, 1213, 1214, 1215, 1216, 1217, 1218, and 1219 Additional CIDs CID 1329, 1236 Emily QI – Editor CIDs, see and 11-18-0658 Graham SMITH – CIDs 1000, 1147 Graham SMITH – CID 1347 – Graham SMITH – CIDs 1356, 1358- Available CIDs/presentations
CID assignment 2018-04-27 Comment resolution FILS CIDs: 1243, 1244, 1323, 1324, 1334, 1335, 1336, 1337, 1338, 1532, 1534, 1539, 1541, 1543, 1544 Additional CIDs/Presentations 4. AOB 5. Adjourn Teleconferences are subject to applicable policies and procedures, see ================================================== • IEEE Code of Ethics – • IEEE Standards Association (IEEE-SA) Affiliation FAQ – • Antitrust and Competition Policy – • IEEE-SA Patent Policy – – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Guidelines (Approved 09 Mar 2018) – • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 10 Nov 2017) – 2018 April Ad-Hoc Agenda As approved at the January 2018 interim meeting, TGmd will hold an ad-hoc meeting on Tuesday, Wednesday and Thursday April 10-12, 2018 in Fort Lauderdale, FL USA. Teleconference facilities will be provided. Location: W Hotel, 401 North Fort Lauderdale Beach Boulevard, Fort Lauderdale, Florida 33304 Teleconference bridge: Meeting number (access code): 622 666 180 Host key: 401221 Meeting password: TGmdFLL Join from a video system or application Dial You can also dial 173.243.2.68 and enter your meeting number.
Additional CIDs Wednesday April 11, 9:30am – 11:30am (AM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Graham SMITH – 11-18-672, 11-18-666 Wednesday April 11, 1pm – 3pm (PM1) 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Additional CIDs Wednesday April 11, 3:30pm – 5:30pm (PM2) Cancelled – event Thursday April 12, 9:30am – 11:30am (AM1) Graham SMITH – 11-18-655, 11-18-666 Mike MONTEMURRO – 11-18-670 Clause 5 CIDs: 1527, 1559, 1561 Thursday April 12, 1pm – 3pm (PM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Jon ROSDAHL – GEN CIDs – assignments & selected CIDs Edward AU – 11-18-676 Additional CIDs Thursday April 12, 3:30pm – 5pm (PM2) 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Clause 6 CIDs Plans for May meeting AOB Adjourn ================================================== Applicable Policies and Procedures: • IEEE Code of Ethics – • IEEE Standards Association (IEEE-SA) Affiliation FAQ – • Antitrust and Competition Policy – • IEEE-SA Patent Policy – – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Chair's Guidelines (Approved 09 Mar 2018) – • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 10 Nov 2017) – References:
Additional CIDs Wednesday 11, 9:30am – 11:30am (AM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Graham SMITH – 11-18-672, 11-18-666 Wednesday April 11, 1pm – 3pm (PM1) 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Additional CIDs Wednesday April 11, 3:30pm – 5:30pm (PM2) Cancelled – event Thursday April 12, 9:30am – 11:30am (AM1) Graham SMITH – 11-18-654, 11-18-656 (CIDs 1147, 1356,1358) 11-18-666 Mike MONTEMURRO – 11-18-670 Thursday 12, 1pm – 3pm (PM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Thursday April 12, 3:30pm – 5:45pm (PM2) Mike MONTEMURRO – CID 1521 Edward AU – 11-18-676 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Jon ROSDAHL – GEN CIDs – assignments & selected CIDs Plans for May meeting AOB Adjourn ================================================== Applicable Policies and Procedures: • IEEE Code of Ethics – • IEEE Standards Association (IEEE-SA) Affiliation FAQ – • Antitrust and Competition Policy – • IEEE-SA Patent Policy – – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Chair's Guidelines (Approved 09 Mar 2018) – • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 10 Nov 2017) – References:
Additional CIDs Wednesday April 11, 9:30am – 11:30am (AM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Graham SMITH – 11-18-672, 11-18-666 Wednesday 11, 1pm – 3pm (PM1) 9.4.2.45 (multiple CIDs – 1287, 1289 to 1299 Additional CIDs Wednesday April 11, 3:30pm – 5:30pm (PM2) Cancelled – local event Thursday April 12, 9:30am – 11:30am (AM1) Graham SMITH – 11-18-654, 11-18-656 (CIDs 1147, 1356,1358) 11-18-666 Mike MONTEMURRO – 11-18-670 Thursday April 12, 1pm – 3pm (PM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Thursday 12, 3:30pm – 5:45pm (PM2) Mike MONTEMURRO – CID 1521 Edward AU – 11-18-676 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Jon ROSDAHL – GEN CIDs – assignments & selected CIDs Plans for May meeting AOB Adjourn ================================================== Applicable Policies and Procedures: • IEEE Code of Ethics – • IEEE Standards Association (IEEE-SA) Affiliation FAQ – • Antitrust and Competition Policy – • IEEE-SA Patent Policy – – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Chair's Guidelines (Approved 09 Mar 2018) – • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 10 Nov 2017) – References:
Clause 4 CIDs: 1534, 1574 Additional CIDs Wednesday April 11, 9:30am – 11:30am (AM1) QI – 11-18-658 – non-trivial editorial CIDs Graham SMITH – 11-18-672, 11-18-666 Wednesday April 11, 1pm – 3pm (PM1) 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Additional CIDs Wednesday April 11, 3:30pm – 5:30pm (PM2) Cancelled – local event Thursday April 12, 9:30am – 11:30am (AM1) Graham SMITH – 11-18-654, 11-18-656 (CIDs 1147, 1356,1358) 11-18-666 Mike MONTEMURRO – 11-18-670 Thursday April 12, 1pm – 3pm (PM1) Emily QI – 11-18-658 – non-trivial editorial CIDs Thursday April 12, 3:30pm – 5:45pm (PM2) Mike MONTEMURRO – CID 1521 Edward AU – 11-18-676 9.4.2.45 (multiple BSSID) CIDs – 1287, 1289 to 1299 Jon ROSDAHL – GEN CIDs – assignments & selected CIDs Plans for May meeting AOB Adjourn ================================================== Applicable Policies and Procedures: • IEEE Code of Ethics – • IEEE Standards Association (IEEE-SA) Affiliation FAQ – • Antitrust and Competition Policy – • IEEE-SA Patent Policy – – – – • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) – • IEEE 802 LMSC Chair's Guidelines (Approved 09 Mar 2018) – • Participation in IEEE 802 Meetings – • IEEE 802.11 WG OM: (Approved 10 Nov 2017) – References:
Study Groups & Topic Interest Groups (TIG) Name (Affiliation) Position Contact Details Marc Emmelmann Broadcast Services (BCS) Study Group Chair Michael Montemurro (Blackberry) Extremely High Throughput Topic Interest Group Chair P. K. Gilb (General Atomics Aeronautical Systems Inc., University of San Diego, Gilb Consulting) Full Duplex Topic Interest Group Chair +1 858-229-4822 Bo Sun (ZTE) Next Generation V2X (NGV) Study Group Chair Liaison Officials to non IEEE-802 organizations Name (Affiliation) Position Contact Details Yee (Akayla) Liaison to IETF (Internet Engineering Task Force) 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 Juan-Carlos Zuniga (InterDigital Communications) Liaison to IEEE 802E Rich Kennedy Liaison to IEEE 802.18 +1 (832) 298-1114 Tuncer Baykas (Istanbul Medipol Universitesi) Liaison to IEEE 802.19 Tim Godfrey (Electric Power Research Institute) Liaison to IEEE 802.24 +1 (650) 855-8584 (office) Annex C : Minutes This Annex contains references to all IEEE 802.11 SC/TG/SG & Ad Hoc Committee (AHC) minutes from this meeting. Please note that they are NOT subject to the approval of these minutes, but are confirmed and approved by their individual group in the opening meeting at their next session. WG TE 18-0634r0
IEEE P802.11 Wireless LANs CR for CID 1949 Date: 2018-- Author(s): Name Affiliation Address Phone email Gaius Wee Panasonic 202 Bedok South Avenue 1, #02-11, Singapore 469332 Hiroyuki Motozuka Solomon Trainin Qualcomm strainin@qti.qualcomm.com CID Page Line Comment Proposed Change Proposed Resolution 1949 39 2 In the draft text the Figure 9-61 does not cover and the Figure 12 makes no sense to DMG devices due to "Unsolicited RSS Enabled field" that is not backward compatible Keep the Figure as is and provide additional figure that is EDMG specific that may define B14 and Next only Revised The unsolicited RSS as defined in 10.39.6.2 is only performed between two EDMG STAs. A non-EDMG STA does not use this subfield. Add text to clarify that non-EDMG STA ignores this subfield. Also, merge the IsResponderTXSS and Unsolicited RSS Enabled subfields as they can coexist in a single beacon interval control field format since its meaning can be determined by the value of the Next A-BFT subfield.
IEEE P802.11 Wireless LANs CR for CID 1949 Date: 2018-4-25 Author(s): Name Affiliation Address Phone email Wee Panasonic 202 Bedok South Avenue 1, #02-11, Singapore 469332 Hiroyuki Motozuka Solomon Trainin Qualcomm strainin@qti.qualcomm.com CID Page Line Comment Proposed Change Proposed Resolution 1949 39 2 In the draft text the Figure 9-61 does not cover and the Figure 12 makes no sense to DMG devices due to "Unsolicited RSS Enabled field" that is not backward compatible Keep the Figure as is and provide additional figure that is EDMG specific that may define B14 and Next only Revised Add text to clarify that non-EDMG STA ignores subfield. Note – a DMG STA needs to rely on the IsResponderTXSS subfield of the BI to determine the type of the A-BFT within that BI. Note – a STA can be determined by the EDMG Supported subfield in the
IEEE P802.11 Wireless LANs CR for CID 1949 Date: 2018-4-25 Author(s): Name Affiliation Address Phone email Wee Panasonic 202 Bedok South Avenue 1, #02-11, Singapore 469332 Hiroyuki Motozuka Solomon Trainin Qualcomm strainin@qti.qualcomm.com Carlos Cordeiro Intel carlos.cordeiro@intel.com CID Page Line Comment Proposed Change Proposed Resolution 1949 39 2 In the draft text the Figure 9-61 does not cover and the Figure 12 makes no sense to DMG devices due to "Unsolicited RSS Enabled field" that is not backward compatible Keep the Figure 9-61 as is and provide additional figure that is EDMG specific that may define B14 and Next A-BFT only Revised Keep figures Add text to clarify that non-EDMG STA ignores the Unsolicited RSS Enabled subfield. Also that EDMG STA ignores this subfield when received from a non-EDMG STA. Additionally, add text to clarify that the IsResponderTXSS subfield is present only when Next A-BFT is zero. Note 1 - the unsolicited RSS as defined in 10.39.6.2 is only performed between two
EDMG STAs. A non-EDMG STA does not use this subfield. Note 2 – a DMG STA needs to rely on the IsResponderTXSS subfield of the BI to determine the type of the A-BFT within that BI. Note 3 – a STA can be determined by the EDMG Supported subfield in the DMG Parameters field. TGay editor to make the changes shown in under all headings that include CID 1949. 1465 39 6 It is confusing to have two different figures that are 99% identical except for the definition of one bit. Can we reduce to one figure? Consolidate the two pictures for Figure 9-61 and clarify the difference in the meaning of B14 when Next is zero Reject Existing text “The difference between the two formats is in the definition of the field occupying B14” makes the situation clear. See resolution of CID 1949 also for additional clarification texts. Proposed changes to D1.1: 9.3.4.2 DMG Beacon Insert the below editor’s instruction and paragraphs before “Insert the following paragraph after the definition of the IsResponderTXSS subfield” (CID #1949)
is a spatial mapping matrix is a matrix element from mth row and nth column In case of spatial expansion, the PPDU waveform of the pre-EDMG and Data fields for the iTXth transmit chain includes a cyclic shift, , dependent on the particular transmit chain number. The cyclic shift, , is defined in SC chip units as (iTX – 1)×Nc×Tc, where Nc is equal to 4 chips and Tc is a chip time duration. where: The TRN field, , shall be defined at the SC chip rate equal to 1.76 GHz per iTXth transmit chain as defined in 30.9.2.2.5. The resulting SU PPDU waveform for a 2.16 GHz channel and single space-time stream (STS = 1) for the iTXth transmit chain concatenates the preamble and Data fields with the TRN field and shall be defined as: is the duration of the L-STF, L-CEF, L-Header, EDMG-Header-A, and Data fields of the PPDU The filtering procedure is performed with a pulse shaping filter, , defined at the Nup×1.76 GHz sampling rate as follows: where: is the length of in samples The definition of the shaping filter impulse response, , and the Nup parameter are implementation dependent.
PPDU transmission over a 2.16 GHz channel with STS > 1 and 4.32 GHz, 6.48 GHz, 8.64 GHz channel with STS ≥ 1 General An EDMG SC mode SU PPDU transmitted over a 2.16 GHz channel with more than one stream (STS > 1) or over a 4.32 GHz, 6.48 GHz, 8.64 GHz channels with one or more space-time streams (STS ≥ 1) is composed of pre-EDMG fields, EDMG preamble, Data field and TRN field. The total number of transmit chains, NTX, shall be constant over the different fields of the EDMG SU PPDU. re-EDMG fields The pre-EDMG fields of the PPDU includes the following modulated fields: where: is the duration of the L-STF field of the PPDU is the total duration of the L-STF and L-CEF fields of the PPDU is the total duration of the L-STF, L-CEF and L-Header fields of the PPDU The definition of the L-STF, L-CEF, and L-Header fields is provided in 30.3.3.2.2, 30.3.3.2.3, and , respectively. In case of digital beamforming transmission, the PPDU waveform of the pre-EDMG fields for the transmit chain shall be defined as: where: is a spatial mapping matrix is a matrix element from mth row and nth column In case of spatial expansion, the PPDU waveform of the pre-EDMG fields for the iTXth transmit chain includes a cyclic shift, , dependent on the particular transmit chain number. The cyclic shift, , is defined in SC chip units as (iTX – 1)×Nc×Tc, where Nc is equal to 4 chips and Tc is a chip time duration. where: The waveform for the pre-EDMG fields for iTXth transmit chain is obtained by up-sampling and filtering and then appropriate carrier frequency shift of the waveform, if required. The up-sampling procedure is applied using a factor of Nup. The filtering procedure is performed with a pulse shaping filter defined at the Nup×1.76 GHz sampling rate as: is the length of in samples
is a spatial mapping matrix is a matrix element from mth row and nth column In case of spatial expansion, the PPDU waveform of the pre-EDMG and Data fields for the iTXth transmit chain includes a cyclic shift, , dependent on the particular transmit chain number. The cyclic shift, , is defined in SC chip units as (iTX – 1)×Nc×Tc, where Nc is equal to 4 chips and Tc is a chip time duration. where: The TRN field, , shall be defined at the SC chip rate equal to 1.76 GHz per iTXth transmit chain as defined in 30.9.2.2.5. The resulting SU PPDU waveform for a 2.16 GHz channel and single space-time stream (STS = 1) for the iTXth transmit chain concatenates the preamble and Data fields with the TRN field and shall be defined as: where: is the total duration of the L-STF, L-CEF, L-Header, EDMG-Header-A, and Data fields of the PPDU The filtering procedure is performed with a pulse shaping filter, , defined at the Nup×1.76 GHz sampling rate as follows: where: is the length of in samples The definition of the shaping filter impulse response, , and the Nup parameter are implementation dependent.
IEEE P802.11 Wireless LANs 802.11ba Teleconference Minutes April 2018 Date: 04-02-18 Author(s): Name Affiliation Address Phone email Leif Wilhelmsson Ericsson AB Mobilvägen 1, 22632 Lund, Sweden +46-706-216956 Teleconference on Monday, April 2nd, 2018, 5:00 – 6:00pm (ET) Agenda: 1. Call meeting to order 2. Agenda setting 3. Patent policy (link at the end of the email) 4. Attendance: send to the chair or secretary (leif.r.wilhelmsson@) 5. Presentations 1) 17/1395r1 “Simple multiplexing of wake-up signals” - Leif Wilhelmsson 2) 18/473 " WUR Discovery Frame Format" - Guoqing Li 6. Adjourn Please note that teleconferences are bound by the conditions stipulated by the documentation below. Please review them and bring up any questions/concerns you may have before proceeding with the teleconference: IEEE Patent Policy - Patent FAQ - LoA Form - Affiliation FAQ - FAQ - Ethics - IEEE 802.11 Working Group Operations Manual – Chair Minyoung Park (Samsung) calls the meeting to order at 5:00pm (ET).
Name Affiliation 1 Osama Aboul-Magd Huawei Technologies 2 Tomo Adachi Toshiba 3 Woojin Ahn Wilus Institute 4 Alfred Asterjadhi Qualcomm 5 Liwen Chu Marvell Semiconductors 6 Yasu Inoue NTT 7 Wookbong Lee Samsung Electronics 8 Narendar Madhavan Toshiba 9 Kome Oteri InterDigital Communications 10 Al Petrick InterDigital Communications 11 Sigurd Schelstraete Quantenna Communications 12 Yongho Seok MediaTek 13 Lochan Verma Qualcomm 14 15
IEEE P802.11 Wireless LANs Resolution for CIDs 1000, 1147 Date: 2018-04 Author(s): Name Affiliation Address Phone Graham SMITH SR Technology Davie, FL, USA. 916 799 9563 gsmith@srtrl.com CID Commenter Clause Page Line Comment Proposed 1000 Lei 3.2 162 31 since PCF has been removed, "point-coordinated BSS" should be changed to "BSS" As per comment sentence: contention period (CP): The time period outside of the contention free period (CFP) in a basic service set (BSS).(#65) In D0.1 149.7 we see contention period (CP): The time period outside of the contention free period (CFP) in a point-coordinated basic service set (BSS). In a BSS where there is no point coordinator (PC), this corresponds to the entire time of operation of the BSS. CID 63 Resolution edited this as follows: 149.7 modify as follows: “contention period (CP): The time period outside of the contention free period (CFP) in a basic service set (BSS). The error can be seen; although deleted, “point-coodinated” was not shown as deleted, The resolution should have been contention period (CP): The time period outside of the contention free period (CFP) in a basic service set (BSS). Commenter is correct. RESOLUTION: REVISED At 162.31 delete “point-cordinated” contention period (CP): The time period outside of the contention free period (CFP) in a basic service set (BSS). CID Commenter Clause Page Line Comment Proposed 1147 Yongho Seok 10.3.5 1612 39 "A STA using the DCF shall use an RTS/CTS exchange for individually addressed frames when the length of the PSDU is As in comment
TGay Editor: modify in Table 1 — RBUFCAP encoding for the EDMG Compressed BlockAck variant P53 (Draft 1.1) as follows: Indicates that the recipient’s memory has enough space to receive A-MPDUs with a length Maximum Length Exponent (Table 5) CID Page Clause Comment Proposed Change 1081 112.23 10.13.7 802.11ah introduced as a general term. So, is no need to add a new terminology for EDMG case. Use S-MPDU for the whole case. 2400 35.00 9.3.1.9.8 S-MPDU is introduced in 11ah, is defined in REVmd_D 0.5. 11ax also replaces single to Change "single MPDU" to Do it through the whole draft. Proposal: Accept CID Page Clause Comment Proposed Change 1083 196.12 10.62.1 It looks like the MPDU sequence number is the same with the original sequence number. The relation between the original sequence number should be explained somewhere in section 9. As in comment. Proposal: Reject Discussion: Sequence Control field that covers the relevant sequence number is defined in 9.2.4.4.1 (Sequence Control field) CID Page Clause Comment Proposed Change 1112 31.07 9.2.4.4.1 The Start of MSDUn subfield is set to one to indicate that the contains the first segment of an MSDU. It is set to zero otherwise. Either change the logic to "The Start of MSDUn subfield is set to zero to indicate..." or remove the n from the subfield name Proposal: Reject Discussion: The comment and the proposal are unclear, and the suggested change does not have any technical impact. MPDU
1256 30.04 9.2.4.4.1 The starting bit position of the MPDU Sequence Number in Figure 4 should be B(MPDU Modulo+3). Modify the diagram with correct bit position 1257 30.04 9.2.4.4.1 the length of the MPDU Sequence Number in Figure 4 is illustrated as B(MSDU Modulo+2), should it be B(MPDU Modulo+3) Correct the diagram Proposal: Reject Discussion: Let’s take an example of MSDU Modulo = 5. In this case the MSDU SN field is [B2 – B6], it is 5 bits allocated for MSDU Modulo. The MPDU SN field is [B7-B15] – it is 9 bits allocated for MPDU SN. 9+5 = 14 equal to the MSDU modulo + MPDU modulo. So, no issues to fix are found. CID Page Clause Comment Proposed Change 1285 31.07 9.2.4.4.1 "The Start of MSDUn subfield is set to one to indicate that......" Change "set to one to " to " set to 1 to" for keeping the same style as REVmd As in comment. Much places need to change, if this comment is approved. Proposal: Reject Discussion: Propose keeping on the editor’s responsibility to resolve the style issues. CID Page Clause Comment Proposed Change 1380 31.04 9.2.4.4.1 It is not clear what is the structure of this field (reserved bits), when MSDU Modulo+MPDU Modulo<14 Add reserved bits 1381 32.14 9.3.1.8.3 It is not clear what is the structure of this field (reserved bits), when MSDU Modulo+MPDU Modulo<14 Add reserved bits Proposal: Revised
1203 Adrian Stephens 9.4.2.250.1 "non-AP or non-PCP EDMG STA" This is inherently ambiguous as it combines (or) and (and) operations and is no clear operator precedence. In this case, is the non-AP STA also an EDMG STA? I suspect it is also incorrect, because AP and PCP EDMG STAs also transmit this element. Replace all such use with the expanded term EDMG STA or non-PCP EDMG STA". Resolution: Revise Discussion: Text is ambiguous and should be changed throughout 802.11ay. It is true that AP EDMG STAs and PCP EDMG STAs transmit this element, however these STAs also declare they are EDMG STAs through the DMG Parameters field that is transmitted in Beacons. Instruct the Editor to make a global change in the 802.11ay draft from "non-AP or non-PCP EDMG STA" to "non-AP EDMG STA or non-PCP EDMG STA" 1204 Adrian Stephens 9.4.2.250.1 "Each Extended Capabilities field is structured as defined in Figure 28." Congratulations on the subelement. However, if you do use the sub-element, you avoid creating a novel concept, you re-use the existing concepts about extensibility, and what happens if you encounter an unknown subelement. Replace these fields with "subelements" following the model of the baseline, e.g. in 9.4.2.22.14. 1207 Adrian Stephens 9.4.2.250.4 "PHY Capability field" - this is an over-general field name, as it is specific to EDMG STAs Insert "EDMG" in the name of the field. Ditto for all the subfields of the EDMG capabilities element.
definition of Segmentation and Reassembly ield Definition Encoding Maximum Segmented MSDU Exponent Indicates the maximum MSDU size supported when segmentation and reassembly is enabled. This subfield is an integer in the 0 to 9. The maximum segmented MSDU size that is defined by this subfield is equal to: 2 (13 + Maximum Segmented MSDU Exponent) – 1 octets Segmentation and Reassembly Support Indicates whether the STA supports the segmentation and reassembly mechanism as specified in 10.62. 0 – Segmentation and reassembly is not supported 1 – Segmentation and reassembly is supported Instruct the Editor to modify paragraph 7 of Section 9.7.1 as follows: An A-MPDU pre-EOF padding refers to the contents of the A-MPDU up to, but not including, the EOF Padding field. 1272 Yan Xin 9.4.2.250.2 DL MU-MIMO is indicated for data trasnmission when MU-MIMO Supported subfield in Beamforming Capability filed is set to one. It is not clear why UL MU-MIMO Supported subfield is defined. UL MU-MIMO phase is optionally a part of MU-MIMO beamforming. clarify the definition of UL MU-MIMO Supported
A-MPDU Parameters TRN Parameters Supported MCS Reserved Bits: 7 12 24 5 —Core Capabilities field format The A-MPDU Parameters field is defined in Figure 30. The definition of the subfields of the A-MPDU Parameters field is shown in Table 5. B0 B3 B4 B6 Maximum Length Exponent Minimum Start Spacing Bits: 4 3 —A-MPDU Parameters field format Parameters field definition Subfield Definition Encoding Maximum A-MPDU Length Exponent Indicates the maximum length of A-MPDU that the STA can receive. This subfield is an integer in the range 0 to 9. The length defined by this subfield is equal to: 2(13 + Maximum A-MPDU Length Exponent) – 1 octets. Minimum MPDU Start Spacing Determines the minimum time between the start of adjacent MPDUs within an A-MPDU that the STA can receive, measured at the PHY SAP. Set to 0 for no restriction Set to 1 for 8 ns Set to 2 for 16 ns Set to 3 for 32 ns Set to 4 for 64 ns Set to 5 for 128 ns Set to 6 for 256 ns Set to 7 for 512 ns The TRN Parameters field is defined in Figure 31. B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 TP1 TP4 TN2 TN4 TN8 RP1 RP4 RN2 RN4 RN8 Short TRN Long TRN Bits: 1 1 1 1 1 1 1 1 1 1 1 1
No objection – Mark Ready for Motion CID 1042 (GEN) Review Comment Proposed Resolution: REJECTED (GEN: 2018-04-10 20:46:32Z) at 158.31 "40MC HT STA" is a defined term and is valid for the definition of 40MC HT STA 2G. No change to the definition is required No objection – Mark ready for motion Review Document 11-18/669r0 – Mark HAMILTON < > CID 1398 (MAC) Review Comment Review context 2280.60 In case of OMN, STA send OMN frame, or include OMN element in Beacon. In case when OMN is not supported, STA could send Notify Channel Width frame, or change the STA Channel Width field in the HT Operation element. Proposed resolution: Revised; Replace the cited note with: “A Notify Channel Width frame or the STA Channel Width field in the HT Operation element is used to signal STA operating channel width changes to and from STAs that are not operating mode notification capable. (Note to editor: clause 11.40”) No objection – Mark Ready for motion CID 1425 (MAC) Review comment Review discussion Proposed Resolution: Accept No objection – Mark Ready for Motion CID 1381 (MAC) Review Comment Review discussion Proposed Resolution: Accept No Objection – Mark for Motion CID 1382 (MAC) Review Comment Review Discussion Proposed Resolution: Rejected. For dot11BSSTransitionActivated to be true, logically, dot11BSSTransitionImplemented must also be true without needing to state so. No Objection – Mark Ready for Motion CID 1390 (MAC) Review Comment Review discussion Proposed Resolution: Accept - Note to Editor the change is at P1063L48 No Objection – Mark Ready for Motion Additional CIDs CID 1534 (GEN) Review Comment Proposed Resolution: REJECTED (GEN: 2018-04-10 21:31:59Z) the result of a FILS setup yields a PMKSA which can be used with caching. No Objection – Mark Ready for Motion CID 1574 (GEN) Review Comment
IEEE P802.11 Wireless LANs CIDs related to Random Access – Part 1 Date: January 2, 2018 Author(s): Name Affiliation Address Phone email Abhishek Qualcomm Inc. appatil@qti.qualcomm.com Alfred Asterjadhi Qualcomm Inc. aasterja@qti.qualcomm.com George Cherian Qualcomm Inc. gcherian@qti.qualcomm.com Abstract This submission proposes resolutions for following CID received for TGax LB230 (16): 13196, 11992, 14208, 12224, 14210, 13198, 11001, 11364, 12178, 11731, 11732, 12179, 11045, 13796, 11379 Revisions: Rev 0: Initial version of the document. 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. CID Commenter Pg / Ln Section Comment Proposed Change Resolution Abhishek 257.12 27.5.5 A UORA STA to set the to true As in comment Revised Agree with the comment. TGax editor, please make changes as shown in doc 11-17/1849r0 that are marked with CID 11033 13196 Rajesh Kumar 257.15 27.5.5 An HE STA that supports UORA shall set the to true Add the following sentence at the end of the first paragraph: "An HE STA that sets the UL OFDMA RA Support subfield in the HE Capabilities element to 1 shall set to true." Revised Agree with the comment. TGax editor, please make changes as in doc 11-17/1849r0 that are marked with CID 13196
IEEE P802.11 Wireless LANs Resolution for CID 1501 Back off timer Date: 2018-04 Author(s): Name Affiliation Address Phone email Graham SMITH SR Technology Davie, FL, USA. 916 799 9563 gsmith@srtrl.com CID Commenter Clause Page Line Comment Proposed 1501 Mark Rison "backoff timer" is confusing since it's not really a timer, it's just a counter (and indeed there are a number of "backoff counter"s). The "backoff counter" should be referenced instead, and then it's not that it expires but that it is/reaches zero Change all the instances of "backoff timer" throughout the draft to "backoff counter" In document 17/0987r11 we had CID Commenter Clause Page Line Comment Proposed 294 Mark RISON 10.3.3 Is the backoff timer in units of slots or in units of time (multiples of aSlotTime)? For example, Equation indicates the backoff time (or Backoff Time) is in units of time, but at 1351.61 the backoff timer is "decremented" and 1351.8 says the backoff timer has a value measured in "backoff slots" Be consistent. It's probably easiest if the backoff timer is something that counts in units of slots 189 10.22.2.4 1486.27 “backoff timer” is confusing since it is not really a timer, it’s just a counter (and indeed there are a number of “backoff counters) Change all instances of “backoff timer” in the draft to “Backoff counter” The resolution was to change the formula “Backoff Timer”to “Backoff Counter”. Equation 10-1 was changed to be Backoff Count = Random () and everywhere we had backoff timer we replaced with backoff count, or so we thought. So theoretically this comment 1501 should have been satisfied by CIDs 294 and 189. BUT
IEEE P802.11 Wireless LANs CIDs 1388 and 1359 Date: 05/07/2018 Author(s): Name Affiliation Address email Sigurd Schelstraete Quantenna sschelstraete@quantenna.com Abstract This submission proposes resolutions for CIDs 1359 and 1388 Introduction 1359 19.3.4 2755 58 Figure 19-3 says that "When STBC is used, the STBC block has more outputs than inputs." but the figure shows the opposite (the STBC block has 4 inputs and 4 outputs) Delete the cited text in the referenced figure 1388 19.3.5 2759 25 "An HT AP that is not a VHT AP shall support all EQM rates for two spatial streams (MCSs 8 to 15) using a 20 MHz channel width." -- there is no reason a VHT AP should be inferior to an HT AP Delete "that is not a VHT AP" in the cited text at the referenced location
There is no distinction between AP and non-AP STAs in this. Therefore, a compliant VHT STA only has to support a single Spatial Stream, regardless of whether it is a STA or an AP. Since every VHT STA is an HT STA by definition, it appears that the standard needs to make a disctiction between the capabilities of HT APs that are VHT APs and HT APs that are not. As such, the requirement on page 2759, line 25 looks intentional. Proposed Resolution Reject the comment as the statement on page 2759, line 25 is needed to guarantee consistency with the mandatory requirements of VHT STAs. Comment Proposed Change Resolution 1388 19.3.5 2759 25 "An HT AP that is not a VHT AP shall support all EQM rates for two spatial streams (MCSs 8 to 15) using a 20 MHz channel width." -- there is no reason a VHT AP should be inferior to an HT AP Delete "that is not a VHT AP" in the cited text at the referenced location Reject. This statement is needed to guarantee consistency with the mandatory requirements of VHT STAs.
IEEE P802.11 Wireless LANs CR on CIDs for 10.39.9.4 (Group Beamforming) Date: 2018-04-18 Author(s): Name Affiliation Address Phone email James Wang Mediatek James.wang@mediatek.com Xiaofei Wang Interdigital Xiaofei.wang@interdigital.com CID Comment Proposed Change Resolution 1202 Adrian Stephens (Editorial) The Length column should have units after the values. (Technical) The change of GroupPairIndex(0) to 8 (unspecified units, presumably bits) from the existing 6 bits makes existing compliant 802.11ad devices in the future, and will not enable old spec and new spec devices to interoperate. Remove these changes. If additional size it needed for these fields, find a backwards compatible way to implement it, e.g. by defining a new element for the purpose. Revised. Instruct the editor to add units (bits) to length column in 9.4.2.146. To address commenter concern of backward incompatibility, the OFDM mode is removed from 11ad and there should not be any legacy 11ad device implement OFDM or DTM. 1906 Oteri For group beamfoming, line 17 and line 22 are in conflict. One says DTI and the other says BTI Fix conflict. Should be BTI Accepted. Instruct the editor to change DTI to BTI in line 10, Page, clause 10.38.9.4 of Draft 1.1
IEEE P802.11 Wireless LANs CR on CIDs for 10.39.9.4 (Group Beamforming) Date: 2018-04-18 Author(s): Name Affiliation Address Phone email James Wang Mediatek James.wang@mediatek.com Xiaofei Wang Interdigital Xiaofei.wang@interdigital.com CID Comment Proposed Change Resolution 1202 Adrian Stephens (Editorial) The Length column should have units after the values. (Technical) The change of GroupPairIndex(0) to 8 (unspecified units, presumably bits) from the existing 6 bits makes existing compliant 802.11ad devices in the future, and will not enable old spec and new spec devices to interoperate. Remove these changes. If additional size it needed for these fields, find a backwards compatible way to implement it, e.g. by defining a new element for the purpose. Revised. Instruct the editor to add units (bits) to length column in 9.4.2.146. To address commenter concern of backward incompatibility, the OFDM mode is removed from 11ad and there should not be any legacy 11ad device implement OFDM or DTM. 1906 Oteri For group beamfoming, line 17 and line 22 are in conflict. One says DTI and the other says BTI Fix conflict. Should be BTI Accepted. Instruct the editor to change DTI to BTI in line 10, Page, clause 10.38.9.4 of Draft 1.1 1408 Oteri In the first paragraph, it says group beamforming takes place in the DTI of a beacon interval. However, the second paragraph indicates it is performed in BTI because it is done by appending TRN-R subfields within the TRN field of a DMG Beacon frame transmitted in a Please clarify. Rejected. Resolve in CID1906.
different antennas as defined in 30.4.6.2." 1379 10.36.11.4.3 "The DMG CTS frame should be transmitted using all SU-MIMO sectors, with a small delay between each sector" - extremely opaque. Small delay is undefined, also sectors are undefined. replace with "The DMG CTS should be transmitted using the same set of atennas and antenna settings planned to be sued during the SU-MIMO transmission and a CSD between the transmission in different antennas as defined in 30.4.6.2." 1409 10.36.11.4.3 The "small delay" needs to be clarified. Similar to what is defined in MU-MIMO case, maybe just call it antenna setting. See the advice provided in comment. 1681 10.36.11.4.3 What is a "small delay"? This needs to be defined Define small delay. 1897 10.36.11.4.3 Editor Note: what is a "small delay"? This needs to be defined. Address editor comment 2005 10.36.11.4.3 It is not clear for "with a small delay between each sector". If "small delay" refers to CSD, need to refer to the related subclause. Please clarify it. 2182 10.36.11.4.3 calls out small delay between each sector in text. Small delay not defined. Define "Small delay”. See note to editor. 2338 10.36.11.4.3 Please remove delay" per Editor's Note. Please replace delay" with a specific value or range of values. Proposed resolution: Accept the proposed resolution in CID 1378, and see the proposed draft text in this document. CID Clause Comment Proposed change 1405 10.36.11.4.4 Similar to what is described in channel access procedure section, here in MU-MIMO channel access procedure section, the use of Grant/Grant Ack frame before the channel access initiation should also be stated. Particularly for those STAs whose Grant Required field within the EDMG Capabilities element is set to 1. Add statements similar to the first three paragraphs in the SU-MIMO channel access procedure section to describe the use of Grant/Grant Ack frame. MIMO MIMO
different antennas as defined in 30.4.6.2." 1379 10.36.11.4.3 "The DMG CTS frame should be transmitted using all SU-MIMO sectors, with a small delay between each sector" - extremely opaque. Small delay is undefined, also sectors are undefined. replace with "The DMG CTS frame should be transmitted using the same set of atennas and antenna settings planned to be sued during the SU-MIMO transmission and a CSD between the transmission in different antennas as defined in 30.4.6.2." 1409 10.36.11.4.3 The delay" needs to be clarified. Similar to what is defined in case, maybe just call it antenna setting. See the advice provided in comment. 1681 10.36.11.4.3 What is a "small delay"? This needs to be defined Define small delay. 1897 10.36.11.4.3 Editor Note: what is a delay"? This needs to be defined. Address editor comment 2005 10.36.11.4.3 It is not for "with a small delay between each sector". If "small delay" refers to CSD, need to refer to the related subclause. Please clarify it. 2182 10.36.11.4.3 calls out small delay between each sector in text. Small delay not defined. Define "Small delay”. See note to editor. 2338 10.36.11.4.3 Please remove "small delay" per Editor's Note. Please replace delay" with a specific value or range of values. Proposed resolution: Accept the proposed resolution in CID 1378, and see the proposed draft text in this document. CID Clause Comment Proposed change 1405 10.36.11.4.4 Similar to what is described in channel access procedure section, here in MU-MIMO channel access procedure section, the use of Ack frame before the channel access initiation should also be stated. Particularly for those STAs whose Grant Required field within the EDMG Capabilities element is set to 1. Add statements similar to the first three paragraphs in the SU-MIMO channel access procedure section to describe the use of Grant/Grant Ack frame. MIMO MIMO
Proposed resolution: Revised, and see the proposed text in this document. CID Clause Comment Proposed change 1406 10.36.11.4.3 "The control trailer also indicates the corresponding DMG antenna configuration for the upcoming transmission or hybrid beamforming."---Table 52 defines the TX Sector Combination Index that indicates the TX sector combination and the corresponding RX AWVs to be used in the following SU-MIMO transmission. Here it should be explicitly pointed out that this field will be used. Explicitly states that the "TX Sector Combination Index" field in the control trailer will be used. Proposed resolution: Revised, and see the proposed text in this document. CID Clause Comment Proposed change 1407 10.36.11.4.4 Except for the EDMG Group ID field, the MU-MIMO Transmission Configuration field Type and Transmission Configuration Index field in the Control Trailer shall also be set accordingly, since as defined in 9.4.2.262, a MU group associated with an EDMG Group ID can have multiple different configuration indexes. Add corresponding statements the mentioned fields in comment apart from EDMG Group ID. Proposed resolution: Revised, and see the proposed text in this document. CID Clause Comment Proposed change 1475 10.36.11.4.2 This phrase makes no sense. "that sensed at least all the MIMO TX antennas was BUSY." "At least all" would seem to mean the same as "all". Is that what is meant? Change "all" to "one". MIMO
CID Clause Comment Proposed change 1655 10.36.11.4.4 there seems no carrier sensing from the client side for the MU-MIMO channel access before sending back DMG CTS. It might be better to explicitly spell this out. Is it safe for the clients? Please clarify Proposed resolution: Revised, and see the proposed text in this document. CID Clause Comment Proposed change 1782 10.36.11.4 MIMO set up procedure for TDD channel access is not defined. We have to define a procedure to enable without immediate response. Please consider to define MIMO setup procedures for TDD channel access. Discussion: The CTS-to-self without response option defined in MU-MIMO channel access procedure enables MU-MIMO channel access within a TDD SP. We can also enable the CTS-to-self without response option in SU-MIMO channel access procedure to enable SU-MIMO channel access within a TDD SP. Proposed resolution: Revised, and see the proposed text in this document. CID Clause Comment Proposed change 1783 10.36.11.4 Subclause 10.36.11.4.2 talks about MIMO channel access rules. It seems that all rules described here are assuming the MIMO is used in CBAP. There should be some description specifying how EDMG STA shall use MIMO in SP. Please add MIMO channel access rules for SP. 2292 10.36.11.4.3 Whether this Grant frame can be sent in a SP? In 9.5.2, it is required to set such Grant frame with RA=broadcast address. However, the information in CT is only meaningful if it is addressed to a specific (group of ) STA Clarify in what type of allocation this procedure can happen, or modify 9.5.2 to allow this procedure in a SP Discussion: The existing MIMO channel access procedures should also be applicable to SP.