VLSI Technology LLC v. Intel Corporation

1

2

3 UNITED STATES DISTRICT COURT

4 NORTHERN DISTRICT OF CALIFORNIA

5 SAN JOSE DIVISION

6

7 VLSI TECHNOLOGY LLC, Case No. 17-cv-05671-BLF

8 Plaintiff,

ORDER GRANTING MOTION FOR

9 v. LEAVE TO AMEND ANSWER

10 INTEL CORPORATION, [Re: ECF No. 809]

11 Defendant.

12

13 On December 4, 2023, the Federal Circuit reversed a Texas district court’s denial of Intel

14 Corporation’s (“Intel”) motion for leave to amend its answer to add a defense that it is licensed to

15 use VLSI Technology LLC’s (“VLSI”) patents. VLSI Tech. LLC v. Intel Corp., 87 F.4th 1332,

16 1351 (Fed. Cir. 2023). Before the Court is a motion for leave to amend involving the same parties

17 and the same license in a separate case. Intel has filed a Motion for Leave to File a Second

18 Amended Answer, Defenses, and Counterclaims. ECF No. 809 (“Mot.”); ECF No. 827

19 (“Reply”). Intel seeks to amend its counterclaims to add a license counterclaim, which the parties

20 have litigated in this Court for over two years as an affirmative defense. See ECF No. 809-1

21 ¶¶ 87–118. VLSI opposes the motion. ECF No. 822 (“Opp.”).

22 The Court finds the motion suitable for disposition without a hearing. See Civ. L.R. 7-

23 1(b). For the reasons discussed below, the Court GRANTS Intel’s motion.

24 I. BACKGROUND

25 On October 2, 2017, VLSI brought this action—its first of several lawsuits against Intel—

26 asserting that Intel products infringe eight of its patents. ECF No. 1. In its “Amended Answer,

27 Defenses, and Counterclaims,” filed on December 21, 2021, Intel alleged as its seventh affirmative

1 liability with respect to all patents asserted in VLSI’s Complaint.” ECF No. 334 ¶ 145.

2 The parties proceeded through IPR and later full discovery in this action, after which four

3 patents remained at summary judgment: U.S. Patent No. 8,566,836 (“’836 Patent”), U.S. Patent

4 No. 8,004,922 (“’922 Patent”), U.S. Patent No. 7,675,806 (“’806 Patent”), and U.S. Patent No.

5 8,268,672 (“’672 Patent”). On December 7, 2023, the Court granted summary judgment that Intel

6 does not infringe the asserted claims of the ’836 and ’922 Patents and that the ’922 Patent is

7 invalid, but denied Intel’s motion for summary judgment that Intel does not infringe the asserted

8 claims of the ’806 and ’672 Patents. ECF No. 772 at 55. In a supplemental order issued after the

9 Federal Circuit’s ruling in VLSI Tech., 87 F.4th 1332, the Court denied Intel and VLSI’s cross

10 motions for summary judgment on Intel’s license defense and determined that the defense was

11 legally valid but that disputed factual issues should be decided at trial based on the narrow

12 question of whether VLSI and certain Finjan entities are under common control of Fortress

13 Investment Group. ECF No. 781 at 16–17. At a hearing on January 4, 2024, previously scheduled

14 for argument on the parties’ Daubert motions pertaining to the ’806 and ’672 Patents, VLSI

15 advised the Court that it would not be proceeding on its claims regarding the remaining patents

16 and shortly thereafter, VLSI granted Intel an “unconditional covenant not to sue as to the ’806 and

17 ’672 Patents” and dismissed all claims relating to those two patents. ECF No. 798-2 at 2; ECF

18 No. 801. At the January 4, 2024 hearing, the Court questioned whether “trial can go forward on

19 the licensing defense” for the ’836 and ’922 Patents, and requested further briefing. ECF No. 797

20 (“Hrg. Tr.”) at 27:22–25. After briefing, the Court found it lacked jurisdiction, ruling that “Intel

21 cannot proceed to trial on its affirmative defense that it is licensed to use the ’836 and ’922

22 Patents” because no live claims remained before the Court. ECF No. 807 at 8. Two days later,

23 Intel filed the instant motion to amend. Trial is set to begin on March 25, 2024, less than two

24 months from now.

25 II. LEGAL STANDARD

26 The Federal Circuit applies “regional circuit law when reviewing a district court’s decision

27 regarding motions for leave to file an amended complaint.” Healthier Choices Mgmt. Corp. v.

1 In the Ninth Circuit, a party seeking to amend a scheduling order must show “good cause”

2 for such relief. Fed. R. Civ. P. 16(b)(4) (“A schedule may be modified only for good cause and

3 with the judge’s consent.”). District court judges are guided by the following principles in

4 exercising their discretion under Rule 16. The Ninth Circuit teaches that “[o]nce the district court

5 ha[s] filed a pretrial scheduling order pursuant to Federal Rule of Civil Procedure 16 which

6 established a timetable for amending pleadings[,] that rule’s standards control[ ].” Johnson v.

7 Mammoth Recreations, Inc., 975 F.2d 604, 607–08 (9th Cir. 1992). “The district court ‘is given

8 broad discretion in supervising the pretrial phase of litigation, and its decisions regarding the

9 preclusive effect of a pretrial order . . . will not be disturbed unless they evidence a clear abuse of

10 discretion.’” C.F. ex rel. Farnan v. Capistrano Unified Sch. Dist., 654 F.3d 975, 984 (9th Cir.

11 2011) (quoting Johnson, 975 F.2d at 607).

12 A Rule 16 “good cause” analysis “is not coextensive with an inquiry into the propriety of

13 the amendment under . . . Rule 15.” Johnson, 975 F.2d at 609. “Unlike Rule 15(a)’s liberal

14 amendment policy . . . , Rule 16(b)’s ‘good cause’ standard primarily considers the diligence of

15 the party seeking the amendment.” Id. Courts may take into account any resulting prejudice to

16 the opposing party, but “the focus of the [Rule 16(b)] inquiry is upon the moving party’s reasons

17 for seeking modification . . . [i]f that party was not diligent, the inquiry should end.” In re W.

18 States Wholesale Nat. Gas Antitrust Litig., 715 F.3d 716, 737 (9th Cir. 2013), aff’d sub nom.

19 Oneok, Inc. v. Learjet, Inc., 135 S. Ct. 1591 (2015) (quoting Johnson, 975 F.2d at 609).

20 If the moving party establishes “good cause” to modify the scheduling order, “it must then

21 demonstrate that its motion is also proper under Rule 15.” Rodarte v. Alameda Cnty., No. 14-cv-

22 00468-KAW, 2015 WL 5440788, at *2 (N.D. Cal. Sept. 15, 2015) (citing Johnson, 975 F.2d at

23 608). Under Rule 15(a), a party may amend its pleading once as a matter of course within 21 days

24 of serving it. Fed. R. Civ. P. 15(a)(1). Further amendment of the pleadings is allowed with the

25 opposing party’s consent or leave of the court. Fed. R. Civ. P. 15(a)(2). The factors considered

26 when determining whether to grant leave to amend include: “(1) bad faith on the part of the

27 movant; (2) undue delay; (3) prejudice to the opposing party; and (4) futility of the proposed

1 (N.D. Cal. Dec. 15, 2010) (citing Foman v. Davis, 371 U.S. 178, 182 (1962)). “This policy is to

2 be applied with extreme liberality.” Farnan, 654 F.3d at 985 (quoting Eminence Cap., LLC v.

3 Aspeon, Inc., 316 F.3d 1048, 1051 (9th Cir. 2003)). “Absent prejudice, or a strong showing of any

4 of the remaining [Foman] factors, there exists a presumption under Rule 15(a) in favor of granting

5 leave to amend.” Ibid.

6 III. DISCUSSION

7 Two issues are before the Court: (1) whether Intel has shown good cause to amend the

8 scheduling order under Rule 16 and (2) whether Intel has shown that its proposed amendment to

9 its Answer, Defenses, and Counterclaims is proper under Rule 15. The Court considers each issue

10 in turn.

11 A. Leave to Amend Scheduling Order Under Rule 16

12 As stated above, “Rule 16(b)’s ‘good cause’ standard primarily considers the diligence of

13 the party seeking the amendment.” Johnson, 975 F.2d at 609. “Although the existence or degree

14 of prejudice to the party opposing the modification might supply additional reasons to deny a

15 motion, the focus of the inquiry is upon the moving party’s reasons for seeking modification.” Id.

16 Intel argues that there is good cause to amend the case schedule because it sought leave of

17 the court to file the license issue as a counterclaim just two days after the Court ruled that Intel

18 could not proceed to trial on the license issue as an affirmative defense. Mot. at 5. Intel adds that

19 before VLSI dismissed the ’806 and ’672 Patents, “there was simply no need for such a

20 counterclaim.” Id. at 6.

21 VLSI responds that Intel was not diligent because Intel has known the underlying facts

22 supporting the license issue “at least as early as November 2020,” and yet decided not to plead it

23 as a counterclaim until now, over three years later. Opp. at 3–4. VLSI also argues that Intel

24 delayed amendment because the counterclaim is “improper.” Id. at 4. VLSI further argues that

25 any amendment would require additional discovery and would prejudice VLSI. Id. at 5–6.

26 The Court finds that Intel was diligent in seeking leave to amend. Although VLSI

27 correctly notes that trial is scheduled to begin less than two months from now and Intel has known

1 affirmative defense in 2021, ECF No. 334, and had no reason then to add a duplicative

2 counterclaim. The license issue remained live as an affirmative defense to alleged infringement of

3 the asserted patents throughout discovery and summary judgment until only weeks ago when

4 VLSI tactically chose to dismiss the remaining asserted patents, while preserving its appeal rights

5 on the ’836 and ’922 Patents, a move that ended the Court’s jurisdiction over any of Intel’s

6 affirmative defenses. See ECF Nos. 801, 807. Two days after the Court issued its order, Intel

7 moved to amend its answer. See ECF Nos. 807, 809. This timeline demonstrates that Intel moved

8 to amend its answer as soon as it was clear that amendment was necessary to continue to pursue

9 the license issue. On this record, the Court finds that dismissal of the license defense changed the

10 tenor of the case, and that event was the motivating factor behind Intel’s request. Further, the

11 Court finds that this amendment does not create any meaningful case management issues.

12 Furthermore, the Court finds that any prejudice to VLSI is minimal. Intel’s 2021 pleading

13 of the issue as an affirmative defense clearly placed VLSI on notice of the claim and provided

14 VLSI with the full opportunity to obtain discovery and develop its arguments to defeat the

15 substance of the license issue. To that point, the parties have already conducted discovery on the

16 substantive merits of the license issue, and the parties’ cross summary judgment motions reduced

17 the issue to the narrow factual question of whether Fortress controls VLSI and Finjan. ECF No.

18 781. Furthermore, any challenges by VLSI to the license issue not already addressed by the Court

19 are largely questions of law or based on the factual record already developed. Thus, the prejudice

20 to VLSI, if any, is minimal.

21 The Ninth Circuit’s Farnan decision further supports the Court’s finding. There, the

22 defendant moved under Rule 16 to add a qualified immunity defense after summary judgment.

23 Farnan, 654 F.3d at 982. The district court granted leave to amend, and the Ninth Circuit

24 affirmed, holding that the district court did not abuse its discretion in concluding that “the tenor of

25 the case changed significantly” when the district court issued its summary judgment ruling and

26 “that this event, rather than any bad faith or dilatory purpose, motivated [the defendant’s]

27 request[.]” Id. at 984. The court also found that the plaintiff was not prejudiced because “he was

1 defendant’s] behalf in their answer, long before the parties filed their motions for summary

2 judgment.” Id. at 985. Similarly, VLSI’s dismissal of the remaining asserted patents after

3 summary judgment changed the tenor of the instant matter. Regarding prejudice, the Court notes

4 that VLSI was on notice of the license defense for at least two years when Intel sought to bring it

5 as a counterclaim.

6 VLSI argues that Intel’s decision to wait until now to assert the license as a counterclaim is

7 “likely because” it would have been improper or “violated the agreement’s forum selection

8 clause.” Opp. at 3. Under the Rule 16 criterion, the Court finds that the substantive merit of the

9 claim is not relevant and concludes that the timing of the proposed amendment does not reflect

10 bad faith or dilatory purpose. Whether the proposed amendment is futile will be addressed under

11 Rule 15.

12 Additionally, VLSI argues that Intel “cannot satisfy Rule 16’s standard unless it can show

13 that it did not know the facts underlying the substance of the claim before the scheduling order’s

14 deadline.” Opp. at 3-4. But the cases VLSI relies on are distinguishable because in each case, the

15 moving party was unable to explain delays before amending. See, e.g., Kamal v. Eden Creamery,

16 LLC, 88 F.4th 1268, 1277 (9th Cir. 2023) (the plaintiffs “offer[ed] no explanation for why they

17 needed eight months to obtain [information] and move to amend the complaint”); Branch Banking

18 & Tr. Co. v. D.M.S.I., LLC, 871 F.3d 751, 765 (9th Cir. 2017) (the defendants offered no reason

19 for their delay); Sosa v. Airprint Sys., Inc., 133 F.3d 1417, 1419 (11th Cir. 1998) (moving party

20 “[did] not address good cause under Rule 16(b)”). Here, Intel’s proposed amendment is explained

21 by the recent change in the tenor of the case after summary judgment. And VLSI’s

22 characterization that Intel sat on the license for three years before deciding to plead it now ignores

23 that Intel pled the license two years ago as an affirmative defense.

24 VLSI also argues that just because “it is now strategically beneficial to assert its

25 affirmative defense as a counterclaim is no argument at all.” Opp. at 4 But VLSI’s arguments

26 that the move is strategic are purely speculative.

27 VLSI also argues that it is prejudiced because it agreed to dismiss its claims on the ’806

1 VLSI contends that Intel “had the opportunity at the January 4 hearing to state that it planned to

2 assert its affirmative defense as an independent claim,” but instead “made clear statements to the

3 contrary.” Id. at 5. VLSI claims that it “relied on these representations, and on the pleadings

4 being long closed, in providing a covenant not to sue.” Id. at 6. Although it is undisputed that the

5 pleadings were long since closed, the transcript of the January 4, 2024 hearing does not reveal any

6 “clear statements” or “representations” made by Intel regarding its intention to convert its license

7 defense into a license counterclaim. To the contrary, it was VLSI who first addressed the issue of

8 committing to dismiss its claims on the ’806 and ’672 Patents if it lost is appeal on the ’836 and

9 ’922 Patents. Hrg. Tr. 5:17–24. This proposal was made in support of VLSI’s request to stay the

10 case pending appeal. After Intel articulated its objection, VLSI further sweetened the pot by

11 committing to enter into a “rock solid” covenant not to sue with respect to the’806 and ’672

12 Patents. Id. 15:13–19, 21:9. VLSI committed to dismissing those claims. Id. 15:22–16:1.

13 Nothing in the transcript shows that Intel promised or even suggested it would only proceed on its

14 affirmative defense. To the extent that VLSI presumed Intel would not seek leave to amend to

15 convert the license dispute to a counterclaim, nothing in the record supports that speculation.

16 Accordingly, the Court finds under its broad discretion that Intel has shown good cause

17 under Rule 16 for leave to amend the scheduling order. Farnan, 654 F.3d at 984; Johnson, 975

18 F.2d at 607. By bringing a license counterclaim instead of a license affirmative defense, Intel’s

19 proposed amendment changes only the name of the dispute, not its substance.

20 B. Leave to Amend Complaint Under Rule 15(a)(2)

21 The remaining question before the Court is whether Intel has shown that amendment is

22 appropriate under Federal Rule of Civil Procedure 15(a)(2). The Court considers “(1) bad faith on

23 the part of the movant; (2) undue delay; (3) prejudice to the opposing party; and (4) futility of the

24 proposed amendment.” Ciampi, 2010 WL 5174013, at *2 (citing Foman, 371 U.S. at 182). The

25 Court addresses the Foman factors in turn.

26 1. Bad Faith

27 First, Intel argues that its proposed amendment is not in bad faith because it does not seek

1 VLSI responds that the proposed amendment “demonstrates bad faith under Rule 15,” is merely a

2 tactical attempt to “prolong the litigation before a Court which lacks subject matter jurisdiction,”

3 manufacture jurisdiction, and improperly rebrand an affirmative defense as a counterclaim. Opp.

4 at 6–8 (citations and quotations omitted, emphasis in original).

5 The Court agrees with Intel. “Bad faith in the context of a motion to amend a complaint to

6 add parties or claims typically involves the moving party’s efforts to prolong the litigation or

7 destroy diversity jurisdiction.” Narog v. City of Redwood City, No. C-13-03237 DMR, 2014 WL

8 3421166, at *3 (N.D. Cal. July 14, 2014) (collecting cases). VLSI does not argue that Intel’s

9 proposed amendment destroys diversity jurisdiction; to the contrary, VLSI claims the amendment

10 would not restore jurisdiction. To the extent that the proceedings may be prolonged, VLSI has

11 made no showing that any potential delays are unreasonable. See id.; Padilla v. Sears, Roebuck &

12 Co., No. 5:12-CV-00653 EJD, 2012 WL 5505071 at *2 (N.D. Cal. Nov. 13, 2012).

13 VLSI cites several cases for the proposition that Intel’s proposed amendment is an

14 improper attempt to manufacture jurisdiction and rebrand its affirmative defense. In Bonin v.

15 Calderon the court found that proposed amendments consisted of “theories [that] should have

16 been pleaded in his petition originally” or were “either duplicative of existing claims or patently

17 frivolous.” 59 F.3d 815, 846 (9th Cir. 1995). In Westwood v. Brott, the court dismissed

18 counterclaims that were wholly redundant of affirmative defenses. 2022 WL 17418975, at *4

19 (N.D. Cal. Dec. 5, 2022). Both cases are distinguishable. Here, Intel already advanced the license

20 issue as an affirmative defense in its Amended Answer, Defenses, and Counterclaims, ECF No.

21 334, and the license issue is not frivolous. See ECF No. 781. Furthermore, had Intel initially pled

22 both an affirmative defense and counterclaim, it might have been redundant, but that is no longer

23 the issue.

24 VLSI argues that Intel “is seeking this amendment for strategic advantage following an

25 adverse ruling.” Opp. at 9 (citing Acri v. Int’l Ass’n of Machinists & Aerospace Workers, 781

26 F.2d 1393 (9th Cir. 1986)). But Acri is distinguishable. There, the plaintiffs sought leave to

27 amend their complaint under Rule 15 to seek damages for emotional distress after oral argument

1 not abuse its discretion in denying leave to amend” where it found, inter alia, that the plaintiffs

2 delayed in bringing the claims “to avoid the possibility of an adverse summary judgment ruling.”

3 Id. at 1398–99. Unlike the plaintiffs in Acri, Intel did not seek to avoid adjudication of the merits

4 of the license issue; both parties brought motions for summary judgment on the license defense.

5 And to the extent VLSI seeks to argue that Intel is jurisdictionally and contractually barred from

6 litigating the license issue as a counterclaim, it may do so after Intel amends.

7 Finally, VLSI argues that the Texas court could resolve the license issue, Opp. at 7, but

8 that is not relevant to whether Intel’s proposed amendment is in good faith.

9 2. Undue Delay

10 Second, Intel argues that it did not unduly delay in seeking leave to amend because it did

11 so two days after the Court ordered that it could not proceed to trial on Intel’s affirmative

12 defenses. Mot. at 7. VLSI responds that Intel’s amendment “represents undue delay” because

13 Intel was dilatory and because trial is scheduled less than two months from now. Opp. at 7.

14 The Court finds no undue delay by Intel. As noted above, Intel diligently sought to amend

15 its answer to add the license counterclaim only two days after the Court found that Intel could not

16 proceed to trial with the license affirmative defense.

17 3. Prejudice

18 Third, Intel argues that VLSI is not prejudiced because the parties “license issue has been a

19 part of this case since Intel amended its answer in December 2021,” “the parties have completed

20 discovery in this action[,] and this Court has already resolved the parties’ cross motions for summary

21 judgment on the license defense.” Mot. at 7–8. VLSI responds that “a new claim, which implicates

22 the license’s forum selection clause, provides a compelling justification for discovery” and that the

23 additional discovery would prejudice VLSI. Opp. at 7–8 (emphasis in original).

24 The Court finds that any prejudice to VLSI is minimal. As noted above, the parties have

25 already conducted discovery and motion practice on the license issue. VLSI has not outlined what

26 kind of additional discovery would be required to enforce a forum selection clause, but the Court

27 has no reason to believe that additional discovery, if necessary, would be particularly burdensome.

1 motion to dismiss if VLSI wishes to file such a motion.

2 4. Futility

3 Finally, Intel argues that its proposed counterclaim is not futile because the Court retains

4 jurisdiction to resolve the license issue and ruled at summary judgment that there were triable

5 issues of fact. Mot. at 9. VLSI responds that Intel’s amendments are futile because 1) Intel’s

6 counterclaim does not create jurisdiction for the court, 2) the Court would be required to dismiss

7 or transfer the counterclaim, 3) declaratory judgment is inappropriate here, and 4) the Finjan

8 License itself prohibits a counterclaim. Opp. at 8–10.

9 VLSI’s arguments seem particularly ironic in light of the Federal Circuit’s very recent

10 reversal of an order denying leave to amend to add this very same license dispute as an affirmative

11 defense in VLSI Tech., 87 F.4th 1332. The Federal Circuit concluded that the finding of futility

12 was “wrong as a matter of law,” id. at 1351, and directed the matter to proceed on a fully

13 developed motion to dismiss. This Court takes guidance from the Federal Circuit, and on this

14 basis, finds that Intel’s proposed counterclaim is not futile.

15 To be more specific, VLSI’s four futility arguments fail at this juncture. First, VLSI

16 claims that the counterclaim does not create jurisdiction for the Court because it is redundant of

17 Intel’s affirmative defenses. Opp. at 8. Intel replies that the counterclaim “does not merely relate

18 to the ’836 and ’922 patents, but also to VLSI’s entire patent portfolio.” Reply at 1.

19 The Court agrees with Intel. As discussed above, Intel’s counterclaim seeks “declaratory

20 judgment that it is licensed to all patents owned by VLSI.” ECF No. 809-1 ¶ 118. Thus, it is not

21 redundant of Intel’s affirmative defenses.

22 Second, VLSI argues that amendment is futile because the Court would be required to stay,

23 dismiss, or transfer the counterclaim to Texas. Opp. at 8–9. Intel replies that this Court should

24 decide the license defense because discovery is further along here and that the instant action is the

25 “first action.” Reply at 2 (emphasis in original).

26 The Court finds that it is not clear at this stage that it would be required to stay, dismiss, or

27 transfer the counterclaim. “When two actions that sufficiently overlap are filed in different federal

1 action, if filed later, generally is to be stayed, dismissed, or transferred to the forum of the

2 infringement action.” Futurewei Techs., Inc. v. Acacia Rsch. Corp., 737 F.3d 704, 708 (Fed. Cir.

3 2013). “But the rule is not absolute; exceptions may be made if justified by ‘considerations of

4 judicial and litigant economy, and the just and effective disposition of disputes.’” Id. (quoting

5 Elecs. for Imaging, Inc. v. Coyle, 394 F.3d 1341, 1347 (Fed. Cir. 2005)). “Justification for an

6 exception may be found in ‘the convenience and availability of witnesses, [the] absence of

7 jurisdiction over all necessary or desirable parties, . . . the possibility of consolidation with related

8 litigation, or considerations relating to the real party in interest.’” Id. (quoting Genentech, Inc. v.

9 Eli Lilly & Co., 998 F.2d 931, 938 (Fed. Cir. 1993). “Application of the first-to-file rule is

10 generally a matter for a district court’s discretion, exercised within governing legal constraints.”

11 Id.

12 The Court notes, however, that in Futurewei, the infringement suit was filed first, and a

13 separate declaratory relief action was later filed in a different judicial district. The facts in this

14 case are quite dissimilar. Namely, VLSI brought the instant infringement action in this forum

15 before it brought any action in Texas. Thus, it is not clear at this stage that any Texas action is

16 “first-filed.” Even if the instant matter is a second-filed action, whether the case should be

17 transferred is “generally a matter for a district court’s discretion,” id., and the Court will not

18 prejudge at this stage whether or not the Futurewei exceptions apply. See VLSI Tech. LLC, 87

19 F.4th at 1351.

20 Third, VLSI argues that declaratory judgment is inappropriate here because the Texas

21 court is willing to resolve the license issue. VLSI argues that “Intel can and must litigate” the

22 license issue “in Texas, where the ‘relevant, substantive claims to which it directly relates are

23 being litigated.’” Opp. at 9–10 (quoting Futurewei, 737 F.3d at 710). Intel replies that the Court

24 should “reject VLSI’s attempt to wipe the slate clean and start over in Texas” because “no

25 discovery has occurred on the license issues in Texas, the mandate has not issued in one Texas

26 case, and there are post-trial motions still pending in the other.” Reply at 2.

27 As discussed above, the license counterclaim is not clearly futile on jurisdictional grounds,

1 Fourth and finally, VLSI argues that the plain language of the Finjan License bars Intel

2 || from bringing a counterclaim in this district. Opp. at 10. According to VLSI, “the Finjan License

3 || prohibits signatories from bringing claims ‘regarding this Agreement’ or ‘related to its

4 || performance’ outside of the ‘Court of Chancery of the State of Delaware . . . or the United States

5 || District Court for the District of Delaware.’” Id. (quoting ECF No. 579-17 (‘Finjan License”) §

6 11.4). VLSI also claims that the Finjan License “does not provide grounds for an independent

7 claim upon which this Court may base its jurisdiction.” Jd. VLSI also cites a motion to stay filed

8 || by Intel in the Texas matter, where Intel wrote that it “agreed that a party seeking to enforce the

9 Finjan License could commence litigation in one of two enumerated [Delaware] venues.” ECF

10 || No. 588-4 at 5.

11 Intel replies that the Finjan License provides that it

Reply at 2 (quoting Finjan License § 9.1). Intel argues that the language of

14 || the license provides that the license “may be pleaded as a not only to claims that □□□

2 15 || or GER but also to claims that and that the only way to

16 || do so is by “bringing a declaratory judgment counterclaim like the one Intel is asserting here.”

2 17 |] 2bid. (emphasis in original).

18 The Court finds that it is not clear from the plain language of the Finjan License that the

19 || license bars Intel from bringing the license issue as a counterclaim in this district such that

20 amendment is futile. Whether the Finjan License may be used for an independent counterclaim is

21 a matter of contract interpretation, and Intel’s counterclaim is not clearly meritless. This issue will

22 benefit from a more developed record. Furthermore, that Intel wrote under different

23 || circumstances in a motion before another court that it “could commence litigation” in Delaware

24 || does not bind it to commencing litigation only in Delaware. Finally, when the Chancery Court

25 declined to hear Intel’s license issue in September 2021, it wrote that Intel could pursue the license

26 || issue in a then-pending action in Delaware district court (that has since been dismissed), or before

27 this Court. Intel Corp. v. Fortress Investment Grp., 2021 WL 4470091, at *9 n.77 (Del. Ch. Ct.

28 || Sept. 30, 2021) (“it appears Intel may present its license defense in the first-filed forum, the

1 California Action”) (emphasis added). Thus, the court finds that the Chancery Court’s opinion

2 || does not clearly foreclose litigation here such that amendment would be futile.

3 While VLSI has briefed several possible deficiencies with Intel’s proposed counterclaim

4 || that may need to be explored further in subsequent briefing such as a motion to dismiss, none of

5 || its arguments convince the Court that Intel’s proposed counterclaim is futile.

6

7 Having found that all four Foman factors weigh in Intel’s favor, the Court finds in its

8 sound discretion to control its calendar, and with an eye to judicial efficiency, that amendment is

9 appropriate under Rule 15. Farnan, 654 F.3d at 985; Eminence, 316 F.3d at 1051.

10 The Court cannot fail to observe that the parties seem to be playing four-way chess that

11 includes their own tactical maneuvers and the related rulings of two federal district courts. What

12 || is clear is that this case was the earliest filed of the many VLSI-Intel disputes, VLSI chose to

5 13 || institute suit in the Northern District of California, and the parties have been actively litigating the

14 || license issue here for over two years, including lengthy summary judgment proceedings. In the

15 interests of judicial efficiency, leave to amend is granted.

16 || IV. ORDER

17 For the foregoing reasons, IT IS HEREBY ORDERED that Intel’s Motion for Leave to

Z 18 File a Second Amended Complaint is GRANTED. Intel SHALL file the amended answer

19 || immediately. VLSISHALL respond to the amended answer within 14 days of the date of this

20 || order. If a motion to dismiss is filed, the Court sua sponte shortens time for Intel’s response to

21 seven days, and VLSI shall have seven days to file a reply.

22

23 Dated: February 9, 2024

TH LABSON FREEMAN

25 United States District Judge

26

27

28