JP2013251588A - Network camera system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network camera system which can acquire an image without defect at a server side even when a failure condition occurs.SOLUTION: When a failure condition occurs, a client 10 stops sending image data D taken by a camera part 11 to a server 20, and makes a client side storage unit 13 store the image data D taken during occurrence of the failure condition. By resolution of the failure condition, the client 10 sends the image data D stored in the client side storage unit 13 during occurrence of the failure condition and image data D taken after resolution of the failure condition to the server 20. The server 20 controls the image data D during occurrence of the failure condition and the image data D before and after occurrence of the failure condition as a series of image data D at a server side storage unit 23.

Description

  The present invention relates to a network camera system.

  In the network camera system described in Patent Document 1 below, a network camera is connected to a router via a hub (in addition to a network camera, an information processing terminal is also connected), thereby configuring a LAN. The router is connected to a communication network, and a terminal device (hereinafter also referred to as a user terminal) operated by a user, a relay server, and a recording / billing server are connected to the communication network. The user terminal has a function of transmitting a connection request to the relay server. Examples of the user terminal include a mobile terminal, a digital video recorder, and a personal computer having a camera function.

  In this system, the network camera periodically inquires of the relay server belonging to the external network whether there is a browsing request by the user terminal. When there is no browsing request from the user terminal, the relay server releases the connection (session) with the network camera each time. On the other hand, when there is a browsing request, the relay server maintains the connection. The network camera captures a subject while the connection with the relay server is maintained, and transmits the captured data to the relay server. Then, the relay server transmits the captured data to the user terminal.

  In this way, the user can view the subject image captured by the network camera in real time from a remote location by accessing the relay server.

JP 2010-57165 A JP 2010-93665 A Japanese Patent Laid-Open No. 2005-26866

  However, according to the network camera system of Patent Document 1, for example, when a failure occurs in the communication network, it is not possible to view the video captured by the network camera during the failure. On the other hand, the countermeasure technique at the time of communication failure is introduced in the above-mentioned patent documents 2 and 3.

  In the network surveillance camera system described in Patent Document 2, a plurality of network cameras are connected to a hub to form a LAN, and a recording medium is provided inside or outside each network camera. The hub is connected to an IP network, and a storage device is connected to the IP network.

  According to this system, normally, video information captured by each network camera is recorded in a recording device via an IP network. On the other hand, when trouble such as IP network communication failure or recording device failure occurs and video information cannot be recorded in the recording device, the video information of each network camera is recorded on a recording medium provided in each network camera. The

  According to the client server system described in Patent Document 3, a network camera having an FTP client function is connected to the FTP server via a network. In normal times, that is, when the network is normal, the network camera writes the imaging output obtained in real time as JPEG compressed image data at a predetermined time interval (for example, 6 seconds) in the backup memory unit of the network camera. Thereafter, the JPEG compressed image data is read from the backup memory unit and transmitted to the server.

  When the data transmission process ends normally, the network camera deletes the transmitted image data from the backup memory unit. On the other hand, if the data transmission process does not end normally, the network camera determines that a failure has occurred in the network, and stores the compressed image data to be transmitted to the server in the backup memory unit. Patent Document 3 also introduces extending the life of the backup memory unit by writing image data into the backup memory unit only when a network failure occurs.

  When the network is restored, the network camera transmits the image data stored in the backup memory unit when a failure occurs to the server. Specifically, the network camera writes newly obtained JPEG compressed image data in the backup memory unit at a predetermined time interval, and reads untransmitted image data from the backup memory unit and transmits it to the server.

  At this time, the network camera transmits untransmitted image data to the server in order from the oldest, that is, without destroying the time series. Alternatively, the network camera alternately transmits the image data in which the failure has occurred and the image data after the failure is restored, and the server re-sorts the received image data in time series using, for example, the imaging time information.

  However, in the system of Patent Document 2, video information during a period in which trouble occurs in the IP network or the like is still recorded in a recording medium provided in each network camera. For this reason, in the storage device connected to the IP network separately from the LAN formed by the network camera, video information during the trouble occurrence period is lost.

  In the system disclosed in Patent Document 3, the server can obtain only still image data.

  Further, in the system of Patent Document 2, it is necessary to provide a recording medium in each network camera, and in the system of Patent Document 3, an additional configuration is required for each network camera. For this reason, the increase in cost will be caused. In particular, as the number of cameras increases, the cost increases significantly.

  An object of the present invention is to provide a system capable of obtaining a video (in other words, a moving image) free from defects on the server side even when a failure state occurs. Another object of the present invention is to provide improved convenience and cost reduction for such a system.

  A network camera system according to an aspect of the present invention includes a client and a server. The client includes a camera unit, a client-side storage unit installed so as to be able to acquire video data captured by the camera unit, and the camera unit and the client-side storage unit installed on a LAN (Local Area Network) side. In addition, a WAN (Wide Area Network) side has a client side router connected to a communication line. The server is installed on the server side router in which the WAN side is connected to the communication line, and installed on the LAN side of the server side router so as to be able to acquire the video data photographed by the camera unit and transmitted from the client A server-side storage unit. The client transmits the video data to the server in order to save the video data in the server-side storage unit when a failure state in which the server-side storage unit cannot acquire the video data has not occurred. . Further, the client stops transmitting the video data to the server due to the occurrence of the failure state, and stores the video data captured during the occurrence of the failure state in the client-side storage unit. . In addition, when the failure state is resolved, the client stores the video data stored in the client-side storage unit during the occurrence of the failure state, and the video data captured after the failure state is resolved. To the server. The server manages the video data during the occurrence of the fault condition and the video data before and after the occurrence of the fault condition as a series of video data in the server-side storage unit.

  According to the above aspect, the client stores the video data captured during the occurrence of the failure state by the client, and transfers the video data to the server after the failure state is resolved. Then, the server manages the video data during the occurrence of the fault condition and the video data before and after the occurrence of the fault condition as a series of video data. For this reason, even if a failure state occurs, the video data can be complemented, and a video with no loss can be obtained.

  The objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description and the accompanying drawings.

FIG. 3 is a diagram for describing the configuration of the network camera system and the operation in a normal state according to the first embodiment. 6 is a diagram for explaining the operation in the fault state (self-detectable type) in the first embodiment. FIG. 6 is a diagram for explaining an operation in a failure state (notified type) in the first embodiment. FIG. FIG. 5 is a sequence diagram for explaining an operation when a failure occurs in the first embodiment (self-detectable type). FIG. 3 is a sequence diagram for explaining an operation at the time of solving a failure in the first embodiment (self-detectable type). FIG. 3 is a sequence diagram for explaining an operation when a failure occurs in the first embodiment (notified type). FIG. 6 is a sequence diagram for explaining an operation at the time of solving a failure in the first embodiment (notified type). 4 is a flowchart for explaining the operation of the server-side router in the first embodiment (self-detectable type). 4 is a flowchart for explaining the operation of the client side router in the first embodiment (self-detectable type). 4 is a flowchart for explaining the operation of the server side router in the first embodiment (notified type). FIG. 10 is a diagram for explaining the configuration of a network camera system and the operation in a normal state according to the second embodiment. FIG. 10 is a diagram for explaining an operation in a failure state (self-detectable type) in the second embodiment. FIG. 10 is a diagram for explaining an operation in a failure state (notified type) in the second embodiment.

<Embodiment 1>
<Outline of configuration>
FIG. 1 shows a block diagram of a network camera system 1 according to the first embodiment. Hereinafter, a case where the network camera system 1 is used for a surveillance camera system will be exemplified, but the use of the network camera system 1 is not limited to this. In the following description and drawings, names of various elements may be abbreviated in order to avoid complication of description.

  In the example of FIG. 1, the network camera system 1 includes a client 10 and a server 20, and the client 10 and the server 20 are installed to be communicable via a communication line 30. Here, the case where the communication line 30 is the Internet is illustrated, and the communication line 30 is also referred to as the Internet 30 using the same reference numeral 30. The communication line 30 may be an in-house LAN or the like. 1 illustrates a plurality of clients 10, but the number of clients 10 connected to the server 20 via the Internet 30 may be one.

  Each client 10 has a shooting function, and transmits data D of a shot video (in other words, a moving image) to the server 20. The server 20 receives the video data D transmitted from each client 10 via the Internet 30, and centrally manages the received video data D.

  As will be described in detail later, in the normal state, that is, in the normal state, the video data D is transmitted from the client 10 to the server 20 and stored in the server 20 as described above. 10 is temporarily stored. The temporarily stored video data D is transferred to the server 20 after the failure state is resolved.

<Configuration of client 10>
In the example of FIG. 1, the client 10 includes a camera unit 11, a client side storage unit 13, and a client side router 14. The camera unit 11 includes at least one camera 12 used as a surveillance camera, and three cameras 12 are illustrated in FIG. Each camera 12 is connected to a client side storage unit 13, and the client side storage unit 13 is connected to a client side router 14. More specific description will be given below.

  The camera 12 can be realized by a so-called network camera. According to this, the camera 12 has a moving image shooting function, a function of performing predetermined digital processing on the data D of the shot moving image (in other words, video), a function of outputting the digital video data D to the outside, and the like. . Here, by adding various modules to a so-called analog camera, the same function as that of the network camera may be realized, and the camera 12 may be realized by such a configuration. In the example of FIG. 1, the three cameras 12 are directly connected to the client-side storage unit 13, respectively. However, for example, a connection form that mediates a hub may be adopted.

  The client side storage unit 13 is installed so as to be able to acquire video data D taken by the camera unit 11. Specifically, in the example of FIG. 1, each camera 12 is connected to the client-side storage unit 13, whereby the client-side storage unit 13 can acquire the video data D directly from each camera 12. The client-side storage unit 13 temporarily stores the acquired video data D during the occurrence of a failure state (see FIGS. 2 and 3). In addition, although the client side memory | storage part 13 gives the example which does not preserve | save video data D in a normal state, it is not limited to this example.

  Here, the case where the client side memory | storage part 13 is implement | achieved by the recorder only for a surveillance camera system is illustrated. For this reason, the client-side storage unit 13 is also referred to as a client-side recorder 13, a recorder 13 or the like using the same reference numeral 13. The client recorder 13 incorporates a recording medium such as a hard disk (HDD), and the video data D acquired from the camera unit 11 is stored in the recording medium.

  The client side recorder 13 has an external communication function, and the communication port of the recorder 13 is connected to a LAN (Local Area Network) port of the client side router 14. A WAN (Wide Area Network) port of the router 14 is connected to the Internet 30. The client side router 14 can be realized by a so-called broadband router.

  According to the above connection form, the client-side recorder 13 and the camera unit 11 connected to the recorder 13 are installed on the LAN side of the client-side router 14.

  The external communication function of the client-side recorder 13 includes a transmission data generation function that processes the video data D acquired from the camera unit 11 into transmission data destined for the server 20 and sends the generated transmission data to the Internet 30. It is. If the camera 12 has such a transmission data generation function, the function of the camera 12 may be used.

<Configuration of Server 20>
In the example of FIG. 1, the server 20 includes a server-side router 21, a server body 22, and a server-side storage unit 23. The server side router 21 is connected to the server main body 22, and the server main body 22 is connected to the server side storage unit 23. More specific description will be given below.

  The server side router 21 can be realized by a so-called broadband router. The WAN port of the router 21 is connected to the Internet 30, and the LAN port of the router 21 is connected to the communication port of the server main body 22.

  Here, the server side router 21 and the client side router 14 have an IPsec-VPN (IP Security-Virtual Private Network) function, and the transfer of the video data D from the client 10 to the server 20 is performed by the IPsec-VPN. It is performed in an established state (see FIG. 1). In particular, by applying high-speed VPN, video data D captured by the camera 12 can be transferred as video data (in other words, video data).

  The server body 22 is a processing unit that provides various functions in the server 20, an external communication function via the communication port, and the like. The server body 22 can be realized by, for example, a personal computer in which a required program is installed and a display device.

  The external communication function of the server main body 22 includes a reception processing function for receiving transmission data (in other words, video data D) sent from the client 10 via the Internet 30 and the server side router 21. The server main body 22 stores the received video data D in the server-side storage unit 23. Thereby, the video data D photographed by each client 10 (more specifically, by each camera 12 of each client 10) is collected in the server 20 and is centrally managed in the server 20. The video data D may be reproduced in real time simultaneously with reception, or may be reproduced as necessary thereafter.

  The external communication function of the server main body 22 may include a remote control function of the client 10 and the like.

  Here, similarly to the client-side storage unit 13, the server-side storage unit 23 exemplifies a case where the server-side storage unit 23 is realized by a dedicated recorder for the monitoring camera system. For this reason, the server-side storage unit 23 is also referred to as a server-side recorder 23, a recorder 23, or the like using the same reference numeral 23. In addition, since the reception process of the video data D is performed by the server body 22, the server-side recorder 23 itself may not have an external communication function unlike the client-side recorder 13. In view of this point, the server-side storage unit 23 can be realized not by a dedicated recorder but by a general hard disk or the like.

  Note that the server-side recorder 23 and the server main body 22 may be housed in the same housing or in separate housings.

  Note that, according to the above connection form, the server-side recorder 23 is installed on the LAN side of the server-side router 21 together with the server body 22 and is installed so as to be able to acquire video data transmitted from the client 10. .

<System operation>
Hereinafter, the operation in the normal state and the operation related to the occurrence and elimination of the failure state will be described more specifically.

  Here, the normal state refers to a state in which the server-side recorder 23 can acquire the video data D taken by the client 10. On the other hand, the failure state refers to a state in which the server-side recorder 23 cannot acquire the video data D from the client 10. In the following, self-detectable type and notified type will be described as classification examples when the failure state is viewed from the client 10 side. However, it is not limited to this classification example.

  The self-detectable failure state 41 (see FIG. 2) refers to a failure state that the client-side router 14 itself can detect from the communication state between the client-side router 14 and the server-side router 21. That is, the self-detectable fault state 41 can be recognized by the client 10 itself. For example, a communication failure on the Internet 30 and a failure on the WAN side of the server side router 21 are included in the self-detectable type.

  On the other hand, even if the routers 14 and 21 can communicate normally, if a failure occurs on the LAN side of the server side router 21, the server side recorder 23 cannot acquire the video data D. The server side router 21 has a function of detecting the occurrence and resolution of a failure on its own LAN side, and notifies the client side router 14 of the detection result. That is, the notified failure state 42 (see FIG. 3) refers to a failure state that the client 10 can recognize by being notified from the server side router 21 to the client side router 14.

  4 and 5 are sequence diagrams for explaining the operations of the server-side router 21 and the client-side router 14 in relation to the self-detectable failure state 41. FIG.

  As shown in FIG. 4, after the system is started, the server side router 21 and the client side router 14 establish an IPsec-VPN between each other. Although illustration is omitted, the video data D is transmitted from the client 10 to the server 20 and stored in the server-side recorder 23 in a state where IPsec-VPN is established.

  After establishing the IPsec-VPN, the server-side router 21 periodically sends a KeepAlive request M1, and when the client-side router 14 receives the request M1, it returns a KeepAlive response M2. Similarly, the client side router 14 periodically transmits a KeepAlive request M3, and when the server side router 21 receives the request M3, it returns a KeepAlive response M4. 4 and 5, it is assumed that the response codes of the KeepAlive responses M2 and M4 are normal.

  However, when a failure occurs in the Internet 30, the KeepAlive requests M1 and M3 do not reach the destination routers 14 and 21. For this reason, the routers 14 and 21 do not transmit the KeepAlive responses M2 and M4. That is, if the routers 21 and 14 cannot receive the KeepAlive responses M2 and M4 from the other party within a predetermined time, the routers 21 and 14 determine that the self-detectable failure state 41 has occurred.

  When the routers 21 and 14 recognize the occurrence of the failure state 41, the routers 21 and 14 disconnect the IPsec-VPN. The client side router 14 switches the storage destination of the video data D taken by the camera 12 from the server side recorder 23 to the client side recorder 13. More specifically, the client side router 14 stops sending the video data D to the server 20 and instructs the client side recorder 13 to save the video data D.

  As shown in FIG. 5, when the failure state 41 is resolved and the Internet 30 is restored, the KeepAlive requests M1 and M3 reach the destination routers 14 and 21. Thereby, the routers 14 and 21 transmit the KeepAlive responses M2 and M4. That is, the routers 21 and 14 determine that the failure state 41 has been resolved by receiving the KeepAlive responses M2 and M4 from the other party.

  When the routers 21 and 14 recognize the cancellation of the failure state 41, the routers 21 and 14 establish the IPsec-VPN. Further, the client side router 14 switches the storage destination of the video data D taken by the camera 12 from the client side recorder 13 to the server side recorder 23. More specifically, the client side router 14 resumes transmission of the video data D, and the video data D stored in the client side recorder 13 during the occurrence of the failure state 41 and the image taken after the failure state 41 is resolved. The transmitted video data D is transmitted to the server. According to the high-speed VPN, it is possible to simultaneously transmit the video data D in which the failure state 41 is occurring and the video data D after the failure state 41 is resolved. Then, the server 20 manages the video data D during the occurrence of the failure state 41 and the video data D before and after the occurrence of the failure state 41 as a series of video data D by the server-side recorder 23.

  6 and 7 are sequence diagrams for explaining the operations of the server-side router 21 and the client-side router 14 in relation to the notified failure state 42. FIG.

  Even if a failure occurs on the LAN side of the server 20, the routers 21 and 14 can communicate with each other, and the transmission and reception of the KeepAlive requests M1 and M3 and the KeepAlive responses M2 and M4 can be executed. 6 and 7, it is assumed that the response codes of the KeepAlive responses M2 and M4 are normal.

  For this reason, as shown in FIG. 6, when the server side router 21 detects that a failure has occurred on its own LAN side and the video data D cannot be stored in the server side recorder 23, the server side router 21 A failure occurrence notification M5 is transmitted. The client-side router 14 recognizes the occurrence of the notified failure state 42 by receiving the failure occurrence notification M5. Thereafter, as in the case of the self-detectable failure state 41 (see FIG. 4), the client-side router 14 switches the storage destination of the video data D captured by the camera 12 from the server-side recorder 23 to the client-side recorder 13. .

  As shown in FIG. 7, thereafter, when the server side router 21 detects the cancellation of the failure state 42, it transmits a failure cancellation notification M <b> 6 to the client side router 14. The client side router 14 recognizes the cancellation of the failure state 42 by receiving the failure cancellation notification M6. Thereafter, the client-side router 14 switches the storage destination of the video data D from the client-side recorder 13 to the server-side recorder 23 as in the case of the self-detectable failure state 41 (see FIG. 5). As a result, the server 20 manages the video data D during the occurrence of the failure state 42 and the video data D before and after the occurrence of the failure state 42 as a series of video data D by the server-side recorder 23.

  In relation to the self-detectable failure state 41, FIG. 8 shows a flowchart of the operation of the server side router 21, and FIG. 9 shows a flowchart of the operation of the client side router 14.

  First, the operation of the server side router 21 will be described with reference to FIG. The server side router 21 establishes IPsec-VPN with the client side router 14 in step S201 after the system is started. After establishing the IPsec-VPN, the server side router 21 transmits a KeepAlive request M1 in step S202. In step S203, the server side router 21 determines whether or not the KeepAlive response M2 has been received from the client side router 14 within a predetermined time. As a result of the determination, if it can be received, step S204 is executed, and if it cannot be received, step S207 is executed.

  In step S204, the server side router 21 determines whether or not the received response code of the KeepAlive response M2 is normal. If the result of the determination is normal, step S205 is executed, and if it is not normal, step S207 is executed.

  In step S205, it is determined whether IPsec-VPN is disconnected at that time. As a result of the determination, if the IPsec-VPN is not in a disconnected state (that is, if IPsec-VPN is in an established state at that time), the server side router 21 returns to the KeepAlive request transmission step S202. On the other hand, if the IPsec-VPN is in a disconnected state at the time of step S205, the server side router 21 establishes the IPsec-VPN in step S206, and then returns to the KeepAlive request transmission step S202.

  As described above, when it is determined No in steps S203 and S204, step S207 is executed. In step S207, it is determined whether IPsec-VPN is established at that time. As a result of the determination, if the IPsec-VPN is in an established state, the server-side router 21 disconnects the IPsec-VPN in step S208, and then returns to the KeepAlive request transmission step S202. On the other hand, when the IPsec-VPN is not established at the time of step S207 (that is, when IPsec-VPN is in a disconnected state at that time), the server side router 21 returns to the KeepAlive request transmission step S202.

  Next, the operation of the client side router 14 will be described with reference to FIG. As can be seen by comparing FIG. 9 with FIG. 8, the client side router 14 executes steps S101 to S108 similar to steps S201 to S208, and further executes steps S109 and S110.

  Specifically, the client-side router 14 executes Step S109 after establishing IPsec-VPN in Step S106 corresponding to Step S206. In step S109, the client side router 14 switches the storage destination of the video data D taken by the camera 12 to the server side (that is, the server side recorder 23). Thereafter, the client side router 14 returns to the KeepAlive request transmission step S202.

  Further, the client side router 14 executes Step S110 after disconnecting the IPsec-VPN in Step S108 corresponding to Step S208. In step S110, the client side router 14 switches the storage destination of the video data D taken by the camera 12 to the client side (that is, the client side recorder 13). Thereafter, the client side router 14 returns to the KeepAlive request transmission step S202.

  The specific processing contents in the storage destination switching steps S109 and S110 are as described above with reference to FIGS.

  FIG. 10 is a flowchart of the operation of the server side router 21 in relation to the notified failure state 42. The flow in FIG. 10 is executed as an interrupt process when the server side router 21 detects a state change on its own LAN side.

  According to the flow of FIG. 10, the server side router 21 determines the type of state change on the LAN side in step S221. If it is determined that a failure has occurred on the LAN side, the server side router 21 notifies the client side router 14 of the occurrence of the notified failure state 42 in step S222. On the other hand, if it is determined in step S221 that the failure has been resolved on the LAN side, the server side router 21 notifies the client side router 14 of the cancellation of the notified failure state 42 in step S223.

  The operation of the client side router 14 when these notifications are received is as described above with reference to FIGS.

<Effect>
According to the network camera system 1, the client 10 stores the video data D captured during the occurrence of the failure state by the client 10 itself, and transfers it to the server 20 after the failure state is resolved. Then, the server 20 manages the video data during the occurrence of the fault condition and the video data before and after the occurrence of the fault condition as a series of video data. For this reason, even if a failure state occurs, the video data D can be complemented, and a video with no loss can be obtained.

  In addition, occurrence and resolution of a failure state is determined by the client side router 14, and switching of the storage destination of the video data D is controlled by the client side router 14. For this reason, it is not necessary to provide those functions in the camera part 11, for example. Thereby, the structure of the camera part 11 can be simplified and the cost of the camera part 11 can be suppressed. Such an effect becomes more prominent as the number of cameras 12 provided in the camera unit 11 increases. In addition, for example, by introducing the client side router 14 and the server side router 21 into an existing facility, a system having the above effects can be easily constructed. In this case, the cost of system construction can be suppressed by the effective use of existing equipment.

<Embodiment 2>
FIG. 11 shows a block diagram of network camera system 1B according to the second embodiment. FIG. 11 is also a diagram for explaining the operation of the system 1B in a normal state. FIG. 12 shows an operation explanatory diagram in the self-detectable failure state 41, and FIG. 13 shows an operation explanatory diagram in the notified-type failure state.

  The network camera system 1B includes a client 10B and a server 20, and the client 10B and the server 20 are installed so as to be communicable via a communication line 30. The server 20 is configured in the same manner as in the first embodiment. Further, the Internet is exemplified as the communication line 30 as in the first embodiment. Further, the number of clients 10B is not limited to the example of FIG. Further, both the clients 10 and 10B according to the first and second embodiments may be provided for the server 20.

  In the example of FIG. 11, the client 10B includes a camera unit 11, a client-side storage unit 13B, and a client-side router 14.

  The camera unit 11 and the router 14 are configured in the same manner as in the first embodiment, but unlike the first embodiment, each camera 12 of the camera unit 11 is connected to the LAN port of the router 14. Each camera 12 has a transmission data generation function for processing captured video data D into transmission data destined for the server 20 and sending the generated transmission data to the Internet 30 in the same manner as a general network camera. It shall have.

  The client-side storage unit 13B is installed so as to be able to acquire video data D taken by the camera unit 11. Specifically, the client-side storage unit 13B is connected to a LAN port, a USB (Universal Serial Bus) port, or the like of the client-side router 14, so that the client-side storage unit 13B can be connected to each camera 12 via the router 14. Video data D can be acquired (see FIGS. 12 and 13). The client-side storage unit 13B temporarily stores the acquired video data D during the occurrence of a failure state (see FIGS. 12 and 13). Note that although the client-side storage unit 13B does not store the video data D in the normal state, the example is not limited to this example.

  Here, in the first embodiment, the case where the client-side storage unit 13 is realized by a recorder dedicated to the surveillance camera system is exemplified. In the second embodiment, the client-side storage unit 13B is generally used as a personal computer or the like. An example realized by an external hard disk (HDD) used in the above will be described. For this reason, the client-side storage unit 13B is also referred to as a client-side hard disk 13B, a hard disk 13B, an HDD 13B, etc., using the same reference numeral 13B.

  According to the above connection form, the WAN side of the client side router 14 is connected to the Internet 30, and the camera unit 11 and the client side hard disk 13 </ b> B are installed on the LAN side of the router 14. The client-side hard disk 13B is connected to the client-side router 14 without going through the camera unit 11.

  The client 10B operates in the same manner as the client 10 according to the first embodiment. However, in the client 10B, the video data D captured by the camera 12 during the occurrence of the failure states 41 and 42 is stored in the client-side hard disk 13B under the storage destination switching control by the router 14.

  Therefore, the network camera system 1B also has the same effect as the system 1 according to the first embodiment.

  In particular, according to the network camera system 1B, the client-side hard disk 13B can be attached to and detached from the client-side router 14 without removing the camera unit 11 from the client-side router 14. Therefore, as compared with the system 1 according to the first embodiment, the client side storage unit can be easily replaced or added. For example, even if the failure becomes longer, the storage of the video data D can be continued by replacing the client-side hard disk 13B. Thus, high convenience is obtained.

  Further, by using a general hard disk as the client-side storage unit 13B, it contributes to cost reduction as compared with a dedicated recorder.

<Modification>
It should be noted that the present invention can be freely combined with each other within the scope of the invention, and each embodiment can be appropriately modified or omitted.

  1, 1B network camera system, 10, 10B client, 11 camera unit, 12 camera, 13, 13B client side storage unit, 14, 14B client side router, 20 server, 21 server side router, 22 server body, 23 server side storage Part, 30 communication line, 41 self-detectable failure state, 42 notified failure state, D video data.

Claims (3)

A camera unit, a client-side storage unit installed so as to be able to acquire video data captured by the camera unit, and the camera unit and the client-side storage unit are installed on a LAN (Local Area Network) side and WAN (Wide (Area Network) side having a client side router connected to the communication line,
A server side router in which the WAN side is connected to the communication line, and a server side installed on the LAN side of the server side router and installed so as to be able to acquire the video data photographed by the camera unit and transmitted from the client A server having a storage unit,
The client
In the case where a failure state in which the server-side storage unit cannot acquire the video data has not occurred, the video data is transmitted to the server to be stored in the server-side storage unit,
Due to the occurrence of the failure state, the transmission of the video data to the server is stopped, and the video data captured during the occurrence of the failure state is stored in the client-side storage unit,
When the failure state is resolved, the video data stored in the client-side storage unit during the occurrence of the failure state and the video data captured after the failure state is resolved are transmitted to the server,
The server
Managing the video data during the occurrence of the fault condition and the video data before and after the occurrence of the fault condition as a series of video data in the server-side storage unit;
Network camera system.   When the client-side router recognizes the occurrence and elimination of the failure state by the client-side router itself or by being notified from the server-side router, the client-side router stores the video data storage destination. The network camera system according to claim 1, wherein the switching of the network camera is controlled.   The network camera system according to claim 1, wherein the client-side storage unit is connected to the client-side router without passing through the camera unit.

Images