KR101656241B1

KR101656241B1 - Method for storing and retrieving event information related to event

Info

Publication number: KR101656241B1
Application number: KR1020150182956A
Authority: KR
Inventors: 최용훈; 표성백
Original assignee: 주식회사 씨트링; 최용훈
Priority date: 2015-08-18
Filing date: 2015-12-21
Publication date: 2016-09-09

Abstract

A method of storing event information related to an event according to an exemplary embodiment of the present invention includes storing time stamp values and application programming interface (API) commands corresponding to a time point at which the event occurs, , And a directory as a city; And storing the first binary file including the index information indicating the characteristics of the event in the directory.

Description

METHOD FOR STORING AND RETRIEVING EVENT INFORMATION RELATED TO EVENT [0002]

The embodiment of the present invention relates to a method of storing and retrieving event information related to an event, wherein the event information is divided into a predetermined time unit using a text-based file and stored in the storage unit, The event information can be easily retrieved from the event information.

A database management system is a program that allows a plurality of computer users to record or access data in a database, providing a convenient and efficient environment for retrieving information in the database, storing information in the database, , Integrates data scattered by each application software, and enables each application software to share the integrated data to systematically utilize the information.

When the database management system is utilized in an embedded device that requires continuous recording of event information, the storage capacity for the event information is continuously increased, and it may be a DVR (Digital Video Recorder) or an NVR (Network Video Recorder) A large load can be imposed on an embedded device such as a hard disk, and a time required for a disk input output (IO) can be increased.

SUMMARY OF THE INVENTION The present invention provides a method of searching for events in a time based search by storing event information in a storage unit using a text-based file, .

A method of storing event information related to an event according to an exemplary embodiment of the present invention includes storing time stamp values and application programming interface (API) commands corresponding to a time point at which the event occurs, Generating a directory as a directory, and storing a first binary file including index information indicating the characteristics of the event in the directory.

The method of storing the event information may further include storing a second binary file including offset information indicating a minute offset of the index information in the first binary file in the directory .

The index information may include at least one of a camera ID of a camera that detects the event, a time stamp of the camera, an event type of the event, an event duration of the event, ). &Lt; / RTI >

The directory may further include at least one of an electronic device for processing the event information, a storage for storing the directory, a type of the event, and user information of the electronic device.

The method for storing the event information may be stored in a computer-readable recording medium.

A method for searching for event information related to an event according to an embodiment of the present invention includes the steps of: setting a time point at which to search for the event information; generating a time stamp and an API command corresponding to the time point; Selecting a directory consisting of year, month, day, and hour to execute the first binary file stored in the directory, and executing a first binary file stored in the directory, and retrieving index information indicating a characteristic of the event from the first binary file .

The method of retrieving the event information may further include executing a second binary file stored in the directory and obtaining offset information indicating a minute offset of the index information from the second binary file have.

The step of searching for the index information may use the offset information to directly search the index information corresponding to the offset from the first binary file.

The method of retrieving the event information may be stored in a computer-readable recording medium.

A method of storing and searching event information related to an event according to an embodiment of the present invention includes storing a database in a time-based search of a user by dividing the event information into a predetermined time unit using a text-based file, It is possible to avoid temporal inefficiency caused by searching the recording medium linearly and to quickly search for the event information.

The method of storing and retrieving event information related to the event according to the embodiment of the present invention has the effect of reducing the time required for disk input output (IO).

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In order to more fully understand the drawings recited in the detailed description of the present invention, a detailed description of each drawing is provided.
1 is a schematic block diagram of an electronic device according to an embodiment of the present invention.
2 is a detailed block diagram of the event storage device included in FIG.
3 is a conceptual diagram according to an embodiment of the present invention.
4 is a conceptual diagram according to another embodiment of the present invention.
5 is a flowchart illustrating a method of storing event information related to an event according to an embodiment of the present invention.
6 is a flowchart illustrating a method for searching for event information related to an event according to an embodiment of the present invention.
FIG. 7A shows a screen for searching for event information when a start point for searching for event information is set to a minute unit according to an embodiment of the present invention.
FIG. 7B shows a screen for searching for event information when a start time for searching for event information is not set to a minute unit according to an embodiment of the present invention.
FIG. 8 is a flowchart illustrating a method of searching for event information related to an event according to whether a starting point for searching for event information is set up to a minute unit according to an embodiment of the present invention.
9 is a screen for searching for event information in the electronic device according to the embodiment of the present invention.

It is to be understood that the present invention is not limited to the description of the embodiments described below, and that various modifications may be made without departing from the technical scope of the present invention. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail.

In the drawings, the same components are denoted by the same reference numerals. And in the accompanying drawings, some of the elements may be exaggerated, omitted or schematically illustrated. It is intended to clearly illustrate the gist of the present invention by omitting unnecessary explanations not related to the gist of the present invention. Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a schematic block diagram of an electronic device according to an embodiment of the present invention. Referring to FIG. 1, an electronic device 10 includes an event sensing device 100, an event storage device 200, and an event reproducing device 300.

The embedded system may be a microcontroller, a digital signal processor (DSP), or a digital signal processor (DSP). The embedded system may be a microprocessor, processor may be mounted.

In this specification, the electronic device 10 means an apparatus capable of detecting an event, storing event information related to the event, and searching for the event information on demand. At this time, the event may be an operation of detecting movement of an object or detecting a specific sound by a sensor built in the electronic device 10. [

Herein, the event information may refer to index information indicating a characteristic of the event, and the index information may include a camera ID of a camera that detects the event, a time stamp of a time when the event occurs, An event_type of the event, an event_duration of the event, and an event_priority of the event.

In the present specification, the time stamp may mean a time displacement parameter indicating the time point at which the data was present at a certain point or a time point at which the time point is commonly referred to. For example, the time stamp may be a unix time stamp.

The electronic device 10 may be a digital video recorder (DVR), a network video recorder (NVR), a smart phone, a tablet PC, a mobile Internet device an Internet device (MID), an Internet tablet, a digital camera, an Internet of things (IoT) device, an Internet of everything (IoE) device, or a wearable computer.

The event detection apparatus 100 refers to a device capable of detecting the event in an environment in which an event occurs periodically (or non-periodically). For example, the event detection device 100 may be a camera device that captures a video signal.

The event detection apparatus 100 may transmit the photographed video signal to the event storage apparatus 200. [ The event detection apparatus 100 may transmit the image signal as an analog signal to the event storage apparatus 200 or may convert the analog signal into digital image data and transmit the digital image data to the event storage apparatus 200. [

According to an embodiment, the event sensing device 100 may be implemented external to the electronic device 10. [ At this time, the event sensing apparatus 100 may be connected to the electronic device 10 by wire or wirelessly.

The event storage device 200 stores video signals transmitted from the event sensing device 100 and can manage (or process) the video signals using event information related to the video signals. The event storage apparatus 200 may transmit all or a part of the video signal to the event reproduction apparatus 300 at the request of the event reproduction apparatus 300. [ The description of the event storage device 200 will be described in detail with reference to FIG.

The event reproducing apparatus 300 can reproduce a video signal transmitted from the event storing apparatus 200. [ The event reproducing apparatus 300 may search for or request a video signal corresponding to the event information from the event storage device 200 when a user performs a time based search for the event information. The event reproducing apparatus 300 may include a display device, a speaker, and the like.

2 is a detailed block diagram of the event storage device included in FIG. 1 and 2, the event storage apparatus 200 may include a first interface 210, a second interface 220, an input unit 230, a control unit 240, and a memory 250 .

The first interface 210 may perform an interface between the event sensing apparatus 100 and the event storage apparatus 200. The first interface 210 may be connected to the event sensing apparatus 100 by wire or wirelessly and may transmit and receive a video signal related to the event detected by the event sensing apparatus 100 to the event sensing apparatus 100.

The second interface 220 may perform an interface between the event storage device 200 and the event reproducing device 300. The second interface 220 is connected to the event reproducing apparatus 300 in a wired or wireless manner and can transmit and receive a video signal related to the event detected by the event detecting apparatus 100 to the event reproducing apparatus 300.

The input unit 230 may include keys for driving the event storage device 200 and setting or executing various functions. According to an embodiment, the event storage device 200 may be implemented without including the input unit 230. [

The control unit 240 may include an event detection module 241, a directory management module 243, an event index file management module 245, and an event offset file management module 247.

A module in this specification may mean hardware capable of performing the functions and operations according to the respective names described in this specification or may include computer program codes capable of performing specific functions and operations May mean an electronic recording medium, such as a processor, having computer program code embodied therein or capable of performing a particular function and operation.

The control unit 240 may control the overall operation of the event storage device 200. [ The control unit 240 controls the first interface 210, the second interface 220, the input unit 230, and the memory 250, and according to the request of the user, for example, The event information for the event detected by the event detection apparatus 100 can be stored or retrieved.

The event detection module 241 may detect an event from the video signal detected by the event detection device 100 received through the first interface 210. [

The directory management module 243 may generate a directory for storing event information related to the event detected by the event detection module 241. [ The directory may mean a file list of a tree structure installed in order to know at which location of a peripheral device a file to be searched in the electronic device 10 exists.

The directory management module 243 may generate a directory indicating the time point at which the event occurred using time stamp information at the time when the event occurred.

Typically, the electronic device 10 uses a unix time as a timestamp. For example, the timestamp value of '1439668810' is a 'second' value that is incremented from 00:00:00 on January 1, 1970. If a specific event occurs at the time of '1439668810', you can create the directory in the following concise manner.

DateTime dt = DateTime (1439668810);

MakeDirectory ("/ device /" + dt.tostring ("/ yyyy / MM / dd / hh /");

Output: / device / 2015/08/15/20 /

Here, 'DateTime' represents a typical application programming interface (API) command, and is one of Open API commands provided in various software development environments. The directory management module 243 can easily generate '/ device / 2015/08/15/20 /', which is a directory corresponding to the time when an event occurs, using a time stamp and an Open API command. That is, the directory may consist of the date and time of the electronic device 10 and the time at which the event occurred.

The control unit 240 can store desired event information in the directory, and can easily search for the event information from the directory.

For example, if a user wishes to know what event occurred at 20:00 on August 15, 2015, the event information can be searched by the following simple method.

File * fp = open ("/ device / 2015/08/15/20 / event.txt");

The user can directly read a file existing in the directory corresponding to the time point of searching for the event information through a file pointer (fp) using the above formula to search for event information. That is, the user can obtain the location of the file of the desired time and read the event index file, so that the event information can be easily obtained.

In the present invention, a user can directly search for event information to be searched in time-based searching. The directory structure is constructed by year, month, day, and hour using a time stamp corresponding to the event when an event occurs, This is because the directory name is set to year, month, day, and hour. The directory structure is set to year, month, day, and hour, and at the same time, the directory name is set to year, month, day, and hour so that the user can directly search the file storing event information .

The method of storing and retrieving event information according to the present invention is a method of storing event information at a desired time point in a user's time-based retrieval without having to search linearly from the first event information to the event information at a desired time point, Can be searched easily.

The event index file management module 245 can manage an event index file. The event index file may include index information indicating a characteristic of an event as a binary file.

The event offset file management module 247 can manage an event offset file. The event offset file may include offset information indicating a minute offset of index information in the event index file as a binary file. In this case, the minute offset means an offset value corresponding to minute information in the event index file 420 or 520. [

The event offset file records a minute offset corresponding to 'minute' information at the time when the index information is recorded in the event index file when an event occurs. In the event index file, a minute offset value Can be set. For example, if an alarm event occurs at 14:22 on November 10, 2015, and the offset value of minutes corresponding to '22 minutes' in the event index file is' 120 ', the event information for the alarm event is obtained The electronic device reads the minute offset value from the event offset file and obtains index information corresponding to '22 minutes' in the event index file.

In the present invention, when the position of the file pointer at the time of recording the event information corresponding to '22 minutes' in the event index file is a minute offset value (for example, when the minute offset value is '120'), The minute offset value can be recorded in the event offset file together with minute information ('22 minutes'). The event offset file may be read linearly to retrieve the offset value '120' corresponding to '22 minutes'. However, in the present invention, when the event index file is opened, '120', it is possible to obtain desired event information by directly accessing a desired location without having to linearly read a file having a large capacity.

The directory, the event index file, and the event offset file according to the embodiments of the present invention will be described in detail with reference to FIGS. 3 and 4. FIG.

The memory 250 may include a program memory and a data memory. The program memory may store programs for the general operation of the event storage device 200. [ The program memory may store a program for detecting an event in a video signal (or image data). The data memory may store data output according to the execution of the programs.

The memory 250 may store video signals (or image data) and event information related to the events detected by the event sensing apparatus 100. [

3 is a conceptual diagram according to an embodiment of the present invention. The present invention generates a directory 410 using a time stamp value at the time of occurrence of an event and an application programming interface (API) command, and generates an event index file 420, which is a binary file of the determined structure, The offset file 430 may be stored in the directory 410.

The storage 440 may be a hard disk drive (HDD), a solid state driver (SSD), or the like, for storing data in an electromagnetic form for access by a computer processor. The storage 440 may be the memory 250 shown in FIG.

1 to 3, the electronic device 10 may store (or update) the event index file 420 in the directory 410 indicating the time when the event occurs (400) .

According to another embodiment, the electronic device 10 may store (or update) the event offset file 430 as well as the event offset file 430 in the directory 410.

According to the embodiment, the directory 410 may be configured in the form of '/ YYYY / MM / DD / HH' at the date and time of the time at which the event occurred. At this time, the event index file 420 is stored in the storage 440 in the form of '/YYYY/MM/DD/HH/event.xxx' in the directory 410, and the event offset file 430 is stored in the directory 410 Quot; /YYYY/MM/DD/HH/eventoffset.xxx " in the storage 440. The " /YYYY/MM/DD/HH/eventoffset.xxx "

The event index file 420 is associated with an event as a binary file and includes preset index information. The event index file 420 is a structure containing contents that a user wants to save when the event occurs, and the contents can be arbitrarily set by the user and can be variable. The user may refer to a developer.

The index information may include at least one of a camera_id, a time stamp, an event_type, an event_duration, and an event_priority for the event.

The event offset file 430 may include offset information indicating the position of the index information in the event index file 420 as a binary file. The event offset file 430 records a minute offset at the time when the index information is recorded when an event occurs. In the event index file 420, one offset may be set each time each minute starts.

The event index file 420 and the event offset file 430 may be generated in units of one hour according to the embodiment. However, the time unit in which the files 420 and 430 are generated may be changed according to the user's preference Can be selected in appropriate units. For example, files 420 and 430 may be created in minutes if they are events that are to be frequently recorded, and files 420 and 430 may be created in days if they are events that rarely occur.

The electronic device 10 selects the directory 410 corresponding to the time when the event is generated from the storage 440 and extracts the event index file 420 stored in the directory 410 and the event The offset file 430 is searched.

According to the embodiment, the directory 410 may be configured in the form of '/ YYYY / MM / DD / HH' at the date and time of the time at which the event occurred. At this time, the electronic device 10 searches the storage 440 for the event index file 420 in the form of '/YYYY/MM/DD/HH/event.xxx' which is the structure of the directory 410, The event offset file 430 in the form of '/YYYY/MM/DD/HH/eventoffset.xxx' can be retrieved from the storage 440.

The electronic device 10 may obtain offset information indicating the location of index information related to the event in the event index file 420 from the event offset file 430 stored in the directory 410. [ The electronic device 10 can select a minute offset corresponding to the 'minute' unit at the time when the event occurs from the event offset file 430 as the offset information.

The offset information indicates a relative address in the event index file 420 and indicates the position of index information related to the event in the event index file 420 as a displacement difference from the beginning to the given point.

The electronic device 10 may obtain the index information from the event index file 430 using the offset information (or minute offset). The electronic device 10 can locate the file pointer in the event index file 430 at a minute offset corresponding to the offset information and select the index information corresponding to the minute offset.

For example, the electronic device 10 may select the index information in the event index file 430 by moving the position of the file pointer arbitrarily using the offset information (or minute offset) and the FSEEK function provided in the standard API .

The electronic device 10 can speed up the storage and retrieval of the event information by using a text-based database (or file database) in a situation where continuous recording of event information is required.

struct eventOffset {
eventOffset () {
nCurrentMin = 0;
nStartOffset = 0;
}
int nCurrentMin;
int nStartOffset;
};
struct eventIndex {
eventIndex () {
camera_id = 0;
timestamp = 0;
event_type = 0;
}
int camera_id;
int timestamp;
int event_type;
};

Table 1 shows an embodiment of the event offset file 430 storing the event offset structure and the event index file 420 storing the event index structure. Assuming that the capacity of the event index file 420 storing the event index structure is 10,000 kb, the capacity of the event offset file 430 storing the event offset structure is 5000 KB, which is smaller than the capacity of the event index file 420. The capacity of the event offset file 430 may be 8 bytes * 60 minutes and may not exceed 480 bytes.

Referring to Table 1, the event offset file 430 may include offset information (nStartOffset) corresponding to minute information (nCurrentMin) and minute information (nCurrentMin). The event index file 420 may include camera ID information (camera_id), time stamp information (timestamp), event type (event_type), and the like.

The electronic device 10 can set a time point at which to search for the event information. According to an embodiment of the present invention, if it is time to search for the event information, the index information is directly retrieved from the event index file 420 stored in the directory 410 corresponding to the time point, It may not be used.

According to another embodiment, if the time point of searching for the event information is a 'minute' unit, offset information indicating the minute offset of the index information from the event offset file 430 stored in the directory 410 corresponding to the time point, And retrieve the index information from the event index file 420 using the offset information.

When the electronic device 10 opens the event index file 420 and directly moves the file pointer to 'nStartOffset' to perform a read operation, the time required for disk input output (IO) Can be reduced.

4 is a conceptual diagram according to another embodiment of the present invention. Except for the form of the directory 510, the configurations 500 to 550 shown in FIG. 4 are substantially the same as or similar to the configurations 400 to 450 shown in FIG.

1 to 4, when an event occurs (500), the electronic device 10 displays an event index file 520 and an event offset file 530 in a directory 510 indicating a time when the event occurred and related information. ) Can be stored (or updated). The related information may further include at least one of an electronic device 10, a storage 540 in which the directory 510 is stored, a type of the event, and a user of the electronic device 10. [

For example, the directory 510 may be configured in the form of '/ DEV / SSD / EVENT / YYYY / MM / DD / HH' of the date and time of the time at which the event occurred.

At this time, the event index file 520 is stored in the storage 540 in the form of '/DEV/SSD/EVENT/YYYY/MM/DD/HH/event.xxx' which is the structure of the directory 510, 530 may be stored in the storage 540 in the form of a directory 510 structure '/DEV/SSD/EVENT/YYYY/MM/DD/HH/eventoffset.xxx'. The DEV represents the electronic device 10, the SSD represents the storage 540, and the EVENT may represent the type of event.

The electronic device 10 selects the directory 510 indicating when the event has occurred from the storage 540 and extracts the event index file 520 stored in the directory 510 and the event offset 520 stored in the directory 510, The file 530 can be searched.

According to the embodiment, the directory 510 can be configured in the form of '/ DEV / SSD / EVENT / YYYY / MM / DD / HH' of the date and time of the time at which the event occurred. At this time, the electronic device 10 searches the storage 540 for the event index file 420 in the form of '/DEV/SSD/EVENT/YYYY/MM/DD/HH/event.xxx' And retrieve the event offset file 430 in the form of '/DEV/SSD/EVENT/YYYY/MM/DD/HH/eventoffset.xxx', which is the structure of the directory 510, from the storage 540.

5 is a flowchart illustrating a method of storing event information related to an event in an electronic device according to an embodiment of the present invention.

1 to 5, the electronic device 10 can detect an event using the event sensing apparatus 100 and acquire time stamp information at the time when the event occurs (S100 ).

The electronic device 10 may check whether there is a directory 410 or 510 indicating the time when the event occurred (S110).

If the directory 410 or 510 does not exist according to the confirmation result (S120), the electronic device 10 uses the time stamp information and an API (application programming interface) command to display the date at which the event occurred The directory 410 or 510 may be created in the event storage 200 (S130).

The electronic device 10 may store the event index file 420 or 520 including the preset index information in the generated directory 410 or 510 in step S140.

If the directory 410 or 510 exists according to the result of the check in step S120, the electronic device 10 displays the event index file 420 or 520 including the preset index information, (410 or 510) (S140).

The electronic device 10 sends an event offset file 430 or 530 containing offset information (or minute offset) indicating the location of the index information in the event index file 420 or 520 to the directory 410 or 510 (S150).

However, the step S150 may be omitted according to the embodiment.

A method of storing event information related to an event in the electronic device 10 can be stored in a computer-readable recording medium written in a computer program.

FIG. 6 is a flowchart illustrating a method of searching event information related to an event in an electronic device according to an embodiment of the present invention.

The electronic device 10 can set a point in time when the user wants to find the event information. The electronic device 10 may generate a directory 410 or 510, which is generated using a time stamp and an API command corresponding to the time point, and which corresponds to the time point, at step S200.

The electronic device 10 receives from the event offset file 430 or 530 stored in the directory 410 or 510 offset information (or minutes) indicating the location of the index information associated with the event within the event index file 420 or 520 Offset) (S210).

The electronic device 10 may obtain the index information from the event index file 420 or 520 stored in the directory 410 or 510 using the offset information at step S220.

A method of retrieving event information related to an event in the electronic device 10 can be stored in a computer-readable recording medium written in a computer program.

FIG. 7A shows a screen for searching for event information when a start point for searching for event information is set to a minute unit according to an embodiment of the present invention.

Referring to FIG. 7A, the user can set the starting point of searching for event information to 14:22 on November 10, 2015. That is, the user can quickly search for the event information by setting a starting point for searching for the event information up to a minute.

Setting the starting point for searching for the event information up to the minute can be performed by setting an index included in the event index file 420 or 520 from the event offset file 430 or 530 stored in the directory 410 or 510, To obtain offset information indicating a minute offset of the information. In this case, the minute offset means an offset value corresponding to minute information in the event index file 420 or 520. [

The final time for the user to search for the event information is set to 14:22 on November 14, 2015, and the final time may be set by the user or set to the current time.

The user can select a specific channel (for example, 'CH01') from among the plurality of channels CH01 to CH16 and search for the type of the event, POS (point of sale) / ATM (automatic teller's machine) devices can be searched. For example, the user may select motion and alarm as the type of event.

FIG. 7B shows a screen for searching for event information when a start time for searching for event information is not set to a minute unit according to an embodiment of the present invention.

Referring to FIG. 7B, the user may set the starting point of searching for event information to 14:00 on November 10, 2015. That is, the user can quickly search for the event information by setting a starting time point for searching for the event information up to a time unit.

Setting the start time to search for the event information up to a time unit means selecting the event index file 420 or 520 corresponding to the time point stored in the directory 410 or 510.

FIG. 8 is a flowchart illustrating a method of searching for event information related to an event according to whether a starting point for searching for event information is set up to a minute unit according to an embodiment of the present invention.

Referring to FIGS. 1 through 8, the electronic device may determine whether it is necessary to read a minute offset corresponding to minute information from the event offset file (S300). That is, the electronic device can determine whether to set up a starting time point for searching for the event information by 'minute' when the user searches for time information based on the event information.

When the electronic device needs to read a minute offset corresponding to the minute information from the event offset file, the electronic device opens the event offset file stored in the directory (/ dev / 2015/11/10/14 / (Open ("/ dev / 2015/11/10/14 / eventOffset.xxx"), S310).

Referring to FIGS. 7A and 8, when the start time for the user to find event information is 14:22 on November 10, 2015, the electronic device reads the minute offset corresponding to '22 minutes' from the event offset file (S320). For example, a minute offset corresponding to '22 minutes' may be a value of '120'.

The electronic device opens a portion corresponding to the minute offset position in the event index file stored in the directory (/ device / 2015/11/10/14 /) by using a minute offset (for example, 120) corresponding to '22 minutes' (Open ("/ dev / 2015/11/10/14 / event.xxx, 120"), S330).

(/ Dev / 2015/11/10/14 /) stored in the directory (/ dev / 2015/11/10/14 /) if the electronic device does not need to read the minutes offset corresponding to the minute information from the event offset file. 2015/11/10/14 / event.xxx) can be opened immediately (S340).

Referring to FIGS. 7B and 8, if the user sets the starting point for searching for event information to 14:00 on November 10, 2015, the electronic device opens an event index file stored in the directory corresponding to the starting point, It is possible to retrieve the index information in the event index file corresponding to 14:00 on November 10.

After steps S330 and S340, the electronic device can open an event index file corresponding to 15:00 on November 10, 2015. The electronic device can retrieve the index information in the event index file corresponding to 15 o'clock on November 10, 2015 (S350).

The electronic device can retrieve the index information in the event index file corresponding to 14:22 on November 14, 2015 (S360). The electronic device may terminate the search for the event information upon completion of the search for the index information until the last search time.

9 is a screen for searching for event information in the electronic device according to the embodiment of the present invention. Referring to FIGS. 1 to 9, the electronic device 10 may provide a user interface for searching for event information stored in a time stamp and storing the event information, and reproducing an event related to the event information. The event information may be index information.

FIG. 9 shows an event information search screen according to an embodiment of the present invention. However, the present invention is not limited to this, and various types of user interfaces may be provided according to design specifications.

The electronic device 10 may preferentially provide an event selection window 610-630 that allows the user to determine the type of event. For example, if the user selects Event 1 (610), the electronic device 10 may provide a user interface associated with Event 1.

If the user determines the type of event, the electronic device 10 may provide the user with a date selection window 640 of the event to be searched. For example, the user may select 'July 31, 2015'. When the user selects a date to search, the electronic device 10 may provide the user with a time selection window 650 for the event to be searched. For example, the user may select '2:14'. According to an embodiment, the user may select up to a time in seconds.

When the user selects the type, date, and time of the event to be searched, the electronic device 10 displays binary files (an event index file and an event index file) stored in a directory corresponding to the type, date, Event offset file) to search for event information.

The electronic device 10 can reproduce an event image corresponding to the event information based on the retrieved event information.

The embodiments of the present invention disclosed in the present specification and drawings are merely illustrative of specific embodiments of the present invention and are not intended to limit the scope of the present invention in order to facilitate understanding of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical idea of the present invention are possible in addition to the embodiments disclosed herein.

10: Electronic device
100: Event detection device
200: Event storage
240:
241: Event detection module
243: Directory management module
245: Event Index File Management Module
247: Event Offset File Management Module
300: Event playback device
410, 510: Directory
420, 520: Event index file
430, 530: Event Offset File
440, 540: Storage

Claims

A method for storing event information related to an event,
Generating a directory as a year, month, day, and hour corresponding to the time point using an API (application programming interface) command and a timestamp value corresponding to a time when the event occurs;
Storing a first binary file including index information indicating characteristics of the event in the directory; And
Storing a second binary file including offset information indicating a minute offset corresponding to minute information in which the index information is recorded in the first binary file, in the directory .

delete

2. The method of claim 1,
At least one of a camera_id of a camera that detects the event, a time stamp value, an event_type of the event, an event_duration of the event, and an event_priority of the event &Lt; / RTI >

The method according to claim 1,
Wherein the event information is generated by at least one of an electronic device processing the event information, a storage in which the directory is stored, a type of the event, and user information of the electronic device.

A computer-readable recording medium having recorded thereon a computer program capable of performing a method of storing event information according to claim 1.

A method for retrieving event information related to an event,
Setting a time point for searching for the event information;
Selecting a directory, which is generated by using a timestamp value corresponding to the time point and an API command, and is composed of year, month, day, and hour corresponding to the time point;
Reading a first binary file stored in the directory and retrieving index information indicating a characteristic of the event from the first binary file; And
Reading the second binary file stored in the directory and obtaining offset information indicating a minute offset corresponding to minute information in which the index information is recorded in the first binary file from the second binary file; &Lt; / RTI >

delete

7. The method of claim 6, wherein the step of retrieving the index information comprises:
And the index information corresponding to the minute offset is retrieved from the first binary file using the offset information.

7. The method of claim 6,
At least one of a camera_id of a camera that detects the event, a time stamp value, an event_type of the event, an event_duration of the event, and an event_priority of the event &Lt; / RTI >

7. The method according to claim 6,
Wherein the event information is generated by at least one of an electronic device processing the event information, a storage in which the directory is stored, a type of the event, and user information of the electronic device.

A computer-readable recording medium having recorded thereon a computer program capable of performing a method of retrieving the event information according to claim 6.