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

Column  

Eslambolchi: 10 Service Provider Pain Points

January 14, 2011 |

Dr. Hossein Eslambolchi, chairman and CEO of 2020 Venture Partners, has sent one of his Top Ten lists. This time, for your edification, the Top Ten Service Provider Pain Points:

1) Flat ARPU
Where is the capex to support 50-percent traffic growth year over year for quad-play services?

2) Network Congestion
How do you plan for capacity when mobility induces temporary congestion without any warning?

3) All-You-Can-Eat Connectivity Services
Good for content providers, but bad for service providers.

4) Peer-to-Peer Traffic
It's growing fast, but there is no business model in sight to monetize it.

5) Over-the-Top Video
Service providers feel their networks are being robbed for this kind of VoD delivery.

6) Network Security
We're seeing attacks, attacks and more attacks. Lots of time, cost and resources exhausted fending off network attacks.

7) IPv6
This is a massive "must do" with no incremental revenue attached.

8) Regulations
Net neutrality is probably hampering a packet monetization solution that could make service provider traffic more profitable.

9) The Inability to Monetize Packet Traffic
Service providers are living with low-margin "dumb"-pipe revenues while Google and others are gaining high-margin traffic via over-the-top applications. This isn't sustainable for service providers, especially on wireless networks where spectrum is constrained.

10) Customer Churn
When customers aren't happy, they churn. When they churn, service providers lose money.

Now a question: What do you think service provders should do in 2011 to eliminate some of these pain points?

For more on Dr. Eslambolchi and his various corporate roles, see:

— The Staff, Light Reading



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.
 
Related Content
White Papers SPONSORED CONTENT
Featured
Docsis Provisioning of EPON (DPoE)
CableLabs spec that blends Docsis-style provisioning with EPON