Task meta-model construction method, database and device for general operational process

Abstract

The application discloses a task meta-model construction method for general combat process, comprising the following steps: S1, constructing a combat concept model by using combat scene logical entities, data and models; S2, constructing a capability concept model; S3, constructing a mission task-capability matrix model; S4, constructing a combat activity resolution tree and a combat activity model; S5, constructing a mapping matrix model of capabilities and combat activities; and S6, integrating the combat concept model, the capability concept model, the mission task-capability matrix model, the combat activity model and the mapping matrix model established in steps S1-S5 to generate a global digital dictionary, i.e., obtaining a task meta-model. The application further discloses a task meta-model database and a construction device. The application can solve the problems that the existing combat system is difficult to model and describe, the combat task model construction efficiency is low, and the combat task model is difficult to verify and reuse, and realizes the rapid combination, verification and reuse of the combat task model architecture.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of system engineering, and particularly relates to a task meta-model construction method for general operational processes, a database and an apparatus. BACKGROUND

[0002] In recent years, with the rapid development of technology, a relatively complete operational system has been formed in modern war, showing the characteristics of system confrontation. The operational system architecture and composition form for operational requirements are constantly changing and evolving. How to reasonably apply system capabilities and research operational system capability construction according to operational development requirements has become a research focus at home and abroad.

[0003] As a complex giant system, the operational system is an organic combination of various operational component systems. The elements constituting the system affect the realization of the overall capability of the system in terms of scale, technical level, composition, etc. The traditional demand analysis method and description means are difficult to handle the complex requirements of the system, and it is also difficult to accurately describe the system using abstract mathematical models. Moreover, the traditional DC (Document Centric) system method has defects such as ambiguity, inability to verify, and difficulty in reuse. Operational system architecture requirement modeling can perform hierarchical decomposition and analysis of operational system capability requirements from top to bottom and obtain operational capabilities from bottom to top. At present, the operational system architecture requirement modeling is mostly based on the related ideas of the American DoDAF to establish system requirement views and use the multi-view method to describe the system requirements. However, there are still challenges:

[0004] 1. Different description specifications result in completely different underlying storage formats of the corresponding model data, making it difficult to realize the exchange and common use of the built models.

[0005] 2. There is a lack of correlation between the specific data of different view models, making it difficult to support the requirements verification such as the executability evaluation and consistency check of system modeling.

[0006] The concept of meta-model originated from the field of software engineering. It is a higher level of abstraction than model, which defines the mutual relationship and semantics between model elements. Its core idea is to customize the modeling language of a specific field according to requirements and generate the modeling language tool of the field. At present, many fields have established the modeling language of the corresponding field through meta-modeling technology. However, the military field, especially the operational task, still lacks the corresponding modeling language. Therefore, it is necessary to design a task meta-model construction method for general operational processes to construct a task meta-model for general operational processes serving the operational system requirements, and use the language to model the operational task in a standardized and unified manner, so as to solve the above technical problems. SUMMARY

[0007] The application aims to provide a task meta-model construction method for general combat process, aiming to solve the technical problems of low construction efficiency, difficulty in verification and reuse of the existing combat system task model.

[0008] The first object of the application is to provide a task meta-model construction method for general combat process, comprising the following steps:

[0009] S1, constructing a combat concept model by using combat scene logical entities, data and models;

[0010] S2, constructing a capability concept model;

[0011] S3, constructing a mission task-capability matrix model;

[0012] S4, constructing a combat activity decomposition tree and a combat activity model;

[0013] S5, constructing a mapping matrix model of capabilities and combat activities, establishing the mapping relationship between combat capabilities and combat activities, and forming a capability requirement directory through the mapping from tasks to capabilities;

[0014] S6, integrating the combat concept model, the capability concept model, the mission task-capability matrix model, the combat activity model and the mapping matrix model established in steps S1-S5 respectively to generate a global digital dictionary, i.e., to obtain the task meta-model.

[0015] Preferably, the specific steps of step S1 are: establishing the association relationship between system elements, converting the description and solution of combat problems into combat capability requirements according to combat concept requirements, forming the overall architecture of the combat system, obtaining the mission task decomposition, describing the task composition and hierarchical relationship, describing the air combat scenario scheme from the task execution level in a high-level graph, establishing the information data interaction relationship between each combat unit of the air combat system and each unit, and obtaining the combat concept model.

[0016] Preferably, the specific steps of step S2 are: converting the combat capability requirements into a visual view of all capabilities required by the system architecture in each stage of the combat life cycle, and refining and decomposing the system capabilities, planning the capability hierarchy and dependency relationship, and obtaining the capability concept model; the specific steps of step S3 are: planning the combat mission task stage according to the combat concept, analyzing the combat capabilities according to the combat concept, obtaining the stage capability requirements, forming the capability requirement directory, establishing a two-dimensional mapping matrix, strengthening the association relationship between different combat tasks and capabilities, verifying the attribution of the proposed combat capabilities, clarifying the amount of each combat capability requirement and the number of each combat capability requirement in each stage in the combat life cycle, and obtaining the task-capability matrix model.

[0017] Preferably, the specific steps of step S4 are: constructing a combat activity decomposition tree, forming the hierarchical relationship and input-output relationship between activities, forming a phased combat activity model, establishing control flow and data flow between combat units, expressing combat business logic, constructing combat resource flow description and combat resource interaction matrix, organizing combat node information and resource interaction, constructing combat rule model and combat state transition description model, and determining the business rules for combat nodes to complete the combat mission and combat activities, defining the timing characteristics of key combat events of combat nodes and the change relationship of combat activities, and obtaining the combat activity model.

[0018] Preferably, the specific steps of step S5 are: planning combat activities according to mission tasks to form a two-dimensional mapping matrix with combat activities as column elements and combat capabilities as row elements, and obtaining a mapping matrix model; and the specific steps of step S6 are: referring to the general terms and formal semantics of DM2 in combination with the characteristics of the air combat system field, organizing the data element requirements of the integrated model, extracting necessary data element requirements in the architecture description to form the logical types of core concepts, concept relationships and attributes, and obtaining a high-level data structure, i.e., generating a global digital dictionary.

[0019] The second object of the present application is to provide a task meta-model database for a general combat process, which is constructed by extracting characteristic core data in the established task meta-model.

[0020] Preferably, the characteristic core data includes mission tasks, combat events, combat activities, combat interfaces, personnel types, and combat unit states.

[0021] The third object of the present application is to provide a task meta-model construction device for a general combat process, which comprises:

[0022] A model design basic environment module for providing a visual modeling environment, supporting users to manage models in an engineering manner, and creating various entities, data, and models required for combat scene logical analysis by using a visual drawing panel;

[0023] A model architecture design module for supporting users to selectively construct views in accordance with standard modeling frameworks and modeling languages, achieving the ability of data interconnection and intercommunication between different system models, reaching system modeling and simulation processes at various levels and granularities, and realizing meta-model data reference of the meta-model library through data reference to quickly construct required models;

[0024] A model simulation verification module for providing a visual model deduction environment, supporting users to observe the dynamic deduction process of the model, controlling the simulation process, and verifying the logical self-consistency of the constructed model through event relationship triggering;

[0025] A requirement development management module is used for generating itemized requirement texts from a model according to model data and certain rules, supporting user development of system development requirements, managing system development requirements, mission task requirements and subsystem requirements, and analyzing user behaviors of receiving upper-layer requirements and developing lower-layer requirements;

[0026] A meta-model management module is used for comprehensively managing task meta-model data, and providing a data reference interface for calling the meta-model by a modeling environment.

[0027] Preferably, the standard modeling framework is the Department of Defense Architecture Framework (DoDAF) 2.0, and the standard modeling language is UPDM.

[0028] Preferably, the task meta-model data adopts an XML file format, the data exchange specification of the meta-model includes a group of XSD files, and the data conversion adopts an international general data conversion standard XMI and an XML-based conversion mode.

[0029] Compared with the prior art, the present application has the following beneficial effects:

[0030] (1) The task meta-model for the general combat process provided by the present application is adaptable to the characteristics of rapid change of a battlefield situation, is oriented to dynamic change of a task, plans combat capability as a whole, adjusts a combat process, and determines a matching relationship between combat activities and capability.

[0031] (2) The task meta-model library established by the present application selects task elements such as combat events, activities and interfaces related to a task through data reference, can quickly construct a task model under the guidance of combat concepts, and realizes rapid integration of a combat architecture.

[0032] (3) The task meta-model construction device established by the present application can realize effective accumulation of architecture data, help iteratively form data resources for optimized demonstration, and is beneficial to sharing and reuse of architecture data resources. BRIEF DESCRIPTION OF DRAWINGS

[0033] Figure 1 A design principle diagram of the task meta-model for the general combat process provided by the embodiment of the present application;

[0034] Figure 2 A block diagram of the high-layer data structure in the embodiment of the present application;

[0035] Figure 3 A structure diagram of the task meta-model construction device for the general combat process provided by the embodiment of the present application;

[0036] Figure 4 A picture when the unmanned high-altitude reconnaissance machine discovers a target in the embodiment of the present application;

[0037] Figure 5 Picture for the unmanned aerial vehicle in the embodiment of the application to cooperatively detect a target;

[0038] Figure 6 Picture for the unmanned aerial vehicle in the embodiment of the application to implement electronic jamming on an enemy radar;

[0039] Figure 7 Picture for the cooperative guidance fire attack in the embodiment of the application;

[0040] Figure 8 Picture for a high-level operational concept. DETAILED DESCRIPTION

[0041] Exemplary embodiments of the present disclosure will be described below in greater detail with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be accurately conveyed to those skilled in the art.

[0042] A mission meta-model is a model that depicts a mission task domain modeling language, provides a standard language with certain logical rules in the architecture design process of a military operational system, is a high-level abstraction of a task model, and can effectively accumulate and help iteratively optimize data resources of argumentation through a task meta-model design method for a general operational process, thereby forming an authoritative task resource library. Figure 1 As shown in the drawing, the main design idea of the task meta-model for a general operational process provided in the embodiment of the application is as follows:

[0043] 1. Architecture design, based on the MOF standard of OMG, the combat task scenario is instantiated and described, the kill chain confrontation mode of the opposing sides is converted into a visual description following the DoDAF2.0 framework for combat architecture modeling, the combat system architecture requirement description is captured under the support of SWT based on the time sequence diagram, activity diagram, state diagram, etc., the combat system task execution process and task style are analyzed and abstracted, the architecture model is designed, including the defined system components, capability structure, interface relationship, the operational concept model, capability view model and task view model are run, and the DMA structure framework is obtained.

[0044] 2. Architecture logic verification, based on the system operation control model, the interaction rules between the member systems of the system during operation are verified, the consistency and integrity of the logic function of the architecture are detected, the system components, capability structure, interface relationship are verified and optimized, and the executable evaluation of the system modeling and other requirement verification are performed.

[0045] 3. Task meta-model generation, task key features and description based on view model and standard relationship "5W1H", extract task core data elements, including mission task, combat event, combat activity, combat interface, personnel type, combat unit state transition.

[0046] The task meta-model construction provided by the embodiment of the application starts from typical combat tasks, constructs a typical task scene according to a combat scenario, completes the argumentation of the system function architecture, and by constructing elements such as a combat concept model, a capability view model and a task view model, the architecture data of an abstract system is summarized into a plurality of mutually related, visualized and easily managed view models, which have a complete data basis for generating the task meta-model.

[0047] S1. Through a visual modeling environment supported by the platform, a combat concept model is constructed by using combat scene logical entities, data and models; the description of the combat problem includes forming a target line through comprehensive combat elements such as a combat time and a combat area, a combat target, a threat object and a battlefield environment, that is, forming a task completion standard according to an expected attack effect of the target; the solution to the combat problem is a scheme implementation of an ordered set of a series of mutually related combat activities for jointly achieving a certain combat target by different equipment to realize an expected attack effect, and the combat capability requirement is the necessary basis for executing the combat activities, therefore, according to a specific combat problem, a combat capability requirement can be formed, such as a long-range missile launching, target tracking and other activities for attacking an enemy target beyond the horizon, that is, a long-range attack capability and a target sensing capability, according to different capabilities, mapping to different types of equipment, such as a warning capability mapping to a warning UAV and an attack capability mapping to an attack UAV. Different types of equipment form a combat system overall architecture, obtain a description of a mission task decomposition, describe a task composition and a hierarchical relationship, and from a task execution level, describe an air combat scenario scheme in a high-level graph, establish an information data interaction relationship between each combat unit of the air combat system and each unit.

[0048] S2. Through a visual modeling environment supported by the platform, a capability concept model is constructed; the strategic background and high-level range of the system combat capability are described, the combat capability requirement is converted into a visual view of all capabilities required by the system architecture in each stage of the combat life cycle, and the system capability is refined and decomposed, and the capability level and dependency relationship is planned. For example, under the BVR air combat concept analysis, the system architecture life cycle is divided into seven system development stages, including ground preparation, take-off formation, guidance flight, penetration into airspace, detection and identification, beyond-horizon attack and return, the capability requirements of each stage are summarized, eight first-level capabilities, including task planning, command and control, communication, target sensing, fire attack, defense, support and maneuver, are obtained, and the attribution relationship between the stages and the capabilities is established.

[0049] S3, build the mission task-capability matrix model through the visual modeling environment supported by the platform; establish the mapping relationship between the mission task and the combat capability. Plan the combat mission task stage according to the combat concept, such as dividing the BVR air combat into ground preparation, formation flight, detection guidance, penetration attack and other stages, analyzing the combat capability according to the combat concept, obtaining the stage capability requirement, forming the capability requirement directory such as electronic countermeasures, tactical avoidance, flight management and other capabilities, taking the mission task as the column element and the combat capability as the row element to establish a two-dimensional mapping matrix, strengthening the correlation between different combat tasks and capabilities under the concept decomposition of BVR air combat, verifying the attribution of the proposed combat capability, and clearly defining the amount of each combat capability required by each combat activity and the number of each combat capability required in each stage.

[0050] S4, build the combat activity decomposition tree and the combat activity model through the visual modeling environment supported by the platform; build the combat activity decomposition tree, such as implementing the BVR attack activity, which needs to perform target search, target identification, threat assessment, weapon preparation, maneuver, attack solution, missile launch and other activities, implementing target identification, which needs to perform infrared identification, passive detection, number analysis and other activities, forming the hierarchical relationship between activities, i.e. activity decomposition, the output of the previous activity, such as "target information" as the output of "search target", the input of "target identification", the output of "identification information", and the input of "threat assessment", and so on, forming the input-output relationship, forming the stage combat activity model, establishing the control flow and data flow between combat units, expressing the combat business logic, building the combat resource flow description and the combat resource interaction matrix, organizing the combat node information, resource interaction, building the combat rule model and the combat state transition description model, as well as the combat event tracking description, determining the business rules that constrain the combat nodes to complete the combat mission and the combat activities, defining the time sequence characteristics of the key combat events of the combat nodes and the change process of the combat activities, generating the sequence of each combat unit in response to external triggers according to the causal relationship over time by tracking the event interaction between combat units, and checking the rationality and realizability of the combat scheme.

[0051] S5, build the mapping matrix model of capability and combat activity, establish the mapping relationship between combat capability and combat activity, form the capability requirement directory through the mapping from task to capability; plan the combat activity composition according to the mission task, such as dividing the penetration attack task into weapon preparation, multi-target tracking, target aiming, attack solution, target locking, missile launch, cooperative guidance and other activities, taking the combat activity as the column element and the combat capability as the row element to establish a two-dimensional mapping matrix, strengthening the correlation between different combat activities and combat capabilities under the penetration attack task, verifying the support of combat capability to combat activity, and clearly defining the amount of each combat capability required by each combat activity and the number of each combat capability required in each combat activity.

[0052] S6, the combat concept model, the capability model, the mission-capability matrix model, the combat activity model and the mapping matrix model established in steps S1-S5 are integrated respectively to generate a global digital dictionary, that is, a mission meta-model is obtained;Specifically, referring to the general terms and formal semantics of DM2 in combination with the characteristics of the air combat system field, the data element requirements of the integrated model are organized, the necessary data element requirements in the system structure description are extracted to form the logical types of core concepts, concept relationships and attributes, and a high-level data structure is obtained, such as Figure 2 As shown in the figure, the core concepts should include "combat activity", "metric", "organization", "system", "individual", "combat resource", etc., and the defined relationships include: "expected effect guiding combat activity", "combat activity executed by executor", "metric of combat activity executed by executor", "combat activity changing combat resource", "metric of combat activity changing combat resource", etc., that is, a global digital dictionary is generated, and a mission meta-model is obtained.

[0053] The embodiment of the application also provides a mission meta-model database for a general combat process, which is constructed by extracting the feature core data in the established mission meta-model. Specifically, the bottom layer data (target, capability, activity, executor, service, resource flow, information and data, project, training / skill, rule, metric and location) in the established mission meta-model is classified according to the standard relationship "5W1H", that is, WHO (executor), WHERE (specific location), WHEN (specific time), WHY (purpose), WHAT (resource or event) and HOW (action), which is summarized as: the executor (WHO) takes certain action (HOW) in a certain location (WHERE) and at a certain time (WHEN) to achieve a certain purpose (WHY), which produces resources or events (WHAT), and then the mission core data elements are extracted around the standard relationship "5W1H", including mission, combat event, combat activity, combat interface, personnel type and combat unit state conversion, to obtain a mission meta-model database.

[0054] As shown in the figure, the core concepts should include "combat activity", "metric", "organization", "system", "individual", "combat resource", etc., and the defined relationships include: "expected effect guiding combat activity", "combat activity executed by executor", "combat activity executed by executor", "metric of combat activity executed by executor", "combat activity changing combat resource", "metric of combat activity changing combat resource", etc., that is, a global digital dictionary is generated, and a mission meta-model is obtained. Figure 3 As shown in the figure, the core concepts should include "combat activity", "metric", "organization", "system", "individual", "combat resource", etc., and the defined relationships include: "expected effect guiding combat activity", "combat activity executed by executor", "combat activity executed by executor", "metric of combat activity executed by executor", "combat activity changing combat resource", "metric of combat activity changing combat resource", etc., that is, a global digital dictionary is generated, and a mission meta-model is obtained.

[0055] The model design basic environment module is used to provide a visual modeling environment, support users to manage the model in an engineering manner, create various entities, data and models required for logical analysis of combat scenes by using a visual drawing panel, and quickly complete the construction of view models at various levels by means of dragging, wiring and automatic layout.

[0056] A model architecture design module is configured to support a user to selectively build a view according to a standard modeling framework and a modeling language, realize the data interconnection and intercommunication capability between different system models, achieve the system modeling and simulation process of various levels and granularities, and realize the meta-model data reference of the meta-model library through data reference to quickly build a required model.

[0057] A model simulation verification module is configured to provide a visual model deduction environment, support a user to observe the dynamic deduction process of a model, control the simulation process, and verify the logic self-consistency of the built model through event relationship triggering.

[0058] A requirement development management module is configured to generate itemized requirement texts from model data according to certain rules, support a user to develop a system development requirement, manage a system development requirement, a mission task requirement and a subsystem requirement, and analyze the behavior of the user to receive an upper-layer requirement and develop a lower-layer requirement.

[0059] A meta-model management module is configured to comprehensively manage task meta-model data, and provide a data reference interface for a modeling environment to call the meta-model.

[0060] The standard modeling framework is a Department of Defense Architecture Framework (DoDAF) 2.0, and the standard modeling language is UPDM.

[0061] The task meta-model data adopts an XML file format, the data exchange specification of the meta-model includes a group of XSD files, and the data conversion adopts an international general data conversion standard XMI and an XML-based conversion mode.

[0062] Manned / unmanned aerial vehicle (MAV / UAV) cooperative combat is a new combat concept of a formation system composed of manned aircraft and unmanned aerial vehicles in deep cooperation in aspects of reconnaissance and detection, command and control, and fire attack, and has characteristics of distributed attack, dynamic adaptability, and decision advantage of a killing chain, and is a development direction of future air combat. Due to the complexity of the MAV / UAV cooperative air combat system, a combat scenario must be taken as an input, STK is used to model and analyze from a time-space domain, a top-level design is performed on the entire combat system under a combat concept, the task meta-model based on the architecture design of an embodiment of the present application is used to model the architecture on a task meta-model construction device to obtain an architecture view product of the MAV / UAV cooperative air combat system, and different expression types and the most important architecture view products are selected for description.

[0063] I. Overview and abstract information view product

[0064] The embodiment of the application refines the core content of the MAV / UAV cooperative air combat concept from the author, version, combat area, battlefield environment, combat time, threat target, combat background, background link and mission task based on the overview and abstract information product developed on the construction device of the task meta-model of the architecture design task meta-model, and the specific content of the concept is as follows:

[0065] On March 2, 2023, Y country dispatched a reconnaissance team, 4 tanks, and entered the southern region of our country under the cover of two fighter jets. The enemy travels along the mountains at an average altitude of 5 kilometers, trying to attack our border warning facilities. Due to the mountain depth, our microwave radar detection is intermittent, and can only provide approximate information such as the direction and trend of the enemy target. The ground command center issues combat tasks to our aircraft (MAV / UAV) according to intelligence information and battlefield situation, and the mixed formation takes off after grouping in the designated area, and the ground control station transfers the UAV formation control right to the manned aircraft; the unmanned high-altitude reconnaissance aircraft discovers that the enemy formation has entered our control area in front, as shown in Figure 4 , the command center orders the mixed formation to intercept in front, the manned aircraft re-plans the combat scheme, leads the UAV formation to change the current flight path to the combat area, searches for targets using detection equipment, as shown in Figure 5 , and conducts comprehensive identification. Our side encounters the threat of being "intercepted" by the enemy radar, and the UAV starts the electronic countermeasure equipment to deceive the enemy radar, as shown in Figure 6 , suppresses the detection distance of the enemy radar, and continues to advance; under the guidance of the manned aircraft, the UAV formation launches weapons to the enemy helicopter, and cooperates with the guidance to complete the firepower attack, as shown in Figure 7 , the MAV completes the elimination of the enemy ground armed forces with the cooperation of the UAV; after completing the combat task, the mixed formation keeps radio silence, and returns to the ground command center for guidance and landing.

[0066] II. High-level graphical combat concept view product

[0067] The high-level combat concept view product developed on the construction device of the task meta-model based on the task meta-model of the architecture design refines the task execution profile of the MAV / UAV cooperative air combat concept in a high-level graphical description, clearly defines the objects contained in the MAV / UAV cooperative air combat system and the combat tasks participated in, and shows the combat purpose and combat architecture, as well as the interaction between the air combat system and the external system, including the information data interaction between each combat unit of the air combat system and each unit, as shown in Figure 8 .

[0068] II. Capability concept view product

[0069] The embodiment of the application develops the capability view product of the task meta-model based on the task meta-model of the architecture design on the construction device of the task meta-model, and describes the strategic background and the high-level demand range of the operational capability of the MAV / UAV air combat system.

[0070] IV. The mapping view product of the operational capability and the operational activity

[0071] The mapping view product of the operational capability and the operational activity of the embodiment of the application based on the task meta-model of the architecture design on the construction device of the task meta-model strengthens the correlation between the operational activity and the system capability under the decomposition of the MAV / UAV cooperative air combat concept, and verifies the attribution of each operational capability in the operational activity and the dependency of each operational activity on the operational capability. Through the correlation analysis, the required amount of the operational capability and the required times of each operational capability in each stage of the operational activity are determined. On this basis, the system capability and the operational activity can be perfected and optimized. The mapping view product of the operational capability and the operational activity actually connects the high-level demand of the air combat system capability level and the operational demand of the operational task level.

[0072] In summary, the task meta-model and the construction device of the task meta-model are combined, the defined air combat system meta-model is instantiated into the air combat system architecture model under the guidance of the operational concept and the assumption analysis, the architecture view product of the MAV / UAV cooperative air combat system is developed through the standardized architecture modeling simulation, the design method of the intelligent air combat system with the iterative capability demand full coverage of the operational concept, the operational capability, the operational task and the system function is formed, the architecture data sharing and reuse are realized, the consistency between the data is ensured, and the architecture design efficiency is improved.

[0073] In summary, the task meta-model provided by the embodiment of the application can adapt to the characteristics of the rapid change of the battlefield situation, plan the operational capability in the light of the dynamic change of the task, adjust the operational process, determine the matching relationship between the operational activity and the capability, select the task-related operational events, activities, interfaces and other task elements through data reference based on the task meta-model library, quickly construct the task model under the guidance of the operational concept, and realize the rapid integration of the operational architecture.

[0074] While embodiments of the application have been shown and described, it is to be understood that the embodiments described are merely divergences of the principles and application of the present application. Numerous modifications, changes, variations, substitutions, and equivalents will occur to those skilled in the art without departing from the spirit and scope of the present application as defined by the following claims and their equivalents.

Claims

1. A task meta-model construction method for a general operational process, characterized by, Comprise the following steps: S1, using the operational scenario logical entity, data, model operation, build operational concept model; S2, build capacity model; S3, build mission task-capability matrix model; S4, build operational activity decomposition tree and operational activity model; S5, build the mapping matrix model of capacity and operational activity, establish the mapping relationship between operational capacity and operational activity, form the capacity requirement directory through the task to the capacity mapping; S6, the operational concept model, capacity model, mission task-capability matrix model, operational activity model and mapping matrix model established in steps S1-S5 are integrated respectively, and a global digital dictionary is generated, that is, a task meta model is obtained; The specific steps of step S2 are: the operational capacity requirement is converted into the visual view of all capabilities required by the system structure in each stage of the operational life cycle, and the system capacity is refined and decomposed, the capacity level and dependency relationship are planned, and the capacity model is obtained; the specific steps of step S3 are: the operational mission task stage is planned according to the operational concept, the operational capacity is analyzed according to the operational concept, the stage capacity requirement is obtained, the capacity requirement directory is formed, the two-dimensional mapping matrix is established, the association relationship between different operational tasks and capacity is strengthened, the attribution of the proposed operational capacity is verified, the required amount of each operational capacity and the required number of each operational capacity in each stage are determined, and the task-capability matrix model is obtained; The specific steps of step S4 are: build operational activity decomposition tree, form the hierarchical relationship and input-output relationship between activities, form the stage operational activity model, establish the control flow and data flow between operational units, express the operational business logic, build operational resource flow description and operational resource interaction matrix, organize operational node information and resource interaction, build operational rule model and operational state transition description model and operational event tracking description, determine the business rules for constraining operational nodes to complete operational missions and operational activities, define the time sequence characteristics of key operational events of operational nodes and the change relationship of operational activities, and obtain the operational activity model.

2. The method of claim 1, wherein the method is characterized by: The specific steps of step S1 are: establish the association relationship between system elements, convert the description and solution of operational problem into operational capacity requirement according to operational concept requirement, form operational system overall architecture, obtain mission task decomposition, describe task composition and hierarchical relationship, describe air combat scenario scheme from task execution level with high-level graph, establish the interaction relationship between information data of each operational unit of air combat system and each unit, and obtain the operational concept model.

3. The method of claim 1, wherein the method further comprises: The specific steps of step S5 are: according to the mission task planning operational activity composition, establish two-dimensional mapping matrix with operational activity as column element and operational capacity as row element, and obtain the mapping matrix model; the specific steps of step S6 are: refer to the general terms and formal semantics of DM2 and combine the field characteristics of air combat system, organize the data element requirements of the integrated model, extract the necessary data element requirements in the system structure description to form the logical types of core concepts, concept relationships and attributes, obtain high-level data structure, and generate a global digital dictionary.

4. A task meta-model database oriented to a generic operational process, characterized in that, The task meta-model database is constructed by extracting feature core data in the task meta-model established in claim 1.

5. The mission meta-model database for common operational processes of claim 4, wherein, The feature core data includes mission task, combat event, combat activity, combat interface, personnel type and combat unit state.

6. A task meta-model construction apparatus for a common operational procedure, characterized by comprising: The device comprises: A model design basic environment module is configured to provide a visual modeling environment, support a user to manage a model in an engineering manner, and create various entities, data and models required for logical analysis of a combat scene by using a visual drawing panel; A model architecture design module is configured to support a user to selectively construct a view according to a standard modeling framework and a modeling language, realize data interconnection and intercommunication between different system models, achieve system modeling and simulation processes at various levels and granularities, and realize meta-model data reference of a meta-model library by data reference, and quickly construct a required model; A model simulation verification module is configured to provide a visual model deduction environment, support a user to observe a dynamic deduction process of a model, control a simulation process, and verify logical self-consistency of a constructed model by triggering an event relationship; A requirement development management module is configured to generate requirement text from model data according to a certain rule, support a user to develop a system development requirement, manage a system development requirement, a mission task requirement and a subsystem requirement, and analyze a behavior of a user to receive an upper-layer requirement and develop a lower-layer requirement; A meta-model management module is configured to comprehensively manage task meta-model data, and provide a data reference interface for a modeling environment to call a meta-model.

7. The task meta-modeling apparatus for general operational flow according to claim 6, wherein, The standard modeling framework is a Department of Defense Architecture Framework (DoDAF) 2.0, and the standard modeling language is UPDM.

8. The task meta-modeling apparatus for general operational flow according to claim 6, wherein, The task meta-model data adopts an XML file format, a data exchange specification of the meta-model includes a group of XSD files, and data conversion adopts an international general data conversion standard XMI and an XML-based conversion mode.

Images