throbber
Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 1 of 7
`
`Juanita R. Brooks (CA SBN 75934) brooks@fr.com
`Roger A. Denning (CA SBN 228998) denning@fr.com
`Jason W. Wolff (CA SBN 215819) wolff@fr.com
`John-Paul Fryckman (CA 317591) fryckman@fr.com
`K. Nicole Williams (CA291900) nwilliams@fr.com
`FISH & RICHARDSON P.C.
`12860 El Camino Real, Ste. 400
`San Diego, CA 92130
`Telephone: (858) 678-5070 / Fax: (858) 678-5099
`
`Proshanto Mukherji (Pro Hac Vice) mukherji@fr.com
`FISH & RICHARDSON P.C.
`One Marina Park Drive
`Boston, MA 02210
`Phone: (617) 542-5070/ Fax: (617) 542-5906
`Robert Courtney (CA SBN 248392) courtney@fr.com
`FISH & RICHARDSON P.C.
`3200 RBC Plaza
`60 South Sixth Street
`Minneapolis, MN 55402
`Phone: (612) 335-5070 / Fax: (612) 288-9696
`
`Attorneys for Plaintiff
`FINJAN LLC
`
`UNITED STATES DISTRICT COURT
`NORTHERN DISTRICT OF CALIFORNIA
`(SAN JOSE DIVISION)
`FINJAN LLC., a Delaware Limited Liability
`Case No. 5:17-cv-04467-BLF (VKD)
`Company,
`
`Plaintiff,
`
`v.
`
`SONICWALL, INC., a Delaware Corporation,
`
`Defendant.
`
`PLAINTIFF FINJAN LLC’S MOTION IN
`LIMINE NO. 3 TO PRECLUDE
`ARGUMENT THAT SONICWALL IS NOT
`SUCCESSOR-IN-INTEREST TO DELL
`
`Date: March 18, 2021
`Time: 1:30 PM
`Hon. Beth Labson Freeman
`Ctrm: 3, 5th Floor
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`Case No. 17-cv-04467-BLF (VKD)
` FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`1 2 3 4 5 6 7 8 9
`
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`
`

`

`Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 2 of 7
`
`
`
`I.
`
`INTRODUCTION
`
`Pursuant to Federal Rules of Evidence 401, 402, 403, and 611, Finjan LLC (“Finjan”)
`
`respectfully requests that the Court exclude from presentation to the jury at trial any argument by
`
`SonicWall, or evidence purporting to relate thereto, that actual notice of Finjan’s infringement
`
`claims, conveyed to SonicWall’s prior owner Dell, does not relate to SonicWall.
`
`II.
`
`ARGUMENT
`
`In pre-trial correspondence, SonicWall attempted to unveil a new defense, never before
`
`presented—or preserved—in any part of the case to date. SonicWall suddenly argued that
`
`Finjan’s pre-suit notice of infringement, conveyed to SonicWall’s then-parent Dell, did not apply
`
`to SonicWall. This argument appears in neither SonicWall’s damages contentions, nor in its
`
`interrogatory responses specifically addressing notice. It is forfeit. It is also meritless.
`
`A.
`
`SonicWall’s Statements in its Answer, Written Discovery, and Damages
`
`Contentions Forfeit Argument That SonicWall Did Not Inherit Notice
`
`At the start of the period for which Finjan seeks damages, SonicWall was owned by Dell.
`
`It is undisputed that Finjan and Dell communicated about SonicWall, and how its activities related
`
`to Finjan’s patents, during the period of Dell’s ownership, starting no later than 2014. In 2016,
`
`Dell divested SonicWall in 2016 to a private equity firm, but nothing about that transaction
`
`suggests that it transformed SonicWall from being on notice of infringement (via its parent Dell)
`
`into one suddenly unaware of Finjan’s claims.
`
`For most of this case, even SonicWall did not make such a contention. Its Amended
`
`Answer, specifically discussing the correspondence between Finjan and Dell relating to
`
`SonicWall’s infringement, repeatedly called Dell SonicWall’s “predecessor-in-interest,” and far
`
`from claiming ignorance, discussed the content of the Finjan-Dell interactions in detail. D.I. 103
`
`at ¶¶ 39. Nowhere did the Amended Answer allege, or even suggest, that SonicWall might not
`
`have Dell’s notice imputed to it.
`
`
`1
`
`Case No. 17-cv-04467-BLF (VKD)
`FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`25
`
`

`

`Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 3 of 7
`
`
`
`
`SonicWall also did not suggest it was not Dell’s successor for notice purposes when
`
`responding to written discovery specifically directed to the issue. Finjan’s very first interrogatory
`
`to SonicWall, served nearly three years ago, sought the details of SonicWall’s first awareness of
`
`Finjan’s patents. Exh. 13 at 3 (Interrogatory No. 1 (“Describe in detail when and under what
`
`circumstances You first became aware of the existence of the Asserted Patents . . . .”).) Far from
`
`contending that SonicWall would not have patent-related interactions with Dell imputed to it,
`
`SonicWall’s response (supplemented several times) specifically invoked the negotiations between
`
`Finjan and Dell, and identified Dell as SonicWall’s “predecessor-in-interest.” Exh. 13 at 4.
`
`SonicWall’s interrogatory response went on to describe how Finjan communicated with Dell
`
`about its patents and infringement theories, including concerning SonicWall. In general,
`
`SonicWall’s interrogatory response (like its other discovery responses) treated Finjan-Dell
`
`correspondence relating to SonicWall as imputed to SonicWall. Id. at 4–5. In a supplemental
`
`response, SonicWall went further, describing awareness by Dell of other Finjan-filed lawsuits as
`
`bearing on SonicWall’s awareness of the patents. Id. at 5. And in a second supplemental
`
`response, SonicWall identified a Dell employee as a knowledgeable person about the subject
`
`matter of the interrogatory. At no point in this or any other interrogatory response did SonicWall
`
`suggest that it did not inherit Dell’s awareness of Finjan’s patents and claims.
`
`A similar story is in the parties’ damages contentions. Finjan’s damages contentions
`
`alleged damages during the period of SonicWall’s ownership by Dell. Exh. 14 at 4. Further, the
`
`contentions directed SonicWall to Finjan-Dell correspondence as reflecting “prior correspondence
`
`between the parties” relevant to damages. Id. at 10. SonicWall’s responsive contentions did not
`
`mention, in any way whatsoever, any theory that notice of infringement to Dell might not be
`
`imputed to SonicWall. Exh. 15. To the contrary, SonicWall’s contentions referred to pre-suit
`
`correspondence about the patents as “pre-suit communications between Finjan and SonicWall,”
`
`drawing no distinction even though some were formally between Finjan and Dell. Indeed, the
`
`2
`Case No. 17-cv-04467-BLF (VKD)
`FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`25
`
`

`

`Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 4 of 7
`
`
`
`only mention of Dell at all was to note that some Dell-Finjan exchanges were marked under Rule
`
`408 (irrelevant to the notice issue). Id. at 13.
`
`Still further, when Finjan argued during summary judgment that SonicWall “does not
`
`dispute—because it cannot—that Finjan expressly brought [its] patents to the attention of
`
`SonicWall’s predecessor Dell in mid-2014,” D.I. 326 at 21, SonicWall did not dispute the issue. It
`
`certainly did not dispute that Dell was SonicWall’s “predecessor,” or that notice to Dell would be
`
`imputed to it. See D.I. 335-3 at 13 et seq.
`
`The only hint, during literal years of discovery, of SonicWall disputing inherited notice
`
`was when SonicWall unaccountably refused Requests for Admission on the subject. But even
`
`then, SonicWall’s refusal was conclusory and unaccompanied by any cognizable evidence. See
`
`generally D.I. 276. While Magistrate Judge DeMarchi denied Finjan’s request to impose an
`
`admission on SonicWall, in no sense did she endorse the idea that SonicWall, by corporate
`
`restructuring, divested itself of § 287 notice. See D.I. 281. No evidence of SonicWall avoiding
`
`inheriting notice was tendered to her, or to Finjan, at any point then, or since.
`
`B.
`
`SonicWall Has Forfeited Argument That It Is Not Dell’s Successor for Notice
`
`In this Court and others, it is well established that failure to timely raise an issue before
`
`trial forfeits the issue at trial. E.g., GPNE Corp. v. Apple, Inc., No. 12-CV-02885-LHK, 2014 WL
`
`3870256, at *5 (N.D. Cal. Aug. 6, 2014) (finding waiver where argument raised only extremely
`
`late). Here, though specifically called by Finjan to address notice under the patents-in-suit several
`
`times, SonicWall never contended, in any sense, that it would not inherit whatever notice had been
`
`given to Dell. Crucially, this included SonicWall’s total failure to raise the issue in damages
`
`contentions, despite Finjan plainly indicating that its damages theory would revolve, in part, on
`
`notice conveyed to Dell. Cf. Finjan, Inc. v. Cisco Systems, Inc., No. 17-cv-00072-BLF, 2019 WL
`
`6174936, at *5 (N.D. Cal. Nov. 20, 2019) (noting that attempts to make arguments not in damages
`
`contentions are appropriate for a motion in limine). Compounded with SonicWall’s decision not
`
`3
`Case No. 17-cv-04467-BLF (VKD)
`FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`25
`
`

`

`Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 5 of 7
`
`
`
`to raise this issue in its Amended Answer, or in its interrogatory responses, nor even to dispute it
`
`when raised by Finjan in summary judgment briefing, it would be profoundly unfair for SonicWall
`
`to inject this new defense into the case during the immediate run-up to trial.
`
`The prejudice to Finjan is plain. During pleadings SonicWall specifically admitted that
`
`Dell was its “predecessor-in-interest.” It failed to dispute inherited notice in damages contentions,
`
`or in interrogatory responses. Additionally, injection of this issue before the jury would have no
`
`practical value except to engender confusion and wastage.
`
`Finally, even had SonicWall not forfeited dispute that it inherited Finjan’s § 287 notice to
`
`Dell, and even were SonicWall permitted to evade its discovery responses confirming Dell as its
`
`“predecessor” for notice purposes, the dispute is meritless. At the time of notice, SonicWall was
`
`wholly controlled Dell and bound by Dell’s negotiation with Finjan, including for notice purposes,
`
`both as an aspect of Dell’s ownership and under the doctrine of apparent agency. This alone
`
`would be sufficient for Finjan’s § 287 notice to relate to SonicWall. Still further, the record shows
`
`that Dell, when it spun SonicWall out, specifically
`
` as part of
`
`the deal. See Exh. 16 at 102 (disclosing, in detail, exchanges between Finjan and Dell).
`
`Additionally, John Gmuender, SonicWall’s CTO during its ownership by Dell and still its CTO
`
`today,
`
`. Exh. 17 at 240:1–18. And more,
`
`when Finjan asked Mr. Gmuender if he had evaluated Finjan’s claims before the spin-out, Mr.
`
`Gmuender refused to answer after a privilege instruction from SonicWall’s counsel. Id. at 241:2–
`
`22. It would be inappropriate and unfair for SonicWall, after specifically blocking inquiry into its
`
`top technology executive’s knowledge of Finjan’s claims, to now be permitted to contend
`
`SonicWall lacked actual notice.
`
`It is unfair and prejudicial for SonicWall to litigate for three years referring to Dell as its
`
`“predecessor-in-direction,” then flip direction after discovery is closed and attempt to tell the jury
`
`
`
`4
`
`Case No. 17-cv-04467-BLF (VKD)
`FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`25
`
`

`

`Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 6 of 7
`
`
`
`the opposite, all while ignoring clear evidence squarely undermining that position. The Court
`
`should preclude this late-rising and meritless argument.
`
`Dated: March 4, 2021
`
`
`
`Respectfully Submitted,
`
`By: /s/ Robert Courtney
`Juanita R. Brooks (CA SBN 75934)
`brooks@fr.com
`Roger A. Denning (CA SBN 228998)
`denning@fr.com
`Jason W. Wolff (CA SBN 215819)
`wolff@fr.com
`John-Paul Fryckman (CA 317591)
`fryckman@fr.com
`K. Nicole Williams (CA 291900)
`nwilliams@fr.com
`FISH & RICHARDSON P.C.
`12860 El Camino Real, Ste. 400
`San Diego, CA 92130
`Phone: (858) 678-5070 / Fax: (858) 678-5099
`
`Proshanto Mukherji (Pro Hac Vice)
`mukherji@fr.com
`FISH & RICHARDSON P.C.
`One Marina Park Drive
`Boston, MA 02210
`Phone: (617) 542-5070/ Fax: (617) 542-5906
`
`Robert Courtney (CA SNB 248392)
`courtney@fr.com
`FISH & RICHARDSON P.C.
`3200 RBC Plaza
`60 South Sixth Street
`Minneapolis, MN 55402
`Phone: (612) 335-5070 / Fax: (612) 288-9696
`
`Attorneys for Plaintiff
`FINJAN LLC
`
`
`
`
`
`
`
`5
`
`Case No. 17-cv-04467-BLF (VKD)
`FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`25
`
`

`

`Case 5:17-cv-04467-BLF Document 368 Filed 03/04/21 Page 7 of 7
`
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a true and correct copy of the above and foregoing
`
`document has been served on March 4, 2021 to all counsel of record who are deemed to have
`
`consented to electronic service via the Court’s CM/ECF system. Any other counsel of record will
`
`be served by electronic mail and regular mail.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Robert Courtney
`Robert Courtney
`courtney@fr.com
`
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`25
`
`
`
`6
`
`Case No. 17-cv-04467-BLF (VKD)
`FINJAN LLC’S MOTION IN LIMINE NO. 3
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket