<?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; semiconductors</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/telecom/tag/semiconductors/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>Juniper&#8217;s radical service-layer software and semiconductor architecture speaks to carriers and enterprises</title>
		<link>http://itknowledgeexchange.techtarget.com/telecom/junipers-radical-service-layer-software-and-semiconductor-architecture-speaks-to-carriers-and-enterprises/</link>
		<comments>http://itknowledgeexchange.techtarget.com/telecom/junipers-radical-service-layer-software-and-semiconductor-architecture-speaks-to-carriers-and-enterprises/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 12:31:25 +0000</pubDate>
		<dc:creator>Tom Nolle</dc:creator>
				<category><![CDATA[cloud architecture]]></category>
		<category><![CDATA[Juniper]]></category>
		<category><![CDATA[Junos operating system]]></category>
		<category><![CDATA[next-generation architecture]]></category>
		<category><![CDATA[platform as a service]]></category>
		<category><![CDATA[semiconductors]]></category>
		<category><![CDATA[service-loayer architecture]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/telecom/?p=985</guid>
		<description><![CDATA[We can&#8217;t apologize for the characterization here; Juniper announced a radical combination of an extensive service-layer software system and a new semiconductor architecture, taking the most profound step the company has taken since it was founded. The new chip is a family, the first member of which is Trio. It is based on a “Network [...]]]></description>
				<content:encoded><![CDATA[<p>We can&#8217;t apologize for the characterization here; Juniper announced a radical combination of an <a href="http://www.reuters.com/article/pressRelease/idUS40638+29-Oct-2009+BW20091029">extensive service-layer software system and a new semiconductor architecture</a>, taking the most profound step the company has taken since it was founded.</p>
<p>The new chip is a family, the first member of which is Trio. It is based on a “Network Instruction Set Processor” model that builds software on the device using instructions customized for network behavior control rather than general-purpose instructions, as NPs do. In this respect, the chip is almost like an ASIC, but unlike an ASIC it’s programmable at the primitive NISP-instruction level, so new features can be added right down to the instruction level. It’s this architecture that accounts for the considerable improvements in performance, scalability, power efficiency, etc. that Juniper has demonstrated (through independent lab tests).</p>
<p>The software (Junos Space) is centered on a <a href="http://blogs.zdnet.com/BTL/?p=26736">complete restructuring of the Juniper Junos operating system</a>, and it extends Junos to cover not only Juniper devices but also independent software development, and even a new device client (Junos Pulse) that will provide security and identity management, VPN control, and connection control.</p>
<p>The software side of the announcement is the most critical because it is based on middleware to create what is, in effect, a platform-as-a-service cloud on which operators can build service features and service management components.The software there can then leverage software running on the routers through the old Juniper PSDP program, and through that could even, in theory, be linked to special “primitives” programmed into the new Trio NISP chip.</p>
<p class="MsoNormal"><span style="font-size: small;font-family: Times New Roman"><span style="font-size: 12pt">From a selfish vendor perspective, the most important thing is that Juniper ties the service layer development downward into its devices (through its router development programs like the old PSDP) and even potentially down into the chips themselves. That creates a value circle for them and it also lets operators build differentiation by linking their service solutions tightly into the network, giving better integration, operations, and performance than OTT players could achieve.</span></span></p>
<p>Juniper released applications for Ethernet activation, surveillance and monitoring, and problem management in the network. These are built on the Junos Space architecture. This new model is so radical that frankly it’s hard to believe it came out of Juniper, never known either for software or for making game-changing moves. This is clearly one such move, though, because it will at the minimum catalyze the whole service-layer marketplace.</p>
<p>Juniper also announced an expansion of its IBM OEM deal to include the SRX, which offers security control and falls under the Junos Space software umbrella at least in a development sense.</p>
<p>Finally, BLADE Network Technology announced it would license Junos for blade server switches, possibly the first porting of a network OS to another platform. Just assimilating all of this will no doubt create some headaches, but early indications from operators suggest they’re very interested, and there is also surprising early interest among large enterprises, particularly in the cloud computing potential.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/telecom/junipers-radical-service-layer-software-and-semiconductor-architecture-speaks-to-carriers-and-enterprises/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
