Doc.: IEEE 802.11-05/0247r1 Submission March 2005 Atsushi FujiwaraSlide 1 Advantages of multiple channel usage in 11s WLAN Mesh network Notice: This document.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Advertisements

Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
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 /0072r0 SubmissionS. Filin H. Harada, NICTSlide 1 Coexistence algorithms Notice: This document has been prepared to assist IEEE
Doc.: IEEE /0054r0 Submission May 2011 Slide 1Hyunduk Kang, et al, ETRI Discussion on mode of management service Notice: This document has been.
Doc.: IEEE /2237r0 Submission July 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D1.0 Insert and Deletion Notice: This document has been.
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 /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 /0460r1 Submission March 2006 Fujio Watanabe, DoCoMo USA LabsSlide 1 Japanese Emergency Call Regulation Notice: This document has been.
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
LB84 General AdHoc Group Sept. Closing TGn Motions
[ 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
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
(Presentation name) For (Name of group) (Presenter’s name,title)
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
Self-organizing and Auto-configuring Mesh Networks
On Coexistence Mechanisms
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
Selection Procedure Recommendation
IEEE P Wireless RANs Date:
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
Advantages of multiple channel usage in 11s WLAN Mesh network
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Timeline Date: Authors: July 2005 July 2005
TGr Proposed Draft Revision Notice
WNG SC Closing Report Date: Authors: July 2006 July 2006
Presentation transcript:

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 1 Advantages of multiple channel usage in 11s WLAN Mesh network 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: 2005-Mar-17 Authors:

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 2 Abstract This presentation discusses advantages on usage of multiple channels and requirements of channel setting technology for 11s mesh network

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 3 Contents Requirements Scenario for Single WLAN interface model Advantage on usage of Multiple channels Required technology for Multi WLAN interface model Suggestions for 11s amendment

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 4 Requirements Channel unification mechanism shall be defined to ensure the connectivity between Mesh APs –Single WLAN interface case and Single channel Framework to build the optimization technology for Multi WLAN Interface network must be defined –Channel Setting Algorithm itself shall be out of scope –Framework must be defined Measurement in multi hop network TPC/DFS in multi hop network 11h/k extension for WLAN mesh network

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 5 Single WLAN Interface Case Requirement of channel setting in mesh network All MAPs shall use the same channel to establish mesh network even in such cases: –simultaneous power on –merge of multiple mesh network Channel unification mechanism shall be standardized Power on scan Power on

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 6 Multiple WLAN Interface Case Requirement of channel setting in mesh network Multiple channel usage will be solutions to some issues on mesh networks –Load balancing –QoS Support –Hidden / Exposed terminal problem Frameworks to support multiple WLAN interfaces shall be standardized –DFS, TPC, Measurement for mesh network –should be extension of 11k and 11h amendment for mesh network

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 7 TCP Throughput degradation due to exposed terminal problem End-to-end throughput (Mbps) Case 1 Case 2 Case 1 Case 2 Carrier Sense Range TCP Throughput degradation due to exposed terminal problem Using different channel between the first and third hop recovers this degradation How to select channel in more complicated case?

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 8 Usage of multiple channel for solving exposed terminal problem (1/7) Mesh network example by 6 nodes M1 M2 M3 M4 M6 M5

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 9 Usage of multiple channel for solving exposed terminal problem (2/7) While nodes 1 and 2 are communicating… M1 M2 M3 M4 M6 M5 L12 – L34 L12 – L45 L12 – L46 Constraints to avoid exposed terminal problem

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 10 Usage of multiple channel for solving exposed terminal problem (3/7) While nodes 1 and 3 are communicating… M1 M2 M3 M4 M6 M5 Constrains to avoid exposed terminal problem L12 – L34 L12 – L45 L12 – L46 L13 – L26 L13 – L46 L13 – L56

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 11 Usage of multiple channel for solving exposed terminal problem (4/7) Derivation of chromatic graph M1 M2 M3 M4 M6 M5 L26 L12 L34 L46 L45 L15 L13 L56 L23 L12 – L34 L12 – L45 L12 – L46 L13 – L26 L13 – L46 L13 – L56 L23 – L15 L23 – L45 L23 – L56 L45 – L12 L45 – L23 L45 – L26 L46 – L12 L46 – L13 L46 – L15 L56 – L13 L56 – L23 L56 – L34 Constraints to avoid exposed terminal problem

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 12 Usage of multiple channel for solving exposed terminal problem (5/7) All possible patterns in 5-MAPs mesh network (21 patterns)

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 13 Usage of multiple channel for solving exposed terminal problem (6/7) tota l Channels MAPs Number of required channels for all the possible topology (up to 8 MAPs)

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 14 Usage of multiple channel for solving exposed terminal problem (7/7) Required number of channels for practical topology (up to 10 MAPs)

doc.: IEEE /0247r1 Submission March 2005 Atsushi FujiwaraSlide 15 Suggestions for 11s amendment 11s shall standardize: Channel Unification mechanism to ensure the connectivity Frameworks to support multiple WLAN interfaces –DFS, TPC, Measurement for mesh network –should be extension of 11k and 11h amendment for mesh network