Finjan, LLC v. Qualys Inc.

CourtDistrict Court, N.D. California
DecidedApril 5, 2021
Docket4:18-cv-07229
StatusUnknown

This text of Finjan, LLC v. Qualys Inc. (Finjan, LLC v. Qualys 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
Finjan, LLC v. Qualys Inc., (N.D. Cal. 2021).

Opinion

1 2 3 UNITED STATES DISTRICT COURT 4 NORTHERN DISTRICT OF CALIFORNIA 5 6 FINJAN, INC., CASE NO. 4:18-cv-07229-YGR

7 Plaintiff, ORDER GRANTING IN PART AND DENYING 8 vs. IN PART DEFENDANT’S MOTION TO STRIKE

9 QUALYS INC., Re: Dkt. No. 156, 157, 158, 163 10 Defendant.

11 12 Plaintiff Finjan, Inc. (“Finjan”) brings this patent infringement action against defendant 13 Qualys Inc. (“Qualys”) for direct and indirect infringement of its patents. Now before the Court is 14 Qualys’ motion strike certain portions of Finjan’s infringement and damages expert reports. (Dkt. 15 No. 158 (“Mot.”).) Qualys contends that Finjan’s expert, Dr. Nenad Medvidovic, introduced six 16 new theories in his report that were not disclosed in Finjan’s infringement contentions. Having 17 carefully considered the pleadings and the papers submitted,1 the Court GRANTS IN PART and 18 DENIES IN PART Qualys’ motion to strike. 19 I. BACKGROUND 20 Finjan accuses Qualys of infringing several patents, including U.S. Patent No. 8,225,408 21 (the “’408 Patent”). The ’408 Patent broadly relates to scanning content for “exploits” (security 22 vulnerabilities). (See ’408 Patent at 1:59-64.) It does so using a scanner that is specific to each 23 programming language and that includes rules to dynamically break down incoming content into 24 “tokens” and analyze patterns in those tokens. (See id. at 1:65-2:19.) Claim 1 recites:

25 1. A computer processor-based multi-lingual method for scanning incoming program code, 26 comprising: 27 receiving, by a computer, an incoming stream of program code; 1

2 determining, by the computer, any specific one of a plurality of programming languages in which the incoming stream is written; 3 instantiating, by the computer, a scanner for the specific programming language, 4 in response to said determining, the scanner comprising parser rules and analyzer rules for the specific programming language, wherein the parser rules define certain 5 patterns in terms of tokens, tokens being lexical constructs for the specific 6 programming language, and wherein the analyzer rules identify certain combinations of tokens and patterns as being indicators of potential exploits, 7 exploits being portions of program code that are malicious;

8 identifying, by the computer, individual tokens within the incoming stream;

9 dynamically building, by the computer while said receiving receives the incoming 10 stream, a parse tree whose nodes represent tokens and patterns in accordance with the parser rules; 11 dynamically detecting, by the computer while said dynamically building builds the 12 parse tree, combinations of nodes in the parse tree which are indicators of potential exploits, based on the analyzer rules; and 13

14 indicating, by the computer, the presence of potential exploits within the incoming stream, based on said dynamically detecting. 15 16 Finjan accuses the Qualys Cloud Platform, which comprises several interrelated products. 17 (Dkt. No. 1 (“Complaint”) ¶ 35; see Dkt. No. 164-3 (“Medvidovic Report”) ¶ 94.) Finjan served 18 its infringement contentions on April 19, 2019, describing generally how “each of the Accused 19 Products” meets the claim limitations. (Dkt. No. 158-6 (“Contentions”) at 2-18.) Fact discovery 20 closed on October 1, 2020, and the parties served their opening expert reports six weeks after that. 21 (Dkt. Nos. 39, 78.) Dr. Medvidovic and Dr. Eric Cole opined on infringement on behalf of Finjan. 22 (Medvidovic Report; Dkt. No. 158-3 (“Cole Report”).) Dr. DeForest McDuff opined on damages. 23 (Dkt. No. 158-4 (“McDuff Report”).) 24 II. LEGAL STANDARD 25 The Patent Local Rules “require parties to crystallize their theories of the case early in the 26 litigation and to adhere to those theories once they have been disclosed.” Simpson Strong-Tie Co., 27 Inc. v. Oz-Post Int’l, LLC, 411 F. Supp. 3d 975, 980-81 (N.D. Cal. 2019) (citation omitted). 1 “Accused Instrumentality” separately for each asserted claim, together with a chart “identifying 2 specifically where and how each limitation of each asserted claim is found within each Accused 3 Instrumentality.” Patent L.R. 3-1(b). Once these disclosures are made, they can only be amended 4 by Court order upon a showing of good cause. Patent L.R. 3-6. 5 The purpose of these rules is to “provide structure to discovery and to enable the parties to 6 move efficiently toward claim construction and the eventual resolution of their dispute.” Huawei 7 Techs., Co., Ltd v. Samsung Elecs. Co, Ltd., 340 F. Supp. 3d 934, 945 (N.D. Cal.2018) (citation 8 omitted). As such, “a party may not use an expert report to introduce new infringement theories, 9 new infringing instrumentalities, new invalidity theories, or new prior art references not disclosed 10 in the parties’ infringement contentions or invalidity contentions.” Looksmart Group, Inc. v. 11 Microsoft Corp., 386 F. Supp. 3d 1222, 1227 (N.D. Cal. 2019) (citation omitted). Undisclosed 12 theories “are barred . . . from presentation at trial (whether through expert opinion testimony or 13 otherwise).” MediaTek Inc. v. Freescale Semiconductor, Inc., No. 11-CV-5341-YGR, 2014 WL 14 690161, at *1 (N.D. Cal. Feb. 21, 2014). 15 A theory, however, is not the same as proof of that theory. Parties “need not ‘prove up’” 16 their case in contentions, and a patentee need only “provide reasonable notice to defendant why 17 [it] believes it has a reasonable chance of proving infringement.” Finjan, Inc. v. Blue Coat Sys., 18 Inc., No. 13-cv-03999-BLF, 2015 WL 3640694, at *2 (N.D. Cal. June 11, 2015) (citations and 19 quotation marks omitted). Courts thus distinguish “identification of the precise element of any 20 accused product alleged to practice a particular claim limitation” and “every evidentiary item of 21 proof showing that the accused element did in fact practice the limitation.” Genetech, Inc. v. Tr. of 22 Univ. of Penn., No. C 10-2037 LHK (PSG), 2012 WL 424985, at *1 (N.D. Cal. Feb. 9, 2012) 23 (citation and internal quotation marks omitted) (emphasis in original). In deciding whether to 24 strike expert testimony, the dispositive question is whether “the expert permissibly specified the 25 application of a disclosed theory” or “impermissibly substituted a new theory altogether.” Digital 26 Reg of Tex., LLC v. Adobe Sys. Inc., No. CV 12-01971-CW (KAW), 2014 WL 1653131, at *2 27 (N.D. Cal. Apr. 24, 2014) (citation omitted). 1 III. ANALYSIS 2 Finjan moves to strike six “theories” in Dr. Medvidovic’s report, including purportedly 3 new theories related to (1) the Cloud Agent, (2) dynamically building a parse tree and detecting 4 exploits, (3) receiving content, (4) date of first infringement, (5) doctrine of equivalents, and (6) 5 foreign sales.2 The Court addresses each. 6 A. Cloud Agents 7 Qualys first moves to strike Finjan’s Cloud Agent theories. According to Dr. Medvidovic, 8 the accused Qualys Cloud Platform collects data through either a scanner—a physical or virtual 9 appliance deployed on a network—or a Cloud Agent, which is an application that resides on the 10 endpoint itself (e.g., on a laptop). (Medvidovic Report ¶¶ 96-100.) Dr. Medvidovic opines that 11 both methods satisfy the limitations of “scanning incoming code” and “receiving, by a computer, 12 an incoming stream of program code.” (Id. ¶¶ 183, 185, 187 & n.6, 195-96.) 13 In addition, Dr. Medvidovic opines that the Cloud Agent provides alternatives methods for 14 performing other steps, including determining a programming language (¶ 214), applying analyzer 15 rules (¶¶ 235-38), identifying individual tokens (¶ 258), dynamically building a parse tree (¶¶ 287- 16 89), dynamically detecting exploits (¶¶ 303-09), and indicating the presence of the exploit (¶¶ 325, 17 327).

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

Related

Huawei Techs., Co. v. Samsung Elecs. Co.
340 F. Supp. 3d 934 (N.D. California, 2018)
Looksmart Grp., Inc. v. Microsoft Corp.
386 F. Supp. 3d 1222 (N.D. California, 2019)

Cite This Page — Counsel Stack

Bluebook (online)
Finjan, LLC v. Qualys Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/finjan-llc-v-qualys-inc-cand-2021.