July 2008 doc IEEE 802 11 080910 r

  • Slides: 12
Download presentation
July 2008 doc. : IEEE 802. 11 -08/0910 r 0 MAC Component Breakdown Topics

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 MAC Component Breakdown Topics for Discussion Authors: Submission Date: 2008 -07 -17 1 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Abstract This presentation introduces

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Abstract This presentation introduces some conditions that can lead to network overload due to excessive RRM and/or WNM frames. Submission 2 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Outline • • •

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Outline • • • Problem statement Overload Examples Considerations Possible Solutions Straw Polls Submission 3 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Problem statement • RRM/WNM

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Problem statement • RRM/WNM frames are meant to characterize and help optimize the wireless network. • But, overuse of those frames could itself overwhelm the network to the point of complete failure (due to bandwidth starvation for real data laden frames). Submission 4 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Overload Examples • •

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Overload Examples • • • measurements diagnostics event logs syslog dump location tracking Submission Scenarios with great potential for network overload by RRM/WNM frames that can overwhelm real data laden frames. 5 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Considerations • A specific

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Considerations • A specific deployment may constitute a system that ONLY does location tracking, e. g. in a warehouse application, so that might be acceptable. • But, in a normal multi-use network deployment RRM/WNM frames could overwhelm normal data frames. In particular delivery of high priority, time sensitive data like VOIP data frames could be compromised. Submission 6 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Possible Solutions • Add

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Possible Solutions • Add QOS header to MMPDUs – set lowest priority for RRM/WNM frames • Duty cycle limit RRM/WNM frames • Other? Submission 7 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Straw Polls • Is

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Straw Polls • Is this an important issue? Y/N • Approach preference? – QOS header – Duty cycle limits Submission 8 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 References • 1. IEEE

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 References • 1. IEEE Std. 802. 11 -2007 • 2. P 802. 11 v_D 3. 0. pdf Submission 9 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Revisions • r 0

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Revisions • r 0 – 2008 -07 -17 First presentation to TGv. Submission 10 Darwin Engwer, Nortel Networks

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Backup Slides Submission 11

July 2008 doc. : IEEE 802. 11 -08/0910 r 0 Backup Slides Submission 11 Darwin Engwer, Nortel Networks

July 2008 Submission doc. : IEEE 802. 11 -08/0910 r 0 12 Darwin Engwer,

July 2008 Submission doc. : IEEE 802. 11 -08/0910 r 0 12 Darwin Engwer, Nortel Networks