Data synchronization

• US 9,996,601 B2
• Filed: 11/14/2013
• Issued: 06/12/2018
• Est. Priority Date: 11/14/2013
• Status: Expired due to Fees

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: Oh, Hyun-Oh, Son, Ju-Hyung, Kwak, Jin-Sam
• Primary Examiner(s): SHOLEMAN, ABU S
• Application Number:
  US14/385,015
• Publication Number:
  US 20160239556A1
• Time in Patent Office: 1,671 Days
• Field of Search: 713164
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 16/235 Update request formulation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: H04L 63/00 Network architectures or network communication protocols for network security cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• 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

Technologies are generally described for a data synchronization scheme. In some examples, a method performed under control of a client device may include connecting to a server based at least in part on user account login information; receiving, from the server, a data file stored in connection with the user account; storing the received data file in a local data storage; receiving a request to logout the client device; determining that the client device is disconnected from the server and/or that the data file stored on the local data storage is not synchronized with the data file stored in connection with the user account; and encrypting the data file stored on the local data storage.

Claims

1. A method performed under control of a client device, the method comprising:

connecting to a server based at least, in part, on user account login information;

receiving, from the server, a data file stored in connection with a user account;

storing the received data file on a local data storage;

receiving a request to logout the client device;

responsive to a determination that either,

the client device is disconnected from the server, or

the data file stored on the local data storage has been modified after being stored and the modified data file is out-of-synchronization with the data file stored in connection with the user account,

encrypting the data file stored on the local data storage;

generating an encryption key based on at least one of the user account login information or device information of the client device;

transmitting the encryption key to the server,

wherein the encrypting the data file is based at least, in part, on the encryption key;

deleting the encryption key after the encrypting the data file;

reconnecting to the server based at least, in part, on the user account login information; and

transmitting, to the server, the encrypted data file stored on the local data storage to update the data file stored in connection with the user account on the server after the client device reconnects to the server.

2. The method of claim 1, further comprising:

modifying the data file stored on the local data storage in accordance with an input to the client device, prior to the receiving the request to logout the client device.

3. The method of claim 1, further comprising:

deleting the encrypted data file stored on the local data storage.

4. A client device, comprising:

a user interface configured to receive at least one of a request to connect to a server or a request to logout the client device;

a communication interface configured to connect to the server based at least, in part, on user account login information and to receive, from the server, a data file stored in connection with a user account;

a memory configured to store instructions; and

a processor operatively coupled to the user interface, the communication interface, and the memory, wherein the processor is configured to execute the instructions stored in the memory to;

store the received data file on the memory; and

based on a determination that either the user interface has received the request to logout the client device or that the client device is disconnected from the server, encrypt the data file stored on the memory,

wherein the processor is further configured to execute the instructions stored in the memory to generate an encryption key based on at least one of the user account login information or device information of the client device,

wherein the communication interface is further configured to transmit the encryption key to the server,

wherein the processor is configured to execute the instructions stored in the memory to encrypt the data file stored on the memory based at least, in part, on the encryption key,

wherein the processor is further configured to execute the instructions stored in the memory to delete the encryption key after the data file is encrypted,

wherein the communication interface is further configured to transmit, to the server, the encrypted data file stored in the memory to update the data file stored in connection with the user account on the server, and

wherein the transmission is performed after the client device is reconnected to the server based at least, in part, on the user account login information.

5. The client device of claim 4, wherein the processor is further configured to execute the instructions stored in the memory to:

modify the data file stored on the memory in accordance with an input to the client device.

6. The client device of claim 5, wherein the processor is further configured to execute the instructions stored in the memory to encrypt the modified data file based on the modified data file being out-of-synchronization with the data file stored in connection with the user account on the server.

7. The client device of claim 4, wherein the processor is further configured to execute the instructions stored in the memory to delete the encrypted data file stored in the memory, after the encrypted data file is transmitted to the server.

8. A non-transitory computer-readable storage medium having stored executable instructions that, in response to execution, cause a client device to perform or control performance of operations, comprising:

connect to a server based at least, in part, on user account login information;

identify a data file received from the server, wherein the data file was stored in connection with a user account;

store the data file on a local data storage;

modify the data file stored on the local data storage in accordance with an input to the client device;

detect a request to logout the client device;

encrypt the modified data file, based on a determination that either the client device is disconnected from the server or that the modified data file is out-of-synchronization with the data file stored in connection with the user account;

generate an encryption key based on at least one of the user account login information or device information of the client device;

transmit the encryption key to the server,

wherein the encryption of the data file is based at least, in part, on the encryption key;

delete the encryption key after the encryption of the data file;

reconnect to the server based at least, in part, on the user account login information; and

transmit, to the server, the encrypted data file stored on the local data storage.

9. The computer-readable storage medium of claim 8, wherein the operations further comprise:

delete the encrypted data file stored on the local data storage.