1 / 17

End-to-end and Redirection Delays in IP Based Mobility

End-to-end and Redirection Delays in IP Based Mobility . Jon-Olov Vatn TSLab, Dept. of Teleinformatics KTH, Stockholm. Outline of talk. Introduction to IP based mobility Aim and scope of this study Evaluation of IP mobility support schemes Summary Future work. Introduction to IP Mobility.

diantha
Télécharger la présentation

End-to-end and Redirection Delays in IP Based Mobility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. End-to-end and Redirection Delays in IP Based Mobility Jon-Olov Vatn TSLab, Dept. of Teleinformatics KTH, Stockholm

  2. Outline of talk • Introduction to IP based mobility • Aim and scope of this study • Evaluation of IP mobility support schemes • Summary • Future work "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  3. Introduction to IP Mobility Inter-operability handled by IP: • Internetworking rather than interworking. • Easy introduction of new link layers. Internet Protocol (IP) GSM DECT UMTS 802.11 HyperLAN/2 "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  4. FA MN MN MN Example: Mobile IPv4 HA CN • IP address specifies • interface on node • location (subnet) • Introduce: • Home Agent (HA) • Foreign Agent (FA) • Care-of Address (COA) Results in longer end-to-end delay(Tee). "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  5. FA FA MN MN IP level handover procedure CN HA • Detect movement • Get new COA • Redirect data traffic This study concerns the redirection delay (Trd). "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  6. Aim and scope of this study The aim of this study has been to evaluate common IP mobility support schemes with respect to their ability to support real-time services like “mobile telephony”. We consider two metrics: the redirection delay (Trd) and end-to-end delay (Tee). The result is a framework with symbolic expressions for Trd and Tee. "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  7. Aim and scope (cont.) To simplify the evaluation of the different schemes, the following assumptions have been made: • Overlapping cells, but MN is only able to attach to one access point at a time. • Both MN and CN are mobile. • MN and CN use the same mobility scheme. • MN (but not CN) is performing a handover. "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  8. FA FA FA MN CN MIPv4: triangular routing HA2 HA1 End-to-end delay Both the upstream and the downstream data traffic may have to pass the backbone twice: Tee,do=TCN->HA1+THA1->MN Tee,up=TMN->HA2+THA2->CN "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  9. FA FA FA MN CN MIPv4: triangular routing HA2 HA1 Redirection delay Both the upstream and the downstream data are affected Trd,do=THA1->MNold+TMN->HA1 Trd,up=TMN->HA1+THA1->MN "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  10. FA FA FA MN CN MIPv4: reverse tunneling HA1 HA2 End-to-end delay Both the upstream and the downstream data may involve three backbone traversals (BTs). Redirection delay Same as triangular routing. . "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  11. FA FA FA MN CN MIPv4: route optimization HA1 HA2 End-to-end delay MN and CN receives info about each others location (COA) from each others Home Agent (HA). Only one BT! (Is not able to pass ingress filtering routers.) "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  12. FA FA FA MN CN MIPv4: route optimization HA1 HA2 Redirection delay • Trd,up as before (2 BTs). • “Smooth handover” • Trd,do differs for intra-AD and cross-AD handovers: • intra-AD: 0 BTs • cross-AD: 3 BTs Why can’t the MN inform the CN directly? "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  13. FA FA FA MN CN MIPv4: Hierarchy of FAs HA2 HA1 End-to-end delay Not affected. Redirection delay Improvement in both directions for intra-AD handover (0 BTs). No (positive) effect on cross-AD handovers. FA "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  14. R R R MN CN MIPv4: co-located COAs HA2 HA1 MN can acquire a COA of its own (e.g. DHCP). This has effect on the upward redirection delay (Trd,up = 0 BTs). "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  15. R R R MN CN Mobile IPv6 HA1 HA2 • Co-located COAs • Route optimization • Smooth handover • MN can notify CN Best of all worlds! (MN loses privacy, though) "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  16. Summary • Extendable framework for Redirection and End-to-end delays for IP based mobility. • Some results: • Route optimization decreases Tee. • Smooth handover decreases Trd,do (intra-AD). • Hierarchal FAs decrease Trd (intra-AD). • Co-located COAs decreases Trd,up. • Trd,do for cross-AD handovers still an issue. "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

  17. Future work • Refine model: • Include AAA services. • Robustness with respect to packet loss. • Let both MN and CN make handover. • Use network delay data from real network configurations instead of symbolic values. • Make test using high performance Mobile IP implementations. • Efficient link layer support. "End-to-end and Redirection Delays ...", J-O Vatn, PWC' 2000, Gdansk-Polen

More Related