You are here: Technologies / Testbeds

Available testbeds

A number of different and diverse testbeds are available in the OpenLab project. Each of them has been build with a certain type of applications in mind and usually uses its own contol framework. It is an objective of OpenLab to enable transparent access to combinations of resources from different testbeds for advance and large scale future Internet experiments

NITOS (Network Implementation Testbed using Open Source code)

NITOS [nitlab.inf.uth.gr/NITlab/index.php/testbed] is an OMF-based wireless testbed in a campus building at UTH in Volos, Greece. It consists of 45 nodes equipped with a mixture of Wi-Fi and GNU-radios, as well as cameras and temperature and humidity sensors. Two programmable robots provide mobility. This publicly available testbed supports experiments across all networking layers. In addition to OMF, the testbed employs locally developed tools: the NITOS scheduler, a resource reservation application, and TLQAP, a topology and connectivity monitoring tool. In OpenLab, under the guidance of COSMOTE, a major ISP provider in Greece, and with the help of Alcatel-GR, NITOS will be extended to meso-scale (WiMAX/3G/LTE), with a base-station and mobile end-user handsets.

w-iLab.t

The w-iLab.t testbed [www.ibbt.be/en/ilabs/ilab-t/wireless-lab] is a wireless mesh and sensor network infrastructure deployed across three floors of the IBBT office building in Ghent, Belgium. It contains 200 locations, each equipped to receive multiple wireless sensor nodes and two IEEE 802.11a/b/g WLAN interfaces. Wi-Fi and sensor networks operate simultaneously, allowing complex and realistic experiments with heterogeneous nodes and multiple wireless technologies. In addition, shielded boxes accommodate nodes that can be connected over coax cables to RF splitters, RF combiners and computer controlled variable attenuators, thus allowing fully reproducible wireless experiments with emulated dynamically changing propagation scenarios. With an in-house designed hardware control device, unique features of the testbed include the triggering of repeatable digital or analogue I/O events at the sensor nodes, real-time monitoring of the power consumption, and battery capacity emulation. Plan

Current users of the w-iLab.t testbed

Who is using w-iLabt?
A large part of the users are somehow linked to IBBT: IBBT researchers, or research partners from industry that collaborate with us in a research project.  Researchers also use it for their PhD. Other accounts are from people working at research institutes or universities worldwide.  This group has been increasing significantly since we made more promotion with w-iLab.t, among others in the margin of CREW and Openlab. A final but very small set of accounts was created for people from industry that (plan to) use w-iLab.t for their future research/development outside of a research project. Finally, w-ilabt is also used by students during lab sessions.

What kind of experiments:
1/ w-iLab.t was used to debug and test a beacon scheduling algorithm (Distributed Assignment of Beacon Slots). It was important to test this on a multi-hop network (at least three hops).

2/ w-iLab.t was used to test an energy harvesting electronic shelf label system. The nodes were powered via the Environment Emulator and ""power source emulation"" scenarios. The application success rate was tested in a star topology with 41 nodes.

3/ w-iLab.t was used to measure the connectivity, signal strength and packet error rate between 40+1 nodes. This information was used in the Castalia simulator (in order to test with 12.000 nodes).

4/ The w-iLab.t will be used to test scalability of the virtualization layer implemented on sensor devices.

5/ The w-iLab.t was used to test different sensor positioning algorithms. It allowed to test the different solutions in a real life environment. When we deployed a sensor network in external locations (De Vooruit, WZC De vijvers), it was easier because we already knew the behavior of the positioning algorithms in the w-iLab.t testbed.
Because of the large number of sensor nodes in the w-iLab.t sensor network, it was possible to test the positioning in a large environment over multiple floors. "

6/ "The testbed was used for testing the QoS framework in IDRA. The testbed was also used for testing the DYMO routing protocol (in IDRA).

7/ The w-ilab.t was used to set up a proof-of-concept demonstration that shows co-located networks benefit from automated negotiation and optimization solutions. The lab was used to set-up the demonstrator and to automatically evaluate the performance gains of the developed solutions.

8/ In the context of CONSERN, the w-iLab.t is most importantly used to measure the power consumption of wireless nodes when running different mechanisms for power saving and for enabling self-growing of the network. Power consumption is measured and compared to the power consumption when these mechanisms are not enabled, to conclude the resulting power saving. In addition, w-iLab.t is used as a common platform for the creation of an integrated proof-of-concept system of the project. The developments of multiple partners are ported and integrated to w-iLab.t, and common scenarios are demonstrated.

9/The w-iLab.t deployment located at Zwijnaarde was used for experiments concerning the 802.11n standard. Throughput and delay tests were performed. Furthermore a modified WLAN driver was tested here.

Are your project facilities deployed by project partners, external organizations, other FP7 projects or FIRE STREPS?
w.iLabt.t is deployed by IBBT. w.iLab.t  is also used in CREW, OFELIA, SPITFIRE, EVARILOS (call 8 project tstarting on 1 Nov. 2012), Fed4FIRE (call 8 project starting on 1 Oct. 2012), CONSERN (objective 3.5 project)

DOTSEL

The DOTSEL testbed at ETH Zürich is focused on delay-tolerant opportunistic protocols and applications. It is composed of 15 Wi-Fi equipped Android Nexus One devices that are carried by staff members, and five Wi-Fi a/b/g ad-hoc gateways. With OpenLab, DOTSEL will be enlarged to 25 nodes and add 3G capability.

PLE (PlanetLab Europe)

PLE [www.planet-lab.eu] is the European arm of the global PlanetLab system, the world’s largest research networking testbed, which gives users access to Internet-connected Linux virtual machines on over 1000 networked servers located in the United States, Europe, Asia, and elsewhere. Nearly 1000 scientific articles mention the PlanetLab system each year(1),  including papers in such prestigious networking and distributed systems conferences as ACM SIGCOMM, ACM CoNEXT, IEEE INFOCOM, ACM HotNets, USENIX/ACM NSDI, ACM SIGMETRICS, and ACM SIGCOMM IMC. Researchers use PLE for experiments on overlays, distributed systems, peer-to-peer systems, content distribution networks, network security, and network measurements, among many other topics. (2)
Established in 2006 and developed by the OneLab initiative, PLE is today overseen by four OpenLab partners: UPMC, INRIA, HUJI, and UNIPI. UPMC handles testbed operations and INRIA co-leads, along with Princeton University, development of MyPLC, the free, open-source software that powers PlanetLab. The PlanetLab Europe Consortium has 150 signed member institutions: mostly universities and industrial research laboratories, each of which hosts two servers that it makes available to the global system. These institutions are home to 937 users. On a typical recent day, 244 were connected to on-going experiments.
OpenLab extends both the PlanetLab software and the PlanetLab Europe Consortium.

(1) Estimate based on Google Scholar search for papers containing “PlanetLab” over the past five years.
(2) For a few examples of PLE use cases, see www.onelab.eu/index.php/services/testbed-access/use-cases.html.

HEN (Heterogeneous Experimental Network)

HEN [mediatools.cs.ucl.ac.uk/nets/hen], built between 2005 and 2010 by UCL, provides 100 server-class machines with between 6 and 14 NICs each, interconnected by a Force10 E1200 switch with 550 Gigabit ports and 24 10-Gigabit ports. This infrastructure allows emulation of rich topologies in a controlled fashion over switched VLANs that connect multiple virtual machines running on each host. The precise control of topology and choice of end-host operating system possible on HEN are particularly valuable facilities to networking and distributed systems researchers.
Many dozens of researchers actively use HEN: at Stanford University, the University of Lancaster, NYU, the Nokia Research Centre, and NEC Labs Europe, to name a few. UK- and EU-funded projects, including the EPSRC-funded Virtual Routers project, EPSRC-funded ESLEA project, EU FP7-funded Trilogy project, and EU FP7-funded CHANGE project, have all generated the bulk of their experimental results on HEN. Results have been published in prestigious networking and distributed system venues including ACM SIGCOMM, ACM HotNets, USENIX/ACM NSDI, USENIX Security, ACM CCR, ACM CoNEXT, Presto, FDNA, PMECT, ICDCSW, and LSAD.
OpenLab extends HEN to support multi-homed operation and interconnection with other FIRE-supported testbeds, yielding a powerful platform for experimental research on multi-path transport and application protocols—a hot area of interest to today’s networking community.

The WIT IMS testbed

The TSSG/WIT NGN IMS testbed [ngntestcentre.com] is an Irish nationally-funded initiative serving telecom firms seeking to develop or test NGN services. It provides them with advanced multimedia services, such as conference calling and handling of presence information. The testbed is a carrier grade NGN platform based on the Ericsson IMS Communications System (ICS). The SIP based horizontal network architecture includes an Ericsson IMS core and the components for managing sessions, addressing, subscriptions and IMS inter-working components with the relevant gateways for connectivity to other networks. The testbed has recently been upgraded with pico/femto cells to allow secure remote access to the test facility. The network also includes support systems for handling provisioning, charging, device configuration and operation and maintenance.
Clients include IP centrex companies, a location based service provider, and developers of pico/femto cell technology. International customers have conducted testing in the area of IMS security and testbed interconnection using the GSMA Pathfinder service operated by Neustar.
In OpenLab, the WIT testbed will be enhanced by the development and integration of a P2P/NGN QoS reservation mechanism that will allow OpenLab experimenters to test application level P2P traffic routing algorithms.

OSIMS - An Open Source IMS experimentation platform

The University of Patras IMS testbed supports PSTN testing scenarios: calls between a PSTN network and any PSTN number (including international and mobile numbers); and calls between IP phones (either soft phone or hard phone) and any PSTN number (including international and mobile numbers). The testbed has been used in numerous interoperability experiments with the carrier grade network of Telecom Austria, and the NGN testbeds of Siemens AG in Munich and Telefónica TID in Madrid. It is currently hosts experiments from the FP7 VITAL++ project. Integration of the testbed into the Teagle framework was carried out under the PII project. In OpenLab, the testbed will be enhanced to incubate P2P/NGN QoS reservation algorithms and establish experimentation paths taking advantage of the OpenFlow protocol. Read more about OSIMS ...

ETOMIC (European Traffic Observatory Measurement InfrastruCture)

ETOMIC [etomic.org] is a high precision (10s of nanoseconds) network measurement testbed featuring dozens of Internet-connected nodes globally synchronized with GPS clocks. More than 100 users from 34 institutions run over 100 experiments per month. Created in 2004-05 within the FP6 EVERGROW Integrated Project, it was awarded the Best Testbed Award at TridentCom 2005. In OneLab2, ETOMIC opened interfaces to MySlice (described above) to transparently provide measurements to PlanetLab users. OpenLab will continue to promote ETOMIC’s experimental plane interoperability.

Current ETOMIC testbed users

Are your project facilities deployed by project partners, external organizations, other FP7 projects or FIRE STREPS?
Project partners+ external organizations.

Which kinds of experiments/measurements are performed? By whom? Would it be possible to get a contact email in case of external organizations?
Precise one-way delay measurements, topology discovery, available bandwidth calculation.