Embed Size (px)
Citation preview
Slide 1
doc.: IEEE 802.11-06/0916r1
Submission
M-WLAN:A Layer-3 solution for Mesh Networking
Notice: This document has been prepared to assist IEEE 802.11. 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 802.11.
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <[email protected]> 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <[email protected]>.
Date: 2006-07-18
Name Company Address Phone email Yuichi Murakami
Niigata University 8050 Igarashi 2, Niigata city, Niigata, Japan
+81-90-2441-3464 [email protected]
Yasunori Owada
NiigataUniversity 8050 Igarashi 2, Niigata city, Niigata, Japan
+81-805475-3451 [email protected]
Hiroei Imai
Niigata University 8050 Igarashi 2, Niigata city, Niigata, Japan
+81-25-262-7431 [email protected]
Mineo Takai
University of California, Los Angeles
3809 Boelter Hall, Los Angeles, CA 90095-1596
+1-310-825-4885 [email protected]
Kenichi Mase
NiigataUniversity 8050 Igarashi 2, Niigata city, Niigata, Japan
+81- 25- 262- 6755 [email protected]
Authors:
Slide 2
doc.: IEEE 802.11-06/0916r1
Submission
Some Standard-Related Activities at Niigata Univ.
• No Overhead Autoconfiguration for OLSR (NOA-OLSR) draft-mase-manet-autoconf-noaolsr-01.txt, February 2006 K. Mase (Niigata Univ.), C. Adjih (INRIA)• PDAD-OLSR: Passive Duplicate Address Detection for OLSR draft-weniger-autoconf-pdad-olsr-01,
June 2006 K. Weniger (Panasonic) and K. Mase (Niigata Univ.)• A Common Framework for Autoconfiguration of Stand-alone Ad Hoc Networks draft-mase-autoconf-framework-02, June 8, 2006 K. Mase (Niigata University), C. Adjih (INRIA)• Gateway Aggregation Protocol (GAP) for Mobile Ad Hoc Networks
draft-mase-autoconf-gap-00, May 2006 K. Mase and Y. Owada (Niigata University)
• Implementation of OLSRv2 is under development.
• OLSR Interop will be held from Oct. 3-5 at Niigata Univ.
Slide 3
doc.: IEEE 802.11-06/0916r1
Submission
Ad Hoc Networks Platform Consortium
• Japanese industries, academia and government have been active in research and development toward the ubiquitous society and have cooperatively developed advanced concepts and technologies including IPv6, TRON OS, RFID, etc.
• The need of active collaboration of industries, academia and government in the area of ad hoc networks has been recognized recently.
• The Ad Hoc Networks Platform Consortium was started December 2003 in Japan, aiming at promoting research and development collaboration and standardization in the area of ad hoc networks.
• Currently, 14 enterprises, 15 universities and a government laboratory have joined the consortium.
Slide 4
doc.: IEEE 802.11-06/0916r1
Submission
A Large-Scale Ad Hoc Network Testbed
• In early 2004, the research project entitled “the next generation ad hoc network base technologies”, led by Niigata University in cooperation with ATR, Hitachi and Oki, was formed in the Consortium.
• This project has been funded by the Ministry of Internal Affairs and Communications (MIC) since July 2004.
• In this project, Niigata University has built a large-scale ad hoc network testbed in Niigata University campus area in November 2004.
Slide 5
doc.: IEEE 802.11-06/0916r1
Submission
Roof (penthouse) 22 nodes
Roof (Self standing) 15 nodes
Wall of building 3 nodes
Solar panel 10 nodes
0 100 200m
Ad Hoc Network Testbed Overview
Slide 6
doc.: IEEE 802.11-06/0916r1
Submission
Slide 7
doc.: IEEE 802.11-06/0916r1
Submission
Slide 8
doc.: IEEE 802.11-06/0916r1
Submission
Slide 9
doc.: IEEE 802.11-06/0916r1
Submission
What’s M-WLAN
• M-WLAN : Multi-hop Wireless LAN• AP-AP : MANET• AP-MS : Usual WLAN• M-WLAN can construct a mesh network
- 802.11a/b/g standard and MANET routing protocol are used- Layer-2 function is left unchanged.
AP AP
MANET
WLAN WLAN
AP: Access PointMS: Mobile Station
MS MS
Slide 10
doc.: IEEE 802.11-06/0916r1
Submission
What’s M-WLAN(2)
• Routing protocol : OLSR– Extension
• Association table– This table is used to decide the route to the MS.
• Associated Address Declaration (AAD) message– This message is used to exchange IP addresses of the MSs between t
he APs and update their Association tables.
• IP address assignment to the MS : DHCP
Slide 11
doc.: IEEE 802.11-06/0916r1
Submission
Routing Calculation
AP’s IPaddr MS’ IPaddr MS’ MACaddr
172.25.2.1 172.25.70.250 00:xx:xx:xx:xx:xx
GW&DHCP server
Internet
MS1
1.IP address assignment by DHCP
3.ＡＡＤmessage
2.Capture DHCP Ack ,extract IP and MAC address of MS and proceeds to update association table.
Association table(AP1)
MAC : 00:xx:xx:xx:xx:xx
172.25.70.250
00:xx:xx:xx:xx:xx
4.Update Association table and make the route to MS
Association table(AP2)AP’s IPaddr MS’ IPaddr MS’ MACaddr
172.25.2.1 172.25.70.250 00:xx:xx:xx:xx:xx
IP : 172.25.70.250
AP2AP1
GW: Gateway
Slide 12
doc.: IEEE 802.11-06/0916r1
Submission
Roaming
MS1
3.ＡＡＤmessage
MAC : 00:XX:XX:XX:XX:XX
172.25.70.250
00:xx:xx:xx:xx:xx
2.Search MS’ MAC address fromAssociation table and update this table.
IP : 172.25.70.250
1.Move & associate with new AP
Association table(AP2)AP’s IPaddr MS’ IPaddr MS’ MACaddr
172.25.2.1 172.25.70.250 00:xx:xx:xx:xx:xx
172.25.2.2(AP2)
AP’s IPaddr MS’IPaddr MS’ MACaddr
172.25.2.1 172.25.70.250 00:xx:xx:xx:xx:xx
Association table(AP1)
172.25.2.2(AP2)
AP1 AP2
4.Update Association table and make the route to MS
Slide 13
doc.: IEEE 802.11-06/0916r1
Submission
Inter-MSs communication & Internet access
GW&DHCP server
Internet
MAC IP
MS1 MS2
Layer 2
Layer 3
MAC IP
MAC IP
IP
From IM To IA
3.Extract IP packet from data frames and pass this packet to OLSR
1.Send data frames
4.Send IP packet according to OLSR
IM : Interface that connects
MSs to an APIA : Interface that connects APs each other
AP1 AP2
2.IM capture all data frames from the MSs even if these data frames are not destined to itself.
Slide 14
doc.: IEEE 802.11-06/0916r1
Submission
Performance Evaluation
• We measured– Throughput & RTT between MSs
– Access to the external network
– Handoff time
• We used M-WLAN test-bed for– Evaluating the capability of M-WLAN.
– Understanding its operation in the real environment.
Slide 15
doc.: IEEE 802.11-06/0916r1
Submission
Our M-WLAN Test-bed construction
3F
2F
1F
30m
9m30m: AP
Slide 16
doc.: IEEE 802.11-06/0916r1
Submission
Wireless Interface card x 2(MANET & WLAN)
Small embedded PC (AP)
AP
Power cable
Ethernet cable(Only for control)
Slide 17
doc.: IEEE 802.11-06/0916r1
Submission
Specification of an AP
Name OpenBlockS
CPU IBM PowerPC 406GPr 266MHz
Built-in storage Compact Flash™1GB
OS Embedded Linux : SSD/Linux
(WLAN Interface)
Wireless LAN card PLANEX GW-NS11H (802.11b)
(MANET Interface)
Wireless LAN card NEC WL54AG (802.11 a/b/g)
AP-AP (MANET: backbone)802.11a
AP-MS (WLAN)802.11b
Slide 18
doc.: IEEE 802.11-06/0916r1
Submission
Evaluation (Throughput & RTT between MSs)
AP4 AP3
AP1
AP2
MS1
MS2
: DHCP server & GW (Laptop PC : One of the MANET nodes)
1 hop in MANET
MANET (backbone network)
• Performance metric : Throughput & RTT between MSs• Measurement environment
– 1 hop in MANET : MS1 -> AP1 -> AP2 ----------------------> MS2– 2 hops : MS1 -> AP1 -> AP2 -> AP3 ------------> MS2– 3 hops : MS1 -> AP1 -> AP2 -> AP3 -> AP4 -> MS2
Slide 19
doc.: IEEE 802.11-06/0916r1
Submission
Experimental parameter
Tool Ping
Hop count 1~3 (In MANET)
Interval 0.1sec
Number of packets 1000
Table.1 Experimental parameters for measuring throughput
Table.2 Experimental parameters for measuring RTT
Tool Netperf2.4.1
protocol TCP/UDP
Packet Size 1500byte
Hop count 1~3 (In MANET)
Number of measurement 10
Slide 20
doc.: IEEE 802.11-06/0916r1
Submission
Results (Throughput & RTT between MSs)
0
1
2
3
4
5
6
1 2 3
Hop count (backbone)
Thro
ughp
ut (M
bps)
UDPTCP
0
1
2
3
4
5
6
7
8
1 2 3
Hop count (backbone)
RTT
(ms)
RTT
Fig1. Throughput against hop count along the backbone
Fig2. RTT against hop count along the backbone
• There is no line-of-sight between AP2 and AP3.
• The effect of fading in the experimental environment causes the reduction of the throughput between AP2 and AP3.
• But this test-bed achieved more 2Mbps throughput in the case that the communication hops three times in MANET.
Slide 21
doc.: IEEE 802.11-06/0916r1
Submission
Evaluation (Access to external network)
AP4 AP3
AP1
AP2
MS1
: DHCP server & GW (Laptop PC : One of the MANET node) 1 hop
in MANET
MANET (backbone network)
• Performance metric : Throughput• An FTP client on MS1 was used to connect to an FTP server in an
external network as part of the experimental setup• Measurement environment
– 1 hop in MANET : MS1 -> AP1 -> GW --------------------->> FTP– 2 hops : MS1 -> AP2 -> AP1 -> GW ----------->> FTP– 3 hops : MS1 -> AP3 -> AP2 -> AP1 -> GW ->> FTP
: FTP server
Slide 22
doc.: IEEE 802.11-06/0916r1
Submission
Result (Access to external network)
Fig3. Throughput between MS and FTP server against hop count along the backbone
0
0.5
1
1.5
22.5
3
3.5
4
4.5
1 2 3
Hop count (backbone)
Thro
ughp
ut (M
bps)
• I confirmed that this test-bed achieved smoothly internet access in the case that the communication hops three times in MANET.
Slide 23
doc.: IEEE 802.11-06/0916r1
Submission
Evaluation (Handoff time)
• Performance metric : Handoff time• MS1 sends ICMP packet to MS2 by Ping, while moving.• I measured the time of communication blackout when MS1
moves out of communication range of AP1 and must reassociate itself with AP2.
AP4 AP3
AP1
AP2MS1
MS2
move
Ping
Slide 24
doc.: IEEE 802.11-06/0916r1
Submission
Timeline (Handoff)
L-2 Handoff
L-3 Handoff
AAD Broadcast
Reassociation response
Reassociation request
Authentication (From AP)
Authentication (From MS)
Deauthentication
55ms
85ms
1ms2ms1ms2ms
13ms Report Association to L-3
Routing Update
Ping stop
Ping restart
Ｔｏｔａｌ140ms
Slide 25
doc.: IEEE 802.11-06/0916r1
Submission
Conclusions
– We designed and implemented M-WLAN.
– We constructed a Mesh Network -802.11 a/b/g standard was used. -L-2 function was left unchanged.
– We evaluated the performance of M-WLAN in our test-bed.– We presented
- the capability of M-WLAN. - a possible solution to upgrade the performance.
