Device full-chain simulation method based on parameter templating configuration, medium and equipment

Abstract

The application provides a device full-chain simulation method based on parameter templating configuration, a medium and equipment. The method comprises the following steps: configuring simulation software, generating a simulation template file based on the configured simulation software, and configuring simulation parameters; based on a pre-prepared simulation engine parameter configuration protocol, controlling each external engine to generate a parameter file in a corresponding protocol format, and based on the parameter file, communicating with the external engine; in response to receiving a simulation start instruction, loading the simulation template file and the parameter file, and based on the simulation template, the parameter file, the simulation parameters, and the properties of each engine pre-configured, controlling each engine to perform cooperative simulation. The application can effectively solve the technical problems that current various device simulation engines or software cannot realize data interface interconnection of engines and software of multiple types of devices, multiple tools, and multiple physical fields, and cannot meet efficient cooperation of multiple cross-scale simulation engines.

Description

Technical Field

[0001] This application belongs to the field of software engineering technology, and in particular relates to the field of device simulation technology. Background Technology

[0002] In the current device simulation design process, there are often problems such as data isolation, difficulty in integration, and low efficiency between data interfaces of single devices, single simulation tools, and single physical fields. Some key technical processes have problems such as "chain disconnection" and "low efficiency". It is impossible to achieve data interface interoperability between engines and software of multiple types of devices, multiple tools, and multiple physical fields, and it is impossible to meet the needs of multiple cross-scale simulation engines to achieve efficient collaboration to realize the full chain simulation of high function density devices.

[0003] Currently, PDKs (Product Data Kits), which encompass various information related to chip design and manufacturing, are widely used in microelectronic device design and simulation workflows. However, different design simulation workflows often require PDKs developed or customized by different companies and institutions. This situation means that key design simulation data, such as PDKs, cannot be easily understood and used by different design tools and workflows. Secondly, single simulation software often corresponds to a single application scenario, and its software interface is often specifically designed to match specific simulation tools and physical scenarios. This results in insufficient applicability of the interface across applications. This isolated interface design not only increases the difficulty of system integration but also reduces the overall efficiency and flexibility of simulation. Finally, when attempting to jointly simulate different physical processes or devices, it is often necessary to use multiple design simulation engines and software developed by international companies such as Candence, Synopsis, and Ansys, or domestic companies. These engines and software typically use custom models, data, and workflows, making data transfer and synchronization between software extremely difficult, especially in complex co-simulation scenarios composed of multiple models. This technical deficiency is even more pronounced in these scenarios.

[0004] Furthermore, current high-function-density devices often integrate multiple complex functions, materials, and structures. Their internal signal transmission involves issues such as circuit stability, thermal management, mechanical stress, and thermal stress. How to accurately and efficiently integrate simulation engines and software across multiple levels, including materials, processes, components, circuits, and devices, to achieve simple and efficient full-chain simulation with data parameter configuration is a problem that current high-function-density device design simulation software urgently needs to solve. Summary of the Invention

[0005] This application provides a device full-chain simulation method, medium, and device based on parameter template configuration, which solves the technical problem that current device simulation engines or software cannot achieve data interface interoperability between engines and software with multiple types of devices, multiple tools, and multiple physics fields, and cannot meet the requirements for efficient collaboration of multiple cross-scale simulation engines.

[0006] In a first aspect, embodiments of this application provide a device full-chain simulation method based on parameter template configuration, comprising: configuring simulation software; generating a simulation template file based on the configured simulation software and configuring simulation parameters; controlling each external engine to generate parameter files in a corresponding protocol format based on a pre-defined simulation engine parameter configuration protocol, and communicating and interacting with the external engines based on the parameter files; and, in response to receiving a simulation start command, loading the simulation template file and the parameter files, and controlling each engine to perform collaborative simulation based on the simulation template, the parameter files, the simulation parameters, and the pre-configured attributes of each engine.

[0007] In one implementation of the first aspect, configuring the simulation software and generating a simulation template file based on the configured simulation software includes: providing a simulation software configuration interface, adding or deleting simulation software, editing the simulation software name and executable path through the simulation software configuration interface; and generating a simulation template file in a preset format based on the information of the configured simulation software.

[0008] In one implementation of the first aspect, controlling each external engine to generate a parameter file in the corresponding protocol format based on a pre-defined simulation engine parameter configuration protocol includes: configuring the simulation engine parameter configuration protocol; configuring engine parameters based on the simulation engine parameter configuration protocol, generating a parameter file in the corresponding protocol format based on the engine parameters; and storing the parameter file in a preset folder corresponding to the external engine.

[0009] In one implementation of the first aspect, communication and interaction with the external engine is achieved through Python, including: encapsulating the external engine API into a standard Python function interface file; constructing a communication monitoring process based on the communication monitoring program provided by Python and the standard Python function interface file; and communicating and interacting with the external engine based on the communication monitoring process.

[0010] In one implementation of the first aspect, communication and interaction with the external engine are achieved through a Socket, including: a custom communication protocol based on the Socket, wherein the communication protocol includes at least a unique identifier for the data engine, text length, text, and multiple types of instructions; encapsulating the Socket service into a function interface and generating a service plugin, providing corresponding services through the service plugin, wherein the service plugin is any one or a combination of a registration client plugin, a sending instruction plugin, a receiving instruction plugin, and a data packet structure plugin; and a Socket listening process based on the communication protocol to achieve communication and interaction with the external engine.

[0011] In one implementation of the first aspect, the method further includes configuring the attributes of each engine, the attributes including project file, input from engine, and input file type; if the attributes of the project file are valid, the corresponding engine is started first; the input from engine is used to specify the upstream dependent engines of the engine; the input file type is used to filter the output files of the upstream engines as the input of the current engine.

[0012] In one implementation of the first aspect, controlling the collaborative simulation of each engine based on the simulation template, the parameter file, the simulation parameters, and the pre-configured attributes of each engine includes: determining the engine execution order based on the attributes of each engine; if upstream dependent engine simulation is required, acquiring and converting the output data of the upstream engine and transmitting it to the downstream engine, which then continues the simulation; and updating the simulation status and outputting the simulation results in real time.

[0013] In one implementation of the first aspect, determining the engine execution order based on the attributes of each engine includes: if the attributes of the project files of multiple engines are all valid, then the corresponding multiple engines are started simultaneously; if the attributes of the project files are invalid, but the attributes of the input from the engine and the input file type are valid, then the engine waits for the upstream dependent engine to finish simulating before starting.

[0014] Secondly, embodiments of this application provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the device full-chain simulation method based on parameter template configuration as described in any one of the first aspects of this application.

[0015] Thirdly, embodiments of this application provide an electronic device, the electronic device including a processor and a memory; the memory stores program instructions; the processor is used to run the program instructions to execute the device full-chain simulation method based on parameter template configuration as described in any one of the first aspects of this application.

[0016] The device full-chain simulation method based on parameter template configuration provided in this application has the following beneficial effects:

[0017] This application establishes data interfaces between different simulation engines or simulation software, enabling unified parameter configuration. It supports custom software chain configuration and template saving for combining one or more simulation engines to complete simulation tasks, simplifies the UI interaction process for users operating multiple simulation engines, increases simulation scale and optimizes simulation efficiency, and effectively solves the technical problems that current simulation engines or software cannot achieve data interface interoperability between engines and software for multiple types of devices, multiple tools, and multiple physics fields, and cannot meet the requirements for efficient collaboration of multiple cross-scale simulation engines. Attached Figure Description

[0018] Figure 1 The diagram shown is an overall flowchart of a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0019] Figure 2 The diagram shown is a schematic of the simulation software configuration in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0020] Figure 3 The illustration shows the intent of storing simulation templates in a device full-chain simulation method based on parameter template configuration, as an embodiment of this application.

[0021] Figure 4 The diagram shown is a flowchart of the unified parameter setting process in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0022] Figure 5 The flowchart shown is a process for generating parameter files in the corresponding protocol format in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0023] Figure 6 The flowchart shown is a process of communicating and interacting with an external engine using Python in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0024] Figure 7 The diagram shown illustrates the principle of information interaction between FullDSI and a third-party simulation engine via Python in a device full-chain simulation method based on parameter template configuration, as described in an embodiment of this application.

[0025] Figure 8 The flowchart shown is a process for communicating and interacting with an external engine via a Socket method in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0026] Figure 9 The diagram shown illustrates the principle of information interaction between FullDSI and a third-party simulation engine via Socket in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0027] Figure 10 The diagram shown is a simulation flowchart of a device full-chain simulation method based on parameter template configuration according to an embodiment of this application.

[0028] Figure 11 The diagram shown is a structural schematic of an electronic device according to an embodiment of this application.

[0029] Component designation explanation

[0030] 100 electronic devices 101 memory 102 processor 103 monitor S100~S300 step S210~S230 step S241~S243 step S251~S253 step Detailed Implementation

[0031] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.

[0032] To address the problems of isolated, difficult-to-integrate, inefficient, and disconnected data, simulation tools, and physical field data across different levels in the current device simulation design process, this application provides a device full-chain simulation method based on parameter template configuration. It supports custom software chain configuration and template saving for combining one or more simulation engines to complete simulation tasks, simplifies the UI interaction process for users operating multiple simulation engines, opens up data interfaces between different simulation engines or software, achieves unified parameter configuration, and provides integrated data configuration and high-speed data interaction and flow based on a unified data format. It offers full-chain simulation templates for various types of device simulation needs, along with template-based integrated self-driving simulation capabilities, reducing the overhead of traditional simulation methods in terms of experimental configuration and computational resources, increasing simulation scale, and optimizing simulation efficiency. The following will refer to the appendices in the embodiments of this application. Figure 1 To be continued Figure 11 This application provides a detailed description of the technical solutions in its embodiments. This allows those skilled in the art to understand and implement the device full-chain simulation method based on parameter template configuration, without requiring creative effort.

[0033] Figure 1 The flowchart shown is a process for simulating the entire device chain based on parameter template configuration, as described in this application. Figure 1 As shown, the device full-chain simulation method based on parameter template configuration provided in this application includes the following steps S100 to S300.

[0034] Step S100: Configure the simulation software, generate a simulation template file based on the configured simulation software, and configure the simulation parameters;

[0035] Step S200: Based on the pre-defined simulation engine parameter configuration protocol, control each external engine to generate parameter files in the corresponding protocol format, and communicate and interact with the external engines based on the parameter files;

[0036] Step S300: In response to receiving the simulation start command, load the simulation template file and the parameter file, and control each engine to perform collaborative simulation based on the simulation template, the parameter file, the simulation parameters, and the pre-configured attributes of each engine.

[0037] The following is in conjunction with the appendix Figure 2 To be continued Figure 10 The steps S100 to S300 of the device full-chain simulation method based on parameter template configuration in this embodiment will be described in detail.

[0038] Step S100: Configure the simulation software, generate a simulation template file based on the configured simulation software, and configure the simulation parameters.

[0039] In one implementation of this embodiment, configuring the simulation software and generating a simulation template file based on the configured simulation software includes:

[0040] 1) such as Figure 2 As shown, a simulation software configuration interface is provided, through which simulation software can be added or deleted, and the simulation software name and executable path can be edited.

[0041] like Figure 2 As shown in this embodiment, for example, in the simulation software configuration interface of the simulation engine, you can click on the multi-simulation engine toolchain option window, and add / delete the software that needs to be simulated through Add / Delete to customize the entire chain of simulation software. It also provides the option to customize and edit the names and executable path information of multiple simulation design software.

[0042] 2) such as Figure 3 As shown, a simulation template file in a preset format is generated based on the information configured in the simulation software.

[0043] like Figure 3 As shown, after adding or deleting simulation software, editing the simulation software name and executable path through the simulation software configuration interface, the entire simulation software is saved as a simulation template file and stored in the engine to provide automated template loading and rapid simulation for subsequent device simulation verification processes. The simulation template file can record the current entire simulation software toolchain, as well as the project configuration information of each simulation software, and is finally saved as a corresponding template file for direct loading by subsequent simulation tasks. For example, the simulation template file has the .tdsi extension, which is an XML format file.

[0044] Figure 4 The diagram shown is a flowchart illustrating the unified parameter setting process in a device full-chain simulation method based on parameter template configuration, according to an embodiment of this application. Figure 4As shown, the unified parameter setting process in the device full-chain simulation method based on parameter template configuration is as follows:

[0045] 1) Start the simulation tool

[0046] The process begins with launching FuIDSI (a full-chain simulation tool with parameter template configuration).

[0047] 2) Load simulation engine configuration

[0048] After the tool starts, it first loads the pre-configured simulation engine information, which includes two types of engines: commercial third-party simulation engines and third-party collaborative / self-developed simulation engines.

[0049] 3) Pass parameters to the engine according to type and execute operations.

[0050] The process is divided into two paths, simultaneously processing different types of simulation engines:

[0051] Commercial third-party simulation engine branch:

[0052] The Python communication interface listener process transmits setting parameters to the commercial third-party simulation engine → the commercial third-party simulation engine reads the corresponding third-party simulation engine setting information → and outputs information after performing simulation operations.

[0053] Tripartite collaboration / self-developed simulation engine approach:

[0054] This type of engine first performs simulation operations and outputs information → the self-developed simulation engine synchronously reads the settings of the third-party simulation engine → the signal receiving module obtains the relevant signals from the engine.

[0055] 4) Integrate information and update simulation settings

[0056] The output information from both engines is read and integrated by the SimulationSetting module, which then updates the simulation settings UI (unified parameter configuration entry) based on the integrated parameters.

[0057] 5) Start the simulation and manage communication and progress.

[0058] After updating the settings, start the simulation process → enter the communication management module to coordinate the interaction of each engine → finally update the Message / progress management module to synchronously display the simulation message logs and progress status.

[0059] 6) Process ends

[0060] After completing parameter settings, simulation startup, and progress synchronization, the process of setting parameters uniformly ends.

[0061] In this embodiment, the engine configuration is loaded uniformly through a tool, parameters are passed to different types of engines in separate paths, and then the information is integrated to update the settings, ultimately achieving unified parameter configuration and simulation collaboration for multiple engines.

[0062] This embodiment provides a unified parameter configuration interface. For example, by right-clicking to bring up the simulation settings window, simulation engine parameters, F-Domain and T-Domain parameters can be edited centrally, realizing integrated settings for multiple tool parameters.

[0063] This embodiment proposes a device full-chain simulation method based on parameter template configuration. It supports custom software chain configuration and template saving for combining one or more simulation engines to complete simulation tasks. This simplifies the UI interaction process for users operating multiple simulation engines and supports template configuration, data model interoperability, unified data configuration, and full-chain collaborative simulation for multi-level simulation engines or software, including materials, processes, components, circuits, and devices. Because this embodiment proposes a template-integrated simulation engine configuration method for the full-chain simulation needs of devices, it provides high-function-density device design simulation engineers with the ability to quickly interact, configure, and run multiple simulation design software programs from a unified user interface.

[0064] Step S200: Based on the pre-defined simulation engine parameter configuration protocol, control each external engine to generate parameter files in the corresponding protocol format, and communicate and interact with the external engines based on the parameter files.

[0065] In this embodiment, one or more simulation engines work together to complete the simulation task. Each simulation engine has its own simulation settings parameters. To simplify user operation, this embodiment provides a simulation engine parameter configuration protocol specification. The third-party engines decide on the simulation settings parameters to be made public based on this protocol specification and provide them in the form of XML files.

[0066] In this embodiment, the simulation engine parameter configuration protocol specification is pre-configured, and third-party and self-developed engines store the publicly available parameters in the form of XML files in a designated directory in accordance with the specification. Figure 5 This is a flowchart illustrating the generation of parameter files in a device full-chain simulation method based on parameter template configuration, according to an embodiment of this application. For example... Figure 5 As shown, in one implementation of this embodiment, controlling each external engine to generate parameter files in the corresponding protocol format based on a pre-defined simulation engine parameter configuration protocol includes the following steps S210 to S230.

[0067] Step S210: Configure the simulation engine parameter configuration protocol;

[0068] Step S220: Each external engine configures engine parameters based on the simulation engine parameter configuration protocol, and generates a parameter file in the corresponding protocol format based on the engine parameters;

[0069] Step S230: Store the parameter file in a preset folder corresponding to the external engine.

[0070] For example, the simulation setting parameter files for commercial simulation engine software are placed in the "Third-Party Simulation Engine Settings" subfolder of the integrated simulation engine software. For simulation engine software developed collaboratively or in-house, the development unit saves the publicly available simulation setting parameters as XML files according to the simulation engine parameter configuration protocol specifications, placing them in the "Simulation Engine Settings" subfolder of the corresponding simulation engine software installation package. When the simulation engine starts, it loads the parameter files from the corresponding folder along with the simulation engine software. In other words, the simulation engine automatically reads the corresponding XML parameter files when loading the simulation software, enabling automatic identification and conversion of parameters from different engines.

[0071] This embodiment provides two communication interaction methods: First, based on Python, the third-party engine API is encapsulated as a standard function interface, and data interaction is achieved through a communication listening process; Second, based on a custom Socket communication protocol, service classes such as FuldsiTCPService are encapsulated to support standardized communication of commands such as simulation start / stop, result display, and file transfer.

[0072] Figure 6 The flowchart shown is a process for communicating and interacting with an external engine using Python in a device full-chain simulation method based on parameter template configuration, according to an embodiment of this application. Figure 6 As shown, in one implementation of this embodiment, communication and interaction with the external engine is achieved through Python, including the following steps S241 to S243.

[0073] Step S241: Encapsulate the external engine API into a standard Python function interface file;

[0074] Step S242: Based on the communication monitoring program provided by Python and the standard Python function interface file, construct a communication monitoring process;

[0075] Step S243: The communication monitoring process interacts with the external engine.

[0076] In this embodiment, based on Python, the API interface of the third-party simulation engine is encapsulated into a standard Python function interface. On this basis, Python is used to encapsulate it again into a communication listening process. FulDSI and the simulation engine are bridged through this communication process to realize information interaction between FulDSI and the engine.

[0077] For example, the API commands provided by the third-party simulation engine are encapsulated into a general function interface file xxx.py using Python. Then, a communication monitoring program is provided based on Python, which loads the above-edited xxx.py file and encapsulates it into a communication monitoring process. 3) Information interaction process between FulDSI and the third-party simulation engine based on the Python communication process.

[0078] Figure 7 This diagram illustrates the principle of information interaction between FullDSI and a third-party simulation engine via Python in a device full-chain simulation method based on parameter template configuration, as described in an embodiment of this application. Figure 7 As shown, in the device full-chain simulation method with parameter template configuration, the information interaction process between FullDSI and the third-party simulation engine is implemented using Python as follows:

[0079] 1) Start FulDSI and load the engine

[0080] The process begins with launching FulDSI (a full-chain simulation tool). After the tool starts, two basic operations are performed simultaneously:

[0081] The loading engine module completes the initial loading of the third-party simulation engine, preparing the underlying engine resources for subsequent interactions; the interaction management module is activated as the central control center for information interaction.

[0082] 2) Command Initiation and Transmission: From Interactive Management to Python Process Monitoring

[0083] The interactive management module generates operation instructions based on simulation requirements, such as starting the simulation and configuring parameters. Based on preset parameter templates, it distributes these instructions to the Python listening process. The Python listening process, as the core of the Python interface between FulDSI and the third-party simulation engine, is responsible for receiving and temporarily storing these operation instructions.

[0084] 3) Instruction parsing and linking: intermediate processing of Python interfaces

[0085] The Python monitoring process parses the received operation commands and converts them into a format that the third-party simulation engine can recognize, such as commands that conform to the engine's API specifications.

[0086] After parsing, a connection is established through the Python communication interface to build a stable communication link (based on protocols such as TCP) with the loaded third-party simulation engine.

[0087] 4) Command execution and result feedback: Engine response and information transmission

[0088] After the connection is established, the Python listening process, through the instruction distribution module, passes the parsed instructions to the third-party simulation engine. Upon receiving the instructions, the third-party simulation engine executes them, such as running the simulation according to template parameters. After completion, it generates feedback results, such as simulation status, intermediate data, and logs. These feedback results are then transmitted back to the Python listening process via the established communication link.

[0089] 5) Interaction Closure: Feedback message processing and process termination

[0090] The Python listening process converts the received feedback results into a format recognizable by FulDSI and passes them to the interaction management module. The interaction management module processes the feedback messages, such as updating the UI status and logging. Finally, the process reaches the end node, completing a full information interaction.

[0091] Throughout the process, the core role of the Python approach is to use Python to monitor the process and perform instruction format conversion, communication connection management, and data relay. This enables FulDSI to efficiently call third-party simulation engines and obtain feedback based on a unified parameter template, ensuring the consistency and stability of cross-engine information interaction in the entire simulation chain.

[0092] Figure 8 The flowchart shown is a process for communication and interaction with an external engine via a Socket method in a device full-chain simulation method based on parameter template configuration according to an embodiment of this application. Figure 8 As shown, in one implementation of this embodiment, communication and interaction with the external engine are achieved through a Socket, including the following steps S251 to S253.

[0093] Step S251: Based on the Socket custom communication protocol, the communication protocol includes at least the data engine unique identifier, text length, text, and multiple types of instructions;

[0094] Step S252: Encapsulate the Socket service into a function interface and generate a service plugin. Provide the corresponding service through the service plugin. The service plugin is any one or more combinations of a registration client plugin, a sending command plugin, a receiving command plugin, and a data packet structure plugin.

[0095] Step S253: Based on the communication protocol, the Socket listening process enables communication and interaction with the external engine.

[0096] In this embodiment, Socket communication can be used, a custom communication protocol can be defined, and the service can be encapsulated into a function interface to provide services as a plugin. Table 1 shows an example of the Socket communication protocol.

[0097] Table 1

[0098]

[0099] Table 2 shows an example of the encapsulated function interface specification.

[0100] Table 2

[0101]

[0102]

[0103] Figure 9 This diagram illustrates the principle of information interaction between FullDSI and a third-party simulation engine via Socket in a device full-chain simulation method based on parameter template configuration, according to an embodiment of this application. Figure 9 As shown, in the device full-chain simulation method based on parameter template configuration, the information interaction process between FullDSI and the third-party simulation engine is realized through the Socket method. This can be summarized in the following steps, referring to the flowchart:

[0104] 1) Initialization tools and engine

[0105] The process begins with launching FulDSI (a full-chain simulation tool), which triggers two core operations simultaneously upon launch:

[0106] The initial loading of the third-party simulation engine is completed by loading the engine module (based on the preset parameter template configuration to ensure the compatibility between the engine and the tool); the interaction management module is activated as the central control center for information interaction, responsible for the generation of instructions and the processing of feedback.

[0107] 2) Command Initiation: The interaction management module generates and distributes operation commands.

[0108] The interaction management module generates operation instructions based on simulation requirements (combined with the configuration rules in the parameter template), such as starting the simulation, adjusting parameters, and querying status, and then passes the instructions to the Socket listening process. This process is the core middleware layer of Socket communication and is responsible for listening for instructions from the interaction management module.

[0109] 3) Instruction processing: The Socket listening process parses and establishes a connection.

[0110] After receiving the operation command, the Socket listening process first parses it, converting it into a format that conforms to the Socket communication protocol and can be recognized by the third-party simulation engine, ensuring that the command is compatible with the engine API. After parsing, a connection is established through the Socket protocol to build a stable communication link with the loaded third-party simulation engine, laying the foundation for subsequent command transmission.

[0111] 4) Command execution: The simulation engine responds and returns the results.

[0112] After the connection is established, the Socket listening process transmits the parsed instructions to the third-party simulation engine through the instruction distribution module. After receiving the instructions, the third-party simulation engine executes the instruction operation according to the configuration in the parameter template, such as running the simulation process according to the preset parameters. After the operation is completed, feedback results are generated, including simulation status, data, logs and other information.

[0113] 5) Results Feedback: Information Transmission and Process Closure

[0114] The third-party simulation engine sends the feedback results back to the Socket listening process through the established Socket connection; the Socket listening process converts the feedback results into a format that FulDSI can recognize and passes them to the interaction management module in the form of feedback messages; the interaction management module processes the feedback messages, such as updating the UI display, logging, and triggering subsequent processes, and finally the process reaches the end node, completing a complete Socket interaction.

[0115] Throughout the process, the core of the Socket approach is to achieve cross-module protocol adaptation, connection management, and command relay through the Socket listening process. Combined with the standardized configuration of parameter templates, it ensures the efficiency, stability, and parameter consistency of information exchange between FullDSI and third-party simulation engines, supporting the collaborative operation of the entire device simulation chain.

[0116] This embodiment proposes an automatic conversion and communication method for simulation parameters between self-developed engines and third-party engines, and establishes data interfaces between different simulation engines or software to achieve unified parameter configuration. Therefore, designers of high-function-density devices can use the templated simulation parameter configuration proposed in this embodiment to optimize the traditional problems of data incompatibility and data silos between different software, supporting a full-chain device simulation method based on parameter template configuration.

[0117] Step S300: In response to receiving the simulation start command, load the simulation template file and the parameter file, and control each engine to perform collaborative simulation based on the simulation template, the parameter file, the simulation parameters, and the pre-configured attributes of each engine.

[0118] In this embodiment, simulation is performed by a combination of one or more simulation engines; each simulation engine corresponds to three attributes: project file, input source engine, and input file type. In one implementation of this embodiment, the attributes of each engine are further configured, including project file, input source engine, and input file type.

[0119] If the attributes of the project file are valid, the corresponding engine will be started first. That is, if the attribute values ​​of the simulation engine's project file are valid, it indicates that the simulation engine will be simulated first in this cross-scale link simulation. The "input from engine" specifies the upstream dependent engines of the current engine, and the "input file type" filters the output files of the upstream engines as input to the current engine. In this embodiment, the "input file type" is used in conjunction with "input from engine" to filter the simulation results input from the engine, and the filtered result files are used as input to the simulation engine. "Input from engine" and "input file type" can be multiple combinations, separated by semicolons (;).

[0120] In one implementation of this embodiment, controlling the collaborative simulation of each engine based on the simulation template, the parameter file, the simulation parameters, and the pre-configured attributes of each engine includes: determining the engine execution order based on the attributes of each engine; if upstream dependent engine simulation is required, acquiring and converting the output data of the upstream engine and transmitting it to the downstream engine, which then continues the simulation; and updating the simulation status and outputting the simulation results in real time.

[0121] In one implementation of this embodiment, determining the engine execution order based on the attributes of each engine includes: if the attributes of the project files of multiple engines are all valid, then the corresponding multiple engines are started simultaneously; if the attributes of the project files are invalid, but the attributes of the input from the engine and the input file type are valid, then the engine waits for the upstream dependent engine to finish simulating before starting.

[0122] In this embodiment, if the project file attribute values ​​of multiple simulation engines are valid in the cross-scale link simulation, it indicates that these simulation engines are not coupled during this cross-scale link simulation and can run the simulation in parallel; if the project file attribute value of the simulation engine is empty or invalid, but the input from the engine and the input file type value are valid, it indicates that this simulation engine will only start the simulation after the upstream engine whose input from the engine has finished its simulation.

[0123] Figure 10 The diagram shown is a simulation flowchart of a device full-chain simulation method based on parameter template configuration, according to an embodiment of this application. Figure 10 As shown, the simulation process in the device full-chain simulation method based on parameter template configuration is as follows:

[0124] 1) Start the tool and initialize the link and engine.

[0125] The process begins with launching FulDSI (a full-chain simulation tool), followed by completing two basic preparations:

[0126] Create a demo link: Based on a preset parameter template, build a simulation link framework adapted to the target device, such as the simulation link of a silicon-based three-dimensional integrated RF device;

[0127] Select the desired simulation engine from the engine library (such as Hermes, ADS, and ETS engines in Figure 10) and match the toolchain configuration corresponding to the parameter template.

[0128] 2) Templated simulation settings

[0129] Complete two core configurations based on parameter templates:

[0130] Simulation parameter settings: Call the preset parameters in the template, such as frequency domain / time domain parameters and device process parameters, and uniformly configure the simulation parameters of each engine;

[0131] Self-driven data flow configuration: Define the input and output dependencies of each engine in the template (e.g., Hermes' output as ADS' input), to prepare for automatic scheduling.

[0132] 3) Self-driven simulation scheduling

[0133] Entering the self-driven simulation module, the scheduling is completed collaboratively by the sub-units within the module:

[0134] The self-driven management module coordinates the entire process;

[0135] The simulation priority management module determines the engine execution order based on the dependencies defined in the template;

[0136] The simulation data flow management module plans the data flow path;

[0137] The data conversion module automatically adapts to the parameter formats of different engines (based on a standardized template protocol).

[0138] The interaction management module sends instructions / messages to this module to synchronize the process status.

[0139] 4) Condition determination for simulation execution and project submission

[0140] The serial / parallel execution logic of multiple engines is controlled by determining whether the Hermes simulation has ended.

[0141] If the Hermes simulation is not finished: wait for it to complete;

[0142] If the Hermes simulation has finished: Submit the corresponding project files to the high-performance computing module:

[0143] Submit the Hermes project (including the generated .mesh conversion results);

[0144] Submit the ADS project (including .s*p files);

[0145] Submit the ETS project (including the .mphtxt file).

[0146] 5) Engine simulation and status feedback

[0147] The high-performance computing module calls the corresponding engine (Hermes, ADS, ETS) to execute the simulation and complete the state synchronization:

[0148] Each engine executes simulation tasks and feeds back the simulation status (such as running, successful, or failed) to the high-performance computing module.

[0149] The high-performance computing module updates the simulation status and sends the status back to the interactive management module.

[0150] 6) Process ends

[0151] The interactive management module integrates the simulation results from all engines and finally outputs the full-chain simulation results, thus ending the process.

[0152] The entire process is centered around parameter templates. Through self-driven scheduling and automatic data conversion, it achieves collaborative simulation of multiple engines, avoids manual intervention, and meets the needs of efficient and unified simulation of the entire device chain.

[0153] Since this embodiment proposes a device full-chain simulation method based on parameter template configuration, it can reduce the time overhead of traditional simulation methods in configuring and adjusting simulation parameters and model data. Therefore, high-function-density device design and simulation personnel can use this embodiment to improve the scale of device simulation and optimize simulation efficiency, thereby enhancing their core competitiveness in the fields of microelectronic device design and key industrial software.

[0154] The following case study demonstrates and verifies that the device simulation method based on parameter template configuration proposed in this embodiment can improve the simulation efficiency of high-functionality device design. The case study includes the workflow and implementation results.

[0155] I. Case Process

[0156] 1. Using the template-integrated simulation engine configuration method proposed in this embodiment for device full-chain simulation needs: Open the silicon-based three-dimensional integrated RF device verification template, and set the device-level Hermes simulation module, the device-level digital twin engine, and the circuit-level XDS simulation module;

[0157] 2. Using the self-developed engine and third-party engine simulation parameter automatic conversion and transfer method proposed in this embodiment: Configure the simulation parameters and files required for the iterative design of silicon-based three-dimensional integrated RF devices at each level, access the S-parameters of GaAs and GaN chip twin models, the S-parameter model of the 3D integrated transmission structure, and the S-parameter dataset of bondwire based on different design parameters in XDS.

[0158] 3. Using the device full-chain simulation method based on parameter template configuration proposed in this embodiment: Start the simulation process, a) establish the 92-96 GHz band S-parameter model of the bondwire through the process-level digital twin engine; b) configure the initial spacing (d), height (H) or length (L), and import the above bondwire 92-96 GHz band S-parameter model into Hermes through the interface engine; c) obtain the device 92-96 GHz band S-parameters by simulating the entire link through XDS.

[0159] 4. Observe and verify the link simulation results: Observe whether there is a standing wave (SWR) and whether the design gain index S21 exceeds 32dB. If not, repeat step bc until the bondwire design parameters are configured so that there is no standing wave and the S-parameter gain index S21 in the 92-96 GHz band exceeds 32dB. Then, use Hfss simulation to perform electromagnetic simulation on the bondwire with the same design parameters to obtain the S-parameters. Use XDS simulation to simulate the entire link to obtain the device's S-parameters in the 92-96 GHz band. Calculate the total time T0 for the above design parameter optimization, simulation, and iteration.

[0160] 5. Configure traditional methods for link design simulation: including HFSS and ADS software, and perform simulations one by one;

[0161] 6. Verify the design acceleration performance of silicon-based 3D integrated RF devices: Iterative design optimization of silicon-based 3D integrated RF devices is carried out. The overall device model is imported into HFSS and divided into sub-modules such as core, transmission structure, and GSG type bondwire.

[0162] 7. Modify the GSG type bondwire model in the existing silicon-based three-dimensional integrated RF device using HFSS software, adjusting the spacing (d), height (H) or length (L). After modification, perform electromagnetic simulation on the model to obtain the S-parameters of the 92-96 GHz frequency band, and accumulate the total time t1 required for design simulation.

[0163] 8. Build the circuit schematic of the silicon-based three-dimensional integrated RF device, including each chip and sub-module, using the circuit-level simulation software ADS, and import the S-parameter models of the chips, transmission structure and bondwire. Simulate the entire link to obtain the S-parameters of the device in the 92-96GHz band and calculate the required time t2.

[0164] 9. Observe the S-parameters of the link simulation to see if there are standing waves and whether the design gain index S21 exceeds 33dB. If not, repeat steps 7-8 to carry out the second and subsequent iterations of design and simulation until there are no standing waves and the gain index S21 in the 92-96 GHz band exceeds 33dB. Then the optimization design is completed. Calculate the time t3 required for all the above second and subsequent iterations of design and simulation.

[0165] 10. Calculate and compare the total simulation time (T0) of silicon-based three-dimensional integrated RF devices after accelerated design with the total simulation time of traditional non-accelerated design (T1=t1+t2+t3).

[0166] II. Implementation Results

[0167] Tests showed that the total duration T0 of the device gain S-parameter was recorded using the device full-chain simulation method based on parameter template configuration proposed in this embodiment.

[0168] The link simulation was performed using traditional methods, with the following stages timed sequentially: 1. Three engineers with 4, 5, and 9 years of experience respectively modified the GSG-type bondwire model in HFSS software according to the traditional silicon-based 3D integrated RF device design flow, adjusting the spacing (d), height (H), or length (L). After modification, electromagnetic simulation was performed on the model to obtain the S-parameters of the 92-96 GHz band, and the total simulation time t1 was accumulated; 2. The circuit schematic of the silicon-based 3D integrated RF device, including each chip and sub-module, was built using the circuit-level simulation software ADS, and the S-parameter models of the chips, transmission structure, and bondwire were imported. The entire link was simulated to obtain the S-parameters of the device in the 92-96 GHz band, and the time required was calculated to t2; 3. The S-parameters of the simulated link were observed to check for standing waves (SWR) and whether the design gain index S21 exceeded 32 dB. If the target was not met, steps 7-8 were repeated for a second and subsequent iteration of design and simulation until no SWR appeared and the S-parameters of the 92-96 GHz band were achieved. If the gain index S21 of the GHz band exceeds 32dB, the optimization design is completed. Calculate the time t3 required for all the above-mentioned second and subsequent iterative design simulations; record the total time T1 of the traditional design simulation method (T1=t1+t2+t3).

[0169] The efficiency improvement was calculated based on the formula: the total simulation time (T1=t1+t2+t3) was increased by the efficiency improvement = (T1-T0) / T1*100%; the operation was repeated three times, and the relevant results are shown in Table 3 below.

[0170] Table 3

[0171]

[0172] In summary, the device full-chain simulation method based on parameter template configuration proposed in this embodiment can simplify the operation process of multiple tools, break down data interface barriers, reduce configuration and resource overhead, and improve simulation efficiency and shorten time by more than 50% when performing full-chain simulation of high-functional-density devices compared with traditional methods. It is suitable for multi-physics field and cross-scale full-chain simulation scenarios of high-functional-density devices.

[0173] The protection scope of the device full-chain simulation method based on parameter template configuration described in this application is not limited to the execution order of the steps listed in this embodiment. Any solution implemented by adding, subtracting, or replacing steps in the prior art based on the principles of this application is included within the protection scope of this application.

[0174] It should be noted that, in this embodiment, the device full-chain simulation tool based on parameter template configuration, constructed according to the principle of the above-mentioned device full-chain simulation method based on parameter template configuration, is used to implement the device full-chain simulation method based on parameter template configuration. It is defined as FulDSI (Full-chain Device Simulation Integration Tool) and is the core carrier tool of the device full-chain simulation method based on parameter template configuration.

[0175] Corresponding to the aforementioned device full-chain simulation method based on parameter template configuration, FulDSI achieves unified management of multiple simulation engines, automatic parameter conversion and flow, and self-driven full-chain simulation scheduling through parameter template configuration. It solves the problems of data isolation across levels, incompatibility of multiple tool interfaces, excessive manual intervention in the process, and low efficiency in traditional microelectronic device simulation. It is suitable for high-functionality devices, such as silicon-based three-dimensional integrated radio frequency devices, for cross-scale and multi-physics full-chain simulation needs.

[0176] The FulDSI tool, built based on the principle of the aforementioned device full-chain simulation method using parameter template configuration, includes the following modules:

[0177] 1. Template and Engine Configuration Modules

[0178] 1-1) Template-integrated simulation engine configuration module

[0179] It supports customization of multiple simulation engine toolchains (Add / Delete operations), saving / reusing toolchain and project parameter templates in .tdsi format (XML), and configuring the executable path of the simulation engine.

[0180] 1-2) Unified configuration module for simulation parameters

[0181] It provides a unified UI interface to enable integrated settings for simulation engine parameters, F-Domain (frequency domain), and T-Domain (time domain) parameters; it manages XML parameter protocol specifications and automatically reads / parses parameter files from each engine.

[0182] 2. Communication and Interaction Modules

[0183] 2-1) Python Communication Interface Module

[0184] It includes a Python communication interface listening process, encapsulates third-party engine APIs into standard Python function interfaces, and implements command / data interaction between FulDSI and third-party engines through the fuldsi_simulation.py script.

[0185] 2-2) Socket Communication Module

[0186] It includes a Socket listening process, which enables interaction without a Python API engine based on a custom Socket protocol (data packet = engine token + text length + text); it also includes sub-modules such as FuldsiTCPService (client registration), FuldsiClient (message sending and receiving), and FuldsiMessage (data packet encoding and decoding).

[0187] 2-3) Communication Management Module

[0188] Coordinate the switching between Python and Socket communication methods and synchronize parameters and commands across engines.

[0189] 3. Self-driven simulation scheduling module

[0190] 3-1) Self-driven management module

[0191] It coordinates the entire self-driven simulation process, receives instructions from the interactive management module, and schedules sub-modules.

[0192] 3-2) Simulation Priority Management Module

[0193] Based on the engine dependencies defined by the parameter template (project file validity, input source engine), the engine execution order (parallel / serial) is determined.

[0194] 3-3) Simulation Data Flow Management Module

[0195] Plan the data flow paths between the engines and match the input and output file types, such as using Hermes' .xml results as input for XDS.

[0196] 3-4) Data Conversion Module

[0197] Based on the XML parameter protocol, it automatically converts the parameters and result formats of different engines to achieve data interoperability.

[0198] 4. Execution and Interaction Modules

[0199] 4-1) Interaction Management Module

[0200] The main control interface of FulDSI is responsible for generating operation commands, receiving feedback messages, updating UI status, and synchronizing simulation logs.

[0201] 4-2) High-performance computing module

[0202] It receives self-driven scheduling project files (such as Hermes projects or ADS .s*p files), calls the corresponding engine to execute simulations, and receives and synchronizes the simulation status.

[0203] 4-3) Message / Progress Management Module

[0204] Record simulation logs (such as engine running status) and synchronize simulation progress to the UI interface.

[0205] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the device full-chain simulation method based on parameter template configuration provided in any embodiment of this application.

[0206] In the embodiments of this application, any combination of one or more storage media may be used. The storage medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, RAM, ROM, erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0207] This application also provides an electronic device. Figure 11 The diagram shown is a structural schematic of the electronic device 100 provided in an embodiment of this application. In some embodiments, the electronic device may be a mobile phone, tablet computer, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), or other terminal device. Furthermore, the device full-chain simulation method based on parameter template configuration provided in this application can also be applied to databases, servers, and service response systems based on terminal artificial intelligence. This application does not limit the specific application scenarios of the device full-chain simulation method based on parameter template configuration.

[0208] like Figure 11 As shown, the electronic device 100 provided in this application embodiment includes a memory 101 and a processor 102.

[0209] The memory 101 is used to store computer programs; preferably, the memory 101 includes various media that can store program code, such as ROM, RAM, magnetic disk, USB flash drive, memory card or optical disk.

[0210] Specifically, memory 101 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory. Electronic device 100 may further include other removable / non-removable, volatile / non-volatile computer system storage media. Memory 101 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this application.

[0211] The processor 102 is connected to the memory 101 and is used to execute the computer program stored in the memory 101 so that the electronic device 100 executes the device full-chain simulation method based on parameter template configuration provided in any embodiment of this application.

[0212] Optionally, the processor 102 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0213] Optionally, in this embodiment, the electronic device 100 may further include a display 103. The display 103 is communicatively connected to the memory 101 and the processor 102, and is used to display the relevant GUI interactive interface of the device full-chain simulation method based on parameter template configuration.

[0214] In summary, this application establishes data interfaces between different simulation engines or software, enabling unified parameter configuration. It supports custom software chain configuration and template saving for combining one or more simulation engines to complete simulation tasks, simplifying the UI interaction process for users operating multiple simulation engines. This improves simulation scale and optimizes simulation efficiency, effectively solving the technical problems of current device simulation engines or software failing to achieve data interface interoperability across multiple device types, tools, and physics fields, and failing to meet the requirements for efficient collaboration among multiple cross-scale simulation engines. Therefore, this application effectively overcomes the various shortcomings of existing technologies and has high industrial application value.

[0215] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. A device full-chain simulation method based on parameter template configuration, characterized in that, include: Configure the simulation software, generate a simulation template file based on the configured simulation software, and configure the simulation parameters; Based on a pre-defined simulation engine parameter configuration protocol, each external engine is controlled to generate parameter files in the corresponding protocol format, and communication and interaction with the external engines are performed based on the parameter files. In response to receiving a simulation start command, the simulation template file and the parameter file are loaded, and the engines are controlled to perform collaborative simulation based on the simulation template, the parameter file, the simulation parameters, and the pre-configured attributes of each engine. It also includes configuring the properties of each engine, including the project file, the engine from which the input comes, and the type of the input file; if the properties of the project file are valid, the corresponding engine will be started first; the engine from which the input comes is used to specify the upstream dependent engines of the engine. The input file type is used to filter the output files of the upstream engine as input to the current engine; The method of controlling the collaborative simulation of each engine based on the simulation template, the parameter file, the simulation parameters, and the pre-configured attributes of each engine includes: determining the engine execution order according to the attributes of each engine; if upstream dependent engine simulation is required, acquiring and converting the output data of the upstream engine and transmitting it to the downstream engine, which then continues the simulation; and updating the simulation status and outputting the simulation results in real time.

2. The device full-chain simulation method based on parameter template configuration according to claim 1, characterized in that, The configuration of the simulation software, and the generation of simulation template files based on the configured simulation software, include: A simulation software configuration interface is provided, through which simulation software can be added or removed, and the simulation software name and executable path can be edited; Based on the information configured in the simulation software, a simulation template file in a preset format is generated.

3. The device full-chain simulation method based on parameter template configuration according to claim 1, characterized in that, The method of controlling each external engine to generate parameter files in the corresponding protocol format based on a pre-defined simulation engine parameter configuration protocol includes: Configure the simulation engine parameter configuration protocol; Each external engine configures engine parameters based on the simulation engine parameter configuration protocol, and generates a parameter file in the corresponding protocol format based on the engine parameters; The parameter file is stored in a preset folder corresponding to the external engine.

4. The device full-chain simulation method based on parameter template configuration according to claim 1, characterized in that, Implementing communication and interaction with the external engine using Python includes: The external engine API is encapsulated into a standard Python function interface file; A communication monitoring process is constructed based on the communication monitoring program provided by Python and the standard Python function interface file. The communication monitoring process interacts with the external engine.

5. The device full-chain simulation method based on parameter template configuration according to claim 1, characterized in that, Communication and interaction with the external engine are achieved via Socket, including: Based on a custom Socket communication protocol, the communication protocol includes at least a unique data engine identifier, text length, text, and multiple types of instructions. The Socket service is encapsulated into a function interface and a service plugin is generated. The corresponding service is provided through the service plugin. The service plugin is any one or more combinations of a registration client plugin, a sending command plugin, a receiving command plugin, and a data packet structure plugin. Based on the aforementioned communication protocol, the Socket listening process enables communication and interaction with the external engine.

6. The device full-chain simulation method based on parameter template configuration according to claim 1, characterized in that, The method of determining the engine execution order based on the attributes of each engine includes: If the properties of the project files for multiple engines are all valid, then the corresponding multiple engines will start simultaneously; If the attributes of the project file are invalid, but the attributes of the input from the engine and the input file type are valid, then the engine will wait for the upstream dependent engine simulation to complete before starting.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the device full-chain simulation method based on parameter template configuration as described in any one of claims 1 to 6.

8. An electronic device, characterized in that, The electronic device includes: Processor and memory; The memory stores program instructions; The processor is configured to run the program instructions to execute the device full-chain simulation method based on parameter template configuration as described in any one of claims 1 to 6.

Images