WO2010097964A1

WO2010097964A1 - Hazard detection subsystem for use in a home security surveillance system

Info

Publication number: WO2010097964A1
Application number: PCT/JP2009/054244
Authority: WO
Inventors: Junichi Suzuki; Tomohiro Suzuki; Seiji Nimura; Takashi Fujii; Dan Hovang
Original assignee: Panasonic Electric Works Co., Ltd.; Securitas Direct Ab
Priority date: 2009-02-27
Filing date: 2009-02-27
Publication date: 2010-09-02
Also published as: CA2753286C; EP2401728A1; CA2753286A1; JP2012519315A; EP2401728B1; JP5238082B2

Abstract

A hazard detection subsystem for use in an integrated home security surveillance system. The subsystem has a gateway unit and detection terminals each configured to detect a hazardous condition and issue a hazard signal upon detection of such condition. The gateway unit acts as an interface to the surveillance system to notify the hazardous condition in the form of an aid-requesting signal. The detection terminal is of a universal design which selectively functions as a master and a slave. The master generates a linking hazard signal to all the detection terminals for generating the alarm at each of the terminals, while the slave transmits an aid-requesting signal to the gateway unit in addition to the hazard signal. An assigning means is included in the gateway unit to assign the master to one of the detection terminals that is energized to establish communication first with the gateway unit, and assign the slave to the other detection terminal that is energized to establish communicate later with the gateway unit.

Description

DESCRIPTION

HAZARD DETECTION SUBSYSTEM FOR USE IN A HOME SECURITY SURVEILLANCE SYSTEM

TECHNICAL FIELD

The present invention is directed to a hazard detection subsystem, and more particularly to such subsystem adapted in use for a home security surveillance system in which a service provider implements a home security service to individual customer's homes respectively equipped with in-house alarm network. BACKGROUND ART

There has been proposed a hazard alarm system, for example, as disclosed in WO 2008/088079 that is designed to operate solely in a user's home for giving a fire alarm in a multiplicity of rooms or locations when any one of the locations is detected to see a fire occurrence. For this purpose, the prior alarm system utilizes a master detector and a plurality of slave detectors, which are disposed in different locations and are communicated with each other through an in-house network. Each of the detectors incorporates a detector for detection of a hazard or fire condition as well as an alarm unit which issues an alarm upon the detector generating a hazard signal indicative of the occurrence of the hazardous condition. The master detector is specifically designed to receive the hazard signal from anyone of the slave detectors and to generate an interlocking hazard signal and transmit the same to all the other detectors for simultaneous alarm at every detectors or rooms. While on the other hand, the slave terminal is designed to transmit the hazard signal to the master detector and optionally to the other slave detectors, but not to relay the hazard signal to the others. Thus, only the master detector acts as a repeater to relay the hazard signal to all the other detectors in order to successfully issue the alarms from all of the detectors for enhancing system integrity against possible failure of issuing the alarm in any one of the rooms.

In recent years, there is a growing demand of expanding the above individual in-house alarm networks to an integrated network service or system with the use of a widely-available computer network, e.g. the Internet, in order to add an assistant service of dealing with the hazardous condition by a third party other than the individual users. When implementing such integrated network service, it is required to employ a computer-based server on the side of a service provider, and a gateway in each of the users' homes as an interface between the in-house alarm network and the server so as to collect the hazard signal transmitted within the in-house alarm network. The server can be designed to communicate through the public computer network with the gateway so as to acknowledge hazardous condition detected in the in-house alarm network for providing the assistance service upon receiving of the hazardous condition detected in the in-house alarm network.

In order to take advantage of the matured in-house alarm network or subsystem utilizing the master detector as distinguished in its repeater function from the slave detectors, the system is required to identify the master detector and the slave detectors at an initialization of the system, i.e., at the time of installing the detectors in the individual users' home. When the master detector and the slave detector are provided as differently designed ones, no particular difficulty is expected at the initialization. However, when the detector of a universal design is provided to operate selectively as the master and slave for the sake of reducing complexity and manufacturing cost of the detectors, it is rather cumbersome for the user to set particular ones of the detectors respectively as the master and the slave, since most users are assumed to be unfamiliar with how to designate the master as distinguished from the slave.

Accordingly, a particular solution has to be made to settle a problem of enabling the user to easily assign the master and the slave to the individual detectors without being informed how to discriminate the master from the slave. DISCLOSURE OF THE INVENTION

The present invention has been achieved to provide a hazard detection subsystem which can be easily adapted to individual users' home, yet assuring an integrated home security surveillance service of providing assistance by the third party to the individual users equipped with the in-house alarm network.

The hazard detection subsystem in accordance with the present invention is utilized in a home security surveillance system which includes a computer-based server configured to store an enrollment record relating to a plurality of detection terminals installed in a customer's home and receive an aid-requesting signal originating from at least one of said detection terminals, and an input device adapted in use to communicate with the server through a public computer network in order to enter and update the enrollment record in the server. Also included in the server is an alert means which is configured to provide an alert report in response to the server receiving the aid-requesting signal.

The hazard detection subsystem includes a plurality of the detection terminaJs and a gateway unit. Each of the detection terminals is configured to detect a hazardous condition in a customer's home and generate a hazard signal, and is equipped with a radio transceiver for transmitting the hazard signal to the other detection terminal through a first communication network. The gateway unit is adapted in use to be installed in the customer's home, and includes a communication means configured to communicate with the server through the public computer network and to establish a radio communication with the detection terminals through a second communication network.

Each of the detection terminals includes an alarm unit which provides an alarm upon generating the hazard signal or receiving a linking hazard signal from one of the other detection terminals. Each detection terminal is also configured to function selectively as a master and a slave. The master is defined to provide the linking hazard signal when receiving the hazard signal from any one of the other detection terminals, while the slave is defined to transmit the hazard signal to the master through the first communication network. Further, each detection terminal is configured to generate and transmit the aid-requesting signal to the gateway unit through the second communication network upon generating the hazard signal. In this connection, the gateway unit is configured to relay the aid-requesting signal to the server upon receiving the aid-requesting signal.

The characterizing feature of the present invention resides in that the gateway unit includes an assigning means which is arranged to assign the master to one of the detection terminals that is energized to establish communication first with the gateway unit, and assign the slave to the other detection terminal that is energized to establish communicate later with the gateway unit. With this configuration, the subsystem can be easily developed in the customer's home without requiring the customer to understand how to discriminate the master from the slave, and vice versa. <master registration / replacement

The gateway unit is preferred to include a terminal status table which stores a master/slave index indicative of whether each of the detection terminals is assigned as the master or slave, in addition to the terminal code for each of said detection terminals. In addition, the gateway unit is programmed to refer to the terminal status table in response to a configuration demand transmitted from the detection terminal establishing communication with the gateway unit, and permit the assigning means to assign the master to the detection terminal transmitting the configuration demand only when the terminal status table shows a record of the detection terminal transmitting the configuration demand, and shows no record of any detection terminal already assigned as the master. Thus, when the master becomes defective and is removed from the subsystem, the gateway unit can assign one of the other detection terminals or newly added detection terminal as a new master for maintaining the system integrity without requiring the user to refer to a complicated installation instruction.

Preferably, each of the detection terminals includes a terminal registration table configured to register said terminal code, a master/slave index indicative of said master or said slave, and a node number which discriminates each one of said detection terminals from the other. Each detection terminal is also configured to transmit to the gateway unit a configuration demand accompanied with its own terminal code, when it is energized to establish communication first with the gateway unit. In this case, the gateway unit is programmed to check whether the detection terminal sending the configuration demand is registered in the terminal status table, and permits the assigning means to send a configuration instruction of assigning the master or slave to the detection terminal when such detection terminal is recorded in the terminal status table. The assigning means is configured to send a registration instruction to the detection terminal when such detection terminal is recorded in the terminal status table and also it is assigned as the slave. Each detection terminal is programmed to make, in response to the registration instruction, a terminal registration which executes steps of:

1 ) requesting the master to receive a permission from the gateway unit that the terminal status table has a record of the terminal code corresponding to the requesting detection terminal;

2) requesting the master, upon reception of the permission, to allocate the node number to the requesting detection terminal and to send thus allocated node number to the gateway unit;

3) requesting the master to enter thus allocated node number in associate with the terminal code and the master/slave index of the requesting detection terminal in the terminal registration table of the master; and

4) storing thus obtained node number in association with the terminal code and the master/slave index of the requesting detection terminal, in addition to the terminal code and a predetermined node number of the master, in the terminal registration table of the requesting detection terminal.

According to the above features, the detection terminal assigned as the slave, i.e., one that is first to communicate with the gateway unit after the gateway unit has assigned the master to preceding detection terminal, is successfully registered in the terminal registration table of the master as belonging to the master for establishing a relation between the master and the slave. All such registration steps can be done solely by the subsystem, without requiring a cumbersome registration work on the side of the user.

Further, when the master becomes defective and is removed in the established subsystem, the gateway unit operates to select one of the remaining detection terminals as a replacing master when such detection terminal comes first to communicate with the gateway unit after removal of the defective master. In order to enable such promotion of the existing slave to the new master, following features are added in the above subsystem.

The detection terminal is configured to register its terminal registration table, when assigned as the master, the terminal code, the master/slave index and the node number for all of the detection terminals. The detection terminal is also configured to register in its own said terminal registration table, when assigned as the slave, the terminal code, the master/slave index, and the node number of its own, in addition to the terminal code, the master/slave index, and the node number of the master. Further the detection terminal is provided with a configuration means and a set button, which upon being manipulated, activates the configuration means to send a configuration demand to the gateway unit and receive therefrom a configuration instruction by which the detection terminal is assigned as the master or the slave.

In this connection, the gateway unit is configured to check whether a condition is satisfied in which the terminal status table shows no record of the detection terminal assigned as the master and shows a record of at least one remaining detection terminal, and to execute, when such condition is satisfied, a reconfjguration routine in response to receiving the configuration demand from any one of the remaining detection terminal of which record is read from the terminal status table. The reconfiguration routine comprises steps of:

1 ) deleting the master/slave index and the node number for all the remaining detection terminals from the terminal status table;

2) assigning the master to one of the remaining detection terminals which comes into communication with the gateway unit first after having its set button manipulated, and sending the configuration instruction as well as the registration instruction to the other ones of the remaining detection terminals in response to the detection terminal being activated by manipulation of the set button.

In this manner, the restructuring of the master and the slave as well as reregistration of the relation between the master and the slave can be easily completed under the control of the gateway unit, while only requiring the user to manipulate the set button.

Preferably, the detection terminal assigned as the slave is programmed to transmit the hazard signal as the aid-requesting signal first to the gateway unit upon generating the hazard signal, and subsequently transmit the hazard signal to the master. Thus, the gateway can promptly transmit the aid-requesting signal to the server for immediate acknowledgement of the hazardous condition on the side of the server.

Further, it is preferred that the first communication network and the second communication networks are arranged to have individual communication protocols different from each other. Thus, the subsystem can be easily adapted to the integrated service network, while avoiding possible interference between thβ two networks.

These and still other advantageous features of the present invention will become more apparent from the following detailed description when taken in conjunction with the attached drawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic view of a home security surveillance system which employs a hazard detection subsystem in accordance with the present invention;

FIG. 2 is a schematic view illustrating terminal registration tables and a terminal status table respectively prepared in detection terminals and a gateway unit constituting the above subsystem, in addition to a terminal enrollment table of a server;

FIG. 3 is a block diagram of the server;

FIG. 4 is a block diagram of the detection terminal;

FIG. 5 is a block diagram of the gateway unit;

FIG. 6 is a timing chart illustrating how the detection terminals are assigned as a master and a slave;

FIG. 7 is a timing chart illustrating how the subsystem is reconfigured in case when one of the slave is removed from the subsystem;

FIG. 8 is a timing chart illustrating how the subsystem is reconfigured in case when the master is removed from the subsystem;

FIG. 9 is a timing chart illustrating how the subsystem is reconfigured in case one of the slaves is replaced with a new detection terminal;

FIG. 10 is a timing chart illustrating how the subsystem is reconfigured in case the master is replaced with a new detection terminal; and FIG. 11 is a timing chart illustrating an operation sequence upon detection of hazardous condition at one of the detection terminals.

BEST MODE FOR CARRYING OUT THE INVENTION

Now referring to FIG. 1 , there is shown a home security surveillance system which employs a hazard detection subsystem in accordance with the present invention. The home security surveillance system is provided by a service provider and includes a computer-based server 30 installed on the side of a service provider for collecting hazard information such as fire occurrence from an in-house alarm network in each of customers' homes and providing an assistance, for instance, dispatching qualified personnel to the customers home and/or informing an urgent prompt to a customer out of ones' home. The in-house network is realized by the subsystem which is developed in each of the customers' homes and includes a plurality of detecting terminals 50 such as smoke detectors, and a gateway unit 10 which acts as an interface between the detecting terminals and the server 30. The server 30 is equipped or linked with an alert device 38 which generates an alert report when receiving the hazard information in the form of an aid-requesting signal from any one of the detection terminals 50 through the gateway unit 10. As will be discussed later in details, each of the detection terminals is configured to communicate with each other through a first communication network, and also communicate with the gateway unit 10 through a second communication network.

The system further includes an input device 100, for instance, a personal computer or the like which belongs to each customer and is configured to communicate with the server 30 through a public computer network, e.g., the Internet for enrolling the detection terminals 50 in the server 30. For this purpose, the server 30 is provided with a terminal enrollment table 37, which is configured, as shown in FIG. 2, to store a record of terminal code, for instance, manufacture's serial number entered by the customer by use of the input device 100. No other entry is required on the side of the customer. The customer is only required to insert the record of the terminal code or delete such record in advance of developing the in-house alarm network of the subsystem.

As shown in FIG. 3, the server 30 includes, in addition to a memory constituting the terminal enrollment table 37, a communication module 32 for communication with the input device 100 as well as the gateway unit 10 through the public network, and a processor constituting an enrolling module 34 and a hazard event module 36. The enrolling module 34 is programmed to insert, delete, and update the enrollment record in the terminal enrollment table 37 in response to the customer's input at the input device 100. The hazard event module 36 is programmed to activate an alert device 38 for providing the alert report in response to the aid-requesting signal transmitted by way of the gateway unit 10 and received at the communication module 32. The alert device 38 may be a display, a speaker, or the like providing information to the personnel of the service provide.

The detection terminals 50 employed in the present invention are of the same configuration which enables each of the detection terminal to function selectively as a master and a slave. The detection terminal 50 is powered by an incoφorated battery (not shown), and includes, as shown in FIG. 4, a power switch 52, a smoke sensor 56, an alarm unit 58, a radio transceiver 68, a processor, and a memory. The smoke sensor 56 is designed to detect a smoke density in an atmosphere and output a density signal indicative of the detected smoke density to a hazard event module 64 realized in the processor. When the smoke density exceeds a predetermined threshold, the hazard even module 64 generate a hazard signal indicative of possible fire and output the signal to the alarm unit 58, which responds to give an alarm sound. The hazard signal is transmitted by means of the radio transceiver 68 to the other detection terminals 50 forming the in-house alarm network through the first communication network, and is also transmitted as the aid-requesting signal to the gateway unit 10 through the second communication network. To this end, the hazard event module 64 is configured to generate the hazard signal in compliance with a first communication protocol specific to the first communication network, and the aid-requesting signal in compliance with a second communication protocol, which is different from the first communication protocol, specific to the second communication network.

The master is defined to provide a linking hazard signal when receiving the hazard signal from any one of the other detection terminals, while the slave is defined to transmit the hazard signal to the master through the first communication network, and to give the alarm upon receiving the linking hazard signal from the master. The linking hazard signal is prepared in accordance with the first communication protocol and is transmitted from the master to all of the slaves forming the in-house alarm network for providing the alarm at every detection terminals simultaneously. The master is also configured to generate and transmit the aid-requesting signal to the gateway unit 10 when receiving the hazard signal from any one of the slaves or when generating the hazard signal by its own. In this sense, the master acts as a repeater to transmit the aid-requesting signal to the gateway unit in parallel with the aid requesting signal transmitted from the slave directly to the gateway unit 10. In addition, the slave is configured to transmit the hazard signal also to the other slave or slaves, when detecting the hazard configuration or fire occurrence. In order to make interrelated operations between the master and the slaves, the detection terminal has a terminal registration table 67 which is realized in the memory to store, as shown in FIG. 2, a record of a master/slave index indicative of the master or slave, and a node number discriminating each one of the detection terminals from the other within the in-house alarm network. Further, the record of the terminal registration table 67 includes the terminal code. When the detection terminal is assigned as the master, as will be discussed later, it is made to store the master/slave index and the node numbers for all of the detection terminals. When, on the other hand, the detection terminal is assigned as the slave, it is made to store the master/slave index and the node number of itself and the master.

The processor also realizes a configuration/registration module 62 which is programmed to interact with the gateway unit 10 to complete a terminal configuration of assigning the maser and slave, and a terminal registration of determining the node number in association with the master/slave index.

As shown in FIG. 5, the gate unit 10 includes a radio transceiver 11 for communication with the server 30 as well as with the detection terminals 50 through the second communication network, which is distinguished from the first communication network of interconnecting the detection terminals 50 due to the use of a specific communication protocol different from that of the first communication network. The gateway unit 10 also includes a memory constituting a terminal status table 17 which has a configuration identical to the terminal enrollment table 37 and is updated to reflect a change in the enrollment record of the terminal enrollment table 37. Further, the gateway unit 10 has a processor constituting a hazard event module 12, an authentication module 14, and an assigning module 16. The hazard event module 12 is programmed to relay the aid-requesting signal to the server 30, in response to receiving it from any one of the detection terminals 50. The authentication module 14 is programmed to authenticate the detection module, i.e., check whether or not the detection terminal 50 making a configuration demand is recorded in the terminal status table 17, and permits the entry of such detection terminal 50 into the in-house alarm network when it is so recorded in the terminal status table 17. The assigning module 16 is programmed to assign the master to one of the authenticated detection terminals 50 and the slave to the other authenticated detection terminals 50. The result of such assignment is recorded in the terminal status table 17, as well as in the terminal registration table 67 of each detection terminals.

Now referring to FIG. 6, the terminal configuration and the terminal registration are explained in details. After the customer enters the terminal code for each of the detection terminals 50 to be installed in one's home in the terminaJ enrollment table 37 of the server, the gateway unit 10 responds to record the terminal code in the terminal status table 17 when communicating first with the server. Thus, the gateway unit 10 becomes ready for making the terminal configuration. When one of the first detection terminals is energized with its power switch turned on, it transmits to the gateway unit 10 the configuration demand including the terminal code. When the gateway unit authenticates the detβction terminal transmitting the configuration demand as being recorded in the terminal status table 17, the gateway unit 10, i.e., the assigning module 16 acknowledges that the detection terminal is the first one that establishes the communication with the gateway unit 10, and returns a configuration request to the detection terminal, requesting the detection terminal to transmit a configuration response of a specific encryption key to the gateway unit 10. When the gateway unit 10 verifies the configuration response as valid, it transmits a configuration instruction a configuration instruction to the detection terminal in order to assign the master thereto, and at the same time, updates the record of the terminal status table 17 with respect to the detection terminal by setting the master/slave index of "1" and the node number of "00", both indicating the master. The configuration request and the configuration response are provided only for exchanging the encryption key between the detection terminal and the gateway unit for an encrypted communication, and may be optional. That is, the gateway unit 10 may be configured to transmit the configuration instruction in direct response to the configuration demand from the detection terminal of which terminal code is authenticated.

Upon receiving the configuration instruction at the detection terminal 50, the configuration/registration module 62 responds to write the master/slave index of ^M1 " and the node number of "00* in association with the terminal code of its own in the terminal registration table 67. Thus, the detection terminal 50 (hereinafter also referred to as " DT-master") becomes ready for registration of the other detection terminals (hereinafter also referred to as ^MDT-slave^B) which constitute the in-house alarm network with the DT-master.

Subsequently, when one of the other detection terminals 50 (DT-slave) is energized by manipulation of the power switch 52, the detection terminal 50 (DT-slave) goes into a stage 1 sequence ( i.e., a slave configuration sequence) of transmitting the configuration demand with its terminal code, and optionally receiving the configuration request from the gateway unit 10, and transmitting back the configuration response to the gateway unit 10. When the terminal code is recorded in the terminal status table 17, the gateway unit 10 assigns the slave to the detection terminal 50 (DT-slave) by transmitting to the DT-slave the configuration instruction by which the configuration/registration module 62 of the DT-slave responds to write the master/slave index of "0" as associated with its own terminal code in the terminal registration table 67. When sending the configuration instruction to the DT-slave which establishes the communication with the gateway unit 10 later than the preceding one of the detection terminals, i.e., the DT-master, the gateway unit 10 includes a registration instruction in the configuration instruction. That is, the assigning module 16 generates the registration instruction to be added with the configuration instruction. When receiving such configuration instruction, the DT-slave goes into a stage 2 sequence (i.e., a slave registration sequence) starting from waking up the DT-master by sending a registration demand to the DT-master.

Upon receiving the registration demand, the DT-master responds to return a demand acknowledgement to the DT-slave, and a registration inquiry to the gateway unit 10. Subsequently, the gateway unit 10 returns a slave registration permission which is prepared by the assigning module 16 to include the node number of "01 " to be given to the DT-slave. Then, the DT-master responds to transmit a registration order to the DT-slave with the node number of "01" indicative of that the DT-terminal is the first slave recognized by the DT-master, in addition to the master/slave index, and the node number of about the DT-master so that the configuration/registration module 62 of the DT-slave updates the record of its own to have the node number of "OT, and adds the record of the DT-master in the terminal registration table 67, as shown in FIG. 2. After completion of updating the terminal registration table 67, the DT-slave returns a registration response to the DT-master which responds to add the record of the DT-slave in its terminal registration table 67. Upon receiving the registration response from the DT-slave, the DT-master sends a slave registration request to the gateway unit 10 so that the gateway unit updates the record of the DT-master and the newly added DT-slave in the terminal status table 17 with regard to the master/slave index and the node number in relation to the terminal code. After updating the terminal status table 17, the gateway unit 10 issues a registration completion response to the DT-slave, completing the slave registration sequence, i.e., the stage 2 sequence.

If the registration completion response is not received within 2500 ms from the configuration demand, the above slave configuration sequence followed by the slave registration sequence is repeated. With the completion of the above registration for aJI of the other DT-terminals, the DT-master acknowledges each of the DT-slaves and the vice versa as constituting the in-house alarm network such that the each DT-slave can transmit the hazard signal to the DT-master and the other DT-slave through the first communication network, i.e., the in-house alarm network, and the DT-master can transmit the aid-requesting signal to the gateway unit 10 through the second communication network upon receiving the hazard signal from any one of the DT-slaves, in addition to that each of the DT-slave can transmit the aid-requesting signal directly to the gateway unit 10 through the second communication network.

Referring to FIG. 7, there is shown a time chart illustrating how the system works when one of the DT-slaves is removed from the system. When the DT-slave, for instance, one having the node number of "01" becomes defective and is powered off, the customer utilizes the input device 100 to delete the record of the defective DT-slave from the terminal enrollment table 37 in the server 30. The change of the record is reflected in the terminal status table 17 of the gateway unit 100 when it communicates with the server 30. That is, the terminal status table 17 is updated to give a delete ftag to the record of the defective DT-slave, indicating that such recorded is to be deleted. In this situation, the DT-master functions to make a status check sequence whether or not the registered DT-slaves are currently available in the system. The status check sequence is initiated by manipulation of a set button 54 on the side of the DT-master. Upon manipulation of the set button 54, the configuration/registration module 62 responds to generate a status check request for all of the existing or registered DT-slaves, interrogating whether or not each of the DT-slaves registered in the terminal registration table 67 is recorded as a valid one in the terminal status table 17 of the gateway unit 10. When returning a status request acknowledgement to the DT-master, the gateway unit 10 provides a slave remove instruction for deleting the defective DT-slave from the terminal registration table 67, i.e., the record of the defective DT-slave which is marked with the delete flag in the terminals status table. In response to the slave remove instruction, the DT-master deletes such record from its terminal registration table 67, and returns a slave remove confirmation to the gateway unit, such that the gateway unit updates its terminal status table 17 by actually deleting the record with the delete flag. When the other non-defective DT-slave, for example, having the node number of "02" has its set button 54 pressed, the DT-slave transmits a like status check request whether or not the DT-slave "02" is recorded in the terminal status table 17 of the gateway unit and receives therefrom the status request acknowledgement, which necessitates no change in the terminal registration table 67 of the DT-slave "02".

It is noted in this connection that the status check sequence is initiated by pressing the set button 54 for a short period, for example, less than 4 seconds. When, on the other hand, the set button 54 is pressed for a long period more than 4 seconds, the DT-master or DT-slave makes the above status check followed by a manual test routine which generates a pseudo hazard signal for checking whether the in-house alarm system reacts to issue the alarm from the individual detection terminal. In this case, after sending the status check request and receiving the status request acknowledgement, the DT-master or the DT-slave issues a test request to the gateway unit which responds to return a test request acknowledgement. Upon receiving the test request acknowledgement, the DT-master or the DT-slave is allowed to enter a manual test mode of giving the pseudo hazard signal to generate the alarm within the in-house alarm network, while the gateway unit can acknowledge that the resulting alarm is false one and simply as a result of the test.

In addition, as will be discussed later with reference to FIG. 11, the set button, when long-pressed, issues a stop alarm signal provided that that there is the hazardous condition detected in the in-house alarm network.

Further, it is also noted in this connection that the each of the DT-master and the DT-slaves is activated intermittently or comes into an intermittent operation mode of checking whether or not the hazardous condition is detected, and wakes-up to transmit the hazard signal as well as the aid-requesting signal immediately upon detection of the hazardous condition. In the figures, such intermittent operation mode of the terminal is denoted by the term "intermittent operation". Also, each of the DT-master and the DT-slave is configured to issue the status check request to the gateway unit at regular intervals for checking whether or not the second communication network operates successfully.

FIG. 8 illustrates a time chart how the system works when the DT-master is removed. As a result of that the DT-master becomes defective and is removed from the system, the customer is required to delete the record of the defective DT-master from the terminal enrollment table 37 in the server 30 such that the gateway unit 10 updates its terminal status table 17 to reflect the deletion. In this situation, when one of the DT-slaves, in this instance, DT-slave having the node number of "01 " has its set button 54 pressed for the short period, this DT-slave makes the status check sequence by transmitting the status check request to the gateway unit 10. However, the gateway unit 10 fails to successfully return the status request acknowledgement to the DT-slave, because of that the gateway unit acknowledges no DT-master in its terminal status table 17. After repeating to transmit the status check request for a predetermined number within a predetermined period after the short-pressing of the set button 54, the DT-slave is allowed to make the configuration sequence to the gateway unit 10. Upon receiving the configuration demand from the DT-slave, the gateway unit 10 makes a reconfiguration routine for reestablishing the in-house alarm network. The reconfiguration routine continues by the gateway unit 10 returning the configuration instruction by which the receiving DT-slave is assigned as a new master and rewrites its terminal registration table 67 to have the master/slave index of "1 ". That is, upon receiving the configuration demand, as explained with reference to FIG. 6, from the detection terminal establishing the communication with the gateway unit, the gateway unit refers to its terminal status table and permits the assigning module 16 to assign the master to the detection terminal transmitting the configuration demand, only when the terminal status table shows a record of the detection terminal transmitting the configuration demand, and shows no record of any detection terminal already assigned as the master.

At this time, the gateway unit 10 updates the terminal status table 17 to rewrite the master/slave index of the new DT-master. Thereafter, the DT-master transmits the status check request to the gateway unit 10 which returns the status request acknowledgement to the DT-master. Whereby, the DT-master responds to clear the records of the remaining DT-slaves with regard to the node number, and the gateway unit 10 clears the records of the remaining DT-slaves with regard to the node number. Then, the gateway unit 10 becomes ready for completing the reconfiguration routine in combination with the DT-master. That is, upon receiving the configuration demand from each of the remaining DT-slaves, in this instance, DT-slave having the node number of "02°, the gateway unit 10 generates the configuration instruction designating a new node number of "01 " and the master/slave index of "0", and transmits the same to the DT-slave, which responds to update its own terminal registration table 67 correspondingly, thereby completing the stage 1 sequence (slave configuration sequence). At this time, the gateway unit 10 has its terminal status table 17 updated to reflect the change made to the DT-slave. The configuration instruction generated in the gateway unit 10 includes the registration instruction by which the DT-slave comes into the stage 2 sequence (i.e., the slave registration sequence), which starts from waking up the new DT-master by sensing the registration demand and complete by receiving the registration completion response from the gateway unit 10, as explained in details with reference to FIG. 6. Similarly, any of the remaining DT-slaves completes the above reconfiguration routine simply by pressing the set button 54 for the short time period. Upon completion of the reconfiguration of the all the existing DT-slaves, the new DT-master has its terminal registration table 67 updated to acknowledge the DT-slaves by their node numbers for communication within the in-house alarm network, in addition to that the DT-master as well as the DT-slaves can communicate with the gateway unit 10 with the use of individual node numbers.

Referring to FIG. 9, there is shown another time chart illustrating how the system works when replacing the DT-slave with a new one. As a result of that one registered DT-slave (one having the node number "01 ^u, in this instance) becomes defective and has to be replaced with the new detection terminal, the customer uses the input device 100 to remove the record of the defective DT-slave from the terminal enrollment table 37 in the server 30 and insert a record of the newly added detection terminal in the terminal enrollment table 37. The change of the record is reflected in the terminal status table 17 of the gateway unit 100 when it communicates with the server 30. In this situation, upon being energized to communicate with the gateway unit 10, the new DT-slave interacts with the gateway unit 10 to complete the stage 1 sequence and the stage 2 sequence as explained herein above so as to be given the master/slave index of "0" and a new node number, whereby the new DT-slave is recognized by the gateway unit 10 and also by the DT-master for successful communication therebetween. Subsequently, in response to the short-pressing of the set button 54, the DT-master makes the status check sequence whether or not the DT-slaves recorded in its terminal registration table are currently available in the system. That is, the DT-master generates and transmits the status check request to the gateway unit 10, interrogating whether or not each of the DT-slaves recorded in the terminal registration table 67 is also recorded as valid one in the terminal status table 17 of the gateway unit 10. When returning a status request acknowledgement to the DT-master, the gateway unit 10 provides the slave remove instruction for deleting from the terminal registration table 67 the record of the terminal which is marked with the delete flag in the terminal status table 17. In response to the slave remove instruction, the DT-master deletes such record from its terminal registration table 67, and returns the slave remove confirmation to the gateway unit for completely deleting such record also from the terminal status table. Thereafter, when the DT-slave has its set button short-pressed, it transmits the status check request to the gateway unit 10 which returns the status request acknowledgement indicative of that no change is necessary for the terminal registration table 67 of the requesting DT-slave.

When the DT-master becomes defective and is replaced with a new one, the system operates as shown in FIG. 10. In this situation, the user updates the terminal enrollment table 37 of the server 30 by deleting the record of the defective DT-master and inserting the terminal code of a new detection terminal. The resulting change is reflected in the terminal status table 17 of the gateway unit 10. In response to the new detection terminal being energized to establish the communication with the gateway unit 10 by sending the configuration demand, the gateway unit 10 checks whether or not there is the record of the detection terminal assigned as the master in the terminal status table 17, and complete the stage 1 sequence by sending the configuration instruction, which assigns the master to the new detection terminal when the terminal status table shows no record of the detection terminal assigned as the master. Thus, the newly added detection terminal is acknowledged as the new DT-master. Thereafter, the new DT master transmits the status check request to the gateway unit 10 and receives therefrom the status request acknowledgement for confirmation of that the DT-master is recorded in the terminal status table. At this time, the DT-master does not acknowledge the associated DT-slaves, since no record of the DT-slaves are entered in its terminal registration table 67. Also, the gateway unit 10 clears the node number of each DT-slave from its terminal status table, such that it fails to return the status acknowledgement to each DT-slave, even when each DT-slave has its set button short-pressed in an attempt to interact with the gateway unit.

Subsequently, upon short-pressing of the set button, the DT-master sends the status check request, requesting the gateway unit 10 to accept the configuration demand followed by the status check request from each DT-slave. After that, the DT-slave is allowed to make the configuration sequence to the gateway unit and receives the configuration instruction to complete the stage 1 sequence and the stage 2 sequence in a manner as described in the above, whereby the DT-slave is redefined as the slave with the node number given from the gateway unit, and is recorded in the terminal registration table of the DT-master. In this manner, all of the existing DT-slaves are redefined and acknowledged by the DT-master and the gateway unit.

FIG. 11 illustrates how the system works upon detection of the hazardous condition at one of the DT-slaves. In this instance, DT-slave having the node number of "01 ' (herein after referred to as detecting DT-slave) detects the hazardous condition and is caused to wake-up to issue the alarm and to transmit the aid-requesting signal to the gateway unit 10. Then, the gateway unit responds to relay the aid-requesting signal to the server 30 to notify the hazardous condition, and return an aid-request acknowledgement to the detecting DT-slave. Immediately subsequently, the detecting DT-slave transmits the hazard signal, waking up the DT-master as well as the other DT-slave (hereinafter referred to as non-detecting DT-slave). In response to the hazard signal, the non-detecting DT-slave issues the alarm, while the DT-master generates and transmits the linking hazard signal to the detecting and non-detecting DT-slaves such that each DT-slave issues the alarm. If the non-detecting DT-slave should have failed to wake-up due to some temporary communication error, it is caused to wake-up by the interconnecting hazard signal and issue the alarm. The detective DT-slave and the non-detective DT-slave, when waking-up, return a linking alarm response back to the DT-master, which in turn comes into an interlocked mode of transmitting the aid-requesting signal repeatedly to the gateway unit, and at the same time transmitting the linking hazard signal repeatedly to the detective and non-detective DT-slaves.

Upon the set button being pressed in this situation where the linking hazard signal is repeatedly transmitted, the DT-master transmits an alarm stop order to the detecting and non-detecting DT-slaves, and at the same time transmits an alarm status signal to the gateway unit, indicating that the DT-master is requesting the DT-slaves to stop the alarm. The alarm stop order and the alarm status signal are transmitted repeatedly within a predetermined time period of 90 seconds, for example. After the elapse of the time period, the DT-master transmits an alarm stop confirmation, requesting the detective and non-detective DT-slaves to return an alarm stop response indicative of that the alarm stop order is accepted at the DT-slave. However, while the detecting DT-slave is still detecting the hazardous condition, the detecting DT-slave returns the alarm stop response indicative of the hazardous condition such that the DT-master responds to continue transmitting the linking hazard signal until the hazardous condition is cleared, and continues transmitting to the gateway unit the aid-request signal including information that the hazardous condition is still being detected at the detecting DT-slave after the DT-master transmits the alarm stop order.

When the hazardous condition is cleared, the detecting DT-slave transmits a stop alarm demand to the DT-master, while stopping its own alarm. Then, the DT-master responds to transmit a stop alarm confirmation order to all the DT-slaves, requesting them to return a stop alarm response including information whether or not the DT-slave is ready for stopping the alarm. Upon acknowledgement of the stop alarm response, the DT-master transmits a stop alarm order to the DT-slaves for stopping the alarm at the individual DT-slaves. When the alarm is stopped, each DT-slave returns the stop alarm response indicative of the alarm status to the DT-master, and comes into the intermittent reception mode. Likewise, the DT-master comes into the intermittent reception mode upon receiving the stop alarm response from the DT-slaves. Further, after receiving the stop alarm demand and until receiving the stop alarm response, the DT-master functions to transmit the alarm status signal to the gateway unit with information that the DT-master receives the stop alarm demand from the detecting DT-slave.

It is noted that the detection terminal is designed to issue the alarm as a sound-voice "whiz whiz warning smoke alarm" when the hazardous condition is detected by its own, and to issue the alarm as a sound-voice "whiz whiz warning smoke in another room " when the hazardous condition is detected by the other detection terminal.

While the detection terminal is in the intermittent operation mode, it transmits the status check request at regular intervals of 33 hours, for instance, to the gateway unit with information about a battery condition or some parameters indicative whether or not the detection terminal is in good order.

Although the present invention has been described with reference to the illustrated embodiment, the individual features as described in the above may be suitably combined to constitute an improved invention or inventions other than the claimed invention.

Claims

CLAIMS:

1. A hazard detection subsystem for use in a home security surveillance system, said security surveillance system including: a computer-based server (30) having a terminal enrollment table (37) arranged to store an enrollment record relating to a plurality of detection terminals (50) installed in a customer's home, said server having a processor configured to receive an aid-requesting signal originating from at least one of said detection terminals, said server including an alert means configured to provide an alert report in response to receiving said aid-requesting signal; and an input device (100) adapted to communicate with said server through a public computer network in order to enter and update said enrollment record in said server, said subsystem comprising: said plurality of detection terminals (50) configured to detect a hazardous condition in a customer's home and generate a hazard signal, each of said detection terminals including a radio transceiver (68) for transmitting said hazard signal to the other detection terminal through a first communication network, a gateway unit (10) being adapted in use to be installed in the customer's home, and including a communication means (11) which is configured to communicate with said server through said public computer network, said communication means being configured to establish a radio communication with said detection terminals through a second communication network, wherein each of said detection terminals includes an alarm unit (58) which provides an alarm upon such detection terminal generating said hazard signal or receiving a linking hazard signal from one of the other detection terminals, each of said detection terminals being configured to function selectively as a mater and a slave, said master being defined to provide said linking hazard signal when receiving said hazard signal from any one of the other detection terminals, and said slave being defined to transmit said hazard signal to said master through said first communication network, each of said detection terminals being configured to generate and transmit said aid-requesting signal to said gateway unit through said second communication network upon generating said hazard signal; said gateway unit being configured to relay said aid-requesting signal to said server upon receiving said aid-requesting signal, said gateway unit including an assigning means (16) arranged to assign said master to one of said detection terminals that is energized to first establish communication with said gateway unit, and assign said slave to the other detection terminal that is energized to later establish communication with said gateway unit

2. A hazard detection subsystem as set forth in claim 1 , wherein said gateway unit includes a terminal status table (17) storing a master/slave index indicative of whether each of said detection terminals is assigned as said master or slave, in addition to said terminal code for each of said detection terminals, said gateway unit is programmed to refer to said terminal status table in response to a configuration demand transmitted from said detection terminal establishing communication with said gateway unit, and permit said assigning means to assign said master to the detection terminal transmitting said configuration demand only when said terminal status table has a record of the detection terminal transmitting said configuration demand, and has no record of any detection terminal already assigned as said master

3. A hazard detection subsystem as set forth in claim 1 , wherein each of said detection terminals (50) includes a terminal registration table (67) configured to register said terminal code, a master/slave index indicative of said master or said slave, and a node number which discriminates each one of said detection terminals from the other, each of said detection terminals is arranged to send to said gateway unit a configuration demand accompanied with its own terminal code, when it is energized first to communicate with said gateway unit, said gateway unit is programmed to check whether the detection terminal sending said configuration demand is registered in said terminal status table, and permits said assigning means to send a configuration instruction of assigning said master or slave to said detection terminal when such detection terminal is recorded in said terminal status table, and said assigning means being arranged to send a registration instruction to said detection terminal when said terminal status table shows a record of such detection terminal to be assigned as said slave or when said terminal status tables shows a change of said master, each of said detection terminals being programmed to make, in respond to said registration instruction, a terminal registration which executes steps of: requesting said master to receive a permission from said gateway unit that said terminal status table has a record of the terminal code corresponding to said requesting detection terminal;

- requesting said master, upon reception of said permission, to allocate said node number to said requesting detection terminal and to send thus allocated node number to said gateway unit; requesting said master to enter thus allocated node number in associate with the terminal code and said master/slave index of the requesting detection terminal in said terminal registration table of said master; and storing thus obtained node number in association with said terminal code and said master/slave index of the requesting detection terminal, in addition to the terminal code and a predetermined node number of said master, in said terminal registration table of the requesting detection terminal.

4. A hazard detection subsystem as set forth in claim 3, wherein said detection terminal being configured to register in its terminal registration table (67), when assigned as said master, said terminal code, said master/slave index and said node number for all of said detection terminals, said detection terminal is configured to register in its own said terminal registration table, when assigned as said slave, said terminal code, said master/slave index, and said node number of its own, in addition to said terminal code, said master/slave index, and said node number of said master, each of said detection terminals being provided with a configuration means (62) and a set button (54) which, upon being manipulated, activates said configuration means to send a configuration demand to said gateway unit and receive therefrom the configuration instruction by which said detection terminal is assigned as said master or said slave, said gateway unit being configured to check whether a condition is satisfied in which said terminal status table shows no record of the detection terminal assigned as said master and shows a record of at least one remaining detection terminal, and to execute, when such condition is satisfied, a reconfiguration routine in response to receiving said configuration demand from any one of the remaining detection terminal of which record is read from said terminal status table, said reconfiguration routine comprising the steps of. a) deleting said master/slave index and said node number for all the remaining detection terminals from said terminal status table; b) assigning said master to one of said remaining detection terminals which comes into communication with said gateway unit first after having its set button manipulated, and sending said configuration instruction and said registration instruction to the other of said remaining detection terminals in response to said detection terminal being activated by manipulation of said set button.

5. A hazard detection subsystem as set forth in claim 1 , wherein said slave is programmed to transmit said hazard signal as said aid-requesting signal first to said gateway unit upon generating said hazard signal, and then transmit said hazard signal to said master, and said gateway unit is programmed to transmit said aid-requesting signal to said sever upon receiving said aid-requesting signal from anyone of said master and slave.

6. A hazard detection subsystem as set forth in claim 1 , wherein said first communication network and said second communication networks are arranged to have individual communication protocols different from each other.