\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={Enhancement of Network Life Time using Binary Tree Based Multicast Routing Protocol for Mobile Ad Hoc Network}, 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{2013-01-15 (revised: 15 January 2013)} \def\TheID{\makeatother } \def\TheDate{2013-01-15} \title{Enhancement of Network Life Time using Binary Tree Based Multicast Routing Protocol for Mobile Ad Hoc Network} \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]{prof.Guru Prasad} \affil[1]{ GURU NANAK DEV ENGINEERING COLLEGE, BIDAR} \renewcommand\Authands{ and } \date{\small \em Received: 10 December 2012 Accepted: 2 January 2013 Published: 15 January 2013} \maketitle \begin{abstract} A mobile ad hoc network (MANET) is an interconnected system of mobile hosts without a fixed infrastructure. In MANETs, each mobile host has multi-hop transmission capability, and it has to serve as a router. Owing to the dynamic topology and limited resources of mobile hosts, the routing scheme in MANETs presents an important challenge. In this study, a Enhancement of Network Life Time using Binary Tree Based Multicast Routing Protocol for MANET is proposed. In this proposed scheme, all nodes are randomly classified into two types, group-1 and group-2. To achieve the load balance, two multicast trees (tree-1 for group-1 and tree-2 for group-2) are constructed. The proposed system mainly focused on maintaining route stability. Thus proposed system outperform AOMDV version of AODV in term of Performance evaluation metrics such as packet delivery ratio, control overhead , Network life time, Normalized delay. \end{abstract} \keywords{packet delivery ratio, control overhead, network life time, normalized delay.} \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 mobile ad hoc network (MANET) is an interconnected system of mobile hosts without a fixed infrastructure. Every node in an MANET must be able to function as a route to forward data to other nodes. When applications must send the same data to more than one destination, multicasting is often used. Multicasting reduces the communication costs for applications that send the same data to multiple recipients. Instead of sending via multiple unicast, multicasting minimizes the link bandwidth consumption, router processing and delivery delay .Existing multicast routing protocols for MANETs can be broadly classified into tree-based routing protocols \hyperref[b0]{[1]}\hyperref[b1]{[2]}\hyperref[b2]{[3]}\hyperref[b3]{[4]}\hyperref[b4]{[5]}\hyperref[b5]{[6]}\hyperref[b6]{[7]}\hyperref[b7]{[8]}\hyperref[b8]{[9]} and mesh-based routing protocols \hyperref[b9]{[10]}\hyperref[b10]{[11]}\hyperref[b11]{[12]}\hyperref[b12]{[13]}\hyperref[b13]{[14]}\hyperref[b14]{[15]}. Tree-based routing protocols build a tree structure that connects all multicast members and provide one path between a pair of source and destination nodes.\par Mesh-based protocols yield a multi-path between the source and the destination nodes. When a link fails, mesh-based multicast protocols do not need to re-compute a mesh. Royer and Perkins \hyperref[b6]{[7]} propose a multicast ad hoc on demand distance vector routing Authors ? ? : Guru Nanak Dev Engineering College Bidar Karnataka, India. E-mails : scarvi@rediffmail.com, sonucs024@gmail.com protocol (MAODV). MAODV establishes on-demand multicast tree and uses these for delivery of multicast data. MAODV is a typical tree-based multicast routing protocols. Ballaradie, A., Crowcroft J., Francis \hyperref[b2]{[3]} proposed a new protocol called MQ, Multicast with QoS, which supports multimedia group communications with QoS guarantees for heterogeneous recipients. With MQ, while resource reservation is de-coupled from QoS multicast routing, they are integrated in a way to avoid the problem of sender-oriented path determination, a problem that occurs when RSVP is used in conjunction with QoS routing for heterogeneous reservations. Bommaiah, E .and McAuley, A \hyperref[b4]{[5]}propose a multicast routing protocol for ad-hoc networks, which is particularly efficient for multi-source multicast transmissions. In order to minimize the total transmission power in MANETs, routing protocols have been proposed to increase the lifetime of networks {\ref [16 -18]}.Minimum total transmission power (MTPR) \hyperref[b16]{[17]} establishes on-demand unicast routing based on the transmission power. This paper is discussed in following number of section. Section II deals Ad-hoc wireless network, Section III deals with Routing protocol. Section IV Wireless Simulation, Section V deals with Simulation Results, Section VI deals with conclusion and section VII deals with References. \section[{II.}]{II.} \section[{Adhoc Wireless Network}]{Adhoc Wireless Network}\par A mobile Adhoc network is a collection of wireless mobile nodes that communicate with one another without any fixed networking infrastructure. Ad Hoc networks are multi-hop wireless networks where all nodes cooperatively maintain network connectivity. These types of networks are useful in any situation where temporary network connectivity is needed, such as in disaster relief. In multi-hop wireless ad-hoc networks, designing energy-efficient routing protocols is important because nodes have limited power. However, it is also an inherently hard problem due to two important factors: First, the nodes may be mobile, this requires that the energy-efficient routing protocol should be fully distributed and adaptive to the current states of nodes; Second, the wireless links may be uni-directional due to asymmetric power configurations of adjacent nodes. \section[{Routing Protocol}]{Routing Protocol}\par Ad hoc Routing protocols is classified into two types such as proactive and reactive. The table-driven routing protocol is proactive, it worked on distance vector based or link state based routing strategies. The drawback of this algorithm is the frequent updation is required which consumes large amount of memory, bandwidth and power \hyperref[b31]{[31]}. But, in the reactive routing protocol, each node does not need to maintain the routing table. When a source node is ready to send data, it initiates the route discovery procedure and maintains its routes only. The reactive routing protocol minimizes the routing overhead and also called on-demand approach. \section[{a) AODV Protocol}]{a) AODV Protocol}\par The AODV \hyperref[b32]{[32]} protocol based on the reactive routing discovery uses three different kinds of messages: Route request (RREQ), Route Reply (RREP) and Route Error (RERR). In addition, destination sequence numbers are used to ensure loop freedom at all times. In AODV, each source node finds a new route by the limited flooding of RREQ and obtains a route to its destination through RREP. b) AOMDV Protocol AOMDV \hyperref[b33]{[33]} uses the basic AODV route construction process. In this case, however, some extensions are made to create multiple loop-free, linkdisjoint paths. The main idea in AOMDV is to compute multiple paths during route discovery. It consists of two components:\par 1. A route update rule to establish and maintain multiple loop-free paths at each node. 2. A distributed protocol to find link-disjoint paths.\par Before describing AOMDV, we first discuss AODV, from which it is derived. In AODV, when a source needs a route to a destination, it initiates a route discovery process by flooding a RREQ for destination throughout the network. RREQs should be uniquely identified by a sequence number so that duplicates can be recognized and discarded. Upon receiving a nonduplicate RREQ, an intermediate node records previous hop and checks whether there is a valid and fresh route entry to the destination in routing table. If such is the case, the node sends back a RREP to the source; if not it rebroadcasts the RREQ. A node updates its routing information and propagates the RREP upon receiving further RREPs only if a RREP contains either a larger destination sequence number (fresher) or a shorter route found. In AOMDV each RREQ, respectively RREP arriving at a node potentially defines an alternate path to the source or destination. Just accepting all such copies will lead to the formation of routing loops. In order to eliminate any possibility of loops, the advertised hop count is introduced. The advertised hop count of a node i for a destination d represents the maximum hop count of the multiple paths for d available at i. The protocol only accepts alternate routes with hop count lower than the advertised hop count, alternate routes with higher or the same hop count are discarded. The advertised hop count mechanism \hyperref[b33]{[33]} establishes multiple loop-free paths at every node. These paths still need to be disjoint. Duplicate copies of a RREQ are not immediately discarded. Each packet is examined to see if it provides a node disjoint path to the source. For node-disjoint paths all RREQs need to arrive via different neighbors of the source. This is verified with the first hop field in the RREQ packet and the first hop list for the RREQ packets at the node. At the destination a slightly different approach is used, the paths determined there are link-disjoint, not node disjoint. In order to do this, the destination replies up to k copies of the RREQ, regardless of the first hops. The RREQs only need to arrive via unique neighbors. c) Enhancement in Network Life time using binary tree based multicast routing protocol for mobile ad hoc network\par In this study, a Enhanced Network Life Time tree-based multicast routing protocol (NLDTMRP) for MANETs is proposed. In the proposed scheme, all nodes are randomly classified into two types, group-1 and group-2. To achieve the load balance, two multicast trees (tree-1 for group-1 and tree-2 for group-2) are constructed .Each node maintained two routing tables: the neighbouring table and the routing table. The neighbouring table was easily obtained by the periodic broadcast of the hello packet. These tables are described below:\par 1. Neighbouring The src ID and Dest ID fields contains the unique addresses of the source and the destination node, respectively. The seqno field contains the sequence number of the source node (guaranteeing the loop-freedom of all routes to the destination node). The route\textunderscore class field recorded the class of route for group-1 or group-2. The next\textunderscore hop field contained the address of the neighbouring node to which data packets had to be forwarded. In the proposed scheme, power level threshold (P threshold ) is defined. When the source node wants to send the packet to the destination nodes, it broadcasts the route request (RREQ) packet to the neighbouring nodes in its transmission range, when the source node does not have a path in the routing table. The RREQ packet carries the following information in its header: 'Type' refers to the packet type: RREQ, RREP or RERR. 'Src' is the source node. 'SrcSeq' is a monotonically increasing sequence number. 'Src' and 'SrcSeq' are used to uniquely identify each RREQ packet. It can be used to check duplicate copies of an old request and detect the stale cached routes. 'DestList' is a set of destinations. 'Path Traversed' Here 'Type' is certainly RREP. 'Source' is the source node. 'Destination' is the destination node. The field 'ReversePath' in each RREP packet includes the reverse path. 'Class' is the type of node: group-1 or group-2.The Class field of RREP packet is the assigned type for the RREQ packet. When the intermediate node receives the RREP packet, it selects the upstream node based on the corresponding type of RREP packet and sends the RREP packets to the source node. The detail of the route discovery process. \section[{i. Algorithm 1: Route discovery process}]{i. Algorithm 1: Route discovery process}\par A n etwork is modeled as graph G(N, E), where N is the finite set of mobile nodes and E is a set of links. Suppose n is the number of mobile nodes and N is the set of mobile nodes N= \{N1, N2, . . . , {\ref Nn\}} \section[{Route Maintenance Process}]{Route Maintenance Process}\par It is divided in to three parts: i. Join Operation When a new member wants to join the multicast tree, it broadcasts a join route request (RREQJ) packet across the networks. Only a node that is a member of the multicast tree (i.e. a router for the group) may respond, if a node receives a RREQJ packet for a multicast group of which it is not a member or it does not have a route to that group, it creates a reverse route entry to the prospective node and then broadcasts the RREQJ packet to its neighbours. Any intermediate node receives the RREQJ, it rebroadcasts the RREQJ if the P remain of the node is higher than P threshold . When each member node of the multicast tree receives the RREQJ ii. Node Prune Operation When a node wants to move from the multicast tree, the pruning node broadcasts to its upstream node a pruning route request (RREQP) packet. When the upstream node receives the RREQP packet, it removes the corresponding entry from its multicast routing table. If the upstream node becomes a leaf node and it is not the tree receiver, the node can further prune itself from the tree. records the routing information. "Class" is the type of node: group-1 or group-2. "RREQType" refers to the RREQ type: RREQ, After neighbouring nodes receive the RREQ packet, the neighbouring nodes first check the remaining battery of nodes (P remain ). When P remain of nodes is higher than P threshold , the neighbouring nodes store received the RREQ packet and re-broadcasted the RREQ packet. The neighbouring node adds its ID to the routing path field of the RREQ packet and the class field of the RREQ packet is assigned a type (group-1 or group-2) of neighbouring node. When the destination node receives the first RREQ packet with group-1 and the first RREQ packet with group-2, the destination node selects the last hop of each RREQ packet as its upstream node to be the primary routing paths for tree-0 and tree-1. Then, the destination node sent two route reply (RREP) packets to the source node. The RREP packet carries the following information in its header: iii. Broken Link Maintenance\par In NLTMRP, when a node fails to deliver the data packet to the next hop of the route, it considers the link to be broken and sends a route error (RERR) packet to the source node. When the upstream node receives the RERR packet, it removes the corresponding entry from its routing table and forwards the RERR packet to the source node. If only one of the two routes is broken, the source uses the remaining valid route to deliver data packets. When both routes of the path are broken, the source node initiates the route discovery process. The RERR packet carries the following information in its header: a. Aglorithm2 \section[{Node Ni continues packet transmission. \} else}]{Node Ni continues packet transmission. \} else}\par The simulation was implemented by using NS2 (Network Simulation 2, version 2.35) \hyperref[b30]{[30]}. The simulation modeled a network in a 900 m × 900 m area with varying mobile speed. We used random waypoint model was used as mobility model. In random waypoint model, each node randomly selects the moving direction, and when it reaches to the boundary of simulation area, it bounces back and continues to move. The transmission range was 150 m. The data packet size was 250 bytes. The initial power of each node was 10 J. P threshold was 0.5J. Each simulation was executed for 600sec. The source and destination nodes were randomly chosen and each node was randomly assigned an initial energy. We used constant bit rate (CBR) as the traffic type. In CBR model, the source transmits a certain number of fixed size packets. The parameters used in the simulations are listed as shown below. The performance evaluation metrics used in the simulations were: \section[{Packet Delivery Ratio}]{Packet Delivery Ratio}\par The data packets delivered divided by the data packets expected to be delivered. \section[{Control Overhead}]{Control Overhead}\par The control packets transmitted divided by the data packets delivered. \section[{Packet Delivery Delay}]{Packet Delivery Delay}\par The interval from the time the multicast is initiated to the time the last host finishes its multicasting. \section[{Total Energy Consumption}]{Total Energy Consumption}\par The total consumed Energy of all nodes after data transmission. \section[{Network Lifetime}]{Network Lifetime}\par The duration of the network operation time until the first node failure because of battery depletion at the node.\par IV. \section[{Wireless Simulation}]{Wireless Simulation}\par The Network simulation-2 implementation has following important parts. T time out seconds, and waits for the repair route reply (RREPR) packet to return. The simulation was implemented by using NS2 (Network Simulation 2, version 2.35) \hyperref[b30]{[30]}. The simulation modeled a network in a 900 m × 900 m area with 50 mobile nodes. We used random way point model was used as mobility model. In random waypoint model, each node randomly selects the moving direction, and when it reaches to the boundary of simulation area, it bounces back and continues to move. The mobile speed of each node was from 1 to 25 m/s. The transmission range was 150 m. The data packet size was 250 bytes. The initial energy of each node was 10 J. P(threshold) was 0.15J . Each simulation was executed for 600s. The value in the following simulation figures are the average values of 50 runs. The source and destination nodes were randomly chosen and each node was randomly assigned an initial energy. We used constant bit rate (CBR) as the traffic type.\par V. \section[{Simulation Results}]{Simulation Results}\par In the following, the impact of mobility speed on AODV, AOMDV and NLTMRP is studied. These protocols have been simulated for packet delivery ratio, packet delivery delay, total energy consumption and Network Life Time.\par From Figs. \hyperref[fig_7]{2-5}, we depict the routing performance of three protocols under different mobility speeds. Fig. \hyperref[fig_7]{2} shows the performance of the packet delivery ratio under various mobility speeds. As shown in Fig. \hyperref[fig_7]{2}, the packet delivery ratio decreased with increasing mobility because of more link breaks. Notice that the packet delivery ratio is high when the nodes have low mobility. NLTMRP achieves a much higher packet delivery ratio than AOMDV and AODV because energy is evaluated while establishing of two stable routing paths for multicasting. Thus, the packet delivery ratio of NLTMRP is higher than that of AOMDV and AODV protocol.\par From Fig. \hyperref[fig_8]{3} we depict performance of the packet delivery delay under various mobility speeds. As shown in Fig. \hyperref[fig_8]{3}, as the mobility speed increases, the packet delivery delay also increases. The packet delivery delay of NLTMRP is lower AOMDV and AODV. This is also because energy is evaluated while establishing of two stable routing paths for multicasting.\par From Fig. {\ref 4}, shows the performance of the total energy consumption energy under various mobility speeds. Owing to the mobility of the node making the control overhead increases, it consumes more energy. Therefore the total energy consumption increases with increasing mobility. As observed in Fig. {\ref 4}, the total energy consumption of NLTMRP is lower than that of AOMDV and AODV. This is because of NLTMRP reducing the energy consumption by using dual trees for transmission.\par Fig. {\ref 5} shows the performance of the control overhead under various mobility speeds. As is expected, the control overhead increases as the mobile nodes became more mobile. The reason is that there are more chances for routes to break when the speed of the mobile nodes is faster. Thus, the number of rebroadcasts increased. NLTMRP not only eliminates inefficient nodes to decrease the number of control packets, but also structures dual trees to reduce the number of route reconstructions. Therefore NLTMRP has a lower control overhead than AOMDV and AODV protocol.\par From Fig. 6 shows the performance of the network lifetime at various mobility speeds. From this figure, the network lifetime of NLTMRP outperforms that of AOMDV and AODV. This is because the node residual battery power of NLTMRP is always higher than that of AOMDV and AODV. \section[{Conclusion}]{Conclusion}\par In this paper, we propose a NLTMRP for MANETs. In this scheme, load balance is used to increase the lifetime of a network. In the route discovery, this scheme not only improves the route stability of multicast routing, but also achieves the load balance of data transmission. Therefore the control overhead for route construction and the number of route reconstructions can be decreased. Simulation results show that the packet delivery ratio and the packet delivery delay of the proposed scheme outperform that of AOMDV and AODV. Moreover, the traffic load can be balanced and the network lifetime can be prolonged. NLTMRP is a energy-aware multicast routing protocol. The node with low energy does not selected as a member of multicast tree. NLTMRP improves the route \begin{figure}[htbp] \noindent\textbf{}\includegraphics[]{image-2.png} \caption{\label{fig_2}E}\end{figure} \begin{figure}[htbp] \noindent\textbf{}\includegraphics[]{image-3.png} \caption{\label{fig_3}A}\end{figure} \begin{figure}[htbp] \noindent\textbf{1}\includegraphics[]{image-4.png} \caption{\label{fig_4}1 .E}\end{figure} \begin{figure}[htbp] \noindent\textbf{1}\includegraphics[]{image-5.png} \caption{\label{fig_5}Figure 1 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{2}\includegraphics[]{image-6.png} \caption{\label{fig_7}Figure 2 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{3}\includegraphics[]{image-7.png} \caption{\label{fig_8}Figure 3 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{45}\includegraphics[]{image-8.png} \caption{\label{fig_9}Figure 4 :Figure 5 :E}\end{figure} \begin{figure}[htbp] \noindent\textbf{:} \par \begin{longtable}{P{0.85\textwidth}} Nodeid Distance\\ 2. Routing Table : This table contained the path that\\ was used for the transmission of data. The format\\ of the path table was\\ Src ID DestID Seqno Routeclass Next\textunderscore hop\end{longtable} \par \caption{\label{tab_0}Table :}\end{figure} \begin{figure}[htbp] \noindent\textbf{} \par \begin{longtable}{} \end{longtable} \par \caption{\label{tab_1}}\end{figure} \begin{figure}[htbp] \noindent\textbf{1} \par \begin{longtable}{P{0.5724489795918367\textwidth}P{0.27755102040816326\textwidth}} Simulator\tabcellsep Ns-2.35\\ Routing Protocol\tabcellsep AODV, AOMDV, NLTMRP\\ Simulation Time\tabcellsep 600sec\\ \multicolumn{2}{l}{Number of Nodes 100}\\ \multicolumn{2}{l}{Mobility peed(m/s) 1-25 m/s}\\ Mobility Model\tabcellsep Random way point Model\\ Simulation Area\tabcellsep 900 X 900\\ Node transmission\tabcellsep 150 m\\ Range\tabcellsep \\ Data packet Size\tabcellsep 250 bytes\\ Traffic Type\tabcellsep CBR\end{longtable} \par \caption{\label{tab_3}Table 1 :}\end{figure} \footnote{EEnhancement of Network Life Time Using Binary Tree Based Multicast Routing Protocol for Mobile Ad Hoc Network} \footnote{EEnhancement of Network Life Time Using Binary Tree Based Multicast Routing Protocol for Mobile Ad Hoc Network} \backmatter \begin{bibitemlist}{1} \bibitem[Das et al. ()]{b4}\label{b4} ‘A dynamic core based multicast routing protocol for ad hoc wireless network’. S K Das , B S Manoj , C S R Murthy . \textit{Proc. Third CM Int. Symp. on Mobile Ad Hoc Networking and Computing}, (Third CM Int. Symp. on Mobile Ad Hoc Networking and Computing) 2002. p. . \bibitem[Tsai and Moors]{b36}\label{b36} ‘A Review of Multipath Routing Protocols From Wireless Ad Hoc to Mesh Networks’. Jack Tsai , Tim Moors . \textit{National ICT Australia} NICTA)1/ University of New South Wales \bibitem[Wu et al. (1998)]{b8}\label{b8} \textit{Ad hoc multicast routing protocol utilizing increasing ID-numbers (amris) functional specification'. Internet Draft}, C W Wu , Y C Tay , C K Toh . November 1998. \bibitem[Perkins ()]{b32}\label{b32} \textit{Ad Hoc Networking}, C Perkins . 2001. Addison-Wesley. (3rd ed.) \bibitem[Marina and Das ()]{b33}\label{b33} \textit{Ad hoc On-demand Multipath Distance Vector Routing}, M K Marina , S R Das . 2003. Computer Science Department, Stony Brook University \bibitem[Perkins and Royer (1999)]{b26}\label{b26} ‘Ad-hoc on-demand distance vector routing’. C E Perkins , E Royer . \textit{Proc. Second IEEE Workshop on Mobile Computing System and Application}, (Second IEEE Workshop on Mobile Computing System and ApplicationNew Orleans, LA, USA) February 1999. p. . \bibitem[Sivaram and Manoj ()]{b31}\label{b31} \textit{Adhoc Wireless Networks Architectures and Protocols, Pearson Education}, C Sivaram , B S Manoj . 2005. (2nd ed.) \bibitem[Gowrishankar et al. ()]{b37}\label{b37} ‘Analysis of AOMDV and OLSR Routing Protocols Under Levy-Walk Mobility Model and Gauss-Markov Mobility Model for Ad Hoc Networks’. . S Gowrishankar , T G Subirkumarsarkar , Basa Varaju . \textit{IJCSE) International Journal on Computer Science and Engineering} 2010. 02 p. . \bibitem[Bommaiah et al. (1998)]{b2}\label{b2} E Bommaiah , M Liu , A Mcauley , R Talpade . \textit{AMRoute: ad hoc multicast routing protocol'. Internet Draft}, August 1998. \bibitem[Ballaradie et al. (1993)]{b0}\label{b0} ‘Core based tree (CBT) -an architecture for scalable interdomain multicast routing protocol’. A Ballaradie , J Crowcroft , P Francis . \textit{Proc. ACM SIGCOM}, (ACM SIGCOM) October 1993. p. . \bibitem[Calvert et al. (1995)]{b3}\label{b3} ‘Core selection methods for multicast routing’. K L Calvert , E W Zegura , M J Donahoo . \textit{Proc. Fourth Int. Conf. on Computer Communications and Networks}, (Fourth Int. Conf. on Computer Communications and Networks) September 1995. p. . \bibitem[Sheng et al. (2003)]{b23}\label{b23} ‘Delay sensitive adaptive routing protocol for ad hoc network’. M Sheng , H Li , Y Shi . \textit{Proc. 17th Int. Conf. on Advanced Information Networking and Applications}, (17th Int. Conf. on Advanced Information Networking and Applications) March 2003. p. . \bibitem[Johnson and Maltz ()]{b25}\label{b25} \textit{Dynamic source routing in ad hoc wireless networks: Mobile computing}, D B Johnson , D A Maltz . 1996. Kluwer Publishing Company. p. . \bibitem[Gui and Mohapatra ()]{b12}\label{b12} ‘Efficient overlay multicast for mobile ad hoc networks’. C Gui , P Mohapatra . \textit{Proc. IEEE Wireless Communication and Networking Conf}, (IEEE Wireless Communication and Networking Conf) 2003. 2 p. . \bibitem[Heinzelman et al.]{b27}\label{b27} \textit{Energy efficient routing protocols for micro}, W R Heinzelman , A Chandrakasan , H Baladrishnan . \bibitem[Prasad and Arvind (2013)]{b30}\label{b30} ‘Energy Optimization and Load Balancing using Tree Based Multicast Routing Protocol for Mobile Adhoc Network’. Guru Prasad , Prof Arvind , S . \textit{International Journal of Engineering Research \& Technology (IJERT)} June -2013. 8 (6) . \bibitem[Wu and Tuan (2009)]{b17}\label{b17} ‘Energy saving routing protocol with energy sieving in wireless ad hoc networks’. Y.-C Wu , C.-C Tuan . \textit{Proc. Int. Conf. on Networks Security, Wireless Communications and Trusted Computing}, (Int. Conf. on Networks Security, Wireless Communications and Trusted Computing) April 2009. 1 p. . \bibitem[Singh et al. (1998)]{b15}\label{b15} ‘Energyaware routing in mobile ad hoc networks’. S Singh , M Woo , C S Raghavendra . \textit{Proc. Fourth Annual ACM/IEEE Int. Conf. on Mobile Computing and Networking}, (Fourth Annual ACM/IEEE Int. Conf. on Mobile Computing and Networking) October 1998. p. . \bibitem[Chiang et al. ()]{b9}\label{b9} ‘Forwarding group multicast protocol (FGMP) for multihop, mobile wireless networks’. C Chiang , M Gerla , L Zhang . \textit{Cluster Comput., Spec. Issue Mob. Comput} 1998, 1. (2) p. . \bibitem[Lee et al. (1999)]{b13}\label{b13} S J Lee , M Gerla , C C Chiang . \textit{On demand multicast routing protocol'. Proc. IEEE Wireless Communication and Networking Conf}, September 1999. p. . \bibitem[Merindol et al. ()]{b38}\label{b38} ‘Low Complexity Link State Multipath Routing’. Pascal Merindol , Jean-Jacques Pansiot , Stephane Cateloin . \textit{IEEE/ACM Tranaction on Network} 2009. \bibitem[Mostafa Mostafavi et al. ()]{b35}\label{b35} ‘Maximum Delay Minimization in multipath Routing’. V S Mostafa Mostafavi , Ehsan Hamadani , Rahim Tafazzoli . \textit{8th IEEE Conference on Communication Networks and Services Research}, 2010. \bibitem[Sinha et al. (1999)]{b14}\label{b14} ‘MCEDAR: multicast core extraction distributed adhoc routing’. P Sinha , R Sivakumar , V Bharghavan . \textit{Proc. Wireless Communications and Networking Conf}, (Wireless Communications and Networking Conf) September 1999. p. . \bibitem[Macker and Corson ()]{b5}\label{b5} ‘Mobile ad hoc networking and the IETF’. J P Macker , M S Corson . \textit{ACM SIGMOBILE Mob. Comput. Commun. Rev} 1998. (2) p. . \bibitem[Royer and Perkins ()]{b6}\label{b6} ‘Multicast operation of the ad hoc on demand distance vector routing protocol’. E M Royer , C E Perkins . \textit{ACM MOBICOM}, 1999. p. . \bibitem[Banner and Orda ()]{b39}\label{b39} ‘Multipath routing algorithms for congestion minimization’. R Banner , Orda . \textit{IEEE/ACMTrans. Netw} 2007. \bibitem[Tekaya et al. (2010)]{b34}\label{b34} ‘Multipath Routing with Load Balancing and QoS in Ad hoc Network’. Mohamed Tekaya , Nabil Tabbane , Sami Tabbane . \textit{IJCSNS International Journal of Computer Science and Network Security} August 2010. 10 p. . \bibitem[Wei and Zakhor ()]{b24}\label{b24} ‘Multiple tree video multicast over wireless ad hoc networks’. W Wei , A Zakhor . \textit{IEEE Trans. Circuits Syst. Video Technol} 2007. 17 (1) p. . \bibitem[Devarapalli and Sidhu (2001)]{b10}\label{b10} ‘MZR: A multicast protocol for mobile ad hoc networks’. V Devarapalli , D Sidhu . \textit{Proc. IEEE Int. Conf. on Communications}, (IEEE Int. Conf. on Communications) June 2001. p. . \bibitem[Wang and Gupta (2003)]{b7}\label{b7} ‘On maximizing lifetime of multicast tree in wireless ad-hoc networks’. B Wang , S K S Gupta . \textit{Proc. Int. Conf. on Parallel Processing}, (Int. Conf. on Parallel essing) October 2003. p. . \bibitem[Pearlman et al. (2000)]{b22}\label{b22} ‘On the impact of alternate routing for load balancing in mobile ad hoc networks’. M R Pearlman , Z J Haas , P Sholander , S S Tabrizi . \textit{Proc. First Annual Workshop on Mobile and Ad Hoc Networking and Computing}, (First Annual Workshop on Mobile and Ad Hoc Networking and Computing) August 2000. p. . \bibitem[Baolin and Layuan (2005)]{b1}\label{b1} ‘On the reliability of MAODV in ad hoc networks’. S Baolin , L Layuan . \textit{Proc. IEEE Int. Symp. on Microwave, Antenna, Propagation and EMC Technologies for Wireless Communications}, (IEEE Int. Symp. on Microwave, Antenna, Propagation and EMC Technologies for Wireless Communications) August 2005. 2 p. . \bibitem[Toh et al. ()]{b16}\label{b16} ‘Performance evaluation of battery life-aware routing scheme for wireless ad hoc networks’. C K Toh , H Cobb , D A Scott . \textit{Proc. IEEE Int. Conf. on Communications}, (IEEE Int. Conf. on Communications) 2001. 9 p. . \bibitem[Proc. 33rd Hawaii Int. Conf. on System Sciences ()]{b28}\label{b28} \textit{Proc. 33rd Hawaii Int. Conf. on System Sciences}, (33rd Hawaii Int. Conf. on System Sciences) 2000. 8 p. . \bibitem[Rappaport ()]{b29}\label{b29} T S Rappaport . \textit{Wireless communications: principles and practice}, (Upper Saddle River, NJ) 1995. Prentice-Hall. \bibitem[Dube et al. ()]{b18}\label{b18} ‘Signal stability based adaptive routing (SSA) for adhoc mobile network’. R Dube , C D Rais , K.-Y Wang , S K Tripathi . \textit{J. IEEE Wirel. Commun} 1997. 4 (1) p. . \bibitem[Wang et al. (2005)]{b20}\label{b20} ‘Signal strength-based routing protocol for mobile ad hoc networks’. S Y Wang , J Y Liu , C C Huang , M Y Kao , Y H Li . \textit{Proc.IEEE Int. Conf. on Advanced Information Networking and Applications}, (.IEEE Int. Conf. on Advanced Information Networking and Applications) March 2005. p. . \bibitem[Lee and Gerla (2001)]{b21}\label{b21} ‘Split multipath routing with maximally disjoint paths in ad hoc networks’. S J Lee , M Gerla . \textit{Proc. IEEE Int. Conf. on Communications}, (IEEE Int. Conf. on Communications) June 2001. p. . \bibitem[Rishiwal et al. (2008)]{b19}\label{b19} ‘Stable and energy efficient routing for mobile ad hoc networks’. V Rishiwal , A Kush , S Verma . \textit{Proc. Int. Conf. on Information Technology: Next Generations}, (Int. Conf. on Information Technology: Next Generations) April 2008. p. . \bibitem[Garcia-Luna-Aceves and Madruga ()]{b11}\label{b11} ‘The coreassisted mesh protocol’. J J Garcia-Luna-Aceves , E L Madruga . \textit{IEEE J. Sel. Areas Commun} 1997. 17 (8) p. . \bibitem[The Network simulator 2-35]{b40}\label{b40} \textit{The Network simulator 2-35}, \url{http://www.isi.edu/nsnam/ns/index.html} \end{bibitemlist} \end{document}