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

Abstract

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

Description

Technical Field

[0001] This application relates to the field of configuration synchronization technology, and in particular to a configuration data synchronization method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the rapid development of information technology, Software-Defined Networking (SDN), as an innovative network architecture, is gradually changing the landscape of traditional networks. Configuration synchronization, as a key component of SDN systems, is of great significance for maintaining network stability, improving service response speed, and reducing operational costs.

[0003] Currently, when the data of the master node in an SDN system changes, all configuration data in the master node needs to be transferred to the backup node to achieve synchronization of configuration data between the master and backup nodes.

[0004] However, in large-scale SDN systems, due to the massive amount of configuration data, each synchronization requires the transmission of a large amount of configuration data, resulting in significant delays in configuration data synchronization. Summary of the Invention

[0005] Therefore, it is necessary to provide a configuration data synchronization method, apparatus, device, storage medium, and program product that can reduce the latency of configuration data synchronization in response to the above-mentioned technical problems.

[0006] Firstly, this application provides a method for configuring data synchronization. The method includes:

[0007] In response to a data synchronization request sent by a client, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group, which is obtained by grouping the resource configuration data of the software-defined network (SDN) system.

[0008] Based on the hash values ​​of each node in the target sub-Merkle tree, determine the target leaf node that has changed;

[0009] Send 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-level 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 by the client to synchronize configuration data.

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

[0011] In response 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; 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 based on the hash values ​​of each node in the second top-level Merkle tree.

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

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

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

[0016] Send a second target information to the client; the second target information includes the 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 by 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 based on 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 based on the first target information includes:

[0020] The transmission time window and transmission bandwidth are determined based on the first target information; the data transmission strategy includes the transmission time window and / or the transmission bandwidth.

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

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

[0023] Secondly, this application also provides a data synchronization configuration device. The device includes:

[0024] The first determining module is used to respond to the data synchronization request sent by the client and determine the target sub-Merkle tree that has changed based on the hash value of each node of the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group, which is obtained by grouping the resource configuration data of the software-defined network (SDN) system.

[0025] The second determining module is used to determine the target leaf node that has changed based on the hash value of each node in the target sub-Merkle tree;

[0026] The first sending module is used to send 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-level 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 by the client to synchronize configuration data.

[0027] Thirdly, this application also provides a computer device, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of any of the above methods.

[0028] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above methods.

[0029] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above methods.

[0030] The aforementioned configuration data synchronization method, apparatus, device, storage medium, and program product, in response to a data synchronization request sent by a client, determines the target sub-Merkle tree that has changed based on the hash values ​​of each node in the top-level Merkle tree, determines the target leaf node that has changed based on the hash values ​​of each node in the target sub-Merkle tree, and sends first target information to the client, 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-level node of the target leaf node, and the hash value of the root node of the top-level Merkle tree, for the client to perform configuration data synchronization. This allows for the determination of the target leaf node that has changed layer by layer based on a hierarchical Merkle tree, improving the targeting of configuration data synchronization. Furthermore, it only requires the transmission of the first target information related to the target leaf node that has changed, reducing the amount of data transmitted during configuration data synchronization, increasing the speed of configuration data synchronization, and reducing the latency of configuration data synchronization. Attached Figure Description

[0031] Figure 1 This is an internal structural diagram of a computer device provided in an embodiment of this application;

[0032] Figure 2 This is a flowchart illustrating a configuration data synchronization method provided in an embodiment of this application;

[0033] Figure 3 This is a timing diagram of a sub-Merkle tree construction provided in an embodiment of this application;

[0034] Figure 4 This is a schematic diagram of a Merkle tree structure provided in an embodiment of this application;

[0035] Figure 5 This is a flowchart illustrating a method for determining a target sub-Merkle tree provided in an embodiment of this application;

[0036] Figure 6 This is a timing diagram for configuring data synchronization provided in an embodiment of this application;

[0037] Figure 7 This is a flowchart illustrating another configuration data synchronization method provided in an embodiment of this application;

[0038] Figure 8 This is another timing diagram for configuring data synchronization provided in an embodiment of this application;

[0039] Figure 9 This is a timing diagram of a first target information transmission provided in an embodiment of this application;

[0040] Figure 10This is a flowchart illustrating a configuration data synchronization method for an SDN system based on a hierarchical Merkle tree, provided in an embodiment of this application.

[0041] Figure 11 This is a flowchart illustrating a method for synchronizing configuration data between primary and backup nodes according to an embodiment of this application.

[0042] Figure 12 This is a structural block diagram of a data synchronization device provided in an embodiment of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0044] With the rapid development of information technology, Software-Defined Networking (SDN), as an innovative network architecture, is gradually changing the landscape of traditional networks. Configuration synchronization, as a key component of SDN systems, is of great significance for maintaining network stability, improving service response speed, and reducing operational costs.

[0045] Currently, when the data of the master node in an SDN system changes, all configuration data in the master node needs to be transferred to the backup node to achieve synchronization of configuration data between the master and backup nodes.

[0046] However, in large-scale SDN systems, due to the massive amount of configuration data, each synchronization requires the transmission of a large amount of configuration data, resulting in significant delays in configuration data synchronization.

[0047] The configuration data synchronization method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown. Figure 1 This is an internal structure diagram of a computer device provided in an embodiment of this 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, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a configuration data synchronization method.

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

[0049] In one embodiment, such as Figure 2 As shown, Figure 2 This is a flowchart illustrating a configuration data synchronization method provided in an embodiment of this application. This method can be applied to... Figure 1 The method, using a computer device, includes the following steps:

[0050] S201, in response to a data synchronization request sent by the client, determines the target sub-Merkle tree that has changed based on the hash values ​​of each node in the top-level Merkle tree.

[0051] The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group, which is obtained by grouping the resource configuration data of the software-defined networking (SDN) system.

[0052] In one embodiment, resource configuration data from an SDN system can be obtained and divided into multiple configuration data groups based on characteristics such as resource type and access mode. Then, the hash value of each data item in each configuration data group is calculated, and a corresponding sub-Merkle tree is constructed for each configuration data group based on these hash values. Next, the hash value of the root node of each sub-Merkle tree (i.e., the root hash value) is obtained, and a top-level Merkle tree is constructed based on the root hash values ​​of each sub-Merkle tree.

[0053] It's important to note that in the constructed top-level Merkle tree and sub-Merkle trees, the hash value of each parent node is obtained by linking the hash values ​​of its child nodes. This means that a change in the resource configuration data corresponding to a node will not only change the hash value of that node, but also the hash values ​​of all its parent nodes. These parent nodes include the node's parent node, grandparent node, and even higher-level ancestor nodes.

[0054] Optional, refer to Figure 3 , Figure 3 This is a timing diagram for constructing a sub-Merkle tree, as provided in an embodiment of this application. It can be based on, for example... Figure 3The steps shown are as follows to construct a sub-Merkle tree: Resource configuration data from the SDN system is obtained; the resource configuration data is preprocessed using a preprocessor; then, the feature classifier calls the SDN northbound interface to divide the preprocessed resource configuration data into multiple configuration data groups based on features such as resource type and access mode. Logical configuration data groups are then formed according to the divided configuration data groups, and a corresponding sub-Merkle tree is constructed for each configuration data group based on the hash value of each data point in each configuration data group.

[0055] For example, refer to Figure 4 , Figure 4 This is a schematic diagram of a Merkle tree structure provided in an embodiment of this application. The sub-Merkle trees and top-level Merkle trees 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 in the top-level Merkle tree is the root hash value of each sub-Merkle tree. Therefore, 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. During the configuration data synchronization process, the client can send a resource synchronization request to the server. After receiving the resource synchronization request from the client, the server can respond to the request by determining the changed nodes of the top-level Merkle tree based on the hash value of the root node of the second top-level Merkle tree on the server's local machine, and then determining the changed target sub-Merkle tree based on the changed nodes of the top-level Merkle tree.

[0057] In another embodiment, after receiving a resource synchronization request from the client, the server can obtain the first hash value of the root node of the first top-level Merkle tree on the client's local machine, and the second hash value of the root node of the second top-level Merkle tree on the server's local machine. Then, the first hash value and the second hash value are compared. If they are inconsistent, the changed node of the top-level Merkle tree is determined based on the hash value of the root node of the second top-level Merkle tree on the server's local machine, and the changed target sub-Merkle tree is then determined based on the changed node. If they are consistent, no configuration data synchronization is required, and a notification message can be sent to the client to indicate that the configuration data is consistent with the server's and no synchronization is needed.

[0058] S202, determine the target leaf node that has changed based on 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 that node, but also change the hash values ​​of all the nodes above that node, the node that has changed 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. Similarly, the nodes that have changed in the target sub-Merkle tree can be determined layer by layer until the target leaf node that has changed is found.

[0060] S203, send the first target information to the client.

[0061] 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-level 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 by the client to synchronize configuration data.

[0062] In one embodiment, after determining the target leaf node, first target information can be sent to the client, containing the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the parent node of the target leaf node, and the hash value of the root node of the top-level Merkle tree. After receiving the first target information, the client can update each sub-Merkle tree and the first top-level Merkle tree locally 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 for configuring data synchronization provided in an embodiment of this application, which can be based on, as follows: Figure 6The steps shown are for configuring data synchronization: After receiving a resource synchronization request from the client, the server can obtain the first hash value of the root node of the first top-level Merkle tree on the client's local machine from the resource synchronization request, and obtain the second hash value of the root node of the second top-level Merkle tree on the server's local machine. Then, the first hash value is compared with the second hash value. If the first hash value and the second hash value are inconsistent, the node of the changed top-level Merkle tree is determined based on the hash value of the root node of the second top-level Merkle tree on the server. Then, the changed target sub-Merkle tree is determined based on the changed top-level Merkle tree node. The changed node in the next level of the target sub-Merkle tree is determined based on the root hash value in the target sub-Merkle tree. The changed node in the target sub-Merkle tree is determined layer by layer in a similar process until the changed target leaf node is found. The first target information containing the resource configuration data corresponding to the target leaf node, the hash value of the target leaf node, the hash value of the upper-level 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. If the first hash value and the second hash value are consistent, no configuration data synchronization is required. A prompt message can be sent to the client to indicate that the configuration data of the client and the server are consistent and no synchronization is required.

[0064] Optionally, after completing 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 matches the second hash value, it indicates that the configuration data has been synchronized, and the client then sends a data synchronization result indicating successful data synchronization to the server. If the first hash value does not match the second hash value, the client can identify the abnormal node in its local Merkle tree based on the inconsistent hash values, and then send a data synchronization result containing the abnormal node to the server. After receiving the data synchronization result containing the abnormal node, the server can identify the target node corresponding to the abnormal node in its local Merkle tree, 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 then re-synchronize the configuration data based on 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 this embodiment, in response to a data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the top-level Merkle tree. Based on the hash values ​​of each node in the target sub-Merkle tree, the target leaf node that has changed is determined. 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-level 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 configuration data synchronization. This allows the target leaf node that has changed to be determined layer by layer based on the hierarchical Merkle tree, improving the targeting of configuration data synchronization. Furthermore, only the first target information related to the target leaf node that has changed needs to be transmitted, reducing the amount of data transmitted during configuration data synchronization, increasing the speed of configuration data synchronization, and reducing the latency of configuration data synchronization.

[0066] To more clearly illustrate the beneficial effects of the embodiments of this application, a comparison is made here between the configuration data synchronization method in the embodiments of this application and the traditional configuration data synchronization method:

[0067] When using the configuration data synchronization method in the embodiments of this application to perform configuration data synchronization, it is assumed that there are a total of There are leaf nodes, distributed in... On average, each sub-Merkle tree contains [number] sub-Merkle trees. The top-level Merkle tree contains leaf nodes and includes leaf nodes. With a number of nodes, the efficiency improvement in configuration data synchronization can be expressed by the following formula (1):

[0068] (1)

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

[0070] When using traditional configuration data synchronization methods, assume the total size of the resource configuration data is... The size of the changed resource configuration data is .

[0071] When using the configuration data synchronization method in this application embodiment to synchronize configuration data, it is assumed that the total size of the hash values ​​that need to be transmitted in the Merkle tree is... In theory, only transmission and Related hash values, but in practical applications, Compared to It is usually very small and can be ignored, or treated as a constant. Therefore, the data that needs to be transmitted when using the configuration data synchronization method in this application embodiment for configuration data synchronization can be approximated as follows: Therefore, compared to traditional methods, the transmission resources saved by the configuration data synchronization method in this application embodiment can be expressed as the following formula (2):

[0072] (2)

[0073] In formula (2), The percentage of transmission resources saved. According to formula (2), the configuration data synchronization method in this embodiment can save transmission resources significantly compared to traditional methods.

[0074] Reference Figure 5 , Figure 5 This is a flowchart illustrating a method for determining a target sub-Merkle tree according to an embodiment of this application. This embodiment relates to a possible implementation of how to determine the changed target sub-Merkle tree based on the hash values ​​of each node in the top-level Merkle tree in response to a data synchronization request sent by a client. Based on the above embodiment, S201 includes the following steps:

[0075] S501, in response to a data synchronization request, obtains 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.

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

[0077] In one embodiment, the data synchronization request may include a first hash value of the root node of the first top-level Merkle tree on the client's local machine. 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 on the client's local machine from the resource synchronization request, and obtain the second hash value of the root node of the second top-level Merkle tree on the server's local machine.

[0078] S502, if the first hash value and the second hash value are inconsistent, then 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.

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

[0080] Alternatively, if the first hash value is the same as the second hash value, then configuration data synchronization is not required. A prompt message can be sent to the client to indicate that the configuration data of the client and the server are consistent and no synchronization is needed.

[0081] In this embodiment, in response 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 based on the hash values ​​of each node of the second top-level Merkle tree. Because in this embodiment, before configuring data synchronization, the current resource configuration data of the client and the resource configuration data of the server are compared. If the current resource configuration data is consistent, data synchronization is not required; only if the current resource configuration data is inconsistent is configuration data synchronization required. This avoids repeated configuration data synchronization when the current resource configuration data is consistent.

[0082] Reference Figure 7 , Figure 7 This is a flowchart illustrating another configuration data synchronization method provided in this application. Based on the above embodiments, the method further includes the following steps:

[0083] S701 receives the data synchronization result sent by the 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 and the second hash value are consistent, it means that the configuration data has been synchronized, and then the client sends 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 and the second hash value are inconsistent, the client can identify the abnormal node in its local Merkle tree based on the inconsistent hash value, and then send the data synchronization result containing the abnormal node to the server.

[0086] S702, if the data synchronization result includes abnormal nodes, 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 its sub-Merkle trees.

[0088] Optionally, after receiving the data synchronization result containing the abnormal node, the server can determine the target node corresponding to the abnormal node from the server's local Merkle tree.

[0089] S703 sends the second target information to the client.

[0090] The second target information includes the 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 by the client to synchronize configuration data.

[0091] In one embodiment, the server can send a 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.

[0092] For example, refer to Figure 8 , Figure 8 This is another timing diagram for configuring data synchronization provided in an embodiment of this application. It can be achieved through methods such as... Figure 8 The steps shown are as follows for configuration data synchronization: After receiving a resource synchronization request from the client, the server determines the first target information, generates a digital signature corresponding to the first target information, and then sends the first target information and the corresponding digital signature to the client. Upon receiving the first target information and the corresponding digital signature from the server, the client performs integrity verification and digital signature validity verification based on the digital signature. If the first target information is found to be complete and the digital signature valid, configuration data synchronization is performed based on the first target information.

[0093] Optionally, if integrity verification based on the digital signature determines that the first target information is incomplete, an aberrant node can be identified in the client's local Merkle tree, and a data synchronization result containing the aberrant node can be sent to the server. Upon receiving the data synchronization result containing the aberrant node, the server can identify the target node corresponding to the aberrant node from its local Merkle tree 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 this embodiment, the data synchronization result sent by the client is received. If the data synchronization result includes an abnormal node, the 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. This enables the configuration data synchronization to be re-performed based on the second target information of the target node corresponding to the abnormal node in the event of an abnormal configuration data synchronization, thereby improving the reliability and security of configuration data synchronization.

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

[0096] The data transmission strategy is determined based on 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. Based on the first target information and the real-time network condition assessment results, the transmission time window for transmitting the first target information is adjusted with the goal of maximizing the configuration data synchronization efficiency. 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 transmission bandwidth. In this case, the transmission bandwidth can be determined based on the size of the first target information, and then the first target information can be 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 transmission bandwidth. Based on the first target information and the real-time network condition assessment results, the transmission time window for transmitting the first target information can be adjusted with the goal of maximizing the configuration data synchronization efficiency. The transmission bandwidth can be determined according to the size of the first target information, and then the first target information can 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 can also be transmitted using a method similar to that described above.

[0101] In this embodiment of the application, a data transmission strategy is determined based on the first target information, and the first target information is sent to the client according to the data transmission strategy. This improves the accuracy of the first target information transmission, reduces the latency of configuration data synchronization while performing configuration data synchronization, maximizes the utilization of transmission resources, and saves transmission resources.

[0102] Based on the above embodiments, determining the data transmission strategy according to the first target information can be achieved in the following ways:

[0103] The transmission time window and transmission bandwidth are determined based on the first target information; the data transmission strategy includes the transmission time window and / or transmission bandwidth.

[0104] For example, refer to Figure 9 , Figure 9 This is a timing diagram of a first target information transmission provided in an embodiment of this application. It can be achieved through, as shown below... Figure 9 The steps shown are as follows: monitor the network condition, obtain the real-time network condition assessment result, adjust the transmission time window according to the real-time network condition assessment result and the first target information, 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 this embodiment, the transmission time window and transmission bandwidth are determined based on the first target information, thereby enabling the first target information to be sent to the client based on the adjusted transmission time window under the constraint of transmission bandwidth. This improves the accuracy of the first target information transmission, reduces the delay of configuration data synchronization while performing configuration data synchronization, maximizes the utilization of transmission resources, and saves transmission resources.

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

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

[0108] In one embodiment, resource configuration data from an SDN system can be obtained and divided into multiple configuration data groups based on characteristics such as resource type and access mode. Then, the hash value of each data item in each configuration data group is calculated, and a corresponding sub-Merkle tree is constructed for each configuration data group based on these hash values. Next, the hash value of the root node of each sub-Merkle tree (i.e., the root hash value) is obtained, and a top-level Merkle tree is constructed based on the root hash values ​​of each sub-Merkle tree.

[0109] It's important to note that in the constructed top-level Merkle tree and sub-Merkle trees, the hash value of each parent node is obtained by linking the hash values ​​of its child nodes. This means that a change in the resource configuration data corresponding to a node will not only change the hash value of that node, but also the hash values ​​of all its parent nodes. These parent nodes include the node's parent node, grandparent node, and even higher-level ancestor nodes.

[0110] In this embodiment, for each configuration data group, a sub-Merkle tree is constructed based on the hash value of each data in the configuration data group, thereby enabling configuration data synchronization based on the hierarchical Merkle tree. This improves the targeting of configuration data synchronization, and only the first target information related to the changed target leaf node needs to be transmitted during configuration data synchronization, reducing the amount of data transmission during configuration data synchronization, improving the speed of configuration data synchronization, and reducing the latency of configuration data synchronization.

[0111] Reference Figure 10 , Figure 10 This is a flowchart illustrating a configuration data synchronization method for an SDN system based on a hierarchical Merkle tree, provided in an embodiment of this application. The method includes the following steps:

[0112] S1001 groups the 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 based on the hash value of each data in the configuration data group.

[0114] S1003, construct the top-level Merkle tree based on the root hash value of each sub-Merkle tree.

[0115] S1004, in response to the data synchronization request, obtain 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.

[0116] S1005, if the first hash value and the second hash value are inconsistent, then 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.

[0117] S1006, Based on the hash values ​​of each node in the target sub-Merkle tree, determine the target leaf node that has changed.

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

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

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

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

[0122] To provide a clearer description of the embodiments of this application, the following is combined with... Figure 11 An example is provided. Figure 11 This is a flowchart illustrating a method for synchronizing configuration data between primary and backup nodes according to an embodiment of this application. A hierarchical Merkle tree can be constructed on the primary node of the distributed system, and the hash value of the root node of the top-level Merkle tree is broadcast to the backup node. The backup 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 backup node's top-level Merkle tree matches that of the primary node's top-level Merkle tree, the configuration data between the primary and backup nodes is synchronized. If the hash value of the root node of the backup node's top-level Merkle tree does not match that of the primary node's top-level Merkle tree, a data synchronization request is sent to the primary node. In response to the data synchronization request, the primary node sends first target information related to the changed target leaf node to the backup node. The standby node performs configuration data synchronization based on the first target information and updates its local Merkle tree. Then, it 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 master node. If they are consistent, the configuration data synchronization is completed. If they are inconsistent, the above configuration data synchronization steps are repeated.

[0123] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0124] Based on the same inventive concept, this application also provides a configuration data synchronization device for implementing the configuration data synchronization method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more configuration data synchronization device embodiments provided below can be found in the limitations of the configuration data synchronization method described above, and will not be repeated here.

[0125] In one embodiment, such as Figure 12 As shown, Figure 12 This is a structural block diagram of a data synchronization device provided in an embodiment of this application. The device 1200 includes:

[0126] The first determining 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 based on the hash values ​​of each node of the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group. Each configuration data group is obtained by grouping the resource configuration data of the software-defined network (SDN) system.

[0127] The second determining module 1202 is used to determine the target leaf node that has changed based on the hash value of each node in the target sub-Merkle tree.

[0128] The first sending module 1203 is used to send first target information to the client; the first target information includes resource configuration data corresponding to the target leaf node, hash value of the target leaf node, hash value of the upper-level node of the target leaf node and 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] The acquisition unit is used to, in response to a data synchronization request, acquire 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; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree.

[0131] The first determining unit is used to determine the target sub-Merkle tree that has changed based on 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 device 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 abnormal nodes; each Merkle tree includes a second top-level Merkle tree and each sub-Merkle tree.

[0135] The second sending module is used to send 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 by the client to synchronize configuration data.

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

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

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

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

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

[0141] Each module in the aforementioned data synchronization device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0142] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0143] In response to the data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group. Each configuration data group is obtained by grouping the resource configuration data of the software-defined network (SDN) system.

[0144] Based on the hash values ​​of each node in the target sub-Merkle tree, determine the target leaf node that has changed;

[0145] 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-level 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 by the client to synchronize configuration data.

[0146] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0147] In response to a data synchronization request, obtain 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; 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 and the second hash value are inconsistent, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the second top-level Merkle tree.

[0149] In one embodiment, the processor, when executing a computer program, also performs the following steps:

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

[0151] If the data synchronization results include abnormal nodes, determine the target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes the second top-level Merkle tree and each sub-Merkle tree;

[0152] Send a second target information to the client; the second target information includes the 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 by the client to synchronize configuration data.

[0153] In one embodiment, the processor, when executing a computer program, also performs the following steps:

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

[0155] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0156] The transmission time window and transmission bandwidth are determined based on the first target information; the data transmission strategy includes the transmission time window and / or transmission bandwidth.

[0157] In one embodiment, the processor, when executing a computer program, also performs the following steps:

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

[0159] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0160] In response to the data synchronization request sent by the client, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group. Each configuration data group is obtained by grouping the resource configuration data of the software-defined network (SDN) system.

[0161] Based on the hash values ​​of each node in the target sub-Merkle tree, determine the target leaf node that has changed;

[0162] 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-level 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 by the client to synchronize configuration data.

[0163] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0164] In response to a data synchronization request, obtain 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; 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 and the second hash value are inconsistent, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the second top-level Merkle tree.

[0166] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

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

[0168] If the data synchronization results include abnormal nodes, determine the target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes the second top-level Merkle tree and each sub-Merkle tree;

[0169] Send a second target information to the client; the second target information includes the 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 by the client to synchronize configuration data.

[0170] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0171] The data transmission strategy is determined based on 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, it further performs the following steps:

[0173] The transmission time window and transmission bandwidth are determined based on the first target information; the data transmission strategy includes the transmission time window and / or transmission bandwidth.

[0174] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

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

[0176] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs 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 based on the hash values ​​of each node in the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group. Each configuration data group is obtained by grouping the resource configuration data of the software-defined network (SDN) system.

[0178] Based on the hash values ​​of each node in the target sub-Merkle tree, determine the target leaf node that has changed;

[0179] 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-level 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 by the client to synchronize configuration data.

[0180] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0181] In response to a data synchronization request, obtain 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; 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 and the second hash value are inconsistent, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the second top-level Merkle tree.

[0183] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

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

[0185] If the data synchronization results include abnormal nodes, determine the target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes the second top-level Merkle tree and each sub-Merkle tree;

[0186] Send a second target information to the client; the second target information includes the 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 by the client to synchronize configuration data.

[0187] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

[0188] The data transmission strategy is determined based on 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, it further performs the following steps:

[0190] The transmission time window and transmission bandwidth are determined based on the first target information; the data transmission strategy includes the transmission time window and / or transmission bandwidth.

[0191] In one embodiment, when the computer program is executed by a processor, it further performs the following steps:

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

[0193] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media 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), magnetic 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. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0194] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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 embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for configuring data synchronization, characterized in that, The method is applied to a server, and the method includes: In response to a data synchronization request sent by a client, the target sub-Merkle tree that has changed is determined based on the hash values ​​of each node in the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group, which is obtained by grouping the resource configuration data of the Software-Defined Network (SDN) system. In the top-level Merkle tree and sub-Merkle trees, the hash value of each parent node is obtained by linking the hash values ​​of its child nodes. Based on the hash values ​​of each node in the target sub-Merkle tree, determine the target leaf node that has changed; Send 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-level 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; The step of responding to a data synchronization request sent by the client, and determining the target sub-Merkle tree that has changed based on the hash values ​​of each node in the top-level Merkle tree, includes: In response 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; 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 target sub-Merkle tree that has changed is determined based on the hash values ​​of each node of the second top-level Merkle tree. The method further includes: Receive the data synchronization result sent by the client; If the data synchronization result includes an abnormal node, determine the target node corresponding to the abnormal node in each Merkle tree of the server; each Merkle tree includes the second top-level Merkle tree and each sub-Merkle tree; Send 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 by the client to synchronize configuration data.

2. The method according to claim 1, characterized in that, Sending the first target information to the client includes: A data transmission strategy is determined based on the first target information, and the first target information is sent to the client according to the data transmission strategy.

3. The method according to claim 2, characterized in that, The step of determining the data transmission strategy based on the first target information includes: The transmission time window and transmission bandwidth are determined based on the first target information; the data transmission strategy includes the transmission time window and / or the transmission bandwidth.

4. The method according to claim 1, characterized in that, The method further includes: For each of the configuration data groups, a sub-Merkle tree is constructed based on the hash value of each data in the configuration data group.

5. A configuration data synchronization device, characterized in that, The device includes: The first determining module is used to respond to a data synchronization request sent by the client and determine the target sub-Merkle tree that has changed based on the hash values ​​of each node in the top-level Merkle tree. The hash value of each node is determined based on the root hash value of each sub-Merkle tree. Each sub-Merkle tree corresponds one-to-one with each configuration data group, and each configuration data group is obtained by grouping the resource configuration data of the software-defined network (SDN) system. In the top-level Merkle tree and the sub-Merkle trees, the hash value of each parent node is obtained by linking the hash values ​​of its child nodes. The second determining module is used to determine the target leaf node that has changed based on the hash value of each node in the target sub-Merkle tree; A first sending module is used to send 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-level 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 by the client to synchronize configuration data. The first determining module includes: The acquisition unit is configured to, in response to the data synchronization request, acquire 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; the top-level Merkle tree includes the first top-level Merkle tree and the second top-level Merkle tree; The first determining unit is configured to determine the target sub-Merkle tree that has changed based on 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. The device further includes: The receiving module is used to receive the data synchronization result sent by the client; The third determining 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 the second top-level Merkle tree and each sub-Merkle tree; The second sending module is used to send 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 by the client to synchronize configuration data.

6. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

Images