KR20120103328A - Surveillance apparatus for event tracking and event tracking method using the same - Google Patents

Abstract

PURPOSE: An unmanned monitoring device for tracing an event and an event tracing method are provided to reduce the misinformation ratio of an event by using an unmanned monitoring device. CONSTITUTION: A user interface unit(210) receives condition information about an event generated in a sensor field. The user interface unit receives a response method about the event from a user. A control engine(220) receives the condition information from sensor nodes. The control engine selects specific sensor nodes which receive the condition information. A cooperation engine(250) transfers the condition information to the control engine. The cooperation engine transfers the condition information to the selected specific sensor node. [Reference numerals] (210) User interface unit; (220) Control engine; (221) Control DB; (230) GIS engine; (240) Middleware engine; (250) Cooperation engine; (260) Image engine; (261) Image DB

Description

SURVILLANCE APPARATUS FOR EVENT TRACKING AND EVENT TRACKING METHOD USING THE SAME}

The present invention relates to an unmanned surveillance apparatus for event tracking and an event tracking method using the same, and more particularly, to an unattended surveillance apparatus for event tracking by interaction of sensors and an event tracking method using the same.

Unmanned surveillance devices use surveillance devices such as CCTV (Closed-Circuit Television) or IP (Internet Protocol) cameras to receive and monitor video. The unmanned market is widely used for crime prevention and information collection, and reduces blind spots by increasing the number of CCTVs or IP cameras. However, when the number of CCTVs or IP cameras increases in the unmanned surveillance device, the amount of information input through the CCTV or IP cameras is enormous, so that the number of surveillance personnel must be increased to monitor in real time.

In addition, the CCTV or IP cameras used in the unmanned surveillance device are not independent of each other as independent monitoring devices, and thus only have a function of displaying a surrounding image. Therefore, the conventional unmanned market value does not dominantly grasp the occurrence of the event, only passive response is possible, it is impossible to track the event in real time and there is a problem that the response to the event is delayed.

In the present invention, an unmanned monitoring system using a situation information between sensor nodes for an event generated in a sensor field in an unmanned monitoring apparatus based on a large sensor network and tracking a real-time event by the interaction of a sensor node and a control center It is to provide a device and a method for tracking events using the same.

A first aspect of the present invention is a user interface that receives situation information on an event generated in a sensor field including a plurality of sensor nodes and receives a response method for an event from a user, and context information from a plurality of sensor nodes. Receives and stores the received and provided to the user interface unit, and transmits the control engine and the situation information to the control engine to select the specific sensor node to receive the context information among the plurality of sensor nodes in response to the response method and the specific selected by the control engine It provides an unmanned market value for event tracking that includes a collaboration engine that delivers contextual information to sensor nodes.

In addition, to provide an unmanned market value for the event tracking further comprises a video engine for generating a surveillance image using the information received from the sensor field and delivers the surveillance image generated in the user interface.

In addition, the GIS engine including map information is further connected to the control engine to provide an unmanned market value for event tracking that enables the user interface unit to locate the sensor field through the map information.

Additionally, it further provides an unmanned market value for event tracking further comprising a middleware engine maintaining a connection between the platform of the plurality of sensor nodes and the platform of the control engine between the control engine and the plurality of sensor nodes.

In addition, the control engine has a context information database, which provides an unmanned market value for storing event information transmitted from the sensor field and tracking the event delivered by the user interface to selected specific sensor nodes. will be.

Additionally, the situation information includes a plurality of fields, and provides an unmanned market value for event tracking that includes at least one of an event ID field, a sensor node ID field, an event probability field, an event occurrence field, and an object information field. It is.

In addition, the event probability field, the event occurrence field, and the object information field in the context information provide an unmanned market value for event tracking that is stored separately before and after the event is confirmed by the control engine.

In addition, the sensor field includes a main sensor node and a slave sensor node connected to the main sensor node, and the main sensor node provides an unmanned market value for event tracking that transmits the status information transmitted from the control sensor to the slave sensor node. It is.

Additionally, the main sensor node and the slave sensor node each has an ID, and the slave sensor node tracks an event connected to the main sensor node in the form of a network.

The second aspect of the present invention, the step of recognizing the occurrence of the event in the sensor node ID field node of the sensor field including a plurality of sensor nodes and transmitting the situation information on the event to the control engine, the situation information transmitted to the control engine Is transmitted to the user interface unit to transmit a tracking command to the control engine to track the object that caused the event in response to the situation information in the user interface unit, and the control engine selects the object information from the sensor field in response to the tracking command. It is to provide an event tracking method comprising the step of delivering to specific sensor nodes.

In addition, in the step of delivering to specific sensor nodes, the control engine selects a specific sensor node in the sensor field and tracks the command to the specific sensor node in the cooperative engine that delivers the user's response to the sensor field through the user interface. It is to provide an event tracking method that delivers

In addition, in the step of recognizing the occurrence of the event, to provide an event tracking method further comprising the step of displaying the location where the event occurred using the map information to the user interface.

In addition, the control engine is provided with a situation information database, to provide the event tracking method for storing the situation information transmitted from the sensor field and delivering the situation information stored by the user interface to the selected specific sensor nodes.

In addition, the sensor field includes a main sensor node and a slave sensor node connected to the main sensor node, and provides an event tracking method for generating situation information in the main sensor node.

In addition, the main sensor node records the event ID, main sensor node ID, slave sensor node ID, event type, event probability, when the event occurred, and objects related to the event in the context information when the event occurs. When the event is confirmed by the control engine, the main sensor node provides an event tracking method for recording the event type, event probability, event occurrence time, and object related information in the situation information.

In addition, the main sensor node is connected to the unmanned monitoring device through a common interface unit to connect the main sensor node to the middleware engine, the middleware engine stores the IDs of the connected main sensor nodes, the slave to the main sensor node The sensor nodes are connected and the main sensor node stores the IDs of the slave sensor nodes, the main sensor node provides the IDs of the slave sensor nodes stored to the middleware engine through the common interface unit, and the middleware engine is the main sensor node ID. It provides a method of constructing a sensor field by providing the unmanned monitoring device with the ID of the slave sensor node connected to the main sensor node.

According to the unmanned monitoring device and the event tracking method using the event tracking according to the present invention, by detecting the event in real time in the sensor field based on the large sensor network and generating situation information, the sensor node included in the large sensor network They can collaborate by sending or receiving context information to automate incident tracking and context awareness and response.

Therefore, the unmanned surveillance apparatus can track the incident, thereby facilitating the resolution of the incident by using the unmanned surveillance market, and can lower the error rate of the judgment of the incident even with a small number of personnel.

1 is a structural diagram showing an embodiment of an unmanned surveillance apparatus for tracking an event according to the present invention.
2 is a structural diagram showing an embodiment of the control device shown in FIG.
3 is a diagram illustrating a process of tracing an event in an unmanned monitoring apparatus for event tracing according to the present invention.
4 is a structural diagram illustrating an embodiment of context information generated by the main sensor node shown in FIG. 1.
FIG. 5 is a flowchart illustrating an embodiment of a process of performing a tracking request to a sensor field in the control engine shown in FIG. 2.

Hereinafter, the present invention will be described in detail so that those skilled in the art can easily understand and reproduce the present invention through these embodiments.

1 is a structural diagram showing an embodiment of an unmanned surveillance apparatus for tracking an event according to the present invention.

Referring to FIG. 1, the unmanned monitoring device 100 includes a control device 110, a plurality of sensor fields 120a, 120b and 120c, and a common interface unit 130.

The control device 110 receives the information collected in the sensor fields 120a, 120b, and 120c to determine whether the event is a temporary event or an additional situation. When the control device 110 determines that an additional situation occurs, for example, the escape of the object that caused the event, the sensor fields 120a, 120b, and 120c track the object that caused the event. .

The sensor fields 120a, 120b, and 120c include a plurality of sensor nodes. The sensor fields 120a, 120b, and 120c collect information about an event occurring in an area in which the sensor nodes are installed, and transmit information on the object that generated the event to be monitored to the control device 110. send. The sensor fields 120a, 120b, and 120c include a plurality of slave sensor nodes connected to the main sensor nodes 121a, 121b, 121c and the respective main sensor nodes 121a, 121b, 121c in order to collect information. (122a, ..., 127a, 122b, ... 127b, 122c, .., 127c). The plurality of main sensor nodes 121a, 121b, 121c and the plurality of longitudinal sensor nodes 122a, ..., 127a, 122b, ... 127b, 122c, .., 127c each have an ID. You can communicate. The main sensor nodes 121a, 121b, 121c and the seed sensor nodes 122a, ..., 127a, 122b, ... 127b, 122c, .., 127c are acoustic sensors, temperature sensors, humidity sensors, illuminance sensors, gravity sensors, and cameras. It may include at least one of the control of the operation of the sensor or the camera and transmit the information collected from the sensor or camera to the control device or the sensor node according.

In addition, one main sensor node may be installed in one sensor field corresponding to the size of the area monitored by the sensor field, and a plurality of main sensor nodes may be installed.

The common interface unit 130 maintains the connection between the control device 110 and the plurality of sensor fields 120a, 120b, and 120c, and relates to an event generated from the plurality of sensor fields 120a, 120b, and 120c. Provides information to the control device 110 and receives the event tracking request from the control device 110 to track the event. The common interface unit 130 may use an Open Network Video Interface Forum (ONVIF) protocol.

2 is a structural diagram showing an embodiment of the control device shown in FIG.

2, the control device 110 includes a user interface 210, a control engine 220, a GIS engine 230, a middleware engine 240, a collaboration engine 250, and an image engine 260. do.

The user interface unit 210 receives the situation information on the event collected in the sensor field including the plurality of sensor nodes and provides the same to the user. In addition, when the user interface unit 210 determines the response method to the event using the situation information provided by the user, the user interface unit 210 receives the determined response method. That is, the user interface unit 210 may provide the user using the unmanned monitoring apparatus 100 with each of the main sensor nodes 121a, 121b, 121c and the longitudinal sensor node 122a of the plurality of sensor fields 120a, 120b, and 120c. ,…, 127a, 122b,… 127b, 122c, 122c, .., 127c) to provide the image and map information collected so that the user can recognize the situation to identify the object that caused the event and to track the object. Create commands to indicate whether or not to track the object and to determine the object in response to the user's decision.

The control engine 220 transmits the plurality of events detected in the plurality of sensor fields 120a, 120b, and 120c to the user interface 210 in real time based on intelligent situation recognition in response to the event information rule. In addition, the control engine 220 includes a control database 221, and stores and stores the contextual information transmitted from the plurality of sensor fields 120a, 120b, and 120c in the control database 221. Update the situation information stored by 210.

The Geographic Information System (GIS) engine 230 uses the map information to database the location information and the attribute information corresponding to the building, the road, and the like to the user interface unit 210 so that the map information can be visually displayed. do.

The middleware engine 240 includes the main sensor nodes 121a, 121b, 121c and the seed sensor nodes 122a, ..., 127a, 122b, ... 127b, 122c included in the plurality of sensor fields 120a, 120b, and 120c. ....., 127c) and the control engine 220 to communicate through the common interface unit 130, in particular, the main sensor node 121a for collecting information using XML (eXtensible Markup Language) Interface technology between the platforms of the control engine 220 and the platform of the 121b, 121c.

The collaboration engine 250 transmits the user's requirements to the sensor fields 120a, 120b, and 120c through the user interface 210. In addition, the collaboration engine 250 may display information received from the plurality of sensor fields 120a, 120b, 120c and the control engine 220 on the map based on the map information stored in the GIS engine 230. To help. In addition, the collaboration engine 250 allows information to be exchanged between the GIS engine 230 and the main sensor nodes 121a, 121b, and 121c that visualize the surveillance information using the panorama technology. When the incident tracking command is input from the user interface unit 210, the collaboration engine 250 may maintain tracking information in the control engine 220 and the main sensor nodes 121a, 121b, and 121c. In addition, the collaboration engine 250 may communicate with the plurality of sensor fields 120a, 120b, and 120c through the common interface unit 130.

The image engine 260 generates a surveillance image by time, region, and group for the monitored region through the network of the main sensor node and the slave sensor nodes included in the sensor fields 120a, 120b, and 120c. In addition, the image engine 260 includes an image database 261, and stores images captured by the sensor fields 120a, 120b, and 120c by time, region, and group. In addition, the image engine 260 may provide the image stored in the image database 261 to the user interface 210 so that the image may be viewed through the user interface 210. The image engine 260 may communicate with the sensor fields 120a, 120b, and 120c through the common interface unit 130.

3 is a diagram illustrating a process of tracing an event in an unmanned monitoring apparatus for event tracing according to the present invention.

Referring to FIG. 3, the unattended market value is monitored through the first sensor field 120a, the second sensor field 120b, and the third sensor field 120c, and the event is detected by the first type sensor nodes 122a,. 127a, 122b, ..., 127b, 122c, ..., 127c and the first area, which is an intersection monitored by the second type sensor nodes 122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c In (A), it is assumed that a collision accident (car and person or car and car, etc.) has occurred.

When the first type sensor node 123a and the second type sensor node 126a detect the occurrence of the first event in the first area A, the first main sensor node 121a is connected to the first type sensor node 123a. The second type sensor node 126a receives information such as an image and transmits the information to the control device 110. In this case, the first type sensor node 123a and the second type sensor node 126a calculate an event probability for an event occurring in the first area A. FIG. In this case, the first type sensor node 123a and the second type sensor node 126a may have different event probabilities for events generated due to differences in photographing positions. In addition, the first main sensor node 121a generates situation information using information collected by the first type sensor node 123a and the second type sensor node 126a and responds to the generated situation information. It is determined that the event recorded in the image collected by the sensor node 123a and the second type sensor node 126a is the same event. The first main sensor node 121a transfers the generated situation information to the control engine 220. The control engine 220 provides the user interface unit 210 with the situation information and the image generated by the image engine 260. In addition, the control engine 220 provides the user interface unit 210 with map information generated by the GIS engine 230. When the event generated by the user interface 210 is confirmed, the control engine 220 confirms that the event has occurred and specifies the object that caused the event. In this case, although the object causing the event is recorded in the situation information generated by the first main sensor node 121a, the object causing the event can be determined and corrected again through the image provided through the user interface 210. And, the control engine 220 predicts the escape route of the object that caused the event using the map information. The collaboration engine 250 grasps sensor fields for monitoring the escape route and transfers the situation information to the sensor field for monitoring the expected escape route. Then, when the vehicle, which is the object that caused the event, escapes from the first area A, which is the first event occurrence area, to the third area C after the second area B, in the second area B, the cooperative engine 250 is used. Monitors the escape vehicle in the third type sensor node 126b that has received the situation information through the third type sensor node 126c in the third area C and receives the situation information through the cooperative engine 250. Monitor your escape vehicle. In this case, in addition to the third type sensor node 126b and the fourth type sensor node 126c in the second area B and the third area C, other type sensor nodes may monitor the escape vehicle at the same time. In addition, the main sensor node and the slave sensor node continuously monitors the escape vehicle or the tracking request is withdrawn using the situation information and the information of the escape vehicle generated by the control engine 220.

4 is a structural diagram illustrating an embodiment of context information generated by the main sensor node shown in FIG. 1.

Referring to FIG. 4, the situation information includes a plurality of fields, an event ID field 401, a main sensor node ID field 402, a slave sensor node ID field 403, an event type field 404a, 404b, The event decision fields 405a and 405b, the event probability fields 406a and 406b, the event occurrence fields 407a and 407b, and the object information fields 408a, 408b, 409a, 409b, 410a, and 410b that caused the event. do.

The event ID field 401 is used to distinguish the generated events. The seed sensor nodes 122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c or the main sensor nodes 121a, 121b, 121c. ) Detects the occurrence of an event, the main sensor nodes (121a, 121b, 121c) is an event detected by itself or events from the slave sensor nodes (122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c) Receives the information of the event and assigns an ID for the event is recorded in the event ID field (401).

The primary sensor node ID field 402 includes the IDs of the primary sensor nodes 121a, 121b and 121c which collected the information on the event, or the slave sensor nodes 122a, ..., 127a, 122b,... The IDs of the main sensor nodes 121a, 121b, 121c connected to, 127b, 122c, ..., 127c are recorded.

The seed sensor node ID field 403 records IDs of the seed sensor nodes 122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c which have collected information on the event.

The event type fields 404a and 404b are divided into two fields, which are determined by the event type fields 404a and 404b, the event decision fields 405a and 405b, the event probability fields 406a and 406b, and the event occurrence field 407a. 407b) and object information fields 408a, 408b, 409a, 409b, 410a, and 410b are divided into two fields, respectively.

The event decision fields 405a and 405b are used to compose the event situation using the event information collected from the main sensor nodes 121a, 121b and 121c in the first field 405a and the second field 405b is used as the main sensor node (405b). After the situation information created in 121a, 121b, 121c is transferred to the control device 110, the modified information in the control engine 220 of the control device 110 can be stored.

The event probability fields 406a and 406b may be expressed in percentage as indicating the probability that an event detected in the sensor fields 120a, 120b and 120c is an event to be monitored. In this case, the probability calculated in the sensor fields 120a, 120b, and 120c is recorded in the first field 406a, and the probability modified in the control engine 220 is recorded in the second field 406b. Can be recorded.

Occurrence time field 407a, 407b is a field for recording the time when the event occurred, the first field 407a is the time detected by the sensor fields (120a, 120b, 120c) is recorded and the second field (407b) control The occurrence time modified in the engine 220 is recorded.

The object information fields 408a, 408b, 409a, 409b, 410a, and 410b store information on the object that caused the event in each of the sensor fields 120a, 120b, and 120c. The first field 408a, 409a, 410a records information about the object determined in the sensor fields 120a, 120b, and 120c, and records information about the object modified in the control engine 220 in the second fields 408b, 409b, and 410b.

FIG. 5 is a flowchart illustrating an embodiment of a process of performing a tracking request to a sensor field in the control engine shown in FIG. 2.

Referring to FIG. 5, a plurality of main sensor nodes 121a, 121b and 121c are connected to the control device 110 through a common interface 130. (500) The main sensor nodes 121a, 121b and 121c are connected to each other. When connected to the unmanned monitoring device 100, the main sensor nodes (121a, 121b, 121c) are connected to the middleware engine 240 through a common interface protocol. When the plurality of main sensor nodes 121a, 121b and 121c are connected to the control device 110, the middleware engine 240 stores IDs of the connected main sensor nodes 121a, 121b and 121c. Then, each of the longitudinal sensor nodes 122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c is connected to the plurality of main sensor nodes 121a, 121b, 121c, and each of the main sensor nodes 121a, 121b, 121c. 121a, 121b, and 121c store IDs of the plurality of seed sensor nodes 122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c. (520) And, the plurality of main sensor nodes ( 121a, 121b, and 121c may use IDs of the seed sensor nodes 122a, ..., 127a, 122b, ..., 127b, 122c, ..., 127c stored in the middleware engine 240 through the common interface unit 130. The middleware engine 240 has IDs of the main sensor nodes 121a, 121b, and 121c, and slave sensor nodes 122a, ..., and 127a corresponding to the main sensor nodes 121a, 121b, and 121c. IDs of, 122b, ..., 127b, 122c, ..., 127c are provided to the control engine 220. (540)

It is to be understood that the technical spirit of the present invention has been specifically described in accordance with the preferred embodiments thereof, but it is to be understood that the above-described embodiments are intended to be illustrative and not restrictive. In addition, it will be understood by those of ordinary skill in the art that various embodiments are possible within the scope of the technical idea of the present invention.

210: user interface unit 220: control engine
221: control database 230: GIS engine
240: middleware engine 250: collaboration engine
260: image engine 261: image database

Claims (16)

A user interface unit receiving situation information on an event generated in a sensor field including a plurality of sensor nodes and receiving a response method for the event from a user;
A control engine configured to receive and store the context information from a plurality of sensor nodes, provide the context information to the user interface unit, and select specific sensor nodes to receive the context information from among the plurality of sensor nodes in response to the response method; And
And a cooperative engine for delivering the situation information to the control engine and delivering the situation information to the specific sensor node selected by the control engine. The method of claim 1,
And an image engine for generating a surveillance image by using the information received from the sensor field and further comprising an image engine for transmitting the surveillance image generated in the user interface unit. The method of claim 1,
And a GIS engine including map information connected to the control engine so that the user interface unit can track the event to determine the location of the sensor field through the map information. The method of claim 1,
And a middleware engine for maintaining a connection between the platform of the plurality of sensor nodes and the platform of the control engine between the control engine and the plurality of sensor nodes. The method of claim 1,
The control engine includes a situation information database, and stores the situation information transmitted from the sensor field and the event tracking to deliver the stored situation information to the selected specific sensor nodes by the user interface. The method of claim 1,
The situation information includes a plurality of fields, the unattended monitoring device for event tracking including at least one of the event ID field, sensor node ID field, event probability field, event occurrence time field, object information field. The method of claim 6,
And an event probability field, an event occurrence time field, and an object information field of the situation information are classified and stored before and after the event is confirmed by the control engine and after being confirmed by the control engine. The method of claim 1,
The sensor field includes a main sensor node and a slave sensor node connected to the main sensor node, wherein the main sensor node tracks an event for transferring the situation information transmitted from the control sensor to the slave sensor node. The method of claim 8,
And the primary sensor node and the slave sensor node each have an ID, and the slave sensor node tracks an event connected to the primary sensor node in the form of a network. Recognizing the occurrence of an event in the sensor node ID field node of the sensor field including a plurality of sensor nodes and delivering the situation information on the event to the control engine;
The situation information transmitted to the control engine is delivered to the user interface unit for transmitting a tracking command to the control engine to track the object that caused the event corresponding to the situation information in the user interface unit; And
The control engine comprises the step of delivering the information of the object to the specific sensor node selected from the sensor field in response to the tracking command. The method of claim 10,
In the step of delivering to the specific sensor nodes, the control engine selects a specific sensor node in the sensor field, and transmits the response method of the user to the sensor field through the user interface to the specific sensor node from the collaboration engine Event tracking method for delivering tracking orders. The method of claim 10,
Recognizing the occurrence of the event, the event tracking method further comprising the step of displaying the location where the event occurred using the map information on the user interface. The method of claim 10,
The control engine includes a situation information database, which stores situation information transmitted from the sensor field and delivers the stored situation information to the selected specific sensor nodes by the user interface. The method of claim 10,
The sensor field includes a main sensor node and a slave sensor node connected to the main sensor node, wherein the main sensor node generates the situation information. 15. The method of claim 14,
When the event occurs, the main sensor node records the event ID, the main sensor node ID, the slave sensor node ID, the event type, the event probability, the occurrence point of the event, and information about objects associated with the event in the situation information. If the control engine confirms the event, the main sensor node records the event type, event probability, event occurrence time, objects associated with the event in the situation information. Connecting the main sensor node to an unmanned monitoring device through a common interface unit to connect the main sensor node to a middleware engine;
The middleware engine storing IDs of connected main sensor nodes;
Slave sensor nodes are connected to the main sensor node, and the main sensor node stores IDs of the slave sensor nodes;
Providing the IDs of the slave sensor nodes stored in the main sensor node to the middleware engine through the common interface unit; And
The middleware engine configures the sensor field by providing the main sensor node ID and the ID of the slave sensor node connected to the main sensor node to the unmanned monitoring device.

Images