Dean Bubley over at Disruptive Wireless has recently published an interesting post in which he wonders whether he has or will have a problem with Wi-Fi and femto offload in the future.
He describes how he is walking from his home to the tube station and his mobile device in the pocket picking up several known Wi-Fi hotspots from BT and connecting to them for a couple of seconds just to loose them again. This wreaks havoc on applications that are actively exchanging information over the network even when the phone is not actively used as the connection is dropped every time. An interesting point he makes there and I don't have a single and simple solution for it but some things come to my mind on how to deal with this:
On the Wi-Fi side:
- The connection manager could wait for a couple of seconds checking the signal strength and only connecting when it stays relatively constant, i.e. the user is not moving and hence, the Wi-Fi hotspot is worth using.
- Distinguish between public Wi-Fi hotspots where such rules should be applied and encrypted home / office hotspots for which it could apply different rules.
- A good Wi-Fi offload solution would be not to get a new IP address in every new hotspot and to break the 3G connectivity. Ideally, an IP tunnel is used so no matter whether connected over 3G or Wi-Fi the device would always use the same IP address. That would also deal with the security issues of unencrypted public Wi-Fi hotspots.
On the Femto side:
- I think there would be less of a problem here because GSM, UMTS and LTE offer myriads of possibilities to ensure a mobile only uses a femto if it is not moving.
- There is no need to assign a new IP address when hopping between femtos so connectivity would not be broken when jumping into or out of a femto.
- The connection can be handed over from and to a femto so continued connectivity with little or no outage can be ensured.
- Access to a femto can be restricted. This book goes into the details of this.