GSOC2009Minstrel - Revision history

Duy: /* NS-3 Developments */

2009-10-29T17:57:22Z

NS-3 Developments

← Older revision		Revision as of 17:57, 29 October 2009
Line 97:		Line 97:
	</pre>		</pre>

	~~==== NS-3 Developments ====~~

	~~please see our developments at http://code.nsnam.org/duy/ns-3-dev-minstrel/~~

	=== Extra Minstrel Information ===		=== Extra Minstrel Information ===

Duy: /* Introduction */

2009-10-29T17:56:57Z

Introduction

← Older revision		Revision as of 17:56, 29 October 2009
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

			This project has already been ported to ns-3.

	[http://linuxwireless.org/en/developers/Documentation/mac80211/RateControl/minstrel Minstrel] is a well-known rate control algorithm in [http://madwifi-project.org/ madwifi] and linux kernel, based on the Sample rate control algorithm. Our goal for this project is to port this control rate algorithm to the NS-3. We hope our findings will contribute some further improvements to the NS-3 simulator.		[http://linuxwireless.org/en/developers/Documentation/mac80211/RateControl/minstrel Minstrel] is a well-known rate control algorithm in [http://madwifi-project.org/ madwifi] and linux kernel, based on the Sample rate control algorithm. Our goal for this project is to port this control rate algorithm to the NS-3. We hope our findings will contribute some further improvements to the NS-3 simulator.

	~~Our current development is at http://code.nsnam.org/duy/ns-3-dev-minstrel/~~

	== Approach ==		== Approach ==

Duy: /* Schedule and Progress */

2009-08-20T19:23:34Z

Schedule and Progress

← Older revision		Revision as of 19:23, 20 August 2009
Line 182:		Line 182:

	Week 10: Release code for review and merge with ns-3-dev[done]		Week 10: Release code for review and merge with ns-3-dev[done]


	~~Current progress and priorities:~~
	~~#Since the interference and error model requires a new wifi phy, our priority right now is to only create a set of test scripts and validating minstrel implementation. Then prepare for code review.~~
	~~#After release code to ns-3-dev for review, work on the new wifi phy for a new error and interference model.~~
	~~#ns-3 simulation and CMU emulation integration is taking longer than expected, so we don't expect to include this in our schedule.~~

	==== NS3 Questions and Comments ====		==== NS3 Questions and Comments ====

Duy: /* Validation Plan */

2009-08-20T19:22:53Z

Validation Plan

← Older revision		Revision as of 19:22, 20 August 2009
Line 148:		Line 148:

	==== Validation Plan ====		==== Validation Plan ====
	Set up scenarios~~(in simulations and testbeds)~~		Set up scenarios

Duy: /* Validation Plan */

2009-08-20T19:15:09Z

Validation Plan

← Older revision		Revision as of 19:15, 20 August 2009
Line 150:		Line 150:
	Set up scenarios(in simulations and testbeds)		Set up scenarios(in simulations and testbeds)

	~~#Two nodes in concurrent transmission move away from one another until they are out of range. Then, they move back again.~~
	~~#:rmz: by concurrent transmissions, you mean that one is transmitting packets to the other one, right?~~
	~~#:duy:yes~~
	~~#Two nodes in concurrent transmission, block the line of sight to cause the degrade in signal. Introduce moving obstacles between nodes~~
	~~#Two nodes in concurrent transmission, suddenly bring the receiver down and up again. Can be accomplished by bringing the network interface down and up.~~
	~~#:rmz: what is the point of this scenario? To find out how the algorithm behave in case of failures?~~
	#:duy: this scenario is somewhat similar to scenario (1), what I am trying to do is to test the algorithm behavior when none of the rates works, and how the algorithm behaves when the links become good all of a sudden.
	~~#Two nodes in concurrent transmission, bring up two other pairs of nodes into transmission, make sure all nodes are within one another's range for maximum interference experience.~~
	~~#Repeat step but suffle the other other two pairs of nodes around in order to cause maximum inteference and degradadtion in throughput~~


	Other types of interference can be introduced by conducting the experiements in an environment which has many nearby Access Points(APs) These experiments will be carried out in the 2.4Ghz frequency of 802.11g and 5Ghz frequency of 802.11a. For each events 1-5 from above, use randomness in time in order to introduce these events into the nodes in concurrent transmission. Study how protocol behaves in both simulation and testbeds. The goal is to mirror simulation of ns-3 with the kernel implementation of minstrel. We may also study the minstrel implementation in madwifi to compare its behavior with linux kernel and ns-3 simulation.

Duy: /* Validation Plan */

2009-08-17T22:24:38Z

Validation Plan

← Older revision		Revision as of 22:24, 17 August 2009
Line 179:		Line 179:
	Scenario 5:		Scenario 5:
	Two nodes moving in and out of transmission range intermittently. Network interfaces are bringing down every 10 seconds and back up within 1 second. The number of packets received vs Time.		Two nodes moving in and out of transmission range intermittently. Network interfaces are bringing down every 10 seconds and back up within 1 second. The number of packets received vs Time.
	[[Image:~~minstrel5~~.jpg\|750px\|center\|Image on center]]		[[Image:minstrel5two.jpg\|750px\|center\|Image on center]]

	==== Schedule and Progress ====		==== Schedule and Progress ====

Duy: /* Validation Plan */

2009-08-16T07:17:44Z

Validation Plan

← Older revision		Revision as of 07:17, 16 August 2009
Line 178:		Line 178:
	[[Image:minstrel4.jpg\|750px\|center\|Image on center]]		[[Image:minstrel4.jpg\|750px\|center\|Image on center]]
	Scenario 5:		Scenario 5:
	Two nodes moving in and out of transmission range intermittently. Network interfaces are ~~bring~~ down every 10 seconds and back up within 1 second. ~~Throughput is shown as the~~ number of packets received vs Time.		Two nodes moving in and out of transmission range intermittently. Network interfaces are bringing down every 10 seconds and back up within 1 second. The number of packets received vs Time.
	[[Image:minstrel5.jpg\|750px\|center\|Image on center]]		[[Image:minstrel5.jpg\|750px\|center\|Image on center]]

Duy: /* Validation Plan */

2009-08-15T23:44:58Z

Validation Plan

← Older revision		Revision as of 23:44, 15 August 2009
Line 178:		Line 178:
	[[Image:minstrel4.jpg\|750px\|center\|Image on center]]		[[Image:minstrel4.jpg\|750px\|center\|Image on center]]
	Scenario 5:		Scenario 5:
	Two nodes moving in and out of transmission range intermittently. Network interfaces are bring down every 5 seconds and back up within 1 second. Throughput is shown as the number of packets received vs Time.		Two nodes moving in and out of transmission range intermittently. Network interfaces are bring down every 10 seconds and back up within 1 second. Throughput is shown as the number of packets received vs Time.
	[[Image:minstrel5.jpg\|750px\|center\|Image on center]]		[[Image:minstrel5.jpg\|750px\|center\|Image on center]]

Duy: /* Schedule and Progress */

2009-08-15T21:49:26Z

Schedule and Progress

← Older revision		Revision as of 21:49, 15 August 2009
Line 192:		Line 192:
	Week 6-9: Start testing and validation phase.[done]		Week 6-9: Start testing and validation phase.[done]

	Week 10: Release code for review[done]		Week 10: Release code for review and merge with ns-3-dev[done]

Duy: /* Schedule and Progress */

2009-08-15T21:47:42Z

Schedule and Progress

← Older revision		Revision as of 21:47, 15 August 2009
Line 190:		Line 190:
	Week 5: Implement retry chain. Finishing up major coding.[done]		Week 5: Implement retry chain. Finishing up major coding.[done]

	Week 6-9: Start testing and validation phase.[~~current~~]		Week 6-9: Start testing and validation phase.[done]

	Week 10: Release code for review		Week 10: Release code for review[done]