Systems and methods for incremental loading of collaboratively generated presentations

• US 9,946,725 B1
• Filed: 08/26/2016
• Issued: 04/17/2018
• Est. Priority Date: 10/17/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Saviano, Steven Joseph, Kopylov, Igor
• Primary Examiner(s): Sall, El Hadji
• Application Number:
  US15/248,986
• Time in Patent Office: 599 Days
• Field of Search: 709203, 709217, 709219, 709224
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/1794 Details of file format conversion
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2147 Locking files
• CPC Class Codes: G06F 40/131 Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Systems and methods for incrementally communicating a document to a client computer are disclosed herein. Time consistent views of the document are maintained throughout the incremental downloading through use of a cryptographically secured permissions token identifying a version of the document the user is permitted to access.

Claims

1. A method of collaborative document editing, the method comprising:

receiving, at a server from a client system, a first request to access a document stored at the server;

providing, by the server, to the client system, an application in a browser of the client system, wherein the application is enabled to modify the document;

providing, by the server, to the client system, a first portion of the document in the application;

receiving, by the server, a second request to access the document;

determining, by the server, whether a user that is associated with the second request is authorized to access the document;

in response to determining that the user is authorized to access the document, transmitting, by the server, a second portion of the document;

receiving an edit to at least one of the first portion of the document or the second portion of the document;

and

saving, by the server, the edit to the at least one of the first portion of the document or the second portion of the document.

2. The method of claim 1, wherein the application is distributed over the server and the client system.

3. The method of claim 1, wherein the first request to access the document comprises at least one of a user identifier, a file identifier or a version identifier.

4. The method of claim 1, wherein in response to determining that the user is not authorized to access the document transmitting an error message.

5. The method of claim 1, wherein the second request comprises at least one of a user identifier, document identifier, portion identifier, or a version identifier.

6. The method of claim 5, wherein determining whether the user is authorized to access the document comprises:

calculating a hash of the user identifier, the file identifier and the version identifier; and

comparing a stored cryptographic hash with the generated hash.

7. The method of claim 1, wherein transmitting the second portion of the document comprises sending an indication that the second portion of the document has been modified.

8. The method of claim 1, further comprising:

saving to the server an unedited version of the document.

9. The method of claim 8, further comprising:

providing different versions of the document to the user and a different user, based on user type, wherein;

an editor user type has a first authorization level that allows an editor user to provide suggested edits to the document, and

a viewer user type has a second authorization level that allows a viewer user to view the unedited version of the document.

10. A system for collaborative document editing the system comprising:

a memory to store a document;

at least one processor coupled to the memory, the at least one processor configured to;

receive, from a client system, a first request to access the document stored in the memory;

provide, to the client system, an application in a browser of the client system, wherein the application is enabled to modify the document;

provide, to the client system, a first portion of the document in the application;

receive a second request to access the document;

determine whether a user that is associated with the second request is authorized to access the document;

in response to a determination that the user is authorized to access the document, transmit a second portion of the document;

receive an edit to at least one of the first portion of the document or the second portion of the document;

and

save the edit to the at least one of the first portion of the document or the second portion of the document.

11. The system of claim 10, wherein the application is distributed over a server and the client system.

12. The system of claim 10, wherein the first request to access the document comprises at least one of a user identifier, a file identifier or a version identifier.

13. The system of claim 10, wherein in response to the determination that the user is not authorized to access the document, the at least one processor is to transmit an error message.

14. The system of claim 10, wherein the second request comprises at least one of a user identifier, a document identifier, portion identifier, or a version identifier.

15. The system of claim 14, wherein to determine whether the user is authorized to access the document the at least one processor is to:

calculate a hash of the user identifier, the file identifier and the version identifier; and

compare a stored cryptographic hash with the generated hash.

16. The system of claim 10, wherein to transmit the second portion of the document the at least one processor is to send an indication that the second portion of the document has been modified.

17. The system of claim 10, wherein the at least one processor is further configured to save an unedited version of the document.

18. The system of claim 17, wherein the at least one processor is further configured to:

provide different versions of the document to the user and a different user, based on user type, wherein;

an editor user type has a first authorization level that allows an editor user to provide suggested edits to the document, and

a viewer user type has a second authorization level that allows a viewer user to view the unedited version of the document.