Deployment method and related device

Abstract

The embodiment of the invention provides a deployment method, which comprises the following steps of: in a server, firstly responding to an uploading operation of target software, generating a target installation package based on the target software, and adding backups of project files respectively corresponding to the target software into compressed files corresponding to devices by taking the devices as units, and storing the backups. On one hand, the target installation package can be simplified, and on the other hand, convenient switching of different projects can be supported based on compressed files corresponding to different devices. When a client side logs in a server, the server can provide downloading service of a target installation package for the client side so that the client side can automatically install target software based on the target installation package, and when the server receives a downloading request for a first target project sent by the client side, the client side can automatically install the target software based on the target installation package. According to the embodiment of the invention, the compressed file corresponding to the first target project can be issued to the client to load the first target project, and a user of the client does not need to implement excessive operations in the whole deployment process, so that the deployment process is simplified.

Description

Technical Field

[0001] The present specification relates to the field of simulation technology, specifically, to the simulation technology of distributed control systems, and more specifically, to a deployment method and related devices. Background Art

[0002] Distributed Control System (DCS) is a software platform used to realize centralized control and management of decentralized equipment and systems in industrial production processes. Simulation software is a tool for dynamic modeling and simulation of physical systems or processes, and it focuses on simulating and analyzing the behavior and performance of the system. Simulation software can simulate the dynamic response of the system under different working conditions and different input conditions, including the performance of the system in terms of stability, response speed, accuracy, etc. Process model software is a tool used to build and simulate process models of various industrial production processes. Based on mathematical models and physical principles, it converts the actual process flow into a virtual model that can be recognized and processed by computers.

[0003] The use of distributed control systems, simulation software and process model software can achieve simulation of process flow and system design, provide a safe training environment and improve the training effect of personnel. The current deployment method of the simulation environment is relatively complex. Summary of the invention

[0004] The embodiments of this specification provide a deployment method and related devices to achieve the purpose of simplifying the simulation environment deployment process.

[0005] To achieve the above technical objectives, the embodiments of this specification provide the following technical solutions:

[0006] In a first aspect, an implementation of this specification provides a deployment method, which is applied to a server in a target system, wherein the target system also includes a client, and the deployment method includes:

[0007] In response to an upload operation for target software, a target installation package is generated based on the target software, wherein the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function;

[0008] Taking devices as units, adding backups of the engineering files corresponding to the target software to the compressed files corresponding to the devices and storing them;

[0009] In response to the client logging into the server, providing the client with a download service of a target installation package, wherein the target installation package is used to instruct the client to install the target software;

[0010] In response to a download request for a first target project sent by the client, a compressed file corresponding to the first target project is sent to the client, and the compressed file is used to instruct the client to decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project.

[0011] In a second aspect, an implementation of this specification provides a deployment method, which is applied to a client in a target system, wherein the target system also includes a server; the deployment method includes:

[0012] In response to the login operation, the server is logged in, a target installation package sent by the server is received, and the target software is installed based on the target installation package; the target installation package includes the target software; the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function; the target software is pre-stored in the server;

[0013] Send a download request for the first target project to the server, receive the compressed file sent by the server, and decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project; the server pre-stores a compressed file, and the compressed file is obtained by the server on a device basis, by adding the backup of the project files corresponding to each of the target software to the compressed file corresponding to the device.

[0014] In a third aspect, an implementation of this specification further provides a deployment system, including: a server and a client; wherein:

[0015] The client is configured to: log in to the server in response to a login operation; send a download request for a first target project to the server, receive a compressed file sent by the server, and decompress a backup of the project file in the compressed file to a project directory corresponding to each of the target software to load the first target project;

[0016] The server is configured to: in response to an upload operation for target software, generate a target installation package based on the target software, the target software including process model software, simulation software and distributed control system software; the distributed control system software is trimmed to remove the engineering configuration function; the simulation software is trimmed to remove the engineering management function; on a device basis, add and store the backup of the engineering files corresponding to each of the target software into a compressed file corresponding to the device; in response to the client logging into the server, provide the client with a download service for the target installation package, and in response to a download request for a first target project sent by the client, send the compressed file corresponding to the first target project to the client.

[0017] In a fourth aspect, an embodiment of the present specification further provides a computing device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the deployment method as described above when executing the computer program.

[0018] In a fifth aspect, an embodiment of the present specification further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the deployment method as described above is implemented.

[0019] In a sixth aspect, the embodiments of this specification provide a computer program product or a computer program, wherein the computer program product includes a computer program, wherein the computer program is stored in a computer-readable storage medium; the processor of the computer device reads the computer program from the computer-readable storage medium, and the processor implements the steps of the above-mentioned deployment method when executing the computer program. Optionally, the computer program may be stored in a computer-readable storage medium or in the cloud; the processor of the computer device reads the computer program from the computer-readable storage medium or in the cloud.

[0020] It can be seen from the above technical scheme that the deployment method provided in the embodiment of this specification first responds to the upload operation of the target software in the server, generates a target installation package based on the target software, and at the same time, adds the backup of the project files corresponding to each target software to the compressed file corresponding to the device and stores it in units of devices. In this way, the target installation package and the compressed file are stored separately, which can simplify the target installation package on the one hand, and support convenient switching of different projects based on the compressed files corresponding to different devices on the other hand. When the client logs in to the server, the server can provide the client with a download service of the target installation package so that the client can automatically install the target software based on the target installation package. When the server receives a download request for the first target project sent by the client, the compressed file corresponding to the first target project can be sent to the client, so that the client can decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project, thereby completing the deployment of the simulation environment and the loading of the project. During the entire deployment process, the user of the client does not need to perform too many operations, which is conducive to simplifying the deployment process. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0022] Figure 1 A schematic diagram of a communication relationship between target software provided for one implementation of this specification;

[0023] Figure 2 A flowchart of a deployment method provided for one embodiment of this specification;

[0024] Figure 3 A schematic diagram of an engineering switching process provided for one embodiment of this specification;

[0025] Figure 4 A flowchart of another deployment method provided for one embodiment of this specification;

[0026] Figure 5 A schematic diagram of a deployment system provided for one embodiment of this specification;

[0027] Figure 6 A schematic diagram of the structure of a computing device provided for one embodiment of the present specification. DETAILED DESCRIPTION

[0028] Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this specification shall have the common meanings understood by persons with ordinary skills in the field to which this specification belongs. The words "first", "second" and similar words used in the embodiments of this specification do not indicate any order, quantity or importance, but are only used to avoid confusion of constituent elements.

[0029] Unless the context requires otherwise, throughout the specification, "plurality" means "at least two", and "including" is interpreted as an open, inclusive meaning, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "examples", "specific examples" or "some examples" are intended to indicate that a particular feature, structure, material or characteristic associated with the embodiment or example is included in at least one embodiment or example of the specification. The schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0030] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0031] Overview

[0032] As described in the background technology, the simulation of process flow and system design can be realized by using distributed control systems, simulation software and process model software. This simulation environment can be applied to various scenarios such as personnel training scenarios and system optimization scenarios. Taking the personnel training scenario as an example, in some industries with high risk factors, such as chemical industry and electricity, there may be safety risks in allowing trainees to be trained directly on actual production equipment. Through the virtual production scenario provided by the simulation environment, trainees can conduct operation training in a safe environment, familiarize themselves with production processes, equipment operations and emergency handling processes, etc., which is conducive to improving trainees' operating skills and ability to deal with emergencies, and reducing the occurrence of accidents that may be caused by human operational errors.

[0033] In a simulation environment, the distributed control system software can monitor and control various physical quantities (such as temperature, pressure, flow, liquid level, etc.) in the production process. Process model software can be used for modeling and simulation of process. Simulation software can be used to simulate industrial control systems in real time, providing a virtual environment for the development, testing and training of control systems. Optionally, the distributed control system software may include HOLLiAS MACs software, the simulation software may include HiaSimuRTS, and the process model software may include GPress software. The distributed control system software, simulation software and process model software work together to provide a simulation environment that simulates a real distributed control system site. The interactive relationship between the three can be referred to. Figure 1 , users can conduct operation learning and training based on the simulation environment. In the existing simulation environment deployment process, engineers need to deploy the simulation environment on a specific terminal in the training room, and trainees need to use the terminal with the simulation environment deployed in the training room to learn the process and practice exercises at regular intervals. This method is limited by the training room environment, the scale of terminals with the simulation environment deployed, and the working hours of trainees, which affects the training time and cannot give full play to the learning potential and subjective initiative of trainees. At present, the deployment of the simulation environment is relatively complex, and it is difficult for trainees to easily deploy it on their own personal computers.

[0034] In order to solve this problem and simplify the deployment difficulty of the simulation environment, the inventor provides a deployment method, in which the server first responds to the upload operation of the target software, generates a target installation package based on the target software, and at the same time, adds the backup of the project files corresponding to each target software to the compressed file corresponding to the device and stores it in units of devices. In this way, the target installation package and the compressed file are stored separately, which can simplify the target installation package on the one hand, and support convenient switching of different projects based on the compressed files corresponding to different devices on the other hand. When the client logs in to the server, the server can provide the client with a download service of the target installation package, so that the client can automatically install the target software based on the target installation package. When the server receives a download request for a first target project sent by the client, the compressed file corresponding to the first target project can be sent to the client, so that the client can decompress the backup of the project files in the compressed file to the project directory corresponding to each target software to load the first target project, thereby completing the deployment of the simulation environment and the loading of the project. During the entire deployment process, the user of the client does not need to perform too many operations, which is conducive to simplifying the deployment process.

[0035] Based on the above concept, an implementation method of this specification is provided. The deployment method provided in the implementation method of this specification is exemplarily described below with reference to the accompanying drawings.

[0036] Exemplary Methods

[0037] To be applied to Figure 2 Taking the server 10 in the target system as an example, some implementations of this specification exemplify the deployment method, such as Figure 2 As shown, the target system also includes a client 20, and the deployment method includes:

[0038] S201: In response to an upload operation for target software, a target installation package is generated based on the target software, wherein the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function;

[0039] S202: adding the backup of the engineering files corresponding to the target software to the compressed file corresponding to the device and storing the backup in units of devices;

[0040] S203: In response to the client logging into the server, providing the client with a download service of a target installation package, where the target installation package is used to instruct the client to install the target software;

[0041] S204: In response to a download request for the first target project sent by the client, a compressed file corresponding to the first target project is sent to the client, wherein the compressed file is used to instruct the client to decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project.

[0042] Figure 2 The target system shown in can also be called a deployment system, in which the number of clients can be one or more, the client can be a user's personal computer, and the server can provide each client with the target software installation service and the project file download service. After the client installs the target software and loads the project, it can provide the user with a corresponding simulation environment for the user to learn the process and practice exercises. After the user deploys the simulation environment in the client, he can run the target software through the intranet (or system network) to learn the process and practice exercises in the simulation environment. The client and the server can be connected through a local area network (such as a factory area network, i.e., a factory local area network) or a wide area network (WAN).

[0043] In the simulation environment, a device is a concept defined from a process perspective. There can be multiple devices in the client, and users can learn and practice different process projects by switching devices. A device can correspond to a process model project, a distributed control system project, and a simulation software project. Among them, the process model project is a simulated process model, which can be a simulation of hardware equipment, instruments, etc. at the distributed control system site. The distributed control system project can be a control project from the distributed control system site. The simulation software project can be the control logic of the control station running at the distributed control system site. Its operating environment is on the computer, and the field environment runs in the controller.

[0044] In the target software, the distributed control system software can be trimmed to remove the engineering configuration function before uploading to the server, and the simulation software can be trimmed to remove the engineering management function. This is because in the student learning scenario, after the deployment is completed, the running project is already a verified project, and the engineering configuration and engineering management functions are no longer needed. This is conducive to simplifying the target installation package and reducing the amount of data required to be transmitted between the server and the client during the deployment process. The process model software is already the smallest operating environment, so there is no need to trim the process model software.

[0045] In this embodiment, the target software itself is integrated into the target installation package, and the backup of the project files corresponding to each target software is added to the compressed files corresponding to each device. In this way, on the one hand, the installation of the target software is distinguished from the switching / loading of the device. When installing the target software, the compressed file can be downloaded first, which is conducive to reducing the amount of data required to be transmitted at one time; on the other hand, the compressed files corresponding to each device are stored separately, which is conducive to increasing the convenience of the device loading and switching process, and facilitating the switching and recovery of each device. This is because the original project file must include multiple directories and multiple files. If the meta-project file is not compressed and directly transmitted, on the one hand, the amount of data required to be transmitted is large, and on the other hand, it is not easy to recover. By adding the backup of the project files corresponding to each target software to the compressed file in units of devices, the amount of data required to be transmitted can be greatly reduced, and when restoring the project, the compressed file can be directly decompressed to the project directory corresponding to each target software.

[0046] In one embodiment, the backup of the project files can be uploaded to the specified path of the server according to the device. The backup of the project files can be compressed and the folders and files dependent on the project can be compressed into a compressed file with a timestamp format, which can be used as identification information of the compressed file.

[0047] In this embodiment, after the client accesses the network where the server is located through VPN (Virtual Private Network), it accesses and logs in to the server through the Web. The server responds to the client's login and sends the target installation package to the client. After receiving the target installation package, the client can automatically install the target software. The automatic installation service can be provided by the Web.

[0048] After the target software is installed, if there is no project to load locally on the client, a download request for the first target project can be sent to the server. The first target project can be one or more projects selected by the user to be downloaded. After receiving the download request, the server sends the compressed file corresponding to the first target project to the client. After receiving the compressed file, the client decompresses it into the project directory corresponding to each target software to load the first target project.

[0049] In general, the deployment method provided in the implementation mode of this specification first responds to the upload operation of the target software in the server, generates a target installation package based on the target software, and at the same time, adds the backup of the project files corresponding to each target software to the compressed file corresponding to the device and stores it in units of devices. In this way, the target installation package and the compressed file are stored separately, which can simplify the target installation package on the one hand, and support convenient switching of different projects based on the compressed files corresponding to different devices on the other hand. When the client logs in to the server, the server can provide the client with a download service of the target installation package so that the client can automatically install the target software based on the target installation package. When the server receives a download request for the first target project sent by the client, the compressed file corresponding to the first target project can be sent to the client, so that the client can decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project, thereby completing the deployment of the simulation environment and the loading of the project. During the entire deployment process, the user of the client does not need to perform too many operations, which is conducive to simplifying the deployment process.

[0050] In an optional implementation, the deployment method further includes:

[0051] In response to the query request sent by the client, comparing whether the versions of the target software in the target installation package are the same as the versions of the target software in the client, and if they are different, updating the target software in the client;

[0052] The query request is triggered when the client runs the process model software.

[0053] In this embodiment, a method for updating the version of a target software is provided. Each time the client runs the process model software, a query request can be triggered. The query request can carry the version information of each target software in the client. When the version of each target software in the target installation package stored in the server is different from the version of each target software in the client, the target installation package can be sent to the client, and the client updates the local target software.

[0054] In addition, in order to simplify the operation of the trainees, in this embodiment, the query request is triggered when the process model software is running. This is because from the deployment of the entire simulation environment, the process model software is generally operated by the trainees, while the simulation software generally does not require the trainees to operate. In the distributed control system software, the trainees operate the operator online software, which is only the interactive part of the distributed control system software and does not have the concept of engineering. Therefore, considering comprehensively, the query request initiated by the process model software is in line with the trainees' operating habits on the one hand, and on the other hand, the trainees do not need to repeatedly initiate queries / updates for the three software, which is conducive to simplifying the operation.

[0055] In one embodiment, in response to the upload operation for the target software, generating a target installation package based on the target software includes:

[0056] In response to an upload operation for the target software, storing the target software in a first target path, and generating the target installation package based on the target software;

[0057] The step of adding the backup of the engineering files corresponding to the target software to the compressed file corresponding to the device and storing the backup of the engineering files corresponding to the target software includes:

[0058] Taking the device as a unit, adding the backup of the engineering files corresponding to each of the target software into the compressed file corresponding to the device, and storing the compressed file in the second target path;

[0059] In response to the download request for the first target project sent by the client, sending the compressed file corresponding to the first target project to the client includes:

[0060] In response to a download request for a first target project sent by the client, a compressed file corresponding to the first target project is determined in the second target path, and the compressed file is sent to the client.

[0061] In this embodiment, a feasible storage and distribution method for the target installation package and the compressed file is provided. In an optional embodiment, the first target path and the second target path may be different, which is helpful to distinguish the target installation package from the compressed file.

[0062] In one embodiment, the deployment method further includes:

[0063] In response to an update request for a second target project sent by the client, when no historical compressed file exists in the client, a current compressed file is sent to the client; the current compressed file is used to instruct the client to switch to the second target project based on the current compressed file;

[0064] The historical compressed file includes the compressed file corresponding to the second target project that has been stored by the client before sending the update request, and the current compressed file includes the compressed file corresponding to the second target project that is currently stored in the server;

[0065] When the client already has a historical compressed file, it is determined whether the historical compressed file is the same as the current compressed file. If they are different, the current compressed file is sent to the client.

[0066] In this embodiment, a feasible update method for a project is provided. When the client needs to update the second target project, an update request for the second target project can be sent to the server. The update request can carry the storage status of the second target project locally on the client (whether a compressed file corresponding to the second target project is stored locally, and identification information of the compressed file corresponding to the second target project stored locally). After receiving the update request, if there is no historical compressed file in the client, the server sends the current compressed file to the client. If there is a historical compressed file in the client, it determines whether the historical compressed file is the same as the current compressed file. If they are different, the current compressed file is sent to the client. If they are the same, a corresponding notification message can be returned to the client.

[0067] refer to Figure 3 , Figure 3 The following is a feasible process for a client to switch an engineering project, which may include:

[0068] The user selects to switch the project (e.g., switch to the second target project) in the process model software, and the process model software sends the device corresponding to the second target project to the distributed control system software to instruct the distributed control system software to unload the loaded project and close the simulation software and services;

[0069] The distributed control system software searches for a locally stored compressed file according to the received second target project, and if the historical compressed file exists and the current compressed file sent by the server is not received, loads the historical compressed file, starts the simulation software and service, and loads the simulation function;

[0070] If the current compressed file sent by the server is received, the current compressed file is loaded and the simulation software and service are started. During the loading process, the loading project of the process model software may refer to some data stored in the model (such as process data), while the loading project of the simulation software refers to loading the data of the control system.

[0071] The following will take the client applied in the target system as an example to exemplarily describe the deployment method provided in the implementation mode of this specification. Figure 4 As shown, the deployment method includes:

[0072] S401: In response to a login operation, log in to the server, receive a target installation package sent by the server, and install the target software based on the target installation package; the target installation package includes the target software; the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function; the target software is pre-stored in the server;

[0073] S402: Send a download request for the first target project to the server, receive a compressed file sent by the server, and decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project; the server pre-stores a compressed file, and the compressed file is obtained by the server by adding the backup of the project files corresponding to each of the target software to the compressed file corresponding to the device in units of devices.

[0074] For the relevant limitations of steps S401 and S402, please refer to the relevant description above, and this specification will not elaborate on them here.

[0075] Optionally, in one embodiment, the deployment method further includes:

[0076] In response to the running operation of the process model software, a query request is sent to the server, and the query request is used to instruct the server to compare whether the version of each target software in the target installation package is the same as the version of each target software in the client. If different, the target software in the client is updated.

[0077] For the relevant limitations on the update process of the target software, please refer to the relevant description above.

[0078] Optionally, in one embodiment, the deployment method further includes:

[0079] In response to a switching operation of the current project to the second target project, an update request for the second target project is sent to the server, wherein the update request is used to instruct the server to send the current compressed file to the client when there is no historical compressed file in the client; and to determine whether the historical compressed file is the same as the current compressed file when there is a historical compressed file in the client, and if they are different, send the current compressed file to the client;

[0080] The historical compressed file includes the compressed file corresponding to the second target project that has been stored by the client before sending the update request, and the current compressed file includes the compressed file corresponding to the second target project that is currently stored in the server;

[0081] When receiving the current compressed file sent by the server, switching to the second target project based on the current compressed file;

[0082] When the current compressed file sent by the server is not received, switching to the second target project based on the historical compressed file.

[0083] Optionally, the switching to the second target project includes:

[0084] Sending the device corresponding to the second target project to the distributed control system software to instruct the distributed control system software to unload the loaded project and close the simulation software and services;

[0085] The distributed control system software searches for the locally stored compressed file based on the received second target project. If the historical compressed file exists and the current compressed file sent by the server is not received, the historical compressed file is loaded, the simulation software and services are started, and the simulation function is loaded; if the current compressed file sent by the server is received, the current compressed file is loaded and the simulation software and services are started.

[0086] For the process of switching projects, please refer to the relevant description above, and this manual will not go into details here.

[0087] Exemplary Devices

[0088] In an exemplary embodiment of the present specification, a deployment device is further provided, which is applied to a server in a target system, wherein the target system also includes a client, and the deployment device includes:

[0089] A software upload module, for generating a target installation package based on the target software in response to an upload operation for the target software, wherein the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function;

[0090] A file compression module, for adding and storing the backup of the engineering files corresponding to the target software respectively in units of devices into the compressed file corresponding to the device;

[0091] A software delivery module, configured to provide a download service of a target installation package to the client in response to the client logging into the server, wherein the target installation package is used to instruct the client to install the target software;

[0092] The device sending module is used to respond to the download request for the first target project sent by the client, and send the compressed file corresponding to the first target project to the client, and the compressed file is used to instruct the client to decompress the backup of the project file in the compressed file to the project directory corresponding to each of the target software to load the first target project.

[0093] In an exemplary embodiment of the present specification, a deployment device is further provided, which is applied to a client in a target system, wherein the target system also includes a server; the deployment device includes:

[0094] A first download module is used to log in to the server in response to a login operation, receive a target installation package sent by the server, and install the target software based on the target installation package; the target installation package includes the target software; the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function; the target software is pre-stored in the server;

[0095] The second download module is used to send a download request for the first target project to the server, receive the compressed file sent by the server, and decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project; the server pre-stores a compressed file, and the compressed file is obtained by the server on a device basis by adding the backup of the project files corresponding to each of the target software to the compressed file corresponding to the device.

[0096] For the specific definition of the deployment device, please refer to the definition of the deployment method above, which will not be repeated here. Each module in the above deployment device can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0097] Exemplary Devices

[0098] An embodiment of the present specification also provides a deployment system, such as Figure 5 As shown, it includes: a server and a client; wherein,

[0099] The client is configured to: log in to the server in response to a login operation; send a download request for a first target project to the server, receive a compressed file sent by the server, and decompress a backup of the project file in the compressed file to a project directory corresponding to each of the target software to load the first target project;

[0100] The server is configured to: in response to an upload operation for target software, generate a target installation package based on the target software, the target software including process model software, simulation software and distributed control system software; the distributed control system software is trimmed to remove the engineering configuration function; the simulation software is trimmed to remove the engineering management function; on a device basis, add and store the backup of the engineering files corresponding to each of the target software into a compressed file corresponding to the device; in response to the client logging into the server, provide the client with a download service for the target installation package, and in response to a download request for a first target project sent by the client, send the compressed file corresponding to the first target project to the client.

[0101] For the relevant limitations on the client and server, please refer to the relevant limitations on the deployment method above, and this manual will not go into details here.

[0102] Optionally, in one embodiment, the client is further used for:

[0103] Create a virtual network card and implement internal system network networking based on the virtual network card.

[0104] In some embodiments, the distributed control system may need to run in an independent 128 / 129 network, which is a relatively closed network environment, generally not open to the outside world, and the 128 / 129 networks are redundant with each other. The internal system network may refer to the system network (e.g., 128 / 129 network) in which the simulated distributed control system runs. By simulating the internal system network, the simulation requirements of a certain device in the field environment of the distributed control system can be met, and the simulation environment can be guaranteed to be consistent with the real field environment. And since the client usually does not have multiple network cards, by adding a virtual network card, it is also convenient to manage and configure the IP address required by the simulation system. When the client switches to install the box, the IP of the operating environment can be added based on the virtual network card. Therefore, in this embodiment, the internal system network networking is realized through the virtual network card, which can meet the simulation requirements of the simulation environment. In general, in this embodiment, the virtual network card can not only meet the internal networking requirements of the client, but also do not interfere with other computers.

[0105] Another embodiment of the present application further provides a computing device, see Figure 6 As shown, an exemplary embodiment of the present specification also provides a computing device, including: a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it executes the steps of the deployment method according to various embodiments of the present specification described in the above embodiments of the present specification.

[0106] The internal structure of the computing device can be as follows Figure 6 As shown, the computing device includes a processor, a memory, a network interface and an input device connected through a system bus. Among them, the processor of the computing device is used to provide computing and control capabilities. The memory of the computing device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computing device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the steps in the deployment method according to various embodiments of the present specification described in the above embodiments of the present specification are performed.

[0107] The processor may include a main processor and may also include a baseband chip, a modem, etc.

[0108] It can be understood that the processor of the embodiment of this specification can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method implementation can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiment of this specification can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of this specification can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0109] It is understood that the memory in the embodiments of this specification may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (ErasablePROM, EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0110] The input device may include a device for receiving data and information input by a user, such as a keyboard, a mouse, a camera, a scanner, a light pen, a voice input device, a touch screen, a pedometer, or a gravity sensor.

[0111] Output devices may include means that allow information to be output to a user, such as display screens, printers, speakers, etc.

[0112] The communication interface may include using any transceiver or the like to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0113] The computing device may also include a display component and a voice component. The display component may be a liquid crystal display or an electronic ink display. The input device of the computing device may be a touch layer covered on the display component, or a button, trackball or touchpad provided on the housing of the computing device, or an external keyboard, touchpad or mouse.

[0114] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of this specification, and does not constitute a limitation on the computing device to which the scheme of this specification is applied. The specific computing device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0115] Exemplary computer program products and storage media

[0116] In addition to the above-mentioned methods and devices, the deployment method provided in the embodiments of this specification may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the deployment method according to various embodiments of this specification described in the above "Exemplary Method" section of this specification.

[0117] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK).

[0118] The computer program product may be written in any combination of one or more programming languages ​​to write program code for performing the operations of the embodiments of the present specification, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0119] In addition, an embodiment of the present specification also provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor to execute the steps of the deployment method according to various embodiments of the present specification described in the above "Exemplary Method" section of the present specification.

[0120] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this specification can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0121] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0122] The above-mentioned embodiments only express several implementation methods of this specification, and the descriptions are relatively specific and detailed, but they cannot be understood as limiting the scope of the solutions provided by the embodiments of this specification. It should be pointed out that for ordinary technicians in this field, several modifications and improvements can be made without departing from the concept of this specification, which all belong to the protection scope of this specification. Therefore, the protection scope of the patent of this specification shall be based on the attached claims.

Claims

1. A deployment method, characterized in that: The server is applied to a target system, wherein the target system also includes a client, and the deployment method includes: In response to an upload operation for target software, a target installation package is generated based on the target software, wherein the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function; Taking devices as units, adding backups of the engineering files corresponding to the target software to the compressed files corresponding to the devices and storing them; In response to the client logging into the server, providing the client with a download service of a target installation package, wherein the target installation package is used to instruct the client to install the target software; In response to a download request for a first target project sent by the client, a compressed file corresponding to the first target project is sent to the client, and the compressed file is used to instruct the client to decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project.

2. The method according to claim 1, characterized in that Also includes: In response to the query request sent by the client, comparing whether the versions of the target software in the target installation package are the same as the versions of the target software in the client, and if they are different, updating the target software in the client; The query request is triggered when the client runs the process model software.

3. The method according to claim 1, characterized in that In response to the upload operation for the target software, generating a target installation package based on the target software includes: In response to an upload operation for the target software, storing the target software in a first target path, and generating the target installation package based on the target software; The step of adding the backup of the engineering files corresponding to the target software to the compressed file corresponding to the device and storing the backup of the engineering files corresponding to the target software includes: Taking the device as a unit, adding the backup of the engineering files corresponding to each of the target software into the compressed file corresponding to the device, and storing the compressed file in the second target path; In response to the download request for the first target project sent by the client, sending the compressed file corresponding to the first target project to the client includes: In response to a download request for a first target project sent by the client, a compressed file corresponding to the first target project is determined in the second target path, and the compressed file is sent to the client.

4. The method according to any one of claims 1 to 3, characterized in that: Also includes: In response to an update request for a second target project sent by the client, when no historical compressed file exists in the client, a current compressed file is sent to the client; the current compressed file is used to instruct the client to switch to the second target project based on the current compressed file; The historical compressed file includes the compressed file corresponding to the second target project that has been stored by the client before sending the update request, and the current compressed file includes the compressed file corresponding to the second target project that is currently stored in the server; When the client already has a historical compressed file, it is determined whether the historical compressed file is the same as the current compressed file. If they are different, the current compressed file is sent to the client.

5. A deployment method, characterized in that: The client is applied to a target system, wherein the target system also includes a server; the deployment method includes: In response to the login operation, the server is logged in, a target installation package sent by the server is received, and the target software is installed based on the target installation package; the target installation package includes the target software; the target software includes process model software, simulation software and distributed control system software; the distributed control system software is cut to remove the engineering configuration function; the simulation software is cut to remove the engineering management function; the target software is pre-stored in the server; Send a download request for the first target project to the server, receive the compressed file sent by the server, and decompress the backup of the project files in the compressed file to the project directory corresponding to each of the target software to load the first target project; the server pre-stores a compressed file, and the compressed file is obtained by the server on a device basis, by adding the backup of the project files corresponding to each of the target software to the compressed file corresponding to the device.

6. The method according to claim 5, characterized in that Also includes: In response to the running operation of the process model software, a query request is sent to the server, and the query request is used to instruct the server to compare whether the version of each target software in the target installation package is the same as the version of each target software in the client. If different, the target software in the client is updated.

7. The method according to claim 5, characterized in that Also includes: In response to a switching operation of the current project to the second target project, an update request for the second target project is sent to the server, wherein the update request is used to instruct the server to send the current compressed file to the client when there is no historical compressed file in the client; and to determine whether the historical compressed file is the same as the current compressed file when there is a historical compressed file in the client, and if they are different, send the current compressed file to the client; The historical compressed file includes the compressed file corresponding to the second target project that has been stored by the client before sending the update request, and the current compressed file includes the compressed file corresponding to the second target project that is currently stored in the server; When receiving the current compressed file sent by the server, switching to the second target project based on the current compressed file; When the current compressed file sent by the server is not received, switching to the second target project based on the historical compressed file.

8. The method according to claim 7, characterized in that The switching to the second target project includes: Sending the device corresponding to the second target project to the distributed control system software to instruct the distributed control system software to unload the loaded project and close the simulation software and services; The distributed control system software searches for the locally stored compressed file based on the received second target project. If the historical compressed file exists and the current compressed file sent by the server is not received, the historical compressed file is loaded, the simulation software and services are started, and the simulation function is loaded; if the current compressed file sent by the server is received, the current compressed file is loaded and the simulation software and services are started.

9. A deployment system, characterized in that: include: Server and Client; where The client is configured to: log in to the server in response to a login operation; send a download request for a first target project to the server, receive a compressed file sent by the server, and decompress a backup of the project file in the compressed file to a project directory corresponding to each target software to load the first target project; The server is configured to: in response to an upload operation for target software, generate a target installation package based on the target software, the target software including process model software, simulation software and distributed control system software; the distributed control system software is trimmed to remove the engineering configuration function; the simulation software is trimmed to remove the engineering management function; on a device basis, add and store the backup of the engineering files corresponding to each of the target software into a compressed file corresponding to the device; in response to the client logging into the server, provide the client with a download service for the target installation package, and in response to a download request for a first target project sent by the client, send the compressed file corresponding to the first target project to the client.

10. The system according to claim 9, characterized in that The client is also used to: Create a virtual network card and implement internal system network networking based on the virtual network card.

Images