DMAP-FR: Integrated Mobility and Service Management with Failure Recovery Support for Mobile IPv6 Systems. Greg Bilodeau Mike Reed. What is DMAP-FR?. An extension of Dynamic Mobility Anchor Points (DMAP) DMAP is an extension of Hierarchical Mobile IPv6 (HMIPv6)
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
An extension of Dynamic Mobility Anchor Points (DMAP)
DMAP is an extension of Hierarchical Mobile IPv6 (HMIPv6)
HMIPv6 is an extension of Mobile IPv6
Mobility in IPv6 Networks.
MIPv6 is expected to have wide deployment in the future for all-IP mobile systems.
More mobile apps will access multimedia and data services over IP
Specialized "foreign agent" routers not needed.
Support for route optimization fundamental part of protocol.
Packets sent to mobile node (MN) sent using IPv6 routing header rather than IP encapsulation
Dynamic home agent (HA) discovery mechanism returns single reply to the mobile node.
Does not solve local or hierarchical forms of mobility management.
Effective mobility and service management schemes to reduce network traffic needed.
Fault tolerance for service continuity despite network router failures.
Allows local mobility handling.
Designed to reduce the amount of signalling traffic between the MN and home agent (HA) and correspondent nodes (CNs).
Utilizes local home agents called mobile anchor points (MAPs).
Unlike FA in IPv4, MAPs not required on every subnet.
Limit the amount of IPv6 signalling traffic outside the local domain
Allow MNs to hide their location from CNs.
MN may chose which MAP (or MAPs) to associate with.
Static domain in terms of number of subnets covered.
Single point of failure.
While mobility is addressed, service and performance management is not considered.
Integrated mobility and service management.
MN not only determines which MAP to bind to, it determines which access router (AR) acts as a MAP.
MAP binding based on both mobility and service requirements of the specific MN.
Location handoff: MN moves across subnet boundary
Service handoff: MN moves across DMAP domain boundary
MAP domain size: number of subnets in region covered by the MAP
Choosing a MAP "further" from the MN decreases the number of service handoffs, but increases the triangular routing overhead and location handoffs
Choosing a MAP "closer" to the MN reduces the intra-subnet routing, but increases the frequency of service handoffs
MN must be capable of collecting required statistical information.
Goal is the minimization of "communication cost" per time unit.
F(Mark(Xs)+1) returns the number of hops between the current subnet and the DMAP separated byMark(Xs)+1 subnets.
The argument of the F(x) function is added by 1 to satisfy the initial condition that Mark(Xs) = 0 in which the DMAP has just moved into a new service area, so at the first subnet crossing event, the distance between the DMAP and the subnet is one subnet apart
As MN must inform HA and all N client nodes of new RCoA
Calculating average communication overhead
Includes delays between CN and DMAP, DMAP to AR of current subnet, and wireless link between AR and MN
Calculating average location change overhead
Total communication cost per time unit:
Dynamic Mobility Anchor Points – Fault Recovery
The addition of fault tolerance to DMAP.