IP Library › Granted Patent US 12,238,170
Granted Patent B2
US 12,238,170 · App. 18/360,884 · Granted Feb 25, 2025

On demand serverless container based storage transfer

Inventors: Alankrit Kharbanda (Seattle, WA); Shyam Venkataraman (San Jose, CA); Sowmya Dayanand (Redmond, WA); Xiangqian Yu (Fremont, CA); Juan Esteller (Mountain View, CA)
Assignee: Google LLC
H04L67/1097H04L63/0823H04L67/06
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,238,170
App. No.
18/360,884
Granted
Feb 25, 2025
Kind
B2
Abstract

A method for on demand serverless container based storage transfer includes receiving a request to transfer data from a first device to a second device, the first device hosted at a private cloud, the private cloud isolated from the Internet. The method includes determining that the first device is communicatively connected to the private cloud. The method also includes, in response to determining that the first device is communicatively connected to the private cloud, instantiating a container at the first device, the container configured to receive the data from the first device without directly accessing a local storage of the first device. The method includes transferring, using the container, the data from the first device to the second device.

Claims (36)

1. A computer-implemented method executed by data processing hardware that causes the data processing hardware to perform operations comprising:

receiving a request to transfer data from a first device to a second device, the first device hosted at a private cloud, the private cloud isolated from the Internet, the first device comprising a portable device;

determining that the first device is communicatively connected to the private cloud;

in response to determining that the first device is communicatively connected to the private cloud, instantiating a container at the first device using a first certificate authority (CA) certificate, wherein the container is configured to receive the data from the first device without the container or the data processing hardware directly accessing a local storage of the first device, and wherein the container is further configured to transfer the data from the first device to the second device using a second CA certificate.

2. The method of claim 1 , wherein the second device is hosted at the private cloud.

3. The method of claim 2 , wherein the second device comprises a data center.

4. The method of claim 3 , wherein the first device comprises an edge device of the private cloud, wherein the edge device comprises one or more of:

a drone;

a smart phone;

a laptop; or

an on-board computer of a vehicle.

5. The method of claim 1 , wherein the second device is not hosted at the private cloud.

6. The method of claim 5 , wherein:

the operations further comprise determining that the first device is communicatively coupled to the second device via a network; and

instantiating the container at the first device is in response to determining that the first device is communicatively coupled to the second device via the network.

7. The method of claim 6 , wherein the network comprises an Internet connection.

8. The method of claim 1 , wherein the operations further comprise, prior to determining that the first device is communicatively connected to the private cloud, determining that the first device is not communicatively connected to the private cloud, wherein determining that the first device is communicatively connected to the private cloud comprises determining that the first device has become communicatively connected to the private cloud after determining that the first device is not communicatively connected to the private cloud.

9. A system comprising:

data processing hardware; and

memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:

receiving a request to transfer data from a first device to a second device, the first device hosted at a private cloud, the private cloud isolated from the Internet, the first device comprising a portable device;

determining that the first device is communicatively connected to the private cloud;

in response to determining that the first device is communicatively connected to the private cloud, instantiating a container at the first device using a first certificate authority (CA) certificate, wherein the container is configured to receive the data from the first device without the container or the data processing hardware directly accessing a local storage of the first device, and wherein the container is further configured to transfer the data from the first device to the second device using a second CA certificate.

10. The system of claim 9 , wherein the second device is hosted at the private cloud.

11. The system of claim 10 , wherein the second device comprises a data center.

12. The system of claim 11 , wherein the first device comprises an edge device of the private cloud, wherein the edge device comprises one or more of:

a drone;

a smart phone;

a laptop; or

an on-board computer of a vehicle.

13. The system of claim 9 , wherein the second device is not hosted at the private cloud.

14. The system of claim 13 , wherein:

the operations further comprise determining that the first device is communicatively coupled to the second device via a network; and

instantiating the container at the first device is in response to determining that the first device is communicatively coupled to the second device via the network.

15. The system of claim 14 , wherein the network comprises an Internet connection.

16. The system of claim 9 , wherein the operations further comprise, prior to determining that the first device is communicatively connected to the private cloud, determining that the first device is not communicatively connected to the private cloud, wherein determining that the first device is communicatively connected to the private cloud comprises determining that the first device has become communicatively connected to the private cloud after determining that the first device is not communicatively connected to the private cloud.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 6, 2023
From: KHARBANDA, ALANKRIT; VENKATARAMAN, SHYAM; DAYANAND, SOWMYA; YU, XIANGQIAN; ESTELLER, JUAN
To: GOOGLE LLC
Reel/Frame 065778/0001 →
Continuity (1)
Related Publication 20250039260A1 · Jan 30, 2025
References Cited (9)
US 9596189B1 · Lea · 2017 [cited by examiner]
US RE48714E · Crouchman · 2021 [cited by examiner]
US 20100332820A1 · Matsushima · 2010 [cited by examiner]
US 20150304417A1 · Tan · 2015 [cited by examiner]
US 20150334070A1 · Dinardo, Jr. et al. · 2015 [cited by applicant]
US 20220407907A1 · Cheng · 2022 [cited by examiner]
CN 115473891A · 2022 [cited by applicant]
CN 114844744B · 2023 [cited by applicant]
International Search Report and Written Opiniion issued in related PCT Application No. PCT/US2024/039929, dated Dec. 6, 2024. [cited by applicant]