1 / 13

Flow mobility support in PMIPv6 draft-trung-netext-flow-mobility-support-01

This document outlines the flow mobility requirements and the necessary PMIPv6 extensions to support flow mobility. It also discusses the NS3 implementation and concludes with key findings.

marierobinson
Download Presentation

Flow mobility support in PMIPv6 draft-trung-netext-flow-mobility-support-01

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. Flow mobility supportin PMIPv6draft-trung-netext-flow-mobility-support-01 T. Tran, Y. Hong (ETRI) Y. Han (KUT) IETF 79 - Beijing trungtm2909@gmail.com

  2. Outlines • Flow mobility requirements • Necessary PMIPv6 extensions • NS3 implementation • Conclusions trungtm2909@gmail.com

  3. Flow mobility requirements (1) • 5-tuple based flow description: Home Network  Prefix should be able to be shared across its attachments (called shared-prefix model) trungtm2909@gmail.com

  4. Flow mobility requirements (2) • HNP based flow description: the HNP is not needed to be shared across interface. Unique-prefix can be assigned to each IF. trungtm2909@gmail.com

  5. Flow mobility requirements (3) • LMA should support flow-based routing 5-tuple based flow description HNP based flow description trungtm2909@gmail.com

  6. PMIPv6 extensions for supporting shared prefix model • Pro-active signaling • The same HNPs are assigned to all interfaces in advance • Re-active signaling • HNP is shared across interfaces only when the flow mobility is occurred trungtm2909@gmail.com

  7. Pro-Active Signaling (1) Modify PBA message to include the HNPs that are assigned to the existing attachments (2) Extend the signaling between LMA/MAG to update new HNP to the MAG trungtm2909@gmail.com

  8. Re-Active Signaling (1) Extend the signaling between LMA/MAG to update new HNP to the MAG trungtm2909@gmail.com

  9. PMIPv6 extensions for supportingFlow-based routing (1) • Extend BCE to support multiple Care-of Address registration (1) The MN1 attached to the network using 2 interfaces (2) LMA requests MAG2 to updated with HNP1 trungtm2909@gmail.com

  10. PMIPv6 extensions for supportingFlow-based routing (2) • Add flow binding function to the LMA (1) Before the flow mobility occurs (2)After the LMA decides to move TCP flow 1 to the MAG 2 trungtm2909@gmail.com

  11. Implementation in NS3 • We are now implementing our proposals in NS3 • Why NS3? • It supports multi-interface nodes • In our simulation, an MN will have WLAN, WiMAX, 3GPP interfaces. • and also logical interface! • It supports (near-complete) IPv6 stack • It conforms to standard input/output formats so that other tools can be reused. • e.g., pcap trace output trungtm2909@gmail.com

  12. Conclusions • PMIPv6 can be extended in two ways to support flow mobility: Pro-active and Re-active signaling • No flow information is needed to be sent from LMA to MAG • To support full flow granularity movement we should differentiate flows by using 5-tuple inf., otherwise we can support just partial handoff. • The MN just obeys the flow policy from the network. It always uses the same interface to receive and send packets of a flow. trungtm2909@gmail.com

  13. Q & A Thank you! trungtm2909@gmail.com

More Related