Light Reading Mobile – Telecom News, Analysis, Events, and Research

Heavy Lifting Analyst Notes  

Carrier Wi-Fi: Always Best Connected

May 13, 2013 | Gabriel Brown |
Wi-Fi is a great technology -- I love it. (Well, like it a lot.) So much so, in fact, that I’m leading Light Reading’s 2013 Service Provider Wi-Fi Industry Initiative. The aim of the initiative is to look at how network operators can scale and accelerate investment in Wi-Fi -- and, of course, why they should.

The technology is well suited to indoor mobile data consumption -- that much we know. And the fact that around half of smartphone data usage is already over Wi-Fi today explains why operators should engage. There's also an opportunity for operators to better exploit the product volume that characterizes the Wi-Fi ecosystem, and the Wi-Fi R&D investment paid for by other people. It's not quite a free ride, but the economics can be compelling.

Let's take it a bit easy on the hype, however, and ask why a majority of operators -- and specifically mobile operators -- haven’t yet made the big bet on Wi-Fi investments? (There are one or two notable exceptions, of course.) Fundamentally, the reason is that the way Wi-Fi works in smartphones today puts it squarely outside the mobile operator's sphere of influence.

One area that crystallizes this issue is connectivity management, and the tendency for smartphones to automatically connect to "bad Wi-Fi" that interrupts, and even breaks, the user experience. Consider the following scenarios, where a smartphone, under its own auspices, might detach itself from a functioning mobile network in favor of "broken" Wi-Fi:

  • Border conditions. Most of us will have experienced being on the very edge of Wi-Fi coverage (in the garden, example), or where there's interference from neighboring access points, and performance is poor as a result. Yet the device still reaches to connect.
  • Skinny backhaul. Wi-Fi is a high-speed radio interface (under the right conditions), but that doesn’t matter much if it's connected to a slow Internet connection. Anyone who's ever tried to use hotel Wi-Fi knows what I’m talking about.
  • On the move. Automatically connecting to known Wi-Fi SSIDs at bus stops, rail stations, traffic lights, or the like might not be the worst thing in the world, but it is annoying.
  • Overloaded networks. Where devices connect to networks that, while not saturated, may already be heavily used, resulting in poor performance for the user and everybody else attached to that access point.
  • Associated but not authorized. You’ve visited this Wi-Fi SSID in the past, so your device attaches automatically, but does not actually connect to the Internet until you log in or pay via captive portal. Again, annoying.

Scenarios such as these explain why mobile operators have preferred to take a hands-off approach and why, to date, they have tended to see Wi-Fi as a tactical rather than strategic technology. Smartphone vendors, meanwhile, have added manual on/off "Wi-Fi toggles" to their devices, and like operators, have been content to excuse themselves from getting involved in what they see as somebody else's problem.

This state of affairs is not a catastrophe, but it feels like a compromise and fudge. The solution is for operators, together with the industry at large, to work to automate network selection and connectivity management. By ensuring that users are always best connected, operators can better take advantage of Wi-Fi technology and economics.

— Gabriel Brown, Senior Analyst, Heavy Reading

Psst: As part of Light Reading's 2013 Carrier Wi-Fi Industry Initiative, I'm hosting a webinar on Accelerating & Scaling Carrier Grade Wi-Fi on Tuesday, May 14, at 12 Noon EST. Click Here to Register.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Related Content
White Papers SPONSORED CONTENT
Featured