Kaavo Inc. v. Amazon.com Inc.
This text of 323 F. Supp. 3d 630 (Kaavo Inc. v. Amazon.com Inc.) is published on Counsel Stack Legal Research, covering District Court, D. Delaware primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.
Opinion
STARK, U.S. District Judge
Pending before the Court are: (I) Defendants Amazon.com, Inc. and Amazon Web Services, Inc.'s (collectively, "Amazon" or "Defendants") motion for summary judgment of invalidity under
I. BACKGROUND
A. Procedural History
Plaintiff sued Defendants for infringement of United States Patent No. 8,271,974 (the "'974 patent"), which is entitled "Cloud Computing Lifecycle Management for N-tier Applications." In related cases, Magistrate Judge Burke issued a report and recommendation that the asserted independent claims, as well as dependent claim 12, be found patent ineligible under. § 101. (C.A. No. 14-1192 D.I. 35; C.A. No. 14-1193 D.I. 42) ("R & R") Over Plaintiffs objection (C.A. No. 14-1192 D.I. 39;
*634C.A. No. 14-1193 D.I. 46), the Court adopted the R & R in full (C.A. No. 14-1192 DJ. 44; C.A. No. 14-1193 D.I. 52). Later, Magistrate Judge Burke ordered limited discovery as well as claim construction and summary judgment briefing, with respect to the eligibility of the remaining dependent claims, and conducted a hearing on these issues. (See DJ. 116) Thereafter, the Court denied without prejudice Defendants' summary judgment motion and Plaintiffs request to re-file a Rule 60 motion for reconsideration of the Court's ruling on the independent claims, instead ordering new briefing to allow the parties-and the Court-to consider anew all § I 01 issues in light of the manifold decisions issued by the Federal Circuit with respect to patent eligibility since this Court's earlier opinion issued in March 2016. (See D.I. 118, 121)
The parties completed briefing (see D.I. 126, 132, 136) and submitted expert declarations (see D.I. 127, 133, 137). On March 12, 2018, the Court held a combined hearing on the motions and claim construction. (See D.I. 140 ("Tr.") )2
B. The Patent-in-Suit
The '974 patent generally relates to methods, devices, and systems [in] the fields of computers, information technology, virtualization, and cloud computing," and, more particularly, the "management of a cloud computing environment for use by a software application." '974 patent, col. 1 11. 6-11. The application may include software "(e.g., a web portal with email functionality, database programs, word processing programs, accounting programs, inventory management programs, numerical analysis programs)," or services "(e.g., an autonomous unit that is responsible for a transformation, storage and/or retrieval of data, such as a database management service or a database API service)."
The patent explains that "[ c]loud computing may be used to leverage virtualization of the resources of, for example, data centers."
The cloud computing environment "may be an N-tier environment."
The patent explains that "[e]ach individual cloud configuration may contribute all, *635a portion, or none of each individual tier of the. N-tier configuration of application cloud environment configuration."
II. LEGAL STANDARDS
A. Summary Judgment
Free access — add to your briefcase to read the full text and ask questions with AI
STARK, U.S. District Judge
Pending before the Court are: (I) Defendants Amazon.com, Inc. and Amazon Web Services, Inc.'s (collectively, "Amazon" or "Defendants") motion for summary judgment of invalidity under
I. BACKGROUND
A. Procedural History
Plaintiff sued Defendants for infringement of United States Patent No. 8,271,974 (the "'974 patent"), which is entitled "Cloud Computing Lifecycle Management for N-tier Applications." In related cases, Magistrate Judge Burke issued a report and recommendation that the asserted independent claims, as well as dependent claim 12, be found patent ineligible under. § 101. (C.A. No. 14-1192 D.I. 35; C.A. No. 14-1193 D.I. 42) ("R & R") Over Plaintiffs objection (C.A. No. 14-1192 D.I. 39;
*634C.A. No. 14-1193 D.I. 46), the Court adopted the R & R in full (C.A. No. 14-1192 DJ. 44; C.A. No. 14-1193 D.I. 52). Later, Magistrate Judge Burke ordered limited discovery as well as claim construction and summary judgment briefing, with respect to the eligibility of the remaining dependent claims, and conducted a hearing on these issues. (See DJ. 116) Thereafter, the Court denied without prejudice Defendants' summary judgment motion and Plaintiffs request to re-file a Rule 60 motion for reconsideration of the Court's ruling on the independent claims, instead ordering new briefing to allow the parties-and the Court-to consider anew all § I 01 issues in light of the manifold decisions issued by the Federal Circuit with respect to patent eligibility since this Court's earlier opinion issued in March 2016. (See D.I. 118, 121)
The parties completed briefing (see D.I. 126, 132, 136) and submitted expert declarations (see D.I. 127, 133, 137). On March 12, 2018, the Court held a combined hearing on the motions and claim construction. (See D.I. 140 ("Tr.") )2
B. The Patent-in-Suit
The '974 patent generally relates to methods, devices, and systems [in] the fields of computers, information technology, virtualization, and cloud computing," and, more particularly, the "management of a cloud computing environment for use by a software application." '974 patent, col. 1 11. 6-11. The application may include software "(e.g., a web portal with email functionality, database programs, word processing programs, accounting programs, inventory management programs, numerical analysis programs)," or services "(e.g., an autonomous unit that is responsible for a transformation, storage and/or retrieval of data, such as a database management service or a database API service)."
The patent explains that "[ c]loud computing may be used to leverage virtualization of the resources of, for example, data centers."
The cloud computing environment "may be an N-tier environment."
The patent explains that "[e]ach individual cloud configuration may contribute all, *635a portion, or none of each individual tier of the. N-tier configuration of application cloud environment configuration."
II. LEGAL STANDARDS
A. Summary Judgment
Under Rule 56(a) of the Federal Rules of Civil Procedure, "[t)he court shall grant summary judgment if the movant shows that there is no genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law." The moving party bears the burden of demonstrating the absence of a genuine issue of material fact. See Matsushita Elec. Indus. Co., Ltd. v. Zenith Radio Corp. ,
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." Matsushita,
*636in support of the nonmoving party's position is insufficient to defeat a motion for summary judgment; there must be "evidence on which the jury could reasonably find" for the nonmoving party. Anderson,
B. Section 101 : Patentable Subject Matter
Under
In Mayo Collaborative Services v. Prometheus Laboratories, Inc. ,
At step one, "the claims are considered in their entirety to ascertain whether their character as a whole is directed to excluded subject matter." Internet Patents Corp. v. Active Network, Inc. ,
Courts should not "oversimplif[y]" key inventive concepts or "downplay" an invention's benefits in conducting a step one analysis. See Enfish, LLC v. Microsoft Corp. ,
At step two, courts must "look to both the claim as a whole and the individual claim elements to determine whether the claims contain an element or combination of elements that is sufficient to ensure that the patent in practice amounts to significantly more than a patent upon the ineligible concept itself"
However, "[t]he inventive concept inquiry requires more than recognizing that each claim element, by itself, was known in the art." Bascom,
The Federal Circuit recently elaborated on the step two standard, stating that "[t]he question of whether a claim element or combination of elements is well-understood, routine and conventional to a skilled artisan in the relevant field is a question of fact. Any fact, such as this one, that is pertinent to the invalidity conclusion must be proven by clear and convincing evidence." Berkheimer,
III. DISCUSSION
A. Reconsideration of March 31, 2016 Order Regarding Ineligibility of Claims 1, 12, 13, 24, and 35
Plaintiff moves for reconsideration of the Court's Order invalidating all of the asserted independent claims-1, 13, 24, and 35-and claim 12, a dependent claim. (C.A. No. 14-1193 D.I. 52) Plaintiffs motion arises under Federal Rule of Civil Procedure 60(b)(6), which permits relief from an order for "any other reason that justifies relief."3 The Third Circuit has *638noted that "courts are to dispense their broad powers under 60(b)(6) only in 'extraordinary circumstances where, without such relief, an extreme and unexpected hardship would occur.' " Cox v. Horn,
Plaintiff argues that the Federal Circuit's decisions in " Enfish, McRO , Bascom , Visual Memory , Core Wireless and Berkheimer, and Aatrix " -all of which were decided after the Court's Order- "were previously unavailable" when the Court issued its 2016 Order. (D.I. 132 at 16) Had the Court followed those decisions, Plaintiff argues, "it is evident that the asserted claims of the '974 patent are directed to an improvement of the functioning of computers and improve an existing technology, and thus are not abstract." (Id.)
Plaintiff has failed to show the kind of extraordinary circumstance required for relief under Rule 60(b)(6). None of the Federal Circuit cases cited by Plaintiff constitutes a change in the law pertaining to § 101. Instead, these cases provide further guidance on applying the Supreme Court's two-step § 101 analysis to different factual scenarios. See Cloud Satchel LLC v. Amazon.com, Inc. ,
Reconsideration is also not warranted because even retroactive application of all of Plaintiffs' new cases would not alter the Court's conclusion that the claims considered in the Order are not directed to patent eligible subject matter. Contrary to *639Plaintiffs assertion (see D.I. 132 at 16-17), the asserted claims here are different from those held to be patent eligible in Enfish, Visual Memory, and Core Wireless .
In Enfish,
In Visual Memory LLC v. NVIDIA Corp. ,
In Core Wireless Licensing S.A.R.L. v. LG Elecs., Inc. ,
Unlike the claims disclosing the self-referential table in Enfish, the computer memory system in Visual Memory , and the user interface in Core Wireless, the claims at issue here-disclosing the cloud computing environment-are not "directed to a particular improvement in the computer's functionality."
Plaintiff points to the claim language reciting that the "initial cloud environment is not yet instantiated and is an N-tier *640computing environment" for use by a software application and that "an adjusted cloud environment configuration [is] to be made available to the application."5 (D.I. 132 at 18) However, the different claim limitations are merely a generalized description of cloud computing that the Court previously found to relate. to the abstract idea of "setting up the cloud computing environment." (D.I. 52 at 5)
In sum, Plaintiff has not demonstrated that the Court should exercise its discretion to provide relief under Rule 60(b)(6).
B. The Asserted Dependent Claims Are Not Patent Eligible Under Section 101
The Court previously concluded that all of the asserted independent claims and one asserted dependent claim are directed to the abstract idea of setting up and managing a cloud computing environment and contain no inventive concept and, thus, are not patent eligible. (D.I. 52 at 4, 6) Defendants now move for summary judgment that the remaining asserted dependent claims-claims 5-6, 8-9, 11, 17-18, 20-21, 23, 28-29, 31-32, and 34-all of which depend from the invalidated independent claims, are similarly not eligible for patent protection under § 101. (DJ. 126 at 3) Plaintiff responds that the dependent claims, "when considered as a whole, as they must be, are directed to an improvement in cloud-computing and not an abstract idea." (D.I. 132 at 4)
The asserted representative dependent claims (5-6, 8-9, and 11) depend from independent claim 1.6 Claim 1 recites:
A method for managing a cloud computing environment for use by a software application comprising:
determining a requested initial cloud environment based on user-defined provisioning information, where the requested initial cloud environment is not yet instantiated and is an N-tier computing environment;
sending an initialization event based on the requested initial cloud environment, where the initialization event is configured to cause an initial cloud environment configuration to be made available to an application;
sending application data that is configured to cause the application to begin execution in the initial cloud environment configuration;
receiving monitoring environment data that represents a current cloud environment state;
detennining a requested adjusted cloud environment based on the monitoring environment data, where the requested adjusted cloud environment is an N-tier computing environment; and
sending a cloud environment adjustment event based on the requested adjusted cloud environment, where the cloud environment adjustment event is configured to cause an adjusted cloud environment configuration to be made available to the application.
*641Dependent claims 5, 6, 8, 9, and 11 include additional limitations, as follows:
• forecasting an optimal cloud environment for future use with the application based on monitoring environment data (claim 5)
• forecasting a future cost associated with executing the application based on monitoring environment data (claim 6)
• the user-defined provisioning information is determined using a needs analysis algorithm and a user input received from a user interface (claim 8)
• the user-defined provisioning information comprises geographic data (claim 9)
• receiving security information, determining a requested security action based on the security information, and sending a security event based on the requested security action (claim 11)
The Court now turns to the Alice / Mayo two-step analysis of these dependent claims.7
1. Step One
Under step one, the Court inquires "whether the claims at issue are directed to one of those patent-ineligible concepts," such as an abstract idea. Alice,
Defendants argue that "[l]ike the independent claims, the asserted dependent claims are directed to the abstract idea of setting up and managing a cloud computing environment." (D.I. 126 at 15) Plaintiff counters that "Defendants oversimplify the language of the dependent claims and completely ignore the limitations of the parent claims." (D.I. 132 at 23-24) In Plaintiffs view, the claims "focus on improving the use of the computers as a tool to execute a software application." (Id.)
The "basic character" or "focus" of dependent claims 5-6, 8-9, and 11 amounts to nothing more than the abstract idea encompassed by independent claim 1 from which they all depend, namely, setting up and managing a cloud computing environment. The dependent claims add no meaningful limitations beyond this abstract idea. Instead, they broadly recite "functional results" for the claimed cloud computing environment, "but [do] not sufficiently describe how to achieve these results in a non-abstract way." Two-Way Media,
Claims 5 and 6, for instance, are drawn to methods of "forecasting." '974 patent, col. 19 IL 49-56. The specification explains that the forecasting "may be performed using techniques such as, for example, neural networks, time-series algorithms, and regression analysis."
Claims 8 and 9 recite methods for determining "user-defined provisioning information" using user input, a needs analysis algorithm,8 and geographic data.
Claim 11 is drawn to a method of receiving "security information," determining a *643"security action" based on the security information, and sending a "security event" based on the security action.
Contrary to Plaintiffs contentions, the dependent claims are not directed to an "improvement to computer functionality." Enfish,
Plaintiff, relying on expert testimony, argues that the dependent claims are not abstract because the corresponding independent claim is not abstract. (See D.I. 132 at 25) (relying on its expert and explaining that dependent claims are "directed to improving 'the reliability and optimization of the cloud environment in which the application runs'-a context required by parent claim 1") (emphasis added) But the Court has already concluded that the asserted independent claims are directed to an abstract idea: this was the Court's decision in the March 31, 2016 Order (C.A. No. 14-1192 D.I. 44; C.A. No. 14-1193 D.I. 52), and the Court has today denied reconsideration of that Order. Plaintiff does not point to any intrinsic evidence to show that any of the dependent claims, taken as a whole, teaches methods that are not abstract or that actually improve the functioning of computers. (See generally D.I. 132 at 22-26) Thus, Plaintiffs reliance on contrary expert opinion alone is insufficient to create a genuine issue of material *644fact. See Mortg. Grader, Inc. v. First Choice Loan Servs. Inc. ,
In sum, Defendants have met their burden at step one.
2. Step Two
At step two, the Court examines the claim limitations "more microscopically," Elec. Power Grp. ,
Defendants argue that the asserted dependent claims lack an inventive concept. (D.I. 126 at 19) Plaintiff responds that "the parties' arguments and dueling expert testimony clearly point to 'at least a genuine issue of material fact' whether the asserted dependent claims overcome the challenges of running an application in a cloud environment in an inventive manner." (D.I. 132 at 26) (citing Berkheimer,
Plaintiff does not point to any intrinsic evidence to support its position. Nothing in the claim language with respect to the dependent claims indicates anything inventive about the methods of the cloud computing environment or how those methods accomplish anything inventive. In particular, to the extent Plaintiff is claiming that what is inventive is the "user-centric" approach, the Court is persuaded by Defendants that no claim language incorporates or requires the "user-centric" approach. (See Tr. at 69)
For instance, Claims 5 and 6 do not specify how the forecasting is performed, what monitoring data is used, or how it is used; any generic algorithm, neural network, or regression analysis could be used. Claim 8 does not limit the method to any specific algorithm or user interface; any generic algorithm or user interface could be used. Claim 9 does not teach how the geographic data is created or determined, or what type of data is required; any generic method or data could be used. Claim 11 does not limit how the security information is collected, how the security action is determined, or how the security event is used; any generic method could be used. Plaintiff has not cited to any portion of the specification that fills any of these gaps.
Although Plaintiff tries to rely on expert testimony, here this is insufficient to create a genuine issue of material fact. See Mortg. Grader,
Thus, the Court finds that the dependent claims, each viewed individually and as an ordered combination, lack an inventive concept. See *645Secured Mail Sols. LLC v. Universal Wilde, Inc. ,
In sum, because the claims are directed to an abstract idea and nothing in the claims add an inventive concept, the claims are not patent eligible under § 101.11
IV. CONCLUSION
The asserted claims of the '974 patent are not patent eligible under § 101. Hence, the Court will grant Defendants' renewed motion for summary judgment and will deny Plaintiff's renewed motion to reconsider the Court's previous Order invalidating certain asserted claims.12 An appropriate Order follows.
ORDER
At Wilmington, this 18th day of June, 2018:
For the reasons set forth in the Memorandum Opinion issued this date,
IT IS HEREBY ORDERED that:
1. Defendants' Renewed Motion for Summary Judgment of Infringement Under 35 U.S.C § 101 (D.I. 124) is GRANTED.
2. Plaintiffs Motion for Reconsideration of Plaintiff s Renewed Motion for the Court to Reconsider the March 31, 2016 Order in Light of Subsequently-Issued Authority (D.I. 131) is DENIED.
*646IT IS FURTHER ORDERED that the parties shall meet and confer and, no later than June 22, 2018, submit a joint status report providing the Court with their position(s) as to how this case should now proceed.
Related
Cite This Page — Counsel Stack
323 F. Supp. 3d 630, Counsel Stack Legal Research, https://law.counselstack.com/opinion/kaavo-inc-v-amazoncom-inc-ded-2018.