1. 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

2. Outline L2 Abstractions for L3-driven Fast HandoverL2 Abstractions for L3-driven Fast Handover –Goals of L3-driven fast handover –Architecture for control information exchange –L2 Primitives for L3-driven fast handover DetailsDetails –Mapping of Primitives and Wireless LAN Parameters EvaluationEvaluation –L3-Driven Fast Handover on FMIPv6 DemonstrationDemonstration –L3-Driven Fast Handover on Predictive-LIN6

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

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

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

6. Usage Types of Primitives 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 request confirmindication request confirm request confirm TYPE 1 TYPE 2 TYPE 3

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

8. Outline L2 Abstractions for L3-driven Fast HandoverL2 Abstractions for L3-driven Fast Handover –Goals of L3-driven fast handover –Architecture for control information exchange –L2 Primitives for L3-driven fast handover DetailsDetails –Mapping of Primitives and Wireless LAN Parameters EvaluationEvaluation –L3-Driven Fast Handover on FMIPv6 DemonstrationDemonstration –L3-Driven Fast Handover on Predictive-LIN6

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

10. L2 Primitives for AP Discovery L2-PeerListL2-PeerList –Network Interface ID –Peer List One or more [Peer*, Condition*] tuplesOne or more [Peer*, Condition*] tuples L2-PeerFound / L2-PeerLostL2-PeerFound / L2-PeerLost –Network Interface ID –Peer List One or more [Peer*, Condition*] tuplesOne or more [Peer*, Condition*] tuples * Each Peer and Condition parameter consists of one or more sub- parameters, as described in the next slide. 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]

11. L2 Primitives for L3 Handover L2-LinkUpL2-LinkUp –Network Interface ID –Peer MAC AddressMAC Address L2-LinkDownL2-LinkDown –Network Interface ID –Peer MAC AddressMAC Address 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 }

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

13. L2 Primitives for L3-Driven Handover L2-LinkConnectL2-LinkConnect –Network Interface ID –Peer MAC AddressMAC Address L2-LinkDisconnectL2-LinkDisconnect –Network Interface ID –Peer MAC AddressMAC Address 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 }

14. Outline L2 Abstractions for L3-driven Fast HandoverL2 Abstractions for L3-driven Fast Handover –Goals of L3-driven fast handover –Architecture for control information exchange –L2 Primitives for L3-driven fast handover DetailsDetails –Mapping of Primitives and Wireless LAN Parameters EvaluationEvaluation –L3-Driven Fast Handover on FMIPv6 DemonstrationDemonstration –L3-Driven Fast Handover on Predictive-LIN6

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

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

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

18. FMIPv6 Implementation for BSD: TARZAN By Nautilus6 ProjectBy Nautilus6 Project –http://www.nautilus6.org/ http://www.ietf.org/internet-drafts/draft-ietf-mipshop-fast-mipv6-03.txt Based on SHISABased on SHISA –Mobile IPv6 and NEMO implementation for KAME (*BSD) –http://www.kame.net/ Support both MN and ARSupport 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) installationManual CAR (Candidate Access Router) installation –car_info.conf Buffering is not supported yet.Buffering is not supported yet.

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

20. Outline L2 Abstractions for L3-driven Fast HandoverL2 Abstractions for L3-driven Fast Handover –Goals of L3-driven fast handover –Architecture for control information exchange –L2 Primitives for L3-driven fast handover DetailsDetails –Mapping of Primitives and Wireless LAN Parameters EvaluationEvaluation –L3-Driven Fast Handover on FMIPv6 DemonstrationDemonstration –L3-Driven Fast Handover on Predictive-LIN6

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

22. Application: DVTS (15Mbps)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)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)L2: IEEE802.11a (5GHz, 54Mbps) –All APs are same channel –All APs have different SSID Project: SIMPLEProject: SIMPLE –Smart Internet Mobile Project with Layered Effects Sender (MN car) Receiver (CN) Handover: L2 (1-2ms) + L3 (RTT 1-2ms) LinkToBeDown () LinkToBeDown (Prepare L3 Handover)  LinkConnect (L2 switch to a specified AP)  LinkUp ()  LinkUp (Finish L3 Handover) START IPv6 Subnet 1 2 3 4 567 Demonstration of L3-Driven Fast Handover on Predictive-LIN6

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

24. Summary Designed L2 abstractions as primitives.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 FMIPv6 was evaluated. L3-driven fast handover on Predictive-LIN6 demonstration.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