GSoC2013WAVE MAC: Difference between revisions

From Nsnam
Jump to navigation Jump to search
(Created page with "= Implementation of WAVE 1609.4/802.11p = * Student: [mailto:linlinjavaer@gmail.com Junling Bu] * Mentor: [mailto:guillaume.remy@ieee.org Guillaume Remy], [mailto:tomh@tomh.or...")
 
m (Add redirect)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
= Implementation of WAVE 1609.4/802.11p =
#REDIRECT [[GSOC2013WAVE MAC]]
* Student: [mailto:linlinjavaer@gmail.com Junling Bu]
* Mentor: [mailto:guillaume.remy@ieee.org Guillaume Remy], [mailto:tomh@tomh.org Tom Henderson],  [mailto:nikkipui@gmail.com Daniel Lertpratchya]
* Abstract: Since WAVE communication standards have been published, there exist many relevant implementations including prototypes, products, and simulations. However the implementation varies significantly, some of them even based on old draft standards.Besides that, ns-3 has no complete WAVE module yet. So I plan to implement WAVE 1609.4/802.11p in mac layer for ns-3, with complete testsuits, examples, helpers and documents.
* Code:
* Midterm report:
* About me: I am a second year Master student from China.I am researching on vehicular network communication in my lab.
 
= Approach =
 
== 802.11p ==
To implement IEEE Std 802.11p[1] mac in ns-3, I plan to define OCB mac mode(Outside the context of a BSS)named OcbWifiMac, which is like AP, station, ad-hoc mode. According to the discussion among ns-3 developers [2-3], the OcbWifiMac subclass will inherit from RegularWifiMac class, which is very like AdhocWifiMac The OcbWifiMac will overwrite some unsuitable functions to only log warn message, overwrite some functions to operate in OCB mode, and also provider some specific functions defined only in 802.11p.Moreover, OcbWifiMac will also set some arguments like default EDCA value in WAVE channels.
 
== 1609.4 ==
Since IEEE Std 1609.4[4] has already been implemented in some other simulations[5-6], I plan to use some ideas from these papers as well as the discussion among ns-3 developers[2-3] as the guideline for implementing. I will define a subclass inheriting from NetDevice named WaveNetDevice,composed of (a) OcbWifiMac mac defined in 802.11p, (b) WaveNetDevice mac extension dealing with functions of 1609.4 management and data plane,(c) subcomponents in 1609.4 including ChannelCoordinator, ChannelManager, SchChannelScheduler and VSARepeater.
== Development methodology ==
== Testing approach ==
== Deliverables ==
According to ns-3 architecture, deliverables are in a new module named WAVE, include:Model, Doc, Helper, Binding, Test, and Examples.
* Model mainly contains : a) implementations of 802.11p, including ocb-wifi-mac.h/.cc; b) implementations of 1609.4, including wave-net-device.h/.cc, vsa-repeater.h/.cc, sch-channel-scheduler.h/.cc, channel-manager.h/.cc, channel-coordinator.h/.cc,vendor-specific-frame.h/.cc,and single-phy-sch-channel-scheduler.h/.cc.
* Doc contains design ideas, implementation details, and manual. Helper contains nice helpers to simplify operation, including wave-helper.h/.cc.
* Test contains some test suits, including ocb-wifi-mac-test-suit.cc, wave-net-device-test-suit.cc.
* Examples contain useful examples, including simple-wave-example.c, and simple-802.11p-example.c.
 
= Plan =
 
Based on the GSoC 2013 timeline, there are totally 12 weeks. The following is my plan (Implementation not only means source codes, but also contains relevant test suits, examples and documents):
* Before June 17: learn Python, ns-3 coding style, read relevant ns-3 codes,talk with mentors about implementation details
* Week 1/2 June 17 – June 30: implement OcbWifiMac
* Week 3/4 June 1 – July 14: implement WaveNetDevice
* Week 5/6 July 15 – July 28: implement SchChannelScheduler 
<br/>
* July 29 - August 2: mid-term report. I will submit source files including ocb-wifi-mac.h/.cc, wave-net-device.h/.cc, ocb-wifi-mac-test-suit.cc, simple-802.11p-example.cc. And I will also submit a document about partial technical details and usage for VANET researchers and a relatively simple introduction of WAVE for other users
<br />
* Week 7 August 3 – August 11: implement ChannelCoordinator
* Week 8 August 12 – August 18: implement ChannelManager
* Week 9/10 August 19 – September1: implement VSARepeater
* Week 11 September 2 – September 8: complete documents, useful helpers
* Week 12 September 9 – September 15: complete some WAVE examples, system test.
<br />
*September 16 – September 23: scrub code, and improve documentation.
 
= Weekly Progress =
 
= Acknowledgement =
Thanks for all comments from Guillaume Rémy, Lalith Suresh, Tommaso Pecorella, and Tom Henderson.
 
=  References =
 
* [1]IEEE Std 802.11p, IEEE Standard for Information Technology-Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 6: Wireless Access in Vehicular Environments, 2010.
* [2] ns-3.Bug 945 - Revise how we provide support for vehicular communications. [Online]. Available: https://www.nsnam.org/bugzilla/show_bug.cgi?id=978.
* [3] ns-3.Bug 978 - Consolidate Wi-Fi MAC high functionality. [Online].Available: http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16.
* [4] IEEE Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-Channel Operation. IEEE Std 1609.4-2010, 2010.
* [5]Chen Qi, Daniel Jiang, and Luca Delgrossi. "IEEE 1609.4 DSRC multi-channel operations and its implications on vehicle safety communications."Vehicular Networking Conference (VNC), 2009 IEEE. IEEE, 2009.
* [6] Ghandour, Ali J., et al. "Modeling and simulation of WAVE1609.4-based multi-channel vehicular ad hoc networks." Proceedings of the 5th International ICST Conference on Simulation Tools and Techniques. ICST (Institute for Computer Sciences, Social-Informatics and Telecommunications Engineering), 2012.

Latest revision as of 20:58, 28 July 2013

Redirect to:

Retrieved from "https://www.nsnam.org/mediawiki/index.php?title=GSoC2013WAVE_MAC&oldid=7768"