IP Library Granted Patent US 11,232,080
Granted Patent B2
US 11,232,080 · App. 16/544,817 · Granted Jan 25, 2022

Systems and methods for providing access to a data file stored at a data storage system

Inventors: Joshua Danziger (Metchen, NJ); Alissa Feldman (New York, NY); Lai Kwan Wong (New York, NY)
Assignee: Google LLC
G06F16/183G06F8/61G06F8/65G06F16/10G06F16/172H04L67/02H04L67/06H04L67/1097
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 11,232,080
App. No.
16/544,817
Granted
Jan 25, 2022
Kind
B2
Abstract

An application server receives from a user device a first request to create a data file that is to be stored at a third-party storage server. Responsive to receiving the first request to create a data file that is to be stored at the third-party storage server, the application server sends to the third-party storage server a second request indicating that the data file is to be created at the third-party storage server. An indication that the data file has been created at the third-party storage server is received from the third-party storage server. Responsive to receiving the indication that the data file has been created at the third-party storage server, the application server generates an instance of the data file that is stored at the application server. The application server provides to the user device the instance of the data file for edit via a relevant application.

Claims (40)

1. A method comprising:

receiving, at an application server hosting a plurality of applications and from a user device, a first request to create a data file that is to be stored at a third-party storage server;

responsive to receiving the first request to create the data file that is to be stored at the third-party storage server, sending, by the application server and to the third-party storage server, a second request indicating that the data file is to be created at the third-party storage server;

receiving, from the third-party storage server, an indication that the data file has been created at the third-party storage server;

responsive to receiving the indication that the data file has been created at the third-party storage server, generating, by the application server, an instance of the data file that is stored at the application server; and

providing, by the application server and to the user device, the instance of the data file for edit via a relevant application of the plurality of applications hosted by the application server.

2. The method of claim 1 , further comprising:

uploading, by the application server and to the third-party storage server, a latest version of the data file stored at the application server.

3. The method of claim 2 , wherein the application server periodically uploads the latest version of the data file stored at the application server to the third-party storage server via an application programming interface (API) that operates under Hypertext Transfer Protocol (HTTP).

4. The method of claim 1 , wherein the first request to create the data file that is to be stored at the third-party storage server comprises a Hypertext Transfer Protocol (HTTP) message that was generated at the user device within a display area of a browser-based application, the display area defined by a structural tag associated with the browser-based application.

5. The method of claim 1 , wherein the first request comprises an access token issued by the third-party storage server for the user device, wherein the access token grants access to the data file for the user device.

6. The method of claim 1 , wherein the second request comprises a file identifier, a file name, and an indication that no content for the data file exists at the application server.

7. The method of claim 1 , wherein receiving the indication that the data file has been created at the third-party storage server comprises receiving metadata associated with the data file created at the third-party storage server.

8. A system comprising:

a memory; and

a processor, coupled to the memory, to:

receive, at an application server hosting a plurality of applications and from a user device, a first request to create a data file that is to be stored at a third-party storage server;

responsive to receiving the first request to create the data file that is to be stored at the third-party storage server, send, by the application server and to the third-party storage server, a second request indicating that the data file is to be created at the third-party storage server;

receive, from the third-party storage server, an indication that the data file has been created at the third-party storage server;

responsive to receiving the indication that the data file has been created at the third-party storage server, generate, by the application server, an instance of the data file that is stored at the application server; and

provide, by the application server and to the user device, the instance of the data file for edit via a relevant application of the plurality of applications hosted by the application server.

9. The system of claim 8 , the processor further to:

upload, by the application server and to the third-party storage server, a latest version of the data file stored at the application server.

10. The system of claim 9 , wherein the application server to periodically upload the latest version of the data file stored at the application server to the third-party storage server via an application programming interface (API) that operates under Hypertext Transfer Protocol (HTTP).

11. The system of claim 8 , wherein the first request to create the data file that is to be stored at the third-party storage server comprises a Hypertext Transfer Protocol (HTTP) message that was generated at the user device within a display area of a browser-based application, the display area defined by a structural tag associated with the browser-based application.

12. The system of claim 8 , wherein the first request comprises an access token issued by the third-party storage server for the user device, wherein the access token grants access to the data file for the user device.

13. The system of claim 8 , wherein the second request comprises a file identifier, a file name, and an indication that no content for the data file exists at the application server.

14. The system of claim 8 , wherein to receive the indication that the data file has been created at the third-party storage server comprises receiving metadata associated with the data file created at the third-party storage server.

15. A non-transitory computer-readable medium comprising instructions that, responsive to execution by a processor, cause the processor to perform operations comprising:

receiving, at an application server hosting a plurality of applications and from a user device, a first request to create a data file that is to be stored at a third-party storage server;

responsive to receiving the first request to create the data file that is to be stored at the third-party storage server, sending, by the application server and to the third-party storage server, a second request indicating that the data file is to be created at the third-party storage server;

receiving, from the third-party storage server, an indication that the data file has been created at the third-party storage server;

responsive to receiving the indication that the data file has been created at the third-party storage server, generating, by the application server, an instance of the data file that is stored at the application server; and

providing, by the application server and to the user device, the instance of the data file for edit via a relevant application of the plurality of applications hosted by the application server.

16. The non-transitory computer-readable medium of claim 15 , further comprising:

uploading, by the application server and to the third-party storage server, a latest version of the data file stored at the application server.

17. The non-transitory computer-readable medium of claim 16 , wherein the application server periodically uploads the latest version of the data file stored at the application server to the third-party storage server via an application programming interface (API) that operates under Hypertext Transfer Protocol (HTTP).

18. The non-transitory computer-readable medium of claim 15 , wherein the first request to create the data file that is to be stored at the third-party storage server comprises a Hypertext Transfer Protocol (HTTP) message that was generated at the user device within a display area of a browser-based application, the display area defined by a structural tag associated with the browser-based application.

19. The non-transitory computer-readable medium of claim 15 , wherein the first request comprises an access token issued by the third-party storage server for the user device, wherein the access token grants access to the data file for the user device.

20. The non-transitory computer-readable medium of claim 15 , wherein receiving the indication that the data file has been created at the third-party storage server comprises receiving metadata associated with the data file created at the third-party storage server.

Assignments (2)
CHANGE OF NAME Recorded Aug 22, 2019
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 050149/0333 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 20, 2019
From: DANZIGER, JOSHUA; FELDMAN, ALISSA; WONG, LAI KWAN
To: GOOGLE INC.
Reel/Frame 050103/0618 →
Continuity (2)
Continuation 15433815 · Feb 15, 2017
Related Publication 20190370228A1 · Dec 5, 2019