Multi-granularity SCADA redundancy control visual configuration method and system

Abstract

The invention discloses a multi-granularity SCADA redundancy control visual configuration method and system, and the method comprises the steps: sequentially executing the following configuration tasks through a visual configuration interface: configuring network parameters of communication between redundant server nodes, and carrying out the online reachability verification of the configured network parameters; selecting and configuring a target arbitration mechanism, a target redundancy strategy and a target data backup mode from the predefined set; generating a system-level redundancy strategy description file based on all parameters and strategies determined by the configuration task, and issuing the file to the target system; loading and instantiating the redundancy strategy description file, establishing a redundancy communication link, initializing arbitration logic, and triggering a fault switching and data synchronization operation corresponding to a target redundancy strategy and a target data backup mode according to a judgment result of the arbitration logic in an operation period, fine-grained and visual configuration of redundancy level, arbitration mechanism and backup strategy is realized.

Description

Technical Field

[0001] This invention relates to the fields of communication and industrial control automation technology, and in particular to a multi-granularity SCADA redundancy control visualization configuration method and system. Background Technology

[0002] Traditional industrial control monitoring networks mostly feature device-level dual-machine redundancy, lack third-party arbitration functionality, and cannot achieve fine-grained redundancy and backup configurations. This invention can refine the levels of redundancy, arbitration, and backup, and configure redundancy, arbitration, and backup, thus meeting the needs of various industrial control monitoring scenarios and possessing high flexibility and strong deployability.

[0003] Existing solutions address the coarse-grained nature of redundancy configuration in industrial monitoring networks. A similar approach is CN201911156289.5, a multi-center redundancy arbitration method and system based on SCADA (Supervisory Control And Data Acquisition) systems. This invention utilizes a reliable third-party arbitration mechanism, enabling multi-NIC servers to determine whether a redundant NIC is offline (i.e., the active node is offline) and maintain the inactive node, thus preventing changes in redundancy status from impacting other servers' applications through the remaining NICs. However, this solution lacks multi-granularity, visualized configuration for redundancy and backup modes, making it inflexible for industrial scenarios. Summary of the Invention

[0004] The purpose of this invention is to provide a multi-granularity SCADA redundancy control visualization configuration method and system, which solves the technical problems of coarse redundancy granularity, single arbitration mechanism, rigid backup strategy, complex configuration and poor deployability in existing SCADA system redundancy control technology.

[0005] This invention provides a multi-granularity SCADA redundancy control visualization configuration method, applied to a monitoring and data acquisition system comprising at least two redundant server nodes. The method includes: Execute the following configuration tasks sequentially through the visual configuration interface: Configure network parameters for communication between redundant server nodes, and perform online reachability verification on the configured network parameters; Select and configure the target arbitration mechanism from the predefined set of arbitration mechanisms; Select and configure a target redundancy policy from a predefined set of redundancy granularity policies, the target redundancy policy being used to define failover operations; Select and configure the target data backup mode from a predefined set of backup modes based on the service instances in the system; Based on all the parameters and strategies determined by the aforementioned configuration task, a system-level redundancy strategy description file is generated and distributed to the target system; Load and instantiate the redundancy strategy description file, establish redundant communication links, initialize arbitration logic, and trigger fault switching and data synchronization operations corresponding to the target redundancy strategy and target data backup mode during runtime based on the arbitration logic's decision.

[0006] Preferably, performing online reachability verification on the configured network parameters includes: Perform compliance verification on the configured IP addresses; Initiate online detection of the IP address within the target network segment; If an address conflict is detected or there is no valid response, an error will be displayed in the visual configuration interface and the subsequent configuration process will be interrupted until the configuration is reconfigured and verified.

[0007] Preferably, the step of selecting and configuring the target arbitration mechanism from a predefined set of arbitration mechanisms includes: If the target arbitration mechanism is configured as a third-party arbitration mechanism, then the network endpoint identifier of the third-party arbitration device is configured, and online reachability verification is performed on the identifier. After the verification is successful, the subsequent redundancy mode and backup mode configurations are performed. If verification fails, return to reconfigure the network endpoint identifier; If the target arbitration mechanism is configured as a dual-machine arbitration mechanism, then the subsequent redundancy mode and backup mode configurations will be executed directly.

[0008] Preferably, the step of selecting and configuring the target redundancy strategy from a predefined set of redundancy granularity strategies includes: Provides a mapping relationship between fault scenarios and redundancy granularity; In response to the user's selection of a specific fault scenario, automatically associate and configure the corresponding redundancy granularity strategy; The mapping between the fault scenarios and redundancy granularity includes at least the following: In response to the selection of hardware downtime failure scenarios, automatically associate and configure device-level redundancy policies with server nodes as the operating unit; In response to the selection of service process crash or dependency timeout failure scenarios, automatically associate and configure service-level redundancy policies with independent service instances as the unit of operation; In response to the selection of data storage media damage or logical error failure scenarios, the system automatically associates and configures data-level redundancy strategies with logical data groups as the operating unit.

[0009] Preferably, the device-level redundancy strategy, service-level redundancy strategy, and data-level redundancy strategy correspond to different failover operation units. When the device-level redundancy strategy is triggered, failover is performed on the entire server node as a unit; when the service-level redundancy strategy is triggered, failover is performed on the independent service instance as a unit; and when the data-level redundancy strategy is triggered, failover is performed on the logical data group as a unit.

[0010] Preferably, the step of selecting and configuring the target data backup mode from a predefined set of backup modes based on the service instance in the system includes: In response to user assessments of the business criticality and real-time requirements of service instances, the system automatically associates and configures the corresponding backup modes. The mapping between the business continuity requirements and backup modes includes at least: hot backup mode, warm backup mode, and cold backup mode.

[0011] This invention also provides a multi-granularity SCADA redundancy control visualization configuration system, comprising: A configuration management platform, consisting of at least two server devices, is used to execute the following configuration tasks sequentially through a visual configuration interface: Configure network parameters for communication between redundant server nodes, perform online reachability verification on the configured network parameters, select and configure target arbitration mechanism, target redundancy strategy and data backup mode from a predefined set, and generate a system-level redundancy strategy description file based on all configurations; A redundant server cluster, comprising at least two redundant server nodes, is communicatively connected to the configuration management platform. It is used to load and instantiate the redundancy policy description file, make fault judgments according to the arbitration mechanism defined in the file, and trigger service switching and data synchronization operations of corresponding granularity. Third-party arbitration equipment is used to provide independent fault judgment services when selecting a third-party arbitration mode; Several industrial field devices and operating terminals, including industrial PLCs, operator stations, engineer stations, and administrator stations, are communicatively connected to the redundant execution cluster; The server nodes in the redundant server cluster run SCADA monitoring services using a microservice architecture.

[0012] Preferably, the configuration management platform integrates a redundant visual configuration module, which includes: The IP module is used to perform the configuration of the network parameters and online reachability verification; The arbitration module is used to provide the selection and configuration of the set of arbitration mechanisms, and supports two modes: dual-machine arbitration and third-party arbitration. The redundancy configuration module is used to provide the selection and configuration of the set of redundancy granularity strategies, including support for redundancy granularity definitions at the task level, data level, and machine level. The backup module is used to provide the selection and configuration of the set of backup modes, including support for hot backup, warm backup and cold backup modes.

[0013] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the computer program is executed by the processor, it implements the steps of the multi-granularity SCADA redundancy control visualization configuration method as described in the embodiments.

[0014] The present invention also provides a computer-readable storage medium having a computer program stored thereon, characterized in that, when the computer program is executed by a processor, it implements the steps of the multi-granularity SCADA redundancy control visualization configuration method as described in the embodiments.

[0015] Compared with the prior art, the present invention has the following beneficial effects: 1. Implementing multi-granularity redundancy strategies to enhance system configuration flexibility and scenario adaptability: This invention innovatively deconstructs redundancy control into three logical granularities: device-level, service-level, and data-level. This architecture allows users to perform refined and strategic redundancy configurations based on specific fault models and business continuity requirements. This completely overturns the traditional "one-size-fits-all" coarse-grained mode of device-level redundancy, enabling the system to dynamically adapt to diverse industrial monitoring scenarios ranging from hardware failures to service anomalies and data corruption, achieving unprecedented configuration flexibility.

[0016] 2. Enhance arbitration mechanisms and fault isolation to ensure high system reliability: This invention effectively avoids the "split-brain" risk that may occur in complex network environments due to the introduction of a configurable third-party arbitration mechanism, significantly improving the accuracy and authority of fault diagnosis. Simultaneously, the multi-granularity redundancy strategy achieves fine-grained isolation of fault domains, ensuring that failover only affects the smallest necessary unit (a single service instance or data group), rather than the entire server node, thereby greatly enhancing the system's robustness and overall availability.

[0017] 3. Provides visual configuration and online verification, reducing deployment complexity and operational barriers: This invention integrates a full-process visual configuration interface and online network parameter reachability verification function, transforming the traditionally highly complex and redundant system deployment process into an intuitive, guided interactive operation. Users do not need in-depth network engineering or system architecture expertise to efficiently and error-free complete system deployment and policy adjustments, significantly improving the system's deployability and maintainability.

[0018] 4. Optimize resource scheduling and backup strategies to maximize cost-effectiveness: By implementing refined redundancy at the service and data levels, this invention achieves on-demand failover, triggering switching only when a local unit fails, thus avoiding the huge waste of computing and storage resources caused by traditional full-system backup. Combined with differentiated backup strategies (hot backup, warm backup, cold backup) tied to business criticality, system resources can be intelligently allocated according to service priority, optimizing total cost of ownership (TCO) while ensuring the continuity of critical business operations. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating the visualization configuration method for multi-granularity SCADA redundancy control in an embodiment of the present invention. Figure 2 This is a schematic diagram of the architecture of the multi-granularity SCADA redundancy control visualization configuration system in an embodiment of the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] See Figure 1 and Figure 2 As shown in the figure, this invention provides a method and system for visual configuration of multi-granularity SCADA redundancy control.

[0022] like Figure 2 As shown, the system architecture of this embodiment includes: Configuration management platform: Typically deployed on engineer workstations or administrator workstations, providing a web-based visual configuration interface.

[0023] Redundant server cluster: It consists of at least two server devices (such as server A and server B), and each server runs a SCADA monitoring service based on a microservice architecture, including multiple independent service instances such as data acquisition service, alarm service, and historical data service.

[0024] At most one third-party arbitration device: a separate, highly available arbitration server for providing fault resolution when the third-party arbitration mode is configured.

[0025] Industrial field equipment and operating terminals: including several industrial PLCs (Programmable Logic Controllers), operator stations, engineer stations, etc., which are connected to a redundant server cluster through an industrial network.

[0026] The configuration management platform integrates a redundant visual configuration module, which further includes: IP module: Includes redundant IP settings, redundant IP existence detection, etc., and is responsible for configuring and verifying redundant network parameters.

[0027] Arbitration module: Responsible for selecting and configuring the arbitration mechanism. It defaults to dual-machine arbitration but can be configured for third-party arbitration.

[0028] Redundancy configuration module: Responsible for selecting and configuring multi-granularity redundancy strategies, including task-level configuration, data-level configuration and machine-level configuration. The task-level configuration is task-level redundancy for multiple services. In the event of a system failure, only the service is switched. The data-level configuration is data-level redundancy for the data group. In the event of a failure, only the data group is switched. The machine-level configuration is device-level redundancy. In the event of a failure, the entire device is switched.

[0029] Backup module: Responsible for selecting and configuring the backup mode, which can be set to warm backup, cold backup, and hot backup. Based on the module settings, the system establishes a redundant network to monitor and collect data from the industrial control network.

[0030] The following is combined with Figure 1 The flowchart illustrates how this embodiment is applied to the industrial control field. Traditional industrial control monitoring networks often feature device-level dual-machine redundancy. This embodiment can refine the granularity of redundancy levels and provide visual configuration for redundancy / arbitration / backup. It can meet various industrial control monitoring scenarios and features high flexibility, high reliability, and strong deployability. The method for visual configuration of SCADA redundancy control using this system is described in detail.

[0031] Step S1: Through the visual configuration interface, execute the following configuration tasks in sequence: Step S101: Configure network parameters for communication between redundant server nodes and perform online reachability verification on the configured network parameters, including: verifying the compliance of the configured IP address; initiating online detection of the IP address within the target network segment; if an address conflict is detected or there is no valid response, report an error in the visual configuration interface and interrupt the subsequent configuration process until reconfiguration and verification are passed.

[0032] 1. Redundant IP Configuration: Users can configure redundant IPs based on industrial control scenarios. During configuration, the system checks the validity and existence of the IPs to avoid discovering IP errors only after system deployment.

[0033] This can be understood as follows: Users configure a redundant IP address (VIP) for the redundant server cluster through the visual interface of the configuration management platform. Upon receiving user input, the IP module automatically performs the following verifications: 1) Compliance verification: Checks whether the IP address format, subnet mask, etc., conform to preset specifications. 2) Online reachability verification: Within the target network segment, it checks whether the VIP has been occupied by another device using ARP probing or ICMPPing. If a conflict is detected or there is no response, the interface will display an error message, such as "IP address 192.168.1.100 is already in use, please reconfigure!", and interrupt the subsequent process until the user enters a usable IP address. If the check passes, it proceeds to the next step.

[0034] Step S102: Select and configure a target arbitration mechanism from a predefined set of arbitration mechanisms. This includes configuring the network endpoint identifier of the third-party arbitration device if the target arbitration mechanism is configured as a third-party arbitration mechanism, and performing online reachability verification on the identifier. If the verification is successful, the subsequent redundancy mode and backup mode configuration will be performed. If the verification fails, the process will return to reconfigure the network endpoint identifier. If the target arbitration mechanism is configured as a dual-machine arbitration mechanism, the subsequent redundancy mode and backup mode configuration will be performed directly.

[0035] 2. Arbitration Configuration: Users configure the arbitration period and arbitrator. If the arbitrator is a third party, the third party's IP address needs to be set separately, as shown in Table 1 below.

[0036] Table 1. Reference Table for Arbitration Configuration Selection Users enter the configuration interface of the arbitration module. The interface offers two arbitration modes to choose from: "Dual-machine Arbitration" and "Third-party Arbitration".

[0037] Scenario 1: Select "Dual-machine arbitration", and the system will directly proceed to step S103.

[0038] Scenario 2: When selecting "Third-Party Arbitration", the interface will ask the user to enter the network endpoint identifier (such as IP address) of the third-party arbitration device. After entering the information, the system will also perform online reachability verification on this IP. If the verification fails, the interface will display an error message and ask the user to re-enter the information. If the verification is successful, proceed to step S103.

[0039] Step S103: Select and configure a target redundancy strategy from a predefined set of redundancy granularity strategies. The target redundancy strategy is used to define the failover operation, including: providing a mapping relationship between fault scenarios and redundancy granularity; and automatically associating and configuring the corresponding redundancy granularity strategy in response to the user's selection of a specific fault scenario. The mapping between fault scenarios and redundancy granularity includes at least the following: automatically associating and configuring a device-level redundancy policy with server nodes as the operating unit in response to the selection of a hardware downtime fault scenario; automatically associating and configuring a service-level redundancy policy with independent service instances as the operating unit in response to the selection of a service process crash or dependency timeout fault scenario; and automatically associating and configuring a data-level redundancy policy with logical data groups as the operating unit in response to the selection of a data storage medium corruption or logical error fault scenario. Preferably, the device-level redundancy policy, service-level redundancy policy, and data-level redundancy policy correspond to different failover operating units. When the device-level redundancy policy is triggered, failover is performed on the entire server node as the unit; when the service-level redundancy policy is triggered, failover is performed on independent service instances as the unit; and when the data-level redundancy policy is triggered, failover is performed on logical data groups as the unit.

[0040] 3. Redundancy mode configuration: The system can be configured with task-level redundancy, machine-level redundancy, and data-level redundancy. See Table 2 for details on the differences between the modes.

[0041] Table 2 Reference Table for Redundancy Configuration Selection Users enter the configuration interface of the redundancy configuration module. This interface guides users to make selections in the form of a "fault scenario - redundancy strategy" mapping table, greatly reducing the difficulty of configuration. If users are concerned about hardware downtime, they can select the "Hardware Downtime" scenario, and the system will automatically associate and configure a device-level redundancy policy. Under this policy, if server A experiences hardware failure, server B will take over all its service instances and network identities (VIPs).

[0042] If users are more concerned about service stability, they can select the "Service Process Crash" scenario, in which the system will automatically associate and configure a service-level redundancy policy. Under this policy, if the "Alarm Service" instance on server A crashes, the system will only switch the service to a standby "Alarm Service" instance running on server B, while other services will remain unaffected.

[0043] If users are concerned about data security, they can select the "Data Storage Media Damage" scenario. The system will automatically associate and configure a data-level redundancy policy. Under this policy, data is logically divided into multiple data groups (such as "Real-time Data Group" and "Historical Data Group"), and each data group has a primary copy and a backup copy on both server A and server B. If the storage media of the "Real-time Data Group" on server A fails, the system will only switch data access to the backup copy on server B, while the service itself can continue to run.

[0044] Step S104: Select and configure a target data backup mode from a predefined set of backup modes based on the service instances in the system, including: automatically associating and configuring the corresponding backup mode in response to the user's assessment input on the business criticality and real-time requirements of the service instances; wherein the mapping between the business continuity requirements and the backup mode includes at least: hot backup mode, warm backup mode and cold backup mode.

[0045] 4. Backup mode configuration: Due to the different importance and real-time requirements of different services, backup modes can be selected for each service. Backup modes include hot backup, cold backup and warm backup, as detailed in Table 3.

[0046] Table 3 Backup Configuration Selection Reference Table Users enter the backup module configuration interface. The interface lists all service instances in the current SCADA system (such as data acquisition service, alarm service, reporting service, etc.). Users can select the backup mode for each service based on its business criticality and real-time requirements: For critical services (such as data acquisition service), which require real-time backup, select the hot backup mode, where the primary and backup service instances synchronize their status in real time and can switch instantly in case of failure; for moderately important services (such as alarm service), which can tolerate a small amount of data latency, select the warm backup mode, where the backup service instance periodically synchronizes its status from the primary instance (e.g., every 5 seconds); for non-critical services (such as reporting service), select the cold backup mode, where the backup service instance does not run under normal circumstances and is only started manually by the system or through scheduled tasks when the primary instance fails.

[0047] Step S2: Based on all the parameters and policies determined by the aforementioned configuration tasks, generate a system-level redundancy policy description file and distribute it to the target system. After all configuration tasks are completed, the configuration management platform will integrate all information such as the network parameters, arbitration mechanism, redundancy policy and backup mode selected by the user to generate a standardized system-level redundancy policy description file (such as XML or JSON format). Then, through a secure communication channel, the file will be distributed to all nodes in the redundant server cluster.

[0048] Step S3: Load and instantiate the redundancy policy description file, establish redundant communication links, initialize arbitration logic, and trigger failover and data synchronization operations corresponding to the target redundancy policy and target data backup mode during runtime, based on the arbitration logic's decision. After receiving the policy description file, each node in the redundant server cluster: Load and instantiate: Parse the file content, load and instantiate the corresponding configuration locally, such as setting the network card VIP according to the IP configuration, starting the heartbeat service or connecting to a third-party arbitration device according to the arbitration configuration, and configuring service discovery and data synchronization mechanisms according to the redundancy policy; Establish redundant communication links: Establish communication links between server nodes for heartbeat detection, data synchronization, and status synchronization; Initialize arbitration logic: Start the configured arbitration logic (dual-machine or third-party) and begin monitoring the cluster status; Runtime fault handling: During system operation, once the arbitration logic detects a fault (such as server A's heartbeat timeout or a service instance not responding), it immediately makes a decision and triggers failover and data synchronization operations corresponding to the pre-configured redundancy policy and backup mode to ensure the continuous and stable operation of the SCADA system.

[0049] Based on the same inventive concept, this invention also provides a multi-granularity SCADA redundancy control visualization configuration system, comprising: A configuration management platform, consisting of at least two server devices, is used to execute the following configuration tasks sequentially through a visual configuration interface: Configure network parameters for communication between redundant server nodes, perform online reachability verification on the configured network parameters, select and configure target arbitration mechanism, target redundancy strategy and data backup mode from a predefined set, and generate a system-level redundancy strategy description file based on all configurations; A redundant server cluster, comprising at least two redundant server nodes, is communicatively connected to the configuration management platform. It is used to load and instantiate the redundancy policy description file, make fault judgments according to the arbitration mechanism defined in the file, and trigger service switching and data synchronization operations of corresponding granularity. A third-party arbitration device is used to provide independent fault determination services when a third-party arbitration mode is selected; Several industrial field devices and operating terminals, including industrial PLCs, operator stations, engineer stations, and administrator stations, are communicatively connected to the redundant execution cluster; The server nodes in the redundant server cluster run SCADA monitoring services using a microservice architecture.

[0050] Specifically, the configuration management platform integrates a redundant visual configuration module, which includes: The IP module is used to perform the configuration of the network parameters and online reachability verification; The arbitration module is used to provide the selection and configuration of the set of arbitration mechanisms, and supports two modes: dual-machine arbitration and third-party arbitration. The redundancy configuration module is used to provide the selection and configuration of the set of redundancy granularity strategies, including support for redundancy granularity definitions at the task level, data level, and machine level. The backup module is used to provide the selection and configuration of the set of backup modes, including support for hot backup, warm backup and cold backup modes. For other principles, please refer to the dual-core processor task scheduling and processing method for implementing a multi-channel vibration data acquisition system, which will not be repeated here.

[0051] In one embodiment, the present invention also provides an electronic device, including a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the multi-granularity SCADA redundancy control visualization configuration method as described in the embodiment.

[0052] In one embodiment, the present invention also provides a computer-readable storage medium storing one or more programs, which, when executed by an electronic system including multiple applications, cause the electronic system to perform the methods described in the embodiment. Further details will not be elaborated here.

[0053] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for visually configuring multi-granularity SCADA redundancy control, characterized in that, Applied to a monitoring and data acquisition system comprising at least two redundant server nodes, the method includes: Execute the following configuration tasks sequentially through the visual configuration interface: Configure network parameters for communication between redundant server nodes, and perform online reachability verification on the configured network parameters; Select and configure the target arbitration mechanism from the predefined set of arbitration mechanisms; Select and configure a target redundancy policy from a predefined set of redundancy granularity policies, the target redundancy policy being used to define failover operations; Select and configure the target data backup mode from a predefined set of backup modes based on the service instances in the system; Based on all the parameters and strategies determined by the aforementioned configuration task, a system-level redundancy strategy description file is generated and distributed to the target system; Load and instantiate the redundancy strategy description file, establish redundant communication links, initialize arbitration logic, and trigger fault switching and data synchronization operations corresponding to the target redundancy strategy and target data backup mode during runtime based on the arbitration logic's decision.

2. The multi-granularity SCADA redundancy control visualization configuration method as described in claim 1, characterized in that, The online reachability verification of the configured network parameters includes: Perform compliance verification on the configured IP addresses; Initiate online detection of the IP address within the target network segment; If an address conflict is detected or there is no valid response, an error will be displayed in the visual configuration interface and the subsequent configuration process will be interrupted until the configuration is reconfigured and verified.

3. The multi-granularity SCADA redundancy control visualization configuration method as described in claim 1, characterized in that, The step of selecting and configuring a target arbitration mechanism from a predefined set of arbitration mechanisms includes: If the target arbitration mechanism is configured as a third-party arbitration mechanism, then the network endpoint identifier of the third-party arbitration device is configured, and online reachability verification is performed on the identifier. After the verification is successful, the subsequent redundancy mode and backup mode configurations are performed. If verification fails, return to reconfigure the network endpoint identifier; If the target arbitration mechanism is configured as a dual-machine arbitration mechanism, then the subsequent redundancy mode and backup mode configurations will be executed directly.

4. The multi-granularity SCADA redundancy control visualization configuration method as described in claim 1, characterized in that, The step of selecting and configuring a target redundancy strategy from a predefined set of redundancy granularity strategies includes: Provides a mapping relationship between fault scenarios and redundancy granularity; In response to the user's selection of a specific fault scenario, automatically associate and configure the corresponding redundancy granularity strategy; The mapping between the fault scenarios and redundancy granularity includes at least the following: In response to the selection of hardware downtime failure scenarios, automatically associate and configure device-level redundancy policies with server nodes as the operating unit; In response to the selection of service process crash or dependency timeout failure scenarios, automatically associate and configure service-level redundancy policies with independent service instances as the unit of operation; In response to the selection of data storage media damage or logical error failure scenarios, the system automatically associates and configures data-level redundancy strategies with logical data groups as the operating unit.

5. The multi-granularity SCADA redundancy control visualization configuration method as described in claim 4, characterized in that, The device-level redundancy strategy, service-level redundancy strategy, and data-level redundancy strategy each correspond to different failover operation units. When the device-level redundancy strategy is triggered, failover is performed on the entire server node as a unit; when the service-level redundancy strategy is triggered, failover is performed on the independent service instance as a unit; and when the data-level redundancy strategy is triggered, failover is performed on the logical data group as a unit.

6. The multi-granularity SCADA redundancy control visualization configuration method as described in claim 1, characterized in that, The step of selecting and configuring the target data backup mode from a predefined set of backup modes based on the service instances in the system includes: In response to user assessments of the business criticality and real-time requirements of service instances, the system automatically associates and configures the corresponding backup modes. The mapping between the business continuity requirements and backup modes includes at least: hot backup mode, warm backup mode, and cold backup mode.

7. A multi-granularity SCADA redundancy control visualization configuration system, characterized in that, include: A configuration management platform, consisting of at least two server devices, is used to execute the following configuration tasks sequentially through a visual configuration interface: Configure network parameters for communication between redundant server nodes, perform online reachability verification on the configured network parameters, select and configure target arbitration mechanism, target redundancy strategy and data backup mode from a predefined set, and generate a system-level redundancy strategy description file based on all configurations; A redundant server cluster, comprising at least two redundant server nodes, is communicatively connected to the configuration management platform. It is used to load and instantiate the redundancy policy description file, make fault judgments according to the arbitration mechanism defined in the file, and trigger service switching and data synchronization operations of corresponding granularity. Third-party arbitration equipment is used to provide independent fault judgment services when selecting a third-party arbitration mode; Several industrial field devices and operating terminals, including industrial PLCs, operator stations, engineer stations, and administrator stations, are communicatively connected to the redundant execution cluster; The server nodes in the redundant server cluster run SCADA monitoring services using a microservice architecture.

8. The multi-granularity SCADA redundancy control visualization configuration system as described in claim 7, characterized in that, The configuration management platform integrates a redundant visual configuration module, which includes: The IP module is used to perform the configuration of the network parameters and online reachability verification; The arbitration module is used to provide the selection and configuration of the set of arbitration mechanisms, and supports two modes: dual-machine arbitration and third-party arbitration. The redundancy configuration module is used to provide the selection and configuration of the set of redundancy granularity strategies, including support for redundancy granularity definitions at the task level, data level, and machine level. The backup module is used to provide the selection and configuration of the set of backup modes, including support for hot backup, warm backup and cold backup modes.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the computer program is executed by the processor, it implements the steps of the multi-granularity SCADA redundancy control visualization configuration method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the multi-granularity SCADA redundancy control visualization configuration method as described in any one of claims 1-7.

Images