MEMORANDUM OPINION
Pending before the Court are Defendant Symantec Corporation’s (“Symantec”) motion for patent invalidity under 35 U.S.C. § 101 (C.A. No. 10-1067 (“Symantec case”) D.I. 698) and Defendants Trend Micro Incorporated and Trend Micro, Inc. (USA)’s (“Trend Micro”) motion for judgment of invalidity under 35 U.S.C. § 101 (C.A. No. 12-1581 (“Trend Micro case”) D.I. 175) of certain claims of U.S. Patent Nos. 6,460,-050 (the “ ’050 patent”), 6,073,142 (the “142 patent”), and 5,987,610 (the “’610 patent”) (collectively, “patents-in-suit”) asserted by Intellectual Ventures ILLC (“IV”).
For the reasons discussed below, the Court will grant in part and deny in part Symantec’s and Trend Micro’s motions. Specifically, the Court concludes that Sym-antec and Trend Micro (“Defendants”) have proven that IV’s ’050 and 142 patents are not patent eligible but have failed to prove that IV’s ’610 patent is not patent eligible.
BACKGROUND
Nature and Stage of the Proceedings
IV sued Symantec, Trend Micro, Check Point Software Technologies Inc., Check Point Software Technologies Ltd., and McAfee, Inc. on December 8, 2010 alleging infringement of the ’050, 142, and ’610-patents, as well as U.S. Patent No. 7,506,-155 (the “155 patent”). (D.I.I)
Symantec filed an answer and counterclaims against IV on January 31, 2011. (D.I.23) Trend Micro filed an answer and counterclaims against IV on February 14, 2011. (D.I.28)
On November 21, 2012, the Court severed the Trend Micro case from the Sym-antec case. (D.I.412) The Court construed disputed claim terms on December 12, 2012. (D.I.425, 426)
• claims 9, 16, and 22 of the ’050 patent;
• claims 1, 7, 21, and 22 of the ’142 patent; and
• claim 7 of the ’610 patent.
On February 6, 2015, the jury returned a verdict finding IV had failed to prove that Symantec infringes the asserted claims of the ’050 patent and had proven that Sym-antec infringes the asserted claims of the ’142 and ’610 patents. (D.I.676) The jury found that Symantec had failed to prove that any of the asserted claims were invalid due to anticipation or obviousness. (Id.) The jury awarded IV $17 million in damages. (Id.)
IV has asserted the following claims against Trend Micro:
• claims 9,13,16, 22, and 24 of the ’050 patent;
• claims 1, 7, 17, 21, 22, 24, and 26 of the T42 patent; and
• claim 7 of the ’610 patent.
(C.A. 12-1581 D.I. 176 at 4,17, 23)
On January 6, 2015, the Court issued a pretrial order in the Symantec case stating that it would “resolve any § 101 issues in connection with post-trial motions and briefing, including hearing any testimony that must be presented[,] only after the conclusion of the forthcoming trial.” (D.I. 615 at 3)
On March 4, 2015, the Court issued a schedule for briefing and oral argument on the § 101 issues in both cases. (D.I.692) The parties completed briefing on April 2, 2015. The Court heard oral argument on April 10, 2015. (See Tr.)
Patents-in-Suit
The ’050 patent, entitled “Distributed content identification system,” generally discloses a method for classifying content of received files by creating a content identifier and then comparing that content identifier to a database of other identifiers. It was filed on December 22, 1999 and issued on October 1, 2002. The patent is directed to filtering e-mail messages, and particularly spam and viruses, by generating a digital identifier for a message, forwarding that identifier to a processing system, determining whether the forwarded identifier matches a characteristic of other identifiers, and then processing the message based on the results of that determination. (See ’050 patent at 2:37-43)
The ’142 patent, entitled “Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments,” was filed on June. 23, 1997 and issued on June 6, 2000. It relates generally to providing an efficient way for business organizations to control the handling of emails and other data objects. Pursuant to business rules, messages are gated, then reviewed by an administrator, and eventually (if safe) directed to their intended recipients. (See T42 patent at 3:3-20, 4:40-54)
LEGAL STANDARDS
Symantec’s Rule 52(c) Motion
“Under Fed.R.Civ.P. 52(c), the court has discretion to enter judgment on any issue after hearing the evidence.” In re Brimonidine Patent Litig.,
Trend Micro’s Motion
Trend Micro' filed its motion pursuant to the Court’s oral order of March 4, 2015. (C.A. No. 12-1581 D.I. 171)
To defeat a motion for summary judgment, the nonmoving party must “do more than simply show that there is some metaphysical doubt as to the material facts.”
Lack of Patentable Subject Matter
Under 35 U.S.C. § 101, “[whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.” There are three exceptions to § 101’s broad patent-eligibility principles: “laws of nature, physical phenomena, and abstract ideas.” Diamond v. Chakrabarty,
In Mayo Collaborative Servs. v. Prometheus Labs., Inc., — U.S.-,
“Simply appending conventional steps, specified at a high level of generality, [is] not enough to supply an inventive concept.” Id. at 2357 (internal quotation marks omitted; emphasis in original). In Bilski v. Kappos,
In determining, at the second step, if a patent embodies an inventive concept, courts may consider whether the process “is tied to a particular machine or apparatus” or “transforms a particular article into a different state or thing.” Bilski
“[T]he machine-or-transformation test is a useful and important clue, an investigative tool, for determining whether some claimed inventions are processes under § 101.” Bilski
Standard of Proof for Lack of Patentable Subject Matter
“Whether a claim is drawn to-patent-eligible subject matter under § 101 is an issue of law....” In re Bilski
Symantec and Trend Micro contend that because patent eligibility is a question of law, they are not obligated to persuade the Court by clear and convincing evidence of the ineligibility of the patents-in-suit. (See D.I. 724 at 2; C.A. No. 12-1581 D.I. 190 at
In Ultramercial, Inc. v. Hulu, LLC,
In these circumstances, District Courts, including this District, have taken varying approaches. See, e.g., In re TLI Communications LLC Patent Litigation,
Given the Court’s conclusions on the merits of the pending motions, it is unnecessary to resolve the parties’ dispute over the standard of proof. For the reasons explained below, the Court would find the ’050 and ’142 patents are patent ineligible even assuming it must impose on Defendants a burden of clear and convincing evidence. Similarly, the Court would conclude that the ’610 patent is not patent ineligible even if this issue must be resolved as a question of law on which Defendants confront, at most, a burden of a preponderance of the evidence.
DISCUSSION
Symantec and Trend Micro argue that the asserted claims are patent-ineligible under the analytical framework set forth in Mayo and Alice. (See D.I. 699 at 2; C.A. No. 12-1581 D.I. 176 at 2) Symantec contends that “[e]ach of IV’s asserted claims [in the Symantec case] covers generic computer implementation of abstract ideas” and “do[es] not provide an ‘inventive concept’ ” that would satisfy the Mayo test for subject-matter eligibility. (D.I. 699 at 2, 5) Trend Micro similarly argues that “[b]ecause the asserted claims of the patents-in-suit are directed to abstract ideas, and because the added computer-related limitations are merely generic and do not add inventive concepts beyond the abstract ideas themselves, none of the asserted claims of the three patents-in-suit are eligible for patent protection.” (C.A. No. 12-1581 D.I. 176 at 29)
IV responds that “[t]he Court should reject Symantec’s sweeping indictment of software patentability, especially when it comes to the Patents-in-Suit, which pass every test the Supreme Court and the Federal Circuit have articulated for patent eligibility.” (D.I. 722 at 1 (emphasis in original)) IV focuses on the Federal Circuit’s post-Aiice opinion in DDR Holdings, LLC v. Hotels.com,
With this general description of the parties’ positions, the Court will now address the specific challenges to the eligibility of each of the three patents-in-suit.
’050 Patent
The asserted claims (9, 13, 16, 22, and 24) of the ’050 patent are method claims. Claims 9, 16, and 22 are independent. Claim 13 depends from claim 9. Claim 24 depends from claim 23, which depends from claim 22.
Independent claim 9 recites as follows:
A method for identifying characteristics of data files, comprising:
receiving, on a processing system, file content identifiers for data files from a plurality of file content identifier generator agents, each agent provided on a source system and creating file content IDs using a mathematical algorithm, via a network;
determining, on the processing system, whether each received content identifier matches a characteristic of other identifiers; and
outputting, to at least one of the source systems responsive to a request from said source system, an indication of the characteristic of the data file based on said step of determining.
Dependent claim 13 recites:
The method of claim 9 wherein each said data file is an email message and said step of determining comprises determining whether said email is SPAM.
Independent claim 16 recites:
A method of filtering an email message, comprising:
receiving, on a second computer, a digital content identifier created using a mathematical algorithm unique to the message content from at least two of a plurality of first computers having digital content ID generator agents;
comparing, on the second computer, the digital content identifier to a characteristic database of digital content identifiers received from said plurality of first computers to determine whether the message has a characteristic; and
responding to a query from at least one of said plurality of computers to identify the existence or absence of said characteristic of the message based on said comparing.
Independent claim 22 recites:
A method for providing a service on the Internet, comprising:
collecting data on a processing system from a plurality of systems having a client agent generating digital content identifiers created using a mathematical algorithm for each of a plurality of files on the Internet to a server having a database;
characterizing the files on the server system based on said digital content identifiers received relative to other digital content identifiers collected in the database; and
transmitting a substance identifier from the server to the client agent indicating the presence or absence of a characteristic in the file.
Dependent claim 28 (referenced in claim 24) recites:
The method of claim 22 wherein said step of collecting comprises collecting a digital identifier for a data file.
Dependent claim 21 recites:
The method of claim 23 wherein said file content is an e-mail.
Mayo Step 1: Are the asserted claims directed to a patent-ineligible “abstract idea”?
“First, given the nature of the invention in this case, we determine whether the claims at issue are directed to a patent-ineligible abstract idea.” DDR Holdings,
• receiving one or more file/digital content identifiers generated using a mathematical algorithm (which is unique to “message content” in claim 16);
• comparing the received identifer(s) to other identifer(s) (and “classifying the files” based on this comparison in claim 22); and
• outputting either (a) a descriptor of the content (claim 9), (b) an identification of whether or not the message is of a certain type/classification (claim 16), or (c) an indication of the presence or absence of a characteristic (claim 22).
(See generally D.I. 425 (construing relevant claim terms))
Symantec argues that the ’050 patent is a “classic example” of solving a problem “by using a computer to perform a general-purpose method in the same manner ‘as a person would do it by head and hand’ or ‘by using a pen and paper.’ ” (D.I. 699 at 15 (citing CyberSource,
The asserted claims of the ’050 patent are also similar to the claims found to be abstract in Content Extraction. (See C.A. No. 12-1581 D.I. 176 at 6-10) The ’050 patent covers the steps of collecting, recognizing, and storing data, like the claims at issue in Content Extraction. The only additional step in the ’050 patent is communicating a result of the “recognizing” step back to a querying computer, but this step, too, is abstract. See buySAEE, Inc. v. Google, Inc.,
IV relies on DDR Holdings as the most analogous precedent, asserting, “As in DDR Holdings, the ’050 Patent does not ‘generically claim ‘use of the Internet’ to perform an abstract business practice’ and does provide solutions necessarily rooted in computer technology to problems specifically arising in the realm of computer networks. DDR Holdings,
Another helpful way of assessing whether the claims of the patent are directed to an abstract idea is to consider if all of the steps of the claim could be performed by human beings in a non-computerized “brick and mortar” context. See, e.g, buySAFE,
(D.I. 699 at 18-19; C.A. No. 12-1581 D.I. 176 at 6-7) The above examples illustrate that the concepts of the ’050 patent are directed to an abstract idea and are not necessarily rooted in computer technology.
■The analysis above is based solely on the claims, specification, and file history of the ’050 patent; what is referred to in the context of claim construction as intrinsic evidence. See Teva Pharms. USA, Inc. v. Sandoz, Inc., — U.S. -, -,
The parties have also put extrinsic evidence before the Court. When this additional evidence is considered, it bolsters the conclusions the Court has already reached based solely on the intrinsic evidence: that the asserted claims of the ’050 patent are directed to an abstract idea.
The inventors of the ’050 patent admitted in deposition testimony that the invention of the ’050 patent could be implemented by humans, albeit more slowly and less accurately than it is performed by a conventional computer:
Q. Okay. So if we were to consider people to be a form of computer, then it could be performed by people, you could put people' — another way to say it is you could put people in place of the computers here andthe invention would work the same, just more slowly and less accurately....
A. Yes, because people are essentially general purpose computers, so yes.
(D.I. 700 Ex. E at 47)
Q. So other than breaking the emails down into smaller parts, how could one have compared like to like in the way that you wanted to?
A. You would have used a human, who are very good at comparing things.
Q. You could have used a person?
A. Yes.
(D.I. 700 Ex. F at 131-32) IV has not identified any contradictory evidence from the patent’s inventors.
Instead, as part of its effort to counter the conclusion that the asserted claims of the ’050 patent are directed to an abstract idea, IV analogizes its claims to those discussed in recent guidance from the PTO. Specifically, IV cites a hypothetical claim the PTO indicated would be deemed patent eligible by an examiner. See Interim Eligibility Guidance, supra note 6. The PTO’s hypothetical claim is directed to creating “sanitized” versions of computer files by “extracting, via file parsing, the malicious code” from computer files. Id. The PTO’s example is necessarily rooted in computer technology because malicious code or “viruses” have no significance outside the realm of computer technology. The ’050 patent, by contrast, is directed to abstract steps that could generally be performed outside of a computing context.
Thus, the Court disagrees with IVs contention that the asserted claims of the ’050 patent are “inextricably tied to computer technology and distinct from the types of concepts found by the courts to be abstract.” (D.I. 723-2 at 2) Instead, the Court concludes that — regardless of the standard of proof — the asserted claims of the ’050 patent are directed to an abstract idea of receiving identifying information, comparing it to other information, and outputting an indication based on the identifying information. Thus, it is necessary to proceed to the second step of the analysis.
Mayo Step 2: Do the asserted claims include an “inventive concept” sufficient to “ensure that the patent in practice amounts to significantly more” than a patent upon an ineligible concept ?
The asserted claims of the ’050 patent may still be patent-eligible if they include an “inventive concept” sufficient to “ensure that the patent in practice amounts to significantly more” than a patent upon an ineligible concept. Alice,
The non-computer limitations comttidn • to all of the independent, asserted claims ' cover the abstract idea of “receiving ari identifier for a data file, matching it against previously-received identifiers to ascertain a characteristic of the data file, and outputting a result.” (See C.A. No. 12-1581 D.I. 176 at 4-7) “Simply appending conventional steps, specified at a high level of generality, [is] not enough to supply an inventive concept.” Alice,
IV points to other limitations foutíd jü&fy ' in certain asserted claims as démbástiMfe 4 Vi
With respect to claim 16, IV contends that the word, “unique” (the “uniqueness limitation”) relates to the “hashing” functionality covered by the ’050 patent. (C.A. No. 12-1581 D.I. 188 at 22) IV touts the uniqueness limitation as part of an “innovative combination” of limitations that comprise an inventive concept. Id. at 22. But hashing is just one of many mathematical algorithms that could be used to implement the uniqueness limitation of claim 16. According to DDR Holdings, the very case on which IV places such heavy reliance, “[w]e know that mathematical algorithms, including those executed on a generic computer, are abstract ideas.”
Similarly, the “characterizing” limitation in claim 22 does not add an inventive concept necessary to save claim 22 from ineligibility. The Court construed the characterizing limitation in claim 22 to mean “classifying the files on the server system by comparing their digital content identifiers to other digital identifiers collected in the database.” (D.I. 425 at 13) This is similar to a limitation at issue in Cyber-Source — reciting “utilizing the map of credit card numbers to determine if the credit card transaction is valid” — which was part of a claim found to be patent-ineligible. See
Likewise, none of the asserted claims are made patent eligible by the set of alternative steps for outputting either (a) a descriptor of the content (claim 9), (b) an identification of whether or not the message is of a certain type/classification (claim 16), or (c) an indication of the presence or absence of a characteristic (claim 22). Each of these limitations is essentially the same for purposes of the § 101 analysis as each covers communicating descriptive information about content or a message using a generic computer implementation. These limitations are part of the same abstract idea, and none add any inventive concept to the asserted claims.
Nor do the limitations in dependent claims 13, 23, or 24, which limit the independent claims on which they depend to the particular technological environment of SPAM email detection, render these three claims patent eligible. In Alice, the Supreme Court noted that “limiting the use of an abstract idea ‘to a particular technological environment’” is “not enough for patent eligibility.”
IV argues, “Taken as a whole, these claimed steps [in the asserted claims of the ’050 patent] narrowly define a set of actions tied to a specific way of describing file content and classifying computer files.” (D.I. 722 at 22 (emphasis added)) However, the combination of limitations pointed to by IV is nothing more than a generic computer implementation of the human-executable abstract idea discussed above. The Court broadly construed key phrases in the ’050 patent — including, for example, construing “file content identifier” as anything “reflecting at least a portion of the content of a data file, but not constituting merely an excised portion of that data
IV argues that the asserted claims satisfy the machine-or-transformation test because they use a generic computer for implementation, the “computer (the machine) is critical for implementing the claims of the Patents-in-Suit,” and “ ‘none of these limitations could be performed by a human alone.’” (D.I. 183 at 30 (citing Helios Software, LLC v. SpectorSoft Corp.,
Regarding exclusion of certain patents from eligibility under § 101, the Supreme Court stated in Alice,
The Court’s conclusion that the claims of the ’050 patent lack an inventive concept is based solely on the intrinsic evidence, as described above. The extrinsic evidence provides further support for this conclusion. Specifically, the inventors of the ’050 patent admitted that hashing was well known at the time of invention of the ’050 patent. (See D.I. 700, Ex. E, deposition of Brooks Talley, at 34-37 (“Q- Do you agree that it’s fair to say that prior to the conception of the ’050 patent it was well known to use hashing as a way to reduce a large amount of data to a small amount of data to confirm that two data objects were
In light of the foregoing, the Court determines that the asserted claims of the ’050 patent are ineligible under § 101.
’142 Patent
Asserted claims 1, 17, 21, 22, 24, and 26 are independent; asserted claim 7 depends from claim 1. Claims 1, 7, and 24 are directed to. “post office” apparatuses. Claims 17, 21, 22, and 26 are process claims directed to the same basic functionality performed by the components of the asserted apparatus claims.
Independent claim 1 recites as follows:
A post office for receiving and redistributing e-mail messages on a computer network, the post office comprising:
a receipt mechanism that receives an email message from a sender, the e-mail message having at least one specified recipient;
a database of business rules, each business rule specifying an action for controlling the delivery of an e-mail message as a function of an attribute of the e-mail message;
a rule engine coupled to receive an email message from the receipt mechanism and coupled to the database to selectively apply the business rules to the e-mail message to determine from selected ones of the business rules a set of actions to be applied to the e-mail message; and
a distribution mechanism coupled to receive the set of actions from the rule engine and apply at least one action thereof to the e-mail message to control delivery of the e-mail message and which in response to the rule engine applying an action of deferring delivery of the e-mail message, the distribution engine automatically combines the email message with a new distribution list specifying at least one destination post office for receiving the e-mail message for review by an administrator associated with the destination post office, and a rule history specifying the business rules that were determined to be applicable to the e-mail message by at least one rule engine, and automatically delivers the e-mail message to a first destination post office on the distribution list instead of a specified recipient of the email message.
Dependent claim 7 recites:
The post office of claim 1, further comprising:
a primary message store, coupled to the receipt engine, for receiving and non-persistently storing e-mail messages; and
a secondary message store, coupled to the distribution engine, for receiving therefrom, and persistently storing an email message in response to the rule engine specifying the action that the email message be reviewed by an administrator recipient prior to delivery to a specified recipient.
Independent claims 17 recites:
A process for controlling the delivery of e-mail message in a business, comprising:
providing to a post office a set of business rules derived from business communication policies, each business rule defining an action applied to an e-mail message based on the attribute of the message;
receiving messages at the post office;
to at least one message received at the post office, applying the business rules to the attributes of the message to determine at least one action of deferring delivery to be applied to the message; automatically combining the e-mail message with a new distribution list specifying at least one destination post office for receiving the e-mail message for review by an administrator associated with the destination post office and a rule history specifying at least one business rule determined to be applicable to the e-mail message; and
automatically delivering the e-mail message to a destination post office on the distribution list instead of a specified recipient of the e-mail message.
Independent claim 21 recites:
A process for deferring the delivery of selected e-mail messages, comprising:
storing a database of business rules, each business rule specifying an action for controlling the delivery of an e-mail message as a function of an attribute of the e-mail message;
receiving a plurality of e-mail messages at a first post office, each e-mail message having at least one specified recipient;
selecting at least one e-mail message from the plurality of e-mail messages by applying at least one business rule to the e-mail message;
delivering each non-selected e-mail message to its specified recipients; and
deferring the selected e-mail message by:
automatically combining the selected email message with a new distribution list specifying at least one new destination post office for receiving the e-mail message for review by an administrator associated with the destination post office and a rule history specifying at least one business rule determined to be applicable to the e-mail message;
automatically delivering the selected email message to a destination post office on the distribution list instead of a specified recipient of the e-mail message;
persistently storing the selected e-mail message in a storage area of the destination post office until the selected email message is reviewed prior to any further delivery of the e-mail message to its specified recipients or to another destination post office on the distribution list.
Independent claim 22 recites:
A computer implemented process for reviewing an e-mail message, comprising:
receiving the e-mail message at a first post office, the e-mail message having at least one specified recipient;
deferring the e-mail message by:
automatically combining the selected email message with a new distribution list specifying at least one second post office for receiving the e-mail message for review by an administrator associated with the second post office and a rule history specifying at least one business rule determined to be applicable to the e-mail message; and
automatically delivering the selected email message to an administrator at the second post office on the distribution list instead of a specified recipient of the email message;
persistently storing the e-mail message at the second post office until the e-mail message is reviewed;
automatically reviewing the e-mail message after a specified time interval to determine an action to be applied to the e-mail message; and
automatically applying the action to the e-mail message.
Independent claim 21 recites:
A post office for receiving and redistributing data objects on a computer network, the post office comprising:
a receipt mechanism that receives a data object from a sender, the data object having at least one specified recipient;a database of business rules, each business rule specifying an action for controlling the delivery of a data object as a function of an attribute of the data object;
a rule engine coupled to receive a data object from the receipt mechanism and coupled to the database to selectively apply the business rules to the ■ data object to determine from selected ones of the business rules a set of actions to be applied to the data object; and
a distribution mechanism coupled to receive the set of actions from the rule engine and apply at least one action thereof to the data object to control delivery of the data object and which in response to the rule engine applying an action of deferring delivery of the data object, the distribution engine automatically combines the data object with a new distribution list specifying at least one new destination post office for receiving the data object for review by an administrator associated with the destination post office and a rule history specifying at least one business rule determined to be applicable to the data object by at least one rule engine, and automatically delivers the data object to a first destination post office on the distribution list instead of a specified recipient of the data object.
Independent claim 26 recites:
A process for deferring the delivery of selected data objects, comprising:
storing a database of business rules, each business rule specifying an action for controlling the delivery of a data object as a function of an attribute of the data object;
receiving a plurality of data objects at a first post office, each data object having at least one specified recipient;
selecting at least one data object from the plurality of data objects by applying at least one business rule to the data object;
delivering each non-selected data object to its specified recipients;
deferring the selected data object by:
automatically combining the selected data object with a new distribution list specifying at least one new destination post office for receiving the data object for review by an administrator associated with the destination post office; and a rule history specifying at least one business rule determined to be' applicable to the data object;
automatically delivering the selected data object to a - destination post office on the distribution list instead of a specified recipient of the data object; and persistently storing the data object in a storage area until the data object is reviewed prior to any further delivery of the data object to its specified recipients.
Mayo Step 1
The asserted claims of the ’142 patent cover the following concepts:
• receiving one or more emails or data objects (“messages”) addressed to at least one recipient (all claims);
• providing at least one business rule applicable to the message(s) (all claims);
• each business rule specifying an action based on an attribute of the message(s) (claims 1, 7, 17, 21, 24, and 26);
• selectively applying one or more business rules to determine at least one action to be applied to the message(s) (claims 1, 17, 21, 24, and 26);
• applying at least one of the action(s) (claims 1, 22, and 24);
• deferring delivery of at least one message by attaching a new distribution list to the message(s) and sending them to an administrator with a rule history list specifying at least one rule applicable to the message(s) (all claims);
• delivering non-selected message(s) to their original recipient(s) (claims 21 and 26);
• persistently storing selected messages(s) until they may be reviewed by the administrator (claims 7, 21, 22, and 26); and
• automatically reviewing persistently stored message(s) that have not been reviewed by the administrator after a specified time interval to determine and apply an action to the message^) (claim 22).
Symantec contends that “[t]he asserted claims of the ’142 patent represent a classic case of merely ‘[s]tating an abstract idea while adding the words ‘apply it with a computer.” ’ (D.I. 699 at 6 (citing Alice,
IV argues that the ’142 patent addresses a problem “specifically arising in the realm of computer networks.” (D.I. 722 at 13 (citing DDR Holdings, -
The Court disagrees. Instead, the claims of the ’142 patent are in essence directed to generic computer implementation of an abstract idea, which does not make the abstract idea patent eligible.
Addressing each of the asserted claims of the ’142 patent individually is unnecessary since “all the claims are ‘substantially similar and linked to the same abstract idea.’ ” Content Extraction,
[[Image here]]
(C.A. No. 12-1581 D.1.176 at 19-20)
(D.I. 699 at 10-11)
IV argues that these analogies are inaccurate, as the analogies' — unlike the asserted patent claims — are not limited to “email” messages. But the suggestion that this makes the claims patent eligible is unavailing. As Defendants observe, in Alice the Supreme Court found ineligible patent claims that were purely computer oriented, as did the Federal Circuit in Ultramercial and Content Extraction. (See, e.g., Tr. at 56) Aside from the limita
As with the ’050 patent, the Court’s conclusion that the asserted claims of the ’142 patent fail Mayo’s step 1 is derived solely from the claims, specification, and file history. Additionally, as with the ’050 patent, the parties have provided extrinsic evidence. Again, this extrinsic evidence confirms the Court’s conclusion that the asserted claims are directed to an abstract idea.
In particular, Trend Micro quotes from IV’s technology tutorial, submitted June 5, 2012 (C.A. No. 12-1581 D.I. 177, Ex. E at 49), to show that even IV believes that, conceptually, the “post office” components, which are central to implementing the asserted claims, are “not much different” from brick-and-mortar U.S. Post Offices. In the tutorial, IV told the Court:
In a business email environment business rules are applied at the “post office.” In the typical environment, the post office resides on a mail server, where the company’s emails are received, processed, and routed to recipients. Conceptually, this post office is not much different than a United States ,Postal Service office that processes letters and packages, except that the process is all computer-implemented and done electronically in a matter of seconds. The business rules are automatically applied to each incoming message, and the post office takes action on messages that trigger the business rules. Other messages are simply routed normally to their designated recipients.
(Id.) (emphasis added) IV has no convincing response to Defendants’ argument, nor does it supply any persuasive countervailing extrinsic evidence.
Thus, the Court concludes that the asserted claims of the ’142 patent are directed to an abstract idea of implementing well-known post office functionality using a computer. The Court will turn its attention to step 2.
Mayo Step 2
Symantec argues that “[t]he asserted claims of the ’142 patent do not clear the § 101 hurdle by including an ‘inventive concept’ that transforms them into something significantly more than the abstract concept itself.” (D.I. 699 at 12) “To the contrary,” Symantec continues, “the specification emphasizes that the asserted claims can be implemented on a conventional network, using conventional computers that run conventional operating systems and conventional e-mail clients.” (Id. at 12 (citing 142 patent at 3:25-26, 5:46-47, 5:49, 9:51-58)) Echoing these contentions, Trend Micro argues that “the asserted claims add no more than well-understood, conventional computer processing to practice the claimed abstract ideas in an automated setting.” (C.A. No. 12-1581 D.I. 176 at 22) IV responds by focusing on the fact that the 142 patent “does not preempt every application of filtering email” (D.I. 722 at 19) and asserting that the 142 patent’s limitations are quite detailed.
“A patent need not ... preempt an entire field to run afoul of § 101.” Gametek LLC v. Zynga, Inc.,
Applying these legal principles here, the Court agrees with Symantec and Trend Micro that the asserted claims of the T42 patent disproportionately tie up use of the patent’s underlying ideas. The fact that the ’142 patent does not preempt the entire field of email filtering does not render the claims per se patent eligible.
Alluding to DDR Holdings, IV argues that the specificity of the “ordered combination of elements ... overrides email’s conventional ‘unabated delivery’ paradigm.” (D.I. 722 at 19) But DDR Holdings is distinguishable at least because the claims at issue in that case were “necessarily rooted in computer technology ... to overcome a problem specifically arising in the realm of computer networks.”
TV cites DDR Holdings also to argue that the claims “do not merely recite the performance of some business practice known from the pre-Internet world along with a requirement to perform it on the Internet.” Id. at 1257. But the core problem addressed by the ’142 patent is the need to intercept and defer delivery of messages. This problem existed long before the Internet or the ’142 patent. “[T]he basic character of a process claim drawn to an abstract idea is not changed by claiming only its performance by computers .... ” CyberSource,
IV points to the “rule engine” in some of the asserted claims as evidence that the T42 patent cannot be implemented on a “conventional” computer. (D.I. 722 at 20-21) But the rule engine and all other components listed in the claims may be implemented purely in software and executed on any generic computer. (See, e.g., ’142 patent at 5:43-62, 6:51-55 (reciting “conventional” computer implementation)) Unlike with the sample PTO claims on which IV relies (see D.I. 723-2 at 2), the ’142 patent’s implementation is not “inextricably tied to computer technology and distinct from the types of concepts found by the courts to be abstract.” Nor does the ’142 patent’s implementation supply an inventive concept under part two of the Mayo test.
IV also argues that the claims satisfy the machine-or-transformation test. But IV does not, and cannot, point to any specific machine used to implement any of the asserted claims. The claims are drawn only to a generic computer implementation of an abstract idea. Thus, again, the Court concludes that the asserted claims of the T42 patent lack an inventive concept.
In light of the foregoing analysis, the Court finds that the asserted claims of the ’142 patent are ineligible under § 101.
Asserted claim 7 of the ’610 patent is a method claim that depends from claim 1. Independent claim 1 recites as follows:
A virus screening method comprising the steps of:
routing a call between a calling party and a called party of a telephone network;
receiving, within the telephone network, computer data from a first party selected from the group consisting of the calling party and the called party;
detecting, within the telephone network, a virus in the computer data; and
in response to detecting the virus, inhibiting communication of at least a portion of the computer data from the telephone network to a second party selected from the group consisting of the calling party and the called party.
Dependent claim 7 recites as follows:
The virus screening method of claim 1 further comprising the step of determining that virus screening is to be applied to the call based upon at least one of an identification code of the calling party and an identification code of the called party.
Mayo Step 1
Symantec and Trend Micro argue that the ’610 patent is directed to “screening data” and “screening information.” (D.I. 699 at 25; C.A. No. 12-1581 D.I. 176 at 24) Symantec states that the “key idea of the ’610 patent is the business concept of providing conventional virus screening as a subscription service to customers.” (D.I. 699 at 23) IV counters Defendants’ arguments by again alluding to. DDR Holdings, stating that Symantec and Trend Micro “cannot legitimately dispute that computer viruses are ‘a problem specifically arising in the realm of computer networks’ and computers.” (C.A. No. 12-1581 D.I. 183 at 19) IV insists, “The human mind cannot screen for computer viruses within the telephone network or elsewhere.” (Id. at 20) (emphasis added)
The Court agrees with IV. The ’610 patent is not directed to screening generic “data” or “information.” Instead, the asserted claim specifically recites a computer virus, which has computer-centric implications that cannot bé abstracted away so broadly. Furthermore, the human mind cannot perform the steps described in the specification for implementing virus screening functionality in a telephone network. For these and other reasons, as explained below, the Court is unpersuaded by Defendants’ analysis.
The specification of the ’610 patent describes how implementing claim 7 requires at least three computers configured in a specific manner, as depicted (for example) in the flowcharts (and accompanying text) shown as Figures 3, 4, and 5 (excerpted below). (’610 patent at 5:12-9:22)
Figure 3 is “an. embodiment of a virus screening method in accordance with the present invention.” (Id. at 5:12-13) Figure 3 shows that “computer data” is received from a “first party” (“calling” or “sending” party). The computer data is destined for a “second party” (“called,” “client,” or “receiving” party). It is inherent that this disclosure includes a computer for both the first and second parties. In block 102, the method of the patent determines whether or not virus screening should be applied to the computer data based on, for example, whether or not “the called party is a sub-
[[Image here]]
Figure 4 is a “preferred embodiment of a method of screening the computer data” that performs some initial processing of the data (i.e., removing transmission-specific data from the computer data, decompressing, and decrypting the data). {Id. at 6:15-17, Fig. 4) The method in Figure 4 then “create[s] a model of a computer,” as indicated in block 206. {Id. at Fig. 4) “The model is provided by a virus screening computer other than the client computer.” {Id. at 7:66-67) This virus screening computer is a third computer; it could not be the sending computer (since virus detection takes place “within the telephone network” but the sending computer is not within the telephone network. {Id. at 3:14-16; see also D.I. 425 at 24-25 (construing “within the telephone network” to mean “in the voice or data network connecting the calling party and called party, exclusive of the networks and gateway nodes of the called party and'calling party”)) ,
“An embodiment of a method of creating the model is described with reference to FIG. 5” (shown above). (Id. at 8:9-10) As shown in Figure 5, block 210 determines certain parameters of the receiving computer, including “operating system, a hardware type, registry information, configuration information, and information from initialization files,” in order to create an accurate model of the receiving computer in the virus screening computer’s memory. (Id. at 8:14-17) If the computer data includes “an executable program such as an installation program or a plug-in program for a Web browser, the executable program is installed” on the virus screening computer. (Id. at .8:5-7) During installation, “a step of intercepting read requests generated by the installation program is performed.” (Id. at 8:29-30) The virus screening computer analyzes the model computer in order to reply to these read requests appropriately. “The reply message is generated by gathering information from the model of the client computer! ] and passing the information to the installation program.” (Id. at 8:35-38) Similarly, the virus screening computer intercepts write requests from the executable program and modifies the model
The result of the steps described above is a model of the client computer stored in the virus screening computer’s memory. The model reflects the general state that the client computer would have been in had it executed the potentially virus-laden code. Virus screening techniques can then be applied to the model computer, as shown in block 220 in Figure 4, in order to determine whether the model computer has been infected.
Although the embodiment described in the specification with respect to Figures 3, 4, and 5 is not the only way to implement claim 7, it is necessary in practicing the claim to in some way imitate the receiving computer’s configuration in order to properly detect whether a harmful virus in an executable file may infect the receiving computer. The coordination between a virus detecting computer, a sending computer, and a receiving computer is something “necessarily rooted in computer technology in order to overcome a problem specifically arising in the realm of computer networks.” DDR Holdings,
Further, the specification confirms that the ’610 patent is directed to solving the problem of individual computer users having periodically to update their virus detection software locally on their computers in order to ensure adequate protection from computer viruses. (See ’610 patent at 1:10-23) The patent is also directed to. problems of users having to be concerned about viruses getting downloaded onto their computers via the Internet. As the specification of the ’610 patent describes:
Embodiments of the present invention advantageously screen computer data for viruses within a telephone network before communicating the computer data to an end user. As a result, end users can download computer data via the telephone network without concern of receiving various predetermined computer viruses.
(Id. at 1:59-67)
The Federal Circuit in DDR Holdings,
As with the other patents, Defendants provide hypothetical showing why they believe the asserted claim of the ’610 patent is patent-ineligible. Unlike with respect to the ’050 and ’142 patents, however, the analogies are not persuasive. Nonetheless, the Court reproduces them below:
(D.I. 699 at 25-26)
(C.A. No. 12-1581 D.I. 176 at 26-27)
Trend Micro further analogizes the asserted claims to the claims at issue in Vehicle Intelligence and Safety LLC v. Mercedes-Benz USA, LLC,
The Court finds all of Defendants’ hypo-theticals unpersuasive. The Court did not construe the phrase “detecting ... a virus in the computer data” from claim 7, as no party asked the Court to do so. {See D.I. 425) Nevertheless, it is evident from the specification that the steps for detecting a computer virus in a telephone network are not as straightforward as observing individuals for signs of intoxication, reading wartime correspondence, or asking someone if she is having an emergency. For example, the specification of the ’610 patent describes, in one embodiment, “installing downloaded data using the virus-screening processor” such that “viruses can be detected in installed data (which may differ from the downloaded data).” (’610 patent at 14:18-21) This is, of course, merely one possible implementation of claim 7 and does not limit the plain and ordinary meaning of the claim language, but it is also the type of functionality that is “necessarily rooted in computer technology in order to overcome a problem specifically arising in the realm of computer networks.” DDR Holdings,
For the reasons stated above, and particularly in light of DDR Holdings, Defendants have failed to prove that claim 7 is directed to an abstract idea.
Mayo Step 2
It is not necessary for the Court to consider step two of the Mayo test, since the asserted claim of the ’610 patent is not directed to an abstract idea. However, the Court notes that the specification of the ’610 patent recites a specific machine configured in a specific way to implement claim 7, as discussed above with regard to Figure 3, 4, and 5 of the ’610 patent and accompanying sections of the specification. Thus, the ’610 patent satisfies the machine-or-transformation test, which is an important clue that the claim includes an inventive concept and is not directed to patent-ineligible subject matter.
TV states that “virus detection ‘within the telephone network’ would not be preempted if a call were not routed between the calling party and the called party or if computer data were not received within the telephone network, as required by the claim language.” (C.A. No. 12-1581 D.I. 188 at 27) IV continues: “[T]he ’610 Patent captures only one form of virus detection, and its continued eligibility will not preclude the use of other virus detection techniques — even if they occur ‘within the telephone network.’ ” (Id.) The Court agrees with IV that the asserted claim of the ’610 patent does not disproportionately preempt virus detection.
Additionally, claim 7 recites “inhibiting communication of at least a portion of the computer data,” which indicates that the claim covers situations where the virus detecting computer is excising virus-infected code. This is similar to the PTO’s patent eligible sample claim directed to excising malignant software code, which the PTO described as “inextricably tied to computer technology and distinct from the types of concepts found by the courts to be abstract.” (See D.I. 723-2 at 2) Excising 'virus-infected code is something that requires a machine that “play[s] a significant part in permitting the claimed method to be performed, rather than functioning] solely as an obvious mechanism for permitting a solution to be achieved more quickly.” SiRF Tech.,
Hence, again, the Court concludes that Defendants have failed to prove by even a preponderance of the evidence that the asserted claim of the ’610 patent is patent-ineligible under § 101. The Court will deny Defendants’ motions with respect to IV’s ’610 patent.
CONCLUSION
For the reasons given above, the asserted claims of the ’050 and T42 patents are directed to patent-ineligible subject matter under 35 U.S.C. § 101. The Court will grant Symantec and Trend Micro’s motions to the extent that it will order that
Appropriate orders follow.
ORDER
At Wilmington this 22nd day of April, 2015:
For the reasons set forth in the Memorandum Opinion issued this same date,
IT IS HEREBY ORDERED that:
1. Defendant Symantec Corporation’s (“Symantec”) Motion for Patent Invalidity Under 35 U.S.C. § 101 of U.S. Patent Nos. 6,460,050 (the “’050 patent”), 6,073,142 (the “ ’142 patent”), and 5,987,610 (the “ ’610 patent”) (D.I.698) is GRANTED IN PART and DENIED IN PART, as follows:
a. Symantec’s motion under Rule 52(c) for patent invalidity of the ’050 and 142 patents due to lack of patentable subject matter is GRANTED.
b. Symantec’s motion under Rule 52(c) for patent invalidity of the ’610 patent due to lack of patentable subject matter is DENIED.
2. The parties shall meet and confer and submit a joint status report, including their proposal(s) for further proceedings and/or order(s), no later than April 27, 2015.
ORDER
At Wilmington this 22nd day of April, 2015:
For the reasons set forth in the Memorandum Opinion issued this same date,
IT IS HEREBY ORDERED that:
1. Trend Micro Incorporated and Trend Micro, Inc. (USA)’s (“Trend Micro”) Motion for Judgment of Invalidity Under 35 U.S.C. § 101 of U.S. Patent Nos. 6,460,-050 (the “'050 patent”), 6,073,142 (the “ 142 patent”), and 5,987,610 (the “ '610 patent”) (D.I. 175) is 'GRANTED IN PART and DENIED IN PART, as follows:
a. Trend Micro’s motion for summary judgment of patent invalidity of the '050 and 142 patents due to lack of patentable subject matter is GRANTED.
b. Trend Micro’s motion for summary judgment of patent invalidity of the '610 patent due to lack of patentable subject matter is DENIED.
2. In light of the fact that a pretrial conference is scheduled for Friday, April 24, and trial is scheduled to begin on May 11, the parties shall meet and confer and advise the Court, by joint letter, no later than Thursday, April 23 at 12:00 p.m., of their position(s) as to how this case should now proceed. Unless the parties jointly indicate in their letter that they believe it is unnecessary, the Court will hold a teleconference with the parties on April 23 beginning at 2:30 p.m. Plaintiffs shall arrange the call.
Notes
. Unless otherwise specified, all docket citations in the remainder of this Opinion are to the Symantec case.
. As used hereinafter in this Opinion, and unless otherwise stated, "asserted claims” refers to this list of claims that have been asserted by IV against Trend Micro, which also includes all of the claims asserted against Symantec.
. Symantec brings its motion under Federal Rule of Civil Procedure 52(c). In the alternative, Symantec requests judgment as a matter of law under Rule 50(b).
. Trend Micro did not state in its briefs the rule under which it was moving, but at the hearing said it did not oppose application of a summary judgment standard. (See Tr. at 20) IV does not object to application of this standard either. (See id. at 71) The Court agrees it is appropriate to apply the Rule 56 summary judgment standard to Trend Micro’s motion.
. The Supreme Court, in its opinion in Alice, referred to “invalidity” once — in describing the declaratory judgment plaintiffs request for relief in its complaint,
. As is obvious from the Court's resolution of the pending motions, the Court does not agree with IV’s contention.
. See "2014 Interim Guidance on Patent Subject Matter Eligibility (Interim Eligibility Guidance) for USPTO personnel to use when determining subject matter eligibility under 35 U.S.C. 101 in view of recent decisions by the U.S. Supreme Court, including Alice Corp., Myriad, and Mayo” (available at www. uspto.gov/patent/laws-and-regulations/ examination-policy (last visited April 13, 2015) at "Abstract Idea Examples,” part 1, example 1, claim 1 (and accompanying analysis); see also D.I. 723-2 at 1-3.
.See McRO, Inc. v. Bandai Namco Games Am., Inc., No. 15-1080 (Fed. Cir. Mar. 6, 2015), amicus brief of BSA I Tue Software Alliance (D.I. 723-1). Tue Court does not find IV’s references to the amicus brief to be persuasive.
. Helios is distinguishable for a number of reasons. The Court’s statement in Helios that "none of these limitations could be performed by a human alone” is not applicable to any of the asserted claims of the '050 (or T42) patents, which consist entirely of limitations that could be performed by humans or limitations directed to generic computer implementation. In addition, the patents at issue in Helios, unlike the ’050(or'142) patents, were "necessarily rooted in computer technology in order to overcome a problem specifically arising in the realm of computer networks.” DDR Holdings,
. For purposes of Trend Micro’s motion, the Court finds that there is no genuine issue of material fact as to the patent ineligibility of the asserted claims of the '050 patent.
. For purposes of Trend Micro’s motion, the Court finds that there is no genuine issue of material fact as to the patent ineligibility of the asserted claims of the ’142 patent.
. Defendants argue unpersuasively that the '610 patent is all and only about "where” virus detection is done — i.e., in the telephone network (see, e.g., Tr. at 51-54) — but this characterization fails to account for the fact that the asserted claim also contains limitations addressing the "what,” including the excision of virus-infected portions of computer data (see '610 patent at 11 :54-64) and the use of three computers. While it is correct that the asserted claim does not delineate the entirety of the "what” — for example, it is not limited to a specific type of virus detection — that fact does not alter the Court's conclusion that Defendants’ depiction of the asserted claim is inaccurately broad.
. In addition, the Court considered the extrinsic evidence, primarily inventor testimony (see D.I. 699 at 23-25), in confirming its conclusion that Defendants have failed to prove by even a preponderance of the evidence that claim 7 is patent ineligible. Basically, Defendants cite inventor testimony to support the persuasiveness of their "brick and mortar” analogies and to suggest that virus screening in general was well known. (See id.) However, the novelty — or lack thereof — of virus screening, before the priority date of the ’610 patent is not dispositive of the patent-eligibility of virus screening in a telephone network with the additional limitations of claim 7.
