WO2011131079A1

WO2011131079A1 - Event processing method and system for distributed control system

Info

Publication number: WO2011131079A1
Application number: PCT/CN2011/072337
Authority: WO
Inventors: 王常力; 施波; 宋晓玉; 马建新; 罗斌
Original assignee: 杭州和利时自动化有限公司
Priority date: 2010-04-20
Filing date: 2011-03-31
Publication date: 2011-10-27
Also published as: CN101799684A

Abstract

An event processing method and system for a distributed control system (DCS) are provided. The method involves: distributed control system(DCS) server receives variable data transmitted by a control station, said DCS server judges whether the variable data generates new events, if yes, said DCS server performs corresponding process for the event according to a predetermined event processing rule. By using the invention, the event processing efficiency of DCS can be increased.

Description

Event processing method and system for distributed control system

This application claims priority to Chinese Patent Application No. 201010153089.7, entitled "Event Processing Method and System for Distributed Control System", filed on April 20, 2010, the entire contents of which are hereby incorporated by reference. Combined in this application. TECHNICAL FIELD The present invention relates to the field of industrial automation control technologies, and more particularly to an event processing method and system for a distributed control system.

Background technique

At present, DCS (Distributed Control System) has been widely used in nuclear power, thermal power, chemical industry, etc. In these fields, real-time and accurate on-the-spot "3⁄4 police incidents can promptly notify staff to rush to the scene to deal with problems. Eliminate hidden dangers and avoid accidents. At the same time, detailed and standardized recording of various events can help the operator to clearly and clearly monitor the operation of the system and quickly resolve various events. The high-efficiency, stable and well-functioning event processing technology is the central link of real-time processing of data and events in the DCS system. The technical indicators and operational effects that can be achieved play an important role in the safety of the industrial control site.

The event processing technology mainly determines the type of event generated based on the field acquisition data, algorithm operation results and engineering data uploaded by the control station, such as: alarm or displacement of the switch quantity, limit alarm of the analog quantity, field module and channel The instrument is faulty. At the same time, functions such as storage of events, queried and alarms are also provided.

At present, most DCS systems at home and abroad have event processing procedures, but their implementation mechanisms and technical indicators are different. The implementation scheme similar to the present invention is shown in FIG. 1. During the generation and processing of the event, the DCS control station program generates corresponding events according to the collected field data and engineering data, and then the event number and the variable. The data is sent to the real-time DCS server. After receiving the event number, the real-time DCS server calls the event handler to generate and log the event, while responding to the operator station's access and operation of the event.

The control station shall upload the collected field data, algorithm operation result and event number to the DCS real-time processing task. Although the processing speed of the control station is high, it is undoubtedly judged at the control station. Reduced the processing efficiency. At the same time, the upload of the event number increases the network data packet, which inevitably increases the network load and improves the communication error rate. In addition, after receiving the uploaded data, the real-time processing task needs to process the variable data and update it to the database on the one hand, and process and store the event on the other hand. At the same time, real-time processing tasks also respond to operator requests for real-time data and events. This design pattern that combines data management and event processing seriously affects the performance of the system and cannot meet the performance requirements of the DCS system for real-time processing, stable operation, and efficient throughput.

Summary of the invention

In view of this, the embodiments of the present invention provide an event processing method and system for a distributed control system, so as to improve the efficiency of the distributed control system for event processing.

An embodiment of the present invention provides an event processing method for a distributed control system, where the method includes: a distributed control system DCS server receives variable data uploaded by a control station;

The DCS server determines whether the variable data generates a new event, and if so, the DCS server processes the event according to the preset event processing rule.

Preferably, after the DCS server performs corresponding processing on the event, the method further includes:

The DCS server stores real-time data generated when the event is processed.

Preferably, the DCS server determines whether the variable data generates a new event, and the method includes: comparing, by the DCS server, whether a current item value corresponding to the variable data is the same as a stored item value, and if not, determining to generate a new one. event.

Preferably, the DCS server processes the event according to a preset event processing rule, including:

The DCS server obtains identification information corresponding to the current event;

The DCS server obtains, according to the identifier information, a processing rule corresponding to the identifier information in a preset event processing rule;

The DCS server performs corresponding processing on the current data according to the processing rule.

Preferably, the preset event processing rule is set in a configuration file manner.

Preferably, the method further includes:

The DCS server detects whether there is a duplicate write in the stored real-time data for the same event The entered data, if yes, deletes the repeated written history data.

An event processing system for a distributed control system, the system comprising a DCS server and a control station, the control station for uploading variable data to the DCS server, the DCS server comprising: a receiving module, configured to receive a control station Uploaded variable data;

a determining module, configured to determine whether the variable data generates a new event;

The event processing module is configured to: if it is determined that a new event is generated, process the event according to the preset event processing rule.

Preferably, the DCS server further includes:

The real-time data storage module is configured to store real-time data generated when the event is processed after the event is processed correspondingly.

Preferably, the determining module further includes:

a current item value obtaining submodule, configured to acquire a current item value corresponding to the variable data;

The comparison submodule is configured to determine whether a new event is generated by comparing whether the current item value is the same as the stored item value, and if not.

Preferably, the event processing module further includes:

An identifier information obtaining submodule, configured to obtain identifier information corresponding to the current event;

a rule obtaining sub-module, configured to obtain, according to the identifier information, a processing rule corresponding to the identifier information in a preset event processing rule;

The processing sub-module is configured to perform corresponding processing on the current data according to the processing rule. Preferably, the system further includes:

a verification module, configured to detect whether there is repeatedly written data in the stored data for the same event;

And deleting a module, configured to delete the repeatedly written data when it is determined that there is data of repeated writing.

Compared with the prior art, the technical solution provided by the present invention can reduce the network data packet uploaded by the control station and improve the network transmission by migrating the process of determining the event from the traditional control station to the upper DCS server in the DCS. In addition, the DCS server rationally divides the real-time variable data management and event processing functions, which can reduce the coupling between modules and improve system performance. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are merely Some embodiments of the present invention may also be used to obtain other drawings based on these drawings without departing from the prior art.

1 is a schematic diagram of a DCS system event processing process provided in the prior art; FIG. 2 is a schematic flowchart of a DCS event processing method according to an embodiment of the present invention; FIG. 3 is a schematic diagram of an embodiment of the present invention. Schematic diagram of the overall process of event generation and event processing;

4 is a schematic structural diagram of a DCS system event processing system according to an embodiment of the present invention; FIG. 5 is a schematic structural diagram of another DCS system event processing system according to an embodiment of the present invention; A schematic diagram of the structure of a DCS system event processing system.

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without the creative work are all within the scope of the present invention.

In the event processing implementation process described in the prior art, the control station uploads the collected field data, the algorithm operation result and the event number to the DCS real-time processing task. Although the processing speed of the control station is very high, the event judgment on the control station undoubtedly reduces its processing efficiency. At the same time, the upload of the event number increases the network packet, which inevitably increases the network load and improves the communication error rate. In addition, after receiving the uploaded data, the real-time processing task needs to process the variable data and update it to the database on the one hand, and process and store the event on the other hand. At the same time, real-time processing tasks also respond to operator requests for real-time data and events. This design pattern that combines data management and event processing seriously affects the performance of the system and does not meet the performance requirements of the DCS system for real-time processing, stable operation, and high throughput.

In order to solve the above-mentioned defects existing in the prior art, the present invention transplants the process of determining an event to an upper layer DCS server, thereby reducing network data packets uploaded by the control station and improving network transmission. Efficiency; At the same time, the DCS server rationally divides the real-time variable data management and event processing functions in order to reduce the coupling between modules and improve system performance.

The following describes the event processing method of the DCS provided by the present invention. Referring to FIG. 2, it is a schematic flowchart of the steps of the method, which mainly includes the following steps:

Step 201: The DCS server receives variable data uploaded by the control station.

In the technical solution of the present invention, after receiving the real-time variable data, the control station does not perform the judgment processing of whether to generate a new event, but directly transmits the variable data to the DCS server, so that the network data uploaded by the control station can be greatly reduced. The package improves the efficiency of network transmission, so the time for processing variable data can be shortened.

Step 202: The DCS server determines whether the variable data generates a new event. If yes, the DCS server processes the event according to the preset event processing rule.

It can be seen that the real-time variable data determines whether a new event is generated by the DCS server. When a new event is generated, the server automatically performs the correct event processing according to the preset event processing rule. Since in the process of judging whether a new event is generated, it is necessary to combine specific variable data, and the real-time variable data is stored in the DCS server, so that the variable between the DCS server and the control station in the prior art can be avoided. Data access, and thus, based on the principle of high cohesion and low coupling, not only can reduce communication between processes, but also, event processing efficiency is greatly improved.

After the DCS server processes the event, the historical data generated by the event processing may be stored by the DCS server according to the specific application scenario. The storage mode may be in the form of a common log. At the same time, the DCS server is able to respond to external requests for query data.

In the embodiment of the present invention, the DCS server determines whether the variable data generates a new event: the DCS server compares whether the current item value corresponding to the variable data is the same as the stored item value, and if not, determines to generate New event.

In order to facilitate system data management, variable data in the system running process is usually defined. Different variable data belong to different variable types and correspond to different item values, and different item values correspond to different events. Therefore, after receiving the variable data uploaded by the control station, the DCS server can obtain the corresponding current item value according to the variable data, and compare whether the current item value is the same as the stored item value, and if the two are different, it can be determined that the data is generated. New event. In addition, the implementation manner of the corresponding processing of the event by the DCS server according to the preset event processing rule may be:

The DCS server obtains, according to the identifier information, a processing rule corresponding to the identifier information in the preset event processing rule;

The identification information described herein is preset to distinguish different events, and may have different representation manners, for example, a conventional event number, which is not specifically limited in the present invention.

Usually, there are different event processing rules for different events. After the DCS server obtains the identification information of the event, the processing rule of the corresponding identification information in the rule may be processed according to the preset event, so that the current event is processed accordingly.

The event processing rule in the embodiment of the present invention mainly adopts a configuration file manner, and can write a configuration file according to unnecessary project requirements, thereby avoiding program modification. This way, the good performance of the software reflects the platform, openness and scalability of the software.

Of course, in the process of storing the real-time data generated by the DCS server in the event processing process, in order to prevent the DCS server from performing repeated historical data records on the same event, a corresponding detection mechanism may be set, when it is determined that there is a history of repeated writing. In the case of data, the historical data repeatedly written is automatically deleted, thereby avoiding waste of redundant data on the DCS server memory resources.

The present invention will be described in detail below in conjunction with the specific embodiments of the invention.

Depending on the acquired signal, different variable types (such as digital input/output type, analog input/output type, etc.) need to be set. Each variable type contains multiple items, and the item also has multiple data types, such as: The current value item of the switch quantity is the bool type, the current value item of the analog quantity is the float type, the alarm item of the switch quantity is the bool type, and the simulation The amount of alarm items is BYTE type. A variable point defined as a variable type may represent a field device, and an item at that point may represent a digital signal or attribute of the device (such as temperature, alarm properties, etc.). Table 1 shows the variable types of AVI4 and the included items.

Table 1, variable types of AVI4

Variable class item name data type item description Type

PN string name

SN BYTE station number

DS string point description

AV float current value

MU float range limit

MD float range lower limit

AVI4 class

H2L float height 2 limit

Type

H1L float height 1 limit

Quantity 4 limit

L1L float low 1 limit

Value input

L2L float low 2 limit

Types of)

H2 BYTE high 2 limit alarm level

HI BYTE high 1 limit alarm level

L1 BYTE low 1 limit alarm level

L2 BYTE low 2 limit alarm level

ASS BYTE limit alarm status

, , , , , , , , ,

The DCS server is responsible for receiving the variable data uploaded by the control station, updating the variable data to the database, and determining whether the new item value corresponding to the current variable data is the same as the existing original item value. If the item value has changed, it is determined that a new event is generated.

For different types of item values, the process of determining the event will refer to different item name event tables: For example: BOOL type item name event table and BYTE type item name event table. Table 2 shows an example of an event with an item value type of BOOL. The event defined by this table is an event whose item value changes between 0 and 1. If the DCS server determines that the item value is a BOOL type, first find the type of the variable point to which the item belongs in the BOOL type item name event table. If it exists, it is determined whether the variable point type is configured with the event of this item. If configured, the corresponding event number is obtained according to the new item value. For example: The DCS server determines that the type of the received variable point is DVI2 type, and the item name is DVJLDV value.

0->1, the comparison table 2 can get the event number 21 (switch 0->1 displacement event); if the DV value is

1- >0, compare table 1 to get event number 22 (switch 1->0 displacement event). If the item ALM of the DVI2 type point is 0->1, the event number 3 can be obtained according to Table 2 (switch alarm event); if the ALM value is 1->0, the event number can be obtained according to Table 2. 4 (switching alarm recovery event) Table 2, BOOL type item name event example

Example Description

[Type_l]

TypeName=DVI2 ; DVI2 variable type

TypeNo=6; type number

ItemNum=8; the number of items. Indicates that 8 items in the DVI2 type change will generate an event.

Iteml=DV

Iteml_0=22; item name. This item is the current value output of the switch

Iteml_l=21 ; the value of this item changes, and the event number generated by 1->0 is 22

Item2=ALM ; the value of this item changes, and the event number generated by 0->1

Item2_0=4 is 21

Item2_l=3 ; item name. This item is a police status item

• . . ; The event number generated by 1->0 is 4

; the event number generated by 0->1 is 3

Table 3 shows an example of an event with an item value of BYTE. Each change (0 and 1) in the item's BYTE data can represent a type of event. If the real-time library management task determines that the item value is BYTE type, first find the event of whether this item is configured in the BYTE type item name event table. If configured, it is determined which bits in the BYTE data have changed, and then the event number is obtained according to the hexadecimal number and the change value (0->1 or 1->0) corresponding to the change bit. For example: the item ASS is the status word of the analog alarm, Vall=0xl indicates that the lowest bit of the ASS changes, when the lowest bit changes from 0 to 1, the event No. 19 (simulation low 4 limit alarm) will be triggered; When the bit changes from 1 to 0, event number 20 (simulation low 4 limit alarm recovery) will be triggered.

BYTE type item name event example

Example Description

[Item_l]

ItemName=ASS; item name. This item is an analog alarm status word, BYTE class

ValNum=8 type (8 digits)

; the number of items. Indicates that an ASS item can generate 8 events.

Vall=0xl

Vall_0=20 ; the lowest bit of the ASS item value changes

Vall"=19; this bit changes, the event number generated by 1->0 is 20

; The bit changes, the event number generated by 0->1 is 19 \Ά\2-- =0x2 ; the last two bits of the ASS item value change

Val2_ —0=16 ; this bit changes, the event number generated by 1->0 is 16

Val2_ —1=15 ; this bit changes, the event number generated by 0->1 is 15

Val3: =0x4 ; the last three bits of the ASS value change

Val3_ —0=12 ; this bit changes, the event number generated by 1->0 is 12

Val3_ —1=11 ; this bit changes, the event number generated by 0->1 is 11

Both the BOOL type item name event table and the BYTE type item name event table are provided in the form of a configuration file. Since the variable types of each project are different, and the change of each item represents different meanings, each project can configure the item name event table according to its own needs without modifying the program code.

After obtaining the event number, you need to find the corresponding event definition in the event definition list. The event definition list defines the preconditions for each type of event, the output content and format of the event description, the identifier of the event entry/table, and the event special handling identifier. The event entry log/table identifier and the event special handling identifier are used by the event processing task in processing the event.

Table 4 lists the definition of the digital alarm event and the definition of the switching displacement event. Where: The precondition for the occurrence of an event can specify the range of conditions triggered by such an event. For example: The alarm event of the switch quantity does not need to be generated without the alarm level. By judging this precondition, the alarm event can be shielded and restricted during the process of generating the event;

The output content and format of the event description is to make the content of the event uniform and convenient, so that the operator can clearly and clearly view the event content. The output format includes output offset, output length, and output mode. The output offset specifies that the content begins to be output at the first digit of the event description. The output length specifies how many bytes of content the content is. The output mode is programmatic, and all specified formats have been processed in advance in the program; The identification of the event entry log/table can facilitate the event processing task to write which type of event and table to which type of event; here, both the log and the table are used to record the data generated during the event processing.

Since some events may require special handling, adding special handling identifiers to the event specification can provide great convenience for handling events.

Table 4 Example of event definition list

Example Description

[EVENT_3]

EventName=Digital Alarm Begin; event definition 3

EventNo=3; event name

ItemNum=2; event number

Item_l=ItemName: DAT, OutOffset: 0, OutWidth: 0, OutForma; number of items processed t: 26, ShowCondition: -l; alarm level limit

Item_2=ItemName: KAPN, OutOffset: 0, OutWidth: 32, OutFor; The output of the KA point name is set to mat: 8, ShowCondition: - 1

Format— ******************************** 艮^^ ; Description of the output

EnterLog=0x8200; enter the log identifier

EnterTable=0x4000 ; enter the identity of the form

SpecProc=0; special handling flag

AlarmLevelIName=DAT ; alarm level item name

ItemName=ALM ; the item name corresponding to the event

[EVENT_21]; event definition 21

EventName=Digital Change 0->l; event name EventNo=21; event number

ItemNum=3 ; the number of items processed

Item_l=ItemName: INLOG, OutOffset: 0, OutWidth: 0, OutFor; generate log limit mat: 36, ShowCondition: -l; jitter limit for events

Item— 2=ItemName: BC, OutOffset: 0, OutWidth: 0, OutFormat:

27, ShowCondition: - 1 ; description of the content, format

Item_3=ItemName: El, OutOffset: 0, OutWidth: 8, OutFormat: ; Description of the output

8, ShowCondition: -l; enter the log ID

Format^** ****** ; enter the identity of the form

EnterLog=0x8000; special handling flag

EnterTable=0; the item name corresponding to the event

SpecProc=0 • . .

ItemName=DV

The list of event definitions is also provided as a configuration file.

The use of this table is illustrated by the example in Table 3. If: After obtaining event number 3, Step 1: Find the event with event number 3 in the event definition list, and write event number 3, variable point name, item name (ALM) and time into the record;

Step 2: Determine whether the number of database items to be processed (ItemNum) is not 0. If it is not 0, process it item by item. The value of each item is first read from the database and then processed according to the output format (OutFormat). The output offset and length of the first alarm level DAT are both 0, indicating that the content of the item does not need to be displayed in the event description. The output mode 26 has been processed in the program. The processing of the 26 output mode means that this event is automatically discarded when the value of the item read from the database is zero. Other items are treated similarly. The second KA point name KAPN has an output offset of 0 and an output length of 32, indicating the item. The content starts at bit 0 of the event description (Format) and is 32 bytes long. The output mode 8 is also processed in the program. The processing meaning of the 8 output mode is that the read item value is output in the format of a string;

Step 3: Since the event defines the alarm level item AlarmLevellName , the value of the alarm level DAT is read and written into the event record;

Step 4: Read the information that should be included in each event from the database according to the variable point name: point description, point type, process system name, area number, station number, etc. This completes a complete event record (the format of the event record is shown in Table 5).

According to the actual needs, the events can be spliced and sorted according to the specifications defined by this event, and finally a complete event information record is obtained.

Table 5 event record structure

The main function of the DCS real-time server is real-time data management and event processing. When an event is generated in the real-time data management task, in the process of sending the event to the event processing task, the shared memory mode of the convenient single is discarded and the network is adopted. The purpose of transmission is to reduce the coupling between modules, improve the independence of the module, and reduce the risk of mutual interference.

The event processing task supports a variety of logs and tables. The type and number of logs/alarms and the maximum number of information for each log/alarm can be configured according to the actual needs of the project. See Table 6 for details. There must be a type of "full log" type in the type of log, all events must enter this log. The full log uses the hash index algorithm to detect whether a write event already exists to prevent repeated writes, which greatly improves the processing power of the system (the system stipulates that 1500 events can be processed in one second). Due to the special nature of the alarm: Only one kind of event of the same point can be recorded (one point of alarm and alarm recovery is the same kind of event), the new event will replace the same kind of event at that point, so the alarm table adopts double index structure: time series index and point name index, which is convenient for alarm Timing reading of writes and alarms. Both the log and alarm tables support cyclic write events, and when full capacity is reached, the new event record will overwrite the old record. In addition, the alarm table write can be configured in another way: When the table is full, new events will be discarded.

Table 6 Log and Table Configuration Table

Example Description

[fix]

Lognum=6; number of records tablenum=8; number of tables

[log_l]

Logno=l ;曰志号 logname=CompleteLog ;log name (full log) logrecnum=30000 ;

[log_2]

Logno=2

Logname=SOE log logrecnum=4000

[table_l]

Tableno=l ; table number Tablename=艮 police total list; table name (alarm total list) tablerecnum=4000; table number

[table_2]

Tableno=2

Tablename^ check alarm list tablerecnum=600

The event processing task processes the event after receiving the event data. First, based on the event number in the event record, the log/table identifier and the special handling identifier are obtained in the event definition list. The log/table identifier is a hexadecimal number, which is judged from the high position. If this bit is 1, the event will enter the log/table. For example: EnterLog=0x8200, starting from the high position, the first and seventh digits are not 0, then the event will enter the 1st and 7th logs. After the event is written to the log/table, the event processing task will specifically handle the special requirements of this event.

Figure 3 is the overall flow chart of the above event generation and event processing, including:

Step 301: The control station uploads real-time variable data to the DCS server.

Step 302: The DCS server acquires an item value corresponding to the variable data.

Step 303, the DCS server determines whether the item value corresponding to the variable data is the same as the stored history item value, and if no, proceeds to step 304;

Step 304: The DCS server searches for an item name event table according to the item value.

Step 305: The DCS server determines whether a new event is generated. If yes, proceed to step 306. Step 306: The DCS server determines, according to the event definition list, which event is generated.

Step 307: The DCS server performs event recording.

Step 308: The DCS server obtains the identifier of the entry/form and the special processing identifier from the event definition list according to the corresponding event record.

Step 309: The DCS server writes the event into a prepared log/table; Step 310: The DCS server determines, according to the special processing identifier, whether the event needs to be specially processed, if yes, proceed to step 311; if not, proceed to step 312;

Step 311: The DCS server performs specific special processing on the event.

Step 312: The DCS server processes the event accordingly.

It can be seen that the judgment of the event generated in the embodiment of the present invention is completed in the DCS server, instead of being in the controller, so that the control station does not need to upload the event number, thereby reducing the data packet transmitted between the control station and the server, thereby reducing the number of packets. The data communication between the control station and the server reduces the network load. Since the real-time variable data is read into the database during the event generation process, the processing of the event is performed in the DCS server, which also reduces the data access between the modules, reduces the complexity of the task processing, and reduces the inter-module space. Coupling degree. In addition, the event generation mechanism mainly adopts a configuration file method, and can write a configuration file according to unnecessary project requirements, without having to rewrite a processing program for each project, thereby avoiding program modification, which improves the reusability of the code. The development cycle is reduced, which is a good example of the platform, openness and scalability of the software. Corresponding to the event processing method embodiment of the distributed control system of the present invention, the embodiment provides an event processing system of the distributed control system, as shown in FIG. 4, which is a schematic structural diagram of the system, and the system mainly includes: DCS The server 40 and the control station 41, the control station 41 is configured to upload variable data to the DCS server 40, wherein the DCS server 40 includes:

The receiving module 401 is configured to receive variable data uploaded by the control station 41.

The determining module 402 is configured to determine whether the variable data generates a new event;

The event processing module 403 is configured to process the event according to the preset event processing rule if the new event is determined to be generated.

It can be seen that the real-time variable data determines whether a new event is generated by the DCS server. When a new event is generated, the server automatically performs the correct event processing according to the preset event processing rule. Since in the process of judging whether a new event is generated, specific variable data needs to be combined, and the real-time variable data is stored in the DCS real-time database in the DCS server, so that the DCS server in the prior art can be avoided. Variable data access between stations, thus, based on the principle of high cohesion and low coupling, not only can reduce communication between processes, but also the event processing efficiency is greatly improved.

Preferably, the determining module further includes: a current item value obtaining submodule, configured to acquire a current item value corresponding to the variable data; a comparison submodule, configured to compare whether the current item value is the same as the stored item value, and if not, determine to generate a new one event.

In order to facilitate system data management, the variable data in the system running process is usually defined. Different variable data corresponds to different item values, and different item values correspond to different events. Therefore, after receiving the variable data uploaded by the control station, the DCS server can obtain the corresponding current item value according to the variable data, and compare whether the current item value is the same as the stored history item value. If the two are different, the DCS server can determine the generation. New events.

The event processing module further includes:

The processing sub-module is configured to perform corresponding processing on the current data according to the processing rule. Usually, there are different event processing rules for different events. After the DCS server obtains the identification information of the event, the processing rule of the corresponding identification information in the rule may be processed according to the preset event, so that the current event is processed accordingly.

Preferably, in another embodiment of the present invention, as shown in FIG. 5, the DCS server may further include: a real-time data storage module 404, configured to store the event after performing corresponding processing on the event Real-time data generated when processing.

After the DCS server processes the event, the historical data storage module in the DCS server stores the historical data generated in the event processing process according to the specific application scenario. The storage mode may be in a common log format. .

In addition, as shown in FIG. 6, the system may further include:

The verification module 405 is configured to detect, in the stored real-time data, whether there is repeated writing of data for the same event; The deleting module 406 is configured to delete the repeatedly written data when it is determined that there is repeatedly written data.

In the process of storing the real-time data generated by the DCS server in the event processing process, in order to prevent the DCS server from performing repeated data recording on the same event, a corresponding detection mechanism may be set, and when it is determined that there is repeatedly written data, The repeatedly written data is automatically deleted, thereby avoiding waste of redundant data resources of the DCS server. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment. The device embodiments described above are merely illustrative, wherein 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, ie may be located One place, or it can be distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the embodiments of the invention. . Therefore, the present embodiments of the invention are not to be limited to the embodiments shown herein, but are to be accorded to the broadest scope of the principles and novel features disclosed herein.

Claims

Rights request

An event processing method for a distributed control system, the method comprising: a distributed control system: a DCS server receives variable data uploaded by a control station;

The event processing method of the distributed control system according to claim 1, wherein after the DCS server performs corresponding processing on the event, the method further includes:

The DCS server stores real-time data generated when the event is processed.

The event processing method of the distributed control system according to claim 1, wherein the DCS server determines whether the variable data generates a new event, including:

The DCS server compares whether the current item value corresponding to the variable data is the same as the stored item value, and if not, determines to generate a new event.

The event processing method of the distributed control system according to claim 1, wherein the DCS server performs corresponding processing on the event according to the preset event processing rule, and the method includes: the DCS server obtaining the current event Corresponding identification information;

The event processing method of the distributed control system according to claim 4, wherein the preset event processing rule is set in a configuration file manner.

The event processing method of the distributed control system according to any one of claims 2 to 5, wherein the method further comprises:

The DCS server detects whether there is duplicate written data for the same event in the stored real-time data, and if so, deletes the repeatedly written data.

An event processing system of a distributed control system, the system comprising a DCS server and a control station, wherein the control station is configured to upload variable data to the DCS server, wherein the DCS server comprises:

a receiving module, configured to receive variable data uploaded by the control station; a determining module, configured to determine whether the variable data generates a new event;

The event processing system of the distributed control system according to claim 7, wherein the DCS server further comprises:

The event processing system of the distributed control system according to claim 7, wherein the determining module further comprises:

The event processing system of the distributed control system according to claim 7, wherein the event processing module further comprises:

The processing sub-module is configured to perform corresponding processing on the current data according to the processing rule.

The event processing system of the distributed control system according to any one of claims 8 to 10, wherein the system further comprises:

a verification module, configured to detect whether there is repeatedly written data in the stored real-time data for the same event;