throbber
Trials@uspto.gov
`571.272.7822
`
`
`
`
`
`
`
`
`
`
`
`Paper No. 7
`
`
`Entered: March 20, 2017
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`APPLE, INC.,
`Petitioner,
`
`v.
`
`REALTIME DATA LLC,
`Patent Owner.
`____________
`
`Case IPR2016-01738
`Patent 8,880,862 B2
`____________
`
`
`
`Before GEORGIANNA W. BRADEN, J. JOHN LEE, and
`JASON J. CHUNG, Administrative Patent Judges.
`
`BRADEN, Administrative Patent Judge.
`
`DECISION
`Granting Institution of Inter Partes Review
`37 C.F.R. § 42.108
`
`
`
`
`
`
`
`
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`INTRODUCTION
`
`I.
`
`A. Background
`
`Apple, Inc. (“Petitioner”) filed a Petition (Paper 2, “Pet.”) requesting
`an inter partes review of claims 8–12, 14–22, 59–82, 101–104, 114–115,
`and 117 (“the challenged claims”) of U.S. Patent No. 8,880,862 B2
`(Ex. 1001, “the ’862 Patent”). Realtime Data, LLC (“Patent Owner”) timely
`filed a Preliminary Response (Paper 6, “Prelim. Resp.”).
`Under 35 U.S.C. § 314, an inter partes review may not be instituted
`
`unless the information presented in the Petition shows “there is a reasonable
`likelihood that the petitioner would prevail with respect to at least 1 of the
`claims challenged in the petition.” See also 37 C.F.R § 42.4(a) (delegating
`authority to the Board). Upon consideration of the Petition, Patent Owner’s
`Preliminary Response, and the evidence cited therein, we determine that the
`information presented demonstrates a reasonable likelihood that Petitioner
`would prevail in establishing the unpatentability of each of the challenged
`claims. Accordingly, we institute an inter partes review of the challenged
`claims.
`
`B. Related Proceedings
`
`The parties identify the following cases as related to the challenged
`patent: Realtime Data, LLC v. Microsoft Corporation, Case No. 4:14-cv-
`00827 (E.D. Tex.), Realtime Data, LLC v. Microsoft Corporation, Case No.
`6:15-cv-00885 (E.D. Tex.), and Realtime Data, LLC v. Apple, Inc., Case No.
`3:16-cv-02595 (N.D. Cal.) (transferred from Realtime Data, LLC v. Apple,
`Inc., Case No. 6:15-cv-00885 (E.D. Tex.)). Pet. 1; Paper 5, 2.
`
`2
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`C. The ’862 Patent
`
`
`
`The ’862 Patent relates to “providing accelerated loading of operating
`
`system and application programs upon system boot or application launch,”
`and the use of data compression and decompression techniques for such
`purpose. Ex. 1001, 1:20–26. The specification discusses the limits of prior
`art storage devices, particularly the significant bandwidth limitations of
`“mass storage devices” such as hard disk drives. Id. at 1:43–57, 2:9–18.
`According to the specification,
`“[A]ccelerated” data storage comprises receiving a digital data
`stream at a data transmission rate which is greater than the data
`storage rate of a target storage device, compressing the input
`stream at a compression rate that increases the effective data
`storage rate of the target storage device and storing the
`compressed data in the target storage device.
`Id. at 5:41–47. One embodiment of the ’862 Patent is illustrated in Figure 1,
`reproduced below.
`
`
`As shown in Figure 1, data storage controller 10 is “operatively connected”
`to hard disk 11 and to host system’s bus 16. Id. at 5:63–6:53. Controller 10
`includes cache 13 for data storage/preloading, and data compression engine
`12 for data compression/decompression. Id. at 5:63–6:53, 20:50–22:11.
`The ’862 Patent explains that, following reset or power on of a computer
`
`3
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`system, the “initial bus commands inevitably instruct the boot device
`controller [e.g., controller 10] to retrieve data from the boot device (such as
`a disk) [e.g., hard disk 11] for the operating system.” Id. at 20:36–49.
`
`D. Illustrative Claims
`
`As noted above, Petitioner challenges claims 8–12, 14–22, 59–82,
`
`101–104, 114–115, and 117 of the ’862 Patent. Pet. 1. Claims 8, 11, and 14
`are independent. Claim 8 is illustrative of the challenged claims, and is
`reproduced below:
`8. A method of loading an operating system for booting a
`computer system, comprising:
`storing a portion of the operating system in a compressed
`form in a first memory;
`loading the portion of the operating system from the first
`memory to a second memory, the portion of the operating
`system being associated with a boot data list;
`accessing the loaded portion of the operating system from the
`second memory in the compressed form;
`decompressing the accessed portion of the operating system
`to provide a decompressed portion of the operating
`system;
`utilizing the decompressed portion of the operating system to
`at least partially boot the computer system; and
`updating the boot data list,
`wherein the portion of the operating system is accessed and
`decompressed at a rate that is faster than accessing the
`loaded portion of the operating system from the first
`memory if the portion of the operating system was to be
`stored in the first memory in an uncompressed form.
`
`Ex. 1001, 27:35–54.
`E. The Evidence of Record and Asserted Grounds of Unpatentability
`
`Petitioner asserts the following grounds of unpatentability under
`
`35 U.S.C. § 103 (Pet. 2–3):
`
`4
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`Challenged Claims
`All Challenged Claims
`All Challenged Claims
`All Challenged Claims
`All Challenged Claims
`All Challenged Claims
`
`
`Asserted Prior Art
`Sukegawa1 and Dye2
`Sukegawa, Dye, and Settsu3
`Sukegawa, Dye, and Burrows4
`Sukegawa, Dye, Settsu, and Burrows
`Sukegawa, Dye, and Zwiegincew5
`
`
`Additionally, Petitioner relies on the Declaration of Dr. Charles J. Neuhauser
`(Ex. 1003) to support its challenges.
`
`II. ANALYSIS
`
`A. Claim Construction
`In an inter partes review, claim terms in an unexpired patent are
`
`interpreted according to their broadest reasonable construction in light of the
`specification of the patent in which they appear. 37 C.F.R. § 42.100(b); see
`Cuozzo Speed Techs., LLC v. Lee, 136 S. Ct. 2131, 2144–46 (2016) (“We
`conclude that the regulation represents a reasonable exercise of the
`rulemaking authority that Congress delegated to the Patent Office.”). Under
`that standard, and absent any special definitions, we give claim terms their
`ordinary and customary meaning, as would be understood by one of ordinary
`
`
`1 U.S. Patent No. 5,860,083, issued Jan. 12, 1999 (Ex. 1005, “Sukegawa”).
`2 U.S. Patent No. 6,145,069, filed Apr. 26, 1999, issued Nov. 7, 2000
`(Ex. 1008, “Dye”).
`3 U.S. Patent No. 6,374,353 B1, filed Mar. 3, 1999, issued Apr. 16, 2002
`(Ex. 1006, “Settsu”).
`4 Michael Burrows et al., On-line Data Compression in a Log-structured
`File System (1992) (Ex. 1007, “Burrows”).
`5 U.S. Patent No. 6,317,818 B1, filed Mar. 30, 1999, issued Nov. 13, 2001
`(Ex. 1010, “Zwiegincew”).
`
`5
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`skill in the art at the time of the invention. In re Translogic Tech., Inc.,
`504 F.3d 1249, 1257 (Fed. Cir. 2007). An inventor, however, may provide a
`meaning for a term that is different from its ordinary meaning by defining
`the term in the specification with “reasonable clarity, deliberateness, and
`precision.” In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994).
`Limitations, however, are not to be read from the specification into the
`claims. In re Van Geuns, 988 F.2d 1181, 1184 (Fed. Cir. 1993). In addition,
`the Board may not “construe claims during [an inter partes review] so
`broadly that its constructions are unreasonable under general claim
`construction principles.” Microsoft Corp. v. Proxyconn, Inc., 789 F.3d
`1292, 1298 (Fed. Cir. 2015).
`
`Based on a review of the record, we determine that no claim terms
`require express construction for purposes of this Decision. See Vivid Techs.,
`Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999).
`
`B. Principles of Law
`A claim is unpatentable under 35 U.S.C. § 103(a) if “the differences
`between the subject matter sought to be patented and the prior art are such
`that the subject matter as a whole would have been obvious at the time the
`invention was made to a person having ordinary skill in the art to which said
`subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406
`(2007). The question of obviousness is resolved on the basis of underlying
`factual determinations, including (1) the scope and content of the prior art;
`(2) any differences between the claimed subject matter and the prior art;
`(3) the level of skill in the art; and (4) objective evidence of nonobviousness,
`i.e., secondary considerations. See Graham v. John Deere Co. of Kansas
`City, 383 U.S. 1, 17–18 (1966).
`
`6
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`“A determination of whether a patent claim is invalid as obvious
`under § 103 requires consideration of all four Graham factors, and it is error
`to reach a conclusion of obviousness until all those factors are considered.”
`Apple Inc. v. Samsung Elecs. Co., Ltd., 839 F.3d 1034, 1048 (Fed. Cir. 2016)
`(en banc) (citations omitted). “This requirement is in recognition of the fact
`that each of the Graham factors helps inform the ultimate obviousness
`determination.” Id.
`“In an [inter partes review], the petitioner has the burden from the
`onset to show with particularity why the patent it challenges is
`unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed.
`Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review
`petitions to identify “with particularity . . . the evidence that supports the
`grounds for the challenge to each claim”)). This burden never shifts to
`Patent Owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800
`F.3d 1375, 1378 (Fed. Cir. 2015) (citing Tech. Licensing Corp. v. Videotek,
`Inc., 545 F.3d 1316, 1326–27 (Fed. Cir. 2008)) (discussing the burden of
`proof in inter partes review). Furthermore, Petitioner cannot satisfy its
`burden of proving obviousness by employing “mere conclusory statements.”
`In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016).
`Thus, to prevail in an inter partes review, Petitioner must explain how the
`proposed combinations of prior art would have rendered the challenged
`claims unpatentable. At this preliminary stage, we determine whether the
`information presented in the Petition shows there is a reasonable likelihood
`that Petitioner would prevail in establishing that the challenged claims
`would have been obvious over the proposed combinations of prior art.
`We analyze the challenges presented in the Petition in accordance
`with the above-stated principles.
`
`7
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`C. Level of Ordinary Skill in the Art
`
`
`
`In determining whether an invention would have been obvious at the
`time it was made, we consider the level of ordinary skill in the pertinent art
`at the time of the invention. Graham, 383 U.S. at 17. “The importance of
`resolving the level of ordinary skill in the art lies in the necessity of
`maintaining objectivity in the obviousness inquiry.” Ryko Mfg. Co. v.
`Nu-Star, Inc., 950 F.2d 714, 718 (Fed. Cir. 1991).
`Petitioner’s declarant, Dr. Charles J. Neuhauser, opines that a person
`of ordinary skill in the art relevant to the ’862 patent would have had “a
`Bachelor’s Degree in electrical engineering, computer engineering, or a
`related area of study” as well as “between three and five years of practical
`experience in the design and implementation of computer systems, such as
`personal computers.” Dr. Neuhauser further opines that, in the alternative, a
`person with “a Master’s Degree in the area of electrical engineering,
`computer engineering, or a related area of study and somewhat less practical
`experience would be similarly qualified.” Ex. 1003 ¶ 15. At this time,
`Patent Owner does not dispute Dr. Neuhauser’ testimony or proffer its own
`assessment regarding a person of ordinary skill in the art relevant to the ’862
`patent at the time of the invention.
`
`Based on our review of the ’862 patent, the types of problems and
`solutions described in the ’862 patent and cited prior art, and the testimony
`of Dr. Neuhauser, we adopt and apply Dr. Neuhauser’s definition of a person
`of ordinary skill in the art at the time of the claimed invention for purposes
`of this Decision. We also note that the applied prior art reflects the
`appropriate level of skill at the time of the claimed invention. See Okajima
`v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).
`
`8
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`D. Overview of the Asserted Prior Art
`1.
`Sukegawa
`
`
`Sukegawa is a U.S. Patent titled “Data Storage System Having Flash
`Memory and Disk Drive” and relates to “a data storage system using a flash
`memory unit and an HDD [(hard disk drive)].” Ex. 1005, at [54], [57]. One
`embodiment of Sukegawa is shown in Figure 1, reproduced below.
`
`
`Figure 1 illustrates a data storage system applied to a computer system. Id.
`at 4:2–4. The system includes flash memory unit 1 and hard disk drive
`(HDD) 2. Id. at 4:5–6. The flash memory unit is used, for example, to store
`“data which is used frequently for a relatively long time period.” Id. at [57].
`Such data could include “control information necessary for starting an
`application program (AP) and an OS [(operating system)].” Id. at 2:65–3:3.
`Although such control information is stored on the HDD, the data may be
`stored also on the flash memory unit so that the OS may be started using the
`control information on the flash memory unit instead of the HDD. Id. at
`6:45–54. This is advantageous because the flash memory unit has a “higher
`access speed,” which allows the OS to be started more quickly. Id. at 6:54–
`58.
`
`9
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`
`Dye
`2.
`
`Dye is a U.S. Patent titled “Parallel Decompression and Compression
`
`System and Method for Improving Storage Density and Access Speed for
`Non-Volatile Memory and Embedded Memory Devices.” Ex. 1008, at [54].
`Dye relates to controllers for flash or embedded memory that include data
`compression and decompression engines “for increased effective memory
`density and improved bandwidth.” Id. at 1:17–22, 2:42–46. According to
`Dye, such a controller enables conventional flash memory to “achieve higher
`bandwidth, more effective density, with less system power and noise.” Id. at
`3:3–12, 3:23–28. The technology permits data to be “saved in either a
`normal or compressed format, retrieved from the Flash Memory Array for
`MPU [(microprocessing unit)] execution in a normal or compressed format,
`or transmitted and stored on a medium in a normal or compressed format.”
`Id. at 3:66–4:8.
`3.
`Settsu
`
`
`Settsu is a U.S. Patent titled “Information Processing Apparatus
`Method [sic] of Booting Information Processing Apparatus at a High Speed”
`and relates to “[a] method of booting up an information processing
`apparatus.” Ex. 1006, at [54], [57]. One embodiment of Settsu is shown in
`Figure 1, reproduced below.
`
`10
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`
`
`
`Figure 1 illustrates an information processing apparatus with boot device 3,
`firmware 6, memory device 2, and boot block 4. Id. at 8:2–8. According to
`Settsu, boot block 4 includes a mini operating system (OS) module that has
`OS functions required for bootstrap processing, and an OS main body
`module located in file system 5 that provides the apparatus with the OS
`functions not included on mini OS module 7. Id. at 8:13–21.
`
`Two other embodiments of Settsu are shown in Figures 6 and 13,
`reproduced below.
`
`
`
`Figures 6 and 13 illustrate dividing up Mini OS Module 7. Id. at 10:59–
`11:3, 13:66–14:6. Settsu discloses that Mini OS Module 7 can include OS
`loading and decompression processing module 50 so that modules can be
`stored as compressed files on a boot device. Id. at 14:6–12, 14:58–63. Each
`of these modules is decompressed each time it is loaded into memory, and
`
`11
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`“the time required for I/O [(input/output)] processing can be reduced” as a
`result, which “provides an advantage of being able to further reduce the time
`required for booting up the information processing apparatus.” Id. at 14:64–
`15:4.
`Burrows
`4.
`
`Burrows is a conference report titled “On-line Data Compression in a
`
`Log-structured File System,” and it “appeared in the proceedings of the Fifth
`International Conference on Architectural Support for Programming
`Languages and Operating Systems (ASPLOS-V), 12–15 October, 1992,
`published by ACM Press.” Ex. 1007, Title, iv. According to Burrows,
`“[b]uilding a file system that compresses the data it stores on disk is clearly
`an attractive idea,” at least because “more data would fit on the disk” and
`using a “fast hardware data compressor” would “increase the effective disk
`transfer rate by the compression factor, thus speeding up the system.” Id. at
`1. Burrows teaches a particular type of file system utilizing data
`compression and reports the results of tests of that system.
`Zwiegincew
`5.
`Zwiegincew is a U.S. Patent titled “Pre-Fetching of Pages Prior to a
`
`Hard Page Fault Sequence,” and it recognizes problems of slow boot that
`result when hard page faults occur during the boot process. Ex. 1010, at
`[54], 1:45–51, 2:12–15, 5:50–51. To improve boot speed, Zwiegincew
`proposes pre-fetching, from a hard disk to memory, pages that are expected
`to be requested during the boot process, thereby reducing occurrence of hard
`page faults. Id. at [57], 1:5–3:55. “Copies of, or references to, the . . . pages
`are stored in a scenario file” and, “[w]hen a hard page fault scenario is
`detected, a corresponding scenario file is fetched from disk storage and the
`determined pages, or copies thereof, are transferred into RAM.” Id. at [57].
`
`12
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`Zwiegincew also recognizes benefits of compressing pre-fetched page data.
`For instance, Zwiegincew’s system includes “a disk
`compressor/decompressor,” which employs “compression algorithms” on
`pre-fetched data to achieve pre-fetch time improvements. Id. at 8:66–9:13,
`Figs. 1–2.
`
`Analysis of Cited Art as Applied to Independent Claims 8, 11,
`
`E. Alleged Obviousness of the Challenged Claims in View of Sukegawa and
`Dye
`Petitioner contends the combination of Sukegawa and Dye teaches or
`
`suggests each element of claims 8–12, 14–22, 59–82, 101–104, 114–115,
`and 117. Pet. 6–55. Patent Owner disputes Petitioner’s contentions. Prelim.
`Resp. 9–30. For reasons that follow, we determine Petitioner has
`demonstrated a reasonable likelihood of prevailing as to the challenged
`claims.
`1.
`
`and 14
`
`Petitioner contends the combined teachings of Sukegawa and Dye
`render every element of independent claims 8, 11, and 14 of the ’862 patent
`obvious. Pet. 6–34. Patent Owner disputes Petitioner’s contentions. Prelim.
`Resp. 9–30. Patent Owner specifically argues that Petitioners fail to show
`that Sukegawa and Dye teaches (1) the “load[ing]” step in claims 8 and 11
`(id. at 12–13, 29–30); (2) the “access[ing]” step in claims 8, 11, and 14 (id.
`at 14–15); (3) the “decompress[ing]” step in claims 8, 11, and 14 (id. at 15–
`16); (4) the “utilizing” clause in claims 8 and 11 (id. at 16–17); and (5)
`“updat[ing] the boot data list” in claims 8, 11, and 14 (id. at 38–44).
`
`After considering the parties’ arguments and evidence, we determine
`that Petitioner presents sufficient evidence to establish a reasonable
`likelihood of prevailing on the ground of obviousness in view of Sukegawa
`
`13
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`and Dye. We address the issues disputed by Patent Owner in more detail
`below.
`
`a. “loading the portion of the [compressed] operating system
`from the first memory to a second memory” and “loading boot
`data in a compressed form . . . from a boot device into a memo”
`
`For the recited steps of “loading the portion of the [compressed]
`
`operating system from the first memory to a second memory” (claim 8) and
`“loading boot data in a compressed form . . . from a boot device into a
`memory” (claim 11), Petitioner identifies teachings in Sukegawa relating to
`maintaining “control information” necessary for starting an OS or an
`application program as boot data used for booting a computer system. Pet.
`11–16, 28–29. For the step of “loading,” Petitioner asserts that Sukegawa’s
`controller 3 loads boot data out of HDD2 (a first memory) and into flash
`memory 1 (a second memory) in performing “data input/output control
`(including cache operation control) for flash memory unit 1 and HDD.” Id.
`at 12 (citing Ex. 1005, 4:1–21, 5:1–6:17, 6:18–7:2; Ex. 1003 ¶ 292).
`According to Petitioner, Sukegawa teaches two techniques for loading boot
`data: (1) user selection of data to load, and (2) automatic selection of data to
`load. Id. (citing Ex. 1005, 5:10–6:58, 7:28–55).
`
`Petitioner contends Sukegawa discloses multiple forms of boot data
`lists that are associated with loaded boot data, and that are used in the
`loading process. Id. at 13 (citing Ex. 1003 ¶¶ 293–96). Petitioner further
`contends that by loading files (or portions of files) of application/OS control
`information into flash memory 1, Sukegawa’s controller 3 loads a portion of
`boot data associated with a portion of a boot data list for booting the
`computer system. Id. at 14 (citing Ex. 1003 ¶¶ 297–98). Petitioner relies on
`the testimony of Dr. Neuhauser to support its position.
`
`14
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`Dr. Neuhauser specifically opines that one of ordinary skill would
`
`have recognized that a file of control information, as described by
`Sukegawa, is a “list” (that is, a list of data) under a broadest reasonable
`interpretation. Ex. 1003 ¶ 297 (citing Ex. 1014 for a definition of the term
`“file” as “[a] complete, named collection of information, such as a program,
`a set of data used by a program, or a user-created document” that “binds a
`conglomeration of instructions . . . into a coherent unit that a user can
`retrieve, change, delete, save, or send to an output device”).6 As supported
`by the cited definition, Dr. Neuhauser testifies one of ordinary skill would
`have understood Sukegawa’s OS and AP program files to be lists of data
`(including, e.g., program instructions). Id. Dr. Neuhauser then testifies that
`because the files of control information maintained by controller 3 are
`necessary for starting the corresponding AP or OS, and because they may be
`used directly as a result of the turn-on of power, these files are, in this
`example, the claimed “list of boot data.” Id. Based on Dr. Neuhauser’s
`testimony, Petitioner concludes that Sukegawa’s loaded boot data (e.g.,
`application/OS control information) becomes part of a boot data list (e.g.,
`part of a file or files of boot data) and, thus, is associated with that boot data
`list. Pet. 14 (citing Ex. 1003 ¶ 297).
`
`
`6 The term “boot data list” is recited explicitly in the challenged claims. See,
`e.g., Ex. 1001, 26:41. Both parties provide contentions regarding the claim
`term, but neither provides a proposed construction. Dr. Neuhauser opines on
`the scope and application of the term, as supported by Exhibit 1014, which is
`sufficient for purposes of this Decision. See Ex. 1003 ¶ 297. To the extent,
`however, the parties present additional evidence concerning the proper scope
`of this term during the course of this proceeding, we will address it in the
`Final Written Decision.
`
`15
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`For the requirement that the boot data be compressed, Petitioner relies
`
`on Dye’s description of a memory controller using data compression and
`decompression engines to compress data for storage.7 Id. at 8. Petitioner
`argues that Dye describes a controller that “uses data compression and
`decompression for improved system cost and performance.” Id. at 8 (citing
`Ex. 1008, at [57], 2:42–4:55, 7:34–9:5, and 10:19–41), 16. Based on the
`testimony of its expert, Dr. Neuhauser, Petitioner argues a person of
`ordinary skill would have been motivated to apply these teachings of Dye to
`the control information of Sukegawa, and to modify Sukegawa, to increase
`the effective density and read access rate of the non-volatile storage devices
`in Sukegawa’s system, and to thereby achieve further reduction in the time
`required for booting up. Id. at 10–11 (citing Ex. 1003 ¶¶ 130–139).
`
`Patent Owner contests Petitioner’s position, arguing Petitioner fails to
`demonstrate that Dye teaches that compression technology could or should
`be used to load compressed “boot data” from a first memory (such as a hard
`disk drive) into a second memory as required by claim 8, or from a “boot
`device” (such as a hard disk drive) into memory as required by claim 11.
`Prelim. Resp. 12–13, 29–30. Specifically, Patent Owner argues that Dye’s
`compression engine 260 exists for one purpose: compressing uncompressed
`data entering flash memory controller 200 for storage in flash memory array
`100. Id. at 30 (citing Ex. 1008, 14:21–39). According to Patent Owner, a
`
`
`7 The Petition also relies on U.S. Patent Application No. 09/239,659 (issued
`as U.S. Patent No. 7,190,284 B2 (“Dye ’284,” Ex. 1009)), which Petitioner
`asserts is incorporated by reference into Dye. Pet. 12. Patent Owner
`contends Dye’s incorporation by reference of Dye ’284 is insufficient.
`Prelim. Resp. 9–11, 18–20. For purposes of this Decision, we need not
`reach this issue because Petitioner has made a sufficient showing for
`purposes of institution even without considering Dye ’284.
`
`16
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`person of ordinary skill in that art would not have been motivated by the
`teachings of Dye to load boot data that is already compressed and residing in
`other memory, such as Sukegawa’s HDD 2. Patent Owner further argues
`that Petitioner does not rely on Sukegawa to disclose or suggest these claim
`elements. Id. at 13.
`
`Despite Patent Owner’s contentions, as discussed above, we are
`satisfied that Petitioner explains sufficiently at this stage how the combined
`teachings of Sukegawa and Dye teach or at least suggest the loading step
`from a first memory (or boot device) into a second memory. See Pet. 11–16,
`28–29.
`
`b. accessing the loaded [boot data/operating system] in the
`compressed form” “decompressing . . . the operating system . .
`. at a rate that is faster than accessing…the operating system . .
`. in an uncompressed form” and “decompress[ing] the
`accessed…boot data . . . at a rate that decreases a [boot time
`of/time to load] the operating system”
`
`Petitioner contends that a person of ordinary skill in the art would
`
`have modified Sukegawa’s controller 3 to include Dye’s
`compression/decompression engine. Pet. 10–11 (citing Ex. 1003 ¶¶ 130–
`139, 165–167), 16–17 (citing Ex. 1003 ¶ 316). According to Petitioner, in
`servicing requests, controller 3 would access compressed control
`information from flash memory 1 and use Dye’s decompression engine to
`decompress the compressed control information at a rate that increases flash
`memory 1’s effective access rate. Id. at 11 (citing Ex. 1003 ¶¶ 138–39, 168;
`Ex. 1008, at [57], 2:42–4:55, 7:34–9:5, 10:19–21), 17–18 (citing Ex. 1003 ¶¶
`325–327), 29–30 (citing Ex. 1003 ¶¶ 391–92, 398), 32–33 (citing Ex. 1003
`¶¶ 428–30).
`
`17
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`Patent Owner’s arguments that Petitioner fails to show the asserted art
`
`teaches “accessing the loaded portion of the boot data in compressed form
`from the memory” and “decompressing the accessed . . . boot data in the
`compressed form at a rate that decreases a boot time” (Prelim. Resp. 14–16)
`are unpersuasive for similar reasons as discussed above.8 Therefore, based
`on the supporting testimony from Dr. Neuhauser, we are persuaded
`Petitioner’s evidence is sufficient at this stage of the proceeding. See Pet.
`10–11, 17–18, 29–30, 32–33; Ex. 1003 ¶¶ 138–39, 168, 391–92, 398, 428–
`30.
`
`c. “utilizing the decompressed…[boot data/operating system] to
`at least partially boot the computer system” or “to load at least
`a portion of the operating system”
`
`Petitioner contends Sukegawa’s controller 3 preloads, into flash
`
`memory 1, “control information” that is expected to be “necessary for
`starting” the OS, and accesses and utilizes the loaded control information to
`service requests “when the OS of the host system 4 is started in a series of
`operations from the turnon of power to the completion of the starting
`operation.” Pet. 19 (citing Ex. 1003 ¶ 330; Ex. 1005, 2:65–3:3, 5:1–6:17,
`6:23–26, 6:49–58, 7:28–39). Petitioner argues that a person of ordinary skill
`in the art would have understood that the “series of operations” including
`“the completion of the starting operation” of the OS necessarily includes
`partially booting the computer system of Sukegawa. Id. (citing Ex. 1003 ¶
`331). Petitioner further contends that a person of ordinary skill in the art
`
`
`8 Several of Patent Owner’s arguments appear to be based in large part on
`Patent Owner’s belief that the Petition improperly relies on Dye ’284. See,
`e.g., Prelim. Resp. 14 n.38, 15 n.41, 16n.43. As discussed above,
`Petitioner’s showing is sufficient at this stage even if Dye ’284 is not
`considered.
`
`18
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`would have modified Sukegawa’s controller 3 to service requests from
`Sukegawa’s host system by using Dye’s compression/decompression engine
`to decompress compressed data accessed from flash memory 1, including a
`portion of the operating system, to boot Sukegawa’s host computer system
`“at higher speed.” Id. at 19–20 (citing Ex. 1003 ¶¶ 332, 333).
`Dr. Neuhauser supports this position by testifying that a person of ordinary
`skill in the art would have understood that with the proposed modification,
`Sukegawa’s controller would have stored control information in HDD 2 in
`compressed form, loaded the compressed control information into flash
`memory unit 1, and used the compressed control information to service
`requests from Sukegawa’s host system. Ex. 1003 ¶ 332.
`
`Patent Owner contests Petitioner’s position, arguing that Dye’s
`compression technology coupled to flash memory does not teach that the
`controller is capable of “utilizing the decompressed [boot data/operating
`system]” to load or boot the OS, as recited” in claims 8 and 11. Prelim.
`Resp. 16–17. At this stage of the proceeding, we are persuaded Petitioner
`has provided sufficient evidence and explanation that the combined
`teachings of Sukegawa and Dye teach or at least suggest “utilizing the
`decompressed…[boot data/operating system] to at least partially boot the
`computer system” and “to load at least a portion of the operating system.”
`Id.
`
`d. “updat[ing] the boot data list”
`Petitioner contends Sukegawa describes a boot data list in at least two
`
`ways: (1) in the form of lists of data that are stored within files of control
`information; and (2) in the form of table 3A, which records “[i]nformation
`for correlating the file name[s]” of control information with associated
`programs. Pet. 20 (citing Ex. 1003 ¶¶ 336–37; Ex. 1005, 5:1–6:17, 6:18–
`
`19
`
`

`

`IPR2016-01738
`Patent 8,880,862 B2
`
`
`7:2, 5:5–9, 5:41–47). Petitioner argues that Sukegawa’s description renders
`obvious updating both types of lists. Id. at 22 (citing Ex. 1003 ¶ 343).
`According to Petitioner, Sukegawa explains that a user runs “Sukegawa’s
`data storage utility program to load control information associated with an
`application program/OS into area 10A of flash memory 1, and uses the same
`data storage utility program to delete loaded control information.” Id. at 20
`(citing Ex. 1005, 5:10–6:17, 6:19–7:2). Petitioner notes that Sukegawa also
`“explains that controller 3 automatically updates control information
`associated with area 10C based on requests from host system 4.” Id. at 21
`(citing Ex. 1005, 7:40–55). From this description, Petitioner argues that a
`person of ordinary skill in the art “would have understood that automatic
`loading of control information into the non-volatile cache area 10C results in
`updates to boot data lists in Sukegawa; namely, updates to lists of boot data
`included in files of control information stored

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


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket