CN111757049A

CN111757049A - Security linkage method, device and system

Info

Publication number: CN111757049A
Application number: CN201910249160.2A
Authority: CN
Inventors: 王兆俊; 郑航; 乔鹿鹿; 杨永
Original assignee: Hangzhou Hikvision System Technology Co Ltd
Current assignee: Hangzhou Hikvision System Technology Co Ltd
Priority date: 2019-03-29
Filing date: 2019-03-29
Publication date: 2020-10-09

Abstract

The embodiment of the invention provides a security linkage method, a security linkage device and a security linkage system, wherein the security linkage method comprises the following steps: acquiring event source data acquired by a pre-registered event source, matching the event source data with a pre-configured linkage rule according to rule conditions of the pre-configured linkage rule, and acquiring a target linkage rule matched with the event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task. Therefore, the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system is very small, and the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system can be reduced.

Description

Security linkage method, device and system

Technical Field

The invention relates to the technical field of security and protection monitoring, in particular to a security and protection linkage method, device and system.

Background

With the development of related technologies in the security field, the security field is developing towards integration and integration, for example, a video monitoring system, an access control system, an anti-theft alarm system, and the like are combined to form a comprehensive security system. So as to facilitate the use and the unified management of users.

In the security field, a single security system generally includes a front-end device and a back-end management software, for example, a video monitoring system includes a front-end video monitoring device and a back-end video monitoring management software, an access control system includes a front-end access control device and a back-end access control management software, and an anti-theft alarm system includes a front-end anti-theft alarm device and a back-end anti-theft alarm management software.

In order to combine a video monitoring system, an access control system, an anti-theft alarm system, and the like, as shown in fig. 1, in the prior art, a security linkage system is generally developed in a software hard coding manner, the anti-theft alarm system 110, the video monitoring system 120, the access control system 130, and the like are taken as subsystems of the security linkage system, specifically, a security linkage management software 140 is compiled in a software hard coding manner, and the security linkage management software 140 may include: the anti-theft alarm management software 111, the video monitoring management software 121, and the access control management software 131 are connected with front-end devices (e.g., the anti-theft alarm device 112, the video monitoring device 122, and the access control device 132) by using a hard-coded software manner, so as to form a security system.

When a user needs to add new equipment or a new subsystem in the security linkage system, the security linkage management software in the security linkage system needs to be modified in a code layer, after the modification is completed, each subsystem of the modified security linkage system needs to be tested, and only after the test is passed, the security linkage system can be put into use, so that the normal operation of the original security linkage system is obviously influenced.

Disclosure of Invention

The embodiment of the invention aims to provide a security linkage method, a security linkage device and a security linkage system so as to reduce the influence of the addition of new equipment or new subsystems on the normal operation of an original security linkage system. The specific technical scheme is as follows:

in a first aspect, an embodiment of the present invention provides a security linkage method, where the security linkage method includes:

acquiring event source data acquired by a pre-registered event source, and matching the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule; a linkage rule comprising: the system comprises at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and pre-registered action sources corresponding to the actions; the rule condition is a condition for event source data; the event sources are: the security equipment and/or the security subsystem can collect event source data; the action sources are: security devices and/or security subsystems capable of performing actions;

acquiring a target linkage rule matched with event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

In a second aspect, an embodiment of the present invention further provides a security linkage device, where the security linkage device includes:

the rule matching module is used for acquiring event source data acquired by a pre-registered event source and matching the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule; a linkage rule comprising: the system comprises at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and pre-registered action sources corresponding to the actions; the rule condition is a condition for event source data; the event sources are: the security equipment and/or the security subsystem can collect event source data; the action sources are: security devices and/or security subsystems capable of performing actions;

the rule execution module is used for acquiring a target linkage rule matched with the event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

In a third aspect, an embodiment of the present invention further provides a linkage system control server, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of the first aspect when executing the program stored in the memory.

In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the method steps in the first aspect are implemented.

In a fifth aspect, an embodiment of the present invention further provides a security linkage system, where the security linkage system includes: the linkage system control server of the third aspect, and the security equipment and/or the security subsystem in communication connection with the linkage system control server.

According to the security linkage method, the security linkage device and the security linkage system, when security equipment or security subsystems are added, the added security equipment and/or security subsystems can be registered as event sources and/or action sources in advance, the added security equipment or security subsystems can be integrated into an original security system, and the rules in the security system can be defined at any time by configuring the linkage rules in advance. The event source data acquired by the event source which is registered in advance is acquired, the event source data is matched with the preset linkage rule according to the rule condition of the preset linkage rule, and when the event source data is separated from the rule, the event source data is matched with the rule to determine whether to execute the linkage action. When the linkage action is determined to be executed, the corresponding task can be generated and sent to the action source, so that the action source executes the corresponding action according to the action parameters and the action content in the generated corresponding task. Therefore, the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system is very small, so that the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system can be reduced. Of course, not all of the advantages described above need to be achieved at the same time in the practice of any one product or method of the invention.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a schematic structural diagram of a security linkage system in the prior art;

fig. 2a is a schematic diagram of a first network structure of a security linkage system according to an embodiment of the present invention;

fig. 2b is a schematic diagram of a second network structure of a security linkage system according to an embodiment of the present invention;

FIG. 3 is a flowchart of a security linkage method according to an embodiment of the present invention;

fig. 4 is a flowchart of a first implementation manner of configuring a linkage rule in a security linkage method according to an embodiment of the present invention;

fig. 5a is a flowchart of a second implementation manner of configuring a linkage rule in a security linkage method according to an embodiment of the present invention;

FIG. 5b is a diagram illustrating a "select event Source" window in the embodiment shown in FIG. 5 a;

FIG. 5c is a diagram of a "select action Source" window in the embodiment shown in FIG. 5 a;

fig. 6a is a flowchart of a third implementation manner of configuring a linkage rule in a security linkage method according to an embodiment of the present invention;

FIG. 6b is a diagram of a "selection rule template" display window in the embodiment shown in FIG. 6 a;

FIG. 6c is a schematic view of the "select scene" display window in the embodiment shown in FIG. 6 a;

FIG. 7 is a schematic diagram of a logic structure of the security linkage system shown in FIG. 2a applied to an actual application scenario;

fig. 8 is a schematic structural diagram of a first implementation manner of a security linkage device according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a second implementation manner of the security linkage device according to the embodiment of the present invention;

fig. 10 is a schematic structural diagram of a linkage system control server according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

In order to solve the problems in the prior art, embodiments of the present invention provide a security linkage method, device, and system, so as to reduce the influence of the addition of new devices or new subsystems on the normal operation of an original security system.

Next, a security linkage method according to an embodiment of the present invention is first described, where the method may be applied to a linkage system control server 210 in a security linkage system shown in fig. 2a, and the security linkage system may further include: security devices and/or security subsystems communicatively coupled to the linkage system control server 210, such as the first security device 220 and the second security device 230, may be the first security subsystem 240 and the second security subsystem 250.

As shown in fig. 3, which is a flowchart of a security linkage method according to an embodiment of the present invention, the method may include:

and S310, acquiring event source data acquired by a pre-registered event source, and matching the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule.

Wherein, the linkage rule includes: the system comprises at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and pre-registered action sources corresponding to the actions; the rule condition is a condition for event source data; the event sources are: the security equipment and/or the security subsystem can collect event source data; the action sources are: security devices and/or security subsystems capable of performing actions.

In some examples, the security linkage system may further include a security linkage control system, which may be a software system installed in an electronic device in the network for implementing security linkage control, such as: and the preset linkage system controls the server. The first security device 220, the second security device 230, the first security subsystem 240 and the second security subsystem 250 may be communicatively connected to the coordinated system control server 210.

In some examples, the security devices or security subsystems described above may be pre-registered with the linkage system control server 210 for communicative connection with the linkage system control server 210. For example, the security device may include: video surveillance cameras or door control management doors, and the like, the security subsystem may include: a video monitoring subsystem, an entrance guard subsystem or an anti-theft alarm system and the like.

In some examples, in order to enable the coordinated system control server 210 to obtain the registration information of the security device and/or the security subsystem, a resource package of the security device and/or the security subsystem may be first imported into the coordinated system control server 210, where the resource package may be a basic resource file of the security device and/or the security subsystem, and for example, the resource package may include a resource file that enables the coordinated system control server 210 to identify the security device and/or the security subsystem. Alternatively, the security devices and/or security subsystems can be enabled to send registration information to the coordinated system control server 210.

After obtaining the resource packet, the coordinated control server 210 may perform configuration based on the resource packet, so as to obtain address information of the security device and/or the security subsystem. The address information may be a physical address or a virtual address.

In still other examples, the coordinated control server 210 may send the address information of the coordinated control server 210 to the security device and/or security subsystem based on the address information. In this way, the security device and/or security subsystem may send its registration information to the coordinated control server 210.

In still other examples, the coordinated control server 210 may further invoke a restful interface based on the address information of the security device and/or the security subsystem, and obtain corresponding registration information from the security device and/or the security subsystem.

In still other examples, the registration information of the security device and/or the security subsystem may also be stored in a common storage module 260 as shown in fig. 2b, and as shown in fig. 2b, the security linkage system may further include a common storage module 260, and the common storage module 260 is communicatively connected to the linkage system control server 210. The coordinated control server 210 may acquire registration information of the security device and/or the security subsystem from the public storage module 260, which is also possible.

In a possible implementation manner of the embodiment of the present invention, the security subsystem may also be a logic unit formed by a plurality of security devices, or a software system running on a hardware device, or the like. For example, the vehicle monitoring system comprises a logic unit consisting of a plurality of physical devices such as a license plate snapshot device, a barrier gate and a coil, or driving monitoring software capable of calculating the driving speed of the vehicle through vehicle positioning data.

In still other examples, when the security device or security subsystem is able to collect event source data, then it may register as an event source. For example, assuming that a video surveillance subsystem may identify strangers based on image data collected by a video surveillance device, the video surveillance subsystem may register as an event source when registering with the linkage system control server 210. Accordingly, the linkage system control server 210 may receive event source data collected by an event source.

As can be seen, the event sources may include:

(1) physical internet of things devices, such as video surveillance cameras, door management gates;

(2) an abstract logic unit, such as an entrance and an exit of a parking lot, wherein the entrance and the exit of the parking lot are actually a logic unit composed of various physical devices such as license plate snapshot devices, banisters and coils;

(3) a software system: for example, the attendance software can calculate the occurrence of late events, absenteeism events and the like, and for example, the driving monitoring software can calculate the obtained vehicle speed information through the vehicle positioning data.

In some examples, the event source and the action source are registered by the following steps:

and step A, acquiring registration information of the security equipment and/or the security subsystem.

Wherein, the registration information of the security equipment and/or the security subsystem can comprise: the security equipment and/or the security subsystem can collect data information and/or can execute action information.

In some examples, the data information that the security device and/or security subsystem can collect may indicate which data information the security device and/or security subsystem can collect or what data information the security device and/or security subsystem can collect. For example, if the security device is a smoke sensor which can collect smoke concentration, the registration information of the smoke sensor may include information that the smoke sensor can collect smoke concentration.

In still other examples, the action information that the security device and/or security subsystem can perform may indicate which actions the security device and/or security subsystem can perform or what actions the security device and/or security subsystem can perform. For example, the security subsystem may execute a photographing action, and the registration information of the security subsystem may include information that the security subsystem can execute the photographing action.

In some examples, the user may store the data packet of the registration information of the security device and/or the security subsystem in a mobile memory, such as a usb disk, a mobile hard disk, or the like, and then import the data packet of the registration information of the security device and/or the security subsystem stored in the mobile memory into the above-mentioned linkage system control server 210. So as to perform event source registration and action source registration through subsequent steps.

B, registering security equipment and/or a security subsystem capable of acquiring event source data as an event source according to the registration information; and registering the security equipment and/or the security subsystem capable of executing the action as an action source.

In some examples, when the coordinated system control server 210 is started, the security device and/or the security subsystem may send its registration information to the coordinated system control server 210 for registration. Thus, the linkage system control server 210 may receive registration information sent by the security devices and/or security subsystems.

After receiving the registration information sent by the security device, the linkage system control server 210 may register the security device as an event source and/or an action source according to the registration information of the security device.

After receiving the registration information sent by the security subsystem, the linkage system control server 210 may register the security subsystem as an event source and/or an action source according to the registration information of the security subsystem.

In some examples, the security device may establish a connection with the linkage system control server 210 through a driver, and the security subsystem may establish a connection with the linkage system control server 210 through an application program interface provided by the subsystem itself.

Specifically, when the registration information of the security device and/or the security subsystem includes: when the security equipment and/or the security subsystem can acquire event source data, the security equipment and/or the security subsystem can be registered as an event source; when the registration information of the security equipment and/or the security subsystem comprises: when the security equipment and/or the security subsystem can execute the action, the security equipment and/or the security subsystem can be registered as an action source.

In some examples, the registration information of the security device and/or the security subsystem may further include identification information or an IP address of the security device and/or the security subsystem, and the like.

In some examples, when the security subsystem provides a plurality of pieces of application program interface information, the registration information of the security subsystem may further include the plurality of pieces of application program interface information of the security subsystem.

In still other examples, when the same security device or security subsystem is capable of both collecting event source data and performing an action, the same security device or security subsystem may send registration information registered as an event source to the linkage system control server 220 and send registration information registered as an action source to the linkage system control server 220, which is also possible.

In some examples, after the security device and/or the security subsystem is registered as the event source, the registration information of the security device and/or the security subsystem is the registration information of the event source. The registration information of the event source may include attribute information of the event source in addition to data information that the event source can collect, and the attribute information of the event source may include an event source type, an event source data type, a presentation style of the event source, and an event source name;

where the event source type describes a category of event source, such as: when the event source is video monitoring equipment, the type of the event source is camera; the presentation style of the event source describes the style of the event source presented in the presentation interface.

In some examples, different types of event sources may generate different types of event source data, and the same type of event source may also generate different types of event source data, for example, a camera may generate event source data such as motion detection data, video occlusion data, region intrusion data, and the like, and to implement classification of event source data, an event source data type may be set, and the event source data type may include: a motion detection type, a video occlusion type, a regional intrusion type, etc.

The event source name describes an event source that acquires event source data, and for example, if there are two event sources, i.e., the camera 1 and the camera 2, which can both collect area intrusion data, the event source name may specifically describe which camera the area intrusion data is collected by.

In some examples, after the security device and/or the security subsystem is registered as the action source, the registration information of the security device and/or the security subsystem is the registration information of the action source. The registration information of the action source may include attribute information of the action source in addition to the action that can be performed by the action source, and the attribute information of the action source may include: action source type, action source name, and presentation style of the action source, etc.

The action source type may describe a type of an action that the action source can perform, for example, when the video surveillance device can perform a photographing action, the action source type of the video surveillance device may be camera. The action source name may describe the action source that performed the action. The presentation style of the action source can describe the style of the action source presented in the presentation interface.

In some examples, the pre-configured linkage rules may be user pre-entered into the linkage system control server.

In some examples, different event sources may collect different event source data, for example, a monitoring camera may collect image data of a monitored area in real time, a sensing device at a doorway of a parking lot may generate sensing information of "having a vehicle" when sensing that there is a vehicle at the doorway, a smoke sensor may generate sensing information of "having smoke" when sensing that there is smoke, and the like.

In still other examples, as shown in fig. 2b, the security linkage system may further include a common storage module 260, the common storage module 260 is communicatively connected to the linkage system control server 210, and the common storage module 260 may be further communicatively connected to the security device and/or the security subsystem. The event source data generated by the event source may be stored in the common storage module 260, such that other devices or systems communicatively coupled to the linkage system control server 210 may be enabled to retrieve the event source data generated by the event source from the common storage module 260.

After acquiring event source data collected by a pre-registered event source, the linkage system control server 210 may match the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule, so as to determine whether event source data matched with the rule condition of the linkage rule exists.

For example, if the linkage rule is "smoke exists in room No. 1, and a smoke alarm is triggered", the rule condition in the linkage rule is "smoke exists in room No. 1". When the event source data received by the linkage system control server 210 is the sensing information of "smoke exists" sent by the smoke sensor corresponding to the "room 1", it can be said that the event source data corresponding to the "room 1" matches the rule condition in the linkage rule.

S320, acquiring a target linkage rule matched with the event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

After the linkage system control server 210 matches the event source data with the preset linkage rule, if there is event source data matching the rule condition of the linkage rule, a target linkage rule matching the event source data is obtained.

In some examples, the linkage system control server 210 may obtain a corresponding linkage action to be executed from the target linkage rule matched with the event source data, and then generate at least one task including an action parameter and an action content according to the linkage action to be executed.

After obtaining the task, in order to enable the corresponding action source to execute the to-be-executed linkage action, the linkage system control server 210 may send at least one task to the corresponding action source, so that the corresponding action source executes the corresponding action according to the action parameter and the action content in the received task.

For example, if the matched linkage rule is "when smoke exists in room No. 1, a smoke alarm is triggered", the to-be-executed linkage action may be acquired as a "smoke alarm". And then, generating at least one task according to the to-be-executed linkage action of smoke alarm, for example, generating a task of alarming once every 3 seconds by No. 1 room alarm, a task of inquiring the contact information of No. 1 room owner and a task of sending reminding information to No. 1 room owner.

Then, the task of alarming once every 3 seconds by the No. 1 room alarm can be sent to the action source of the No. 1 room alarm, and the task of inquiring the contact information of the homeowner in the No. 1 room is sent to a database connected with the security linkage system, wherein the database can store the contact information of the homeowners in all rooms; and sending the task of sending the reminding information to the room owner of the No. 1 room to the reminding information sending device so that the reminding information sending device sends the reminding information to the contact information of the room owner of the No. 1 room.

For another example, assume that the linkage rule is "when a stranger enters room No. 1, trigger the client to alarm and take a snapshot every 5 seconds". After the monitoring camera in the room No. 1 shoots a face, the face can be identified to identify whether the face is a stranger, if so, information that a stranger enters the room No. 1 can be sent to the linkage system control server 210, and after the information that the stranger enters the room No. 1 is received, the linkage system control server 210 can be matched with the linkage rule. For example, a linkage rule that when a stranger enters the room No. 1, a client alarm is triggered and photos are taken at intervals of 5 seconds can be matched, and then linkage motion to be executed can be acquired as client alarm and camera-taken photos. Further, at least one task may be generated according to the linkage action "client alarm" to be performed, for example, a task of "sending a photographed stranger picture to the client" or a task of "starting a client alarm ring" may be generated. The task of 'capturing photos by a camera in the room No. 1 once every 5 seconds' can be generated according to the linkage action 'capturing photos by a camera' to be executed.

According to the security linkage method provided by the embodiment of the invention, when event source data acquired by a pre-registered event source is acquired, the event source data can be matched with a pre-configured linkage rule according to the rule condition of the pre-configured linkage rule; when event source data matched with a pre-configured linkage rule are obtained, a target linkage rule matched with the event source data can be obtained; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and finally, sending the at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

Therefore, when the security equipment and/or the security subsystem is newly added to the original security system, the newly added security equipment and/or the security subsystem can be integrated into the original security system as an event source and/or an action source through pre-registration, the event source data can be separated from the rules through pre-configuration of the linkage rules, and whether the linkage action is executed or not can be determined through matching the event source data with the rules. When the linkage action is determined to be executed, the corresponding task can be generated and sent to the action source, so that the action source executes the corresponding action according to the action parameters and the action content in the corresponding task sent by the rule matching module. Therefore, the influence of the addition of the newly added security equipment or security subsystem on the normal operation of the original security system can be reduced.

In some examples, an embodiment of the present invention further provides a method for configuring a linkage rule, as shown in fig. 4, which is a flowchart of a first implementation manner for configuring a linkage rule in a security linkage method according to an embodiment of the present invention, where the linkage rule may be preconfigured by adopting the following steps:

s410, first rule information input by a user is obtained, and at least one rule condition and at least one action used for linkage are obtained from the first rule information.

Wherein the first rule information includes at least one rule condition and at least one action for linkage.

In some examples, the user may input rule information, which may be the first rule information, into the linkage system control server 210 described above, and thus the linkage system control server 210 may acquire the first rule information input by the user.

In some examples, the rule information may be a text entry by the user, for example, the rule information may be "trigger an alarm when a camera shoots that a stranger enters room number 1". For another example, the rule information may be "in the time period 10 to 12 points, the camera triggers an alarm to alarm when a stranger enters room No. 1. For another example, the rule information may be "trigger an alarm to alarm and send a short message when a stranger enters room No. 1 as photographed by the camera".

The linkage system control server 210 may acquire at least one rule condition and at least one action for linkage from the rule information after acquiring the first rule information input by the user.

For example, the linkage system control server 210 may obtain the rule condition "stranger enters room No. 1" and the linkage action "trigger alarm" in the first rule information "trigger alarm when stranger enters room No. 1" input by the user. The action source may also be acquired as an "alarm". It will be appreciated that the rule condition does not specify the action parameters of the action source, and thus the action parameters of the action source may be the action parameters previously set for the alarm. It is also possible that when the alarm is triggered, the alarm action is performed according to the preset action parameter.

In some examples, in order to enable a user to flexibly input rule information when inputting the rule information, the embodiment of the present invention further provides a possible implementation manner, for example, the user may also input a rule information in natural language text, and for example, the user may input a rule information "indicate a smoke alarm to alarm when the smoke concentration in a room is greater than or equal to 0.06%". In contrast, the linkage system control server 210 may extract at least one rule condition and at least one action for linkage from the first rule information according to the preset standard rule condition text, the correspondence between the standard linkage action text and the natural language text, and the registration information.

In some examples, the user may preset a standard rule condition word, a corresponding relationship between a standard linkage action word and a natural language word in the linkage system control server 210 in advance, for example, a natural language "when the room smoke concentration is greater than or equal to 0.06%, the smoke alarm is indicated to alarm" the corresponding standard rule word is "rule condition: the smoke concentration is greater than or equal to 0.06% ", and the standard linkage action text is" linkage action: smoke alarms ".

When the linked action "smoke alarm" that can be executed by the action source "smoke alarm" is stored in the registration information of the linked system control server 210, the linked system control server 210 may extract the rule conditions "smoke concentration is greater than or equal to 0.06%" and the linked action "linked action, according to the preset standard rule condition words, the correspondence between the standard linked action words and the natural language words, and the registration information: smoke alarms ".

And S420, determining action parameters and action contents of each action and an action source corresponding to each action according to at least one action for linkage.

In some examples, each of the at least one action for linkage may correspond to one action source, that is, each action source may execute one linkage action, and in this case, the linkage system control server 210 may determine the action parameter and the action content of each action and the action source corresponding to each action according to at least one rule condition and at least one action for linkage.

In some examples, the user may previously define attribute information of each action for linkage in the linkage system control server 210 described above, and the attribute information may include: the information includes information on the action content of the linked action, the IP address of the action source of the linked action, the action parameter of the linked action, and the message format. The operation parameters for each of the linked operations may be provided by the registration information transmitted from the operation source or may be customized by the user, and the setting method of the operation parameters is not limited here.

For example, the linkage system control server 210 may determine the action parameters, the action content, and the action source according to the obtained rule condition "stranger enters room No. 1", and the linkage action "triggers an alarm to alarm".

S430, storing at least one rule condition, at least one action for linkage, action parameters and action contents of each action and an action source corresponding to each action as a linkage rule.

After obtaining at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and an action source corresponding to each action, the linkage system control server 210 may store the at least one rule condition, the at least one action for linkage, the action parameters and the action contents of each action, and the action source corresponding to each action as a linkage rule.

For example, the linkage system control server 210 obtains the action parameters and action contents of the rule condition "stranger enters room No. 1" and the linkage action "trigger alarm", and the action source "alarm device" corresponding to the linkage action "trigger alarm". Action parameters and action contents of the rule condition that a stranger enters a No. 1 room and the linkage action triggers the alarm and action sources corresponding to the linkage action triggers the alarm are stored as linkage rules.

According to the embodiment of the invention, the user can generate the linkage rule only by inputting the rule information comprising the rule condition and the linkage action, so that the content input by the user can be reduced, and the flexibility of using the security linkage system of the embodiment of the invention by the user is improved.

In still other examples, when the first rule information input by the user includes a plurality of rule conditions and a plurality of actions for linkage, the embodiment of the present invention may also implement configuration of a complex linkage rule.

Specifically, the linkage system control server 210 may present a plurality of operators for the user to select, so that the relationship between the plurality of rule conditions and the relationship between the plurality of actions for linkage may be determined. In some examples, the plurality of operators includes: "and", "or" and "not", etc.

When the user selects an operator corresponding to the multiple rule conditions from the multiple displayed operators, the multiple rule conditions may be subjected to logical operation based on the selected first operator to obtain rule expressions corresponding to the multiple rule conditions.

For example, the plurality of rule conditions may be "specified time period", "specified area", "continuous occurrence", "specified event", and the first operator may be "and". Then, based on the plurality of rule conditions and the first operator, the corresponding rule expression '"specified time period' and 'specified area' and 'continuous occurrence' and 'specified event'" may be obtained. The regular expression may represent a rule in which specified events continuously occur for a specified period of time and a specified area.

When the user selects an operator corresponding to the plurality of actions for linkage among the plurality of operators displayed, the plurality of actions for linkage may be logically operated based on the selected second operator to obtain the action expressions corresponding to the plurality of actions for linkage.

For example, the plurality of motions for linkage may be "motion a" or "motion B". The second operator may be "or". A corresponding action expression "'action a' or 'action B'" may be derived based on the plurality of actions for linkage and the second operator. The action expression may represent performing action a or action B.

After the rule expressions corresponding to the plurality of rule conditions and the action expressions corresponding to the plurality of actions for linkage are obtained, the rule expressions corresponding to the plurality of rule conditions, the action expressions corresponding to the plurality of actions for linkage, the action parameters and the action contents of each action, and the action sources corresponding to each action may be saved as a linkage rule.

For example, the above-mentioned rule expression '"specifying time period' and 'specified area' and 'continuous occurrence' and 'specified event'", the action expression '"action a' or 'action B'", the action parameter and the action content of "action a", and the action parameter and the action content of "action B" may be saved as the linkage rule.

The linkage rule may indicate that the action is executed according to the action parameters and the action content of the action a or according to the action parameters and the action content of the action B when the specified event continuously occurs in the specified time period and the specified area.

Therefore, the complex linkage rule comprising a plurality of rule conditions and a plurality of linkage actions can be obtained based on the single rule condition and the single action for linkage, and the security linkage method provided by the embodiment of the invention can be applied to more complex scenes.

In some examples, besides that a user inputs rule information to pre-configure a linkage rule, an embodiment of the present invention further provides a possible implementation manner for configuring a linkage rule, as shown in fig. 5a, which is a flowchart of a second implementation manner for configuring a linkage rule in a security linkage method according to an embodiment of the present invention, the configuration linkage rule may be pre-configured by the following steps:

and S510, receiving a rule configuration instruction input by a user.

In some examples, in addition to inputting the rule information in the form of natural language text into the linkage system control server 210 described above, the user may configure the linkage rules by selecting an event source and an action source in the linkage system control server 210.

When the user selects an event source and an action source in the linkage system control server 210, a rule configuration command may be input to the linkage system control server 210 first, so that the linkage system control server 210 can configure the linkage rule.

S520, acquiring data information which can be acquired by at least one event source from the public storage module 260, and displaying the data information which can be acquired by each event source.

When the linkage system control server 210 receives a rule configuration instruction input by a user, data information that can be collected by an event source can be displayed to the user, so that the user can select the event source according to the data information that can be collected by each event source.

In some examples, the data information that can be collected by the event source can be stored in the common storage module 260 shown in fig. 2b, and the linkage system control server 210 can obtain the data information that can be collected by at least one event source from the common storage module 260 and display the data information.

For example, the linkage system control server 210 may present the user with a "select event source" window as shown in fig. 5b, which may include 6 selectable event sources and corresponding data information that can be collected.

S530, receiving an event source selected by a user based on data information which can be collected by each event source and an input rule condition corresponding to the selected event source.

In some examples, after the linkage system control server 210 displays data information that can be collected by each event source, the user may select an event source based on the displayed registration information of each event source.

When the user selects an event source, a rule condition may be input, and thus the linkage system control server 210 may receive the event source selected by the user and the input rule condition.

In some examples, the linkage system control server 210 described above may also present a "selection rule conditions" window to the user, which, as shown in fig. 5b, may include: event occurrence area, event occurrence time and event source.

In this way, the user can first select when entering the rule condition and then enter the specific content of the rule condition in the template of the selected rule condition. For example, the user may select "event occurrence area" in "selection rule condition" shown in fig. 5b, and then input a specific area where the event occurs, for example, the area may be "cell gate", "level crossing", or the like. The user may also select "event occurrence time" and then input a specific occurrence time, for example, an occurrence time of "10 pm. -7 am." or the like may be input.

In this way, the flexibility of the user to input rule conditions may be increased.

And S540, acquiring the action information which can be executed by at least one action source from the public storage module 260, and displaying the action information which can be executed by each action source.

And S550, receiving the action source selected by the user based on the action information which can be executed by each action source and the action for linkage corresponding to the selected action source.

S560, determining the action parameter and the action content of the linkage action according to the selected action source and the action used for linkage corresponding to the selected action source;

s570, storing the rule condition corresponding to the selected event source, the selected action source, the action for linkage corresponding to the selected action source, the action parameter of the action for linkage, and the action content as the linkage rule.

In some examples, in addition to the data information that can be collected by the event source and the action information that can be executed by the action source, which are described above, may be stored in the common storage module 260, so that the linkage system control server 210 may obtain the action information that can be executed by at least one action source from the common storage module 260, and display the action information that can be executed by each action source, so that the user may select the action source according to the action information that can be executed by each action source.

For example, the linkage system control server 210 described above may present the user with a "select action source" window as shown in FIG. 5c, which may include multiple action sources, e.g., 5 action sources as shown in FIG. 5 c. In some examples, each action source may correspond to action information that can be performed, such as: the executable action information corresponding to the action source 1 is "pop up the specified monitoring point real-time video", the executable action information corresponding to the action source 2 is "play the specified monitoring point video playback", the executable action information corresponding to the action source 3 is "send prompt information to the user", and the like. The executable action information may indicate an associated action that the action source can execute.

The linkage system control server 210 may determine the action parameter and the action content of each action according to the selected action source and the action for linkage corresponding to the selected action source after receiving the event source selected by the user, the selected action source, the action for linkage corresponding to the selected action source, and the input rule condition.

For example, assume that the event source selected by the user is a smoke sensor, the input rule condition corresponding to the selected event source is "room smoke density is greater than or equal to 0.06%", the selected action source is a smoke alarm, and the action for linkage corresponding to the selected action source is "trigger smoke alarm". The smoke alarm may be preset with default action parameters, for example, the default action parameters are "alarm once every 5 seconds". Then the determined motion parameter is "alarm once every 5 seconds" and the content of the motion is "alarm" according to the selected motion source and the motion for linkage corresponding to the selected motion source.

In some examples, the user may also input motion parameters for the linkage motion when selecting the motion source and the motion corresponding to the motion source for the linkage. For example, the motion parameter of the user-input linkage motion is "alarm once in three seconds".

In this way, it is also possible to make the action source preferentially adopt the action parameters input by the user when performing the action.

After the operation parameters and the operation contents of each operation are determined, the linkage system control server 210 may store the rule condition corresponding to the selected event source, the selected operation source, the operation for linkage corresponding to the selected operation source, and the operation parameters and the operation contents of the linkage operation as the linkage rule.

Therefore, the embodiment of the invention can enable the user to select the action source and the event source when inputting the rule information, thereby improving the flexibility of inputting the rule information by the user. In addition, the embodiment of the invention can realize the configuration of the linkage rule based on the rule information input by the user, also improves the flexibility of the embodiment of the invention for configuring the linkage rule and enlarges the application range of the embodiment of the invention.

In some examples, the user may store the preset rule conditions and linkage actions in a mobile memory, such as a usb disk, a mobile hard disk, etc., and then import the preset rule conditions and linkage actions stored in the mobile memory into the linkage system control server 210.

In still other examples, the user may also store a preset event source data type in the mobile memory and then import the preset event source data type stored in the mobile memory into the linkage system control server 210. Thereby, more detailed classification of event source data can be realized.

In still other examples, the user may also select attribute information of the rule condition when entering the rule condition, and the attribute information of the rule condition may include: the type of the rule condition, the presentation style of the rule condition, the viewing permission information of the rule condition, and the like, wherein the presentation style may be the style shown in the "select rule condition" box shown in fig. 5 b. The type of the rule condition may be the same or similar to the event source data type.

In some examples, the presentation style may be a tree, a shuttle box, a drop down list, an input box, etc., page base presentation style or a combination of base presentation styles.

In still other examples, when the user inputs the linkage action, the attribute information of the linkage action may be further selected, and the attribute information of the linkage action may include: the method comprises the following steps of linkage action type, action parameter, presentation style of linkage action, action source and address information of the action source, wherein the linkage action type can be the type of action which can be executed by the action source, and the action parameter can be: the action source may execute the action at the following time, the number of times the action is executed, the time interval for executing the action, the time duration for executing the action, the time delay duration for executing the action, and the like: an operation start time, an operation stop time, and the like.

It should be understood that the description is given here for the attribute information of the linkage action, and the attribute information may be one attribute information described above, may be a plurality of attribute information, and may be contents of other attribute information that can be defined as the linkage action.

In some examples, an embodiment of the present invention further provides a possible implementation manner of configuring a linkage rule, as shown in fig. 6a, which is a flowchart of a third implementation manner of configuring a linkage rule in a security linkage method according to an embodiment of the present invention, where the configuration linkage rule may be preconfigured by adopting the following steps:

s610, storing a plurality of rule templates established in advance.

Each rule template comprises selectable rule conditions, linkage actions and action sources corresponding to the rule template.

In some examples, in order to provide more convenience for a user, the security linkage method of the embodiment of the invention further provides a rule template. In order to obtain the rule template, the linkage system control server 210 may count the frequency of matching the linkage rule with the event source data.

For example, assuming that the linkage rules "rule 1", "rule 2", and "rule 3" exist, when matching "rule 1" with the event source data, the frequency with which "rule 1" is matched to the event source data may be counted; when matching "rule 2" with event source data, the frequency of matching "rule 2" to event source data may be counted; in matching "rule 3" with the event source data, the frequency of matching "rule 3" to the event source data may be counted, which may be a quotient of the number of times each rule is matched to the event source data and the total number of event source data.

After counting the frequency of matching the linkage rule with the event source data, the linkage system control server 210 may select a plurality of linkage rules as the basic template of the rule template according to the frequency.

For example, a linkage rule satisfying a preset frequency condition may be used as a base template of the rule template. In some examples, the preset frequency condition may be greater than a preset frequency threshold or the frequency ranking is greater than a preset frequency ranking threshold.

And then setting the rule condition in the basic template as a selectable rule condition, setting the linkage action in the basic template as a selectable linkage action, and setting the action source in the basic template as a selectable action source, thereby obtaining the rule template.

In some examples, when counting the frequency of matching the linkage rule with the event source data, a user type may also be set, and then the frequency of matching the linkage rule corresponding to the user type with the event source data may be counted according to different user types.

For example, when the user type is a cell user, the frequency of matching the linkage rule corresponding to the cell user with the event source data may be counted, and when the user type is a mall user, the frequency of matching the linkage rule corresponding to the mall user with the event source data may be counted.

After the rule template is obtained, the rule template may be stored for subsequent use.

S620, displaying a plurality of stored rule templates which are established in advance.

S630, receiving second rule information selected by the user from the plurality of rule templates.

In some examples, the second rule information includes a rule condition selected by a user from one of the plurality of rule templates, a selected linkage action, and a selected action source. The one rule template may also be a template selected by the user from the plurality of rule templates.

And S640, generating the linkage rule according to the second rule information selected from the plurality of rule templates by the user.

In some examples, when the user wants to input rule information, the user may select to add the rule information from the rule template, and at this time, the linkage system control server 210 may receive an instruction of "add rule information from rule template", and then obtain a plurality of rule templates established in advance, and present the plurality of rule templates, so that the user may select the rule information from the plurality of rule templates.

For example, the rule template may be as shown in FIG. 6 b. A plurality of rule templates may be included in fig. 6b, and a user may select a rule template to be used from among the plurality of rule templates and select a rule condition, a linkage action, and an action source from among the selected rule templates to be used, so that the user may be provided with more flexibility in inputting rule information.

In some examples, when the user selects the rule template, the location of the event source may also be selected, for example, the location of the event source may be the entrance of a cell, the cash register of a store, etc., and by selecting the location, the linkage system control server 210 of the embodiment of the present invention may be brought closer to the actual use of the user.

After the user selects the rule information from the rule template, the linkage system control server 210 may generate and store the corresponding linkage rule according to the rule information selected by the user from the rule template.

In some examples, different rule templates may be applied to different scenes, and thus, the above-described plurality of rule templates may be stored separately by scene. When the rule templates are stored according to the scenes, S620 may include:

step A, acquiring scene information input by a user, and determining a current scene according to the scene information input by the user;

and step B, displaying a plurality of rule templates pre-established for the current scene.

In some examples, the plurality of rule templates may be classified according to scenes in advance, and then the classified rule templates may be stored according to scenes.

After the rule template is stored according to the scene, when the user inputs scene information, the linkage system control server 210 may acquire a pre-established rule template corresponding to the scene information input by the user, and then display the pre-established rule template corresponding to the scene information input by the user, so that the user may select the rule information from the pre-established rule templates corresponding to the scene information.

For example, as shown in fig. 6c, when the scene information input by the user is the "perimeter intrusion notification monitoring scene", a rule template corresponding to the "perimeter intrusion notification monitoring scene" may be displayed, when the scene information input by the user is the "forbidden zone illegal parking notification monitoring scene", a rule template corresponding to the "forbidden zone illegal parking notification monitoring scene" may be displayed, when the scene information input by the user is the "fire passage occupation notification monitoring scene", a rule template corresponding to the "fire passage occupation notification monitoring scene" may be displayed, and when the scene information input by the user is the "landscape pool abnormal intrusion notification monitoring scene", a rule template corresponding to the "landscape pool abnormal intrusion notification monitoring scene" may be displayed.

Through the embodiment of the invention, the linkage system control server 210 can be combined with the actual use scene of the user, so that the linkage system control server 210 of the embodiment of the invention is closer to the actual use scene of the user, and the user experience is improved.

In some examples, different rule templates are stored according to scenes, so that after a security linkage system is established by applying the security linkage method of the embodiment of the present invention, the security linkage system may use different rule templates in different scenes, and the rule templates may be configured with corresponding rules in advance, for example, when a usage scene of a user is a cell scene, corresponding rule templates may be set for a fire passage, a monitoring center, an entrance guard, and the like of the cell, and when the usage scene of the user is a checkout counter of a chain supermarket, corresponding rule templates may be set for the checkout counter of the chain supermarket.

Therefore, when the user uses the security linkage system, the rule template corresponding to the user scene can be used by setting the use scene, so that the personalized customization can be realized for the user, and the security linkage system can be applied to different industries.

For a more clear description of the embodiment of the present invention, a security linkage system according to the embodiment of the present invention is described below with reference to fig. 7 as an example.

As shown in fig. 7, which is a schematic diagram of a logic structure of the security linkage system shown in fig. 2a applied in an actual application scenario, assuming that original event sources of the security linkage system of the embodiment of the present invention are the access control subsystem 710, the burglar alarm subsystem 720 and the video monitoring subsystem 730, and original action sources may also be the access control subsystem 710, the burglar alarm subsystem 720 and the video monitoring subsystem 730, registration information of the newly added parking lot parking management subsystem 740, the driving monitoring subsystem 750 and the linkage client device 760 may be registered to a registration module in the security linkage system, and then the newly added parking lot parking management subsystem 740 is simultaneously registered as an event source and an action source, and the newly added driving monitoring subsystem 750 is registered as an event source, the linkage client device 760 is registered as the action source.

Therefore, when new security equipment or a security subsystem is added, software hard coding does not need to be carried out on the security linkage system again.

After the registration is completed, the user can input rule information in the security linkage system, and after the security linkage system obtains the rule information input by the user, the security linkage system can generate a linkage rule according to the rule information.

Then, the security linkage system can acquire event source data generated by each event source and then match the event source data with rule conditions in the linkage rule.

For example, when the door opening or closing event occurs to the door access subsystem 710, corresponding event source data may be generated; when an burglar alarm installed in a room detects a person entering the room, the burglar alarm subsystem 720 may generate event source data as "alarm information"; the video surveillance subsystem 730 may generate video data; when a vehicle enters a parking lot, the vehicle identification device in parking management subsystem 740 may identify the vehicle and generate event source data as "parking data", which may include the time when the vehicle entered the parking lot, vehicle identification information. The event source data that may be generated when the traffic monitoring device in the traffic monitoring subsystem 750 detects that the vehicle travel speed exceeds the defined travel speed may be "overspeed warning information" and travel speed information.

When the event source data is matched with the rule conditions in the linkage rule, the linkage action and the action source in the linkage rule can be acquired.

For example, assume that the linkage rule is "when there is suspicious people in the surveillance video, the surveillance video goes to the video wall". Then, when there is suspicious people in the surveillance video shot by the video surveillance equipment in the video surveillance subsystem 730, the linkage action "on the video wall of the surveillance video" and the action source "video surveillance subsystem 730" may be obtained. A task may then be generated and sent to the video surveillance subsystem 730, such that the video surveillance subsystem 730 may retrieve the surveillance video of the video surveillance device and play the retrieved surveillance video on the video wall 750 of the video surveillance subsystem 730. The video wall 750 may include, among other things, a video wall control device and a video wall display screen.

For another example, assume that the linkage rule is "when there is suspicious people in the surveillance video, the linkage client device plays the surveillance video". Then when there is suspicious people in the surveillance video captured by the video surveillance equipment of the video surveillance subsystem 730, the linked action "video playback" and the action source "linked client device 760" may be obtained. A task is then generated and sent to the linkage client device 760, so that the linkage client device 760 can retrieve the captured surveillance video captured by the video surveillance device from the video surveillance subsystem 730 for playback.

In some examples, the linkage client device 760 may be a user handheld terminal device, such as: the mobile terminal can be a smart phone, a tablet computer and the like capable of playing videos, and can also be a personal computer, a notebook computer and the like of a user.

Therefore, according to the embodiment of the invention, when new security equipment or a security subsystem is added to the original security linkage system, the normal operation of the original security linkage system is not influenced, so that the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security linkage system can be reduced, and in addition, the event source data can be separated from the event rule, so that the event rule can be edited and changed, and the flexibility of the security linkage system applying the embodiment of the invention can be improved.

Corresponding to the above method embodiment, an embodiment of the present invention further provides a security linkage device, where the security linkage device may be applied to a linkage system control server in a security linkage system shown in fig. 2a or fig. 2b, and the security linkage system may further include: as shown in fig. 8, the security device and/or the security subsystem in communication connection with the linkage system control server is a schematic structural diagram of a first implementation manner of the security linkage device according to the embodiment of the present invention, and the security linkage device may include:

the rule matching module 810 is configured to obtain event source data collected by a pre-registered event source, and match the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule; a linkage rule comprising: the system comprises at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and pre-registered action sources corresponding to the actions; the rule condition is a condition for event source data; the event sources are: the security equipment and/or the security subsystem can collect event source data; the action sources are: security devices and/or security subsystems capable of performing actions;

a rule executing module 820, configured to obtain a target linkage rule matched with the event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

According to the security linkage device provided by the embodiment of the invention, when the security equipment or the security subsystem is added, the added security equipment and/or the added security subsystem can be registered as the event source and/or the action source in advance, so that the added security equipment or the added security subsystem can be integrated into the original security system, and the rules in the security system can be defined at any time by pre-configuring the linkage rules. The event source data acquired by the event source which is registered in advance is acquired, the event source data is matched with the preset linkage rule according to the rule condition of the preset linkage rule, and when the event source data is separated from the rule, the event source data is matched with the rule to determine whether to execute the linkage action. When the linkage action is determined to be executed, the corresponding task can be generated and sent to the action source, so that the action source executes the corresponding action according to the action parameters and the action content in the generated corresponding task. Therefore, the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system is very small, so that the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system can be reduced.

On the basis of the security linkage device shown in fig. 8, an embodiment of the present invention further provides a possible implementation manner, as shown in fig. 9, which is a schematic structural diagram of a second implementation manner of the security linkage device of the embodiment of the present invention, and the security linkage device may further include: a registration module 830 and a first configuration module 840;

the registration module 830 is configured to receive registration information sent by the security device and/or the security subsystem, or acquire a pre-stored resource packet including the registration information of the security device and/or the security subsystem; wherein, the registration information includes: data which can be collected and/or actions which can be executed by the security equipment and/or the security subsystem;

registering security equipment and/or a security subsystem which can acquire event source data as an event source according to the registration information; and registering the security equipment and/or the security subsystem capable of executing the action as an action source.

A first configuration module 840, comprising: a first rule information obtaining submodule, a condition and rule obtaining submodule and a first rule storage submodule;

the first rule information acquisition submodule is used for acquiring first rule information input by a user and acquiring at least one rule condition and at least one action for linkage from the first rule information;

the first rule storage submodule is used for determining action parameters and action contents of each action and an action source corresponding to each action according to at least one action for linkage; and storing at least one rule condition, at least one action for linkage, action parameters and action contents of each action and an action source corresponding to each action as a linkage rule.

Specifically, when the first rule information includes a plurality of rule conditions and a plurality of actions for linkage; the first configuration module 840, further comprising:

the operator obtaining sub-module is used for obtaining a first operator selected by a user aiming at a plurality of rule conditions and a second operator selected aiming at a plurality of actions for linkage, wherein the first operator and the second operator are operators in the operators displayed after the first rule information is received;

a first rule holding submodule comprising:

the first logic operation unit is used for carrying out logic operation on the plurality of rule conditions by adopting a first operator to obtain rule expressions corresponding to the plurality of rule conditions;

the second logical operation unit is used for carrying out logical operation on the plurality of actions for linkage by adopting a second operator to obtain a plurality of action expressions corresponding to the actions for linkage;

and the first rule storage unit is used for storing the rule expressions corresponding to the rule conditions, the action expressions corresponding to the actions for linkage, the action parameters and the action contents of each action and the action sources corresponding to each action as linkage rules.

Specifically, the first rule information is rule information of natural language characters;

specifically, the first rule information obtaining sub-module is specifically configured to extract at least one rule condition and at least one linkage action from the first rule information according to a preset standard rule condition text, a corresponding relationship between a standard linkage action text and a natural language text, and registration information.

Specifically, event source data is stored in a public storage module by a pre-registered event source;

the rule matching module 810 is specifically configured to acquire event source data of event sources registered in advance and stored in the common storage module, and match the event source data with a preset linkage rule.

Specifically, the registration information is stored in a public storage module; this security protection aggregate unit can also include: a second configuration module;

a second configuration module comprising: the system comprises an instruction receiving submodule, an event source display submodule, a rule condition receiving submodule, an action source display submodule, a second rule information acquisition submodule and a second rule storage submodule;

the instruction receiving submodule is used for receiving a rule configuration instruction input by a user;

the event source display sub-module is used for acquiring data information which can be acquired by at least one event source from the public storage module and displaying the data information which can be acquired by each event source;

the rule condition receiving submodule is used for receiving an event source selected by a user based on data information which can be collected by each event source and an input rule condition corresponding to the selected event source;

the action source display sub-module is used for acquiring action information which can be executed by at least one action source from the public storage module and displaying the action information which can be executed by each action source;

the linkage action receiving submodule is used for receiving action sources selected by a user based on action information which can be executed by each action source and actions for linkage corresponding to the selected action sources;

and the second rule storage submodule is used for determining the action parameters and the action content of the linkage action according to the selected action source and the action for linkage corresponding to the selected action source, and storing the rule condition corresponding to the selected event source, the selected action source, the action for linkage corresponding to the selected action source, the action parameters and the action content of the linkage action as the linkage rule.

Specifically, this security protection aggregate unit can also include: the template storage module and the third configuration module;

the template storage module is used for storing a plurality of rule templates which are established in advance; each rule template comprises selectable rule conditions, linkage actions and action sources corresponding to the rule template;

a third configuration module, which may include: the template display submodule, the second rule information receiving submodule and the linkage rule generating submodule;

the template display submodule is used for displaying a plurality of stored rule templates which are established in advance;

the second rule information receiving submodule is used for receiving second rule information selected by a user from the plurality of rule templates, wherein the second rule information comprises a rule condition selected by the user from one of the plurality of rule templates, a selected linkage action and a selected action source;

and the linkage rule generating submodule is used for generating a linkage rule according to second rule information selected by a user from the plurality of rule templates.

Specifically, the rule template storage module stores the pre-established rule templates respectively according to scenes;

the template display submodule is specifically used for acquiring scene information input by a user; determining a current scene according to scene information input by a user; and displaying a plurality of rule templates pre-established for the current scene.

The embodiment of the present invention further provides a linkage system control server, as shown in fig. 10, which includes a processor 1001, a communication interface 1002, a memory 1003 and a communication bus 1004, wherein the processor 1001, the communication interface 1002 and the memory 1003 complete mutual communication through the communication bus 1004,

a memory 1003 for storing a computer program;

the processor 1001 is configured to implement the following steps when executing the program stored in the memory 1003:

The communication bus 1004 mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 1004 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

The communication interface 1002 is used for communication between the electronic apparatus and other apparatuses.

The Memory 1003 may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. In some examples, memory 1003 may also be at least one memory device located remotely from the aforementioned processor.

The Processor 1001 may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

When the security equipment or the security subsystem is added, the added security equipment and/or the added security subsystem can be registered as an event source and/or an action source in advance, so that the added security equipment or the added security subsystem can be integrated into the original security system, and the rules in the security system can be defined at any time by pre-configuring the linkage rules. The event source data acquired by the event source which is registered in advance is acquired, the event source data is matched with the preset linkage rule according to the rule condition of the preset linkage rule, and when the event source data is separated from the rule, the event source data is matched with the rule to determine whether to execute the linkage action. When the linkage action is determined to be executed, the corresponding task can be generated and sent to the action source, so that the action source executes the corresponding action according to the action parameters and the action content in the generated corresponding task. Therefore, the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system is very small, so that the influence of the addition of the new equipment or the new subsystem on the normal operation of the original security system can be reduced.

The embodiment of the invention also provides a security linkage system, which comprises the following steps: the linkage system control server and the security equipment and/or the security subsystem which are in communication connection with the linkage system control server. For example, as shown in fig. 2, the security linkage system may include: the linkage system comprises a control server 210, a first security device 220, a second security device 230, a first security subsystem 240 and a second security subsystem 250.

The embodiment of the invention also provides a computer readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the method and electronic device embodiments, since they are substantially similar to the system embodiments, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiments.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.

Claims

1. A security linkage method is characterized by comprising the following steps:

acquiring event source data acquired by a pre-registered event source, and matching the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule; the linkage rule includes: the system comprises at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and pre-registered action sources corresponding to the actions; the rule condition is a condition for event source data; the event sources are: the security equipment and/or the security subsystem can collect event source data; the action sources are as follows: security devices and/or security subsystems capable of performing actions;

acquiring a target linkage rule matched with the event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending the at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

2. The method of claim 1, wherein the event source and the action source are registered by:

acquiring registration information of the security equipment and/or the security subsystem; wherein, the registration information includes: data information and/or executable action information which can be collected by the security equipment and/or the security subsystem;

3. The method of claim 2, wherein the linkage rules are pre-configured by:

acquiring first rule information input by a user, and acquiring at least one rule condition and at least one action for linkage from the first rule information;

determining action parameters and action contents of each action and an action source corresponding to each action according to the at least one action for linkage;

and storing the at least one rule condition, the at least one action for linkage, the action parameter and the action content of each action and the action source corresponding to each action as the linkage rule.

4. The method according to claim 3, characterized in that when the first rule information includes a plurality of rule conditions and a plurality of actions for linkage; the method further comprises the following steps:

acquiring a first operator selected by a user for the plurality of rule conditions and a second operator selected by the user for the plurality of actions for linkage;

the storing the at least one rule condition, the at least one action for linkage, the action parameter and the action content of each action, and the action source corresponding to each action as the linkage rule includes:

performing logical operation on the plurality of rule conditions by using the first operator to obtain rule expressions corresponding to the plurality of rule conditions;

performing logical operation on the plurality of actions for linkage by adopting the second operator to obtain action expressions corresponding to the plurality of actions for linkage;

and storing the rule expressions corresponding to the rule conditions, the action expressions corresponding to the actions for linkage, the action parameters and the action contents of each action and the action source corresponding to each action as the linkage rule.

5. The method according to claim 3, wherein the first rule information is rule information of a natural language text; the step of obtaining at least one rule condition and at least one action for linkage from the first rule information includes:

and extracting at least one rule condition and at least one action for linkage from the first rule information according to the preset standard rule condition characters, the corresponding relation between the standard linkage action characters and the natural language characters and the registration information.

6. The method of claim 2, wherein the registration information is stored in a common storage module; the linkage rule is pre-configured by adopting the following steps:

receiving a rule configuration instruction input by a user;

acquiring data information which can be acquired by the at least one event source from the public storage module, and displaying the data information which can be acquired by each event source;

receiving event sources selected by a user based on data information which can be collected by each event source and input rule conditions corresponding to the selected event sources;

acquiring the action information which can be executed by the at least one action source from the public storage module, and displaying the action information which can be executed by each action source;

receiving action sources selected by a user based on action information which can be executed by each action source and actions for linkage corresponding to the selected action sources;

determining action parameters and action contents of the action according to the selected action source and the action for linkage corresponding to the selected action source;

and storing the rule condition corresponding to the selected event source, the selected action source, the action for linkage corresponding to the selected action source, the action parameter and the action content of the action as the linkage rule.

7. The method of claim 1, wherein the linkage rules are pre-configured by:

storing a plurality of rule templates which are established in advance; each rule template comprises selectable rule conditions, linkage actions and action sources corresponding to the rule template;

displaying the plurality of rule templates;

receiving second rule information selected by the user from the plurality of rule templates, wherein the second rule information comprises a rule condition selected by the user from one of the plurality of rule templates, a selected linkage action and a selected action source;

and generating the linkage rule according to the second rule information.

8. The method according to claim 7, wherein the pre-established rule templates are stored separately by scene;

the step of displaying the plurality of rule templates includes:

acquiring the scene information input by the user, and determining the current scene according to the scene information input by the user;

and displaying a plurality of rule templates pre-established for the current scene.

9. A security linkage, the device comprising:

the rule matching module is used for acquiring event source data acquired by a pre-registered event source and matching the event source data with a pre-configured linkage rule according to a rule condition of the pre-configured linkage rule; the linkage rule includes: the system comprises at least one rule condition, at least one action for linkage, action parameters and action contents of each action, and pre-registered action sources corresponding to the actions; the rule condition is a condition for event source data; the event sources are as follows: the security equipment and/or the security subsystem can collect event source data; the action sources are as follows: security devices and/or security subsystems capable of performing actions;

the rule execution module is used for acquiring a target linkage rule matched with the event source data; generating at least one task comprising action parameters and action contents according to the linkage action to be executed in the target linkage rule; and sending the at least one task to a corresponding action source, so that the corresponding action source executes a corresponding action according to the action parameters and the action content in the received task.

10. A linkage system control server, characterized by: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for finishing mutual communication through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of any of claims 1 to 8 when executing a program stored in the memory.

11. The utility model provides a security protection linked system which characterized in that includes: the linked system control server of claim 10 and security devices and/or security subsystems communicatively connected to the linked system control server.