Can Apps Really Damage a Cellular Network?

schnell writes "In FCC filings earlier this year, T-Mobile described how the behavior of one Android IM app nearly brought their cellular data network to a breakdown in one city. Even more interesting, the US carrier describes how just the 300,000 unlocked iPhones on their network caused massive spikes in data usage. T-Mobile is using these anecdotes as evidence that mobile carriers should be able to retain control over the applications and devices on their network to ensure quality of service for all users. Do they have a point?"

Comments

If you find that selling people unlimited or huge

[Assmasher]

data plans is biting you in the a** when it comes time to deliver, perhaps you should stop selling people unlimited or huge data plans... Arguing that not being able to control exactly how people use their data plan when you've advertised and sold them on the idea that they can do just about whatever they want seems sort of silly.

I'm not arguing that these phones/devices don't have the potential to cause huge problems, obviously they do, but you can't have your cake and eat it too.

My only thought when reading the summary ...

[BitZtream]

Is that the only thing the first post should say is 'No'

I was thinking exactly what you said, as a Network Admin in yesteryear I can't imagine anyone who says 'the users broke my network by using it!'

Our network simple handle 'bad users' on its own. To much traffic was simply handled by throttling the user to a safe level when needed.

Seriously, how can you not have complete control over a network when its this size? I'd have to resign if I was in charge of their network and had to say 'some random user broke it, sorry boss'

You NEVER trust any part of your network to 'play' nice, even if its under your complete control ... you can make mistakes too. You just assume the end users aren't going to play nice, and go from there, most do bad things without even knowing they are bad so you just plan for it like you would in any other business process.

Re:My only thought when reading the summary ...

[fermion]

As a person who used the networks of yore, I can remember many times when the users broke the network. That is why, for instance, outlook has added so many layers of optional protection' like the blocking of attachments and the like.

I am not sure why everyone, all of the sudden, is forgetting 10 years of DDOS and worm and virus attacks that used to regularly take down networks. We are protected from this not, partly because of more sophisticated software and users, but also because higher bandwidths and lower ping times make such attacks less trivial.

But ping time and bandwidth and the sophistication of younger users, and older users with no corporate control, make such an attack more probable on a phone network. Ping times on my cell network at about 5-10X as long wifi. Such times might lead to opportunities for rouge apps to degrade the user experience. Combine with lower bandwidth it might be conceivable that we will see some of the same attacks as we did at the turn of the century.

I am not saying that networks should be closed like Apple, but that until we learn how to use the tools, such disruptions will occasionally occur either accidentally or deliberately. it will be for us to decide if we want to deal with the dropped calls, as we did with the occasionally site becoming unreachable.

Poor infrastructure and management on your part...

[Omnifarious]

do not constitute a reason for me to submit to having which applications I can and can't run decided by a third party.

Bandwidth should be managed on a user-by-user basis, not an application-by-application basis. If you have an application that sucks up all your bandwidth, then you shouldn't have anymore bandwidth to use. Carriers should advertise burst and long-term bandwidth rates and if you go above the long-term rate you should be subject to having your bandwidth capped at that rate.

No telling you which application you are allowed to run and which you aren't. No throttling based on port. If you're a customer, you are promised X bandwidth and no more. The carrier is allowed to deliver in excess of that if they so choose, but they aren't allowed to decide you use it for.

And the carrier should not be allowed to decide on a per-application basis whether or not you get to exceed the bandwidth cap. It must be based on a global, application agnostic bandwidth usage policy that chooses which customers get the extra bandwidth (if any) based on some algorithm that has nothing to do with what their traffic contains.