zilongwang/ReadingBank huggingface dataset:
Average class size has increased to 19.2 in Spring 2011. We added three new adjunct faculty in 2010-2011 and one additional faculty for the Fall of 2011. Section III: Assessment of Outcomes The Program Outcomes for this program are listed below. At least one-third of your program outcomes must be assessed as part of this Annual Update, and across the next three years all of these program outcomes must be assessed at least once. Mental Health Technology Program Outcomes In which courses are these program outcomes addressed? Which of these program outcomes were assessed during the last fiscal year? Assessment Methods Used 1) Accurately gather information through clinical interviews and observation. MHT 201 Mean scores for intake and Rubric administered to practicum supervisor 2) Assess and prioritize client needs. MHT 204 Assessed in last fiscal Year 2011-2012 Rubric administered to practicum supervisor 3) Plan effective intervention strategies. MHT 204 Plan to Asses Rubric administered to practicum supervisor 4) Demonstrate interventions to meet client needs. MHT 204 Plan to Assess Rubric administered to practicum supervisor 5) Establish/maintain effective therapeutic relationships with others. MHT 202, 203 and 204 Rubric administered to practicum supervisor 6) Demonstrate professional and ethical practice with a sensitivity to and respect for cultural, ethnic, and life style differences. MHT 204 Rubric administered to practicum supervisor 7) Demonstrate effective self awareness and self-management. MHT 204 Assessed in last fiscal year 2010-2011 Rubric administered to practicum supervisor and 2012
2011 Graduates 2010 Graduates 2009 Graduates 2008 Graduates Certification CRT 18/18 (100%) 30/30 (100%) 23/23 (100%) 25/25 (100%) Written RRT 11/13 (84.6%) 28/28 (100%) 21/21 (100%) 22/24 (91.7%) Clinical Simulation RRT 10/13 (76.9%) 27/28 (96.4%) 20/21 (95.2%) 21/22 (95.5%) Overall Employer Satisfaction TBD 95.8% 94.4% 88.8% Overall Graduate Satisfaction TBD 100% 100% 88% Positive Placement within 6 mos. 89% 96.7% 78.3% 88% On-time Graduation Rate 84.6% 87.1% 80.8% 86.4% Attrition by Starting Cohort TBD 19% 55.3% 27.9% Interpretation and Analysis of Trend Data Included in the Section Above Suggestions of questions that might be addressed in this section: What trends do you see in the above data? Are there internal or external factors that account for these trends? What are the implications for the program or department? What actions have the department taken that have influenced these trends? What strategies will the department implement as a result of this data? Attrition continues to be the primary problem area of our program despite a variety of strategies over the past several years. As the admissions process changes to a competitive format, we hope retention will be greatly improved. Section II: Progress Since the Most Recent Review What was the fiscal year of the most recent Program Review for this program? (The most recent Program Review self-study can be found at ). 08-09
DEVELOPMENTAL DISABILITIES ADMINISTRATION (DDA) Enhanced Case Management Referral Consideration CLIENT’S NAME AGE ADSA ID NUMBER CRM NAME ECMP CARE ASSESSMENT TRIGGERED REFERRAL? No Yes DATE REPORTING UNIT / OFFICE CRM SUPERVISOR Does client live with paid caregiver OR is client largely dependent on a paid caregiver in home? No (not eligible) Yes (continue) Name of paid caregiver: Is the client always able to supervise caregiver? (CARE Decision making screen) No Yes Who is designated to supervise the paid caregiver? Does client have communication barriers and few community contacts? No Yes Comments: Does client have additional paid or unpaid services that would provide additional oversight in the person’s home? No Yes Waiver: List authorized services in PCSP: Are there Adult Protective Services (APS) or Child Protective Services (CPS) referrals in the past year? No Yes Comments (enter dates / results): Are there concerns about the home environment that may jeopardize the client’s health and safety or quality of care? No Yes Comments: Does the client have a Person Centered Goal identified in the Finalized Plan? No Yes Comments: Provide additional information the client challenging behaviors, medical concerns, unresolved issues, etc.), and/or provider concerns (contract, training, quality of care). Comments:
TABLE r. 6 Column 1 Drug Column 1A (Large Commercial Quantity) Quantity Column 1B (Large Commercial Quantity) Quantity of mixture of substance and drug of dependence Column 2 (Commercial Quantity) Quantity Column 2A (Commercial Quantity) Quantity of mixture of substance and drug of dependence Column 2B (Automatic Forfeiture Quantity) Quantity Column 3 (Traffickable Quantity) Quantity of mixture of substance and drug of dependence Column 3A (Traffickable Quantity) Quantity Column 4 (Small Quantity) Quantity (common name AM–694) 10·0 kg 1·0 kg 3·0 g 1·0 g (common name JWH–250) 10·0 kg 1·0 kg 3·0 g 1·0 g (common name JWH–200) 10·0 kg 1·0 kg 3·0 g 1·0 g (common name JWH–073) 10·0 kg 1·0 kg 3·0 g 1·0 g (common name JWH–122) 10·0 kg 1·0 kg 3·0 g 1·0 g
Appendix C. Amendment Raffle Slips No state may violate equal rights of conscience, the press, or trial by jury in criminal Freedom of Religion Freedom of Speech Freedom of Press Right of Assembly Right to Petition No ex post facto law except for those that apply to criminal law Wild Card (find contemporary support for a new amendment not previously proposed) Right to Keep and bear arms Protection from quartering of troops Right to be secure in one’s person Right to Due Process Trial Rights (fair, public, speedy trial, right to counsel, confronted by witnesses, alerted of charges) Protection from Cruel and Unusual Punishment to protections that are not explicit in the Constitution
Minimum Service Interval S Nominal MSDU size/mean data rate, if specified (VoIP typically uses this) Maximum Service Interval S ) Inactivity Interval Always specified Suspension Interval Minimum Data Rate be specified if peak data rate is specified Equal to mean data rate X Mean Data Rate S S S Size X X S Minimum PHY Rate Always specified Table N-1—Admissible TSPECs (continued) parameter Continuous time QoS traffic (HCCA) Controlled- access CBR traffic (HCCA) Bursty traffic (HCCA) Contention- based traffic (EDCA) Peak Data Rate be specified if Minimum Data Rate Specified Equal to Mean Data Rate Delay Bound S S Surplus Bandwidth Allowance S S Medium Time (not specified by non-AP STA; only an output from the HC)
That IEEE P802.11 Wireless LANs Modification to the Amendment Text of adaptive ANQP element provisioning in the beacon Date: 2013-01-02 Author(s): Name Affiliation Address Phone Email George Calcev Huawei Technologies Co. Ltd. Lin Cai Huawei Technologies Co. Ltd. Lin.Cai@huawei.com Eric Zhang Huawei Technologies Co. Ltd. 8.3.3.2 Beacon frame format Information Notes ANQP_List_IE ANA One or multiple ANQP information elements are provided if many GAS requests are received for the specific ANQP IE and dot11InterworkingServiceActivated is true and dot11AdaptiveANQPBeaconElement is true 8.4.2 Information elements 8.4.2.1 General Instructions to Editor: Append the Clause 8.4.2.1 with the following text: Table 8-54ai—Element IDs Element Element ID Length of indicated element (in octets) Extensible ANQP_List_IE ANA 0-255 yes 8.4.2.121 ANQP_List IE element The ANQP_List_IE information element includes one or more ANQP element values for which IDs are specified in Table 8-184ai01—ANQP-element definitions, The format of the ANQP_List_IE information element is presented in Figure 8-401 Element ID Length ANQP Info ID Value … ANQP Info ID Value Octets 2 2 1 Variable
Pilot Index \ Pattern Index 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 -122 -118 -114 -110 -106 -102 -98 -94 -120 -116 -112 -108 -104 -100 -96 -92 1 -90 -86 -82 -78 -74 -70 -66 -62 -88 -84 -80 -76 -72 -68 -64 -60 2 -58 -54 -50 -46 -42 -38 -34 -30 -56 -52 -48 -44 -40 -36 -32 -28 3 -26 -22 -18 -14 -10 -6 -2 2 -24 -20 -16 -12 -8 -4 2 4 4 6 10 14 18 22 26 30 34 8 12 16 20 24 28 32 36 5 38 42 46 50 54 58 62 66 40 44 48 52 56 60 64 68 6 70 74 78 82 86 90 94 98 72 76 80 84 88 92 96 100 7 102 106 110 114 118 122 120 -120 104 108 112 116 120 122 -2 -122 R.3.7.D: Modulation of the traveling pilots [Nov 2012 meeting minutes, 11-12/1322r0] For single space time stream, traveling pilots in data field are modulated the same way as fixed pilots in data field (with the exception of boosting by a factor of 1.5). For STBC, the traveling pilots tones across two consecutive data symbols are modulated the same way as the data tones in LTF. 3.8 Timing-Related Constants R.3.8.A: The draft specification shall include the following timing-related constants: [Nov 2012 meeting minutes, 11-12/1363r1] Parameter CBW1 Description NSD 24 Number of data subcarriers per OFDM symbol NSP 2 4 6 8 Number of pilot subcarrier per OFDM symbol NST 26 number of useful subcarriers per OFDM symbol NSR 13 Highest data subcarrier index per OFDM symbol F 31.25 kHz Subcarrier frequency spacing TDFT 32 s = 1/F IDFT/DFT period TGI 8 s = TDFT/4 Guard interval duration TDGI 16 s Double guard interval TSGI 4 s = TDFT/8 Short guard interval duration
“Oo, diba nga nabasa mo naman yung nakasulat dun sa 3rd letter? Diba ang sabi do something new daw! Eto, new ‘to! I’m joining a new club at alam mo namang never kong natry magtaekwando diba? I think this would be cool!” “I this would be a disaster! You can’t even open a cap of a bottled ketchup what more kung makikipagbugbugan ka pa dyan sa mga taekwando students! Baka mabalian ka lang!” tawa pa rin sya ng tawa. Tinignan ko sya ng masama at sarcastic na sinabi, “Napakasupportive mong kaibigan.” Mamamatay na ata sa kakatawa si Kate, “Eh kasi naman bakit hindi ka na lang sumali sa club ko? Dun ka na lang sa club ko.” “Heh. Mas prefer ko pang mabalian ng buto sa taekwando kesa magsayaw! Alam mo namang balu-baluktot ang paa ko! Mas mamamatay pa ako sa pagsasayaw kesa sa pagta-taekwando!” “Sige na nga, bahala ka. Basta paalala lang, ilagay mo na sa speed dials mo ang 911.” “Heh! Umalis ka na nga dito! Dumiretso ka na sa club mo, tignan mo nga kung oras na. Iniintay ka na ng mga club members mo!”
“Teka, teka. Ikaw nga dyan hindi nagsasabi ng mga bagay na matino eh, I asked you properly if you're James' blind date. Now, I don't want to hear silly jokes.” Tinaasan ko sya ng “Silly jokes? Who was kidding with whom? Ewan ko sayo basta wala akong kilalang James.” Hindi sya convinced sa sinabi ko, nagdial sya sa phone nya at ilang segundo lang eh tumunog yung cellphone ko. “See?” “What?!” I am a bit panicky. “It's not impossible that you know James 'coz he gave me your number, “ Ewan ko, may mali dun sa phrase nya na sobrang ikinainis ko, “Ah ganun? When you received it, did you not even realize that it was my number before calling? This is unfair, ako all this time, saulo ko number mo pero ikaw, you don't even recognize my number?”
IEEE P802.11 Wireless LANs Minutes for TG Teleconferences April 2013 Date: 2013-04-19 Author(s): Name Affiliation Address Phone email Dorothy Stanley Aruba Networks 1322 Crossman Ave Sunnyvale, CA 94089 +1-630-363-1389 Jon Rosdahl CSR Technology Inc 10871 N 5750 W Highland, UT 1-801-492-4023 Minutes for the TG REVmc Telecon for April 5, 2013 Proposed Agenda – Apr 5, 2013: Call to order, Patent Policy, Attendance Editor Report Comment Resolution - review available resolutions, MAC+GEN comment assignments, if needed AOB Adjourn Called to order by Dorothy Stanley, Chair of TG REVmc at 10:02 am; no agenda changes. Call for Patents - Review Patent Policy and Meeting Policy Identified Attendance: Dorothy STANLEY, Aruba; Adrian STEPHENS, Intel; Mark HAMILTON; Carlos ALDANA, Qualcomm. Editor Report – Adrian Stephens defect resolution underway, mainly editorial; reviewers have identified additional technical changes; consider those changes either before or as submitted comments on the next ballot. plans to have a draft incorporating the editorial defects and approved editorial comments soon – D1.3. will incorporate approved technical comments, available before the May meeting. edits re: MPPDU are still in the draft. Comment Resolution comment resolutions available in . Includes CIDs 1263, 1269, 1392, 1480, 1694, 1703, 1704, 1705, 1706, and in . Includes CIDs 89, 1008, 1134, 1135, 1424. to begin with 11-13-391-00 comments, then 11-13-0361-03 comments. CID 1263: Agree with proposed Accept. CID 1269: Agree with proposed Revised. CID 1392: Agree with proposed Revised. CID 1480: Agree with Reject. Discussion – does 11ac change the restriction? Add reference to 11ac text. Modify reject reason, adding “Note that in 11ac D5.0 P77L8, the restriction to is within a Sub-band triplet sequence” are not used within the same Subband Triplet Sequence field”. Can have overlapping between two sub-band triplet sequences.”
Change from “5-n” to “5” “n+1” to “6” “n+2” to “7” “n+3” to “8” “n+4” to “9” “n+5” to “10” For 8-202—ADDTS Response frame Action field format, At 813.51 Change from “7-n” to “7” “n+1” to “8” “n+2” to “9” “n+3” to “10” “n+4” to “11” And for 8-205—QoS Map configure frame body 815.17, Change from “3-n” to “3” CID 1043 1043 845.03 8.5.8.18 Figure 8-475 QMF Policy element length should include 0 as a valid length in the case when it is absent. replace "3-257" with "0 or 3-257" Discussion: The comment is on the length value shown for the QMF Policy element, currently 3-257. The commenter proposes to change from “3-257” to “0 or 3-257” as the field is optional. Agree with the commenter. Proposed resolution: Accepted CID 1059 1059 1022.45 9.21.10.3 References to 9.13 and 9.3.2.5 at the location are probably wrong. Correct them Discussion: The comment is on the following text, the references to 9.13 and 9.3.2.5:
IEEE P802.11 Wireless LANs Proposed TGah Draft Amendment Date: 2013-05-13 Author(s): Name Affiliation Address Phone email Eric Wong Broadcom Matthew Fischer Broadcom 190 Mathilda Place, Sunnyvale, CA +1 408 543 3370 Nihar Jindal Broadcom Ron Porat Broadcom Vinko Erceg Broadcom Hyoungjin Kwon ETRI Jae Seung Lee ETRI Jaewoo Park ETRI Cheong ETRI 138 Gajeongno, Dajeon, Korea +82 42 860 5635 Sok-kyu Lee ETRI Betty Zhao Huawei Bin Zhen Huawei David Yangxun Huawei George Calcev Huawei Rolling Meadows, IL USA Osama Aboul Magd Huawei Young Hoon Kwon Huawei Chin Keong Ho I2R Haiguang Wang I2R Li Chia Choo I2R Shoukang Zheng I2R 1 Fusionopolis Way, Connexis Tower, Singapore 138632 +65-6408 2000 Sumei Sun I2R Wai Leong Yeow I2R Yuan Zhou I2R Zander Lei I2R 1 Fusionopolis Way, Connexis Tower, Singapore 138632 +65-6408 2000 Zhou Yuan I2R Eldad Perahia Corp. Emily Qi Intel Corp. Minyoung Park Intel Corp. 2111 NE 25th Ave. Hillsboro, OR 1 503 712 4705
CID Page Clause Comment Proposed Change Proposed Resolution 10159 90.55 8.4.2.56 Figure 8-246a is the format of the Current Operating Class Extension Sequence field and its length is 1+variable octets. This field should fit in the field with the same name in Figure 8-246 but the field there is said to be 1 octet. Change "1" under the "Current Operating Class Extension Sequence (optional)" in Figure 8-246 to "variable". Accepted 10160 90.65 8.4.2.56 The OneHundredAndThirty Delimiter field is no longer extensible from its definition, name, and value. Is this OK? Feels like there is a more straight forward way, such as changing it to be like a sub IE and adding the length information of the Current Operating Class Extension field. As in comment. Rejected. The 130 delimiter is indeed not extensible, but this does not appear to cause a problem. 10161 91.01 8.4.2.56 Here, an explanation of the Current Operating Class Extension field is required, not the Current Operating Class Extension Sequence field. As in comment. Revised. Delete "Sequence" in "Current Operating Class Extension Sequence field". In addition, in Figure 8-246 (Supported Operating Classes element format), in the fourth field, add "es" to "Operating Class". 10162 91.15 8.4.2.56 Figure 8-246b is the format of the Operating Duple Sequence field and its length is 1+2n octets. This field should fit in the field with the same name in Figure 8-246 but the field there is said to be 1 octet. Change "1" under the "Operating Class Duple Sequence (optional)" in Figure 8-246 to "variable". Accepted. 10163 91.24 8.4.2.56 The Zero Delimiter is no longer extensible from its definition, name, and value. Is this OK? Feels like there is a more straight forward way, such as changing it to be like a sub IE and adding the length information of the Operating Class Duple List field. As in comment. Rejected. The 0 delimiter is indeed not extensible, but this does not appear to cause a problem. CID Page Clause Comment Proposed Change Proposed Resolution
IEEE P802.11 Wireless LANs Comment Resolution for Clause 6.5 Date: 2013-05-30 Author: Name Affiliation Address Edward Au Huawei Technologies 303 Terry Fox Drive, Suite 400, K2K 3J1 Kanata Ontario This submission presents proposed resolution to CIDs 10224, 10065, and 10226. Changes indicated by a mixture of Word track-changes and instructions. R1 – Proposed resolutions for CIDs 10065 and 10226 are revised during the call on May 23. R2 – Proposed resolution for CID after an offline discussion with Allert Van Zelst. R3 – Minor fixes on the proposed resolution for CID 10224. R4 – Proposed resolution for CID 10224 is revised during the call on May 30. CID 10225 CID Clause Page Line Comment Proposed Change 10225 6.5.4.2 24 26 This list of exceptions is getting rediculous. Just replace all the "is not used" exceptions with one sentence that not all parameters are used by all PHY (Maybe this has to be done by TGmc.) Replace "The parameter aMPDUDurationFactor is not used by all PHYs defined within this standard. The parameters aSignalExtension, aRIFSTime, aSymbolLength, aSTFOneLength, aSTFTwoLength, aLTFOneLength, aLTFTwoLength, aPLCPSigTwoLength, aPLCPServiceLength, aPLCPConvolutionalTailLength, aMPDUDurationFactor, aMPDUMaxLength, aPSDUMaxLength, aPPDUMaxTime, aIUSTime, aDTT2UTTTime, and aMaxCSIMatricesReportDelay are not used by all PHYs defined within this standard. Not every PHY in this standard uses the parameters aTxPLCPDelay, aRxPLCPDelay, aTxRFDelay, aRxRFDelay, aTxPHYDelay, aRxPHYDelay, aTxPmdTxStartRFDelay, aTxPmdTxStartRMS,
[NAME] [TITLE] [MAILING ADDRESS] [PHONE NUMBER] June 24, 2013 EXECUTIVE SUMMARY [TO BE ADDED] I. 4 II. 6 III. U-NII 7 IV. U-NII-2 U-NII-3 DFS TDWR 11 A. DFS TDWR – 12 B. 16 V. 18 A
[SUMMARIZE REPLY COMMENT HERE] In this comment, IEEE 802.11 will discuss: in Section II, IEEE 802.11 and its members are prepared to assist the Commission in order to begin to resolve the issues in this important docket. We believe the Commission can and should issue its first Report and Order in this proceeding in the fourth calendar quarter of this year or soon thereafter. Because the enabled by IEEE 802.11 are global, we are mindful of the important precedent that the Commission will be setting for other regulators around the world. The explosive growth that we are witnessing in the use of 802.11 radio local area networks (RLANs) requires prompt and thoughtful regulatory action to frame the debate for regulators everywhere. Accordingly, we find suggestions that the Commission do nothing unless and until there is a change in ITU regulations to be ill-informed. As the record amply demonstrates, 802.11 technology is too important to consumers, businesses, service providers, and to national economies, to delay. Spectrum rules that best enable the next generation of .11 technology, and which will meet the rising tide of consumer and business demand, are essential as 802.11 RLANs become the primary on and off ramp to the Internet. Unlicensed devices are playing an role in meeting wireless data needs For the Commission to dedicate resources to a proceeding as wide-ranging and technical as this one, there needs to be a motivating driver. IEEE 802.11 asserts that the Commission look no further than the comments. Filing after filing reveals breathtaking advancements in how technology enabled by standards is being utilized. While the record is extensive, IEEE 802.11 wishes to call out a few of the most salient points:
randomly chosen from [-20,20] ppm with a uniform distribution. Uplink multi-user simulations for all comparisons except offset compensation shall be run using a fixed carrier frequency offset selected from the array [N(1) ,N(2),……,N(16) ], relative to the receiver, where N(j) corresponds to the frequency offset of the j-th client and is randomly chosen from [-2,2] KHz with a uniform distribution. IM3 Phase noise The phase noise will be specified with a pole-zero model. PSD(0) = -100 dBc/Hz pole frequency fp = 250 kHz zero frequency fz = 7905.7 kHz Note, this model results in PSD(infinity) = -130 dBc/Hz Note, this impairment is modeled at both transmitter and receiver. Unchanged from 802.11n IM4 Noise figure Input referred total noise figure from antenna to output of the A/D will be 10dB. Unchanged from 802.11n IM5 Antenna The TGn antenna configuration at both ends of the radio link shall be a uniform linear array of isotropic antennas with separation of one-half wavelength, with an antenna coupling coefficient of zero. The TGac antennas can be assumed to either be all vertically polarized or a mix of vertical and horizontal polarizations or dual polarization at ±45 degree, as specified in the TGac channel model addendum document [11] Mix of vertically and horizontally polarized antennas or dual polarization at ±45 degree is also considered for TGac devices IM6 Light Effects The fluoroscent light effects specifed in the TGn Channel model shall not be considered for the simulation scenarios. IM7 Timing Uplink Multi-user simulations shall be run using a fixed timing offset selected from the array [N(1) ,N(2),……,N(16) ], where N(j) corresponds to the time offset of the j-th client transmission with respect to a common time reference and is randomly chosen from [-100,100] ns with a uniform distribution PHY link level simulation (placeholder) Comparison criteria (placeholder)
IEEE P802.11 Wireless LANs SB01 resolutions for various comments Date: 2013-07-08 Author(s): Name Affiliation Address Phone email Robert Stacey +1-503-724-0893 CID 10229 CID Page Clause Comment Proposed Change Resolution 10229 2.11 3.1 What is an "associated" MPDU? "Associated" has a definite meaning in 802.11, and this usage doesn't seem to match. Either use another term or delete "associated". Delete "associated" from this definition. ACCEPTED Context with proposed edit aggregate medium access control (MAC) protocol data unit (A-MPDU) subframe: A portion of an A-MPDU containing a delimiter and optionally containing an MPDU.
Scan MLME-SCAN.confirm Semantics of the service primitive Insert the following rows at the end of the second table in this subclause: Name Type Valid range Description IBSS adoption VHT Capabilities As defined in frame format As defined in 8.4.2.160 (VHT Capabilities element) The values from the VHT Capabilities element. The parameter is present if dot11VHTOptionImplemented is true and a VHT Capabilities element was present in the Response or Beacon frame from which the BSSDescription was determined, and not present otherwise. Do not VHT Operation As defined in frame format As defined in 8.4.2.161 (VHT Operation element) The values from the VHT Operation element. The parameter is present if dot11VHTOptionImplemented is true and a VHT Operation element was present in the Response or Beacon frame from which the BSSDescription was determined, and not present otherwise. Adopt
CID 10055 CID Page Clause Comment Proposed Change Resolution 10055 410.30 S Has the MATLAB code in 11-06/ 1714 been checked to see if it runs the latest versions of MATLAB? The reason for asking is that it is 6 years old. Check that this legacy MATLAB code still runs? REJECTED – The commenter has not identified a problem with the In response to the commenter’s question, it is not known whether the code still runs on the latest version of MATLAB.
10239 Hunter, David 3.2 5.07 A "beamforee' is defined as a "beamformee". Very useful. Also, the "as x, as y" form is confusing at best and a definition is not an index , so reference pointers should not be included. Replace "beamformee, as described ... beamforming).F44" with "receiver." Rjected: Beamformee is defined on page 7 in the baseline . Clause 3.2 is specific to 802.11 and can contain references. These references help disambiguate between HT beamformee and VHT beamformee Discussion: It seems CID 10239 refers to the following definition in page 6 line 7 (not page 5) in D5.0: high throughput (HT) beamformee: An HT station (STA) that receives an HT physical layer protocol data unit (PPDU) that was transmitted using a beamforming steering matrix and that supports an HT transmit beamforming mechanism as beamformee, as described in 9.29.2 (HT tTransmit beamforming with implicit feedback) or 9.29.3 (Explicit feedback beamforming). Hunter, David 3.2 6.51 If this "can" does not mean "may", then this statement is completely Physically and logically there can, of course, be multiple things identified as "primary AC" at the same time. So this statement is trying to sneak in a requirement -- that only one primary AC is _permitted_ at a time. Replace this normative use of "can be" with "is", so this statement is only a report that there is only one primary AC at a time. (Though this statement really isn't relevant to the definition of primary AC, so it would be better to delete it.) Revised. Agree with the commenter to remove the second sentence.
IEEE P802.11 Wireless LANs IEEE 802.11 TGac Sponsor Ballot 1 SB01 comment resolutions Date: 10 June 2013 Author(s): Name Affiliation Address Phone email Yasuhiko Inoue NTT 1-1 Hikari-no-oka, Yokosuka, Kanaawa Japan Yusuke Asai NTT 1-1 Hikari-no-oka, Yokosuka, Kanaawa Japan asai.yusuke@lab.ntt.co.jp This document contains a proposed resolution for CID 10132. Revison history: R0 - initial revision CID Page Clause Comment Proposed Change 10132 372.32 B.4.23.2 Static BW operation is mandatory feature and its signaling is carried by non-HT duplicate PPDUs. This inherently suggest that transmission function of non-HT duplicate PPDUs is mandatory for a VHT STA; however, it is not clear whether a VHT STA shall support to transmit non-HT duplicate PPDUs or not. Add a corresponding row for duplicate format to PICS (in B.4.23.2) as well as "VHTP2: VHT format". Discussion: Agreed. As described in 4.3.10a (Very High Throughput (VHT) station (STA)), it is one of the mandatory features for a VHT STA to respond to a bandwidth indication (provided by the RXVECTOR parameters CH_BANDWIDTH_IN_NON_HT and DYN_BANDWIDTH_IN_NON_HT) in a non-HT and non-HT duplicate RTS frame. The responding VHT STA shall respond with a CTS frame carried in a non-HT or non-HT duplicate PPDU after a SIFS period as specified in 9.3.2.6 (CTS and DMG CTS procedure). Therefore, it is appropriate to include the non-HT duplicate format in the PICS.
IEEE P802.11 Wireless LANs TGah D0.1 Comment Collections 9 Resolutions on 24.3.8 Sections Date: 2013-07-15 Author(s): Name Affiliation Address Phone Email Eugene Baik Qualcomm Technologies, Inc. 5775 Morehouse Dr. San Diego, CA 92122 858-658-2568 eugeneb@qti.qualcomm.com Abstract: This document contains proposed resolutions for the following CIDs from TGah D0.1 Comment Collection 9: Clause 24.3.8: 145, 190, 270, 271, 272, 273, 298, 299, 872, 873, 880 CIDs for Clause 24.3.8 CID Section Page Line Comment Proposed Change Resolution 270 Kenichi Mori 239 16 Maybe, section 24.3.8.2.2.1.2 is typo because this section indicates itself. Maybe, correct section is "24.3.8.2.1.2". Accepted 271 Kenichi Mori 24.3.8.3.2 253 52 The section 3.2.1.2 of the SFD indicates "[0.5, -1, 1, -1, -1, ╬│ is a normalization factor - ╬│ = 2.4 for MCS0 rep2, 1.7 otherwise" but this explanation is different. Should be revised as the SFD. [0.5, -1, 1, -1, -1, ╬│ where ╬│ is a normalization factor, ╬│ = 2.4 for MCS0 rep2, 1.7 otherwise. Rejected. The existing notation is equivalent and more accurate in context of the overall STF equation, in that the sum power of the populated tones is 6 (and equal to the number of populated tones) 2
IEEE P802.11 Wireless LANs TGah D0.1 Comment Collections 9 Resolutions on 24.3.8 Sections Date: 2013-07-15 Author(s): Name Affiliation Address Phone Email Eugene Baik Qualcomm Technologies, Inc. 5775 Morehouse Dr. San CA 92122 858-658-2568 eugeneb@qti.qualcomm.com Abstract: This document contains proposed resolutions for the following CIDs from TGah D0.1 Comment Collection 9: Clause 24.3.8: 145, 270, 271, 272, 273, 298, 299, 872, 873, 880 CIDs for Clause 24.3.8 CID Section Page Line Comment Proposed Change Resolution 270 Kenichi Mori 239 16 Maybe, section 24.3.8.2.2.1.2 is typo because this section indicates itself. Maybe, correct section is "24.3.8.2.1.2". Accepted 271 Kenichi Mori 24.3.8.3.2 253 52 The section 3.2.1.2 of the SFD indicates "[0.5, -1, 1, -1, -1, ╬│ is a normalization factor - ╬│ = 2.4 for MCS0 rep2, 1.7 otherwise" but this explanation is different. Should be revised as the SFD. [0.5, -1, 1, -1, -1, ╬│ where ╬│ is a normalization factor, ╬│ = 2.4 for MCS0 rep2, 1.7 otherwise. Rejected. The existing notation is equivalent and more accurate in context of the overall STF equation, in that the sum power of the populated tones is 6 (and equal to the number of populated tones) 2
IEEE P802.11 Wireless LANs Comment Collection 09 MAC CIDs (Comment Resolutions for CC09) Date: 2013-MM-DD Author(s): Name Affiliation Address Phone email Minynoung Park Intel Corporation minyoung.park@intel.com CID Clause Page Line Resn Status Comment Proposed Change Resolution 58 9.32h 145 20 V Details of the UL synch procedure are not defined. Specifically should the STA access SIFS time after the synch frame. What if the STA is unresponsive. Should the AP send a CF-End after PIFS time? If Yes this forces the STA to respond in SIFS time. If not the STA can respond at different times but with other consequances. The simples way is to refer to Reverse direction protocol description in section 9.25 and add support for NDP CTS synch frame as the reverse direction grant frame. Revised – agree in principle on the comment that the details of the UL synch procedure is not define. to changes in under CID 917 heading. 107 9.32h.1 144 63 J In the sentence "When an AP receives a Sync frame from a STA with the Time Slot Protection Request field set to 1, the AP shall protect a time slot that is assigned for the STA in a RAW or a TWT time of the STA with frame exchanges." the signaling for the setting Please indicate the necessary signaling Rejected – Since any frame can be used as a synch frame and there are many ways to set the NAV, it is unneccessry to indicate all possible signalings for the NAV setting.
IEEE P802.11 Wireless LANs Comment Collection 09 MAC CIDs (Comment Resolutions for CC09) Date: 2013-07-13 Author(s): Name Affiliation Address Phone email Minynoung Park Intel Corporation CID Clause Page Line Resn Status Comment Proposed Change Resolution 123 9.19.4a.3 131 43 J How is RAW access under a mixed BSS case? How do different types of STAs access the RAW? Please clarify. Rejected – The comment is invalid. The comment fails to identify a specific issue to be addressed. It fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined. In reply to the commenter, different types of STAs can be allocated to different RAWs so that a RAW is accessed by a same type of STAs. 366 9.19.4a.3 130 32 V Division is unacceptable at this level of MAC operation. Add a field NRAW to the IE Revised – Refer to changes in under CID 366 heading.
Both void AIDs and unassigned valid AIDs can be considered as unassigned AIDs. When RAW is not restricted to STAs whose AID bits are set to 1, if the unassigned AIDs becomes the "holes" in the RAW slot assignement and should not be considered for implicit slot allocation in 9.19.4a.3. The slot assignment for the STA to compute its allocated slot should be modified. TIM element are set to 1, k=0; otherwise k is the number of unassigned AIDs in the RAW group that is smaller than x. If there is no unassigned AID, k=0." to a small number of AIDs, which may have little affect to performance and the unassigned AIDs in the middle of the RAW group can be managed by the AID reassignment. 967 9.19.4a.3 131 63 J To identify the unassigned AIDs, AP may indicate to the STA the unassigned AIDs explicitly. AP may indicate whether to the allocation of the unassigned AIDs e.g. in its capability element of beacon frame. AP indicates the unassigned AIDs in TBD IE. Rejected – The overhead of signaling unassigned AIDs to the STAs in the RAW with a new information element is large. For example, to signal just 5 AIDs, there needs to be at least 5x13bits for unknown gain. Moreover, considering unassigned AIDs within the RAW Group increases the complexity at a STA, which defeats the purpose of implicit slot allocation scheme. The unassigned AIDs can be avoided by utilizing the AID reassignment so that the RAW Group does not have unassigned AIDs.
IEEE P802.11 Wireless LANs Comment Collection 09 MAC CIDs (Comment Resolutions for CC09) Date: 2013-MM-DD Author(s): Name Affiliation Address Phone email Haiguang WANG I2R 1 Fusionopolis Way, #21-01 Connexis (South Tower) Singapore 138632 +65 64082256 hwang@i2r.a-star.edu.sg Zander LEI I2R leizd@i2r.a-star.edu.sg 0 Revision R0: First draft CID Page Line Category Comment Proposed Change Remark 176 64 39 Editorial Paged AID has been defined in 3.1 line 9, the definition of page AID in this subclause is unnecessary. Remove the page ID definition in the paragraph as highlighted. The Encoded Block Information field consists of the Encoding Word Length (EWL) subfield, Length subfield, n AID Differential Values (∆AID) subfields and padding subfield, where n is the number of paged AIDs encoded in the ADE block. The paged AIDs refer to those AIDs with their corresponding bits being set to '1' if encoded by partial virtual bitmap. The format of the Encoded Block Information field is shown in Figure 8-87q (Encoded Block Information (ADE Block)). Accepted – see document IEEE for the resolution 177 65 14 Editorial is a typo in the formula to calculate the Block Offset value Change " floor(AID1 modulo 2048) x 64" to " floor(AID1 modulo 2048) / 64" Accepted – see document IEEE
for the resolution 178 65 50 Editorial Change "inverse bit" to "Inverse Bit Subfield" Change subclause from "When decoding, if inverse bit Inverse Bitmap Field is 1, EWL and Length subfield are zeros, all AIDs in the ADE blocks are paged." Accepted – see document IEEE for the resolution 179 65 54 Editorial Change "inverse bit" to "Inverse Bit Subfield" If inverse bitInverse Bitmap Field is 1, EWL is 7 and Length subfield is 1, all AIDs except one in the ADE blocks are paged. The unpaged AID is ∆AID1 + Block Offset x 64. Accepted – see document IEEE for the resolution 180 65 55 Editorial Page offset is missed in the calculation of the unpaged AID. If inverse bitInverse Bitmap Field is 1, EWL is 7 and Length subfield is 1, all AIDs except one in the ADE blocks are paged. The unpaged AID is ∆AID1 + PageIndex x 2048 + Block Offset x 64. Accepted – see document IEEE for the resolution 181 66 16 Editorial Page offset is missed in the calculation of the range of AIDs. Change the subclause as follows: "Then the AIDs encoded by this ADE block is [PageIndex x 2048 + Offset1 x 64, PageIndex x 2048 + Offset2 x 64), PageIndex x 2048 + Offset1x 64 is included and PageIndex x 2048 + Offset2 x 64 is excluded." Accepted – see document IEEE for the resolution 776 65 8 Editorial Bit length of ∆AID is not necessarily "8" as in Figure Change "8" to "1~8". Accepted – see document IEEE for the resolution Discussion: None Proposed changes: 8.2.4.7.1.4 TIM Compression Instruction to Editor: Please modify the following paragraph of sub-clause 8.2.4.7.1.4 as follows: [CID 176]
IEEE P802.11 Wireless LANs Comment Resolution for Subclauses 8.4.2.170c and 9.32j Date: 2013-07-06 Author(s): Name Affiliation Address Phone email Yuan Zhou I2R 1 Fusionopolis Way, Connexis South Tower, Singapore 138632 +65 6408 2472 yzhou@i2r.a-star.edu.sg Zander Lei I2R 1 Fusionopolis Way, Connexis South Tower, Singapore 138632 Shoukang Zheng I2R 1 Fusionopolis Way, Connexis South Tower, Singapore 138632 Haiguang Wang I2R 1 Fusionopolis Way, Connexis South Tower, Singapore 138632 Abstract This document provides resolutions for CID 927. The changes are in the following subclauses: 8.4.2.170c, 9.32j. 0 Revision Notes R0: First draft CID Comment Page Number Line Proposed Changes Proposed Resolution 927 "Page Period" indication has been accepted in 802.11ah SFD in May. The normative text is missing in draft D0.1 81 12 Insert a field called "Page Period" with length 1 octet before the field "Page Index" in Figure 8-401cr. Also add the definition of page period in 8.4.2.10c: "The Page Accept use
MAC Modifications: 3. Definitions, acronyms, and abbreviations 3.2 Definitions specific to IEEE Std 802.11 REVmc editor: modify REVmc D1.4 Clause 3.2 as follows: directional multi-gigabit (DMG) access point (AP): An AP whose radio transmitter is capable of transmitting and receiving DMG physical layer () protocol data units (PPDUs). directional multi-gigabit (DMG) frame: A frame transmitted or received within a DMG physical layer () protocol data unit (PPDU). directional multi-gigabit (DMG) physical layer () protocol data unit (PPDU): A Clause 21 PPDU transmitted or received using the Clause 21 physical layer (PHY). directional multi-gigabit (DMG) station (STA): A STA whose radio transmitter is capable of transmitting and receiving DMG physical layer () protocol data units (PPDUs). 4. General description 4.3.17 DMG STA REVmc editor: modify REVmc D1.4 Clause 4.3.17 as follows: … A DMG STA supports the PHY signaling as described in 21.4, 21.5, 21.6, and 21.7. At a minimum, a DMG STA supports the mandatory modulation and coding scheme (MCS) and protocol data unit (PPDU) formats described in 21.4 and 21.6. A DMG STA has PHY features that include a low-density parity check (LDPC) encoding, a preamble making use of Golay sequences, and beamforming. The PPDUs are always transmitted with the same channel spacing as described in Annex E. Clause 4.9 Reference Model 4.9.3 Reference model for supporting multiple MAC sublayers REVmc editor: modify REVmc D1.4 Figure 4-20 as follows: Delete PMD Sublayer Delete PMD SAP Change PLCP to PHY REVmc editor: modify REVmc D1.4 Clause 4.9.3, P98L5 as follows: Multiple STAs coordinated by an MM-SME have a single that is shared by the multiple MAC sublayers. Transmission attempts of different MAC sublayers can collide internally if the STAs share a single PHY, and a backoff procedure is invoked in this case. Since multiple STAs coordinated
IEEE P802.11 Wireless LANs Proposed resolution for lb193mc CID 78, 309, and 310 Date: 2013-07-11 Author(s): Name Company Address Phone email Qi Wang Broadcom Corporation 190 Mathilda Place, Sunnyvale, CA 94086 +1-408-922-8798 Matthew Fischer Broadcom Corporation 190 Mathilda Place, Sunnyvale, CA 94086 +1-408-543-3370 Introduction This submission contains a proposal to enable frame classification based on the MAC header content, which is a proposed resolution for CID-78, 309 and 310 from LB193mc. The proposed modifications are in reference to the text in IEEE P802.11REVmc/D1.5 [1] and are indicated by the change marks as follows: 3.1 Definitions traffic classification (TCLAS): The specification of certain parameter values to identify the medium access control (MAC) data units (MDUs). The classification process, performed at a quality-of-service (QoS) access point (AP), uses the parameter values to examine each MDU and determine whether th MDU . TCLAS might also occur at (non-AP) QoS station (STA). NOTE—However, classification is beyond the scope of this standard. traffic filter: A set of traffic specifications defined by the use of traffic classification (TCLAS) elements that are utilized by the traffic filtering service (TFS) to identify specific allowed frames. 8.4.2.33 TCLAS element The TCLAS element specifies an element that contains a set of parameters necessary to identify incoming MSDUs (from a higher layer in all STAs or from the DS in an AP) that belong to a particular TS. The TCLAS element is also used when the traffic does not belong to a TS, for example, by the FMS, DMS, and TFS services. If required, the TCLAS element is provided in ADDTS Request and ADDTS Response frames only for the downlink or
REFERENCE: [1] IEEE P802.11REVmc_D1.5, Draft IEEE Standard for Information Technology – Telecommunications and information exchange between systems, local and metropolitan area networks – Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications
(DMG STA-A) or dot11BeamLinkMaintenanceTime (DMG STA-B)equals 0 is undefined 8.6.3 Discussion: 802.11-2012 enables delivery of RD and AC constraint when transmitting BAR by using of Control Wrapper, but 802.11ad does not provide the functionality. Propose to allow aggregation of BAR with QoS Null to provide the same functionality as 802.11-2012. In addition, propose to clean up the text and separate the DMG and non-DMG behavior. Change the indicated row in (Table 8-367—A-MPDU contents in the data enabled immediate response context) as follows Data sent under an Block Ack agreement or, in a DMG BSS, QoS Null MPDUs with Ack Policy set to No Acknowledgment QoS Data MPDUs with the same TID, which corresponds to an HT-immediate Block Ack agreement, or in a DMG BSS QoS Null MPDUs with Ack Policy set to No Acknowledgment. MPDUs all have the Ack Policy field equal to the same value, which is either Implicit Block Ack Request or Block Ack. In addition, in a DMG BSS, QoS Null with Ack Policy set to No Acknowledgment. Of these, at most one of the following is present in a BSS: — QoS Null MPDU (in DMG BSS only) with Ack Policy set to No Acknowledgment — One or more QoS Data MPDUs with the Ack Policy field equal to Implicit Block Ack Request — A BlockAckReq frame Of these, at most one of the following is present in a DMG BSS: — One or more QoS Data MPDUs with the Ack Policy field equal to Implicit Block Ack Request — QoS Null MPDU with Ack Immediate BlockAckReq At most one BlockAckReq frame with a TID that corresponds to an Block Ack agreement. This is the last MPDU in the It is not
Reassociation Request body Order Information Notes … TBD S1G Capabilities S1G Capabilities element is optionally present if dot11S1GOptionImplemented is true. Probe Request frame format Instruction to Editor: Please modify Table 8-30 in Clause 8.3.3.9 (@REVmc D1.1) as follows: Probe Request frame body Information Notes … TBD S1G Capabilities S1G Capabilities element is optionally present if dot11S1GOptionImplemented is true. DLS Request frame format Instruction to Editor: Please modify 8-243 in Clause 8.6.4.2 (@REVmc D1.1) as follows:
B0 B1 B2 B3 B4 B5 B6 B7 Uplink Synch Capable Dynamic AID BAT Support TIM ADE Support Non-TIM Support TWT Support STA Type Support Bits: 1 1 1 1 1 1 2 S1G Capabilities Info field The subfields of the S1G Capabilities Info field are defined in Table 8-191d (Subfields of the S1G Capabilities Info field). of the S1G Capabilities Info Subfield Definition Encoding …
IEEE P802.11 Wireless LANs Comment Resolution for Subclauses 9.32f.5 Date: 2013-07-17 Author(s): Name Affiliation Address Phone Email Amin Jafarian Qualcomm Inc. 5775 Morehouse Dr San Diego, CA 92109 1-858-651-9464 Matthew Fischer Broadcom Inc. Abstract This document provides resolution for CIDs 68, 445, 676, 446, 447, 35, 232, 674, 449, 450, 451
4 Outdoor Large BSS Hotspot D - Large BSSs, uniform e.g. 100-200m AP distance ~100s of STAs/AP, P2P pairs Managed Outdoor Flat Mobile 4a Outdoor Large BSS Hotspot + Residential D+A Managed + Unmanaged Hierarchical Mobile + Home 1 - Residential Scenario (From documents 11-13/1081r0, 786) Parameter Topology
PHY parameters Center frequency and BW All BSSs either all at 2.4GHz, or all at 5GHz [0 MHz BSS at 5GHz] MCS GI [Long] Data Preamble [5GHz, 11ac] STA TX power 17dBm AP TX Power 2dBm AP #of TX antennas 2,4 AP #of RX antennas 2,4 STA #of TX antennas 1, 2 STA #of RX antennas 1, 2 MAC parameters Access protocol parameters [EDCA with default parameters]
# Source/Sink Name Traffic definition Flow specific parameters AC Downlink D1 AP/STA1 to AP/STA10 Highly compressed video (streaming) T2 D2 AP/STA11 to AP/STA20 Web browsing T4 D3 AP/STA21 to AP/STA30 Local file transfer T3 Uplink U1 STA1/AP to STA10/AP Highly compressed video (streaming) – UL TCP ACKs… U2 STA11/AP to STA20/AP Web browsing: – UL TCP ACKs… U3 to STA30/AP Local file transfer T3 P2P P1 NONE (see interfering scenarios) Idle / Management M1 AP Beacon TX M2 STA36 to STA TBD Probe Req. TY Interfering Scenario for Scenario 3 This scenario introduces and overlay of unmanaged P2P networks on top of Scenario 3. Parameter Value Topology Figure 8 - BSSs layout, with interfering P2P links Topology Description K P2P pairs of STAs APs location Pairs randomly placed in simulation area
1 - Reference traffic profiles per scenario Reference traffic profile for Scenario 1 Traffic Model # Traffic model name Description Application traffic (Forward / Backward) Application Load (Mbps) (Forward / Backward) A-MPDU Size (B) (Forward / Backward) T1 Local file transfer FTP/TCP transfer of large file within local network FTP file transfer / FTP TCP ACK Full buffer / 0.1 Max / 64 T2 Lightly compressed video T3 Internet streaming video/audio T4 4k streaming T5 Online game server T6 Management: Beacon T7 Management: Probe requests Reference traffic profile for Scenario 2 Traffic Model # Traffic model name Description Application traffic (Forward / Backward) Application Load (Mbps) (Forward / Backward) A-MPDU Size (B) (Forward / Backward) T1 Local file transfer FTP/TCP transfer of large file within local network FTP file transfer / FTP TCP ACK Full buffer / 0.1 Max / 64 T2 Lightly compressed video T3 Internet streaming video/audio T4 4k video streaming T5 Online game server T6 Management: Beacon T7 Management: Probe requests Reference traffic profile for Scenario 3 Traffic # Traffic model name Description Application traffic (Forward / Backward) Application Load (Mbps) (Forward / Backward) A-MPDU Size (B) (Forward / Backward) T1 file transfer FTP/TCP transfer of large file within local network FTP file transfer / FTP TCP ACK Full buffer / 0.1 Max / 64 T2 Lightly compressed video T3 Internet streaming T4 4k video streaming T5 Online game server T6 Management: Beacon
Reserved Reserved for future use CID P.L SC Comment Proposed Change Resolution 923 169.35 Better expression is recommended. Also, to be logically match with contents in 10.1.3.7a.1, it is better to rephrase the sentence. Modify the sentence from "... a Short Beacon may be sent or instead of a Beacon during at a TBTT that coincides with a TSBTT." to "... a Beacon frame may be sent instead of a Short Beacon frame at a TSBTT that coincides with a TBTT." Accepted – Editor to make the changes proposed by the commenter. Discussion: None
IEEE P802.11 Wireless LANs Resolution for CID 11018 Date: 2013-09-05 Author(s): Name Affiliation Address Phone email Sigurd Schelstraete Quantenna Communications, Inc 3450 W. Warren Ave Fremont, CA 94538 +1 510 743 2260
comment. Any spec changes are not needed. CID Page Clause Comment Proposed Change Resolution 886 For S1G band, the NDP transmission protocol should be defined. Simply, we can replace VHT of section 9.31.6 with S1G. Define a S1G NDP transmission protocol. Revised- TGah editor to make changes shown in under the heading for CID 813, 816, 886 813 the folowing sentence "For S1G band, the same sounding protocol is applied, with "VHT" replaced by "S1G"" is too simplistic and if applied generates several inconsistencies; e.g. this would indicate also an "S1G NDP Announcement", which does not exist. Is the VHT NDP announcements used? Similarly for the VHT CompressedBeamforming Have a thorough revision of the section and make sure the desired behavior is clearly defined Revised- TGah editor to make changes shown in under the heading for CID 813, 816, 886 816 "9.31.5.2 Rules for VHT sounding protocol sequences" A VHT beamformer shall not transmit either a VHT NDP Announcement+HTC frame or a Beamforming ReportPoll+HTC frame that contains an HT variant HT Control field. Does S1G supports HTC or VHTC? Clarify for S1G Sounding Protocol. Revised- TGah editor to make changes shown in under the heading for CID 813, 816, 886 CID 813, 816, 886 Discussion: For S1G band, the same VHT sounding protocol is applied to a S1G STA.