Doc.: IEEE 802.11-07/2814r0 Submission Slide 1 Performance implications of wireless mesh coexistence with WLANs Notice: This document has been prepared.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0028r0 Submission July 2006 Steve Shellhammer, QualcommSlide 1 Coexistence Scenario – A Pair of Unlicensed Wireless Networks Notice:
Advertisements

Doc.: IEEE /0029r0 Submission July 2006 Steve Shellhammer, QualcommSlide 1 Coexistence Scenario – A Pair of Unlicensed Wireless Networks, one.
Doc.: IEEE /0916r0 Submission September 2005 Slide 1 Adjacent channel interference and its impact on the Mesh MAC Date: Authors: Notice:
Doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 1 Advantages of multiple channel usage in 11s WLAN Mesh network Notice: This document.
Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
Doc.: IEEE /2910r0 Submission November 2007 Mathilde Benveniste, Avaya LabsSlide 1 Simplified ‘Express’ Forwarding for single-channel wireless.
Doc.: IEEE /0024r0 Submission May 2006 Steve Shellhammer, QualcommSlide 1 Discussion of Coexistence Scenarios Notice: This document has been prepared.
Doc.: IEEE /0094r0 Submission November 2009 Steve Shellhammer, QualcommSlide 1 Comments on PAR Notice: This document has been prepared.
Doc.: IEEE /2180r0 SubmissionM. Benveniste (Avaya Labs) Some Simulation Results for ‘Express Forwarding’ Notice: This document has been prepared.
doc.: IEEE /1059r0 Submission July 2006 Mathilde Benveniste, Avaya LabsSlide 1 Next generation MAC Notice: This document has been prepared to.
Doc.: IEEE /0644r2 Submission May 2006 Päivi Ruuska, NokiaSlide 1 Measurement Pilot Transmission Information as optional information in Probe.
Doc.: IEEE /0619r1 Submission May 2008 M. Benveniste (Avaya Labs) Scheduled service periods in wireless mesh Notice: This document has been prepared.
Doc.: IEEE /0340r0 Submission April 2005 Marianna Goldhammer, AlvarionSlide 1 CBP-SG Contention Based Protocol and QoS Notice: This document.
Doc.: IEEE /0569r0 Submission April 2006 Tomoko Adachi, Toshiba CorporationSlide 1 Performance evaluation of 40MHz transmission - regarding CCA.
Doc.: IEEE /1212r0 Submission TGT and MEF Liaison Notice: This document has been prepared to assist IEEE It is offered as a basis for.
Doc.: IEEE /0003r0 Submission January 2006 Peter Ecclesine, Cisco SystemsSlide 1 Multiple Access and Effects of Aggregation Notice: This document.
Doc.: IEEE /0028r0 Submission January 2005 Eleanor Hepworth, Siemens Roke ManorSlide 1 Definitions and Terminology Notice: This document has been.
Doc.: IEEE /0197r0 Submission March 2005 Nancy Cam-Winget et alSlide 1 TAP & JIT Merge Process Notice: This document has been prepared to assist.
Doc.: IEEE /0619r0 Submission May 2008 M. Benveniste (Avaya Labs) Scheduled service periods in wireless mesh Notice: This document has been prepared.
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
Doc.: IEEE /0076r0 Submission Jan 2006 Tom Siep, Cambridge Silicon Radio PlcSlide 1 Coexistence TAG Liaison Report Notice: This document has been.
Performance implications of wireless mesh coexistence with WLANs
[ Interim Meetings 2006] Date: Authors: July 2005
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
Splicing in a Mesh Network
[ Considering of Intra-cell multiple CBP response]
March 2014 Election Results
[ Policies and Procedure Summary]
Motion to accept Draft p 2.0
[place presentation subject title text here]
Coexistence issues for single-channel wireless mesh
(Presentation name) For (Name of group) (Presenter’s name,title)
Coexistence problem of s Congestion Control
Splicing in a Mesh Network
On Coexistence Mechanisms
[Comparison between CDMA Code and Contention-based Access]
TGu-changes-from-d0-02-to-d0-03
November Opening Report
On Coexistence Mechanisms
Reflector Tutorial Date: Authors: July 2006 Month Year
Coexistence problem of s Congestion Control
MAC Extensions for Increasing Aggregate WLAN Throughput
Experimental DTV Sensor
IEEE P Wireless RANs Date:
More on Performance Evaluation of ‘Express Forwarding’ for Mesh
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
May 2006 doc.: IEEE /0601r0 May 2006 Handling the Groupcast Sequence Number for Proxied Device in Multihop Mesh Date: Authors: Notice:
TGy draft 2.0 with changebars from draft 1.0
Solution for 40MHz in 2.4 GHz band
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November 2007 Effect of Contention Window Size on ‘Express Forwarding’ Performance for Single-Channel Mesh Date: Authors: Name Address Company.
Leader based Multicast
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
Liaison Report From Date: Authors: Month Year
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
Some Simulation Results for ‘Express Forwarding’
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
Discussion of Coexistence Scenarios
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Presentation transcript:

doc.: IEEE /2814r0 Submission Slide 1 Performance implications of wireless mesh coexistence with WLANs Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. Date: Authors: NameAddressCompanyPhone Mathilde Benveniste 233 Mt Airy Road Basking Ridge, NJ 07920, US Avaya

doc.: IEEE /2814r0 Submission Slide 2 Performance implications of wireless mesh coexistence with WLANs Mathilde Benveniste

doc.: IEEE /2814r0 Submission Slide 3 Introduction Reference: “Wireless mesh networks: Performance implications for WLANs,” M. Benveniste, Interop New York, Oct WLANs (wireless LANs)* operate in the 2.4 GHz and 5 GHz unlicensed RF bands Wireless mesh networks will operate on the same RF spectrum QoS challenges arise for VoIP and multimedia –if mesh multi-hop transmissions use a single channel, which is also used by WLANs nearby _______ *The WiFi Alliance certifies WLAN devices for compliance with IEEE standard

doc.: IEEE /2814r0 Submission Slide 4 Enterprise Wireless Mesh MP- AP MP-Printer MP-PDA MP-Camera MP-Portal Converged “Wired” Enterprise Networking Infrastructure c Wireless/ Wireline Demarcation Point Switch/Router Wireless Mesh Laptop WiFi telephone Non-mesh End-User Devices MP-HDTV MP-Desktop (Managed) Service Provider Network IP Network

doc.: IEEE /2814r0 Submission Slide 5 About meshes Purpose of a wireless mesh –to extend the area of wireless broadband and eliminate need for much wiring –for temporary extensions to LAN/WLANs (such as trade shows or multi-venue sporting events) without re-working wiring/cabling Mesh characteristics –Mesh points will typically not be able to hear most of the mesh points other than their neighbors –The neighbor of a neighbor will likely be a hidden node

doc.: IEEE /2814r0 Submission Slide 6 Wireless Mesh and WLAN Wired Network Portal Mesh Point Mesh AP Station Multi-hop transmission 11 WLAN AP Station

doc.: IEEE /2814r0 Submission Slide 7 QoS Challenges in meshes 1.Traffic Concentration Points 2.“Hidden Node” Collisions 3.Correlated Traffic: Multi-hop Flows

doc.: IEEE /2814r0 Submission Slide 8 Traffic Concentration Points  Without proper traffic engineering, bottlenecks arise, which increase the latency experienced by VoIP/ multimedia frames Sufficient radios must be available at traffic concentration points, such as the point of interface with wired network Single radio mesh points are inadequate for a wireless mesh used to connect multiple fully loaded APs  Multi-channel (-radio) mesh needed as backbone for WLAN networks Single-channel mesh simply extends coverage range of a WLAN through multiple-hop transmissions

doc.: IEEE /2814r0 Submission Slide 9 “Hidden node” collisions in single-channel mesh  Because of hidden nodes, a mesh using a single channel with CSMA/CA (or EDCA) for access experiences more collisions than a BSS (where most stations hear each other)  Hidden node collisions may repeat on retransmission and lead to dropped frames, even in light traffic  The problem is exacerbated in the presence of multi-hop transmissions, leading to substantial delays

doc.: IEEE /2814r0 Submission Slide 10 Examples

doc.: IEEE /2814r0 Submission Slide 11 Acknowledgment induced collision A and C cannot hear each other B experiences a collision when D sends acknowledgement to C A must retry transmission F EDC (((((((( ACK X Hidden node Tx Fig 1 A B

doc.: IEEE /2814r0 Submission Slide 12 Single transmission failures A cannot hear either C or D B experiences a collision when C transmits A BCD Tx (((((((( X Hidden node Fig 2 D Remedy: Use large backoff window on retransmission X ACK (((((((( RTX Hidden node If D’s ACK collides with the retransmission, A must retransmit again If D’s ACK collides with the ACK to A’s retransmission, C must retransmit

doc.: IEEE /2814r0 Submission Slide 13 Hidden node collision ‘loop’ A and D cannot hear each other C cannot receive when A transmits B cannot receive when D transmits A and D retransmit unsuccessfully until retry limit is reached Without a remedy, both frames will be dropped! A B Tx X C D (((((((( (((((((( X Fig 3 Remedy: Use large backoff window on retransmission

doc.: IEEE /2814r0 Submission Slide 14 Correlated Traffic: Multi-hop Flows exacerbate contention  When a multi-hop flow frame causes a hidden node collision to another frame, the latter could experience substantial delay  Successful retransmission may be delayed for any of the following: The same hidden node collisions repeat on retransmission Another collision may be experienced with the forwarded frame The frame experiencing collision will yield the channel to forwarded frames because of its longer retry window

doc.: IEEE /2814r0 Submission Slide 15 A and C cannot hear each other D cannot receive when A transmits B cannot receive when C transmits A and C retransmit repeatedly without success Without a remedy, both frames will be dropped Hidden node collision loop & correlated transmissions A B D C (((((((( (((((((( Tx X X Fig 4 E Remedy: Use large backoff window on retransmission & Express Forwarding for multi-hop flow Tx If transmission to D succeeds, D’s forwarded frame will preempt A’s retransmission due to A’s longer backoff A’s transmission is delayed The sooner D completes its transmission the sooner A will be able to transmit

doc.: IEEE /2814r0 Submission Slide 16 Acknowledgment induced collision & correlated transmissions A cannot hear C or D, and vice versa B experiences a collision when D sends acknowledgement to C A must retry transmission F EDC ACK Tx (((((((( X Hidden node Tx Fig 5 A B Tx D and E will preempt A’s retransmission due to A’s the longer backoff A’s transmission is delayed The sooner D and E complete their transmissions the sooner A will be able to transmit Remedy: Use Express Forwarding

doc.: IEEE /2814r0 Submission Slide 17 “Express Forwarding” Reference: ‘Express’ Forwarding for Single-Channel Wireless Mesh, M. Benveniste, IEEE Doc  “Express forwarding” is a prioritization method for multi-hop transmissions Can be used selectively for VoIP/multi-media  Prioritization thru next hop reservation The Duration field on the frame is extended to keep all other neighbors silent longer Simulation results show substantial latency reduction (50-95%) Tx Hop 1 Channel reservation Tx Hop 2 Channel reservation time

doc.: IEEE /2814r0 Submission Slide 18 Example Reference: “Performance Evaluation of ‘Express Forwarding’ for a Single-Channel Mesh,” M. Benveniste and K. Kaustubh, IEEE Doc g Mesh Mix of multi-hop and single-hop VoIP calls and video users transmitting on the same channel as an independent WLAN Single mesh portal Data rate 54 Mbps; Ack rate 24 Mbps

doc.: IEEE /2814r0 Submission Slide 19 P VIDEO (L) VIDEO (H) VIDEO (L) VOIP  If the ACK from 2 (or 3) causes collision at Node 6, retransmission of frame from Node 25 will wait till multi-hop TX P->5 completes  The sooner the latter completes, the sooner the transmission 25->6 will complete  Express Forwarding reduces time of transmission P->5, thus shortens delay for flow 25->6  With Express Forwarding, the ACK from Node 2 prevents collision by Node 25 with subsequent transmission from Node 2 ANIMATED A collision with the ACK leads to longer backoff for Node25 Nodes 2, 3, 4 & 5 likely to draw shorter backoff than Node25 Data Range Ack Range 802. Fig g Network

doc.: IEEE /2814r0 Submission Slide 20 Mean Delays Delays are substantially shorter without the multi-hop flows Express Forwarding reduces the negative effect of multi-hop flows on other traffic

doc.: IEEE /2814r0 Submission Slide 21 Conclusions Multi-radio/channel meshes must be used to alleviate heavy traffic concentration In a single channel mesh, hidden node collisions and multi-hop flows can cause severe delays and/or dropped packets Remedies include large backoff windows on retransmission and Express Forwarding for multi-hop flows

doc.: IEEE /2814r0 Submission Slide 22 References 1.“Wireless mesh networks: Performance implications for WLANs,” M. Benveniste, Interop New York, Oct “‘Express’ Forwarding for Single-Channel Wireless Mesh, M. Benveniste”, IEEE Doc r1 3.“Draft Text Changes for ‘Express Forwarding’ in a Mesh, M. Benveniste”, IEEE Doc r1 4.“Performance Evaluation of ‘Express Forwarding’ for a Single-Channel Mesh”, M. Benveniste and K. Kaustubh, IEEE Doc r1