METHOD FOR SYNCHRONIZING DATA, SYSTEM, AND APPARATUS THEREOF

• US 20100228866A1
• Filed: 05/19/2010
• Published: 09/09/2010
• Est. Priority Date: 02/18/2008
• 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: Chai, Xiaoqian, Liu, Haitao, Wang, Rui, Li, Kepeng
• Application Number:
  US12/783,271
• Publication Number:
  US 20100228866A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 16/275 Synchronous replication
• 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 synchronizing data is disclosed: a synchronization initiator sends a synchronization session request to a synchronization recipient to create a synchronization session connection with the synchronization recipient; and a synchronization process is started in the synchronization session, and the synchronization initiator synchronizes data with the synchronization recipient through the synchronization process. A synchronization process is started in the synchronization session, and the synchronization initiator synchronizes data with the synchronization recipient through the synchronization process, thus synchronizing the data between both parties flexibly.

Claims

1. A method for synchronizing data, comprising:

sending a synchronization session request to a synchronization recipient to create a synchronization session connection between a synchronization initiator and the synchronization recipient, thereby establishing a synchronized session; and

starting, in the synchronization session, a synchronization process through which a synchronization initiator synchronizes data with the synchronization recipient.

2. The method of claim 1, wherein:

the synchronization session comprises one or more synchronization processes, wherein each of the synchronization processes comprises a unique process identifier or a unique database identifiers.

3. The method of claim 1, wherein:

affixing a synchronization process end identifier to the synchronization process; and

determining termination of the synchronization process according to the synchronization message package that carries the synchronization process end identifier.

4. The method of claim 1, wherein:

affixing a synchronization session end identifier to the synchronization session; and

determining termination of the synchronization session according to a synchronization message package that carries the synchronization session end identifier.

5. The method of claim 3, wherein:

the synchronization process comprises a first synchronization process and a second synchronization process, and the synchronization process end identifier comprises a first synchronization process end identifier and a second synchronization process end identifier;

wherein the process identifier of the first synchronization process is correlated with the synchronization process end identifier of the first synchronization process, and the process identifier of the second synchronization process is correlated with the synchronization process end identifier of the second synchronization process.

6. The method of claim 1, wherein in the synchronization session, and after completion of the synchronization process, the method further comprises:

sending a session maintenance command or an idle message package to a synchronization recipient; and

receiving an acknowledgement returned by the synchronization recipient, and maintaining the synchronization session.

7. The method of claim 1, wherein the sending a session maintenance command or an idle message package to a synchronization recipient comprises:

sending the session maintenance command or the idle message package to the synchronization recipient at preset intervals.

8. The method of claim 6, wherein:

the session maintenance command carries authentication information, wherein both of the synchronization initiator and the synchronization recipient authenticate each other through the authentication information.

9. The method of claim 7, further comprising:

specifying a time interval of maintaining the synchronization session in a session command by the synchronization initiator or the synchronization recipient.

10. The method of claim 9, wherein specifying the time interval of maintaining the synchronization session in a session command comprises:

specifying the time interval of maintaining the session in the session maintenance command by the synchronization initiator; and

receiving an acknowledgement returned by the synchronization recipient after an expiry of the time interval.

11. The method of claim 9, wherein specifying the time interval of maintaining the synchronization session in a session command comprises:

receiving, by the synchronization recipient, the session maintenance command sent by the synchronization initiator;

returning an acknowledgement to the synchronization initiator, wherein the acknowledgement specifies the time interval of maintaining the session; and

re-receiving a session maintenance command after an expiry of the time interval.

12. The method of claim 9, further comprising:

starting, by the synchronization initiator or the synchronization recipient, the synchronization process within the time interval of maintaining the session.

13. The method of claim 1, wherein before starting the synchronization process, the method further comprises:

receiving, by the synchronization recipient, a synchronization process request, wherein the synchronization process request carries a first anchor value stored by the synchronization initiator after a first synchronization process ends and carries a second anchor value newly generated by the synchronization initiator;

judging whether the received first anchor value is the same as a first anchor value stored by the synchronization recipient; and

sending a second anchor value to the synchronization initiator if the received first anchor value is the same as the first anchor value stored by the synchronization recipient, and the second anchor value is the same as the second anchor value sent by the synchronization initiator.

14. The method of claim 1, further comprising:

updating an anchor value when the synchronization process ends or after a message package of the synchronization process is sent, wherein the anchor value indicates whether the synchronization process ends successfully or whether the message package of the synchronization process is sent successfully.

15. The method of claim 14, wherein the updating the anchor value comprises:

updating by the synchronization recipient, the first anchor value stored by the synchronization recipient to the second anchor value sent by the synchronization initiator, and

sending an acknowledgement command to the synchronization initiator to confirm termination of the synchronization process.

16. A system for synchronizing data, comprising:

a synchronization initiator, adapted to synchronize data with a synchronization recipient; and

a synchronization recipient, adapted to receive a synchronization session request,

wherein the synchronization initiator is adapted to send the synchronization session request to the synchronization recipient to create a synchronization session connection with the synchronization recipient, start a synchronization process in the synchronization session, and synchronize data with the synchronization recipient through the synchronization process.

17. A synchronization initiator, comprising:

a creating module adapted to send a synchronization session request to the synchronization recipient to create a synchronization session connection with the synchronization recipient;

a starting module adapted to start a synchronization process in the synchronization session created by the creating module; and

a synchronizing module adapted to synchronize data with the synchronization recipient through the synchronization process started by the starting module.

18. The synchronization initiator of claim 17, further comprising:

an identifier affixing submodule adapted to affix a synchronization process end identifier to the synchronization process.

19. The synchronization initiator of claim 18, further comprising:

a correlating submodule adapted to correlate the synchronization process identifier affixed by the identifier affixing submodule with a process identifier of the synchronization process.

20. The synchronization initiator of claim 17, further comprising:

a command sending submodule adapted to send a session maintenance command or an idle message package to the synchronization recipient when waiting for new synchronization data after a synchronization process ends in the synchronization session; and

an acknowledgement receiving submodule adapted to receive an acknowledgement returned by the synchronization recipient and hold the synchronization session.