1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 Swarm Technology LLC, No. CV-21-00438-PHX-DWL
10 Plaintiff, ORDER
11 v.
12 Amazon.com Incorporated, et al.,
13 Defendants. 14 15 Swarm Technology, LLC (“Plaintiff”) holds certain patents related to the design of 16 multiprocessor systems. In this action, Plaintiff accuses Amazon Web Services, Inc. and 17 Amazon.com, Inc. (collectively, “Defendants”) of infringing those patents in violation of 18 35 U.S.C. § 271. 19 Defendants previously moved to dismiss the complaint, arguing that Plaintiff’s 20 patents are ineligible under 35 U.S.C. § 101 because they are directed to an abstract idea— 21 computerizing the well-known project management technique known as a “scrum 22 board”—and do not contain any inventive concepts. (Doc. 29.) In September 2021, the 23 judge previously assigned to the case granted Defendants’ motion. (Doc. 64.) However, 24 the Court also held that “[i]f [Plaintiff] believes it may amend its pleadings to state a viable 25 claim, then it may file a motion for leave to file a first amended complaint to explain how 26 it could address the deficiencies identified in this Order.” (Id. at 9.) 27 Plaintiff took advantage of this opportunity and filed a motion for leave to file a 28 First Amended Complaint (“FAC”) (Doc. 66), along with a proposed FAC (Doc. 66-13). 1 The proposed FAC differs from the original complaint in three notable respects: first, it 2 contains an array of new allegations intended to establish that the patents at issue are 3 eligible under § 101 (Doc. 66-1 at 30-60); second, it is ostensibly supported by detailed 4 declarations from two experts, Dr. Brent Nelson of Brigham Young University (Doc. 66- 5 14) and Dr. Douglas Sylvester of the Sandra Day O’Connor College of Law at Arizona 6 State University (Doc. 66-15); and third, whereas the original complaint accused 7 Defendants of infringing two patents—U.S. Patent No. 9,852,004 (“the ’004 Patent”) and 8 No. 10,592,275 (“the ’275 Patent”)—held by Plaintiff, the FAC adds allegations regarding 9 a third patent, U.S. Patent No. 9,146,777 (“the ’777 Patent”). 10 After Plaintiff’s motion to amend became fully briefed (Docs. 68, 69), the 11 previously assigned judge recused (Doc. 76). The Court has now had an opportunity to 12 review the entire docket in this matter, as well as the parties’ many filings concerning 13 developments in related administrative proceedings (Docs. 81, 84, 86-92) and a recent 14 decision in which a different court rejected the sufficiency of Plaintiff’s allegations 15 regarding patent eligibility under § 101. Juniper Networks Inc. v. Swarm Tech., 2022 WL 16 3031211 (N.D. Cal. 2022). As explained below, although the issue presents a close call, 17 the Court concludes that the proposed FAC contains sufficient factual allegations to survive 18 dismissal under § 101 at the Rule 12(b)(6) stage. Accordingly, Plaintiff’s motion for leave 19 to amend is granted. 20 DISCUSSION 21 I. The September 2021 Dismissal Order And Juniper 22 Before addressing the parties’ current arguments, it is helpful to begin by 23 summarizing the September 2021 dismissal order and the recent Juniper decision, because 24 both help frame the dispute now before the Court. 25 The September 2021 order begins by discussing the nature of the two patents then 26 at issue, the ’004 Patent and the ’275 Patent. (Doc. 64 at 1-2.) It explains that they 27 “purport[] to cover a ‘processing architecture’ whereby ‘autonomous co-processors . . . 28 proactively retrieve tasks from a task pool populated by a central processing unit.’” (Id.) 1 Next, the September 2021 order identifies the relevant test for evaluating these patents’ 2 eligibility under § 101. (Id. at 3.) It explains that, under Alice Corp. Pty. Ltd. v. CLS Bank 3 Int’l, 573 U.S. 208 (2014), the “two-step analysis” consists of (1) assessing whether the 4 claims at issue are directed to a patent-ineligible concept, such as an abstract idea; and (2) 5 if so, assessing whether the elements of the claims nevertheless “contain an inventive 6 concept . . . that is sufficient to ensure that the patent in practice amounts to significantly 7 more than a patent upon the ineligible concept itself.” (Id., cleaned up.) 8 As for the first step, the September 2021 order explains that the dispute turns on 9 whether the patents may be characterized as “abstract because [they] simply computerize[] 10 a well-known project management technique known as a ‘scrum board,’” which “works by 11 first having a project manager list tasks on sticky notes and post them on one side of a 12 board. As the team members collect and perform each task, they individually move the 13 notes from the ‘incomplete’ side of the board to the other side, the ‘complete’ side of the 14 board.” (Id. at 4-5.) Although Plaintiff argued that “the scrum board comparison is a 15 mischaracterization of its Patents” because they “provide[] a ‘multiprocessor system with 16 the speed of parallel processing’ without traditional downsides,” the Court disagreed, 17 concluding that the “Patents are directed towards the abstract idea of a scrum board. 18 Although the Patents are aimed at allocating computer processing power in an efficient 19 way, scrum boards also allocate human resources in an efficient way. The Patents therefore 20 are not aimed at a ‘specific implementation of a solution’ as much as they consist of 21 ‘generalized steps to be performed on a computer using conventional computer activity.’ 22 The idea of a scrum board does not become non-abstract when limited to the computer 23 environment. Although there is no doubt that computers could perform tasks organized by 24 a scrum board more efficiently than humans, the idea itself remains abstract.” (Id. at 5-6.) 25 As for the second step, Plaintiff argued the inventive-concept requirement should 26 be deemed satisfied for three reasons: (1) it had overcome previous objections to its patents 27 under 35 U.S.C. §§ 102-03; (2) “the Patents ushered in a ‘new parallel processing 28 paradigm’ that dramatically increases computer performance”; and (3) “whether its Patents 1 represent something that genuinely improves computer performance is a question of fact, 2 which would preclude a finding that the Patents are ineligible on a motion to dismiss.” (Id. 3 at 7-8.) The Court disagreed. As for Plaintiff’s first argument, the Court identified 4 “caselaw show[ing] that whether a patent is novel or nonobvious [under §§ 102/103] is 5 irrelevant to the Alice analysis.” (Id. at 7.) As for Plaintiff’s second argument, the Court 6 held that “it is not enough that [Plaintiff] claim its Patents are novel. The Court has already 7 found that the Patents are abstract in that they describe a computerized scrum board, and 8 simply applying an abstract idea to computers, standing alone, cannot be an innovative 9 concept.” (Id.) As for Plaintiff’s third argument, the Court held that although “the 10 Complaint alleged that the Patents are designed to address two problems related to parallel 11 computer processing”—namely, “too much processing bandwidth was being occupied in 12 assigning tasks to ‘slave’ processors” and “many processors were being left idle while 13 awaiting a task”—these allegations did not appear in the patents themselves. (Id. at 7-8.) 14 The Court further held that “[a]lthough [Plaintiff] makes the conclusory assertion that its 15 Patents contain claim elements that, when combined, ‘are not well-understood, routine or 16 conventional,’ [Plaintiff] fails to elaborate.” (Id. at 8.) The Court continued: “The Court 17 doubts that [Plaintiff] could point to a specific inventive concept. It is plain from the 18 specification of the ’004 Patent that it requires ‘no improved computer resources . . . , just 19 already available computers, with their already available basic functions, to use as tools in 20 executing the claimed process.’ For example, the specification contemplates a person 21 playing video games on their laptop and tapping into the processing power on a nearby 22 smartphone, ‘thereby enhancing the video game experience.’ This appears to be directed 23 towards ‘generic components,’ such as laptops and smartphones, ‘performing conventional 24 activities,’ such as playing video games. [Plaintiff] may argue that the allocation of 25 processing power between the laptop and smartphone is the specific inventive concept, but 26 this allocation is based solely upon the abstract idea of a scrum board.” (Id. at 8-9.) Thus, 27 the Court concluded that “[w]ithout specific and concrete allegations of specific 28 improvements to computer technology, all [Plaintiff] has alleged is an improvement to the 1 speed and efficiency of computer systems stemming from the implementation of an 2 abstract idea. The improved efficiencies from the application of an abstract idea are not an 3 inventive concept.” (Id. at 9.) 4 Meanwhile, Juniper is an action in the Northern District of California in which the 5 plaintiff (Juniper Networks, Inc.) seeks a declaration that its patents do not infringe the 6 ’004 Patent, the ’275 Patent, or the ’777 Patent. 2022 WL 3031211 at *1. In response, 7 Plaintiff asserted counterclaims of infringement, which Juniper then moved to dismiss “on 8 the grounds that all claims of the ’777 patent, ’004 patent, and ’275 patent are directed to 9 patent-ineligible subject matter under 35 U.S.C. § 101.” Id. In an order filed on August 1, 10 2022, the district court granted Juniper’s motion to dismiss. Id. 11 Notably, the court did not address the sufficiency of Plaintiff’s claims regarding the 12 ’004 and’275 Patents. Id. Instead, the court held that because this Court had already 13 determined those patents to be invalid under § 101 in the September 2021 order, and 14 Plaintiff had in turn filed a motion to amend, it did not make sense to relitigate the § 101 15 eligibility analysis regarding the ’004 Patent or the ’275 Patent while the motion to amend 16 remained pending. Id. Thus, the court dismissed the counterclaims regarding the ’004 17 Patent and the ’275 Patent “without prejudice . . . as developments in the District of Arizona 18 or on appeal warrant.” Id. at *1-2. 19 As for Plaintiff’s counterclaim regarding the ’777 Patent, the court began by 20 addressing (as this Court did in the September 2021 order) whether, under the first step of 21 the Alice framework, the claims should be considered directed toward an abstract idea 22 because they were analogous to a scrum board. Id. at *5-6. Plaintiff argued that “the ’777 23 patent is not directed to an abstract idea because it is directed to an improvement in how 24 computers operate and computer efficiency” and “teaches a way to reconfigure computer 25 systems to function more efficiently,” but the court disagreed, emphasizing that Plaintiff 26 “does not point to a specific improvement to computer technology identified in the ’777 27 patent” and that “to the extent that [Plaintiff] points to the ‘monolithic integrated circuit’ 28 as an element that is non-abstract, that element is limited to the ’004 and ’275 patents and 1 is not present in any claims of the ’777 patent.” Id. at *6. 2 As for the second step of the Alice framework, Plaintiff sought to establish that “its 3 claim represents an inventive concept” by “listing out seven elements that [Plaintiff] 4 believes were not well-understood, routine, or conventional,” but the court determined 5 these arguments were conclusory because Plaintiff’s “brief is entirely devoid of any 6 explanation for how these seven elements were not well-understood, routine, or 7 conventional. . . . That is precisely where [Plaintiff] dropped the ball. It did not plausibly 8 allege, based on non-conclusory and factual statements, that the ’777 patent embodies an 9 inventive concept. The conclusory allegations in the counterclaims will not do.” Id. at *6- 10 7. The court concluded by expressing “some doubt that [Plaintiff] can amend around this 11 problem” but still granted leave to amend. Id. at *7. 12 II. Legal Standard 13 Plaintiff’s amendment request is governed by Rule 15(a) of the Federal Rules of 14 Civil Procedure, which “advises the court that ‘leave [to amend] shall be freely given when 15 justice so requires.’” Eminence Cap., LLC v. Aspeon, Inc., 316 F.3d 1048, 1051 (9th Cir. 16 2003). “This policy is ‘to be applied with extreme liberality.’” Id. (citation omitted). Thus, 17 Plaintiff’s amendment request should be granted unless “the amendment: (1) prejudices the 18 opposing party; (2) is sought in bad faith; (3) produces an undue delay in litigation; or (4) 19 is futile.” AmerisourceBergen Corp. v. Dialysist W., Inc., 465 F.3d 946, 951 (9th Cir. 20 2006). 21 Here, the sole ground on which Defendants oppose the amendment request is 22 futility. (Doc. 68 at 1.) “An amended complaint is futile where it would be subject to 23 dismissal under Rule 12(b)(6).” Reed v. Nevada, 2021 WL 3722879, *2 (D. Nev. 2021) 24 (quoting Steckman v. Hart Brewing, Inc., 143 F.3d 1293, 1298 (9th Cir. 1998)); see also 25 Moore v. Kayport Package Exp., Inc., 885 F.2d 531, 538 (9th Cir. 1989) (“Leave to amend 26 need not be given if a complaint, as amended, is subject to dismissal.”). Thus, to determine 27 whether amendment is futile, the Court must consider whether the proposed FAC could 28 survive a § 101 eligibility analysis under Rule 12(b)(6). 1 III. The Parties’ Arguments 2 Plaintiff argues its amendment request should be granted because its proposed FAC 3 “contains specific and concrete allegations” sufficient to establish patentability under both 4 steps of the Alice framework. (Doc. 66.) As for the first step, Plaintiff argues that its 5 “invention is not directed at organizing human behavior, and is legally non-abstract” 6 because it “invented a new computer processing architecture that reconfigures the elements 7 of a computer’s processing system and introduces new code to operate those elements. In 8 combination, these elements provide an improvement to the functionality of the computer 9 itself. [Plaintiff’s] new architecture revolutionizes the interaction of computer components 10 and addresses technology issues that only arise in a computer context. Simply put, 11 [Plaintiff’s] new architecture provides a new way for computer parts (e.g., a processing 12 system) to interact with each other by modifying existing parts (controller and co- 13 processors) and interposing a new intermediary part (task pool) to manage communication 14 among all the parts.” (Id. at 1-2.) Plaintiff contends that, under Enfish, LLC v. Microsoft 15 Corp., 822 F.3d 1327 (Fed. Cir. 2016), improvements to “computer functionality” are 16 necessarily non-abstract and the ’004 Patent qualifies as such an improvement because it 17 “recite[s] improvements to computer functionality, including by using co-processors that 18 act autonomously and proactively to retrieve, process, and complete tasks without 19 communication between the co-processors and the [Central Processing Unit (‘CPU’)]. In 20 contrast, conventional coprocessors wait idly for instructions from a CPU.” (Id. at 11-16.) 21 Plaintiff further notes that, in Enfish, the Federal Circuit stated that an improvement to 22 “chip architecture” would qualify as a non-abstract improvement and contends that the 23 improvements described in its patents qualify as chip architecture improvements because, 24 as discussed in the Nelson declaration, computer and multiprocessor architectures can be 25 described as “the structure, organization, and behavior of functional components within a 26 computer processing system.” (Id. at 12, 16-17.) As for the second step, Plaintiff 27 specifically identifies the following five inventive concepts that are alleged in the FAC: (1) 28 “a controller configured to populate a task pool with a plurality of first tasks and a plurality 1 of second tasks” (’004 Patent); (2) “a first co-processor configured to . . . retrieve a first 2 task from the task pool . . . without any communication between the first co-processor and 3 the controller; and a second co-processor configured to . . . retrieve a second task from the 4 task pool . . . without any communication between the second co-processor and the 5 controller” (’004 Patent); (3) “a task pool” interposed between “a controller” and “co- 6 processors” (’275 Patent); (4) “configured to dynamically accept the first co-processor, the 7 second co-processor, and an additional co-processor” on a “plug-and-play basis without 8 any communication with the controller” (’275 Patent); and (5) “the first solidarity cell 9 comprising a first agent configured to proactively retrieve, from the task pool, without 10 requiring an instruction from the CPU, a matching task for the solidarity cell to process” 11 (’777 Patent). (Id. at 7-11.) Plaintiff further notes that, with respect to each claimed 12 inventive concept, the Nelson declaration establishes that the feature was not well- 13 understood, routine, or conventional in the field or industry. (Id.) 14 Defendants respond that amendment would be futile. (Doc. 68.) According to 15 Defendants, “although the FAC inserted an additional 30 pages and a third patent (the ’777 16 patent) that is materially the same as the other two, it nowhere identifies an inventive 17 concept apart from the abstract scrum board idea.” (Id. at 5.) Defendants contend that 18 “parallel processing using multiple co-processors is nothing new” and “the patents’ only 19 purported improvement is to collect the necessary tasks in a ‘task pool,’ and then the co- 20 processors autonomously retrieve and complete the tasks,” but all the claims remain 21 directed to the abstract idea of a scrum board. (Id. at 2, 8, 14.) Defendants also contend 22 that the purported benefit of greater efficiency simply flows from implementing the 23 abstract idea itself, and therefore does not make the claims any less abstract. (Id. at 13.) 24 Defendants also argue that the claim specifications admit that the invention does not require 25 any improved computer technology or any particular implementation. (Id. at 2-3.) 26 Additionally, Defendants contend that the claims themselves say nothing about a “chip 27 architecture,” making it an “unclaimed detail,” and Plaintiff “cannot rely on such 28 unclaimed details to supply the patent-eligible content.” (Id. at 10-11.) As for the 1 declarations, Defendants argue they are improper and irrelevant—“[e]xtrinsic evidence 2 cannot change or supplement the absence of patent-eligible subject matter in the patents 3 themselves”—and, in any event, they identify nothing inventive apart from the abstract 4 idea. (Id. at 17.) Finally, Defendants note that Claim 1 of the ’004 Patent remains 5 representative for purposes of § 101 eligibility because Plaintiff does not argue there are 6 any meaningful differences between the claims (and, thus, the Court needn’t analyze each 7 claim separately). (Id. at 4 & n.5, 8.) 8 In reply, Plaintiff argues that, even assuming “interposing a task pool between a 9 CPU and co-processors amounts to an abstract idea because the task pool is tantamount to 10 a scrum board . . . , that abstract idea is only the beginning; Swarm’s claims add 11 ‘significantly more’ to the ‘abstract idea.’” (Doc. 69 at 1-2.) In support, Plaintiff provides 12 a few “non-limiting” examples, including a “plug-and-play” concept (which “allows an 13 unlimited number of computational tasks to be performed by an unlimited number of task 14 performers (co-processors) while communicating only with the task pool”) and a “retrieval 15 scheme” concept (which enables co-processors to “retrieve tasks from the task pool without 16 requiring instructions from the CPU” and allows “one CPU to manage an unlimited number 17 of task managers (networks) that interact with an unlimited number of task performers (co- 18 processors)”). (Id. at 2.) Plaintiff contends these concepts “had never been done before” 19 and provide technical solutions to interoperability problems in networks and computers by 20 “unlocking unlimited scalability” and “allowing simultaneous management of multiple 21 networks,” respectively. (Id. at 2, 4-5.) Plaintiff also argues that, “[a]t this juncture, [it] is 22 not required to prove that its inventive concepts are unconventional. Rather, [its] FAC 23 need only properly allege that the claims recite more than ‘well-understood, routine’ 24 activities,” which it does. (Id. at 7.) As for the use of off-the-shelf, conventional computer 25 technology, Plaintiff reiterates that Defendants are mistaken—Plaintiff’s invention 26 requires the computers to be “first modified by changing their operating software to 27 implement [the] new architecture.” (Id. at 8.) Finally, Plaintiff argues that Claim 1 of the 28 ’004 Patent is not representative of Claim 1 of the ’777 Patent (because that patent contains 1 additional elements not found in the ’004 Patent), nor is it representative of any of the other 2 claims (as Claims 2-12 of the ’004 Patent, Claims 2-17 of the ’275 Patent, and Claims 1- 3 14 of the ’777 Patent were first asserted in the FAC, and involve separate, non-abstract 4 limitations). (Id. at 8-9.) 5 IV. Analysis 6 A. Section 101 Eligibility 7 Under 35 U.S.C. § 101, “[w]hoever invents or discovers any new and useful process, 8 machine, manufacture, or composition of matter, or any new and useful improvement 9 thereof, may obtain a patent therefor, subject to the conditions and requirements of this 10 title.” However, the Supreme Court has “long held that this provision contains an 11 important implicit exception: Laws of nature, natural phenomena, and abstract ideas are 12 not patentable.” Alice, 573 U.S. at 216 (citation omitted). “[W]hether a claim recites 13 patent-eligible subject matter is a question of law which may contain disputes over 14 underlying facts.” Berkheimer v. HP Inc., 881 F.3d 1360, 1368 (Fed. Cir. 2018). 15 The Supreme Court has established a two-step test “for distinguishing patents that 16 claim laws of nature, natural phenomena, and abstract ideas from those that claim patent- 17 eligible applications of those concepts.” Alice, 573 U.S. at 217 (citing Mayo Collaborative 18 Servs. v. Prometheus Lab’s, Inc., 566 U.S. 66, 77-78 (2012)). First, the court must 19 “determine whether the claims at issue are directed to one of those patent-ineligible 20 concepts.” Id. (citation omitted). However, because “all inventions at some level embody, 21 use, reflect, rest upon, or apply laws of nature, natural phenomena, or abstract ideas,” 22 Mayo, 566 U.S. at 71, “courts must be careful to avoid oversimplifying the claims by 23 looking at them generally and failing to account for the specific requirements of the 24 claims.” McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1313 (Fed. Cir. 25 2016) (citation and internal quotation marks omitted). See also Enfish, 822 F.3d at 1337 26 (“[D]escribing the claims at [too] high [a] level of abstraction and untethered from the 27 language of the claims all but ensures that the exceptions to § 101 swallow the rule.”). 28 “Because there is no conclusive method of determining what constitutes an ‘abstract 1 idea’ that meets the first step of the Alice framework, courts compare the claims at issue to 2 those claims from previous cases, already determined to be directed to an abstract idea. 3 ‘Distinguishing between claims that recite a patent-eligible invention and claims that add 4 too little to a patent-ineligible abstract concept can be difficult, as the line separating the 5 two is not always clear.’ This difficulty is particularly pronounced in the context of patent 6 claims related to computer technology.” Crypto Research, LLC, v. Assa Abloy, Inc., 236 7 F. Supp. 3d 671, 680-81 (E.D.N.Y. 2017) (citations omitted). On the one hand, “the use 8 of a computer to implement a fundamental economic or conventional business practice 9 does not, by itself, render the claims patent eligible.” Id. at 681. On the other hand, “the 10 Federal Circuit has held that some developments in computer-related technology, in which 11 the focus of the claims is on solutions ‘necessarily rooted in computer technology in order 12 to overcome a problem specifically arising in the realm of computer networks,’ or on 13 ‘improvement to computer functionality itself,’ are not directed to an abstract idea.” Id. 14 (citations omitted). 15 If the first step of the Alice analysis shows that the claims are directed to an abstract 16 idea, the second step addresses whether the claims include an “inventive concept”—that 17 is, whether “an element or combination of elements . . . is sufficient to ensure that the patent 18 in practice amounts to significantly more than a patent upon the ineligible concept itself.” 19 Alice, 573 U.S. at 217-18 (cleaned up). “The second step of the Alice test is satisfied when 20 the claim limitations involve more than performance of well-understood, routine, and 21 conventional activities previously known to the industry.” Berkheimer, 881 F.3d at 1367 22 (cleaned up). “[A]n inventive concept can be found in the non-conventional and non- 23 generic arrangement of known, conventional pieces.” Bascom Glob. Internet Servs., Inc. 24 v. AT&T Mobility LLC, 827 F.3d 1341, 1350 (Fed. Cir. 2016). 25 B. Preliminary Matters 26 Before turning to the heart of the dispute—whether the factual allegations in the 27 proposed FAC are sufficient to survive a motion to dismiss with respect to § 101 28 eligibility—it is necessary to address a few preliminary matters. 1 First, to the extent Defendants contend it was improper for Plaintiff to add 2 allegations regarding the ’777 Patent to the proposed FAC,1 the Court disagrees. In the 3 September 2021 order, the Court did not place any specific limitations on the scope of the 4 anticipated amendment request, other than to explain that the purpose of any proposed 5 amendment should be to “address the deficiencies identified in this Order.” (Doc. 64 at 9- 6 10.) Those deficiencies, in turn, related to the insufficiency of the factual allegations in the 7 original complaint under both steps of the Alice test. Because the new allegations in the 8 FAC related to the ’777 Patent are intended to address those deficiencies, they do not fall 9 outside the scope of the amendment authorization. Furthermore, Defendants do not 10 contend that the new allegations regarding the ’777 Patent are somehow time-barred or 11 unfairly prejudicial.2 As noted, the sole ground on which Defendants oppose the 12 amendment request is futility. Thus, the presence of the new allegations regarding the ’777 13 Patent does not provide a basis for denying the amendment request. 14 Second, although the proposed FAC identifies an array of different claims appearing 15 in Plaintiff’s patents, “[t]he Federal Circuit has held that the district court need not address 16 each claim of the asserted patents individually. Instead, if the district court determines that 17 the claims are substantially similar and linked to the same abstract idea, the court may 18 consider a representative claim.” Crypto Research, 236 F. Supp. 3d at 680 (citation 19 omitted). Here, as in the September 2021 order, the Court agrees with Defendants that 20 Claim 1 of the ’004 Patent recites a system comprising a task pool, a controller, and co- 21 processors completing tasks, which is substantially similar to Claim 1 of the ’275 Patent 22 and Claim 1 of the ’777 Patent. Similarly, upon the Court’s review, the dependent claims— 23 that is, Claims 2-12 of the ’004 Patent, Claims 2-17 of the ’275 Patent, and Claims 2-14 of
24 1 Doc. 68 at 9 (describing Plaintiff’s “attempt to add a third, related, patent” as “unsanctioned”). 25 2 Plaintiff notified Defendants of the issuance of the ’777 Patent before the complaint 26 was filed (Doc. 1 ¶¶ 93, 96) and Defendants themselves emphasize that the ’777 Patent relates to and shares largely identical specifications with the ’004 and ’275 Patents (see 27 Doc. 68 at 2, 4, 9). Additionally, the remaining claims of the ’004 and ’275 Patents, and the claims of the ’777 Patent, are alleged to have been infringed by the same products 28 (AWS IoT Core and AWS IoT Greengrass) identified in the original complaint. (Doc. 66- 1 ¶¶ 94, 269, 281-82.) 1 the ’777 Patent—flow directly from Claim 1 of their respective patents and largely recite 2 the same content. (See Doc. 66-2 at 16-17, 25-26, 42-43.) Consequently, these claims 3 warrant similar substantive treatment, and the Court will again consider Claim 1 of the 4 ’004 Patent to be representative. 5 Third, the Court agrees with Defendants that the Nelson and Sylvester declarations 6 may not be considered at this juncture of the case. The narrow issue to be decided here is 7 whether Plaintiff’s motion to amend should be denied on futility grounds. The futility 8 analysis, in turn, rises and falls with the sufficiency of the proposed FAC under Rule 9 12(b)(6). And although the sufficiency analysis requires consideration of some highly 10 technical concepts, the Federal Circuit has “repeatedly recognized that in many cases it is 11 possible and proper to determine patent eligibility under 35 U.S.C. § 101 on a Rule 12(b)(6) 12 motion.” Genetic Techs. Ltd. v. Merial L.L.C., 818 F.3d 1369, 1373 (Fed. Cir. 2016). Thus, 13 the mere fact that Plaintiff is defending against a § 101 challenge does not mean that 14 Plaintiff is entitled to introduce expert declarations at the motion-to-dismiss stage. 15 Nor do the Nelson and Sylvester declarations qualify as the sorts of materials that a 16 district court would ordinarily be allowed to consider when ruling on a Rule 12(b)(6) 17 challenge. It is hornbook law that “a district court may not consider any material beyond 18 the pleadings in ruling on a 12(b)(6) motion.” Lee v. City of Los Angeles, 250 F.3d 668, 19 688 (9th Cir. 2001) (cleaned up). “A court may, however, consider certain materials— 20 documents attached to the complaint, documents incorporated by reference in the 21 complaint, or matters of judicial notice—without converting the motion to dismiss into a 22 motion for summary judgment.” United States v. Ritchie, 342 F.3d 903, 907-08 (9th Cir. 23 2003). It is difficult to see how that Nelson and Sylvester declarations could fall within 24 any of these exceptions. They are not attached to the proposed FAC (at the risk of putting 25 form over substance, they were filed as attachments to the motion to amend, not as 26 attachments to the proposed FAC),3 they are not incorporated by reference in the proposed
27 3 Doc. 66 at introductory page (“Plaintiff . . . respectfully moves the Court for leave to file the attached redlined [FAC] (Exhibit 1). As a courtesy, a clean copy of the FAC is 28 also attached as Exhibit 2. This Motion for Leave to file the FAC . . . is made pursuant to Fed. R. Civ. P. 15(a)(2) and supported by the Declarations of Dr. Brent Nelson and Dr. 1 FAC (the words “Nelson” and “Sylvester” do not appear anywhere in the proposed FAC), 2 and they are not subject to judicial notice. Cf. Athena Diagnostics, Inc. v. Mayo 3 Collaborative Servs., LLC, 915 F.3d 743, 755 (Fed. Cir. 2019) (affirming district court’s 4 refusal to consider patentee’s expert declaration when ruling on a § 101-based motion to 5 dismiss in part because “[t]he declaration does not ‘merge into the pleadings,’ as the 6 complaint does not reference it or otherwise depend on it. Nor is the declaration an official 7 public record, another type of document a court may consider with the pleadings.”). 8 Indeed, it appears that Plaintiff’s purpose in submitting the declarations was to prove the 9 veracity of the factual allegations in the FAC. (Doc. 69 at 10 [“As an expert with decades 10 of computing experience, Dr. Nelson confirms the factual allegations in ¶¶ 178-181 of the 11 FAC.”].) But there is no need to prove anything at the Rule 12(b)(6) stage—“[w]hen there 12 are well-pleaded factual allegations, a court should assume their veracity and then 13 determine whether they plausibly give rise to an entitlement to relief.” Ashcroft v. Iqbal, 14 556 U.S. 662, 679 (2009). 15 C. Merits 16 The September 2021 order concluded that the “Patents are directed towards the 17 abstract idea of a scrum board” for purposes of step one of the Alice analysis because the 18 factual allegations in the original complaint merely showed that “the Patents are aimed at 19 allocating computer processing power in an efficient way,” yet “scrum boards also allocate 20 human resources in an efficient way.” (Doc. 64 at 5-6.) The September 2021 order stated 21 that “[t]he Patents therefore are not aimed at a ‘specific implementation of a solution’ as 22 much as they consist of ‘generalized steps to be performed on a computer using 23 conventional computer activity.’” (Id. at 5-6.) Similarly, in Juniper, although Plaintiff 24 attempted to argue “that the ’777 patent teaches a way to reconfigure computer systems to 25 function more efficiently,” the court concluded this argument was not supported by the 26 record because “[Plaintiff] does not point to a specific improvement to computer 27 technology identified in the ’777 patent. Instead, [Plaintiff] quotes language from the 28 Douglas Sylvester attached as Exhibits 3 . . . and 4 . . . .”). 1 patent that the system ‘may be implemented retroactively on any computer or computer 2 network having an operating system that may be modified or otherwise configured to 3 implement the functionality described.’ This falls short of teaching a specific improvement 4 to computer technology, instead simply reconfiguring traditional computer networks to 5 operate as claimed in the ’777 patent.” 2022 WL 3031211 at *6. 6 In an effort to address the criticisms in the September 2021 order, the proposed FAC 7 adds detailed allegations regarding computer-specific functionality improvements. For 8 example, the proposed FAC alleges that, “[t]aken together, the controller, task pool, and 9 co-processors confer a substantial advantage over prior art processing systems by allowing 10 different types of co-processors to interact with the task pool without significantly 11 compromising their individual performance. Claim 1 [of the ’004 Patent] thus focuses on 12 improvements to computer functionality, as opposed to merely being directed to an abstract 13 idea.” (Doc. 66-1 at 31 ¶ 127.) Elsewhere, the proposed FAC elaborates as to why these 14 functionality improvements are computer-specific: “[C]onventional processors include a 15 CPU and one or more co-processors, where the CPU partitions the computational 16 requirements into tasks and distributes the tasks to co-processors. Consequently, a 17 significant amount of CPU bandwidth is consumed by task distribution; waiting for tasks 18 to be completed before distributing new tasks (often with dependencies on previous tasks); 19 responding to interrupts from co-processors when a task is completed; and responding to 20 other messages from co-processors. To address these shortcomings, [the ’004 Patent] 21 invented a revolutionary new parallel processing paradigm, including co-processors 22 configured to proactively retrieve new tasks from the task pool without having to 23 communicate directly with (or wait for) the CPU.” (Id. at 32 ¶¶ 131-32.) 24 In the tentative order issued before oral argument, the Court suggested these new 25 allegations could be viewed as supplying important new details that were missing from the 26 complaints deemed insufficient in the September 2021 order and in Juniper. However, 27 during oral argument, Defendants identified various reasons why the proposed FAC’s 28 factual allegations should be viewed as essentially indistinguishable from the allegations 1 that were analyzed in those orders. (Doc. 97-1.) Upon reflection, Defendants’ argument 2 has some force—although the new paragraphs in the proposed FAC discussing computer- 3 specific functionality improvements are more detailed than the allegations on that topic 4 that appeared in the original complaint, they can be viewed as raising the same overarching 5 points. 6 Despite this, the Court stands by the conclusion in the tentative order that the factual 7 allegations in the proposed FAC are sufficient to avoid dismissal under step one of the 8 Alice framework.4 “[T]he first step in the Alice inquiry . . . asks whether the . . . focus of 9 the claims is on the specific asserted improvement in computer capabilities . . . or, instead, 10 on a process that qualifies as an ‘abstract idea’ for which computers are invoked merely as 11 a tool.” Enfish, 822 F.3d at 1335-36. Where “the plain focus of the claims is on an 12 improvement to computer functionality itself, not on economic or other tasks for which a 13 computer is used in its ordinary capacity,” the claims are not abstract. Id. at 1336. See 14 also Ancora Techs., Inc. v. HTC Am., Inc., 908 F.3d 1343, 1348-49 (Fed. Cir. 2018) 15 (“[C]laim 1 of the ’941 patent is not directed to an abstract idea. Improving security . . . 16 can be a non-abstract computer-functionality improvement if done by a specific technique 17 that departs from earlier approaches to solve a specific computer problem. . . . In short, 18 claim 1 of the ’941 patent is directed to a solution to a computer-functionality problem . . . 19 [and] therefore passes muster under Alice step one, as it is not directed to patent-ineligible 20 subject matter.”); Electric Power Group, LLC v. Alstom S.A., 830 F.3d 1350, 1354 (Fed. 21 Cir. 2016) (contrasting Enfish, where “the claims at issue focused . . . on a specific
22 4 To the extent this conclusion is inconsistent with the conclusions reached in the September 2021 order and in Juniper, the Court acknowledges that when two experienced 23 and esteemed jurists have reached the same conclusion on a complicated issue such as the one presented here, a third judge should think long and hard before going a different 24 direction. Nevertheless, the analysis below represents the undersigned’s best attempt to independently evaluate the sufficiency of the proposed FAC under the complicated and 25 often difficult-to-reconcile law pertaining to Alice’s first step. See generally Visual Memory LLC v. NVIDIA Corp., 867 F.3d 1253, 1259 (Fed. Cir. 2017) (acknowledging “the 26 difficulty inherent in delineating the contours of an abstract idea”); DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1255 (Fed. Cir. 2014) (“Distinguishing between claims 27 that recite a patent-eligible invention and claims that add too little to a patent-ineligible abstract concept can be difficult, as the line separating the two is not always clear.”); Crypto 28 Research, 236 F. Supp. 3d at 680-81 (“This difficulty is particularly pronounced in the context of patent claims related to computer technology.”). 1 improvement—a particular database technique—in how computers could carry out one of 2 their basic functions of storage and retrieval of data,” with “[t]he present case,” where “the 3 focus of the claims is not on such an improvement in computers as tools, but on certain 4 independently abstract ideas that use computers as tools”). 5 Here, the specification of the ’004 Patent states that “[t]he present invention 6 generally relates to parallel-process computing, and particularly to a processing 7 architecture which involves autonomous co-processors configured to proactively retrieve 8 tasks from a task pool population by a central processing unit.” (Doc. 66-2 at 10.) It 9 explains that “[p]resently known multiprocessing approaches are disadvantageous in that 10 a significant amount of CPU bandwidth is consumed by task distribution; waiting for tasks 11 to be completed before distributing new tasks (often with dependencies on previous tasks); 12 responding to interrupts from co-processors when a task is completed; and responding to 13 other messages from co-processors.” (Id.) Given these existing problems, the specification 14 states that “[a] multiprocessor architecture is . . . needed which reduces CPU management 15 overhead, and which also more effectively harnesses and exploits available co-processing 16 resources.” (Id.) The specification explains that the claims in the ’004 Patent address and 17 improve upon these computer-functionality problems in various ways, including by 18 enabling “the CPU [to] communicate[] directly with the task pool, and communicate[] 19 indirectly with the co-processors through the task pool,” and that, “[as] a result, the co- 20 processors work together ‘in solidarity’ with one another and with the task pool to complete 21 aggregate computations requirements by autonomously retrieving and completing 22 individual tasks which may or may not be inter-related.” (Id.) It continues: “Those skilled 23 in the art will appreciate that interoperability among the CPU and co-processors may be 24 facilitated by configuring the CPU to compose and/or structure tasks at a level of 25 abstraction which is independent of the instruction set architecture associated with the 26 various co-processors, thereby allowing the components to communicate at a task level 27 rather than an instruction level. As such, devices and their associated processors may be 28 added to a network on a ‘plug and play’ basis. Another aspect of this invention provides 1 interoperability within a heterogenous array of CPUs with different instruction set 2 architectures.” (Id. at 11.) 3 Given this backdrop, the new allegation in the proposed FAC that “[c]laim 1 . . . 4 focuses on improvements to computer functionality, as opposed to merely being directed 5 to an abstract idea” (Doc. 66-1 at 31 ¶ 127) is non-conclusory and plausible. The claims 6 in the ’004 Patent expressly focus on addressing existing problems in computer 7 functionality—“Presently known multiprocessing approaches are disadvantageous in that 8 a significant amount of CPU bandwidth is consumed by task distribution; waiting for tasks 9 to be completed before distributing new tasks (often with dependencies on previous tasks); 10 responding to interrupts from co-processors when a task is completed; and responding to 11 other messages from co-processors”—by creating a new “multiprocessor architecture” that 12 “reduces CPU management overhead” and “more effectively harnesses and exploits 13 available co-processing resources.” As noted, the Federal Circuit has held that claimed 14 improvements should be considered non-abstract at step one where “the plain focus of the 15 claims is on an improvement to computer functionality itself” (Enfish), or where the claims 16 are directed at “a solution to a computer-specific functionality problem” (Ancora), or where 17 the claims are directed at “a specific improvement . . . in how computers carry out one of 18 their basis functions of storage and retrieval of data” (Electric Power Group). The 19 proposed FAC specifically alleges that Claim 1 of the ’004 Patent is intended to achieve 20 such improvements and those allegations are non-conclusory and plausible because they 21 are grounded in the contents of the ’004 Patent itself. 22 Notwithstanding all of this, Defendants argue that the alleged functionality 23 improvements must be considered abstract because they are analogous to how a scrum 24 board enhances the efficiency of human decisionmaking. The Court understands the 25 analogy but disagrees that it carries the day for purposes of step one. In Data Engine Techs. 26 LLC v. Google LLC, 906 F.3d 999 (Fed. Cir. 2018), which Plaintiff cited during oral 27 argument, the court confronted a similar argument. There, Google argued that a claim 28 “directed to a specific method for navigating through three-dimensional electronic 1 spreadsheets” was ineligible under § 101 because courts have “repeatedly found that claims 2 directed to methods of organizing and presenting information are abstract.” Id. at 1010. 3 Google elaborated “that humans have long used tabs to organize information. It cites 4 tabbed notebooks, binder dividers, file folders, and sticky Post-it notes as well-known 5 examples of organizing information using tabs.” Id. at 1011. The Federal Circuit rejected 6 this argument and reversed the district court’s determination that Google was entitled to 7 judgment on the pleadings with respect to the § 101 challenge, explaining: 8 We agree that tabs existed outside the context of electronic spreadsheets prior to the claimed invention. It is not enough, however, to merely trace the 9 invention to some real-world analogy. The eligibility question is not whether 10 anyone has ever used tabs to organize information. That question is reserved for §§ 102 and 103. The question of abstraction is whether the claim is 11 ‘directed to’ the abstract idea itself. We must consider the claim as a whole 12 to determine whether the claim is directed to an abstract idea or something more. Google fails to appreciate the functional improvement achieved by 13 the specifically recited notebook tabs in the claimed method. 14 Id. (emphasis added). Thus, the court concluded that the claim “is not abstract under Alice 15 step one” and found it unnecessary to “reach Alice step two.” Id. Here, too, even if the 16 scrum-board analogy has some merit, it is not dispositive (at least at the motion-to-dismiss 17 stage) in light of the FAC’s non-conclusory and plausible allegations of computer-specific 18 functionality improvements. 19 In a related vein, to the extent Defendants argue the claimed improvements are not 20 really computer-specific functionality improvements, but simply the efficiencies that 21 would arise in any setting from the use of a scrum board, the Court cannot see how this 22 sort of assertion could be resolved in Defendants’ favor at the current stage of the case. 23 Although Defendants are correct (Doc. 97-1 at 2) that the Federal Circuit has frequently 24 made Alice ineligibility determinations at the pleading stage, this does not mean the 25 determination should always be made at that stage. See, e.g., Visual Memory LLC v. 26 NVIDIA Corp., 867 F.3d 1253, 1261-62 (Fed. Cir. 2017) (“Configuring the memory system 27 based on the type of processor connected to the memory system is the improvement in 28 computer technology to which the claims are directed. Alice requires no more from the 1 claims or the specification to support our conclusion that the claims are not directed to an 2 abstract idea. This conclusion is particularly proper on a motion to dismiss under Rule 3 12(b)(6), where all factual inferences drawn from the specification must be weighed in 4 favor of Visual Memory, the non-moving party.”). Because the Court lacks independent 5 knowledge of how parallel-process computing works, which is not a matter of common 6 sense, it would be inappropriate to simply disregard the proposed FAC’s allegation that the 7 claimed improvements are intended to overcome computer-related functionality problems. 8 Ashcroft v. Iqbal, 556 U.S. 662, 679 (2009) (“Determining whether a complaint states a 9 plausible claim for relief will . . . be a context-specific task that requires the reviewing court 10 to draw on its judicial experience and common sense.”). Defendants may very well be able 11 to establish at a future stage of the case that the claimed functionality improvements are 12 not computer-specific, but it would be premature to make that determination now. 13 Finally, the Court disagrees with Defendants’ contention, raised during oral 14 argument, that Yu v. Apple, 1 F.4th 1040 (Fed. Cir. 2021), compels a ruling in their favor 15 at step one. There, the claim was expressly directed at the “idea of taking two pictures 16 (which may be at different exposures) and using one picture to enhance the other in some 17 way.” Id. at 1043. See also id. (“[W]e note that claim 1 results in ‘producing a resultant 18 digital image from said first digital image enhanced with said second digital image.’”). 19 Additionally, the plaintiff did “not dispute that . . . the idea and practice of using multiple 20 pictures to enhance each other has been known by photographers for over a century.” Id. 21 As a result, the Federal Circuit (over Judge Newman’s dissent) rejected the patentholder’s 22 argument “that the asserted claims ‘are directed to a patent-eligible improvement in digital 23 camera functionality’ by ‘providing a specific solution’ to problems such as ‘low resolution 24 cause by low pixel counts’ and ‘inability to show vivid colors caused by limited pixel 25 depth.” Id. at 1044. This was because “claim 1’s solution to those problems is the abstract 26 idea itself—to take one image and ‘enhance’ it with another.” Id. Here, in contrast, the 27 FAC plausibly alleges that Claim 1 of the’004 Patent is not directed at using computers as 28 a tool for accomplishing some abstract end (such as enhancing an image), but instead is || directed at an improvement to computer functionality itself, And where “the plain focus 2|| of the claims is on an improvement to computer functionality itself, not on economic or || other tasks for which a computer is used in its ordinary capacity,” the claims are not 4|| abstract. Enfish, 822 F.3d at 1336. 5 Given these conclusions, it is unnecessary to address whether the proposed FAC 6|| also sufficiently alleges inventive concepts to survive dismissal under step two. Data 7\| Engine, 906 F.3d at 1011. During oral argument, Defendants raised various points that 8 || would otherwise require careful review and potential reconsideration of the tentative 9|| ruling’s step-two analysis. Because Plaintiff's amendment request has been pending for an unusually long time and is serving as the bottleneck for several other developments, 11 |} including future proceedings in Juniper and, as Defendants’ counsel explained during oral 12 || argument, a potential motion to stay in this action based on Juniper and/or pending IPR 13} proceedings (Doc. 92), the Court concludes that it makes sense to rule now rather than continue to ponder whether step two provides an alternative basis for granting the 15 || amendment request. 16 Accordingly, 17 IT IS ORDERED that Plaintiff's motion for leave to amend (Doc. 66) is granted. 18 IT IS FURTHER ORDERED that Plaintiff must file its proposed FAC (Doc. 66- || 13) within seven days of the issuance of this order. 20 Dated this 22nd day of August, 2022. 21 22 im a 23 } CC —— Dominic W. Lanza IA United States District Judge 25 26 27 28
-21-