JP5162034B2 - Home security monitoring system - Google Patents

Description

  The present invention relates to a home security monitoring system, and more particularly, to a system for providing home security services to each customer residence equipped with a home alarm network by a service provider.

  For example, as disclosed in WO2008 / 088079, a failure alarm system has been proposed conventionally. This system is designed to operate only in the user's home as a fire alarm for multiple rooms or places when a fire is detected in one of the multiple rooms or places. Has been. For this purpose, conventional alarm systems use a single master detector and multiple slave detectors, which are located at different locations and communicate over a home network. It is like that. Each of the master and slave detectors includes a detector that detects a fault or a fire condition, and an alarm unit that issues an alarm when the detector generates a fault signal indicating the occurrence of a fault condition. The master detector, in particular, receives a fault signal from any slave detector, generates an interlock fault signal, and sends it to all other detectors to simultaneously alert all detectors or rooms. Designed to do. Slave detectors, on the other hand, are designed to send fault signals to the master detector and optionally to other slave detectors, but are designed to relay fault signals to other slave detectors. It has not been. For this reason, only the master detector acts as a repeater, relays the failure signal to all other detectors, and issues alarms in any room by issuing alarms from all detectors. The integrity of the system has been increased so that this does not occur.

  In recent years, using the widely available computer network such as the Internet, the above-described individual home alarm network has been expanded to the integrated network service and system, and the failure status has been increased to a third level other than the individual user. There is an increasing demand to provide assistance services that are addressed by the elderly. In order to implement such an integrated service, it is required to use a server by a computer on the service provider side, and each user's home is used as an interface between the home alarm network and the server. It is required to use a gateway to collect fault signals transmitted within the alarm network. The server communicates with the gateway via the public computer network to recognize the fault condition detected in the home alarm network, and when the server receives the fault condition detected in the home alarm network, the support service Can be designed to provide

  Thus, it is necessary to establish communication between the gateway and the home alarm network, i.e. at least one detector. Therefore, the simplest solution is to use the communication protocol used in the home alarm network for communication between the home alarm network and the gateway, and to communicate between the gateway and the master detector. This is done using the relay function of this detector.

However, with such a simple solution, if a communication error occurs in the home alarm network, the server is notified of the failure status, and the same defect occurs even if the master detector fails. Therefore, it is considered inadequate for highly reliable and fail-safe services.Therefore, when implementing an integrated network system, the above-mentioned potential deficiencies are taken into consideration and well-harmonized with existing home alarm networks. Therefore, it is necessary to realize a highly reliable and fail-safe home security monitoring system.

WO2008 / 0888079

  The present invention provides a highly reliable and fail-safe home security monitoring system, that is, an integrated service system in which a server can reliably collect fault conditions detected by a home alarm network via different signal information paths. It was made to solve the problem.

  A home security monitoring system according to the present invention includes a plurality of detection terminals configured to detect a failure situation in a customer's house and generate a failure signal, a server configured by a computer, and installed in each house The gateway unit is provided. The server includes a terminal registration table that holds registration records regarding the respective detection terminals. The registration record includes a predetermined terminal code that identifies each detection terminal. Each detection terminal includes a wireless transceiver for transmitting the above failure signal to the other detection terminals via the first communication network. The gateway unit has communication means for communicating with the server via a public computer network, and the communication terminal establishes wireless communication with each of the detection terminals via the second communication network. Configured to receive a support request signal from at least one detection terminal and transmit the support request signal to the server. The server comprises a processor configured to receive the support request signal from the gateway unit and a warning means configured to generate a warning report when receiving the support request.

  Each of the detection terminals includes an alarm unit that issues an alarm when receiving the above-described failure signal generated by itself or a linked failure signal from one of the other detection terminals. Further, each detection terminal is configured to selectively function as a master or a slave. The master is defined to give the interlock failure signal when receiving the failure signal from any other detection terminal, and the slave transmits the failure signal to the master via the first communication network. It is prescribed to The gateway unit is configured to relay the support request signal to the server when receiving the support request signal.

  A feature of the present invention is that when each of the detection terminals generates the failure signal, the support request signal is generated, and the support request signal is transmitted to the gateway unit via the second communication network. The second communication network has a communication protocol different from that of the first communication network.

  Because of this feature, the server can receive the support request signal from the master or the slave and can recognize the failure status detected at the customer's home in a fail-safe manner, and between the first communication network and the second communication network. It is possible to eliminate possible interference between the two.

  Preferably, the gateway unit is configured to transmit a request reception confirmation signal to a detection terminal that transmits a support request signal, and each detection terminal does not receive the request reception confirmation signal within a predetermined response period. If so, the support request signal is configured to be retransmitted. For this reason, even if the transmission of the support request signal is temporarily disabled, the master and the slave can reliably transmit the support request signal to the server via the gateway unit.

  Further, a sensing terminal assigned as a slave can be programmed to first send the support request signal to the gateway unit and then send the fault signal to the master when a fault signal is generated. . For this reason, the gateway unit immediately transmits a support request signal to the server, and the server can recognize the failure status without delay. In addition, the slave is configured to retransmit the failure signal to the master when it does not receive the request receipt confirmation signal from the gateway unit within a predetermined response period, so that the master can know the failure signal reliably. .

  In a preferred embodiment, the gateway unit has an assigning means, and the assigning means assigns the detection terminal that is first turned on and communicates to the gateway unit as the master, and is turned on later. The other detection terminal that communicates with the gateway unit is assigned as the slave. For this reason, this system can be easily deployed in customer residences without requiring the customer to understand how to distinguish master from slave or vice versa.

  The above and other advantages of the present invention will become more apparent from the following detailed description with reference to the accompanying drawings.

FIG. 1 is a schematic diagram showing a home security monitoring system according to the present invention. FIG. 2 is a schematic diagram showing a terminal registration table of a server in addition to a terminal registration table and a terminal status table respectively prepared in a detection terminal and a gateway unit constituting the system. FIG. 3 is a block diagram illustrating a server. FIG. 4 is a block diagram showing a detection terminal. FIG. 5 is a block diagram showing a gateway unit. FIG. 6 is a timing diagram showing a scheme in which detection terminals are assigned as masters and slaves. FIG. 7 is a timing diagram showing how the system is reconfigured when one of the slaves is removed from the system. FIG. 8 is a timing diagram showing how the system is reconfigured when the master is deleted from the system. FIG. 9 is a timing diagram of how the system is reconfigured when one of the slaves is replaced with a new sensing terminal. FIG. 10 is a timing diagram of how the system is reconfigured when the master is replaced with a new sensing terminal. FIG. 11 is a timing chart showing a series of operations when a failure situation is detected by one of the detection terminals.

  FIG. 1 shows a home security monitoring system using a failure detection subsystem according to the present invention. The home security monitoring system is provided by a service provider, and includes a server 30 that is a computer installed on the service provider side, and this server is, for example, a fire outbreak from the home alarm network of each customer house. Collects fault information and provides assistance, such as sending qualified personnel to customer homes or notifying customers on the go. The home network is realized by a subsystem developed in each customer house. For example, a plurality of detection terminals 50 such as smoke detectors, and a gateway unit 10 that operates as an interface between the detection terminals and the server 30. Is provided. The server 30 includes or is linked to a warning device 38, and this warning device generates a warning report when receiving failure information that is a support request signal from any of the detection terminals 50 via the gateway unit 10. To do. As will be described in detail later, the detection terminals are configured to communicate with each other via the first communication network and to communicate with the gateway unit 10 via the second communication network.

  This system includes an input device 100 such as a personal computer belonging to each customer. This input device communicates with a server 30 via a public computer network, that is, the Internet, and registers a detection terminal 50 in the server. . For this reason, the server 20 is provided with a terminal registration table 37, which is a terminal such as a manufacturer's serial number that the customer has entered using the input device 100 as shown in FIG. It is configured to store the records. No other input is required on the customer side. The first requirement for customers to develop a home alarm network is simply to add or delete terminal code records.

  As shown in FIG. 3, the server 30 includes a communication module 32 that communicates with the input device 100 and the gateway unit 10 via the public network, a registration module 34, and a failure event in addition to the memory that forms the terminal registration table 37. A processor constituting the module 36 is provided. The registration module 34 is programmed to add, delete, and update registration records in the terminal registration table 37 in response to input by the customer at the input device 100. The failure event module 36 is programmed to operate the alert device 38 to provide an alert report in response to the assistance request signal transmitted through the gateway unit 10 and received by the communication module 32. The warning device may be a display, a speaker, or the like, as long as it can provide information to the service provider staff.

  The detection terminal 50 used in the present invention has the same configuration, and enables each detection terminal to function as a master or a slave. The detection terminal 50 receives power from a built-in battery (not shown), and includes a power switch 52, a smoke sensor 56, an alarm unit 58, a wireless transceiver 68, a processor, and a memory, as shown in FIG. Yes. The smoke sensor 56 is configured to detect smoke concentration in the atmosphere and output a concentration signal indicative of the detected smoke concentration to the fault event module 64 implemented by the processor. When the smoke concentration exceeds a predetermined threshold, the fault event module 64 generates a fault signal indicating a possible fire and outputs this signal to the alarm unit 58, which in response generates an alarm sound. The failure signal is transmitted by the wireless transceiver 68 to the other detection terminals 50 forming the home alarm network via the first communication network, and the second communication network is transmitted to the gateway unit 10 as a support request signal. Sent through. For this reason, the failure event module 64 generates a failure signal conforming to the first communication protocol specific to the first communication network, is specific to the second communication network, and conforms to the second communication protocol different from the first communication protocol. A support request signal is generated.

  When the master receives a failure signal from any of the other detection terminals, the master is defined to give the interlock failure signal, and the slave transmits the failure signal to the master via the first communication network. It is stipulated that an alarm be given when a message is received. The interlock failure signal is generated based on the first communication protocol, and is transmitted from the master to all the slaves constituting the home alarm network, and simultaneously gives an alarm at each detection terminal. The master is also configured to generate a support request signal and send it to the gateway unit 10 when a failure signal is received from any of the slaves or when the failure signal is generated by itself. In this sense, the master operates as a repeater and transmits the support request signal to the gateway unit in parallel with the support request signal transmitted from the slave to the gateway unit directly. The slave is also configured to transmit a failure signal to another slave when it detects a failure condition, i.e., a fire occurrence. In order to perform a related operation between the master and the slave, the detection terminal has a terminal registration table 67 created in the memory, and as shown in FIG. 2, a master / slave identifier indicating the master and the slave, The node number record for distinguishing from other detection terminals is stored in the alarm network. Further, the record of the terminal registration table 67 includes a terminal code. When a detection terminal is assigned as a master, as will be described later, a master / slave identifier and node numbers for all detection terminals are stored. On the other hand, when a detection terminal is assigned as a slave, a master / slave identifier and node numbers for itself and the master are stored.

  The processor forms a configuration / registration module 62, which, in cooperation with the gateway unit 10, realizes terminal configuration for assigning masters and slaves and terminal registration for determining node numbers in relation to master / slave identifiers. To do.

  As shown in FIG. 5, the gate unit 10 includes a wireless transceiver 11 for communicating with the server 30 and the detection terminal 50 via the second communication network. The second communication network uses a specific communication protocol different from that of the first communication network, and is distinguished from the first communication network that couples the detection terminals. The gateway unit 10 also includes a memory that implements a terminal status table 17 having the same configuration as the terminal registration table 37. The terminal status table is updated to reflect changes in the registration record in the terminal registration table 37. Is done. Further, the gateway unit 10 includes a processor that constitutes a failure event module 12, an authentication module 14, and an assignment module 16. The failure event module 12 is programmed to relay a support request signal from any of the detection terminals 50 to the server 30 when it is received. The authentication module 14 authenticates the detection terminal, that is, checks whether the detection terminal 50 that makes the configuration request is recorded in the terminal status table 17. If the detection terminal 50 is recorded in the terminal status table 17, the authentication module 14 Permits participation in home alarm network. The assignment module 16 is programmed to assign a master to one of the authorized sensing terminals 50 and assign a slave to another authorized sensing terminal. The assignment result is recorded in the terminal status table 17 and the terminal registration table 67 of each detection terminal.

  Next, the terminal configuration and terminal registration will be described in detail with reference to FIG. After the terminal code for each detection terminal 50 installed in the house is input to the terminal registration table 37 by the customer, the gateway unit 10 records the terminal code in the terminal status table 17 when first communicating with the server. . In this way, the gateway unit 10 is ready for terminal configuration. When one of the detection terminals is first energized with the power switch turned on, the detection terminal transmits a configuration request including the terminal code to the gateway unit 10. When the gateway unit authenticates the detection terminal that transmits the configuration request as recorded in the terminal status table 17, the gateway unit 10, that is, the allocation module 16 is the first one that establishes communication with the gateway unit 10. As it is, a configuration request is returned to the detection terminal, and a request for transmission of a configuration response with a unique encryption key is sent from the detection terminal to the gateway unit 10. When the gateway unit 10 confirms that the configuration response is valid, it sends a configuration command to assign the master to the detection terminal, and simultaneously detects the master / slave identifier of “1” and the node number of “00”, both indicating the master. Set to the terminal, and update the record relating to this detection terminal in the terminal status table 17. The configuration request and the configuration response are prepared only for exchanging the encryption key between the detection terminal and the gateway unit for encrypted communication, and may be omitted. That is, the gateway unit 10 can be configured to transmit a configuration command in a form that directly responds to a configuration request from a detection terminal whose terminal code is authenticated.

  When the configuration command is received at the detection terminal 50, the configuration / registration module 62 writes the master / slave identifier “1” and the node number “00” in the terminal registration table 67 in association with its own terminal code accordingly. As a result, the detection terminal (hereinafter also referred to as DT master) is ready for registration of another detection terminal (hereinafter also referred to as DT slave) that forms a home alarm network with the DT master.

  Next, when one of the other detection terminals 50 (DT slave) is energized by the operation of the power switch 52, the detection terminal 50 (DT slave) proceeds to the procedure of stage 1 (that is, the slave configuration procedure), and the configuration A request is transmitted with the terminal code, and optionally a configuration request from the gateway unit 10 is received and a configuration response is returned to the gateway unit 10. When the terminal code is recorded in the terminal status table 17, the gateway unit 10 transmits a configuration command to the detection terminal 50, thereby assigning a slave to this detection terminal (DT slave) and configuring / registering the DT slave. Based on this configuration command, the module 62 writes the master / slave identifier “0” in the terminal registration table 67 in association with its own terminal code. When the configuration command is transmitted to the previous detection terminal, that is, the DT master and later to the DT slave that establishes communication with the gateway unit 10, the gateway unit 10 includes the registration command in the configuration command. That is, the assignment module 16 generates a registration command that is added to the configuration command. Upon receiving such a configuration command, the DT slave goes to the stage 2 procedure (slave registration procedure) and wakes up the DT master by sending a registration request to the DT master.

  When receiving the registration request, the DT master returns a request approval to the DT slave and returns a registration inquiry to the gateway unit 10. After this, the gateway unit 10 returns a slave registration permission, which includes the node number “01” created by the assignment module 16 and given to the DT slave. The DT master then sends a registration command, along with the master / slave identifier and the node number of the DT master, to the DT slave having the node number “01” indicating that it is the first DT slave recognized by the DT master. As a result, the DT slave configuration / registration module 62 updates its own record as the node number “01”, and adds the DT master record to the terminal registration table 67 as shown in FIG. When the update of the terminal registration table is completed, the DT slave returns a registration response to the DT master, and the DT master adds a record of the DT slave to the terminal registration table 67. Upon receipt of the registration response from the DT slave, the DT master transmits a slave registration request to the gateway unit 10, and the gateway unit 1 performs DT relating to the node number associated with the master / slave identifier and terminal code in the terminal status table 17. The records of the master and the newly added DT slave are updated. After updating the terminal status table 17, the gateway unit 10 sends a registration completion response to the DT slave to complete the slave registration procedure, that is, the stage 2 procedure.

  If the registration completion response is not received within 2500 milliseconds from the configuration request, the above slave configuration procedure and subsequent slave registration procedure are repeated. When the above registration is completed for all other DT slaves, the DT master recognizes that each DT slave constitutes a home alarm network, and similarly, each DT slave recognizes the DT master. A DT slave can transmit a failure signal to the DT master and other DT slaves via the first communication network, that is, the home alarm network, and each DT slave supports when a failure signal is received from any DT slave. In addition to being able to send the request signal directly to the gateway unit 10 via the second communication network, the DT master can send the assistance request signal to the gateway unit 10 via the second communication network.

  FIG. 7 shows a time chart showing how the system operates when one of the DT slaves is removed from the system. When a DT slave, for example, one having a node number “01” fails and the power is turned off, the customer uses the input device 100 to record a record of the failed DT slave from the terminal registration table 37 in the server 30. delete. In the terminal status table 17 of the gateway unit 10, the change of this record is reflected when communicating with the server 30. That is, the terminal status table 17 is updated and a deletion flag indicating that this record should be deleted is added to the record of the failed DT slave. In this situation, the DT master functions to perform a status check procedure for checking whether the registered DT slave is currently available. The status check procedure is started by operating the setting button 54 of the DT master. When the setting button 54 is operated, the configuration / registration module 62 generates a status check request for all existing, that is, registered DT slaves in response thereto, and is registered in the terminal registration table 67. It is checked whether the DT slave is registered as valid in the terminal status table 17 of the gateway unit 10. When the status request approval is returned to the DT master, the gateway unit 10 deletes the failed DT slave from the terminal registration table 67, that is, the record of the DT slave to which the deletion flag is added in the terminal status table 17. Give a directive. In response to this slave removal command, the DT master deletes this record from its terminal registration table, and returns a slave deletion confirmation to the gateway unit, so that the gateway unit actually deletes the record with the deletion flag. As a result, the terminal status table is updated. When the setting button 54 is pressed with another non-failed DT slave, for example, the node number “02”, this DT slave records the same status check request, and the DT slave “02” is recorded in the terminal status table of the gateway unit. However, no change is required in the terminal registration table 67 of the DT slave.

  The status check procedure is started by pressing the setting button 54 for a short time, for example, 4 seconds or less. On the other hand, if the setting button 54 is pressed for a long time exceeding 4 seconds, the DT master or DT slave performs the above-described status check and then performs a manual test. In the manual test, a virtual fault signal is generated to check whether the home alarm system reacts and issues an alarm from each detection terminal. In this case, after transmitting a status check request and receiving a status request approval, the DT master or DT slave transmits a test request to the gateway unit, and the gateway unit returns a test request approval. Upon receipt of the test request acknowledgment, the DT master or DT slave can enter a manual test mode that provides a virtual fault signal for generating an alarm within the home network. In this case, the gateway unit recognizes that the resulting alarm is false and is simply the result of the test.

  In addition, as will be described later with reference to FIG. 11, when there is a failure status detected in the home alarm network, an alarm stop signal is generated by pressing and holding the setting button.

  Furthermore, each DT master or DT slave is operated intermittently, that is, intermittently wakes up to transmit a failure signal and a support request signal as soon as the failure status is detected by checking whether a failure status has been detected. It becomes an operation mode. In the drawing, such an intermittent operation mode of the terminal is expressed as “intermittent operation”. Each of the DT master and the DT slave is configured to transmit a status check request to the gateway unit at regular intervals in order to check whether the second communication network is operating normally.

  FIG. 8 shows a time chart showing how the system operates when the DT master is deleted. When the DT master fails and is excluded from the system, the customer is required to delete the record of the failed DT master from the terminal registration table 37 of the server 30. As a result, the gateway unit 10 updates the terminal status table 17 to reflect the deletion of the record in its own terminal status table 17. Under such circumstances, when the setting button 54 of one of the DT slaves, in this case, the DT slave having the node number “01” is pressed for a short time, the DT slave transmits a status check request to the gateway unit 10. Perform the status check procedure. However, since the gateway unit 10 cannot recognize the DT master in its own terminal status table 17, it cannot return a status request approval to the DT slave. After repeatedly transmitting the status check request a predetermined number of times within a predetermined period after the setting button 54 is pressed shortly, the DT slave is allowed to perform a configuration procedure on the gateway unit 10. Upon receiving a configuration request from the DT slave, the gateway unit 10 performs a reconfiguration routine to reestablish the home alarm network. This reconfiguration routine is continued by the gateway unit 10 that sends back the configuration command. With this configuration command, the receiving DT slave is assigned as a new master, and its terminal registration table 67 is set to the master / slave identifier “1”. Update. That is, as described with reference to FIG. 6, when a configuration request is received from a detection terminal that has established communication with the gateway unit, the gateway unit refers to its own terminal status table and records the detection terminal that transmits the configuration request. In the terminal status table and the assignment module 16 permits the assignment module 16 to assign the master to the detection terminal that transmits the configuration request only when there is no record of the detection terminal already assigned as the master in the terminal status table.

  At this point, the gateway unit 10 updates the terminal status table 17 and rewrites the master / slave identifier of the new DT master. Thereafter, the DT master transmits a status check request to the gateway unit 10, and returns a status request approval to the DT master. As a result, the DT master clears the remaining DT slave records for the node number, and the gateway unit clears the remaining DT slave records for the node number. Subsequently, the gateway unit 10 prepares for the reconfiguration routine in cooperation with the DT master. That is, upon receiving a configuration request from each of the remaining DT slaves, in this case, the DT slave with the note number “02”, the gateway unit 10 designates a new node number “01” and a master / slave identifier “0”. The command is generated and transmitted to the DT slave, and the DT slave receiving the command updates its terminal registration table 67 so as to correspond to this, and completes the stage 1 procedure (slave configuration procedure). At this point, the gateway unit 10 updates its terminal status table 17 to reflect the changes made to the DT slave. The configuration command generated by the gateway unit 10 includes a registration command, which causes the DT slave to move to the stage 2 procedure (that is, the slave registration procedure). This procedure will be described in detail with reference to FIG. As described above, it starts by sending a configuration request to wake up a new DT master, and is completed by receiving a registration completion response from the gateway unit 10. Similarly, any of the remaining DT slaves complete the above-described reconfiguration routine by simply pressing the set button 54. When the reconfiguration for all existing DT slaves is completed, in addition to the DT master and the DT slave being able to transmit to the gateway unit 10 by individual node numbers, the new DT master will store its terminal registration table 67. By updating, the DT slave can be recognized by the node number for communication in the home alarm network.

  FIG. 9 shows another time chart showing how the system operates when replacing a DT slave with a new one. When a registered DT slave (for example, node number “01”) fails and must be replaced with a new detection terminal, the customer uses the input device 100 to record a record of the failed DT slave on the server 30. Is deleted from the terminal registration table 37 and a record of a newly added detection terminal is inserted into the terminal registration table 37. This change in the record is reflected in the terminal status table 17 of the gateway unit 10 when the gateway unit 10 communicates with the server 30. Under this situation, when a new DT slave communicates with the gateway unit 10 by energization, the stage 1 procedure and the stage 2 procedure are completed by the interaction with the gateway unit 10 as described above. A slave identifier “0” and a new node number are given, whereby a new DT slave is recognized by the gateway unit 10 and the DT master, and reliable communication can be performed between them. After that, the DT master performs a status check procedure as to whether or not the DT slave recorded in the terminal registration table is currently available in the system by pressing the setting button 54 for a short time. That is, the DT master creates a status check request and transmits it to the gateway unit 10, and whether each DT slave recorded in the terminal registration table 67 is recorded as a valid person in the terminal status table 17 of the gateway unit 10. Check out. When the gateway unit 10 returns a status request approval to the DT master, it generates a slave deletion command for deleting from the terminal registration table 67 the record of the terminal to which the deletion flag is attached in the terminal status table 17. In response to the slave deletion command, the DT master deletes the record from the terminal registration table 67, returns a slave deletion confirmation to the gateway unit 10, and completes deleting this record from the terminal status table. . Thereafter, when the setting button of the DT slave is pressed for a short time, a status check request is transmitted from the DT slave to the gateway unit 10, and the gateway unit 10 does not need to change the terminal registration table of the requesting DT slave. Status request approval is returned.

  When the DT master fails and is replaced with a new one, the system operates as shown in FIG. Under this circumstance, the user updates the server's terminal registration table by deleting the failed DT master record and inserting the terminal code of the new sensing terminal. Changes accompanying this are reflected in the terminal status table 17 of the gateway unit 10. When a new detection terminal is energized and establishes communication with the gateway unit 10 by transmitting a configuration request, the gateway unit 10 determines whether there is a record of the detection terminal assigned to the terminal status table 17 by mass assignment. Check and complete the stage 1 procedure by sending a configuration command to assign the master to this new sensing terminal if there is no record in the terminal status table indicating the sensing terminal assigned as the master. In this way, the newly added detection terminal is recognized as a new DT master. Thereafter, the new DT master transmits a status check request to the gateway unit 10, and receives a status request approval for confirming that the DT master is recorded in the terminal status table. At this time, since the DT slave record is not input to the terminal registration table 67, the DT master does not recognize the associated DT slave. Further, the gateway unit 10 clears the node number of each DT slave from the terminal status table, and even if each DT slave tries to communicate with the gateway unit and presses the setting button for a short time, the status is acknowledged to each DT slave. Can not return.

  Next, when the setting button is pressed for a short time, the DT master transmits a status check request to request the gateway unit 10 to accept a configuration request from each DT slave and a subsequent status check request. After that, the DT slave performs the configuration procedure for the gateway unit, and is permitted to receive the configuration command and complete the stage 1 procedure and the stage 2 procedure in the manner described above. It is redefined as a slave having a node number given from the gateway unit and recorded in the terminal registration table of the DT master. In this way, all existing DT slaves are redefined and recognized by the DT master and gateway unit.

  FIG. 11 shows how the system operates when a fault condition is detected on one of the DT slaves. In this example, a DT slave having a node number “01” (hereinafter referred to as a detected DT slave) is woken up upon detection of a failure condition, issues an alarm, and transmits a support request signal to the gateway unit 10. In response to this, the gateway unit relays a support request signal to the server 30 to notify the failure status, and returns support request approval to the detected DT slave. Immediately after this, the detected DT slave transmits a failure signal to wake up the DT master and other DT slaves (hereinafter referred to as non-detected DT slaves). In response to the failure signal, the non-detected DT slave issues an alarm, and the DT master generates an interlocking failure signal and transmits it to the non-detected DT slave, whereby each DT slave issues an alarm. If a non-detected DT slave cannot wake up due to some temporary communication error, it is woken up by an interlock failure signal and an alarm is issued. When the detected DT slave and the non-detected DT slave wake up, they return a linked alarm response to the DT master, and in response, the DT master repeatedly sends a support request signal to the gateway unit, and simultaneously sends a linked failure signal. The interlock mode for transmitting to the repeatedly detected DT slave and the non-detected DT slave is entered.

  When the setting button is pressed in a situation where the interlock failure signal is repeatedly sent, the DT master sends an alarm stop command to the detected DT slave and the non-detected DT slave, and at the same time, the DT master requests the DT slave to stop the alarm. An alarm status signal indicating that the gateway unit 10 is in operation. The alarm stop command and the alarm status signal are repeatedly transmitted for a predetermined period of 90 seconds, for example. After this period, the DT master sends an alarm stop confirmation requesting the detected and non-detected DT slaves to return an alarm stop response indicating that the alarm stop command has been accepted. However, while the detected DT slave is still detecting the failure status, the detected DT slave returns an alarm stop response indicating the failure status, and the DT master responds by transmitting a linked failure signal until the failure status disappears. Even after the DT master transmits an alarm stop command, it continues to transmit a support request signal including information that the failure status is still detected in the detected DT slave to the gateway unit 10.

  When the failure situation disappears, the detection DT slave transmits an alarm stop request to the DT master and stops its own alarm. The DT master then responds by sending an alarm stop confirmation command to all DT slaves, requesting that the DT slave return an alarm stop response that includes information on whether the DT slave is ready to stop the alarm. Upon receiving an alarm stop response, the DT master transmits an alarm stop command to the DT slave to stop the alarm at each DT slave. When the alarm is stopped, each DT slave returns an alarm stop response indicating the alarm status to the DT master and enters the intermittent reception mode. Similarly, when receiving a warning stop response from the DT slave, the DT master enters the intermittent reception mode. Furthermore, after receiving the alarm stop request, until the alarm stop response is received, the DT master sends an alarm status signal to the gateway unit together with information that the DT master has received an alarm stop request from the detected DT slave. Function.

  In addition, the detection terminal issues an audio warning “Boom-Boom Smoke Warning” when a fault condition is detected by itself, and if it is detected by another detection terminal, “Boom-Boom in another room”. It is designed to emit a voice alert called “Smoke Warning Warning”.

  When the detection terminal is in the intermittent operation mode, for example, at a fixed interval of every 33 hours, a status check request is sent along with information on the battery status and some other parameters indicating whether the detection terminal is normal. Transmit to the gateway unit 10.

  Although the present invention has been described with reference to exemplary embodiments, it is possible to appropriately combine the individual features described above in order to construct an improved invention other than the claimed invention. .

Claims (3)

A home security monitoring system comprising a detection terminal, a server configured by a computer, and a gateway unit,
The detection terminal is configured to detect a failure condition in a customer's house and generate a failure signal, and each detection terminal transmits the failure signal to the other detection terminals via the first communication network. With a wireless transceiver to transmit,
The server configured by a computer includes a terminal registration table that holds a registration record for each of the plurality of detection terminals, and the registration record includes a predetermined terminal code that identifies each detection terminal,
The gateway unit is installed in each house, and has communication means for communicating with the server via a public computer network. The communication terminal performs second communication with each of the detection terminals. It is configured to establish wireless communication via a network, receive a support request signal from at least one of the detection terminals, and transmit it to a server,
The server comprises a processor configured to receive the support request signal from the gateway unit, and warning means configured to generate a warning report when receiving the support request,
Each of the detection terminals includes an alarm unit that issues an alarm when it receives the failure signal generated by itself or a linked failure signal from one of the other detection terminals,
Each of the detection terminals is configured to selectively function as a master or a slave, and the master gives the interlock failure signal when receiving the failure signal from any of the other detection terminals. The slave is defined to send the fault signal to the master via a first communication network;
The gateway unit is configured to relay it to the server when receiving the support request signal,
Each of the detection terminals is configured to generate the support request signal when the failure signal is generated, and transmit the support request signal to the gateway unit via the second communication network. the second communication network has to have a communication protocol different from the first communication network,
The gateway unit has an assigning unit, and the assigning unit assigns the detection terminal that is first turned on and communicated to the gateway unit as the master, and is later turned on and the gateway unit is turned on. A home security monitoring system configured to assign another detection terminal that communicates with the slave as the slave . The gateway unit is configured to transmit a request receipt confirmation signal to the detection terminal that transmits the support request signal.
2. The configuration according to claim 1, wherein each of the detection terminals is configured to retransmit the support request signal when the request reception confirmation signal is not received within a predetermined response period. 3. Home security monitoring system. The slave is programmed to first send the support request signal to the gateway unit when the fault signal is generated, and then send the fault signal to the master;
The gateway unit is configured to transmit a request receipt confirmation signal to a slave that transmits the support request signal.
2. The slave according to claim 1, wherein the slave is configured to retransmit the failure signal to the master if the slave does not receive the request receipt confirmation signal within a predetermined response period. Home security monitoring system.

Images