IPR2023-00120, No. 1018 Exhibit - Infringement Contentions served in LS Cloud v Google (P.T.A.B. Nov. 2, 2022)

Infringement Chart for US 10,154,092 vs. Google
`
`Claim Language
`1. An apparatus
`comprising:
`
`Cloud Storage is an apparatus
`
` Google Evidence
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`a first interface
`configured to
`receive
`input/output (I/O)
`
` Cloud Storage has a first interface configured to receive input/output (I/O) traffic from a first host
`device via a dedicated I/O channel (traffic from a host device (on-premises sources ), the I/O
`traffic comprising a read command
`
`1
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 1 of 62
`
`

`traffic from a first
`host device via a
`dedicated I/O
`channel, the I/O
`traffic comprising a
`read command;
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`2
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 2 of 62
`
`

`
`Dedicated Interconnect overview
`Source: https://cloud.google.com/storage-transfer/docs/on-prem-overview
`
`
`
`
`
`Google Storage Transfer Service receive first data (data from online sources) via a network
`
`
`
`a second interface
`configured to
`receive first data
`via a network;
`
`
`
`3
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 3 of 62
`
`

`
`
`
`
`
`Storage Transfer Service | Google Cloud
`Source: https://cloud.google.com/storage-transfer-service#storage-transfer-service
`
`
`
`
`
`
`
`
`4
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 4 of 62
`
`

`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`5
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 5 of 62
`
`

`Source: https://youtu.be/sBNtvg5D2CM?t=154
`
`
`
`
`
`
`a cache memory
`configured to store
`second data;
`
`
`Cloud Storage comprises a cache memory configured to store second data
`
`
`
`
`
`
`
`
`6
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 6 of 62
`
`

`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`
`
`a storage device
`configured to store
`third data; and
`
`that a storage bucket is empty.
`
`
`
`
`
`
`
`7
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 7 of 62
`
`

`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the transfer process is complete.
`
`
`
`
`
`
`
`
`
`8
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 8 of 62
`
`

`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the data is stored in the storage bucket after completion of transfer process, which appears to relate to
`“storing third data at a storage device” as claimed.
`
`
`
`
`9
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 9 of 62
`
`

`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
`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=191
`
`Cloud Storage comprises a processor(Console is operated bt a processor) coupled to the cache
`memory
`
`
`
`
`
`10
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 10 of 62
`
`

`processing of the
`I/O traffic, the
`processor further
`configured to
`perform an access
`operation at the
`storage device
`based on the I/O
`traffic.
`
`
`Source :https://cloud.google.com/storage/docs/introduction
`
`The request to transfer data is received via a dedicated channel and actual data from S3 is received at the google
`cloud storage via internet. Further the data received from S3 is loaded into cache memory and then written into
`cloud storage bucket. Therefore, it is evident that the path used for writing data into storage bucket is different
`(the Processor uses fast memory (i.e. cache memory) for processing the various functions which are used to
`complete the process of transfer of data from S3 to GCS)
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`The dedicated I/O channel is associated with dedicated throughput that corresponds to the I/O
`traffic, for example, the channel from application server to client is the dedicated I/O channel
`associated with dedicated throughput corresponds to the I/O traffic.
`
`
`
`11
`
`
`2. The apparatus
`of claim 1, wherein
`the dedicated I/O
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 11 of 62
`
`

`channel is
`associated with
`dedicated
`throughput that
`corresponds to the
`I/O traffic.
`
`
`Dedicated Interconnect overview
`Source: https://cloud.google.com/storage-transfer/docs/on-prem-overview
`
`
`Cloud Storage comprises a second interface configured to receive first data via a network. Since
`receive first data via a network, not between computers and storage just as the I/O traffic, the I/O
`traffic is distinct from the first data.
`
`
`
`
`
`
`3. The apparatus
`of claim 1, wherein
`the I/O traffic is
`distinct from the
`first data.
`
`
`
`12
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 12 of 62
`
`

`
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`The second interface comprises an Ethernet interface
`
`13
`
`
`5. The apparatus
`of claim 1, wherein
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 13 of 62
`
`

`the second
`interface
`comprises an
`Ethernet interface
`or an
`asynchronous
`transfer mode
`(ATM) interface.
`
`
`6. The apparatus
`of claim 1, wherein
`the I/O traffic
`further comprises
`a write command.
`
`
`
`
`
`
`Storage Transfer Service | Google Cloud
`Source: https://cloud.google.com/storage-transfer-service#storage-transfer-service
`
`
`The I/O traffic comprising a write command (access data include read and write)
`
`
`
`
`14
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 14 of 62
`
`

`
`Source: https://cloud.google.com/appengine/docs/standard/go111/googlecloudstorageclient/read-write-to-cloud-
`storage
`
`the first data comprises a second read request, a write request, or a combination thereof
`
`
`15
`
`
`7. The apparatus
`of claim 1, wherein
`the first data
`comprises a
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 15 of 62
`
`

`second read
`request, a write
`request, or a
`combination
`thereof.
`
`
`8. The apparatus
`of claim 1, wherein
`the network
`comprises a
`plurality of
`interconnected
`computing
`devices.
`
`Source: https://cloud.google.com/bigtable/docs/writes
`
`
`
`
`
`The network comprises a plurality of interconnected computing devices
`
`
`
`
`
`16
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 16 of 62
`
`

`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`the storage device (from host to storage area) and the dedicated I/O channel (from Appliance
`server to client) are independently accessible
`
`
`17
`
`
`9. The apparatus
`of claim 1, wherein
`the storage device
`and the dedicated
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 17 of 62
`
`

`I/O channel are
`independently
`accessible, 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.
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`
`
`18
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 18 of 62
`
`

`the processor is configured to read at least a portion of the second data from the cache memory
`based on the read command
`
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`
`The host device comprises a server
`
`
`
`
`19
`
`
`12. The apparatus
`of claim 1, wherein
`the host device
`comprises a
`server.
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 19 of 62
`
`

`
`Source: https://cloud.google.com/storage
`
`
`
`
`13. A method
`comprising:
`
`
`Google Storage Transfer Service is a service(method) for transferring data from cloud or on-
`premises sources
`
`
`
`
`Overview | Cloud Storage Transfer Service Documentation | Google Cloud
`Source: https://cloud.google.com/storage-transfer/docs/overview
`
`
`
`
`
`
`20
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 20 of 62
`
`

`
`
`
`
`
` Google Storage Transfer Service input/output (I/O) traffic from a host device (on-premises
`sources)
`
`
`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;
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`
`
`
`
`
`21
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 21 of 62
`
`

`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`traffic from a host device (on-premises sources) via a dedicated I/O channel (Dedicated
`Interconnect Work) at a first interface.
`
`
`
`
`
`Dedicated Interconnect overview
`Source: https://cloud.google.com/storage-transfer/docs/on-prem-overview
`
`
`
`
`
`
`
`22
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 22 of 62
`
`

`
`
`
`
`Introducing Storage Transfer Service for on-premises data
`Source: https://cloud.google.com/blog/products/storage-data-transfer/introducing-storage-transfer-service-for-
`on-premises-data
`
`
`
`When user clicks on the create button highlighted with red rectangle in the figure 2. An I/O command is
`received by the processor of allocated cloud machine to transfer data from any other cloud to a bucket of
`google platform cloud, which appears to relate to “receiving input/output (I/O)” the purpose of the
`create command is to load files into google cloud storage bucket, which appears to relate to write command.
`
`
`
`
`
`
`23
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 23 of 62
`
`

`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=154
`
`
`
`Google Storage Transfer Service receive first data (data from online sources) via a network
`
`
`
`receiving first data
`via a network at a
`second interface;
`
`
`
`24
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 24 of 62
`
`

`
`
`
`
`
`Storage Transfer Service | Google Cloud
`Source: https://cloud.google.com/storage-transfer-service#storage-transfer-service
`
`
`
`
`
`
`
`
`25
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 25 of 62
`
`

`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`26
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 26 of 62
`
`

`Source: https://youtu.be/sBNtvg5D2CM?t=154
`
`
`
`
`
`
`
`
`storing second
`data at a cache
`memory;
`
`
`During the execution of this service all data and commands received on google cloud platform are processed
`only after loading into fast memory (like cache) as evident from code of a
`Function Shown below, Hence, getting the files from Amazon S3 and printing file name in Google Cloud
`Platform bucket appears to relate to “second data” as claimed.
`
`
`
`
`27
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 27 of 62
`
`

`
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`28
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 28 of 62
`
`

`storing third data
`at a storage
`device;
`
`that a storage bucket is empty.
`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`
`
`the transfer process is complete.
`
`
`
`
`
`29
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 29 of 62
`
`

`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the data is stored in the storage bucket after completion of transfer process, which appears to relate to
`“storing third data at a storage device” as claimed.
`
`
`
`
`30
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 30 of 62
`
`

`
`Source: https://youtu.be/sBNtvg5D2CM?t=191
`During the execution of this service all data and commands received on google cloud platform are processed
`only after loading into fast memory (like cache) as evident from codes I/O function in the follow evidence
`
`
`
`
`
`
`accessing the
`cache memory
`during processing
`of the I/O traffic;
`and
`
`
`
`31
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 31 of 62
`
`

`
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`The request to transfer data from amazon’s S3 is received via a dedicated channel and actual data
`from S3 is received at the google cloud storage via internet. Further the data received from S3 is loaded into
`cache memory and then written into cloud storage bucket. Therefore, it is evident that the path used for
`writing data into storage bucket is different (the Processor uses fast memory (i.e. cache memory) for
`processing the various functions which are used to complete the process of transfer of data from S3 to GCS)
`
`32
`
`performing one or
`more access
`operations at the
`storage device
`based on the I/O
`traffic, the one or
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 32 of 62
`
`

`more access
`operations utilizing
`a communication
`path between a
`processor and the
`storage device, the
`communication
`path distinct from
`the dedicated I/O
`channel.
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`
`
`
`
`
`
`
`14. The method
`of claim 13,
`wherein the I/O
`traffic is distinct
`from the first data.
`
`
`Cloud Storage comprises a second interface configured to receive first data via a network. Since
`receive first data via a network, not between computers and storage just as the I/O traffic, the I/O
`traffic is distinct from the first data.
`
`
`
`
`
`33
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 33 of 62
`
`

`
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`The storage device (from host to storage area) and the dedicated I/O channel (from Appliance
`server to client) are independently accessible
`
`34
`
`
`15. The method
`of claim 13, further
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 34 of 62
`
`

`
`
`comprising
`performing a first
`access operation
`at the storage
`device
`independently of
`the dedicated I/O
`channel.
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`
`
`35
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 35 of 62
`
`

`the processor is configured to read at least a portion of the second data from the cache memory
`based on the read command
`
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`
`
`
`the second data is written at the cache memory in response to the write command.
`
`
`
`36
`
`
`16. The method
`of claim 13,
`wherein the
`second data is
`written at the
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 36 of 62
`
`

`cache memory in
`response to the
`write command.
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=154
`
`
`
`
`
`19. An apparatus
`comprising:
`
`
`Cloud Storage is an apparatus
`
`
`
`
`
`
`37
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 37 of 62
`
`

`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`Cloud Storage has a first interface configured to receive input/output (I/O) traffic from a first host
`device via a dedicated I/O channel (traffic from a host device (on-premises sources ), the I/O
`traffic comprising a read command
`
`
`
`
`38
`
`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
`one or more read
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 38 of 62
`
`

`commands, one or
`more write
`commands, or a
`combination
`thereof;
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`39
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 39 of 62
`
`

`
`Dedicated Interconnect overview
`Source: https://cloud.google.com/storage-transfer/docs/on-prem-overview
`
`Google Storage Transfer Service receive first data (data from online sources) via a network
`
`
`
`a second interface
`configured to
`receive first data
`via a network;
`
`
`
`40
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 40 of 62
`
`

`
`
`
`
`
`Storage Transfer Service | Google Cloud
`Source: https://cloud.google.com/storage-transfer-service#storage-transfer-service
`
`
`
`
`
`
`
`
`41
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 41 of 62
`
`

`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`42
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 42 of 62
`
`

`Source: https://youtu.be/sBNtvg5D2CM?t=154
`
`
`
`
`
`
`a cache memory;
`
`
`Cloud Storage comprises a cache memory
`
`
`
`
`
`
`
`43
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 43 of 62
`
`

`a storage device;
`and
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`a storage bucket is empty.
`
`
`
`
`
`
`
`44
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 44 of 62
`
`

`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the transfer process is complete.
`
`
`
`
`
`
`
`
`
`45
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 45 of 62
`
`

`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the data is stored in the storage bucket after completion of transfer process, which appears to relate to “at a
`storage device” as claimed.
`
`
`
`
`46
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 46 of 62
`
`

`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, the
`processor further
`configured to
`perform one or
`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=191
`
`Cloud Storage comprises a processor(Console is operated bt a processor) coupled to the cache
`memory
`
`
`
`
`
`47
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 47 of 62
`
`

`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.
`
`
`Source :https://cloud.google.com/storage/docs/introduction
`
`The request to transfer data is received via a dedicated channel and actual data from S3 is received at the google
`cloud storage via internet. Further the data received from S3 is loaded into cache memory and then written into
`cloud storage bucket. Therefore, it is evident that the path used for writing data into storage bucket is different
`(the Processor uses fast memory (i.e. cache memory) for processing the various functions which are used to
`complete the process of transfer of data from S3 to GCS)
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`The dedicated I/O channel is associated with dedicated throughput that corresponds to the I/O
`traffic, for example, the channel from application server to client is the dedicated I/O channel
`associated with dedicated throughput corresponds to the I/O traffic.
`
`
`
`48
`
`
`20. The apparatus
`of claim 19,
`wherein the
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 48 of 62
`
`

`dedicated I/O
`channel is
`associated with
`dedicated
`throughput that
`corresponds to the
`I/O traffic.
`
`
`
`
`Dedicated Interconnect overview
`Source: https://cloud.google.com/storage-transfer/docs/on-prem-overview
`
`
`
`Cloud Storage comprises a second interface configured to receive first data via a network. Since
`receive data via a network, not between computers and storage just as the I/O traffic, the I/O
`traffic is distinct from the data.
`
`
`
`
`21. The apparatus
`of claim 19,
`wherein the I/O
`traffic is distinct
`from the data.
`
`
`
`49
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 49 of 62
`
`

`
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`The data corresponds to one or more read request, a write request, or a combination(access)
`thereof
`
`
`50
`
`
`22. The apparatus
`of claim 19,
`wherein the data
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 50 of 62
`
`

`
`
`corresponds to
`one or more read
`requests, one or
`more write
`requests, or a
`combination
`thereof.
`
`
`
`
`
`Source: https://cloud.google.com/bigtable/docs/writes
`
`The storage device (from host to storage area) and the dedicated I/O channel (from Appliance
`server to client) are independently accessible
`
`
`
`23. The apparatus
`of claim 19,
`wherein the
`storage device and
`the dedicated I/O
`channel are
`independently
`accessible.
`
`
`
`51
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 51 of 62
`
`

`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`52
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 52 of 62
`
`

`24. An apparatus
`comprising:
`
`
`Cloud Storage is an apparatus
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`Cloud Storage has a first interface configured to receive input/output (I/O) traffic from a first host
`device via a dedicated I/O channel (traffic from a host device (on-premises sources ), the I/O
`traffic comprising a read command
`
`
`
`
`53
`
`means for
`receiving
`input/output (I/O)
`traffic from a first
`host device via a
`dedicated I/O
`channel, the I/O
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 53 of 62
`
`

`traffic comprising a
`write command;
`
`
`
`Cloud Storage as a data lake | Cloud Architecture Center | Google Cloud
`Source: https://cloud.google.com/architecture/build-a-data-lake-on-gcp
`
`
`
`
`
`
`
`54
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 54 of 62
`
`

`
`Dedicated Interconnect overview
`Source: https://cloud.google.com/storage-transfer/docs/on-prem-overview
`
`Google Storage Transfer Service receive data (data from online sources) via a network
`
`
`
`means for
`receiving data via a
`network;
`
`
`
`55
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 55 of 62
`
`

`
`
`
`
`
`Storage Transfer Service | Google Cloud
`Source: https://cloud.google.com/storage-transfer-service#storage-transfer-service
`
`
`
`
`
`
`means for short-
`term data storage;
`
`
`Cloud Storage comprises a cache memory (means for short-term data storage)
`
`
`
`
`
`56
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 56 of 62
`
`

`
`
`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`means for long-term data storage
`
`
`
` a
`
`
`
`
` storage bucket is empty.
`
`means for long-
`term data storage;
`and
`
`
`
`57
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 57 of 62
`
`

`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the transfer process is complete.
`
`
`
`
`
`
`
`
`
`58
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 58 of 62
`
`

`
`
`
`
`Source: https://youtu.be/sBNtvg5D2CM?t=105
`
`
`
`the data is stored in the storage bucket after completion of transfer process, which appears to relate to
`“means for long-term data storage ” as claimed.
`
`
`
`
`59
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 59 of 62
`
`

`
`Source: https://youtu.be/sBNtvg5D2CM?t=191
`
`Means (console) 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.
`
`
`
`
`
`60
`
`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
`
`
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 60 of 62
`
`

`storage based on
`the I/O traffic, the
`means for
`performing distinct
`from the dedicated
`I/O channel.
`
`
`Source :https://cloud.google.com/storage/docs/introduction
`
`The request to transfer data is received via a dedicated channel and actual data from S3 is received at the google
`cloud storage via internet. Further the data received from S3 is loaded into cache memory and then written into
`cloud storage bucket. Therefore, it is evident that the path used for writing data into storage bucket is different
`(the Processor uses fast memory (i.e. cache memory) for processing the various functions which are used to
`complete the process of transfer of data from S3 to GCS)
`
`
`
`
`
`61
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 61 of 62
`
`

`
`Source: https://cloud.google.com/storage/docs/migrating
`
`
`
`
`
`
`
`
`
`
`62
`
`Google Exhibit 1018
`Google v. LS Cloud Storage Technologies
`IPR2023-00120, Page 62 of 62
`
`

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

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.

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

Supplemental Search

Search for PTAB Motions

PTAB Analytics

TTAB Analytics

Basic Search

Filters

Party Search

Advanced

Selected Courts

Recently Selected Courts

Find PTAB Decisions

PTAB Analytics

Special PTAB Alerts

Orange Book

Directly Search Federal Courts

Search Trademark ...

This document is available on Docket Alarm but you must sign up to view it.

Accessing this document will incur an additional charge of $.

Still Working On It

A few More Minutes ... Still Working

This document could not be displayed.

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.

One Moment Please

Your document is on its way!

Sealed Document

We are redirecting youto a mobile optimized page.

Document Unreadable or Corrupt

We are unable to display this document.

STEP 2 of 2

Choose your membership type

Flat-Fee

Pay-As-You-Go

Add your payment information

Login or Join

Enter your corporate Email

Thousands of your peers are saving time and gaining a competitive advantage with Docket Alarm.

Join Docket Alarm to perform smarter legal research.

Download this document and millions of others instantly with a Docket Alarm membership.

Join Docket Alarm and start performing smarter legal research.

Start tracking this docket instantly with a Docket Alarm membership.

Join thousands of your peers and start performing smarter legal research.

STEP 1 of 2

Millions of Documents | 15 Seconds to Signup

Hi !

Welcome to Docket Alarm

Welcome to Docket Alarm!

Explore Litigation Insights andManage Your Cases

Reset Password

What is PACER?

Why do I need it?

What will I be charged?

Do other courts have fees?

Basic Free Access

Welcome

Thank you

Check Firm Account

We are redirecting you
to a mobile optimized page.

Explore Litigation Insights and
Manage Your Cases