Juniper Networks Inc. v. Swarm Technology LLC

CourtDistrict Court, N.D. California
DecidedAugust 1, 2022
Docket3:20-cv-03137
StatusUnknown

This text of Juniper Networks Inc. v. Swarm Technology LLC (Juniper Networks Inc. v. Swarm Technology LLC) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Juniper Networks Inc. v. Swarm Technology LLC, (N.D. Cal. 2022).

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 JUNIPER NETWORKS INC., et al., Case No. 3:20-cv-03137-JD

8 Plaintiffs, ORDER RE MOTION TO DISMISS v. 9

10 SWARM TECHNOLOGY LLC, Defendant. 11

12 13 In this declaratory judgment action, plaintiff Juniper Networks, Inc. and its wholly owned 14 subsidiary, Apstra, Inc., (collectively, Juniper) seek a declaration of non-infringement of U.S. 15 Patent No. 9,146,777 (the ’777 patent), U.S. Patent No. 9,852,004 (the ’004 patent), and U.S. 16 Patent No. 10,592,275 (the ’275 patent) against defendant and patent owner Swarm Technology 17 LLC (Swarm). Dkt. No. 38 (first amended complaint); Dkt. No. 64-1 (’004 patent); Dkt. No. 64-2 18 (’275 patent); Dkt. No. 64-3 (’777 patent). Swarm filed counterclaims alleging that Juniper 19 infringes the three patents. Dkt. No. 64. Juniper asks to dismiss the counterclaims on the grounds 20 that all claims of the ’777 patent, ’004 patent, and ’275 patent are directed to patent-ineligible 21 subject matter under 35 U.S.C. § 101. Dkt. No. 75. In light of “the sources properly considered 22 on a motion to dismiss, such as the complaint, the patent, and materials subject to judicial notice,” 23 Aatrix Software, Inc. v. Green Shades Software, Inc., 882 F.3d 1121, 1128 (Fed. Cir. 2018), the 24 counterclaims are dismissed under Section 101 and Alice Corp. Pty. Ltd. v. CLS Bank 25 International, 573 U.S. 208 (2014), with leave to amend. 26 I. THE ’004 PATENT AND ’275 PATENT 27 In an unrelated case pending in the District of Arizona, the ’004 patent and ’275 patent 1 Amazon.com, Inc., 561 F. Supp. 3d 861 (D. Ariz. 2021). The court dismissed Swarm’s 2 infringement claims based on the patents, and stated that Swarm could file a motion for leave to 3 file an amended complaint, id. at 869, which Swarm did on October 20, 2021. Swarm Tech. LLC 4 v. Amazon.com, Inc., No. 2:21-cv-438-DWL, Dkt. No. 66 (D. Ariz.). The case was reassigned to a 5 different judge in the District of Arizona, and the motion for leave to file an amended complaint is 6 pending. Id. at Dkt. No. 78. 7 Swarm in effect invites the Court to disregard the invalidation of the ’004 and ’275 patents, 8 and allow the counterclaims based on them to proceed. The request is ill taken. Strictly speaking, 9 this is not a matter of preclusion. As a general principal, “once the claims of a patent are held 10 invalid in a suit involving one alleged infringer, and unrelated party who is sued for infringement 11 of those claims may reap the benefit of the invalidity decision under principles of collateral 12 estoppel.” Soverain Software LLC v. Victoria’s Secret Direct Brand Mgmt., LLC, 778 F.3d 1311, 13 1315 (Fed. Cir. 2015). But collateral estoppel does not apply absent a final judgment, and the 14 invalidation order in the District of Arizona is not final yet. See Reyn’s Pasta Bella, LLC v. Visa 15 USA, Inc., 442 F.3d 741, 746 (9th Cir. 2006); Slip Track Sys., Inc. v. Metal-Lite, Inc., 304 F.3d 16 1256, 1262 (Fed. Cir. 2002) (regional circuit law applies for collateral estoppel analysis). Even 17 so, good reasons weigh against ignoring the order, as Swarm urges. Swarm has ample opportunity 18 to respond to the order by seeking leave to amend its complaint, which it has already done, 19 requesting reconsideration from the District of Arizona, or appealing to the Federal Circuit. A 20 lateral appeal to a sister district court is not appropriate, or consistent with the fair and efficient 21 administration of justice. 22 Consequently, the counterclaims based on the’004 and ’275 patents are dismissed. The 23 dismissal is without prejudice, and Swarm may request leave to re-allege them as developments in 24 the District of Arizona or on appeal warrant. 25 II. THE ’777 PATENT 26 The ’777 patent was issued on September 29, 2015, and is assigned to Swarm. Dkt. No. 27 64-3. The patent is directed to a “method and apparatus for processing information in parallel 1 unit” (CPU). Id. at Abstract. The autonomous computer processing units are called “solidarity 2 cells,” which can be “general- or special-purpose processor[s].” Id. at 1:59-66. The solidarity 3 cells also have “agents” which are “software modules” that can be dispatched to a task pool, 4 populated by the CPU, to pick up tasks for the solidarity cell to complete. Id. at 2:1-18. The 5 patent states that this approach solves two problems in typical multiprocessing frameworks: that 6 “a significant amount of the CPU’s processing time is consumed by managing the co-processing 7 tasks,” and that “a co-processor will remain idle as it waits for a thread to be assigned to it by the 8 CPU.” Id. at 1:31-45. 9 For the eligibility dispute, the parties do not address whether Claim 1 is representative, but 10 their treatment of the claims suggests that Claim 1 should be treated as such, as neither party 11 argues that the other claims of the ’777 patent contain any significant limitations other than those 12 included in Claim 1. See Elec. Power Grp. v. Alstom S.A., 830 F.3d 1350, 1352 (Fed. Cir. 2016). 13 Consequently, the Court will treat Claim 1 as representative. 14 Claim 1 recites: 15 1. An apparatus for parallel processing of a large computing requirement, the apparatus comprising: 16 a central processing unit (“CPU”); a task pool in electronic communication with the CPU; and 17 a first solidarity cell in electronic communication with the task pool, the first solidarity cell comprising a first agent 18 configured to proactively retrieve, from the task pool, without requiring an instruction from the CPU, a matching task for the 19 solidarity cell to process; wherein the CPU populates the task pool by dividing the 20 requirement into one or more threads and placing the threads in the task pool, each thread comprising one or more tasks, 21 and the matching task being one of the tasks; wherein each task comprises a descriptor, the descriptor 22 containing at least: a function to be executed; and 23 a memory location of data upon which the function is to be executed; 24 wherein the first agent is a data frame comprising: a source address, a destination address and a payload; 25 wherein the first agent retrieves the matching task by: being dispatched by the first solidarity cell to the task pool, 26 during which the source address is the first solidarity cell's address, the destination address is the task pool's address, 27 and the payload comprises a list of functions the first and has a function that the first solidarity cell can perform; 1 and returning to the first solidarity cell, during which the source 2 address is the task pool's address, the destination address is the first solidarity cell's address, and the payload 3 comprises the descriptor of the matching task. 4 Dkt. No. 64-3 at 7:41-8:8. 5 A. Legal Standards 6 Rule 8(a)(2) of the Federal Rules of Civil Procedure requires the complaint to provide “a short 7 and plain statement of the claim showing that the pleader is entitled to relief.” To meet that rule and 8 survive a Rule 12(b)(6) motion to dismiss, a plaintiff must allege “enough facts to state a claim to 9 relief that is plausible on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). This does 10 not impose a probability requirement at the pleading stage.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Marrero v. Goya of Puerto Rico, Inc.
304 F.3d 7 (First Circuit, 2002)
CyberSource Corp. v. Retail Decisions, Inc.
654 F.3d 1366 (Federal Circuit, 2011)
Intellectual Ventures I LLC v. Capital One Bank (USA)
792 F.3d 1363 (Federal Circuit, 2015)
Genetic Technologies Limited v. Merial L.L.C.
818 F.3d 1369 (Federal Circuit, 2016)
Enfish, LLC v. Microsoft Corporation
822 F.3d 1327 (Federal Circuit, 2016)
Tli Communications LLC v. Av Automotive, L.L.C.
823 F.3d 607 (Federal Circuit, 2016)
Electric Power Group, LLC v. Alstom S.A.
830 F.3d 1350 (Federal Circuit, 2016)
Affinity Labs of Texas, LLC v. amazon.com Inc.
838 F.3d 1266 (Federal Circuit, 2016)
Fairwarning Ip, LLC v. Iatric Systems, Inc.
839 F.3d 1089 (Federal Circuit, 2016)
Two-Way Media Ltd. v. Comcast Cable Communications, LLC
874 F.3d 1329 (Federal Circuit, 2017)
Villalta-Martinez v. Sessions
882 F.3d 20 (First Circuit, 2018)
Aatrix Software, Inc. v. Green Shades Software, Inc.
882 F.3d 1121 (Federal Circuit, 2018)
Berkheimer v. Hp Inc.
890 F.3d 1369 (Federal Circuit, 2018)
Bsg Tech LLC v. Buyseasons, Inc.
899 F.3d 1281 (Federal Circuit, 2018)
Cellspin Soft, Inc. v. Fitbit, Inc.
927 F.3d 1306 (Federal Circuit, 2019)

Cite This Page — Counsel Stack

Bluebook (online)
Juniper Networks Inc. v. Swarm Technology LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/juniper-networks-inc-v-swarm-technology-llc-cand-2022.