Communication protocols for an online content management system

Patent metadata

Field	Value
Publication number	US-11848994-B2
Application number	US-202016896819-A
Country	US
Kind code	B2
Filing date	Jun 9, 2020
Priority date	Jun 5, 2014
Publication date	Dec 19, 2023
Grant date	Dec 19, 2023

Abstract

In some embodiments, a client application at a client device can receive, from a browser application at the client device, a first message including a unique identifier associated with a session of the browser application at a website associated with a content management system. The client application can extract the unique identifier from the first message, and establish a connection between the client application and the content management system by sending, from the client application to the content management system, a second message including the unique identifier. The client application can then receive, from the content management system through the connection, a third message relayed by the content management system from the website, where the third message is associated with the unique identifier.

First claim

What is claimed is:

1. A computer-implemented method comprising:
receiving, by a client application at a client device, a unique identifier uniquely identifying a browser application;
sending, from the client application to a content management system, a message including the unique identifier of the browser application; and
in response to sending the message to the content management system, receiving, by the client application, a response message relayed by the content management system from the browser application to the client application, wherein the content management system includes a mapping of the client application to the browser application, the mapping established based on the unique identifier included in the message and used by the content management system to relay communications between the client application and the browser application.

2. The computer-implemented method of claim 1 , wherein the client application is installed at the client device and used to synchronize local content items at the client device or access content items hosted on the content management system through an interface of the client application.

3. The computer-implemented method of claim 1 , wherein the unique identifier is a nonce based on data or details specific to the browser application.

4. The computer-implemented method of claim 1 , wherein the message further includes metadata identifying a type of information that the client application is expecting or a source or session associated with the message that the client application is expecting.

5. The computer-implemented method of claim 1 , wherein the message includes a request, the message was based on the request for the content management system to relay the message to the client application.

6. The computer-implemented method of claim 5 , wherein the message further includes a second request for the content management system to relay to the client application any messages which includes a reference to the unique identifier.

7. The computer-implemented method of claim 1 , further comprising:
indicating a type of message that the client application is expecting from the browser application in the message.

8. The computer-implemented method of claim 1 , wherein the client application and the browser application are running at the client device under a same OS username and a match is verified by the content management system.

9. The computer-implemented method of claim 1 , further comprising:
receiving a second response message that is relayed to a different session than a first session that was relayed the response message, wherein the second response message and the response message both includes a same unique identifier.

10. A system comprising:
one or more processors;
a computer-readable medium; and
computer-readable instructions, stored on the computer-readable medium, that when executed cause the one or more processors to:
receive, by a client application at a client device, a unique identifier uniquely identifying a browser application;
send, from the browser application to a content management system, a message including the unique identifier of the browser application; and
in response to sending the message to the content management system, receive, by the client application, a response message relayed by the content management system from the browser application to the client application, wherein the content management system includes a mapping of the client application to the browser application, the mapping established based on the unique identifier included in the message and used by the content management system to relay communications between the client application and the browser application.

11. The system of claim 10 , wherein the client application is installed at the client device and used to synchronize local content items at the client device or access content items hosted on the content management system through an interface of the client application.

12. The system of claim 10 , wherein the unique identifier is a nonce based on data or details specific to the browser application.

13. The system of claim 10 , wherein the message further includes metadata identifying a type of information that the client application is expecting or a source or session associated with the message that the client application is expecting.

14. The system of claim 10 , wherein the message includes a request, the message was based on the request for the content management system to relay the message to the client application.

15. The system of claim 14 , wherein the message further includes a second request for the content management system to relay to the client application any messages which includes a reference to the unique identifier.

16. The system of claim 10 , the computer-readable instructions, when executed, further cause the one or more processors to indicate a type of message that the client application is expecting from the browser application in the message.

17. The system of claim 10 , the computer-readable instructions, when executed, further cause the one or more processors to determine, by the client application, if the message is a secure session request from the browser application.

18. A non-transitory computer-readable storage medium having stored therein instructions which, when executed by one or more processors, cause the one or more processors to:
receive, by a client application at a client device, a unique identifier uniquely identifying a browser application;
send, from the client application to a content management system, a message including the unique identifier of the browser application; and
in response to sending the message to the content management system, receiving, by the client application, a response message relayed by the content management system from the browser application to the client application, wherein the content management system includes a mapping of the client application to the browser application, the mapping established based on the unique identifier included in the message and used by the content management system to relay communications between the client application and the browser application.

19. The non-transitory computer-readable storage medium of claim 18 , wherein further instructions which, when executed by the one or more processors, cause the one or more processors to:
maintain a connection or communication channel between the client application and the content management system open based on the unique identifier.

20. The non-transitory computer-readable storage medium of claim 18 , wherein further instructions which, when executed by the one or more processors, cause the one or more processors to:
determine, by the client application, if the message is a secure session request from the browser application.

Assignees

• Dropbox Inc

Inventors

• Bortz Andrew
• Tian Sang
• Kaplan Joshua
• Akhawe Devdatta

Classifications

• H04L67/141 Primary

  Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title

• H04L63/08

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• H04L67/02

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

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L67/306

  User profiles · CPC title