Fast handovers for PMIPv6

Hidetoshi Yokota KDDI LabKuntal Chowdhury Starent NetworksRajeev Koodli Nokia Research CenterBasavaraj Patil Nokia Siemens Networks

IETF #69 Chicago

2

Background and motivation PMIPv6 is expected to be adopted in multiple SDOs (e.g. 3GPP

SAE, 3GPP2 CAN) Service continuity during inter access gateway handover is critic

al for real-time applications

WiMAX3GPP2 CAN

EPS HA

P-GW/S-GW/MME

non-3GPPGW

AGW AGW ASN-GW ASN-GW

HA HA

R3(PMIPv6?)

R4

U16(PMIPv6)

U15

S2a(PMIPv6)

BS BSeBS eBSeNodeB

Non-3GPPRAN

3GPP SAE

3

Background and motivation (cont’d)

FMIPv6 can be a common protocol for IP-level fast handover

FMIPv6 is designed for MIPv6 Adaptation to PMIPv6 is needed It became clearer that context transfer is as

much important as bearer packet forwarding to expedite the mobility management Enhancement of FMIPv6 for context transfer is desired

4

Design principles

Reuse FMIPv6 as much as possible Minimum amendments for PMIPv6

MN is not involved with FMIP signaling RtSolPr, PrRtAdv, FBU, FBAck and FNA are not used or re

placed by lower layer signaling Context transfer is realized by FMIP signaling

Context is transferred by HI/Hack message exchange Context information independent of access technologies are

defined (e.g. NAI, MN-HoA…) Context information dependent on access technologies are

defined as Vendor-specific option

5

MN

Predictive fast handover (PAR initiated)PAR NAR

HI

P-AN N-ANReport(MN ID,

New AP ID)

(HO initiate, (MN ID, New AP ID)

AN-AR connection establishment(substitute for FNA)

HAck

PBU

PBA

PARPAR NARNAR MN LLAMN LLA

LMA

MN-AN connectionestablishment

IPA(PCoA)IPA(PCoA) IPA(NCoA)IPA(NCoA)

PARPAR NARNAR MN IDMN ID IPA(MH-HoA)IPA(MH-HoA) IPA(LMA)IPA(LMA)

NARNAR PARPAR IPA(NCoA)IPA(NCoA)

NARNAR PARPAR MN IDMN ID

handover

FMIPv6

PFMIPv6

6

MN

Reactive fast handover (NAR initiated)PAR NAR

HI

P-AN N-AN

AN-AR connection establishment(substitute for FNA)

HAck

PBU

PBA

PARPAR NARNAR MN LLAMN LLA

LMA

MN-AN connectionestablishment

IPA(PCoA)IPA(PCoA) IPA(NCoA)IPA(NCoA)

PARPAR NARNAR MN IDMN ID

NARNAR PARPAR IPA(NCoA)IPA(NCoA)

NARNAR PARPAR MN IDMN ID

handover

IPA(MH-HoA)IPA(MH-HoA) IPA(LMA)IPA(LMA)

CRO(MH-HoA, LMA)CRO(MH-HoA, LMA)

7

MN

[Reference] Packet transfer between MN and CN/HA (FMIPv6)

PAR NAR

PARPAR NCoANCoA CN/HACN/HA PCoAPCoA DL dataDL data

encapsulation

decapsulation

NCoANCoA PARPAR PCoAPCoA

HI/HAck

CN/HA

CN/HACN/HA PCoAPCoA DL dataDL data

PCoAPCoA

CN/HACN/HA UL dataUL data

CN/HACN/HA UL dataUL data

handover

decapsulation

FBU

PARPAR NCoANCoA CN/HACN/HA PCoAPCoA DL dataDL dataCN/HACN/HA PCoAPCoA DL dataDL data

PCoAPCoA CN/HACN/HA UL dataUL data

DL dataDL data

NCoANCoA PARPAR

CN/HACN/HA PCoAPCoA DL dataDL data

encapsulation

8

LMALMA

MN

Packet transfer between MN and CN(PFMIv6)

PAR NAR

PARPAR NARNAR CNCN HoAHoA DL dataDL data

LMA

CNCN HoAHoA DL dataDL datadecapsulation

HoAHoA

NARNAR PARPAR HoAHoA

HI/HAck

CN

CNCN HoAHoA DL dataDL dataPARPAR CNCN HoAHoA DL dataDL dataCNCN HoAHoA DL dataDL data

encapsulation

PARPAR LMALMA HoAHoA HoAHoA

CNCN UL dataUL data

CNCN UL dataUL data CNCN UL dataUL data

CNCN UL dataUL data

handover

re-encapsulation

PMIPv6 tunnel

FMIPv6 tunnel

encapsulation

9

New options for context transfer

Major and common context information NAI new option Tunnel-ID new option MN-HoA new option-code for IP Address option LMA new option-code for IP Address option

Technology-dependent context information Vendor-specific option new option

Context Request Option new option Option to request context information (see next slide)

10

New options for context transfer Context Request Option

The Length field is in units of 8 octets (RFC4068) 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +---------------+---------------+---------------+---------------+ | Type | Length | Option-Code | Reserved | +---------------------------------------------------------------+ | Reserved | +---------------+---------------+-------------------------------+ | Req-type-1 | Req-option-1 | Padding | +---------------------------------------------------------------+ | Padding | +---------------+---------------+-------------------------------+ | Req-type-2 | Req-option-2 | Vendor-ID | +-------------------------------+-------------------------------+ | Vendor-ID | VS-Type | +---------------------------------------------------------------+ | ... |

When requested option is Vendor -specific option

requested option

commonoption header

11

Related work “Mobile Node Agnostic Fast Handovers for Proxy Mobile IPv6”

Context transfer: HI/HAck for predictive FHO, FBU/FBAck for reactive FHO

HI/HAck are ICMP, whereas FBU/FBAck are IP w/MH All options except MH LLA option are ICMP option FBU/FBAck are not suitable for context transfer

HI/HAck should be used HI/HAck are identical to RFC4068

Behaviors of PAR/NAR are different from RFC4068 MIPv6 and PMIPv6 operations could be coexistent HI/HAck for PMIPv6 should be distinguished

LUP message between t-BS and NMAG may be ok for 802.16e, but not for 3G

12

Way forward

Fast handover protocol for PMIPv6 is important work should be in the charter MIPSHOP WG is a more appropriate place to discuss fast hando

ver??

Fast handover protocol for PMIPv6 should be common to various access technologies that (potentially) use PMIPv6 3GPP, 3GPP2 (and WiMAX) Common context information and call flows should be specified