Novel function virtual prototype model system capable of achieving distributed simulation

Abstract

The invention belongs to the technical field of system design and simulation based on models, and particularly relates to a novel function virtual prototype model system capable of achieving distributed simulation. Comprising a demand analysis chart used for importing system demands; the product is decomposed into a structure chart, functions required by the system and physical entities with bearing functions are summarized according to the analysis result of the demand analysis chart, and the hierarchical relation of the physical entities is displayed in a tree structure; the physical topological graph is used for displaying an interface connection relationship and a data transmission relationship among the physical entities and corresponds to the product decomposition structure graph; the use case graph is used for bearing functions obtained through demand analysis by use of use cases according to an analysis result of the demand analysis graph; the activity graph is used for describing function logic of the system; the data model graph is used for defining a data structure body and members thereof, binding basic data types and forming a unified data carrier; and the software scheduling graph is used for configuring an operation relation of software which resides on the physical entity and realizes corresponding functions.

Description

Technical Field

[0001] This invention belongs to the field of model-based system design and simulation technology, and specifically relates to a novel functional virtual prototype model system capable of distributed simulation. Background Technology

[0002] Model-based systems engineering addresses many problems inherent in traditional document-driven design methods by replacing static documents with models. SysML, currently the most widely used standard modeling language in model-based systems engineering, provides nine diagram types: requirement diagrams, use case diagrams, block definition diagrams, internal block diagrams, activity diagrams, state machine diagrams, sequence diagrams, communication diagrams, and parameter diagrams. In real-world projects, limitations such as functionality, cost, and efficiency often prevent the creation of all nine diagram types, and some project requirements cannot be expressed using these nine types. Therefore, a new functional virtual prototype model architecture suitable for engineering projects and capable of fully encompassing project information is needed. Summary of the Invention

[0003] The purpose of this invention is to provide a novel functional virtual prototype model system capable of distributed simulation, comprising a requirements analysis diagram, a product breakdown structure diagram, a physical topology diagram, a use case diagram, an activity diagram, a data model diagram, and a software scheduling diagram. Starting with requirements analysis, the system functions are decomposed and summarized, and these functions are allocated to physical units. The relationships between these physical units are clarified to determine the physical topology. Simultaneously, use cases in the use case diagram are mapped one-to-one with system functions. The activity diagram represents the functional logic and decomposes the functions, establishing the functional logic of the system's internal components and lower-level subsystems and devices. The system's data structure diagram is defined as the interface specification for information interaction, and the system's software scheduling diagram is defined to express the scheduling relationships of the functional software. Finally, the system model, which integrates the aforementioned functional logic, interface specifications, software scheduling relationships, and hardware carrier topology relationships, can undergo distributed simulation. In a virtual environment, the system can be dynamically verified, its performance analyzed, and iteratively optimized, thereby achieving integration from design to verification.

[0004] Technical solution: A novel functional virtual prototype model system capable of distributed simulation includes: Requirements analysis diagrams are used to import system requirements and present them to designers in the form of charts, so that designers can decompose and summarize the requirements to form the functional requirements of the system. The product breakdown structure diagram, based on the analysis results of the requirements analysis diagram, summarizes the functions required by the system and the physical entities that need to support the functions to realize the system functions, and displays the hierarchical relationship of the physical entities in a tree structure. The physical topology diagram shows the interface connection relationships and data transmission relationships between various physical entities, which corresponds to the product breakdown structure diagram. Use case diagrams are based on the analysis results of requirements analysis diagrams, using use cases to carry the functions obtained from requirements analysis, with each use case corresponding to one function; Activity diagrams are used to describe the functional logic of a system. One use case corresponds to one activity diagram. Functional units are assigned through physical entities, and data flow, control flow, and activities are defined. Logical data structures are built on the data flow. A data model diagram is used to define data structures and their members, bind basic data types, and form a unified data carrier. A software scheduling diagram is used to configure the operational relationships of software that resides on physical entities and performs corresponding functions.

[0005] Furthermore, the requirements analysis diagram includes four types of elements: requirement ID, requirement name, requirement content, and requirement type.

[0006] Furthermore, the product breakdown structure diagram is used to define the hierarchical relationships within the system.

[0007] Furthermore, the system requirements are divided into the following categories, each corresponding to a type of physical entity, as detailed below: a) Data processing class: Possesses data processing capabilities and has a CPU; b) Video processing: Possesses video processing capabilities and a GPU; c) Display-type: Capable of displaying complex images, equipped with a display screen; d) Display and control class: It has simple screen display capabilities, data input capabilities, and a display screen and keyboard; e) Data acquisition type: Capable of collecting various types of data, serving as sensors; f) Data routing class: It has bus data conversion and input / output capabilities and is adaptable to multiple buses; g) Data storage: Possesses audio and video data storage capabilities and has a large-capacity memory card.

[0008] Furthermore, the physical topology graph contains the following information: a) Models and attributes of each level of system, subsystem, device, and software; b) The interfaces and types of each level of the system to the outside world; c) The bus components included in the system and their configuration; d) The connection relationship between the interfaces at each level of the system and the bus components; e) Data structure transmitted on interfaces at each level of the system.

[0009] Furthermore, the activity graph is implemented using the standard SysML language.

[0010] Furthermore, the specific steps for constructing an activity graph are as follows: 1) Define the purpose and scope; 2) Identify the main actions; 3) Establish an action sequence; 4) Add decision-making and merging; 5) Handling concurrency and synchronization; 6) Define the inputs and outputs; 7) Divide physical entities.

[0011] Furthermore, in order to simulate the operation of the functional logic, the input and output interfaces of each activity in the activity diagram are bound to the data structure, and also to the data transmission bus; the physical entity to which the activity belongs, the bus component for transmission, the data transmitted through the interface, etc., correspond one-to-one with the connections in the physical topology diagram.

[0012] Furthermore, the interaction of signals in the system is carried out through data structures and transmitted in the data bus.

[0013] Furthermore, the software scheduling graph includes runtime, priority, and resident partition information.

[0014] Beneficial effects: This invention provides a novel functional virtual prototype model architecture that can be distributed for simulation.

[0015] 1. Incorporate physical topology into the model: The introduction of physical topology corresponds the model to the actual system, enabling the logical model to be linked with physical entities.

[0016] The physical topology diagram contains information such as the device itself, the interfaces of the device, and the data structure transmitted on the device interfaces, enabling the model to be combined with the physical object for simulation.

[0017] The physical topology diagram can be further extended to reveal many attributes of the device, truly realizing the complete digitization of the actual system with a functional virtual prototype.

[0018] 2. Multi-level system modeling architecture: Physical architecture design layer: used to define the hierarchical relationship of the system and support rapid verification of the rationality of the architecture.

[0019] Physical topology design layer: synthesizes logical interfaces into physical interface data and supports the automatic generation and mapping of bus messages.

[0020] Data model design layer: Based on structures, it supports multi-level nesting and ensures consistency between logical interfaces and physical messages.

[0021] Functional modeling and design layer: Decomposes relationships through swimlane mapping architecture and assigns functional units to lower-level systems / devices.

[0022] 3. Automatic conversion mechanism from logic to physical: It supports the automatic generation of bus messages in the physical topology from the logical data structure in the functional modeling diagram, ensuring the consistency and traceability of data flow.

[0023] It provides automatic merging and mapping of logical data structures to physical data structures.

[0024] 4. Distributed simulation and closed-loop verification process: It supports performing simulations in a distributed environment to simulate data transmission across systems / devices.

[0025] After the simulation is completed, an analysis report is automatically generated, supporting data visualization and performance evaluation, forming a closed loop of "modeling-simulation-optimization". Attached Figure Description

[0026] Figure 1 Architecture diagram of the new functional virtual prototype model; Figure 2 Requirements analysis diagram; Figure 3 Product breakdown diagram; Figure 4 Physical topology diagram; Figure 5 Use case diagram; Figure 6 Activity diagram; Figure 7 Data model diagram; Figure 8 Software scheduling diagram. Detailed Implementation

[0027] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0028] In this application, the terms "upper," "lower," "left," "right," "front," "rear," "top," "bottom," "inner," "outer," "middle," "vertical," "horizontal," "lateral," and "longitudinal" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. These terms are primarily for the purpose of better describing this application and its embodiments, and are not intended to limit the indicated device, element, or component to having a specific orientation, or to be constructed and operated in a specific orientation.

[0029] Furthermore, the terms "installation," "setup," "equipped with," "connection," "linking," and "socketing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral structure; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium, or an internal connection between two devices, components, or parts. Those skilled in the art can understand the specific meaning of these terms in this application based on the specific circumstances.

[0030] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0031] The novel functional virtual prototype model architecture for distributed simulation proposed in this invention is as follows: Figure 1 As shown, starting with the decomposition of user needs, the decomposed sub-functions reside in different products according to their categories, leading to a product decomposition structure diagram. The decomposed sub-functions are represented by use case diagrams, the detailed function flows of each use case are represented by activity diagrams, and the data flows passed within these function flows are represented by data model diagrams. The composition of products, their connections, and the data structures transmitted between products are summarized in a physical topology diagram, providing a clear visual representation for designers. This diagram can also be transformed into a system model capable of combining virtual and physical simulations. Finally, the scheduling relationships of functions on hardware resources are displayed by a software scheduling diagram.

[0032] The new functional virtual prototype model architecture fully demonstrates information at all levels of the system, with each component working in tandem. The specific meanings of each component are as follows: 1. Requirements Analysis Diagram Requirements analysis diagrams are used to import system requirements and present them to designers in a graphical format. This allows designers to break down and summarize the requirements, forming the system's functional and performance requirements. A requirements analysis diagram includes elements such as requirement ID, requirement name, requirement content, and requirement type. An example is shown below. Figure 2 .

[0033] Taking avionics systems as an example, if the requirement is "to have basic flight information display functions", after importing, the requirement ID is 1, the requirement content is "to have basic flight information display functions", and the requirement type is functional requirement. Decomposing the requirement yields two functions: "screen display" and "data acquisition". Implementing this function implicitly involves "data processing".

[0034] 2. Product Explosion-Out Structure Diagram Product breakdown structure (BBS) is used to define the hierarchical relationships within a system. Based on the requirements analysis, the required functions of the system are summarized. To implement these functions, physical entities are needed to carry them. The BBS displays the hierarchical relationship of these physical entities in a tree structure. For example... Figure 3 As shown.

[0035] The novel functional virtual prototype model architecture presented in this paper categorizes system requirements into the following major categories, each corresponding to a product type, as detailed below: a) Data processing class: Possesses data processing capabilities and has a CPU; b) Video processing: Possesses video processing capabilities and a GPU; c) Display-type: Capable of displaying complex images, equipped with a display screen; d) Display and control class: It has simple screen display capabilities, data input capabilities, and a display screen and keyboard; e) Data acquisition category: These are devices capable of collecting various types of data; most are sensors. f) Data routing class: It has bus data conversion and input / output capabilities and is adaptable to multiple buses; g) Data storage: Possesses audio and video data storage capabilities and has a large-capacity memory card.

[0036] Taking avionics systems as an example, the "screen display" function belongs to the screen display category, should have a display screen, is identified as a display product, and belongs to the display subsystem; the "data acquisition" function belongs to the data acquisition category, should have a sensor, is identified as a sensor product, and belongs to the data acquisition subsystem; the "data processing" function belongs to the data processing category, should have a CPU, is identified as a processor product, and belongs to the mission subsystem. The processor, display, and sensor each require their own application software, middleware, and operating system, etc.

[0037] Therefore, the system decomposition structure is established as follows: System: Avionics System Subsystems: Task Subsystem, Display Subsystem, Data Acquisition Subsystem Equipment: Processor, display, sensor Software: Processor application software, processor middleware, processor operating system, display application software, display middleware, display operating system, sensor application software, sensor middleware, sensor operating system.

[0038] 3. Physical topology diagram Physical topology design is used to illustrate the interface connection relationships and data transmission relationships of devices within the system, corresponding to physical entities, as shown in the diagram. Figure 4As shown, the product breakdown diagram illustrates the system's components, while the physical topology diagram further demonstrates the connections between these components.

[0039] The physical topology diagram contains the following information: a) Models and attributes at each level, including systems, subsystems, devices, and software; b) The interfaces and types of each level of the system to the outside world; c) The bus components included in the system and their configuration; d) The connection relationship between the interfaces at each level of the system and the bus components; e) Data structure transmitted on interfaces at each level of the system.

[0040] Physical topology Figure 1 Generally applied in the field of network engineering, the novel functional virtual prototype model architecture presented in this paper applies the physical topology diagram to the field of systems engineering, and has the following characteristics: a) The system is presented in an intuitive graphical format, clearly showing the system's components, interfaces, cables, and other resources. System information is configured in the properties of each component to achieve a unified source of system information. (b) The physical topology diagram contains essential information such as composition, connections, data structure, and transmission paths for system virtual simulation. It can serve as the entry point for simulating all the functions of the system. Furthermore, the physical topology diagram allows for system decomposition, enabling the combination of semi-virtual and semi-physical devices for hybrid virtual-physical simulation testing. c) It has great scalability and can embed unlimited system information by configuring the attributes of the components, so as to realize the digitization of the system more realistically and completely.

[0041] Taking avionics systems as an example, the models at each level, including systems, subsystems, equipment, and software, include system components (avionics systems without subsystems), equipment components (processors, displays, and sensors), and software components (processor application software, processor middleware, processor operating system, display application software, display middleware, display operating system, sensor application software, sensor middleware, and sensor operating system). The attributes of each component display information such as its name, model, and configuration.

[0042] Each layer of the system has external interfaces, including two interfaces for the processor to interact with the display and sensors respectively, and one interface each for the display and sensors to interact with the processor. As a simple system, the data transmission is also relatively simple, with RS422 interfaces configured.

[0043] Since the system can complete data transmission using an RS422 interface, no complex bus components are required. All interfaces at each level of the system are RS422 interfaces, which can be directly connected. Furthermore, there is no direct data interaction between the sensor and the display; the connection is that the sensor connects to the processor and then to the display.

[0044] The data structure transmitted at each level of the system interface is the data required for the "screen display" and "data acquisition" functions.

[0045] 4. Use Case Diagram Use case diagrams build upon the requirements analysis results, using use cases to represent the functionalities derived from the analysis. Each use case in the diagram corresponds to a function, and each use case also corresponds to an activity diagram, serving as a bridge between different functions. A schematic diagram is shown below. Figure 5 As shown.

[0046] Taking avionics systems as an example, the system-level requirement is "to have basic flight information display functions," so the first-level use case is "basic flight information display." The functions obtained from the requirements analysis are "data acquisition," "screen display," and "data processing," so the second-level use cases of the system are three: "data acquisition," "screen display," and "data processing."

[0047] 5. Activity diagram Activity diagrams are used to define the functional logic of a system. They are implemented using the standard SysML language. Each use case corresponds to one activity diagram, with functional units assigned via swimlanes, and data flow, control flow, and activities defined. Logical data structures are built on top of the data flow. A schematic diagram is shown below. Figure 6 As shown.

[0048] The specific steps for constructing an activity diagram are as follows: 1) Define the purpose and scope; 2) Identify the main actions; 3) Establish an action sequence; 4) Add decision-making and merging; 5) Handling concurrency and synchronization; 6) Define the inputs and outputs; 7) Divide the swimming lanes.

[0049] Accordingly, in order to simulate the operation of the functional logic, the input and output interfaces of each activity in the activity diagram also need to be bound to the data structure and the data transmission bus. By matching the swimlane (i.e., physical entity) to which the activity belongs, the bus component for transmission, the data transmitted through the interface, etc., with the connections in the physical topology diagram, the correctness of the simulation is ensured.

[0050] Taking avionics systems as an example, the activity diagram should include swimlanes for sensors, processors, displays, etc. Sensors have data acquisition activities, and the output interface of the sensor's data acquisition activities should be bound to the sensor device, the sensor's data acquisition structure, and the RS422 bus, thereby uniquely determining a transmission path in the physical topology diagram. Other swimlanes are set up in the same way as sensors, thus establishing a functional logic model that can be distributed for simulation.

[0051] 6. Data Model Diagram Data model diagrams are used to define structures and their members, bind basic data types, and form a unified data carrier. The construction of data structures is based on basic data models, such as speed, from which airspeed and ground speed can be derived as structure members of the data structure.

[0052] The interaction of signals in the system requires data structures as carriers, which are transmitted in the data bus, as shown in the diagram. Figure 7 As shown.

[0053] Taking avionics systems as an example, the data sent by the sensors to the processor should be "sensor acquisition data," and the data sent by the processor to the display should be "display data," as shown in the following example: Sensor data collection: {"magnetic heading", "ground speed"} Display data: {"Magnetic heading", "Ground speed"} 7. Software Scheduling Diagram The software scheduling graph is used to configure the running relationships of software residing on the device, including information such as running cycle, priority, and residing partition. A schematic diagram is shown below. Figure 8 As shown.

[0054] Taking an avionics system as an example, the processor is assumed to use a single-core, dual-partition CPU. Two software programs run on each partition. Software program 1, residing on partition 1, has a higher priority than partition 2, occupying a 20ms time slice with a 50ms period. Software program 2 has a lower priority, occupying a 30ms time slice. This can be illustrated in a diagram. Figure 7 The software scheduling diagram shown illustrates how, during distributed simulation, the processor can schedule tasks according to... Figure 7 The simulation of the scheduling relationship shown demonstrates the completion of the function.

[0055] 8. Simulation Execution and Analysis The system composition is determined by the physical architecture, the connection relationships are clarified by the physical topology, data models are added to the topology model and functional model, the system functions are implemented by the functional model, and the resources and priorities occupied by the functions are clarified by the software scheduling relationship. These factors work together to build a digital prototype model that can be simulated with respect to the actual system.

[0056] The system's digital prototype model is simulated in a distributed environment. After completing the system input configuration, the output values ​​for each stage of system operation can be obtained. By analyzing the output values ​​at each stage of system operation, the metrics of the system's digital prototype model are iteratively optimized.

[0057] The present invention has the following advantages: 1. Achieve closed-loop management of the entire process from logical design to physical implementation; 2. Improve the consistency, traceability, and efficiency of modeling and simulation; 3. Supports collaborative simulation verification across systems and devices; 4. Reduce system integration risks and manual regression costs; 5. Improve the overall efficiency and quality of avionics system development.

[0058] The above description is merely a specific embodiment of the present invention, providing a detailed description of the invention. Parts not covered herein are conventional techniques. However, the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. The scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A novel functional virtual prototype model system capable of distributed simulation, characterized in that: The system includes: Requirements analysis diagrams are used to import system requirements and present them to designers in the form of charts, so that designers can decompose and summarize the requirements to form the functional requirements of the system. The product breakdown structure diagram, based on the analysis results of the requirements analysis diagram, summarizes the functions required by the system and the physical entities that need to support the functions to realize the system functions, and displays the hierarchical relationship of the physical entities in a tree structure. The physical topology diagram shows the interface connection relationships and data transmission relationships between various physical entities, which corresponds to the product breakdown structure diagram. Use case diagrams are based on the analysis results of requirements analysis diagrams, using use cases to carry the functions obtained from requirements analysis, with each use case corresponding to one function; Activity diagrams are used to describe the functional logic of a system. One use case corresponds to one activity diagram. Functional units are assigned through physical entities, and data flow, control flow, and activities are defined. Logical data structures are built on the data flow. A data model diagram is used to define data structures and their members, bind basic data types, and form a unified data carrier. A software scheduling diagram is used to configure the operational relationships of software that resides on physical entities and performs corresponding functions.

2. The system according to claim 1, characterized in that: The requirements analysis diagram includes four types of elements: requirement ID, requirement name, requirement content, and requirement type.

3. The system according to claim 2, characterized in that: Product breakdown structure diagrams are used to define the hierarchical relationships within a system.

4. The system according to claim 3, characterized in that: System requirements are divided into the following categories, each corresponding to a type of physical entity, as detailed below: a) Data processing class: Possesses data processing capabilities and has a CPU; b) Video processing: Possesses video processing capabilities and a GPU; c) Display-type: Capable of displaying complex images, equipped with a display screen; d) Display and control class: It has simple screen display capabilities, data input capabilities, and a display screen and keyboard; e) Data acquisition type: Capable of collecting various types of data, serving as sensors; f) Data routing class: It has bus data conversion and input / output capabilities, adapts to multiple bus interfaces, and has a bus terminal module or switch module; g) Data storage: Possesses audio and video data storage capabilities and has a large-capacity memory card.

5. The system according to claim 4, characterized in that: The physical topology diagram contains the following information: a) Models and attributes of each level of system, subsystem, device, and software; b) The interfaces and types of each level of the system to the outside world; c) The bus components included in the system and their configuration; d) The connection relationship between the interfaces at each level of the system and the bus components; e) Data structure transmitted on interfaces at each level of the system.

6. The system according to claim 5, characterized in that: The activity diagram is implemented using the standard SysML language.

7. The system according to claim 6, characterized in that: The specific steps for constructing an activity diagram are as follows: 1) Define the purpose and scope; 2) Identify the main actions; 3) Establish an action sequence; 4) Add decision-making and merging; 5) Handling concurrency and synchronization; 6) Define the inputs and outputs; 7) Divide physical entities.

8. The system according to claim 7, characterized in that: To simulate the operation of functional logic, the input / output interfaces of each activity in the activity diagram are bound to the data structure and the data transmission bus; the physical entity to which the activity belongs, the bus component for transmission, the data transmitted through the interface, etc., correspond one-to-one with the connections in the physical topology diagram.

9. The system according to claim 8, characterized in that: The interaction of signals in the system is carried out through data structures and transmitted in the data bus.

10. The system according to claim 9, characterized in that: The software scheduling graph includes runtime, priority, and resident partition information.

Images