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

Heavy Lifting Analyst Notes  

APIs Can Generate Billions for Telcos

December 12, 2012 | Simon Sherrington- Research Analyst |

"You can get the milk without knowing how to milk the cow" was how Locaid CEO Rip Gerber described the benefit of application programming interface (API)-based access to telecom networks. And you can get a lot of milk out of telecom networks if you know how.

The idea of API enablement might sound "tech-y," but it is important for executives at telecom operators and service providers to understand the potential of a market that could be worth billions of dollars a year. APIs may well be the next killer app that telcos have been looking for – essentially making it easy for their own internal teams and for developers out in the wider world to access their network systems, to easily create new revenue-generating services.

It is an idea a few major telecom operators are now coming to grips with. AT&T Inc. is one of the most public leaders in this space, with major projects to open up APIs for new service creation and a program to engage developers. Other major carriers, such as Verizon Communications Inc. and Telefónica O2, are also active, as are the Canadian mobile operators. In addition, mobile operators in the U.S. have all been forced to provide access to location APIs. Yet there are many telecom operators that have not moved API development much beyond participation in the various cross-industry API standardization schemes (such as the development of OSA/Parlay and OneAPI). And there are many more that have not even been involved in those programs.

There are many technological, financial and cultural reasons for the slow rate of movement. But operators that do not embrace the idea of exposing APIs will be slower to market than their rivals, miss great collaboration opportunities with the Internet developer community and fail to open up some great revenue-generating opportunities.

Fixed and mobile operators have the opportunity to exploit API access into their systems, and they don't have to do it all themselves. A range of vendors have moved into the market to support them, including heavyweights, such as Alcatel-Lucent, Cisco Systems Inc., Ericsson AB, IBM Corp. and Oracle Corp., that offer various ways for operators to expose their own APIs; specialist API service providers, such as Locaid, LocationSmart (Technocom Wireless), Twilio Inc. and Placecast, that are offering developers API access to services across multiple providers' networks; and independent API creation and management platform providers, including Aepona Ltd., Apigee Corp., Layer 7 Technologies Inc. and Voxeo Labs, whose systems are designed to support carriers in widespread exposure of APIs.

The new Heavy Reading Service Provider IT Insider, "Opening the Door to Web Developers: How APIs Can Generate Billions for Operators," takes a detailed look at how operators can use APIs to grow their businesses; shows the many use cases that are emerging, and the range of business models being used; provides a detailed case study of AT&T; and profiles the leading technology providers identified above, analyzing the solutions they offer to telecom operators.

— Simon Sherrington, Analyst, Heavy Reading Service Provider IT Insider

Opening the Door to Web Developers: How APIs Can Generate Billions for Operators, a 41-page report in PDF format, is available as part of an annual subscription (6 bimonthly issues) to Heavy Reading Service Provider IT Insider, priced at $1,595. Individual reports are available for $900.



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 Content
White Papers SPONSORED CONTENT
Featured
Trill
A Spanning Tree alternative in Ethernet networks