doc.: IEEE /0034r0 Submission January 15, 2009 Grodzinsky / De VegtSlide ac and ad Usage Models Documents Proposal Date: Authors:

doc.: IEEE /0034r0 Submission January 15, 2009 Grodzinsky / De VegtSlide ac and ad Usage Models Documents Proposal Submission for the January 2009 IEEE Joint VHT Group Meeting in Los Angeles, CA

doc.: IEEE /0034r0 Submission January 15, 2009 Grodzinsky / De VegtSlide 3 Context and Introduction In November document 08/1323 (Introduction to VHT Usage Models was presented) This submission provided an overview of the purpose, contents and scope of: –the Usage Model Document that was developed in Taskgroup 11n –the VHT Usage Model Document submitted by the WFA* –Furthermore a set of open questions and proposed next steps regarding the Usage Model activities for the VHT Taskgroups were identified This document contains a proposal for how to get started with the creation of Usage Model Documents for ac and ad * Document IEEE / )

doc.: IEEE /0034r0 Submission January 15, 2009 Grodzinsky / De VegtSlide 4 Proposal WFA created a submission on Usage Models for the VHT Studygroup (document 07/ ) –6 Usage Model Categories and 21 Usage Models were identified and described –WFA submission does not contain an assessment of likely technology fit with.11ac versus.11ad –Review of the 21 Usage Models leads to the conclusion that some Usage models will be a better fit with.11ac technology, some with.11ad technology and some may arguably be enabled by both Proposal is to create 2 separate Usage Model ‘Starter documents’ –802.11ac Usage Model ‘Starter Document’ –802.11ad Usage Model ‘Starter Document’ Each taskgroup to manage changes and additions to the Usage Model document independently from here-on –Main role of the Usage Model is to serve as input to the definition of Functional Requirements (and Simulation Scenarios) for the specification

doc.: IEEE /0034r0 Submission January 15, 2009 Grodzinsky / De VegtSlide 5 Next Steps Agreement with this approach? Identify volunteers / editors for the respective documents Each group to discuss potential additions and changes to the Usage Model documents Each group to identify relevant Functional Requirements (and Simulation scenarios) based on the Usage Model documents