Equipment label generation method, apparatus and equipment

Abstract

The present application provides a device label generation method, apparatus and device, the method comprising: determining label processing reference information for any monitored event message; determining the label processing action corresponding to the event message according to the label processing reference information and label processing rules. The method can automatically perform label processing for the front-end device.

Description

Technical Field

[0001] The present application relates to the field of security technology, and in particular to a method, device and equipment for generating a device label. Background Art

[0002] With the continuous development of security construction, more and more monitoring devices or sensor devices are deployed in various areas. Security management platforms usually need to manage tens of thousands of monitoring devices and sensor devices (referred to as front-end devices). How to quickly search for the front-end devices that users want to view has become an important research topic.

[0003] For example, if a user wants to see where there is water on the road, it would be time-consuming and laborious to click on the preview screen of each device one by one, and there is a possibility of missing something. Summary of the invention

[0004] In view of this, the present application provides a method, apparatus and device for generating a device tag.

[0005] According to a first aspect of an embodiment of the present application, a method for generating a device tag is provided, including:

[0006] For any monitored event message, determine the label processing reference information;

[0007] Determine the label processing action corresponding to the event message based on the label processing reference information and the label processing rule; wherein the label processing rule includes a label generation rule and a label cancellation rule, and determine the label processing action corresponding to the event message based on the label processing reference information and the label processing rule, including: judging whether the label processing reference information satisfies the label generation rule, and if so, marking the front-end device to which the event message belongs with a label corresponding to the label generation rule;

[0008] It is determined whether the label processing reference information satisfies the label cancellation rule. If so, the label corresponding to the label generation rule is cancelled for the front-end device to which the event message belongs.

[0009] According to a second aspect of an embodiment of the present application, there is provided a device tag generating apparatus, including:

[0010] A first determining unit is configured to determine label processing reference information for any monitored event message;

[0011] A second determining unit is configured to determine a label processing action corresponding to the event message according to the label processing reference information and the label processing rule;

[0012] The label processing rules include label generation rules and label cancellation rules.

[0013] The second determining unit is specifically configured to:

[0014] Determine whether the label processing reference information satisfies the label generation rule, and if so, mark the front-end device to which the event message belongs with a label corresponding to the label generation rule;

[0015] It is determined whether the label processing reference information satisfies the label cancellation rule. If so, the label corresponding to the label generation rule is cancelled for the front-end device to which the event message belongs.

[0016] According to a third aspect of an embodiment of the present application, there is provided an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0017] Memory, used to store computer programs;

[0018] The processor is used to implement the method provided in the first aspect when executing the program stored in the memory.

[0019] According to a fourth aspect of an embodiment of the present application, a non-temporary computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the method provided in the first aspect is implemented.

[0020] The device label generation method of the embodiment of the present application can determine the label processing reference information for any event message monitored, and determine the label processing action corresponding to the event message based on the label processing reference information and the label processing rules, thereby realizing automatic label processing for the front-end device based on the event message reported by the front-end device, providing technical support for label-based device search, and thus improving the efficiency of device search; in addition, since the label processing rules include label generation rules and label cancellation rules, the label processing action may include marking or canceling the label for the front-end device to which the event message belongs, that is, the label marked by the front-end device can be automatically canceled when the conditions are met. Therefore, the label of the front-end device can change dynamically in real time according to the event message reported by it, thereby improving the rationality of label setting. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is a flowchart of a method for generating a device tag provided in an embodiment of the present application;

[0022] Figure 2 It is a flowchart of a method for generating a device tag provided in an embodiment of the present application;

[0023] Figure 3It is a structural schematic diagram of a device label generation apparatus provided in an embodiment of the present application;

[0024] Figure 4 It is a structural schematic diagram of another device label generation apparatus provided in an embodiment of the present application;

[0025] Figure 5 It is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the technical solutions provided by the embodiments of the present application and to make the above-mentioned purposes, features and advantages of the embodiments of the present application more obvious and understandable, the technical solutions in the embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0027] It should be noted that the serial numbers of the steps in the embodiments of the present application do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0028] See also Figure 1 , is a flow chart of a method for generating a device tag provided in an embodiment of the present application, such as Figure 1 As shown, the device tag generation method may include the following steps:

[0029] Step S100: For any monitored event message, determine tag processing reference information.

[0030] Step S110: determining the label processing action corresponding to the event message according to the label processing reference information and the label processing rule; wherein the label processing rule includes a label generation rule and a label cancellation rule, and determining the label processing action corresponding to the event message according to the label processing reference information and the label processing rule includes: determining whether the label processing reference information satisfies the label generation rule, and if so, marking the front-end device to which the event message belongs with a label corresponding to the label generation rule;

[0031] It is determined whether the label processing reference information satisfies the label cancellation rule. If so, the label corresponding to the label generation rule is cancelled for the front-end device to which the event message belongs.

[0032] Exemplarily, the label processing reference information may include, but is not limited to, one or more of the frequency of event occurrence, the value of a specific field in the event message, and the number of times the label corresponding to the event is marked.

[0033] Exemplarily, the event message reported by the front-end device may be recorded in a message queue of the device generating the event, and the event message reported by the device may be monitored by monitoring the message queue.

[0034] In the embodiment of the present application, for any monitored event message, the label processing action corresponding to the event message can be determined based on the label processing reference information and label processing rules of the event message.

[0035] Exemplarily, the label processing rules include label generation rules and label cancellation rules.

[0036] Accordingly, for any monitored event message, it can be determined whether the label processing reference information of the event message satisfies the label generation rule, or satisfies the label cancellation rule.

[0037] If the label processing reference information of the event message satisfies the label generation rule, the front-end device to which the event message belongs (ie, the front-end device that reports the event message) is marked with a label corresponding to the label generation rule.

[0038] If the label processing reference information of the event message satisfies the label cancellation rule, the label corresponding to the label generation rule is cancelled for the front-end device to which the event message belongs.

[0039] Exemplarily, the front-end device to which the event message belongs may be determined based on the device code in the event message.

[0040] It should be noted that when the label processing reference information of the event message meets the label cancellation rule, it can be determined whether the front-end device to which the event message belongs has currently been marked with the corresponding label. If it has been marked, the corresponding label is canceled, otherwise, no additional processing is required.

[0041] It can be seen that in Figure 1 In the method flow shown, for any event message monitored, the label processing reference information can be determined, and based on the label processing reference information and the label processing rules, the label processing action corresponding to the event message can be determined, thereby realizing automatic label processing for the front-end device based on the event message reported by the front-end device, providing technical support for label-based device search, and thus improving the efficiency of device search; in addition, since the label processing rules include label generation rules and label cancellation rules, the label processing action can include marking or canceling the label for the front-end device to which the event message belongs, that is, the label marked by the front-end device can be automatically canceled when the conditions are met. Therefore, the label of the front-end device can change dynamically in real time according to the event message it reports, thereby improving the rationality of label setting.

[0042] In some embodiments, the tag processing reference information includes event occurrence frequency.

[0043] Determining the label processing action corresponding to the event message based on the label processing reference information and the label processing rule may include:

[0044] According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the number of times the front-end device reports events of the event type within the first time window;

[0045] The label processing action corresponding to the event message is determined based on the comparison result of the number of times the front-end device reports events of the event type within the first time window and the reporting number threshold.

[0046] Exemplarily, take the example that the tag processing reference information includes the frequency of event occurrence.

[0047] For the monitored event message, the front-end device to which the event message belongs and the event type corresponding to the event message can be determined.

[0048] For example, the front-end device to which the event message belongs can be determined based on the device code in the event message. The event type corresponding to the event message can be determined based on the event code in the event message.

[0049] Based on the front-end device to which the event message belongs and the event type corresponding to the event message, the number of times the front-end device reports events of this event type within a preset time window (which can be called the first time window) can be determined, and the number of reports can be compared with the preset reporting number threshold, and the label processing action corresponding to the event message can be determined based on the comparison result.

[0050] In an example, the above-mentioned determining the label processing action corresponding to the event message based on the comparison result of the number of times the front-end device reports the event type within the first time window and the reporting number threshold includes:

[0051] If the number of times the front-end device reports events of the event type within the first time window is not less than the reporting number threshold, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the label generation rule;

[0052] If the number of times the front-end device reports events of the event type within the first time window is less than the reporting number threshold, the label cancellation rule is met, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0053] The tag corresponding to the tag generation rule represents the occurrence of the event corresponding to the event type. In some embodiments, the tag processing reference information includes the value of a specific field in the event message.

[0054] Determining the label processing action corresponding to the event message based on the label processing reference information and the label processing rule may include:

[0055] Determine the label processing action corresponding to the event message based on the comparison result between the value of a specific field in the event message and a preset threshold;

[0056] or,

[0057] According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the comparison result between the value of a specific field in the event message of the event type reported by the front-end device within the second time window and a preset threshold, and determine the label processing action corresponding to the event message according to the comparison result;

[0058] or,

[0059] According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the comparison result between the value of a specific field in the event message and the target value, and determine the label processing action corresponding to the event message according to the comparison result; wherein the target value is the minimum or maximum value of the value of a specific field in the event message of the event type reported by the front-end device within the previous third time window;

[0060] or,

[0061] Determine, based on the front-end device to which the event message belongs and the event type to which the event message corresponds, the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, and determine, based on the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, the label processing action corresponding to the event message;

[0062] or,

[0063] Based on the front-end device to which the event message belongs and the event type corresponding to the event message, determine the value of a specific field in the event message, compare it with the value of a specific field in the event message of this event type last reported by the front-end device, and determine the label processing action corresponding to the event message based on the comparison result.

[0064] Exemplarily, take the example that the tag processing reference information includes the value of a specific field in the event message.

[0065] For the monitored event messages, the tag processing action can be determined based on the value of a specific field in the event message.

[0066] Exemplarily, the label processing action can be determined based on the comparison result between the value of a specific field in the event message and a preset threshold, or the comparison result between the values ​​of specific fields in different event messages of the same type of event reported by the same front-end device.

[0067] It may further include determining the label processing action based on a comparison result between a value of a specific field in the event message and a preset threshold, or a comparison result between values ​​of specific fields in different event messages of the same event.

[0068] As an example, the label processing action corresponding to the event message may be determined based on a comparison result between a value of a specific field in the event message and a preset threshold.

[0069] In one example, the preset threshold may include at least one threshold range;

[0070] The above-mentioned determining the label processing action corresponding to the event message based on the comparison result of the value of the specific field in the event message and the preset threshold value may include:

[0071] If the value of a specific field in the event message is within any threshold range of at least one threshold range, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the threshold range among the labels corresponding to the label generation rule;

[0072] If the value of a specific field in the event message is not within any threshold range of at least one threshold range, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is canceled for the front-end device.

[0073] Exemplarily, take the example that the preset threshold includes at least one threshold range, wherein different threshold ranges may correspond to different tags.

[0074] Accordingly, it can be determined whether the value of a specific field in the event message is within any threshold range of the at least one threshold range.

[0075] If the value of a specific field in the event message is within any threshold range of at least one threshold range, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the threshold range in the label corresponding to the label generation rule.

[0076] If the value of a specific field in the event message is not within any threshold range of at least one threshold range, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is canceled for the front-end device.

[0077] For example, taking the rainfall reporting event as an example, based on the value of the "rainfall" field in the event report (which can be called the rainfall value), the at least one threshold range can include a threshold range corresponding to the "heavy rain" label (greater than or equal to the first rainfall threshold, which can be called the first threshold range), a threshold range corresponding to the "moderate rain" label (less than the first rainfall threshold and greater than or equal to the second rainfall threshold, which can be called the second threshold range), and a threshold range corresponding to the "light rain" label (less than the second rainfall threshold and greater than 0, which can be called the third threshold range).

[0078] Accordingly, when the rainfall value is greater than or equal to the first rainfall threshold (i.e., it is within the first threshold range), the label "heavy rain" is generated; when the rainfall value is less than the first rainfall threshold and greater than or equal to the second rainfall threshold (i.e., it is within the second threshold range), the label "moderate rain" is generated; when the rainfall value is less than the second rainfall threshold and greater than 0 (i.e., it is within the third threshold range), the label "light rain" is generated; when the rainfall value is equal to 0 (i.e., it is not within any threshold range), the label previously marked for the corresponding device (if any) is canceled, or there is no need to generate a label.

[0079] As another example, based on the front-end device to which the event message belongs and the event type corresponding to the event message, the comparison result between the value of a specific field in the event message of the event type reported by the front-end device within the second time window and a preset threshold can be determined, and the label processing action corresponding to the event message can be determined based on the comparison result.

[0080] In one example, the preset threshold includes at least one threshold range;

[0081] Determining a label processing action corresponding to the event message based on a comparison result between a value of a specific field in the event message of the event type reported by the front-end device within the second time window and a preset threshold value may include:

[0082] If the values ​​of specific fields in the event messages of the event type reported by the front-end device within the second time window are all within the same threshold range, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the threshold range among the labels corresponding to the label generation rule;

[0083] If the value of a specific field in the event message of the event type reported by the front-end device within the second time window is not within the same threshold range, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0084] Among the tags corresponding to the tag generation rule, the tags corresponding to any threshold range represent that the event corresponding to the threshold range continues to occur.

[0085] Exemplarily, a time window (which may be called a second time window) may be pre-set to determine whether a corresponding event continues to occur based on whether the value of a specific field in an event message of the same type of event reported by the same front-end device within the second time window continues to be within the same threshold range.

[0086] Still taking the rainfall reporting event as an example, if the rainfall values ​​in the rainfall reporting event messages reported by the same front-end device in the time window t (i.e., the second time window) are all greater than or equal to the first rainfall threshold (i.e., they are all within the first threshold range), the label "Continuous Heavy Rain" can be marked. If the rainfall values ​​in the event messages reported by the same front-end device in the time window t do not satisfy the requirement that they are all greater than or equal to the first rainfall threshold (i.e., they are not within the same threshold range), the "Continuous Heavy Rain" label (if it exists) can be cancelled.

[0087] As another example, the comparison result between the value of a specific field in the event message and the target value can be determined based on the front-end device to which the event message belongs and the event type corresponding to the event message, and the label processing action corresponding to the event message can be determined based on the comparison result; wherein the target value is the minimum or maximum value of the specific field in the event message of the event type reported by the front-end device within the previous third time window.

[0088] In an example, determining a label processing action corresponding to the event message according to a comparison result between a value of a specific field in the event message and a target value may include:

[0089] If the target value is the minimum value, the value of the specific field in the event message is less than the target value, and the difference between the two is not less than the preset threshold, or the target value is the maximum value, the value of the specific field in the event message is greater than the target value, and the difference between the two is not less than the preset threshold, then the label generation rule is satisfied, and the front-end device is marked with a label corresponding to the label generation rule;

[0090] Otherwise, if the label cancellation rule is met, the label corresponding to the label generation rule is cancelled for the front-end device;

[0091] The label corresponding to the label generation rule indicates that the event of the event type meets a specific trend.

[0092] For example, a trend can be judged and a tag processing action can be determined by comparing a field value in different event messages.

[0093] Take the target value as the minimum value as an example.

[0094] When the value of a specific field in the event message is less than the target value and the difference between the two is not less than the preset threshold, it can be determined that a corresponding trend exists, and thus, the front-end device can be marked with a label corresponding to the label generation rule (which can be called a trend label).

[0095] When the value of a specific field in the event message is not less than the target value, or the value of a specific field in the event message is less than the target value, but the difference between the two is less than the preset threshold, it can be determined that there is no corresponding trend, and the label corresponding to the label generation rule is canceled for the front-end device.

[0096] For example, taking the water level detection event as an example, for the monitored water level detection reporting event, you can get the value of the "water level" field, determine the current water level value, and compare the current water level value with the lowest water level value in the previous time window (which can be called the third time window). If the current water level value is greater than the lowest water level value in the previous time window, and the difference between the two is greater than or equal to the preset water level difference threshold, then the label "Water level increases too fast" is generated.

[0097] As another example, the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window can be determined based on the front-end device to which the event message belongs and the event type to which the event message corresponds, and the label processing action corresponding to the event message can be determined based on the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window. In one example, determining the label processing action corresponding to the event message based on the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window can include:

[0098] Determine the sum of the differences within the fourth time window according to the difference between the values ​​of two specific fields in the event message of the event type reported by the front-end device within the fourth time window;

[0099] If the sum of the differences within the fourth time window is not less than a preset threshold, the label generation rule is satisfied, and a label corresponding to the label generation rule is marked on the front-end device;

[0100] If the sum of the differences within the fourth time window is less than a preset threshold, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0101] The label corresponding to the label generation rule indicates that the event of the event type meets a specific trend.

[0102] Exemplarily, corresponding statistical values ​​may be determined based on multiple field values ​​in the same event message, and a trend may be judged and a label processing action may be determined based on the statistical values ​​within a preset time window (which may be referred to as a fourth time window).

[0103] For example, taking passenger flow statistics as an example, the front-end equipment can be deployed at the entrances and exits of a specific area. When people are detected entering or exiting, the passenger flow event message is reported. The passenger flow event message includes the number of people entering and the number of people leaving. For any time window (which can be called the fourth time window), the new passenger flow can be determined based on the passenger flow event message reported within the fourth time window.

[0104] Among them, for any passenger flow event message, the number of people entering the passenger flow event message minus the number of people leaving the passenger flow event message is the new passenger flow corresponding to the passenger flow event message. Thus, the new passenger flow in the fourth time window can be counted. When the new passenger flow exceeds the preset passenger flow threshold, a "passenger flow surge" label is generated.

[0105] As another example, the value of a specific field in the event message can be determined based on the front-end device to which the event message belongs and the event type to which the event message corresponds, and the result of comparison between the value of a specific field in the event message of the event type last reported by the front-end device, and the label processing action corresponding to the event message can be determined based on the comparison result.

[0106] In an example, determining the label processing action corresponding to the event message based on the comparison result of the value of a specific field in the event message and the value of a specific field in the event message of the event type last reported by the front-end device may include:

[0107] If the value of the specific field in the event message minus the value of the specific field in the event message of the event type reported by the front-end device last time, the difference is greater than the preset threshold, then the label generation rule is met, and the front-end device is marked with a label corresponding to the label generation rule;

[0108] If the value of the specific field in the event message minus the value of the specific field in the event message of the event type reported by the front-end device last time, the difference is not greater than the preset threshold, then the label cancellation rule is met, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0109] The label corresponding to the label generation rule represents the occurrence of the event corresponding to the event type.

[0110] Exemplarily, label processing may be performed for the front-end device based on the difference between the values ​​of specific fields in event messages of the same type continuously reported by the same front-end device.

[0111] For example, taking the tilt detection event as an example, for the monitored tilt detection event message, the value of the tilt field in the tilt detection event message can be subtracted from the value of the tilt field in the previous tilt detection event message reported by the same front-end device. If the difference is greater than the preset tilt difference threshold, it is determined that a tilt offset has occurred, and the label "tilt offset" is generated.

[0112] In some embodiments, the tag processing reference information includes the number of times the tag is marked corresponding to the event.

[0113] The above-mentioned determination of the label processing action corresponding to the event message based on the label processing reference information and the target label generation rule may include:

[0114] According to the label corresponding to the event message, the label marking times of the label are determined, and according to the comparison result of the label marking times of the label and the label marking times threshold, the label processing action corresponding to the event message is determined.

[0115] Exemplarily, the tag processing reference information may also include the number of times the same tag is marked.

[0116] Exemplarily, for any tag of any front-end device, the number of times the tag is marked can be counted.

[0117] Among them, for any label of any front-end device, when the front-end device changes from a state where the label is not marked to a state where the label is marked, the number of times the label is marked is increased by 1.

[0118] If the label marking times of the tag is not updated within the preset maximum update time (which can be set according to actual needs), it is reset to 0. Exemplarily, for the monitored event message, the tag corresponding to the event message can be determined, and then the label marking times of the tag can be determined, and the label processing action corresponding to the event message can be determined based on the comparison result of the label marking times and the label marking times threshold.

[0119] In an example, the above-mentioned determining the label processing action corresponding to the event message based on the comparison result of the label annotation times and the label annotation times threshold may include:

[0120] If the labeling times of the label is not less than the labeling times threshold, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the label generation rule;

[0121] The label corresponding to the label generation rule indicates that the event corresponding to the label has a high probability of occurrence.

[0122] For example, taking the road waterlogging event as an example, suppose a road waterlogging event was detected 10 days ago (for example, a road waterlogging event message was monitored), and the corresponding front-end device was labeled with a "road waterlogging" label, and the number of labelings increased by 1. Subsequently, the staff handled the road waterlogging, and no road waterlogging event message was received within the label expiration time, and the labeled "road waterlogging" label was also cancelled; but road waterlogging was detected again 5 days ago, and the number of "road waterlogging" labelings was 2, and then the staff handled the road waterlogging, and the labeled "road waterlogging" label was also cancelled; but road waterlogging occurred again today, and the number of "road waterlogging" labelings was 3. Assuming the labeling number threshold is 3, a "repeated road waterlogging" or "prone to road waterlogging" label can be generated (indicating that the probability of "road waterlogging" events occurring on this road is high).

[0123] In some embodiments, determining the label processing action corresponding to the event message based on the label processing reference information and the label processing rule may include:

[0124] When the label processing action corresponding to the event message is to mark the label corresponding to the target label generation rule, and the front-end device to which the event message belongs has a target label among the currently marked labels that conflict with the currently generated label, cancel the target label of the front-end device and mark the currently generated label for the front-end device.

[0125] For example, considering that in actual scenarios, there may be conflicts (or mutual exclusion) between different tags.

[0126] For example, taking rainfall as an example, labels such as "heavy rain", "moderate rain" and "light rain" are mutually exclusive labels, and for the same front-end device, as the actual situation changes, it may be labeled with the above different labels.

[0127] Accordingly, when it is determined in the above manner that a label needs to be marked for the front-end device based on the monitored event message, it can be determined whether there is a label (which can be called a target label) among the labels currently marked by the front-end device that conflicts with the currently generated label based on the currently generated label (i.e., the label corresponding to the target label generation rule) and the label currently marked by the front-end device.

[0128] In the case where a target tag exists, the target tag of the front-end device can be cancelled, and the front-end device can be labeled with a currently generated tag to avoid the same device being labeled with multiple conflicting tags.

[0129] In some embodiments, for any monitored event message, determining the corresponding label processing reference information may include:

[0130] For any monitored event message, determine the target label generation rule associated with the event message based on the association relationship between the event and the label generation rule;

[0131] According to the target label generation rule, determine the corresponding label processing reference information;

[0132] The label processing reference information and the label processing rule are used to determine the label processing action corresponding to the event message, including:

[0133] According to the label processing reference information and the target label generation rule, the label processing action corresponding to the event message is determined.

[0134] In the embodiment of the present application, corresponding label generation rules can be configured for events according to event characteristics, thereby generating an association relationship between events and label generation rules.

[0135] Exemplarily, the event characteristics may include one or more of the following information: the frequency of occurrence of the event, the value of a specific field in the event message corresponding to the event, the number of times the label corresponding to the event is marked, and the like.

[0136] Exemplarily, the association relationship between an event and a label generation rule may include an association relationship between an event code and a label generation rule.

[0137] The event code is used to identify a type of event.

[0138] For example, one type of event may be associated with one or more tag generation rules.

[0139] Exemplarily, different types of events may be associated with the same label generation rule.

[0140] For any monitored event message, the label generation rule (which may be referred to as the target label generation rule) associated with the event message may be determined based on the association relationship between the event and the label generation rule.

[0141] Exemplarily, for any monitored event message, the association relationship between the event and the label generation rule can be queried based on the event code in the event message to determine the target label generation rule associated with the event message.

[0142] It should be noted that, when the currently monitored event message is associated with multiple different target label generation rules, for any target label generation rule, the corresponding label processing action can be determined in the above manner, and its specific implementation is not repeated here.

[0143] In some embodiments, the device tag generation method provided by the embodiments of the present application may include:

[0144] According to the target tag information carried in the detected device query instruction, the front-end device whose tag matches the target tag information is queried.

[0145] Exemplarily, when the front-end device is labeled in the above manner, the user can query the front-end device according to the label as needed.

[0146] For example, in the device management interface, you can filter the corresponding devices by tags without having to click on each device to view the current screen.

[0147] In order to enable those skilled in the art to better understand the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described below with reference to specific examples.

[0148] In this embodiment, in order to realize dynamic generation of device tags, the following processing flow may be included:

[0149] 1. By collecting and analyzing events generated by equipment in the security field, a variety of label generation models are abstracted.

[0150] For example, the following six models can be abstracted:

[0151] Model 1: Within the time window t1 (i.e., the first time window mentioned above), the number of event reports is greater than or equal to n (i.e., the reporting number threshold mentioned above), and the front-end device is labeled with a label "the event occurred".

[0152] For example, considering that algorithm detection events usually use rolling time window statistical methods, such as exposed garbage monitoring, motor vehicle illegal parking monitoring, etc., it is possible to count the number of event reports within a period of time (i.e., the frequency of event occurrence) and label the front-end device based on the frequency of event occurrence.

[0153] Exemplarily, the time window t1 value needs to be determined according to the algorithm strategy and the event reporting frequency strategy; in addition, the reporting number threshold n can be determined according to the actual scenario.

[0154] Exemplarily, within the time window t1, when the number of event reports is less than n, the label is cancelled.

[0155] Model 2: Determine the labels to be marked based on one or more field values ​​in the event message.

[0156] For example, for meteorological data reported by sensors, they usually report event messages including meteorological data (such as temperature, humidity, rainfall, etc.) at regular intervals.

[0157] Taking rainfall as an example, labels can be annotated as follows:

[0158] 2.1. When the rainfall value in the rainfall reporting event message (hereinafter the same) is greater than or equal to n, the "heavy rain" label is marked.

[0159] 2.2. When the rainfall value is less than n and greater than or equal to m, mark it with the label "moderate rain".

[0160] 2.3. When the rainfall value is less than m and greater than 0, mark it with the label "light rain".

[0161] 2.4. When the rainfall value is equal to 0, cancel the previous label (if any) or do not label it.

[0162] For example, the values ​​of m and n can be determined based on empirical values.

[0163] Exemplarily, the above labels are mutually exclusive, that is, only one label can be applied at the same time.

[0164] Model 3: In the time window t2 (i.e., the second time window mentioned above), a field in the message is continuously greater than or less than a certain value, and is marked with the label "continuously maintain a certain state".

[0165] For example, still taking rainfall as an example, within the time window t2, the rainfall value is always greater than n, and a label of “continuous heavy rain” can be marked.

[0166] If the rainfall does not always exceed n within the time window t2, the "continuous heavy rain" label can be cancelled.

[0167] Model 4: By calculating or comparing one or more field values ​​in different event messages, a trend is determined and labeled.

[0168] Taking the water level detection event as an example, it is possible to determine whether the water level is increasing too fast by calculating the difference of the water level values ​​within the time window t3 (ie, the third time window mentioned above).

[0169] Exemplarily, for any water level detection event message monitored, the current water level value can be determined based on the value of the "water level" field in the water level detection event message, and the current water level value can be subtracted from the lowest water level value in the previous third time window. If the result is greater than or equal to the preset water level difference threshold, the "water level is rising too fast" label is marked.

[0170] Taking passenger flow events as an example, based on the passenger flow event messages received within the t3 time window (i.e., the fourth time window mentioned above), the new passenger flow can be counted by the method of number of people entering - number of people leaving, and the cumulative number of people within the t3 time window can be counted. When the cumulative number of people is greater than or equal to the preset number threshold (i.e., the above-mentioned passenger flow threshold), a "passenger flow surge" label is marked.

[0171] Exemplarily, if the above trend is not satisfied within the time range t, the trend label is cancelled.

[0172] Model 5: By counting the number of times the same label is applied, the model is labeled as “the event is prone to / repeatedly / frequently occur”.

[0173] Exemplarily, if a label expires and is then marked again after a specified time interval, it is counted as a repeated marking of the label. Then, by judging whether the number of repeated markings is greater than a specified value, it is determined whether the label is marked as an event that is easy / repeated / frequent to occur.

[0174] For example, if a road flooding incident occurred 10 days ago, the device was labeled with the label "road flooding", and the number of labelings increased by 1. Subsequently, government personnel dealt with the road flooding, and the label "road flooding" was cancelled. However, if the road flooding occurred again 5 days ago, the number of labelings for "road flooding" increased by 1 to 2. Subsequently, government personnel dealt with the road flooding, and the label "road flooding" was cancelled. However, if the road flooding occurred again today, the number of labelings for "road flooding" increased by 1 to 3. If the number of labelings is greater than or equal to 3, it is labeled "repeated road flooding" or "prone to road flooding".

[0175] Model 6: Subtract a field from the previous event when the field of the current event is greater than or equal to n, and get the corresponding label.

[0176] For example, taking the tilt detection event as an example, the value of the tilt field in the current tilt detection event message is subtracted from the value of the tilt field in the last tilt detection event message reported by the same front-end device. When the difference is greater than the preset tilt difference threshold, it is determined that a tilt offset has occurred, and the corresponding front-end device is marked with a "tilt offset" label.

[0177] 2. Based on the characteristics of the event and the label model abstracted in step 1, configure label generation rules for the event.

[0178] For example, the configuration items that need to be configured for label generation rules corresponding to different models are not exactly the same:

[0179] For model 1, you need to specify the name of the generated label, time window t1 (i.e. the first time window mentioned above), reporting number threshold n, and label expiration time;

[0180] Exemplarily, for any label set for a front-end device according to the solution provided in the embodiment of the present application, if the labeling time of the label reaches the preset label expiration time, the label of the front-end device can be cancelled. Exemplarily, for any front-end device, if it is determined that a label needs to be marked for the front-end device, but the front-end device has currently marked the label, the label marking time of the label can be refreshed, and the label expiration time can be determined based on the refreshed label marking time.

[0181] For model 2, you need to specify the name of the generated label, the field position in the event message that needs to be judged (that is, the position of the specific field), the threshold for generating labels corresponding to the specific field value, the threshold for canceling labels corresponding to the specific field value, and the label expiration time.

[0182] For model 3, you need to specify the name of the generated label, time window t2 (i.e., the second time window), the location of the specific field, the threshold for generating labels corresponding to the specific field value, the threshold for canceling labels corresponding to the specific field value, and the label expiration time.

[0183] For model 4, you need to specify the name of the generated label, the location of the specific field, the time window t3 (i.e., the third time window), the threshold for generating labels corresponding to the specific field value, the threshold for canceling labels corresponding to the specific field value, and the label expiration time.

[0184] For model 5, you need to specify the name of the generated label, the threshold of the number of times the same label is annotated, and the label expiration time;

[0185] For model 6, you need to specify the name of the generated label, the location of the specific field, the threshold of the field of the current event minus the field of the previous event, and the label expiration time.

[0186] 3. Generate a label analysis task according to the label generation rules configured in step 2, and start the label analysis task to generate corresponding labels.

[0187] Exemplarily, based on the specified event consumption queue and the configured label generation rules, a label analysis task is assembled and the label generation task is started.

[0188] During the execution of the label generation task, events can be obtained from the message queue, and the events can be analyzed according to the label generation rules. If the label configuration rules are met, labels for corresponding devices are generated, or labels for corresponding devices are canceled.

[0189] 4. Based on the analysis results of step 3, label or unlabel the corresponding devices.

[0190] The implementation flow chart of dynamic generation of device tags can be as follows: Figure 2 shown.

[0191] 5. In the device management interface, you can filter out the corresponding devices through the generated tags without clicking on each device to view the current screen.

[0192] The method provided by the present application is described above. The device provided by the present application is described below:

[0193] See also Figure 3 , is a schematic diagram of the structure of a device tag generating apparatus provided in an embodiment of the present application, such as Figure 3 As shown, the device tag generating device may include:

[0194] The first determining unit 310 is configured to determine label processing reference information for any monitored event message;

[0195] The second determining unit 320 is configured to determine the label processing action corresponding to the event message according to the label processing reference information and the label processing rule;

[0196] Among them, the label processing rules include label generation rules and label cancellation rules.

[0197] The second determining unit 320 is specifically configured to:

[0198] Determine whether the label processing reference information satisfies the label generation rule. If so, mark the front-end device to which the event message belongs with a label corresponding to the label generation rule;

[0199] Determine whether the label processing reference information satisfies the label cancellation rule, and if so, cancel the label corresponding to the label generation rule for the front-end device to which the event message belongs. In some embodiments, the label processing reference information includes the frequency of event occurrence;

[0200] The second determination unit 320 is specifically configured to determine the number of times the front-end device reports events of the event type within the first time window based on the front-end device to which the event message belongs and the event type corresponding to the event message; and determine the label processing action corresponding to the event message based on a comparison result of the number of times the front-end device reports events of the event type within the first time window and a reporting number threshold.

[0201] In some embodiments, the second determination unit 320 is specifically configured to mark the front-end device with a label corresponding to the label generation rule if the number of times the front-end device reports the event of the event type within the first time window is not less than the reporting number threshold, then the label generation rule is satisfied;

[0202] If the number of times the front-end device reports events of the event type within the first time window is less than the reporting number threshold, the label cancellation rule is met, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0203] The label corresponding to the label generation rule represents the occurrence of the event corresponding to the event type.

[0204] In some embodiments, the tag processing reference information includes the value of a specific field in the event message;

[0205] The second determining unit 320 is specifically configured to determine a label processing action corresponding to the event message according to a comparison result between a value of a specific field in the event message and a preset threshold;

[0206] or,

[0207] According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the comparison result between the value of a specific field in the event message of the event type reported by the front-end device within the second time window and a preset threshold, and determine the label processing action corresponding to the event message according to the comparison result;

[0208] or,

[0209] According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the comparison result between the value of a specific field in the event message and the target value, and determine the label processing action corresponding to the event message according to the comparison result; wherein the target value is the minimum or maximum value of the value of a specific field in the event message of the event type reported by the front-end device within the previous third time window;

[0210] or,

[0211] Determine, based on the front-end device to which the event message belongs and the event type to which the event message corresponds, the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, and determine, based on the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, the label processing action corresponding to the event message;

[0212] or,

[0213] Based on the front-end device to which the event message belongs and the event type corresponding to the event message, determine the value of a specific field in the event message, compare it with the value of a specific field in the event message of this event type last reported by the front-end device, and determine the label processing action corresponding to the event message based on the comparison result.

[0214] In some embodiments, the preset threshold includes at least one threshold range;

[0215] The second determination unit 320 is specifically configured to, if the value of the specific field in the event message is within any threshold range of the at least one threshold range, satisfy the label generation rule, and mark the front-end device with a label corresponding to the threshold range in the label corresponding to the label generation rule; if the value of the specific field in the event message is not within any threshold range of the at least one threshold range, satisfy the label cancellation rule, and cancel the label corresponding to the label generation rule for the front-end device;

[0216] or,

[0217] The preset threshold includes at least one threshold range;

[0218] The second determination unit 320 is specifically configured to satisfy the label generation rule and label the front-end device with a label corresponding to the threshold range in the label corresponding to the label generation rule if the values ​​of the specific fields in the event message of the event type reported by the front-end device within the second time window are all within the same threshold range; if the values ​​of the specific fields in the event message of the event type reported by the front-end device within the second time window are not within the same threshold range, the label cancellation rule is satisfied and the label corresponding to the label generation rule is cancelled for the front-end device;

[0219] Among the labels corresponding to the label generation rule, the labels corresponding to any threshold range represent the continuous occurrence of the event corresponding to the threshold range;

[0220] or,

[0221] The second determination unit 320 is specifically configured to, if the target value is the minimum value, the value of the specific field in the event message is less than the target value, and the difference between the two is not less than the preset threshold, or, if the target value is the maximum value, the value of the specific field in the event message is greater than the target value, and the difference between the two is not less than the preset threshold, then the label generation rule is satisfied, and the label corresponding to the label generation rule is marked for the front-end device; otherwise, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0222] The label corresponding to the label generation rule indicates that the event of the event type meets a specific trend;

[0223] or,

[0224] The second determination unit 320 is specifically configured to determine the sum of the difference values ​​in the fourth time window according to the difference between the values ​​of two specific fields in the event message of the event type reported by the front-end device in the fourth time window; if the sum of the difference values ​​in the fourth time window is not less than a preset threshold, the label generation rule is satisfied, and the label corresponding to the label generation rule is marked for the front-end device; if the sum of the difference values ​​in the fourth time window is less than the preset threshold, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0225] The label corresponding to the label generation rule indicates that the event of the event type meets a specific trend;

[0226] or,

[0227] The second determination unit 320 is specifically configured to, if the value of the specific field in the event message minus the value of the specific field in the event message of the event type last reported by the front-end device, the difference obtained is greater than a preset threshold, then the label generation rule is satisfied, and the front-end device is marked with a label corresponding to the label generation rule; if the value of the specific field in the event message minus the value of the specific field in the event message of the event type last reported by the front-end device, the difference obtained is not greater than the preset threshold, then the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device;

[0228] The label corresponding to the label generation rule represents the occurrence of the event corresponding to the event type.

[0229] In some embodiments, the tag processing reference information includes the number of times the tag is marked corresponding to the event;

[0230] The second determining unit 320 is specifically configured to determine the labeling times of the label according to the label corresponding to the event message, and determine the label processing action corresponding to the event message according to the comparison result of the labeling times of the label and the labeling times threshold.

[0231] In some embodiments, the second determining unit 320 is specifically configured to, if the number of times the tag is marked is not less than the marking number threshold, satisfy the tag generation rule, and mark the front-end device with a tag corresponding to the tag generation rule;

[0232] The tag corresponding to the tag generation rule indicates that the event corresponding to the tag has a high probability of occurrence.

[0233] In some embodiments, the second determination unit 320 is specifically configured to cancel the target label of the front-end device and label the currently generated label for the front-end device when the label processing action corresponding to the event message is to label a label corresponding to the target label generation rule, and when the currently labeled labels of the front-end device to which the event message belongs contain a target label that conflicts with the currently generated label.

[0234] In some embodiments, the first determination unit 310 is specifically configured to determine, for any monitored event message, a target tag generation rule associated with the event message according to the association relationship between the event and the tag generation rule; and determine corresponding tag processing reference information according to the target tag generation rule;

[0235] The second determining unit 320 is specifically configured to determine the label processing action corresponding to the event message according to the label processing reference information and the target label generation rule.

[0236] In some embodiments, Figure 4 As shown, the device tag generating apparatus may further include:

[0237] The query unit 330 is configured to query the front-end device whose tag matches the target tag information according to the target tag information carried in the detected device query instruction.

[0238] See also Figure 5 , is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. The electronic device may include a processor 501, a communication interface 502, a memory 503 and a communication bus 504. The processor 501, the communication interface 502 and the memory 503 communicate with each other through the communication bus 504. Among them, the memory 503 stores a computer program; the processor 501 can execute the device tag generation method described above by executing the program stored in the memory 503.

[0239] The memory 503 mentioned herein may be any electronic, magnetic, optical or other physical storage device that may contain or store information, such as executable instructions, data, etc. For example, the memory 503 may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as optical disk, DVD, etc.), or similar storage medium, or a combination thereof.

[0240] The present application also provides a non-transitory machine-readable storage medium storing a computer program, such as Figure 5 The computer program may be stored in the memory 503. Figure 5The processor 501 in the electronic device shown executes to implement the device tag generating method described above.

[0241] The present application also provides a computer program stored in a non-transitory machine-readable storage medium, such as Figure 5 The memory 503 in the memory, and when the processor executes the computer program, it prompts the processor 501 to execute the device tag generation method described above.

Claims

1. A method for generating a device tag, characterized in that: include: For any event message monitored, determine the label processing reference information; Determine the label processing action corresponding to the event message based on the label processing reference information and the label processing rule; wherein the label processing reference information is used to compare with the value indicated by the label processing rule, and the comparison result is used to determine the label processing action corresponding to the event message; the label processing reference information includes one or more of the frequency of event occurrence, the value of a specific field in the event message, and the number of times the label is marked corresponding to the event; The label processing rule includes a label generation rule and a label cancellation rule. The label processing action corresponding to the event message is determined based on the label processing reference information and the label processing rule, including: Determine whether the label processing reference information satisfies the label generation rule, and if so, mark the front-end device to which the event message belongs with a label corresponding to the label generation rule; It is determined whether the label processing reference information satisfies the label cancellation rule. If so, the label corresponding to the label generation rule is cancelled for the front-end device to which the event message belongs.

2. The method according to claim 1, characterized in that The tag processing reference information includes the frequency of event occurrence; Determining the label processing action corresponding to the event message according to the label processing reference information and the label processing rule includes: According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the number of times the front-end device reports events of the event type within the first time window; The label processing action corresponding to the event message is determined based on the comparison result of the number of times the front-end device reports events of the event type within the first time window and the reporting number threshold.

3. The method according to claim 2, characterized in that Determining a label processing action corresponding to the event message according to a comparison result of the number of times the front-end device reports the event type within the first time window and the reporting number threshold, including: If the number of times the front-end device reports events of the event type within the first time window is not less than the reporting number threshold, the label generation rule is satisfied, and the front-end device is marked with a label corresponding to the label generation rule; If the number of times the front-end device reports events of the event type within the first time window is less than the reporting number threshold, the label cancellation rule is met, and the label corresponding to the label generation rule is cancelled for the front-end device; The label corresponding to the label generation rule represents the occurrence of the event corresponding to the event type.

4. The method according to claim 1, characterized in that: The tag processing reference information includes the value of a specific field in the event message; Determining the label processing action corresponding to the event message according to the label processing reference information and the label processing rule includes: Determine the label processing action corresponding to the event message based on the comparison result between the value of a specific field in the event message and a preset threshold; or, According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the comparison result between the value of a specific field in the event message of the event type reported by the front-end device within the second time window and a preset threshold, and determine the label processing action corresponding to the event message according to the comparison result; or, According to the front-end device to which the event message belongs and the event type corresponding to the event message, determine the comparison result between the value of a specific field in the event message and the target value, and determine the label processing action corresponding to the event message according to the comparison result; wherein the target value is the minimum or maximum value of the value of a specific field in the event message of the event type reported by the front-end device within the previous third time window; or, Determine, based on the front-end device to which the event message belongs and the event type to which the event message corresponds, the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, and determine, based on the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, the label processing action corresponding to the event message; or, Based on the front-end device to which the event message belongs and the event type corresponding to the event message, determine the value of a specific field in the event message, compare it with the value of a specific field in the event message of this event type last reported by the front-end device, and determine the label processing action corresponding to the event message based on the comparison result.

5. The method according to claim 4, characterized in that The preset threshold includes at least one threshold range; The step of determining a label processing action corresponding to the event message based on a comparison result between a value of a specific field in the event message and a preset threshold value includes: If the value of the specific field in the event message is within any threshold range of the at least one threshold range, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the threshold range among the labels corresponding to the label generation rule; If the value of the specific field in the event message is not within any threshold range of the at least one threshold range, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device; or, The preset threshold includes at least one threshold range; Determining a label processing action corresponding to the event message according to a comparison result between a value of a specific field in the event message of the event type reported by the front-end device within the second time window and a preset threshold, including: If the values ​​of specific fields in the event messages of the event type reported by the front-end device within the second time window are all within the same threshold range, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the threshold range among the labels corresponding to the label generation rule; If the value of a specific field in the event message of the event type reported by the front-end device within the second time window is not within the same threshold range, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device; Among the labels corresponding to the label generation rule, the labels corresponding to any threshold range represent the continuous occurrence of the event corresponding to the threshold range; or, According to the comparison result between the value of a specific field in the event message and the target value, the label processing action corresponding to the event message is determined, including: If the target value is the minimum value, the value of the specific field in the event message is less than the target value, and the difference between the two is not less than the preset threshold, or the target value is the maximum value, the value of the specific field in the event message is greater than the target value, and the difference between the two is not less than the preset threshold, then the label generation rule is satisfied, and the front-end device is marked with a label corresponding to the label generation rule; Otherwise, if the label cancellation rule is met, the label corresponding to the label generation rule is cancelled for the front-end device; The label corresponding to the label generation rule indicates that the event of the event type meets a specific trend; or, The determining, according to the value of a specific field in the event message of the event type reported by the front-end device within the fourth time window, a label processing action corresponding to the event message includes: Determine the sum of the differences within the fourth time window according to the difference between the values ​​of two specific fields in the event message of the event type reported by the front-end device within the fourth time window; If the sum of the differences within the fourth time window is not less than a preset threshold, the label generation rule is satisfied, and a label corresponding to the label generation rule is marked on the front-end device; If the sum of the differences within the fourth time window is less than a preset threshold, the label cancellation rule is satisfied, and the label corresponding to the label generation rule is cancelled for the front-end device; The label corresponding to the label generation rule indicates that the event of the event type meets a specific trend; or, According to the comparison result of the value of a specific field in the event message and the value of a specific field in the event message of the event type reported by the front-end device last time, the label processing action corresponding to the event message is determined, including: If the value of the specific field in the event message minus the value of the specific field in the event message of the event type reported by the front-end device last time, the difference is greater than the preset threshold, then the label generation rule is met, and the front-end device is marked with a label corresponding to the label generation rule; If the value of the specific field in the event message minus the value of the specific field in the event message of the event type reported by the front-end device last time, the difference is not greater than the preset threshold, then the label cancellation rule is met, and the label corresponding to the label generation rule is cancelled for the front-end device; The label corresponding to the label generation rule represents the occurrence of the event corresponding to the event type.

6. The method according to claim 1, characterized in that The label processing reference information includes the number of label markings corresponding to the event; Determining the label processing action corresponding to the event message according to the label processing reference information and the label processing rule includes: According to the label corresponding to the event message, the label marking times of the label are determined, and according to the comparison result of the label marking times of the label and the label marking times threshold, the label processing action corresponding to the event message is determined.

7. The method according to claim 6, characterized in that The step of determining the label processing action corresponding to the event message according to the comparison result of the label marking times and the label marking times threshold includes: If the labeling times of the label is not less than the labeling times threshold, the label generation rule is satisfied, and the front-end device is labeled with a label corresponding to the label generation rule; The tag corresponding to the tag generation rule indicates that the event corresponding to the tag has a high probability of occurrence.

8. The method according to any one of claims 1 to 7, characterized in that: The step of determining corresponding label processing reference information for any monitored event message includes: For any monitored event message, determine the target label generation rule associated with the event message based on the association relationship between the event and the label generation rule; Determine corresponding label processing reference information according to the target label generation rule; Then, according to the label processing reference information and the label processing rule, determining the label processing action corresponding to the event message includes: The label processing action corresponding to the event message is determined according to the label processing reference information and the target label generation rule.

9. A device label generation device, characterized in that: include: A first determining unit is configured to determine label processing reference information for any monitored event message; A second determination unit is configured to determine the label processing action corresponding to the event message based on the label processing reference information and the label processing rule; wherein the label processing reference information is used to compare with the value indicated by the label processing rule, and the comparison result is used to determine the label processing action corresponding to the event message; the label processing reference information includes one or more of the frequency of event occurrence, the value of a specific field in the event message, and the number of label annotations corresponding to the event; The label processing rules include label generation rules and label cancellation rules. The second determining unit is specifically configured to: Determine whether the label processing reference information satisfies the label generation rule, and if so, mark the front-end device to which the event message belongs with a label corresponding to the label generation rule; It is determined whether the label processing reference information satisfies the label cancellation rule. If so, the label corresponding to the label generation rule is cancelled for the front-end device to which the event message belongs.

10. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; A processor, configured to implement the method according to any one of claims 1 to 8 when executing a program stored in a memory.

Images