Multi-domain cooperative combat data model construction system

Abstract

The invention discloses a multi-domain cooperative combat data model construction system, and belongs to the technical field of software system integration. The system comprises a shared data model and a multi-domain collaborative domain specific data model, the multi-domain collaborative domain specific data model is constructed based on the shared data model, and a multi-domain collaborative project data model is constructed based on the multi-domain collaborative domain specific data model. According to the system, clear definition and ordered connection of functions of each domain are realized, the logicality and normalization of a system architecture are improved, a clear basis is provided for collaborative operation of each link, and optimization of the overall operation efficiency and reduction of the interaction cost are facilitated.

Description

Technical Field

[0001] This invention relates to the field of software system integration technology, and in particular to a multi-domain collaborative data model construction system. Background Technology

[0002] In the current era of rapidly evolving information warfare, modern military operations have shifted from confrontations between single combat units to systemic collaboration involving multiple services and branches of the armed forces across multiple operational spaces. System-to-system confrontation verification has become a core element in testing combat capabilities. Simultaneously, the iteration of military technologies (such as the widespread adoption of intelligent equipment and distributed combat platforms) and the continuous deepening of joint operations requirements have resulted in battlefield data exhibiting heterogeneous sources, diverse formats, and inconsistent standards. Systems in different operational domains (such as environmental, perception, and weapon domains) often operate based on their own independent data specifications. This makes the interoperability of data between different domains a critical issue that needs to be addressed in multi-domain joint system confrontation verification. Not only are the definitions, formats, and semantics of data across different domains difficult to unify, but ambiguities and conflicts during cross-domain data interaction also severely impact information sharing efficiency and even restrict the effectiveness of system-wide operations. How to achieve effective interoperability of data between different domains has become a key bottleneck that urgently needs to be overcome in the construction of current multi-domain collaborative combat systems. Summary of the Invention

[0003] In response to the aforementioned technical background, this invention proposes a multi-domain collaborative data model. Based on the domain data model, a data model for multi-domain system integration projects is constructed, which solves the problem of mutual understanding in multi-domain collaboration, realizes the clear definition and orderly connection of the functions of each domain, improves the logic and standardization of the system architecture, optimizes the overall operating efficiency, and reduces interaction costs.

[0004] To achieve the above objectives, the embodiments of the present invention adopt the following technical solution: a multi-domain collaborative data model construction system, which includes a shared data model and a multi-domain collaborative domain-specific data model, and constructs a multi-domain collaborative domain-specific data model based on the shared data model, and constructs a multi-domain collaborative project data model based on the multi-domain collaborative domain-specific data model; The data architecture of the shared data model includes a data model, a UoP model, and an integration model; Data Model: Through data refinement from Conceptual Data Model (CDM) to Logical Data Model (LDM) and then to Platform Data Model (PDM), the definition is carried out from the semantics of operational concepts to the physical storage format; Among them, the Conceptual Data Model (CDM) defines entities, relationships, and semantic rules that are common to multiple domains; the Logical Data Model (LDM) supplements the Conceptual Data Model (CDM) with measurement rules, value range constraints, and unit standards; and the Platform Data Model (PDM) binds physical storage formats, interface protocols, and hardware adaptation details. UoP Model: By refining the interface link from the abstract UoP model to the UoP data model, the data model is bound to the interface contract of portable software components; The abstract UoP model defines the functional boundaries and input / output interface types of components; the UoP data model binds to the specific data format in the PDM. Integration Model: By abstracting the integration model to the integration model IM, the interaction rules between components are defined; The abstract integration model defines the interaction relationships and topology between components; the integration model IM binds the transmission protocol, timing constraints, and fault handling rules. The shared data model includes five elements: basic data types, enumerations, observables, measurement systems, and units.

[0005] Furthermore, the basic data types include FACE_char, FACE_boolean, FACE_octet, FACE_short, FACE_long, FACE_long_long, FACE_unsigned_short, FACE_unsigned_long, FACE_float, and FACE_double; The enumeration types include combat domain enumeration, IFF enumeration, platform category enumeration, platform type enumeration, platform model enumeration, sensor type enumeration, radar model enumeration, weapon type enumeration, missile type enumeration, air-to-air missile model enumeration, ship-to-air missile model enumeration, chain type enumeration, area shape enumeration, and cloud shape enumeration. Observable measurements include ID, distance, angle, position, velocity, acceleration, altitude, temperature, quantity, time point, time period, period, frequency, identifier, and type; The measurement system includes CGCS2000, ECEF, Northeast Sky, North Sky East, North East Ground, Machine System, Missile System, Ship System, Quasi-Ship Reference Coordinate System, Shipborne Radar Output Coordinate System, Navigation Reference Coordinate System, Intraday Second Time Measurement System, UTC Time Measurement System, and Counting Measurement System; Units include units of length, angle, angular velocity, velocity, acceleration, temperature, time, and frequency.

[0006] Furthermore, the multi-domain collaborative domain-specific data model, based on the shared data model, is customized and extended for 10 core operational domains, with each domain supplemented with exclusive data elements; at the same time, it refines data relationships through conceptual entity models and logical entity models. The conceptual entity model defines the core data entities and their relationships within the domain, clarifying the semantic logic of the data; the logical entity model supplements the logical rules of the data, ensuring the validity and consistency of the data within the domain.

[0007] Furthermore, the 10 core operational domains are: environment domain, user management domain, perception domain, decision-making domain, integrated fire control domain, communication domain, platform domain, sensor domain, weapon domain, and knowledge domain.

[0008] Furthermore, the data model elements of multi-domain collaborative projects are bound to the physical implementation details of specific projects, transforming the abstract data model into technical specifications that can be directly used for system development: the platform entity model defines the storage and transmission format of data on specific hardware platforms, ensuring that data can be stored and parsed on the actual platform; the platform view model defines the visualization and interaction specifications of data; and the UoP model defines the interface specifications of portable units, ensuring that software components from different domains can communicate directly.

[0009] The multi-domain collaborative data model proposed in this invention has the following beneficial effects: The system includes a shared data model and a multi-domain collaborative domain-specific data model. The multi-domain collaborative domain-specific data model is constructed based on the shared data model, and a multi-domain collaborative project data model is constructed based on the multi-domain collaborative domain-specific data model. This system achieves clear definition and orderly connection of the functions of each domain, which not only improves the logic and standardization of the system architecture but also provides a clear basis for the collaborative operation of each link, helping to optimize overall operating efficiency and reduce interaction costs. Attached Figure Description

[0010] Figure 1 This is a data architecture diagram that this invention follows; Figure 2 These are the elements involved in the shared data model in this invention; Figure 3 This refers to the domains involved in the multi-domain collaborative domain-specific data model of this invention; Figure 4 These are the elements involved in the conceptual entity model of the multi-domain collaborative domain-specific data model in this invention; Figure 5 These are the elements involved in the logical entity model of the multi-domain collaborative domain-specific data model in this invention; Figure 6 These are the elements involved in the platform entity model of the multi-domain collaborative project data model in this invention; Figure 7 These are the elements involved in the platform view model of the multi-domain collaborative project data model in this invention; Figure 8 These are the elements involved in the UoP model of the multi-domain collaborative project data model in this invention. Detailed Implementation

[0011] In the description of this invention, it should be understood that the terms "center," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0012] A multi-domain collaborative data model is proposed, which designs a shared data model and a multi-domain collaborative domain-specific data model. Based on the shared data model, a multi-domain collaborative domain-specific data model is constructed, and based on the multi-domain collaborative domain-specific data model, a multi-domain collaborative project data model is constructed, thus solving the problem of information interoperability in multi-domain collaborative combat systems.

[0013] This invention enables airborne multi-domain systems to understand and process airborne system information, airborne multi-domain systems to understand and process shipborne system information, shipborne multi-domain systems to understand and process shipborne system information, and shipborne multi-domain systems to understand and process airborne system information in the field of multi-domain collaboration. Example

[0014] According to the appendix Figures 1 to 8 The present invention will be further described as follows: In this embodiment, the multi-domain collaborative data model is designed with a multi-domain collaborative data model architecture, such as... Figure 1 As shown in the diagram, the progression of the three core levels—data model, UoP model, and integration model—is the foundation for multi-domain collaborative data interoperability.

[0015] Data Model: Through the data refinement link from Conceptual Data Model (CDM) to Logical Data Model (LDM) and then to Platform Data Model (PDM), the entire lifecycle definition from operational concept semantics to physical storage format is realized, ensuring the consistency of multi-domain systems' understanding of the same data.

[0016] Conceptual Data Model (CDM): As a top-level abstraction, it defines entities, relationships, and semantic rules that are common to multiple domains; Logical Data Model (LDM): Based on CDM, it supplements measurement rules, value range constraints, and unit standards; Platform Data Model (PDM): It binds physical storage format, interface protocol, and hardware adaptation details.

[0017] UoP Model: By abstracting the interface from the UoP model to the UoP data model UM, the data model is bound to the interface contract of portable software components, solving the problem of component reading / writing data.

[0018] Abstract UoP Model: Defines the functional boundaries and input / output interface types of components; UoP Data Model (UM): Binds to the specific data format in PDM. This refined interface logic enables UoP components to be plug-and-play across different platforms, significantly reducing the integration cost of multi-domain systems.

[0019] Integration Model Definition: By abstracting the integration model → IM "integration refinement" link, the interaction rules between components are defined to solve the problem of data flow between systems.

[0020] Abstract Integration Model: Defines the interaction relationships and topology between components; it serves as the logical blueprint for system integration. Integration Model (IM): Binds transmission protocols, timing constraints, and fault handling rules to complete physical interactions.

[0021] The final output consists of three types of products: data specification documents, component code, and system configuration files.

[0022] It should be noted that shared data model elements, such as Figure 2 As shown, a basic data specification that is common to multiple domains is defined to ensure consistency across different domains from the data source. The core elements include: Basic data types: FACE_char, FACE_boolean, FACE_octet, FACE_short, FACE_long, FACE_long_long, FACE_unsigned_short, FACE_unsigned_long, FACE_float, FACE_double, to avoid data parsing errors caused by type incompatibility.

[0023] Enumeration types: combat domain enumeration, friend or foe identification enumeration, platform category enumeration, platform type enumeration, platform model enumeration, sensor type enumeration, radar model enumeration, weapon type enumeration, missile type enumeration, air-to-air missile model enumeration, ship-to-air missile model enumeration, chain type enumeration, area shape enumeration, cloud shape enumeration, with unified semantic definition.

[0024] Observable parameters: ID, distance, angle, position, velocity, acceleration, altitude, temperature, quantity, time point, time period, period, frequency, identifier, type.

[0025] Measurement systems include: CGCS2000, ECEF, Northeast Sky, North Sky East, North East Ground, Aircraft System, Missile System, Ship System, Quasi-ship Reference Coordinate System, Shipborne Radar Output Coordinate System, Navigation Reference Coordinate System, Intraday Second Time Measurement System, UTC Time Measurement System, and Counting Measurement System, ensuring that position data from different platforms can be directly compared.

[0026] Units: length units, angle units, angular velocity units, velocity units, acceleration units, temperature units, time units, frequency units, solving the conversion problem of different units for the same parameter.

[0027] Multi-domain collaborative domain-specific data model elements such as Figures 3-5 As shown, based on the shared model, customized extensions are made for 10 core operational domains, with each domain supplemented with exclusive data elements. Simultaneously, data relationships are refined through conceptual entity models and logical entity models. Figure 3 The system covers all key aspects of collaborative operations, including: the environment domain (battlefield weather, terrain), the user management domain (combatant permissions), the perception domain (radar / satellite reconnaissance data), the decision-making domain (command and control instructions), the integrated fire control domain (firepower allocation data), the communication domain (data link transmission parameters), the platform domain (combat platform status), the sensor domain (sensor detection range / accuracy), the weapon domain (weapon type / range), and the knowledge domain (battlefield rule base).

[0028] Conceptual Entity Model: Defines the core data entities and their relationships within the domain, such as basic entities, specialized entities, and related entities, and clarifies the semantic logic of the data.

[0029] Logical entity model: Supplementing the logical rules of data, such as measurement systems, unit constraints, and reference points, to ensure the validity and consistency of data within the domain.

[0030] Multi-domain collaborative project data model elements such as Figures 6-8 As shown, it binds to the physical implementation details of specific projects, transforming the abstract data model into technical specifications that can be directly used for system development. The core includes: Platform entity model: Defines the storage and transmission format of data on a specific hardware platform, such as IDL type, signal bit width, and quantization precision, to ensure that data can be stored and parsed on the actual platform.

[0031] Platform view model: Defines the visualization and interaction specifications for data, such as English name-Chinese name mapping and array length, to support human-computer interaction interface design.

[0032] UoP model: Defines the interface specifications of portable units, such as port names, communication styles, message exchange types, topics / addresses, to ensure that software components from different domains can communicate directly.

[0033] This model enables four key cross-domain interoperability capabilities, directly addressing the core pain points of multi-domain collaboration: Airborne multi-domain system ↔ Airborne system information: data interoperability within airborne systems; Airborne multi-domain system ↔ Shipborne system information: air-sea cross-domain data interoperability; Shipborne multi-domain system ↔ Shipborne system information: data interoperability within shipborne systems; Shipborne multi-domain system ↔ Airborne system information: sea-air cross-domain data interoperability.

[0034] Shared models unify basic standards, reducing redundant adaptations; domain-specific models support rapid expansion to new operational domains (such as network domains); models are bound to physical implementations, directly supporting system integration and shortening development cycles.

[0035] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A multi-domain collaborative data model construction system, characterized in that, The system includes a shared data model and a multi-domain collaborative domain-specific data model. It constructs a multi-domain collaborative domain-specific data model based on the shared data model and a multi-domain collaborative project data model based on the multi-domain collaborative domain-specific data model. The data architecture of the shared data model includes a data model, a UoP model, and an integration model; Data Model: Through data refinement from Conceptual Data Model (CDM) to Logical Data Model (LDM) and then to Platform Data Model (PDM), the definition is carried out from the semantics of operational concepts to the physical storage format; Among them, the Conceptual Data Model (CDM) defines entities, relationships, and semantic rules that are common to multiple domains; the Logical Data Model (LDM) supplements the Conceptual Data Model (CDM) with measurement rules, value range constraints, and unit standards; and the Platform Data Model (PDM) binds physical storage formats, interface protocols, and hardware adaptation details. UoP Model: By refining the interface link from the abstract UoP model to the UoP data model, the data model is bound to the interface contract of portable software components; The abstract UoP model defines the functional boundaries and input / output interface types of components; the UoP data model binds to the specific data format in the PDM. Integration Model: By abstracting the integration model to the integration model IM, the interaction rules between components are defined; The abstract integration model defines the interaction relationships and topology between components; the integration model IM binds the transmission protocol, timing constraints, and fault handling rules. The shared data model includes five elements: basic data types, enumerations, observables, measurement systems, and units.

2. The multi-domain collaborative data model construction system according to claim 1, characterized in that, The basic data types include FACE_char, FACE_boolean, FACE_octet, FACE_short, FACE_long, FACE_long_long, FACE_unsigned_short, FACE_unsigned_long, FACE_float, and FACE_double; The enumeration types include combat domain enumeration, IFF enumeration, platform category enumeration, platform type enumeration, platform model enumeration, sensor type enumeration, radar model enumeration, weapon type enumeration, missile type enumeration, air-to-air missile model enumeration, ship-to-air missile model enumeration, chain type enumeration, area shape enumeration, and cloud shape enumeration. Observable measurements include ID, distance, angle, position, velocity, acceleration, altitude, temperature, quantity, time point, time period, period, frequency, identifier, and type; The measurement system includes CGCS2000, ECEF, Northeast Sky, North Sky East, North East Ground, Machine System, Missile System, Ship System, Quasi-Ship Reference Coordinate System, Shipborne Radar Output Coordinate System, Navigation Reference Coordinate System, Intraday Second Time Measurement System, UTC Time Measurement System, and Counting Measurement System; Units include units of length, angle, angular velocity, velocity, acceleration, temperature, time, and frequency.

3. The multi-domain collaborative data model construction system according to claim 2, characterized in that, The multi-domain collaborative domain-specific data model, based on the shared data model, is customized and extended for 10 core operational domains, with each domain supplemented with exclusive data elements. At the same time, it refines data relationships through conceptual entity models and logical entity models. The conceptual entity model defines the core data entities and their relationships within the domain, clarifying the semantic logic of the data; the logical entity model supplements the logical rules of the data, ensuring the validity and consistency of the data within the domain.

4. The multi-domain collaborative data model construction system according to claim 3, characterized in that, The 10 core operational domains are: environment domain, user management domain, perception domain, decision-making domain, integrated fire control domain, communication domain, platform domain, sensor domain, weapon domain, and knowledge domain.

5. The multi-domain collaborative data model construction system according to claim 4, characterized in that, Multi-domain collaborative project data model elements are bound to the physical implementation details of specific projects, transforming the abstract data model into technical specifications that can be directly used for system development: the platform entity model defines the storage and transmission format of data on specific hardware platforms, ensuring that data can be stored and parsed in the actual platform; the platform view model defines the visualization and interaction specifications of data; the UoP model defines the interface specifications of portable units, ensuring that software components from different domains can communicate directly.

Images