Scribd
Upload
2 views

MC module5

Mobility management in networks consists of location management and handoff management, facilitating user connection as they move. Mobile IPv4 and Mobile IPv6 are protocols for macromobility, with IPv6 offering enhanced features like address auto-configuration and route optimization. FMIPv6 enhances MIPv6 by allowing predictive handovers and faster binding updates, improving the efficiency of mobile connections during transitions between networks.

Uploaded by

SEB212Sanchi Dilip Deshmukh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

MC module5

Mobility management in networks consists of location management and handoff management, facilitating user connection as they move. Mobile IPv4 and Mobile IPv6 are protocols for macromobility, with IPv6 offering enhanced features like address auto-configuration and route optimization. FMIPv6 enhances MIPv6 by allowing predictive handovers and faster binding updates, improving the efficiency of mobile connections during transitions between networks.

Uploaded by

SEB212Sanchi Dilip Deshmukh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 33

Mobility management consists of two components:

• location management and


• handoff management.

Location management enables the network to discover the current point of attachment of the mobile user
so that a new connection can be established when a new multimedia call arrives.
Handoff management, often known as terminal mobility, allows the network to maintain the user’s
connection binding as the mobile node moves from one attachment point to another in the network

Network layer mobility can be categorized into two types: macromobility and micromobility.
The macromobility mechanism takes care of global mobility where the mobile moves between
administrative domains.

We describe two types of network layer macromobility, namely Mobile IPv4 and
Mobile Ipv6.
IPv6’s increased address space and inherent support for security and auto configuration have made it an attractive candidate to
support mobility for the next-generation Internet.
Mobile IPv6 is the protocol to support mobility for IPv6 nodes.
Since address auto configuration is a standard part of MIPv6, the MN will always obtain a CoA routable to a foreign network.
Thus, there is no need to have a foreign agent in MIPv6.
When the mobile node moves to a new foreign network, it acquires a temporary care-of-address using stateless auto
configuration or via DHCPv6
Figure shows the functional components of Mobile IPv6.
Unlike Mobile IPv4, the visited networks do not have any foreign agents.
MIPv6’s route optimization feature also enables direct data delivery from the correspondent host (CN) to the mobile node.
Although Mobile IPv6 is defined as a network layer approach and one needs to install an MIPv6 stack so as to support mobility
in an IPv6 space, any standard operating system will in future come with inherent Mobile IPv6 support.
While Mobile IPv6 provides a way of making sure of the uniqueness
of an address as a mobile moves to a new router space, it also adds
delay to the binding update and binding acknowledgement as in Mobile IPv4.

Route optimization is a standard feature of MIPv6, so there is no need for the


CH to be equipped with additional software.

The MN sends a binding update directly to CH and makes use of the home
address destination option as part of the binding update.

This allows the correspondent host to keep a binding cache that


maps the care-of address of the mobile to the mobile’s home address.

For the ongoing traffic, this avoids triangular routing, and thus packets
from the CH to the MN need not be encapsulated but are sent directly to
the MH with its CoA as the source route.

However, when a new CH needs to communicate with the mobile for the
first time, the packets from the CH need to travel to the home agent
and be tunneled to the mobile host.

The mobile moves during the packet transfer process, the subsequent
packets are tunneled directly to the mobile host without being routed via
the home agent
The FMIPv6 protocols work in conjunction with the existing MIPv6 stack.
Figure 2.16 shows the interaction among several network elements.

The predictive operation of FMIPv6.


The mobile host sends a router solicitation for a proxy (RtSolPr) message
to its default access router (pAR) in order to obtain information related to
the link layer addresses of the neighboring access points discovered during
the layer 2 scanning process, and the prefixes associated with the neighboring
access router (nAR).
The current access router (pAR) communicates with the nAR using protocols
such as Candidate Access Router Discovery (CARD) (Liebsch et al., 2005) to
obtain the relevant information about the neighboring network elements.
The pAR serving the user responds with a proxy router advertisement (PrRtAdv)
containing the requested information, thus allowing the mobile host to perform
address autoconfiguration prior to its movement to the new network.
The host, after formulating a prospective new CoA, sends a fast binding update (FBU)
to its default router instructing it to tunnel packets addressed to its old CoA (oCoA)
towards its new CoA (nCoA).
The access router currently serving the host (pAR) starts buffering newly arriving packets
with the CoA as their destination and exchanges handover initiate (HI) and handover
acknowledge (HAck) messages with the nAR to initiate the process of the MH’s handover.
This HI/HAck message exchange can also serve for validation of the nCoA already
formed by the host.
The pAR responds to the MH with a fast binding acknowledge (FBack) message on
both links (old and new) and starts the tunneling of buffered and arriving data to the nCoA.

You might also like