Finjan, Inc. v. ESET, LLC et al

Filing 195

Claim Construction Order. Signed by Judge Cathy Ann Bencivengo on 11/14/2017. (Attachments: # 1 Attachment A)(jjg)

Download PDF
1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 FINJAN, INC., Case No.: 3:17-cv-0183-CAB-(BGS) Plaintiff, 12 13 v. 14 CLAIM CONSTRUCTION ORDER ESET, LLC, a California Limited Liability and ESET SPOL. S.R.O., a Slovak Republic Corporation, 15 16 Defendants. 17 18 On September 25 and 26, 2017, the Court held a hearing to construe certain terms 19 and phrases of the following patents: U.S. Patent Nos. 6,154,844; 6,804,780; 8,079,086; 20 9,189,621; 9,219,755; and 7,975,305. The parties submitted briefing in accordance with 21 this District’s local patent rules and the case management order. A tutorial was presented 22 by both sides to assist the Court with the history and background of the patents. 23 The Court requested further briefing regarding certain terms. Having now 24 considered all the submissions of the parties, the arguments of counsel and for the reasons 25 set forth at the hearing and herein, the Court hereby enters the claim constructions set 26 forth below. 27 28 1 3:17-cv-0183-CAB-(BGS) 1 2 A. “Downloadable” in U.S. Patent Nos. 6,154,844; 6,804,780; 8,079,086; 9,189,621 and 9,219,755 3 The parties seek construction of the term Downloadable as it is used in five of the 4 patents at issue. This claim term can be traced through two branches of the family tree of 5 this patent (see Attachment A) with somewhat differing definitions. The Court however 6 concludes that the variations between the definitions can be reconciled and the 7 specifications in their entirety give notice of what is encompassed by the claim term 8 Downloadable to one of skill in the art. 9 Downloadable initially appears as a defined term in the specification of the 10 6,167,520 patent, and its continuation the 6,480,962 patent, as a small executable or 11 interpretable application program which is downloaded from a source computer and run 12 on a destination computer. 13 The specification of the 6,092,194 patent, and its continuation the ‘780 patent (which 14 is at issue in this litigation), define Downloadable as an executable application program 15 which is downloadable from a source computer and run on the destination computer. The 16 specification however provides as examples of a Downloadable, application programs 17 such as Java™ applets, known as little application programs in machine language, and 18 JavaScripts™ scripts, an interpretable application program. These examples are in accord 19 with the definition, incorporated by reference, set forth in the ‘520 patent. The ‘194 patent 20 and its progeny therefore conform to the ‘520 patent’s definition of Downloadable as small 21 executable or interpretable application programs through the use of the examples in the 22 specifications. The Court finds that one of skill in the art would be able to ascertain what 23 is claimed as a Downloadable in the context of these patents, and that in light of the 24 examples provided in the ‘194 patent specification, concludes that the meaning of 25 Downloadable is consistent with the definition provided in the ‘520 patent. 26 The ‘844 patent (which is at issue in this litigation) defines Downloadable as an 27 executable application program which is downloadable from a source computer and run 28 on the destination computer and also includes references to small executable and 2 3:17-cv-0183-CAB-(BGS) 1 interpretable application programs as examples of a Downloadable. The ‘844 patent 2 incorporates by reference the ‘520 patent and ‘194 patent. The Court finds that the 3 definition of Downloadable based on the ‘844 patent specification, the examples provided 4 therein and the incorporation of the ‘520 patent and the ‘194 patent, informs one of skill in 5 the art with reasonable certainty the scope of the invention. 6 specification’s description would inform that Downloadable includes executable and 7 interpretable application programs, in accordance with the examples and incorporated 8 references. The entirety of the 9 The ‘822 patent is a Continuation in Part of both the ‘962 patent and ‘780 patent and 10 incorporates those patents by reference. Its continuation patents, including the ‘086 patent, 11 ‘621 patent and ‘755 patent, which are at issue in this litigation, do not include a definition 12 of Downloadable in the specification but incorporate by reference the ’962 patent and the 13 ‘780 patent, and their definitions and examples of a Downloadable. 14 The Court finds that the two branches of the family tree of the patents at issue inform 15 that a Downloadable in the context of these patents means a small executable or 16 interpretable application program which is downloaded from a source computer and run 17 on a destination computer. This construction comports with the plain definition set forth 18 in the ‘520 patent and the ‘962 patent, and is supported by the written description including 19 the definition and the examples set forth in the ‘194 patent and its progeny, and in the 20 entirety of specification of the ‘844 patent. 21 The Court therefore construes the term Downloadable in all five patents as a small 22 executable or interpretable application program which is downloaded from a source 23 computer and run on a destination computer. 24 25 26 27 28 3 3:17-cv-0183-CAB-(BGS) 1 2 B. U.S. Patent No. 6,154,844 The parties sought construction of the following phrase appearing in various claims of 3 the ‘844 patent: before the web server makes the Downloadable available to web 4 clients. The Court’s construction for this term is: Before the Downloadable is available 5 on a web server to be called up or forwarded to a web client. (‘844 @ Col. 3:32-52; Col. 6 7 8 9 10 11 12 13 14 4:65 - Col. 5:13; Figure 1.) C. U.S. Patent No. 6,804,780 The parties sought construction of the following terms and phrases appearing in various claims of the ‘780 patent. The Court’s constructions for these terms are: Claim Term COURT’S CONSTRUCTION software components components of code that the Downloadable is required to be executed required to execute by the Downloadable (agreed construction) ID generator Defendant’s request for application of 112 ¶6 denied. 15 “ID generator” is not a nonce term as advocated by 16 Defendant. It is a common name for a known 17 program construct that would be familiar to one of 18 skill in the art to perform a function further identified 19 20 21 22 23 24 25 by its modifier. performing a hashing performing a hashing function on the function on the Downloadable together with its fetched software Downloadable and the components fetched software (Adopting PTO Construction from the IPR of the components to generate a ‘780 patent April, 2016.) Downloadable ID 26 27 28 4 3:17-cv-0183-CAB-(BGS) 1 D. U.S. Patent No. 7,975,305 2 The parties sought construction of the following phrase appearing in various claims 3 of the ‘305 patent, network interface, housed within a computer. Defendant’s proposed 4 construction that “housed within a computer” necessarily limits the structure of the network 5 interface to a hardware component is declined. The specification includes software 6 interface examples. The Court therefore finds in the context of the patent, the use of 7 “housed” in contrast to “stored” does not dictate that the claim be limited to hardware 8 components. To the extent clarification is required the Court construes this phrase as 9 network interface, contained within the computer. 10 The parties agreed construction for database, a collection of interrelated data 11 organized according to a database schema to serve one or more applications, is adopted. 12 13 14 E. U.S. Patent No. 8,079,086 The parties sought construction of the following terms appearing in various claims of the ‘086 patent. The Court’s constructions for these terms are: 15 Claim Term COURT’S CONSTRUCTION 16 appended Downloadable a Downloadable with a representation of the 17 DSP data attached to the end of the 18 Downloadable 19 Declaration of Dr. Spafford, ¶¶36-39, and 20 references cited therein, that one skilled in the 21 art at the time would understand “append” to 22 mean attach or add to the end of the existing file. 23 The claim recites appending a representations of 24 the DSP data to the Downloadable indicating an 25 order. 26 27 destination computer Separate computer receiving the appended Downloadable 28 5 3:17-cv-0183-CAB-(BGS) 1 file appender Defendant’s request for application of 112 ¶ 6 is 2 denied. “File appender” is not a nonce term as 3 advocated by Defendant. It is a common name 4 for a known program construct that would be 5 familiar to one of skill in the art to perform a 6 function further identified by its modifier. 7 Transmitter Defendant’s request for application of 112 ¶ 6 is 8 denied. “Transmitter” is not a nonce term as 9 advocated by Defendant. It a common name for 10 a known program construct that would be 11 familiar to one of skill in the art. 12 13 14 15 F. U.S. Patent No. 9,189,621 The parties sought construction of the following terms appearing in various claims of the ‘621 patent. The Court’s constructions for these terms are: 16 Claim Term COURT’S CONSTRUCTION 17 wherein the information Defendant asserts that this phrase in indefinite as 18 pertaining to the it is not possible to ascertain the meaning of 19 downloadable includes “information pertaining to the operation of the 20 information pertaining to downloadable that is distinct from information 21 operation of the pertaining to the request.” The Court finds that 22 downloadable and distinct in the context of the claim in its entirety and for 23 from information pertaining the reasons set forth on the record, one of skill in 24 to the request the art would understand the meaning and scope 25 of this claim language, and no further 26 construction is needed. 27 a response engine for Defendant asserts that use of “response engine” 28 performing a predetermined is the equivalent of “means for” claiming and is 6 3:17-cv-0183-CAB-(BGS) 1 responsive action based on limited to the structures disclosed in the ‘520 2 the comparison Patent at Figs. 5 and 6, Steps 525, 530, 540 and 3 610-30. Plaintiff asserts that “engine” is a 4 common name for a known program construct 5 that would be familiar to one of skill in the art to 6 perform a function further identified by its 7 modifier, in this case “response.” The Court 8 agrees that “engine” is not a nonce term as 9 advocated by Defendant, and that the claim 10 provides sufficient structure for one skilled in 11 the art. 12 Defendant’s request for application of 112 ¶ 6 is 13 denied. 14 a response engine for Defendant asserts that “response engine” is the 15 performing a predetermined equivalent of “means for” claiming and no 16 responsive action based on structure to perform this function is disclosed. 17 the comparison with the Plaintiff asserts that “engine” is a common name 18 information pertaining to the for a known program construct that would be 19 predetermined suspicious familiar to one of skill in the art to perform a 20 downloadable function further identified by its modifier, in this 21 case “response.” “Engine” is not a nonce term. 22 Defendant’s request for application of 112 ¶ 6 is 23 denied. 24 Database a collection of interrelated data organized 25 according to a database schema to serve one or 26 more applications 27 (joint construction) 28 7 3:17-cv-0183-CAB-(BGS) 1 The final construction at issue with regard to the ‘621 patent is a “means for” 2 limitation. An element of a claim may be expressed as a means for performing a specified 3 function without the recital of the structure and is construed to cover the corresponding 4 structure described in the specification or equivalents thereof. 35 U.S.C. § 112, ¶ 6. The 5 limitation at issue appears in claim 15, which is dependent on claim 10. 6 7 8 9 10 11 12 13 14 15 16 17 Claim 10. A system for reviewing an operating system call issued by a downloadable, comprising: … a plurality of operating system probes for monitoring substantially in parallel a plurality of subsystems of an operating system during runtime for an event caused from a request made by a Downloadable, wherein the plurality of subsystems includes a network system; …. Claim 15. The system of claim 10, wherein the plurality of operating system probes operating substantially in parallel for monitoring the operating system includes means for monitoring a request sent to a downloadable engine. The parties agree that the “means for” element of claim 15 is governed by 35 U.S.C. § 112, ¶ 6. The patent specification must disclose with sufficient particularity the corresponding structure for performing the claimed function and clearly link that structure to the function. Triton Tech of Tx., LLC. V. Nintendo of Am., Inc., 753 F.3d 1375, 1378 18 (Fed. Cir. 2014). The claimed function is “monitoring a request sent to a downloadable 19 engine.” After the claim construction hearing, the Court requested supplemental briefing 20 21 from the parties identifying with sufficient particularity the corresponding structure in the specification for performing the claimed function. [Doc. 178-1.] 22 The plaintiff refers to the specification of the ‘962 patent [Doc. No. 138-9], 23 incorporated by reference in the ‘621 patent, for the corresponding structure that supports 24 this “means for” claim. Plaintiff directs the Court to the component identified in the 25 26 27 specification as the request broker 306 described at Col. 4:12-18, Figs. 3 and 4 [id. at 6-7, 12] as the corresponding structure providing the function in the system of monitoring a request sent to a downloadable engine. [See Doc. No. 183 at 3.] 28 8 3:17-cv-0183-CAB-(BGS) 1 The specification describes the system for monitoring requests made by a 2 Downloadable 140 to a downloadable engine 250 at Col. 3:51 – Col. 5:48. [Doc. No. 138- 3 9, at 6-7, 12-13.] In the examples provided (see Figs. 3 and 4), extensions 304, 404, 405, 4 406 examine a Downloadable’s request for access to classes 302 of a Java™ Virtual 5 Machine (the downloadable engine 250) or to message calls 401, DDE calls 402 and DLL 6 calls 403 of a ActiveX™ platform (the downloadable engine 250). The Downloadable’s 7 request to the downloadable engine may be interrupted by the extension which then notifies 8 the request broker 306 of the Downloadable’s request. The request broker 306 in turn 9 forwards the request to the event router 308. [Id.] 10 The extensions 304, 404, 405, 406 monitor requests made to the downloadable engine 11 250. Col. 5:40-49 (the extensions recognize a request made by a Downloadable to the 12 downloadable engine, interrupt the processing of the request and generate and forward a 13 message identifying the incoming Downloadable to request broker which forwards the 14 message to the event router.); Col. 4:10-15 (each extension 304 manages a respective one 15 of the Java™ classes, interrupts the request and generates a message to the request broker 16 306); Col. 5:23-38 (each extension 404, 405, 406 recognizes a call to an ActiveX™ 17 platform 401, 402, 403, and generates a message to the request broker 306). The request 18 broker 306 forwards the request on for further analysis and response. The structures 19 identified in the specification corresponding to a means for monitoring a request sent to 20 a downloadable engine, are the Java Class extensions 304, the Message Extension 404, 21 the Dynamic-Data-Exchange Extension 405 and Dynamically-Linked-Library Extension 22 406, and their equivalents. 23 24 25 26 27 28 9 3:17-cv-0183-CAB-(BGS) 1 2 3 F. U.S. Patent No. 9,219,755 The parties sought construction of the following terms appearing in various claims of the ‘755 patent. The Court’s constructions for these terms are: 4 Claim Term COURT’S CONSTRUCTION 5 a downloadable engine for Defendant asserts that “downloadable engine” is 6 intercepting a request the equivalent of “means for” claiming and the 7 message being issued by a disclosed structures disclosed to perform this 8 downloadable to an operating function are a Java Virtual Machine 250 or 9 system Active X Platform 250 (‘960 patent, Col. 3:54- 10 56; Fig. 3; Col. 5:25-27; Fig. 4). Plaintiff asserts 11 that “engine” is a common name for a known 12 program construct that would be familiar to one 13 of skill in the art to perform a function further 14 identified by its modifier, in this case “response.” 15 The Court agrees that “engine” is not a nonce 16 term as advocated by Defendant, and that the 17 claim provides sufficient structure for one skilled 18 in the art. 19 Defendant’s request for application of 112 ¶ 6 is 20 denied. 21 intercepting an operating stopping a request message before the request 22 system call being issued by message is received by the operating system 23 the downloadable to an 24 operating system 25 a response engine for Defendant asserts that use of “response engine” 26 receiving a violation message is the equivalent of “means for” claiming and is 27 from the runtime limited to the structures disclosed in the ‘520 28 10 3:17-cv-0183-CAB-(BGS) 1 environment … and blocking Patent, at Figs. 5 and 6, Steps 525, 530, 540 and 2 … and allowing …. 610-30. Plaintiff asserts that “engine” is a 3 common name for a known program construct 4 that would be familiar to one of skill in the art to 5 perform a function further identified by its 6 modifier, in this case “response.” The Court 7 agrees that “engine” is not a nonce term as 8 advocated by Defendant, and that the claim 9 provides sufficient structure for one skilled in the 10 art. Defendant’s request for application of 112 ¶6 11 is denied. 12 13 It is SO ORDERED. 14 Dated: November 14, 2017 15 16 17 18 19 20 21 22 23 24 25 26 27 28 11 3:17-cv-0183-CAB-(BGS)

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?