19.11.2012 Views

MASTER THESIS REPORT MSc IN ELECTRICAL ENGINEERING ...

MASTER THESIS REPORT MSc IN ELECTRICAL ENGINEERING ...

MASTER THESIS REPORT MSc IN ELECTRICAL ENGINEERING ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

MEE 09: 17<br />

<strong>MASTER</strong> <strong>THESIS</strong> <strong>REPORT</strong><br />

<strong>MSc</strong> <strong>IN</strong> <strong>ELECTRICAL</strong> ENG<strong>IN</strong>EER<strong>IN</strong>G<br />

WITH EMPHASIS ON TELECOMMUNICATION<br />

TRASMISSION CONTROL PROTOCOL (TCP)<br />

PERFORMANCE EVALUATION <strong>IN</strong> MANET<br />

Author:<br />

Muhammad Ijaz<br />

m_ijazf@yahoo.com<br />

Supervisor & Examiner:<br />

Adrian Popescu<br />

adrian.popescu@bth.se<br />

BLEK<strong>IN</strong>GE <strong>IN</strong>STITUTE OF TECHNOLOGY<br />

MARCH 2009<br />

1


ACKNOWLEDGEMENT<br />

In the name of greatest All mighty ALLAH who has always bless me with potential<br />

knowledge and success.<br />

I am thankful to my supervisor Adrain Popescu, my friends who help me during my hard<br />

times when I need their assistance during simulation.<br />

I am especially thankful to my Parents, Uncles and Grandmother, who had always provided<br />

me the courage, strength, best wishes, moral and financial support during my whole career.<br />

I also have best regards for BTH faculty including Mikeal Åsman and Lena Magnusson who<br />

had been helpful throughout my maters degree.<br />

2


Abstract<br />

Mobile Ad hoc network routing protocols have been divided in several different categories<br />

such as Reactive and Proactive Routing Protocol. The performances of these categories are<br />

evaluated in different scenario with TCP variants. We present a comprehensive TCP<br />

performance evaluation study to understand the nature of the TCP performance in different<br />

scenarios with variable amount of payload and number of nodes. The traffic consists of three<br />

different packet sizes i.e. 512, 1000, 1500 bytes each. Three different routing protocols<br />

(AODV, DSR and TORA) are to be evaluated with three different TCP variants (Tahoe, Reno<br />

and New Reno) in three different scenarios having 3, 5 and 8 nodes. The performances<br />

parameters on the basis of which routing protocols are to be graded are mainly throughput,<br />

congestion window and delay. Conclusions are drawn based on the simulation results and the<br />

comparisons between them have been elaborated.<br />

3


LIST OF OBSERVATIONS<br />

ABR Associativity -Based Routing<br />

ACK Acknowledgement<br />

ALP Adaptive Link-State Protocol<br />

AODV Ad hoc On Demand Distance Vector<br />

BER Bit Error Rate<br />

CLR Clear<br />

CWND Congestion Window<br />

DAG Directed Acyclic Graph<br />

DREAM Distance Routing Effect Algorithm for Mobility<br />

DSDV Destination Sequence Distance Vector<br />

DSN Distance Sequence numbers<br />

DSR Dynamic Source Routing<br />

FORP Flow Oriented Routing Protocol<br />

FSR Fisheye State Routing<br />

GLS Grid Location Service<br />

GPS Global Positioning System<br />

GPSR Greedy Perimeter Stateless Routing<br />

GSR Global State Routing<br />

IEEE Institute of Electronics and Electrical Engineers<br />

IP Internet Protocol<br />

LAN Local Area Network<br />

LANMAR Landmark Ad Hoc Routing<br />

LAR Location-Aided Routing<br />

LMR Lightweight Mobile Routing<br />

LRR Least Resistance Routing<br />

MANET Mobile Ad hoc Network<br />

MAC Medium Access Control<br />

MDSR Multipath Dynamic Source Routing<br />

MSS Maximum Segment Size<br />

OLSR Optimized Link State Routing<br />

OPNET Optimized Network Evaluation Tool<br />

PHY Physical Layer<br />

RABR Route-Lifetime Assessment Based Routing<br />

4


RERRs Route Errors<br />

RIP Routing Internet Protocol<br />

QRY Query<br />

RREQs Route Requests<br />

RREP Route Reply<br />

RTO Retransmission Time Out<br />

RDMAR Relative Distance Micro-discovery Ad Hoc Routing<br />

ROAM Routing On demand Acyclic Multipath<br />

RWND Advertize Window<br />

SSA Signal Stability-Based Adaptive<br />

STAR Source Tree Adaptive Routing<br />

SWND Send Window<br />

TCP Transmission Control Protocol<br />

TORA Temporally Ordered Routing Algorithm<br />

TTL Time-To-Live<br />

UDP User Datagram Protocol<br />

WRP Wireless Routing Protocol<br />

ZHLS Zone-Based Hierarchical Link State<br />

5


LIST OF FIGURES<br />

FIGURE DESCRIPTION PAGE<br />

Figure 2.1 Slow Start and Congestion Avoidance Mechanism 15<br />

Figure 2.2 Hidden and Exposed Node Terminal Problem 18<br />

Figure 3.1 Route discovery for target node 23<br />

Figure 3.2 Maintenance for Error Route 24<br />

Figure 3.3 Route Discoveries in TORA – QRY Message 26<br />

Figure 3.4 Route Discoveries in TORA – Update Message 26<br />

Figure 4.1 Research Methodology 30<br />

Figure 5.1 Simulation Model 32<br />

Figure 5.2 MANET eight node scenarios 33<br />

Figure 5.3 Simulation Flow 34<br />

Figure 5.4 Throughput comparison in three nodes scenario 36<br />

Figure 5.5 Throughput comparison in five nodes scenario 37<br />

Figure 5.6 Throughput comparison in eight nodes scenario 38<br />

Figure 5.7 Delay Comparisons in Different Scenario 39<br />

Figure 5.8 Congestion Window dynamics 40<br />

LIST OF TABLES<br />

TABLE DESCRIPTION PAGE<br />

Table 5.1 Detail of TCP Variants and Routing Protocol for Three Nodes 35<br />

Table 5.2 Detail of TCP Variants and Routing Protocol for Five<br />

Table 5.3 Detail of TCP Variants and Routing Protocol for Eight Nodes<br />

6<br />

36<br />

37


LIST OF CONTENTS<br />

CHAPTER 1 Introduction 9<br />

1.1 Background 11<br />

1.2 Aims/ Objectives 11<br />

1.3 Research Questions 11<br />

1.4 Thesis Structure 11<br />

1.5 Expected Contribution 11<br />

CHAPTER 2 TCP and Ad hoc Networks 12<br />

2.1 Types of Wireless Networks 13<br />

2.1.1 Infrastructure Networks 13<br />

2.1.2 Ad hoc Networks 13<br />

2.2 TCP working mechanism and Variants of TCP 14<br />

2.2.1 Working Mechanism of TCP 14<br />

2.2.2 Various Flavor of TCP 15<br />

2.2.2.1 Tahoe 15<br />

2.2.2.2 Reno 16<br />

2.2.2.3 New Reno 16<br />

2.3 Challenges and Limitation of TCP in Wireless Network 16<br />

2.3.1 Dynamic Topology/Mobility 16<br />

2.3.2 Multi Hopping 17<br />

2.3.3 Differentiating Transmission and Congestion Losses 17<br />

2.3.4 High Bit Errors 17<br />

2.3.5 Channel Contention 17<br />

2.3.6 Hidden and exposed terminal problem 18<br />

2.3.7 Out of Order Packet 19<br />

CHAPTER 3 Ad hoc Network Routing Protocols 20<br />

3.1 Proactive routing protocols 22<br />

3.2 Reactive routing protocols 22<br />

3.2.1 Dynamic Source Routing (DSR) 23<br />

3.2.2 Ad hoc on Demand Distance Vector (AODV) 24<br />

3.2.3 Temporarily Order Routing Algorithm (TORA) 25<br />

CHAPTER 4 Research Methodology 28<br />

4.1 Research Methodology 29<br />

4.2 Author Approach 29<br />

4.3 Research Design 29<br />

4.3.1 Problem Selection / Identification 29<br />

4.3.2 Literature Review for TCP and MANET 29<br />

4.3.3 Building Simulation Environment 30<br />

4.3.4 Simulation Results 30<br />

4.4 Simulation Tools 30<br />

7


CHAPTER 5 Simulation and Empirical Study 31<br />

5.1 Simulation Environment 32<br />

5.1.1 Model 32<br />

5.1.2 OPNET 32<br />

5.1.3 Network Entities and Functions 32<br />

5.1.3.1 Application Definition 33<br />

5.1.3.2 Profile Configuration 33<br />

5.1.3.3 Mobility Configuration 33<br />

5.1.3.4 Server 33<br />

5.1.3.5 Mobile Nodes 33<br />

5.2 Simulation Configuration 33<br />

5.3 Simulation Flow 33<br />

5.4 Scenarios 34<br />

CHAPTER 6 Discussion/ Results 42<br />

6.1 Conclusions 43<br />

6.2 Future Work 43<br />

Appendix 44<br />

Reference 60<br />

8


Chapter 1<br />

<strong>IN</strong>TRODUCTION<br />

9


1.1 Background<br />

Internet evolution thrives with time and development in the diverse technology<br />

improvements. Communication devices and medium have significant impact on overall<br />

internet. Numerous networks mixtures are present at the internet and even within these<br />

networks different preposition and parametric approaches for implementations are deployed<br />

subject organization needs. Overall internet traffic is somehow dependent upon underlying<br />

networks and vice versa. To cope with multiple simultaneous data networks internet requires<br />

and efficient algorithmic techniques to support data transmission successfully. Transmission<br />

Control Protocol/Internet Protocol (TCP/IP) has been very effective in data transmission<br />

delivery and have also developed variants to possess the possibility to increase performance<br />

and multiple packet loss recovery. An important aspect form [1] defines the data flow method<br />

that applications are responsible for the selection of the protocols and IP plays a central role<br />

all TCP and user datagram protocol (UDP) for data transmission.<br />

TCP is reliable and connection oriented protocol developed in 1981. It’s based on simple<br />

sliding window flow control, during the early stages congestion collapses occurred because of<br />

lack of congestion control mechanism. With the advent of Jacobson congestion algorithms for<br />

TCP as a remedy, TCP is updated to its new version known as TCP Tahoe. Now currently<br />

TCP Reno is widely used in Internet. TCP Tahoe congestion Control includes slow start,<br />

congestion avoidance and fast retransmission. While in addition to these three algorithms,<br />

TCP Reno also adds the fast recovery algorithm. TCP is design for wired network, but with<br />

the technology emerging towards wireless medium, the need to implement TCP is of great<br />

important but it faces many problems especially in an ad hoc networks. Mobile ad hoc<br />

network (MANET) is a famous ad hoc network can be utilized well for emergency situation<br />

and military applications. TCP has poor performance in MANTE due to dynamic topology,<br />

shared medium, high error ratio; channel connotation and multi hop architecture.<br />

As an evident, ad hoc networks are growing dynamically and its true development fact lies in<br />

the problems associated with the seamless internet access and connectivity. With evolution in<br />

the hardware devices and software that offers wireless access to the internet by means of an<br />

intermediate connection through access point ad hoc tends to improve and increase gradually.<br />

Mobile ad hoc network is sub field with enormous commercial, industrial and military growth<br />

and realistic practical approach for internet access. Most important things to know about the<br />

technology is the ability of autonomously establishing and managing the network [2] while<br />

the an effective military consensus applications, data exchange based on mobility networks<br />

for commercial purpose i.e. business organization or it could be better utilized during<br />

emergency within and out of remote areas. This IP based dynamic wireless networks works<br />

effectively, reliable and robust data transmissions.<br />

Problems are associated with in the MANET performance, an evaluation and optimization<br />

techniques are necessary to opt and adhere for the better execution of the transmission<br />

medium. Pledged data delivery is TCP utmost drawback in wireless networks but possible<br />

solutions are available to recognize the data transmission effects. To measure the performance<br />

of different TCP variants, simulation study has been conducted in practice. MANET utilizes<br />

TCP and UDP for data transmission and our study focus on different variants of the TCP i.e.<br />

particularly Tahoe, Reno and New Reno explicitly using AODV, DSR and TORA protocols<br />

in focus.<br />

10


1.2 Aims/ Objectives<br />

Thesis aims to understand the performance of the TCP variants in MANET and its behavior<br />

with respect to different protocols. It focuses following issues in the thesis:<br />

Detail literature study for “state of the art” technology in TCP and MANET.<br />

Performance comparison in delay and throughput by increasing number of nodes.<br />

Performance comparison between the different protocols used in MANET through<br />

congestion window, delay and throughput.<br />

Suggest better protocol and TCP variant for MANET.<br />

1.3 Research Questions<br />

Q1: What are different TCP variants and its need?<br />

Q2: What are important routing protocols used in MANET?<br />

Q3: What is the impact on TCP performance during different protocol selection/<br />

implementation in MANET?<br />

Q4: Which factors influence the TCP performance and why?<br />

1.4 Thesis Structure<br />

Chapter 2 defines wireless networks and an extension to ad hoc networks and its working, it<br />

also include the detail study about the TCP flavors and its limitations.<br />

Chapter 3 is associated with the study of MANET routing protocols specific to ad hoc<br />

networks, their types, working and algorithms.<br />

Chapter 4 depicts the overall project flow explicitly starting form problem definition and<br />

following it towards solution, implementation, simulation and results hierarchy.<br />

Chapter 5 contains simulation environment description, list of figures and assumptions.<br />

Chapter 6 holds the brief discussion about the simulation results and future work.<br />

1.5 Expected Contribution<br />

The thesis will address the scientific society about the TCP and MANET implementations in<br />

reality. It will contribute through using multiple different numbers of nodes to describe the<br />

behavior of the TCP performance over different variants; it should reveal the idea to<br />

developing commercial and non commercial business project for MANET deployments and<br />

the results in reality should have utmost significance.<br />

11


Chapter 2<br />

TCP AND AD HOC<br />

NETWORKS<br />

12


In this chapter first to discuss the taxonomy of wireless networks such is infrastructure<br />

networks and ad hoc networks or infrastructure-less networks. Then before to discuss the<br />

different challenges transmission control protocol (TCP) is facing in wireless networks, it is<br />

better to give a look to the TCP working mechanism and its different variants.<br />

2.1. Types of Wireless Networks<br />

One of the unique features of wireless networks is compare to wire network is that data is<br />

transmitted from one point to another through wireless links i.e. there is no need of wired link<br />

between the two nodes for transmission. They just need to be in the transmission range of<br />

each other. Wireless networks or divided into two categories. Infrastructure wireless network<br />

and infrastructure less or ad hoc wireless network.<br />

2.1.1. Infrastructure Networks<br />

Infrastructure network have fixed network topology. Wireless nodes connect through the<br />

fixed point known as base station or access point. In most cases the access point or base<br />

station or connected to the main network through wired link. The base station, or access point,<br />

is one of the important elements in such types of networks. All of the wireless connections<br />

must pass from the base station. Whenever a node is in the range of several base stations then<br />

it connect to any one of them on the bases of some criteria [3].<br />

2.1.2. Ad hoc Networks<br />

Ad hoc networks also called infrastructure less networks are complex distributed systems<br />

consist of wireless links between the nodes and each node also works as a router to forwards<br />

the data on behalf of other nodes. The nodes are free to join or left the network without any<br />

restriction. Thus the networks have no permanent infrastructure. In ad hoc networks the nodes<br />

can be stationary or mobile. Therefore one can say that ad hoc networks basically have two<br />

forms, one is static ad hoc networks (SANET) and the other one is called mobile ad hoc<br />

networks (MANET). From the introduction of new technologies such as IEEE 802.11[4] the<br />

commercial implementation of ad hoc network becomes possible [5].<br />

One of the good features of such networks is the flexibility and can be deployed very easily.<br />

Thus it is suitable for the emergency situation. But on the other side it is also very difficult to<br />

handle the operation of ad hoc networks. Each node is responsible to handle its operation<br />

13


independently. Topology changes are very frequent and thus there will be need of an efficient<br />

routing protocol, whose construction is a complex task. TCP performances are also very poor<br />

in mobile ad hoc network. In coming sections we are discussing the TCP working mechanism<br />

and challenges for TCP in ad hoc networks in more detail.<br />

2.2 TCP working mechanism and Variants of TCP<br />

Transmission Control Protocol (TCP) [6] is a Transport Layer Protocol and originally<br />

designed for wired network in 1981. The basic responsibility of TCP is to provide reliable<br />

transfer of data between the nodes i.e. to ensure that the data is reached the destination<br />

correctly without any loss or damage. The data is transmitted in the form of continuous stream<br />

of octets. The mechanism is adopted to assign a sequence number to each octet of data and<br />

receiver respond with positive acknowledgement to ensure that the data is received correctly.<br />

Another aspect of TCP is the tree way handshakes mechanism to establish a connection<br />

between the end points (nodes). In case if there are two or more TCP connection between the<br />

end points for this TCP uses the port assignment mechanism to differentiate each connection<br />

from others.<br />

2.2.1 Working Mechanism of TCP<br />

The congestion control algorithm employed by TCP is window based. It uses three types of<br />

windows called congestion window (cwnd), advertize window (rwnd) and send window<br />

(swnd). Congestion windows shows the total amount of data the sender is allowed to output to<br />

the network without any Acknowledgement (ACK). While on the other hand the advertise<br />

window indicates the amount of data the receiver is ready to accept. It is equal to the available<br />

buffer size on the receiver. Now the size of the flight window or send window is set to the<br />

minimum of the congestion window and advertize window.<br />

Basically the congestion control mechanism has two phases the slow start and congestion<br />

avoidance phase. When a connection is established the initial size of congestion window is set<br />

to One MSS (Maximum Segment Size). Receiving data from the sender the receiver ACK the<br />

reception of data to the sender, the receiver is actually indicating the sequence number of next<br />

expected data segment in ACK, from this the sender conclude that all the data segments<br />

which have sequence number less than the indicated one are delivered correctly. While in case<br />

of packet loss, out-of-order packets arrive at the receiver. Then the receiver sends a duplicate<br />

14


ACK to the sender in response of each out-of-order packet arrival. When sender receives three<br />

duplicates ACK, it is concluded that the packet is lost and retransmission of data packet take<br />

place.<br />

Congestion Window<br />

24<br />

22<br />

20<br />

18<br />

16<br />

14<br />

12<br />

10<br />

8<br />

6<br />

4<br />

2<br />

0<br />

Slow Start threshold<br />

Slow Start<br />

Congestion Avoidance<br />

Phase<br />

Time out Occured<br />

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16<br />

Number of Acknowledgement<br />

Slow Start threshold<br />

Figure 2.1 Slow Start and Congestion Avoidance Mechanism [10]<br />

If sender receives non-duplicate ACK Then the congestion window is incremented. In slow<br />

start phase exponential incrimination occurs until it reaches to the slow start threshold. While<br />

in congestion avoidance phase the cwnd is incremented by one packet. This window growth is<br />

limited to a maximum window size. This whole process is depicted in Fig. 2.1.<br />

2.2.2. Various Flavor of TCP<br />

After the introduction of first version of TCP several different flavors exist, here we are<br />

discussing the most famous implementation of TCP called Tahoe, Reno, New Reno and<br />

Vegas.<br />

2.2.2.1. Tahoe<br />

In the first version of TCP there was no congestion control mechanism. So after observing the<br />

congestion collapses 1988 Jacobson introduced several Congestion Control algorithms [7] and<br />

this version is called TCP-Tahoe. The congestion control algorithms introduced in this version<br />

are:<br />

15


a) Slow start<br />

b) Congestion Avoidance<br />

c) Fast Retransmit<br />

2.2.2.2. Reno<br />

The fast retransmit phase was first introduced in TCP-Tahoe followed by Slow Start. But<br />

TCP-Reno [8] also added the algorithm of Fast Recovery, so that Fast Recovery dictates the<br />

sender to perform congestion avoidance directly after fast retransmission rather than<br />

immediately reducing the data flow using slow start mechanism.<br />

2.2.2.3. New Reno<br />

TCP Reno recovers only one lost packet during the recovery process. So TCP-New Reno [9]<br />

is just adding the capability to TCP Reno to deals with multiple packets losses to recovery in a<br />

single transmission window.<br />

2.3. Challenges and Limitation of TCP in Wireless Network<br />

As compare to wired network wireless network have some special characteristic such as<br />

Mobility, share medium and signal fading. All these factors are responsible to create different<br />

types of challenges that restrict the range, data rate and reliability of the wireless transmission.<br />

These challenges are as follow.<br />

2.3.1. Dynamic Topology/Mobility<br />

In contrast to wired network, in wireless ad hoc networks the devices are free to move<br />

which leads to frequent topology changes. Then two types of problem occurrence are<br />

possible [11].<br />

(a) Path loss<br />

(b) Network Partition<br />

Path loss leads to the path re-computation at sender side and during this phase there will<br />

be no transmission which ultimately causes throughput degradation. Another possibility<br />

during this phase is that if path re-computation take more time then may be retransmission<br />

time out (RTO) occurs. Thus there will be data retransmission, RTO is increased<br />

exponentially and TCP enter to slow start phase. This affect will be more serious in high<br />

16


mobility environment. In case of network partition the sender and receiver remains at<br />

different network and all the packets will be dropped. In such situation multiple<br />

consecutive transmission of the same segment are possible, while the receiver will be<br />

disconnected and it is called serial time out.<br />

2.3.2. Multi-hoping<br />

In Ad hoc Network Environment every node is also supporting the responsibility of router to<br />

forwards packets on behalf of other nodes. Thus longer flow, in since of hops, having longer<br />

round trip time and higher packet dropping probability and high fluctuating end-to-end<br />

throughput as compare to flow having small number of hops.<br />

2.3.3.Differentiating Transmission and Congestion Losses<br />

Since wireless network have open medium, signal passing through the medium they have to<br />

face different blockage such as building, due to these blockages the transmission signals are<br />

reflected, diffracted and scattered and thus causes packets loss. TCP assume that this loss is<br />

occurred due to congestion and it activate its congestion control and result in congestion<br />

window reduction, which leads to low throughput and low utilization of available bandwidth.<br />

So TCP has no such mechanism to differentiate between congestion losses and transmission<br />

losses.<br />

2.3.4 High Bit Errors<br />

In wired network the Bit Error Rate (BER) is ranging from 10 -6 to 10 -8 , while in wireless<br />

network this range is from 10 -3 to 10 -1 . Since due to high BER the packet losses are very<br />

frequent and TCP reaction to these losses reduces the congestion window. Thus leads to non-<br />

optimal performance [10].<br />

2.3.5 Channel Contention<br />

Another reason of TCP performance degradation is the channel contention due to increasing<br />

number of nodes. It can occur between different flows passing through the same vicinity or<br />

between different packets in the same flow. In IEEE802.11, when the number of try for<br />

channel access exceeds the predefined limit, then cause to drop the packets and the Medium<br />

Access Control (MAC) Protocol notifies (wrongly) the upper layer that the path is<br />

17


unavailable. In response the upper layer starts the route recovery procedure [12] and TCP stop<br />

its transmission and the throughput drop to zero during route recovery process.<br />

This channel contention also leads to unfairness problem. The unfairness also occurs between<br />

the nodes so that each node has or not the equal access to the medium as compare to other<br />

node. If there is no equal access to the medium for each node then the unfairness occurs<br />

between the flows passing from different nodes. This unfairness also happens among the<br />

flows passing from the same path.<br />

2.3.6 Hidden and exposed terminal problem<br />

Due to the share medium and multi hoping capability the nodes facing the hidden and exposed<br />

node problem. Fig: 2.2 representing the hidden and exposed terminal problem of IEEE<br />

802.11 standard. The circles show the transmission range of A and B, where C is in the<br />

transmission range of both A and B. Let A and B both want to transmit data to C, so there will<br />

be collision at C, because A and B do not know about the transmission of each other due to<br />

hidden node problem.<br />

Figure 2.2: Hidden and Exposed Node Terminal Problem<br />

Now let that there is a transmission between C and B, while at the same time A wants to<br />

transmit data to D, but when A senses the medium, it find that the medium is busy due to C<br />

transmission and thus A stops its transmission. Actually in this situation A transmission for D<br />

will not going to collide with C transmission, This problem exist in IEEE802.11 standard and<br />

known as exposed terminal problem.<br />

18


2.3.7 Out of Order Packet<br />

When a receiver receives out of order packets, the receiver transmits duplicate<br />

acknowledgement, after receiving three duplicate ACK the sender retransmit the packets and<br />

congestion control is activated. But the problem is that congestion control is activated<br />

wrongly most of the time, because out-of-order packet occurrence take place due to different<br />

reasons such as multipath routing protocol and rout failure and not only due to congestion.<br />

19


Chapter 3<br />

Ad hoc Network Routing<br />

Protocols<br />

20


In this chapter routing protocols are described. In general route means the way and protocol is<br />

the set of rules through which two or more devices (computers, mobile nodes) are<br />

communicating with each others. Routes are multi hop in ad hoc networks because the<br />

propagation range (250 meters in an open field) of wireless radio is limited. Nodes travel<br />

freely and randomly in the network and routes are often find connection or disconnection.<br />

Establishing strong routes, maintaining and reconstruction in time are the main task for<br />

routing protocols. All the above responsibilities are performed by the routing protocol, except<br />

generating excessive control message overhead. Data packets send efficiently must be utilized<br />

by control packets and be generated only when needed. Routing protocol efficiency in<br />

bandwidth and energy consumption could be made by reducing the control overhead. [13]<br />

In generally mobile ad hoc wireless networks routing protocols can be classified by their<br />

routing strategy.<br />

Pure distance vector algorithms (e.g., Distributed Bellman Ford, Routing Internet<br />

Protocol (RIP), etc.) do not give a good result in mobile networks because of some<br />

limitation. Then some new protocols were proposed to modify and enhance the<br />

distance vector algorithm. Protocols such as Wireless Routing Protocol (WRP), Least<br />

Resistance Routing (LRR), Destination Sequence Distance Vector (DSDV) routing<br />

protocol, and the protocol by Lin and Liu.<br />

The protocols which are based on link state algorithms. Theses protocols include<br />

Global State Routing (GSR), Landmark Ad Hoc Routing (LANMAR) protocol,<br />

Optimized Link State Routing (OLSR) protocol, Adaptive Link-State Protocol (ALP),<br />

Fisheye State Routing (FSR) protocol, and Source Tree Adaptive Routing (STAR)<br />

protocol.<br />

The third one is on-demand routing protocols which are planned only for ad hoc<br />

network. Route to every destination of the networks on a regular basis is not<br />

maintained by on-demand routing protocols. The source establishes routes on demand.<br />

The source floods a route request packet to construct a route when it needed. The<br />

destination use route selection algorithm and select the best route for which<br />

destination receives request. Then route reply packet is sent to the source through new<br />

best route. There is no requirements of periodic exchange of route tables and control<br />

traffic overhead is greatly reduce by on-demand routing protocols. Several protocols<br />

of this type have been propose d. Ad-Hoc On Demand Distance Vector (AODV)<br />

21


outing, Dynamic Source Routing (DSR), Lightweight Mobile Routing (LMR),<br />

Temporarily Ordered Routing Algorithm (TORA), Route-Lifetime Assessment Based<br />

Routing (RABR), Associativity-Based Routing (ABR), Relative Distance Micro-<br />

discovery Ad Hoc Routing (RDMAR) protocol, Signal Stability-Based Adaptive<br />

(SSA) routing, Multipath Dynamic Source Routing (MDSR), and Routing On<br />

demand Acyclic Multipath (ROAM) algorithm are on demand routing protocol.<br />

The fourth category is GPS (Global Positioning System), in the early stages protocols<br />

was using node location information while building routes have been proposed<br />

recently. Through information node position, routing can require more cost to<br />

exchange location information. GPS routing protocols are Greedy Perimeter Stateless<br />

Routing (GPSR), Distance Routing Effect Algorithm for Mobility (DREAM), Grid<br />

Location Service (GLS), Location-Aided Routing (LAR), Flow Oriented Routing<br />

Protocol (FORP), and Zone-Based Hierarchical Link State (ZHLS).<br />

In addition we can say routing protocols are categorized as reactive, proactive and hybrid<br />

(combination of both is called hybrid). [13]<br />

3.1 Proactive Routing Protocols<br />

This type of protocols has to construct and maintain fresh routing information to all the nodes.<br />

This is free of whether or not the route is needed. For this achievement control message are<br />

transmitted periodically. Proactive routing protocols are not bandwidth well-organize. Even if<br />

there is no data flow, the control message is broadcasted. This type of protocols has some<br />

advantages and disadvantages. One of the main advantages is that nodes can get easily routing<br />

information and easy to set up a session. The disadvantage is:<br />

There is too much data kept by the nodes for route protection and restructure is slow when<br />

there is a failure in exacting link. DSDV is an example of proactive routing protocol.<br />

3.2 Reactive Routing Protocols<br />

Reactive routing protocols are specially planned for ad hoc networks. Permanent routing<br />

information is not kept by these protocols. Routes are built when the source needed. Route<br />

request is sending across the network to achieve this. In reactive routing protocols we describe<br />

in detail DSR (Dynamic Source Routing) protocol, AODV (Ad Hoc On-demand Distance<br />

Vector) protocol, and TORA (Temporally Ordered Routing Algorithm) protocol. [13]<br />

22


3.2.1 Dynamic Source Routing (DSR)<br />

DSR was developed at Carnegie Mellon University. It is simple and efficient reactive routing<br />

protocol which is specially designed for multi-hop ad hoc network of mobile nodes. The<br />

nodes in the network easily join or leave the network without any information. The network<br />

using DSR is not requiring existing network infrastructure or administration. The node<br />

desiring to transmit a packet define route for the packet because it is based on source routing.<br />

DSR works for ad-hoc network of approximately 200 nodes. Each node participating in ad-<br />

hoc network should forward packets and discard the erroneous packets (corrupted). DSR has<br />

two mechanisms: route discovery and route maintenance. [13]<br />

Route discovery<br />

The source starts a route discovery when sending data packet to the destination<br />

but have no routing information. To set up a route, the source floods RREQs<br />

message with a distinctive request ID. When the destination receives this<br />

request message or a node which has destination route information then it<br />

transmits RREP message back to the source with route information. Figure 3.1<br />

shows route discovery of DSR. Node 2 is the initiator and node 9 is the target.<br />

Figure 3.1: Route discovery for target node, [19]<br />

Route Maintenance<br />

In LAN routing the main improvement of DSR is in route maintenance and<br />

monitoring in the attendance of mobility. DSR based on the acknowledgments of<br />

data packets sent to adjacent nodes to monitors the validity of existing routes. This<br />

monitoring is achieved by inactively listening for communication of the adjacent to<br />

the next hop or sitting a bit in a packet to ask for open acknowledgment. The<br />

RERRs packet is sent to the creative sender to raise a new route discovery stage<br />

when a node fails to accept an acknowledgment. Nodes receive a REERs message<br />

remove any route entry (from their route cache) which uses the out of order link.<br />

23


When a node has problem transferring packet during that link then REER message<br />

is propagated. So this selective transmission reduces control overhead (if no packets<br />

pass through a link), it yields a long delay when a packet wants to go through a new<br />

link. [13]. Node 9 cannot be reached by node 6 anymore and a REER is returned to<br />

node 2.<br />

Figure 3.2: Maintenance for Error Route, [19]<br />

DSR main advantages are that it reduce routing overhead and does not need to discover routes<br />

to all the nodes in the network. The disadvantage of DSR is low mobility and static networks.<br />

Its performance is reduced by high mobility.<br />

3.2.2 Ad Hoc On-demand Distance Vector (AODV)<br />

The Ad hoc On-Demand Distance Vector (AODV) is a routing protocol. AODV is designed<br />

for ad hoc mobile networks and of both routing, that is unicast and multicast routing. AODV<br />

establish routes between different nodes as needed by source nodes. AODV maintain these<br />

routes as well as form trees which connect different multicast group members. The group<br />

members compose the trees and the members are connected by the nodes. In an ad hoc<br />

network when two nodes want to make a connection with each other, AODV enable multi-<br />

hop routes within the nodes. Ad hoc On-demand distance vector is free loop. DSN (Distance<br />

Sequence numbers) is used by the AODV to avoid counting to infinity, and this is one of the<br />

most important quality and feature of this algorithm. In a network the requested nodes send<br />

the DSN with other routing information from the source to the destination. It has also the<br />

feature to select optional route which is based on the sequence number. [14]<br />

There are three messages which are defined by AODV. These messages are Route Errors<br />

(RERRs), Route Request (RREQs) and Route Replies (RREPs). [15].<br />

24


For discovering and maintaining routes in the network these three messages are used, by using<br />

UDP packets from source to destination. A node uses its IP address as the source address in<br />

the IP header of a message when it request for a route, and for broadcast 255.255.255.255. In<br />

the ad hoc network the number of hops a particular routing message is determined by the TTL<br />

(Time-To-Live). The RREQ is broadcasted by the requested node when a route is needed to<br />

be created to the destination. When the next hop node received the message a new route is<br />

determined, or itself by the destination [16]. Routes of the PREQ from the originator to all the<br />

stations that receive message are cached in these stations. A RERR message is delivered or<br />

generated when there is a failure in the link. The message has all the important information<br />

about the node which is not reachable because of the failure. The IP address of the nodes is<br />

also mentioned in the message as the next hop for the destination.<br />

AODV is table based. All the information about the routes in the network is stored in this<br />

table. The routing table has the following entries i.e. DSN, flag, next hop, IP address, State,<br />

hop count, the list of precursors, Life time and network interface.<br />

3.2.3 Temporally Ordered Routing Algorithm (TORA)<br />

TORA is a reactive routing algorithm based on the conception of link reversal and used in<br />

MANETs to improve the scalability. Highly dynamic mobile ad hoc networks can be used by<br />

TORA. It is an adaptive routing protocol and used in multi-hop networks. It makes scaled<br />

routes between source and destination and Directed Acyclic Graph (DAG) is used to build in<br />

the destination node. A DAG is accomplished for the network by handing over each node i<br />

with a height metric i.e. hi. Directional from the link i to j means hi > hi . The height of the<br />

node in TORA is defined as quintuple, which contains the unique ID of the node, a<br />

propagation ordering parameter, the logical time of a link failure, a reflection indicator bit and<br />

a unique ID of the node which defines the new reference level. The first two values identify<br />

an offset with respect to the reference level and the last three values jointly represent the<br />

reference level. A data packet goes from up flow to down flow according the height<br />

difference between nodes. TORA has the capacity that many nodes can send packets to a<br />

given destination is provided by DAG. It also guarantees that all routes are loop free. There<br />

are three basic functions in TORA, [17 and 20].<br />

Route Creation<br />

Route maintenance<br />

25


Route erasure<br />

A route creation operation start all the nodes height is set to NULL i.e. (-,-,-,-,i) and<br />

destination is set to ZERO i.e. (0,0,0,0,dest). The nodes height is flexible according to the<br />

topology. A QRY message containing the destination’s ID is broadcasted by the source. A<br />

non-NULL height node responds with UPD packet containing its own height. With the<br />

reception of UPD packet, a node increment its height with one than that of the UPD generator.<br />

The higher height of a node is measured as up flow and lower height of a node is measured as<br />

down flow. Then the DAG from source to destination is constructed. Route maintenance<br />

operation is a main part of TORA. It has an exclusive quality that control message are<br />

contained into a small set of nods near the happening of topology changes. A node generates a<br />

new reference level and broadcasts the reference to its neighbours when it loses its last down<br />

flow link. Then the links reproduce the topology change and adjust to the new reference level.<br />

The route erasure operation in TORA floods CLR packets through the network and remove<br />

unacceptable routes, [18].<br />

Figure 3.3 Route Discoveries in TORA – QRY Message<br />

In this figure node A shows and node B shows destination. Node D and node G is one hop<br />

neighbours away from the destination. So they will propagate updates as shown in next figure.<br />

Figure 3.4 Route Discoveries in TORA – Update Message<br />

26


The algorithm [21], contains many flows with most severe in which algorithm extremely<br />

depend upon the numbers of nodes during initial stage, which causes dependence on the<br />

traffic requirement. It is measured as change in rate with regard to total number of nodes<br />

participating in network traffic. In case of gradually positive increase in the network volume,<br />

TORA is not considered as better solution.<br />

27


Chapter 4<br />

Research Methodology<br />

28


4.1 Research Methodology<br />

It illustrates the overall thesis work to be carried out in as in the form of research activity. It<br />

generalizes the understanding about author concept in developing multiple steps or stages for<br />

whole work.<br />

Creswell [22] enlighten two major form of research i.e. quantitative and qualitative.<br />

Quantitative research is carried out by means of inquiry strategies including certain<br />

experiments and simulations which produce some form of statistical data for analysis or<br />

decisions. Qualitative research is based on the researcher knowledge through participatory<br />

and /or constructive perspectives.<br />

4.2 Author approach<br />

Thesis is carried out through multiple stages starting form literature review about the state of<br />

art technology specific to TCP and MANET and then performing the simulation in OPNET<br />

v14.5 tool. So both molds of approaches are necessary to complete the thesis work and have<br />

been administered.<br />

4.3 Research Design<br />

Author believes that the most of the time is spent in identifying and selecting the problem and<br />

conduction literature review. It is also vital to determine that simulation tool also requires<br />

some time during configuration and simulation, as results are often indispensable. Author<br />

divided the overall research into four stages.<br />

4.3.1 Problem Selection / Identification<br />

In problem selection stage author adhere to only MANET and TCP as focus area of research<br />

interest. Problem has been selected in consideration to data performance issues in MANET<br />

due to wireless nature of the network.<br />

4.3.2 Literature Review for TCP and MANET<br />

It is necessary to conduct literature study for understand basic and expertise concept regarding<br />

TCP variants, Ad hoc networks, MANET protocols and related work. OPNET simulator study<br />

is also important to develop the scenario, run simulation and collect result.<br />

29


State of art<br />

Technology<br />

Evolution<br />

Internet<br />

Problem<br />

Identification<br />

and Selection<br />

Real<br />

Problem<br />

Author<br />

Interest<br />

Books<br />

Figure 4.1 Research Methodology<br />

4.3.3 Building Simulation Environment<br />

This stage is critical to understand as it exhibit deep understanding of how and why<br />

these specific nodes and protocols are chosen. Also it conceptually accelerates the<br />

whole simulation work efficiently and smoothly.<br />

4.3.4 Simulation Results<br />

The last stage is to grasp the relevant results of interest for research study. Simulation<br />

graph results consist of TCP performance for Tahoe, Reno and New Reno relative to<br />

each selectable MANET protocol i.e. AODV, DSR and TORA.<br />

4.4 Simulation Tool<br />

Literature<br />

Review of<br />

TCP and<br />

MANET<br />

Building<br />

Scenario<br />

State of<br />

art study<br />

Tool<br />

Selection<br />

TCP Variant<br />

Selection<br />

Protocol<br />

Selection<br />

Problem<br />

Simulation<br />

Implementation<br />

Graph<br />

Results<br />

Tool<br />

Configuration<br />

Simulation<br />

Results<br />

Performance<br />

Analysis<br />

Assumption and<br />

Conclusions<br />

OPNET is selected as it offer easy graphical interface, possibility to develop and run<br />

this simulation environment, validity of the simulation results and the tools is highly<br />

reliable, robust and efficient. Another factor of choosing OPNET is the author’s<br />

familiarity and trust over the tool.<br />

30


Chapter 5<br />

Simulation and Empirical<br />

Study<br />

31


5.1 Simulation Environment<br />

This section is the major portion of the thesis, it is important to setup simulation environment<br />

to observer TCP behavior over MANET. Quantitative analysis is conducted to with the help<br />

of OPNET tool.<br />

5.1.1 Model<br />

Actual problems are simulated through computers by modeling design for actual systems and<br />

theoretical described systems, simulations are executed through computers for the collection<br />

of relative informational results. Learning by doing [23], is a primary concept about systems<br />

in study which requires modeling and operating them.<br />

Execution<br />

Analysis<br />

Model<br />

Design<br />

Model<br />

Execution<br />

Figure 5.1: Simulation Model, [23]<br />

5.1.2 OPNET<br />

Optimized Network Evaluation Tool (OPNET version 14.5) modeler is used in<br />

for simulation network design and execution. OPNET technologies Inc [24],<br />

offers drag and drop communication devices, maximum technologies, multiple<br />

protocols and virtual environment for simulation.<br />

5.1.3 Network Entities and Functions<br />

Simulation network model contain important entities as depicted in the figure<br />

below:<br />

32


Figure 5.2 MANET eight node scenarios<br />

5.1.3.1 Application Definition<br />

In our thesis, this module has been configured to achieve the desired results.<br />

Basically we administer application name as FTP_Application and made<br />

necessary configurations, [Appendix].<br />

5.1.3.2 Profile Configuration<br />

In this configuration I set the profile name with start time offset and starts time,<br />

[Appendix].<br />

5.1.3.3 Mobility Configuration<br />

This module is required to produce the mobility options for the mobile nodes; I<br />

have set default random waypoint and adjusted some parameters, [Appendix].<br />

5.1.3.4 Server<br />

This module controls the traffic for MANET, protocol selection and TCP flavor<br />

has been selected through this module, [Appendix].<br />

5.1.3.5 Mobile Nodes<br />

I have set the mobility options; dynamically allocate the IP addresses to all<br />

mobile nodes including server as well as different routing protocols,<br />

[Appendix].<br />

5.2 Simulation Configuration<br />

A detail configure is described in [Appendix].<br />

5.3 Simulation Flow<br />

Step by step approach is used to keep the simulation flow clear and easy.<br />

Following model for simulation flow is drawn.<br />

33


MANET<br />

Network<br />

design<br />

Running/<br />

Executing<br />

Simulation<br />

Figure 5.3: Simulation Flow<br />

MANET network is designed for the simulating the model and configuration statistics<br />

are applied on the whole model separately and the with regard to each individual<br />

scenario.<br />

Simulation is executed multiple times to obtain accurate results describe in each<br />

scenario.<br />

Results from each scenario are gathered as graphs and stored in .jpg files to further use<br />

in the thesis report. Some graphs were plotted one over another and with different<br />

protocol selections and TCP flavors to observe the require statistics.<br />

5.4 Scenarios<br />

The results obtained during the simulation are depicted in this area. In simulation there are<br />

three type of different scenarios based on the number of nodes. Mainly we are concern with<br />

throughput of each variant of TCP and to find out which variants out perform with what type<br />

of routing protocol. To keep clear analysis let us consider each scenario separately, starting<br />

from the three node scenario.<br />

Three nodes Scenario<br />

Apply<br />

Configuration<br />

and Statistics<br />

Collecting<br />

Results<br />

The table 5.1 shows the detail of routing protocol and TCP variants in three nodes scenario.<br />

Without these three nodes there is a fixed node which working as source. A connection has<br />

been established from each node to transfer a file of the same size over each connection. Then<br />

to find out that which variants of TCP perform well and what was the underlying protocol.<br />

34


Table5.1 Detail of TCP Variants and Routing Protocol for Three Nodes<br />

THROUGHPUT/ DELAY/ CONGESTION W<strong>IN</strong>DOW MEASUREMENT<br />

Stages TCP Variants Protocol Number of nodes Speed of Nodes m/s<br />

A New Reno AODV 3 10<br />

A New Reno DSR 3 10<br />

A New Reno TORA 3 10<br />

B Reno AODV 3 10<br />

B Reno DSR 3 10<br />

B Reno TORA 3 10<br />

C Tahoe AODV 3 10<br />

C Tahoe DSR 3 10<br />

C Tahoe TORA 3 10<br />

Throughput<br />

From figure 5.4, by looking at the throughput performance between AODV and DSR at<br />

approximately 25 seconds, AODV has better throughput performance over DSR. Comparing<br />

AODV with TORA at the approximation of 95 sec, AODV provides better throughput<br />

performance, in all the three graphs.<br />

Total time consumed by each protocol for send the data through New Reno, Reno and Tahoe<br />

is relatively smaller for AODV followed by DSR and than TORA. It means that TORA has<br />

worst throughput performance in each of the three cases for MANET 3 nodes.The cause<br />

behind the TORA less performance is considered as the reality of TORA working for route<br />

recreation, maintenance and erasure, if dropping of the route occurs, which requires more<br />

time and have bad impact in the data performance.<br />

35


A B C<br />

Figure 5.4: Throughput comparison in three nodes scenario<br />

Five Nodes Scenario.<br />

For five nodes scenario the detail of different protocols as shown in Table 5.2. There are five<br />

nodes working as clients to establish connection with a fixed node working as source, and to<br />

transfer a file of the same size over each connection.<br />

Table5.2 Detail of TCP Variants and Routing Protocol for Five Nodes<br />

THROUGHPUT/ DELAY/ CONGESTION W<strong>IN</strong>DOW MEASUREMENT<br />

Stages TCP Variants Protocol Number of nodes Speed of Nodes m/s<br />

A New Reno AODV 5 10<br />

A New Reno DSR 5 10<br />

A New Reno TORA 5 10<br />

B Reno AODV 5 10<br />

B Reno DSR 5 10<br />

B Reno TORA 5 10<br />

C Tahoe AODV 5 10<br />

C Tahoe DSR 5 10<br />

C Tahoe TORA 5 10<br />

Throughput<br />

Form figure 5.5, comparing all the three graphs with each other I have more or less same<br />

assumption as for node three scenario, but when comparing figure 5.5 with figure 5.4, we<br />

observe that as the number of the nodes are increased approximately 75% (3 to 5), throughput<br />

has been decreased for every TCP variant and each desired protocols.<br />

36


A B C<br />

Figure 5.5: Throughput comparison in five nodes scenario<br />

Eight Nodes Scenario<br />

Different protocols evaluated in this scenario are listed in Table 5.3. Like other scenario<br />

depending on the number of clients eight simultaneous connections has been established with<br />

a fixed source to download a file of the same size over each connection.<br />

Table5.3 Detail of TCP Variants and Routing Protocol for Eight Nodes<br />

THROUGHPUT/ DELAY/ CONGESTION W<strong>IN</strong>DOW MEASUREMENT<br />

Stages TCP Variants Protocol Number of nodes Speed of Nodes m/s<br />

A New Reno AODV 8 10<br />

A New Reno DSR 8 10<br />

A New Reno TORA 8 10<br />

B Reno AODV 8 10<br />

B Reno DSR 8 10<br />

B Reno TORA 8 10<br />

C Tahoe AODV 8 10<br />

C Tahoe DSR 8 10<br />

C Tahoe TORA 8 10<br />

Throughput<br />

From figure 5.6, we conclude that the graph behavior remains same and the assumption made<br />

for figure 5.4 are also acknowledgeable. Further we observe that the AODV have the higher<br />

throughput in the start in all the three figures (5.4, 5.5, and 5.6) as compared to the DSR and<br />

TORA. A small change has been observed in the number of data packets when nodes are<br />

increased to 8 in figure 5.6. The highest number of data packets are reduces from<br />

approximately 750 to 575, which means that if more and more nodes are added in MANET,<br />

37


throughput will reduce. Similarly TORA takes more time when the numbers of nodes are<br />

increased to 8, as compared to 3 nodes and 5 nodes.<br />

A B C<br />

Table 5.6 Throughput comparison in eight nodes scenario<br />

Assumptions<br />

It has been concluded that throughput performance of DSR and TORA are minutely affected<br />

with increase in the number of nodes and due to mobility. In general, MANET could have<br />

dynamic number of nodes connectivity in mobility, so it’s important to realize that when the<br />

number of nodes is higher, DSR and TORA would be avoided. AODV has better throughput<br />

performance shown in all three figures as compared to DSR and TORA and is the best<br />

solution for MANET. However simulation results for AODV with respect to New Reno, Reno<br />

and Tahoe depict that throughput is the same in all the cases, so our proposed solution in this<br />

case will be New Reno as it offers multiple packet loss recovery.<br />

Delay<br />

Figure 5.7 hold the simulation results of each and every TCP variant with respect different<br />

routing protocols all together.<br />

With three node scenario, TORA has the highest delay as compared to DSR and AODV<br />

which validate our simulation results. With 5 node and 8 node scenario, TORA and DSR have<br />

approximately same delay, which is not considered as a good perception in wireless networks,<br />

as we encounter numerous losses and delays due to SNR, reflection, diffraction and inter<br />

symbol interference, so the delay measure is considered highly sensitive. AODV on the other<br />

hand have similar delay for 9 results, it maybe because the high resolution graph will show us<br />

small difference in each graph subject to 3, 5 and 8 nodes respectively.<br />

38


1 2 3<br />

4 5 6<br />

7 8 9<br />

Figure 5.7 Delay Comparisons in Different Scenario<br />

39


Congestion Window<br />

Figure 5.8 hold 6 graphs define earlier for all the simulated scenarios; there are much<br />

dissimilarity within each set of variants and routing protocols.<br />

Considering 3 node scenario, congestion window of TORA reaches to the maximum of<br />

160,000 bytes and will remain there which depicts that the exponential increase in the<br />

congestion window leads to the delay and lower performance, as there are not enough space<br />

in the buffer to manage incoming data and the window remains constant.<br />

1 2 3<br />

4 5 6<br />

Figure 2.8 Congestion Window dynamics<br />

Secondly, DSR have different results in all the six cases, variations for congestion window are<br />

found approximately between 65,000 bytes to 80,000 except for case 3, where it had reached<br />

around 11,000 bytes. So it’s likely to know that DSR congestion window is quite uncertain<br />

40


and its use in the MANET network will have severe results. Congestion window will<br />

ultimately influence throughput and delay parameters important for the performance<br />

evaluation.<br />

Third protocol, AODV have similar results during individual 3 nodes and 5 nodes (New<br />

Reno, Reno and Tahoe). It explicitly defines that AODV has the formal behavior of TCP as<br />

within the normal networks. The congestion window is dynamically increasing and<br />

decreasing after receiving reply for the receiver. It is however not much clear whether it<br />

doubles the size of the congestion window after each successful data packet transmission or<br />

not, but the behavior of the graph exactly resembles with the actual TCP congestion window<br />

graph with increase and decrease. We suggest AODV as the best possible solution and<br />

recommendation for MANET.<br />

41


Chapter 6<br />

Discussions/ Results<br />

42


6.1 Conclusion<br />

The overall research has been conducted in the well organized way as defined in chapter 4.<br />

Research questions 1 and 2 defined in chapter 1 are answered through state of art study and<br />

literature review. Research question 3 and four are based on the simulation results and<br />

explanations.<br />

We adhere to the simulation results as an evident that TCP variants have minor affect on the<br />

overall results except in few cases defined earlier, but the major dependence lies on MANET<br />

routing protocols. Simulation observation based on AODV, DSR and TORA clearly describe<br />

us about the performance evaluation through measuring throughput, delay and congestion<br />

window that the best routing protocol for MANET is AODV.<br />

6.2 Future Work<br />

As I have selected these numerous MANET routing protocols of interest by simulation in an<br />

OPNET tool, another possibility of doing the same work can be done through another tool<br />

like NS-2. Also, selection of other routing protocols can be use for the performance<br />

evaluation or other parameters of performance could be considered for simulation.<br />

43


Appendix: Simulation Steps<br />

Open the OPNET simulator.<br />

Click on File and select New then click ok<br />

Enter name to project and scenario then click ok.<br />

Select Create empty scenario and click Next<br />

44


Select Campus Network then Click Next<br />

X span: 1000<br />

Y span: 1000<br />

Units : Meters then Click Next<br />

Select the Technology (MANET) then Click Next<br />

45


Now Click Finish<br />

From object Palette Tree select one by one<br />

Application Config, Profile Config, Mobility Config, Wlan_Server (Fixd Node) and<br />

Wlan_wkstn (Mobile node) with the requirements of the user.<br />

46


Drag all these object one by one in the working area.<br />

Right Click on Application Config, profile Config, mobility Config and Server to set<br />

their name.<br />

47


Click Ok<br />

1 Application Configuration<br />

Right Click on Application Config then Edit Attributes and configure the Application.<br />

48


At last Click Ok<br />

2 Profile Configurations<br />

Right Click on Profile Config then Edit Attributes and configure the Profile.<br />

50


Select all Nodes and Server Click on Protocol menu � IP � Addressing � Auto-<br />

Assign IPv4 Address.<br />

Select all Nodes and Server � Right Click on Server � Edit Attributes � Select AD-<br />

HOC Routing Protocol .e.g. AODV.<br />

In TCP Select the Parameters e.g. Tahoe.<br />

Tick Apply to Selected Objects � Ok<br />

51


3 Server Configurations<br />

Right Click on Server � Edit Attributes � Application � set Application Supported<br />

Services and Click Ok.<br />

52


4 Mobile Node Configurations<br />

Select all Nodes Right Click on one � Edit Attributes. Click on Applications �<br />

Application: Destination Preferences and set some parameters.<br />

Click on Application: Supported Profiles and set some values � Tick Apply to<br />

Selected Objects. Click Ok.<br />

53


5 Click Topology menu � Select Random Mobility � set Mobility Profile � Click<br />

Continue � Click Ok.<br />

6 Mobility Configurations<br />

Right Click on Mobility Config � Edit Attributes � Click Default Random Waypoint<br />

� Click Random Waypoint Parameters. Click OK.<br />

55


7 Save the Project.<br />

8 Click DES Menus<br />

Click DES or Right Click on work area and select Individual Statistics.<br />

56


Expand Node Statistics<br />

a) Expand TCP Connection and Tick the Congestion Window Size (byte).<br />

Right Click on it then choose Change Collection Mode then Tick Advance and<br />

Select All Values then Click Ok.<br />

b) Expand Wireless Lan Tick Delay (sec) and Throughput (bit/sec) then Right Click<br />

on both one by one and select Change Collection Mode then Tick Advance and<br />

Select All Values then Click Ok.<br />

9 Run the Project<br />

Click on DES menu Select Configure/Run Discrete Event Simulation ….ctrl+R.<br />

Here you can set Time in Weeks, Days, Hours, Minuets, and Seconds. Then Click<br />

Run.<br />

57


When Simulation is Completed then Click Close.<br />

58


10 Show the Result<br />

Click on DES menu or Right Click on Work area then Select Results then View result<br />

59


References:<br />

[1] http://www.ietf.org/rfc/rfc1180.txt<br />

[2] http://www.ietf.org/rfc/rfc2501.txt<br />

[3] K. Leung and Vivtor O.K. Li, “Transmission Control Protocol (TCP) in wireless<br />

Networks: issues, approaches and challenges,” IEEE Communications Survey, Vol. 8 No.<br />

4, pp. 64-79, 4th October 2006<br />

[4] IEEE Standard 802.11, Wireless LAN Medium Access Control (MAC) and Physical<br />

Layer (PHY) Specifications, June 2007<br />

[5] A. A. Hanbali, E. Altman, and P. Nain, “A Survey of TCP over Ad Hoc Networks,” IEEE<br />

Communication. Surveys and Tutorials, Vol. 7, No. 3, 3rd Quarter 2005,<br />

[6] J. Postal,”Transmission Control Protocol”, Request for comments, RFC 793, September<br />

1981.<br />

[7] V. Jacobson, “Congestion avoidance and control,” in: Proceedings of ACM SIGCOMM,<br />

pp. 314-29, 1988.<br />

[8] Allman, V. Paxson, and W. Stevens, “TCP Congestion Control,” Request for Comments,<br />

RFC 2581, Network Working Group, Internet Engineering Task Force, April. 1999.<br />

[9] Jany Hoe: S. Floyd and T. Henderson, “The NewReno Modification to TCP's Fast<br />

Recovery Algorithm,” RFC 2582, Network Working Group, Internet Engineering Task<br />

Force, April. 1999.<br />

[10] D. Kliazovich, F. Granelli, “C 3 TCP: Cross-layer congestion control in ad hoc wireless<br />

networks”, ELSEVIER Ad HocNetworks 4, pp. 687-708, 2006.<br />

[11] J. Liu and S. Singh, “ATCP: TCP for Mobile ad hoc Networks”, IEEE Journal in<br />

Selected Areas in Communication (JSAC), Vol 19, No.7, pp. 1300-15, July 2001,.<br />

[12] R. Cheng, H. Lin, “A Cross-layer Design for TCP End-to-End Performance<br />

Improvement in multi-hop wireless networks”, ELSEVIER, Computer communication<br />

Vol. 31, issue 14, pp. 3145-3152, Sep. 2008<br />

[13] Routing and Multicasting Strategies in Wireless Mobile Ad hoc Networks by Sung –Ju<br />

Lee University of California, Los Angeles 2000.<br />

[14] A. Zahary, A. Ayesh, “Analytical study to detect threshold number of efficient routes in<br />

multipath AODV extensions”, proceedings of International Conference of Computer<br />

Engineering & Systems, ICCES, 2007, pp. 95 – 100<br />

[15] R. Misra and C.R. Mandal, “Performance comparison of AODV/DSR on-demand<br />

routing protocols for ad hoc networks in constrained situation” ICPWC International<br />

Conference, IEEE, 2005, pp. 86 – 89<br />

[16] Lijuan Cao, K. Sharif, Yu Wang, T. Dahlberg, “Adaptive Multiple Metrics Routing<br />

Protocols for Heterogeneous Multi-Hop Wireless Networks”,<br />

[17] Changling Liu, Jörg Kaiser, A Survey of Mobile Ad Hoc network Routing Protocols*<br />

kaiser@ivs.cs.uni-magdeburg.de<br />

[18] Jin Mook Kim, In Sung Han, Jin Baek Kwon, Hwang Bin Ryou, “A Novel Approach to<br />

Search a Node in MANET”, Information Science and Security, ICISS, 2008, pp. 44 – 48<br />

60


[19] R. Thorulp, “Mobile Ad Hoc Networks and Routing Protocols”, Implementing and<br />

Evaluating the DYMO Routing Protocol, Master’s Thesis at the University of AARHUS,<br />

pp. 7- 20, 2007<br />

[20] Jin Mook Kim, In Sung Han, Jin Baek Kwon, Hwang Bin Ryou, “A Novel Approach to<br />

Search a Node in MANET”, Information Science and Security, ICISS, 2008, pp. 44 – 48<br />

[21] S. R. Chaudhry, A. Al-Khwildi, Y. Casey, H. Aldelou, “A Performance Comparison of<br />

Multi On- Demand Routing in Wireless Ad Hoc Networks”, Wireless Network and<br />

Communications Group (WNCG), School of Engineering & Design, Brunel University,<br />

West London<br />

[22] J. W. Creswell, Research Design: Qualitative, Quantitative and Mixed Methods<br />

Approach, 2nd Ed, Sage Publications Inc, California, July 2002.<br />

[23] http://www.cis.ufl.edu/~fishwick/introsim/node1.html<br />

[24] http://www.opnet.com/<br />

61

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

Saved successfully!

Ooh no, something went wrong!