January 2011 doc IEEE 802 11 110184 r

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 802. 11 ah Spec Development Discussion Document Date: 2010 -11 -08 Authors: Submission Slide 1 Rolf de Vegt (Qualcomm))

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Contents • Context and Introduction • Learnings from past. 11 projects that address PHY and MAC elements • Example of the 802. 11 ac Process • Unique Characteristics of 802. 11 ah • Topics to be addressed regarding. 11 ah proposal development • Strawpolls Submission Slide 2 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Context and Introduction • Taskgroup 802. 11 ah is chartered to develop an Industry Standard specification that is projected to enable a number of new, high volume use cases for 802. 11 technology • Up to this point there has been limited discussion amongst taskgroup members about: – The process to be followed for achieving wide industry support / consensus about a specification – The foundational documents required for the development of a successful industry standard • This document provides a point of view regarding spec development processes and a series of strawpolls to assess taskgroup sentiment on this topic Submission Slide 3 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Learnings from other standards groups developing PHY / MAC standards • Taskgroups typically develop a common understanding of the process to be followed for the development of a specification, prior to the commencement of actual spec development work • Taskgroups typically adopt a channel model document and a functional requirement documents prior to considering proposal submissions • The process of continuous down selects of competing proposals that has historically been followed has contributed to considerable delays in the standardization process due to stalemated debates between competing proposal groups Submission Slide 4 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Overview of. 11 ac Spec Development Process Source: 11 -9/0059 r 6 Submission Slide 5 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Sample Content of Spec Framework Document • The. 11 ac Spec Framework document (11 -09/0992 r 21) has been updated by TGac Motion as the addition of new functionality has obtained sufficient support • Sample Content of the Spec Framework Document: A VHT mixed format (MF) preamble shall be supported in the draft specification and device support is mandatory. The VHT mixed format preamble shall have the following characteristics: R 3. 2. 1. A: Robust legacy 11 a deferral. The VHT MF preamble shall be designed such that a legacy 11 a device will defer for the duration of the transmission to the same degree that it does for an HT MF preamble. R 3. 2. 1. D: The VHT MF preamble shall include training for a wider channel 1 to 8 spatial streams (see Section 3. 4) DL MU-MIMO R 3. 2. 1. E: Since the HT SIG field cannot be expanded without breaking backward compatibility, the VHT MF preamble shall include VHT SIG fields. The VHT SIG fields may include signaling for the following: a) wider bandwidth b) enhanced MCS (see Section 3. 3) c) more spatial streams (see Section 3. 4) Submission Slide 6 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Unique Characteristics of 802. 11 ah • TGah has participants from various backgrounds, with different experiences regarding spec development processes – E. g. 802. 11, 15. 4, new participants • The unique use cases that are being discussed drive significantly different requirements from ‘traditional Wi-Fi’ – – – ‘Thousands of STA’s per BSS’ Short, bursty traffic at large time intervals Extreme low power consumption Range up to 1 km, outdoor Relatively narrow frequency band • Significantly different propagation characteristics than traditional 2. 4 and 5 GHz Wi-Fi – Frequency band – Outdoor usage Submission Slide 7 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Topics to be addressed by TGah • Establishing taskgroup consensus around a spec development process to be followed • Determine whether the taskgroup will develop a Usage Model document • Determine whether the taskgroup should develop and maintain a Channel Model document • Determine whether the taskgroup should develop a Functional Requirements document • Determine whether spec development should occur after consensus has been reached on Channel Model and Functional requirements, or in parallel Submission Slide 8 Rolf de Vegt (Qualcomm)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Strawpolls (Yes/No/Abstain) 1. TGah shall develop and adopt a Specification Development process (aka ‘Selection Procedure’) document (56/0/2) 2. TGah shall develop and adopt a Usage Model document (58/0/0) 3. TGah shall develop and adopt a Channel Model document – no one indicates they want to vote ‘no’ 4. TGah shall develop and adopt a Functional requirements document (41/0/18) 5. TGah shall adopt Draft specification text after the taskgroup has adopted a Spec Development process document, Functional Requirements document and Channel Rolf de Vegt (Qualcomm) Submission Slide 9 Model document (34/7/12)

January 2011 doc. : IEEE 802. 11 -11/0184 r 0 Motion • TGah shall develop and adopt a Specification Development Process document • Move: Rolf de Vegt • Second: Paul Lambert Motion passes unanimous consent Submission Slide 10 Rolf de Vegt (Qualcomm)