• 1
  • 2
  • 3
  • 4

Activities

  • NITOS Outdoor deployment consists of powerful nodes that feature multiple wireless interfaces and allow for experimentation with heterogeneous (Wi-Fi, WiMAX,

    Read More
  • The setup NITOS testbed is currently using is a fixed setup (employing no mobility between BSs) that does not require

    Read More
  • Towards the development of a remote accessible LTE testbed, where experimenters from all the word will be able to run

    Read More
  • NITOS facility provides remote access to OpenFlow switches (2 x Pronto 3290 , 2 x HP 3800 ), enabling the user to create

    Read More
  • NITlab developed a software defined radio (SDR) testbed that consists of 18 Universal Software Radio Peripheral (USRP) devices attached to

    Read More
  • NITOS is an Intelligent Transport System (ITS) compatible facility thanks to the implementation of the key components of the ITS

    Read More
  • NITOS cloud infrastructure is based on HP GEN8 blade servers and one HP DL380p GEN8 server. Cloud Infrastructure UTH Each blade server has

    Read More

NITOS

The Future Internet Facility

  • Outdoor Testbed

    Experiments under real world environment Read More
  • Indoor Testbed

    Experiments in RF isolated environment Read More
  • Office testbed

    Experiments in an office environment Read More
  • 1
  • 2
  • 3

NITOS - Planetlab Federation

1. The Scenario

The experiment highlights the importance of association mechanisms in the general context of a network involving wired and wireless (Wi-Fi) components. The scenario is that of figure 1. A wireless station operating in an environment with two available access-points is sending traffic to a remote destination through the Internet. In current 802.11 WLANs, the station selects the AP to associate with only taking into account the RSSI values from the APs. This is clearly suboptimal even in an exclusively wireless context and much research work has focused on proposing new association metrics. The goal of this experiment is to shed light on an important parameter, often neglected in this context, the fact that the perceived QoS of a station depends on end-to-end performance metrics, rather than AP-specific metrics. In particular, one specific metric is taken into account, the end-to-end delay. However it is clear that extensions to more complex end-to-end metrics are relatively straightforward.

federation1

Figure 1: The scenario of our user association experiment

 

2. Resources involved

A synergy between two different testbeds is established for the purposes of the experiment, namely between the NITOS wireless testbed, located at the premises of the  University of Thessaly, and the large-scale distributed Planetlab Europe wired testbed. The University of Thessaly has two Planetlab nodes deployed at their facilities. These nodes are connected to two wireless nodes of NITOS, configured to operate as access-points. A third wireless NITOS node, in range with the former two, is used as the station sending the traffic. This traffic is destined to a remote Planetlab node, located at the INRIA facilities in Paris, France. The synergy between the two testbeds is depicted in Figure 2.

 

federation2

Figure 2: The synergy of NITOS and PLE during the experiment

 

3. Experiment Description

The three wireless nodes at NITOS are running modified versions of the MadWifi open-source driver. At the APs the drivers read a delay value from a specific proc-file. This value is obtained for each node through periodic pings to the destination node at INRIA taking place at the application level at regular time intervals. Each AP advertises this value through beacons, so that wireless stations in their neighborhood can take this parameter into account for their association decision. At the station side, the driver has been modified, so that the station associates to the AP with the lowest delay value, rather than to the AP with the highest RSSI. Again, it is clear that alternative policies using combined metrics of RSSI, delay and other parameters are straightforward to implement.

federation3

Figure 3: The actual scenario - Delay emulation through Dummynet

 

In order to control the delay of the different routes to the destination, a network emulator is being used on the destination side, Dummynet in particular. We configure Dummynet to apply different delays to the streams arriving from the two APs at NITOS and change this configuration periodically on the fly, as the experiment is running. The APs running the periodic ping applications sense these changes and update the relative proc-files accordingly.

Download the experiment description in OMF:

experiment.rb

 

4. Related paper

You can also download the relevant paper accepted in Tridentom 2012:

Keranidis_Federation_TridentCom_2012_paper.pdf

 

5. Demonstration through OMF

federation video

Figure 4: Screenshot from our Demonstration Video

The whole experiment is orchestrated through the OMF testbed control and management framework. NITOS has adopted OMF as its software framework and Planetlab nodes can incorporate OMF software upon request.

What Our Experimenters Say

  • NITOS is a very reliable and well managed platform. The offered infrastructure and features are great. The management team is very supportive.

    Mustafa Al-Bado
    Postdoctoral researcher
    Insight centre, University College Cork (UCC)
  • 1
  • 2
 
uth
image
image
image
 
 

Login Form