throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`JUNIPER NETWORKS, INC.
`Petitioner
`
`v.
`
`IMPLICIT, LLC
`Patent Owner
`
`Case: IPR2020-00587
`Patent No. 9,591,104
`
`
`
`
`
`
`
`
`
`SUR-REPLY IN RESPONSE TO PETITION FOR INTER PARTES
`REVIEW OF U.S. PATENT NO. 9,591,104
`
`
`
`
`
`
`
`

`

`TABLE OF CONTENTS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Table of Authorities .................................................................................................. ii
`
`I.
`
`
`
`
`
`The Petition Relies on the Same Prior Art—Decasper ......................... 1
`
`The Petition Relies on Substantially the Same Prior Art—CheckPoint
`and Smith .............................................................................................. 2
`
`The First Prong of Advanced Bionics Applies ................................................ 1
`
`A.
`
`B.
`
`
`
`
`C.
`
`The Petition Presents Substantially the Same Arguments That Were
`Before the Patent Office ........................................................................ 3
`
`Juniper Has Not Demonstrated That the Patent Office Erred ......................... 5
`
`
`II.
`
`III. Conclusion ....................................................................................................... 7
`
`
`
`
`
`
`i
`
`

`

`
`
`TABLE OF AUTHORITIES
`
`
`Cases
`
`Acceleration Bay, LLC v. Activision Blizzard, Inc.,
`
`908 F.3d 765 (Fed. Cir. 2018) ......................................................................... 6
`
`Advanced Bionics, LLC v. MED-EL Elektromedizinische Geräte GmbH
`
`IPR2019-01469, Paper 6 (PTAB Dec. Feb. 13, 2020) .................................... 1
`
`Becton, Dickinson & Co. v. B. Braun Melsungen AG
`
`IPR2017-01586, Paper 8 (PTAB Dec. 15, 2017) ............................................ 5
`
`Colas Sols., Inc. v. Blacklidge Emulsions, Inc.,
`759 F. App’x 986 (Fed. Cir. 2019) (non-precedential) ................................... 6
`
`
`Intelligent Bio-Systems, Inc. v. Illumina Cambridge Ltd.,
`
`821 F.3d 1359 (Fed. Cir. 2016) ....................................................................... 6
`
`
`Statutes
`
`35 U.S.C. § 325(d) ..................................................................................................... 1
`
`
`
`
`
`
`
`ii
`
`

`

`
`
`Juniper fails to show that the Board should institute proceedings. It is
`
`undisputed that the Patent Office considered Decasper in detail and allowed the
`
`claims. That reality—which Juniper did not address in Reply—weighs heavily
`
`against instituting proceedings under the first prong of Advanced Bionics. Juniper
`
`also conceded in its Petition that it did not seek reversal of any alleged error made
`
`during prosecution. Pet. at 15. That forecloses additional review under the second
`
`prong of Advanced Bionics. And it ends the inquiry under Section 325(d).
`
`In Reply, Juniper focuses on two different references—CheckPoint and
`
`Smith—as providing a reason to institute proceedings. But Juniper only relies on
`
`those references for disclosure of supposed “trivial ‘TCP’ limitations,” Reply, at 1.
`
`And, for that disclosure, these references are the same in substance as what the Patent
`
`Office already considered during prosecution when it allowed these claims. And,
`
`again, Juniper did not allege in its Petition that the Patent Office erred. Section
`
`325(d) forecloses further review.
`
`I.
`
`The First Prong of Advanced Bionics Applies
`
`A. The Petition Relies on the Same Prior Art—Decasper
`
`It is undisputed that (1) both grounds in the Petition are based on the Decasper
`
`reference and (2) the Decasper reference was front-and-center during prosecution of
`
`the Implicit Patents. Juniper does not contest those facts. It instead flips around the
`
`references to call CheckPoint and Smith (and not Decasper) the “primary”
`
`
`
`1
`
`

`

`
`
`references. But Juniper’s Reply exposes that mislabeling: Juniper relies on
`
`CheckPoint and Smith for the supposed “trivial ‘TCP’ limitations” of the claims,
`
`Reply, at 1, while it relies on Decasper’s teaching for every other limitation (e.g.,
`
`receiving packets of a message, creating a path, storing the path, processing
`
`subsequent packets using the path, etc…).
`
`Decasper is the primary reference for both of Juniper’s proposed grounds.
`
`The Patent Office considered that reference, and Implicit addressed that reference in
`
`detail during prosecution. This weighs against instituting proceedings here.
`
`B.
`
`The Petition Relies on Substantially the Same Prior Art—
`CheckPoint and Smith
`
`CheckPoint and Smith were also before the Patent Office in substance (and,
`
`in the case of CheckPoint, by name). With regard to CheckPoint, Juniper does not
`
`dispute that two CheckPoint references were before the Patent Office during
`
`prosecution. Juniper also does not contend that, for the issues in its Petition, the
`
`substance in its “new” CheckPoint reference is different from the prior CheckPoint
`
`references. See Reply, at 5.
`
`Juniper instead points to different words from the new CheckPoint reference,
`
`specifically “application-layer ‘Security Server’” and the “Content Vectoring
`
`Protocol (CVP).” Reply, at 5. These different words, however, do not change the
`
`analysis. Juniper relies on those disclosures for their alleged application-layer
`
`processing. See Pet. at 54–57. That is the same supposed teaching reproduced in
`
`
`
`2
`
`

`

`
`
`the dozen-plus instances from the two prior CheckPoint references that Implicit cited
`
`in its Response. See Resp. at 10–12. And, critically, Juniper does not contest that
`
`fact in Reply. It does not allege that either of these “new” disclosures from
`
`CheckPoint are different in substance from what the prior references already
`
`disclosed. That weighs against institution.
`
`The same is true for Smith. Juniper asserts that Smith contains new subject
`
`matter because it is at an “endpoint of [two] TCP connections” and contains a
`
`“Caching Web Documents” feature that uses HTTP. Reply, at 4. But that subject
`
`matter was before the Patent Office in other references. Those references disclose
`
`gateways that can operate as endpoints. See, e.g., Ex. 2011, at 163 (depicting
`
`gateway as endpoint for communications with Computer A and Computer B); Ex.
`
`2012, at 16 (“[O]ur approach towards performing QoS control was an end-to-end
`
`solution, i.e., adaptation was achieved at the end points of a video conferencing
`
`session.”). They also disclose the use of HTTP. See, e.g., Resp. at 11–12 (collecting
`
`citations to CheckPoint references, including HTTP). And, like its new CheckPoint
`
`reference, Juniper does not explain how Smith is materially different than what the
`
`Patent Office considered during prosecution. Because Smith and CheckPoint are at
`
`most cumulative, the first prong of Advanced Bionics is satisfied.
`
`C. The Petition Presents Substantially the Same Arguments
`That Were Before the Patent Office
`
`Juniper’s Petition presents the same subject matter that the Patent Office
`
`
`
`3
`
`

`

`
`
`considered during prosecution. That satisfies the first prong of Advanced Bionics.
`
`In addition, substantially the same arguments were before the Patent Office. During
`
`reexamination of the Implicit Patent family, Juniper made the same arguments
`
`regarding Decasper that it makes here, namely that Decasper could be implemented
`
`in a firewall or gateway. See, e.g., Resp. at 16–17 (citing instances in which Juniper
`
`asserted that “Decasper98 teaches ‘a firewall plugin’” and “Decasper98 teaches an
`
`architecture that is ‘very well suited to Application Layer Gateways . . . and to
`
`security devices like Firewalls’”). Juniper does not contest that fact in Reply.
`
`Juniper instead ignores these statements. It contends that its arguments for
`
`Smith are new because there allegedly was not “any consideration of how the
`
`Decasper framework would be beneficially incorporated into this type of ALG.”
`
`Reply, at 4 (emphasis added). But Juniper’s own Petition shows that this position is
`
`wrong: the Petition relies on the exact same disclosure as above to assert a
`
`motivation to combine Decasper with Smith. Pet. at 20 (“As detailed below, it was
`
`obvious to apply Decasper to Smith, particularly since Decasper explains that its
`
`“framework is also very well suited to Application Layer Gateways (ALGs), and to
`
`security devices like Firewalls.”) (emphases in original).
`
`Juniper also argues that the Board should ignore its prior arguments regarding
`
`CheckPoint because those arguments related to “different limitations.” Reply, at 4.
`
`That misses the point. During prosecution of the Implicit Patents, Implicit
`
`
`
`4
`
`

`

`
`
`specifically pointed the Examiner to the reexamination record of the Implicit Patent
`
`family, disclosed the CheckPoint references, and amended the claims to add the
`
`limitations requiring executing TCP and converting packets from TCP to another
`
`format (such as an application-level format). If that functionality were “trivial,” the
`
`Examiner had the material to make the rejection, including Juniper’s arguments
`
`about CheckPoint and Decasper. The Examiner declined to do so, and allowed the
`
`claims. Juniper disagrees and recycles those arguments in its Petition. But it is not
`
`the purpose of Inter Partes Review to second guess the Examiner’s decision. Thus,
`
`under either route, the first prong of Advanced Bionics is satisfied in this case.
`
`II.
`
`Juniper Has Not Demonstrated That the Patent Office Erred
`
`Juniper has not demonstrated error. Indeed, Juniper’s Petition conceded that
`
`it was not basing its Petition on an error. It asserted that the error during examination
`
`factor (Becton, Dickinson factor (e)) “do[es] not apply in the instant action”:
`
`the examiner’s
`Although Petitioner disagrees with
`apparent finding that Decasper fails to disclose the added
`TCP limitations, this Petition does not rely on a reversal of
`any such finding. Instead, the challenge here uses other
`references for the allegedly missing limitation. Hence,
`these two [Becton, Dickinson] factors [(e) and (f)] do not
`apply in the instant action.
`
`Pet. at 15. Juniper also did not point to new evidence in its Petition as justifying
`
`review, other than the “other references” its presented besides Decasper (i.e.,
`
`CheckPoint and Smith).
`
`
`
`5
`
`

`

`
`
`Juniper then changed positions in Reply. It now asserts that the Examiner
`
`committed “material error,” including its decision to “not challenge Implicit’s
`
`mischaracterization of Decasper as limited to an IP router implementation.” Reply,
`
`at 6. It points to its “detailed expert evidence” as supporting review. Id. at 7.
`
`None of those positions were in Juniper’s Petition, and, for that reason,
`
`Juniper has waived them. See, e.g., Intelligent Bio-Systems, Inc. v. Illumina
`
`Cambridge Ltd., 821 F.3d 1359, 1369–70 (Fed. Cir. 2016) (finding that Board
`
`properly excluded Reply Brief under 37 C.F.R. § 42.23(b) where the Brief raised an
`
`“entirely new rationale” that was not raised in the Petition); Acceleration Bay, LLC
`
`v. Activision Blizzard, Inc., 908 F.3d 765, 775 (Fed. Cir. 2018) (finding that the
`
`Board properly excluded new argument in Reply that was “not made in the petition,”
`
`even though the petition “had an opportunity to present this argument in its petition,
`
`but chose not to”); Colas Sols., Inc. v. Blacklidge Emulsions, Inc., 759 F. App’x 986,
`
`990 (Fed. Cir. 2019) (non-precedential) (upholding Board’s exclusion of theory
`
`raised in Reply brief where the Petitioner “fail[ed] to point to a single line of its
`
`original Petition articulating this theory”). Because Juniper did not demonstrate
`
`error in its Petition—and, in fact, conceded the point—Juniper has not carried its
`
`burden on this factor.
`
`Juniper’s new arguments in Reply are also wrong on the merits. The
`
`Examiner did not overlook art or arguments. Implicit addressed Decasper in detail
`
`
`
`6
`
`

`

`
`
`and specifically pointed the examiner to the reexamination file histories (in which
`
`Decasper rendered claims unpatentable and contain the same arguments that Juniper
`
`makes here). Implicit submitted the relevant prior art subject matter that Juniper
`
`recycles in its Petition. Implicit amended the claims to add the TCP-related
`
`limitations and explained, in detail, why the claims were patentable. The Examiner
`
`had the art and arguments to make the rejections that Juniper now requests, and
`
`Decasper was front-and-center. The Examiner decided to allow the claims.
`
`Juniper has not demonstrated an error during prosecution that warrants re-
`
`plowing the same ground. It has not pointed to any particular error in the Examiner’s
`
`findings. It has not provided new prior art subject matter to demonstrate an error.
`
`And it has not pointed to any arguments or evidence beyond what was already in
`
`front of the Office during examination via the reexamination history, viz., that
`
`Decasper “teaches ‘a firewall plugin’” and teaches “architecture that is ‘very well
`
`suited to Application Layer Gateways . . . and to security devices like Firewalls.”
`
`Juniper may believe the Examiner’s decision is incorrect. But that is insufficient to
`
`meet Juniper’s burden under the second prong of Advanced Bionics.
`
`III. CONCLUSION
`
`For the reasons set forth above, Patent Owner respectfully requests that the
`
`Board decline to institute proceedings in this case under Section 325(d).
`
`
`
`
`
`
`
`7
`
`

`

`
`
`Dated: June 23, 2020
`
`
`
`
`
`Respectfully submitted,
`
`DAVIS FIRM, PC
`
`By:/s/Christian J. Hurt
`Christian J. Hurt
`
`8
`
`
`
`
`
`

`

`
`
`CERTIFICATE OF COMPLIANCE
`
`I hereby certify that the foregoing Preliminary Response complies with the
`
`type-volume limitation and general format requirements pursuant to 37 C.F.R.
`
`§§42.24 and 42.6. I further certify that this response contains seven pages or less
`
`per the Board’s Order, excluding parts exempted by 37 C.F.R. §42.24.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/Christian J. Hurt
`Christian J. Hurt
`
`
`
`9
`
`

`

`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on June 23, 2020, a true copy of the following
`
`document(s):
`
`PATENT OWNER IMPLICIT, LLC’S SUR-REPLY PETITION FOR
`INTER PARTES REVIEW OF U.S. PATENT NO. 9,591,104
`was served as follows:
`
`Rory P. Shea
`shea@ls3ip.com
`Cole B. Richter
`richter@ls3ip.com
`George I. Lee
`lee@ls3ip.com
`Michael P. Boyea
`boyea@ls3ip.com
`Lee Sullivan Shea & Smith LLP
`224 North Desplaines Street, Suite 250
`Chicago, IL 60661
`
`
`I declare under penalty of perjury under the laws of the United States of
`
`America that the foregoing is true and correct. Executed on June 23, 2020 at
`
`Dallas, Texas.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/Christian J. Hurt
`Christian J. Hurt
`
`10
`
`

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