throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`In re Patent of: Baek et al.
`U.S. Patent No.: 6,978,346 Attorney Docket No.: 27450-0011IP1
`Issue Date:
`December 20, 2005
`Appl. Serial No.: 09/753,245
`Filing Date:
`December 29, 2000
`Title:
`APPARATUS FOR REDUNDANT INTERCONNECTION BETWEEN
`
`MULTIPLE HOSTS AND RAID
`
`Mail Stop Patent Board
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`CORRECTED PETITION FOR INTER PARTES REVIEW OF UNITED STATES PATENT
`NO. 6,978,346 PURSUANT TO 35 U.S.C. §§ 311-319, 37 C.F.R. § 42
`
`

`

`TABLE OF CONTENTS
`
`
`I.  MANDATORY NOTICES UNDER 37 C.F.R § 42.8 (a) (1) ..................................... 1 
`A.  Real Party-In-Interest Under 37 C.F.R. § 42.8 (b) (1) ......................................... 1 
`B.  Related Matters Under 37 C.F.R. § 42.8 (b) (2) ................................................ 1 
`C.  Lead and Back-Up Counsel Under 37 C.F.R. § 42.8 (b) (3)................................. 2 
`D.  Service Information ................................................................................... 2 
`II.  PAYMENT OF FEES UNDER 37 C.F.R. § 42.103 ............................................... 2 
`III.  REQUIREMENTS FOR IPR UNDER 37 C.F.R. § 42.104 ...................................... 2 
`A.  Grounds for Standing Under 37 C.F.R. § 42.104 .............................................. 2 
`B.  Challenge Under 37 C.F.R. § 42.104(b) and Relief Requested ............................ 3 
`C.  Claim Construction under 37 C.F.R. §§ 42.104(b)(3) ......................................... 4 
`1. 
`“RAID” (Claims 1-9) ................................................................................ 5 
`2. 
`“RAID controller/RAID controlling unit” (Claims 1-9) ....................................... 6 
`3. 
`“exchange/exchanges information” (Claims 1-9) ............................................ 6 
`4. 
`“connection unit” (Claims 1-9) ................................................................... 6 
`5. 
`“network interface controller,” “network controlling unit,” and “network interface
`controlling unit” (Claims 1-9) ........................................................................... 6 
`SUMMARY OF THE ’346 PATENT ............................................................... 7 
`IV. 
`A.  Brief Description ....................................................................................... 7 
`B.  Prosecution History ................................................................................... 8 
`V.  MANNER OF APPLYING CITED PRIOR ART TO EVERY CLAIM FOR WHICH AN
`IPR IS REQUESTED, THUS ESTABLISHING A REASONABLE LIKELIHOOD THAT AT
`LEAST ONE CLAIM OF THE ’346 PATENT IS UNPATENTABLE ............................... 9 
`A.  Brief Description of the References ............................................................... 9 
`i.  Mylex ..................................................................................................... 9 
`ii.  Hathorn ................................................................................................ 10 
`iii.  Deitz .................................................................................................... 10 
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`iv.  Griffith .................................................................................................. 11 
`v.  DeKoning .............................................................................................. 12 
`B.  Motivation to Combine ............................................................................. 13 
`[GROUND 1 and GROUND 2] – The Combination of Mylex and Hathorn Renders
`A. 
`Obvious Claims 1-9 ....................................................................................... 16 
`[GROUND 3] – The Combination of Deitz or Mylex with Griffith or DeKoning Renders
`B. 
`Obvious Claims 1-9 ....................................................................................... 41 
`VI.  CONCLUSION ....................................................................................... 58 
`CERTIFICATE OF SERVICE ............................................................................. 61 
`
`
`
`ii
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`
`EXHIBITS
`
`
`VMWARE-1001: U.S. Patent No. 6,978,346 to Baek et al., foreign application priority date
`9/19/2000 (“the ’346 patent”);
`
`VMWARE-1002: Excerpts from the Prosecution History of the ’346 Patent;
`
`VMWARE-1003: Expert Declaration of Dr. Robert Horst;
`
`VMWARE-1004: Dr. Robert Horst Curriculum Vitae;
`
`VMWARE-1005: U.S. Patent No. 5,574,950 to Hathorn et al., issued 11/12/1996
`(“Hathorn”);
`
`VMWARE-1006: Smith, Kevin J., “Storage Area Networks: Unclogging LANs and Improving
`Data Accessibility,” Mylex Corporation White Paper (published 5/29/1998) (“Mylex paper”);
`
`VMWARE-1007: U.S. Patent No. 6,401,170 to Griffith et al., filed on 8/18/1999 (“Griffith”);
`
`VMWARE-1008: U.S. Patent No. 6,578,158 to Deitz et al., filed on 10/28/1999 (“Deitz”);
`
`VMWARE-1009: Affidavit of Mr. Chris Butler, on behalf of Internet Archive;
`
`VMWARE-1010: U.S. Patent No. 6,073,218 to DeKoning et al., filed on 12/23/1996
`(“DeKoning”);
`
`VMWARE-1011: Clark, “Designing Storage Area Networks,” 1st Edition, Addison-Wesley
`Professional (1999);
`
`VMWARE-1012: Spainhower, “Design for Fault-Tolerance in System ES /9000 Model 900,”
`IEEE (1992);
`
`VMWARE-1013: IEEE 100: Authoritative Dictionary of IEEE Standards Terms, 7th Edition
`(2000); and
`
`VMWARE-1014: Siewiorek, D and Swarz R., “Reliable Computer Systems, Design and
`Evaluation,” Digital Press (1992).
`
`iii
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`VMware, Inc. (“Petitioner”) petitions for Inter Partes Review (“IPR”) under 35 U.S.C.
`
`§§ 311-319 and 37 C.F.R. § 42 of claims 1-9 (“the Challenged Claims”) of U.S. Patent No.
`
`6,978,346 (“the ’346 patent” or “the Baek patent”). As explained in this petition, there exists
`
`a reasonable likelihood that Petitioner will prevail with respect to each of the Challenged
`
`Claims.
`
`The Challenged Claims are unpatentable based on teachings set forth in at least the
`
`references presented in this petition. Petitioner respectfully submits that an IPR should be
`
`instituted, and that the Challenged Claims should be cancelled as unpatentable.
`
`I.
`
`MANDATORY NOTICES UNDER 37 C.F.R § 42.8 (a) (1)
`
`A.
`
`Real Party-In-Interest Under 37 C.F.R. § 42.8 (b) (1)
`
`Petitioner VMware, Inc. is the real party-in-interest.
`
`B.
`
`Related Matters Under 37 C.F.R. § 42.8 (b) (2)
`
`The ’346 patent is the subject of a number of civil actions in the District Court for
`
`Delaware: Civil Action Nos. 1-13-cv-01152; 1-13-cv-01151; 1-13-cv-01150; 1-13-cv-01088;
`
`1-13-cv-01089; 1-13-cv-01090; 1-13-cv-00928; 1-13-cv-00927; 1-13-cv-00931; 1-13-cv-
`
`00932; 1-13-cv-00930; 1-13-cv-00929; 1-13-cv-00926; 1-12-cv-01629; 1-12-cv-01625; 1-12-
`
`cv-01627; 1-12-cv-01624; 1-12-cv-01628; and 1-12-cv-01626.
`
`The ’346 patent is also the subject of Inter Partes Review No. IPR2013-00635 and
`
`petitions for Inter Partes Review Nos. IPR2014-00901 and IPR2014-00976.
`
`1
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`Lead and Back-Up Counsel Under 37 C.F.R. § 42.8 (b) (3)
`
`C.
`
`
`
`Petitioner provides the following designation of counsel.
`
`LEAD COUNSEL
`Katherine Kelly Lutton
`Reg. No. 46,333
`Fish & Richardson P.C.
`3200 RBC Plaza
`60 South Sixth Street
`Minneapolis, MN 55402
`T: 202-783-5070
`F: 202-783-2331
`
`
`D.
`
`Service Information
`
`BACK-UP COUNSEL
`Timothy W. Riffe
`Reg. No. 43,881
`Fish & Richardson P.C.
`3200 RBC Plaza
`60 South Sixth Street
`Minneapolis, MN 55402
`T: 202-783-5070
`F: 202-783-2331
`
`Please address all correspondence and service to counsel at the addresses
`
`provided in Section I(C) of this petition. Petitioner also consents to electronic service by
`
`email at IPR27450-0011IP1@fr.com.
`
`II.
`
`PAYMENT OF FEES UNDER 37 C.F.R. § 42.103
`
`Petitioner authorizes the Patent and Trademark Office to charge Deposit Account
`
`No. 06-1050 for the fee set forth in 37 C.F.R. § 42.15 (a) for this petition and further
`
`authorizes payment for any additional fees to be charged to this Deposit Account.
`
`III.
`
`REQUIREMENTS FOR IPR UNDER 37 C.F.R. § 42.104
`
`A.
`
`Grounds for Standing Under 37 C.F.R. § 42.104
`
`Petitioner certifies that the ’346 Patent is eligible for IPR. The present petition is
`
`being filed within one year of service of the complaint against Petitioner in the Delaware
`
`2
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`District Court Action.1 Petitioner is not barred or estopped from requesting this review
`
`challenging the Challenged Claims on the below-identified grounds.
`
`Challenge Under 37 C.F.R. § 42.104(b) and Relief Requested
`B.
`Petitioner requests an IPR of the Challenged Claims on the grounds set forth in the
`
`table shown below, and request that each of the Challenged Claims be found unpatentable.
`
`An explanation of how these claims are unpatentable under the statutory grounds identified
`
`below is provided in the form of a detailed description that indicates where each element
`
`can be found in the cited prior art, and the relevance of that prior art. Additional explanation
`
`and support for each ground of rejection is set forth in Exhibit VMWARE-1003, the
`
`Declaration of Dr. Robert Horst (“Horst Declaration”), referenced throughout this petition.
`
`Ground
`Ground 1
`
`’346 Patent Claims
`Claims 1-9
`
`Ground 2
`
`Ground 3
`
`Claims 1-9
`
`Claims 1-9
`
`Basis for Rejections
`Obvious under §103 based on Mylex in
`view of Hathorn
`Obvious under §103 based on Hathorn
`in view of Mylex
`Obvious under §103 based on Deitz or
`Mylex in view of Griffith or DeKoning
`
`
`On its face, the ’346 Patent claims priority to U.S. Patent Application. No.
`
`09/753,245, filed on 12/29/2000, and a Korean application filed on 9/19/2000.
`
`The Hathorn patent (Ex. 1005) issued on 11/12/1996 and thus qualifies as prior art
`
`under 35 U.S.C. §§ 102(a) and (b). The Mylex paper (Ex. 1006) was publicly distributed no
`
`1 The Complaint against Petitioner (Case No. 13-cv-00928) was served on June 4, 2013.
`
`3
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`later than 5/29/19982 and thus qualifies as prior art under 35 U.S.C. §§ 102(a) and (b).
`
`Therefore, both Hathorn and Mylex are printed publications that were publicly distributed
`
`more than one year before any of the applications to which the ’346 patent claims priority.
`
`The application that issued as the Griffith patent was filed on 8/18/1999, thus Griffith
`
`(Ex. 1007) qualifies as prior art under 35 U.S.C. § 102(e). The application that issued as the
`
`Dietz patent was filed on 10/28/1999, thus Deitz (Ex. 1008) qualifies as prior art under 35
`
`U.S.C. § 102(e). The application that issued as the DeKoning patent was filed on
`
`12/23/1996, thus DeKoning (Ex. 1010) qualifies as prior art under 35 U.S.C. § 102(e).
`
`Therefore, Griffith, Deitz, and DeKoning are patents that issued on respective applications
`
`filed before any of the applications to which the ’346 patent claims priority.
`
`C.
`
`Claim Construction under 37 C.F.R. §§ 42.104(b)(3)
`
`A claim subject to IPR is given its “broadest reasonable construction in light of the
`
`specification of the patent in which it appears.” 37 C.F.R. § 42.100(b). Thus, the words of
`
`the claim are given their plain meaning unless inconsistent with the specification. In re Zletz,
`
`893 F.2d 319, 321 (Fed. Cir. 1989). Petitioner submits, for purposes of the IPR only, that the
`
`claim terms are presumed to take on their broadest reasonable interpretation in view of the
`
`specification of the ’346 patent. In particular, Petitioner expressly reserves the right to
`
`submit constructions for individual claim terms in the matters now pending in the District of
`
`
`2 The Mylex paper was publicly available for download via www.mylex.com. (See Ex. 1009.)
`
`4
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`Delaware, under the legal standards applicable in those proceedings which are different
`
`than those proposed or adopted in this proceeding, including how a person of ordinary skill
`
`in the art would understand the claims in light of relevant intrinsic and extrinsic evidence.
`
`Under the law applicable to construction in IPR proceedings, the following claim
`
`terms should be construed applying the broadest reasonable interpretation to be broad
`
`enough to encompass the corresponding definition:
`
`Claim Term
`
`“RAID”
`“RAID controller/RAID controlling unit”
`
`“exchange/exchanges information”
`
`“connection unit”
`“network interface controller,” “network
`controlling unit,” and “network interface
`controlling unit”
`
`
`1.
`
`“RAID” (Claims 1-9)
`
`Broadest Reasonable Interpretation
`“redundant array of inexpensive disks”
`“a component that controls operation of the
`RAID”
`“to transmit and receive information
`reciprocally”
`“a hub or switch”
`“the part of a RAID controller that allows the
`RAID controller to communicate with the
`‘connection units’”
`
`Under the broadest reasonable interpretation in light of the specification, the term
`
`“RAID” should be construed as “at least a redundant array of independent disks.” “RAID” is
`
`understood by one of ordinary skill as an acronym for “redundant array of inexpensive
`
`disks.” (Ex. 1001 at Abstract; Ex. 1003, ¶¶ 14-16.)
`
`5
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`“RAID controller/RAID controlling unit” (Claims 1-9)
`
`2.
`
`Under the broadest reasonable interpretation in light of the specification, the phrases
`
`“RAID controller” and “RAID controlling unit” should both be construed as “a component that
`
`controls operation of the RAID.” (Ex. 1003, ¶¶ 14-16.)
`
`3.
`
`“exchange/exchanges information” (Claims 1-9)
`
`Under the broadest reasonable interpretation in light of the specification, the phrases
`
`“exchange information” and “exchanges information” should both be construed to mean “to
`
`transmit and receive information reciprocally.” (Ex. 1003, ¶¶ 14-16.)
`
`4.
`
` “connection unit” (Claims 1-9)
`
`Under the broadest reasonable interpretation in light of the specification, the phrase
`
`“connection unit” should be construed as “a hub or switch.” (Ex. 1003, ¶¶ 14-16.) This
`
`construction is supported by the specification, which uses the term hub to refer to a hub or
`
`switch. (Ex. 1001 at 3:13-18.)
`
`5.
`
`“network interface controller,” “network controlling unit,” and
`“network interface controlling unit” (Claims 1-9)
`Under the broadest reasonable interpretation in light of the specification, the phrases
`
`“network interface controller,” “network controlling unit,” and “network interface controlling
`
`unit” should be construed as “the part of a RAID controller that allows the RAID controller to
`
`communicate with the ‘connection units.’” (Ex. 1003, ¶¶ 14-16.)
`
`6
`
`

`

`
`
`SUMMARY OOF THE ’3446 PATENTT
`
`
`
`
`
`
`
`
`
`Atttorney Docket No.: 27450-00011IP1
`
`
`IPR of U.S. PPatent No. 6,9778,346
`
`IV.
`
`A.
`
`
`
`Brief Descriptioon
`
`
`
`
`
`
`
`
`
`S A T
`
`
`
`The ’346 pattent relates to a systemm with “redunndant intercconnections between
`
`
`
`
`
`
`
`multiple hosts and aa RAID.” Thee system includes two
`
`
`
`
`
`
`
`
`
`RAID contrrollers. Eachh RAID
`
`
`
`
`
`controlleer has two network interrface controollers (“NICss”). The systtem has twoo hub/switchh
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`devices. Fig. 4 illusttrates the syystem descrribed in the
`
`
`
`
`
`
`
`
`
`FFigure 4 is a block diagrram of a sysstem includi
`
`
`
`
`
`
`
`
`
`to host ccomputers 4400-405. (Id. at 2:64-3:66.) RAID 49
`
`
`
`
`
`
`
`
`
`’346 patentt:
`
`
`
`ng RAID 4990 and its innterconnecti
`
`
`
`on
`
`
`
`0 includes ttwo RAID coontrollers 4660
`
`
`
`
`
`
`
`and 461 and hubs 4440 and 441. (Id. at 3:10-18.) Eachh RAID conttroller includdes a pair off
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`or example
`network interface coontrollers. F
`
`
`
`
`, RAID conttroller 460 inncludes netwwork interfaace
`
`
`
`
`
`
`
`
`
`
`
`controlleers 470 and 471, and R
`
`
`
`AID control
`
`
`ler 461 incluudes netwo
`
`7
`
`
`
`rk interface controllers 480
`
`
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`and 481. (Id. at 3:11-13.) Each host computer has its own network interface controller (410
`
`to 415), which connects the host computer through the hubs to the network interface
`
`controllers (470, 471, 480, 481) of RAID controllers 460 and 461. (Id. at 3:31-35.)
`
`This structure provides a “communication passage between two RAID controllers.”
`
`(Id. at 3:64-65.) For example, RAID controller 460 can send data to RAID controller 461 via
`
`NIC 470, switch/hub 440, and NIC 480. (Id. at 3:66-4:12.)
`
`This redundant system of RAID controllers and network interface controllers purports
`
`to provide a “fault tolerant function.” (Id. at 3:63-66.) A RAID controller “having [an] error
`
`occurrence is removed from the network” and a NIC from the other RAID controller “takes
`
`over a function” of a NIC on the faulty RAID controller. (Id. at 4:19-25.)
`
`B.
`
`Prosecution History
`
`Two amendments were made during prosecution of the application which issued as
`
`the ’346 patent. An initial amendment was made following a rejection over US 5,812,754
`
`(hereinafter “Lui”). On February 10, 2005, the examiner issued a Final Office Action
`
`rejecting all claims over Lui. In response, Applicant amended claims 1-9 and argued that Lui
`
`does not teach “two network interface controlling units included in each RAID controller.”
`
`(Ex. 1002 at 48.) Applicant argued that Lui does not teach that “the first network controlling
`
`unit exchanges information with the fourth network controlling unit and the second network
`
`controlling unit exchanges information with the third network controlling unit.” (Id. at 48-49.)
`
`8
`
`

`

`V.
`
`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`MANNER OF APPLYING CITED PRIOR ART TO EVERY CLAIM FOR WHICH AN
`IPR IS REQUESTED, THUS ESTABLISHING A REASONABLE LIKELIHOOD
`THAT AT LEAST ONE CLAIM OF THE ’346 PATENT IS UNPATENTABLE
`This request shows how the references above, alone or in combination with each
`
`other and other supporting references, disclose the limitations of the Challenged Claims and
`
`show they are unpatentable. As detailed below, this request shows a reasonable likelihood
`
`that Petitioner will prevail with respect to the Challenged Claims.
`
`A.
`
`Brief Description of the References
`i.
`Mylex
`Mylex is a whitepaper entitled “Storage Area Networks: Unclogging LANs and
`
`Improving Data Accessibility,” authored by Kevin J. Smith of the Mylex Corporation and
`
`published on the Mylex Corporation’s public website. Mylex describes the Mylex Fibre
`
`Channel product line of external RAID controllers and the use of storage area networks to
`
`configure reliable and high-performance pools of storage. (Ex. 1006 at 2.) Mylex discloses
`
`SANs (storage area networks) made up of hubs and switches that include redundant
`
`connections between multiple hosts and RAID arrays, allowing for host-independent
`
`failover. (Id. at 16.) Mylex teaches fault tolerance where NICs on one RAID controller take
`
`over the function of NICs on a faulty RAID controller. (Id. at Figs. 17-19; Ex. 1003, ¶¶ 39-41,
`
`140-141). Mylex discloses a direct heartbeat path between controllers for exchanging fault
`
`tolerance information. (Ex. 1006 at Fig. 17).
`
`9
`
`

`

`Hathorn
`ii.
`The Hathorn patent, entitled “Remote Data Shadowing Using A Multimode Interface
`
`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`
`To Dynamically Reconfigure Control Link-Level And Communication Link-Level” and
`
`assigned to IBM, is directed to DASDs (direct access storage devices) and discloses that
`
`multiple DASDs can be configured as a RAID. (Ex. 1003, ¶ 44.) Hathorn discloses that if a
`
`single DASD fails, then the lost data can be recovered by using the remaining data and
`
`error correction procedures. (Ex. 1005 at 2:4-11.)
`
`Hathorn teaches that RAID controllers can communicate either via direct paths
`
`between controllers, like in the Mylex reference, or by modifying the NICs to communicate
`
`between each other over the existing switch network. (Ex. 1003, ¶¶ 48-55.) Hathorn teaches
`
`that the storage controllers can have “dual function link-level facilities … [which allow] the
`
`primary and secondary storage controller ports 321, 324, 331, and 334 [to] be dynamically
`
`set to communicate either as a channel or control unit link-level facility.” (Ex. 1005 at 8:1-6;
`
`10:41-45.) A “channel link-level facility” allows the storage controller ports on two different
`
`RAID controllers to exchange information. (Id. at 5:8-15.)
`
`Deitz
`iii.
`U.S. Patent No. 6,578,158 to Deitz, titled “Method And Apparatus For Providing A
`
`RAID Controller Having Transparent Failover And Fallback,” is assigned to IBM. Deitz
`
`discloses redundant RAID systems including multiple host computers connected to a
`
`plurality of hubs, where 1) one hub is connected to (i) an active RAID controller port on a
`
`10
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`first RAID controller and (ii) an inactive RAID controller port on a second RAID controller,
`
`and 2) a second hub is connected to (i) an inactive RAID controller port on a first RAID
`
`controller and (ii) an active RAID controller port on a second RAID controller. (Ex. 1003, ¶¶
`
`224.)
`
`Deitz discloses the transmission of heartbeat signals (also called pings or polls)
`
`between RAID controllers through an inter-RAID-controller path (Figure 1) or a storage-side
`
`path (Figure 2, and 6:59-64). (Ex. 1008, at Figures 1-2; 6:59-63.)
`
`Griffith
`iv.
`The Griffith patent, titled “RAID Systems During Non-Fault And Faulty Conditions On
`
`A Fiber Channel Arbitrated Loop SCSI Bus Or Switch Fabric Configuration,” is assigned to
`
`Digi-Data Corporation. Griffith discloses a RAID system that uses arbitrated fiber channels
`
`or switch fabric to connect multiple host computers and storage array controllers (“SACs”).
`
`(Ex. 1007, at Abstract.) Griffith Figure 5 shows an embodiment of an “ACTIVE-ACTIVE
`
`redundant RAID system … which incorporates a switch fabric configuration.” (Id. at 4:53-55;
`
`Ex. 1003, ¶ 207.) Griffith teaches that fault tolerance information can be exchanged either
`
`through (i) a direct path between RAID controllers or (ii) by allowing the NICs to exchange
`
`information using the existing switch network. (Ex. 1007, at 9:15-21; 8:25-26; 9:37-40; Ex.
`
`1003, ¶¶ 204-16.) For example, see the annotated Griffith Fig. 4 below:
`
`11
`
`

`

`
`
`
`
`Atttorney Docket No.: 27450-00011IP1
`
`
`IPR of U.S. PPatent No. 6,9778,346
`
`
`
`
`GGriffith disclooses a redunndant RAIDD system in wwhich the swwitch fabric connectingg the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`host commputers andd the controllers “provides redundaancy in the ccase of any single compputer
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`or controoller failure.”” (Ex. 1007, at 2:35-38;; 8:63-64.) ““[E]ach SACC is designaated a primaary
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SAC for an array of storage uniits, which it
`
`
`
`normally seerves as conntroller, andd as a seconndary
`
`
`
`
`
`
`
`
`
`SAC for another array of storagge units.” (Idd. at Abstracct; Ex. 10033, ¶ 209.)
`
`
`
`
`
`
`
`
`
`
`
`
`v.
`DeKoningg
`
`
`
`TThe DeKoninng patent, tittled “Metho
`
`
`
`ds And Appparatus For
`
`
`
`Coordinatinng Shared
`
`
`
`Multiple Raid Controoller Accesss To Commoon Storage Devices,” iss assigned tto LSI Logicc
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Corp. D
`
`
` …
`eKoning disscloses an ““invention [that] providees inter-conttroller commmunications
`
`
`
`
`
`
`
`
`
`
`
`
`
`[so that aa plurality of RAID conttrollers] commmunicate aamong themmselves to ppermit continnued
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`operationns in case oof failures.” (Ex. 1010 aat 3:15-21.) DeKoning teaches ussing several
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`12
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`communication mediums to exchange between RAID controllers, including using the
`
`existing host-side communication bus. (Id. at 4:58-5:10; Ex. 1003, ¶¶ 206, 216.)
`
`Motivation to Combine
`B.
`One of ordinary skill would have been motivated to apply the respective teachings of
`
`Mylex and Hathorn to render obvious claims 1-9 of the ’346 Patent. One of ordinary skill
`
`would have been motivated to combine the teachings of Mylex with Hathorn because of the
`
`close relationship between Mylex Corporation and IBM, assignee of the Hathorn patent. In
`
`September of 1999, IBM acquired Mylex. Storage system designers at IBM in the 2000
`
`timeframe would have been strongly motivated to combine and leverage storage technology
`
`from Mylex, and vice versa. Later IBM products were partly based on the technology IBM
`
`acquired from Mylex, demonstrating that the motivation to combine these features was real
`
`and actually resulted in new products. (Ex. 1003, ¶ 34.)
`
`Mylex and Hathorn also are directed to the same field of endeavor, and both
`
`describe similar redundant RAID systems that connect multiple hosts to switches or hubs,
`
`which in turn connect to RAID controllers with two or more ports. Both Mylex and Hathorn
`
`describe redundancy in terms of sending communications between two or more RAID
`
`controllers and/or network interface controller ports. Both Mylex and Hathorn disclose RAID
`
`1-type systems (disk mirroring/shadowing) (Ex. 1006 at 12; Ex. 1005 at 1:9-12), and
`
`disclose using off-the-shelf components for constructing the RAID system, and as such their
`
`combination is merely the use of known techniques to achieve predictable results. (Ex. 1006
`
`13
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`at 15 (marketing “Mylex controllers”); Ex. 1005 at 6:25-34 (describing an IBM Enterprise
`
`Systems/9000 (ES/9000) processor running DFSMS/MVS operating software, IBM 3990
`
`Model 6 storage controllers, and an IBM ESCON Director dynamic switch).) One of ordinary
`
`skill would have been motivated to study multiple examples of disk mirroring systems when
`
`designing a new RAID system. As a result of their similarity, one of ordinary skill would have
`
`been able to apply the fault tolerance teachings of Mylex to the system disclosed by
`
`Hathorn, or the modifying NICs to communicate teachings of Hathorn to the system
`
`disclosed by Mylex with predictable results. (Ex. 1003, ¶ 33-34.)
`
`In addition, one of ordinary skill would have been motivated to apply (i) the Griffith
`
`teachings of exchanging fault tolerance information using the existing switch network or (ii)
`
`the DeKoning teachings of using a host-side communication bus to allow RAID controllers
`
`to exchange information, to the systems described in Mylex or Deitz in order to render every
`
`claim in the ’346 patent obvious. Mylex, Deitz, Griffith and DeKoning are in the same field of
`
`endeavor, and each describes redundant RAID systems that connect multiple hosts to RAID
`
`controllers. While Griffith only discloses using one switch or hub, and DeKoning discloses
`
`using a host-side communication bus, the concept of using multiple switches or hubs in
`
`RAID systems was well known at the time of the alleged invention. (See, Ex. 1005 at Fig. 3.)
`
`Further, Griffith, DeKoning, Deitz and Mylex describe fault tolerance in terms of
`
`sending communications between two or more RAID controllers and/or network interface
`
`controlling unit ports. One of ordinary skill would have been motivated to study multiple
`
`14
`
`

`

`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`examples of fault tolerant RAID systems when designing a new RAID system, and Mylex
`
`Corporation, IBM (assignee of the Deitz patent) and Digi-Data Corporation (assignee of the
`
`Griffith patent) were all RAID providers. One of ordinary skill would have known to look at
`
`the teachings of these RAID providers when configuring redundant RAID systems.
`
`Furthermore, Mylex, Deitz, and Griffith all describe redundant RAID systems comprised of
`
`off-the shelf components, and as such their combination is merely the use of known
`
`techniques to achieve predictable results. (Ex. 1006, at 15 (marketing “Mylex controllers”);
`
`Ex. 1007 at 5:33-35 (“A preferred SAC is the Z-9100 Ultra-Wide SCSI RAID controller
`
`manufactured by Digi-Data Corporation, Jessup, Md.”); Ex. 1008 at 5:33-36 (“controllers
`
`105 can be any suitable fibre channel compatible controller that can be modified to operate
`
`according to the present invention, such as for example the DAC960SF, commercially
`
`available from Mylex, Inc., Boulder, Colo.”); Ex. 1003, ¶¶ 221-222, 230.)
`
`One of ordinary skill also would have been motivated to combine the teachings of
`
`Griffith with Mylex controllers because Griffith discloses that its “preferred dual-port disk is
`
`the 3.5-Inch Ultrastar2 XP available from IBM” (Ex. 1007 at 8:38-39), and there was a close
`
`relationship between IBM and Mylex Corporation. In September of 1999, IBM completed the
`
`acquisition of Mylex. Storage system designers in that timeframe using the IBM 3.5-Inch
`
`Ultrastar2 XP disclosed in Griffith would have been strongly motivated to combine and
`
`leverage the teachings from other IBM and Mylex storage technology. (Ex. 1003, ¶ 221-222,
`
`230.)
`
`15
`
`

`

`A.
`
`
`Attorney Docket No.: 27450-0011IP1
`IPR of U.S. Patent No. 6,978,346
`[GROUND 1 and GROUND 2] – The Combination of Mylex and Hathorn
`Renders Obvious Claims 1-9
`Claims 1-9 of the ’346 patent are obvious in light of Mylex in view of the teaching of
`
`Hathorn, and/or Hathorn in view of the teachings of Mylex, thereby rendering each of these
`
`claims unpatentable under 35 U.S.C. § 103.3
`
`Specifically, a person of ordinary skill would understand that the Mylex paper
`
`discloses every element of the ’346 patent’s claims 1-9, with the exception of a direct
`
`exchange of information between network interface controlling units. Instead, the Mylex
`
`paper discloses a direct “heartbeat” communication path between controllers for exchanging
`
`information. However, the Hathorn patent teaches that communication paths are expensive,
`
`and that this expense can be reduced by modifying network interface controlling unit ports
`
`to use the existing switch network for communications between RAID controllers (instead of
`
`using a direct “heartbeat” path). (Ex. 1003, ¶¶ 32, 48-55.) An annotated Mylex Figure 17 is
`
`included below showing this combination:
`
`
`3 To avoid the duplicative presentation of formal elements (e.g. the claim language) and for
`
`the Board’s convenience, Petitioner presents a single claim chart to address Grounds 1-2.
`
`16
`
`

`

`
`
`
`
`Atttorney Docket No.: 27450-00011IP1
`
`
`IPR of U.S. PPatent No. 6,9778,346
`
`
`
`
`
`AAdditionally, a person off ordinary skkill would unnderstand thhat the Hathhorn patent
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`disclosess every elemment of the ’346 patentt’s claims 1--9, with the ppossible ex
`
`
`
`
`
`
`
`
`
`
`
`
`
`ception of thhe
`
`
`
`fault toleerance functtionality recited in the ’3346 patent’ss claims 4 a
`
`
`
`
`
`
`
`
`
`
`
`nd 9. Howeever, the Myylex
`
`
`
`closes that
`
`all
`
`
`
`paper teaches fault tolerance aas claimed. ((Ex. 1003, ¶¶¶ 40-41.) HHathorn dis
`
`
`
`
`
`
`
`
`
`
`
`
`
`NICs cann be modifieed to excha
`
`
`
`
`
`
`
`
`
`nge informaation using tthe switch nnetwork. (Exx. 1005 at 1
`
`
`
`
`
`
`
`channel link-level faacility, sendss an EPC fraame to the ssecondary sstorage conntroller 335
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`the secoondary storaage controlleer 335 proceesses the EEPC frame aand returns
`
`
`
`
`
`
`
`
`
`
`
`
`
`acknowleedgement (AACK) framee.”); Ex. 10003, ¶¶ 48-555.) As such
`
`
`
`
`
`
`
`
`
`an
`
`
`
`, with refereence to Hathhorn
`
`
`
`
`
`43 (“Thee primary stoorage controoller 325, accting as hosst with the pports 324 ennabled as
`
`
`
`
`
`
`
`
`
`
`
`1:25-
`
`…
`
`
`
`Fig. 3, poorts 324B and 334B (2nd and 4th NICs) can bbe used to eexchange faault tolerancce
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`informatiion in a nonn-faulty statee, as claimeed. Using thee fault toleraance teachi
`
`
`
`
`
`
`
`
`
`
`
`
`
`ngs of Myleex,
`
`17
`
`

`

`
`
`these poorts can execute a functtion of portss 324A and
`
`
`
`
`
`
`
`
`
`state, ass claimed.
`
`
`
`
`
`Atttorney Docket No.: 27450-00011IP1
`
`
`IPR of U.S. PPatent No. 6,9778,346
`
`
`
`334A (1st aand 3rd NICCs) in a faultty
`
`
`
`FFurther, with respect to claim [4b], oone of ordinnary skill, ussing the teacchings of
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hathorn,, would havee found it obbvious to coonfigure Myllex’s secondd and fourthh network
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`interfacee controlling units to excchange fault tolerance
`
`
`
`
`
`
`
`information
`
`
`
`. For exampple, with
`
`
`
`reference to

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