\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Comparative Analysis of Routing Protocols for Mobile Adhoc Networks},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2012-01-15 (revised: 15 January 2012)}
\def\TheID{\makeatother }
\def\TheDate{2012-01-15}
\title{Comparative Analysis of Routing Protocols for Mobile Adhoc Networks}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Dr. Gurjeet  Singh}

             \affil[1]{  }

\renewcommand\Authands{ and }

\date{\small \em Received: 10 December 2011 Accepted: 4 January 2012 Published: 15 January 2012}

\maketitle


\begin{abstract}
        


Mobile ad-hoc networks (MANETs) are selfconfiguring networks of nodes connected via wireless. This kind of networks is currently one of the most important research subjects, due to the huge variety of applications (emergency, military, etc...). In MANETs, each node acts both as host and as router, thus, it must be capable of forwarding packets to other nodes. Topologies of these networks change frequenly. To solve this problem, special routing protocols for MANETs are needed because traditional routing protocols for wired networks cannot work efficiently in MANETs.

\end{abstract}


\keywords{}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
obile Ad-Hoc networks or MANET networks are mobile wireless networks, capable of autonomous operation. Such networks operate without a base station infrastructure. The nodes cooperate to provide connectivity. Also, a MANET operates without centralized administration and the nodes cooperate to provide services.   
\section[{Routing protocols for mobile adhoc networks}]{Routing protocols for mobile adhoc networks}\par
MANETs are necessary to have different routing protocols from the wired networks. There are three types of routing protocols for MANETS: protocol), WRP (Wireless Routing Protocol), OSPF (Open Shortest Path First) MANET, etc. ? Demand-driven (Reactive): AODV, DSR, TORA (Temporally Ordered Routing Algorithm), etc. ? Hybrids: ZRP (Zone Routing Protocol), HSLS (Hazy Sighted Link State), etc.\par
In the proactive protocols, each node has a routing table, updated periodically, even when the nodes don't need to forward any message.\par
In the reactive protocols, the routes are calculated only when required. When a source wants to send information to some destination, it calls on route discover mechanisms to find the best route to this destination.\par
The hybrids protocols try to use a combination of both to improve them. 
\section[{a) Reactive Routing Protocols}]{a) Reactive Routing Protocols}\par
These protocols find the route on demand by flooding the network with Route Request packets. The main characteristics of these protocols are:\par
? Path-finding process only on demand.\par
? Information exchange only when required.\par
? For route establishment, the network is flooded with requests and replies.\par
i.\par
The Dynamic Source Routing (DSR)\par
DSR is a reactive routing protocol. It uses source routing. The source node must determine the path of the packet. The path is attached in the packet header and it allows to update the information stored in the nodes from the path. There are no periodical updates. Hence, when a node needs a path to another one, it determines the route with its stored information and with a discovery route protocol. This protocol has 2 parts:\par
? Route Discovery ? Route Maintenance a. Route Discovery When a node sends a packet to a destination, firstly it looks at its Route Cache the routes previously learned. If no route is found in its cache, then the node begins the route discovery process with a Route Request Packet (RREQ) broadcast. This packet includes the destination address, the source address and an identification number (request id). Each node receiving the RREQ, looks for the destination in its cache. If it does not know the route to the destination, it adds its( D D D D )\par
address to the 'route record' in the RREQ and propagates it by transmitting it as a local broadcast packet (with the same request id). To limit the number of RREQ's, if one node receiving the RREQ has recently seen another RREQ from the same source, with the same request id, or if it finds its own address in the route record, then it discards the RREQ. In Figure \hyperref[fig_4]{1}.2 the development of the route record while the RREQ is spreading through the network is shown. The maintenance of the routes is useful to check the operation of a route and to report any routing error to the source. This check is made between consecutive nodes. When there is a problem in the transmission found by the link level, the RERR (Route Error) packets are sent by the node. This RERR has the addresses of both nodes in which the link failed. For example, in the situation illustrated in Figure \hyperref[fig_4]{1}.3 N1 has originated a packet for N8 using a source route through intermediate nodes N2 and N5. In this case, N1 is responsible for the reception of the packet at N2, N2 is responsible for the reception at N5, and N5 is responsible for the reception at the final destination N8.\par
Figure \hyperref[fig_4]{1}.3 : Forwarding of the RREP with the route record As N5 is unable to deliver the packet to N8, N5 returns a Route Error to N1 stating that the link from N5 to N8 is currently 'broken'. N1 then removes this broken link from its cache. In other words, when a node receives a RERR, it deletes the link failed in its routes list, and all the routes that have this link are cut at this point. Besides the RERRs, ACKs (acknowledgements) can be used to verify the links availabity.\par
ii.\par
The Adhoc On Demand Distance Vector (AODV)\par
The AODV protocol is a reactive routing protocol. It is a Single Scope protocol and it is based on DSDV. The improvement consists of minimizing the number of broadcasts required to create routes. Since it is an on demand routing protocol, the nodes who are not in the selected path need not maintain the route neither participate in the exchange of tables.\par
When a node wants to transmit to a destination and it does not have the valid route, it must begin the Path Discovery process. Firstly, it sends a broadcast of the Route Request (RREQ) packet to its neighbours, and they relay the packet to their neighbours and so on until they reach the destination or any intermediate node which has a 'fresh' route to the destination (Figure \hyperref[fig_4]{1}.4). Just like in DSDV sequence numbers are used to identify the most recent routes and to solve the loops. If a source node moves, it is capable of restarting the discovery protocol to find a new path to the destination. If an intermediate node moves, its previous neighbour (in source-destination way) must forward a RREP not requested with a fresh sequence number (greater than the known sequence number) and with a number of hops to destination infinite to the source node. In this way, the source node restarts the path discovery process if it is still needed.\par
Hello messages (periodic broadcasts) are used to inform mobile node about all the neighbourhood nodes. These are a special type of RREP not solicited, of which sequence number is equal to the sequence number of the last RREP sent and which has a TTL=1 (Time To Life) to not flood the network. They can be used to maintain the network connectivity, although other methods used more often exist for this function, like for example, to listen to the neighbour nodes transmissions. Each node maintains a route to the rest of the nodes of the ad hoc network. The nodes of the ad hoc network periodically exchange messages about the link state, but it uses the 'multipoint replaying' OLSR strategy to minimize the messages quantity and the number of nodes that send in broadcast mode the routing messages. The strategy MPR (Multipoint Relay) [MANET lies in that each node uses 'Hello' messages to discover what nodes are in a one hop distance and makes a list. Each node selects a group of neighbours of that list that are able to reach all the nodes in a distance of two hops with regard to the node that is making the selection. For example, in Figure \hyperref[fig_4]{1}.9 the node A selects the nodes B, C, K and N as the MPR nodes, because they are capable of reaching all the nodes at two hops distance with regard to the node A.\par
Figure \hyperref[fig_4]{1}.9 : Multipoint Relays These neighbours selected are the only nodes in charge to relay the routing packets and are called MPRs (Multipoint Relays). The rest of the neighbourhood process the routing packets that they receive, but they can not relay them.\par
Each node decides an optimum path (in number of hops) to each destination using the stored information (in its topology routing table and in of their neighbours ones). Besides each node stores that information in a routing table for usage when a node wants to sent data. This protocol selects bidirectional links to send packets, and does not use unidirectional links. The OLSR protocol is more efficient in networks with high density and highly sporadic traffic. The quality metrics are easy to expand to the current protocol. OLSR requires that it continuously has some bandwidth in order to receive the topology updates messages.\par
ii. 
\section[{The Destination Sequenced Distance Vector (DSDV)}]{The Destination Sequenced Distance Vector (DSDV)}\par
The DSDV is a distance vector, proactive routing protocol. It is based in the Bellman-Ford algorithm, but improved to solve the routing loop problem. It uses the distance vector algorithm to find the shortest path to the destination. Each node within the ad hoc network maintains a routing table with the following information to each destination.\par
? Destination IP address.\par
? Destination sequence number.\par
? Next hop (IP address). ? Cost (in number of hops).\par
? Install time: used to delete old routes.\par
Each node sends periodically broadcasts with the routing table updated to its neighbours:\par
? Each node adds its sequence number when it sends its routing table. ? When the other nodes receive this information, they update its routing tables.\par
The routing tables also can be sent if there are topology changes (link creation or breakage). In this case, the update information travelling in the routing messages is:\par
? Destination IP address.\par
? Number of hops.\par
? Sequence number.\par
The nodes use the sequence numbers to distinguish between old and new routes to a destination. A node increases its sequence number when there is a topology change (a new link is created or deleted). The route to a destination with the biggest sequence number (the more current) is the valid one. If there are two routes with the same sequence number, the valid is the one which number of hops is smaller. Two types of route update are used ? Full dump: This packet carries the whole routing table. It is unusual to send this packet. ? Incremental: This packet carries only the routing table information of a node that has changed since the last full dump sent. These packets are sent more frequently. Hence, the control overhead and the bandwidth consumption are smaller. 
\section[{c) Hybrid Routing Protocols}]{c) Hybrid Routing Protocols}\par
These protocols are a combination of reactive and proactive routing protocols, trying to solve the limitations of each one.\par
Hybrid routing protocols have the potential to provide higher scalability than pure reactive or proactive protocols. This is because they attempt to minimise the number of rebroadcasting nodes by defining a structure (or some sort of a backbone), which allows the nodes to work together in order to organise how routing is to be performed. By working together the best or the most suitable nodes can be used to perform route discovery. i. 
\section[{The Zone Routing Protocol (ZRP)}]{The Zone Routing Protocol (ZRP)}\par
The Zone Routing Protocol (ZRP) is a hybrid routing protocol. It combines the advantages from reactive and proactive routing protocols. This protocol divides its network in different zones. These zones are the nodes local neighbourhood. Each node has its own zone. Each node can be into multiple overlapping zones, and each zone can be of a different size. The size of a zone is given by a radius of length, where the number of hops is the perimeter of the zone. Within each zone it is used a proactive routing protocol.\par
Therefore, each node into the zone knows how to reach its neighbours. However, if the packets are sent to a node outside of the zone, it is used a reactive routing protocol.\par
ZRP runs three routing protocols:? Intrazone Routing Protocol (IARP) ? Interzone Routing Protocol (IERP) ? Bordercast Resolution Protocol (BRP)\par
IARP is a link state routing protocol. It operates within a zone and learns the routes proactively. Hence, each node has a routing table to reach the nodes within its zone.\par
IERP uses the border nodes to find a route to a destination node outside of the zone. IERP uses the BRP.\par
BRP is responsible for the forwarding of a route request.\par
When the Route Discovery process begins, the source node asks to its routing table and if necessary, it starts a route search between different zones to reach a destination. If a route is broken by a node's mobility into the same zone where the node was, the routing tables used for the proactive routing protocol must be updated. If the node's mobility is from one zone to another one, then it is necessary to execute a query between zones.\par
To use a reactive routing protocol to find a route from a source node to a destination node placed in another zone reduces the control overhead (in comparison with the proactive ones) and the delays in the Route Discovery (in comparison with the pure reactive ones), since these routes are discovered much faster. The reason is because to find a route to a node placed outside the routing zone, the route request is send only to the border router within the zone where the destination is. This border router can answer to the request since it has a routing table to do the proactive routing and knows how to reach the destination.\par
The disadvantage of ZRP is that it becomes a proactive routing protocol if the radius is big. Otherwise, if the radius is small, it becomes a reactive routing protocol.\par
In Figure \hyperref[fig_4]{1}.10 a Route Discovery process is shown; the node S sends information to the node X, and by IARP decides X is not in the same zone that S. The search travels through the border nodes to find the zone where X is. Finally, the border node G discovers that X is in its zone and sends a route response to S. Even though the hybrid nature of the ZRP seems to indicate that it is a hierarchical protocol, it is important to point out that the ZRP is in fact a flat protocol. ZRP is more efficient for large networks. 
\section[{d) Reactive Vs Proactive}]{d) Reactive Vs Proactive}\par
Proactive routing protocols loose more time updating their routing tables. Therefore when the topology changes frequently, most of the current routes in the tables can be wrong. Hence, these protocols are recommended for ad-hoc networks semi dynamics.\par
Reactive routing protocols have delay in route determination, because of the flooding mechanism. They are recommended for networks with nodes moving constantly.\par
Intuitively, we can think in the advantages and disadvantages of both looking the table 1.1:( D D D D )\par
Table  {\ref 1}.1 : Comparison between proactive and reactive routing protocols e) Quality of Service Quality of service can be used as a measurement of how good the routes in the network are. The routes should guarantee a set of pre specified service attributes, such as delivery, bandwidth and delay variance (jitter). It also involves the specification of latency, loss, availability etc... For a protocol to provide good QoS it must determine new routes rapidly and with minimal bandwidth consumption. There are several metrics that directly affect the QoS of every protocol, for example: Packet delivery ratio, control packet overhead (packets and total bytes), average hop count, end-to-end latency and power consumption to mention a few. Using a protocol that provides good quality of service will greatly affect the MANETs performance. 
\section[{f) Comparing the Protocols}]{f) Comparing the Protocols}\par
As a proactive routing protocol, OLSR inserts high control traffic overhead on the network. To maintain and to update the routing table for the entire network it needs a lot of communication between the nodes, as well as periodic updates flooding the network. The use of MPR's reduces this control traffic overhead, but for small networks the improvement is minimal. The traffic overhead also consumes bandwidth.\par
The behaviour of reactive protocols AODV and DSR is different. The main part of control traffic is emitted during route discovery. Therefore, a lot of the resource and bandwidth consumption is related to actual data traffic.  
\section[{Results}]{Results}\par
In Figure \hyperref[fig_4]{1}.11, the Control Overhead curve for the Node Density experiments is shown. The control overhead measurements are normalized. The horizontal axis represents the distance between neighbouring nodes in the grid. The sparse networks have higher paths lengths. Thus, in these networks there are more rebroadcasts of route requests, and more route reply packets. For that reason DSR increases its control overhead when the density is smaller. However, AODV begins with a high overload when the node density is high, but uses fewer control packets as the density is smaller.\par
Figure \hyperref[fig_4]{1}.11 : Throughput for Network Size ZRP performs similar to AODV. When the density is high, it performs better and this is because the original route acquisition process depends on neighbouring nodes overhearing and rebroadcasting route requests, and if router requests are lost, the entire process stalls. The hidden terminal problem can contribute to route request losses, and is more prevalent in sparse networks. These protocols have difficulty dealing with a network with few neighbours. 
\section[{a) Number of Hops}]{a) Number of Hops}\par
The strangest result is to see that the latency for OLSR has the highest values from 1 to 10 hops, and generally the highest slope. For OLSR to lose its innate advantage in latency, network route convergence would have to be slower than route acquisition, and given the high control overhead data that was collected for this experiment set, it is easy to see that this is the case. However, under normal circumstances the OLSR is supposed to be the best of the analyzed protocols since the point of view of the latency. For ZRP at the 1 and 2 hop has better latency than OLSR. This is because the proactive zone of interest is much smaller. At 3 hops and beyond, this result is indicative of the interzone routing, and it shows a fairly flat graph from 3 to 10 hops, with some oscillation caused by random number seeds not being completely filtered out.\par
IV. 
\section[{Conclusion}]{Conclusion}\par
For a network with a large number of nodes, which move with changing velocities and have different traffic patterns, a hybrid routing protocol is the best choice. The nodes moving slowly and with high traffic should run the proactive routing features, and the rest of nodes implement the reactive ones. Besides, the choice should be a hierarchical approach to achieve a big scalability. The AODV and DSR protocols will perform better in the networks with static traffic and with a number of source and destination pairs relatively small for each host. In this case, AODV and DSR use fewer resources than OLSR, because the control overhead is small. Also, they require less bandwidth to maintain the routes. Besides, the routing table is kept small reducing the computational complexity. Both reactive protocols can be used in resource critical environments.\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{11}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 1 . 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{12}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 1 . 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1416}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 1 . 4 :Figure 1 . 6 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Figure 1 .}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-7.png}
\caption{\label{fig_6}Figure 1 .}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-8.png}
\caption{\label{fig_7}Figure 1 .}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-9.png}
\caption{\label{figure9}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-10.png}
\caption{\label{figure10}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-11.png}
\caption{\label{figure11}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{}
\end{longtable} \par
  {\small\itshape [Note: ? : AP,Deptt of CSE/IT Desh Bhagat Institute of Engg \& Management Moga. Author ? : AP,Deptt of CSE/IT Desh Bhagat Institute of Engg \& Management Moga.]} 
\caption{\label{tab_0}?}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{12} \par 
\begin{longtable}{P{0.85\textwidth}}
D D D D )\\
(\end{longtable} \par
  {\small\itshape [Note: : Comparison between the Protocols III.]} 
\caption{\label{tab_1}Table 1 . 2}\end{figure}
 			\footnote{© 2012 Global Journals Inc. (US)} 		 		\backmatter  			 			 			  				\begin{bibitemlist}{1}
\bibitem[Abolhasan et al. ()]{b0}\label{b0} 	 		‘A Review of Routing Protocols for Mobile Ad hoc Networks’.  		 			M Abolhasan 		,  		 			T A Wysocki 		,  		 			E Dutkiewicz 		.  	 	 		\textit{In Elsevier Journal of Ad hoc Networks}  		2004. p. .  	 
\bibitem[Perkins et al. (2001)]{b1}\label{b1} 	 		‘Ad hoc On-Demand Distance Vector (AODV) Routing’.  		 			C E Perkins 		,  		 			; C Perkins 		,  		 			E Belding-Royer 		,  		 			S Das 		.  		 <draft-ietf-manet-aodv- 12.txt>.  	 	 		\textit{IETF RFC}  		2003. 2001. November 2002. Addison-Wesley. 3561.  	 	 (Ad hoc On-Demand Distance Vector (AODV) Routing) 
\bibitem[Benzaid et al. ()]{b2}\label{b2} 	 		‘Analysis and simulation of fast-OLSR’.  		 			M Benzaid 		,  		 			P Minet 		,  		 			A K Al 		.  	 	 		\textit{The 57th IEEE Semiannual Vehicular Technology Conference. 3},  				2003. p. pp.  	 
\bibitem[Thomas Heide Clausen, Philippe Jacquet and Laurent Viennot (ed.)]{b4}\label{b4} 	 		\textit{Comparative Study of Routing Protocols for Mobile Ad-hoc NET works},  		Thomas Heide Clausen, Philippe Jacquet and Laurent Viennot (ed.)  		 	 
\bibitem[Perkins and Bhagwat ()]{b5}\label{b5} 	 		‘Highly Dynamic Destination Sequenced Distance Vector (DSDV) for Mobile Computers’.  		 			Charles E Perkins 		,  		 			Pravin Bhagwat 		.  	 	 		\textit{Proceedings of the SIGCOMM'94 Conference on Communications Architectures, Protocols and Applications},  				 (the SIGCOMM'94 Conference on Communications Architectures, Protocols and Applications)  		2010.  	 
\bibitem[Benzaid et al. ()]{b3}\label{b3} 	 		‘Integrating fast Mobility in the OLSR routing protocol’.  		 			M Benzaid 		,  		 			P Minet 		,  		 			A K Al 		.  	 	 		\textit{Proceedings of the 4th IEEE Conference on Mobile and Wireless Communications Networks},  				 (the 4th IEEE Conference on Mobile and Wireless Communications NetworksStockholm, Sweden)  		2002.  	 
\bibitem[Johnson et al. ()]{b6}\label{b6} 	 		\textit{The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks(DSR)},  		 			D Johnson 		,  		 			D Maltz 		,  		 			Y Hu 		.  		2011.  	 	 (IETF Internet-Draft) 
\end{bibitemlist}
 			 		 	 
\end{document}
