<?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>McBride Law, PC &#187; Patent Law</title>
	<atom:link href="http://www.mcbride-law.com/category/patent/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mcbride-law.com</link>
	<description>General, Commercial Lease Disputes, Fraud and Misrepresentation , Legal Malpractice, partnership and shareholder disputes, vendor and partner disputes, trademark litigation, employment litigation, Document Retention Policies, Electronic Discovery, Internet Law, Technology Law, Copyright Litigation, Patent Litigation, Commercial Insurance Litigation, Contract Litigation, Contract Breach, Contract Interference, Commercial Litigation and Dispute Resolution, Dispute Resolution and Business Litigation, Los Angeles - Kevin McBride</description>
	<lastBuildDate>Tue, 08 Mar 2011 23:51:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Business Method &amp; Software Patents Survive Biliski v. Kappos</title>
		<link>http://www.mcbride-law.com/2010/06/28/business-method-software-patents-survive-biliski-v-kappos/</link>
		<comments>http://www.mcbride-law.com/2010/06/28/business-method-software-patents-survive-biliski-v-kappos/#comments</comments>
		<pubDate>Mon, 28 Jun 2010 17:09:31 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[Biliski]]></category>
		<category><![CDATA[bright-line tests in patent litigation]]></category>
		<category><![CDATA[business method patents]]></category>
		<category><![CDATA[Parker v. Flook; machine-or-transformation test]]></category>
		<category><![CDATA[patent litigation]]></category>
		<category><![CDATA[software patents]]></category>

		<guid isPermaLink="false">http://www.mcbride-law.com/?p=1174</guid>
		<description><![CDATA[If there is an overriding lesson to take away from Biliski, I believe it is this: bright-line tests in patent litigation no longer exist.  Virtually all patent litigation now requires nuanced argument, with expert interpretation, similar to practice in general commercial litigation. ]]></description>
			<content:encoded><![CDATA[<p>In <strong><em><a href="http://www.mcbride-law.com/wp-content/uploads/2010/06/Bilski-v.-Kappos-US-2010.pdf">Biliski v. Kappos</a></em></strong> the United States Supreme Court issued its long-awaited decision on business method patents.   The bottom line:  <strong><em>business method patents are still recognized as patentable inventions</em></strong>.  By implication, software patents (called into question by the Federal Circuit&#8217;s <em>en banc</em> decision in the case below) also remain alive.</p>
<p>Biliski involved a patent claim for hedging the risk of price fluctuations in the economy.  The patent examiner rejected the patent application, explaining it “‘is not implemented on a specific apparatus and merely manipulates [an] abstract idea and solves a purely mathematical problem without any limitation to a practical application, therefore, the invention is not directed to the technological arts.&#8221;</p>
<p>The examiner&#8217;s rejection was affirmed by the Board of Patent Appeals and by the Federal Circuit Court.  However, in its <em>en banc</em> decision (that produced 5 separate opinions), the Federal Circuit took the additional step of declaring that a method was <strong><em>only</em></strong> patent eligible if: (1) it is tied to a particular machine or apparatus, or (2) it transforms a particular article into a differentstate or thing.  This test is known as the “machine-or-transformation test.&#8221;</p>
<p>Because the vast majority of software applications are designed only for a &#8220;general purpose&#8221; computing machine, the question remained after the Federal Circuit&#8217;s Biliski opinion as to <em>whether software patents were patentable at all</em>.</p>
<p>The US Supreme Court affirmed the examiner&#8217;s rejection of this particular patent application, <strong><em>but rejected the &#8220;machine-or-transformation&#8221; test imposed by the Federal Circuit </em></strong>and, in its final opinion of the October, 2009 term, restored a degree of normalcy to patent practice in the United States.</p>
<p><span id="more-1174"></span></p>
<p>The signature of this Supreme Court in the past 12 years of patent decisions has been to end the various “bright-line” tests for patentability established by the Federal Circuit Court of Appeals, in favor of “functional” tests that can only be determined in a courtroom, after input from expert witnesses on both sides of the patentability test.</p>
<p>This approach to patent law was continued in <strong><em>Biliski v. Kappos</em></strong>.  The majority opinion, authored by Justice Kennedy, used traditional rules of statutory construction to reach its opinion that the &#8220;machine-or-transformation&#8221; test was just <em>one method</em> for determining patentability of a business method patent&#8211;<strong><em>not</em></strong> <em>the only method</em>.</p>
<p>The majority reasoned that 35 U. S. C. §273(b)(1), in an infringement action, creates a prior-use defense against &#8220;a method in [a] patent;&#8221;  <em>ipso facto</em> §273 implies a broad definition of the statutory term &#8220;method.&#8221;  The Court explained:</p>
<blockquote><p>For purposes of this defense alone, “method” is defined as “a method of doing or conducting business.” In other words, by allowing this defense the statute itself acknowledges that there may be business method patents. Section 273’s definition of “method,” to be sure, cannot change the meaning of a prior-enacted statute. But what §273 does is clarify the understanding that a business method is simply one kind of “method” that is, at least in some circumstances, eligible for patenting under §101.</p></blockquote>
<p>The majority opinion reasoned that if business methods are not patentable in any circumstances, §273 would be rendered meaningless.  &#8220;This would violate the canon against interpreting any statutory provision in a manner that would render another provision superfluous.&#8221;</p>
<p>Thus, rather than adopting categorical rules that &#8220;might have wide-ranging and unforeseen impacts,&#8221; the Court resolved Biliski narrowly: (1) on the basis of standard statutory construction, and (2) on the basis of previous decisions (<a href="http://en.wikipedia.org/wiki/Parker_v._Flook"><em><strong>Parker v. Flook </strong></em></a>and <a href="http://en.wikipedia.org/wiki/Diamond_v._Diehr"><em><strong>Diamond v. Diehr</strong></em></a>) which show that petitioners’ claims are not patentable processes because they are attempts to patent abstract ideas.</p>
<p>In a separate opinion concurring in the result, Justice Stevens (in his last written opinion on the Court) rejected the majority&#8217;s approach to statutory construction in patent cases.  A long-time opponent of software patents, Justice Stevens argued that:</p>
<blockquote><p>[T]he Court at points appears to reject the well-settled proposition that the term“process” in §101 is not a “‘process’ in the ordinary sense of the word,” <em>Flook</em>, 437 U. S., at 588. Instead, the Court posits that the word “process” must be understood in light of its “ordinary, contemporary, common meaning.&#8221;  <strong><em>Although this is a fine approach to statutory interpretation in general, it is a deeply flawed approach to a statute that relies on complex terms of art developed against a particular historical background.</em></strong> [Emphasis added.]</p></blockquote>
<p>While there are many possibile interpretations of the Court&#8217;s opinion, I believe this focus is possibly the most instrucive to clients and counsel anticipating patent litigation: <strong><em>the Court will continue to decide patent cases according to standard rules of construction, while ignoring (for the most part) the complex terms of art developed against a particular historical background. </em></strong>Indeed, this has been the pattern of Court decisions for at least the past 12 years. <em>See</em>, <a href="http://www.mcbride-law.com/2009/12/26/the-end-of-bright-line-tests-in-patent-litigation/"><em><strong>The End of Bright-Line Tests in Patent Litigation</strong></em></a>.</p>
<p>General commercial litigation typically involves the standard rules of statutory construction applied by the US Supreme Court in <strong><em>Biliski</em></strong>.  However, historicially patent litigators have generally dealt with more constrained, concrete and predicatible rules of construction&#8211;more in keeping with the predicability desired by scientists and mathmeticians involved in the world of patenting. </p>
<p>If there is an overriding lesson to take away from Biliski, I believe it is this: bright-line tests in patent litigation no longer exist (for the foreseeable future).  Going forward, patent litigation will require nuanced argument, with expert interpretation, similar to practice in general commercial litigation.  This will exponentially increase the cost burden associated with patent litigation.</p>
<p>The majority opinion was authored by <a href="http://en.wikipedia.org/wiki/Anthony_Kennedy">Justice Anthony Kennedy</a>; joined (except for sec. II) by <a href="http://en.wikipedia.org/wiki/Antonin_Scalia">Justice Scalia</a>, and by the remainder of the conservative wing of the Court: <a href="http://en.wikipedia.org/wiki/Clarence_Thomas">Justice Thomas</a>, <a href="http://en.wikipedia.org/wiki/John_G._Roberts">Chief Justice Roberts</a> and <a href="http://en.wikipedia.org/wiki/Samuel_Alito">Justice Alito</a>.   The makeup of this majority reflects the statutory-construction basis for the decision.</p>
<p><a href="http://en.wikipedia.org/wiki/John_Paul_Stevens">Mr. Justice Stevens&#8217; </a>concurring opinion was joined by the liberal wing of the Court: <a href="http://en.wikipedia.org/wiki/Sonia_Sotomayor">Justice Sotomayor</a>, <a href="http://en.wikipedia.org/wiki/Ruth_Bader_Ginsburg">Justice Ginsberg </a>and <a href="http://en.wikipedia.org/wiki/Stephen_Breyer">Justice Breyer</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2010/06/28/business-method-software-patents-survive-biliski-v-kappos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Obviousness&#8221; v. &#8220;Anticipation&#8221;—Similar but Different Patent Law Defenses</title>
		<link>http://www.mcbride-law.com/2010/03/02/obviousness-v-anticipation%e2%80%94similar-but-different-patent-law-defenses/</link>
		<comments>http://www.mcbride-law.com/2010/03/02/obviousness-v-anticipation%e2%80%94similar-but-different-patent-law-defenses/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 02:44:48 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[35 USC 102]]></category>
		<category><![CDATA[35 USC 103]]></category>
		<category><![CDATA[anticipation]]></category>
		<category><![CDATA[comaper v. best buy]]></category>
		<category><![CDATA[Federal Circuit Court]]></category>
		<category><![CDATA[KSR]]></category>
		<category><![CDATA[obvious to try]]></category>
		<category><![CDATA[obviousness]]></category>
		<category><![CDATA[patent litigation]]></category>
		<category><![CDATA[teaching-suggestion-motivation]]></category>
		<category><![CDATA[Theronese v. Beckton Dickson]]></category>
		<category><![CDATA[TSM test]]></category>

		<guid isPermaLink="false">http://www.mcbride-law.com/?p=1063</guid>
		<description><![CDATA[“Anticipation” is a patent defense that must be based on a single prior art reference. 

“Obviousness” is a patent defense that may be based on multiple prior art references; but requires the additional element of proof that a "teaching" suggests a "motivation" to combine the elements of the prior art references into a single invention.]]></description>
			<content:encoded><![CDATA[<p>In two recent Federal Circuit Court cases, <em><strong><a href="http://www.mcbride-law.com/wp-content/uploads/2010/03/Comaper-Corp.-v.-BestBuy-Fed.Cir_.2010obviousness-v.-anticipation.pdf"><em><strong>Comaper v. Best Buy</strong></em></a> </strong></em>and <em><strong><a href="http://www.mcbride-law.com/wp-content/uploads/2010/03/theronese-v.-becton-dickson-fed.cir_.2010anticipation.pdf">Theronese v. Beckton Dickson</a></strong></em>, the district courts below erroneously applied patent law defenses of “anticipation” and “obviousness.” The Federal Circuit’s discussion of each case provides a useful framework to understand these inter-related defenses. </p>
<p>The Federal Circuit Court explained:</p>
<p style="padding-left: 30px;">“Anticipation” [under <a href="http://www.law.cornell.edu/uscode/html/uscode35/usc_sec_35_00000102----000-.html">35 USC §102</a>] is a patent defense that must be based on a single prior art reference.  For a claim to be anticipated, each claim element must be disclosed, either expressly or inherently, in a single prior art reference, and the claimed arrangement or combination of those elements must also be disclosed, either expressly or inherently, in that same prior art reference.</p>
<p style="padding-left: 30px;">“Obviousness” [under <a href="http://www.law.cornell.edu/uscode/html/uscode35/usc_sec_35_00000103----000-.html">35 USC §103</a>] is a patent defense that may be based on multiple prior art references. Determining obviousness requires considering whether two or more pieces of prior art could be combined, or a single piece of prior art could be modified, to produce the claimed invention. This analysis typically invokes the familiar teaching-suggestion-motivation (“TSM”) test, asking whether a person having ordinary skill in the art would have found some teaching, suggestion, or motivation to combine or modify the prior art references.</p>
<p>“Anticipation” requires only <strong><em>one step</em></strong> to prove, <strong><em>if</em></strong> a single prior art reference is available.  If a single document teaches all elements of a patent, in the same arrangement, the single prior art reference can invalidate the target patent. (Subject to a clear and convincing evidence standard for issued patents).</p>
<p>“Obviousness” requires <strong><em>two steps</em></strong> to prove.  Even though multiple patents can be used as prior art references, there must also be a “teaching” that suggests a “motivation” to combine the prior art references into a single new invention (<strong><em>the “TSM” test</em></strong>).  The “suggestion” to combine can be provided by the references themselves, through another document, or via affidavit or declaration testimony of a person of ordinary skill in the art of the invention.<br />
<span id="more-1063"></span><br />
In its landmark decision on patent obviousness, <a href="http://en.wikipedia.org/wiki/KSR_v._Teleflex"><em><strong>KSR International Co. v. Teleflex, Inc.</strong></em></a>, the US Supreme Court emphasized that motivation may be present even if a combination just was <strong><em>obvious to try</em></strong>:</p>
<blockquote><p>“[c]ommon sense teaches . . . that familiar items may have obvious uses beyond their primary purposes, and in many cases a person of ordinary skill will be able to fit the teachings of multiple patents together like pieces of a puzzle.”</p>
<p>Thus, [w]hen there is a design need or market pressure to solve a problem and there are a finite number of identified, predictable solutions, a person of ordinary skill has good reason to pursue the known options within his or her technical grasp. If this leads to the anticipated success, it is likely the product not of innovation but of ordinary skill and common sense. <strong><em>In that instance the fact that a combination was obvious to try might show that it was obvious under [35 U.S.C.] § 103</em></strong>.</p></blockquote>
<p>In one of the two cases referenced above, <em>Comaper v. Best Buy</em>, a jury found that the main independent claims for a computer fan housing were not obvious; but the dependent claims were obvious.  On post-trial motions, counsel argued it was logically impossible for independent claims to be non-obvious while the claims upon which they depend to be obvious. </p>
<p>The district court rejected these arguments under an analysis that seemed (to the Federal Circuit) to require a single prior art teaching in order to find obviousness.  Pointing out the district court’s legal and logic flaws, the Federal Circuit explained that the “single prior art” teaching governs anticipation, not obviousness.  The Federal Circuit then went on to find that the claimed invention was obvious as a matter of law once multiple available prior art references were considered from the vantage point of one of ordinary skill in the art.</p>
<p>In the other case referenced above, <em>Theronese v. Beckton,</em> the district court instructed the jury that “anticipation” could be found if a single reference taught one skilled in the art that “all of the claimed elements <strong><em>could have been arranged</em></strong> as in the claimed invention.”</p>
<p>The Federal Circuit Court rejected this instruction, again because of an inherent logical flaw: it was logically possible that individual claim elements “could have been arranged” in a way that is not itself described or depicted in the anticipatory reference.</p>
<p>The Federal Circuit Court explained:</p>
<p style="padding-left: 30px;">Inherency may not be established by probabilities or possibilities. The mere fact that a certain thing may result from a given set of circumstances is not sufficient.</p>
<p style="padding-left: 30px;">For a claim to be anticipated, each claim element must be disclosed, either expressly or inherently, in a single prior art reference, and the claimed arrangement or combination of those elements must also be disclosed, either expressly or inherently, in that same prior art reference.</p>
<p>The defenses of “anticipation” and “obviousness” are related, but different.  And as the Federal Circuit Court’s opinions imply, a periodic refresher in the set theory analysis can also be useful to patent litigation practitioners.</p>
<p>See the related article: <a href="http://www.mcbride-law.com/2009/12/26/the-end-of-bright-line-tests-in-patent-litigation/"><em><strong>The End of Bright-Line Tests in Patent Litigation</strong></em></a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2010/03/02/obviousness-v-anticipation%e2%80%94similar-but-different-patent-law-defenses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>“Intent” to Induce Patent Infringement, Revisited</title>
		<link>http://www.mcbride-law.com/2010/02/11/%e2%80%9cintent%e2%80%9d-to-induce-patent-infringement-revisited/</link>
		<comments>http://www.mcbride-law.com/2010/02/11/%e2%80%9cintent%e2%80%9d-to-induce-patent-infringement-revisited/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 15:35:57 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[34 USC 271(b)]]></category>
		<category><![CDATA[actual infringement]]></category>
		<category><![CDATA[constructive knowledge]]></category>
		<category><![CDATA[deliberately disregards]]></category>
		<category><![CDATA[DSU Med. Corp.]]></category>
		<category><![CDATA[induce infringement]]></category>
		<category><![CDATA[Judge Randall R. Radar]]></category>
		<category><![CDATA[Judge Richard Linn]]></category>
		<category><![CDATA[Judge Steven C. Robinson]]></category>
		<category><![CDATA[Judge William C. Bryson]]></category>
		<category><![CDATA[known risk]]></category>
		<category><![CDATA[Norman H. Zivin]]></category>
		<category><![CDATA[patent infringement]]></category>
		<category><![CDATA[SEB SA]]></category>
		<category><![CDATA[SEB v. Montgomery Ward]]></category>
		<category><![CDATA[specific intent]]></category>
		<category><![CDATA[T-Fal Corp]]></category>

		<guid isPermaLink="false">http://www.mcbride-law.com/?p=882</guid>
		<description><![CDATA["Constructive knowledge” is sufficient for inducing infringement where a person deliberately disregards a known risk that a patent exists.]]></description>
			<content:encoded><![CDATA[<p>“Whoever actively induces infringement of a patent shall be liable as an infringer.” <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_271.htm">35 USC §271(b)</a>.</p>
<p>But what does it mean to “actively induce” infringement? </p>
<p>Inducement requires a showing of <strong><em>specific intent</em></strong> to encourage <strong><em>another’s infringement</em></strong>. The Federal Circuit is now developing the definition of “intent” required for active inducement, one case at a time.<span id="more-882"></span></p>
<p>In a 2006 case, <strong><em><a href="http://www.mcbride-law.com/wp-content/uploads/2010/02/DMU-Medical-Corp.-v.-JMS-Corp.-Fed.Cir_.2006.pdf">DSU Med. Corp. v. JMS Corp</a></em></strong>., The Federal Circuit ruled:</p>
<blockquote><p>The plaintiff must show that the alleged infringer <strong><em>knew or should have known</em></strong> that his actions would induce <strong><em>actual</em></strong> infringements. This requirement <strong><em>necessarily includes</em></strong> the requirement that <strong><em>he or she knew of the patent</em></strong><em>.</em></p></blockquote>
<p>In other words, it is not enough to just induce the <strong><em>act</em></strong> of direct infringement. <strong><em>Without</em></strong> <strong><em>knowledge of the</em></strong> <strong><em>patent itself</em></strong>, a person <strong><em>cannot induce infringement</em></strong> for the purposes of §271(b). </p>
<p>But an important unresolved question remained after under <em>DSU Med Corp</em>.: must “knowledge” of the patent be “actual” knowledge, or will “constructive” knowledge suffice?</p>
<p>The Federal Circuit addressed this question in a recent (Feb. 2010) case, <em><a href="http://www.mcbride-law.com/wp-content/uploads/2010/02/SEB-v.-T-Fal-Fed.Cir_.2010contributory-infringement-test.pdf"><strong>SEB v. Montgomery Ward</strong></a></em>., finding “constructive knowledge” for the purpose of inducing infringement where a person <strong><em>deliberately disregards</em></strong> a <strong><em>known risk</em></strong> that a patent exists. </p>
<p>The Court ruled: ”[A] claim for inducement is viable even where the patentee has not produced direct evidence that the accused infringer actually knew of the patent-in-suit.”</p>
<p>In the SEB case, the record showed <strong><em>no direct evidence</em></strong> that the defendant had <strong><em>actual</em></strong> knowledge of the patent.  However, the record showed the defendant copied a new-and-improved rice cooker by having it designed and built in Hong Kong, and then imported to the United States.  The defendant also hired an attorney to conduct a right-to-use study, but did not tell him that it had based its new rice cooker on the product sold by the plaintiff. </p>
<p>The Federal Circuit found this conduct a <strong><em>deliberate disregard</em></strong> of the <strong><em>known risk</em></strong> that plaintiff had a patent.</p>
<p>Following the rationale of other courts, the Federal Circuit explained that:</p>
<blockquote><p>“[S]pecific intent” in the civil context is not so narrow as to allow an accused wrongdoer to actively disregard a known risk that an element of the offense exists. <span style="text-decoration: underline;">See Crawford-El v. Britton</span>, 951 F.2d 1314, 1318 (D.C. Cir. 1991) (equating specific intent and deliberate indifference); <span style="text-decoration: underline;">Boim v. Holy Land Found. for Relief &amp; Dev.</span>, 549 F.3d 685, 693 (7th Cir. 2008) (equating intentional misconduct with knowledge and deliberate indifference).</p></blockquote>
<p>The Federal Circuit further explained that “a failure to inform one’s counsel of copying would be highly suggestive of deliberate indifference in most circumstances.”</p>
<p>The Court closed its opinion with a dictum to be addressed in the future:</p>
<blockquote><p>Our opinion does not purport to establish the outer limits of the type of knowledge needed for inducement. For instance, a patentee may perhaps only need to show constructive knowledge with persuasive evidence of disregard for clear patent markings, similar to the constructive notice requirement in § 287(a).</p></blockquote>
<p>Apparently, the Federal Circuit intends to further develop the “intent” requirement for inducing infringement in future cases, as proper fact patterns are presented.</p>
<p>Prevailing counsel in SEB SA v. T-Fal Corp. was <a href="http://www.cooperdunham.com/professionals/partners/norman-zivin">Norman H. Zivin</a></p>
<p>The Federal Circuit panel included: <a href="http://www.cafc.uscourts.gov/judgbios.html#Rader">Judge Randall R. Radar</a>, <a href="http://www.cafc.uscourts.gov/judgbios.html#Bryson">Judge William C. Bryson </a>and <a href="http://www.cafc.uscourts.gov/judgbios.html#Linn">Judge Richard Linn</a>.</p>
<p>The Southern District of New York judge in the case below was <a href="http://www.nysd.uscourts.gov/judge_info.php?id=75">Judge Steven C. Robinson</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2010/02/11/%e2%80%9cintent%e2%80%9d-to-induce-patent-infringement-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pre-Internet Patent Specification Fails to Anticipate Internet-Based Embodiments</title>
		<link>http://www.mcbride-law.com/2010/01/23/pre-internet-patent-specification-fails-to-include-internet-based-embodiments/</link>
		<comments>http://www.mcbride-law.com/2010/01/23/pre-internet-patent-specification-fails-to-include-internet-based-embodiments/#comments</comments>
		<pubDate>Sat, 23 Jan 2010 15:57:41 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[Catch Curve v. Venali]]></category>
		<category><![CDATA[claim construction]]></category>
		<category><![CDATA[Dean C. Pregerson]]></category>
		<category><![CDATA[fax protocol]]></category>
		<category><![CDATA[Federal Circuit]]></category>
		<category><![CDATA[John C. Carey]]></category>
		<category><![CDATA[Markman]]></category>
		<category><![CDATA[Pauline Newman]]></category>
		<category><![CDATA[specification]]></category>
		<category><![CDATA[Timothy B. Dyk]]></category>
		<category><![CDATA[William C. Bryson]]></category>

		<guid isPermaLink="false">http://www.mcbride-law.com/?p=504</guid>
		<description><![CDATA[The patent's specification is always highly relevant to claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.
]]></description>
			<content:encoded><![CDATA[<p>In <em><strong><a href="http://www.mcbride-law.com/wp-content/uploads/2010/01/CatchCurve-v.-Venali-Fed.Cir_.2010fax-machine-non-infringement.pdf">Catch Curve v. Venali</a></strong></em>, the plaintiff owns five patents covering a fax transmission technology. The first patent was filed in 1988, well before commercialization of the Internet.</p>
<p>All five patents referred to a common specification. The specification makes clear that fax messages are sent and received over a switched telephone network using fax protocol. At the <a href="http://en.wikipedia.org/wiki/Markman_hearing"><em><strong>Markman</strong></em></a> hearing, the district court limited the patents to communications routed over a switched telephone network.</p>
<p>The defendant has a later-generation fax technology that relies on IP protocol instead of fax protocol. The defendant’s system converts messages into formats other than fax protocol before storing or forwarding the messages and then transmits the messages to their intended destinations via SMTP, HTTP, or HTTPS protocol over the Internet.</p>
<p>Based on this difference in protocols, the district court entered summary judgment of non-infringement.<span id="more-504"></span></p>
<p>Catch Curve argued on appeal the patent claims are not limited to a specific protocol. According to Catch Curve, a fax message refers to the “image data” that is transmitted by a fax machine, independent from the transmission protocol used. This argument, however, ignores the specification, which specifies that fax messages are sent and received over a switched telephone network using fax protocol.</p>
<p>In patent claim construction, the metes and bounds of claims are restricted to the embodiments (practical examples) of the invention set out by the inventor in the specification.</p>
<p>The claims are always read in the context of the specification, and may not exceed the embodiments set forth in the specification by the inventor.</p>
<p>In the instant case, because the specification was first filed in 1988, a reference to “existing fax terminal machines” pertains to technology as it existed at that time. Nothing in the specification suggests that the fax messages of the invention are converted to a different format and transmitted to the recipient over a medium other than a switched telephone network.</p>
<p>This non-precedential opinion highlights the practical difficulty of reading pre-Internet patent claims onto Internet-based systems. The case also reinforces Federal Circuit teaching that the patent specification is always highly relevant to claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.</p>
<p>For a general discussion of claim construction rules see, <a href="http://www.mcbride-law.com/2010/01/20/the-basics-of-patent-claim-construction/"><em><strong>The Basics of Patent Claim Construction</strong></em></a>.</p>
<p>Prevailing counsel in the case was <a href="http://www.crgplaw.com/john_carey.html">John C. Carey</a>, Miami.</p>
<p>The Federal Circuit panel included <a href="http://www.cafc.uscourts.gov/judgbios.html#Newman">Judge Pauline Newman</a>, <a href="http://www.cafc.uscourts.gov/judgbios.html#Bryson">Judge William C. Bryson</a>, and <a href="http://www.cafc.uscourts.gov/judgbios.html#Dyk">Judge Timothy B. Dyk</a>. The Federal Circuit opinion is non-precedential.</p>
<p>The trial judge was <a href="http://www.cacd.uscourts.gov/CACD/CourtDir.nsf/e4da2e24040ebe038825688700688ff9/2ca44c18d70f5dda882568b30062b7b9?OpenDocument">Dean D. Pregerson</a>, <a href="http://www.cacd.uscourts.gov/">Central District of California</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2010/01/23/pre-internet-patent-specification-fails-to-include-internet-based-embodiments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Patent Damages Handbook for use by Federal District Court Judges</title>
		<link>http://www.mcbride-law.com/2010/01/21/new-patent-damages-handbook-for-use-by-federal-district-court-judges/</link>
		<comments>http://www.mcbride-law.com/2010/01/21/new-patent-damages-handbook-for-use-by-federal-district-court-judges/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 22:26:54 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[bifurcated trial]]></category>
		<category><![CDATA[confidential information]]></category>
		<category><![CDATA[Daubert motions]]></category>
		<category><![CDATA[document production]]></category>
		<category><![CDATA[limits on depositions]]></category>
		<category><![CDATA[patent damages]]></category>
		<category><![CDATA[Patent Damages Handbook]]></category>
		<category><![CDATA[phasing discovery]]></category>
		<category><![CDATA[protective orders]]></category>

		<guid isPermaLink="false">http://www.mcbride-law.com/blog/?p=466</guid>
		<description><![CDATA[Patent litigation lawyers need to familiarize themselves with the new Patent Damages Handbook at a detailed level]]></description>
			<content:encoded><![CDATA[<p>As reported today by <em><strong><a href="http://www.foley.com/people/bio.aspx?employeeid=26326">Justin Gray </a></strong></em>at his patent blogsite, <a href="http://www.grayonclaims.com"><em><strong>Gray on Claims</strong></em></a>, a new Patent Damages Handbook has been prepared at the direction of Fed. Circuit Chief Justice Michel for use by federal district court judges in patent cases.</p>
<p>Needless to say, this new Patent Damages Handbook is required reading for all patent litigation attorneys.  A free copy of the Handbook can be downloaded from Gray on Claims, <a href="http://www.grayonclaims.com/home/2010/1/21/new-patent-damages-handbook-released.html"><em><strong>here</strong></em></a>.</p>
<p>Highlights of the 34-page handbook are outlined below under the following headings:<span id="more-466"></span></p>
<ul>
<li><em>Types of Damages<br />
</em></li>
<li><em>Initial Estimate of Damages and Rule 26 Disclosures</em></li>
<li><em>Limits on Depositions</em></li>
<li><em>Possibility of Bifurcated Trial</em></li>
<li><em>Protective Orders<br />
</em></li>
<li><em>Confidential Information<br />
</em></li>
<li><em>Limits on Depositions</em></li>
<li><em>Document Production</em></li>
<li><em>SJ Motions on Damages<br />
</em></li>
<li><em>Daubert Motions<br />
</em></li>
<li><em>Verdict Forms at Trial</em></li>
</ul>
<p><strong><em>Types of Damages</em></strong></p>
<p>Compensatory patent infringement damages attempt to assess the difference between the patentee’s pecuniary condition after the infringement, and what his condition would have been if the infringement had not occurred. The question to be asked in determining such damages is: “had the Infringer not infringed, what would [the] Patent Holder have made?”</p>
<p>Compensatory patent damages traditionally fall into three categories: lost profits; established royalty, and reasonable royalty.</p>
<p><span style="text-decoration: underline;">Lost profits</span> normally are profits that would have been made by the patentee “but for” the infringement.</p>
<p><span style="text-decoration: underline;">Established royalty</span> can be shown when the patentee has consistently licensed others to engage in conduct comparable to the defendant’s at a uniform, established royalty rate.</p>
<p><span style="text-decoration: underline;">Reasonable royalty</span> damages can be calculated by determining what a willing licensee in the place of the infringer reasonably would have paid and what a willing licensor in the place of the patentee reasonably would have accepted for the grant of a license, had such a license been negotiated just before the infringement began, with both parties assuming the patent was valid, enforceable and infringed.</p>
<p><strong><em>Initial Estimate of Damages and Rule 26 Disclosures</em></strong></p>
<p>Any lack of specificity in the complaint may well be overcome by the requirement of Rule 26 that the patent owner voluntarily provide damages information and documents as part of its initial disclosures. Any initial damages calculations that are provided reasonably may be considered preliminary or approximate. At the same time, courts should not accept skeletal initial damages disclosures uncritically.</p>
<p>Meaningful compliance with the initial damages disclosure requirements can be essential to the efficient management of the litigation, and courts overseeing damages disclosures should be mindful of the role these disclosures may play in the early resolution of the litigation.</p>
<p>Failure to provide good faith damages disclosures and at least “high level” damages discovery at the outset of the litigation may hinder settlement discussions, delay settlement, and result in unnecessary expenditure of time, money and judicial resources.</p>
<p><strong><em>Phasing Discovery</em></strong></p>
<p>To minimize burden and improve efficiency, courts should consider, as part of the initial case assessment and scheduling, whether the interests of justice would be served by phasing damages discovery. For example, after the mandatory Rule 26 damages disclosures and the above-described initial “top level” damages disclosures from both parties, the court may choose to stay some or all damages discovery until after the court’s ruling on claim construction.</p>
<p><strong><em>Possibility of Bifurcated Trial</em></strong></p>
<p>Some courts opt to bifurcate patent infringement cases into liability and damages phases for both discovery and trial. Rule 42 gives courts wide discretion to separate issues or claims at trial “[f]or convenience, to avoid prejudice, or to expedite and economize . . . .” Damages can be tried by a different jury after all issues of liability have been finally resolved, both at trial and on appeal.</p>
<p>Under this approach, the court can streamline the case and reduce the burden on judicial resources by trying damages only when (and if) it becomes necessary to do so.</p>
<p><strong><em>Early Protective Orders</em></strong></p>
<p>It is important that a protective order be in place early in the case: Most patent litigants will not produce documents without one, and there is no reason to allow this issue to cause any delay in conducting discovery.</p>
<p><strong><em>Confidential Information</em></strong></p>
<p>One of the most common areas of dispute in protective orders is who will be allowed access to the confidential information and whether a two-tier protective order is necessary or appropriate. One approach is to have a single-tier protective order that provides only a single level of “confidential” protection that allows designated materials to be disclosed to both in-house and outside counsel.</p>
<p>In many cases, one or both of the parties believe the information to be disclosed is so highly confidential and competitively sensitive as to merit an extra level, or “second tier,” of confidentiality protection. Such additional protection is often necessary where employees or in-house counsel for the receiving party are involved in competitive decision making, “e.g., patent strategy, licensing negotiations, sales and marketing, and research and development in<br />
[the] relevant product market.”</p>
<p><strong><em>Limits on Depositions</em></strong></p>
<p>Absent agreement by the parties, courts should permit deviations from the ten-deposition limit only with a cogent and particularized explanation of what specific additional depositions are necessary – and why – and a showing that the additional depositions genuinely are necessary and will not be redundant. Vague references to the complexity of the case or to large amounts at stake should not be sufficient. One approach that is gaining favor is that of limiting the number of deposition hours to be allowed to each party. This may be the preferred approach in highly complex cases, as many different witnesses may need to be deposed. Limiting the number of deposition hours forces counsel to plan carefully for each deposition and to use their time wisely. The result is often more efficient discovery than would be achieved by simply limiting the number of deponents.</p>
<p>Rule 30(b) (6) depositions often are useful in patent infringement cases. Courts should guard against “runaway 30(b) (6) depositions,” however, and ensure that they are not used to evade the limits on the number of depositions. One effective approach is for the initial scheduling order to provide that “each day of [Rule] 30(b) (6) deposition counts as a separate deposition for purposes of the per-side deposition limit.</p>
<p><strong><em>Document Production</em></strong></p>
<p>Courts should be particularly cautious about granting requests for production of “all documents” relating to a particular issue, especially when dealing with electronically stored information, unless it is clear that such production is reasonably calculated to lead to the discovery of better or more probative evidence on that issue, and is not propounded for the purpose of increasing cost, disrupting the litigation, or otherwise harassing the party from whom discovery is sought. Courts also should ensure that Rule 34 requests for production are not abused and should take steps to facilitate effective, cost-efficient document production. The need for judicial control and oversight is particularly acute when addressing requests directed to electronically stored information</p>
<p>The parties’ discovery plan also should address the format for document production, particularly as it relates to electronically stored documents. Courts should consider the potential cost and time savings that may result by allowing (or requiring) production of financial or other damages-related data in a format that permits ready manipulation for purposes of damages analyses.</p>
<p><strong><em>SJ Motions on Damages</em></strong></p>
<p>It is often appropriate for the court to consider summary judgment motions relating to damages at the same time as – but separate from – Daubert challenges to the experts’ opinions. Delaying resolution of summary judgment motions until the eve of trial is inefficient for both the parties and the court. It is best to resolve summary judgment motions well in advance of the final pretrial conference (indeed, well in advance of the meetings of counsel that typically precede the final pretrial conference), so that the court and the parties can prepare their pretrial submissions and prepare for trial knowing precisely what issues must be tried.</p>
<p>There are damages-related issues that may not depend on expert testimony, and it is often best to resolve such issues as early as possible since they, too, can affect a damages expert’s analysis. Where it is possible to do so, addressing such issues before the exchange of expert reports can yield significant efficiencies and cost savings.</p>
<p><strong><em>Daubert Motions</em></strong></p>
<p>Critical to managing a patent trial is the court’s ability to control expert testimony. No issue in a patent trial cries out for strict application of the gatekeeping tools of Federal Rule of Evidence 702 and the Supreme Court’s Daubert decision more than damages.</p>
<p>Challenges to expert testimony on patent damages usually focus on the qualifications of the expert to opine on the issues and the reliability of the expert’s analysis of those issues.</p>
<p>The reliability analysis focuses on the expert’s analysis itself, that is, whether the analysis is conclusory or misapplies an accepted methodology. This issue arises most often in connection with the determination of a reasonable royalty, which is usually based on a multi-factored framework for identifying the royalty to which the parties would have agreed had they conducted a negotiation when the infringement first began, knowing that the patent was valid and infringed, and willing to enter into a license agreement.</p>
<p><strong><em>Verdict Forms at Trial</em></strong></p>
<p>Although the law does not require a trial court to use a special verdict in patent cases it is advisable for the court to do so. The Supreme Court has noted, “in cases that reach the jury, a special verdict and/or interrogatories on each claim element could be very useful in facilitating review, uniformity, and possibly post-verdict judgments as a matter of law.&#8221;</p>
<p><strong><em>Summary</em></strong></p>
<p>The above excerpts are only a few highlights from the new Patent Damages Handbook for use by federal district court judges. Obviously, practitioners and judges need to familiarize themselves with this Handbook at a detailed level.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2010/01/21/new-patent-damages-handbook-for-use-by-federal-district-court-judges/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Basics of Patent Claim Construction</title>
		<link>http://www.mcbride-law.com/2010/01/20/the-basics-of-patent-claim-construction/</link>
		<comments>http://www.mcbride-law.com/2010/01/20/the-basics-of-patent-claim-construction/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 05:05:33 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[claim construction]]></category>
		<category><![CDATA[Otis Elevator]]></category>
		<category><![CDATA[patent litigation]]></category>
		<category><![CDATA[patent specification]]></category>
		<category><![CDATA[patents]]></category>
		<category><![CDATA[Philips v. AVH]]></category>
		<category><![CDATA[prosecution history]]></category>
		<category><![CDATA[Schindler Elevator]]></category>

		<guid isPermaLink="false">http://www.mcbride-law.com/?p=414</guid>
		<description><![CDATA[To arrive at the “ordinary and customary meaning” of a patent claim term, the court evaluates (a) the <em>words of the</em> <em>claim</em>, (b) the patent <em>specification</em>, (c) the <em>prosecution history</em>, and (d) <em>extrinsic evidence</em> concerning relevant scientific principles, the meaning of technical terms, and the state of the art.
]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://www.mcbride-law.com/wp-content/uploads/2010/01/Schindler-Elevator-v.-Otis-Elevator-Fed.C.r.2010claim-construction.pdf"><em><strong>Schindler Elevator v. Otis Elevator</strong></em></a>, the Federal Circuit Court of Appeals again re-visited the basics of patent claim construction. Understanding claim construction can seem daunting to clients—even lawyers. But the Federal Circuit Court never seems to tire of setting out the basic rules of claim construction to continue its educational efforts in this core area of intellectual property practice. <span id="more-414"></span></p>
<p>In this most recent case, the Schindler Elevator invention was a “smart” elevator that can recognize a specific user when he or she enters the building; then automatically sends an elevator car for the user; then takes the user a specific floor.</p>
<p> The terms at issue on appeal were “information transmitter” and “information device.”  These were the parts of the invention that recognized an elevator user when he or she entered the building and transmitted the relevant information to the elevator.  The district court construed these terms to mean a system that would work “without requiring any sort of personal action by the passenger.”  By this definition, the patent only covered automatic elevators that did not so much as require the user to lift a finger to be recognized.</p>
<p> On appeal, the Federal Circuit found this definition to be too narrow, and struck the words “without requiring any sort of personal action by the passenger” from the definition of the terms “information transmitter and “information device,” holding the district court had not interpreted the patent properly.</p>
<p> A claim term is generally given its “ordinary and customary meaning,” which is “the meaning that the term would have to a <em>person of ordinary skill in the art</em> in question <em>at the time of the invention</em>.” <strong><em><a href="http://caselaw.lp.findlaw.com/data2/circs/fed/031269pv2.pdf">Phillips v. AWH Corp</a></em></strong>.  To arrive at the “ordinary and customary meaning” of a patent claim term, the court evaluates (a) the <em>words of the</em> <em>claim</em>, (b) the patent <em>specification</em>, (c) the <em>prosecution history</em>, and (d) <em>extrinsic evidence</em> concerning relevant scientific principles, the meaning of technical terms, and the state of the art.</p>
<p><strong><em>Words of the Claim</em></strong></p>
<p> The place to start in claim construction is the words of the claim.   The patent claim sets out the &#8220;metes and bounds&#8221; of the intellectual property description&#8211;the claimed invention.  Since the ultimate objective of claim construction is to ascertain the limits of the claimed invention, the words used in the claims themselves are of greatest importance.</p>
<ul>
<li> Are the words of a claim specifically defined in the patent?  If so, this definition is usually accepted by the court.</li>
<li>Do the claim words have a clearly-understood meaning to one of ordinary skill in the art? </li>
<li>What is the context in which the words are used in the particular claim sentence and in the overall claim paragraphs?  Does the context make common sense and consistent with the overall purpose of the patented invention?</li>
<li> How are the words used in other claims of the patent, and elsewhere throughout the patent?  Again, consistency is the key.  If the patent lawyer defined a word one way in the patent, it will mean the same thing throughout the patent.</li>
</ul>
<p> In the <em>Schindler Elevator</em> case, the Federal Circuit read the patent to allow the possibility of a transmitter “carried by an elevator user.” Carrying a transmitter is thus a type of “personal action” expressly allowed by the claims. The Federal Circuit reasoned that since the patent does not require the transmitter to be carried in any particular way, it was logically foreseeable that the user might raise his or her hand to activate the elevator.  Therefore, limiting the scope of the patent to an invention not requiring “any sort of personal action by the passenger” was too narrow.</p>
<p><strong><em> Patent Specification</em></strong></p>
<p> The patent specification is the part of the patent that shows various examples of how the invention can be enabled, or put into practice. </p>
<p>The specification is a &#8220;reality check&#8221; on the intent of the inventor, limiting claims that extend beyond the examples (enablements) set out in the specification.  Therefore, the patent specification is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the single best guide to the meaning of a disputed term.</p>
<p>Turning again to the<em> Schindler Elevator</em> analysis, the Federal Court pointed out that he phrase “personal action” is used only once in the Schindler Elevator specification, in the following sentence:</p>
<blockquote><p>The advantages achieved by the invention reside in the fact that the desired journey destination is communicated automatically to the elevator control by (1) the information transmitters carried by the elevator users <span style="text-decoration: underline;">or</span> by (2) the recognition of features of the elevator users without any personal action being required by the passenger.</p></blockquote>
<p> Because the Schindler Elevator specification allowed for an information transmitter actually carried by the elevator user, the Federal Circuit reasoned that an information transmitter requiring no personal action was only <em>one optional use of the device</em>.  Therefore, logically, limiting the scope of the patent to an invention not requiring “any sort of personal action by the passenger” was too narrow.</p>
<p> <strong><em>Prosecution History</em></strong></p>
<p>Prosecution history is the entire patent file holding the communications back and forth between the inventor and the patent office during the patenting process.  Thus, if the inventor willingly narrowed the scope of his or her patent claim in order to get the patent approved by the patent office, this information will be contained in the file history (sometimes called the &#8220;file wrapper&#8221;).   </p>
<p>The purpose of consulting the prosecution history in construing a claim is to exclude any interpretation that was disclaimed during prosecution, thereby making the claim scope narrower than it would otherwise be.  <strong><em><a href="http://caselaw.lp.findlaw.com/data2/circs/fed/031269pv2.pdf">Phillips</a></em></strong> at 1317.</p>
<p> The doctrine of prosecution disclaimer attaches where an applicant, whether by amendment or by argument, “unequivocally disavowed a certain meaning to obtain his patent.”  An argument made to an examiner constitutes a disclaimer only if it is “clear and unmistakable.”</p>
<p>Turning back again to the <em>Schindler Elevator</em> case, the district court found statements in the prosecution history which describe the invention as operating “automatically, contactlessly, and independently of the orientation of the information transmitter.” The district court read these statements as unambiguously disavowing the use of a passenger’s hands for any and all purposes. The Federal Circuit Court disagreed. As in the specification, those terms modify actions that take place only <span style="text-decoration: underline;">after</span> the passenger has brought the transmitter within range of the recognition device.  Therefore there was no “clear and unmistakable” disclaimer.</p>
<p>The Federal Circuit Court therefore modified the district court’s construction of “information transmitter” and “recognition device” by striking the phrase “without requiring any sort of personal action by the passenger” from each construction.</p>
<p><strong><em>Extrinsic Evidence</em></strong></p>
<p>Extrinsic evidence of the meaning of claim terms in a patent is found in things like dictionaries and professional treatises.  This is called &#8220;extrinsic&#8221; evidence because it is found &#8220;outside&#8221; the content of the patent itself.  Because extrinsic evidence is outside the content of the patent, it is the least reliable source of information as to a patent&#8217;s meaning, and is sometimes ignored by the parties in claim construction analysis.</p>
<p>Indeed, in the <em>Schindler Elevator</em> case, extrinsic evidence was not admitted by the parties at the <strong><em><a href="http://en.wikipedia.org/wiki/Markman_hearing">Markman</a></em></strong> claim construction hearing, so the Federal Circuit did not address the extrinsic evidence factor of claim construction.   </p>
<p><strong><em>Summary</em></strong></p>
<p>Claim construction can be a daunting process, but the Federal Circuit Court of Appeals strives in case after case to re-visit the straightforward logic of its claim construction rules—rules that can be learned by anyone.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2010/01/20/the-basics-of-patent-claim-construction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The End of Bright-Line Tests in Patent Litigation</title>
		<link>http://www.mcbride-law.com/2009/12/26/the-end-of-bright-line-tests-in-patent-litigation/</link>
		<comments>http://www.mcbride-law.com/2009/12/26/the-end-of-bright-line-tests-in-patent-litigation/#comments</comments>
		<pubDate>Sun, 27 Dec 2009 04:35:16 +0000</pubDate>
		<dc:creator>Kevin McBride</dc:creator>
				<category><![CDATA[Patent Law]]></category>
		<category><![CDATA[Bilski]]></category>
		<category><![CDATA[eBay]]></category>
		<category><![CDATA[Federal Circuit]]></category>
		<category><![CDATA[Festo]]></category>
		<category><![CDATA[Genentech]]></category>
		<category><![CDATA[Kappos]]></category>
		<category><![CDATA[KSR]]></category>
		<category><![CDATA[Medimmune]]></category>
		<category><![CDATA[Mercexchange]]></category>
		<category><![CDATA[method patents]]></category>
		<category><![CDATA[obvious to try]]></category>
		<category><![CDATA[obviousness]]></category>
		<category><![CDATA[patent litigation]]></category>
		<category><![CDATA[patentability]]></category>
		<category><![CDATA[patents]]></category>
		<category><![CDATA[Pfaff]]></category>
		<category><![CDATA[Shoketsu]]></category>
		<category><![CDATA[Signature Financial]]></category>
		<category><![CDATA[software patents]]></category>
		<category><![CDATA[State Street Bank]]></category>
		<category><![CDATA[Teleflex]]></category>
		<category><![CDATA[Warner-Jenkinson]]></category>
		<category><![CDATA[Wells Electronics]]></category>

		<guid isPermaLink="false">http://mcbride.harrisrashid.com/?p=10</guid>
		<description><![CDATA[In <strong>Bilski v. Kappos</strong>, the United Supreme Court is deciding whether a patentable "process" must be tied to a particular machine or apparatus or transfer an article into a different state or thing.  The Court's ruling in this case portends possible dramatic changes  to the world of software and internet patents, most of which are process-based and operate on general-purpose computing platforms.]]></description>
			<content:encoded><![CDATA[<p>In <strong><a href="http://www.patentlyo.com/patent/2009/11/supreme-court-hears-bilski-v-kappos.html">Bilski v. Kappos</a></strong>, the United Supreme Court is deciding whether a patentable &#8220;process&#8221; must be tied to a particular machine or apparatus or transfer an article into a different state or thing. The Court&#8217;s ruling in this case portends possible dramatic changes to the world of software and internet patents, most of which are process-based and operate on general-purpose computing platforms. Supreme Court watchers forecast a ruling in <em>Bilski </em>that may substantially limit the practice of granting a process-based patent application unless the patent is tied to a physical “machine.”</p>
<p>Such a ruling would overturn a broad scope of process patenting that has been recognized since the Federal Circuit’s ruling in the seminal business-methods patenting case, <strong><a href="http://en.wikipedia.org/wiki/State_Street_Bank_v._Signature_Financial_Group">State Street Bank &amp; Trust Co. v. Signature Financial Group</a></strong> (Fed.Cir.1998). Such a ruling would also call into question the validity of many internet and software patents, virtually none of which is tied to a specific physical machine. The key question to be answered by the Supreme Court is, of course, whether a physical machine (needed to support a methods-based patent) can also include a general-purpose computer.<span id="more-10"></span></p>
<p>The signature of this Supreme Court in the past 12 years of patent decisions has been to end the various “bright-line” tests for patentability established by the Federal Circuit Court of Appeals, in favor of “functional” tests that can only be determined in a courtroom, after input from expert witnesses on both sides of the patentability test. This, of course, is a particularly expensive and risky exercise. The presumption of validity and various bright-line tests had allowed small companies to litigate a patent with fewer hurdles to patentability. But the practical effect of these recent US Supreme Court cases has been to<strong><em> tip the scales of justice away from small-company patentees</em></strong> who depended on “bright-line” patentability tests, and in favor of big company defendants who depend on numerous hurdles to patentability in defending patent cases.</p>
<p>This tendency away from bright-line tests was most recently highlighted in the US Supreme Court’s 2007 ruling in<strong> <a href="http://en.wikipedia.org/wiki/KSR_v._Teleflex">KSR v. Teleflex</a></strong>. Under pre-KSR law, a patent was <strong><em>presumed valid</em></strong> unless <strong><em>written prior art </em></strong>existed that <strong><em>explicitly</em></strong> taught an element of the patent. KSR changed that test by ruling that (a) even <strong><em>implicit</em></strong> knowledge possessed by one of ordinary skill in the art could make an element of the patent “obvious” and (b) that obviousness would be found if the element was “obvious to try” to a person of ordinary skill in the art. In effect, the US Supreme Court erased an important bright-line test for patent validity that had been controlling Federal Circuit law for 23 years.</p>
<p>With this significant shift in analysis away from a “bright line” test to a “functional” test, many, if not most, software patents have been put at risk, even though few commentators have been willing to acknowledge that fact publicly. Because software patents normally cover incremental increases in the knowledge in any particular area, it is usually easy for defendants to argue that a particular software patent was obvious to others of ordinary skill, and that a particular subroutine would be “obvious to try.”</p>
<p>In at least five other major patent cases decided by the Supreme Court since 1997, an overriding theme has been to narrow the scope of patentable inventions and eliminate various bright-line tests by the Federal Circuit in one area or another of patent law:</p>
<ul>
<li><strong><a href="http://en.wikipedia.org/wiki/MedImmune,_Inc._v._Genentech,_Inc.">Medimmune v. Genentech</a></strong>, 127 S.Ct. 764 (2007) eliminated the bright-line test for protection against a declaratory judgment action by a prospective patent licensee;</li>
<li><strong><a href="http://en.wikipedia.org/wiki/EBay_Inc._v._MercExchange,_L.L.C.">eBay, Inc. v. Mercexchange, LLC</a>.</strong>, 126 S.Ct. 1837 (2006) stopped the practice of granting an automatic permanent injunction after a successful trial verdict;</li>
<li><strong><a href="http://en.wikipedia.org/wiki/Festo_Corp._v._Shoketsu_Kinzoku_Kogyo_Kabushiki_Co.">Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co</a>.</strong>, 535 US 722 (2002) narrowed patentability by ruling that prosecution history estoppel arises from any amendment that narrows the patent claims;</li>
<li><strong><a href="http://en.wikipedia.org/wiki/Pfaff_v._Wells_Electronics,_Inc.">Pfaff v. Wells Electronics, Inc</a>,</strong>, 525 US 55 (1998) narrowed patentability by construing the &#8220;on-sale bar&#8221; to patentability to be measured from the first commercial offer for sale of an inventive product, even where the invention has not yet been reduced to practice; and</li>
<li><strong><a href="http://en.wikipedia.org/wiki/Warner-Jenkinson_Company,_Inc._v._Hilton_Davis_Chemical_Co.">Warner-Jenkinson Company, Inc. v. Hilton Davis Chemical Co</a></strong>., 520 US 17 (1997) eliminated a bright-line test in evaluating prosecution history estoppel.</li>
</ul>
<p>The net effect of these US Supreme Court rulings has been to place so many hurdles in the way of small-company patentees that litigation against large-company patent violators is impractical in all but the most clear-cut cases. The Court’s ruling in <em>Bilski v. Tappos</em> may well provide another high hurdle to most small-company patent litigation if software and internet patents are subjected to yet an additional murky legal test for patentability.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mcbride-law.com/2009/12/26/the-end-of-bright-line-tests-in-patent-litigation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

