throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`___________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`___________________
`
`SONY INTERACTIVE ENTERTAINMENT LLC,
`Petitioner,
`
`v.
`
`BOT M8, LLC,
`Patent Owner.
`
`____________________
`
`Case IPR2020-01288
`U.S. Patent No. 7,664,988
`__________________________________________________________
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`
`
`
`
`
`
`
`
`

`

`
`
`TABLE OF CONTENTS
`

`

`

`
`Page
`Introduction .................................................................................................... 1 
`Overview of the ’988 Patent .......................................................................... 2 
`  Claim Construction ........................................................................................ 4 
`A. 
`“fault inspection program” .................................................................. 4 
`B. 
`“boot program” .................................................................................. 11 
`  Overview of the Asserted References ......................................................... 12 
`A. 
`Sugiyama ........................................................................................... 12 
`B. 
`Gatto .................................................................................................. 13 
`C.  Morrow ’952 and Morrow ’771 ........................................................ 15 
`D.  Yamaguchi ......................................................................................... 15 
`E. 
`Cheston .............................................................................................. 16 
`F. 
`Proudler ............................................................................................. 17 
`The Board Should Deny the Petition Pursuant To 35 U.S.C.
`§ 325(d) ........................................................................................................ 18 
`A. 
`Petitioner Presents the Same Prior Art and Arguments
`That the Office Previously Considered. ............................................ 21 
`1. 
`The Same, Similar, and Cumulative Nature
`Between the Asserted Art and the Prior Art
`Involved During Examination................................................. 22 
`The Extent of the Overlap Between the Arguments
`Made During Examination and the Manner in
`Which Petitioner Relies on the Prior Art or Patent
`Owner Distinguishes the Prior Art. ......................................... 25 
`Petitioner Failed to Sufficiently Demonstrate Error by the
`Office. ................................................................................................ 30 
`  The Challenged Claims are Patentable ........................................................ 32 
`A.  Ground 1: Claims 1–9 Are Patentable Over Sugiyama
`and Gatto ........................................................................................... 32 
`
`B. 
`
`2. 
`
`- i -
`
`

`

`1. 
`
`2. 
`
`2. 
`
`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`Petitioner Has Not Demonstrated That Sugiyama
`in View of Gatto Discloses the Claimed Fault
`Inspection Program ................................................................. 32 
`Petitioner Has Not Demonstrated That Sugiyama
`in View of Gatto Disclose a Control Device that
`“Completes the Execution of the Fault Inspection
`Program Before the Game is Started” ..................................... 39 
`Ground 2: Claims 1-9 Are Patentable Over Morrow ’952
`and Morrow ’771 ............................................................................... 43 
`1. 
`Petitioner Has Not Demonstrated That Morrow
`’952 and Morrow ’771 Disclose the Claimed Fault
`Inspection Program ................................................................. 43 
`Petitioner Has Not Demonstrated that Morrow
`’952 and Morrow ’771 Disclose “a First Memory
`Device [for Storing or Configured to Store] a Boot
`Program Executed When the Gaming Device is
`Started to Operate” .................................................................. 46 
`Grounds 3 and 4: Claims 2, 7 Are Further Patentable
`Over Yamaguchi ................................................................................ 47 
`D.  Grounds 5 and 6: Claim 8 Is Further Patentable Over
`Proudler ............................................................................................. 48 
`Ground 7 and 8: Claim 10 Is Further Patentable Over
`Cheston .............................................................................................. 48 
`  Conclusion ................................................................................................... 53 
`
`
`B. 
`
`C. 
`
`E. 
`
`
`
`- ii -
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Federal Cases
`Advanced Bionics, LLC v. MED-EL Elektromedizinische Geräte
`GmbH,
`No. IPR2019-01469, Paper 6 (P.T.A.B. Feb. 13, 2020) ................... 19, 22, 30, 31
`Akzo Nobel Coatings, Inc. v. Dow Chem. Co.,
`811 F.3d 1334 (Fed. Cir. 2016) ............................................................................ 7
`Becton, Dickinson, & Co. v. B. Braun Melsungen AG,
`No. IPR2017-01586, Paper 8 (P.T.A.B. Dec. 15, 2017) ........................ 21, 22, 31
`Becton, Dickinson & Co. v. Tyco Healthcare Grp., LP,
`616 F.3d 1249 (Fed. Cir. 2010) ...................................................................... 7, 10
`E-Pass Techs., Inc. v. 3Com Corp,
`343 F.3d 1364 (Fed. Cir. 2003) ............................................................................ 5
`K/S Himpp v. Hear–Wear Techs,
`4751 F3d 1362 (Fed. Cir. 2014) ......................................................................... 45
`McKesson Information Solutions, Inc. v. Bridge Medical, Inc.,
`487 F.3d 897 (Fed. Cir. 2007) ............................................................................ 26
`Neville v. Found. Constructors, Inc.,
`972 F.3d 1350 (Fed. Cir. Aug. 27, 2020) ............................................................. 7
`Personalized Media Communs., LLC v. Apple Inc.,
`952 F.3d 1336 (Fed. Cir. Mar. 13, 2020) ................................................ 10, 12, 46
`Phillips v. AWH Corp,
`415 F.3d 1303 (Fed. Cir. 2005) .......................................................................... 10
`Power Mosfet Techs., LLC v. Siemens AG,
`378 F3d 1396 (Fed. Cir. 2004) ............................................................................. 8
`ProMOS Techs., Inc. v. Samsung Elecs. Co., Ltd.,
`809 Fed. Appx. 825 (Fed. Cir. Apr. 6, 2020) ....................................................... 5
`
`- iii -
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`Shire Dev., LLC v. Watson Pharms., Inc.,
`787 F. 3d 1359 (Fed. Cir. 2015)f ........................................................................ 47
`Sunovian Pharms. Inc. v. Teva Pharms USA, Inc.,
`809 Fed. Appx. 825 (Fed. Cir. Apr. 6, 2020) .......................................... 5, 10 , 46
`Sony Interactive Entertainment LLC v. Bot M8, LLC,
`IPR2020-00726, Paper No. 13 (P.T.A.B. Oct. 6, 2020) ................................. 9, 10
`Travelocity.com L.P. v. Cronos Techs., LLC,
`No. CBM2014-00082, Paper 12 (P.T.A.B. Oct. 16, 2014) .................................. 2
`Willis Elec. Co., Ltd. v. Polygroup Macau Ltd. (BVI),
`777 Fed. Appx. 495 (Fed. Cir. 2019) .............................................................. 7, 10
`Federal Statutes
`35 U.S.C. § 325(d) ............................................................................................passim
`Other Authorities
`37 C.F.R. § 1.97(e) ....................................................................................... 20, 22, 25
`37 C.F.R. §§ 1.98(a)(2)–(3) ..................................................................................... 26
`37 C.F.R. § 42.104(b)(4) .......................................................................................... 34
`
`
`- iv -
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`On July 27, 2020, Sony Interactive Entertainment LLC (“Sony” or
`
`“Petitioner”) submitted a Petition to institute inter partes review of Bot M8, LLC’s
`
`(“Bot M8” or “Patent Owner”) U.S. Patent No. 7,664,988 (Ex. 1001, “the ’988
`
`Patent”), challenging claims 1–10 (“the Challenged Claims”). The Board should
`
`deny institution of inter partes review because Petitioner has not demonstrated a
`
`reasonable likelihood that any Challenged Claim is unpatentable.
`
`
`
`Introduction
`The Board should deny the Petition because every Challenged Claim
`
`requires a separate boot program and fault inspection program. As set forth below,
`
`the proposed grounds variously identify only a single program that purportedly
`
`performs the boot and fault inspection programs—failing to satisfy the separate
`
`program requirement—or do not even disclose a fault inspection program.
`
`Without such a disclosure, none of the grounds create a reasonable likelihood that
`
`any Challenged Claim is unpatentable.
`
`The Board should also deny the Petition because it rehashes the same prior
`
`art and arguments that were cited during prosecution. In particular, the file history
`
`submitted by Petitioner fails to include a European Search Report that the
`
`Applicant submitted during prosecution. See Ex. 1002 at 61–62, 119–20; Ex.
`
`2007. The European Search Report characterizes Petitioner’s primary reference,
`
`Sugiyama (Ex. 1005), in the same way that Petitioner does. The Challenged
`
`1
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`Claims were allowed to issue over those arguments, and the Petition does not
`
`identify any reason why the Board should revisit the issue.1
`
`Although this case has some similarities to another case the Board already
`
`instituted, the Board should deny the Petition because the European Search Report
`
`was not disclosed in that case and because the proposed grounds fail to disclose
`
`separate boot and fault inspection programs.
`
` Overview of the ’988 Patent
`The technology underlying the ’988 Patent was developed by Universal
`
`Entertainment Corporation (“UEC”), a Japanese gaming conglomerate with a
`
`history dating back to 1969. Ex. 2008 at 1. UEC’s products include single and
`
`multiplayer arcade cabinets used in arcade gaming halls, software for home
`
`gaming machines such as Sony’s PlayStation, gaming software for personal
`
`computers, and electronic wagering machines such as slot machines. See id. at 1-3.
`
`
`
`1 Although there are a variety of reasons why the ’988 Patent is valid over
`
`Petitioner’s asserted references, this Preliminary Response focuses on only limited
`
`reasons why inter partes review should not be instituted. See Travelocity.com L.P.
`
`v. Cronos Techs., LLC, No. CBM2014-00082, Paper 12 at 10 (P.T.A.B. Oct. 16,
`
`2014) (“[N]othing may be gleaned from the Patent Owner’s challenge or failure to
`
`challenge the grounds of unpatentability for any particular reason.”).
`
`2
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`At the time of the invention, it was common for gaming machines, including
`
`those sold by Aruze Corporation/UEC, to experience faults, including damage to
`
`one or more of its memory devices and falsification or other changes to the
`
`programs stored thereon, but existing solutions were insufficient to address such
`
`faults. See ’988 Patent at 1:14–30.
`
`To address this long-felt need, the ’988 Patent discloses a gaming machine
`
`that executes a process for detecting faults in its hardware and software. Id. at
`
`1:15–16. This process, referred to in the ’988 Patent as a “fault inspection
`
`program” is responsible for detecting faults, including damage to the memory
`
`device and change or falsification of a game application stored in the memory
`
`device. Id. at 4:4–7. The fault inspection program is stored in a first memory
`
`device separate from a second memory device storing the game application
`
`program so that a fault in the second memory device will not affect the fault
`
`inspection program. Id. at 1:58–63, 4:22–29.
`
`Importantly, the fault inspection program is separate and distinct from the
`
`apparatus’ boot program, which may be stored in the same memory:
`
`3
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`
`
`Id. at FIG. 1 (annotated); see also id. at FIG. 2, 2:40–53; Ex. 1002 (’988 Patent
`
`FH) at 207. Executing the fault inspection program after the boot program has
`
`initialized the hardware and operating system but before executing the game
`
`program allows the fault inspection program to check all hardware and software
`
`components for faults and avoid issues during gameplay. ’988 Patent at 3:66–4:28.
`
` Claim Construction
`A.
`“fault inspection program”
`The proper construction of the term “fault inspection program” is “a
`
`program, other than a boot program, that inspects a memory device for faults,
`
`4
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`including damage to the memory device and change or falsification of programs
`
`stored thereon.”
`
`During prosecution of the ’988 Patent, the Applicant distinguished the
`
`Bizzarri reference (Ex. 1050) on the basis that “the boot program and the fault
`
`inspection program are distinct.” Ex. 1002 at 207 (emphasis added). This clear
`
`statement defines the meaning of the terms, and should control their construction.
`
`See ProMOS Techs., Inc. v. Samsung Elecs. Co., Ltd., 809 Fed. Appx. 825, 832
`
`(Fed. Cir. Apr. 6, 2020) (non-precedential) (“unless ‘the patentee has chosen to be
`
`his own lexicographer in the specification or has clearly disclaimed coverage
`
`during prosecution,’ we must interpret claims according to their plain language”)
`
`(quoting E-Pass Techs., Inc. v. 3Com Corp., 343 F.3d 1364, 1370 (Fed. Cir.
`
`2003)).
`
`The Applicant’s definitional statement during prosecution is consistent with
`
`the rest of the intrinsic record. The ’988 Patent explains that the term “fault
`
`inspection program” refers to “a program for inspecting whether or not a fault such
`
`as damage, change or falsification occurs in the programs or data” stored in a
`
`memory device. ‘988 Patent at 1:20-24. Moreover, the fault inspection program
`
`cannot simultaneously be the boot program. Id.
`
`5
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`Using Claim 1, reproduced below, as a representative claim for the ’988
`
`Patent, “the boot program” and “the fault inspection program” are claimed as
`
`separate programs:
`
`1. A gaming device configured to execute a game, the gaming
`device comprising:
`
`a first memory device for storing a boot program executed when
`the gaming device is started to operate;
`
`a mother board on which the first memory device is provided;
`
`a second memory device for storing a game application program
`for the game, the second memory device being connected to the mother
`board; and
`
`a control device for executing a fault inspection program for the
`gaming device to inspect whether or not a fault occurs in the second
`memory device and the game application program stored therein,
`
`wherein the fault inspection program is stored in the first
`memory device and the control device executes the fault inspection
`program when the gaming device is started to operate and completes
`the execution of the fault inspection program before the game is
`started.
`’988 Patent, Claim 1 (emphasis added).
`
`While “a boot program” and “a fault inspection program” must reside on the
`
`first memory device, Applicant UEC drafted the claims such that “a boot program”
`
`and “a fault inspection program” are listed as separate elements, so the plain
`
`language is that both “a boot program” and “a fault inspection program” must be
`
`6
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`distinct, mutually exclusive components of the patented invention. See id.; Ex.
`
`1002 at 207.
`
`Separately listed claim elements are distinct, mutually exclusive parts of
`
`claimed invention. Becton, Dickinson & Co. v. Tyco Healthcare Grp., LP, 616
`
`F.3d 1249, 1254 (Fed. Cir. 2010) (“Where a claim lists elements separately, ‘the
`
`clear implication of the claim language’ is that those elements are ‘distinct
`
`component[s]’ of the patented invention”). Moreover, separately-recited claim
`
`elements cannot “coexist as the same element.” Willis Elec. Co., Ltd. v. Polygroup
`
`Macau Ltd. (BVI), Case Nos. 2018-2125, 2018-2151, 777 Fed. Appx. 495, 498
`
`(Fed. Cir. 2019) (“Nothing in the claims suggest that ‘inner void’ and the ‘channel
`
`void’ can coexist as the same element.”).
`
`Furthermore, the Federal Circuit has held that “[a] claim construction that
`
`renders asserted claims facially nonsensical cannot be correct.” Neville v. Found.
`
`Constructors, Inc., No. 20-1132, 972 F.3d 1350, 1357 (Fed. Cir. Aug. 27, 2020)
`
`(affirming the lower court’s construction where a “protrusion” is “extending
`
`outwardly” from the “end plate” “does not extend to a structure in which the
`
`alleged ‘end plate’ is an indistinguishable part of the alleged ‘protrusion’; an object
`
`cannot protrude from itself”). Here, conflating the two program elements would
`
`render the separate claim elements meaningless surplusage. Akzo Nobel Coatings,
`
`Inc. v. Dow Chem. Co., 811 F.3d 1334, 1339–40 (Fed. Cir. 2016) (“Interpretations
`
`7
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`that render some portion of the claim language superfluous are disfavored.”)
`
`(quoting Power Mosfet Techs., LLC v. Siemens AG, 378 F.3d 1396, 1410 (Fed. Cir.
`
`2004)).
`
`The Specification and Claims confirm the fact that “the boot program and
`
`the fault inspection program are distinct.” Ex. 1002 at 207. For example, as
`
`illustrated in and described with respect to FIG. 1 of the ’988 Patent, the “boot
`
`program” and “fault inspection program” are distinct programs stored in distinct
`
`portions of the ROM:
`
`The ROM 13 corresponds to a first memory device. And in the ROM
`13, as shown in FIG. 1, a boot program storing area 13a for storing a
`boot program, a fault inspection program storing area 13b for storing
`a fault inspection program and a start program storing area 13c for
`storing a start program are formed.
`
`8
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`
`
`’988 Patent at 2:43–48 and FIG. 1 (annotated); see also id. at 2:49–53, 3:57–4:11.
`
`Accordingly, the intrinsic record demands that the “fault inspection
`
`program” recited in the Challenged Claims be distinct from a “boot program.” As
`
`discussed in detail below, because Petitioner contends that Sugiyama’s Start
`
`program is both a “boot program” and a fault inspection program, the purported
`
`invalidity challenge fails and the Petition must be denied.
`
`The Board’s construction of a parallel term in a different proceeding should
`
`not control. Sony Interactive Entertainment LLC v. Bot M8, LLC, IPR2020-00726,
`
`Paper No. 13 (P.T.A.B. Oct. 6, 2020) (“IPR2020-00726”). The Board’s conclusion
`
`that “[the Board] see[s] nothing in the record that precludes the ‘fault inspection
`
`9
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`program’ from also being a ‘boot program’” is contrary to the intrinsic record
`
`discussed above, including the Applicant’s definitional statement during
`
`prosecution, and the Federal Circuit precedent that separately listed elements
`
`should be construed to be distinct parts of the invention. Becton, Dickinson, 616
`
`F.3d at 1254; Willis Elec. Co., 777 Fed. Appx. at 498.
`
`The Petitioner’s construction, adopted by the Board in that case, is further
`
`flawed because it is based upon extrinsic evidence to the exclusion of all of the
`
`intrinsic evidence discussed above. IPR2020-00726, Paper No. 13, at 14–17.
`
`Extrinsic evidence is not to be used to contradict the unambiguous meaning of
`
`claim terms in view of the intrinsic record. Personalized Media Communs., LLC v.
`
`Apple Inc., 952 F.3d 1336, 1339 (Fed. Cir. Mar. 13, 2020) (“‘When construing
`
`claim terms, we . . . primarily rely on, the intrinsic evidence including the claims
`
`themselves, the specification, and the prosecution history of the patent, which is
`
`usually dispositive,’” in part because “‘patentees frequently use terms
`
`idiosyncratically.’”) (quoting Sunovion Pharms., Inc. v. Teva Pharms. USA, Inc.,
`
`731 F.3d 1271, 1276 (Fed. Cir. 2013) and Phillips v. AWH Corp., 415 F.3d 1303,
`
`1314 (Fed. Cir. 2005), respectively). Here, the Applicant’s plain definitional
`
`statement during prosecution should control.
`
`10
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`B.
`“boot program”
`The term “boot program” means “a program that initializes various devices
`
`including the extended BIOS and the operating system.” This construction follows
`
`from the explicit description of a “boot program” in the Specification of the ’988
`
`Patent:
`
`Here, the boot program is a program stored in the boot program storing
`area 13a of the ROM 13, and based on the boot program, initialization
`of various devices including the extended BIOS (Basic Input Output
`System) in the hard disk 24 and the OS (Operating System) in the
`hard disk 24 is executed.
`
`’988 Patent at 3:57–62 (emphasis added). This explanation is consistent with a
`
`POSITA’s understanding of the term “boot,” which involves a “computer
`
`execut[ing] the software that loads and starts the computer’s more complicated
`
`operating system and prepares it for use.” Ex. 2003 at 3.
`
` Petitioner’s proposed construction of the term “boot program”—that a “boot
`
`program” is “a small start-up program that enables a computer to load larger
`
`programs”—is overbroad. Petition at 6. As explicitly stated in the ’988
`
`Patent, the term “boot program” refers to a program that initializes various
`
`devices including the extended BIOS and the operating system. ’988 Patent
`
`at 3:57–62. Therefore, when the Specification provides a definition of a
`
`“boot program,” the definition holds particular precedence over other
`
`11
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`constructions. See Personalized Media Communs., LLC, 952 F.3d at 1339
`
`(“‘When construing claim terms, we . . . primarily rely on, the intrinsic
`
`evidence including the claims themselves, the specification, and the
`
`prosecution history of the patent, which is usually dispositive,’” in part
`
`because “‘patentees frequently use terms idiosyncratically.’”) (citations
`
`omitted).
`
`As discussed in detail below, Morrow ’952’s file allocation reader, which
`
`executes “before booting the operating system,” cannot be a “boot program”
`
`because the term “boot program” requires initialization of the operating system.
`
`See § VI.B, infra.
`
` Overview of the Asserted References
`A.
`Sugiyama
`Applicant UEC cited to the Office Japanese Unexamined Patent Application
`
`Publication No. JP 2000-35888 to Sugiyama (“Sugiyama”) in an Information
`
`Disclosure Statement (“IDS”) for the ’988 Patent. Ex. 1002 at 61–62.
`
`Sugiyama discloses a karaoke terminal that includes “a service program for
`
`causing a CPU to execute processing for examining and restoring failures and the
`
`like of a hard disk drive . . . .” Sugiyama at Abstract. Critically, and like the
`
`Bizzarri reference that was considered during prosecution of the ’988 Patent,
`
`Sugiyama discloses utilizing a boot program to “initially inspect[] whether or not
`
`12
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`an abnormality (i.e., fault) occurs on HDD 24.” Petition at 22; see also Sugiyama
`
`at [0022] (disclosing a “startup program” that determines whether or not an
`
`abnormality has occurred in a karaoke terminal). Only after this boot program
`
`runs, including detecting abnormalities, does Sugiyama execute an HDD inspection
`
`program, which merely “checks the details of the abnormality of the hard disk
`
`drive,” That was already detected by the boot program. Sugiyama at [0023].
`
`B. Gatto
`Gatto (Ex. 1006) discloses a method for verifying downloaded game
`
`software. Gatto at Abstract. The verification process uses a code signing
`
`mechanism to verify the code signature of downloaded code both after
`
`downloading and before executing the code. Gatto at 12:2-17.
`
`13
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`
`
`Gatto at FIG. 1.
`
`Unlike the “fault inspection program” disclosed and claimed in the ’988
`
`Patent, Gatto’s verification process only verifies a program’s code signature and
`
`fails to inspect a memory device for damage. See § III.A, supra (“The proper
`
`construction of the term ‘fault inspection program’ is ‘a program, other than a boot
`
`program, that inspects a memory device for faults, including damage to the
`
`memory device and change or falsification of programs stored thereon.’”).
`
`14
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`C. Morrow ’952 and Morrow ’771
`Like Gatto, Morrow ’952 discloses a verification program rather than a fault
`
`inspection program. Morrow ’952’s verification software 70 verifies the various
`
`system components by comparing identification numbers associated with the
`
`components against values stored in a database. Morrow ’952 at [0037]–[0041].
`
`Importantly, this verification software fails to inspect a memory device for faults
`
`and it is executed before the boot program. Id. at [0062].
`
`Morrow ’771 (Ex. 1008) discloses a similar software verification technique
`
`but rather than being executed prior to booting the system, Morrow ’771’s
`
`verification software executes “during boot-up and game operation.” Morrow ’771
`
`at [0037]. Accordingly, Morrow ’771 suffers from the same deficiencies as
`
`Morrow ’952 as well as Sugiyama, in that neither disclose a boot program nor a
`
`fault inspection program.
`
`D. Yamaguchi
`Yamaguchi discloses a static memory device that “has compatibility with a
`
`disk drive installed in an electronic apparatus as an external storage unit.”
`
`Yamaguchi at Abstract. In particular, Yamaguchi describes a “hard disk drive 22”
`
`having a “connector 22a to which is coupled the connector 8a provided at an end of
`
`the flat cable 8,” wherein “the hard disk drive 22 explained with reference to FIG.
`
`2C can also be connected to the connector 1a through the flat cable 8.” Id. at 5:5-
`
`15
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`8, 6:6-8, 6:21-23, Figs. 2C, 14. Notably, Yamaguchi does not disclose a boot
`
`program nor a fault inspection program.
`
`E. Cheston
`Cheston discloses a “system and method for storing adaptor card Option
`
`ROM BIOS extensions on the system’s DASD [Direct Access Storage Device]
`
`and, more particularly, on a partition of the DASD that is generally inaccessible to
`
`the operating system.” Cheston at Abstract. Cheston provides that “BIOS
`
`extensions files are stored in the hidden partition” of a hard disk drive. Id.
`
`Further, Cheston describes that the system BIOS, when executed, “interrogates the
`
`hidden partition [of hard disk drives or DASD 120] for BIOS extension files.” Id.
`
`Indeed, as Cheston shows in Figure 3, annotated below, “[i]f the hidden partition
`
`contains a BIOS extension file corresponding to an identified peripheral device,
`
`[then] the file is verified for authenticity,” prior to initializing the BIOS. Id. at
`
`[0024], FIG. 3.
`
`16
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`
`
`Cheston at FIG. 3 (annotated).
`
`F.
`Proudler
`Like the software verification program described in Morrow ’952 or the
`
`software validation program described in Cheston, Proudler discloses a “trusted
`
`17
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`component having a processor and trusted memory area” that carries out “[a]
`
`method of security monitoring of data files in a computer platform.” Proudler at
`
`Abstract. Indeed, Proudler describes “applying a hash function” to data files or, in
`
`other words, only software files to “produce hash function data corresponding to
`
`said data file,” wherein discrepancies or “differences between a previous and a
`
`current digest data indicate that a file in the untrusted memory area has been
`
`corrupted.” Id. at Abstract, 5:8–10.
`
` The Board Should Deny the Petition Pursuant To 35 U.S.C. § 325(d)
`The Board should deny the Petition pursuant to 35 U.S.C. § 325(d) because
`
`it rehashes art and arguments already before the Office during original prosecution.
`
`Specifically, Applicant submitted to the Office a European Search Report which
`
`discussed the same aspects of Sugiyama that the Petition relies on. Petitioner did
`
`not include this important non-patent literature document in its submission of the
`
`file history along with the Petition. The Applicant also overcame other references
`
`and arguments that are the same or substantially the same as the grounds presented
`
`in the Petition.
`
`Because the Petition presents grounds cumulative over those already
`
`considered, the Board should exercise its discretion to deny institution of the inter
`
`partes review of the Challenged Claims of the ’988 Patent under 35 U.S.C.
`
`§ 325(d). The subject matter of the prior art relied on by Petitioner was previously
`
`18
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`considered and distinguished during prosecution of the ’988 Patent. See Ex. 1002;
`
`Ex. 2007.
`
`The Board uses a two-part framework to evaluate whether to exercise its
`
`discretion under Section 325(d). Advanced Bionics, LLC v. MED-EL
`
`Elektromedizinische Geräte GmbH, No. IPR2019-01469, Paper 6 at 8-9 (P.T.A.B.
`
`Feb. 13, 2020) (precedential) (framework demonstrates “a commitment to defer to
`
`previous Office evaluations of the evidence of record unless material error is
`
`shown.”) (emphasis added). The Board focuses on: (1) whether the same or
`
`substantially the same art or arguments previously were presented to the Office;
`
`and (2) if that condition is satisfied, then whether Petitioner has demonstrated that
`
`the Office erred in a manner material to the patentability of the Challenged Claims.
`
`Id.
`
`As previously mentioned, during prosecution of the ‘988 Patent, Applicant
`
`cited to the Office Japanese Unexamined Patent Application Publication No. JP
`
`2000-35888 to Sugiyama (“Sugiyama”) in an Information Disclosure Statement2
`
`(“IDS”) for the ’988 Patent. Ex. 1002 at 61–62.
`
`
`
`2 Applicant UEC submitted the IDS pursuant to its duty to the PTO to
`
`disclose references relied upon in a European Search Report from a co-pending
`
`19
`
`

`

`IPR2020-01288 (U.S. Patent No. 7,664,988)
`Patent Owner’s Preliminary Response
`
`This European Search Report and Opinion is missing from Petitioner’s
`
`purported submission of the ’988 Patent’s file history wrapper. See Ex. 1002 at 61
`
`(“The applicant(s) wish to make of record the reference(s) cited in the attached
`
`Extended European Search Report and listed on the attached form PTO-1449”),
`
`119–20 (Electronic Filing Receipt dated January 25, 2008, showing the submission
`
`of a six-page document with the Document Description “NPL Document[]”).
`
`This now-missing-but-previously-filed non-patent literature (NPL)
`
`document referenced in the Electronic Filing Receipt is the Extended European
`
`Search Report, as evidenced by the following: (1) the submitted foreign references
`
`match the cited art in the search report and IDS, (2) the search report and IDS both
`
`cite the same art, (3) the transmittal letter explicitly references “an attached
`
`Extended European Search Report,” and (4) under 37 C.F.R. § 1.97(e), the
`
`Applicant must disclose the art cited within European Search Report (dated
`
`December 7, 2007) “not more than three months prior to” the filing of the IDS
`
`
`
`European Patent (EPO) counterpart EP 1630659 (EP Application No. 05018280.7).
`
`Ex. 1002 at 119–20; see 37 C.F.R. § 1.97(e). Both the ’988 Patent and its EPO
`
`counterpart claim priority to the same Japanese Patent Application JP 2004-
`
`245337, and the counterpart is the only foreign counterpart filed with the European
`
`Patent Office. Ex. 1001 at code (30); Ex. 2009 a

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