# Enhanced IoT-Based End-To-End Emergency and Disaster Relief System
## 5 Experimentation
### Results and Discussion  
In this subsection, we present the results of the experiment aimed to evaluate the CROW\({}^{2}\) system performance based on the ORACE-Net routing protocol on a real test-bed. To do so, we consider the following metrics: throughput and jitter, End-to-End delay (\(E2E_{delay}\)) and End-to-End Link Quality Estimation (\(E2E_{LQE}\)). Throughput is the maximum amount of data processed for sending from the source node (i.e., ORACE-Net mobile device) to the destination node (i.e., Labeeb-IoT platform). \"Jitter\" is the amount of variation in latency/response time (typically in milliseconds). Reliable connections consistently report back the same latency over and over again. Much variation (or 'jitter') is an indication of connection issues. Jitter is a relevant indicator of the network performance because it defines what kind of applications the network is able to support. The \(E2E_{LQE}\) is calculated by the ORACE-Net protocol to estimate end-to-end links. The \(E2E_{delay}\) is the round trip time delay recorded from the source node to the destination node. This latter metric informs also about nodes'  
\begin{table}
\begin{tabular}{c c} \hline \hline \multicolumn{2}{c}{**General Settings**} \\ \hline
**Parameter** & **Setting** \\ \hline ORACE-Net Tactical Devices & 4 (Raspberry Pi 2) \\  & OS: Raspbian v8.0 \\ \hline Mobile nodes & 2 (Samsung Galaxy S3-I9300, rooted) \\  & OS: Android 4.2.2 CyanogenMod 10.0 \\ \hline Wireless mode & Ad hoc \\ \hline ESID & CROW2 \\ \hline Wireless standard & IEEE 802.11n/2.412 GHz (Channel 1) \\ \hline Transmission power & 0 dBm \\ \hline Experiment area & 30 m \(\times\) 150 m \\ \hline CC-node connection & Ethernet to Internet \\  & Ad hoc WiFi to ORACE-Net network \\ \hline Experimentation duration & 30 min/iteration \\ \hline Power batteries & - Smart phone: 2100 mAh Li-Ion (3.7 v) \\  & - Raspberry-Pi: 10,000-mA Li-ion (12 v) \\  & - CC-node: 12 V power supply \\ \hline \multicolumn{2}{c}{**ORACE-Net Protocol Settings**} \\ \hline Application layer & MQTT client used for pushing \\  & data to the Labeeb-IoT platform \\ \hline MQTT msgsize/intervals & 30 Kb/1 s \\ \hline Hello/ADV packet size & 20/25 bytes \\ \hline Hello/ADV intervals & 3 s \\ \hline Multicast address/port & 224.0.0.0/10000 \\ \hline \multicolumn{2}{c}{**Shimmer Sensing Settings [30]**} \\ \hline Wireless standard & Bluetooth IEEE 802.15.1 \\ \hline \multirow{3}{*}{Sensed data} & Pressure, Temperature, Gyroscope \\  & (x, y, zaxis-angle), acceleration (x, y, z), \\  & magnetometer (x, y, z), battery level \\ \hline Device/Body & 1 (with multiple sensors) \\ \hline Buffer [31] & 1024 bytes \\ \hline Message interval & 1 s \\ \hline \hline \end{tabular}
\end{table}
Table 2: Experimentation parameters and configuration settings.  
disconnections. In addition to the above performance metrics, we discuss the collected data from the IoT platform to detect motions and prevent unavailability. Finally, we discuss the overall approximate interference and noise affecting the indoor signal using an academic version of the AirMagnet software.