Data Hogs: the Monsters Carriers Created

jfruhlinger writes "A recent study claimed that the top 1 percent of mobile data users eat up half of the available bandwidth. But assuming it's true, who's at fault? Stats show data usage has increased radically with each new model of the iPhone, and similar phenomena are in place for Android phones — all of which are gleefully sold to the public by the same people who complain about 'data hogs.' Isn't this the equivalent of a car dealer heavily promoting Cadillacs, then complaining about poor fuel efficiency, then charging a ton for extra gasoline?"

Comments

To be fair

[mr1911]

Who would have guessed that consumers would actually use their data plan?

Re:Laws of mathematics

[vlm]

And I bet the top 1% of slashdot posters live in 80% of all basements.

Top 1% of posters get 80% of all +5 articles. This is true.

Re:Taking a cue from

[kasperd]

its a bit daft to think that every subscriber uses 100% of their bandwidth 24/7, so why not oversell it? After all, if I use 10% of my total bandwidth, there's no reason why you can't allocate that to 9 more subscribers, thus bringing the price down to 1/10th of what it was.

This would work great if they made throttling to actually match the principles you describe, and then advertise the lines as such.

For example they could advertise a line as 100Mbit/s maximum speed, 1Mbit/s average speed. As long as you stay below 1Mbit/s averaged over a week, you will get your 100Mbit/s. If your average over a week goes above 1Mbit/s though, then your maximum speed will start decreasing. Once your weekly average hits 2Mbit/s your maximum speed will have decreased to 1Mbit/s, which is sure to get your weekly average down again.

They could improve it even more by allowing users to put their traffic into different QoS bands, and ensure that they provide incentives for users to use appropriate QoS bands for the traffic they are sending. I think the following three QoS classes would make sense for most users.

• Default QoS. In this class you get to transfer as much data as specified by your subscription. It is intended for webbrowsing, email, and most other more or less interactive usages. The providers should guarantee that there is capacity to give you the bandwidth you paid for in this class.
• Latency sensitive QoS. In this class you only get to transfer one third of the amount of data specified by your subscription. It is intended for VOIP, action games, and other applications where latency is the important factor. On the routers this traffic needs to go into a special queue. That queue should be short since this traffic is very sensitive to latency. That will increase packet loss a bit, but for some latency sensitive applications packet drops are less of a problem than increased latency. Since this class by design should never ever use more than one third of the capacity of any link, packet drops should be rare anyway.
• Bulk QoS. In this class you get to transfer as much data as you want, it doesn't count towards your usage, and you don't get throttled for using too much. OTOH traffic in this class is not guaranteed at all. It only gets what is left over when the above two classes have gotten what they need. This would be useful for downloads lasting hours or days. Probably most traffic in this class would be bittorrent.

I think a classification as described above would give users sufficient incentive to use the proper class for their traffic, and providers don't have to pretend to know better and reclassify the traffic.