<?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/"
		>
<channel>
	<title>Comments on: Enterprise Mobility from the Telecom Carrier perspective</title>
	<atom:link href="http://www.ipass.com/blog/enterprise-mobility-from-the-telecom-carrier-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ipass.com/blog/enterprise-mobility-from-the-telecom-carrier-perspective/</link>
	<description>Providing best practices, insight and updates on Enterprise Mobility, helping companies better manage mobile device connections security and costs.</description>
	<lastBuildDate>Tue, 30 Apr 2013 19:17:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Marcio Avillez</title>
		<link>http://www.ipass.com/blog/enterprise-mobility-from-the-telecom-carrier-perspective/comment-page-1/#comment-29</link>
		<dc:creator>Marcio Avillez</dc:creator>
		<pubDate>Wed, 27 Jan 2010 21:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://www3.ipass.com/?p=3488#comment-29</guid>
		<description><![CDATA[You are correct, the problem is only getting worse for the mobile carriers.  The result of more people using these devices times more bandwidth intensive apps per device creates a multi-year problem for the MNOs and the range of effective solutions: LTE upgrade, cell site splitting and increased backhaul capacity are all fairly capital intensive and time-consuming.  The carriers will need to do something to control the demand side of the equation to have a shot of getting ahead of this in the near term – either getting more people to pay for data they don’t use or provide pricing plans that create “incentives for users to behave better.”]]></description>
		<content:encoded><![CDATA[<p>You are correct, the problem is only getting worse for the mobile carriers.  The result of more people using these devices times more bandwidth intensive apps per device creates a multi-year problem for the MNOs and the range of effective solutions: LTE upgrade, cell site splitting and increased backhaul capacity are all fairly capital intensive and time-consuming.  The carriers will need to do something to control the demand side of the equation to have a shot of getting ahead of this in the near term – either getting more people to pay for data they don’t use or provide pricing plans that create “incentives for users to behave better.”</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Kapustka</title>
		<link>http://www.ipass.com/blog/enterprise-mobility-from-the-telecom-carrier-perspective/comment-page-1/#comment-25</link>
		<dc:creator>Paul Kapustka</dc:creator>
		<pubDate>Tue, 26 Jan 2010 06:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://www3.ipass.com/?p=3488#comment-25</guid>
		<description><![CDATA[AT&amp;T recently announced just how far behind it was in regards to backhaul -- in 2009 they added 13,500 T-1 lines in just San Francisco and New York combined -- plus over 200 DS-3 optical connections.

&quot;Unprecedented&quot; was how they described the traffic surge on their network the past few years. But it looks like that will be the norm, not the exception, for the future.

See our post on the subject: 

http://bit.ly/7QK5IM]]></description>
		<content:encoded><![CDATA[<p>AT&amp;T recently announced just how far behind it was in regards to backhaul &#8212; in 2009 they added 13,500 T-1 lines in just San Francisco and New York combined &#8212; plus over 200 DS-3 optical connections.</p>
<p>&#8220;Unprecedented&#8221; was how they described the traffic surge on their network the past few years. But it looks like that will be the norm, not the exception, for the future.</p>
<p>See our post on the subject: </p>
<p><a href="http://bit.ly/7QK5IM" rel="nofollow">http://bit.ly/7QK5IM</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>