Amazon Tech Support

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

Tuesday, 23 March 2010

How much mobile broadband traffic is outside the user's awareness?

Posted on 09:15 by Unknown
There's a lot of talk about controlling mobile broadband traffic by segmenting customers, or by trying to use tariffing to "modify behaviour".

Some of this makes sense - perhaps offering discounts for certain types of day, or even for using uncongested cells.

But I see a problem, literally "in the background" which may stifle attempts to "make customers use networks more responsibly" by being more careful about which applications they choose to use, or how they consume bandwidth.

I suspect that the amount of data traffic and events that are outside users' conscious control is going to rise inexorably. It will be very difficult to charge users for downloads that did not arise from them specifically clicking on a link, or firing up a particular application.

I'm thinking about:

- Javascript on web pages fetching extra data or applications
- Automated software updates running in the background (eg virus profiles, OS security patches)
- Interrupted downloads resuming while mobile
- Retransmitted data when someone reloads a web page because it hangs
- Repeated downloads of the same content (eg email attachments) because a device doesn't allow "save as", or because the file system is too convoluted to find it anyway
- Push notifications which drive both signalling and media consumption
- Pings and keep-alives between applications and servers
- Tracking data like cookies
- Monitoring of data about device "state" by the operator, OEM or 3rd party
- Encryption overhead
- Firmware updates and patches
- Lack of clear delineation between local applications and cloud-based components

.. and so forth.

I think that factors like these will make any application-based policy and charging very difficult to realise for mobile broadband. Expecting the user to know what their phone or PC is doing on their behalf, in the background is going to be a pretty tough sell. It's not user behaviour, it's device and application behaviour.

Does any operator have liability insurance that covers them for the consequences of throttling virus update downloads?

And should the user be aware of any compression being conducted on their behalf by the network? If I download a 10MB attachment, but it was only 2MB over-the-air, how can I be certain I'm charged for the lesser amount? Or if I'm drip-fed a downloaded video from an operator's buffer, is there extra signalling involved that I'm supposed to pay for?

Later this week, I'm going to be announcing the publication of a report on Mobile and Fixed Broadband Business Models, written on behalf of my associates at Telco 2.0. One of the themes it looks at is the role of policy in helping operators define new operating and revenues models. My view is that it is very important, but some of the theoretical possibilities about charging are overstated, because of complexities like these. If you're interested in getting some more detailed information about the new report, please email information AT disruptive-analysis DOT com.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home
View mobile version

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)
    • ►  May (19)
    • ►  April (11)
    • ▼  March (18)
      • The dangers of over-reliance on simplistic metrics
      • Mobile broadband problems - looking beyond the "ob...
      • LTE and offload - a few random questions
      • Hopefully, we'll be rid of the Twitter obsession soon
      • Network policy management and "corner cases"
      • Nokia acquisition of Novarra - fragmentation of op...
      • Non-user revenue models for broadband - excellent ...
      • New Research Report on Fixed & Mobile Broadband Bu...
      • Picocells and the return of the DECT guard band - ...
      • How much mobile broadband traffic is outside the u...
      • A quick tip for North American readers....
      • WiFi offload will not always win out over femtocells
      • The right way to sell mobile broadband....
      • "You can't use my eyeballs for free"
      • Will MIMO work indoors?
      • Netbooks - a skewed view on mobile broadband
      • CTIA....
      • Mobile traffic management - video confusion
    • ►  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