TriDiNetworks Ltd. v. NXP USA, Inc.

District Court, D. Delaware·Decided May 15, 2020·No. 1:19-cv-01062·Unknown

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE

TRIDINETWORKS LTD., ) ) Plaintiff, ) ) v. ) Civil Action No. 19-1062-CFC-CJB ) NXP-USA, INC. and NXP B.V., ) ) Defendants. )

REPORT AND RECOMMENDATION

Pending in this patent infringement case brought by Plaintiff TriDiNetworks Ltd. (“Plaintiff”) against Defendants NXP-USA, Inc. (“NXP-USA” or “Defendant”) and NXP B.V. (collectively with NXP-USA, “Defendants”) is NXP-USA’s motion to dismiss the operative First Amended Complaint (“FAC”) against it for failure to state a claim (the“Motion”), filed pursuant to Federal Rule of Civil Procedure 12(b)(6). (D.I. 13) For the reasons set forth below, the Court recommends the Motion be GRANTED-IN-PART and DENIED-IN-PART. I. BACKGROUND The Court assumes familiarity with and incorporates by reference the summary of the background of this case set out in its May 7, 2020, Report and Recommendation (“May 7 R&R”), in which it recommended granting foreign Defendant NXP B.V.’s motion to dismiss for lack of personal jurisdiction, pursuant to Federal Rule of Civil Procedure 12(b)(2). (D.I. 43) Further relevant facts related to resolution of the Motion will be set out as needed in Section III. The Motion was filed on October 18, 2019. (D.I. 13) Briefing on the Motion was completed on November 8, 2019. (D.I. 21) II. LEGAL STANDARD Defendant’s Motion was brought pursuant to Rule 12(b)(6). The Court will review the Motion pursuant to the familiar two-part analysis set out in cases like Fowler v. UPMC Shadyside, 578 F.3d 203, 210-11 (3d Cir. 2009); it incorporates the relevant legal standard set out in Fowler by reference herein.

III. DISCUSSION

In the FAC, Plaintiff brings five Counts against both Defendants, including NXP-USA. NXP-USA’s Motion argues for dismissal of all Counts against it. Below, the Court will analyze Defendant’s arguments as to Count I (regarding direct infringement), then as to Counts II and II (regarding induced infringement) and then as to Counts IV and V (regarding contributory infringement). A. Direct Infringement Under 35 U.S.C. § 271(a) (Count I) In Count I, Plaintiff brings a claim for direct infringement of the patent-in-suit, United States Patent No. 8,437,276 (the “'276 patent”) against both Defendants. (D.I. 7 (“FAC”) at ¶¶ 26-30) In Count I, Plaintiff accuses both Defendants of a broad array of infringing conduct with regard to the accused products (which include certain “Smart Home” development kits, or “kits,” including the “JN516x-EK004” or “JN516x Evaluation Kit”). (Id. at ¶¶ 25, 27) But in its answering brief, Plaintiff narrowed its direct infringement theory. There, Plaintiff asserted that the FAC at least plausibly alleges that NXP-USA makes the accused kits, and that it uses the kits by testing them and by demonstrating them at trade shows in the U.S. (D.I. 18 at 7) By the time it filed its reply brief, Defendant was challenging the sufficiency of these direct infringement allegations on only one ground: that in the FAC, Plaintiff had impermissibly “lumped” it together with NXP B.V., without sufficiently identifying which Defendant was responsible for which act of direct infringement. (D.I. 21 at 1-4) To that end, it is not impermissible per se for a plaintiff to refer to multiple defendants collectively in a complaint. But in order to sufficiently plead direct infringement as to each defendant, at some point the plaintiff has to plausibly and clearly allege that each individual defendant has engaged in at least one type of infringing act. See Promos Techs., Inc. v. Samsung Elecs. Co., Civil Action No. 18- 307-RGA, 2018 WL 5630585, at *3 (D. Del. Oct. 31, 2018); N. Star Innovations, Inc. v. Toshiba

Corp., Civil Action No. 16-115-LPS-CJB, 2016 WL 7107230, at *2 (D. Del. Dec. 6, 2016). Paragraph 25 of the FAC (a part of Count I) sets out how at least the accused JN516x Evaluation Kit may be used to infringe at least method claim 1 of the patent-in-suit. (FAC at ¶ 25(a)-(h)) The first portion of that method claim regards creating a design for the claimed network. ('276 patent, col. 24:63-67; FAC at ¶ 25(a)-(b)) As to that step, the Court understands that Plaintiff’s allegation is that this step is satisfied when “NXP” creates and pre-loads device profiles for expected connecting nodes at a factory (i.e., when it makes the kit). (Id. at ¶¶ 25, 27) And as for the remaining steps of the method claim, Plaintiff alleges that “NXP” “perform[s] steps c-h when demonstrating ‘Smart Home’ systems and also when testing ‘Smart Home’ components at the factory.” (Id. at ¶ 25(g); see also id. at ¶¶ 18-19 (alleging that “NXP”

promotes its products at trade shows)) It is true that when making these allegations, Plaintiff uses the collective term “NXP”—a term the FAC clearly means to refer to both Defendants. (Id. at ¶ 4) But then in paragraph 27 (also found in Count I), the FAC goes on to explicitly state that its allegations of direct infringement are asserted “including, without limitation [at] each of Defendant NXP[-USA1] and

1 Defendant takes issue with the fact that in this portion of Count I, Plaintiff actually lists NXP-USA’s corporate name as “NXP Semiconductors US, Inc.[,]” (FAC at ¶ 27), which is an error, as there is no entity with that name, (D.I. 14 at 7; D.I. 21 at 3). But in light of the entirety of the FAC, it is clear that there Plaintiff intended to refer to NXP-USA. (D.I. 14 at 1 n.3; D.I. 18 at 4) The Court thus interprets this reference as such. . . . NXP[] B.V.” (Id. at ¶ 27) That is a direct statement that NXP-USA (via its employees) is said to be committing the accused acts of direct infringement in the U.S. And from what the Court can glean from the FAC, it is not implausible that NXP-USA—a Defendant who, after all, is based in the United States, (id. at ¶ 2)—actually does make these accused products in the U.S.,

test those products in the U.S. and demonstrate those products at U.S.-based trade shows. (See also D.I. 18 at 7 (Plaintiff’s answering brief arguing the same)) Taking these allegations together, it is clear to the Court that both Defendants were separately being accused of certain acts of direct infringement.2 And it is plausible that NXP- USA actually commits such acts in the U.S. Thus, the Court recommends denial of Defendant’s Motion as to Count I. B. Induced Infringement Under 35 U.S.C. §§ 271(b) & (f)(1) (Counts II and III) In Counts II and III, Plaintiff brings claims for induced infringement against both Defendants pursuant to 35 U.S.C. § 271(b) (“Section 271(b)”) and § (f)(1) (“Section 271(f)(1)”), respectively. (FAC at ¶¶ 31-49) Pursuant to Section 271(b), “[w]hoever actively induces infringement of a patent shall be liable as an infringer.”3 In order to prove induced infringement,

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

TriDiNetworks Ltd. v. NXP USA, Inc., (D. Del. 2020).

TriDiNetworks Ltd. v. NXP USA, Inc. (TriDiNetworks Ltd. v. NXP USA, Inc.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Lucent Technologies, Inc. v. Gateway, Inc.
580 F.3d 1301 (Federal Circuit, 2009)
Zoltek Corp. v. United States
672 F.3d 1309 (Federal Circuit, 2012)
Toshiba Corp. v. Imation Corp.
681 F.3d 1358 (Federal Circuit, 2012)
Fowler v. UPMC SHADYSIDE
578 F.3d 203 (Third Circuit, 2009)
R+L Carriers, Inc. v. DriverTech LLC
681 F.3d 1323 (Federal Circuit, 2012)
Sincavage v. Barnhart
171 F. App'x 924 (Third Circuit, 2006)
Henderson v. Carlson
812 F.2d 874 (Third Circuit, 1987)