CN115577990A

CN115577990A - Method for establishing equipment system task reliability model

Info

Publication number: CN115577990A
Application number: CN202211570104.7A
Authority: CN
Inventors: 于海跃; 吴昕阳
Original assignee: National University of Defense Technology
Current assignee: National University of Defense Technology
Priority date: 2022-12-08
Filing date: 2022-12-08
Publication date: 2023-01-06
Anticipated expiration: 2042-12-08
Also published as: CN115577990B

Abstract

The invention provides a method for establishing a device system task reliability model, which comprises the steps of establishing a description model for describing system task reliability, establishing an analysis model for analyzing the system task reliability, and providing a basis for obtaining a numerical solution of the device system task reliability. According to the method and the device, the EOOPN model is selected as a model for analyzing the reliability of the equipment system task, the conversion rule from the DoDAF sub-model to the EOOPN model is determined, and the purpose of establishing the reliability model of the equipment system task based on the EOOPN model is achieved.

Description

Method for establishing equipment system task reliability model

Technical Field

The invention relates to the field of computer application of equipment systems, in particular to a method for establishing a task reliability model of an equipment system in EOOPN.

Background

With regard to the research on the reliability model of the equipment system task, the following problems mainly exist:

(1) Task reliability description method of equipment system

The premise for analyzing a large complex system is to make clear the composition, structure and functional behavior. For the task reliability analysis of the equipment architecture, the system must first be described clearly from the task reliability point of view. The description not only accords with engineering practice, but also is convenient for task reliability modeling and evaluation, not only can have a definite description on the composition unit and the functional structure of the system, but also can consider the expression of factors such as the time period of the battle tasks born by the system, the logic relation among the tasks, the resource constraint of the task use, the dynamic randomness of the resource state and the like. Currently, the developed architecture analysis framework is mainly used for the aspects of demand analysis, equipment demonstration, development supervision and the like of the system, and a description model is less established from the perspective of task reliability. Therefore, the existing architecture analysis framework needs to be expanded to solve the problem of describing the reliability of the task of the equipment system.

(2) Selection and generation of system task reliability analysis model

The task reliability description model of the equipment system is only a static description model and cannot finish quantitative analysis on the task reliability of the system. The original Petri net is difficult to be used for analyzing complex systems such as an equipment system due to the fact that the model elements are limited in types and simple in structure. In addition, when an EOOPN (extended object-oriented Petri network) model is established for a large-scale complex system such as an equipment system, the workload is large and the error probability is high only through a manual means. Therefore, translation methods need to be found to simplify the EOOPN modeling difficulty.

Disclosure of Invention

The invention aims to provide a method for establishing an equipment system task reliability model, which comprises the steps of establishing a description model for describing the reliability of a system task, establishing an analysis model for analyzing the reliability of the system task, and providing a basis for obtaining a numerical solution of the reliability of the equipment system task later, so as to solve the technical problems of constructing the system description model from the perspective of task reliability, simplifying EOOPN modeling difficulty and helping modeling personnel to analyze and calculate the model.

In order to achieve the above object, the present invention provides a method for establishing a reliability model of a task of an equipment architecture, comprising the steps of:

A. establishing a description model for describing the reliability of the system task;

expanding a system interface model on the basis of a 2.0 frame of a structure frame of the United states department of defense; constructing three DoDAF submodels, namely a combat mission multi-stage model for describing a stage mission, a stage mission reliability logic model for describing reliability logic and a system state transition description model for describing component state transition in a DoDAF view product;

B. establishing an analysis model for system task reliability analysis;

on the basis of an EOOPN model, a DoDAF submodel is used as input, a transition structure of an XML label of the EOOPN submodel is defined, and the DoDAF submodel is converted into three corresponding EOOPN submodels; applying the EOOPN model to the multi-stage task system for modeling; the three EOOPN submodels are a multi-stage model of the combat mission, a component state model of a stage mission reliability model and a system state transition description model.

Preferably, the three DoDAF submodels are specifically:

the multi-stage model of the combat mission divides the working time of the weapon platform at each stage, time slices at the same stage have the same length after division, and the time sequence logic description is carried out on the mission and the execution sequence at each stage;

the method comprises the steps of a stage task reliability logic model, an expansion system interface description model, and logical signs of AND, OR and vote, and is used for describing reliability logic between weapon platforms or between components;

the system state transition describes a model, describes the system state, events causing state changes, and relationships between states.

Preferably, the transition structure of the XML tag defining the EOOPN submodel is specifically:

the label structure of transition comprises AND gate transition, NOT gate transition, OR gate transition, voting gate transition, probability gate transition and time delay gate transition.

Preferably, the applying the EOOPN model to the multi-stage task system for modeling specifically includes:

the modeling of a multi-phase task system is divided into three layers:

the first layer carries out modeling in a total task layer and describes the type, duration and execution sequence of tasks in each stage contained in the total task;

the second layer carries out modeling at a stage task level and describes working modes and stage success states among weapon platforms which undertake the stage task, wherein the working modes comprise series connection, parallel connection, voting or mixed connection;

the third layer models at the component level, describing the state change information of the component.

Preferably, the step of converting the modeling of the total task hierarchy is as follows:

step 101: reading in an XML document of a multi-stage model of the battle tasks in the DoDAF submodel, and generating an XML writing stream;

step 102: judging whether XML label elements exist or not; if yes, go to step 103; if not, the step 112 is executed;

step 103: reading XML tag elements, and turning to step 104 when the XML tag elements are 'DoDAF self-defined models'; when the XML tag element is not the 'DoDAF custom model', the step 105 is carried out;

step 104; writing in an outermost layer network with ID of EOOPN, adding a successful library place, a failed library place and a broadcast library place for the EOOPN network, and adding arcs connecting the successful library place and the failed library place; returning to the step 103;

step 105: judging whether the XML tag element is 'P _ Connection', if so, turning to a step 106, otherwise, turning to a step 107;

step 106: adding arcs between a successful AND gate at the last stage, a failed AND gate and a starting library place at the next stage for the EOOPN network; returning to the step 103;

step 107: judging whether the XML tag element is 'Phase _ Session', if so, turning to step 108, otherwise, turning to step 112;

step 108: writing a stage i subnet with the ID being Phase _ ID for an EOOPN network, and writing a stage starting library place, a stage finishing library place, a stage success library place and a stage failure library place for the stage i subnet; entering the next layer of a 'Phase _ Session' label, namely an 'EOOPN' network writing-in Phase ending time delay transition, phase success and Phase failure AND gate transition, and writing-in connection ending library locations and ending transition, successful library locations and successful transition, and arcs between failed library locations and failure transition;

step 109: judging whether the current stage i is stage 1, if so, turning to step 110, otherwise, turning to step 103;

step 110: writing the time delay transition of the next task start for the phase i subnet; writing an arc connecting a starting library place and the time delay transition into the phase i subnet;

step 111: switching to a conversion algorithm of a stage task layer;

step 112: and (6) ending.

Preferably, the step of converting the phase task level modeling includes:

step 201: judging whether XML label elements exist or not; if yes, go to step 202; if not, go to step 213;

step 202: reading the XML tag element, and when the XML tag element is 'Logic _ Mark', turning to step 203; when the XML tag element is not "Logic _ Mark", proceed to step 204;

step 203: writing Logic transition with the ID being Logic _ ID and the Type being opposite to Logic _ Type into the subnet at the stage i; returning to the step 201;

step 204: judging whether the XML tag element is 'System _ Unit', if so, turning to step 205, otherwise, turning to step 207;

step 205: writing the i-subnet into the equipment library and the equipment working library, writing the i-subnet into a probability gate transition, and adding an arc connecting the equipment library, the equipment working library and the probability gate transition; writing a component state network with the ID of System _ ID for the stage i subnet;

step 206: entering the next layer of the label of the System _ Unit, and switching to a conversion algorithm of a component level;

step 207: judging whether the XML tag element is 'L _ Connection', if so, turning to a step 208, otherwise, turning to a step 214;

step 208: judging whether the two ends are logic symbols or not; if yes, go to step 209, otherwise go to step 210;

step 209: writing in the intermediate library for the stage i subnet, writing in the arcs of both FrontNode and RearNode and the intermediate library; then, writing in an intermediate library for the stage i subnet, and writing in an arc connecting the FrontNode and the RearNode with the intermediate library; returning to the step 201;

step 210: judging whether one end is empty, if yes, turning to a step 211, otherwise, turning to a step 212;

step 211: writing an arc into the subnet at the stage i, wherein the front item is FrontNode, and the back item is a broadcast base; writing an arc into the subnet at the stage i, wherein the front item is-FrontNode, and the back item is a broadcast base; writing an arc for transmitting a work starting message for the stage i subnet, wherein the front item is-FrontNode, and the back item is a unit work starting library; returning to the step 201;

step 212: writing an arc for the stage i subnet, wherein the former item is an equipment working library and the latter item is a RearNode; writing an arc for the stage i subnet, wherein the former item is an equipment working library and the latter item is-RearNode; returning to the step 201;

step 213: writing an AND gate transition representing the stage start for the stage i subnet, and writing arcs connecting the stage start library location, the broadcast library location, the stage start AND gate transition and each equipment library location; writing in an AND gate transition representing the beginning of a phase, and writing in an arc connecting a phase starting library location, a phase finishing library location, a phase success AND gate transition and a phase success library location; writing in an AND gate transition representing a stage failure, and writing in arcs of a connection stage starting library place, a broadcast library place, a stage failure AND gate transition and a stage failure library place;

step 214: and (6) jumping out.

Preferably, the conversion step of modeling at the component task level is:

step 301: judging whether XML label elements exist or not; if yes, go to step 302; if not, go to step 310;

step 302: reading XML tag elements, and when the XML tag elements are 'State', turning to step 303; when the XML tag element is not "State", proceeding to step 304;

step 303: writing a library place with the ID of State _ ID into a component State network with the ID of System _ ID; returning to the step 301;

step 304: judging whether the XML tag element is 'Transition', if so, turning to step 305; if not, go to step 310;

step 305: judging whether Condition is empty, if yes, turning to step 306; if not, go to step 307;

step 306: writing a time delay Transition with the ID of Transition _ ID into a component state network with the ID of System _ ID; go to step 308;

step 307: writing an AND gate Transition with the ID of Transition _ ID into a component state network with the ID of System _ ID; writing an arc into a component state network with the ID of System _ ID, wherein the former item is Condition and the latter item is Transition _ ID;

step 308: writing an arc into a component State network with the ID of System _ ID, wherein the former item is State _ ID, and the latter item is Transition _ ID;

step 309: writing an arc into a component state network with the ID of System _ ID, wherein the former item is Transition _ ID, and the latter item is End _ ID; writing an arc into a component state network with the ID of System _ ID, wherein the former item is Transition _ ID, and the latter item is a broadcast library; turning to step 301;

step 310: and (6) ending. Jump out of the hierarchy and go back to the conversion algorithm of the stage task hierarchy.

The invention has the following beneficial effects:

the invention provides a method for establishing a reliability model of a system task of equipment. Specifically, the method comprises the following steps:

1. standardized description model for providing equipment system task reliability

Aiming at the task reliability modeling requirement of an equipment system, 8 view products are extracted from 52 products of a DoDAF2.0 framework, a system interface model is expanded, and a multi-stage model of the battle task is additionally defined. Through the extraction and the extension, the improved system task reliability description model can clearly describe the system, the tasks and the relationship among the systems and the tasks and has the capability of describing the task reliability of the system.

2. Selecting EOOPN model as model for analyzing reliability of equipment system task

In order to reduce the modeling difficulty of the EOOPN model, the inventor extracts three view products from ten view products for describing the task reliability of the equipment architecture to form a DoDAF submodel suitable for modeling the task reliability of the multi-stage task system, and defines an XML transition structure.

3. Defining the conversion rule from the DoDAF submodel to the EOOPN model

The method provides an algorithm for converting the XML label of the DoDAF submodel into the XML document of the EOOPN submodel, and provides a feasible method for converting the DoDAF submodel into the EOOPN model.

In addition to the objects, features and advantages described above, other objects, features and advantages of the present invention are also provided. The present invention will be described in further detail below with reference to the drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments of the invention and, together with the description, serve to explain the invention and not to limit the invention. In the drawings:

FIG. 1 is a schematic diagram of a multi-stage EOOPN model of a mission in accordance with the present invention;

FIG. 2 is a schematic diagram of the phase task reliability EOOPN model of the present invention;

FIG. 3 is a schematic diagram of a state model of the components of the early warning radar (UEWR) of the present invention;

FIG. 4 illustrates the relationship between the DoDAF submodel and the EOOPN submodel;

FIG. 5 is a diagram of a conversion algorithm for the overall task hierarchy;

FIG. 6 is a schematic diagram of a phase task hierarchy conversion algorithm;

FIG. 7 is a diagram of a conversion algorithm at the component task level.

Detailed Description

Embodiments of the invention will be described in detail below with reference to the drawings, but the invention can be implemented in many different ways, which are defined and covered by the claims.

A method for establishing an equipment architecture task reliability model, comprising the steps of:

based on the 2.0 framework of the American national defense department architecture framework (DoDAF), 8 view products are expanded to serve as a DoDAF-ROD model, a system interface model in the DoDAF-ROD model is expanded, and the composition of a system is directly described;

respectively constructing a DoDAF description model (view product) for describing basic information of the system and a DoDAF submodel for describing task reliability information of the system;

the DoDAF description model comprises a high-level combat concept graph, a system interface model, a system measure matrix, a combat activity decomposition tree model, a combat activity to system tracking matrix, a combat activity model and a combat event tracking description model;

the three DoDAF submodels are respectively a combat mission multi-stage model for describing the stage missions, a stage mission reliability logic model for describing reliability logics and a system state transition description model for describing component state transition in a DoDAF view product.

Wherein, the specific definition of the DoDAF description model is as follows:

1. high-level operational concept (OV-1)

Firstly, a high-level combat conceptual diagram is established to describe task scene information. The whole intercontinental ballistic missile defense combat task of the equipment system is described, and a high-level and abstract description of what task the system structure completes and how to complete the task is provided, so that a modeling worker can integrally grasp and know the task.

2. System interface model (SV-1)

And secondly, establishing a system interface model and describing an architecture. As a first model for describing the system information, the system composition and structure are described, including each weapon platform under the system and each component under the weapon platform. The system interface model (SV-1) describes the corresponding system deployed on the warfare node, as defined in DoDAF 2.0. The concept of a combat node varies according to the description level of the combat demand and does not necessarily correspond to a real physical facility. It may be represented as a fighter role, an organization or type of organization, etc. A weapons platform is referred to herein as a combat node.

3. System measure matrix (Sv-7)

And thirdly, establishing a system measure matrix to describe the performance parameters. As a second model for describing system information, the matrix will describe the existing performance parameters of the component, including failure distribution, condition level, and serviceability. As well as performance parameters that are expected or required over a particular period of time in the future.

4. Operational decomposition tree model (OV-5 a)

Fourthly, establishing a combat activity decomposition tree model and describing task level information. As the only model for describing task information, the method analyzes and describes the intercontinental ballistic missile defense combat task of the equipment system. The combat mission is refined to the combat activity undertaken by each combat node (weapons platform) in a stepwise decomposition and refinement manner according to the design objectives and capabilities of the architecture.

5. Battle activity to system tracking matrix (SV-5 b)

And fifthly, establishing a battle activity to system tracking matrix, and describing the mapping relation between the battle activity and the weapon platform. As the first model to describe the many-to-many mapping between the campaign and the weapons platforms. Its main function is to establish the link between the bottom layer of the battle activity decomposition tree and the weapon platform in the system interface model.

6. Operational active model (OV-5 b)

And sixthly, establishing a combat activity model and describing a weapon platform activity interaction process. As a second model describing a many-to-many mapping between the campaign and the weapons platforms. For the entire combat task, the model describes the order of execution of all the combat activities. For each weapons platform (i.e., a combat node), the model describes the order of execution of the various combat activities undertaken by a weapons platform.

7. Operational event tracking description model (OV-6 c)

And seventhly, establishing a combat event tracking description model for describing the activity interaction time of the weapon platform. As a third model describing a many-to-many mapping between the campaign and the weapons platforms. It will provide the time of information exchange between the weapons platforms, the sequence of events, and the duration of the individual combat activities under each weapons platform for a particular scenario. The main difference between the model and the OV-5b is that the model can express the specific time slice length, and lays a foundation for the following multi-stage task division.

The specific definition of the DoDAF submodel is:

the DoDAF submodel will mainly perform a standardized description on the task reliability information of the equipment architecture.

8. Multi-stage model of combat mission

And eighth, establishing a multi-stage model of the battle task, and describing task stage information. The model mainly describes each phase task and the execution sequence among them. The multi-stage model of the combat mission is a custom model. The whole combat mission is divided according to the lengths of different time slices in the combat event tracking description model, and the time slices in the same stage have the same length after division, which means that weapon platforms in the stage have the same working time. Through the division, the complex interactive relation among the battle activities can be changed into simple sequential logic of each stage.

9. Stage task reliability logic model

And ninthly, establishing a stage task reliability logic model, and describing stage task logic information and component reliability logic information. The model is an extension of a system interface description model, and introduces logic symbols for describing reliability logic between weapon platforms or between components. For logical relationships between weapons platforms that are tasked at the same stage or between components below the same weapons platform, the logical relationships include: and, or, and vote.

10. System state transition description model (SV-10 b)

And tenth, establishing a system state transition description model to describe the state transition condition of the component. The model is used to describe the state of the system, the events that cause the state changes, and the relationships between the states, the state of a component will determine the state of the system it makes up. The states of the components are divided into an idle state, a working state and a fault state. The component state transition description is placed herein in the equipment architecture task reliability information description section because the state of a component directly affects the functionality of the weapons platform through logical relationships with other components.

In the DoDAF submodel, the XML tag structure is specifically as follows:

(1) Multi-stage model tag structure for combat mission

The XML label of the multi-stage model of the battle mission comprises two sub-elements, namely a stage mission element and a connecting line element.

The Phase task element comprises element attributes such as Phase _ ID, phase _ Name, T1 and T2, and the connecting line element comprises element attributes such as Connection _ ID, connection _ Type, frontMision and RearMision.

The XML specification description is as follows:

< DoDAF custom model >

< P _ Connection _ ID = "Connection _ Type =" Phase _ Connection "FrontMision =" number 1 "RearMision =" number 2"/> (P _ Connection _ ID =" number "Connection _ Type =" Phase _ Connection _ Type = "number 1"/>)

< Phase _ transmission Phase _ ID = "number 1" Phase _ Name = "Name 1" T1= "start time 1" T2 = "end time 1" >)

…

</ Phase_Mission >

< Phase _ transmission Phase _ ID = "number 2" Phase _ Name = "Name 2" T1= "start time 2" T2 = "end time 2" >)

…

</ Phase_Mission >

…

</DoDAF custom model >

(2) Label structure of stage task reliability logic model

The label of the stage task reliability logic model comprises three sub-elements, namely a logic symbol element, a connecting line element and a weapon platform element, besides the attribute of the label.

The logical symbol elements comprise element attributes such as Logic _ ID, logic _ Name and Logic _ Type, the connecting line elements comprise element attributes such as Connection _ ID, connection _ Type, frontNode and RearNode, and the weapon platform elements comprise element attributes such as System _ ID and System _ Name.

The XML specification description is as follows:

< Phase _ transmission Phase _ ID = "number 1" Phase _ Name = "Name 1" >)

< L _ Connection _ ID = "Connection _ Type =" Logic _ Connection "FrontNode ="1 "realnode ="2 "/>)

< System_Unit System_ID="2" System_Name=" ">

…

</ System_Unit >

<Logic_Mark Logic_ID="1" Logic _Name=" " Logic _Type=”AND”/>

…

</ Phase_Mission >

(3) Label structure of system state transition description model

The label of the system state transition description model comprises two sub-elements, namely a component state element and a state transition element, besides the attribute of the label.

The component State element comprises element attributes such as State _ ID and State _ Name, and the State Transition element comprises element attributes such as Transition _ ID, transition _ Name, startID, endID and Condition.

The XML specification description is as follows:

< System_Unit System_ID="2" System_Name=" ">

…

…

</ System_Unit >

B. establishing an analysis model for system task reliability analysis;

defining a transition structure of an XML label of a DoDAF submodel by taking the DoDAF submodel as input on the basis of an extended object-oriented Petri network (EOOPN) model; providing a method for converting the DoDAF submodel into the EOOPN submodel, and converting the DoDAF submodel into three corresponding EOOPN submodels; the three EOOPN submodels are a combat mission multi-stage model, a stage mission reliability model component state model and a system state transition description model.

First, the metamodel group class of the EOOPN model is composed of a Place class, a Transition class, an Arc class, and itself.

The library Place class has three inherited subclasses, namely an Information Place class, a Broadcast Place class and a Simple Place class.

Meanwhile, there is a one-to-one initial identification (initial identification) class composite with the vault class for representing the token condition in the vault in the initial case. The Token (Token) class is a compound relationship with the vault class.

The Transition class has six inherited subclasses, which are respectively an And gate Transition (And Transition) class, a Not gate Transition (Not Transition) class, an Or gate Transition (Or Transition) class, a voting gate Transition (RN Transition) class, a probability gate Transition (PRO Transition) class And a Delayed gate Transition (Delayed Transition) class. A Probability gate transition class may compound multiple Probability (Proavailability) classes. One time delay gate transition class can compound a plurality of transition color (transition-color) classes, and one transition color class can only compound one Distribution (Distribution) class.

The arc class has two integrated subclasses, namely a front arc (front) class and a rear arc (rear) class. Meanwhile, there are three classes that represent the attributes of the arc in combination with the arc class. Respectively as follows: source (source), end (end), and arcnote expressions. The source has an attribute frommonodeid, the end has an attribute tonodeld, and the on-arc expression has an attribute express.

The relationship between the arc and the library and the transition can be described as: a top arc can be connected exclusively as an output of a library and an input of a transition, and a bottom arc can be connected exclusively as an output of a transition and an input of a library.

In the EOOPN submodel, the XML tag structure is specifically as follows:

(1) Label structure of EOOPN

EOOPN includes two PetriNetID, petriNetName element attributes.

The XML specification description is as follows:

< EOOPN id = "number" name = "name" >)

< EOOPN id = "number 1" name = "name 1" >)

…

</EOOPN>

…

</EOOPN>

(2) Label structure of Place

1. Label structure of Simple Place

The simple library includes two sub-elements, a simple library element and an initial identification element.

The simple library elements comprise element attributes such as place _ ID, place _ Name, capacity, placeTag, moveSequence and the like, and the initial identification elements comprise express element attributes.

There are two options for the token move out rule for the pool, first In First Out (FIFO) and First In Last Out (FILO). Meanwhile, a "PlaceTag" library identifier is set for the library, and the identifier means that the token condition in the library identifier is counted after simulation.

The XML standardization of the method is described as follows:

< SimplePlace place _ id = "number" place _ name = "name" capacity = "4" PlaceTag = "null" Movesequence = "FIFO" >)

</SimplePlace >

2. Tag structure of Information Place

The information base comprises two sub-elements, namely an information base element and an initial identification element.

The elements of the information base comprise element attributes such as place _ ID, place _ Name, capacity, placeTag, moveSequence and the like, and the initial identification element comprises an express element attribute.

The XML specification description is as follows:

< InformationPlace place _ id = "number" place _ name = "name" capacity = "1" place tag = "null" move sequence = "FIFO" >)

</InformationPlace >

3. Label structure of Broadcast Place

The broadcast base element includes two sub-elements, which are a broadcast base element and an initial identification element.

The elements of the broadcast library comprise element attributes such as place _ ID, place _ Name, capacity, placeTag, moveSequence and the like, and the initial identification element comprises an express element attribute.

The XML specification description is as follows:

< BroadcastPlace _ id = "number" place _ name = "name" capacity = "100" PlaceTag = "null" Movesequence = "FIFO" > ", and" name "capacity ="100 "PlaceTag =" null "Movesequence =" FIFO ">"

</BroadcastPlace >

(3) Transition (Transition) tag structure

1. Tag structure of AND gate Transition (Add Transition)

The AND gate transition element includes element attributes such as transition _ ID, transition _ Name, and priority.

The priority (priority) of the transition indicates the priority in which the transition is enabled when the ignition is selected. The higher the priority, the smaller the priority value of the transition.

The XML specification description is as follows:

< transmission _ ID = "number" transmission _ Name = "Name" priority = "0"/>)

2. Tag structure of Not Transition (Not Transition)

The NOT gate transition element includes element attributes such as transition _ ID, transition _ Name, and priority.

The XML specification description is as follows:

< NotTransition transition _ ID = "number" transition _ Name = "Name" priority = "0"/>)

3. Tag structure of OR gate Transition (Or Transition)

The OR gate transition element includes element attributes such as transition _ ID, transition _ Name, priority, and the like.

The XML specification description is as follows:

< OrTransition transition _ ID = "number" transition _ Name = "Name" priority = "0"/>)

4. Label structure of voting gate Transition (RN Transition)

The voting gate transition element contains element attributes such as transition _ ID, transition _ Name, priority, R, and the like.

The condition R represents the number of bins required to fire the transition that satisfy the condition on the arc.

The XML standardization of the method is described as follows:

< RNTransition transition _ ID = "number" transition _ Name = "Name" = "0" R = "1"/>)

5. Label structure of probability gate Transition (PRO Transition)

The probability gate transition element comprises two sub-elements, namely a probability gate transition element and a trigger probability element.

The probability gate transition element comprises element attributes such as transition _ ID, transition _ Name and priority, and the trigger probability element comprises element attributes such as value and pro.

The trigger Probability (Proavailability) represents the arrival of tokens corresponding to different token states (value), and the trigger Probability of the probabilistic gate transition is pro. A probability gate transition may have a number of different trigger probabilities.

The XML specification description is as follows:

< PROTRANSITION TRANSITION _ ID = "number" transition _ Name = "Name" priority = "0" >)

</PROTransition>

6. Label structure of Delayed door Transition (Delayed Transition)

The time delay gate transition comprises three sub-elements, namely a time delay gate transition element, a transition color element and a distribution element.

The probabilistic gate transition element includes element attributes such as transition _ ID, transition _ Name, and priority, the transition color element includes value element attributes, and the distribution element includes element attributes such as type, value1, and value 2.

Transition-color indicates the arrival of tokens corresponding to different token states (values), and the resulting time delay profile of the delay gate transition is Distribution. Distribution (Distribution) has 6 probability Distribution types, including uniform Distribution, poisson Distribution, exponential Distribution, weibull Distribution, normal Distribution, and lognormal Distribution. A delay gate transition may have multiple transition colors, with one transition color corresponding to only one distribution type.

The XML standardization of the method is described as follows:

< DelayedTransition transmission _ ID = "number" transmission _ Name = "Name" priority = "0" >)

<transition-color value="1">

</ transition-color >

</DelayedTransition>

(4) Label structure of Arc (Arc)

1. The antecedent Arc comprises four sub-elements, and the element attributes of the antecedent Arc are antecedent Arc (Arc _ ID), source (frotneid), terminal (tonnodeid) and expression (express).

The XML specification description is as follows:

< front Arc _ ID = "number" >)

< source fromNodeID = "preceding item number"/>)

< end tonodeld = "item number after"/>)

</ front >

2. The post Arc comprises four sub-elements, and the element attributes of the four sub-elements are respectively post Arc (Arc _ ID), source (fromNodeID), terminal (toNodeID) and expression (express).

The XML specification description is as follows:

< real Arc _ ID = "number" >)

< source fromNodeID = "preceding item number"/>)

< end tonodeld = "item number after"/>)

</ rear >

(5) Label structure of Token (Token)

The Token element attributes include element attributes such as Token _ ID, token _ Name, token _ State, and Token _ Type.

The XML specification description is as follows:

< Token _ ID = "number" Token _ Name = "Name" Token _ Type = "Type" Token _ State = "0"/>)

On the basis of the label structure, an EOOPN model is applied to a multi-stage task system (PMS) for modeling, and a task reliability model of the PMS is divided into the following three layers:

the first layer models the PMS at the overall task level, including an EOOPN submodel. The model describes the category, duration and execution sequence of each phase task contained in the overall task. The model can be used to describe both tasks and the downward partitioning of phase tasks.

The second layer models the PMS at the stage task level, which defines an EOOPN submodel. The model mainly describes the working modes (series, parallel, voting or mixed connection) among weapon platforms which undertake the stage and the stage success state.

The third layer models the PMS at the component level, which defines an EOOPN submodel. The model mainly describes the state change information of the component.

1. Total task hierarchy

Reference is made to fig. 1, which shows details of the Phase one (Phase 1), phase two (Phase 2) and Phase eight (Phase 8), phase nine (Phase 9) models. The models of the other intermediate stages are the same as those of the second stage and the eighth stage. After phase i is executed, the token representing "success" of the phase enters the "i-mp3" pool, and the token representing "failure" of the phase enters the "i-mp4" pool. Next, whether the phase succeeds or not, the i-phase completion token is always passed into the next phase "i +1-mp1" pool. Thus, different completion conditions (success or failure) for the i stage will affect the task reliability of the i +1 stage and then the completion condition of the stage.

The elements in the model are explained as follows:

b1, 1-mp1: the starting work information of the stage 1 is of the type of an information library;

e1, 1-mp2: the type of the end work information of the stage 1 is an information library;

and (4) Success: the task is successful, and the type is a simple library;

failure: the task fails, and the type is a simple library;

2-mp3: stage 2 fails, the type is simple library;

2-mp4: stage 2 succeeds, and the type is a simple library;

t0: representing the starting time of the task, wherein the type is time delay gate transition;

t1, t2, \8230;, t8, t9: the duration of the stage 1 to the stage 9 is respectively, and the type is time delay gate transition;

1-ADR1, 1-ADR2: and gate transition.

2. Staged task hierarchy

Taking the fourth stage task of the missile defense combat task as an example, the three early warning radars are connected in parallel and are connected in series with the command level C2 BMC. Assuming that the codes of the three early warning radars are a, b and C and the code of the commander level C2BMC system is d, the EOOPN model of the stage task reliability model at this stage is shown in fig. 2. If other working modes exist among weapon platforms at the same stage, the content in the dotted line frame is only replaced during modeling.

The elements in the model are explained as follows:

4-mp1: the work request from the system task indicates that the stage starts and the type is an information base;

mp1: a work start request descending to the weapon platform level one is classified as an information base;

mp2: the work ending request descending to the weapon platform level one is of the type of an information base;

4-mp2: the work end message from the system task indicates that the stage is ended, and meanwhile, the work end message descends to the first stage of equipment, and the type of the work end message is an information base;

4-mp4: the stage is successful, and the type is a simple library;

4-mp3: stage failure, the type is simple library;

a: the state and type of the equipment a are simple libraries;

b: the state and type of the equipment b are simple libraries;

bro1: the latest condition of the latest state information receiving stage of the broadcasting equipment in the broadcasting warehouse;

p: and (4) probability gate transition, wherein the probability of completing the task by the weapon platform is different for different completion conditions of the previous stages.

2. Component hierarchy

The components are the basic units that support the completion of the weapons platform task. It is assumed here that the components have only the following four states during task execution: "idle", "working" and "failed" and "failover". After the fault is repaired, the system does not participate in the task at the current stage, and only participates in the task coming from the next stage.

Taking fig. 3 as an example, a schematic diagram of a state model of components of an early warning radar (UEWR) is shown.

The elements in the model are explained as follows:

p1: UEWR is "idle" state, type is simple library. Initially, the token in the "idle" state is located in the vault;

mp1: the type of the work application (Activation request) information is an information base;

p2: UEWR is in a working state, and the type is a simple library;

p3: UEWR is a 'failure' state, and the type is a simple library;

p4: UEWR is a 'failure repair' state, and the type is a simple library;

mp2: UEWR operation end (release) message, the type is the information base;

b1: the broadcast base station receives the latest state information of the components and broadcasts the latest state information to other networks;

t1: UEWR fault events, of the type with delay gate transitions having some time distribution, different token states will trigger different fault time distributions, resulting in different delays. After this event, the component state becomes a failure (failure);

t2: UEWR repair events, of the type with delay gate transitions with certain time distributions, will trigger different maintenance time distributions, resulting in different delays. After this event, the state of the component becomes free;

AND1: and gate transition, when the work application message arrives and the UEWR state is idle (free), indicates that the UEWR starts to work. After this event, the UEWR state becomes active (busy);

AND2: and gate transition, when UEWR end of work message arrives and UEWR status is work (busy), indicating that UEWR stops working. After this event, the UEWR state becomes idle (free);

AND3: and the AND gate transitions, and when the UEWR operation end message arrives and the UEWR state is failure repair (free), the UEWR state becomes idle (free) again.

By introducing the ten system task reliability description requirement-oriented DoDAF models and the three system task reliability analysis-oriented EOOPN submodels, a non-professional Petri network modeling worker can complete the construction of the system task reliability description model and the system task reliability analysis model.

From the above description, it can be seen that the DoDAF submodel and EOOPN submodel have correspondence in three levels, namely, the total task, the stage task and the weapon platform, as shown in fig. 4, and the presence of the XML normalized description in the model provides a possibility for the conversion of the two types of models.

(1) Total task hierarchy conversion

FIG. 5 is a diagram of the conversion algorithm of the overall task hierarchy; in the multi-stage model of the mission in the DoDAF submodel, three XML tag elements appear in the XML document: the names are respectively 'DoDAF custom model', 'Phase _ Session' and 'P _ Connection', and the conversion steps are as follows:

step 101: reading in an XML document of a multi-stage model of the battle tasks in the DoDAF submodel and generating a XML writing stream;

step 102: judging whether XML label elements exist or not; if yes, go to step 103; if not, go to step 112;

step 103: reading the XML tag element, and turning to step 104 when the XML tag element is a 'DoDAF self-defined model'; when the XML tag element is not the 'DoDAF custom model', the step 105 is carried out;

step 108: writing a stage i subnet with the ID being Phase _ ID for an EOOPN network, and writing a stage starting library place, a stage finishing library place, a stage success library place and a stage failure library place for the stage i subnet; entering the next layer of the 'Phase _ Session' label, namely the time delay transition of the end of the writing Phase of the 'EOOPN' network, the AND gate transition of the success Phase and the failure Phase, writing the arc between the end transition of the end library location and the write connection, the successful library location and the successful transition, and the failure library location and the failure transition;

step 111: switching to a stage task level conversion algorithm;

step 112: and (6) ending.

(2) Transition of stage task hierarchy

FIG. 6 is a schematic diagram of a phase task level conversion algorithm; in the phase task reliability logic model in the DoDAF submodel, three XML tag elements appear in the XML document: the names are respectively 'System _ Unit', 'Logic _ Mark' and 'L _ Connection', and the conversion steps are as follows:

step 202: reading the XML tag element, and turning to step 203 when the XML tag element is 'Logic _ Mark'; when the XML tag element is not "Logic _ Mark", proceed to step 204;

step 203: writing Logic transition with the ID of Logic _ ID and the Type of Logic _ Type opposite to the ID of the phase i subnet; returning to the step 201;

step 209: writing in the intermediate library for the stage i subnet, writing in the arcs of both FrontNode and RearNode and the intermediate library; then, the subnet at the stage i is written into the second intermediate library, and an arc connecting the FrontNode and the RearNode and the second intermediate library is written into the subnet at the stage i; returning to the step 201;

step 210: judging whether one end is empty, if so, turning to a step 211, otherwise, turning to a step 212;

step 211: writing an arc for the stage i subnet, wherein the front item is FrontNode, and the back item is a broadcast base; writing an arc for the stage i subnet, wherein the front item is-FrontNode, and the back item is a broadcast base; writing an arc for transmitting a work starting message for the phase i subnet, wherein the front item is a FrontNode, and the back item is a unit work starting library; returning to the step 201;

step 214: and (6) jumping out.

(3) Component task hierarchy conversion

Referring to fig. 7, which is a schematic diagram of a conversion algorithm at a component task level, in a system state transition model in the DoDAF submodel, two XML tag elements appear in an XML document: the names are respectively 'State' and 'Transition', and the conversion steps are as follows:

step 302: reading the XML tag element, and when the XML tag element is 'State', turning to step 303; when the XML tag element is not "State", proceeding to step 304;

step 303: writing a library with the ID of State _ ID for a component State network with the ID of System _ ID; returning to the step 301;

step 307: writing an AND gate Transition with the ID of Transition _ ID for a component state network with the ID of System _ ID; writing an arc into a component state network with the ID of System _ ID, wherein the former item is Condition and the latter item is Transition _ ID;

step 309: writing an arc into a component state network with the ID of System _ ID, wherein the former item is Transition _ ID and the latter item is End _ ID; writing an arc into a component state network with the ID of System _ ID, wherein the former item is Transition _ ID, and the latter item is a broadcast library; turning to step 301;

After the three layers are converted, a framework of the EOOPN model can be obtained, and some detail information in the EOOPN model, such as token information in a library, color information on transitions, and expression information on arcs, needs to be edited and added by a user subsequently.

Examples of editing additions may be as follows:

read "XML file for DoDAF";

generating a stream for writing an XML document;

// the File stream is used to record EOOPN models representing multi-phase models of combat missions

(1) First layer, conversion to mission Multi-stage EOOPN model

Create FirstLevel (DoDAF XML file)

{

Switch( NodeName )

{

case "DoDAF custom model":

writing the outermost mesh;

the element name EOOPN;

the attributes are as follows: { id = "EOOPN", name = "EOOPN" };

writing to a library for an "EOOPN" network;

// failure depot

Element name simplepace;

the attribute is as follows: { place _ id = "Failure"; place _ name = "Failure", capacity = "100000", placeTag = "null", movesequence = "FIFO" };

the child element name Initialmarking;

the attribute is as follows: { express = "" };

v/successful depot

The type is SimplePlace, the ID is "Success", and the initial representation is null;

// broadcasting depot

The type is BroadcastPlace, the ID is 'bro 1', and the initial representation is null;

writing arcs for the "EOOPN" net;

// the arc connects the success depot with 9-ADR1 (success AND gate of last stage)

The type is RearArc, the ID is 'Success', the former ID is 9-ADR1, the latter ID is Success, and the expression on the arc is null;

// the arc connects the failure repository with 9-ADR2 (last stage failure AND gate)

The type is RearArc, the ID is 'Failure', the former ID is 9-ADR2, the latter ID is Failure, and the expression on the arc is null;

break；

case “Phase_Mission”:

writing into a phase i subnet;

the element name EOOPN;

the attributes are as follows: { ID = Phase _ ID, name = Phase _ Name };

writing the stage i subnet network into a library place;

// phase Start storehouse

The type of the library 1 is InformationPlace, the ID is 'b' + i, and the library is initially represented as null;

the library 2 is InformationPlace in type, the ID is i + "-mp1", and the initial representation is null;

// end of stage depot

The library 1 type is InformationPlace, the ID is 'e' + i, and the initial representation is null;

the library 2 type is InformationPlace, the ID is i + "-mp2", and the initial representation is null;

// stage success depot

Type SimplePlace, ID i + "-mp4", initially indicated as null;

// stage failure depot

The type is SimplePlace, the ID is i + "-mp3", and the initial representation is null;

writing transitions for the "EOOPN" net;

successful AND gate transition

The element name anddistribution;

the attribute is as follows: { transition _ ID = i + "-ADR1", transition _ name = i + "-ADR1", priority = "0" };

// stage failure AND Gate transition

Type is AndTransmission, ID is i + "-ADR2";

// phase end delay transition

The element name DelayedTransition;

the attributes are as follows: { transition _ ID = "t" + i, transition _ name = "t" + i, priority = "0" };

the sub-element name transition-color;

the attributes are as follows: { value = "" };

the child element name Distribution;

the attributes are as follows: { type = "const", value1= T2, value2= "" };

writing arcs for the "EOOPN" net;

// the arc connects the end-of-phase library 1 with the end-of-phase delay transition

The type is SimpleArc, the ID is i + 'end', the ID of the front item is 'e' + i, the ID of the back item is't' + i, and the expression on the arc is null;

// the arc connects the end-of-phase delay transition with the end-of-phase repository 2

The type is RearArc, the ID is 'end' + i, the ID of the front item is't' + i, the ID of the back item is i + '-mp 2', and the expression on the arc is null;

// the arc connects the stage success AND gate with the stage success library

The type is SimpleArc, the ID is s + i, the ID of the front item is i + "-mp4", the ID of the back item is i + "-ADR1", and the expression on the arc is null;

// the arc connects the stage failure AND gate with the stage failure library

The type is SimpleArc, the ID is 'f' + i, the ID of the front item is i + '-mp 3', the ID of the back item is i + '-ADR 2', and the expression on the arc is null;

writing the next layer of network, and stage task reliability model;

Create SecondLevel（Phase_Mission）；

additional operations on the first stage task;

if (i = 1)// If the phase task is the first phase

{

// adding several elements additionally

// adding a task-initiated time-delayed transition for EOOPN networks

The type is delayedtdisplacement, the ID is "T0", the time delay is a constant, and the constant value is the first stage start time T1;

v/arc between the adding start library for EOOPN network and the time delay transition

The type is SimpleArc, the ID is 'b 1', the ID of the front item is 'b 1', the ID of the back item is't 0', and the expression on the arc is null;

the type is RearArc, the ID is '1 b', the ID of the front item is't 0', the ID of the back item is '1-mp 1', and the expression on the arc is null;

}

break；

case “P_Connection”:

// adding three arcs to the EOOPN network, linking two phase tasks with sequential phase

The type of the first arc is SimpleArc, the ID is Connection _ ID + '1', the former ID is the beginning library place 'b' of the real Session, the latter ID is the 'ADR 1' of the FrontSession, and the expression on the arc is null;

the second arc type is RearArc, the ID is Connection _ ID + '2', the former ID is ADR1 of Front Session, the latter ID is mp1 of the beginning library of RearSession, and the expression on the arc is null;

the second arc type is RearArc, the ID is Connection _ ID + '3', the former ID is ADR2 of Front Session, the latter ID is mp1 of the beginning library of RearSession, and the expression on the arc is empty;

Break；

}

(2) Second layer, transition to phase task reliability EOOPN model

Create SecondLevel（Phase_Mission）

{

The following operations are all additions of elements to the stage i subnet

Switch( NodeName )

{

case “System_Unit”:

Writing a library place with the type of SimplePlace and the ID of System _ ID, and initially indicating that the library place is null;

writing a library place with the type SimplePlace, the ID of System _ ID + "', and the initial representation of null;

writing a transition with the type of PROtransition and the ID of pro + System _ ID;

writing two arcs, the type of which is SimpleArc, connecting the two declared banks with a transition, wherein the expression on the arcs is null;

writing the next layer of net and the component state model;

the element name EOOPN;

the attribute is as follows: { ID = System _ ID, name = System _ Name };

Create ThirdLevel（System_Unit）；

Break；

case “Logic_Mark”：

writing a Logic transition, wherein the Type is Logic _ Type, and the ID is Logic _ ID;

writing a Logic transition with Type opposite to Logic _ Type (or if AND gate, and if OR gate, and opposite), ID of "-" + Logic _ ID;

Break；

case “L_Connection”：

if (logic symbol at both ends of the connecting line)

{

Writing a library place, wherein the type is SimplePlace, the ID is 'p 3' + Connection _ ID, and the library place is initially indicated as null;

writing an arc, wherein the type is SimpleArc, the ID is Connection _ ID + '1', the ID of a front item is FrontNode, the ID of a back item is 'p 3' + Connection _ ID, and the expression on the arc is null;

writing an arc, wherein the type is SimpleArc, the ID is Connection _ ID + '2', the ID of a front item is 'p 3' + Connection _ ID, the ID of a back item is RearNode, and the expression on the arc is null;

writing a library place, wherein the type of the library place is SimplePlace, the ID is 'p 4' + Connection _ ID, and the library place is initially indicated as null;

writing an arc, wherein the type is SimpleArc, the ID is Connection _ ID + '3', the ID of the front item is-FrontNode, the ID of the back item is 'p 4' + Connection _ ID, and the expression on the arc is null;

writing an arc, wherein the type is SimpleArc, the ID is Connection _ ID + '4', the ID of a front item is 'p 3' + Connection _ ID, the ID of a back item is-RearNode, and the expression on the arc is null;

}

if (logic symbol on one end of the connecting line and weapon platform on the other end)

{

Writing an arc, wherein the type is SimpleArc, the ID is Connection _ ID + ' 1 ', the former ID is FrontNode + ', the latter ID is RearNode, and the expression on the arc is null;

writing an arc, wherein the type is SimpleArc, the ID is Connection _ ID + ' 2 ', the ID of the front item is FrontNode + ', the ID of the back item is-RearNode, and the expression on the arc is empty;

}

if (logic symbol at one end of the connecting line and empty at the other end)

{

Writing an arc, wherein the type is RearArc, the ID is Connection _ ID + '1', the ID of the front item is FrontNode, the ID of the back item is 'bro 1', and the expression on the arc is null;

writing an arc, wherein the type is RearArc, the ID is Connection _ ID + '2', the ID of the front item is-FrontNode, the ID of the back item is 'bro 1', and the expression on the arc is null;

// re-write arcs for downloading start-of-work information equal in number to the number of weapons platforms engaged in the task

The type is RearArc, the former ID is-FrontNode, the latter ID is 'mp 1' of the starting working library of each weapon platform participating in the task, and the expression on the arc is null;

}

// adding several modeling elements to perfect the stage task reliability model

Writing a logic transition with type of AndTranssition and ID Phase _ ID + "-ADR1";

v/adding an arc connected to the transition

Writing an arc, wherein the type is InformationArc, the former item is Phase _ ID + '-mp 1', the latter item is Phase _ ID + '-ADR 1', and the expression on the arc is empty;

writing an arc, wherein the type of the arc is SimpleArc, the front item is bro1, the back item is Phase _ ID + "-ADR1, and the expression on the arc is null;

writing a plurality of arcs, wherein the type is RearArc, the front item is Phase _ ID + "-ADR1", the back item is each weapon platform participating in the task at the stage, and the expression on the arcs is null;

writing a logic transition with type of AndTranssition and ID Phase _ ID + "-ADR2";

writing an arc, wherein the type of the arc is SimpleArc, the front item is Phase _ ID + "-mp1", the back item is Phase _ ID + "-ADR2", and the expression on the arc is empty;

writing an arc, wherein the type of the arc is SimpleArc, the front item is Phase _ ID + "-mp2", the back item is Phase _ ID + "-ADR2", and the expression on the arc is empty;

writing an arc, wherein the type is RearArc, the front item is Phase _ ID + "-ADR2", the back item is Phase _ ID + "-mp4", and the expression on the arc is null;

writing a logic transition with type of AndTranssition and ID Phase _ ID + "-ADR3";

writing an arc, wherein the type of the arc is SimpleArc, the front item is Phase _ ID + "-mp1", the back item is Phase _ ID + "-ADR3", and the expression on the arc is empty;

writing an arc, wherein the type is SimpleArc, the former term is bro1, the latter term is Phase _ ID +' -ADR3, and the expression on the arc is null;

writing an arc, wherein the type is RearArc, the front item is Phase _ ID + "-ADR3", the back item is Phase _ ID + "-mp3", and the expression on the arc is null;

}

(3) Third level, EOOPN model for component State transition

Create ThirdLevel（System_Unit）；

{

The following operations are all added elements to the component status of the System _ ID

Writing a warehouse entry, wherein the type is InformationPlace, the ID is System _ ID + "-mp1", and the initial representation is null;

writing a warehouse entry, wherein the type is InformationPlace, the ID is System _ ID + "-mp2", and the initial representation is null;

Switch( NodeName )

{

Case “State”:

writing a warehouse entry, wherein the type is SimplePlace, the ID is State _ ID, and the initial representation is null;

Case “Transition”:

if (Condition is not empty)

{

Writing in Transition, wherein the type is AndTransition, and the ID is Transition _ ID;

the type of the write-in arc is SimpleArc, the ID is Transition _ ID + '1', the former item is Start _ ID, and the latter item is Transition _ ID;

the type of the write-in arc is SimpleArc, the ID is Transition _ ID + '2', the former item is Condition, and the latter item is Transition _ ID;

the type of the write-in arc is RearArc, the ID is Transition _ ID + '3', the former item is Transition _ ID, and the latter item is End _ ID;

the type of the write arc is RearArc, the ID is Transition _ ID + '4', the former item is Transition _ ID, and the latter item is 'bro 1';

}

else

{

writing in Transition, wherein the type is DelayTransition, the ID is Transition _ ID, and the time parameter is undetermined;

the type of the write-in arc is RearArc, the ID is Transition _ ID + '2', the former item is Transition _ ID, and the latter item is End _ ID;

the type of the write arc is RearArc, the ID is Transition _ ID + "3", the former item is Transition _ ID, and the latter item is "bro1";

}

break；

}

in conclusion, after some detail information in the EOOPN model is edited and supplemented, an analysis model for system task reliability analysis is established, and a platform basis is provided for obtaining a numerical solution of equipment system task reliability later.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for establishing an equipment architecture task reliability model, comprising the steps of:

establishing a description model for describing the reliability of the system task;

expanding a system interface model based on a 2.0 framework of a system framework of the United states department of defense; constructing three DoDAF submodels, namely a combat mission multi-stage model for describing a stage mission, a stage mission reliability logic model for describing reliability logic and a system state transition description model for describing component state transition in a DoDAF view product;

establishing an analysis model for system task reliability analysis;

on the basis of an EOOPN model, a DoDAF submodel is used as input, a transition structure of an XML label of the EOOPN submodel is defined, and the DoDAF submodel is converted into three corresponding EOOPN submodels; applying the EOOPN model to the multi-stage task system for modeling; the three EOOPN submodels are a combat mission multi-stage model, a stage mission reliability model component state model and a system state transition description model.

2. The method for building an equipment architecture task reliability model according to claim 1, wherein the three DoDAF submodels are specifically:

the multi-stage model of the battle mission divides the working time of the weapon platform in each stage, the time slices in the same stage have the same length after division, and the time sequence logic description is carried out on the mission and the execution sequence of each stage;

a stage task reliability logic model, an expansion system interface description model and three logic signs of AND, OR and voting are introduced to describe reliability logic between weapon platforms or between components;

3. The method for establishing the equipment architecture task reliability model as claimed in claim 1, wherein the transition structure defining the EOOPN submodel XML tag specifically is:

4. The method for building equipment architecture task reliability model according to claim 3, characterized in that, the method comprises

The method for applying the EOOPN model to the multi-stage task system for modeling specifically comprises the following steps:

the modeling of the multi-stage task system is divided into three layers:

5. The method for building equipment architecture task reliability model according to claim 4, wherein the transformation step of modeling the overall task hierarchy is:

step 110: writing the time delay transition of the next task start for the phase i subnet; writing an arc connecting a starting library place and the time delay transition into the stage i subnet;

step 111: switching to a stage task level conversion algorithm;

step 112: and (6) ending.

6. The method for building equipment architecture task reliability model according to claim 4, wherein the conversion step of the modeling of the phase task hierarchy is:

step 205: writing the i-subnet into the equipment library and the equipment working library, writing the i-subnet into a probability gate transition, and adding an arc connecting the equipment library, the equipment working library and the probability gate transition; writing a component state network with the ID being System _ ID into the stage i subnet;

step 206: entering the next layer of the System _ Unit label, and switching to a component level conversion algorithm;

step 209: writing in the intermediate library for the stage i subnet, writing in the arcs of both FrontNode and RearNode and the intermediate library; then, writing in an intermediate library for the stage i subnet, and writing in an arc connecting the FrontNode and the RearNode and the intermediate library; returning to the step 201;

step 212: writing an arc for the stage i subnet, wherein the former item is an equipment working library and the latter item is RearNode; writing an arc for the stage i subnet, wherein the former item is an equipment working library and the latter item is-RearNode; returning to the step 201;

step 213: writing an AND gate transition representing the stage start for the stage i subnet, and writing arcs connecting the stage start library location, the broadcast library location, the stage start AND gate transition and each equipment library location; writing in an AND gate transition representing the start of a stage, and writing in an arc connecting a stage start library station, a stage end library station, a stage success AND gate transition and a stage success library station; writing in an AND gate transition representing a stage failure, and writing in arcs of a connection stage starting library place, a broadcast library place, a stage failure AND gate transition and a stage failure library place;

step 214: and (6) jumping out.

7. The method for building equipment architecture task reliability model according to claim 4, wherein the conversion step of modeling at component task level is:

step 305: judging whether the Condition is empty, if so, turning to step 306; if not, go to step 307;

step 310: and finally, jumping out of the layer and returning to the conversion algorithm of the stage task layer.