throbber
Presentation of Petitioner Apple Inc.
`
`IPR2016-00331
`IPR2016-00332
`
`U.S. Patent No. 8,504,696
`
`Apple Inc. v. VirnetX Inc., IPR2016-00331
`Apple Inc. v. VirnetX Inc., IPR2016-00332
`Petitioner Apple Inc. – Ex. 1078
`
`1
`
`

`

`1.
`
`2.
`
`IPR2016-00331, -332
`Grounds
`IPR2016-00331: Beser
`A. Ground 1: Whether Claims 1-11, 14-25, and 28-30 are
`obvious under 35 U.S.C. § 103 over Beser and RFC
`2401
`IPR2016-00332: Aventail
`A. Ground 1: Whether Claims 1, 4, 5, 9-11, 14-16, 19, 20,
`24, 25, 28, and 30 are obvious under 35 U.S.C. § 103
`over Aventail and RFC 2401
`B. Ground 2: Whether Claims 2, 3, 6-8, 17, 18, and 21-23
`are obvious under 35 U.S.C. § 103 over Aventail, RFC
`2401, and RFC 2543
`C. Ground 3: Whether Claims 15 and 30 are obvious
`under 35 U.S.C. § 103 over Aventail, RFC 2401, and
`Yeager
`
`Petitioner Apple Inc. – Ex. 1078
`
`2
`
`

`

`IPR2016-00331, -332
`Roadmap
`
`1. Estoppel
`2. Aventail
`3. Beser
`4. Prior Art Status / Motion to Exclude
`
`Petitioner Apple Inc. – Ex. 1078
`
`3
`
`

`

`’696 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’696 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`4
`
`

`

`Related Federal Circuit Decisions
`
`Appeal No. Patent
`
`PTO
`Proceedings
`
`Outcome
`
`Invalidating
`Reference(s)
`
`No. 2015-1934 8,504,697
`
`IPR2014-00237
`IPR2014-00238
`
`Affirmed,
`mandate issued
`
`No. 2016-1211 7,987,274
`
`IPR2014-00403
`IPR2014-00404
`
`Affirmed,
`mandate issued
`
`7,188,180
`
`IPR2014-00481
`IPR2014-00482
`
`Affirmed,
`mandate issued
`
`Wesinger
`
`Provino
`
`Provino
`
`No. 2016-1480 8,051,181 No. 95/001,949
`
`Affirmed,
`mandate issued
`
`Provino
`Mattaway
`
`Other
`Considered
`Reference(s)
`
`Beser
`RFC 2401
`
`Kiuchi
`
`Kiuchi
`
`Beser
`
`331 Paper 16 at 1-2
`
`Petitioner Apple Inc. – Ex. 1078
`
`5
`
`

`

`Patent Owner Estoppel
`
`§42.73 Judgment.
`(a) A judgment, except in the case of a termination, disposes of all issues that were, or by motion
`reasonably could have been, raised and decided.
`
`(b) Request for adverse judgment. A party may request judgment against itself at any time during a
`proceeding. Actions construed to be a request for adverse judgment include:
`(1) Disclaimer of the involved application or patent;
`(2) Cancellation or disclaimer of a claim such that the party has no remaining claim in the trial;
`(3) Concession of unpatentability or derivation of the contested subject matter; and
`(4) Abandonment of the contest.
`
`(d) Estoppel. …
`(3) Patent applicant or owner. A patent applicant or owner is precluded from taking action
`inconsistent with the adverse judgment, including obtaining in any patent:
`(i) A claim that is not patentably distinct from a finally refused or canceled claim; or
`(ii) An amendment of a specification or of a drawing that was denied during the trial
`proceeding, but this provision does not apply to an application or patent that has a different
`written description.
`
`37 C.F.R. § 42.73; 331 Reply 2-3; 331 Paper 18 at 3
`
`Petitioner Apple Inc. – Ex. 1078
`
`6
`
`

`

`Aventail Issues
`
`1. Aventail’s “Determination”
`
`2. Aventail’s “[VPN] Communication Link”
`
`Petitioner Apple Inc. – Ex. 1078
`
`7
`
`

`

`Grounds Based on Aventail and RFC 2401
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01
`Admin Guide_Page_010.png
`Aventail (Ex. 1009) at 10; 332 Pet. at 22, 38
`
`Aventail (Ex. 1009) at 72
`332 Pet. at 20-21
`
`Petitioner Apple Inc. – Ex. 1078
`
`8
`
`

`

`Grounds Based on Aventail and RFCs 2401 & 2543
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`332 Pet. at 22-23, passim
`
`Petitioner Apple Inc. – Ex. 1078
`
`9
`
`

`

`Grounds Based on Aventail and RFCs 2401 & 2543
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`Aventail (Ex. 1009) at 11-12
`332 Pet. at 22-23, passim
`
`Petitioner Apple Inc. – Ex. 1078
`
`10
`
`

`

`Aventail Issues
`
`1. Aventail’s “Determination”
`
`2. Aventail’s “[VPN] Communication Link”
`
`Petitioner Apple Inc. – Ex. 1078
`
`11
`
`

`

`’696 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’696 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`12
`
`

`

`Grounds Based on Aventail and RFC 2401
`“determin[ing] … whether the second network device is available”
`
`US8868705_Page_001.png
`
`332 Pet. 38-39
`
`Petitioner Apple Inc. – Ex. 1078
`
`13
`
`

`

`Patent Owner Assertion
`“determin[ing] … whether the second network device is available”
`
`US8868705_Page_001.png
`
`332 Resp. 23-24
`
`Petitioner Apple Inc. – Ex. 1078
`
`14
`
`

`

`Final Written Decision in IPR2015-00871
`“determin[ing] … whether the second network device is available”
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2015-00871 at 56-57; 332 Reply 7
`
`Petitioner Apple Inc. – Ex. 1078
`
`15
`
`

`

`Aventail Issues
`
`1. Aventail’s “Determination”
`
`2. Aventail’s “[VPN] Communication Link”
`
`Petitioner Apple Inc. – Ex. 1078
`
`16
`
`

`

`’696 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’696 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`17
`
`

`

`“Virtual Private Network Communication Link”
`
`US8868705_Page_001.png
`
`331 Reply 4-5
`
`Petitioner Apple Inc. – Ex. 1078
`
`18
`
`

`

`Grounds Based on Aventail and RFC 2401
`“[VPN] Communication Link”
`
`US8868705_Page_001.png
`
`332 Pet. 40-41
`
`Petitioner Apple Inc. – Ex. 1078
`
`19
`
`

`

`Patent Owner Assertion
`“[VPN] Communication Link”
`
`US8868705_Page_001.png
`
`332 Resp. 29
`
`Petitioner Apple Inc. – Ex. 1078
`
`20
`
`

`

`Final Written Decision in IPR2015-00871
`“[VPN] Communication Link”
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2015-00871 at 64; 332 Reply 4, 11
`
`Petitioner Apple Inc. – Ex. 1078
`
`21
`
`

`

`Beser Issues
`
`1. Beser’s “[VPN] Communication Link”
`
`2. Combination of Beser and RFC 2401
`
`3. Beser’s “Request to Look Up an [IP] address”
`
`4. Beser’s “Intercepting” the Request
`
`Petitioner Apple Inc. – Ex. 1078
`
`22
`
`

`

`Beser and RFC 2401 Grounds
`
`RFC 2401 (Ex. 1008), 25; 331 Pet. 27
`
`Petitioner Apple Inc. – Ex. 1078
`
`23
`
`Ex. 1007 (Beser) at Figs. 1 & 6; 331 Pet. 18-20
`
`

`

`Beser Issues
`
`1. Combination of Beser and RFC 2401
`
`2. Beser’s “[VPN] Communication Link”
`
`3. Beser’s “Request to Look Up an [IP] address”
`
`4. Beser’s “Intercepting” the Request
`
`Petitioner Apple Inc. – Ex. 1078
`
`24
`
`

`

`Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`331 Pet. 33
`
`Petitioner Apple Inc. – Ex. 1078
`
`25
`
`

`

`Patent Owner Assertion
`Combining Beser and RFC 2401
`
`US8868705_Page_001.png
`
`331 Resp. 36-37
`
`Petitioner Apple Inc. – Ex. 1078
`
`26
`
`

`

`Final Written Decision in IPR2014-00237
`Combining Beser and RFC 2401
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2014-00237 at 41; 331 Reply 7
`
`Petitioner Apple Inc. – Ex. 1078
`
`27
`
`

`

`Beser Issues
`
`1. Combination of Beser and RFC 2401
`
`2. Beser’s “[VPN] Communication Link”
`
`3. Beser’s “Request to Look Up an [IP] address”
`
`4. Beser’s “Intercepting” the Request
`
`Petitioner Apple Inc. – Ex. 1078
`
`28
`
`

`

`’696 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’696 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`29
`
`

`

`Patent Owner Assertion
`Patent Owner Does Not Address the Combination or its Claim Construction
`
`US8868705_Page_001.png
`
`331 Resp. 30-31
`
`Petitioner Apple Inc. – Ex. 1078
`
`30
`
`

`

`Final Written Decision in IPR2015-00866
`“[VPN] Communication Link”
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2015-00866 at 39; 331 Reply 18
`
`Petitioner Apple Inc. – Ex. 1078
`
`31
`
`

`

`Beser Issues
`
`1. Combination of Beser and RFC 2401
`
`2. Beser’s “[VPN] Communication Link”
`
`3. Beser’s “Request to Look Up an [IP] address”
`
`4. Beser’s “Intercepting” the Request
`
`Petitioner Apple Inc. – Ex. 1078
`
`32
`
`

`

`’696 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’696 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`33
`
`

`

`Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`331 Pet. 37
`
`Petitioner Apple Inc. – Ex. 1078
`
`34
`
`

`

`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`331 Resp. 24
`
`Petitioner Apple Inc. – Ex. 1078
`
`35
`
`

`

`Final Written Decision in IPR2014-00237
`“a request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2014-00237 at 24; 331 Reply 15
`
`Petitioner Apple Inc. – Ex. 1078
`
`36
`
`

`

`Beser Issues
`
`1. Combination of Beser and RFC 2401
`
`2. Beser’s “[VPN] Communication Link”
`
`3. Beser’s “Request to Look Up an [IP] address”
`
`4. Beser’s “Intercepting” the Request
`
`Petitioner Apple Inc. – Ex. 1078
`
`37
`
`

`

`’696 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’696 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`38
`
`

`

`Beser and RFC 2401
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`331 Pet. 38
`
`Petitioner Apple Inc. – Ex. 1078
`
`39
`
`

`

`Patent Owner Assertion
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`331 Resp. 27
`
`Petitioner Apple Inc. – Ex. 1078
`
`40
`
`

`

`Final Written Decision in IPR2014-00237
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2014-00237 at 24; 331 Reply 15
`
`Petitioner Apple Inc. – Ex. 1078
`
`41
`
`

`

`Final Written Decision in IPR2015-00871
`Motion to Exclude
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2015-00871 at 73; 332 Paper 23 at 1
`
`Petitioner Apple Inc. – Ex. 1078
`
`42
`
`

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