\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={Adaptive Routing Based on Delay Trusted Routing in Adhoc 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{2011-03 2011-02-18 (revised: March 2011 18 February 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-03 2011-02-18}
\title{Adaptive Routing Based on Delay Trusted Routing in Adhoc 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]{Dr. T.K.Shaik  Shavali}

             \author[2]{T. Bhaskara  Reddy}

             \affil[1]{  S.K.UNIVERSITY}

\renewcommand\Authands{ and }

\date{\small \em Received: 13 January 2011 Accepted: 3 February 2011 Published: 18 February 2011}

\maketitle


\begin{abstract}
        


Existing network hardware is constantly being improved and new communication technology continues to be developed. Together with the trend that computing hardware becomes smaller and portable, this network technology progress has led to dynamic networks. Next generation wireless networks are characterized as heterogeneous networks, particularly in terms of its underlying technology. One of the challenges of these heterogeneous networks is to manage handoff. Mobile IP is chosen for managing the handoff to accommodate the all-IP vision of the future interconnected networks. However, the handoff management of the mobile IP is mainly for data services where delay is not of a major concern. Therefore, it would be considerable challenge to achieve low latency handoff for real-time services. In this paper, we propose a multicasting scheme for delay-sensitive applications.

\end{abstract}


\keywords{MobileIP, Handoff, Heterogeneous Network, Mobile stations, Quality of Service.}

\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
n the near future, a large number of Mobile Stations (MSs) will be equipped with multiple radio interfaces for wireless access to the Internet. A multi-mode MS with multiple air interfaces (cellular interface, Bluetooth, IEEE 802.11 and IEEE 802.16 etc) and different data rates will be able to access cellular Base Stations (BSs), WLAN or WMAN Access Points (APs). In this scenario, the integration of multi-hop ad hoc communications with infrastructure based (or single-hop) wireless networks, such as wireless WANs (e.g., 2.5G, 3G, and 4G), wireless LAN (e.g., IEEE 802.11 a/b/e/g and HiperLAn/2) and wireless MANs (e.g., IEEE 802. \hyperref[b15]{16}), is fundamental to improving the coverage and performance of the integrated network \hyperref[b2]{[3]}. In addition, multi-hop communications can be used to increase the utilization and capacity of a BS by decreasing the co-channel interference via lowering the transmission power either of the BS or of the MSs \hyperref[b4]{[5]}  \hyperref[b8]{[9]}.Also, the integration can be useful in achieving load-balancing by forwarding part of the traffic from an overloaded cell to a free neighboring cell \hyperref[b5]{[6]}  \hyperref[b6]{[7]}. From the protocol stack perspective, the network layer is the lowest possible layer where the convergence of heterogeneous wireless systems can be developed. Furthermore, the desire to extend the great success of the Internet Protocol (IP) from the wired world to wireless leads to an all-IP vision \hyperref[b2]{[3]}. So far, the IP is the best integration technology for heterogeneous networks and there is currently no foreseeable alternative to the IP \hyperref[b3]{[4]}. To allow for seamless handoff to take place in IP-based heterogeneous networks, the IP must support users' mobility. In an effort to do that, the Internet Engineering Task Force (IETF) has developed the mobile IP standard to support mobility in IP-based networks \hyperref[b4]{[5]}. In recent years, there has been a considerable amount of works that address the mobile IP-based handoff problem in heterogeneous networks \hyperref[b1]{[2]}, \hyperref[b2]{[3]}, \hyperref[b5]{[6]}- \hyperref[b8]{[9]}. Since data packets could be lost during the latency period, mobile IP-based handoff may not meet the quality-of-service (QoS) requirements for real time voice applications. Even though, mobile IP describes a scheme to recover the lost packets from the old foreign agent to the new one, this process takes some time as the signal experiences a random delay when it travels through the network. This makes the latency even longer. For non-real time services, this additional delay will not create a major problem. However, for real time services, this will dramatically degrade the QoS requirements. This problem can be solved if multicasting is employed. In this case, data packets are sent to the neighboring foreign agents as soon as the Received Signal Strength (RSS) of the mobile host goes below a certain threshold level. When this occurs, the data packets are stored in the buffer at the new foreign agent, and in the process, the latency can be reduced.\par
In this paper, we consider a multicasting scheme to solve the handoff latency problem in heterogeneous networks. The proposed handoff technique offers two main advantages: a. It reduces the handoff latency in hybrid networks, b. Recovers lost packets during the handoff process, which increases the system throughput. 
\section[{II. MOBILE IP AND HANDOFFS}]{II. MOBILE IP AND HANDOFFS}\par
First, second-and third-generation mobile systems depended on the employment of the radio spectrum that was either unlicensed (available for public use) or licensed for use by a very small number of service providers and network operators in each region. 
\section[{I}]{I}\par
Differences in bandwidth and coverage areas have led to the necessity of developing multi-network interface devices (terminals) that are capable of using the variety of different network services provided. 
\section[{1) Mobile IP}]{1) Mobile IP}\par
Mobile IP is an Internet protocol, defined by the Internet Engineering Task Force (IETF) that allows users keep the same IP address, and stay connected to the Internet while roaming between networks. The key feature of Mobile IP design is that all required functionalities for processing and managing mobility information are embedded in well-defined entities, the Home Agent (HA), Foreign Agent (FA), and Mobile Nodes (MNs) \hyperref[b0]{[1,}\hyperref[b1]{2]}. When a MN moves from its Home Network (HN) to a Foreign Network (FN), the correct delivery of packets to its current point of attachment depends on the MN's IP address, which changes at every new point of attachment. Therefore, in order to guarantee packets delivery to the MN, Mobile IP allows the MN to use two IP addresses: The Home address, which is static and assigned to the MN at the home network; and the Care-of-Address (CoA), which represents the current location of the MN \hyperref[b1]{[2]}. One of the main problems that face the implementation of the original Mobile IP is the Triangle Routing Problem. When a CN sends traffic to the MN, the traffic gets first to the HA, which encapsulates this traffic and tunnels it to the FA. The FA de-tunnels the traffic and delivers it to the MN. The route taken by this traffic is triangular in nature, and the most extreme case of routing can be observed when the CN and the MN are in the same subnet \hyperref[b3]{[4,}\hyperref[b4]{5]}.\par
In mobile IP, two network entities are defined to support users mobility namely; the home agent and the foreign agent. These two agents periodically send advertisement messages to their corresponding networks (i.e., home and foreign networks) to acknowledge the mobile of its present location. Based on these advertisement messages, and the present location of the mobile host, the mobile host decides whether it belongs to its home network or to a new foreign network. If the mobile host discovers that it has migrated to a new foreign network, it sends a registration request to the corresponding new foreign agent to obtain a care-of-address. Also the foreign agent registers the new address (i.e., new location) with the mobile host home agent. After this process, any data packets that are received at the mobile's home network will be encapsulated with a new IP address and tunneled to the new foreign agent to which the mobile host resides. The foreign agent (at the other end of the tunnel) takes care of the de-encapsulation of the arriving data packets, and then forwards them to the mobile host using the new IP address. In the same way, if the mobile host transmits data packets to its correspondent host, it uses the foreign agent for the tunneling process to forward these data packets to the home agent for subsequent transmission to the correspondent host. 
\section[{2) Classification of Handoffs}]{2) Classification of Handoffs}\par
In principle, each mobile terminal (node) is, at all times, within range of at least one network access point, also known as a base station. The area serviced by each base station is identified as its cell. The dimensions and profile of every cell depend on the network type, size of the base stations, and transmission and reception power of each base station. Usually, cells of the same network type are adjacent to each other and overlap in such a way that, for the majority of time, any mobile device is within the coverage area of more than one base station. Cells of heterogeneous networks, on the other hand, are overlaid within each other. Therefore, the key issue for a mobile host is to reach a decision from time to time as to which base station of which network will handle the signal transmissions to and from a specific host and handoff the signal transmission if necessary. We classify handoffs based on several factors as shown in Fig.  {\ref 1}. No longer is the network type the only handoff classification factor. Many more factors constitute categorization of handoffs including the administrative domains involved, number of connections and frequencies engaged. The following are categorization factors along with the handoff classifications that are based on them. 
\section[{Figure1-Hierarichal Classification of Handoff}]{Figure1-Hierarichal Classification of Handoff}\par
Handoffs can be classified as either horizontal or vertical. This depends on whether a handoff takes place between a single type of network interface or a variety of different network interfaces.\par
Horizontal Handoff: The handoff process of a mobile terminal between access points supporting the same network technology. For example, the changeover of signal transmission (as the mobile terminal moves around) from an IEEE 802.11b base station to a geographically neighboring IEEE 802.11b base station is considered as a horizontal handoff process.\par
Vertical Handoff: The handoff process of a mobile terminal among access points supporting different network technologies. For example, the changeover of signal transmission from an IEEE 802.11b base station to an overlaid cellular network is considered a vertical handoff process. 
\section[{III. SYSTEM ARCHITECTURE}]{III. SYSTEM ARCHITECTURE}\par
The proposed interconnection architecture using mobile IP is shown in Fig.  {\ref 2}. The following are the network parameters and assumptions used in our handoff technique:\par
1. The home agent (HA), the foreign agents (FAs) and the correspondent host (CH) are interconnected through Internet 2. FAs are connected to the Internet through a wireless or a wired medium with large bandwidth. 3. The CH can be a fixed or mobile host.\par
The time taken to switch from the home agent of the mobile user to the new foreign agent is known as the mobile IP handoff latency. In addition to this handoff latency if the mobile host enters into a new foreign agent (from another foreign agent) during the tunneling process between the home agent and the old foreign agent, and before registering with the new foreign agent, data packets destined to the mobile host will be lost. These packets will then be retransmitted leading to an increase in the overall system delay.\par
Figure2-Proposed IP-based handoff architecture.\par
In delay-sensitive applications, handoff latency can cause serious degradation in the quality of the underlying application. As a result of the frequent handoffs, this handoff latency becomes a major problem if the coverage area of the sub-networks gets smaller. Recent works on the existing problems of the handoff latency of mobile IP based networks and possible solutions can be found in \hyperref[b11]{[12]}- \hyperref[b13]{[14]}. 
\section[{IV. PROPOSED IMPROVEMENT IN LATENCY 1) Improvement in Registration Time}]{IV. PROPOSED IMPROVEMENT IN LATENCY 1) Improvement in Registration Time}\par
The improvement in Registration Time is achieved by starting to forward data packets after a small fixed delay (termed as the 'Fixed Registration Delay') following the Registration Request from the MH to the new FA through the new AP/BS. That is, data packets will not wait for the registration process to be completed. Given the fact that the new FA has data packets stored in its buffer, it can start sending these packets to the MH immediately after receiving the Registration Request from the MH. This, in turn, will reduce the total handoff latency and the requirement of large buffer capacity at the FA. To improve the probability of packet loss during the handoff process, we propose a simple modification to the standard mobile IP. In that, the new FA can directly send the Binding Update to the CH instead of sending it to the HA. This of course requires the CH to be notified earlier about the new point of attachment of the MH. This modification is shown to assist in reducing the number of data packets forwarded to the old FA, which in turn reduces the probability of packet loss during the handoff process. 
\section[{2) Improvement in Packet Reception Time}]{2) Improvement in Packet Reception Time}\par
The main contributor to the Packet Reception Time is the time required for transmitting the data packets to the MH. This time is mainly dependent on the packet size and the transmission data rate. For low data rate applications, such as voice communications, the transmission takes a significant amount of time. In this case, the Packet Reception Time will have a significant effect on the overall handoff latency. In our scheme, the network will adjust the packet size according to the application data rate. Therefore, the packet size will be small (or large) depending on the transmission data rate of the underlying application.\par
Note that the use of smaller packet size has an impact on the amount of packet lost. A smaller packet size results in a short packet transmission time. Hence, the duration of which packet loss occurs also gets smaller \hyperref[b2]{[3]}. Since our focus is on the handoff latency and not on the system throughput, we have not considered the effect of packet loss here. For more details on the system throughput and probability of packet loss, the reader is referred to \hyperref[b14]{[15]}. Even though the proposed adaptive packet size technique may lead to a large reduction in the handoff latency, lowering the packet size will have an impact on the associated transmission are accompanied with a considerably large header size. However using header compression techniques, this problem can be greatly eliminated. 
\section[{V. RESULT OBSERVATION}]{V. RESULT OBSERVATION}\par
Results have been for the handoffs in a network model to observe the distribution of handoff latency using the standard mobile IP multicasting technique compared to our proposed multicasting technique.    
\section[{VI. CONCLUSIONS}]{VI. CONCLUSIONS}\par
Mobility is the most important feature of a wireless cellular communication system. Usually, continuous service is achieved by supporting handoff (or handover) from one cell to another. Handoff is the process of changing the channel (frequency, time slot, spreading code, or combination of them) associated with the current connection while a call is in progress. Mobile IP signal flows to reduce the handoff latency in heterogeneous networks with frequent handoffs. In the first modification, we proposed a multicasting scheme where the new foreign agent can only wait for a fixed time for the registration time process to be completed, and after which it can send data packets to the mobile host. The second approach implements a variable packet size depending on the underlying application. \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 3 .}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 4 .}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 5 .}\end{figure}
 			\footnote{March 2011Adaptive Routing Based on Delay Trusted Routing in Adhoc Network ©2011 Global Journals Inc. (US)} 			\footnote{March 2011©2011 Global Journals Inc. (US)} 			\footnote{March 2011©2011 Global Journals Inc. (US)} 		 		\backmatter  			 			 			  				\begin{bibitemlist}{1}
\bibitem[Wu et al. (2002)]{b6}\label{b6} 	 		‘A Seamless handoff Approach for Mobile IP Protocol for Mobile Wireless Networks’.  		 			W Wu 		,  		 			W Chen 		,  		 			H Liao 		,  		 			F F Young 		.  	 	 		\textit{IEEE Tran. on Consumer Elect}  		May 2002. p. .  	 
\bibitem[Valko ()]{b1}\label{b1} 	 		‘Cellular IP: A New Approach to Internet MS Mobility’.  		 			A G Valko 		.  	 	 		\textit{ACM Com. comm. Rev}  		1999.  	 
\bibitem[Feng and Reeves ()]{b13}\label{b13} 	 		‘Explicit Proactive Handoff with Motion Prediction for Mobile IP’.  		 			F Feng 		,  		 			D Reeves 		.  	 	 		\textit{IEEE Wireless Communications and Networking Conference},  				2004. 2004. p. .  	 
\bibitem[Wu et al. ()]{b4}\label{b4} 	 		‘Integrated Cellular and Ad hoc Relaying Systems: iCAR’.  		 			H Wu 		,  		 			C Qiao 		,  		 			S De 		,  		 			Q Tonguz 		.  	 	 		\textit{IEEE Journal}  		2001. 19  (10)  p. .  	 	 (Selected Areas in Communications) 
\bibitem[Perkins ()]{b8}\label{b8} 	 		‘IP Mobility Support’.  		 			C Perkins 		.  		 \url{http:H/www.ietf.org/rfc/rfc2002.txt}  	 	 		\textit{IETF RFC}  		2002. Oct. 1996.  	 
\bibitem[Sharma et al. (2004)]{b11}\label{b11} 	 		‘Low-Latency Mobile IP Handoff for Infrastructure-Mode Wireless LANs’.  		 			S Sharma 		,  		 			N Zhu 		,  		 			T Chiueh 		.  	 	 		\textit{IEEE Journal on Selected Areas in Communications}  		May 2004. 22  (4)  p. .  	 
\bibitem[Ye et al. (2002)]{b5}\label{b5} 	 		‘Mobile IP Handoff between Hybrid Networks’.  		 			M Ye 		,  		 			H Liu 		,  		 			Zhang 		.  	 	 		\textit{PIMRC 2002. Proc. of the 13th IEEE International Symposium},  				Sept. 2002. p. .  	 
\bibitem[Lin and Hsu ()]{b3}\label{b3} 	 		‘Multihop Cellular: A New Architecture for Wireless Communications’.  		 			Y.-D Lin 		,  		 			Y.-C Hsu 		.  	 	 		\textit{INFOCOM}  		2000. IEEE.  (3)  p. .  	 
\bibitem[Berezdivin et al. (2002)]{b7}\label{b7} 	 		\textit{Next-Generation Wireless Communications Concepts and Technologies},  		 			R Berezdivin 		,  		 			R Breinig 		,  		 			R Topp 		.  		Mar. 2002. IEEE Communications Magazine. p. .  	 
\bibitem[Aggelou and Tafazolli ()]{b2}\label{b2} 	 		‘On the relaying capability of nextgeneration GSM cellular networks’.  		 			N Aggelou 		,  		 			R Tafazolli 		.  	 	 		\textit{IEEE Personal Communications}  		2001.  (1) .  	 
\bibitem[Sarikaya (2000)]{b12}\label{b12} 	 		‘Packet Mode in Wireless Networks: Overview of Transition to Third Generation’.  		 			B Sarikaya 		.  	 	 		\textit{IEEE Communications Magazine}  		Sept. 2000. 38  (9)  p. .  	 
\bibitem[Min-Hue et al. ()]{b10}\label{b10} 	 		‘Performance Analysis of TCP/UDP During Mobile IP Handoffs’.  		 			Y Min-Hue 		,  		 			W Zhe-Wei 		,  		 			Z Hui-Min 		,  		 			L Yu 		.  	 	 		\textit{International Conference on Info-tech and Infonet},  				 (Beijing)  		2001. 2 p. .  	 
\bibitem[Hossain ()]{b16}\label{b16} 	 		\textit{Performance Improvement of Mobile IP-Based Handoff between WLAN and GPRS Networks},  		 			M Hossain 		.  		2004.  		 			Dept. of Electrical and Computer Engineering, Concordia University 		 	 	 (Master Thesis) 
\bibitem[Perkins (2001)]{b0}\label{b0} 	 		 			C E Perkins 		.  		\textit{Revised, IETF Internet Draft, draft-ietf-mobile-rfc2002-bis-08.txt},  				Sept. 2001.  	 	 (IP Mobility Support for IPV4) 
\bibitem[Kim and Copeland (2003)]{b15}\label{b15} 	 		‘TCP for Seamless Vertical Handoff in Hybrid Mobile Data Networks’.  		 			S Kim 		,  		 			J Copeland 		.  	 	 		\textit{Proc. of the IEEE Globecom},  				 (of the IEEE Globecom)  		2003. Dec. 2003. p. .  	 
\bibitem[Yu et al. (2003)]{b14}\label{b14} 	 		‘The Handoff Schemes in Mobile IP’.  		 			L Yu 		,  		 			Y Min-Hua 		,  		 			Z Hui-Min 		.  	 	 		\textit{IEEE Vehicular Technology Conference, VTC-2003 Spring},  				Apr. 2003. p. .  	 
\bibitem[Park et al. ()]{b9}\label{b9} 	 		‘Vertical Handoff Procedure and Algorithm between IEEE 802.11 WLAN and CDMA Cellular Network’.  		 			H Park 		,  		 			S Yoon 		,  		 			T Kim 		,  		 			J Park 		,  		 			M Do 		,  		 			J Lee 		.  	 	 		\textit{LNCS)}  		2003.  (2524)  p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
