throbber
Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 1 of 7
`
`IRELL & MANELLA LLP
`Jonathan S. Kagan (SBN 166039)
`jkagan@irell.com
`Alan Heinrich (SBN 212782)
`aheinrich@irell.com
`Joshua Glucoft (SBN 301249)
`jglucoft@irell.com
`1800 Avenue of the Stars, Suite 900
`Los Angeles, California 90067-4276
`Telephone: (310) 277-1010
`Facsimile: (310) 203-7199
`
`Rebecca Carson (SBN 254105)
`rcarson@irell.com
`Ingrid Petersen (SBN 313927)
`ipetersen@irell.com
`Kevin Wang (SBN 318024)
`kwang@irell.com
`840 Newport Center Drive, Suite 400
`Newport Beach, California 92660-6324
`Telephone: (949) 760-0991
`Facsimile: (949) 760-5200
`
`Attorneys for Defendant
`JUNIPER NETWORKS, INC.
`
`
`
`
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`SAN FRANCISCO DIVISION
`
`FINJAN, INC., a Delaware Corporation,
`
`
`Plaintiff,
`
`vs.
`
`
`
`
`JUNIPER NETWORKS, INC., a Delaware
`Corporation,
`
`
`Defendant.
`
`
`
`
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`Case No. 3:17-cv-05659-WHA
`
`DEFENDANT JUNIPER NETWORKS,
`INC.’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`
`
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`
`
`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
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`

`

`Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 2 of 7
`
`
`
`1
`
`I.
`
`INTRODUCTION
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`In its original summary judgment briefing, Finjan argued that the Court could and should
`
`resolve Juniper’s alleged infringement of the ’154 Patent on summary judgment because “there is
`
`no genuine dispute as to any material fact.” Dkt. 368-4 at 8. Now that Finjan has lost the dispositive
`
`claim construction issue, however, it suddenly claims that there are myriad factual disputes making
`
`summary judgment inappropriate. Finjan was right the first time.
`
`Finjan’s attempt to manufacture 11th hour factual disputes fail because Finjan has not—and
`
`cannot—identify any “modified content” within the meaning of the claim. Instead, Finjan attempts
`
`to gin up new meanings of “modified content” that are completely divorced from the claim language
`
`and the disclosures of the ’154 Patent. Moreover, Finjan’s allegation that Juniper somehow
`
`sandbagged Finjan with a new construction is a desperate attempt at revisionist history. Indeed, it
`
`was Finjan that sandbagged Juniper by departing from its infringement contentions and introducing
`
`new theories for the first time on summary judgment (as detailed in Juniper’s motion to strike those
`
`contentions). In short, Finjan has not identified a legitimate reason why the Court should not enter
`
`summary judgment in Juniper’s favor on Claim 1 of the ’154 Patent given the Court’s construction
`
`16
`
`of “content processor.”
`
`17
`
`II.
`
`ARGUMENT
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`A.
`
`Finjan Has Not Raised A Genuine Factual Dispute That Would Preclude
`Summary Judgment In Juniper’s Favor.
`
`1.
`
`Finjan Has Not Identified Any Evidence That The Accused Products
`Process “Modified Content” Within The Meaning Of Claim 1.
`
`As explained in the parties summary judgment papers, the accused Juniper products do not
`
`process “modified content” as required by the ’154 Patent. Finjan’s initial response to this
`
`undisputed fact was to try to read the “modified content” requirement out of its patent. Having failed
`
`to convince the Court to do so, Finjan now tries to salvage its infringement case by redefining the
`
`meaning of “modified content” to include “original content,” which was explicitly distinguished by
`
`both this Court and the PTAB. Dkt. 459 at 7 (noting that “the substitute function exists only after
`
`the original content is modified at the gateway computer”); Dkt. 390-19 at 9-10 (PTAB
`
`distinguishing between “original,” “modified” and “dynamically generated” content). In particular,
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`- 1 -
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 3 of 7
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`Finjan claims that the accused products process “modified content” because they process (1) content
`
`that has been compromised by hackers at some point before it is requested by the client/end user,
`
`(2) content that has been encrypted before it is sent from a server to the end user, (3) content that
`
`has been compressed (e.g., in a zip file) before being sent to the end user, and (4) content that has
`
`been “buffered and chunked” for purposes of processing it.
`
`None of the categories of “content” identified by Finjan actually constitute “modified
`
`content” within the meaning of the ’154 Patent. As the Court noted, the content processed by the
`
`8
`
`“content processor” includes a
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`“‘first function’ [that] clearly involves the ‘substitute function,’ which
`sends the content’s input to the security computer for inspection once
`invoked. According to the specification, the substitute function exists
`only after the original content is modified at the gateway computer
`(see, e.g., ’154 patent at 9:13-28). Accordingly, the claimed ‘content’
`necessarily refers to modified content.”
`
`Dkt. 459 at 7 (citing Palo Alto Networks, Inc. v. Finjan, Inc., 752. F. App’x 1017, 1018 (Fed. Cir.
`
`2018); Finjan, Inc. v. Cisco Systems, Inc., 2018 WL 3537142, at *20-23 (N.D. Cal. July 23, 2018)).
`
`Indeed, the ’154 patent explains that “the present invention operates by replacing original function
`
`calls with substitute function calls within the content, at a gateway computer, prior to the content
`
`being received at the client computer.” ’154 Patent at 4:55-60.
`
`Finjan has not alleged that any of the accused products process content that has been modified
`
`by inserting a “substitute function” that sends the input to a security computer for inspection when
`
`it is invoked. In fact, the accused products do no such thing. See Dkt. 468 (Juniper’s Response to
`
`Order to Show Cause). Finjan’s theories regarding hacked, encrypted or compressed content involve
`
`content that is altered or prepared at the server hosting that content before it is sent to the client and
`
`before it even reaches the gateway. Thus, this type of content is the “original content,” not the
`
`“modified content.” See Dkt. 390-19 at 9 (“First, there is the ‘original content’ that is scanned and
`
`modified at the gateway computer.”) (emphasis added).
`
`Finjan’s theory involving “buffered” or “chunked” content also fails because the content is
`
`simply being broken into pieces for processing, not “modified.” Relatedly, Finjan argues that Sky
`
`ATP and ATP Appliance receive “modified” content because the SRX or ATP Appliance collector
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`- 2 -
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 4 of 7
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`“replaces the get request with its own, and its own ip address.” Dkt. 474 at 6, 9. But the “get request”
`
`and “ip address” are not even part of the “content” that Sky ATP or ATP Appliance processes, much
`
`less a “substitute function” that would comprise “modified content” within the meaning of Claim 1.
`
`Rather, this is simply location information that tells Sky ATP or ATP Appliance where to send the
`
`results of the analysis. Finjan’s argument that the ATP Appliance processes “modified” content
`
`because it processes the original content along with “metadata” similarly falls flat. Dkt. 474 at 8.
`
`Creating “metadata” to help process a file does not constitute “modification” of the content of that
`
`file because there is no alteration of the functions contained within the content. Rather, the metadata
`
`simply adds information to aid in the processing of the original functions contained in the original
`
`10
`
`content.
`
`11
`
`Because Finjan has not and cannot identify any evidence that the accused products actually
`
`12
`
`process “modified content,” its new infringement theories fail as a matter of law and the Court should
`
`13
`
`entered summary judgment in favor of Juniper.
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`2.
`
`Finjan Has Not Identified Any Evidence That The Content It Alleges Is
`“Modified” Would Satisfy The Other Claim Elements.
`
`Even if the categories of content identified by Finjan could be considered “modified
`
`content”—which they cannot—Finjan has not identified any infringement scenario involving that
`
`content that would satisfy the other limitations of Claim 1. Indeed, Finjan presented an infringement
`
`theory where the “first function” is an “http function” that uses a “URL” or “IP Address” as an input.
`
`Dkt. 368-4 at 10, 16 and 20. Finjan offers no explanation for how the new “content” that it identifies
`
`contains any alleged “first function” nor how it would meet the requirement that a “second function”
`
`is invoked with the input only if the security computer indicates that it is safe. Indeed, to the extent
`
`Finjan is now arguing that the SRX replaces the “get request” and “IP address,” then Finjan is
`
`admitting that the “content” that it pointed to in its infringement theory never actually gets sent to
`
`the “security computer” (i.e., Sky ATP or ATP Appliance). Nor does Finjan address the remainder
`
`of Juniper’s non-infringement arguments, which are equally applicable to Finjan’s new theories.
`
`Moreover, as the Court acknowledged in its Order, “Juniper makes a strong argument for the
`
`proposition that the content processor resides on the client computer.” Dkt. 459 at n.2. There is no
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`- 3 -
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 5 of 7
`
`
`
`1
`
`2
`
`3
`
`4
`
`dispute that the accused products are not “client/user computer,” and therefore fail to meet the
`
`“content processor” limitation for this separate reason. As such, the accused products would still
`
`not infringe Claim 1 of the ’154 Patent as a matter of law for the reasons set forth in Juniper’s
`
`opposition, including because the alleged “content processor” is not located on a client/user
`
`5
`
`computer.
`
`3.
`
`Juniper Does Not Infringe Under the Doctrine of Equivalents.
`
`Finjan also claims that Juniper infringes under the doctrine of equivalents (“DOE”), but fails
`
`to show how the accused products perform the same function in the same way to obtain the same
`
`result. First, Finjan claims that the accused products infringe under DOE because they process
`
`content that was received from the internet that has been modified on the server. Yet, this is precisely
`
`the “original content” described by the PTAB and fundamentally distinct from the claimed content,
`
`which is the modified content that had an original function call replaced by a substitute function.
`
`Indeed, the PTAB explained “[t]he claimed content cannot refer to the ‘original content’ that is
`
`received by the gateway and over the Internet because that content, according to the Specification,
`
`would be capable of generating the undetected dynamically generated malicious content from which
`
`the client computer is to be protected.” Dkt. 390-19 at 10 (emphasis in original). Equivocating
`
`between these distinct concepts is entirely improper. As such, Finjan’s new infringement scenario
`
`does not perform the same function in the same way to obtain the same result. Moreover, Finjan’s
`
`theory that simply processing original content could read on Claim 1 would undoubtedly ensnare
`
`the prior art that is discussed in the ’154 Patent itself. ’154 Patent at 1:65-2:16 (discussing prior art
`
`that performs behavioral analysis on original content at the gateway).
`
`Second, Finjan alleges that the accused products “effectively modify the content so that
`
`functions included in the content to obtain further content (e.g., denoted by an http:// command or
`
`an iframe command) are replaced by functions which instead send the input to a security computer
`
`so that the security computer can return an indicator whether it is safe to invoke a second function
`
`with the input.” Dkt. 469-3 at 10. Yet, the only thing Finjan cites for support is its expert’s
`
`declaration, which is an almost verbatim regurgitation of Finjan’s attorney arguments with literally
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`- 4 -
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 6 of 7
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`no evidence to support its claims. See Dkt. 469-6 at ¶ 111. As explained in Juniper’s letter to the
`
`Court, no such evidence exists. See Dkt. 468.
`
`4.
`
`Finjan Does Not Have Cause to Supplement its Infringement
`Contentions.
`
`Finjan does not have cause to supplement its infringement contentions based on its new
`
`infringement theories because, as explained above, they are premised on an untenable, overly broad
`
`interpretation of the content that is processed by the content processor. As such, these theories fail
`
`as a matter of law and it would be futile for Finjan to amend its infringement contentions.
`
`B.
`
`Juniper Did Not Sandbag Finjan On The Construction Of “Content
`Processor.”
`
`10
`
`Alternatively, Finjan argues that it would be unfair to enter summary judgment in favor of
`
`11
`
`Juniper because Juniper allegedly “sandbagged” Finjan with its proposed construction of “content
`
`12
`
`processor.” Finjan’s complaint rings hollow.
`
`13
`
`As an initial matter, the need to clarify whether the content processed by the content
`
`14
`
`processor is “original content” or “modified content” was created by Finjan’s effort to introduce new
`
`15
`
`infringement theories, which it raised for the first time in its opening summary judgment brief. See
`
`16
`
`Dkt. 391 (Juniper’s Motion to Strike). Finjan’s new theories essentially amounted to accusing
`
`17
`
`conventional URL/IP filtering functionality and disregarding the core invention disclosed in the ’154
`
`18
`
`Patent—i.e., the use of a substitute function to verify safety before invoking an original function.
`
`19
`
`Thus, if any party was sandbagged, it was Juniper, not Finjan.
`
`20
`
`In any event, Finjan can hardly claim that it was ambushed with a “new” meaning of “content
`
`21
`
`processor,” given that every tribunal to consider this issue has found that the context of claim 1
`
`22
`
`makes clear that the “content” being processed is “modified content.” Finjan itself argued that that
`
`23
`
`“no claim construction was necessary” and the plain and ordinary meaning applied, and referenced
`
`24
`
`the IPR record in supporting its argument. See Dkt. 176 (Finjan’s Claim Construction Brief) at
`
`25
`
`17-18. As the Court noted in its Order, in the IPR proceedings the PTAB unambiguously explained
`
`26
`
`that the claimed content of claim 1 refers to “modified content.” See Dkt. 390-19 at 9-10. In
`
`27
`
`affirming the PTAB’s decision, the Federal Circuit explained that Claim 1 “recit[es] a system or
`
`28
`
`software program that executes a substitute function,” thus confirming that the “content” being
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`- 5 -
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 479 Filed 05/16/19 Page 7 of 7
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`processed is modified content. Palo Alto Networks, Inc. v. Finjan, Inc., 752. F. App’x 1017, 1018
`
`(Fed. Cir. 2018) (emphasis added). Similarly, Judge Freeman recently construed the term “first
`
`function” to mean “substitute function” and “second function” as “original function, which is
`
`different than the first function.” Finjan, Inc. v. Cisco Systems, Inc., 2018 WL 3537142, at *20-23
`
`(N.D. Cal. July 23, 2018). Thus, Finjan’s suggestion that it could not have anticipated that the Court
`
`would construe Claim 1 in a manner that is entirely consistent with these prior rulings is simply not
`
`7
`
`credible.
`
`8
`
`9
`
`Moreover, Finjan was not prejudiced as it had has the opportunity to address Juniper’s
`
`arguments in its reply brief, and did just that. Dkt. 414-3 (Finjan Reply) at 2-3. And, if Finjan
`
`10
`
`legitimately thought Juniper had raised improper arguments, it certainly could have sought
`
`11
`
`additional briefing and/or moved to strike Juniper’s arguments. But Finjan chose not to do so, as
`
`12
`
`any such effort would have merely highlighted Finjan’s changing infringement theories. Finjan’s
`
`13
`
`complaints are simply a pretext to divert this Court from the inevitable—and previously undisputed
`
`14
`
`material fact—that Juniper’s products simply do not infringe under the proper interpretation of
`
`15
`
`Claim 1 of the ’154 Patent. The Court should therefore enter judgment that the accused products do
`
`16
`
`not infringe Claim 1 of the ’154 Patent.
`
`17
`
`III. CONCLUSION
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`Finjan has not identified any evidence that the accused products process “modified content”
`
`within the meaning of Claim 1 of the ’154 Patent. As Juniper detailed in its opposition to Finjan’s
`
`motion for summary judgment, the accused products employ a fundamentally different approach to
`
`malware analysis than the approach disclosed in the ’154 Patent. Dkt. 390 at 11-15. The Court
`
`should reject Finjan’s desperate attempt to expand the meaning of “modified content” to include the
`
`distinguishable “original content,” and enter summary judgment in favor of Juniper.
`
`24
`
`Dated: May 16, 2019
`
`25
`
`26
`
`27
`
`28
`
`IRELL & MANELLA LLP
`A Registered Limited Liability
`Law Partnership Including
`Professional Corporations
`
`10680017
`
`
`Respectfully submitted,
`
`IRELL & MANELLA LLP
`
`By: /s/ Rebecca L. Carson
`Rebecca L. Carson
`Attorneys for Defendant
`Juniper Networks, Inc.
`
`- 6 -
`
`JUNIPER’S REPLY TO FINJAN’S RESPONSE
`TO ORDER TO SHOW CAUSE
`(Case No. 3:17-cv-05659-WHA)
`
`

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