A method for implementing resynchronization of heterogeneous redundant protocols

Abstract

The present invention provides a method for implementing heterogeneous redundancy protocol resynchronization, comprising: in a dynamic heterogeneous redundancy architecture, performing scrubbing and resynchronization together with a protocol executor module via a negative feedback control message processing module, a scrubbing and resynchronization module, and a scheduling module; the negative feedback control message processing module controls message transmission in the scrubbing and resynchronization process; the scrubbing and resynchronization module controls the scrubbing and resynchronization process and the data migration therein; and the scheduling module implements timer reset in the scrubbing and resynchronization process. The present invention can perform scrubbing operations on heterogeneous protocol executors that have been attacked by unknown attacks within heterogeneous redundant mimetic architecture network devices, achieving complete recovery of the protocol executor's configuration data, status data, and state machine without affecting the normal forwarding of network services, thereby enhancing network security.

Description

Technical Field

[0001] The present invention relates to the technical field of heterogeneous redundancy mechanisms in mimetic network devices, and in particular to a method for implementing resynchronization of heterogeneous redundancy protocols. Background Art

[0002] In mimetic network devices, Layer 2 and 3 protocols (such as STP, OSPF, and PIM) have multiple heterogeneous executors. These executors may be taken offline for cleaning due to abnormal output under attack, reset as a preventive measure due to policy scheduling, or be forcibly restarted and resynchronized. How to quickly resynchronize the state with the online executor after cleaning, resetting, or reconfiguration operations is crucial to the effectiveness of heterogeneous redundancy mechanisms and the usability of defense scenarios.

[0003] Resynchronization mechanisms are similar to hot standby technology but are more complex and difficult to implement. Resynchronization mechanisms involve repairing or migrating large amounts of data files, but the mimicking heterogeneous mechanism prevents data migration from being simply implemented through memory mapping and data structure copying. Resynchronization mechanisms require that executors, after cleanup and recovery, synchronize with online executor timers and state machines, a difficult feat to achieve using existing hot standby technology. Routing protocol graceful restart technology enables hot standby with uninterrupted forwarding, but this technology places high demands on the external environment. It requires neighboring devices implementing uninterrupted forwarding technology to have corresponding graceful restart capabilities, and additional protocol messages are generated during the restart or negotiation process. Therefore, to achieve resynchronization of heterogeneous executors in mimicking network devices, a set of implementation methods must be designed to address current technical challenges, meet the technical requirements of mimicking synchronization and uninterrupted service, and minimize network impact. Summary of the Invention

[0004] The present invention aims to provide a method for implementing heterogeneous redundant protocol resynchronization to solve the problem of cleaning and resynchronizing heterogeneous protocol execution bodies in mimetic network devices.

[0005] The present invention provides a method for implementing heterogeneous redundancy protocol resynchronization, comprising:

[0006] In the dynamic heterogeneous redundant architecture, the negative feedback control message processing module, the cleaning and resynchronization module and the scheduling module work together with the protocol execution module to complete the cleaning and resynchronization;

[0007] The negative feedback control message processing module controls the process control of the cleaning and resynchronization process;

[0008] The cleaning and resynchronization module controls the cleaning and resynchronization process and the data migration therein;

[0009] The scheduling module implements synchronization event scheduling and timer resetting in the cleaning and resynchronization process.

[0010] Furthermore, the cleaning and resynchronization process includes:

[0011] a) When the inconsistency of the output decisions of the protocol executor reaches a set threshold, the multi-mode arbitrator notifies the negative feedback controller to start cleaning the protocol executor, and the negative feedback controller sends a cleaning start message to the cleaned protocol executor;

[0012] b) After receiving the cleaning start message, the cleaned protocol execution body performs route maintenance and starts cleaning preparation. After the cleaning preparation is completed, it sends a cleaning confirmation message to the negative feedback controller;

[0013] c) The negative feedback controller receives the cleaning confirmation message and simultaneously sends a cleaning confirmation ACK message to the three heterogeneous protocol executors;

[0014] d) After receiving the cleansing confirmation ACK message, the normal protocol executor collects local data and sends it to the negative feedback controller. The negative feedback controller selects the optimal data and forwards it to the cleaned protocol executor. After receiving the optimal data, the cleaned protocol executor first simulates the events that have occurred based on the received data to bring the cleaned protocol executor to the same state according to the protocol standard process. Then, data migration is performed to ensure that the state recording time of the three heterogeneous protocol executors is consistent.

[0015] e) After receiving the last data migration message from the normal protocol executor, the negative feedback controller sends a timer synchronization message to the three heterogeneous protocol executors, and the heterogeneous protocol executors synchronously reset the timers and refresh the routing tables;

[0016] f) After completing the timer synchronization, the heterogeneous protocol executor sends a synchronization decision message to the negative feedback controller, i.e., it re-decides the synchronized key information and sends the decision result to the multi-mode arbitrator and the heterogeneous protocol executor;

[0017] g) If the decision result is failure, the multi-mode arbiter re-initiates the cleaning and resynchronization process or modifies the strategy; if the decision result is success, the cleaned protocol executor and the multi-mode arbiter exit the cleaning and resynchronization state.

[0018] Furthermore, the cleaning start message includes protocol type information.

[0019] Furthermore, the cleaning preparation includes restarting the protocol execution body process, reinitializing to enter the initial state, or restoring the protocol execution body configuration.

[0020] Furthermore, the local data includes configuration data and status data.

[0021] Furthermore, the routing is maintained using a graceful restart mechanism.

[0022] The data migration is implemented by event simulation and protocol message simulation.

[0023] Furthermore, the data migration implementation method includes:

[0024] (1) When the configuration data is restarted, the configuration data shared by the heterogeneous protocol execution bodies is obtained from the negative feedback controller;

[0025] (2) During data migration, data is converted into the byte order and bit width that are unanimously recognized by the heterogeneous protocol execution bodies for storage and transmission;

[0026] (3) When migrating data, a custom format is used to differentiate protocols, differentiate sessions, identify data types, segment data, and migrate data effectively.

[0027] Furthermore, the timer synchronization implementation method includes:

[0028] Timers are divided into two categories for reset: periodic packet sending timers and timeout processing timers;

[0029] For periodic packet sending timers, the timer reset should be called back first and then restarted;

[0030] For timeout processing timers, the remaining time thread->u.sands should be directly reset without callback.

[0031] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are:

[0032] The heterogeneous redundant protocol resynchronization implementation method provided by the present invention can cleanse heterogeneous protocol execution bodies that have been attacked by unknown attacks within heterogeneous redundant mimetic architecture network devices, achieving complete recovery of the protocol execution body's configuration data, status data, and state machine without affecting the normal forwarding of network services, thereby enhancing network security. The present invention can also be used in hot standby technology to implement an uninterrupted routing hot standby mechanism without affecting network services, modifying protocol standards, or incurring additional network overhead, further improving the reliability of network devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings in the embodiments will be briefly introduced below. It should be understood that the following drawings only illustrate certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0034] Figure 1 This is a diagram of the dynamic heterogeneous redundancy architecture in an embodiment of the present invention.

[0035] Figure 2 This is a diagram of the protocol software composition in an embodiment of the present invention.

[0036] Figure 3 Flowchart of cleaning and resynchronization in an embodiment of the present invention.

[0037] Figure 4 The figure is a flow chart of a method for implementing route maintenance in an embodiment of the present invention.

[0038] Figure 5 Schematic diagram of a custom format used in data migration in an embodiment of the present invention. DETAILED DESCRIPTION

[0039] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings herein can be arranged and designed in various different configurations.

[0040] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention as claimed, but rather merely represents selected embodiments of the present invention. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without creative effort are intended to fall within the scope of protection of the present invention.

[0041] Example

[0042] like Figure 1 As shown in Figure 1, cyberspace mimicry defense is an active defense behavior that mainly targets unknown threats such as unknown vulnerabilities, backdoors, viruses or Trojans. Mimicry network devices introduce dynamic, random, and diverse defense elements based on closed-loop negative feedback control. It adopts a dynamic heterogeneous redundant architecture such as Figure 1 shown.

[0043] All software and hardware components in the dynamic heterogeneous redundant architecture are allowed to have different vulnerabilities; there are no forms of interactive communication links or connections between executors; unless the output state of the multi-mode arbiter is the desired consistent state, the feedback control loop always strives to achieve the desired output state of the multi-mode arbiter by changing the current operating environment or the arbitration algorithm. That is, under the condition that the service function remains unchanged, the target executor or construction scenario is dynamically replaced (migrated), cleaned and restored according to the control algorithm, and related background processing mechanisms (such as virus detection and antivirus, vulnerability and backdoor scanning and patching) are activated. Strategy scheduling, such as scheduling, can be implemented, so that known security risks and unknown security threats can be suppressed with normalized robust control functions.

[0044] Heterogeneous redundancy resynchronization refers to the process of restarting and recovering the protocol executor after it is offline, and resynchronizing with the running executor. Resynchronization requires that during the cleaning and recovery process of the protocol executor, the device's external performance should be as imperceptible to users, terminals, and neighboring devices as possible, and the cleaned executor can restore the synchronization state as soon as possible to ensure that the mimetic security defense capability is restored as soon as possible. Resynchronization technology is difficult to implement in the mimetic defense system. Existing network technologies (such as hot standby technology) make it difficult to achieve complete synchronization of the executor state machine after cleaning and recovery, and the recovery speed is fast and does not affect network services. The present invention uses uninterrupted forwarding technology to maintain routing during the cleaning phase, and uses information copying and event simulation technology to realize data migration. Finally, the state machine synchronization of the executor is guaranteed through the modification of the scheduling machine. The corresponding protocol software consists of: the protocol software that provides the resynchronization function adds mimetic synchronization, cleaning resynchronization, and negative feedback control message processing on the basis of the original protocol software, such as Figure 2 Therefore, this embodiment proposes a method for implementing heterogeneous redundancy protocol resynchronization, including:

[0045] In the dynamic heterogeneous redundant architecture, the negative feedback control message processing module, the cleaning and resynchronization module and the scheduling module work together with the protocol execution module to complete the cleaning and resynchronization;

[0046] The negative feedback control message processing module controls the process control of the cleaning and resynchronization process;

[0047] The cleaning and resynchronization module controls the cleaning and resynchronization process and the data migration therein;

[0048] The scheduling module implements synchronization event scheduling and timer resetting in the cleaning and resynchronization process.

[0049] As mentioned above, when the output state of the multi-mode arbiter reaches the set threshold, the feedback control implements the cleaning recovery strategy. Figure 3 As shown, the cleaning and resynchronization process includes:

[0050] a) when the output decision inconsistency of the protocol executor reaches a set threshold, the multi-mode arbiter notifies the negative feedback controller to start cleaning the protocol executor, and the negative feedback controller sends a cleaning start message to the cleaned protocol executor; wherein the cleaning start message includes protocol type information;

[0051] b) After the cleaned protocol executor receives the cleaning start message, it maintains the route and starts cleaning preparation, which includes restarting the protocol executor process, reinitializing to the initial state or restoring the protocol executor configuration. After the cleaning preparation is completed, it sends a cleaning confirmation message to the negative feedback controller;

[0052] c) The negative feedback controller receives the cleaning confirmation message and simultaneously sends a cleaning confirmation ACK message to the three heterogeneous protocol executors;

[0053] d) After receiving the cleansing confirmation ACK message, the normal protocol executor collects local data (including configuration data and status data) and sends it to the negative feedback controller. The negative feedback controller selects the optimal data and forwards it to the cleaned protocol executor. After receiving the optimal data, the cleaned protocol executor first simulates the events that have occurred based on the received data to bring the cleaned protocol executor to the same state according to the protocol standard process. Then, data migration is carried out to ensure that the state recording time of the three heterogeneous protocol executors is consistent.

[0054] e) After receiving the last data migration message (message end flag = 1) from the normal protocol executor, the negative feedback controller sends a timer synchronization message to the three heterogeneous protocol executors, and the heterogeneous protocol executors synchronously reset the timers and refresh the routing tables;

[0055] f) After completing the timer synchronization, the heterogeneous protocol executor sends a synchronization decision message to the negative feedback controller, i.e., it re-decides the synchronized key information and sends the decision result to the multi-mode arbitrator and the heterogeneous protocol executor;

[0056] g) If the decision result is failure, the multi-mode arbiter re-initiates the cleaning and resynchronization process or modifies the strategy; if the decision result is success, the cleaned protocol executor and the multi-mode arbiter exit the cleaning and resynchronization state.

[0057] In the above cleaning and resynchronization process, the routing is maintained using the graceful restart mechanism, such as Figure 4 As shown, this provides uninterrupted service forwarding during the cleaning and resynchronization process. The graceful restart mechanism sends a graceful restart message to the peer device before the protocol restart (or carries the graceful restart message during the session) to notify the peer device to maintain the route. The local device notifies the routing management module to maintain the routing table and starts a timeout timer. After the protocol restarts, the route is relearned and the routing table is refreshed when the graceful restart timer expires.

[0058] The cleaning and recovery of mimetic network devices is aimed at executable bodies that have been attacked or have vulnerabilities. In order to avoid the incorrect impact of cleaning and recovery on the device itself and avoid incorrect responses from the peer device, speed up the cleaning and resynchronization speed, and reduce the impact on network services, the present invention only uses the routing retention mechanism of the graceful restart mechanism. The recovery of the routing table is achieved through data migration. The resynchronization completion time is guaranteed by the recovery process and processing speed. The peer device is unaware of the entire process and no additional messages are generated.

[0059] Furthermore, a major implementation challenge for data migration is the creation and association of complex data structures such as linked lists and hash tables. By analyzing key protocol data, the data migration described in this invention utilizes event simulation and protocol message simulation to achieve the migration of such complex data structures. Taking the multicast routing protocol PIM as an example, PIM operations primarily involve shared tree expansion. Simulating shared tree operations can generate most of the linked lists and hash table entries in the PIM protocol, while simulating IGMP protocol messages can generate the group information table. Subsequently, simple data migration can achieve information synchronization.

[0060] For event simulation, API calls are used. Taking the multicast routing protocol PIM as an example, the process and entry function are as follows:

[0061] if (receive migration multicast routing data) {

[0062] / *Data parsing* /

[0063] mimicry_info_sync_decode(format,sinfo,sizeof(sinfo),p_data,datalen);

[0064] / *Get shared tree key information based on parsed data* /

[0065] src.s_addr=(p_mroute->src.s_addr);

[0066] group.s_addr=(p_mroute->group.s_addr);

[0067] / *Event simulation API entry* /

[0068] pim_mrt_add_notification_recv(&src,&group,MRIB_MRT_ADD_SUCCESS,msg_flags,0);

[0069] }

[0070] Protocol message simulation simulates protocol messages according to protocol standards and performs normal parsing and processing on protocol messages. Protocol message simulation is suitable for scenarios where the protocol state machine is not too complex, such as the IGMP join group message. The message format is as shown in the figure below. The message receiving and parsing entry function is igmp_dec_msg. After the simulation is completed, IGMP group information is created.

[0071] Based on the above event simulation and protocol message simulation, event simulation cannot achieve consistency in the states between heterogeneous protocol executors, such as routing update time. Data migration between heterogeneous protocol executors within a mimetic network device is much more difficult than hot standby data migration. Since heterogeneous protocol executors may have differences in byte order, bit width, etc., simple memory mirroring and copying cannot achieve data migration between heterogeneous protocol executors. Therefore, the data migration implemented by the present invention using event simulation and protocol message simulation includes:

[0072] (1) When the configuration data is restarted, the configuration data shared by the heterogeneous protocol execution bodies is obtained from the negative feedback controller;

[0073] (2) During data migration, data is converted into the byte order and bit width that are unanimously recognized by the heterogeneous protocol execution bodies for storage and transmission;

[0074] (3) When migrating data, a custom format is used to distinguish protocols, sessions, data types, data fragmentation, and effective data migration. Custom formats such as Figure 5 shown.

[0075] Furthermore, different protocols use different cleaning and resynchronization methods, and the time used is also different, ranging from microseconds to minutes. To meet the requirement of consistent mimetic output, all protocol execution bodies should achieve millisecond-level (≤10ms) timer synchronization of heterogeneous protocol execution bodies through timer reset after resynchronization. This step is achieved by the scheduling module. In-depth analysis of the protocol execution body software timer, the timer synchronization implementation method of the present invention includes:

[0076] Timers are divided into two categories for reset: periodic packet sending timers and timeout processing timers;

[0077] For periodic packet sending timers, the timer reset should be called back first and then restarted;

[0078] For timeout processing timers, the remaining time thread->u.sands should be directly reset without callback.

[0079] The timer is reset through the scheduling module, and the implementation method is relatively simple.

[0080] In summary, the heterogeneous redundant protocol resynchronization implementation method provided by the present invention can cleanse heterogeneous protocol executors that have been attacked by unknown attacks within heterogeneous redundant mimetic architecture network devices, achieving complete recovery of the protocol executor's configuration data, status data, and state machine without affecting the normal forwarding of network services, thereby enhancing network security. The present invention can also be used in hot standby technology to implement an uninterrupted routing hot standby mechanism without affecting network services, modifying protocol standards, or incurring additional network overhead, further improving the reliability of network devices.

[0081] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A method for implementing resynchronization of a heterogeneous redundancy protocol, characterized in that: include: In the dynamic heterogeneous redundant architecture, the negative feedback control message processing module, the cleaning and resynchronization module and the scheduling module work together with the protocol execution module to complete the cleaning and resynchronization; The negative feedback control message processing module controls the process control of the cleaning and resynchronization process; The cleaning and resynchronization module controls the cleaning and resynchronization process and the data migration therein; The scheduling module implements synchronization event scheduling and timer resetting in the cleaning and resynchronization process; The cleaning and resynchronization process includes: a) When the inconsistency of the output decisions of the protocol executor reaches a set threshold, the multi-mode arbitrator notifies the negative feedback controller to start cleaning the protocol executor, and the negative feedback controller sends a cleaning start message to the cleaned protocol executor; b) After receiving the cleaning start message, the cleaned protocol execution body performs route maintenance and starts cleaning preparation. After the cleaning preparation is completed, it sends a cleaning confirmation message to the negative feedback controller; c) The negative feedback controller receives the cleaning confirmation message and simultaneously sends a cleaning confirmation ACK message to the three heterogeneous protocol executors; d) After receiving the cleansing confirmation ACK message, the normal protocol executor collects local data and sends it to the negative feedback controller. The negative feedback controller selects the optimal data and forwards it to the cleaned protocol executor. After receiving the optimal data, the cleaned protocol executor first simulates the events that have occurred based on the received data to bring the cleaned protocol executor to the same state according to the protocol standard process. Then, data migration is performed to ensure that the state recording time of the three heterogeneous protocol executors is consistent. e) After receiving the last data migration message from the normal protocol executor, the negative feedback controller sends a timer synchronization message to the three heterogeneous protocol executors, and the heterogeneous protocol executors synchronously reset the timers and refresh the routing tables; f) After completing the timer synchronization, the heterogeneous protocol executor sends a synchronization decision message to the negative feedback controller, i.e., it re-decides the synchronized key information and sends the decision result to the multi-mode arbitrator and the heterogeneous protocol executor; g) If the decision result is failure, the multi-mode arbiter re-initiates the cleaning and resynchronization process or modifies the strategy; if the decision result is success, the cleaned protocol executor and the multi-mode arbiter exit the cleaning and resynchronization state.

2. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 1, wherein: The cleaning start message includes protocol type information.

3. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 1, wherein: The cleaning preparation includes restarting the protocol execution body process, reinitializing to enter the initial state, or restoring the protocol execution body configuration.

4. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 1, wherein: The local data includes configuration data and status data.

5. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 1, wherein: The routing is maintained using a graceful restart mechanism.

6. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 1, wherein: The data migration is implemented by event simulation and protocol message simulation.

7. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 6, wherein: The data migration implementation method includes: (1) When the configuration data is restarted, the configuration data shared by the heterogeneous protocol execution bodies is obtained from the negative feedback controller; (2) During data migration, data is converted into the byte order and bit width that are unanimously recognized by the heterogeneous protocol execution bodies for storage and transmission; (3) When migrating data, a custom format is used to differentiate protocols, differentiate sessions, identify data types, segment data, and migrate data effectively.

8. The method for implementing heterogeneous redundancy protocol resynchronization according to claim 1, wherein: The timer synchronization implementation method includes: Timers are divided into two categories for reset: periodic packet sending timers and timeout processing timers; For periodic packet sending timers, the timer should be called back before being reset; For timeout processing timers, the remaining time thread->u.sands should be directly reset without callback.

Images