Software redundancy processing method and device, storage medium and electronic equipment

Abstract

The invention discloses a software redundancy processing method and device, a storage medium and electronic equipment, and is applied to the technical field of software redundancy in an industrial control system. In the process of communication between an instance management component and each software instance, when it is monitored that the software instance in a communication state has a fault, the software instance management component sends the fault to an instance management component; the fault software instance of the service queue is isolated through a pre-combined floating IP, the corresponding software instance is switched according to a preset switching rule, the floating IP is obtained by combining rule information in a configuration file and virtual routing equipment, and when it is monitored that the fault software returns to normal, the fault software instance is switched to the corresponding software instance. And adding the software instance which is recovered to be normal to a preset position of the service queue, and starting the next service instance according to the sequence of the service queue.

Description

Technical Field

[0001] This application relates to the technical field of software redundancy in industrial control systems, and more specifically, to a software redundancy processing method, device, storage medium, and electronic device. Background Art

[0002] Most software in industrial control systems (such as software for collecting stateless data) adopts the master-slave hot standby redundancy method. To avoid system unavailability caused by single-point failures, when the host fails due to network failures or software failures, the slave can diagnose the host failure and immediately switch its operating state to the host to maintain data communication with other software.

[0003] Although the above method can avoid system unavailability caused by single-point failures, when the host fails, the industrial control system operates in a single-machine mode, which increases the risk of stable operation of the industrial control system during the single-machine operation.

[0004] Therefore, how to reduce the risk of stable operation of industrial control systems is an urgent problem to be solved in this application. Summary of the Invention

[0005] In view of this, this application discloses a software redundancy processing method, device, storage medium, and electronic device, aiming to achieve multi-instance redundancy of control software, enabling the industrial control system to operate safely and stably and reducing the risk of operation of the industrial control system.

[0006] To achieve the above object, the disclosed technical solutions are as follows:

[0007] The first aspect of this application discloses a software redundancy processing method, which includes:

[0008] During the communication process between the instance management component and each software instance, when a software instance in the communication state is detected to have a failure, isolate the failed software instance of the service queue through a pre-combined floating IP, and switch the corresponding software instance according to a preset switching rule; wherein, the floating IP is obtained by combining rule information in a configuration file and a virtual routing device;

[0009] When it is detected that the failed software returns to normal, add the software instance that has returned to normal to a preset position in the service queue, and start the next service instance according to the service queue order.

[0010] Preferably, the combination process of the floating IP includes:

[0011] When integrating and deploying with each software instance, read the rule information in the configuration file;

[0012] According to the Virtual Router Redundancy Protocol, at least one router is combined to form a virtual routing device;

[0013] The rule information and the virtual routing device are combined into a floating IP.

[0014] Preferably, during the communication between the instance management component and each software instance, when a software instance in a communication state is detected to have a fault, the faulty software instance in the service queue is isolated through the pre-combined floating IP, and the corresponding software instance is switched according to a preset switching rule, including:

[0015] During the communication between the instance management component and each software instance, when a software instance in a communication state is detected to have a fault, the faulty software instance is deleted from the service queue through the pre-combined floating IP to complete the process of isolating the faulty software instance in the service queue;

[0016] The next software instance is switched from the service queue; wherein, the next software instance is the next software instance based on the faulty software instance.

[0017] Preferably, when it is detected that the faulty software returns to normal, adding the software instance that has returned to normal to a preset position in the service queue and starting the next service instance according to the service queue order, including:

[0018] When it is detected that the faulty software returns to normal, adding the software instance that has returned to normal to the end of the service queue and starting the next service instance in the service queue after the faulty software instance according to the service queue order.

[0019] Preferably, it further includes:

[0020] When a new software instance request is received, sending the unique identifier corresponding to the new software instance request to the software instance communicating with the outside;

[0021] Adding the software instance communicating with the outside to the end of the service queue and synchronizing the service queue with other software instances.

[0022] The second aspect of the present application discloses a software redundancy processing device, and the method includes:

[0023] A first monitoring unit, configured to, during the communication between the instance management component and each software instance, when a software instance in a communication state is detected to have a fault, isolate the faulty software instance in the service queue through the pre-combined floating IP, and switch the corresponding software instance according to a preset switching rule; wherein, the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device;

[0024] A second monitoring unit, configured to add a software instance that has returned to normal to a preset position in the service queue when it monitors that a faulty software has returned to normal, and start the next service instance according to the service queue order.

[0025] Preferably, the first monitoring unit in the process of combining floating IPs includes:

[0026] A reading module, configured to read rule information in a configuration file when integrating and deploying with each software instance;

[0027] A composition module, configured to combine at least one router into a virtual routing device according to the Virtual Router Redundancy Protocol;

[0028] A combination module, configured to combine the rule information and the virtual routing device into a floating IP.

[0029] Preferably, the first monitoring unit includes:

[0030] A deletion and isolation module, configured to delete a faulty software instance from the service queue through a pre-combined floating IP when it monitors that a software instance in a communication state has a fault during the process of the instance management component communicating with each software instance, so as to complete the process of isolating the faulty software instance in the service queue;

[0031] A switching module, configured to switch to the next software instance in the service queue; wherein, the next software instance is the next software instance based on the faulty software instance.

[0032] A third aspect of the present application discloses a storage medium, which includes stored instructions, wherein when the instructions run, they control the device where the storage medium is located to execute the software redundancy processing method according to any one of the first aspects.

[0033] A fourth aspect of the present application discloses an electronic device, including a memory, and one or more instructions, wherein one or more instructions are stored in the memory and are configured to be executed by one or more processors to execute the software redundancy processing method according to any one of the first aspects.

[0034] As can be seen from the above technical solutions, the present application discloses a software redundancy processing method, device, storage medium, and electronic device. During the communication process between the instance management component and each software instance, when a software instance in the communication state is detected to have a fault, the faulty software instance in the service queue is isolated through a pre-combined floating IP, and the corresponding software instance is switched according to a preset switching rule. Among them, the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device. When it is detected that the faulty software returns to normal, the software instance that has returned to normal is added to a preset position in the service queue, and the next service instance is started according to the service queue order.

[0035] Through the above solution, multiple external software instances can be managed, a floating IP can be provided for multiple software instances, and services can be provided for multiple software instances through the floating IP. When a software instance fails due to reasons such as network failure or software itself failure, the faulty software is isolated. There are still multiple software instances running in the industrial control system. Instances can be switched according to the switching rule, available software instances can be found as needed, and software instances can be added during the operation of the industrial control system, realizing multi-instance redundancy of the control software, enabling the industrial control system to operate safely and stably, and reducing the operation risk of the industrial control system. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0037] Figure 1 It is a schematic flow chart of a software redundancy processing method disclosed in an embodiment of the present application;

[0038] Figure 2 It is a schematic diagram of another software redundancy processing method disclosed in an embodiment of the present application;

[0039] Figure 3 It is a schematic structural diagram of a software redundancy processing device disclosed in an embodiment of the present application;

[0040] Figure 4 It is a schematic structural diagram of an electronic device disclosed in an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0042] In the present application, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article or device including the said element.

[0043] As can be seen from the background technology, most software in industrial control systems adopts the master-slave hot standby redundancy method. In order to avoid system unavailability caused by single-point failures, when the host fails due to network failures or software itself failures, the slave can diagnose the host failure and immediately switch its running state to the host to maintain data communication with other software. Although the above method can avoid system unavailability caused by single-point failures, when the host fails, the industrial control system runs in a single-machine mode, which will increase the risk of stable operation of the industrial control system during the single-machine operation. Therefore, how to reduce the risk of stable operation of the industrial control system is an urgent problem to be solved in the present application.

[0044] To solve the above problems, the present application discloses a software redundancy processing method, device, storage medium and electronic device, which can manage multiple software instances, provide floating IPs for multiple software instances, and provide services externally through the floating IPs. When a software instance fails due to reasons such as network failures or software itself failures, the faulty software is isolated. There are still multiple software instances running in the industrial control system, and instances can be switched according to the switching rules, and available software instances can be found as needed. Software instances are added during the operation of the industrial control system, realizing multi-instance redundancy of the control software, enabling the industrial control system to operate safely and stably, and reducing the risk of operation of the industrial control system. The specific implementation manners will be specifically described in the following embodiments.

[0045] Refer to Figure 1 As shown in

[0046] S101: During the communication process between the instance management component and each software instance, monitor each software instance in the communication state. When a software instance in the communication state is detected to have a fault, execute S102; when it is detected that the faulty software instance returns to normal, execute S103.

[0047] Faults include but are not limited to network faults, disconnections due to software's own faults, etc.

[0048] S102: Isolate the faulty software instance of the service queue through the pre-combined floating IP, and switch the corresponding software instance according to the preset switching rules; among them, the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device.

[0049] The specific combination process of the floating IP is as shown in A1 - A3.

[0050] A1: When the instance management component is integrated and deployed with each software instance, read the rule information in the configuration file.

[0051] Among them, the rule information includes but is not limited to information such as the IP, port, and routing of the local machine.

[0052] A2: According to the Virtual Router Redundancy Protocol (VRRP), combine at least 1 router to form a virtual routing device.

[0053] In A2, according to VRRP, combine one or more routers to form one virtual routing device, and use the IP address of this virtual routing device as the default gateway to provide communication externally.

[0054] A3: Combine the rule information and the virtual routing device into a floating IP.

[0055] This solution is based on the VRRP protocol and provides a floating IP externally. The VRRP protocol combines one or more routers to form one virtual routing device, and uses the IP address of the virtual routing device (i.e., the floating IP) as the default gateway to provide communication externally.

[0056] This solution is based on the VRRP protocol to implement a software instance management component. The software instance management component manages multiple software instances, can provide services externally through the floating IP. After a software instance fails, the instance can be switched according to the preset switching rules, and software instances can be added as needed during the system operation.

[0057] When the instance management component is integrated into the software instance, the instance management component reads the configuration file, and the instance management components communicate with each other. The software instance of the integration component obtains information such as the local IP, port, and route according to the configuration. The instance management component sends the information to one of the lists for summarization. The instance management component combines this information into a floating IP to provide services externally. The software instance no longer differentiates between the master and slave states. Each software instance is assigned a unique identifier, and each software instance no longer maintains its own data storage. The software instance receives the data and stores the received data in the database. These data include the business data requested by the user, such as the point value information queried in the business, and the status data of the software instance, such as the instance name currently providing services.

[0058] In S102, based on the VRRP protocol, it is deployed integrated with each software instance. The software instance is started. The instance management component first reads the rule information in the configuration file, and the components communicate with each other. The software instances are combined into a floating IP. This floating IP is manually configured, in the same network segment as the instance, and has a different IP from the software instance. The software instance ranked first in the service queue will provide services externally with this floating IP. Other software instances can communicate with this instance through this floating IP. The content of the communication includes, but is not limited to, heartbeat packets, status information, collected data information, etc.

[0059] Each software instance has a unique identifier. For example, Figure 2 Instance A in

[0060] Config.ini

[0061] [count]

[0062] Count = 4 The number of queue services

[0063] [service] Set the queue service name and start order

[0064] Num1 = Instance A

[0065] Num2 = Instance B

[0066] Num3 = Instance C

[0067] Num4 = Instance D

[0068] [timeout]

[0069] Timeout = 100 Set the timeout for the service. If there is no communication within 100 ms, start the next one

[0070] [isignore]

[0071] isignore = 0 Whether to remove the faulty node from the queue after communication failure

[0072] [issupport]

[0073] Issupport = 1 Whether to support adding the service back to the queue

[0074] [style]

[0075] Style = 1 The value ranges from 1 to 3, and different values represent different methods. 1 means sequential startup, 2 means random startup, and 3 means startup according to a certain rule;

[0076] [VirtualIP]

[0077] IP = 192.168.3.230

[0078] [VirtualPort]

[0079] Port = 2023

[0080] [ownIP]

[0081] Ownip = 192.168.3.231

[0082] [ownPort]

[0083] OwnPort = 2024.

[0084] As configured above, parameters such as the order and timeout of software instances in the service queue can be set to maintain the queue of software instances.

[0085] When it is detected that a software instance for communication has failed and cannot provide services, the instance management component will select the next software instance in the queue of the faulty software instance to provide services externally, communicate with other software instances, and isolate the faulty software instance, that is, delete the software instance from the service queue, and synchronize this service queue among all software instances.

[0086] When it is detected that the faulty software has recovered, the instance management component can manually add the instance to the end of the list. After adding it to the end, if the rule is set to sequential startup, according to the current order in the queue, when the service in the front fails, the next service will start according to the queue order and be synchronized to other software instances.

[0087] The instance management component also supports the function of adding software instances during system operation. When the instance management component receives a request to add a new software instance, it sends the unique identifier corresponding to the request to the software instance communicating with the outside, adds the software instance communicating with the outside to the end of the service queue, and synchronizes the service queue with other software instances.

[0088] When a new software instance needs to be added, the instance management component sends the unique identifier of the software instance to the software instance communicating with the outside. After receiving it, the communicating software instance adds the instance to the end of the service queue list through communication software and synchronizes the service queue list with other software instances.

[0089] Specifically, the faulty software instances in the service queue are isolated through pre-combined floating IPs, and the corresponding software instances are switched according to the preset switching rules, as shown in B1 - B2.

[0090] B1: During the communication process with each software instance, when a faulty software instance in the communication state is detected, the faulty software instance is deleted from the service queue through pre-combined floating IPs to complete the process of isolating the faulty software instance in the service queue.

[0091] B2: Switch to the next software instance in the service queue; where the next software instance is the next software instance based on the faulty software instance.

[0092] Among them, switching to the next software instance in the service queue, where the next software instance is the next software instance based on the faulty software instance, is the preset switching rule.

[0093] S103: Add the software instance that has returned to normal to the preset position in the service queue and start the next service instance according to the service queue order.

[0094] In S103, when it is detected that the faulty software has returned to normal, add the software instance that has returned to normal to the end of the service queue and start the next service instance in the service queue after the faulty software instance according to the service queue order.

[0095] For the convenience of the software redundancy processing process, combined with Figure 2 for explanation, Figure 2 shows a schematic diagram of another software redundancy processing method.

[0096] Figure 2In this case, after integrating the instance management component with software instances A, B, and C, the integrated software instances A, B, and C are respectively deployed on three physical machines or virtual machines, and the configuration files are placed on the three machines according to the above configuration;

[0097] After the three software instances are started, a configured IP address such as 192.168.3.230 is provided. When the user requests the functions of the software instance through this IP, the program of instance A is first accessed, and the query and write results are stored in the database cluster;

[0098] After software instance A fails, the instance management component hands over the floating IP to software instance B according to the configuration, and instance A is removed from the list. Data synchronization is performed between the instance management components. When receiving a user request again, the response to the request is provided by software instance B. After software implementation A is repaired, its configuration is placed in the configuration file of software instance B. When the component reads the configuration periodically and finds that instance A has been added, instance A will be added to the end of the queue, and other components will be notified to update the queue.

[0099] This application relates to a software redundancy method in an industrial control system. Software redundancy can improve system reliability and enable the industrial control system to operate safely and stably. The industrial control software redundancy method proposed in this application can be used for software redundancy in industrial control systems, especially nuclear power control systems.

[0100] In this application, in an industrial control system, a software instance management component is proposed based on the VRRP protocol, which provides a floating IP for multiple software instances, isolates faulty software, and finds available software instances according to set rules; this solution can dynamically add software instances during runtime by designing a software management component (i.e., the instance management component).

[0101] This application proposes a software redundancy method for an industrial control system, which realizes multi-instance redundancy of control software. When a software instance is disconnected due to reasons such as network failure or software itself failure, multiple software instances in the industrial control system are still running, enabling the industrial control system to operate safely and stably. This method supports adding new software instances during runtime.

[0102] Advantages of the embodiments of the present application: During the communication between the instance management component and each software instance, when a software instance in the communication state is detected to have a fault, the faulty software instance in the service queue is isolated through a pre-combined floating IP, and the corresponding software instance is switched according to a preset switching rule. Among them, the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device. When it is detected that the faulty software returns to normal, the software instance that has returned to normal is added to a preset position in the service queue, and the next service instance is started according to the service queue order. Through the above solution, multiple external software instances can be managed, floating IPs are provided for multiple software instances, and services are provided for multiple software instances through the floating IPs. When a software instance fails due to network failure or software itself failure, etc., the faulty software is isolated, and multiple software instances still run in the industrial control system. Instances can be switched according to the switching rules, and available software instances can be searched as needed. Software instances are added during the operation of the industrial control system, realizing multi-instance redundancy of the control software, enabling the industrial control system to operate safely and stably, and reducing the risk of operation of the industrial control system.

[0103] Based on the above embodiments Figure 1 A software redundancy processing method disclosed, and the embodiments of the present application also correspondingly disclose a software redundancy processing device, as Figure 3 shown, the software redundancy processing device includes:

[0104] A first monitoring unit 301, configured to, during the communication between the instance management component and each software instance, when a software instance in the communication state is detected to have a fault, isolate the faulty software instance in the service queue through a pre-combined floating IP, and switch the corresponding software instance according to a preset switching rule; among them, the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device;

[0105] A second monitoring unit 302, configured to, when it is detected that the faulty software returns to normal, add the software instance that has returned to normal to a preset position in the service queue, and start the next service instance according to the service queue order.

[0106] Further, the first monitoring unit 301 in the combination process of the floating IP includes:

[0107] A reading module, configured to read the rule information in the configuration file when integrated and deployed with each software instance;

[0108] A composition module, configured to jointly form a virtual routing device by combining at least 1 router according to the virtual routing redundancy protocol;

[0109] A combination module, configured to combine the rule information and the virtual routing device into a floating IP.

[0110] Further, the first monitoring unit 301 includes:

[0111] A deletion and isolation module, configured to, during the communication between the instance management component and each software instance, when it is detected that a software instance in a communication state fails, delete the failed software instance from the service queue through a pre-combined floating IP, so as to complete the process of isolating the failed software instance in the service queue;

[0112] A switching module, configured to switch to the next software instance from the service queue; wherein, the next software instance is the next software instance based on the failed software instance.

[0113] Further, the second monitoring unit 302 is specifically configured to, when it is detected that a failed software recovers to normal, add the software instance that has recovered to normal to the end of the service queue, and start the next service instance of the failed software instance in the service queue according to the service queue order.

[0114] Further, the software redundancy processing device further includes:

[0115] A sending unit, configured to, when receiving a request for adding a new software instance, send the unique identifier corresponding to the request for adding a new software instance to the software instance communicating with the outside;

[0116] A synchronization unit, configured to add the software instance communicating with the outside to the end of the service queue and synchronize the service queue with other software instances.

[0117] The beneficial effects of the embodiments of the present application: During the communication between the instance management component and each software instance, when it is detected that a software instance in a communication state fails, isolate the failed software instance in the service queue through a pre-combined floating IP, and switch the corresponding software instance according to a preset switching rule. Among them, the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device. When it is detected that the failed software recovers to normal, add the software instance that has recovered to normal to a preset position in the service queue, and start the next service instance according to the service queue order. Through the above solution, multiple external software instances can be managed, floating IPs are provided for multiple software instances, services are provided for multiple software instances through the floating IPs. When a software instance fails due to reasons such as network failure or software itself failure, isolate the failed software. There are still multiple software instances running in the industrial control system. Instances can be switched according to the switching rule, and available software instances can be found as needed. When adding software instances during the operation of the industrial control system, multi-instance redundancy of the control software is realized, enabling the industrial control system to operate safely and stably and reducing the operation risk of the industrial control system.

[0118] An embodiment of the present application also provides a storage medium, which includes stored instructions. When the instructions run, they control the device where the storage medium is located to execute the software redundancy processing method as described above.

[0119] An embodiment of the present application also provides an electronic device, and its structural schematic diagram is as Figure 4 shown, specifically including a memory 401 and one or more instructions 402. One or more instructions 402 are stored in the memory 401 and are configured to be executed by one or more processors 403 to execute the above software redundancy processing method.

[0120] For the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0121] It should be noted that the embodiments in this specification are all described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts among the embodiments can be referred to each other. For system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments.

[0122] The steps in the methods of the embodiments of the present application can be adjusted, combined, and deleted according to actual needs.

[0123] Finally, it should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0124] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0125] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A method for processing software redundancy, characterized in that: The method comprises: In the process of the instance management component communicating with each software instance, when a software instance in the communication state is detected to have a fault, the faulty software instance in the service queue is isolated through a pre-assembled floating IP, and the corresponding software instance is switched according to a preset switching rule; wherein the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device; When it is detected that the faulty software has returned to normal, the restored software instance is added to the preset position of the service queue, and the next service instance is started according to the service queue sequence.

2. The method according to claim 1, characterized in that The floating IP combination process includes: When integrated and deployed with each software instance, the rule information in the configuration file is read; According to the virtual routing redundancy protocol, at least one router is combined to form a virtual routing device; The rule information and the virtual routing device are combined into a floating IP.

3. The method according to claim 1, characterized in that In the process of the instance management component communicating with each software instance, when a software instance in a communication state is detected to have a fault, the faulty software instance of the service queue is isolated through a pre-assembled floating IP, and the corresponding software instance is switched according to a preset switching rule, including: During the communication between the instance management component and each software instance, when a software instance in the communication state is detected to be faulty, the faulty software instance is deleted from the service queue through the pre-assembled floating IP to complete the process of isolating the faulty software instance in the service queue; Switch the next software instance from the service queue; wherein the next software instance is the next software instance based on the failed software instance.

4. The method according to claim 1, characterized in that: When the faulty software is detected to be restored to normal, the restored software instance is added to the preset position of the service queue, and the next service instance is started according to the service queue sequence, including: When it is detected that the faulty software has returned to normal, the restored software instance is added to the end of the service queue, and the next service instance of the faulty software instance in the service queue is started according to the service queue sequence.

5. The method according to claim 1, characterized in that Also includes: When receiving a request for adding a new software instance, sending a unique identifier corresponding to the request for adding a new software instance to the software instance communicating with the outside; The software instance for external communication is added to the end of the service queue and the service queue is synchronized with other software instances.

6. A software redundancy processing device, characterized in that: The method comprises: A first monitoring unit is used to isolate the faulty software instance in the service queue through a pre-assembled floating IP when a fault is detected in the software instance in the communication state during the communication between the instance management component and each software instance, and switch the corresponding software instance according to a preset switching rule; wherein the floating IP is obtained by combining the rule information in the configuration file and the virtual routing device; The second monitoring unit is used to add the restored software instance to a preset position of the service queue when it is detected that the faulty software has been restored to normal, and start the next service instance according to the service queue sequence.

7. The device according to claim 6, characterized in that The first monitoring unit of the floating IP combination process includes: A reading module is used to read the rule information in the configuration file when integrating and deploying with each software instance; A composition module, used for combining at least one router into a virtual routing device according to a virtual routing redundancy protocol; The combining module is used to combine the rule information and the virtual routing device into a floating IP.

8. The device according to claim 6, characterized in that The first monitoring unit comprises: The deletion isolation module is used to delete the faulty software instance from the service queue through the pre-assembled floating IP when a fault occurs in the software instance in the communication state detected by the instance management component during the communication between the instance management component and each software instance, so as to complete the process of isolating the faulty software instance in the service queue; The switching module is used to switch the next software instance from the service queue; wherein the next software instance is the next software instance based on the faulty software instance.

9. A storage medium, characterized in that: The storage medium includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the software redundancy processing method according to any one of claims 1 to 5.

10. An electronic device, characterized in that: The system comprises a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by one or more processors to perform the software redundancy processing method according to any one of claims 1 to 5.

Images