Editing an unhosted third party application

Patent metadata

Field	Value
Publication number	US-9930092-B2
Application number	US-201113312883-A
Country	US
Kind code	B2
Filing date	Dec 6, 2011
Priority date	Dec 6, 2010
Publication date	Mar 27, 2018
Grant date	Mar 27, 2018

Abstract

A document editing system using a third party application having an embedded document editing module is disclosed. The system include a client-side document editing engine that accepts requests to edit a document from and displays at least a portion of the document to a user of the client-side system. The system includes a first server-side application engine that processes the requests to edit the document. The system can include a second server-side data storage engine that stores the document in a remote storage location.

First claim

What is claimed is:

1. A system comprising:
memory;
at least one processor;
a third party application user interface;
a third party application engine, coupled to the third party application user interface, configured to implement a third party application on a client-side network, wherein the client-side network is client-side relative to a server-side application server, wherein the third party application implemented on the client-side network is not hosted by the server-side application server and is hosted by a remote server that forms part of the client-side network, and the third party application implemented on the client-side network is embedded with a document application program interface enabling the third party application implemented on the client-side network to execute a document editing application hosted by the server-side application server;
a file storage repository, coupled to the third party application engine, and configured to maintain a file on the client-side network;
a client-side remote communications engine coupled to the third party application engine and configured to communicate with the server-side application server;
wherein, in operation:
the third party application user interface receives a request from a user to process a modification to the file using the third party application implemented on the client-side network;
the third party application engine selects a set of custom parameters influencing presentation of the file;
the third party application engine transfers the request and the set of custom parameters to the client-side remote communications engine;
the client-side remote communications engine establishes a session to the server-side application server on a server-side network;
the client-side remote communications engine transfers the request and the set of custom parameters to the server-side application server;
the client-side remote communications engine receives a response to the request from the server-side application server, the response including application data that can be presented by the third party application implemented on the client-side network;
the third party application engine displays at least a portion of the file, modified in accordance with the request and the set of custom parameters, at the third party application user interface;
the third party application engine instructs the client-side remote communications engine to initiate a procedure to close the session in response to detecting a termination stimulus.

2. The system of claim 1 , wherein, in operation, the third party application engine receives a save command to save data associated with the file in the file storage repository.

3. The system of claim 1 , wherein, in operation, the client-side remote communications engine sends the request to a server-side remote communications engine at the server-side application server over the Internet using an Internet protocol.

4. The system of claim 1 , wherein the request includes a command to open, view, edit, or save the file.

5. The system of claim 1 , wherein the request includes data sufficient to identify a universal resource locator (URL) of the file.

6. The system of claim 5 , further comprising a browser engine, wherein a browser of the browser engine receives the file using the URL.

7. The system of claim 5 , further comprising a browser engine, wherein a browser of the browser engine uses the URL to open the file in a human-readable format.

8. The system of claim 5 , wherein the client-side remote communications engine sends a publicly accessible URL of a service in the request, wherein, in operation, the service is configured to fetch content of the file from the client-side network and save the content in a specified location in the file storage repository.

9. The system of claim 5 , wherein the request includes a save command and is used to transfer content to a third party's repository without the presence of a firewall.

10. The system of claim 1 , wherein the user is one of a plurality of collaborating users editing the file, each having identities sufficient to enable the client-side network to differentiate between the plurality of collaborating users.

11. The system of claim 1 , wherein the third party application implemented on the client-side network runs on a mobile device.

12. The system of claim 1 , further comprising a document selection engine coupled to the third party application user interface, wherein, in operation, the document selection engine facilitates selection of the file from a list of files.

13. The system of claim 1 , further comprising a document selection engine coupled to the third party application user interface, wherein, in operation, the document selection engine facilitates selection of a new file as the file.

14. The system of claim 1 , wherein the request to the server-side application server includes an identification of the file.

15. The system of claim 1 , wherein the client-side network is coupled to a wide area network (WAN) over which the request is sent to the server-side application server.

16. The system of claim 1 , wherein the client-side remote communications engine receives file data from the server-side application server in association with the request to the server-side application server.

17. The system of claim 1 , wherein the client-side remote communications engine receives file data from a document repository on a private network in association with the request to the server-side application server.

18. The system of claim 1 , wherein the client-side remote communications engine sends document processing commands to the server-side application server and receives responses to the document processing commands from the server-side application server.

19. The system of claim 1 , wherein the client-side remote communications engine saves the file, with edits, at a document repository on a private network as part of a session-closing procedure that includes the client-side remote communications engine sending a save notification.

20. The system of claim 1 , wherein the third party application user interface opens a partner web portal to facilitate browsing to find the file as part of a file opening routine.

21. The system of claim 1 , wherein the third party application user interface enables the user to open the file as part of a file opening routine that includes providing a file opening command to the client-side remote communications engine to send as the request to the server-side application server.

22. The system of claim 1 , further comprising a document retrieval engine coupled to the third party application user interface, wherein, in operation:
the client-side remote communications engine receives from the server-side application server in association with the request a location identifier of the file on a private network;
the document retrieval engine uses the location identifier to enable the third party application user interface to render at least a portion of the file.

Assignees

• Vegesna Venkata Ramakrishna Raja
• Ranjithkumar Sakthiamuthu D
• Sabhiok Raj P
• Vembu Sridhar
• Zoho Corporation Private Ltd

Inventors

• Vegesna-Venkata Ramakrishna Raja
• Ranjithkumar Sakthiamuthu D
• Sabhiok Raj P
• Vembu Sridhar

Classifications

• H04L67/143

  Termination or inactivation of sessions, e.g. event-controlled end of session · CPC title

• H04L67/146

  Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G06F40/166

  Editing, e.g. inserting or deleting · CPC title

• G06F17/24

  Physics · mapped topic