`PetitionersPetitioners
`
`Dell, H-P, and NetAppDell, H-P, and NetApp
`
`
`IPR2013-00635IPR2013-00635
`
`U.S. Patent No. 6,978,346U.S. Patent No. 6,978,346
`
`
`Russ EmersonRuss Emerson
`
`David McCombsDavid McCombs
`
`Thomas KeltonThomas Kelton
`
`Haynes and Boone, LLPHaynes and Boone, LLP
`
`December 18, 2014December 18, 2014
`
`1
`
`Dell et al. v Electronics and Telecommunications / IPR2013-00635
`DHPN-1016 / Page 1 of 34
`
`
`
`
`
`’346 Patent, Claim 1’346 Patent, Claim 1
`
`DHPN‐1001, ’346 Patent, claim 1
`(Discussed inter alia in Petition,
`paper no. 1 at 45‐53)
`
`2
`
`IPR2013-00635 / DHPN-1016
`Page 2 of 34
`
`
`
`
`
`Hathorn discloses a RAID and RAID controlling unitsHathorn discloses a RAID and RAID controlling units
`
`DHPN‐1012, Second Mercer Decl. at p.13
`(Discussed at Petitioner’s Reply,
`paper no. 33 at pp.3‐4)
`
`3
`
`IPR2013-00635 / DHPN-1016
`Page 3 of 34
`
`
`
`
`
`Competing constructions of “RAID”Competing constructions of “RAID”
`
`Paper 19, Institution Decision at p.8
`(Discussed at Petitioner’s reply, paper no. 33 at p.2)
`
`Paper 27, PO Response at p.12
`
`4
`
`IPR2013-00635 / DHPN-1016
`Page 4 of 34
`
`
`
`
`
`A RAID is not limited to a “single logical unit”A RAID is not limited to a “single logical unit”
`
`DHPN‐1003 (Weygant) at p.153
`(Discussed at Petitioner’s reply, paper no. 33 at p.7)
`
`5
`
`IPR2013-00635 / DHPN-1016
`Page 5 of 34
`
`
`
`
`
`Hathorn discloses “shadowing”Hathorn discloses “shadowing”
`
`DHPN‐1005, ‘950 Patent (“Hathorn”)
`(Discussed inter alia in Petition, paper no. 1 at 45‐53)
`
`6
`
`IPR2013-00635 / DHPN-1016
`Page 6 of 34
`
`
`
`
`
`“RAID” includes mirroring“RAID” includes mirroring
`
`DHPN‐1006, Mercer Decl. at pp.22‐23, citing DHPN‐1003, Weygant at p.153
`(Discussed at Petitioner’s Reply, paper no. 33 at pp.4,7‐8)
`
`7
`
`IPR2013-00635 / DHPN-1016
`Page 7 of 34
`
`
`
`
`Mirroring and shadowing are the same concept and Mirroring and shadowing are the same concept and
`
`both are within RAIDboth are within RAID
`
`DHPN‐1012, 2nd Mercer Decl. at p.4, citing DHPN‐1011, Chen at p.10
`(Discussed at Petitioner’s Reply, paper no. 33 at pp.3‐4 and 5)
`
`8
`
`IPR2013-00635 / DHPN-1016
`Page 8 of 34
`
`
`
`
`Hathorn recognizes that DASDs can be configured as Hathorn recognizes that DASDs can be configured as
`
`a RAIDa RAID
`
`DHPN‐1005, ‘950 Patent (“Hathorn”) at 2:4‐11
`(Discussed inter alia in Petition, paper no. 1 at 47)
`
`9
`
`IPR2013-00635 / DHPN-1016
`Page 9 of 34
`
`
`
`
`PO’s expert acknowledges that Hathorn teaches a PO’s expert acknowledges that Hathorn teaches a
`
`RAID and RAID controlling unitRAID and RAID controlling unit
`
`ETRI‐2003, Conte Decl., at pp.32‐33
`(Discussed at Petitioner’s Reply, paper no. 33 at p.4)
`
`DHPN‐1012, Second Mercer Decl. at p.13
`(Discussed at Petitioner’s Reply, paper no. 33 at pp.3‐4)
`
`10
`
`IPR2013-00635 / DHPN-1016
`Page 10 of 34
`
`
`
`
`Board’s construction of “RAID controlling unit” is Board’s construction of “RAID controlling unit” is
`
`correctcorrect
`
`Paper 19, Institution Decision at pp.9‐10
`(Discussed at Petitioner’s reply, paper no. 33 at p.6)
`
`11
`
`IPR2013-00635 / DHPN-1016
`Page 11 of 34
`
`
`
`
`PO’s construction of “RAID controlling unit” is too PO’s construction of “RAID controlling unit” is too
`
`narrownarrow
`
`Paper 27, PO Response at p.13
`
`12
`
`IPR2013-00635 / DHPN-1016
`Page 12 of 34
`
`
`
`
`Hathorn discloses two “RAID controlling units” each with two Hathorn discloses two “RAID controlling units” each with two
`
`“network [interface] controlling units”“network [interface] controlling units”
`
`DHPN‐1012, 2nd Mercer Decl. at p.15,
`annotating DHPN‐1005, Hathorn Fig. 3
`(Discussed at Petitioner’s Reply,
`paper no. 33 at pp.10‐11)
`
`13
`
`IPR2013-00635 / DHPN-1016
`Page 13 of 34
`
`
`
`
`The Board correctly applied the plain and ordinary meaning to The Board correctly applied the plain and ordinary meaning to
`
`“network [interface] controlling unit”“network [interface] controlling unit”
`
`Paper 19, Institution Decision at p.11
`(Discussed at Petitioner’s reply, paper no. 33 at p.9)
`
`14
`
`IPR2013-00635 / DHPN-1016
`Page 14 of 34
`
`
`
`
`PO’s expert incorrectly limits the scope to hardware cards PO’s expert incorrectly limits the scope to hardware cards
`
`and adaptersand adapters
`
`ETRI‐2003, Conte Decl., at pp.24‐26
`(Discussed in Petitioner Reply, paper no. 33 at p.9)
`
`15
`
`IPR2013-00635 / DHPN-1016
`Page 15 of 34
`
`
`
`
`
`“network [interface] control unit” is not linked to hardware“network [interface] control unit” is not linked to hardware
`
`DHPN‐1013, The Authoritative Dictionary of IEEE Standards Terms, 7th Ed. (cited in 2nd Mercer Decl. at
`pp.6‐7 and discussed in Petitioner Reply, paper no. 33 at p.9)
`
`DHPN‐1014, Microsoft Computer Dictionary, 4th Ed. (cited in 2nd Mercer Decl. at pp.6‐7 and
`discussed in Petitioner Reply, paper no. 33 at p.9)
`
`16
`
`IPR2013-00635 / DHPN-1016
`Page 16 of 34
`
`
`
`
`
`“network [interface] control unit” is not linked to hardware“network [interface] control unit” is not linked to hardware
`
`DHPN‐1012, 2nd Mercer Decl. at p.4
`(Discussed at Petitioner’s Reply, paper no. 33 at p.9)
`
`17
`
`IPR2013-00635 / DHPN-1016
`Page 17 of 34
`
`
`
`
`Hathorn’s ports are “network [interface] control units” that are Hathorn’s ports are “network [interface] control units” that are
`
`dynamically set to control communication over the networkdynamically set to control communication over the network
`
`DHPN‐1005, Hathorn 8:1‐16,
`(Discussed at Petitioner’s Reply, paper no. 33 at p.11)
`
`DHPN‐1012, 2nd Mercer Decl. at p.15,
`annotating DHPN‐1005, Hathorn Fig. 3
`(Discussed at Petitioner’s Reply, paper no. 33 at pp.10‐11)
`
`18
`
`IPR2013-00635 / DHPN-1016
`Page 18 of 34
`
`
`
`
`Hathorn’s “respective RAID controlling units are connected to Hathorn’s “respective RAID controlling units are connected to
`
`the plurality of individual connecting units” (Claim 2)the plurality of individual connecting units” (Claim 2)
`
`DHPN‐1005, Fig. 3 (annotated), as cited in DHPN‐1006, Mercer Decl. at pp.140 and 145‐146
`(Discussed at Petition, paper no. 1 at p.54)
`
`19
`
`IPR2013-00635 / DHPN-1016
`Page 19 of 34
`
`
`
`
`Claim 2 does not require that each RAID controlling unit connects Claim 2 does not require that each RAID controlling unit connects
`
`to all of the individual connecting unitsto all of the individual connecting units
`
`DHPN‐1001, ‘346 patent, claim 2
`(Discussed at Petitioner’s Reply, paper no. 33 at p. 12)
`
`20
`
`IPR2013-00635 / DHPN-1016
`Page 20 of 34
`
`
`
`
`Hathorn teaches “the first network interface controlling unit is coupled to the Hathorn teaches “the first network interface controlling unit is coupled to the
`
`connecting unit of one side and the second network interface controlling unit is connecting unit of one side and the second network interface controlling unit is
`
`coupled to the connecting unit of another side” (Claim 3)coupled to the connecting unit of another side” (Claim 3)
`
`DHPN‐1005, Fig. 3 (annotated), as cited in DHPN‐1006 DHPN‐1006, Mercer Decl. at pp.146‐147
`(Discussed at Petition, paper no. 1 at p.54‐55)
`
`21
`
`IPR2013-00635 / DHPN-1016
`Page 21 of 34
`
`
`
`
`
`Hathorn teaches the connections of claim 8Hathorn teaches the connections of claim 8
`
`DHPN‐1005, Hathorn Fig. 3 (annotated)
`(Discussed at Petition, paper no. 1 at p.60)
`
`22
`
`IPR2013-00635 / DHPN-1016
`Page 22 of 34
`
`
`
`
`
`“connected” includes connections through hubs/switches“connected” includes connections through hubs/switches
`
`DHPN‐1001, ‘346 patent, 3:31‐38
`(Discussed at Petitioner’s Reply, paper no. 33 at pp.11‐12)
`
`DHPN‐1001, ‘346 patent, claim 1
`(Discussed at Petitioner’s Reply, paper no. 33 at pp.11‐12)
`
`23
`
`IPR2013-00635 / DHPN-1016
`Page 23 of 34
`
`
`
`
`
`Petitioner did not construe “connected”Petitioner did not construe “connected”
`
`DHPN‐1006, Mercer Decl. at ¶ 36
`(Discussed at Petitioner’s Reply, paper no. 33 at p.12)
`
`24
`
`IPR2013-00635 / DHPN-1016
`Page 24 of 34
`
`
`
`
`
`Petitioner did not construe “connected”Petitioner did not construe “connected”
`
`DHPN‐1012, 2nd Mercer Decl. at ¶ 9
`(Discussed at Petitioner’s Reply, paper no. 33 at p.12)
`
`25
`
`IPR2013-00635 / DHPN-1016
`Page 25 of 34
`
`
`
`
`Hathorn teaches the hub equipment connected to the numerous host computers Hathorn teaches the hub equipment connected to the numerous host computers
`
`(Claim 5)(Claim 5)
`
`DHPN‐1005, Fig. 3 (annotated), as cited in DHPN‐1006, Mercer Decl. at pp.149‐150
`(Discussed at Petition, paper no. 1 at pp.55‐56)
`
`26
`
`IPR2013-00635 / DHPN-1016
`Page 26 of 34
`
`
`
`
`
`‘346 Patent defines “hub” as “hub or switch”‘346 Patent defines “hub” as “hub or switch”
`
`DHPN‐1001, ‘346 patent, 3:13‐18
`(Discussed at Petitioner’s Reply, paper no. 33 at p.13)
`
`27
`
`IPR2013-00635 / DHPN-1016
`Page 27 of 34
`
`
`
`
`
`Claims 5 and 6 are different even if “hub” means “hub or switch”Claims 5 and 6 are different even if “hub” means “hub or switch”
`
`DHPN‐1001, ‘346 patent, claim 1
`(Discussed at Petitioner’s Reply, paper no. 33 at p.13)
`
`28
`
`IPR2013-00635 / DHPN-1016
`Page 28 of 34
`
`
`
`
`Hathorn teaches the plurality of connecting units have at least [X] connection ports, Hathorn teaches the plurality of connecting units have at least [X] connection ports,
`
`[Y] of the at least [X] connection ports is coupled to one of the first network [Y] of the at least [X] connection ports is coupled to one of the first network
`
`interface controlling unit and the third network controlling unit (Claims 5-7)interface controlling unit and the third network controlling unit (Claims 5-7)
`
`DHPN‐1005, Fig. 3 (truncated and annotated),
`as cited in DHPN‐1006, Mercer Decl. at pp.146‐147
`(Discussed at Petition, paper no. 1 at p.149‐150)
`
`29
`
`IPR2013-00635 / DHPN-1016
`Page 29 of 34
`
`
`
`
`Hathorn teaches the rest of the connection ports being provided as a hub Hathorn teaches the rest of the connection ports being provided as a hub
`
`equipment connected with the numerous host computers (Claims 5-7)equipment connected with the numerous host computers (Claims 5-7)
`
`DHPN‐1005, Fig. 3 (annotated),
`as cited in DHPN‐1006, Mercer Decl. at pp.149‐150
`(Discussed at Petition, paper no. 1 at pp.55‐56)
`
`30
`
`IPR2013-00635 / DHPN-1016
`Page 30 of 34
`
`
`
`
`The hub equipment/network switch equipment is The hub equipment/network switch equipment is
`
`“connected with the numerous host computers.” “connected with the numerous host computers.”
`
`DHPN‐1001, ‘346 patent, claim 1
`(Discussed at Petitioner’s Reply,
`paper no. 33 at pp.14‐15)
`
`31
`
`IPR2013-00635 / DHPN-1016
`Page 31 of 34
`
`
`
`
`
`PO's brief replaces key words with ellipses (Claim 3)PO's brief replaces key words with ellipses (Claim 3)
`
`PO's Response at p.55
`(Discussed at Petitioner's Reply, paper no. 33 at pp.14‐15)
`
`32
`
`IPR2013-00635 / DHPN-1016
`Page 32 of 34
`
`
`
`
`
`Hathorn teaches the connection units with connection portsHathorn teaches the connection units with connection ports
`
`DHPN‐1005,Hathorn, Fig. 3
`(Discussed at Petition, paper no. 1at pp.51 and Petitioner’s Reply, paper no. 33 at pp.15)
`
`DHPN‐1005,Hathorn, Fig. 3
`(Discussed at Petition, paper no. 1at p.55 and Discussed at Petitioner’s Reply, paper no. 33 at p.15)
`
`33
`
`IPR2013-00635 / DHPN-1016
`Page 33 of 34
`
`
`
`
`PetitionersPetitioners
`
`Dell, H-P, and NetAppDell, H-P, and NetApp
`
`
`IPR2013-00635IPR2013-00635
`
`U.S. Patent No. 6,978,346U.S. Patent No. 6,978,346
`
`
`Russ EmersonRuss Emerson
`
`David McCombsDavid McCombs
`
`Thomas KeltonThomas Kelton
`
`Haynes and Boone, LLPHaynes and Boone, LLP
`
`December 18, 2014December 18, 2014
`
`34
`
`IPR2013-00635 / DHPN-1016
`Page 34 of 34
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
