IPR2016-01737, No. 1050-78 Exhibit - Petitioners Demonstratives (P.T.A.B. Jan. 3, 2018)

Apple Inc., (Petitioner)
`v.
`Realtime Data LLC (Patent Owner)
`
`Demonstratives
`Trial Nos. IPR2016-01737, -01738, and -01739
`U.S. Patent No. 8,880,862
`
`Before Hon. G. W. Braden, Jason J. Chung, and Debra Stephens,
`Administrative Patent Judges
`
`1
`
`APPLE 1050
`Apple v. Realtime Data
`IPR2016-01737
`
`

`Table of Contents
`
`2
`
`
`
`
`
`
`
`
`
`
`
`
`
`4
`5
`6
`
`The ‘862 Patent and the Instituted Challenges
`Overview
`
`
`
`
`
`
`
`Grounds Instituted in Inter Partes Review
`
`
`IPR2016-01737, -01738, & -01739: Issues Relating to Challenges 8
`1.0: The Applied Prior Art is Properly Combined
`
`
`9
`1.1: “Boot Data List” Construction
`
`
`13
`1.2: The Art Discloses Boot Data Lists
`
`
`
`17
`1.3: The Art Discloses Updating Boot Data Lists
`
`
`
`26
`1.4: The Art Renders Obvious Updating in Response to Utilizing
`30
`1.5: “Non-Accessed Boot Data” Construction
`
`31
`1.6: The Art Discloses Disassociating Non-Accessed Boot Data 34
`1.7: The Art Renders Obvious Further Partial Booting 39
`
`

`Table of Contents
`
`3
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`41
`42
`43
`
`IPR2016-01737 & -01738: Amendments
`Amendment Overview
`
`
`
`Prior Art Applied in Oppositions
`
`
`
`44
`IPR2016-01737 & -01738: Issues Relating to Amendments
`45
`2.0: “Preloading” Construction
`
`
`
`
`
`
`50
`2.1: Settsu Performs the Claimed Preloading
`
`
`54
`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`2.3: The Sukegawa-Dye-Esfahani Combination Performs Preloading 60
`2.4: The Sukegawa-Dye-Kroeker Combination Performs Preloading 62
`2.5: Cost Would have Motivated the Sukegawa Combinations
`65
`2.6: Speed Would have Motivated the Sukegawa Combinations
`72
`
`

`The ’862 Patent and the Instituted Challenges
`
`4
`
`

`Overview
`
`These three related proceedings involve a single
`patent with 117 original claims.
`
`IPR2016-01737 challenges claims 1-4, 6-7, 13,
`23-34, 47-58, 83-96, 99-100, 105-111, 113, and
`116 as obvious over combinations featuring
`Sukegawa as the primary reference.
`
`IPR2016-01738 challenges claims 8-12, 14-22,
`59-82, 101-104, 114-115, and 117 116 as
`obvious over combinations featuring
`Sukegawa as the primary reference.
`
`IPR2016-01739 challenges claims 5, 35-46, 97,
`98, and 112 as obvious over combinations
`featuring Settsu as the primary reference.
`
`US 8,880,862 (“the ’862 Patent”)
`
`See, e.g., IPR2016-01737, Ex. 1001; IPR2016-01737
`Petition; IPR2016-01738 Petition, IPR2016-01739 Petition.
`
`5
`
`

`Grounds Instituted: IPR2016-01737, -01738
`
`Grounds Instituted in Inter Partes Review of the ‘862 Patent – 35 U.S.C. § 103(a)
`
`Prior Art
`
`IPR2016-01737
`
`IPR2016-01738
`
`US Patent No. 5,860,083
`(“Sukegawa”) & US Patent
`No. 6,145,069 (“Dye”)
`
`1–4, 6–7, 13, 23–34, 47–58, 83–96,
`99–100, 105–111, 113, & 116
`
`8–12, 14–22, 59–82, 101–104, 114–115,
`& 117
`
`Sukegawa, Dye, & US
`Patent No. 6,374,353
`(“Settsu”)
`
`1–4, 6–7, 13, 23–34, 47–58, 83–96,
`99–100, 105–111, 113, & 116
`
`8–12, 14–22, 59–82, 101–104, 114–115,
`& 117
`
`Sukegawa, Dye, &
`NPL (“Burrows”)
`
`1–4, 6–7, 13, 23–34, 47–58, 83–96,
`99–100, 105–111, 113, & 116
`
`8–12, 14–22, 59–82, 101–104, 114–115,
`& 117
`
`Sukegawa, Dye, Settsu, &
`Burrows
`
`1–4, 6–7, 13, 23–34, 47–58, 83–96,
`99–100, 105–111, 113, & 116
`
`8–12, 14–22, 59–82, 101–104, 114–115,
`& 117
`
`Sukegawa, Dye, & US
`Patent No. 6,317,818
`(“Zwiegincew”)
`
`1–4, 6–7, 13, 23–34, 47–58, 83–96,
`99–100, 105–111, 113, & 116
`
`8–12, 14–22, 59–82, 101–104, 114–115,
`& 117
`
`6
`
`

`Grounds Instituted: IPR2016-01739
`
`Grounds Instituted in Inter Partes Review of the ‘862 Patent – 35 U.S.C. § 103(a)
`
`Prior Art
`
`IPR2016-01739
`
`Settsu
`
`5, 35–46, & 97
`
`Settsu & Zwiegincew
`
`5, 35–46, 97, 98, & 112
`
`Settsu & Dye
`
`5, 35–46, & 97
`
`Settsu, Zwiegincew, & Dye
`
`5, 35–46, 97, 98, & 112
`
`7
`
`

`IPR2016-01737, -01738, & -01739:
`Issues Relating to Instituted Challenges
`
`8
`
`

`1.0: The Applied Prior Art is Properly Combined
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Rest on Impermissible Hindsight”
`IPR2016-01737 Pap. 20, 53; IPR2016-01738 Pap. 21, 56.
`
`Petition
`
`IPR2016-01737 Pap. 2, 8
`(reproducing Sukegawa, Fig. 1 (excerpt, annotated)).
`
`IPR2016-01737 Pap. 2, 14
`Dye, Fig. 3 (excerpt, annotated).
`
`9
`
`

`1.0: The Applied Prior Art is Properly Combined
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Rest on Impermissible Hindsight”
`IPR2016-01737 Pap. 20, 53; IPR2016-01738 Pap. 21, 56.
`
`Petition
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Pap. 2, 16. (reproducing
`Sukegawa, Fig.1 & Dye, Fig. 3 (combined excerpts, annotated).
`
`IPR2016-01737 Ex. 1003, ¶80.
`
`IPR2016-01737 Ex. 1003, ¶81.
`
`IPR2016-01737 Ex. 1003, ¶87.
`
`10
`
`

`1.0: The Applied Prior Art is Properly Combined
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Rest on Impermissible Hindsight”
`IPR2016-01737 Pap. 20, 53; IPR2016-01738 Pap. 21, 56.
`
`Petitioner’s Reply (Addressing -01737 & -01738 Grounds 2-5)
`
`IPR2016-01737 Pap. 23, 20-21.
`
`IPR2016-01737 Pap. 23, 20.
`
`IPR2016-01737 Pap. 23, 21.
`
`11
`
`

`1.0: The Applied Prior Art is Properly Combined
`
`Settsu
`
`Petition
`
`Settsu, FIG. 12.
`
`IPR2016-01739 Pap. 2, 6.
`
`IPR2016-01739 Pap. 2, 10-11.
`
`12
`
`

`1.1: “Boot Data List” Construction
`
`Rebuttal to:
`
`“The term ‘boot data list’ … should mean ‘record used to identify and load boot data into memory.”
`IPR2016-01737 Pap. 20, 19; -01738 Pap. 21, 18; -01739 Pap. 15, 15.
`
`Petition
`
`’862 Claim 1
`
`IPR2016-01737 Pap. 2, 5;
`-01738 Pap. 5; -01739 Pap. 2, 15.
`
`’862 Patent, 26:38-51 (claim 1).
`
`13
`
`

`1.1: “Boot Data List” Construction
`
`Rebuttal to:
`
`“The term ‘boot data list’ … should mean ‘record used to identify and load boot data into memory.”
`IPR2016-01737 Pap. 20, 19; -01738 Pap. 21, 18; -01739 Pap. 15, 15.
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`’862 Patent
`
`IPR2016-01737 Ex. 1003, ¶122.
`
`’862 Patent, Abs.
`
`14
`
`

`1.1: “Boot Data List” Construction
`
`Rebuttal to:
`
`“The term ‘boot data list’ … should mean ‘record used to identify and load boot data into memory.”
`IPR2016-01737 Pap. 20, 19; -01738 Pap. 21, 18; -01739 Pap. 15, 15.
`
`’862 FIG. 7B
`
`’862 Claim 6
`
`’862 Patent, 27:9-25 (claim 6).
`
`’862 Patent, FIG. 7B.
`
`15
`
`

`1.1: “Boot Data List” Construction
`
`Rebuttal to:
`
`“The term ‘boot data list’ … should mean ‘record used to identify and load boot data into memory.”
`IPR2016-01737 Pap. 20, 19; -01738 Pap. 21, 18; -01739 Pap. 15, 15.
`
`Petitioner’s Reply
`
`Ex. 2012
`
`IPR2016-01737 Pap. 23, 4;
`-01738 Pap. 24, 3; -01739 Pap. 17, 4.
`
`IPR2016-01737 Ex. 2012, 2-3 (combined excerpts).
`
`16
`
`

`1.2: The Art Discloses Boot Data Lists
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Pap. 23, 7-8.
`
`IPR2016-01737 Ex. 1003, ¶122.
`
`18
`
`

`1.2: The Art Discloses Boot Data Lists
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply
`
`’862 Patent
`
`’862 Patent, 3:42-59.
`
`IPR2016-01737 Pap. 23, 8-9.
`
`19
`
`

`1.2: The Art Discloses Boot Data Lists
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply
`
`PO’s Response
`
`IPR2016-01737 Pap. 20, 34.
`
`IPR2016-01737 Pap. 23, 9-10.
`
`21
`
`

`1.2: The Art Discloses Boot Data Lists
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply
`
`Sukegawa
`
`IPR2016-01737 Pap. 23, 11.
`
`PO’s Response
`
`IPR2016-01737 Pap. 20, 19.
`
`Sukegawa, FIG. 1.
`
`23
`
`

`1.2: The Art Discloses Boot Data Lists
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply (Addressing -01737 & -01738 Ground 5)
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Pap. 23, 12.
`
`IPR2016-01737 Ex. 1003, ¶149.
`
`24
`
`

`1.2: The Art Discloses Boot Data Lists
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply
`(Addressing -01737 & -01738 Grounds 2 & 4)
`
`Settsu
`
`IPR2016-01737 Pap. 23, 12; -01738 Pap. 24, 10.
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Ex. 1003, ¶146.
`
`Settsu, FIG. 20.
`
`25
`
`

`1.3: The Art Discloses Updating Boot Data Lists
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Fail to Disclose Claim 5’s ‘Updating the Boot Data List.’”
`IPR2016-01739 Pap. 15, 24.
`
`Petitioner’s Reply
`
`’862 Claim 5
`
`’862 Patent, 26:60-27:8 (claim 5).
`
`IPR2016-01739 Pap. 17, 7-8.
`
`26
`
`

`1.3: The Art Discloses Updating Boot Data Lists
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Fail to Disclose Claim 5’s ‘Updating the Boot Data List.’”
`IPR2016-01739 Pap. 15, 24.
`
`Petitioner’s Reply
`
`IPR2016-01739 Pap. 17, 10.
`
`IPR2016-01739 Pap. 17, 10-11.
`
`27
`
`

`1.3: The Art Discloses Updating Boot Data Lists
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Fail to Disclose Claim 5’s ‘Updating the Boot Data List.’”
`IPR2016-01739 Pap. 15, 24.
`
`Petitioner’s Reply
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01739 Pap. 17, 11-12.
`
`IPR2016-01739 Ex. 1003, ¶117.
`
`28
`
`

`1.3: The Art Discloses Updating Boot Data Lists
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Fail to Disclose Claim 5’s ‘Updating the Boot Data List.’”
`IPR2016-01739 Pap. 15, 24.
`
`Petitioner’s Reply (Addressing -01739 Grounds 2 & 4)
`
`IPR2016-01739 Pap. 17, 13.
`
`IPR2016-01739 Pap. 17, 20-21.
`
`29
`
`

`1.4: The Art Renders Obvious Updating in Response to Utilizing
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Render Obvious Claim 112’s
`“Updating the Boot Data List” in Response to the “Utilizing” Step.’” IPR2016-01739 Pap. 15, 41.
`
`Petitioner’s Reply
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01739 Ex. 1003, ¶¶207-208.
`
`IPR2016-01739 Pap. 17, 20-21.
`
`30
`
`

`1.5: “Non-Accessed Boot Data” Construction
`
`Rebuttal to:
`
`“The term ‘non-accessed boot data’ … should mean[ ] ‘boot data identified in the boot data list that was not
`requested during system boot-up.’” IPR2016-01737 Pap. 20, 25; -01738 Pap. 21, 23; -01739 Pap. 15, 20.
`
`’862 Claims
`
`Petitioner’s Reply
`
`’862 Patent, 31:39-42 (claim 96).
`
`’862 Patent, 32:58-61 (claim 100).
`
`’862 Patent, 33:1-4 (claim 102).
`
`IPR2016-01737 Pap. 23, 5;
`-01738 Pap. 24 4-5; -01739 Pap. 17, 5.
`
`’862 Patent, 33:9-13 (claim 104).
`
`31
`
`

`1.5: “Non-Accessed Boot Data” Construction
`
`Rebuttal to:
`
`“The term ‘non-accessed boot data’ … should mean[ ] ‘boot data identified in the boot data list that was not
`requested during system boot-up.’” IPR2016-01737 Pap. 20, 25; -01738 Pap. 21, 23; -01739 Pap. 15, 20.
`
`Petitioner’s Reply
`
`’862 Prosecution History
`
`IPR2016-01737 Pap. 23, 5-6;
`-01738 Pap. 24, 5; -01739 Pap. 17, 5-6.
`
`IPR2016-01737 Ex. 1002 (Part 1), 156.
`
`“As a non-limiting example, Applicant respectfully
`directs the Examiner to … removing from the list any
`boot data previously stored in the list and not request
`by the computer system.” IPR2016-01737 Ex. 1014, 3
`(emphasis removed).
`
`32
`
`

`1.6: The Art Discloses Disassociating Non-Accessed Boot Data
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`’862 Claims
`
`Petitioner’s Reply
`
`’862 Patent, 31:39-42 (claim 96).
`
`’862 Patent, 32:58-61 (claim 100).
`
`’862 Patent, 33:1-4 (claim 102).
`
`’862 Patent, 33:9-13 (claim 104).
`
`IPR2016-01737 Pap. 23, 13.
`
`34
`
`

`1.6: The Art Discloses Disassociating Non-Accessed Boot Data
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Pap. 23, 13-14.
`
`IPR2016-01737 Ex. 1003, ¶658.
`
`IPR2016-01737 Pap. 23, 14.
`
`35
`
`

`1.6: The Art Discloses Disassociating Non-Accessed Boot Data
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petition
`
`Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Pap. 2, 5.
`
`IPR2016-01737 Ex. 1003, ¶660.
`
`36
`
`

`1.6: The Art Discloses Disassociating Non-Accessed Boot Data
`
`Rebuttal to:
`
`“Petitioner’s Combinations Do Not Disclose or Render Obvious the ‘Boot Data List’ Limitations.’”
`IPR2016-01737 Pap. 20, 25; IPR2016-01738 Pap. 21, 27.
`
`Petitioner’s Reply (Addressing -01737 & -01738 Ground 5) Dr. Neuhauser’s Declaration of Sep. 9, 2016
`
`IPR2016-01737 Pap. 23, 15-16.
`
`IPR2016-01737 Ex. 1003, ¶214.
`Petition
`
`IPR2016-01737 Pap. 2, 71.
`37
`
`

`1.6: The Art Discloses Disassociating Non-Accessed Boot Data
`
`Rebuttal to:
`
`“Each Ground is Defective Because Petitioner’s Combinations Do Not Render Obvious Claim 98’s
`‘Disassociating Non-Accessed Boot Data from the Boot Data List.’” IPR2016-01739 Pap. 15, 37.
`
`Petitioner’s Reply
`
`IPR2016-01739 Pap. 17, 17.
`
`IPR2016-01739 Pap. 17, 19.
`
`38
`
`

`1.7: The Art Renders Obvious Further Partial Booting
`
`Rebuttal to:
`
`“Sukegawa Does Not Teach … Utilizing the Stored Additional Portion of the Operating System
`to at Least Further Partially Boot the Computer System.’” IPR2016-01738 Pap. 21, 78.
`
`’862 Claim 9
`
`Petition
`
`’862 Patent, 27:55-63 (claim 9).
`
`IPR2016-01738 Pap. 2, 24.
`Sukegawa
`
`Sukegawa, 6:32-44.
`39
`
`

`1.7: The Art Renders Obvious Further Partial Booting
`
`Rebuttal to:
`
`“Sukegawa Does Not Teach … Utilizing the Stored Additional Portion of the Operating System
`to at Least Further Partially Boot the Computer System.’” IPR2016-01738 Pap. 21, 78.
`
`Petition
`
`Sukegawa
`
`IPR2016-01738 Pap. 2, 24.
`
`Sukegawa, 8:30-36.
`
`IPR2016-01738 Pap. 2, 25.
`
`Sukegawa, FIG. 1.
`
`40
`
`

`Amendments
`
`IPR2016-01737 & -01738:
`IPR2016-01737 & -01738:
`Amendments
`
`41
`41
`
`

`Amendment Overview
`
`IPR2017-01737: Patent Owner requested that,
`“[i]n the event the Board finds independent claims
`8, 11, and 14 unpatentable,” the Board grant its
`motion to amend and issue corresponding
`substitute claims 118, 122, and 124.
`
`Substitute dependent claims 119-121, 123, and
`125-173 were said to have been “amended only
`to reflect their new dependency from the
`amended substitute independent claims.”
`
`IPR2017-01738: Patent Owner requested that,
`“[i]n the event the Board finds independent claims
`8, 11, and 14 unpatentable,” the Board grant its
`motion to amend and issue corresponding
`substitute claims 174, 177, and 179.
`
`Substitute dependent claims 175-176, 178, and
`179-218 were said to have been “amended only
`to reflect their new dependency from the
`amended substitute independent claims.”
`
`IPR2016-01737 Pap. 19, 1.
`
`IPR2016-01737 Pap. 19, 2-3.
`
`IPR2016-01737 Pap. 19, 3.
`
`See, e.g., IPR2017-01737, Pap. 19, 1-4; IPR2017-01738,
`Pap. 20, 1-4.
`
`42
`
`

`Prior Art Applied in Oppositions
`
`Prior Art Applied to Patent Owner’s Proposed Substitute Claims
`
`Prior Art
`
`IPR2016-01737
`
`IPR2016-01738
`
`US Patent No. 6,374,353
`(“Settsu”).
`
`Claims 118-173. See Pap. 24, 9-25;
`Pap. 37, 8-10; Pap. 43, 2-3.
`
`Claims 174-218. See Pap. 25, 9-25;
`Pap. 39, 8-11; Pap. 45, 2-3.
`
`Settsu & US Patent No.
`6,317,818 (“Zwiegincew”).
`
`Claims 118-173. See Pap. 24, 9-25;
`Pap. 37, 8-12; Pap. 43, 2-3.
`
`Claims 174-218. See Pap. 25, 9-25; Pap.
`39, 8-12; Pap. 45, 2-3.
`
`US Patent No. 5,860,083
`(“Sukegawa”) & US Patent
`No. 6,145,069 (“Dye”).
`
`Sukegawa, Dye, & US
`Patent No. 6,073,232
`(“Kroeker”).
`
`Sukegawa, Dye, & US
`Patent No. 6,434,695
`(“Esfahani”).
`
`Claims 118-173. See Pap. 24, 6-8.
`
`Claims 174-218. See Pap. 25, 6-8.
`
`Claims 118-173. See Pap. 37, 1-2, 5-
`8; Pap. 43, 3-5.
`
`Claims 174-218. See Pap. 39, 1-2, 5-8;
`Pap. 45, 3-5.
`
`Claims 118-173. See Pap. 37, 1-5;
`Pap. 43, 3-5.
`
`Claims 174-218. See Pap. 39, 1-5; Pap.
`45, 3-5.
`
`43
`
`

`IPR2017-01737 & -01738:
`Issues Relating to Amendments
`
`44
`
`

`2.0: “Preloading” Construction
`
`Rebuttal to:
`
`“the [BRI] of ‘preloading’ cannot include beginning to load operating system boot
`data only after receiving a request for that data over [the] computer bus.” Pap. 31, 5.
`
`Petitioner’s Supplemental Reply
`
`Exemplary Amended Claim 118
`
`IPR2016-01737 Pap. 43, 1
`
`“Notably absent … is language requiring that
`preloading ‘must begin before a request for the
`boot data has been received over the [the]
`computer bus’” IPR2016-01737 Pap. 43, 1.
`
`IPR2016-01737 Pap. 19, iii (Claim 118)
`
`45
`
`

`2.0: “Preloading” Construction
`
`Rebuttal to:
`
`“the [BRI] of ‘preloading’ cannot include beginning to load operating system boot
`data only after receiving a request for that data over [the] computer bus.” Pap. 31, 5.
`
`Petitioner’s Supplemental Reply
`
`’862 Patent
`
`IPR2016-01365 Patent Owner’s Response
`
`IPR2016-01737 Pap. 43, 1
`
`’862 Patent, 1:5-15
`
`IPR2016-01365 (’608) Patent Owner’s Response, 12
`
`46
`
`

`2.0: “Preloading” Construction
`
`Rebuttal to:
`
`“the [BRI] of ‘preloading’ cannot include beginning to load operating system boot
`data only after receiving a request for that data over [the] computer bus.” Pap. 31, 5.
`
`Transcript of November 2, 2017
`Deposition of Dr. Back
`
`“So you’re asking if a person of skill would
`have the same understanding of the term
`‘preloading’ when reading the claims of the
`‘608 patent and the amended claims of the
`‘862 patent?”
`
`“I would say they would have the same
`understanding.” (emphasis added)
`
`IPR2016-01737 Ex. A-1046, 82:18-83:8.
`
`47
`
`

`2.0: “Preloading” Construction
`
`Rebuttal to:
`
`“the [BRI] of ‘preloading’ cannot include beginning to load operating system boot
`data only after receiving a request for that data over [the] computer bus.” Pap. 31, 5.
`
`Petitioner’s Supplemental Reply
`
`’862 Patent
`
`IPR2016-01737 Pap. 43, 1
`
`’862 Patent, 21:3-12
`
`’862 Patent, 21:43-59
`
`48
`
`

`2.0: “Preloading” Construction
`
`Rebuttal to:
`
`“the [BRI] of ‘preloading’ cannot include beginning to load operating system boot
`data only after receiving a request for that data over [the] computer bus.” Pap. 31, 5.
`
`Transcript of November 2, 2017
`Deposition of Dr. Back
`
`Q: “…in your opinion, would a [POSITA]
`have understood that the data storage
`controller may receive requests for preloaded
`boot data while it is preloading other boot
`data?”
`
`A: “Yes that is correct … it is possible for
`the data storage controller to – to engage
`in the preloading process while already
`servicing requests for preloaded data
`during that second phase where booting and
`preloading may be performed
`simultaneously….” (emphases added).
`
`IPR2016-01737 Ex. A-1046, 120:13-121:11.
`
`49
`
`

`2.1: Settsu Performs the Claimed Preloading
`
`Rebuttal to:
`
`“Settsu … does not teach ‘preloading’ within the
`broadest reasonable Interpretation of that term.” Pap. 31, 5.
`
`Petitioner's Supplemental Opposition
`
`Settsu
`
`Settsu FIG. 12 (as reproduced in -01737 Pap. 24, 11).
`
`IPR2016-01737 Pap. 37, 10
`(citing Settsu, Abs. 8:21-35, FIG. 12).
`
`50
`
`

`2.1: Settsu Performs the Claimed Preloading
`
`Rebuttal to:
`
`“Settsu … does not teach ‘preloading’ within the
`broadest reasonable Interpretation of that term.” Pap. 31, 5.
`
`Petitioner's Supplemental Opposition
`
`Settsu
`
`IPR2016-01737 Pap. 37, 10
`(citing Settsu, Abs. 8:21-35, FIG. 12).
`
`Settsu, Abs.
`
`Settsu, 8:28-35.
`
`51
`
`

`2.1: Settsu Performs the Claimed Preloading
`
`Rebuttal to:
`
`“Settsu … does not teach ‘preloading’ within the
`broadest reasonable Interpretation of that term.” Pap. 31, 5.
`
`Petitioner's Supplemental Opposition
`
`Settsu
`
`IPR2016-01737 Pap. 37, 10
`(citing Settsu,12:6-16, 15:62-16:4).
`
`’862 Patent
`
`Settsu, 12:6-16.
`
`’862 Patent, 21:43-59
`
`52
`
`

`2.1: Settsu Performs the Claimed Preloading
`
`Rebuttal to:
`
`“Settsu … does not teach ‘preloading’ within the
`broadest reasonable Interpretation of that term.” Pap. 31, 5.
`
`Petitioner's Supplemental Reply
`
`Settsu
`
`IPR2016-01737 Pap. 43, 2
`(citing Settsu,3:6-25, 13:49-15:5).
`
`Settsu, 3:6-25.
`
`53
`
`

`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`
`Rebuttal to:
`
`“Zwiegincew cannot be combined with Settsu.” Pap. 31, 8
`
`Petitioner's Supplemental Opposition
`
`Settsu
`
`IPR2016-01737 Pap. 37, 11.
`
`Settsu, 11:31-33.
`
`Settsu, 14:26-28.
`
`Zwiegincew
`
`Zwiegincew, 2:12-14.
`
`54
`
`

`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`
`Rebuttal to:
`
`“Zwiegincew cannot be combined with Settsu.” Pap. 31, 8
`
`Petitioner's Supplemental Opposition
`
`Settsu
`
`Settsu, FIG. 17
`(excerpt).
`
`IPR2016-01737 Pap. 37, 11-12
`(citing Settsu, 16:7-17:62, FIGS. 17-20).
`
`Settsu, FIG. 20.
`
`55
`
`

`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`
`Rebuttal to:
`
`“Zwiegincew cannot be combined with Settsu.” Pap. 31, 8
`
`Petitioner's Supplemental Opposition
`
`Settsu
`
`IPR2016-01737 Pap. 37, 12.
`
`Zwiegincew
`
`Settsu, 17:48-62.
`
`Zwiegincew, 2:12-14.
`
`56
`
`

`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`
`Rebuttal to:
`
`“Zwiegincew cannot be combined with Settsu.” Pap. 31, 8
`
`Petitioner's Supplemental Reply
`
`Transcript of November 2, 2017
`Deposition of Dr. Back
`
`IPR2016-01737 Ex. A-1046, 146:3-12.
`
`IPR2016-01737 Pap. 37, 2-3.
`
`IPR2016-01737 Ex. A-1046, 148:2-8.
`
`57
`
`

`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`
`Rebuttal to:
`
`“Zwiegincew cannot be combined with Settsu.” Pap. 31, 8
`
`Petitioner's Supplemental Reply
`
`Petitioner’s Opposition
`
`Opposition, 13 (citing Settsu, 16:7-17:62, FIG. 20).
`
`IPR2016-01737 Pap. 37, 2-3.
`
`Opposition, 14-15 (citing Settsu, 16:7-17:62, FIG. 20).
`
`58
`
`

`2.2: Zwiegincew’s Preloading Techniques are Applicable in Settsu
`
`Rebuttal to:
`
`“Zwiegincew cannot be combined with Settsu.” Pap. 31, 8
`
`Petitioner's Supplemental Reply
`
`Settsu
`
`IPR2016-01737 Pap. 37, 3.
`
`Settsu, 16:15-30.
`
`Settsu, 17:48-62.
`
`59
`
`

`2.3: The Sukegawa-Dye-Esfahani Combination Preloads
`
`Rebuttal to:
`
`“Esfahani does not teach ‘preloading,’ either alone or in combination.” Pap. 39, 10
`
`Petitioner’s Supplemental Opposition Brief
`
`IPR2016-01737 Pap. 37, 2.
`
`IPR2016-01737 Pap. 37, 3.
`
`60
`
`

`2.3: The Sukegawa-Dye-Esfahani Combination Preloads
`
`Rebuttal to:
`
`“Esfahani does not teach ‘preloading,’ either alone or in combination.” Pap. 39, 10
`
`Petitioner’s Supplemental Reply
`
`’862 Patent
`
`IPR2016-01737 Pap. 43, 3.
`
`IPR2016-01737 Pap. 43, 1
`
`’862 Patent, 21:43-59
`
`61
`
`

`2.4: The Sukegawa-Dye-Kroeker Combination Preloads
`
`Kroeker
`
`Transcript of December 7, 2017
`Deposition of Dr. Back
`
`Kroeker, Abs.
`
`IPR2016-01737 Ex. A-1047,
`112:19-113:4.
`
`62
`
`

`2.4: The Sukegawa-Dye-Kroeker Combination Preloads
`
`Petitioner’s Supplemental Reply
`
`Petitioner’s Supplemental Reply
`
`PO’s Supplemental Response ISO Motion to Amend
`
`IPR2016-01737 Pap. 43, 1
`
`IPR2016-01737 Pap. 43, 3-4.
`
`IPR2016-01737 Pap. 39, 10
`
`63
`
`

`2.4: The Sukegawa-Dye-Kroeker Combination Preloads
`
`Petitioner’s Supplemental Opposition Brief
`
`IPR2016-01737 Pap. 37, 5.
`
`IPR2016-01737 Pap. 37, 6-7.
`
`64
`
`

`2.5: Cost Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘cost’ motivation.” Pap. 39, 3
`
`Petitioner’s Supplemental Reply
`
`Patent Owner’s Evidence
`
`PC Magazine, 12/1/99, 4
`(Ex. 2029)
`
`PC Magazine, 3/7/00, 5
`(Ex. 2029)
`
`PC Magazine, 3/21/00, 5
`(Ex. 2029)
`
`IPR2016-01737 Pap. 43, 4-5.
`
`PC Magazine, 12/1/99, 3
`(Ex. 2029)
`
`PC Magazine, 3/7/00, 4
`(Ex. 2029)
`
`PC Magazine, 3/21/00, 4
`(Ex. 2029)
`
`65
`
`

`2.5: Cost Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘cost’ motivation.” Pap. 39, 3
`
`Petitioner’s Supplemental Reply
`
`Patent Owner’s Evidence
`
`“Fits most desktops”
`Ex. 2029, 4.
`
`PC Magazine, 12/1/99, 4 (Ex. 2029)
`
`IPR2016-01737 Pap. 43, 4-5.
`
`PC Magazine, 12/1/99, 3 (Ex. 2029)
`
`“These are the
`squarish, nonvolatile
`memory card
`formats used in
`digital cameras …
`and the like.”
`Ex. 2029, 3.
`
`66
`
`

`2.5: Cost Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘cost’ motivation.” Pap. 39, 3
`
`Petitioner’s Supplemental Reply
`
`Patent Owner’s Evidence
`
`IPR2016-01737 Pap. 43, 5.
`
`PC Magazine, 12/1/99, 4
`(Ex. 2029)
`
`PC Magazine, 3/7/00, 5
`(Ex. 2029)
`
`PC Magazine, 3/21/00, 5
`(Ex. 2029)
`
`PC Magazine, 12/1/99, 3
`(Ex. 2029)
`
`PC Magazine, 3/7/00, 4
`(Ex. 2029)
`
`PC Magazine, 3/21/00, 4
`(Ex. 2029)
`
`67
`
`

`2.5: Cost Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘cost’ motivation.” Pap. 39, 3
`
`Petitioner’s Supplemental Reply
`
`Transcript of Nov. 2, 2017 Deposition of Dr. Back
`
`IPR2016-01737 Pap. 43, 5.
`
`“a [POSITA] would probably be
`discouraged from the use of non-
`volatile memory for a number of
`reasons, one which is the higher
`price of the memory.”
`
`IPR2016-01737 Ex. A-1046, 58:9-59:1.
`
`69
`
`

`2.5: Cost Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘cost’ motivation.” Pap. 39, 3
`
`Petitioner’s Supplemental Reply
`
`Transcript of Nov. 2, 2017 Deposition of Dr. Back
`
`IPR2016-01737 Pap. 43, 5.
`
`“[T]he use of non-volatile memory
`is not necessary or beneficial for
`the envisioned preloading …. I can
`think of additional reasons,
`including the slower speed and
`likely the high expense associated
`with non-volatile memory.”
`
`IPR2016-01737 Ex. A-1046, 66:8-66:19.
`
`70
`
`

`2.5: Cost Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘cost’ motivation.” Pap. 39, 3
`
`Petitioner’s Supplemental Reply
`
`Transcript of Nov. 2, 2017 Deposition of Dr. Back
`
`IPR2016-01737 Pap. 43, 5.
`
`“I would not have cited to this
`statement if I had disagreed with
`it.”
`
`“Volatile memory is faster, is
`cheaper, and … the use of non-
`volatile memory is neither
`necessary, nor beneficial.”
`
`IPR2016-01737 Ex. A-1046, 60:12-21.
`
`IPR2016-01737 Ex. A-1046, 50:10-51:1.
`
`71
`
`

`2.6: Speed Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘speed’ motivation.” Pap. 39, 5
`
`Nov. 10 Declaration of Dr. Neuhauser
`
`IPR2016-01737 Ex. A-1043, ¶22.
`
`IPR2016-01737 Ex. A-1043, ¶23.
`
`IPR2016-01737 Ex. A-1043, ¶47.
`
`IPR2016-01737 Ex. A-1043, ¶48.
`
`72
`
`

`2.6: Speed Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘speed’ motivation.” Pap. 39, 5
`
`Petitioner’s Supplemental Reply
`
`Kroeker
`
`IPR2016-01737 Pap. 43, 4.
`
`Kroeker, Abs.
`
`Kroeker, 1:55-67.
`
`73
`
`

`2.6: Speed Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘speed’ motivation.” Pap. 39, 5
`
`Transcript of Dec. 7, 2017 Deposition of Dr. Back
`
`“I’m not providing a critique or
`evaluation of Kroeker’s method.”
`
`“The speed … may be slower.”
`
`“I did not evaluate the speed of
`either system separately because
`that is not what I was asked to do.”
`
`-01737 Ex. A-1047, 117:9-118:15.
`
`IPR2016-01737 Ex. A-1047, 117:9-118:15.
`
`74
`
`

`2.6: Speed Would have Motivated the Sukegawa Combinations
`
`Rebuttal to:
`
`“The evidence refutes the alleged ‘speed’ motivation.” Pap. 39, 5
`
`Transcript of Dec. 7, 2017 Deposition of Dr. Back
`
`“Q: So it may slow down the boot
`speed … or it may speed up the
`boot speed?”
`
`“A: … I think either outcome is
`possible.”
`
`IPR2016-01737 Ex. A-1047, 91:11-20.
`
`75
`
`

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

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.

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

Supplemental Search

Search for PTAB Motions

PTAB Analytics

TTAB Analytics

Basic Search

Filters

Party Search

Advanced

Selected Courts

Recently Selected Courts

Find PTAB Decisions

PTAB Analytics

Special PTAB Alerts

Orange Book

Directly Search Federal Courts

Search Trademark ...

This document is available on Docket Alarm but you must sign up to view it.

Accessing this document will incur an additional charge of $.

Still Working On It

A few More Minutes ... Still Working

This document could not be displayed.

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.

One Moment Please

Your document is on its way!

Sealed Document

We are redirecting youto a mobile optimized page.

Document Unreadable or Corrupt

We are unable to display this document.

STEP 2 of 2

Choose your membership type

Flat-Fee

Pay-As-You-Go

Add your payment information

Login or Join

Enter your corporate Email

Thousands of your peers are saving time and gaining a competitive advantage with Docket Alarm.

Join Docket Alarm to perform smarter legal research.

Download this document and millions of others instantly with a Docket Alarm membership.

Join Docket Alarm and start performing smarter legal research.

Start tracking this docket instantly with a Docket Alarm membership.

Join thousands of your peers and start performing smarter legal research.

STEP 1 of 2

Millions of Documents | 15 Seconds to Signup

Hi !

Welcome to Docket Alarm

Welcome to Docket Alarm!

Explore Litigation Insights andManage Your Cases

Reset Password

What is PACER?

Why do I need it?

What will I be charged?

Do other courts have fees?

Basic Free Access

Welcome

Thank you

Check Firm Account

We are redirecting you
to a mobile optimized page.

Explore Litigation Insights and
Manage Your Cases