Light Reading Mobile – Telecom News, Analysis, Events, and Research

8:00 AM -- I doubt wireless service providers will move to pay-per-bit or usage-based billing anytime soon. Having tiers of service where consumers pick how much data they think they'll use is more productive for the bottom line. Consumers want to avoid penalties and bill shock, so they often buy a higher, more expensive tier that allows for more data than they'll actually use in a given month.

That was the main point I made on a recent appearance on TIA NOW, the video service run by the Telecommunications Industry Association (TIA), starting at about the 5:00 mark. Click here to see that video.

Of course, we're seeing data caps in wireline networks, too, as broadband providers are slowing training consumers that there is no such thing as all-you-can-eat broadband, since so much compelling content is being consumed outside the confines of what's offered via popular pay TV services.

Consumers may not like data caps, but they'll be with us for a while. Why? They seem to be the only way operators can assure their shareholders that they will grow the amount of revenue they can get per user even after the customer is purchasing the highest available speed on the network. Add and change the tiers at will, impose ludicrous fees for "unlimited" plans and you can force consumers to buy a little more data each time.

While we're talking about this, what service provider plan do you like the most? Which one suits you best or offers what you think is a solid bargain?

For more

— Phil Harvey, Editor-in-Chief, Light Reading

8:00 AM Consumers have to accept data caps as service providers find that tiered plans are the easiest way to slow consumption and raise revenues
August 20, 2012 | Phil Harvey |


Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Going Soft at MWC

SPONSORED BY
Related Videos
White Papers SPONSORED CONTENT
Featured
Interlaken
A chip-to-chip interface useful in 100G