<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Interview: Ericsson CEO on the rise of the HetNet</title>
	<atom:link href="http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 15:54:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Rupert Baines</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-836645</link>
		<dc:creator><![CDATA[Rupert Baines]]></dc:creator>
		<pubDate>Sun, 29 Apr 2012 10:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-836645</guid>
		<description><![CDATA[Kevin

&#039;&#039;femto guys&#039;&#039; and small cell are esseentially the same.

The issue about just how well those devices live in a separate layer under the macro layer with independence &amp; without problems is, indeed, at the heart of the debate.

For residential it clearly works.

The indications where small cell contracts are separate from macro contracts (for Korea with LTE, USA &amp; UK with 3G) suggest that this is viable.]]></description>
		<content:encoded><![CDATA[<p>Kevin</p>
<p>&#8221;femto guys&#8221; and small cell are esseentially the same.</p>
<p>The issue about just how well those devices live in a separate layer under the macro layer with independence &amp; without problems is, indeed, at the heart of the debate.</p>
<p>For residential it clearly works.</p>
<p>The indications where small cell contracts are separate from macro contracts (for Korea with LTE, USA &amp; UK with 3G) suggest that this is viable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835805</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 13:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835805</guid>
		<description><![CDATA[I see your point, Dave. It does seem an awful lot is done in the name of building a &quot;carrier-class&quot; network, when at the end of the day the consumer doesn&#039;t really care. They just want Internet access.]]></description>
		<content:encoded><![CDATA[<p>I see your point, Dave. It does seem an awful lot is done in the name of building a &#8220;carrier-class&#8221; network, when at the end of the day the consumer doesn&#8217;t really care. They just want Internet access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835803</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 13:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835803</guid>
		<description><![CDATA[Yeah, I see your point, Dean. You can&#039;t really splice together a bunch of coffeeshop, hotel and airport networks, add a connection manager and call it HetNet. What about what KDDI is doing? The scope seems impressive.]]></description>
		<content:encoded><![CDATA[<p>Yeah, I see your point, Dean. You can&#8217;t really splice together a bunch of coffeeshop, hotel and airport networks, add a connection manager and call it HetNet. What about what KDDI is doing? The scope seems impressive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Wright</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835801</link>
		<dc:creator><![CDATA[Dave Wright]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 13:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835801</guid>
		<description><![CDATA[I think the mobile industry needs to back up and question some presumptions.  Why does a successful Wi-Fi strategy need unified network intelligence between licensed and unlicensed?  AT&amp;T, O2, China Mobile, PCCW, etc... have all developed Wi-Fi architectures that are carrying significant portions of their wireless data traffic (54% for China Mobile and ~30% for AT&amp;T).  They did this without any unified anything, beyond an autoconnect feature on their handsets.  Informa/Mobidia is indicating that 70% of global smartphone data  usage may already be going over Wi-Fi (this includes non-operator Wi-Fi – home, business, other public, etc…)

While I’m goring sacred cows, they should also consider whether their efforts to make Public Wi-Fi access work similarly to, and in conjunction with, legacy BSS and OSS models is the right longterm decision.  Those architectures were developed around a voice service paradigm decades ago.  We could come up with much better/simpler solutions focused around mobile data today.  If they don’t do it, some upstarts from the Wi-Fi side eventually will.

Operators who insist on this holy grail of a unified cellular/WLAN infrastructure are missing out on a huge market that is developing all around them as they dither.  I don’t need my access networks to be unified and coordinated, I just need them to be available, to work, and to provide access to my services and data.  

(Note, I think 802.11u and Hotspot 2.0 are great enhancements for Public Wi-Fi.  But we need to see some architectures put forward that don’t involve integrating them with a legacy cellular core)]]></description>
		<content:encoded><![CDATA[<p>I think the mobile industry needs to back up and question some presumptions.  Why does a successful Wi-Fi strategy need unified network intelligence between licensed and unlicensed?  AT&amp;T, O2, China Mobile, PCCW, etc&#8230; have all developed Wi-Fi architectures that are carrying significant portions of their wireless data traffic (54% for China Mobile and ~30% for AT&amp;T).  They did this without any unified anything, beyond an autoconnect feature on their handsets.  Informa/Mobidia is indicating that 70% of global smartphone data  usage may already be going over Wi-Fi (this includes non-operator Wi-Fi – home, business, other public, etc…)</p>
<p>While I’m goring sacred cows, they should also consider whether their efforts to make Public Wi-Fi access work similarly to, and in conjunction with, legacy BSS and OSS models is the right longterm decision.  Those architectures were developed around a voice service paradigm decades ago.  We could come up with much better/simpler solutions focused around mobile data today.  If they don’t do it, some upstarts from the Wi-Fi side eventually will.</p>
<p>Operators who insist on this holy grail of a unified cellular/WLAN infrastructure are missing out on a huge market that is developing all around them as they dither.  I don’t need my access networks to be unified and coordinated, I just need them to be available, to work, and to provide access to my services and data.  </p>
<p>(Note, I think 802.11u and Hotspot 2.0 are great enhancements for Public Wi-Fi.  But we need to see some architectures put forward that don’t involve integrating them with a legacy cellular core)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: srsaunders</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835761</link>
		<dc:creator><![CDATA[srsaunders]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 11:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835761</guid>
		<description><![CDATA[Re Michael Elling&#039;s question, we fully accounted for the backhaul (and plenty of other) costs in the study at http://bit.ly/HJGVIL and small cells turn out to still play an important role, alongside spectrum and macrocell upgrades.]]></description>
		<content:encoded><![CDATA[<p>Re Michael Elling&#8217;s question, we fully accounted for the backhaul (and plenty of other) costs in the study at <a href="http://bit.ly/HJGVIL" rel="nofollow">http://bit.ly/HJGVIL</a> and small cells turn out to still play an important role, alongside spectrum and macrocell upgrades.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Bubley</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835689</link>
		<dc:creator><![CDATA[Dean Bubley]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 07:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835689</guid>
		<description><![CDATA[Kevin

I think you will see some aggregation (&amp; indeed already do) - although almost certainly not the sort of network-centric seamless approach that some envisage. Seams - borders, really - are too important to get rid of arbitrarily. See my blog post from a few weeks ago:
http://disruptivewireless.blogspot.com/2012/04/operator-wifi-seamless-is-wrong.html

There are some use-cases where HetNets will be valuable, but equally there are plenty of others where that level of integration will be damaging to the user experience, or the desires &amp; requirements of private WiFi owners.

Dean]]></description>
		<content:encoded><![CDATA[<p>Kevin</p>
<p>I think you will see some aggregation (&amp; indeed already do) &#8211; although almost certainly not the sort of network-centric seamless approach that some envisage. Seams &#8211; borders, really &#8211; are too important to get rid of arbitrarily. See my blog post from a few weeks ago:<br />
<a href="http://disruptivewireless.blogspot.com/2012/04/operator-wifi-seamless-is-wrong.html" rel="nofollow">http://disruptivewireless.blogspot.com/2012/04/operator-wifi-seamless-is-wrong.html</a></p>
<p>There are some use-cases where HetNets will be valuable, but equally there are plenty of others where that level of integration will be damaging to the user experience, or the desires &amp; requirements of private WiFi owners.</p>
<p>Dean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835558</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Fri, 27 Apr 2012 00:21:43 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835558</guid>
		<description><![CDATA[Hey Rupert,

Good points. I think ALU is firmly in the single vendor camp, though, as is NSN. The may not make Wi-Fi access points but they can easily partner with companies that do (or buy Ruckus). Otherwise they&#039;re advocating their carriers adopt a single-vendor lifestyle. :)

The femto guys make an interesting case for a multi-vendor world, but their main argument seems to be low cost, which has merits, but if there is no integration it just won&#039;t work. I think the femto guys would have us believe their cells can live in colonies without SON right under the macro network and somehow magically not interfering with the macro network.

As for Wi-Fi, great idea, but I&#039;m shocked at just how hard it is to implement. Maybe it&#039;s because there are three separate standards, three separate industry bodies trying to implement three separate technologies...]]></description>
		<content:encoded><![CDATA[<p>Hey Rupert,</p>
<p>Good points. I think ALU is firmly in the single vendor camp, though, as is NSN. The may not make Wi-Fi access points but they can easily partner with companies that do (or buy Ruckus). Otherwise they&#8217;re advocating their carriers adopt a single-vendor lifestyle. :)</p>
<p>The femto guys make an interesting case for a multi-vendor world, but their main argument seems to be low cost, which has merits, but if there is no integration it just won&#8217;t work. I think the femto guys would have us believe their cells can live in colonies without SON right under the macro network and somehow magically not interfering with the macro network.</p>
<p>As for Wi-Fi, great idea, but I&#8217;m shocked at just how hard it is to implement. Maybe it&#8217;s because there are three separate standards, three separate industry bodies trying to implement three separate technologies&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rupert Baines</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-835504</link>
		<dc:creator><![CDATA[Rupert Baines]]></dc:creator>
		<pubDate>Thu, 26 Apr 2012 21:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-835504</guid>
		<description><![CDATA[One interesting aspect (and this touches on Dean&#039;s &quot;sep net&quot; concept) is the degree the networks are integrated, and if so who is in control.

For example, Ericsson would advocate that macro, small cell &amp; WiFi all come from one vendor: het net in layers, but &quot;homo net&quot; in service, vendor, OSS and purchasing (ahem)

An operatopr may prefer single network from services but the freedom to purchase from different suppliers: one can imagine Ruckus or ALU advocating this, as distinct from macro contracts.

Will .11u / HotSpot2.0  and the 3GPP SmallCell analogs support this - or is it a coherent, integrated, single vendor monolithy?]]></description>
		<content:encoded><![CDATA[<p>One interesting aspect (and this touches on Dean&#8217;s &#8220;sep net&#8221; concept) is the degree the networks are integrated, and if so who is in control.</p>
<p>For example, Ericsson would advocate that macro, small cell &amp; WiFi all come from one vendor: het net in layers, but &#8220;homo net&#8221; in service, vendor, OSS and purchasing (ahem)</p>
<p>An operatopr may prefer single network from services but the freedom to purchase from different suppliers: one can imagine Ruckus or ALU advocating this, as distinct from macro contracts.</p>
<p>Will .11u / HotSpot2.0  and the 3GPP SmallCell analogs support this &#8211; or is it a coherent, integrated, single vendor monolithy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-834979</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Thu, 26 Apr 2012 00:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-834979</guid>
		<description><![CDATA[Thanks!]]></description>
		<content:encoded><![CDATA[<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/04/25/what-is-hetnet-ericsson-vestberg/#comment-834964</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Wed, 25 Apr 2012 23:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=514500#comment-834964</guid>
		<description><![CDATA[I dunno Dean,

I agree that at 1,000 carrier-hotspot effort means little, but there are a lot of hotspot operators, telcos and and cable operators looking to sell their capacity off. If you can piece enough of those deals together, they could have a big impact. I&#039;m not yet willing to concede that Wi-Fi offload is quite as silly as IMS. :)]]></description>
		<content:encoded><![CDATA[<p>I dunno Dean,</p>
<p>I agree that at 1,000 carrier-hotspot effort means little, but there are a lot of hotspot operators, telcos and and cable operators looking to sell their capacity off. If you can piece enough of those deals together, they could have a big impact. I&#8217;m not yet willing to concede that Wi-Fi offload is quite as silly as IMS. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
