JP7525877B2 - Recorder management system and recorder management method - Google Patents

Description

This disclosure relates to a recorder management system and a recorder management method.

Patent document 1 discloses a hard disk recording device that records received programs onto a hard disk based on recording reservation data. When the hard disk recording device itself is in standby mode and there is sufficient time until the start of the next scheduled recording to allow for more than the time required for self-diagnosis, the hard disk recording device performs a self-diagnosis to detect whether there is an abnormality in the hard disk.

JP 2006-18963 A

However, in Patent Document 1, when the hard disk recording device records video data, for example from a surveillance camera that records continuously or for long periods of time, it is inconvenient because recording cannot be made on the hard disk recording device while the self-diagnosis is being performed, and there is a possibility that the accuracy of surveillance may decrease.

The present disclosure has been devised in consideration of the above-mentioned conventional circumstances, and aims to provide a recorder management system and a recorder management method that can provide users with warnings regarding hard disks used to record video captured by surveillance cameras and assist users in their surveillance work.

The present disclosure provides a recorder management system in which a recorder and a management server are connected to each other so that they can communicate with each other, the recorder transmits identification information capable of individually identifying one or more hard disks capable of recording surveillance camera images to the management server, the management server stores a hard disk list including the identification information of each of a plurality of hard disks registered as targets for warning and warning information corresponding to each of the identification information, and when a predetermined event occurs and it is determined that the identification information transmitted from the recorder is included in the hard disk list, the management server transmits warning information corresponding to the identification information to the recorder, and the recorder outputs the warning information transmitted from the management server to a monitor.

The present disclosure also provides a recorder management method executed by a system in which a recorder and a management server are connected to each other so that they can communicate with each other, wherein the recorder reads out identification information capable of individually identifying one or more hard disks capable of recording video captured by a surveillance camera, and when a specified event occurs, the management server determines whether the identification information is present in a hard disk list including the identification information of each of a plurality of hard disks registered as targets for warning and warning information corresponding to each of the identification information, and when the management server determines that the identification information is present in the hard disk list, the recorder generates a warning screen based on the warning information corresponding to the identification information and outputs it to a monitor.

According to the present disclosure, it is possible to provide users with warnings regarding hard disks used to record video captured by surveillance cameras, thereby assisting users in their surveillance work.

FIG. 1 is a diagram for explaining an example of the overall configuration of a recorder management system according to a first embodiment; FIG. 1 is a sequence diagram showing a first example of an operation procedure of the recorder management system according to the first embodiment; FIG. 11 is a sequence diagram showing a second example of an operation procedure of the recorder management system according to the first embodiment. A diagram showing an example of a hard disk warning screen FIG. 11 is a sequence diagram showing a third example of an operation procedure of the recorder management system according to the first embodiment. A diagram showing an example of a hard disk warning screen FIG. 11 is a sequence diagram showing a fourth example of an operation procedure of the recorder management system according to the second embodiment.

(Background to this disclosure)
For example, a hard disk manufacturer may collect information (such as lot number, model, details of the defect, etc.) on hard disks that have been sold and have many defects. In such a case, if the hard disk used by a user is defective or has many defects, the customer service department of the manufacturer may wish to provide the user with warning information regarding the hard disk or to suggest replacing or buying a new one.

Below, with reference to the drawings as appropriate, each embodiment that specifically discloses the configuration and operation of the recorder management system and recorder management method according to the present disclosure will be described in detail. However, more detailed explanation than necessary may be omitted. For example, detailed explanation of already well-known matters and duplicate explanation of substantially identical configurations may be omitted. This is to avoid the following explanation becoming unnecessarily redundant and to make it easier for those skilled in the art to understand. Note that the attached drawings and the following explanation are provided to enable those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims.

(Embodiment 1)
1 is a diagram showing an example of the overall configuration of a recorder management system 100 according to the first embodiment. The recorder management system 100 according to the first embodiment is a system that acquires information about a hard disk inserted into each of a plurality of recorders R1, R2, R3, ... that are connected via a network NW and record images captured by a surveillance camera, and notifies (presents) the user of the recorder (for example, a management company of the base BS1, a person belonging to a security company, an administrator monitoring the surveillance cameras C1, ..., CN, etc.) of the attention information previously stored in association with the hard disk when it is determined that the acquired hard disk is a hard disk that requires attention. The recorder management system 100 is configured to include at least a management server S1, a plurality of recorders R1, ..., and a network NW.

In the recorder management system 100 according to the first embodiment, as an example, an example is shown in which it is determined whether or not there is warning information corresponding to a hard disk inserted into each of the recorders R1, .... However, each of the recorders R1, ... may have, instead of a hard disk, for example, an SSD (Solid State Drive) inserted (used) as a built-in storage medium (media). In such a case, the recorder management system 100 according to the first embodiment may replace the hard disk (HDD) with warning information (see below) corresponding to the SSD and determine whether or not there is warning information corresponding to the SSD. If it is determined that the SSD is a storage medium that requires warning, it may notify (present) the user of the recorder of the warning information previously stored in association with the SSD.

In the example of the overall configuration of the recorder management system 100 shown in FIG. 1, the recorder R1 and the terminal device P1 including the operation unit OP and the monitor MN1 are configured separately and connected to enable communication, but for example, the recorder R1 may be configured integrally with the terminal device P1 and connected to enable communication between the operation unit OP and the monitor MN1.

Base BS1 indicates, for example, a facility, a building such as a store, or a management area managed by a user. At base BS1, a recorder R1, a terminal device P1, a PoE (Power over Ethernet) hub PH, and multiple surveillance cameras C1, C2, ..., CN are installed. Note that the number of surveillance cameras and recorders installed may be one or more.

The recorder R1 records the images captured by the surveillance cameras C1, ..., CN on one or more hard disks 13A inserted by the user. The recorder R1 is communicably connected to the terminal device P1 via a wired cable such as an HDMI (High-Definition Multimedia Interface) (registered trademark) cable or a connector such as an HDMI (registered trademark) connector, and transmits the captured images to the terminal device P1. In the example shown in FIG. 1, one recorder R1 is installed at the base BS1, but multiple recorders may be installed. The recorder R1 includes a communication unit 10, a processor 11, a memory 12, and at least one hard disk 13A.

The communication unit 10 is connected to the terminal device P1, each of the multiple surveillance cameras C1, ..., CN, and the PoE hub PH so as to be able to communicate by wire or wirelessly. The communication unit 10 is also connected to the management server S1 via the network NW so as to be able to communicate by wire or wirelessly. The wireless communication referred to here is, for example, short-range wireless communication such as Bluetooth (registered trademark) or NFC (registered trademark), or communication via a wireless LAN (Local Area Network) such as Wi-Fi (registered trademark).

The communication unit 10 transmits the hard disk information output from the processor 11 to the management server S1. The communication unit 10 also outputs the captured images transmitted from each of the multiple surveillance cameras C1, ..., CN to the processor 11 via the PoE hub PH. The communication unit 10 outputs the warning information regarding the recorder R1 transmitted from the management server S1 to the processor 11.

The hard disk information referred to here is information that can individually identify each of the hard disks 13A, ..., and is S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) information. In addition to S.M.A.R.T. information, the hard disk information may also include information about the hard disk, such as the hard disk model number, the hard disk serial number, or information about the manufacturer that manufactured the hard disk.

The processor 11 is configured using, for example, a CPU (Central Processing unit) or an FPGA (Field Programmable Gate Array) and performs various processes and controls in cooperation with the memory 12. Specifically, the processor 11 references the programs and data stored in the memory 12 and executes the programs to realize the functions of each unit. The functions referred to here are, for example, a function to read hard disk information from the hard disks 13A, ..., a function to record the images captured by each of the multiple surveillance cameras C1, ..., CN on the hard disks 13A, ..., a function to transmit the read hard disk information to the management server S1 via the communication unit 10, a function to transmit warning information to the terminal device P1, etc.

Memory 12 has, for example, a RAM (Random Access Memory) as a work memory used when executing each process of processor 11, and a ROM (Read Only Memory) that stores programs and data that define the operation of processor 11. Data or information generated or acquired by processor 11 is temporarily stored in the RAM. Programs that define the operation of processor 11 are written in the ROM. Memory 12 stores hard disk information for each of the currently inserted hard disks 13A, ....

The hard disks 13A, ... record the images captured by each of the multiple surveillance cameras C1, ..., CN. The hard disks 13A, ... are inserted into the recorder R1 by the user and are provided in the recorder R1, and are capable of recording the captured images. When the hard disks 13A, ... are inserted into the recorder R1, the processor 11 reads out the hard disk information.

The PoE hub PH supplies power to each of the multiple surveillance cameras C1, ..., CN from an external commercial power source. The PoE hub PH may obtain power directly from the external commercial power source. The PoE hub PH may also include a battery (e.g., a cell) capable of storing charge supplied from the external commercial power source, or may be configured to be removable, and may be capable of supplying power to each of the multiple surveillance cameras C1, ..., CN even when disconnected from the external commercial power source.

The terminal device P1 is, for example, a PC (Personal Computer), a notebook PC, a tablet terminal, etc., and is operated by the user of the recorder R1. The terminal device P1 is connected to the recorder R1 that recorded the captured video so as to be able to communicate data with it via a wired cable such as a USB cable, or a connector such as a USB connector. The terminal device P1 is also connected to the management server S1 via the network NW so as to be able to communicate with it via wired or wireless communication. Note that the wireless communication referred to here is communication via a wireless LAN such as Wi-Fi (registered trademark). The terminal device P1 is configured to include an operation unit OP and a monitor MN1.

The operation unit OP is a so-called user interface, and is composed of, for example, a mouse, a touch panel, a keyboard, etc. The operation unit OP accepts user operations and converts them into signals.

The monitor MN1 is configured, for example, using an LCD (Liquid Crystal Display) or an organic EL (Electroluminescence). The monitor MN1 displays warning information regarding any of the hard disks transmitted from the recorder R1.

Each of the multiple surveillance cameras C1, ..., CN is installed indoors or outdoors and captures the area to be monitored. Each of the multiple surveillance cameras C1, ..., CN may capture the area to be monitored at all times, or may capture the area to be monitored only during a time period preset by the user. Each of the multiple surveillance cameras C1, ..., CN is connected to the recorder R1 via the PoE hub PH so that data communication is possible.

The management server S1 is connected to the terminal device P2 and each of the multiple recorders R1, ... via a network NW so that data can be communicated between them. The management server S1 has a management list database 23 managed by an administrator who operates the terminal device P2. The management server S1 is configured to include a communication unit 20, a processor 21, a memory 22, and a management list database 23.

The communication unit 20 is connected to the terminal device P2 and each of the multiple recorders R1, ... via the network NW so that data communication is possible. The communication unit 20 outputs to the processor 21 hard disk information of each of the multiple recorders R1, ... transmitted from each of the multiple recorders R1, ..., control commands transmitted from the terminal device P2, etc. The communication unit 20 also transmits the warning information output from the processor 21 to the recorder to which the warning is to be sent via the network NW. Note that the warning recorder here refers to the recorder that transmitted the hard disk information that was determined by the processor 21, described below, to be a hard disk that requires warning.

The processor 21 is configured using, for example, a CPU or FPGA, and performs various processes and controls in cooperation with the memory 22. Specifically, the processor 21 references the programs and data stored in the memory 22 and executes the programs to realize the functions of each section. The functions referred to here are, for example, a function to add the hard disk information and warning information sent from the terminal device P2 to the hard disk list stored in the management list database 23 (i.e., to update the hard disk list), a function to determine whether the hard disk information acquired via the network NW is in the hard disk list, and a function to transmit warning information corresponding to the hard disk information to the recorder that transmitted the hard disk information if it is determined that the hard disk information is in the hard disk list.

The processor 21 acquires hard disk information transmitted from each of the multiple recorders R1, .... The processor 21 compares the acquired hard disk information with each of the multiple hard disk information stored in the management list database 23, and determines whether or not the hard disk indicated by the acquired hard disk information is a hard disk that requires attention (i.e., a hard disk that is the target of the attention).

Specifically, the processor 21 acquires the lot number for each hard disk contained in the hard disk information from the hard disk information (e.g., S.M.A.R.T. information) transmitted from each of the multiple recorders R1, .... The processor 21 compares the acquired lot number for each hard disk with the lot number for each hard disk registered in the hard disk list, and determines whether or not the hard disk indicated by the acquired hard disk information is a hard disk that requires attention (i.e., a hard disk that is the target of attention). Note that the comparison (determination) process performed by the processor 21 is not limited to the lot number. For example, if the hard disk information transmitted from each of the multiple recorders R1, ... includes a user ID, a hard disk product number, a serial number, manufacturer information, etc., the processor 21 may combine these pieces of information, or combine these pieces of information with the lot number, to perform the comparison (determination) process.

When the processor 21 determines that the acquired hard disk information exists in each of the multiple hard disk information stored in the management list database 23 (i.e., when it determines that the hard disk is one that requires attention), it outputs the attention information stored in association with this hard disk information as a collation result to the communication unit 20. Note that the attention information referred to here includes information about a failure or defect that has occurred in a hard disk having the same model, the same product number, or the same lot number, information recommending the replacement or purchase of a hard disk, etc., and is generated, for example, as a CGI (Common Gateway Interface) command.

In addition, when the processor 21 determines that the acquired hard disk information exists in each of the multiple hard disk information registered (stored) in the management list database 23, the processor 21 may transmit warning information generated as a result of the comparison to the terminal device P2.

The memory 22 has, for example, a RAM as a work memory used when executing each process of the processor 21, and a ROM (Read Only Memory) that stores programs and data that define the operation of the processor 21. The RAM temporarily stores data or information generated or acquired by the processor 21. The ROM has written therein the programs that define the operation of the processor 21.

The management list database 23 registers (stores) the hard disk information to be alerted, which is sent from the terminal device P2, and the alert information to be notified (presented) to the user, in association with the hard disk information. The management list database 23 shown in FIG. 1 shows an example of a configuration in which it is configured integrally with the management server S1, but it may be configured as a separate entity connected to the terminal device P2 and the management server S1 via the network NW so that data communication is possible. If each of the recorders R1, ... is a device into which an SSD can be inserted, the management list database 23 may register (store) the SSD information to be alerted to and the alert information to be notified (presented) to the user, in association with the SSD information.

The terminal device P2 is, for example, a PC (Personal Computer), and is connected to the management server S1 via the network NW so that it can communicate with the management server S1. The terminal device P2 is operated by an administrator of the management server S1 (for example, an employee of the manufacturer of the recorders R1, ..., a person in the customer service department, an employee of the management company that manages the recorders R1, ..., etc.) to update the hard disk list (i.e., hard disk information and warning information) registered (stored) in the management list database 23. The terminal device P2 also has a monitor (not shown) that displays warning information corresponding to the hard disk information included in the hard disk list sent from the management server S1 and presents it to the administrator.

Each of the multiple recorders R2, R3, etc. is installed at one or more different bases from base BS1 and is managed by other users. Note that each of the multiple recorders R2, R3, etc. has a similar configuration to recorder R1, so a description thereof will be omitted.

The network NW connects each of the multiple recorders R1, ... to the management server S1, and between the management server S1 and the terminal device P2 so that data communication is possible.

The first operation procedure of the recorder management system 100 according to the first embodiment will be described with reference to FIG. 2. FIG. 2 is a sequence diagram showing an example of the first operation procedure of the recorder management system 100 according to the first embodiment.

First, we will explain the continuous update process RP for the management list database 23. The recorder management system 100 executes the continuous update process RP by processing steps St1 to St3, which are described below.

The terminal device P2 receives hard disk information requiring attention and attention information corresponding to this hard disk information through operation by the administrator of the management server S1 (St1). The terminal device P2 transmits the hard disk information and the attention information to the management server S1 (St2).

The management server S1 registers (stores) the hard disk information and warning information sent from the terminal device P2 in the management list database 23, and updates the management list database 23 (St3).

The recorder R1 detects that a new hard disk has been inserted (added) by the user (St10).

When a hard disk is added by the user, the recorder R1 reads the hard disk information of the added hard disk (hereafter referred to as "additional hard disk information") (St11).

The recorder R1 transmits the read additional hard disk information to the management server S1 via the network NW (St12).

The management server S1 acquires the additional hard disk information sent from the recorder R1 (St13). The management server S1 executes a comparison (determination) process to determine whether the acquired hard disk information exists in each of the multiple hard disk information registered (stored) in the management list database 23 (St14).

As an example of the determination process executed in step St14, the management server S1 determines whether the lot number for each hard disk transmitted from the recorder R1 is included in each of the lot numbers of the multiple hard disks registered (stored) in the management list database 23. Note that the determination process executed in step St14 may be executed by comparing the lot numbers in the hard disk information, or may be executed by, for example, combining and comparing each of the multiple pieces of information included in the hard disk information.

If the management server S1 determines in the processing of step St14 that each of the multiple hard disk information contains additional hard disk information (St14, YES), it transmits warning information (CGI command) corresponding to this additional hard disk information to the recorder R1 (St15).

On the other hand, if the management server S1 determines in the processing of step St14 that there is no additional hard disk information for any of the multiple hard disk information (St14, NO), it transmits notification information (CGI command) to the recorder R1 to notify that there is no warning information (CGI command) corresponding to the additional hard disk information as a result of the comparison (St16). In addition, the management server S1 may omit the processing of step St16 described above and terminate the processing of the recorder management system 100 (St17).

The recorder R1 sends warning information (CGI command) corresponding to the additional hard disk information sent from the management server S1 to the terminal device P1 (St18).

The terminal device P1 generates a warning screen SC1 (see FIG. 4) based on the warning information transmitted from the recorder R1 and displays it on the monitor MN1 (St19).

As described above, the recorder management system 100 in the first example operation procedure according to embodiment 1 can collect hard disk information for each hard disk when a new hard disk is inserted (added) into each of the multiple recorders R1, ..., and can present the user with warning information corresponding to the inserted (added) hard disk. Therefore, the user can check the warning information corresponding to the added hard disk more quickly before recording the video captured by each of the multiple surveillance cameras C1, ..., CN.

Next, the second operation procedure of the recorder management system 100 according to the first embodiment will be described with reference to FIG. 3. FIG. 3 is a sequence diagram showing an example of the second operation procedure of the recorder management system 100 according to the first embodiment. Note that in the sequence diagram shown in FIG. 3, the processing in steps St14 to St19 is similar to the processing described in the first operation procedure shown in FIG. 2, and therefore a description thereof will be omitted.

In the second operation procedure example shown in FIG. 3, the management server S1 also executes the constantly running update process RP for the management list database 23. When the management list database 23 is updated, the management server S1 in the second operation procedure example generates a control signal requesting the reading and transmission of all currently inserted hard disk information, and transmits this to each of the multiple recorders R1, ... (St20).

In the following explanation of the second operation procedure, only an example will be explained in which the management server S1 determines whether or not all hard disk information inserted (equipped) in the recorder R1 is in the management list database 23, and the explanation of each of the other recorders R2, ... will be omitted.

Based on the control signal sent from the management server S1, the recorder R1 reads out all hard disk information currently inserted (equipped) in the recorder R1 (St21).

The recorder R1 transmits all of the hard disk information that it has read to the management server S1 via the network NW (St22).

The management server S1 acquires each of all hard disk information sent from the recorder R1 (St23). The management server S1 executes a comparison (determination) process to determine whether the acquired hard disk information is included in each of the multiple hard disk information registered (stored) in the management list database 23 (St14).

In addition, if there is a notification destination of the warning information set in advance by the user, the recorder R1 generates and transmits a warning notification (e.g., an email or summary notification) including the warning information to the notification destination (e.g., a terminal device such as a smartphone, tablet terminal, or other computer owned by the user, or a terminal device such as a smartphone, tablet terminal, or other computer owned by a person who manages the recorder R1 like the user) (St24). Note that the processing of step St24 is not limited to the second operation procedure. The recorder R1 may execute the processing of step St24 in the first operation procedure as well as in the second operation procedure example of the recorder management system 100 according to embodiment 1.

As described above, the recorder management system 100 in the second operation procedure example of the first embodiment can determine whether or not each of the hard disks inserted (equipped) in each of the recorders R1, ... that are connected so as to be capable of data communication is a hard disk that requires a warning when the management list database 23 is updated by the administrator. Therefore, the user can obtain the latest warning information about the hard disks used in the recorders.

Furthermore, in the second example operation procedure according to embodiment 1, if there is a notification destination for warning information that has been set in advance by the user, the recorder management system 100 can generate and send an email or summary notification including the warning information to this notification destination. This allows the user to check the warning information without being limited by time or place.

Referring to FIG. 4, the warning screen SC1 displayed on the monitor MN1 of the terminal device P1 based on the warning information transmitted from the management server S1 will be described. FIG. 4 is a diagram showing an example of a warning screen SC1 related to a hard disk. Note that the warning screen SC1 shown in FIG. 4 shows an example in which a live video VD1 of a surveillance camera indicated by "CAM4" among the multiple surveillance cameras C1, ..., CN is displayed, but it goes without saying that each of the multiple live videos may be displayed simultaneously. Furthermore, the captured video displayed on the warning screen SC1 is not limited to live video, and may be, for example, captured video recorded on the recorder R1 (i.e., past video).

The warning screen SC1 is a screen for presenting warning information transmitted from the management server S1 to the user, and is generated by the terminal device P1 and displayed on the monitor MN1. When the history display button BT1 is selected (pressed) by a user operation, the terminal device P1 displays a list of each piece of history information indicating the warning information transmitted from the recorder R1 in the error history column LT1. In addition, when the setting button BT2 is selected (pressed) by a user operation, the warning screen SC1 displays a warning screen SC2 (see Figure 6) on the monitor MN1 that displays a list of whether or not warning information has been received for each hard disk 13A, ....

The error history column LT1 is displayed including at least occurrence date and time information LT10 indicating the timing (date and time) when it was determined that the hard disk required attention, and content information LT11 indicating an overview of each piece of attention information. For example, the latest attention information LT12 indicated by "No. 1" in the error history column LT1 shown in FIG. 4 indicates that it was determined that the hard disk required attention on "2020/04/13 13:33:42", and the content of the attention information is "HDD operation warning". It goes without saying that the content of the attention information shown in FIG. 4 is an example and is not limited to this.

When the user selects (presses) any piece of warning information, the terminal device P1 displays a message contained in the warning information in the notification field MS. For example, when the user selects (presses) warning information LT12, the terminal device P1 displays a message contained in the warning information LT12 in the notification field MS, stating, "According to a report from the manufacturer, there is a risk of a malfunction occurring in your HDD. Replacement is recommended." Note that the message shown in FIG. 4 is merely an example, and needless to say, the present invention is not limited to this.

In addition, the recorder R1 in the recorder management system 100 according to the second embodiment described later detects failures occurring in the recorder R1 and devices capable of data communication with the recorder R1 (e.g., each of the multiple surveillance cameras C1, ..., CN, terminal device P1, etc.) and targets in which failures occur (e.g., surveillance camera C1, terminal device P1, monitor MN1, etc.) based on the log (processing history information and type information) of the processor 11 of the recorder R1. The recorder R1 generates an error history column LT1 that includes this failure information (e.g., failure information LT13, LT141, LT151, etc. shown in FIG. 4). When generating failure resolution information that notifies the recorder R1 that a failure that occurred has been resolved, the error history column LT1 generates an error history column LT1 that includes the failure resolution information sent from the recorder R1 (e.g., failure resolution information LT142, LT152, etc. shown in FIG. 4).

For example, when the recorder R1 detects that the terminal device P1 has two or more monitors and that one of the two or more monitors set as a sub-monitor cannot be detected based on the log, the recorder R1 generates fault information LT13 based on the detected fault (detection error, communication error, etc.) and transmits it to the terminal device P1. The fault information LT13 includes, for example, information on the date and time of the fault occurrence, "2020/4/13 13:32:08", and fault information "Sub-monitor not detected". The terminal device P1 generates an error history column LT1 (attention screen SC1) including the fault information LT13 transmitted from the recorder R1 and displays it on the monitor MN1. This allows the user to know that a fault (detection error, communication error, etc.) has occurred on the sub-monitor based on the fault information LT13 displayed in the error history column LT1 of the attention screen SC1.

When the recorder R1 detects, for example, a fault (communication error) between the recorder R1 and "camera 1" among the multiple surveillance cameras C1, ..., CN based on the log, the recorder R1 generates fault information LT141 based on the detected fault (communication error) and transmits it to the terminal device P1. The fault information LT141 includes, for example, information on the date and time of the fault, "2020/4/13 13:32:12", and fault information "Communication error: Camera 1". The terminal device P1 generates an error history column LT1 (attention screen SC1) including the fault information LT141 transmitted from the recorder R1 and displays it on the monitor MN1. This allows the user to know that a communication error (fault) has occurred between the recorder R1 and "camera 1" based on the fault information LT141 displayed in the error history column LT1 of the attention screen SC1.

Furthermore, when the recorder R1 detects based on the log that the fault (communication error) occurring with "Camera 1" indicated in the fault information LT141 has been resolved, the recorder R1 generates fault resolution information LT142 indicating the fault resolution and transmits it to the terminal device P1. The fault resolution information LT142 includes, for example, information on the date and time of the fault occurrence, "2020/4/13 13:32:16", and fault resolution information "Communication restored: Camera 1". The terminal device P1 generates an error history column LT1 (attention screen SC1) including the fault resolution information LT142 transmitted from the recorder R1 and displays it on the monitor MN1. This allows the user to know that the communication error (fault) occurring with "Camera 1" has been resolved based on the fault resolution information LT142 displayed in the error history column LT1 of the attention screen SC1.

When the recorder R1 detects, for example, a fault (communication error) between the recorder R1 and "camera 1" among the multiple surveillance cameras C1, ..., CN based on the log, the recorder R1 generates fault information LT151 and transmits it to the terminal device P1. The fault information LT151 includes, for example, information on the date and time of the fault, "2020/4/13 13:32:15", and fault information, "Communication error (live): camera 1". The terminal device P1 generates an error history column LT1 (attention screen SC1) including the fault information LT151 transmitted from the recorder R1 and displays it on the monitor MN1. This allows the user to know that an error (fault) has occurred between the recorder R1 and "camera 1" based on the fault information LT151 displayed in the error history column LT1 of the attention screen SC1.

Furthermore, when the recorder R1 detects based on the log that the fault (communication error) occurring with "camera 1" indicated in the fault information LT151 has been resolved, the recorder R1 generates fault resolution information LT152 indicating the resolution of the fault and transmits it to the terminal device P1. The fault information LT151 includes, for example, information on the date and time of the fault occurrence, "2020/4/13 13:32:15", and fault information "Communication restored (live): camera 1". The terminal device P1 generates an error history column LT1 (attention screen SC1) including the fault resolution information LT152 transmitted from the recorder R1 and displays it on the monitor MN1. This allows the user to know that the communication error (fault) occurring with "camera 1" has been resolved based on the fault resolution information LT152 displayed in the error history column LT1 of the attention screen SC1.

Next, the third operation procedure of the recorder management system 100 according to the first embodiment will be described with reference to FIG. 5. FIG. 5 is a sequence diagram showing an example of the third operation procedure of the recorder management system 100 according to the first embodiment. Note that in the sequence diagram shown in FIG. 5, the processing in steps St14 to St19 is similar to the processing described in the first operation procedure example shown in FIG. 2, and therefore description thereof will be omitted.

Furthermore, in the explanation of the third operation procedure given below, only an example will be explained in which the management server S1 determines whether or not each of the hard disk information inserted (equipped) in the recorder R1 is in the management list database 23, and the explanation of each of the other recorders R2, ... will be omitted.

In the third operation procedure shown in FIG. 5, an example is described in which the terminal device P1 requests the management server S1 to perform a process (hereinafter, referred to as a "hard disk inspection") to determine whether or not each of one or more hard disks 13A, ... inserted (provided) in the recorder R1 is a hard disk that requires attention, based on a user operation.

When the terminal device P1 receives a request for a hard disk inspection through a user operation (St30), it generates a control command requesting a hard disk inspection. The terminal device P1 transmits the generated control command to the recorder R1 (St31).

Based on the control command sent from the terminal device P1 requesting a hard disk inspection, the recorder R1 reads out information about all hard disks currently inserted (equipped) in the recorder R1 (St32).

The recorder R1 transmits all of the read hard disk information and a control command requesting a hard disk inspection to the management server S1 via the network NW (St33).

The management server S1 acquires all of the hard disk information sent from the recorder R1 and a control command requesting a hard disk inspection (St34). Based on the control command requesting a hard disk inspection, the management server S1 executes a comparison (determination) process to determine whether the hard disk information sent from the recorder R1 is included in each of the multiple hard disk information registered (stored) in the management list database 23 (St14).

In addition, if the management server S1 determines, as a result of the processing of step St14, that there is no acquired hard disk information in each of the multiple hard disk information recorded in the management list database 23 (St14, NO), it transmits notification information (CGI command) to the recorder R1 notifying that there is no warning information (CGI command) as the inspection result (St32).

The recorder R1 transmits the notification information of the inspection result sent from the management server S1 to the terminal device P1 (St33).

The terminal device P1 generates a test result screen to present the notification information of the test result sent from the recorder R1 to the user, and displays it on the monitor MN1 (St34).

As described above, the recorder management system 100 in the third example of the operation procedure according to the first embodiment can determine whether or not each of the hard disks inserted (equipped) in each of the recorders R1, ... connected for data communication is a hard disk that requires attention when the user wishes to perform a hard disk inspection.

Now, referring to FIG. 6, we will explain the warning screen SC2 displayed on the monitor MN1 of the terminal device P1 based on the warning information sent from the management server S1. FIG. 6 is a diagram showing an example of a warning screen SC2 related to a hard disk. Note that the recorder R1 in FIG. 6 shows an example in which each of three hard disks ("HDD1", "HDD2", and "HDD3" shown in FIG. 6) is currently inserted (equipped). Also, in the example shown in FIG. 6, the terminal device P1 currently receives warning information for the hard disk displayed as "HDD3" out of the three hard disks in the recorder R1.

When the user selects (presses) the maintenance button BT4 in the setting field SF1 or the setting button BT2 in the warning screen SC1 shown in FIG. 4, the terminal device P1 generates a warning screen SC2 including a hard disk list field LT2 and displays it on the monitor MN1.

The settings field SF1 has a network button BT3 and a maintenance button BT4.

When the network button BT3 is selected (pressed) by a user operation, the terminal device P1 displays a setting screen (not shown) for the notification destination (i.e., other destinations to which the warning notification is sent other than the terminal device P1 connected to the recorder R1 so that data communication is possible) used in the processing of step St24 (the second operation procedure shown in FIG. 3). The terminal device P1 sends one or more notification destinations input (set) by user operation to the recorder R1. The recorder R1 stores one or more notification destinations, and when it receives warning information from the management server S1, it sends the warning information to the terminal device P1 and also sends warning notifications to the one or more stored notification destinations.

When the maintenance button BT4 is selected (pressed) by a user operation, the terminal device P1 displays the hard disk list column LT2.

The hard disk list column LT2 is generated to include at least the status information of each of the three hard disks currently inserted in the recorder R1. The hard disk list column LT2 shown in FIG. 6 includes capacity information, operating time information, status information, and date and time range information of the recorded images (videos) of each of the three hard disks currently inserted in the recorder R1.

Specifically, the hard disk list column LT2 indicates that "HDD1" provided in recorder R1 has a capacity of "2000 GB", an operating time of "1740 hours", a status of "normal", and records recorded images (video) from "2018/05/15 12:00" to "2020/04/13 13:40". The hard disk list column LT2 indicates that "HDD2" provided in recorder R1 has a capacity of "2000 GB", an operating time of "599 hours", a status of "normal", and records recorded images (video) from "2018/05/18 15:14" to "2018/05/20 17:32". The hard disk list field LT2 also indicates that "HDD3" included in recorder R1 has a capacity of "3000 GB," an operating time of "916 hours," a status of "warning," and that recorded images (video) were recorded from "2018/05/20 17:32" to "2018/06/29 13:15." Note that in the hard disk list field LT2, in order to emphasize the "warning" status of the hard disk corresponding to the attention information, the text color of the "warning" status may be displayed in red, for example, or the text of the "warning" status may be surrounded by a border AR.

(Embodiment 2)
The recorder management system 100 according to the first embodiment judges whether or not the hard disk inserted in each of the recorders R1, ... is a hard disk that requires attention based on a predetermined event. The predetermined event in the first embodiment is the insertion (addition) of a new hard disk in the first operation procedure, the update of the management list database 23 in the second operation procedure, and the acceptance of a request for hard disk inspection by a user operation in the third operation procedure. When the recorder management system 100 according to the second embodiment detects, as a predetermined event, a failure occurring in the recorder R1 and a device capable of data communication with the recorder R1 (for example, each of the multiple surveillance cameras C1, ..., CN, the terminal device P1, etc.), it judges whether or not the hard disk inserted in the recorder is a hard disk that requires attention.

When the recorder R1 according to the second embodiment detects the occurrence of a fault based on the log resulting from the processing of the processor 11 in the recorder R1, the recorder R1 generates a control command to request the management server S1 to inspect the hard disk. The recorder R1 transmits the log and the control command of the recorder R1 to the management server S1 via the network NW.

The log here includes at least the processing history information executed by the processor 11 of the recorder R1, type information indicating the subject in which the event content (e.g., information, warning, error, error resolution, etc.) occurred, and hard disk information of the hard disk inserted in the recorder R1.

Specifically, the processing history information includes the processing date and time when the processing was performed and the event content. The type information is information capable of identifying the target where the event content occurred, and includes, for example, hard disk information (lot number, product number, manufacturer, etc.) and identification information capable of individually identifying a surveillance camera. Note that the processing history information and type information are not limited to the above examples. For example, when the terminal device P1 is equipped with each of multiple monitors, the type information may be information capable of individually identifying these monitors. Also, for example, the type information may be information on the notification destination (a destination other than the terminal device P1 to which the warning notification is sent) used in the processing of step St24 shown in FIG. 3.

As a result, when recorder R1 determines that the processing history information included in the log indicates an error, it can detect that an error (i.e., a fault) occurred in the target indicated by the type information at the processing date and time indicated by the processing history information. In addition, when recorder R1 determines that the processing history information included in the log indicates that the error that occurred has been resolved, it can detect that the error (i.e., a fault) that occurred in the target indicated by the type information at the processing date and time indicated by the processing history information has been resolved.

Based on the log sent from recorder R1, management server S1 acquires hard disk information for each hard disk inserted (equipped) in recorder R1. Based on the control command sent from recorder R1, management server S1 determines whether the acquired hard disk information is in the hard disk list registered (stored) in management list database 23.

Next, the fourth operation procedure of the recorder management system 100 according to the second embodiment will be described with reference to FIG. 7. FIG. 7 is a sequence diagram showing an example of the fourth operation procedure of the recorder management system 100 according to the first embodiment. Note that in the sequence diagram shown in FIG. 7, the processing in steps St14 to St17 is similar to the processing explained in the first operation procedure example shown in FIG. 2, and therefore the explanation will be omitted.

Furthermore, in the explanation of the fourth operation procedure given below, only an example will be explained in which the management server S1 determines whether or not each of the hard disk information inserted (equipped) in the recorder R1 is in the management list database 23, and the explanation of each of the other recorders R2, ... will be omitted.

In the fourth operation procedure shown in FIG. 7, recorder R1 acquires a log (St40).

When recorder R1 detects that a fault has occurred based on the processing history information contained in the log (St41), it generates a control command to request management server S1 to inspect the hard disk, and transmits recorder R1's log and the generated control command to management server S1 via network NW (St42).

Based on the recorder R1 log sent from the recorder R1, the management server S1 obtains hard disk information for each hard disk inserted (equipped) in the recorder R1 (St43).

Based on the control command sent from the recorder R1, the management server S1 determines whether the acquired hard disk information is in the hard disk list registered (stored) in the management list database 23 (i.e., whether it is a hard disk that requires attention) (St14).

When the recorder R1 receives warning information (CGI command) from the management server S1, it transmits the received warning information and the detected fault information to the terminal device P1 (St44).

Based on the warning information and fault information transmitted from the recorder R1, the terminal device P1 generates a warning screen SC1 (see FIG. 4) including the fault information and displays it on the monitor MN1 (St45).

In addition, when the recorder R1 receives warning information (CGI command) from the management server S1, if there is a notification destination for the warning information that has been set in advance by the user, it generates and sends a warning notification (e.g., an email or summary notification) including the warning information and the fault information to this notification destination (e.g., a terminal device such as a smartphone, tablet terminal, or other computer owned by the user, or a terminal device such as a smartphone, tablet terminal, or other computer owned by a person who manages the recorder R1 like the user) (St46).

As described above, the recorder management system 100 in the fourth operation procedure example according to the second embodiment can determine whether or not each of the hard disks inserted (equipped) in the recorder R1 is a hard disk that requires a warning when a fault occurs in the recorder R1 and in a device (e.g., each of the surveillance cameras C1, ..., CN, terminal device P1, etc.) that is connected to the recorder R1 so as to be able to communicate with each other. In addition, the recorder management system 100 according to the second embodiment can more efficiently notify the user of the fault information and warning information by generating and displaying a warning screen SC1 that includes the determination result as well as information on the fault that has occurred.

In the recorder management system 100 according to the first and second embodiments, the recorder R1 and the management server S1 are connected to each other so that they can communicate with each other, and the recorder R1 transmits to the management server S1 hard disk information (an example of identification information, for example, S.M.A.R.T. information for each hard disk, lot number, hard disk product number, serial number, or manufacturer information) that can individually identify one or more hard disks 13A, ... that can record images from the surveillance cameras C1, ..., CN. The management server S1 stores a hard disk list that includes hard disk information for each of a plurality of hard disks registered as attention targets and attention information associated with each of these hard disk information, and when a predetermined event occurs and it is determined that the hard disk list contains hard disk information transmitted from the recorder R1, the management server S1 transmits attention information corresponding to this hard disk information to the recorder R1, and the recorder R1 outputs the attention information transmitted from the management server S1 to the monitor MN1.

As a result, if there is warning information corresponding to the hard disk inserted in recorder R1, the recorder management system 100 according to embodiments 1 and 2 can present this warning information to the user and assist the user in monitoring operations. Therefore, the user can consider replacing or buying a new hard disk, or change the hard disks that record the images captured by each of the surveillance cameras C1, ..., CN, based on the warning information before an abnormality occurs in the hard disk.

When a new hard disk is inserted by a user, the recorder R1 in the recorder management system 100 according to the first embodiment acquires hard disk information of the new hard disk and transmits it to the management server S1. The management server S1 determines whether there is new hard disk information in the hard disk list based on the hard disk information of the new hard disk transmitted from the recorder R1. This allows the recorder management system 100 according to the first embodiment to collect hard disk information for each hard disk when a new hard disk is inserted into the multiple recorders R1, and to present the user with warning information corresponding to the inserted hard disk. Therefore, the user can check more quickly whether there is warning information corresponding to the inserted hard disk before recording the images captured by each of the multiple surveillance cameras C1, ..., CN.

In addition, when the hard disk list is updated, the management server S1 in the recorder management system 100 according to the first embodiment determines whether or not the hard disk information of the recorder R1 is included in the updated hard disk list. As a result, when the management list database 23 is updated by the administrator, the recorder management system 100 according to the first embodiment can determine whether or not each of the hard disks inserted (included) in each of the recorders R1, ... that are connected so as to be able to communicate data is a hard disk that requires attention. Therefore, the user can obtain the latest attention information about the hard disks used in the recorders.

Furthermore, the recorder R1 in the recorder management system 100 according to the first embodiment transmits a determination request to the management server S1 in response to a user operation to determine whether or not there is hard disk information in the hard disk list. The management server S1 determines whether or not there is hard disk information in the hard disk list based on the determination request transmitted from the recorder R1. This allows the recorder management system 100 according to the first embodiment to determine whether or not each of the hard disks inserted (equipped) in each of the recorders R1, ... connected for data communication is a hard disk that requires attention at the time when the user wishes to perform a hard disk inspection.

Furthermore, when the management server S1 in the recorder management system 100 according to the first embodiment determines that the hard disk list does not contain hard disk information sent from the recorder R1, it generates notification information notifying the recorder R1 that there is no warning information corresponding to the hard disk and sends the notification information to the recorder R1. The recorder R1 outputs the notification information sent from the management server S1 to a monitor. This allows the recorder management system 100 according to the first embodiment to notify the user that there is no warning information on the hard disk inserted in the recorder R1.

In addition, when the recorder R1 in the recorder management system 100 according to the second embodiment determines that a fault has occurred based on the processing history information of the recorder R1, the recorder R1 transmits a log including the processing history information and type information indicating the target in which the fault has occurred to the management server S1. The management server S1 acquires the hard disk information inserted into the recorder R1 from the log transmitted from the recorder R1, generates a determination result of whether or not the acquired hard disk information is in the hard disk list, and transmits the result to the recorder R1. The recorder R1 outputs the determination result and fault information transmitted from the management server S1 to the monitor MN1. As a result, the recorder management system 100 according to the second embodiment can determine whether or not each of the hard disks inserted (equipped) in the recorder R1 is a hard disk that requires attention at the time when a fault occurs in the recorder R1 and the device (e.g., each of the surveillance cameras C1, ..., CN, the terminal device P1, etc.) connected to the recorder R1 so as to be able to communicate with each other. Furthermore, the recorder management system 100 according to the second embodiment can more efficiently notify the user of the fault information and the warning information by generating and displaying a warning screen SC1 that includes information about the fault that has occurred along with the judgment result.

In addition, when the recorder R1 in the recorder management system 100 according to the second embodiment determines that the fault has been resolved based on the processing history information of the recorder R1, the recorder R1 outputs fault resolution information to the monitor MN1 to notify that the fault has been resolved. This allows the recorder management system 100 according to the second embodiment to promptly notify the user that the fault has been resolved.

Furthermore, when the management server S1 in the recorder management system 100 according to the first and second embodiments determines that the hard disk list contains hard disk information for the recorder R1, it transmits this hard disk information and warning information corresponding to the hard disk information to a destination preset by the user. As a result, when a notification destination for warning information has been preset by the user, the recorder management system 100 according to the first and second embodiments can generate and transmit an email or summary notification including the warning information to this notification destination. Thus, the user can check the warning information regardless of time or place.

Although various embodiments have been described above with reference to the attached drawings, the present disclosure is not limited to such examples. It is clear that a person skilled in the art can conceive of various modifications, corrections, substitutions, additions, deletions, and equivalents within the scope of the claims, and it is understood that these also fall within the technical scope of the present disclosure. Furthermore, the components in the various embodiments described above may be combined in any manner as long as it does not deviate from the spirit of the invention.

This disclosure is useful as a recorder management system and a recorder management method that can provide users with warnings regarding hard disks used to record video captured by surveillance cameras and assist users in their surveillance work.

10, 20 Communication unit 11, 21 Processor 12, 22 Memory 13A Hard disk 23 Management list database 100 Recorder management system C1, C2, CN Surveillance camera MN1 Monitor NW Network P1, P2 Terminal device R1, R2, R3 Recorder S1 Management server SC1, SC2 Warning screen

Claims (9)

A recorder management system in which a recorder and a management server are communicatively connected to each other,
The recorder includes:
Transmitting identification information capable of individually identifying one or more hard disks capable of recording images from a surveillance camera to the management server;
The management server includes:
storing a hard disk list including identification information of each of a plurality of hard disks registered as warning targets and warning information associated with each of the identification information;
when it is determined that the identification information transmitted from the recorder is included in the hard disk list when a predetermined event occurs, transmitting, to the recorder, attention-call information corresponding to the identification information;
The recorder includes:
outputting the warning information transmitted from the management server to a monitor;
Recorder management system. The recorder includes:
When a new hard disk is inserted by a user, identification information of the new hard disk is obtained and transmitted to the management server;
The management server includes:
determining whether the identification information of the new hard disk is included in the hard disk list based on the identification information of the new hard disk transmitted from the recorder;
2. The recorder management system according to claim 1. The management server includes:
When the hard disk list is updated, it is determined whether the identification information is present in the updated hard disk list.
2. The recorder management system according to claim 1. The recorder includes:
A determination request is sent to the management server by a user operation to determine whether the identification information is present in the hard disk list;
The management server includes:
determining whether the identification information is present in the hard disk list based on the determination request transmitted from the recorder;
2. The recorder management system according to claim 1. The management server includes:
if it is determined that the identification information transmitted from the recorder is not present in the hard disk list, generating notification information notifying that the warning information corresponding to the hard disk is not present and transmitting the notification information to the recorder;
The recorder includes:
outputting the notification information transmitted from the management server to the monitor;
2. The recorder management system according to claim 1. The recorder includes:
When it is determined that a failure has occurred based on the processing history information of the recorder, a log including the processing history information and type information indicating a target where the failure has occurred is transmitted to the management server;
The management server includes:
obtaining the identification information inserted in the recorder from the log transmitted from the recorder;
generating a determination result as to whether the acquired identification information is in the hard disk list or not, and transmitting the determination result to the recorder;
The recorder includes:
outputting the determination result and the fault information transmitted from the management server to the monitor;
2. The recorder management system according to claim 1. The recorder includes:
when it is determined that the fault has been resolved based on the processing history information of the recorder, outputting fault resolution information notifying that the fault has been resolved to the monitor.
7. The recorder management system according to claim 6. The management server includes:
if it is determined that the identification information exists in the hard disk list, the identification information and the warning information are transmitted to a destination preset by a user.
2. The recorder management system according to claim 1. A recorder management method executed by a system in which a recorder and a management server are communicatively connected to each other, comprising:
The recorder includes:
Reading out identification information capable of individually identifying one or more hard disks capable of recording images captured by the surveillance camera;
The management server includes:
When a predetermined event occurs, a determination is made as to whether or not the identification information is included in a hard disk list including identification information of each of a plurality of hard disks registered as targets for warning and warning information associated with each of the identification information;
The recorder includes:
if the management server determines that the identification information exists in the hard disk list, it generates a warning screen based on warning information corresponding to the identification information and outputs the warning screen to a monitor.
Recorder management method.

Images