Presentation of Petitioner Apple Inc.
`
`IPR2015-00866
`IPR2015-00868
`IPR2015-00870
`IPR2015-00871
`
`U.S. Patent No. 8,458,341
`U.S. Patent No. 8,516,131
`U.S. Patent No. 8,560,705
`
`Apple Inc. v. VirnetX Inc., IPR2015-00866
`Apple Inc. v. VirnetX Inc., IPR2015-00868
`Apple Inc. v. VirnetX Inc., IPR2015-00870
`Apple Inc. v. VirnetX Inc., IPR2015-00871
`Petitioner Apple Inc. – Ex. 1072
`
`1
`
`
`
`IPR2015-00866
`IPR2015-00868
`IPR2015-00870
`IPR2015-00871
`
`U.S. Patent No. 8,458,341
`U.S. Patent No. 8,516,131
`U.S. Patent No. 8,560,705
`
`Apple Inc. v. VirnetX Inc., IPR2015-00866
`Apple Inc. v. VirnetX Inc., IPR2015-00868
`Apple Inc. v. VirnetX Inc., IPR2015-00870
`Apple Inc. v. VirnetX Inc., IPR2015-00871
`Petitioner Apple Inc. – Ex. 1072
`
`1
`
`
`
`1.
`
`2.
`
`3.
`
`IPR2015-00866, -868 & -870
`Beser and RFC 2401
`Grounds
`IPR2015-00866 (’341 patent)
`A. Ground 1: Whether Claims 1-11, 14-25, and 28 are
`obvious under 35 U.S.C. § 103 over Beser (Beser (Ex.
`1007)) and RFC 2401 (Ex. 1008)
`IPR2015-00868 (’131 patent)
`A. Ground 1: Whether Claims 1-10,13-22, and 25-27 are
`obvious under 35 U.S.C. § 103 over Beser (Beser (Ex.
`1007)) and RFC 2401 (Ex. 1008)
`IPR2015-00870 (’705 patent)
`A. Ground 1: Whether Claims 1-23 and 25-30 are obvious
`under 35 U.S.C. § 103 over Beser (Beser (Ex. 1007)) and
`RFC 2401 (Ex. 1008)
`B. Ground 2: Whether Claim 24 is obvious under 35 U.S.C.
`§ 103 over Beser, RFC 2401 and Brand (Ex. 1012)
`
`
`
`Petitioner Apple Inc. – Ex. 1072
`
`2
`
`
`
`’341 Patent, Claim 15
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at Claim 15
`
`Petitioner Apple Inc. – Ex. 1072
`
`3
`
`
`
`’131 Patent, Claim 15
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 15
`
`Petitioner Apple Inc. – Ex. 1072
`
`4
`
`
`
`’705 Patent, Claim 1
`
`US8868705_Page_001.png
`
`Inst. Dec. at 5 (quoting ’705 Patent (Ex. 1050) at Claim 1)
`
`Petitioner Apple Inc. – Ex. 1072
`
`5
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`E.
`
`2.
`
`Petitioner Apple Inc. – Ex. 1072
`
`6
`
`
`
`Beser and RFC 2401 Grounds
`
`RFC 2401 (Ex. 1008) at 25; Pet. (866) at 25-26
`
`Petitioner Apple Inc. – Ex. 1072
`
`7
`
`Ex. 1007 (Beser) at Figs. 1 & 6; Pet. (866) at 18, 19
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A. “Virtual Private Network Communication Link” (866:
`claims; 868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`E.
`
`2.
`
`Petitioner Apple Inc. – Ex. 1072
`
`8
`
`
`
`The ’341 Claims:
`a “virtual private network communication link”
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`9
`
`
`
`Beser and RFC 2401
`a “virtual private network communication link”
`
`VPN Communication Link
`
`Patent Owner’s Construction
`Petitioner’s Construction
`a transmission path between two
`a communication path between two
`devices that restricts access to data,
`devices in a virtual private network,
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect
`addresses, or other information on
`where a virtual private network is a
`v3.01 Admin
`the path, generally using obfuscation
`network of computers which
`methods to hide information on the
`privately and directly communicate
`path, including, but not limited to,
`with each other by encrypting traffic
`one or more of authentication,
`on insecure paths between the
`encryption, or address hopping
`devices where the communication is
`both secure and anonymous
`Pet. (866) at 14; Resp. (866) at 8
`
`US8868705_Page_001.png
`
`Petition
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect
`v3.01 Admin
`
`Pet. (866) at 31
`
`Petitioner Apple Inc. – Ex. 1072
`
`10
`
`
`
`Beser and RFC 2401
`a “virtual private network communication link”
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`Pet. (866) at 47
`
`Petitioner Apple Inc. – Ex. 1072
`
`11
`
`
`
`Patent Owner Assertion
`Patent Owner Does Not Address the Combination or its Claim Construction
`
`US8868705_Page_001.png
`
`Response (866) at 31
`
`Petitioner Apple Inc. – Ex. 1072
`
`12
`
`
`
`Patent Owner Admission
`Virtual Private Network
`
`US8868705_Page_001.png
`
`Response (866) at 17
`
`Response (866) at 19
`Petitioner Apple Inc. – Ex. 1072
`
`13
`
`
`
`Patent Owner Admission
`Virtual Private Network
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`Ex. 2008 at 24-25; Reply (866) at 15
`
`US8868705_Page_001.png
`
`Petitioner Apple Inc. – Ex. 1072
`
`14
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`E.
`
`2.
`
`Petitioner Apple Inc. – Ex. 1072
`
`15
`
`
`
`The Challenged Claims:
`“audio/video data”
`
`’341 Patent (Ex. 1001) at Claim 1
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 1
`
`’705 Patent (Ex. 1050) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`16
`
`
`
`Combining Beser and RFC 2401
`“audio/video data”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Pet. (866) at 31
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Pet. (866) at 33
`
`Petitioner Apple Inc. – Ex. 1072
`
`17
`
`
`
`Patent Owner Assertion
`Combining Beser and RFC 2401
`
`US8868705_Page_001.png
`
`Response (866) at 39
`
`Petitioner Apple Inc. – Ex. 1072
`
`18
`
`
`
`Final Written Decision in IPR2014-00237
`Combining Beser and RFC 2401
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2014-00237 at 41; Reply (866) at 2-3
`
`Petitioner Apple Inc. – Ex. 1072
`
`19
`
`
`
`Grounds Based on Beser and RFC 2401
` Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Beser (Ex. 1007) at 1:60-67; Pet. (866) at 27; Reply (866) at 6
`
`US8868705_Page_001.png
`
`Petitioner Apple Inc. – Ex. 1072
`
`20
`
`
`
`Grounds Based on Beser and RFC 2401
` Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at 2:18-35; Pet. (866) at 32; Reply (866) at 4, 6
`
`Petitioner Apple Inc. – Ex. 1072
`
`21
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been
`obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`Petitioner Apple Inc. – Ex. 1072
`
`E.
`
`2.
`
`22
`
`
`
`Beser and RFC 2401
` Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Beser (Ex. 1007) at 1:54-58; Pet. (866) at 27, 29-31
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Beser (Ex. 1007) at 2:1-5; Reply (866) at 4
`
`Petitioner Apple Inc. – Ex. 1072
`
`23
`
`
`
`Beser and RFC 2401
` Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`Beser (Ex. 1007) at 2:36-40; Reply (866) at 5
`
`US8868705_Page_001.png
`
`Petitioner Apple Inc. – Ex. 1072
`
`24
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a
`domain name associated with the second network
`[target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`Petitioner Apple Inc. – Ex. 1072
`
`E.
`
`2.
`
`25
`
`
`
`The Challenged Claims:
`“a request to look up an Internet Protocol (IP) address… based on a domain name”
`
`’341 Patent (Ex. 1001) at Claim 15
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 15
`
`’705 Patent (Ex. 1050) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`26
`
`
`
`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
`
`Pet. (866) at 35
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Ex. 1005 at ¶ 348; Pet. (866) at 37
`
`Petitioner Apple Inc. – Ex. 1072
`
`27
`
`
`
`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`
`US8868705_Page_001.png
`
`Response (866) at 27
`
`Petitioner Apple Inc. – Ex. 1072
`
`28
`
`
`
`Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`Beser (Ex. 1007) at Fig. 5; Reply (866) at 9-10
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect
`v3.01 Admin
`
`* * *
`
`Beser (Ex. 1007) at 11:23-58; Pet. (866) at 38
`
`Beser (Ex. 1007) at Fig. 6; Pet. (866) at 19-21, 38
`
`Petitioner Apple Inc. – Ex. 1072
`
`29
`
`
`
`Beser and RFC 2401
` Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at Fig. 9; Pet. (866) at 22-23
`
`Petitioner Apple Inc. – Ex. 1072
`
`30
`
`
`
`Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`Ex. 1005 at ¶¶ 344-45; Pet. (866) at 21
`
`Petitioner Apple Inc. – Ex. 1072
`
`31
`
`
`
`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
`
`Ex. 1005 at ¶ 348; Pet. (866) at 21, 37-38
`
`Petitioner Apple Inc. – Ex. 1072
`
`32
`
`
`
`The Challenged Claims vs. the Specification:
`“a request to look up an Internet Protocol (IP) address”
`
`’341 Patent (Ex. 1001) at Claim 15; ’131 Patent (Ex. 1003) at Claim 15
`
`US8868705_Page_001.png
`
`Patent Owner’s Specification
`
`’705 Patent (Ex. 1050) at Claim 1
`
`’341 Patent (Ex. 1001) at 40:39-44
`
`Petitioner Apple Inc. – Ex. 1072
`
`33
`
`
`
`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`
`US8868705_Page_001.png
`
`Response (866) at 26
`
`Petitioner Apple Inc. – Ex. 1072
`
`34
`
`
`
`Grounds Based on 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
`Beser (Ex. 1007) at 9:29-30; Pet. (866) 21-22, 38
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`Beser (Ex. 1007) at Fig. 6; Pet. (866) at 19-21
`
`Petitioner Apple Inc. – Ex. 1072
`
`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; Reply (866) at 6-8
`
`Petitioner Apple Inc. – Ex. 1072
`
`36
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`E. “Interception of the request to look up an Internet
`Protocol (IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`2.
`
`Petitioner Apple Inc. – Ex. 1072
`
`37
`
`
`
`The Challenged Claims:
`“Intercepting…a request to look up an Internet Protocol (IP) address…”
`
`’341 Patent (Ex. 1001) at Claim 15
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 15
`
`’705 Patent (Ex. 1050) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`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
`
`Pet. (866) at 35-36
`Petitioner Apple Inc. – Ex. 1072
`
`39
`
`
`
`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
`
`Beser (Ex. 1007) at 8:38-43; Pet. (866) at 20, 36-37
`
`Petitioner Apple Inc. – Ex. 1072
`
`40
`
`
`
`Beser and RFC 2401
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`Interception of the Request
`Petitioner’s Construction
`Patent Owner’s Construction
`Receiving a request pertaining to a
`No construction necessary;
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect
`first entity at another entity
`
`alternatively, receiving a request to
`
`look up an internet protocol address
`v3.01 Admin
`and, apart from resolving it into an
`address, performing an evaluation
`on it related to establishing a virtual
`private network communication link
`Pet. (866) at 9-10; Resp. (866) at 8
`
`Reply:
`
`US8868705_Page_001.png
`
`Reply (866) at 31
`
`Petitioner Apple Inc. – Ex. 1072
`
`41
`
`
`
`Patent Owner Admission
` Dr. Monrose: tunneling requests are not addressed to the trusted device
`
`US8868705_Page_001.png
`
`Response (866) at 30-31
`
`Ex. 1066 at 101:11-14; Reply (866) at 14-15
`
`Petitioner Apple Inc. – Ex. 1072
`
`42
`
`
`
`The Challenged Patents
` “intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at 40:26-28
`
`Ex. 1005 at ¶ 73; Pet. (866) at 10
`
`Petitioner Apple Inc. – Ex. 1072
`
`43
`
`
`
`Patent Owner Admission
`Dr. Monrose: has no opinion about what “intercepting” requires
`
`US8868705_Page_001.png
`
`Ex. 1066 at 132:7-13; Reply (866) at 14
`
`Petitioner Apple Inc. – Ex. 1072
`
`44
`
`
`
`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; Reply (866) at 7-8
`
`Petitioner Apple Inc. – Ex. 1072
`
`45
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A. “Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A.
`“email” and “secure domain name”
`
`
`E.
`
`2.
`
`Petitioner Apple Inc. – Ex. 1072
`
`46
`
`
`
`The ’341 and ’131 Claims:
` “receiving” an “indication” and the “requested IP address”
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at Claim 1
`
`’131 Patent (Ex. 1003) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`47
`
`
`
`Patent Owner Assertion
`Beser does not show both “an indication” and a “network address”
`
`US8868705_Page_001.png
`
`Response (868) at 36-37
`
`Petitioner Apple Inc. – Ex. 1072
`
`48
`
`
`
`Grounds Based on Beser and RFC 2401
`Beser teaches “an indication” and a “network address”
`
`US8868705_Page_001.png
`
`Pet. (866) at 40
`
`Beser (Ex. 1007) at 21:48-54; Pet. (866) at 40; Reply (866) at 17
`Petitioner Apple Inc. – Ex. 1072
`49
`
`
`
`IPR2015-00866, -868, -870
` Beser and RFC 2401 Issues
`
`1. Common Issues (866, 868, & 870)
`A.
`“Virtual Private Network Communication Link” (866: claims;
`868: claim 10; 870: claims 6 & 21)
`B. Encrypting audio/visual data
`C. Combining Beser and RFC 2401 would have been obvious
`D. A “request to look up an []IP address… based on a domain
`name associated with the second network [target] device”
`“Interception of the request to look up an Internet Protocol
`(IP) address”
`Issues Affecting 866 & 868 Only
`A.
`“Receiv[ing]. . . An Indication [and] a Network Address”
`3. Dependent Claims
`A. “email” and “secure domain name”
`
`
`E.
`
`2.
`
`Petitioner Apple Inc. – Ex. 1072
`
`50
`
`
`
`’341 Patent, Claim 4, 5, 18, and 19
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at Claim 4, 5, 18, and 19
`
`Petitioner Apple Inc. – Ex. 1072
`
`51
`
`
`
`Beser and RFC 2401
`“email”
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at 10:55-66; Pet. (866) at 51
`
`Petitioner Apple Inc. – Ex. 1072
`
`52
`
`
`
`Beser and RFC 2401
`“email”
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`Ex. 1005 at ¶ 351; Pet. (866) at 51
`
`Petitioner Apple Inc. – Ex. 1072
`
`53
`
`
`
`’705 Patent, Claim 7 and 22
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1050) at Claim 7 and 22
`
`Petitioner Apple Inc. – Ex. 1072
`
`54
`
`
`
`Beser and RFC 2401
`“secure domain name”
`
`Beser (Ex. 1007) at 11:22-28; Pet. (870) at 49
`
`US8868705_Page_001.png
`
`Petitioner Apple Inc. – Ex. 1072
`
`55
`
`
`
`Final Written Decision in IPR2014-00481
`“secure domain name”
`
`Final Written Decision, IPR2014-00482 at 13; Reply (871) at 3-4; Pet. (866) at 15
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2014-00482 at 13-14; Reply (871) at 3-4; Pet. (866) at 15
`
`Petitioner Apple Inc. – Ex. 1072
`
`56
`
`
`
`Patent Owner Admission
`“secure domain name”
`
`US8868705_Page_001.png
`
`Ex. 1069 at 9; Reply (870) at 17
`
`Petitioner Apple Inc. – Ex. 1072
`
`57
`
`
`
`Beser and RFC 2401
`“secure domain name”
`
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at 10:38-45; Pet. (870) at 48-49
`
`Petitioner Apple Inc. – Ex. 1072
`
`58
`
`
`
`IPR2015-00871
`
`Grounds
`1. Whether Claims 1-23 and 25-30 are obvious under
`35 U.S.C. § 103 over Aventail (Ex. 1009), and RFC
`2401 (Ex. 1008), and RFC 2543 (Ex. 1013)
`
`2. Whether Claim 24 is obvious under 35 U.S.C. § 103
`over Aventail (Ex. 1009), and RFC 2401 (Ex. 1008),
`RFC 2543 (Ex. 1013), and Brand (Ex. 1012)
`
`
`Petitioner Apple Inc. – Ex. 1072
`
`59
`
`
`
`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 10; Pet. at 22, 33
`
`
`Aventail (Ex. 1009) at 72
`Pet. at 20
`
`Petitioner Apple Inc. – Ex. 1072
`
`60
`
`
`
`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
`Pet. at 36-37, passim
`
`Petitioner Apple Inc. – Ex. 1072
`
`61
`
`
`
`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
`Pet. at 36-37, passim
`
`Petitioner Apple Inc. – Ex. 1072
`
`62
`
`
`
`IPR2015-00871
` Aventail, RFC 2401, and RFC 2543 Issues
`
`1. Aventail, RFC 2401, and RFC 2543 Issues
`A. Aventail and the RFCs teach a “Determination as a
`Result of the Request that the Target Device Is a
`Device with which a Secure Communication Link
`Can be Established” (claims 1, 16)
`B. Aventail and the RFCs teach a “Secure
`Communications Link” between the Client and Target
`Devices (claims 1, 16) and a “VPN” (claims 6, 21)
`
`
`
`Petitioner Apple Inc. – Ex. 1072
`
`63
`
`
`
`’705 Patent, Claim 1
` Aventail, RFC 2401, and RFC 2543 Issues
`
`US8868705_Page_001.png
`
`Inst. Dec. at 5-6 (quoting ’705 Patent (Ex. 1050) at Claim 1)
`
`Petitioner Apple Inc. – Ex. 1072
`
`64
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Pet. at 39
`Admin
`Reply at 4-5
`
`US8868705_Page_001.png
`
`Pet. at 38-39
`
`Petitioner Apple Inc. – Ex. 1072
`
`65
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 10
`Pet. at 22, 33, 39
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`
`Petitioner Apple Inc. – Ex. 1072
`
`66
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 10
`Pet. at 22, 33, 39
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 73
`Pet. (871) at 24, 39
`
`Petitioner Apple Inc. – Ex. 1072
`
`67
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`US8868705_Page_001.png
`
`Reply (871) at 5-6
`
`Petitioner Apple Inc. – Ex. 1072
`
`68
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`Pet. at 39; Reply at 4-5
`
`US8868705_Page_001.png
`
`Pet. (871) at 40
`Petitioner Apple Inc. – Ex. 1072
`
`69
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`Pet. at 36-37, passim
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`Pet. at 36-37, passim
`
`Petitioner Apple Inc. – Ex. 1072
`
`70
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1011) at 19
`Pet. at 19; Reply at 8-9
`
`Petitioner Apple Inc. – Ex. 1072
`
`71
`
`
`
`Patent Owner Assertion
`“a determination as a result of the request”
`
`US8868705_Page_001.png
`
`Resp. (871) at 34-35
`
`Petitioner Apple Inc. – Ex. 1072
`
`72
`
`
`
`’705 Patent, Claim 1
` “a determination as a result of the request”
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1050) at 40:57-63; Reply at 8
`
`Petitioner Apple Inc. – Ex. 1072
`
`73
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“a determination as a result of the request”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`US8868705_Page_001.png
`
`Aventail (Ex. 1009) at 11-12
`
`Petitioner Apple Inc. – Ex. 1072
`
`74
`
`
`
`IPR2015-00871
` Aventail, RFC 2401, and RFC 2543 Issues
`
`1. Aventail, RFC 2401, and RFC 2543 Issues
`A. Aventail and the RFCs teach a “Determination as a
`Result of the Request that the Target Device Is a
`Device with which a Secure Communication Link Can
`be Established” (claims 1, 16)
`B. Aventail and the RFCs teach a “Secure
`Communications Link” between the Client and
`Target Devices (claims 1, 16) and a “VPN” (claims
`6, 21)
`
`
`
`Petitioner Apple Inc. – Ex. 1072
`
`75
`
`
`
`“Secure Communication Link” and “[VPN] Link”
`
`’705 Patent (Ex. 1050) at Claim 16
`
`’705 Patent (Ex. 1050) at Claim 21
`
`Secure Communication Link
`
`US8868705_Page_001.png
`Patent Owner’s Construction
`Petitioner’s Construction
`A transmission path that restricts access
`A direct communication link that
`to data, addresses, or other information
`provides data security through
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect
`on the path, generally using obfuscation
`encryption
`v3.01 Admin
`methods to hide information on the path,
`including, but not limited to, one or more
`of authentication, encryption, or address
`hopping
`
`Pet. (871) at 11-12; Resp. (871) at 5
`
`Petitioner Apple Inc. – Ex. 1072
`
`76
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“[Direct] secure communications link”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`US8868705_Page_001.png
`
`Aventail (Ex. 1009) at 60; Pet. at 46; Reply at 10
`
`Petitioner Apple Inc. – Ex. 1072
`
`77
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“[Direct] secure communications link”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`US8868705_Page_001.png
`
`Aventail (Ex. 1009) at 60; Pet. at 46; Reply at 10
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01
`Admin Guide_Page_010.png
`
`RFC 2401 (Ex. 1008) at 26; Pet. at 29, 44
`
`Petitioner Apple Inc. – Ex. 1072
`
`78
`
`
`
`Grounds Based on Aventail and RFCs 2401 & 2543
`“[Direct] secure communications link”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01
`Admin Guide_Page_010.png
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 72; Pet. (871) at 35, 44-45
`
`Petitioner Apple Inc. – Ex. 1072
`
`79
`
`
`
`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 72
`Pet. at 20
`
`Petitioner Apple Inc. – Ex. 1072
`
`80
`
`
`
`Final Written Decision in IPR2014-00481
`“secure communication link” & “VPN link”
`
`US8868705_Page_001.png
`
`Final Written Decision, IPR2014-00481 at 10; Reply (871) at 2, 3; Pet. (866) at 14, 26
`
`Petitioner Apple Inc. – Ex. 1072
`
`81
`
`
`
`Declaration of Christopher A. Hopen
`
`
`
`
`
`US8868705_Page_001.png
`
`Petition (871) at 18
`Reply at 16-17
`Ex. 1023
`
`Petitioner Apple Inc. – Ex. 1072
`
`82
`
`
`
`Cross-Examination of Christopher A. Hopen
`
`
`
`
`
`Paper 33 at 5
`Ex. 1057 at 191:12-16
`
`US8868705_Page_001.png
`
`Paper 33 at 5
`Ex. 1057 at 183:2-13
`Petitioner Apple Inc. – Ex. 1072
`
`83
`
`
`
`Declaration of James Chester
`
`
`
`
`
`US8868705_Page_001.png
`
`Petition (871) at 18
`Reply at 17
`Ex. 1022
`Petitioner Apple Inc. – Ex. 1072
`
`84
`
`
`
`Declaration of Michael Allyn Fratto
`
`
`
`
`
`US8868705_Page_001.png
`
`Petition (871) at 18
`Reply at 17
`Ex. 1043
`Petitioner Apple Inc. – Ex. 1072
`
`85
`
`
`
`Exhibit I to
`Declaration of Michael Allyn Fratto
`
`
`
`
`Ex. 1043 at ¶13; Paper 33 at 3
`
`US8868705_Page_001.png
`
`Ex. 1043 at 275
`
`Petitioner Apple Inc. – Ex. 1072
`
`86
`
`
`
`RFCs
`
`
`
`Petitioner’s Expert, Dr. Tamassia
`
`
`
`Petitioner’s Expert, Dr. Tamassia
`
`US8868705_Page_001.png
`
`Ex. 1005 at ¶187; Ex. 1036 at 6; 866 Pet. at 24
`
`Ex. 2019 at 103:1-13; Reply (866) at 21
`
`Petitioner Apple Inc. – Ex. 1072
`
`87
`
`
`
`RFCs
`
`
`
`
`
`US8868705_Page_001.png
`
`US8868705_Page_001.png
`
`Ex. 1063 at 10:5-11, 40:20-24; Reply (866) at 20
`
`Ex. 1008 at 1; 866 Pet. at 24
`
`Petitioner Apple Inc. – Ex. 1072
`
`88
`
`
`
`RFCs
`
`NetworkWorld, Mar. 15, 1999
`
`InfoWorld, Aug. 16, 1999
`
`Ex. 1065 at 3; 866 Reply at 20
`
`Ex. 1064 at 9; 866 Reply at 20
`
`Petitioner Apple Inc. – Ex. 1072
`
`89
`
`
`
`Patent Owner Admission
`RFC 2401
`
`US8868705_Page_001.png
`
`Ex. 2008 at 24-25; Reply (866) at 15
`
`Ex. 2008 at 19; Reply (866) at 15
`
`Ex. 2008 at 21; Reply (866) at 15
`
`Petitioner Apple Inc. – Ex. 1072
`
`90
`
`
`
`Patent Owner Admission
` RFC 2401
`
`Ex. 2009 (Dr. Monrose) at ¶16; Prelim. Resp. (866) at 37 (citing Ex. 2009 at ¶16)
`
`US8868705_Page_001.png
`
`Response (866) at 19
`
`Petitioner Apple Inc. – Ex. 1072
`
`91
`
`
`
`’341 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`92
`
`
`
`’341 Patent, Claim 17
`
`US8868705_Page_001.png
`
`’341 Patent (Ex. 1001) at Claim 17
`
`Petitioner Apple Inc. – Ex. 1072
`
`93
`
`
`
`’131 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1072
`
`94
`
`
`
`’131 Patent, Claim 2, 3, and 16
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 2, 3, and 16
`
`Petitioner Apple Inc. – Ex. 1072
`
`95
`
`
`
`’131 Patent, Claim 10
`
`US8868705_Page_001.png
`
`’131 Patent (Ex. 1003) at Claim 10
`
`Petitioner Apple Inc. – Ex. 1072
`
`96
`
`
`
`’705 Patent, Claim 16
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1050) at Claim 16
`
`Petitioner Apple Inc. – Ex. 1072
`
`97
`
`
`
`’705 Patent, Claim 3, 6, and 21
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1050) at Claim 3, 6, and 21
`
`Petitioner Apple Inc. – Ex. 1072
`
`98
`
`
`
`’705 Patent, Claim 4 and 20
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1050) at Claim 4 and 20
`
`Petitioner Apple Inc. – Ex. 1072
`
`99
`
`
`
`’705 Patent, Claim 13 and 28
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1050) at Claim 13 and 28
`
`Petitioner Apple Inc. – Ex. 1072
`
`100
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
