Upload
evan-mason
View
213
Download
0
Embed Size (px)
Citation preview
May 2003
Adrian Stephens, Intel et al
Slide 1
doc.: IEEE 802.11-03/327r0
Submission
A Proposed Usage Model Methodology for High Throughput
Task Group
Adrian Stephens ([email protected])
Eldad Perahia ([email protected])
Sean Coffey ([email protected])
May 2003
Adrian Stephens, Intel et al
Slide 2
doc.: IEEE 802.11-03/327r0
Submission
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
May 2003
Adrian Stephens, Intel et al
Slide 3
doc.: IEEE 802.11-03/327r0
Submission
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
May 2003
Adrian Stephens, Intel et al
Slide 4
doc.: IEEE 802.11-03/327r0
Submission
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)
May 2003
Adrian Stephens, Intel et al
Slide 5
doc.: IEEE 802.11-03/327r0
Submission
Applications
• 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
May 2003
Adrian Stephens, Intel et al
Slide 6
doc.: IEEE 802.11-03/327r0
Submission
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)
May 2003
Adrian Stephens, Intel et al
Slide 7
doc.: IEEE 802.11-03/327r0
Submission
Application Specification (example)
Datagram size Idle time Application Traffic Type
Offered Load
Distribution Type
Average value
Distribution Type
Average value
Web Browsing
TCP downlink
TBD TBD 4KB TBD 40s
TCP downlink
TBD TBD TBD TBD TBD Email
TCP uplink
TBD TBD TBD TBD TBD
… + the other applications
May 2003
Adrian Stephens, Intel et al
Slide 8
doc.: IEEE 802.11-03/327r0
Submission
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
May 2003
Adrian Stephens, Intel et al
Slide 9
doc.: IEEE 802.11-03/327r0
Submission
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
May 2003
Adrian Stephens, Intel et al
Slide 10
doc.: IEEE 802.11-03/327r0
Submission
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.