USPatent applicationPatented

Method and system for authenticating a security device

Granted 9 Oct 2007 · no office action yet

Current assignee: Resideo Technologies, Inc. · originally Honeywell International

Law firm: Law firm · Log in to unlock

Attorney: Attorney · Log in to unlock

Inventors: Thomas Schmit · Examiner: Thomas R. Peeso · AU 2132 · TC 2100

Life of the application

10 dated events
⤢ drag to zoom200420062008201020122014201620182020202220242026ProsecutionOwnershipTerm & fees
ProsecutionOwnershipTerm & feeshover for detail · click to open

Abstract

A method of authenticating a security device to determine if it is authorized to be used with a security system. First and second encryption keys are stored in the control panel and the security device. A challenge message is produced by encrypting, with the first key, a challenge index (such as a random number generated by the control panel). The challenge message is transmitted the security device, where the encrypted challenge index is extracted from the challenge message and then decrypted using the first key at the security device to produce a response index. A response message is produced by encrypting, with the second key, the response index decrypted by the security device. The response message is transmitted to the control panel, and the encrypted response index is extracted and then decrypted using the second key at the control panel to produce the response index. The control panel then compares the response index with the challenge index previously generated. If they are the same, then the control panel indicates that the security device is authentic and allows further communications between the control panel and the security device. If they are not the same, then the control panel indicates that the security device is not authentic and disallows further communications between the control panel and the security device.

Description

6 parts
›FIELD OF THE INVENTION

This invention relates to security and other types of networked systems, and in particular to a method and system for authenticating a security device to determine if it is authorized to be used with the security system.

›BACKGROUND OF THE INVENTION

Security systems used to monitor premises and determine if the premises has been breached or an alarm condition exists are well known in the art. These systems typically include a control panel, a systems communications medium such as a data bus, and a number of security devices located throughout the premises for performing a certain function in the system. Security devices typically include glass break sensors, smoke detectors, fire detectors, motion sensors, door and window opening sensors, etc. Security devices also include peripherals such as dialers, keypads, display consoles, RF transmitters and receivers, etc. The control panel is typically configured to communicate with the security devices to collect and send information with these devices, such as when a user enters a “system arm” code in the keypad in order to arm the control panel and the security system.

Due to increasing complexities in security device design and the interaction with the control panel, it has become necessary to use such devices that can operate properly and robustly under the conditions imposed by the system. In some cases, communications between a control panel and the security devices may be encrypted or otherwise secured to ensure that only authorized devices are used in the system. That is, if a security device that is not designed to comport with the rigorous standards of the system is attempted to be used with this type of system, it will likely not operate properly since it has not been programmed with the appropriate encryption methodologies. This is one methodology utilized to ensure that only authorized security devices are used in the system.

It is sometime desired, however, to implement a security system with a communications protocol that is not per se secure, i.e. one that is not encrypted and is sent in the clear. In the situations, it is desired to provide a method of authenticating a security device, both during installation as well as during operation of the system, to ensure that the device has been designed and programmed to operate specifically with the system. It is also desired to prevent someone from substituting a bogus or malicious device into a security system in an attempt to circumvent the security of the system (e.g. gain unauthorized entry). It is desired, therefore, to be able to determine if such a security device is unauthorized and therefore should not be allowed to operate with the system.

›SUMMARY OF THE INVENTION

Accordingly, the present invention is a method of authenticating a security device to determine if it is authorized to be used with the security system. The security system has a control panel and a plurality of security devices interconnected to the control panel over a communications medium located in a premises. A first encryption key and a second encryption key are stored in the control panel and in the security device. A challenge index, such as a random number, is generated at the control panel, and a challenge message is produced by encrypting the challenge index using the first encryption key and including the encrypted challenge index in the challenge message. The challenge message is then transmitted over the communications medium to and received by the security device.

At the security device, the encrypted challenge index is extracted from the challenge message and then decrypted using the first encryption key at the security device to produce a response index. A response message is then produced by encrypting the response index using the second encryption key at the security device and including the encrypted response index in the response message. The response message is transmitted over the communications medium by the security device to and received by the control panel.

The encrypted response index is extracted by the control panel from the response message, and then decrypted using the second encryption key at the control panel to produce the response index. The control panel then compares the response index with the challenge index previously generated. If the response index decrypted by the control panel is the same as the challenge index previously generated by the control panel, then the control panel indicates that the security device is authentic (i.e. it has the same encryption keys and encryption/decryption algorithms in its memory as does the control panel) and allows further communications between the control panel and the security device. If, however, the response index decrypted by the control panel is not the same as the challenge index previously generated by the control panel, then the control panel indicates that the security device is not authentic and disallows further communications between the control panel and the security device.

›BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a block diagram of a typical security system;

FIG. 2 is a flowchart of the operation of this invention;

FIG. 3 is a detailed block diagram of the control panel functionality under this invention; and

FIG. 4 is a detailed block diagram of the security device functionality under this invention.

›DETAILED DESCRIPTION OF THE INVENTION · 1 of 2

The preferred embodiment of the present invention is now described with reference to the Figures. FIG. 1 illustrates a typical security system that includes a control panel 2 , a number of security devices 4 , and a communications medium (bus) 6 that allows communication between and amongst the security devices and the control panel as known in the art. The communication medium 6 may be a wired bus or loop, a wireless (e.g. RF) system, or a combination of any type of wired and wireless technologies as well known in the art. As previously indicated, the security devices may be any device that is used in a security system, including but not limited to glass break sensors, smoke detectors, fire detectors, PIR motion sensors, microwave motion sensors, door and window opening sensors, dialers, keypads, display consoles, RF transmitters and receivers, and the like. The security device may also be a gateway, adapter or interface between the control panel and another device. For example, it is common to have an RF receiver connected to a wired communications bus (or loop) to which the control panel is connected. The RF receiver receives messages from another security device such as a wireless PIR sensor (there may also be an RF transmitter for sending messages to the wireless PIR sensor). In this case, both the RF receiver (and/or RF transmitter) as well as the wireless sensors are considered to be security devices in the scope of this invention.

The control panel 2 acts as the system controller for the security system and provides for various functions such as arming and disarming the system, supervising security devices, accepting messages from the security devices to determine if an alarm condition exists, causing an alarm to sound, etc.

Security device authentication will now be described with respect to FIGS. 2 , 3 and 4 . The authentication process, which may be initiated at installation, will first cause a challenge index to be generated or retrieved from memory. In the preferred embodiment, a challenge random number R 1 is generated by random number generator 8 at the control panel 2 . Alternatively, the index may be generated in a predetermined manner (such as by an incrementing or decrementing counter). Also, an index may be stored in memory and used for each authentication attempt. The random number is preferred, however, since it is harder to emulate and reproduce in the event that transmissions are captured by an eavesdropper.

Random number R 1 is then encrypted by an encryption algorithm 14 , using encryption key K 1 12 as shown in FIG. 3 . Encryption is well known in the art and will modify the random number as a function of the algorithm used as well as the key K 1 . The encrypted R 1 is the used to produce a challenge message 16 , which will be sent via data transmitter 18 to the security device 4 that is being authenticated by the control panel 2 .

The security device 4 receives the challenge message via data receiver 36 , and decrypts the challenge message with a decryption algorithm 40 and encryption key K 1 42 . Assuming that K 1 42 is the same as K 1 12 , then the index (random number) R 2 will be the same as the index (random number) R 1 generated by the control panel. Index (random number) R 2 is then encrypted using encryption algorithm 48 (which may or may not be the same as encryption algorithm 14 in the control panel) and encryption key K 2 46 to produce a response message 50 . The response message 50 is transmitted by data transmitter 52 back to the control panel 2 .

The control panel receives the response message via its data receiver 20 , and then decrypts it using decryption algorithm 24 and encryption key K 2 28 to generate R 2 26 . Assuming that K 2 28 is the same as K 2 46 , then R 2 26 will be the same as R 2 44 , which will be the same as R 1 if K 1 12 and K 1 42 are the same. R 2 26 will then be compared by the comparator 30 to determine if there is a match between R 1 10 and R 2 26 . If there is a match, then the security device is deemed to be authentic; if there is no match, then the security device is deemed to be not authentic.

That is, a device that is authentic will have the same encryption keys K 1 , K 2 as the control panel (and the same encryption and decryption algorithms), since they will have been made by the same manufacturer (or authorized and licensed by that manufacturer). As such, the index passed through the system as described above will be the same, after being encrypted and decrypted twice, resulting in a positive comparison. If any of the encryption keys do not match—such as when an unauthorized security device is installed or substituted in the system, then at least one (and likely both) keys K 1 , K 2 will not match with the control panel and the index R 2 decrypted at the security device and/or the index R 2 decrypted at the control panel will not match the index R 1 originally generated by the control panel, resulting in a failed comparison.

If the comparison passes, then the security device is considered to be authentic and a flag or other indicia will be set in memory along with the address (which refers to any identifying indicia such as a device ID or serial number) of the security device authenticated to indicate to the control panel that that device may be properly communicated with in subsequent messages with the control panel. If, however, the comparison fails, then the security device is considered to not be authentic and a flag or other indicia will be set in memory along with the address of the failed security device to indicate to the control panel that that device may not be operated or properly communicated with in subsequent messages with the control panel. That is, a failed authentication will result in the security device being effectively not part of the security system and useless In the event that the device fails authentication, a message may be sent by the control panel to a display in the security system that indicates that the device has failed (e.g. “DOOR SENSOR FAILED AUTHENTICATION—DO NOT USE”).

›DETAILED DESCRIPTION OF THE INVENTION · 2 of 2

The authentication procedure will be an automated procedure that is initiated every time a new security device is added to the system and the device's address or other ID is “learned” to the control panel as known in the art. It is also possible to provide for a technician to initiate the authentication procedure at any desired time, such as by entering a predetermined function code into a keypad, pressing a dedicated button, etc. Moreover, in addition to (or instead of) executing the authentication procedure as part of the installation process, it may be desired to execute it automatically at periodic times during operation of the system, for example every four hours.

The control panel and security device will have memory and processing circuitry appropriate to carry out the processes described herein. The functionality described above may be embodied in a microprocessor or microcomputer, ASICs, and the like. Memory in the control panel will store the encryption keys K 1 and K 2 , which will likely be programmed at the factory. Memory that normally stores a list of valid addresses for security devices in the system (e.g. those that have been “learned” into the control panel) will be adapted to include a field that indicates if the device is authentic. In the alternative, there may be a routine that will prevent that device from being learned in the control panel if the authentication procedure fails as described above. The circuitry and software necessary to carry out authentication under this invention preferably resides in the system control panel, but it may also reside in any other device (or devices) in the system, including a device dedicated for the purpose of authenticating other security devices.

In addition to having a direct communication between the control panel and the security device (such as when the control panel authenticates an RF receiver/transmitter device that is wired to the communications medium), there may be situations where the control panel will authenticate a wireless sensor with which the RF receiver/transmitter communicates. That is, the RF receiver/transmitter will act an a gateway between the wireless sensor and the control panel, passing data messages from the control panel to the wireless sensor and from the wireless sensor to the control panel as described above.

In addition to security systems as described herein, the present invention may be used in other networked systems such as access control systems, HVAC systems, home automation systems, and the like.

Although the preferred embodiment doesn't require encrypted transmissions to occur between the control panel and the devices, such encrypted or other types of secure transmissions may be used as well. Also, while the preferred embodiment utilizes encryption methodologies, other types of schemes may be used, such as encoding and obfuscation techniques known in the art.

Claims as granted

35 claims

Log in to read the claims of this application.

Log in to unlock

Classifications

10 codes
IPC · International Patent Classification
Section G — Physics
  • G06F1/24
Section H — Electricity
  • H04L9/32
  • H04L9/00
USPC · US Patent Classification
713/182713/151713/155713/168713/161713/166713/169

Claim changes

Soon
Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this application are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoomJul 2004Jan 2005Jul 2005Jan 2006Jul 2006Jan 2007Jul 2007USPTOApplicantNotice of allowance
USPTOApplicanthover for detail · click to open
Pendency
3.5 y
1,286 days filing → grant
Office actions
0
none on record
Examiner
Thomas R. Peeso
art unit 2132 · TC 2100
Citations: 2 back · 19 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Documents

Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.

Log in to unlock

Chain of title

⤢ drag to zoom200420062008201020122014201620182020202220242026Owner 1Owner 2liens, releases & corrections
TitleLienhover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.

Log in to unlock