Chrimar Systems, Inc. v. Ruckus Wireless Inc.

CourtDistrict Court, N.D. California
DecidedApril 16, 2020
Docket3:16-cv-00186
StatusUnknown

This text of Chrimar Systems, Inc. v. Ruckus Wireless Inc. (Chrimar Systems, Inc. v. Ruckus Wireless Inc.) 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
Chrimar Systems, Inc. v. Ruckus Wireless Inc., (N.D. Cal. 2020).

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 Case No. 16-cv-00186-SI (Dkt. No. 131) 7 CHRIMAR SYSTEMS INC, et al., And related cases: 3:16-cv-00558-SI (Dkt. No. 109) 8 Plaintiffs, 3:16-cv-00624-SI (Dkt. No. 132) 3:16-cv-00897-SI (Dkt. No. 102) 9 v. ORDER GRANTING DEFENDANTS’ 10 RUCKUS WIRELESS, INC., MOTION TO DISMISS

11 Defendant.

13 Before the Court is defendants’ motion to strike, or in the alternative, to dismiss Count I of 14 plaintiff Chrimar’s Third Amended Complaint (“TAC”). Dkt. No. 129. Having reviewed the 15 parties’ submissions, the Court hereby GRANTS the motion to dismiss. 16

17 BACKGROUND 18 Plaintiff Chrimar Systems Inc. and Chrimar Holding Company LLC (collectively, 19 “Chrimar”) filed these patent infringement actions against Juniper Networks Inc. (“Juniper”), 20 Ruckus Wireless Inc. (“Ruckus”), Netgear Inc. (“Netgear”), and Fortinet Inc. (“Fortinet”) 21 (collectively, “defendants”) on July 1, 2015, in the Eastern District of Texas. See Dkt. No. 1 22 (Complaint). The complaint alleges infringement of four patents held by Chrimar: U.S. Patent Nos. 23 8,115,012 (“the ’012 patent”), 8,942,107 (“the ’107 patent”), 8,902,760 (“the ’760 patent”), and 24 9,019,838 (“the ’838 patent”). Id. The actions were transferred from Texas to the Northern District 25 of California in December 2015. Dkt. No. 89. On July 8, 2016, defendant Juniper filed petitions 26 for Inter Partes Review (“IPR”) of the four patents and was later joined by defendants Ruckus and 27 Netgear. Dkt. No. 126 at 2. For the ’107 patent, defendant Juniper requested review of claims 1, 5, 1 31, 43, 70, 72, 74, 75, 83, 103 (across 1, 5, 31, 43, 70, 72, and 75), 104, 111, 123, and 125 (across 2 104, 111, and 123). Dkt. No. 132-3. On September 26, 2016, this Court stayed the patent 3 infringement actions, until the Patent Trial and Appeal Board (“PTAB”) reached final written 4 decisions with respect to the four IPR petitions. Dkt. No. 96 at 10. Between December 2016 and 5 January 2017, the PTAB instituted an IPR for each asserted patent, including the ’107 patent. Dkt. 6 No. 132-6. 7 In IPR, defendants Juniper, Ruckus, and Netgear successfully asserted the challenged claims 8 of the ’107 patent were obvious1 over prior art Hunter, Bulan, Bloch, Huizinga, and IEEE 802.3. 9 Dkt. No. 132-8 at 15, 49. Claim 103 of the ’107 patent is a multiple dependent claim and recites 10 “wherein the piece of Ethernet terminal equipment is a piece of powered-off Ethernet terminal 11 equipment.” ’107 patent, at 22:13-16. The PTAB found “that the ‘powered-off’ limitation is shown 12 by the combination of Hunter and Bulan.” Dkt. No. 132-8 at 16. The PTAB stated that “claims 1, 13 5, 31, 43, 70, 72, 74, 75, 83, 103, 104, 111, 123, and 125 of the ’107 patent would have been obvious 14 over Hunter and Bulan.” Id. at 48 (emphasis added). The PTAB also found that “the combination 15 [of Bloch, Huizinga, and IEEE] and specifically Bloch discloses ‘powered off’ terminal 16 equipment.’” Id. at 64. The PTAB ultimately “ORDERED claims 1, 5, 31, 43, 70, 72, 74, 75, 83, 17 103, 104, 111, 123, and 125 of the ’107 patent … unpatentable.” Id. at 84. 18 The PTAB reached final written decisions in the other three IPR petitions and ordered those 19 challenged claims unpatentable as well. Dkt. No. 126 at 3. However, an ex parte reexamination 20 was filed by a third party on the ’760 patent prior to final written decision, and claims 73-100, 104- 21 169, and 173-219 were amended and found patentable, as amended. Dkt. No. 122 at 2. The PTAB 22 did not review the amended claims of the ’760 patent that were found patentable during 23 reexamination. Id. Chrimar appealed all four of the PTAB’s Final Written Decisions to the U.S. 24 Court of Appeals for the Federal Circuit, which upheld the PTAB decisions. Dkt. No. 126. Chrimar 25 filed a petition for Writ of Certiorari in the U.S. Supreme Court challenging the Federal Circuit’s 26 1 Under 35 U.S.C. § 103 (a) a patent claim is invalid as obvious if the differences between 27 the claimed invention and the prior art are “such that the subject matter as a whole would have been 1 affirmations. Id. On February 24, 2020, the Supreme Court denied Chrimar’s petition.2 Dkt. No. 2 131 at 3. 3 In December 2019, this Court lifted the stay on the patent infringement actions and set a case 4 management conference for January 24, 2020. Dkt. No. 123. At the case management conference, 5 Chrimar requested permission to add an additional claim from the ’107 patent based on a new claim 6 construction that came out of the IPR proceedings. Dkt. No. 133 at 2. On January 30, 2020, the 7 Court issued a scheduling order permitting Chrimar to “file an Amended Complaint adding only (1) 8 allegations relating to the ex parte reexamination certificate of the ’760 patent and (2) allegations 9 regarding the ’825 patent.” Dkt. No. 127 (Scheduling Order). The Court also permitted Chrimar to 10 file corresponding amended infringement contentions. Id. On February 7, 2020, Chrimar filed the 11 TAC, which included four causes of action: (1) Infringement of the ’107 Patent; (2) Infringement 12 of the ’760 Patent; (3) Infringement of the ’838 Patent; and (4) Infringement of the ’825 Patent. 13 Dkt. No. 129. On the same day, Chrimar sent defendants the First Amended Infringement 14 Contentions alleging direct infringement of claim 103 (across claim 87) of the ’107 patent. Dkt. 15 No. 131-5. 16 On February 28, 2020, defendants filed the instant Motion to Strike, or in the alternative, to 17 Dismiss, arguing the Court should strike the first cause of action for infringement of the ’107 patent 18 because it violates the scheduling order, or alternatively, the Court should dismiss the first cause of 19 action because it fails to recite a plausible claim of patent infringement. Dkt. No. 131 (Motion). In 20 the latter argument, defendants argue claim 103 of the ’107 patent was invalidated without 21 qualification, and an invalid claim cannot be infringed. Id. at 6. In its Opposition, Chrimar seeks 22 permission to amend its infringement contentions to include claim 103 (across claim 87) of the ’107 23 patent. Id. at 9. 24 25 26 2 The Federal Circuit judgment of the ’107 patent and the U.S. Supreme Court’s Order List 27 denying Chrimar’s petition were attached to Defendant’s Joint Motion to Strike, or in the alternative, 1 LEGAL STANDARD 2 Under Federal Rule of Civil Procedure 12(b)(6), a district court must dismiss a complaint if 3 it fails to state a claim upon which relief can be granted. To survive a Rule 12(b)(6) motion to 4 dismiss, the plaintiff must allege “enough facts to state a claim to relief that is plausible on its face.” 5 Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570, 127 S.Ct. 1955, 167 L.Ed.2d 929 (2007). This “facial 6 plausibility” standard requires the plaintiff to allege facts that add up to “more than a sheer 7 possibility that a defendant has acted unlawfully.” Ashcroft v. Iqbal, 556 U.S. 662, 678, 129 S.Ct. 8 1937, 173 L.Ed.2d 868 (2009). While courts do not require “heightened fact pleading of specifics,” 9 a plaintiff must allege facts sufficient to “raise a right to relief above the speculative level.” 10 Twombly, 550 U.S. at 555, 570, 127 S.Ct. 1955. 11 To state a claim for patent infringement, “a patentee need only plead facts sufficient to place 12 the alleged infringer on notice. This requirement ensures that the accused infringer has sufficient 13 knowledge of the facts alleged to enable it to answer the complaint and defend itself.” Phonometrics, 14 Inc. v.

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)

Cite This Page — Counsel Stack

Bluebook (online)
Chrimar Systems, Inc. v. Ruckus Wireless Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/chrimar-systems-inc-v-ruckus-wireless-inc-cand-2020.