1 / 12

Fast handovers for PMIPv6

Fast handovers for PMIPv6. Hidetoshi Yokota KDDI Lab Kuntal Chowdhury Starent Networks Rajeev Koodli Nokia Research Center Basavaraj Patil Nokia Siemens Networks. IETF #69 Chicago. Background and motivation. PMIPv6 is expected to be adopted in multiple SDOs (e.g. 3GPP SAE, 3GPP2 CAN)

pfinn
Download Presentation

Fast handovers for PMIPv6

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. Fast handovers for PMIPv6 Hidetoshi Yokota KDDI Lab Kuntal Chowdhury Starent Networks Rajeev Koodli Nokia Research Center Basavaraj 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 critical for real-time applications 3GPP SAE WiMAX 3GPP2 CAN EPS HA HA HA S2a (PMIPv6) U16 (PMIPv6) R3 (PMIPv6?) U15 R4 P-GW/ S-GW/ MME non-3GPP GW AGW AGW ASN-GW ASN-GW Non-3GPP RAN BS BS eBS eBS eNodeB

  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 replaced 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. NAR PAR MN ID Predictive fast handover (PAR initiated) MN P-AN N-AN PAR NAR LMA Report (MN ID, New AP ID) (HO initiate, (MN ID, New AP ID) HI FMIPv6 PAR NAR MN LLA IPA(PCoA) IPA(NCoA) PAR NAR MN ID IPA(MH-HoA) IPA(LMA) PFMIPv6 HAck NAR PAR IPA(NCoA) handover MN-AN connection establishment AN-AR connection establishment (substitute for FNA) PBU PBA

  6. NAR PAR MN ID handover Reactive fast handover (NAR initiated) MN P-AN N-AN PAR NAR LMA MN-AN connection establishment AN-AR connection establishment (substitute for FNA) HI PAR NAR MN LLA IPA(PCoA) IPA(NCoA) PAR NAR MN ID CRO(MH-HoA, LMA) HAck NAR PAR IPA(NCoA) IPA(MH-HoA) IPA(LMA) PBU PBA

  7. [Reference] Packet transfer between MN and CN/HA (FMIPv6) MN PAR NAR CN/HA CN/HA PCoA DL data CN/HA PCoA DL data FBU HI/HAck PAR NCoA handover CN/HA PCoA DL data encapsulation decapsulation PAR NCoA CN/HA PCoA DL data DL data CN/HA PCoA DL data NCoA PAR UL data PCoA CN/HA encapsulation NCoA PAR PCoA CN/HA UL data PCoA CN/HA UL data decapsulation

  8. Packet transfer between MN and CN(PFMIv6) MN PAR NAR LMA CN LMA PAR CN HoA DL data CN HoA DL data CN HoA DL data HI/HAck PMIPv6 tunnel handover PAR NAR DL data CN HoA encapsulation FMIPv6 tunnel CN HoA DL data decapsulation HoA CN UL data NAR PAR HoA CN UL data encapsulation PAR LMA HoA CN UL data HoA CN UL data re-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 | +---------------------------------------------------------------+ | ... | commonoption header requested option When requested option is Vendor -specific option

  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 handover?? • 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

More Related