zilongwang/ReadingBank huggingface dataset:
1032 Ke Yao 26.3.2 75.19 "DL HE NDP is one DL HE sounding format." means only one? Or one of some choices? It's not clear. And what does DL HE sounding format refer to? make it clear Revised. Change to as in the resolution of CID1032 in doc 1613 Mark RISON 26.3.2 75.19 "DL HE NDP is one DL HE sounding format." -- what does this mean? Delete the sentence Accepted 1929 Sigurd Schelstraete 26.3.2 75.20 Make separate subclause for sounding PPDU See comment Revised. Change to as in the resolution of CID 1929 in doc 1614 Mark RISON 26.3.2 75.21 "The format of a HE NDP PPDU is shown in Figure 26-5 (HE NDP PPDU format)." -- as the end of this subclause says, an HE NDP PPDU is just a vanilla HE SU PPDU without a Data field Delete lines 21 to 43 inclusive Rejected. Although HE NDP PPDU transmission uses HE SU PPDU format without Data field, it has some specific properties such as HELTF-2x symbol format, 4μs PE duration. It is worth to put it in a separate subclause. 542 Eunsung Park 26.3.2 75.37 We agreed the PE for NDP is 4us. Define the PE extension for NDP as 4us. Revised. Change to as in the resolution of CID542 in doc 837 Jinsoo Choi 26.3.2 75.37 The duration of PE in the NDP PPDU was decided as being always 4us. Change to: "The PE is always present and the duration of PE is 4us." Revised. Change to as in the resolution of CID837 in doc 1844 Sameer Vermani 26.3.2 75.42 The text "The HE NDP PPDU has the following properties: --It uses the HE SU PPDU format but without the Data field --is an HE SU PPDU as implied by the value of L-Length field in L-SIG field" seems redundant and unclear. The first bullet says it is an PPDU format already and then second Make this more succinct and technically precise. Revised. Change to as in the resolution of CID 1844 in doc
1 1 0 π/2-BPSK 1 2 1/2 385 2 2 0 π/2-BPSK 1 1 1/2 770 3 3 0 π/2-BPSK 1 1 5/8 962.5 4 4 0 π/2-BPSK 1 1 3/4 1155 5 5 0 π/2-BPSK 1 1 13/16 1251.25 6 6 0 π/2-QPSK 2 1 1/2 1540 7 7 0 π/2-QPSK 2 1 5/8 1925 8 8 0 π/2-QPSK 2 1 3/4 2310 9 9 0 π/2-QPSK 2 1 13/16 2502.5 9.1 6 1 π/2-QPSK 2 1 7/8 2695 10 10 0 π/2-16QAM 4 1 1/2 3080 11 11 0 π/2-16QAM 4 1 5/8 3850 12 12 0 π/2-16QAM 4 1 3/4 4620 12.1 1 π/2-16QAM 4 1 13/16 5005 12.2 1 π/2-16QAM 4 1 7/8 5390 12.3 1 π/2-64QAM 6 1 5/8 5775 12.4 1 π/2-64QAM 6 1 3/4 6390 12.5 1 π/2-64QAM 6 1 13/16 12.6 12 1 π/2-64QAM 6 1 7/8 8085 References: [1] Draft P802.11REVmc_D5.4 [2] 11-16-0220-03-000m-clause-20-SC-extended-MCSs [3] 11-16-0541-03-000m-SC-64-QAM-response-to-editor-comments
No new presentations, other than those listed in the agenda, were requested. The Chair asked for approval of the agenda No objection raised Presentation of contributions 662r2 Further consideration on channel access rule to facilitate MU transmission opportunity #1 (pre-motion): Do you to add to the following to 11ax TG SFD: Do you agree to allow the AP choose any access category for contending to send the trigger frame? The chosen AC may give to the AP higher priority in accessing the channel compared to its associated STAs Y/N/A: 8/0/many Strawpoll passes 664r2 Consideration on backoff procedure for UL MU transmission #1 Do you support? The non-AP STA resets its backoff counter after successfully transmitting an UL PPDU as the response to trigger frame. Y/N/A: 8/13/16 #2 Do you support? The non-AP STA keeps the backoff counter unchanged after successfully transmitting an UL PPDU as the response to trigger frame. Y/N/A: 19/1/21 665r0 Some Notes on Interference Alignment for Downlink Multi-User MIMO The strawpolls were moved to the TGax joint session because the topic requires the presence of PHY experts. 667r0 Signaling of Multi-TID Aggregation Limit #1: Do you agree to add to the TGax SFD The basic variant Trigger frame shall contain the TID Aggregation Limit subfield in the Trigger Dependent Per User Info field that indicates the limit of the number of TIDs that can be aggregated by a STA in a multi-TID A-MPDU carried in the responding Trigger-based PPDU? The responding STA not aggregate QoS Data frames in the multi-TID with a number of TIDs that exceeds the value indicated in the TID Aggregation Limit sub-field intended to it Y/N/A: 32/0/7 Strawpoll passes 0582r3 Random Access RU Allocation in the Trigger Frame
No Objection – Mark Ready for Motion 7732 (GEN) Review Comment Proposed Resolution: REVISED; Change the body of 12.3.1 to read just “Except for Open System authentication, all pre-RSNA security mechanisms are obsolete. Support for them might be removed in a later revision of the standard.” No Objection – Mark Ready for Motion Motion #236: 2nd set of Thurs PM2 CIDs (2nd set): Move to resolve: CIDs 7087(MAC), 7088(MAC) as “Revised; incorporate the text changes in CIDs 7747(MAC) and 7748(MAC) as “Revised” with a resolution of “Incorporate the text changes in 11-16-276r11< > , which clarify the exact rules for MPDU ordering in A-MPDUs for a DMG STA.” CID 7573(GEN) as “Revised” with a resolution of “Incorporate the text changes in 11-16-276r11< >” CID 7732 (GEN) Proposed Resolution: REVISED, Change the body of 12.3.1 to read just “Except for Open System authentication, all pre-RSNA security mechanisms are obsolete. Support for them might be removed in a later revision of the standard.”. Adrian STEPHENS Seconded: Sean COFFEY REVmc Secretary note: The motion deck has CID 7087 and 7088 being resolved with the following: “Revised” incorporate the text changes in 11-16-228r13”, But the earlier minutes and the data base show that this resolution was to be set to “REVISED (MAC: 2016-05-20 03:48:52Z): At 1351.61 replace "idle" with "busy" “ Which matches the text changes in 11-16/228r13. Result #236: 11-0-2 Motion passes Time Extension: Asked for time to extend meeting for one motion – No Objection Motion #237: CID 7541(MAC) Move to resolve: CID 7541 as “Rejected” with a resolution of “the proposed change is not necessarily correct or complete in all contexts” Moved: Sean COFFEY Seconded: Adrian STEPHENS Discussion: none Results #237: 9-1-5 Motion Passes Adjourned at 6:03pm References: Tuesday PM1: List of Prior Minutes:
CID Comment Proposed Change 155 2 2 T Comment on coexistence assurance document: Section 2 (Channelization) says" While adopting 1.08GHz channel as described in Clause 25 for 802.11aj [1], 802.11aj ensures coexistence with 802.11ad by using DBC mechanism defined in clause 9 in 802.11aj [1]". The DBC mechanism in Draft 1.0 is a protection that breaks with density and mobility of DMG devices; to the best of my knowledge all viable 802.11 amendments have used a PHY-based protection using legacy headers. 802.11aj will NOT be backward compatible with 802.11ad unless using the 11ad preamble; otherwise no part of a CDMG packet can be decoded by a DMG device. Define a plan for coexistence with 11ad. Suggestion is to limit 802.11aj to QDMG. 166 In Section 2 (Channelization) of coexistence assurance document it states that " adopting 1.08GHz channel as described in Clause 25 for 802.11aj [1], 802.11aj ensures coexistence with 802.11ad by using DBC mechanism defined in clause 9 in 802.11aj [1]". The DBC is a MAC based approach, quite different from PHY based coexistence approach as in all other 11 standards. In addition the DBC relies on using SP both on DMG and CDMG. Since DMG is using CBAP mainly, the DBC mechanism may not work well. Define a plan for coexistence with 11ad. Suggest limiting 802.11aj to QDMG Proposed resolution: Revised. In order to effectively share the same spectrum with DMG STAs as much as possible, besides existing MAC layer mechanisms defined in 11aj, some amendments are proposed to 11aj D1.0, including transmitting the length of the 1.08 GHz PPDU on 2.16 GHz channel. See details in clause 3.4 of the general discussions on proposed resolutions on page 3-4. use
Common Info and type-specific Per User Info are not present. Please specify an absence of the Common Info and type-specific Per User Info in the Basic Trigger. present for the basic variant of the trigger type.However the per user information is present. Text added based on document 16/0667 and motion passed in IEEE 802.11 May meeting. 2691 Yuichi Morioka 21.14 Usage of Basic Trigger is not defined. Add description of Basic Trigger Revised. Text added based on document 16/0667 and motion passed in IEEE 802.11 May meeting. 2692 Yuichi Morioka 21.22 CF_End should be allowed to be triggered to cancel the NAV set by the MU-RTS change "4-TBD" to "4" and Change "Reserved" to "MU CF_End" and "Reserved" Revised. Text has been added to enable reset of NAV if a CTS is not received. 2900 Zhou Lan 19.49 trigger fame contains type specific info which can be achieved by aggregating trigger frame and control frame. remove type specific info and simplify the trigger frame design otherwise clarify the benefits of this mechanism over aggregating trigger and control/Management frame Rejected This is asking to remove type specific info from the trigger frame. Aggregating leads to overhead, and would not allow the Trigger frame to be sent in legacy format. TGax Editor: Add the subclause below as resolution to (#CID 2219):
(Typo “82dBm” ->”-82dBm”, refer to r1 for the correct SP text) Q: don’t know how to measure the inaccuracy, better to clarify the word “platform” A: to work in other organization to clarify platform requirement. SP Result: 30Y/1N/8A; SP passed. 4.5 16/0618 11ax CSD Design, Bin Tian (Qualcomm) Discussions: SP#1: Do you support to add to the SFD reuse the 11ac per stream CSD values for all HE PPDU? (refer to r1 for revised SP text) SP Result: No Objection; SP passed. SP#2: Do you support that in UL MU-MIMO transmission the per stream CSD value is based on global stream index? (refer to r1 for revised SP text) SP Result: No Objection; SP passed. SP#3: Do you support per antenna CSD values for in Pre HE modulation Reuse the 11ac per antenna CSD values when beam change =1 Not specified (absorbed in the Q matrix) when beam_change=0? (refer to r1 for revised SP text) SP Result: No Objection; SP passed. SP#4: Do you support that in UL MU transmission the per antenna CSD is based on the antenna index of each STA (i.e. local index)? (refer to r1 for revised SP text) SP Result: No Objection; SP passed. 4.6 16/0619 PAPR Reduction for HE SIG-B, Bin Tian (Qualcomm) Discussions: Q: Broadcast STAID being all 1s, phase rotates back to all 0?
IEEE P802.11 Wireless LANs CIDs for: Section 25.6 HE Sounding Comment Resolution Date: 2016-05-16 Raja Banerjea Qualcomm Simone Merlin Youhan Kim Sameer Vermani Lochan Verma Bin Tian Chu Marvell Narendar Madhavan Toshiba 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 PP.LL Comment Proposed Change Resolution 55 Ahmadreza Hedayat 25.6 Clarify whether an AP can share the sounding sequence in this clause between a set of UL-MU-capable STAs and another set od STAs that are not UL-MU-capable STAs. As in the comment, specify the choices that are available for an AP to perform HE sounding amon these two sets of STAs specfied in this comment. Revised – There are two mechanisms that have been accepted and they are defined as SU and MU sounding and the AP can chose either of them.
802 Jing Ma 60.36 the draft doesn't clarify how an HE AP solicit beamforming feedback from multiple STAs sequentially through SU transmission. Does it mean that we just follow the sounding protocol with multi-user in 11ac (the example procedure shown in Figure of the sounding protocol with a single VHT beamformee) "An example of soliciting beamforming feedback from multiple STAs through SU transmission sequences are shown in Figure 9-41b41a (Example of the sounding protocol with a single VHT beamformee)" should be added at the end of "an HE AP solicit beamforming feedback from multiple STAs sequentially through SU transmission" Revised. Agree in principle with the comment. Proposed resolution clarifies these missing details. Provided details 1695 Oghenekome Oteri 61.39 No details on Feedback for HE sounding protocol Update draft to reflect March agreements Revised Agree and as above. . Provided details TGax Editor: Add the subclause as resolution to (#CID 55, 1000, 1221, 1915, 2234, 2459, 2665,802,1695):
frame from multiple STAs sequentially through SU transmission. An example of the HE Radio measurement protocol using MU operation to solicit report is shown in Figure 25-x [add new figure]." Also add "Measurement" into reserved Trigger Type field table(p.21 Table 9-ax2) 702 Jae Seung Lee 61.28 Remove the TBDs Revised. The TBDs in section 25.6 have been addressed. 1916 Sigurd Schelstraete 25.6 Why (TBD)? See comment Revised. The TBDs in section 25.6 have been addressed. 2233 Tomoko Adachi 25.6 An HE NDP Announcement frame should be defined. Add a definition of the HE NDP Announcement in clause 9. Revised. HE NDP Announcement frame is define.
Codebook Information Indicates the size of codebook entries: If Feedback Type is SU: Set to 0 for 2 bits for ψ, 4 bits for Set to 1 for 4 bits for ψ, 6 bits for If Feedback Type is MU: Set to 0 for 5 bits for ψ, 7 bits for Set to 1 for 7 bits for ψ, 9 bits for Note: The codebook size for MU Feedback with Ng=16 is limited to (9,7) Feedback Type Indicates the feedback type: Set to 0 for SU Set to 1 for MU Set to 2 for CQI Feedback (CID #971, 2713) 3 is Reserved Remaining Feedback Segments Indicates the number of remaining feedback segments for the associated VHT Compressed Beamforming Set to 0 for the last feedback segment of a segmented report or the only feedback segment of an unsegmented report. Set to a value between 1 and 6 for a feedback segment that is neither the first nor the last of a segmented report. Set to a value between 1 and 7 for a feedback segment that is not the last feedback segment of a segmented report. In a retransmitted feedback segment, the field is set to the same value associated with the feedback segment in the original transmission. First Feedback Segment Set to 1 for the first feedback segment of a segmented report or the only feedback segment of an unsegmented report; set to 0 if it is not the first feedback segment or if the VHT Compressed Beamforming Report field and MU Exclusive Beamforming Report field are not present in the frame. In a retransmitted feedback segment, the field is set to the same value associated with the feedback segment in the original transmission. RU Start Index The starting RU index indicates the first RU26 for which the HE beamformer is requesting feedback. RU End Index The ending RU index indicates the last RU26 for which the HE beamformer is requesting feedback. Sounding Dialog Token Number In a HE Compressed Beamforming frame not carrying all or part of a HE Compressed Beamforming report, the Nc Index, Nr Index, Channel Width, Grouping, Codebook Information, Feedback Type and Sounding Dialog Token Number are reserved, the First Feedback Segment subfield is set to 0 and the Remaining Feedback Segments subfield is set to 7.
262 Bin Tian 19.37 MU Motion #55 on additions to the Trigger frame was approved but no corresponding specification text has been added Add text to include the additions as per the motion 372 Brian Hart 20.19 subsequent Trigger frame subsequent Trigger frame in the same TXOP . 612 Geonjung Ko 19.61 It is required to describe how to set RA field value. The RA field for the Trigger frame triggering multiple STAs is set to broadcast/multicast address and the RA field for the Trigger frame triggering one STA is set to the STA's MAC address. . 660 Huizhao Wang 19.61 Need to specify in what case(s), the RA is not part of Trigger frame Add a table to list out Trigger frame formats . 830 Jinsoo Ahn 19.61 RA of Trigger Frame needs to be determined except for the case of single STA Chage the following (The RA field of the Trigger frame is the address of the recipient STA. Whether RA is not part of Trigger frame is TBD.)'RA field of Trigger Frame shall be set to identical value of TA field(MAC address of AP)' 864 Jun Luo 21.43 MAC Motion #74 (RU allocation for each STA in per user info field of Trigger frame) was approved but no corresponding spec text is present in the draft TBD 1083 Kiseon Ryu 19.39 Update the Trigger frame format as defined in the latest SFD (v16). Update the Trigger frame format. 1716 Osama Aboulmagd 19.61 "The RA field of the Trigger frame is the address of the recipient STA. It is not clear why as in comment
8.4.1.9 StatusCodes NP 8.4.2.1 ElementIDs NP 8.4.2.1 Element ID Extension 1 OK 8.4.2.100.2 Active Path Selection Protocol NP 8.4.2.27.2 CipherSuiteSelectors NP 8.4.2.27.3 AKMSuiteSelectors NP 8.4.2.27.4 RSNCapabilities NP 8.4.2.29 ExtendedCapabilities OK 8.4.2.50 FastBSSTransitionSubElementIDs NP 8.4.4 Info IDs OK 8.5.14.28 WNM-Notification NP 8.5.2.1 SpectrumManagementActionFrames NP 8.5.8.1 PublicActionFrames NP 8.8.3 ShortFrameTypes NP 8.8.4 ShortControlFrameSubTypes NP 8.8.5 ShortManagementFrameSubTypes NP annex C dot11mac NP C.3 dot11Groups See Action 1 C.3 dot11OperationEntry NP C.3 dot11phy NP C.3 dot11smt NP C.3 dot11StationConfigEntry See Action 2 C.3 ieee802dot11 NP C.3 dot11Compliances See Action 3 D.1 BehaviorLimits NP E.1 OperatingClassesInJapan NP E.1 OperatingClassesInEurope NP E.1 OperatingClassesGlobal NP E.1 OperatingClassesInUSA NP None MAC addresses NP Notes: NP – Not present OK – Present and values are correct Actions arising:
CQI CQI FORMAT is HE_SU and PSDU_LENGTH equals 0 Contains an array of received SNR measurements for each spatial stream per 26-tone. Each SNR is an absolute number represented by 6 bits, with 1 dB granularity and a range of -10 dB to 53 dB N Y FORMAT is HE_MU or HE_EXT_SU or HE_TRIG or (FORMAT is HE_SU and PSDU_LENGTH is greater than 0) Not present N N Otherwise See corresponding entry in Table 21-1 NO_SIG_EXTN NO_SIG_EXTN FORMAT is HE_SU or HE_MU or HE_EXT_SU or HE_TRIG Not present N N Otherwise See corresponding entry in Table 21-1 FEC_CODING FEC_CODING FORMAT is HE_SU or HE_MU or HE_EXT_SU or HE_TRIG Indicates FEC encoding is used. Enumerated type: BCC_CODING indicates binary convolutional code. LDPC_CODING indicates low-density parity code. Otherwise See corresponding entry in Table 21-1
BEAMFORMED BEAMFORMED FORMAT is or HE_EXT_SU Set to 1 if a beamforming steering matrix is applied to the waveform in an SU transmission. Set to 0 otherwise. Y O FORMAT is HE_MU or HE_TRIG For single-user allocation in an RU, set to 1 if a beamforming steering matrix is applied, and set to 0 otherwise. For each user in a multi-user allocation in an RU, always set to 0. O Otherwise See corresponding in Table 21-1 HE-LTF_TYPE HE-LTF_TYPE FORMAT is HE_SU or HE_MU or HE_EXT_SU or HE_TRIG Indicates the type of HE-LTF. Enumerated type: 1x HE-LTF 2x HE-LTF 4x HE-LTF See 26.3.9.10 HE-LTF for details. Y Y Otherwise Not present N N HE-LTF_MODE HE-LTF_MODE FORMAT is HE_TRIG Indicates whether the UL MU MIMO transmission uses single stream pilots or a mask on each spatial stream of the LTF sequence by a distinct orthogonal code. It is only present for full bandwidth MU-MIMO. Y N Otherwise Not present N N
PREAMBLE_TYPE PREAMBLE_TYPE FORMAT is NON_HT and is one of —ERP-DSSS —ERP-CCK Enumerated type: SHORTPREAMBLE LONGPREAMBLE Y Y Otherwise Not present N N
FORMAT is NON_HT In TXVECTOR, if present, indicates the initial state of the scrambler of the transmitted PPDU. In RXVECTOR, indicates the Scrambler Initialization value in the Service field, prior to descrambling. O Y FORMAT is HE_MU or HE_TRIG Not present N N Otherwise Indicates the Scrambler Initialization value in the Service field, prior to descrambling. N Y
one-to-one correspondence. 1137 Kwok Shum Au 17.14 In Table 9-24, one combination is missing. In Table 9-24, please define the BlockAck frame variant when Multi-TID subfield is 0, Compressed Bitmap subfield is 1, subfield is 0, and subfield is 1. REVISED The missing combination that the commenter pointed out was used for BlockAck in 11ak and was added in Table 9-24. 804 Jinjing 15.18 the added bit of the multi-STA subfield to indicate the Multi-STA BA variant for 11ax seems not to be efficient use of the reserved bits. Even this bit is added, there are multiple reserved options that do not have valid meaning. In the future, if new variant is added, one more bit needs to be used. Change subfield" to be "BA variant subfield", or change the whole B1-B4 to be the "BA variant subfield". REVISED Make changes in doc. 16/0819. in principal. There are many combinations that are reserved and they should be used efficiently in the future. The B1-B4 of the BA control field is changed to BA Type subield. Similar problem existing in BAR control field may be solved in REVmc. 212 Alfred Asterjadhi 17.16 Table 9-24: Blockack frame variant encoding: 0-1-0-1 should also be added to the table (as reserved As in comment REVISED The missing combination that the commenter pointed out was used for BlockAck in 11ak and was added in Table 9-24. GCR STA
2212 Tomoko Adachi 16.52 How to set the RA field of the Multi-STA BlockAck should be explained in 9.3.1.9.1. Explain that the same legacy rule (setting to the address of the recipient STA that requested the Block Ack) shall be applied for the RA field for a Multi-STA BlockAck frame with BA Information for a single AID. Also add here that the RA field for a BlockAck frame with BA Information for multiple AIDs is set to the broadcast address. (The last sentence in the first para o 25.4.1 may be removed.) As in comment. REVISED Make changes in doc. 16/0819. 2412 Yongho Seok 16.64 B4 of BA Control is already used by 802.11ak (GCR mode). Use B5 for Multi STA subfield. As per comment 2413 Yongho Seok 17.14 Table 9-24 should be updated based on the changes from 802.11ak Draft 2.0. As per comment REVISED – 1136 Kwok Shum Au 16.60 Replace STA" with "Multi-STA" in Figure 9-32. Replace "Multi STA" with "Multi-STA" in Figure 9-32. 1493 Mark 55.52 It says "with BA Information for multiple AIDs" Change to "with one or more BA Information fields with more than one AID" REVISED -
Operating classes in the United States Operating class Global operating class (see Table E-4 (Global operating classes)) Channel starting frequency (GHz) Channel spacing (MHz) Channel set(#3054) Channel center frequency index Behavior limits set 1 115 5 20 36, 40, 44, 48 — 2 118 5 20 52, 56, 60, 64 — DFS_50_100_Behavior 3 124 5 20 149, 153, 157, 161 — NomadicBehavior 4 121 5 20 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 144(11ac) — DFS_50_100_Behavior, UseEirpForVHTTxPowEnv(11ac) 5 125 5 20 149, 153, 157, 161, 165 — LicenseExemptBehavior 6 103 4.9375 5 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 — 7 103 4.9375 5 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 — 8 102 4.89 10 11, 13, 15, 17, 19 — 9 102 4.89 10 11, 13, 15, 17, 19 — 10 101 4.85 20 21, 25 — 11 101 4.85 20 21, 25 — 12 81 2.407 25 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 — LicenseExemptBehavior 13 94 3.000 20 133, 137 — CCA-EDBehavior 14 95 3.000 10 132, 134, 136, 138 — CCA-EDBehavior 15 96 3.0025 5 131, 132, 133, 134, 135, 136, 137, 138 — CCA-EDBehavior 16 —(#3079) 5.0025 5 170–184 — ITS_nonmobile_operations, ITS_mobile_operations 17a, —(#3079) 5 10 171–184 — ITS_nonmobile_operations, ITS_mobile_operations 18a, b —(#3079) 5 20 172–183 — ITS_nonmobile_operations, ITS_mobile_operations 19–21 Reserved Reserved Reserved Reserved Reserved Reserved
Global operating classes Operating class Nonglobal operating Channel starting frequency (GHz) Channel spacing (MHz) Channel Channel center frequency Behavior limits set 1–80 —(#3079) Reserved Reserved Reserved — Reserved 81 E-1-12, E-2-4, E-3-30, 2.407 25 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 — 82 E-3-31 2.414 25 14 — 83 E-1-32, E-2-11, E-3-56, 2.407 40 1, 2, 3, 4, 5, 6, 7, 8, 9 — PrimaryChannelLowerBehavior 84 E-1-33, E-2-12, E-3-57, 2.407 40 5, 6, 7, 8, 9, 10, 11, 12, 13 — PrimaryChannelUpperBehavior 85(11af) —(#3079) — 6, 7, 8 — — 86(11af) —(#3079) — 12, 14, 16 — — GeoDB 87(11af) —(#3079) — 24, 28, 32 — — 88-93 —(#3079) Reserved Reserved Reserved Reserved Reserved 94 E-1-13 3 20 133, 137 — CCA-EDBehavior 95 E-1-14 3 10 132, 134, 136, 138 — CCA-EDBehavior 96 E-1-15 3.0025 5 131, 132, 133, 134, 135, 136, 137, 138 — CCA-EDBehavior 97–100 —(#3079) Reserved Reserved Reserved Reserved Reserved 101 E-1-10,11 4.85 20 21, 25 —
IEEE P802.11 Wireless LANs CID 8028 – High throughput airtime link metric Date: 2016-07-7 Author(s): Name Company Address Phone email Kazuyuki Sakoda Sony Kazuyuki.Sakoda (at) am (dot) sony (dot) com Hiertz Guido.Hiertz (at) ericsson (dot) com Comment: CID Comment Proposed Change Suggested Resolution 8028 Kazuyuki Sakoda 802.11s introduced mesh procedures. As a part of the mesh procedures, path selection protocol and path selection metric are used to determine a mesh path over multiple hops. Path selection protocol and path selection metric are replacable module. Active path selection protocol and active path selection metric are signaled through Active Path Selection Protocol Identifier field and Active Path Selection Metric Identifier field in the Mesh Configuration element (see 9.4.2.98). For path selection metric, Airtime link metric is defined in clause 14.9, as the default path selection metric. Value 1 is assigned to represent Airtime link metric in the Active Path Selection Metric Identifier. In summary of the problem, the current Airtime link metric cannot express high throughput link appropriately and causes significant quantization error. Add another Path Selection Metric, "High throughput airtime link metric", that scales to higher throughput links considering 802.11n and 802.11ac usage. To minimize the impact to the specification, the new Active Path Selection Metric shall work with existing Active Path Selection Protocol, HWMP. Only change the metric module. In particular: a) Assign a new Acive Path Selection Metric Identifier in 9.4.2.98, b) Add new clause describing "High throughput airtime link metric" after 14.9 (Airtime link metric), REVISED: Adopt changes proposed in
IEEE P802.11 Wireless LANs Updates for the Advice of Charge and Network Authentication Type ANQP-elements Date: 2016-07-26 Author(s): Name Company Address Phone email Stephen McCann BlackBerry Ltd 200 Bath Road, Slough, Berkshire, SL1 3XE, UK +44 1753 667099 Michael Montemurro BlackBerry Ltd 4701 Blvd., Mississauga, ON. CANADA. L4W 0B4 +1-289-261-4183 Modify the table in the following clause as shown: Access Network Query Protocol (ANQP) elements(11u) Table 9-271 ANQP-element definitions (11u) ANQP-element name Info ID ANQP- (Ed)element (clause) Reserved 0 – 255 n/a … … … Reserved <ANA+1> – 56796 n/a Vendor Specific 56797 8.4.5.8 (Vendor Specific Reserved 56798 – 65535 n/a Modify the following subclause 9.4.5.21 Advice of Charge ANQP-element
22 96,124 8 96,122 23 124,152 24 152,180 25 176,204 26 204,232 27 232,260 28 260,288 9 = (S,E) for 80 MHz ‒ 256 29 284,312 10 30 312,340 11 31 340,368 12 32 364,392 13 33 392,420 14 34 420,448 15 35 448,476 16 36 472,500 17 Table YY-2: Feedback subcarrier indices indicating Start 26-tone RU index and end 26-tone RU index for Ng = 16. 80 MHz 26 RU Index 80 MHz (S,E) FB tone 40 MHz 26 RU Index 40 MHz (S,E) FB tone 20 MHz 26 RU Index 20 MHz (S,E) FB tone 0 -500,-468 0 = (S,E) for 80 MHz + 256 1 -484,-436 1 2 -452,-420 2 3 -420,-388 3 4 -404,-356 4 5 -372,-340 5 6 -340,-308 6 7 -324,-276 7 8 -292,-260 8 9 -260,-228 10 -244,-196 11 -212,-164 12 -180,-148 13 -164,-116 14 -132,-84 0 -122,-84 15 -100,-68 1 = (S,E) for 80 MHz 16 -84,-36 2 -68,-36 17 -52,-4 3 = (S,E) for 80 MHz 18 -20,20 4 19 4,52 5 20 36,84 6 36,68 21 68,100 7 = (S,E) for 80 MHz 22 84,132 8 84,122 23 116,164 24 148,180 25 164,212 26 196,244 27 228,260 28 260,292 9 = (S,E) for 80 MHz ‒ 256 29 276,324 10 30 308,340 11 31 340,372 12 32 356,404 13 33 388,420 14 34 420,452 15 35 436,484 16 36 468,500 17
PeerSTAAddress MACAddress Any valid individual MAC address Specifies the address of the peer MAC entity from which the association request was received. ResultCode Enumeration SUCCESS, REFUSED_REASON_UNSPECIFIED, REFUSED_EXTERNAL_REASON, REFUSED_AP_OUT_OF_MEMORY, REFUSED_TEMPORARILY Indicates the result response to the association request from the peer MAC entity. Capability- Information Capability Information field As defined in 9.4.1.4 (Capability Information field) Specifies the operational capabilities advertised by the AP or PCP(11ad). AssociationID Integer Non-DMG: 1–2007 DMG: 1–254(#6290) If the association request result was SUCCESS, then AssociationID specifies the association ID value assigned to the peer MAC entity by the AP or PCP(11ad). EDCAParameterSet EDCA Parameter Set element As defined in 9.4.2.29 (EDCA Parameter Set element) Specifies the EDCA parameter set that the STA should use. The parameter is present if is true; otherwise not present(#28). RCPI Integer As defined in 9.4.2.38 (RCPI element)(#6756) The RCPI value represents the measured RCPI of the corresponding Association Request frame. The element is optionally present if is true; otherwise not present(#28). RSNI Integer As defined in 9.4.2.41 (RSNI element) The RSNI represents the measured RSNI at the time the corresponding Association Request frame was received. The element is optionally present if is true; otherwise not present(#28). RM Enabled Capabilities element As defined in 9.4.2.45 (RM Enabled Capabilities element) Specifies the RM enabled capabilities advertised by the AP or PCP(11ad). The element is present if is true; otherwise not present(#28).
Multi-band peer,(11ad) MMS,(11ad) VHT Capabilities,(11ac) VendorSpecificInfo ) Name Type Valid range Description PeerSTAAddress MACAddress Any valid individual MAC address Specifies the address of the peer MAC entity from the association request was received. ResultCode Enumeration SUCCESS, REFUSED_REASON_UNSPECIFIED, REFUSED_EXTERNAL_REASON, REFUSED_AP_OUT_OF_MEMORY, REFUSED_TEMPORARILY Indicates the result response to the association request from the peer MAC entity. Capability- Information Capability Information field As defined in 9.4.1.4 (Capability Information field) Specifies the operational capabilities advertised by the AP or PCP(11ad). AssociationID Integer Non-DMG: 1–2007 DMG: 1–254(#6290) If the association request result was SUCCESS, then AssociationID specifies the association ID assigned to the peer MAC entity by the AP or PCP(11ad). EDCAParameterSet EDCA Parameter Set element As defined in 9.4.2.29 (EDCA Parameter Set element) Specifies the EDCA parameter set that the STA should use. The parameter is present if is true; otherwise not present(#28). RCPI Integer As defined in 9.4.2.38 (RCPI element)(#6756) The RCPI value represents the measured RCPI of the corresponding Association Request frame. The element is optionally present if is true; otherwise not present(#28). RSNI Integer As defined in 9.4.2.41 (RSNI element) The RSNI value represents the measured RSNI at the time the corresponding Association Request frame was received. The element is optionally present if is true; otherwise not present(#28).
2604 For VHT MU PPDU sent to HE STA, MU-BAR frame can additionally be used for soliciting responses. Modify the text to "Responses to A-MPDUs within a VHT MU PPDU or an HE MU PPDU that are not immediate responses to the VHT MU PPDU or the HE MU PPDU are transmitted in response to explicit BlockAckReq or explicit MU-BlockAckReq frames by the AP.". Revised- Agree in principal. TGax editor makes changes as shown in the as specified in 2487 "A non-AP STA that is the recipient, within a HE MU PPDU, of an MPDU that solicits an immediate response with Ack Policy '01' in QoS Control shall send the immediate response according to the scheduling information defined by the UL trigger information that is carried either in the Trigger frame(s) or in MAC header." When the HE AP transmits the VHT MU PPDU that is destined to VHT STAs and HE STAs, the VHT MU PPDU can also solicit immediate responses from the target HE STAs with Ack Policy '01'. Change the corresponding sentence as the following: "A non-AP STA that is the recipient, within a VHT MU PPDU or an HE MU PPDU, of an MPDU that solicits an immediate response with Ack Policy '01' in QoS Control field, shall send the immediate response according to the scheduling information defined by the UL trigger information that is carried either in the Trigger frame(s) or in MAC header." As per comment Rejected- VHT MU PPDU can not solicit immediate responses in UL MU format from the target HE STAs. It additional complexity to the receiver. 2396 The BA cannot be sent within EIFS duration in 20MHz bandwidth for MCS0 and Nss=1, even in single user case. Specific rules to transmit BlockAck frames or Multi-STA Insert the following sentence in the paragraph as below: When receiving multiple frames from more than one STA that are part of an UL MU transmission (Clause 9.42.2) and that require an Rejected- Regarding the below proposed wording, “If BlockAck or Multi-STA BlockAck frames are transmitted, it should be transmitted using
1182 Lei Huang 19.12 "When the Fragment Number subfield is 1" should be "When the Fragment Number subfield is 0" Change "When the Fragment Number subfield is 1" to "When the Fragment Number subfield is 0" REVISED. Please see DCN 11-16/868. 1143 Kwok Shum Au 19.31 is no BlockAck Bitmap field. Change "BlockAck Bitmap field" with "Block Ack Bitmap field". Accept 1286 Mark RISON 19.22 "When the Fragment Number subfield is 1" -- the ACK Type subfield needs to be 1 too Add to that effect Reject. The ACK Type value conditions are already mentioned at 19.09 962 kaiying Lv 19.00 change "when the Fragment Number subfield is 1" to "when the Fragment Number subfield is 0" as the comment REVISED. Please see DCN 11-16/868. 1287 Mark RISON 19.32 "for 4 fragments of each of the 16 MSDUs" -- what if the 16 are not all MSDUs, but some are A-MSDUs? Can they still be fragmented? Either say only the bit is used in the case of A-MSDUs, or add "or REVISED. A-MSDUs are not allowed to be fragmented. It is clarified in the Note. Please see below 831 Jinsoo Ahn 18.36 RA field of Multi-STA BA needs to be determined except for the case of single STA Insert the following "RA field of Multi-STA BA shall be set to identical value of TA field(MAC address of AP)" REVISED. Please see resolution to CID 2212 508 Dengyu Qiao 19.11 MAC Motion #72 (length indication of BA Bitmap subfield of M-BA) was approved but no corresponding spec text is present in the draft TBD REVISED. Please see DCN 11-16/868.
1288 Mark RISON 19.32 "for 4 fragments of each of the 16 MSDUs" -- the MSDUs might not be fragmented into 4 fragments Change to "for the up to the 4 fragments of each of the 16 MSDUs" REVISED. Please see DCN 11-16/868. 1814 Rojan Chitrakar 19.31 "16 subbitmaps", "16 MSDUs" may no longer be valid since the bitmap length may vary. Change 16 to "BA Bitmap length"/4. REVISED. Please see DCN 11-16/868.
IEEE P802.11 Wireless LANs Operating Mode Indication – PART Tx OMI (TOMI) Date: 2016-07-05 Author(s): Name Affiliation Address Phone email Jayh Park LGE Seocho R&D Campaus, Seocho-gu, Seoul South Korea +82-10-3646-7657 hyunh.park@lge.com Jarkko Kneckt Apple jkneckt@apple.com Alfred Asterjadhi Qualcomm Inc. aasterja@qti.qualcomm.com Reza Hedayat Newracom reza.hedayat@newracom.com Xing Weimin ZTE xing.weimin@zte.com.cn Robert Stacey Intel robert.stacey@intel.com Abstract This submission proposes resolutions for multiple comments related to TGax D0.1 with the following CIDs (13 CIDs): 95, 365, 656, 794, 1134, 1135, 1260, 2298, 2407, 2463, 2469, 2658, 2659 Revisions: Rev 0: Initial version of the document Rev 1: Incorporated editorial suggestions received during the F2F from Yongho, Brian, and Matt (changes highlighted in green)
Fields in the HE-SIG-A for an HE trigger-based PPDU Two Parts of HE-SIG-A Bit Number of bits Description Spatial “SR_allowed” signaling indicates whether SR operation is allowed or not. Other details are TBD. this part needs further development.(#2169)
IEEE P802.11 Wireless LANs Spec text for Date: 2016-07-08 Author(s): Name Affiliation Address Phone Joonsuk Kim Apple 1 Infinite Loop, Cupertino, CA 95014 Abstract This submission proposes resolutions for RU restriction rule for operating STAs related comment related to TGax D0.2 with the following CID: 854 Revisions: Rev 0: Initial version of the document. Interpretation of a Motion to 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 P.L Comment Proposed Change Resolution 854 Joonsuk Kim 26.3.7.1 Some of RUs are not usuable to STAs which operates with smaller bandwidth than OFDMA PPDU We need to restrict some RU to operate for such STAs; I will submit a proposal with details Revised Discussion: Presented in TGax Editor: Add the following new sub-clause 26.3.7.4 26.3.7.4 RU restriction rules when operating 20MHz
table-look up given Nuser. Instruction to Editor: TGax editor to make the changes shown in under all headings that include CID 311 Proposed Text Changes for CID 311 Instruction to Editor: Please insert the following sentence in TGax D0.2 P118 L 45 under subclause 26.3.9.8.5 CID 1002, 2036 CID Page. Line Clause Number Comment Proposed Change Proposed Resolution 1002 26.3.8.9.5 Clarify the STA-ID in the Table 26.19. The description reference to a MAC section is unclear and needs to be clarified Replace the sentence "The STA identifier that addresses a STA - reference to MAC section(?)" with the following sentence: "The STA-ID refers to the AID described in the section 8.4.1.8. The 11 LSBs of the AID field are used to address STAs in this field. Accepted Instruction to Editor: TGax editor to make the changes shown in under all headings that include CID 1002 2036 26.3.8.9.5 missing reference Replace "reference to MAC section(?)" with correct reference. DUPLICATE of CID 1002 in doc 16-928r1. Proposed Text Changes for CID 1002 Instruction to Editor: Please make the following changes in TGax D0.2 P120 L 13 subclause 26.3.9.8.5 CID 1003 CID Page. Line Clause Number Comment Proposed Change Proposed Resolution 1003 26.3.8.9.5 Clarify the STA-ID field in the Table 26.20. The description reference to a MAC section is unclear and needs to be clarified Replace the sentence "The STA identifier that addresses a STA - reference to MAC section(?)" with the following sentence: "The STA-ID refers to the AID described in the section Accepted. Instruction to Editor: TGax editor to make the changes shown in under all
2627 The draft doesn't include MIBs Add MIBs Revised- Agree in principle. TGah editor to make changes shown in under the heading for CID 2094, 1005, 2483, 2627, 2645, 2232, 2234 2645 The amendment adds MIB objects but contains not edits to Annex C Edit the MIB to include the MIB objects referenced in the draft Revised- Agree in principle. TGah editor to make changes shown in under the heading for CID 2094, 1005, 2483, 2627, 2645, 2232, 2234 2232 The parameter is not defined. Define in Annex C. Revised- Agree in principle. TGah editor to make changes shown in under the heading for CID 2094, 1005, 2483, 2627, 2645, 2232, 2234 2234 171.41 9.20.5.1 The parameter is not defined. Define in C. Revised- in principle. TGah editor to make changes shown in under the heading for CID 2094, 1005, 2483, 2627, 2645, 2232, 2234 Discussion: CID 2094, 1005, 2483, 2627, 2645, 2232, 2234 Agree in principle. TGah draft 1.0 is missing the Annex C. Propose: Revised for CID 2094, 1005, 2483, 2627, 2645, 2232, 2234, per discussion and editing instructions in ASN.1 encoding of the MAC and PHY MIB MIB Detail Change Dot11StationConfigEntry as follows:
MIB used to operate at sub 1 GHz." MODULE -- this module MANDATORY-GROUPS { dot11PhyS1GComplianceGroup, dot11PhyTxPowerComplianceGroup2, dot11S1GTransmitBeamformingGroup, dot11S1GComplianceGroup } -- OPTIONAL-GROUPS { } ::= { dot11Compliances 16 } TGah editor: Replace “dot11TravelingPilotCapability” with “dot11S1GTravelingPilotOptionActivated” TGah editor: Replace “travelling” and “Travelling” with “traveling” and “Traveling”respectively. TGah editor: Reeplace “dot11NDPPSPollSupport field equal to true” with “dot11NDPPSPollSupport equal to true”at Page 281 Line 38.
IEEE P802.11 Wireless LANs Comment Resolution on OBSS_PD Conditions in 25.9.3 Date: 2016-07-24 Author(s): Name Affiliation Address Phone Email James Wang Mediatek, Inc. 2840 Junction Avenue, San Jose, CA 95134 408 526-1899 James.Wang@Mediatek.com Po-Kai Huang Intel Yuichi Morioka Sony Laurent Cariou Jun Luo Huawei CID Clause Number Comment Proposed Change Resolution 706 25.9.3 63 57 "an HE STA is allowed to adjust the OBSS_PD threshold in conjunction with transmit power control" should be modified based on the SFD DCN132-16 P37L35 "adjustment rules formula Please update the adjustment rules for OBSS_PD trhehsold and transmit power as stated. Revised. OBSS_PD level adjustment rules are included. Instruction to editor: Please modify the text according to the changes under CID 706 Red Lined Text Change for the Proposed Resolutions: Changes to D0.1 Related to CID 706 In Clause 25.9.2, the additional TBD conditions at P63L46are described in Clause 25.9.3. Additionally, the adjustment rules for adjusting OBSS_PD level is provided in 5.1 of SFD. Instructions for Editor: P49L43 TGax editor: Remove the following sentence starting in line 41, page 63 of 11ax D0.1; P50L1
Chair asked if there are any objections to approve the TGax schedule as follow. are no objections. The TGax schedule is approved. Monday Tuesday Wednesday Thursday AM1 TGax (full, ad hoc) TGax (full) AM2 TGax (MAC) TGax (PHY) TGax (full) PM1 TGax (PHY) TGax (MAC) TGax (full) PM2 TGax (full) TGax (SR) TGax (MU) TGax (full) PM3 TGax (MAC) TGax (PHY) Presentations Bo Sun (ZTE) presented “Proposed Resolutions to comments on 26.2.2” based on the submission 11-16-0813-03 (on behalf of Ke Yao). Resolutions for the CIDs 1780, 370, 1923, 2517 and 1610 are proposed. TBDs are removed. Three parameters for the TXVECTOR and RXVECTOR are added. Discussion A member asked for offline discussion on additional parameters. There are two other related submissions. Next step Bo Sun to work with the authors of related submissions. Alfred Asterjadhi (Qualcomm) presented “EIFS,” based on the submission 11-16-0835-00. The of the document is EIFS, however it is mostly related to Discussion No discussion. Jeongki Kim (LG Electronics) presented “Comment Resolution on CID 783 (TXOP Duration Field),” based on the submission 11-16-0877-00. Text for TXOP Duration field was proposed. No discussion. Jeongki to work with Alfred. Po-Kai Huang (Intel) presented “Setting for TXOP Duration Field,” based on the submission 11-16-0951-00. Size of TXOP Duration field in HE-SIG-A has been decided. The setting rule of TXOP Duration remains TBD and is discussed in this contribution. Spec text contained in 16/953r0 which related to CID 2596 was also presented. A member has a suggestion on the proposed text.
Do you possess a driver license? If yes, list state and license number: Have your driving privileges ever been canceled, suspended, or revoked? If yes, explain: 20a. Have you ever used, or experimented with any illegal drug? If yes, explain: b. Have you ever sold, delivered, manufactured, smuggled, trafficked in illegal substances or drug paraphernalia? c. Have you ever possessed illegal substances or drug paraphernalia? 21a. Have you ever been convicted of a felony or a misdemeanor? b. Have you ever pled Nolo Contendere or pled guilty to a which is a felony or a misdemeanor? c. Have you ever had the adjudication of guilt withheld for a crime which is a felony or a misdemeanor (including sealed records)? d. If you answered "Yes" to 21 a, b, or c, complete the following: Date Place Agency Charge Disposition Details Are you or have you ever knowingly been under investigation by any local, state, federal agency, or entity for any wrongdoing either administrative, civil or criminal? If yes, explain: Have you ever committed a crime, whether arrested or not, that would constitute a felony or a misdemeanor? Yes No Have you ever been civilly or administratively adjudicated guilty to have engaged in any sexual abuse or sexual harassment? Have you now or have you ever had any affiliation with a known threat group “gang”? If so, describe the circumstances in detail.
What to do? Forms/tools When? Indicative timescales Plan the work , communicate with the team and set date to start. (Select a typical week(s)) Week 1-4 Draw out and analyse high level patient flow map. Appendix 1 Week 5-6 Record incoming queries and requests from all routes Appendix 2 1-4 week period Record appointment requests from all routes Appendix 3 1-4 week period Collect appointment activity data and lost activity and extras Appendices 7,8 1-4 week period Record appropriateness of consultations Appendix 4,5 1-2 week period Record and partner time available Appendix 6 At any point before week 16 Analyse the data (Demand, capacity and activity.) Appendices 9,10 Week 16-20 Discuss the analyses and any additional information such as annual access survey and patient and views Week 20-24 and submit the Practice Action Report Template by 15th March 2015 Appendix 11 Week 24 Step 1 Know your patients and practice Create a patient flow map Draw out a high level patient flow map, focussing on the patient’s journey from home into and through the practice. (Appendix 1 contains one for use or adaptation.) Identify and mark decision points, handoffs and other points that can result in delays for patients.
DC2200 Firmware Changes V 1.0.13 The fan voltage can be set from 6 V to 13 V with a resolution of 0.1 V and an accuracy of ±0.5 V. This can be done within the “System Setting”. Click on “more …” to go to page 2. The menu item “Fan Voltage” can be found there. Operation of non-Thorlabs LEDs and other light sources The DC2200 was designed to drive LEDs including non-Thorlabs LEDs. Thorlabs LEDs feature an EEPROM which stores all relevant data about the LED including the forward voltage. A test function was created for the operation of non-Thorlabs LEDs. A small current of 5 mA is driven and the resulting voltage is measured. Assuming a characteristic current-voltage (I-V curve), the maximum voltage is calculated and set as the maximum forward voltage. If the LED has an additional ohmic resistance due to large conductors, the calculated forward voltage may be too small. This results in a “LED output voltage protection was tripped – check connection.” error. The LED will be switched off. “Meas Head” function is After clicking on the “Test Head” button in the “LED Setting” menu an additional button “Meas Head” appears (only when non-Thorlabs light sources without an EEPROM are connected). This function drives different currents up to the “User Current Limit” and measures the resulting voltage. The max forward voltage is determined and the light source can be driven up to its maximum current without errors.
can also be true. fewer participants can be included in the experiment. is less variance among means of samples than if the null hypothesis were not true. the estimate of the population variance is smaller than the estimate. A population is normally distributed with μ = 50, σ = 8, and N = 10. The shape of the distribution of means in this example is __________. If the mean score on a stress scale is 5, the standard deviation is 2, and the distribution is normal, what would be the mean value when converted to a Z-distribution?