1 / 24

Koki Mitani Rie Shibui Kazutaka Gogo Fumio Teraoka Keio University

Unified L2 Abstractions for L3-Driven Fast Handover - Media Independent L2 Triggers from the Perspective of IP Layer -. Koki Mitani Rie Shibui Kazutaka Gogo Fumio Teraoka Keio University {koki,shibrie,gogo,tera}@tera.ics.keio.ac.jp. Outline. L2 Abstractions for L3-driven Fast Handover

brooke
Download Presentation

Koki Mitani Rie Shibui Kazutaka Gogo Fumio Teraoka Keio University

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. Unified L2 Abstractionsfor L3-Driven Fast Handover- Media Independent L2 Triggers from the Perspective of IP Layer - Koki Mitani Rie Shibui Kazutaka Gogo Fumio Teraoka Keio University {koki,shibrie,gogo,tera}@tera.ics.keio.ac.jp

  2. Outline • L2 Abstractions for L3-driven Fast Handover • Goals of L3-driven fast handover • Architecture for control information exchange • L2 Primitives for L3-driven fast handover • Details • Mapping of Primitives and Wireless LAN Parameters • Evaluation • L3-Driven Fast Handover on FMIPv6 • Demonstration • L3-Driven Fast Handover on Predictive-LIN6

  3. Goal A: L3-Driven Fast Handover more than 1 sec L3 Handover Preparation L3 Handover L3 more than 1.5 sec L2 Handover L2 Delay Time Disruption L3 Handover Preparation L3 Handover L3 L2-LinkStatus/PeerList L2-PeerFound/Lost L2-LinkTo BeDown L2-LinkConnect L2-LinkUp L2 Handover L2 Time Disruption • Current Sequence • L3-Driven Fast Handover

  4. Goal B: L3-Driven Vertical Handover L3 Handover L3 Handover L2-LinkToBeDown L2-LinkUp Continuous communication is difficult. L2-LinkConnect L2-LinkConnect Communication quality improves. L3 L2-LinkStatus L2-a L2-b L2-c Time

  5. Architecture for Control Information Exchange Abstract Entity Abstract Entity Protocol Entity Protocol Entity <Layer N> Service User Layer Request Indication Inter-Layer System Confirm Response Service Provider Layer <Layer N-m> Abstract Entity Abstract Entity Protocol Entity Protocol Entity Request is the acquisition request of the lower layer information or a registration of conditions for Indication. In response, Confirmreturns. Indication is asynchronously delivered to an upper layer when an event which needs to be notified occurs. In response, Responsereturns.

  6. Usage Types of Primitives request request confirm confirm request confirm indication Type 1. Provide L2 information to upper layers request:Acquisition request confirm: L2 information Type 2. Notify upper layers of L2 events request: Registration for notification confirm: Valid or invalid indication: Asynchronous notification Type 3. Control L2 actions from upper layers request: Control confirm: Ack or nack TYPE 1 TYPE 2 TYPE 3

  7. L2 Primitives for L3-driven Fast Handover Link Quality Level VERY GOOD : high quality GOOD : available (high watermark) FAIR : adequate quality BAD : low quality (low watermark) VERY BAD : unavailable TYPE 1 TYPE 2 • L2-LinkStatus • Acquisition request for the current link status. • L2-PeerList • Acquisition request for the list of possible access points. • L2-PeerFound / L2-PeerLost • Indication of discovery/missing of candidate access points. • L2-LinkUp / L2-LinkDown • Notification that a new link is brought up / an existing link is brought down. • L2-LinkToBeDown • Notification that the existing link is bringing down. • L2-LinkConnect / L2-LinkDisconnect • Request for connection/disconnection of the specific link. TYPE 3

  8. Outline • L2 Abstractions for L3-driven Fast Handover • Goals of L3-driven fast handover • Architecture for control information exchange • L2 Primitives for L3-driven fast handover • Details • Mapping of Primitives and Wireless LAN Parameters • Evaluation • L3-Driven Fast Handover on FMIPv6 • Demonstration • L3-Driven Fast Handover on Predictive-LIN6

  9. L2 Primitives for Link Status L2-LinkStatus i/f id: ath0 peer { MACaddr: 01:23:45:67:89:ab } condition { bw: 2Mbps quality: GOOD } Link Quality Level VERY GOOD : high quality GOOD : available (high watermark) FAIR : adequate quality BAD : low quality (low watermark) VERY BAD : unavailable • L2-LinkStatus • Network Interface ID • Peer • MAC Address • Condition • Bandwidth • Link Quality Level

  10. L2 Primitives for AP Discovery L2-PeerList i/f id: ath0 [Peer1, Condition1] [Peer2, Condition2] [Peer3, Condition3] [Peer4, Condition4] L2-PeerFound i/f id: ath0 [Peer5, Condition5] L2-PeerLost i/f id: ath0 [Peer5, Condition5] • L2-PeerList • Network Interface ID • Peer List • One or more [Peer*, Condition*] tuples • L2-PeerFound / L2-PeerLost • Network Interface ID • Peer List • One or more [Peer*, Condition*] tuples * Each Peer and Condition parameter consists of one or more sub-parameters, as described in the next slide.

  11. L2 Primitives for L3 Handover L2-LinkUp i/f id: ath0 peer { MACaddr: 01:23:45:67:89:ab } L2-LinkDown i/f id: ath0 peer { MACaddr: 01:23:45:67:89:ab } • L2-LinkUp • Network Interface ID • Peer • MAC Address • L2-LinkDown • Network Interface ID • Peer • MAC Address

  12. L2 Primitives for Preparing L3 Handover L2-LinkToBeDown i/f id: ath0 peer { MACaddr: 01:23:45:67:89:ab } condition { bw: 2Mbps quality: BAD } Link Quality Level VERY GOOD : high quality GOOD : available (high watermark) FAIR : adequate quality BAD : low quality (low watermark) VERY BAD : unavailable • L2-LinkToBeDown • Network Interface ID • Peer • MAC Address • Condition • Bandwidth • Link Quality Level

  13. L2 Primitives for L3-Driven Handover L2-LinkConnect i/f id: ath0 peer { MACaddr: 01:23:45:67:89:ab } L2-LinkDisconnect i/f id: ath0 peer { MACaddr: 01:23:45:67:89:ab } • L2-LinkConnect • Network Interface ID • Peer • MAC Address • L2-LinkDisconnect • Network Interface ID • Peer • MAC Address

  14. Outline • L2 Abstractions for L3-driven Fast Handover • Goals of L3-driven fast handover • Architecture for control information exchange • L2 Primitives for L3-driven fast handover • Details • Mapping of Primitives and Wireless LAN Parameters • Evaluation • L3-Driven Fast Handover on FMIPv6 • Demonstration • L3-Driven Fast Handover on Predictive-LIN6

  15. What is FMIPv6? Home Agent (Location Management Server) Binding Cache Correspondent Node Home Address Previous Care-of Address Forwarding data packets from/to the new location Internet Registration of new location by MN is in progress. Previous Access Router New Access Router Previous Care-of Address Mobile Node Binding Update of New Care-of Address • L3 Fast Handover Protocol based on Mobile IPv6 • AR forwards data packets to the new location during L3 handover

  16. L3-Driven Fast Handover on FMIPv6 New AR Start Forwarding Handoff Complete HI FNA Previous AR HAck Exchange Information RtSolPr FBU Data Packets FBack PrRtAdv AP/AR Discovery L3 Handover Preparation L3 Handover L3 L2-PeerList L2-PeerFound/Lost L2-LinkTo BeDown L2-LinkConnect L2-LinkUp Mobile Node L2 Handover L2 Time • L3-Driven + FMIPv6 Predictive Mode

  17. L3-Driven Fast Handover on FMIPv6 Start Forwarding Handoff Complete New AR FBU HAck Previous AR FNA[FBU] Exchange Information HI RtSolPr Data Packets FBack PrRtAdv AP/AR Discovery L3 Handover L3 L2-LinkDown L2-PeerList L2-PeerFound/Lost L2-LinkUp Mobile Node L2-LinkConnect L2 Handover L2 Time • FMIPv6 Reactive mode • The case that handover prediction failed.

  18. FMIPv6 Implementation for BSD: TARZAN • By Nautilus6 Project • http://www.nautilus6.org/ http://www.ietf.org/internet-drafts/draft-ietf-mipshop-fast-mipv6-03.txt • Based on SHISA • Mobile IPv6 and NEMO implementation for KAME (*BSD) • http://www.kame.net/ • Support both MN and AR • L2 trigger by LIES • Inter-Layer Control Information Exchange Architecture • L2 Abstraction: http://www.ietf.org/internet-drafts/draft-koki-mobopts-l2-abstractions-02.txt • Manual CAR (Candidate Access Router) installation • car_info.conf • Buffering is not supported yet.

  19. Evaluation of L3-Driven Predictive FMIPv6 NCoA PCoA (Forwarded to NCoA) L2 Handover PCoA LinkConnect FNA BU FBU BA (from Distant HA) LinkUp FBack LinkToBeDown (without Buffering) Total Disruption Time: 60ms(L2) + 50ms(L3) = 110ms / L2: Wireless Environment Emulator

  20. Outline • L2 Abstractions for L3-driven Fast Handover • Goals of L3-driven fast handover • Architecture for control information exchange • L2 Primitives for L3-driven fast handover • Details • Mapping of Primitives and Wireless LAN Parameters • Evaluation • L3-Driven Fast Handover on FMIPv6 • Demonstration • L3-Driven Fast Handover on Predictive-LIN6

  21. L3-Driven Fast Handover on Predictive-LIN6 more than 1 sec L3 Handover Preparation L3 Handover L3 more than 1.5 sec L2 Handover L2 Delay Time Disruption L3 Handover Preparation L3 Handover L3 L2-LinkStatus/PeerList L2-PeerFound/Lost L2-LinkTo BeDown L2-LinkConnect L2-LinkUp L2 Handover L2 Time Disruption • Current Sequence • L3-Driven Fast Handover

  22. Demonstration ofL3-Driven Fast Handover on Predictive-LIN6 3 2 IPv6 Subnet 1 4 START 7 6 5 • Application: DVTS (15Mbps) • Digital Video Stream on IEEE1394 Encapsulated into IP • Sender: MN in a car • L3 Mobility Protocol: Predictive-LIN6 (No Forwarding, No Buffering) • Prediction of LinkDown and Candidate AP/AR by L2 Triggers • DAD is performed before L2 handover • L2: IEEE802.11a (5GHz, 54Mbps) • All APs are same channel • All APs have different SSID • Project: SIMPLE • Smart Internet Mobile Project with Layered Effects Handover: L2 (1-2ms) + L3 (RTT 1-2ms) LinkToBeDown (Prepare L3 Handover)  LinkConnect (L2 switch to a specified AP)  LinkUp (Finish L3 Handover) Receiver (CN) Sender (MN car)

  23. Sequence of L3-Driven Fast Handover on Predictive-LIN6 Sequence of L2 and L3 Handover: 3-4ms (L3 Disruption Time) Address Configuration Location Registration L3 Link Connect LinkUp LinkDown L2 Time 0.8 ms 0.9 ms RTT: 1-2 ms Sequence of L2 Trigger: 40us Indication Userland Daemon 19.8 us 13.1 us Kernel 2.6 us Wireless Device Time L2 Event

  24. Summary • Designed L2 abstractions as primitives. • L2-PeerList / L2-PeerFound / L2-PeerLost • L2-LinkStatus / L2-LinkUp / L2-LinkDown / L2-LinkToBeDown • L2-LinkConnect / L2-LinkDisconnect • L3-driven fast handover on FMIPv6 was evaluated. • L3-driven fast handover on Predictive-LIN6 demonstration. IETF Document: http://www.ietf.org/internet-drafts/draft-koki-mobopts-l2-abstractions-02.txt Teraoka Lab. Keio Univ. http://www.tera.ics.keio.ac.jp/ Nautilus6 Project http://www.nautilus6.org/ SIMPLE Project

More Related