From: Pasquale Imputato <p.imputato@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: mab-wifi@lists.bufferbloat.net
Subject: Re: [mab-wifi] Possible contribution
Date: Wed, 5 Apr 2017 15:47:19 +0200 [thread overview]
Message-ID: <CAJdyoV1=P2K=kJ7esDqMRyAu7LdshPoaxkyXna-1yg80rNAqOA@mail.gmail.com> (raw)
In-Reply-To: <87h92ytiik.fsf@alrua-karlstad>
[-- Attachment #1: Type: text/plain, Size: 2398 bytes --]
Hi Toke,
sorry for the long delay.
In ns-3 the 802.11 standard is implemented rather accurately.
The simulator models the standards 802.11a/b/g/n/ac, an initial draft of ax
and the e emendament for the QoS support.
The models support MIMO in 802.11n/ac/ax.
The example 802-11n-mimo in examples/wireless provide and overview of the
MCS and MIMO capabilities by exploring for each HT MCS from 1 to 4 MIMO
streams.
Multiple rate control algorithms are implemented in the simulator. Some of
them are found on real devices, while much others are only available in
literature. There is implemented the minstreal HT algorithm, that could be
useful for benchmark.
The rate control algorithms are modelled by the WiFiRemoteStationManager
class of the wifi module. The class hold a list of per-station-state info
modelled after the struct sta_info in Linux kernel.
Create a new rate control algorithm can be done by introducing a new child
class of the WiFiRemoteStationManager class in the wifi module of the
simulator.
The simulator capabilities seem to fit our needs in term of MCS and MIMO.
Since we are in an exploration phase, how we can contribute to the
exploration?
Thanks,
Pasquale Imputato
2017-03-12 20:14 GMT+01:00 Toke Høiland-Jørgensen <toke@toke.dk>:
> Pasquale Imputato <p.imputato@gmail.com> writes:
>
> > Hi everyone,
> > I and Stefano Avallone are working to improve wifi simulations with
> traffic-control in ns-3.
> > We would like to participate in the experiment of collaboratively
> writing a research paper on a new wifi rate control algorithm.
> > We are willing to contribute to the design of the new algorithm and by
> carrying out ns-3 simulations to evaluate the new algorithm.
> >
> > Please let us know your opinion and how we can start contributing to
> > this joint effort.
>
> Hi Pasquale
>
> That sounds awesome! We are still at a fairly early stage in terms of
> algorithm development (still exploring options), but having an ns3
> implementation will definitely be useful once we get something a bit
> more concrete :)
>
> I'm not terribly familiar with the capabilities of ns3 in the wifi
> space. Could you provide an overview of what parts of 802.11 are
> implemented in ns3 and how rate control hooks into that? And maybe how
> it compares to Linux, if you are familiar with that?
>
> -Toke
>
[-- Attachment #2: Type: text/html, Size: 3167 bytes --]
next prev parent reply other threads:[~2017-04-05 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 9:36 Pasquale Imputato
2017-03-12 19:14 ` Toke Høiland-Jørgensen
2017-04-05 13:47 ` Pasquale Imputato [this message]
2017-04-10 13:29 ` Toke Høiland-Jørgensen
2017-04-11 17:37 ` Matias Richart
2017-04-12 8:33 ` Toke Høiland-Jørgensen
[not found] ` <CAGp19xeK_7zhCqeMmNzLqoF4C94buxY2etOxjT9o4G2d2VVOVA@mail.gmail.com>
2017-04-18 10:03 ` Pasquale Imputato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJdyoV1=P2K=kJ7esDqMRyAu7LdshPoaxkyXna-1yg80rNAqOA@mail.gmail.com' \
--to=p.imputato@gmail.com \
--cc=mab-wifi@lists.bufferbloat.net \
--cc=toke@toke.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox