<?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"
	>
<channel>
	<title>Comments on: Sweet - my Dish DVR is illegal!</title>
	<atom:link href="http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/</link>
	<description>All The Wisdom That Fits</description>
	<pubDate>Thu, 04 Dec 2008 18:52:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Robert</title>
		<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-786</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Mon, 14 Jul 2008 06:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-786</guid>
		<description>Excellent web site I will be visiting oftenp</description>
		<content:encoded><![CDATA[<p>Excellent web site I will be visiting oftenp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cap'n Ken's Homespun Wisdom » Dish Network killing my illegal TiVo-patent-violating 942 DVR after all</title>
		<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-710</link>
		<dc:creator>Cap'n Ken's Homespun Wisdom » Dish Network killing my illegal TiVo-patent-violating 942 DVR after all</dc:creator>
		<pubDate>Thu, 03 Jul 2008 19:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-710</guid>
		<description>[...] back in April Dish Network was slapped with an injunction against selling certain DVRs in the wake of the TiVo patent infringement case. The models affected included the HD 942 DVR that [...]</description>
		<content:encoded><![CDATA[<p>[...] back in April Dish Network was slapped with an injunction against selling certain DVRs in the wake of the TiVo patent infringement case. The models affected included the HD 942 DVR that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TCL</title>
		<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-74</link>
		<dc:creator>TCL</dc:creator>
		<pubDate>Sat, 26 Apr 2008 18:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-74</guid>
		<description>Word</description>
		<content:encoded><![CDATA[<p>Word</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cap'n Ken</title>
		<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-71</link>
		<dc:creator>Cap'n Ken</dc:creator>
		<pubDate>Sat, 26 Apr 2008 12:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-71</guid>
		<description>Thank you, counselor. So much written about the case and the ruling, so little actual context given. Searching for the "loctl" term you referred to got me a little more information about that argument, but not much. 

I would think in today's patent-happy and device-happy world, the TiVo v Echo case would be a fertile topic for tech writers to examine and explain how such technical details can influence an infringement case. You and I have talked enough about how patent litigators earn their keep for me to have a sense of how small the details can be that swing a case, but little is out there really talking about the intricacies of the field.</description>
		<content:encoded><![CDATA[<p>Thank you, counselor. So much written about the case and the ruling, so little actual context given. Searching for the &#8220;loctl&#8221; term you referred to got me a little more information about that argument, but not much. </p>
<p>I would think in today&#8217;s patent-happy and device-happy world, the TiVo v Echo case would be a fertile topic for tech writers to examine and explain how such technical details can influence an infringement case. You and I have talked enough about how patent litigators earn their keep for me to have a sense of how small the details can be that swing a case, but little is out there really talking about the intricacies of the field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TCL</title>
		<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-69</link>
		<dc:creator>TCL</dc:creator>
		<pubDate>Sat, 26 Apr 2008 04:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-69</guid>
		<description>Not hanging around so much as swinging by, thanks to RSS.  Just on a quick read, because I'm wrapped up in the world of carboxylated nitrile butadiene rubber gloves right now, the answer is, nope, not the encoding standard.  Briefly, the Echostar DVRs were found by the district court to infringe two "hardware" claims and two "software" claims.  The CAFC reversed on the hardware claims, but upheld the infringement of the software claims.  The issue of encoding standard would have arisen with respect to the hardware claims.  The hardware claims were found not infringed on a basis unrelated to encoding standard; indeed, the CAFC noted, in rejecting Echo's argument that the patent required processing of both digital and analog signals, that the patent spec describes both MPEG standards:  "After describing how Figure 7 operates to process analog signals, the specification adds the following: 'If a digital TV signal is being processed instead, the MPEG encoder is replaced with an MPEG2 Transport Demultiplexor, and the MPEG audio encoder and VBI decoder are deleted.'” [Col. 6, ll. 30-33].

Instead, my best guess, again on a quick read, is one of two things:  (a) Bullshit that the "next gen" software is a non-infringing work-around, and Echo will be in contempt of the injunction soon; or (b) the software push has something to do with the "Ioctl" command and the way in which the chip and temporary storage buffer work together.  The CAFC affirmed infringement of the software claims with the following conclusion:  "Based on evidence that the Broadcom chip and the temporary data storage buffer operate together in the process of moving data from the physical data source, it was reasonable for the jury to find that the temporary data buffer was simply an extension of the physical data source where data was stored pending its extraction for further processing. From that evidence, the jury could permissibly find that the “Ioctl” command, the relevant portion of the source object in the EchoStar DVRs, extracts video and audio data from the physical data source. . . . and because we agree that the pertinent data and operations do not need to be housed within a particular file or grouping of lines of code, the EchoStar DVRs satisfy the 'extracting' limitation."  That is, it was "reasonable for the jury to find that the two-part process of moving data from the physical data source to the source object, as practiced in the EchoStar devices, constitutes extraction by the source object of video and audio data from the physical data source."  And therefore, perhaps Echo pushed some software that simply places another step, or some more distinct separation in the operation of the physical data source and the temporary storage buffer, such that they are no longer linked together as one process of retrieving from the physical data source.

But what do I know, I have two crappy cable DVRs.</description>
		<content:encoded><![CDATA[<p>Not hanging around so much as swinging by, thanks to RSS.  Just on a quick read, because I&#8217;m wrapped up in the world of carboxylated nitrile butadiene rubber gloves right now, the answer is, nope, not the encoding standard.  Briefly, the Echostar DVRs were found by the district court to infringe two &#8220;hardware&#8221; claims and two &#8220;software&#8221; claims.  The CAFC reversed on the hardware claims, but upheld the infringement of the software claims.  The issue of encoding standard would have arisen with respect to the hardware claims.  The hardware claims were found not infringed on a basis unrelated to encoding standard; indeed, the CAFC noted, in rejecting Echo&#8217;s argument that the patent required processing of both digital and analog signals, that the patent spec describes both MPEG standards:  &#8220;After describing how Figure 7 operates to process analog signals, the specification adds the following: &#8216;If a digital TV signal is being processed instead, the MPEG encoder is replaced with an MPEG2 Transport Demultiplexor, and the MPEG audio encoder and VBI decoder are deleted.&#8217;” [Col. 6, ll. 30-33].</p>
<p>Instead, my best guess, again on a quick read, is one of two things:  (a) Bullshit that the &#8220;next gen&#8221; software is a non-infringing work-around, and Echo will be in contempt of the injunction soon; or (b) the software push has something to do with the &#8220;Ioctl&#8221; command and the way in which the chip and temporary storage buffer work together.  The CAFC affirmed infringement of the software claims with the following conclusion:  &#8220;Based on evidence that the Broadcom chip and the temporary data storage buffer operate together in the process of moving data from the physical data source, it was reasonable for the jury to find that the temporary data buffer was simply an extension of the physical data source where data was stored pending its extraction for further processing. From that evidence, the jury could permissibly find that the “Ioctl” command, the relevant portion of the source object in the EchoStar DVRs, extracts video and audio data from the physical data source. . . . and because we agree that the pertinent data and operations do not need to be housed within a particular file or grouping of lines of code, the EchoStar DVRs satisfy the &#8216;extracting&#8217; limitation.&#8221;  That is, it was &#8220;reasonable for the jury to find that the two-part process of moving data from the physical data source to the source object, as practiced in the EchoStar devices, constitutes extraction by the source object of video and audio data from the physical data source.&#8221;  And therefore, perhaps Echo pushed some software that simply places another step, or some more distinct separation in the operation of the physical data source and the temporary storage buffer, such that they are no longer linked together as one process of retrieving from the physical data source.</p>
<p>But what do I know, I have two crappy cable DVRs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-50</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 22 Apr 2008 22:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.capnken.com/wisdom/2008/04/21/sweet-my-dish-dvr-is-illegal/#comment-50</guid>
		<description>Yeah, I wouldn't go quoting Charleton Heston on that point.

The prying's been done.</description>
		<content:encoded><![CDATA[<p>Yeah, I wouldn&#8217;t go quoting Charleton Heston on that point.</p>
<p>The prying&#8217;s been done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
