A model-based reliability modeling and analysis method for ship electronic information systems

Abstract

The present invention discloses a model-based reliability modeling and analysis method for ship electronic information systems, which relates to the technical field of ship electronic information systems. The method comprises the following steps: S1. constructing an AADL structural model, an AADL behavioral model, and an AADL error model for the ship electronic information system; S2. constructing an AADL reliability model for the ship electronic information system using the AADL structural model, the AADL behavioral model, and the AADL error model as meta-models; S3. mapping the AADL reliability model to a GSPN model; and S4. analyzing system reliability based on the GSPN model. The present invention utilizes a model-based reliability analysis method to address the problems of unclear fault propagation patterns, chaotic system states, and uncertain mission capabilities in current ship electronic information systems with new architectures.

Description

Technical Field

[0001] The present invention relates to the technical field of ship electronic information systems, and more particularly to a reliability modeling and analysis method for ship electronic information systems based on a model. Background Art

[0002] Model-Based Systems Engineering (MBSE) is a concept that corresponds to traditional document-based reliability analysis methods. Its goal is to strengthen communication and coordination between different designers by enhancing the traceability of requirements, while also improving knowledge extraction capabilities, design accuracy, and integrity, thereby facilitating information reuse, strengthening the systems engineering process, and reducing development risks. MBSE modeling methods can be used throughout functional development and design, as well as all subsequent stages. The continuous development of MBSE technology, especially the continuous standardization and unification of system modeling methods, has provided a new approach to solving the reliability analysis and evaluation of complex equipment systems, especially complex electronic information systems.

[0003] Compared to the traditional "dedicated" architecture, the new architecture of shipboard electronic information systems features "resource sharing and reuse, on-demand functional reconfiguration, loose coupling of software and hardware, and integrated business operations." This leads to unclear fault propagation patterns in shipboard electronic information system components, chaotic system states, and uncertain mission capabilities, making reliability analysis difficult.

[0004] Therefore, there is an urgent need for a reliability analysis method for ship electronic information systems based on a new architecture to realize the reliability analysis of ship electronic information systems and provide a quick and effective way for system designers and users to analyze system reliability. Summary of the Invention

[0005] In view of this, the present invention proposes a model-based reliability modeling and analysis method for ship electronic information systems. Its purpose is to use the model-based reliability analysis method to solve the problems of unclear fault propagation laws, chaotic system states, and uncertain mission capabilities in the current new architecture of ship electronic information systems.

[0006] In order to achieve the above object, the present invention adopts the following technical solutions:

[0007] A reliability modeling and analysis method for a ship electronic information system based on a model includes the following steps:

[0008] S1. Construct the AADL structural model, AADL behavioral model and AADL error model of the ship electronic information system;

[0009] S2. Using the AADL structural model, AADL behavioral model and AADL error model of the ship electronic information system as meta-models, a AADL reliability model of the ship electronic information system is constructed.

[0010] S3, mapping the AADL reliability model of the ship electronic information system to the GSPN model;

[0011] S4. Analyze system reliability based on the GSPN model.

[0012] Preferably, in step S1, constructing the AADL structural model of the ship electronic information system specifically includes:

[0013] According to the structural and functional characteristics, the component structure of the ship's electronic information system is divided into three levels: front-end, middle-end and back-end. The front-end includes the ship search and perception system composed of radar components and other perception equipment hardware components; the middle-end includes the ship command system composed of software components and public computing service equipment hardware components; the back-end includes the ship weapon system composed of missile components and other weapon hardware components;

[0014] Map each component in the ship's electronic information system to the corresponding AADL metamodel according to the hierarchical relationship to generate the AADL structural metamodel;

[0015] The AADL structural metamodel is instantiated, and each AADL structural metamodel after the instantiation operation is bound to a software process executed on a corresponding CPU to establish an AADL structural model of a ship electronic information system.

[0016] Preferably, in step S1, constructing the AADL behavior model of the ship electronic information system specifically includes:

[0017] Describe the behavior patterns of various components of the ship's electronic information system and construct an AADL behavior metamodel, which includes a hardware dynamic reconfiguration metamodel and a software dynamic configuration metamodel.

[0018] The state change trigger event of the AADL behavior metamodel is configured on each component of the corresponding ship electronic information system AADL structure model to establish the ship electronic information system AADL behavior model.

[0019] Preferably, in step S1, constructing the AADL error model of the ship electronic information system specifically includes:

[0020] Analyze the fault types of each component of the front-end, middle-end and back-end of the ship's electronic information system layer by layer, and establish the corresponding AADL fault library;

[0021] Analyze the fault status and transition conditions of each component, establish a fault state machine, and set the fault state machine and the fault propagation path between components to the corresponding components;

[0022] According to the hierarchical relationship of each component distribution, the fault propagation relationship between different components is divided into horizontal propagation between components at the same level and vertical propagation between components at different levels;

[0023] The AADL error model of the ship electronic information system is established based on the fault propagation relationship between different components and the fault propagation relationship within each component.

[0024] Preferably, in step S3, mapping the AADL reliability model of the ship electronic information system to the GSPN model specifically includes:

[0025] Using the AADL reliability model of the ship's electronic information system, each component in the ship's electronic information system is added to the mapping library according to its own fault state machine, and the state transition of the fault state machine is added to map each component in the ship's electronic information system into a corresponding sub-GSPN model.

[0026] A GSPN model of the ship electronic information system is established based on the sub-GSPN model.

[0027] Preferably, step S4 includes the following steps:

[0028] S41, reading and parsing the AADL code file in the AADL reliability model of the ship electronic information system, extracting component information in the AADL code file using a regular expression, and classifying the components in the component information according to the front end, the middle end, and the back end;

[0029] S42. Store component information, where the component information includes component category information.

[0030] S43, adding fault propagation relationships between components and binding relationships between software and hardware, running the fault propagation relationships and binding relationships one by one, and generating an XML engineering file of the GSPN model of the ship electronic information system using an XML module;

[0031] S44. Use Pipe2 software to open the XML project file of the GSPN model of the ship electronic information system, and set the corresponding fault failure probability and fault propagation probability of the component according to the fault type that each component in the ship electronic information system can transmit;

[0032] S45. Analyze the GSPN model of the ship electronic information system using the GSPN Analysis function of the Pipe2 software, and derive the probability distribution of the ship electronic information system in various stable states based on the fault failure probability and the fault propagation probability;

[0033] S46. Record the probability distribution of the stable state of the ship's electronic information system, and analyze the reliability of the ship's electronic information system based on the probability distribution of the stable state of the ship's electronic information system.

[0034] It can be seen from the above technical solutions that, compared with the prior art, the present invention discloses a model-based reliability modeling and analysis method for ship electronic information systems, which has the following beneficial effects:

[0035] This paper proposes a metamodel-based construction method for establishing an AADL reliability model for shipboard electronic information systems. This method constructs an AADL reliability model based on structure, behavior, and errors. Regarding the automatic conversion between AADL and GSPN models, a method for automatically mapping AADL code files to GSPN models is proposed. This provides an automated solution for reliability analysis and assessment of shipboard electronic information systems, addressing issues such as unclear fault propagation patterns, chaotic system states, and uncertain mission capabilities in current shipboard electronic information systems with new architectures. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0037] Figure 1 A schematic diagram of the overall process provided by the present invention;

[0038] Figure 2 A schematic diagram of the overall construction process of the AADL reliability model for the ship electronic information system provided by the present invention;

[0039] Figure 3 Schematic diagram of the hardware backup reconstruction metamodel provided by the present invention;

[0040] Figure 4 A schematic diagram of the dynamic configuration of the software provided by the present invention;

[0041] Figure 5 A schematic diagram of the process of constructing the AADL error model for the ship electronic information system provided by the present invention;

[0042] Figure 6 Schematic diagram of the GSPN model corresponding to the components provided by the present invention;

[0043] Figure 7 Schematic diagram of the GSPN model corresponding to the error propagation model provided by the present invention;

[0044] Figure 8 A schematic diagram of the overall construction process of the AADL reliability model for the ship electronic information system provided by the present invention;

[0045] Figure 9 A schematic diagram of a reliability analysis process is provided for the present invention. DETAILED DESCRIPTION

[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0047] like Figure 1-2 As shown, an embodiment of the present invention provides a model-based reliability modeling and analysis method for ship electronic information systems, the goal of which is to use a model-based reliability analysis method to solve the problems of unclear fault propagation laws, chaotic system states, and uncertain mission capabilities in ship electronic information systems with new architectures.

[0048] The method includes:

[0049] S1. Construct the AADL structural model, AADL behavioral model and AADL error model of the ship electronic information system;

[0050] S2. Using the AADL structural model, AADL behavioral model and AADL error model of the ship electronic information system as meta-models, a AADL reliability model of the ship electronic information system is constructed.

[0051] S3, mapping the AADL reliability model of the ship electronic information system to the GSPN model;

[0052] S4. Analyze system reliability based on the GSPN model.

[0053] Step S1 mainly includes three steps:

[0054] (1) Establish the AADL structural model of the ship electronic information system;

[0055] (2) Establishing the AADL behavior model of the ship's electronic information system;

[0056] (3) Establish the AADL error model of the ship's electronic information system.

[0057] The following describes the three steps in step S1 in detail.

[0058] (1) Establishing the AADL structural model of the ship electronic information system

[0059] The establishment of the AADL structural model of the ship electronic information system mainly includes the following steps:

[0060] According to the structural and functional characteristics, the component structure of the ship's electronic information system is divided into three levels: front-end, middle-end and back-end. The front-end includes the ship search and perception system composed of radar components and other perception equipment hardware components; the middle-end includes the ship command system composed of software components and public computing service equipment hardware components; the back-end includes the ship weapon system composed of missile components and other weapon hardware components;

[0061] Map each component in the ship's electronic information system to the corresponding AADL metamodel according to the hierarchical relationship to generate the AADL structural metamodel;

[0062] The AADL structural metamodel is instantiated, and each AADL structural metamodel after the instantiation operation is bound to a software process executed on a corresponding CPU to establish an AADL structural model of a ship electronic information system.

[0063] This step is carried out according to the idea of ​​metamodel modeling. First, the requirements of the ship's electronic information system are analyzed. Based on its functional and structural characteristics, the mapping relationship of the metamodel elements is designed, and then the system reliability analysis model is established based on the metamodel. The ship's electronic information system with a new architecture has a distinct layered structure and can be divided into three components: front-end, mid-end, and back-end. According to the hierarchical analysis method, the component structure of the ship's electronic information system can be decoupled by level. After clearly analyzing the AADL structural model of the components in each level, the structural model of the entire ship's electronic information system can be conveniently improved and established according to the component structure combination.

[0064] The front end primarily includes detection and perception components such as radar and sonar. The mid-end comprises the command and control system (C2) of the ship's electronic information system, a hardware-software coupled system comprised of specialized software components and public computing service hardware components. The back end comprises strike weaponry such as missiles and naval guns, comprised of modular hardware components. Table 1 shows the correspondence between the various modules of the ship's electronic information system and the AADL metamodel.

[0065]

[0066]

[0067] Table 1 Correspondence between system components and AADL metamodel

[0068] For the ship's electronic information system, each component is hierarchically divided into its own sub-level system according to the layered approach shown in Table 1, and each component is mapped to its AADL metamodel according to the corresponding relationship shown in Table 1. On this basis, the above-mentioned structural metamodel is included in the system instance in AADL, and the data flow between components is connected using AADL elements such as Access, Connect, and Flow. Then, the Bing attribute is used to bind the software processes executed on the corresponding CPU to obtain the AADL structural model of the entire ship's electronic information system.

[0069] (2) Establishing the AADL behavior model of the ship's electronic information system

[0070] Establishing the AADL behavior model of the ship's electronic information system mainly includes:

[0071] Describe the behavior patterns of various components of the ship's electronic information system and construct an AADL behavior metamodel, which includes a hardware dynamic reconfiguration metamodel and a software dynamic configuration metamodel.

[0072] The state change trigger event of the AADL behavior metamodel is configured on each component of the corresponding ship electronic information system AADL structure model to establish the ship electronic information system AADL behavior model.

[0073] Specifically, the behavior patterns of the ship's electronic information system in a fault state mainly include the hardware backup and reconstruction behavior and the dynamic configuration behavior of each software of the command subsystem on the computing node during the hardware reconstruction process. Step (1) constructs the AADL structural model. On this basis, this step needs to describe the behavior pattern of the ship's electronic information system, construct the system behavior metamodel according to the metamodel construction method, and configure the metamodel state change trigger event to the component of the corresponding system structure model. In this way, the AADL behavior model of the system can be established.

[0074] The behavioral meta-model of hardware backup reconstruction is as follows Figure 3As shown in the figure, M represents the computing resource device of the entire command subsystem, M_1 and M_2 represent two computing nodes in the computing resource device, and A represents the functional software configured on the resource device. The two computing nodes back up each other. In the initial state, M_1 provides computing resources for software A. If M_1 fails, functional software A will be bound to M_2. At this time, M_2 provides computing resources for functional software A, ensuring that the entire system remains normal.

[0075] like Figure 4 As shown in the figure, as computing hardware is dynamically configured, functional software is also dynamically configured on different hardware. This is reflected at the system level as the dynamic binding of functional software to different computing modules. M_1 is a resource device, M_2 is a resource device with the same function, A_1 and A_2 are the functional software running on resource devices M_1 and M_2, respectively, and I is the task supported by that function. If resource device M_1 fails, since functional software A_2 has the lowest priority, to ensure the effective completion of task I, functional software A_2 is shut down and functional software A_1 is assigned to resource device M_2.

[0076] In establishing the AADL behavioral model, the Mode Transition element in the AADL model is used to represent behaviors that cause hardware backup and reconstruction and software dynamic configuration in the ship's electronic information system. By configuring the state change trigger event to the components of the system structure model established in step (1), the AADL behavioral model of the system can be established. This fundamentally solves the problem of state chaos in the new architecture ship's electronic information system, which makes it difficult to analyze faults.

[0077] (3) Establishing the AADL error model of the ship's electronic information system

[0078] Establishing the AADL error model of the ship's electronic information system mainly includes:

[0079] Analyze the fault types of each component of the front-end, middle-end and back-end of the ship's electronic information system layer by layer, and establish the corresponding AADL fault library;

[0080] Analyze the fault status and transition conditions of each component, establish a fault state machine, and set the fault state machine and the fault propagation path between components to the corresponding components;

[0081] According to the hierarchical relationship of each component distribution, the fault propagation relationship between different components is divided into horizontal propagation between components at the same level and vertical propagation between components at different levels;

[0082] The AADL error model of the ship electronic information system is established based on the fault propagation relationship between different components and the fault propagation relationship within each component.

[0083] Specifically, after establishing the AADL structural model of the system in step (1), it is necessary to set the fault category and fault state machine of each component to each component corresponding to the AADL structural model, and set the fault transmission path between components to the corresponding different components of the structural model.

[0084] The AADL model can automatically propagate faults in ship electronic information systems according to data lines and set fault propagation paths, eliminating the tedious configuration of each fault propagation path individually. This solves the problem of chaotic fault propagation paths in ship electronic information systems and difficulty in reliability analysis.

[0085] According to the subsystems of each ship electronic information system shown in Table 1, the fault types of each component in the system search system, command system, and strike weapon (the meaning of each component is clearly indicated in the structural model) are analyzed layer by layer to establish the corresponding AADL fault library. After analyzing the fault status and conversion conditions of each component, a fault state machine (error_behavior) model is established in the AADL model. After analyzing the propagation relationship of faults between each component, the propagation relationship of the fault is divided into two types according to the hierarchical relationship of component distribution: horizontal propagation of faults of components at the same level and vertical propagation of faults of components at different levels. According to the corresponding AADL code template, the fault propagation path is set between each component in the ship electronic information system, thereby completing the establishment of the AADL error model of the ship electronic information system. The specific process is as follows. Figure 5 shown.

[0086] In another implementation, the fault modeling of the ship's electronic information system can be performed using the Error Model Attachment (EMA) based on the constructed dynamic architecture model according to the mission failure mode and fault transmission mechanism. Fault modeling mainly models the behavior, propagation, and type of the fault. The detailed analysis process is as follows:

[0087] Declare the fault behavior library and define fault types, events, and states;

[0088] Fault modeling is performed. First, a component fault behavior state machine is used to model and analyze the fault propagation sources and paths within the component. The fault state transitions and the events that trigger them are then described. Outgoing ports are designated for the faults, along with properties such as the probability distribution of event occurrence. A composite fault behavior state machine is then used to map the fault logic of the composite component's subcomponents.

[0089] Fault transmission is described by matching out-in names. For example, when a resource device is in a stress-disappearing fault state, it transmits a "dissappeard_temporary_failed_outflow" error. The service unit and functional unit introduce the error through "dissappeard_temporary_failed_outflow". The state changes of the resource layer and functional layer after the error is transmitted / introduced are described under their respective "transition" keywords.

[0090] The AADL error model annex language is used to describe the vertical transmission mode of system faults as follows:

[0091] error model A / / error model type

[0092] features / / Error model features [...]

[0094] (+)dissappeard_temporary_failed_outflow:out error propagation; / / outgoing error

[0095] (+)hw_permanent_failed_outflow:out error propagation; / / outgoing error

[0096] (+)reboot:out error propagation; / / outgoing error

[0097] (+)sw_permanent_failed_outflow:in out error propagation; / / introduce error

[0098] end A; / / end of error model type

[0099] error model implementation A.general / / Error model implementation

[0100] transitions / / State transfer instructions [...]

[0102] (+)errorfree-[in sw_permanent_failed_outflow]->dissappeard_temporary_failed; / / State transfer after the error is introduced

[0103] (+)dissappeard_temporary_failed-[dissappeard_temporary_failed_outflow]->dissappeard_temporary_failed; / / State transfer after outflow error

[0104] (+)permanent_failed-[out hw_permanent_failed_outflow]->permanent_failed; / / State transfer after outgoing error

[0105] (+)errorfree-[out reboot]->errorfree; / / State transfer after outgoing error

[0106] properties / / Random event property description

[0107] (+)occurrence=>poisson dtfo applies to dissappeard_temporary_failed_outflow;

[0108] (+)occurrence=>fixed 1applies to hw_permanent_failed_outflow;

[0109] (+)occurrence=>poisson r applies to reboot;

[0110] (+)occurrence=>fixed 1applies to sw_permanent_failed_outflow;

[0111] end A.general; / / End of error model implementation.

[0112] The AADL fault model annex language is used to describe the fault lateral transmission mode between two components as follows:

[0113] error model A / / error model type

[0114] features / / Error model features [...]

[0116] (+)errorpropa:out error propagation; / / outgoing error

[0117] end A; / / end of error model type

[0118] error model implementation A.general / / Error model implementation

[0119] transitions / / State transfer instructions [...]

[0121] (+)failed-[out errorpropa]->failed; / / State transfer after outgoing error

[0122] properties / / Random event property description

[0123] (+)occurrence=>fixed ep applies to errorpropa;

[0124] end A.general; / / End of error model implementation

[0125] error model B / / error model type

[0126] features / / Error model features [...]

[0128] (+)errorpropa:in error propagation; / / introduce error

[0129] end B; / / end of error model type

[0130] error model implementation B.general / / Error model implementation

[0131] transitions / / State transfer instructions [...]

[0133] (+)failed-[in errorpropa]->failed; / / State transfer after introducing error

[0134] properties / / Random event property description

[0135] (+)occurrence=>fixed 1applies to errorpropa;

[0136] end B.general; / / End of error model implementation

[0137] In the above code, components A and B describe the outgoing and incoming errors by matching the out-in names.

[0138] S2. Using the AADL structural model, AADL behavioral model and AADL error model of the ship electronic information system established in step S1 as meta-models, a AADL reliability model of the ship electronic information system is constructed.

[0139] S3. Mapping the AADL reliability model of the ship electronic information system to the GSPN model

[0140] Steps (1) to (3) sequentially establish the structure, behavior, and error models of AADL, thereby establishing the AADL reliability model of the ship's electronic information system. However, the AADL reliability model cannot be quantitatively analyzed and evaluated, and it needs to be converted into a GSPN model that can be analyzed and calculated. Generalized stochastic Petri nets (GSPN) are graphical information flow models that contain two types of nodes: state and event. If black dots that identify system state information are added to the network model with states and events as nodes, and the state changes are driven by events according to certain "ignition" rules, the dynamic evolution of the system state can be described. Due to the superiority of the GSPN network in analyzing "asynchronous concurrent" events, it is suitable for modeling the reliability analysis model of the new architecture ship's electronic information system.

[0141] Mapping the AADL reliability model of the ship electronic information system to the GSPN model mainly includes using the AADL reliability model of the ship electronic information system to add the normal state and each fault state of each component in the ship electronic information system into the mapping library according to its own fault state machine, and adding the state transition of the fault state machine to map each component in the ship electronic information system into the corresponding sub-GSPN model;

[0142] A GSPN model of the ship electronic information system is established based on the sub-GSPN model.

[0143] The GSPN model corresponding to the component is as follows Figure 6As shown in the figure, the GSPN model indicates that: at the initial moment, the component is in a normal state. After a period of operation, the component fails (i.e., Fail migration is implemented), causing the component to be in an error state (i.e., the identifier of the Errorfree position will move to the Failed position). Due to the fault-tolerant design of the ship's new system architecture combat system components, the component will not lose its function immediately, but will start fault detection (i.e., Detection migration can be implemented), and the detection will end after a period of time (i.e., the Failed identifier moves to the Detection_end position). The fault may be permanent or temporary. If it is a permanent fault (i.e., Direct_damage migration is implemented), the component will fail permanently (i.e., the identifier at the Detection_end position moves to the Permanent_failed position); if it is a temporary fault (i.e., Performance_degradation migration is implemented), the component will be in a temporary fault state (i.e., the identifier at the Detection_end position moves to the Temporary_failed position). Temporary faults are further divided into removable and non-removable. If the fault is removable (i.e., Removable migration is implemented, the black dot at the Temporary_failed position moves to the Removable If the fault is irremovable (the Unremovable migration is implemented, causing the Temporary_failed position to move to the Unremovable_temporary_failed position), and a sufficient period of time has passed (the Time_damage migration is implemented), the fault becomes a permanent failure (the black dot in the Unremovable_temporary_failed position moves to the Permanent_failed position). For permanent failures, the component can be restarted (the Restart migration is implemented), and the component will return to normal after restart (the Permanent_failed position moves to the Errorfree position).

[0144] When only considering the individual components or relatively independent components in the electronic information system of the new ship architecture, the basic elements of the reliability model, namely error state, error event, and error state migration, are converted into basic elements such as position, arc, and migration in the GSPN model, as shown in Table 2.

[0145]

[0146]

[0147] Table 2 Mapping of AADL model elements to GSPN model elements of ship electronic information system

[0148] When the AADL error model of the ship electronic information system is converted into the GSPN model, such as Figure 7 As shown, by combining outpropagation and inpropagation, a vertical fault transmission model and a horizontal fault transmission model can be established. In the figure, component A is the fault transmitter, and component B is the fault receiver. The two are connected through a data interface, and fault transmission is also transmitted through the data port. The fault transmitted by component A and the fault introduced by component B are the same. As shown in the figure, a bidirectional arc from the fault output point Outprop to the fault input point InProp and a prohibited arc from the fault input source In_src to t* are added;

[0149] The bidirectional arc from the fault output point Outprop to the fault input point InProp indicates that when a fault occurs in the fault propagation source Out_src of component A, an identifier is stored in the fault output point Outprop. If there is also an identifier in the fault input point InProp at this time, component B will receive the fault of component A and a fault state transition will occur. If there are other fault-introducing components, they can also receive the fault, and the identifier in the fault output point OutProp should not disappear. Therefore, there must be a bidirectional arc between the fault output point Outprop and the fault input point InProp.

[0150] The prohibited arc from the fault incoming source In_src to t* indicates that when the fault propagation source out_src only has one fault transmission to the fault state Out_dst, there is an identifier in the fault outgoing point Outprop. If there is already an identifier in the fault incoming source In_src of component B at this time, the fault introducing component B is ready to introduce the fault. In order to prevent the identifier in this fault outgoing point OutProp from being absorbed by t*, a prohibited arc from the fault incoming source In_src to t* is added.

[0151] In the embodiment, components A and B may be components of the same level or components of different levels.

[0152] Figure 8This is the GSPN model corresponding to mode transitions described in the AADL language. The left side shows the GSPN portion corresponding to "Guard_event" in the AADL language. Since "Guard_event" triggers corresponding events through event ports and is closely related to the state of the component, it corresponds to a position in the GSPN model and represents a state of the component. The "modes" on the right are used to describe the different operating modes of the system, that is, the different states of the system, and are also represented by positions. The "Guard_transition" in the middle describes the logical conditions that prompt the system mode transition, so it first requires a corresponding transition. At the same time, logical conditions are represented in the GSPN by connecting related positions and transitions with directed arcs.

[0153] Based on the above-mentioned metamodel element mapping between the AADL model and the GSPN model, the AADL reliability model of the ship electronic information system constructed in steps S1-S2 (including the structural model, behavioral model, and error model) is analyzed layer by layer to analyze each component of the AADL reliability model. Figure 6 The GSPN model corresponding to the corresponding components is mapped, and the structural heterogeneous behavior of the ship electronic information system in the behavioral model of the AADL reliability model is used to describe the system state change caused by the system error. Figure 8 The GSPN model description of the mode transition is shown, and the fault propagation paths of the fault model of the AADL reliability model are expressed as Figure 7 The GSPN model of fault propagation is shown in the figure. By converting the AADL reliability model to the GSPN model layer by layer, we can finally obtain the GSPN model of the ship electronic information system, which lays the foundation for the reliability analysis of the ship electronic information system in the next step.

[0154] S4. Analyze system reliability based on the GSPN model.

[0155] After steps S1 and S2, the AADL reliability model of the system can be established, and according to step S3, the corresponding GSPN model of the ship's electronic information system can be designed. Pipe2 (Platform Independent Petri Net Editor) is a platform-independent, open-source GSPN model analysis tool. Manually editing the GSPN model designed according to step (4) in Pipe2 software will make the reliability analysis process very tedious and complicated, resulting in low efficiency.

[0156] In order to solve this problem, when analyzing the system reliability, the AADL code file of the established ship electronic information system is first read, and the component information and component categories in the text are parsed. After the file is read, the component information table is stored, and the component propagation and binding relationship is added. After the component error propagation path is clarified, the component and propagation relationship is executed one by one. Create and generate the GSPN engineering XML file, use Pipe2 software to open the XML file, and after setting the failure probability and the fault propagation probability, use the GSPN Analysis function to analyze the reliability of the corresponding GSPN model. After recording and analyzing the system reliability, different failure probabilities and fault propagation probabilities can be set to further analyze the system reliability. The process is as follows Figure 9 shown.

[0157] The specific process is as follows:

[0158] S41. Read and parse the AADL code file in the AADL reliability model of the ship's electronic information system, extract component information from the AADL code file using regular expressions, and classify it into front-end (sonar and radar components), mid-end (target recognition, information processing, situation display and other software components and computing nodes and other hardware components) and back-end (aviation missiles and artillery components);

[0159] The component classification corresponds to each component in the established AADL structural model, so that the GSPN model of each component can be converted in a targeted manner. At the same time, the hierarchy of each component is distinguished, which facilitates the setting of the error propagation relationship between components (5.3). If the file pointer does not reach the end, it means that the AADL code file parsing has not been completed. Continue to parse the component information sentence by sentence and classify it; if the file pointer reaches the end, it means that the AADL code file parsing is complete, and go to step S42 to store the component information;

[0160] S42. Store component information, where the component information includes component category information.

[0161] According to the component information and categories extracted from the system AADL code file in step S41, an XML file automatic generation module can be written by analyzing the tree structure of the XML engineering file of the GSPN model, which includes an XML file automatic generation function for generating a single-component GSPN model. This module can automatically generate single-component XML codes one by one according to the stored component information and category table, thereby realizing automatic conversion of single-component AADL code files to GSPN models.

[0162] S43, adding fault propagation relationships between components and binding relationships between software and hardware, running the fault propagation relationships and binding relationships one by one, and generating an XML engineering file of the GSPN model of the ship electronic information system using an XML module;

[0163] S44. Use Pipe2 software to open the XML project file of the GSPN model of the ship electronic information system, and set the corresponding fault failure probability and fault propagation probability of the component according to the fault type that each component in the ship electronic information system can transmit;

[0164] According to the XML engineering file of the GSPN reliability model of the ship electronic information system automatically generated in S2 and S3, it is opened with Pipe2 software, and the failure probability and fault propagation probability of each component are set in the corresponding GSPN model; the corresponding failure probability and fault propagation probability of each component in the ship electronic information system are set according to the fault type that can be transmitted by each component, so that the probability distribution of each steady state of the system can be calculated in S46;

[0165] S45. Analyze the GSPN model of the ship electronic information system using the GSPN Analysis function of the Pipe2 software, and derive the probability distribution of the ship electronic information system in various stable states based on the fault failure probability and the fault propagation probability;

[0166] According to the GSPN reliability model of the ship electronic information system set by S44 in Pipe2 software, the GSPN Analysis function provided by Pipe2 software can be used to analyze the current GSPN model and obtain the probability distribution of the system in various stable states;

[0167] S46. Record the probability distribution of the stable state of the ship's electronic information system, and analyze the reliability of the ship's electronic information system based on the probability distribution of the stable state of the ship's electronic information system.

[0168] Calculate and statistically analyze the probability distribution of the system in each stable state obtained in S45. Determine the system state (failure or normal operation) based on the state of each component in the system. This allows us to calculate the probability of the system operating normally and obtain the system's steady-state availability index.

[0169] Determine whether to change the failure probability and continue analyzing the reliability of the system. If a stop instruction is received, go to the end; otherwise, go to step S44 to continue setting the system GSPN model.

[0170] The idea of ​​the present invention is that it is difficult to directly use AADL modeling based on the characteristics of clear hierarchy and loose coupling of software and hardware of the ship electronic information system with a new architecture. The present invention proposes a metamodel modeling method as shown in the figure, which builds the structure, behavior, and error metamodel of the system based on the needs. According to the structural metamodel, the reliability structure model of the system is constructed according to the composition structure of the system, and then the behavior metamodel and the error metamodel are configured in each component of the structural model. By adding specific fault propagation relationships, the behavior model and error model of the system can be constructed, and finally the establishment of the system AADL reliability model is completed. It solves the problems of unclear fault propagation laws and chaotic system states in document-based reliability analysis. After completing the conversion of the system AADL reliability model to the GSPN model, the reliability of the new architecture ship electronic information system can be analyzed based on the GSPN model.

[0171] First, the ship's electronic information system's structure and hardware and software components were analyzed to derive the system's structural metamodel. The system's operating principles were analyzed to derive the system's behavioral metamodel. The system's failure modes and fault propagation patterns were analyzed to derive the system's error metamodel. Based on the metamodels, the system's structural, behavioral, and error models were constructed, ultimately completing the establishment of the system's AADL reliability model.

[0172] This model-based ship electronic information system reliability modeling and analysis method proposes a metamodeling technique to establish the system's AADL structure, behavior, and error models, constructing an AADL reliability model. A mapping relationship between the AADL model and the GSPN model is proposed. Using the Pipe2 software, the GSPN model mapped to the AADL model can be automatically established and reliability analysis can be performed. This achieves the goal of reliability analysis for new-architecture ship electronic information systems, providing a quick and intuitive way for system designers and users to analyze system reliability.

[0173] At present, this method has been verified on typical ship electronic information systems and can solve the problem of reliability analysis of electronic information systems of ships with new architectures.

[0174] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Reference can be made to the common and similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method description.

[0175] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A model-based reliability modeling and analysis method for ship electronic information systems, characterized in that: The method comprises: S1. Construct the AADL structural model, AADL behavioral model, and AADL error model of the ship electronic information system; specifically, According to the structural and functional characteristics, the component structure of the ship's electronic information system is divided into three levels: front-end, middle-end and back-end. The front-end includes the ship search and perception system composed of radar components and other perception equipment hardware components; the middle-end includes the ship command system composed of software components and public computing service equipment hardware components; the back-end includes the ship weapon system composed of missile components and other weapon hardware components; Map each component in the ship's electronic information system to the corresponding AADL metamodel according to the hierarchical relationship to generate the AADL structural metamodel; Instantiating the AADL structural metamodel, binding each instantiated AADL structural metamodel to a software process executed on a corresponding CPU, and establishing an AADL structural model of a ship electronic information system; Describe the behavior patterns of various components of the ship's electronic information system and construct an AADL behavior metamodel, which includes a hardware dynamic reconfiguration metamodel and a software dynamic configuration metamodel. The state change trigger event of the AADL behavior metamodel is configured on each component of the corresponding ship electronic information system AADL structure model to establish the ship electronic information system AADL behavior model; Analyze the fault types of each component of the front-end, middle-end and back-end of the ship's electronic information system layer by layer, and establish the corresponding AADL fault library; Analyze the fault status and transition conditions of each component, establish a fault state machine, and set the fault state machine and the fault propagation path between components to the corresponding components; According to the hierarchical relationship of each component distribution, the fault propagation relationship between different components is divided into horizontal propagation between components at the same level and vertical propagation between components at different levels; The AADL error model of the ship electronic information system is established based on the fault propagation relationship between different components and the fault propagation relationship within each component. S2. Using the AADL structural model, AADL behavioral model and AADL error model of the ship electronic information system as meta-models, a AADL reliability model of the ship electronic information system is constructed. S3, mapping the AADL reliability model of the ship electronic information system to the GSPN model; S4. Analyze system reliability based on the GSPN model.

2. The model-based ship electronic information system reliability modeling and analysis method according to claim 1 is characterized in that: In S3, the AADL reliability model of the ship electronic information system is mapped to the GSPN model, specifically including: Using the AADL reliability model of the ship's electronic information system, each component in the ship's electronic information system is added to the mapping library according to its own fault state machine, and the state transition of the fault state machine is added to map each component in the ship's electronic information system into a corresponding sub-GSPN model. A GSPN model of the ship electronic information system is established based on the sub-GSPN model.

3. The model-based ship electronic information system reliability modeling and analysis method according to claim 1 is characterized in that: The S4 specifically includes: S41, reading and parsing the AADL code file in the AADL reliability model of the ship electronic information system, extracting component information in the AADL code file using a regular expression, and classifying the components in the component information according to the front end, the middle end, and the back end; S42. Store component information, where the component information includes component category information. S43, adding fault propagation relationships between components and binding relationships between software and hardware, running the fault propagation relationships and binding relationships one by one, and generating an XML engineering file of the GSPN model of the ship electronic information system using an XML module; S44. Use Pipe2 software to open the XML project file of the GSPN model of the ship electronic information system, and set the corresponding fault failure probability and fault propagation probability of the component according to the fault type that each component in the ship electronic information system can transmit; S45. Analyze the GSPN model of the ship electronic information system using the GSPN Analysis function of the Pipe2 software, and derive the probability distribution of the ship electronic information system in various stable states based on the fault failure probability and the fault propagation probability; S46. Record the probability distribution of the stable state of the ship's electronic information system, and analyze the reliability of the ship's electronic information system based on the probability distribution of the stable state of the ship's electronic information system.

Images