- Juniper Networks, Inc. v. Finjan, Inc.No claims unpatentablePTAB · Apr 7, 2020 · IPR2019-00026 · APJ Charles J Boudreau · IPR · Final written decision
Claims 1, 15, and 41 were not shown unpatentable: Abadi did not identify suspicious code in its annotations, and the Abadi and Gryaznov combination did not cure that deficiency.
RulingsFinal written decision- Skill levelOther
“differences between the claimed subject matter and the prior art are “such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations, including (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; 2 Abadi et al., U.S. Patent No. 6,253,370 B1, issued June 26, 2001 (filed Dec. 1, 1997) (Ex. 1008, “Abadi”). 3 Dmitry O. Gryaznov, Scanners of the Year 2000: Heuristics, Virus Bull. Conf. 225 (Sept. 1995) (Ex. 1009, 2–11, “Gryaznov”). (3) the level of skill in the art; and (4) when in evidence, objective evidence of nonobviousness, i.e., secondary considerations. Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966). “To satisfy its burden of proving obviousness, a petitioner cannot employ mere conclusory statements. The petitioner must instead articulate specific reasoning, based on evidence of record, to support the legal conclusion of obviousness.” In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016). We analyze the asserted grounds with the principles stated above in mind.” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“Having considered the parties’ arguments, we see no reason to disturb their agreed construction of “Downloadable” as “an executable application program, which is downloaded from a source computer and run on the destination computer,” with which the parties state their express agreement. We clarify in Section II.D.2. below that we agree with Patent Owner that the executable application program that is to be run on the destination computer must be the same executable application program that is downloaded from the source computer within the agreed construction. Sur-reply 1–2. This interpretation is not a question of the construction of the term “Downloadable” itself, but rather flows from the express language of the challenged claims, in which “the Downloadable” that is “ma[de] . . . available to web clients” in the final step of each of independent claims 1 and 41 has its antecedent basis in the first claim step, “receiving . . . a Downloadable.” Likewise, the antecedent in claim 15 for “the Downloadable” that is made available to web clients is the Downloadable in which suspicious code is identified by the content inspection engine. We also agree with Patent Owner that the claimed “linking” of a DSP “to the Downloadable” does not compel a different understanding because we are not persuaded that the linking contemplated in the ’844 patent requires modification of the code of the Downloadable itself. Sur-reply 2–3.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionDecided for patent owner
“Having considered the full record developed during trial, we agree with Patent Owner that the replacement of the word “profile” with “information” does not add any clarity to the meaning of this phrase and that the proper construction of “Downloadable security profile that identifies suspicious code in [the received / a] Downloadable” in the context of the ’844 patent is “profile that must at least include, but is not necessarily limited only to, an identification of hostile, potentially hostile, undesirable, or potentially undesirable code in the corresponding Downloadable.” PO Resp. 7–8. Regardless, we do not discern that the difference between the parties’ positions with respect to these phrases is dispositive of any issues in this proceeding.” slip op. at 14
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“generate an ID for the Downloadable.” PO Resp. 21 (emphasis added) (quoting Ex. 2015, 15), 23 (emphasis added) (citing Ex. 2015, 20). Based on Patent Owner’s arguments, we are not persuaded that the ’639 provisional demonstrates possession by the inventors of linking a DSP to the Downloadable “before a web server makes the Downloadable available to web clients.” Rather, by the time that the DSP has been linked to the Downloadable (e.g., by code scanner 325, in Patent Owner’s mapping), we understand that the Downloadable has already been received—and hence “made available”—by the web server. Notably, this conclusion does not depend on where the “linking” occurs—particularly, whether it may occur at a network gateway, a focus of the parties’ claim construction arguments (see, e.g., Pet. 25–27; PO Resp. 10–12; Section II.B.5, supra)—but instead on when it occurs relative to the Downloadable being made available to clients. Further, having considered the alleged Appendix to the ’639 provisional (Ex. 2015, 37–45), including portions cited by Dr. Butler in related litigation (see Ex. 2047), we are not persuaded that anything in the Appendix demonstrates possession of linking “before a web server makes the Downloadable available to web clients.” In conclusion, therefore, we are not persuaded that the inventors were in possession of the subject matter of the challenged claims at any time prior to the December 22, 1997, filing date of the ’648 application.” slip op. at 35
Patent outcomesUS 6,154,844 not shown unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 6,154,844
Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.