- IETF 64 -

FMIPv6 over IEEE 802.16 (draft-jang-mipshop-fh80216-00’.txt)

HeeJin Jang, Youn-Hee Han, Soohong Daniel Park

SAMSUNG

Junghoon Jee, Jaesun Cha

ETRI

- IETF 64 - 2/9

• 802.16 Deployment Architectures• 802.16 Handover Overview• Change points

– Two New Primitives

– Handover Scenarios

– Implementation with 802.21 MIHF

• Q&A

Contents

- IETF 64 - 3/9

802.16 Deployment Architectures

IP Mobility is required

IP Mobility is required

Fig. (a) a subnet = one AR + several BSs Fig. (b) a subnet = one AR + one BS

- IETF 64 - 4/9

802.16e Handover Overview

Target BSServing BS

MOB_MSHO-REQ

MOB_BSHO-RSP

MOB_HO-IND

MOB_NBR-ADV

MN L2 (MS)

Scanning

MOB_SCN_REQ

MOB_SCN_RSP

802.16e Network re-entry

Packets

1) MN collects info. about the serving BS and neighboring BSs through the periodic L2 neighbor advertisement and the scanning.

2) MN starts HO by sending MOB_MSHO-REQ to BS and then BS replies with MOB_BSHO-RSP including the candidates BSs.

3) MN selects the target BS and then sends the MOB_HO-IND to the serving BS and switches the links

4) After the HO, MN performs the network re-entry procedures.

- IETF 64 - 5/9

• Changes from the initial presentation– Two more primitives are defined

– Five HO steps are changed into four HO steps

– Implementation with 802.21 MIHF (Media Independent Handover Function) is described

Change points

- IETF 64 - 6/9

Four Primitives for interaction of FMIPv6 & 802.16e

Primitives Direction Description Action

Link_Going_Down L2->L3The signal strength goes low and it’s time to prepare for the handover

L3 sends FBU

Link_Up L2->L3 The link became available now. L3 sends FNA

New_BS_Found L2->L3 New BS is detected L3 sends RtSolPr

Link_Switch L3->L2 Switch to the new link L2 switches to the new link

• We defined two more primitives, New_BS_Found and Link_Switch

• New_BS_Found is triggered from L2 to L3 when new BS is detected in order that the MN starts the NAR discovery by exchange of RtSolPr & PrRtAdv

• Link_Switch is introduced to notify L2 of L3 HO preparation completion– By default, L2 doesn’t need to wait this primitive

– It could be implemented to make higher the possibility of predictive HO

- IETF 64 - 7/9

L2/L3 Handover Scenarios

<HO execution>

1) NAR Discovery– MN learns the neighboring BSs– NAR IP address resolution with BSID afte

r getting (1)

2) HO Preparation– MN requests HO and gets the reply back fr

om the BS and triggers (2)– Tunnel is setup and packets are redirected

to NAR– NCoA is confirmed

3) HO Execution– After the arrival of FBAck, MN issues (3).– MN L2 sends HO indication to the serving

BS and switches the links– IEEE 802.16e network entry

4) HO Completion– MN sends FNA and receives the buffered

packets from NAR

• Conceptually divided into four steps: 5 steps => 4 steps– 802.16 network entry step is integrated into HO execution step

1) New_BS_Found 2) Link_Going_Down 3) Link_Switch 4) Link_UP

< NAR discovery>

<HO completion>

<HO preparation>

- IETF 64 - 8/9

Implementation with 802.21 MIHF

New BS detected

Link goes down

Link up

L3 HO preparation is

completed

MIHF 802.16e

Link_Going_Down (E)

MN FMIPv6

Link_Detected (E)

MIH_Switch (C)

Link_Up (E)

New_BS_Found

Link_Going_Down

Link_Switch

Link_Up

• MIH function services– MI Event service (MIES)

– MI Command service (MICS)

– MI Information service (MIIS)

• If the terminal is equipped with MIHF module, the proposed primitives can be implemented to cooperate with 802.21 MIHF

- IETF 64 - 9/9

Future Works

• We assumed that Neighbor discovery over 802.16 networks works well.

• We need to consider the problems which may also cause mal-operation in FMIPv6.