Data synchronization

US2016239556A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016239556-A1
Application numberUS-201314385015-A
CountryUS
Kind codeA1
Filing dateNov 14, 2013
Priority dateNov 14, 2013
Publication dateAug 18, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

1 . A method performed under control of a client device, 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 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 has been modified after being stored and 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 based on the determining. 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 of the request to logout the client device. 3 . The method of claim 1 , further comprising: 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. 4 . The method of claim 3 , further comprising: deleting the encrypted data file stored on the local data storage. 5 . The method of claim 1 , further comprising: receiving, from the server, an encryption key, wherein the encrypting of the data file is based at least in part on the encryption key. 6 . The method of claim 5 , further comprising: deleting the encryption key after the encrypting of the data file. 7 . The method of claim 1 , further comprising: generating an encryption key based on at least one of the user account login information or device information of the client device; and transmitting the encryption key to the server, wherein the encrypting of the data file is based at least in part on the encryption key. 8 . The method of claim 7 , further comprising: deleting the encryption key after the encrypting of the data file. 9 . A method performed under control of a server, comprising: receiving, from a client device, a request to connect to a user account; establishing a connection with the client device; transmitting, to the client device, a data file stored in connection with the user account; reestablishing the connection with the client device which had been disconnected; receiving, from the client device, an encrypted data file and a request to update the data file stored in connection with the user account; decrypting the encrypted data file; and updating the data file stored in connection with the user account by replacing the data file stored in connection with the user account with the decrypted data file. 10 . The method of claim 9 , wherein the encrypted data file is one that was modified from the data file by the client device in accordance with an input from a user of the client device. 11 . The method of claim 9 , further comprising: transmitting, to the client device, an encryption key, wherein the encrypted data file is encrypted with the encryption key. 12 . The method of claim 9 , further comprising: receiving, from the client device, an encryption key that is generated based on at least one of user account login information or device information of the client device, and wherein the encrypted data file is encrypted with the encryption key. 13 . A client device, comprising: a request receiver unit configured to receive at least one of a request to connect to a server or a request to logout the client device; a connection handler unit configured to connect to the server based at least in part on user account login information; a file receiver unit configured to receive, from the server, a data file stored in connection with a user account; a data file management unit configured to store the received data file in a local data storage; and an encryption unit configured to encrypt the data file stored on the local data storage based on determining that the request receiver unit receives the request to logout the client device and/or the client device is disconnected from the server. 14 . The client device of claim 13 , further comprising: a modification unit configured to modify the data file stored on the local data storage in accordance with an input to the client device. 15 . The client device of claim 14 , wherein the encryption unit is further configured to encrypt the modified data file based on the modified data file is not synchronized with the data file stored in connection with the user account on the server. 16 . The client device of claim 13 , further comprising: a transmission unit configured to transmit, to the server, the encrypted data file stored on the local data storage when the client device is reconnected to the server based at least in part on the user account login information. 17 . The client device of claim 16 , wherein the data file management unit is further configured to delete the encrypted data file stored on the local data storage after the encrypted data file is transmitted to the server. 18 . The client device of claim 13 , wherein the file receiver unit is further configured to receive, from the server, an encryption key, and wherein the encryption unit is further configured to encrypt the data file stored on the local data storage based at least in part on the encryption key. 19 . The client device of claim 13 , further comprising: an encryption key generation unit configured 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 encryption unit is further configured to encrypt the data file stored on the local data storage based at least in part on the encryption key. 20 . A computer-readable storage medium having stored thereon computer-executable instructions that, in response to execution, cause a client device to perform operations, 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 data file in a local data storage; modifying the data file stored on the local data storage in accordance with an input to the client device; receiving a request to logout the client device; encrypting the modified data file, based on determining that the client device is disconnected from the server and/or that the modified data file is not synchronized with the data file stored in connection with the user account. 21 . The computer-readable storage medium of claim 20 , wherein the operations further comprise: reconnecting to the server based at least in part on the user account login information; transmitting, to the server, the encrypted data file stored on the local data storage; and deleting the encrypted data file stored on the local data storage. 22 . The computer-readable storage medium of claim 20 , wherein the operations further comprise: receiving, from the server, an encryption key, wherein the encrypting of the modified data file is based at least in part on the encryption key. 23 . The computer-readable storage medium of claim 20 , wherein the operations further comprise: generating an encryption key based on at least one of the user account login information or device information of the client device; and transmitting the encryption key to the server,

Assignees

Inventors

Classifications

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

  • Event-based monitoring · CPC title

  • specially adapted for file transfer, e.g. file transfer protocol [FTP] · CPC title

  • 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 title

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016239556A1 cover?
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…
Who is the assignee on this patent?
Empire Technology Dev Llc
What technology area does this patent fall under?
Primary CPC classification H04L67/1095. Mapped technology areas include Electricity.
When was this patent published?
Publication date Thu Aug 18 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).