`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`GOOGLE LLC
`Petitioner
`
`v.
`
`LS CLOUD STORAGE TECHNOLOGIES LLC
`Patent Owner
`____________
`
`Case IPR2023-00120
`U.S. Patent No. 10,154,092
`____________
`
`GOOGLE LLC’S PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 10,154,092
`
`
`
`
`
`TABLE OF CONTENTS
`
`Page
`
`I.
`
`INTRODUCTION ......................................................................................... 1
`
`II. MANDATORY NOTICES ........................................................................... 2
`
`A. Real Party-in-Interest ......................................................................... 2
`
`B.
`
`Related Matters ................................................................................... 2
`
`C. Counsel and Service ............................................................................ 3
`
`D.
`
`Power of Attorney ............................................................................... 4
`
`E.
`
`Fees ........................................................................................................ 4
`
`III. REQUIREMENTS FOR INTER PARTES REVIEW .............................. 4
`
`A. Grounds for Standing ......................................................................... 4
`
`B.
`
`Identification of Challenge and Relief Requested ............................ 4
`
`IV. THE ’092 PATENT ....................................................................................... 6
`
`V.
`
`PROSECUTION HISTORY ........................................................................ 8
`
`VI. THE CHALLENGED CLAIMS ARE UNPATENTABLE .....................11
`
`A.
`
`State of the Art ................................................................................... 11
`
`B. Overview of the Prior Art ................................................................. 13
`
`a.
`
`b.
`
`c.
`
`d.
`
`Heil 13
`
`Nakayama ................................................................................ 15
`
`Gulick ....................................................................................... 17
`
`Berman ..................................................................................... 17
`
`C.
`
`Level of Ordinary Skill in the Art ................................................... 17
`
`
`
`i
`
`
`
`
`
`D. Claim Construction ........................................................................... 18
`
`E. Ground 1: Claims 1-3, 7-12, and 19-23 are anticipated by
`Heil under 35 U.S.C. § 102(e) ........................................................... 21
`
`a.
`
`Claim 1 ..................................................................................... 21
`
`i.
`
`ii.
`
`Claim 1.pre ....................................................................21
`
`Claim 1.a: “a first interface configured to
`receive input/output (I/O) traffic from a first
`host device via a dedicated I/O channel, the I/O
`traffic comprising a read command” ..........................21
`
`iii. Claim 1.b: “a second interface configured to
`receive first data via a network” .................................24
`
`iv. Claim 1.c: “a cache memory configured to store
`second data” ..................................................................26
`
`v.
`
`Claim 1.d: “a storage device configured to store
`third data” .....................................................................26
`
`vi. Claim 1.e: “a processor coupled to the cache
`memory, the processor coupled to the storage
`device via a communication path that is distinct
`from the dedicated I/O channel, the processor
`configured to access the cache memory during
`processing of the I/O traffic” .......................................27
`
`vii. Claim 1.f: “the processor further configured to
`perform an access operation at the storage
`device based on the I/O traffic” ...................................30
`
`Claim 2 ..................................................................................... 31
`
`Claim 3 ..................................................................................... 31
`
`Claim 7 ..................................................................................... 33
`
`Claim 8 ..................................................................................... 34
`
`ii
`
`b.
`
`c.
`
`d.
`
`e.
`
`
`
`
`
`
`
`
`
`f.
`
`Claim 9 ..................................................................................... 35
`
`g.
`
`h.
`
`i.
`
`j.
`
`i.
`
`ii.
`
`Claim 9.a: “the storage device and the
`dedicated I/O channel are independently
`accessible” ......................................................................35
`
`Claim 9.b: “wherein the processor is configured
`to read at least a portion of the second data
`from the cache memory based on the read
`command” .....................................................................36
`
`Claim 10 ................................................................................... 37
`
`Claim 11 ................................................................................... 38
`
`i.
`
`Claim 11.a: “configuration manager circuitry
`configured to route an I/O request included in
`the I/O traffic to the cache memory, to route the
`I/O request to the storage device, or to deny the
`I/O request” ...................................................................38
`
`ii.
`
`Claim 11.b: “front-end circuitry configured to
`process the I/O request” ...............................................39
`
`iii. Claim 11.c: “back-end circuitry configured to
`perform a read operation or a write operation
`at the storage device based on the I/O request” ........40
`
`Claim 12 ................................................................................... 40
`
`Claim 19 ................................................................................... 41
`
`i.
`
`ii.
`
`Claim 19.pre ..................................................................41
`
`Claim 19.a: “a first interface configured to
`receive input/output (I/O) traffic from a host
`computer via a dedicated I/O channel, the I/O
`traffic comprising one or more read commands,
`one or more write commands, or a combination
`thereof” ..........................................................................41
`
`iii
`
`
`
`
`
`iii. Claim 19.b: “a second interface configured to
`receive data via a network” .........................................41
`
`iv. Claim 19.c: “a cache memory” ....................................41
`
`v.
`
`Claim 19.d: “a storage device” ....................................41
`
`vi. Claim 19.e: “a processor coupled via a
`communication path to the storage device, the
`processor configured to access the cache
`memory during processing of the I/O traffic” ...........41
`
`vii. Claim 19.f: “the processor further configured to
`perform one or more access operations at the
`storage device based on the I/O traffic, wherein
`the communication path is distinct from the
`dedicated I/O channel” .................................................42
`
`k.
`
`Claim 20 ................................................................................... 42
`
`l.
`
`Claim 21 ................................................................................... 42
`
`m. Claim 22 ................................................................................... 42
`
`n.
`
`Claim 23 ................................................................................... 43
`
`F. Ground 2: Claims 10 and 11 are anticipated by Heil under
`35 U.S.C. § 102(b) .............................................................................. 43
`
`G. Ground 3: Claims 1-3 and 6-24 are obvious over Heil and
`Nakayama under 35 U.S.C. § 103(a) ............................................... 44
`
`a.
`
`A POSITA Would Have Combined Heil and
`Nakayama ................................................................................ 44
`
`b.
`
`Claim 1 ..................................................................................... 45
`
`i.
`
`Claim 1.pre ....................................................................45
`
`ii.
`
`Claim 1.a ........................................................................45
`
`iii. Claim 1.b ........................................................................47
`
`
`
`iv
`
`
`
`
`
`
`
`iv. Claim 1.c ........................................................................47
`
`v.
`
`Claim 1.d ........................................................................47
`
`vi. Claim 1.e ........................................................................47
`
`vii. Claim 1.f .........................................................................47
`
`c.
`
`d.
`
`e.
`
`f.
`
`g.
`
`h.
`
`i.
`
`j.
`
`Claim 2 ..................................................................................... 48
`
`Claim 3 ..................................................................................... 48
`
`Claim 6 ..................................................................................... 48
`
`Claim 7 ..................................................................................... 49
`
`Claim 8 ..................................................................................... 49
`
`Claim 9 ..................................................................................... 49
`
`Claim 10 ................................................................................... 49
`
`Claim 11 ................................................................................... 50
`
`k.
`
`Claim 12 ................................................................................... 51
`
`l.
`
`Claim 13 ................................................................................... 51
`
`i.
`
`Claim 13.pre ..................................................................51
`
`ii.
`
`Claim 13.a ......................................................................51
`
`iii. Claim 13.b ......................................................................53
`
`iv. Claim 13.c ......................................................................53
`
`v.
`
`Claim 13.d ......................................................................53
`
`vi. Claim 13.e ......................................................................53
`
`vii. Claim 13.f .......................................................................53
`
`v
`
`
`
`
`
`
`
`viii. Claim 14 .........................................................................55
`
`ix. Claim 15 .........................................................................55
`
`m. Claim 16 ................................................................................... 57
`
`n.
`
`Claim 17 ................................................................................... 58
`
`i.
`
`Claim 17.a ......................................................................58
`
`ii.
`
`Claim 17.b ......................................................................59
`
`o.
`
`p.
`
`Claim 18 ................................................................................... 59
`
`Claim 19 ................................................................................... 61
`
`i.
`
`Claim 19.pre ..................................................................61
`
`ii.
`
`Claim 19.a ......................................................................61
`
`iii. Claim 19.b ......................................................................62
`
`iv. Claim 19.c ......................................................................62
`
`v.
`
`Claim 19.d ......................................................................62
`
`vi. Claim 19.e ......................................................................62
`
`vii. Claim 19.f .......................................................................62
`
`q.
`
`Claim 20 ................................................................................... 62
`
`r.
`
`s.
`
`t.
`
`Claim 21 ................................................................................... 62
`
`Claim 22 ................................................................................... 63
`
`Claim 23 ................................................................................... 63
`
`u.
`
`Claim 24 ................................................................................... 63
`
`i.
`
`Claim 24.pre ..................................................................63
`
`vi
`
`
`
`
`
`ii.
`
`Claim 24.a ......................................................................64
`
`iii. Claim 24.b ......................................................................67
`
`iv. Claim 24.c ......................................................................68
`
`v.
`
`Claim 24.d ......................................................................69
`
`vi. Claim 24.e ......................................................................70
`
`H. Ground 4: Claim 4 is obvious over Heil, Nakayama, and
`Gulick under 35 U.S.C. § 103(a) ...................................................... 73
`
`a.
`
`A POSITA Would Have Combined Heil, Nakayama,
`and Gulick ................................................................................ 73
`
`b.
`
`Claim 4 is obvious ................................................................... 74
`
`I.
`
`Ground 5: Claim 5 is obvious over Heil, Nakayama, and
`Berman under 35 U.S.C. § 103(a) .................................................... 75
`
`a.
`
`A POSITA Would Have Combined Heil, Nakayama,
`and Berman ............................................................................. 75
`
`b.
`
`Claim 5 is obvious ................................................................... 76
`
`VII. SECONDARY CONSIDERATIONS ........................................................76
`
`VIII. DISCRETION ..............................................................................................77
`
`A.
`
`The Fintiv Factors Favor Institution ............................................... 77
`
`B. General Plastic is Inapplicable Here ............................................... 80
`
`C.
`
`35 U.S.C. § 325(d) Favors Institution .............................................. 80
`
`IX. CONCLUSION ............................................................................................81
`
`
`
`
`
`
`
`vii
`
`
`
`
`
`CASES
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`Brown v. 3M,
`265 F.3d 1349 (Fed. Cir. 2001) .......................................................................33
`
`Samsung Elecs. Am. Inc. v. Prisua Eng’g Corp.,
`948 F.3d 1342 (Fed. Cir. 2020) .......................................................................19
`
`Thryv, Inc. v. Click-To-Call Techs., LP,
`140 S. Ct. 1367 (2020) .....................................................................................79
`
`Williamson v. Citrix Online, LLC,
`792 F.3d 1339 (Fed. Cir. 2015) .......................................................................18
`
`STATUTES
`
`35 U.S.C. § 102 ......................................................................................... 4, 6, 21, 44
`
`35 U.S.C. § 103 ......................................................................................... 4, 5, 73, 75
`
`35 U.S.C. § 112 ................................................................................................. 18, 19
`
`35 U.S.C. § 132 ......................................................................................................5, 9
`
`35 U.S.C. § 325 ........................................................................................................80
`
`AGENCY DECISIONS
`
`Apple Inc. v. Fintiv, Inc.,
`IPR2020-00019, Paper 11 (Mar. 20, 2020) .....................................................77
`
`General Plastic Industrial Co., Ltd. v. Canon Kabushiki Kaisha,
`IPR2016-01357, Paper 19 (Sept. 6, 2017) .......................................................80
`
`Samsung Elecs. Co. Ltd. v. Dynamics Inc.,
`IPR2020-00505, Paper 11 (Aug. 12, 2020) .....................................................79
`
`
`
`
`
`viii
`
`
`
`
`
`REGULATIONS
`
`37 C.F.R. § 42.10 ....................................................................................................... 4
`
`37 C.F.R. § 42.104 ...................................................................................................19
`
`37 C.F.R. § 42.100 ...................................................................................................18
`
`PATENT PROCEDURES
`
`MPEP § 211 .............................................................................................................11
`
`
`
`
`
`
`
`ix
`
`
`
`
`
`PETITIONER’S EXHIBIT LIST
`
`
`
`Exhibit Number
`
`Description
`
`1001
`
`U.S. Patent No. 10,154,092
`
`1002
`
`File History of U.S. Patent No. 10,154,092 (Application No.
`
`14/997,327)
`
`1003
`
`File History of U.S. Patent No. 6,549,988 (Application No.
`
`09/236,409)
`
`1004
`
`Declaration of Dr. Paul Franzon, Ph.D.
`
`1005
`
`CV of Dr. Paul Franzon, Ph.D.
`
`1006
`
`U.S. Patent No. 6,173,374 (“Heil”)
`
`1007
`
`U.S. Patent No. 5,920,893 (“Nakayama”)
`
`1008
`
`U.S. Patent No. 5,692,211 (“Gulick”)
`
`
`
`x
`
`
`
`
`
`
`
`1009
`
`U.S. Patent No. 6,118,776 (“Berman”)
`
`1010
`
`United States District Courts – National Judicial Caseload
`
`Profile, https://www.uscourts.gov/sites/default/files/
`
`fcms_na_distprofile0331.2022.pdf (accessed September 21,
`
`2022)
`
`1011
`
`Order Staying Case in LS Cloud Storage Technologies, LLC
`
`v. Google LLC, 1:22-cv-00853 (W.D. Tex. 2022)
`
`1012
`
`USPTO Memo: Interim Procedure for Discretionary Denials
`
`in AIA Post-Grant Proceedings with Parallel District Court
`
`Litigation, June 21, 2022
`
`1013
`
`Order Setting Initial Pretrial Conference for 11/3/2022 in LS
`
`Cloud Storage Technologies, LLC v. Google LLC, 1:22-cv-
`
`00853 (W.D. Tex. 2022)
`
`1014
`
`D. Patterson, G. Gibson, R. Katz, entitled “A Case for
`
`Redundant Arrays of Inexpensive Disks (RAID)”.
`
`SIGMOD88: International Conference On Management of
`
`Data Chicago Illinois USA June 1 - 3, 1988
`
`xi
`
`
`
`
`
`1015
`
`R. H. Katz, "Network-attached storage systems," Proceedings
`
`Scalable High Performance Computing Conference SHPCC-
`
`92., Williamsburg, VA, USA, 1992, pp. 68-75
`
`1016
`
`Gang Ma and A. L. Narasimha Reddy, "An evaluation of
`
`storage systems based on network-attached disks,"
`
`Proceedings. 1998 International Conference on Parallel
`
`Processing (Cat. No.98EX205), Minneapolis, MN, USA,
`
`1998, pp. 278-285.
`
`1017
`
`Average Time to Trial for Patent Cases before Judge Yeakel,
`
`retrieved from www.docketnavigator.com
`
`1018
`
`Infringement Contentions served in LS Cloud Storage
`
`Technologies, LLC v. Google LLC, 1:22-cv-00853 (W.D.
`
`Tex. 2022)
`
`
`
`
`
`
`
`
`
`xii
`
`
`
`
`
`[1.pre]
`
`[1.a]
`
`[1.b]
`
`[1.c]
`
`[1.d]
`
`[1.e]
`
`LISTING OF CHALLENGED CLAIMS
`
`Reference
`
`Claim Limitation
`
`Claim 1
`
`An apparatus comprising:
`
`a first interface configured to receive
`
`input/output (I/O) traffic from a first
`
`host device via a dedicated I/O channel,
`
`the I/O traffic comprising a read
`
`command;
`
`a second interface configured to receive
`
`first data via a network;
`
`a cache memory configured to store
`
`second data;
`
`a storage device configured to store
`
`third data; and
`
`a processor coupled to the cache
`
`memory, the processor coupled to the
`
`storage device via a communication
`
`path that is distinct from the dedicated
`
`I/O channel, the processor configured
`
`to access the cache memory during
`
`processing of the I/O traffic,
`
`
`
`xiii
`
`
`
`
`
`[1.f]
`
`[2.pre]
`
`[2.a]
`
`[3.pre]
`
`[3.a]
`
`[4.pre]
`
`[4.a]
`
`
`
`the processor further configured to
`
`perform an access operation at the
`
`storage device based on the I/O traffic.
`
`
`
`Claim 2
`
`The apparatus of claim 1,
`
`wherein the dedicated I/O channel is
`
`associated with dedicated throughput
`
`that corresponds to the I/O traffic.
`
`
`
`Claim 3
`
`The apparatus of claim 1,
`
`wherein the I/O traffic is distinct from
`
`the first data.
`
`
`
`Claim 4
`
`The apparatus of claim 1,
`
`wherein the dedicated I/O channel
`
`comprises a small computer system
`
`interface (SCSI) channel.
`
`
`
`xiv
`
`
`
`
`
`[5.pre]
`
`[5.a]
`
`[6.pre]
`
`[6.a]
`
`[7.pre]
`
`[7.a]
`
`Claim 5
`
`The apparatus of claim 1,
`
`wherein the second interface comprises
`
`an Ethernet interface or an
`
`asynchronous transfer mode (ATM)
`
`interface.
`
`
`
`Claim 6
`
`The apparatus of claim 1,
`
`wherein the I/O traffic further
`
`comprises a write command.
`
`
`
`Claim 7
`
`The apparatus of claim 1,
`
`wherein the first data comprises a
`
`second read request, a write request, or
`
`a combination thereof.
`
`
`
`Claim 8
`
`[8.pre]
`
`The apparatus of claim 1,
`
`
`
`xv
`
`
`
`
`
`[8.a]
`
`[9.pre]
`
`[9.a]
`
`wherein the network comprises a
`
`plurality of interconnected computing
`
`devices.
`
`
`
`Claim 9
`
`The apparatus of claim 1,
`
`wherein the storage device and the
`
`dedicated I/O channel are
`
`independently accessible,
`
`[9.b]
`
`and wherein the processor is configured
`
`to read at least a portion of the second
`
`data from the cache memory based on
`
`the read command.
`
`
`
`Claim 10
`
`The apparatus of claim 1,
`
`wherein the processor is further
`
`configured to route the read command
`
`to the cache memory or to the storage
`
`device.
`
`
`
`Claim 11
`
`xvi
`
`[10.pre]
`
`[10.a]
`
`
`
`
`
`
`
`[11.pre]
`
`[11.a]
`
`[11.b]
`
`[11.c]
`
`[12.pre]
`
`[12.a]
`
`The apparatus of claim 1,
`
`configuration manager circuitry
`
`configured to route an I/O request
`
`included in the I/O traffic to the cache
`
`memory, to route the I/O request to the
`
`storage device, or to deny the I/O
`
`request;
`
`front-end circuitry configured to
`
`process the I/O request; and
`
`back-end circuitry configured to
`
`perform a read operation or a write
`
`operation at the storage device based on
`
`the I/O request.
`
`
`
`Claim 12
`
`The apparatus of claim 1,
`
`wherein the host device comprises a
`
`server.
`
`
`
`Claim 13
`
`[13.pre]
`
`A method comprising:
`
`
`
`xvii
`
`
`
`
`
`[13.a]
`
`[13.b]
`
`[13.c]
`
`[13.d]
`
`[13.e]
`
`[13.f]
`
`receiving input/output (I/O) traffic from
`
`a host device via a dedicated I/O
`
`channel at a first interface, the I/O
`
`traffic comprising a write command;
`
`receiving first data via a network at a
`
`second interface;
`
`storing second data at a cache memory;
`
`storing third data at a storage device;
`
`accessing the cache memory during
`
`processing of the I/O traffic; and
`
`performing one or more access
`
`operations at the storage device based
`
`on the I/O traffic, the one or more
`
`access operations utilizing a
`
`communication path between a
`
`processor and the storage device, the
`
`communication path distinct from the
`
`dedicated I/O channel.
`
`
`
`Claim 14
`
`[14.pre]
`
`The apparatus of claim 13,
`
`
`
`xviii
`
`
`
`
`
`[14.a]
`
`[15.pre]
`
`[15.a]
`
`[16.pre]
`
`[16.a]
`
`[17.pre]
`
`[17.a]
`
`wherein the I/O traffic is distinct from
`
`the first data.
`
`
`
`Claim 15
`
`The apparatus of claim 13,
`
`further comprising performing a first
`
`access operation at the storage device
`
`independently of the dedicated I/O
`
`channel.
`
`
`
`Claim 16
`
`The apparatus of claim 13,
`
`wherein the second data is written at
`
`the cache memory in response to the
`
`write command.
`
`
`
`Claim 17
`
`The apparatus of claim 13,
`
`further comprising: receiving a read
`
`request via the network; and
`
`
`
`xix
`
`
`
`
`
`[17.b]
`
`[18.pre]
`
`[18.a]
`
`[19.pre]
`
`[19.a]
`
`transmitting at least a portion of the
`
`second data from the cache memory via
`
`the network responsive to the read
`
`request being associated with a cache
`
`hit.
`
`
`
`Claim 18
`
`The apparatus of claim 13,
`
`further comprising storing fourth data
`
`at the cache memory, wherein the
`
`second data is indicated by the write
`
`command, and wherein the fourth data
`
`is indicated by a second write
`
`command received at the second
`
`interface.
`
`
`
`
`
`Claim 19
`
`An apparatus comprising:
`
`a first interface configured to receive
`
`input/output (I/O) traffic from a host
`
`computer via a dedicated I/O channel,
`
`the I/O traffic comprising one or more
`
`
`
`xx
`
`
`
`
`
`[19.b]
`
`[19.c]
`
`[19.d]
`
`[19.e]
`
`read commands, one or more write
`
`commands, or a combination thereof;
`
`a second interface configured to receive
`
`data via a network;
`
`a cache memory;
`
`a storage device; and
`
`a processor coupled via a
`
`communication path to the storage
`
`device, the processor configured to
`
`access the cache memory during
`
`processing of the I/O traffic,
`
`[19.f]
`
`the processor further configured to
`
`perform one or more access operations
`
`at the storage device based on the I/O
`
`traffic, wherein the communication
`
`path is distinct from the dedicated I/O
`
`channel.
`
`
`
`Claim 20
`
`[20.pre]
`
`The apparatus of claim 19,
`
`
`
`xxi
`
`
`
`
`
`[20.a]
`
`[21.pre]
`
`[21.a]
`
`[22.pre]
`
`[22.a]
`
`[23.pre]
`
`[23.a]
`
`
`
`wherein the dedicated I/O channel is
`
`associated with dedicated throughput
`
`that corresponds to the I/O traffic.
`
`
`
`Claim 21
`
`The apparatus of claim 19,
`
`wherein the I/O traffic is distinct from
`
`the data.
`
`
`
`Claim 22
`
`The apparatus of claim 19,
`
`wherein the data corresponds to one or
`
`more read requests, one or more write
`
`requests, or a combination thereof.
`
`
`
`Claim 23
`
`The apparatus of claim 19,
`
`wherein the storage device and the
`
`dedicated I/O channel are
`
`independently accessible.
`
`
`
`xxii
`
`
`
`
`
`[24.pre]
`
`[24.a]
`
`[24.b]
`
`[24.c]
`
`[24.d]
`
`[24.e]
`
`
`
`Claim 24
`
`An apparatus comprising:
`
`means for receiving input/output (I/O)
`
`traffic from a first host device via a
`
`dedicated I/O channel, the I/O traffic
`
`comprising a write command;
`
`means for receiving data via a network;
`
`
`means for short-term data storage;
`
`means for long-term data storage; and
`
`means for performing one or more
`
`access operations at the means for
`
`short-term data storage during
`
`processing of the I/O traffic and for
`
`performing one or more access
`
`operations at the means for long-term
`
`data storage based on the I/O traffic,
`
`the means for performing distinct from
`
`the dedicated I/O channel.
`
`
`
`xxiii
`
`
`
`
`
`I.
`
`INTRODUCTION
`
`Google LLC (“Google” or “Petitioner”) requests inter partes review (IPR)
`
`of claims 1-24 (the “Challenged Claims”) of U.S. Patent No. 10,154,092 (the “’092
`
`Patent”) assigned to LS Cloud Storage Technologies LLC (“PO”).
`
`The ’092 Patent relates to cached data storage systems and describes an
`
`apparatus and method in which host computers provide input to a cache memory or
`
`a disk storage device. The host may be a local host that accesses the cache or disk
`
`storage via a dedicated I/O channel, or a remote host that accesses the cache or
`
`disk storage via a network interface.
`
`As the ’092 Patent admits, such data storage and caching architectures were
`
`already well known in the art. “Numerous prior art systems and methods exist for
`
`managing cache memory in a data storage system,” and a “typical data processing
`
`system generally involves a cached data storage system that connects to local host
`
`computers via I/O channels or remote host computers via network links.” Ex.1001,
`
`1:56-58, 1:30-34. Indeed, U.S. Patent 6,173,374 to Heil discloses a data storage
`
`and caching architecture identical to that of the ’092 Patent that similarly provides
`
`for host access to cache memory and disk storage via either a dedicated I/O
`
`channel or a network interface.
`
`Google respectfully requests review and cancellation of the Challenged
`
`Claims based on the grounds as set forth below.
`
`
`
`1
`
`
`
`
`
`II. MANDATORY NOTICES
`
`A. Real Party-in-Interest
`
`Google LLC is the real party-in-interest for this petition.1
`
`B. Related Matters
`
`PO asserted the ’092 Patent against Petitioner and other parties in the
`
`following cases in the Waco Division of the Western District of Texas:
`
`● LS Cloud Storage Technologies, LLC v. Google LLC, 6:22-cv-00318 (W.D.
`
`Tex. 2022)
`
`o Transferred to the Austin Division as LS Cloud Storage Technologies,
`
`LLC v. Google LLC, 1:22-cv-00853 (W.D. Tex. 2022) by agreement
`
`of the parties on August 15, 2022
`
`● LS Cloud Storage Technologies, LLC v. Amazon.com, Inc., 6:22-cv-00316
`
`(W.D. Tex. 2022) (joint motion to transfer to the Austin Division granted
`
`October 31, 2022)
`
`● LS Cloud Storage Technologies, LLC v. Cisco Systems, Inc., 6:22-cv-00319
`
`(W.D. Tex. 2022)
`
`
`1 Google LLC is a subsidiary of XXVI Holdings Inc., which is a subsidiary of
`
`Alphabet Inc. XXVI Holdings Inc. and Alphabet Inc. are not real parties-in-interest
`
`to this proceeding.
`
`
`
`2
`
`
`
`
`
`o Dismissed and refiled as LS Cloud Storage Technologies, LLC v.
`
`Cisco Systems, Inc., 6:22-cv-00845 (W.D. Tex. 2022)
`
`● LS Cloud Storage Technologies, LLC v. Microsoft Corporation, 6:22-cv-
`
`00321 (W.D. Tex. 2022)
`
`o Transferred to the Austin Division as LS Cloud Storage Technologies,
`
`LLC v. Microsoft Corporation, 1:22-cv-00974 (W.D. Tex. 2022)
`
`Petitioner was served with the complaint on March 28, 2022.
`
`C. Counsel and Service
`
`Petitioner appoints the following lead and back-up counsel:
`
`Lead Counsel
`
`Back-up Counsel
`
`James T. Carmichael
`Reg. No. 45,306
`
`Carmichael IP, PLLC
`8000 Towers Crescent Drive
`13th Floor
`Tysons Corner, VA 22182
`Tel: 703-646-9255
`Email: jim@carmichaelip.com
`
`Minghui Yang
`Reg. No. 71,989
`
`Carmichael IP, PLLC
`8000 Towers Crescent Drive
`13th Floor
`Tysons Corner, VA 22182
`Tel: 703-646-9255
`Email: mitch@carmichaelip.com
`
`Petitioner consents to service by electronic mail at the following addresses:
`
`jim@carmichaelip.com;
`
`mitch@carmichaelip.com; and
`
`Google-LS-Cloud-IPR@Carmichaelip.com.
`
`3
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`D.
`
`Power of Attorney
`
`A power of attorney is filed herewith in accordance with 37 C.F.R. §
`
`42.10(b).
`
`E.
`
`Fees
`
`Petitioner concurrently electronically submits the required fees for this
`
`Petition.
`
`III.
`
`REQUIREMENTS FOR INTER PARTES REVIEW
`
`A. Grounds for Standing
`
`Petitioner certifies that the ’092 Patent is available for IPR, and that
`
`Petitioner is not barred or estopped from requesting this IPR.
`
`B.
`
`Identification of Challenge and Relief Requested
`
`Petitioner requests cancellation of the Challenged Claims on the following
`
`grounds:
`
`Ground 1: Anticipation of claims 1-3, 7-12, and 19-23 by U.S. Patent
`
`6,173,374 (“Heil”) issued January 9, 2001, under 35 U.S.C. § 102(e);
`
`Ground 2: Anticipation of claims 10 and 11 by Heil under 35 U.S.C. §
`
`102(b);
`
`Ground 3: Obviousness of claims 1-3 and 6-24 based on Heil and U.S.
`
`Patent 5,920,893 (“Nakayama”) issued July 6, 1999, under 35 U.S.C. § 103(a);
`
`
`
`4
`
`
`
`
`
`Ground 4: Obviousness of claim 4 based on Heil, Nakayama, and U.S.
`
`Patent 5,692,211 (“Gulick”) issued November 25, 1997, under 35 U.S.C. § 103(a);
`
`and
`
`Ground 5: Obviousness of claim 5 based on Heil, Nakayama, and U.S.
`
`Patent 6,118,776 (“Berman”) issued September 12, 2000, under 35 U.S.C. §
`
`103(a).
`
`Each ground is supported by the Declaration of Dr. Paul Franzon, Ph.D., an
`
`expert in the field of computer networking and cache management. None of the
`
`prior art used in any of the grounds was cited during prosecution.
`
`As explained in Section V, the ’092 Patent claims priority through a chain of
`
`applications, the earliest of which (U.S. Application No. 09/236,409) has a filing
`
`date of January 22, 1999. The written description support for claims 10 and 11 of
`
`the ’092 Patent, however, was not included in the original specification of the ’409
`
`Application. Rather, it was introduced as new matter during the prosecution of the
`
`’409 Application. Because “[n]o amendment shall introduce new matter into the
`
`disclosure of the invention,” claims 10 and 11 are not entitled to claim the January
`
`22, 1999, priority date of the ’409 Application. 35 U.S.C. § 132. Instead, claims 10
`
`and 11 have a priority date no earlier than the March 5, 2003 filing date of U.S.
`
`Application No. 10/382,016, the first child application of the ’409 Application in
`
`
`
`5
`
`
`
`
`
`the ’092 Patent’s priority chain having the ’409 Application’s new matter in its
`
`original specification.
`
`For all claims, Heil, Nakayama, and Berman are prior art pursuant to at least
`
`(pre-AIA) 35 U.S.C. § 102(e). Gulick is prior art pursuant to (pre-AIA) 35 U.S.C.
`
`§ 102(b). To the extent that the ’409 Application’s new matter does not entitle
`
`claims 10 and 11 to the ’409 Application’s January 22, 1999 priority date, Heil and
`
`Nakayama further qualify as prior art under (pre-AIA) 35 U.S.C. § 102(b).
`
`IV. THE ’092 PATENT
`
`The ’092 Patent relates to cached data storage systems and describes an
`
`apparatus and method in which host computers provide input to a cache memory or
`
`a disk storage device. Ex.1001, abstract. Figure 1 shows the configuration of the
`
`preferred embodiment in which hosts 111 and 112 are connected via I/O channels
`
`121 and 122 respectively to a PC data storage system 131. Ex.1001, 5:9-16. PC
`
`data storage system 131 includes a cache memory managed by a cache manager as
`
`well as disks 161 and 162. Ex.1001, 5:25-34. When the host accesses the cache or
`
`storage
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
