Amazon Tech Support

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

Wednesday, 25 August 2010

Mobile traffic management - the Inter-technology war begins

Posted on 09:24 by Unknown
I've been following the proliferation of mobile broadband traffic management technologies for some considerable time now, having published a reseach paper on the bewildering range of options a few months back.

The continued hoo-ha around Net Neutrality is starting to catalyse open warfare between the advocates of different approaches to solving the mobile capacity crunch.

WiFi vs. femtocell offload competition is nothing new, but it's interesting to see new rivalry springing up between other purveyors of policy management and control. Flash Networks, for example, is one of a number of vendors that compress/optimise traffic, especially video destined for transmission over cellular networks.

There is quite a lot that can be done at the interface between the operator's gateway and its main Internet peering point - reformatting video, changing codecs or frame-rates, buffering cleverly and so on. Flash has made a very pointed Tweet to say that this is a much better option than performing brute-force traffic-shaping somewhere else in the operator's core or access network. Basically, they are suggesting it's better to compress traffic actively by modifying, rather than force the "natural" content to squeeze through a narrowed pipe.

(The Flash Tweet in full: Nice illustration of watching video with not enough bandwidth, or why bandwidth SHAPING is a DISASTER for online videos http://ow.ly/2upYv)

Of course, the content-optimisation approach to traffic management is not without its flaws either. Firstly, it changes the data transmitted, which is very much the spirit of Internet connectivity. Secondly, it is typically not "bearer-aware", only compressing the traffic if there is actual congestion. Most such solutions are also blind to whether the device is connected via femto or macro networks as well - there is almost no justification for changing content delivered over the user's home broadband and femto.

I don't want to single out Flash here, it's just an example of what I see as an emerging trend for warfare between the various options for traffic management.

Frankly, until we get closer to what I term "holistic traffic management", none of the options will be without problems. There needs to be much more awareness of content, user, network, device, application, actual congestion, pricing/tiering and numerous other criteria in order to make rational and customer-friendly policy decisions.

If you're interested in working through the mobile broadband policy/traffic minefield, please get in touch.
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)
      • Telcos: time to stop reporting "subscribers" and s...
      • Mobile traffic management - the Inter-technology w...
      • Is mobile voice being over-valued?
      • The Top 10 Unwarranted Assumptions in Telecoms
      • The hidden secret in the Google / Verizon statemen...
      • Work in Progress (comments welcome) - Code of Cond...
      • Device rental as a mechanism for mitigating roamin...
      • BlackBerry BBM intercept - workarounds probable?
      • Device-specific data plans and policy management
    • ►  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