Testbed Federation Survey
To establish the feature set among the existing CONET testbeds as potential candidates for the future CONET Testbed Federation (CTF), we have performed an extensive online survey. The questions cover a range of hardware, software and policy issues that formed the basis for the CTF platform requirements analysis and were used to compile a single point of reference for the existing testbed resources at disposal of CONET partners.
CONET Testbeds
Summary of Features
|
Operational Status
|
|
|
| Planning phase |
|
3 |
27% |
| Set-up phase |
|
2 |
18% |
| Stable and running |
|
6 |
55% |
|
|
Technology Focus
|
|
|
| Wireless Sensor Networks |
|
10 |
91% |
| Autonomous Robots |
|
2 |
18% |
| Other |
|
4 |
36% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Deployment Scenario
|
|
|
| Indoor partitioned space (e.g.: office space) |
|
9 |
82% |
| Indoor continuous space (e.g.: sport hall) |
|
2 |
18% |
| Outdoor urban space (e.g.: parking lot) |
|
0 |
0% |
| Outdoor non-urban space (e.g.: vineyard, forest) |
|
0 |
0% |
| Other |
|
0 |
0% |
|
|
Deployment Pattern
|
|
|
| Uniform 2D (e.g.: regular lattice ceiling deployment on a single floor in a building) |
|
5 |
45% |
| Non-uniform 2D (e.g.: scattered deployment on a single floor in a building) |
|
3 |
27% |
| Uniform 3D (e.g.: latice over multiple floors in a building) |
|
1 |
9% |
| Non-uniform 3D (e.g.: scattered deployment over multiple floors in a building) |
|
0 |
0% |
| Other |
|
2 |
18% |
|
|
Mobility Support
|
|
|
| Fixed nodes |
|
11 |
100% |
| Mobile nodes |
|
3 |
27% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Variability of Supported SUT Platforms
|
|
|
| Single - homogeneous SUT |
|
4 |
36% |
| Multiple - heterogeneous SUT |
|
7 |
64% |
|
|
Primary SUT Platform
|
|
|
| Tmote Sky |
|
6 |
55% |
| MicaZ |
|
1 |
9% |
| BTnode |
|
0 |
0% |
| eyesIFX |
|
0 |
0% |
| Mica2 |
|
0 |
0% |
| TNOde |
|
1 |
9% |
| Other |
|
3 |
27% |
|
|
Additional SUT Platform
|
|
|
| Tmote Sky |
|
1 |
14% |
| MicaZ |
|
1 |
14% |
| BTnode |
|
1 |
14% |
| eyesIFX |
|
1 |
14% |
| Mica2 |
|
0 |
0% |
| TNOde |
|
1 |
14% |
| Other |
|
2 |
29% |
|
|
Additional SUT Platform
|
|
|
| Tmote Sky |
|
1 |
14% |
| MicaZ |
|
1 |
14% |
| BTnode |
|
1 |
14% |
| eyesIFX |
|
1 |
14% |
| Mica2 |
|
0 |
0% |
| TNOde |
|
1 |
14% |
| Other |
|
2 |
29% |
|
|
Power Supply of SUT Nodes
|
|
|
| Scavenging |
|
0 |
0% |
| Battery |
|
6 |
55% |
| Power over USB |
|
8 |
73% |
| Power over Ethernet |
|
0 |
0% |
| Mains powered |
|
4 |
36% |
| Other |
|
1 |
9% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Control/Monitoring Plane Separation
|
|
|
| In-band (control/monitoring plane and SUT data share the same medium/channel) |
|
5 |
45% |
| Out-of-band (the control/monitoring plane uses separate medium/channel from the SUT) |
|
6 |
55% |
|
|
Control/Monitoring Plane Communication Technologies
|
|
|
| 802.15.4 |
|
4 |
36% |
| Bluetooth |
|
2 |
18% |
| WLAN |
|
3 |
27% |
| USB |
|
6 |
55% |
| Ethernet |
|
5 |
45% |
| Serial (RS-232) |
|
2 |
18% |
| GSM/GPRS/3G |
|
0 |
0% |
| Other |
|
2 |
18% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Control/Monitoring Plane Architecture
|
|
|
| Flat and centralized (direct connection to a single main "controlling" entity/server) |
|
4 |
36% |
| Hierarchical
and distributed (connection via set of secondary nodes / micro-servers
which are then connected to the main "controlling" entity/server |
|
5 |
45% |
| Other |
|
2 |
18% |
|
|
Control/Monitoring Plane Gateway Platforms
|
|
|
| BTnode |
|
2 |
22% |
| Xbow MIB-510 |
|
0 |
0% |
| Xbow MIB-520 |
|
0 |
0% |
| Xbow MIB-600 |
|
0 |
0% |
| Xbow SPB-400 |
|
0 |
0% |
| Xbow NB-100 (Linksys NSLU2) |
|
0 |
0% |
| Motiv Tmote Connect (Linksys NSLU2) |
|
1 |
11% |
| Custom NSLU2 |
|
1 |
11% |
| Laptop PC |
|
3 |
33% |
| Desktop PC |
|
3 |
33% |
| Other |
|
3 |
33% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Job Execution Model
|
|
|
| Batch (automatic execution of jobs without user intervention) |
|
3 |
27% |
| Interactive (direct user control over the job execution process) |
|
7 |
64% |
| Other |
|
3 |
27% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Job Registration and Scheduling Interface
|
|
|
| Web UI |
|
2 |
18% |
| GUI client |
|
4 |
36% |
| Programmable Client APIs |
|
2 |
18% |
| No job registration and scheduling |
|
2 |
18% |
| Other |
|
3 |
27% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Authentication and Authorization Architecture
|
|
|
| Basic HTTP authorization |
|
1 |
9% |
| HTTPS with custom database |
|
1 |
9% |
| HTTPS with PAM backend |
|
0 |
0% |
| HTTPS with LDAP backend |
|
0 |
0% |
| SSH password |
|
0 |
0% |
| SSH public-key |
|
1 |
9% |
| No authentication and authorization |
|
6 |
55% |
| Other |
|
3 |
27% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Job Control Interface
|
|
|
| Web services - REST |
|
0 |
0% |
| Web services - XML-RPC |
|
1 |
11% |
| Custom web services |
|
3 |
33% |
| Custom RPC/RMI in Java |
|
2 |
22% |
| Custom RPC/RMI in Python |
|
2 |
22% |
| Custom RPC/RMI in C++ |
|
1 |
11% |
| Custom shell script / ssh command automation |
|
1 |
11% |
| No interactive job control |
|
3 |
33% |
| Other |
|
1 |
11% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
SUT Node Control Services
|
|
|
| Power cycling |
|
4 |
36% |
| Resetting |
|
6 |
55% |
| Image programming |
|
5 |
45% |
| Image erasing |
|
4 |
36% |
| Data collection |
|
7 |
64% |
| Data injection |
|
3 |
27% |
| Power consumption monitoring |
|
2 |
18% |
| Other |
|
7 |
64% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
SUT Data Access
|
|
|
| Direct raw access to the serial/secondary channel output of the SUT nodes |
|
5 |
63% |
| Direct raw access to the serial/secondary channel input of the SUT nodes |
|
5 |
63% |
| Indirect access to serial/secondary channel via client library APIs |
|
4 |
50% |
| Indirect access to serial/secondary channel via "shell" abstraction |
|
1 |
13% |
| Indirect access to serial/secondary channel via data persistence on the server |
|
3 |
38% |
| Other |
|
0 |
0% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
SUT Data Persistence
|
|
|
| File-system storage in raw text format |
|
3 |
33% |
| File-system storage in custom XML format |
|
0 |
0% |
| File-system storage in Common Base Event (CBE) format |
|
0 |
0% |
| Database storage in raw text format |
|
3 |
33% |
| Database storage in custom XML format |
|
0 |
0% |
| Database storage in Common Base Event (CBE) format |
|
0 |
0% |
| Database storage with automatic message field -> table attribute conversion (like in MoteLab) |
|
0 |
0% |
| No persistence |
|
2 |
22% |
| Other |
|
1 |
11% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Time Stamping Services
|
|
|
| Source-based time-stamping (time stamping in the SUT) |
|
1 |
11% |
| Distributed
time-stamping using time synchronized control/monitoring plane (time
stamping at the micro-server/secondary node level that are globally
synchronized using a service like NTP or FTSP) |
|
3 |
33% |
| Centralized time-stamping (time stamping at the server) |
|
1 |
11% |
| No time stampiing |
|
3 |
33% |
| Other |
|
1 |
11% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Integration with Simulators and Emulators
|
|
|
| Integration of simulated nodes in the testbed run (e.g.: emulation of interaction between real and simulated nodes) |
|
3 |
30% |
| Integration
of testbed nodes in a simulation run (e.g.: use of real comm interfaces
from the testbed nodes while simulating the SW stack in a simulator) |
|
2 |
20% |
| No integration |
|
7 |
70% |
| Other |
|
2 |
20% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|
|
Remote Use Policy
|
|
|
| Payed access |
|
0 |
0% |
| Free access for (project) partners |
|
2 |
20% |
| Free access for academia |
|
1 |
10% |
| Free access for industry |
|
0 |
0% |
| No remote access |
|
8 |
80% |
| Other |
|
0 |
0% |
People may select more than one checkbox, so percentages may add up to more than 100%.
|