Design and Analysis of the FHCoP-B Scheme for Fast Handoff Support in the Nested Mobile Network

Abstract

In the past, our proposed HCoP-B has achieved route optimization and resolved the RO-storm problem for handoffs of the nested mobile network. However, because HCoP-B is a pure layer three, i.e., network layer, approach which handoff operations are performed after the layer two, i.e., data link layer, link breaks, it still suffers from a long handoff latency and serious packet losses. In this paper, by adopting the handoff prediction concept of the fast mobile IPv6 on HCoP-B, our cross-layer architecture, which is called the fast HCoP-B (FHCoP-B), can trigger HCoP-B layer three route optimization flow by 802.11 and 802.16 link events before the actual Layer 2 handoff occurs. In this way, FHCoP-B further shortens both the handoff latency and packet losses of HCoP-B.

Reactive fast handover mechanisms in the nested mobile networks

“…The NMAP caches the first subsequent packet from the time it receives the GBAck from the CN after the RR procedure until the time it receives the FBAck from the PMAP after the HI/HAck procedure. Hence, the total buffering time of case 1 of this scenario is equal to the NMAP buffering time for subsequent packets, which is formulated as (4). However, that of case 2 is zero.…”

“…We have also integrated HCoP-B with the fast handover mechanism incurred by layer 2 (L2) 802.11 and 802.16 triggers as predictive FHCoP-B [4]. With the predictive FHCoP-B, all MNs and MRs of the whole nested NEMO during handover can acquire their new care-of address (CoA), perform duplicate address detection (DAD) for these CoAs and execute global binding updates and return routability (RR) to their home agents (HA) and correspondent nodes (CN) before the nested NEMO has completed its association with the new L2 link.…”

Performance Analysis of Reactive FHCoP-B in Nested Mobile Networks

“…In the past, we have proposed the HCoP-B scheme [4] to achieve route optimization (RO) for packet transmission in the nested NEMO. We have also integrated HCoP-B with the fast handover mechanism incurred by layer 2 (L2) 802.11 and 802.16 triggers as the proactive FHCoP-B [5] to further reduce its handover latency. However, there are two scenarios that proactive FHCoP-B cannot complete its operations if the link down event occurs too early due to fast movements of the NEMO.…”