throbber

`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`__________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`__________________________________________________________________
`
`
`
`UNIFIED PATENTS, INC.
`Petitioner
`
`
`
`v.
`
`
`
`SPEX TECHNOLOGIES, INC.
`Patent Owner
`
`
`
`Patent No. 6,088,802
`Filing Date: June 4, 1997
`Issue Date: July 11, 2000
`Title: PERIPHERAL DEVICE WITH INTEGRATED SECURITY
`FUNCTIONALITY
`
`
`
`__________________________________________________________________
`
`SPEX TECHNOLOGIES, INC.’S
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`Case No. IPR2017-00430
`__________________________________________________________________
`
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`
`
`I.
`
`II.
`
`TABLE OF CONTENTS
`
`Page(s)
`
`INTRODUCTION ........................................................................................... 1
`
`THE PETITION SHOULD NOT BE INSTITUTED BECAUSE
`PETITIONER'S CLAIM CONSTRUCTIONS ARE INCORRECT
`IN LIGHT OF THE SPECIFICATION, THE CLAIMS, AND THE
`LAW ................................................................................................................ 3
`
`A.
`
`The Board Should Deny Institution on All Grounds Because
`Petitioner’s Construction of the “Security Means” Fails to
`Identify the Corresponding Structure .................................................... 3
`
`III.
`
`PETITIONER HAS NOT DEMONSTRATED A REASONABLE
`LIKELIHOOD OF SUCCESS FOR THE GROUNDS
`ADVANCED IN THE PETITION, AND THE PETITION
`SHOULD BE DENIED. .................................................................................. 7
`
`Requirements for Showing Anticipation Under 35 U.S.C.
`§ 102 and Obviousness Under 35 U.S.C. § 103. ................................... 7
`
`Ground I: Claims 1, 2, 6, 7, 11-13, 23-26, and 36-39 Are Not
`Anticipated by Jones ............................................................................. 9
`
`1.
`
`2.
`
`3.
`
`4.
`
`Petitioner Failed to Show that the Claimed “Security
`Means” Is Disclosed in Jones ..................................................... 9
`
`Petitioner Failed to Show that the Claimed “Means for
`Operably Connecting” Is Disclosed in Jones ............................10
`
`Petitioner Failed to Show that the Claimed “Means for
`Mediating Communications . . . so that the
`Communicated Data Must First Pass through the
`Security Means” Is Disclosed in Jones .....................................12
`
`Petitioner Failed to Show that Claims 38 and 39 Are
`Anticipated by Jones .................................................................17
`
`i
`
`A.
`
`B.
`
`
`
`

`

`
`
`C.
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Ground II: Claims 5, 10, 14, 22, 27, and 35 Are Not Obvious
`over Jones in View of Harari ...............................................................18
`
`D. Ground III: Claims 1-39 Are Not Obvious Over Clark in View
`of USB Specification ...........................................................................18
`
`1.
`
`2.
`
`3.
`
`4.
`
`Petitioner Failed to Show that the Claimed “Security
`Means” Is Obvious Over Clark in View of the USB
`Specification ..............................................................................19
`
`Petitioner Failed to Identify Where the “Target
`Means” Is Found in Clark or the USB Specification ................19
`
`Petitioner Failed to Show that the Corresponding
`Structure for the Claimed “Means for Mediating
`Communications” Is Disclosed in Clark or the USB
`Specification ..............................................................................20
`
`Petitioner Failed to Show that Claims 38 and 39 Are
`Obvious Over Clark in View of the USB Specification ...........21
`
`IV. CONCLUSION ..............................................................................................22
`
`
`
`
`
`ii
`
`

`

`
`
`Cases
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Golight, Inc. v. Wal-Mart Stores, Inc.,
`355 F.3d 1327 (Fed. Cir. 2004) ............................................................................ 4
`
`Net MoneyIN, Inc. v. VeriSign, Inc.,
`545 F.3d 1359 (Fed. Cir. 2008) ............................................................................ 7
`
`Transclean Corp. v. Bridgewood Servs., Inc.,
`290 F.3d 1364 (Fed. Cir. 2002) ...................................................................... 8, 12
`
`Verdegaal Bros., Inc. v. Union Oil Co. of Cal.,
`814 F.2d 628 (Fed. Cir. 1987) .............................................................................. 7
`
`Williamson v. Citrix Online, LLC,
`792 F.3d 1339 (Fed. Cir. 2015) ........................................................................ 5, 6
`
`Statutes
`
`35 U.S.C. § 102 .......................................................................................................... 7
`
`35 U.S.C. § 103 .......................................................................................................... 7
`
`35 U.S.C. § 112(6) ..................................................................................................... 6
`
`35 U.S.C. § 312(a)(3) ............................................................................................... 10
`
`35 U.S.C. § 314(a) ..................................................................................................... 2
`
`Other Authorities
`
`37 C.F.R. 42.104(b) ..........................................................................................passim
`
`iii
`
`
`
`
`
`

`

`I.
`
`INTRODUCTION
`
`On December 14, 2016, Unified Patents, Inc. (“Petitioner”) submitted a
`
`Petition (the “Petition”) to institute inter partes review (“IPR”) of U.S. Patent
`
`No. 6,088,802 (Ex. 1001, “the ’802 Patent”), challenging Claims 1 to 39 (“the
`
`Challenged Claims”).
`
`The Petition should be denied because it is deficient in several respects.
`
`First, Petitioner does not properly construe the means-plus-function claim term,
`
`“security means.” The Petition fails to identify the function and the corresponding
`
`structure of the security means disclosed in the specification, but generically
`
`identifies “hardware, software and/or firmware” or a “device” without specifying a
`
`structure or algorithm clearly linked to the undisclosed function. Without a proper
`
`construction, Petitioner has also failed to show that the structure of the “security
`
`means” is found in the prior art.
`
`Second, Petitioner failed to show that the cited references, U.S. Patent
`
`No. 5,623,637 to Jones (“Jones”) and U.S. Patent No. 5,815,577 to Clark
`
`(“Clark”), disclose the structure of the “means for mediating communication . . . so
`
`that the communicated data must first pass through the security means.” Petitioner
`
`identified an “interface control device, including a conventional field-
`
`programmable gate away (FPGA)” as the corresponding structure for the claimed
`
`
`
`1
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`“means for mediating communication . . . so that the communicated data must first
`
`pass through the security means,” but provided no structural analysis of whether
`
`the cited references disclose an interface control device or an equivalent.
`
`Third, Petitioner fails to identify the “target means” disclosed in the Clark
`
`reference. The section of the Petition dedicated to the “target means” describes a
`
`variety of structures disclosed in Clark, but Petitioner does not specify which of
`
`these structures, if any, are the “target means.”
`
`Fourth, Petitioner asserts that Jones anticipates several claims of the ’802
`
`Patent, but then argues that the “means for operably connecting” is obvious over
`
`Jones in view of the knowledge of one of ordinary skill in the art concerning
`
`PCMCIA standards or drivers. As such, Petitioner fails to properly identify the
`
`legal grounds for its invalidity arguments.
`
`Due to at least these deficiencies, the Petition does not establish “a
`
`reasonable likelihood that the Petitioner would prevail with respect to at least one
`
`of the claims challenged in the Petition.” 35 U.S.C. § 314(a). While Patent Owner
`
`explicitly reserves the right to provide further distinctions and deficiencies, the
`
`deficiencies of the Petition noted herein are sufficient for the Board to find that
`
`
`
`2
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Petitioner has not met its burden to demonstrate a reasonable likelihood that it
`
`would prevail in showing unpatentability of any of the Challenged Claims.
`
`II. THE PETITION SHOULD NOT BE INSTITUTED BECAUSE
`PETITIONER'S CLAIM CONSTRUCTIONS ARE
`INCORRECT IN LIGHT OF THE SPECIFICATION, THE
`CLAIMS, AND THE LAW1
`
`A. The Board Should Deny Institution on All Grounds Because
`Petitioner’s Construction of the “Security Means” Fails to
`Identify the Corresponding Structure
`
`The claim element “security means for enabling one or more security
`
`operations to be performed on data” is found in Claims 1-37. Petitioner’s proposed
`
`construction of “security means” is incorrect because Petitioner failed to identify a
`
`recited function and a corresponding structure disclosed in the specification that is
`
`
`
`1 For the sake of brevity, Patent Owner currently addresses only those of
`
`Petitioner’s claim constructions that are most relevant to the arguments in this
`
`response. The Petition is deficient, even without considering the scope of other
`
`constructions. Patent Owner’s silence regarding the appropriate construction of
`
`any term should not be taken as an agreement with Petitioner’s construction and
`
`Patent Owner reserves the right to challenge any of Petitioner’s constructions at a
`
`later juncture in this proceeding and elsewhere.
`
`
`
`3
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`clearly linked or associated with the function in the claim. Golight, Inc. v. Wal-
`
`Mart Stores, Inc., 355 F.3d 1327, 1334 (Fed. Cir. 2004). Petitioner bears the
`
`burden of identifying the claimed function and the specific portions of the
`
`specification that describe the structure corresponding to the claimed function
`
`when construing a means-plus-function claim term. 37 C.F.R. § 42.104(b)(3).
`
`Petitioner identifies two structures that allegedly correspond to the
`
`undisclosed function of the “security means”:
`
`1. Hardware, software and/or firmware capable of performing
`
`cryptographic or other related mathematical functions,
`
`including data encryption and decryption. See id. at 12:10-16,
`
`17:52-67, 15:63-67; see also id. at 2:30-32.
`
`2. A device that performs security operations and that includes
`
`one or more mechanisms to provide security for the content of
`
`those operations. See id. at 5:32-33.
`
`Pet. at 18. Petitioner does not show how either of these structures is clearly linked
`
`to the function of the “security means.” Even assuming that the function of the
`
`security means is “enabling one or more security operations to be performed on
`
`data,” the generic “structures” identified by Petitioner are not bona fide structures.
`
`
`
`4
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`The first alleged structure cannot be the required corresponding structure
`
`because the specification does not link “hardware, software and/or firmware” to
`
`the claimed security means. The sole reference to the language “hardware,
`
`software and/or firmware” in the specification is at 2:30-32, cited by Petitioner as a
`
`“see also,” which refers to a security device 203 in the prior art. Nothing in the
`
`specification indicates that the claimed security means is the security means in the
`
`prior art.
`
`Regardless, even if the term “hardware, software and/or firmware” at 2:30-
`
`32 were linked to the claimed security means, Petitioner has not met its burden
`
`because the cited portion of the specification fails to identify a specific hardware
`
`structure or, if the structure includes software or firmware as Petitioner contends, a
`
`software algorithm for performing the claimed function. See Williamson v. Citrix
`
`Online, LLC, 792 F.3d 1339, 1352 (Fed. Cir. 2015). The cited passage merely
`
`recites the function of the “hardware, software and/or firmware” without
`
`identifying structure: “The security device 203 includes appropriately configured
`
`hardware, software and/or firmware which can be directed to perform one or more
`
`cryptographic operations.” Ex. 1001 at 2:30-32. Generic references to “hardware”
`
`or “software,” similar to the “module” in Williamson, are insufficient to identify
`
`
`
`5
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`corresponding structure for a mean-plus-function claim term in the absence of an
`
`algorithm. Williamson, 792 F.3d at 1350.
`
`The remaining cited portions of the specification do not cure this defect.
`
`The passage at 12:10-16 refers to a “peripheral device” that performs encryption
`
`and decryption without identifying the structure of the device. The passage at
`
`17:52-67 refers to the “security functionality of a peripheral device,” but also fails
`
`to identify a structure. Finally, the passage at 15:63-67 refers to a “cryptographic
`
`processing device 801” that Petitioner does not contend is a corresponding
`
`structure. Ex. 1001 at 15:64-67. Thus, Petitioner has not met its burden to show
`
`that “hardware, software, and/or firmware” is a proper corresponding structure to
`
`meet the requirements of 35 U.S.C. § 112(6). Williamson, 792 F.3d at 1352.
`
`The second alleged structure, “[a] device that performs security operations
`
`and that includes one or more mechanisms to provide security for the content of
`
`those operations,” is similarly defective. This alleged structure replaces the
`
`“security means” in the claim with a nonce term, “device,” that is not the name of a
`
`structure, Williamson, 792 F.3d at 1350, and then reiterates the function of the
`
`“security means” albeit with different words.
`
`
`
`6
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`While Patent Owner believes that the specification discloses sufficient
`
`structure to render the “security means” definite, it is the Petitioner’s burden, and
`
`not the Patent Owner’s burden, to identify the claimed function and cite the
`
`appropriate corresponding structure. 37 C.F.R. § 42.104(b)(3). Because Petitioner
`
`has failed to properly construe “security means,” the Petition cannot properly
`
`identify how the prior art renders the claims unpatentable. The Petition should be
`
`denied on all grounds with respect to Claims 1 through 37.
`
`III. PETITIONER HAS NOT DEMONSTRATED A REASONABLE
`LIKELIHOOD OF SUCCESS FOR THE GROUNDS
`ADVANCED IN THE PETITION, AND THE PETITION
`SHOULD BE DENIED.
`
`A. Requirements for Showing Anticipation Under 35 U.S.C.
`§ 102 and Obviousness Under 35 U.S.C. § 103.
`
`A reference cannot anticipate a claim unless each and every element as set
`
`forth in the claim is found in that reference. See, e.g., Verdegaal Bros., Inc. v.
`
`Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Moreover, the elements
`
`in the reference must be arranged as required by the claim. Net MoneyIN, Inc. v.
`
`VeriSign, Inc., 545 F.3d 1359, 1371-72 (Fed. Cir. 2008).
`
`To establish the presence of a means-plus-function limitation in the prior art,
`
`the challenger must show that the structure corresponding to the claimed function,
`
`or an equivalent, is present in the prior art. Fresenius USA, Inc. v. Baxter Int’l,
`
`
`
`7
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Inc., 582 F.3d 1288, 1299 (Fed. Cir. 2009). “To anticipate a claim reciting a
`
`means-plus-function limitation, the anticipatory reference must disclose the recited
`
`function identically.” Transclean Corp. v. Bridgewood Servs., Inc., 290 F.3d 1364,
`
`1372 (Fed. Cir. 2002).
`
`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) where in evidence, so-called secondary considerations.
`
`Graham, 383 U.S. 1, at 17–18. The Board has held that a failure to identify the
`
`differences between the claimed subject matter and the prior art is fatal to an
`
`obviousness challenge. See, Apple, Inc. v. Contentguard Holdings, Inc., IPR2015-
`
`00355, Decision Denying Institution of Inter Partes Review, Paper 9 at 9-10
`
`(PTAB June 26, 2015) (denying institution for failure to identify the differences
`
`between the claimed subject matter and the prior art).
`
`This Petition is deficient because it fails to meet the fundamental
`
`requirements for demonstrating invalidity. The Petitioner was required to “specify
`
`where each element of the claim is found in the prior art patents or printed
`
`
`
`8
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`publications relied upon.” 37 C.F.R. § 42.104(b)(4). As set forth below, Petitioner
`
`failed to meet this burden.
`
`B. Ground I: Claims 1, 2, 6, 7, 11-13, 23-26, and 36-39 Are Not
`Anticipated by Jones
`
`Petitioner failed to meet its burden with respect to Ground I because
`
`Petitioner (1) did not identify the corresponding structure for the “security means,”
`
`and, therefore, failed to show where that structure is disclosed in Jones; (2) failed
`
`to show that the claimed “means for operably connecting” is disclosed in Jones;
`
`(3) failed to show that the “means for mediating communications” is found in
`
`Jones; and (4) failed to show that Claims 38 and 39 are anticipated by Jones.
`
`1.
`
`Petitioner Failed to Show that the Claimed “Security
`Means” Is Disclosed in Jones
`
`Independent claims 1, 6, 11, 23, 24, 36, and 37 of the ʼ802 Patent recite a
`
`“security means” and dependent claims 2, 7, 12, 13, 24, and 25 include this
`
`limitation via dependence. As set forth above, Petitioner failed to identify the
`
`corresponding structure for the “security means” disclosed in the specification.
`
`Because the Board’s rules require that the Petitioner “must specify where each
`
`element of the claim is found in the prior art patents or printed publications relied
`
`upon,” 37 C.F.R. 42.104(b)(4), and the controlling Federal Circuit case law
`
`requires that “a challenger who seeks to demonstrate that a means-plus-function
`
`
`
`9
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`limitation was present in the prior art must prove that the corresponding
`
`structure—or an equivalent—was present in the prior art,” Fresenius USA, 582
`
`F.3d at 1299, Ground I is deficient with respect to Claims 1, 2, 6, 7, 11-13, 23-26,
`
`and 36-37 and should be denied as to those claims.
`
`2.
`
`Petitioner Failed to Show that the Claimed “Means for
`Operably Connecting” Is Disclosed in Jones
`
`The Petition is deficient because the Petitioner fails to accurately disclose
`
`the statutory grounds for its arguments. A petition is required to “identif[y], in
`
`writing and with particularity, each claim challenged, the grounds on which the
`
`challenge to each claim is based, and the evidence that supports the grounds for the
`
`challenge to each claim.” 35 U.S.C. § 312(a)(3). The Petition must provide a
`
`statement of “[t]he specific statutory grounds under 35 U.S.C. 102 or 103 on which
`
`the challenge to the claim is based and the patents or printed publications relied
`
`upon for each ground.” 37 C.F.R. § 42.104(b)(2). The Petition also must identify
`
`“[h]ow the construed claim is unpatentable under the statutory grounds identified
`
`in paragraph (b)(2).” 37 C.F.R. § 42.104(b)(4).
`
`Independent claims 1 and 6 recite a “means for operably connecting the
`
`security means and/or the target means to the host computing device in response to
`
`an instruction from the host computing device.” Petitioner argues that Jones
`
`
`
`10
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`discloses this claim element because “Jones uses the PCMCIA interface standard
`
`and the related standard software device driver for implementing that interface
`
`standard in communicating between the secure memory card and host computer of
`
`Jones.” Pet. at 27. Petitioner also contends that Jones discloses that the secure
`
`memory card “stores information to help the host computer and secure memory
`
`card of Jones to establish an appropriate communications interface using ‘suitable
`
`driver software which executes on the host computer.’” Pet. at 27-28. Petitioner
`
`does not, however, argue that Jones discloses that the operable connection of the
`
`host computer to the security means and/or target means occurs “in response to an
`
`instruction from the host computing device” as required in the claimed function.
`
`In an admission that Jones does not disclose this aspect of the claimed
`
`function, Petitioner argues that a person of ordinary skill in the art would have
`
`known that a plug-and-play feature “ubiquitous” among PCMCIA standard devices
`
`“involves the suitable software drivers being provided to the host computer in
`
`response to an instruction to do so by the host computer.” Pet. at 28. In other
`
`words, Petitioner admits that Jones does not disclose that the software drivers are
`
`provided to the host computer “in response to an instruction from the host
`
`computing device,” but that this limitation is either supplied by the PCMCIA
`
`
`
`11
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`standard or is at least common in PCMCIA standard devices. This is an
`
`obviousness, not anticipation, argument. See Transclean Corp., 290 F.3d at 1372
`
`(a claimed function must be disclosed identically in the cited reference to be
`
`anticipated).
`
`By cloaking its obviousness argument as an anticipation argument,
`
`Petitioner has submitted a deficient Petition, and Ground I of the Petition should be
`
`denied as to Claims 1, 2, 6, and 7.
`
`3.
`
`Petitioner Failed to Show that the Claimed “Means for
`Mediating Communications . . . so that the Communicated
`Data Must First Pass through the Security Means” Is
`Disclosed in Jones
`
`Independent claims 1, 11, 23, and 36 recite a “means for mediating
`
`communication of data between the host computing device and the target means so
`
`that the communicated data must first pass through the security means.” Petitioner
`
`proposed to construe this term to include the corresponding structure described in
`
`the specification: an interface control device, including a conventional field
`
`programmable gate array (FPGA),” citing Ex. 1001 at 16:40-56 and, also, 13:5–26.
`
`
`
`12
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Pet. at 212. Petitioner then argues that the “means for mediating communication”
`
`is disclosed by the gate 178 of Jones. Pet. at 29, 32.
`
`Petitioner’s argument that the gate 178 of Jones performs the same function
`
`as the interface control device disclosed in the ’802 Patent at 16:40-56, and has the
`
`same or equivalent structure as the interface control device, should be rejected.
`
`The interface control device 802, depicted in Figure 8, “enables the in-line
`
`cryptography aspect of the invention, since the interface control device 802
`
`controls the flow of data between the host computing device and the target
`
`functionality 807.” Ex. 1001 at 16:52-56. Figure 9A illustrates the flow of data
`
`through the interface control device 802. Ex. 1001 at 16:57-58.
`
`
`
`2 Patent Owner does not agree that Petitioner’s proposed construction is correct.
`
`
`
`
`
`13
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`As shown, in embodiments where data from the host computing device is
`
`processed by the cryptographic processing device and passed to the target device,
`
`the interface control device 802 mediates the communication of data by causing
`
`data to flow from the host interface 806 to the cryptographic processing device
`
`interface 808 prior to being sent to the target functionality interface 807. Ex. 1001
`
`at 16:57-17:6.
`
`Petitioner has failed to meet its burden to “specify where each element of the
`
`claim is found in the prior art patents or printed publications relied upon” as
`
`required by 37 C.F.R. § 42.104(b)(4) because Petitioner does not argue that gate
`
`178 performs the claimed function of “mediating communication of data between
`
`the host computing device and the target means so that the communicated data
`
`must first pass through the security means.” Instead, Petitioner states this
`
`limitation is met because “[d]ata from the host computing device must first pass
`
`through the gate before it can make its way to the common memory array,” Pet. at
`
`29, but Petitioner does not contend that the gate 178 mediates this communication
`
`“so that the communicated data must first pass through the security means” as
`
`required by the claim limitation. Thus, Petitioner has failed to meet its burden of
`
`showing how this element of the claim is met by the gate 178.
`
`
`
`14
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Petitioner could not argue that gate 178 performs this function because gate
`
`178 has no role in passing data first through the alleged security means of Jones,
`
`which Petitioner identifies as the encryption-decryption unit 177. As is apparent
`
`from Figure 1 of Jones reproduced below, the communication of data from the host
`
`computer 110 to the encryption-decryption unit 177 could not be mediated by gate
`
`178 because the gate is not interposed between the host computer and encryption-
`
`decryption unit. Ex. 1003, Fig. 1. Thus, gate 178 does not mediate
`
`communications so that the data must first pass through the encryption-decryption
`
`unit 177.
`
`
`
`15
`
`
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Additionally, even if the gate 178 performed the function of a “means for
`
`mediating communication,” Petitioner has not shown that the gate 178 has the
`
`same or equivalent structure as the interface control device that Petitioner asserts is
`
`the corresponding structure. As the Federal Circuit has stated:
`
`It is firmly established in our precedent that a structural analysis
`
`is required when means-plus-function limitations are at issue; a
`
`functional analysis alone will not suffice. . . . Just as a patentee
`
`who seeks to prove infringement must provide a structural
`
`analysis by demonstrating that the accused device has the
`
`identified corresponding structure or an equivalent structure, a
`
`challenger who seeks to demonstrate that a means-plus-function
`
`limitation was present in the prior art must prove that the
`
`corresponding structure—or an equivalent—was present in the
`
`prior art.
`
`Fresenius USA, Inc., 582 F.3d at 1299 (citations omitted).
`
`Petitioner did not perform a structural analysis in the Petition. Petitioner
`
`simply states, without explanation, that the gate in Jones is an interface control
`
`device without comparing the structure of the gate to the structure of the interface
`
`
`
`16
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`control device. Pet. at 29. It is evident from the disclosure of the ’802 Patent that
`
`an interface control device must be more than a simple gate. Moreover, an FPGA
`
`includes, among other things, an array of gates, which is much more than a single
`
`gate. Petitioner’s purely functional analysis is insufficient under the controlling
`
`law. Accordingly, Ground I is deficient with respect to Claims 1, 2, 11-13, 23, and
`
`36 and should be denied.
`
`4.
`
`Petitioner Failed to Show that Claims 38 and 39 Are
`Anticipated by Jones
`
`Petitioner states that Claims 38 and 39 are invalid for the same reasons as
`
`independent Claims 1, 6, 11, 23, 24, 36, and 37 because Claims 38 and 39 “do not
`
`provide patentably distinguishing claim elements.” Pet. at 32-33. Petitioner
`
`assumes that the Board will reach the same conclusion as the Examiner did
`
`concerning the scope of the claims (while arriving at a different conclusion
`
`regarding patentability) without any articulated reasoning or analysis. In so doing,
`
`Petitioner fails to fulfill its obligation to “specify where each element of the claim
`
`is found in the prior art patents or printed publications relied upon,” 37 C.F.R.
`
`42.104(b)(4). For this reason, Ground I should be denied as to Claims 38 and 39.
`
`In any event, if Petitioner is correct that Claims 38 and 39 are of the same
`
`scope as Claims 1 and 11, then for the same reasons as set forth above, Petitioner
`
`
`
`17
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`has failed to demonstrate that Claims 38 and 39 are anticipated by Jones for at least
`
`the reasons set forth above.
`
`C. Ground II: Claims 5, 10, 14, 22, 27, and 35 Are Not Obvious
`over Jones in View of Harari
`
`Ground II should be denied because Harari is cited to address solely
`
`dependent claims and does not cure the defects in Petitioner’s arguments set forth
`
`above in Section III.B. Since all of the claims of Ground II depend from claims
`
`that Petitioner has not shown are anticipated by Jones in Ground I, and Harari does
`
`not supply the missing limitations, Ground II should not be instituted.
`
`D. Ground III: Claims 1-39 Are Not Obvious Over Clark in
`View of USB Specification
`
`Ground III should not be instituted because Petitioner (1) did not identify the
`
`corresponding structure for the “security means” and, therefore, failed to show
`
`where that structure is disclosed in Clark; (2) failed to identify where the “target
`
`means” is found in Clark; (3) failed to show that the “means for mediating
`
`communications” is found in Clark; and (4) failed to show that Claims 38 and 39
`
`are obvious over Clark in view of the USB Specification.
`
`
`
`18
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`1.
`
`Petitioner Failed to Show that the Claimed “Security
`Means” Is Obvious Over Clark in View of the USB
`Specification
`
`As set forth above, independent Claims 1, 6, 11, 23, 24, 36, and 37 of the
`
`ʼ802 Patent recite a “security means,” but Petitioner failed to identify the
`
`corresponding structure for the “security means” disclosed in the specification of
`
`the ’802 Patent. See supra, § II.A. Therefore, as discussed with respect to
`
`Ground I, Petitioner has failed to meet its burden to “specify where each element
`
`of the claim is found in the prior art patents or printed publications relied upon,”
`
`37 C.F.R. 42.104(b)(4), because Petitioner has not shown where the unidentified
`
`corresponding structure for the “security means” is disclosed in Clark (and does
`
`not contend that it is disclosed in the USB Specification). Pet. at 43; supra,
`
`§ III.B.1. Accordingly, Ground III is deficient with respect to Claims 1-37 and
`
`should be denied.
`
`2.
`
`Petitioner Failed to Identify Where the “Target Means” Is
`Found in Clark or the USB Specification
`
`Petitioner has failed to meet its burden to “specify where each element of the
`
`claim is found in the prior art patents or printed publications relied upon” as
`
`required by 37 C.F.R. § 42.104(b)(4) because Petitioner did not identify where the
`
`“target means” is found in Clark. Petitioner states that the “[a]cquisition input unit
`
`
`
`19
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`of the Clark encryption module can take many forms,” and that Clark’s encryption
`
`module can include “virtually any source” for providing confidential data to be
`
`encrypted. Pet. at 43-44. However, Petitioner never explicitly states that any
`
`specific structure in Clark is the claimed “target means,” and Petitioner does not
`
`contend that the “target means” is disclosed in the USB Specification.
`
`Accordingly, Ground III is deficient with respect to Claims 1-37 and should be
`
`denied.
`
`3.
`
`Petitioner Failed to Show that the Corresponding Structure
`for the Claimed “Means for Mediating Communications” Is
`Disclosed in Clark or the USB Specification
`
`Similar to its argument with respect to Jones in Ground I, Petitioner argues
`
`that the “means for mediating communication of data between the host computing
`
`device and the target means so that the communicated data must first pass through
`
`the security means” is the switch 3912 of Clark3. Petitioner argues that switch
`
`3912 mediates the communication between the acquisition input 3904 and the PC
`
`via communication links 3926-3932 so that the data must pass through the
`
`encryption engine 3924. Pet. at 49.
`
`
`
`3 Petitioner does not contend that the USB Specification discloses this limitation.
`
`
`
`20
`
`

`

`
`
`
`
`IPR2017-00430
`U.S. Patent No. 6,088,802
`
`Even assuming that the switch performs the claimed function, the Petition is
`
`deficient because Petitioner has not sh

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