Alarm method based on multi-technology fusion and perimeter security system

Abstract

The invention provides an alarm method based on multi-technology fusion and a perimeter security system, which can reduce missing alarm and false alarm caused by animal activity and environmental interference, improve alarm accuracy and enhance accuracy and reliability of the system. The method comprises the steps that when a first detection result of core detection equipment is received for the first time, an event attribute set containing state information of rechecking equipment and the type of the first detection result is generated, and the initial type of an event corresponding to the event attribute set is set as early warning. And if the event attribute set is not updated, triggering a corresponding alarm process according to the initial type of the event. And when the event attribute set is updated, if the event attribute set has the type of the second detection result of the rechecking equipment, updating the type of the event according to the type of the first detection result and the type of the second detection result. And if the type of the second detection result reported by the rechecking device does not exist in the event attribute set, updating the type of the event based on the running state of the rechecking device and the type of the first detection result.

Description

Technical Field

[0001] This application relates to the field of perimeter security technology, and in particular to an alarm method and perimeter security system based on multi-technology fusion. Background Technology

[0002] Perimeter security systems are a key technology system applied to the security protection of physical boundaries. They achieve alarm and proactive prevention of illegal intrusion by monitoring boundary areas such as walls, fences, and entrances / exits in real time. Perimeter security systems are widely used in airports, industrial parks, and other locations with high security requirements.

[0003] Currently, perimeter security systems primarily rely on single detection technologies for intrusion detection. If the detection indicates an intrusion, the system will issue an alarm. These technologies include infrared detection, electronic fences, vibration fiber optic detection, and microwave detection. However, perimeter security systems relying on single detection technologies are susceptible to environmental interference in practical applications. For example, microwave detection, electronic fences, and vibration fiber optics are vulnerable to severe weather and electromagnetic interference, while infrared detection is susceptible to interference from animal activity. This can lead to a higher false alarm rate or an increased risk of missed alarms, affecting the system's reliability and usability.

[0004] Therefore, there is an urgent need for an alarm method that can improve the accuracy of alarms, thereby enhancing the reliability and practicality of perimeter security systems. Summary of the Invention

[0005] This application provides an alarm method and perimeter security system based on multi-technology fusion, which can accurately determine the type of event, thereby precisely triggering the corresponding alarm process, reducing missed alarms and false alarms caused by animal activities and environmental interference, improving alarm accuracy, and enhancing the accuracy and reliability of the perimeter security system.

[0006] Firstly, a multi-technology fusion-based alarm method is provided, applied to a backend management device. This backend management device is included in a perimeter security system, which also includes a core detection device deployed in the target defense zone and at least one verification device. The core detection device and the at least one verification device employ different detection technologies. The method includes:

[0007] If the first detection result of the intrusion behavior is received from the core detection device for the first time, an event attribute set corresponding to the target defense zone is generated. The event corresponding to the event attribute set is the response of the background management device to the intrusion behavior. The event attribute set is used to record and update the first detection result reported by the core detection device and the status information of each verification device. The first detection result includes the type of the first detection result. The type of event and the type of the first detection result include warning and alarm. The intrusion risk level corresponding to the warning is lower than the intrusion risk level corresponding to the alarm. The status information indicates whether the verification device is operating normally.

[0008] The initial type of the event is determined to be an alert;

[0009] If the event attribute set is updated, and the event attribute set also records the second detection result reported by the verification device for the intrusion behavior and the type of the second detection result, and the type of the second detection result is alarm, then the event type is updated according to the type of the first detection result and the type of the second detection result in the updated event attribute set;

[0010] If the event attribute set is updated and the event attribute set does not record the type of the second detection result reported by the verification device for the intrusion behavior, the type of the event is updated according to the type of the first detection result in the updated event attribute set and the status information of each verification device;

[0011] The corresponding alarm process is triggered based on the type of event.

[0012] In one feasible design, the event type is updated based on the type of the first detection result in the updated event attribute set and the status information of each verification device, including:

[0013] If the status information of each verification device indicates that the verification device is not operating properly, the type of the first detection result in the updated event attribute set is determined as the event type, and the event type is updated.

[0014] If at least one verification device contains status information indicating that the verification device is operating normally, the update event type is warning.

[0015] In one feasible design, the event type is updated based on the types of the first and second probe results in the updated event attribute set, including:

[0016] If the types of the first and second detection results in the updated event attribute set are the same, the updated event type is alarm.

[0017] In one feasible design, the event type is updated based on the types of the first and second probe results in the updated event attribute set, including:

[0018] If the types of the first and second detection results in the updated event attribute set are inconsistent, the type of the updated event is an alert.

[0019] In a feasible design, the methods include:

[0020] If a second detection result is received from the verification device regarding the intrusion behavior, the defense zone associated with the verification device is determined;

[0021] Determine if the defense zone corresponds to an event attribute set;

[0022] If the defense zone has an event attribute set, determine that the type of the second detection result is an alarm, and add the second detection result and its corresponding type to the event attribute set.

[0023] In a feasible design, the methods include:

[0024] If the defense zone does not have a corresponding event attribute set, discard the second detection result.

[0025] In one feasible design, the core detection equipment is an intelligent detection cable based on microwave detection technology, and the detection technology used by at least one verification device is determined according to the environmental conditions of the target defense zone.

[0026] In a feasible design, an alarm process is triggered based on the type of event, including:

[0027] If the event type is alarm, activate the audible and visual alarm;

[0028] If the event type is an alert, a notification is sent to the administrator to alert them of potential intrusion into the target zone.

[0029] In a feasible design, determining the zones associated with the verification equipment includes:

[0030] Based on the Internet Protocol address of the verification device in the second detection result, the associated defense zone of the verification device is determined by querying the mapping table, which contains the association between the verification device and the defense zone.

[0031] Secondly, a perimeter security system is provided, including a back-end management device, a core detection device deployed in the target defense zone, and at least one verification device, wherein the core detection device and at least one verification device use different detection technologies;

[0032] The core detection equipment is used to report the first detection results of intrusion behavior to the back-end management equipment in real time;

[0033] The verification equipment is used to report the second detection results of intrusion behavior to the background management equipment in real time;

[0034] The background management device is used to generate an event attribute set corresponding to the target defense zone if it receives the first detection result of the intrusion behavior reported by the core detection device for the first time. The event attribute set is the response of the background management device to the intrusion behavior. The event attribute set is used to record and update the first detection result reported by the core detection device and the status information of each verification device. The first detection result includes the type of the first detection result. The type of event and the type of the first detection result include warning and alarm. The intrusion risk level corresponding to the warning is lower than the intrusion risk level corresponding to the alarm. The status information indicates whether the verification device is operating normally.

[0035] The backend management equipment is also used to determine the initial type of an event as an alert;

[0036] The background management device is also used to update the event type if the event attribute set is updated, and the event attribute set also records the second detection result reported by the verification device for the intrusion behavior and the type of the second detection result, where the type of the second detection result is alarm;

[0037] The background management device is also used to update the event type based on the type of the first detection result in the updated event attribute set and the status information of each verification device if the event attribute set is updated and the event attribute set does not record the type of the second detection result reported by the verification device for the intrusion behavior.

[0038] The back-end management equipment is also used to trigger corresponding alarm processes based on the type of event.

[0039] This application embodiment achieves hierarchical alarm decision-making by fusing multi-source data from core detection devices and verification devices employing different detection technologies, combined with a dynamically updated event attribute set. Upon receiving the first detection result from the core detection device, the method generates an event attribute set containing the status information of the verification device and the type of the first detection result, and sets the initial type of the event corresponding to the event attribute set as a warning. If the event attribute set is not updated, a corresponding low-level alarm process is triggered based on the initial type of the event – ​​warning, achieving an early warning effect for potential intrusion behaviors. When the event attribute set is updated, if the event attribute set contains the type of a second detection result from a verification device, conflict verification is performed by combining the types of the first and second detection results to improve the accuracy of event type determination. An accurate event type helps initiate subsequent alarm processes of corresponding warning levels, thereby improving alarm accuracy and reducing false alarm rates. If the event attribute set does not contain the type of a second detection result reported by a verification device, the event type is updated based on the operating status of the verification device and the type of the first detection result, avoiding misjudgment of the event type due to verification device anomalies, further reducing the false alarm rate.

[0040] In summary, this application utilizes multiple detection devices capable of adapting to various environmental conditions and employing diverse detection technologies to work collaboratively, obtaining multi-source heterogeneous data that includes detection results from the core detection device, detection results from the verification device, and status information of the verification device. Based on this multi-source heterogeneous data, joint decision-making accurately determines the type of event, thereby precisely triggering the corresponding alarm process. This reduces missed and false alarms caused by animal activity and environmental interference, enhancing the accuracy and reliability of the perimeter security system. Attached Figure Description

[0041] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic flowchart illustrating an example of an alarm method based on multi-technology fusion provided in an exemplary embodiment of this application;

[0043] Figure 2 This is a schematic diagram of an exemplary perimeter security system provided in an exemplary embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0045] In practical applications, relying solely on a single detection technology can be affected by environmental interference or complex intrusion behaviors, leading to low alarm accuracy and impacting the reliability and practicality of perimeter security systems. To address this, this application proposes an alarm method and perimeter security system based on multi-technology fusion. It constructs a multimodal perception and collaborative decision-making mechanism by using core detection equipment as the foundation and verification equipment employing different detection technologies as an auxiliary tool. Using this mechanism, the proposed solution can select appropriate verification equipment based on different environmental conditions to adapt to complex scenario requirements. When intrusion behavior or environmental interference is detected, the backend management device can comprehensively analyze the detection results of the core detection equipment and the verification equipment for joint judgment, significantly reducing the false alarm rate and improving the environmental adaptability of the perimeter security system.

[0046] It should be noted that the core detection and verification equipment in this application can continuously report detection results multiple times in response to intrusion behavior.

[0047] The following is a description of the technical terms used in this application:

[0048] Event: The response of the backend management device to an intrusion attempt includes three states: new status, updated status, and terminated status.

[0049] New Status: After the core detection device detects an intrusion for the first time, it reports the detection result to the backend management device, triggering the backend management device to generate the event attribute set corresponding to the event. In other words, the event is in the new status until the core detection device reports the detection result a second time.

[0050] Updated State: The state change during the event's continuation. In other words, the event is in the updated state after the core detection device first reports the detection result and before the last report. In the updated state, the core detection device or verification device will continuously report new detection results, and the background management device will update the event attribute set based on these results to reflect the latest state of the intrusion behavior.

[0051] Termination Status: The intrusion activity has ended. In other words, the event is in the termination status after the core detection device reports its detection results for the last time. The last detection result reported by the core detection device usually includes a termination flag for the intrusion activity. Based on this, the background management device determines that the event is in the termination status and performs other processing such as clearing the event attribute set corresponding to the event.

[0052] Events are categorized into two types: warnings and alarms. Warnings correspond to a lower intrusion risk level than alarms; a higher intrusion risk level indicates a greater threat from the intrusion. In this application, warning-type events correspond to potential intrusion activities, and the backend management device provides an initial alert for such events. Alarm-type events correspond to confirmed intrusion activities, and the backend management device initiates the corresponding level of alarm procedures, such as audible and visual alarms. This application distinguishes between warnings and alarms based on intrusion risk levels, without limiting the specific method of classifying intrusion risk levels. Therefore, the level of alert for a warning-type event is lower than that for an alarm-type event.

[0053] Zone: An independent monitoring area defined by the back-end management equipment, with the zone as the smallest management unit for events.

[0054] Core Detection Equipment: The primary reference equipment for the backend management system to respond to intrusion attempts. In this embodiment, a smart detection cable based on microwave detection technology is used as the core detection equipment. The specific detection technology adopted can be selected according to actual needs. The smart detection cable based on microwave detection technology has multiple built-in microwave transceivers, forming a microwave field covering the physical fence through continuous transmission and reception of microwave signals. The coverage area of ​​this field can extend to the area below and around the physical fence, forming a three-dimensional protective space. When an intruder enters the microwave field, it changes the propagation path and field strength distribution of the microwave signal. The monitoring server analyzes the changes in microwave signal waveform in real time, and judges the physical attributes of the intruder, such as mass and speed, through the microwave signal distortion mode, distinguishing between personnel, animals, or environmental interference (such as falling leaves, rainfall, etc.), thereby generating detection results including the type of detection result, defense zone identification, physical coordinates of the intrusion location, the subject of the intrusion, and timestamp.

[0055] First detection result: The detection results of intrusion behavior reported by the core detection equipment, which usually include the type of first detection result, the defense zone identifier, the physical coordinates of the intrusion location, the subject of the intrusion behavior, the image, the timestamp, and other information.

[0056] Verification equipment: Auxiliary detection equipment that works in conjunction with the core detection equipment to provide multi-source data verification. Examples include thermal imagers and video analysis terminals. To overcome the potential performance limitations of the core detection equipment under specific environmental conditions, this application employs verification equipment with different detection technologies than the core detection equipment. By utilizing a cross-verification mechanism of multi-source sensing data, it significantly improves alarm accuracy and system reliability. This application may employ one or more verification devices. When multiple verification devices are used, they may employ the same or different detection technologies, but all must be different from the detection technology of the core detection equipment.

[0057] The second detection result: the detection results reported by the verification device for intrusion behavior, which usually include Internet Protocol address, physical coordinates of the intrusion location, subject of the intrusion behavior, image, timestamp and other information.

[0058] Based on the above explanation, the following describes an exemplary deployment process for a perimeter security system:

[0059] (1) Install core detection equipment and install supporting software system on background management equipment.

[0060] (2) Divide the physical defense zones and complete the parameter configuration of the software system so that each defense zone can be monitored.

[0061] (3) Deploy at least one verification device. The core detection device and at least one verification device use different detection technologies.

[0062] (4) Add the verification device information to the software system and complete the registration. The added verification device information includes Internet Protocol address, port, username, password, etc. The background management device can communicate with the verification device through the standardized communication interface provided by the verification device manufacturer based on the verification device information to realize real-time collection of detection results and working status. The software system is installed on the background management device.

[0063] (5) Bind the verification device to the corresponding defense zone and generate a mapping table. The mapping table contains the association between the verification device and the defense zone.

[0064] In one feasible design, the core detection equipment is an intelligent detection cable based on microwave detection technology, and the detection technology used by at least one verification device is determined according to the environmental conditions of the target defense zone.

[0065] For example, in the case of low light or low temperature conditions in the target defense zone, at least one verification device uses infrared thermal imaging technology for detection; in the case of good light conditions in the target defense zone, at least one verification device uses image recognition (such as image recognition based on video) for detection.

[0066] For example, in order to adapt to changes in environmental conditions, when there are multiple verification devices, different verification devices can adopt different detection technologies. For example, at least one verification device may include a verification device using infrared thermal imaging technology and a verification device using image recognition technology, so as to ensure efficient detection under different lighting and temperature conditions. This realizes the integration of multiple sensing technologies such as microwave detection, image recognition, and thermal imaging, and improves the comprehensiveness of intrusion detection.

[0067] Because intelligent detection cables based on microwave detection technology can accurately detect, locate, classify, and track the intruders, generating initial detection results in real time, selecting intelligent detection cables as the core detection device ensures the accuracy and real-time performance of the initial detection results. Furthermore, by determining the detection technology used by at least one verification device based on the environmental conditions of the target zone, the shortcomings of the core detection device in certain environments can be compensated for missed detections. This application enhances the comprehensiveness and environmental adaptability of the perimeter security system, ensuring the accuracy of alarms.

[0068] Based on the perimeter security system deployed above, the following will combine... Figure 1 This application describes an alarm method based on multi-technology fusion, which is applied to a backend management device and includes:

[0069] S110, if the first detection result for intrusion behavior is received from the core detection device for the first time, generate the event attribute set corresponding to the target defense zone.

[0070] The first detection result includes the type of the first detection result. The event attribute set corresponds to the perimeter security system's response to intrusion behavior. The event attribute set is used to record and update the first detection results reported by the core detection device and the status information of each verification device. The first detection result includes the type of the first detection result. The types of events and the types of first detection results include warnings and alarms. The intrusion risk level corresponding to a warning is lower than that corresponding to an alarm. The status information indicates whether the verification device is operating normally.

[0071] For example, if the type of the event or the first detection result is a warning, it means that there is a potential intrusion; if the type of the event or the first detection result is an alarm, it means that there is a confirmed intrusion. The backend management device can trigger different alarm processes according to different event types.

[0072] Once the backend management device receives the first detection result for intrusion behavior reported by the core detection device, it triggers the generation of an event attribute set, which means that a new event has been added. That is, one event corresponds to one event attribute set.

[0073] For example, the event attribute set is also used to record and update at least one second detection result reported by the verification device in response to the intrusion behavior, as well as the type of at least one second detection result. The type of the second detection result in the event attribute set can correspond one-to-one with the second detection result, or multiple second detection results can share a single type (because the type of the second detection result is only "alarm," the subsequent judgment process in this embodiment only depends on whether a type of second detection result exists, and is unrelated to the number of types of second detection results).

[0074] For example, "normal operation of the verification device" means that the working status reported by the verification device indicates that it is online and capable of identifying intrusion behavior. The working status can be reported periodically by the verification device to the backend management device, and does not necessarily need to be reported synchronously with the second detection results.

[0075] For example, malfunction of the verification device refers to the verification device being offline, or the verification device reporting an operational status indicating that it is unable to identify intrusion behavior. Specifically, if the backend management device does not receive an operational status report from the verification device for a period of time, the verification device is determined to be offline.

[0076] It should be noted that each time the backend management device receives a new first detection result, it will update the first detection result in the event attribute set; each time it receives a new second detection result reported by the verification device, it will update the second detection result of the corresponding verification device in the event attribute set, as well as update the type of the second detection result; each time it receives a work status report from the verification device, it will update the status information of the corresponding verification device in the event attribute set.

[0077] It should be understood that this application embodiment does not limit whether the reporting frequencies of the core detection device and the verification device are consistent. In fact, the core detection device and the verification device perform intrusion detection independently, and when they report depends on their respective settings. It is also possible that after the core detection device reports the first detection result, the verification device does not detect the intrusion behavior and therefore does not report the second detection result.

[0078] S120, determine the initial type of the event as an early warning.

[0079] When an event is in the newly added state, the intrusion risk level of the intrusion behavior is considered to be low. Therefore, the initial type of the event is determined to be an alert.

[0080] In a feasible design, the methods include:

[0081] If a second detection result is received from the verification device regarding the intrusion behavior, the defense zone associated with the verification device is determined;

[0082] Determine if the defense zone corresponds to an event attribute set;

[0083] If the defense zone has an event attribute set, determine that the type of the second detection result is an alarm, and add the second detection result and its corresponding type to the event attribute set.

[0084] Since the verification equipment is positioned to supplement the core detection equipment, the second detection result of the verification equipment will only be considered after the core detection equipment detects intrusion behavior in the protected area and reports the first detection result, triggering the background management equipment to generate an event attribute set. If the protected area has a corresponding event attribute set, the second detection result and its corresponding type will be added to the event attribute set to update it. This will allow the background management equipment to re-evaluate the event type, thereby enabling real-time and accurate alarm response to intrusion behavior.

[0085] It should be noted that this application sets the type of the first detection result as both early warning and alarm, while setting the type of the second detection result as only alarm, for the following considerations:

[0086] This design stems from the difference in role positioning and technical verification logic of the two types of devices in the security system. Its essence is to build a hierarchical decision-making mechanism of "active detection and passive verification".

[0087] As the primary detector, the core detection equipment must proactively discover all potential threats (regardless of whether an intrusion is confirmed) to provide a basis for decision-making by the backend management equipment. Therefore, the type of its initial detection output is divided into warning and alarm. For example, if a smart detection cable detects a moving target but cannot immediately identify the type (such as a shadowy figure in the distance), a warning is needed to indicate a potential intrusion. Therefore, the type of the initial detection output is determined as a warning. Compared to simply setting the type of the initial detection output to alarm, dividing the initial detection output into warning and alarm types allows for more flexible responses to uncertain threats.

[0088] The verification device serves as an auxiliary verification tool. Its intrusion detection results are only considered after the core detection device has identified a potential threat. The verification device's task is to further verify suspicious targets; it only needs to provide whether it has identified a confirmed intrusion, not whether it has identified potential intrusions (which are identified by the core detection device). That is, if the verification device reports a second detection result, it is considered to have identified a confirmed intrusion, thus escalating the event response level. If the verification device does not report a second detection result, it is considered not to have identified an intrusion. Limiting the second detection result to an alarm type (rather than a dual warning / alarm type) significantly simplifies the event type decision logic, reduces the computational load on the backend management device, and improves system processing efficiency, while ensuring the verification device fulfills its auxiliary verification function.

[0089] In a feasible design, the zones associated with the verification equipment are determined in the following way:

[0090] Based on the Internet Protocol address of the verification device in the second detection result, the defense zone associated with the verification device is determined by querying the mapping table, which contains the association relationship between each verification device and each defense zone.

[0091] In the example above, the backend management device can efficiently and accurately determine the protection zone associated with the verification device by querying the mapping table based on the Internet Protocol address of the verification device.

[0092] In a feasible design, the methods include:

[0093] If the defense zone does not have a corresponding event attribute set, discard the second detection result.

[0094] If a zone does not have a corresponding event attribute set, it means that the core detection device for that zone did not detect any intrusion. Since the detection results of the core detection device are usually more accurate, the second detection result of the verification device for that zone is not considered based on the core detection device not identifying any intrusion.

[0095] It should be noted that the embodiments of this application can select a suitable combination of core detection equipment and verification equipment based on environmental conditions, thereby overcoming the problem that a single type of detection equipment may cause missed detections due to environmental factors. Furthermore, since core detection equipment typically employs high-precision detection technologies (such as intelligent detection cables based on microwave detection technology), it usually does not have the problem of missed detections. Therefore, if the protected zone does not correspond to an event attribute set, it indicates that the core detection equipment has not detected intrusion behavior. It is generally assumed that the verification equipment has issued a false alarm, and the second detection result is discarded, thus avoiding the risk of missed detections.

[0096] S130, if the event attribute set is updated, and the event attribute set also records the second detection result reported by the verification device for the intrusion behavior and the type of the second detection result, update the event type according to the type of the first detection result and the type of the second detection result in the updated event attribute set.

[0097] The type of the second detection result is an alarm.

[0098] For example, an update to the event property set means that one or more of the following are updated:

[0099] First detection result, second detection result, type of first detection result, type of second detection result.

[0100] In one feasible design, the event type is updated based on the types of the first and second probe results in the updated event attribute set, as follows:

[0101] If the types of the first and second detection results in the updated event attribute set are the same, the updated event type is alarm.

[0102] In the example above, when the types of the first and second detection results in the updated event attribute set are consistent—meaning both are alarms—it indicates that both the core detection device and the verification device have confirmed the intrusion, indicating a high level of intrusion risk. The backend management system updates the event type to alarm, triggering a high-level alarm process to promptly notify security personnel to take appropriate measures. This example, through multi-dimensional joint judgment of the detection results from the core detection device and the verification device, achieves high-precision confirmation of the event type, further improving the accuracy and reliability of the perimeter security system.

[0103] In one feasible design, the event type is updated based on the types of the first and second probe results in the updated event attribute set, including:

[0104] If the types of the first and second detection results in the updated event attribute set are inconsistent, the type of the updated event is an alert.

[0105] In the example above, when the types of the first and second detection results in the updated event attribute set are inconsistent—that is, the first detection result is a warning and the second detection result is an alarm—the backend management device forcibly downgrades the event type to a warning, blocking the path for the event type to escalate to an alarm. This avoids the risk of false escalation due to contradictions in multi-source data, establishes a conservative decision-making strategy in conflict scenarios, and ensures that the backend management device prioritizes maintaining a low-risk state when perceiving discrepancies, improving the reliability of the backend management device's decision-making and reducing the false alarm rate. For example, when the core detection device is a smart detection cable and the verification device is an image recognition device, due to the high sensitivity of the smart detection cable, animal activity or environmental interference may cause it to report a first detection result of type alarm; while the image recognition device does not detect human intrusion and does not report a second detection result. After joint judgment, the backend management device updates the event type to warning instead of alarm, avoiding false alarms.

[0106] In summary, the backend management device will only classify an event as an alarm if both the second and first detection results are classified as alarms. If the first detection result is a warning and the second detection result is an alarm, the event will be classified as a warning. Therefore, the first detection result plays a leading role in determining the event type, while the second detection result serves as a supplementary verification. Under this decision-making mechanism, adding a warning as a second detection result would also burden the verification device with the responsibility of judging potential intrusion behavior, overlapping with the core detection device's responsibilities. This would increase decision-making complexity and reduce the overall efficiency of the backend management device in responding to intrusion behavior.

[0107] S140, if the event attribute set is updated and the event attribute set does not record the type of the second detection result reported by the verification device for the intrusion behavior, update the event type according to the type of the first detection result in the updated event attribute set and the status information of each verification device.

[0108] The fact that the event attribute set did not record the type of the second detection result reported by the verification device for the intrusion behavior means that there was no second detection result reported by the verification device and the verification device did not detect the intrusion behavior.

[0109] In a feasible design, the event type is updated based on the type of the first probe result in the updated event attribute set and the status information of each verification device, as follows:

[0110] If the status information of each verification device indicates that the verification device is not operating properly, the type of the first detection result in the updated event attribute set is determined as the event type, and the event type is updated.

[0111] If at least one verification device contains status information indicating that the verification device is operating normally, the update event type is warning.

[0112] In the example above, when the event attribute set is updated but no verification device reports a second detection result, a multi-dimensional analysis based on the status information of each verification device is required to ensure the accuracy of the decision. If the status information of each verification device indicates that the verification device is not operating normally, the background management device automatically downgrades to a single-modal judgment based on the first detection result of the core detection device, ensuring the robustness of the decision-making scheme. If at least one verification device is operating normally but has not reported a second detection result, the background management device tends to handle the situation conservatively, forcibly updating the event type to an alert to avoid the risk of false alarms. This multi-level decision-making mechanism not only makes full use of the status information of the verification devices but also ensures the reliability of decisions in the case of device anomalies, effectively improving the overall early warning capability of the system and further reducing the false alarm rate.

[0113] S150, trigger the corresponding alarm process according to the type of event.

[0114] It should be understood that if the event attribute set is not updated, after determining that the initial type of the event is a warning, the corresponding alarm process is triggered according to the initial type of the event; if the event attribute set is updated, after updating the type of the event, the corresponding alarm process is triggered according to the updated event type.

[0115] In a feasible design, the alarm process based on the event type can be triggered in the following way:

[0116] If the event type is alarm, activate the audible and visual alarm;

[0117] If the event type is an alert, a notification is sent to the administrator to alert them of potential intrusion into the target zone.

[0118] When the event type is alarm, it means that the risk of intrusion is high. The example above uses audible and visual alarms to achieve an immediate blocking effect through strong sensing methods (such as high-frequency alarm sounds and flashing warning lights). This design can forcibly attract the attention of on-site personnel and shorten the emergency response time.

[0119] When the event type is an alert, a notification is sent only to management personnel, using SMS, system pop-ups, and other notifications to achieve risk prediction. This low-level alert method is suitable for scenarios where the device has not been confirmed to have a threat or where there is potential risk due to environmental interference, avoiding misoperation caused by excessive alerts and thus reducing the false alarm rate.

[0120] Based on the foregoing embodiments, this application also provides an alarm method based on multi-technology fusion, comprising the following steps:

[0121] Step a: After receiving the first detection result for the intrusion behavior reported by the core detection device, generate the event attribute set corresponding to the target defense zone.

[0122] Step b: Determine the initial type of the event corresponding to the event attribute set as an alert (at this time, the event status is new).

[0123] Step c: After the event attribute set is first updated, the event enters an update state. In this state, each update to the event attribute set triggers an update of the event type until the core detection device sends the first detection result, which includes a termination flag indicating intrusion behavior. The steps for updating the event type include:

[0124] Step c1: Determine whether the event attribute set records the type of the second detection result reported by the verification device for the intrusion behavior. If yes, proceed to step c2; otherwise, proceed to step c3.

[0125] Step c2: Determine whether the types of the first probe result and the second probe result in the updated event attribute set are consistent. If yes, proceed to step c4; otherwise, proceed to step c5.

[0126] Step c3: Determine if all the verification devices are malfunctioning. If so, proceed to step c6; otherwise, proceed to step c7.

[0127] Step c4: Update the event type to alarm.

[0128] Step c5: Update the event type to alert.

[0129] Step c6: Determine the type of the first probe result in the updated event attribute set as the event type, and update the event type.

[0130] Step c7: Update the event type to alert.

[0131] Step d: After the core detection device sends the first detection result, which includes a termination flag indicating intrusion behavior, the event enters the end state.

[0132] Through the above steps, the back-end management device achieves full-process management from the first detection of intrusion behavior to the termination of the intrusion behavior, ensuring accurate judgment of early warnings and alarms, and effectively improving the timeliness and accuracy of security protection.

[0133] This application embodiment achieves hierarchical alarm decision-making by fusing multi-source data from core detection devices and verification devices employing different detection technologies, combined with a dynamically updated event attribute set. Upon receiving the first detection result from the core detection device, the method generates an event attribute set containing the status information of the verification device and the type of the first detection result, and sets the initial type of the event corresponding to the event attribute set as a warning. If the event attribute set is not updated, a corresponding low-level alarm process is triggered based on the initial type of the event – ​​warning, achieving an early warning effect for potential intrusion behaviors. When the event attribute set is updated, if the event attribute set contains the type of a second detection result from a verification device, conflict verification is performed by combining the types of the first and second detection results to improve the accuracy of event type determination. An accurate event type helps initiate subsequent alarm processes of corresponding warning levels, thereby improving alarm accuracy and reducing false alarm rates. If the event attribute set does not contain the type of a second detection result reported by a verification device, the event type is updated based on the operating status of the verification device and the type of the first detection result, avoiding misjudgment of the event type due to verification device anomalies, further reducing the false alarm rate.

[0134] In summary, this application utilizes multiple detection devices capable of adapting to various environmental conditions and employing diverse detection technologies to work collaboratively, obtaining multi-source heterogeneous data that includes detection results from the core detection device, detection results from the verification device, and status information of the verification device. Based on this multi-source heterogeneous data, joint decision-making accurately determines the type of event, thereby precisely triggering the corresponding alarm process. This reduces missed and false alarms caused by animal activity and environmental interference, enhancing the accuracy and reliability of the perimeter security system.

[0135] like Figure 2 As shown, this application also provides a perimeter security system, including a back-end management device, a core detection device deployed in the target defense zone, and at least one verification device, wherein the core detection device and at least one verification device use different detection technologies;

[0136] The core detection equipment is used to report the first detection results of intrusion behavior to the back-end management equipment in real time;

[0137] The verification equipment is used to report the second detection results of intrusion behavior to the background management equipment in real time;

[0138] The background management device is used to generate an event attribute set corresponding to the target defense zone if it receives the first detection result of the intrusion behavior reported by the core detection device for the first time. The event attribute set is the response of the background management device to the intrusion behavior. The event attribute set is used to record and update the first detection result reported by the core detection device and the status information of each verification device. The first detection result includes the type of the first detection result. The type of event and the type of the first detection result include warning and alarm. The intrusion risk level corresponding to the warning is lower than the intrusion risk level corresponding to the alarm. The status information indicates whether the verification device is operating normally.

[0139] The backend management equipment is also used to determine the initial type of an event as an alert;

[0140] The background management device is also used to update the event type if the event attribute set is updated, and the event attribute set also records the second detection result reported by the verification device for the intrusion behavior and the type of the second detection result, where the type of the second detection result is alarm;

[0141] The background management device is also used to update the event type based on the type of the first detection result in the updated event attribute set and the status information of each verification device if the event attribute set is updated and the event attribute set does not record the type of the second detection result reported by the verification device for the intrusion behavior.

[0142] The back-end management equipment is also used to trigger corresponding alarm processes based on the type of event.

[0143] In a feasible design, the backend management device updates the event type based on the type of the first probe result in the updated event attribute set and the status information of each verification device:

[0144] If the status information of each verification device indicates that the verification device is not operating properly, the type of the first detection result in the updated event attribute set is determined as the event type, and the event type is updated.

[0145] If at least one verification device contains status information indicating that the verification device is operating normally, the update event type is warning.

[0146] In a feasible design, the backend management device updates the event type based on the types of the first and second probe results in the updated event attribute set:

[0147] If the types of the first and second detection results in the updated event attribute set are the same, the updated event type is alarm.

[0148] In a feasible design, the backend management device updates the event type based on the types of the first and second probe results in the updated event attribute set:

[0149] If the types of the first and second detection results in the updated event attribute set are inconsistent, the type of the updated event is an alert.

[0150] In one feasible design, the back-end management device is also used to determine the type of the second detection result in the following way:

[0151] If a second detection result is received from the verification device regarding the intrusion behavior, the defense zone associated with the verification device is determined;

[0152] Determine if the defense zone corresponds to an event attribute set;

[0153] If the defense zone has an event attribute set, determine that the type of the second detection result is an alarm, and add the second detection result and its corresponding type to the event attribute set.

[0154] In one feasible design, the back-end management device is also used to discard the second detection result if the zone does not correspond to an event attribute set.

[0155] In one feasible design, the core detection equipment is an intelligent detection cable based on microwave detection technology, and the detection technology used by at least one verification device is determined according to the environmental conditions of the target defense zone.

[0156] In a feasible design, the backend management device triggers the corresponding alarm process based on the type of event in the following way:

[0157] If the event type is alarm, activate the audible and visual alarm;

[0158] If the event type is an alert, a notification is sent to the administrator to alert them of potential intrusion into the target zone.

[0159] In a feasible design, the back-end management device determines the zones associated with the verification device in the following way:

[0160] Based on the Internet Protocol address of the verification device in the second detection result, the associated defense zone of the verification device is determined by querying the mapping table, which contains the association between the verification device and the defense zone.

[0161] Other implementation methods and effects of the above system can be found in the description of the embodiments of the alarm method based on multi-technology fusion, and will not be repeated here.

[0162] The basic principles of this application have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the application to the necessity of employing the aforementioned specific details for implementation.

[0163] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0164] The block diagrams of devices, apparatuses, devices, and systems involved in this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0165] It should also be noted that in the apparatus, equipment, and methods of this application, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions of this application.

[0166] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of this application. Therefore, this application is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0167] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. An alarm method based on multi-technology fusion, characterized in that, The method is applied to a back-end management device, which is included in a perimeter security system. The perimeter security system further includes a core detection device deployed in the target defense zone and at least one verification device. The core detection device and the at least one verification device employ different detection technologies. If the first detection result for the intrusion behavior is received for the first time from the core detection device, an event attribute set corresponding to the target defense zone is generated. The event corresponding to the event attribute set is the response of the background management device to the intrusion behavior. The event attribute set is used to record and update the first detection result reported by the core detection device and the status information of each verification device. The first detection result includes the type of the first detection result. The type of the event and the type of the first detection result include warning and alarm. The intrusion risk level corresponding to the warning is lower than the intrusion risk level corresponding to the alarm. The status information indicates whether the verification device is operating normally. The initial type of the event is determined to be an early warning; If the event attribute set is updated, and the event attribute set also records the second detection result reported by the verification device for the intrusion behavior and the type of the second detection result, wherein the type of the second detection result is an alarm, the type of the event is updated according to the type of the first detection result and the type of the second detection result in the updated event attribute set; If the event attribute set is updated, and the event attribute set does not record the type of the second detection result reported by the verification device for the intrusion behavior, the type of the event is updated according to the type of the first detection result in the updated event attribute set and the status information of each verification device; The corresponding alarm process is triggered based on the type of the event.

2. The method according to claim 1, characterized in that, Based on the type of the first detection result in the updated event attribute set and the status information of each verification device, the type of the event is updated, including: If the status information of each of the verification devices indicates that the verification device is not operating properly, the type of the first detection result in the updated event attribute set is determined as the type of the event, and the type of the event is updated. If at least one of the verification devices contains status information indicating that the verification device is operating normally, the event type is updated to warning.

3. The method according to claim 1 or 2, characterized in that, The step of updating the type of the event based on the type of the first probe result and the type of the second probe result in the updated event attribute set includes: If the type of the first detection result and the type of the second detection result are the same in the updated event attribute set, update the type of the event to alarm.

4. The method according to claim 1 or 2, characterized in that, The step of updating the type of the event based on the type of the first probe result and the type of the second probe result in the updated event attribute set includes: If the types of the first and second detection results in the updated event attribute set are inconsistent, update the event type to warning.

5. The method according to claim 1 or 2, characterized in that, The method includes: If a second detection result is received from the verification device regarding the intrusion behavior, the defense zone associated with the verification device is determined; Determine whether the defense zone corresponds to an event attribute set; If the defense zone corresponds to an event attribute set, determine that the type of the second detection result is an alarm, and add the second detection result and its corresponding type to the event attribute set.

6. The method according to claim 5, characterized in that, The method includes: If the defense zone does not correspond to an event attribute set, the second detection result is discarded.

7. The method according to claim 1 or 2, characterized in that, The core detection device is an intelligent detection cable based on microwave detection technology, and the detection technology used by at least one of the verification devices is determined according to the environmental conditions of the target defense zone.

8. The method according to claim 1 or 2, characterized in that, Trigger the corresponding alarm process based on the type of event, including: If the event type is an alarm, activate the audible and visual alarm; If the event type is an early warning, a notification is sent to the administrator, which is used to alert the target defense zone to potential intrusion.

9. The method according to claim 5, characterized in that, The zone associated with the verification device includes: Based on the Internet Protocol address of the verification device in the second detection result, the defense zone associated with the verification device is determined by querying a mapping table, which contains the association between the verification device and the defense zone.

10. A perimeter security system, characterized in that, It includes a back-end management device, a core detection device deployed in the target defense zone, and at least one verification device, wherein the core detection device and at least one verification device use different detection technologies; The core detection device is used to report the first detection result of the intrusion behavior to the background management device in real time. The verification device is used to report the second detection result to the background management device in real time regarding the intrusion behavior; The background management device is used to generate an event attribute set corresponding to the target defense zone if it receives a first detection result for intrusion behavior reported by the core detection device for the first time. The event attribute set corresponds to the event of the background management device in response to the intrusion behavior. The event attribute set is used to record and update the first detection result reported by the core detection device and the status information of each verification device. The first detection result includes the type of the first detection result. The type of the event and the type of the first detection result include warning and alarm. The intrusion risk level corresponding to the warning is lower than the intrusion risk level corresponding to the alarm. The status information indicates whether the verification device is operating normally. The background management device is also used to determine that the initial type of the event is an early warning; The background management device is further configured to, if the event attribute set is updated, and the event attribute set also records the second detection result reported by the verification device for the intrusion behavior and the type of the second detection result, wherein the type of the second detection result is an alarm, update the type of the event according to the type of the first detection result and the type of the second detection result in the updated event attribute set; The background management device is further configured to, if the event attribute set is updated and the event attribute set does not record the type of the second detection result reported by the verification device for the intrusion behavior, update the type of the event according to the type of the first detection result in the updated event attribute set and the status information of each verification device; The background management device is also used to trigger corresponding alarm processes based on the type of the event.

Images