An alarm linkage configuration method and a security system

Abstract

An embodiment of the present application provides an alarm linkage configuration method and a security system, which relate to the field of security and can enable the backend device to successfully process the alarm messages reported by the frontend device without updating the backend device. This method is applied to the backend device in a security system where the first front channel of the frontend device accesses the first back channel of the backend device. The method includes: obtaining the channel alarm capability set of the first front channel; generating at least one linkage configuration file according to the channel alarm capability set and the alarm source, where the alarm source is used to indicate the first back channel and / or the first front channel; the linkage configuration file includes the alarm source, the capability identifier matching the alarm type corresponding to the linkage configuration file, and the linkage rule; the linkage rule is used to indicate that when the backend device receives the capability identifier in the linkage configuration file through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs, it performs the corresponding linkage operation.

Description

Technical Field

[0001] The present application relates to the field of security management, and in particular, to an alarm linkage configuration method and a security system. Background Art

[0002] With the development of digital technology, more and more front-end devices (such as network cameras, access control devices, etc.) in existing security systems have more powerful intelligence. After the equipment is updated and replaced, the front-end devices can identify richer alarm events and have more powerful alarm functions. In this case, if the corresponding back-end devices or back-end platforms are not updated, the back-end devices cannot correctly identify and process the alarm messages reported by the front-end, and then the entire security system cannot operate normally. Therefore, in order to update the security system to adapt to the new alarm scenario requirements, after updating the front-end devices, it is often necessary to update the supporting back-end devices / platforms at the same time. However, because the back-end devices themselves have complex structures and high costs, and the update period is very long, the security system with updated front-end devices cannot quickly use the updated functions. Summary of the Invention

[0003] Embodiments of the present application provide an alarm linkage configuration method and a security system, which can enable the back-end device to successfully process the alarm messages reported by the front-end device without updating the back-end device.

[0004] To achieve the above object, the embodiments of the present application adopt the following technical solutions:

[0005] 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 includes 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 includes: First, obtain a channel alarm capability set of the first front channel; the channel alarm capability set includes at least one alarm capability supported by the first front channel, there is a unique corresponding capability identifier for the alarm capability, and there is a unique corresponding alarm type for the capability identifier. Then, generate at least one linkage configuration file according to the channel alarm capability set and the alarm source; the linkage configuration files are in one-to-one correspondence with the alarm types; the alarm source is used to indicate the first back channel and / or the first front channel; the linkage configuration file includes the alarm source, the capability identifier matching the alarm type corresponding to the linkage configuration file, and a linkage rule; wherein, the linkage rule is used to indicate that when the back-end device receives the capability identifier in the linkage configuration file through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs, the back-end device performs a corresponding linkage operation.

[0006] Based on the above technical solution, the backend device can automatically identify the channel alarm capability set of the frontend device (composed of at least one alarm capability (specifically, the capability identifier of the alarm capability) supported by a certain front channel of the frontend device), and according to the preset rules, based on each capability identifier and the alarm source that can indicate the channel for transmitting the alarm message (such as the back channel of the backend device and / or the front channel of the frontend device), automatically generate a linkage rule configuration file for each alarm type corresponding to each channel connected between the backend device and the frontend device. Moreover, in this process, the backend device does not need to identify or translate to obtain the alarm type corresponding to each alarm capability in the channel alarm capability set obtained by the frontend device, but can directly generate the linkage configuration file using the capability identifier of the alarm capability. In this way, whether there are newly updated alarm capabilities or no newly updated alarm capabilities in the channel alarm capability set of the frontend device, it is possible to make the backend device, without the need to separately update and develop the configuration for the new alarm type, match the capability identifier and the front channel identifier carried in the alarm message with the capability identifier and the alarm source in the previously generated linkage configuration file when receiving the alarm message, thereby determining the linkage configuration file corresponding to the alarm message, further determining the corresponding linkage rule and performing the corresponding operation. Compared with the prior art, this solution can, without updating the backend device, conveniently and quickly enable the backend device to identify and process the alarm messages of the newly added alarm types of the updated frontend device, improve the reliability of the security system, and reduce the development cost.

[0007] Optionally, obtaining the channel alarm capability set of the first front channel includes: obtaining all the alarm capabilities supported by the first front channel; filtering all the alarm capabilities according to the preset filtering rules to obtain at least one alarm capability that constitutes the channel alarm capability set, and forming the channel alarm capability set by the at least one alarm capability.

[0008] Optionally, the security system further includes a security platform, and the method further includes: 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 identifier is one of the capability identifiers of at least one alarm capability; in response to the linkage rule request, determining a first linkage configuration file corresponding to the first back channel identifier and the first capability identifier, and sending the first linkage rule in the first linkage configuration file to the security platform; the first linkage configuration file is one of at least one linkage configuration file.

[0009] Optionally, the security system further includes a security platform, and the method further includes: receiving a linkage modification request from the security platform; the linkage modification request carries a first back-channel identifier, a second capability identifier, and a pending linkage rule; the second capability identifier is one of the capability identifiers of at least one alarm capability; in response to the linkage modification request, updating a second linkage configuration file corresponding to the first back-channel identifier and the second capability identifier by using the pending linkage rule; the second linkage configuration file is one of at least one linkage configuration file.

[0010] Optionally, the security system further includes a security platform, and the method further includes: receiving an alarm modification request from the security platform; the alarm modification request indicates a first back-channel identifier and a pending alarm rule; the first back-channel identifier is the identifier of the first back channel; determining a first front-channel identifier corresponding to the first back-channel identifier according to the channel mapping relationship; the channel mapping relationship is used to indicate the correspondence between the back channels of the backend devices and the front channels of the frontend devices; the first front-channel identifier is the identifier of the first front channel; replacing the first back-channel identifier in the alarm modification request with the first front-channel identifier to obtain an updated alarm modification request; sending the updated alarm modification request to the frontend device so that the frontend device updates the alarm rule of the first front channel by using the pending alarm rule.

[0011] Further optionally, after sending the updated pending alarm request to the frontend device, it further includes: receiving a modification response sent by the frontend device; the modification response indicates the first front-channel identifier, and the modification response is used to indicate that the frontend device has completed the modification of the alarm rule; determining a first back-channel identifier corresponding to the first front-channel identifier according to the channel mapping relationship, and replacing the first front-channel identifier indicated in the modification response with the first back-channel identifier to obtain an updated modification response; sending the updated modification response to the security platform.

[0012] Optionally, the method further includes: receiving an alarm message from the frontend device; the alarm message indicates a first front-channel identifier and a third capability identifier; the third capability identifier is one of the capability identifiers of at least one alarm capability; determining a first back-channel identifier corresponding to the first front-channel identifier according to the channel mapping relationship; the channel mapping relationship is used to indicate the correspondence between the channels of the backend devices and the front channels of the frontend devices; 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 configuration file is one of at least one linkage configuration file; performing corresponding linkage operations according to the linkage rules in the third linkage configuration file.

[0013] Optionally, the security system further includes a security platform, and the method further includes: 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 to request to subscribe to an alarm message corresponding to the fourth capability identifier and the first back-channel identifier, and request that the format of the alarm-related resources carried in the alarm message be the resource transmission format; the first back-channel identifier is the identifier of the first back-channel; in response to the subscription request, when receiving an alarm message from a front-end device, if the fifth capability identifier carried in the alarm message is the fourth capability identifier, and the front-channel identifier carried in the alarm message is the identifier of the first front-channel corresponding to the first back-channel identifier, then replace the front-channel identifier carried in the alarm message with the first back-channel identifier, and set the format of the alarm-related resources in the alarm message to the resource transmission format to obtain an updated alarm message; send the updated alarm message to the security platform.

[0014] Optionally, after obtaining the channel alarm capability set of the first front-channel, the method further includes: comparing the channel alarm capability set with the device alarm capability set, and adding the alarm capabilities that do not exist in the device alarm capability set in the channel alarm capability set into the device alarm capability set; the device alarm capability set is composed of the alarm capabilities pre-stored in the back-end device.

[0015] Optionally, the method further includes: receiving a display request from the security platform; the display request is used to request to display the device alarm capability set of the back-end device; according to the name mapping table, determine the alarm name corresponding to each alarm capability in the device alarm capability set; the name mapping table is used to represent the alarm name corresponding to each alarm capability in the device alarm capability set; send at least one alarm capability in the device alarm capability set and its corresponding alarm name to the security platform.

[0016] Optionally, the security system further includes a security platform, and the method further includes: receiving a search instruction from the security platform; the search instruction indicates the to-be-searched capability identifier; in response to the search instruction, according to the target association relationship, determine the to-be-searched storage identifier corresponding to the to-be-searched capability identifier, and search for all data associated with the to-be-searched storage identifier according to the to-be-searched storage identifier; wherein, the target association relationship is used to indicate the association relationship between the capability identifier of each alarm capability in the device alarm capability set of the back-end device and its storage identifier; the storage identifier is obtained based on the hash algorithm of the capability identifier of the alarm capability in the device alarm capability set; generate a search result based on the data associated with the to-be-searched storage identifier, and send the search result to the security platform.

[0017] Further optionally, generating a search result based on all the data associated with the to-be-searched storage identifier includes: when determining that the to-be-searched storage identifier is duplicated, determining the target data associated with the to-be-searched capability identifier in the data associated with the to-be-searched storage identifier; using the target data as the search result.

[0018] In a second aspect, a backend device is provided, which is applied to a security system. The security system further includes a front-end device, and a first front channel of the front-end device is connected to a first rear channel of the backend device. The backend device includes an acquisition module and a processing module. Among them, the acquisition module is configured to acquire a channel alarm capability set of the first front channel; the channel alarm capability set includes at least one alarm capability supported by the first front channel, and there is a unique corresponding capability identifier for each alarm capability, and there is a unique corresponding alarm type for each capability identifier. The processing module is configured to generate at least one linkage configuration file according to the channel alarm capability set and the alarm source acquired by the acquisition module; the linkage configuration file corresponds to the alarm type one by one; the alarm source is used to indicate the first rear channel and / or the first front channel; the linkage configuration file includes the alarm source, the capability identifier matching the alarm type corresponding to the linkage configuration file, and a linkage rule. Among them, the linkage rule is used to instruct the backend device to perform a corresponding linkage operation when receiving the capability identifier in the linkage configuration file indicated by the alarm source 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.

[0019] Optionally, the acquisition module is specifically configured to: acquire all alarm capabilities supported by the first front channel; filter all alarm capabilities according to a preset filtering rule to obtain at least one alarm capability that constitutes the channel alarm capability set, and form the channel alarm capability set by the at least one alarm capability.

[0020] Optionally, the security system further includes a security platform, and the backend device further includes a sending module; the acquisition module is further configured to receive a linkage rule request from the security platform; the linkage rule request indicates a first rear channel identifier and a first capability identifier; the first capability identifier is one of the capability identifiers of at least one alarm capability; the processing module is further configured to determine a first linkage configuration file corresponding to the first rear channel identifier and the first capability identifier in response to the linkage rule request received by the acquisition module; the sending module is configured to send the first linkage rule in the first linkage configuration file determined by the processing module to the security platform; the first linkage configuration file is one of the at least one linkage configuration file.

[0021] Optionally, the security system further includes a security platform; the acquisition module 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 capability identifier, and a pending linkage rule; the second capability identifier is one of the capability identifiers of at least one alarm capability; the processing module is further configured to update the second linkage configuration file corresponding to the first rear channel identifier and the second capability identifier with the pending linkage rule in response to the linkage modification request received by the acquisition module; the second linkage configuration file is one of the at least one linkage configuration file.

[0022] Optionally, the security system further includes a security platform; the backend device further includes a sending module; the obtaining module is further configured to receive an alarm modification request from the security platform; the alarm modification request indicates a first rear channel identifier and a pending alarm rule; the first rear channel identifier is the identifier of the first rear channel; the processing module 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; the channel mapping relationship is used to indicate the corresponding relationship between the rear channels of the backend device and the front channels of the front-end device; the first front channel identifier is the identifier of the first front access; the processing module is further configured to use the first front channel identifier to replace the first rear channel identifier in the alarm modification request 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 the alarm rule of the first front channel using the pending alarm rule.

[0023] Further 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 to indicate that the front-end device has completed the modification of the alarm rule; the processing module is further configured to determine, according to the channel mapping relationship, a first rear channel identifier corresponding to the first front channel identifier indicated by the modification response received by the obtaining module, and use the first rear channel identifier to replace the first front channel identifier indicated in the modification response to obtain an updated modification response; the sending module is further configured to send the updated modification response to the security platform.

[0024] Optionally, the obtaining module is further configured to receive an alarm message from the front-end device; the alarm message indicates a first front channel identifier and a third capability identifier; the third capability identifier is one of the capability identifiers of at least one alarm capability; the processing module is further configured to determine, according to the channel mapping relationship, a first rear channel identifier corresponding to the first front channel identifier indicated by the alarm message received by the obtaining module; the channel mapping relationship is used to indicate the corresponding relationship between the channels of the backend device and the front channels of the front-end device; the processing module is further configured to determine a third linkage configuration file corresponding to the first rear channel identifier and / or the first front channel identifier, and the third capability identifier; the third linkage configuration file is one of at least one linkage configuration file; the processing module is further configured to perform corresponding linkage operations according to the linkage rules in the third linkage configuration file.

[0025] Optionally, the security system further includes a security platform; the backend device further includes a sending module; the obtaining module 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 to request to subscribe to an alarm message corresponding to the fourth capability identifier and the first back-channel identifier, and request that the format of the alarm-related resources carried in the alarm message be the resource transmission format; the first back-channel identifier is the identifier of the first back-channel; the processing module is further configured to, in response to the subscription request received by the obtaining module, when the obtaining module receives an alarm message from the front-end device, if the fifth capability identifier carried in the alarm message is the fourth capability identifier, and the front-channel identifier carried in the alarm message is the identifier of the first front-channel corresponding to the first back-channel identifier, then replace the front-channel identifier carried in the alarm message with the first back-channel identifier, and set the format of the alarm-related resources in the alarm message to the resource transmission format, so as to obtain an updated alarm message; the sending module is configured to send the updated alarm message obtained by the processing module to the security platform.

[0026] 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 the alarm capabilities that do not exist in the device alarm capability set to the device alarm capability set; the device alarm capability set is composed of the alarm capabilities pre-stored in the backend device.

[0027] Further optionally, the security system further includes a security platform; the backend device further includes a sending module; the obtaining module is further configured to receive a display request from the security platform; the display request is used to request to display the device alarm capability set of the backend device; the processing module is further configured to determine the alarm name corresponding to each alarm capability in the device alarm capability set according to the name mapping table; the name mapping table is used to represent the alarm name corresponding to each alarm capability in the device alarm capability set; the sending module is configured to send at least one alarm capability in the device alarm capability set determined by the processing module and its corresponding alarm name to the security platform.

[0028] Optionally, the security system further includes a security platform; the backend device further includes a sending module; the obtaining module is further configured to receive a search instruction from the security platform; the search instruction indicates a to-be-searched capability identifier; the processing module is further configured to, in response to the search instruction received by the obtaining module, determine a to-be-searched storage identifier corresponding to the to-be-searched capability identifier indicated by the search instruction according to the target association relationship, and search for all data associated with the to-be-searched storage identifier according to the to-be-searched storage identifier; wherein, the target association relationship is used to indicate the association relationship between the capability identifier of each alarm capability in the device alarm capability set of the backend device and its storage identifier; the storage identifier is obtained based on the hash algorithm for the capability identifier of the alarm capability in the device alarm capability set; the processing module is further configured to generate a search result based on the data associated with the to-be-searched storage identifier; the sending module is configured to send the search result generated by the processing module to the security platform.

[0029] Further optionally, the processing module is specifically configured to: in the case of determining that the to-be-searched storage identifier is duplicated, determine the target data associated with the to-be-searched capability identifier among the data associated with the to-be-searched storage identifier; and use the target data as the search result.

[0030] In a third aspect, a backend device is provided, including a processor and a memory for storing executable instructions for processing; wherein, the processor is configured to execute the executable instructions so that the backend device implements the alarm linkage configuration method provided in the first aspect.

[0031] In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium includes computer-executable instructions, when the computer-executable instructions run on the backend device in the security system, the backend device is caused to execute the alarm linkage configuration method provided in the first aspect.

[0032] In a fifth aspect, a computer program product is provided, including instructions, when the instructions run on the backend device in the security system, the backend device is caused to execute the alarm linkage configuration method provided in the first aspect.

[0033] In a sixth aspect, a security system is provided, including the backend device provided in the second aspect or the backend device provided in the third aspect.

[0034] It can be understood that the solutions provided in the second to sixth aspects above all correspond to the alarm linkage configuration method in the first aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding alarm linkage configuration method provided above, and will not be elaborated here.

[0035] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit this application. Description of the Drawings

[0036] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on these drawings.

[0037] Figure 1 Schematic diagram of the architecture of a security system provided by an embodiment of the present application;

[0038] Figure 2 Schematic flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 1 ;

[0039] Figure 3 Schematic flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 2 ;

[0040] Figure 4 Schematic flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 3 ;

[0041] Figure 5 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 1 ;

[0042] Figure 6 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 2 ;

[0043] Figure 7 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 3 ;

[0044] Figure 8 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 4 ;

[0045] Figure 9 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 5 ;

[0046] Figure 10 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 6 ;

[0047] Figure 11 Supplementary flow chart of an alarm linkage configuration method provided by an embodiment of the present application Figure 7 ;

[0048] Figure 12 Schematic diagram of the supplementary process of an alarm linkage configuration method provided by an embodiment of the present application Figure 8 ;

[0049] Figure 13 Schematic diagram of the supplementary process of an alarm linkage configuration method provided by an embodiment of the present application Figure 9 ;

[0050] Figure 14 Schematic diagram of the supplementary process of an alarm linkage configuration method provided by an embodiment of the present application Figure 10 ;

[0051] Figure 15 Schematic diagram of the structure of a backend device provided by an embodiment of the present application;

[0052] Figure 16 Schematic diagram of the structure of another backend device provided by an embodiment of the present application. Detailed implementation manners

[0053] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0054] It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific manner.

[0055] It should also be noted that in the embodiments of the present application, "(English: of)", "corresponding (English: corresponding, relevant)" and "corresponding (English: corresponding)" can sometimes be used interchangeably. It should be pointed out that when their differences are not emphasized, the meanings they express are the same.

[0056] To facilitate a clear description of the technical solutions in the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and roles. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order.

[0057] For ease of understanding, the terms in the embodiments of the present application are first introduced:

[0058] IPC: The full name is IP camera, that is, a network camera. It is a new generation of camera produced by combining traditional cameras and network technologies. It can transmit images over the network to the other end of the earth, and viewers at the remote end do not need any professional software, as long as a standard web browser (such as Microsoft IE or Netscape) can monitor its images. A network camera generally consists of a lens, an image, a sound sensor, an A / D converter, an image, a sound, a controller network server, an external alarm, a control interface, and other parts.

[0059] NVR: The full name is network video recorder, that is, a network video recorder. It is the storage and forwarding part of a network video security system. NVR works in cooperation with a video encoder or a network camera, has specific decoding capabilities, and can complete video recording, storage, and forwarding.

[0060] Hash algorithm: That is, HASH, generally translated as hash, or transliterated as hash. It transforms an input of any length (also called pre-image) into an output of a fixed length through a hash algorithm, and this output is the hash value.

[0061] Front-end device: Refers to the device installed at the scene or the very front end in a security system. For example, devices such as IPC and access control devices that collect data in real time at the scene. In the embodiments of the present application, the communication interface or communication link used by the front-end device to connect to the back-end device can be called the front channel.

[0062] Back-end device: Refers to the device in a security system that receives alarms (alarm messages) from the front-end device and performs linkage operations on the alarm according to preset linkage rules. For example, NVR. In the embodiments of the present application, the communication interface or communication link used by the back-end device to connect to the front-end device can be called the back channel.

[0063] Security platform: Refers to the device or cloud platform in a security system that can remotely manage the front-end device and the back-end device.

[0064] Alarm event: Refers to the situation where, when the front-end device collects data, the relevant parameters of the data meet the preset alarm strategy or conditions. At this time, it is considered that there is an alarm event, and the front-end device will generate a corresponding alarm message and upload it to the back-end device. The alarm strategies or conditions corresponding to alarm events of different alarm types are different.

[0065] In the current security system, the data formats of the alarm messages generated by the front-end devices for alarm events of different alarm types may be different. Therefore, for the back-end devices to parse and identify the alarm messages of alarm events of different alarm types, it is necessary to write corresponding parsing programs or scripts manually. With the development of digital technology, more and more front-end devices (such as network cameras, access control devices, etc.) in the existing security system will be more intelligent. After the equipment is updated and replaced, the front-end devices can identify richer alarm events and have more powerful alarm functions, and will report more different alarm messages to the back-end devices. In this case, if the back-end devices are not updated, it will cause the back-end devices to be unable to identify and process the alarm messages corresponding to the newly emerged alarm events. However, due to their complex structure, high cost, and long development cycle required for updating, the security system with updated front-end devices cannot quickly use the updated functions.

[0066] In view of the above problems, the embodiment of the present application provides an alarm linkage configuration method applied to a security system, which can automatically identify the channel alarm capability set of the front-end device (composed of at least one alarm capability supported by the front-end device, each alarm capability corresponds to a unique capability identifier, and each capability identifier matches an alarm type), and automatically generate a linkage rule configuration file for each alarm type corresponding to each channel connected between each back-end device and the front-end device according to the capability identifier of each alarm capability and the alarm source (such as the back channel of the back-end device and / or the front channel of the front-end device) used to indicate the transmission of the alarm message. In this way, when the back-end device receives an alarm message later, it can match the capability identifier carried in the alarm message and the identifier of the front channel of the front-end device (the back-end device may have a mapping table indicating the corresponding relationship between the back channel and the front channel, and according to this mapping table, the identifier of the corresponding back channel of any front channel can be determined) with the capability identifier and the alarm source in the above-mentioned linkage configuration file, so as to determine the linkage configuration file corresponding to the alarm message, and further determine the corresponding linkage rule and execute the corresponding operation.

[0067] The alarm linkage configuration method provided by the embodiment of the present application can be applied to a security system. Figure 1 A possible structure of the security system is shown. As Figure 1 shown, the security system may include a security platform 01, a back-end device 02, and at least one front-end device 03. Figure 1 Among them, the front-end devices 03A, 03B, and 03C are used to indicate at least one front-end device 03, and in practice, there may be more or fewer. Among them, the security platform 01 and the back-end device 02 are communicatively connected by wire or wirelessly. The back-end device 02 and the front-end device 03 are communicatively connected by wire or wirelessly.

[0068] In the embodiments of the present application, the communication among the security platform 01, the backend device 02, and the front-end device is carried out using the same standardized communication protocol. In this communication protocol, each alarm type is matched with a unique capability identifier, and each capability identifier corresponds to a unique alarm capability.

[0069] The security platform 01 is specifically configured to receive user operations and, in response to the user operations, manage the backend device 02 and the front-end device 03. This includes, but is not limited to, modifying the linkage rules in the backend device and modifying the alarm rules in the front-end device 03. Exemplarily, the security platform can be a single server or a service cluster or data center composed of multiple servers. The present application does not make specific limitations in this regard.

[0070] The backend device 02 is mainly configured to receive the alarm messages reported by the front-end device 03 and perform parsing and processing on them. The backend device 02 is also configured to receive instructions from the security platform to modify its own linkage rules, or instruct the front-end device 03 to modify the alarm rules of the front-end device 03, or send the information in the alarm messages reported by the front-end device 03 to the security platform according to certain rules. Of course, this is only an example here. In practice, the backend device 02 can also have any other feasible functions, and the present application does not make specific limitations in this regard. Exemplarily, the backend device can be various terminals with decoding, playback, and storage capabilities, such as computing devices like personal computers, laptops, smartphones, and tablets. It can also be a video recorder device such as a digital video recorder (DVR) or a network video recorder.

[0071] In the embodiments of the present application, the backend device 02 has multiple 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 front-end device 03. For the convenience of description, in the embodiments of the present application, the channels of the backend device 02 can be referred to as rear channels, and their corresponding identifiers are rear channel identifiers; the channels of the front-end device 03 can be referred to as front channels, and their corresponding identifiers are front channel identifiers. The front-end device 03 is specifically configured to collect data in a specified area, such as video data, audio data, photos, etc. When the front-end device 03 collects data in the specified area, if the collected data meets the preset alarm policy / rule / condition, it generates corresponding alarm messages and reports them to the backend device 02. Taking the collected data as a photo as an example, in addition to the message header specified by the communication protocol, the reported alarm messages should also include its own features (such as front channel identifier, device identifier, etc.), the features of the corresponding alarm type (such as capability identifier), and the corresponding data features (such as photo name, photo format, photo content, features extracted from the photo (such as face features), confidence level, etc.).

[0072] In the embodiments of the present application, the front-end device 03 may have one or more channels according to its own structure. For example, when 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 some channels may be connected to the back-end device.

[0073] In the embodiments of the present application, the data packet format reported by the front-end device 03 to the back-end device 02 is fixed to facilitate the back-end device 02 to quickly parse and identify.

[0074] In some embodiments, referring to Figure 1 As shown, in this security system, the user can also manage the back-end device 02 and the front-end device 03 through the web using their own client.

[0075] Based on the above Figure 1 As shown in the security system, 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 being connected to the first back channel of the NVR as an example, the alarm linkage configuration method provided by the embodiments of the present application will be introduced. Referring to Figure 2 As shown, the method may include 201 and 202:

[0076] 201. The NVR obtains the channel alarm capability set of the first front channel of the front-end device 03A.

[0077] Among them, the first front channel may be any front channel through which the front-end device 03A is connected to the NVR. The channel alarm capability set of the first front channel includes at least one alarm capability supported by the first front channel. There is a unique corresponding capability identifier for the alarm capability, and the capability identifier is matched with a unique corresponding alarm type. Exemplarily, the alarm capability may be an alarm capability for high-altitude parabolic, etc.; the capability identifier may be a string uniquely corresponding to the alarm capability; the alarm type may be the specific alarm type corresponding to the alarm capability. For example, the alarm type may be "high-altitude parabolic alarm". The capability identifier of the alarm capability may be simultaneously in the channel alarm capability, or there may be a separate relationship table for representing the corresponding relationship between the alarm capability and its capability identifier. The front-end device may send the relationship table to the NVR together when the NVR obtains the channel alarm capability set.

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

[0079] Specifically, the NVR can send a retrieval request to the front-end device 03A connected to itself. The retrieval request may carry the identifier of the first front channel of the channel through which the front-end device 03A is connected to the NVR (i.e., the first front-channel identifier). After receiving the retrieval request, the front-end device 03A sends at least one alarm capability (specifically, the capability identifier uniquely corresponding to the alarm capability) corresponding to the identifier of the front channel to the back-end device NVR. Generally, the at least one here is all. Of course, in practice, the NVR can obtain the channel alarm capability set of all the front channels through which the front-end device is connected to the NVR. In the technical solution provided in the embodiments of the present application, the first front channel in the subsequent part may also be other front channels through which the front-end device is connected to the back-end device. Of course, the corresponding back channel will also change accordingly.

[0080] In practice, there may be some alarm types that users do not wish to process, or do not wish to process currently (for example, the security system previously required face alarms, but now requires fire alarms, so the face alarm type does not need to be processed currently). Then, when obtaining the channel alarm capability set of the front-end device, the corresponding alarm capabilities can be filtered out. Therefore, in one feasible way, in combination with Figure 2 , referring to Figure 3 as shown, 201 may include 2011 and 2012:

[0081] 2011. The NVR obtains all the alarm capabilities supported by the first front channel of the front-end device 03A.

[0082] 2012. 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 that constitutes the channel alarm capability set, and the at least one alarm capability forms the channel alarm capability set of the first front channel.

[0083] Among them, the preset filtering rule may be a preset filtering table, and the capability identifiers of the alarm capabilities that are not desired to be processed may exist in the filtering table.

[0084] In this way, since the NVR does not obtain the alarm capabilities that the user does not wish to process from the beginning, corresponding linkage rules will not be generated subsequently. Because it has not been obtained, the NVR will not parse and identify the alarm messages corresponding to the alarm type subsequently, and there will be no relevant alarm data during the interaction with the security platform. This enriches the user experience.

[0085] 202. The NVR generates at least one linkage configuration file according to the channel alarm capability set and the alarm source.

[0086] Among them, the alarm source is used to indicate the first back channel of the NVR and / or the first front channel of the front-end device 03A.

[0087] In one implementable way, since the generation of the linkage configuration file and the subsequent matching of the alarm message and the linkage configuration are both performed on the backend device, for the purpose of convenient configuration (the first back-channel identifier is easier to obtain), the alarm source can directly be the identifier of the first back-channel of the NVR (i.e., the first back-channel identifier). In another implementable way, the alarm source can also be the identifier of the first front-channel of the front-end device 03A, i.e., the first front-channel identifier. In yet another implementable way, the alarm source can also be the first back-channel identifier and the first front-channel identifier.

[0088] The alarm types corresponding to the linkage configuration file and the centralized alarm capabilities of the channel alarm capabilities are in one-to-one correspondence. Here, "correspondence" specifically means that if a certain linkage configuration file is generated based on the capability identifier matching a certain alarm type, then the two correspond. The linkage configuration file includes an alarm source, a capability identifier matching the alarm type corresponding to the linkage configuration file, and a linkage rule. The linkage rule is used to instruct the NVR to perform corresponding linkage operations when receiving the capability identifier 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.

[0089] Exemplarily, the format of the linkage configuration file is shown in Table 1 below.

[0090] Table 1

[0091] Capability Identifier Alarm Source Linkage Rule

[0092] In the embodiments of the present application, since the linkage rule is to be matched with the channels (i.e., the first back-channel and / or the first front-channel indicated by the alarm source) connecting the backend device and the front-end device and the capability identifier matching the alarm type, and specifically which linkage operations the linkage rule needs to perform needs to be determined by the user, the linkage rule initially set by the backend device only has a format, and the specific content needs to be set in response to the user's operation. For example, if the linkage rule includes the arming time and the linkage method, the specific format of the linkage rule can be as shown in Table 2 below.

[0093] Table 2

[0094]

[0095] It can be seen that at this time, the positions in the linkage rule for filling in the specific arming time and the linkage method are empty. Of course, in practice, it can be filled with a character representing "empty", such as "0".

[0096] Based on the above technical solution, the backend device (NVR) can automatically identify the channel alarm capability set of the front-end device (composed of at least one alarm capability (specifically, the capability identifier of the alarm capability) supported by a certain front channel of the front-end device), and according to the preset rules, based on each capability identifier and the alarm source (such as the rear channel of the backend device and / or the front channel of the front-end device) that can indicate the transmission of the alarm message, automatically generate a linkage rule configuration file for each alarm type corresponding to each channel connected by the backend device and the front-end device. Moreover, in this process, the backend device does not need to identify or translate the alarm type corresponding to each alarm capability in the channel alarm capability set obtained by the front-end device, but can directly generate the linkage configuration file using the capability identifier of the alarm capability. In this way, whether there are newly updated alarm capabilities or not in the channel alarm capability set of the front-end device, it is possible to make the subsequent backend device match the capability identifier and alarm source in the previously generated linkage configuration file according to the capability identifier and the front channel identifier carried in the alarm message when receiving the alarm message on the basis that the backend device does not need to update and develop the configuration for the new alarm type separately, so as to determine the linkage configuration file corresponding to the alarm message, further determine the corresponding linkage rule and execute the corresponding operation. Compared with the prior art, this solution can make the alarm message of the new alarm type added by the updated front-end device be recognized and processed by the backend device conveniently and quickly without updating the backend device, improve the reliability of the security system, and reduce the development cost.

[0097] In addition, because there are alarm sources, capability identifiers and linkage rules in the linkage configuration file, which are associated with the alarm type (reflected by the capability identifier) and the communication channel between the backend device and the front-end device (reflected by the alarm source). Therefore, even if there are differences in the setting of the capability identifier corresponding to the same alarm type in different front-end devices, it will not cause the backend device to match the wrong linkage rule.

[0098] In some embodiments, in order to enable the backend device to provide all alarm types that it can support to the security platform, optionally, in combination with Figure 2 , referring to Figure 3 shown, after step 201, 201A may further be included:

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

[0100] Among them, the device alarm capability set consists of the alarm capabilities pre-stored by the backend device NVR. The alarm capabilities pre-stored by the NVR here are the alarm capabilities that can be recognized by the backend device and are set when the NVR leaves the factory. Of course, in the technical solution provided by the embodiments of the present application, the NVR itself does not need to identify which alarm capability the alarm message reported by the front-end device 03A specifically corresponds to, and can directly use the carried capability identifier for relevant processing. Of course, if the capability identifiers are stored in the device alarm capability set, the alarm capabilities that do not exist in the device alarm capability set and are added to the channel alarm capability set of the device alarm capability set specifically refer to their capability identifiers.

[0101] In this way, when the security platform requests all the alarm capabilities (or alarm types) that the backend device can currently support from the backend device, the backend device can send the device alarm capability set updated after the latest connection of the front-end device to the security platform.

[0102] Further optionally, when the security platform requests the device alarm capability set of the backend device, it is mainly for display to the user, and what the user generally wants to see is the name of the device type. Based on this, in combination with Figure 3 , referring to Figure 4 as shown, after 201A, the method may further include S1-S4:

[0103] S1. The NVR receives a display request from the security platform 01.

[0104] Among them, the display request is used to request the display of the device alarm capability set of the NVR.

[0105] In some embodiments, the display request may also request the display of the channel alarm capability set of the target back channel of the NVR. The channel alarm capability set of the target back channel is the channel alarm capability set of the front-end device corresponding to the target back channel and the target front channel connected to the target back channel. In this case, the display request should carry the back channel identifier of the target back channel.

[0106] S2. The NVR determines the alarm name corresponding to each alarm capability in the device alarm capability set according to the name mapping table.

[0107] The name mapping table is used to represent the alarm name corresponding to each alarm capability in the device alarm capability set. The alarm capability here may specifically be the capability identifier of the alarm capability.

[0108] The name mapping table may be set when the NVR leaves the factory.

[0109] In one implementable way, the name mapping table may refer to Table 3 shown below.

[0110] Table 3

[0111] Alarm Capability Preset Alarm Name

[0112] Among them, the preset alarm name can be the name set for the known alarm capabilities when the NVR leaves the factory. For the new alarm capabilities obtained by the NVR from the front-end devices connected to itself after leaving the factory, the NVR can add a new row in the name mapping table to place the new alarm capabilities and their corresponding preset alarm names. The preset alarm name of the new alarm capabilities can be itself.

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

[0114] In another implementable way, the name mapping table can be as shown in Table 4 below.

[0115] Table 4

[0116] Alarm Capability Preset Alarm Name Custom Name

[0117] When the name mapping table is the table shown in Table 4, the NVR can receive the name customized by the user for any alarm capability through the security platform and fill it in the position for the customized name corresponding to the alarm capability in Table 4.

[0118] In this case, the NVR can first judge whether each alarm capability identifier in the device alarm capability set has a corresponding customized name. If so, it determines its customized name as its alarm name. If not, it determines its preset alarm name as its alarm name.

[0119] It should be noted that the "alarm capability" in the name mapping table mentioned in the foregoing embodiments can actually be the "capability identifier" in practice. The alarm capabilities in the relevant descriptions can be replaced with the capability identifiers of the alarm capabilities.

[0120] S3. The NVR sends at least one alarm capability in the device alarm capability set and its corresponding alarm name to the security platform 01.

[0121] Generally, at least one here can be all. Of course, if the display request sent by the security platform in practice includes alarm screening conditions (for example, only requests to display alarm types and alarm names for the fire protection field), then at least one alarm capability here can be screened out from all the alarm capabilities in the device alarm capability set according to the alarm screening conditions.

[0122] S4. The security platform 01 receives at least one capability identifier in the device alarm capability set from the NVR and its corresponding alarm name and displays them.

[0123] All the alarm capabilities displayed by the specific security platform and their corresponding alarm names can be implemented in the manner of Table 3 or Table 4. Of course, in practice, it can also be any other feasible manner, and this application does not make specific restrictions on this.

[0124] In this way, users can quickly obtain the alarm names of all the alarm capabilities currently supported by the NVR through the security platform. Further, for the data in any process of the subsequent alarm linkage configuration method, if it can be displayed to the user for viewing through the security platform, the alarm capabilities (or the capability identifiers of the alarm capabilities) therein can be converted into alarm names for display according to this name mapping table, which is convenient for users to view more intuitively.

[0125] In some embodiments, taking the backend device as the NVR and the front-end device as the front-end device 03A, and the first front channel of the front-end device 03A accessing the first rear channel of the NVR as an example, referring to Figure 5 as shown, the method further includes S501 - S507:

[0126] S501. The security platform 01 receives a configuration trigger operation and, in response to the configuration trigger operation, sends a channel capability set acquisition request to the NVR.

[0127] Among them, the trigger configuration operation can be an operation to instruct the security platform 01 to open the linkage rule configuration page of a certain rear channel (such as the first rear channel) of the NVR. The specific operation can be any feasible operation, and this application does not make specific restrictions on this.

[0128] The channel capability set acquisition request includes the first rear channel identifier of the first rear channel indicated by the trigger configuration operation. The channel capability set acquisition request is used to request the channel alarm capability set of the first rear channel. The channel alarm capability set of the first rear channel includes all the alarm capabilities supported by the first rear channel or the 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 rear channel or the capability identifiers of the alarm capabilities). Of course, in this example, the first front channel and the first rear channel are taken as examples, and in practice, it can also be other rear channels and front channels connected between the backend device and the front-end device.

[0129] S502. The NVR receives the channel capability set acquisition request from the security platform 01 and, in response to the channel capability set acquisition request, sends the channel alarm capability set of the first rear channel to the security platform 01.

[0130] S503. The security platform 01 receives the channel alarm capability set of the first rear channel from the NVR and displays it.

[0131] Specifically, the security platform 01 can display the channel alarm capability set of the first rear channel in the form of a list.

[0132] S504. The security platform 01 receives an alarm selection operation, generates a linkage rule request indicating a first post-channel identifier and a first capability identifier in response to the alarm selection operation, and sends the linkage rule request to the NVR.

[0133] The linkage rule request may specifically include a first post-channel identifier and a first capability identifier, and is used to request a linkage rule that matches the first post-channel identifier and the first capability identifier.

[0134] Among them, if the channel alarm capabilities of the first post-channel include the alarm capabilities supported by the first post-channel and their corresponding capability identifiers, the alarm selection operation may be an operation in which the user selects a first alarm capability (or the capability identifier of the first alarm capability) from the channel alarm capabilities of the first post-channel displayed on the security platform 01. The first alarm capability may be one of at least one alarm capability in the channel alarm capabilities of the first channel mentioned in the foregoing embodiments. The first capability identifier is the capability identifier of the first alarm capability.

[0135] If the channel alarm capabilities of the first post-channel include the capability identifiers of the alarm capabilities supported by the first post-channel, the alarm selection operation may be an operation in which the user selects the capability identifier of the first alarm capability from the channel alarm capabilities of the first post-channel displayed on the security platform 01. Of course, the alarm selection operation may also be any other feasible operation, which is specifically determined according to the actual situation, and this application does not make specific limitations.

[0136] S505. The NVR receives the linkage rule request from the security platform 01.

[0137] S506. In response to the linkage rule request, the NVR determines a first linkage configuration file corresponding to the first post-channel identifier and the first capability identifier.

[0138] Among them, the first linkage configuration file may be one of at least one linkage configuration file generated according to the alarm source and the channel alarm capabilities of the first front-channel in the foregoing embodiments.

[0139] In an implementable manner, if the alarm source in the linkage configuration file generated in the foregoing embodiments is the first post-channel identifier capable of indicating the first post-channel, the first linkage configuration file corresponding to the first post-channel identifier and the first capability identifier may be directly determined from at least one linkage configuration file.

[0140] In another implementable way, if the alarm source in the generated linkage configuration file in the foregoing embodiment is the first front-channel identifier that can indicate the first front channel, the NVR needs to first determine the corresponding rear-channel identifier of the first front-channel identifier in the linkage configuration file or determine the corresponding front-channel identifier of the first rear-channel identifier in the linkage rule request according to the pre-stored channel mapping relationship, and then it can determine the first linkage configuration file corresponding to the first rear-channel identifier and the first capability identifier from at least one linkage configuration file.

[0141] In yet another implementable way, if the alarm source in the generated linkage configuration file in the foregoing embodiment is the first front-channel identifier that can indicate the first front channel and the first rear-channel identifier that can indicate the first rear channel, the first linkage configuration file corresponding to the first rear-channel identifier and the first capability identifier can be directly determined from at least one linkage configuration file.

[0142] S507. The NVR sends the first linkage rule in the first linkage configuration file to the security platform 01.

[0143] Among them, if the first linkage configuration file is newly generated after the NVR accesses a certain front-end device, the first linkage rule has no substantial content and only a format framework, as shown in Table 2.

[0144] In this way, the user can smoothly view the linkage rules corresponding to any alarm capability of any channel of the NVR through the security platform, improving the user experience.

[0145] In some embodiments, taking the rear-end device as the NVR and the front-end device as the front-end device 03A, and the first front channel of the front-end device 03A accessing the first rear channel of the NVR as an example, referring to Figure 6 As shown, the method further includes S601-S603:

[0146] S601. The security platform 01 receives the linkage modification operation, generates a linkage modification request in response to the modification operation, and sends the linkage modification request to the NVR.

[0147] Among them, the linkage modification request indicates the first rear-channel identifier, the second capability identifier, and the pending linkage rule. The linkage modification request can specifically carry the first rear-channel identifier, the second capability identifier, and the pending linkage rule, and can be used to request to update the linkage rule in the linkage configuration file matching the first rear-channel identifier and the second capability identifier with the pending linkage rule.

[0148] The specific linked modification operation may be an operation of inputting the first post-channel identifier, the second capability identifier (or the alarm capability to which the second capability identifier belongs), and the to-be-determined linkage rule, or an operation of selecting the first post-channel identifier and the second capability identifier (or the alarm capability to which the second capability identifier belongs) and inputting the to-be-determined linkage rule. The second capability identifier may be one of the capability identifiers of at least one alarm capability in the channel alarm capabilities of the first channel mentioned in the foregoing embodiments.

[0149] S602. The NVR receives a linked modification request from the security platform 01.

[0150] S603. In response to the linked modification request, the NVR updates the second linkage rule in the second linkage configuration file corresponding to the first post-channel identifier and the second capability identifier by using the to-be-determined linkage rule.

[0151] For the specific method of determining the second linkage configuration file corresponding to the first post-channel identifier and the second capability identifier, reference may be made to the relevant description of determining the first linkage configuration file corresponding to the first post-channel identifier and the first capability identifier in the foregoing, which will not be elaborated here.

[0152] In a possible implementation manner, if the first linkage rule in the foregoing embodiment has no substantial content, then S601 is executed after S507. At this time, the second capability identifier may be the first capability identifier, the to-be-determined linkage rule is the first linkage rule with some parameters added or modified by the user, and the second linkage rule is the first linkage rule with no substantial content. At this time, the linked modification operation may be an operation for the user to input the to-be-determined linkage rule. Among them, the operation of inputting the to-be-determined linkage rule may be a modification of the first linkage rule or a directly input to-be-determined linkage rule, and the present application does not make specific restrictions on this.

[0153] Optionally, because in practice, it may be caused by a malicious intrusion into the security system or a program vulnerability, and the identifier and capability identifier of the post-channel input or selected by the user through the security platform are changed to the first post-channel identifier and the second capability identifier. Therefore, for the security of the use of the security system, based on Figure 6 , with reference to Figure 7 as shown, S603 may specifically be S603A:

[0154] S603A. In response to the linked modification request, when it is determined that there is a second linkage configuration file corresponding to the first post-channel identifier and the second capability identifier, the NVR updates the second linkage rule in the second linkage configuration file corresponding to the first post-channel identifier and the second capability identifier by using the to-be-determined linkage rule.

[0155] In addition, if it is determined that there is no second linkage configuration file corresponding to the first post-channel identifier and the second capability identifier, the linkage modification request is discarded, and information such as the failure of the linkage rule modification or the inability to modify the linkage rule is indicated to the security platform.

[0156] It should be noted that when a user modifies a linkage rule and needs to select a capability identifier of an alarm capability displayed in the device alarm capability set or the channel alarm capability set of the backend device displayed on the security platform to modify the linkage rule of the alarm capability, in order to enable the user to know specifically what alarm capability (or alarm type) linkage rule is modified when modifying the linkage rule, in the embodiments of the present application, the capability identifier can have actual semantics. For example, if the alarm capability is face alarm, its capability identifier can be "face".

[0157] Based on the above solution, 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, improving the user experience.

[0158] In some embodiments, taking the backend device as an NVR, the front-end device as front-end device 03A, and the first front channel of the front-end device 03A accessing the first post-channel of the NVR as an example, with reference to Figure 8 as shown, the method further includes S801-S806:

[0159] S801. The security platform 01 receives an alarm modification operation, generates an alarm modification request in response to the alarm modification operation, and sends the alarm modification request to the NVR.

[0160] Among them, the alarm modification request indicates a first post-channel identifier and a pending alarm rule, and is used to request to update / modify the alarm rule of the front channel of a certain front-end device connected to the post-channel corresponding to the first post-channel identifier with the pending alarm rule. Specifically, the alarm modification request can carry the first post-channel identifier and the pending alarm rule.

[0161] In an implementable manner, before S801, the security platform 01 can also accept an alarm request operation, generate an alarm rule request carrying the first post-channel identifier in response to the alarm request operation, and send it to the NVR. The alarm request operation can be an operation of the user on the security platform 01, or an operation performed by the user after logging in to the security platform 01 through other devices, or an operation generated by any other feasible method, and the present application does not make specific limitations.

[0162] This alarm rule request is used to request the alarm rule of the front-end device corresponding to the first back-channel identifier. Subsequently, the NVR can send this alarm rule request to the front-end device 03A connected to its own first back-channel (the channel with the first back-channel identifier), so that the front-end device 03A sends the alarm rule of the first front-channel to which the front-end device is connected to the first back-channel to the NVR. Subsequently, the NVR will send this alarm rule to the security platform 01 for the security platform 01 to display. Thereafter, the security platform 01 executes S801.

[0163] In this case, the alarm modification operation can be the modification operation of the alarm rule displayed by the user on the security platform 01, or the operation of directly inputting the pending alarm rule. The pending alarm rule is the rule after the update of the alarm rule displayed by the security platform 01.

[0164] In the embodiment of the present application, the alarm rule specifically refers to the condition or strategy for generating an alarm message.

[0165] S802. The NVR receives an alarm modification request from the security platform 01.

[0166] S803. The NVR determines the first front-channel identifier corresponding to the first back-channel identifier according to the channel mapping relationship.

[0167] The channel mapping relationship is used to indicate the corresponding relationship between the channels of the back-end device and the channels of the front-end devices connected to the back-end device. The first back-channel identifier is the identifier of the first back-channel, and the first front-channel identifier is the identifier of the first front-channel.

[0168] S804. The NVR replaces the first back-channel identifier in the alarm modification request with the first front-channel identifier to obtain an updated alarm modification request.

[0169] The purpose of S803 and S804 is that when the front-end device 03A receives the alarm modification request sent by the NVR, if the first back-channel identifier is carried in the alarm modification request, since the first back-channel identifier may not exist in all the front-channel identifiers of the front-end device 03A, or there may be a front-channel identifier that is the same as the first back-channel identifier but is not the front-channel identifier of the front-channel connected to this NVR, in order for the front-end device 03A to accurately identify and modify the alarm rule corresponding to this alarm modification request, it is necessary to generate this updated alarm modification request.

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

[0171] 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.

[0172] Of course, in practice, the alarm rules for all front channels of the front-end device can be the same. In this case, the first back-channel identifier may not be carried in the alarm modification request, and the updated alarm modification request does not need to be generated either.

[0173] Based on the technical solutions corresponding to S801 - S806, the user can smoothly modify the alarm rules for any front channel of any front-end device corresponding to the NVR through the security platform.

[0174] Optionally, in order for the security platform 01 to know that the alarm rules of the front-end device 03A have been successfully modified, combined with Figure 8 , referring to Figure 9 as shown, after S806, S807 - S810 are further included:

[0175] S807: The front-end device 03A sends a modification response to the NVR.

[0176] The modification response indicates the first front-channel identifier, and the modification response is used to indicate that the front-end device 03A has completed the modification of the alarm rules. Specifically, the modification response may carry the first front-channel identifier.

[0177] S808: The NVR receives the modification response sent by the front-end device 03A.

[0178] S809: The NVR determines the first back-channel identifier corresponding to the first front-channel identifier according to the channel mapping relationship, and uses the first back-channel identifier to replace the first front-channel identifier indicated by the modification response to obtain an updated modification response.

[0179] The purpose of S809 is that when the user operates the security platform to modify the alarm rules of a certain front channel, the user does not need to know which front channel of which front-end device, but directly selects a certain channel of the back-end device to be modified to complete. Therefore, the subsequent modification response does not need to reflect the relevant identifier of the front-end device (i.e., the first front-channel identifier), so the modification response only needs to indicate the first back-channel identifier.

[0180] S810: The NVR sends the updated modification response to the security platform 01.

[0181] It should be noted that in practice, if the front-end device 03A fails to complete the modification of the alarm rules for any reason, the modification response in the foregoing embodiments can also be used to indicate that the front-end device 03A has not completed the modification of the alarm rules. The specific implementation process is similar and will not be elaborated here.

[0182] Based on the above solutions, the user can timely understand through the security platform whether the alarm rules of a front-end device corresponding to a certain back channel of the NVR specified by the user have been modified.

[0183] In some embodiments, in order for the backend device to successfully determine the linkage rule based on the alarm message reported by the frontend device and perform the corresponding linkage operation, taking the backend device as an NVR, the frontend device as frontend device 03A, and the first front channel of the frontend device 03A being connected to the first rear channel of the NVR as an example, referring to Figure 10 As shown, the method further includes S101 - S105:

[0184] S101. The NVR receives the alarm message from the frontend device 03A.

[0185] The alarm message carries a first front channel identifier and a third capability identifier. Specifically, the alarm message may carry the first front channel identifier and the third capability identifier. In addition, there should also be alarm - related resources in the alarm message; the data format of the alarm message can be a preset protocol format.

[0186] Among them, the third capability identifier can be one of the capability identifiers of at least one alarm capability in the channel alarm capabilities of the first front channel mentioned in the foregoing embodiments.

[0187] Exemplarily, taking the frontend device 03A collecting picture data as an example, the data format of the alarm message can be as shown in Table 5 below.

[0188] Table 5

[0189] Message Header Alarm Information Header Alarm Information Picture 1 Header Picture 1 Picture 2 Header Picture 2 …

[0190] Among them, the substantial content of the entire alarm message includes 1 alarm information and several pictures.

[0191] The message header includes the length of the entire alarm message and addressing information. The alarm information header includes the length of the alarm information. The picture X header includes the length (i.e., size) of picture X and the picture ID of picture X.

[0192] The alarm information includes basic information, feature information, and attachment information.

[0193] Among them, the basic information includes: the capability identifier (i.e., the foregoing third capability identifier), the device Internet Protocol (IP) address of the frontend device that generates the alarm message, and the front channel identifier of the front channel of the frontend device that transmits the alarm message (i.e., the foregoing first front channel identifier).

[0194] The feature information includes: descriptive information of the alarm content, such as the features of the target (license plate number, face features, etc.), confidence level (used to indicate the credibility of the target corresponding to the alarm message being a target that requires an alarm), etc.

[0195] The attachment information includes: the name and picture format of each picture, etc.

[0196] The aforementioned alarm-related resources may be all the content in the alarm message except for the first front channel identifier and the third capability identifier.

[0197] S102. The NVR parses the alarm message according to a preset rule to obtain the first front channel identifier and the third capability identifier carried in the alarm message.

[0198] Since the format of the alarm message is stipulated by the communication protocol between the NVR and the front-end device 03A, the preset rule here is the parsing rule corresponding to this communication protocol.

[0199] S103. The NVR determines the first rear channel identifier corresponding to the first front channel identifier according to the channel mapping relationship.

[0200] Among them, the channel mapping relationship is used to indicate the corresponding relationship between the channels of the back-end device (here it is the NVR) and the channels of the front-end device (here it is the front-end device 03A) connected to the back-end device. The first rear channel identifier is the rear channel identifier of the first rear channel connected to the first front channel corresponding to the first front channel identifier in the NVR.

[0201] S104. The NVR determines the third linkage configuration file corresponding to the first rear channel identifier and / or the first front channel identifier, and the third capability identifier.

[0202] Specifically, since the previously generated linkage configuration file contains alarm sources and capability identifiers indicating the communication channels (such as the first front channel and / or the first back channel) between the backend device and the frontend device, the third linkage configuration file can be accurately determined here. The third linkage configuration file here can be the linkage configuration file corresponding to the third capability identifier among at least one linkage configuration file generated in the foregoing embodiments. Whether the NVR uses the first back channel identifier, the first front channel identifier, or both to determine the third linkage configuration file in combination with the third capability identifier specifically depends on the specific content of the alarm source in the previously generated linkage configuration file. For specific reference, please refer to the foregoing relevant statements and will not be elaborated here. In some other embodiments, since the NVR itself generates many linkage configuration files, there are also many linkage rules, and the operations to be performed for different linkage rules are different. If some linkage rules that perform the same linkage operation are processed by the same processing module (which can be called the linkage processing module), the processing efficiency will be improved. Based on this, there may be multiple linkage processing modules in the actual NVR. After the communication module of the NVR receives the alarm message from the frontend device 03A, it needs to transmit the alarm message to all linkage processing modules so that the linkage processing modules that meet the requirements of the alarm message (that is, after parsing the alarm message, it is determined that the linkage rule belongs to the linkage rule that can be processed by itself) can process it.

[0203] It can be seen that since each linkage processing module needs to parse the alarm message to know whether it can be processed, all parsing actions need to be performed by each linkage processing module. In this way, it will greatly increase the consumption of the NVR's computing resources. Therefore, in order to reduce the consumption of computing resources, after receiving the alarm message, the NVR can first parse the alarm message. After obtaining the corresponding back channel identifier (that is, the first back channel identifier) and the capability identifier of the alarm capability (that is, the third capability identifier), the content of the alarm message except for the message header and the alarm information header is re-integrated into a specific data format that can be directly recognized without parsing, which can be called unified alarm information. Then, the unified alarm information can be transmitted to all linkage processing modules. In this way, since the NVR only needs to parse once as a whole, the consumption of computing resources is greatly reduced.

[0204] Exemplarily, taking the alarm message shown in Table 5 as an example, the format of the unified alarm information can be as shown in Table 6 below.

[0205] Table 6

[0206] Capability Identifier Alarm Source Alarm Time Alarm Information Number of Pictures Picture Array

[0207] Among them, the alarm source may include a back-channel identifier and / or a front-channel identifier, and the alarm time may be the time when the alarm message is uploaded to the NVR. The alarm information is the alarm information in the original data packet. The picture array may be all the picture headers and pictures in the foregoing embodiments.

[0208] Furthermore, because all the essential information in the alarm message is included in the unified alarm information, it can also be used by the NVR for the development of some other services related to the alarm message.

[0209] S105. The NVR executes corresponding linkage operations according to the linkage rules in the third linkage configuration file.

[0210] Based on the above solution, since the NVR could generate a corresponding linkage configuration file for the alarm capabilities (or alarm types) supported by each front-end device when it connected to a front-end device before, and could modify the linkage configuration file after receiving the modification operation of the user. Therefore, after the NVR receives the alarm message corresponding to any alarm capability of the front-end device and parses to obtain the corresponding back-channel identifier and capability identifier, it can successfully determine the matching linkage configuration file and linkage rules, and then complete the corresponding linkage operations. Further, since only the front-channel identifier and capability identifier in the alarm message need to be concerned here, rather than other information, it greatly reduces the complexity of the NVR processing the alarm message, and it is not necessary to perform complex development for the NVR to use it normally, which greatly reduces the cost and improves the efficiency.

[0211] In some embodiments, in practice, users may need to obtain alarm messages corresponding to some specific alarm types regularly or in real time through the security platform. Therefore, based on this, taking the back-end device as the NVR, the front-end device as the front-end device 03A, and the first front-channel of the front-end device 03A accessing the first back-channel of the NVR as an example, referring to Figure 11 as shown, the method further includes S111-S114:

[0212] S111. The NVR receives a subscription request from the security platform 01.

[0213] Among them, the subscription request indicates a fourth capability identifier, a first back-channel identifier (the identifier of the first back-channel). Specifically, the subscription request may carry a fourth capability identifier, a first back-channel identifier, and a resource transmission format. The resource transmission format is at least any one of the following: binary data, the download address of the back-end device, the cloud download address; the subscription request is used to request to subscribe to the alarm message corresponding to the fourth capability identifier and the first back-channel identifier, and requests that the format of the alarm-related resources carried in the alarm message be the resource transmission format.

[0214] Among them, the fourth alarm type may be one of the ability identifiers of at least one alarm ability in the channel alarm ability concentration of the first front channel mentioned in the foregoing embodiments. This subscription request may be generated after the security platform 01 receives a user's subscription operation.

[0215] Optionally, when a user subscribes to alarm messages of a certain alarm type through the security platform, the user does not know which alarm types the NVR supports at this time. Therefore, before S111 and S112, as shown in Figure 11 refer to Figure 12 shown, the method should also include S111A and S111B:

[0216] S111A. The NVR determines whether the fourth ability identifier in the subscription request exists in the device alarm ability set of the NVR.

[0217] If the NVR determines that the fourth ability identifier in the subscription request exists in the device alarm ability set of the NVR, then execute S112; if the NVR determines that the fourth ability identifier in the subscription request does not exist in the device alarm ability set of the NVR, then execute S111B.

[0218] Among them, the device alarm ability set is updated each time the NVR accesses the front-end device. The specific implementation can refer to the relevant description of 201A in the foregoing embodiments, and will not be elaborated here.

[0219] S111B. The NVR discards the subscription request and sends a subscription failure indication to the security platform 01.

[0220] Among them, the subscription failure indication is at least used to indicate subscription failure, and can also be used to indicate that the reason for subscription failure is that the specified alarm type does not exist.

[0221] In this way, the NVR can, after receiving the subscription request, only receive and process the subscription requests that it can process, and can also promptly inform the user of the subscription requests that it cannot process, improving the user experience.

[0222] S112. The NVR receives the alarm message from the front-end device 03A and parses the front-channel identifier, the fifth ability identifier, and the alarm-related resources carried in the alarm message according to a preset rule.

[0223] Among them, the data format of the alarm message is a preset protocol format. The specific implementation can refer to the relevant content of the foregoing S101 and S102, and will not be elaborated here.

[0224] S113. In response to a subscription request, when the NVR receives an alarm message from the front-end device 03A, if the fifth capability identifier carried in the alarm message is the fourth capability identifier and the front-channel identifier carried in the alarm message is the first front-channel identifier corresponding to the first rear-channel identifier, the NVR replaces the front-channel identifier in the alarm message with the first rear-channel identifier and converts the alarm-related resources in the alarm message into a resource transmission format to obtain an updated alarm message.

[0225] In addition, since users only need to know the information of the NVR through the security platform 01 during the actual use of the security system and do not need to know the information of the front-end device 03A. Therefore, in the embodiment of the present application, in S113, in addition to replacing the front-channel identifier in the alarm message with the first rear-channel identifier, it is also necessary to modify all the information in the alarm message that can indicate the front-end device 03A to the relevant information indicating the NVR. Exemplarily, taking the alarm message shown in Table 4 above as an example, it is also necessary to modify the device IP address of the front-end device 03A that generates the alarm message in the basic information of the alarm information to the IP address of the NVR.

[0226] In one possible implementation, if the resource transmission format is binary data, the information in the updated alarm message other than the capability identifier, front-channel identifier, and information indicating the front-end device 03A that need to be modified is the same as the original alarm message.

[0227] In another possible implementation, taking the alarm message shown in Table 4 as an example, if the resource transmission format is the download address of the back-end device, converting the alarm-related resources in the alarm message into the resource transmission format to obtain the updated alarm message can specifically be: storing all the pictures in the original alarm message in the NVR and placing the corresponding download address at the position where the pictures are stored in the original alarm message to obtain the updated alarm message.

[0228] In yet another possible implementation, taking the alarm message shown in Table 4 as an example, if the resource transmission format is the cloud download address, converting the alarm-related resources in the alarm message into the resource transmission format to obtain the updated alarm message can specifically be: storing all the pictures in the original alarm message in the cloud (such as the cloud server provided by Company A) and placing the corresponding download address at the position where the pictures are stored in the original alarm message to obtain the updated alarm message.

[0229] It should be noted that before S113, the NVR can also, as mentioned in the foregoing embodiments, first parse and process the alarm message to obtain unified alarm information. Then, based on the capability identifier and front-channel identifier carried in the content of the unified alarm information, perform the relevant processing in step S113.

[0230] S114. The NVR sends the updated alarm message to the security platform 01.

[0231] Based on the above solution, users can successfully subscribe to the alarm messages of the alarm capabilities / types they need to view through the security platform, improving the user experience of using the security system.

[0232] In some embodiments, after obtaining the alarm message, the alarm-related resources therein are generally stored for subsequent user call and view. When storing, in order to indicate the alarm-related resources belonging to different alarm capabilities / types, the capability identifier is associated with its corresponding alarm-related resources during storage (stored in the same storage area or storing the two separately and then storing the corresponding relationship between the two). Subsequently, if it is necessary to search for the alarm-related resources of a certain alarm capability / type, the capability identifier corresponding to the alarm type can be used for searching. However, because the data volume of the capability identifier itself is large, if there are many different capability identifiers, the time required to search for a certain capability identifier will be long, and the user experience is not good. To solve this problem, in combination with Figure 3 , referring to Figure 13 as shown, after 201A, the method further includes S131 - S137:

[0233] S131. The NVR determines the storage identifier of the capability identifier of each alarm capability in the device alarm capability set according to the hash algorithm, so as to obtain the target association relationship between the capability identifier of each alarm capability in the device alarm capability set and its storage identifier.

[0234] Specifically, in the embodiments of the present application, the capability identifier of the alarm capability is converted into an integer data according to the hash algorithm.

[0235] S132. When the NVR receives the alarm message from the front-end device 03A, it parses the alarm message according to the preset rules to obtain the target capability identifier carried by the alarm message.

[0236] Among them, the data format of the alarm message is the preset protocol format. The specific implementation can refer to the relevant content of the foregoing S101 and S102, which will not be elaborated here.

[0237] S133. The NVR determines the target storage identifier corresponding to the target capability identifier according to the target association relationship.

[0238] S134. The NVR associates and stores the target storage identifier, the target capability identifier, and the alarm-related resources carried by the alarm message.

[0239] Among them, the alarm-related resources can refer to the relevant expressions of the alarm message shown in Table 4 above, which will not be elaborated here.

[0240] Of course, specifically, after storing the alarm-related resources of the alarm message, S134 may further store the association relationship among the target storage identifier, the target capability identifier, and the alarm-related resources carried by the alarm message. The alarm-related resources carried by the alarm message in this association relationship may be represented by a specific identifier.

[0241] In an implementable manner, if NVR converts the alarm message into the unified alarm information shown in Table 6 before S134 is executed, then S134 may be to 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.

[0242] S135. The NVR receives a search instruction from the security platform 01.

[0243] Among them, the search instruction indicates the to-be-searched capability identifier; specifically, the search instruction may carry the to-be-searched capability identifier. This alarm instruction may be generated by a user performing a search operation on the security platform 01.

[0244] S136. In response to the search instruction, the NVR determines the to-be-searched storage identifier corresponding to the to-be-searched capability identifier according to the target association relationship, and searches for all the data associated with the to-be-searched storage identifier according to the to-be-searched storage identifier.

[0245] S137. The NVR generates a search result based on the data associated with the to-be-searched storage identifier and sends the search result to the security platform.

[0246] Specifically, the data associated with the to-be-searched storage identifier here may specifically refer to the alarm-related resources and the capability identifier associated and stored with the to-be-searched storage identifier.

[0247] Based on the above solution, the NVR can search for the alarm-related resources corresponding to the capability identifier to be searched faster, improving the user experience.

[0248] It should be noted that Figure 13 taking S131 - S137 after 202 as an example, in practice, the sequence relationship between step 202 and S131 - S137 is determined according to the actual situation, and the present application does not make specific restrictions.

[0249] Furthermore, in some other embodiments, due to the characteristics of the hash algorithm itself, different capability identifiers may be converted into the same integer data (i.e., the storage identifier). Therefore, in order to prevent the data searched by the NVR according to the storage identifier from being the alarm-related resources corresponding to multiple different capability identifiers, in combination with Figure 13 , as shown in reference to Figure 14 , S137 may specifically include S1371 - S1373:

[0250] S1371. When it is determined that there are duplicate search storage identifiers, determine the target data associated with the search capability identifier among the data associated with the search storage identifier.

[0251] S1372. Send the target data as a search result to the security platform.

[0252] S1373. When it is determined that there are duplicate search storage identifiers, determine all the data associated with the search storage identifier as the search result and send it to the security platform 01.

[0253] Based on the above solution, when determining the search result, it is necessary to determine whether the storage identifier (the search storage identifier in the embodiment) is duplicate. If there is a duplicate, the target data corresponding to the search capability identifier is screened again from all the data associated with the storage identifier, and then the target data is determined as the search result and sent to the security platform. In this way, it is ensured that the data finally received by the security platform from the NVR is the data required by the user, and the user is prevented from viewing unnecessary data.

[0254] The embodiments of the present application can divide the functional modules of the backend device according to the above method examples. For example, the backend device can correspond to each function and divide each functional module, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present disclosure is illustrative, and is only a logical function division. In actual implementation, there may be other division methods.

[0255] In the case of dividing each functional module corresponding to each function, Figure 15 shows a possible structural schematic diagram of the backend device, which is applied to a security system (such as Figure 1 shown), and the security system further includes a front-end device, and the first front channel of the front-end device is connected to the first rear channel of the backend device. The backend device includes: an acquisition module 151 and a processing module 152.

[0256] Among them, the acquisition module 151 is used to acquire the channel alarm capability set of the first front channel; the channel alarm capability set includes at least one alarm capability supported by the first front channel, there is a unique corresponding capability identifier for the alarm capability, and there is a unique corresponding alarm type for the capability identifier. The processing module 152 is used to generate at least one linkage configuration file according to the channel alarm capability set and the alarm source acquired by the acquisition module 151; the linkage configuration file corresponds to the alarm type one by one; the alarm source is used to indicate the first back channel and / or the first front channel; the linkage configuration file includes the alarm source, the capability identifier matching the alarm type corresponding to the linkage configuration file, and the linkage rule. Among them, the linkage rule is used to indicate that the backend device performs corresponding linkage operations when receiving the capability identifier in the linkage configuration file indicated by the alarm source in the linkage configuration file to which the linkage rule belongs through the channel.

[0257] Optionally, the acquisition module 151 is specifically used to: acquire all alarm capabilities supported by the first front channel; filter all alarm capabilities according to a preset filtering rule to obtain at least one alarm capability that constitutes the channel alarm capability set, and the channel alarm capability set is composed of at least one alarm capability.

[0258] Optionally, the security system further includes a security platform, and the backend device further includes a sending module 153; the acquisition module 151 is further used to receive a linkage rule request from the security platform; the linkage rule request indicates the first back channel identifier and the first capability identifier; the first capability identifier is one of the capability identifiers of at least one alarm capability; the processing module 152 is further used to determine a first linkage configuration file corresponding to the first back channel identifier and the first capability identifier in response to the linkage rule request received by the acquisition module 151; the sending module 153 is used 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 configuration file is one of at least one linkage configuration file.

[0259] Optionally, the security system further includes a security platform; the acquisition module 151 is further used to receive a linkage modification request from the security platform; the linkage modification request carries the first back channel identifier, the second capability identifier, and the pending linkage rule; the second capability identifier is one of the capability identifiers of at least one alarm capability; the processing module 152 is further used to update the second linkage configuration file corresponding to the first back channel identifier and the second capability identifier with the pending linkage rule in response to the linkage modification request received by the acquisition module 151; the second linkage configuration file is one of at least one linkage configuration file.

[0260] Optionally, the security system further includes a security platform; the backend device further includes 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 a first rear channel identifier and a pending alarm rule; the first rear channel identifier is the identifier of the first rear 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 relationship is used to indicate the corresponding relationship between the rear channels of the backend device and the front channels of the front-end device; the first front channel identifier is the identifier of the first front channel; the processing module 152 is further configured to replace the first rear channel identifier in the alarm modification request with the first front channel identifier to obtain an updated alarm modification request; the sending module 153 is 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.

[0261] 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 to indicate that the front-end device has completed the modification of the alarm rule; the processing module 152 is further configured to determine, according to the channel mapping relationship, a first rear 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 rear channel identifier to obtain an updated modification response; the sending module 153 is further configured to send the updated modification response to the security platform.

[0262] Optionally, the obtaining module 151 is further configured to receive an alarm message from the front-end device; the alarm message indicates a first front channel identifier and a third capability identifier; the third capability identifier is one of the capability identifiers of at least one alarm capability; the processing module 152 is further configured to determine, according to the channel mapping relationship, a first rear channel identifier corresponding to the first front channel identifier indicated by the alarm message received by the obtaining module 151; the channel mapping relationship is used to indicate the corresponding relationship between the channels of the backend device and the front channels of the front-end device; the processing module 152 is further configured to determine a third linkage configuration file corresponding to the first rear channel identifier and / or the first front channel identifier, and the third capability identifier; the third linkage configuration file is one of at least one linkage configuration file; the processing module 152 is further configured to perform corresponding linkage operations according to the linkage rules in the third linkage configuration file.

[0263] Optionally, the security system further includes a security platform; the backend device further includes 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 to request a subscription to an alarm message corresponding to the fourth capability identifier and the first back-channel identifier, and to request that the format of the alarm-related resources carried in the alarm message be the resource transmission format; the first back-channel identifier is the identifier of the first back-channel; the processing module 152 is further configured to, in response to the subscription request received by the obtaining module 151, when the obtaining module 151 receives an alarm message from the front-end device, if the fifth capability identifier carried in the alarm message is the fourth capability identifier, and the front-channel identifier carried in the alarm message is the identifier of the first front-channel corresponding to the first back-channel identifier, then replace the front-channel identifier carried in the alarm message with the first back-channel identifier, and set the format of the alarm-related resources in the alarm message to the resource transmission format, so as to obtain an updated alarm message; the sending module 153 is configured to send the updated alarm message obtained by the processing module 152 to the security platform.

[0264] 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 the alarm capabilities that do not exist in the device alarm capability set in the channel alarm capability set into the device alarm capability set; the device alarm capability set is composed of the alarm capabilities pre-stored in the backend device.

[0265] Further optionally, the security system further includes a security platform; the backend device further includes 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 to request a display of the device alarm capability set of the backend device; the processing module 152 is further configured to determine, according to the name mapping table, the alarm name corresponding to each alarm capability in the device alarm capability set; the name mapping table is used to represent the alarm name corresponding to each alarm capability in the device alarm capability set; the sending module 153 is configured to send at least one alarm capability in the device alarm capability set determined by the processing module 152 and its corresponding alarm name to the security platform.

[0266] Optionally, the security system further includes a security platform; the backend device further includes a sending module 153; the obtaining module 151 is further configured to receive a search instruction from the security platform; the search instruction indicates a to-be-searched capability identifier; the processing module 152 is further configured to, in response to the search instruction received by the obtaining module 151, determine a to-be-searched storage identifier corresponding to the to-be-searched capability identifier indicated by the search instruction according to the target association relationship, and find all data associated with the to-be-searched storage identifier according to the to-be-searched storage identifier; wherein, the target association relationship is used to indicate the association relationship between the capability identifier of each alarm capability in the device alarm capability set of the backend device and its storage identifier; the storage identifier is obtained based on the hash algorithm for the capability identifier of the alarm capability in the device alarm capability set; the processing module 152 is further configured to generate a search result based on the data associated with the to-be-searched storage identifier; the sending module 153 is configured to send the search result generated by the processing module 152 to the security platform.

[0267] Further optionally, the processing module 152 is specifically configured to: when it is determined that the to-be-searched storage identifier is repeated, determine target data associated with the to-be-searched capability identifier among the data associated with the to-be-searched storage identifier; and use the target data as the search result.

[0268] Regarding the backend device in the above embodiments, the specific manners of operations performed by each module and the corresponding beneficial effects have been described in detail in the embodiments of the alarm linkage configuration method described above, and will not be elaborated here.

[0269] In the case of adopting an integrated module, an embodiment of the present application provides a backend device, which can be applied to a security system (as Figure 1 shown), and the security system further includes a front-end device, and a first front channel of the front-end device is connected to a first rear channel of the backend device. The backend device may include: a storage unit and a processing unit. The processing unit is used for control and management. For example, the processing unit is used to support the backend device to execute the steps performed by each module in the backend device in the foregoing embodiments; the storage unit is used to store program codes and data of the electronic device, and specifically can support the backend device to execute the alarm linkage configuration method in the foregoing embodiments.

[0270] Wherein, taking the processing unit as a processor and the storage unit as a memory as an example. Referring to Figure 16 shown, an embodiment of the present application further provides a backend device, which includes a memory 161 and a processor 162. Among them, the memory 161 is used to store 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 embodiments.

[0271] In a specific implementation, as an embodiment, the processor 162 (162-1 and 162-2) may include one or more CPUs. For exampleFigure 16 CPU0 and CPU1 shown in Figure 16 Processor 162-1 and processor 162-2 shown in

[0272] Memory 161 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this. Memory 161 can exist independently and be connected to processor 162 through bus 163. Memory 161 can also be integrated with processor 162.

[0273] In a specific implementation, memory 161 is used to store the data in this application and the computer execution instructions corresponding to the software program that executes this application. Processor 162 can realize various functions of the backend device by running or executing the software program stored in memory 161 and calling the data stored in memory 161.

[0274] Communication interface 164 uses any device such as a transceiver to communicate with other devices or communication networks, such as a control system, a radio access network (RAN), a wireless local area network (WLAN), etc. Communication interface 164 can include a receiving unit to implement the receiving function and a transmitting unit to implement the transmitting function.

[0275] The bus 163 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus 163 can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 16 only a thick line is used to represent it in Figure 16 , but it does not mean that there is only one bus or one type of bus.

[0276] The embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium includes computer-executable instructions. When the computer-executable instructions run on the backend device in the security system, the backend device is enabled to execute the alarm linkage configuration method provided in the above embodiment.

[0277] The embodiment of the present application further provides a computer program product, including instructions. When the instructions run on the backend device in the security system, the backend device is enabled to execute the alarm linkage configuration method provided in the above embodiment.

[0278] Those skilled in the art should be able to realize that in one or more of the above examples, the functions described in the present invention can be implemented by hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. The computer-readable medium includes a computer-readable storage medium and a communication medium, where the communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0279] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0280] In several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units can be one physical unit or multiple physical units, that is, they can be located in one place or distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0281] In addition, each functional unit in various embodiments of the present invention can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such an understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of the present invention. And the aforementioned storage medium includes: USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs and other various media that can store program codes.

[0282] The above is only the specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by the present invention should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. An alarm linkage configuration method is applied to a backend device in a security system. The security system further includes a frontend device. A first front channel of the frontend device is connected to a first rear channel of the backend device. It is characterized in that, The method includes: Obtaining a channel alarm capability set of the first front channel; the channel alarm capability set includes at least one alarm capability supported by the first front channel, there is a unique corresponding capability identifier for the alarm capability, and there is a unique corresponding alarm type for the capability identifier; Generating at least one linkage configuration file according to the channel alarm capability set and the alarm source; the linkage configuration file corresponds one-to-one with the alarm type; the alarm source is used to indicate the first back channel and / or the first front channel; the linkage configuration file includes the alarm source, the capability identifier matching the alarm type corresponding to the linkage configuration file, and the linkage rule; Wherein, the linkage rule is used to indicate that when the backend device receives the capability identifier in the linkage configuration file indicated by the alarm source in the linkage configuration file to which the linkage rule belongs through the channel, it performs corresponding linkage operations.

2. The method according to claim 1, wherein The obtaining the channel alarm capability set of the first front channel includes: Obtaining all alarm capabilities supported by the first front channel; Filtering all the alarm capabilities according to a preset filtering rule to obtain the at least one alarm capability that constitutes the channel alarm capability set, and forming the channel alarm capability set by the at least one alarm capability.

3. The method according to claim 1, wherein The security system further includes a security platform, and the method further includes: Receiving a linkage rule request from the security platform; the linkage rule request indicates the first back channel identifier and the first capability identifier; the first capability identifier is one of the capability identifiers of the at least one alarm capability; In response to the linkage rule request, determining a first linkage configuration file corresponding to the first back channel identifier and the first capability identifier, and sending the first linkage rule in the first linkage configuration file to the security platform; the first linkage configuration file is one of the at least one linkage configuration file.

4. The method according to claim 1, characterized in that The security system further includes a security platform, and the method further includes: Receiving a linkage modification request from the security platform; the linkage modification request carries the first back channel identifier, the second capability identifier, and the pending linkage rule; the second capability identifier is one of the capability identifiers of the at least one alarm capability; In response to the linkage modification request, updating the second linkage configuration file corresponding to the first back channel identifier and the second capability identifier with the pending linkage rule; the second linkage configuration file is one of the at least one linkage configuration file.

5. The method according to claim 1, characterized in that The security system further includes a security platform, and the method further includes: Receiving an alarm modification request from the security platform; the alarm modification request indicates the first back channel identifier and the pending alarm rule; the first back channel identifier is the identifier of the first back channel; Determining a first front channel identifier corresponding to the first back channel identifier according to the channel mapping relationship; the channel mapping relationship is used to indicate the corresponding relationship between the back channel of the backend device and the front channel of the front-end device; the first front channel identifier is the identifier of the first front access; Replace the first back-channel identifier in the alarm modification request with the first front-channel identifier to obtain the updated alarm modification request; Send the updated alarm modification request to the front-end device so that the front-end device updates the alarm rule of the first front-channel with the pending alarm rule.

6. The method according to claim 5, characterized in that, After sending the updated pending alarm request to the front-end device, it further includes: Receive the modification response sent by the front-end device; the modification response indicates the first front-channel identifier, and the modification response is used to indicate that the front-end device has completed the modification of the alarm rule; Determine the first back-channel identifier corresponding to the first front-channel identifier according to the channel mapping relationship, and replace the first front-channel identifier indicated in the modification response with the first back-channel identifier to obtain the updated modification response; Send the updated modification response to the security platform.

7. The method according to claim 1, characterized in that, It further includes: Receive an alarm message from the front-end device; the alarm message indicates the first front-channel identifier and the third capability identifier; the third capability identifier is one of the capability identifiers of the at least one alarm capability; Determine the first back-channel identifier corresponding to the first front-channel identifier according to the channel mapping relationship; the channel mapping relationship is used to indicate the corresponding relationship between the channels of the back-end device and the front-channels of the front-end device; Determine the 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 configuration file is one of the at least one linkage configuration file; Execute corresponding linkage operations according to the linkage rules in the third linkage configuration file.

8. The method according to claim 1, wherein The security system further includes a security platform, and the method further includes: 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 to request to subscribe to an alarm message corresponding to the fourth capability identifier and the first back-channel identifier, and request that the format of the alarm-related resources carried in the alarm message be the resource transmission format; the first back-channel identifier is the identifier of the first back-channel; In response to the subscription request, when an alarm message from the front-end device is received, if the fifth capability identifier carried in the alarm message is the fourth capability identifier, and the front-channel identifier carried in the alarm message is the identifier of the first front-channel corresponding to the first back-channel identifier, then replace the front-channel identifier carried in the alarm message with the first back-channel identifier, and set the format of the alarm-related resources in the alarm message to the resource transmission format to obtain the updated alarm message; Send the updated alarm message to the security platform.

9. The method according to claim 1, wherein After obtaining the channel alarm capability set of the first front-channel, it further includes: Compare the channel alarm capability set with the device alarm capability set, and add the alarm capabilities that do not exist in the device alarm capability set in the channel alarm capability set into the device alarm capability set; the device alarm capability set consists of the alarm capabilities pre-stored by the backend device.

10. The method according to claim 9, wherein It further includes: Receive a display request from the security platform; the display request is used to request to display the device alarm capability set of the backend device; According to the name mapping table, determine the alarm name corresponding to each alarm capability in the device alarm capability set; the name mapping table is used to represent the alarm name corresponding to each alarm capability in the device alarm capability set; Send at least one alarm capability in the device alarm capability set and its corresponding alarm name to the security platform.

11. The method according to claim 1, characterized in that, The security system further includes a security platform, and the method further includes: Receive a search instruction from the security platform; the search instruction indicates the to-be-searched capability identifier; In response to the search instruction, according to the target association relationship, determine the to-be-searched storage identifier corresponding to the to-be-searched capability identifier, and search for all data associated with the to-be-searched storage identifier according to the to-be-searched storage identifier; wherein, the target association relationship is used to indicate the association relationship between the capability identifier and the storage identifier of each alarm capability in the device alarm capability set of the backend device; the storage identifier is obtained based on the hash algorithm for the capability identifier of the alarm capability in the device alarm capability set; Generate a search result based on the data associated with the to-be-searched storage identifier, and send the search result to the security platform.

12. The method according to claim 11, wherein, The generating the search result based on all the data associated with the to-be-searched storage identifier includes: In the case of determining that the to-be-searched storage identifier is repeated, determine the target data associated with the to-be-searched capability identifier among the data associated with the to-be-searched storage identifier; Use the target data as the search result.

13. A backend device is applied to a security system, and a front-end device is further included in the security system. A first front channel of the front-end device is connected to a first rear channel of the backend device. It is characterized in that The backend device includes: An acquisition module, configured to acquire the channel alarm capability set of the first front channel; the channel alarm capability set includes 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, configured to generate at least one linkage configuration file according to the channel alarm capability set and the alarm source acquired by the acquisition module; the linkage configuration file corresponds to the alarm type one by one; the alarm source is used to indicate the first rear channel and / or the first front channel; the linkage configuration file includes the alarm source, the capability identifier matching the alarm type corresponding to the linkage configuration file, and the linkage rule; Wherein, the linkage rule is used to indicate that when the backend device receives the capability identifier in the linkage configuration file through the channel indicated by the alarm source in the linkage configuration file to which the linkage rule belongs, it performs the corresponding linkage operation.

14. The backend device according to claim 13, wherein The obtaining module is specifically configured to: obtain all the alarm capabilities supported by the first front channel; filter all the alarm capabilities according to a preset filtering rule to obtain the at least one alarm capability that constitutes the channel alarm capability set, and form the channel alarm capability set with the at least one alarm capability; and / or, The obtaining module is further configured to receive an alarm message from the front-end device; the alarm message indicates the first front channel identifier and the third capability identifier; 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 the channel mapping relationship, the first back channel identifier corresponding to the first front channel identifier indicated by the alarm message received by the obtaining module; the channel mapping relationship is used to indicate the correspondence between the channels of the back-end device and the front channels of the front-end device; 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 configuration file is one of the at least one linkage configuration file; the processing module is further configured to execute a corresponding linkage operation according to the linkage rule in the third linkage configuration file; and / or, 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 the alarm capabilities that do not exist in the device alarm capability set in the channel alarm capability set into the device alarm capability set; the device alarm capability set is composed of the alarm capabilities pre-stored by the back-end device; When the security system further includes a security platform and the back-end device further includes a sending module, The obtaining module is further configured to receive a linkage rule request from the security platform; the linkage rule request indicates the first back channel identifier and the first capability identifier; the first capability identifier is one of the capability identifiers of the at least one alarm capability; the processing module is further configured to, in response to the linkage rule request received by the obtaining module, determine a first linkage configuration file corresponding to the first back channel identifier and the first capability identifier; the sending module is configured to send the first linkage rule in the first linkage configuration file determined by the processing module to the security platform; the first linkage configuration file is one of the at least one linkage configuration file; and / or, The obtaining module is further configured to receive a linkage modification request from the security platform; the linkage modification request carries the first back channel identifier, the second capability identifier, and the pending 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, in response to the linkage modification request received by the obtaining module, update the second linkage configuration file corresponding to the first back channel identifier and the second capability identifier with the pending linkage rule; the second linkage configuration file is one of the at least one linkage configuration file; And / or, The obtaining module is further configured to receive an alarm modification request from the security platform; the alarm modification request indicates a first back-channel identifier and a pending alarm rule; the first back-channel identifier is the identifier of the first back-channel; the processing module is further configured to determine, according to the channel mapping relationship, a first front-channel identifier corresponding to the first back-channel identifier indicated by the alarm modification request received by the obtaining module; the channel mapping relationship is used to indicate the correspondence between the back-channels of the backend device and the front-channels of the frontend device; the first front-channel identifier is the identifier of the first front-channel; 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 the updated alarm modification request; The sending module is configured to send the updated alarm modification request obtained by the processing module to the frontend device, so that the frontend device updates the alarm rule of the first front-channel with the pending alarm rule; And / or, After the sending module sends the updated alarm modification request obtained by the processing module to the frontend device, the obtaining module is further configured to receive a modification response sent by the frontend device; the modification response indicates the first front-channel identifier, and the modification response is used to indicate that the frontend device has completed the modification of the alarm rule; the processing module is further configured to determine, according to the 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 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 obtaining module 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 to request to subscribe to an alarm message corresponding to the fourth capability identifier and the first back-channel identifier, and request that the format of the alarm-related resources carried in the alarm message be the resource transmission format; the first back-channel identifier is the identifier of the first back-channel; the processing module is further configured to, in response to the subscription request received by the obtaining module, when the obtaining module receives an alarm message from the frontend device, if the fifth capability identifier carried in the alarm message is the fourth capability identifier, and the front-channel identifier carried in the alarm message is the first front-channel identifier corresponding to the first back-channel identifier, then replace the front-channel identifier carried in the alarm message with the first back-channel identifier, and set the format of the alarm-related resources in the alarm message to the resource transmission format to obtain the updated alarm message; the sending module is configured to send the updated alarm message obtained by the processing module to the security platform; And / or, The obtaining module is further configured to receive a display request from the security platform; the display request is used to request to display the device alarm capability set of the backend device; the processing module is further configured to determine, according to the name mapping table, the alarm name corresponding to each alarm capability in the device alarm capability set; the name mapping table is used to represent the alarm name corresponding to each alarm capability in the device alarm capability set; the sending module is configured to send at least one alarm capability and its corresponding alarm name in the device alarm capability set determined by the processing module to the security platform; and / or, The obtaining module is further configured to receive a search instruction from the security platform; the search instruction indicates a to-be-searched capability identifier; the processing module is further configured to, in response to the search instruction received by the obtaining module, determine, according to the target association relationship, the to-be-searched storage identifier corresponding to the to-be-searched capability identifier indicated by the search instruction, and search for all data associated with the to-be-searched storage identifier according to the to-be-searched storage identifier; wherein, the target association relationship is used to indicate the association relationship between the capability identifier and the storage identifier of each alarm capability in the device alarm capability set of the backend device; the storage identifier is obtained by the capability identifier of the alarm capability in the device alarm capability set based on the hash algorithm; the processing module is further configured to generate a search result based on the data associated with the to-be-searched storage identifier; the sending module is configured to send the search result generated by the processing module to the security platform; and / or, Specifically, the processing module is configured to: when it is determined that the to-be-searched storage identifier is repeated, determine the target data associated with the to-be-searched capability identifier in the data associated with the to-be-searched storage identifier; Use the target data as the search result.

15. A backend device, characterized in that, It includes a processor and a memory for storing executable instructions for processing; wherein, the processor is configured to execute the executable instructions to enable the backend device to execute the alarm linkage configuration method according to any one of claims 1-12.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions, and when the computer-executable instructions run on the backend device in the security system, the backend device is enabled to execute the alarm linkage configuration method according to any one of claims 1-12.

17. A security system, characterized in that, It includes the backend device according to claim 13 or 14, or the backend device according to claim 15.

Images