WiSwitcher: an efficient client for managing multiple APs
Proceedings of the 2nd ACM SIGCOMM workshop on Programmable routers for extensible services of tomorrow
Proceedings of the fifth ACM international workshop on Mobility in the evolving internet architecture
Intentional networking: opportunistic exploitation of mobile network diversity
Proceedings of the sixteenth annual international conference on Mobile computing and networking
Fair WLAN backhaul aggregation
Proceedings of the sixteenth annual international conference on Mobile computing and networking
Spider: improving mobile networking with concurrent wi-fi connections
Proceedings of the ACM SIGCOMM 2011 conference
Concurrent Wi-Fi for mobile users: analysis and measurements
Proceedings of the Seventh COnference on emerging Networking EXperiments and Technologies
Hi-index | 0.00 |
There are many situations in which an additional network interface—or two—can provide benefits to a mobile user. Additional interfaces can support parallelism in network flows, improve handoff times, and provide sideband communication with nearby peers. Unfortunately, such benefits are outweighed by the added costs of an additional physical interface. Instead, virtual interfaces have been proposed as the solution, multiplexing a single physical interface across more than one communication endpoint. However, the switching time of existing implementations is too high for some potential applications, and the benefits of this approach to real applications are not yet clear. This paper directly addresses these two shortcomings. It describes a link-layer implementation of a virtual 802.11 networking layer, called Juggler, that achieves switching times of approximately 3 ms, and less than 400 \mu{\rm s} in certain conditions. We demonstrate the performance of this implementation on three application scenarios. By devoting 10 percent of the duty cycle to background tasks, Juggler can provide nearly instantaneous handoff between base stations or support a modest sideband channel with peer nodes, without adversely affecting foreground throughput. Furthermore, when the client issues concurrent network flows, Juggler is able to assign these flows across more than one AP, providing significant speedup when wired-side bandwidth from the AP constrains end-to-end performance.