Amazon Tech Support

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

Thursday, 20 June 2013

WiFi - the coming indoor vs. outdoor divide

Posted on 00:46 by Unknown
I've been speaking to assorted vendors recently about their plans for carrier WiFi, linked to the usual rhetoric about Hotspot 2.0, ANDSF, so-called "seamless" authentication and so forth.

I still contend that a lot of this is nonsense - the mobile operators are only one group in an increasingly complex ecosystem of stakeholders interested in WiFi. The end-users, venue-owners, tenants, fixed/cable ISPs, device vendors, OS suppliers, content players, app providers, employers, advertisers and local government all have "skin in the game" with helping users connect to WiFi. Mobile operators are not "special flowers" among that group - and certainly have no likelihood of enforcing their will about when and where users will connect; much less charge them or subject them to onerous policy controls.

But I'm starting to spot a subtle distinction: indoor vs. outdoor use.

In an indoor environment,  users are used to WiFi being provided by their hotel, cafe, airport, home, office or other sponsor. Increasingly it is free, but perhaps with a small "hoop" to jump through such as watching an advert, or asking a barista for a code. Usually, the access point and backhaul are controlled by the venue or tenant, although a 3rd-party like a wireless ISP might be contracted to provide these. There will be an expectation that any person in that venue - irrespective of which cellular operator(s) they might use - will have access to WiFi, especially as many devices like PCs and tablets are WiFi-only anyway.

This is very different from outdoors.

Outdoors, people are properly "mobile", ie moving-about. They get access from only one provider - their cellular operator. Any other stakeholders like MVNO hosts, network-sharing consortia, site owners and so forth are hidden behind the "Operator X" logo displayed on the phone's screen. People accept and except that different operators will have different coverage, and that they do indeed expect "seamless" handoff from cell to cell.

Outdoors, the HetNet vision makes more sense - macrocell, picocell, femtocell - and, yes, maybe WiFi - owned and operated by the telco, may be used to provide decent data connectivity, as well as telephony and SMS.

While a few cities now have outdoor WiFi provided by a local council or company, that remains rare. People don't have expectations about outdoor WiFi behaviour the same way they do inside a building. A smartphone's WiFi essentially becomes a single-stakeholder environment (or two including the user) in the street, or perhaps a few special locations like aircraft.

In summary;

Indoor WiFi = multi-stakeholder, too complex for the 3GPP/WBA/OMA/GSMA model of operator control and network integration. Limited relevance of ANDSF, carrier-driven Hotspot 2.0, SIM authentication. Largely a UX problem.

Outdoor WiFi = fewer stakeholders, more chance for direct integration & seamlessness. Although complexities where the user could access WiFi as well as 3G/4G metrocells & macrocells. Largely a RAN/policy problem.

The other meta-problem comes from how to know when to switch from carrier-WiFi mode to multi-stakeholder WiFi mode as you enter or exit a venue. Linked to all this is a rather thorny issue of pricing and perceived value.

For many years, the mobile industry has assumed that "nomadic" use of its network was a core part of its proposition, as well as when users are "truly mobile". While that might have been the case for telephony - an indoor mobile call is "worth" as much as an outdoor one - that no longer holds true for data. The assumption (increasingly, although varying by country) is that indoor data is free - provided as an amenity, equivalent to air-conditioning or lavatories. Carrier-provided indoor WiFi will be accepted by end-users as long as it is not charged against data plans, or subject too stricter policy controls than "native" WiFi. This is going to be as much a challenge for billing & charging systems as it is for the network.

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

  • The Number 1 problem for "seamless" models of WiFi offload / network selection
    I frequently argue against the assumption that "seamless" connection to WiFi is practical or desirable, especially for the general...
  • 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...
  • Part of Nokia's problem - making Ovi compelling
    I've got a Nokia Ovi account somewhere. Signed up for it ages ago, to play around with the Ovi Store when I had an N97 to play with, ba...
  • Putting a value on customer data with reference to offload
    There continues to be a ferocious discussion about AT&T's new data plans - and also, as I commented a couple of weeks ago, about the...
  • 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...
  • For telcos, "Monetising OTT" is about distribution partnerships & revshare, not QoS or termination fees
    A couple of years ago, I moderated a panel session at a conference on broadband business models and "traffic management". It was o...
  • BT WiFi smartphone application
    I've just seen BT's announcement of its new iPhone and Android app, offering free WiFi access at its Openzone and FON hotspots to i...
  • An update on @DApremium - the world's first paid Twitter channel. Now available with quarterly or annual subscriptions
    It's now been six weeks since I announced the launch of @DApremium , my second Twitter stream - one which is available only to paid subs...
  • 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...
  • There really needs to be a "User tariff API" for developers
    Generally speaking, app developers and website owners know what device you've got, what OS, and what browser. Furthermore, they know wha...

Blog Archive

  • ▼  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ▼  June (6)
      • What I'm looking for at this week's WebRTC Confere...
      • WiFi - the coming indoor vs. outdoor divide
      • WebRTC partnerships and ecosystems
      • Disruptive Analysis WebRTC Q2 Update: Forecasts up...
      • Is Israel about to ban carrier WiFi offload?
      • Delayed WebRTC standards may have unexpected side-...
    • ►  May (5)
    • ►  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