1 / 14

Mobile IPv6 Fast Handovers for 3G CDMA Networks

Mobile IPv6 Fast Handovers for 3G CDMA Networks. < draft- ietf -mipshop-3gfh-01.txt >. Hidetoshi Yokota KDDI Lab Gopal Dommety Cisco. Changes from -00 draft. A new fast handover sequence is added to align with 3GPP2 FHO work Additional message types are defined

rufin
Download Presentation

Mobile IPv6 Fast Handovers for 3G CDMA Networks

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. Mobile IPv6 Fast Handovers for 3G CDMA Networks <draft-ietf-mipshop-3gfh-01.txt> Hidetoshi Yokota KDDI Lab Gopal Dommety Cisco 67th IETF MIPSHOP WG

  2. Changes from -00 draft • A new fast handover sequence is added to align with 3GPP2 FHO work • Additional message types are defined • Security consideration is added • Additional handover information (aka “context”) can be exchanged during the handover signaling phase • Additional option is defined 67th IETF MIPSHOP WG

  3. Fast handover types • Predictive fast handover • Reactive fast handover • to apply RFC4068 to 3GPP2 fast handover procedures • Network-controlled fast handover • based on and to apply to “fast handover for HRPD (3GPP2 X.P0043)” 67th IETF MIPSHOP WG

  4. Network-controlled fast handover • The lower layer can provide necessary information for handover and support handover triggering • MN is not explicitly involved with fast handover • Two handover options • Immediate fast handover • Delayed fast handover 67th IETF MIPSHOP WG

  5. raw packet processed packet Immediate fast handover MN P-AN N-AN PAR NAR HA AAA MN-AAA sec. MN-AAA sec. Access-request (PMIP-supported) Link-layer connection (PPP) Access-accept (Root Key) PCoA Root Key BU (MN-AAA Auth) Access-Req/Accept BA Root Key packet(dst:PCoA) A16-HO Req/Initiate (PAR) A11-RRQ/RRP (Flow ID, PAR) HO Request (Flow ID, CID, GRE key) HO Response (Context, GRE key, Root Key, Immediate) Root Key [buffering] 67th IETF MIPSHOP WG

  6. raw packet processed packet Immediate fast handover (cont’d) MN P-AN N-AN PAR NAR HA AAA [buffering] movement packet(dst:PCoA) A11 (Active Start Airlink Record) (PPP setup is not needed) Context install complete Proxy BU (HoA, NAR, MN-AAA-Auth) Access-Req/Accept Proxy BA packet (dst:NAR) PPP IPv6CP + RA (NCoA assignment) NCoA BU (HoA, NCoA, MN-AAA Auth) Access-Req/Accept BA packet (dst:NCoA) 67th IETF MIPSHOP WG

  7. raw packet processed packet Delayed fast handover MN P-AN N-AN PAR NAR HA AAA MN-AAA sec. MN-AAA sec. Access-request (PMIP-supported) Link-layer connection (PPP) Access-accept (Root Key) PCoA Root Key BU (MN-AAA Auth) Access-Req/Accept BA Root Key packet(dst:PCoA) A16-HO Req/Initiate (PAR) A11-RRQ/RRP (Flow ID, PAR) HO Request (Flow ID, CID, GRE key) HO Response (Context, GRE key, Root Key, Delayed) Root Key [buffering] 67th IETF MIPSHOP WG

  8. Appendix 2/2 raw packet processed packet Delayed fast handover (cont’d) MN P-AN N-AN PAR NAR HA AAA [buffering] movement packet(dst:PCoA) A11 (Active Start Airlink Record) (PPP setup is not needed) Context install complete HO Ack (trigger to handover) Proxy BU (NCoA, HoA, MN-AAA-Auth) Access-Req/Accept Proxy BA packet (dst:NAR) PPP IPv6CP + RA (NCoA assignment) NCoA BU (MN-AAA Auth) Access-Req/Accept BA 67th IETF MIPSHOP WG packet (dst:NCoA)

  9. Combined handover procedure MN P-AN N-AN PAR NAR HA AAA | |HO initiation | | | | (a) | |.........>| | | | | | | |AN-AR connection establishment | (b) | | |/------------------\| | | | | |\------------------/| | | | | | | HReq | | | (c) | | | |<--------| | | | | | | HRes | | | (d) | | | |-------->| | | | | | | HAck | | | (e) | | | |<- - - - | | | | | | |forward packets | | (f) | | | |========>| | | | | | | +-----------+ | | | | | | | buffering | | | | | | | +-----------+ | | handover | | | | | | |radio-link conn. est. & AN-AR conn. activation | | (g) |/------------------\|/------------------\| | | |\------------------/|\------------------/| | | | | deliver packets | | | | (h) |<========================================| | | | | | | | BU | | (i) | | | | |------->| | | | | | | | Auth. | (j) | | | | | |<------->| | | | | | BA | | (k) | | | | |<-------| | | | deliver packets | | | | (l) |<========================================|<=======| | | | IPv6CP + RA | | | | (m) |<--------------------------------------->| | | | | | BU/BA | | | Auth. | (n) |<------------------------------------------------>|<------->| | | | | | | | 67th IETF MIPSHOP WG

  10. Differences in message type 67th IETF MIPSHOP WG

  11. Additional messages • Handover Request (HReq) • NAR -> PAR • Valid option: CVSE/NVSE (RFC3115) [type=38/124] • To request contexts 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 | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Subtype | Reserved | Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options ... +-+-+-+-+-+-+-+-+-+-+-+- 67th IETF MIPSHOP WG

  12. Additional messages (cont’d) • Handover Response (HRes) • PAR -> NAR • I flag: immediate (1)/delayed (0) • Valid option: CVSE/NVSE (RFC3115) [type=38/124] • To send requested contexts 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 | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Subtype |I| Reserved | Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options ... +-+-+-+-+-+-+-+-+-+-+-+- 67th IETF MIPSHOP WG

  13. Summary of change • “Network-controlled fast handover” is added to align with 3GPP2 FHO work • AR-originated BU/AR-terminated BA functionality is added • Limited to fast handover phase • Security consideration is added • Additional messages/option are added • Handover Request (HReq)/Handover Response (HRes) • Vendor specific extension (RFC3115) can be attached as an option to convey contexts 67th IETF MIPSHOP WG

  14. Next steps • Tighter liaison between 3GPP2 and IETF • More feedback from 3GPP2 • Keep track of 3GPP2/IETF work • Current 3GPP2 FHO work includes network-based mobility management feature, which is on-going work in IETF • The I-D will incorporate the results to get in sync and go forward 67th IETF MIPSHOP WG

More Related