Ad Hoc Networks : Technologies and Protocols - University of ...
Ad Hoc Networks : Technologies and Protocols - University of ...
Ad Hoc Networks : Technologies and Protocols - University of ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Transport Layer for <strong>Ad</strong>-hoc <strong>Networks</strong>: Overview 135<br />
link failure. This also contributes to the delay after which a source realizes that<br />
a path is broken, consequently increasing the probability <strong>of</strong> timeouts. Figure<br />
5.4(b) shows the latency involved in the MAC layer detecting a link failure. It<br />
can be observed that for higher loads, the latency could be in the order <strong>of</strong> a few<br />
seconds.<br />
Both <strong>of</strong> the above factors directly contribute to more number <strong>of</strong> losses occuring<br />
in the network, <strong>and</strong> thus impact the throughput performance <strong>of</strong> network<br />
connections.<br />
Impact <strong>of</strong> Routing Layer. The characteristics <strong>of</strong> the underlying routing<br />
protocol have a significant impact on TCP’s performance. Some <strong>of</strong> the important<br />
ones are outlined below.<br />
In most <strong>of</strong> the reactive routing protocols (such as DSR), there is a provision<br />
for the routing layer at the upstream node <strong>of</strong> a broken link to send back a path<br />
failure message to the source. Once the source is informed <strong>of</strong> the path failure, it<br />
initiates a new route computation. Any packet originating at the source during<br />
this route-recomputation phase does not have a route. This directly increases<br />
the fraction <strong>of</strong> time that packets in the routing layer spend without a route to the<br />
destination during a connection’s lifetime. Further, the time taken to recompute<br />
the new route also increases with increasing load. This can be observed in Figure<br />
5.4(c) where the latency involved in route computation is presented.<br />
In addition to the absolute impact <strong>of</strong> not having a route in the route computation<br />
phase, TCP is also likely to experience timeouts during each route<br />
computation time, especially in the heavy load scenario where route computation<br />
time is around a couple <strong>of</strong> seconds. Furthermore, successive timeouts<br />
<strong>and</strong> the resulting back-<strong>of</strong>fs could potentially result in the stalling <strong>of</strong> the data<br />
connection.<br />
Finally, it is in the best interest <strong>of</strong> the connection to minimize the number <strong>of</strong><br />
route failures resulting from the routing protocol’s operation. This is because,<br />
the number <strong>of</strong> route failures directly influence the above two factors. As the<br />
number <strong>of</strong> route errors increases, the fraction <strong>of</strong> time a packet spends without a<br />
route at the routing layer increases, consequently increasing the probability <strong>of</strong><br />
the expiry <strong>of</strong> TCP’s retransmission timer.<br />
5.3 Transport Layer for <strong>Ad</strong>-hoc <strong>Networks</strong>: Overview<br />
Existing approaches to improve transport layer performance over ad-hoc<br />
networks fall under three broad categories: (i) Modifying TCP to h<strong>and</strong>le the<br />
characteristics <strong>of</strong> an ad-hoc network, (ii) Cross-layer TCP aware modifications<br />
to the lower layers <strong>of</strong> the protocol stack to hide from TCP the vagaries <strong>of</strong> an<br />
ad-hoc network, (iii) Built-from-scratch transport protocols that involve a fully<br />
re-designed transport layer approach suited for ad-hoc networks. In the rest <strong>of</strong>