route optimization of mobile ip - sfu.ca · • route optimization is efficient in mobile ip to...
TRANSCRIPT
ENSC 835-3: Network Protocols and PerformanceCMPT 885-3: Special Topics: High Performance Networks
FINAL PROJECT PRESENTATIONSSpring 2002
Route Optimization ofMobile IP
Hao (Leo) Chen [email protected]
http://www.sfu.ca/~lcheu/885-project.htm
2/5/03 2
Road Map
• Introduction & Overview– Mobile IP (MIP)– Route Optimization of Mobile IP (ROMIP)
• Project Objectives & Scope
• Implementation– Current MIP in ns– Extension of ROMIP in ns– Simulation
• Conclusion
• References
2/5/03 3
Introduction: Mobile IP overview
• What is Mobile IP?
– Mobility support in IP [rfc3220]
– Portable IP address
– Terminology:
• Home Agent (HA)• Foreign Agent (FA)• IP Tunneling• Encapsulate/Decapsulate
• Mobile Host (MH)• Home Address (Haddr)• Correspondent Host (CH)• Care-of-Address (COA)
P u b l i c N e t w o r k H A
M H
C H
F A
Figure 1. MH in its home network. Communications between CH and MH are shown
by arrows in this figure.
sfu ubc
2/5/03 4
Introduction: Triangle Routing in MIP
• Triangle Routing problem in Mobile IP– Routing when MH is in HA’s domain (figure 1)
– Routing when MH is in FA’s domain (figure 2)
P u b l i c N e t w o r k H A
C H
F A
Figure 2. MH in foreign network. Communications between CH and MH are shown
by arrows in this figure.
M H sfu ubc
ubc
2/5/03 5
Introduction: Route Optimization inMIP• Binding Update Message [2]
HA -> CH
• Binding Caches
• Binding Warning etc.
P u b l i c N e t w o r k H A
C H
F A
Figure 3. MH in foreign network. Communications between CH and MH are shown
by arrows in this figure.
M H sfu ubc
ubc
2/5/03 6
Project Objectives & Scope
• Understand the MIP and ROMIP
• Figure out the current chaotic implementation of Mobile IP inns
• Modify MIP in ns to extend the Route Optimization support –Binding Update Message, Correspondent Host (C++, OTcl)
• Simulate Mobile IP in ns with/without Route Optimization
• Analyze the wireless trace file and compare the result
2/5/03 7
MIP Architecture in ns
Agent
MIPBSAgent
Node
MobileNodeMIPMHAgent
MIPEncapsulatorMIPDecapsulator
Classifier MIPBS MIPMH
2/5/03 8
Current Mobile IP in ns
Route Module
MIPEncapsulator
MH in mynetwork?
Yes
No
Send packet to the COAof the MH
Delivery IP packets to destination
Route Module
MIPDecapsulator
MH in my network?
Yes
No
Get the correspondingaddress of the MH
Delivery IP packets to destination
Home Agent : MIPBSAgent Foreign Agent : MIPBSAgent
I am HA I am FA
2/5/03 9
Implementation – Send Binding Update
Route Module
MIPEncapsulator
MH in foreignnetwork?
Yes
No
Send packet to the COAof the MH
Delivery IP packets to destination
Send Binding Update Message to CH
Home Agent :MIPBSAgent
Am I theHome Agent?
Look up the COA of MH
Send the Binding Update Message to CH
Yes
NoRoute Module
Format of Binding Update Message
C++OTcl
2/5/03 10
Implementation – Receive Binding Update
Route Module
Received BindingUpdate Msg?
Yes
No
Store the COA of the MHin Binding Caches
Delivery IP packets to destination
Correspondent Host : MIPBSAgent
Activate MIPEncapsulator
Route Module
MIPEncapsulatoractivated?
Yes
No
Encapsulate the IP packetwith the COA of the MH
Deliver the IPinIP packets
Delivery IP packets to destination
C++OTcl
2/5/03 11
Simulation - Mobile IP w/o RO
• 1 Home Agent, 1 Foreign Agent, 1 Mobile Host
• 2 wired nodes
• Wireless coverage: 50m
• Distance between HA & FA: 150m
• Traffic Type: CBR
2/5/03 12
Simulation - Mobile IP w/o RO
Home Agent
Foreign Agent
Mobile Host
Correspondent HostDelay: 20ms
Delay: 5ms
2/5/03 13
Simulation Result (Mobile IP w/o RO)
HA FA
CH
time
End-to-end delay
2/5/03 14
Simulation Result Analysis (MIP w/oRO)
• When MH is within HA domain:Minimum delay from CH to MH isaround 33ms = 20 + 5 + 8* ms
• When MH is within FA domain:Minimum delay from CH to MH ismore than 60ms = 5 + 20 + 20 + 5 + 10* ms
• Triangle Routing drastically increases the end-to-end packetdelay, especially when MH is far from HA
* : wireless transmission delay
2/5/03 15
Simulation (Mobile IP with RO)
Home Agent
Foreign Agent
Mobile Host
Correspondent Host
Binding Update
Delay: 20ms
Delay: 5ms
2/5/03 16
Simulation Result (Mobile IP with RO)
HA FA
CH
time
End-to-end delay
2/5/03 17
Simulation Result Analysis (MIP withRO)
• When MH is within HA domain:Minimum delay from CH to MH isstill around 33ms = 20 + 5 + 8* ms
• When MH is within FA domain:Minimum delay from CH to MH isless than 20ms = 5 + 5 + 10* ms
• Triangle Routing is eliminated; end-to-end delay decreasesdrastically
* : wireless transmission delay
2/5/03 18
Simulation Result Comparison
Scenario MH in FAMH in HA
20 ms33 msMIP with RO
60 ms33 msMIP w/o RO
Minimum End-to-End Delay
2/5/03 19
• Route Optimization is efficient in Mobile IP toeliminate Triangle Routing, and decrease theminimum end-to-end delay
• Successfully implement the Binding Update messageand Correspondent Host of ROMIP in ns-2
• The ROMIP can be contributed to ns-2 as anextension of the current MIP
• Future Work– Complete the Route Optimization of MIP– Comparison of ROMIP in IPv4 between IPv6 [3]– Comparison of ROMIP with other approaches [6,7]
Conclusions
!! 20ms << 60ms !! !! 20ms << 60ms !!
2/5/03 20
References• [1] RFC3220: "IP Mobility Support for IPv4", C. Perkins, January 2002
• [2] Internet Draft: "Route Optimization in Mobile IP", C. Perkins, D. Johnson,09/06/2001. (work in progress)
• [3] Internet Draft: "Mobility Support in IPv6", C. Perkins, D. Johnson,11/21/2001. (work in progress)
• [4] The ns Manual, Edited by Kevin Fall & Kannan Varadhan.
• [5] S. Cheshire and M. Baker, "Internet Mobility 4x4", ACM SIGCOMMComputer Communication Review, Conference proceedings on Applications,technologies, architectures, and protocols for computer communications.Volume 26 Issue 4, August 1996, pp. 318 - 329.
• [6] P. Zhou and O. Yang, "Reverse Routing: An Alternative to MIP and ROMIPProtocols", Proceedings of 1999 IEEE Canadian Conference on Electrical andComputer Engineering, Volume 1, pp. 150 - 155.
• [7] R. Jain, T. Raleigh, et al. "Enhancing Survivability of Mobile Internet AccessUsing Mobile IP with Location Registers", INFOCOM '99. Proceedings ofEighteenth Annual Joint Conference of the IEEE Computer andCommunications Societies. Volume: 1 pp. 3 - 11.