Amazon Tech Support

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

Monday, 21 June 2010

If mobile data billing takes too long to change, device-based intelligence will fill the gap

Posted on 01:01 by Unknown
My recent posts have discussed the issue of femto-originated data traffic being charged against the same caps and policies as macro traffic. I think that this is likely to be seen negatively by many consumers - it is fundamentally unjustifiable, as the cost-bases are so different.

It reminds me of one of the problems with many implementations of earlier voice FMC services such as UMA or VCC - where a mobile call is terminated via WiFi and the user's own fixed broadband network rather than the inbound operator's cellular infrastructure, the justification for keeping the call termination wholesale fees the same diminish. In that case, the customer (and the originating operator) is paying not just for a network it's not using, but for spectrum as well.

The problem is that it's very difficult for billing and rating engines to take account of cost differentials involved in a given call or data stream - not least because most operators don't really have neat and accurate per-min or per-MB costs, and it can vary according to lots of specific circumstances. The cost of connecting to a voicemail server is different to connecting to a phone; the cost of a call in a rural area is different to a city centre and so on.

So operators just take a broad average, reflected in the retail and wholesale prices and hope that people don't nit-pick too much - at least not so much that the regulator gets involved.

While I think that's fair enough - we're never going to get precise cost-based pricing even if we want it - it doesn't excuse the most *egregious* examples of iniquity. The femto vs. WiFi traffic against mobile data cap issue does seem pretty egregious, because there's an immediate A-to-B comparison available to the end user.

The industry spends a huge amount of time telling us that "customers don't care what technology they use, they just want to get connected". Which is fine, but only if there's no glarig differences in price and performance.

This comes back to my assertion that there is a need for holistic approaches to mobile data traffic management - combining all the various bits of the puzzle to offload / charge / optimise mobile traffic so that this type of head-smacking event and potential PR/loyalty disaster doesn't occur.

Although we still haven't got a detailed comment from AT&T (and Vodafone does the same) about their billing system, it is not uncommon for any major changes to take a considerably long time to implement. That's especially true in cases, such as here, where AT&T was also moving its whole system from flat-rate charging to tiered-and-capped. They may well have been aware of the femto vs. cap unfairness, but decided that it would take too long, or involve too much risk, to address that at the same time as the more general switch-over in policy and charging.

This situation is likely to be repeated throughout the data traffic management arena, in various scenarios. It is *theoretically* possible to hook various bits of the policy/charging/optimisation infrastructure up to the radio network, or other bits of the carrier's machinery. But it's not easy, it's not cheap, and it's not quick.

That leads me to think that there will have to be some short-term workarounds that are easier to implement. Top of my list is smart connection-management clients for smartphones and laptops, which have awareness of tariffs, data consumption and different access methods. "Are you sure you want to connect via the 3G femtocell? I can easily register with this nearby WiFi if you want free connectivity".

It will be interesting to see if the slowness of creating sensible end-to-end traffic management and billing priniciples in the OSS/BSS leads to the device intelligence taking the lead again. I'm tracking a number of infrastructure vendors who are looking more closely at the role of the device as a key actor in determining mobile data routing, and I suspect their collective work will pay off.

For more detail on the technologies available for holistic mobile broadband traffic management (including device connection managers), please consider purchasing my new study, from $350.
NEW Mobile Broadband Traffic Management Paper
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

  • Quick musing on Cloud Computing
    I just heard the phrase "Everything as a Service" during a presentation on Cloud, SaaS and other forms of managed service offering...
  • Apple, embedded SIMs, NFC and mobile payments - some speculation
    I wonder if I've just managed to join up the dots on something rather important: - Recent reports suggest that Apple is intending to use...
  • New Cisco VNI traffic report out
    One of the broadband industry's "bibles" has been published in a 2010 edition . Cisco's "Visual Networking Index...
  • Is the MID a market?
    MIDs (Mobile Internet Devices) are being pushed by some notebook OEMs and silicon suppliers as the next big convergent handheld category. I...
  • "You can't use my eyeballs for free"
    Let's look forward 10 years. We've all got augmented reality browsers on our handsets, or perhaps our 4G-connected sunglasses. They ...
  • Mobile traffic management - the Inter-technology war begins
    I've been following the proliferation of mobile broadband traffic management technologies for some considerable time now, having publish...
  • Pre-MWC notes for analyst relations staff
    OK, it's the time of the year when I get bombarded by emails and phone calls from a million people inviting me to briefings and similar ...
  • Mobile operators' future voice strategies decoded
    Apologies in advance, but this blog post is deliberately a bit of a tease. I'm not going to spell out the answer here, as it's too v...
  • Hosted mobile services in the recession - Caveat Emptor
    I used to work as an equity analyst at an investment bank back in 2000-2001. I remember an unending stream of first generation Application S...
  • Challenges in measuring offload volumes
    I suspect we're going to get bombarded with statistics in the next year, along the lines of "Operator X deployed Vendor Y's off...

Blog Archive

  • ►  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ►  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)
      • Social media uselessness
      • Mobile operators' future voice strategies decoded
      • The risks of using someone else's numbers & forecasts
      • If mobile data billing takes too long to change, d...
      • Putting a value on customer data with reference to...
      • A counterpoint to femtocells - are they really nec...
      • Inter-technology competition and substitution - ph...
      • Doing a 180 on Vodafone 360
      • Will delays to LTE help or hinder VoLTE?
      • PRESS RELEASE: New study forecasts $416bn worldwi...
      • "Comes with data" business model for TomTom SatNav
      • Right up to the cap....
      • LTE iPhone? Not until 2013, I reckon
      • Thought for the day - mobile communities...
      • Upcoming events
      • New Cisco VNI traffic report out
      • Optimised Internet apps. vs. RCS vs. multi-headed ...
      • AT&T tiering, femtocells and holistic traffic mana...
      • Does a "coalition of the losers" ever win?
    • ►  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