1 / 10

A Proposed Usage Model Methodology for High Throughput Task Group

A Proposed Usage Model Methodology for High Throughput Task Group. Adrian Stephens ( adrian.p.stephens@intel.com ) Eldad Perahia ( eperahia@cisco.com ) Sean Coffey ( coffey@ti.com ). Methodology Goals.

jedv
Download Presentation

A Proposed Usage Model Methodology for High Throughput Task Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Proposed Usage Model Methodology for High Throughput Task Group Adrian Stephens (adrian.p.stephens@intel.com) Eldad Perahia (eperahia@cisco.com) Sean Coffey (coffey@ti.com) Adrian Stephens, Intel et al

  2. Methodology Goals • To allow measurement of properties of a proposal so that it can be evaluated against our criteria • To be adequately realistic • To be as simple as this permits • To get a common set of assumptions • To allow apples-apples comparison Adrian Stephens, Intel et al

  3. Goals of this submission • To get agreement to the methodology • Agreement to the principle, not the details • Straw Poll • Highlight that lots of TBDs need to be researched • We can work on the methodology in this meeting • But need to go away and look for figures • Call for interest in setting up a special committee to fill in the TBDs Adrian Stephens, Intel et al

  4. Use Cases / Scenarios • Enterprise • Planned “cellular” deployment • Hot spot • Large numbers of clients • Uncoordinated deployment of APs from different vendors and by different service providers • Home • Mix of multimedia and data • Mixed • Mix of co-channel legacy and HT devices • + others TBD (e.g. backhaul) Adrian Stephens, Intel et al

  5. Web Browsing Email File server Instant Messaging Interactive Video (e.g. netmeeting) + others we haven’t thought of yet Video Gaming HDTV High Quality Audio VoIP phones File sharing Backup Applications Adrian Stephens, Intel et al

  6. Application Types • TCP vs UDP, “Down” vs “Up” • TCP application follows a repeating: wait, transmit request, wait for response cycle. • UDP application follows a wait, transmit cycle • Each application has specified distributions for: • Wait duration • Request length (“up” applications) • Response length (“down” applications) Adrian Stephens, Intel et al

  7. Application Specification (example) … + the other applications Adrian Stephens, Intel et al

  8. Usage model specification • For each usage model specify: • Number of STA • For each STA: • List applications running on that STA • e.g. STA1 (HDTV), STA2 (backup), STA3 (email + web browsing + interactive video). • Channel model type & Range of BSS • e.g. Domestic, NLOS, 20m Adrian Stephens, Intel et al

  9. Other model details • STA are distributed randomly (uniform distribution) within BSS defined by usage model range • Measurements performed over at least 5 minutes of run time • Measurements to be averaged over TBD multiple random STA position configurations Adrian Stephens, Intel et al

  10. Where do we go from here? • A special committee is proposed to develop a usage model using the methodology described here. • Major decisions will always be taken by the TG, but we don’t have time to debate each of the parameters in a usage model. • Contributions are solicited from members to: • share results of research between meetings • coordinate presentations on usage models • with the aim of providing the unknowns in the current framework • Straw Poll for interest. Adrian Stephens, Intel et al

More Related