CN114222094A

CN114222094A - Alarm linkage configuration method and security system

Info

Publication number: CN114222094A
Application number: CN202111554933.1A
Authority: CN
Inventors: 吴志煌; 刘健; 吴豪
Original assignee: Hangzhou Hikvision Digital Technology Co Ltd
Current assignee: Hangzhou Hikvision Digital Technology Co Ltd
Priority date: 2021-12-17
Filing date: 2021-12-17
Publication date: 2022-03-22

Abstract

The embodiment of the application provides an alarm linkage configuration method and a security system, relates to the field of security and protection, and can enable a back-end device to smoothly process an alarm message reported by a front-end device under the condition that the back-end device is not updated. The method is applied to the back-end equipment in a security system in which a first front channel of the front-end equipment is accessed to a first back channel of the back-end equipment. The method comprises the following steps: acquiring a channel alarm capacity set of a first front channel; generating at least one linkage configuration file according to the channel alarm capacity set and the alarm source; the alarm source is used for indicating the first rear channel and/or the first front channel; the linkage configuration file comprises an alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule; the linkage rule is used for indicating the back-end equipment to execute corresponding linkage operation when receiving the capability identification in the linkage configuration file to which the linkage rule belongs through a channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs.

Description

Alarm linkage configuration method and security system

Technical Field

The application relates to the field of security management, in particular to an alarm linkage configuration method and a security system.

Background

With the development of digital technology, more and more front-end devices (such as network cameras, access control devices, and the like) in the existing security system have stronger intelligence. Through the updating and upgrading of the equipment, the front-end equipment can identify richer alarm events and has stronger alarm function. Under the circumstance, if the back-end equipment or the back-end platform corresponding to the front-end equipment is not updated, the back-end equipment cannot correctly identify and process the alarm message reported by the front end, and then the whole security system cannot normally operate. Therefore, after the front-end device is updated, the matched back-end device/platform is often updated at the same time in order to update the security system to meet the new alarm scene requirement. However, since the structure of the back-end device is complex, the cost is high, and the period required for updating is long, the security system which updates the front-end device cannot use the updated function quickly.

Disclosure of Invention

Embodiments of the present application provide an alarm linkage configuration method and a security system, which enable a back-end device to smoothly process an alarm message reported by a front-end device without updating the back-end device.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an alarm linkage configuration method is provided, which is applied to a back-end device in a security system, the security system further comprises a front-end device, and a first front channel of the front-end device is connected to a first back channel of the back-end device. The method comprises the following steps: firstly, acquiring a channel alarm capacity set of a first front channel; the channel alarm capability set comprises at least one alarm capability supported by the first front channel, the alarm capability has a unique corresponding capability identifier, and the capability identifier has a unique corresponding alarm type. Then, generating at least one linkage configuration file according to the channel alarm capacity set and the alarm source; the linkage configuration files correspond to the alarm types one by one; the alarm source is used for indicating the first rear channel and/or the first front channel; the linkage configuration file comprises an alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule; and the linkage rule is used for indicating the back-end equipment to execute corresponding linkage operation when receiving the capability identification in the linkage configuration file to which the linkage rule belongs through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs.

Based on the above technical solution, the back-end device can automatically identify a channel alarm capability set (composed of at least one alarm capability (specifically, an alarm capability identifier) supported by a certain front channel of the front-end device) of the front-end device, and automatically generate a linkage rule configuration file corresponding to each alarm type of each channel connected between each back-end device and the front-end device according to each capability identifier and an alarm source (for example, a back channel of the back-end device and/or a front channel of the front-end device) of the channel capable of indicating alarm message transmission according to a preset rule. In the process, the back-end equipment does not need to recognize or translate the alarm types corresponding to each alarm capability in the channel alarm capability set acquired by the front-end equipment, but directly generates the linkage configuration file by using the capability identification of the alarm capability. Therefore, no matter whether the channel alarm capability of the front-end equipment is concentrated with the newly updated alarm capability or not, the configuration for a new alarm type does not need to be separately updated and developed by the back-end equipment, so that the subsequent back-end equipment can be matched with the capability identifier and the alarm source in the generated linkage configuration file according to the capability identifier and the front channel identifier carried in the alarm message when receiving the alarm message, thereby determining the linkage configuration file corresponding to the alarm message, further determining the corresponding linkage rule and executing the corresponding operation. Compared with the prior art, the scheme can conveniently and quickly enable the updated front-end equipment to add the alarm message of the new alarm type to be identified and processed by the back-end equipment on the basis of not updating the back-end equipment, thereby improving the reliability of the security system and reducing the development cost.

Optionally, obtaining a channel alarm capability set of the first front channel includes: acquiring all alarm capabilities supported by a first front channel; and filtering all the alarm capacities according to a preset filtering rule to obtain at least one alarm capacity forming a channel alarm capacity set, and forming the channel alarm capacity set by the at least one alarm capacity.

Optionally, the security system further includes a security platform, and the method further includes: receiving a linkage rule request from a security platform; the linkage rule request indicates a first back channel identifier and a first capability identifier; the first capability identification is one of the capability identifications of the at least one alarm capability; responding to the linkage rule request, determining a first linkage configuration file corresponding to the first back channel identifier and the first capacity identifier, and sending a first linkage rule in the first linkage configuration file to the security platform; the first linkage profile is one of the at least one linkage profile.

Optionally, the security system further includes a security platform, and the method further includes: receiving a linkage modification request from a security platform; the linkage modification request carries a first rear channel identifier, a second capacity identifier and an undetermined linkage rule; the second capability identification is one of the capability identifications of the at least one alarm capability; updating a second linkage configuration file corresponding to the first rear channel identifier and the second capacity identifier by using an undetermined linkage rule in response to the linkage modification request; the second linkage profile is one of the at least one linkage profile.

Optionally, the security system further includes a security platform, and the method further includes: receiving an alarm modification request from a security platform; the alarm modification request indicates the first back channel identifier and the undetermined alarm rule; the first back channel mark is the mark of the first back channel; determining a first front channel identifier corresponding to the first rear channel identifier according to the channel mapping relation; the channel mapping relation is used for indicating the corresponding relation between a rear channel of the rear-end equipment and a front channel of the front-end equipment; the first front channel identifier is an identifier of a first front access; replacing a first back channel identifier in the alarm modification request with the first front channel identifier to obtain an updated alarm modification request; and sending an updated alarm modification request to the front-end equipment so that the front-end equipment updates the alarm rule of the first front channel by using the undetermined alarm rule.

Further optionally, after sending the updated pending alarm request to the front-end device, the method further includes: receiving a modification response sent by the front-end equipment; the modification response indicates the first front channel identifier, and the modification response is used for indicating that the front-end equipment completes the modification of the alarm rule; determining a first rear channel identifier corresponding to the first front channel identifier according to the channel mapping relation, and replacing the first front channel identifier indicated in the modification response with the first rear channel identifier to obtain an updated modification response; and sending the updated modification response to the security platform.

Optionally, the method further includes: receiving an alarm message from front-end equipment; the first front channel identifier and the third capability identifier are indicated in the message alarm; the third capability identification is one of the capability identifications of the at least one alarm capability; determining a first back channel identifier corresponding to the first front channel identifier according to the channel mapping relation; the channel mapping relation is used for indicating the corresponding relation between the channel of the back-end equipment and the front channel of the front-end equipment; determining a third linkage configuration file corresponding to the first back channel identifier and/or the first front channel identifier and the third capacity identifier; the third linkage profile is one of the at least one linkage profile; and executing corresponding linkage operation according to the linkage rule in the third linkage configuration file.

Optionally, the security system further includes a security platform, and the method further includes: receiving a subscription request from a security platform; the subscription request carries a fourth capability identifier, a first back channel identifier and a resource transmission format; the subscription request is used for requesting to subscribe the alarm message corresponding to the fourth capability identifier and the first back channel identifier, and requesting the format of the alarm related resource carried in the alarm message to be a resource transmission format; the first back channel mark is the mark of the first back channel; responding to the subscription request, under the condition that an alarm message from front-end equipment is received, if a fifth capacity identification carried in the alarm message is a fourth capacity identification and a front channel identification carried in the alarm message is an identification of a first front channel corresponding to a first rear channel identification, replacing the front channel identification carried in the alarm message with the first rear channel identification, and setting the format of alarm-related resources in the message alarm to be a resource transmission format to obtain an updated alarm message; and sending the updated alarm message to the security platform.

Optionally, after acquiring the channel alarm capability set of the first front channel, the method further includes: comparing the channel alarm capacity set with the equipment alarm capacity set, and adding the alarm capacity which does not exist in the equipment alarm capacity set in the channel alarm capacity set into the equipment alarm capacity set; the device alarm capability set is composed of alarm capabilities prestored by the back-end device.

Optionally, the method further includes: receiving a display request from a security platform; the display request is used for requesting to display the equipment alarm capability set of the back-end equipment; determining an alarm name corresponding to each alarm capability in the equipment alarm capability set according to the name mapping table; the name mapping table is used for representing the alarm name corresponding to each alarm capability in the equipment alarm capability set; and sending at least one alarm capability in the equipment alarm capability set and the corresponding alarm name to the security platform.

Optionally, the security system further includes a security platform, and the method further includes: receiving a search instruction from a security platform; the search instruction indicates the capability identifier to be searched; responding to a search instruction, determining a storage identifier to be searched corresponding to the capability identifier to be searched according to the target association relation, and searching all data associated with the storage identifier to be searched according to the storage identifier to be searched; the target incidence relation is used for indicating the incidence relation of the capacity identifier and the storage identifier of each alarm capacity in the equipment alarm capacity set of the back-end equipment; the storage identification is obtained by the alarm capacity identification of the alarm capacity in the equipment alarm capacity set according to a Hash algorithm; and generating a search result based on the data associated with the storage identifier to be searched, and sending the search result to the security platform.

Further optionally, generating a search result based on all data stored in association with the storage identifier to be searched includes: under the condition that the storage identifier to be searched is determined to be repeated, target data associated with the capability identifier to be searched in the data associated with the storage identifier to be searched is determined; and taking the target data as a search result.

The second aspect provides a back-end device, which is applied to a security system, the security system further comprises a front-end device, and a first front channel of the front-end device is connected to a first back channel of the back-end device. The back-end equipment comprises an acquisition module and a processing module. The acquisition module is used for acquiring a channel alarm capacity set of the first front channel; the channel alarm capability set comprises at least one alarm capability supported by the first front channel, the alarm capability has a unique corresponding capability identifier, and the capability identifier has a unique corresponding alarm type. The processing module is used for generating at least one linkage configuration file according to the channel alarm capacity set and the alarm source acquired by the acquisition module; the linkage configuration files correspond to the alarm types one by one; the alarm source is used for indicating the first rear channel and/or the first front channel; the linkage configuration file comprises an alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule. And the linkage rule is used for indicating the back-end equipment to execute corresponding linkage operation when receiving the capability identification in the linkage configuration file to which the linkage rule belongs through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs.

Optionally, the obtaining module is specifically configured to obtain all alarm capabilities supported by the first front channel; and filtering all the alarm capacities according to a preset filtering rule to obtain at least one alarm capacity forming a channel alarm capacity set, and forming the channel alarm capacity set by the at least one alarm capacity.

Optionally, the security system further includes a security platform, and the back-end device further includes a sending module; the acquisition module is also used for receiving a linkage rule request from the security platform; the linkage rule request indicates a first back channel identifier and a first capability identifier; the first capability identification is one of the capability identifications of the at least one alarm capability; the processing module is also used for responding to the linkage rule request received by the obtaining module and determining a first linkage configuration file corresponding to the first back channel identifier and the first capacity identifier; the sending module is used for sending the first linkage rule in the first linkage configuration file determined by the processing module to the security platform; the first linkage profile is one of the at least one linkage profile.

Optionally, the security system further comprises a security platform; the acquisition module is also used for receiving a linkage modification request from the security platform; the linkage modification request carries a first rear channel identifier, a second capacity identifier and an undetermined linkage rule; the second capability identification is one of the capability identifications of the at least one alarm capability; the processing module is also used for responding to the linkage modification request received by the acquisition module and updating a second linkage configuration file corresponding to the first rear channel identifier and the second capacity identifier by using an undetermined linkage rule; the second linkage profile is one of the at least one linkage profile.

Optionally, the security system further comprises a security platform; the back-end equipment also comprises a sending module; the acquisition module is also used for receiving an alarm modification request from the security platform; the alarm modification request indicates the first back channel identifier and the undetermined alarm rule; the first back channel mark is the mark of the first back channel; the processing module is further used for determining a first front channel identifier corresponding to a first rear channel identifier indicated by the alarm modification request received by the acquisition module according to the channel mapping relation; the channel mapping relation is used for indicating the corresponding relation between a rear channel of the rear-end equipment and a front channel of the front-end equipment; the first front channel identifier is an identifier of a first front access; the processing module is further used for replacing a first back channel identifier in the alarm modification request with the first front channel identifier to obtain an updated alarm modification request; and the sending module is used for sending the updated alarm modification request obtained by the processing module to the front-end equipment so that the front-end equipment updates the alarm rule of the first front channel by using the undetermined alarm rule.

Optionally, after the sending module sends the updated alarm modification request obtained by the processing module to the front-end device, the obtaining module is further configured to receive a modification response sent by the front-end device; the modification response indicates the first front channel identifier, and the modification response is used for indicating that the front-end equipment completes the modification of the alarm rule; the processing module is further configured to determine, according to the channel mapping relationship, a first back channel identifier corresponding to the first front channel identifier indicated by the modification response received by the obtaining module, and replace the first front channel identifier indicated in the modification response with the first back channel identifier, so as to obtain an updated modification response; the sending module is further used for sending the updated modification response to the security platform.

Optionally, the obtaining module is further configured to receive an alarm message from the front-end device; the first front channel identifier and the third capability identifier are indicated in the message alarm; the third capability identification is one of the capability identifications of the at least one alarm capability; the processing module is also used for determining a first back channel identifier corresponding to the first front channel identifier indicated by the alarm message received by the acquisition module according to the channel mapping relation; the channel mapping relation is used for indicating the corresponding relation between the channel of the back-end equipment and the front channel of the front-end equipment; the processing module is further configured to determine a third linkage configuration file corresponding to the first back channel identifier and/or the first front channel identifier, and the third capability identifier; the third linkage profile is one of the at least one linkage profile; the processing module is further used for executing corresponding linkage operation according to the linkage rule in the third linkage configuration file.

Optionally, the security system further comprises a security platform; the back-end equipment also comprises a sending module; the acquisition module is also used for receiving a subscription request from the security platform; the subscription request carries a fourth capability identifier, a first back channel identifier and a resource transmission format; the subscription request is used for requesting to subscribe the alarm message corresponding to the fourth capability identifier and the first back channel identifier, and requesting the format of the alarm related resource carried in the alarm message to be a resource transmission format; the first back channel mark is the mark of the first back channel; the processing module is further configured to respond to the subscription request received by the obtaining module, and under the condition that the obtaining module receives an alarm message from the front-end device, if a fifth capability identifier carried in the alarm message is a fourth capability identifier and a front channel identifier carried in the alarm message is an identifier of a first front channel corresponding to the first back channel identifier, replace the front channel identifier carried in the alarm message with the first back channel identifier, and set a format of an alarm-related resource in the alarm message to a resource transmission format to obtain an updated alarm message; and the sending module is used for sending the updated alarm message obtained by the processing module to the security platform.

Optionally, after the obtaining module obtains the channel alarm capability set of the first front channel, the processing module is further configured to compare the channel alarm capability set obtained by the obtaining module with the device alarm capability set, and add, into the device alarm capability set, an alarm capability that does not exist in the device alarm capability set in the channel alarm capability set; the device alarm capability set is composed of alarm capabilities prestored by the back-end device.

Further optionally, the security system further comprises a security platform; the back-end equipment also comprises a sending module; the acquisition module is also used for receiving a display request from the security platform; the display request is used for requesting to display the equipment alarm capability set of the back-end equipment; the processing module is also used for determining an alarm name corresponding to each alarm capability in the equipment alarm capability set according to the name mapping table; the name mapping table is used for representing the alarm name corresponding to each alarm capability in the equipment alarm capability set; and the sending module is used for sending at least one alarm capability in the equipment alarm capability set determined by the processing module and the corresponding alarm name to the security platform.

Optionally, the security system further comprises a security platform; the back-end equipment also comprises a sending module; the acquisition module is also used for receiving a search instruction from the security platform; the search instruction indicates the capability identifier to be searched; the processing module is also used for responding to the search instruction received by the acquisition module, determining a storage identifier to be searched corresponding to the capability identifier to be searched indicated by the search instruction according to the target association relation, and searching all data associated with the storage identifier to be searched according to the storage identifier to be searched; the target incidence relation is used for indicating the incidence relation of the capacity identifier and the storage identifier of each alarm capacity in the equipment alarm capacity set of the back-end equipment; the storage identification is obtained by the alarm capacity identification of the alarm capacity in the equipment alarm capacity set according to a Hash algorithm; the processing module is also used for generating a search result based on the data associated with the storage identifier to be searched; and the sending module is used for sending the search result generated by the processing module to the security platform.

Further optionally, the processing module is specifically configured to: under the condition that the storage identifier to be searched is determined to be repeated, target data associated with the capability identifier to be searched in the data associated with the storage identifier to be searched is determined; and taking the target data as a search result.

In a third aspect, a backend device is provided, comprising a processor and a memory for storing processing executable instructions; wherein the processor is configured to execute the executable instructions to cause the backend device to implement the alarm linkage configuration method as provided in the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, where the computer-readable storage medium includes computer-executable instructions, and when the computer-executable instructions are executed on a backend device in a security system, the backend device executes the alarm linkage configuration method according to the first aspect.

In a fifth aspect, a computer program product is provided, which contains instructions that, when run on a backend device in a security system, cause the backend device to perform the alarm linkage configuration method as provided in the first aspect.

In a sixth aspect, a security system is provided, which includes the backend device provided in the second aspect or the backend device provided in the third aspect.

It can be understood that the solutions of the second aspect to the sixth aspect provided above all correspond to the alarm linkage configuration method of the first aspect, and therefore, the beneficial effects that can be achieved by the solutions can refer to the beneficial effects in the corresponding alarm linkage configuration method provided above, and are not described herein again.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

In order to more clearly illustrate the embodiments of the present application 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 application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram of an architecture of a security system provided in an embodiment of the present application;

fig. 2 is a first flowchart illustrating an alarm linkage configuration method according to an embodiment of the present disclosure;

fig. 3 is a second schematic flowchart of an alarm linkage configuration method according to an embodiment of the present application;

fig. 4 is a third schematic flowchart of an alarm linkage configuration method according to an embodiment of the present application;

fig. 5 is a first supplementary flowchart of an alarm linkage configuration method according to an embodiment of the present disclosure;

fig. 6 is a schematic supplementary flowchart of a method for configuring alarm linkage according to an embodiment of the present application;

fig. 7 is a schematic supplementary flowchart of a method for configuring alarm linkage according to an embodiment of the present application;

fig. 8 is a schematic supplementary flowchart of a fourth alarm linkage configuration method according to an embodiment of the present application;

fig. 9 is a schematic supplementary flowchart of an alarm linkage configuration method according to an embodiment of the present application;

fig. 10 is a schematic supplementary flowchart of a method for configuring alarm linkage according to an embodiment of the present application;

fig. 11 is a seventh supplementary flowchart of an alarm linkage configuration method according to an embodiment of the present application;

fig. 12 is a supplementary flowchart of an alarm linkage configuration method according to an embodiment of the present application, schematically illustrating an eighth step;

fig. 13 is a schematic supplementary flowchart illustration nine of an alarm linkage configuration method according to an embodiment of the present application;

fig. 14 is a supplementary flowchart illustrating a method for configuring an alarm linkage according to an embodiment of the present disclosure;

fig. 15 is a schematic structural diagram of a backend apparatus according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another backend apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, 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 application.

It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

It should be noted that in the embodiments of the present application, "of", "corresponding" and "corresponding" may be sometimes used in combination, and it should be noted that the intended meaning is consistent when the difference is not emphasized.

For the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", and the like are used for distinguishing the same items or similar items with basically the same functions and actions, and those skilled in the art can understand that the terms "first", "second", and the like are not limited in number or execution order.

For ease of understanding, the words in the examples of this application are introduced:

IPC: the internet protocol camera is a new generation camera combining traditional camera and internet technology, which can transmit images to the other end of the earth through the internet, and the remote browser can monitor the images without any professional software. The network camera is generally composed of a lens, an image sensor, a sound sensor, an A/D converter, an image sensor, a sound sensor, a controller network server, an external alarm, a control interface and the like.

NVR: the network video recorder is a storage and forwarding part of a network video security system, and the NVR and the video encoder or the network camera work cooperatively to achieve specific decoding capability, so that video recording, storage and forwarding can be completed.

And (3) Hash algorithm: HASH, which is generally translated as a HASH, or transliteration, is the process of converting an input of arbitrary length (also called pre-image) into a fixed-length output, known as a HASH value, by a hashing algorithm.

Front-end equipment: the device refers to a device which is arranged on the site or at the forefront in a security system. Such as IPC, entrance guard equipment and the like, which collect data in real time on site. In this embodiment, a communication interface or a communication link used by the front-end device to connect to the back-end device may be referred to as a front channel.

A back-end device: the device is a device which receives an alarm (alarm message) of a front-end device in the security system and performs linkage operation on the alarm according to a preset linkage rule. Such as NVR. In this embodiment, a communication interface or a communication link used by the backend device to connect to the frontend device may be referred to as a back channel.

Security protection platform: the device refers to a device or a cloud platform which can remotely manage front-end equipment and back-end equipment in a security system.

An alarm event: when the front-end equipment collects data, the related parameters of the data accord with a preset alarm strategy or condition. At this time, the front-end device will generate a corresponding alarm message and upload the alarm message to the back-end device. Alarm policies or conditions corresponding to alarm events of different alarm types are different.

In the existing security system, the data formats of alarm messages generated by front-end devices aiming at alarm events of different alarm types may be different. The analysis and identification of the alarm messages of the back-end equipment aiming at the alarm events of different alarm types need to write corresponding analysis programs or scripts manually. With the development of digital technology, more and more front-end devices (such as network cameras, access control devices and the like) in the existing security system are more intelligent. Through the updating and upgrading of the equipment, the front-end equipment can identify richer alarm events, has stronger alarm function and can report more different alarm messages to the back-end equipment. In this case, if the backend device is not updated, the backend device cannot identify and process the alarm message corresponding to the new alarm event. However, the structure is complex, the cost is high, and the development period required for updating is long, so that the security system with updated front-end equipment cannot use the updated function quickly.

In view of the foregoing problems, an embodiment of the present application provides an alarm linkage configuration method applied in a security system, which can automatically identify a channel alarm capability set (composed of at least one alarm capability supported by a front-end device, where each alarm capability corresponds to a unique capability identifier, and each capability identifier matches one alarm type), and automatically generate a linkage rule configuration file corresponding to each alarm type of a channel through which each back-end device and the front-end device are connected, according to the capability identifier of each alarm capability and an alarm source (for example, a back channel of the back-end device and/or a front channel of the front-end device) for indicating an alarm message transmission channel. Therefore, when receiving the alarm message, the subsequent back-end device can match the capacity identifier and the alarm source in the linkage configuration file according to the capacity identifier carried in the alarm message and the identifier of the front channel of the front-end device (the back-end device can have a mapping table indicating the corresponding relation between the back channel and the front channel, and the identifier of the back channel corresponding to the identifier of any front channel can be determined according to the mapping table), so as to determine the linkage configuration file corresponding to the alarm message, further determine the corresponding linkage rule and execute the corresponding operation.

The alarm linkage configuration method provided by the embodiment of the application can be applied to a security system. Fig. 1 shows one possible structure of the security system. As shown in fig. 1, the security system may include a security platform 01, a backend device 02, and at least one front-end device 03. In fig. 1, at least one front-end device 03 is indicated by a front-end device 03A, a front-end device 03B, and a front-end device 03C, and in practice, the number of the front-end devices may be more or less. The security platform 01 and the back-end equipment 02 are in communication connection in a wired or wireless mode. The backend device 02 and the frontend device 03 are connected in a wired or wireless communication manner.

In the embodiment of the application, the communication among the security platform 01, the back-end device 02 and the front-end device is communicated by the same standardized communication protocol. In the communication protocol, each alarm type is matched with a unique capability identifier, and each capability identifier corresponds to a unique alarm capability.

The security platform 01 is specifically configured to receive an operation of a user, and manage the backend device 02 and the front-end device 03 in response to the operation of the user. Including, but not limited to, modification of linkage rules in the back-end equipment, and modification of alarm rules in the front-end equipment 03. For example, the security platform may be a server or a service cluster formed by a plurality of servers or a data center. This is not specifically limited by the present application.

The back-end device 02 is mainly configured to receive the alarm message reported by the front-end device 03 and perform parsing processing on the alarm message. The back-end device 02 is further configured to receive an instruction of the security platform to modify a linkage rule of the back-end device, or instruct the front-end device 03 to modify an alarm rule of the front-end device 03, or send information in an alarm message reported by the front-end device 03 to the security platform according to a certain rule. Of course, this is merely an example, and in reality, the backend device 02 may have any other feasible functions, and this application is not limited to this specifically. For example, the backend device may be a variety of terminals with decoding capability, playing capability, and storage capability, such as a personal computer, a notebook computer, a smart phone, a tablet computer, and other computing devices. The device can also be a video recorder device such as a Digital Video Recorder (DVR) or a network video recorder.

In the embodiment of the present application, the backend device 02 is provided with a plurality of channels (i.e., communication interfaces or communication links), and each channel can be used to access one channel (i.e., communication interface or communication link) of the frontend device 03. For convenience of description, in this embodiment of the present application, a channel of the backend device 02 may be referred to as a back channel, and a corresponding identifier of the back channel is a back channel identifier; the channel of the front-end device 03 may be referred to as a front channel, and its corresponding identifier is a front channel identifier. The front-end device 03 is specifically configured to collect data of a designated area, such as video data, audio data, a photo, and the like. When the front-end device 03 collects data in a designated area, if the collected data meets a preset alarm policy/rule/condition, a corresponding alarm message is generated and reported to the back-end device 02. Taking the collected data as an example of a photo, the reported alarm message should include, in addition to a message header specified by the communication protocol, its own features (e.g., a front channel identifier, an equipment identifier, etc.), features of a corresponding alarm type (e.g., a capability identifier), and corresponding data features (e.g., a photo name, a photo format, a photo content, features extracted from a photo (e.g., a face feature), a confidence level, etc.).

In the embodiment of the present application, the front-end device 03 may have one or more channels according to its own structure, for example, if the front-end device 03 is an IPC, if the IPC itself has two cameras, the IPC may have two channels. The channels of the front-end device 03 may all be connected to the back-end device 02, or part of the channels may be connected to the back-end device.

In this embodiment, the format of the data packet reported to the back-end device 02 by the front-end device 03 is fixed, so that the back-end device 02 can quickly analyze and identify the data packet.

In some embodiments, referring to fig. 1, in the security system, a user may also use a client of the user to manage the backend device 02 and the frontend device 03 through a web.

Based on the security system shown in fig. 1, the alarm linkage configuration method provided by the embodiment of the present application is described below by taking the front-end device as the front-end device 03A, the back-end device as the NVR, and the first front channel of the front-end device 03A is accessed to the first back channel of the NVR as an example. Referring to fig. 2, the method may include 201 and 202:

201. the NVR acquires a channel alarm capability set of the first front channel of the front-end device 03A.

The first front channel may be any front channel of the front-end 03A accessing NVR. The channel alarm capability set of the first front channel comprises at least one alarm capability supported by the first front channel, the alarm capability has a uniquely corresponding capability identifier, and the capability identifier is matched with a uniquely corresponding alarm type. For example, the alarm capability may be a high altitude parabolic alarm capability, or the like; the capability identifier can be a character string uniquely corresponding to the alarm capability; the alarm type may then be the alarm type to which the alarm capability specifically corresponds, e.g. the alarm type may be a "high altitude parabolic alarm". The capability identifier of the alarm capability can be simultaneously in the access alarm capability, or a relationship table for representing the corresponding relationship between the alarm capability and the capability identifier can be independently existed. The front-end device may send the relationship table to the NVR together when the NVR acquires the set of channel alarm capabilities.

Of course, in practice, for storage convenience, the set of channel alarm capabilities of the first front channel may include only capability identifications of at least one alarm capability supported by the first front channel.

Specifically, the NVR may send an acquisition request to the front-end device 03A accessing itself, where the acquisition request may carry an identifier of a first front channel (i.e., a first front channel identifier) of a channel of the front-end device 03A accessing the NVR. After receiving the acquisition request, the front-end device 03A sends at least one alarm capability (specifically, a capability identifier uniquely corresponding to the alarm capability) corresponding to the identifier of the front channel to the back-end device NVR. Generally, at least one of these is all. Of course, in practice, the NVR may acquire a channel alarm capability set of all front channels of the front-end device accessing the NVR. In the technical scheme provided by the embodiment of the application, the first front channel in the subsequent part can also be other front channels of the front-end equipment accessing the back-end equipment. Of course, the corresponding rear channel will also change.

In practice, some alarm types may be processed by users without the desire of the users, or processed currently (for example, a security system needs to perform a face alarm before, and a fire alarm needs to be performed currently, so that the alarm type of the face alarm does not need to be processed currently), and the corresponding alarm capability can be filtered when the channel alarm capability set of the front-end device is obtained. So, in an implementable manner, as shown with reference to fig. 3 in conjunction with fig. 2, 201 may include 2011 and 2012:

2011. the NVR acquires all alarm capabilities supported by the first front channel of the front-end device 03A.

2012. And the NVR filters all the alarm capabilities supported by the first front channel according to a preset filtering rule to obtain at least one alarm capability forming a channel alarm capability set, and the at least one alarm capability forms the channel alarm capability set of the first front channel.

The preset filtering rule may be a preset filtering table, and a capability identifier of the alarm capability that is not desired to be processed may exist in the filtering table.

Therefore, the NVR does not acquire the alarm capacity which the user does not want to process at the beginning, and does not generate the corresponding linkage rule subsequently. Because the alarm message NVR is not acquired, the alarm message NVR corresponding to the subsequent alarm type cannot be analyzed and identified, and related alarm data cannot exist in the process of interacting with the security platform. The use experience of the user is enriched.

202. And the NVR generates at least one linkage configuration file according to the channel alarm capacity set and the alarm source.

The alarm source is used for indicating the first back channel of the NVR and/or the first front channel of the front-end device 03A.

In an implementation manner, for the generation of the linkage configuration file and the subsequent matching of the alarm message and the linkage configuration, both are performed on the backend device, so for the purpose of convenient configuration (the first back channel identifier is more easily obtained), the alarm source may be directly the identifier of the first back channel of the NVR (i.e., the first back channel identifier). In another implementation, the source of the alarm may be an identifier of the first front channel of the front-end device 03A, i.e., a first front channel identifier. In yet another implementation, the alarm source may also be a first back channel identification and a first front channel identification.

The linkage configuration files correspond to alarm types corresponding to the alarm capacity of the channel alarm capacity set one by one, wherein the correspondence specifically means that if a certain linkage configuration file is generated according to a capacity identifier matched with a certain alarm type, the two are corresponding. The linkage configuration file comprises an alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule. The linkage rule is used for indicating the NVR to execute corresponding linkage operation when receiving the capability identification in the linkage configuration file to which the linkage rule belongs through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs.

Illustratively, the linkage profile format is shown in table 1 below.

TABLE 1

Capability identification
	Alarm source
Rules of linkage

In the embodiment of the present application, since the linkage rule is to be corresponding to the capability identifier matching the channel (i.e. the first back channel and/or the first front channel indicated by the alarm source) connected between the back-end device and the front-end device and the alarm type, and which linkage operations need to be executed specifically by the linkage rule needs to be determined by the user, the linkage rule initially set by the back-end device herein only has a format, and specific contents need to be set in response to the operation of the user. For example, if the linkage rule includes arming time and linkage mode, the specific format of the linkage rule may be as shown in table 2 below.

TABLE 2

It can be seen that, at this time, the position for filling in the specific arming time and the linkage mode in the linkage rule is empty. Of course, in practice, it is possible to fill in with a character representing "empty", for example "0".

Based on the above technical solution, the back-end device (NVR) can automatically identify a channel alarm capability set (composed of at least one alarm capability (specifically, an alarm capability identifier) supported by a certain front channel of the front-end device) of the front-end device, and automatically generate a linkage rule configuration file corresponding to each alarm type of the channel connected between each back-end device and the front-end device according to each capability identifier and an alarm source (for example, the back channel of the back-end device and/or the front channel of the front-end device) capable of indicating an alarm message transmission channel according to a preset rule. In the process, the back-end equipment does not need to recognize or translate the alarm types corresponding to each alarm capability in the channel alarm capability set acquired by the front-end equipment, but directly generates the linkage configuration file by using the capability identification of the alarm capability. Therefore, no matter whether the channel alarm capability of the front-end equipment is concentrated with the newly updated alarm capability or not, the configuration for a new alarm type does not need to be separately updated and developed by the back-end equipment, so that the subsequent back-end equipment can be matched with the capability identifier and the alarm source in the generated linkage configuration file according to the capability identifier and the front channel identifier carried in the alarm message when receiving the alarm message, thereby determining the linkage configuration file corresponding to the alarm message, further determining the corresponding linkage rule and executing the corresponding operation. Compared with the prior art, the scheme can conveniently and quickly enable the updated front-end equipment to add the alarm message of the new alarm type to be identified and processed by the back-end equipment on the basis of not updating the back-end equipment, thereby improving the reliability of the security system and reducing the development cost.

In addition, since the linkage configuration file has an alarm source, a capability identifier and a linkage rule, the linkage configuration file is associated with the alarm type (capability identifier embodiment) and the communication channel (alarm source embodiment) of the front-end device with which the back-end device is associated. Therefore, even if the capability identifiers corresponding to the same alarm type in different front-end equipment are set differently, the rear-end equipment cannot be matched with wrong linkage rules.

In some embodiments, in order to enable the backend device to provide all self-supportable alarm types to the security platform, optionally, as shown in fig. 3 in conjunction with fig. 2, the step 201 may further include, after:

201A, NVR compares the channel alarm capability set with the device alarm capability set and adds alarm capabilities in the channel alarm capability set that do not exist in the device alarm capability set into the device alarm capability set.

The equipment alarm capacity set consists of alarm capacities prestored in a back-end equipment NVR. The warning capability prestored in the NVR is the warning capability which can be identified by the back-end equipment and is set when the NVR leaves a factory. Certainly, in the technical solution provided in this embodiment, the NVR itself does not need to identify the alarm capability specifically corresponding to the alarm message reported by the front-end device 03A, and directly uses the capability identifier carried by the NVR to perform the relevant processing. Of course, if the alarm capability of the device is stored in the alarm capability set as the capability identifier, the alarm capability that is added to the channel alarm capability set and does not exist in the alarm capability set of the device is specifically referred to as the capability identifier.

Therefore, when the security platform requests all the alarm capabilities (or alarm types) which can be currently supported by the back-end equipment from the back-end equipment, the back-end equipment can send the updated equipment alarm capability set which is accessed into the front-end equipment for the latest time to the security platform.

Further optionally, because the security platform requests its device alarm capability set from the backend device, it is primarily for presentation to the user, and what the user generally wants to see is the name of the device type. Based on this, referring to fig. 4 in conjunction with fig. 3, after 201A, the method may further include S1-S4:

s1, the NVR receives the display request from the security platform 01.

The display request is used for requesting to display the NVR equipment alarm capability set.

In some embodiments, the exposure request may also request exposure of a channel alarm capability set of the target back channel of the NVR. And the channel alarm capacity set of the target back channel is a channel alarm capacity set of a target front channel which is connected with the target back channel by the front-end equipment corresponding to the target back channel. In this case, the show request should carry the back channel id of the target back channel.

And S2, the NVR determines the alarm name corresponding to each alarm capability in the equipment alarm capability set according to the name mapping table.

The name mapping table is used for representing the alarm name corresponding to each alarm capability in the equipment alarm capability set. The alarm capability may specifically be a capability identification of the alarm capability.

The name mapping table may be set for the NVR when shipped from the factory.

In one implementation, the name mapping table can be referred to as shown in table 3 below.

TABLE 3

Alarm capability	Presetting alarm name

The preset alarm name may be a name set for a known alarm capability when the NVR leaves a factory. For the newly added alarm capability acquired by the NVR from the front-end device accessed by the NVR after leaving the factory, the NVR may add a new line in the name mapping table for placing the newly added alarm capability and the corresponding preset alarm name, and the preset alarm name of the newly added alarm capability may be the NVR itself.

In this case, the alarm name determined in S2 is the preset alarm name.

In another implementation, the name mapping table may be as shown in Table 4 below.

TABLE 4

Alarm capability	Presetting alarm name	Custom name

Under the condition that the name mapping table is the table shown in table 4, the NVR can receive the name customized to any one of the alarm capabilities by the user through the security platform, and fill the placement position of the customized name corresponding to the alarm capability in the table 4.

In this case, the NVR may determine whether each alarm capability identifier in the device alarm capability set has a corresponding custom name, determine the custom name as its alarm name if the custom name exists, and determine the preset alarm name as its alarm name if the custom name does not exist.

It should be noted that the "alarm capability" in the name mapping table mentioned in the foregoing embodiment may also be "capability identification" in practice. The alarm capability in the related expression can be replaced by the capability identification of the alarm capability.

S3, NVR sends at least one alarm capability in the equipment alarm capability set and the corresponding alarm name to the security platform 01.

In general, at least one of these may be all. Of course, if the display request sent by the security platform actually includes an alarm screening condition (for example, only the alarm type and the alarm name for the fire protection field are requested to be displayed), at least one alarm capability therein may be screened from all the alarm capabilities in the device alarm capability set according to the alarm screening condition.

S4, the security platform 01 receives and displays at least one capability identifier in the equipment alarm capability set from the NVR and the corresponding alarm name.

All alarm capabilities and corresponding alarm names displayed by the specific security platform can be realized in a mode of table 3 or table 4. Of course, any other feasible manner may be adopted, and the present application is not limited to this specifically.

Therefore, the user can quickly acquire the alarm names of all the alarm capabilities currently supported by the NVR through the security platform. Furthermore, if data in any flow of the subsequent alarm linkage configuration method can be displayed for a user to check through the security platform, the alarm capacity (or capacity identification of the alarm capacity) in the data can be converted into an alarm name to be displayed according to the name mapping table, so that the user can check more intuitively.

In some embodiments, taking as an example that the back-end device is an NVR, the front-end device is a front-end device 03A, and a first front channel of the front-end device 03A is accessed to a first back channel of the NVR, as shown in fig. 5, the method further includes S501 to S507:

s501, the security platform 01 receives configuration triggering operation and sends a channel capability set acquisition request to the NVR in response to the configuration triggering operation.

The trigger configuration operation may be an operation of instructing the security platform 01 to open a linkage rule configuration page of a certain back channel (for example, a first back channel) of the NVR. The specific operation may be any feasible operation, and the present application does not specifically limit this.

The channel capability set acquisition request comprises a first back channel identifier of a first back channel, which triggers the configuration operation indication. The channel capability set acquisition request is used for requesting a channel alarm capability set of the first back channel. The channel alarm capability set of the first back channel includes all the alarm capabilities supported by the first back channel or capability identifiers of the alarm capabilities (i.e. all the alarm capabilities supported by the first front channel of the front-end device connected to the first back channel or capability identifiers of the alarm capabilities). Of course, in this example, the first front channel and the first back channel are taken as an example, and other back channels and front channels connected between the back-end device and the front-end device may be actually used.

S502, the NVR receives a channel capacity set acquisition request from the security platform 01, responds to the channel capacity set acquisition request, and sends a channel alarm capacity set of a first back channel to the security platform 01.

S503, the security platform 01 receives and displays the channel alarm capacity set of the first back channel from the NVR.

Specifically, the security platform 01 may display the channel alarm capability set of the first back channel in the list.

S504, the security platform 01 receives the alarm selection operation, generates a linkage rule request indicating the first back channel identifier and the first capacity identifier in response to the alarm selection operation, and sends the linkage rule request to the NVR.

The linkage rule request may specifically include a first back channel identifier and a first capability identifier, and is used to request a linkage rule matched with the first back channel identifier and the first capability label.

If the channel alarm capability set of the first back channel includes the alarm capability supported by the first back channel and the capability identifier corresponding to the alarm capability, the alarm selection operation may be an operation in which the user selects the first alarm capability (or the capability identifier of the first alarm capability) in the channel alarm capability set of the first back channel displayed by the security platform 01. The first alarm capability may be one of at least one alarm capability of the set of channel alarm capabilities of the first channel mentioned in the previous embodiments. The first capability identifier is the capability identifier of the first alarm capability.

The channel alarm capability set of the first back channel includes an alarm capability identifier supported by the first back channel, and the alarm selection operation may be an operation in which the user selects the first alarm capability identifier in the channel alarm capability set of the first back channel displayed by the security platform 01. Of course, the alarm selection operation may also be any other feasible operation, which is determined according to the practical situation, and the application is not limited specifically.

And S505, the NVR receives a linkage rule request from the security platform 01.

S506, responding to the linkage rule request, the NVR determines a first linkage configuration file corresponding to the first rear channel identifier and the first capacity identifier.

Wherein the first ganged profile may be one of the at least one ganged profile generated according to the alarm source and the channel alarm capability set of the first front channel in the previous embodiments.

In an implementation manner, if the alarm source in the linkage configuration file generated in the foregoing embodiment is a first rear channel identifier capable of indicating a first rear channel, a first linkage configuration file corresponding to the first rear channel identifier and a first capability identifier may be directly determined from at least one linkage configuration file.

In another implementation manner, if the alarm source in the linkage configuration file generated in the foregoing embodiment is a first front lane identifier capable of indicating a first front lane, the NVR needs to determine a back lane identifier corresponding to the first front lane identifier in the linkage configuration file or determine a front lane identifier corresponding to the first back lane identifier in the linkage rule request according to a pre-stored lane mapping relationship, and then may determine a first linkage configuration file corresponding to the first back lane identifier and the first capability identifier from at least one linkage configuration file.

In another implementation manner, if the alarm source in the linkage configuration file generated in the foregoing embodiment is a first front channel identifier capable of indicating a first front channel and a first rear channel identifier capable of indicating a first rear channel, the first linkage configuration file corresponding to the first rear channel identifier and the first capability identifier may be directly determined from at least one linkage configuration file.

S507, the NVR sends the first linkage rule in the first linkage configuration file to the security platform 01.

If the first linkage configuration file is newly generated after the NVR is connected to a certain front-end device, the first linkage rule has no substantial content, and only the format frame is shown in table 2.

Therefore, the user can smoothly check the linkage rule corresponding to any alarm capability of any channel of the NVR through the security platform, and the user experience is improved.

In some embodiments, taking as an example that the back-end device is an NVR, the front-end device is a front-end device 03A, and a first front channel of the front-end device 03A is accessed to a first back channel of the NVR, as shown in fig. 6, the method further includes S601-S603:

s601, the security platform 01 receives linkage modification operation, generates a linkage modification request in response to the modification operation, and sends the linkage modification request to the NVR.

And the linkage modification request indicates the first rear channel identifier, the second capacity identifier and the undetermined linkage rule. The linkage modification request may specifically carry the first back channel identifier, the second capability identifier, and the undetermined linkage rule, and may be used to request updating of the linkage rule in the linkage configuration file matched with the first back channel identifier and the second capability identifier using the undetermined linkage rule.

The linkage modification operation may specifically be an operation of inputting the first rear channel identifier, the second capability identifier (or the alarm capability to which the second capability identifier belongs), and the pending linkage rule, or an operation of selecting the first rear channel identifier and the second capability identifier (or the alarm capability to which the second capability identifier belongs) and inputting the pending linkage rule. The second capability identifier may be one of the capability identifiers of at least one alarm capability in the set of channel alarm capabilities of the first channel mentioned in the previous embodiments.

And S602, the NVR receives a linkage modification request from the security platform 01.

And S603, responding to the linkage modification request by the NVR, and updating a second linkage rule in a second linkage configuration file corresponding to the first rear channel identifier and the second capacity identifier by using the undetermined linkage rule.

Specifically, how to determine the second linkage configuration file corresponding to the first back channel identifier and the second capability identifier may refer to the foregoing description for determining the first linkage configuration file corresponding to the first back channel identifier and the first capability identifier, and details are not repeated here.

In a possible implementation manner, if the first linkage rule in the foregoing embodiment has no substantial content, the step S601 is executed after the step S507. At this time, the second capability identifier may be the first capability identifier, the pending linkage rule is the first linkage rule in which the user adds or modifies some parameters, and the second linkage rule is the first linkage rule without substantial content. At this time, the linkage modification operation may be an operation in which the user inputs a rule of pending linkage. The operation of inputting the undetermined linkage rule may be modification of the first linkage rule or may be directly input of the undetermined linkage rule, which is not specifically limited in this application.

Optionally, because there may be a malicious intrusion of the security system or a program bug in practice, the identifier and the capability identifier of the back channel input or selected by the user through the security platform are changed to the first back channel identifier and the second capability identifier, based on fig. 6, as shown in fig. 7, S603 may specifically be S603A:

S603A, responding to the linkage modification request, and under the condition that it is determined that a second linkage configuration file corresponding to the first back channel identifier and the second capability identifier exists, using the undetermined linkage rule to update a second linkage rule in the second linkage configuration file corresponding to the first back channel identifier and the second capability identifier.

In addition, if it is determined that the second linkage configuration file corresponding to the first back channel identifier and the second capacity identifier does not exist, discarding the linkage modification request, and indicating information such as linkage rule modification failure or linkage rule incapability of modification to the security platform.

It should be noted that, if a user needs to select the alarm capability of the linkage rule to be modified from the capability identifiers of the alarm capabilities, which are displayed in the device alarm capability set or the channel alarm capability set of the back-end device and displayed in the security platform, when modifying the linkage rule, in order to enable the user to know what alarm capability (or alarm type) linkage rule is specifically modified when modifying the linkage rule, in the embodiment of the present application, the capability identifier may have actual semantics. For example, if the alert capability is a human face alert, then its capability identification may be a face.

Based on the scheme, the user can smoothly modify the linkage rule corresponding to any alarm capability (or alarm type) of any channel of the NVR according to the security platform, and the user experience is improved.

In some embodiments, taking as an example that the back-end device is an NVR, the front-end device is a front-end device 03A, and a first front channel of the front-end device 03A is accessed to a first back channel of the NVR, as shown in fig. 8, the method further includes S801 to S806:

s801, the security platform 01 receives the alarm modification operation, generates an alarm modification request in response to the alarm modification operation, and sends the alarm modification request to the NVR.

The alarm modification request indicates the first back channel identifier and the undetermined alarm rule and is used for requesting to update/modify the alarm rule of the front channel of a certain front-end device connected with the back channel corresponding to the first back channel identifier by using the undetermined alarm rule. Specifically, the alarm modification request may carry the first back channel identifier and the to-be-determined alarm rule.

In an implementation manner, before S801, the security platform 01 may further receive an alarm request operation, generate an alarm rule request carrying the first back channel identifier in response to the alarm request operation, and send the alarm rule request to the NVR. The alarm request operation may be an operation of a user on the security platform 01, an operation performed after the user logs on the security platform 01 through other devices, or an operation generated in any other feasible manner, and the application is not particularly limited.

The alarm rule request is used for requesting an alarm rule of the front-end equipment corresponding to the first back channel identifier. Then, the NVR may send the alarm rule request to the front-end device 03A connected to its first back channel (the channel identified by the first back channel), so that the front-end device 03A sends the alarm rule of the first front channel, where the front-end device accesses the first back channel, to the NVR. And then, the NVR sends the alarm rule to the security platform 01 so that the security platform 01 displays the alarm rule. Thereafter, the security platform 01 performs S801.

In this case, the alarm modification operation may be a modification operation of the alarm rule displayed by the security platform 01 by the user, or an operation of directly inputting the pending alarm rule. The undetermined alarm rule is the updated alarm rule displayed by the security platform 01.

In the embodiment of the present application, the alarm rule specifically refers to a condition or a policy for generating an alarm message.

S802, NVR receives an alarm modification request from the security platform 01.

And S803, the NVR determines a first front channel identifier corresponding to the first back channel identifier according to the channel mapping relation.

The channel mapping relationship is used for indicating the corresponding relationship between the channel of the back-end equipment and the channel of the front-end equipment accessed to the back-end equipment. The first back channel mark is the mark of the first back channel, and the first front channel mark is the mark of the first front channel.

S804, the NVR replaces the first back channel identification in the alarm modification request by the first front channel identification to obtain an updated alarm modification request.

S803 and S804 are intended for, when the front-end device 03A receives the alarm modification request sent by the NVR, if the alarm modification request carries the first back channel identifier, since the first back channel identifier may not exist in all the front channel identifiers of the front-end device 03A, or the front channel identifier that is the same as the first back channel identifier but is not the front channel identifier of the front channel accessed to the NVR exists, the updated alarm modification request needs to be generated in order that the front-end device 03A can accurately identify and modify the alarm rule corresponding to the alarm modification request.

S805, the NVR sends the updated alarm modification request to the front-end device 03A corresponding to the first front channel identifier.

S806, in response to the updated alarm modification request, the front-end device 03A updates the alarm rule of the first front channel of the front-end device 03A using the pending alarm rule.

Of course, in practice, the alarm rules of all front lanes of the front-end segment device may be the same, and in this case, the alarm modification request may not carry the first back lane identifier, and the updated alarm modification request may not be generated.

Based on the technical scheme corresponding to the S801-S806, the user can smoothly modify the alarm rule of any front channel of any front-end device corresponding to the NVR through the security platform.

Optionally, in order to enable the security platform 01 to know that the alarm rule of the front-end device 03A has been successfully modified, with reference to fig. 9 in conjunction with fig. 8, S806 further includes S807-S810:

s807, the front-end device 03A sends a modification response to the NVR.

The modification response indicates the first front-channel identification, and the modification response indicates that the front-end device 03A has completed modifying the alarm rule. Specifically, the modification correspondence may carry the first front channel identifier.

And S808, the NVR receives the modification response sent by the front-end device 03A.

And S809, the NVR determines a first back channel identifier corresponding to the first front channel identifier according to the channel mapping relation, and replaces the first front channel identifier indicated by the modification response with the first back channel identifier to obtain an updated modification response.

The purpose of S809 is that, when the user operates the security platform to modify the alarm rule of a certain front channel, the user does not need to know which front channel is of which front-end device, but directly selects a certain channel of the back-end device that the user wants to modify. Therefore, the subsequent modification response does not need to embody the relevant identifier (i.e. the first front channel identifier) of the front-end device, and thus only the first back channel identifier needs to be indicated in the modification response.

And S810, the NVR sends the updated modification response to the security platform 01.

It should be noted that, in the case that the front-end device 03A does not complete the modification of the alarm rule for any reason, the modification response in the foregoing embodiment may also be used to indicate that the front-end device 03A does not complete the modification of the alarm rule. The specific implementation flows are similar and are not described herein again.

Based on the scheme, the user can timely know whether the rear channel of the designated NVR finishes the modification of the alarm rule on the front-end equipment or not according to the security platform.

In some embodiments, in order to enable the back-end device to smoothly determine the linkage rule according to the alarm message reported by the front-end device and execute the corresponding linkage operation, taking the back-end device as the NVR, the front-end device as the front-end device 03A, and taking an example that the first front channel of the front-end device 03A is accessed to the first back channel of the NVR, as shown in fig. 10, the method further includes S101 to S105:

s101, the NVR receives an alarm message from the front-end equipment 03A.

The alarm packet carries a first front channel identifier and a third capability identifier, and a specific alarm packet may carry the first front channel identifier and the third capability identifier. In addition, alarm related resources also exist in the alarm message; the data format of the alarm message may be a preset protocol format.

Wherein the third capability identifier may be one of the capability identifiers of at least one alarm capability in the set of channel alarm capabilities of the first front channel mentioned in the foregoing embodiments.

For example, taking the example that the front-end device 03A collects the picture data, the data format of the alarm message may be as shown in table 5 below.

TABLE 5

Message header
	Alarm information head
Alarm information
	Picture 1 head
Picture 1
	Picture 2 head
Picture 2
	…

The essential content of the whole alarm message comprises 1 alarm message and a plurality of pictures.

The message header contains the length and addressing information of the whole alarm message. The alarm information header contains the length of the alarm information. The picture X header includes the length (i.e., size) of the picture X and the picture ID of the picture X.

The alarm information includes basic information, characteristic information, and accessory information.

Wherein the basic information includes: a capability identifier (i.e., the aforementioned third capability identifier), an Internet Protocol (IP) address of a front-end device generating the alarm message, and a front-channel identifier of a front-channel of the front-end device transmitting the alarm message (i.e., the aforementioned first front-channel identifier).

The characteristic information includes: the description information of the alarm content, such as the features of the target (license plate number, facial features, etc.), the confidence level (for representing the credibility that the target corresponding to the alarm message is the target that needs to be alarmed), etc.

The accessory information includes: name and picture format of each picture, etc.

The aforementioned alarm-related resource may be all contents of the alarm message except the first front channel identifier and the third capability identifier.

S102, the NVR analyzes the alarm message according to a preset rule to obtain a first front channel identifier and a third capacity identifier carried by the alarm message.

Since the format of the alarm message is well specified by the communication protocol between the NVR and the front-end device 03A, the preset rule is an analysis rule corresponding to the communication protocol.

S103, determining a first back channel identifier corresponding to the first front channel identifier by the NVR according to the channel mapping relation.

The channel mapping relationship is used to indicate a correspondence relationship between a channel of the backend device (here, NVR) and a channel of the front-end device (here, front-end device 03A) accessing the backend device. The first back channel identifier is a back channel identifier of a first back channel connected to the first front channel corresponding to the first front channel identifier and the NVR.

S104, determining a third linkage configuration file corresponding to the first back channel identifier, the first front channel identifier and/or the third capability identifier by the NVR.

Specifically, since the alarm source and the capability identifier indicating the communication channel (e.g., the first front channel and/or the first rear channel) of the back-end device and the front-end device exist in the previously generated linkage profile, the third linkage profile can be accurately determined here. The third linkage profile here may be a linkage profile corresponding to the third capability identifier in at least one linkage profile generated in the foregoing embodiment. Here, whether the NVR uses the first back channel identifier or the first front channel identifier, or both, and the third capability identifier is combined to determine the third linkage configuration file, which specifically needs to be determined according to the specific content of the alarm source in the previously generated linkage configuration file, and specifically refers to the foregoing related expressions, which are not described herein again. In other embodiments, because the NVR itself generates many linkage profiles, there are many linkage rules, and the operations that need to be performed by different linkage rules are different. If some linkage rules that perform the same linkage operation are processed by the same processing module (which may be referred to as a linkage processing module), processing efficiency is improved. Based on this, in practice, a plurality of linkage processing modules may exist in the NVR, and after the communication module of the NVR receives the alarm message from the front-end device 03A, the alarm message needs to be transmitted to all linkage processing modules, so that the linkage processing modules in all linkage processing modules, which meet the requirement of the alarm message (i.e., after the alarm message is analyzed, the determined linkage rule belongs to the linkage rule that can be processed by the linkage processing modules themselves), perform processing.

It can be seen that, because each linkage processing module needs to analyze the alarm message to know whether the alarm message can be processed, all the analysis actions need to be performed by each linkage processing module, so that the consumption of NVR computing resources is greatly increased. In order to reduce the consumption of computing resources, after receiving the alarm message, the NVR may analyze the alarm message first, and after obtaining the corresponding back channel identifier (i.e., the first back channel identifier) and the capability identifier of the alarm capability (i.e., the third capability identifier), re-integrate the contents of the alarm message except for the message header and the alarm information header into data in a specific data format that can be directly recognized without being analyzed, which may be referred to as unified alarm information. Then, can transmit this unified alarm information for all linkage processing modules, so, because NVR is whole only need to resolve once, so greatly reduced computational resource's consumption.

For example, taking the alarm message shown in table 5 as an example, the format of the unified alarm information may be as shown in table 6 below.

TABLE 6

Capability identification
	Alarm source
Time of alarm
	Alarm information
Number of pictures
	Picture array

The alarm source may include a back channel identifier and/or a front channel identifier, and the alarm time may be the time for the alarm message to be uploaded to the NVR. The alarm information is the alarm information in the original data message. The picture array may be all picture headers and pictures in the foregoing embodiments.

Further, since the unified alarm message includes all the essential information in the alarm message, it can also be used by NVR for developing some other services for the alarm message.

And S105, the NVR executes corresponding linkage operation according to the linkage rule in the third linkage configuration file.

Based on the scheme, before the NVR, when accessing one front-end device, a corresponding linkage configuration file can be generated for the alarm capability (or alarm type) supported by the front-end device, and the linkage configuration file can be modified after receiving the modification operation of the user. Therefore, after receiving the alarm message corresponding to any alarm capability of the front-end device and analyzing the alarm message to obtain the corresponding back channel identifier and capability identifier, the NVR can smoothly determine the linkage configuration file and the linkage rule matched with the back channel identifier and the capability identifier, and further complete the corresponding linkage operation. Furthermore, only the front channel identifier and the capability identifier in the alarm message need to be concerned, and other information does not need to be concerned, so that the complexity of processing the alarm message by the NVR is greatly reduced, the NVR can be normally used without carrying out complex development on the NVR, the cost is greatly reduced, and the efficiency is improved.

In some embodiments, in practice, a user may need to obtain an alarm message corresponding to some specific alarm type regularly or in real time through a security platform, so based on this, taking the backend device as NVR, the front-end device as the front-end device 03A, and taking as an example that the first front channel of the front-end device 03A is accessed to the first back channel of the NVR, as shown in fig. 11, the method further includes S111-S114:

and S111, the NVR receives a subscription request from the security platform 01.

The subscription request indicates a fourth capability identifier, a first back channel identifier (identifier of a first back channel), and a resource transmission format, and specifically, the subscription request may carry the fourth capability identifier, the first back channel identifier, and the resource transmission format. The resource transmission format is at least any one of: binary data, a download address of the back-end equipment and a cloud download address; the subscription request is used for requesting to subscribe the alarm message corresponding to the fourth capability identifier and the first back channel identifier, and requesting that the format of the alarm-related resource carried in the alarm message is a resource transmission format.

Wherein the fourth alarm type may be one of the capability identifications of at least one alarm capability in the set of channel alarm capabilities of the first front channel mentioned in the previous embodiments. The subscription request may be generated after the security platform 01 receives a subscription operation of the user.

Optionally, when the user subscribes to an alarm packet of a certain alarm type through the security platform, the user does not know which alarm types are supported by the NVR at this time, so before S111 and S112, as shown in fig. 11 with reference to fig. 12, the method further includes S111A and S111B:

S111A, the NVR judges whether the fourth capability identification in the subscription request exists in the device alarm capability set of the NVR.

If the NVR determines that the fourth capability identifier in the subscription request exists in the device alarm capability set of the NVR, S112 is executed; if the NVR determines that the fourth capability identification in the subscription request does not exist in the device alert capability set of the NVR, S111B is performed.

The device alarm capability set is updated by NVR each time the NVR accesses the front-end device, and specific implementation may refer to the related expression in the foregoing embodiment 201A, which is not described herein again.

S111B, NVR discards the subscription request and sends a subscription failure indication to the security platform 01.

The subscription failure indication is at least used for indicating that the subscription fails, and can also be used for indicating that the reason for the subscription failure is that the specified alarm type does not exist.

Therefore, after receiving the subscription request, the NVR can only receive and process the subscription request which can be processed by itself, and can inform the user of the subscription request which can not be processed in time, so that the user experience is improved.

And S112, the NVR receives the alarm message from the front-end device 03A, and analyzes the alarm message according to a preset rule to obtain a front channel identifier, a fifth capability identifier and alarm related resources carried by the alarm message.

The data format of the alarm message is a preset protocol format. For specific implementation, reference may be made to the related contents of S101 and S102, which are not described herein again.

S113 and NVR respond to the subscription request, and in a case of receiving the alarm packet from the front-end device 03A, if the fifth capability identifier carried in the alarm packet is the fourth capability identifier and the front channel identifier carried in the alarm packet is the first front channel identifier corresponding to the first back channel identifier, replace the front channel identifier in the message with the first back channel identifier, and convert the alarm-related resource in the message into a resource transmission format, so as to obtain an updated alarm packet.

In addition, in the process of actually using the security system, the user only needs to know the information of the NVR through the security platform 01, and does not need to know the information of the front-end device 03A. Therefore, in this embodiment of the application, in addition to replacing the front channel identifier in the alarm message with the first back channel identifier in S113, all information that can indicate the front-end device 03A in the alarm message needs to be modified into related information that indicates NVR. For example, taking the alarm message shown in table 4 as an example, the IP address of the front-end device 03A generating the alarm message in the basic information in the alarm information needs to be modified to the IP address of NVR.

In an implementation manner, if the resource transmission format is binary data, the updated alarm message is the same as the original alarm message except for the capability identifier, the front channel identifier, and the information indicating the front-end device 03A that need to be modified.

In another implementation manner, taking the alarm message shown in table 4 as an example, if the resource transmission format is the download address of the backend device, the resource related to the alarm in the alarm message is converted into the resource transmission format, so as to obtain the updated alarm message, which may specifically be: and storing all pictures in the original alarm message in NVR, and placing the corresponding download address at the position of the picture stored in the original alarm message to obtain an updated alarm message.

In another implementation manner, taking the alarm message shown in table 4 as an example, if the resource transmission format is the cloud download address, the alarm related resource in the alarm message is converted into the resource transmission format, so as to obtain the updated alarm message, which may specifically be: all pictures in the original alarm message are stored in a cloud terminal (such as a cloud server provided by company A), and a corresponding download address is placed at the position where the pictures are stored in the original alarm message, so that an updated alarm message is obtained.

It should be noted that before S113, the NVR may also analyze and process the alarm message to obtain unified alarm information, as mentioned in the foregoing embodiment. And then, based on the capability identifier and the front channel identifier carried in the content in the unified alarm information, performing the relevant processing in step S113.

And S114, the NVR sends the updated alarm message to the security platform 01.

Based on the scheme, the user can smoothly subscribe the alarm message with the alarm capacity/type required to be checked through the security platform, and the use experience of the user on the security system is improved.

In some embodiments, after the alarm message is obtained, the alarm-related resource in the alarm message is generally stored for a subsequent user to invoke for viewing. During storage, in order to indicate alarm related resources belonging to different alarm capabilities/types, the capability identifier and the corresponding alarm related resource are stored in an associated manner during storage (the capability identifier and the corresponding alarm related resource are stored in the same storage area or are stored in the same storage area respectively, and then the corresponding relationship between the capability identifier and the corresponding alarm related resource is stored). If alarm related resources of certain alarm capacity/type need to be searched subsequently, the capacity identification corresponding to the alarm type can be used for searching. However, because the data size of the capability identifier itself is large, if there are many different capability identifiers, the time required for searching for a certain capability identifier is long, and the user experience is not good enough. To solve this problem, referring to fig. 13 in conjunction with fig. 3, the method further includes, after 201A, S131-S137:

s131, the NVR determines the storage identifier of the capability identifier of each alarm capability in the equipment alarm capability set according to the Hash algorithm so as to obtain the capability identifier of each alarm capability in the equipment alarm capability set and the target association relation of the storage identifier.

Specifically, in the embodiment of the present application, the capability identifier of the alarm capability is converted into integer data according to a hash algorithm.

S132, under the condition that the NVR receives the alarm message from the front-end device 03A, the alarm message is analyzed according to a preset rule to obtain a target capability identifier carried by the alarm message.

And S133, determining a target storage identifier corresponding to the target capability identifier by the NVR according to the target association relation.

And S134, the NVR stores the target storage identifier, the target capability identifier and the alarm related resource carried by the alarm message in an associated manner.

The alarm related resource may refer to the related expression of the alarm packet shown in table 4, and is not described herein again.

Of course, S134 may specifically store, after storing the alarm related resource of the alarm message, an association relationship among the target storage identifier, the target capability identifier, and the alarm related resource carried by the alarm message, where the alarm related resource carried by the alarm message in the association relationship may be represented by a specific identifier.

In an implementation manner, if the NVR converts the alarm message into the unified alarm information shown in table 6 before the S134 is executed, the S134 may store the target storage identifier, the target capability identifier, and the alarm information, the number of pictures, and the picture array in the unified alarm information in an associated manner.

And S135, the NVR receives a search instruction from the security platform 01.

The searching instruction indicates the capability identifier to be searched; specifically, the search instruction may carry the capability identifier to be searched. The alarm instruction may be generated by a user performing a search operation on the security platform 01.

And S136, responding to the search instruction, the NVR determines a storage identifier to be searched corresponding to the capability identifier to be searched according to the target association relation, and searches all data associated with the storage identifier to be searched according to the storage identifier to be searched.

And S137, the NVR generates a search result based on the data associated with the storage identifier to be searched, and sends the search result to the security platform.

Specifically, the data associated with the storage identifier to be searched may specifically refer to the alarm-related resource and capability identifier stored in association with the storage identifier to be searched.

Based on the scheme, the NVR can search the alarm related resource corresponding to the capability identification needing to be searched more quickly, and the user experience is improved.

It should be noted that, in fig. 13, taking S131 to S137 as an example after 202, in practice, the precedence relationship between step 202 and S131 to S137 is determined according to the practice, and the present application is not particularly limited.

Further, in other embodiments, due to the characteristics of the hash algorithm, different capability identifiers may be converted into the same integer data (i.e. storage identifier), so as to avoid that the data searched by the NVR according to the storage identifier is an alarm-related resource corresponding to a plurality of different capability identifiers, referring to fig. 14 in combination with fig. 13, S137 may specifically include S1371 to S1373:

s1371, under the condition that the storage identifier to be searched is determined to be repeated, target data associated with the capability identifier to be searched in the data associated with the storage identifier to be searched is determined.

S1372, sending the target data serving as a search result to the security platform.

S1373, under the condition that the storage identifier to be searched is determined to be repeated, all data related to the storage identifier to be searched are determined to be a search result and sent to the security platform 01.

Based on the above scheme, it is determined whether there is duplication of the storage identifier (in the embodiment, the storage identifier to be searched) when determining the search result. If the repeated data exists, the target data corresponding to the capability identifier to be searched is screened again from all the data stored in association with the storage identifier, and then the target data is determined as a search result and is sent to the security platform. Therefore, the data from the NVR finally received by the security platform is ensured to be the data required by the user, and the user is prevented from viewing the data which is not required.

In the embodiment of the present application, the back-end device may be divided into the functional modules according to the above method example, for example, the back-end device may divide each functional module corresponding to each function, or may integrate two or more functions into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiments of the present disclosure is illustrative, and is only one division of logic functions, and there may be another division in actual implementation.

Under the condition that each function module is divided by adopting corresponding functions, fig. 15 shows a possible structural schematic diagram of the back-end device, the back-end device is applied to a security system (as shown in fig. 1), the security system further comprises a front-end device, and a first front channel of the front-end device is accessed to a first back channel of the back-end device. The backend apparatus includes: an acquisition module 151 and a processing module 152.

The acquiring module 151 is configured to acquire a channel alarm capability set of a first front channel; the channel alarm capability set comprises at least one alarm capability supported by the first front channel, the alarm capability has a unique corresponding capability identifier, and the capability identifier has a unique corresponding alarm type. A processing module 152, configured to generate at least one linkage configuration file according to the channel alarm capability set and the alarm source obtained by the obtaining module 151; the linkage configuration files correspond to the alarm types one by one; the alarm source is used for indicating the first rear channel and/or the first front channel; the linkage configuration file comprises an alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule. And the linkage rule is used for indicating the back-end equipment to execute corresponding linkage operation when receiving the capability identification in the linkage configuration file to which the linkage rule belongs through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs.

Optionally, the obtaining module 151 is specifically configured to obtain all the alarm capabilities supported by the first front channel; and filtering all the alarm capacities according to a preset filtering rule to obtain at least one alarm capacity forming a channel alarm capacity set, and forming the channel alarm capacity set by the at least one alarm capacity.

Optionally, the security system further includes a security platform, and the back-end device further includes a sending module 153; the obtaining module 151 is further configured to receive a linkage rule request from the security platform; the linkage rule request indicates a first back channel identifier and a first capability identifier; the first capability identification is one of the capability identifications of the at least one alarm capability; the processing module 152 is further configured to determine, in response to the linkage rule request received by the obtaining module 151, a first linkage configuration file corresponding to the first back channel identifier and the first capability identifier; the sending module 153 is configured to send the first linkage rule in the first linkage configuration file determined by the processing module 152 to the security platform; the first linkage profile is one of the at least one linkage profile.

Optionally, the security system further comprises a security platform; the obtaining module 151 is further configured to receive a linkage modification request from the security platform; the linkage modification request carries a first rear channel identifier, a second capacity identifier and an undetermined linkage rule; the second capability identification is one of the capability identifications of the at least one alarm capability; the processing module 152 is further configured to update, in response to the linkage modification request received by the obtaining module 151, a second linkage profile corresponding to the first rear channel identifier and the second capability identifier using the undetermined linkage rule; the second linkage profile is one of the at least one linkage profile.

Optionally, the security system further comprises a security platform; the backend device further comprises a sending module 153; the obtaining module 151 is further configured to receive an alarm modification request from the security platform; the alarm modification request indicates the first back channel identifier and the undetermined alarm rule; the first back channel mark is the mark of the first back channel; the processing module 152 is further configured to determine, according to the channel mapping relationship, a first front channel identifier corresponding to the first rear channel identifier indicated by the alarm modification request received by the obtaining module 151; the channel mapping relation is used for indicating the corresponding relation between a rear channel of the rear-end equipment and a front channel of the front-end equipment; the first front channel identifier is an identifier of a first front access; the processing module 152 is further configured to replace the first back channel identifier in the alarm modification request with the first front channel identifier to obtain an updated alarm modification request; a sending module 153, configured to send the updated alarm modification request obtained by the processing module 152 to the front-end device, so that the front-end device updates the alarm rule of the first front channel using the pending alarm rule.

Further optionally, after the sending module 153 sends the updated alarm modification request obtained by the processing module 152 to the front-end device, the obtaining module 151 is further configured to receive a modification response sent by the front-end device; the modification response indicates the first front channel identifier, and the modification response is used for indicating that the front-end equipment completes the modification of the alarm rule; the processing module 152 is further configured to determine, according to the channel mapping relationship, a first back channel identifier corresponding to the first front channel identifier indicated by the modification response received by the obtaining module 151, and replace the first front channel identifier indicated in the modification response with the first back channel identifier, so as to obtain an updated modification response; the sending module 153 is further configured to send the updated modification response to the security platform.

Optionally, the obtaining module 151 is further configured to receive an alarm message from a front-end device; the first front channel identifier and the third capability identifier are indicated in the message alarm; the third capability identification is one of the capability identifications of the at least one alarm capability; the processing module 152 is further configured to determine, according to the channel mapping relationship, a first back channel identifier corresponding to the first front channel identifier indicated by the alarm packet received by the obtaining module 151; the channel mapping relation is used for indicating the corresponding relation between the channel of the back-end equipment and the front channel of the front-end equipment; the processing module 152 is further configured to determine a third linkage profile corresponding to the first back channel identifier and/or the first front channel identifier, and the third capability identifier; the third linkage profile is one of the at least one linkage profile; the processing module 152 is further configured to execute a corresponding linkage operation according to the linkage rule in the third linkage configuration file.

Optionally, the security system further comprises a security platform; the backend device further comprises a sending module 153; the obtaining module 151 is further configured to receive a subscription request from the security platform; the subscription request carries a fourth capability identifier, a first back channel identifier and a resource transmission format; the subscription request is used for requesting to subscribe the alarm message corresponding to the fourth capability identifier and the first back channel identifier, and requesting the format of the alarm related resource carried in the alarm message to be a resource transmission format; the first back channel mark is the mark of the first back channel; the processing module 152 is further configured to respond to the subscription request received by the obtaining module 151, and in a case that the obtaining module 151 receives an alarm packet from a front-end device, if a fifth capability identifier carried in the alarm packet is a fourth capability identifier and a front channel identifier carried in the alarm packet is an identifier of a first front channel corresponding to a first back channel identifier, replace the front channel identifier carried in the alarm packet with the first back channel identifier, and set a format of an alarm-related resource in the alarm packet to a resource transmission format, so as to obtain an updated alarm packet; and the sending module 153 is configured to send the updated alarm message obtained by the processing module 152 to the security platform.

Optionally, after the obtaining module 151 obtains the channel alarm capability set of the first front channel, the processing module 152 is further configured to compare the channel alarm capability set obtained by the obtaining module 151 with the device alarm capability set, and add, into the device alarm capability set, an alarm capability that does not exist in the device alarm capability set in the channel alarm capability set; the device alarm capability set is composed of alarm capabilities prestored by the back-end device.

Further optionally, the security system further comprises a security platform; the backend device further comprises a sending module 153; the obtaining module 151 is further configured to receive a display request from the security platform; the display request is used for requesting to display the equipment alarm capability set of the back-end equipment; the processing module 152 is further configured to determine, according to the name mapping table, an alarm name corresponding to each alarm capability in the device alarm capability set; the name mapping table is used for representing the alarm name corresponding to each alarm capability in the equipment alarm capability set; and the sending module 153 is configured to send, to the security platform, at least one alarm capability in the set of device alarm capabilities determined by the processing module 152 and an alarm name corresponding to the alarm capability.

Optionally, the security system further comprises a security platform; the backend device further comprises a sending module 153; the obtaining module 151 is further configured to receive a search instruction from the security platform; the search instruction indicates the capability identifier to be searched; the processing module 152 is further configured to, in response to the search instruction received by the obtaining module 151, determine, according to the target association relationship, a to-be-searched storage identifier corresponding to the to-be-searched capability identifier indicated by the search instruction, and search, according to the to-be-searched storage identifier, all data associated with the to-be-searched storage identifier; the target incidence relation is used for indicating the incidence relation of the capacity identifier and the storage identifier of each alarm capacity in the equipment alarm capacity set of the back-end equipment; the storage identification is obtained by the alarm capacity identification of the alarm capacity in the equipment alarm capacity set according to a Hash algorithm; the processing module 152 is further configured to generate a search result based on the data associated with the storage identifier to be searched; and the sending module 153 is configured to send the search result generated by the processing module 152 to the security platform.

Further optionally, the processing module 152 is specifically configured to: under the condition that the storage identifier to be searched is determined to be repeated, target data associated with the capability identifier to be searched in the data associated with the storage identifier to be searched is determined; and taking the target data as a search result.

Regarding the backend device in the above embodiments, the specific manner in which each module executes operations and the corresponding beneficial effects have been described in detail in the foregoing embodiments of the alarm linkage configuration method, and will not be described again here.

In the case of using an integrated module, an embodiment of the present application provides a backend device, where the backend device may be applied to a security system (as shown in fig. 1), the security system further includes a front-end device, and a first front channel of the front-end device is accessed to a first back channel of the backend device. The backend device may include: storage unit, processing unit. The processing unit is used for controlling and managing, for example, the processing unit is used for supporting the backend device to execute the steps executed by each module in the backend device in the foregoing embodiments; the storage unit is used for storing program codes and data of the electronic equipment, and specifically can support the back-end equipment to execute the alarm linkage configuration method in the embodiment.

In which, the processing unit is taken as a processor and the storage unit is taken as a memory as an example. Referring to fig. 16, an embodiment of the present application further provides a backend device, which includes a memory 161 and a processor 162. The memory 161 is used for storing instructions executable by the processor 162, and the processor 162 is configured to execute the executable instructions to implement the alarm linkage configuration method in the above embodiment.

In particular implementations, processor 162(162-1 and 162-2) may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 16, for example, as one embodiment. And as an example, the backend device may include multiple processors 162, such as processor 162-1 and processor 162-2 shown in fig. 16. Each of the processors 162 may be a Single-core processor (Single-CPU) or a Multi-core processor (Multi-CPU). Processor 162 may refer herein to one or more devices, circuits, and/or processing cores that process data (e.g., computer program instructions).

The Memory 161 may be, but is not limited to, a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable Read-Only Memory (EEPROM), a compact disc Read-Only Memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 161 may be separate and coupled to the processor 162 via a bus 163. Memory 161 may also be integrated with processor 162.

In a specific implementation, the memory 161 is used for storing data in the present application and computer-executable instructions corresponding to software programs for executing the present application. The processor 162 may implement various functions of the backend device by running or executing software programs stored in the memory 161 and invoking data stored in the memory 161.

The communication interface 164 is any device, such as a transceiver, for communicating with other devices or communication networks, such as a control system, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), and the like. The communication interface 164 may include a receiving unit to implement a receiving function and a transmitting unit to implement a transmitting function.

The bus 163 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an extended ISA (enhanced industry standard architecture) bus, or the like. The bus 163 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 16, but this is not intended to represent only one bus or type of bus.

The embodiment of the application further provides a computer-readable storage medium, which includes a computer execution instruction, and when the computer execution instruction runs on a back-end device in a security system, the back-end device is enabled to execute the alarm linkage configuration method provided by the embodiment.

The embodiment of the present application further provides a computer program product, which includes an instruction, and when the instruction runs on a back-end device in a security system, the back-end device executes the alarm linkage configuration method provided in the foregoing embodiment.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer-readable storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical function division, and there may be other division ways in actual implementation. For example, various elements or components may be combined or may be integrated into another device, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. Units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. The utility model provides an alarm linkage configuration method, is applied to the backend equipment in the security protection system, the security protection system still includes the front end equipment, the first front channel of front end equipment inserts the first back channel of backend equipment, its characterized in that, the method includes:

acquiring a channel alarm capacity set of the first front channel; the channel alarm capability set comprises at least one alarm capability supported by the first front channel, the alarm capability has a unique corresponding capability identifier, and the capability identifier has a unique corresponding alarm type;

generating at least one linkage configuration file according to the channel alarm capacity set and the alarm source; the linkage configuration files correspond to the alarm types one by one; the alarm source is used for indicating the first rear channel and/or the first front channel; the linkage configuration file comprises the alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule;

and the linkage rule is used for indicating the back-end equipment to execute corresponding linkage operation when receiving the capability identification in the linkage configuration file to which the linkage rule belongs through a channel indicated by an alarm source in the linkage configuration file to which the linkage rule belongs.

2. The method of claim 1, wherein obtaining the set of channel alarm capabilities for the first front channel comprises:

acquiring all alarm capabilities supported by the first front channel;

and filtering all the alarm capacities according to a preset filtering rule to obtain the at least one alarm capacity forming the channel alarm capacity set, and forming the channel alarm capacity set by the at least one alarm capacity.

3. The method of claim 1, wherein the security system further comprises a security platform, the method further comprising:

receiving a linkage rule request from the security platform; the linkage rule request indicates the first back channel identifier and a first capability identifier; the first capability identifier is one of capability identifiers of the at least one alarm capability;

responding to the linkage rule request, determining a first linkage configuration file corresponding to the first back channel identifier and the first capacity identifier, and sending a first linkage rule in the first linkage configuration file to the security platform; the first linkage profile is one of the at least one linkage profile.

4. The method of claim 1, wherein the security system further comprises a security platform, the method further comprising:

receiving a linkage modification request from the security platform; the linkage modification request carries the first rear channel identifier, the second capacity identifier and the undetermined linkage rule; the second capability identifier is one of the capability identifiers of the at least one alarm capability;

updating a second linkage configuration file corresponding to the first rear channel identifier and the second capacity identifier by using the undetermined linkage rule in response to the linkage modification request; the second linkage profile is one of the at least one linkage profile.

5. The method of claim 1, wherein the security system further comprises a security platform, the method further comprising:

receiving an alarm modification request from the security platform; the alarm modification request indicates a first back channel identifier and an undetermined alarm rule; the first back channel identifier is an identifier of the first back channel;

determining a first front channel identifier corresponding to the first rear channel identifier according to a channel mapping relation; the channel mapping relation is used for indicating the corresponding relation between the rear channel of the rear-end equipment and the front channel of the front-end equipment; the first front channel identifier is an identifier of the first front access;

replacing the first back channel identifier in the alarm modification request with the first front channel identifier to obtain an updated alarm modification request;

and sending the updated alarm modification request to the front-end equipment so that the front-end equipment updates the alarm rule of the first front channel by using the undetermined alarm rule.

6. The method of claim 5, wherein after sending the updated pending alarm request to the front-end device, further comprising:

receiving a modification response sent by the front-end equipment; the modification response indicates the first front channel identifier, and the modification response is used for indicating that the front-end equipment completes modification of the alarm rule;

determining the first back channel identifier corresponding to the first front channel identifier according to a channel mapping relation, and replacing the first front channel identifier indicated in the modification response with the first back channel identifier to obtain an updated modification response;

and sending the updated modification response to the security platform.

7. The method of claim 1, further comprising:

receiving an alarm message from the front-end equipment; the first front channel identifier and the third capability identifier are indicated in the alarm message; the third capability identifier is one of the capability identifiers of the at least one alarm capability;

determining the first back channel identifier corresponding to the first front channel identifier according to a channel mapping relation; the channel mapping relationship is used for indicating the corresponding relationship between the channel of the back-end equipment and the front channel of the front-end equipment;

determining a third linkage configuration file corresponding to the first back channel identifier and/or the first front channel identifier and the third capability identifier; the third linkage profile is one of the at least one linkage profile;

and executing corresponding linkage operation according to the linkage rule in the third linkage configuration file.

8. The method of claim 1, wherein the security system further comprises a security platform, the method further comprising:

receiving a subscription request from the security platform; the subscription request carries a fourth capability identifier, a first back channel identifier and a resource transmission format; the subscription request is used for requesting subscription of an alarm message corresponding to the fourth capability identifier and the first back channel identifier, and requesting the format of alarm-related resources carried in the alarm message to be the resource transmission format; the first back channel identifier is an identifier of the first back channel;

responding to the subscription request, under the condition that an alarm message from the front-end device is received, if a fifth capability identifier carried in the alarm message is the fourth capability identifier and a front channel identifier carried in the alarm message is the identifier of the first front channel corresponding to the first back channel identifier, replacing the front channel identifier carried in the alarm message with the first back channel identifier, and setting the format of alarm-related resources in the alarm message as the resource transmission format to obtain the updated alarm message;

and sending the updated alarm message to the security platform.

9. The method of claim 1, wherein after obtaining the set of channel alarm capabilities for the first front channel, further comprising:

comparing the channel alarm capacity set with the equipment alarm capacity set, and adding the alarm capacity which does not exist in the equipment alarm capacity set in the channel alarm capacity set into the equipment alarm capacity set; the device alarm capability set is composed of alarm capabilities prestored by the back-end device.

10. The method of claim 9, further comprising:

receiving a display request from the security platform; the display request is used for requesting to display the equipment alarm capacity set of the back-end equipment;

determining an alarm name corresponding to each alarm capability in the equipment alarm capability set according to a name mapping table; the name mapping table is used for representing an alarm name corresponding to each alarm capability in the equipment alarm capability set;

and sending at least one alarm capability in the equipment alarm capability set and the corresponding alarm name to the security platform.

11. The method of claim 1, wherein the security system further comprises a security platform, the method further comprising:

receiving a search instruction from the security platform; the search instruction indicates a capability identifier to be searched;

responding to the search instruction, determining a storage identifier to be searched corresponding to the capability identifier to be searched according to a target association relation, and searching all data associated with the storage identifier to be searched according to the storage identifier to be searched; the target incidence relation is used for indicating the incidence relation of the capacity identifier and the storage identifier of each alarm capacity in the equipment alarm capacity set of the back-end equipment; the storage identification is obtained by the alarm capacity identification of the alarm capacity in the equipment alarm capacity set according to a Hash algorithm;

and generating a search result based on the data associated with the storage identifier to be searched, and sending the search result to the security platform.

12. The method of claim 11, wherein generating search results based on all data stored in association with the to-be-searched storage identifier comprises:

under the condition that the storage identifier to be searched is determined to be repeated, target data associated with the capability identifier to be searched in the data associated with the storage identifier to be searched is determined;

and taking the target data as the search result.

13. The utility model provides a rear end equipment, is applied to the security protection system, still include front end equipment among the security protection system, the first front channel of front end equipment inserts the first back channel of rear end equipment, its characterized in that, rear end equipment includes:

an obtaining module, configured to obtain a channel alarm capability set of the first front channel; the channel alarm capability set comprises at least one alarm capability supported by the first front channel, the alarm capability has a unique corresponding capability identifier, and the capability identifier has a unique corresponding alarm type;

the processing module is used for generating at least one linkage configuration file according to the channel alarm capacity set and the alarm source acquired by the acquisition module; the linkage configuration files correspond to the alarm types one by one; the alarm source is used for indicating the first rear channel and/or the first front channel; the linkage configuration file comprises the alarm source, an alarm type matching capability identifier corresponding to the linkage configuration file and a linkage rule;

14. The backend apparatus of claim 13,

the acquisition module is specifically used for acquiring all alarm capabilities supported by the first front channel; filtering all the alarm capacities according to a preset filtering rule to obtain at least one alarm capacity forming the channel alarm capacity set, and forming the channel alarm capacity set by the at least one alarm capacity;

and/or the presence of a gas in the gas,

the acquisition module is also used for receiving an alarm message from the front-end equipment; the first front channel identifier and the third capability identifier are indicated in the alarm message; the third capability identifier is one of the capability identifiers of the at least one alarm capability; the processing module is further configured to determine, according to a channel mapping relationship, the first back channel identifier corresponding to the first front channel identifier indicated by the alarm packet received by the obtaining module; the channel mapping relationship is used for indicating the corresponding relationship between the channel of the back-end equipment and the front channel of the front-end equipment; the processing module is further configured to determine a third linkage configuration file corresponding to the first back channel identifier and/or the first front channel identifier, and the third capability identifier; the third linkage profile is one of the at least one linkage profile; the processing module is further used for executing corresponding linkage operation according to the linkage rule in the third linkage configuration file;

and/or the presence of a gas in the gas,

after the acquisition module acquires the channel alarm capability set of the first front channel, the processing module is further configured to compare the channel alarm capability set acquired by the acquisition module with an equipment alarm capability set, and add an alarm capability, which does not exist in the equipment alarm capability set, in the equipment alarm capability set; the equipment alarm capacity set consists of alarm capacities prestored by the back-end equipment;

under the condition that the security system also comprises a security platform and the back-end equipment also comprises a sending module,

the acquisition module is also used for receiving a linkage rule request from the security platform; the linkage rule request indicates the first back channel identifier and a first capability identifier; the first capability identifier is one of capability identifiers of the at least one alarm capability; the processing module is further configured to determine, in response to the linkage rule request received by the obtaining module, a first linkage configuration file corresponding to the first back channel identifier and the first capability identifier; the sending module is used for sending the first linkage rule in the first linkage configuration file determined by the processing module to the security platform; the first linkage profile is one of the at least one linkage profile;

and/or the presence of a gas in the gas,

the acquisition module is also used for receiving a linkage modification request from the security platform; the linkage modification request carries the first rear channel identifier, the second capacity identifier and the undetermined linkage rule; the second capability identifier is one of the capability identifiers of the at least one alarm capability; the processing module is further configured to update a second linkage configuration file corresponding to the first rear channel identifier and the second capability identifier by using the undetermined linkage rule in response to the linkage modification request received by the obtaining module; the second linkage profile is one of the at least one linkage profile;

and/or the presence of a gas in the gas,

the acquisition module is also used for receiving an alarm modification request from the security platform; the alarm modification request indicates a first back channel identifier and an undetermined alarm rule; the first back channel identifier is an identifier of the first back channel; the processing module is further configured to determine, according to a channel mapping relationship, a first front channel identifier corresponding to the first rear channel identifier indicated by the alarm modification request received by the obtaining module; the channel mapping relation is used for indicating the corresponding relation between the rear channel of the rear-end equipment and the front channel of the front-end equipment; the first front channel identifier is an identifier of the first front access; the processing module is further configured to replace the first back channel identifier in the alarm modification request with the first front channel identifier to obtain an updated alarm modification request; the sending module is configured to send the updated alarm modification request obtained by the processing module to the front-end device, so that the front-end device updates an alarm rule of the first front channel by using the to-be-determined alarm rule;

and/or the presence of a gas in the gas,

after the sending module sends the updated alarm modification request obtained by the processing module to the front-end device, the obtaining module is further configured to receive a modification response sent by the front-end device; the modification response indicates the first front channel identifier, and the modification response is used for indicating that the front-end equipment completes modification of the alarm rule; the processing module is further configured to determine, according to a channel mapping relationship, the first back channel identifier corresponding to the first front channel identifier indicated by the modification response received by the obtaining module, and replace the first front channel identifier indicated in the modification response with the first back channel identifier, so as to obtain the updated modification response; the sending module is further configured to send the updated modification response to the security platform;

and/or the presence of a gas in the gas,

the acquisition module is further used for receiving a subscription request from the security platform; the subscription request carries a fourth capability identifier, a first back channel identifier and a resource transmission format; the subscription request is used for requesting subscription of an alarm message corresponding to the fourth capability identifier and the first back channel identifier, and requesting the format of alarm-related resources carried in the alarm message to be the resource transmission format; the first back channel identifier is an identifier of the first back channel; the processing module is further configured to, in response to the subscription request received by the obtaining module, in a case where the obtaining module receives an alarm packet from the front-end device, if a fifth capability identifier carried in the alarm packet is the fourth capability identifier and a front channel identifier carried in the alarm packet is an identifier of the first front channel corresponding to the first back channel identifier, replace the front channel identifier carried in the alarm packet with the first back channel identifier, and set a format of an alarm-related resource in the alarm packet to the resource transmission format, so as to obtain the updated alarm packet; the sending module is used for sending the updated alarm message obtained by the processing module to the security platform;

and/or the presence of a gas in the gas,

the acquisition module is also used for receiving a display request from the security platform; the display request is used for requesting to display the equipment alarm capacity set of the back-end equipment; the processing module is further used for determining an alarm name corresponding to each alarm capability in the equipment alarm capability set according to a name mapping table; the name mapping table is used for representing an alarm name corresponding to each alarm capability in the equipment alarm capability set; the sending module is used for sending at least one alarm capability in the equipment alarm capability set determined by the processing module and the corresponding alarm name to the security platform;

and/or the presence of a gas in the gas,

the acquisition module is further used for receiving a search instruction from the security platform; the search instruction indicates a capability identifier to be searched; the processing module is further configured to respond to the search instruction received by the obtaining module, determine, according to a target association relationship, a storage identifier to be searched corresponding to the capability identifier to be searched indicated by the search instruction, and search for all data associated with the storage identifier to be searched according to the storage identifier to be searched; the target incidence relation is used for indicating the incidence relation of the capacity identifier and the storage identifier of each alarm capacity in the equipment alarm capacity set of the back-end equipment; the storage identification is obtained by the alarm capacity identification of the alarm capacity in the equipment alarm capacity set according to a Hash algorithm; the processing module is further used for generating a search result based on the data associated with the storage identifier to be searched; the sending module is used for sending the search result generated by the processing module to the security platform;

and/or the presence of a gas in the gas,

the processing module is specifically configured to: under the condition that the storage identifier to be searched is determined to be repeated, target data associated with the capability identifier to be searched in the data associated with the storage identifier to be searched is determined; and taking the target data as the search result.

15. A backend device comprising a processor and a memory for storing processing executable instructions; wherein the processor is configured to execute the executable instructions to cause the backend device to perform the alarm linkage configuration method of any of claims 1-12.

16. A computer-readable storage medium comprising computer-executable instructions that, when run on a backend device in a security system, cause the backend device to perform the alarm linkage configuration method of any of claims 1-12.

17. A security system comprising a backend device according to claim 13 or 14, or a backend device according to claim 15.