Orion Routing Protocol for Delay-Tolerant Networks

In this paper, we address the problem of efficient routing in delay tolerant network. We propose a new routing protocol dubbed as ORION. In ORION, only a single copy of a data packet is kept in the network and transmitted, contact by contact, towards the destination. The aim of the ORION routing protocol is twofold: on one hand, it enhances the delivery ratio in networks where an end-to-end path does not necessarily exist, and on the other hand, it minimizes the routing delay and the network overhead to achieve better performance. In ORION, nodes are aware of their neighborhood by the mean of actual and statistical estimation of new contacts. ORION makes use of autoregressive moving average (ARMA) stochastic processes for best contact prediction and geographical coordinates for optimal greedy data packet forwarding. Simulation results have demonstrated that ORION outperforms other existing DTN routing protocols such as PRoPHET in terms of end-to-end delay, packet delivery ratio, hop count and first packet arrival

Using Neighborhood Beyond One Hop in Disruption-Tolerant Networks

Most disruption-tolerant networking (DTN) protocols available in the literature have focused on mere contact and intercontact characteristics to make forwarding decisions. Nevertheless, there is a world behind contacts: just because one node is not in contact with some potential destination, it does not mean that this node is alone. There may be interesting end-to-end transmission opportunities through other nearby nodes. Existing protocols miss such possibilities by maintaining a simple contact-based view of the network. In this paper, we investigate how the vicinity of a node evolves through time and whether such information can be useful when routing data. We observe a clear tradeoff between routing performance and the cost for monitoring the neighborhood. Our analyses suggest that limiting a node's neighborhood view to three or four hops is more than enough to significantly improve forwarding efficiency without incurring prohibitive overhead.Comment: 5 pages, 5 figures, 1 tabl