[Ns-developers] Mac layer 802.11n

Mathieu Lacage mathieu.lacage at sophia.inria.fr
Sat Jan 10 23:18:15 PST 2009


On Sat, 2009-01-10 at 20:31 +0100, Mirko Banchi wrote:

> > 1) QstaWifiMac+QapWifiMac+EdcaTxop
> > 2) modified MacLow according to previous discussion
> > 3) extended EdcaTxop using MacLow to implement aggregation
> 
> Ok...About EdcaTxop, what do you think about a unique class EdcaTxopN?
> Another way could be to create a common abstract class which EdcaTxop
> and EdcaTxopN inherits from.In the first implementation would be not
> possible to use only 802.11e standard features without the 802.11n
> features. There would be only possible (in an easy manner) to switch off
> aggregation.Maybe the second implementation is better...with a common
> interface we could use, in QstaWifiMac and in QapWifiMac, EdcaTxop or
> EdcaTxopN.This also would help us to have in the same wlan many types of
>  terminals (for example 802.11e and 802.11n terminals).

uh, oh, I think I understand what you are saying now: you are saying
that the EdcaTxop code would need to be different between 802.11e and
802.11n. Ok. Yes, this makes sense and I agree on the following:
  - DcaTxop (non-802.11e/n)
  - EdcaTxop: abstract base interface
  - EdcaTxopE: implementation of EdcaTxop for 802.11e
  - EdcaTxopN: implementation of EdcaTxop for 802.11n

The easiest way to implement this is to first implement separately
EdcaTxopE and EdcaTxopN and figure out what their common code/API is and
then move that common code/API in the base class (it is easier than
implementing the base class first and the subclasses later).

regards,
Mathieu



More information about the Ns-developers mailing list