IEEE 802.

21 MEDIA INDEPENDENT HANDOVER

DCN: 21-07-0382-00-0000
Title: Network based Distributed Mobility Approach
Date Submitted: July, 19, 2011

Authors or Source(s):
Antonio de la Oliva, Fabio Giust and Carlos J. Bernardos
Abstract: This document presents an IEEE 802.21 based
mechanism to enabled network based distributed mobility
management.

21-07-xxxx-00-0000
 IEEE 802.21
IEEE 802.21 presentation
presentation release
release statements
statements
This document
This documenthas hasbeen
been prepared
prepared to assist
to assist the IEEE
the IEEE 802.21 802.21
WorkingWorking
Group.Group. It is
It is offered
as a basisasfor
offered a discussion
basis for and is not binding
discussion and is on notthe contributing
binding on theindividual(s)
contributing or
organization(s).
individual(s) or Theorganization(s).
material in this document
The materialis subject to change
in this in form
document is and content
subject to
after further study. The contributor(s) reserve(s) the right to add,
change in form and content after further study. The contributor(s) reserve(s) amend or withdraw
material contained herein.
the right to add, amend or withdraw material contained herein.
The contributor
Thecontained
contributor grants
grantsa free,
a irrevocable
free, license
irrevocable to thetoIEEE
license the to incorporate
IEEE to material
incorporate
in this contribution, and any modifications thereof, in the creation of an
material contained in this contribution,
IEEE Standards publication; to copyright inand the any modifications
IEEEs name any IEEEthereof, in the
Standards
creation ofeven
publication an IEEE
thoughStandards
it may include publication;
portions oftothis
copyright in the
contribution; andIEEEs name
at the IEEEs
any discretion
sole IEEE Standards
to permitpublication even though
others to reproduce it may
in whole or ininclude
part theportions
resultingofIEEE
this
contribution;
Standards and at the
publication. TheIEEEs sole discretion
contributor to permitand
also acknowledges others to reproduce
accepts that this
in whole ormay
contribution in part the public
be made resulting IEEE802.21.
by IEEE Standards publication. The contributor
Thealso acknowledges
contributor is familiarand
withaccepts that this
IEEE patent contribution
policy, may be6made
as stated in Section of the public
IEEE-SA by
IEEE 802.21.
Standards Board bylaws <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and
Theincontributor
Understanding is familiar with During
Patent Issues IEEE patent policy, asDevelopment
IEEE Standards outlined in Section 6.3 of
http://standards.ieee.org/board/pat/faq.pdf>
the IEEE-SA Standards Board Operations Manual
<http://standards.ieee.org/guides/opman/sect6.html#6.3> and in
Understanding Patent Issues During IEEE Standards Development
http://standards.ieee.org/board/pat/guide.html>

21-07-xxxx-00-0000
 Network based
Distributed Mobility Management
(A PMIP approach)

Antonio de la Oliva, Fabio Giust, Carlos

J. Bernardos
 Overview
Current Mobility Management schemes (e.g.,
MIPv6, HMIPv6, PMIPv6,) rely on a centralized
entity as cardinal point both for data and control
plane
Net-DMM is a proposal to flatten the architecture
for network-based mobility
Remove the central anchor (at least for the data path)
Keep the mobility operations in the network nodes,
e.g., PMIPv6-alike
The involvement of Mobile Nodes is reduced to movement
detection and/or handover control (e.g., with IEEE 802.21)
 Distributed Mobility Management (i)
Mobility operations are spread among edge
routers:
Mobility Anchor and Access Router (MAAR)
It concentrates the functionalities of an LMA and an
MAG defined in PMIPv6
It is the first IP hop seen by Mobile Nodes (MNs)
It is the anchor for IP flows started by a MN when
attached to it. For these flows:
It acts as standard router if the MN is still attached
It establishes a bidirectional tunnel with the MAAR that is
currently serving the MN
Flows do not need to traverse the central node in the core
network
 Distributed Mobility Management (ii)
Mobility operations are spread among edge
routers:
Each MAAR advertises a unique prefix to the MN upon
attachment
MN configures a different IPv6 address per each visited MAAR
This endows edge routers to be anchor (for the prefix pool they
handle)
Mobility support is provided with finer granularity
Two approaches are presented here
Fully distributed
with the integration of IEEE 802.21 for handover control
Partially distributed
 Full distribution
MAARs learn about the MNs movements by means
of a dedicated control plane (IEEE 802.21 Media
Independent Handover Services)
Upon handover, a MAAR knows where the MN was
previously attached and sends a PBU to the old MAAR
The old MAAR replies with a PBA and a tunnel is
established between them to recover the flow
More than one MAAR might be anchoring ongoing flows, thus
the sequence of operations is repeated once per each MAAR
 Full distribution
CN CN

MAAR MAAR MAAR MAAR PBU MAAR MAAR

1 2 3 1 2 3

PBA
Pref1::Addr1 Pref2::Addr2
Pref1::Addr1 MN
MN CN
CN CN

MAAR MAAR MAAR MAAR MAAR MAAR

1 2 3 1 2 3
TUNNEL TUNNEL

Pref2::Addr2 Pref2::Addr2
Pref1::Addr1 MN Pref1::Addr1 MN
 Partial distribution
The data plane is distributed, as each MAAR anchors
the flows containing the prefixes of their pool
The Central Mobility Database plays a fundamental role
for the control plane
It stores the MNs mobility-related info
At each MNs attachment (either initial registration or
handover), MAARs query the CMD to retrieve and/or
update the session
The CMD informs old MAARs as well, in order to keep the
routing state at the MAARs consistent with the entries
stored
The messages are based on the PBU/PBA format, with
changes and extension according to the sequence of
operations adopted
Different solutions are possible
 Partial distribution
CN CN

MAAR MAAR
3 3
CMD PBU CMD

MAAR MAAR PBA

MN
1 1 Pref2::Addr2
MAAR MAAR
Pref1::Addr1 MN
2 2
Pref1::Addr1

CN
CN CN

MAAR
3 MAAR
CMD 3
CMD
MAAR
1 Pref2::Addr2 MAAR
MAAR
MN 1 Pref2::Addr2
2
TUNNEL Pref1::Addr1
MAAR
MN
2
TUNNEL Pref1::Addr1
 Conclusion
Network-based DMM
Routers at the edge (MAARs) manage the mobility
on behalf of the MNs
The central anchor is not traversed by data packets
The degree of achieved distribution can be
FULL: the control plane is distributed too, with the help of
a dedicated protocol suite for the handover phase and
movement detection (IEEE 802.21)
PARTIAL: a central entity is needed for the control plane,
playing as a MNs mobility sessions database, which the
MAARs query and update according to MNs events
 Changes Required
IEEE 802.21
We need a way of providing the information regarding
the list of previous MAARs anchoring flows to the new
MAAR
This can be done extending the primitives
carrying the address of the previous AR to use a
list instead of just one address.
MIH_N2N_HO_Query_Resources.request
IETF
Extend PMIP signaling, and PMIP state machine to
accommodate the new CMD functionality