HMIPv6:

Hierarchical
MIPv6
Houssem
Alayet

2016 - 2017

Planning

Overview of Mobile IP
HMIPv6
HMIPv6 Reference Architecture
HMIPv6 Operation
Performance Comparison of MIPv6, HMIPv6,
RRMIPv6
HMIPv6 Disadvantages
Conclusion

Mobile IP
In MIPv6 every
mobile node is
identified by two
addresses:
Home Address (HA)
Care of Address
(CoA)

Every time MN
visits Foreign
network it sends
BU to HA.
CN also maintains
binding cache to
solve the

Source: P. Reinbold, O. Bonaventure, IP micro

mobility protocols

HMIPv6
HMIP is an extension to Mobile IP for
micromobility Management
To Reduce the amount of signaling
between the Mobile Node, its
Correspondent Nodes, and its Home
Agent.
To Improve the handover latency

HMIPv6: Terminology Used

Access Router (AR): The AR is the Mobile
Node's default router.
Mobility Anchor Point (MAP): A Mobility
Anchor Point is a router located in a network
visited by the mobile node.
Regional CareofAddress (RCoA): An RCoA
is an address obtained by the mobile node
from the visited network.
On Link CareofAddress (RCoA): The LCoA
is the onlink CoA configured on a mobile
node's interface based on the
prefix
advertised by its default router.
Source:
Local
Binding
Update
(LBU):
TheIPv6MN
H. Soliman,
C. Casteluccia, K.EI
Malki, and L. Bellier.
"Hierarchical Mobile
Mobilitysends
Management (HMIPv6), RFC 4140.
a Local Binding Update to the MAP in order to

HMIPv6 Reference Architecture

H
A

C
N

RCo
A

AR1
LCoA
1

MA
P

AR
2

LCoA
2

Moveme
nt
Adapted from: H. Soliman, C. Casteluccia, K.EI Malki, and L. Bellier. "Hierarchical Mobile IPv6 Mobility
Management (HMIPv6), RFC 4140.

HMIPv6 Operation
HMIPv6 involves three
phases:
MAP Discovery
MAP Registration
Packet Forwarding

Mobility Anchor Point (MAP)

Discovery
Discovery is accomplished using a new MAP
option in Router Advertisement.
MAP Optin*

*Source: H. Soliman, C. Casteluccia, K.EI Malki, and L. Bellier. "Hierarchical Mobile IPv6 Mobility
Management (HMIPv6), RFC 4140.

Mobility Anchor Point (MAP)

Discovery
HMIPv6 offers two choices:
Static Configuration
Dynamic MAP Discovery
MN Operation
After processing the MAP option, the MN
obtains MAP IP address
Obtains the Distance of MAP from
Current AR
Verifies the Life time, if it is nonzero
then select the MAP with highest
preference value

Mobility Anchor Point (MAP)

Registration
MN Operation (1)
MN needs to configure two CoA: an RCoA on the
MAP link and onlink CoA. RCoA is formed using
the prefix advertised in the MAP option
MN creates a binding between the RCoA and
LCoA at the MAP
MN sends LBU to newly discovered MAP, LBU
format* is:

*Source: H. Soliman, C. Casteluccia, K.EI Malki, and L. Bellier. "Hierarchical Mobile IPv6 Mobility
Management (HMIPv6), RFC 4140.

Mobility Anchor Point (MAP)

Registration
MAP Operation
MAP performs a DAD for RCoA
MAPS Sends a Binding Acknowledge (BAck) to
MN which is identical to MIPv6 BAck.

MN Operation (2)
MN sends binding update to its HA and active
CNs with RCoA as its source address and HA,
CNs address as destinate address
Lifetime of the binding update sent to HA, CNs
must not be greater than the Lifetime in BAck
received from the MAP

Packet Forwarding
A bidirectional tunnel between the mobile
node and the MAP is established
All packets
sent by
the mobile
node
are tunneled
to the MAP.
LCo
A

MAP
IP

RCo
A

Peers
IP

All packets destined to the mobile node's

RCoA are
intercepted by the MAP and
tunneled to the mobile node's LCoA.
MAP
IP

LCo
A

Peers IP
RCoA

HMIPv6 Working Mechanism

H
A

C
N

RtAd
v

A
R

MA
P

A
R

HMIPv6 Working Mechanism

H
A

C
N

MA
P

RtAd
v

A
R

A
R

HMIPv6 Working Mechanism

H
A

C
N

MA
P

A
R
Configure
LCoA and
RCoA

A
R

HMIPv6 Working Mechanism

H
A

C
N

MA
P

LBU

A
R

A
R

HMIPv6 Working Mechanism

H
A

C
N

LBU

A
R

MA
P

A
R

HMIPv6 Working Mechanism

H
A

C
N

Perform DAD on
RCoA

A
R

MA
P

A
R

HMIPv6 Working Mechanism

H
A

C
N

BAc
k

A
R

MA
P

A
R

HMIPv6 Working Mechanism

H
A

C
N

MA
P

BA
ck

A
R

A
R

HMIPv6 Working Mechanism

H
A

C
N

RCoA
Tunnel between LCoA
and MAP IP address

A
R
LCo
A

MA
P

A
R

HMIPv6 Working Mechanism

H
A

C
N

RCoA
Tunnel between LCoA
and MAP IP address

LCo
A

B
U

A
R

MA
P

A
R

HMIPv6 Working Mechanism

H
A BU

BU

RCoA
Tunnel between LCoA
and MAP IP address

A
R
LCo
A

MA
P

A
R

C
N

HMIPv6 Working Mechanism

H
A

Tunnel between LCoA

and MAP IP address

C
N

RCo
A

A
R
LCo
A

Moveme
nt

MA
P

A
R

HMIPv6 Working Mechanism

H
A

C
N

RCo
A

MA
P

A
R

Movement is transparent to
HA, CN

A
R
Configure
only
New
LCoA and
bind
with
MAP

Performance Comparison of MIPv6,

HMIPv6, RRMIPv6
Handoff
Latency

Network
Topology

*Source: L. Osborne, A. A. Hamid, R. Ramadugu, A Performance Comparison of Mobile IPv6, Hierarchical

Mobile IPv6, and Mobile IPv6 Regional Registrations

Performance Comparison of MIPv6,

HMIPv6, RRMIPv6
Impact of Handoff rate on outside domain
signaling load

*Source: L. Osborne, A. A. Hamid, R. Ramadugu, A Performance Comparison of Mobile IPv6, Hierarchical

Mobile IPv6, and Mobile IPv6 Regional Registrations

Performance Comparison of MIPv6,

HMIPv6, RRMIPv6
Impact of Number of
CNs

*Source: L. Osborne, A. A. Hamid, R. Ramadugu, A Performance Comparison of Mobile IPv6, Hierarchical

Mobile IPv6, and Mobile IPv6 Regional Registrations

Disadvantages of HMIPv6
It is a single point of failure.
The intermap
handover may
take a
long
time
if the MAPs
are topologically far

Conclusion
HMIPv6 is independent of underlying access
technology
Reduces the number of BU sent to HA and
CN. In the intraMAP handover case only
one BU is required. In InterMAP handover
the BU to Correspondent Node and Home
Agent is required
The use of Hierarchical Mipv6 can reduce
the handover time because BU has to go
only from the Mobile Node to the MAP.
HMIPv6 outperforms MIPv6