Comparison of Draft Spec Framework Documents Month Year doc.: IEEE 802.11-yy/xxxxr0 Comparison of Draft Spec Framework Documents Date: 2009-09-22 Authors: John Doe, Some Company

Context and Introduction Month Year doc.: IEEE 802.11-yy/xxxxr0 Context and Introduction There have been two draft spec framework documents submitted to Tgac: Document 09/633r1, “Strawmodel 802.11ac Specification Framework” Document 09/992r0, “Proposed Specification Framework for Tgac” The formats of the two document differ significantly but there is a lot of overlap in terms of feature content The purpose of this document is to identify the differences in feature content between the two documents John Doe, Some Company

Top Level Feature Content Comparison* Month Year doc.: IEEE 802.11-yy/xxxxr0 Top Level Feature Content Comparison* Doc 09/633 r1 Doc 09/992 r0 20/40/80 MHz Operation Yes DL MU-MIMO Multi-Channel Operation No OBSS Management UL MU-MIMO * Table entry indicates whether the feature is included in the document referenced John Doe, Some Company

Back Up Relevant Excerpts from document 09/633r1 Month Year doc.: IEEE 802.11-yy/xxxxr0 Back Up Relevant Excerpts from document 09/633r1 John Doe, Some Company

Multiple Channel Access Month Year doc.: IEEE 802.11-yy/xxxxr0 Multiple Channel Access Purpose Enable access on a set of multiple channels Required Inputs NA Expected Outputs CCA Methodology for multiple channels Protocols for assigning STAs to channels Protocols for aggregating channels to a single STAs Protocols for access on multiple channels Channel Switching Protocol Link Adaptation Frame Formats and Field Descriptions Proposed Performance Metrics Uplink/Downlink Data Throughput at the MAC SAP Channel usage efficiency Packet transfer latency from the Tx MAC SAP to Rx MAC SAP Packet loss rate subject to application latency requirements Dependencies VHT SIG field Block Ack Scheduling Possible Directions Synchronous Contiguous Multi Channel Synchronous Non-Contiguous Multi Channel Asynchronous Non-Contiguous Multi Channel John Doe, Some Company

OBSS Management Purpose Required Inputs Expected Outputs Month Year doc.: IEEE 802.11-yy/xxxxr0 OBSS Management Purpose Preserve or increase the system throughput of OBSS's when compared to the case of 802.11n OBSS. Required Inputs TBD Expected Outputs OBSS management protocol, which includes a MU-MIMO frame sequence that can set the NAV at an OBSS Proposed Performance Metrics Throughput and delay statistics of OBSS's in the presence of BSS Dependencies Downlink/Uplink MU-MIMO protocol Multichannel protocol Possible Directions Protocol considering multichannel, MU-MIMO and 802.11aa OBSS protocols Dynamic Frequency Selection Transmit Power Control Channel Switching Protocol Slide 6 Page 6 John Doe, Some Company

Uplink MU-MIMO Protocol Month Year doc.: IEEE 802.11-yy/xxxxr0 Uplink MU-MIMO Protocol Purpose Enable efficient MU-MIMO for Uplink Data Transmission Required Inputs NA Expected Outputs Uplink MU-MIMO transmission protocol including Control Message sequence Frame formats and Field Descriptions Coexistence with 11a/n Transmit Power Control Channel Sounding Protocol DL Block Ack Protocol Link Adaptation Protocol Proposed Performance Metrics Uplink Data Throughput at the MAC SAP Packet transfer latency from the Tx MAC SAP to Rx MAC SAP Packet loss rate subject to application latency requirements Dependencies Channel sounding protocol Channel reservation protocol for multiple STAs DL Block Ack transmission to multiple STAs VHT SIG Field Design Possible Directions TBD John Doe, Some Company