05.01.2013 Views

Ad Hoc Networks : Technologies and Protocols - University of ...

Ad Hoc Networks : Technologies and Protocols - University of ...

Ad Hoc Networks : Technologies and Protocols - University of ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

96 Multicasting in <strong>Ad</strong> <strong>Hoc</strong> <strong>Networks</strong><br />

Approach 3: Reliance on No Nodes Since all nodes are mobile, the multicast<br />

routes would need maintenance as time goes by. If session states are stored in<br />

packet headers, the protocol does not have to rely on any specific nodes to form<br />

a forwarding path because we do not even need one! Session states carried in<br />

packet header may be a list <strong>of</strong> node IDs, or a series <strong>of</strong> location coordinates. In<br />

a protocol using this approach, intermediate nodes check the packet header <strong>and</strong><br />

decide where or who to forward the packet.<br />

Examples for this approaches include location guided small group communication<br />

[8] <strong>and</strong> DDM [9].<br />

Approach 4: Reliance on Stabler Nodes This approach attempts to take<br />

advantage <strong>of</strong> node mobility <strong>and</strong> network architecture. If nodes in a network<br />

have different degrees <strong>of</strong> mobility, for example, fast <strong>and</strong> slow, we can rely on the<br />

slow (thus stabler) nodes in order to build the multicast route. Note that “fast”<br />

<strong>and</strong> “slow” could be in the relative sense. For example, a group <strong>of</strong> nodes may<br />

move fast together toward a common direction, but the relative speed among<br />

group member is “slow”.<br />

An example <strong>of</strong> this approach is M-LANMAR [10], which is a multicast<br />

protocol exploiting team-based mobility.<br />

Approach 5: Reliance on an Overlay Layer Since all nodes are mobile,<br />

adapting to network dynamics is an extra burden for multicasting protocols. By<br />

inserting a middle layer in between, we can hide dynamics in lower layer <strong>and</strong><br />

let multicast protocols concentrate only on multicasting. In this approach, the<br />

protocols normally build an overlay mesh on top <strong>of</strong> the physical network, <strong>and</strong><br />

the multicasting route is built on top <strong>of</strong> this overlay mesh. Without knowing<br />

the underlying dynamics, it is easier for the multicast protocol to focus on<br />

implementing multicast functionalities.<br />

<strong>Protocols</strong> using this approach includes AMRoute [11] <strong>and</strong> PAST-DM [12],<br />

both <strong>of</strong> which construct a virtual mesh structure on top <strong>of</strong> the physical network.<br />

The virtual mesh relies on some unicast routing protocols to provide tunneling<br />

route between any two nodes on mesh. Data forwarding tree is extracted on top<br />

<strong>of</strong> the virtual mesh, <strong>and</strong> is unaware <strong>of</strong> underlying topology changes.<br />

Several popular multicasting protocols are classified according to our discussion<br />

<strong>and</strong> are summarized in Table 4.1.<br />

4.3 Multicasting <strong>Protocols</strong><br />

In the previous sections, we reviewed the special properties <strong>of</strong> mobile ad<br />

hoc networks, <strong>and</strong> examined how these properties affect the design <strong>and</strong> implementation<br />

<strong>of</strong> network protocols. To deliver packets effectively to the multicast<br />

group members, any multicasting protocol should address these properties. In

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

Saved successfully!

Ooh no, something went wrong!