throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`
`
`ORACLE CORPORATION, NETAPP INC. and
`HUAWEI TECHNOLOGIES CO., LTD.,
`Petitioners,
`v.
`CROSSROADS SYSTEMS, INC.
`Patent Owner.
`____________
`Case IPR2014-01207
`Patent No. 7,051,147
`____________
`
`
`
`PATENT OWNER’S MOTION TO EXCLUDE EVIDENCE
`CITED BY PETITIONERS
`
`
`
`

`
`
`
`Patent Owner respectfully requests that certain evidence relied on by Petitioners
`
`be excluded pursuant to 37 C.F.R. § 42.64(c). Patent Owner objected to various
`
`exhibits on either February 17, 2015 (Attachment A), February 18, 2015 (Attachment
`
`B) or August 28, 2015 (Paper 47). Patent Owner’s objections to deposition testimony
`
`were made in the record during deposition. In addition or in the alternative, because
`
`Petitioners repeatedly mischaracterize the deposition testimony of Patent Owner’s
`
`expert Dr. Levy and declarant John Middleton, Patent Owner further requests that the
`
`Board consider additional portions of these deponents’ testimony pursuant to the Rule
`
`of Completeness (FRE 106).
`
`I. PETITIONERS MISCHARACTERIZE THE TESTIMONY OF
`DR. LEVY
`Petitioners rely on certain testimony by Dr. John Levy, Ph.D., Patent Owner’s
`
`expert, which should be excluded because it was obtained pursuant to objectionable
`
`questioning and/or mischaracterizes his testimony.
`A. Objection #1
`Petitioners cite Ex.1218 at 56:19-57:24 for the proposition that “a host channel
`
`ID (a Fibre Channel ID in the CRD combined system) is sufficient to identify the host
`
`device within the meaning of the claims of the ‘147 patent where there is only a single
`
`host on each host or fibre channel.” Paper 45 (“Reply”) at 3. The subject testimony is
`
`as follows:
`
`Q. So my question was directed to the device, not the storage
`address or partition within the storage device. . . . So my question is,
`
`
`
`
`
`1
`
`

`
`
`
`where there is only a single SCSI bus attached to the storage router, is
`the SCSI ID sufficient to identify the storage device within the
`meaning of the claims of the '147 patent?
`MR. HALL: Objection; form.
`A. And so you mean to identify the device in the map, the claim
`map?
`Q. Correct.
`A. Well, given that an entire storage device is what needs to be
`represented in the map and that there is only one SCSI bus and that
`SCSI IDs are unique on that SCSI bus, which they must be, then in
`that case a SCSI ID could be sufficient to identify the mapped storage.
`Q. Okay. So let's discuss the parallel concept on the fibre channel
`side. In the circumstance where there is only a single host device
`on a fibre channel, is the fibre channel ID sufficient to identify the
`host device?
`MR. HALL: Objection; form.
`* * *
`A. Well, on the host side of the map, all that's required in the map
`is an identifier sufficient to distinguish between multiple hosts on the
`first transport medium. So a fibre channel ID of some kind would be
`one example of something that could distinguish between such hosts.
`
`Ex. 1218, 56:14-57:24 (emphasis added). Patent Owner’s counsel’s form objection is
`
`included above; as Petitioners’ changing interpretations of the phrase demonstrate, the
`
`use of “fibre channel ID” is vague. The term appears nowhere in the record but here
`
`and Petitioners’ reply; it does not appear to have been used in the Petition or
`
`supporting declaration.
`
`
`
`
`
`2
`
`

`
`
`
`Petitioners first indicated that “fibre channel ID” was an analog to “SCSI ID.”
`
`Earlier in the deposition, SCSI ID was used to refer to the ID of a device on a SCSI
`
`bus (e.g., the SCSI ID of a storage device) used to distinguish the device from other
`
`devices on the SCSI bus, as opposed to identifying the bus itself.
`
`A. . . . . Well, let's see. We -- I need to clarify what is meant by
`"the SCSI IDs of the storage devices." Are we talking about the -- the
`SCSI ID on the SCSI bus of the storage -- storage devices? Is that
`correct?
`Q. Correct. It's the same SCSI ID, I believe, that you testified about
`in your previous deposition.
`A. Well, we had a lot of testimony about SCSI IDs on a SCSI bus,
`yes. Right.
`Q. And I'm using the term "SCSI ID" in that same sense.
`
`Ex 1218, 54:5-16. See also, Ex. 1232 at 127:14-20 (A. . . . “there can’t be more than
`
`one host with the same SCSI ID on a SCSI bus. Therefore, the SCSI ID is, in fact,
`
`adequate to distinguish a host on the SCSI bus.”)1
`
`After discussing SCSI IDs, Petitioners’ counsel stated “let’s discuss the parallel
`
`concept on the fibre channel side” indicating that “fibre channel ID” was somehow
`
`analogous to SCSI ID. See Ex. 1218 at 57:8-12. Clearly this is what Dr. Levy
`
`understood, testifying that “fibre channel ID” refers to an identifier that can be used to
`
`
`1 The parties agreed that this testimony could be cited in the present proceeding.
`
`Ex. 1218, 7:9-21.
`
`
`
`
`
`3
`
`

`
`
`
`distinguish between multiple hosts on the first transport medium. Id., 57:19-24.
`
`Petitioners’ reply appears to reinterpret “fibre channel ID” to refer to, or be
`
`analogous to, a “host channel ID”. Reply at 3 (referring to “a host channel ID (a Fibre
`
`Channel ID in the CRD combined system)”). To the extent Petitioners are attempting
`
`to conflate “fibre channel ID” as used in the cited question with the internal identity of
`
`a CRD-5500 host channel (i.e., the slot number), such an interpretation demonstrates
`
`the vagueness of the question and is, further, contrary to both Dr. Levy’s testimony in
`
`the cited passage (Ex. 2018, 57:19-22) and Petitioners’ explicit acknowledgement that
`
`a fibre channel ID refers to the ID of a host device, not a channel ID:
`
`Q. In the example where the control unit bridges between a fibre
`channel device interface and a SCSI disk, the fibre channel would
`output its own ID, in particular an FC ID. Is that right?
`A. I think you probably meant to say the fibre channel host. Is
`that correct?
`Q. (BY MR. GARDELLA) Yes.
`A. In the interactions between a host and a target on fibre channel,
`the host identifies both itself and the target in the frame.
`
`Ex 1218, 67:22-68:8 (emphasis added) (objection omitted). This cited passage shows
`
`that fibre channels per se do not have identifiers, and counsel agreed. Petitioners’
`
`shifting interpretations of “fibre channel ID” show the ambiguity of the term. Because
`
`Ex. 1218, 56:19-57:24 is vague and ambiguous and is being mischaracterized in a
`
`prejudicial manner contrary to the record, it should be excluded under FRE 403.
`
`
`
`
`
`Petitioners’ attempt to use Dr. Levy’s testimony on “fibre channel ID” to
`
`
`4
`
`

`
`
`
`support that a “host channel ID in the CRD-5500” identifies a host is directly contrary
`
`to Dr. Levy’s testimony on the channel IDs of the CRD-5500. For example, in his
`
`earlier deposition, Dr. Levy testified that a channel identification in a CRD-5500 is
`
`not a host identification:
`
`Q. Okay. Now, why is it relevant that the swapping of cables
`caused the storage accessible by a host to change? What bearing
`does that have on the mapping limitation?
`A. Well, because Dr. Hospodor seems to be claiming --
`asserting that channel identification is the same as a host
`identification. And, yet, that's not true because the -- the only
`mapping performed by a CRD-5500 is [channel to] storage, not
`[host to] storage. In fact, any host and every host connected to a
`single channel has access to exactly the same storage.
`
`Ex. 1232 at 126:8-19 (emphasis added).
`
`If the cited testimony is not excluded, Patent Owner requests that, pursuant to
`
`FRE 106, the Board consider the record as a whole and in particular the additional
`
`testimony of Dr. Levy at Ex. 1218, 54:5-16, 67:22-68:8, discussed above, 94:15-22
`
`(“Well, I don’t agree in the sense that the host interface ID only identifies the host
`
`interface and not the host”), 93:9-15 (“[T]he interface identifier only identifies the
`
`interface.”), and 92:14-20 (“[T]he host interface ID does not identify the host”); and
`
`Ex. 1232 at 126:8-19, 127:14-20.
`
`
`
`5
`
`
`
`
`
`

`
`
`
`B. Objection #2
`Petitioners cite Ex. 1218 at 93:20-96:4 for the proposition that Bergsten
`
`“sufficiently identifies host devices because there is only a single host device attached
`
`to each ‘host interface,’” which, according to Petitioners, Dr. Levy allegedly
`
`conceded. Reply at 18-19. The cited passage, however, includes multiple
`
`objectionable questions, which objections were made on the record:
`
`Q. So in this particular use case or embodiment, I believe we're in
`agreement that there is a single host attached to each host interface
`within each storage controller. Is that correct?
`A. Yes.
`Q. So in that circumstance, identifying a host interface is
`sufficient to identify for routing purposes a particular host?
`MR. HALL: Objection; form.
`Q. (BY MR. GARDELLA) Do you agree with that?
`A. I'm thinking about it.
`MR. HALL: Same objection.
`A. I'm just trying to understand what "for routing purposes"
`means in that context. It's certainly clear that knowing the interface
`through which a command is received does tell the controller which
`interface to send a response to that command back on, and if there is
`only one host on that interface, then that would be sent to the
`appropriate host.
`Q. (BY MR. GARDELLA) So is your answer that in this use
`case, identifying host interface is sufficient to identify the single host
`that is attached to the host interface?
`MR. HALL: Objection; form.
`
`
`
`
`
`6
`
`

`
`
`
`A. Well, I don't agree in the sense that the host interface ID only
`identifies the host interface and not the host.
`Q. (BY MR. GARDELLA) Given that there is only a single host
`identified to each host interface, why, again, for routing purposes, is
`it not sufficient to identify the host interface?
`A. Well, if by "routing purposes" you mean to be sure that the
`response to a command goes back to the correct host, then
`responding on this correct interface would be responding to the
`correct host.
`Q. Okay. So in that context and for that purpose, it would be
`sufficient to identify the host interface?
`A. Well --
`MR. HALL: Objection; form.
`A. -- I still disagree with identifying the host because it doesn't
`actually identify the host.
`Q. (BY MR. GARDELLA) But you would agree that the host
`interface ID is sufficient to ensure in this embodiment that
`transmissions are sent to the proper hosts?
`MR. HALL: Objection; form.
`A. Well, as in the CRD-5500 where there is a channel identifier,
`this interface ID does get the response sent back on the proper
`interface. And when there's only a single host present, that would be
`the host that is indicated.
`Q. (BY MR. GARDELLA) So is your answer, yes, in this use
`case or embodiment, identifying the host interface is sufficient to
`ensure that the host gets the appropriate message transmissions?
`MR. HALL: Objection; asked and answered.
`A. I guess so.
`
`
`
`
`
`7
`
`

`
`
`
`Ex. 1218 at 93:20-96:4. Patent Owner objected to the questions referenced above
`
`because, inter alia, “routing purposes” was vague and confusing. Dr. Levy, himself,
`
`expressed confusion at the use of this phrase. Id. at 94:8-9. Thus, the testimony cited
`
`by Petitioners at 93:25-94:14 should be excluded under FRE 403.
`
`Petitioners’ subsequent characterization of Dr. Levy’s testimony in response to
`
`these questions establishes the vagueness of “routing purposes.” Specifically, Dr.
`
`Levy discussed routing messages to the proper interface, which does not require
`
`identifying what may be attached to that interface. However, Petitioners use this
`
`testimony to allege that Levy conceded that, in a single host embodiment, the interface
`
`ID is sufficient to identify a host, despite Dr. Levy’s clear testimony—within the
`
`quoted passage—that the host interface does not identify the host. Id. at 94:20-22,
`
`95:11-12. Moreover, the vagueness of the questions is illustrated by the fact that the
`
`entire quoted passage was in the context of the Bergsten reference. Petitioners’ reply
`
`appears to characterize Dr. Levy’s testimony as relating to the claimed invention;
`
`however, Dr. Levy was testifying regarding the “routing purposes” of Bergsten. Thus,
`
`the question is vague to the extent that “for routing purposes” has some significance
`
`beyond merely the Bergsten reference. For the above reasons, the testimony at 93:25-
`
`94:14 cited by Petitioners should be excluded.
`
`Furthermore, Petitioners’ question at 95:13-16 is also vague and ambiguous. It
`
`is unclear what was meant by “the host interface ID is sufficient to ensure in this
`
`embodiment that transmissions are sent to the proper hosts” because, in the prior
`
`
`
`
`
`8
`
`

`
`
`
`examples there were not multiple hosts per host interface ID. See Ex. 1218, 93:20-24.
`
`In addition, it is not clear what “sufficient” means. Dr. Levy had just stated that “Well,
`
`as in the CRD-5500 there is a channel identifier, this interface identifier does get the
`
`response sent back on the proper interface.” Id. at 95:18-20. However, Dr. Levy
`
`makes clear in the rest of his testimony that he does not concede that the host interface
`
`ID is sufficient to identify a host. Id. at 94:20-22, 95:11-12.
`
`The final question in the cited passage is also vague and ambiguous because it
`
`is unclear what is meant by “in this use case or embodiment the host interface ID is
`
`sufficient . . . .” It is unclear whether the “use case or embodiment” is referring to the
`
`CRD-5500 just referenced or something else. Moreover, it unclear what is meant by
`
`“sufficient to ensure.” As Dr. Levy had just answered, the host interface ID would get
`
`the response back to the proper interface.
`
`Moreover, Petitioners mischaracterize Dr. Levy’s testimony. Dr. Levy had
`
`already been asked on multiple occasions variations of the question of whether the
`
`“interface ID” is sufficient to identify the host when there is a single host attached to
`
`an interface; Dr. Levy consistently answered that it was not. See e.g. Ex. 1218 at 92:8-
`
`20 (“[Dr. Levy]: In the examples . . . there is a single host connected to a particular
`
`interface. Q. And in that situation, the host interface ID is sufficient to uniquely
`
`identify the host. Correct? A. I don’t know because the host interface ID does not
`
`identify the host.”); see also id. at 93:9-15 (“Q. So in this embodiment, identifying the
`
`host interface identifies inferentially or implicitly the host. Correct? ... A. Well, as this
`
`
`
`
`
`9
`
`

`
`
`
`paragraph explains, because there can be multiple paths to the same host, the interface
`
`identifier only identifies the interface -- the interface.”); 94:15:22, 95:7-12.
`
`Furthermore, during redirect, Dr. Levy further described the use of host
`
`interface IDs (Ex. 1219, 205:2-206:15), explaining that the host interface ID only
`
`identifies the particular interface in the storage controller of Bergsten, not the SCSI ID
`
`of the host attached to the SCSI bus. See Ex. 1219 at 205:21-206:11 (“Q. So . . . you
`
`have the host with SCSI ID 7. I’d like you to assume an administrator or someone
`
`unplugs the host from the bus and attaches another host to the bus so that it’s using the
`
`same interface as the -- prior host. This host is using SCSI ID 6, a different SCSI ID.
`
`Would a request from the new host have the same host interface ID applied to it? A.
`
`The host interface ID is only identifying the particular attachment or interface or SCSI
`
`interface card, if you like, in the storage controller and not the host or host ID attached
`
`to somewhere else on the bus. And so it would have only the ID of the host interface,
`
`not the host itself.”) (objections omitted).
`
`Dr. Levy repeatedly explained that the host interface ID was not sufficient to
`
`identify a host, even in the situation in which only one host was attached to an
`
`interface. The fact that Dr. Levy finally gave a soundbite answer close enough for
`
`Petitioners to use (which still fails to actually state that the host interface ID is
`
`sufficient to identify the host), after multiple failed attempts by Petitioners to procure
`
`the desired response, does not reflect a change in Dr. Levy’s opinion. Rather, it shows
`
`that Petitioners are twisting the answers to their increasingly vague attempts to ask the
`
`
`
`
`
`10
`
`

`
`
`
`same question. Because Ex. 1218, 93:20-96:4 is vague and ambiguous and is being
`
`used in a prejudicial manner contrary to the record, it should be excluded under FRE
`
`403.
`
`If the cited testimony is not excluded, then Patent Owner requests that, pursuant
`
`to FRE 106, the Board consider the record as a whole and in particular, in light of Dr.
`
`Levy’s consistent testimony in the above cited passage that the host interface does not
`
`identify the host, the additional consistent testimony of Dr. Levy at Ex. 1218, 92:8-20,
`
`93:9-15 and Ex. 1219, 205:2-206:15.
`
`II. PETITIONERS MISCHARACTERIZE THE TESTIMONY OF
`JOHN MIDDLETON
`Petitioners mischaracterize the testimony of John Middleton via selective
`
`citation. First, Petitioners state that Middleton testified that he “knew of no technical
`
`obstacle that would have prevented development and testing of the access control
`
`feature on a testbed during the critical period.” Reply at 11-12 (citing Ex. 1220 at 54,
`
`58-59, 63-65). Patent Owner objected as to foundation (63:24-64:2) because
`
`Middleton explained that he was not capable of answering such questions as they
`
`relate to the software (i.e., access controls), because his expertise was in hardware. Ex.
`
`1220 at 46:14-47:14; 52:3-15, 53:12-20. Middleton further testified (on cross, re-
`
`direct, and re-cross) that Crossroads could not have tested access controls, under any
`
`conditions, until Verrazano was completed. Id. at 52:3-12, 106:13-107:15, 108:5-15,
`
`113:7-14, and 115:14-17 (“Q. (BY MR. GARDELLA) Could the access controls . . .
`
`have been simulated completely in software? A. Completely, no.”).
`
`
`
`
`11
`
`

`
`
`
`Petitioners also mischaracterize Middleton’s testimony (70:16-72:22) to the
`
`effect that Crossroads’ “could have built the access controls into the Verrazano/4100
`
`bridge but chose not to do so for business reasons, i.e., because incorporation of
`
`access controls would delay the commercial launch of the product.” Reply at 12-14.
`
`Patent Owner objected on the record because Middleton’s testimony was based purely
`
`on speculation; he merely agreed that certain of Petitioners’ theories were possibly
`
`true. Moreover, Petitioners’ theory overlooks Middleton’s additional testimony that
`
`the Verrazano bridge—without access controls—was sold as Crossroads 4100 bridge
`
`only after the critical period was over. Ex. 1220 at 71:9-12; Ex. 2305 ¶ 2; Ex. 2043
`
`¶ 3. If access controls would have delayed the commercial launch, it still would have
`
`occurred after the critical period ended. This testimony is thus irrelevant to diligence
`
`and should be excluded under FRE 401, 402.
`
`III. THE BOARD SHOULD EXCLUDE EXHIBITS 1224, 1225 AND 1226
`Exhibits 1224 and 1225 consist of a Crossroads’ preliminary infringement
`
`contentions and accompanying claims chart filed by Crossroads in prior litigation
`
`prior to discovery. Ex. 1224 at 1. Exhibit 1226 is a user guide for “Diligent
`
`Technologies ProtecTIER for REO 9500D.” Patent Owner timely objected. Paper 47.
`
`Exhibit 1224, the “Concise Statement of Infringement”, discusses the Overland REO
`
`9500D, but makes no reference to the ProtecTIER software from Diligent. See e.g.,
`
`Ex. 1225. Petitioners’ arguments characterize the infringement contentions without
`
`supporting evidence. Petitioners also provide no evidence that the accused Overland
`
`
`
`
`
`12
`
`

`
`
`
`9500D actually operated in the manner described in Ex. 1226. Exhibit 1226 should
`
`therefore be excluded as irrelevant under FRE 401, 402. As Ex. 1226 is the only
`
`proffered explanation for the relevance of Exhibits 1224 and 1225, they should also be
`
`excluded under FRE 401, 402.
`
`In regards to Ex. 1226, Petitioners also make the unsupported assertion that
`
`“‘the FC ports’ referenced in the infringement contentions correspond to each FC
`
`adapter card in the back of the Overland appliance.” Reply at 4 (citing Ex. 1226 at 7,
`
`16, 19, 47, 85, 106, 108). This is nothing more than attorney argument with no
`
`supporting evidence. None of the cited portions of Ex. 1226 reference an “FC adapter
`
`card.” Therefore, the cited portions are irrelevant to the reason for which they are
`
`being cited and should be excluded under FRE 401, 402.
`
`Petitioners argue that “the accused Overland system is identical to the proposed
`
`combination in that the mapping is between remote storage devices and an FC adapter
`
`card port or channel, which is in turn connected to a single host device.” Reply at 4-5.
`
`Again, Petitioners provide only attorney argument with no supporting evidence (e.g.,
`
`either in the manual or by someone with firsthand knowledge of how the Overland
`
`9500D itself operated). Moreover, in the configuration of the ProtectTIER device
`
`cited (Reply at 4), a single backup server connects to all ports and can access all of the
`
`LUNs. For the foregoing reasons, Ex. 1226 should be excluded as irrelevant under
`
`FRE 401, 402.
`
`Even if considered relevant, Exhibits 1224-26 should be excluded under FRE
`
`
`
`
`
`13
`
`

`
`
`
`403 because their probative value is substantially outweighed by a danger of unfair
`
`prejudice. Given that Petitioners waited until their reply to bring this argument and
`
`these exhibits, have brought forth no expert testimony to analyze them, and Patent
`
`Owner has no opportunity to respond with its own expert testimony, Petitioners’
`
`conclusory and one-sided analysis is unfairly prejudicial and misleads the Board.
`
`IV. THE BOARD SHOULD EXCLUDE EXHIBIT 1009
`Petitioners cite Crossroads’ preliminary infringement contentions (Ex. 1009)
`
`and rely on “Patent Owner’s assertion in litigation,” to argue that certain limitations
`
`fall under the broadest reasonable interpretation standard that is applied in PTAB
`
`proceedings. Pet. at 20-51 (passim). Patent Owner objected to Exhibit 1009.
`
`Attachs. A, B. It is improper to construe claims with respect to accused
`
`instrumentalities. NeoMagic Corp. v. Trident Microsystems, Inc., 287 F.3d 1062,
`
`1074 (Fed. Cir. 2002); see also E.I. du Pont de Nemours and Co. v. Monsanto Tech.
`
`LLC, IPR2014-00332, Paper 16 at 6-7 (PTAB July 11, 2014). Moreover, those
`
`contentions “[were] preliminary as Crossroads [had] received no discovery from
`
`Oracle.” Ex. 1009 at 2 n.2. “[P]reliminary infringement contentions are too tenuous to
`
`be relevant to the Board’s application of the broadest reasonable construction
`
`standard.” Mentor Graphics Corp. v. Synopsis, Inc., IPR2014-00287, Paper 17 at 3
`
`(PTAB Aug. 1, 2014). Accordingly, the Board should exclude Ex. 1009 as irrelevant.
`
`V. THE BOARD SHOULD EXCLUDE EXHIBIT 1008
`Petitioners rely on JP Patent Application Publication No. Hei 5[1993]-181609
`
`
`
`
`
`14
`
`

`
`
`
`to support one of their alleged grounds of unpatentability. Pet. at 5 (citing Ex. 1008).
`
`37 C.F.R. § 42.63(b) states that “[w]hen a party relies on a [foreign language]
`
`document . . ., a translation of the document into English and an affidavit attesting to
`
`the accuracy of the translation must be filed with the document.” (emphasis added).
`
`Patent Owner objected to Ex. 1008. Attachs. A, B. Because Ex. 1008, as filed with
`
`the Petition, did not contain an affidavit, it is not admissible and should be excluded.
`
`37 C.F.R. §§ 42.61(a), 42.63(b).
`
`On July 30, 2014, Petitioners filed, without authorization, a “substitute” exhibit
`
`1008 (“1008v2”). The certificate within Ex. 1008v2 was signed by Susan Andrus,
`
`marketing manager of TranslateMedia. Ex 1008v2 at 11. There is no evidence to
`
`suggest that Ms. Andrus could personally attest to the accuracy of the translation nor
`
`did she. Moreover, the certificate did not contain any perjury warning. Accordingly,
`
`the certificate is not an affidavit as required by 37 C.F.R. § 42.63(b). Because Ex.
`
`1008v2 was filed without authorization and is defective, it is not the operative exhibit
`
`in this proceeding and should be excluded or given zero weight.
`
`On March 6, 2015, Petitioners served a third version of Ex. 1008 (“1008v3”)
`
`containing a certificate of translation dated February 19, 2015. Rule 37 C.F.R. §
`
`42.63, however, “is unequivocal and requires . . . that a certificate of translation ‘must
`
`be filed with’ the Petition.” Zhongshan Broad Ocean Motor Co., Ltd. v. Nidec Motor
`
`Corp., IPR2014-01121, Paper 25 at 5 (PTAB Feb. 24, 2015). Therefore, even if filed,
`
`Ex. 1008v3 could not cure the defect in the original Ex. 1008. See, id.
`
`
`
`
`
`15
`
`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`SPRINKLE IP LAW GROUP
`
` John L. Adair /
`
` /
`
`John L. Adair
`Reg. No. 48,828
`Counsel for Patent Owner
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Dated: September 22, 2015
`
`
`
`
`
`1301 W. 25th Street
`Suite 408
`Austin, Texas 78705
`Tel. (512) 637-9220
`Fax. (512) 371-9088
`
`
`
`
`
`
`16
`
`

`
`ATTACHMENT
`
`ATTACHMENT
`A
`
`A
`
`
`
`

`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`ORACLE CORPORATION, NETAPP INC. and
`HUAWEI TECHNOLOGIES CO., LTD.
`Petitioner,
`
`v.
`
`CROSSROADS SYSTEMS, INC.
`Patent Owner
`
`____________
`
`
`Case IPR2014-01197
`Patent 6,425,035
`____________
`
`
`PATENT OWNER’S OBJECTIONS TO EVIDENCE SERVED IN
`PRELIMINARY PROCEEDING PURSUANT TO 37 CFR § 42.64(B)(1)
`
`
`
`
`
`

`
`
`
`Pursuant to 37 C.F.R. § 42.64, Patent Owners submit the following objections to
`
`certain evidence relied upon by Petitioner in the Petition.
`
`I.
`
`Objections to Exhibits Containing Grounds of Unpatentability
`Rejected by the Board
`
`Patent Owner objects to the following exhibits because they relate to or
`
`comprise grounds of unpatentability which were rejected by the Board and upon
`
`which trial was not instituted: 1003, 1004, 1006.
`
`II. Objections to Exhibits Never Cited or Explained in the Petition
`Patent Owner objects to those exhibits filed with the Petition that are not cited
`
`to in the Petition, and/or for which Petitioner fails to explain the relevance of the
`
`evidence to the challenge raised. Thus, they are irrelevant under FRE 401, 402, and
`
`37 CFR § 42.104(b)(5). Patent Owner specifically identifies the following exhibits:
`
`1011–1023, 1027–1031, and 1033.
`
`Furthermore, although Petitioner cites to Ex. 1009, Patent Owner objects to
`
`this Exhibit as irrelevant under FRE 401, as it is neither prior art nor does it contain
`
`any relevant admissions.
`
`III. Objections to Admissibility of Certain Dates
`Patent Owner objects to Exhibit 1003 and 1004 under FRE 401, 402, 802, and
`
`901. Specifically, the revision dates and copyright dates in each are not evidence
`
`that the document was revised or publically available on any particular date. The
`
`1
`
`

`
`
`
`apparent date contained in the URL of Exhibit 1004 is likewise inadmissible to show
`
`the date of public availability. These dates are also inadmissible hearsay regarding
`
`the date the documents were last revised or publically available, to the extent
`
`Petitioner relies on these dates to prove the date of last revision, public availability,
`
`or the like.
`
`IV. Objections to Lack of Authentication
`Petitioner has not produced evidence sufficient to authenticate the following
`
`exhibits under FRE 901: 1003, 1004, 1005, and 1027.
`
`Exhibit 1037, the declaration of Ms. Ullagaddi, is insufficient to authenticate
`
`the referenced exhibits because it is not based on personal knowledge. Exhibit 1037
`
`is itself objectionable under FRE 701, to the extent offered as lay testimony, because
`
`the testimony regarding the operation of the Internet Archive is outside the
`
`qualification of a lay witness. To the extent that Ms. Ullagaddi is offered as an expert
`
`witness, Ex. 1037 is objectionable under FRE 702 because she is not qualified as an
`
`expert on the Internet Archive or related technology.
`
`V. Objection to Form of Evidence Under 37 CFR § 42.63(b)
`Petitioner relies on Exhibit 1008, a Japanese language patent application and
`
`purported English translation, as a basis for at least one ground of unpatentability.
`
`Petitioner failed to file with the exhibit an affidavit attesting to the accuracy of the
`
`translation as required by 37 CFR § 42.63(b). Petitioner then filed, without
`
`2
`
`

`
`
`
`explanation and without permission from the Board, a “substitute” Exhibit 1008, one
`
`week later. Paper 5. Accordingly, Exhibit 1008 fails to comply with § 42.63(b) and
`
`should be excluded under 37 CFR. § 42.61(a). See Zhongshan Broad Ocean Motor
`
`Co. v. Nidec Motor Corp., IPR2013-01123 Paper 20 (PTAB Jan. 21, 2015).
`
`The improperly substituted Exhibit 1008 also fails to comply with the
`
`requirements of 37 CFR § 42.63(b), which requires an affidavit attesting to the
`
`accuracy of the translation. The translation company’s certification does not do so,
`
`but includes a statement from the company’s marketing manager (who is not the
`
`same person that translated the document and who provides no evidence that they
`
`are competent in the Japanese language) that “we” certify that the translation
`
`“conforms essentially to the original Japanese language.” It is not clear what
`
`“conforms essentially” means, but it does not state that the translation is accurate.
`
`Moreover, under 37 CFR § 42.2, an affidavit or declaration must meet the
`
`requirements of 37 CFR § 1.68, which requires the inclusion of certain language and
`
`requires signature under penalty of perjury. Accordingly, Patent Owner objects to
`
`the substituted Ex. 1008 for the foregoing reasons.
`
`VI. Hearsay Objections
`Patent Owner objects to the following exhibits as inadmissible hearsay under
`
`FRE 802, not within any exception: 1004 (statements regarding the design of the
`
`CRD-5500); 1027 (statements regarding the operation of the SP-8BFC); and 1028
`
`3
`
`

`
`
`
`(statements regarding the status of Fibre Channel). For example, Exhibit 1004
`
`includes the inadmissible hearsay statement by an unknown declarant that “CMD’s
`
`advanced ‘Viper’ RAID architecture and ASICs were designed to support
`
`tomorrow’s high speed serial interfaces.”
`
`VII. Objections to Exhibits 1010
`Patent Owner objects to the admissibility of all testimony in Exhibit 1010 that
`
`relies on inadmissible evidence as described above, including, for example, Exhibits
`
`1004, 1027, and 1028. Patent Owner further objects to certain testimony in Exhibit
`
`1010 for the following reasons:
`
`(1) The declarant’s opinion regarding the qualifications of one skilled in the
`
`art (¶¶ 14-15) lacks any explanation of the underlying facts or data on
`
`which the opinion is based and is thus entitled to no weight under 37 CFR
`
`§ 42.65(a). Moreover the testimony is inadmissible under FRE 702
`
`because it includes no explanation of the principles and methods applied,
`
`or the manner in which they were applied, to the facts of the case.
`
`(2) The following testimony fails to disclose the underlying facts or data on
`
`which the opinion is based as required by 37 CFR § 42.65:
`
`a. ¶ 22 (“these virtual local network storage regions are variously known
`
`in the art as virtual or logical partitions, virtual or logical disks, storage
`
`volumes or logical units”)
`
`4
`
`

`
`
`
`b. ¶ 23 (“[a] large number of prior-art systems . . . ”) (citing two examples)
`
`c. ¶ 24
`
`d. ¶ 27 (“storage access over Fibre Channel involves use of a ‘Native
`
`Low-Level Block Protocol”); additionally, ¶ 27 relies on Ex. 1009
`
`(itself irrelevant) as the basis for an opinion related to how the claim
`
`terms have been interpreted by Patent Owner in its infringement
`
`contentions, which is irrelevant under FRE 401 and 402;
`
`e. ¶ 96 (“the tree structure is beneficial only in enhancing performance
`
`when identifying alternate locations on alternate storage controllers . . .
`
`)”;
`
`f. ¶ 151 (this testimony is also objectionable under FRE 702 because it
`
`includes no explanation of the principles and methods applied, or the
`
`manner in which they were applied, to the facts of the case)
`
`(3) The following testimony is irrelevant as it not directed to any grounds upon
`
`which trial was requested and/or instituted: ¶¶ 24-25, 29-35, 39-89, 93-
`
`143, 198-200;
`
`(4) The following testimony is objected to under 37 CFR § 42.104 because the
`
`proffered opinion is based on prior art or publications which have not been
`
`instituted as grounds of unpatentability:

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