CN116614657A - Event information sending method, device, system and electronic equipment - Google Patents

Abstract

The present application provides a method, device, system, and electronic device for sending event information. A specific implementation of the method includes: for any type of event information, determining the event attribute information corresponding to the event information, and according to the event Attribute information, configure the weight corresponding to the event information; determine the sending order of various event information according to the order of the weight, and send the various event information to the publishing server according to the sending order when the sending cycle arrives; wherein, The sending period is set based on the publishing frequency of the publishing server. The method can reasonably send event information while limiting the publishing frequency of the publishing server, so as to meet actual needs.

Description

Event information sending method, device, system and electronic equipment

technical field

The present application relates to the field of information processing, in particular, to a method, device, system and electronic equipment for sending event information.

Background technique

At present, cameras are deployed in many scenes, and these cameras will trigger many events during the working process (for example, detecting a moving object in the screen), and the cameras can record the triggered event information (such as event trigger time, event trigger location etc.), and send it to users who are concerned about these events (for example, users who have a specific APP installed on their mobile phones) at an appropriate time, so that users can be informed of the occurrence of these events and take corresponding measures.

When the camera records multiple event information, it usually records the trigger time of the event, and then sends the corresponding event information sequentially according to the order of the event trigger time. However, in some application scenarios, this method of sending events according to the sequence of event triggering times cannot meet actual needs.

Contents of the invention

The purpose of the embodiments of the present application is to provide a method, device, system and electronic equipment for sending event information, so as to reasonably send event information while limiting the publishing frequency of the publishing server, so as to meet actual needs.

In the first aspect, the embodiment of the present application provides a method for sending event information. The method includes: for any type of event information, determining the event attribute information corresponding to the event information, and configuring the event attribute information according to the event attribute information. The weight corresponding to the event information; determine the sending order of various event information according to the order of the weight, and when the sending cycle arrives, send the various event information to the publishing server according to the sending order; wherein, the sending cycle is based on The publishing frequency setting of the publishing server. In this way, the sending order of each type of event information can be determined more flexibly according to the weight, and then the event information can be sent more reasonably while limiting the publishing frequency of the publishing server, which meets the actual demand.

Optionally, the event information of any type includes independent information of an independent event, the independent information includes event trigger time, and the event attribute information includes event status, and the event information for any type, Determining the event attribute information corresponding to the event information, and configuring the weight corresponding to the event information according to the event attribute information, including: using the same time counting rule to count the current time and the event trigger time; for the independent information , when the interval between the current time and the event trigger time is greater than a duration threshold, determine that the independent event is in the end state; if the independent event is in the end state, increase the weight corresponding to the independent information. In this way, the event reporting device can make no deviation between the triggering times of various events through the same time counting rule, so that it is convenient to configure an appropriate weight for each independent event based on the same time standard, and then can more reasonably determine the sending sequence.

Optionally, the event information of any type includes independent information of multiple independent events, the independent information includes event trigger time, and the event attribute information includes event status, and the event information for any type , determining the event attribute information corresponding to the event information, and configuring the weight corresponding to the event information according to the event attribute information, including: using the same time counting rule to count the current time and the event trigger time; for any For independent information, when the current time and the time interval between event triggering times are greater than the duration threshold, it is determined that the independent event is in the end state; when the independent event is in the end state, the weight corresponding to the independent information is increased. In this way, the event reporting device can make no deviation between the triggering times of various events through the same time counting rule, so that it is convenient to configure an appropriate weight for each independent event based on the same time standard, and then can more reasonably determine the sending sequence.

Optionally, for any type of event information, determining the event attribute information corresponding to the event information, and configuring the weight corresponding to the event information according to the event attribute information, further includes: In the case of , if current independent information is received, merge the current independent information with the historical independent information; accumulate the weights corresponding to the historical independent information and the current independent information; and The order of the weights determines the sending order of various event information, and when the sending period arrives, sends the various event information to the publishing server according to the sending order, including: determining the various event information according to the weight order of the merged information , and when the sending period arrives, send the combined information to the publishing server according to the sending order. In this way, multiple independent information belonging to the same type can be combined to reduce the number of event information to be sent, which in turn can reduce the processing pressure on the event reporting device and the publishing server, and shorten the same type of event to a certain extent. How long the message was sent.

Optionally, the event attribute information includes new event information or common event information, and for any type of event information, determine the event attribute information corresponding to the event information, and configure the event attribute information according to the event attribute information. The weight corresponding to the event information includes: for any type of event information, if the event information is the first detected information of this type, then determine that the event attribute information includes new event information, and increase the weight corresponding to the event information; if If the event information is not the type of information detected for the first time, it is determined that the event attribute information includes common event information, and the weight corresponding to the event information remains unchanged. In this way, by dividing each event information into new event information and common event information, the weight of the detected new type of event can be increased to increase its sending priority, and then it can be sent to the publishing server as soon as possible.

Optionally, for any type of event information, determining the event attribute information corresponding to the event information, and configuring the weight corresponding to the event information according to the event attribute information, further includes: keeping the event information corresponding to Under the condition that the weight remains unchanged, if the event information meets the emergency event information requirement, the weight corresponding to the event information is increased. In this way, corresponding weights can be adaptively configured according to the urgency of common event information, and then a more reasonable sending order can be obtained, so that more urgent common events can be sent to the publishing server faster.

Optionally, the emergency event information requirement includes: the event information is information that fails to be sent. In this way, the failed event information can be sent to the publisher as soon as possible.

In the second aspect, the embodiment of the present application provides a method for sending event information applied to a network video recorder. The method includes: receiving any type of event information sent by multiple camera devices; type of event information, the event information is sent according to the method described in the first aspect. In this way, since the event sending method is applied to the network video recorder, the event information sent by multiple camera devices can be managed as a whole, and then the event information sent by each camera device can be sent under the condition that the publishing frequency of the publishing server is limited. The sequence is more reasonable and meets the actual needs.

In the third aspect, the embodiment of the present application provides an event information sending device, which includes: a weight configuration module, configured to determine the event attribute information corresponding to the event information for any type of event information, and according to the The event attribute information configures the weight corresponding to the event information; the information sending module is used to determine the sending order of various event information according to the order of the weight, and when the sending cycle arrives, send the said sending order to the publishing server according to the sending order Various types of event information; wherein, the sending period is set based on the publishing frequency of the publishing server. In this way, the sending order of each type of event information can be determined more flexibly according to the weight, and then the event information can be sent more reasonably while limiting the publishing frequency of the publishing server, which meets the actual demand.

In a fourth aspect, the embodiment of the present application provides an event information sending device applied to a network video recorder, the device includes: a receiving module, configured to receive any type of event information sent by any camera device; For any type of event information sent by any imaging device, the event information is sent according to the method described in the first aspect. In this way, since the event sending device is applied to a network video recorder, the event information sent by multiple camera equipment can be managed in an overall manner, and then the event information sent by each camera equipment can be sent under the condition that the publishing frequency of the publishing server is limited. The sequence is more reasonable and meets the actual needs.

In the fifth aspect, the embodiment of the present application provides an event information sending system, the system includes: an event reporting device, configured to determine the event attribute information corresponding to the event information for any type of event information, and according to the Event attribute information, configuring the weight corresponding to the event information; and determining the sending order of various event information according to the order of the weight, and sending the various event information to the publishing server according to the sending order when the sending cycle arrives; Wherein, the sending period is set based on the publishing frequency of the publishing server; the publishing server is used to receive the various event information. In this way, the sending order of each type of event information can be determined more flexibly according to the weight, and then the event information can be sent more reasonably while limiting the publishing frequency of the publishing server, which meets the actual demand.

In the sixth aspect, the embodiment of the present application provides an electronic device, including a processor and a memory, the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the operation is as described above The steps in the method provided by the first aspect or the second aspect.

In the seventh aspect, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it runs as in the method provided in the first or second aspect above. step.

Other features and advantages of the present application will be set forth in the ensuing description and, in part, will be apparent from the description, or can be learned by practicing the embodiments of the present application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings that need to be used in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application, so It should not be regarded as a limitation on the scope, and those skilled in the art can also obtain other related drawings according to these drawings without creative work.

FIG. 1 is an application scenario of the event processing method provided by the embodiment of the present application;

FIG. 2 is a flow chart of a method for sending event information provided in an embodiment of the present application;

FIG. 3 is a flow chart of marking after an event is triggered according to an embodiment of the present application;

FIG. 4 is a flow chart of a method for sending event information applied to a network video recorder provided in an embodiment of the present application;

FIG. 5 is a structural block diagram of an event information sending device provided in an embodiment of the present application;

FIG. 6 is a structural block diagram of an event information device applied to a network video recorder provided by an embodiment of the present application;

FIG. 7 is a structural block diagram of an event information sending system provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of an electronic device for executing a method for sending event information provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all of them. The components of the embodiments of the application generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Accordingly, the following detailed description of the embodiments of the application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative efforts belong to the scope of protection of the present application.

It should be noted that like numerals and letters denote similar items in the following figures, therefore, once an item is defined in one figure, it does not require further definition and explanation in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second" and the like are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

It should be noted that, in the case of no conflict, the embodiments in the present application or the technical features in the embodiments may be combined.

In related technologies, there is a problem that events are sent according to the sequence of event trigger time, which cannot meet the actual needs; in order to solve this problem, this application provides a method for sending event information; further, through each type of event information Corresponding to the event attribute information, the weight corresponding to the event information is set, and then the sending sequence of each type of event information can be determined according to the weight. The sending order determined based on the foregoing weights is more flexible, and thus more satisfying actual needs.

In some application scenarios, the above method for sending event information may be applied to an event reporting device. The above-mentioned event reporting device may include a camera device or a network video recorder. The aforementioned imaging device may include, for example, a video camera, a camera, and other devices that substantially have an imaging function. The aforementioned Network Video Recorder (NVR for short) may receive event information sent by one or more camera devices.

If the above event information sending method is applied to the camera device, the camera device can set the weight corresponding to any type of event information it collects according to the event attribute information, and then determine the sending order of each event information according to the weight.

If the above method for sending event information is applied to a network video recorder, then the network video recorder can receive event information sent by one or more camera devices, and can, for each type of event information sent by each camera device, according to its event attributes The information sets the weight corresponding to each type of event information, and then the sending order of each type of event information can be determined according to the weight.

It should be noted that when the above event information sending method is applied to the event reporting device, it can be used as an independent processing module to process the event information detected by the camera, or process the event information received by the network video recorder to A sending sequence corresponding to each event information is determined.

The defects in the solutions in the above related technologies are all the results obtained by the inventor after practice and careful research. Therefore, the discovery process of the above problems and the solutions to the above problems proposed by the embodiments of the present invention below, All should be the inventor's contribution to the invention during the process of the invention.

Please refer to FIG. 1 , which shows a flowchart of a method for sending event information provided by an embodiment of the present application. As shown in FIG. 1 , the method for sending event information includes the following steps 201 to 202 .

Step 201, for any type of event information, determine the event attribute information corresponding to the event information, and configure the weight corresponding to the event information according to the event attribute information;

The above event information may include, for example, event image, event description text, event type, event trigger time, event trigger location and other information related to the event. The above-mentioned event types may include, for example, motion detection types, toxic gas detection types, area intrusion detection types, boundary-crossing detection types, passenger flow counting types, and other types that can substantially use camera equipment to achieve corresponding purposes. The above event triggering time may be regarded as the time when event information is detected or received.

The above-mentioned event attribute information may include, for example, event urgency, event delay time, whether the event is a discardable event, and other attribute information that may substantially affect the sending sequence.

In some application scenarios, the event reporting device may determine the corresponding event attribute information for any type of event information. For example, the event reporting device can determine that the event attribute information corresponding to the event information A is an event that cannot be delayed for the event information A of the toxic gas detection type; It is determined that the event attribute information corresponding to the event information B is a delayable event.

After the event reporting device determines the event attribute information corresponding to various types of event information, it can set the corresponding weight according to the event attribute information. For example, for the above event information A, the event reporting device may configure a higher weight for it; for the above event information B, the event reporting device may configure a lower weight for it.

It should be noted that the above weights can be represented by specific numerical values such as weight value 8, weight value 16 or weight value 16, or by percentage values such as weight 1%, weight 2%, weight 3%, etc., which is not limited in this application .

In some application scenarios, the event reporting device can, for example, obtain various possible event attribute information in advance, and then set the corresponding relationship between event attribute information and weight, so as to use the corresponding relationship to quickly configure various types of event information. more reasonable weight. The above correspondence may include, for example: Delayable event information-increase weight value 0, non-delayable event information-increase weight value 8, discardable event information-increase weight value 0, non-discardable event information-increase weight value 2%, etc. .

Step 202, determine the sending order of various event information according to the order of weight, and send the various event information to the publishing server according to the sending order when the sending cycle arrives; wherein, the sending cycle is based on the publishing The publishing frequency setting for the server.

In some application scenarios, the event reporting device may determine the order of sending event information according to the order of weight. For example, the event reporting device may arrange various event information in descending order according to weight, and then determine the sending priority of various event information according to the order of arrangement. In these application scenarios, for multiple event information of the same type, for example, the respective sending priorities can be determined by the event triggering time corresponding to each event; the respective sending priorities can also be determined by the event triggering location corresponding to each event, There is no limitation here.

After the event reporting device determines the sending order, it can send various event information to the publishing server according to the sending order when the sending period arrives. The above publishing server is also a server that sends event information to users.

In some application scenarios, after the event reporting device obtains the event information collected by the camera device, it can send it to the publishing server, so that the publishing server can send it to users who are concerned about these events. These application scenarios may include, for example, the scenario shown in FIG. 1 .

As shown in Figure 1, this scenario uses a publish/subscribe architecture to implement the process of the event reporting device sending event information to the user. Wherein, the participants may include a mobile phone 101, a server 102, and a camera 103, wherein the server 102 may include a registration server and a publishing server, the two may be two servers, or the same server may integrate two functions of registration and publishing , and there may be one or more cameras 103 . The working process of these parties is briefly described as follows:

Processes 1-2: The APP on the mobile phone 101, as a subscriber, registers with the registration server through the Internet. The registration parameters include the APP's identity token (Token), the identity token (ID) corresponding to the camera to be subscribed, and communication-related information. Among them, the Token can be the unique mark of the APP, and a different Token will be generated every time the APP is installed, and the ID is the unique mark of the camera.

The internal processing process of the camera 103 can be: the camera 103 will trigger an event according to its built-in logic during work (for example, if a moving object is detected in the picture, then trigger a motion detection event), the camera 103 can trigger the event Put them into the buffer in the memory, and the sending thread in the camera 103 sends the events in the buffer according to the interaction logic with the publishing server.

Processes 3-4: The camera 103, as the publisher, publishes a notification message to the publishing server, and the notification message carries the camera ID, event information, and the like.

The internal processing process of the server 102 may be as follows: the publishing server obtains the Token and communication information of all subscribers who have subscribed to this ID from the registration server according to the camera ID carried in the message.

Process 5-6: The publishing server publishes a notification message to all subscribers who have subscribed to the ID according to the communication information, and the message carries event information, etc.

The above-mentioned sending period may be regarded as an opportunity for the event reporting device to send event information. It can be set according to the publishing frequency of the publishing server. The above publishing frequency can be regarded as the frequency at which the publishing server sends event information to the user. For example, the publishing server can send 2, 3, 5, etc. event information to the user per second.

In some application scenarios, the publishing server may inform the event reporting device of the frequency (that is, the publishing frequency) of sending event information to the user in advance, and the event reporting device may set the sending period according to the publishing frequency. For example, the sending period can be the same as the publishing frequency. For example, if the publishing server sends 1 or 2 event information to the user per second, the sending period may be 1 second, and the event reporting device may send 1 or 2 event information to the publishing server per second. In addition, the sending cycle may also be different from the publishing frequency, but the amount of event information sent within the sending cycle should not exceed the publishing frequency of the publishing server. For example, if the publishing server sends 1 or 2 event information to the user every second, the sending period may be 2 seconds, and the event reporting device may send 1 or 2 event information to the publishing server every 2 seconds.

In the related art, when the publishing frequency of the publishing server is limited, if there is too much event information to be sent to the user, the frequency of publishing these event information will exceed the publishing frequency of the publishing server. If the event information is sent sequentially in the order of the event trigger time, it may take a long time for the event information to be sent, or it may be discarded directly, and the user needs to wait for a long time to learn about the event. information, or cannot obtain these event information. Therefore, the actual demand cannot be met.

In this embodiment, for any type of event information, the weight corresponding to the event information can be reasonably set according to its event attribute information, and then the sending order of each type of event information can be determined more flexibly according to the weight, and then the When the publishing frequency of the publishing server is limited, the event information is sent to the publishing server sequentially according to the sending order, so that the event information can be sent more reasonably, which meets the actual demand. To a certain extent, the situation of waiting for a long time or discarding event information is also improved.

In addition, this embodiment determines the sending order from the event reporting device to the publishing server based on the event attribute information, so that when the sending frequency of the publishing server sending event information to the user is limited, the actual demand can be met. In this way, for different publishing servers, the event reporting device can adaptively set the sending period according to its publishing frequency, and then the event reporting device can cooperate with different publishing servers, expanding the use range of the event reporting device.

In some optional implementation manners, the event information of any type includes independent information of an independent event, the independent information includes event trigger time, and the event attribute information includes event status.

In some application scenarios, each type of event information may only include one event, which is the above-mentioned independent event, and information corresponding to the event is also the above-mentioned independent information. The above independent information may also include information such as event type, event trigger time, event trigger location and the like.

The above event states may include a start state and an end state. In some application scenarios, after an event is triggered, it can be considered as being in the start state. From the start state to the end state of the event information, it can be considered that the event information is continuously waiting to be sent, and after the corresponding waiting time is reached, it can be regarded as in the end state. The above waiting time can be regarded as a preset sending time, for example. If the event information is not sent within the waiting period, the event information may be determined to be in an end state.

In this way, for any type of event information described in the above step 201, determining the event attribute information corresponding to the event information, and configuring the weight corresponding to the event information according to the event attribute information may include the following substeps:

Sub-step 2011A, using the same time counting rule to count the current time and the trigger time of the event;

The above-mentioned same time counting rule can be regarded as the same time calculation rule. For example, the event reporting device may use the same counter for timing, or use multiple counters with the same time starting point and the same timing frequency for timing.

In some application scenarios, the event reporting device can use the same time counting rule to count the current time and the event trigger time. For example, it can use a counter to record the time, and then after the event is triggered, record the current time displayed by the counter when the event is triggered. For example, the counter can be incremented by 1 every second, and if event a is triggered when the counter shows "5", the trigger time of event a can be recorded as the 5th second. After 3 seconds, the current time is the 8th second, and the current event trigger time of the event a is the 5th second.

Sub-step 2012A, for the independent information, when the interval between the current time and the event trigger time is greater than the duration threshold, determine that the independent event is in the end state;

In some application scenarios, the event reporting device may determine the interval between the current time of the independent information and the event trigger time. For example, for the above event a, the event reporting device may determine that the interval between the 8th second of the current time and the 5th second of the event trigger time is 3 seconds.

Then, the event reporting device may determine whether the interval duration is greater than a duration threshold. The aforementioned duration threshold may include, for example, 30 seconds, 35 seconds, etc., during which the event information may be sent to the publishing server substantially. In these application scenarios, the duration threshold can be set based on experience, for example, or can be determined by the sending duration of historical event information of the same type that has been successfully sent, which is not limited here.

If the event reporting device determines that the interval time is greater than the time threshold, it may determine that the independent event is currently in an end state.

Sub-step 2013A, if the independent event is in the end state, increase the weight corresponding to the independent information.

When the event reporting device determines that the independent event is in an end state, it may increase its corresponding weight. That is, since the independent event is not sent within the preset sending duration, it needs to be sent as soon as possible, so the probability of its being sent is increased by increasing its corresponding weight.

In related technologies, when recording the event trigger time, it is usually recorded by a camera. In this way, the recorded event triggering times are not in the same timing standard due to different geographical locations of the cameras or different timing hardware installed. For example, if camera A is in the United States and camera B is in China, there is a time difference between the event triggering times recorded by the two cameras. Or, if camera A does not have a crystal oscillator, and camera B uses a crystal oscillator for timing, there is also a deviation in the event trigger time recorded by the two respectively. Therefore, when the camera sends event information based on the event triggering time recorded by itself, more event information will be accumulated in the publishing server, even exceeding its limited publishing frequency.

In this implementation, the event reporting device can use the same time counting rule so that there is no deviation between the triggering times of each event, so that it is convenient to configure an appropriate weight for each independent event based on the same time standard, and then more reasonably determine the sending time. order.

In some optional implementation manners, the event information of any type includes independent information of multiple independent events, the independent information includes event trigger time, and the event attribute information includes event status.

In some application scenarios, each type of event information may include multiple events, which are the aforementioned multiple independent events. Each independent event may include corresponding information such as event type, event trigger time, event trigger location and the like.

In this way, for any type of event information described in the above step 201, determining the event attribute information corresponding to the event information, and configuring the weight corresponding to the event information according to the event attribute information may include the following substeps:

Sub-step 2011B, using the same time counting rule to count the current time and the trigger time of the event;

Sub-step 2012B, for any independent information, when the interval between the current time and the event trigger time is greater than the duration threshold, determine that the independent event is in the end state;

Sub-step 2013B, when the independent event is in the end state, increase the weight corresponding to the independent information.

The implementation process of the above sub-step 2011B to sub-step 2013B and the technical effect obtained may be the same as or similar to the above-mentioned sub-step 2011A to sub-step 2013A, and will not be repeated here.

In some optional implementation manners, for any type of event information described in step 201 above, the event attribute information corresponding to the event information is determined, and the weight corresponding to the event information is configured according to the event attribute information , which can also include the following substeps:

Sub-step 2014B, if the historical independent information is not sent, if the current independent information is received, merge the current independent information with the historical independent information;

In some application scenarios, multiple event information of the same type may be triggered, and the multiple event information of the same type are also the above-mentioned multiple independent information. For example, if it is detected that someone enters the preset area, an area intrusion type event can be triggered, and one or more people may be detected entering the preset area at different times or at the same time, and then multiple events belonging to the area intrusion type event may be triggered. event. For example, event information C may be generated according to the detected event of someone entering the preset area at 1:01, and event information D may be generated based on the event detected at 1:02 of someone entering the preset area. The aforementioned preset area may include, for example, a construction area, a confidential office area, and the like.

In these application scenarios, the independent information in the starting state can be regarded as historical independent information. If it has not been sent, if new independent information is received, the new independent information can be regarded as current independent information . For example, if the above event information C is not sent at 1:02, it may be regarded as historical independent information, and the above event information D may be regarded as current independent information.

Then, the event reporting device can combine the current independent information with the historical independent information. For example, the above-mentioned event information C and the above-mentioned event information D may be combined into one event information.

It should be noted that when merging, the merging may be performed according to actual needs. That is, multiple independent information may be combined into one event information, or multiple independent information may be combined into two event information, which is not limited here.

In some application scenarios, an accumulator may be used to record the times of merging independent information. For example, after the above-mentioned event information C and event information D are merged, the accumulator can be increased by 1, and if new current independent information E is received, the accumulator can be increased by 1, and so on, and the times of merging independent information are recorded by the accumulator . In these application scenarios, the number of mergers recorded by the accumulator can also be regarded as the number of occurrences of this type of event currently detected.

Sub-step 2015B, accumulating weights corresponding to the historical independent information and the current independent information respectively.

In some application scenarios, after the event reporting device combines the historical independent information with the current independent information, it may accumulate weights corresponding to the two. That is to say, both historical independent information and current independent information may have increased weight due to the existence of other event attribute information (such as whether it can be delayed, whether it is already in the end state), and then the corresponding weights of the two can be accumulated to obtain The weight of the combined information.

In some application scenarios, if the weights configured for the same event attribute information of the same type are the same, the cumulative sum of the weights may be determined based on the number of merging times. For example, for the above-mentioned event information C and event information D, if the configured weight value is 8 when both are in the end state, the weight value can be multiplied by the number of times of merging, and then the weight accumulation sum of the merging information can be obtained .

In other application scenarios, if the weights configured for the same event attribute information of the same type are different, it is also possible to check whether the weight accumulation times are correct based on the number of merging times, and then check whether the weight accumulation sum is correct. For example, for the above-mentioned event information C and event information D, if the configured weights of the two are different due to the different event trigger locations, the accumulation times that are the same as the number of times of merging can be determined, and then the weight accumulation sum of the merging information can be obtained .

In this way, determining the sending order of various types of event information according to the order of the weights described in step 202 above, and sending the various types of event information to the publishing server according to the sending order when the sending cycle arrives may include: The order of the weights of the merged information determines the sending order of various event information, and when the sending period arrives, the merged information is sent to the publishing server according to the sending order.

After the event reporting device obtains the merged information, it can determine the sending order of various event information according to the order of the cumulative sum of weights, and then can send each merged information according to the determined sending order when the sending period arrives.

In this implementation, a plurality of independent information belonging to the same type can be combined to reduce the number of event information to be sent, thereby reducing the processing pressure of the event reporting device and the publishing server, and shortening the same time to a certain extent. The sending duration of each type of event information.

In addition, since a plurality of independent information can be combined, the event information may not be discarded, and the integrity of the event information is maintained to a certain extent.

In some optional implementation manners, the event attribute information includes new event information or common event information.

The above-mentioned new event information can be regarded as event information belonging to a new event type.

The above common events can be regarded as event information that does not belong to the new event type.

For example, when the event reporting device detects the event information M belonging to the motion detection type for the first time, the event information M may be regarded as new event information. If the event information N belonging to the motion detection type is detected when the event information M is not sent, since the event information N is not the first detected event information belonging to the motion detection type, it can be attributed to in ordinary events.

In this way, for any type of event information described in step 201 above, determine the event attribute information corresponding to the event information, and configure the weight corresponding to the event information according to the event attribute information, including:

First, for any type of event information, if the event information is the type of information detected for the first time, then determine that the event attribute information includes new event information, and increase the weight corresponding to the event information;

In some application scenarios, for any event information of any type, if the event information is the first detected event information of this type, it can be determined as new event information, and then its corresponding weight can be increased. For example, if it is detected that the above event information M is new event information, its corresponding weight value may be increased.

It should be noted that, for new event information of the same type, the added weights may be the same, so as to facilitate the overall management of event information by the event reporting device.

Then, if the event information is not the type of information detected for the first time, it is determined that the event attribute information includes common event information, and the weight corresponding to the event information remains unchanged.

For any event information of any type, if the event information is not the first detected event information of this type, it can be determined as ordinary event information, and then its corresponding weight will not be increased to keep its corresponding weight. Change. For example, if it is detected that the above event information N is common event information, its corresponding weight value may not be increased.

In this implementation, each event information is divided into new event information and common event information, and the weight of the detected new type of event can be increased to increase its sending priority, and then it can be sent to the publishing server as soon as possible.

In some optional implementation manners, for any type of event information described in step 201 above, the event attribute information corresponding to the event information is determined, and the weight corresponding to the event information is configured according to the event attribute information , further comprising: in the case of keeping the weight corresponding to the event information unchanged, if the event information meets the requirements of emergency event information, increasing the weight corresponding to the event information.

In some application scenarios, if the weight of the event information remains unchanged, it can be regarded as belonging to ordinary event information, and then it can be further judged whether the event information is an emergency event, so as to increase the corresponding weight through its urgency adaptability.

In these application scenarios, the event reporting device can determine whether the event information meets the emergency event information requirements. The emergency event information requirement can be set based on, for example, the following conditions: (1) Whether the type of the event information belongs to the type of toxic gas detection, area intrusion detection, etc. that may substantially cause large losses. In turn, emergency event information requirements can be set by event type. (2) Whether the type of the event information belongs to the type that needs to be sent within a relatively short period of time, and these types may include, for example, alarm types, fault types, and the like. Then, the emergency information request can be set through the waiting time.

In some optional implementation manners, the emergency event information requirement includes: the event information is information that fails to be sent.

In some application scenarios, the event reporting device may determine the event information that fails to be sent as emergency event information. That is, if a certain event information fails to be sent, it can be considered that it meets the emergency event information requirements. In these application scenarios, if a certain event information is sent successfully, it can be deleted from the stored buffer to save storage space.

After the event reporting device determines that certain event information meets the requirements of emergency event information, it can increase its corresponding weight, so as to increase the sending priority of the event information, and send it to the publishing server as soon as possible.

In this implementation, according to the urgency of common event information, corresponding weights can be adaptively configured for it, and then a more reasonable sending sequence is obtained, so that more urgent common events can be sent to the publishing server faster.

Those skilled in the art can understand that in the above-mentioned method of the specific embodiment, the writing order of each step does not imply a strict execution order and constitutes any limitation on the implementation process, and the specific execution order of each step should be based on its function and possible The inner logic is OK.

Then, when the event reporting device executes the method for sending event information including the above steps or sub-steps, it can mark corresponding information one by one when an event is triggered. In some application scenarios, for example, marking may be performed through the flow chart shown in FIG. 3 .

As shown in Figure 3, after an event is triggered, it can be judged whether it is a new event to judge whether the corresponding event information is new event information; if it is new event information, a buffer for storing the new event type can be created area for storing the new event information. Then it can be further judged whether it is an emergency event (for example, judging whether its event information meets the emergency event information requirements), if it is an emergency event, it can be marked such as "emergency send flag set", "new event flag set", " Accumulator is set to 0", "event status is set to start state", "mark counter value is event trigger time" and other information; if it is not an emergency event, it can be marked such as "emergency send flag set to 0", "new event flag set to 1" , "Set the accumulator to 0", "Set the event state to the start state", "The flag counter value is the event trigger time", etc.;

If the event is not a new event (that is, a common event), it can be further judged whether it is an emergency event (that is, whether its event information meets the emergency event information requirements). ", "Set the new event mark to 0", "Set the accumulator to 0", "Set the event state to the start state", "The value of the mark counter is the event trigger time", etc. If it is not an emergency event, you can mark things such as "set the emergency send flag to 0", "set the new event flag to 0", "set the accumulator to 0", "set the event state to the start state", "the value of the flag counter is the event trigger time" wait.

After the event reporting device marks the above information, it can be dropped into the buffer pool for management. In this way, since the corresponding event information is marked after the event is triggered, the corresponding event attribute information can be determined more conveniently.

Please refer to FIG. 4 , which shows a flowchart of a method for sending event information applied to a network video recorder provided by an embodiment of the present application. As shown in FIG. 4 , the event information sending method may include step 401 to step 403 .

Step 401, receiving any type of event information sent by multiple camera devices.

Step 402, for any type of event information sent by any camera device, determine the event attribute information corresponding to the event information, and configure the weight corresponding to the event information according to the event attribute information;

Step 403: Determine the sending order of various types of event information according to the order of weight, and send the various types of event information to the publishing server according to the sending order when the sending cycle arrives; wherein, the sending cycle is based on the publishing The publishing frequency setting for the server.

That is to say, after the network video recorder receives any type of event information sent by a plurality of camera devices, for each type of event information, the event information can be sent to the publisher according to the method of the embodiment shown in Figure 1 server.

The implementation process of the above-mentioned step 402 to sub-step 403 and the technical effect obtained may be the same as or similar to the above-mentioned sub-step 201 to sub-step 202, and will not be repeated here.

In this embodiment, since the event sending method is applied to the network video recorder, the event information sent by multiple camera devices can be managed in an overall manner, and then the event information sent by each camera device can be made under the condition that the publishing frequency of the publishing server is limited. The sending sequence of the event information is more reasonable, and then the event information can be sent more reasonably, which meets the actual demand. To a certain extent, the situation of waiting for a long time or discarding event information is also improved.

Please refer to FIG. 5 , which shows a structural block diagram of a device for sending event information provided by an embodiment of the present application. The device for sending event information may be a module, program segment or code on an electronic device. It should be understood that the device corresponds to the above-mentioned embodiment of the method in FIG. 2 , and can perform various steps involved in the embodiment of the method in FIG. 2 . The specific functions of the device can refer to the description above. To avoid repetition, detailed descriptions are appropriately omitted here.

Optionally, the above event information sending device includes a weight configuration module 501 and an information sending module 502 . Among them, the weight configuration module 501 is used to determine the event attribute information corresponding to the event information for any type of event information, and configure the corresponding weight of the event information according to the event attribute information; the information sending module 502 uses Determine the sending order of various event information according to the order of weight, and send the various event information to the publishing server according to the sending order when the sending period arrives; wherein, the sending period is based on the publishing server's Publish frequency settings.

Optionally, the above-mentioned information sending module 502 may be divided into a determining module and a sending sub-module. Wherein, the determining module can be used to determine the sending order of various event information according to the order of weight, and the sending sub-module can be used to send the various event information to the publishing server according to the sending order when the sending period arrives. In this way, after it is divided into the determination module and the sending sub-module, when the event information sending device sets the sending cycle based on the publishing frequency of the publishing server, it can only modify the corresponding sending cycle parameter in the sending sub-module, which is more convenient for positioning Modify the location.

Optionally, the event information of any type includes independent information of an independent event, the independent information includes event trigger time, and the event attribute information includes event status, and the weight configuration module 501 is further configured to: use the same Time counting rules, counting the current time and the event trigger time; for the independent information, when the interval between the current time and the event trigger time is greater than the duration threshold, it is determined that the independent event is in the end state; When the event is in the end state, increase the weight corresponding to the independent information.

Optionally, the event information of any type includes independent information of multiple independent events, the independent information includes event trigger time, and the event attribute information includes event status, and the weight configuration module 501 is further configured to: utilize The same time counting rule, counting the current time and the event trigger time; for any independent information, when the interval between the current time and the event trigger time is greater than the duration threshold, it is determined that the independent event is in the end state; When the event is in the end state, increase the weight corresponding to the independent information.

Optionally, the weight configuration module 501 is further configured to: combine the current independent information with the historical independent information if the current independent information is received if the historical independent information is not sent; The historical independent information and the weights corresponding to the current independent information are accumulated; and the information sending module 502 is further configured to: determine the sending order of various event information according to the weight order of the merged information, and when the sending period arrives, Send the combined information to the publishing server according to the sending sequence.

Optionally, the event attribute information includes new event information or common event information, and the weight configuration module 501 is further configured to: for any type of event information, if the event information is the first detected information of this type, Then determine that the event attribute information includes new event information, and increase the weight corresponding to the event information; if the event information is not the type of information detected for the first time, then determine that the event attribute information includes common event information, and keep the event information corresponding to weight remains unchanged.

Optionally, the weight configuration module 501 is further configured to: increase the weight corresponding to the event information if the event information meets the emergency event information requirements while keeping the weight corresponding to the event information unchanged.

Optionally, the emergency event information requirement includes: the event information is information that fails to be sent.

It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working process of the device described above can refer to the corresponding process in the foregoing method embodiment, and the description will not be repeated here.

Please refer to FIG. 6 , which shows a structural block diagram of an event information sending device applied to a network video recorder provided by an embodiment of the present application. The event information sending device may be a module, program segment or code on an electronic device. It should be understood that the device corresponds to the above-mentioned method embodiment in FIG. 4 , and can perform various steps involved in the method embodiment in FIG. 4 . The specific functions of the device can refer to the description above. To avoid repetition, detailed descriptions are appropriately omitted here.

Optionally, the above event information sending device includes a receiving module 601 and a sending module 602 . Wherein, the receiving module 601 is configured to receive any type of event information sent by any camera device;

The sending module 602 is configured to send the event information according to the method of the embodiment shown in FIG. 1 for any type of event information sent by any camera device.

It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working process of the device described above can refer to the corresponding process in the foregoing method embodiment, and the description will not be repeated here.

Please refer to FIG. 7 , which shows a structural block diagram of an event information sending system provided by an embodiment of the present application. The event information sending system may include an event reporting device and a publishing server. It should be understood that the event reporting device and the publishing server correspond to the above-mentioned embodiment of the method in Figure 2, and can perform the various steps involved in the embodiment of the method in Figure 2. The specific functions of the event reporting device can refer to the description above. To avoid repetition, here Detailed description is omitted here.

Optionally, the event information sending system includes an event reporting device 701 and a publishing server 702 . Wherein, the event reporting device 701 is configured to, for any type of event information, determine the event attribute information corresponding to the event information, and configure the weight corresponding to the event information according to the event attribute information; and according to the order of weight Determine the sending order of various event information, and when the sending period arrives, send the various event information to the publishing server according to the sending order; wherein, the sending period is set based on the publishing frequency of the publishing server; the publishing server 702, configured to receive the various types of event information.

It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working process of the system described above can refer to the corresponding process in the foregoing method embodiments, and the description will not be repeated here.

Please refer to FIG. 8. FIG. 8 is a schematic structural diagram of an electronic device for executing a method for sending event information provided by an embodiment of the present application. The electronic device may include: at least one processor 801, such as a CPU, and at least one communication interface 802 , at least one memory 803 and at least one communication bus 804 . Wherein, the communication bus 804 is used to realize the direct connection and communication of these components. Wherein, the communication interface 802 of the device in the embodiment of the present application is used for signaling or data communication with other node devices. The memory 803 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory 803 may also be at least one storage device located far away from the aforementioned processor. Computer-readable instructions are stored in the memory 803 , and when the computer-readable instructions are executed by the processor 801 , the electronic device can execute the above-mentioned method process shown in FIG. 2 or FIG. 4 .

It can be understood that the structure shown in FIG. 8 is only for illustration, and the electronic device may also include more or less components than those shown in FIG. 8 , or have a configuration different from that shown in FIG. 8 . Each component shown in FIG. 8 may be implemented by hardware, software or a combination thereof.

An embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the method performed by the electronic device in the method embodiment shown in FIG. 2 or FIG. 4 can be executed. process.

An embodiment of the present application provides a computer program product, the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program includes program instructions, and when the program instructions are executed by a computer, The computer can execute the methods provided by the above method embodiments. For example, the method may include: for any type of event information, determining the event attribute information corresponding to the event information, and configuring the event according to the event attribute information. The weight corresponding to the information; determine the sending order of various event information according to the order of the weight, and send the various event information to the publishing server according to the sending order when the sending cycle arrives; wherein, the sending cycle is based on the The publishing frequency setting of the publishing server.

In the embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

In addition, a unit described as a separate component may or may not be physically separated, and a component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Furthermore, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

In this document, relational terms such as first and second etc. are used only to distinguish one entity or operation from another without necessarily requiring or implying any such relationship between these entities or operations. Actual relationship or sequence.

The above descriptions are only the embodiments of the present application, and are not intended to limit the protection scope of the present application. For those skilled in the art, various modifications and changes may be made to the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims (13)

1. An event information transmission method, characterized in that the method comprises:

determining event attribute information corresponding to the event information aiming at any type of event information, and configuring weight corresponding to the event information according to the event attribute information;

determining the sending sequence of various event information according to the weight sequence, and sending the various event information to a release server according to the sending sequence when a sending period arrives; wherein the transmission period is set based on a distribution frequency of the distribution server.

2. The method of claim 1, wherein the event information of any type comprises independent information of an independent event, the independent information comprises event trigger time, and the event attribute information comprises event status, and

the determining the event attribute information corresponding to the event information for any type of event information, and configuring the weight corresponding to the event information according to the event attribute information comprises the following steps:

counting the current time and the event triggering time by using the same time counting rule;

for the independent information, when the interval time length of the current time and the event triggering time is larger than a time length threshold value, determining that the independent event is in an ending state;

and under the condition that the independent event is in an ending state, increasing the weight corresponding to the independent information.

3. The method of claim 1, wherein the event information of any type comprises independent information of a plurality of independent events, the independent information comprises event trigger time, and the event attribute information comprises event status, and

the determining the event attribute information corresponding to the event information for any type of event information, and configuring the weight corresponding to the event information according to the event attribute information comprises the following steps:

Counting the current time and the event triggering time by using the same time counting rule;

for any independent information, when the time interval of the current time and the event triggering time is longer than a time length threshold value, determining that the independent event is in an ending state;

and increasing the weight corresponding to the independent information under the condition that the independent event is in the ending state.

4. The method of claim 3, wherein for any type of event information, determining event attribute information corresponding to the event information, and configuring weights corresponding to the event information according to the event attribute information, further comprises:

under the condition that the history independent information is not sent, if the current independent information is received, combining the current independent information with the history independent information;

accumulating weights corresponding to the history independent information and the current independent information respectively; and

the method for determining the sending sequence of various event information according to the order of the weights, and sending the various event information to a release server according to the sending sequence when a sending period arrives comprises the following steps:

and determining the sending sequence of various event information according to the weight sequence of the merging information, and sending the merging information to a release server according to the sending sequence when the sending period arrives.

5. The method according to any one of claims 1 to 4, wherein the event attribute information includes new event information or general event information, and

the determining the event attribute information corresponding to the event information for any type of event information, and configuring the weight corresponding to the event information according to the event attribute information comprises the following steps:

for any type of event information, if the event information is the type of information detected for the first time, determining that the event attribute information comprises new event information, and increasing the weight corresponding to the event information;

if the event information is not the type information detected for the first time, determining that the event attribute information comprises common event information, and keeping the weight corresponding to the event information unchanged.

6. The method according to claim 5, wherein for any type of event information, determining event attribute information corresponding to the event information, and configuring weights corresponding to the event information according to the event attribute information, further comprises:

under the condition that the weight corresponding to the event information is kept unchanged, if the event information meets the emergency event information requirement, the weight corresponding to the event information is increased.

7. The method of claim 6, wherein the emergency information requirement comprises: the event information is information of transmission failure.

8. An event information transmitting method, which is applied to a network video recorder, comprising:

receiving event information of any type sent by a plurality of camera devices;

event information of any type transmitted by any image capturing apparatus is transmitted according to the method as claimed in any one of claims 1 to 7.

9. An event information transmitting apparatus, characterized in that the apparatus comprises:

the weight configuration module is used for determining event attribute information corresponding to the event information aiming at any type of event information, and configuring weight corresponding to the event information according to the event attribute information;

the information sending module is used for determining the sending sequence of various event information according to the sequence of the weight, and sending the various event information to the release server according to the sending sequence when the sending period arrives; wherein the transmission period is set based on a distribution frequency of the distribution server.

10. An event information transmitting apparatus, applied to a network video recorder, comprising:

A receiving module, configured to receive any type of event information sent by any one of the image capturing apparatuses;

a transmission module configured to transmit event information of any type transmitted by any one of the image capturing apparatuses according to the method as claimed in any one of claims 1 to 7.

11. An event information transmission system, comprising:

event reporting equipment, configured to determine event attribute information corresponding to event information according to any type of event information, and configure weight corresponding to the event information according to the event attribute information; and

determining the sending sequence of various event information according to the weight sequence, and sending the various event information to a release server according to the sending sequence when a sending period arrives; wherein the transmission period is set based on the release frequency of the release server;

and the release server is used for receiving the various event information.

12. An electronic device comprising a processor and a memory storing computer readable instructions that, when executed by the processor, perform the method of any of claims 1-7 or 8.

13. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, performs the method according to any of claims 1-7 or 8.