UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________________
`
`GOOGLE LLC,
`Petitioner,
`
`v.
`
`BLACKBERRY LTD.,
`Patent Owner.
`
`_________________
`
`Case IPR2017-01619
`Patent 8,489,868 B2
`_________________
`
`PETITIONER’S DEMONSTRATIVE EXHIBITS
`
`
`
`_________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________________
`
`GOOGLE LLC,
`Petitioner,
`
`v.
`
`BLACKBERRY LTD.,
`Patent Owner.
`
`_________________
`
`Case IPR2017-01619
`Patent 8,489,868 B2
`_________________
`
`PETITIONER’S DEMONSTRATIVE EXHIBITS
`
`
`
`Demonstratives of Petitioner Google LLC
`
`Inter Partes Reviews of
`U.S. Patent No. 8,489,868
`
`IPR2017-01619
`IPR2017-01620
`
`Oral Hearing: September 17, 2018
`
`1
`
`
`
`IPR2017-01619 – Instituted Grounds
`
`• Claims 1, 13, 76, 78, 81, 84, 85, 87, 88, 90-93, 95,
`98, 100, 104, 108, 112, 113, 137-39, and 142-44 as
`obvious over Garst and Gong;
`• Claims 77, 79, 80, and 82 as obvious over Garst,
`Gong, and Davis;
`• Claim 83 as obvious over Garst, Gong, and Chang;
`• Claim 86 as obvious over Garst, Gong, and Sibert;
`• Claim 89 as obvious over Garst, Gong, and Wong-
`Insley; and
`• Claim 94 as obvious over Garst, Gong, and
`Haddock.
`
`IPR2017-01619, Dec. (Paper 9) at 21
`
`2
`
`
`
`IPR2017-01620 – Instituted Grounds
`• Claims 1, 76, 78, 81, 84, 85, 90-92, 95, 104, 113,
`137, and 142 as anticipated by Lin;
`• Claims 13, 88, and 98 as obvious over Lin and
`Garst;
`• Claims 93, 100, 112, and 139 as obvious over Lin
`and Gong;
`• Claims 77, 79, 80, and 82 as obvious over Lin and
`Davis;
`• Claim 83 as obvious over Lin and Chang;
`• Claim 86 as obvious over Lin and Sibert;
`• Claim 89 as obvious over Lin and Wong-Insley; and
`• Claim 94 as obvious over Lin and Haddock.
`
`IPR2017-01920, Dec. (Paper 9) at 23
`
`3
`
`
`
`Representative Independent Claim
`
`’868 Patent (Ex. 1001) at Claim 1
`
`4
`
`
`
`Claim Construction
`
`Term
`“…wherein a signed
`software application
`includes a digital
`signature…”
`
`“signed software
`application”
`
`Petitioner
`“…a digital signature generated
`using a private key of a private
`key-public key pair
`corresponding to an entity with
`an interest in protecting access
`to the sensitive API…”
`Plain and ordinary meaning
`
`“sensitive API”
`
`“an API to which access is
`restricted on an application-by-
`application basis”
`
`Patent Owner
`No construction
`
`Board
`No construction
`
`“the signature is of the software
`application or a unique
`transformation of the software
`application, such as a hash or
`an abridging function”
`“an API classified as
`implicating a security concern”
`
`No construction
`
`* PO did not present a
`construction in POPR
`
`“an API to which [application]
`access is restricted [on an
`application-by-application
`basis]”
`
`“non-sensitive API”
`
`“abridged version of the
`software application”
`
`“an API to which access is not
`restricted on an application-by-
`application basis”
`Plain and ordinary meaning
`(i.e., shortened version of the
`software application)
`
`“a unique transformation of the
`software application that is
`* PO did not present a
`smaller than the software
`construction in POPR
`application”
`IPR2017-01619, Pet. (Paper 1) at 7-14; Reply (Paper 19) at 1-9; Resp. (Paper 16) at 6-22; Dec. (Paper 9) at 9-13
`IPR2017-01620, Pet. (Paper 1) at 7-14; Reply (Paper 19) at 1-2; Resp. (Paper 16) at 5-9; Dec. (Paper 9) at 9-13
`
`“an API that is not classified as
`implicating a security concern”
`
`“an API to which application
`access is not restricted”
`(IPR2018-01619)
`No construction
`
`5
`
`
`
`Claim Construction
`
`“Signed Software Application”
`(IPR2018-01619)
`
`“Sensitive API” / “Non-Sensitive API”
`(IPR2018-01619)
`
`“Abridged Version of the Software Application”
`(IPR2018-01619 & -01620)
`
`6
`
`
`
`Claim Construction
`
`“Signed Software Application”
`(IPR2018-01619)
`
`“Sensitive API” / “Non-Sensitive API”
`(IPR2018-01619)
`
`“Abridged Version of the Software Application”
`(IPR2018-01619 & -01620)
`
`7
`
`
`
`Claim Construction – “Signed Software Application”
`
`Petitioner
`Plain and ordinary
`meaning
`
`Patent Owner
`“the signature is of the
`software application or a
`unique transformation of
`the software application,
`such as a hash or an
`abridging function”
`
`Board
`No construction
`
`* PO did not present a
`construction in POPR
`
`IPR2017-01619, Reply (Paper 19) at 1-4
`
`IPR2017-01619, Resp. (Paper 16) at 6-15
`
`8
`
`
`
`Claim Construction – “Signed Software Application”
`
`’868 Patent (Ex. 1001) at Claim 1
`
`9
`
`
`
`Claim Construction – “Signed Software Application”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 4:36-55
`
`IPR2017-01619, Reply (Paper 20) at 2
`
`10
`
`
`
`Claim Construction – “Signed Software Application”
`
`Dr. McDaniel
`
`Dr. McDaniel Decl. (Ex. 1002) at ¶39
`
`IPR2017-01619, Reply (Paper 20) at 3-4
`
`11
`
`
`
`Claim Construction – “Signed Software Application”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 6:26-37
`
`IPR2017-01619, Reply (Paper 20) at 3-4
`
`12
`
`
`
`Claim Construction
`
`“Signed Software Application”
`(IPR2018-01619)
`
`“Sensitive API” / “Non-Sensitive API”
`(IPR2018-01619)
`
`“Abridged Version of the Software Application”
`(IPR2018-01619 & -01620)
`
`13
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`Petitioner
`sensitive API: “an API to
`which access is restricted
`on an application-by-
`application basis”
`
`Patent Owner
`sensitive API: “an API
`classified as implicating a
`security concern”
`
`Board
`sensitive API: “an API to
`which [application]
`access is restricted [on an
`application-by-
`application basis]”
`
`non-sensitive API: “an
`API to which access is
`not restricted on an
`application-by-
`application basis”
`
`non-sensitive API: “an
`API that is not classified
`as implicating a security
`concern”
`
`non-sensitive API: “an
`API to which application
`access is not restricted”
`(IPR2018-01619)
`
`IPR2017-01619, Reply (Paper 19) at 4-9
`
`IPR2017-01619, Resp. (Paper 16) at 16-21
`
`IPR2017-01619, Dec. (Paper 9) at 10-12
`IPR2017-01620, Dec. (Paper 9) at 10-12
`
`14
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`’868 Patent (Ex. 1001) at Claims 1, 112, 139
`
`15
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at Claim 117
`
`IPR2017-01619, Reply (Paper 20) at 5
`
`16
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 3:46-61
`
`IPR2017-01619, Reply (Paper 20) at 5
`
`17
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 1:36-50
`
`’868 Patent (Ex. 1001) at 5:51-65
`
`IPR2017-01619, Reply (Paper 20) at 6-7
`
`18
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 131:16-132:3
`
`IPR2017-01619, Reply (Paper 20) at 7-8
`
`19
`
`
`
`Claim Construction – “Sensitive API” / “Non-Sensitive API”
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 130:4-13
`
`IPR2017-01619, Reply (Paper 20) at 7-8
`
`20
`
`
`
`Claim Construction
`
`“Signed Software Application”
`(IPR2018-01619)
`
`“Sensitive API” / “Non-Sensitive API”
`(IPR2018-01619)
`
`“Abridged Version of the Software Application”
`(IPR2018-01619 & -01620)
`
`21
`
`
`
`Claim Construction – “Abridged . . . Software Application”
`
`Petitioner
`Plain and ordinary
`meaning (i.e., shortened
`version of the software
`application)
`
`Patent Owner
`“a unique transformation
`of the software
`application that is smaller
`than the software
`application”
`
`Board
`No construction
`
`* PO did not present a
`construction in POPR
`
`IPR2017-01619, Reply (Paper 19) at 9
`IPR2017-01620, Reply (Paper 19) at 1-2
`
`IPR2017-01619, Resp. (Paper 16) at 21-22
`IPR2017-01620, Resp. (Paper 16) at 8-9
`
`22
`
`
`
`Claim Construction – “Abridged . . . Software Application”
`
`’868 Patent (Ex. 1001) at Claim 86
`
`23
`
`
`
`Claim Construction – “Abridged . . . Software Application”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 6:16-19
`
`’868 Patent (Ex. 1001) at 6:29-37
`
`IPR2017-01619, Reply (Paper 20) at 9
`
`24
`
`
`
`Claim Construction – “Abridged . . . Software Application”
`
`Webster’s Dictionary (Ex. 2005)
`
`Webster’s Dictionary (Ex. 2005) at 3
`
`IPR2017-01619, Reply (Paper 20) at 9
`
`25
`
`
`
`IPR2017-01619: The Challenged Claims Are Obvious
`
`“Signed Software Application”
`“Sensitive API”
`Claim 112
`Claims 77, 79, 80, and 82
`Claim 86
`
`26
`
`
`
`IPR2017-01619: The Challenged Claims Are Obvious
`
`“Signed Software Application”
`“Sensitive API”
`Claim 112
`Claims 77, 79, 80, and 82
`Claim 86
`
`27
`
`
`
`“Signed Software Application” – Garst & Gong
`
`Garst
`
`Garst (Ex. 1012) at 9:17-21
`
`Garst (Ex. 1012) at 9:48-58
`
`IPR2017-01619, Reply (Paper 19) at 10-11
`
`28
`
`
`
`“Signed Software Application” – Garst & Gong
`
`Garst
`
`Garst (Ex. 1012) at 9:38-41
`
`IPR2017-01619, Reply (Paper 19) at 13-14
`
`29
`
`
`
`“Signed Software Application” – Garst & Gong
`
`Patent Owner
`
`IPR2017-01619, Resp. (Paper 16) at 30
`
`30
`
`
`
`“Signed Software Application” – Garst & Gong
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 182:3-185:14
`IPR2017-01619, Reply (Paper 19) at 14
`
`31
`
`
`
`“Signed Software Application” – Garst & Gong
`
`Gong
`
`Gong (Ex. 1016) at 26
`
`IPR2017-01619, Pet. (Paper 1) at 14
`
`32
`
`
`
`“Signed Software Application” – Garst & Gong
`
`Petitioner
`
`IPR2017-01619, Pet. (Paper 1) at 26-27
`
`33
`
`
`
`IPR2017-01619: The Challenged Claims Are Obvious
`
`“Signed Software Application”
`“Sensitive API”
`Claim 112
`Claims 77, 79, 80, and 82
`Claim 86
`
`34
`
`
`
`“Sensitive API” – Garst & Gong
`
`Petitioner
`
`IPR2017-01619, Pet. (Paper 1) at 18-19
`
`IPR2017-01619, Pet. (Paper 1) at 21
`
`35
`
`
`
`IPR2017-01619: The Challenged Claims Are Obvious
`
`“Signed Software Application”
`“Sensitive API”
`Claim 112
`Claims 77, 79, 80, and 82
`Claim 86
`
`36
`
`
`
`Claim 112 – Garst & Gong
`
`’868 Patent (Ex. 1001) at Claim 112
`
`’868 Patent (Ex. 1001) at Claim 76
`
`37
`
`
`
`Claim 112 – Garst & Gong
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 3:54-61
`
`’868 Patent (Ex. 1001) at Claim 141
`
`IPR2017-01619, Reply (Paper 19) at 17-18
`
`38
`
`
`
`Claim 112 – Garst & Gong
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 140:4-141:5
`
`IPR2017-01619, Reply (Paper 19) at 17-18
`
`39
`
`
`
`IPR2017-01619: The Challenged Claims Are Obvious
`
`“Signed Software Application”
`“Sensitive API”
`Claim 112
`Claims 77, 79, 80, and 82
`Claim 86
`
`40
`
`
`
`Claims 77, 79, 80 and 82 – Garst, Gong, & Davis
`
`’868 Patent (Ex. 1001) at Claims 77, 79, 80, 82
`
`41
`
`
`
`Claims 77, 79, 80 and 82 – Garst, Gong, & Davis
`
`Petitioner
`
`IPR2017-01619, Pet. (Paper 1) at 18-19
`
`IPR2017-01619, Pet. (Paper 1) at 52-53
`
`42
`
`
`
`IPR2017-01619: The Challenged Claims Are Obvious
`
`“Signed Software Application”
`“Sensitive API”
`Claim 112
`Claims 77, 79, 80, and 82
`Claim 86
`
`43
`
`
`
`Claim 86 – Garst, Gong, & Sibert
`
`’868 Patent (Ex. 1001) at Claim 86
`
`44
`
`
`
`Claim 86 – Garst, Gong, & Sibert
`Sibert
`
`Sibert (Ex. 1015) at 7:42-46
`
`Sibert (Ex. 1015) at 22:3-6
`
`Sibert (Ex. 1015) at 22:23-27
`IPR2017-01619, Reply (Paper 19) at 19-20
`
`45
`
`
`
`Claim 86 – Garst, Gong, & Sibert
`
`Dr. Ligler
`
`IPR2017-01619, Dr. Ligler Decl. (Ex. 2002) at ¶43 n.10
`
`IPR2017-01619, Reply (Paper 19) at 20
`
`46
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`47
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`48
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`’868 Patent (Ex. 1001) at Claim 1
`
`49
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Patent Owner
`
`IPR2017-01620, Resp. (Paper 16) at 24
`
`50
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin
`
`Lin (Ex. 1011) at FIG. 3
`
`IPR2017-01620, Pet. (Paper 1) at 23-26
`
`51
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 6
`
`Lin (Ex. 1011) at 5:13-21
`
`IPR2017-01620, Reply (Paper 19) at 2-4
`
`52
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Patent Owner
`
`IPR2017-01620, Resp. (Paper 16) at 22 n.4
`
`53
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 6
`
`Lin (Ex. 1011) at 5:13-21
`
`IPR2017-01620, Reply (Paper 19) at 2-4
`
`54
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 6
`
`Lin (Ex. 1011) at 3:25-35
`
`IPR2017-01620, Reply (Paper 19) at 3-4
`
`55
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 6
`
`Lin (Ex. 1011) at 5:1-4
`
`IPR2017-01620, Resp. (Paper 16) at 22 n.4
`
`56
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 224:18-225:8
`IPR2017-01620, Reply (Paper 19) at 4
`
`57
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 225:9-25
`IPR2017-01620, Reply (Paper 19) at 4
`
`58
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 6
`
`Lin (Ex. 1011) at 3:29-35
`
`IPR2017-01620, Reply (Paper 19) at 4
`
`59
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 2
`
`Lin (Ex. 1011) at 2:66-3:5
`
`IPR2017-01620, Pet. (Paper 1) at 24 ; Reply (Paper 19) at 5-6
`
`60
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figures 2 & 6
`
`Lin (Ex. 1011) at 1:59-2:11
`
`IPR2017-01620, Reply (Paper 19) at 5-6
`
`61
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Patent Owner & Dr. Ligler
`
`IPR2017-01620, Resp. (Paper 16) at 16
`
`Dr. Ligler Decl. (Ex. 2002) at ¶64
`
`IPR2017-01620, Reply (Paper 19) at 5-6
`
`62
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Lin – Figure 6
`
`Lin (Ex. 1011) at 5:6-19
`
`IPR2017-01620, Reply (Paper 19) at 6-7
`
`63
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 222:14-16
`
`IPR2017-01620, Reply (Paper 19) at 6-7
`
`64
`
`
`
`“Signed Software Application” Including a “Digital Signature”
`
`Petitioner
`
`IPR2017-01620, Reply (Paper 19) at 7-8
`
`65
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`66
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`’868 Patent (Ex. 1001) at Claim 1
`
`67
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Patent Owner
`
`IPR2017-01620, Resp. (Paper 16) at 26
`
`68
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Lin
`
`Lin (Ex. 1011) at 6:18-20
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`69
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Lin
`
`Lin (Ex. 1011) at 1:19-29
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`70
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Lin
`
`Lin (Ex. 1011) at FIG. 3
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`71
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Lin
`
`Lin (Ex. 1011) at 6:21-26
`
`Lin (Ex. 1011) at 6:18-20
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`72
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Lin
`
`Lin (Ex. 1011) at 3:62-64
`
`Lin (Ex. 1011) at 5:43-45
`
`Lin (Ex. 1011) at 5:45-48
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`73
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Dr. McDaniel
`
`IPR2017-01620, Dr. McDaniel Decl. (Ex. 1002) at ¶175
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`74
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Patent Owner
`
`IPR2017-01620, Resp. (Paper 16) at 31
`
`75
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Dr. McDaniel
`
`Dr. McDaniel Dep. Tr. (Ex. 2002) at 230:13-231:10
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`76
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Dr. McDaniel
`
`Dr. McDaniel Dep. Tr. (Ex. 2002) at 224:18-25
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`77
`
`
`
`“Based Upon Verifying the Digital Signature”
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 48:9-25
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`78
`
`
`
`“Based Upon Verifying the Digital Signature”
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 216:17-217:8
`
`IPR2017-01620, Reply (Paper 19) at 8-11
`
`79
`
`
`
`“Based Upon Verifying the Digital Signature”
`
`Inside the Java 2 Virtual Machine (Ex. 1032)
`
`Ex. 1032 at 69
`
`IPR2017-01620, Reply (Paper 19) at 11
`
`80
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`81
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`
`’868 Patent (Ex. 1001) at Claim 1
`
`82
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`
`Patent Owner
`
`IPR2017-01620, Resp. (Paper 16) at 33
`
`83
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`
`Dr. McDaniel
`
`IPR2017-01620, Dr. McDaniel Decl. (Ex. 1002) at ¶168
`
`IPR2017-01620, Reply (Paper 19) at 11-12
`
`84
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`Dr. McDaniel
`
`Dr. McDaniel Dep. Tr. (Ex. 2002) at 208:9-209:5
`IPR2017-01620, Reply (Paper 19) at 11-12
`
`85
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 85:23-86:12
`IPR2017-01620, Reply (Paper 19) at 11-12
`
`86
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`
`Dr. McDaniel
`
`Dr. McDaniel Dep. Tr. (Ex. 2002) at 209:20-210:9
`
`IPR2017-01620, Reply (Paper 19) at 12
`
`87
`
`
`
`“Wherein the Private Key Is Not Accessible to the Mobile Device”
`
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 5:43-50
`
`IPR2017-01620, Reply (Paper 19) at 12
`
`88
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`89
`
`
`
`Claims 78 and 81 – Lin
`
`’868 Patent (Ex. 1001) at Claims 78, 81
`
`90
`
`
`
`Claims 78 and 81
`
`Lin
`
`Lin (Ex. 1011) at 5:6-13
`
`Lin (Ex. 1011) at 6:18-20
`
`IPR2017-01620, Reply (Paper 19) at 13-14
`
`91
`
`
`
`Claims 78 and 81
`
`Patent Owner
`
`IPR2017-01620, Resp. (Paper 16) at 38
`
`92
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`93
`
`
`
`Claims 85 and 104 – Lin
`
`’868 Patent (Ex. 1001) at Claims 85, 104
`
`94
`
`
`
`Claims 85 and 104 – Lin
`Lin
`
`Lin (Ex. 1011) at 6:21-26
`
`Lin (Ex. 1011) at 3:42-46
`
`Lin (Ex. 1011) at 5:45-48
`IPR2017-01620, Pet. (Paper 1) at 32, 32 n.12; Reply (Paper 19) at 14-15
`
`95
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`96
`
`
`
`Claim 95 – Lin
`
`’868 Patent (Ex. 1001) at Claim 95
`
`97
`
`
`
`Claim 95 – Lin
`
`Lin
`
`Lin (Ex. 1011) at 3:48-56
`
`IPR2017-01620, Pet. (Paper 1) at 35; Reply (Paper 19) at 15
`
`98
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`99
`
`
`
`Claims 13 and 88 – Lin & Garst
`
`’868 Patent (Ex. 1001) at Claim 13
`
`100
`
`
`
`Claims 13 and 88 – Lin & Garst
`
`Lin
`
`Lin (Ex. 1011) at 1:30-40
`
`Lin (Ex. 1011) at 5:26-30
`IPR2017-01620, Pet. (Paper 1) at 20-21 ; Reply (Paper 19) at 15-16
`
`101
`
`
`
`Claims 13 and 88 – Lin & Garst
`Petitioner
`
`IPR2017-01620, Pet. (Paper 1) at 37
`
`IPR2017-01620, Pet. (Paper 1) at 38
`Reply (Paper 19) at 15-16
`
`102
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`103
`
`
`
`Claim 98 – Lin & Garst
`
`’868 Patent (Ex. 1001) at Claim 98
`
`104
`
`
`
`Claim 98 – Lin & Garst
`
`Dr. McDaniel
`
`IPR2017-01620, Dr. McDaniel Decl. (Ex. 1002) at ¶175
`
`IPR2017-01620, Reply (Paper 19) at 16-17
`
`105
`
`
`
`Claim 98 – Lin & Garst
`
`Lin
`
`Lin (Ex. 1011) at 5:31-37
`
`IPR2017-01620, Reply (Paper 19) at 16-17
`
`106
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`107
`
`
`
`Claim 86 – Lin & Sibert
`
`’868 Patent (Ex. 1001) at Claim 86
`
`108
`
`
`
`Claim 86 – Lin & Sibert
`Sibert
`
`Sibert (Ex. 1015) at 7:42-46
`
`Sibert (Ex. 1015) at 22:3-6
`
`Sibert (Ex. 1015) at 22:23-27
`IPR2017-01620, Reply (Paper 19) at 18-20
`
`109
`
`
`
`Claim 86 – Lin & Sibert
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 52:22-53:16
`
`IPR2017-01619, Reply (Paper 19) at 18-20
`
`110
`
`
`
`IPR2017-01620: The Challenged Claims Are Obvious
`
`“Signed Software Application” Including a “Digital
`Signature”
`“Based Upon Verifying the Digital Signature”
`“Wherein the Private Key Is Not Accessible to the
`Mobile Device”
`Claims 78 and 81
`Claim 85 and 104
`Claim 95
`Claims 13 and 88
`Claim 98
`Claim 86
`Claim 112
`
`111
`
`
`
`Claim 112 – Lin & Gong
`
`’868 Patent (Ex. 1001) at Claim 112
`
`’868 Patent (Ex. 1001) at Claim 76
`
`112
`
`
`
`Claim 112 – Lin & Gong
`The ’868 Patent
`
`’868 Patent (Ex. 1001) at 3:54-61
`
`’868 Patent (Ex. 1001) at Claim 141
`
`IPR2017-01620, Reply (Paper 19) at 20-21
`
`113
`
`
`
`Claim 112 – Lin & Gong
`
`Dr. Ligler
`
`Dr. Ligler Dep. Tr. (Ex. 1046) at 140:4-141:5
`
`IPR2017-01620, Reply (Paper 19) at 20-21
`
`114
`
`
`
`Public Availability – Gong
`
`Gong (Ex. 1016) at 1
`
`IPR2017-01619, Reply (Paper 19) at 21
`IPR2017-01620, Reply (Paper 19) at 21-22
`
`115
`
`
`
`Public Availability – Gong
`
`• Gong bears a copyright date of “1999” and indicates it was first
`printed in June 1999
`• Gong was received by the Library of Congress by September 2,
`1999
`• Gong was cataloged at NCSU as early as July 1999
`• Gong includes “due date” stamps as early as February 8, 2000
`• Gong was available for purchase on Amazon.com before
`September 21, 2000, and was customer reviewed as early as May
`1999
`• Gong was discussed and given away during an online chat on
`September 30, 1999
`• Gong was cited in articles before September 21, 2000
`• The author of Gong provided unrebuted testimony that the book
`was available for purchase prior to September 21, 2000
`
`IPR2017-01619, Reply (Paper 19) at 21-25
`IPR2017-01620, Reply (Paper 19) at 21-25
`
`116
`
`
`
`Public Availability – Gong
`
`Gong (Ex. 1016) at 4
`
`IPR2017-01619, Reply (Paper 19) at 23
`IPR2017-01620, Reply (Paper 19) at 23-24
`
`117
`
`
`
`Public Availability – Gong
`
`Ex. 1033 at 1
`IPR2017-01619, Reply (Paper 19) at 22
`IPR2017-01620, Reply (Paper 19) at 22-23
`
`118
`
`
`
`Public Availability – Gong
`
`Ex. 1039 at 1
`
`IPR2017-01619, Reply (Paper 19) at 24-25
`IPR2017-01620, Reply (Paper 19) at 24-25
`
`Ex. 1039 at 6-7
`
`119
`
`
`
`Public Availability – Gong
`
`Ex. 1040 at 1
`
`IPR2017-01619, Reply (Paper 19) at 24
`IPR2017-01620, Reply (Paper 19) at 24
`
`Ex. 1040 at 2
`
`120
`
`
`
`Public Availability – Gong
`
`Ex. 1042 at 202
`
`Ex. 1042 at 214
`
`IPR2017-01619, Reply (Paper 19) at 24
`IPR2017-01620, Reply (Paper 19) at 24
`
`121
`
`
`
`Public Availability – Gong
`
`Ex. 1045 at ¶¶5-6
`
`Ex. 1045
`
`IPR2017-01619, Reply (Paper 19) at 24-25
`IPR2017-01620, Reply (Paper 19) at 24-25
`
`122
`
`
`
`Public Availability – Gong
`
`Ex. 1044
`
`Ex. 1044 at ¶¶8, 13, 15
`
`IPR2017-01619, Reply (Paper 19) at 24-25
`IPR2017-01620, Reply (Paper 19) at 24-25
`
`123
`
`
`
`Case IPR2017-01619
`Patent 8,489,868 B2
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on September 10, 2018, I caused a true and correct copy of
`
`the foregoing Petitioner’s Demonstrative Exhibits to be served electronically on
`
`Patent Owner at the following address:
`
`Ching-Lee Fukuda
`SIDLEY AUSTIN LLP
`787 Seventh Avenue
`New York, NY 10019
`clfukuda@sidley.com
`
`Samuel A Dillon
`Sharon Lee
`SIDLEY AUSTIN LLP
`1501 K. Street, N.W.
`Washington, D.C. 20005
`samuel.dillon@sidley.com
`sharon.lee@sidley.com
`
`Dated: September 10, 2018
`
`By: /Naveen Modi/
` Naveen Modi (Reg. No. 46,224)
` Counsel for Petitioner
`
`
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
