100 likes | 237 Views
Mobile IPv6 Fast Handovers for 3G CDMA Networks. <draft-yokota-mipshop-3gfh-02.txt>. Hidetoshi Yokota KDDI Lab Gopal Dommety Cisco. 65 th IETF MIPSHOP WG. Focus of this I-D. Implement fast handovers in 3G CDMA networks Adaptation of FMIPv6 (RFC4068) to 3G CDMA networks
E N D
Mobile IPv6 Fast Handovers for 3G CDMA Networks <draft-yokota-mipshop-3gfh-02.txt> Hidetoshi Yokota KDDI Lab Gopal Dommety Cisco 65th IETF MIPSHOP WG
Focus of this I-D • Implement fast handovers in 3G CDMA networks • Adaptation of FMIPv6 (RFC4068) to 3G CDMA networks • FMIPv6 extensions • Clarifications • Link-layer connection in the new network can be simplified by introducing FMIPv6 • bootstrapping parameters can be obtained in FMIPv6 operation • Selective bi-casting is considered • multiple/single IF(s) • bicasting at PAR/HA
Available information for the target network pilot channels cell information serving nodes location of BS or MN MN Handover trigger & information in 3G CDMA networks 3G core network PAR NAR P-AN N-AN BS BS BS report C/I estimates pilot channel “Handover assist information”
Issues and possible solutions (1) • The FBU may be delayed and the MN gets to the NAR before the handover is detected • bi-casting does not solve this situation • it is more effective in the predictive mode • If the predictive mode is failed, it falls back to the reactive mode (Sec 3.2 #2 in RFC4068) • a delayed FBU was not well taken into consideration in the previous (-01) I-D
pFBU: transmitted in the previous network nFBU: transmitted in the new network Delayed FBU (case 1) MN P-AN PAR NAR RtSolPr PrRtAdv pFBU handover Link-layer connection establishment+bootstrapping (3) FNA[nFBU] (2) nFBU HI (Code:1) HAck reactive mode (1) discard FBAck forwarding
Delayed FBU (case 2) MN P-AN PAR NAR RtSolPr PrRtAdv pFBU handover Link-layer connection establishment+bootstrapping (3) address validity check FNA[nFBU] HI (Code:0) reactive mode HAck (reject; Code:128-130) (2) nFBU HI (Code:1) reactive mode HAck (1) FBAck forwarding
Delayed FBU (case 3) MN P-AN PAR NAR RtSolPr PrRtAdv pFBU address validity check handover Link-layer connection establishment+bootstrapping predictive mode HI (Code:0) (3) HAck (accept) FBAck FNA[nFBU] forwarding accept FNAignore nFBU reactive mode (2) reactive mode (1)
Issues and possible solutions (2) • NAR is resolved by PAR with the New AP LLA • In 3G networks, New AP LLA is not used • Handover assist information should be used • The length of the LLA Option is in units of 8 octets • Length of handover assist information may be information-specific • In the last l-D, a new option-code in the LLA option was defined • New Option is defined to convey handover assist information
New option for vendor-specific handover information 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 | VS-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VS-Value... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type T.B.D. Length The size of this option in 8 octets including the Type, Length, Option-Code and VS-Length fields. Option-Code Indicates the particular type of vendor-specific information. This value is administrated by the vendor or organization that uses this option. VS-Length The size of the VS-Value field in octets. VS-Value Zero or more octets of vendor-specific information data.
Summary of primary changes from -01 draft • Consideration of delayed FBU • When HI arrives at the NAR before FNA [FBU], it should behave as the predictive mode • otherwise, it should behave as the reactive mode • New option to convey handover assist information is defined instead of extending LLA option