 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Uncommon Wisdom &#187; application enablement</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/telecom/tag/application-enablement/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/telecom</link>
	<description>A SearchCloudProvider.com blog</description>
	<lastBuildDate>Wed, 26 Oct 2011 20:46:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>How quickly can Alcatel-Lucent&#8217;s Open API program adapt to the market?</title>
		<link>http://itknowledgeexchange.techtarget.com/telecom/how-quickly-can-alcatel-lucents-open-api-program-adapt-to-the-market/</link>
		<comments>http://itknowledgeexchange.techtarget.com/telecom/how-quickly-can-alcatel-lucents-open-api-program-adapt-to-the-market/#comments</comments>
		<pubDate>Tue, 21 Dec 2010 18:14:04 +0000</pubDate>
		<dc:creator>Tom Nolle</dc:creator>
				<category><![CDATA[Alcatel-Lucent]]></category>
		<category><![CDATA[APIs]]></category>
		<category><![CDATA[application development]]></category>
		<category><![CDATA[application enablement]]></category>
		<category><![CDATA[application program interface]]></category>
		<category><![CDATA[Open API]]></category>
		<category><![CDATA[open APIs]]></category>
		<category><![CDATA[OTT]]></category>
		<category><![CDATA[over-the-top]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/telecom/?p=2116</guid>
		<description><![CDATA[Alcatel-Lucent continues to showcase the developer side of its Application Enablement approach, including its Open API program, which federates application services across multiple developers. There is no question that the company has started to gain some traction in the market with this, but there is still a question in our mind regarding how quickly the [...]]]></description>
				<content:encoded><![CDATA[<p>Alcatel-Lucent continues to showcase the developer side of its <a href="http://searchtelecom.techtarget.com/feature/The-application-enablement-based-broadband-model-as-network-savior">Application Enablement approach</a>, including its <a href="http://searchtelecom.techtarget.com/news/1375851/Alcatel-Lucent-launches-service-layer-architecture-for-carrier-application-developer-mashups">Open API program</a>, which federates application services across multiple developers. There is no question that the company has started to gain some traction in the market with this, but there is still a question in our mind regarding how quickly the program can adapt to market conditions.</p>
<p>The thing that has made <a href="http://searchtelecom.techtarget.com/tip/Going-over-the-top-Build-telecom-revenue-with-mobile-social-networking-services">over-the-top</a> players successful in the service layer is that they&#8217;ve dodged inertia. Because they don&#8217;t worry about standards beyond blowing a casual kiss here and there, they can expose features via <a href="http://searchexchange.techtarget.com/definition/application-program-interface">APIs</a> very quickly. If you wait for industry consensus on APIs, you&#8217;re putting yourself at the tail end of a multi-year process and then saying you&#8217;re running at market speed. I&#8217;d like to see Alcatel-Lucent open up more regarding how it will create features in Application Enablement and how quickly it can expose them using <a href="http://searchsoa.techtarget.com/tip/RESTful-resources-for-potential-REST-developers">RESTful</a> APIs.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/telecom/how-quickly-can-alcatel-lucents-open-api-program-adapt-to-the-market/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NSN&#8217;s three vendors standing vision &#8212; but which ones?</title>
		<link>http://itknowledgeexchange.techtarget.com/telecom/nsns-three-vendors-standing-vision-but-which-ones/</link>
		<comments>http://itknowledgeexchange.techtarget.com/telecom/nsns-three-vendors-standing-vision-but-which-ones/#comments</comments>
		<pubDate>Tue, 21 Dec 2010 15:23:08 +0000</pubDate>
		<dc:creator>Tom Nolle</dc:creator>
				<category><![CDATA[Alcatel-Lucent]]></category>
		<category><![CDATA[application enablement]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Ericsson]]></category>
		<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Juniper]]></category>
		<category><![CDATA[NSN]]></category>
		<category><![CDATA[procurement zones]]></category>
		<category><![CDATA[service layer]]></category>
		<category><![CDATA[telecom equipment vendors]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/telecom/?p=2121</guid>
		<description><![CDATA[NSN’s CEO has recently suggested that the telecom sector will consolidate with only three major players remaining; Ericsson, Huawei and NSN.  I think that vision of the future is a tad self-serving in terms of the players, but I think that it is very clear that somewhere around three players is what we could expect [...]]]></description>
				<content:encoded><![CDATA[<p>NSN’s CEO has recently suggested that the telecom sector will consolidate with only three major players remaining; <a href="http://itknowledgeexchange.techtarget.com/telecom/nsnericsson-wo…placing-huaweinsnericsson-won-teliasonera-lte-deal-displacing-huawei/">Ericsson</a>, <a href="http://searchtelecom.techtarget.com/feature/ACG-Research-on-Huawei-Chinese-business-culture-and-the-Art-of-War">Huawei</a> and <a href="http://itknowledgeexchange.techtarget.com/telecom/potential-nsn-…ad-news-anglespotential-nsn-minority-stake-sale-has-good-newsbad-news-angles/">NSN</a>.  I think that vision of the future is a tad self-serving in terms of the players, but I think that it is very clear that somewhere around three players is what we could expect to see if the industry can’t find better feature differentiation.  If Alcatel-Lucent wants to make the cut here, it definitely needs to make <a href="http://itknowledgeexchange.techtarget.com/telecom/the-handwriting-on-the-tablet-users-mobility-and-wireless-networks/">Application Enablement </a>work, and it’s frustrating to me how close itis to that, and yet how far. But it’s not atypical with <a href="http://searchtelecom.techtarget.com/tip/Service-layer-architecture-4-main-network-operator-requirements">service-layer strategies</a> in the big vendor space. Nobody has it right there.</p>
<p>One might ask where this consolidation would leave Cisco and Juniper, the other big players in the IP layer at least. That&#8217;s another area where NSN&#8217;s comments oversimplify. In operator trends toward <a href="http://searchtelecom.techtarget.com/tip/Procurement-zones-become-telecom-network-infrastructure-strategy">procurement zones</a> for buying, we’re seeing an attempt to create a market where a single giant vendor with a full product line can’t dominate everything.</p>
<p>The operators would like innovation, particularly with respect to the service layer, and they can’t get it by having everything collapse into a single giant commoditized space. But if the specialty guys like Cisco and Juniper can’t make a case in the service layer, then they can’t defend their narrower position in a commoditizing market. Thus, we could see the NSN “vision of three” being right, even if the three turn out to be different names than expects.</p>
<p><!-- .entry-content --></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/telecom/nsns-three-vendors-standing-vision-but-which-ones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
