22.07.2013 Views

Routing protocols for mobile ad-hoc networks - Computer Networks ...

Routing protocols for mobile ad-hoc networks - Computer Networks ...

Routing protocols for mobile ad-hoc networks - Computer Networks ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Routing</strong> <strong>protocols</strong> <strong>for</strong> <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong><br />

We continue our series on <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong> with a discussion of routing <strong>protocols</strong>, or how the in<strong>for</strong>mation is<br />

going to move throughout the network.<br />

Mobile <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong>, also known as short-lived <strong>networks</strong>, are autonomous systems of <strong>mobile</strong> nodes <strong>for</strong>ming<br />

network in the absence of any centralized support. This is a new <strong>for</strong>m of network and might be able to provide<br />

services at places where it is not possible otherwise. Absence of fixed infrastructure poses several types of<br />

challenges <strong>for</strong> this type of networking. Among these challenges is routing.<br />

By routing, we mean process of exchanging in<strong>for</strong>mation from one station to the other stations of the network.<br />

<strong>Routing</strong> <strong>protocols</strong> of <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network tend to need different approaches from existing Internet <strong>protocols</strong>,<br />

since most of the existing Internet <strong>protocols</strong> were designed to support routing in a network with fixed structure. In<br />

the ac<strong>ad</strong>emic and industrial world, those who think about such things have written quite a few papers proposing<br />

various routing solutions <strong>for</strong> <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong>. Proposed solutions could be classified into six types: table-<br />

driven, on-demand, hierarchical, power-aware, geographical, and multicast <strong>protocols</strong>.<br />

Table - driven <strong>protocols</strong><br />

Table-driven <strong>protocols</strong> are one of the old ways of acquiring routing in <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong>. These <strong>protocols</strong><br />

maintain consistent overview of the network. Each node uses routing tables to store the location in<strong>for</strong>mation of<br />

other nodes in the network. This in<strong>for</strong>mation is used to transfer data among various nodes of the network.<br />

To ensure the freshness of the routing tables, these <strong>protocols</strong> <strong>ad</strong>opts different sorts of mechanisms. One of the<br />

<strong>ad</strong>opted methods is bro<strong>ad</strong>casting "hello," a special message containing <strong>ad</strong>dress in<strong>for</strong>mation, at fixed intervals of<br />

time. On receiving this message, each node updates its routing tables with fresh locations in<strong>for</strong>mation of other<br />

participating nodes. Destination Sequence Distance Vector routing protocol (DSDV), Wireless <strong>Routing</strong> Protocol (WRP)<br />

and Cluster-he<strong>ad</strong> Gateway Switch <strong>Routing</strong> (CGSR) are some of the popular table-driven <strong>protocols</strong> <strong>for</strong> <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong><br />

<strong>networks</strong>.<br />

Table-driven <strong>protocols</strong> might not be considered an effective routing solution <strong>for</strong> <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network. Nodes in<br />

<strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong> operate with low battery power and with limited bandwidth. Presence of high mobility,<br />

large routing tables and low scalability result in consumption of bandwidth and battery life of the nodes. Moreover<br />

continuous updates could create unnecessary network overhe<strong>ad</strong>.<br />

On - demand routing <strong>protocols</strong><br />

Another in the family of routing <strong>protocols</strong> <strong>for</strong> <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network is on-demand routing <strong>protocols</strong>. With on-<br />

demand <strong>protocols</strong>, if a source node requires a route to the destination <strong>for</strong> which it does not have route in<strong>for</strong>mation,<br />

it initiates a route discovery process which goes from one node to the other until it reaches to the destination or an<br />

intermediate node has a route to the destination.<br />

It is the responsibility of the route request receiver node to reply back to the source node about the possible route<br />

to the destination. The source node uses this route <strong>for</strong> data transmission to the destination node. Some of the better


known on-demand <strong>protocols</strong> are Ad-<strong>hoc</strong> On-demand Distance Vector routing (AODV), Dynamic Source <strong>Routing</strong> (DSR)<br />

and Temporary Ordered <strong>Routing</strong> Algorithm (TORA).<br />

These <strong>protocols</strong> differ on storing the previously known route in<strong>for</strong>mation and on how they use the established route<br />

data. Again, in a network with many participating nodes we may suffer with same sort of problems what we have<br />

seen in table-driven <strong>protocols</strong>.<br />

Conclusion<br />

In conclusion, routing is one of the core issues in <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network. An effective routing mechanism will be<br />

helpful to extend the successful deployment of <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong>. Current routing <strong>protocols</strong> provide routing<br />

solutions up to a certain level, but are lacking the ability to handle other related issues.<br />

Moreover most of these <strong>protocols</strong> have designed and implemented on small scale. If these <strong>protocols</strong> could be<br />

extended further by taking into accounts other routing related factors we may come out with a standard routing<br />

solution <strong>for</strong> <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network.<br />

Ad Hoc <strong>Networks</strong><br />

Introduction<br />

An <strong>ad</strong>-<strong>hoc</strong> network is a self-configuring network of wireless links connecting <strong>mobile</strong> nodes. These nodes may be<br />

routers and/or hosts. The <strong>mobile</strong> nodes communicate directly with each other and without the aid of access points,<br />

and there<strong>for</strong>e have no fixed infrastructure. They <strong>for</strong>m an arbitrary topology, where the routers are free to move<br />

randomly and arrange themselves as required.<br />

Each node or <strong>mobile</strong> device is equipped with a transmitter and receiver. They are said to be purpose-specific,<br />

autonomous and dynamic. This compares greatly with fixed wireless <strong>networks</strong>, as there is no master slave<br />

relationship that exists in a <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network. Nodes rely on each other to established communication, thus<br />

each node acts as a router. There<strong>for</strong>e, in a <strong>mobile</strong> <strong>ad</strong>-<strong>hoc</strong> network, a packet can travel from a source to a destination<br />

either directly, or through some set of intermediate packet <strong>for</strong>warding nodes.<br />

In a wireless world, dominated by Wi-Fi, architectures which mix mesh networking and <strong>ad</strong>-<strong>hoc</strong> connections are the<br />

beginning of a technology revolution based on their simplicity.<br />

Ad <strong>hoc</strong> <strong>networks</strong> date back to the Seventies. They were developed by the Defense Forces, to comply with a military<br />

framework. The aim was to rapidly deploy a robust, <strong>mobile</strong> and reactive network, under any circumstances. These<br />

<strong>networks</strong> then proved useful in commercial and industrial fields, first aid operations and exploration missions. Ad<br />

<strong>hoc</strong> <strong>networks</strong>, also called peer-to-peer <strong>networks</strong>, still have a long way to go in order to be fully functional and<br />

commercial, as it has its defects such as security and routing which we will discuss further.


<strong>Routing</strong> Protocols<br />

<strong>Routing</strong> <strong>protocols</strong> between any pair of nodes within an <strong>ad</strong> <strong>hoc</strong> network can be difficult because the nodes can move<br />

randomly and can also join or leave the network. This means that an optimal route at a certain time may not work<br />

seconds later. Discussed below are three categories that existing <strong>ad</strong>-<strong>hoc</strong> network routing <strong>protocols</strong> fall into:<br />

1. Table Driven Protocols<br />

2. On Demand Protocols<br />

3. Hybrid Protocols<br />

Ad-<strong>hoc</strong> Mobile <strong>Routing</strong> Protocols<br />

Diagram 1<br />

1. Table Driven <strong>Routing</strong> Protocols, also known as Proactive Protocols, work out routes in the background<br />

independent of traffic demands. Each node uses routing in<strong>for</strong>mation to store the location in<strong>for</strong>mation of other<br />

nodes in the network and this in<strong>for</strong>mation is then used to move data among different nodes in the network. This<br />

type of protocol is slow to converge and may be prone to routing loops. These <strong>protocols</strong> keep a constant overview of<br />

the network and this can be a dis<strong>ad</strong>vantage as they may react to change in the network topology even if no traffic is<br />

affected by the topology modification which could create unnecessary overhe<strong>ad</strong>. Even in a network with little data<br />

traffic, Table Driven Protocols will use limited resources such as power and link bandwidth there<strong>for</strong>e they might not<br />

be considered an effective routing solution <strong>for</strong> Ad-<strong>hoc</strong> <strong>Networks</strong>. Fisheye State <strong>Routing</strong> is an example of a Table<br />

Driven Protocol.<br />

2. On Demand <strong>Routing</strong> Protocols, also known as Reactive Protocols, establish routes between nodes only when<br />

they are required to route data packets. There is no updating of every possible route in the network inste<strong>ad</strong> it<br />

focuses on routes that are being used or being set up. When a route is required by a source node to a destination <strong>for</strong><br />

which it does not have route in<strong>for</strong>mation, it starts a route discovery process which goes from one node to the other<br />

until it arrives at the destination or a node in-between has a route to the destination. On Demand <strong>protocols</strong> are<br />

generally considered efficient when the route discovery is less frequent than the data transfer because the network


traffic caused by the route discovery step is low compared to the total communication bandwidth. This makes On<br />

Demand Protocols more suited to large <strong>networks</strong> with light traffic and low mobility. An example of an On Demand<br />

Protocol is Dynamic Source <strong>Routing</strong>.<br />

3. Hybrid <strong>Routing</strong> Protocols combine Table Based <strong>Routing</strong> Protocols with On Demand <strong>Routing</strong> Protocols. They<br />

use distance-vectors <strong>for</strong> more precise metrics to establish the best paths to destination <strong>networks</strong>, and report routing<br />

in<strong>for</strong>mation only when there is a change in the topology of the network. Each node in the network has its own<br />

routing zone, the size of which is defined by a zone r<strong>ad</strong>ius, which is defined by a metric such as the number of hops.<br />

Each node keeps a record of routing in<strong>for</strong>mation <strong>for</strong> its own zone. Zone <strong>Routing</strong> Protocol (ZRP) is an example of a<br />

Hybrid routing protocol.<br />

Security<br />

Ad-<strong>hoc</strong> <strong>networks</strong> are highly vulnerable to security attacks and dealing with this is one of the main challenges of<br />

developers of these <strong>networks</strong> today. The main reasons <strong>for</strong> this difficulty are;<br />

"Shared bro<strong>ad</strong>cast r<strong>ad</strong>io channel, insecure operating environment, lack of central authority, lack of association<br />

among nodes, limited availability of resources, and physical vulnerability."<br />

Generally, when considering the security of a network, we examine it under the he<strong>ad</strong>ings; availability,<br />

confidentiality, authentication, integrity and non-repudiation. Availability refers to the fact that the network must<br />

remain operational at all times despite denial of service attacks. Confidentiality ensures that certain in<strong>for</strong>mation is<br />

never disclosed to certain users. Authentication is the ability of a node to identify the node with which it is<br />

communicating. Integrity guarantees that a message is never corrupted when transferred. Non-repudiation states<br />

that the sender of the message cannot deny having sent it. An <strong>ad</strong>-<strong>hoc</strong> network has extra security requirements<br />

caused by its lack of proper infrastructure and the dynamic relationship between the nodes in the network. Because<br />

of the lack of infrastructure, accountability is very difficult to determine as there is "no central authority which can<br />

be referenced when it comes to making trust decisions about other parties in the network."<br />

The dynamic relationship between the nodes leaves very little opportunity <strong>for</strong> the nodes to <strong>for</strong>m trust<br />

relationships with each other. In an <strong>ad</strong>-<strong>hoc</strong> network, nodes must act as both terminals and routers <strong>for</strong> other<br />

nodes. Because there are no dedicated nodes, a secure routing protocol is needed. Multi hop routing <strong>protocols</strong> are<br />

usually employed. These can le<strong>ad</strong> to problems due to non-cooperating nodes and denial of service attacks.<br />

Denial of Service Attacks


Diagram 2<br />

These problems are not easily solved and routing <strong>protocols</strong> <strong>for</strong> <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong> are still under active research.<br />

Confidentiality is also a major issue in <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong> but it is one that can be solved more easily. Cryptography is<br />

one of the most common and reliable means to ensure confidentiality.<br />

"It is the study of the principles, techniques, and algorithms by which in<strong>for</strong>mation is trans<strong>for</strong>med into a disguised<br />

version which no unauthorized person can re<strong>ad</strong>, but which can be recovered in its original <strong>for</strong>m by an intended<br />

recipient."<br />

Another issue to be considered is protecting the in<strong>for</strong>mation that is actually stored on the device as the more<br />

portable the device, the easier it is to tamper with in general. We must also attempt to retain confidentiality of<br />

identity and location which will become more important in the ubiquitous computing environment. Ad-<strong>hoc</strong> <strong>networks</strong><br />

require a high level of security, but because of the nature of these <strong>networks</strong>, this can often be difficult to<br />

provide. There<strong>for</strong>e, it is an issue which requires a lot more research if these <strong>networks</strong> are to continue to thrive.<br />

The future of <strong>ad</strong> <strong>hoc</strong> <strong>networks</strong><br />

Mobile <strong>ad</strong> <strong>hoc</strong> <strong>networks</strong> are the future of wireless <strong>networks</strong>. Why? Because they're practical, versatile, simple, easy<br />

to use and inexpensive! We will be living in a world where our network instantly updates and reconfigures itself to<br />

keep us connected anywhere we go.<br />

These <strong>networks</strong> provide a new approach <strong>for</strong> wireless communication and by operating in a license free frequency<br />

band prove to be relatively inexpensive.<br />

With the current trend of society's demand <strong>for</strong> in<strong>for</strong>mation at out fingertips, we will see our future living<br />

environments requiring communication <strong>networks</strong> between the many devices we use in day to day living, allowing<br />

them to talk to each other.


For example devices like personal digital assistants and <strong>mobile</strong> phones being able to receive instant messages from a<br />

home device. Such as a refrigerator sending a message to a PDA to update its shopping list; notifying that it's run out<br />

of milk. Or washing machines and ovens sending a report to say the clothes are finished or the chicken's cooked.<br />

Likewise, in education <strong>ad</strong> <strong>hoc</strong> <strong>networks</strong> may be deployed <strong>for</strong> student laptops interacting with the lecturer during<br />

classes.<br />

Also wireless public access <strong>for</strong> dense urban areas (Nokia RoofTopT): A wireless bro<strong>ad</strong>band solution <strong>for</strong> residential<br />

markets, based on a multi-hop Ad-Hoc (mesh) networking.<br />

Or similarly, <strong>ad</strong> <strong>hoc</strong> <strong>networks</strong> <strong>for</strong> cars, sending instant traffic reports and other in<strong>for</strong>mation. Sensors and robots<br />

<strong>for</strong>ming multimedia network that allows remote visualization and control, multiple airborne routers (from tiny<br />

robots to blimps) automatically providing connectivity and capacity where needed (e.g., at a football game); an <strong>ad</strong><br />

<strong>hoc</strong> network of spacecrafts around and in transit between the Earth and Mars.<br />

Science fiction? Only time will tell.<br />

Conclusion<br />

Nokia RoofTopT Wireless <strong>Routing</strong><br />

Diagram 3<br />

After researching Ad-<strong>hoc</strong> <strong>networks</strong> in depth, we believe that they will be the future of wireless networking. It is true<br />

that per<strong>for</strong>mance suffers as the number of devices grows and large <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong> become difficult to route and<br />

manage. However, much time is being devoted to achieving routing stability, and a few technical issues need to be<br />

solved be<strong>for</strong>e they become common place. The area of <strong>ad</strong> <strong>hoc</strong> <strong>networks</strong> is a very fast growing area, and due to the<br />

vast research in them, we are seeing these problems disappear and they are coming into a world of their own.


List of <strong>ad</strong> <strong>hoc</strong> routing <strong>protocols</strong><br />

An <strong>ad</strong>-<strong>hoc</strong> routing protocol is a convention, or standard, that controls how nodes decide which way<br />

to route packets between computing devices in a <strong>mobile</strong> <strong>ad</strong> <strong>hoc</strong> network .<br />

In <strong>ad</strong>-<strong>hoc</strong> <strong>networks</strong>, nodes are not familiar with the topology of their <strong>networks</strong>. Inste<strong>ad</strong>, they have to discover it. The<br />

basic idea is that a new node may announce its presence and should listen <strong>for</strong> announcements bro<strong>ad</strong>cast by its<br />

neighbours. Each node learns about nodes nearby and how to reach them, and may announce that it, too, can reach<br />

them.<br />

Note that in a wider sense, <strong>ad</strong> <strong>hoc</strong> protocol can also be used literally, that is, to mean an improvised and often<br />

impromptu protocol established <strong>for</strong> a specific purpose.<br />

The following is a list of some <strong>ad</strong> <strong>hoc</strong> network routing <strong>protocols</strong>.<br />

1 Pro-active (table-driven) routing<br />

2 Reactive (on-demand) routing<br />

3 Flow-oriented routing<br />

4 Hybrid (both pro-active and reactive) routing<br />

5 Hierarchical routing <strong>protocols</strong><br />

6 Backpressure <strong>Routing</strong><br />

7 Host Specific <strong>Routing</strong> <strong>protocols</strong><br />

8 Power-aware routing <strong>protocols</strong><br />

9 Multicast routing<br />

10 Geographical multicast <strong>protocols</strong> (Geocasting)<br />

11 On-Demand Data Delivery routing<br />

Pro-active (table-driven) routing<br />

This type of <strong>protocols</strong> maintains fresh lists of destinations and their routes by periodically distributing routing tables<br />

throughout the network. The main dis<strong>ad</strong>vantages of such algorithms are:<br />

1. Respective amount of data <strong>for</strong> maintenance.<br />

2. Slow reaction on restructuring and failures.


Examples of pro-active algorithms are:<br />

Babel, a protocol inspired by DSDV with faster convergence and ETX link quality estimation. Free<br />

implementation available.<br />

B.A.T.M.A.N. – Better approach to <strong>mobile</strong> <strong>ad</strong><strong>hoc</strong> networking.<br />

DSDV (Highly Dynamic Destination-Sequenced Distance Vector routing protocol)<br />

HSR (Hierarchical State <strong>Routing</strong> protocol)<br />

HSLS The hazy-sighted link-state algorithm.<br />

This algorithm is based on empirical and theoretical studies to limit link-state traffic while achieving practical<br />

link mobility. It avoids the message flooding of DSR, OLSR and AODV by growing the range of the link-state<br />

updates twofold <strong>for</strong> each twofold expansion of time. It has a practical large network in place at CuWIN.<br />

IARP (Intrazone <strong>Routing</strong> Protocol/pro-active part of the ZRP)<br />

Linked Cluster Architecture | LCA (Linked Cluster Architecture)<br />

WAR (Witness Aided <strong>Routing</strong>)<br />

OLSR Optimized Link State <strong>Routing</strong> Protocol<br />

Reactive (on-demand) routing<br />

This type of <strong>protocols</strong> finds a route on demand by flooding the network with Route Request packets. The main<br />

dis<strong>ad</strong>vantages of such algorithms are:<br />

1. High latency time in route finding.<br />

2. Excessive flooding can le<strong>ad</strong> to network clogging.<br />

Examples of reactive algorithms are:<br />

SENCAST –A Scalable Protocol <strong>for</strong> Unicasting and Multicasting in a Large Ad <strong>hoc</strong> Emergency Network,<br />

International Journal of <strong>Computer</strong> Science and Network Security.<br />

Reliable Ad <strong>hoc</strong> On-demand Distance Vector <strong>Routing</strong> Protocol<br />

Ant-based <strong>Routing</strong> Algorithm <strong>for</strong> Mobile Ad Hoc <strong>Networks</strong> – ARA – the ant-colony based routing algorithm<br />

<strong>for</strong> manets,<br />

Admission Control enabled On demand <strong>Routing</strong> (ACOR) –<br />

Ari<strong>ad</strong>ne – A Secure On-Demand <strong>Routing</strong> Protocol <strong>for</strong> Ad Hoc <strong>Networks</strong><br />

Associativity-Based <strong>Routing</strong> – A Novel Distributed <strong>Routing</strong> Protocol To Support Ad <strong>hoc</strong> Mobile Computing<br />

Ad <strong>hoc</strong> On-demand Distance Vector(AODV)<br />

Ad <strong>hoc</strong> On-demand <strong>Routing</strong> Protocol (AORP)<br />

Ad <strong>hoc</strong> On-demand Multipath Distance Vector<br />

Backup Source <strong>Routing</strong><br />

Dynamic Source <strong>Routing</strong><br />

Flow State in the Dynamic Source <strong>Routing</strong><br />

Dynamic NIx-Vector <strong>Routing</strong><br />

Dynamic Manet On-demand <strong>Routing</strong><br />

Endaira: It is on demand source routing protocol and it is designed to <strong>ad</strong>dress the hidden channel attack in<br />

ari<strong>ad</strong>ne.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!