Network configuration method and device, computer equipment and computer readable storage medium

Abstract

The invention relates to a network configuration method and device, computer equipment and a computer readable storage medium. The method comprises the following steps: based on a first multicast group address, issuing a configuration update message to each network element device in a first multicast group; wherein the configuration update message comprises configuration update information, the configuration update information is used for performing configuration update on each network element device, and after each network element device obtains a configuration update result, the configuration update result is sent to a second multicast group in the multicast network through a configuration confirmation message and a second multicast group address; and summarizing the configuration confirmation messages received by the second multicast group, and determining a comprehensive configuration result of each network element device based on the configuration confirmation messages. By adopting the method, the network configuration efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of network management technology and intelligent operation and maintenance technology, and in particular to a network configuration method, apparatus, computer equipment and computer-readable storage medium. Background Art

[0002] As the scale of SDN (Software Defined Networking SDN) networks continues to expand, errors may lead to network performance degradation, security vulnerabilities, and even network outages. Therefore, configuration reconciliation has become one of the key technologies to maintain the health of SDN networks. In large networks, the configuration consistency of network devices is the key to ensuring the normal operation of the network.

[0003] In traditional technology, the configuration delivery and reconciliation method is usually that the controller in the SDN network uses unicast to deliver configuration information to all network element devices in the SDN network one by one, and traverses to obtain the configuration information of all network element devices during the configuration reconciliation process, and compares and analyzes them one by one to obtain the configuration reconciliation results of each network element device.

[0004] However, in the conventional technology, configuration information is sent down in a unicast manner, and configuration reconciliation needs to be performed on each network element device one by one. When the network scale is large, the efficiency of configuration sending and configuration reconciliation is low. Summary of the invention

[0005] Based on this, it is necessary to provide a network configuration method, apparatus, computer device and computer-readable storage medium to address the above technical problems.

[0006] In a first aspect, the present application provides a network configuration method, the method being applied to a controller in a multicast network, the multicast network also including a network element device, and for different multicast addresses, dividing the network element devices included in the multicast network into different multicast groups, the method comprising:

[0007] Based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message includes configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address;

[0008] The configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation messages, a comprehensive configuration result of each of the network element devices is determined.

[0009] In one of the embodiments, before sending the configuration update message to each network element device in the first multicast group based on the first multicast group address, the method further includes:

[0010] In response to the configuration update operation, the controller is locally updated based on the configuration update information, and a configuration file is generated according to a preset format;

[0011] A first verification code after the controller configuration is updated is generated based on the configuration file.

[0012] In one embodiment, sending a configuration update message to each network element device in the first multicast group based on the first multicast group address includes:

[0013] Generate a configuration update message in a preset organization mode based on the message type, the configuration update timestamp, the configuration update information and the first verification code;

[0014] The configuration update message is encrypted based on a preset symmetric encryption algorithm, and the configuration update message is sent to each network element device in the first multicast group based on the first multicast group address.

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

[0016] Start a first timer of a preset duration;

[0017] If the second multicast group receives the first configuration confirmation message sent by the network element device within the preset time period, it is determined that the configuration of the network element device is completed;

[0018] If the second multicast group receives the second configuration confirmation message sent by the network element device within the preset time period, the network element device that sends the second configuration confirmation message is reconfigured until the configuration of the network element device is completed within the preset time period.

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

[0020] Based on a preset time period, regularly sending a configuration reconciliation message to each network element device in the first multicast group, wherein the configuration reconciliation message includes configuration update information, and the configuration update information is used to perform configuration reconciliation on each of the network element devices;

[0021] The configuration confirmation messages received by the second multicast group are summarized, and the configuration reconciliation result of each of the network element devices is determined based on the configuration confirmation messages.

[0022] In a second aspect, the present application provides a network configuration method, which is applied to a network element device in a first multicast group in a multicast network, wherein the multicast network also includes a controller, and for different multicast addresses, the network element devices included in the multicast network are divided into different multicast groups, wherein the method includes:

[0023] Receiving a configuration update message sent by the controller, wherein the configuration update message includes configuration update information;

[0024] Performing configuration update processing on the network element device based on the configuration update information, and determining a configuration update result of the network element device after the configuration update processing;

[0025] Based on the second multicast group address and the confirmation suppression mechanism, it is determined whether to send the configuration update result of the network element device to the second multicast group to instruct the controller in the multicast network to obtain the comprehensive configuration result of the network element device.

[0026] In one of the embodiments, the receiving a configuration update message sent by the controller includes:

[0027] An encrypted configuration update message sent by the controller is received, and the encrypted configuration update message is decrypted based on a preset symmetric encryption algorithm to obtain a decrypted configuration update message.

[0028] In one embodiment, the configuration update message further includes a first verification code, and the performing configuration update processing on the network element device based on the configuration update information and determining the configuration update result of the network element device after the configuration update processing includes:

[0029] Based on the configuration update information, performing configuration update processing on the network element device to obtain a network element device after the configuration update;

[0030] Synchronously updating the configuration file according to the configuration update information, and generating a second verification code based on the updated configuration file;

[0031] A configuration reconciliation is performed based on the first verification code and the second verification code to determine a configuration update result of the network element device.

[0032] In one of the embodiments, determining whether to send the configuration update result of the network element device to the second multicast group based on the second multicast group address and the confirmation suppression mechanism includes:

[0033] If the first verification code is consistent with the second verification code, a first configuration update result is obtained;

[0034] Based on the confirmation suppression mechanism, a second timer with a random duration is started;

[0035] During the timing of the second timer, if the first configuration update result sent by other network element devices is not received, sending a first configuration confirmation message to the second multicast group;

[0036] The first configuration confirmation message includes information about the first configuration update result.

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

[0038] During the timing of the second timer, if the first configuration update result sent by other network element devices is received, the first configuration confirmation message is suppressed from being sent to each network element device included in the second multicast group.

[0039] In one of the embodiments, determining whether to send the configuration update result of the network element device to the second multicast group based on the second multicast group address and the confirmation suppression mechanism includes:

[0040] If the first verification code and the second verification code are inconsistent, obtaining a second configuration update result;

[0041] Sending a second configuration confirmation message to each network element device and controller included in the second multicast group;

[0042] The second configuration confirmation message includes information about the second configuration update result.

[0043] In a third aspect, the present application further provides a network configuration device, which is applied to a controller in a multicast network, wherein the multicast network also includes a network element device, and for different multicast addresses, the network element devices included in the multicast network are divided into different multicast groups, wherein the device includes:

[0044] A sending module, configured to send a configuration update message to each network element device in the first multicast group based on the first multicast group address; the configuration update message contains configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address;

[0045] The determination module is used to summarize the configuration confirmation messages received by the second multicast group, and determine the comprehensive configuration results of each of the network element devices based on the configuration confirmation messages.

[0046] In a fourth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0047] Based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message includes configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address;

[0048] The configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation messages, a comprehensive configuration result of each of the network element devices is determined.

[0049] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0050] Based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message includes configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address;

[0051] The configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation messages, a comprehensive configuration result of each of the network element devices is determined.

[0052] In a sixth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0053] Based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message includes configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address;

[0054] The configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation messages, a comprehensive configuration result of each of the network element devices is determined.

[0055] The above-mentioned network configuration method, device, computer equipment and computer-readable storage medium, the method is applied to a controller in a multicast network, the multicast network also includes network element devices, for different multicast addresses, the network element devices contained in the multicast network are divided into different multicast groups, based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message contains configuration update information, the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address; the configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation message, the comprehensive configuration result of each network element device is determined. This method uses a one-time multicast method to send configuration update messages to the first multicast group based on the first multicast group address, which greatly improves the efficiency of configuration delivery and reduces network traffic and controller load. Secondly, through the confirmation suppression mechanism, the network element device reports the configuration confirmation message to the second multicast group, avoiding the tedious operation of one-by-one reconciliation and significantly shortening the reconciliation time. In addition, the multicast method optimizes the configuration delivery and reconciliation process, reduces the controller load, and improves network resource utilization and system performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0057] Figure 1 is a schematic diagram of the architecture of a first multicast group in a multicast network in an embodiment;

[0058] Figure 2 is a schematic diagram of the architecture of a second multicast group in a multicast network in an embodiment;

[0059] Figure 3 It is a flowchart of a network configuration method on the controller side in one embodiment;

[0060] Figure 4 A schematic diagram of a flow chart of generating a configuration file for configuring account reconciliation and a first verification code step in one embodiment;

[0061] Figure 5 A schematic diagram of a flow chart of steps for sending a configuration update message in a multicast manner in an embodiment;

[0062] Figure 6A schematic diagram of a flow chart of steps for receiving and processing configuration update results of each network element device in an embodiment;

[0063] Figure 7 A schematic diagram of a flow chart of a step of performing timed configuration reconciliation on each network element device in a multicast network in an embodiment;

[0064] Figure 8 A schematic diagram of a flow chart of a network configuration method on a network element device side in an embodiment;

[0065] Fig. 9 A schematic diagram of a flow chart of steps for decrypting a configuration update message in one embodiment;

[0066] Fig.10 A schematic flow chart of the steps of performing configuration update on a network element device to obtain a configuration update result in one embodiment;

[0067] Fig.11 A flowchart of a step of sending a first configuration confirmation message to a second multicast group based on a confirmation suppression mechanism in an embodiment;

[0068] Fig.12 A schematic diagram of a flow chart of canceling the step of sending a first configuration confirmation message to a second multicast group based on a confirmation suppression mechanism in an embodiment;

[0069] Fig.13 A schematic diagram of a flow chart of a step of sending a second configuration confirmation message to a second multicast group in an embodiment;

[0070] Fig.14 It is a structural block diagram of a network configuration device in one embodiment;

[0071] Fig.15 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0072] 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.

[0073] The network configuration method provided in the embodiment of the present application can be applied to a multicast network. Specifically, the network configuration method is applied to a controller in a multicast network, and the multicast network also includes network element devices. In the multicast network, the controller and each network element device are divided into different multicast groups based on different multicast addresses.

[0074] For example, to build a PIM-SM (Protocol Independent Multicast - Sparse Mode) multicast network, plan the multicast RP (Rendezvous Point) of the network, such as Figure 1 As shown in the figure, all network element devices join the first multicast group (represented by group1) and the second multicast group (represented by group2) respectively. Figure 2 As shown in the figure, all controllers only need to statically join the second multicast group (represented by group2). The multicast group address group1 is used by the controller to send configurations to all network elements. All network elements need to statically join the multicast group through IGMP (Internet Group Management Protocol). The multicast group address group2 is used by network elements to confirm configuration processing. All network elements and controllers need to join the multicast group.

[0075] Among them, group1: the first multicast group address: 228.1.1.1 port: 60010, group1 is used by the controller to multicast configuration update messages, configuration reconciliation messages, and configuration re-push messages to network element devices.

[0076] group2: Second multicast group address: 228.1.1.2 port: 60020 group2 is used by network element devices to multicast configuration confirmation messages to the controller and other network element devices.

[0077] Optionally, in order to improve the stability of the network system of the multicast network, a master and a standby controller are set in the multicast network. The master and standby controllers share a virtual address VIP (Virtual IP Address). The VIP takes effect on the master controller as the multicast source address for configuration distribution. The configuration information between the controllers is synchronized in real time through the database. In the embodiments of this application, unless otherwise specified, the following embodiments are all master controllers, which will not be repeated in the description of the following embodiments.

[0078] In an exemplary embodiment, Figure 3 As shown, a network configuration method is provided, which is applied to Figure 2 The controller in FIG. 1 is taken as an example to illustrate, and the method includes the following steps 302 to 304. Among them:

[0079] Step 302: Based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group.

[0080] In implementation, in a pre-planned multicast network, a symmetric encryption algorithm and an encryption key are pre-agreed between the controller and the network element devices, and all controllers and network element devices generate a configuration file in a pre-determined format and order for configuration reconciliation. Specifically, when processing a configuration update, the controller responds to the configuration update operation, performs configuration update processing on the controller based on the configuration update information, and synchronously updates the configuration file used for configuration reconciliation, records the configuration update time, and obtains an updated configuration timestamp. In this way, after the controller configuration update processing is performed, since all network element devices are included in the first multicast group, the controller can send a configuration update message to each network element device in the first multicast group in a multicast manner based on the first multicast group address.

[0081] The configuration update message includes configuration update information. The configuration update information is used to perform configuration update on each network element device so as to obtain configuration update results of each network element device. After each network element device obtains the configuration update result, each network element device sends the configuration update result to the second multicast group in the multicast network in the form of a configuration confirmation message based on the second multicast group address.

[0082] Optionally, the multicast source of the configuration update message is the controller vip, the multicast group address is group1, and the configuration update message may include the following content:

[0083] (1)Message type: 1.

[0084] (2) Timestamp: The timestamp of the controller's last configuration update.

[0085] (3) First verification code: the verification code of the configuration reconciliation file last updated by the controller, for example, MD5 value.

[0086] (4) Configuration update information: Configuration information that needs to be updated in this round.

[0087] Step 304: Summarize the configuration confirmation messages received by the second multicast group, and determine the comprehensive configuration result of each network element device based on the configuration confirmation messages.

[0088] In implementation, the second multicast group of the multicast network includes a controller, so that when the configuration update of each network element device is completed and a configuration confirmation message is sent to the second multicast group, the controller divided into the second multicast group can summarize the configuration confirmation messages received by the second multicast group group2. The configuration confirmation message contains the configuration update results of each network element device. In this way, the controller can determine the overall comprehensive configuration result based on the configuration update results of each network element device. If the configuration update result of the network element device indicates that the configuration update of the network element device is successful, then stop processing the network element device. If the configuration update result of the network element device indicates that the configuration update of the network element device is unsuccessful, then it is necessary to reconfigure the network element device, that is, re-push the configuration until the configuration update of the network element device is completed.

[0089] Optionally, the configuration confirmation message sent by the network element device to the second multicast group can be divided into a first configuration confirmation message and a second configuration confirmation message. The first configuration confirmation message indicates that the configuration update result is successful, that is, the first check code of the controller and the second check code of the network element device are consistent; the second configuration confirmation message indicates that the configuration update result is a configuration update failure, that is, the first check code of the controller and the second check code of the network element device are inconsistent. In the following embodiments, different configuration confirmation messages fed back by the network element device will be described in detail, which will not be repeated here.

[0090] In the above network configuration method, based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message contains configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address; the configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation message, the comprehensive configuration result of each network element device is determined. With this method, a configuration update message is sent to the first multicast group in a one-time multicast manner based on the first multicast group address, which greatly improves the efficiency of configuration sending and reduces network traffic and controller load; secondly, the network element device reports the configuration confirmation message to the second multicast group through the confirmation suppression mechanism, avoiding the tedious operation of one-by-one reconciliation and significantly shortening the reconciliation time. In addition, the configuration sending and reconciliation process is optimized through multicast, reducing the controller load, and improving the network resource utilization and system performance.

[0091] In an exemplary embodiment, Figure 4 As shown, before step 302, the network configuration method further includes:

[0092] Step 402: In response to the configuration update operation, a configuration update process is performed locally on the controller based on the configuration update information, and a configuration file is generated according to a preset format.

[0093] In implementation, the controller responds to the configuration update operation, performs configuration update processing on the controller locally based on the configuration update information, and generates a new configuration file for configuration reconciliation according to a preset format.

[0094] Step 404: Generate a first verification code after the controller configuration is updated based on the configuration file.

[0095] In implementation, the controller generates a first verification code after the controller configuration is updated based on the configuration file. For example, the first verification code is an MD5 value. The MD5 value is used to verify whether the configuration updates of the controller and each network element device are consistent.

[0096] Optionally, in the configuration update process, in addition to synchronously updating the configuration file, it is also necessary to update the timestamp of the configuration update, etc., so that the relevant information of the current round of configuration update is included in the configuration update message, and the configuration update message is sent to the first multicast group (group1). The configuration update message needs to be encrypted by a pre-agreed symmetric encryption algorithm to ensure the accuracy and information security of the configuration update message.

[0097] In this embodiment, the controller is configured to be updated, and a configuration file for configuration reconciliation is generated at the same time. An updated first verification code is generated based on the configuration file, and then the configuration update result of the network element device is reconciled with the help of the first verification code, thereby improving the accuracy and stability of the configuration update.

[0098] In an exemplary embodiment, Figure 5 As shown, the specific processing process of step 302 includes the following steps:

[0099] Step 501: Generate a configuration update message in a preset organization mode based on the message type, configuration update timestamp, configuration update information and a first verification code.

[0100] In implementation, the controller needs to integrate this information into a structured message, i.e., a configuration update message, according to the message type, configuration update timestamp, configuration update information, and the first check code in a preset organizational manner. Specifically, the message type is used to identify the purpose of the message (such as configuration update) to ensure that the receiver can correctly parse and process it; the configuration update timestamp records the specific time of the configuration update, which is used to track the order and timeliness of configuration changes; the configuration update information contains the actual configuration content or instructions, which is the core part of the message and is used to guide the receiver to complete the configuration update operation; the first check code is a unique identifier generated based on the configuration update information, which is used to verify the integrity and consistency of the message to prevent data from being tampered with or damaged during transmission.

[0101] Specifically, the information contained in the configuration update message can be expressed as:

[0102] (1) Message type: 1. (“1” indicates the configuration update message type)

[0103] (2) Timestamp: The timestamp of the controller's last configuration update.

[0104] (3) First verification code: the verification code of the configuration reconciliation file last updated by the controller, for example, MD5 value.

[0105] (4) Configuration update information: Configuration information that needs to be updated in this round.

[0106] Step 502: encrypt the configuration update message based on a preset symmetric encryption algorithm, and send the configuration update message to each network element device in the first multicast group based on the first multicast group address.

[0107] In implementation, in order to ensure the information security of the configuration update information, the controller encrypts the configuration update message containing the configuration update information based on a preset symmetric encryption algorithm (such as AES, DES, etc.) to obtain an encrypted configuration update message. Then, the controller sends the encrypted configuration update message to each network element device in the first multicast group based on the first multicast group address.

[0108] In this embodiment, by encrypting the configuration update message, the configuration update message is guaranteed to have strong security, and the message is prevented from being stolen or tampered with during transmission, thereby improving the security of the network configuration process.

[0109] In an exemplary embodiment, Figure 6 As shown, the method also includes:

[0110] Step 601: Start a first timer with a preset duration.

[0111] In implementation, after sending the configuration update message by multicast, the controller starts a first timer of a preset duration. Specifically, the first timer can be a 2-second timer, so that within 2 seconds, the controller waits to receive the configuration confirmation message fed back by the network element device.

[0112] Optionally, the preset duration of the first timer can be set based on actual conditions, which is not limited in the embodiments of the present application.

[0113] Among them, if there is a network element device whose configuration update result is a successful configuration update, then based on the pre-set confirmation suppression mechanism, a network element device is selected from the network element devices whose configuration update is successful, and the first configuration confirmation message is fed back to the second multicast group. If there is a network element device whose configuration update result is a failed configuration update, the network element device can directly feed back the second configuration confirmation message to the second multicast group, so that the controller can clearly understand the configuration update status of the network element device in the second multicast group. The following describes in detail the situation where the controller receives different configuration update messages.

[0114] Step 602: If the second multicast group receives the first configuration confirmation message sent by the network element device within the preset time period, it is determined that the configuration of the network element device is completed.

[0115] In implementation, the controller is included in the second multicast group, so that when the network element device sends a first configuration confirmation message to the second multicast group based on the second multicast group address, the controller can obtain the first configuration confirmation message. Specifically, if the second multicast group receives the first configuration confirmation message sent by the network element device within the timing duration (preset duration) of the first timer preset by the controller, the controller determines that the configuration of the network element device is complete. The network element devices represented by the first configuration confirmation message are all network element devices excluding those that send the second configuration confirmation message to the second multicast group. If no network element device sends the second configuration confirmation message to the second multicast group, it proves that all network element devices in the multicast network are configured (i.e., the configuration is successful).

[0116] Step 603: If the second multicast group receives the second configuration confirmation message sent by the network element device within the preset time period, the network element device that sends the second configuration confirmation message is reconfigured until the configuration of the network element device is completed within the preset time period.

[0117] In implementation, if the second multicast group receives the second configuration confirmation message sent by the network element device within the preset duration, it indicates that the configuration update of the network element device in the multicast network has failed in this round of configuration update process, and the network element that sent the second configuration confirmation message is the target network element device that failed the configuration update. In this way, the controller needs to reconfigure the network element device that sent the second configuration confirmation message (i.e., the target network element device), that is, re-push the configuration of the target network element device, and repeat steps 302 to 304 in the above configuration update process. In this way, until the controller completes the reconfiguration of the target network element device within the preset duration of the first timer.

[0118] In this embodiment, when the configuration of each network element device in the multicast network is updated, real-time configuration reconciliation of each network element device is completed, and after the real-time configuration reconciliation, customized configuration is promptly re-pushed for all network element devices that failed to update the configuration, to ensure the timeliness of the network element configuration update and the consistency of the network element device configuration.

[0119] In an exemplary embodiment, Figure 7 As shown, in addition to performing real-time configuration reconciliation on each network element device during this round of configuration update, in order to avoid the appearance of new network element devices in the multicast network, or the original network element devices in the multicast network being temporarily offline and then resuming communication, etc., resulting in the network element device not being updated in time, a periodic configuration consistency reconciliation mechanism is set in this embodiment to perform configuration reconciliation on each network element device in the current multicast network according to a preset period to avoid configuration inconsistency. Therefore, the method also includes:

[0120] Step 701: Based on a preset time period, a configuration reconciliation message is periodically sent to each network element device in the first multicast group.

[0121] The configuration reconciliation message includes configuration update information, and the configuration update information is used to perform configuration reconciliation on each network element device.

[0122] In implementation, the controller periodically sends configuration reconciliation messages to each network element device in the first multicast group based on a preset time period. The configuration reconciliation message includes: message type 3 (configuration reconciliation message), configuration update timestamp (main controller configuration update success timestamp) and configuration file summary MD5 value. Then, the controller organizes the message type 4 (configuration reconciliation message), configuration update timestamp and configuration file summary MD5 value information in an agreed manner, and encrypts them through a symmetric encryption algorithm to obtain an encrypted configuration reconciliation message. The controller sends the encrypted configuration reconciliation message to the first multicast group group1 based on the first multicast group address. In this way, after sending the configuration reconciliation message, the controller starts a 2s timer and waits for the reconciliation confirmation message from each network element device within the timer.

[0123] After receiving the configuration reconciliation message sent by the first multicast group group1, the network element device decrypts it according to the agreed symmetric encryption algorithm to obtain information such as message type 4 (configuration reconciliation message), configuration update timestamp, and the latest MD5 value of the controller. When the network element device identifies that the message type is configuration reconciliation, it compares the MD5 value of the controller with the MD5 value of the network element device after the configuration is updated. If the MD5 value of the network element device is inconsistent with the MD5 value sent by the controller, a multicast message (second configuration confirmation message) is immediately sent to the second multicast group group2. Specifically, the message content of the second configuration confirmation message includes message type 2 (network element configuration confirmation message), configuration update timestamp, network element device information, and configuration file summary MD5 value. In this way, after the network element device organizes the message content in the second configuration confirmation message in the agreed manner, it encrypts the second configuration confirmation message through the symmetric encryption algorithm, and sends the encrypted second configuration confirmation message to the second multicast group group2.

[0124] If the MD5 value of the network element device is consistent with the MD5 sent by the controller, the configuration confirmation suppression mechanism is started to determine whether the network element device sends the first configuration confirmation message to the second multicast group. The confirmation suppression mechanism will be described in detail in the following embodiments, and will not be repeated here. If the current network element needs to send the first configuration confirmation message to the second multicast group based on the judgment of the confirmation suppression mechanism, the network element device immediately sends a multicast message (i.e., the first configuration confirmation message) to the second multicast group group2. Specifically, the message content of the first configuration confirmation message includes information such as message type 2 (network element configuration confirmation message), configuration update timestamp, network element device information, and configuration file summary MD5 value. In this way, the current network element device organizes information such as message type 2 (network element configuration confirmation message), configuration update timestamp, network element device information, and configuration file summary MD5 value in an agreed manner, encrypts it through a symmetric encryption algorithm, obtains the encrypted first configuration confirmation message, and sends the encrypted first configuration confirmation message to the second multicast group group2.

[0125] Step 702: Summarize the configuration confirmation messages received by the second multicast group, and determine the configuration reconciliation results of each network element device based on the configuration confirmation messages.

[0126] In implementation, the controller in the second multicast group summarizes the received configuration confirmation messages (which may include at least one of the first configuration confirmation message and the second configuration confirmation message) before the first timer times out. Then, based on the configuration confirmation message, the controller identifies and determines the configuration reconciliation results of each network element device included in the current round of multicast network. For the configuration reconciliation results of each network element device, if the configuration reconciliation result indicates that there is a failure in the configuration update of a certain network element device, that is, the MD5 value of the network element device is inconsistent with the MD5 value of the controller, then the controller needs to re-push the configuration of the network element device. The controller starts to re-push from the minimum timestamp fed back by the inconsistently configured network element device. After the first timer expires, the message type 4 (configuration re-push message), configuration update timestamp (controller configuration update success timestamp), network element device information list to be re-pushed, configuration information, and configuration file summary MD5 contained in the message content are organized in an agreed manner, encrypted by a symmetric encryption algorithm, and the encrypted configuration re-push message is sent to the network element device of the first multicast group group1.

[0127] The re-push configuration information list is a re-push configuration information list sent by the controller. Each configuration information in the re-push configuration information list includes a timestamp and specific configuration information.

[0128] Re-push network element device information list: The re-push network element device information list sent by the controller contains the information of all network element devices to be re-push.

[0129] When the network element device in the first multicast group receives the configuration re-push message, it decrypts the message content based on the pre-defined preset encryption algorithm. If the current network element device itself is in the list of network element devices to be re-pushed, it is necessary to perform configuration update processing on the current network element device, and then perform configuration confirmation again in the manner described in the above process (i.e., compare the first verification code of the controller and the second verification code of the network element device). If the network element device is not in the list of network element devices to be re-pushed, the network element device does not need to process this configuration update task.

[0130] Optionally, when a new network element device needs to be deployed in the multicast network, the newly added network element device is also added to the second multicast group group2 and the first multicast group group1. In addition, when configuring static joining of the first multicast group group1, the network element device needs to immediately send a configuration confirmation message to the second multicast group group2 to trigger the controller to re-push the configuration for the network element device.

[0131] In addition, the scheduled configuration reconciliation process is similar to the real-time configuration reconciliation process included in the configuration update process. Both are based on the verification code of the configuration file (the first verification code of the controller and the second verification code of the network element device) to verify the configuration update results of each network element device, and re-configure the network element device with configuration problems (i.e., verification inconsistency) found in the configuration reconciliation process to achieve configuration consistency. Therefore, the technical means in the periodic scheduled configuration reconciliation process described in the embodiments of the present disclosure can be migrated to the real-time configuration reconciliation process, and the technical means in the real-time configuration reconciliation process can also be migrated to the scheduled configuration reconciliation process. In this way, the confirmation suppression mechanism will be described in detail in the following embodiments of this application, and the confirmation suppression mechanism is also applied to the scheduled configuration reconciliation process, but this embodiment will not be described in detail.

[0132] In this embodiment, based on the scheduled reconciliation update of the network element devices, it is ensured that the consistent configuration can be automatically restored after the failure of each network element device during the configuration update process, thereby ensuring the configuration consistency of each network element device in the multicast network.

[0133] In an exemplary embodiment, Figure 8 As shown, a network configuration method is provided, which is applied to a network element device in a first multicast group in a multicast network, wherein the multicast network also includes a controller, and the network element devices included in the multicast network are divided into different multicast groups according to different multicast addresses, and the method includes:

[0134] Step 801: Receive a configuration update message sent by a controller.

[0135] The configuration update message includes configuration update information.

[0136] In implementation, during the configuration update process of the multicast network to the network element device, the network element device in the first multicast group receives an encrypted configuration update message sent by the controller, the configuration update message includes configuration update information, and the configuration update information is used to perform configuration update processing on the current network element device.

[0137] Step 802: Perform configuration update processing on the network element device based on the configuration update information, and determine the configuration update result of the network element device after the configuration update processing.

[0138] In implementation, the network element device performs configuration update processing on the network element device based on the configuration update information, and determines the configuration update result of the network element device after the configuration update processing. Specifically, after receiving the configuration update message sent by the first multicast group group1, the network element device decrypts it according to the agreed symmetric encryption algorithm to obtain information such as message type 1 (configuration update message), configuration update timestamp, and the latest MD5 value of the controller. When the network element device identifies that the message type is a configuration update, it compares the MD5 value of the controller with the MD5 value of the network element device after the configuration is updated to obtain the configuration update result of the network element device.

[0139] Step 803: Based on the second multicast group address and the confirmation suppression mechanism, determine whether to send the configuration update result of the network element device to the second multicast group to instruct the controller in the multicast network to obtain the comprehensive configuration result of the network element device.

[0140] During implementation, after obtaining the configuration update result of the network element device, based on the difference in the configuration update result and the confirmation suppression mechanism (confirmation suppression mechanism) set between the network element devices, the network element device determines whether to send the configuration update result of the network element device itself to the second multicast group, so as to instruct the controller in the multicast network to determine the comprehensive configuration result of each network element device in the multicast network.

[0141] Specifically, if the configuration update result of the network element device is configuration update failure, the network element device needs to immediately send a multicast message (i.e., a second configuration confirmation message) to the second multicast group group2, so as to enable the controller to re-push the configuration of the current network element device. If the configuration update result of the network element device is configuration update success, the network element device sets a second timer of a random duration, and each network element device in the first multicast group sets a second timer of a random duration. Then, based on the confirmation suppression mechanism, among the second timers of random durations corresponding to each network element device, the network element device where the second timer with the earliest expiration is located is determined to send a multicast message (i.e., a first configuration confirmation message) to the second multicast group. Therefore, the second timer corresponding to the current network element device expires the earliest, and the current network element device needs to send the first configuration confirmation message to the second multicast group. At the same time, upon receiving the restriction of the first configuration confirmation message sent by the current network element device, other network element devices with successful configuration updates no longer send the first configuration confirmation message to the second multicast group. In this way, after the second multicast group receives the configuration update message sent by each network element device, the controller in the second multicast group determines the comprehensive configuration result of each network element device in the multicast network.

[0142] In this embodiment, the configuration of the network element device is updated based on the configuration update message sent by multicast, which greatly improves the efficiency of configuration sending and reduces network traffic and controller load; secondly, after completing the configuration update, the network element device decides whether to send the configuration update result to the second multicast group based on the second multicast group address and the confirmation suppression mechanism, effectively reducing redundant communications in the multicast network, avoiding the network bandwidth occupation problem that may be caused by multiple network element devices sending configuration confirmation messages to the controller one by one, and further enhancing the stability and reliability of the multicast network configuration update.

[0143] In an exemplary embodiment, Fig. 9 As shown, the specific processing process of step 801 includes:

[0144] Step 901: receiving an encrypted configuration update message sent by a controller, and decrypting the encrypted configuration update message based on a preset symmetric encryption algorithm to obtain a decrypted configuration update message.

[0145] In implementation, after the network element device receives the encrypted configuration update message sent by the controller, it decrypts the encrypted configuration update message based on the pre-agreed symmetric encryption algorithm and encryption key to obtain the decrypted plaintext configuration update message. Specifically, the configuration update message may include, but is not limited to:

[0146] (1) Message type: 1. (“1” indicates the configuration update message type)

[0147] (2) Timestamp: The timestamp of the controller's last configuration update.

[0148] (3) First verification code: the verification code of the configuration reconciliation file last updated by the controller, for example, MD5 value.

[0149] (4) Configuration update information: Configuration information that needs to be updated in this round.

[0150] Specifically, the message type is used to identify the purpose of the message (such as configuration update) to ensure that the recipient can correctly parse and process it; the configuration update timestamp records the specific time of the configuration update and is used to track the order and timeliness of configuration changes; the configuration update information contains the actual configuration content or instructions and is the core part of the message, used to guide the recipient to complete the configuration update operation; the first checksum is a unique identifier generated based on the configuration update information, which is used to verify the integrity and consistency of the message and prevent data from being tampered with or damaged during transmission.

[0151] In this embodiment, by decrypting the encrypted configuration update message, the strong security of the configuration update message is guaranteed, the message is prevented from being stolen or tampered with during the transmission process, and the security of the network configuration process is improved.

[0152] In one embodiment, if Fig.10 As shown, the configuration update message also includes a first verification code, and the specific processing process of step 802 includes:

[0153] Step 1001: Perform configuration update processing on a network element device based on configuration update information to obtain a network element device after configuration update.

[0154] In implementation, the network element device identifies the message type of the configuration update message. If the message type is configuration update, the network element device performs configuration update processing on its own device based on the configuration update information in the configuration update message to obtain a network element device after the configuration update.

[0155] Step 1002: Synchronously update the configuration file according to the configuration update information, and generate a second verification code based on the updated configuration file.

[0156] In implementation, during the configuration update process, the network element device synchronously updates the configuration file according to the configuration update information, and generates a second verification code of the network element device based on the updated configuration file, for example, the MD5 value of the network element device.

[0157] Step 1003: Perform configuration reconciliation based on the first verification code and the second verification code to determine a configuration update result of the network element device.

[0158] In implementation, the network element device performs configuration reconciliation for the obtained second verification code and the first verification code of the controller carried in the configuration update message, and compares the first verification code with the second verification code, thereby determining the configuration update result of its own device. Specifically, if the second verification code of the network element device is inconsistent with the first verification code sent by the controller, the configuration update result of the network element device is determined to be a configuration update failure; if the second verification code of the network element device is consistent with the first verification code sent by the controller, the configuration update result of the network element device is determined to be a configuration update success.

[0159] In this embodiment, configuration reconciliation is performed based on the first verification code and the second verification code corresponding to the configuration file, which can quickly and accurately determine the configuration update result of the network element device and ensure the integrity and consistency of the configuration update. The need for manual intervention is reduced and the complexity of operation is reduced. At the same time, the verification code reconciliation mechanism can quickly discover configuration anomalies, facilitate timely repair of problems, and enhance the maintainability and security of the system.

[0160] In an exemplary embodiment, Fig.11As shown, after the configuration reconciliation is performed based on the first verification code and the second verification code, different processing operations are subsequently performed for different configuration update results of the network element device. Therefore, for the case where the first verification code and the second verification code are consistent, the specific processing process of step 803 includes:

[0161] Step 1101: If the first verification code and the second verification code are consistent, a first configuration update result is obtained.

[0162] In implementation, if the first check code of the controller is consistent with the second check code of the network element device, the network element device determines that the first configuration update result is obtained, and the first configuration update result indicates that the configuration update of the network element device is successful. Specifically, taking the check code as an MD5 value as an example, when the latest configuration MD5 value (second check code) of the network element device is consistent with the MD5 value (first check code) issued by the controller, the network element device determines that the configuration update of its own device is successful, that is, the first configuration update result is obtained.

[0163] Step 1102: Based on the confirmation suppression mechanism, start a second timer with a random duration.

[0164] During implementation, the network element device starts a second timer of a random duration based on the confirmation suppression mechanism.

[0165] Specifically, after the configuration of the network element device is successfully updated, the network element device controls to update the timestamp of the last successful configuration of its own device to the configuration update timestamp contained in the configuration update message sent by the controller, and starts the configuration confirmation suppression mechanism at the same time, that is, starts a second timer with a random duration, which can be within the time range of 0.5~1.5 (unit, seconds). The second timer is used to suppress the sending of its own configuration confirmation message.

[0166] Step 1103: During the timing of the second timer, if no first configuration update result is received from other network element devices, a first configuration confirmation message is sent to the second multicast group.

[0167] The first configuration confirmation message includes information about the first configuration update result.

[0168] In implementation, for the pre-set confirmation suppression mechanism, before the second timer expires, the current network element device will not send the first configuration confirmation message to the second multicast group. Since the configuration update message is sent via multicast, the configurations of multiple network element devices in the multicast network are successfully updated within the same period. Therefore, since each network element device starts a second timer with a random duration, the random duration of the second timer started by each network element device is different. Therefore, in the case where the second timers expire one after another, it is possible to effectively suppress multiple network element devices in the multicast network from sending the first configuration confirmation message to the second multicast group one by one, that is, control the network element device that expires first to send the first configuration confirmation message, and suppress and cancel the sending of the first configuration confirmation message by each network element device that expires later, thereby reducing network bandwidth consumption.

[0169] In this way, during the timing of the second timer, the second timer of the current network element device expires, and the current network element device, as a network element device in the second multicast group, has not received the first configuration update result sent by other network element devices, which indicates that the second timer corresponding to the current network element device is the earliest expired timer, and the current network element device sends the first configuration update result of its own device to the second multicast group. Specifically, the first configuration update result is sent in the form of a first configuration confirmation message, wherein the message content of the first configuration confirmation message includes message type 2 (network element configuration confirmation message), configuration update timestamp, network element device information, and configuration file summary MD5, etc. In this way, the current network element device organizes the information contained in the message content of the first configuration confirmation message in a preset manner, encrypts the first configuration confirmation message through a symmetric encryption algorithm, and sends the encrypted first configuration message to the second multicast group group2.

[0170] In this embodiment, the second timer with a random duration is used to disperse the time for sending the first configuration confirmation message of each network element device. The network element device that expires first sends the first configuration confirmation message, while the device that expires later is suppressed and cancels the sending, thereby effectively reducing redundant communication in the network. This not only significantly reduces the consumption of network bandwidth, but also improves the stability and transmission efficiency of the network.

[0171] In an exemplary embodiment, Fig.12 As shown, during the timing of the second timer, if a first configuration update result sent by other network element devices is received, the current network element device is suppressed from sending the first configuration confirmation message to the second multicast group, and the method further includes:

[0172] Step 1201: During the timing of the second timer, if a first configuration update result sent by other network element devices is received, suppress sending a first configuration confirmation message to each network element device included in the second multicast group.

[0173] In implementation, during the timing of the second timer, if before the expiration of the second timer, the current network element device, as a network element device in the second multicast group, receives a first configuration update result sent by other network element devices (the network element device whose second timer expires earliest), and the first configuration update result is the same as the configuration update result to be sent by the current network element device, that is, both are consistent with the first verification code representing the controller and the second verification code of the network element device, indicating the first configuration update result of a successful configuration update, then the current network element device cancels the timing of the second timer and no longer sends the first configuration confirmation message.

[0174] In this embodiment, the confirmation suppression mechanism effectively avoids the problem of communication redundancy caused by multiple devices sending confirmation messages to the second multicast group one by one, thereby improving the stability and transmission efficiency of the network. In addition, the confirmation suppression mechanism reduces the repeated sending of configuration confirmation messages, reduces the processing pressure on the controller, and improves the real-time and accuracy of configuration management.

[0175] In an exemplary embodiment, Fig.13 As shown, the specific process of determining whether to send the configuration update result of the network element device to the second multicast group based on the second multicast group address and the confirmation suppression mechanism in step 803 includes:

[0176] Step 1301: If the first verification code and the second verification code are inconsistent, a second configuration update result is obtained.

[0177] In implementation, if the first verification code of the controller is inconsistent with the second verification code of the current network element device, it indicates that the configuration update of the current network element device fails, thereby obtaining the second configuration update result indicating the configuration update failure of the current network element device.

[0178] Step 1302: Send a second configuration confirmation message to each network element device and controller included in the second multicast group.

[0179] The second configuration confirmation message includes information about the second configuration update result.

[0180] In implementation, for network element devices that fail to update their configuration, the confirmation suppression mechanism is not adopted. Instead, the network element device directly reports to the second multicast group, instructing the second multicast group to re-push the configuration of the network element device. Therefore, for the second configuration update result of the current network element device, the current network element device sends a second configuration confirmation message to each network element device and controller included in the second multicast group. Specifically, taking the MD5 value as an example, when the latest MD5 value calculated by the current network element device is inconsistent with the MD5 sent by the controller, the network element device does not update the last successful configuration timestamp in its own device, and immediately sends a multicast message (i.e., the second configuration confirmation message) to the second multicast group group2. The message content of the second configuration confirmation message includes message type 2 (network element configuration confirmation message), the last successful configuration timestamp, network element device information, and configuration file summary MD5. In this way, the current network element device organizes the information contained in the message content of the second configuration confirmation message in a preset manner, encrypts the second configuration confirmation message through a symmetric encryption algorithm, and sends the encrypted second configuration message to the second multicast group group2 to instruct the controller in the second multicast group to re-push the configuration of the current network element device. The configuration re-push process for the network element device that failed to update the configuration has been described in the above embodiment, such as the content in the above step 702, and will not be repeated here.

[0181] In this embodiment, by sending the second configuration confirmation message to the second multicast group, the controller can promptly obtain information about the failure of the network element device configuration update, quickly locate the network element device configuration update problem and take configuration re-push, thereby improving the reliability and maintainability of the system.

[0182] It should be understood that, although the steps in the flowcharts involved in the above 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 is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may 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.

[0183] Based on the same inventive concept, the embodiment of the present application also provides a network configuration device for implementing the network configuration 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 network configuration device embodiments provided below can refer to the limitations on the network configuration method above, and will not be repeated here.

[0184] In an exemplary embodiment, Fig.14 As shown, a network configuration device 1400 is provided, including: a sending module 1401 and a determining module 1402, wherein:

[0185] The sending module 1401 is used to send a configuration update message to each network element device in the first multicast group based on the first multicast group address; the configuration update message contains configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through the configuration confirmation message and the second multicast group address;

[0186] The determination module 1402 is used to summarize the configuration confirmation messages received by the second multicast group, and determine the comprehensive configuration result of each network element device based on the configuration confirmation messages.

[0187] In one embodiment, the apparatus 1400 further includes:

[0188] A configuration update processing module, used to respond to the configuration update operation, perform configuration update processing on the controller locally based on the configuration update information, and generate a configuration file according to a preset format;

[0189] The generating module is used to generate a first verification code after the controller configuration is updated based on the configuration file.

[0190] In one embodiment, the sending module 1401 is specifically configured to generate a configuration update message in a preset organization mode based on the message type, the configuration update timestamp, the configuration update information, and the first verification code;

[0191] The configuration update message is encrypted based on a preset symmetric encryption algorithm, and the configuration update message is sent to each network element device in the first multicast group based on the first multicast group address.

[0192] In one embodiment, the apparatus 1400 further includes:

[0193] A starting module, used to start a first timer with a preset duration;

[0194] A receiving and confirming module, configured to determine that the configuration of the network element device is completed if the second multicast group receives the first configuration confirmation message sent by the network element device within a preset time period;

[0195] The configuration re-push module is used to reconfigure the network element device that sends the second configuration confirmation message if the second multicast group receives the second configuration confirmation message sent by the network element device within the preset time length, until the configuration of the network element device is completed within the preset time length.

[0196] In one embodiment, the apparatus 1400 further includes:

[0197] A timing sending module, used for sending a configuration reconciliation message to each network element device in the first multicast group based on a preset time period, wherein the configuration reconciliation message includes configuration update information, and the configuration update information is used for configuration reconciliation of each network element device;

[0198] The summary determination module is used to summarize the configuration confirmation messages received by the second multicast group, and determine the configuration reconciliation results of each network element device based on the configuration confirmation messages.

[0199] In one embodiment, another network configuration device is provided, which is applied to a network element device in a first multicast group in a multicast network, wherein the multicast network also includes a controller, and the network element devices included in the multicast network are divided into different multicast groups according to different multicast addresses, including:

[0200] A receiving module, used for receiving a configuration update message sent by the controller, wherein the configuration update message contains configuration update information;

[0201] A configuration update processing module, used to perform configuration update processing on the network element device based on the configuration update information, and determine the configuration update result of the network element device after the configuration update processing;

[0202] The determination module is used to determine whether to send the configuration update result of the network element device to the second multicast group based on the second multicast group address and the confirmation suppression mechanism, so as to instruct the controller in the multicast network to obtain the comprehensive configuration result of the network element device.

[0203] In one of the embodiments, the receiving module is specifically configured to receive an encrypted configuration update message sent by the controller, and decrypt the encrypted configuration update message based on a preset symmetric encryption algorithm to obtain a decrypted configuration update message.

[0204] In one of the embodiments, the configuration update message further includes a first verification code, and the configuration update processing module is specifically used to perform configuration update processing on the network element device based on the configuration update information to obtain the network element device after the configuration update;

[0205] Synchronously updating the configuration file according to the configuration update information, and generating a second verification code based on the updated configuration file;

[0206] A configuration reconciliation is performed based on the first verification code and the second verification code to determine a configuration update result of the network element device.

[0207] In one of the embodiments, the determination module is specifically configured to obtain a first configuration update result if the first verification code and the second verification code are consistent;

[0208] Based on the confirmation suppression mechanism, a second timer with a random duration is started;

[0209] During the timing of the second timer, if no first configuration update result sent by other network element devices is received, sending a first configuration confirmation message to the second multicast group;

[0210] The first configuration confirmation message includes information about the first configuration update result.

[0211] In one embodiment, the device further comprises:

[0212] The sending module is used to suppress sending the first configuration confirmation message to each network element device included in the second multicast group if a first configuration update result sent by other network element devices is received during the timing of the second timer.

[0213] In one of the embodiments, the determination module is specifically configured to obtain a second configuration update result if the first verification code and the second verification code are inconsistent;

[0214] Sending a second configuration confirmation message to each network element device and controller included in the second multicast group;

[0215] The second configuration confirmation message includes information about the second configuration update result.

[0216] Each module in the above network configuration 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.

[0217] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.15As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. 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 and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (Near Field Communication, NFC) or other technologies. When the computer program is executed by the processor, a network configuration method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0218] Those skilled in the art will understand that Fig.15 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.

[0219] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0220] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0221] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0222] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments 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 memory 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. 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, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0223] The technical features of the above embodiments may be combined arbitrarily. 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 application.

[0224] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations 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 network configuration method, characterized in that: The method is applied to a controller in a multicast network, wherein the multicast network also includes network element devices, and the network element devices included in the multicast network are divided into different multicast groups according to different multicast addresses. The method includes: Based on the first multicast group address, a configuration update message is sent to each network element device in the first multicast group; the configuration update message includes configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address; The configuration confirmation messages received by the second multicast group are summarized, and based on the configuration confirmation messages, a comprehensive configuration result of each of the network element devices is determined.

2. The method according to claim 1, characterized in that Before sending the configuration update message to each network element device in the first multicast group based on the first multicast group address, the method further includes: In response to the configuration update operation, the controller is locally updated based on the configuration update information, and a configuration file is generated according to a preset format; A first verification code after the controller configuration is updated is generated based on the configuration file.

3. The method according to claim 2, characterized in that The sending of the configuration update message to each network element device in the first multicast group based on the first multicast group address includes: Generate a configuration update message in a preset organization mode based on the message type, the configuration update timestamp, the configuration update information and the first verification code; The configuration update message is encrypted based on a preset symmetric encryption algorithm, and the configuration update message is sent to each network element device in the first multicast group based on the first multicast group address.

4. The method according to claim 3, characterized in that The method further comprises: Start a first timer of a preset duration; If the second multicast group receives the first configuration confirmation message sent by the network element device within the preset time period, it is determined that the configuration of the network element device is completed; If the second multicast group receives the second configuration confirmation message sent by the network element device within the preset time period, the network element device that sends the second configuration confirmation message is reconfigured until the configuration of the network element device is completed within the preset time period.

5. The method according to claim 1, characterized in that The method further comprises: Based on a preset time period, regularly sending a configuration reconciliation message to each network element device in the first multicast group, wherein the configuration reconciliation message includes configuration update information, and the configuration update information is used to perform configuration reconciliation on each of the network element devices; The configuration confirmation messages received by the second multicast group are summarized, and the configuration reconciliation result of each of the network element devices is determined based on the configuration confirmation messages.

6. A network configuration method, characterized in that: The method is applied to a network element device in a first multicast group in a multicast network, wherein the multicast network also includes a controller, and for different multicast addresses, the network element devices included in the multicast network are divided into different multicast groups, and the method includes: Receiving a configuration update message sent by the controller, wherein the configuration update message includes configuration update information; Performing configuration update processing on the network element device based on the configuration update information, and determining a configuration update result of the network element device after the configuration update processing; Based on the second multicast group address and the confirmation suppression mechanism, it is determined whether to send the configuration update result of the network element device to the second multicast group to instruct the controller in the multicast network to obtain the comprehensive configuration result of the network element device.

7. The method according to claim 6, characterized in that The receiving a configuration update message sent by the controller includes: An encrypted configuration update message sent by the controller is received, and the encrypted configuration update message is decrypted based on a preset symmetric encryption algorithm to obtain a decrypted configuration update message.

8. The method according to claim 6, characterized in that The configuration update message further includes a first check code, and the performing configuration update processing on the network element device based on the configuration update information and determining a configuration update result of the network element device after the configuration update processing includes: Based on the configuration update information, performing configuration update processing on the network element device to obtain a network element device after the configuration update; Synchronously updating the configuration file according to the configuration update information, and generating a second verification code based on the updated configuration file; A configuration reconciliation is performed based on the first verification code and the second verification code to determine a configuration update result of the network element device.

9. The method according to claim 8, characterized in that The determining whether to send the configuration update result of the network element device to the second multicast group based on the second multicast group address and the confirmation suppression mechanism includes: If the first verification code is consistent with the second verification code, a first configuration update result is obtained; Based on the confirmation suppression mechanism, a second timer with a random duration is started; During the timing of the second timer, if the first configuration update result sent by other network element devices is not received, sending a first configuration confirmation message to the second multicast group; The first configuration confirmation message includes information about the first configuration update result.

10. The method according to claim 9, characterized in that The method further comprises: During the timing of the second timer, if the first configuration update result sent by other network element devices is received, the first configuration confirmation message is suppressed from being sent to each network element device included in the second multicast group.

11. The method according to claim 8, characterized in that The determining whether to send the configuration update result of the network element device to the second multicast group based on the second multicast group address and the confirmation suppression mechanism includes: If the first verification code and the second verification code are inconsistent, obtaining a second configuration update result; Sending a second configuration confirmation message to each network element device and controller included in the second multicast group; The second configuration confirmation message includes information about the second configuration update result.

12. A network configuration device, characterized in that: The device is applied to a controller in a multicast network, the multicast network also includes network element devices, and the network element devices included in the multicast network are divided into different multicast groups according to different multicast addresses. The device includes: A sending module, configured to send a configuration update message to each network element device in the first multicast group based on the first multicast group address; the configuration update message contains configuration update information, and the configuration update information is used to update the configuration of each network element device, and after each network element device obtains the configuration update result, the configuration update result is sent to the second multicast group in the multicast network through a configuration confirmation message and a second multicast group address; The determination module is used to summarize the configuration confirmation messages received by the second multicast group, and determine the comprehensive configuration results of each of the network element devices based on the configuration confirmation messages.

13. 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, the steps of the method according to any one of claims 1 to 11 are implemented.

14. 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 11 are implemented.

Images