CN117407007A

CN117407007A - Application management system and method of chemical equipment controller

Info

Publication number: CN117407007A
Application number: CN202311703533.1A
Authority: CN
Inventors: 张雪静
Original assignee: Kyland Technology Co Ltd
Current assignee: Kyland Technology Co Ltd
Priority date: 2023-12-13
Filing date: 2023-12-13
Publication date: 2024-01-16

Abstract

The application management system of the chemical equipment controller comprises a model management tool running on a user terminal, a scheduler and a MOTT server running on the equipment controller, wherein the model management tool and the scheduler are configured as clients of the MOTT server; the model management tool is used for sending one or more files to the selected one or more controllers, wherein the files comprise model packages; the scheduler in the controller is used for deploying the model package in the received file into the controller and is used for acquiring the operation data of the model in the controller and issuing the operation data in a first theme; the MOTT server is used for pushing the topics published by the scheduler to a model management tool subscribed to the first topic. Corresponding management methods are also provided. The method and the device can realize unified deployment and unified management of a plurality of special applications to the controller of the equipment, and simplify the complexity of safety management.

Description

Application management system and method of chemical equipment controller

Technical Field

The present disclosure relates to the field of communication technologies, and the field of intelligent management and monitoring technologies for device security, and in particular, to an application management system and method for a chemical device controller, a computing device, and a storage medium.

Background

For some industrial devices, especially chemical devices, one of the schemes for realizing the intelligence is to make an operating system, such as a linux system, run on a controller of the industrial device, and install and deploy a plurality of industry-specific applications on the operating system. For example, a function implemented by a dedicated application may be to collect and process data, then save results and logs to a database, and upload to a designated host computer; as another example, a special application is a timed trigger device self-test; as another example, a special purpose application is monitoring equipment load, performance conditions, and the like.

These dedicated applications may be provided by different third parties, and may not be pre-integrated into the operating system run by the controller of the device, and may be deployed separately to the controller or uninstalled as desired. The special application is deployed in a mode of not being integrated in the operating system in advance, and the equipment can conveniently have new functions by adding new special application (namely under the premise of hardware support).

However, in the case of chemical equipment, especially in the case of new installation machines, in order to enable the equipment to realize a plurality of functions as required, a plurality of industry-specific applications need to be installed and deployed for the equipment, and if each of the application-specific applications is manually installed one by one, this causes a lot of trouble to the safety management work. Particularly, when a plurality of devices are installed for new installation, a plurality of special applications are manually deployed one by each device, which brings about huge and complicated workload of safety management.

On the other hand, when a plurality of special applications are deployed on the device, the special applications need to be operated sequentially (for example, log information, alarm information and the like of each special application are checked) in the security management process, and a lot of trouble is brought to the security management work.

In view of this, how to implement unified deployment and unified management of multiple dedicated applications by a controller of a chemical device, so as to avoid operating each dedicated application separately, is a technical problem to be solved.

Disclosure of Invention

In view of the above problems in the prior art, the present application provides a management system and method for applications on a chemical plant controller, a computing device, and a storage medium, which can implement unified deployment and unified management of multiple dedicated applications to a controller of the device, and simplify complexity of security management.

The first aspect of the application provides an application management system of a chemical equipment controller, which comprises a model management tool running on a user terminal, a scheduler running on the equipment controller and a MOTT server, wherein the model management tool and the scheduler are configured as clients of the MOTT server; the model management tool is used for sending one or more files to the selected one or more controllers, wherein the files comprise model packages; the scheduler in the controller is used for deploying the received model packages in the files into the controller and is used for acquiring the operation data of the models in the controller and issuing the operation data in a first theme; the MOTT server is used for pushing the topics published by the scheduler to the model management tool subscribed to the first topic.

From this, a batched deployment of model packages to controllers of one or more devices may be implemented, and one or more models may be batched deployed. In addition, the information of the model can be actively sent to the model management tool on the user terminal through the publishing-subscribing mechanism of the MOTT service, so that the user can obtain the related information in time.

As a possible implementation manner of the first aspect, the model management tool is further configured to issue management instructions as a second topic; the MOTT server is further used for pushing the second theme published by the model management tool to the dispatcher subscribed to the second theme; and the dispatcher enables the corresponding model to execute the management instruction according to the management instruction corresponding to the second theme.

By the method, batch sending of management instructions to each model subscribed to the instruction subject can be realized based on a release-subscription mechanism of MOTT service.

As a possible implementation manner of the first aspect, the file further includes a configuration file corresponding to the model package; the scheduler is configured to deploy the model package into a controller, including: the scheduler is used for deploying the model package into the controller according to the configuration file corresponding to the model package.

As a possible implementation manner of the first aspect, the first theme includes one of the following theme or a combination of any of the theme: taking the name of the model as a theme, the data under the theme comprises: new operational data generated by the model of the name; taking different time periods as topics, the data under the topics comprise: operating data generated by the corresponding time period model; taking a specific operation data type as a theme, the data under the theme comprises: operational data associated with the particular operation.

By the setting of different topics, the user can flexibly and selectively obtain the related data of the related model of the subscribed topic.

As a possible implementation manner of the first aspect, the method further includes a model repository for providing model packages; the model management tool is further configured to obtain a model package from the model repository.

Thus, the centralized acquisition and management of the model package are facilitated.

A second aspect of the present application provides a method for managing applications of a chemical plant device controller, which is implemented based on an application management system of any one of the chemical plant device controllers in the first aspect, and the method includes: selecting one or more controllers and one or more files corresponding to each controller through a model management tool, wherein the files comprise model packages; the model management tool sending the corresponding one or more files to the selected one or more controllers; the scheduler of the controller receives the corresponding file and deploys the model package in the file into the controller; the controller acquires operation data of a model in the controller and issues the operation data in a first theme; and the MOTT server pushes the topics published by the scheduler to the model management tool subscribed to the first topic.

As a possible implementation manner of the second aspect, the method further includes: the model management tool issues management instructions as a second theme; the MOTT server pushes the second topic published by the model management tool to the scheduler subscribed to the second topic; and the dispatcher enables the corresponding model to execute the management instruction according to the management instruction corresponding to the second theme.

As a possible implementation manner of the second aspect, the first theme includes one of the following theme or a combination of any of the theme: taking the name of the model as a theme, the data under the theme comprises: new operational data generated by the model of the name; taking different time periods as topics, the data under the topics comprise: operating data generated by the corresponding time period model; taking a specific operation data type as a theme, the data under the theme comprises: operational data associated with the particular operation.

A third aspect of the present application provides a computing device comprising: a processor, and a memory having stored thereon program instructions that, when executed by the processor, cause the processor to perform the method of any of the second aspects.

A fourth aspect of the present application provides a computer readable storage medium having stored thereon program instructions which when executed by a computer cause the computer to implement the method of any of the second aspects above.

Drawings

FIG. 1 is a schematic illustration of a management system for an application on a chemical plant controller provided in a first embodiment of the present application;

FIG. 2 is a flow chart of a method of managing applications on a chemical plant controller provided in a second embodiment of the present application;

fig. 3 is a schematic structural diagram of a computing device provided herein.

It should be understood that in the foregoing structural schematic diagrams, the sizes and forms of the respective block diagrams are for reference only and should not constitute an exclusive interpretation of the embodiments of the present invention. The relative positions and inclusion relationships between the blocks presented by the structural diagrams are merely illustrative of structural relationships between the blocks, and are not limiting of the physical connection of embodiments of the present invention.

Detailed Description

The technical scheme provided by the application is further described below by referring to the accompanying drawings and examples. It should be understood that the system structures and service scenarios provided in the embodiments of the present application are mainly for illustrating possible implementations of the technical solutions of the present application, and should not be construed as the only limitation of the technical solutions of the present application. As one of ordinary skill in the art can know, with the evolution of the system structure and the appearance of new service scenarios, the technical scheme provided in the application is applicable to similar technical problems.

It should be understood that the management scheme of the application on the controller provided in the embodiments of the present application includes a management system and method, a computing device and a storage medium of the application on the controller, and a device applied to the scheduling apparatus or the scheduling method. Because the principles of solving the problems in these technical solutions are the same or similar, in the following description of the specific embodiments, some repetition is not described in detail, but it should be considered that these specific embodiments have mutual references and can be combined with each other.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. If there is a discrepancy, the meaning described in the present specification or the meaning obtained from the content described in the present specification is used. In addition, the terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the present application. For the purpose of accurately describing the technical content of the present application, and for the purpose of accurately understanding the present invention, the terms used in the present specification are given the following explanation or definition before the explanation of the specific embodiments:

1) Message queue telemetry transport protocol (Message Queuing Telemetry Transport, MQTT): is a lightweight communication protocol based on a publish-subscribe mode. The MQTT has the advantages of providing real-time reliable message service for connecting remote equipment by using few codes and limited bandwidth, and can be applied to products such as the Internet of things, small-sized equipment and the like.

The framework for achieving MQTT communication comprises publishers, subscribers and servers. A publisher (publisher) describes data by defined published data types, related attributes and the like, and then publishes the data to a server; subscribers (subscribers) may specify the types of data and related attributes of interest to themselves by defining subscription rules and then subscribe to these data. When a publisher publishes new data, the server will transmit the data to subscribers.

2) Secure Shell protocol (SSH): is an encrypted network transport protocol that provides a secure transport environment for network services in an unsecure network. It enables the connection between SSH clients and servers by creating a secure tunnel in the network.

3) And (3) model: refers to executable code packaged as modules (e.g., packages) that may perform a certain function. In this example, each application is encapsulated as a model, and when the model is issued to the controller of the device, a configuration file (module. Ini) of the model is issued in cooperation with the model. The configuration file records an Identification (ID), name information, version information, format information of a start command, scheduling policy information, and the like of a specific application corresponding to the model. The configuration file may also record the location of files (e.g., file directories) released by the model in the controller, etc. The configuration files may be sent separately or packaged with the model in a file package.

The application scenario of the management scheme of the application on the controller provided by the application can be an application scenario of equipment security management. When the scheme is deployed on the user terminal side and the controller on the equipment, a plurality of special applications can be deployed to the equipment controller in a unified and batched mode, or the special applications can be managed in a unified and batched mode, and information actively uploaded by the special applications can be timely obtained. The user terminal is user side equipment, and the user terminal can be a computer, a notebook computer, a smart phone, a tablet personal computer and the like. The devices may be intelligent industrial devices, such as power generation devices, mining devices, smelting devices, water conservancy devices, and the like, or small devices, such as intelligent control devices of building air paths, and the like, and the devices are provided with controllers. The controller of the device can be realized by a control card or an industrial personal computer, and the hardware of the controller can comprise a processor chip, a memory, a storage and a communication chip. The controller can run an Intel, or Linux, UNIX or other operating system, and a plurality of special applications can be installed, deployed and run on the operating system.

The present application will be described in detail with reference to the accompanying drawings.

Fig. 1 shows a schematic structural diagram of a first embodiment of the present application, where the first embodiment is an application management system of a chemical plant controller, and the system includes a model management tool 11 running on a user terminal, including a scheduler 21 and a MOTT server 22 running on the plant controller, and may further include a model repository 30. Wherein each dedicated application is packaged into model packages, each model package can be sent to the controller in batches through the model management tool 11 at the user terminal side, and the scheduler 21 on the device controller deploys each installation package to the controller. The management system is described in detail below with reference to fig. 1:

the model management tool 11 has a man-machine interaction operation interface, so that a user can graphically operate functions provided by the model management tool 11 and display information returned by the device side controller. The following exemplifies some of the functions provided by the model management tool 11:

1) A function of downloading or uploading model packages in batches from the model repository 30 (each dedicated application is packaged as a model package), and a function of accessing a local model repository (the local model repository is located in a user terminal) or a remote model repository (the remote model repository may be located in a server provided by a third party service provider or in a server uniformly managed by an operator of the apparatus);

2) A function of importing or exporting a model package into or from the model management tool 11;

3) A function of transmitting one or more model packages or corresponding configuration files to a controller of the selected one or more devices, or a function of transmitting upgrade files;

4) A subscription/unsubscribe function, wherein a subscription operation interface can be provided to enable a user to visually select subscribed objects and subscribed contents; where the subscribed object is e.g. which device, which controller, which model (i.e. application specific). Subscribed content such as the running state of the model, logs, alarm information, fault information, general maintenance information, etc.

5) A function of displaying information sent by a model (i.e., a dedicated application) on a device side, the information being specifically related to a subscribed object or a subscribed content;

6) A function of displaying and controlling the model running state of the equipment side;

7) Common model management functions on the device side, such as start instructions, disable instructions, emulation instructions, stop emulation instructions, manual debugging, stop manual debugging, uninstall, etc.

Wherein the scheduler 21 is configured to deploy the model package sent by the model management tool 11 into the controller during a deployment phase of the model (i.e., the application specific application); and is used for after the model is deployed, obtain the management instruction that the model management tool 11 sends, send to the correspondent model in order to carry out; and for acquiring operation data (such as instruction operation results, operation states of the models, logs, alarm information, fault information, general maintenance information, etc.) of each model after the model is deployed, to feed back to the model management tool 11; and for scheduling execution of each deployed model, e.g., scheduling operation of the respective model according to a scheduling policy, timing, fixed or variable period, or based on monitored event triggers, or priorities, etc., recorded in a profile of each model.

Wherein the MOTT server 22 is used for realizing the transmission of data between the model management tool 11 and the scheduler 21. Specifically, the model management tool 11 and the scheduler 21 function as clients, respectively, and are configured as publishers and subscribers of the certain topic according to the relationship between transmission and reception of data. For example, for a management instruction to be issued by a user, such as an execution instruction, a query instruction, an update instruction, an uninstall instruction, and the like, the model management tool 11 issues the management instruction as a certain topic as a publisher, and the scheduler 21 is configured as a subscriber to the corresponding topic, so that when the model management tool 11 issues the management instruction of the topic, the MQTT server 22 pushes the topic to the scheduler 21 in time, and the scheduler may further obtain the management instruction of the topic, and based on the instruction, cause one or more models to execute the content of the corresponding instruction. For example, for the running data generated by the model, the scheduler 21 obtains the data, the data is published as a topic by the publisher of the data, and the model management tool 11 is configured as a subscriber of the topic, so that when the scheduler 21 publishes the data of the topic, the MQTT server 22 pushes the topic to the model management tool 11 in time, and the model management tool 11 obtains the data of the topic.

Based on the MOTT server 22, the model management tool 11 as a client and the scheduler 21, a subscription-publishing framework is realized, and each data can be provided for a user more flexibly, for example, the scheduler 21 can configure different topics according to the content of the data to be transmitted, so that the user can obtain the data content of different topics subscribed through the model management tool 11. Examples are as follows:

1) The names of the different models (i.e. programs) may be used as topics, the data under which include: the model of the name generates new operational data. Specifically, when the model generates new operation data, the scheduler 21 acquires and publishes the model name as a topic, so that the model management tool 11 can obtain the operation data of the subscribed topic as a subscriber. In this way, only the topic of interest (i.e., model name) can be subscribed to, so that the user can timely learn the operation data of the model of interest.

2) Different time periods may be used as a theme, the data under the theme including: operational data generated by each model corresponding to the time period. Specifically, the scheduler 21 acquires the operation data generated for each model of the corresponding time period and publishes it as the subject, so that the model management tool 11 can obtain the operation data for each model of the subscribed time period as a subscriber. By the method, the user can timely learn the operation data of each model under the concerned time period by taking the time period as a condition.

3) A specific type of operational data may be used as a theme, the data under the theme including: operational data associated with the particular operation. For example, with the fault type as a subject, when a certain model generates such a fault, the scheduler 21 issues information including the corresponding model with the fault type. In this way, when a certain device generates a certain fault, the user is enabled to timely learn the information of the device generating the fault.

The foregoing is merely illustrative, and is not limited to the above topics, and different topics may be set according to management and security management requirements, and subscribers may subscribe to all or part of the topics. In the subscription-release form, independent of the request of the active data of the user, when the scheduler 21 running on the device controller releases the corresponding topic, the active release of the data is realized, and the MQTT server 22 pushes the topic data to the model management tool 11 on the user terminal side as the subscriber in time, so that the user can learn the corresponding data in time. In addition, when there are a plurality of user terminals, the model management tool 11 on different user terminals may subscribe to different topics respectively as subscribers, so that different user terminals may only need to obtain data of corresponding topics.

The model repository 30 is used to provide each model package that can be deployed to the device controller, and may be located in the cloud, as a remote model repository, or on the user terminal, as a local model repository, and the model management tool 11 may upload and download model packages from the model repository 30.

The communication between the model management tool 11 on the user terminal and the MOTT server 22 or the scheduler 21 on the device controller, such as the transmission of the theme information, the transmission of the deployment phase model package, the transmission of the upgrade file package, and the like, may be performed based on the SSH protocol, so as to increase security.

Fig. 2 shows a flowchart of a second embodiment of the present application, where the method for managing an application on a chemical plant controller according to the second embodiment of the present application is implemented based on the application management system of the chemical plant controller, and includes the following steps:

s10: the user terminal side runs the model management tool 11, presents a user operation interface, and determines a model to be deployed (in this example, a configuration file is included) and a controller of the target device in response to the user operation.

The user operation interface may include a "select file" control, which is used to read the model package into the model management tool 11, and each time a model package is read, the name corresponding to the model package may be displayed. The user interface may also be used to select units of the model package to be deployed, where each unit corresponds to a controller of a device. Wherein different units (i.e., controllers) may deploy the same or different model packages read into the model management tool 11.

In this example, the model package and the configuration file are packaged into one file. In other embodiments, different files may be deployed in the controllers of the corresponding devices, and the principle is the same as that of the corresponding devices and will not be described again.

The principle of the embodiment is the same as that of the above and will not be repeated.

S20: in response to the user's operation, the model management tool 11 transmits the corresponding model package to the corresponding target device according to the determined model to be deployed and the controller of the corresponding target device.

The method may be that one target device has a plurality of models to be deployed, or a plurality of devices and a plurality of models to be deployed, as described above.

S30: the scheduler 21 in the controller of the target device receives the model package to be deployed and deploys into the controller.

Wherein the deployment process comprises: releasing the model package, storing the released files into corresponding folders of a file system of the controller, wherein the folders can be default folders, preferably folders specified in configuration files of the model, and starting the model by default.

Wherein different models are released to different folders, and the configuration file of each model is under the folder of each model.

A specific example is: the scheduler 21 receives the model package (which may be, for example, model20220616.Tar. Gz), the scheduler 21 releases the package, releases the model files and configuration files therein to the model1 directory (which is a default directory, or a directory specified in the configuration files), completes the installation of the program, and brings the model into a scheduling queue managed by the scheduler 21. The scheduling queue managed by the scheduler 21 includes an identifier of each model, and the scheduler 21 may implement unified scheduling of each model in the scheduling queue based on the queue, specifically may perform scheduling execution according to a scheduling policy of the model. Wherein the scheduling policy is configured in a configuration file of each model.

S40: the scheduler 21 schedules the operation of each model in a queue manner, and the scheduler 21 monitors the operation state of each model in real time and generates corresponding topics for publication.

S50: the MQTT server 22 within the controller of the apparatus pushes the subject published by the scheduler 21 to the user terminal-side model management tool 11 as a subscriber to be displayed by the model management tool 11.

The model management tool 11 also provides a management interface for subscribing the topics on the model management tool 11 to manage the topics that can be subscribed to.

The model management tool 11 also provides a management interface for managing the topic publishing and subscribing of the scheduler 21 on the device controller, so as to manage the content of the topic which can be published by the scheduler 21, and the like.

In addition, the model management tool 11 also defaults to the publisher that is the subject of the management instruction, and the scheduler 21 defaults to the subscriber that is the subject of the management instruction, so that the management instruction issued by the model management tool 11 is pushed to the scheduler 21 by the MQTT server 22, and the scheduler 21 controls the corresponding model to execute the corresponding instruction according to the instruction. The management instructions operate on the model, such as start, disable, simulate, stop simulate, manually debug, stop manually debug, unload, etc.

In addition, in some embodiments, when the model management tool 11 sends the corresponding model package to the corresponding target device in step S20, a package configuration file (package. Ini) may also be sent, and the package configuration file may be packaged with the model package into a file package. The package configuration file is used for describing package version and information and versions of a plurality of models protected in the current file package.

Fig. 3 is a schematic diagram of a computing device 400 provided by an embodiment of the present application. The computing device may be the above-described method or alternative embodiments thereof, and the computing device may be a terminal, or may be a chip or a chip system within the terminal. As shown in fig. 3, the computing device 400 includes: processor 410, memory 420, and communication interface 430.

It should be appreciated that the communication interface 430 in the computing device 400 shown in fig. 3 may be used to communicate with other devices, and may include, in particular, one or more transceiver circuits or interface circuits.

Wherein the processor 410 may be coupled to a memory 420. The memory 420 may be used to store the program codes and data. Accordingly, the memory 420 may be a storage unit internal to the processor 410, an external storage unit independent of the processor 410, or a component including a storage unit internal to the processor 410 and an external storage unit independent of the processor 410.

Optionally, computing device 400 may also include a bus. The memory 420 and the communication interface 430 may be connected to the processor 410 through buses. The bus may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, an unbiased line is shown in FIG. 3, but does not represent only one bus or one type of bus.

It should be appreciated that in embodiments of the present application, the processor 410 may employ a central processing unit (central processing unit, CPU). The processor may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. Or the processor 410 may employ one or more integrated circuits for executing associated programs to carry out the techniques provided in embodiments of the present application.

The memory 420 may include read only memory and random access memory and provides instructions and data to the processor 410. A portion of the processor 410 may also include non-volatile random access memory. For example, the processor 410 may also store information of the device type.

When the computing device 400 is running, the processor 410 executes computer-executable instructions in the memory 420 to perform any of the operational steps of the methods described above, as well as any of the alternative embodiments.

It should be understood that the computing device 400 according to the embodiments of the present application may correspond to a respective subject performing the methods according to the embodiments of the present application, and that the above and other operations and/or functions of the respective modules in the computing device 400 are respectively for implementing the respective flows of the methods of the embodiments, and are not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Embodiments of the present application also provide a computer-readable storage medium having stored thereon a computer program for performing the above-described method when executed by a processor, the method comprising at least one of the aspects described in the above-described embodiments.

Any combination of one or more computer readable media may be employed as the computer storage media of the embodiments herein. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

In addition, the terms "first, second, third, etc." or module a, module B, module C, etc. in the description and the claims are used solely for distinguishing between similar objects and not necessarily for a specific ordering of objects, it being understood that a specific order or sequence may be interchanged if allowed to enable the embodiments of the application described herein to be practiced otherwise than as specifically illustrated and described herein.

In the above description, reference numerals indicating steps such as S110, S120, … …, etc. do not necessarily indicate that the steps are performed in this order, and the order of the steps may be interchanged or performed simultaneously as the case may be.

The term "comprising" as used in the description and claims should not be interpreted as being limited to what is listed thereafter; it does not exclude other elements or steps. Thus, it should be interpreted as specifying the presence of the stated features, integers, steps or components as referred to, but does not preclude the presence or addition of one or more other features, integers, steps or components, or groups thereof. Thus, the expression "a device comprising means a and B" should not be limited to a device consisting of only components a and B.

Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments as would be apparent to one of ordinary skill in the art from this disclosure.

Note that the above is only a preferred embodiment of the present application and the technical principle applied. Those skilled in the art will appreciate that the present application is not limited to the particular embodiments described herein, but is capable of numerous obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the present application. Thus, while the present application has been described in terms of the foregoing embodiments, the present application is not limited to the foregoing embodiments, but may include many other equivalent embodiments without departing from the spirit of the present application, all of which fall within the scope of the present application.

Claims

1. An application management system of a chemical plant controller, comprising a model management tool running on a user terminal, a scheduler running on the plant controller and a MOTT server, wherein the model management tool and the scheduler are configured as clients of the MOTT server;

the model management tool is used for sending one or more files to the selected one or more controllers, wherein the files comprise model packages, and each model package corresponds to an application;

the scheduler in the controller is used for deploying the received model packages in the files into the controller and is used for acquiring the operation data of the models in the controller and issuing the operation data in a first theme;

the MOTT server is used for pushing the first theme published by the scheduler to the model management tool subscribed to the first theme.

2. The system of claim 1, wherein the model management tool is further configured to issue management instructions as a second topic;

the MOTT server is further used for pushing the second theme published by the model management tool to the dispatcher subscribed to the second theme;

and the dispatcher enables the corresponding model to execute the management instruction according to the management instruction corresponding to the second theme.

3. The system of claim 2, wherein the file further comprises a configuration file corresponding to the model package;

the scheduler is configured to deploy the model package into a controller, including: the scheduler is used for deploying the model package into the controller according to the configuration file corresponding to the model package.

4. The system of claim 3, wherein the first theme comprises one of the following or a combination of any of the following:

taking the name of the model as a theme, the data under the theme comprises: new operational data generated by the model of the name;

taking different time periods as topics, the data under the topics comprise: operating data generated by the corresponding time period model;

taking a specific operation data type as a theme, the data under the theme comprises: operational data associated with the particular operation.

5. The system of claim 1, further comprising a model repository for providing model packages;

the model management tool is further configured to obtain a model package from the model repository.

6. A method for managing applications of a chemical plant controller, wherein the method is implemented based on the application management system of the chemical plant controller according to any one of claims 1 to 5, and comprises:

selecting one or more controllers and one or more files corresponding to each controller through a model management tool, wherein the files comprise model packages;

the model management tool sending the corresponding one or more files to the selected one or more controllers;

the scheduler of the controller receives the corresponding file and deploys the model package in the file into the controller;

the controller acquires operation data of a model in the controller and issues the operation data in a first theme;

the MOTT server pushes the first topic published by the scheduler to the model management tool subscribed to the first topic.

7. The method as recited in claim 6, further comprising:

the model management tool issues management instructions as a second theme;

the MOTT server pushes the second topic published by the model management tool to the scheduler subscribed to the second topic;

8. The method of claim 7, wherein the first theme comprises one or a combination of any of the following themes:

9. A computing device, comprising:

processor and method for controlling the same

A memory having stored thereon program instructions that when executed by the processor cause the processor to perform the method of managing the application of the chemical plant controller of any one of claims 6 to 8.

10. A computer readable storage medium having stored thereon program instructions which, when executed by a processor, cause the processor to perform a method of managing the application of a chemical plant controller according to any one of claims 6 to 8.