In the future work, there is plenty room for improvements on IBR-DTN utilisation, the applications developed and overall system performance analysis. For instance, IBR-DTN protocol implements a lot of pretty good functionalities that we did not test, such as proactive and reactive fragmentation, security mechanisms and data compression. Instead of using the IBR-DTN API, developed applications functionalities could be embedded in IBR-DTN code. Although their performance may increase, it has the disadvantage of when a new IBR-DTN version comes out, porting every- thing to the new version could be hard work. Also, DTN performance analysis could be performed in both directions, from sense units to the server and in the reverse way. Finally, at this moment, sense units can run the sending sensors’ data over TCP and DTN applications independently or both at the same time. However, in these ways, sending sensors’ data over TCP is not prioritised. As future work, is necessary to implement the network manager discussed in chapter 4, which integrates both applications and ables sense units to automatically choose the best interface to accomplish sensors’ data transmission.