## 3 Survey Results
### Software Level Tasks
\begin{table}
\begin{tabular}{c l l l l l} \hline \hline
**Nr** & **Codename** & \begin{tabular}{l} **Kernel service** \\ **count** \\ \end{tabular} & \
\begin{tabular}{l} **Kernel services** \\ **task count** \\ \end{tabular} &
\begin{tabular}{l} **App-level tasks** \\ **task count** \\ \end{tabular} \\ \hline
5 & Counter-sniper &? &? &? &? &? \\
6 & Electro-shepherd &? & - & & sense and send \\
7 & Virtual fences &? & MAC & 1 & sense and issue warning (play sound file) \\
8 & Oil tanker & 0 & & 4 & cluster formation and time sync, sensing, data transfer \\
9 & Enemy vehicles &? &? &? &? \\
10 & Trove game & 1 & MAC & 3 & sense and send, receive, buzz \\
11 & Elder RFID & 1 & MAC & 2 & query RFID, report \\
12 & Murphy potatoes & 2 & MAC, routing & 1 & sense and send \\
13 & Firewavenet & 2 & MAC, routing & 2 & sensing and sending, reception and time-sync \\
14 & AlarmNet &? &? & 3 & query processing, sensing, report sending \\
15 & Ecuador Volcano & 3 & time sync, remote reprogram, routing & 3 & sense, detect events, process queries \\
16 & Pet game & 2 & MAC, routing &? & sense and send, receive configuration \\
17 & Plug & 2 & MAC, routing, radio listen & 2 & sensing and statistics and report, radio RX \\
18 & B-Live &? &? & 3 & sensing, actuation, data transfer \\
19 & Bimontion & 2 & MAC, time sync & 1 & sense and send \\
20 & AID-N & 3 & MAC, routing, transport & 3 & query processing, sensing, report sending \\
21 & Firefighting & 1 & routing & 2 & sensing and sending, user input processing \\
22 & Rehabil & 0? &? & 1 & sense and send \\
23 & CargoNet & 0? &? & 1 & sense and send \\
24 & Fence monitor & 2 & MAC, routing & 4 & sense, preprocess, report, receive neighbor response \\
25 & BikeNet & 1 & MAC & 5 & hello broadcast, neighbor discovery and task reception, sensing, data download, data upload \\
26 & BriMon & 3 & Time sync, MAC, routing & 3 & sensing, flash storage, sending \\
27 & IP net &? &? &? &? \\
28 & Smart home &? &? &? &? \\
29 & SVATS & 2 & MAC, time sync & 2 & listen, decide \\
30 & Hitchhiker & 4 & MAC, routing, transport, timesync & 1 & sense and send \\
31 & Daily morning & 1 & MAC & 1 & sense and send \\
32 & Heritage & & &? &? \\
33 & AC meter &? &? & 2 & sampling, routing \\
34 & Coal mine & 2 & MAC, routing & 2 & receive beacons, send beacon and update neighbor \\
35 & ITS & 2 & MAC, routing & 1 & listen for queries and sample and process and report \\
36 & Underwater & 2 & MAC, timesync & 3 & sensing + sending, reception, motor control \\
37 & PipeProbe & 0? & - & 1 & sense and send \\
38 & Badgers & 3 & MAC, routing, User Datagram & 1 & sense and send \\  & & & Protocol (UDP) connection establishment & & \\
39 & Helens volcano & 5 & MAC, routing, transport, time sync, remote reprogram & 5 & sense, detect events, compress, Remote Procedure \\
40 & Tunnels & 2 & MAC, routing & 1 & sense and send \\ \hline \hline \end{tabular}
\end{table} 
Table 14: _Cont._programming approach and provide maximum resource efficiency, which might be important for the most resource-constrained platforms. Figure 11: **The number of application layer software tasks used in deployments.–Thirty-three percent of deployments use just one task; however, up to six tasks are used in more complex cases. The task count is unknown in 18% of deployments**  
Figure 10: **The number of kernel level software services used in deployments—fifty-five percent of deployments use two or less kernel services. For 28%, the kernel service count is unknown. **