Transcript nemo

Fast-integrated handover scheme with NEMO
support in IEEE 802.16e BWA networks
Lei ZHONG
School of Electronics and Information Engineering, Tongji University,
P.R. China
Fuqiang LIU
School of Electronics and Information Engineering, Tongji University,
P.R. China
Yusheng JI
National Institute of Informatics (NII) and The Graduate University for
Advanced Studies, Japan
1
Outline
Introduction
 Related work
 Proposed algorithm
 Analysis and results
 Conclusion

2
Introduction -demand
3
Introduction -NEMO scenario
4
Outline
Introduction
 Related work
 Proposed algorithm
 Analysis and results
 Conclusion

5
Related work

Mobile IPv6 Fast Handovers over IEEE 802.16e Networks
(FH80216e)

advantage
To solve the problem of unacceptable latency for real-time services,
FMIPv6 was proposed to performs part of the time-consuming process
before actual mobile node handover, reducing handover latency.
FH80216e describes how FMIPv6 could be implemented on link layers
conforming to the 802.16e specification by introducing some crosslayer triggers.

Shortcomings
both the two layered handover mechanisms still operate alternately,
not in parallel.
mainly designed for the node mobility scenarios, suffers from bad
performance when serving moving networks due to its extra
encapsulation.
6
Related work

NEMO basic support
protocol

MN
Advantage
provides native NEMO
handover.
MR
PAR
MN
Tunnel

Shortcomings
produces high handover
latency due to have no
consideration of link-layer
handover.
CN
NAR
MN
Internet
HA
7
Related work

NEMO basic support
protocol

Advantage
provides native NEMO
handover.
PAR
MN

Shortcomings
produces high handover
latency due to have no
consideration of link-layer
handover.
CN
Internet
NAR
Tunnel
MN
MR
HA
MN
8
Outline
Introduction
 Related work
 Proposed algorithm
 Analysis and results
 Conclusion

9
Proposed algorithm

Network model


The typical NEMO
scenario is a vehicular
network, with the
vehicles moving mostly
along roads, rails, or
flight paths.
In such a scenario,
advance preparation for
an impending handover
works quite well.
Internet
CN
Operator's
IP core network
AR1
HA
AR2
V
Serving
BS
Target
BS
MR
10
Proposed algorithm

Handover operation
MR
L3
Serving
BS
L2
PAR
Target BS
Packet tunneling
NAR
HA
Packet forwarding
E
Packet tunneling
D
CN
R
MOB_NBR-ADV
(PrRtAdv)
Scan procedure
HO threshold
LGD
MOB_MSHO-REQ
FBU
Negotiation
MOB_BSHO-RSP
HI
DAD
FBACK
FBACK
LSW
MOB_HO-IND
LUP
HACK
B
Packet tunneling Packet forwarding
E
Link layer re-establishment
FNA
Packet tunneling
R
D
E Encapsulation
R Routing
D Decapsulation
B Buffering
Data packet
11
Outline
Introduction
 Related work
 Proposed algorithm
 Analysis and results
 Conclusion

12
Analysis and results

parameters:









Tframe: Frame duration of IEEE 802.16e OFDMA PHY.
TBS_nego: Negotiation delay between the serving BS and the
recommended BS in ms.
TL2_entry: Latency of IEEE 802.16e network re-entry procedure.
Thop: Delay of every routing hop in a wired backbone network.
Nnar_ha: Distance between the NAR and the HA in hops.
Npar_ha: Distance between the PAR and the HA in hops.
Npar_nar: Distance between the NAR and the HA in hops.
Tdad: Time needed to perform a DAD process.
Tcn_ha: Link delay between CN and HA.
13
Analysis and results

Expressions:

Handover latency
FINEMO
T FINEMO  Tprepare
 TL 2 _ entry  Tfna
BNEMO
T BNEMO  Tprepare
 TL 2_ entry  Tcoa  Tbu
FH 80216e
T FH 80216e  Tprepare
 TL 2_ entry  Tfna

Service disruption time
D FINEMO  TL 2 _ entry  T fna
D BNEMO  TL 2 _ entry  Tcoa  Tbu
D FH 80216 e  TL 2 _ entry  T fna
14
Analysis and results
Handover latency for different frame durations
Handover latency for different distances
between MR and HA
15
Analysis and results
Disruption time for different frame durations
Disruption time for different distances
between MR and HA
16
Outline
Introduction
 Related work
 Proposed algorithm
 Analysis and results
 Conclusion

17
Conclusion
achieves a lower handover latency and
service disruption time and, with a
buffered router, supports even seamless
handover in the network.
 Compatible and works well together with
FH80216e, which supports node mobility.

18
Thanks for your attention.
Any question?
19