Condroid WSN/DTN Gateway - Verification Rest Report

!

!"#$%&#'()&*!)+''
,*-./.0)&.1#'&*"&'
-*21-&'
! ,*-".1#'345'

2011
!"#$%&'()%*+(,%+-%"( !"#$%&'(&#*&.(
' (
'
Lan Sun (lansun@kth.se), 15 ECTS (((((/#*&.(*01(2"#$%&'(#30%"(
Hervé Ntareme
Qing An (qinga@kth.se), 15 ECTS
/#4&#*&.(
Michel Hognerud
Jun Gao (jungao@kth.se), 15 ECTS
/.*+25#0(
Laili Aidi (aidi@kth.se), 18 ECTS
Björn Pehrson!
Yasir Ali (yasireal@kth.se), 15 ECTS

SUMMER CSD

WSN/DTN Gateway Verification Test Report V.1.0
!

Revision History

Version Date Responsible Change
V1.0 2011-10-13 Laili Aidi Initial version of the document

2

!

Contents

Contents.................................................................................................................................................................................. 3

Summary ................................................................................................................................................................................. 4

Abbreviation........................................................................................................................................................................... 5

1. Introduction ................................................................................................................................................................... 6

2. Hardware Verification .................................................................................................................................................. 7

3. Network Architecture & Configuration Verification .............................................................................................. 9

3. Bottom-ware Software Verification .........................................................................................................................11

4. Middle-ware Software Verification...........................................................................................................................13

5. Upper-ware Software Verification............................................................................................................................15

6. Conclusion ...................................................................................................................................................................21

7. Reference......................................................................................................................................................................22

3

!

Summary

This document describes the Verification test of the WSN/DTN Gateway, which was done during Week 40 –
Week 41, October 3, 2011 to October 13, 2011.

4

!

Abbreviation
Abbreviations used in this document:
Abbreviation Description
MySQL An Open source Relational database management system (RDBMS)
ALIX Board Single board computer capable of running operating systems
SunSPOT Embedded microprocessor that runs Java
Voyage Linux GNU/Linuxderived distribution that is best run on a x86 embedded platforms
Barkeley DB Software library that provides embedded database for key/value data
USB Universal Serial Bus
WPA Wi-Fi Protected Access
Wi-Fi Trademark of a product based on IEEE 802.11
Apache HTTP Server
PHP Hypertext Preprocessor, Server-side HTML embedded scripting language
Dnsmasq Lightweight version to configure DNS forwarder and DHCP server.
JDK Java Development Environment
Apache Ant XML-based build scripting language
Hald HAL Daemon
SunSPOT Embedded microprocessor that runs Java
DHCP Dynamic Address Allocation Protocol
AP Access-Point
DNS Domain Name System
ProPHET Probabilistic Routing Protocol using History of Encounters and Transitivity
Wi-Fi Trademark of a product based on IEEE 802.11
DTN Delay Tolerant Network / Delay Disruptive Network
WSN Wireless Sensor Network
DTN Delay Tolerant Network / Delay Disruptive Network
Bytewalla Implementation of DTN in the Android platform.

5

!

1. Introduction
The main objective of this document is to verify the WSN/DTN Gateway, which is a part of the Condroid
project objective. The verification is mainly focus on 4 elements, which are listed as below:
a. Hardware Verification
b. Bottom-ware software verification
c. Middle-ware software verification
d. Upper-ware software verification

Table 1. Project Identification
Project Name Project Number Project Manager Project Owner Date Created
Condroid 1 Laili Aidi Hervé Ntareme 2011-06-13
Project Sponsor Program Manager Verificator
Laili Aidi
KTH/ICT/TSLAB Björn Pehrson
Qing An

6

!

2. Hardware Verification
The simulation of WSN/DTN Gateway environment needs several main equipments, which should be met in
order to set up, make it work and tested properly. The Verification components are based on the WSN/DTN
Gateway System Architecture & Requirement [1]:

Table 2. Hardware Verification Matrix
Verification
No Status Specification Amount Detail / Comment
Element
Type: ALIX2d13
• CPU: 500 MHz AMD Geode LX800
• RAM: 256 MB DDR DRAM
• Storage: CF socket, 44 pin IDE header
• Power: DC jack or passive POE, min. 7V to max.
20V
• Network Interface: 3 Ethernet channels (Via 3
VT6105M 10/100)
• I/O: DB9 serial port, dual USB port
• Casing: For 6x6" board size, Silver color
• WiFi Antenna: Black 25 cm, 2.4 GHz, 5dBI indoor The WiFi Antenna
1 ALIX Board Pass Omni, RSMA female connector and cable has been installed in
• Power cable with adapter all the ALIX boards
Type: ALIX2d2
• CPU: 500 MHz AMD Geode LX800
• RAM: 256 MB DDR DRAM
• Storage: CF socket, 44 pin IDE header
• Power: DC jack or passive POE, min. 7V to max.
1
20V
• Network Interface: 2 Ethernet channels (Via
VT6105M 10/100)
• I/O: DB9 serial port, dual USB port
• Casing: For 6x6" board size, Silver color

7

!

• WiFi Antenna: Black 15 cm, 2.4 GHz, 5dBI indoor
Omni, RSMA female connector and cable
• Power cable with adapter
Compact Flash 4 GB 1 The CFs have been
2 Compact Flash Pass Compact Flash Reader 1 installed on all the
USB Connector 1 ALIX boards
Switch – Netgear 1 -
3 Switch Set Pass UTP Cables 7 -
Adaptor – Netgear 12 V 1 -
HTC Tatoo (IMEI: 358355027509369 and
2 The SD Card in
Pass 358355020235012) + 2 GB SD Card
Phone with IMEI
4 Android Phone with HTC Nexus One + Power charging adaptor
1 358355020235012 is
note (EMEI: 354957037701540)
broken
USB Connector 3

8

!

3. Network Architecture & Configuration Verification
During the verification process, the network configuration of the WSN/DTN Gateway environment has been
set up as follow:
! 1 WSN/DTN Gateway with City / Receiver mode (Identification: WSN/DTN Gateway 2):
• WLAN0 Interface, activated as AP with the specification: IP Address 192.168.2.1, SSID “Bytewalla-
Voyage2”, lease IP Addresses with range 192.168.2.35 - 192.168.2.50. Multicast is enabled in this
interface
• Eth0 Interface, activated as DHCP client
• Eth1 Interface, IP Address 192.168.24.2. The default route is enabled in this interface, and it is
connected directly with Ethernet LAN to WSN/DTN Gateway 4
• Eth2 Interface, IP Address 192.168.22.1

! 2 WSN/DTN Gateways with Village / Sender mode:
1. The Village node 1 (Identification: WSN/DTN Gateway 3)
• WLAN0 Interface, activated as AP with the specification: IP Address 192.168.3.1, SSID: “Bytewalla-
interface to allow the Core-Engine SunSPOT running on the OS.
• Eth0 Interface, activated as DHCP client.
• Eth2 Interface, IP Address 192.168.23.1.

2. The Village node 2 (Identification: WSN/DTN Gateway 4):
• WLAN0 Interface, activated as AP with the specification: IP Address 192.168.4.1, SSID “Bytewalla-
interface to allow the Core-Engine SunSPOT running on the OS.
• Eth0 Interface, activated as DHCP client.
• Eth2 Interface, IP Address 192.168.24.1. The default route is enabled in this interface, and it is
connected directly with Ethernet LAN to WSN/DTN Gateway 2

9

!

In order to isolate the system, we also have set so the Village nodes able to connect directly to City node with
Ethernet LAN connection with the IP arrangement described above. Thus we can say this configuration has
been meet up the requirement as it is fit to simulate the Network Architecture specification that is described in
the WSN/DTN Gateway System Architecture & Requirement [1].

Figure 1. WSN/DTN Gateway Test-Bed Network Architecture

10

!

3. Bottom-ware Software Verification
The Bottom-ware software verification contains the verification for the elements below:
• Voyage OS verification
• DTN2 verification
This verification is based on the procedure that is described in Voyage & DTN2 Installation & Configuration
Guide On ALIX Board [2]. The result of this verification are listed in the table below:

Table 3. Bottom-ware Software Verification Matrix
Verification
No Status Specification Detail / Comment
Element

1 Voyage OS Pass Voyage OS 0.75 Voyage OS 0.75 is installed in all 4 ALIX boards

The latest version of dependencies
packages for DTN2 installation found
in the system:
The libdb is not the latest version because
build-essential, autoconf, g++,
libdb5.1 is currently not stable when this
libavahi-compat-libdnssd-dev,
2 DTN2 Pass procedure is done, and there is no BarkeleyDB
libdb4.6, libdb4.6-dev, libxerces-c2-
4.8 available on the website, thus we fall back to
dev, libxerces-c28, libexpat1-dev,
libdb4.7
mono-1.0-devel, tcl8.4, tcl8.4-dev,
tcllib, tclreadline, tclx8.4-dev, tclx8.4,
zlib1g-dev, libdb4.7

Berkeley DB version 4.7 with AES encryption
Berkeley DB (13M). The path can be found in environment
variable in root/usr/local/BerkeleyDB.4.7/lib

Oasys version 1.4 (Oasys-1.4.0) is found in
Oasys
root/dtn2/oasys/

11

!

DTN version 2.7 (DTN-2.7.0) is found in
DTN2 root/dtn2/DTN2/ and the configuration is
found in /usr/voyagedtn/dtn.conf

The WSN/DTN Gateways have been
configured with Dynamic Route proPHET
routing. However, it seems the proPHET
routing implementation in Voyage OS is not
table yet. Thus sometime the DTN cannot
discover the link to the other DTN node event
Pass they are directly connected. To solve this, we
3 with DTN Configuration have to delete the BarkeleyDB file in
note /usr/voyagedtn/db and
/usr/voyagedtn/bundles, then initiate the
database again with
/dtn2/DTN2/daemon/dtnd -c
/usr/voyagedtn/dtn.conf --init-db. After this is
done, all the node can send and receive simple
DTN message and file transfer

HTC Tatoo (IMEI: 358355027509369
and 358355020235012) + 2 GB SD
Card The SD Card in HTC Tatoo Phone with IMEI
Pass
358355020235012 is broken, thus we did not use
4 Android Phone with HTC Nexus One + Power charging
it. The Bytewalla software versions 4 have been
note adaptor
installed to the phones.
(EMEI: 354957037701540)

USB Connector

12

!

4. Middle-ware Software Verification
The Middle-ware software verification contains the verification for the elements below:
• DNS service
• DHCP server and client service
• Web server service
• PHP5
• Database server service
• HALD service
• Java
• Ant
• Sunspot
This verification is based on the procedure that is described in WSN/DTN Gateway Middleware Installation
and Configuration Guide On ALIX Board [3]. The result of this verification are listed in the table below:

Table 4. Middle-ware Software Verification Matrix
Verification
Element

DNS service is set up with DNSMAQ, it is running
DNS Server
properly in all 3 WSN/DTN Gateways.

1 DNS Service Pass Kernel IP routing table & resolv.conf configuration are
DNS Client set up properly and 3 WSN/DTN Gateways can connect
to the Internet.

DHCP server service is set up with DNSMAQ, it is
running properly in all 3 WSN/DTN Gateways:
• City Node: lease IP Addresses with range
192.168.2.35 - 192.168.2.50
2 DHCP DHCP Server
• Village Node 1: lease IP Addresses with range
192.168.3.35 - 192.168.3.50
• Village Node 2: lease IP Addresses with range
192.168.4.35 - 192.168.4.50

13

!

DHCP client service is running properly, and all 3
DHCP Client WSN/DTN Gateways can connect the KTH network
and get the IP address in its Eth0 interface

2 Apache Pass Apache service -
3 PHP Pass PHP version 5 -

MySQL Server is running properly in all 3 WSN/DTN
4 MySQL Pass MySQL version 5.1 Gateways with sunspot account exist to be used by
WSN/DTN Gateway Upper-ware platform.

5 Java Pass JDK version 6 -
6 Ant Pass Apache Ant version 1.8 -
7 HALD Pass - -

SunSPOT SDK Yellow is found in all 3 WSN/DTN
Pass
Gateways, in /root/SunSPOT/sdk-yellow-101117-1, but
8 SunSPOT with SunSPOT SDK
it unable to get socket connection in Voyage OS opened
note
to connect with the Base station.

14

!

5. Upper-ware Software Verification
The Upper-ware software verification contains the verification for the elements below:
• WSN/DTN Spot Application
• WSN/DTN Core-Engine Receiver
• WSN/DTN Core-Engine Sender
• WSN/DTN Web-base Admin
This verification is based on the procedure that is described in WSN/DTN Gateway Engine Installation Guide
& User Manual [4]. The result of this verification are listed in the table below:

a. Verification WSN/DTN Spot Application
Table 5. WSN/DTN Spot Application Verification Matrix
Verification
Element
The spot application that is used in
HALD Service able to detect the connected
WSN/DTN Gateway can be deployed
SPOT mote. The Application can be found
1 Installation Pass to SunSPOT mote from any
in /root/core-
WSN/DTN Gateways using it’s USB
engine/WSNDTNSpotEngine/
interfaces

The SPOT application able to read the
The temperature, humidity, battery status and
2 Functionalities Pass sensor as specified and broadcasts that
time when the data is gathered is sent
to any Base station in its range

15

!

b. Verification WSN/DTN Core-Engine Sender Application
Table 6. WSN/DTN Sender Engine Verification Matrix
Verification
Element

The Application can be found in /root/core-
Application can run in WSN/DTN
1 Deployment Pass Gateway engine/WSNDTNCoreEngine-Sender/ and
run using this command: ant host-run

The DTN module able to be run
Pass DTN Daemon module
automatically from the application

The WSN module unable to run and read the
Pass sensor data broadcasted by the Mote(s), as
with WSN Daemon module the Voyage OS can not granted the
note application to open the socket connection to

Basic the Base station
2
functionalities
The application can respond the instruction
set by user trough WSN/DTN Web base
GUI, which are:
Pass Instruction aware module • The specification of WSN/DTN Gateway
(DTN node name, DTN receiver name)
• Starting / Stopping service (DTN sending
& WSN data receiving from the mote)

Data The application can compress the file contain
3 distribution Pass Compression module WSN data before it is sent as DTN Bundle,
functionalities using simple tar.gz data compression

16

!

The application can trigger scheduler
distribution of DTN send; using dtncp
command, in every specific span time, in this
simulation it is set statically every 1m.
Scheduler distribution module
Application can check if there is any new
data in the database that is not distributed yet
and trigger compression module before send
it as DTN bundle

The application can response to the
controlled distribution instruction from user
that is set trough WSN/DTN Web base
Controlled distribution module GUI. Application can check if there is any
new file created by Web base GUI that is not
distributed yet and trigger compression
module before send it as DTN bundle

Application can receive the data from the
Spot application, but because the Voyage OS
cannot grant any socket connection to be
opened by the application to make
Not connection to the Base station, the
Data receiving module
pass application cannot read any data from the
Data Logging
4 Spot application from its attached Base
Functionalities
station. However, this module is running
properly in other OS (MacOS, Ubuntu,
Windows).

The application can inject the data to its
Pass Data Injection module
database

17

!

c. Verification WSN/DTN Core-Engine Receiver Application
Table 7. WSN/DTN Receiver Engine Verification Matrix
Verification
Element

The Application can be found in /root/core-
engine/WSNDTNCoreEngine-Receiver/
Application can run in WSN/DTN and run using this command:
1 Deployment Pass Gateway
Java –jar “core-
engine/WSNDTNCoreEngine-Receiver/
dist/WSNDTNCoreEngine-Receiver.jar”

The DTN module able to be run
DTN Daemon module
automatically from the application

The application can respond the instruction
Basic set by user trough WSN/DTN Web base
2 Pass
functionalities GUI, which are:
Instruction aware module • The specification of WSN/DTN Gateway
(DTN node name)
• Starting / Stopping service (DTN receiving
module)

The application can trigger scheduler
receiving of DTN receive; using dtncpd
command, in every specific span time, in this
Scheduler receiving module
simulation it is set statically every 1s. So
Data
application will check if there is any new file
3 distribution Pass
received from other DTN node
functionalities

The application can uncompress the file
Compression module
received from DTN contain WSN data

18

!

Application can read the WSN data from the
Pass DTN File reading module
file received as DTN bundle

The Application can check if the data in the
Data Logging
4 Pass Data redundancy checking file receive as DTN bundle is already in the
Functionality
its database or not

The application can inject the data to its
Pass Database Data Injection module
database

d. Verification WSN/DTN Web-base Admin Application
Table 8. WSN/DTN Web-base Admin Verification Matrix
Verification
Element

The PHP file can be found in
Application can run in WSN/DTN /root/var/www and the web page can be
1 Deployment Pass Gateway
accessed in all network interfaces of the
WSN/DTN Gateway

Management User can set the mode of the gateway, either
2 WSN/DTN Gateway Mode
functionalities as Village (Sender) or City (Receiver)

Pass
User can set the name of the gateway. This
WSN/DTN Gateway name data is also used to set the dtn node of this
gateway and put in dtn.conf file as EID name

User can set the name of the gateway receiver
Pass WSN/DTN Gateway Receiver name. This data is also used in dtn.conf file
as route in proPHET routing

19

!

User can control the core-engine to running
Pass Start/Stop Core-Engine module the WSN data receiving from the SPOT
motes and DTN data sending / receiving

The application can create new DTN
configuration file (dtn.conf) based on data
Pass DTN configuration module
that is set by user in Management Gateway
page

User can see the detail of the running Core-
Monitoring Engine, either it is as Village (Sender) or City
3 Pass -
functionality (Receiver), and the detail about the DTN
bundle (transferred, pending, received, etc)

User can see the WSN data in the table,
Pass Data Display module
organized based on Gateway ID and spot ID

Data User can generate the graphs (temperature,
Processing & Pass Graphing Data module humidity, battery level) form specific spot,
4 during specific range time, in specific gateway
Analyzing Sub-
System
User can download the data (temperature,
Pass Data Download humidity, battery level) form specific spot,
during specific range time, in specific gateway

Data User can choose to distribute specific data as
5 distribution Pass Controlled distribution module DTN bundle form specific spot, during
functionalities specific time range

20

!

6. Conclusion
Based on the verification elements that have been done to the WSN/DTN Gateway both as Village (Sender)
and City (Receiver) mode, we can conclude that the concept in this system is feasible to be deployed in real-life
scenario, and the platform that has been deployed in this project meet the requirement to make the system run.
However, there are still some issues rise and it is necessary to add several modules in order to improve the
features of this WSN/DTN gateway, including the improvement in Core-Engine, Bytewalla, DTN2 and
SunSPOT Deployment issues in Voyage OS.

21

!

7. Reference
[1] WSN/DTN Gateway System Architecture & Requirement Version 1.0
http://csd.xen.ssvl.kth.se/csdlive/content/wsndtn-gateway-system-analysis-design Last visited: October,
2011
[2] Voyage & DTN2 Installation & Configuration Guide On ALIX Board Version 1.4
http://csd.xen.ssvl.kth.se/csdlive/content/wsndtn-gateway-system-development Last visited: October
2011
[3] WSN/DTN Gateway Middleware Installation and Configuration Guide On ALIX Board Version
1.2 http://csd.xen.ssvl.kth.se/csdlive/content/wsndtn-gateway-system-development Last visited: October
2011
[4] WSN/DTN Gateway Engine Installation Guide & User Manual Version 1.1
http://csd.xen.ssvl.kth.se/csdlive/content/wsndtn-gateway-system-deployment-testing Last visited:
October 2011

22

Condroid WSN/DTN Gateway - Verification Rest Report

Recommandé

Recommandé

Contenu connexe

Similaire à Condroid WSN/DTN Gateway - Verification Rest Report

Similaire à Condroid WSN/DTN Gateway - Verification Rest Report (20)

Plus de Laili Aidi

Plus de Laili Aidi (20)

Dernier

Dernier (20)

Condroid WSN/DTN Gateway - Verification Rest Report