An empirical analysis of the IEEE 802.11 MAC layer handoff process
ACM SIGCOMM Computer Communication Review
Improving the latency of 802.11 hand-offs using neighbor graphs
Proceedings of the 2nd international conference on Mobile systems, applications, and services
IMC '05 Proceedings of the 5th ACM SIGCOMM conference on Internet Measurement
Initiative movement prediction assisted adaptive handover trigger scheme in fast MIPv6
Computer Communications
WLAN cell handoff latency abatement using an FPGA fuzzy logic algorithm implementation
Advances in Fuzzy Systems - Special issue on High Performance Fuzzy Systems for Real World Problems
Scanless fast handoff technique based on global Path-Cache for WLANs
The Journal of Supercomputing
| Hi-index | 0.00 |
IEEE 802.11 Wireless LANs are increasingly being used in enterprise environments for broadband access. Such large scale IEEE 802.11 WLAN deployments implies the need for client mobility support; a mobile station has to be "handed off" from one Access Point to another. Seamless handoff is possible for data traffic, which is not affected much by the handoff delay. However, voice traffic has stringent QoS requirements and cannot tolerate more than 50ms net handoff delay. The basic IEEE 802.11 handoff scheme (implemented in Layers 1 & 2) only achieves a handoff delay of 300ms at best, leading to disrupted connectivity and call dropping. The delay incurred in scanning for APs across channels contributes to 90% of the total handoff delay. In this paper, the FastScan scheme is proposed which reduces the scanning delay by using a client-based database. The net handoff delay is reduced to as low as 20 ms for IEEE 802.11b networks. We next suggest "Enhanced FastScan" that uses the direction and relative position of the client with respect to the current AP to satisfy the latency constraint in IEEE 802.11a scenarios, which have significantly higher scanning delays due to the larger number of channels. The proposed schemes do not need any changes in the infrastructure (access points) and require only a single radio and a small cache memory at the client side.