CN112509296B - Alarm pushing method and device, electronic equipment and machine-readable storage medium - Google Patents
Alarm pushing method and device, electronic equipment and machine-readable storage medium Download PDFInfo
- Publication number
- CN112509296B CN112509296B CN202011246674.1A CN202011246674A CN112509296B CN 112509296 B CN112509296 B CN 112509296B CN 202011246674 A CN202011246674 A CN 202011246674A CN 112509296 B CN112509296 B CN 112509296B
- Authority
- CN
- China
- Prior art keywords
- monitoring point
- client
- point device
- alarm
- alarm information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
- H04N7/181—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a plurality of remote sources
Abstract
The application provides an alarm pushing method, an alarm pushing device, electronic equipment and a machine-readable storage medium, wherein the method comprises the following steps: when an alarm event is detected, detecting whether the equipment is in a preview state; and when the equipment is in a preview state, pushing alarm information to the first CS client. The method can realize the pushing of the alarm information, reduce the cost of the alarm pushing and improve the reliability of the alarm pushing.
Description
Technical Field
The present application relates to the field of video monitoring technologies, and in particular, to an alarm pushing method and apparatus, an electronic device, and a machine-readable storage medium.
Background
Real-time alarming is often used in the monitoring industry, and the traditional alarming pushing scheme is that alarming information is pushed to an alarming server through equipment, and the alarming server pushes the alarming information to a CS client.
However, practice shows that the traditional alarm pushing scheme needs to deploy an alarm server, the scheme implementation cost is high, if the alarm server is down, the pushing cannot be completed by the alarm, and the reliability of the alarm pushing is relatively low.
Disclosure of Invention
In view of this, the present application provides an alarm pushing method, an alarm pushing apparatus, an electronic device, and a machine-readable storage medium.
According to a first aspect of the embodiments of the present application, an alarm pushing method is provided, which is applied to a first monitoring point device, and the method includes:
when an alarm event is detected, detecting whether the equipment is in a preview state;
when the equipment is in a preview state, pushing alarm information to a first CS client; the first CS client is a CS client which previews the first monitoring point equipment at present.
According to a second aspect of the embodiments of the present application, there is provided an alarm pushing apparatus, which is applied to a first monitoring point device, the apparatus including:
the detection unit is used for detecting whether the equipment is in a preview state or not when the alarm event is detected;
the pushing unit is used for pushing alarm information to the first CS client when the equipment is in a preview state; the first CS client is a CS client which previews the first monitoring point equipment at present.
According to a third aspect of the embodiments of the present application, there is provided an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;
A memory for storing a computer program;
and the processor is used for realizing the alarm pushing method in the first aspect when executing the program stored in the memory.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium having stored therein a computer program, which when executed by a processor, implements the alarm push method of the first aspect.
According to the alarm pushing method, when an alarm event is detected, whether the equipment is in a preview state or not is detected; when the equipment is in a preview state, the alarm information is pushed to the CS client which previews the equipment at present, under the condition that an alarm server is not required to be deployed, the pushing of the alarm information is realized, the cost of the alarm pushing is reduced, and the reliability of the alarm pushing is improved.
Drawings
FIG. 1 is a flow diagram illustrating an alarm push method according to an exemplary embodiment of the present application;
FIG. 2 is a schematic flow chart diagram illustrating another method of alert pushing according to yet another exemplary embodiment of the present application;
FIG. 3 is a block diagram illustrating an architecture of a specific application scenario according to an exemplary embodiment of the present application;
FIG. 4 is a flow diagram illustrating an alarm push method according to an exemplary embodiment of the present application;
FIG. 5 is a schematic diagram illustrating an alarm pushing device according to an exemplary embodiment of the present application;
FIG. 6 is a schematic diagram of another alarm pushing device shown in another exemplary embodiment of the present application;
fig. 7 is a schematic diagram of a hardware structure of an electronic device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
In order to make the technical solutions provided in the embodiments of the present application better understood and make the above objects, features and advantages of the embodiments of the present application more comprehensible, the technical solutions in the embodiments of the present application are described in further detail below with reference to the accompanying drawings.
Referring to fig. 1, a flow diagram of an alarm pushing method provided in an embodiment of the present application is shown, where the alarm pushing method may be applied to any monitoring point device (referred to as a first monitoring point device herein), and as shown in fig. 1, the alarm pushing method may include the following steps:
it should be noted that, unless otherwise specified, all the monitoring point devices mentioned in the embodiment of the present application refer to monitoring point devices that support the alarm push scheme provided in the embodiment of the present application, and the following description of the embodiment of the present application is not repeated.
And step S100, when the alarm event is detected, detecting whether the equipment is in a preview state.
In the embodiment of the application, when the first monitoring point device detects an alarm event, whether the device is in a preview state or not can be detected.
For example, the first monitoring point device may detect whether the device is in a preview state by:
When the device is in the stream fetching/stream pushing state, it is determined that the device is in the preview state or the stream pushing state (i.e., the monitoring video is pushed to the specified storage device for storage) based on the stream fetching/stream pushing parameters (e.g., newly added flag bit parameters in a stream fetching/stream pushing URL (Uniform Resource Locator)).
Step S110, when the equipment is in a preview state, alarm information is pushed to the first CS client; the first CS client is a CS client which previews the first monitoring point equipment at present.
In this embodiment of the present application, when the first monitoring point device is in a preview state, the first monitoring point may push alarm information to a CS client (referred to as a first CS client herein) that is currently previewing the first monitoring point device.
For example, when the monitoring point device pushes a code stream to the CS client, a new data type (referred to as an alarm type herein) may be added on the basis of the current code stream data type (including a message header type, a data stream type, an end flag, and the like), and the CS client may determine that the received code stream is a data code stream or alarm information based on a type identifier in the code stream. After the CS client obtains the alarm information, the CS client may display the alarm information according to a preset manner, for example, output a voice prompt, obtain a code stream of the monitoring point device corresponding to the alarm information, and perform preview display.
Optionally, when the monitoring point device pushes the alarm information to the CS client, the alarm types may be different for the alarm event detected by the monitoring point device and the alarm events detected by other monitoring point devices, that is, the alarm types may at least include a first alarm type and a second alarm type, where the first alarm type is the alarm information triggered by the alarm event detected by the monitoring point device, and the second alarm type is the alarm information triggered by the alarm event detected by other monitoring point devices.
Illustratively, the alarm information may include monitoring point information, such as one or more of identification information of the monitoring point, affiliated network, IP address, affiliated domain information, and the like.
As can be seen, in the method flow shown in fig. 1, when the monitoring point device detects an alarm event and is in a preview state, the monitoring point device pushes alarm information to the CS client that previews the device at present, so that the alarm information is pushed without deploying an alarm server, the cost of alarm pushing is reduced, and the reliability of alarm pushing is improved.
In some embodiments, as shown in fig. 2, after step S100, the following steps may be further included:
And step S120, broadcasting an alarm event notification message when the equipment is not in a preview state.
Step S130, when receiving a response message sent by the second monitoring point device, pushing alarm information to the second monitoring point device so that the second monitoring device pushes the alarm information to the second CS client; and the second CS client is the CS client which previews the second monitoring point equipment at present.
Illustratively, the first monitoring point device may broadcast an alarm event notification message when the first monitoring point device detects an alarm event but the device is not in the preview state.
For example, a first monitoring point device may broadcast an alarm event notification message within a local area network in which the device is located.
When other monitoring point devices receive the alarm event notification message of the advertisement of the first monitoring point device, it can be determined that the alarm information of the first monitoring point device needs to be pushed, at this time, the other monitoring point devices can detect whether the device is in a preview state, and when it is determined that the device is in the preview state, a response message is sent to the first monitoring point device.
When the first monitoring point device receives a response message sent by a monitoring point device (referred to as a second monitoring point device herein), the first monitoring point device pushes alarm information to the second monitoring point device.
When receiving the alarm information pushed by the first monitoring point device, the second monitoring point device may push the alarm information to a CS client (referred to as a second CS client herein) that is currently previewing the second monitoring point device.
As can be seen, in the flow shown in fig. 2, for the monitoring point device that detects the alarm event and is not in the preview state, alarm information pushing may be performed by other monitoring point devices in the preview state, so that reliability of alarm information pushing is further improved.
In one example, in step S130, the response message carries the user ID of the second CS client.
In step S130, when receiving a response message sent by the second monitoring point device, pushing alarm information to the second monitoring point device may include:
acquiring the user ID of the second CS client carried in the response message, and determining whether the equipment records the user ID;
if not, pushing alarm information to second monitoring point equipment, and recording the user ID;
and if not, refusing to push the alarm information to the second monitoring point device.
For example, considering that when a monitoring point device broadcasts an alarm event notification message, there may be a plurality of monitoring point devices in a preview state, and the plurality of monitoring point devices in the preview state may have previews of some or all of the monitoring point devices by the same user (e.g., a monitoring person), in order to avoid repeated pushing of alarm information, when the monitoring point device in the preview state sends a response message to the monitoring point device broadcasting the alarm event notification message, the response message may carry a user ID of a CS client (i.e., a user ID used for login when the monitoring point device is previewed by the CS client).
Accordingly, when receiving a response message sent by the second monitoring point device, the first monitoring point device may obtain the user ID of the second CS client carried in the response message, and determine whether the device (the first monitoring point device) has recorded the user ID.
If the first monitoring point device does not record the user ID, the first monitoring point device may determine that the alarm information has not been pushed to the user, and at this time, the first monitoring point device may push the alarm information to the second monitoring point device and record the user ID.
And if the first monitoring point equipment records the user ID, refusing to push the alarm information to the second monitoring point equipment so as to avoid repeated pushing of the alarm information.
As can be seen, in this example, by recording the user ID subjected to alert information pushing, it is possible to support pushing alert information to multiple CS clients and avoid repeated pushing of alert information.
In one example, after broadcasting the alarm event notification message in step S120, the method may further include:
and when the response message is not received within the preset time, caching the alarm information.
For example, when the monitoring point device pushes the alarm information, if there is no monitoring point device in the preview state, the monitoring device that detects the alarm event cannot receive the response message, and at this time, the monitoring point device that detects the alarm event may cache the alarm event.
In one example, after caching the alarm information, the method may further include:
when detecting that the equipment is in a preview state, pushing cached alarm information to a third CS client; and the third CS client is the CS client which previews the first monitoring point equipment at present.
For example, after the first monitoring point device caches the alert information, when it is detected that the device is in a preview state (for a specific implementation, see the relevant description in step S100), the first monitoring point device may push the cached alert information to a CS client (referred to as a third CS client herein) that is currently previewing the first monitoring point device.
For example, the third CS client and the first CS client may be the same or different.
In another example, after caching the alarm information, the method may further include:
broadcasting an alarm event notification message according to a preset time interval, and pushing alarm information to third monitoring point equipment when receiving a response message sent by the third monitoring point equipment so that the third monitoring equipment pushes the alarm information to a fourth CS client; the third monitoring point device is in a preview state, and the fourth CS client is a CS client which previews the third monitoring point device currently;
Or the like, or a combination thereof,
when the alarm event is detected again and the device is not in a preview state, broadcasting an alarm event notification message, and when a response message sent by a fourth monitoring point device is received, pushing alarm information to the fourth monitoring point device so that the fourth monitoring device pushes the alarm information to a fifth CS client; and the fifth CS client is the CS client which previews the fourth monitoring point device currently.
For example, after the first monitoring point device buffers the alarm information, the first monitoring point device may further broadcast an alarm event notification message at preset time intervals (which may be set according to an actual scene), and when receiving a response message sent by a monitoring point device (referred to as a third monitoring point device herein), push the alarm information to the third monitoring point device.
The third monitoring point device may push the alert information to a CS client (referred to herein as a fourth CS client) that is currently previewing the present device (i.e., the third monitoring point device).
Alternatively, the first and second electrodes may be,
after the first monitoring point device caches the alarm information, it may also broadcast an alarm event notification message when the first monitoring point device detects the alarm event again and determines that the device is not in the preview state, and push the alarm information to a fourth monitoring point device when receiving a response message sent by the monitoring point device (referred to as a fourth monitoring point device herein).
The fourth monitoring point device may push this alert information to the CS client (referred to herein as the fifth CS client) that is currently previewing the present device (i.e., the fourth monitoring point device).
It should be noted that, when the first monitoring point device receives the response messages sent by the multiple third monitoring point devices (or fourth monitoring points), the repeated pushing of the alarm information may be avoided in the manner described in the foregoing embodiment.
In addition, when the first monitoring point device finishes pushing the cached alarm information, the first monitoring point device may stop broadcasting the alarm event notification message, and delete the cached alarm information.
In some embodiments, the alarm pushing method provided in the embodiment of the present application may further include:
when an alarm event notification message sent by a fifth monitoring point device is received and the device is in a preview state, sending a response message to the fifth monitoring point device;
when receiving the alarm information pushed by the fifth monitoring point device, pushing the alarm information to a sixth CS client; and the sixth CS client is the CS client which previews the first monitoring point equipment at present.
For example, when the first monitoring point device receives an alarm event notification message sent by a monitoring point device (referred to as a fifth monitoring point device herein), the first monitoring point device may detect whether the device (the first monitoring point device) is in a preview state.
When the first monitoring point device is in the preview state, the first monitoring point device may send a reply message to the fifth monitoring point device.
Optionally, the response message may carry a user ID of a CS client (referred to as a sixth CS client herein) that is currently previewing the first monitoring point device.
The processing flow when the fifth monitoring point device receives the response message sent by the first monitoring point device may refer to the processing flow when the first monitoring point device receives the response message sent by the second monitoring point device described in the foregoing embodiment.
When the first monitoring point device receives the alarm information pushed by the fifth monitoring point device, the first monitoring point device may push the alarm information to the sixth CS client.
Further, in this embodiment of the application, when the CS client receives the alarm information pushed by the monitoring point device, the CS client may obtain an alarm video clip from the monitoring point device based on the resource information included in the alarm information (for example, the IP address of the monitoring point device that detects the alarm event); the alarm video clip may be a video clip with a preset time length in front and back of the alarm time included in the alarm information.
It should be noted that, when the video data is stored in another server, the monitoring point device may also push the alarm information list to the other server (a server for storing the video data), and the CS client may obtain the alarm video from the other server.
In order to enable those skilled in the art to better understand the technical solutions provided in the embodiments of the present application, the following describes the technical solutions provided in the embodiments of the present application with reference to specific application scenarios.
In this embodiment, the alarm push of a monitoring point device (such as a dome camera) in a shopping mall is taken as an example.
Referring to fig. 3, a schematic diagram of an application scenario provided in the embodiment of the present application is shown in fig. 3, where the application scenario includes monitoring point devices a to E, and the monitoring point devices a to E are located in the same local area network.
As shown in fig. 4, based on the application scenario shown in fig. 3, the alarm push implementation flow of the monitoring point device is as follows:
when the monitoring point device a detects an alarm event, the monitoring point device a may detect whether the device is in a preview state.
If the monitoring point device A is in a preview state, the monitoring point device A pushes alarm information to a CS client which previews the monitoring point device A at present, and the CS client analyzes and displays the alarm information.
And if the monitoring point device A is not in the preview state, the monitoring point device A broadcasts an alarm event notification message.
When receiving the alarm event notification message, other monitoring point devices (monitoring point devices B to E) in the local area network may detect whether the device is in a preview state, and return a response message to the monitoring point device a when the device is in the preview state, where the response message carries the user ID of the CS client that previews the monitoring point device.
If the monitoring point device a receives the response message, the monitoring point device a may acquire the user ID carried in the response message and determine whether the user ID has been recorded; if the alarm information is recorded, the alarm information is not pushed to the monitoring point equipment; if not, alarm information is pushed to the monitoring point equipment, and the user ID is recorded.
For example, assuming that the monitoring point device a receives a response message sent by the monitoring piece device B, the monitoring point device a may obtain a user ID carried in the response message, and when the monitoring point device a determines that the user ID is not recorded, the monitoring point device a may push alarm information to the monitoring point device B.
Assuming that the user 1 logs in the CS client by using the user ID1 and previews the monitoring point device B and the monitoring point C, when the monitoring point device B and the monitoring point device C receive the alarm event notification message of the monitoring point device a, both the monitoring point device B and the monitoring point device C may send a response message to the monitoring point device a, where the response message carries the user ID 1.
Monitoring point device a receives the response messages sent by monitoring point device B and monitoring point device C (assuming that the response message sent by monitoring point device B is received first), determines that user ID1 is not recorded, and sends alarm information to monitoring point device B, and records user ID 1; when monitoring point device a receives the response message of monitoring point device C, since user ID1 has been recorded, monitoring point device a does not push alarm information to monitoring point device C to avoid repeated pushing of alarm information.
If the monitoring point device A does not receive the response message, the monitoring point device A caches the alarm information.
When monitoring point device a receives an alarm event notification message of other monitoring point devices (taking monitoring point device C as an example), monitoring point device a detects whether the device is in a preview state; if the monitoring point device A is in a preview state, sending a response message to the monitoring point device C, and pushing alarm information to a CS client side which previews the monitoring point device A at present when receiving the alarm information pushed by the monitoring point device C; if not, the alarm event notification message is not responded.
The methods provided herein are described above. The following describes the apparatus provided in the present application:
referring to fig. 5, a schematic structural diagram of an alarm pushing device according to an embodiment of the present application is shown in fig. 5, where the alarm pushing device may include:
a detecting unit 510, configured to detect whether the device is in a preview state when an alarm event is detected;
a pushing unit 520, configured to push alarm information to the first CS client when the device is in a preview state; the first CS client is a CS client which previews the first monitoring point equipment at present.
In some embodiments, as shown in fig. 6, the apparatus further comprises:
a broadcasting unit 530, configured to broadcast an alarm event notification message when the apparatus is not in the preview state;
the pushing unit 520 is further configured to, when receiving a response message sent by a second monitoring point device, push alarm information to the second monitoring point device, so that the second monitoring device pushes the alarm information to a second CS client; and the second CS client is a CS client which previews the second monitoring point equipment at present.
In some embodiments, the response message carries a user ID of the second CS client;
the pushing unit 520 is specifically configured to acquire the user ID of the second CS client carried in the response message, and determine whether the device has recorded the user ID; if not, pushing alarm information to the second monitoring point equipment, and recording the user ID; and if not, refusing to push the alarm information to the second monitoring point equipment.
In some embodiments, the broadcasting unit 530 is further configured to buffer the alarm information when the response message is not received within a preset time after the alarm event notification message is broadcasted.
In some embodiments, the pushing unit 520 is further configured to push the cached alert information to a third CS client when the detecting unit 510 detects that the device is in a preview state; and the third CS client is the CS client which previews the first monitoring point equipment at present.
In some embodiments, the broadcasting unit 530 is further configured to broadcast the alarm event notification message according to a preset time interval after the alarm information is cached;
the pushing unit 520 is further configured to, when receiving a response message sent by a third monitoring point device, push alarm information to the third monitoring point device, so that the third monitoring device pushes the alarm information to a fourth CS client; the third monitoring point device is in a preview state, and the fourth CS client is a CS client that previews the third monitoring point device at present;
or the like, or a combination thereof,
the broadcasting unit 530 is further configured to broadcast an alarm event notification message when the detecting unit 510 detects the alarm event again and the device is not in the preview state;
the pushing unit 520 is further configured to, when receiving a response message sent by a fourth monitoring point device, push alarm information to the fourth monitoring point device, so that the fourth monitoring device pushes the alarm information to a fifth CS client; and the fifth CS client is the CS client which previews the fourth monitoring point device currently.
In some embodiments, the pushing unit 520 is further configured to send a response message to a fifth monitoring point device when the alarm event notification message sent by the fifth monitoring point device is received and the device is in a preview state; when the alarm information pushed by the fifth monitoring point device is received, pushing the alarm information to a sixth CS client; and the sixth CS client is the CS client which previews the first monitoring point equipment at present.
Fig. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure. The electronic device may include a processor 701, a communication interface 702, a memory 703, and a communication bus 704. The processor 701, the communication interface 702, and the memory 703 communicate with each other via a communication bus 704. Wherein, the memory 703 is stored with a computer program; the processor 701 may perform the alert push method described above by executing a program stored on the memory 703.
The memory 703, as referred to herein, may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the memory 702 may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
Embodiments of the present application also provide a machine-readable storage medium, such as the memory 703 in fig. 7, storing a computer program, which can be executed by the processor 701 in the electronic device shown in fig. 7 to implement the alarm pushing method described above.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (9)
1. An alarm pushing method is applied to a first monitoring point device, and comprises the following steps:
when an alarm event is detected, detecting whether the equipment is in a preview state;
when the equipment is in a preview state, pushing alarm information to a first CS client; the first CS client is a CS client which previews the first monitoring point equipment at present;
when the equipment is not in a preview state, broadcasting an alarm event notification message;
when a response message sent by a second monitoring point device is received, pushing alarm information to the second monitoring point device so that the second monitoring point device pushes the alarm information to a second CS client; and the second CS client is a CS client which previews the second monitoring point equipment at present.
2. The method according to claim 1, wherein the response message carries a user ID of the second CS client;
When receiving a response message sent by a second monitoring point device, pushing alarm information to the second monitoring point device, including:
acquiring the user ID of the second CS client carried in the response message, and determining whether the equipment records the user ID;
if not, pushing alarm information to the second monitoring point equipment, and recording the user ID;
and if not, refusing to push the alarm information to the second monitoring point equipment.
3. The method of claim 1, wherein after broadcasting the alarm event notification message, further comprising:
and when the response message is not received within the preset time, caching the alarm information.
4. The method of claim 3, wherein after caching the alarm information, further comprising:
when detecting that the equipment is in a preview state, pushing cached alarm information to a third CS client; and the third CS client is the CS client which previews the first monitoring point equipment at present.
5. The method of claim 3, wherein after caching the alarm information, further comprising:
broadcasting an alarm event notification message according to a preset time interval, and pushing alarm information to a third monitoring point device when receiving a response message sent by the third monitoring point device, so that the third monitoring point device pushes the alarm information to a fourth CS client; the third monitoring point device is in a preview state, and the fourth CS client is a CS client that previews the third monitoring point device at present;
Or the like, or a combination thereof,
when the alarm event is detected again and the device is not in a preview state, broadcasting an alarm event notification message, and when a response message sent by a fourth monitoring point device is received, pushing alarm information to the fourth monitoring point device so that the fourth monitoring point device pushes the alarm information to a fifth CS client; and the fifth CS client is the CS client which previews the fourth monitoring point device currently.
6. The method of claim 1, further comprising:
when an alarm event notification message sent by a fifth monitoring point device is received and the device is in a preview state, sending a response message to the fifth monitoring point device;
when receiving the alarm information pushed by the fifth monitoring point device, pushing the alarm information to a sixth CS client; and the sixth CS client is the CS client which previews the first monitoring point equipment at present.
7. An alarm pushing device, which is applied to a first monitoring point device, the device comprising:
the detection unit is used for detecting whether the equipment is in a preview state or not when the alarm event is detected;
The pushing unit is used for pushing alarm information to the first CS client when the equipment is in a preview state; the first CS client is a CS client which previews the first monitoring point equipment at present;
wherein the apparatus further comprises:
the broadcast unit is used for broadcasting the alarm event notification message when the equipment is not in the preview state;
the pushing unit is further configured to, when receiving a response message sent by a second monitoring point device, push alarm information to the second monitoring point device, so that the second monitoring point device pushes the alarm information to a second CS client; and the second CS client is a CS client which previews the second monitoring point device currently.
8. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method of any one of claims 1 to 6 when executing a program stored in the memory.
9. A machine readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011246674.1A CN112509296B (en) | 2020-11-10 | 2020-11-10 | Alarm pushing method and device, electronic equipment and machine-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011246674.1A CN112509296B (en) | 2020-11-10 | 2020-11-10 | Alarm pushing method and device, electronic equipment and machine-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112509296A CN112509296A (en) | 2021-03-16 |
| CN112509296B true CN112509296B (en) | 2022-07-29 |
Family
ID=74957479
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011246674.1A Active CN112509296B (en) | 2020-11-10 | 2020-11-10 | Alarm pushing method and device, electronic equipment and machine-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112509296B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202976369U (en) * | 2012-11-08 | 2013-06-05 | 深圳天行健电子有限公司 | Intrusion alarm and monitoring video system, video detection terminals and monitoring host |
| US9082018B1 (en) * | 2014-09-30 | 2015-07-14 | Google Inc. | Method and system for retroactively changing a display characteristic of event indicators on an event timeline |
| CN105049819A (en) * | 2015-08-25 | 2015-11-11 | 天津福威科技发展有限公司 | Communication system having real-time video monitoring function |
| CN105096550A (en) * | 2015-06-16 | 2015-11-25 | 湖南亿谷科技发展股份有限公司 | Campus safety alarm prompting system and method thereof |
| CN206162816U (en) * | 2016-10-09 | 2017-05-10 | 深圳市泛海三江科技发展有限公司 | Control fire alarm linked system and net -harddisk video recorder |
| CN110708505A (en) * | 2019-09-18 | 2020-01-17 | 上海依图网络科技有限公司 | Video alarm method, device, electronic equipment and computer readable storage medium |
-
2020
- 2020-11-10 CN CN202011246674.1A patent/CN112509296B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202976369U (en) * | 2012-11-08 | 2013-06-05 | 深圳天行健电子有限公司 | Intrusion alarm and monitoring video system, video detection terminals and monitoring host |
| US9082018B1 (en) * | 2014-09-30 | 2015-07-14 | Google Inc. | Method and system for retroactively changing a display characteristic of event indicators on an event timeline |
| CN105096550A (en) * | 2015-06-16 | 2015-11-25 | 湖南亿谷科技发展股份有限公司 | Campus safety alarm prompting system and method thereof |
| CN105049819A (en) * | 2015-08-25 | 2015-11-11 | 天津福威科技发展有限公司 | Communication system having real-time video monitoring function |
| CN206162816U (en) * | 2016-10-09 | 2017-05-10 | 深圳市泛海三江科技发展有限公司 | Control fire alarm linked system and net -harddisk video recorder |
| CN110708505A (en) * | 2019-09-18 | 2020-01-17 | 上海依图网络科技有限公司 | Video alarm method, device, electronic equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112509296A (en) | 2021-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7302481B1 (en) | Methods and apparatus providing remote monitoring of security and video systems | |
| CN101442647B (en) | Control method for video playback and localization of video monitoring system and storage server thereof | |
| CN106803997B (en) | system and method for detecting client playing state in audio and video live broadcast | |
| EP1794934A1 (en) | Method, device a program for detecting an unauthorised connection to access points | |
| US20100257201A1 (en) | Method And System For Pulling Network Contents | |
| CN106844662B (en) | Method and device for recording reading state of instant message | |
| CN111372093B (en) | Live broadcast room management method, device, equipment and storage medium | |
| US10341290B2 (en) | Method and system for presenting recommendation information | |
| CN112509296B (en) | Alarm pushing method and device, electronic equipment and machine-readable storage medium | |
| CN113328972A (en) | Equipment monitoring method, device, equipment and storage medium | |
| CN110888790B (en) | Log management method and device, electronic equipment and storage medium | |
| CN111131484A (en) | Node mounting method, device, network node and storage medium | |
| CN107566216B (en) | Monitoring method, device and service system | |
| CN110971599A (en) | Vulnerability scanning method and device | |
| WO2016177237A1 (en) | Playing control method and device | |
| CN114465783B (en) | Method, system and storage medium for associating attack point with service message | |
| EP2721786A1 (en) | Evaluation of overall performance of interactive application service | |
| CN112702361B (en) | Safety blocking method, device and equipment based on lightweight distributed cooperative equipment | |
| CN110944037B (en) | Method, computer device and storage medium for client cache change configuration | |
| CN112948020A (en) | Configuration file processing method and device | |
| CN106603386A (en) | Method for managing instant messaging application chat records | |
| CN113473247A (en) | Video playing request processing method, device and system and electronic equipment | |
| CN112583627A (en) | Networking topology structure display method and device | |
| CN117579383B (en) | Method, device and equipment for detecting and intercepting active HTTP response | |
| CN111818296A (en) | Monitoring target identification method and distributed monitoring system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |