1 handover for pmipv6 using mih kang joon-suk 姜俊錫

1

Handover for PMIPv6

Using MIH

KANG Joon-Suk

姜俊錫

2

Contents

Why Proxy MIPv6 Fast HO procedure Fast HO Time line Problems to be solved Vertical Handover Problems to be solved Comments

3

Agenda


4

Why Proxy MIPv6

The provisioning of seamless mobility to moving nodes across homogeneous/heterogeneous access networks

Theoretical Target IPv6 nodes

PC, Mobile phone, PDA, Web camera, Home application, VoIP phone, Mobile router, etc..

Mobile/Multimedia applications….. But actually No current targets…..

5

Why Proxy MIPv6

Increasing number of Mobile node users.. VoIP phone, PDA, Note book, During walking

Voice/Video over IP phone During riding moving vehicles

All devices to use Internet Mobile router is strongly needed

6

Why Proxy MIPv6

Normal MIPv6 was already completed Leaded by mobile phone suppliers

NOKIA… Heavy overhead to MN

Energy problem, Waste of air resources There are no charming points to the Telecommuni

cation Operator(supporting commercial services).

7

Why Proxy MIPv6

Many vendors and Standard organizations were concerned about alternative technology. CISCO, Juniper, WiMAX, 3GPP, IETF… Proxy Mobile IPv6

Proxy MIPv6 is good technology to support commercial service by Telecommunication Operators and router vendors.

8

Agenda


9

Scenario

pMAG: serving MAG1

MAG2

- LMA : current home agent for the mn

- pMAG : currently serving MAG

- MAG1&MAG2 : candidate MAGs for a next MAG

LMA

MN

Handover

10

Protocol stack

PMIPv6 for MN(simple modification

of IPv6)

MIHF

MAC

PMIPv6

MAC

PMIPv6

MIHF

MAC

TARGETIEEE 802.16IEEE 802.11

MN MAG LMA

11

Procedure

pMAG: serving MAG1

Scan for Candidate N

etworks

1

2

1. MN is moving

2. Scan for Candidate Networks To make the list of

candidate networks When the MN finds

new network areas…

LMA

MAG2

12

2- How to Scan for Candidate Networks

Main method : Automatic method Using Link_Detect event

The Link Detected event is generated on the MN when a PoA(Point of Attachment) of an access network is detected for the first time.

Automatically detected

Complement Manual method Using MIH_Link_Actions(Link_Scan) command

To get a list of discovered PoAs and related information. Manually trigger

13

2- How to Scan for Candidate Networks - Automatic

pMAG: serving MAG1

MAG2

Scan for Candidate N

etworks

During MN is moving, if the MN finds the new network area, Link_Detected event is generated on the MN The event comprise

the information of PoA

MN stores the PoA information Making a list

LMA

14

2- How to Scan for Candidate Networks - Passive

MN pMAG nMAGPMIPv6Client

MIHFProtocol

MAC PoA(MAC)

PoS(MIHF)

PMIPv6Client

PoA(MAC)

PoS(MIHF)

PMIPv6Client

MIISServer

MIH_Event_Subscribe.request{Link_Detected}

Link_Detected

Link_Detected

Link_Detected

Stores the link info.


15

2- How to Scan for Candidate Networks - Active

pMAG: serving MAG1

MAG2Link_Going_Down

1

2

1. When Link_Going_Downoccures,

2. if the MN has no PoA informationor the confidence level of Link_Going_Down is low,

3. Start to scan for Candidate Networks=> Using MIH_Link_Actions(Link_Scan) command

LMA

16

2- How to Scan for Candidate Networks - Active


MIHFProtocol

MAC PoA(MAC)

PoS(MIHF)

PMIPv6Client

PoA(MAC)

PoS(MIHF)

PMIPv6Client

MIISServer

MIH_Scan.request

Link Going Down withLow Confidence Level

Link_Going_Down.indication

MIH_Link_Going_Down.indication

Scan for Candidate Network

Link_Action.request (LINK_SCAN)

Link_Action.confirm(ScanResult)

MIH_ScanResponse

LINK_SCAN


17

Procedure – contd.

pMAG: serving MAG1

1 2

3

LMA

3. Link_Going_Down event occurs with High confidence level

4. Decision of Target MAG4-1. MN send PoA list to pMAG4-2. pMAG selects target MAG using the list.

4

Link_Going_Down(70%)

18

4- Target Decision

MIH_N2N_HO_Query_Resource command By what parameters?

Signal strength? It must be considered more

19

MN pMAG nMAG4- Target Decision

PMIPv6Client

MIHFProtocol

MAC PoA(MAC)

PoS(MIHF)

PMIPv6Client

PoA(MAC)

PoS(MIHF)

PMIPv6Client

MIISServer

……

Resource Availability CheckMIH_N2N_HO_Query_Resource.request

MIH_N2N_HO_Query_Resource.request

MIH_N2N_HO_Query_Resource.request

MIH_N2N_HO_Query_Resource.response

MIH_N2N_HO_Query_Resource.response

20


pMAG: serving MAG1

LMA

5. pMAG makes MAG1 prepare handover Sending

“Trigger_L3_HO”message

6. Virtual PBU

7. Setup virtual BCE and Tunnel with MAG1

8. Virtual PBA

9. Setup Tunnel and Routing

5

6

7

8

9

21


10. Inform that virtual PBU is finished

11. LMA sends packets to MAG1 by the new tunnel, and MAG1 forwards them to pMAG Because the MN is

attaching to pMAG yet The packets from the

MN can be transferred by pMAG

pMAG: serving MAG1

LMA

10

11

22

Procedure – contd. ☞ In current stage

pMAG is serving the MN yet LMA has two tunnels for the MN

with pMAG with MAG1

LMA has two cache entry for the MN with pMAG with MAG1

Packet path from LMA to MN LMA -> MAG1 –(forwarding)-> pMAG -> MN

Packet path from MN to LMA MN -> pMAG -> LMA

23

Why Use Forwarding Path for Packets from LMA to MN

Forwarding path MN -> pMAG -> LMA

Why? To prevent the HO latency between LMA and

MAG after L2 handover

24





pMAG: serving MAG1

1

LMA

25


2~3. L2 HO The L2 connection with

pMAG is closed New L2 connection is

established with MAG1

4. Immediately, MAG1 can recognize that L2 HO was just finished.

5. MAG1 stops forwarding packets to pMAG at once

6. MAG1 starts to forward packets to MN directly

pMAG: serving MAG1

2 3

LMA

45

6

7

8

911

26

In case of normal PMIPv6, there must be time waste after L2 HO When MAG1 informs LMA that L2 HO was just finished.

MAG1 has to send PBU to LMA, and then LMA has to send PBA to MAG1

Total latency = 2 x delay(LMA ~ MAG1) Too long latency

It’s the most part of total HO latency

In case of FMIPv6 There is no time waste


27


pMAG: serving MAG1

LMA

12. pMAG triggers L2 HO using MIH command MIH_HO_Commit

• Until L2 HO is finished, pMAG caches packets which come from MN and MAG1 caches packets which come from LMA.

• During L2 HO, the MN stores packets destined for LMA

12

28


13. L2 HO is finished

14. RS

15. RA

16. IP set up

17. pMAG sends the packets cached to MAG1 and MAG1 forwards them to the MN

18. pMAG releases all resources about the MN

pMAG: serving MAG1

LMA18

13

17

141516

29


pMAG

MAG1: serving

LMA

19. HO is totally finished19

30

12- L2 HO procedure using MIH command


MIHFProtocol

MAC PoA(MAC)

PoS(MIHF)

PMIPv6Client

PoA(MAC)

PoS(MIHF)

PMIPv6Client

MIISServer

……

Resource Availability Check MIH_N2N_HO_Commit.request

MIH_N2N_HO_Commit Request

MIH_N2N_HO_Commit.indication

MIH_N2N_HO_Commit.response

MIH_N2N_HO_Commit Response

MIH_N2N_HO_Commit.confirm

MIH_Net_HO_Commit.request

MIH_Net_HO_CommitRequest

L2 HO

MIH_Net_HO_Commit.confirm

MIH_Net_HO_CommitResponse (Status = Success)

31

12- L2 HO procedure using MIH command


MIHFProtocol

MAC PoA(MAC)

PoS(MIHF)

PMIPv6Client

PoA(MAC)

PoS(MIHF)

PMIPv6Client

MIISServer

MIH_MN_HO_Complete.request

MIH_MN_HO_CompleteRequest

MIH_MN_HO_Complete.indication

MIH_MN_HO_Complete.response

MIH_MN_HO_CompleteResponse

MIH_MN_HO_Complete.confirm

32

Agenda


33

Time Line 1. Preparing HOMN pMAG MAGnMAG1 … LMA

TunnelServing

Beacon / Response to a probe

Link_detect


Link_Going_Down(Low confidence)

Link_Action(Link_Scan)

Link_Scan


Link_Going_Down(High confidence)

PoA ListResource Query

Target Decision=> MAG1

Low

34

Time Line 2. make before breakingMN pMAG MAG1 LMA

Tunnel

Inform that virtual PBU is finished

Trigger_L3_HOVirtual PBU

BCE UpdateVirtual PBA

Packet forwarding(destined for MN)

Packet forwarding(from MN)

35

Time Line3. Complete L2 HO MN pMAG MAG1 LMA

Tunnel

L2 HO

Trigger_L2_HOBCE Update

Link_down Link_down

Packet cachingPacket caching

Serving

HO complete

release

BCE Release

RS

RA

36

Agenda


37

Problems to be solved

When does the ‘scanning for Candidate Networks’ start? 1. After Link_Going_Down(Low confidence

Level) message occurs ? It acts totally up to Link_Going_Down event But, I’m not sure whether Link_Going_Down can be

performed to my wishes. 2. Check the signal from serving MAG periodically.

If it decreases to specific level, start ‘scanning’ Additive technic is required. It Maybe become a burden to the MN

38

Agenda


39

Vertical Handover

IPv6 Backbone IPv6 BackboneMAG1 MAG2

Different Access Network Type

MN MN

L2 Link Detection& Interface SWAP

L2 Link Detection& Interface SWAP

MN

.. .. ..

High speed wireless LAN

Wireless LAN

Interface

Wireless LAN

Interface

3GPP Interface

3GPP Interface

3GPP(Cellular)

40

Why Vertical Handover Cost/Capacity/Coverage….. If a laptop might be able to use both a high speed

wireless LAN and a cellular technology for Internet access. Wireless LAN connections generally provide higher speeds

benefit of utilizing the higher bandwidth and lower cost Cellular technologies generally provide more ubiquitous

coverage. better mobility support and larger coverage

The laptop user might want to use a wireless LAN connection whenever one is available, and to 'fail over' to a cellular connection when the wireless LAN is unavailable.

41

Two Issues of V-Handover

Multihoming problem. There are many types of access network(L2) Mobile Node : Multiple Interfaced Node.

Have to support unified signaling service between L2 and L3 regardless of L2 type MIH

42

Reuse of the Fast-handover method Fast-HO uses MIH events and commands between

MAG and MN Those events and commands are applicable to various L2

techniques MIH_Event_Subscribe Link_Detect Link_Going_Down MIH_N2N_HO_Query_Resource MIH_Link_Actions(Link_Scan) MIH_HO_Commit ….

The process between MAG and LAM has only L3 procedure Independent on L2

43

Multiple Ifs for MIPv6

Scenarios and Motivations for Multihomed mobile nodes Need for ubiquitous access to the Internet Need to redirect established sessions Need to set up preferences Need to select the best access technology Need to dispatch traffic over distinct paths Need for reliability Need to accelerate transmission

44

IPv6 addressing methods

Auto-configuration is recommended Stateless

‘Network Prefix’(from Router) + ‘unique If ID’(from L2 address of If)

Statefull DHCPv6 & ‘unique If ID’(from L2 address of If)

Manual-configuration It is not related with If ID

Auto-configuration is strongly recommended To improve efficiency of network management

45

IP changing problem

Transport

IPv6

MAC1 MAC2

MN

Transport

IPv6

MAC1 MAC2

MN

Moving and

Changing

IP = Net Prefix + IF ID from MAC1


Session will break down after handover Because of IP

address changing

46

IP changing problem

To achieve seamless connection IP address must not be changed

To get other advantages of multi-homing Each Interface must have unique IP address

I will focus on ‘Seamless connection’

47

Using current RA method ?

I did not want to modify normal addressing system.

But, Router Advertisement message supports information about only auto-configuration.

48

Virtual Interface(Switch manager) ??

Application

FH-PMIPv6

MIHF

MAC

Application

FH-PMIPv6

MIHF

MAC

Application

FH-PMIPv6

MIHF

MAC

Application

FH-PMIPv6

MIHF

Virtual Interface(Switch manager)

Multiple MACS…

MN MAG

MAGMN

RepresentativeIP address

RepresentativeIP address

RepresentativeInterface ID

RepresentativeInterface ID

49

Simple Modification of Auto-configuration process

MN must memorize representative Interface The interface by which the MN is attached to

LMA. When the MN set up the IP address using

auto-configuration method (by the information from RA)

To get a Interface ID, the MN uses the MAC address of representative Interface, instead of actual interface.

50

Simple Modification of Auto-configuration process

Transport

IPv6

MAC1 MAC2

MN

Transport

IPv6

MAC1 MAC2

MN

Moving but

no Changing




51

Procedure

Almost same with fast-HandOver procedure But it is possible to set up the connection

between MN and new MAG, before breaking the connection between MN and old MAG

First part is same with fastHO procedure Stage 1 ~ Stage 9

52


10. Trigger L2 connection setup(MAG1 and MN’s new IF)

11. Setup the L2 connection with MAG1

pMAG: serving MAG1

LMA

10

11

MN

53


12. Inform that virtual PBU is finished




pMAG: serving MAG1

LMA

12

13

MN

54

Procedure – contd.14. Change the

connection• Until L2 HO is finished,

pMAG caches packets which come from MN and MAG1 caches packets which come from LMA.

• During L2 HO, the MN stores packets destined for LMA

pMAG: serving MAG1

LMA

14

MN

55


15. L2 HO is finished

16. RS

17. RA

18. IP set up

19. pMAG sends the packets cached to MAG1 and MAG1 forwards them to the MN

20. pMAG releases all resources about the MN

pMAG: serving MAG1

LMA20

15

19

161718

56


pMAG

MAG1: serving

LMA

21. HO is totally finished21

57

Time Line 1. Preparing HOMN pMAG MAGnMAG1 … LMA

TunnelServing

Beacon / Response to a probe

Link_detect


Link_Going_Down(Low confidence)

Link_Action(Link_Scan)

Link_Scan


Link_Going_Down(High confidence)

PoA ListResource Query

Target Decision=> MAG1

Low

58

Time Line 2. make before breakingMN pMAG MAG1 LMA

Tunnel

Inform that virtual PBU is finished

Trigger_L3_HOVirtual PBU

BCE UpdateVirtual PBA

Packet forwarding(destined for MN)

Packet forwarding(from MN)

L2 connection(new if)

59

Time Line3. Complete L2 HO MN pMAG MAG1 LMA

Tunnel

L2 HO

Trigger_L2_HOBCE Update

Link_down Link_down

Packet cachingPacket caching

Serving

HO complete

release

BCE Release

RS

RA

60

Agenda


61

Problems to be solved

Complexity MIH signaling

Rollback procedure Rapid and sudden movement of MN

Have to consider unexpected actions

62

Ns-2 status

Modification for MIH (NS-2.29) Link_detected Link_Going_Down

Source analysis for MIPv6 Mobiwan Based on NS2.26/NS2.27

63

Comments & Questions

1 handover for pmipv6 using mih kang joon-suk 姜 俊錫

Documents

1 handover for pmipv6 using mih kang joon-suk 姜俊錫