21-12-2012, 03:17 PM
Optimizing Handover Performance in Host Identity Protocol
Optimizing Handover Performance.pdf (Size: 353.31 KB / Downloads: 95)
INTRODUCTION
Many devices use several network interfaces – even at the same time. This ability is called multi-homing. TCP/IP does not support either mobility or multi-homing. The shortcomings of TCP cause problems when it is used on mobile devices. Due to the widespread deployment of TCP/IP, the common Internet infrastructure which relies on the Internet Protocol (IP) and several existing applications which use TCP/IP, the use of the TCP/IP protocol suite on mobile devices is still nevertheless desirable. However, various challenges must be solved before TCP/IP is fit for use with mobile devices.
A host and its location are identified using Internet Protocol (IP) addresses in the current Internet architecture. However, IP addresses can serve only as short-term identifiers because a considerable amount of hosts are portable devices and they change their IP addresses when moved from one network to another. Short-term identifiers disrupt long-term transport layer connections, such as Internet phone calls, and make locating the peer host more difficult.
HOST IDENTITY PROTOCOL
The Host Identity Protocol (HIP) protocol is
described in the HIP base draft. The Host Identity
Protocol provides mobility support for the TCP/IP
protocol suite. It is currently being standardized by the
IETF. Two IETF groups, the HIP working group and the
HIP research group, are working on the protocol details.
The goal of HIP is to provide end-host mobility in a safe
and decentralized fashion. In contrast to mobile IP, no
home agents or third party hosts are needed to support
basic host mobility. HIP provides host authentication and
secure communication for mobile hosts. The HIP protocol
architecture is described in RFC 4423.
PROPOSED APPROACH
PROBLEM STATEMENT: This project deals
with the optimization of micro-mobility handover
performance in Host Identity Protocol (HIP) in micro
mobility environment. The main aim is to reduce the
handover that arises when a mobile node moves with in
the same domain
PROPOSED SOLUTION:
The solutions which
are present until now do not provide a sufficient micromobility
management solution for HIP. We propose a HIP
micro-mobility solution with the advantages of keeping
the IP addresses of the Mobile Nodes stable in a given
domain. The mobility entities in our architecture are
responsible for tracking the movements of the mobile host
and the exchange of the required mobility signaling on
behalf of the mobile node.