Monitoring equipment, plug-in updating method and device thereof and program product

Abstract

The invention relates to the field of monitoring, in particular to monitoring equipment, a plug-in updating method and device of the monitoring equipment and a program product. The method comprises the following steps: when monitoring that a new plug-in is installed in monitoring equipment, acquiring a monitoring video event type included in the new plug-in; comparing the monitoring video event type included in the new plug-in with a preset range of monitoring video event types which can be recognized by firmware, and determining an unrecognizable monitoring video event type; and establishing a mapping relationship between the unrecognizable monitoring video event type and a preset null event type, and operating the video fragment corresponding to the new plug-in according to the mapping relationship. The video fragment corresponding to the new plug-in can be effectively operated according to the mapping relation, so that the compatibility of the new plug-in and firmware is effectively improved, the video fragment corresponding to the new plug-in is conveniently searched, and the use experience of a user using the plug-in of the monitoring equipment is improved.

Description

Technical Field

[0001] The present application relates to the field of monitoring, and in particular to monitoring equipment and its plug-in updating method, device and program product. Background Art

[0002] IPC (Internet Protocol Camera) supports multiple detection functions, and different detection functions correspond to different types of surveillance video events. Currently, most IPC models support a fixed number of detection functions. If you need to support new detection functions, you need to upgrade the IPC firmware version to achieve it, that is, the detection function is coupled with the firmware.

[0003] In order to better meet the needs of users to manage existing detection functions and use new detection functions, the algorithm mall function is proposed to present various detection functions in the mall in the form of plug-ins. Users can download plug-ins supported by IPC from the algorithm mall and manage the downloaded plug-ins on IPC, including installation, uninstallation, switch control, settings, etc. In this way, the plug-in and firmware are decoupled, allowing users to adjust the plug-in they use without upgrading the IPC firmware.

[0004] The IPC is updated and managed in the form of a plug-in, which effectively improves the flexibility of the detection function management. However, the IPC firmware may not be able to recognize the new surveillance video event type supported by the new plug-in, that is, the video triggered by the surveillance video event type of the new plug-in may not be recognized and the video clips may not be saved, or when the client queries, plays back or downloads the video, the video clips triggered by the surveillance video event type of the new plug-in may not be found because the new plug-in is not effectively compatible with the firmware, which is not conducive to improving the user experience of using the plug-in of the monitoring device. Summary of the invention

[0005] In view of this, the embodiments of the present application provide a monitoring device and its plug-in update method, device and program product to solve the problem in the prior art that the new plug-in is not effectively compatible with the firmware and may not be able to find the video clips triggered by the monitoring video event type of the new plug-in, which is not conducive to improving the user experience of using the plug-in of the monitoring device.

[0006] A first aspect of an embodiment of the present application provides a method for updating a plug-in of a monitoring device, the method comprising:

[0007] When a new plug-in is detected to be installed on the monitoring device, obtaining the type of monitoring video event included in the new plug-in;

[0008] Compare the surveillance video event types included in the new plug-in with the range of surveillance video event types that can be recognized by the preset firmware to determine unrecognizable surveillance video event types;

[0009] A mapping relationship between the unrecognizable surveillance video event type and a preset empty event type is established, and the video clip corresponding to the new plug-in is operated according to the mapping relationship.

[0010] In combination with the first aspect, in a first possible implementation manner of the first aspect, after obtaining the surveillance video event type included in the new plug-in, the method further includes:

[0011] Comparing the surveillance video event type included in the new plug-in with a preset range of identifiable surveillance video event types to determine the identifiable surveillance video event type;

[0012] The identifiable surveillance video event type and the video clip are associated and stored, and the video clip is recorded when the surveillance video event represented by the identifiable surveillance video event type is triggered.

[0013] In combination with the first aspect, in a second possible implementation manner of the first aspect, operating the video clip corresponding to the new plug-in according to the mapping relationship includes:

[0014] In the case where a surveillance video event represented by an unrecognizable surveillance video event type included in the new plug-in is triggered to record, searching for an empty event type corresponding to the unrecognizable surveillance video event type according to the mapping relationship;

[0015] The video clip is associated with the empty event type and stored, and the video clip is recorded when a surveillance video event represented by an unrecognizable surveillance video event type included in the new plug-in is triggered.

[0016] In combination with the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, after the video segment determined when the surveillance video event is triggered is associated with the empty event type and stored, the method further includes:

[0017] Obtaining an operation request for a video clip of the new plug-in;

[0018] Determine a target empty event type corresponding to the unrecognizable surveillance video event type according to a correspondence between the unrecognizable surveillance video event type and the empty event type;

[0019] A corresponding video clip is determined according to the target empty event type.

[0020] In combination with the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the operation request is a query request, and the query request includes the start and end time of the video segment requested to be queried;

[0021] Determining a corresponding video clip according to the target empty event type includes:

[0022] According to the start and end times included in the query request, a first target video segment is searched in the video segments corresponding to the target empty event type.

[0023] In combination with the third possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the operation request is a playback request or a download request, and the playback request or the download request includes a start time of the playback or the download;

[0024] Determining a corresponding video clip according to the target empty event type includes:

[0025] According to the start time included in the playback request or the download request, a second target video segment for playback or downloading is determined in the video segment corresponding to the target empty event type.

[0026] In combination with any one of the first aspect to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, before comparing the surveillance video event type included in the new plug-in with the range of surveillance video event types identifiable by a preset firmware, the method further includes:

[0027] Determine a first number of surveillance video event types included in the plug-in in the surveillance device, and determine a second number of empty event types of the surveillance device, and determine a coding identification sequence of the surveillance video event types and the empty event types according to the first number and the second number, wherein the coding identification in the coding identification sequence is a continuous coding identification, and the coding order of the coding identification of the empty event type is after the coding identification of the surveillance video event type;

[0028] After comparing the surveillance video event types included in the new plug-in with the range of surveillance video event types that can be identified by the preset firmware and determining unidentifiable surveillance video event types, the method includes:

[0029] Searching the list of empty event types for which no mapping relationship is established according to the coding identifier;

[0030] A mapping relationship is established between the empty event type for which no mapping relationship is established and the unrecognizable surveillance video event.

[0031] A second aspect of an embodiment of the present application provides a plug-in updating device for a monitoring device, the device comprising:

[0032] A monitoring video event type acquisition unit, used to acquire the monitoring video event type included in the new plug-in when detecting that a new plug-in is installed in the monitoring device;

[0033] A comparison unit, configured to compare the surveillance video event type included in the new plug-in with a preset range of surveillance video event types identifiable by the firmware, and determine unidentifiable surveillance video event types;

[0034] The mapping relationship establishing unit is used to establish a mapping relationship between the unrecognizable surveillance video event type and a preset empty event type, and operate the video clip corresponding to the new plug-in according to the mapping relationship.

[0035] A third aspect of an embodiment of the present application provides a monitoring device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the monitoring device implements a method as described in any one of the first aspects.

[0036] A fourth aspect of the embodiments of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method in the first aspect or its various implementations.

[0037] A fifth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in any one of the first aspects are implemented.

[0038] The sixth aspect of the embodiment of the present application provides a chip for implementing the methods in each implementation of the first aspect. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in the first aspect or its implementation.

[0039] Compared with the prior art, the embodiments of the present application have the following beneficial effects: when a new plug-in is installed in a monitoring device, the embodiments of the present application obtain the monitoring video event type included in the new plug-in, and determine whether the monitoring video event range in the new plug-in includes unrecognizable monitoring video event types through a preset range of monitoring video event types recognizable by the firmware; if there are unrecognizable monitoring video event types, a mapping relationship between the unrecognizable monitoring video event type and a preset empty event type is established; since the empty event type is an event type recognizable by the monitoring device, the video clip corresponding to the new plug-in can be effectively operated according to the mapping relationship, thereby effectively improving the compatibility of the new plug-in with the firmware, facilitating the search for the video clip corresponding to the new plug-in, and improving the user experience of using the plug-in of the monitoring device. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0041] Figure 1 It is a schematic diagram of an implementation scenario of a plug-in update method for a monitoring device provided in an embodiment of the present application;

[0042] Figure 2 It is a schematic diagram of an implementation flow of a plug-in update method for a monitoring device provided in an embodiment of the present application;

[0043] Figure 3 This is a schematic diagram of a coding identification sequence provided in an embodiment of the present application;

[0044] Figure 4 This is a schematic diagram of a coding identification sequence after firmware update provided by an embodiment of the present application;

[0045] Figure 5 A schematic diagram of a mapping relationship for updating an empty event type provided in an embodiment of the present application;

[0046] Figure 6 This is a schematic diagram of the interaction process between a user terminal and a monitoring device provided in an embodiment of the present application;

[0047] Figure 7 It is a schematic diagram of a plug-in updating device for a monitoring device provided in an embodiment of the present application;

[0048] Figure 8 It is a schematic diagram of a monitoring device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may 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 prevent unnecessary details from obstructing the description of the present application.

[0050] In order to illustrate the technical solution described in this application, a specific embodiment is provided below for illustration.

[0051] As an important video surveillance device, IPC (network camera) can identify and record specific surveillance video event types through detection function. The detection function is the basis for IPC to identify specific events, such as motion detection, sound detection, etc. Each detection function corresponds to one or more surveillance video event types, which define when the IPC starts recording, alarming, etc. The fixed number of detection functions limits the monitoring capabilities of IPC, so that it can only handle preset surveillance video event types. If new detection functions need to be added, they usually need to be implemented through firmware upgrades. Firmware upgrades may involve complex development and testing processes, which limits the rapid deployment and application of new functions.

[0052] In order to solve the limitation of firmware upgrade, the detection function can be provided to users in the form of plug-ins through the algorithm mall. Users can browse, download and install the required plug-ins in the algorithm mall to expand the detection function of IPC. This management method decouples plug-ins and firmware, allowing users to adjust the functions of IPC as needed without upgrading the firmware.

[0053] Although the plug-in format increases the flexibility of using surveillance video event types, the IPC firmware may not be able to recognize the surveillance video event types supported by the new plug-in. This may cause the video triggered by the new plug-in to not be correctly recognized and saved, and the user cannot query, play back or download the video triggered by the new plug-in, and cannot fully utilize the functions provided by the new plug-in, affecting the user experience of the surveillance device.

[0054] Figure 1 A schematic diagram of an implementation scenario of a monitoring device plug-in update method provided in an embodiment of the present application. Figure 1As shown, the implementation scenario includes a user terminal, a monitoring device and a server, wherein the monitoring device may include devices such as an IPC. The user terminal may establish a communication connection with the server, and the monitoring device may establish a connection with the server. The user terminal may select a required new plug-in or delete a plug-in in the monitoring device by accessing the plug-in center provided by the server. For example, the user terminal may select a required new plug-in by accessing the plug-in center of the server, and send an operation instruction for plug-in update to the server. The plug-in update instruction includes identification information of the monitoring device, such as information such as the IP address of the monitoring device, and the monitoring device is a monitoring device for which the user terminal has operation authority.

[0055] The server sends the new plug-in to the monitoring device according to the identification information of the monitoring device in the update instruction, such as the IP address of the monitoring device. After receiving the new plug-in and installing the plug-in, the monitoring device can trigger the recording according to the monitoring video event type included in the new plug-in. In addition, the monitoring device compares the monitoring video event type included in the new plug-in with the identifiable monitoring video event type. If the monitoring video event type included in the new plug-in is not identifiable, a mapping relationship between the monitoring video event type of the new plug-in and the preset empty event type can be established. Based on the mapping relationship, the empty event type is associated with the video clip triggered by the monitoring video event type of the new plug-in. Since the empty event type is a pre-set event type that can be recognized by the monitoring device, it can effectively interact with the firmware, so that when the user end sends a query, download or playback operation instruction through the server, the video clip corresponding to the monitoring video event of the new plug-in can be queried.

[0056] Not limited to Figure 1 The implementation scenario shown may also include a video surveillance terminal with an input device, through which the plug-ins of the video surveillance terminal may be managed, including adding or deleting plug-ins.

[0057] The firmware cannot identify the surveillance video event type, including the surveillance video event type that exceeds the surveillance video event type range defined by the firmware, or the surveillance video event type that does not match the surveillance video event type defined by the firmware.

[0058] Figure 2 The present application provides a monitoring device plug-in update method, such as Figure 2 As shown, the method includes:

[0059] In S201, when it is detected that a new plug-in is installed in the monitoring device, the monitoring video event type included in the new plug-in is obtained.

[0060] The monitoring device in the embodiment of the present application may include an image acquisition terminal such as a network camera (IPC in English). When installing a new plug-in in the monitoring device, the user terminal can first establish a connection with the server, and the user terminal selects the new plug-in to be added or deletes the installed plug-in in the monitoring device by accessing the plug-in center of the server. After receiving the plug-in update instruction from the user terminal, such as receiving the instruction to install a new plug-in, the server sends the new plug-in to the monitoring device via the network. After the monitoring device receives and installs the new plug-in, the monitoring device can detect that the monitoring device has installed the new plug-in.

[0061] Without limitation thereto, when installing a new plug-in, the monitoring device in the embodiment of the present application may also include data of the new plug-in read from a mobile storage device to update the plug-in of the monitoring device.

[0062] The monitoring video event type of the plug-in in the embodiment of the present application includes at least one of the event types such as motion detection event type, sound detection event type, loss detection event type, intrusion detection event type, and specific event trigger detection type. The specific events in the specific event trigger detection type include fireworks events, sleeping on duty events in job inspections, etc.

[0063] The motion detection event type is used to trigger surveillance recording when an object in the monitoring area moves. The sound detection event type is used to trigger surveillance recording when the sound in the monitoring area exceeds the preset decibel value. The loss detection event type is used to trigger surveillance recording when an object in the monitoring area disappears or is blocked. The intrusion detection event type is used to trigger surveillance recording when an unauthorized individual enters the protected area. The specific event trigger detection type is used to trigger surveillance recording when a fireworks event is detected, or when a staff member is detected leaving the post, or when a staff member is detected sleeping at the post.

[0064] In S202, the surveillance video event types included in the new plug-in are compared with the range of surveillance video event types that can be identified by the preset firmware, and unidentifiable surveillance video event types are determined.

[0065] The monitoring device in the embodiment of the present application is pre-installed with firmware that is compatible with a specific monitoring video event type and can identify a specific monitoring video event type. For example, the monitoring video event type compatible with the firmware may include a motion detection event type, a sound detection event type, etc.

[0066] The event types that can be identified by the firmware include, in addition to specific surveillance video event types, also empty event types. The parameters or instructions in the empty event type are compatible with the firmware of the surveillance device, and the empty event type can interact effectively with the firmware, including querying the video clips corresponding to the empty event type.

[0067] In order to effectively manage the event types in the monitoring device, the embodiment of the present application can continuously encode the first number of surveillance video event types included in the firmware of the monitoring device and the second number of empty event types, and determine the coding identification sequence constructed by the coding identification of the surveillance video event type and the empty event type. The coding order of the coding identification of the empty event type can be set after the coding identification of the surveillance video event type, which is convenient for adding the coding identification of the surveillance video event type. When the IPC updates the firmware, the coding identification of the expanded surveillance video event type can be added to support more plug-ins to avoid adding too many new plug-ins and mapping all the coding identifications of the empty event type.

[0068] for example Figure 3 As shown, the number of surveillance video event types included in the firmware of the monitoring device is m+1, and the number of empty event types is n. The surveillance video event types in the plug-in are continuously encoded, and the encoding identifiers are 0 to m respectively, and the empty event types are continuously encoded, and the encoding identifiers are m+1 to m+n respectively after the encoding sequence of the surveillance video event types in the plug-in.

[0069] When the firmware in the monitoring device is updated, the coding identification sequence can be updated according to the identifiable monitoring video events in the updated firmware.

[0070] When the updated firmware adds new identifiable surveillance video event types, these newly added identifiable surveillance video event types can be used to update the coding identification sequence, and the coding identification of the newly added identifiable surveillance video event types is stored between the coding identification of the empty event type before the update and the coding identification of the identifiable surveillance video event type.

[0071] The number of coding identifiers that need to be updated can be determined based on the number of newly added identifiable surveillance video event types included in the updated firmware. After determining the number of newly added identifiable surveillance video event types in the updated firmware, the coding identifier of the empty event type can be increased by a corresponding value based on the number. After updating the coding identifier of the empty event, the newly added identifiable surveillance video event types in the updated firmware are continuously encoded and encoded to the end of the coding identifier of the identifiable surveillance video event types before the update.

[0072] For example, in Figure 3 In the schematic diagram of the coding identification sequence shown in FIG. 1 , if the number of newly identifiable surveillance video event types in the updated firmware is 1, then Figure 4 As shown, firstly, the coding identifiers of the empty event type are all incremented by 1, so that the coding identifier range of the empty event type is updated from m+1 to m+n to m+2 to m+1+n.

[0073] After the coding identifier of the empty event type is updated, the coding identifier of the newly added identifiable surveillance video event type in the updated firmware can be encoded to the end of the first coding identifier subsequence constructed by the identifiable surveillance video event type before the firmware update. The surveillance video event type that constructs the first coding identifier subsequence includes the identifiable surveillance video event type in the firmware before the update.

[0074] The coded identification sequence corresponding to the updated firmware is as follows Figure 4 As shown, the coding identifier of the empty event type can be updated from m+1 to m+n to m+2 to m+1+n. The coding identifiers in the first coding identifier subsequence constructed by the identifiable surveillance video event types before the firmware update are 0 to m, and the end of the first coding identifier subsequence is m. When the newly added identifiable surveillance video event types in the updated firmware are continuously encoded at the end, the newly added identifiable surveillance video event types in the updated firmware are encoded as m+1. After the encoding of the newly added identifiable surveillance video event types is completed, the coding identifiers of the updated first coding identifier subsequence are 0 to m+1.

[0075] After the coding identifier of the identifiable surveillance video event type is updated, the coding identifier of the first empty event type can be updated accordingly. Since the coding identifier of the empty event type is a continuous code, when establishing a mapping relationship between the empty event type and the unidentifiable surveillance video event type, the empty event type that can be mapped can be efficiently found based on the continuous coding identifier.

[0076] In the embodiment of the present application, the surveillance video event type that can be recognized by the firmware can be pre-set in the monitoring device. After the new plug-in is installed, the surveillance video event type included in the new plug-in can be compared with the identifiable surveillance video event type to determine whether it belongs to the range of identifiable surveillance video event types. If so, the video clip triggered by the surveillance video event type can be directly associated with the surveillance video event type and stored.

[0077] If the surveillance video event type included in the new plug-in does not match the range of surveillance video event types that can be recognized by the preset firmware, that is, no surveillance video event type matching the surveillance video event type in the new plug-in can be found within the preset range of surveillance video event types (multiple surveillance video event types), then it means that the surveillance video event type in the new plug-in is an unrecognizable surveillance video event type.

[0078] In S203, a mapping relationship between the unrecognizable surveillance video event type and a preset empty event type is established, and the video clip corresponding to the new plug-in is operated according to the mapping relationship.

[0079] For surveillance video event types that cannot be recognized in the new plug-in, a target empty event type that can be used to establish a mapping relationship (i.e., not occupied by a mapping relationship) can be searched in the second coding identification subsequence constructed by the empty event type, and a correspondence between the surveillance video event type in the new plug-in and the target empty event type can be established.

[0080] like Figure 5 In the mapping diagram of surveillance video event type and empty event type shown, after the new plug-in is installed in the monitoring device, the surveillance video event type in the new plug-in can be compared with the surveillance video event type that can be identified in the firmware to determine whether there is an unidentifiable surveillance video event type. If the surveillance video event type in the new plug-in matches the surveillance video event type that can be identified in the firmware, it means that the surveillance video event type in the plug-in is an identifiable surveillance video event type, and the surveillance video event type can be directly used to operate the corresponding video clip.

[0081] If there is no match, that is, there is an unrecognizable surveillance video event type in the new plug-in, then the unrecognizable surveillance video event type needs to be mapped to an empty event type, and you can traverse from the beginning in the second encoding identifier subsequence to find an empty event type that has not been mapped. Figure 5 As shown in the upper part, the empty event types m+1 and m+2 have been mapped with the new plug-in surveillance video event types h (h>m, indicating that the surveillance video event type h is not within the surveillance event type range 0-m that can be recognized by the firmware) and i (i>m, indicating that the surveillance video event type i is not within the surveillance event type range 0-m that can be recognized by the firmware). The empty event type m+k has not been mapped. In this case, the new plug-in can include the unrecognizable surveillance video event type j. (j >m ) Mapping with the empty event type m+k yields Figure 5 The second coding identification subsequence shown in the lower part, in which the new plug-in includes an unrecognizable surveillance video event type j and a null event type m+k, in which a mapping relationship has been successfully established.

[0082] For the video clips triggered by the unrecognizable surveillance video event type in the new plug-in, the video clips can be stored in association with the empty event type according to the established mapping relationship. According to the relationship of the associated storage, when querying the video clips related to the new plug-in, the empty event type mapped to the surveillance video event type of the new plug-in can be first searched according to the mapping relationship. Since the empty event type is an event type recognizable by the firmware, the related video clips can be queried through the empty event type, thereby obtaining the video clips corresponding to the surveillance video event type in the new plug-in.

[0083] for example Figure 6The figure shows a flow chart of the interaction between a user terminal and a monitoring device provided by an embodiment of the present application. The details are as follows:

[0084] In S601, the user terminal sends an operation request for a video clip of a surveillance video event type j of a new plug-in to the surveillance device.

[0085] The new plug-in may include one or more surveillance video event types. Surveillance video event type j is a surveillance video event type that cannot be identified by the firmware. The operation request may be a query request, a download request, or a playback request.

[0086] Among them, after establishing a mapping relationship between the empty event type and the unrecognizable surveillance video event type of the new plug-in, the embodiment of the present application can store the video clips determined by the unrecognizable surveillance video event type in association with the mapped target empty event type according to the mapping relationship.

[0087] In S602, the monitoring device searches for an empty event represented by the empty event type m+k according to a preset mapping relationship.

[0088] When the monitoring device detects that a new plug-in has been installed, it establishes a mapping relationship between the monitoring video event type and the empty event type for the unrecognizable monitoring video event type included in the new plug-in, and associates and stores the video clips triggered by the monitoring video event type with the mapped empty event type. Based on the established mapping relationship, the monitoring video event type j and the mapped empty event type m+k can be quickly found.

[0089] In S603, it is detected whether the operation request is a query request.

[0090] The operation request may be any one of a query request, a download request or a playback request. If the operation request is a query request, the query request includes the start and end time range of the query, that is, the time range determined by the start time and the end time.

[0091] If the operation request is a download request or a playback request, the download request or the playback request includes the start time of the video clip that needs to be downloaded or played back, that is, from the start time backward, the requested video clip is searched in the video clips stored in association with the target empty event type, and the searched video clips are downloaded or played back in sequence.

[0092] In S604, if the operation request is a query request, the video segment corresponding to the empty event type m+k is searched according to the start and end time range, and the search result of the video segment is sent to the user end.

[0093] If the operation request is a query request, then the video clips that meet the time range can be searched in the video clips associated with the empty event type m+k mapped to the surveillance video event type j in the new plug-in according to the start and end time range included in the query request, and the query results, including the number of video clips, the length of the video clips or the summary information of the video clips, etc., are sent to the user end.

[0094] In S606, if the operation request is a download request or a playback request, the video segment corresponding to the empty event type m+k is searched according to the start time, and the searched video segment is sent to the user terminal for downloading or playback.

[0095] If the operation request is a download request or a playback request, the video clip after the start time can be determined in the video clip associated with the empty event type m+k mapped to the surveillance video event type j in the new plug-in according to the start time included in the download request or the playback request. The searched video clip is read and parsed so that it can be sent to the user end, and the user end downloads or plays back the searched video clip.

[0096] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0097] Figure 7 A schematic diagram of a plug-in updating device for a monitoring device provided in an embodiment of the present application, the device comprising:

[0098] The surveillance video event type acquisition unit 701 is used to acquire the surveillance video event type included in the new plug-in when it is detected that a new plug-in is installed in the surveillance device;

[0099] A comparison unit 702, configured to compare the surveillance video event type included in the new plug-in with a preset range of surveillance video event types identifiable by the firmware, and determine unidentifiable surveillance video event types;

[0100] The mapping relationship establishing unit 703 is used to establish a mapping relationship between the unrecognizable surveillance video event type and a preset empty event type, and operate the video clip corresponding to the new plug-in according to the mapping relationship.

[0101] Figure 7 The plug-in updating device of the monitoring device shown in the figure is Figure 2 The plug-in update method of the monitoring device shown corresponds to this.

[0102] Figure 8 Schematic diagram of a monitoring device provided in an embodiment of the present application. Figure 8As shown, the monitoring device 8 of this embodiment includes: a processor 80, a memory 81, and a computer program 82 stored in the memory 81 and executable on the processor 80, such as a plug-in update program for the monitoring device. When the processor 80 executes the computer program 82, the steps of the above-mentioned plug-in update method embodiments of each monitoring device are implemented. Alternatively, when the processor 80 executes the computer program 82, the functions of each module / unit in the above-mentioned device embodiments are implemented.

[0103] Exemplarily, the computer program 82 may be divided into one or more modules / units, which are stored in the memory 81 and executed by the processor 80 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 82 in the monitoring device 8.

[0104] The monitoring device 8 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The monitoring device may include, but is not limited to, a processor 80 and a memory 81. Those skilled in the art will appreciate that Figure 8 It is only an example of a monitoring device 8 and does not constitute a limitation of the monitoring device 8. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the monitoring device may also include input and output devices, network access devices, buses, etc.

[0105] The processor 80 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0106] The memory 81 may be an internal storage unit of the monitoring device 8, such as a hard disk or memory of the monitoring device 8. The memory 81 may also be an external storage device of the monitoring device 8, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the monitoring device 8. Further, the memory 81 may also include both an internal storage unit and an external storage device of the monitoring device 8. The memory 81 is used to store the computer program and other programs and data required by the monitoring device. The memory 81 may also be used to temporarily store data that has been output or is to be output.

[0107] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0108] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0109] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0110] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0111] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0112] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0113] If the integrated module / 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, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by hardware related to computer program instructions. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0114] In addition, an embodiment of the present application also provides a computer program product, which, when executed on a computer, enables the computer to execute the methods in the above-mentioned implementation modes.

[0115] The embodiments described above 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 aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions 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 method for updating a plug-in of a monitoring device, characterized in that: The method comprises: When a new plug-in is detected to be installed on the monitoring device, obtaining the type of monitoring video event included in the new plug-in; Compare the surveillance video event types included in the new plug-in with the range of surveillance video event types that can be recognized by the preset firmware to determine unrecognizable surveillance video event types; A mapping relationship between the unrecognizable surveillance video event type and a preset empty event type is established, and the video clip corresponding to the new plug-in is operated according to the mapping relationship.

2. The method according to claim 1, characterized in that After obtaining the surveillance video event type included in the new plug-in, the method further includes: Comparing the surveillance video event type included in the new plug-in with a preset range of identifiable surveillance video event types to determine the identifiable surveillance video event type; The identifiable surveillance video event type and the video clip are associated and stored, and the video clip is recorded when the surveillance video event represented by the identifiable surveillance video event type is triggered.

3. The method according to claim 1, characterized in that: Operating the video clip corresponding to the new plug-in according to the mapping relationship includes: In the case where a surveillance video event represented by an unrecognizable surveillance video event type included in the new plug-in is triggered to record, searching for an empty event type corresponding to the unrecognizable surveillance video event type according to the mapping relationship; The video clip is associated with the empty event type and stored, and the video clip is recorded when a surveillance video event represented by an unrecognizable surveillance video event type included in the new plug-in is triggered.

4. The method according to claim 3, characterized in that: After associating and storing the video clip determined when the surveillance video event is triggered with the empty event type, the method further includes: Obtaining an operation request for a video clip of the new plug-in; Determine a target empty event type corresponding to the unrecognizable surveillance video event type according to a correspondence between the unrecognizable surveillance video event type and the empty event type; A corresponding video clip is determined according to the target empty event type.

5. The method according to claim 4, characterized in that The operation request is a query request, and the query request includes the start and end time of the video clip requested for query; Determining a corresponding video clip according to the target empty event type includes: According to the start and end times included in the query request, a first target video segment is searched in the video segments corresponding to the target empty event type.

6. The method according to claim 4, characterized in that The operation request is a playback request or a download request, and the playback request or the download request includes a start time of the playback or the download; Determining a corresponding video clip according to the target empty event type includes: According to the start time included in the playback request or the download request, a second target video segment for playback or downloading is determined in the video segment corresponding to the target empty event type.

7. The method according to any one of claims 1 to 6, characterized in that: Before comparing the surveillance video event type included in the new plug-in with the range of surveillance video event types that can be identified by the preset firmware, the method further includes: Determine a first number of surveillance video event types included in the plug-in in the surveillance device, and determine a second number of empty event types of the surveillance device, and determine a coding identification sequence of the surveillance video event types and the empty event types according to the first number and the second number, wherein the coding identification in the coding identification sequence is a continuous coding identification, and the coding order of the coding identification of the empty event type is after the coding identification of the surveillance video event type; After comparing the surveillance video event types included in the new plug-in with the range of surveillance video event types that can be identified by the preset firmware and determining unidentifiable surveillance video event types, the method includes: Searching the list of empty event types for which no mapping relationship is established according to the coding identifier; A mapping relationship is established between the empty event type for which no mapping relationship is established and the unrecognizable surveillance video event.

8. A plug-in updating device for monitoring equipment, characterized in that: The device comprises: A monitoring video event type acquisition unit, used to acquire the monitoring video event type included in the new plug-in when detecting that a new plug-in is installed in the monitoring device; A comparison unit, configured to compare the surveillance video event type included in the new plug-in with a preset range of surveillance video event types identifiable by the firmware, and determine unidentifiable surveillance video event types; The mapping relationship establishing unit is used to establish a mapping relationship between the unrecognizable surveillance video event type and a preset empty event type, and operate the video clip corresponding to the new plug-in according to the mapping relationship.

9. A monitoring 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 monitoring device implements the method according to any one of claims 1 to 7.

10. A computer program product comprising computer program instructions, characterized in that When the computer program is executed, the method according to any one of claims 1 to 7 is performed.

Images