Method For Processing Data Synchronization And Client Terminal, Server, And Data Synchronization System Thereof

• US 20080270485A1
• Filed: 05/16/2008
• Published: 10/30/2008
• Est. Priority Date: 11/16/2005
• Status: Abandoned Application

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Gao, Wei, Yu, Hongbin, Zhou, Yingjun, Chen, Chunrong
• Application Number:
  US12/122,120
• Publication Number:
  US 20080270485A1
• Time in Patent Office: Days
• US Class Current: 707/201
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: H04L 61/457 containing identifiers of data entities on a computer, e.g. file names
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A method for processing data synchronization includes a client terminal performing corresponding updating process for the updating data item transmitted from a server; storing the global unique identity (GUID) corresponding to the updating data item sent from the server; if this synchronization process is interrupted, after next synchronization process is re-initiated, the client terminal reporting the stored GUID to server memory; according to the stored result, the server transmitting GUID and the corresponding updating data items which are not included in the stored result in itself updating database to the client terminal, then returning to procedure. Correspondingly, the present disclosure also provides a client terminal, server and data synchronization system. The present disclosure enables to complete data synchronization normally even if the case that the data synchronization process is interrupted.

Claims

1. A method for processing data synchronization comprising:

performing, by a client, corresponding modification on a modified data item sent from a server;

buffering, by the client, a global unique identity sent from the server corresponding to the modified data item;

reporting, by the client, the buffered global unique identity to the server after restarting the synchronization process next time in a case that the current synchronization process is interrupted; and

storing, by the server, the reported information, sending a global unique identity (GUID) and a corresponding modified data item in its own modification database to the client for the client to perform corresponding process, wherein the GUID is not included in the stored result.

2. The method according to claim 1, wherein, after successfully storing the reported information by the server, the method further comprises:

feeding back, by the server, a successful storage response message to the client; and

deleting, by the client, the global unique identity buffered by the client upon receiving the successful storage response message fed back by the server.

3. The method according to claim 1, wherein, after successfully storing the reported information by the server, the method further comprises:

ending the data synchronization process in a case that no GUID that is not comprised in the stored result and corresponding modified data item can be indexed in the own modification database of the server.

4. The method according to claim 1, wherein buffering a global unique identity sent from the server corresponding to the modified data item comprises:

allocating, by the client, a corresponding local unique identity to the modified data item sent from the server;

creating, by the client, a mapping relationship between the local unique identity and the global unique identity sent from the server corresponding to the modified data item; and

buffering, by the client, the created mapping relationship.

5. The method according to claim 4, wherein reporting the buffered global unique identity to the server by the client is implemented by reporting the buffered mapping relationship to the server.

6. The method according to claim 5, wherein storing the reported information by the server comprises updating a mapping information table by the server according to the reported mapping relationship.

7. The method according to claim 6, wherein, after updating the mapping information table by the server, the method further comprises:

feeding a mapping information storage success response message back to the client; and

deleting the buffered mapping relationship by the client upon receiving the mapping information storage success response message fed back by the server.

8. The method according to claim 4 further comprising:

reporting, by the client, the buffered mapping relationship to the server and clear the buffered mapping relation from the client in a case that the current synchronization process is success.

9. The method according to any one of claim 1, wherein the modified data item is a newly added data item.

10. The method according to any one of claim 2, wherein the modified data item is a newly added data item.

11. The method according to any one of claim 3, wherein the modified data item is a newly added data item.

12. The method according to any one of claim 4, wherein the modified data item is a newly added data item.

13. The method according to any one of claim 5, wherein the modified data item is a newly added data item.

14. The method according to any one of claim 6, wherein the modified data item is a newly added data item.

15. The method according to any one of claim 7, wherein the modified data item is a newly added data item.

16. The method according to any one of claim 8, wherein the modified data item is a newly added data item.

17. A client comprising:

a modification processing unit, adapted for performing corresponding modification on a modified data item sent from a server;

an identity buffering unit, adapted for buffering a global unique identity sent from the server corresponding to the modified data item; and

an identity reporting unit, adapted for reporting the global unique identity buffered by the identity buffering unit to the server after restarting a synchronization process next time in a case that the current synchronization process is interrupted.

18. The client according to claim 17 further comprising:

an identity deleting unit, adapted for deleting the global unique identity buffered in the identity reporting unit upon receiving a successful storage response message fed back by the server.

19. The client according to claim 17, wherein the identity buffering unit comprises:

an identity allocating subunit, adapted for allocating a corresponding local unique identity to the modified data item sent from the server;

a mapping relationship creating subunit, adapted for creating a mapping relationship between the local unique identity allocated by the identity allocating subunit and the global unique identity sent from the server corresponding to the modified data item; and

a mapping identity buffering subunit, adapted for buffering the mapping relationship created by the mapping relation creating subunit.

20. The client according to claim 19, wherein the identity reporting unit is a mapping identity reporting unit adapted for reporting the mapping relationship buffered in the mapping identity buffering subunit to the server.

21. A server comprising:

a reported information storage unit, adapted for storing a global unique identity reported by a client, wherein the global unique identity corresponds to a modified data item updated by the client sent from the server;

a searching unit, adapted for searching a global unique identity and a corresponding modified data item in the own modification database of the server;

the global unique identity is not comprised in the reported information storage unit; and

a sending unit, adapted for sending the global unique identity and the corresponding modified data item searched by the searching unit to the client.

22. The server according to claim 21 further comprising a storage response unit adapted for feeding a successful storage response message back to the client upon successfully storing the global unique identity by the reported information storage unit.

23. The server according to claim 21, wherein the reported information storage unit is a mapping information table updating unit adapted for updating a mapping information table in the server according to the mapping relationship between the global unique identity and the local unique identity reported by the client.

24. A data synchronization system comprising a client and a server, wherein:

the client is adapted for performing corresponding modification on a modified data item sent from the server, buffering a global unique identity corresponding to the modified data item sent from the server, and reporting the buffered global unique identity to the server upon restarting a interrupted synchronization process; and

the server is adapted for storing the reported information and sending the global unique identity and the corresponding modified data item in its modification database to the client;

the global unique identity is not comprised in the storage result.