JP4845175B2 - Information processing apparatus, control method therefor, program, and recording medium - Google Patents

Description

  The present invention relates to an information processing apparatus, an image file transfer method, a program, and a computer-readable recording medium that can refer to past image data corresponding to an emergency event when an emergency event occurs. .

  In Patent Literature 1, recorded video information and real-time video before the occurrence of an alarm are transmitted to a video display terminal, and the video display terminal displays both images at the same time and compares them. A video surveillance system is disclosed that can easily monitor and judge whether or not an abnormality has occurred.

  In Patent Document 2, the alarm image storage unit stores an image of a television camera corresponding to the sensor when the sensor detects an abnormality. The image storage unit immediately after the alarm stores an image of a television camera corresponding to the sensor a predetermined time after the sensor senses an abnormality. After the storage of the image in the image storage unit immediately after the alarm is completed via the transmission / reception unit, the control unit centers each image stored in the periodic image storage unit, the alarm time image storage unit, and the image storage unit immediately after the alarm. An image transmission system for transmitting to an apparatus is disclosed.

Japanese Patent Application Laid-Open No. 2004-266592 JP-A-8-124065

  In the prior art disclosed in Patent Document 1, an image that is traced back for a predetermined time can be reproduced when an event occurs. However, when an event occurs at a short time interval at a plurality of locations, or when an event occurs at the same location multiple times, simultaneous display Has its limits.

  In addition, the archiving method shown in Patent Document 2 has a problem that the transmission of the archive file imposes a burden on the image processing server and may interfere with the reception of the normal captured image, and the image is stored until the reception of the archived image is completed. There is a problem that it cannot be referenced.

  Accordingly, an object of the present invention is to reduce the time lag until the reproduction of the image file even in the archiving method, and to avoid the load on the receiving side due to simultaneous transmission of a large amount of image data as in the prior art.

An information processing apparatus according to the present invention is an information processing apparatus connected to at least one photographing apparatus via a communication line, and includes an image data receiving unit that receives image data from the photographing apparatus, and an image data receiving unit. Recording control means for recording received image data on a recording medium, and using the image data recorded on the recording medium, a predetermined value from the photographing apparatus or another external device connected via the communication line A first image file including image data up to a second time point that is a predetermined time point after a first time point when the input signal is present, and a predetermined time has elapsed from the first time point the image file generation means and the image file of the first generated by the generation means for generating a second image file including the image data up to the third time is the time at separately Transfer the image file, then characterized by comprising an image file transfer means for transferring the second image file.

  According to the present invention, an image file including past image data is generated by receiving a predetermined input signal, and the image file is immediately transferred. It is possible to reduce the time lag until reproduction and to avoid the load on the receiving side due to simultaneous transmission of a large amount of image data as in the prior art.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments to which the invention is applied will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a diagram showing a schematic configuration of a network video recorder system according to an embodiment of the present invention. It should be noted that the connection configuration of various terminals on the network 100 in FIG. 1 is merely an example, and it is needless to say that various configuration examples can be taken according to applications and purposes. In other words, the number of camera servers 400 is not limited to the three illustrated, and may be various, and the number of sensors 405 and independent sensors and the number of client PCs 300 are not limited to the illustrated numbers. It is also possible to connect the sensor 405 or the independent sensor 405 and the monitoring client 500 directly with a dedicated sensor line.

  The server 200 acquires image data from each camera server 400 connected via the network 100 and records (records) it inside. The recorded image data is transmitted to the client PC 300 that issued the request in response to a request from the client PC 300.

  The client PC 300 (viewer) performs various setting processes of the network video recorder system, a process of reproducing image data received from the server 200, a camera control operation, and the like in accordance with an operation by the operator. FIG. 8 is a diagram illustrating an example of a display screen on the client PC 300. As shown in FIG. 8, on the client PC 300, a plurality of image data received from each camera server 400 via the server 200 can be displayed simultaneously.

  The camera server 400 acquires image data generated by imaging processing of one or more cameras connected to the camera server 400, and caches the acquired image data in a recording medium such as a RAM. The cached image data is transferred to the server 200. One or more sensors 405 are connected to the camera server 400. The detection information of the sensor 405 is transmitted to the server 200 via the camera server 400. Further, the independent sensor 450 in which a power source, an AD converter, and a communication module are added to a single sensor transmits a sensor signal directly to the server 200 via the network 100.

  The monitoring client 500 is a personal computer operated by a person in charge of monitoring work. The monitoring client 500 can view images of each camera server 400 and displays an event occurrence message on the screen. Further, when an emergency event occurs, the server 200 transfers the images for a predetermined time before and after the occurrence of the emergency event to the monitoring client 500 as a file. The person in charge of monitoring work can accurately grasp the situation by browsing the images before and after the occurrence of the emergency event a desired number of times from a desired time point.

Next, the hardware configuration of the server 200 in FIG. 1 will be described with reference to FIG. The CPU 201 comprehensively controls each device and controller connected to the system bus 204. In the ROM 203 or the external memory 211, a BIOS (Basic Input / Output System) that is a control program of the CPU 201, a part of an operating system program, and various programs to be described later that are necessary for realizing functions executed by each server or PC. Etc. are stored. The RAM 202 functions as a main memory, work area, and the like for the CPU 201. The RAM 202 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 202 and executing the program.

  The input controller 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). The video controller 206 controls display on a display device such as the CRT display 210. As the display device, not only a CRT but also other display devices such as a liquid crystal display can be applied.

  The memory controller 207 includes a boot program, browser software, a network video recorder program 212 for causing the CPU 201 to execute processing described below, a definition file 213 including the IP address of each camera server, and a setting file for each camera server. Access to external memory 211 such as a compact flash (registered trademark) memory connected via an adapter to various tables 214, hard disk (HD), flexible disk (FD), PCMCIA card slot for storing recording data 215 and operating system To control.

  The various tables 214 store information relating to the specific camera and the camera server 400 for the sensor 405 and the independent sensor 450, and event contents corresponding to event classifications.

  The communication I / F controller 208 is connected to and communicates with an external device via a network, and executes communication control processing on the network. For example, Internet communication using TCP / IP is possible. Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 202, for example. Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  The external memory 216 is a storage medium for captured images when an event occurs (sensor detection), and uses a hard disk or a DVD (DVD-RW, DVD + RW, DVD-RAM).

  Next, the operation of the network video recorder system will be described with reference to the flowcharts of FIGS. 3 to 7 and the screen / file layouts of FIGS. 8 to 14.

  First, FIG. 7 is a flowchart of a setting process of each camera server 400 that is performed prior to shooting of the network video recorder system. This process is executed by the client PC 300, and the set information is transmitted from the client PC 300 to the server 200 and registered.

  In step S711, basic information such as the IP address and identification ID of each camera server 400 and the file output timing for each camera server 400 is input (screen is not shown). For example, when the file output timing is set to 10 minutes, one physical file storing an image in the recorded data 215 is created every time 10 minutes are taken. The name of the physical file includes the ID of each camera server and the creation date and time of the file, and is a unique name.

  In step S712, a recording schedule including recording time (start and end), day of the week, recording mode, video size (number of pixels in the vertical and horizontal directions), and presence / absence of a preset is set on the screen of FIG. After the recording schedule, as shown at 901 in FIG. 9, the recording modes that can be set include a normal recording mode, a motion detection recording mode, and a sensor recording mode. On the setting screen shown in FIG. 9, a check box is provided corresponding to each recording mode, and a check can be made by operating a mouse or the like in the check box to set the corresponding recording mode. it can.

  A pull-down menu 902 for setting a frame rate for normal recording is provided on the right side of the check box for the normal recording mode. By operating this pull-down menu 902, the user can select a frame rate for outputting image data from the camera server 400 during normal recording.

  On the right side of each check box for the motion detection recording mode and the sensor recording mode, setting buttons 903 and 904 for performing various settings of the motion detection recording mode and the sensor recording mode are provided. If the motion detection recording mode setting button 903 is pressed, the process proceeds to step S713, and the setting screen shown in FIG. 11 is displayed. If the sensor recording mode setting button 904 is pressed, the process is performed. Proceeding to step S713, the setting screen shown in FIG. 10 is displayed.

  On the setting screen for the sensor recording mode shown in FIG. 10, the priority of the sensor event recording process, the frame rate at the time of the sensor event recording process (sensor event recording frame rate value), the recording time before the sensor event occurs (event Pre-recording time), recording time from the end of the sensor event (post-event recording time), etc. are set. Although not shown in FIG. 10, as other setting contents of the sensor recording mode, the pan value (sensor event recording pan value), tilt value (sensor event recording tilt value) of the camera at the time of sensor event recording processing, and A zoom value (sensor event recording zoom value), a duration of sensor event recording processing (sensor event recording setting time), and the like are set.

  On the setting screen for the motion detection recording mode shown in FIG. 11, the motion detection means, the frame rate at the time of motion detection event recording processing, the sensitivity of motion detection, and the area of the shooting screen targeted for motion detection correspond to the total shooting area. Ratio (area ratio), duration of motion detection state as a reference for motion detection, priority of motion detection recording processing, frame rate during motion detection recording processing (motion detection recording frame rate), from before the motion detection event occurred The recording time (pre-event recording time), the recording time from the end of the motion detection event (post-event recording time), and the like are set. Although not shown in FIG. 11, the duration of motion detection recording processing (motion detection recording setting time) and the like are set as other setting contents of the motion detection recording mode.

  If the “OK” button is pressed on the setting screen of FIG. 9, 10 or 11, the process proceeds to step S714. However, if both the motion detection recording check box and the sensor recording check box are turned on in the screen of FIG. 9, when the “OK” button in FIG. 10 is pressed, the screen transitions to the screen of FIG. If the “OK” button is pressed on the screen of FIG. 11, the process proceeds to step S714. When the recording schedule is set as described above, the screen after the recording schedule registration shown in FIG. 12 is displayed, and the recording schedule set for each camera server 400 is shown on this screen.

  In step S714, the emergency event setting screen of FIG. 13 is displayed. The detailed setting screen 1310 is a setting screen for a part of the extended recording mode (1301 in FIG. 13), and is displayed by pressing a detailed setting button on the extended screen 1301. In the detailed setting screen, one or a plurality of camera servers can be collectively specified by setting the target camera (1302 in FIG. 13), and the target event of the emergency event (in the example of FIG. 13, when a specific button is pressed ( Urgent), sensor detection of a specific camera, detection of motion of a specific camera, reception of an alarm signal from other sensors (1303 in FIG. 13), pre-event recording time and post-event recording time corresponding to the target event (in FIG. 13) 1304, 1305), image size, image quality (bit rate), frame rate, and output format (format of image to be archived) (1306 to 1309 in FIG. 13) can be specified.

  Here, the pre-event recording time and the post-event recording time are based on the time of event occurrence, and archive the captured images of the target camera server from the desired time before the event occurrence to the desired time after the event occurrence. Means to send to. In other words, when the pre-event recording time is 5 minutes and the post-event recording time is 3 minutes, the captured images for a total of 8 minutes from the 5 minutes before the event occurrence to the 3 minutes after the event occurrence are archived.

  In step S715, the above setting content is transmitted from the client PC 300 to the server 200, and the server 200 registers each setting content in the network camera control master table (M102) of FIG. 14 corresponding to the corresponding camera server 400. To do.

  FIG. 3 is a main flowchart during recording. In FIG. 3, step S301 is executed by the camera server 400, and step S305 is executed by the sensor 405 or the independent sensor 450. Steps S311 to S319 are executed under the control of the CPU 201 of the server 200.

  First, in step S311, when the shooting start button is pressed on the initial screen (not shown) of the video recorder system of the server 200, the process proceeds to step S312. In step S312, the server 200 starts an image reception process. At the start of the image receiving process, an image buffer and a sensor signal buffer are secured in the RAM 202.

  In step S313, a session for transmitting and receiving captured images is established between each camera server 400 and server 200. In step S301, the camera server 400 transmits the captured image, and the server 200 starts receiving the captured image. . The received image data is stored in the image buffer of the RAM 202 via the communication I / F controller 208 and added to the recorded data 215 of the external memory 211 by the image reception process. This image reception process continues until the photographing end button is pressed, and processing is performed in parallel with the sensor signal processing process in steps S314 to S319 (however, in the case of a single CPU, time sharing).

  When the sensor 405 or the independent sensor 450 detects a sensor event in step S305, the sensor 405 or the independent sensor 450 transmits a sensor signal to the server 200. The sensor signal includes a sensor number and a detection time. The sensor signal is stored in the sensor signal buffer of the RAM 202 via the communication I / F controller 208 of the server 200.

  In step S314, it is determined whether the server 200 has received a new sensor signal. Specifically, the sensor signal buffer and event log in the RAM 202 are read to determine whether a new sensor signal has been received. If a new sensor signal is received, the process proceeds to step S317. If a new sensor signal is not received, the process proceeds to step S315.

  In step S315, it is determined whether the file output timing has arrived for the file for which a captured image is being added by each camera server 400. Specifically, it is determined based on the file output interval of the definition file 213, the current time, and the time stamp of the file that was output immediately before. If the file output timing has arrived, the process proceeds to step S316. If the file output timing has not arrived, the process returns to step S314.

  In step S316, the file output process is called with the camera ID and file generation time as arguments. Details will be described with reference to the flowchart of FIG.

  In step S317, it is determined whether the sensor information means an emergency event. Whether or not it is an emergency depends on whether or not the event is set in step S714 in FIG. If it means an emergency event, the process proceeds to step S318. If it does not mean an emergency event, the process proceeds to step S319.

  In step S318, emergency event processing is executed, shooting is interrupted according to the setting in step S714 of FIG. 7, and a moving image for a predetermined time is transmitted to the monitoring client 500. Details will be described with reference to the flowchart of FIG.

  In step S319, normal event processing is executed. Details will be described with reference to the flowchart of FIG.

  FIG. 4 is a flowchart showing details of the file output process in step S316. The processing shown in FIG. 4 is also executed under the control of the CPU 201 of the server 200.

  The CPU 201 secures an area in the RAM 202 when the server 200 is activated, and the file output process is activated and enters a standby state. In the file output step S316, the camera ID of the camera server 400 is delivered as an argument to the file output process, and in the predetermined folder specified by the camera ID of the camera server 400 to which the standby file output process is delivered in step S412. The file name currently being recorded (for example, a file starting with FILE_STB) is acquired.

  In step S413, the control command for interrupting the addition of the image data to the file currently recorded at the camera ID and the file generation time is delivered to the image reception process. As a result, the image receiving process interrupts the addition of the image data to the file currently being recorded. Since the image data of the camera server 400 newly received at the time of interruption is stored in the image buffer in the work area of the RAM 202 by the image reception process, no image data is lost.

  In step S414, the name of the recorded file is renamed. For example, the file being recorded is FILE_STB_MEDIA_0001 — 20050701 — 124000. If it is avi, FILE_ARC_MEDIA_0001 — 20050701 — 124000. Change to avi. Here, 0001 is the ID of the camera server, and 20050701_124000 means the file creation date time.

  In step S415, a new recording file is generated in a predetermined folder uniquely determined by the camera ID. For example, if the camera ID is 0001 and is generated at 12:57:00 on July 1, 2005, FILE_STB_MEDIA_0001_2005050701-125000. avi.

  In step S416, the camera ID, the control command for resuming the addition of the image data to the file currently being recorded, and the recording file name generated in step S415 are delivered to the image reception process. As a result, the image reception process resumes adding the received image data from the camera server stored in the image buffer in the work area of the RAM 202 to the recording file generated in step S415.

  FIG. 5 is a flowchart showing details of the emergency event processing in step S318 of FIG. The processing shown in FIG. 5 is executed under the control of the CPU 201 of the server 200. First, a flow of processing for transmitting an image after occurrence of an emergency event and before the occurrence of the emergency event will be described.

  In step 511, message information that conveys the contents of the emergency event that has occurred (sensor ID, camera server ID, event occurrence time and event contents) is transmitted to the monitoring client 500.

  In step S512, the name of a file currently being recorded (for example, a file beginning with FILE_STB) in a predetermined folder specified by the camera ID of the camera server 400 in which the emergency event has occurred is acquired.

  In step S513, the camera ID and a control command for interrupting the addition of the image data to the currently recorded file are delivered to the image reception process. As a result, the image receiving process interrupts the addition of the image data to the file currently being recorded. The image data of the camera server 400 newly received after the interruption is stored in the image buffer in the work area of the RAM 202.

  In step S514, the name of the recorded file is renamed. For example, the file being recorded is FILE_STB_MEDIA_0001 — 20050701 — 124000. If it is avi, FILE_ARC_MEDIA_0001 — 20050701 — 124000. Change to avi. Here, 0001 is the ID of the camera server 400, and 20050701 — 124000 means the file creation date time. In the generated file, for example, an image from the position immediately after the file output in the immediately preceding step S315 to the position where the additional recording was interrupted in step S513 is stored.

  In step S515, a new recording file is generated in a predetermined folder uniquely determined by the camera ID. For example, if the camera ID is 0001 and is generated at 12:57:00 on July 1, 2005, FILE_STB_MEDIA_0001_2005050701-125000. avi.

In step S516, the camera ID, the control command for resuming the addition of the image data to the file currently being recorded, and the recording file name generated in step S515 are delivered to the image reception process. As a result, the image reception process resumes adding the received image from the camera server 400 stored in the image buffer in the work area of the RAM 202 to the recording file generated in step S515. That is, the image data from the position immediately after the additional recording is interrupted in step S513 is stored in the file generated in step S515. FIG. 15 is a diagram for explaining an example of the archive processing for recorded image data. Additional recording is interrupted at the position of t ₃ in FIG. 15 (event occurrence time).

  In step S517, it is determined whether there is an event log of an emergency event that is currently being processed. If the event log of the emergency event does not exist, the process proceeds to step S518. If the event log of the emergency event exists, the process proceeds to step S522.

  In step S518, the event that occurred this time is added to the event log that includes the sensor ID, camera server ID, event occurrence time and event classification, event flag, transmission counter, and post-event time lapse flag corresponding to the current emergency event. At this time, the event flag is turned on and the transmission counter is set to zero.

  In step S519, an emergency event occurs from the pre-event recording time at the emergency event set in step S714 (numerical value of how many minutes (seconds) are archived before the event occurs) and the file output time in step S316. Compare the time elapsed to the time.

In step S520, whether the comparison result in step S 519, retroactive minutes before the event occurs in the generated image file in step S514 (pre-event recording time of the image (in FIG. 15 (1)) it is all included For example, when an image of 5 minutes before the occurrence of the emergency event is requested (when the retroactive part is 5 minutes), the elapsed time from the file output time in step S316 to the emergency event occurrence time is about 4 minutes. If there is (in the example of FIG. 15, it is located between the file output time and t1 and t3), the image data ((1) in FIG. 15) five minutes before the occurrence of the emergency event is generated in step S514. Therefore, the image data from 5 minutes before to 4 minutes before is included in the file output in step S316. In addition to the image file generated in S514, it is necessary to extract image data from the file output in Step S316. As a result of the determination in Step S520, an event occurs in the image file generated in Step S514. If all the previous retroactive parts are not included, the process proceeds to step S521. If the image file generated in step S514 includes all the retroactive parts before the event occurrence, the process proceeds to step S521. The process proceeds to S522.

  In step S521, from the image file output in step S316, the image file generated in step S514 has insufficient image data for the retroactive portion before the event occurrence (in the above example, image data of about one minute (in FIG. 15 (3)) is extracted.

  In step S522, when the transmission counter is zero and the post-event time lapse flag is OFF, the retroactive image data before the occurrence of the event is extracted from the image file generated in step S514. If it is determined in step S520 that the image file generated in step S514 does not include all of the retroactive events before the occurrence of the event, all image data (in FIG. 15) from the image file generated in step S514. (1)-(3)) are extracted and added to the end of the image data extracted in step S521 ((3) in FIG. 15). On the other hand, if it is determined in the image file generated in step S514 that all the retroactive parts before the occurrence of the event are included, the image data corresponding to the retroactive part from the image file (in FIG. 1)) is extracted.

  In step S523, the extracted image is transmitted to the monitoring client 500 as an image file. At this time, the event log transmission counter of the emergency event is incremented by one.

  In step S524, the event log of the emergency event is referred to and it is determined whether image data after the occurrence of the event has been transmitted. If the value of the transmission counter in the event log is 1, it is determined that only the image before the event has been transmitted, and the image after the event has not been transmitted yet. Here, since the value of the transmission counter is 1, it is determined that the image after the event has not been transmitted yet. Accordingly, the process proceeds to step S525 here.

  In step S525, it is determined whether the post-event recording time set in step S714 has elapsed since the occurrence of the emergency event. If it is determined that the recording time after the event has elapsed since the occurrence of the emergency event, the process returns to step S512, and it is determined that the recording time after the event has not elapsed since the occurrence of the emergency event Shifts the processing to step S526. The reception determination of other event signals in step S526 will be described in detail later. If it is determined in step S526 that no other event signal has been received, the process proceeds to step S527 and waits for a predetermined time (about 0.3 seconds). When such a standby time is repeated and the recording time after the event has elapsed since the occurrence of the emergency event, the process proceeds to step S512 as described above. At this time, the post-event time lapse flag in the event log is turned on.

  Next, image transmission processing after occurrence of an emergency event after the recording time after the event has elapsed (processing when returning from step S525 to step S512) will be described. In step S512, the name of the file currently being recorded in the predetermined folder specified by the camera ID of the camera server 400 in which the emergency event has occurred is acquired.

In step S513, the camera ID and a control command for interrupting the addition of the image data to the currently recorded file are delivered to the image reception process. As a result, the image reception process interrupts the addition of the image to the currently recorded file. The image data of the camera server 400 newly received after the interruption is stored in the image buffer in the work area of the RAM 202 .

  In step S514, the name of the recorded file is renamed. For example, the recording file is FILE_STB_MEDIA_0001_2005050701_124500. If it is avi, FILE_ARC_MEDIA_0001 — 20050701 — 124500. Change to avi. Here, 0001 is the ID of the camera server 400, and 20050701_124500 means the file creation date time. In the generated file, image data from the position immediately after the additional recording is interrupted in the previous step S513 to the position where the additional recording is interrupted in the current step S513 is stored.

  In step S515, a new recording file is generated in a predetermined folder uniquely determined by the camera ID.

  In step S516, the camera ID, the control command for resuming the addition of the image data to the file currently being recorded, and the recording file name generated in step S515 are delivered to the image reception process. As a result, the image reception process resumes adding the received image from the camera server 400 stored in the image buffer in the work area of the RAM 202 to the recording file generated in step S515. That is, the image data from the position immediately after the additional recording is interrupted in step S513 is stored in the file generated in step S515.

  In step S517, it is determined whether an event log of the emergency event exists. Since the event log has already been generated for the emergency event in the previous step S518, the process proceeds to step S522 here.

  In step S522, when the transmission counter is 1 and the post-event time lapse flag of the event is on, all image data is extracted from the image file generated in step S514. In step S523, the image after the event has occurred is extracted. The file is transmitted to the monitoring client 500 as a file. At this time, the transmission counter is incremented by one. As a result, the event log transmission counter of the emergency event is 2.

  In the subsequent step S524, it is determined by referring to the event log transmission counter whether or not the image has been transmitted after the event has occurred. Here, since the value of the event log transmission counter is 2, it is determined that the image after the event has already been transmitted. If the image after the occurrence of the event has already been transmitted, the event flag of the event log of the emergency event is turned off.

  Next, a case where an emergency event corresponding to another camera (hereinafter referred to as a second emergency event) occurs following the occurrence of the emergency event (hereinafter referred to as a first emergency event) will be described. If the pre-event elapsed time of the second emergency event does not overlap the time zone before the recording time after the first emergency event elapses, the flow of FIG. 5 is executed individually for the second emergency event. Therefore, the description in this case is omitted. Hereinafter, a case will be described in which the pre-event elapsed time of the second emergency event overlaps the time zone before the post-event recording time of the first emergency event elapses. FIG. 17 is a diagram for explaining an example of the archive processing for image data to be recorded.

  A determination is made in step S526 as to whether or not the pre-event elapsed time of the second emergency event overlaps the time zone before the post-event recording time of the first emergency event elapses. This determination is made by referring to the sensor signal buffer in the work area of the RAM 202, receiving a new sensor signal, and referring to the pre-event recording time of the second emergency event. If the pre-event elapsed time of the second emergency event overlaps the time zone before the recording time of the first emergency event elapses, the process returns to step S317. If the pre-event elapsed time of the second emergency event does not overlap with the time zone before the recording time of the first emergency event elapses, the process proceeds to step S527.

  For the second emergency event, the process proceeds to step S511 via step S317. Since the event log of the second emergency event does not yet exist, the process starts from the transmission of the message information to the monitoring client 500 in step S511. By executing the processing up to the transmission of the pre-event image in S523, the pre-event image ((2) in FIG. 17) is transmitted to the monitoring client 500.

  Next, in step S524, it is determined whether the post-event image has been transmitted for both the first and second emergency events. Since the post-event image has not yet been transmitted for both the first and second emergency events, it is determined in step S525 whether the post-event recording time has elapsed for both the first and second emergency events. Judgment is made. The determination as to whether or not the post-event recording time has elapsed is made independently for each of the first and second emergency events.

  For example, when the post-event recording time of the first emergency event has elapsed, the post-event time elapse flag of the first event log is turned on in step S525, and the process proceeds to step S512. Thereafter, the processes of steps S512 to S517 and steps S522 to S523 are executed for both the first emergency event and the second emergency event. In step S523, the post-event image ((3) in FIG. 17) of the first event for which the post-event time lapse flag is on is transmitted to the monitoring client 500, and is stored in the event log of the first emergency event. The value of the transmission counter is set to 2. On the other hand, the post-event time lapse flag of the second emergency event is still in an off state, so the post-event image of the second emergency event is not yet transmitted to the monitoring client 500.

  Thereafter, since there is an event log whose transmission counter is 2, the process proceeds to step S528, and the event flag of the event log is set to OFF. In a succeeding step S529, it is determined whether or not event flags of all event logs are off. Here, only the first and second emergency events have been described, and the event flag of the second emergency event is still on, so the process proceeds to step S525.

  Next, for the second emergency event, the processes in steps S525 to S527 are repeated until the post-event recording time of the second emergency event has elapsed. When the post-event recording time elapses, the post-event time elapse flag in the event log is turned on, and the processing in steps S512 to S517 and S522 to S523 is performed in the same manner, and the image data after the event of the second emergency event is generated. Is transmitted to the monitoring client 500.

  By transmitting the image after the event occurrence, the event log transmission counter of the second emergency event becomes 2, and the event log is set to OFF in step S528 via step S524. In a succeeding step S529, it is determined whether or not event flags of all event logs are set to OFF. Here, since only the event logs of the first and second emergency events are described as an object, it is determined that the event flags of all event logs are set to OFF, and the processing illustrated in FIG. 5 is ended. .

  Next, a case where another emergency event corresponding to the same camera (hereinafter referred to as a third emergency event) occurs in succession to the occurrence of the emergency event (hereinafter referred to as a first emergency event) will be described. To do. If the pre-event elapsed time of the third emergency event does not overlap the time zone before the recording time after the event of the first emergency event elapses, the flow of FIG. 5 is executed individually for the third emergency event. Therefore, the description in this case is omitted. Hereinafter, a case will be described in which the pre-event elapsed time of the third emergency event overlaps the time zone before the post-event recording time of the first emergency event elapses. FIG. 16 is a diagram for explaining an example of the archive processing for image data to be recorded.

  A determination is made in step S526 as to whether or not the pre-event elapsed time of the third emergency event overlaps the time zone before the post-event recording time of the first emergency event elapses. This determination is made by referring to the sensor signal buffer in the work area of the RAM 202, receiving a new sensor signal, and referring to the pre-event recording time of the third emergency event. If the pre-event elapsed time of the third emergency event overlaps the time zone before the post-event recording time of the first emergency event elapses, the process returns to step S317. If the pre-event elapsed time of the third emergency event does not overlap with the time zone before the post-event recording time of the first emergency event elapses, the process proceeds to step S527.

  For the third emergency event, the process proceeds to step S511 via step S317. Since the event log of the third emergency event does not yet exist, the process starts from the transmission of the message information to the monitoring client 500 in step S511. By executing the processing up to the transmission of the pre-event image data in S523, the pre-event image data is transmitted to the monitoring client 500. However, in this case, the image file generated in step S514 normally stores image data that is traced back by the pre-event recording time set from the time of the occurrence of the third emergency event, but here the first emergency event is stored. The image data before event occurrence ((1) in FIG. 16) has already been transmitted for the image, and the image data before the event occurrence is recorded in the image before the event occurrence by going back the pre-event recording time set from the time of the third event occurrence. Since there is an overlapping portion ((5) in FIG. 16), the overlapping portion ((5) in FIG. 16) is obtained from the image data that is traced back by the pre-event recording time set from the time of the third event occurrence. The image data to be excluded ((2) in FIG. 16) is stored in the image file generated in step S514 and transmitted as the pre-event image data of the third emergency event. That.

  Next, in step S524, it is determined whether post-event image data has been transmitted for both the first and third emergency events. Since post-event image data has not yet been transmitted for both the first and third emergency events, whether or not the post-event recording time has elapsed for both the first and second emergency events in step S525. Judgment is made. The determination as to whether or not the post-event recording time has elapsed is performed independently for each of the first and third emergency events.

  For example, when the post-event recording time of the first emergency event has elapsed, the post-event time elapse flag of the first event log is turned on in step S525, and the process proceeds to step S512. Then, the process of step S512-step S517 and step S522-step S523 is performed about both a 1st emergency event and a 3rd emergency event. In step S523, the post-event image of the first emergency event whose post-event time lapse flag is on is transmitted to the monitoring client 500, and the value of the transmission counter in the event log of the first emergency event is set to 2. Will be set. However, in this case, the image file generated in step S514 normally stores image data corresponding to the time after the occurrence of the event set from the occurrence of the first emergency event. Since the pre-event image ((2) in FIG. 16) has already been transmitted for the emergency event, and the pre-event image data overlaps with the post-event image data of the first event, the first emergency Image data ((3) in FIG. 16) obtained by removing the third pre-event image data ((2) in FIG. 16) from the post-event event image data is saved in the image file generated in step S514. It is transmitted as pre-event image data of the first emergency event.

  Thereafter, since there is an event log whose transmission counter is 2, the process proceeds to step S528, and the event flag of the event log is set to OFF. In a succeeding step S529, it is determined whether or not event flags of all event logs are off. Here, only the first and third emergency events are described as an object, and since the event flag of the third emergency event is still on, the process proceeds to step S525.

  Next, for the third emergency event, the processes in steps S525 to S527 are repeated until the post-event recording time of the third emergency event has elapsed. When the post-event recording time elapses, the post-event time elapse flag in the event log is turned on, and the processing of step S512 to step S517 and step S522 to step S523 is similarly performed, and the image data after the occurrence of the event of the third emergency event Is transmitted to the monitoring client 500. However, in this case, the image file generated in step S514 normally stores image data corresponding to the time after the occurrence of the event set from the time of the occurrence of the third emergency event. Since the after image already overlaps with the image data ((3) in FIG. 16) transmitted as the image after the occurrence of the first emergency event, the post-event occurrence time set from the occurrence of the third emergency event The image data (FIG. 16 (4)) excluding the post-event image of the first emergency event ((4) in FIG. 16) from the image data that has just passed is stored in the image file generated in step S514. Then, it is transmitted as image data after the occurrence of the third event.

  By transmitting the image data after the occurrence of the third emergency event, the transmission counter of the event log of the third emergency event becomes 2, and the event log is set off in step S528 through step S524. In a succeeding step S529, it is determined whether or not event flags of all event logs are set to OFF. Here, since only the event logs of the first and third emergency events are described as an object, it is determined that the event flags of all event logs are set to OFF, and the processing illustrated in FIG. 5 is ended. .

  By processing in this way, when an emergency event occurs, the image file that is recording the image received from the target camera server 400 is quickly closed, and a new image file for recording is assigned and closed. An image for a desired time is archived from the image file, and transmitted to the monitoring client as an archive image until the event occurs. After that, when the recording time after the event elapses, the image file being recorded again is promptly closed, a new image file for recording is assigned, the image data for the recording time after the event is archived from the closed image file, and the event The generated archive archive image is transmitted to the monitoring client 500.

  According to the present embodiment, as described above, the image data before the event occurrence and the image data after the event occurrence are sequentially archived, and each image is generated when the image file before the event occurrence and the image file after the event occurrence are generated. Since the files are sequentially transmitted to the monitoring client 500, the time lag until reproduction on the monitoring client 500 is reduced even in the archiving method, and monitoring by simultaneous reception of a large amount of image data as in the past is performed. It is possible to avoid the load on the client 500 for use. Therefore, it is possible to browse images of the relevant part before and after the emergency event quickly and in a desired manner, and to take an appropriate response to the emergency event.

  Even if another emergency event occurs in another camera server before the time after the occurrence of an emergency event, it is identified by the camera server ID and time of occurrence in the event log, and managed by event flags Therefore, an appropriate image file can be extracted and transmitted to the monitoring client 500. In the above description, the image data before and after the occurrence of the event is archived and transmitted in response to the occurrence of the event. However, the above operation may be performed in response to the reception of the motion detection signal.

  FIG. 6 is a flowchart showing details of the normal event processing shown in step S319 of FIG. The process shown in FIG. 6 is executed under the control of the CPU 201 of the server 200.

  When the server 200 is activated, an area is secured in the RAM 202, the event image output process is activated, and a standby state is entered.

  In step S611, the preset (pan / tilt / zoom) value at the event occurrence set in step S713 is transmitted to the camera server 400.

  In step S612, the event that has occurred this time is added to the event log that includes the sensor ID, camera server ID, event occurrence time, and event classification.

  In step S613 of the event image output process call, the server 200 delivers the camera ID, sensor ID, event occurrence time, and event classification of the camera server 400 as arguments to the file output process.

  In step S614, message information that conveys the content of the event that has occurred (sensor ID, camera server ID, event occurrence time, and event content) is transmitted to the monitoring client 500.

  In step S621, the name of a file currently being recorded (for example, a file beginning with FILE_STB) in a predetermined folder specified by the camera ID of the camera server 400 that has been delivered is acquired. In step S622, the system waits for a predetermined time (for example, about 5 seconds).

  In step S623, the recorded file name acquired in step S622 is compared with the time portion of the currently recorded file name to determine whether the recorded file has been switched from the time of step S621. That is, in step S623, it is determined whether the image file output by the file output process in step S316 has been switched. If switched, the process proceeds to step S624. If not switched, the process returns to step S622.

  In step S624, a file having a predetermined name (including the camera ID, sensor ID, event classification, and event occurrence time) for the time specified in step S713 is generated, and images before and after the event are specified for the specified time. make a copy. If the file being recorded is switched after the event occurs and the image file for a predetermined time after the event cannot be copied, the process returns to step S622 and waits until a new image file is output by the file output process in step S316. When a new image file is output, the images before and after the event are copied from the image file output in the previous step S316 and the image file output in the current step S315 for a specified time.

  In step S625, the images before and after the event copied in step S624 are moved to a predetermined folder.

  Next, a second embodiment of the present invention will be described. In FIG. 5, when an emergency event occurs in steps S519 to S521, files for a predetermined time before the occurrence of the event are extracted and then sent to the monitoring client. An embodiment in which one or two image files generated immediately before in step S316 are immediately transmitted to the monitoring client is also conceivable. By processing in this way, it is possible to save time for extracting image files for a predetermined time from the previous one or two image files. This embodiment is particularly suitable when the network is fast.

  Next, a third embodiment of the present invention will be described. In the present embodiment, the transmission image file is extracted according to the normal file output timing and the occurrence timing of the emergency event as in the first embodiment, or the immediately preceding 1 is extracted as in the second embodiment. A determination step for determining whether to transmit one or two image files as they are is further added. That is, the transmission image file extraction processing time is compared with the increase time of the transmission time by transmitting a large image file stored in the normal file output, and a determination is made based on which is smaller.

  For example, suppose that the setting for requesting an image of 5 minutes before the occurrence of an event is made in step S714, and normal file output is every 10 minutes. When an emergency event occurs 4 minutes after normal file output, the last 1 minute of the previous output file and the currently recorded file 4 minutes are images to be sent to the monitoring client. Here, the processing time for extracting the transmission image file for 1 minute from the image file for 10 minutes is 10 seconds, and when the image for 10 minutes stored in the hard disk is transmitted by normal file output, the image for 1 minute is transmitted. When it is required to be longer by 30 seconds than when transmitting the image, the extraction process is selected because it is faster to extract the transmission image file for 1 minute. This determination requires a table of extraction processing time and a table of file capacity and required transmission time according to the recording time to the file, and these are recorded in various tables 214. Needless to say, the required transmission time is not a numerical value based on a theoretical value such as a LAN but an effective speed (about 30 to 40% of the theoretical value in Ethernet (registered trademark)).

  Next, a fourth embodiment of the present invention will be described. In the above-described embodiment, the case where the recorder server and the image reference terminal that refers to the images before and after the event occurrence are separate cases has been described. However, the present invention is not limited to this, and a multiprocessor is installed or a multicore processor is installed. When hardware with high image file processing capability is used, such as when it is installed, a configuration in which the recorder server and the image reference terminal are integrated is also possible. In this case, the archive image file before and after the event need not be transmitted over the network, and the archive image file is transferred from the hard disk storage area for image storage via the bus under the control of the processor controlling the recorder. The data is transferred to the hard disk storage area used by the processor executing the reference program.

  Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium. Needless to say, this can also be achieved by reading and executing the program code stored in.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention.

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (basic system or operating system) running on the computer based on the instruction of the program code. Needless to say, a case where the functions of the above-described embodiment are realized by performing part or all of the actual processing and the processing is included.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function is determined based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion board or function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

It is a figure which shows schematic structure of the network video recorder system which concerns on one Embodiment of this invention. It is a figure which shows the hardware constitutions of a server. It is a main flowchart at the time of image data recording. It is a flowchart which shows the detail of the file output process of step S316 of FIG. It is a flowchart which shows the detail of the emergency event process of step S318 of FIG. It is a flowchart which shows the detail of the normal event process shown to step S319 of FIG. It is a flowchart which shows the setting process of each camera server performed prior to imaging | photography of a network video recorder system. It is a figure which shows the example of a display structure of the image data of each camera server on client PC. It is a figure which shows an example of the recording schedule setting screen of a camera server. It is a figure which shows an example of the setting screen for sensor recording modes. It is a figure which shows an example of the setting screen for motion detection video recording modes. It is a figure which shows an example of the display screen after recording schedule registration. It is a figure which shows an example of an emergency event setting screen. It is a figure which shows the example of 1 structure of a network camera control master table. It is a figure for demonstrating the example of this archive process with respect to the recorded image data. It is a figure for demonstrating the example of this archive process with respect to the recorded image data. It is a figure for demonstrating the example of this archive process with respect to the recorded image data.

Explanation of symbols

100: Network 200: Server 300: Client PC
400: Camera server 405: Sensor 450: Independent sensor 500: Monitoring client 201: CPU
202: RAM
203: ROM
204: System bus 205: Input controller 206: Video controller 207: Memory controller 208: Communication I / F controller 209: Keyboard (KB)
210: CRT
211, 216: External memory 212: Network video recorder program 213: Definition file 214: Various tables 215: Recorded data

Claims (13)

An information processing apparatus connected to at least one photographing apparatus via a communication line,
Image data receiving means for receiving image data from the imaging device;
Recording control means for recording image data received by the image data receiving means on a recording medium;
A predetermined time from a first time point when a predetermined input signal is received from the image capturing device or another external device connected via the communication line using the image data recorded on the recording medium. A first image file that is an image file including image data up to a second time point that is a retroactive time point, and image data up to a third time point when a predetermined time has elapsed from the first time point. Image file generation means for individually generating a second image file that is an image file including the image file;
An information processing apparatus comprising: an image file transfer unit that transfers the first image file generated by the image file generation unit , and then transfers the second image file . When there is no predetermined input signal , the image file generation means extracts image data for the predetermined time from the recording medium every time a predetermined time elapses, and an image file including the extracted image data The information processing apparatus according to claim 1, wherein: The image file generation means is a third image file that is the image file that is generated immediately before the predetermined input signal and has the predetermined input signal, and immediately after the third image file is generated. If the fourth time point, which is the time point, is after the second time point, in addition to the image data from the fourth time point to the first time point, a part of the image in the third image file The information processing apparatus according to claim 1, wherein the first image file is generated using data . The time required to transfer the third image file by the image file transfer means and the time required to generate the first image file by the image file generation means and transfer by the image file transfer means And a judgment means for judging which time is short,
The image file transfer means transfers the third image file when the determination means determines that the time required for transferring the third image file is shorter, and transfers the first image file. 4. The information processing apparatus according to claim 1, wherein the first image file is transferred when it is determined that the time required for generation and transfer is shorter . 5. The image file generation means generates an image file by removing image data that overlaps with image data of another image file generated before the time of generating the image file. The information processing apparatus described. The image file generating means is a third image file in which the first time point is an image file generated immediately before the predetermined input signal, and a time point immediately after the third image file is generated. If the second time point is before the fourth time point, and the second time point is before the fifth time point, which is the time point when a predetermined time has elapsed from the fourth time point The information processing apparatus according to claim 5, wherein the first image file is generated by removing image data included between the first time point and the fourth time point. When the first time point is before the fifth time point, the image file generation means, except for the image data included between the first time point and the fourth time point, The information processing apparatus according to claim 6, wherein an image file including image data from a fourth time point to the fifth time point is generated. The image file transfer means transfers the image file generated by the image file generation means to an external device or a predetermined internal recording area via the communication line. The information processing apparatus according to any one of 7 . Said predetermined input signal, the information processing apparatus according to any one of claims 1 to 8, characterized in that the event detection signal from the sensor device for detecting the events that are connected via the communication line . Said predetermined input signal, the information processing apparatus according to any one of claims 1 to 9, characterized in that a motion detection signal from the imaging device. A method of controlling an information processing apparatus connected to at least one photographing apparatus via a communication line ,
An image data receiving means for receiving image data from the photographing apparatus;
A recording control step for recording the image data received in the image data receiving step on a recording medium;
The first time when the image file generating means receives a predetermined input signal from the image capturing device or another external device connected via the communication line using the image data recorded on the recording medium. A first image file that includes image data up to a second time point that is a predetermined time later than the first time point, and an image up to a third time point that is a predetermined time point elapsed from the first time point An image file generation step for individually generating a second image file including data;
An image file transfer step in which an image file transfer means transfers the first image file generated by the image file generation step, and then transfers the second image file;
A method for controlling an information processing apparatus, comprising: The program for making a computer perform the control method of the information processing apparatus of Claim 11 . A computer-readable recording medium on which the program according to claim 12 is recorded.

Images