<?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: Forget caps, here&#8217;s the next big thing in wireless pricing</title>
	<atom:link href="http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 07:32:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-796171</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Sat, 14 Jan 2012 19:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-796171</guid>
		<description><![CDATA[Hi Roman, yep I agree. The tricky thing is establishing a baseline of what is a &quot;standard&quot; service. All mobile data -- with the exception of a few carrier apps -- is all best effort today, which can be good (such as when you get a 20 Mbps connection on LTE) or bad (when you get 100 kbps on a congested network). By suddenly creating a &quot;premium&quot; category, you aren&#039;t boosting someone&#039;s speed. Rather you&#039;re downgrading someone else&#039;s speed to ensure that the premium customer always gets speeds in the upper range of their typical service. I just don&#039;t the see that concept gelling with consumers.]]></description>
		<content:encoded><![CDATA[<p>Hi Roman, yep I agree. The tricky thing is establishing a baseline of what is a &#8220;standard&#8221; service. All mobile data &#8212; with the exception of a few carrier apps &#8212; is all best effort today, which can be good (such as when you get a 20 Mbps connection on LTE) or bad (when you get 100 kbps on a congested network). By suddenly creating a &#8220;premium&#8221; category, you aren&#8217;t boosting someone&#8217;s speed. Rather you&#8217;re downgrading someone else&#8217;s speed to ensure that the premium customer always gets speeds in the upper range of their typical service. I just don&#8217;t the see that concept gelling with consumers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-796169</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Sat, 14 Jan 2012 19:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-796169</guid>
		<description><![CDATA[Hey Thomas, we&#039;re already starting to see this overseas. Operators aren&#039;t charging per app, but excepting certain apps from the cap. Orange is selling a Facebook phone in some countries which gives you unlimited Facebook but a bucket of MBs for all other Internet use. Would be interesting to see if they try that in the U.S.]]></description>
		<content:encoded><![CDATA[<p>Hey Thomas, we&#8217;re already starting to see this overseas. Operators aren&#8217;t charging per app, but excepting certain apps from the cap. Orange is selling a Facebook phone in some countries which gives you unlimited Facebook but a bucket of MBs for all other Internet use. Would be interesting to see if they try that in the U.S.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roman Geyzer</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-795833</link>
		<dc:creator><![CDATA[Roman Geyzer]]></dc:creator>
		<pubDate>Sat, 14 Jan 2012 04:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-795833</guid>
		<description><![CDATA[Unless you can schedule traffic (which you can&#039;t), this is just robbing from one user to give to the next. It will probably make money for the carriers, but result in lower quality for users.]]></description>
		<content:encoded><![CDATA[<p>Unless you can schedule traffic (which you can&#8217;t), this is just robbing from one user to give to the next. It will probably make money for the carriers, but result in lower quality for users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Sachson</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-795788</link>
		<dc:creator><![CDATA[Thomas Sachson]]></dc:creator>
		<pubDate>Sat, 14 Jan 2012 02:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-795788</guid>
		<description><![CDATA[&quot;The per-app charging is even worse. Unless there is specific collaboration with the app/content co the network will make too many mistakes trying to guess what’s what.&quot;   -- We totally agree that doing any byte tracking in the network (DPI) is very tough to do well for any large number of data sources (herding billions of cats).  But if you move the tracking into the app itself (which reports to a billing server periodically -- not real time) it is secure, accurate, and easy to implement for the carrier.  Even better, the apps are not made by the carrier, but by the developers using a carrier supplied toolkit (e.g. modified Android ADK) who want to push content, so even less deployment costs to the carrier and in turn lower costs / greater choice to their customers.]]></description>
		<content:encoded><![CDATA[<p>&#8220;The per-app charging is even worse. Unless there is specific collaboration with the app/content co the network will make too many mistakes trying to guess what’s what.&#8221;   &#8212; We totally agree that doing any byte tracking in the network (DPI) is very tough to do well for any large number of data sources (herding billions of cats).  But if you move the tracking into the app itself (which reports to a billing server periodically &#8212; not real time) it is secure, accurate, and easy to implement for the carrier.  Even better, the apps are not made by the carrier, but by the developers using a carrier supplied toolkit (e.g. modified Android ADK) who want to push content, so even less deployment costs to the carrier and in turn lower costs / greater choice to their customers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arvin Alba</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-793992</link>
		<dc:creator><![CDATA[Arvin Alba]]></dc:creator>
		<pubDate>Tue, 10 Jan 2012 15:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-793992</guid>
		<description><![CDATA[In the Philippines, most ISPs and providers do this - all unlimited, but plans are based on speed. You pay this, your maximum speed is 1mbps, you pay this and it gets bumped to 2, and so on and so forth. Yeah, the speeds are pathetic, but we&#039;re not really that well off...]]></description>
		<content:encoded><![CDATA[<p>In the Philippines, most ISPs and providers do this &#8211; all unlimited, but plans are based on speed. You pay this, your maximum speed is 1mbps, you pay this and it gets bumped to 2, and so on and so forth. Yeah, the speeds are pathetic, but we&#8217;re not really that well off&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Fitchard</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-793794</link>
		<dc:creator><![CDATA[Kevin Fitchard]]></dc:creator>
		<pubDate>Tue, 10 Jan 2012 05:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-793794</guid>
		<description><![CDATA[Great points, Dean. And herein lies the problem of policy management (or at least trying to service plans around policies). With a shared network you can&#039;t maintain a consistent baseline from which to base a premium service.

I&#039;m curious, do you think operators will ever try to break out signaling from data consumption, charge for it separately or even charge the application developer?]]></description>
		<content:encoded><![CDATA[<p>Great points, Dean. And herein lies the problem of policy management (or at least trying to service plans around policies). With a shared network you can&#8217;t maintain a consistent baseline from which to base a premium service.</p>
<p>I&#8217;m curious, do you think operators will ever try to break out signaling from data consumption, charge for it separately or even charge the application developer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Bubley</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-793792</link>
		<dc:creator><![CDATA[Dean Bubley]]></dc:creator>
		<pubDate>Tue, 10 Jan 2012 05:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-793792</guid>
		<description><![CDATA[A lot of this is very fine in principle, but unworkable wishful thinking in reality. There are hundreds of &#039;gotchas&#039; for all of this. What happens when lots of people all hit Turbo during congestion? It can&#039;t magically generate more capacity, so the speed uplift will be minimal and the carrier will need to process refunds &amp; complaints. More generally, how does the customer know they got what they paid for?

The per-app charging is even worse. Unless there is specific collaboration with the app/content co the network will make too many mistakes trying to guess what&#039;s what.

It&#039;s telling that VZW says this is still &#039;deep in the labs&#039; - they&#039;ll have to go through multiple cycles of testing &amp; problem-fixing, and then deal with the fact the mobile data goalposts keep moving at the same time.

Also none of this fixes the problem of signalling load

Dean Bubley
@disruptivedean]]></description>
		<content:encoded><![CDATA[<p>A lot of this is very fine in principle, but unworkable wishful thinking in reality. There are hundreds of &#8216;gotchas&#8217; for all of this. What happens when lots of people all hit Turbo during congestion? It can&#8217;t magically generate more capacity, so the speed uplift will be minimal and the carrier will need to process refunds &amp; complaints. More generally, how does the customer know they got what they paid for?</p>
<p>The per-app charging is even worse. Unless there is specific collaboration with the app/content co the network will make too many mistakes trying to guess what&#8217;s what.</p>
<p>It&#8217;s telling that VZW says this is still &#8216;deep in the labs&#8217; &#8211; they&#8217;ll have to go through multiple cycles of testing &amp; problem-fixing, and then deal with the fact the mobile data goalposts keep moving at the same time.</p>
<p>Also none of this fixes the problem of signalling load</p>
<p>Dean Bubley<br />
@disruptivedean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SpeedReality</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-793766</link>
		<dc:creator><![CDATA[SpeedReality]]></dc:creator>
		<pubDate>Tue, 10 Jan 2012 04:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-793766</guid>
		<description><![CDATA[So, I&#039;ve been annoyed in the past with mobile network performance, so I wrote an app to measure it, in terms of real world speed, over time, in different locations:  free - enjoy.  

https://market.android.com/details?id=com.spdreality.SpeedReality]]></description>
		<content:encoded><![CDATA[<p>So, I&#8217;ve been annoyed in the past with mobile network performance, so I wrote an app to measure it, in terms of real world speed, over time, in different locations:  free &#8211; enjoy.  </p>
<p><a href="https://market.android.com/details?id=com.spdreality.SpeedReality" rel="nofollow">https://market.android.com/details?id=com.spdreality.SpeedReality</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Sachson</title>
		<link>http://gigaom.com/2012/01/09/forget-caps-heres-the-next-big-thing-in-wireless-pricing/#comment-793383</link>
		<dc:creator><![CDATA[Thomas Sachson]]></dc:creator>
		<pubDate>Mon, 09 Jan 2012 15:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=466547#comment-793383</guid>
		<description><![CDATA[There is another service that will soon be showing up to improve service -- except it will be free to users.  It is called the toll-free app (FreeBand) and works like a 1-800 voice call where a third party pays for the bandwidth consumed.   So the carrier gets a new revenue stream and the user free bytes.  And no one gets slowed down in the process (it&#039;s just a subsidy -- no throttling up or down).  For more info visit Box Top Solutions at CES in Las Vegas this week.  Thanks!]]></description>
		<content:encoded><![CDATA[<p>There is another service that will soon be showing up to improve service &#8212; except it will be free to users.  It is called the toll-free app (FreeBand) and works like a 1-800 voice call where a third party pays for the bandwidth consumed.   So the carrier gets a new revenue stream and the user free bytes.  And no one gets slowed down in the process (it&#8217;s just a subsidy &#8212; no throttling up or down).  For more info visit Box Top Solutions at CES in Las Vegas this week.  Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
