System model generation methods, apparatus, computer equipment, readable storage media, and program products

By parsing and creating cross-dimensional relationship chains, the inefficiency and error-proneness of SysML tools in creating complex system models are solved, achieving efficient system model generation.

CN123114429APending Publication Date: 2026-11-17SHANGHAI AIRCRAFT DESIGN & RES INST COMML AIRCRAFT OF CHINA +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611483339.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing SysML tools suffer from inefficiency and error-proneness when creating complex system models, especially in the cumbersome process of establishing relationships between model elements, which affects the efficiency of system modeling.

Method used

By receiving a structured data source, multiple data units are parsed to extract element attribute data and associated features. Based on this data, model elements are created in the target model storage, and cross-dimensional relationship chains are established, including the allocation relationship chain between behavioral model elements and entity model elements, as well as the connection relationship chain between entity model elements and interaction model elements.

Benefits of technology

It improves system modeling efficiency, shortens the modeling time for complex systems, and enhances the efficiency of system model construction and the accuracy of topology.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114429A_ABST
    Figure CN123114429A_ABST
Patent Text Reader

Abstract

This application relates to a system model generation method, apparatus, computer device, computer-readable storage medium, and computer program product. The method acquires multiple data units carrying different architectural dimensions such as functional logic, physical components, and interface interactions, and extracts element association features determined based on the reference relationships between these data units during parsing. This enables the system to automatically establish cross-dimensional relationship chains while batch-creating model elements in the target model storage. Specifically, this includes at least one of the following: allocation relationship chains between behavioral model elements and entity model elements; and connection relationship chains between entity model elements and interaction model elements. This effectively improves the efficiency of establishing complex system architectural relationships and shortens the modeling time for complex systems. Simultaneously, automatically establishing relationship chains based on determined element association features effectively improves the efficiency of system model construction and the accuracy of the topology.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a system model generation method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the development of computer technology and systems engineering technology, the adoption of model-based systems engineering (MBSE) has become a trend in the design and development of complex systems such as aircraft. Its core is the use of SysML (Systems Modeling Language) to build system models within architecture modeling tools. However, since initial system design data is often stored in spreadsheets, the standard spreadsheet / CSV import functionality provided by existing SysML tools has fundamental limitations. It cannot efficiently and accurately create complete system models with complex hierarchies and relationships in batches based on spreadsheet data. This results in a time-consuming, laborious, and error-prone manual conversion process from data to model, becoming a major efficiency bottleneck for the widespread application of MBSE.

[0003] Currently, the standard spreadsheet / CSV import function provided by mainstream SysML tools adopts a "single-row, single-element" mapping mode. This means that each row of data in the spreadsheet—a single column, a single attribute—can only create one independent SysML model element (such as a Block), and each column corresponds to one attribute value for that element. However, this method makes establishing all the relationships between model elements that reflect the system architecture (composition, allocation, dependency, interface connections, etc.) cumbersome, impacting system modeling efficiency. Summary of the Invention

[0004] Therefore, it is necessary to provide a system model generation method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of system modeling in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a system model generation method, including:

[0006] Receive a system model generation request and obtain a structured data source corresponding to the system model generation request; the structured data source includes multiple data units, each of which carries data of different architectural dimensions of the system architecture, and the architectural dimensions include at least functional logic dimension, physical component dimension and interface interaction dimension;

[0007] The multiple data units are parsed to extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0008] Based on the element attribute data, the model elements are created in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0009] Based on the element association features, a cross-dimensional relationship chain is established among the created model elements to generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

[0010] In one embodiment, parsing the plurality of data units and extracting element attribute data and element association features includes:

[0011] The parsing order is determined according to the data dependencies between the multiple data units, and the multiple data units are parsed sequentially according to the parsing order;

[0012] When parsing the current data unit, based on the reference identifier in the current data unit, the element attribute data that matches the reference identifier is searched from the previously parsed data units, and the element association feature is determined based on the matching result.

[0013] In one embodiment, the parsing order is to sequentially parse the data unit carrying the data of the functional logic dimension, the data unit carrying the data of the physical component dimension, and the data unit carrying the data of the interface interaction dimension;

[0014] Specifically, when parsing data units carrying data of the physical component dimension, the currently parsed physical entity data is matched with previously parsed functional behavior data to obtain element association features representing the association between function and physical allocation; when parsing data units carrying data of the interface interaction dimension, the currently parsed interaction interface data is matched with previously parsed physical entity data to obtain element association features representing the association between physical and interactive connections.

[0015] In one embodiment, the extracted element association features include:

[0016] Identify the preset separator within the cell of the data unit;

[0017] Based on the preset separator, the multi-entry data in the cell is split into multiple independent related entries;

[0018] Each of the multiple independent associated entries is used as an independent relation endpoint to establish a one-to-many allocation relation chain and / or connection relation chain.

[0019] In one embodiment, the element association feature includes a direction indicator feature; establishing a cross-dimensional relationship chain among the created model elements based on the element association feature includes:

[0020] When the directional marker feature indicates a first direction, a first dependency relationship is established between the interaction model element and the behavior model element;

[0021] When the direction marker feature indicates a second direction, a second dependency is established between the behavior model element and the interaction model element, the second dependency being in the opposite direction to the first dependency.

[0022] In one embodiment, the element association features include local port features, peer port features, and interaction signal features; establishing the connection relationship chain based on the element association features includes:

[0023] Based on the local port feature and the peer port feature that appear together in the same data row, establish a connection relationship between the port model elements associated with the entity model element;

[0024] Based on the characteristics of the interaction signals, the corresponding signal streams are bound to the established connection relationships.

[0025] Secondly, this application also provides a system model generation apparatus, comprising:

[0026] The data acquisition module is used to receive system model generation requests and acquire structured data sources corresponding to the system model generation requests. The structured data sources include multiple data units, which respectively carry data of different architectural dimensions of the system architecture. The architectural dimensions include at least functional logic dimensions, physical component dimensions, and interface interaction dimensions.

[0027] The data table parsing module is used to parse the multiple data units and extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0028] The element generation module is used to create the model elements in the target model storage based on the element attribute data. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0029] The system model generation module is used to establish cross-dimensional relationship chains among the created model elements based on the element association features, and generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

[0030] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0031] Receive a system model generation request and obtain a structured data source corresponding to the system model generation request; the structured data source includes multiple data units, each of which carries data of different architectural dimensions of the system architecture, and the architectural dimensions include at least functional logic dimension, physical component dimension and interface interaction dimension;

[0032] The multiple data units are parsed to extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0033] Based on the element attribute data, the model elements are created in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0034] Based on the element association features, a cross-dimensional relationship chain is established among the created model elements to generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

[0035] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0036] Receive a system model generation request and obtain a structured data source corresponding to the system model generation request; the structured data source includes multiple data units, each of which carries data of different architectural dimensions of the system architecture, and the architectural dimensions include at least functional logic dimension, physical component dimension and interface interaction dimension;

[0037] The multiple data units are parsed to extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0038] Based on the element attribute data, the model elements are created in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0039] Based on the element association features, a cross-dimensional relationship chain is established among the created model elements to generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

[0040] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0041] Receive a system model generation request and obtain a structured data source corresponding to the system model generation request; the structured data source includes multiple data units, each of which carries data of different architectural dimensions of the system architecture, and the architectural dimensions include at least functional logic dimension, physical component dimension and interface interaction dimension;

[0042] The multiple data units are parsed to extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0043] Based on the element attribute data, the model elements are created in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0044] Based on the element association features, a cross-dimensional relationship chain is established among the created model elements to generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

[0045] The aforementioned system model generation method, apparatus, computer equipment, computer-readable storage medium, and computer program product receive a system model generation request and obtain a structured data source corresponding to the request. The structured data source includes multiple data units, each carrying data for different architectural dimensions of the system architecture. These architectural dimensions include at least functional logic dimensions, physical component dimensions, and interface interaction dimensions. The method parses the multiple data units to extract element attribute data and element association features. The element attribute data defines model elements within the corresponding architectural dimension. The element association features are determined at least partially based on the reference relationships between the multiple data units and are used to characterize the association relationships between model elements in different architectural dimensions. Based on the element attribute data, model elements are created in the target model storage. These created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension. Based on the element association features, a cross-dimensional relationship chain is established between the created model elements to generate and output the target system model. The cross-dimensional relationship chain includes at least one of the following: an allocation relationship chain between behavioral model elements and entity model elements, and a connection relationship chain between entity model elements and interaction model elements. This application acquires multiple data units that respectively carry different architectural dimensions such as functional logic, physical components, and interface interactions. During parsing, it extracts element association features determined by the reference relationships between these data units. This enables the system to automatically establish cross-dimensional relationship chains while batch-creating model elements in the target model storage. Specifically, this includes at least one of the following: allocation relationship chains between behavioral model elements and entity model elements; and connection relationship chains between entity model elements and interaction model elements. This effectively improves the efficiency of establishing complex system architectural relationships and shortens the modeling time for complex systems. Furthermore, automatically establishing relationship chains based on determined element association features effectively improves the efficiency of system model construction and the accuracy of the topology. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 This is an application environment diagram of the system model generation method in one embodiment;

[0048] Figure 2 This is a flowchart illustrating a system model generation method in one embodiment;

[0049] Figure 3 This is a schematic diagram of the automatic generation of the model package structure in one embodiment;

[0050] Figure 4 This is a schematic diagram of the configuration interface in one embodiment;

[0051] Figure 5 This is a schematic diagram of the structured data submission workflow in one embodiment;

[0052] Figure 6 This is a flowchart illustrating the data processing of multiple sheet templates in one embodiment;

[0053] Figure 7 A flowchart illustrating the creation of model relationships in one embodiment;

[0054] Figure 8 A flowchart illustrating the creation of functional architecture template relationships in one embodiment;

[0055] Figure 9 A flowchart illustrating the creation of functional architecture template relationships in one embodiment;

[0056] Figure 10 A flowchart illustrating the creation of a template relationship between device functions and interface cross-linking in one embodiment;

[0057] Figure 11 This is a structural block diagram of a system model generation device in one embodiment;

[0058] Figure 12 This is an internal structural diagram of a computer device in one embodiment;

[0059] Figure 13 This is a diagram of the internal structure of a computer device in another embodiment. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0061] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0062] The system model generation method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or located in the cloud or on other network servers. When a user on terminal 102 wants to generate a complex system model, they can edit the data on terminal 102 to generate a structured data source for building the system. Then, a system model generation request is submitted to server 104 based on the structured data source. Server 104 receives the system model generation request and obtains the structured data source corresponding to the system model generation request. The structured data source includes multiple data units, which respectively carry data of different architectural dimensions of the system architecture. The architectural dimensions include at least functional logic dimension, physical component dimension, and interface interaction dimension. Multiple data units are parsed to extract element attribute data and element association features. The element attribute data is used to define model elements under the corresponding architectural dimension. The element association features are determined at least in part based on the reference relationship between multiple data units and are used to characterize the association relationship between model elements of different architectural dimensions. Based on the element attribute data, model elements are created in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension. Based on the element association features, cross-dimensional relationship chains are established between the created model elements to generate and output the target system model. The cross-dimensional relationship chain includes at least one of the following: the allocation relationship chain between behavioral model elements and entity model elements, and the connection relationship chain between entity model elements and interaction model elements. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection equipment. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. Server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0063] In one exemplary embodiment, such as Figure 2 As shown, a system model generation method is provided, which can be applied to a terminal or a server. Figure 1 Taking server 104 as an example, the explanation includes the following steps 201 to 207. Wherein:

[0064] Step 201: Receive the system model generation request and obtain the structured data source corresponding to the system model generation request; the structured data source includes multiple data units, which respectively carry data of different architectural dimensions of the system architecture. The architectural dimensions include at least the functional logic dimension, the physical component dimension, and the interface interaction dimension.

[0065] A structured data source refers to a collection of data with a fixed data format, clearly defined fields, and an inherent logical structure. In a specific embodiment, a structured data source may be a spreadsheet file (such as an Excel file) containing multiple logically related worksheets, or an equivalent collection of database tables, nested JSON arrays, etc.

[0066] A data unit refers to a collection of data in a structured data source that is independently indexed and carries data of a certain architectural dimension. Data units include, but are not limited to: different worksheets in the same spreadsheet file, different data ranges in the same worksheet, tabular data in different data files, data tables in a database, and data nodes in structured documents (such as JSON and XML documents). For example, in a spreadsheet (Excel) scenario, a data unit specifically corresponds to a worksheet (Sheet) in the spreadsheet file.

[0067] In systems engineering (such as architectural frameworks like SysML), the architectural dimension refers to a specific perspective or aspect from which complex systems are abstracted, described, and analyzed. This application reduces data coupling by decoupling complex system architecture into multiple related dimensions at the data source.

[0068] In terms of architectural dimensions, the functional logic dimension describes "what the system does." This dimension focuses on the decomposition tree of system functions, the hierarchical relationships of functions, and the logical interactions between functions, without concerning the specific physical hardware or software that carries the functions. The physical component dimension describes "what physical entities the system is composed of." This dimension focuses on the system's physical hardware devices, software components, system hierarchical inclusion relationships, and the spatial or logical organization of physical entities. The interface interaction dimension describes the architectural perspective of "how the various physical components of the system connect and communicate." This dimension focuses on the low-level interaction details on physical devices, such as ports, connectors, signal flows, data packets, and Interface Control Documents (ICDs).

[0069] For example, when a user on terminal 102 wants to generate a complex system model, they can edit the relevant basic data of the system model on terminal 102, and then construct a structured data source based on this basic data. They then submit a system model generation request to server 104 based on the structured data source. Server 104 receives the system model generation request, parses the request message, and obtains the storage path or file identifier of the target structured data source. Subsequently, server 104 loads and reads the corresponding structured data source (e.g., a user-uploaded "architectural Excel template" file) from the local disk, distributed file system, or model attachment library, and loads it into the server's memory or temporary workspace, while performing basic syntax and format checks on the file. Then, server 104 can call the corresponding table parsing engine to traverse the structured data source and identify the multiple data units it contains, such as multiple sheet sub-tables in an Excel file. In this process, server 104 also determines the different architectural dimensions of the system architecture carried by multiple data units, specifically including: data units carrying the functional logic dimension, which are used to define the decomposition tree and hierarchical relationship of system-level functions and device-level functions; data units carrying the physical component dimension, which are used to define the physical hierarchical inclusion relationship of the system, physical devices, and resident software; and data units carrying the interface interaction dimension, which are used to define interaction details such as device ports, connector pins, signal names, and input / output directions. In another embodiment, server 104 can further identify independent data units (Sheets) for subsequently attaching complex attributes such as IDs and FDL levels to the functional model, thereby decoupling functional definition from attribute assignment.

[0070] Step 203: parse multiple data units and extract element attribute data and element association features; element attribute data is used to define model elements under the corresponding architecture dimension; element association features are determined at least in part based on the reference relationship between multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0071] Element attribute data refers to scalar data extracted from each column of a data unit, used to define the characteristics of a model element (i.e., the characteristics of a single model element itself) under the corresponding architectural dimension. Examples include: function name, ID, FDL level; physical device name, ATA chapter number; and port type, pin number, etc. Element association features, on the other hand, refer to data features determined at least partially based on the reference relationships between multiple data units (e.g., extracted from the inline structure, cell content, or cross-data unit mapping of a data unit), used to characterize the association relationships (such as topological connections or logical dependencies) between model elements in different architectural dimensions.

[0072] The relationships between model elements across different architectural dimensions include functional-to-physical allocation relationships and physical-to-interaction connection relationships. Functional-to-physical allocation relationships refer to the mapping characteristics between elements representing the functional logic dimension (such as system-level functions, device-level functions) and elements representing the physical component dimension (such as systems, physical devices). In SysML, this is specifically represented by the Allocate allocation relationship. Physical-to-interaction connection relationships refer to the mapping characteristics between elements representing the physical component dimension (such as devices, ports) and elements representing the interface interaction dimension (such as signals, data flows) regarding "physical connectivity and data transmission." In SysML, this is represented by Connector connections and item flow relationships.

[0073] For example, after parsing and determining the data units, a preset parsing rule is first loaded to establish a preset architectural dependency order, and multiple data units are parsed sequentially accordingly. During the specific parsing process, server 104 prioritizes parsing data units carrying functional logic dimensions. In this process, not only are element attribute data such as function names extracted, but also key element association features are extracted. After the functional data parsing is complete, server 104 further parses data units carrying physical components in the dependency order, extracting element attribute data of physical entities such as systems, physical devices, and resident software. For the parsing process of physical component dimension data units, server 104 specifically uses in-row association inference or cross-data unit mapping queries to match the physical entity data parsed in the current row with the functional behavior data parsed and cached in the previous stage. For example, based on the co-occurrence of "system name" and "device name" in the same row, or the correspondence between functions and carrying devices, the function-to-physical allocation association features are accurately extracted, providing data support for the subsequent automatic creation of function-to-physical device allocation relationships (Allocate). Finally, server 104 parses the data units of the interface interaction dimension, extracting element attribute data of the interaction interface such as connector number, pin number, and signal name. Simultaneously, this step matches the currently parsed port / pin data with the physical device data parsed in the previous stage, extracting the physical-to-interaction connection association. The element association features are determined at least in part based on the reference relationships between multiple data units, namely, matching queries of reference identifiers (such as LIN number, name, ID), cross-data unit mapping table queries (including attribute mapping tables), and fault tolerance handling when matching fails. In a specific embodiment, server 104 also extracts the status flag bits (such as the "input / output" direction flag) from the data row, using them as key element association features characterizing the directionality of the connection relationship. This flag bit feature can be used to determine the direction of the dependency relationship, thereby providing precise control parameters for creating signal flow transmission relationships with a clear data flow direction (such as ICD item flow). In another embodiment, when extracting element attribute data and element association features, data validation and null value normalization are also required. This process terminates and reports an error when required fields (such as LIN number, ATA chapter number) are empty; preset null value identifiers such as "empty string", " / ", and "N / A" are uniformly normalized to null values; and parsing terminates when the template structure is invalid. This effectively ensures the validity of the data unit parsing process.

[0074] Step 205: Based on the element attribute data, create model elements in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0075] The target model storage refers to the underlying database or model engineering space used for persistent storage, management and maintenance of system model elements and their relationships. The target model storage includes, but is not limited to, model databases, model engineering spaces, and model description files (such as XMI and XML format model description files) that exist in file form.

[0076] For specific model elements, behavioral model elements correspond to the functional logic dimension and are model objects used to represent "what" the system does. In SysML, these can be represented as functional blocks, activities, or use cases, used to describe the functional decomposition and logical behavior of the system. Entity model elements correspond to the physical component dimension and are model objects used to represent "what" the system is composed of. In SysML, these can be represented as physical blocks, components, or nodes, used to describe the system's physical hardware, software carriers, and system hierarchy. Interaction model elements correspond to the interface interaction dimension and are model objects used to represent "how" the various physical components of the system connect and communicate. In SysML, these can be represented as ports, connectors, interfaces, or item flows, used to describe the underlying physical connections and signal transmission mechanisms.

[0077] For example, server 104 first obtains the preset target storage path (e.g., the target location specified by the user through the configuration interface) and determines the root node for creating model elements in the target model storage. Furthermore, it can clean and handle conflicts in the element attribute data to ensure data validity. Based on the cleaned and conflict-handled element attribute data, it calls the model instantiation engine to create heterogeneous model elements corresponding to different architectural dimensions. For model element creation, attribute data from the functional logic dimension can be instantiated into behavioral model elements (e.g., creating a function block and assigning attributes such as ID and FDL level); attribute data from the physical component dimension can be instantiated into entity model elements (e.g., creating a system block or physical device block); and attribute data from the interface interaction dimension can be instantiated into interaction model elements (e.g., creating a port or signal).

[0078] Step 207: Based on element association features, establish cross-dimensional relationship chains among the created model elements, generate and output the target system model; the cross-dimensional relationship chain includes at least one of the following: the allocation relationship chain between behavioral model elements and entity model elements, and the connection relationship chain between entity model elements and interaction model elements.

[0079] In this context, the allocation chain refers to the set of logical mappings and hierarchical relationships established between the functional logic dimension (behavior) and the physical component dimension (entity). For example, in SysML, this manifests as the allocation relationship from function to physical device, and the combination / inclusion relationship between functional or physical levels. The connection chain, on the other hand, refers to the set of physical connectivity and data transfer relationships established between the physical component dimension (entity) and the interface interaction dimension (interaction). In SysML, this manifests as connector relationships between ports, and item flows or dependencies with explicit data flow directions.

[0080] The target system model refers to the system engineering model generated after batch creation of elements and automatic construction of relationship chains, which contains complete architectural dimensions (behaviors, entities, interactions) and their inter-topological relationships. This model can be directly used for subsequent view rendering, simulation analysis, or traceability verification.

[0081] For example, server 104 can load various model elements (behavioral model elements, entity model elements, and interaction model elements) into memory and simultaneously load the element association features extracted during the parsing phase. Subsequently, in order to generate the system model, server 104 will start the built-in automated relationship mapping engine to prepare to transform the abstract data association features into specific model topology connections.

[0082] First, during the model creation process, server 104 performs cross-dimensional relationship inference based on the parsing results of functional and physical architecture data units. For example, when server 104 identifies the simultaneous existence of first-level and second-level behavioral fields in peer data (e.g., the simultaneous existence of "aircraft-level function" and "system-level function" fields), it automatically creates a behavioral hierarchy inclusion relationship between the corresponding behavioral model elements based on this co-occurrence feature; similarly, it creates a physical hierarchy inclusion relationship for system-level and device-level entity fields. When it identifies the simultaneous existence of behavioral fields (functions) and entity fields (carrying devices / systems) in peer data, or when it matches the correspondence between functions and physical devices through cross-data sub-table mapping features, the server automatically creates an allocation relationship (such as SysML's Allocate relationship) between the corresponding behavioral model elements and entity model elements. If the element association feature contains a single-cell multi-value association feature (e.g., a lower-level function is assigned to multiple upper-level systems, with the cell separated by a newline character), the server splits it into multiple independent association entries and creates one-to-many allocation relationships in batches accordingly. The hierarchical inclusion relationship and the cross-dimensional allocation relationship are intertwined to form a complete allocation relationship chain.

[0083] For the parsing results of the interface interaction dimension data units, physical connectivity and data flow direction inference are performed. When server 104 recognizes that both local port fields (such as device interface pins) and peer port fields (such as external crosslink pins) exist in the same row of data, it automatically creates physical connection relationships between the corresponding entity model elements (or their subordinate port interaction model elements) based on this co-occurrence feature. Building upon the established physical connection, if the same row of data also contains interaction signal fields and direction flag fields (such as "input / output" flags), the server reads the values ​​of these status flag features. If the first direction is indicated (such as output), a "signal-to-function" dependency relationship is created between the interaction model element and the behavior model element; if the second direction is indicated (such as input), a "function-to-signal" dependency relationship is created. This generates a signal flow transmission relationship with a clear data flow direction. The combination of physical connection relationships and directional signal flow transmission relationships constitutes a complete connection relationship chain.

[0084] Finally, by binding the automatically constructed allocation and connection chains to the endpoints of the behavioral model elements, entity model elements, and interaction model elements in memory, a complete system topology graph is formed. Subsequently, the server persistently saves this topology structure, containing all elements and their relationship chains, to the target model library, thus formally generating the target system model.

[0085] The aforementioned system model generation method, apparatus, computer equipment, computer-readable storage medium, and computer program product receive a system model generation request and obtain a structured data source corresponding to the request. The structured data source includes multiple data units, each carrying data for different architectural dimensions of the system architecture. These architectural dimensions include at least functional logic dimensions, physical component dimensions, and interface interaction dimensions. The method parses the multiple data units to extract element attribute data and element association features. The element attribute data defines model elements within the corresponding architectural dimension. The element association features are determined at least partially based on the reference relationships between the multiple data units and are used to characterize the association relationships between model elements in different architectural dimensions. Based on the element attribute data, model elements are created in the target model storage. These created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension. Based on the element association features, a cross-dimensional relationship chain is established between the created model elements to generate and output the target system model. The cross-dimensional relationship chain includes at least one of the following: an allocation relationship chain between behavioral model elements and entity model elements, and a connection relationship chain between entity model elements and interaction model elements. This application acquires multiple data units that respectively carry different architectural dimensions such as functional logic, physical components, and interface interactions. During parsing, it extracts element association features determined by the reference relationships between these data units. This enables the system to automatically establish cross-dimensional relationship chains while batch-creating model elements in the target model storage. Specifically, this includes at least one of the following: allocation relationship chains between behavioral model elements and entity model elements; and connection relationship chains between entity model elements and interaction model elements. This effectively improves the efficiency of establishing complex system architectural relationships and shortens the modeling time for complex systems. Furthermore, automatically establishing relationship chains based on determined element association features effectively improves the efficiency of system model construction and the accuracy of the topology.

[0086] The element attribute data parsed in this application creates behavioral model elements corresponding to the functional logic dimension, entity model elements corresponding to the physical component dimension, and interaction model elements corresponding to the interface interaction dimension in the target model storage. This allows for the automatic identification and instantiation of different types of heterogeneous model elements based on the attribute characteristics in the multi-dimensional data sub-tables (e.g., automatically instantiating functional data as behavioral blocks, device data as entity blocks, and port data as interaction ports). This breaks the limitation of traditional import tools that can only generate single-type elements, achieving automated classification and batch generation of multiple types of model elements, further shortening the model initialization cycle.

[0087] In an exemplary embodiment, step 203 includes: determining the parsing order according to the data dependencies between multiple data units, and parsing the multiple data units sequentially according to the parsing order; when parsing the current data unit, searching for element attribute data that matches the reference identifier from the previously parsed data units based on the reference identifier in the current data unit, and determining the element association features based on the matching result.

[0088] Specifically, data units can be parsed based on a preset data dependency order. This preset data dependency order refers to the fixed sequence that server 104 must follow when parsing multiple data units. This order is specifically set based on the logical dependency relationship in system engineering: "first define behavior (function), then define carrier (physical), and finally define connectivity (interface)." Based on the architectural dependency order, it can be ensured that when parsing subsequent dimensions, the basic data of previous dimensions are already ready in memory, avoiding dangling references when extracting cross-dimensional relationships.

[0089] The current data unit refers to the specific data unit that the server is currently performing read, traverse, and parse operations on in the parsing order.

[0090] Reference identifiers are identifiers carried in the data record of the current data unit (such as a row of data) that are used to point to, associate with or reference specific data items in other data units (e.g., system name, device number, function ID, etc.).

[0091] Previously parsed data units: refers to data units that are ranked before the current data unit in the parsing order, and that have already been parsed by the server and whose extracted element attribute data has been cached in memory or temporary workspace.

[0092] For example, after obtaining a structured data source containing multiple data units, the server first analyzes the logical support relationships (i.e., data dependencies) between the architectural dimensions carried by each data unit. Based on these dependencies, the server determines a strict parsing order. Subsequently, the server loads and parses the multiple data units sequentially according to this parsing order, and caches the element attribute data extracted in each parsing in memory.

[0093] For the specific parsing process, when the server sequentially parses to a current data unit (e.g., a data unit carrying a physical component dimension), the server not only extracts the element attribute data of the current row but also reads the reference identifier carried in the current row data (e.g., "system name" or "carrying function ID"). Based on this reference identifier, the server actively accesses the cached data of previously parsed data units in memory (e.g., data units carrying a functional logic dimension) to find element attribute data that matches the reference identifier. After finding the matching element attribute data, the server determines the element association features used to characterize the relationships between elements in different architectural dimension models based on this matching result. In this way, the server automatically completes cross-data unit relationship inference and feature extraction while parsing the current data unit.

[0094] In the above embodiments, by determining the parsing order according to the data dependencies between multiple data units and parsing them sequentially, it is ensured that when parsing subsequent data units, the preceding basic data (i.e., previously parsed data units) they depend on are already ready in memory, thus guaranteeing the stability of the data parsing process. Furthermore, by using reference identifiers to find matching element attribute data from previously parsed data units and determining element association features based on the matching results, the server can logically and seamlessly connect discrete attribute data distributed across different data units based on explicit identifier references. This mechanism ensures the accuracy and traceability of cross-dimensional association feature extraction, providing highly reliable data support for the subsequent automatic construction of cross-dimensional model relationship chains.

[0095] In an exemplary embodiment, the parsing order is as follows: parsing data units carrying data in the functional logic dimension, data units carrying data in the physical component dimension, and data units carrying data in the interface interaction dimension; wherein, when parsing data units carrying data in the physical component dimension, the currently parsed physical entity data is matched with previously parsed functional behavior data to obtain element association features representing the association between function and physical allocation; when parsing data units carrying data in the interface interaction dimension, the currently parsed interaction interface data is matched with previously parsed physical entity data to obtain element association features representing the association between physical and interactive connections.

[0096] Functional behavior data refers to the element attribute data extracted from data units carrying the functional logic dimension, used to define the characteristics of model elements such as system function decomposition and behavioral logic. Physical entity data refers to the element attribute data extracted from data units carrying the physical component dimension, used to define the characteristics of physical component model elements such as system hardware devices and software carriers. Interaction interface data refers to the element attribute data extracted from data units carrying the interface interaction dimension, used to define the characteristics of interaction mechanism model elements such as device ports, connectors, and signal flows.

[0097] For example, the server can parse data units in the following order: first, parse data units carrying functional logic dimensions; second, parse data units carrying physical component dimensions; and finally, parse data units carrying interface interaction dimensions.

[0098] When the server parses data units sequentially down to the dimension of the physical component, it first needs to extract the physical entity data (such as device name, hardware model, etc.) from the current data record. Simultaneously, it actively retrieves previously parsed functional behavior data from memory. The server matches the currently parsed physical entity data with the previously parsed functional behavior data, and based on the matching result, obtains the element association features representing the association between function and physical allocation.

[0099] As the server continues parsing sequentially to the data units carrying the interface interaction dimension, it extracts the interaction interface data (such as port number, pin definition, signal name, etc.) from the current data record. Simultaneously, it actively retrieves previously parsed physical entity data from memory (i.e., data extracted from the physical component dimension data units). The currently parsed interaction interface data is then matched with the previously parsed physical entity data (e.g., assigning a specific port or signal to a specific physical device). Based on the matching results, element association features representing the physical-to-interaction connection are obtained.

[0100] In the above embodiments, by limiting the data units to be parsed sequentially for the functional logic dimension, physical component dimension, and interface interaction dimension, the processing logic of complex systems—"first define behavior, then define carrier, and finally define connectivity"—is followed. This ensures that when parsing subsequent dimensions, the underlying data (functional behavior data and physical entity data) of the preceding dimensions are already fully ready in memory, fundamentally avoiding logical inversion or failure to extract related features due to out-of-order parsing. Furthermore, by accurately matching the preceding functional behavior data when parsing the physical component dimension and the preceding physical entity data when parsing the interface interaction dimension, the server can provide direct and reliable data support for the subsequent automated construction of highly accurate system allocation and connection relationship chains based on a clear data dependency chain. This effectively avoids the technical defects of incorrect or missing cross-dimensional relationships in complex system modeling.

[0101] In an exemplary embodiment, extracting element association features includes: identifying a preset delimiter within a cell of a data unit; splitting multi-entry data within a cell into multiple independent associated entries based on the preset delimiter; and using the multiple independent associated entries as independent relation endpoints to establish a one-to-many allocation relation chain and / or connection relation chain.

[0102] A preset separator is a predefined specific character or combination of characters used to distinguish and isolate multiple independent data items within a single data cell in a spreadsheet. In one embodiment, the preset separator is a newline character, while in another embodiment, the preset separator may be other conventional symbols such as commas or semicolons.

[0103] Multi-entry data refers to a collection of multiple data values ​​or text strings connected together within the same cell of a structured data source using a preset delimiter. Independent related entries, on the other hand, refer to atomic data items with a single, clearly defined semantic meaning, separated from the multi-entry data after splitting. Each independent related entry can be used independently to trigger and establish a model relationship in subsequent processing.

[0104] One-to-many refers to a system model topology in which there is an association mapping relationship between a source model element and multiple target model elements. For example, a lower-level function is assigned to multiple upper-level systems at the same time, or a physical device port is simultaneously linked to multiple external signals.

[0105] For example, this application can also utilize a preset delimiter to achieve one-to-many association processing. First, during the parsing of functional architecture data units (such as "functional architecture templates") or interface interaction data units (such as "device function and interface crosslinking templates"), the server traverses the data line by line, focusing on specific association columns, such as the cell content of the parent function column, allocation system column, or external crosslinking pin column in the data unit. Then, it reads the string within the cell and checks whether it contains a preset delimiter. When the server detects the presence of a preset delimiter in a single cell, it triggers data splitting logic. Based on the preset delimiter as the cutting point, the multi-entry data (i.e., a long string of text containing multiple values) within a single cell is split and separated into multiple independent association entries. For example, if a cell stores the three names "System A," "System B," and "System C" using line breaks, it will be directly split into three independent string objects, resulting in three independent association entries. Finally, after the splitting is complete, the server stores the resulting multiple independent association entries into an association feature queue in memory. In the subsequent relation mapping stage, each independent association entry will be treated as an independent relation endpoint. Based on this, the server addresses and binds multiple target elements (such as system A, system B, and system C) for the source element (such as a device-level function) of the current row, thereby accurately representing and instantiating the one-to-many function-to-physical allocation association, or the one-to-many physical-to-interaction connection association at the underlying data logic.

[0106] In the above embodiments, by using a preset delimiter to store multiple data entries within a single cell and programmatically splitting them, the traditional table's error-prone, data-structurally corrupting, and difficult-to-read merged cell formatting method is completely replaced. This improves the success rate, stability, and processing efficiency of parsing complex table data. Furthermore, by splitting multiple data entries into multiple independent related entries, the server can directly and accurately create one-to-many assignment or connection relationships in batches based on these atomic independent entries. This enhances the completeness of one-to-many topological relationships in complex system models and effectively avoids the problem of missing or incorrect relationship creation due to limitations in data representation.

[0107] In an exemplary embodiment, the element association feature includes a direction marker feature; based on the element association feature, a cross-dimensional relationship chain is established between the created model elements, including: when the direction marker feature indicates a first direction, a first dependency relationship is established between the interaction model element and the behavior model element;

[0108] When the directional marker feature indicates a second direction, a second dependency is established between the behavior model element and the interaction model element. The direction of the second dependency is opposite to that of the first dependency.

[0109] Here, the direction marker feature refers to the status identifier data extracted from the data unit (especially the data unit carrying the interface interaction dimension) to indicate the direction of data flow, signal transmission, or control logic. The first direction and the second direction refer to two mutually exclusive logical directions that the direction marker feature can indicate. For example, the first direction can represent "output" and the second direction can represent "input".

[0110] For example, in the process of establishing a cross-dimensional relationship chain based on element association features, the server first identifies the direction marker feature from the extracted element association features. This feature typically originates from a specific field in the data unit carrying the interface interaction dimension (such as the "input / output" flag in the current row of data). The server reads the specific value of this flag to determine the direction indicated by the current data record. Then, the value of the direction marker feature is logically judged. If it is determined that the direction marker feature indicates a first direction (e.g., indicating "output"), the server establishes a first dependency relationship between the created interaction model element (such as a signal element) and the behavior model element (such as a function element). At this time, the direction of this dependency relationship is from the interaction model element to the behavior model element (i.e., the signal is output to the function).

[0111] If a directional indicator suggests a second direction (e.g., "input"), the server needs to establish a second dependency between the existing behavioral model elements (e.g., functional elements) and interaction model elements (e.g., signal elements). Since the second direction is mutually exclusive with the first direction, the second dependency constructed by the server is strictly opposite in direction to the first dependency (i.e., it points from the behavioral model element to the interaction model element, indicating function generation / input signal).

[0112] In the above embodiments, by introducing directional marker features into the element association features, the server can automatically determine and establish the dependency relationship between interaction model elements and behavior model elements based directly on the state identifiers in the underlying data. By distinguishing between the first direction and the second direction, and establishing first and second dependency relationships with completely opposite directions, it ensures that the input / output logic between interaction model elements (such as signals) and behavior model elements (such as functions) is realistically and accurately reproduced in the model topology.

[0113] In an exemplary embodiment, step 205 includes: determining the root node for creating model elements in the target model storage based on a preset target storage path, and generating a corresponding tree-like organizational package structure under the root node; during the creation of model elements, when it is detected that the model element to be created has an identifier conflict with an existing model element in the target model library, performing a new creation operation or an update operation based on a duplicate model processing strategy to obtain the processed model element; and assigning the processed model element to the package node corresponding to the tree-like organizational package structure to obtain behavioral model elements corresponding to the functional logic dimension, entity model elements corresponding to the physical component dimension, and interactive model elements corresponding to the interface interaction dimension.

[0114] The target storage path refers to the starting directory or namespace path specified by the user through the configuration interface or set by the system default, used to store the model elements generated in this import in the target model library.

[0115] The root node refers to the highest-level container or starting package located in the target model library based on the target storage path. It is the starting point for this batch model creation operation.

[0116] A tree-like package structure refers to a directory tree structure with logical hierarchy (such as the Package hierarchy in SysML) that is automatically deduced and dynamically generated by the server based on the business hierarchy attributes (such as system name, device name, functional level, etc.) of model elements under the creation of the root node.

[0117] Identifier conflict refers to a data state where the model element to be created and the model element already existing in the target model library have the same or overlapping unique business identifiers (such as name, LIN number, ATA chapter number, etc.).

[0118] The duplicate model handling strategy refers to the pre-configured control rules that guide the server on how to handle conflicting data when an identifier conflict occurs. It mainly includes new creation operations (such as renaming and then creating a new one to retain historical versions) and update operations (overwriting the attributes of existing elements).

[0119] The processed model element is a final, state-defined model element instance generated after the identification conflict detection and the execution of the new or update operation.

[0120] For example, in the scheme of this application, for model elements, the model is not simply created under the root package selected by the user, but an organized package structure is automatically generated according to the business hierarchy. For this process, the server first obtains the preset target storage path and addresses it in the target model storage to determine the root node for creating the model element. Subsequently, the server does not simply stack elements flatly under the root node, but dynamically generates the corresponding tree-like organized package structure under the root node based on the business hierarchy information carried in the parsed element attribute data. For example, the server automatically constructs a hierarchical path of "target package::function::device-level function::[specific system name]" or "target package::physical::[specific device name]", providing a framework for the precise aggregation of subsequent elements.

[0121] Meanwhile, during the process of traversing element attribute data to prepare for model element instantiation, the server also performs real-time deduplication checks. If a conflict is detected between the currently created model element and an existing model element in the target model library (e.g., duplicate name or LIN number), a preset duplicate model handling strategy is invoked. If the strategy is "create new," the server generates a new model instance (e.g., automatically renames it); if the strategy is "update," the server extracts the current element attribute data and overwrites the attributes of the existing model element. After the "create new" or "update" operation, a processed model element with a determined status is obtained.

[0122] Finally, after obtaining the processed model elements, the server precisely categorizes them into the corresponding package nodes of the dynamically generated tree-like organizational package structure. Through this aggregation process, the server formally completes the classification and instantiation in the target model library, ultimately obtaining behavioral model elements corresponding to the functional logic dimension (such as functional blocks categorized under functional packages), entity model elements corresponding to the physical component dimension (such as device blocks categorized under physical packages), and interaction model elements corresponding to the interface interaction dimension (such as ports or signals categorized under interface packages). In one embodiment, this application is used to create complex models related to aircraft design; in this case, the automatically generated schematic diagram of the model package structure can be referenced. Figure 3 As shown, they can be divided into function packages and system packages. Function packages contain system function information related to aircraft-level functions and software functions. System packages contain information such as relationships, transit items, equipment, and resident software.

[0123] In the above embodiments, by dynamically generating corresponding tree-like organizational packages under the root node and assigning processed model elements to the corresponding package nodes, the batch-created model elements can be automatically categorized and stored according to business logic. This avoids the chaotic, flat stacking of elements in the model library, improving the organization, readability, and efficiency of subsequent model retrieval and maintenance. By detecting identifier conflicts in real time during the creation process and flexibly executing new creation or update operations based on duplicate model handling strategies, the system can intelligently and properly handle duplicate or legacy data in the data source. This ensures the accuracy and consistency of the attributes of the finally generated model elements. By grouping the processed model elements by dimension, the system can automatically and simultaneously create and organize three types of heterogeneous elements: behavioral model elements, entity model elements, and interaction model elements, effectively improving the processing efficiency of model generation and shortening the processing cycle for complex model generation.

[0124] In an exemplary embodiment, the element association features include local port features, peer port features, and interaction signal features; establishing a connection relationship chain based on the element association features includes: establishing a connection relationship between port model elements associated with entity model elements based on the local port features and peer port features that appear together in the same data row; and binding the corresponding signal stream to the established connection relationship based on the interaction signal features.

[0125] Among them, the local port feature refers to the data features extracted from the data unit that characterize the interface port attributes of the current physical component (such as a device) itself (e.g., local device name, local connector number, local pin number, etc.). The remote port feature refers to the data features extracted from the data unit that characterize the interface port attributes of the external physical component that performs physical connection or data interaction with the current physical component (e.g., external crosslinking device name, remote connector number, remote pin number, etc.). The interaction signal feature is the data feature extracted from the data unit that characterizes the specific data content, electrical signal, or protocol type actually transmitted between physical ports (e.g., signal name, data packet name, etc.).

[0126] For example, in the process of establishing a connection chain, the server traverses the data rows of data units to identify and extract the local and remote port features that co-occur within the current data row. This data structure feature of "co-occurrence within the same data row" (i.e., co-occurrence within the same row) is used by the server as the direct basis for triggering the establishment of physical connection relationships. Then, based on the identified local and remote port features that co-occur within the same row, the server locates the corresponding entity model elements (i.e., local and remote physical devices) in the target model storage, and further locates the port model elements (i.e., local and remote ports) associated with these entity model elements. A connection relationship is then automatically established between these two port model elements, thereby constructing the physical connectivity topology between physical components at the model's underlying layer. After successfully establishing the connection relationship between ports, the server continues to read the interaction signal features (such as signal names) in the current data row. Based on these interaction signal features, the server automatically binds the corresponding signal stream to the newly established connection relationship. This action concretizes the abstract physical connection relationship into a logical channel with clear data transmission semantics, completing the full modeling from "physical connectivity" to "data interaction."

[0127] In the above embodiments, by establishing connection relationships based on the local and remote port characteristics that co-occur within the same data row, the server can directly utilize the "co-occurrence in the same row" mechanism of table data to automatically and accurately infer and instantiate the physical connection topology between physical component ports, effectively improving the efficiency and accuracy of physical architecture modeling. After establishing the connection relationship, the corresponding signal flow is immediately bound to the connection relationship based on the interaction signal characteristics, ensuring that the target system model not only has the correct physical connection skeleton but also complete and accurate underlying data interaction semantics, effectively avoiding the omission or misbinding problems that are easily caused when manually separating and configuring connections and signal flows.

[0128] In an exemplary embodiment, the method further includes: obtaining model import configuration parameters in response to interactive operations of the configuration interface; and determining the target storage path and duplicate model processing strategy based on the model import configuration parameters.

[0129] The configuration interface refers to the graphical user interface (GUI), web form, or plugin dialog box provided to users. It is used to collect users' customized settings for the model import process before initiating the system's automated model building process. A diagram of the configuration interface can be found in [link to diagram]. Figure 4 As shown, users can upload the corresponding architecture Excel file through the configuration interface and specify the corresponding target storage path and duplicate model handling strategy.

[0130] Interactive operations refer to actions performed by the user on the configuration interface, such as inputting, selecting, checking, or clicking. Figure 4In the interface, select the path in the "Target Location" drop-down box, select "New Model" or "Update Model" in the "Repeated Model Processing" radio button, and click the "Import" button, etc.

[0131] Model import configuration parameters refer to the set of data or variables collected by the server through the configuration interface, used to globally control the model import and creation behavior. The duplicate model handling strategy, determined by the configuration parameters, is the control rule (such as creation or update) that guides the server on how to handle conflicting data when model identifier conflicts occur.

[0132] For example, the server can initiate the system model generation process by receiving interactive operation events from the client's configuration interface. When the user completes the relevant settings on the configuration interface and triggers the import command (e.g., clicking the "Import" button on the interface), the server responds to the interactive operation by receiving and obtaining the model import configuration parameter data packet transmitted from the front end. Then, the server parses the obtained model import configuration parameters and extracts the path configuration items (e.g., the model package path selected by the user in the "Target Location" control). The server converts this path configuration item into an absolute path, node identifier, or namespace that can be recognized by the underlying target model library, thereby accurately determining the target storage path for this model creation.

[0133] In addition, the server also needs to parse the model import configuration parameters, extract the conflict handling configuration items, and map the option to the system's internal preset conflict handling logic rules (such as triggering renaming and creation logic, or triggering attribute overwrite and update logic), so as to accurately determine the duplicate model handling strategy for this import process, which can be called by subsequent model creation steps.

[0134] In this embodiment, model import configuration parameters are obtained through interactive operations in response to the configuration interface. This allows users to customize import behavior through an intuitive graphical interface without modifying underlying code, scripts, or manually adjusting table structures. This significantly lowers the barrier to entry for the system and improves the processing efficiency of model generation. Furthermore, accurately determining the target storage path and duplicate model handling strategy based on the model import configuration parameters ensures that the server strictly adheres to user-defined rules during subsequent batch creation and conflict handling, guaranteeing the security, standardization, and high controllability of model library management.

[0135] In an exemplary embodiment, the method further includes: generating corresponding model visualization views and data statistics matrices based on system model elements and model relationship chains; rendering and displaying the model visualization views to present the hierarchical inclusion relationships and internal physical interaction topology of system model elements; and verifying the allocation integrity between functional logic dimensions and physical component dimensions based on the data statistics matrix, and generating model traceability verification results.

[0136] Among them, the model visualization view refers to the graphical representation carrier automatically generated based on the system model elements and their relationship chains (in the SysML context, it can be specifically represented as Block Definition Graph (BDD), Internal Block Graph (IBD), etc.), which is used to transform the abstract model data structure into a human-readable graphical topology.

[0137] A data statistics matrix is ​​a two-dimensional cross table (such as a function and physical allocation matrix) automatically generated based on system model elements and their relationship chains. It is used to quantitatively and structurally display the mapping and association status between model elements of different dimensions.

[0138] Hierarchical inclusion relationships refer to the hierarchical and subordinate structures formed between system model elements based on logical or physical levels (such as a system containing subsystems, and subsystems containing devices), which are usually presented in block definition diagrams (BDDs).

[0139] Internal physical interaction topology refers to the physical connectivity and data transmission network structure established within or between physical component-level model elements (such as devices) through interaction model elements (such as ports and connectors), and is usually presented in the internal block diagram (IBD).

[0140] Model traceability verification results refer to the structured reports or status identifiers generated after integrity verification, which are used to indicate the health of the model's cross-dimensional traceability links.

[0141] For example, after generating the model, to ensure its visibility, the built-in view and matrix generation engine can be invoked. The server reads the persistent system model elements and model relationship chains from the target model library, and automatically generates the corresponding model visualization view (such as generating the underlying graphical description data of BDD and IBD diagrams) and data statistics matrix based on preset graphical layout algorithms and matrix construction rules. The underlying graphical description data of the generated model visualization view is sent to the client's graphics rendering engine (or rendered directly as an image stream by the server). Through rendering and display operations, the hierarchical containment relationship of system model elements (such as displaying the hierarchical combination structure from system to device through a BDD diagram) and the internal physical interaction topology (such as displaying the connectors and signal flow between device ports through an IBD diagram) are intuitively presented on the user terminal's display interface. In addition, the data verification engine is invoked, and based on the data statistics matrix (such as a function-physical allocation matrix), the cross cells in the matrix are automatically traversed to verify the completeness of the allocation between the functional logic dimension and the physical component dimension. Specifically, the server checks the matrix for completely empty rows (i.e., a functional logical element is not assigned to any physical component) or completely empty columns (i.e., a physical component element does not carry any function). Based on the results of the traversal verification, the server automatically generates model traceability verification results.

[0142] In the above embodiments, a model visualization view is automatically generated based on system model elements and model relationship chains, and rendered to present the hierarchical containment relationship and internal physical interaction topology. This allows users to directly obtain a clear and accurate architecture drawing that reflects the underlying model data without having to perform tedious manual graphic layout and connection arrangement in modeling tools, thereby effectively improving the visualization level of the system model and the efficiency of engineering communication.

[0143] In one specific embodiment, this application is applied to an aircraft design system, where the workflow for submitting structured data can be referred to... Figure 5 As shown, the designer first needs to select the Excel file to be uploaded, then the Excel parsing module parses the file, the designer previews the parsing results, and then proceeds to... Figure 4 The user can access the import configuration interface, configure the import configuration items within the interface, and then submit the configuration items. The model creation module will then create the model according to the user's configuration items.

[0144] The multi-sheet template data processing workflow can be referenced. Figure 6 As shown, there are three main processes processed sequentially: functional architecture template processing flow, physical architecture template processing flow, and device function and interface cross-linking template processing flow.

[0145] For the specific system model generation and execution process, the initial stage requires the user to import an Excel file. The Excel file is then parsed, the sheet type is identified, and the appropriate processing flow is routed based on the type (functional architecture template, physical architecture template, device function and interface interaction template). Upon receiving the import request, the server loads the Excel file and, by recognizing the sheet name or header characteristics, accurately maps different worksheets to preset architectural dimensions (functional logic dimension, physical component dimension, interface interaction dimension). This sheet-type-based routing and distribution mechanism achieves multi-dimensional decoupling of complex system architectures at the data source, laying the foundation for subsequent sequential processing according to dependencies.

[0146] For the functional architecture template processing flow, this process first requires performing template invalidation validation. If it fails, the process terminates and the error is logged. If it passes, the processes of model creation, relationship creation, and interface / view creation are executed sequentially. The processing flow for physical architecture templates and device function and interface crosslinking templates is similar. The difference lies in that model creation for functional architecture templates is responsible for creating the system, physical devices, and functions; relationship creation is responsible for directional combination and allocation relationships; and view creation creates the Functional Decomposition Diagram (BDD) and allocation matrix. For physical architecture templates, model creation is responsible for creating connectors, pins, and signals; relationship creation is responsible for connection relationships and ICD item flows; and view creation creates the Internal Block Diagram (IBD) and item flow statistics graph. For device function and interface crosslinking templates, model creation is responsible for creating functions and signals; relationship creation is responsible for allocation relationships and dependencies; and view creation creates a function-signal dependency graph.

[0147] Finally, after all processing is complete, a complete SysLM model can be generated.

[0148] The flowchart for creating the model relationships can be found by referring to... Figure 7 As shown, when processing the current row of data in Excel, it is necessary to first identify the template type to which the data belongs. Then, based on the template type, it enters the functional architecture relationship creation process, physical architecture relationship creation process, or signal-function dependency relationship creation process. After completing the creation based on the template, it is necessary to check whether there is a relationship of the same type between the source and target models in the relationship for verification. If so, the creation is skipped to prevent duplication. If not, the corresponding relationship element is created in the SysLM model. Then, the next row of data is processed until all data rows are processed, and the creation result of the current template relationship is obtained. The diagram clearly depicts the following path: parsing table row data -> identifying data relationships (such as system name and device name in the same row) -> querying or creating corresponding model elements -> according to predefined rules (such as combination, allocation) -> creating SysML relationship chains between model elements.

[0149] For the creation process of various template relationships, the creation process of functional architecture template relationships can be referenced. Figure 8 As shown, this process requires determining the relationship type based on the column data, and then creating the corresponding directional combination relationship or assignment relationship.

[0150] The process for creating physical architecture template relationships can be referenced. Figure 9 As shown, it is necessary to determine the relationship type based on the column data, and then create the corresponding connection relationship, directed combination relationship, or dependency relationship. During the connection relationship creation process, the ICD relationship creation process is executed based on the existence of signal name data. The process for creating device function and interface crosslink template relationships can be referenced. Figure 10As shown, this process mainly requires creating corresponding dependencies based on the values ​​of the "input / output" fields.

[0151] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0152] Based on the same inventive concept, this application also provides a system model generation apparatus for implementing the system model generation method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more system model generation apparatus embodiments provided below can be found in the limitations of the system model generation method described above, and will not be repeated here.

[0153] In one exemplary embodiment, such as Figure 11 As shown, a system model generation device is provided, comprising:

[0154] The data acquisition module 1102 is used to receive system model generation requests and acquire structured data sources corresponding to the system model generation requests. The structured data sources include multiple data units, which respectively carry data of different architectural dimensions of the system architecture. The architectural dimensions include at least functional logic dimensions, physical component dimensions, and interface interaction dimensions.

[0155] The data table parsing module 1104 is used to parse multiple data units and extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions.

[0156] The element generation module 1106 is used to create model elements in the target model storage based on element attribute data. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension.

[0157] The system model generation module 1108 is used to establish cross-dimensional relationship chains between created model elements based on element association features, and generate and output the target system model; the cross-dimensional relationship chain includes at least one of the following: the allocation relationship chain between behavioral model elements and entity model elements, and the connection relationship chain between entity model elements and interaction model elements.

[0158] In one embodiment, the data table parsing module 1104 is specifically used to: determine the parsing order according to the data dependency relationship between multiple data units, and parse multiple data units sequentially according to the parsing order; when parsing the current data unit, search for element attribute data that matches the reference identifier in the previously parsed data units according to the reference identifier in the current data unit, and determine the element association features according to the matching result.

[0159] In one embodiment, the parsing order is to parse the data units carrying data of the functional logic dimension, the data units carrying data of the physical component dimension, and the data units carrying data of the interface interaction dimension in sequence. The data table parsing module 1104 is further configured to: when parsing the data units carrying the physical component dimension, match the currently parsed physical entity data with the previously parsed functional behavior data to obtain element association features representing the association between function and physical allocation; when parsing the data units carrying the interface interaction dimension, match the currently parsed interaction interface data with the previously parsed physical entity data to obtain element association features representing the association between physical and interactive connections.

[0160] In one embodiment, the data table parsing module 1104 is specifically used to: identify a preset delimiter within a cell of a data unit; based on the preset delimiter, split the multi-entry data within the cell into multiple independent related entries; and use the multiple independent related entries as independent relation endpoints to establish a one-to-many allocation relation chain and / or connection relation chain.

[0161] In one embodiment, the system model generation module is specifically used to: establish a first dependency relationship between interaction model elements and behavior model elements when the direction marker feature indicates a first direction; and establish a second dependency relationship between behavior model elements and interaction model elements when the direction marker feature indicates a second direction, wherein the direction of the second dependency relationship is opposite to that of the first dependency relationship.

[0162] In one embodiment, the system model generation module is specifically used to: establish a connection relationship between port model elements associated with entity model elements based on the local port features and peer port features that appear together in the same data row; and bind the corresponding signal stream to the established connection relationship based on the interaction signal features.

[0163] Each module in the aforementioned system model generation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0164] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 12 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data related to system model generation. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a system model generation method.

[0165] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 13As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a system model generation method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0166] Those skilled in the art will understand that Figure 12 and Figure 13 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0167] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0168] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0169] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the steps in the above-described method embodiments.

[0170] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0171] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0172] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0173] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for generating a system model, characterized in that, The method includes: Receive a system model generation request and obtain a structured data source corresponding to the system model generation request; the structured data source includes multiple data units, each of which carries data of different architectural dimensions of the system architecture, and the architectural dimensions include at least functional logic dimension, physical component dimension and interface interaction dimension; The multiple data units are parsed to extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions. Based on the element attribute data, the model elements are created in the target model storage. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension. Based on the element association features, a cross-dimensional relationship chain is established among the created model elements to generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

2. The method according to claim 1, characterized in that, The step of parsing the multiple data units and extracting element attribute data and element association features includes: The parsing order is determined according to the data dependencies between the multiple data units, and the multiple data units are parsed sequentially according to the parsing order; When parsing the current data unit, based on the reference identifier in the current data unit, the element attribute data that matches the reference identifier is searched from the previously parsed data units, and the element association feature is determined based on the matching result.

3. The method according to claim 2, characterized in that, The parsing order is to parse the data unit carrying the data of the functional logic dimension, the data unit carrying the data of the physical component dimension, and the data unit carrying the data of the interface interaction dimension in sequence. Specifically, when parsing data units carrying data of the physical component dimension, the currently parsed physical entity data is matched with previously parsed functional behavior data to obtain element association features representing the association between function and physical allocation; when parsing data units carrying data of the interface interaction dimension, the currently parsed interaction interface data is matched with previously parsed physical entity data to obtain element association features representing the association between physical and interactive connections.

4. The method according to claim 1, characterized in that, The extracted element association features include: Identify the preset separator within the cell of the data unit; Based on the preset separator, the multi-entry data in the cell is split into multiple independent related entries; Each of the multiple independent associated entries is used as an independent relation endpoint to establish a one-to-many allocation relation chain and / or connection relation chain.

5. The method according to claim 1, characterized in that, The element association features include directional marker features; the step of establishing cross-dimensional relationship chains among the created model elements based on the element association features includes: When the directional marker feature indicates a first direction, a first dependency relationship is established between the interaction model element and the behavior model element; When the direction marker feature indicates a second direction, a second dependency is established between the behavior model element and the interaction model element, the second dependency being in the opposite direction to the first dependency.

6. The method according to claim 1, characterized in that, The element association features include local port features, peer port features, and interaction signal features; establishing the connection relationship chain based on the element association features includes: Based on the local port feature and the peer port feature that appear together in the same data row, establish a connection relationship between the port model elements associated with the entity model element; Based on the characteristics of the interaction signals, the corresponding signal streams are bound to the established connection relationships.

7. A system model generation device, characterized in that, The device includes: The data acquisition module is used to receive system model generation requests and acquire structured data sources corresponding to the system model generation requests. The structured data sources include multiple data units, which respectively carry data of different architectural dimensions of the system architecture. The architectural dimensions include at least functional logic dimensions, physical component dimensions, and interface interaction dimensions. The data table parsing module is used to parse the multiple data units and extract element attribute data and element association features; the element attribute data is used to define model elements under the corresponding architecture dimension; the element association features are determined at least in part based on the reference relationship between the multiple data units and are used to characterize the association relationship between model elements in different architecture dimensions. The element generation module is used to create the model elements in the target model storage based on the element attribute data. The created model elements include behavioral model elements associated with the functional logic dimension, entity model elements associated with the physical component dimension, and interaction model elements associated with the interface interaction dimension. The system model generation module is used to establish cross-dimensional relationship chains among the created model elements based on the element association features, and generate and output the target system model; the cross-dimensional relationship chain includes at least one of the allocation relationship chain between the behavior model element and the entity model element, and the connection relationship chain between the entity model element and the interaction model element.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.