Configuration data synchronization method and device, equipment, storage medium and program product

Abstract

The invention relates to a configuration data synchronization method and device, equipment, a storage medium and a program product. The method comprises the steps of determining a changed target sub-Merkle tree according to a hash value of each node of a top-layer Merkle tree in response to a data synchronization request sent by a client, determining a changed target leaf node according to a hash value of each node in the target sub-Merkle tree, and synchronizing the changed target leaf node with the target leaf node according to the hash value of each node in the target leaf node. And sending first target information comprising resource configuration data corresponding to the target leaf node, a hash value of the target leaf node, a hash value of an upper-layer node of the target leaf node and a hash value of a root node of a top-layer Merkle tree to the client, so that the client performs configuration data synchronization. Therefore, the changed target leaf node can be determined layer by layer based on the hierarchical Merkle tree, the pertinence of configuration data synchronization is improved, only the first target information related to the changed target leaf node needs to be transmitted, the speed of configuration data synchronization is improved, and the delay of configuration data synchronization is reduced.

Description

Technical Field

[0001] The present application relates to the technical field of configuration synchronization, and in particular to a configuration data synchronization method, apparatus, device, storage medium and program product. Background Art

[0002] With the rapid development of information technology, Software-Defined Networking (SDN), as an innovative network architecture model, is gradually changing the traditional network landscape. Configuration synchronization, as a key link in the SDN system, is of great significance for maintaining network stability, improving business response speed, and reducing operation and maintenance costs.

[0003] Currently, when data of a master node in an SDN system changes, all configuration data in the master node needs to be transmitted to the standby node to synchronize the configuration data of the master node and the standby node.

[0004] However, in large-scale SDN systems, due to the huge amount of configuration data, each synchronization needs to transmit a large amount of configuration data, which leads to a large delay in configuration data synchronization. Summary of the invention

[0005] Based on this, it is necessary to provide a configuration data synchronization method, apparatus, device, storage medium and program product that can reduce the delay of configuration data synchronization in order to solve the above technical problems.

[0006] In a first aspect, the present application provides a configuration data synchronization method. The method comprises:

[0007] In response to the data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, and each sub-Merkle tree corresponds to each configuration data group one by one, and each configuration data group is obtained by grouping the resource configuration data of the software defined network SDN system;

[0008] According to the hash value of each node in the target sub-Merkle tree, determine the target leaf node that has changed;

[0009] Sending first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0010] In one embodiment, the response to the data synchronization request sent by the client, according to the hash value of each node of the top-level Merkle tree, determines the target sub-Merkle tree that has changed, including:

[0011] In response to the data synchronization request, obtaining a first hash value of a root node of a first top-level Merkle tree of the client and a second hash value of a root node of a second top-level Merkle tree of the server; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree;

[0012] If the first hash value and the second hash value are inconsistent, the target sub-Merkle tree that has changed is determined according to the hash values ​​of each node of the second top-level Merkle tree.

[0013] In one embodiment, the method further comprises:

[0014] Receive the data synchronization result sent by the client;

[0015] In the case where the data synchronization result includes an abnormal node, determining a target node corresponding to the abnormal node in each Merkle tree of the server; each of the Merkle trees includes the second top-level Merkle tree and each of the sub-Merkle trees;

[0016] Sending second target information to the client; the second target information includes resource configuration data corresponding to the target node, a hash value of the target node, and a hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

[0017] In one embodiment, sending the first target information to the client includes:

[0018] A data transmission strategy is determined according to the first target information, and the first target information is sent to the client according to the data transmission strategy.

[0019] In one embodiment, determining the data transmission strategy according to the first target information includes:

[0020] A transmission time window and a transmission bandwidth are determined according to the first target information; and the data transmission strategy includes the transmission time window and / or the transmission bandwidth.

[0021] In one embodiment, the method further comprises:

[0022] For each of the configuration data groups, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group.

[0023] In a second aspect, the present application also provides a configuration data synchronization device. The device includes:

[0024] A first determination module is used to respond to a data synchronization request sent by a client, and determine a target sub-Merkle tree that has changed according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, and each sub-Merkle tree corresponds to each configuration data group one by one, and each configuration data group is obtained by grouping resource configuration data of a software defined network SDN system;

[0025] A second determination module is used to determine the target leaf node that has changed according to the hash value of each node in the target sub-Merkle tree;

[0026] The first sending module is used to send the first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0027] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any of the above methods when executing the computer program.

[0028] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of any of the above methods when executed by a processor.

[0029] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of any of the above methods when executed by a processor.

[0030] The above-mentioned configuration data synchronization method, apparatus, equipment, storage medium and program product, by responding to the data synchronization request sent by the client, determine the changed target sub-Merkle tree according to the hash value of each node of the top-level Merkle tree, determine the changed target leaf node according to the hash value of each node in the target sub-Merkle tree, and send the first target information including the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree to the client for configuration data synchronization, so that the changed target leaf node can be determined layer by layer based on the hierarchical Merkle tree, thereby improving the targetedness of configuration data synchronization, and only the first target information related to the changed target leaf node needs to be transmitted, thereby reducing the amount of data transmission during configuration data synchronization, improving the speed of configuration data synchronization, and reducing the delay of configuration data synchronization. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 is an internal structure diagram of a computer device provided in an embodiment of the present application;

[0032] Figure 2 It is a flowchart of a configuration data synchronization method provided in an embodiment of the present application;

[0033] Figure 3 It is a timing diagram of constructing a sub-Merkle tree provided in an embodiment of the present application;

[0034] Figure 4 It is a schematic diagram of the structure of a Merkle tree provided in an embodiment of the present application;

[0035] Figure 5 It is a flowchart of a method for determining a target sub-Merkle tree provided in an embodiment of the present application;

[0036] Figure 6 It is a timing diagram of configuration data synchronization provided by an embodiment of the present application;

[0037] Figure 7 It is a flowchart of another configuration data synchronization method provided in an embodiment of the present application;

[0038] Figure 8 is another timing diagram of configuration data synchronization provided by an embodiment of the present application;

[0039] Fig. 9 is a timing diagram of first target information transmission provided by an embodiment of the present application;

[0040] Fig.10It is a flowchart of a configuration data synchronization method of an SDN system based on a hierarchical Merkle tree provided in an embodiment of the present application;

[0041] Fig.11 It is a flowchart of a method for synchronizing configuration data of a master and a standby node provided in an embodiment of the present application;

[0042] Fig.12 It is a structural block diagram of a configuration data synchronization device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0044] With the rapid development of information technology, Software-Defined Networking (SDN), as an innovative network architecture model, is gradually changing the traditional network landscape. Configuration synchronization, as a key link in the SDN system, is of great significance for maintaining network stability, improving business response speed, and reducing operation and maintenance costs.

[0045] Currently, when data of a master node in an SDN system changes, all configuration data in the master node needs to be transmitted to the standby node to synchronize the configuration data of the master node and the standby node.

[0046] However, in large-scale SDN systems, due to the huge amount of configuration data, each synchronization needs to transmit a large amount of configuration data, which leads to a large delay in configuration data synchronization.

[0047] The configuration data synchronization method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Figure 1 is an internal structure diagram of a computer device provided in an embodiment of the present application. The computer device may be a server, and its internal structure diagram may be as follows Figure 1 As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a configuration data synchronization method is implemented.

[0048] Those skilled in the art will understand that Figure 1 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0049] In one embodiment, Figure 2 As shown, Figure 2 is a flow chart of a configuration data synchronization method provided in an embodiment of the present application, which can be applied to Figure 1 In a computer device, the method comprises the following steps:

[0050] S201, in response to a data synchronization request sent by a client, determining a target sub-Merkle tree that has changed according to the hash value of each node of the top-level Merkle tree.

[0051] The hash value of each node is determined according to the root hash value of each sub-Merkle tree, each sub-Merkle tree corresponds to each configuration data group, and each configuration data group is obtained by grouping resource configuration data of the software defined network SDN system.

[0052] In one embodiment, resource configuration data in the SDN system can be obtained, and the resource configuration data in the SDN system can be divided into multiple configuration data groups according to characteristics such as resource type and access mode. Then, the hash value of each data in each configuration data group is calculated, and a corresponding sub-Merkle tree is constructed for each configuration data group according to the hash value of each data in each configuration data group. Then, the hash value of the root node of each sub-Merkle tree, that is, the root hash value, is obtained, and a top-level Merkle tree is constructed according to the root hash value of each sub-Merkle tree.

[0053] It should be noted that in the constructed top-level Merkle tree and child Merkle tree, the hash value of each parent node is obtained by linking the hash values ​​of its child nodes. In other words, changes in the resource configuration data corresponding to a node will not only change the hash value of the node, but also the hash values ​​of all upper-level nodes of the node. Among them, all upper-level nodes of a node include the node's parent node, grandparent node, and ancestor nodes at higher levels.

[0054] Optional, see Figure 3 , Figure 3 This is a timing diagram of a sub-Merkle tree construction provided in an embodiment of the present application. Figure 3The steps shown in the figure are used to construct a sub-Merkle tree: resource configuration data in the SDN system is obtained, the resource configuration data is preprocessed based on the preprocessor, and then the feature classifier calls the SDN northbound interface to divide the preprocessed resource configuration data into multiple configuration data groups according to the resource type, access mode and other features. According to the divided configuration data groups, the logical configuration data groups are configured, and according to the hash value of each data in each configuration data group, the corresponding sub-Merkle tree is constructed for each configuration data group.

[0055] For example, refer to Figure 4 , Figure 4 is a schematic diagram of the structure of a Merkle tree provided in an embodiment of the present application. The sub-Merkle tree and the top-level Merkle tree constructed according to the above method can be as follows: Figure 4 The structure shown.

[0056] In one embodiment, the hash value of each node of the top-level Merkle tree is the root hash value of each sub-Merkle tree, so the hash value of the root node of the top-level Merkle tree is obtained by linking the root hash values ​​of each sub-Merkle tree. In the process of configuring data synchronization, the client can send a resource synchronization request to the server. After receiving the resource synchronization request sent by the client, the server can respond to the resource synchronization request, determine the node of the top-level Merkle tree that has changed according to the hash value of the root node of the second top-level Merkle tree local to the server, and then determine the target sub-Merkle tree that has changed according to the node of the top-level Merkle tree that has changed.

[0057] In another embodiment, after receiving the resource synchronization request sent by the client, the server can obtain the first hash value of the root node of the first top-level Merkle tree of the client from the resource synchronization request, and obtain the second hash value of the root node of the second top-level Merkle tree from the server. Then compare the first hash value with the second hash value. If the first hash value is inconsistent with the second hash value, determine the node of the top-level Merkle tree that has changed based on the hash value of the root node of the second top-level Merkle tree of the server, and then determine the target sub-Merkle tree that has changed based on the node of the top-level Merkle tree that has changed; if the first hash value is consistent with the second hash value, there is no need to synchronize the configuration data, and a prompt message can be sent to the client to prompt that the configuration data of the client and the server are consistent and synchronization is not required.

[0058] S202, determining the target leaf node that has changed according to the hash value of each node in the target sub-Merkle tree.

[0059] In one embodiment, since a change in the resource configuration data corresponding to a node will not only change the hash value of the node, but also the hash values ​​of all upper-level nodes of the node, the changed nodes in the next layer of the target sub-Merkle tree can be determined based on the root hash value in the target sub-Merkle tree. Similar to the above process, the changed nodes in the target sub-Merkle tree are determined layer by layer until the changed target leaf node is found.

[0060] S203: Send first target information to the client.

[0061] Among them, the first target information includes the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0062] In one embodiment, after the target leaf node is determined, the first target information including the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node, and the hash value of the root node of the top-level Merkle tree can be sent to the client. After receiving the first target information, the client can update the local sub-Merkle trees and the first top-level Merkle tree of the client according to the first target information to achieve configuration data synchronization.

[0063] For example, refer to Figure 6 , Figure 6 This is a timing diagram of configuration data synchronization provided by an embodiment of the present application, which can be based on Figure 6The steps shown are used to synchronize configuration data: after the server receives the resource synchronization request sent by the client, it can obtain the first hash value of the root node of the first top-level Merkle tree of the client from the resource synchronization request, and obtain the second hash value of the root node of the second top-level Merkle tree from the server. Then compare the first hash value with the second hash value. If the first hash value is inconsistent with the second hash value, determine the node of the top-level Merkle tree that has changed according to the hash value of the root node of the second top-level Merkle tree locally on the server, and then determine the changed target sub-Merkle tree according to the node of the changed top-level Merkle tree, and determine the changed node in the next layer of the target sub-Merkle tree according to the root hash value in the target sub-Merkle tree. In a similar way to the above process, determine the changed nodes in the target sub-Merkle tree layer by layer until the changed target leaf node is found, and send the first target information including the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node, and the hash value of the root node of the top-level Merkle tree to the client; if the first hash value is consistent with the second hash value, there is no need to synchronize the configuration data, and a prompt message can be sent to the client to prompt that the configuration data of the client and the server are consistent and no synchronization is required.

[0064] Optionally, after completing the configuration data synchronization, the client can compare the first hash value of the root node of the first top-level Merkle tree with the second hash value of the root node of the second top-level Merkle tree. If the first hash value is consistent with the second hash value, it means that the configuration data has been synchronized, and then send the data synchronization result of successful data synchronization to the server; if the first hash value is inconsistent with the second hash value, the abnormal node can be determined in the local Merkle tree of the client according to the inconsistent hash value, and then send the data synchronization result containing the abnormal node to the server. After the server receives the data synchronization result containing the abnormal node, it can determine the target node corresponding to the abnormal node from the local Merkle tree of the server, and then send the hash value of the target node and the hash value of the root node of the second top-level Merkle tree to the client. The client can re-synchronize the configuration data according to the hash value of the target node and the hash value of the root node of the second top-level Merkle tree sent by the server.

[0065] In an embodiment of the present application, by responding to a data synchronization request sent by the client, the changed target sub-Merkle tree is determined according to the hash value of each node of the top-level Merkle tree, and the changed target leaf node is determined according to the hash value of each node in the target sub-Merkle tree, and the first target information including the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree is sent to the client for the client to synchronize the configuration data, so that the changed target leaf node can be determined layer by layer based on the hierarchical Merkle tree, thereby improving the targetedness of the configuration data synchronization, and only the first target information related to the changed target leaf node needs to be transmitted, thereby reducing the amount of data transmission during configuration data synchronization, improving the speed of configuration data synchronization, and reducing the delay of configuration data synchronization.

[0066] In order to more clearly introduce the beneficial effects of the embodiments of the present application, the configuration data synchronization method in the embodiments of the present application is compared with the traditional configuration data synchronization method:

[0067] When using the configuration data synchronization method in the embodiment of the present application to synchronize configuration data, it is assumed that there are leaf nodes, respectively distributed in On the Merkle tree, each Merkle tree includes an average of leaf nodes, the top-level Merkle tree includes nodes, so the efficiency improvement of configuration data synchronization can be expressed as the following formula (1):

[0068] (1)

[0069] In formula (1), is the percentage of configuration data synchronization efficiency improvement, which is the number of sub-Merkle trees that need to be synchronized. Often much smaller than , which means that the efficiency improvement of configuration data synchronization may be very significant, especially when only a small number of sub-Merkle trees need to be synchronized.

[0070] When using the traditional configuration data synchronization method to synchronize configuration data, assuming that the size of the full resource configuration data is , the size of the changed resource configuration data is .

[0071] When using the configuration data synchronization method in the embodiment of the present application to synchronize configuration data, it is assumed that the total size of the hash value to be transmitted in the Merkle tree is In theory, only the transmission and Related hash values, but in practical applications, Relative to Usually very small and can be ignored or considered a constant , then the data that needs to be transmitted when using the configuration data synchronization method in the embodiment of the present application to synchronize configuration data can be approximately Therefore, compared with the traditional method, the transmission resources saved by the configuration data synchronization method in the embodiment of the present application can be expressed as the following formula (2):

[0072] (2)

[0073] In formula (2), is the percentage of transmission resource savings. According to formula (2), the configuration data synchronization method in the embodiment of the present application can also greatly save transmission resources compared with the traditional method.

[0074] Reference Figure 5 , Figure 5 : is a flow chart of a method for determining a target sub-Merkle tree provided by an embodiment of the present application. This embodiment involves a possible implementation method of how to respond to a data synchronization request sent by a client and determine a changed target sub-Merkle tree according to the hash value of each node of the top-level Merkle tree. Based on the above embodiment, the above S201 includes the following steps:

[0075] S501, in response to a data synchronization request, obtaining a first hash value of a root node of a first top-level Merkle tree of a client and a second hash value of a root node of a second top-level Merkle tree of a server.

[0076] The top-level Merkle tree includes a first top-level Merkle tree and a second top-level Merkle tree.

[0077] In one embodiment, the data synchronization request may include the first hash value of the root node of the first top-level Merkle tree of the client. After the server receives the resource synchronization request sent by the client, the first hash value of the root node of the first top-level Merkle tree of the client may be obtained from the resource synchronization request, and the second hash value of the root node of the second top-level Merkle tree may be obtained from the server.

[0078] S502: If the first hash value and the second hash value are inconsistent, determine the target sub-Merkle tree that has changed according to the hash value of each node of the second top-level Merkle tree.

[0079] In one embodiment, the first hash value can be compared with the second hash value. If the first hash value is inconsistent with the second hash value, the node of the top-level Merkle tree that has changed is determined based on the hash value of the root node of the second top-level Merkle tree locally on the server, and then the target sub-Merkle tree that has changed is determined based on the node of the top-level Merkle tree that has changed.

[0080] Alternatively, if the first hash value is consistent with the second hash value, there is no need to synchronize the configuration data, and a prompt message may be sent to the client to prompt that the configuration data of the client and the server are consistent and synchronization is not required.

[0081] In an embodiment of the present application, by responding to the data synchronization request, the first hash value of the root node of the first top-level Merkle tree of the client and the second hash value of the root node of the second top-level Merkle tree of the server are obtained. If the first hash value and the second hash value are inconsistent, the target sub-Merkle tree that has changed is determined according to the hash values ​​of each node of the second top-level Merkle tree. In an embodiment of the present application, before synchronizing the configuration data, the resource configuration data of the current client and the resource configuration data of the server are compared. If the current resource configuration data are consistent, data synchronization is not required. If the current resource configuration data are inconsistent, configuration data synchronization is required. Therefore, when the current resource configuration data are consistent, repeated configuration data synchronization can be avoided.

[0082] Reference Figure 7 , Figure 7 FIG. 1 is a flow chart of another configuration data synchronization method provided in an embodiment of the present application. Based on the above embodiment, the method further includes the following steps:

[0083] S701, receiving a data synchronization result sent by a client.

[0084] In one embodiment, after completing the configuration data synchronization, the client can compare the first hash value of the root node of the first top-level Merkle tree with the second hash value of the root node of the second top-level Merkle tree. If the first hash value is consistent with the second hash value, it means that the configuration data has been synchronized, and then send the data synchronization result of successful data synchronization to the server.

[0085] Alternatively, after completing the configuration data synchronization, the client can compare the first hash value of the root node of the first top-level Merkle tree with the second hash value of the root node of the second top-level Merkle tree. If the first hash value is inconsistent with the second hash value, the abnormal node can be determined in the local Merkle tree of the client based on the inconsistent hash values, and then the data synchronization result including the abnormal node can be sent to the server.

[0086] S702: When the data synchronization result includes an abnormal node, determine the target node corresponding to the abnormal node in each Merkle tree of the server.

[0087] Each Merkle tree includes a second top-level Merkle tree and each sub-Merkle tree.

[0088] Optionally, after receiving the data synchronization result including the abnormal node, the server may determine the target node corresponding to the abnormal node from the local Merkle tree of the server.

[0089] S703: Send second target information to the client.

[0090] The second target information includes resource configuration data corresponding to the target node, a hash value of the target node, and a hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

[0091] In one embodiment, the server may send the second target information to the client. After receiving the second target information, the client may re-synchronize the configuration data according to the hash value of the target node sent by the server and the hash value of the root node of the second top-level Merkle tree.

[0092] For example, refer to Figure 8 , Figure 8 is another timing diagram of configuration data synchronization provided by an embodiment of the present application. Figure 8 The steps shown are used to synchronize configuration data: after receiving the resource synchronization request sent by the client, the server can determine the first target information, generate a digital signature corresponding to the first target information, and then send the first target information and the digital signature corresponding to the first target information to the client. After receiving the first target information sent by the server and the digital signature corresponding to the first target information, the client can perform integrity verification and digital signature validity verification based on the digital signature. When it is determined that the first target information is complete and the digital signature is valid, the configuration data is synchronized based on the first target information.

[0093] Optionally, if the first target information is determined to be incomplete after integrity verification based on the digital signature, an abnormal node can be determined in the local Merkle tree of the client, and then a data synchronization result containing the abnormal node can be sent to the server. After receiving the data synchronization result containing the abnormal node, the server can determine the target node corresponding to the abnormal node from the local Merkle tree of the server, and then send the second target information to the client. After receiving the second target information, the client can reconfigure data synchronization based on the hash value of the target node sent by the server and the hash value of the root node of the second top-level Merkle tree.

[0094] In an embodiment of the present application, a data synchronization result sent by the client is received, and when the data synchronization result includes an abnormal node, a target node corresponding to the abnormal node in each Merkle tree of the server is determined, and second target information is sent to the client. Therefore, when the configuration data synchronization is abnormal, the configuration data synchronization can be re-performed according to the second target information of the target node corresponding to the abnormal node, thereby improving the reliability and security of the configuration data synchronization.

[0095] Based on the above embodiment, the above S203 includes the following steps:

[0096] A data transmission strategy is determined according to the first target information, and the first target information is sent to the client according to the data transmission strategy.

[0097] In one embodiment, the data transmission strategy may include a transmission time window. The transmission time window for transmitting the first target information may be adjusted based on the first target information and the real-time network status evaluation results, with the goal of maximizing the configuration data synchronization efficiency, and then the first target information is sent to the client based on the adjusted transmission time window.

[0098] Alternatively, the data transmission strategy may include a transmission bandwidth, and the transmission bandwidth may be determined according to the size of the first target information, and then the first target information is sent to the client under the constraint of the transmission bandwidth to maximize the utilization of transmission resources and save transmission resources.

[0099] Alternatively, the data transmission strategy may include a transmission time window and a transmission bandwidth. The transmission time window for transmitting the first target information may be adjusted based on the first target information and the real-time network status evaluation results, with the goal of maximizing the configuration data synchronization efficiency, and the transmission bandwidth may be determined based on the size of the first target information. Then, the first target information may be sent to the client based on the adjusted transmission time window under the constraint of the transmission bandwidth.

[0100] Similarly, the second target information may also be transmitted using a method similar to the above.

[0101] In an embodiment of the present application, a data transmission strategy is determined based on the first target information, and the first target information is sent to the client based on the data transmission strategy, thereby improving the accuracy of the transmission of the first target information, reducing the delay in configuration data synchronization while synchronizing configuration data, maximizing the utilization of transmission resources, and saving transmission resources.

[0102] Based on the above embodiment, determining the data transmission strategy according to the first target information can be implemented in the following manner:

[0103] A transmission time window and a transmission bandwidth are determined according to the first target information; and a data transmission strategy includes a transmission time window and / or a transmission bandwidth.

[0104] For example, refer to Fig. 9 , Fig. 9 is a timing diagram of a first target information transmission provided by an embodiment of the present application. Fig. 9 The steps shown transmit the first target information: monitor the network status, obtain real-time network status evaluation results, adjust the transmission time window according to the real-time network status evaluation results and the first target information, and determine the transmission bandwidth according to the first target information, and then send the first target information to the client based on the adjusted transmission time window under the constraint of the transmission bandwidth.

[0105] In an embodiment of the present application, the transmission time window and the transmission bandwidth are determined based on the first target information, so that the first target information can be sent to the client based on the adjusted transmission time window under the constraint of the transmission bandwidth, thereby improving the accuracy of the transmission of the first target information, reducing the delay in configuration data synchronization while synchronizing the configuration data, maximizing the utilization of transmission resources, and saving transmission resources.

[0106] Based on the above embodiment, the method further includes the following steps:

[0107] For each configuration data group, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group.

[0108] In one embodiment, resource configuration data in the SDN system can be obtained, and the resource configuration data in the SDN system can be divided into multiple configuration data groups according to characteristics such as resource type and access mode. Then, the hash value of each data in each configuration data group is calculated, and a corresponding sub-Merkle tree is constructed for each configuration data group according to the hash value of each data in each configuration data group. Then, the hash value of the root node of each sub-Merkle tree, that is, the root hash value, is obtained, and a top-level Merkle tree is constructed according to the root hash value of each sub-Merkle tree.

[0109] It should be noted that in the constructed top-level Merkle tree and child Merkle tree, the hash value of each parent node is obtained by linking the hash values ​​of its child nodes. In other words, changes in the resource configuration data corresponding to a node will not only change the hash value of the node, but also the hash values ​​of all upper-level nodes of the node. Among them, all upper-level nodes of a node include the node's parent node, grandparent node, and ancestor nodes at higher levels.

[0110] In an embodiment of the present application, for each configuration data group, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group, so that configuration data synchronization can be performed based on the hierarchical Merkle tree, thereby improving the targeted nature of the configuration data synchronization, and during configuration data synchronization, only the first target information related to the target leaf node that has changed needs to be transmitted, thereby reducing the amount of data transmitted during configuration data synchronization, improving the speed of configuration data synchronization, and reducing the delay in configuration data synchronization.

[0111] Reference Fig.10 , Fig.10 1 is a flow chart of a configuration data synchronization method for an SDN system based on a hierarchical Merkle tree provided in an embodiment of the present application. The method comprises the following steps:

[0112] S1001, grouping resource configuration data of the SDN system to obtain multiple configuration data groups.

[0113] S1002: For each configuration data group, construct a sub-Merkle tree according to the hash value of each data in the configuration data group.

[0114] S1003, construct a top-level Merkle tree according to the root hash value of each sub-Merkle tree.

[0115] S1004, in response to the data synchronization request, obtaining a first hash value of the root node of the first top-level Merkle tree of the client and a second hash value of the root node of the second top-level Merkle tree of the server.

[0116] S1005: If the first hash value and the second hash value are inconsistent, determine the target sub-Merkle tree that has changed according to the hash value of each node of the second top-level Merkle tree.

[0117] S1006, determining the target leaf node that has changed according to the hash value of each node in the target sub-Merkle tree.

[0118] S1007, determine a transmission time window and a transmission bandwidth according to the first target information, and send the first target information to the client according to the transmission time window and the transmission bandwidth.

[0119] S1008, receiving the data synchronization result sent by the client.

[0120] S1009: When the data synchronization result includes an abnormal node, determine the target node corresponding to the abnormal node in each Merkle tree of the server.

[0121] S1010, sending second target information to the client.

[0122] In order to introduce the embodiments of the present application more clearly, Fig.11 An exemplary description is given. Fig.11 It is a flow chart of a method for synchronizing configuration data of a master and standby node provided in an embodiment of the present application. A hierarchical Merkle tree can be constructed at the master node of a distributed system, and the hash value of the root node of the top-level Merkle tree can be broadcast to the standby node. The standby node checks the hash value of the root node of the top-level Merkle tree. If the hash value of the root node of the top-level Merkle tree of the standby node is consistent with the hash value of the root node of the top-level Merkle tree of the master node, the configuration data of the master node and the standby node are synchronized; if the hash value of the root node of the top-level Merkle tree of the standby node is inconsistent with the hash value of the root node of the top-level Merkle tree of the master node, a data synchronization request is sent to the master node. In response to the data synchronization request, the master node sends the first target information related to the target leaf node that has changed to the standby node. The standby node performs configuration data synchronization according to the first target information, updates the local Merkle tree, and then re-determines whether the hash value of the root node of the top-level Merkle tree of the standby node is consistent with the hash value of the root node of the top-level Merkle tree of the primary node. If they are consistent, the configuration data synchronization is completed; if they are inconsistent, the above configuration data synchronization steps are re-executed.

[0123] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0124] Based on the same inventive concept, the embodiment of the present application also provides a configuration data synchronization device for implementing the configuration data synchronization method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more configuration data synchronization device embodiments provided below can refer to the above limitations on the configuration data synchronization method, and will not be repeated here.

[0125] In one embodiment, Fig.12 As shown, Fig.12 1 is a structural block diagram of a configuration data synchronization device provided in an embodiment of the present application. The device 1200 includes:

[0126] The first determination module 1201 is used to respond to the data synchronization request sent by the client, and determine the target sub-Merkle tree that has changed according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, and each sub-Merkle tree corresponds to each configuration data group one by one, and each configuration data group is obtained by grouping the resource configuration data of the software defined network SDN system.

[0127] The second determination module 1202 is used to determine the changed target leaf node according to the hash value of each node in the target sub-Merkle tree.

[0128] The first sending module 1203 is used to send the first target information to the client; the first target information includes the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0129] In one embodiment, the first determining module 1201 includes:

[0130] An acquisition unit is used to acquire, in response to a data synchronization request, a first hash value of a root node of a first top-level Merkle tree of a client and a second hash value of a root node of a second top-level Merkle tree of a server; the top-level Merkle tree includes a first top-level Merkle tree and a second top-level Merkle tree.

[0131] The first determining unit is used to determine the changed target sub-Merkle tree according to the hash values ​​of each node of the second top-level Merkle tree if the first hash value and the second hash value are inconsistent.

[0132] In one embodiment, the apparatus 1200 further includes:

[0133] The receiving module is used to receive the data synchronization results sent by the client.

[0134] The third determination module is used to determine the target node corresponding to the abnormal node in each Merkle tree of the server when the data synchronization result includes an abnormal node; each Merkle tree includes a second top-level Merkle tree and each sub-Merkle tree.

[0135] The second sending module is used to send the second target information to the client; the second target information includes resource configuration data corresponding to the target node, the hash value of the target node and the hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

[0136] In one embodiment, the first sending module 1203 includes:

[0137] The sending unit is used to determine a data transmission strategy according to the first target information, and send the first target information to the client according to the data transmission strategy.

[0138] In one of the embodiments, the sending unit is specifically configured to determine a transmission time window and a transmission bandwidth according to the first target information; and the data transmission strategy includes a transmission time window and / or a transmission bandwidth.

[0139] In one embodiment, the apparatus 1200 further includes:

[0140] The construction module is used to construct a sub-Merkle tree according to the hash value of each data in the configuration data group for each configuration data group.

[0141] Each module in the above configuration data synchronization device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0142] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0143] In response to the data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, and each sub-Merkle tree corresponds to each configuration data group one by one, and each configuration data group is obtained by grouping the resource configuration data of the software defined network SDN system;

[0144] Determine the target leaf node that has changed based on the hash value of each node in the target child Merkle tree;

[0145] Send the first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0146] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0147] In response to the data synchronization request, obtaining a first hash value of a root node of a first top-level Merkle tree of the client and a second hash value of a root node of a second top-level Merkle tree of the server; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree;

[0148] If the first hash value is inconsistent with the second hash value, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the second top-level Merkle tree.

[0149] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0150] Receive data synchronization results sent by the client;

[0151] In the case where the data synchronization result includes an abnormal node, determining a target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes a second top-level Merkle tree and each sub-Merkle tree;

[0152] The second target information is sent to the client; the second target information includes resource configuration data corresponding to the target node, the hash value of the target node and the hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

[0153] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0154] A data transmission strategy is determined according to the first target information, and the first target information is sent to the client according to the data transmission strategy.

[0155] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0156] A transmission time window and a transmission bandwidth are determined according to the first target information; and a data transmission strategy includes a transmission time window and / or a transmission bandwidth.

[0157] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0158] For each configuration data group, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group.

[0159] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0160] In response to the data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, and each sub-Merkle tree corresponds to each configuration data group one by one, and each configuration data group is obtained by grouping the resource configuration data of the software defined network SDN system;

[0161] Determine the target leaf node that has changed based on the hash value of each node in the target child Merkle tree;

[0162] Send the first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0163] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0164] In response to the data synchronization request, obtaining a first hash value of a root node of a first top-level Merkle tree of the client and a second hash value of a root node of a second top-level Merkle tree of the server; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree;

[0165] If the first hash value is inconsistent with the second hash value, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the second top-level Merkle tree.

[0166] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0167] Receive data synchronization results sent by the client;

[0168] In the case where the data synchronization result includes an abnormal node, determining a target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes a second top-level Merkle tree and each sub-Merkle tree;

[0169] The second target information is sent to the client; the second target information includes resource configuration data corresponding to the target node, the hash value of the target node and the hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

[0170] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0171] A data transmission strategy is determined according to the first target information, and the first target information is sent to the client according to the data transmission strategy.

[0172] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0173] A transmission time window and a transmission bandwidth are determined according to the first target information; and a data transmission strategy includes a transmission time window and / or a transmission bandwidth.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0175] For each configuration data group, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group.

[0176] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0177] In response to the data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, and each sub-Merkle tree corresponds to each configuration data group one by one, and each configuration data group is obtained by grouping the resource configuration data of the software defined network SDN system;

[0178] Determine the target leaf node that has changed based on the hash value of each node in the target child Merkle tree;

[0179] Send the first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

[0180] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0181] In response to the data synchronization request, obtaining a first hash value of a root node of a first top-level Merkle tree of the client and a second hash value of a root node of a second top-level Merkle tree of the server; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree;

[0182] If the first hash value is inconsistent with the second hash value, the target sub-Merkle tree that has changed is determined according to the hash value of each node of the second top-level Merkle tree.

[0183] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0184] Receive data synchronization results sent by the client;

[0185] In the case where the data synchronization result includes an abnormal node, determining a target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes a second top-level Merkle tree and each sub-Merkle tree;

[0186] The second target information is sent to the client; the second target information includes resource configuration data corresponding to the target node, the hash value of the target node and the hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

[0187] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0188] A data transmission strategy is determined according to the first target information, and the first target information is sent to the client according to the data transmission strategy.

[0189] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0190] A transmission time window and a transmission bandwidth are determined according to the first target information; and a data transmission strategy includes a transmission time window and / or a transmission bandwidth.

[0191] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0192] For each configuration data group, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group.

[0193] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0194] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0195] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A configuration data synchronization method, characterized in that: The method is applied to a server, and the method comprises: In response to a data synchronization request sent by a client, a target sub-Merkle tree that has changed is determined according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, each sub-Merkle tree corresponds to each configuration data group, and each configuration data group is obtained by grouping resource configuration data of a software defined network SDN system; Determine the target leaf node that has changed according to the hash value of each node in the target sub-Merkle tree; Sending first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

2. The method according to claim 1, characterized in that The responding to the data synchronization request sent by the client, determining the target sub-Merkle tree that has changed according to the hash value of each node of the top-level Merkle tree, includes: In response to the data synchronization request, obtaining a first hash value of a root node of a first top-level Merkle tree of the client and a second hash value of a root node of a second top-level Merkle tree of the server; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree; If the first hash value and the second hash value are inconsistent, the changed target sub-Merkle tree is determined according to the hash value of each node of the second top-level Merkle tree.

3. The method according to claim 2, characterized in that The method further comprises: Receiving the data synchronization result sent by the client; In the case where the data synchronization result includes an abnormal node, determining a target node corresponding to the abnormal node in each Merkle tree of the server; each of the Merkle trees includes the second top-level Merkle tree and each of the sub-Merkle trees; Sending second target information to the client; the second target information includes resource configuration data corresponding to the target node, a hash value of the target node, and a hash value of the root node of the second top-level Merkle tree; the second target information is used for the client to synchronize configuration data.

4. The method according to any one of claims 1 to 3, characterized in that: The sending the first target information to the client includes: A data transmission strategy is determined according to the first target information, and the first target information is sent to the client according to the data transmission strategy.

5. The method according to claim 4, characterized in that The determining of the data transmission strategy according to the first target information includes: A transmission time window and a transmission bandwidth are determined according to the first target information; and the data transmission strategy includes the transmission time window and / or the transmission bandwidth.

6. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: For each of the configuration data groups, a sub-Merkle tree is constructed according to the hash value of each data in the configuration data group.

7. A configuration data synchronization device, characterized in that: The device comprises: A first determination module is used to respond to a data synchronization request sent by a client, and determine a target sub-Merkle tree that has changed according to the hash value of each node of the top-level Merkle tree; the hash value of each node is determined according to the root hash value of each sub-Merkle tree, each sub-Merkle tree corresponds to each configuration data group, and each configuration data group is obtained by grouping resource configuration data of a software defined network SDN system; A second determination module is used to determine the target leaf node that has changed according to the hash value of each node in the target sub-Merkle tree; The first sending module is used to send the first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper node of the target leaf node and the hash value of the root node of the top-level Merkle tree; the first target information is used for the client to synchronize configuration data.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images