1 / 33

Logical Interface and Flow Mobility Technology

Logical Interface and Flow Mobility Technology. Laboratory of Intelligent Networks (LINK) @ KUT Youn-Hee Han http://link.kut.ac.kr November 26, 2010. Global IPv6 Summit in Korea 2010. IETF Core Standards for IPv6 Mobility Management. [Related WG: MEXT, MIPSHOP, NETEXT – November 2010].

maalik
Télécharger la présentation

Logical Interface and Flow Mobility Technology

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. Logical Interface and Flow Mobility Technology Laboratory of Intelligent Networks (LINK) @ KUT Youn-Hee Han http://link.kut.ac.kr November 26, 2010 Global IPv6 Summit in Korea 2010

  2. IETF Core Standards for IPv6 Mobility Management [RelatedWG: MEXT, MIPSHOP, NETEXT– November 2010] Host-based IP Mobility Network-basedIP Mobility Mobility Support in IPv6 [RFC 3775, June 2004] Hierarchical Mobile IPv6 [RFC 4140, Aug. 2005] Mobile IPv6 Support for Dual Stack Hosts and Routers [RFC 5555, June 2009] Fast Handovers for Mobile IPv6 [RFC 4068, July 2005] Multiple Care-of Addresses Registration [RFC 5648, Oct. 2009] Flow Bindings in Mobile IPv6 and NEMO Basic Support [draft-ietf-mext-flow-binding-11] Traffic Selectors for Flow Binding [draft-ietf-mext-binary-ts-05] Proxy Mobile IPv6 [RFC 5213, Aug. 2008] IPv4 Support for Proxy Mobile IPv6 [RFC 5844, May 2010] Fast Handovers for Proxy Mobile IPv6 [draft-ietf-mipshop-pfmipv6-14] Multiple Care-of Addresses Registration & Flow Bindings in Proxy Mobile IPv6 [draft-trung-netext-flow-mobility-support-01 & draft-bernardos-netext-pmipv6-flowmob-01] Horizontal Handover A handover is initiated when mobile device exits the boundaries of an administrative domain. Single interface is used. Vertical Handover A mobile device does need to move in order to initiate a handover. Multiple interfaces are required, but use one interface at a time. Complexity Level Multiple Interface Management Simultaneous use of multiple interfaces and access networks. Association of an application with an interface Multiple Flow Management Ability to split individual flows between links with respect to the requirements of the flows and the user preferences Per-flow Mobility Management 2

  3. PMIPv6 and Flow Mobility Problems

  4. Proxy Mobile IPv6[IETF RFC 5213, August 2008] LMA: Localized Mobility AgentMAG: Mobile Access Gateway IP Tunnel IP-in-IP tunnel between LMA and MAG LMA Home Network MN’s Home Network (Topological Anchor Point) MAG LMA Address (LMAA) That will be the tunnel entry-point LMM (Localized Mobility Management)Domain MAG movement Proxy Binding Update/Ack. (PBU/PBA) Control messages exchanged by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 MN’ Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain Proxy Care of Address (Proxy-CoA) The address of MAG That will be the tunnel end-point 4

  5. PMIPv6 Features • No Change to Host Stack • IP Mobility handled by the network, and transparent to the host • Any MN is just a IPv6 host • Home in Any Place • MAG sends the RA (Router Advertisement) messages advertising MN’s home network prefix and other parameters • MAG will emulate the home link on its access link. • RA Unicast • RA should be UNICASTed to an MN • It will contain MN’s Home Network Prefix • Per-MN Prefix • M:1 Tunnel • LMA-MAG tunnel is a shared tunnel among many MNs. • One tunnel is associated to multiple MNs’ Binding Caches. • IPv4 Support • RFC 5844 (May 2010) 5

  6. PMIPv6 Operation PBU: Proxy Binding UpdatePBA: Proxy Binding Ack. MN MAG AAA&Policy Store LMA CN MN Attachment AAA Query with MN-ID AAA Reply with Profile PBU with MN-ID, Home Network Prefix option (all zero), Timestamp option PBA with MN-ID, Home Network Prefix option Router Advertisement(Home Network Prefix) Tunnel Setup Optional DHCP Server DHCP Request DHCP Request DHCP Response DHCP Response [MN-HoA:CN](data) [Proxy-CoA:LMAA][MN-HoA:CN](data) [MN-HoA:CN](data) 6

  7. Flow Mobility Problems • Case 1 • Create additional mobility sessions on demand • e.g., additional connection for a particular service • A new mobility session with a new prefix is created LMA LMA Mobile IPTVflow Mobile IPTVflow PBU PBU MAG MAG MAG MAG VoIPflow VoIPflow WiMax 3G WiMax 3G HTTPflow WiBro 3G WiBro 3G MN MN 7

  8. Flow Mobility Problems • Case 2 • If another access is enabled on the MN, some of the existing flows could be moved over, to achieve, e.g., load balancing and better user experience LMA LMA Mobile IPTVflow Mobile IPTVflow PBU PBU MAG MAG MAG MAG VoIPflow VoIPflow WiMax 3G WiMax 3G WiBro 3G WiBro 3G MN MN 8

  9. Flow Mobility Problems • Case 3 • Without any attachment event, LMA can move a flow due to network status change and better QoS support. LMA LMA Mobile IPTVflow Mobile IPTVflow PBU MAG MAG MAG MAG VoIPflow WiMax 3G WiMax 3G VoIPflow WiBro 3G WiBro 3G 단말 단말 9

  10. Flow, Session, Traffic Selector, and Flow Binding

  11. What is Flow? • Flow • A sequence of packets matching a flow description • An interior attribute of a flow is a “direction” • Flow Description: a 5-tuple • <Src. IP, Dest. IP, Src. Port, Dest. Port, Protocol> • The followings can be optionally used • Differentiated Services (Traffic Class in IPv6), IPSEC SPI, Flow Label (IPv6 Only) • Two types of flows • MN manages “Outbound flow” • MN decides which MAG the outbound flow is sent to. • LMA manages “Inbound flow” • LMA decides which MAG the inbound flow is sent to. MAG MAG Inbound flow Outbound flow MN MN

  12. What is Session ? • Session • A Pair of two symmetrically congruent 5-tuples • or, a flow (unidirectional session) • All sessions are anchored by the LMA • We assume that the two flows in a session are delivered via a same type of access technology. Inbound flow: • <3ffe::1, 78dd::2, 20, 15792, UDP> • < 78dd::2, 3ffe::1, 15792, 20, UDP> Outbound flow:

  13. What is Traffic Selector? • Traffic Selector • An information used for traffic filtering • a 5-tuple (allows the asterisk mark) • (3ffe::1, *, 20, *, UDP) • (*, *, *, *, TCP) • (*, *, *, 15792, UDP) • Where does the traffic selector information come from? • The local policy profile in MN • Keeps the traffic selector of outbound flow. • The remote policy profile in LMA (come from Policy Profile) • Keeps the traffic selector of inbound flow for every MN.

  14. Flow Binding Information • Outbound Flow Binding • Assume that MN has a functionality that controls the priority list of physical interfaces for a flow selector • The information is saved at the MN local policy profile • We call the above “Outbound flow binding” Flow selector A Priority List <3ffe::1, *, 20, 15792, UDP> (3G  WL)

  15. Flow Binding Information • Inbound Flow Binding • Remote policy profile at LMA (come from Policy Profile) • Assume that the policy server contains the priority list of technologies for a flow selector • Maybe, a user can manage and control the priority in the remote policy profile • LMA contacts the policy server and get the technology list information. • We call the above “Inbound flow binding” • [NOTE] The two information of local and remote policy profiles should be symmetrically congruent. • MN’s local binding change will be notified to policy profile by out-of-band signal Flow Selector A Priority List (3G  WL) <*, 3ffe::1, 15792, 20, UDP>

  16. Flow Mobility Design

  17. Flow Mobility Scenario • Three types of flow mobility initiation and What is the exact meaning of the network-based flow mobility? 1) [Flow Mobility by a New Connection/Disconnection] • MN makes a connection to a new access technology with a new interface. At this time, LMA (and/or MN) initiates the flow mobility at the same time based on its local policy. 2) [Flow Mobility by LMA’s Decision at a Time] • Network (e.g., LMA) can determine the status of wired and wireless links. • Link’s availability • Congestion • Number of MN (or Flows) Serviced • Therefore, LMA can control flow distribution at any time and it can initiate flow mobility with perfect freedom.

  18. Design Approach • Prefix Allocation Policy • Instead of physical interfaces, the logical interface is actually assigned the whole prefixes. LMA MAG MAG HNP1 HNP2 HNP1 HNP2 WLAN 3G PI: Physical Interface LI: Logical Interface PI1 PI2 MN LI

  19. MN Stack Architecture • MN’s Stacks including the Logical Interface Layer • Logical Interface Layer • Logical Interface • Just a Logical interface made by using the host’s “NetDevice” • Flow Binding Manager • Manage “Flow Binding Information” • Determine the proper physical interface (PI) for the “outbound packets” from MN Application Layer Transport Layer (TCP, UDP…) Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Logical Interface Layer New Layer Data Link Layer PI1 [IEEE 802.11] PI2 [3GPP] PI3 [IEEE 802.16] … Logical Interface Flow Binding Manager

  20. MN Stack Architecture • Flow Binding Manager in Logical Interface Layer • FBM’s role • Gather the mapping information from the MN local policy or inbound packets • Mapping a flow to the one of physical interfaces (PIs) • Determine the physical interface for the outbound packets • Mirroring • Leaning and Action Application Layer Application Layer Learning Action Transport Layer (TCP, UDP…) Transport Layer (TCP, UDP…) Local Policy Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Logical Interface Layer Logical Interface Layer Data Link Layer Data Link Layer PI1 [IEEE 802.11] PI1 [IEEE 802.11] PI2 [3GPP] PI2 [3GPP] PI3 [IEEE 802.16] PI3 [IEEE 802.16] … … Logical Interface Logical Interface Flow Binding Manager Flow Binding Manager Inbound packets Outbound packets

  21. LMA Stack Architecture • LMA’s stacks including the Flow Binding Manager • Flow Binding Manager in PMIPv6 • Manage a “Binding Cache” and “Flow Binding List” for each MN • Gather the mapping information from the service policy or outbound packets • Mapping a flow to the one of bindings • Determine the proper tunnel for the “inbound packets” from a CN Network Layer (PMIPv6) Network Layer (PMIPv6) Network Layer (PMIPv6) Flow Binding Manager Flow Binding Manager Flow Binding Manager Data Link Layer Data Link Layer Data Link Layer Tunnel #1 (to MAG1) Tunnel #2 (to MAG2) Tunnel #3 (to MAG3) … Tunnel #1 (to MAG1) Tunnel #1 (to MAG1) Tunnel #2 (to MAG2) Tunnel #2 (to MAG2) Tunnel #3 (to MAG3) Tunnel #3 (to MAG3) … … “(remote) policy profile” Outbound packets Inbound packets

  22. Reference Stack Architecture & FBL/FIL Binding Cache Network Layer (PMIPv6) Flow Binding Manager Flow Binding List (FBL) Data Link Layer LMA Tunnel #2 (to MAG2) Tunnel #3 (to MAG3) … Tunnel #1 (to MAG1) Frompolicyprofile MAG1 MAG2 MAG3 Default Logical Interface Flow Interface Manager PI1 [IEEE 802.11] PI2 [3GPP] PI3 [IEEE 802.16] … Symmetry in flow info. Data Link Layer Flow Interface List (FIL) Logical Interface Layer MN Network Layer (IPv4, IPv6, ICMPv4, ARP, ICMPv6, …) Fromlocalpolicy Transport Layer (TCP, UDP…) Application Layer Default

  23. Protocol Operation • Flow Mobility by a New Connection – Case 1 MAG#1 MAG#2 LMA CN MN if1 RA[HNP1,HNP2,HNP3] flow X to HNP1:LIID flow Y to HNP2:LIID flow Z to HNP3:LIID if2 PBU[MN-ID,HI=1] New Connection • Check the binding cache and flow binding information • Decide not to move any flow PBA[MN-ID,HNP=HNP4] RA[HNP4] LIID: Logical Interface ID

  24. Protocol Operation • Flow Mobility by a New Connection – Case 2 MAG#1 MAG#2 LMA CN MN if1 RA[HNP1,HNP2,HNP3] flow X to HNP1:LIID flow Y to HNP2:LIID flow Z to HNP3:LIID if2 PBU[MN-ID,HI=1] New Connection • Check the binding cache and flow binding information • Decide to move flow Y to the new attachment PBA[MN-ID,HNP=HNP2] RA[HNP2] flow Y to HNP2:LIID

  25. Protocol Operation • Flow Mobility by LMA’s Decision at a Time MAG#1 MAG#2 LMA CN MN if1 if2 RA[HNP1,HNP2,HNP3] RA[HNP2] flow X to HNP1:LIID flow Y to HNP2:LIID flow Z to HNP3:LIID • Decide to move flow Y to the interface if1 • Check the binding cache and flow binding information • - Just move it! (because HNP2 has been allocated to the MAG#1) flow Y to HNP2:LIID • Decide to move flow X to the interface if2 • Check the binding cache and flow binding information • Send FMI to the MAG#2 (because HNP1 has not been allocated to the MAG#2) HUR[MN-ID,HNP1,add] HUA[MNID,HNP1,add] RA[HNP1,HNP2] flow X to HNP1:LIID HUR: HNP Update Request HUA: HNP Update Ack.

  26. Flow Mobility Verification in NS3

  27. Why NS3? • Current Release • ns-3.9 (August 20, 2010) • Monthly download count of ns-3 releases

  28. Why NS3? • Features • Alignment with real systems • sockets, device driver interfaces • Standard input/output formats • e.g., pcap trace & wireshark • ns-3 is adding support for running implementation code • e.g., Linux TCP code • P2P link, shared link with CSMA. • Routing, ARP • A node can be equipped with multiple network interfaces. • Support (nearly) complete IPv6 • Can run real implementation of applications. • Wireless • WiFi, WiMAX, UMTS (PPP)

  29. Tested Network Topology • PBU Message Format implemented in NS3

  30. Tested Network Topology • Network Topology

  31. Tested Scenario • Test Scenario • 1.0 sec.: MN attaches WLAN • 1.3 sec.: UDP1 and UDP2 flows are served through WLAN • 5.5 sec.: MN also attaches WiMax and only UDP2 flow is moved to WiMax • 10.0 sec.: MN also attaches 3GPP network • 12.0 sec.: new UDP3 flow is served through 3GPP • 15.0 sec.: UDP1 flow is moved to WiMax from WLAN.

  32. Throughput Change • Throughput Graph - 1

  33. Throughput Change • Throughput Graph - 2

More Related