Ship control system fault scheduling method, system and device and storage medium

Abstract

The invention discloses a ship control system fault scheduling method, system and device and a storage medium, and relates to the technical field of ship control, and the method comprises the steps: dividing a ship control system into a plurality of sub-control systems, and determining a software configuration table and a hardware configuration table of each sub-control system according to a ship cycle task; constructing a software fault tree minimum cut set and a hardware fault tree minimum cut set according to historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table; calculating the fault occurrence probability of each sub-control system at the current moment based on the software fault tree minimum cut set and the hardware fault tree minimum cut set; and respectively virtualizing software and hardware of the ship control system, and carrying out flexible recombination scheduling when the fault occurrence probability exceeds a preset probability threshold. According to the method, the sub-control systems are divided, potential faults of each sub-system are accurately positioned and analyzed, and flexible recombination scheduling can quickly respond to and process the faults without interrupting system operation.

Description

Technical Field

[0001] The present application relates to the field of ship control technology, and more specifically, to a ship control system fault scheduling method, system, device and storage medium. Background Art

[0002] Ship control system is a key component of normal ship operation and safety assurance, and is mainly used for operation control and management of ship-related equipment. With the continuous advancement of ship technology and the improvement of intelligence level, ship control system plays an increasingly important role in ship navigation, equipment monitoring, fault diagnosis, energy efficiency management, etc.

[0003] At present, ship control systems mostly adopt a tightly coupled design, that is, there is a one-to-one relationship between the control software of a certain function and the control hardware device. The control software is usually tightly bound to specific hardware devices, which can ensure the simplicity and directness of the ship control system to a certain extent.

[0004] However, due to the tightly coupled design of the ship control system, when a hardware device or software fails, the corresponding hardware or software will not be able to continue to complete the original work even if it is in normal condition. The entire system may be affected, resulting in reduced reliability of the ship control system, increased risks of ship operation, and even serious safety accidents. Summary of the invention

[0005] In response to at least one defect or improvement need in the prior art, the present invention provides a ship control system fault scheduling method, system, device and storage medium, which are used to solve the problem that when a hardware device or software fails in the tightly coupled design of the ship control system in the prior art, the corresponding hardware or software cannot continue to complete the original work even if it is in a normal state, resulting in reduced reliability of the ship control system, increased risk of ship operation, and may even lead to safety accidents in severe cases.

[0006] To achieve the above object, according to a first aspect of the present invention, a ship control system fault scheduling method is provided, comprising:

[0007] Divide the ship control system into several sub-control systems, and determine the software configuration table and hardware configuration table of each sub-control system according to the ship's periodic tasks;

[0008] Determine the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table;

[0009] Calculate the probability of failure of each sub-control system at the current moment based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree;

[0010] The software and hardware of the ship control system are virtualized separately, and flexible reorganization scheduling is performed when the probability of failure exceeds the preset probability threshold.

[0011] In a possible implementation, the ship control system is divided into several sub-control systems, and the software configuration table and the hardware configuration table of each sub-control system are determined according to the ship periodic tasks, and further include:

[0012] Dividing the ship control system into a plurality of sub-control systems according to a first granularity according to a control object of the ship control system;

[0013] Determine the software components required for each sub-control system according to the ship's periodic tasks, and generate a software configuration table based on the software granularity;

[0014] Determine the hardware components required for each sub-control system according to the ship's periodic tasks, and generate a hardware configuration table based on the hardware granularity.

[0015] In a possible implementation, determining the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table includes:

[0016] Based on the historical full-cycle data, software configuration table and hardware configuration table, a software resource fault tree and a hardware resource fault tree are established for each sub-control system;

[0017] According to the software resource fault tree and the hardware resource fault tree, the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree are determined respectively.

[0018] In a possible implementation, a software resource fault tree and a hardware resource fault tree are established for each sub-control system based on historical full-cycle data, a software configuration table, and a hardware configuration table, including:

[0019] Statistical analysis is performed on the software configuration table and the hardware configuration table based on historical full-cycle data to establish a full-cycle software failure probability function and a full-cycle hardware failure probability function;

[0020] Based on the full-cycle software failure probability function and the full-cycle hardware failure probability function, the software resource fault tree and the hardware resource fault tree are established respectively.

[0021] In a possible implementation, the probability of failure of each sub-control system at the current moment is calculated based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree, including:

[0022] Obtain the current operating status of each sub-control system of the ship control system;

[0023] The current fault occurrence probability of each sub-control system is calculated according to the current operating state, the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree.

[0024] In a possible implementation, the current fault occurrence probability of each sub-control system is calculated according to the current operating state, the minimum cut set of the software fault tree, and the minimum cut set of the hardware fault tree, including:

[0025] Calculate the current software occurrence probability of each sub-control system based on the current operating state and the minimum cut set of the software fault tree;

[0026] Calculate the current hardware occurrence probability of each sub-control system based on the current operating state and the minimum cut set of the hardware fault tree;

[0027] The current fault occurrence probability of each sub-control system is calculated based on the current software occurrence probability and the current hardware occurrence probability.

[0028] In a possible implementation, the software and hardware of the ship control system are virtualized separately, and flexible reorganization scheduling is performed when the probability of failure exceeds a preset probability threshold, including:

[0029] Virtualizing the software components of each sub-control system based on a preset scoring rule to obtain a software score;

[0030] Virtualizing the hardware components of each sub-control system based on a preset classification strategy to obtain a hardware level;

[0031] If the current fault probability exceeds the preset fault threshold and the fault is sent to the software component, the software component is flexibly reorganized and scheduled based on the software score;

[0032] If the current probability of a fault exceeding a preset fault threshold and a hardware component sends a fault, the hardware component is flexibly reorganized and scheduled based on the hardware level.

[0033] According to a second aspect of the present invention, there is also provided a ship control system fault dispatching system, comprising:

[0034] A software and hardware division module, which is configured to divide the ship control system into a plurality of sub-control systems, and determine the software configuration table and the hardware configuration table of each sub-control system according to the ship's periodic tasks;

[0035] A construction module, which is configured to construct a software fault tree minimum cut set and a hardware fault tree minimum cut set according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table;

[0036] A fault probability calculation module, which is configured to calculate the fault occurrence probability of each sub-control system at the current moment based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree;

[0037] The reorganization scheduling module is configured to virtualize the software and hardware of the ship control system respectively, and perform flexible reorganization scheduling when the probability of failure exceeds a preset probability threshold.

[0038] According to the third aspect of the present invention, there is also provided a ship control system fault scheduling device, which includes at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program, and when the computer program is executed by the processing unit, the processing unit executes the steps of any one of the above-mentioned ship control system fault scheduling methods.

[0039] According to a fourth aspect of the present invention, there is also provided a storage medium storing a computer program executable by an access authentication device, wherein when the computer program runs on the access authentication device, the access authentication device executes any one of the steps of the ship control system fault scheduling method described above.

[0040] In general, the above technical solutions conceived by the present invention can achieve the following beneficial effects compared with the prior art:

[0041] The present invention provides a ship control system fault scheduling method, which divides the ship control system into several sub-control systems, which helps to more accurately locate and analyze the performance and potential faults of each sub-system. By formulating independent software configuration tables and hardware configuration tables for each sub-system, it can ensure that the resource configuration of each sub-system is more reasonable, thereby optimizing the performance and reliability of the overall system. By calculating the probability of failure of each sub-control system at the current moment through the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree, abnormal situations can be discovered and handled in time. When the probability of failure of a sub-control system exceeds a preset probability threshold, the method realizes flexible reorganization scheduling by virtualizing software and hardware resources, which not only improves the flexibility and scalability of the system, but also can quickly respond to and handle faults without interrupting the operation of the system, which helps to minimize the system downtime caused by faults, improve the availability and reliability of the overall system, and take preventive measures before the failure occurs, thereby reducing the maintenance cost caused by the failure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0043] Figure 1A schematic diagram of a flow chart of an embodiment of a ship control system fault dispatching method provided by the present invention;

[0044] Figure 2 The present invention provides Figure 1 A schematic flow chart of an embodiment of step S101;

[0045] Figure 3 A schematic diagram of a flow chart of an embodiment of calculating the current probability of occurrence of a fault in each sub-control system provided by the present invention;

[0046] Figure 4 The present invention provides Figure 1 A schematic flow chart of an embodiment of step S104;

[0047] Figure 5 A schematic diagram of the structure of an embodiment of a ship control system fault dispatching system provided by the present invention;

[0048] Figure 6 A schematic diagram of the structure of a ship control system fault dispatching device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0050] The terms "first", "second", "third", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0051] The present invention provides a ship control system fault scheduling method, system, device and storage medium, which are respectively described below.

[0052] See also Figure 1 , Figure 1 A schematic flow chart of an embodiment of a ship control system fault dispatching method provided by the present invention. In a specific embodiment of the present invention, a ship control system fault dispatching method is disclosed, comprising:

[0053] S101, dividing the ship control system into a plurality of sub-control systems, and determining the software configuration table and hardware configuration table of each sub-control system according to the ship periodic tasks;

[0054] S102, determining a minimum cut set of a software fault tree and a minimum cut set of a hardware fault tree according to historical full-cycle data of the ship control system, a software configuration table, and a hardware configuration table;

[0055] S103, calculating the probability of failure of each sub-control system at the current moment based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree;

[0056] S104, virtualizing the software and hardware of the ship control system respectively, and performing flexible reorganization scheduling when the probability of failure exceeds a preset probability threshold.

[0057] In the above embodiment, the complex ship control system is divided into multiple relatively independent sub-control systems K (K = 1, 2, ..., N), such as navigation control subsystem, power control subsystem, environmental monitoring subsystem, etc., which simplifies the complex ship control system and facilitates subsequent analysis and management. Then, according to the daily operation cycle tasks of the ship, a detailed software configuration table and hardware configuration table are formulated for each sub-control system. The software configuration table includes information such as software version, functional module, and dependency relationship; the hardware configuration table covers key data such as hardware device model, performance parameters, and connection relationship.

[0058] The software fault tree and hardware fault tree are constructed by using the historical full-cycle data of the ship control system (including fault records, maintenance logs, performance test results, etc.) combined with the determined software configuration table and hardware configuration table. A fault tree is a logical diagram used to represent the various factors that may cause faults in the system and their interrelationships. Through fault tree analysis, the minimum cut set of the software fault tree (that is, the minimum event combination that causes software faults) and the minimum cut set of the hardware fault tree are identified.

[0059] Based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree, combined with multi-dimensional information such as historical fault data, equipment aging, environmental factors, etc., probabilistic calculation methods (such as Bayesian networks, Markov chains, etc.) are used to accurately calculate the probability of software failure and hardware failure of each sub-control system at the current moment. Not only the possibility of a single failure is considered, but also the mutual influence and chain reaction between failures, thereby improving the accuracy and comprehensiveness of fault prediction.

[0060] In order to improve the flexibility and maintainability of the system, the software and hardware of the ship control system are virtualized separately. Software virtualization uses containerization or virtualization technology to achieve rapid deployment, migration and backup of software; hardware virtualization simulates real hardware functions through the virtual hardware layer to achieve flexible resource allocation and fault isolation. When the probability of failure of a sub-control system exceeds the preset probability threshold, the flexible reorganization scheduling strategy is immediately triggered. According to the current system operation status, resource availability and task priority, the configuration of the sub-control system is dynamically adjusted, such as switching spare hardware, updating software version, reallocating tasks, etc., to minimize the impact of the failure on the ship operation. Flexible reorganization scheduling can not only achieve rapid recovery after failure, but also optimize resources preventively. Through continuous monitoring and dynamic adjustment, it ensures that the ship control system is always in the best operating state. When the probability of failure of a sub-control system exceeds the preset probability threshold, it can quickly respond and handle the failure without interrupting the system operation, which helps to minimize the system downtime caused by the failure and improve the availability and reliability of the overall system.

[0061] Compared with the prior art, the ship control system fault scheduling method provided in this embodiment divides the ship control system into several sub-control systems, which helps to more accurately locate and analyze the performance and potential faults of each sub-system. By formulating independent software configuration tables and hardware configuration tables for each sub-system, it can ensure that the resource configuration of each sub-system is more reasonable, thereby optimizing the performance and reliability of the overall system. By calculating the probability of failure of each sub-control system at the current moment through the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree, abnormal situations can be discovered and handled in time. When the probability of failure of a sub-control system exceeds the preset probability threshold, the method realizes flexible reorganization scheduling by virtualizing software and hardware resources, which not only improves the flexibility and scalability of the system, but also can quickly respond to and handle faults without interrupting the operation of the system, which helps to minimize the system downtime caused by faults, improve the availability and reliability of the overall system, and take preventive measures before the failure occurs, thereby reducing the maintenance cost caused by the failure.

[0062] See also Figure 2 , Figure 2 The present invention provides Figure 1 In some embodiments of the present invention, the ship control system is divided into a plurality of sub-control systems, and the software configuration table and the hardware configuration table of each sub-control system are determined according to the ship periodic task, and further includes:

[0063] S201, dividing the ship control system into a plurality of sub-control systems according to a first granularity according to a control object of the ship control system;

[0064] S202, determining the software components required for each sub-control system according to the ship cycle tasks, and generating a software configuration table according to the software granularity;

[0065] S203: Determine the hardware components required for each sub-control system according to the ship's periodic tasks, and generate a hardware configuration table according to the hardware granularity.

[0066] In the above embodiment, the control objects of the ship control system may include the ship's propulsion system, navigation system, communication system, environmental monitoring system, safety system, etc., and each control object has its specific functions and performance requirements. According to the characteristics and functional requirements of the control object, the ship control system is divided into several sub-control systems according to the first granularity (i.e., a larger functional unit or system module). For example, the ship control system can be divided into a propulsion control subsystem, a navigation control subsystem, a communication control subsystem, an environmental monitoring control subsystem, a safety control subsystem, etc. The functional boundaries and input and output interfaces of each sub-control system are clarified to ensure that the subsystems can work together and can be operated and maintained relatively independently.

[0067] According to the ship's periodic tasks (such as voyage planning, cargo loading and unloading, maintenance, etc.) and the functional requirements of each sub-control system, determine the software components required for each sub-control system, which may include control algorithms, data processing programs, user interfaces, communication protocol stacks, etc. According to the complexity and reusability of software components, define the software granularity. Software components with smaller granularity (such as function libraries and modules) are easier to reuse and maintain, while software components with larger granularity (such as applications) contain more functions and business logic. According to the defined software granularity, generate a detailed software configuration table for each sub-control system. The software configuration table should include but not be limited to the name, version, dependency, installation path, configuration file and other information of the software component to facilitate software deployment, upgrade and troubleshooting.

[0068] Similarly, according to the ship's periodic mission and the functional requirements of each sub-control system, the hardware components required for each sub-control system are determined, which may include sensors, actuators, controllers, communication equipment, etc. Similar to software granularity, hardware granularity also reflects the complexity and replaceability of hardware components. Hardware components with smaller granularity (such as a single sensor) are easier to replace and upgrade, while hardware components with larger granularity (such as an integrated control system) may contain more functions and interfaces. According to the defined hardware granularity, a detailed hardware configuration table is generated for each sub-control system, which may include but is not limited to the name, model, quantity, installation location, connection relationship, power supply requirements and other information of the hardware components to facilitate the procurement, installation, debugging and maintenance of the hardware.

[0069] In some embodiments of the present invention, determining the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table includes:

[0070] Based on the historical full-cycle data, software configuration table and hardware configuration table, a software resource fault tree and a hardware resource fault tree are established for each sub-control system;

[0071] According to the software resource fault tree and the hardware resource fault tree, the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree are determined respectively.

[0072] In the above embodiment, the operation data of the ship control system in the past period of time (full cycle) is collected, including fault records, maintenance logs, performance test results, etc., and key information such as the occurrence time, fault type, impact range, and repair measures of each fault are recorded in detail. According to the previously generated software configuration table and hardware configuration table, the detailed information of the software components and hardware components of each sub-control system is obtained, including component name, version, quantity, installation location, connection relationship, etc.

[0073] For the software part of each sub-control system, a software resource fault tree is constructed based on historical fault data and software configuration table. The top layer of the fault tree is the software fault of the sub-control system, and the bottom layer is the real-time operating status of each software component that caused the fault. The faults at each layer are connected through logic gates (such as AND gates and OR gates) to represent the logical relationship between the faults.

[0074] Similarly, for the hardware part of each sub-control system, a hardware resource fault tree is constructed based on the historical fault data and hardware configuration table. The top layer of the fault tree is the hardware fault of the sub-control system, and the bottom layer is the real-time operating status of each hardware component that caused the fault. Similarly, the faults at each layer are connected by logic gates to represent the logical relationship between hardware faults.

[0075] In the software resource fault tree, the software fault tree minimum cut set A refers to all possible and minimum combinations of bottom-level software component failures that lead to top-level software failures. All possible minimum cut sets are found through fault tree analysis software (such as FTA tools) or manual analysis. The importance of software component failures in each minimum cut set is evaluated to determine which failures have the greatest impact on the system, thereby guiding subsequent fault prevention and response measures.

[0076] In the hardware resource fault tree, the minimum cut set analysis method is also used to identify all possible and minimum combinations of bottom-level hardware component failures that lead to top-level hardware failures. The importance of hardware component failures in the minimum cut set B of each hardware fault tree is evaluated to determine which hardware failures have the most critical impact on the system, providing decision support for subsequent hardware maintenance and upgrades.

[0077] In some embodiments of the present invention, a software resource fault tree and a hardware resource fault tree are established for each sub-control system based on historical full-cycle data, a software configuration table, and a hardware configuration table, including:

[0078] Statistical analysis is performed on the software configuration table and the hardware configuration table based on historical full-cycle data to establish a full-cycle software failure probability function and a full-cycle hardware failure probability function;

[0079] Based on the full-cycle software failure probability function and the full-cycle hardware failure probability function, the software resource fault tree and the hardware resource fault tree are established respectively.

[0080] In the above embodiment, the historical full-cycle data is cleaned and sorted, duplicate, invalid or abnormal data is removed, the accuracy and consistency of the data are ensured, and the data in the software configuration table and the hardware configuration table are associated with the historical fault data to analyze the fault conditions under a specific configuration. Based on the historical fault data, the software components and hardware components of each sub-control system are statistically analyzed for fault frequency, fault type, fault impact, etc., and the fault trend of the software components and hardware components over time is analyzed to identify the periodic, seasonal or random characteristics of the fault occurrence.

[0081] Based on the historical failure data of software components, statistical modeling methods (such as exponential distribution, Weibull distribution, etc.) are used to establish the failure probability function of software components in the entire cycle, which describes the probability of software components failing at different time points. Similarly, based on the historical failure data of hardware components, the failure probability function of hardware components in the entire cycle is established, and the impact of factors such as wear and aging of hardware components on the failure probability needs to be considered.

[0082] In the fault tree, logic gates (such as AND gates, OR gates, XOR gates, etc.) are used to connect events at each level to represent the logical relationship between them. For example, if multiple underlying events occur simultaneously to cause an intermediate event to occur, use an AND gate to connect these underlying events; if any underlying event causes an intermediate event to occur, use an OR gate to connect them. Continuously iterate and improve the fault tree to ensure that all possible fault paths are covered. At the same time, verify the logical correctness and consistency of the fault tree to ensure that it can accurately reflect the fault behavior of the system.

[0083] In some embodiments of the present invention, the probability of failure of each sub-control system at the current moment is calculated based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree, including:

[0084] Obtain the current operating status of each sub-control system of the ship control system;

[0085] The current fault occurrence probability of each sub-control system is calculated according to the current operating state, the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree.

[0086] In the above embodiments, the current operating data of each sub-control system in the ship control system is collected in real time through sensors, monitoring systems or manual records, and the current operating data should cover key information such as the system's operating status, parameter settings, and performance indicators. The collected operating data is processed and analyzed to evaluate the current operating status of each sub-control system, including whether the system is in a normal working state, whether there are abnormal alarms or performance degradation, etc. Combining historical fault data with the current operating status, identifying potential fault points or known fault modes that may exist helps to more accurately evaluate the probability of fault occurrence at the current moment.

[0087] The minimum cut set represents all possible and minimum combinations of underlying software component failures that lead to software failures. Based on the current running state and the failure probability of the software components in the minimum cut set (these probabilities can be obtained from the full-cycle software failure probability function), the probability of software failure at the current moment is calculated using the basic principles of probability theory (such as the multiplication principle, the addition principle, etc.). If there is a correlation between the software component failures in the minimum cut set (such as the failure of one component may increase the failure probability of another component), more complex calculation methods such as conditional probability or joint probability are required.

[0088] Similarly, based on the current operating state and the probability of hardware component failure in the minimum cut set (these probabilities can be obtained from the full-cycle hardware failure probability function), a similar probability calculation method is used to calculate the probability of hardware failure at the current moment. The failure probability of hardware components may be affected by environmental factors (such as temperature, humidity, vibration, etc.). Therefore, when calculating the probability of hardware failure, it is necessary to consider the potential impact of these environmental factors on the probability of component failure.

[0089] Combining the probability of software failure and the probability of hardware failure to comprehensively evaluate the current probability of failure of each sub-control system requires considering the mutual influence between software failure and hardware failure and their impact on the overall performance of the system.

[0090] See also Figure 3 , Figure 3 A flow chart of an embodiment of calculating the current fault occurrence probability of each sub-control system provided by the present invention. In some embodiments of the present invention, the current fault occurrence probability of each sub-control system is calculated according to the current operating state, the minimum cut set of the software fault tree, and the minimum cut set of the hardware fault tree, including:

[0091] S301, calculating the current software occurrence probability of each sub-control system according to the current operating state and the minimum cut set of the software fault tree;

[0092] S302, calculating the current hardware occurrence probability of each sub-control system according to the current operating state and the minimum cut set of the hardware fault tree;

[0093] S303: Calculate the current fault occurrence probability of each sub-control system according to the current software occurrence probability and the current hardware occurrence probability.

[0094] In the above embodiment, the current operating status data of each sub-control system is collected, including the operating status of software components, error logs, performance parameters, etc., and the collected data is preprocessed to remove noise and fill in missing values ​​to ensure the accuracy and completeness of the data.

[0095] For each software fault tree minimum cut set, based on the current operating state and the known software component failure probabilities (these probabilities can be obtained from historical data or estimated based on experience), the basic principles of probability theory are used to calculate the probability that the cut set will cause a software failure at the current moment. If the minimum cut set contains multiple software component failures, it is necessary to consider the correlation between these failures (for example, the failure of one component may increase the failure probability of another component), and use more complex calculation methods such as conditional probability or joint probability. The software failure probabilities caused by all minimum cut sets are summarized to obtain the current software failure probability of each sub-control system, and the mutual influence between different cut sets and their impact on the overall software performance of the system need to be considered.

[0096] Collect the current hardware operating status data of each sub-control system, including the temperature, voltage, current, vibration and other parameters of the hardware components, and pre-process the collected data to ensure the accuracy and consistency of the data.

[0097] For each minimum cut set of the hardware fault tree, based on the current operating state and the known probability of hardware component failure (these probabilities can be obtained from historical data or estimated based on experience), the basic principles of probability theory are used to calculate the probability that the cut set will cause a hardware failure at the current moment, taking into account the correlation between hardware component failures (such as the failure of one component may accelerate the wear of another component) and the impact of environmental factors (such as temperature, humidity, etc.) on the probability of hardware failure. The hardware failure probabilities caused by all minimum cut sets are summarized to obtain the current probability of hardware failure in each sub-control system.

[0098] The current software failure probability P(At) and the current hardware failure probability P(Bt) of each sub-control system are combined. For the same sub-control system K, its current failure probability P(Kt) = P(At) + P(Bt) - P(At)P(Bt). The current failure probability of each sub-control system is obtained, which reflects the overall risk of system failure under the current operating state.

[0099] The calculated current fault probability is used as the basis for decisions such as fault warning, maintenance planning, and system optimization. According to the actual operating conditions and the changing trend of the fault probability, the fault tree model and its minimum cut set calculation method are continuously adjusted and optimized to improve the accuracy and reliability of fault prediction.

[0100] See also Figure 4 , Figure 4 The present invention provides Figure 1 FIG. 1 is a flow chart of an embodiment of step S104 in FIG. 1 . In some embodiments of the present invention, the software and hardware of the ship control system are virtualized respectively, and flexible reorganization scheduling is performed when the probability of failure exceeds a preset probability threshold, including:

[0101] S401, virtualizing the software components of each sub-control system based on a preset scoring rule to obtain a software score;

[0102] S402, virtualizing the hardware components of each sub-control system based on a preset classification strategy to obtain a hardware level;

[0103] S403: If the current fault occurrence probability exceeds the preset fault threshold and the fault is sent by the software component, the software component is flexibly reorganized and scheduled based on the software score;

[0104] S404: If the current probability of a fault occurring exceeds a preset fault threshold and a hardware component sends a fault, the hardware component is flexibly reorganized and scheduled based on the hardware level.

[0105] In the above embodiment, the preset scoring rules can consider multiple dimensions such as reliability, stability, performance, resource occupancy, maintainability, etc. of the components. The historical operation data of each software component is collected, including fault records, performance monitoring data, resource usage, etc. The collected data is preprocessed to remove noise, fill in missing values, and ensure the accuracy and completeness of the data. According to the preset scoring rules, each software component is virtualized, that is, it is converted into a software entity in a virtual environment, and factors such as dependencies between components and data interaction need to be considered. According to the preset scoring rules and the preprocessed data, the score of each software component is calculated.

[0106] In a preferred embodiment of the present invention, different parameter calculation components are set to 1 point, 3 points, 5 points, and 7 points, and the virtual machine technology is adopted to establish a dedicated software resource calling interface and management module to allocate all required software components R ruan For a sub-control system K, if its parameter calculation component requirement is 11 points, a 7-point parameter calculation component and a 5-point parameter calculation component can be dispatched to replace it.

[0107] The preset classification strategy can be based on multiple factors such as the complexity, importance, redundancy, and replaceability of components. According to the preset classification strategy, each hardware component is virtualized, that is, it is converted into a hardware entity in a virtual environment, and factors such as physical connections and data communications between components need to be considered. According to the classification strategy and the virtualized hardware components, different hardware levels are divided, reflecting the relative importance and priority of the components in the system.

[0108] In a preferred embodiment of the present invention, a hierarchical virtualization strategy is adopted for the virtualization of hardware components, which is divided into three levels: device level, board level, and component level. For example, for hardware computing power, the ship control system has 12 embedded hardware devices at the same time, each device has a dual redundant embedded board, and the embedded chip of each board can simultaneously support 10 computing tasks in isolation. For the hardware requirements of different computing tasks, the hardware virtualization support of the ship control system has different hierarchical strategies.

[0109] Monitor the failure probability of each software component in real time. When the probability exceeds the preset failure threshold, trigger the early warning mechanism and judge the failure type as a software component failure, that is, the failure is related to the running status, code logic, etc. of the software component. According to the software score, perform flexible reorganization and scheduling of the faulty software component, migrate the faulty component to other virtual environments, restart the component, replace it with a spare component, etc. During the flexible reorganization and scheduling process, it is necessary to ensure the continuity and stability of the system.

[0110] Monitor the failure probability of each hardware component in real time. When the probability exceeds the preset failure threshold, trigger the early warning mechanism and judge the fault type as a hardware component failure, that is, the fault is related to the physical state and electrical performance of the hardware component. According to the hardware level, perform flexible reorganization and scheduling of the faulty hardware components, isolate the faulty components from the system, enable spare components, adjust hardware resource allocation, and other measures. During the scheduling process, the security and reliability of the system need to be ensured. While performing flexible reorganization and scheduling, consider the optimal use of hardware resources, for example, through load balancing, resource scheduling, and other means to improve the overall performance and resource utilization of the system.

[0111] In order to better implement the ship control system fault dispatching method in the embodiment of the present invention, based on the ship control system fault dispatching method, correspondingly, please refer to Figure 5 , Figure 5 This is a schematic diagram of the structure of an embodiment of a ship control system fault dispatching system provided by the present invention. The embodiment of the present invention provides a ship control system fault dispatching system 500, including:

[0112] A software and hardware division module 510 is configured to divide the ship control system into a plurality of sub-control systems, and determine the software configuration table and the hardware configuration table of each sub-control system according to the ship periodic tasks;

[0113] A construction module 520, which is configured to construct a software fault tree minimum cut set and a hardware fault tree minimum cut set according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table;

[0114] A fault probability calculation module 530, which is configured to calculate the fault occurrence probability of each sub-control system at the current moment based on the software fault tree minimum cut set and the hardware fault tree minimum cut set;

[0115] The reorganization scheduling module 540 is configured to virtualize the software and hardware of the ship control system respectively, and perform flexible reorganization scheduling when the probability of the failure exceeds a preset probability threshold.

[0116] It should be noted here that the system 500 provided in the above embodiment can implement the technical solutions described in the above method embodiments. The specific implementation principles of the above modules or units can refer to the corresponding contents in the above method embodiments, which will not be repeated here.

[0117] See also Figure 6 , Figure 6 The schematic diagram of the structure of the ship control system fault dispatching device provided by the embodiment of the present invention. Based on the above ship control system fault dispatching method, the present invention also provides a ship control system fault dispatching device, which can be a computing device such as a mobile terminal, a desktop computer, a notebook, a palm computer, and a server. The ship control system fault dispatching device 600 includes a processor 610, a memory 620, and a display 630. Figure 6 Only some components of the synchronous tracking flying welding equipment for real-time measurement of battery height are shown, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.

[0118] In some embodiments, the memory 620 may be an internal storage unit of the ship control system fault dispatching device 600, such as a hard disk or memory of the ship control system fault dispatching device 600. In other embodiments, the memory 620 may also be an external storage device of the ship control system fault dispatching device 600, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the ship control system fault dispatching device 600. Further, the memory 620 may also include both an internal storage unit and an external storage device of the ship control system fault dispatching device 600. The memory 620 is used to store application software and various types of data installed in the ship control system fault dispatching device 600, such as the program code for installing the ship control system fault dispatching device 600. The memory 620 may also be used to temporarily store data that has been output or is to be output. In one embodiment, the memory 620 stores a ship control system fault dispatching program 640, which can be executed by the processor 610, thereby realizing the ship control system fault dispatching method of each embodiment of the present application.

[0119] In some embodiments, the processor 610 may be a central processing unit (CPU), a microprocessor or other data processing chip, used to run program codes or process data stored in the memory 620, such as executing a ship control system fault scheduling method.

[0120] In some embodiments, the display 630 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, etc. The display 630 is used to display information on the ship control system fault dispatching device 600 and to display a visual user interface. The components 610-630 of the ship control system fault dispatching device 600 communicate with each other via a system bus.

[0121] In one embodiment, when the processor 610 executes the ship control system fault scheduling program 640 in the memory 620, the steps in the above ship control system fault scheduling method are implemented.

[0122] This embodiment also provides a computer-readable storage medium, on which a ship control system fault scheduling program is stored. When the ship control system fault scheduling program is executed by a processor, the following steps are implemented:

[0123] Divide the ship control system into several sub-control systems, and determine the software configuration table and hardware configuration table of each sub-control system according to the ship's periodic tasks;

[0124] Determine the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table;

[0125] Calculate the probability of failure of each sub-control system at the current moment based on the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree;

[0126] The software and hardware of the ship control system are virtualized separately, and flexible reorganization scheduling is performed when the probability of failure exceeds the preset probability threshold.

[0127] In summary, the present invention provides a ship control system fault scheduling method, which divides the ship control system into several sub-control systems, which helps to more accurately locate and analyze the performance and potential faults of each sub-system. By formulating independent software configuration tables and hardware configuration tables for each sub-system, it can ensure that the resource configuration of each sub-system is more reasonable, thereby optimizing the performance and reliability of the overall system. By calculating the probability of failure of each sub-control system at the current moment through the minimum cut set of the software fault tree and the minimum cut set of the hardware fault tree, abnormal situations can be discovered and handled in time. When the probability of failure of a sub-control system exceeds the preset probability threshold, the method realizes flexible reorganization scheduling by virtualizing software and hardware resources, which not only improves the flexibility and scalability of the system, but also can quickly respond to and handle faults without interrupting the operation of the system, which helps to minimize the system downtime caused by faults, improve the availability and reliability of the overall system, and take preventive measures before the failure occurs, thereby reducing the maintenance cost caused by the failure.

[0128] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the above method are implemented. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a micro drive, and a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic card or an optical card, a nanosystem (including a molecular memory IC), or any type of medium or device suitable for storing instructions and / or data.

[0129] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0130] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0131] In the several embodiments provided in the present application, it should be understood that the disclosed system can be implemented in other ways. For example, the system embodiments described above are only schematic, such as the division of the units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interfaces, and the indirect coupling or communication connection of the system or unit can be electrical or other forms.

[0132] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0133] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0134] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, disk or optical disk and other media that can store program code.

[0135] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable memory, which can include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0136] The above is only an exemplary embodiment of the present disclosure, and the scope of the present disclosure cannot be limited thereto. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the specification and practicing the disclosure here, those skilled in the art will easily think of the implementation scheme of the present disclosure. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the technical field not recorded in the present disclosure. The description and examples are regarded as exemplary only, and the scope and spirit of the present disclosure are defined by the claims.

[0137] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0138] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A ship control system fault dispatching method, characterized in that: include: Divide the ship control system into several sub-control systems, and determine the software configuration table and hardware configuration table of each sub-control system according to the ship's periodic tasks; Constructing a software fault tree minimum cut set and a hardware fault tree minimum cut set according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table; Calculating the probability of failure of each sub-control system at the current moment based on the software fault tree minimum cut set and the hardware fault tree minimum cut set; The software and hardware of the ship control system are virtualized separately, and flexible reorganization scheduling is performed when the probability of the failure exceeds a preset probability threshold.

2. The ship control system fault dispatching method according to claim 1, characterized in that: The method of dividing the ship control system into a plurality of sub-control systems and determining the software configuration table and the hardware configuration table of each sub-control system according to the ship periodic tasks also includes: Dividing the ship control system into a plurality of sub-control systems according to a first granularity according to a control object of the ship control system; Determine the software components required for each sub-control system according to the ship's periodic tasks, and generate a software configuration table based on the software granularity; Determine the hardware components required for each sub-control system according to the ship's periodic tasks, and generate a hardware configuration table based on the hardware granularity.

3. The ship control system fault dispatching method according to claim 1, characterized in that: The method of constructing a software fault tree minimum cut set and a hardware fault tree minimum cut set according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table includes: Based on the historical full-cycle data, the software configuration table and the hardware configuration table, a software resource fault tree and a hardware resource fault tree are established for each sub-control system; A software fault tree minimum cut set and a hardware fault tree minimum cut set are constructed according to the software resource fault tree and the hardware resource fault tree respectively.

4. The ship control system fault dispatching method according to claim 3, characterized in that: The method of establishing a software resource fault tree and a hardware resource fault tree for each sub-control system based on the historical full-cycle data, the software configuration table and the hardware configuration table includes: Performing statistical analysis on the software configuration table and the hardware configuration table according to the historical full-cycle data to establish a full-cycle software failure probability function and a full-cycle hardware failure probability function; A software resource fault tree and a hardware resource fault tree are established based on the full-cycle software fault probability function and the full-cycle hardware fault probability function, respectively.

5. The ship control system fault dispatching method according to claim 1, characterized in that: The calculating the probability of failure of each sub-control system at the current moment based on the software fault tree minimum cut set and the hardware fault tree minimum cut set includes: Obtain the current operating status of each sub-control system of the ship control system; The current fault occurrence probability of each sub-control system is calculated respectively according to the current running state, the software fault tree minimum cut set and the hardware fault tree minimum cut set.

6. The ship control system fault dispatching method according to claim 5, characterized in that: The calculating the current fault occurrence probability of each sub-control system according to the current running state, the software fault tree minimum cut set and the hardware fault tree minimum cut set respectively includes: Calculating the current software occurrence probability of each sub-control system according to the current operating state and the minimum cut set of the software fault tree; Calculating the current hardware occurrence probability of each sub-control system according to the current operating state and the minimum cut set of the hardware fault tree; The current fault occurrence probability of each sub-control system is calculated according to the current software occurrence probability and the current hardware occurrence probability.

7. The ship control system fault dispatching method according to claim 1, characterized in that: The software and hardware of the ship control system are virtualized separately, and flexible reorganization scheduling is performed when the probability of the failure exceeds a preset probability threshold, including: Virtualizing the software components of each sub-control system based on a preset scoring rule to obtain a software score; Virtualizing the hardware components of each sub-control system based on a preset classification strategy to obtain a hardware level; If the current fault occurrence probability exceeds a preset fault threshold and the fault is sent to a software component, flexibly reorganize and schedule the software component based on the software score; If the current fault occurrence probability exceeds a preset fault threshold and a hardware component sends a fault, the hardware component is flexibly reorganized and scheduled based on the hardware level.

8. A ship control system fault dispatching system, characterized in that: include: A software and hardware division module, which is configured to divide the ship control system into a plurality of sub-control systems, and determine the software configuration table and the hardware configuration table of each sub-control system according to the ship's periodic tasks; A construction module, which is configured to construct a software fault tree minimum cut set and a hardware fault tree minimum cut set according to the historical full-cycle data of the ship control system, the software configuration table and the hardware configuration table; A fault probability calculation module, configured to calculate the fault occurrence probability of each sub-control system at the current moment based on the software fault tree minimum cut set and the hardware fault tree minimum cut set; The reorganization scheduling module is configured to virtualize the software and hardware of the ship control system respectively, and perform flexible reorganization scheduling when the probability of the failure exceeds a preset probability threshold.

9. A ship control system fault dispatching device, characterized in that: It comprises at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program, and when the computer program is executed by the processing unit, the processing unit executes the steps of the ship control system fault scheduling method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: It stores a computer program executable by an access authentication device. When the computer program runs on the access authentication device, the access authentication device executes the steps of the ship control system fault scheduling method according to any one of claims 1 to 7.

Images