Security equipment management system, intelligent equipment and computer readable storage medium

Abstract

The invention is suitable for the technical field of security and protection, and provides a security and protection equipment management system, intelligent equipment and a computer readable storage medium. The linkage rule plug-in is used for updating a registered event type when the security and protection equipment management system generates an equipment event, or is used for updating the registered event type when the security and protection equipment management system generates a service event, the equipment event is an event related to security equipment accessing the security equipment management system, and the service event is an event related to service of the security equipment management system. Through the processing of the linkage rule plug-in, the user does not need to manually update, so that the updating efficiency is improved, and the iteration speed of the security and protection equipment management system is improved.

Description

Technical Field

[0001] This application belongs to the field of security technology, and particularly relates to a security device management system, intelligent devices, computer-readable storage media, and computer program products. Background Art

[0002] With the improvement of living standards, people hope to obtain relevant information about their working or living environments more promptly. For example, people hope to receive alarm messages in a timely manner when a fire occurs, and for another example, people hope to promptly detect smokers in the environment.

[0003] To meet the needs of users, network cameras can be installed in the environment, and the information collected by the network cameras can be processed through a security device management system, and then corresponding alarm messages can be pushed according to the processing results. For example, when it is determined that the information collected by the network camera includes fire information, an alarm message containing the information about the occurrence of a fire is pushed.

[0004] In the existing security device management system, when the event type corresponding to the alarm message changes, it is necessary for the staff to update the setting of the corresponding event type. However, since it is difficult for the staff to update the event type in a timely manner, the iteration speed of the security device management system is reduced. Summary of the Invention

[0005] Embodiments of this application provide a security device management system, intelligent devices, and computer-readable storage media, which can solve the problem of too slow iteration speed of the security device management system.

[0006] In a first aspect, embodiments of this application provide a security device management system, including a linkage rule plugin;

[0007] The linkage rule plugin is used to update the registered event types when the security device management system generates device events, or is used to update the registered event types when the security device management system generates service events, where the device events are events related to the security devices connected to the security device management system, and the service events are events related to the services of the security device management system.

[0008] The beneficial effects of the embodiments of this application compared with the prior art are:

[0009] In an embodiment of the present application, the security device management system includes a linkage rule plugin, and the linkage rule plugin updates the registered event types when a device event or a service event occurs in the security device management system. Since a device event is an event related to the security devices connected to the security device management system, and a service event is an event related to the services of the security device management system, and the security devices or the services of the security device management system are usually corresponding to event types, therefore, when a device event or a service event occurs, the linkage rule plugin updates the registered event types, which is equivalent to timely updating the event types that may change, and is beneficial to improving the accuracy of the registered event types. In addition, since the registered event types are updated by the linkage rule plugin, that is, there is no need for users to manually update, so the update efficiency is improved, thereby improving the iteration speed of the security device management system.

[0010] In a second aspect, an embodiment of the present application provides an intelligent device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the functions of the linkage rule plugin of the security device management system as described in the first aspect.

[0011] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the functions of the linkage rule plugin of the security device management system as described in the first aspect.

[0012] In a fourth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on an intelligent device, it causes the intelligent device to execute the functions of the linkage rule plugin of the security device management system as described in the first aspect.

[0013] It can be understood that the beneficial effects of the second aspect to the fourth aspect can refer to the relevant descriptions in the first aspect, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art.

[0015] Figure 1 is an interaction schematic diagram of a security device management system, security devices, and a front end provided by an embodiment of the present application;

[0016] Figure 2 is a page schematic diagram of a linkage rule provided by an embodiment of the present application;

[0017] Figure 3It is a schematic diagram of the interaction between another security device management system provided by an embodiment of the present application, security devices, and the front end;

[0018] Figure 4 It is a schematic diagram for block diagram marking of a newly added event type provided by an embodiment of the present application;

[0019] Figure 5 It is a schematic diagram of the structure of an intelligent device provided by another embodiment of the present application. Detailed implementation manners

[0020] In the following description, for the purpose of illustration rather than limitation, specific details such as specific system architectures and technologies are proposed to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0021] It should be understood that when used in the specification and claims of the present application, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0022] It should also be understood that the term "and / or" used in the specification and claims of the present application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0023] The reference to "an embodiment" or "some embodiments" etc. described in the specification of the present application means that a specific feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, the statements "in an embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways.

[0024] A security device management system is a system for monitoring, managing, and maintaining security protection devices. Its front end (such as a Web end or an application (APP) end) is usually used for centralized management and operation of security devices (such as an IP camera (IPC)), providing functions such as real-time monitoring, alarm management, and device status monitoring.

[0025] When the security equipment management system generates equipment events or service events that change, the event types involved in the security equipment management system usually also change. At this time, it is necessary for the staff to update the settings of the event types registered in the security equipment management system. Since the update settings require the participation of the staff to be realized, and it is difficult for the staff to handle them in a timely manner when the event types need to be updated. For example, if a user purchases a new algorithm plug-in (such as a fireworks detection algorithm plug-in) and installs it on the IPC managed by the security equipment management system, although the IPC can detect fireworks, since the current server does not define this event type, that is, the event type corresponding to fireworks detection does not exist in the linkage configuration rules of the server, and it takes a certain amount of time for the staff to find the server and define the corresponding event type for the server. Therefore, the user cannot set the event type corresponding to fireworks detection in the linkage configuration rules, and thus cannot control the IPC to detect fireworks through the linkage configuration rules.

[0026] In order to be able to set the event types corresponding to equipment events or service events in a timely manner, an embodiment of the present application provides a new security equipment management system.

[0027] In the new security equipment management system, there is a linkage rule plug-in, which updates the registered event types when the security equipment management system generates equipment events or service events.

[0028] For ease of understanding, the following describes in conjunction with the interaction schematic diagram of the security equipment management system provided by the embodiment of the present application with the security equipment and the front end (that is Figure 1 ).

[0029] In Figure 1 , the linkage rule plug-in included in the security equipment management system can communicate with the security equipment, such as receiving and registering the event types reported by the security equipment, and the registered event types are event types that can be configured by the user. The linkage rule plug-in can also communicate with the front end. When the user communicates with the security equipment management system through the front end (such as the Web end or the APP end), the linkage rule plug-in sends the registered event types to the front end. In this way, the user can configure the event types presented on the front end.

[0030] In the embodiments of the present application, the linkage rule plugin included in the security device management system is based on an event type registration mechanism. The information related to the event type in its code is not fixed, but can be changed. For example, by providing an interface for other business parties to call this interface to register their own event types, the event types of the linkage rule plugin can be changed. With such a setting, the linkage rule plugin can be configured by the user into the linkage rules after the event type is registered, thus greatly improving the scalability of the event type and further increasing the iteration speed of the security device management system.

[0031] Specifically, the linkage rule plugin is used to update the registered event types when the security device management system generates a device event, or is used to update the registered event types when the security device management system generates a service event, where the device event is an event related to the security devices connected to the security device management system, and the service event is an event related to the services of the security device management system.

[0032] The above-mentioned security devices refer to the general term for various devices and technologies used to ensure the security of personnel, property, information, etc. The security devices and the security device management system they are connected to help users prevent security threats such as theft, fire, illegal intrusion, and accidents through functions such as prevention, detection, alarm, and monitoring. Optionally, the above-mentioned security device can be a network camera, which can be connected to the network in a wired manner or in a wireless manner. In addition, the security devices connected to the security device management system can also be door magnetic sensors for detecting the opening and closing status of doors and windows, vibration detectors for detecting vibrations during illegal intrusion, etc., which are not limited here.

[0033] The above-mentioned device events include the access events of security devices to the security device management system. For example, when the security device is a network camera, an access event will be generated when the security device management system accesses the network camera, that is, a device event is generated. The device event also includes the installation event of installing an algorithm plugin on the security device that has been connected to the security device management system. Among them, the algorithm plugin is a module encapsulating specific algorithm logic, usually used to implement functions such as data processing, analysis, and prediction. It interacts with the main program through a defined unified interface and can flexibly expand or replace algorithm functions without modifying the core logic of the main program.

[0034] The above-mentioned service events include the installation events generated when various business plugins are installed in the security management system. Among them, the business plugin focuses on implementing specific business logics and is used to expand the business functions of the main program. It usually involves data reading, processing, and storage and is closely integrated with the business process.

[0035] The above-mentioned event types refer to the types of events that security devices or service plugins, etc. can support detection for. Such event types include not wearing a safety helmet, not wearing safety clothing, a vehicle entering a parking space, a vehicle leaving a parking space, driving detection, a vehicle stopping stably in a parking space, cross-parking, vehicle congestion detection, and so on. When an event type is not registered in the linkage rule plugin of the security management system, the user cannot configure the unregistered event type through the linkage rules of the security management system. However, when an event type is registered in the linkage rule plugin of the security management system, the user can configure the registered event type in the linkage rules.

[0036] Figure 2 shows a page schematic diagram of a linkage rule provided by an embodiment of the present application. In Figure 2 it, the event types include "area intrusion", "human detection", and "electric vehicle detection". Taking the "human detection" event type as an example, if a certain device among 20 pre-selected devices detects a human figure, the pan-tilt of this device or other devices can be controlled to obtain more human figure information, and the detected human figure picture can be highlighted for 5 seconds for alarm, and alarms can be sent through methods such as broadcast, SMS sending, and email sending.

[0037] Considering that different security devices or different services usually support different types of detectable events, therefore, when the security management system generates a device event or a service event, the registered event types in the security management system usually need to be updated. For example, after a new security device is connected to the security management system, some event types may need to be added to the registered event types, or, after a security device that has been connected to the security management system withdraws from the connection, some event types may need to be deleted from the registered event types to improve the accuracy of the registered event types, and further improve the accuracy of the user's configuration of the event types. In the embodiment of the present application, when there are no registered event types in the linkage rule plugin, the number of the registered event types is 0, and conversely, the number of the registered event types is greater than 0. When a certain event type is registered in the linkage rule plugin, this event type will be able to be configured by the user in the linkage rule, and the security management system will then perform corresponding linkage control according to the linkage rule.

[0038] In the embodiments of the present application, the security device management system includes a linkage rule plugin, and the linkage rule plugin updates the registered event types when device events or service events occur in the security device management system. Since device events are events related to the security devices connected to the security device management system, and service events are events related to the services of the security device management system, and security devices or the services of the security device management system are usually corresponding to event types, therefore, when device events or service events occur, the linkage rule plugin updates the registered event types, which is equivalent to timely updating the event types that may change, facilitating improving the accuracy of the registered event types. In addition, since the registered event types are updated by the linkage rule plugin, that is, there is no need for users to manually update, thus, the update efficiency is improved, and thereby the iteration speed of the security device management system is increased.

[0039] In some embodiments, considering that the event types corresponding to different security devices are usually different, therefore, in order to reduce the probability that event types are missed and registered to the linkage rule plugin, after a new security device is connected to the security device management system, the newly connected security device needs to report all the event types it supports, that is, when the security device management system generates device events, the linkage rule plugin updates the registered event types, including:

[0040] When the security device newly connects to the security device management system, the linkage rule plugin receives all the event types actively reported by the security device, and updates the registered event types according to the received all the event types.

[0041] Among them, all the event types actively reported by the security device here refer to all the event types corresponding to all the events that the security device can detect. For example, assume that security device A can detect the following events: (1) event of not wearing a safety helmet; (2) event of not wearing safety clothing; (3) smoke detection event. Then when the security device A is connected to the security device management system, the security device A actively reports the event types corresponding to the event of not wearing a safety helmet, the event types corresponding to the event of not wearing safety clothing, and the event types corresponding to the smoke detection event. The linkage rule plugin registers the received event types to achieve the update of the registered event types.

[0042] Optionally, when the linkage rule plugin updates the registered event types according to the received full set of event types, it deduplicates the received full set of event types according to the registered event types (e.g., deduplicates according to the event type name and / or the description of the event type), and then registers the remaining event types after deduplication to update the registered event types. For example, when the registered event types do not include the "not wearing a safety helmet event" and the "smoke detection event" reported by the security device A, the "not wearing a safety helmet event" and the "smoke detection event" are registered in the linkage rule plugin. However, when the registered event types include the "not wearing safety clothing event" reported by the security device A, the "not wearing safety clothing event" is not registered in the linkage rule plugin. Of course, if the registered event types include all the event types reported by the security device A, there is no need to register new event types in the linkage rule plugin. At this time, the updated registered event types are the same as the registered event types before the update.

[0043] Since deduplication is performed when registering event types, the probability of the same event type being repeatedly registered is reduced.

[0044] In some embodiments, when the device event is generated in the security device management system, the linkage rule plugin updates the registered event types, including:

[0045] After the linkage rule plugin installs a new algorithm plugin in the security device, it receives the event types corresponding to the algorithm plugin actively reported by the security device, and updates the registered event types according to the received event types.

[0046] Specifically, considering that different algorithm plugins installed in security devices can usually implement different detection functions, when a new algorithm plugin is installed in a security device, it actively reports the event types corresponding to the algorithm plugin (i.e., the incremental event types of the security device). The linkage rule plugin updates the registered event types according to the received incremental event types. Since the linkage rule plugin only receives the event types corresponding to the new algorithm plugin installed in the security device, and installing a new algorithm plugin only affects the event types corresponding to the new algorithm plugin, updating the registered event types in the above manner is beneficial to improving the update efficiency.

[0047] Optionally, when the linkage rule plugin updates the registered event types according to the received event types, it deduplicates the received incremental event types according to the registered event types (e.g., deduplicates according to the event type name and / or the description of the event type), and then registers the remaining event types after deduplication to update the registered event types.

[0048] Optionally, when the linkage rule plugin provided in the embodiment of the present application communicates directly with the security device, the linkage rule plugin can directly receive the full (or incremental) event types actively reported by the security device. When the linkage rule plugin provided in the embodiment of the present application does not communicate directly with the security device (such as through gateway forwarding), the security device actively reports the full (or incremental) event types to the gateway, and the gateway then forwards the received full event types to the linkage rule plugin, so that after the linkage rule plugin de-duplicates and registers, it is stored in the corresponding database.

[0049] Optionally, for the convenience of event type management, the event types can be classified into two levels. At this time, the format of the message body used by the security device to report event types includes the information of the first-level classification and the second-level classification of the event types, as shown in Table 1 below.

[0050] Table 1:

[0051]

[0052] In Table 1, "newMsg" represents the new event types reported by the security device, and the new event types are the event types that the security device has not reported.

[0053] Since the format of the message body used by the security device to report event types includes the information of the first-level classification and the second-level classification of the event types, the linkage rule plugin of the security device management system can obtain more detailed classification information of the event types, which is conducive to more detailed classification and management of the event types according to the obtained classification information.

[0054] In some embodiments, the security device management system further includes a service plugin. When a service event occurs in the security device management system, the linkage rule plugin updates the registered event types, including:

[0055] After the service plugin is installed in the security device management system and started, the service plugin actively registers event types with the linkage rule plugin, so that the linkage rule plugin updates the registered event types according to the registered event types.

[0056] Specifically, after the service plugin is installed in the security device management system, it needs to register event types with the linkage rule plugin in the following two scenarios: one is when the service plugin is first installed and started, and the other is after service upgrade (that is, when the code implementation of the service plugin has changes).

[0057] In the embodiments of the present application, the service plugin can call the Remote Procedure Call (RPC) interface of the linkage rule plugin through the startup hook (i.e., Hook), and register the corresponding event type with the linkage rule plugin through the called RPC interface. Among them, Hook is a mechanism that allows plugins to insert custom logic when specific lifecycle nodes or events occur. For the case where the service plugin is first installed and started, the service plugin can call the RPC interface through the first startup hook to implement the registration of the corresponding event type; for the case after the service plugin is upgraded, the service plugin can call the RPC interface through the upgraded hook to implement the registration of the corresponding event type. It should be noted that when the first startup hook calls the RPC interface to register the event type, it usually deduplicates all the event types that the service plugin can detect with the registered event types before registration, and when the upgraded hook calls the RPC interface to register the event type, it usually deduplicates the event types added after the service plugin is upgraded with the registered event types before registration.

[0058] Since different service plugins may be installed in the security device management system, the linkage rule plugin provides an RPC interface that can be called by the hook of the service plugin, enabling the service plugin to call the RPC interface through the startup hook to register the corresponding event type with the linkage rule plugin, so that the linkage rule plugin can update the corresponding event type, which is beneficial to improving the flexibility of event type registration.

[0059] Optionally, the RPC interface (i.e., the registration interface for registration) can be as shown in Table 2 below.

[0060] Table 2:

[0061]

[0062] According to Table 2, the first-level type and second-level type of the event type can be reported through the registration interface, and the Chinese name of the event type is also included. Therefore, the service plugin can accurately register the event type by calling this registration interface.

[0063] In some embodiments, when the service event is generated in the security device management system, the linkage rule plugin updates the registered event type, including:

[0064] When the service plugin is uninstalled from the security device management system, the service plugin actively cancels the event type with the linkage rule plugin, so that the linkage rule plugin can update the registered event type according to the cancelled event type.

[0065] Specifically, when the security device management system uninstalls a service plugin, the service plugin calls the RPC interface of the linkage rule plugin through the uninstall hook to cancel the event type corresponding to the service plugin in the linkage rule plugin, thereby updating the registered event types of the linkage rule plugin. Optionally, to improve the accuracy of canceling the event type, when canceling the event type, the linkage rule plugin takes the event type corresponding to the uninstalled service plugin as the type to be canceled, and matches the to-be-canceled event type with the event types corresponding to other service plugins installed in the security device management system (i.e., service plugins that are not currently uninstalled by the security device management system) or the connected security devices. If the same event type is matched, it indicates that even after the service plugin is uninstalled, the security device management system still has the detection function for the corresponding event type. At this time, the event type corresponding to the uninstalled service type may not be canceled. Otherwise, if no same event type is matched, it indicates that after the service plugin is uninstalled, the security device management system will not have the detection function for the corresponding event type. At this time, the event type corresponding to the uninstalled service type is canceled to update the registered event types of the linkage rule plugin.

[0066] In some embodiments, the user can communicate with the linkage rule plugin through the front end to obtain the registered event types of the linkage rule plugin. That is: The linkage rule plugin provided in the embodiments of the present application is further used for:

[0067] After receiving a request for configurable event types sent by the front end, sending the registered event types to the front end.

[0068] Wherein, the configurable event type is the registered event type of the linkage rule plugin.

[0069] Specifically, after the linkage rule plugin receives a request for configurable event types sent by the front end, it sends the registered event types stored in it to the front end. Optionally, if the linkage rule plugin stores filtering information for filtering event types, the request for configurable event types sent by the front end may also include filtering information. After the linkage rule plugin filters the registered event types according to the filtering information included in the received request, it then sends the filtered event types to the front end. Among them, the above filtering information includes one or more of the following: the name of the event type, the identity identifier of the security device to which the event type belongs, the registration time information, etc.

[0070] Figure 3 Shows another interaction schematic diagram of the security device management system, the security device, and the front end provided by the embodiments of the present application. In Figure 3In the [system], when the security device management system installs a service plugin, the service plugin calls the interface of the linkage rule plugin through the hook at the first startup (or the hook after service upgrade) to register the corresponding event type. After the event type is successfully registered, the linkage rule plugin returns the information of "OK" to the service plugin, so that the security device can know that the gateway has successfully received the event type. Of course, if the event type registration fails, the linkage rule plugin can return the information corresponding to the failure to the service plugin, which is not limited here.

[0071] When the security device management system uninstalls a service plugin, the service plugin calls the interface of the linkage rule plugin through the uninstall hook to cancel the corresponding event type. After the event type is successfully cancelled, the linkage rule plugin returns "OK" to the service plugin.

[0072] When a security device first accesses the security management system, the security device reports all event types to the gateway. When a security device that has accessed the security management system installs a new algorithm plugin, the security device reports incremental event types to the gateway. After the network receives the event type, it returns the information of "OK" to the security device, so that the security device can know that the gateway has successfully received the event type. The gateway forwards the event types it receives to the linkage rule plugin, and the linkage rule plugin performs deduplication processing on the received event types and stores them in the corresponding database.

[0073] After the user sends a request for configurable event types to the linkage rule plugin through the front end (such as the Web end or the APP end), the linkage rule plugin returns the event types corresponding to the request.

[0074] Optionally, the event types returned by the linkage rule plugin are returned in the form of a list for the convenience of the user to view.

[0075] In some embodiments, the linkage rule plugin sends the registered event types to the front end, including:

[0076] In the case where the registered event types include a first event type and a second event type, mark the first event type or the second event type to obtain the corresponding marking information, and send the registered first event type, second event type, and marking information to the front end, where the first event type refers to the event type that was not included in the event types sent to the front end last time, and the second event type refers to the event type that was included in the event types sent to the front end last time.

[0077] Specifically, when marking the first event type, the obtained marking information is used to indicate that the first event type is an event type not included in the event types sent to the front end last time; when marking the second event type, the obtained marking information is used to indicate that the second event type is an event type included in the event types sent to the front end last time.

[0078] When the above marking information is the marking information obtained by marking the first event type, the user can quickly learn from the marking information that the first event type is a newly added event type. For example, assume that the event types obtained by the user through the front end at time T1 are "area intrusion" and "motion detection", and between time T1 and T2, the newly registered event types by the linkage rule plugin are "channel occupancy" and "smoke detection". Then, the event types obtained by the user through the front end at time T3 (this time T3 is after time T2) usually include "area intrusion", "motion detection", "channel occupancy", and "smoke detection". And since "channel occupancy" and "smoke detection" are newly added event types, therefore, "channel occupancy" and "smoke detection" will be marked.

[0079] Optionally, the above marking information includes text descriptions and also graphic markings, such as markings by block diagrams. As Figure 4 shown, Figure 4 it shows a schematic diagram of marking newly added event types by block diagrams provided by an embodiment of the present application. In Figure 4 it, since the event types boxed by the dotted block diagram are "channel occupancy" and "smoke detection", therefore, the "channel occupancy" and "smoke detection" are newly added event types. After the user quickly determines the newly added event types according to the marking information, the user can quickly configure the linkage rules for the newly added event types, thereby improving the configuration efficiency.

[0080] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0081] Figure 5 It is a schematic structural diagram of an intelligent device provided by an embodiment of the present application. As Figure 5 shown, the intelligent device 5 in this embodiment includes: at least one processor 50 ( Figure 5 only one processor is shown in

[0082] The intelligent device 5 may be a computing device such as a desktop computer, a notebook, a palm computer, and a cloud server. The intelligent device may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art can understand that Figure 5 merely examples of the intelligent device 5, which do not constitute a limitation on the intelligent device 5, may include more or fewer components than shown in the figure, or combine some components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0083] The so-called processor 50 may be a central processing unit (CPU), and the processor 50 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0084] The memory 51 may be an internal storage unit of the intelligent device 5 in some embodiments, such as the hard disk or memory of the intelligent device 5. The memory 51 may also be an external storage device of the intelligent device 5 in other embodiments, such as a plug-in hard disk equipped on the intelligent device 5, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Further, the memory 51 may also include both the internal storage unit and the external storage device of the intelligent device 5. The memory 51 is used to store an operating system, application programs, a boot loader, data, and other programs, such as the program code of the computer program, etc. The memory 51 may also be used to temporarily store data that has been output or will be output.

[0085] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiments can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working processes of the units and modules in the above system can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated here.

[0086] An embodiment of this application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor. When the processor executes the computer program, the functions of the linkage rule plug-in of the above security device management system are implemented.

[0087] An embodiment of this application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the functions of the linkage rule plug-in of the above security device management system can be implemented.

[0088] An embodiment of this application provides a computer program product. When the computer program product runs on an intelligent device, the intelligent device can implement the functions of the linkage rule plug-in of the above security device management system when executed.

[0089] When 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 computer-readable storage medium. Based on this understanding, to implement all or part of the processes in the above method embodiments of this application, a computer program can be used to instruct the relevant hardware to complete. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the photographing device / smart device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disc, etc. In some jurisdictions, according to legislation and patent practice, the computer-readable medium cannot be an electrical carrier signal and a telecommunication signal.

[0090] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0091] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0092] In the embodiments provided in this application, it should be understood that the disclosed device / network device and method can be implemented in other ways. For example, the device / network device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

[0093] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0094] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A security equipment management system, characterized in that: Including linkage rule plug-in; The linkage rule plug-in is used to update the registered event type when the security device management system generates a device event, or to update the registered event type when the security device management system generates a service event, wherein the device event is an event related to the security device connected to the security device management system, and the service event is an event related to the service of the security device management system.

2. The security equipment management system according to claim 1, characterized in that: The linkage rule plug-in updates the registered event type when the security device management system generates a device event, including: When the security device is newly connected to the security device management system, the linkage rule plug-in receives a full amount of event types actively reported by the security device, and updates the registered event types according to the received full amount of event types.

3. The security equipment management system according to claim 1, characterized in that: The linkage rule plug-in updates the registered event type when the security device management system generates a device event, including: After the new algorithm plug-in is installed in the security device, the linkage rule plug-in receives the event type corresponding to the algorithm plug-in actively reported by the security device, and updates the registered event type according to the received event type.

4. The security equipment management system according to claim 1, characterized in that: The security equipment management system further includes a service plug-in, and the linkage rule plug-in updates the registered event type when the security equipment management system generates a service event, including: After the service plug-in is installed in the security device management system and started, the service plug-in actively registers the event type with the linkage rule plug-in, so that the linkage rule plug-in updates the registered event type according to the registered event type.

5. The security equipment management system according to claim 1, characterized in that: The linkage rule plug-in updates the registered event type when the security device management system generates a service event, including: When the service plug-in is uninstalled from the security device management system, the service plug-in actively deregisters the event type to the linkage rule plug-in, so that the linkage rule plug-in updates the registered event type according to the deregistered event type.

6. The security equipment management system according to claim 1, characterized in that: The linkage rule plug-in is further used to send the registered event type to the front end after receiving a request for a configurable event type sent by the front end.

7. The security equipment management system according to claim 6, characterized in that: The sending the registered event type to the front end includes: In the case that the registered event types include a first event type and a second event type, the first event type is marked or the second event type is marked to obtain corresponding marking information, and the registered first event type, the second event type and the marking information are sent to the front end, wherein the first event type refers to an event type that is not included in the event type sent to the front end last time, and the second event type refers to an event type included in the event type sent to the front end last time.

8. An intelligent device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the function of the linkage rule plug-in of the security equipment management system according to any one of claims 1 to 7 is realized.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the function of the linkage rule plug-in of the security equipment management system according to any one of claims 1 to 7 is realized.

10. A computer program product, characterized in that It comprises a computer program, and when the computer program is run, the function of the linkage rule plug-in of the security equipment management system according to any one of claims 1 to 7 is executed.

Images