1. Introduction
With the interpenetration of information technology and manufacturing, the integration of manufacturing physical systems and information systems has been increasingly enhanced [
1]. The IoMT technology with embedded systems, RFID, and wireless sensor networks at its core, has come into shape as a ubiquitously-perceptual, heterogeneously-integrated, self-adaptive, interoperable, and intelligent manufacturing and information service model. The application of Internet of Things (IoT) technology in the manufacturing industry provides the technical basis for interconnection, real-time position tracking, intelligent control, and so on in the manufacturing process [
2]. It also promotes the fusion of manufacturing physical systems and information systems, and can achieve dynamic perception and optimized processing of resources and information production. IoT has been utilized in decision-making in manufacturing to contribute to knowledge-based intelligent manufacturing [
3,
4].
With the development of more intelligent manufacturing processes, an increasing number of studies have been conducted to explore techniques for manufacturing information perception. Since 2003, the emergence of RFID and other IoT technologies have brought an intelligent revolution in manufacturing [
5], which has helped to achieve automated data collection [
6], assurance of data dependencies, improvements in production and inventory visibility [
7], etc. Kenneth et al. [
8] proposed a Radio Frequency Identification (RFID) -based risk management system (RRMS) with rule-based reasoning and RFID integration technology to more effectively monitor real-time operations on site. Barenji et al. [
9] proposed a multi-agent RFID-enabled distributed control and monitoring system for a flexible manufacturing shop to enhance the agility, flexibility, and reconfigurability of its manufacturing system. Brintup [
6] proposed to use RFID technology to achieve leaner manufacturing through automated data collection and improvements in better monitoring of production and inventory. Liukkonen [
10] showed that most application targets of RFID are related to warehouse management, process management, tool management, supply chain management, and life cycle management. Wireless sensor networks [
11] have been used for the perception of mobile units to achieve anticipatory control for a flexible manufacturing system. Zhang et al. [
12] developed a real-time information capturing and integration framework of the Internet of Manufacturing Things based on Internet of Things (IoT) technology. Tao et al. [
13] proposed a framework to use IoT for achieving intelligent perception and access of various resource in cloud manufacturing. Jeschke et al. [
14] and Tao et al. [
15] introduced frameworks for industrial IoTs and cyber-manufacturing systems.
It is widely recognized that comprehensive perception and intelligent processing of multi-source manufacturing information are critical to decision support for intelligent controls in production processes [
16]. The decreasing cost of sensors and the need for intelligent manufacturing has led to the adoption of diverse types of sensors in modern factories for quality control, fault diagnosis, etc. However, this has caused significant challenges in big data processing of such enormous amounts of heterogeneous information from such sensors: how to detect different types of events; how to match events to appropriate decision-making rules; and how to handle the real-time requirement of complex events processing.
Among the datasets produced in the process of interconnected manufacturing, the manufacturing events that guide decision support include primitive events and critical events [
17]. Primitive events occur when the perception components of equipment collect raw data. Critical events are complex decision-making events that are generated by association rules from primitive events or complex events [
18]. The manufacturing events of a manufacturing process can be complicated due to the distributed deployment structure of the manufacturing system. A complex event processing engine takes the massive heterogeneous data as the observation and extraction objects, obtains meaningful event information from regular operations, and makes up the complex events so that meaningful events can be extracted and summarized in real-time [
19]. These concurrent event processes have been discussed by Tanase et al. [
20].
The main focus of this paper is how to deal with the complex relationships among multi-level manufacturing events to achieve fast and intelligent complex event processing. Several pioneering studies have been done in this area. Vaidehi et al. [
21] designed an ECA language for wireless sensor networks to generate data and events. A single ECA was used to describe simple events and ECA combinations were used to represent complex events. Gerald et al. [
22] developed the Cordis event processing model by adopting complex event processing in the event-related research of distributed systems. They also suggested an algebra to describe the association between event information and an algorithm to detect the independent event information in the association description. Romdhane et al. [
23] presented a unified processing framework for uncertain information based on probability theory in the process of complex event recognition and created a new composite event model description language to overcome the “complex temporal constraints”. Wang et al. [
24,
25] developed a distributed complex event processing architecture based on the Common Object Request Broker architecture. They also designed an algorithm of plan-based distributed CEP (PDCEP) and a high-performance distributed complex event processing method based on probability, extending the basic finite automata to support the probability of event flow processing models. Yao et al. [
26] defined RFID event modeling and complex event operators and presented an architecture for complex event processing for real-time processing of RFID events and the integrity of logical semantic description. Hu et al. [
16] showed that event construction, state prediction, and disturbance detection suitable for big-data environments of modern complex manufacturing systems are critical for RFID-enabled intelligent manufacturing. It is also noted that the greatest challenge is to design efficient and intelligent schemes for manufacturing event processing. Allen et al. [
27] proposed an anomaly detection approach for event-based systems that consist of processes that interact through shared resources. A resource-based Petri net formalism is introduced to model these types of systems. Their model generation uses an algorithm based on workflow mining to generate resource-based models. Dias [
28] studied how to use timed event graphs to simulate synchronizing operations on productive systems. Complex event processing in IoMTs can also exploit the emerging big data technologies and platforms, such as Apache Spark [
29], real-time stream processing platforms [
30,
31], etc., [
32,
33,
34].
The complex events in IoT-based manufacturing processes can be regarded as flows of information from multiple sources, for which Cugola and Margara [
35] conducted a comprehensive review considering issues from data streams to complex event processing. Fang et al. [
36] introduced an information processing mechanism based on a critical event model to organize real-time field data in various abstract levels for enterprise decisions. Their case study at an air conditioner manufacturing company showed its effectiveness. Fault diagnosis of discrete event systems has also been analyzed by Zaytoon et al. [
37]. Event-based models have also been used for modeling distributed sensor networks in battery manufacturing [
38]. Due to the ubiquity of RFID-based manufacturing plants, new computing methods are needed for rapid processing of the big event data from hundreds or thousands of sensors. Dagkaris et al. [
39] proposed and shared ManPy, an open-source software tool for building discrete event simulation models of manufacturing systems. Nie et al. [
40] adopted an event handling engine (PUCEP) to improve uncertain complex event matching efficiency by combining the data stream processing engine (SASE) with data generation management and the probability flow theory. The purpose is to link the Internet of Things to data collection and improve the accuracy and reliability of complex events matching. Li et al. [
41] suggested a spatiotemporal event model for the complex event processing of farmland IOT, and used the complex event relation operator to judge the spatial-temporal relationship between sub-event and complex event. They also designed and implemented a real-time complex event processing engine, to determine complex events through real-time matching of atomic events and complex event patterns. However, current complex event processing for manufacturing processes lacks a standard model and mechanisms for semantic expression of complex association relations among events. It becomes an urgent need to improve complex event matching processing with strong association rules.
To achieve active sensing and processing of key events in manufacturing processes, this paper proposes an active sensing and processing architecture (ASPIE) for processing manufacturing process events. First, an active sensing method is developed for obtaining key events in manufacturing processes. To address the issue of event expression and processing, an XML-based extensible and easy-to-parse event description language with related event operators is designed to realize the unified description of complex semantic relations. We also proposed a sophisticated event matching scheme to conduct complex event processing based on correlation templates. To evaluate our active sensing and processing architecture and methods, we implemented an ASPIE module embedded in the manufacturing resources management system at a large factory famous for chili sauce production, aiming to support intelligent decisions and optimization of their manufacturing system. The framework and methods for handling the perception and processing of key events in manufacturing processes may provide theoretical and practical guidance for developing enterprise production management decision-making systems.
The remaining paper is organized as follows: In
Section 2, an architecture for active sensing and processing of key events in IoMT is introduced. In
Section 3, we proposed the methodology for active sensing of key events in manufacturing processes including system design, data processing and packaging, complex events association mining and matching, and transmission and access of the data obtained via active sensing.
Section 4 describes how to describe and process the manufacturing events in a standardized way using an improved XML language and template matching. In
Section 5, we described our implementation and evaluation of the proposed architecture, models and methods for active sensing and processing of key events at a chili oil sauce manufacturing company. In
Section 6, the concluding remarks are presented, and the contributions of this paper and directions for future research are discussed.
3. Active Sensing Method for Key Events of Manufacturing Processes Based on IoMT
In order to realize active sensing and standard output of the shop manufacturing process, the multi-hop heterogeneous sensor network can be adopted in the manufacturing workshop to manage the heterogeneous sensors and to collect the dynamic data. In data processing, firstly, the sensor information is defined according to the sensor type and data description template, and the heterogeneous data is normalized by the ISA95 standard encapsulation data [
44]. Secondly, based on the event business logic and rule based algorithms, key events are obtained by matching the perceptual data based on the XML templates. Finally, the perceived key events are transmitted through Web service technology.
The implementation steps of active sensing of manufacturing process events based on the IoT technology are as follows:
- (1)
The design of the perception system;
- (2)
Data processing and standardized packaging;
- (3)
Complex event correlation matching; and
- (4)
Transmission and access of perception results.
The process of active sensing and processing manufacturing complex events is shown in
Figure 4. The details of the processes are explained as below in subsections.
3.1. Perception System Design
Due to the sensor heterogeneity, an embedded manufacturing information sensing device is designed to conduct multi-source heterogeneous data acquisition, network I/O control, rule based algorithm processing, and data storage and transmission. It also realizes heterogeneous sensor concentration management and heterogeneous information-aware processing. In the perception system, real-time manufacturing information can be acquired with the underlying components of the sensing node module. The intermediate component integrates the data collected by the bottom node, real-time transmission, and decision briefing, and generates events through the logical operation of data information. A unified user interface facilitates the development of the system and the efficient transfer of information. A unified description of the sensor information achieves the standardization of information processing and expression. For the sake of generality, real-time sensing data per sensor is encapsulated as a standard Web service so that real-time data can be transmitted over the network.
Perception system integration of functional modules mainly includes plug-and-play of heterogeneous sensors, condition monitoring equipment, multi-source heterogeneous information processing and standardization, multi-level event matching operations and packaging, and event push and access.
3.2. Processing and Standardized Package of Perception Data
According to the data structure of storage, the real-time manufacturing information is divided into dynamic data and static data. Dynamic data is stored as XML documents, of which the data structure is semi-structured and unstructured. Static data (basic data) is the property data of manufacturing resources, also referred to as the basic information of the object, which is stored in a relational database. In order to achieve the unified expression and efficient call of heterogeneous data, the relational data and XML data can be exchanged, and the perception data is encapsulated and stored as XML documents.
3.3. Correlation Matching of Complex Events
First of all, we need to integrate the manufacturing information that’s processed and packaged in a standard package (including multi-source manufacturing information related to definition of association, template matching of multi-level events, regular operation, and increment processing of events). The event association matching process consists of three steps: (1) to establish an event association model using XML language to describe the association of multi-source manufacturing information, and to establish an XML file describing the event structure; (2) to mine association rules of events based on association data mining algorithms and to establish the correlation matching templates of complex events; and (3) to improve the performance of the algorithm in the event stream processing engine and perform the calculation of the complicated events in the production process based on template matching.
3.4. The Transmission and Access of Perception Results
Perceived complex events are mainly based on Web service technology for active push and remote access, as shown in
Figure 5 and
Figure 6.
4. Standardized Descriptions and Processing Of Manufacturing Process Events
With the improved XML language, the standardized processing of manufacturing events is achieved in order to realize the unified semantic expression of the complex relations of multi-level events in the manufacturing process. At the same time, we developed a complicated event association matching scheme to process complex events based on templates.
4.1. Correlation Model of Manufacturing Association Events
In general, the relationship between the manufacturing process events are: (1) temporal relationships or time-sequence relationships, which can be described using time models; (2) logical hierarchies, which can be described using hierarchical models; and (3) causal relationships, described using semantic operators for expression. Assuming CE represents a key event or complex event. PE represents an original event. The expression for the key event can be written as: CE = f(PE1, PE2, ···, CE1, CE2, ···). The logical operator f defines the logical relationship between events and can be nested in multiple layers.
Based on the production process event type and correlation analysis, a complex event structure model oriented to the production process is established (see
Figure 7). Relational operators are used to describe the relationship between the multi-level events, such as timing and logic hierarchy, to reveal the information of sub-events and their implications in multi-level complex events, and to explain the selection and matching of sub-event instances of complex events. The temporal and semantic relations between multi-level events can also be identified.
There exists an association of similar event type aggregations between event CE1 and event CEn. For event PE, the CE1n upper level event is CE1, and there is a generalized relationship between event CE1, events CE1n and PE. The aggregation process for the critical event CE11 [
45] is: (1) if the original event PEn occurs, the event value is TRUE; (2) if the original event PEm does not occur, the event value is FALSE, and the non-operator aggregation event value becomes TRUE; (3) after the two original events are processed, the event value becomes TRUE by the sequence operator; and (4) after the time constraint operator is aggregated, the event value becomes TRUE, i.e., the event CE11 occurred.
4.2. Description of XEDL-based Manufacturing Events
- (1)
Basic Syntax Structure
Our basic syntax definition of XML-based event description language (XEDL) includes three aspects: (1) XEDL text should conform to the XML specification, the starting line should be: <?xml version = “1.0” encoding = “utf-8”?>; (2) With XEDL as root: <XEDL>…/XEDL>; (3) Under the root, there are three parts: event structure, event strategy and event attributes.
The XEDL syntax consists of a collection of raw event registries and key event sachems. The syntax is described as follows:
<XEDL> |
<PEset>//Primitive event registry |
<PE>…</PE>//Primitive event description |
</PEset> |
<CEset>//A collection of key event patterns |
<CE>…</CE>//Key event patterns |
</CEset> |
</XEDL> |
- (2)
Description Syntax of Original Events
The primitive event triggered by the sensor node is represented by a unique identifier ID and it represents a change in the same class or similar state. The original event body contains the source sensing device, the time, the location of occurrence, and other attributes.
Description syntax of the primitive event is as follows:
<PE> |
<ID>primitive event_i</ID>//The original event i uniquely identifies the ID |
<sources>//The original event occurs from the source sensor node |
<source>sensor_n</source>//Sensing source n |
</sources> |
<other_attributes>//Other attribute definitions |
<attribute>otherattr_m</attribute>//The attribute m |
</other_attributes> |
</PE> |
- (3)
Description Syntax of Key Events
A key event is described as a complex event pattern, which includes three aspects: the cause event set, the instance strategy, and the logic operation function. The key event expression consists of the event operator and the operand, denoted as CE expression (operator, operand). The operands represent the event type, and the operators combine the event types. The definition of event operator [
46,
47] consists of three parts: (1) the number of instances of the operands; (2) the usage strategy and consumption strategy of the event instance; (3) the usage strategy of event instances consists of four operators: primitive, recent, continuous, and cumulative; and the consumption strategy of the event instance consists of four operators: reserve, remove-early, remove-current, remove-all. Qualified events are reserved following the usage strategy or consumption strategy of the operand processing or after deleting the ineligible instances when the number of event instances of the operand is exceeded. The usage strategy of an event instance specifies how an event instance can be used for event aggregation. The consumption policy of the event instance determines whether the complex event is saved or deleted after it is involved in complex event calculations.
Combined with the complex event operators and XML syntax, the key event XEDL syntax is defined as follows:
<CE> |
<ID>complex_event_n</ID>// The unique ID of the key event n |
<attributes>•••</attributes>// Definition of event attributes |
<eventset>// An set of cause event instances |
<event>•••</event>// Acause event instance and strategies |
</eventset> |
<logicfunction=”judgefunction|constructorfunction”>// The logical operation function of the event |
<judgefunction>conjunction|disjunction</judgefunction>//Judgmentfunction |
<constructorfunction>•••</constructorfunction>// calculation function of attributes |
</logicfunction> |
</CE> |
- (1)
The Policy Description of the Causal Event Instance
The use of the event instance, the consumption policy, and the cause event are described in XEDL syntax as follows:
<event> |
<use>// Use policy definitions |
primitive|recent|continuous|cumulative// Use the policy options |
</use> |
<consume>// Definition of consumption policy←← |
reserve|removecurren|removeearly|removeall// Consumption policy options |
</consume> |
</event> |
|
- (2)
Syntax Description of the Logic Operation Function
<logicfunction>// Event logic operation function |
<judgefunction>// Judgment function |
<attributes>position|source|time|other</attributes>// The type of the event attribute |
••• |
</judgefunction> |
<constructorfunction>// The calculation function for the attribute |
<attributes>•••</attributes>// The event property name is evaluated |
<variables>•••</variables>// The calculation of the variables |
••• |
</constructorfunction> |
</logicfunction> |
4.3. Manufacturing Process Event Processing Based on Complex Event Processing (CEP) and Associated Templates
The manufacturing process event is processed by matching relation scheme based on template sequences. Firstly, the Apriori algorithm is used to mine the event data set and generate the matching template, which is stored in the memory database in XML format. Then, the template-based complex event processing operation is performed, and the key events of the manufacturing process are obtained [
17].
- (1)
Manufacturing Process Event Matching Association Scheme
The Apriori algorithm is used to mine association rules and generates matching templates. The algorithm rules are: (1) if there is a causal relationship between active-perceived events and sub-events, the confidence level of the association rules is 1; (2) there are one-to-one, many-to-one association rules between perceived complex events and the causal events. There is no need to consider one-to-many or many-to-many cases; and (3) for the one-to-one association rules of events, there is a sufficient non-essential conditional relation between the source event and the target event.
The algorithm of matching template [
48] is generated as follows:
1: begin |
2: U ← (History-aware event patterns from the database); |
3: for all EiU do |
4: Di.id = newid;//Complex Event Matching Pattern Detection |
5: for all DiU do |
6: if (Di = Φ) |
7: Delete (Di); |
8: if (Di - 1! = Φ) |
9: Di-2 = Di-2Di-1;//The last level of event handling |
10: Al ← {iDi, and i satisfies the term of the support degree S }; //A 1-level association rules with minimum support |
11: for k = [2,3,…] do |
12: Tk = Ak -1 × Al; //Multilayer transaction matching |
13: Ak {iTk and i satisfies the term of the support degree S}; //A k-level association rule with minimum support |
14: if(Ak = Φ) |
15: break; |
16: E ← (The event group in Ak (k! = 1) conf(e) = 1); |
17: Association template ← {the event group eE, conf(e) = 1}; |
18: end |
- (2)
Template-Based Matching of Production Process Events
To achieve the complex processing and analysis of multiple atomic events in real-time, we chose template matching as the complex event processing data stream processing scheme. The template is stored in the knowledge base of “in-memory database”, and the production process events are handled by template matching and complex event processing. The main flow is shown in
Figure 8.
In complex event processing, the NFA is used to describe the push decision of an atomic event. Depending on the business needs, the application of nondeterministic finite automata in complex event processing is extended and innovated as follows:
- (1)
When the life cycle of the automatic validation machine is overdue, the automatic machine that does not complete dies, and the event request was cancelled.
- (2)
During the concurrent event processing, the automaton calculates and matches the matching system separately, and provides the suspending function for event handling.
- (3)
For those automaton that “from suspend to die”, atomic events will be deposited into a temporary library for subsequent repair.
The complex event processing algorithm of the finite machine is described as follows:
1: e = GetEvent (); // Get the atomic event |
2: if (Timeup (e)) do |
3: Cep Start With (e); // If the time of event e exceeds the verification period, a new periodic process is detected |
4: if Request wait (e) do |
5: Send (e); // If there is a request for an e event, an e event is sent |
6: result = result Cep (e); // for complex event processing |
7: if Cep List push (e) do |
8: goto step 1; //determine the completion of the event is not processed and re-verified |
9: if result = Cep End do |
10: SendtotempDB (e); //complex event aborted, the event e stored in the memory database |
11: if result = CepSuccess |
12: Outputresult (resultCep (e)); //complex event processing operations to terminate and output critical events |
13: goto step 1; |
- (3)
Key Processes for Manufacturing Processes Based on Matching Templates
- (1)
Heuristic Real-Time CEP of the Directed Graph
To realize real-time active sensing of complex events by the CEP engine, we have developed a set of algorithms based on association templates to improve the speed of event detection and correlation matching. One of the major contributions of this paper is to develop methods to achieve real-time processing of multi-level event instances by performing complicated event pattern matching according to the set task priorities, thus reducing the processing time and facilitating real-time active sensing of key events.
Due to the relatively fixed mechanism of automata and Petri nets in the CEP intermediate structure, it is difficult to adjust the priority of tasks. We, thus, proposed a complex event structure model according to event expression and the type of the manufacturing process. A directed graphic [
49] is chosen to show the mapping model of complex event processing. Specifically, complex event patterns in the library are mapped to a directed graph and stored in the memory database, where there are directed graph nodes, intermediate nodes, and root nodes, which correspond to atomic events, intermediate modes, and complex event modes. Identical nodes are merged, as shown in
Figure 9. There exist necessary relationships between event PE (process event) and CE (complex event).
The mid-point node performs complex event correlation matching according to the CEP patterns and transmits the result to the parent node when the atomic event is generated by the complex event processing procedure of the directed graph. When the corresponding parent node detects the input of the sub-node event, the CEP matching pattern in the corresponding node is searched and the association process is performed. If the match is successful, the intermediate node outputs the processed complex event to the parent node for subsequent association, and the root node outputs the final event-aware event. Otherwise, the corresponding event is stored or discarded depending on the semantic judgment.
- (2)
Event Matching Based on the Heuristic CEP Algorithm
The essence of our heuristic is to find the shortest path function that defines the path from the sub-node to the parent node in a complex event pattern tree, which is used to search and evaluate the optimal complex event processing scheme. The heuristic function considers two factors: (I) when some or all of the sub-events of the node occur, the pattern matching is carried out; (II) the shorter the path between event processing nodes, the fewer the event composition layers, and the easier it is for complex event pattern matching. Heuristic functions are defined as follows:
where
is the heuristic function of node
n.
denotes all sets of paths from the node n to each exit node, representing that node
is a node on the path
r from node
n to a particular exit node.
is a waiting function of node
n, used to ensure the efficiency of synchronous threads and programs. The value of
is determined according to the value range of
,
,
P, and
.
Prepresents the number of sub-events that have occurred for the complex event pattern.
represents the minimum number of sub-events required to trigger the pattern matching.
Our heuristic based complex event pattern matching algorithm is shown as follows:
1: Imports: subevent flow = [e1, e2, e3, ...] // input atomic event stream |
2: Exports: complex event flow / / output according to complex event pattern matching the key event flow |
3: Function Heuristic Search (Instance II ext) |
4: For each subevent flow e { |
5: hb set to null //initialization engine, the node queue hb is empty |
6: n← e // Case e The corresponding node |
7: For the parent node f of n{ |
8: append e into the end of the cache queue at f |
9: Put f into hb}} |
10: While hb is not null { |
11: n←The smallest node existed in hb |
12: ce← the first event instance in the Buffer queue at node n |
/ / event instance with priority to handle |
13: ins ←new event instance or null generated by the ce pattern matching at node n |
14: remove ce from the the cache queue n |
15: Recalculate H(n) and all its children node H(ni) |
16: If ins <> null { |
17: If n is an exit node { |
18: append ins at the end of output queue of complex events |
19: Else |
20: For the parent node f of n{ |
21: append ins at the end of the buffer queue of |
22: save f into hb}}}} |
23: If the instance cache queue of n is null { |
24: remove n from hb}} |
25: End function |
- (3)
Real-time CEP Framework and its Working Mode
Our real-time CEP engine was developed under the Eclipse environment using the Java language. The overall framework is shown in
Figure 10. Atomic events are formed after the sensed data is cleaned and encapsulated. The atomic events are extracted by atomic event extractor and the atomic events stream is generated. At the same time, atomic events are standardized and encapsulated, and entered into the real-time CEP engine in XML format. The CEP engine receives the atomic event stream and simultaneously detects the complex event pattern and completes the event correlation matching. The complex event stream is exported at last. The domain expert can add or delete the matching template generated by association rules mining online.
The working principles of the real-time CEP engine associates atomic events with complex event patterns generated by association rules and outputs complex events. The CEP engine first buffers and distributes the atomic events. Then, the fast heuristic CEP algorithm based on the directed graph is implemented by the detection/execution module, and the complex events resulting from the correlation matching are placed in the complex event cache in XML format. Finally, complex events are exported to the information application system to provide decision support for the manufacturing process. The real-time CEP service evaluates the latest response time of the complex event pattern during the detection process and ensures the real-time performance of the event sensing. The real-time CEP engine communicates via two types of interfaces: (I) XML documents are transmitted through the XML Socket; and (II) data are transmitted through Java RMI that invokes the event processing methods in the engine remotely.
In order to deal with complex event pattern processing in the CEP engine, domain experts generate event-matching templates through complex event association rule mining and improving related algorithms, and transform them into XML-based complex event correlation matching description templates, which are saved in the knowledge base. The complex event correlation matching template is mapped by a parser into a complex event pattern, which is identified by a pattern-matching structure based on a directed graph to facilitate the transmission of complex event processing.
According to the framework of the real-time CEP engine, the real-time CEP engine operating mode f is defined as follows: (I). The atomic event stream is entered into the atomic event cache of the CEP engine via the XML Socket interface. (II) According to the event type and the control of the event processing, the atomic event dispatcher is used to load the atomic event into the corresponding node processing unit and cache the queue according to the heuristic function value. The heuristic function calculator is used to recalculate the heuristic function of the node when the node instance cache changes, and, thus, rearrange the node queue. (III) The priority node is extracted in the queue through the detection/execution module and the corresponding node in the node is deleted. Meanwhile, the node processing unit script is calculated. (IV) The heuristic function calculator together with the detection/execution module process the event instances until there are no event in the pending node queue. A, and the priority event in the atomic event cache continues to load the node processing queue through the atomic event dispatcher. (V) Complex events generated by the detection module and the CEP node are appended to the complex event cache and will be exported through the XML Socket interface