CN117407007A - Application management system and method of chemical equipment controller - Google Patents

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 for chemical equipment controller

Technical field

This application relates to the field of communication technology and the field of intelligent management and monitoring technology of equipment security, and in particular to an application management system and method for a chemical equipment controller, a computing device and a storage medium.

Background technique

For some industrial equipment, especially chemical equipment, one of the solutions to achieve intelligence is to enable the controller of the industrial equipment to run an operating system, such as a Linux system, etc., and to install and deploy multiple industry-specific applications on the operating system. accomplish. For example, the function implemented by a dedicated application can be to collect and process data, then save the results and logs to the database, and upload them to the designated host computer; another example is a dedicated application that triggers equipment self-test at regular intervals; another example is a dedicated application that monitors Equipment load, performance, etc.

Among them, these special applications can be provided by different third parties and are not pre-integrated into the operating system running by the controller of the device. They can be separately deployed and installed on the controller or uninstalled as needed. This method of deploying special applications that is not pre-integrated into the operating system can easily add new special applications to enable the device to have new functions (under the premise of hardware support).

However, for chemical equipment, especially when it is newly installed, in order to enable it to achieve multiple required functions, it is necessary to install and deploy multiple industry-specific applications. If each dedicated application is installed manually one by one, this will It will bring a lot of trouble to safety management work. Especially when targeting multiple newly installed devices, manually deploying multiple dedicated applications one by one for each device will bring a huge and tedious security management workload.

On the other hand, when multiple dedicated applications are deployed on the device, during the security management process, these dedicated applications need to be operated in sequence (such as viewing the log information and alarm information of each dedicated application), which also brings challenges to the security management work. A lot of trouble.

In view of this, how to realize the unified deployment and unified management of multiple special applications by the controller of chemical equipment to avoid operating each special application separately is a technical problem that needs to be solved.

Contents of the invention

In view of the above problems of the prior art, this application provides a management system and method for applications on a chemical equipment controller, a computing device and a storage medium, which can realize the unified deployment and unification of multiple dedicated applications to the controller of the equipment. management, simplifying the complexity of security management.

The first aspect of this application provides an application management system for chemical equipment controllers, including a model management tool running on a user terminal, a scheduler and a MOTT server running on the equipment controller, the model management tool and the The scheduler is configured as a client of the MOTT server; the model management tool is used to send one or more files to the selected one or more controllers, the files including the model package; the scheduler in the controller uses Deploy the received model package in the file into the controller, and obtain the running data of the model in the controller and publish it with the first theme; the MOTT server is used to publish all the model packages published by the scheduler. The topic is pushed to the model management tool that is subscribed to the first topic.

Based on the above, model packages can be deployed to the controllers of one or more devices in batches, and one or more models can be deployed in batches. In addition, through the publish-subscribe mechanism of the MOTT service, model information can be actively sent to the model management tool on the user terminal, allowing users to obtain relevant information in a timely manner.

As a possible implementation of the first aspect, the model management tool is also used to publish management instructions in a second topic; the MOTT server is also used to push the second topic published by the model management tool. To the scheduler that subscribes to the second topic; the scheduler causes the corresponding model to execute the management instruction according to the management instruction corresponding to the second topic.

From the above, based on the publish-subscribe mechanism of the MOTT service, management instructions can be sent in batches to each model that has subscribed to the instruction topic.

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

As a possible implementation of the first aspect, the first topic includes one of the following topics or a combination of any topics: taking the name of the model as the topic, and the data under this topic includes: new data generated by the model with this name. Operation data; with different time periods as themes, the data under this theme includes: the operation data generated by the model corresponding to the time period; with a specific operation data type as the theme, the data under this theme includes: operation data related to the specific operation .

From the above, through the settings of different topics, users can flexibly and optionally obtain relevant data of the relevant models of the subscribed topics.

As a possible implementation manner of the first aspect, it also includes a model warehouse for providing each model package; the model management tool is also used for obtaining the model package from the model warehouse.

From the above, it facilitates centralized acquisition and management of model packages.

The second aspect of this application provides a management method for the application of a chemical equipment controller, which is implemented based on the application management system of any one of the chemical equipment controllers described in the first aspect. The method includes: selecting one or Multiple controllers, and one or more files corresponding to each controller, where the files include a model package; the model management tool sends the corresponding one or more files to the selected controller or controllers. file; the scheduler of the controller receives the corresponding file and deploys the model package in the file to the controller; the controller obtains the running data of the model in the controller and publishes it with the first theme; The MOTT server pushes the topic published by the scheduler to the model management tool subscribed to the first topic.

As a possible implementation of the second aspect, it also includes: the model management tool publishes management instructions in a second topic; the MOTT server pushes the second topic published by the model management tool to subscribed users. The scheduler of the second topic; the scheduler causes the corresponding model to execute the management instructions according to the management instructions corresponding to the second topic.

As a possible implementation of the second aspect, the first topic includes one of the following topics or a combination of any topics: taking the name of the model as the topic, and the data under this topic includes: new data generated by the model with this name. Operation data; with different time periods as themes, the data under this theme includes: the operation data generated by the model corresponding to the time period; with a specific operation data type as the theme, the data under this theme includes: operation data related to the specific operation .

A third aspect of the present application provides a computing device, including: a processor, and a memory, on which program instructions are stored. When executed by the processor, the program instructions cause the processor to execute any one of the second aspects. method described in the item.

A third aspect of the present application provides a computing device, including: a processor, and a memory, on which program instructions are stored. When executed by the processor, the program instructions cause the processor to execute any one of the second aspects. method described in the item.

A fourth aspect of the present application provides a computer-readable storage medium on which program instructions are stored. When executed by a computer, the program instructions cause the computer to implement any of the methods described in the second aspect.

Description of the drawings

Figure 1 is a schematic diagram of a management system applied on a chemical equipment controller provided by the first embodiment of the present application;

Figure 2 is a flow chart of a management method for applications on a chemical equipment controller provided by the second embodiment of the present application;

Figure 3 is a schematic structural diagram of a computing device provided by this application.

It should be understood that in the above structural schematic diagram, the size and shape of each block diagram 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 block diagrams presented in the structural schematic diagram only schematically represent the structural relationships between the block diagrams, but do not limit the physical connection methods of the embodiments of the present invention.

Detailed ways

The technical solution provided by this application will be further described below with reference to the accompanying drawings and examples. It should be understood that the system structure and business scenarios provided in the embodiments of this application are mainly to illustrate possible implementations of the technical solution of this application and should not be interpreted as the sole limitation of the technical solution of this application. Persons of ordinary skill in the art will know that with the evolution of system structures and the emergence of new business scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

It should be understood that the management solution for applications on the controller provided by the embodiments of the present application includes a management system and method for applications on the controller, computing devices and storage media, as well as equipment applied to the scheduling device or the scheduling method. Since the principles of solving problems of these technical solutions are the same or similar, in the following introduction of specific embodiments, some overlapping points may not be described again, but it should be considered that these specific embodiments have been referenced to each other and can be combined with each other.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. If there is any inconsistency, the meaning explained in this manual or the meaning derived from the content recorded in this manual shall prevail. In addition, the terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application. In order to accurately describe the technical content in this application and to accurately understand the present invention, the following explanations or definitions are provided for the terms used in this specification before describing the specific embodiments:

1) Message Queuing Telemetry Transport (MQTT): It is a lightweight communication protocol based on the publish-subscribe model. The advantage of MQTT is that it uses very little code and limited bandwidth to provide real-time and reliable messaging services for connecting remote devices. It can be applied to products such as the Internet of Things and small devices.

The framework for implementing MQTT communication includes publishers, subscribers, and servers. The publisher describes the data by defining published data types and related attributes, etc., and then publishes the data to the server; the subscriber can specify the data types and related attributes that they are interested in by defining subscription rules, and then Subscribe to this data. When the publisher has new data to publish, the server transmits the data to the subscribers.

2) Secure Shell (SSH): It is an encrypted network transmission protocol that can provide a secure transmission environment for network services in insecure networks. It enables connections between SSH clients and servers by creating a secure tunnel in the network.

3) Model: refers to runnable code that can implement a certain function and is packaged as a module (such as a file package). In this example, each dedicated application is encapsulated into a model. When the model is delivered to the device's controller, the model's configuration file (module.ini) will be delivered in conjunction with the model. The configuration file records the identification (ID), name information, version information, startup command format information, scheduling policy information, etc. of the dedicated application corresponding to the model. The configuration file can also record the file location (such as file directory) released by the model in the controller. Configuration files can be sent separately or packaged with the model in a package.

The application scenario of the management solution for applications on the controller provided by this application may be the application scenario of device security management. When the solution of this application is deployed on the user terminal side and the controller on the device, it can realize unified and batch deployment of multiple dedicated applications to the device controller, or unified and batch management of these dedicated applications, and can also obtain dedicated applications in a timely manner. Information actively uploaded by the application. Wherein, the above-mentioned user terminal is a user-side device, and the user terminal may be a computer, a laptop, a smart phone, a tablet, etc. Among them, the above-mentioned equipment can be intelligent industrial equipment, such as power generation equipment, mining equipment, smelting equipment, water conservancy equipment, etc., or some small equipment, such as intelligent control equipment for building air ducts, etc. These equipment have controllers. Among them, the controller of the equipment can be implemented by a control card or an industrial computer, and its hardware can include processor chips, memory, storage, and communication chips. The controller can run operating systems such as Intewell, or based on Linux, UNIX, or other operating systems. Multiple dedicated applications can be installed, deployed, and run on the operating system.

Below, the present application will be introduced in detail with reference to the accompanying drawings.

Figure 1 shows a schematic structural diagram of the first embodiment of the present application. The first embodiment is an application management system for chemical equipment controllers. The system includes a model management tool 11 running on a user terminal, including a model management tool 11 running on the equipment control system. The scheduler 21 and MOTT server 22 on the server may also include a model warehouse 30. Each dedicated application is packaged into a model package, and each model package can be sent to the controller in batches through the model management tool 11 on the user terminal side. The scheduler 21 on the device controller deploys each installation package to the controller. The following is a detailed introduction to the management system with reference to Figure 1:

Among them, the model management tool 11 has a human-computer interactive operation interface, allowing the user to graphically operate various functions provided by the model management tool 11 and display the information returned by the device-side controller. The following are examples of some of the functions provided by Model Management Tool 11:

1) The function of batch downloading or uploading model packages from the model warehouse 30 (each dedicated application is packaged as a model package), providing access to the local model library (the local model library is located at the user terminal) or the remote model library (the remote model library can be located at Functions provided by a server provided by a third-party service provider, or located in a server managed by the operator of the device);

2) The function of importing or exporting model packages to the model management tool 11;

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

4) Subscription/unsubscription function, which can provide a subscription operation interface to allow users to visually select the objects and content to be subscribed; among them, the objects to be subscribed are such as which device, which controller, and which model ( i.e. dedicated applications). The subscribed content includes the model's running status, logs, alarm information, fault information, general maintenance information, etc.

5) The function of displaying information sent by a model on a certain device side (i.e., a dedicated application). The information is specifically related to the subscribed objects and subscribed content;

6) The function of displaying and controlling the model operating status on the equipment side;

7) Commonly used model management functions on the device side, such as start instructions, disable instructions, simulation instructions, stop simulation instructions, manual debugging, stop manual debugging, uninstallation, etc.

Among them, the scheduler 21 is used to deploy the model package sent by the model management tool 11 into the controller during the deployment stage of the model (ie, dedicated application); and is used to obtain the management instructions sent by the model management tool 11 after the model is deployed. , and sent to the corresponding model for execution; and used to obtain the operating data of each model (such as instruction running results, model operating status, logs, alarm information, fault information, general maintenance information, etc.) after the model is deployed, to Feedback to the model management tool 11; and used to schedule the execution of each deployed model, for example, according to the scheduling policy recorded in the configuration file of each model, regularly, regularly or with variable periods, or based on monitoring event triggers, or priority, etc., to schedule the running of the corresponding model.

Among them, the MOTT server 22 is used to realize data transmission between the model management tool 11 and the scheduler 21 . Specifically, the model management tool 11 and the scheduler 21 serve as clients respectively, and are configured as the publisher and subscriber of a certain topic based on the relationship between data sending and receiving. For example, for management instructions to be issued by the user, such as execution instructions, query instructions, update instructions, uninstall instructions, etc., the model management tool 11 acts as a publisher to publish the management instructions in the form of a certain topic, and the scheduler 21 is configured to respond accordingly. Subscriber of the topic. Therefore, when the model management tool 11 releases the management instruction of the topic, the MQTT server 22 will push the topic to the scheduler 21 in time. The scheduler can then obtain the management instruction of the topic and based on the instruction , causing one or more models to execute the contents of the corresponding instructions. For another example, for the running data generated by the model, the scheduler 21 obtains these data and publishes them as a publisher of these data in the form of a certain topic. The model management tool 11 will be configured as a subscriber of these topics. Therefore, when the scheduler 21 After the server 21 publishes the data of a certain topic, the MQTT server 22 will push the topic to the model management tool 11 in time, and the model management tool 11 obtains the data of these topics.

Based on the MOTT server 22, as well as the model management tool 11 and the scheduler 21 as the client, a subscription-publishing architecture is implemented, which can provide each data to the user more flexibly. For example, the scheduler 21 can be based on the content of the data to be sent. Configure different topics so that users can obtain the data content of different subscribed topics through the model management tool 11. Examples are as follows:

1) The names of different models (i.e. programs) can be used as topics. The data under this topic includes: new running data generated by the model with this name. Specifically, when the model generates new running data, the scheduler 21 obtains and publishes the model name as the topic, so that the model management tool 11, as a subscriber, can obtain the subscribed running data of the topic. In this way, you can only subscribe to the topic you are interested in (that is, the model name), so that users can learn the running data of the model you are interested in in a timely manner.

2) Different time periods can be used as themes, and the data under this theme include: operating data generated by each model in the corresponding time period. Specifically, the scheduler 21 obtains the operating data generated by each model in the corresponding time period and publishes it on the topic, so that the model management tool 11, as a subscriber, can obtain the operating data of each model in the subscribed time period. Through this method, the time period can be used as the condition, so that the user can obtain the operating data of each model in the time period of interest in a timely manner.

3) A specific operating data type can be used as the subject, and the data under this subject include: operating data related to the specific operation. For example, the fault type is used as the theme. When a certain model generates such a fault, the scheduler 21 publishes information including the corresponding model based on the fault type. Through this method, when a certain fault occurs in a certain device, the user can promptly learn the information of the device that caused the fault.

The above is only an example and is not limited to the above topics. Different topics can be set according to management and security management needs. Subscribers can subscribe to all topics or part of the topics. In the form of subscription-publishing, it does not depend on the user's active data request. When the scheduler 21 running on the device controller publishes the corresponding topic, the active publishing of data is realized, and the MQTT server 22 pushes the topic data in a timely manner. to the model management tool 11 on the user terminal side as the subscriber, so that the user can learn the corresponding data in a timely manner. In addition, when there are multiple user terminals, the model management tools 11 on different user terminals, as subscribers, can subscribe to different topics respectively, so that different user terminals can only obtain data of the corresponding topics.

Among them, the model warehouse 30 is used to provide each model package that can be deployed to the device controller. It can be located in the cloud as a remote model warehouse, or it can be located on the user terminal as a local model warehouse. The model management tool 11 can be uploaded from the model warehouse 30 , download the model package.

Among them, the communication between the model management tool 11 on the user terminal and the MOTT server 22 or scheduler 21 on the device controller, such as the transmission of theme information, the transmission of model packages in the deployment stage, or the transmission of upgrade file packages, etc. Can be done based on SSH protocol for added security.

Figure 2 shows a flow chart of the second embodiment of the present application. The second embodiment of the present application provides a management method for applications on a chemical equipment controller, which is implemented based on the application management system of the chemical equipment controller. The method includes the following steps:

S10: Run the model management tool 11 on the user terminal side, present the user operation interface, respond to the user's operation, and determine the model to be deployed (including the configuration file in this example) and the controller of the target device.

The user operation interface may include a "select file" control for reading the model package into the model management tool 11. Each time a model package is read in, the name of the corresponding model package may be displayed. Through the user operation interface, you can also select the units to which the model package is to be deployed, where each unit corresponds to a controller of a device. Among them, different units (ie controllers) can deploy the same or different model packages read into the model management tool 11.

In this example, the model package and configuration file are packaged into one file. In other embodiments, different files can also be deployed to the controller of the corresponding device. The principle is the same as above and will not be described again.

This embodiment also supports the deployment of other files, such as board files and system files, into the controller of the corresponding device. The principles are the same as above and will not be described again.

S20: In response to the user's operation, the model management tool 11 sends the corresponding model package to the corresponding target device based on the previously determined model to be deployed and the controller of the corresponding target device.

As mentioned above, there may be one target device with multiple models to be deployed, or multiple devices and multiple models to be deployed.

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

The deployment process includes: releasing the model package, and storing the released files in the corresponding folder of the controller's file system. The folder can be the default folder, preferably the folder specified in the model's configuration file, and This model is launched by default.

Among them, different models are released to different folders, and the configuration files of each model are under the folder of each model.

A specific example is: the scheduler 21 receives the model file package (for example, it can be model20220616.tar.gz), the scheduler 21 releases the file package, and releases the model files and configuration files in it to the model1 directory (this directory is the default directory, or the directory specified in the configuration file), complete the installation of the program, and include the model into the scheduling queue managed by the scheduler 21. Among them, the scheduling queue managed by the scheduler 21 includes the identification of each model. The scheduler 21 will implement unified scheduling of each model in the scheduling queue based on the queue. Specifically, scheduling and execution can be performed according to the scheduling policy of the model. The scheduling strategy is configured in the configuration file of each model.

S40: The scheduler 21 schedules the running of each model in a queue, and the scheduler 21 monitors the running status of each model in real time, and generates corresponding topics for publication.

S50: The MQTT server 22 in the controller of the device pushes the topic published by the scheduler 21 to the user terminal side model management tool 11 as a subscriber, so as to be displayed by the model management tool 11.

Among them, the model management tool 11 also provides a management interface for topic subscription on the model management tool 11 to manage the topics that can be subscribed.

Among them, the model management tool 11 also provides a management interface that models the publication and subscription of topics on the scheduler 21 on the device controller to manage the contents of topics that can be published by the scheduler 21.

In addition, the model management tool 11 also acts as the publisher of the management instruction topic by default, and the scheduler 21 acts as the subscriber of the management instruction topic by default. Therefore, the management instructions issued by the model management tool 11 are pushed to the scheduler 21 by the MQTT server 22, and the scheduler 21 According to this instruction, the corresponding model is controlled to execute the corresponding instruction. Management instructions include operating the model, such as starting, disabling, simulating, stopping simulation, manual debugging, stopping manual debugging, uninstalling, etc.

In addition, in some embodiments, when the model management tool 11 in the above step S20 sends the corresponding model package to the corresponding target device, it can also send a package configuration file (package.ini). The package configuration file can be packaged with the model package in one file. Bag. The package configuration file is used to describe the package version, information and versions of multiple models protected in this file package.

FIG. 3 is a schematic structural diagram of a computing device 400 provided by an embodiment of the present application. The computing device can be the above method or its optional embodiments. The computing device can be a terminal, or a chip or chip system inside the terminal. As shown in FIG. 3 , the computing device 400 includes: a processor 410 , a memory 420 , and a communication interface 430 .

It should be understood that the communication interface 430 in the computing device 400 shown in Figure 3 can be used to communicate with other devices, and specifically can include one or more transceiver circuits or interface circuits.

The processor 410 can be connected to the memory 420 . The memory 420 may be used to store the program code and data. Therefore, the memory 420 may be a storage unit internal to the processor 410 , or may be an external storage unit independent of the processor 410 , or may include a storage unit internal to the processor 410 and an external storage unit independent of the processor 410 . part.

Optionally, the computing device 400 may also include a bus. Among them, the memory 420 and the communication interface 430 can be connected to the processor 410 through a bus. The bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, a line without an arrow is used in Figure 3, but it does not mean that there is only one bus or one type of bus.

It should be understood that in this embodiment of the present application, the processor 410 may be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (field programmable gate arrays, FPGAs) or other Programmed logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. Or the processor 410 uses one or more integrated circuits to execute relevant programs to implement the technical solutions provided by the 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 processor 410 may also include non-volatile random access memory. For example, processor 410 may also store device type information.

When the computing device 400 is running, the processor 410 executes the computer execution instructions in the memory 420 to perform any operation step of the above method and any optional embodiment thereof.

It should be understood that the computing device 400 according to the embodiments of the present application may correspond to the corresponding subject in performing the methods according to the various embodiments of the present application, and the above and other operations and/or functions of the various modules in the computing device 400 are respectively intended to implement the present application. For the sake of brevity, the corresponding processes of each method in the embodiment will not be described again here.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can 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 can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Embodiments of the present application also provide a computer-readable storage medium on which a computer program is stored. The program is used to perform the above method when executed by a processor. The method includes at least one of the solutions described in the above embodiments. one.

The computer storage medium in the embodiment of the present application may be any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of computer readable storage media include: electrical connections having one or more conductors, portable computer disks, hard drives, random access memory (RAM), read only memory (ROM), Erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. As used herein, a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit 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 suitable medium, including, but not limited to, wireless, wire, optical cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for performing the operations of the present application may be written in one or more programming languages, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional Procedural programming language—such as "C" or a similar programming language. 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 situations involving remote computers, the remote computer can 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 it can be connected to an external computer (such as an Internet service provider through the Internet). connect).

In addition, the words "first, second, third, etc." or similar terms such as module A, module B, module C, etc. in the description and claims are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understood that the specific order or sequence may be interchanged where permitted, so that the embodiments of the application described herein can be implemented in an order other than that illustrated or described herein.

In the above description, the labels indicating the steps involved, such as S110, S120..., etc., do not necessarily mean that this step will be executed. If permitted, the order of the preceding and following steps can be interchanged, or executed at the same time.

The term "comprising", as used in the specification and claims, should not be construed as being limited to what is listed thereafter; it does not exclude other elements or steps. It should therefore be construed as specifying the presence of stated features, integers, steps or components mentioned, but not excluding the presence or addition of one or more other features, integers, steps or components and groups thereof. Therefore, the expression "an apparatus comprising means A and B" should not be limited to an apparatus consisting only of components A and B.

Reference in this 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 present application. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places in 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 are only the preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments. Without departing from the concept of the present application, it can also include more other equivalent embodiments, all of which belong to the present application. Apply for protection scope.

Claims (10)

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;

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

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

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.

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.