Method, system and storage medium for deployment testing of industrial applications

Abstract

The embodiment of the application discloses a kind of deployment test method, system and storage medium of industrial application program.Therein, method includes: the Docker image corresponding to current industrial application program is built, the Docker image includes code file, code runtime and code dependency;The Docker image is packed into application file;The application file is provided to industrial edge simulator simulating an industrial edge device for testing, and test result is obtained;The industrial edge simulator includes device information configuration interface, industrial communication protocol configuration interface and data source configuration interface, and the industrial edge simulator is simulated into corresponding industrial edge device by configuring device information configuration interface, industrial communication protocol configuration interface and data source configuration interface.The technical scheme in the embodiment of the application can improve the deployment efficiency of industrial application program.

Description

Technical Field

[0001] This invention relates to the industrial field, and in particular to a method, system, and computer-readable storage medium for deploying and testing industrial applications. Background Technology

[0002] Currently, when developing applications (Apps), some software platforms provide users with application development tools, which users can use to deploy, purchase, and develop applications.

[0003] Patent application CN109614108A discloses an automated deployment and testing method for Docker-based applications. This method utilizes GitHub, Jenkins, Docker, and automated deployment scripts to automate the packaging, testing, and deployment of applications. However, while code files can be automatically packaged into the deployment package, all dependencies and the code runtime environment are manually pre-configured by the user and do not automatically change with modifications to the code files. Furthermore, this method is designed for general application development and lacks support for industrial technologies, thus making it unsuitable for testing industrial applications.

[0004] Therefore, those skilled in the art are also working to find deployment solutions for industrial applications. Summary of the Invention

[0005] In view of this, this invention provides, on the one hand, a deployment testing method for industrial applications, and on the other hand, a deployment testing system and a computer-readable storage medium for industrial applications, in order to improve the deployment efficiency of industrial applications.

[0006] An industrial application deployment and testing method proposed in this embodiment of the invention includes: constructing a Docker image corresponding to the current industrial application, wherein the Docker image contains code files, code runtime, and code dependencies; packaging the Docker image into an application file; providing the application file to an industrial edge simulator simulating an industrial edge device for testing, and obtaining test results; wherein the industrial edge simulator includes a device information configuration interface, an industrial communication protocol configuration interface, and a data source configuration interface, and by configuring the device information configuration interface, the industrial communication protocol configuration interface, and the data source configuration interface, the industrial edge simulator simulates the corresponding industrial edge device.

[0007] In one implementation, building a Docker image corresponding to the current industrial application includes: analyzing the code files of the current industrial application, determining the code dependencies that need to be run based on the dependency tags, determining the target services that need to be configured for the code dependencies based on the service items under the dependency tags; calling the corresponding code dependency modules from a dependency library that pre-stores various code dependency modules based on the determined code dependencies, configuring the corresponding target services for the called code dependency modules based on the determined target services, and obtaining instantiated code dependencies; and layering the instantiated code dependencies, the runtime code, and the code files in a Docker container to obtain a Docker image corresponding to the current industrial application.

[0008] In one embodiment, the industrial edge simulator stores pre-collected data from various data sources for testing; or, the industrial edge simulator is capable of reading pre-collected data from various data sources for testing from external memory.

[0009] An industrial application deployment and testing system proposed in this embodiment of the invention includes: a Docker image building module for building a Docker image corresponding to the current industrial application, wherein the Docker image contains code files, code runtime, and code dependencies; a file packaging module for packaging the Docker image into an application file; and an industrial edge simulator, which includes a device information configuration interface, an industrial communication protocol configuration interface, and a data source configuration interface. By configuring the device information configuration interface, the industrial communication protocol configuration interface, and the data source configuration interface, the industrial edge simulator simulates the corresponding industrial edge device to test the application file and obtain corresponding test results.

[0010] In one implementation, the Docker image building module includes: a dependency library storing various code dependency modules, each stored as a Docker image; a code analyzer analyzing the code files of the current industrial application, determining the code dependencies to be run based on dependency tags, and determining the target services to be configured for the code dependencies based on the service items under the dependency tags; and an application builder calling the corresponding code dependency modules from the pre-stored dependency library based on the determined code dependencies, configuring the corresponding target services for the called code dependency modules based on the determined target services, thereby obtaining instantiated code dependencies; and layering the instantiated code dependencies, the runtime code, and the code files in a Docker container to obtain a Docker image corresponding to the current industrial application.

[0011] In one embodiment, the industrial edge simulator stores pre-collected data from various data sources for testing; or, the industrial edge simulator is capable of reading pre-collected data from various data sources for testing from external memory.

[0012] In one embodiment, it further includes: an interface module for providing a human-machine interface, receiving a code file of the current industrial application input by the user through the human-machine interface, and providing the code file to the code analyzer; and presenting the running status and test results of the industrial edge simulator on the current application file through the human-machine interface.

[0013] An industrial application deployment testing system proposed in this embodiment of the invention includes: at least one memory and at least one processor, wherein: the at least one memory is used to store a computer program; and the at least one processor is used to call the computer program stored in the at least one memory to execute the industrial application deployment testing method as described in any of the above embodiments.

[0014] An embodiment of the present invention provides a computer-readable storage medium storing a computer program thereon; the computer program can be executed by a processor to implement the deployment and testing method of the industrial application described in any of the above embodiments.

[0015] As can be seen from the above solution, because an industrial edge simulator is set up in this embodiment of the invention to simulate various industrial edge devices, the APP file can be directly tested to test its usability, without having to go through the process of uploading the APP file to the edge management tool and then downloading it from the edge management tool to the industrial edge device. This allows users to determine the usability of the APP based on the test results of the industrial edge simulator, improving the deployment efficiency of industrial applications. Furthermore, if problems are found during testing, the APP file can be iteratively developed, thereby shortening the development cycle.

[0016] Furthermore, by setting up a dependency library to store all code dependencies and automatically analyzing the code, the system retrieves the corresponding code dependencies from the library based on the analysis results, configures the retrieved code dependencies, and automatically stacks the configured code dependencies, code, and runtime to form a Docker image of the running code files. This greatly simplifies the complexity of deploying industrial applications for users. Attached Figure Description

[0017] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which will make the above and other features and advantages of the present invention more apparent to those skilled in the art. In the drawings:

[0018] Figure 1 These are exemplary flowcharts of a deployment and testing method for an industrial application according to an embodiment of the present invention.

[0019] Figure 2 This is a flowchart illustrating a deployment and testing method for an industrial application in an example of the present invention.

[0020] Figure 3 This is an exemplary structural diagram of a deployment and testing system for an industrial application according to an embodiment of the present invention.

[0021] Figure 4 This is an exemplary structural diagram of a deployment and testing system for an industrial application, as described in another embodiment of the present invention.

[0022] The accompanying figure is labeled as follows:

[0023]

[0024] Detailed Implementation

[0025] In this embodiment of the invention, considering the existence of a software platform called Industrial Edge, users can deploy custom applications based on this platform, which typically includes the following four steps: 1) Building a Docker image in the Docker engine. The Docker image contains code files, runtime code, and code dependencies. The runtime code refers to the language foundation, framework, or platform on which the code runs, typically referring to what is necessary during runtime. Code dependencies refer to databases, servers, or communication protocols that the code depends on or involves during runtime. 2) Using a publishing tool, such as an App Publisher, packaging the Docker image into an App file, and then exporting the App file. 3) Uploading the App file to the Edge Management Tool. 4) Downloading the App file from the Edge Management Tool to the industrial edge device and running it.

[0026] However, in practical applications, users may encounter a lengthy verification cycle during the application deployment process described above. Due to differences in the operating environments of edge devices and development PCs, an application that runs correctly on a development PC may not run correctly on an edge device. However, users cannot verify the application before performing the four deployment steps and running it on the edge device. If any error occurs in the final step, the user must redo the entire process. Therefore, in this embodiment of the invention, an industrial edge simulator is considered to simulate various industrial edge devices, thereby testing the application's usability. This allows users to iterate on the application development based on the test results from the industrial edge simulator, thus shortening the development cycle.

[0027] Furthermore, considering that users may encounter the time-consuming process of building Docker images during the application deployment process, as they need to first pull a Docker image and manually put the code, runtime code, and code dependencies into it, this embodiment of the invention considers setting up a dependency library to store various code dependencies. By analyzing the code, the corresponding code dependencies are called based on the analysis results, and the called dependencies are configured. The configured dependencies, code, and runtime are then layered to form a Docker image containing the running code files.

[0028] To make the objectives, technical solutions, and advantages of the present invention clearer, the following embodiments are provided to further illustrate the present invention in detail.

[0029] Figure 1 This is an exemplary flowchart of a deployment and testing method for an industrial application according to an embodiment of the present invention. Figure 1 As shown, the method may include the following steps:

[0030] Step S10: Build a Docker image corresponding to the current industrial application. The Docker image contains code files, code runtime, and code dependencies.

[0031] In this step, you can manually build the Docker image corresponding to the current industrial application using existing methods. Alternatively, you can build the Docker image using the following method.

[0032] Step S11: Analyze the code file of the current industrial application, determine the code dependencies (such as database, server or communication protocol, etc.) that need to be run based on the dependency tags, and determine the target service that needs to be configured for the code dependencies based on the service items under the dependency tags.

[0033] For example, Figure 2 This is an exemplary flowchart of a deployment and testing method for an industrial application, as exemplified in this invention. Figure 2 As shown, the code file CF can be provided to a code analyzer 21, which will then analyze the code file. Figure 2 The top left corner shows a portion of the code in the CF file. Tag 1 corresponds to a MySQL database dependency, with a specified connection port (Connect(url,port)). It instructs the creation of a new table (TABLE1) in the MySQL database, containing entries 1, 2, 3, ... (item1, item2, item3, ...). Tag 2 corresponds to the MQTT protocol dependency, with a specified connection port (Connect(ip, port)); ...

[0034] By analyzing the code file F, it can be determined that... Figure 2 The code dependencies D shown in the lower left corner include: MySQL, MQTT, ... For MySQL, the target services that need to be configured are: 1) Connection port (Connect(url,port)); 2) Create a new table 1 (TABLE1), which includes items 1, 2, 3, ... (item1, item2, item3, ...). For MQTT, the target services that need to be configured are: 1) Connection port (Connect(ip,port)); ...

[0035] Step S12: Based on the determined code dependencies, call the corresponding code dependency module from the dependency library that pre-stores various code dependency modules.

[0036] In this embodiment, the dependency library 22 can store various code dependencies, such as various runtime RTs like Python, various communication protocols CPs like MQTT, various databases DBs like MySQL, various operating systems OSs like Debian, various kernels KNs like the Linux kernel, etc. In addition, there can be other code dependencies, which are not limited here.

[0037] like Figure 2 As shown, for Figure 2 The code dependencies identified on the left can be called by the application builder 23 from the dependency library 22, such as the MySQL module, MQTT module, etc. In addition, the Linux operating system and kernel are also called.

[0038] Step S13: Based on the determined target service, configure the corresponding target service for the called code dependency module to obtain the instantiated code dependency.

[0039] like Figure 2 As shown below, the application builder 23 can set the port for the MySQL database (Set DBurl and port); if the database exists, it creates a table containing items 1, ... (create table(item1, ...)); otherwise, it first creates the database (create db first), and then creates the table containing items 1, ... (create table(item1, ...)). For the MQTT protocol, it sets the port (Set MQTTbroker ip.port) and modifies the configuration file.

[0040] Step S14: Stack the instantiated code dependencies, code runtime, and code files layer by layer in the Docker container to obtain the Docker image corresponding to the current industrial application.

[0041] like Figure 2 As shown, the application builder 23 can stack instantiated code dependencies, code runtime, and code files layer by layer within a Docker container.

[0042] Step S20: Package the Docker image into the application file.

[0043] In this step, an application publisher can be used to package the Docker image into the application file AF.

[0044] Step S30: The application file is provided to an industrial edge simulator 24 simulating an industrial edge device for testing, and a test result Rs is obtained. The industrial edge simulator includes a device information configuration interface 241, an industrial communication protocol configuration interface 242, a data source configuration interface 243, and an application runtime module 244. By configuring the device information configuration interface 241, the industrial communication protocol configuration interface 242, and the data source configuration interface 243, the industrial edge simulator simulates the corresponding industrial edge device. In practical applications, the test result Rs can indicate whether the application is usable or it can indicate an error. If an error occurs, the user can iteratively develop the application's code file CF, thereby shortening the development cycle.

[0045] The device information configuration interface 241 can be used to configure the current runtime operating system, such as IPC 127E, IPC 227E, IPC 427E, or IOT 2050.

[0046] The data source used for the current test can be configured through the data source configuration interface 243, such as a data source for offline testing collected from a programmable logic controller (PLC), a drive, a sensor, or a frequency converter.

[0047] The industrial communication protocol configuration interface 242 can be used to configure the current industrial communication protocol, such as MQTT, RESTful, S7, OPC UA, or PROFINET IO. Specifically, the industrial communication protocol configuration interface 242 may include a data bus configuration interface and a field device connector configuration interface. The field device connector configuration interface can be used to configure data acquisition protocols such as S7, OPC UA, or PROFINET IO to read data from the data source according to the configured protocol, simulating interaction with field devices. The data bus configuration interface can be used to configure protocols such as MQTT or RESTful to distribute the read data from the data source to the application program.

[0048] The deployment and testing method for industrial applications in the embodiments of the present invention has been described in detail above. The deployment and testing system for industrial applications in the embodiments of the present invention will now be described in detail. The deployment and testing system for industrial applications in the embodiments of the present invention can be used to implement the deployment and testing method for industrial applications in the embodiments of the present invention. For details not disclosed in detail in the system embodiments of the present invention, please refer to the corresponding descriptions in the method embodiments of the present invention, which will not be repeated here.

[0049] Figure 3 This is an exemplary structural diagram of a deployment and testing system for an industrial application according to an embodiment of the present invention. Figure 3 As shown, the system may include: a Docker image building module 31, a file packaging module 32, and an industrial edge simulator 24.

[0050] The Docker image building module 31 is used to build a Docker image corresponding to the current industrial application. The Docker image contains code files, code runtime, and code dependencies.

[0051] The file packaging module 32 is used to package the Docker image into an application file;

[0052] The industrial edge simulator 24 is used to simulate an industrial edge device to test the application file and obtain corresponding test results. The structure of the industrial edge simulator 24 can be as follows: Figure 4As shown, it includes a device information configuration interface 241, an industrial communication protocol configuration interface 242, a data source configuration interface 243, and an application file execution module 244. By configuring the device information configuration interface 241, the industrial communication protocol configuration interface 242, and the data source configuration interface 243, the industrial edge simulator can simulate the corresponding industrial edge device.

[0053] The device information configuration interface 241 is used to configure the current runtime operating system, such as IPC 127E, IPC227E, IPC 427E, or IOT 2050.

[0054] The industrial communication protocol configuration interface 242 is used to configure the current industrial communication protocol, such as MQTT, RESTful, S7, OPC UA, or PROFINET IO. In a specific implementation, the industrial communication protocol configuration interface 242 may include a data bus configuration interface 2421 and a field device connector configuration interface 2422. The data bus configuration interface 2421 can be used to configure protocols such as MQTT or RESTful, while the field device connector configuration interface 2422 can be used to configure protocols such as S7, OPC UA, or PROFINET IO.

[0055] The data source configuration interface 243 is used to configure the data source used in the current test, such as a programmable logic controller (PLC), driver, or sensor.

[0056] The program file execution module 244 is used to run the application file and output the corresponding running status and test results.

[0057] In other embodiments, the industrial edge simulator 24 may also have a storage module (not shown) for storing pre-collected data from various data sources for testing; or, the industrial edge simulator 24 may also read pre-collected data from various data sources for testing from an external memory.

[0058] In one implementation, the Docker image building module 31 can be as follows: Figure 2 As shown, it includes: dependency library 22, code analyzer 21, and application builder 23.

[0059] The dependency library 22 stores various code dependency modules, each of which is stored as a Docker image.

[0060] The code analyzer 21 is used to analyze the code files of the current industrial application, determine the code dependencies that need to be run based on the dependency tags, and determine the target services that need to be configured for the code dependencies based on the service items under the dependency tags.

[0061] Application builder 23 is used to call the corresponding code dependency module from the dependency library that stores various code dependency modules in advance, according to the determined code dependency, and configure the corresponding target service for the called code dependency module according to the determined target service to obtain the instantiated code dependency; and stack each instantiated code dependency, as well as the code runtime and code file in the Docker container layer by layer to obtain the Docker image corresponding to the current industrial application.

[0062] In one embodiment, the industrial application deployment and testing system of the present invention may further include an interface module 33 for providing a human-machine interface, receiving the code file CF of the current industrial application input by the user through the human-machine interface, and providing the code file to the code analyzer 21; and presenting the running status and test results of the current application file by the industrial edge simulator 24 through the human-machine interface.

[0063] Figure 4 This is a schematic diagram of the structure of another industrial application deployment and testing system in this application embodiment, which can be used for implementation. Figure 1 The method or implementation shown Figure 3 The system shown. As... Figure 4 As shown, the system may include at least one memory 41, at least one processor 42, and at least one display 43. Additionally, it may include other components, such as communication ports. These components communicate via a bus 44.

[0064] At least one memory 41 is used to store a computer program. In one embodiment, the computer program can be understood to include... Figure 3 The diagram shows the various modules of the deployment and testing system for the industrial application. Additionally, at least one memory 41 can store an operating system, etc. Operating systems include, but are not limited to: Android, Symbian, Windows, Linux, etc.

[0065] At least one processor 42 is used to invoke a computer program stored in at least one memory 41 to execute the deployment and testing method of the industrial application described in this embodiment. The processor 42 can be a CPU, processing unit / module, ASIC, logic module, or programmable gate array, etc. It can receive and send data through the communication port.

[0066] Specifically, at least one processor 42 is used to invoke a computer program stored in at least one memory 41 to cause the system to perform operations in the deployment and testing method of the industrial application in any of the above embodiments.

[0067] At least one display 43 is used to display the human-computer interaction interface.

[0068] It should be noted that not all steps and modules in the above processes and structural diagrams are mandatory; some steps or modules can be omitted as needed. The execution order of the steps is not fixed and can be adjusted as required. The division of modules is merely for the convenience of description and functional division. In actual implementation, a module can be implemented by multiple modules, and the functions of multiple modules can also be implemented by the same module. These modules can be located in the same device or in different devices.

[0069] It is understood that the hardware modules in the above embodiments can be implemented mechanically or electronically. For example, a hardware module may include specially designed permanent circuits or logic devices (such as dedicated processors, such as FPGAs or ASICs) to perform specific operations. A hardware module may also include programmable logic devices or circuits (such as general-purpose processors or other programmable processors) temporarily configured by software to perform specific operations. The specific method used to implement the hardware module—whether it is mechanical, a dedicated permanent circuit, or a temporarily configured circuit (such as one configured by software)—can be determined based on cost and time considerations.

[0070] Furthermore, this application embodiment also provides a computer-readable storage medium storing a computer program that can be executed by a processor to implement the deployment and testing method for the industrial application described in this application embodiment. Specifically, a system or device equipped with a storage medium can be provided, on which software program code implementing the functions of any of the above embodiments is stored, and the computer (or CPU or MPU) of the system or device can read and execute the program code stored in the storage medium. In addition, the operating system or the like operating on the computer can be instructed based on the program code to perform some or all of the actual operations. The program code read from the storage medium can also be written to a memory provided in an expansion board inserted into the computer or to a memory provided in an expansion unit connected to the computer, and then the CPU or the like installed on the expansion board or expansion unit can be instructed based on the program code to execute some and all of the actual operations, thereby realizing the functions of any of the above embodiments. The storage medium embodiments for providing program code include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer via a communication network.

[0071] As can be seen from the above solution, because an industrial edge simulator is set up in this embodiment of the invention to simulate various industrial edge devices, the APP file can be directly tested to test its usability, without having to go through the process of uploading the APP file to the edge management tool and then downloading it from the edge management tool to the industrial edge device. This allows users to determine the usability of the APP based on the test results of the industrial edge simulator, simplifying the deployment process of industrial applications and improving deployment efficiency. Furthermore, if problems are found during testing, the APP file can be iteratively developed, thereby shortening the development cycle.

[0072] Furthermore, by setting up a dependency library to store all code dependencies and automatically analyzing the code, the system retrieves the corresponding code dependencies from the library based on the analysis results, configures the retrieved code dependencies, and automatically stacks the configured code dependencies, code, and runtime to form a Docker image of the running code files. This greatly simplifies the complexity of deploying industrial applications for users.

[0073] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A deployment testing method for industrial applications, characterized in that, include: Build a Docker image corresponding to the current industrial application, wherein the Docker image contains code files, code runtime, and code dependencies; Package the Docker image into the application file; The application file is provided to an industrial edge simulator that simulates an industrial edge device for testing, and the test results are obtained. The industrial edge simulator includes a device information configuration interface, an industrial communication protocol configuration interface, and a data source configuration interface. By configuring the device information configuration interface, the industrial communication protocol configuration interface, and the data source configuration interface, the industrial edge simulator can simulate the corresponding industrial edge device. The construction of the Docker image corresponding to the current industrial application includes: The code files of the current industrial application are analyzed, and the code dependencies that need to be run are determined based on the dependency tags. Based on the service items under the dependency tags, the target services that need to be configured for the code dependencies are determined. Based on the determined code dependencies, the corresponding code dependency module is called from the dependency library that pre-stores various code dependency modules. Based on the determined target service, the corresponding target service is configured for the called code dependency module to obtain the instantiated code dependency. The instantiated code dependencies, code runtime, and code files are layered on top of each other in a Docker container to obtain the Docker image corresponding to the current industrial application.

2. The deployment and testing method for industrial applications according to claim 1, characterized in that, The industrial edge simulator stores pre-collected data from various data sources for testing; or, the industrial edge simulator is capable of reading pre-collected data from various data sources for testing from external memory.

3. A deployment and testing system for industrial applications, characterized in that, include: The Docker image building module is used to build Docker images corresponding to the current industrial application. The Docker image contains code files, code runtime, and code dependencies. The file packaging module is used to package the Docker image into the application file; An industrial edge simulator includes a device information configuration interface, an industrial communication protocol configuration interface, and a data source configuration interface. By configuring the device information configuration interface, the industrial communication protocol configuration interface, and the data source configuration interface, the industrial edge simulator can simulate a corresponding industrial edge device to test the application file and obtain the corresponding test results. The Docker image building module includes: The dependency library stores various code dependency modules, each of which is stored as a Docker image. The code analyzer is used to analyze the code files of the current industrial application, determine the code dependencies that need to be run based on the dependency tags, and determine the target services that need to be configured for the code dependencies based on the service items under the dependency tags. The application builder is used to call the corresponding code dependency modules from the dependency library that stores various code dependency modules based on the determined code dependencies. Based on the determined target service, it configures the corresponding target service for the called code dependency modules to obtain instantiated code dependencies. The instantiated code dependencies, as well as the code runtime and code files, are stacked layer by layer in a Docker container to obtain the Docker image corresponding to the current industrial application.

4. The deployment and testing system for industrial applications according to claim 3, characterized in that, The industrial edge simulator stores pre-collected data from various data sources for testing; or, the industrial edge simulator is capable of reading pre-collected data from various data sources for testing from external memory.

5. The deployment and testing system for industrial applications according to claim 3, characterized in that, Further includes: The interface module is used to provide a human-machine interface, through which the code file of the current industrial application input by the user is received, and the code file is provided to the code analyzer; The human-computer interaction interface presents the running status and test results of the current application file by the industrial edge simulator.

6. A deployment and testing system for industrial applications, characterized in that, include: At least one memory and at least one processor, wherein: The at least one memory is used to store computer programs; The at least one processor is used to invoke a computer program stored in the at least one memory to execute the deployment test method for the industrial application as described in claim 1 or 2.

7. A computer-readable storage medium having a computer program stored thereon; characterized in that, The computer program can be executed by a processor to implement the deployment and testing method for the industrial application as described in claim 1 or 2.

Images