CN113128878A

CN113128878A - Equipment guarantee simulation rule construction method and terminal equipment

Info

Publication number: CN113128878A
Application number: CN202110441814.9A
Authority: CN
Inventors: 刘彬; 高鲁; 吴巍屹; 古平; 于同刚; 郑丽珍; 屈金标; 颜鹏
Original assignee: Army Engineering University of PLA
Current assignee: Army Engineering University of PLA
Priority date: 2021-04-23
Filing date: 2021-04-23
Publication date: 2021-07-16

Abstract

The invention is suitable for the technical field of equipment, and discloses an equipment guarantee simulation rule construction method and terminal equipment, wherein the method comprises the following steps: acquiring equipment guarantee simulation rules, and storing the equipment guarantee simulation rules into an equipment guarantee simulation rule base; detecting whether the equipment guarantees that a rule with a defect exists in a simulation rule base; and if the equipment guarantee simulation rule base is detected to have the rule with the defect, optimizing the rule with the defect to obtain the optimized equipment guarantee simulation rule base. The invention can realize the automatic maintenance of the equipment guarantee simulation rule base without manual maintenance, thereby greatly improving the efficiency and saving the time.

Description

Equipment guarantee simulation rule construction method and terminal equipment

Technical Field

The invention belongs to the technical field of equipment, and particularly relates to an equipment guarantee simulation rule construction method and terminal equipment.

Background

The equipment security simulation rule is the basis of the equipment security simulation, so that the equipment security simulation rule needs to be established firstly in the process of carrying out the equipment security simulation. The established equipment security simulation rules can be stored in the equipment security simulation rule base.

In the initial stage of establishing the equipment guarantee simulation rule base, the scale is small, the equipment guarantee simulation rule base can be maintained by adopting a manual method, but in the later stage, along with the gradual increase of the rules, the scale of the equipment guarantee simulation rule base is gradually increased, the relation and the influence among the rules are gradually complicated, and the manual maintenance can not meet the requirements of time and efficiency.

Disclosure of Invention

In view of this, the invention provides an equipment assurance simulation rule construction method and a terminal device, so as to solve the problem that the prior art cannot meet the requirements of time and efficiency.

The invention provides a method for constructing an equipment security simulation rule, which comprises the following steps:

acquiring equipment guarantee simulation rules, and storing the equipment guarantee simulation rules into an equipment guarantee simulation rule base;

detecting whether the equipment guarantees that a rule with a defect exists in a simulation rule base;

and if the equipment guarantee simulation rule base is detected to have the rule with the defect, optimizing the rule with the defect to obtain the optimized equipment guarantee simulation rule base.

A second aspect of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the equipment assurance simulation rule construction method according to the first aspect when executing the computer program.

A third aspect of the present invention provides a computer-readable storage medium storing a computer program which, when executed by one or more processors, implements the steps of the equipment assurance simulation rule construction method according to the first aspect.

Compared with the prior art, the invention has the following beneficial effects: according to the invention, the acquired equipment guarantee simulation rule is stored in the equipment guarantee simulation rule base, whether the equipment guarantee simulation rule base has the rule with the defect or not is detected, if so, the rule with the defect is optimized to obtain the optimized equipment guarantee simulation rule base, so that the automatic maintenance of the equipment guarantee simulation rule base can be realized, the manual maintenance is not needed, the efficiency can be greatly improved, and the time is saved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic flow chart illustrating an implementation of a method for constructing an equipment assurance simulation rule according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an input interface of equipment assurance simulation rules according to an embodiment of the present invention;

FIG. 3 is a block diagram of an SWRL in accordance with an embodiment of the present invention;

fig. 4 is a schematic block diagram of an equipment assurance simulation rule construction apparatus according to an embodiment of the present invention;

fig. 5 is a schematic block diagram of a terminal device according to an embodiment of the present invention.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

In order to explain the technical means of the present invention, the following description will be given by way of specific examples.

Fig. 1 is a schematic implementation flow diagram of an equipment assurance simulation rule construction method according to an embodiment of the present invention, and for convenience of description, only a part related to the embodiment of the present invention is shown. The execution main body of the embodiment of the invention can be terminal equipment.

As shown in fig. 1, the method may include the steps of:

s101: and acquiring the equipment guarantee simulation rule, and storing the equipment guarantee simulation rule into an equipment guarantee simulation rule base.

Wherein the equipment assurance simulation rules describe the related art constraints in the equipment assurance simulation for specifying what actions are necessary, optional, or prohibited for the involved objects to follow under a certain scenario, context, or state in the equipment assurance simulation. The information sources for establishing the equipment guarantee simulation rule mainly comprise: equipment support documentation, documents related to previous development systems, equipment support domain experts, and the like. The equipment assurance simulation rules should have the following characteristics:

normalization. Normalization means that the representation adopted by the equipment assurance simulation rule has definite regulations and adopts accepted and unambiguous concepts, terms, symbols and grammars. Only in a standardized semantic environment, development groups in different fields can form consistent understanding and description on the field space concerned commonly, the quality hidden trouble is eliminated as early as possible in the development process, and a foundation is laid for the integration and reuse of the system.

Constraint. The equipment guarantee simulation rule is used for restricting the behavior of individuals in the field and determining what the individuals can do or not do under a specific environment. Its restrictive behavior is that under certain conditions, the basic conditions, range and direction of movement or change of things are limited, and some degree of "causal" relationship is determined.

Triggering. The triggering performance of the equipment guarantee simulation rule is embodied as that the rule corresponds to a certain reaction behavior, and the behavior can be triggered under a certain situation, background or state.

Extensibility. The expandability of the equipment guarantee simulation rule is embodied in two aspects: firstly, the rules in the simulation system can be customized according to the special simulation application target of the user, which is an important guarantee for improving the system; and secondly, modifying and supplementing the semantic environment of the equipment guarantee simulation rule according to the requirement.

According to the characteristics of the equipment assurance simulation rules, the equipment assurance simulation rules can be divided into three categories, namely constraint rules, deduction rules and behavior rules.

Constraint rules are statements of importance in the domain that detail explicit, static concepts in the domain, primarily for the purpose of ensuring the legitimacy of the domain concepts. Constraints can be divided into mandatory and instructive constraints. The difference between them is that when an event occurs that violates a mandatory constraint rule, the rule refuses to continue execution downwards, and when an instructive business rule is violated, the rule alerts the user that execution can continue. For example: the mandatory constraint is the constraint that the equipment command post must open, and the instructive constraint is the constraint that the equipment command post can open.

Deductive rules, also called derivative rules, are rules that result from the derivation or mathematical computation of constraint rules, other derivative facts or behavioral rules. Deductive rules can be divided into two categories, computational rules and deductive rules. The calculation rule describes the process of calculating an expression, which uses arithmetic operations to derive a new arithmetic value, such as the rule "maneuvering speed 50% × equipment maximum speed". Derivation rules are derived by logical reasoning or inference to derive a new fact, consisting of one or more preconditions and conclusions that can only be satisfied IF all the preconditions hold, as in the rule "IF P (x1) ^ P (x2) THEN Q (y)".

An action rule is a rule on some dynamic aspect in the field that specifies constraints that may have an impact on an action, specifying that an action should be activated when a certain event occurs or when a condition that needs to be satisfied is satisfied. The constraint may be a plurality of, linked by a logical conjunction such as AND, OR, NOT, etc. For example: if the rescue team arrives at the predetermined location and the designated equipment is trapped, it is a behavior rule to start the rescue of the equipment.

Alternatively, embodiments of the present invention primarily consider deductive rules and behavioral rules, both of which may be expressed in "IF … THEN …" format.

The embodiment of the invention provides a method for constructing an equipment guarantee simulation rule, and particularly provides a method for constructing an equipment guarantee simulation rule base. Firstly, acquiring an equipment guarantee simulation rule, specifically, acquiring an equipment guarantee simulation rule input by a user, and storing the acquired equipment guarantee simulation rule in an equipment guarantee simulation rule base. An interface diagram of the user input equipment safeguard simulation rule is shown in fig. 2.

In an embodiment of the present invention, the equipment assurance simulation rules are described using SWRL (Semantic Web Rule Language).

In order to better express what a rule contains and what is implemented, the rule needs to be described in a uniform form so as to realize effective management of the rule. However, at present, there is no uniform rule description form, and different rule models have different rule descriptions. The main rule description methods are as follows: decision tables, decision trees, rule description languages, and scripts.

The decision table represents the rules in the form of a table, each row represents a rule, the columns represent conditions or actions, and when all conditions are satisfied, the action is performed.

Decision trees are tree structures that represent a set of rules, each branch representing a decision path, and leaf nodes representing results or actions.

Rule description language refers to a syntactic description rule using a certain language. There are currently a number of rule languages, each of which is suitable for solving problems in its particular domain, can provide better performance, but is more difficult to maintain than graphical representations.

Scripts (templates) are the business logic used to describe the procedural, the basis for decision tables, decision trees, rule languages. By using the script, a regular expression form with a good structure can be obtained.

In the equipment guarantee simulation, whether the model is reasonable or not is mainly verified by using rules, and the readability of the rules must be strong, so that the rules can be identified by a machine and can support reasoning. Therefore, we select a rule description language to describe the rule. Rule description languages are generally divided into two categories: one type is "business-oriented" rule language, which is the language used by business personnel and usually can be recognized by machines after "translation"; the other type is a rule language of 'program-oriented technology', which has strong technical performance and weak readability and is suitable for technical developers to use. The semantic Web rules language SWRL is a rule description language that has been used by more and more developers in recent years to represent rules due to its well-formed and supporting logical reasoning.

The SWRL is a Language for expressing rules in a semantic mode, integrates the characteristics of OWL (Web Ontology Language) and Rule ML (Rule Markup Language), well combines the rules with an Ontology library of the OWL, and describes inference rules by using the SWRL so as to realize interaction between Rule knowledge and Ontology knowledge described by the OWL and maximally realize the reusability and interoperability between the Rule knowledge in the OWL system. SWRL is mainly composed of four parts, i.e., Imp, Atom, Variable and build-ins, and its architecture is shown in FIG. 3.

As can be seen from FIG. 3, the rule of SWRL is composed of Imp, in which the head in RuleML represents the inference result and the body represents the basic form of the inference premise. The basic component of head and body that is allowed to appear is Atom, i.e. the Hom clause used in its architecture is composed of Atom. The head part of Imp allows only one Atom to appear, while the body part allows the conjunctions of several Atom to appear, i.e. rules have the characteristics of Atom clauses, while having the form of Atom clauses may facilitate reasoning. The variables used in Atom are partially recorded in Variable, and Atom contains a single restriction formula, which can be divided into four types:

c (x): c is the description of the class in the OWL ontology, and x is an individual variable or an OWL individual;

p (x, y): p is an object type attribute in the OWL ontology, and x and y can be variables, data types or instances;

sameAs (x, y): the variables x and y are equal;

divientfrom (x, y): the variables x and y are different.

The build-ins is a SWRL modular component, and all logic comparison relations that can be referred to in the SWRL rules are recorded in the build-ins. Respectively, for numerical comparisons, mathematical calculations, boolean operations, string operations, time and date, etc. For example, build-Ins for numerical comparison includes: lessthanan, lessThanOrEqual, greaterthanteran, greaterThanOrEqual, etc., may be used to compare the correlation numerical relationships in the equipment assurance simulation model.

The SWRL can be regarded as a combination of a rule and an ontology, and the combination of the rule and the ontology enables the relationship and words described in the ontology to be directly used when the rule is written, and the relationship between the categories may need additional rule description, but the description of the ontology can be directly used in the SWRL. A rule contains a premise (body) and a conclusion (head). When the premise is satisfied (true), then the conclusion must be satisfied. This feature makes SWRL writing domain rules easier. For example, the following relationships are defined in the ontology:

Instanceof(m,C)

HasAttribute(C,A)

by ontology description we can know that m (first-aid repair 1 group) is an example of class C (tracked armor first-aid repair group), the tracked armor first-aid repair group has attribute of a (armor equipment repair capability), and a rule is designed by SWRL to explain the relation between m and a, and the description is as follows:

body

Instanceof(m,C)

HasAttribute(C,A)

head

HasAttribute(m,A)

embodiments of the present invention may use SWRL Tab plug-ins to edit rules, which allows a user to seamlessly switch between SWRL rule editing environments and common OWL editing environments at will. The editing interface of the above rule in the plug-in is shown in fig. 2, and is described as follows:

Instanceof(？x,？y)∧HasAttribute(？y,？z)→HasAttribute(？x,？z)

s102: and detecting whether the equipment guarantees that the simulation rule base has a rule with a defect.

While the equipment assurance simulation rules are part of the conceptual modeling, another important function is to implement rule reuse while they are used to verify the conceptual model. Therefore, the embodiment of the invention forms all the rules into the equipment guarantee simulation rule base, so that the rules can be added, deleted, modified and inquired by field experts and modeling personnel conveniently. At the initial stage of establishing the equipment guarantee simulation rule base, the scale of the equipment guarantee simulation rule base is possibly small, the equipment guarantee simulation rule base can be maintained by adopting a manual method, but along with more and more rules, the scale of the equipment guarantee simulation rule base is also increased, the interrelation and influence among the rules are more and more complex, and the manual maintenance method cannot meet the requirement, so that the embodiment of the invention can automatically analyze and check the equipment guarantee simulation rule base and automatically detect the rules with defects.

By analyzing the defect characteristics of the equipment guarantee simulation rule, the rules with defects are divided into 5 types, namely an equivalence rule, a circulation rule, a conflict rule, an inclusion rule and a omission rule. The embodiment of the invention can detect and optimize the 5 types of defective rules to obtain an optimized equipment guarantee simulation rule base.

S103: and if the equipment guarantee simulation rule base is detected to have the rule with the defect, optimizing the rule with the defect to obtain the optimized equipment guarantee simulation rule base.

As can be seen from the above description, in the embodiment of the present invention, the obtained equipment security simulation rule is stored in the equipment security simulation rule base, and whether a rule having a defect exists in the equipment security simulation rule base is detected, and if the rule having the defect exists in the equipment security simulation rule base, the rule having the defect is optimized to obtain the optimized equipment security simulation rule base, so that automatic maintenance of the equipment security simulation rule base can be achieved, manual maintenance is not required, efficiency can be greatly improved, and time can be saved.

In one embodiment of the invention, the rules for which there is a defect include equivalence rules;

the method for detecting whether the equipment guarantee simulation rule base has a rule with a defect comprises the following steps:

extracting clauses in the equipment security simulation rule base according to the sequence, and assigning sequence numbers to the extracted clauses;

for each equipment guarantee simulation rule in the equipment guarantee simulation rule base, adjusting the sequence of clauses in the equipment guarantee simulation rule to ensure that the sequence of the clauses in the equipment guarantee simulation rule is consistent with the sequence of the sequence numbers of the corresponding clauses;

detecting whether the equipment guarantee simulation rule base has the same equipment guarantee simulation rules or not;

if the equipment guarantee simulation rule base has the identical equipment guarantee simulation rules, determining that the equipment guarantee simulation rule base has the equivalent rules, and determining that the identical equipment guarantee simulation rules are the equivalent rules;

correspondingly, optimizing the rule with defects to obtain an optimized equipment guarantee simulation rule base, comprising:

only one equipment guarantee simulation rule is reserved for the same equipment guarantee simulation rule, and an optimized equipment guarantee simulation rule base is obtained.

And if the rule on a certain day and the other rule meet the same condition and have the same conclusion, the two rules are called equivalent rules. For example, "P (x) Lambda Q (x) → R (x)" and rule "Q (x) Lambda P (x) → R (x)" are equivalent rules. Equivalence rules affect the efficiency of the operation of the rule base and should therefore be reduced.

The reason why the equivalence rule is generated is that the order of clauses is disordered when the rule is expressed. Therefore, the clauses in the equipment safeguard simulation rule base can be extracted in sequence first, and are assigned with sequence numbers or serial numbers in sequence. Then, all rules in the library are checked, and the sequence of the clauses in the precondition and conclusion of each rule is adjusted to make the sequence of the clauses consistent with the sequence numbers of the clauses, that is, the clauses in each rule have the sequence numbers of the small clauses arranged in the front and the sequence numbers of the large clauses arranged in the back. And for the ordered rule base, if the identical equipment guarantee simulation rules exist, determining that the equipment guarantee simulation rule base has equivalent rules, wherein the identical equipment guarantee simulation rules are the equivalent rules. For equivalent rules, only one rule is retained and other identical rules are deleted. And if the identical equipment guarantee simulation rules do not exist in the equipment guarantee simulation rule base, determining that the equipment guarantee simulation rule base does not have the equivalence rules.

In one embodiment of the invention, the rules for which defects exist include looping rules;

testing the equipment guarantee simulation rules in the equipment guarantee simulation rule base according to the first preset test case set by adopting forward reasoning, and recording each reasoning path and the sequence number of each called reasoning element;

judging whether a newly called reasoning element appears in each reasoning path, if so, determining that the equipment guarantee simulation rule base has a circulation rule, stopping reasoning and identifying the reasoning path;

sending the identified inference path to an expert terminal so that the expert terminal modifies the equipment guarantee simulation rule corresponding to the identified inference path to obtain a modified equipment guarantee simulation rule;

and receiving the modified equipment guarantee simulation rule sent by the expert terminal, and replacing the modified equipment guarantee simulation rule with the equipment guarantee simulation rule before modification to obtain an optimized equipment guarantee simulation rule base.

If a group of rules in the equipment assurance simulation rule base are linked together to form a closed loop, the group of rules is called a loop rule set, and the rules are called loop rules. For example, the rule set: { X → Y, Y → Z, Z → X }, which can constitute a cyclic link X → Y → Z → X, wherein the conclusion of the previous rule is the precondition of the next rule. The rules in the rule set are a set of rotation rules.

Because a system with a loop rule can be in a dead loop in operation, the system must be optimized, and the specific optimization process is as follows:

aiming at a decision problem, designing a complete test case set, namely a first preset test case set; adopting forward reasoning, sequentially calling different test cases in a first preset test case set to test the equipment guarantee simulation rules in the equipment guarantee simulation rule base, and expressing each reasoning path as follows: x_i→X_j→X_m→ …, recording the sequence number of the reasoning element used in each step; judging whether the called reasoning elements appear on the reasoning path or not, if so, determining that a circulation rule exists, and immediately terminating reasoning; and identifying the path, sending the identified inference path to an expert terminal, so that the expert terminal modifies the equipment guarantee simulation rule corresponding to the identified inference path to obtain a modified equipment guarantee simulation rule, receiving the modified equipment guarantee simulation rule sent by the expert terminal, and replacing the modified equipment guarantee simulation rule with the equipment guarantee simulation rule before modification (namely the previously determined circulation rule) to obtain an optimized equipment guarantee simulation rule base.

And if the phenomenon that the newly called reasoning elements appear in the corresponding reasoning paths does not appear in all the reasoning paths, determining that no circulation rule exists in the rule base.

The first preset test case set can be designed for a specific decision problem, and is not limited herein.

The expert terminal is a terminal of a domain expert, and for example, can be a mobile phone, a computer and the like of the domain expert.

In one embodiment of the invention, the rules for which there is a defect include conflicting rules;

if equipment guarantee simulation rules with the same premise and different conclusions exist in the equipment guarantee simulation rule base, determining that conflict rules exist in the equipment guarantee simulation rule base;

sending equipment guarantee simulation rules with the same premise and different conclusions to an expert terminal so that the expert terminal determines a first target rule; the first target rule is a correct rule selected from equipment guarantee simulation rules with the same conclusion and different conclusions;

and receiving a first target rule sent by the expert terminal, reserving the first target rule in the equipment guarantee simulation rule base, and deleting the rule which conflicts with the first target rule to obtain the optimized equipment guarantee simulation rule base.

Wherein, if the two rules have the same premise but contradict each other, the two rules are called conflict rules. For example, the rules "X (m) → Y (m) → and" X (m) → Y (m) → are a pair of conflicting rules.

If equipment guarantee simulation rules with the same premise and different conclusions exist in the equipment guarantee simulation rule base, determining that conflict rules exist in the equipment guarantee simulation rule base; and if the equipment guarantee simulation rule base does not have equipment guarantee simulation rules with the same preconditions and different conclusions, determining that the equipment guarantee simulation rule base does not have conflict rules. In specific use, whether a rule with the same conclusion as the premise of the newly added equipment guarantee simulation rule is different from the rule of the newly added equipment guarantee simulation rule or not can be detected for each newly added equipment guarantee simulation rule, if yes, the conflict rule is sent to the expert terminal, and the rule is determined to be correct and incorrect, so that the correct rule is reserved, and the incorrect rule is deleted.

Illustratively, if a new rule "x (m) → y (m)" is added, the rule premised on x (m) in the rule base is found, and if any of these rules concludes y (m), then the two rules are sent together to the expert terminal to determine which rule to use and which rule to delete.

In one embodiment of the invention, the rules for which a defect exists include an inclusion rule;

selecting equipment guarantee simulation rules with the same conclusion from an equipment guarantee simulation rule base to obtain a rule subset;

aiming at every two rules in the rule subsets, if the precondition clause set of one rule contains the precondition clause set of the other rule, determining that the equipment guarantee simulation rule base contains the rules;

sending the two rules containing the rules to the expert terminal so that the expert terminal determines a second target rule; the second target rule is the correct rule of the two rules;

receiving a second target rule sent by the expert terminal;

if the number of the second target rules is one, reserving the second target rules in the equipment guarantee simulation rule base, and deleting the other rule of the two rules to obtain an optimized equipment guarantee simulation rule base;

if the number of the second target rules is two, the included rules of the two rules are reserved in the equipment guarantee simulation rule base, and the other rule of the two rules is deleted to obtain the optimized equipment guarantee simulation rule base.

Wherein, if two rules Rule1 and Rule2 have the same conclusion, but Rule2 has additional constraint conditions, Rule2 is called inclusion Rule of Rule1, and Rule1 is inclusion Rule of Rule 2.

Specifically, rule subsets with the same conclusion in the equipment assurance simulation rule base are identified, the rules in each rule subset are subjected to precondition detection, and if a precondition clause set of a certain rule contains a precondition clause set of another rule, it is determined that the rule base contains the rule. And sending the two rules containing the rules to an expert terminal, determining which rule is correct and which rule is wrong, reserving the correct rule, and deleting the wrong rule. If both rules are correct, the included rule is preferentially retained.

And if the phenomenon that the precondition clause set of one rule contains the precondition clause set of the other rule does not exist in all the rule subsets, determining that no containing rule exists in the rule base.

In one embodiment of the invention, the rules for which there is a defect include missing rules;

aiming at each subtask in the second preset test case set, adopting an inference machine to implement forward inference operation on rules in the equipment guarantee simulation rule base;

if the target subtask with an empty inference result exists, determining that the equipment guarantee simulation rule base has missing rules;

sending the target subtask and the corresponding equipment guarantee simulation rule to the expert terminal so that the expert terminal determines a new insertion rule according to the target subtask and the corresponding equipment guarantee simulation rule;

receiving a new insertion rule sent by the expert terminal, and inserting the new insertion rule into the equipment guarantee simulation rule base to obtain a new equipment guarantee simulation rule base;

aiming at each subtask in the second preset test case set, adopting an inference machine to implement forward inference operation on rules in the new equipment guarantee simulation rule base;

and if the target subtask still exists, skipping to the step of sending the target subtask and the corresponding equipment guarantee simulation rule to the expert terminal for cyclic execution until the target subtask does not exist.

Wherein, for a certain rule set, the object attribute may take the value M_i(referred to as legal values) which may be some value or values, and if not contained by the premise of any rule, the rule set is said to contain missing rules, i.e., no rule can be found to satisfy M_i。

If there are missing rules in the rule base, this will have a large impact on the system, and attributes that are only partially covered may prevent the system from reaching a certain conclusion, or the system will be in error when an uncovered attribute is encountered at runtime. Therefore, optimization of the missing rule must be performed, which includes the following steps:

aiming at each subtask in the second preset test case set, the inference machine implements forward inference operation by using rules in the optimization rule base; if a certain inference result is null, indicating that the equipment guarantee simulation rule base has missing rules and needing to identify the problems; and sending the subtasks (target subtasks) with problems and the corresponding rules thereof to the expert terminal so that the expert terminal determines new insertion rules according to the target subtasks and the corresponding equipment guarantee simulation rules. And inserting the new insertion rule into the equipment guarantee simulation rule base to obtain a new equipment guarantee simulation rule base, and continuing to adopt the second preset test case set to test the new equipment guarantee simulation rule base until target subtasks do not exist, namely all subtasks can be solved.

And if the inference result is not empty for all subtasks in the second preset test case set, determining that no missing rule exists in the equipment guarantee simulation rule base.

The second preset test case set may be designed according to actual requirements, and is not limited herein.

The embodiment of the invention can lead the rule base to be continuously updated and perfected by carrying out defect inspection and optimization treatment on the equipment guarantee simulation rule base, ensure the correctness and feasibility of the rule base, improve the operation efficiency of the rule base and better support the verification of the concept model.

In one embodiment of the invention, the equipment assurance simulation rules include rules inside the model, rules inside the views, rules between the views, and synthesis rules;

the rules in the model comprise the dependency relationship among tasks in the task model, the priority relationship among behaviors in the behavior model, the dependency relationship among functions in the function model, the priority/dependency relationship among information in the information model, the inheritance relationship among entities in the entity model, the membership relationship among nodes in the organization model and the inheritance transfer relationship of similar concepts in the same model;

the rules within the view include precedence/dependency relationships between homogeneous models, decomposition relationships between homogeneous models, and completion relationships between heterogeneous models.

Specifically, in the framework of SWRL, the restrictive formula of condition judgment is established in Atom, the real rule is established in Imp, the restrictive sources of both head and body contained in Imp are provided by Atom, and these restrictive formulas can be reused by different rules. Two limiting formulas are mainly used in the equipment guarantee simulation rule: c (x) and P (x, y) respectively correspond to a meta-concept and a meta-relationship in the ontology, wherein the meta-relationship includes relationships of triggering, membership, …, calling, … and the like in addition to Association (Association), Aggregation (Aggregation), Generalization (Generalization) and Dependency (Dependency) in the UML, and the specific description is shown in table 1.

TABLE 1 Atom Table based on SWRL Equipment Provisioning simulation rules

According to the view composition characteristics of the equipment guarantee simulation conceptual model architecture, equipment guarantee simulation rules are divided into four types: rules within the model, rules within the views, rules between the views, and composite rules.

The rules inside the model refer to rules defined by determining relationships between elements inside the model in order to reduce errors existing in the equipment assurance simulation conceptual model. The rules inside the model are mainly expressed as relationships among the elements of the same type, and the relationships comprise: precedence, aggregation, association, inheritance, membership, dependency, etc.

Rule 1.1: dependencies between tasks in the task model. For example, the maneuver and repair tasks belong to the same task model, but during the operation of the system, the latter depends on the former, and its SWRL is expressed as follows:

MoveTask(？x)∧RepairTask(？y)→Dependency(？y,？x)

rule 1.2: the precedence relationship between behaviors in the behavior model. For example, maneuver and repair actions belong to the same behavior model, but during system operation, the former takes precedence over the latter, and its SWRL is expressed as follows:

Move(？x)∧Repair(？y)→Prior-To(？x,？y)

rule 1.3: dependencies between functions in the functional model. For example, equipment supply functions and transport functions belong to the same functional model, but during system operation, the former depends on the latter, and its SWRL is expressed as follows:

EquipSupplyFunction(？x)∧TransportFunction(？y)→Dependency(？x,？y)

rule 1.4: precedence/dependencies between information in the information model. For example, in a certain equipment safeguard activity, an equipment safeguard squad reports the damage condition of the equipment to a command post, and the equipment safeguard squad reports the repair completion of the equipment to the command post, and the SWRL of the equipment safeguard squad is represented as follows:

DamReport(？x)∧FinishReport(？y)→Prior-To(？x,？y)

rule 1.5: inheritance relationships between entities in an entity model. For example, a tank and a 99A tank both belong to the entity model, and the 99A tank inherits to the tank entity, and SWRL thereof is expressed as follows:

Tank(？x)∧TankA(？y)→SubClassOf(？y,？x)

rule 1.6: and organizing membership between nodes in the model. For example, the repair team and the general repair group are two nodes in an organization model, and there is a membership relationship between them, that is, the general repair group is subordinate to the repair team, and its SWRL is expressed as follows:

Universal_Repair_Group(？x)∧RepairUnit(？y)→Belong-To(？x,？y)

rule 1.7: in the same model, the same concept inherits the transfer relationship. For example, transitivity between entity concepts, SWRL, is expressed as follows:

SubClassOf(？x,？y)∧SubClassOf(？y,？z)→SubClassOf(？x,？z)

the rule inside the view refers to a rule defined for reducing grammatical and semantic errors existing inside the same view in an equipment assurance simulation conceptual model architecture. The method mainly comprises two rules, namely rules between similar models and rules between heterogeneous models. For example, the action models and the task models are contained in the running view, rules among the task models and between the action models belong to the same-class rules, and rules between the action models and the task models are heterogeneous rules.

Rule 2.1: there is a precedence/dependency relationship between homogeneous models. For example, the maneuver model and the repair model are behavior models in the equipment first-aid repair process, and in the system operation process, the maneuver model is firstly operated, then the repair model is operated, namely the maneuver model is prior to the repair model, and if the sequence is opposite, the priority/dependency relationship between the models is violated. Its SWRL is represented as follows:

MoveModel(？x)∧RepairModel(？y)→Prior-To(？x,？y)

MoveModel(？x)∧RepairModel(？y)→Dependency(？y,？x)

rule 2.2: the same kind of models have a decomposition relation. For example, the emergency repair task can be decomposed into tasks such as maneuvering, expanding, repairing, withdrawing and the like, the emergency repair task model and other task models are in a decomposition relationship, and the SWRL is expressed as follows:

RepairTask(？x)∧MoveTask(？y)→Part-Of(？x,？y)

RepairTask(？x)∧SpreadTask(？y)→Part-Of(？x,？y)

RepairTask(？x)∧MendTask(？y)→Part-Of(？x,？y)

RepairTask(？x)∧WithdrawTask(？y)→Part-Of(？x,？y)

rule 2.3: the heterogeneous models have a completion relationship, for example, the maneuver behavior model and the maneuver task model have a completion relationship, that is, the maneuver behavior is mainly established for completing the maneuver task, and SWRL thereof is expressed as follows:

MoveBehavior(？x)∧MoveTask(？y)→Finish(？x,？y)

the rule between the views refers to that in an equipment support simulation conceptual model architecture, consistency problems such as omission, redundancy, logic errors and the like may exist in description of the same object due to overlapping of contents between different views, and corresponding rules must be defined to reduce the occurrence of the consistency problems. The rules between views are mainly embodied as rules between models contained in the views.

Illustratively, such rules are illustrated by taking the relationship between the run view and the functional view as an example. Because the running view comprises the task model and the behavior model, the rule between the running view and the function view is embodied as a rule problem between the task model and the behavior model and the function model. The concrete expression is as follows:

rule 3.1: the function may decide what action to perform. Taking the maneuver behavior and maneuver function as examples, the latter determines the former. The SWRL rule is expressed as follows:

MoveBehavior(？x)∧MoveFunction(？y)→Decide(？y,？x)

rule 3.2: in the case of explicit behavior, the functionality required to implement the behavior can be inferred. Also taking maneuver behavior and maneuver function as examples, there is a desired relationship between the two. The SWRL rule is expressed as follows:

MoveBehavior(？x)∧MoveFunction(？y)→Need(？x,？y)

rule 3.3: the function may decide what task to perform. Taking the repair function and the repair task as an example, the former determines the latter. The SWRL rule is expressed as follows:

RepairTask(？x)∧RepairFunction(？y)→Decide(？y,？x)

the comprehensive rule refers to that the relationship between the views and the relationship inside the views or inside the model exist in the premise of the rule. For example: c1 and C2 are two functions, B1 and B2 are two actions, C1 depends on C2, while C1 decides B1 and C2 decides B2, then it can be concluded that C2 takes precedence over C1, and its SWRL represents as follows:

Dependency(C1,C2)∧Decide(C1,B1)∧Decide(C2,B2)→Prior-To(C2,C1)

compared with other rules, the comprehensive rule is more complex than other types of rules and is easier to meet in the actual system operation, so that the comprehensive rule meeting the requirements can be established according to the actual requirements of the system.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

Corresponding to the equipment security simulation rule construction method, an embodiment of the invention also provides an equipment security simulation rule construction device, which has the same beneficial effects as the equipment security simulation rule construction method. Fig. 4 is a schematic block diagram of an equipment assurance simulation rule building apparatus according to an embodiment of the present invention, and for convenience of description, only parts related to the embodiment of the present invention are shown.

In the embodiment of the present invention, the equipment safeguard simulation rule construction device 30 may include an obtaining module 301, a detecting module 302, and an optimizing module 303.

The obtaining module 301 is configured to obtain an equipment security simulation rule, and store the equipment security simulation rule in an equipment security simulation rule base;

a detection module 302, configured to detect whether there is a defective rule in the equipment assurance simulation rule base;

the optimizing module 303 is configured to, if it is detected that the equipment insurance simulation rule base has a rule with a defect, optimize the rule with the defect to obtain an optimized equipment insurance simulation rule base.

the detection module 302 may also be configured to:

the optimization module 303 may also be configured to:

the detection module 302 may also be configured to:

the optimization module 303 may also be configured to:

the detection module 302 may also be configured to:

the optimization module 303 may also be configured to:

the detection module 302 may also be configured to:

the optimization module 303 may also be configured to:

receiving a second target rule sent by the expert terminal;

the detection module 302 may also be configured to:

the optimization module 303 may also be configured to:

In one embodiment of the invention, the equipment assurance simulation rules are described using SWRL.

It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional units and modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional units and modules as needed, that is, the internal structure of the equipment support simulation rule building apparatus is divided into different functional units or modules to perform all or part of the above described functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the above-mentioned apparatus may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

Fig. 5 is a schematic block diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 5, the terminal device 40 of this embodiment includes: one or more processors 401, a memory 402, and a computer program 403 stored in the memory 402 and executable on the processors 401. The processor 401, when executing the computer program 403, implements the steps in the above-described embodiments of the equipment assurance simulation rule construction method, such as the steps S101 to S103 shown in fig. 1. Alternatively, the processor 401, when executing the computer program 403, implements the functions of the modules/units in the above-mentioned embodiment of the equipment assurance simulation rule building device, such as the functions of the modules 301 to 303 shown in fig. 4.

Illustratively, the computer program 403 may be partitioned into one or more modules/units that are stored in the memory 402 and executed by the processor 401 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used for describing the execution process of the computer program 403 in the terminal device 40. For example, the computer program 403 may be divided into an acquisition module, a detection module and an optimization module, and each module has the following specific functions:

the acquisition module is used for acquiring the equipment guarantee simulation rule and storing the equipment guarantee simulation rule into the equipment guarantee simulation rule base;

the detection module is used for detecting whether the equipment guarantee simulation rule base has a rule with a defect;

and the optimization module is used for optimizing the rule with the defect to obtain an optimized equipment guarantee simulation rule base if the rule with the defect is detected in the equipment guarantee simulation rule base.

Other modules or units can refer to the description of the embodiment shown in fig. 4, and are not described again here.

The terminal device 40 may be a computing device such as a desktop computer, a notebook, a palm computer, and a cloud server. The terminal device 40 includes, but is not limited to, a processor 401 and a memory 402. Those skilled in the art will appreciate that fig. 5 is only one example of a terminal device 40, and does not constitute a limitation to the terminal device 40, and may include more or less components than those shown, or combine some components, or different components, for example, the terminal device 40 may further include an input device, an output device, a network access device, a bus, etc.

The Processor 401 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 402 may be an internal storage unit of the terminal device 40, such as a hard disk or a memory of the terminal device 40. The memory 402 may also be an external storage device of the terminal device 40, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 40. Further, the memory 402 may also include both an internal storage unit of the terminal device 40 and an external storage device. The memory 402 is used for storing the computer program 403 and other programs and data required by the terminal device 40. The memory 402 may also be used to temporarily store data that has been output or is to be output.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed equipment assurance simulation rule construction device and method may be implemented in other ways. For example, the above-described embodiment of the equipment assurance simulation rule building device is only illustrative, for example, the division of the module or unit is only one logic function division, and there may be other division manners in actual implementation, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media which may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A method for constructing an equipment security simulation rule is characterized by comprising the following steps:

detecting whether a rule with a defect exists in the equipment guarantee simulation rule base;

2. The equipment assurance simulation rule building method of claim 1, wherein the flawed rule comprises an equivalence rule;

the detecting whether the equipment protection simulation rule base has a rule with a defect comprises the following steps:

if the equipment guarantee simulation rule base has the identical equipment guarantee simulation rules, determining that the equipment guarantee simulation rule base has equivalent rules, and determining that the identical equipment guarantee simulation rules are equivalent rules;

correspondingly, the optimizing the rule with the defect to obtain the optimized equipment guarantee simulation rule base comprises:

and only one identical equipment guarantee simulation rule is reserved to obtain an optimized equipment guarantee simulation rule base.

3. The equipment safeguarding simulation rule construction method of claim 1, wherein the defective rule comprises a loop rule;

testing the equipment guarantee simulation rules in the equipment guarantee simulation rule base according to a first preset test case set by adopting forward reasoning, and recording each reasoning path and the sequence number of each called reasoning element;

4. The equipment safeguarding simulation rule construction method of claim 1, wherein the flawed rule comprises a conflict rule;

sending the equipment guarantee simulation rules with the same premise and different conclusions to an expert terminal so that the expert terminal determines a first target rule; the first target rule is a correct rule selected from equipment guarantee simulation rules with the same premise and different conclusions;

and receiving the first target rule sent by the expert terminal, reserving the first target rule in the equipment guarantee simulation rule base, and deleting the rule which conflicts with the first target rule to obtain the optimized equipment guarantee simulation rule base.

5. The equipment safeguarding simulation rule construction method of claim 1, wherein the defective rule comprises an inclusion rule;

selecting equipment guarantee simulation rules with the same conclusion from the equipment guarantee simulation rule base to obtain a rule subset;

for every two rules in the rule subset, if the precondition clause set of one rule contains the precondition clause set of the other rule, determining that the equipment protection simulation rule base contains the rule;

receiving the second target rule sent by the expert terminal;

if the number of the second target rules is two, the included rule of the two rules is reserved in the equipment guarantee simulation rule base, and the other rule of the two rules is deleted to obtain the optimized equipment guarantee simulation rule base.

6. The equipment safeguarding simulation rule construction method of claim 1, wherein the defective rule comprises a missing rule;

aiming at each subtask in the second preset test case set, adopting an inference machine to implement forward inference operation on the rules in the equipment guarantee simulation rule base;

if the target subtask with an empty inference result exists, determining that the equipment guarantee simulation rule base has a missing rule;

sending the target subtask and the corresponding equipment guarantee simulation rule to an expert terminal so that the expert terminal determines a new insertion rule according to the target subtask and the corresponding equipment guarantee simulation rule;

receiving the new insertion rule sent by the expert terminal, and inserting the new insertion rule into the equipment guarantee simulation rule base to obtain a new equipment guarantee simulation rule base;

aiming at each subtask in the second preset test case set, adopting an inference machine to implement forward inference operation on the rules in the new equipment guarantee simulation rule base;

7. The equipment security simulation rule construction method according to any one of claims 1 to 6, wherein the equipment security simulation rule is described using SWRL.

8. The equipment assurance simulation rule construction method according to any one of claims 1 to 6, wherein the equipment assurance simulation rule includes a rule inside a model, a rule inside a view, a rule between views, and a comprehensive rule;

the rules inside the view include precedence/dependency relationships between homogeneous models, decomposition relationships between homogeneous models, and completion relationships between heterogeneous models.

9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the equipment assurance simulation rule construction method according to any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by one or more processors, implements the steps of the equipment assurance simulation rule construction method according to any one of claims 1 to 8.