A data processing method, data retrieval method and electronic device for events

Abstract

The embodiment of the present application provides a data processing method, a data retrieval method and an electronic device for an event, which are applied in the field of data processing technology. The specific implementation scheme is: whenever the starting condition of any event link of the target event is met, the target configuration information of the event link is obtained; the device indicated by the device indication information recorded in the target configuration information is determined; the device corresponding to the event link is controlled to execute the target function service; the collected data obtained by the device corresponding to the event link in the process of executing the target function service is obtained; the identification information of the target object corresponding to the target collected data is determined; the inline information containing at least the identification information of the target object and the link identification of the event link is constructed, and the inline information is bound and stored with the collected data of the event link. It can be seen that this scheme provides an implementation basis for operations such as retrieval of collected data corresponding to each link of the same target event.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data processing method, a data retrieval method and an electronic device for an event. Background Art

[0002] Video surveillance is widely used in various scenarios to monitor events, such as monitoring process events of factory production. A complete event can include various event links (also called various processes) executed for the same task object, and each event link can be equipped with corresponding equipment to collect data for objects appearing in the event link. In the prior art, the equipment corresponding to each event link can monitor the same event link of multiple events of the same event type, but it is impossible to distinguish different event links of each event, that is, it is impossible to distinguish different event links of each object.

[0003] Exemplarily, the event type may be an event type corresponding to a steel pipe production process. The event corresponding to this event type may include link 1, link 2, and link 3. The devices corresponding to link 1, link 2, and link 3 may respectively collect data for link 1, link 2, and link 3 of multiple events, but cannot distinguish the collected data of link 1, link 2, and link 3 belonging to the same event, that is, cannot distinguish which collected data are the collected data of link 1, link 2, and link 3 of the same object.

[0004] Therefore, when analyzing a target event, the user needs to manually collect data from various devices and retrieve the collected data corresponding to each link of the target event for analysis. Therefore, there is an urgent need for a data processing method for events, so as to provide a basis for the retrieval of collected data of each event link of the same object. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a data processing method, a data retrieval method and an electronic device for an event. The specific technical solution is as follows:

[0006] In a first aspect, the present application provides a data processing method for an event, which is applied to a video recording device; the method comprises:

[0007] Whenever the starting condition of any event link of the target event is met, the configuration information of the event link is obtained from the event configuration information pre-customized for the target event as the target configuration information; wherein the target event includes multiple event links, and the event configuration information includes the configuration information of each of the multiple event links; the configuration information of the event link records the device indication information and target function service corresponding to the event link, the device indication information is used to indicate the device for data collection for any object appearing in the event link, and the target function service is the target function service required to be enabled for the device indicated by the device indication information during the execution of the event link;

[0008] Determine the device indicated by the device indication information recorded in the target configuration information as the device corresponding to the event link;

[0009] When the device corresponding to the event link currently has the target function service enabled, control the device corresponding to the event link to execute the target function service, and when the end condition of the event link is met, control the device corresponding to the event link to end the execution of the target function service under the event link;

[0010] Acquire the collected data obtained by the device corresponding to the event link in the process of executing the target function service as the collected data of the event link;

[0011] Determine identification information of an object that appears in the event link during the execution of the target function service;

[0012] In response to the data storage conditions for the event link, the global object information corresponding to the object appearing in the event link is determined, and combined information containing at least the global object information and the link identifier of the event link is constructed as inline information, and the inline information is bound and stored with the collected data of the event link; wherein the global object information is the identification information of the task object to which the object appearing in the event link belongs, which is determined based on the identification information of the object appearing in the event link, and any task object is an object indicated for processing by the event task represented by the target event.

[0013] In a second aspect, the present application provides a data retrieval method for an event, which is applied to an aggregation service device; the method comprises:

[0014] Receiving a search keyword for a target event input by a user in a search interface of the aggregation service device; wherein the search keyword includes identification information of any task object; any task object is an object indicated for processing by an event task represented by the target event;

[0015] Sending a search instruction carrying the search keyword to a video recording device, so that the video recording device, in response to receiving the search instruction, screens each inline information matching the search keyword carried in the search instruction and the collected data stored and bound with each screened inline information based on the inline information and collected data of the event link of the target event that are currently bound and stored, and feeds back each screened inline information and the bound collected data to the aggregation service device; wherein the video recording device binds and stores the inline information and collected data of the event link of the target event according to the above-mentioned data processing method for events;

[0016] Receive each inline information fed back by the video recording device and the bound collected data;

[0017] The aggregate information corresponding to the search keyword and including each inline information fed back by the video recording device and the bound collected data is output in the form of a workflow of the target event.

[0018] In a third aspect, the present application provides a data retrieval method for an event, which is applied to a video recording device, and the method comprises:

[0019] Receive a search instruction carrying a search keyword; wherein the search instruction is a search keyword for a target event input by a user in a user interface of an aggregation service device; wherein the search keyword includes identification information of any task object; any task object is an object indicated for processing by an event task represented by the target event; based on the inline information and collected data of the event link of the target event that are currently bound and stored, filter each inline information that matches the search keyword carried in the search instruction and the collected data bound and stored with each filtered inline information; wherein the recording device binds and stores the inline information of the event link of the target event with the collected data according to the above-mentioned data processing method for the event;

[0020] Feedback the screened inline information and bound collected data to the aggregation service device, so that the aggregation service device outputs the aggregated information corresponding to the search keyword and including the inline information and bound collected data fed back by the video recording device.

[0021] In a fourth aspect, the present application provides an electronic device, including:

[0022] Memory, used to store computer programs;

[0023] The processor is used to implement any of the above-mentioned data processing methods and / or data retrieval methods when executing the program stored in the memory.

[0024] Beneficial effects of the embodiments of the present application:

[0025] The scheme of the embodiment of the present application can bind and store the collected data of any event link with the inline information, wherein the collected data is the data obtained by the device corresponding to the event link in the process of executing the target function service, and the inline information at least includes the identification information of the target object and the link identification of the event link. In this way, the collected data of the same object in different event links can be aggregated through the inline information, thereby providing a basis for the retrieval of the collected data corresponding to each link of the target event and other operations.

[0026] Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, 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, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0028] Figure 1 A flowchart of a data processing method for an event provided in an embodiment of the present application;

[0029] Figure 2 A schematic diagram of adding additional information provided in an embodiment of the present application;

[0030] Figure 3 A schematic diagram of a system structure of an examination event provided in an embodiment of the present application;

[0031] Figure 4A A schematic diagram of an event configuration provided in an embodiment of the present application;

[0032] Figure 4B Another event configuration diagram provided in an embodiment of the present application;

[0033] Figure 4C A schematic diagram of another event configuration provided in an embodiment of the present application;

[0034] Figure 5 A schematic diagram of a scene of a glass production event link provided in an embodiment of the present application;

[0035] Figure 6 A system schematic diagram of a factory event provided by an embodiment of the present application;

[0036] Figure 7A system schematic diagram of an examination event provided in an embodiment of the present application;

[0037] Figure 8 A schematic diagram of a display interface for standard deviation clustering outlier analysis provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0039] In the technical solution of this application, the operations of obtaining, storing, using, processing, transmitting, providing and disclosing the event-related information involved are all carried out with authorization.

[0040] The following first introduces a data processing method for events provided in an embodiment of the present application. The data processing method provided in this embodiment can be applied to a video recording device; the video recording device can specifically be an NVR (Network Video Recorder) and a DVR (Digital Video Recorder). This application does not limit the video recording device.

[0041] Among them, a data processing method for an event provided in an embodiment of the present application may include:

[0042] Whenever the starting condition of any event link of the target event is met, the configuration information of the event link is obtained from the event configuration information pre-customized for the target event as the target configuration information; wherein the target event includes multiple event links, and the event configuration information includes the configuration information of each of the multiple event links; the configuration information of the event link records the device indication information and target function service corresponding to the event link, the device indication information is used to indicate the device for data collection for any object appearing in the event link, and the target function service is the target function service that needs to be enabled for the device indicated by the device indication information during the execution of the event link.

[0043] Determine the device indicated by the device indication information recorded in the target configuration information as the device corresponding to the event link;

[0044] When the device corresponding to the event link currently has the target function service enabled, control the device corresponding to the event link to execute the target function service, and when the end condition of the event link is met, control the device corresponding to the event link to end the execution of the target function service under the event link;

[0045] Acquire the collected data obtained by the device corresponding to the event link in the process of executing the target function service as the collected data of the event link;

[0046] Determine identification information of an object that appears in the event link during the execution of the target function service;

[0047] In response to the data storage conditions for the event link, the global object information corresponding to the object appearing in the event link is determined, and combined information containing at least the global object information and the link identifier of the event link is constructed as inline information, and the inline information is bound and stored with the collected data of the event link; wherein the global object information is the identification information of the task object to which the object appearing in the event link belongs, which is determined based on the identification information of the object appearing in the event link, and any task object is an object indicated for processing by the event task represented by the target event.

[0048] The scheme of the embodiment of the present application can bind and store the collected data of any event link with the inline information, wherein the collected data is the data obtained by the device corresponding to the event link in the process of executing the target function service, and the inline information at least includes the identification information of the target object and the link identification of the event link. In this way, the collected data corresponding to each link of the same target event can be aggregated through the inline information, thereby providing a basis for the retrieval of the collected data corresponding to each link of the same target event.

[0049] A data processing method for events provided in an embodiment of the present application is introduced below in conjunction with the accompanying drawings.

[0050] like Figure 1 As shown, the data processing method for events provided in the embodiment of the present application may include the following steps:

[0051] S101, whenever the starting condition of any event link of the target event is met, the configuration information of the event link is obtained from the event configuration information pre-customized for the target event as the target configuration information; wherein the target event includes multiple event links, and the event configuration information includes the configuration information of each of the multiple event links; the configuration information of the event link records the device indication information and target function service corresponding to the event link, the device indication information is used to indicate the device for data collection for any object appearing under the event link, and the target function service is the target function service that needs to be enabled for the device indicated by the device indication information during the execution of the event link.

[0052] The target event in this application is composed of multiple event links (also referred to as multiple processes, multiple process links, and multiple sub-events). Moreover, each event link in the target event in this application can be used to perform a task on an object, and different event links are used to perform different tasks on an object. Therefore, the target event in this application is different from motion detection events, object recognition events, and other events used to perform a single task on an object. According to the domain dimension, the type of target event can be a factory event type, or an exam event type, etc.; for a factory event type, the target event can be a production event of a product or commodity such as a steel pipe production event or a glass production event; and for an exam event type, the target event can be a sports exam event, etc.

[0053] The execution logic of each event link of different types of target events may be different, and the execution logic of each event link may be in chronological order or in horizontal order. The chronological order means that there is a temporal sequence between each event link of the target event. For example, for the glass production event, after the glass production link, the glass transportation link is executed, and after the glass transportation link, the glass packaging link is executed. The horizontal order means that although each event link of the target event belongs to the same target event, there may be no necessary chronological order between the event links. For example, in the production event of a water cup, the production link of the water cup body and the production link of the cup lid are both part of the resolution of the same event, but there is no necessary time relationship, and these two event links can be carried out independently. It should be noted that the temporal sequence between the various event links of the above-mentioned target event can mean that: all event links of the target event have a temporal sequence, such as the various event links of the above-mentioned glass production event have a temporal sequence, or, the examination events belonging to the chemical experiment test have sequence requirements for various operation links (each operation link can be called an event link); of course, it can also mean that some event links in the target event have a temporal sequence, while other event links may not have a temporal sequence. For example, for examination events such as physical education examinations, test items such as skipping rope, 50m, and sit-ups (each test item can be regarded as an event link) can be out of order, but face scanning and ID card swiping at the beginning of the examination have a sequence (face scanning can be regarded as an event link, and ID card swiping can also be regarded as an event link).

[0054] The various processes of producing goods, that is, the various event links, can exemplarily include: process A1, process A2, process A3...process An, which are in chronological order, that is, vertical; the various links of the examination events belonging to the examination items are horizontal, which means that the various links of the examination events do not necessarily have to be in chronological order.

[0055] In the present application, the event configuration information can be obtained based on the event template configuration provided to the user. By configuring the event template, it is possible to add, delete, and modify the event itself, add, delete, and modify each link of the event, and add, delete, and modify the configuration information of the event links.

[0056] In the present application, the device indication information can be obtained based on the event template configuration provided to the user. Specifically, the device indication information can be information such as the identification of the device corresponding to the event link; if the device is bound to a transmission channel in the recording device, the device indication information can also be the channel identification of the transmission channel bound to the device.

[0057] It is understandable that in the present application, the device can be a collection device, and any device capable of data collection can be used as the device of the present application. For example, a camera for collecting images, a card reader for collecting work badge information, a temperature sensor for collecting temperature, and so on. The present application does not limit this device. For any event link, considering that data collection is required and the method of data collection may be different during the execution of the event link, therefore, the device and the required functional services can be allocated to the event link; and considering that when the device is associated with the video recording device, that is, when data is transmitted to the video recording device, the device can be associated with the video recording device through the transmission channel for association. The device can be the video recording device itself, and the video recording device can obtain the collected data of other devices. The target functional service that the video recording device needs to enable can be the function of obtaining collected data from other devices.

[0058] In this application, the device is used to provide data collection services, and the device can be bound to one or more channels of the video recording device. Of course, the device can also communicate directly with the video recording device without binding a channel, and the device's service can be used as an independent process in the event link. Later, when displaying and searching in real time, the service status of the service provided by the device can be obtained for display.

[0059] In addition, in the present application, the target event may have multiple event links, and each event link corresponds to a starting condition of the event link.

[0060] During the execution of each event link recorded in the configuration information of the event link, there may be multiple device indication information and target function services corresponding to the event link that need to be utilized.

[0061] In one implementation, the starting condition of the event link includes a first external trigger condition, or a first internal trigger condition; wherein the first external trigger condition is receiving a trigger instruction for starting the event link sent by a predetermined control terminal, and the first internal trigger condition is detecting predetermined trigger information sent by a designated device connected to the recording device;

[0062] The termination conditions of the event link include: wherein, the second external trigger condition is receiving a trigger instruction for the end of the event link sent by a predetermined control terminal, and the second internal trigger condition is detecting that the process for the target function service meets the predetermined termination condition.

[0063] As long as any one of the first external trigger condition and the first internal trigger condition of the event link is met, the event link can be started. The second external trigger condition and the second internal trigger condition of the event link are the same.

[0064] It is understandable that when the starting condition is the first internal trigger condition, the first internal trigger condition of different event links of the target event may be different. Specifically, the predetermined trigger information set for each different link may be different. Of course, the predetermined trigger information set for each different link may be the same, but different event links are provided with different designated devices to send the predetermined trigger information to the video recording device through the channel, so that it can also be distinguished which event link is specifically triggered. Exemplarily, for the glass placement link and the glass packaging link in the glass production event, the predetermined trigger information is the coding information corresponding to the glass collected by the barcode scanning gun, but the glass placement link is collected by barcode scanning gun 1, and the glass packaging link is collected by barcode scanning gun 2. Therefore, when the video recording device receives the coding information sent by barcode scanning gun 1, it triggers the start of the glass placement link.

[0065] The predetermined control terminal can be an information transmission device such as a remote control and a mobile phone. The predetermined control terminal can send a trigger instruction for opening a certain event link to the recording device to trigger the opening of the link. Usually, the first external trigger condition can be sent by the predetermined control terminal under human control. Of course, the first external trigger condition can provide a guarantee for the execution of the target event. For example, if the processing logic for the first internal trigger condition built into the recording device fails, or the specified device is damaged and cannot work, resulting in the inability to trigger the execution of the event link, the first external trigger condition can be used to trigger the execution of the event link. Of course, the first external trigger condition can also be set according to the actual needs of the user. For example, if the user wants to use the PLC (Programmable Logic Controller) system to control the start and stop of the event link, the PLC system can send a control instruction to the NVR, and the recording device receives the control instruction representing the opening, which is the first external trigger condition.

[0066] The second external trigger condition and the second internal trigger condition are the same as the first external trigger condition and the first internal trigger condition mentioned above. The only difference is that the first external trigger condition is used to trigger the start of the event link, and the second external trigger condition is used to trigger the end of the event link; the second internal trigger condition corresponds to the second internal trigger condition mentioned above. The only difference is that the second internal trigger condition is used to trigger the start of the event link, and the second internal trigger condition is used to trigger the end of the event link, and no further details will be given here.

[0067] Internal trigger conditions, for example, such as work badge recognition, barcode scanner recognition, alarm input, high-level trigger, etc., can be triggered when the NVR itself meets certain conditions. External trigger conditions, for example, user-defined trigger conditions are injected from the outside, and fixed-format messages are sent to the NVR as trigger conditions. The NVR can receive and parse them. For example, when the NVR is connected to the platform, the platform sends a message to the NVR, and the NVR records it as the start time after parsing it.

[0068] Moreover, when any event link of the target event is executed in sequence, the first internal trigger condition may be related to the termination condition of the previous event link of any link. Usually, the first internal trigger condition is for the event link other than the first link of the target event, and the first internal trigger condition of the event link may include: a predetermined time length away from the reference time point corresponding to the event link. The reference time point corresponding to the event link may be the time point when the previous event link is started, or the time point when the previous event link is ended. For example, event link 1 and event link 2 are executed sequentially, and it is pre-set that event link 2 is started 20S after event link 1 ends. Then the first internal trigger condition of event link 2 is that event link 1 meets the termination condition of event link 1 20S later.

[0069] In another implementation, when the event link is the first link of the target event, the starting condition of the event link includes a first external trigger condition, or a first internal trigger condition;

[0070] In the case where the event link is a link other than the first link of the target event, the starting condition of the event link includes: a predetermined time distance from a reference time point corresponding to the event link; wherein the reference time point corresponding to the event link is: a time point when the previous event link corresponding to the event link is detected to meet the starting condition;

[0071] The termination conditions of the event link include: a second external trigger condition, or a second internal trigger condition;

[0072] Among them, the second external trigger condition is receiving a trigger instruction for the end of the event link sent by a predetermined control terminal, and the second internal trigger condition is detecting that the process for the target function service meets the predetermined end condition.

[0073] In this implementation, the first external trigger condition is receiving a trigger instruction for starting the first link of a target event sent by a predetermined control terminal, and the first internal trigger condition is detecting that the process for serving the target function meets a predetermined start condition.

[0074] The predetermined time interval between the reference time point corresponding to the event link can be the execution standard time corresponding to the previous event link corresponding to the event link. The execution standard time corresponding to the event link can be the standard time from the start to the end of the event link determined based on a pre-statistical analysis.

[0075] The application scenario of this implementation method may be a scenario where each event link of the target event is executed in sequence. Thus, each link can be executed in sequence and efficiently according to the solution of this implementation method.

[0076] In the present application, the pre-defined event configuration information may be stored in the recording device, or may be stored in other devices. The recording device may communicate with other devices to obtain the time configuration information stored in other devices.

[0077] In the present application, a recording device may have multiple transmission channels, and a recording device may serve multiple different types of target events; therefore, for different target events, a transmission channel belonging to the target event may be allocated to each target event, and further, the transmission channel belonging to the target event may be divided into transmission channels belonging to different links of the target event. Furthermore, it can be understood that the transmission channel is a transmission channel provided to each device, and therefore, each transmission channel belonging to the target event has a corresponding relationship with the device belonging to the target event.

[0078] S102: Determine the device indicated by the device indication information recorded in the target configuration information as the device corresponding to the event link.

[0079] In this application, with respect to the execution process of an event link, the equipment required in the event link is predefined.

[0080] Optionally, in response to the fact that the target function service recorded in the target configuration information is not included in the function services currently enabled on the device corresponding to the event link, the target function service is enabled for the device corresponding to the event link.

[0081] In the present application, for the execution process of the event link, the functional services that the device indicated by the device indication information needs to execute in the event link are pre-specified. If it is detected that there are unstarted functional services among the functional services that the device indicated by the device indication information needs to execute, the unstarted functional services can be started. It can be understood that the functional services corresponding to different devices can be different. For any device, if the functional service corresponding to the device is not started, the device can be triggered to start the corresponding functional service.

[0082] S103, when the device corresponding to the event link has currently enabled the target function service, control the device corresponding to the event link to execute the target function service, and when the end condition of the event link is met, control the device corresponding to the event link to end the execution of the target function service under the event link.

[0083] In this application, the target function service is affected by the target event, event link and equipment, and the target function service can be determined according to the specific application scenario. For example, for link 1 of the steel pipe production event, the device can be a camera, and the camera can always perform a video recording service for the target point. When link 1 is executed, a steel pipe may appear at the target point. Therefore, during the execution of link 1, the camera can also perform a function service for analyzing the OCR (Optical Character Recognition) information corresponding to the steel pipe in the image at a preset analysis frame rate such as 3 frames per second for the recorded video. Different devices can correspond to different target function services, and this application does not limit the target function service.

[0084] It is understandable that any device of the present application can execute multiple functional services, and some functional services only need to be executed during the event link, and these functional services are the above-mentioned target functional services. Therefore, the target functional service can be turned on when the starting conditions of the event link are met, and turned off when the start and end conditions of the event link are met.

[0085] S104, acquiring the collected data obtained by the device corresponding to the event link in the process of executing the target function service as the collected data of the event link;

[0086] The collected data obtained by each device during the execution of the target function service can be sent to the recording device in real time, or the collected data obtained during the execution of the target function service can be stored first and then sent to the recording device after the event link is completed. The device bound to the channel of the recording device can send the collected data to the recording device through the bound channel.

[0087] It is understandable that the target function service is only executed during the execution of the event link. Therefore, the collected data obtained by the device during the execution of the target function service in any event link has a unique corresponding relationship with the event link. And the collected data can be actively collected by the NVR or passively injected from the outside. For example, there may be other systems such as PLC inside the factory. The PLC can send a message to the NVR to inform it whether it is the first step, the second step, etc. These data can also be used as the collected data of the event link.

[0088] S105, determining identification information of an object appearing in the event link during the execution of the target function service;

[0089] In each event link in the target event, there is an object of the event link. The target objects of each event link in a target event can be the same. For example, in the glass production event, the target object of each event link is glass. The target objects of each event link in a target event can also be different, but in the same target event, different target objects have a corresponding relationship. For example, in an examination event, the target object in link 1 can be the examinee, and the target object in link 2 can be the ID card, but the examinee in link 1 corresponds to the ID card in link 2.

[0090] The identification information of the object appearing in the event link may be obtained by the function service for collecting the identification information of the object included in the target function service, or may be obtained by external transmission to the recording device. It can be understood that if the identification information of the object is only obtained by the function service for collecting the identification information of the object included in the target function service, the target function service at least includes the function service for collecting the identification information of the target object. S106, in response to the data storage condition for the event link, determine the global object information corresponding to the object appearing in the event link, construct combined information at least including the global object information and the link identification of the event link as inline information, and bind the inline information with the collected data of the event link for storage; wherein the global object information is the identification information of the task object to which the object appearing in the event link belongs, determined based on the identification information of the object appearing in the event link, and any task object is the object indicated to be processed by the event task represented by the target event. The data storage condition of the event link may be determined by the task type of the target event to which the event link belongs. Different task types have different ways of determining the global object information corresponding to the object appearing in the event link.

[0091] For example, the event task represented by the target event is a task for analyzing and processing an existing task object. Accordingly, determining the global object information corresponding to the object appearing in the event link includes: determining the identification information of the object appearing in the event link as the global object information;

[0092] Alternatively, the event task represented by the target event is an assembly generation task for a task object. Accordingly, determining the global object information corresponding to the object appearing in the event link includes: determining the identification information of the object appearing in the event link according to the mapping relationship between the identification information of the task object and the identification information of the object appearing in each event link, and obtaining the global object information corresponding to the object appearing in the event link;

[0093] Among them, the mapping relationship is determined based on the collected data in the specified link; in the mapping relationship, the identification information of any task object corresponds to the identification information of the object appearing in each event link: the identification information of the object appearing in each event link used when assembling and generating the task object, and the specified link is the task object assembly link in the multiple event links of the target event.

[0094] The task of analyzing and processing an existing task object may be, for example, a glass production task. During the entire glass production task, the objects of the various event links are the produced glass.

[0095] The assembly generation task for a task object may refer to a task that requires the assembly of parts produced in multiple event links. For example, it may be a car production task, etc. It is understandable that the production of some task objects involves the assembly of different parts, and the production of each part can be used as a link of the event. Therefore, the object identifiers in each event link of the event may be different, but the task object targeted by the entire target event is the object that needs to be assembled. For example, in a car production event, the production of parts such as tires and doors belongs to the event link of the target event. In the tire production link, the object identifier is the tire identifier, and in the door production link, the object identifier is the door identifier. The car produced in the assembly link is assembled from parts such as tires and doors. The produced car is the task object of the event task of the target event, and the car identifier is the global object information.

[0096] The present application can determine the mapping relationship between the identification information of the task object and the identification information of the objects appearing in each event link in the task object assembly link in the multiple event links of the target event. Specifically, a mapping relationship can be established between the identification of the task object and the identification of each object constituting the character object.

[0097] Thus, according to the mapping relationship between the identification information of the task object and the identification information of the object appearing in each event link, the identification information of the object appearing in the event link is determined, and the global object information corresponding to the object appearing in the event link is obtained. Specifically, for each event link, the identification information of the object appearing in the event link is determined, and the identification information of the task object with a mapping relationship is used as the global object information corresponding to the object appearing in the event link. For example, if tire A is used to assemble car B, there is a mapping relationship between the identification of tire A and the identification of car B, and the global object information corresponding to the object appearing in the event link of tire A production is the identification of car B.

[0098] The link identifier of the event link is an identifier determined based on the event link as a dimension. For example, in an automobile production event, the identifier of the tire production link may be: identifier 1. It is understandable that in each target event of the same type, the link identifiers of the same type of event links may be the same. For example, in multiple automobile production events, the identifiers of multiple tire production links may all be: identifier 1.

[0099] There are many ways to bind and store the inline information with the collected data of the event link. For different scenarios, different storage methods can be used to store the bound inline information with the collected data of the event link. Exemplarily, the binding and storage of the inline information with the collected data of the event link can be in the following ways:

[0100] Implementation method 1: writing the inline information into a private frame of the code stream of the collected data of the event link, and saving the code stream in which the inline information is written.

[0101] This implementation is aimed at the scenario where the collected data is video data.

[0102] Specifically, for a certain target event, after detecting process 001, you can organize the factory event alarm start information body, the user-defined event intermediate process, organize the user-defined information structure, detect process 00N, and organize the factory event alarm stop information structure; the factory event alarm start information body, the user-defined information structure, and the factory event alarm stop information structure constitute private frame information, and the private frame information is recorded in the private frame of the code stream to complete the preview overlay and recording tasks. The detection of process 001 is the starting condition of the target event, and the detection of process 00N is the end condition of the target event.

[0103] In one implementation, when a product enters a process, the process name in the template is superimposed on the private frame of the bitstream through a specified interface, such as the OSD (Object Storage Device) interface, so that the process name in the private frame of the bitstream can be used for subsequent video tracing. At each specific step, the process information can be superimposed on the bitstream.

[0104] Implementation method 2: storing the collected data of the event link to a hard disk, and writing the inline information as additional information of the collected data of the event link to the hard disk.

[0105] This implementation is a universal method. In any scenario, the collected data can be stored in the hard disk, and the inline information can be written into the hard disk as additional information of the collected data of the event link. And using the inline information as additional information of the collected data can create a binding relationship between the inline information and the collected data of the event link.

[0106] The additional information is a mechanism for recording event information in a hard disk file. After an event occurs, the start time, end time, video type, text information, and video clips of the event are synchronously written to the hard disk file in reverse order from the end of the file. The collected data corresponding to the additional information can be quickly found by searching the content of the additional information.

[0107] The additional information may generally include video frame description information, motion detection information, ATM (Automatic Teller Machine) transaction information, POS (point of sale) information, intelligent information, etc. It may also be used to store various specified data, such as OEM (Original Equipment Manufacturer) customer customized data. The additional information is written in reverse order.

[0108] Optionally, in another implementation, such as Figure 2 As shown in Figure 1, when a factory event is triggered, the video can be cut into segments first, and then label information can be added to the current segment. Figure 2 As shown. The device first cuts the segment and then adds a label to the new segment. The current time is used as the start time of the label, and the end time of the label is specified by the template. Of course, if a process in the template has no label duration, the default duration can be set to 20s. The video data can be stored in segments according to the predetermined size. For example, after the video is full of 1G, the next 1G of data is marked with the same label as the previous one; such as the labeling of process 3 across video segments below.

[0109] Tags are similar to additional information, but they are different. Additional information is generally not displayed to users, but tags can be displayed to users. Tags can be understood as the attributes of a video. The first video clip is labeled A1, the second video clip is labeled B1, and the third is labeled A2. Letters represent events, and numbers represent the stages of events. Later, the first and third videos can be filtered out as the same factory event. Figure 2 As shown, 1G data includes the collected data of process A1, process A2 and process A3, and the index of process 1 is used as additional information 1, the index of process 2 is used as additional information 2, and the index of process 3 is used as additional information 3. It can be understood that data can be stored in segments. For example, when storing the collected data of process 3, 1G data is full, then the remaining collected data of process 3 can be stored in the next 1G data, such as Figure 2 As shown, the next 1G data may include the collected data of process A3 and process A4, with the index of process 3 as additional information and the index of plant event A as additional information of plant event A, which includes the information of the complete process. The index of the process corresponds to the above inline information.

[0110] The above two implementation methods are only two of the multiple implementation methods for the present application to bind and store the inline information with the collected data of the event link. Any method that can bind and store the inline information with the collected data of the event link can be applied to the present application.

[0111] Optionally, the inline information also includes: a sequence number of the event link in the target event.

[0112] It is understandable that each event link in the same event has a corresponding sequential number; and different users, when displaying the collected data of each event link of the target event in the form of the workflow of the target event, have different arrangement requirements for each event link, and this application can customize the order of event links in the workflow according to the needs of users. For example, the production of water cups. Process 1 is code scanning, process 2 is edge grinding capture, process 3 is cleaning video, and process 4 is packaging voice broadcast. When recording, first record according to process 1, process 2, process 3, process 4. But in the end, the workflow sequence that the user wants is process 1, process 3, process 2, process 4. The user can choose to arrange the workflow in the order of process 1, process 3, process 2, process 4, so that the workflow in the order of process 1, process 3, process 2, process 4 can be displayed.

[0113] As shown in Table 1, the specific contents of the factory event steps, process names, services included in the factory event, factory preset standards, and inline information are introduced by way of example.

[0114] Table 1

[0115]

[0116] According to the inline information after the template update is updated, the order of event links in the workflow can be customized according to user needs. For example, the link sequence of an event originally recorded in the hard disk is link A, link B, link C, link D, link E. According to user feedback, the link sequence of the event needs to be link B, link C, link A, link E, link D. This feedback can be a template set by the user. The NVR can create a process copy process new based on this template, and then update based on this copy. Therefore, this application can not only process real-time video recordings, but also reorganize historical recordings.

[0117] Exemplarily, the reporting process may include: sending a capture command to the camera; calling back to process the image data; saving the image data to the hard disk; obtaining the file URL; receiving the scanning information of the POS; recording the start / end recording time period; and transmitting the alarm to the reporting platform.

[0118] Below, the process of reporting time using the barcode scanner is introduced in detail.

[0119] NVR reads the configuration parameter Vector1 of process 1, calls the POS of the single-step service link, connects the barcode scanner, and links the channel Channels to record. When NVR parses the POS data with barcode value, it records the characteristic value character1, and triggers the recording message to the recording plan thread according to the linkage link information, superimposes the barcode value on the preview screen in POS mode, and records the information body info to the database or tag information, etc. Among them, Vector=[monitoring point Channels→process step→sequence characteristic character→single-step service link→factory event information body info]

[0120] The premise of process 2 is to scan the barcode first and then delay for 20s (to facilitate placing the glass at a fixed point). The system reads the configuration parameter Vector2, detects that the delay time of 20s is up, calls the single-step service recording, and reads the data buffer value is not empty, then starts manual recording, records the characteristic value character2, and links normally and writes additional information. However, the additional information here refers to Table 1, and the chain information of the factory event will be recorded additionally.

[0121] Read the configuration parameter Vector3 of process 3, call the single-step service capture to trigger the capture instruction, and the system will send IPC (IP Camera) to capture the image only when the detection delay time is reached and the recording service status is normally turned on. The background will store it to the hard disk according to the link. By calling the SDK command sent by the IPC camera session interface and setting the image format (JPEG format), image quality and bitstream type to be obtained, the image data of the IPC is received (the data length is dynamically opened and cannot exceed 16M at most). The IPC then processes the received data through callback, stores the image according to the manual screenshot type during preview, and saves the image to the hard disk. The single-threaded polling process channel manually captures the data, and then converts it into the address reported to the HCP (Hitachi Content Platform, an enterprise-level content management platform) platform.

[0122] And so on, until the last process. NVR reports the IPC name, NVR name, barcode scanning time, barcode value, IPC capture address, manual recording start / end time and other information to the aggregation service device in the form of SDK (Software Development Kit) transparent transmission according to the customized agreement. The platform parses and stores the barcode alarm information reported by the NVR. The platform supports real-time preview and video retrieval and playback of barcode events, and the video clips exported by the platform can display the barcode information normally using the player, which is the overall design logic.

[0123] The scheme of the embodiment of the present application can bind and store the collected data of any event link with the inline information, wherein the collected data is the data obtained by the device indicated by the device indication information of the event link in the process of executing the target function service, and the inline information at least includes the identification information of the target object and the link identification of the event link. In this way, the collected data of the same object in different event links can be aggregated through the inline information, thereby providing a basis for the retrieval of the collected data corresponding to each link of the same target event and other operations.

[0124] Optionally, the method further includes:

[0125] After binding and storing the inline information with the collected data of the event link, determining the description information corresponding to the event link; wherein the description information corresponding to the event link includes the specified identification information, the link identification of the event link, the description information of the collected data of the event link and the specified configuration information related to the event link; wherein the description information of the collected data of the event link includes information for describing the storage location of the collected data of the event link; the specified identification information includes the first identification information or the second identification information, the first identification information is the identification information of the object appearing in the event link and the global object information corresponding to the object appearing in the event link, and the second identification information is the identification information of the object appearing in the event link;

[0126] The description information corresponding to the event link is sent to the aggregation service device, so that the aggregation service device performs a designated aggregation process based on the received description information corresponding to the event link.

[0127] When the event task represented by the target event is an assembly generation task for a task object, the designated identification information may include first identification information.

[0128] When the event task represented by the target event is a task for analyzing and processing an existing task object, the designated identification information may include second identification information.

[0129] The description information of the collected data of each event link is sent to the recording device after each device of the event link collects data for the event link. Different target function services collect different data, so the description information of the collected data for executing different target function services can be different.

[0130] For example, when the target functional service of a certain device is a video recording service, the description information of the collected data of the event link may include: the start time and end time of the collected data of the event link, and the device information of the device corresponding to the event link;

[0131] If the device indication information of the event link is a device identifier, the device information may be the device identifier; if the device indication information of the event link is a channel identifier, the device information may be the device identifier and the channel identifier.

[0132] When the target functional service is a picture capture service, the description information of the collected data of the event link may include: the storage address of the collected data of the event link.

[0133] The specified configuration information related to the event link may be pre-set information related to the event, such as link information, process information, threshold conditions and other information. The specified configuration information of different event links may be different, and this application does not limit this.

[0134] The aggregation service is to aggregate various event links belonging to the same target event. The aggregation service device can be the recording device itself or a predetermined service platform. The aggregation process can be that the recording device itself aggregates and pushes it to the corresponding target platform. It can also be that the predetermined service platform aggregates itself.

[0135] Optionally, the target functional service includes an alarm service;

[0136] The method further comprises:

[0137] Receiving alarm data analyzed and reported by the device corresponding to the event link when executing the alarm service during the execution of the event link; wherein the alarm data includes the alarm content, the alarm type and the identification of the object involved in the event link;

[0138] In response to satisfying the alarm aggregation conditions for the event link, determine the alarm data that has been received and reported by the device corresponding to the event link and contains identification information of the same object, select the alarm content whose image quality meets the predetermined selection conditions from the determined alarm data, bind the link identifier of the event link, the selected alarm content and the identification information of the same object, and perform predetermined alarm processing on the bound content.

[0139] Different events may have different devices and different alarm services. The alarm data of different alarm services may have different alarm contents. For example, the alarm contents may include alarm pictures, alarm video segments, alarm voice segments, etc. It is understandable that in different scenarios, if the device is a recording device, the alarm contents may be alarm recording segments, and if the device is a video recording device, the alarm contents may be alarm video segments.

[0140] The alarm content may be obtained by recording the current environment in which the device is located by the device.

[0141] It is also understandable that each alarm service can set corresponding alarm conditions, and when the alarm conditions are met, corresponding alarm data can be reported. For example, in an exam event, during the identity verification process, if it is identified that the person performing identity verification does not match the candidate information, a photo taken of the person can be used as part of the alarm data.

[0142] In the present application, the alarm services included in the target function services of different devices may be different. For example, for a device used for facial image acquisition, the alarm service is to alarm whether the face matches the preset face. For a device used for OCR acquisition, the alarm service is to alarm whether the collected identity information matches the preset identity information.

[0143] Exemplarily, in an examination event, the device is a camera, which captures the facial image of any person to be tested and matches it with the facial information of a pre-stored reference person. If the matching result indicates that the facial image of the person to be tested does not belong to the reference person, an alarm is issued, wherein the alarm picture may be an image captured by the camera of the person to be tested, the alarm type is the test person mismatch type, and the object identifier of the object involved in the event link may be the facial image of the person to be tested.

[0144] For example, the alarm trigger condition corresponding to the device can be set. If the similarity score between the collected face device and the face on the student ID card is less than 50 points, the examiner mismatch event is triggered. For example, if the similarity score of the face on the ID card of student A12345 is less than 50, the examiner mismatch factory event is triggered. Wherein, the ID is the order of detection, CarNUM is the number of the student ID card, and Score is the score.

[0145] The predetermined alarm processing may be sending the bound content to a staff member, etc. The predetermined alarm processing set in different scenarios is different, and this application does not limit this.

[0146] In addition, in the present application, each event link belonging to the same event may generate alarm data. Therefore, the scheme of the present application can also report the alarm data generated by each event link together after each event link of the same event is executed and completed.

[0147] Optionally, the device indication information corresponding to the event link is multiple; the determining of the identification information of the object appearing in the event link during the execution of the target function service includes:

[0148] Determine the target collection data obtained by the target device during the event link; wherein the target device is a device among the devices indicated by the multiple device indication information, the collection range of which can include the identification information of the object appearing in the event link;

[0149] The identification information of the target object corresponding to the determined target collection data is obtained, and the identification information of the object appearing in the event link during the execution of the target function service is obtained.

[0150] Among the devices indicated by the plurality of device indication information, the devices whose collection range can include the object identification of the object appearing in the event link may be predetermined.

[0151] It is understandable that in some cases, due to the different service functions set for the devices and the influence of the installation orientation of the devices, not all devices in the same event link can recognize the object identification of the event link. However, using the solution of this implementation method, the object identification collected by any device belonging to the target device can be used as the identification information of the object appearing in the event link.

[0152] In addition, the target acquisition data of the present application may be externally injected. Specifically, as described in the above embodiments, the identification information of the corresponding target object may be determined through the externally injected target acquisition data.

[0153] Channels with the same type of target function services can be bound, and the information to be aggregated generated by the channels with a binding relationship can be aggregated. The channels with a binding relationship can be used as a channel group. The information to be aggregated is generated by the channel executing the target function service. Whether the target function service corresponds to the information to be aggregated is predetermined. When aggregating the information to be aggregated generated by the channels with a binding relationship, this implementation method can consider the time dimension. Based on the time when the information to be aggregated is generated by the channels with a binding relationship, the information to be aggregated whose generation time belongs to the same time range can be aggregated to obtain aggregated data. The aggregated data can be stored or uploaded to the aggregation service device; and the aggregated data corresponds to the identifier of the channel group, and the identifier of the channel group can be used to retrieve the aggregated data corresponding to the channel group later.

[0154] For example, Figure 3As shown, in the test event, the device can be an OCR device and a camera, and the factory event template can be pre-configured: channel group + test identity; the device corresponding to channel 1 of the NVR is an OCR device, which is used to collect ID card OCR, that is, ID card information, and the device corresponding to channel 2 is a camera, which is used to collect face information. The OCR device corresponds to a service function for alarming identity information, and the camera corresponds to a service function for alarming faces. Both service functions are alarm type service functions. Channel 1 and channel 2 can be bound, and channel 1 and channel 2 are a channel group, and the channel group is identified as channel group A. If the face and OCR results do not match, the NVR alarm is issued. The NVR can upload the fused alarm and video data to the platform. The information to be aggregated is the alarm information. The alarm information belonging to the specified time range can be aggregated, so that the aggregated data of channel group A can be obtained. For example, if the specified time range is 5s, then the face alarm time and the OCR alarm time, if the time interval is within 5s, then aggregation is performed. Within 5s, whether the face alarm time or the OCR alarm time comes first, aggregation can be performed. If there are multiple face alarms and one OCR alarm, the face alarms 5S before the OCR alarm are aggregated with the OCR alarm based on the time point of the OCR alarm. If there are multiple face alarms and OCR alarms, the OCR alarms and face alarms within each 5S interval are aggregated starting from the earliest time point among the multiple alarm data.

[0155] Furthermore, it is understandable that the alarm information generated within each 5S interval can be cached. For example, Alarm Cache represents the alarm cache. Face list represents the face alarm information, Ocr list represents the OCR alarm information, and the alarm information can be marked with subscripts such as 0 and 1.

[0156] It is understandable that there may be multiple alarm contents, and therefore, the present application may determine the alarm content whose quality meets the predetermined selection criteria for use.

[0157] When the alarm content is an alarm picture, the alarm content whose quality meets the predetermined selection condition is selected, and the alarm picture with the highest image quality may be selected.

[0158] In this embodiment, there may be multiple ways to determine the alarm picture with the highest image quality. In one implementation, the alarm pictures in each alarm data may be analyzed using a preset image quality analysis method to obtain the alarm picture with the highest quality. For example, the image quality analysis method may be to score each alarm picture using an image clarity scoring model to obtain the picture with the highest score. The image quality analysis method of this application utilizes existing technology, and this application does not limit this.

[0159] In another implementation, the device parameters of each device capable of collecting alarm images can be used in advance to determine the device performance of each device. Thus, for each alarm image in the alarm data, the alarm image collected by the device with the best device performance is used as the alarm image with the highest image quality.

[0160] In the present application, the number of the alarm pictures with the highest image quality is not limited to one, and can be one or more.

[0161] For the alarm video segment, the quality meets the predetermined selection conditions, which can be that the picture clarity of the alarm video segment meets the specified requirements. For the alarm audio segment, the quality meets the predetermined selection conditions, which can be that the audio clarity of the alarm audio segment meets the specified requirements. Different alarm contents correspond to different predetermined selection conditions, and this application does not limit this.

[0162] Optionally, the configuration information of the event link is provided with a corresponding alarm triggering condition; the method further includes:

[0163] Send the alarm trigger condition to the device corresponding to the event link;

[0164] Receive the alarm information reported by the device corresponding to the event link when detecting that the alarm triggering condition is met during the execution of the target function service, and issue an alarm for the event link based on the alarm information.

[0165] It is understandable that the alarm triggering conditions of different event links can be set according to the application scenario. Exemplarily, the alarm triggering condition sent to the device 1 is that if the face image collected by the device is detected and does not match the preset face image, an alarm is issued.

[0166] Specifically, the alarm trigger condition can be triggered not only by the content of the video screen, but also by the start of the preset process steps. After the factory event is triggered, an edited workflow can be obtained. For example, each packaged and shipped glass triggers a workflow to form a process instance. The execution of multiple processes does not affect each other, and independent records can be generated, which is convenient for querying on the factory assembly line.

[0167] In this embodiment, for each target event, an independent alarm record for the object of the target event can be generated for the object, which is convenient for tracing.

[0168] Optionally, the event configuration information of the target event also includes: identification information of a target group with a device as an element within the group and each device included in the target group; wherein each device included in the target group is a device indicated by device indication information corresponding to at least two event links, or a plurality of devices indicated by device indication information corresponding to one event link; the identification information of the target group is identification information set based on the collection range that can be covered by each device included in the target group;

[0169] The method further comprises:

[0170] Obtaining target information reported by each device included in the target group; wherein the target information reported by each device includes the collected data of the device, or the analysis content obtained after performing a specified analysis based on the collected data of the device; wherein the specified analysis includes reporting an alarm analysis for a predetermined alarm event;

[0171] Based on the acquired target information reported by each device, perform a specified aggregate analysis on each device in the target group to obtain an aggregate analysis result;

[0172] The identification information of the target group is used as the identification information of the aggregate analysis result, and the aggregate analysis result is output.

[0173] The solution of the present application can classify multiple devices into a group. The devices in the group can be devices indicated by device indication information corresponding to different event links, or devices indicated by device indication information corresponding to the same event link.

[0174] Each device of the present application can first perform a specified analysis by itself, and then send the analysis content to the video recording device, so that the video recording device can summarize more effectively. Since the functions implemented by each device can be different, the specified analysis performed by each device can be different.

[0175] The specified analysis may include an alarm analysis for a predetermined alarm event, or may include a statistical analysis for abnormal data, etc. In different scenarios, the specified analysis is different, and this application does not limit the specified analysis.

[0176] For example, in a security inspection scenario, face camera A is set at entrance area A, and face camera B is set at exit area B. Face camera A and face camera B are devices belonging to different event links. Face camera A and face camera B can be regarded as devices of a target group. After face camera A in area A recognizes a face, it can automatically build a model and store it in the face database. If the same person is recognized multiple times, it is only stored once, and the current time is recorded. When face camera B in area B recognizes a face, it is compared with the person in the face database. If the comparison is successful, the current time is subtracted from the time when the person is imported into the face database, as the queue time for the person to walk from area A to area B. If the queue time exceeds the preset value, it is considered to be an alarm for too long queue time, and the alarm information and pictures are transmitted to the platform. And the person is deleted from the face database to avoid repeated alarms. After face camera B recognizes a face, the operation of comparing it with the person in the face database is the above-mentioned specified analysis.

[0177] For example, some areas can be set with alarms, and if someone encounters an unexpected situation, the alarm can be pressed to alert. Each alarm can be set with a corresponding area range, and each camera in the area range and the alarm can be set into a group. When the alarm is triggered, the data collected by each camera in the group can be uploaded synchronously.

[0178] For example, the sky-sensing box can be bound to the channel on the video recording device. When the sky-sensing box analyzes the code stream of the access channel and generates an alarm of high-altitude dropping, the sky-sensing box can report the alarm information, alarm content and alarm video to the video recording device. The sky-sensing box is a data analysis device for analyzing whether there is an image of high-altitude dropping in the video corresponding to the code stream. The channel and the sky-sensing box constitute a group.

[0179] In this embodiment, different devices can be grouped into a group, and the data collected by the devices in the group can be used for designated analysis. The group can be used as a whole to implement the corresponding functions. This embodiment can also be applied to the scenario of third-party device docking, and the third-party device can be bound to the channel on the recording device, that is, multiple devices can be bound to one channel. After binding, the original channel is used externally, but the functions implemented by the channel include the functions of the third-party device and other bound devices. The channel is the above-mentioned group.

[0180] In addition, the solution of this embodiment can also be applied to projects such as microphones and environmental data acquisition instruments.

[0181] For example, the production of glass A, glass B and glass C are different events, and the production of glass A, glass B and glass C are all carried out according to a preset glass production template. The workflow of each glass production event may include the member name of the staff member corresponding to the event link, and the step refers to the event link.

[0182] Optionally, the process of configuring the event configuration information of the target event includes:

[0183] Outputting a configuration interface containing a custom template of a target event; wherein the custom template contains configuration items for a custom event link for the target event, and configuration items for configuring configuration information of the custom event link;

[0184] The configuration information set in the configuration interface is acquired to obtain the event configuration information of the target event.

[0185] The user can use the configuration interface to configure each event link of the target event, the device indication information of the recording device required for the target event, the device corresponding to each event link, the target function service required to be enabled for each device, the alarm triggering conditions, the start and end conditions of the event link, the start and end conditions of the target event, etc.

[0186] Exemplarily, as shown in the following table, configuration information may be set for a target event by configuring the following five submodules.

[0187] Table 2

[0188]

[0189] Among them, number PD-001 is a custom factory event module, and the configuration of the custom factory event template can be divided into 4 steps. The first step is to divide the process. The second step is to set different services and threshold parameters. The third step is to bind different channel groups, and different channels are responsible for different processes. The fourth step is to store the template. The process is each event link. The service is the above-mentioned service function, and the threshold parameter may refer to the execution time threshold corresponding to each link. For example, event link 2 must be completed within 30s. The event link 2 actually takes 40s, and the workflow record of the abnormal event link will be recorded, so as to be more in line with the factory management method.

[0190] PD-002 is a module for marking the start and end conditions of factory events. This module is used to configure the conditions received by NVR from inside and outside the NVR (that is, as long as it is an instruction that the NVR can recognize, such as POS data, network, etc.). The internal and external conditions correspond to the first internal trigger condition, the first external trigger condition, the second internal trigger condition, and the second external trigger condition.

[0191] PD-003 is the event trigger module, which is used to set the trigger mode of the target event, such as stream trigger, time trigger, threshold trigger, etc. You can set the linkage NVR to get the IPC stream, set the start of recording mark, set reporting, set log writing, etc.

[0192] No. PD-004 is an event clustering module, which is used to set a location for binding and storing the inline information with the collected data of the event link, for example, it can be stored in a private frame, additional information, database and / or memory.

[0193] No. PD-005 is a workflow display module, which is used to set workflow and exception status.

[0194] As an example, a configuration process for factory events is introduced below.

[0195] For the standard operation monitoring points and monitoring operations of factory events, the glass factory production workflow can be arranged in the interface by editing methods such as text / parameter setting / graphic drag and drop. The required service types can also be combined to form a new user event (such as glass production events, examination events). This event can combine the existing multiple services of DVR / NVR in a nested manner (POS, preview, capture, recording, IOT (Internet of Things), identification and alarm services, etc.), and each service itself has formed an independent user interface. Taking the glass factory as an example, the elements on the interface during the new creation process at least include: service type service type + delay time + IP port + channel associated with the work + nested conditions, and the engine mode on the DVR / NVR will change with the changes of the newly created service type. Factory event core tags: You can customize the input and set the content of the step.

[0196] like Figure 4A-4B As shown, in the configuration interface, you can add, modify, delete and preview, which are used to configure the configuration items corresponding to specific factory events. Figure 4A An example interface for factory event settings. Figure 4AAs shown, the configuration items are: wire drawing station, work number, factory event SOP (Standard Operating Procedure) and process name. Among them, the wire drawing station, work number and process name are configured. Figure 4A As shown, you can select a capture mode from multiple factory event SOPs, such as a mode for capturing a face area. The interface after selecting is as follows Figure 4B shown. Figure 4C In the interface, channel selection is to configure the corresponding channel for the capture mode. Figure 4C The factory event single-step process settings are introduced in detail, including channel selection, enabling face capture, arming time, linkage mode and rule configuration options, and the above options can be cleared and applied.

[0197] The custom factory event template provided in this embodiment connects the existing NVR services in series for use, and each step stores a specific event type, increasing the applicability of different scenarios. In the prior art, different target events, such as events corresponding to steel plants, glass plants, and examinations, need to be customized each time because of the different services used. After the present application provides a custom template, all services are set up according to the rules, and the system executes according to the template internally, reducing customization. In addition, the solution of the present application provides a mechanism for reorganizing massive monitoring information. The NVR aggregates according to user scenarios, and regularly integrates different event results from different channels, which can improve search efficiency.

[0198] Next, in conjunction with specific scenarios, an embodiment of the event data processing method of the present application applied to a specific scenario is introduced.

[0199] First, for glass production scenarios, such as Figure 5 As shown, in the glass placement phase of the glass production event, the workbench is as follows Figure 5 As shown, six IPC cameras 501 can be deployed to capture the conditions of the glass 502 in all directions. After the staff scans the QR code on the glass, that is, the code of the glass, through the POS machine, they can get the ID of the glass. The IPC camera 501 automatically starts recording the entire process of glass placement. After the glass is placed at the target position and left to stand, the six IPC cameras 501 can capture the conditions of the glass in the corresponding images of six directions. After detecting that no one is there, the recording stops. Finally, the scanned ID, the start / end recording time, and the addresses of all captured pictures are uploaded to the platform at the same time.

[0200] The IPC camera and POS machine are the above-mentioned devices. The object of this embodiment is glass, and the ID of the glass is the above-mentioned object identifier. The POS machine scans the QR code on the glass, which is the starting condition of the event link, and detecting that there is no one is the ending condition of the event link. Recording the entire process of glass placement and capturing the glass status in 6 frames are achieved by the above-mentioned target function service function. The glass status captured in 6 frames refers to the 6 IPC cameras capturing the glass status in their respective corresponding viewing angles. The start / end recording time point and all the captured image addresses are the collected data of the event link.

[0201] In the specific implementation process of a glass production scenario, the following steps are included:

[0202] Process 1: Work number recognition, staff attendance on NVR (face, work number, work position and other attributes), D1 linkage voice broadcast.

[0203] Process 2: Labeling and scanning. The staff uses POS scanning or OCR to identify the QR code on the glass. Each piece of packaged glass has an independent label (such as barcode + area code + customer information + destination information, etc.), which is directly input into the NVR by the scanner. To complete this action, you need to enable the D1 POS service of the NVR.

[0204] Process 3: Edge cleaning. Link D2 to start recording.

[0205] Process 4: Personnel leave the site. NVR D1~D6 detects whether there are personnel present.

[0206] When cameras D1~D6 detect that there is no person present, it means that the person has left the site and process 5 can be carried out.

[0207] Process 5: Keep records before installation. D1~D6 NVR takes sequential pictures and stores the addresses.

[0208] Step 6: Packing and delivery. NVR D1~D6 stop recording, link voice broadcast, and upload to the platform.

[0209] Step 7: Resume data after network disconnection. NVR can store data during the period of disconnection from the platform and transmit it back to the platform after the network is restored.

[0210] In a steel pipe production event, there may be 10 event links. It is necessary to confirm the material information of the steel pipe in the current event link at each event link. Thus, the corresponding relationship between the steel pipe material information and the event link can be uploaded to the business platform. Through the business platform, the event link of the steel pipe of a certain material can be queried. Figure 6As shown, it includes 1-8 and two QC (Quality Control) event links, and the QC event link is the quality inspection link. The terminal is the above-mentioned device. The HUB is a communication hub. The electronic billboard is mainly used to display the relevant data of each event link. It can be seen that Figure 6 The connection relationship is that the platform and NVR are connected in communication, and NVR is connected in communication with the electronic signboard and each terminal respectively. The electronic signboard is used to display workshop and production line information, such as workshop: 3A2; production line: 01 line.

[0211] In the steel pipe production event, the network topology can be IPC-recording equipment-business platform. Network communication can be performed between IPC and recording equipment, and network communication can be performed between business platform and recording equipment.

[0212] When a steel pipe production event is executed, one video recording device is used to analyze the points of 10 event links in a factory area. When the same steel pipe passes through different points, IPC extracts feature value records from it through OCR, and finally the points captured at different points can be aggregated. That is, this embodiment identifies the material information of the steel pipe involved in each event link, binds and stores the material information of the steel pipe and the video collected for the steel pipe in each event link, and then determines the various videos belonging to the same steel pipe based on the material information. The material information of the steel pipe is the above-mentioned inline information, and the video collected for the steel pipe is the above-mentioned collected data.

[0213] In this embodiment, the OCR analysis frame rate is a configurable item, for example, the frame rate of the OCR video analysis can be adjusted to 1s, 3 images. The recognition result of the OCR analysis frame rate can be processed according to the optimal frame, or it can be counted according to the result with the highest probability. For example, the steel pipe in process 2 of the assembly line can be set to be recognized 5 times, 3 of which are #2405108690#, and 2 are #24000000#, then the final recognition result is determined to be #2405108690#.

[0214] For example, the material information of a steel pipe may be "#2405108690#". The IPC may be based on an algorithm callback filter, and when two "#"s are identified, the data within the #s are extracted as a feature value, that is, the object identifier of the steel pipe, and the object identifier may be reported to the video recording device.

[0215] Each steel pipe production has its own independent and complete record of the collected data of the 10 processes. Using the object identification of the steel pipe, the collected data of the 10 processes of each steel pipe can be associated.

[0216] In the event of physical examination, such as Figure 7As shown, it includes a card reader device, an NVR, a switch, a mobile phone, a computer, etc. Among them, the access control card reader device is connected to the NVR for communication, and the NVR is connected to the switch for communication. The switch is used for data exchange, and the mobile phone and the computer are used to deploy the aggregation service device. The mobile phone APP, that is, the aggregation service device, can communicate with the switch through the WAN (wide area network).

[0217] In this embodiment, the NVR can be connected to a card reader device, and an aggregation service device is used to manage video arbitration. The NVR serves as a storage center, and the ID card information swiped into the card reader is entered into the label information in the device's channel to facilitate subsequent tracing and arbitration. The label information content includes the ID card number and name information of the ID card information. Locally, the platform's label search interface is used for subsequent searches. The search supports fuzzy searches and can enter ID card numbers or names for video searches. This makes it convenient for parents or students to conduct targeted retrospective searches when they have questions about their test scores to resolve some necessary disputes. At the same time, the option uses an NVR with built-in audio broadcast to access the card reader device, which is easy to carry and has a high cost-effectiveness ratio. Managers can search by ID number or name, quickly locate the problem, improve parent user satisfaction, and reduce the adverse effects of various disputes.

[0218] Moreover, the solution of this embodiment can enhance business value. Specifically, the value to users is as follows: when an ID card is swiped, a prompt will be displayed saying that the card is swiped successfully, ensuring that the information has been entered. The value to competition is as follows: the optional NVR device is small and can be carried to each examination room, reducing the overall deployment cost. This embodiment has a simple system structure and can reuse the existing video surveillance system to form a traceable record of the current recordings of each channel.

[0219] Corresponding to the above-mentioned data processing method for events, the present application also provides another data processing method for events, which is applied to an aggregation service device, and includes:

[0220] Step A1 receives a search keyword for a target event input by a user in a search interface of the aggregation service device; wherein the search keyword includes identification information of any object; any task object is an object indicated for processing by an event task represented by the target event;

[0221] The search interface of the aggregation service device may have a corresponding search box, in which the user may enter a search keyword. The identification information corresponds to the identification information in the above embodiment. For example, for a glass production event, the user may enter a code corresponding to any glass.

[0222] Step A2 sends a search instruction carrying the search keyword to the video recording device, so that the video recording device responds to the receipt of the search instruction, based on the inline information and collected data of the event link of the target event that are currently bound and stored, to screen out each inline information that matches the search keyword carried in the search instruction and the collected data bound and stored with each screened inline information, and feeds back each screened inline information and the bound collected data to the aggregation service device; wherein the video recording device binds and stores the inline information and collected data of the event link of the target event in accordance with the above-mentioned data processing method for events.

[0223] Step A3 receives each inline information fed back by the video recording device and the bound collected data;

[0224] Step A4 outputs the aggregate information corresponding to the search keyword and including each inline information fed back by the video recording device and the bound collected data in the form of a workflow of the target event.

[0225] In this embodiment, the search can support fuzzy search by the main type of factory events, the secondary type of events, and keywords. Support retrieval in chronological order and then aggregation. The event steps are defined according to the order of occurrence of events, and each step stores a specific event type. The key is to have a timeline order. The video clip set {A1, B1, ...M1} of process 1 and the video clip set {A2, B2, ...M2} of step 2 are retrieved. Similarly, each template type will generate a fragment result list, and the results will be aggregated during the search according to the template order and the fragment time order. It can support the retrieval of a collection of all different process steps according to event feature values. For example, multiple processes are searched according to the same glass QR code, and then the results are aggregated according to the size of the process number.

[0226] The implementation process of a data retrieval method is introduced as an example. First, the recording device can receive a factory event retrieval request message, analyze the template mapping table according to the factory event type, retrieve the feature value according to the time sequence or retrieve the process step according to the spatial sequence, cluster the factory events, merge the videos, and export the backup. The backup export can back up the aggregated data and upload it to the aggregation service device.

[0227] Optionally, the method further comprises:

[0228] In response to the event information summary instruction about the target keyword, the description information containing the target keyword is retrieved from the description information corresponding to each event link reported by the recording device currently saved; wherein the target keyword includes the object identifier of any task object or the link identifier of any event link;

[0229] For the same target event, the object identifiers corresponding to the various event links of the target event are the same. Therefore, when the target keyword includes the object identifier of any object, the saved description information includes the description information of the target keyword, which is the description information of the event links belonging to the same target event.

[0230] The link identifiers corresponding to the same event link type of different target events of the same event type are the same. When the target keyword includes the link identifier of any event link, the saved description information includes the description information of the target keyword, that is, the description information of each event link belonging to the same event link type.

[0231] Based on the filtered description information, an event information summary result for the target keyword is constructed.

[0232] The solution of this embodiment can summarize the description information including the target keyword, and obtain the event information summary result for the target keyword.

[0233] The summary results of this application can be used to analyze events, etc.

[0234] Exemplarily, after constructing the event information summary result for the target keyword based on the filtered description information, the method further includes:

[0235] Based on the constructed event information summary result, data analysis of specified analysis dimensions is performed to obtain analysis results; wherein the specified analysis dimensions include analysis dimensions for event links, analysis dimensions for objects, or analysis dimensions for accuracy of event information.

[0236] Each event link can be displayed according to the workflow steps, so that the specific link is clear at a glance. Whether each specific step meets the standard can also be displayed intuitively. Each process template can independently set alarm thresholds, so the workflow can clearly show which step is currently being carried out and whether there are any abnormalities.

[0237] Specifically, a workflow display interface can display the execution time of each event link of each target event and the benchmark time of each event link. If the execution time of any event link exceeds the benchmark time, it means that there is an abnormality in the link.

[0238] In this application, data analysis of specified analysis dimensions is performed to obtain analysis results. For example, the time spent on each step and the standard deviation can be divided, and abnormal time periods and defective products can be quickly discovered. The simplest process contains time, which can help factories to do statistics on efficiency dimensions. The normal production time of each process of each commodity is quantified into a one-dimensional array. Process 1 takes 15 seconds, process 2 takes 30 seconds, etc. The specific one-dimensional array can be [15, 30, 20, 160, 30, 50, 5, 10, 120, 250].

[0239] The factory produces 200 items per day, so the actual production situation should be a 200x10 two-dimensional sequence:

[0240] For example: [

[0242] [20,29,19,150,30,50,5,10,120,270]

[0243] [22,29,29,140,30,50,15,10,220,270]

[0244] ……]

[0245] Then, the variance is calculated with the series of standard production time. Based on the calculation results, the process with possible abnormal behavior can be determined, and the corresponding products can be sampled.

[0246] The sequence of standard production time is as follows: [

[0248] [0,1,1,0,1,0,1,0,0,0]

[0249] [0,0,1,0,1,0,1,0,0,0]

[0250] [0,0,1,0,1,0,1,0,0,0]

[0251] [0,1,1,0,1,0,1,1,0,0]

[0252] … ]

[0254] In this application, there may be one or more NVR devices corresponding to the same target event.

[0255] like Figure 8 The figure shows a schematic diagram of abnormal product analysis based on process standard deviation clustering in the present application. Figure 8The cluster statistics of different time periods from 2024-3-1 to 2024-3-5 are recorded. It can be understood that the smaller the number of time cluster distribution, the fewer the same category, the greater the abnormality, and the corresponding log information can be viewed by clicking on each data. Exemplarily, it can be a cluster statistics of the time spent on the same process corresponding to each event in each time period. If the number recorded in the statistics in the table is larger, it means that there are more events with similar time spent on the execution of the process in each event, and the process is less abnormal. For example, at 13:00 on 2024-3-1, there are 500 events that executed process 1, and 425 of them were executed within 30S-35s, then process 1 of the 425 events is normal.

[0256] Multiple NVR devices are orchestrated together, first clustered, then process defined, and finally responding according to the preset scheduling rules. For example, facing the production line, device NVR-A performs facial feature recognition in 1~10s, device NVR-B weighs and labels in 2~20s, and device NVR-C performs full-channel capture sampling in 2~20s. Finally, through the search of commodity production events, for example, the storage module receives a user's request to query commodities, and uses the image search algorithm to search the images stored in the HDD according to the personnel pictures and ID numbers provided by the user, and finally generates a linked list package of the appearance time period associated with the given personnel. If there is a backup download requirement, the video data segment associated with the personnel in the query information can be used to query and download the video data. Finally, the packaged information and video data segments are returned to the business in sequence.

[0257] The solution of this embodiment can effectively realize retrieval and data aggregation for multiple video recording devices.

[0258] In the scheme of this embodiment, since the inline information of the event link of the target event can be bound and stored with the collected data through the above-mentioned data processing method for the event, after the user enters the search keyword for the target event in the search interface of the aggregation service device, the aggregation service device can send a search instruction carrying the search keyword to the recording device, so that the recording device can filter out the inline information and collected data of the event link of the target event that are currently bound and stored, and filter out the various inline information that matches the search keyword carried in the search instruction and the collected data bound and stored with the filtered inline information, and feed back to the aggregation service device, and the aggregation service device receives the various inline information and bound collected data fed back by the recording device. Therefore, the aggregation service device can output the aggregate information corresponding to the search keyword, which contains the various inline information and bound collected data fed back by the recording device. It can be seen that this embodiment can retrieve the collected data corresponding to each link of the same target event.

[0259] The present application also provides a data processing method for an event, which is applied to a video recording device, and the method includes:

[0260] Receiving a search instruction carrying a search keyword; wherein the search instruction is a search keyword for a target event input by a user in a user interface of an aggregation service device; wherein the search keyword includes identification information of any task object; any task object is an object indicated for processing by an event task represented by the target event; based on the inline information and collected data of the event link of the target event that are currently bound and stored, screening each inline information matching the search keyword carried in the search instruction and the collected data bound and stored with each screened inline information; wherein the recording device binds and stores the inline information of the event link of the target event with the collected data according to any of the above-mentioned data processing methods for events;

[0261] Feedback the screened inline information and bound collected data to the aggregation service device, so that the aggregation service device outputs the aggregated information corresponding to the search keyword and including the inline information and bound collected data fed back by the video recording device.

[0262] In this embodiment, the aggregation service device may be the video recording device, and the video recording device may have a corresponding UI (User Interface), in which retrieval may be performed. After the user enters a retrieval instruction in the user interface, the video recording device may filter out each inline information matching the retrieval keyword carried in the retrieval instruction and the collected data stored and bound to each inline information filtered out from the inline information and collected data of the event link of the target event that are currently bound and stored, and feed back to the user interface. Thus, the user interface of the video recording device may output the aggregate information corresponding to the retrieval keyword, including each inline information fed back by the video recording device and the bound collected data.

[0263] The present application also provides an electronic device, including:

[0264] The memory is used to store computer programs; the processor is used to implement any of the above-mentioned data processing methods for events, data retrieval methods for events applied to aggregation service devices, and / or data retrieval methods for events applied to video recording devices when executing the programs stored in the memory. In addition, the above-mentioned electronic device may also include a communication bus and / or a communication interface, and the processor, communication interface, and memory communicate with each other via the communication bus.

Claims

1. A data processing method for an event, characterized in that: Applied to video recording equipment; the method comprises: Whenever the starting condition of any event link of the target event is met, the configuration information of the event link is obtained from the event configuration information pre-customized for the target event as the target configuration information; wherein the target event includes multiple event links, and the event configuration information includes the configuration information of each of the multiple event links; the configuration information of the event link records the device indication information and target function service corresponding to the event link, the device indication information is used to indicate the device for data collection for any object appearing in the event link, and the target function service is the target function service required to be enabled for the device indicated by the device indication information during the execution of the event link; Determine the device indicated by the device indication information recorded in the target configuration information as the device corresponding to the event link; When the device corresponding to the event link currently has the target function service enabled, control the device corresponding to the event link to execute the target function service, and when the end condition of the event link is met, control the device corresponding to the event link to end the execution of the target function service under the event link; Acquire the collected data obtained by the device corresponding to the event link in the process of executing the target function service as the collected data of the event link; Determine identification information of an object that appears in the event link during the execution of the target function service; In response to the data storage conditions for the event link, the global object information corresponding to the object appearing in the event link is determined, and combined information containing at least the global object information and the link identifier of the event link is constructed as inline information, and the inline information is bound and stored with the collected data of the event link; wherein the global object information is the identification information of the task object to which the object appearing in the event link belongs, which is determined based on the identification information of the object appearing in the event link, and any task object is an object indicated for processing by the event task represented by the target event.

2. The method according to claim 1, characterized in that The event task represented by the target event is a task for analyzing and processing an existing task object. Accordingly, determining the global object information corresponding to the object appearing in the event link includes: determining the identification information of the object appearing in the event link as the global object information; or, The event task represented by the target event is an assembly generation task for a task object. Accordingly, determining the global object information corresponding to the object appearing in the event link includes: determining the identification information of the object appearing in the event link according to the mapping relationship between the identification information of the task object and the identification information of the object appearing in each event link, and obtaining the global object information corresponding to the object appearing in the event link; Among them, the mapping relationship is determined based on the collected data in the specified link; in the mapping relationship, the identification information of any task object corresponds to the identification information of the object appearing in each event link: the identification information of the object appearing in each event link used when assembling and generating the task object, and the specified link is the task object assembly link in the multiple event links of the target event.

3. The method according to claim 1, characterized in that The method further comprises: After binding and storing the inline information with the collected data of the event link, determining the description information corresponding to the event link; wherein the description information corresponding to the event link includes the specified identification information, the link identification of the event link, the description information of the collected data of the event link and the specified configuration information related to the event link; wherein the description information of the collected data of the event link includes information for describing the storage location of the collected data of the event link; the specified identification information includes the first identification information or the second identification information, the first identification information is the identification information of the object appearing in the event link and the global object information corresponding to the object appearing in the event link, and the second identification information is the identification information of the object appearing in the event link; The description information corresponding to the event link is sent to the aggregation service device, so that the aggregation service device performs a designated aggregation process based on the received description information corresponding to the event link.

4. The method according to any one of claims 1 to 3, characterized in that: The device indication information corresponding to the event link is multiple; the identification information of the object appearing in the event link during the process of executing the target function service is determined, including: Determine the target acquisition data obtained by the target device during the event link, wherein the target device is a device among the devices indicated by the multiple device indication information, and the acquisition range can include the identification information of the object appearing in the event link; obtain the identification information of the target object corresponding to the determined target acquisition data, and obtain the identification information of the object appearing in the event link during the execution of the target function service; and / or, The starting condition of the event link includes a first external trigger condition, or a first internal trigger condition; wherein the first external trigger condition is receiving a trigger instruction for starting the event link sent by a predetermined control terminal, and the first internal trigger condition is detecting a predetermined trigger information sent by a designated device connected to the recording device; the termination condition of the event link includes a second external trigger condition, or a second internal trigger condition; wherein the second external trigger condition is receiving a trigger instruction for ending the event link sent by a predetermined control terminal, and the second internal trigger condition is detecting that a process for serving a target function satisfies a predetermined termination condition; and / or, In the case where the event link is the first link of the target event, the starting condition of the event link includes the first external trigger condition, or the first internal trigger condition; in the case where the event link is a link other than the first link of the target event, the starting condition of the event link includes: a predetermined time distance from a reference time point corresponding to the event link; wherein the reference time point corresponding to the event link is: the time point when the previous event link corresponding to the event link is detected to meet the starting condition; the termination condition of the event link includes: a second external trigger condition, or a second internal trigger condition; Among them, the second external trigger condition is receiving a trigger instruction for the end of the event link sent by a predetermined control terminal, and the second internal trigger condition is detecting that the process for the target function service meets the predetermined end condition.

5. The method according to any one of claims 1 to 3, characterized in that: The target functional service includes an alarm service; The method further comprises: Receiving alarm data analyzed and reported by the device corresponding to the event link when executing the alarm service during the execution of the event link; wherein the alarm data includes the alarm content, the alarm type and the identification of the object involved in the event link; In response to satisfying the alarm aggregation conditions for the event link, determine the alarm data that has been received and reported by the device corresponding to the event link and contains identification information of the same object, select the alarm content whose quality meets the predetermined selection conditions from the determined alarm data, bind the link identifier of the event link, the selected alarm content and the identification information of the same object, and perform predetermined alarm processing on the bound content.

6. The method according to any one of claims 1 to 3, characterized in that: The event configuration information of the target event also includes: identification information of a target group with a device as an element in the group and each device included in the target group; wherein each device included in the target group is a device indicated by device indication information corresponding to at least two event links, or multiple devices indicated by device indication information corresponding to one event link; the identification information of the target group is identification information set based on the collection range that can be covered by each device included in the target group; The method further comprises: Obtaining target information reported by each device included in the target group; wherein the target information reported by each device includes the collected data of the device, or the analysis content obtained after performing a specified analysis based on the collected data of the device; wherein the specified analysis includes reporting an alarm analysis for a predetermined alarm event; Based on the acquired target information reported by each device, perform a specified aggregate analysis on each device in the target group to obtain an aggregate analysis result; The identification information of the target group is used as the identification information of the aggregate analysis result, and the aggregate analysis result is output.

7. The method according to any one of claims 1 to 3, characterized in that: The step of binding and storing the inline information with the collected data of the event link includes: Writing the inline information into a private frame of the code stream of the collected data of the event link, and saving the code stream with the inline information written therein; or, Store the collected data of the event link to the hard disk, and write the inline information as additional information of the collected data of the event link to the hard disk; or, The collected data of the event link is stored to obtain a storage location, and a corresponding relationship between the obtained storage location and the inline information is stored in a database or memory.

8. A data retrieval method for an event, characterized in that: Applied to an aggregation service device; the method comprises: Receiving a search keyword for a target event input by a user in a search interface of the aggregation service device; wherein the search keyword includes identification information of any task object; any task object is an object indicated for processing by an event task represented by the target event; Sending a search instruction carrying the search keyword to a video recording device, so that the video recording device, in response to receiving the search instruction, screens each inline information matching the search keyword carried in the search instruction and the collected data stored and bound with each screened inline information based on the inline information and collected data of the event link of the target event that are currently bound and stored, and feeds back each screened inline information and the bound collected data to the aggregation service device; wherein the video recording device stores the inline information and collected data of the event link of the target event in a bound manner according to the method described in any one of claims 1 to 7; Receive each inline information fed back by the video recording device and the bound collected data; The aggregate information corresponding to the search keyword and including each inline information fed back by the video recording device and the bound collected data is output in the form of a workflow of the target event.

9. The method according to claim 8, characterized in that The method further comprises: In response to the event information summary instruction about the target keyword, the description information containing the target keyword is retrieved from the description information corresponding to each event link reported by the recording device currently saved; wherein the target keyword includes the object identifier of any task object or the link identifier of any event link; Based on the filtered description information, construct an event information summary result for the target keyword; and / or, After constructing the event information summary result for the target keyword based on the screened description information, the method further includes: Based on the constructed event information summary result, data analysis of specified analysis dimensions is performed to obtain analysis results; wherein the specified analysis dimensions include analysis dimensions for event links, analysis dimensions for objects, or analysis dimensions for accuracy of event information.

10. A data retrieval method for an event, characterized in that: Applied to a video recording device, the method comprises: Receive a search instruction carrying a search keyword; wherein the search instruction is a search keyword for a target event input by a user in a user interface of an aggregation service device; wherein the search keyword includes identification information of any task object; any task object is an object indicated for processing by an event task represented by the target event; based on the inline information and collected data of the event link of the target event that are currently bound and stored, filter each inline information that matches the search keyword carried in the search instruction and the collected data that is bound and stored with each filtered inline information; wherein the video recording device binds and stores the inline information of the event link of the target event with the collected data according to the method described in any one of claims 1 to 7; Feedback the screened inline information and bound collected data to the aggregation service device, so that the aggregation service device outputs the aggregated information corresponding to the search keyword and including the inline information and bound collected data fed back by the video recording device.

11. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, for implementing the method described in any one of claims 1 to 7, the method described in any one of claims 8 to 9, and / or the method described in claim 10 when executing a program stored in a memory.

Images