Amazon Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Wednesday, 29 May 2013

The Number 1 problem for "seamless" models of WiFi offload / network selection

Posted on 03:05 by Unknown
I frequently argue against the assumption that "seamless" connection to WiFi is practical or desirable, especially for the general case of smartphones or tablets being "pushed" automatically to connect via a combination of technologies and new standards like Passpoint, Hotspot 2.0, ANDSF and EAP-SIM.

I thought it was worth stressing and clarifying the single most problematic use-case:

Worst case scenario: A device automatically being connected to paid or overly policy-managed carrier-WiFi, when a free alternative is readily available

Nothing will cause customer dissatisfaction & churn faster than incurring additional costs (or additional usage against a quota) than this. Expect lawyers, regulators, consumer press & commentators to throw very large & painful bricks at you if it occurs. And probably device & OS vendors too.

The classic example that most readers of this blog will be familiar with is attending a conference in a hotel with expensive WiFi, but where the event organisers give you a free code, or even set up their own APs for better performance/lower cost. We'd be deeply annoyed if our phones "roamed onto" the local WiFi automatically, unless the usage was 100% free as well. Similar story if your frequent-flyer lounge has free WiFi, but your devices magically jumped onto the paid/roamed WiFi in the main airport hall.

I am writing this on a laptop, with two phones by my side, in Starbucks in London. There is free WiFi (provided by BT Openzone in this case). You typically log on via a very simple splash page and selecting an obvious Openzone-Starbucks SSID. A very small "seam" indeed. Alternatively, I can use the BT WiFi app I have on my phones for free, or login on the "normal" BT Openzone SSID page, because I have BT Broadband at home. I'd be irritated if I was automatically shunted to one of my CellCo's SSIDs instead, with their charging and policy being applied.

Same thing in hundreds of other situations too - restaurants, pubs, offices, friends' homes, public buildings and so forth. There is free WiFi - often very good too - easily obtainable from a source other than the cellular operator. There are multiple stakeholders here - the venue, advertisers, content companies, fixed operators, your device supply, your employer and so forth. All might have negotiated a better "private" WiFi experience than your cellular provider at that location.

Not only that, but the cellular WiFi option might be subject to onerous policy restrictions (eg VoIP blocking) which don't apply when you use WiFi in "private" mode. 

There must be an easy and obvious way to manage this - and not just buried 7 layers down in the menus with some obscure configuration settings. The alternative is that the carrier WiFi is 100% free, 100% unmetered, in which case people won't care about the other options. That is why Apple is happy with AT&T and some other operators doing automated WiFi log-on, as it's in a customer-friendly form. One other possible option is that the operator (instead of charging you) gives you extra free stuff such as exclusive content to tempt you onto its WiFi option.

Seams are often there for good reasons, as well as bad. Seams can be monetised; seams can present the user with important information or choices. In some cases automation and "frictionless" connection in desirable, while in other cases it's not. Mobile operators are just one (often minor) stakeholder in the overall WiFi ecosystem, and need to stop arrogantly assuming that their WiFi choices trump either users', or other parties. Unless and until Hotspot 2.0 and its related standards fully and explicitly recognise these choices, it's dead in the water.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Mobile social networking - how I'll know when it's going mainstream....
    This falls into the category of "amusing personal anecdotes" rather than "rigorous industry analysis". But it also refle...
  • Forget lobbyists, this is how Net Neutrality gets enacted in law....
    I've long held that the Internet will always find ways around any blocking/filtering mechanisms for certain types of application, especi...
  • UK ISPs Code of Practice on Traffic Management - OK as a start, but major flaws
    A group of the UK's largest fixed and mobile ISPs have published a "Code of Practice" about managing traffic on their broadban...
  • The mobile industry buzzword of 2009 will be......
    OFFLOAD This year has been all about mobile broadband revenue and traffic growth. Dongles, iPhones, embedded PCs, Android, consumer BlackBer...
  • The danger of "cutting the cord" - where's the femtocell going to go?
    I see many references to people wanting to "cut the cord", and have an all-mobile home. This is particularly the case in the US, w...
  • The "Social web" - does anyone actually want it?
    Is this another example of The Emperor's New Clothes? I've lost count of the number of pitches I've heard recently along the lin...
  • The Novatel MiFi - possibilities for new mobile broadband business models
    OK, I realise that I've been a bit grumpy and critical of some things recently. But before everyone assumes I'm getting more cantank...
  • Is it just me, or is 3G either really good or really bad, but rarely "OK"
    I've started noticing that my experience of mobile broadband (iPhone 3GS on Voda UK) is much more polarised than that of fixed broadband...
  • What's the story with the Phonejack 'femtocell"?
    I'm now trying to catch up with events and analysis over the past few weeks, as I've been on vacation. One of the more bewildering t...
  • Android - the retail experience
    I just stopped off at my local branch of Carphone Warehouse on a whim, to have a quick look at what's being sold and how. (By coincidenc...

Blog Archive

  • ▼  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ▼  May (5)
      • The Number 1 problem for "seamless" models of WiFi...
      • WebRTC - how to get support into old browsers?
      • Telcos need to offer 2+ separate voice application...
      • An RCS use-case I'd actually support & see as viable
      • There is no "messaging market"
    • ►  April (1)
    • ►  March (3)
    • ►  February (3)
    • ►  January (5)
  • ►  2012 (46)
    • ►  December (5)
    • ►  November (4)
    • ►  October (3)
    • ►  September (2)
    • ►  August (4)
    • ►  July (3)
    • ►  June (1)
    • ►  May (6)
    • ►  April (4)
    • ►  March (1)
    • ►  February (9)
    • ►  January (4)
  • ►  2011 (73)
    • ►  December (4)
    • ►  November (10)
    • ►  October (8)
    • ►  September (6)
    • ►  August (3)
    • ►  July (5)
    • ►  June (7)
    • ►  May (9)
    • ►  April (4)
    • ►  March (7)
    • ►  February (6)
    • ►  January (4)
  • ►  2010 (130)
    • ►  December (4)
    • ►  November (10)
    • ►  October (10)
    • ►  September (6)
    • ►  August (9)
    • ►  July (7)
    • ►  June (19)
    • ►  May (19)
    • ►  April (11)
    • ►  March (18)
    • ►  February (7)
    • ►  January (10)
  • ►  2009 (126)
    • ►  December (4)
    • ►  November (14)
    • ►  October (9)
    • ►  September (8)
    • ►  August (9)
    • ►  July (10)
    • ►  June (21)
    • ►  May (14)
    • ►  April (2)
    • ►  March (11)
    • ►  February (15)
    • ►  January (9)
  • ►  2008 (94)
    • ►  December (24)
    • ►  November (26)
    • ►  October (25)
    • ►  September (19)
Powered by Blogger.

About Me

Unknown
View my complete profile