CN100461704C - Data Synchronization Method - Google Patents

Abstract

The invention discloses a method for synchronizing data, which is used for synchronizing dynamic data in an upgrade process without interruption, mainly comprising the following steps: A. setting the same dynamic data block number in the new version software as that in the old version software; B. Establish a new version software and old version software synchronization data block content conversion function, and call the conversion function when the dynamic data is synchronized from the non-upgraded device to the upgraded device to complete the synchronization of the dynamic data. Through the method provided by the present invention, the problem of the consistency of data block identification in the new and old versions of software is solved, and the new version of the software is guaranteed to be able to identify the content of the synchronized data blocks, so as to realize the synchronization of dynamic data between different software versions , thereby realizing the function of not interrupting the service during the upgrade process, and meeting the urgent needs of the operators. Upgrading applications that do not interrupt service functions will greatly improve operators' service quality and operational reliability.

Description

Data Synchronization Method

technical field

The invention relates to the communication field, in particular to a method for data synchronization in an uninterrupted upgrading process.

Background technique

Currently, software upgrades are common in the communications field, and service interruptions are likely to occur during the upgrade process. Today, with increasingly high reliability requirements for telecommunication services, it is very urgent to upgrade without interrupting services. The main process of upgrading existing equipment is as follows:

(11) Before the upgrade, both the main and standby boards were running normally, and all were running the old version;

(12) Both the main board and the standby board are loaded with new programs and configuration data;

(13) Reset the two main control boards to make the new program take effect.

It can be seen that the two main control boards have been reset during the upgrade process, and service interruption is inevitable.

Due to the limitations of the existing technology, it is not possible to replace the old program software with the new program software without resetting the main control board for the time being, so the reset of the main control board is inevitable for software upgrades. The common practice now is to use the active/standby switchover function to realize the uninterrupted service upgrade function. The steps are as follows:

(21) Before the upgrade, the main and standby boards were running normally, and all were running the old version;

(22) The standby board is upgraded to a new version;

(23) The main board synchronizes the data to the standby board;

(24) After the data synchronization is completed, the master-standby switchover is completed, and the new main board (the original standby board) starts to use the new version program to control the operation of the business;

(25) The new backup board (the original main board) is upgraded to a new version.

In the above operation process, step (23) is the key, because only when the data of the main board is completely synchronized to the standby board, can the active and standby switchover be performed, so as to ensure that the business will not be interrupted after the switchover. Since the active and standby versions are different at this time, the data on the main board is synchronized to the standby board, and the standby board cannot guarantee complete recognition and understanding. Therefore, the data synchronization of different versions is the key to solve the upgrade without interrupting the business.

The data synchronized by master and backup can be divided into two types, one is user configuration data, and the other is dynamic operation data. Configuration data can be synchronized by first exporting it in the form of a file, then using an external tool to upgrade to a new version, and then loading it to the standby board. However, dynamic data is related to the dynamic operating status of the system, and this method cannot be used. Synchronization of dynamic data It can only be synchronized through message transmission during the operation of the master and slave boards.

The synchronization of dynamic data in the scenario where the upgrade does not interrupt the business faces a difficulty: the master and backup versions are inconsistent during data synchronization, and there will be differences in understanding the data that has been synchronized by the main board and the backup board according to the data definition rules of the new version. How to correctly identify the data synchronized from the old version and how to convert the synchronized data into data understood by the new version is a current problem.

It is precisely because of the above-mentioned problems that the dynamic operation data is actually lost during the upgrade process, and there is no guarantee that the upgrade will not interrupt the business. To realize the upgrade without interrupting the business, the key technology is to solve the synchronization problem of dynamic data.

The application scenario of the existing dynamic data synchronization solution for the active and standby boards is not an upgrade scenario, but a scenario where the normal standby board plays a protective role. At this time, the main board and the The dynamic data on the standby board is divided into synchronous data blocks according to their functions. Each synchronous data block contains several dynamic data describing the same function. The size and content of each synchronous data block may be different. The synchronization data block has two levels of indexes to identify, one is the module identification, and the other is the synchronization block number in the module. The module identification indicates which module the synchronization block belongs to, and the synchronization block number identifies the number of the synchronization block in the module. number + sync block sequence number uniquely identifies a sync data block. Since the master and backup software are completely consistent, the number and definition of the module number and the number and definition of the synchronization block serial number on the master and slave boards are absolutely consistent. The main board only needs to carry the module number + synchronization block serial number to send a synchronization block to the standby board. Yes, the standby board can uniquely identify the synchronization block according to the module number + synchronization block serial number after receiving the synchronization data block, and the backup board simply overwrites its own corresponding block with the received synchronization block data. As shown in Figure 1.

During normal operation, if the dynamic data of the main board changes, the main board will send the synchronization data block where the changed dynamic data is located to the backup board, and the backup board will identify the synchronization data block and overwrite its corresponding block, thus To achieve the purpose of synchronizing the dynamic data of the main board with the standby board. When the main board fails, since the software, configuration data, and dynamic data of the standby board are completely consistent with the main board, active/standby switchover will not interrupt services.

The premise that this synchronization solution is feasible requires that the identification of the synchronization block of the main board and the backup board and the content of the synchronization block with the same identification are completely consistent, which can only be realized in the same software version. Therefore, this solution only solves the problem of dynamic data synchronization when the master and backup software are completely consistent. In the upgrade scenario, since the standby board software has been upgraded to the new software first, the number and content of dynamic blocks in the new software may be modified compared with the old software. At this time, the synchronization scheme cannot correctly identify the synchronization block. , and the content after identification cannot be overwritten, because the content of blocks in the old and new versions of the software may be inconsistent, so this solution cannot correctly synchronize dynamic data to the standby board in the upgrade scenario.

Contents of the invention

The embodiment of the present invention provides a data synchronization method to solve the problem of service interruption during the upgrade process.

Embodiments of the present invention provide a method for synchronizing data in an uninterrupted service upgrade process, including:

A. Set the same data block number in the new version software as in the old version software;

B. Establish a conversion function for converting the data block content between the new version software and the old version software. The above conversion function is to upgrade the data block corresponding to the data block number from the old version to the new version; and when the data is synchronized from the non-upgraded device to the upgraded device device, call the conversion function corresponding to the data block number of the above data.

Embodiments of the present invention solve the problem of data block identification consistency in the old and new version software by setting the same data block number in the new version software as in the old software version, and by establishing the data block content conversion in the new version software The function ensures that the new version of the software can identify the content of the synchronized data block, and realizes the synchronization of data between different software versions, so as to realize the function of not interrupting the service during the upgrade process and meet the urgent needs of operators. Upgrading applications that do not interrupt service functions will greatly improve operators' service quality and operational reliability.

Description of drawings

FIG. 1 is a schematic diagram of a dynamic data synchronization method in the prior art.

FIG. 2 is a schematic flowchart of a first embodiment of a data synchronization method according to an embodiment of the present invention.

Fig. 3 is a schematic diagram of setting the consistency of data block identifiers between the new version software and the old version software according to the first embodiment of the present invention.

FIG. 4 is a schematic diagram of the implementation process of the data synchronization conversion function in the first embodiment of the embodiment of the present invention.

FIG. 5 is a schematic flowchart of a second embodiment of a data synchronization method according to an embodiment of the present invention.

Fig. 6 is a schematic diagram of setting the consistency of data block identifiers between the new version software and the old version software according to the second embodiment of the embodiment of the present invention.

FIG. 7 is a schematic diagram of the implementation process of the data synchronization conversion function in the second embodiment of the embodiment of the present invention.

FIG. 8 is a schematic diagram of the structure of the linked list of conversion function pointers according to the embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention more clear, the following will further describe the solution of the present invention in detail with examples and with reference to the accompanying drawings.

Referring to Fig. 2, this figure is a flow chart of the first embodiment of the data synchronization method in the uninterrupted upgrade process of the embodiment of the present invention, and its main process is as follows:

Step 201: setting the same dynamic data block number in the new version software as in the old version software;

Set the same dynamic data block number in the new version of the software as in the old version of the software, that is, to ensure that the same data block in the new version of the software has the same identification as the old version of the software. On this basis, if a new data block is added, its The identification can only use the newly added number, so as not to affect the numbering of the data block in the old version. Referring to Figure 3, module M in software V1.0 has N synchronization data blocks, then in the new version of software V2.0, block 1 in module M corresponds to block 1 in module M in V1.0, and block N in V2.0 Corresponding to block N in V1.0, if a new synchronization data block is added in module M of V2.0, its number is N+1. If there is a situation that the block identification needs to be reduced, as long as these no longer used numbers are reserved on the block number, the function of the reduced block can be removed functionally.

Step 202: Establish a function for converting dynamic data block content between the new version software and the old version software, and call the conversion function when the dynamic data is synchronized from the non-upgraded device to the upgraded device.

The specific implementation is as follows:

Referring to FIG. 4 , this figure is a schematic diagram of an implementation process of a data synchronization conversion function according to Embodiment 1 of the present invention. The conversion function realizes the conversion from V1.0 to V2.0. Among them, the module M in V1.0 contains N data blocks, the module M in V2.0 contains N data blocks, the content of block 1 in V2.0 has changed, and the identification of block 1 is: module M + block 1 needs to use The conversion function converts its content. This conversion function transforms the content format of block 1 to the content format of block 1 defined by V2.0, so as to ensure that the application program of V2.0 software can understand it, and realize the dynamic synchronization of block 1 of module M from V1.0 to V2.0 synchronization.

This conversion function is specifically written and linked by the software developers of V2.0. This conversion function is only applicable to the conversion of block 1 in module M, and only applicable to the conversion between V1.0 and V2.0, that is, any A conversion function is all about upgrading from a specific version to a specific version for a specific block. The entry parameter of the conversion function is the structure content of block 1, and the exit parameter of the function carries the structure content of block 1 defined by V2.0 after conversion. A function prototype can be defined as:

intModule-M-Block-1-Convert-From-V1.0-To-V2.0 (V1.0 block 1 structure *pBlock1, V2.0 block 1 structure *pBlock2)

Parameter description: The pointer of pBlock1 points to the sync data block before conversion, and the pointer of pBlock2 points to the sync data block after conversion.

The new version adds a conversion function of a synchronization block, and then applies for a new data structure to be linked to the pointer list of the synchronization block. Refer to FIG. 8 , which is a schematic diagram of the structure of the conversion function pointer linked list in the present invention. The pointer linked list of the synchronization block is sorted, so that the backup board can execute the conversion function in order from front to back after receiving the synchronization data block.

Since the version before the upgrade is uncertain, a conversion function from the version before the upgrade to the new version is attached to each synchronization block with changed content on the new version, and the conversion is realized by converting adjacent versions one by one , each version only needs to consider the data block conversion problem with the previous adjacent old version.

The method of upgrading versions one by one is: all software versions are sorted according to the release order of software versions, for example, V1.0->V2.0->V3.0->V4.0->V5.0->V6.0, starting from one Upgrading from an old version to a new version is not done in one step, but is upgraded step by step according to the order of versions. The conversion function does not directly call a conversion function from the old version to the new version, but calls the synchronization block in order. All conversion functions between upgrade versions. For example: after block X is synchronized from V2.0 to V6.0, the V6.0 software does not directly call the conversion function of block X from V2.0 to V6.0, but first calls block X from V2.0 To the conversion function of V3.0, the content of the converted synchronization block is converted through the conversion function of block X from V3.0 to V4.0... until the last call of block X from V5.0 to V6.0 The conversion function to get the block content that V6.0 can understand. If there is no conversion function attached to two adjacent versions during the calling process (if there is no change in the content of block X between two adjacent versions, the two versions do not have a conversion function attached), skip directly and continue to call the next conversion function .

During the dynamic data block synchronization process, the standby board receives the data block synchronized from the main board, finds the unique synchronization block corresponding to the backup board according to the carried module number + synchronization block number, and thus finds the conversion function linked list attached to the synchronization block. Determine the first converted function in the conversion function linked list according to the version number (old version number) of the motherboard, and then execute the conversion functions on the linked list one by one from this function to the end in order, and the new software can be obtained after the conversion of the last conversion function is completed. The new software can correctly understand the content of the synchronization block on the version, and send the content to the application module for use.

If the content of the data block corresponding to the old version software in the new version software does not change, because the new version software can recognize the content of the block, so the conversion function can not be set for the unchanged data block content; The conversion function is set for the data block, but the conversion function does not perform any conversion, and its implementation method is as described above, which can also achieve the purpose of data synchronization.

Referring to FIG. 5, this figure is a flow chart of the second embodiment of the data synchronization method in the uninterrupted upgrade process of the embodiment of the present invention, and its main process is as follows:

Step 501: Set the same dynamic data block number in the new version software as in the old version software, that is, ensure that the identification of the same data block in the new version software is the same as the identification in the old version software. On this basis, if the new data block, its identification can only use the newly added number, so as not to affect the number of the data block in the old version. Referring to Figure 6, module M in software V1.0 has N synchronous data blocks, then block 1 in module M in the new version of software V2.0 corresponds to block 1 in module M in V1.0, and block N in V2.0 Corresponding to block N in V1.0, if a new synchronization data block is added in module M of V2.0, its number is N+1. If there is a situation that the block identification needs to be reduced, as long as these no longer used numbers are reserved on the block number, the function of the reduced block can be removed functionally.

Step 502: Establish a function for converting dynamic data block content between the new version software and the old version software, and call the conversion function when the dynamic data is synchronized from the non-upgraded device to the upgraded device.

The specific implementation is as follows:

Referring to FIG. 7 , this figure is a schematic diagram of the implementation process of the data synchronization conversion function in Embodiment 2 of the present invention. The conversion function realizes the conversion from V1.0 to V4.0. Among them, the module M in V1.0 contains N data blocks, the module M in V4.0 contains N data blocks, the content of block 1 in V4.0 has changed, and the identification of block 1 is: module M+ block 1, which needs Transform its contents with a transform function.

After block 1 in module M is synchronized from V1.0 to V4.0, if the content of block 1 changes, the software of V4.0 must have a conversion function, and the conversion function will change the content format of block 1 To the content format of block 1 defined by V4.0, to ensure that the application program of V4.0 software can understand, and realize the synchronization of dynamic synchronization block 1 of module M from V1.0 to V4.0.

This conversion function is specifically written and linked by the software developers of V4.0. This conversion function is only applicable to the conversion of block 1 in module M, and only applicable to the conversion between V1.0 and V4.0, that is, any A conversion function is all about upgrading from a specific version to a specific version for a specific block. The entry parameter of the conversion function is the structure content of block 1, and the exit parameter of the function carries the structure content of block 1 defined in V4.0 after conversion. A function prototype can be defined as:

intModule-M-Block-1-Convert-From-V1.0-To-V4.0 (V1.0 block 1 structure *pBlock1, V4.0 block 1 structure *pBlock4)

Parameter description: The pointer of pBlock1 points to the sync data block before conversion, and the pointer of pBlock4 points to the sync data block after conversion.

The new version adds a conversion function of a synchronization block, and then applies for a new data structure to be linked to the pointer list of the synchronization block. Refer to FIG. 8 , which is a schematic diagram of the structure of the conversion function pointer linked list in the present invention. The pointer linked list of the synchronization block is sorted, so that the backup board can execute the conversion function in order from front to back after receiving the synchronization data block.

In this embodiment, a conversion function from the pre-upgrade version to the new version is mounted on the new version for each synchronization block whose content has changed. Since the version before the upgrade is uncertain, the actual conversion does not use adjacent Versions are converted one by one, but all previous old versions are used as a reference. Each synchronization block corresponds to each previous old version. A conversion function is attached. When data is synchronized, the standby board does not need to call adjacent versions one by one for the received data. transition function, instead calling the only transition function from the old version to the new version. This solution improves the efficiency of data synchronization, but when developing a new version, it is necessary to consider the changes in the synchronization data block compared with all previous versions.

During the dynamic data block synchronization process, the standby board receives the data block synchronized from the main board, finds the unique synchronization block corresponding to the backup board according to the carried module number + synchronization block number, and thus finds the conversion function linked list attached to the synchronization block. Determine the conversion function linked list according to the version number (old version number) of the motherboard, find the function directly converted from the old version to the new version, and then you can get the content of the synchronization block on the new software version. The new software can correctly understand this synchronization block, and use the The content is sent to the application module for use.

Embodiments of the present invention solve the problem of data block identification consistency in the old and new version software by setting the same data block number in the new version software as in the old software version, and by establishing the data block content conversion in the new version software The function ensures that the new version of the software can identify the content of the synchronized data block, and realizes the synchronization of data between different software versions, so as to realize the function of not interrupting the service during the upgrade process and meet the urgent needs of operators. Upgrading applications that do not interrupt service functions will greatly improve operators' service quality and operational reliability.

If the content of the data block corresponding to the old version software in the new version software does not change, because the new version software can recognize the content of the block, so the conversion function can not be set for the unchanged data block content; The conversion function is set for the data block, but the conversion function does not perform any conversion, and its implementation method is as described above, which can also achieve the purpose of data synchronization.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (9)

1. A method for data synchronization, used for uninterrupted data synchronization in the service upgrade process, characterized in that: A. Set the same data block number in the new version software as in the old version software; B. Establish a conversion function for the conversion of new version software and old version software data block content, the conversion function is to upgrade the data block corresponding to the data block number from the old version to the new version; and when the data is synchronized from the non-upgraded device to the existing When upgrading the device, call the conversion function corresponding to the data block number of the data. 2. The method according to claim 1, characterized in that, said step A further comprises: when adding a new data block in the new version software, retaining the existing data block numbering, and adding the new numbering to the existing numbering Added on the basis of . 3 . The method according to claim 1 , wherein the step B further comprises: converting the content of the same data block in the new version software and the old version software through the called conversion function. 4 . 4. The method according to claim 3, characterized in that, the step B further comprises: converting the content of the data block by the called conversion function is aimed at a single data block. 5. The method according to claim 1, wherein the step B further comprises: converting the content of the data block by the called conversion function is aimed at the data block whose content has changed. 6. The method according to claim 1 or 5, characterized in that the step B further comprises: converting the data block content by the called conversion function step by step according to the order of software versions. 7. The method according to claim 1 or 5, characterized in that the step B further comprises: the conversion of the data block content by the called conversion function is directly converted from the old version software to the new version software. 8. The method according to claim 1 or 5, wherein the step B further comprises: when setting the conversion function, attaching the conversion function to a linked list of pointers to the data blocks converted by the conversion function. 9. The method according to claim 1 or 5, wherein said step B further comprises: When the conversion function performs conversion, the entry parameter of the conversion function is the structure content of the converted data block of the old version software, and the exit parameter carries the structure content of the converted data block defined by the new version software.

Images