throbber
Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 1 of 218
`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 1 of 218
`
`
`
`
`
`EXHIBIT 1
`EXHIBIT 1
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 2 of 218
`
`
`
`
`
`IRELL & MANELLA LLP
`Jonathan S. Kagan (SBN 166039)
`jkagan@irell.com
`Joshua Glucoft (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
`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
`)
`Case No. 3:17-cv-05659-WHA
`)
`
`)
`
`JUNIPER NETWORKS, INC.’S FIRST
`)
`SUPPLEMENT TO INITIAL
`)
`DISCLOSURES
`)
`
`)
`
`)
`
`)
`)
`)
`)
`)
`
`FINJAN, INC.,
`
`Plaintiff,
`
`vs.
`
`
`JUNIPER NETWORKS, INC.,
`
`Defendant.
`
`
`
`
`
`
`
`
`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
`
`10567759
`
`
`
`
`
`JUNIPER’S FIRST SUPPLEMENT TO
`INITIAL DISCLOSURES
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 3 of 218
`
`Name & Contact Information
`Frank Jas*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Rakesh Manocha*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Raju Manthena*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Chandra Nagarajan*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Shelly Gupta*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Michael Bushong*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Michael Marcellin*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Scott Coonan*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Shlomo Touboul
`Senior Advisor, Finjan
`
`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
`
`
`
`Summary of Information
`May have technical information about accused
`Juniper and Cyphort products.
`
`May have technical information about accused
`Juniper products.
`
`May have technical information about accused
`Juniper products.
`
`May have technical information about accused
`Juniper products.
`
`May have financial information related to accused
`Juniper products.
`
`May have marketing information related to the
`accused Juniper products.
`
`May have company information related to Juniper.
`
`May have company information related to Juniper,
`Juniper’s licensing practices, and Juniper’s
`communications with Finjan.
`
`Named inventor on the ‘844, ‘780, ‘926, ‘633, ‘731,
`and ‘494 Patents. May have information regarding
`the patents-in-suit, including: inventorship;
`conception and reduction to practice; prior art and
`inequitable conduct; alleged embodiments of the
`patents-in-suit; offers for sale; assignments or other
`transactions regarding ownership; secondary
`considerations regarding the obviousness of the
`patents-in-suit; and licensing and enforcement
`activities.
`
`10567759
`
`
`
`- 3 -
`
`JUNIPER’S FIRST SUPPLEMENT TO
`INITIAL DISCLOSURES
`(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
`
`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 4 of 218
`
`
`
`CERTIFICATE OF SERVICE
`The undersigned hereby certifies that on September 10, 2018, a copy of JUNIPER
`NETWORKS, INC.’S FIRST SUPPLEMENT TO INITIAL DISCLOSURES was caused to be
`served via email on the following counsel of record:
` Email Service Addresses
`:
`
`
`
`
`
`
`
`
`
`pandre@kramerlevin.com
`
`
`
`
`
`lkobialka@kramerlevin.com
`
`
`
`
`
`jhannah@kramerlevin.com
`
`
`
`
`
`kkastens@kramerlevin.com
`
`
`
`
`
`amanes@kramerlevin.com
`shedvat@kramerlevin.com
`mhlee@kramerlevin.com
`cmartinez@kramerlevin.com
`SNguyen@kramerlevin.com
`
`
`
`
`
`
`
`/s/ Eileen Holland
`Eileen Holland
`
`10567759
`
`
`
`
`
`JUNIPER’S FIRST SUPPLEMENT TO
`INITIAL DISCLOSURES
`(Case No. 3:17-cv-05659-WHA)
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 5 of 218
`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 5 of 218
`
`
`
`
`
`EXHIBIT 2
`EXHIBIT 2
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`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 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 6 of 218
`
`IRELL & MANELLA LLP
`Jonathan S. Kagan (SBN 166039)
`jkagan@irell.com
`Joshua Glucoft (SBN 301249)
`jglucoft@irell.com
`Casey Curran (SBN 305210)
`ccurran@irell.com
`Sharon Song (SBN 313535)
`ssong@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
`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.,
`
`
`Plaintiff,
`
`vs.
`
`
`
`
`JUNIPER NETWORKS, INC.,
`
`
`Defendant.
`
`
`
`
`
`
`
`
`10604227
`
`
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`Case No. 3:17-cv-05659-WHA
`
`
`JUNIPER NETWORKS, INC.’S SECOND
`SUPPLEMENT TO INITIAL
`DISCLOSURES
`
`
`
`
`JUNIPER’S SECOND SUPPLEMENT TO
`INITIAL DISCLOSURES
`(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
`
`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 7 of 218
`
`Name & Contact Information
`
`Summary of Information
`
`
`
`Meredith McKenzie*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Alex Icasiano*
`1133 Innovation Way
`Sunnyvale, CA 94089
`408-745-2000
`Shlomo Touboul
`Senior Advisor, Finjan
`
`Nachshon Gal
`
`Yigal Mordechai Edery
`
`Nimrod Itzhak Vered
`
`10604227
`
`
`
`May have company information related to Juniper,
`Juniper’s licensing practices, and Juniper’s
`communications with Finjan.
`
`May have operational information related to the
`accused Juniper products.
`
`Named inventor on the ‘844, ‘780, ‘926, ‘633, ‘731,
`and ‘494 Patents. May have information regarding
`the patents-in-suit, including: inventorship;
`conception and reduction to practice; prior art and
`inequitable conduct; alleged embodiments of the
`patents-in-suit; offers for sale; assignments or other
`transactions regarding ownership; secondary
`considerations regarding the obviousness of the
`patents-in-suit; and licensing and enforcement
`activities.
`Named inventor on the ‘844 Patent. May have
`information regarding the patents-in-suit, including:
`inventorship; conception and reduction to practice;
`prior art and inequitable conduct; alleged
`embodiments of the patents-in-suit; offers for sale;
`assignments or other transactions regarding
`ownership; secondary considerations regarding the
`obviousness of the patents-in-suit; and licensing and
`enforcement activities.
`Named inventor on the ‘926, ‘633, and ‘494 Patents.
`May have information regarding the patents-in-suit,
`including: inventorship; conception and reduction to
`practice; prior art and inequitable conduct; alleged
`embodiments of the patents-in-suit; offers for sale;
`assignments or other transactions regarding
`ownership; secondary considerations regarding the
`obviousness of the patents-in-suit; and licensing and
`enforcement activities.
`Named inventor on the ‘926, ‘633, and ‘494 Patents.
`May have information regarding the patents-in-suit,
`including: inventorship; conception and reduction to
`practice; prior art and inequitable conduct; alleged
`embodiments of the patents-in-suit; offers for sale;
`assignments or other transactions regarding
`ownership; secondary considerations regarding the
`obviousness of the patents-in-suit; and licensing and
`enforcement activities.
`
`- 4 -
`
`JUNIPER’S SECOND SUPPLEMENT TO
`INITIAL DISCLOSURES
`(Case No. 3:13-cv-00616-JCS)
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 8 of 218
`
`the patents-in-suit are unenforceable, and reasonable attorneys’ fees and costs incurred in this
`
`
`
`action pursuant to 35 U.S.C. § 285.
`
`IV.
`
`Insurance Agreements
`
`Juniper is not aware of any insurance agreements under which an insurance business may
`
`be liable to satisfy all or part of a possible judgment in this action or to indemnify or reimburse
`
`Juniper for payments made to satisfy a judgment.
`
`Dated: November 5, 2018
`
`Respectfully submitted,
`
`/s/ Rebecca Carson
`Rebecca Carson
`Irell & Manella LLP
`Attorneys for Defendant
`JUNIPER NETWORKS, INC.
`
`
`
`
`
`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
`
`10604227
`
`
`
`- 13 -
`
`JUNIPER’S SECOND SUPPLEMENT TO
`INITIAL DISCLOSURES
`(Case No. 3:13-cv-00616-JCS)
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 9 of 218
`
`
`
`
`
`
`
`
`
`
`
`
`
`Exhibit 3
`
`REDACTED VERSION OF
`DOCUMENT SOUGHT TO BE SEALED
`DOCUMENT REDACTED IN ITS
`ENTIRETY
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 10 of 218
`
`
`
`
`
`
`
`
`
`
`
`
`
`Exhibit 4
`
`REDACTED VERSION OF
`DOCUMENT SOUGHT TO BE SEALED
`DOCUMENT REDACTED IN ITS
`ENTIRETY
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 11 of 218
`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 11 of 218
`
`
`
`
`
`EXHIBIT 5
`EXHIBIT 5
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 12 of 218
`
`
`
`I.
`
`INTRODUCTION
`
`EXPERT REPORT OF AVIEL D. RUBIN
`
`1.
`
`I have been retained as an independent expert in this lawsuit by the law firm of Irell &
`
`Manella LLP on behalf of Juniper Networks, Inc. (“Juniper”). I have been asked to provide an opinion
`
`related to whether Claim 10 of U.S. Patent No. 8,677,494 (“the ‘494 Patent”) contains an inventive
`
`concept sufficient to transform the claimed abstract idea into a patent-eligible application. As discussed
`
`in further detail in this declaration, it is my opinion that Claim 10 does not contain an inventive concept
`
`sufficient to transform the claimed abstract idea into a patent-eligible application.
`
`2.
`
`In addition to opinions outlined in this report, I may also provide testimony (1) in rebuttal
`
`to Finjan’s positions, including opinions of its experts and materials they discuss or rely upon, (2) based
`
`on any Orders from the Court, (3) based on documents, contentions, or other discovery that Finjan or
`
`others have not yet produced or were produced too late to be considered before my report was due, and/or
`
`(4) based on witness testimony which has not been given or was given too late to be considered before
`
`my report was due. I reserve the right to supplement or amend my opinions as further documentation
`
`and information is received.
`
`3.
`
`If called to testify in this matter, I may use as exhibits various documents produced in this
`
`matter that refer or relate to the matters discussed in this report. I have not yet selected the particular
`
`exhibits that may be used. In addition, I may create or assist in the creation of certain demonstrative
`
`exhibits or summaries of my findings and opinions to assist me in testifying. Such exhibits have not yet
`
`been created.
`
`II.
`
`BACKGROUND AND QUALIFICATIONS
`
`4.
`
`I am being paid at my customary rate of $775 per hour for time spent on this case. I am
`
`also being reimbursed for reasonable and customary expenses. My compensation is not dependent in
`
`any way on the results of the lawsuit or the substance of my testimony.
`
`5.
`
`I provide below an overview of my background and qualifications. Additional details of
`
`my education and employment history, professional service, patents, publications, and other testimony
`
`are
`
`set
`
`forth
`
`in my current curriculum vitae
`
`(CV), which can be
`
`found here:
`
`10571956
`
`
`- 1 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 13 of 218
`
`
`http://avirubin.com/Avi_Rubins_home_page/Vita.html. My CV found at that website is incorporated
`
`herein by reference and also attached hereto as Exhibit 1.
`
`A.
`
`6.
`
`Education & Career
`
`I received my Ph.D. in Computer Science and Engineering from the University of
`
`Michigan, Ann Arbor in 1994, with a specialty in computer security and cryptographic protocols. My
`
`thesis was titled “Nonmonotonic Cryptographic Protocols” and concerned authentication in long-
`
`running networking operations.
`
`7.
`
`I am currently employed as Professor of Computer Science at Johns Hopkins University,
`
`where I perform research, teach graduate courses in computer science and related subjects, and supervise
`
`the research of Ph.D. candidates and other students. Courses I have taught include Security and Privacy
`
`in Computing and Advanced Topics in Computer Security. I am also the Technical Director of the Johns
`
`Hopkins University Information Security Institute, the University’s focal point for research and
`
`education in information security, assurance, and privacy. The University, through the Information
`
`Security Institute’s leadership, has been designated as a Center of Academic Excellence in Information
`
`Assurance by the National Security Agency and leading experts in the field. The focus of my work over
`
`my career has been computer security, and my current research concentrates on systems and networking
`
`security, with special attention to software and network security.
`
`8.
`
`After receiving my Ph.D., I began working at Bellcore in its Cryptography and Network
`
`Security Research Group from 1994 to 1996. During this period I focused my work on Internet and
`
`Computer Security. While at Bellcore, I published an article titled “Blocking Java Applets at the
`
`Firewall” about the security challenges of dealing with JAVA applets and firewalls, and a system that
`
`we built to overcome those challenges.
`
`9.
`
`In 1997, I moved to AT&T Labs, Secure Systems Research Department, where I
`
`continued to focus on internet and computer security. From 1995 through 1999, in addition to my work
`
`in industry, I served as Adjunct Professor at New York University, where I taught undergraduate classes
`
`on computer, network and internet security issues.
`
`10.
`
`I stayed at AT&T until 2003, when I left to accept a full time academic position at Johns
`
`Hopkins University. I was promoted to full professor with tenure in April, 2004.
`
`10571956
`
`
`- 2 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 14 of 218
`
`
`
`11.
`
`I serve, or have served, on a number of technical and editorial advisory boards. For
`
`example, I served on the Editorial and Advisory Board for the International Journal of Information and
`
`Computer Security. I also served on the Editorial Board for the Journal of Privacy Technology. I have
`
`been Associate Editor of IEEE Security and Privacy Magazine, and served as Associate Editor of ACM
`
`Transactions on Internet Technology. I am currently an Associate Editor of the journal Communications
`
`of the ACM. I was an Advisory Board Member of Springer’s Information Security and Cryptography
`
`Book Series. I have served in the past as a member of the DARPA Information Science and Technology
`
`Study Group, a member of the Government Infosec Science and Technology Study Group of Malicious
`
`Code, a member of the AT&T Intellectual Property Review Team, Associate Editor of Electronic
`
`Commerce Research Journal, Co-editor of the Electronic Newsletter of the IEEE Technical Committee
`
`on Security and Privacy, a member of the board of directors of the USENIX Association, the leading
`
`academic computing systems society, and a member of the editorial board of the Bellcore Security
`
`Update Newsletter.
`
`12.
`
`I have spoken on information security and electronic privacy issues at more than 50
`
`seminars and symposia. For example, I presented keynote addresses on the topics “Security of Electronic
`
`Voting” at Computer Security 2004 Mexico in Mexico City in May 2004; “Electronic Voting” to the
`
`Secure Trusted Systems Consortium 5th Annual Symposium in Washington DC in December 2003;
`
`“Security Problems on the Web” to the AT&T EUA Customer conference in March, 2000; and “Security
`
`on the Internet” to the AT&T Security Workshop in June 1997. I also presented a talk about hacking
`
`devices at the TEDx conference in October 2011 and also another TEDx talk on the same topic in
`
`September 2015.
`
`13.
`
`I was founder and President of Independent Security Evaluators (ISE), a computer
`
`security consulting firm, from 2005-2011. In that capacity, I guided ISE through the qualification as an
`
`independent testing lab for Consumer Union, which produces Consumer Reports magazine. As an
`
`independent testing lab for Consumer Union, I managed an annual project where we tested all of the
`
`popular anti-virus products. Our results were published in Consumer Reports each year for three
`
`consecutive years.
`
`10571956
`
`
`- 3 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 15 of 218
`
`
`
`14.
`
`I am currently the founder and managing partner of Harbor Labs, a software and
`
`networking consulting firm.
`
`B.
`
`15.
`
`16.
`
`Publications
`
`I am a named inventor on ten U.S. patents in the information security area.
`
`I have also testified before Congress regarding the security issues with electronic voting
`
`machines and in the U.S. Senate on the issue of censorship. I also testified in Congress on November
`
`19, 2013 about security issues related to the government’s Healthcare.gov website.
`
`17.
`
`I am author or co-author of five books regarding information security issues: Brave New
`
`Ballot, Random House, 2006; Firewalls and Internet Security (second edition), Addison Wesley, 2003;
`
`White-Hat Security Arsenal, Addison Wesley, 2001; Peer-to-Peer, O’Reilly, 2001; and Web Security
`
`Sourcebook, John Wiley & Sons, 1997. I am also the author of numerous journal and conference
`
`publications, which are reflected in my CV.
`
`III. MATERIALS CONSIDERED
`
`18.
`
`I have considered information from various sources in forming my opinions. In addition
`
`to drawing from over two decades of experience in the computer industry, I also have reviewed the
`
`following documents: (a) the ‘494 Patent; (b) the prosecution file history (including IPRs) for the ‘494
`
`Patent; (c) the parties’ summary judgment briefing related to the ‘494 Patent, including exhibits thereto,
`
`and the related Court Order; and (d) the other documents and references cited herein (not limited to the
`
`specific excerpts cited). I am also aware of information generally available to, and relied upon by,
`
`persons of ordinary skill in the art at the relevant time, including, for example, textbooks, manuals,
`
`technical papers, and articles, as well as commercially available systems.
`
`IV.
`
`LEVEL OF ORDINARY SKILL
`
`19.
`
`Finjan’s expert Dr. Medvidovic has previously opined that a person of ordinary skill in
`
`the art in the field of the ‘494 Patent would be someone with a bachelor’s degree in computer science or
`
`a related field and either two or more years of industry experience and/or an advanced degree in computer
`
`science or related field. IPR2015-01892, Ex. 2007 ¶ 37 (Ex. 21 hereto); see also IPR2016-00159, Ex.
`
`2011 ¶ 37 (Ex. 22 hereto). For purposes of my analysis, I have adopted this level of ordinary skill, but I
`
`do not think that my analysis would change if a somewhat higher or lower level of skill were adopted.
`
`10571956
`
`
`- 4 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 16 of 218
`
`
`V.
`
`PRIORITY DATE OF THE ‘494 PATENT
`
`20.
`
`I understand that Finjan has asserted that Claim 10 of the ‘494 Patent is entitled to a
`
`priority date of November 8, 1996. Ex. 2 at 6. For purposes of my analysis, I have assumed that this
`
`priority date applies and considered the state of the art as it existed prior to that time.
`
`VI.
`
`LEGAL STANDARDS
`
`21.
`
`As set forth by the Court in this matter regarding Section 101 of Title 35 of the United
`
`States Code (“Section 101” or “§ 101”), I understand that:
`
`Under well-established Supreme Court precedent, laws of nature, natural
`phenomena, and abstract ideas remain patent-ineligible under Section 101.
`See, e.g., Ass’n for Molecular Pathology v. Myriad Genetics, Inc., 569 U.S.
`576, 589 (2013) (citations and quotations omitted). The Supreme Court has
`set forth a two-step “framework for distinguishing patents that claim laws
`of nature, natural phenomena, and abstract ideas from those that claim
`patent-eligible applications of those concepts.” Under this framework, a
`court must first “determine whether the claims at issue are directed to one
`of those patent-ineligible concepts.” If so, then the court must further
`“consider the elements of each claim both individually and ‘as an ordered
`combination’ to determine whether the additional elements ‘transform the
`nature of the claim’ into a patent-eligible application.” Alice Corp. Pty. Ltd.
`v. CLS Bank Int’l, 134 S. Ct. 2347, 2355 (2014) (quoting Mayo
`Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66 (2012)).
`
`Dkt. No. 189 (Ex. 17) at 18. I may refer to this two-step analysis set forth by the Supreme Court and
`
`summarized by the Court in this matter as the “Alice test.”
`
`22. With respect to Step Two of the Alice test, as this Court held:
`
`The Supreme Court has described step two as “a search for an inventive
`concept — i.e., an element or combination of elements that is sufficient to
`ensure that the patent in practice amounts to significantly more than a patent
`upon the ineligible concept itself.” Alice, 134 S. Ct. at 2355 (quotations and
`citation omitted) (emphasis added).
`
`Dkt. No. 189 at 20. I further understand that in order for components to transform the nature of the
`
`claim, their role must be more than “‘well-understood, routine, [and] conventional activit[ies]’
`
`previously known to the industry.” Alice, 134 S. Ct. at 2359
`
`VII. CLAIM 10 FAILS STEP ONE OF THE ALICE TEST
`
`23.
`
`It is my opinion that Claim 10 claims a patent-ineligible abstract idea and therefore fails
`
`Step One of the Alice test.
`
`10571956
`
`
`- 5 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 17 of 218
`
`
`
`24.
`
`I understand that the Court in this matter has already found that Claim 10 of the ‘494
`
`Patent is directed to a patent-ineligible abstract idea. Dkt. No. 189 at 18-19. Of particular relevance, the
`
`Court found:
`
`It broadly claims the fundamental practice of collecting data, analyzing
`data, and storing results, a concept that is inherently needed for virtually
`any variation of data analysis, storage, and retrieval. … Claim 10 does not
`recite “a new kind of file,” i.e. a security profile, “that enables a computer
`security system to do things it could not do before.” [citation] Rather, Claim
`10 recites deriving “security profile data.” Ultimately, the thrust of Claim
`10 is on analyzing a file and extracting information — which, once washed
`of its technological context, is merely an abstract idea. … Claim 10 of the
`‘494 patent does not itself recite any step beyond the mere identification of
`suspicious operations within a received Downloadable (and then storing the
`information somewhere). [citation] It stops short of claiming any non-
`fundamental, routine step, such as comparing the security profile with the
`access control list or any kind of protective measure. As such, Claim 10 is
`directed to an abstract idea rather than an improvement on computer
`functionality.
`
`Dkt. No. 189 at 18-19. I agree with the Court’s reasoning and analysis. Claim 10 is directed to collecting,
`
`analyzing, and storing data using well-understood, routine, and conventional steps.
`
`25.
`
`I understand that at least two other courts have also found that Claim 10 is directed to an
`
`abstract idea. Finjan, Inc. v. Blue Coat Sys., LLC, No. 15-cv-03295-BLF, 2016 WL 7212322, at *9
`
`(N.D. Cal. Dec. 13, 2016) (“Blue Coat”); Finjan v. Sophos, 244 F. Supp. 3d 1016, 1059-60 (N.D. Cal.
`
`Mar. 14, 2017). The Blue Coat court found that the ‘494 Patent claims were abstract, reasoning that
`
`“[a]lthough they are deployed in the context of malware detection, the asserted claims merely recite the
`
`familiar concepts of gathering data, analyzing that data for certain characteristics, and storing the results
`
`of that analysis[; t]hese are fundamental concepts germane to any type of content analysis.” Blue Coat,
`
`2016 WL 7212322, at *9. The court further reasoned “[a]t their heart, they claim nothing more than a
`
`solution that scans through data (e.g., the disassembled code from the code scanner . . .), identifies certain
`
`characteristics (e.g., the operations that match its pre-existing list of operations . . .), and stores the results
`
`of the analysis (e.g., the list of suspicious operations encountered, stored as formatted DSP data . . .).
`
`This is not inherently different from how a human would perform a classification process with pencil
`
`and paper. . . . Accordingly, the ‘character as a whole’ of the claims is directed to data collection and
`
`analysis, an abstract idea.” Id. (internal citations omitted). The Sophos court adopted substantially
`
`10571956
`
`
`- 6 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 18 of 218
`
`
`similar reasoning in holding that the ‘494 Patent claims were abstract. I agree with the holdings and
`
`reasoning by these courts that the ‘494 Patent (including Claim 10) is directed to an abstract idea.
`
`VIII. CLAIM 10 DOES NOT CONTAIN AN INVENTIVE CONCEPT
`
`26.
`
`Considering the elements of Claim 10 both individually and as an ordered combination,
`
`it is my opinion that Claim 10 does not have a transformative inventive concept. Instead, each of the
`
`components found in the claim were well understood, routine, and conventional activities previously
`
`known to the industry prior to the time of the purported invention, and the combination of the elements
`
`is also well understood, routine, and conventional.
`
`A.
`
`27.
`
`The Functionality Recited In Claim 10 Was Not Inventive.
`
`It is my opinion that the following steps were well known, routine, and conventional in
`
`the art before the priority date of Claim 10 of the ‘494 Patent: receiving an incoming Downloadable;
`
`deriving security profile data for the Downloadable, including a list of suspicious computer operations
`
`that may be attempted by the Downloadable; and storing the Downloadable security profile data in a
`
`database.
`
`28.
`
`Claim 10 of the ‘494 Patent is nearly identical to Claim 1 of the ‘494 Patent, where Claim
`
`10 is merely a system claim that performs the steps claimed in the method of Claim 1. The following
`
`table compares the claims, and shows the additional system components that differentiate Claim 10 from
`
`for managing Downloadables,
`
`Claim 1:
`
`Claim 1
`for computer-based method,
`A method
`comprising the steps of:
`receiving an incoming Downloadable;
`
`the
`for
`deriving security profile data
`Downloadable, including a list of suspicious
`computer operations that may be attempted by
`the Downloadable
`
`storing the Downloadable security profile
`data in a database
`
`for
`
`receiving
`
`an
`
`incoming
`
`Claim 10
`A
`system
`comprising:
`a
`receiver
`Downloadable;
`a Downloadable scanner coupled with said
`receiver, for deriving security profile data for the
`Downloadable, including a list of suspicious
`computer operations that may be attempted by the
`Downloadable
`said
`a database manager coupled with
`Downloadable
`scanner,
`for
`the
`storing
`Downloadable security profile data in a database.
`
`
`
`10571956
`
`
`- 7 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 19 of 218
`
`
`
`29.
`
`In IPR2016-00159, the PTAB issued a Final Written Decision invalidating Claim 1 of the
`
`‘494 Patent in view of a prior art article titled “Dynamic Detection and Classification of Computer
`
`Viruses Using General Behaviour Patterns” by Morton Swimmer et al. (“Swimmer”). IPR2016-0159,
`
`Paper 50 (Ex. 19) at 45. More specifically, the PTAB found that all of the overlapping limitations in
`
`Claim 10 (i.e., everything from the limitations that is not bolded/underlined in the table above) was
`
`disclosed in the art before the priority date for the ‘494 Patent.
`
`30.
`
`In reaching this conclusion, the PTAB applied a construction of the term “a list of
`
`suspicious computer operations” as “a list of all operations that could ever be deemed potentially
`
`hostile.” Paper 50 at 33. That construction differs from the construction of the term applied by the Court
`
`in this proceeding of “a list of computer operations in a received Downloadable that are deemed hostile
`
`or potentially hostile.” Dkt. No. 189 at 5. But the Board noted that its “ultimate conclusions regarding
`
`patentability of the challenged claims did not turn on [its] adoption of that construction….” Paper 50 at
`
`33. Indeed, the Board found “that Swimmer discloses deriving security profile data including a list of
`
`suspicious computer operations even under Patent Owner’s proposed construction,” which was “a list of
`
`computer operations deemed suspicious.” Paper 50 at 33-34. I agree with the Board that Swimmer
`
`discloses deriving “a list of computer operations deemed suspicious.” In addition, Finjan’s prior
`
`proposed construction is substantially similar to the construction adopted by the Court in this matter, and
`
`therefore it is my opinion that the Board’s previous finding that Swimmer teaches all of the limitations
`
`in Claim 1 applies in this proceeding as well.
`
`B.
`
`The Element Of A “Receiver For Receiving An Incoming Downloadable” Does Not
`
`Contain An Inventive Concept.
`
`31.
`
`It is my opinion that using a “receiver” to receive an incoming Downloadable is not an
`
`inventive concept. Rather, receivers were well known, routine, and conventional in the art before the
`
`priority date of Claim 10 of the ‘494 Patent, and using a receiver to receive an incoming file (including
`
`Java files, HTML, PDFs, Microsoft Word, executables, etc.) was a routine and conventional use of a
`
`receiver.
`
`32.
`
`For example, Swimmer teaches that a receiver can be used for receiving an incoming
`
`Downloadable in a malware detection system. Ex. 3 at 13 (“One possibility is to use it as a type of
`
`10571956
`
`
`- 8 -
`
`DECL. OF AVIEL D. RUBIN REGARRDING § 101
`Case No. 3:17-cv-05659-WHA
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 254-10 Filed 11/27/18 Page 20 of 218
`
`
`firewall for programs entering a protected network.”). I note that Finjan did not even challenge whether
`
`Swimmer taught a receiver during the IPR proceedings. See generally IPR 2016-00159, Paper 17 (Patent
`
`Owner’s Response) (Ex. 20).
`
`33.
`
`There are numerous other prior art references that disclosed using a “receiver” to receive
`
`a Downloadable. See, e.g., U.S. Patent No. 5,802,275 (Ex. 29) (filed June 22, 1994) at Claim 6 (“a
`
`receiver for receiving [] programs”); U.S. Patent No. 6,065,118 (Ex. 30) (filed September 24, 1996) at
`
`Claim 11 (“importing to the system a data stream containing at least one mobile program component
`
`which is to execute on the computer system from an external source”) and Claim 7 (“the program
`
`components which are to be intercepted and run within the execution location are Applets”).
`
`34.
`
`Indeed, firewalls and network gateways were well-known long before the priority date of
`
`the ‘494 Patent, and all firewalls and network gateways must necessarily have a receiver for receiving
`
`files to be processed. See, e.g., U.S. Patent No. 6,065,118 (Ex. 30) at Claim 5 (“the execution location
`
`is provided with at least one firewall between the execut

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