Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
I. I NTRODUCTION
HE Internet Engineering Task Force (IETF) has specified a number of mobility support protocols for nextgeneration wireless mobile networks. IETF mobility support
protocols, i.e., Mobile IPv6 (MIPv6) [1], Hierarchical Mobile
IPv6 (HMIPv6) [2], and Fast Mobile IPv6 (FMIPv6) [3], have
Manuscript received January 15, 2011; revised April 11, 2011; accepted
April 22, 2011. Date of publication May 27, 2011; date of current version
January 20, 2012. The review of this paper was coordinated by Dr. A. Vinel.
J.-H. Lee is with the French National Institute for Research in Computer
Science and Control (INRIA), Rocquencourt, France (e-mail: jong-hyouk.lee@
inria.fr).
T. Ernst is with the French National Institute for Research in Computer
Science and Control (INRIA), Rocquencourt, France, and Mines ParisTech,
Paris, France (e-mail: thierry.ernst@inria.fr).
N. Chilamkurti is with La Trobe University, Melbourne, Vic. 3086, Australia
(e-mail: n.chilamkurti@latrobe.edu.au).
Color versions of one or more of the figures in this paper are available online
at http://ieeexplore.ieee.org.
Digital Object Identifier 10.1109/TVT.2011.2157949
been developed to support reachability at a global Internet Protocol (IP) address and continuous Internet connectivity while
a mobile host (MH) performs its handover between different
access networks.
NEtwork MObility Basic Support (NEMO-BS) is a mobility
support protocol specially designed to manage mobility of
an entire IP network in motion (NEtwork MObility, NEMO)
subnet, e.g., in-vehicle IP network [4]. In other words, session
connectivity and reachability for a set of hosts attached to a
mobile router (MR) is supported by the MR. In NEMO-BS, the
MR is responsible for maintaining the binding update (BU) list,
which is a conceptual data structure for the hosts attached to
the MR. While the MR resides at its home network, it obtains
its home address (HoA). As the MR is attached to a new access
router (AR), it configures a new address called care-of address
(CoA) based on the prefix announced by the AR. The MR then
registers a binding between its new CoA, which is used as a
locator, and the HoA, which is used as the identifier, by sending
a BU message to its home agent (HA), where it is recorded in
the binding cache. A binding acknowledgement (BA) message
from the HA is sent to the MR as a response message. This
location update enables the HA to record a network-specific
route that results in establishing a bidirectional tunnel between
the MR and HA for data packets destined to the hosts attached
to the MR. The data packets are first routed to the HA and
forwarded to the MR via the bidirectional tunnel. Then, the data
packets are delivered to the hosts by the MR.
Since NEMO-BS is the sole protocol that is able to provide
mobility for a set of hosts, i.e., NEMO, at the network-layer
level, it is considered in Intelligent Transport Systems (ITS)
standards. For instance, NEMO-BS is adopted as part of the
Communication Architecture for Land Mobile (CALM), which
is also referred to as the ITS station reference architecture,
developed by the International Organization for Standardization (ISO) TC204 WG16 [5]. ITS applications particularly for
general Internet access, image and video transfer, infotainment,
traffic management, and remote management will largely rely
on NEMO-BS. NEMO-BS has also been combined with geographic addressing and routing (GeoNetworking). This work,
which is initially specified by the GeoNet European project [6],
has been standardized by the European Telecommunications
Standards Institute (ETSI) [7], [8].
Even though NEMO-BS provides session connectivity and
reachability for hosts attached to an MR, its handover performance is often not acceptable. In addition, mobility signaling
between the MR and HA must be exchanged for each handover
of the MR. Previously conducted studies [9][14] showed such
limitations of NEMO-BS and tried to improve the performance
75
76
Fig. 2.
Fig. 3.
77
B. FP-NEMO
As an extension to P-NEMO, FP-NEMO is described here.
FP-NEMO optimizes the handover performance of P-NEMO
by utilizing wireless L2 events to anticipate the impending
handover of the vehicles MR. Prior to the attachment of MR
to a new access network, the context of MR is transferred from
the pMAG to the nMAG via the bidirectional tunnel established
between them. The fast handover approach for an MH in
PMIPv6 has been recently standardized as Fast Handovers for
PMIPv6 (FPMIPv6) [28], but it is only designed to enhance the
handover performance of a single MH. FP-NEMO adopts the
approach of FPMIPv6, consisting of the predictive and reactive
modes. In this paper, we only describe the predictive mode
of FP-NEMO.
For FP-NEMO, the following functionalities of MAG and
LMA are required:
MAG for FP-NEMO: The functionalities of MAG in
P-NEMO are required. The neighbor MAGs information
such as network identification and address is maintained in
each MAG. The context transfer functionality is required
to send and receive the context of the MR from neighbor
MAGs. This context transfer is triggered by wireless L2
events, so that it is reasonably assumed that the transmission of the context from the pMAG to the nMAG is completed before the MR actually attaches to the nMAG. The
data packet forwarding and buffering functionalities are
required to prevent packet loss during the MRs handover.
LMA for FP-NEMO: The functionalities of LMA in
P-NEMO are required.
Fig. 4 shows the signaling call flow of FP-NEMO when
the MR performs its handover from its current access network
of pMAG to a new access network of nMAG. As shown in
Fig. 4, the fast handover support of FP-NEMO is started with
the MRs handover report, which is access technology specific.
This report provides the MR-ID and the new access network
information to the pMAG. The handover initiate (HI) message,
78
including the MRs identification, HNP, MNP, and LMA address, are sent to the nMAG. Upon the nMAG obtaining the
HI message, it checks if its status is able to serve the fast
handover support for the MR. Note that the nMAGs decision
for request of fast handover support is determined based on
the requested MRs priority, available buffer size, number of
attached MRs, etc. The nMAG sends the handover acknowledge
(HAck) message including the acceptance or refusal value back
to the pMAG. In the case of acceptance, the pMAG and nMAG
updates their routing status and BU list for the MR. The pMAG
forwards data packets for the MR, i.e., data packets destined
to the MR or hosts attached to the MR, to the nMAG if only
it receives the HAck message with the acceptance value. Note
that this data packet forwarding is continued until the pMAG
receives data packets for the MR from the LMA.
As the link of MR is down from the access network of
pMAG, the MR undergoes the link switching process, i.e., L2
handover, from the pMAG to the nMAG. Then, as the nMAG
is informed the attachment of the MR at its access network, it
immediately sends data packets buffered to the MR. As shown
in Fig. 4, the RS message is assumed to be an indicator for
the attachment of the MR in this paper. The nMAG informs the
attachment of the MR to the LMA by sending the PBU message
and receives the PBA message. As the bidirectional tunnel
between the LMA and nMAG is established, data packets for
the MR go through this tunnel, as described in [28]. The rest
signaling call flow of FP-NEMO is the same with those of
P-NEMO.
Thanks to the context transfer triggered by wireless L2
events, FP-NEMO minimizes the service interruption occurred
by the MRs handover and prevents packet losses.
est fL (t)dt.
(1)
t=0
=
est L eL t dt.
(2)
t=0
1fL
(S )
,
K=0
1
S
(3)
(K) =
2
K1
1
, K1
S (1 fL (S )) (fL (S ))
where S is the session-to-mobility ratio obtained as S /L
[30], [31].
79
TABLE I
N OTATIONS
CSG
i
=
Fig. 5.
Considered topology.
(i) LU (NEMOBS)
i=0
i=1
i
(1 fL (S ))2 (fL (S ))i1
S
LU (NEMOBS)
(5)
B. Considered Topology
The considered topology for performance analysis is shown
in Fig. 5, showing communication paths between relevant
nodes. Note that communication paths related to the CN, i.e.,
HCNLMA and HCNHA , are not used in our analysis.
Suppose that is a localization value indicating the degree
of localized mobility management. Then, is expressed as
Distance between M oving Object and Local Agent
Distance between M oving Object and Global Agent
HLMAMAG + HMAGMR
(4)
=
HHAAR + HARMR
=
where 0 < 1.
We assume that the wired link is robust and no message transmission failure is expected, whereas the message transmission
failure over the wireless link, e.g., HMAGMR and HARMR ,
is expected.
(6)
nf
where
SARMR = HARMR (SBU + SBA ),
SHAAR =
HHAAR (SBU + SBA ), and nf is taken into account for the
wireless link. We apply pf into (6) and then have [34]
LU (NEMOBS) =
pf SARMR
+ SHAAR .
1 pf
(7)
80
(NEMOBS)
CPT
= nn
= nn
nf
pf PARMR
+ PHAAR E(S)
1 pf
(8)
CSG
i
(i) LU (PNEMO)
i=0
i
2
i1
LU (PNEMO)
=
(1 fL (S )) (fL (S ))
S
i=1
(9)
=
(10)
CPT
= nn PLMAMAG E(S)
(11)
i
(i) LU (FPNEMO)
i=0
i
2
i1
=
(1 fL (S )) (fL (S ))
LU (FPNEMO)
S
i=1
(12)
=
(13)
CPT
LHO
+ TLU
(NEMOBS)
+ TP
(15)
where TWRS is a random value uniformly distributed in the interval [0, M AX_RT R_SOLICIT AT ION _DELAY ]. The
movement detection process is started by sending an RS message and is completed by receiving a solicited RA message in
the new access network. Thus, TMD is expressed as follows:
(NEMOBS)
TMD = TRS
+ TRA .
(16)
The delay including the packet service delay and the prop(NEMOBS)
and TRA . Let DP
agation delay is required for TRS
denotes the packet service delay consisting of the processing
delay and the transmission delay at each node. We adopt the
M/M/1 queuing model for the packet service delay. Suppose
that there is no packet loss during the processing. Let 1/P and
81
TRS
= TRA =
pf DARMR
1 pf
(17)
Fig. 7. Handover timing diagram of P-NEMO.
where DARMR = HARMR (DP + D ), D is the propagation delay for the wireless link, and DP is derived as
DP = 1/(1 )P
(18)
where = P /P .
In turn, TDAD in (15) is replaced as RetransT imer defined
in [35] and [36], with the assumption that the address, i.e.,
CoA generated based on the network prefix provided in the
RA message, is not used in any node in the access network.
This is because the DAD process is successfully completed if
a defending neighbor advertisement message for the CoA does
not arrived in RetransT imer [35], [37].
(NEMOBS)
is the delay of the handover registraIn (15), TLU
tion and is represented as the sum of the delay for exchanging
the BU and BA messages between the MR and HA. Suppose that the BA message and the data packet destined for
the MR are simultaneously sent from the HA. Accordingly,
(NEMOBS)
(NEMOBS)
+ TP
is calculated as follows:
TLU
(NEMOBS)
TLU
(NEMOBS)
+ TP
pf DARMR
+ DHAAR
1 pf
(NEMOBS)
+ max(TBA , TP
pf DARMR
+ DHAAR
1 pf
pf DARMR
=
+ DHAAR
1 pf
TBA =
(NBS)
(20)
(21)
LHO
= TWRS
(PNEMO)
TRS
(PNEMO)
where TRS
TLU
(PNEMO)
+ TP
= DLMAMAG
(PNEMO)
+ max TPBA , TP
TPBA = DLMAMAG
(PNEMO)
TP
(26)
LHO
(FPNEMO)
= TWRS +TRS
(FPNEMO)
where TRS
culated as follows:
(PNEMO)
= TRS
(FPNEMO)
(PNEMO)
TP
(25)
pf DMAGMR
+ (DLMAMAG )
1 pf
TP
(PNEMO)
TLU
(24)
) (19)
TP
(22)
(FPNEMO)
(27)
(FPNEMO)
is cal-
+TP
, and TP
pf DMAGMR
.
1 pf
(28)
is calculated as follows:
(PNEMO)
TRS
pf DMAGMR
1 pf
E. Numerical Results
(23)
82
NEMOBS/PNEMO
Fig. 9.
pf and S . (c)
PNEMO/FPNEMO
GC
NEMOBS/PNEMO
and S . (c)
NEMOBS/PNEMO
(NEMOBS)
+ CPT
(PNEMO)
+ CPT
CSG
CSG
(NEMOBS)
(PNEMO)
(29)
NEMOBS/FPNEMO
GC
(NEMOBS)
+ CPT
(FPNEMO)
+ CPT
CSG
CSG
(NEMOBS)
(FPNEMO)
(30)
PNEMO/FPNEMO
GC
NEMOBS/FPNEMO
versus
versus and S .
versus
versus pf and S .
Fig. 10. Variation of relative cost performance gains with pf = 0.1. (a) GC
PNEMO/FPNEMO
GC
NEMOBS/FPNEMO
(PNEMO)
+ CPT
(FPNEMO)
+ CPT
CSG
CSG
(PNEMO)
(FPNEMO)
(31)
Fig. 9 shows the variation of the relative cost performance
gains against S and pf with HHAAR = 10, i.e., = 0.55.
Here, S and pf are varied from 0.1 to 10 and from 0.1 to
0.5, respectively. When S is high, low mobility with a high
session rate happens, i.e., session activity dominates mobility.
S is thus a more serious performance factor than L . On the
other hand, high mobility with a low session rate happens when
S is low, i.e., the MRs handover more frequently happens
83
NEMOBS/PNEMO
Fig. 11. Variation of relative handover performance gains with HHAAR = 10.(a) GH
versus pf and . (c)
PNEMO/FPNEMO
GH
versus pf and .
NEMOBS/PNEMO
Fig. 12. Variation of relative handover performance gains with pf = 0.1. (a) GH
and . (c)
PNEMO/FPNEMO
GH
NEMOBS/FPNEMO
NEMOBS/FPNEMO
versus
versus and .
NEMOBS/PNEMO
GH
LHO
(32)
(PNEMO)
LHO
(NEMOBS)
NEMOBS/FPNEMO
GH
LHO
(33)
(FPNEMO)
LHO
(PNEMO)
PNEMO/FPNEMO
GH
LHO
(FPNEMO)
(34)
LHO
V. C ONCLUSION
NEMO Basic Support (NEMO-BS) is the mobility management protocol considered in ITS standards to maintain Internet
connectivity of vehicles. However, NEMO-BS often results
in unacceptable long handover latency and increased traffic
load to the vehicle. To address these issues, in this paper, we
have introduced new NEMO support protocols, which rely on
84
R EFERENCES
[1] D. Johnson, C. Perkins, and J. Arkko, Mobility Support in IPv6, RFC
3775, Jun. 2004.
[2] H. Soliman, C. Castelluccia, K. ElMalki, and L. Bellier, Hierarchical
Mobile IPv6 (HMIPv6) Mobility Management, RFC 5380, Oct. 2008.
[3] R. Koodli, Mobile IPv6 Fast Handovers, RFC 5568, Jul. 2009.
[4] V. Devarapalli, R. Wakikawa, A. Petrescu, and P. Thubert, Network
Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan. 2005.
[5] Intelligent Transport SystemsContinuous Air Interface, Long and
Medium Range (CALM)IPv6 Networking, ISO Draft DIS 21210,
Feb. 2009.
[6] GeoNet Project, Jul. 2010. [Online]. Available: http://www.geonetproject.eu/
[7] Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 3: Network Architecture, ETSI TS 102 636-3, Mar. 2010.
[8] Intelligent Transport Systems (ITS); Vehicular Communications; Part 4:
Geographical Addressing and Forwarding for Point-to-Point and Point-toMultipoint Communications; Sub-part 1: Media-Independent Functionality, ETSI TS 102 636-4-1, Nov. 2010.
[9] H. Petander, E. Perera, K.-C. Lan, and A. Seneviratne, Measuring and
improving the performance of network mobility management in IPv6
networks, IEEE J. Sel. Areas Commun., vol. 24, no. 9, pp. 16711681,
Sep. 2006.
[10] Q. B. Mussabbir, W. Yao, Z. Niu, and X. Fu, Optimized FMIPv6 using
IEEE 802.21 MIH services in vehicular networks, IEEE Trans. Veh.
Technol., vol. 56, no. 6, pp. 33973407, Nov. 2007.
[11] S.-J. Yoo, S.-J. Choi, and D. Su, Analysis of fast handover mechanisms
for hierarchical mobile IPv6 network mobility, Wireless Pers. Commun.,
vol. 48, no. 2, pp. 215238, Jan. 2009.
[12] R. Kuntz, J. Montavont, G. Schreiner, D. Binet, and T. Noel, An improved
network mobility service for intelligent transportation systems, Wireless
Commun. Mobile Comput., Oct. 2009, DOI: 10.1002/wcm.860.
[13] S. Pack, T. Kwon, Y. Choi, and E. Paik, An adaptive network mobility
support protocol in hierarchical mobile IPv6 networks, IEEE Trans. Veh.
Technol., vol. 58, no. 7, pp. 36273639, Sep. 2009.
[14] M. Tsukada, J. Santa, O. Mehani, Y. Khaled, and T. Ernst, Design and
experimental evaluation of a vehicular network based on NEMO and
MANET, EURASIP J. Adv. Signal Process., vol. 2010, Mar. 2010.
[15] S. Gundavelli, K. Leung, V. Devarapalli, K. Chowdhury, and B. Patil,
Proxy Mobile IPv6, RFC 5213, Aug. 2008.
[16] J.-H. Lee, B.-J. Han, T.-M. Chung, and H.-J. Lim, Network mobility
basic support within proxy mobile IPv6: scenarios and analysis, draftjhlee-netlmm-nemo-scenarios-01, Sep. 2008.
[17] I. Soto, C. J. Bernardos, M. Calderon, A. Banchs, and A. Azcorra,
NEMO-enabled localized mobility support for Internet access in automotive scenarios, IEEE Commun. Mag., vol. 47, no. 5, pp. 152159,
May 2009.
85