JP7675327B2 - Security devices and systems - Google Patents

Description

This invention relates to a security device that detects the occurrence of an abnormal event, such as the intrusion of a suspicious person or a fire, and reports the event to a specified reporting destination.

So-called security devices are often installed in offices, schools, commercial facilities, and other facilities where no one is using them at night or on holidays. Security devices are also beginning to be used in ordinary homes to ensure safety at night when residents are often out and about or asleep and out of sight. For example, as shown in FIG. 11, security devices 11 installed in various guarded facilities 10 are connected to various monitoring sensors (anomaly detection sensors) such as an intrusion sensor SX1 and a fire sensor SX2.

The intrusion sensor SX1 includes a human presence sensor that uses infrared rays, ultrasound, visible light, etc. to detect the presence of humans, an opening/closing sensor that uses magnetism or acceleration to detect the opening/closing of doors and windows, and an impact sensor that detects the impact when a window or door is broken. The fire sensor SX2 includes a smoke sensor that detects smoke and a heat sensor that detects heat. These various monitoring sensors are connected to the sensor input circuit section 12 of the security device 11. The sensor input circuit section 12 of the security device 11 monitors the output signals from each of the monitoring sensors SX1, SX2, etc., and when it detects the occurrence of an abnormality, it reports it via the wide area network 20 to a specified reporting destination, for example, the security destination accommodation device (control device) 31 of the security company 30.

The wide area network 20 is a communication network such as a public telephone network, a mobile phone network, or the Internet. At the security company 30, when the guarded accommodation device 31 receives a report from the security device 11 of the guarded facility 10, it notifies the monitor 40 by, for example, emitting a sound to indicate the received message. The monitor 40 operates the guarded accommodation device 31 to identify the source of the report and instructs the security guard 50 to be dispatched to the source of the report. This allows the security guard to be swiftly dispatched to the guarded facility 10 where an abnormality has occurred and to take appropriate action.

As disclosed in Patent Document 1, which will be described later, an invention has been disclosed relating to a security system that connects security devices to a monitoring center via different networks, the Internet and a public line. In the case of the invention disclosed in Patent Document 1, even if a network failure occurs, an alarm of abnormality detection information can be sent to the monitoring center via another communication line, making it possible to quickly respond to abnormalities in the monitored area.

JP 2006-285645 A

In recent years, cloud computing, which provides users with the right to use software and hardware as a service over a network, has become widely used. The various data centers and server devices that are set up on the Internet to realize this cloud computing method are called clouds. The cloud provides users with the desired software, hardware, etc. without the users being aware of the actual server devices.

In security systems, rather than simply connecting security devices and security company devices via different networks as in the security system disclosed in Patent Document 1, security systems are being constructed using cloud systems. For example, a receiving server device that receives reports from multiple facilities to be guarded and a security server device that notifies the security company of the occurrence of an abnormality based on information from this receiving server device are provided in the cloud. By using a cloud system, a large-scale, highly reliable security system can be constructed without the security company having to build a large-scale system.

In this way, even when using a cloud system, it may not be possible to report the occurrence of an abnormality at the appropriate time due to communication problems on the Internet. Communication problems in this case include problems with the Internet and problems with the server device as a cloud system. For this reason, as a BCP (Business Continuity Plan) measure, it is necessary to connect the security device to the so-called on-premises server device of the security company through a network other than the Internet. If a communication problem occurs on the Internet side, a report is sent to the security company's on-premises server device through that other network, and the occurrence of an abnormality is notified to the security destination accommodation device (control device) through that on-premises server device, making it possible to take appropriate action quickly.

Redundancy refers to the process of having a backup device in place and operating normally as a backup in order to maintain the overall system's functionality even after a failure occurs in the event that a failure occurs in part of the system. In this way, in a redundant security system that includes a cloud system as part of it, let's say that due to a communication failure on the Internet side, the security device reports to the security company's on-premises server device via a network other than the Internet.

In this case, once the communication failure that occurred on the Internet side has been resolved, the report data that was sent to the security company's on-premises server device via another network must also be resent to the receiving server device of the cloud system. This is because if the receiving server device on the Internet side, which is the main communication system, is not able to manage all report data, discrepancies will occur in the history and appropriate management and operation will be impossible. For this reason, it is possible to resend the report data that could not be sent from the security device to the receiving server device on the Internet side (cloud system), but there are concerns that this could cause inconvenience.

For example, a discrepancy may occur between the arrival time of the report data and the actual handling of the report data. In other words, if the report data is simply resent from the security device to the receiving server device of the cloud system, the actual arrival time at the receiving server device will be the arrival time of the resent report data received by the receiving server device. However, the resent report data has already been sent to the on-premises server device, which is the backup report destination, and the security destination accommodation device (control device) is handling it at the arrival time of the on-premises server device. For this reason, a discrepancy may occur between the report data sent to the receiving server device of the cloud system and the actual handling of the report data sent to the on-premises server device, making it impossible to manage appropriately.

In view of the above, the present invention aims to prevent inconveniences related to the retransmission of report data after a communication failure or the like that occurs on the cloud side is resolved in a redundant security system that is configured using a cloud system.

In order to solve the above problems, the security device of the invention described in claim 1 is:
a notification data generating means for generating notification data when an occurrence of an abnormality is detected;
a first notification processing means for transmitting the notification data formed by the notification data forming means to a first notification destination through a first network;
a fault determination means for determining whether a fault has occurred on the first network side;
a first storage means for storing and holding the report data that could not be transmitted to the first report destination as post-failure report data when the fault determination means determines that the fault has occurred;
a second notification processing means for transmitting the post-failure notification data stored in the first storage means to a second notification destination through a second network different from the first network;
a recovery determination means for determining whether or not the failure occurring on the first network side has been recovered from;
a first provision request sending means for sending, when the recovery determination means determines that the failure has been recovered from, a first provision request to the second report destination, the first provision request requesting the second report destination to provide the post-failure report data including an arrival time at the second report destination;
a first acquisition means for acquiring the post-failure report data including the arrival time returned from the second report destination in response to the first provision request as post-failure provision data from the second report destination;
a first updating means for updating the arrival time of the post-failure provision data corresponding to the post-failure provision data acquired by the first acquiring means among the post- failure notification data stored and held in the first storage means;
and a first retransmission processing means for transmitting the post-fault report data, the arrival time of which has been updated by the first update means, to the first report destination via the first network.

According to the security device of the invention described in claim 1, when an abnormality is detected, first, the report data forming means forms report data, which is then transmitted to the first report destination via the first network by the first report processing means. Assume that the failure determination means determines that a failure has occurred on the first report destination side. In this case, the report data that could not be transmitted to the first report destination is stored and held in the first storage means as post-failure report data, and the second report processing means transmits the post-failure report data held in the first storage means to the second report destination via the second network.

When the recovery determination means determines that the failure at the first report destination side has been recovered, first, the first provision request transmission means transmits a request to the second report destination for provision of post-failure report data including the arrival time. In response to this, post-failure report data (post-failure provision data) including the arrival time at the second report destination returned from the second report destination is acquired through the first acquisition means. Thereafter, the first update means updates the arrival time of the post-failure provision data corresponding to the acquired post-failure provision data among the post-failure report data stored and held in the first storage means. The post-failure report data in the first storage means with the updated arrival time is transmitted to the first report destination through the first network by the first retransmission processing means.

According to this invention, report data that could not be sent to the first report destination due to the occurrence of a communication failure or the like is sent to the second report destination, but after the failure is restored, the report data that could not be sent to the first report destination is resent to the first report destination with the arrival time at the second report destination added. This makes it possible for the report data processed at the second report destination to be processed at the first report destination as if it had been processed at the arrival time at the second report destination.

1 is a block diagram for explaining a configuration example of a security system according to an embodiment; 1 is a block diagram for explaining a configuration example of a security device according to an embodiment; FIG. 2 is a block diagram for explaining a configuration of a receiving server device according to an embodiment. FIG. 2 is a block diagram for explaining the configuration of a security server device 5 according to an embodiment. FIG. 2 is a block diagram for explaining a configuration example of an on-premises server device according to an embodiment. FIG. 2 is a block diagram for explaining a configuration example of a control device according to an embodiment. 1 is a diagram for explaining the processing flow in a security system according to an embodiment. FIG. 4 is a diagram for explaining an example of report data transmitted and received in the security system of the embodiment. FIG. 4 is a flowchart for explaining processing performed by a security device of an embodiment. 10 is a flowchart continuing from FIG. 9 . FIG. 1 is a diagram for explaining an example of a conventional security system.

Below, we will explain the embodiment of the device and system according to the present invention with reference to the figures.

[Security system configuration example]
FIG. 1 is a block diagram for explaining a configuration example of a security system according to an embodiment. The security system according to this embodiment is configured by connecting a security device 1 and a control device 6 of a security company through two different paths. The security device 1 is installed, for example, in a company office, and is connected to a plurality of monitoring sensors (anomaly detection sensors). When an abnormality is notified, the security device 1 forms report data and transmits the report data to a security company's report destination, and functions as a transmitter of report data. Note that there may be a plurality of security devices 1 installed in different locations. For example, in a large office, the office may be divided into a plurality of areas, and a security device 1 may be installed in each area. There may also be a case where the security device 1 is installed in the offices of a plurality of different companies.

When notified of an abnormality, the security company's control device 6 outputs when, where, and what type of abnormality has occurred, and is realized, for example, as a control PC (Personal Computer). Based on the output information from the control device 6, the security company's personnel can perform so-called control tasks, such as reporting the abnormality to designated authorities such as the police or fire department, and sending security guards to the site where the abnormality has occurred. Note that there may be multiple control devices 6. For example, a control device 6 may be provided for each region. Different security companies may also use the cloud system, in which case there will be multiple control devices 6 from different security companies.

In the security system of this embodiment, the first route connecting the security device 1 and the control device 6 is a route that connects through the cloud system. As shown in FIG. 1, the cloud system is made up of a receiving server device 4 connected to the Internet 3 and a security server device 5. The receiving server device 4 receives and aggregates the report data from the security device 1, and notifies the security server device 5 through the Internet 3. The security server device 5 notifies the security company's control device 6 of when, where, and what kind of abnormality has occurred based on the report data from the receiving server device 4. In this way, the route in which the report data from the security device 1 is sent to the Internet 3 through the gateway (written as GW in FIG. 1) 2, received by the receiving server device 4, and provided to the control device 6 through the security server device 5 is the first route.

The second route connecting the security device 1 and the control device 6 is a route that is connected through another network 7 different from the Internet 3. Examples of other networks different from the Internet include digital communication networks such as public switched telephone networks (PSTNs) and integrated services digital networks (ISDNs). In this embodiment, for the sake of simplicity, the other network 7 is assumed to be a public switched telephone network. As shown in FIG. 1, a so-called on-premises server device 8 is connected to the security company side of the other network 7. The on-premises server device means an on-premises server, and in this example, it means a server device installed on the premises of the security company (not installed on the cloud side). The on-premises server device 8 has both the functions of the receiving server device 4 and the security server device 5 of the cloud system.

The on-premises server device 8 receives the report data from the security device 1 and notifies the control device 6 of when, where, and what type of abnormality has occurred. In this way, the second route is the route in which the report data from the security device 1 is sent to the other network 7, received by the on-premises server device 8, and a corresponding report is sent to the control device 6. In the case of the security system of this embodiment, the first route via the cloud system is the main route that is normally used.

If some kind of failure occurs on this main route, i.e., on the cloud system side (receiving server side) including the Internet, and the report data cannot be sent properly, the report is sent using a second route via another network 7. Cases where this report data cannot be sent properly also include cases where the receiving server device 4 cannot receive the report data properly. In this way, the second route is a backup sub-route set up for BCP measures. Note that failures on the main route (Internet 3 side) include various cases such as communication failures on the Internet 3 and malfunctions of the receiving server device 4 or security server device 5.

In a security system configured in this way, if some kind of failure occurs on the main route (Internet side), the report data is sent to the on-premises server device 8 using a second route via another network 7, and the abnormality that has occurred is dealt with. After this, when the failure on the main route (Internet side) is resolved, the security device 1 resends the report data sent to the on-premises server device 8 to the receiving server device 4, but this is done in a way that prevents any problems that would occur if the data were simply resent.

The first problem that can arise in this case is that a discrepancy occurs between the time the report data arrives and the actual response to the report data. As mentioned above, if the security device 1 simply resends the report data to the receiving server device 4, the report data will be treated as having arrived at the date and time it arrived at the receiving server device 4. However, the resent report data has already been sent to the on-premises server device 8, and the control device 6 has responded to it at the time it arrived at the on-premises server device 8. This can lead to a discrepancy between the report data sent to the receiving server device 4 and the actual response based on the report data sent to the on-premises server device 8, making it difficult to manage appropriately.

Secondly, the resent reporting data may result in a duplicate report. Depending on the timing and content of a failure on the Internet 3 side, it is possible that the reporting data resent from the security device 1 has actually already been notified to the control device 6 via the cloud system. In this case, the same reporting data is sent twice, and since the arrival times of the reporting data will be different, this will result in a duplicate report, and it may happen that an event that has already been dealt with will be dealt with again.

Thirdly, it is conceivable that the report data received by the receiving server device 4 of the cloud system may be lost during the transmission process. That is, even if the report data sent from the security device 1 is received by the receiving server device 4 of the cloud system and is not normally subject to retransmission, it may be lost within the cloud system depending on the timing and content of the failure. For example, when the report data is transmitted from the receiving server device 4 of the cloud system to the security server device 5, it may be lost due to a failure that occurs in the receiving server device 4 or the security server device 5, even if this is rare.

In the security system of this embodiment, the security device 1 cooperates with the on-premises server device 8 and the receiving server device 4 to prevent the above-mentioned problems from occurring. Below, we will explain examples of the configuration of each device that makes up the security system of this embodiment, and provide details of the processing performed in the security system of this embodiment.

[Configuration example of security device 1]
2 is a block diagram for explaining a configuration example of the security device 1 according to the embodiment. In FIG. 2, the connection terminal 101T and the first communication I/F 101 realize a function of communicating through the Internet 3. The connection terminal 107T and the second communication I/F 107 realize a function of communicating through another network (public switched telephone network) 7.

The control unit 102, which is not shown in the figure, is a microprocessor configured by connecting a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and non-volatile memory via a bus, and realizes the function of controlling each part of the security device 1. The storage device 103 is configured by a recording medium and its driver, and makes it possible to write, read, change, and delete data to the recording medium. The storage device 103 is realized, for example, as a non-volatile memory device or SSD (Solid State Drive).

As shown in Figure 2, in the storage device 103 of the security device 1, a report data file 1031, a past report data file 1032, and a post-fault report data file 1033 are formed. In addition to these, the storage device 103 also forms, for example, program files and data files that hold data required for processing, and working files that temporarily store intermediate results of processing.

The report data file 1031 temporarily stores report data to be sent (report data to be sent). The past report data file 1032 stores and holds past report data that has already been sent (past report data). In this embodiment, past report data from the start of security to the end of security is stored. Specifically, in the office in which the security device 1 is installed, the report data sent by the last employee leaving the office between the start of security and the end of security is accumulated as past report data.

The post-failure report data file 1033 stores and holds, as post-failure report data, report data that could not be properly sent to the receiving server device 4 or that was not properly received due to a failure on the cloud system side. The report data to be sent, past report data, and post-failure report data are all time-series data that were generated in chronological order. These data are report data of the same format that are generated at different times and are classified according to the situation, such as data before transmission, data that has already been transmitted, and data that could not be properly transmitted to the receiving server device 4 due to a failure.

The connection ends 104T1, 104T2, ..., 104Tn constitute the connection ends with the monitoring sensors 105(1), 105(2), ..., 105(n). The sensor detection unit 104 monitors the output signals from the monitoring sensors 105(1), 105(2), ..., 105(n), and notifies the control unit 102 when it detects the occurrence of an abnormality. There are various types of monitoring sensors, such as intrusion sensors, fire sensors, and flood sensors, but in this embodiment, for the sake of simplicity, the monitoring sensors 105(1), 105(2), ..., 105(n) will be described as intrusion sensors.

The sensor detection unit 104 can also determine which of the monitoring sensors 105(1), 105(2), ..., 105(n) detected the occurrence of an abnormality and notify the control unit 102. Therefore, as the intruder moves, the occurrence of the abnormality can be grasped according to the detection by the monitoring sensors 105(1), 105(2), ..., 105(n) installed at various locations. For example, it is possible to grasp the occurrence of an intrusion (the intruder's movement situation) such as when the intrusion is first detected by the monitoring sensor 105(1), then by the monitoring sensor 105(3), and then by the monitoring sensor 105(4). The clock circuit 106 provides the current date, current day of the week, and current time, and also provides the transmission date and time (transmission time) of the report data transmitted from the security device 1, as described later.

As described above, the control unit 102, which has received notification of the occurrence of an abnormality from the sensor detection unit 104, forms notification data, stores it in the notification data file 1031, and controls the first notification processing unit 111 to transmit the notification data to the first notification destination. Under the control of the control unit 102, the first notification processing unit 111 transmits the notification data stored in the notification data file 1031 to the Internet 3 via the first communication I/F 101 and the connection end 101T, and performs processing to transmit the data to the receiving server device 4. If the data is transmitted to the receiving server device 4 through the first notification processing unit 111 and properly received, the control unit 102 functions to transfer the notification data in the notification data file 1031 to the past notification data file 1032. Whether the notification data has been properly received by the receiving server device 4 can be determined, for example, by whether a response has been returned from the receiving server device 4.

The fault determination unit 112 determines that a fault has occurred when, despite sending report data to the receiving server device 4 via the first report processing unit 111, no response is returned or a notice of a fault is received from the Internet 3. The fault determination unit 112 notifies the control unit 102 of the determination result. Upon receiving the notice of a fault from the fault determination unit 112, the control unit 102 transfers the report data in the report data file 1031 to the post-fault report data file 1033. Furthermore, the control unit 102 controls the second report processing unit 113 to transmit the report data to the second report destination. Under the control of the control unit 102, the second report processing unit 113 performs processing to transmit the report data to the on-premises server device 8 of the security company, which is the second report destination.

Specifically, the second report processing unit 113 connects a communication line between the on-premises server device 8 and the other network 7. After this, the second report processing unit 113 performs processing to send the past report data stored in the past report data file 1032 to the other network (public switched telephone network) 7 via the second communication I/F 107 and the connection end 107T, and transmits it to the on-premises server device 8. In addition to past report data that has already arrived at the control device 6, there is a possibility that past report data that has not arrived or reports that have been abandoned may also exist. For this reason, by providing past report data that has not arrived or reports that have been abandoned to the control device 6, it is possible to prevent the occurrence of missed reports.

The second notification processing unit 113 also performs processing to send the post-fault notification data stored in the post-fault notification data file 1033 to another network (public switched telephone network) 7 via the second communication I/F 107 and the connection end 107T, and transmit it to the on-premises server device 8. This allows the occurrence of a new abnormality to be reported to the security company's control device 6 without delay. Note that the second notification processing unit 113 has been described as first transmitting past notification data to the on-premises server device 8, and then transmitting post-fault notification data, but this is not limited to this. The second notification processing unit 113 can also first transmit post-fault notification data to the on-premises server device 8 to report the occurrence of the latest abnormality, and then transmit past notification data to prevent missed reports.

The recovery determination unit 114 transmits the report data to the on-premises server device 8 through the second report processing unit 113, and then performs a retry communication with the receiving server device 4 to determine whether or not the failure that occurred on the Internet 3 side has been restored. The result of the determination by the recovery determination unit 114 is notified to the control unit 102. The control unit 102, which has received a notification from the recovery determination unit 114 of the determination result that the failure, etc. that occurred on the Internet 3 side has been restored, controls the report data acquisition unit 115 and performs processing to acquire the arrival time of the report data transmitted to the on-premises server device 8.

Specifically, the report data acquisition unit 115 forms and transmits a request for providing the post-fault report data transmitted from the security device 1 to the on-premises server device 8, the post-fault report data having the updated arrival time at the on-premises server device 8. The request for providing is sent to the other network (public switched telephone network) 7 via the second communication I/F 107 and the connection end 107T, and transmitted to the on-premises server device 8. In response to this, the on-premises server device 8 returns the post-fault report data transmitted from the security device 1, the post-fault report data having the updated arrival time at the on-premises server device 8, as post-fault provision data. The post-fault provision data from the on-premises server device 8 is received via the connection end 107T and the second communication I/F 107, and is recorded in a work file in the storage device 103 by the control unit 102.

Similarly, under the control of the control unit 102, the report data acquisition unit 115 forms and transmits a request for providing past report data transmitted from the security device 1 to the on-premises server device 8, the past report data being the past report data with the updated arrival time at the on-premises server device 8. The request for providing is sent to the other network (public switched telephone network) 7 through the second communication I/F 107 and the connection end 107T, and transmitted to the on-premises server device 8. In response to this, the on-premises server device 8 returns the past report data transmitted from the security device 1, the past report data with the updated arrival time at the on-premises server device 8, as past provision data. The past provision data from the on-premises server device 8 is received through the connection end 107T and the second communication I/F 107, and is recorded in the working file of the storage device 103 by the control unit 102. After this, the control unit 102 controls the retransmission processing unit 116 to perform retransmission processing of the report data that could not be transmitted to the receiving server device 4 due to the failure.

Under the control of the control unit 102, the retransmission processing unit 116 identifies the post-failure notification data in the post-failure notification data file 1033 that corresponds to the post-failure provided data from the on-premises server device 8 in the work file of the storage device 103. Next, the retransmission processing unit 116 updates the arrival time of the corresponding post-failure provided data from the on-premises server device 8 for the identified post-failure notification data, sends it to the Internet 3 via the first communication I/F 101 and the connection end 101T, and retransmits it to the receiving server device 4. This makes it possible to retransmit the post-failure notification data that could not be transmitted to the receiving server device 4 due to a failure on the Internet 3 side. Since the arrival time at the on-premises server device 8 has been updated for the retransmitted post-failure notification data, the receiving server device 4 can process it as notification data that has already been notified to the control device 6.

In addition, under the control of the control unit 102, the retransmission processing unit 116 identifies the past report data in the past report data file 1032 that corresponds to the past provided data from the on-premises server device 8 in the work file of the storage device 103. Next, the retransmission processing unit 116 updates the arrival time of the corresponding past report data from the on-premises server device 8 for the identified past report data, sends it to the Internet 3 through the first communication I/F 101 and the connection end 101T, and retransmits it to the receiving server device 4. This makes it possible to properly manage report data that has already been sent but has not yet reached the control device 6 or has been abandoned from being sent to the control device 6 and does not exist in the receiving server device 4. In this case, since the arrival time at the on-premises server device 8 has been updated for the retransmitted past report data, the receiving server device 4 can process it as report data that has already been notified to the control device 6.

In this way, when the security device of this embodiment detects the occurrence of an abnormality through the monitoring sensors 105(1), 105(2), ..., 105(n), it can report this through report data to the receiving server device 4 of the cloud system, which is the first report destination. Also, suppose that some kind of failure occurs on the Internet 3 side, and the report data cannot be properly provided to the receiving server device 4. In this case, the report data can be sent via another network 7 to the on-premises server device 8 of the security company, which is the second report destination, and notified to the control device 6. This allows the report to be processed without delay.

Furthermore, when a failure or the like on the Internet 3 side is restored, the post-failure report data and past report data can be resent to the receiving server device 4 with the arrival time updated at the on-premises server device 8. Since the resent report data has the arrival time at the on-premises server device 8 updated, the receiving server device 4 can handle it as already processed report data that was processed at the arrival date and time at the on-premises server device 8.

[Example of configuration of receiving server device 4]
Fig. 3 is a block diagram for explaining the configuration of the receiving server device 4 according to the embodiment. In Fig. 3, a connection terminal 401T and a communication I/F 401 realize a function of performing communication via the Internet 3. A control unit 402, not shown, is a microprocessor configured by connecting a CPU, a ROM, a RAM, and a non-volatile memory via a bus, and realizes a function of controlling each unit of the receiving server device 4.

The storage device 403 is composed of a recording medium and its driver, and allows data to be written to, read from, modified, and deleted from the recording medium. The storage device 403 is realized, for example, as a non-volatile memory device or SSD. In addition to forming a report data file that stores and holds received report data, the storage device 403 also forms, for example, program files, data files that store data required for processing, and work files that temporarily store intermediate results of processing.

The clock circuit 404 provides the current date, current day of the week, and current time, and can obtain the arrival time at the security device 1 of the report data sent from the security device 1, as described below. The report data reception unit 405 receives report data from the security device 1 received through the connection end 401T and the communication I/F 401. If the received report data has not had its arrival date and time updated, the report data reception unit 405 can determine that it is new report data. In this case, the report data reception unit 405 obtains the arrival date and time at the security device 1 from the clock circuit 404, updates the arrival date and time of the received report data, and provides this to the report data provision unit 406, which makes it the subject of the report to the control device 6.

If the received report data has an updated arrival date and time, the report data reception unit 405 performs a process of recording the report data in the report data file of the storage device 403, since the report data has already been reported to the control device 6 via the on-premises server device 8. In this case, in order to prevent duplicate reports, the report data reception unit 405 discards the received report data if report data with the same serial number assigned to the report data already exists in the report data file, as will be described in detail later.

The report data providing unit 406 sends the report data with the updated arrival time from the report data receiving unit 405 via the communication I/F 401 and the connection end 401T to the Internet 3, and transmits it to the security server device 5. The report data providing unit 406 also records the report data transmitted to the security server device 5 in a report data file in the storage device 403.

In this way, the receiving server device 4 has the function of receiving report data from the security device 1 and handing it over to the security server device 5. Even if there are multiple security devices 1, the report data can be received in a centralized manner and handed over to the security server device 5 without delay.

[Example of configuration of security server device 5]
Fig. 4 is a block diagram for explaining the configuration of the security server device 5 according to the embodiment. In Fig. 4, a connection terminal 501T and a communication I/F 501 realize a function of performing communication via the Internet 3. A control unit 502, which is not shown, is a microprocessor configured by connecting a CPU, a ROM, a RAM, and a non-volatile memory via a bus, and realizes a function of controlling each unit of the security server device 5.

The storage device 503 is composed of a recording medium and its driver, and allows data to be written, read, changed, and deleted from the recording medium. The storage device 503 is realized, for example, as a non-volatile memory device or SSD. The storage device 503 is formed with a report data file that stores and holds report data, and a notification destination file that associates the report source with the control device 6 of the security company that is the report destination. In addition, the storage device 503 is formed with, for example, program files, data files that hold data required for processing, and work files that temporarily store intermediate results of processing.

The clock circuit 504 provides the current date, current day of the week, and current time, and can, for example, obtain the processing time in the device itself. The report data reception unit 505 receives report data from the receiving server device 4 received through the connection terminal 501T and the communication I/F 501, and provides this to the report data provision unit 406, which then makes it the subject of reporting to the control device 6.

The report notification unit 506 references the notification destination file in the storage device 503 based on the notification source of the report data from the report data reception unit 505, identifies the control device 6 of the security company that is the notification destination, and provides the report data to that control device 6. This makes it possible to notify the target control device 6 of at least when, where, and what kind of abnormality occurred. The report notification unit 506 also records the report data that is to be notified to the control device 6 in the report data file in the storage device 503. Note that the security server device 5 can also add necessary information to the report data and provide it. Examples of necessary information include the address and telephone number of the facility under guard where the abnormality is occurring.

In this way, the security server device 5 has the function of receiving the reporting data from the receiving server device 4 and reporting to the target control device 6. Even if multiple control devices 6 exist, the appropriate control device 6 can be identified and a report made depending on the installation location of the security device that sent the reporting data.

[Configuration example of on-premises server device 8]
Fig. 5 is a block diagram for explaining a configuration example of the on-premises server device 8 according to the embodiment. In Fig. 5, a connection terminal 801T and a communication I/F 801 realize a function of communicating through another network (public switched telephone network) 7. A connection terminal 809T and a LAN I/F 809 realize a function of communicating with a control device 6 connected to a LAN. Although not shown, a control unit 802 is a microprocessor configured by connecting a CPU, a ROM, a RAM, and a non-volatile memory via a bus, and realizes a function of controlling each unit of the on-premises server device 8.

The storage device 803 is composed of a recording medium and its driver, and allows data to be written, read, changed, and deleted from the recording medium. The storage device 803 is realized, for example, as a non-volatile memory device or SSD. The storage device 803 is formed with a post-fault report data file that stores and holds post-fault report data from the security device, and a past report data file that stores and holds past report data. The storage device 803 is also formed with, for example, program files, data files that store data required for processing, and work files that temporarily store intermediate results of processing. The clock circuit 804 provides the current date, current day of the week, and current time, and can, for example, obtain the processing time in the device itself.

The report data reception unit 805 receives the post-fault report data and past report data from the security device 1 received through the connection end 801T and the communication I/F 801, and records them in a post-fault data file and a past report data file in the storage device 803. In this case, the report data reception unit 805 obtains the current date and time from the clock circuit 804 as the arrival date and time, updates the arrival date and time of the received post-fault report data and past report data, and records them in the storage device 803. In this way, the report data from the security device 1 includes post-fault report data and past report data. The report notification unit 806 functions to immediately send the post-fault report data to the LAN via the LAN I/F 809 and the connection end 809T, and transmits it to the control device 6. This makes it possible to respond quickly to the occurrence of an abnormality.

The control unit 802 also provides past report data to the control device 6 via the connection terminal 809T and the LAN I/F 809. The control device 6 is able to identify past report data from the on-premises server device 8 that is not present in the report data it holds, and take action against past report data that does not exist in its own device. Therefore, even for past report data that is not provided properly through the receiving server device 4 and security server device 5, which are the cloud system, and that does not exist in the control device 6, the control device 6 can obtain it from the on-premises server device 8 and take appropriate action. In other words, missed reports are prevented.

The provision request receiving unit 807 receives a request for post-fault reporting data or past reporting data from the security device 1 received through the connection end 801T and the communication I/F 801, and notifies the control unit 802. The control unit 802, which has received the provision request, controls the provision data providing unit 808 to perform the provision process of the provided data. That is, under the control of the control unit 802, the provision data providing unit 808 returns the post-fault reporting data and past reporting data with the updated arrival date and time at its own device stored and held in the storage device 803 to the security device 1 that sent the report as post-fault provision data and past provision data. The post-fault provision data and past provision data from the on-premises server device 8 are sent to the other network 7 through the communication I/F 801 and the connection end 801T, and are returned to the security device 1.

In this way, the on-premises server device 8 realizes the function of receiving and holding the report data from the security device 1 and providing it to the security company's control device 6. The on-premises server device 8 also has the function of returning post-fault report data and past report data, with the date and time of arrival at its own device updated, to the security device 1 as post-fault provided data and past provided data from its own device in response to a request for provision from the security device 1.

[Example of configuration of control device 6]
Fig. 6 is a block diagram for explaining a configuration example of the control device of the embodiment. In Fig. 6, a connection terminal 601T and a communication I/F 601 realize a function of communicating through the Internet 3. A connection terminal 602T and a LAN I/F 602 realize a function of communicating with an on-premises server device 8 connected through a LAN. Although not shown, the control unit 102 is a microprocessor configured by connecting a CPU, a ROM, a RAM, and a non-volatile memory through a bus, and realizes a function of controlling each part of the control device 6.

The storage device 604 is composed of a recording medium and its driver, and allows data to be written, read, changed, and deleted from the recording medium. The storage device 604 is realized, for example, as a non-volatile memory device or SSD. The operation unit 605 is composed, for example, of a pointing device such as a keyboard or a mouse, and receives operation input from the user and notifies the control unit 603 of the received information as an electrical signal. This allows the control unit 603 to control each unit according to instructions from the user and perform the processing intended by the user.

The microphone 606, the audio input unit 607, the display unit 608, the audio output unit 609, and the speaker 610 constitute a user interface. The microphone 606 picks up sound, converts it into an electrical signal, and supplies it to the audio input unit 607. The audio signal from the audio input unit 607 is converted into a digital signal and imported into the device. In this way, the microphone 606 and the audio input unit 607 realize the audio input function.

The audio output unit 609 converts the digital audio signal from the control unit 603 into an analog audio signal and supplies it to the speaker 610. This causes the speaker 610 to emit audio corresponding to the digital audio signal from the control unit 603. In this way, the audio output unit 609 and the speaker 610 realize an audio output function. The display unit 608 is composed of a display element such as an LCD (Liquid Crystal Display) and its driver, and displays information mainly corresponding to the received report data and information necessary for control operations under the control of the control unit 603. The communication I/F 611 and the connection end 611T enable connection to an external device such as a communication device.

As a result, the control device 6 can receive report data from the security server device 5 of the cloud system via the connection end 601T and the communication I/F 601, and report data from the on-premises server device 8 via the connection end 602T and the LAN I/F 602. When report data is received, the necessary information can be displayed on the display unit 608, and an alarm sound can be emitted from the audio output unit 609 and the speaker 610, to notify the security company staff of the occurrence of an abnormality.

A security company employee can operate the operation unit 605 to connect a communication line to, for example, a communication device in a security vehicle via the communication I/F 611 and connection end 611T. This makes it possible to use the microphone 606 and audio input unit 607 as a transmitter and the audio output unit 609 and speaker 610 as a receiver to have a voice call with a security guard, to give instructions or receive status reports.

[Security system processing flow]
Fig. 7 is a diagram for explaining the flow of data in the security system of the embodiment. The part enclosed by the dotted line box on the left side of Fig. 7 shows the part related to the transmission of report data of the security device 1. The part enclosed by the dotted line box on the upper right side of Fig. 7 shows the part of the cloud system configured by connecting the receiving server device 4 and the security server device 5 via the Internet 3. The part enclosed by the dotted line box on the lower right side of Fig. 7 shows the part of the LAN system of the security company configured by connecting the on-premises server device 8 and the control device 6 via the LAN.

As explained using FIG. 2, suppose that an abnormality (intrusion in this embodiment) is detected in the security device 1 through the monitoring sensors 105(1)-105(n) and the sensor detection unit 104. In this case, the control unit 102 forms report data and stores it in the report data file 1031 of the storage device 103. Thereafter, under the control of the control unit 102, the first report processing unit 111 sends the report data in the report data file 1031 to the Internet 3 through the first communication I/F 101, and transmits it to the receiving server device 4, which is the first report destination (FIG. 7(1), (2)). After transmitting the report data, the control unit 102 transfers the report data in the report data file 1031 to the past report data file 1032 (FIG. 7(3)).

The report data sent to the receiving server device 4 is sent to the security server device 5 (FIG. 7 (4)), and is sent from the security server device 5 to the control device 6 of the security company (FIG. 7 (5)), which reports the occurrence of an abnormality and allows the security company to take appropriate action. In this way, the processes shown in (1) to (5) in FIG. 7 are normal report processes through the cloud system. In this case, as shown by the dotted arrow (FIG. 7 (NG)) from the receiving server device 4 to the first communication I/F 101, a communication failure or the like occurs on the Internet side, and the report data cannot be properly transmitted or cannot be properly received by the receiving server device 4. The occurrence of a communication failure on the Internet side can be determined, for example, when no response is returned despite the sending of report data, or when the occurrence of a failure is notified from the Internet 3 side. The occurrence of a communication failure or the like is determined by the failure determination unit 112 and notified to the control unit 102.

When the control unit 102 is notified of the occurrence of a communication failure or the like, it transfers the report data in the report data file 1031 to the post-failure report data file 1033 in the storage device 103 (FIG. 7(A)). After this, the second report processing unit 113, under the control of the control unit 102, sends the past report data in the past report data file 1032 to the other network 7 through the second communication I/F 107 and transmits it to the on-premises server device 8 of the security company (FIGS. 7(B) and (C)). Furthermore, under the control of the control unit 102, the second report processing unit 113 sends the post-failure report data in the post-failure report data file 1033 to the other network 7 through the second communication I/F 107 and transmits it to the on-premises server device 8 of the security company (FIGS. 7(D) and (E)).

The on-premises server device 8 updates the arrival date and time of the received past report data and post-fault report data to the current date and time of the arrival obtained from its own clock circuit 804. The past report data is then recorded in a past report data file in the storage device 803, and the post-fault report data is recorded in a post-fault report data file in the storage device 803. This allows the on-premises server device 8 to receive past report data and post-fault report data from the security device 1 and provide them to the control device 6 when a communication failure or the like occurs on the Internet 3 side (Figure 7 (F)).

In this case, the control device 6 identifies the report data that has not been provided by the security server device 5, outputs the contents of the newly acquired report data, and notifies the security company's personnel of the occurrence of the abnormality. Based on the report data, the security company's personnel will report the occurrence of the abnormality to a specified reporting destination, or send a security guard to the location of the abnormality. Note that, as shown in FIG. 7, although the transmission of past report data itself has been completed, in addition to report data that has reached the control device 6 normally (reached control device), there is a possibility that there is also report data that has not reached the control device 6 due to the influence of a failure or the like (not reached control device). There is also a possibility that the transmission itself has been abandoned for some reason, and there is a possibility that there is report data that has not reached the receiving server device 4 (abandoned).

In this way, past report data that has not yet reached the control device 6 (not reached control device) and data for which transmission has been abandoned and the report has not yet reached the receiving server device 4 (abandoned) can also be provided from the security device 1 to the control device 6 via the on-premises server device 8. This makes it possible to reliably avoid a "missed report" situation in which no report data is provided to the control device 6 at all.

After this, in the security device 1, under the control of the control unit 102, the recovery determination unit 114 functions to perform a retry communication to the receiving server device 4, which is the first report destination, via the first communication I/F 101 and the Internet 3 (FIG. 7 (RT)). The recovery determination unit 114 determines whether the retry communication is successful or not, i.e., whether the communication failure or the like has been recovered or not. The recovery determination unit 114 notifies the control unit 102 of the determination result. When the control unit 102 is notified of the fact that the communication failure or the like has been resolved, the control unit 102 controls the report data acquisition unit 115 to perform a process of acquiring report data from the on-premises server device 8 in which the date and time of arrival at the on-premises server device 8 has been updated.

That is, the report data acquisition unit 115 creates a request to acquire past report data, and sends it to the other network 7 via the second communication I/F 107 to transmit it to the on-premises server device 8 (FIGS. 7(G) and (H)). In response to this, the on-premises server device 8 returns past report data with the updated arrival date and time at its own device as past provision data. The security device 1 receives this via the connection end 107T and the second communication I/F 107 (FIGS. 7(I) and (J)). The control unit 102 functions to record the received past provision data in the work file of the storage device 103. After this, the retransmission processing unit 116 functions to update the arrival date and time of the past report data corresponding to the past provision data recorded in the work file, among the past report data in the past report data file 1032, to the arrival date and time of the past provision data in the work file.

Similarly, the report data acquisition unit 115 creates a request to acquire post-failure report data, and sends it to the other network 7 via the second communication I/F 107 to transmit it to the on-premises server device 8 (FIGS. 7(K), (L)). In response to this, the on-premises server device 8 returns the post-failure report data with the updated arrival date and time at its own device as post-failure provision data. The security device 1 receives this via the connection end 107T and the second communication I/F 107 (FIGS. 7(M), (N)). The control unit 102 functions to record the received post-failure provision data in the work file of the storage device 103. Thereafter, the retransmission processing unit 116 functions to update the arrival date and time of the post-failure report data corresponding to the post-failure provision data recorded in the work file, among the past report data in the post-failure report data file 1033, to the arrival date and time of the post-failure provision data in the work file.

Then, the control unit 102 controls the retransmission processing unit 116 to perform a retransmission process of the past report data with the updated arrival date and time and the post-failure report data. That is, the retransmission processing unit 116 reads the past report data with the updated arrival date and time from the past report data file 1032 (FIG. 7(O)), sends it to the Internet 3 via the first communication I/F 101, and retransmits it to the receiving server device 4 (FIG. 7(Q)). Similarly, the retransmission processing unit 116 reads the post-failure report data with the updated arrival date and time from the post-failure report data file 1033 (FIG. 7(P)), sends it to the Internet 3 via the first communication I/F 101, and retransmits it to the receiving server device 4 (FIG. 7(Q)).

Figure 8 is a diagram for explaining an example of report data sent and received in the security system of the embodiment. As shown in Figure 8 (A), the report data consists of a serial number, report destination, report source, report content, occurrence location, transmission date and time, and reception date and time. The serial number is a so-called sequential number that is counted up by one each time it is assigned in the control unit 102 of the security device 1 to prevent duplication. The report destination is a URL (Uniform Resource Locator) or IP address of the receiving server device 4 that identifies the receiving server device to which the report data is to be sent. Note that when the report data is sent to the on-premise server device 8 of the security company through another network (public switched telephone network) 7, for example, the communication line is connected as if making a phone call, and then the report data is sent. For this reason, the destination can remain the URL or IP address that identifies the receiving server device.

The report source is information that allows the security company's control device 6, which is the destination, to uniquely identify the security facility where the security device 1 is located, such as a security destination ID that allows the security company's control device 6, which is the destination, to distinguish between the security facility where the security device 1 is located. The report content is information that indicates what abnormality has occurred. In this embodiment, since the monitoring sensors 105(1) to 105(n) are intrusion sensors, the report content indicates the occurrence of an intrusion. The occurrence location is information that identifies the monitoring sensor (intrusion sensor) 105(1) to 105(n) that detected the intrusion, and a sensor ID is used, for example. The transmission date and time is information that indicates the date and time when the security device 1 transmits the report data. The reception date and time is usually information that indicates the date and time of reception at the receiving server device 4, but in the case of resent past report data or post-fault report data, it is information that indicates the date and time of reception at the security company's on-premises server device 8.

Therefore, the report data first sent from the security device 1 to the receiving server device 4 of the cloud system (the report data sent in (2) of Figure 7) will have the sending date and time cleared to zero or initialized, as shown in Figure 8 (B). In contrast, past report data and post-fault report data that are not sent properly due to a communication failure on the cloud system side, and are sent to the security company's on-premises server device 8 and then resent to the receiving server device 4 of the cloud system will be as shown in Figure 8 (C). In other words, the report data resent in Figure 7 (Q) will have the arrival date and time at the on-premises server device 8 updated, as shown in Figure 8 (C).

This makes it possible to prevent the three problems mentioned above from occurring. The first problem is that when report data is resent, a discrepancy occurs between the arrival time of the report data and the actual action taken against the report data. This problem can be prevented by updating the arrival date and time at the security company's on-premises server device 8 for the resent past report data and post-fault report data.

The second problem is that resent notification data may result in duplicate notifications. To address this problem, the receiving server device 4 discards resent and received past notification data or post-fault notification data if notification data with the same serial number is already being held in the receiving server device 4. This prevents duplicate notifications of notification data.

A third problem may occur when report data received by the receiving server device 4 of the cloud system is lost during the transmission process. This problem is addressed by sending past report data to the on-premises server device 8 and also resending it to the receiving server device 4. This makes it possible to restore lost report data, prevents missed reports, and allows the report data to be restored at the receiving server device 4.

[Summary of the processes performed by the security device 1]
9 and 10 are flow charts for explaining the processing performed by the security device 1 of the embodiment. The processing of the flow charts shown in Figs. 9 and 10 is executed by each unit of the security device 1 functioning under the control of the control unit 102 of the security device 1. When the security device 1 is in an operating state, the control unit 102 monitors the output signal from the sensor detection unit 104 that aggregates the monitoring sensors 105(1) to 105(n) and determines whether an abnormality (intrusion) has occurred (step S101). When it is determined in the determination process of step S101 that no abnormality has occurred, the control unit 102 repeats the processing from step S101.

When it is determined in the determination process of step S101 that an abnormality has occurred, the control unit 102 forms the report data of the form shown in FIG. 8 (B) in the report data file 1031 (step S102). Next, the control unit 102 controls the first report processing unit 111 to transmit the report data formed in the report data file 1031 to the receiving server device 4 of the cloud system, which is the first report destination, via the first communication I/F and the connection end 101T (step S103). Thereafter, the control unit 102 transfers the report data formed in the report data file 1031 to the past report data file 1032 (step S104).

Next, the control unit 102 determines whether or not a communication failure or the like has occurred on the cloud system side based on the determination result from the failure determination unit 112 (step S105). When it is determined in the determination process of step S105 that a communication failure or the like has not occurred, the control unit 102 repeats the process from step S101. It is assumed that it is determined in the determination process of step S105 that a communication failure or the like has occurred. In this case, the control unit 102 controls the second report processing unit 113 to connect a communication line with the on-premises server device 8 via the second communication I/F 107 and the connection end 107T, and transmits the past report data of the past report data file 1032 (step S106).

The control unit 102 then transfers the report data in the report data file 1031 to the post-failure report data file 1033 (step S107) and transmits it to the security company's on-premises server device 8 via the second communication I/F 107 and the connection end 107T (step S108). After this, the control unit 102 proceeds to the process of FIG. 10, controls the recovery determination unit 114 to perform a retry communication with the receiving server device 4, and determines whether or not the communication failure has been restored based on the determination result from the recovery determination unit 114 (step S109).

When it is determined in the determination process of step S109 that the communication failure or the like has not been restored, the control unit 102 determines whether or not a new abnormality has been detected, similar to the process of step S101 (step S110). When it is determined in the determination process of step S110 that a new abnormality has not been detected, the process from step S109 is repeated. When it is determined in the determination process of step S110 that a new abnormality has been detected, report data for reporting the occurrence of the new abnormality is formed in the report data file 1031 (step S111), and the process from step S107 in FIG. 9 is repeated. This allows the report data to continue to be sent to the on-premises server device 8 of the security company even if a new abnormality is detected. This is because in this state, the communication failure or the like on the cloud system side has not yet been restored.

In the determination process of step S109, it is determined that the communication failure, etc. has been restored. In this case, the control unit 102 controls the report data acquisition unit 115 to form a request for provision of past report data and post-failure report data, including the date and time of arrival at the on-premises server device 8, and transmits the request to the on-premises server device 8 (step S112). The request for provision in this case is also sent to the other network 7 via the second communication I/F 107 and the connection end 107T, and transmitted to the on-premises server device 8. In response, the on-premises server device 8 returns the past report data and post-failure report data, with the date and time of arrival at the on-premises server device 8 updated.

Therefore, the control unit 102 receives the provided data (past report data, post-fault report data) from the on-premises server device 8 through the connection end 107T and the second communication I/F 107, and records it in a work file in the storage device 103 (step S113). In step S113, when the acquisition of the past report data and post-fault report data from the on-premises server device 8 is completed, the communication line connected between the security device 1 and the on-premises server device 8 through the other network (public switched telephone network) 7 is released.

Then, the control unit 102 controls the report data acquisition unit 115 to update the arrival date and time of the corresponding provided data to the past report data and post-fault report data that correspond to the provided data recorded in the work file (step S114). In this case, the past report data is stored and held in the past report data file 1032, and the post-fault report data is stored and held in the post-fault report data file 1033. The control unit 102 then controls the retransmission processing unit 116 to perform a retransmission process of the past report data and post-fault report data with the updated arrival date and time (step S115).

That is, in step S115, the retransmission processing unit 116 reads the past report data with the updated arrival date and time from the past report data file 1032, and reads the post-failure report data with the updated arrival date and time from the post-failure report data file 1033. After this, the retransmission processing unit 116 sends the read past report data and post-failure report data to the Internet 3 via the first communication I/F 101 and retransmits them to the receiving server device 4. After the past report data and post-failure report data are retransmitted to the receiving server device 4 on the cloud system side where the communication failure or the like has been restored by the processing of step S115, the control unit 102 repeats the processing from step S101 in FIG. 9. In this way, the security device 1 is capable of cooperating with the receiving server device 4 on the cloud system side and the on-premises server device 8 of the security company.

[Effects of the embodiment]
As described above, when the security device 1 detects the occurrence of an abnormality (an intrusion in this embodiment), it forms report data and transmits it to the receiving server device 4 of the cloud system, which is the first report destination, and can report to the security company's control device 6 via the cloud system. However, if a communication failure or the like occurs on the cloud system side, as a BCP measure, the report data can be transmitted via another network 7 to the security company's on-premises server device 8, and a report can be sent to the security company's control device 6 via the on-premises server device 8.

In this case, as described above, the security device 1 can provide not only post-failure report data that could not be sent due to the occurrence of a communication failure or the like, but also past report data to the control device 6 via the on-premises server device 8. As a result, in cases where report data has been received normally by the receiving server device 4 but has not yet reached the control device 6 due to a communication failure or the like occurring on the cloud system side, it becomes possible to provide the report data in question to the control device 6, thereby reliably preventing missed reports.

Furthermore, after recovery from a failure on the cloud system side, the past report data and post-failure report data sent to the on-premises server device 8 can be updated with the arrival date and time at the on-premises server device 8 and resent to the receiving server device 4. This prevents discrepancies between the arrival time of the report data and the actual handling of the report data. Furthermore, because the report data is assigned a serial number, even if already existing report data is resent at the receiving server device 4, it can be discarded, preventing the inconvenience of duplicate reports.

[Modification]
In the above embodiment, when a communication failure or the like occurs on the cloud system side, both the past report data and the post-failure report data are transmitted to the on-premises server device 8 of the security company. However, this is not limited to this. At least, only the post-failure report data that has occurred most recently and could not be provided appropriately to the receiving server device 4 may be transmitted to the on-premises server device 8 of the security company. This allows at least the latest post-failure report data to be provided to the control device 6 through the on-premises server device 8, making it possible for the security company to take a quick response. However, in order to reliably avoid missed reports, it is preferable to transmit the past report data to the on-premises server device 8 of the security company as well.

In the above-described embodiment, all the report data transmitted during the period covered by the security device 1 is stored in the past report data file 1032. In this case, when a communication failure or the like occurs on the cloud system side, all the past report data stored in the past report data file 1032 is transmitted to the on-premises server device 8, but this is not limited to this. For example, when past report data is accumulated over a long period in the past report data file 1032, past report data for a predetermined period from the latest past report data may be transmitted to the on-premises server device 8. The predetermined period in the past may be determined, for example, based on the transmission date and time of the past dispensing report data, such as a period of the past 30 minutes or a period of the past 1 hour. The past report data to be transmitted may also be determined by the number of cases, such as 100 cases from the latest past report data.

The format of the report data is not limited to that described using FIG. 8, and various modifications are possible, such as adding more information. For example, it is possible to provide a division so that post-fault report data and past report data can be distinguished.

In addition, in the above-described embodiment, the sending date and time and the receiving date and time are used, but this is not limited to this. Usually, the security period of the security device 1 is not very long from start to finish, such as from 10:00 PM to 7:00 AM the following day. For this reason, it is also possible to use only the sending time (hour, minute, second) and the receiving time (hour, minute, second) rather than the sending date and time and the receiving date and time.

[others]
As can be seen from the above description of the embodiment, the function of the notification data forming means in the claims is realized by the control unit 102 of the security device 1, and the function of the first notification processing means in the claims is realized by the first notification processing unit 111 of the security device. In addition, the function of the fault determination means in the claims is realized by the fault determination unit 112 of the security device 1, and the function of the first storage means in the claims is realized by the post-fault notification data file 1033 of the security device 1. In addition, the function of the second notification processing means in the claims is realized by the second notification processing unit 113 of the security device 1, and the function of the recovery determination means in the claims is realized by the recovery determination unit 114 of the security device 1. In addition, the function of the first provision request transmission means in the claims is realized by the notification data acquisition unit 115 of the security device 1, and the function of the first acquisition means in the claims is mainly realized by the control unit 102. In addition, the function of the first update means in the claims is realized by the retransmission processing unit 116 of the security device 1, and the function of the first retransmission processing means in the claims is realized by the retransmission processing unit 116 of the security device 1.

The function of the second storage means in the claim is realized by the past report data file 1032 of the security device 1. The function of the third report processing means in the claim is realized by the second report processing unit 113, and the function of the second provision request transmission means in the claim is realized by the report data acquisition unit 115 of the security device 1. The function of the second acquisition means in the claim is mainly realized by the control unit 102, the function of the second update means in the claim is realized by the retransmission processing unit 116 of the security device 1, and the function of the second retransmission processing means in the claim is realized by the retransmission processing unit 116 of the security device 1.

The second notification destination device in the claims corresponds to the on-premises server device 8 in the embodiment. The function of the first provision request receiving means of the second notification destination device in the claims is realized mainly by the provision request accepting unit 807 of the on-premises server device 8, and the function of the provision data transmitting means of the second notification destination device in the claims is realized mainly by the provision data providing unit 808 of the on-premises server device 8.

The first destination device in the claims corresponds to the receiving server device 4 in the embodiment. The function of the notification data receiving means of the first destination device in the claims is realized mainly by the notification data receiving unit 405 of the receiving server device 4. The function of the notification data processing means of the first destination device in the claims is realized by the notification data receiving unit 405 and the notification data providing unit 406 of the receiving server device 4 working together.

Furthermore, a security device according to the present invention can be realized by forming a program that executes the processing shown in the flowcharts of Figures 9 and 10 and installing it in a security device equipped with a control unit including a CPU. That is, each function of the first notification processing unit 111, the fault determination unit 112, the second notification processing unit 113, the recovery determination unit 114, the notification data acquisition unit 115, and the retransmission processing unit 116 of the security device 1 can be realized as a function of the control unit of the security device by a program executed in the control unit.

The report data receiving unit 405 and the report data providing unit 406 of the receiving server device 4 can also be realized as functions of the control unit 402 of the receiving server device 4 by a program executed in the control unit 402 of the receiving server device 4. The report data receiving unit 505 and the report notification unit 506 of the security server device 5 can also be realized as functions of the control unit 502 of the security server device 5 by a program executed in the control unit 502 of the security server device 5.

1...security device, 101T...connection end, 101...first communication I/F, 102...control unit, 103...storage device, 1031...report data file, 1032...past report data file, 1033...post-failure report data file, 104T1-104Tn...connection end, 104...sensor detection unit, 105(1)-105(n)...monitoring sensor, 106...clock circuit, 107T...connection end, 107...second communication I/F, 111...first report processing unit, 112...failure determination unit, 113...second report processing unit, 114...recovery determination unit, 115...report data acquisition unit, 116...retransmission processing unit, 2...gateway, 3 internet, 4...receiving server device, 5...security server device, 6...control device, 7...other network, 8...on-premise server device

Claims (4)

a notification data generating means for generating notification data when an occurrence of an abnormality is detected;
a first notification processing means for transmitting the notification data formed by the notification data forming means to a first notification destination through a first network;
a fault determination means for determining whether a fault has occurred on the first network side;
a first storage means for storing and holding the report data that could not be transmitted to the first report destination as post-failure report data when the fault determination means determines that the fault has occurred;
a second notification processing means for transmitting the post-failure notification data stored in the first storage means to a second notification destination through a second network different from the first network;
a recovery determination means for determining whether or not the failure occurring on the first network side has been recovered from;
a first provision request sending means for sending, when the recovery determination means determines that the failure has been recovered from, a first provision request to the second report destination, the first provision request requesting the second report destination to provide the post-failure report data including an arrival time at the second report destination;
a first acquisition means for acquiring the post-failure report data including the arrival time returned from the second report destination in response to the first provision request as post-failure provision data from the second report destination;
a first updating means for updating the arrival time of the post-failure provision data corresponding to the post-failure provision data acquired by the first acquiring means among the post- failure notification data stored and held in the first storage means;
A security device characterized by comprising a first retransmission processing means for transmitting the post-fault report data, the arrival time of which has been updated by the first update means, to the first report destination via the first network. 2. The security device of claim 1,
a second storage means for storing and holding the past report data generated by the report data generating means and transmitted to the first report destination as past report data;
a third notification processing means for transmitting the past notification data stored in the second storage means to a second notification destination through a second network different from the first network when the failure determination means determines that the failure has occurred;
a second provision request sending means for sending a second provision request to the second report destination when it is determined by the recovery determination means that the failure has been recovered from, the second provision request requesting the second report destination to provide the past report data including an arrival time;
a second acquisition means for acquiring the past report data including the arrival time returned from the second report destination in response to the second provision request as past provision data from the second report destination;
a second updating means for updating the arrival time of the past report data corresponding to the past provision data acquired by the second acquiring means among the past report data stored and held in the second storage means;
A security device characterized by comprising a second retransmission processing means for transmitting the past report data, the arrival time of which has been updated by the second update means, to the first report destination via the first network. The security device according to claim 1 or 2,
The security device, wherein the notification data forming means forms the notification data to which a serial number is added. A security system in which a security device and a first notification destination device are connected through a first network, and the security device and a second notification destination device are connected through a second network different from the first network,
The security device is
a notification data generating means for generating notification data when an occurrence of an abnormality is detected;
a first notification processing means for transmitting the notification data formed by the notification data forming means to a first notification destination through a first network;
a fault determination means for determining whether a fault has occurred on the first network side;
a first storage means for storing and holding the report data that could not be transmitted to the first report destination as post-failure report data when the fault determination means determines that the fault has occurred;
a second notification processing means for transmitting the post-failure notification data stored in the first storage means to a second notification destination through a second network different from the first network;
a recovery determination means for determining whether or not the failure occurring on the first network side has been recovered from;
a first provision request sending means for sending, when the recovery determination means determines that the failure has been recovered from, a first provision request to the second report destination, the first provision request requesting the second report destination to provide the post-failure report data including an arrival time at the second report destination;
a first acquisition means for acquiring the post- failure report data including the arrival time returned from the second report destination in response to the first provision request as post-failure provision data from the second report destination;
a first updating means for updating the arrival time of the post-failure provision data corresponding to the post-failure provision data acquired by the first acquiring means among the post- failure notification data stored and held in the first storage means;
a first retransmission processing means for transmitting the post-failure report data, the arrival time of which has been updated by the first update means, to the first report destination through the first network;
The second destination device is
a first provision request receiving means for receiving the first provision request from the security device;
and a provision data transmission means for transmitting the post-fault notification data from the security device, the post-fault notification data having an arrival time at the security device added thereto, as the post-fault provision data to the security device in response to the first provision request from the security device,
The first destination device is
a notification data receiving means for receiving the notification data from the security device;
and a report data processing means for processing the received report data as if the received report data had a time of arrival added thereto, as if the received report data had arrived at the device at the time of arrival.

Images