Integrated design management system with automatic registration communication agent engine and method thereof

Abstract

The invention discloses an integrated design management system with an automatic registration communication agent engine and a method thereof, and relates to the technical field of software integrated design simulation. The method has a heterogeneous integration breakthrough, the five communication modes are matched with the software without the API / command line / file, different heterogeneous software can support one communication mode, and the integration cost is remarkably reduced; dynamic expansibility is achieved, a newly added software module only needs to deploy a proxy engine and configure registration, and zero-shutdown upgrading of the platform is achieved; high concurrency reliability is achieved, resource conflicts are solved for an instance mechanism, and parallel task efficiency is improved; and full-process automation is achieved, and the cross-software design process execution time is obviously shortened.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software integrated design simulation, in particular to an integrated design management system with an automatic registration communication agent engine and a method thereof. BACKGROUND

[0002] In the industrial design, such as the development of complex products like aircraft, vehicles, etc., multiple professional software (such as UG software, CAD modeling, CAE simulation, optimization design tools, and some calculation, simulation, and simulation software developed by the enterprise itself) need to be used collaboratively.

[0003] The prior art has the following defects: heterogeneity barrier, each software can only run independently, cannot be linked, because the communication interface is not unified (API / file / command line), the data format difference is large; deployment dispersion, software modules are independently deployed on different servers, communication and connection are difficult; low efficiency of cooperation, cross-software data transmission depends on manual operation, low efficiency, and prone to errors; high integration cost, customized interface development workload is large, poor scalability; process automation is difficult, lack of flexible arrangement and monitoring mechanism of cross-software process; the existing integration platform generally cannot solve such highly heterogeneous and distributed deployment tools, and cannot support automatic process arrangement and other problems. Therefore, we propose an integrated design management system with an automatic registration communication agent engine and a method thereof. SUMMARY

[0004] The purpose of the present application is to solve the problems mentioned in the background art, and the present application provides an integrated design management system with an automatic registration communication agent engine and a method thereof.

[0005] In order to achieve the above purpose, the present application specifically adopts the following technical solutions:

[0006] An integrated design management system with an automatic registration communication agent engine comprises:

[0007] Control center: a Web interface based on a browser, providing management of communication agent engines on different nodes, realizing control of heterogeneous software (such as starting, stopping, data saving, data exporting, and data transmission), supporting process design between heterogeneous software, realizing user management, process scheduling, and task allocation;

[0008] Communication agent engine: used for connecting control center and local software module, each heterogeneous software module is deployed in the same host node (Windows / Linux), and each communication agent engine is deployed in different host to manage related heterogeneous software in the host; each engine is automatically registered to the control center through configuration file information when starting; the communication mode between the communication agent engine and each software supports multiple docking modes; the communication agent engine provides standardized RESTful API (task start and stop, file transmission, state query) to the outside, which meets the control center to control each heterogeneous software through API;

[0009] Multiple heterogeneous software modules: each heterogeneous software needs to support at least one docking mode, or encapsulate and transform the original independent software to support one of the docking modes.

[0010] Further, the control center comprises:

[0011] The registration and resource management module is used for receiving engine registration request, analyzing engineConfig.yaml content, verifying field legality, recording engine network address and program instance information, establishing primary key index, associating running state (idle, running, fault, etc.) and time stamp for each instance, responding to heartbeat request and updating engine state, supporting online and offline judgment and alarm;

[0012] The process arrangement and task scheduling module, users can customize the process (specify program instance in process step) in the front end; the control center schedules the process steps in sequence, controls the process to automatically push back; each process step state (queued, running, completed, failed) is visualized; it has task retry, manual termination and other operation and maintenance interfaces;

[0013] The result return and storage module, after each process step is completed, the agent engine returns the result data; the control center is uniformly stored in the file system or the database, the database uses a relational database as the main database, uniformly stores agent engine registration information, program instance state, user process data, and forms task execution log; the front end supports users to view running state, download results or graphical display in real time.

[0014] Further, the communication agent engine comprises:

[0015] The registration module is used for automatically reading engineConfig.yaml; sending engine meta information to the control center / api / register through HTTP protocol; if failed, retry and write log; after successful registration, enter running state and start heartbeat thread;

[0016] Task execution management module: after receiving the / api / dispatch request, find the corresponding program path according to the specified program instance name instName, judge whether it is a multi-instance program, construct the execution command and start the sub-process, listen to the sub-process state, collect the log; after the program ends, package the output file and return to the control center through / api / result.

[0017] Further, the docking mode in the communication agent engine is divided into sub-process control, API calling, file monitoring, embedded interaction and manual triggering.

[0018] Further, the heterogeneous software in the plurality of heterogeneous software modules is an industrial design software such as UG NX software, a simulation tool (such as ANSYS), an optimization design program or self-developed software or product.

[0019] An integrated design management method with an automatic registration communication agent engine, comprising the management system of any one of the above, comprising the following steps:

[0020] S1, dynamic registration, for dynamic registration of information;

[0021] S2, engine configuration file: for reading the information of the engine configuration file when the agent engine starts;

[0022] S3, program instance control, after the communication agent engine is successfully registered, the control center manages and schedules the related instances of each agent engine;

[0023] S4, multi-instance concurrent control, for coordinating the parallel execution of multiple program instances through sub-process control or API calling, ensuring reasonable allocation of resources and avoiding conflicts;

[0024] S5, execution across software, for coordinating and driving the execution of cross-software tasks, through the specified docking mode such as API calling, file monitoring or embedded interaction, realizing data transmission, command execution and process automation between different heterogeneous software (such as UG NX, ANSYS simulation tool or self-developed optimization program), ensuring the coherence and interoperability of design, simulation and optimization operations;

[0025] S6, task execution management: after receiving the task request, construct the execution command according to the specified instance path, start the sub-process and listen to its state in real time, and collect the running log at the same time;

[0026] S7, result processing: after the task ends, automatically package the output file and return to the control center through the API interface to complete the closed-loop management;

[0027] S8, Abnormality processing and monitoring, for detecting errors or conflicts in real time during execution, automatically retrying, pausing or notifying the control center to intervene through preset rules of the engine configuration file, guaranteeing system stability and task reliability.

[0028] Further, the dynamic registration comprises the following steps:

[0029] S11, Engine startup registration: when the proxy engine starts, read the engine configuration file information, obtain the heterogeneous software information of the node, each heterogeneous software is a program instance of the engine, and then send a registration request to the control center;

[0030] S12, Control center stores engine information: after the control center receives the registration request, first checks the legality of the engine information in the database, and then persistently stores the registration information of the engine identifier, network address and supported program instance;

[0031] S13, Registration success response: after storage is completed, the control center returns a registration success response to the engine, notifying the engine that it has successfully joined the management system;

[0032] S14, Periodic heartbeat reporting: after registration is completed, the engine sends a heartbeat message to the control center every 30 seconds to report its online state;

[0033] S15, Update survival state: the control center updates the "last survival time" or state flag of the engine in the database when receiving each heartbeat, so as to monitor and schedule.

[0034] Further, the engine configuration file comprises the following steps:

[0035] S21, Address information part engineParam of the control center: giving the address information of the control center service;

[0036] S22, Address information part proxyEngine of the local proxy engine: giving the address information of the proxy engine, and the position of the mutual transmission file of the control center and the proxy engine;

[0037] S23, Configuration information part EngineInst of the engine instance: giving the program instance information of each managed program instance, including the name of the program instance, the executable file position, and whether it is a multi-instance program.

[0038] Further, the program instance control comprises the following steps:

[0039] S31, Query current engine and instance state;

[0040] S32, data and file transmission, transmitting files from the control center to the agent engine, or transmitting the running parameters of the program instance;

[0041] S33, task distribution, i.e. starting a specified program instance to execute the related design task;

[0042] S34, forcibly terminating the specified task;

[0043] S35, the engine returns the output file and running result of the program instance to the control center for storage or analysis.

[0044] Further, the execution across software includes the following steps:

[0045] S51, the user initiates a design request in the control center system, thereby forming a "user design flow", which clearly specifies the program instance required to be executed at each step, and the current only supports the sequential execution of steps;

[0046] S52, which is received and parsed by the control center to generate an executable flow step sequence;

[0047] S53, the control center calls the API of the communication agent engine to distribute the flow instructions to the specified software to perform specific calculation or design tasks;

[0048] S54, after the software is executed, the result data is output to the data bus of the platform for subsequent routing and distribution;

[0049] S55, the data bus routes the output content of the software result of the previous step to the software of the next step according to the flow configuration;

[0050] S56, after the last step is run, the final result of each step is stored and displayed or analyzed through the front end.

[0051] The beneficial effects of the present application are as follows:

[0052] 1. Heterogeneous integration breakthrough: through 5 communication modes, API / command line / file type software is adapted, different heterogeneous software can support one of the communication modes, and the integration cost is significantly reduced.

[0053] 2. Dynamic scalability: new software modules only need to deploy agent engines and configure registration, and the platform can be upgraded without downtime.

[0054] 3. High concurrency reliability: the instance mechanism solves resource conflicts and improves the efficiency of parallel tasks.

[0055] 4. Full-process automation: the execution time of cross-software design flow is significantly shortened. BRIEF DESCRIPTION OF DRAWINGS

[0056] Figure 1 is a system architecture diagram of the present application;

[0057] Figure 2 is a dynamic registration flow diagram of the present application;

[0058] Figure 3 is a system deployment diagram of the present application;

[0059] Figure 4 is a method flow diagram of the present application;

[0060] Figure 5 is a method diagram of dynamic registration of the present application;

[0061] Figure 6 is a flow diagram of engine configuration file of the present application;

[0062] Figure 7 is a flow diagram of program instance control of the present application;

[0063] Figure 8 is a flow diagram of executing cross-software of the present application. DETAILED DESCRIPTION

[0064] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application.

[0065] Please refer to Figure 1 - Figure 3 The present application provides an integrated design management system with automatic registration of communication agent engine, comprising:

[0066] Control center: browser-based Web interface, providing management of communication agent engine on different nodes, control of heterogeneous software (such as starting, stopping, data saving, data export and data transmission), supporting process design between heterogeneous software, realizing user management, process scheduling and task allocation;

[0067] Communication agent engine: used for connecting control center and local software module, deployed on the same host node (Windows / Linux) with each heterogeneous software module, and each communication agent engine is deployed on different host to manage related heterogeneous software on the host; each engine is automatically registered to the control center through configuration file information when starting; the communication mode between communication agent engine and each software supports multiple docking modes; the communication agent engine provides standardized RESTful API (task start / stop, file transmission, state query) to the outside, satisfying the control of each heterogeneous software by the control center through API;

[0068] Multiple heterogeneous software modules: each heterogeneous software needs to support at least one docking mode, or encapsulate the original independent software to support one of the docking modes.

[0069] In this embodiment, preferably, the control center comprises:

[0070] The registration and resource management module is used for receiving an engine registration request, parsing the content of engineConfig.yaml, checking the field legality, recording the engine network address and program instance information, establishing a primary key index, associating the running state (idle, running, failure, etc.) and time stamp of each instance, responding to a heartbeat request and updating the engine state, supporting online and offline judgment and alarm;

[0071] The process arrangement and task scheduling module allows users to customize the process (specify the program instance in the process step) on the front end; the control center schedules the process steps in sequence, controls the process to automatically advance backward; the state (queued, running, completed, failed) of each process step is visualized; the task retry, manual termination and other operation and maintenance interfaces are provided;

[0072] The result return and storage module returns the result data to the control center after each process step is completed; the control center uniformly stores the result in the file system or the database; the database uses a relational database as the main database, uniformly stores the proxy engine registration information, program instance state, user process data, and forms a task execution log; the front end supports users to view the running state in real time, download the result or graphically display.

[0073] In this embodiment, preferably, the communication proxy engine comprises:

[0074] The registration module is used for automatically reading engineConfig.yaml; sending the engine meta information to the control center / api / register through the HTTP protocol; if the registration fails, the registration is retried and the log is written; after the registration is successful, the running state is entered and the heartbeat thread is started;

[0075] The task execution management module finds the corresponding program path according to the specified program instance name instName after receiving the / api / dispatch request, judges whether it is a multi-instance program, constructs an execution command and starts a sub-process, listens to the sub-process state, collects logs; after the program ends, the output files are packaged and returned to the control center through / api / result.

[0076] In this embodiment, preferably, the docking mode in the communication proxy engine is divided into sub-process control, API calling, file monitoring, embedded interaction and manual triggering.

[0077] In this embodiment, preferably, the heterogeneous software in the plurality of heterogeneous software modules is industrial design software such as UG NX software, simulation tools (such as ANSYS), optimization design programs, or self-developed software or products.

[0078] Working principle and use process of the application:

[0079] First, the communication agent engine automatically reads the local engineConfig.yaml configuration file at startup, parses the engine meta information (such as host address, software instance path, etc.) therein, and sends registration data to the / api / register interface of the control center through an HTTP POST request.

[0080] After receiving the request, the registration and resource management module of the control center checks the field legality, stores the engine information into a relational database, establishes a primary key index to associate the running state (such as idle, running or failure), and responds to the registration success confirmation. After registration is completed, the agent engine starts the heartbeat thread, periodically sends state updates to the control center, and ensures that the control center monitors the engine online state in real time; if the heartbeat times out, the control center marks the engine as offline and triggers an alarm notification.

[0081] When the user uses the system, the user accesses the Web interface of the control center through a browser. After logging in, the user can view all registered communication agent engines and their associated heterogeneous software modules (such as UG NX, ANSYS or optimization design programs) on the front end. The user designs a custom workflow through the process orchestration and task scheduling module: adds process steps, specifies target software instances and input parameters (such as file paths or calculation variables), defines output requirements (such as data files or status reports). After the design is completed, the user starts the process, and the control center schedules the tasks in sequence: sends task instructions (such as start / stop commands or file transfer requests) to the / api / dispatch interface of the corresponding agent engine through RESTful API.

[0082] The task execution management module of the communication agent engine receives the instruction, finds the target software path according to the configuration file, judges whether it is a multi-instance program, and performs operations based on the connection mode: for the sub-process control mode, the software sub-process is started and its running state is monitored, and real-time logs are collected; for the API calling mode, the interface of the software is directly called to complete the operation. During the task execution, the agent engine listens to the sub-process or API response, and once it is completed, the output data is packaged and returned to the control center through the / api / result interface. The result return and storage module of the control center receives the data, which is uniformly stored in the file system or database, the task state (such as completion or failure) is updated, and the execution log is generated. Users can visualize the process state (such as step queuing or running) in real time on the front end, support downloading of result files, viewing of logs or data graphic display. If the task fails, the control center automatically retries or provides a manual termination interface; the whole system realizes the automatic integration of heterogeneous software, improves the efficiency and reliability of the design process.

[0083] Through the combination and cooperation of the above components, the automatic integration of heterogeneous software can be realized, the seamless execution of complex design processes is supported, and the efficiency and system reliability of multi-node cooperation are effectively improved; the control center uniformly schedules tasks through standardized APIs, the communication agent engine responds to instructions in real time and manages local software execution, the heterogeneous modules are flexibly adapted based on diversified connection modes, ensuring efficient data transmission and state synchronization between processes, ultimately forming a closed-loop design management environment, reducing manual operation errors and accelerating product development cycles.

[0084] Please refer to Figure 4 Figure 8 The application also provides an integrated design management method with an automatically registered communication agent engine, including the management system of any one of the above, including the following steps:

[0085] S1, dynamic registration, used for dynamic registration of information;

[0086] S2, engine configuration file: used for reading the information of the engine configuration file when the agent engine starts;

[0087] S3, program instance control, after the communication agent engine is successfully registered, the control center manages and schedules related instances of each agent engine;

[0088] S4, multi-instance concurrent control, used for coordinating the parallel execution of multiple program instances through sub-process control or API calling, ensuring reasonable allocation of resources and avoiding conflicts;

[0089] ​S5, cross-software execution, for coordinating and driving the execution of cross-software tasks, realizing data transmission, command execution and process automation between different heterogeneous software (such as UG NX, ANSYS simulation tools or self-developed optimization programs) through a specified interfacing mode such as API calling, file monitoring or embedded interaction, ensuring the coherence and interoperability of design, simulation and optimization operations;

[0090] S6, task execution management: after receiving a task request, an execution command is constructed according to a specified instance path, a sub-process is started and its state is listened to in real time, and operation logs are collected at the same time;

[0091] S7, result processing: after the task is completed, the output files are automatically packaged and returned to the control center through the API interface to complete the closed-loop management;

[0092] S8, exception handling and monitoring, for real-time detection of errors or conflicts in the execution process, automatic retry, suspension or notification of the control center for intervention through the preset rules of the engine configuration file, to ensure system stability and task reliability.

[0093] In this embodiment, the dynamic registration preferably includes the following steps:

[0094] S11, engine start registration: when the agent engine starts, the engine configuration file information is read, the heterogeneous software information of the node is obtained, each heterogeneous software is a program instance of the engine, and then a registration request is sent to the control center;

[0095] S12, control center stores engine information: after receiving the registration request, the control center first checks the legality of the engine information in its own database, and then stores the registration information of the engine identifier, network address and supported program instances persistently;

[0096] S13, registration success response: after storage is completed, the control center returns a registration success response to the engine, notifying the engine that it has successfully joined the management system;

[0097] S14, periodic heartbeat reporting: after registration is completed, the engine sends a heartbeat message to the control center every 30 seconds to report its online state;

[0098] S15, update survival state: the control center updates the "last survival time" or state flag of the engine in the database when receiving each heartbeat, for monitoring and scheduling.

[0099] In this embodiment, the engine configuration file preferably includes the following steps:

[0100] S21, address information part engineParam of the control center: gives the address information of the control center service;

[0101] S22, address information part of the local proxy engine proxyEngine: gives the address information of the proxy engine, and the location of the mutual transmission of files between the control center and the local proxy engine;

[0102] S23, configuration information part of the engine instance EngineInst: gives the information of each managed program instance, including the name of the program instance, the location of the executable file, and whether it is a multi-instance program.

[0103] In this embodiment, the program instance control preferably includes the following steps:

[0104] S31, query the current engine and instance state;

[0105] S32, data and file transmission, transmit files from the control center to the proxy engine, or transmit the running parameters of the program instance;

[0106] S33, task delivery, i.e. starting a specified program instance to execute the related design task;

[0107] S34, forcibly terminate the specified task;

[0108] S35, the engine returns the output file and running result of the program instance to the control center for saving or analysis.

[0109] In this embodiment, the execution of cross-software preferably includes the following steps:

[0110] S51, the user initiates a design request in the control center system, thereby forming a "user design flow", which clearly specifies the program instance required to be executed at each step, and the current only supports the sequential execution of steps;

[0111] S52, which is received and parsed by the control center to generate an executable flow step sequence;

[0112] S53, the control center calls the API of the communication proxy engine to deliver the flow instructions to the specified software to perform specific calculation or design tasks;

[0113] S54, after the software is executed, the result data is output to the data bus of the platform for subsequent routing and distribution;

[0114] S55, the data bus routes the output content of the software result of the previous step to the software of the next step according to the flow configuration;

[0115] S56, after the last step is run, the final result of each step is stored and displayed or analyzed through the front end.

[0116] Through the above method steps, seamless integration and automatic collaboration between heterogeneous software can be realized, and the overall efficiency and reliability of the design, simulation and optimization process can be effectively improved. The dynamic registration mechanism ensures the instant availability of the agent engine, the engine configuration file provides flexible parameter management, the program instance control realizes precise scheduling, the multi-instance concurrent control optimizes the resource utilization rate, the execution cross-software function breaks the software barrier, the task execution management guarantees the real-time and controllability of task execution, the result processing realizes closed-loop feedback, the exception processing and monitoring enhance the robustness and fault tolerance of the system; manual intervention can be significantly reduced, the risk of operation conflict can be reduced, and automatic execution of large-scale complex engineering tasks can be supported, thereby improving the consistency and traceability of product development cycle.

[0117] The above description of disclosed embodiments enables one of ordinary skill in the art to make or use the application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An integrated design management system with an auto-registration communication agent engine, characterized by, Comprise: Control center: browser-based web interface, providing management of communication agent engines on different nodes, control of heterogeneous software (such as starting, stopping, data saving, data export and data transmission), supporting process design between heterogeneous software, realizing user management, process scheduling and task allocation; Communication agent engine: used to connect the control center and the local software module, deployed on the same host node (Windows / Linux) as each heterogeneous software module, and each communication agent engine is deployed on a different host to manage the related heterogeneous software on the host; each engine is automatically registered to the control center through the configuration file information when it starts; the communication agent engine supports multiple docking modes in communication with each software; The communication agent engine provides standardized RESTful API (task start and stop, file transfer, state query) to the outside, meeting the control center's control of each heterogeneous software through API; A variety of heterogeneous software modules: each heterogeneous software needs to support at least one docking mode, or encapsulate and transform the original independent software to support one of the docking modes.

2. The integrated design management system with automatic registration of communication agents engine of claim 1, wherein, The control center comprises: A registration and resource management module for receiving engine registration requests, parsing engineConfig.yaml content, verifying field legality, recording engine network address and program instance information, establishing a primary key index, associating each instance with a running state (idle, running, fault, etc.) and a timestamp, responding to heartbeat requests and updating engine state, supporting online and offline judgment and alarm; A process arrangement and task scheduling module, users can customize the process (specify program instances in process steps) on the front end; the control center schedules the process steps in order and controls the process to automatically advance backward; each process step state (queued, running, completed, failed) is visualized; it has task retry, manual termination and other operation and maintenance interfaces; A result return and storage module, after each process step is completed, the agent engine returns the result data; the control center stores it uniformly in the file system or the database, the database uses a relational database as the main database, uniformly stores agent engine registration information, program instance state, user process data, and forms a task execution log; the front end supports users to view the running state in real time, download the result or graphically display.

3. The integrated design management system with automatic registration of communication agents engine of claim 1, wherein, The communication agent engine comprises: A registration module for automatically reading engineConfig.yaml; sending engine meta information to the control center / api / register through HTTP protocol; if it fails, it will retry and write log; after successful registration, it enters the running state and starts the heartbeat thread; A task execution management module: after receiving the / api / dispatch request, it finds the corresponding program path according to the specified program instance name instName, judges whether it is a multi-instance program, constructs the execution command and starts the child process, listens to the child process state, collects logs; after the program ends, it packs the output file and returns to the control center through / api / result.

4. The integrated design management system with automatic registration of communication agents engine of claim 1, wherein, The docking mode in the communication agent engine is divided into sub-process control, API calling, file monitoring, embedded interaction and manual triggering.

5. The integrated design management system with automatic registration of communication agents engine of claim 1, wherein, The heterogeneous software in the plurality of heterogeneous software modules is industrial design software such as UG NX software, simulation tools (such as ANSYS), optimization design programs, or self-developed software or products.

6. A method of integrated design management with an automatically registering communication agent engine, comprising the management system of any one of claims 1-5, characterized in that, The method comprises the following steps: S1, dynamic registration, for dynamic registration of information; S2, engine configuration file: for reading the information of the engine configuration file when the proxy engine starts; S3, program instance control, after the communication proxy engine is registered successfully, the control center manages and schedules the related instances of each proxy engine; S4, multi-instance concurrent control, for coordinating the parallel execution of multiple program instances through sub-process control or API call to ensure reasonable allocation of resources and avoid conflicts; S5, cross-software execution, for coordinating and driving cross-software tasks, through a specified docking mode such as API call, file monitoring or embedded interaction, data transmission, command execution and process automation between different heterogeneous software (such as UG NX, ANSYS simulation tools or self-developed optimization programs) are realized, ensuring the coherence and interoperability of design, simulation and optimization operations; S6, task execution management: after receiving the task request, the execution command is constructed according to the specified instance path, the sub-process is started and its state is listened to in real time, and the running log is collected; S7, result processing: after the task is completed, the output files are automatically packaged and returned to the control center through the API interface to complete the closed-loop management; S8, exception handling and monitoring, for real-time detection of errors or conflicts in the execution process, automatic retry, suspension or notification of the control center for intervention through the preset rules of the engine configuration file, to ensure system stability and task reliability.

7. A method for managing an integrated design having an automatic registration communication agent engine according to claim 6, wherein, The dynamic registration comprises the following steps: S11, engine start registration: when the proxy engine starts, the engine configuration file information is read, the heterogeneous software information of the node is obtained, each heterogeneous software is a program instance of the engine, and then a registration request is sent to the control center; S12, control center stores engine information: after receiving the registration request, the control center first checks the legality of the engine information in its own database, and then stores the identification, network address and supported program instances of the engine and other registration information persistently; S13, registration success response: after storage is completed, the control center returns a registration success response to the engine, notifying the engine that it has successfully joined the management system; S14, periodic heartbeat reporting: after registration is completed, the engine sends a heartbeat message to the control center every 30 seconds to report its online status; S15, update survival state: the control center updates the "last survival time" or state flag of the engine in the database when receiving each heartbeat, so as to monitor and schedule.

8. A method for managing an integrated design having an automatic registration communication agent engine according to claim 6, wherein, The engine configuration file comprises the following steps: S21, address information part engineParam of the control center: giving the address information of the control center service; S22, address information part proxyEngine of the local proxy engine: giving the address information of the proxy engine, and the position of the mutual transmission file of the control center and the proxy engine; S23, the configuration information part EngineInst of the engine instance: gives the information of each managed program instance, including the name of the program instance, the executable file location, and whether it is a multi-instance program.

9. The integrated design and management method for an automatically registered communication agent engine according to claim 6, characterized in that, The program instance control includes the following steps: S31, query the current engine and instance state; S32, data and file transmission, transmit files from the control center to the agent engine, or transmit the running parameters of the program instance; S33, task delivery, i.e. starting a specified program instance to execute the related design task; S34, forcibly terminate the specified task; S35, the engine returns the output file and running result of the program instance to the control center for saving or analysis.

10. The method of claim 6, wherein the integrated design management having an automatic registration communication agent engine is characterized by, The execution across software includes the following steps: S51, the user initiates a design request in the control center system, thereby forming a "user design flow", which clearly specifies the program instance required to be executed at each step, and at present only supports the sequential execution of steps; S52, which is received and parsed by the control center to generate an executable flow step sequence; S53, the control center calls the API of the communication agent engine to deliver the flow instructions to the specified software to perform specific calculation or design tasks; S54, after the software is executed, the result data is output to the data bus of the platform for subsequent routing and distribution; S55, the data bus routes the output content of the software result of the previous step to the software of the next step according to the flow configuration; S56, after the last step is run, the final results of each step are stored and displayed or analyzed through the front end.

Images