Event notification method, event notification device and event processing system
The event notification method simplifies the docking of industrial equipment and information systems in low-code application development, solves the problems of docking complexity and high cost in the existing technology, and realizes the rapid development and efficient integration of low-code applications.
Patent Information
- Application Number
- CN202410550177.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-05-06
- Publication Date
- 2024-12-03
AI Technical Summary
When existing low-code development tools achieve the connection between industrial IoT devices and industrial information systems, they have high thresholds, high costs and low efficiency, requiring developers to have complex professional knowledge and long implementation cycles.
Provide an event notification method, by obtaining data from industrial IoT devices and industrial information systems, analyzing and converting according to preset specifications, simplifying the docking process, reducing docking complexity, realizing event notification, and triggering the business logic of target applications.
It simplifies the docking process of industrial equipment and information systems in low-code application development, reduces development costs, improves development efficiency, and allows ordinary business personnel to carry out event integrated development of low-code applications.
Smart Images

Figure CN119065868A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of Internet of Things, and in particular to an event notification method, an event notifier and an event processing system. Background Art
[0002] In the low-code platform system, users can quickly develop applications by dragging and dropping and orchestrating business events, which has the characteristics of low development cost, high efficiency, and fast application function iteration.
[0003] In traditional industrial low-code application development, if you want to realize the call integration with factory equipment, you generally need to go through multiple complex steps such as device docking, interface docking, and business event docking. This makes the threshold and cost of calling industrial equipment in low-code applications relatively high. Users not only need to understand the operating principle of the Internet of Things platform (IOT), but may also need to know the operating process and principle of hardware devices such as sensors and PLCs. Some even need to know the principle process of device communication protocols such as mqtt, OPC UA, and Modbus. Only through protocol analysis, protocol conversion, and data docking can the docking call between low-code applications and industrial equipment be smoothly realized. This undoubtedly creates considerable difficulties in integrating industrial equipment in industrial low-code applications. In addition, in low-code applications, if you want to realize the call with the factory information system, you usually need to perform complex operations such as system interface authentication, protocol conversion, and data analysis. The docking process is similar to the device docking process and is also relatively complicated, with a high docking threshold.
[0004] It can be seen that the low-code development tools currently on the market need to be able to connect with industrial IoT devices and industrial information systems. This requires a high level of professionalism from low-code developers, a complex development process, and a long implementation cycle, resulting in high application development costs and low efficiency. Summary of the invention
[0005] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.
[0006] In view of the shortcomings of the prior art mentioned above, the present invention discloses an event notification method, an event notifier and an event processing system, so as to provide a simple, easy-to-operate, fast and low-cost way for low-code developers to realize the docking of the low-code applications to be developed with industrial Internet of Things equipment and industrial information systems, thereby reducing application development costs and improving application development efficiency.
[0007] An embodiment of the present invention discloses an event notification method, which includes: obtaining device data reported by an industrial Internet of Things device, and determining device attribute data and device events of the device data according to a preset device data parsing specification; obtaining system data sent by an industrial information system, and determining system attribute data and system events of the system data according to a preset event notification interface specification; determining a target application and input parameter rules of the target application according to the event to be notified and preset application event subscription data, and converting the event attribute data to be notified of the event to be notified into input attribute data to be notified according to the input parameter rules, the event to be notified includes the device event and / or the system event, and the event attribute data to be notified includes the device attribute data and / or the system attribute data; sending the input attribute data to be notified to the target application, triggering the target application to execute the business logic corresponding to the event to be notified based on the input attribute data to be notified, so as to complete the event notification to the target application.
[0008] In one embodiment of the present invention, before determining the device attribute data and device events of the device data according to a preset device data parsing specification, the method includes: obtaining the subscription event requirements of a preset application; creating an event to be subscribed according to the subscription event requirements, and defining the event type and event attributes of the event to be subscribed; if the event type is a device event type, determining at least one industrial IoT device as the event source of the event to be subscribed, and defining a device data parsing sub-specification for each industrial IoT device, so as to generate corresponding device attribute data based on the device data reported by the event source through the device data parsing sub-specifications of all industrial IoT devices, and trigger the generation of device events; generating a preset device data parsing specification based on the device data parsing sub-specifications of all industrial IoT devices.
[0009] In one embodiment of the present invention, a device data parsing sub-specification is defined for each industrial IoT device, so as to trigger the generation of a device event based on the device data reported by the event source through the device data parsing sub-specifications of all industrial IoT devices, including: obtaining an industrial equipment object model; determining a device data parsing sub-specification for each industrial IoT device based on the industrial equipment object model, the device data parsing sub-specification including at least a point data trigger condition and a point data format; performing point data format identification on the device data reported by the event source to obtain point format data; if the point format data meets the point data trigger condition, triggering the generation of the device event.
[0010] In one embodiment of the present invention, after generating a preset device data parsing specification based on the device data parsing sub-specifications of all industrial IoT devices, the method further includes: triggering the release and operation of the preset application.
[0011] In one embodiment of the present invention, before determining the system attribute data and system events of the system data according to a preset event notification interface specification, the method includes: obtaining the subscription event requirements of a preset application; creating an event to be subscribed according to the subscription event requirements, and defining the event type and event attributes of the event to be subscribed; if the event type is a system event type, determining at least one industrial information system as the event source of the event to be subscribed, and defining an event notification interface sub-specification for each industrial information system, so as to generate corresponding system attribute data based on the system data reported by the event source through the event notification interface sub-specifications of all industrial information systems, and trigger the generation of system events; generating a preset event notification interface specification based on the event notification interface sub-specifications of all industrial information systems.
[0012] In one embodiment of the present invention, an event notification interface sub-specification of each industrial information system is defined, including: dynamically creating an event trigger interface specification by importing a Swagger Rest API to define an event notification interface sub-specification of each industrial information system.
[0013] In one embodiment of the present invention, before determining the target application and the input parameter rules of the target application based on the event to be notified and the preset application event subscription data, the method includes: obtaining the subscription event requirements of the preset application, wherein the subscription event requirements are determined based on the business logic of the preset application; comparing the subscription event requirements with the created event description of the created event; if there is a created event description that meets the subscription event requirements, triggering the preset application to subscribe to the created event corresponding to the created event description; obtaining the input parameter rules corresponding to the business logic; generating the preset application event subscription data based on the created event, the preset application, and the input parameter rules, wherein the preset application event subscription data represents the subscription relationship between the event and the preset application, and the input parameter rules of the event subscribed by the preset application.
[0014] In one embodiment of the present invention, a target application and input parameter rules of the target application are determined based on the event to be notified and preset application event subscription data, including: if the number of the target applications is multiple; determining the input parameter rules of each target application corresponding to the event to be notified based on the preset application event subscription data, so as to convert the event attribute data to be notified of the event to be notified into corresponding input attribute data to be notified according to the input parameter rules of each target application, and sending the input attribute data to be notified to the corresponding target application.
[0015] An embodiment of the present invention discloses an event notifier, which includes: an industrial equipment data adaptation module, which is used to obtain equipment data reported by industrial Internet of Things equipment, and determine equipment attribute data and equipment events of the equipment data according to a preset equipment data parsing specification; an industrial information system interface adaptation module, which is used to obtain system data sent by the industrial information system, and determine system attribute data and system events of the system data according to a preset event notification interface specification; an event execution module, which is used to determine a target application and an input parameter rule of the target application according to an event to be notified and preset application event subscription data, convert the event attribute data to be notified of the event to be notified into input attribute data to be notified according to the input parameter rule, the event to be notified includes the device event and / or the system event, and the event attribute data to be notified includes the device attribute data and / or the system attribute data, and is used to send the input attribute data to be notified to the target application, trigger the target application to execute the business logic corresponding to the event to be notified based on the input attribute data to be notified, so as to complete the event notification to the target application.
[0016] An embodiment of the present invention discloses an event processing system, which includes the event notifier described in any of the above embodiments, one or more preset applications, one or more industrial devices, and one or more industrial information systems, wherein: the industrial equipment is used to report device data to the industrial equipment data adaptation module of the event notifier through an industrial data acquisition gateway; the industrial information system is used to send system data to the industrial information system interface adaptation module of the event notifier; when the preset application is the target application, the preset application is used to receive the input attribute data to be notified sent by the event execution module of the event notifier, and execute the input attribute data to be notified through the business logic corresponding to the event to be notified.
[0017] An embodiment of the present invention discloses an electronic device, including: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the above method.
[0018] Beneficial effects of the present invention:
[0019] By respectively acquiring the device data reported by the industrial IoT device and the system data sent by the industrial information system, the device attribute data, device events, system attribute data and system events are obtained, and one or more target applications that subscribe to the above events are found according to the device events and / or system events, and according to the input parameter rules of each target application, the device attribute data and / or system attribute data are converted into input attribute data to be notified, and sent to the corresponding target application, triggering the target application to execute the corresponding business logic, and completing the event notification of the target application. Since there is no need to perform secondary development on the application side, the industrial IoT device side or the industrial information system side for event notification, the docking development process of system event integration is simplified, the application development cost is reduced, and the application development efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 is a flow chart of an event notification method in an embodiment of the present invention;
[0021] Figure 2 It is a schematic diagram of an application interface of a reading object model in the event notification method in an embodiment of the present invention;
[0022] Figure 3 It is a schematic diagram of an application interface for defining event generation rules based on a physical model in an event notification method according to an embodiment of the present invention;
[0023] Figure 4 is a schematic diagram of an event definition process in an event notification method in an embodiment of the present invention;
[0024] Figure 5 It is a schematic diagram of an event triggering process in an event notification method in an embodiment of the present invention;
[0025] Figure 6 is a schematic diagram of the structure of an event notifier in an embodiment of the present invention;
[0026] Figure 7 is a schematic diagram of the structure of an event processing system in an embodiment of the present invention;
[0027] Figure 8 It is a schematic diagram of the structure of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION
[0028] The following describes the embodiments of the present invention through specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and sub-samples in the embodiments can be combined with each other without conflict.
[0029] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.
[0030] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.
[0031] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so as to describe the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.
[0032] Unless otherwise stated, the term "plurality" means two or more.
[0033] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.
[0034] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.
[0035] In order to facilitate understanding of the technical solutions of the embodiments of the present application, a brief introduction to the related technologies of the present application is first given as follows.
[0036] Application Program Interface (API): API is a set of definitions, programs and protocols. Different applications can communicate with each other through API. One of the main functions of API is to provide a common set of functions. Representational state transfer (REST) is a common style of API. Usually, after the server that provides the API (hereinafter referred to as the server) provides the API to the outside world through the hypertext transfer protocol (HTTP), the API can be called by other applications (called the client that calls the API, hereinafter referred to as the client). After calling the API provided by the server, the client can implement the functions provided by the API. API protocol information: API protocol information is used to specify a series of rules for using the API, for example, specifying the input and output parameters, URI, etc. of the API.
[0037] The physical model is a digital abstract description of the device, describing what the device is, what it can do, and what services it can provide. The physical model digitizes the physical device in the physical space and builds a data model of the entity in the cloud, that is, the entity in the physical space is formatted and represented in the cloud.
[0038] IOT (Internet of things) refers to the real-time collection of any object or process that needs to be monitored, connected, and interacted through various devices and technologies such as information sensors, radio frequency identification technology, global positioning system, infrared sensors, laser scanners, etc., and the collection of various required information such as sound, light, heat, electricity, mechanics, chemistry, biology, location, etc. Through various possible network access, it realizes ubiquitous connection between objects and objects, objects and people, and realizes intelligent perception, identification and management of objects and processes. The Internet of Things is an information carrier based on the Internet, traditional telecommunications networks, etc. It allows all ordinary physical objects that can be independently addressed to form an interconnected network.
[0039] In the related art, the general steps for integrating application / low-code application with industrial equipment or industrial information system for event notification are as follows: (1) Application / low-code application develops event notification interface to receive calls from event source; (2) Event source (industrial equipment and industrial information system) calls the above event notification interface; (3) Application / low-code application receives the call and executes the business logic corresponding to the event. The above process involves the development of both the application side and the event source, which is usually cumbersome, resulting in low development efficiency and high development cost.
[0040] In traditional industrial low-code application development, if you want to achieve event integration with factory equipment, you generally need to go through the process of application interface development, event source notification processing, and application receiving and processing events. This makes the threshold and cost of integrating industrial equipment and industrial information systems in low-code applications relatively high. Users not only need to understand the operating principles of the Internet of Things platform (IOT), but may also need to know the operating process and principles of hardware devices such as sensors and PLCs, and some even need to know the principles and processes of device communication protocols such as MQTT, OPC UA, and Modbus.
[0041] In addition, if you want to implement event notifications for low-code applications from industrial equipment and industrial information systems, it requires not only the development of the notified party, but also the development cooperation of the notifying party, which also creates a considerable obstacle to the system integration of low-code applications.
[0042] To solve the above problems, an embodiment of the present invention provides an event notification method that can simplify the above process. Only simple configuration is required on the application / low-code application side to achieve docking with the event source. By adapting to both industrial information systems and industrial equipment event sources, it can effectively reduce the difficulty of event integration development for low-code developers, allowing ordinary business personnel to also perform event integration development for low-code applications.
[0043] Combination Figure 1 As shown, Figure 1 FIG. 1 is a flow chart of an event notification method in an embodiment of the present invention. Figure 1 As shown, the embodiment of the present disclosure provides an event notification method, including:
[0044] Step S110, obtaining device data reported by the industrial IoT device, and determining device attribute data and device events of the device data according to a preset device data parsing specification.
[0045] In the embodiment of the present application, there is no need to make special development for the reporting interface of the industrial IoT device, and the method can support the original data reporting method of the industrial IoT device. For example, the device data can be reported by the industrial IoT device through the industrial data acquisition gateway through methods such as MQTT (Message Queuing Telemetry Transport). There can be one or more industrial IoT devices, and the number is not limited. The selection of industrial IoT devices can be added or reduced according to the subscription event requirements of subsequent applications. When the application served by this method has a demand for the device data of a certain industrial IoT device, the device data reported by the industrial IoT device is obtained. For non-required industrial IoT devices, their device data can be refused to ensure system security.
[0046] The industrial IoT device can report its device data regularly so that the event notifier can obtain the device data, or it can obtain its device data by sending a data acquisition request to the industrial IoT device regularly or irregularly.
[0047] The execution of step S110 can be achieved through an event notifier. The event notifier is independent of the low-code application, the IoT platform, and the industrial information system. In this way, in scenarios where the triggering conditions of an event need to be modified, it can be achieved based on the adjustment of the event notifier, without the need to redevelop the low-code application, which is more flexible.
[0048] The preset device data parsing specification can be determined by the industrial device object model of the industrial IoT device, or can be obtained by the parsing specification predefined by the technicians in this field. For example, the MQTT data reported by the industrial IoT device can be read according to the specification defined by the object model, and the device event and device attribute data can be generated according to the preset configuration rules. The device attribute data is in the preset initial attribute data format. As an example, the device attribute data of all industrial IoT devices are stored in the preset initial attribute data format so that they can be called by other applications later. As an example, the device data parsing specification can characterize the event triggering conditions and the specific attribute content of the event.
[0049] In one embodiment, before determining the device attribute data and device events of the device data according to the preset device data parsing specification, the method includes: obtaining the subscription event requirements of the preset application; creating the event to be subscribed according to the subscription event requirements, and defining the event type and event attributes of the event to be subscribed; if the event type is the device event type, determining at least one industrial IoT device as the event source of the event to be subscribed, and defining the device data parsing sub-specification of each industrial IoT device, so as to generate the corresponding device attribute data based on the device data reported by the event source through the device data parsing sub-specification of all industrial IoT devices, and trigger the generation of device events; based on the device data parsing sub-specification of all industrial IoT devices, generate the preset device data parsing specification. For example, event triggering rules and attribute content can be set for each industrial IoT device to obtain the device data parsing sub-specification. Since the event notifier may be for multiple industrial IoT devices, multiple event triggering conditions (i.e., event generation rules) and corresponding attribute content can be set for the device data of each industrial IoT device. When the device data meets the event triggering condition, the attribute data is generated according to the requirements of the attribute content.
[0050] When developing low-code applications (also known as low-code applications), based on the orchestrated low-code application business logic, the encoded low-code application business logic may have multiple sub-logics. Based on the business needs of each sub-logic, you can first select the Internet of Things device (also known as the Industrial Internet of Things device), and then select the low-code business logic associated with each Industrial Internet of Things device, and configure the low-code business logic parameter association, so that when an event is generated later, you can find the business logic of the low-code application associated with the event, call the business logic, and complete the low-code business logic parameter association before publishing the low-code application.
[0051] Following the above embodiment, after generating a preset device data parsing specification based on the device data parsing sub-specifications of all industrial IoT devices, the method further includes: triggering the release and operation of a preset application. After the low-code application is released, the deployment of the low-code application is completed, and then the low-code application is run. After a certain event is monitored or a certain event is triggered, the business logic corresponding to the low-code application can be triggered to perform a preset operation.
[0052] Continuing from the above embodiment, a device data parsing sub-specification is defined for each industrial IoT device, so as to trigger the generation of device events based on the device data reported by the event source through the device data parsing sub-specifications of all industrial IoT devices, including: obtaining the industrial equipment object model; determining the device data parsing sub-specification of each industrial IoT device based on the industrial equipment object model, the device data parsing sub-specification at least including the point data triggering condition and the point data format; performing point data format identification on the device data reported by the event source to obtain point format data; if the point format data meets the point data triggering condition, triggering the generation of the device event.
[0053] As an example, when developing low-code applications, different event sources are defined in the event notifier in advance. By importing the industrial equipment object model, the point data format reported by the equipment is dynamically identified, and then the triggering of the equipment event is identified by defining the point data triggering conditions (a form of event generation rules). For example, if a certain data reaches the preset data threshold, the equipment event is triggered.
[0054] See also Figure 2 , Figure 2 is a schematic diagram of an application interface of a reading object model in an event notification method in an embodiment of the present invention, such as Figure 2As shown, taking the transmission protocol as mqtt, the industrial data acquisition gateway as TBOX, and the number of industrial IoT devices as 10 as an example, the device data can be read and parsed through the pre-set object model. The object model supports users to implement it by importing it into the preset notification application, and it can also support users to export the object model in the notification application. The editing control can be used to control whether the object model is allowed to be adjusted. After the object model reads the device data, it will at least get the device attribute data such as attribute identification, attribute name, data type, read-write type, description (attribute content requirements), etc. Each attribute data also supports adjustment through the editing control in the operation module. You can also manually add, import, and export attributes, and it also supports event definition.
[0055] See also Figure 3 , Figure 3 is a schematic diagram of an application interface for defining event generation rules based on a physical model in an event notification method according to an embodiment of the present invention. Figure 3 As shown, when editing an event, you can define basic information such as event ID, event name, event level, output parameters, JSON object, subscription type, event subscription, description, etc. The subscription type can be transparent or other. Subscriptions can be added through event subscriptions, and event generation rules can be added for subscriptions. For example, when the vehicle speed is greater than or equal to 100 and the vehicle speed is less than 130, attribute reporting is performed. You can also add a mapping to associate vehicle speed with speed. For event generation rules, other rules can be added by adding. When the event generation rules are met, the corresponding device event is generated.
[0056] Step S120, acquiring system data sent by the industrial information system, and determining system attribute data and system events of the system data according to a preset event notification interface specification.
[0057] It should be noted that the execution sequence between step S110 and step S120 is not limited here. During the execution of the low-code application, step S110 and step S120 can be executed sequentially once or multiple times, or randomly once or multiple times. This method supports the reception of device data reported by industrial IoT devices, and also supports the reception of system data reported by industrial information systems.
[0058] In one embodiment, before determining the system attribute data and system events of system data according to a preset event notification interface specification, the method includes: obtaining the subscription event requirements of a preset application; creating an event to be subscribed according to the subscription event requirements, and defining the event type and event attributes of the event to be subscribed; if the event type is a system event type, determining at least one industrial information system as the event source of the event to be subscribed, and defining the event notification interface sub-specification of each industrial information system, so as to generate corresponding system attribute data based on the system data reported by the event source through the event notification interface sub-specifications of all industrial information systems, and trigger the generation of system events; generating a preset event notification interface specification based on the event notification interface sub-specifications of all industrial information systems.
[0059] Following the above embodiment, an event notification interface sub-specification of each industrial information system is defined, including: dynamically creating an event trigger interface specification by importing a Swagger Rest API to define an event notification interface sub-specification of each industrial information system.
[0060] Swagger Rest API, Swagger is a RESTFUL interface document online automatic generation + functional testing software. Swagger Rest API is a REST (Representational State Transfer, a software architecture style) style HTTP interface based on the Swagger specification, API (Application Programming Interface). Through the Swagger method, you can define input, address, input parameters, output parameters and other information. Subsequent industrial information systems can report corresponding system data according to their requirements by calling the Swagger Rest API.
[0061] When developing low-code applications, first create the events required by the low-code application (that is, the preset application) in the event notifier, and then define the event type and attributes of the event. If the event type is an industrial information system, add the industrial information system as the event source, and then use the Swagger Rest API to dynamically create the event trigger interface specification. The event trigger interface can be generated according to the interface specification (original interface specification) defined by the third-party system (the industrial information system added as the event source) (generate an interface that can receive the system data reported by the industrial information system corresponding to the event notifier, and generate a preset event notification interface specification). The preset event notification interface specification defined by the event notifier can obtain system events and system attribute data based on the system data reported by the industrial information system. The system attribute data is in a preset initial attribute data format (which can be the same as or different from the initial attribute data format of the industrial IoT device). As an example, the system attribute data of all industrial information systems are stored in accordance with the preset initial attribute data format so that they can be called by other applications later.
[0062] The above method can complete the definition of events by the event notifier.
[0063] See also Figure 4 , Figure 4 FIG. 1 is a schematic diagram of an event definition process in an event notification method according to an embodiment of the present invention. Figure 4 As shown, the event notifier adapted to the low-code platform creates events based on the event requirements of the low-code application during the low-code application development process, and then defines the event type and attributes, and adds event sources according to the event type. If the event type is an industrial information system type, add the corresponding industrial information system as the event source. If the event type is an industrial equipment type, add the corresponding industrial IoT device as the event source. Then, for the industrial information system, determine the interface specification by importing Swagger to define the event notification interface specification, and determine the parsing specification by reading the IoT model of the industrial IoT device on the IoT platform to define the device data parsing specification. This completes the event definition.
[0064] When creating an event, you can define the subscription type of the event, such as broadcast events and targeted events. Broadcast events allow one event to have multiple subscribers, while targeted events allow one event to have only one subscriber. Subscribers can be the business logic of the application.
[0065] Step S130, determining the target application and the input parameter rule of the target application according to the event to be notified and the preset application event subscription data, and converting the event attribute data to be notified of the event to be notified into the input attribute data to be notified according to the input parameter rule.
[0066] Among them, the events to be notified include device events and / or system events, and the attribute data of the events to be notified include device attribute data and / or system attribute data. It can be understood that device data may trigger the generation of device events, or may not trigger the generation of device events. Similarly, system data may also trigger the generation of system events, or may not trigger the generation of system events. The target application is determined based on which type of event is currently generated. When the event to be notified is a device event, the corresponding attribute data of the event to be notified is the device attribute data; accordingly, when the event to be notified is a system event, the corresponding attribute data of the event to be notified is the system attribute data; when the event to be notified is a system event and a device event, the corresponding attribute data of the event to be notified is the system attribute data and the device attribute data.
[0067] An event manager may correspond to one or more preset applications, and a preset application may have multiple business logics with time event triggering requirements. At this time, if the generated event to be notified is broadcast to all preset applications, on the one hand, it will cause a waste of data transmission resources, and on the other hand, it will not be conducive to data security. At this time, according to the method provided in the aforementioned embodiment, according to the event subscription situation of the preset application to the event notifier during the development process, or according to the event definition data configured by the event notifier based on the event requirements of the preset application during the development process as the preset application event subscription data, based on the preset application event subscription data, find which preset application and which business logic the event to be notified is subscribed to, and use the preset application that subscribes to the event to be notified as the target application, and use the entry parameter rules of the subscribed business logic as the input parameter rules, and then convert the attribute data of the event to be notified according to the input parameter rules to obtain data that can be used by the business logic, that is, to obtain the input attribute data to be notified.
[0068] It should be noted that the preset application can be a low-code application or an application developed in other ways.
[0069] In one embodiment, before determining the target application and the input parameter rules of the target application based on the event to be notified and the preset application event subscription data, the method includes: obtaining the subscription event requirements of the preset application, the subscription event requirements are determined based on the business logic of the preset application; comparing the subscription event requirements with the created event description of the created event; if there is a created event description that meets the subscription event requirements, triggering the preset application to subscribe to a created event corresponding to the created event description; obtaining the input parameter rules corresponding to the business logic; generating the preset application event subscription data based on the created event, the preset application, and the input parameter rules, the preset application event subscription data representing the subscription relationship between the event and the preset application, and the input parameter rules of the event subscribed by the preset application.
[0070] Since the event notifier may have multiple predefined events, if an event is defined for each business logic of each preset application, it may cause the business logic of the two preset applications to have the same subscription event requirements. In this way, the event notifier may have defined an event based on the subscription event requirements of the previous preset application. If the same event (event name and attribute data are the same) is defined based on the same subscription event requirements of the next preset application, it will cause event redundancy in the event notifier, resulting in resource waste. After obtaining the subscription event requirements of the preset application, first verify whether the same subscription event requirements have been received in the historical data, or whether the created event description of the currently defined event can meet the subscription event requirements received this time. If so, in order to avoid resource waste, the current preset application can be directly subscribed to the created event that has been created in the history.
[0071] The created event description may also be determined according to its corresponding subscription event requirement. As an example, the created event description may directly use the subscription event requirement that triggers its defined event, or the created event description may be associated with the subscription event requirement through an association relationship configured by a person skilled in the art, so that the subsequent comparison of the subscription event requirement with the created event description of the created event can obtain the result that the created event description meets the subscription event requirement.
[0072] Although the subscription event requirements of two preset applications may be the same, the input parameter requirements of the business logic they apply may be different. In this case, it is necessary to generate the preset application event subscription data based on the created events, preset applications, and input parameter rules, so as to find the corresponding target application based on the preset application event subscription data and the events to be notified, and find the input parameter rules of the target application.
[0073] Continuing from the above embodiment, the target application and the input parameter rules of the target application are determined according to the event to be notified and the preset application event subscription data, including: if the number of target applications is multiple; the input parameter rules of each target application corresponding to the event to be notified are determined according to the preset application event subscription data, so as to convert the event attribute data to be notified of the event to be notified into corresponding input attribute data to be notified according to the input parameter rules of each target application, and send the input attribute data to be notified to the corresponding target application.
[0074] If there are multiple target applications, as mentioned in the above embodiment, there may be two target applications that require different input parameter rules for the business logic of the event to be notified. In order to avoid difficulties for subsequent applications in using event attribute data, the attribute data of the event to be notified can be converted according to the input parameter rules of each target application to obtain the notification input attribute data that can be used by the business logic of the target application.
[0075] See also Figure 5 , Figure 5 FIG. 1 is a schematic diagram of an event triggering process in an event notification method according to an embodiment of the present invention. Figure 5 As shown, taking the preset application as a code application as an example, and taking the event notification method running on the low-code platform-event notifier as an example, the process involves the low-code platform, industrial information system, low-code platform-event notifier, and IOT Internet of Things. When developing low-code applications (preset applications, low-code applications) on the low-code platform, the low-code application business logic will be arranged, and the Internet of Things device will be selected according to the business logic, that is, one or more industrial Internet of Things devices will be added as the event source, and then the associated low-code business logic will be selected. One event can be associated with one or more business logics. Configure the low-code business logic parameter association to know the input parameter rules of the business logic, so that after obtaining the event required by the business logic, the event attribute data of the event will be converted into data that can be used by the business logic based on the input parameter rules. After completing the above configuration, the low-code application is published. Run the low-code application. When the low-code application is running, the event source notifies the adapter module of the event notifier, or the adapter module of the event notifier parses the mqtt data reported by the industrial equipment to complete the event identification and triggering.
[0076] For example, when the event source is an industrial information system, the industrial information system event calls notification and reports system data. The event notifier determines whether the system data triggers event generation (that is, triggers the event notifier to execute the steps of business event triggering and parameter parsing). If an event is generated based on the system data, the system attribute data of the system event is further determined. A business event notification is then generated, and the system attribute data is sent to the business logic corresponding to the low-code application to trigger the execution of the business logic and complete the event notification of the industrial information system and the low-code application. As an example, the event source can drive the notification mechanism of business events by calling the pre-configured industrial information system interface processing module in the event notifier, receiving the parameters of the business event, querying the event source and event subscription, and then finding the target application and the business logic corresponding to the target application.
[0077] For example, when the event source is an industrial IoT device of the IOT IoT platform, the device data of the industrial IoT device is reported through MQTT and other methods, that is, the industrial device data is reported through MQTT, and then the event notifier parses and identifies the device data, triggers business events and analyzes parameters. If the device event and device attribute data are obtained, a business event notification is generated, and the device attribute data is sent to the business logic corresponding to the low-code application, triggering the execution of the business logic to complete the event notification of the industrial equipment and the low-code application. As an example, the industrial equipment data processing module pre-set by the event notifier processes industrial equipment events by reading the MQTT message queue provided by the industrial data acquisition gateway. The industrial equipment data module is connected to the industrial equipment object model library to realize the parsing, processing, judgment and event triggering of equipment data. The event execution module is used to query the event source and event subscription. The downstream low-code application business logic is notified through the event notification module to perform business processing to complete the event notification of industrial equipment and low-code applications.
[0078] Step S140 , sending the input attribute data to be notified to the target application, triggering the target application to execute the business logic corresponding to the event to be notified based on the input attribute data to be notified, so as to complete the event notification to the target application.
[0079] The execution method of the business logic here can be implemented in a manner known to those skilled in the art and is not limited here.
[0080] The event notification method provided in the above embodiment obtains device attribute data, device events, system attribute data and system events by respectively acquiring device data reported by industrial IoT devices and system data sent by industrial information systems, finds one or more target applications that subscribe to the above events according to device events and / or system events, and converts the device attribute data and / or system attribute data into input attribute data to be notified according to the input parameter rules of each target application, sends it to the corresponding target application, triggers the target application to execute the corresponding business logic, and completes the event notification of the target application. Since there is no need to perform secondary development on the application side, industrial IoT device side or industrial information system side for event notification, the docking development process of system event integration is simplified, the application development cost is reduced, and the application development efficiency is improved.
[0081] The above-mentioned event notification method can adapt to two event sources, industrial IoT devices and industrial information systems, at the same time. There is no need to adapt and adjust the industrial IoT devices, industrial information systems and applications separately, which is simpler and easier to execute. This method can automatically read the device data reported by the industrial IoT device according to the specifications defined by the industrial equipment object model, identify the industrial equipment event data, and then convert it into a business event and notify and call the low-code application business logic to complete the event integration of industrial equipment and low-code applications. The definition of the event notification interface format can also be completed by identifying interface specification files such as Swagger. The interface specifications of event notification can be determined by different third-party industrial information systems. There is no need for third-party industrial information systems to perform secondary development to connect to the event system, simplifying the docking development process of system event integration. This unified event notification method can effectively reduce the technical difficulty of event integration for low-code application developers and reduce the skill requirements for developers.
[0082] Through this event notification method, it is possible to define separate device events and system events based on the business logic of application development orchestration, simplifying the calls to industrial equipment and industrial information systems in industrial low-code application development, simplifying model definitions, and making it unnecessary for low-code developers to have a detailed understanding of industrial information systems and industrial IoT devices. By passing the attribute data of the event to be notified to the business logic through the event notification method, it can be quickly integrated with industrial equipment and information systems in low-code applications, greatly improving the efficiency of low-code application development.
[0083] See also Figure 6 , Figure 6 FIG. 1 is a schematic diagram of the structure of an event notifier in an embodiment of the present invention. Figure 6 As shown, an embodiment of the present invention further provides an event notifier 600, which includes: an industrial device data adaptation module 601, which is used to obtain device data reported by industrial IoT devices, and determine device attribute data and device events of the device data according to a preset device data parsing specification; an industrial information system interface adaptation module 602, which is used to obtain system data sent by the industrial information system, and determine system attribute data and system events of the system data according to a preset event notification interface specification; an event execution module 603, which is used to determine the target application and the input parameter rules of the target application according to the event to be notified and the preset application event subscription data, convert the event attribute data to be notified of the event to be notified into the input attribute data to be notified according to the input parameter rules, the event to be notified includes device events and / or system events, and the event attribute data to be notified includes device attribute data and / or system attribute data, and is used to send the input attribute data to be notified to the target application, trigger the target application to execute the business logic corresponding to the event to be notified based on the input attribute data to be notified, so as to complete the event notification to the target application.
[0084] In one embodiment, the event notifier further includes an event management module, which is used to obtain the subscription event requirements of the preset application before the industrial device data adaptation module determines the device attribute data and device events of the device data according to the preset device data parsing specification; create the event to be subscribed according to the subscription event requirements, and define the event type and event attributes of the event to be subscribed; if the event type is a device event type, determine at least one industrial IoT device as the event source of the event to be subscribed, and define the device data parsing sub-specification of each industrial IoT device, so as to generate corresponding device attribute data based on the device data reported by the event source through the device data parsing sub-specification of all industrial IoT devices, and trigger the generation of device events; generate the preset device data parsing specification based on the device data parsing sub-specification of all industrial IoT devices. And trigger the release and operation of the preset application.
[0085] In one embodiment, the industrial equipment data adaptation module is also used to obtain the industrial equipment object model; determine the device data parsing sub-specification of each industrial IoT device based on the industrial equipment object model, and the device data parsing sub-specification at least includes the point data trigger condition and the point data format; perform point data format identification on the device data reported by the event source to obtain point format data; if the point format data meets the point data trigger condition, trigger the generation of a device event.
[0086] In one embodiment, the event management module is also used to obtain the subscription event requirements of the preset application before the industrial information system interface adapter module determines the system attribute data and system events of the system data according to the preset event notification interface specification; create the event to be subscribed according to the subscription event requirements, and define the event type and event attributes of the event to be subscribed; if the event type is a system event type, determine at least one industrial information system as the event source of the event to be subscribed, and define the event notification interface sub-specification of each industrial information system, so as to generate corresponding system attribute data based on the system data reported by the event source through the event notification interface sub-specifications of all industrial information systems, and trigger the generation of system events; generate a preset event notification interface specification based on the event notification interface sub-specifications of all industrial information systems.
[0087] Among them, the event management module is also used to obtain the system interface sub-specification of each event source; by importing the Swagger Rest API, the event trigger interface specification is dynamically created to define the event notification interface sub-specification of each industrial information system.
[0088] In one embodiment, the event execution module is also used to obtain the subscription event requirements of the preset application before determining the target application and the input parameter rules of the target application based on the event to be notified and the preset application event subscription data, and the subscription event requirements are determined based on the business logic of the preset application; compare the subscription event requirements with the created event description of the created event; if there is a created event description that meets the subscription event requirements, trigger the preset application to subscribe to a created event corresponding to the created event description; obtain the input parameter rules corresponding to the business logic; generate the preset application event subscription data based on the created event, the preset application, and the input parameter rules, and the preset application event subscription data represents the subscription relationship between the event and the preset application, as well as the input parameter rules of the event subscribed by the preset application.
[0089] In one embodiment, the event execution module is also used to, if there are multiple target applications, determine the input parameter rules of each target application corresponding to the event to be notified based on the preset application event subscription data, so as to convert the event attribute data to be notified of the event to be notified into corresponding input attribute data to be notified according to the input parameter rules of each target application, and send the input attribute data to be notified to the corresponding target application.
[0090] The event management module can be used to manage events that low-code applications can subscribe to. For example, for device events that come from industrial IoT devices, the event attributes are mapped by reading the object model definition, and the event generation rules are configured. This allows the subsequent industrial equipment data adaptation module to determine whether to generate a device event based on the reported device data, and when a device event is generated, obtain the device attribute data of the device event. It can also provide which business logic of which preset application the event execution module should call after the device data is generated, and how to convert the device attribute data to meet the needs of the business logic.
[0091] After being configured by the event management module, the event execution module can be responsible for querying which application and which logic the current event to be notified corresponds to, and converting the attribute data of the event to be notified into the input attribute data to be notified, passing it to the application for execution, converting the attribute data obtained in the event notifier into the attribute data required by the application, and adapting the attribute data in the event notifier to the input parameters required by the application. Then trigger the application to execute the corresponding business logic.
[0092] After being configured by the event management module, the industrial equipment data adapter module is responsible for reading the MQTT data reported by the industrial IoT devices according to the specifications defined by the object model, and generating events and attribute data (equipment attribute data) according to the configuration rules, which can realize the conversion of coupled device data to event data. The industrial equipment data processing module processes industrial equipment events by reading the MQTT message queue provided by the industrial data acquisition gateway. The industrial equipment data module is connected to the industrial equipment object model library to realize the parsing, processing, judgment and event triggering of equipment data. The event execution module is used to query the event source and event subscription. The event notification module is used to notify the downstream low-code application business logic to perform business processing and complete the event notification of industrial equipment and low-code applications.
[0093] After being configured by the event management module, the industrial information system adapter module is responsible for receiving the interface call of the event source system according to the event notification interface specification, matching the corresponding event and parsing the event attributes. The event source drives the notification mechanism of business events by calling the industrial information system interface processing module, receives the parameters of the business event, and queries the event source and event subscription through the event execution module. The event notification module notifies the downstream low-code application business logic to perform business processing and complete the event notification of the industrial information system and the low-code application.
[0094] The preset application corresponding to the above event notifier may be one or more, and the events subscribed by the application may be added, modified or deleted through the event management module.
[0095] For the specific definition of the event notifier, please refer to the definition of the event notification method above, which will not be repeated here. Each module in the above event notifier can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the electronic device in hardware form, or can be stored in the memory of the electronic device in software form, so that the processor can call and execute the operations corresponding to the above modules.
[0096] In this embodiment, the event notifier is essentially provided with multiple modules for executing the event notification method in any of the above embodiments. The specific functions and technical effects can be referred to the above embodiments and will not be repeated here.
[0097] Combination Figure 7 As shown, Figure 7 is a schematic diagram of the structure of an event processing system in an embodiment of the present invention. Figure 7As shown, an embodiment of the present disclosure provides an event processing system, which includes an event notifier as provided in the above embodiments, one or more preset applications, one or more industrial devices, and one or more industrial information systems, wherein: the industrial equipment is used to report device data to the industrial equipment data adaptation module of the event notifier through the industrial data acquisition gateway; the industrial information system is used to send system data to the industrial information system interface adaptation module of the event notifier; when the preset application is the target application, the preset application is used to receive the input attribute data to be notified sent by the event execution module of the event notifier, and execute the input attribute data to be notified through the business logic corresponding to the event to be notified.
[0098] The target application is the preset application that has subscribed to the event in advance.
[0099] For the specific limitations of the event processing system, please refer to the limitations of the event notification method above, which will not be repeated here. Each module in the above event processing system can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the electronic device in hardware form, or can be stored in the memory of the electronic device in software form, so that the processor can call and execute the operations corresponding to the above modules.
[0100] In this embodiment, the event processing system is essentially provided with multiple modules for executing the event notification method in any of the above embodiments. The specific functions and technical effects can be referred to the above embodiments and will not be repeated here.
[0101] An embodiment of the present disclosure further provides an electronic device, including: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes a method provided in any of the above embodiments.
[0102] The embodiment of the present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the aforementioned method embodiment when executed by a processor.
[0103] Figure 8 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 8 The computer system 900 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0104] like Figure 8As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 902 or the program loaded from the storage part 908 to the random access memory (RAM) 903, such as executing the method in the above embodiment. In the RAM 903, various programs and data required for system operation are also stored. The CPU 901, ROM 902 and RAM 903 are connected to each other through a bus 904. An I / O (Input / Output) interface 905 is also connected to the bus 904.
[0105] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.
[0106] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 909, and / or installed from a removable medium 911. When the computer program is executed by a central processing unit (CPU) 901, various functions defined in the system of the present application are executed.
[0107] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, 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, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0108] The electronic device disclosed in this embodiment includes a processor, a memory, a transceiver and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication with each other. The memory is used to store computer programs, the communication interface is used to communicate, and the processor and the transceiver are used to run the computer program so that the electronic device executes each step of the above method.
[0109] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, 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, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0110] The above description and accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent possible changes only. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. Parts and subsamples of some embodiments may be included in or replace parts and subsamples of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of a stated sub-sample, whole, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other sub-samples, wholes, steps, operations, elements, components and / or groups of these. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.
[0111] Those skilled 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 in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. Technicians can clearly understand that for the convenience and simplicity of description, the specific working process of the systems, devices and units described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0112] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some sub-samples can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.
[0113] The flowchart and block diagram in the accompanying drawings show the possible architecture, functions and operations of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.
Claims
1. An event notification method, characterized in that: The event notification method includes: Obtain device data reported by industrial IoT devices, and determine device attribute data and device events of the device data according to preset device data parsing specifications; Acquire system data sent by the industrial information system, and determine system attribute data and system events of the system data according to a preset event notification interface specification; determining a target application and an input parameter rule of the target application based on the event to be notified and preset application event subscription data, and converting event attribute data of the event to be notified into input attribute data to be notified based on the input parameter rule, wherein the event to be notified includes the device event and / or the system event, and the event attribute data to be notified includes the device attribute data and / or the system attribute data; The input attribute data to be notified is sent to the target application, triggering the target application to execute the business logic corresponding to the event to be notified based on the input attribute data to be notified, so as to complete the event notification to the target application.
2. The event notification method according to claim 1, wherein: Before determining the device attribute data and device events of the device data according to a preset device data parsing specification, the method includes: Get the subscription event requirements of the preset application; Create an event to be subscribed according to the subscription event requirements, and define the event type and event attributes of the event to be subscribed; If the event type is a device event type, determine at least one industrial IoT device as the event source of the event to be subscribed, and define a device data parsing sub-specification for each industrial IoT device, so as to generate corresponding device attribute data based on the device data reported by the event source through the device data parsing sub-specifications of all industrial IoT devices, and trigger the generation of a device event; Generates preset device data parsing specifications based on the device data parsing sub-specifications of all industrial IoT devices.
3. The event notification method according to claim 2, wherein: Define the device data parsing sub-specification for each industrial IoT device to trigger the generation of device events based on the device data reported by the event source through the device data parsing sub-specifications of all industrial IoT devices, including: Obtain industrial equipment object models; Determine a device data parsing sub-specification for each industrial IoT device based on the industrial device object model, wherein the device data parsing sub-specification includes at least a point data trigger condition and a point data format; Performing point data format recognition on the device data reported by the event source to obtain point format data; If the point format data meets the point data trigger condition, the device event is triggered to be generated.
4. The event notification method according to claim 2, wherein: After generating a preset device data parsing specification based on the device data parsing sub-specifications of all industrial IoT devices, the method further includes: Trigger the release and execution of the preset application.
5. The event notification method according to claim 1, wherein: Before determining the system attribute data and system events of the system data according to a preset event notification interface specification, the method includes: Get the subscription event requirements of the preset application; Create an event to be subscribed according to the subscription event requirements, and define the event type and event attributes of the event to be subscribed; If the event type is a system event type, at least one industrial information system is determined as the event source of the event to be subscribed, and an event notification interface sub-specification is defined for each industrial information system, so as to generate corresponding system attribute data based on the system data reported by the event source through the event notification interface sub-specifications of all industrial information systems, and trigger the generation of a system event; Generate a preset event notification interface specification based on the event notification interface sub-specifications of all industrial information systems.
6. The event notification method according to claim 5, wherein: Defines the event notification interface sub-specifications for each industrial information system, including: Dynamically create event trigger interface specifications by importing Swagger Rest API to define the event notification interface sub-specifications of each industrial information system.
7. The event notification method according to any one of claims 1 to 6, characterized in that: Before determining the target application and the input parameter rules of the target application according to the event to be notified and the preset application event subscription data, the method includes: Obtaining a subscription event requirement of a preset application, where the subscription event requirement is determined based on the business logic of the preset application; Comparing the subscription event requirement with the created event description of the created event; If there is a created event description that meets the subscription event requirement, trigger the preset application to subscribe to the created event corresponding to the created event description; Obtain input parameter rules corresponding to the business logic; The preset application event subscription data is generated based on the created event, the preset application, and the input parameter rules. The preset application event subscription data represents the subscription relationship between the event and the preset application, as well as the input parameter rules of the event subscribed by the preset application.
8. The event notification method according to any one of claims 1 to 6, characterized in that: Determining a target application and input parameter rules for the target application based on the event to be notified and the preset application event subscription data includes: If there are multiple target applications; According to the preset application event subscription data, the input parameter rules of each target application corresponding to the event to be notified are determined, so as to convert the event attribute data to be notified of the event to be notified into corresponding input attribute data to be notified according to the input parameter rules of each target application, and send the input attribute data to be notified to the corresponding target application.
9. An event notifier, characterized in that: The event notifier includes: The industrial device data adaptation module is used to obtain the device data reported by the industrial IoT device and determine the device attribute data and device events of the device data according to the preset device data parsing specification; An industrial information system interface adapter module is used to obtain system data sent by the industrial information system and determine system attribute data and system events of the system data according to a preset event notification interface specification; An event execution module is used to determine the target application and the input parameter rules of the target application based on the event to be notified and the preset application event subscription data, convert the event attribute data to be notified of the event to be notified into input attribute data to be notified according to the input parameter rules, the event to be notified includes the device event and / or the system event, the event attribute data to be notified includes the device attribute data and / or the system attribute data, and is used to send the input attribute data to be notified to the target application, triggering the target application to execute the business logic corresponding to the event to be notified based on the input attribute data to be notified, so as to complete the event notification to the target application.
10. An event processing system, characterized in that: The event processing system comprises the event notifier according to claim 9, one or more preset applications, one or more industrial devices, and one or more industrial information systems, wherein: The industrial equipment is used to report equipment data to the industrial equipment data adaptation module of the event notifier through the industrial data acquisition gateway; The industrial information system is used to send system data to the industrial information system interface adapter module of the event notifier; When the preset application is the target application, the preset application is used to receive the input attribute data to be notified sent by the event execution module of the event notifier, and execute the input attribute data to be notified through the business logic corresponding to the event to be notified.
Citation Information
Cited By
Telemetering general analysis real-time compiling method and system and computer readable storage medium
CN120743285A
