Rolling code security system

Abstract
A rolling code transmitter is useful in a security system for providing secure encrypted RF transmission comprising an interleaved trinary bit fixed code and rolling code. To provide even greater security, the transmitter is limited in the number of times it may perform a resynchronization procedure. A receiver demodulates the encrypted RF transmission and recovers the fixed code and rolling code. Upon comparison of the fixed and rolling codes with stored codes and determining that the signal has emanated from an authorized transmitter, a signal is generated to actuate an electric motor to open or close a movable barrier.
Description
BACKGROUND OF THE INVENTION

The invention relates in general to security systems which allow operation upon the receipt of a properly coded signal. More particularly, the invention relates to a security system or to a barrier operator system, such as a garage door operator, employing a transmitter and a receiver which communicate via code streams having at least a portion thereof which changes with multiple operation of the device.


It is well known in the art to provide garage door operators or other barrier operators which include an electric motor connectable through a transmission to a door or other movable barrier which is to be opened and closed. Since many of these systems are associated with residences, as well as with garages, it is important that opening of the barrier be permitted only by one who is authorized to obtain entry to the area which the barrier protects. Some garage door operator systems have in the passed employed mechanical lock and key arrangements associated with electrical switches mounted on the outside of the garage. While these systems enjoy a relatively high level of security, they are very inconvenient to use for a person because it necessitates them exiting their vehicle in order to send the command to open the garage door. This also may present some danger to people when the exit the relative security of their vehicle if someone may be waiting to do injury to them.


It is also well known to provide radio-controlled garage door operators which include a garage door operator unit having a radio receiver and a motor connected to be driven from the radio receiver. The radio receiver is adapted to receive radio frequency signals or other electromagnetic signals having particular signal characteristics which, when received, cause the door to be opened. More recently, such transmitter and receiver systems have become relatively more sophisticated in that they use radio transmitters which employ coded transmissions of multiple or three-valued digits, also known as “trinary bits” or other serial coded transmission techniques. Among these systems are U.S. Pat. No. 3,906,348 to Willmott, which employs a transmitter and receiver system wherein a plurality of mechanical switches may be used to set a stored authorization code.


U.S. Pat. No. 4,529,980 to Liotine et al. discloses a transmitter and receiver combination for use in a device such as a garage door operator wherein the transmitter stores an authorization code which is to be transmitted to and received by the receiver via a radio frequency link. In order to alter or update the authorization code contained within the transmitter, the receiver is equipped with a programming signal transmitter or light emitting diode which can send a digitized optical signal back to the transmitter where it is stored. Other systems also employing encoded transmissions are U.S. Pat. Nos. 4,037,201, 4,535,333, 4,638,433, 4,750,118 and 4,988,992.


While each of these devices has provided good security for the user, it is apparent that persons wishing to commit property or person-related crimes have become more sophisticated as well. It is known in the security industry today that devices are being made available that can intercept or steal rolling code.


Transequatorial Technology, Inc. sells integrated circuit code hopping encoders identified as Keeloq Model NTQ105, NTQ115, NTQ125D and NTQ129. Some of the Keeloq code hopping encoders generate serial codes having fixed portions, i.e., which do not change with repeated actuation of the encoding portion of the chip and rolling code portions which alter with each actuation of the encoding portion of the chip. In order to avoid, however, having the problem of the encoding portion of the chip having been inadvertently enabled and causing the rolling code to be altered on successive enabling attempts thereby leading to a rolling code which is transmitted and not recognized by a receiver, the Keeloq code hopping encoders provide a window forward system, that is they are operable with systems having code receivers which recognize as a valid code not a single rolling code, but a plurality of 1 rolling codes within a certain code window or window of values which are the values which would be generated on a relatively small number of switch closures as compared to the total number of rolling codes available. The problem with such a system, however, might arise if a user was away for a period of time or had inadvertently caused codes to be transmitted excluding the number of codes normally allowed within the valid forward code window. In that case, the rolling code would not be recognized by the receiver and the user could not gain entry without taking other measures to defeat the locking system or the garage door operator system which might involve the intervention of a trained engineer or technician.


Texas Instruments also has a prior system identified as the Mark Star TRC1300 and TRC1315 remote control transmitter/receiver combination. The system involves the use of a rolling code encoder which increments or rolls potentially the entire code, that is, it does not leave a fixed portion. The system also includes a forward windowing function which allows an authorized user to be able to cause the receiver to be enabled within a limited number of key pushes. Like the Keeloq system, if the forward window is exceeded, the Texas Instruments system must be placed in a learn mode to cause the system to relearn the code. In order to place the system into the learn mode, the person must obtain direct access to the receiver to cause a programming control system associated with the receiver to be hand actuated causing the receiver to enter a learn mode. Once the receiver has learned the new code, the receiver will then construct a new valid forward code window within which valid rolling codes may be received. The problem, of course, with such a system is that if, for instance in a garage door operator, the only portal of entry to the garage door is through the overhead door controlled by the garage door operator, the user will not be able to obtain entry to the garage without possibly having to do some damage to the structure. This problem is sometimes referred to in the industry as a “vaulted garage.”


What is needed is an economical encoding system which provides good security by using a rolling code, but which enables a user of the system to proceed via a gradually degraded pathway in the event that the receiver detects a signal condition indicative of what might be a lack of security.


SUMMARY OF THE INVENTION

The invention relates in general to an electronic system for providing remote security for entry of actuation of a particular device. Such a system may include a transmitter and receiver set, for instance with a hand-held transmitter and a receiver associated with a vehicle such as an automobile or the like. The transmitter, upon signaling the receiver, causes the vehicle to start up or to perform other functions. The system may also be useful in a barrier operator system such as a garage door operator by allowing the garage door to be opened and closed in a relatively secure fashion while preventing persons who may be intercepting the radio frequency signals from being able to, although unauthorized, cause the vehicle to begin running or to allow access to the garage.


The system includes a transmitter generally having means for developing a fixed code and a rolling or variable code. The rolling or variable code is changed with each actuation of the transmitter. The fixed code remains the same for each actuation of the transmitter. In the present system, the transmitter includes means for producing a 32-bit frame comprising the fixed portion of the code and a second 32-bit frame comprising the variable portion of the code. The 32-bit rolling code is then mirrored to provide a 32-bit mirrored rolling code. The 32-bit mirrored rolling code then has its most significant bit “deleted” by setting it to zero. The transmitter then converts the 32-bit fixed code and the mirrored variable code to a three-valued or trinary bit fixed code and a three-valued or trinary bit variable code or rolling code.


To provide further security, the fixed code and the rolling codes are shuffled so that alternating trinary bits are comprised of a fixed code bit and a rolling code bit to yield a total of 40 trinary bits. The 40 trinary bits are then packaged in a first 20-trinary bit frame and a second 20-trinary bit frame which have proceeding them a single synchronization and/or identification pulse indicating the start of the frame and whether it is the first frame or the second frame. Immediately following each of the frames, the transmitter is placed into a quieting condition to maintain the average power of the transmitter over a typical 100 millisecond interval within legal limits promulgated by the United States Federal Communications Commission. The first trinary frame and the second trinary frame are used to modulate a radio frequency carrier, in this case via amplitude modulation, to produce an amplitude modulated encrypted signal. In a preferred embodiment, the radio frequency signal is amplitude modulated. The amplitude modulated signal is then launched and may be received by an AM receiver. In the preferred embodiment, the AM receiver receives the amplitude modulated signal, demodulates it to produce a pair of trinary bit encoded frames. The trinary bits in each of the frames are converted on the fly to 2-bit or half nibbles indicative of the values of the trinary bits which are ultimately used to form two 16-bit fixed code words and two 16-bit variable code words. The two 16-bit fixed code words are used as a pointer to identify the location of a previously stored rolling code value within the receiver. The two 16-bit rolling code words are concatenated by taking the 16-bit word having the more significant bits, multiplying it by 310 and then adding it to the second of the words to produce a 32-bit encrypted rolling code. In order to make certain that if the transmitter was inadvertently actuated a number of times, the authorized user can still start his car or gain entry to his garage. The 32-bit encrypted code is then compared via a binary subtraction with the stored rolling code. If the 32-bit code is within a window or fixed count, in the present embodiment 1000, the microprocessor produces an authorization signal which is then responded to by other portions of the circuit to cause the garage door to open or close as commanded. In the event that the code is greater than the stored rolling code, plus 1000, indicative of a relatively large number of incrementations, the user is not locked out of the garage, but is allowed to provide further signals or indicia to the receiver that he is an authorized user without any significant degradation of the security. This is done by the receiver entering an alternate mode requiring two or more successive valid codes to be received, rather than just one. If the two or more successive valid codes are received, the garage door will open. However, in order to prevent a person who has previously or recently recorded a recent valid code from being able to obtain access to the garage, a trailing window, in this case starting at a count of 300 less than the present stored count and including all code values between the present stored count and 300 less is compared to the received code. If the received code is within this backward window, the response of the system simply is to take no further action, nor to provide authorization during that code cycle on the assumption that the code has been purloined.


Thus, the present system provides important advantages over the previous garage door operator systems and even previous rolling code systems. The system provides a multiple segmented windowed system which provides a valid code window, a second relatively insecure code window in which two successive valid codes must be received and finally a window in which no valid codes are recognized due to the likelihood of the receiver having been stolen.


It is a principal object of the present invention to provide a security system involving a radio frequency transmitter and receiver wherein multiple security conditions may exist requiring different levels of signal security.


It is another object of the present invention to provide a secure radio transmitter receiver system which may rapidly and easily decode a relatively large code combination.


Other advantages of the invention will become obvious to one of ordinary skill in the art upon a perusal of the following specification and claims in light of the accompanying drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a perspective view of an apparatus for moving a barrier or garage embodying the present invention;



FIG. 2 is a block diagram of a transmitter for use with a garage door operator of FIG. 1;



FIG. 3 is a block diagram of a receiver positioned within a head unit of the garage door operator shown in FIG. 1;



FIG. 4 is a schematic diagram of the transmitter shown in FIG. 2;



FIG. 5 is a schematic diagram of the receiver shown in FIG. 3;



FIG. 6 is a timing diagram of signals generated by a portion of the transmitter;



FIGS. 7A, B, and C are flow diagrams showing the operation of the transmitter;



FIGS. 8A, B, C, D, E and F are flow charts showing the operation of the receiver;



FIG. 9 is a flow chart showing the operation of the receiver in an embodiment allowing resynchronization;



FIG. 10 is a flow chart showing the operation of the receiver in an additional embodiment disallowing resynchronization;



FIG. 11 is a flow chart showing the operation of the receiver in an additional embodiment enabling windows of variable range sizes;



FIG. 12 is a flow chart showing the operation of the receiver in an additional embodiment preventing resynchronization of resynchronized transmitters;



FIG. 13 is a flow chart showing the operation of the receiver in an additional embodiment requiring time between reception of resynchronization codes; and



FIG. 14 is a flow chart showing the operation of the receiver in an additional embodiment requiring no reception before resynchronization.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring now to the drawings and especially to FIG. 1, more specifically a movable barrier door operator or garage door operator is generally shown therein and includes a head unit 12 mounted within a garage 14. More specifically, the head unit 12 is mounted to the ceiling of the garage 14 and includes a rail 18 extending therefrom with a releasable trolley 20 attached having an arm 22 extending to a multiple paneled garage door 24 positioned for movement along a pair of door rails 26 and 28. The system includes a hand-held transmitter unit 30 adapted to send signals to an antenna 32 positioned on the head unit 12 and coupled to a receiver as will appear hereinafter. An external control pad 34 is positioned on the outside of the garage having a plurality of buttons thereon and communicates via radio frequency transmission with the antenna 32 of the head unit 12.


An optical emitter 42 is connected via a power and signal line 44 to the head unit. An optical detector 46 is connected via a wire 48 to the head unit 12.


Referring now to FIG. 2, the transmitter 30 is shown therein in general and includes a battery 70 connected by a pushbutton switch 72 to a power supply 74 which is coupled via leads 75 and 76 to a microcontroller 78. The microcontroller 78 is connected by a serial bus 79 to a non-volatile memory 80. An output bus 81 connects the microcontroller to a radio frequency oscillator 82. The microcontroller 78 produces coded signals when the button 72 is pushed causing the output of the RF oscillator 82 to be amplitude modulated to supply a radio frequency signal at an antenna 83 connected thereto. More specifically, as shown in FIG. 5, details of the transmitter 30 are shown therein, including a plurality of switches 72. When switch 72 is closed, power is supplied through a diode 100 to a capacitor 102 to supply a 7.1 volt voltage at a lead 103 connected thereto. A light emitting diode 104 indicates that the transmitter button has been pushed and provides a voltage to a lead 105 connected thereto. A Zanier diode 106 provides voltage regulation and causes the back biased diode 107 to cause the crystal 108 to be energized, thereby energizing the microcontroller 78, a Zilog 125C0113 8-bit microcontroller in this embodiment. The signal is also sent via a resistor 110 through a lead 111 to a P32 pin of the microcontroller 78. Likewise, when a switch 113 is closed, current is fed through a diode 114 to the lead 103 also causing the crystal 108 to be energized, powering up the microcontroller at the same time that pin P33 of the microcontroller is pulled up. Similarly, when a switch 118 is closed, power is fed through a diode 119 to the crystal 108 as well as pull up voltage being provided through a resistor 120 to the pin P31. It should also be appreciated that pin P34 of the microcontroller is configured via a connection with the resistor 123 to be an RS232 input port 124.


The microcontroller is coupled via the serial bus 79 to a chip select port, a clock port and a DI port to which and from which serial data may be written and read and to which addresses may be applied. As will be seen hereinafter in the operation of the microcontroller, the microcontroller 78 produces output signals at the lead 81, which are supplied to a resistor 125 which is coupled to a voltage dividing resistor 126 feeding signals to the lead 127. A 30-nanohenry inductor 128 is coupled to an NPN transistor 129 at its base 130. The transistor 129 has a collector 131 and an emitter 132. The collector is connected to the antenna 83 which, in this case, comprises a printed circuit board, loop antenna having an inductance of 25-nanohenries, comprising a portion of the tank circuit with a capacitor 133, a variable capacitor 134 for tuning, a capacitor 135 an a capacitor 136. A 30-nanohenry inductor 138 is coupled via a capacitor 139 to ground. The capacitor has a resistor 140 connected in parallel with it to ground. When the output from lead 81 is driven high by the microcontroller, the capacitor Q1 is switched on causing the tank circuit to output a signal on the antenna 83. When the capacitor is switched off, the output to the drive the tank circuit is extinguished causing the radio frequency signal at the antenna 83 also to be extinguished.


Referring now to FIG. 3, the receiver is shown therein and includes a receiver antenna 200 coupled to an amplitude modulated receiver 202 driven from a power supply 204 connectable to a source of alternating current 206. The receiver 202 provides a demodulated output via a bandpass filter 210 to an analog-to-digital converter 212 which provides input to a microcontroller 214 having an internal read-only memory 216 and an internal random-access memory 218. A serial non-volatile memory 220 is connected via a memory bus 222 to the microcontroller 214 to send and receive information thereto. The microcontroller has an output line 226 coupled to a motor controller 228 which may include a plurality of relays or other standard electromechanical features which feeds electrical current on lines 230 and 232 to an electric motor 234.


Referring now to FIG. 3 the antenna 200 coupled to a reactive divider network 250 comprised of a pair of series connected inductances 252 and 254 and capacitors 256 and 258 which supply an RF signal to a buffer amplifier having an NPN transistor 260, at its emitter 261. The NPN transistor 260 has a pair of capacitors 262 and 264 connected to it for power supply isolation. The buffer amplifier provides a buffered radio frequency output signal on a lead 268. The buffered RF signal is fed to an input 270 which forms part of a super-regenerative receiver 272 having an output at a line 274 coupled to the bandpass filter which provides digital output to the bandpass filter 212. The bandpass filter 212 includes a first stage 276 and a second stage 278 to provide a digital level output signal at a lead 280 which is supplied via an averaging circuit 282 to an input pin P32 of the microcontroller 214.


The microcontroller 214 may have its mode of operation controlled by a programming or learning switch 300 coupled via a line 302 to the P25 pin. A command switch 304 is coupled via a jumper 306 to a line 308 and ultimately through a resistor to the input pin P22. A pin P21 sinks current through a resistor 314 connected to a light emitting diode 316, causing the diode to light to indicate that the receiver is active. The microcontroller 214 has a 4 MHZ crystal 328 connected to it to provide clock signals and includes an RS232 output port 332 that is coupled to the pin P31. A switch 340 selects whether constant pressure or monostable is to be selected as the output from output terminals P24 and P23 which are coupled to a transistor 350 which, when switched on, sinks current through a coil 352 of a relay 354, causing the relay to close to provide an actuating signal on a pair of leads 356 and 358 to an electric motor.


It may be appreciated that the power supply 204 may receive power from an external transformer or other AC source through a jack 370 which is connected to a pair of RJ uncoupling capacitors 372 and 374. The input signal is then set to a full-wave rectifier bridge 376 which provides an output current at a resistor 378. An 18-volt Zanier diode 380 is connected between ground and the resistor 378 and includes high frequency bypass capacitor 382 connected in parallel with it. An 8.2-volt Zanier diode 384 is connected in back-biased configuration to the resistor 378 to receive a signal therefrom to guarantee that at least an 8.2-volt signal is fed to a resistor 390 causing an LED 392 to be illuminated and also causing power to be supplied to a 5-volt 78LO5 voltage regulator 396. The voltage regulator 396 supplies regulated voltage to an output line 398. Filtering capacitors 400a, 400b, 400c and 400d limit the fluctuations at the power supply.


The program code listing for the transmitter is set forth at pages A-1 through A-19 and for the receiver at pages A-20 through A-51 of the attached appendix. Referring now to FIGS. 7A through 7C, the flow chart set forth therein describes the operation of the transmitter. A rolling code is incremented by three in a step 500, followed by the rolling code being stored for the next transmission from the transmitter when the transmitter button is pushed. The order of the binary digits in the rolling code is inverted or mirrored in a step 504, following which in a step 506, the most significant digit is converted to zero effectively truncating the binary rolling code. The rolling code is then changed to a trinary code having values 0, 1 and 2 and the initial trinary rolling code is set to 0. It may be appreciated that it is trinary code which is actually used to modify the radio frequency oscillator signal and the trinary code is best seen in FIG. 6. It may be noted that the bit timing in FIG. 6 for a 0 is 1.5 milliseconds down time and 0.5 millisecond up time, for a 1, 1 millisecond down and 1 millisecond up and for a 2, 0.5 millisecond down and 1.5 milliseconds up. The up time is actually the active time when carrier is being generated. The down time is inactive when the carrier is cut off. The codes are assembled in two frames, each of 20 trinary bits, with the first frame being identified by a 0.5 millisecond sync bit and the second frame being identified by a 1.5 millisecond sync bit.


In a step 510, the next highest power of 3 is subtracted from the rolling code and a test is made in a step 512 to determine if the result is equal to zero. If it is, the next most significant digit of the binary rolling code is incremented in a step 514, following which flow is returned to the step 510. If the result is not greater than 0, the next highest power of 3 is added to the rolling code in the step 516. In the step 518, another highest power of 3 is incremented and in a step 520, a test is determined as to whether the rolling code is completed. If it is not, control is transferred back to step 510. If it has, control is transferred to step 522 to clear the bit counter. In a step 524, the blank timer is tested to determine whether it is active or not. If it is not, a test is made in a step 526 to determine whether the blank time has expired. If the blank time has not expired, control is transferred to a step 528 in which the bit counter is incremented, following which control is transferred back to the decision step 524. If the blank time has expired as measured in decision step 526, the blank timer is stopped in a step 530 and the bit counter is incremented in a step 532. The bit counter is then tested for odd or even in a step 534. If the bit counter is not even, control is transferred to a step 536 where the output bit of the bit counter divided by 2 is fixed. If the bit counter is even, the output bit counter divided by 2 is rolling in a step 538. The bit counter is tested to determine whether it is set to equal to 80 in a step 540. If it is, the blank timer is started in a step 542. If it is not, the bit counter is tested for whether it is equal to 40 in a step 544. If it is, the blank timer is tested and is started in a step 544. If the bit counter is not equal to 40, control is transferred back to step 522.


Referring now to FIGS. 8A through 8F and, in particular, to FIG. 8A, the operation of the receiver is set forth therein. In a step 700, an interrupt is detected and acted upon from the radio input pin. The time difference between the last edge is determined and the radio inactive timer is cleared in step 702. A determination is made as to whether this is an active time or inactive time in a step 704, i.e., whether the signal is being sent with carrier or not. If it is an inactive time, indicating the absence of carrier, control is transferred to a step 706 to store the inactive time in the memory and the routine is exited in a step 708. In the event that it is an active time, the active time is stored in memory in a step 710 and the bit counter is tested in a step 712. If the bit counter zero, control is transferred to a step 714, as may best be seen in FIG. 8B and a test is made to determine whether the inactive time is between 20 milliseconds and 55 milliseconds. If it is not, the bit counter is cleared as well as the rolling code register and the fixed code register in step 716 and the routine is exited in step 718.


In the event that the inactive time is between 20 milliseconds and 55 milliseconds, a test is made in a step 720 to determine whether the active time is greater than 1 millisecond, as shown in FIG. 8C. If it is not, a test is made in a step 722 to determine whether the inactive time is less than 0.35 milliseconds. If it is, a frame 1 flag is set in a step 728 identifying the incoming information as being associated with frame 1 and the interrupt routine is exited in a step 730. In the event that the active time test in step 722 is not less than 0.35 milliseconds, in the step 724, the bit counter is cleared as well as the rolling code register and the fixed register and the return is exited in the step 726. If the active time is greater than 1 millisecond as tested in step 720, a test is made in a step 732 to determine whether the active time is greater than 2.0 milliseconds. If it is not, the frame 2 flag is set in a step 734 and the routine is exited in step 730. If the active time is greater than 2 milliseconds, the bit counter rolling code register and fixed code register are cleared in step 724 and the routine is exited in step 726.


In the event that the bit counter test in step 712 indicates that the bit counter is not 0, control is transferred to step 736, as shown in FIG. 8A. Both the active and inactive periods are tested to determine whether they are less than 4.5 milliseconds. If either is not less than 4.5 milliseconds, the bit counter is cleared as well as the rolling code register and the fixed code registers. If both are equal to greater than 4.5 milliseconds, the bit counter is incremented and the active time is subtracted from the inactive time in the step 738, as shown in FIG. 8D. In the step 740, the results of the subtraction are determined as to whether they are less than 0.38 milliseconds. If they are, the bit value is set equal to zero in step 742 and control is transferred to a decision step 743. If the results are not less than 0.38 milliseconds, a test is made in a step 744 to determine if they difference between the active time and inactive time is greater than 0.38 milliseconds and control is then transferred to a step 746 setting the bit value equal to 2. Both of the bit values being set in steps 742 and 746 relate to a translation from the three-level trinary bits 0, 1 and 2 to a binary number.


If the result of the step 744 is in the negative, the bit value is set equal to 1 in step 748. Control is then transferred to the step 743 to test whether the bit counter is set to an odd or an even number. If it is set to an odd number, control is transferred to a step 750 where the fixed code, indicative of the fact that the bit is an odd numbered bit in the frame sequence, rather an even numbered bit, which would imply that it is one of the interleaved rolling code bits, is multiplied by three and then the bit value added in.


If the bit counter indicates that it is an odd number trinary bit being processed, the existing rolling code registers are multiplied by three and then the trinary bit value obtained from steps 742, 746 and 748 is added in. Whether step 750 or 752 occurs, the bit counter value is the tested in the step 754, as shown in FIG. 8E. If the bit counter value is greater than 21, the bit counter rolling code register and fixed code register are cleared in the step 758 and the routine is exited. If the bit counter value is less than 21, there is a return from the interrupt sequence in a step 756. If the bit counter value is equal to 21, indicating that a sink bit plus trinary data bits have been received, a test is made in a step 760 to determine whether the sink bit was indicative of a first or second frame, if it was indicative of a first frame, the bit counter is cleared and set up is done for the second frame following which there is a return from the routine in the step 762. In the event that the second frame is indicated as being received by the decision of step 760, the two frames have their rolling contributions added together to form the complete inverted rolling code. The rolling code is then inverted or mirrored to recover the rolling code counter value in the step 764.


A test is made in the step 766 to determine whether the program mode has been set. If it has been set, control is transferred to a step 768 where the code is compared to the last code received. If there is no match, as would be needed in order to get programming, then another code will be read until two successive codes match or the program mode is terminated. In a step 770, the codes are tested such that the fixed codes are tested for a match with a fixed code in non-volatile memory. If there is a match, the rolling portion is stored in the memory. If there is not, it is stored in the non-volatile memory. Control is then transferred to step 772, the program indicator is switched off, the program mode is exited and there is a return from the interrupt. In the event that the test of step 766 indicates that the program mode has not been set, the program indicator is switched on in a step 774, as shown in FIG. 8F. The codes are tested to determine whether there is a match for the fixed portion of the code in the step 776. If there is no match, the program indicator is switched off and the routine is exited in step 778. If there is a match, the counter which is indicative of the rolling code is tested in step 780 to determine whether its value is greater than the stored rolling code by a factor or difference of less than 3,000 indicating an interval of 1,000 button pushes for the transmitter. If it is not, a test is made in the step 786 to determine whether the last transmission from the same transmitter is with a rolling code that is two to four less than the reception and, if true, is the memory value minus the received rolling code counter value greater than 1,000. If it is, control is transferred to a step 782 switching off the program indicator and setting the operation command word causing a commanded signal to operate the garage door operator. Note that the factor and interval values are by way of example only. These values may be modified, a described below, by factory authorized service personnel.


The reception time out timer is cleared and the counter value for the rolling code is stored in non-volatile memory, following which the routine is exited in the step 784. In the event that the rolling portion of the present reception is not within two to four of the rolling code value of the prior rolling code and the difference is not greater than 1,000, in step 786 there is an immediate return from the interrupt in the step 784. In the event that the counter test in the step 780 is positive, steps 782 and 784 are then executed thereafter. The step 780, as shown in FIG. 8F, provides its final stage of door operation in response to properly received codes. That is if the received rolling code is within a predetermined number e.g., 3000 of an expected code, flow proceeds to block 782 where the operation command is set to open, close or stop the barrier and the received rolling code is stored in non-volatile memory for use with approving or not, a subsequently received code.


In some cases, it is possible that the rolling code transmitted will be considerably different (greater than the predetermined number of block 780) than what is expected. Such might occur, for example, when this same transmitter is used with a frequently opened residence barrier movement system and an infrequently used vacation home barrier movement system. The rolling code carried by the transmitter will continue to be updated during use of the residence while the rolling code at the vacation home receiver will not.


To protect against loss of use of a barrier movement system (the one at the vacation home in the example) the flow diagram provides the ability of the barrier movement receiver to resynchronize the out of step receiver with the transmitter. When the received rolling code (counter) is more than the predetermined number, e.g., 3000 greater than the expected (stored) code, flow proceeds to decision block 786 which in part implements resynchronization.


Block 786 permits resynchronization when the received rolling code is not within 1000 past codes and when two successive rolling codes from the same transmitter are received within a predetermined range, e.g., 2 through 4, of one another. When the block 786 determines that its conditions are met, a command such as barrier movement is carried out and the rolling code stored in the receiver non-volatile memory is updated in block 782. Resynchronization as shown includes both a command, such as operation of the barrier and updating of the stored rolling code in the receiver. As discussed below, resynchronization may also comprise just the updating of the stored rolling code so that subsequent activations of the transmitter will result in a barrier movement command.


The following text when read in conjunction with FIGS. 9-15 describes several additional embodiments of the present rolling code security system that are used to limit access to resyncing. Because of their similarity to FIG. 8F in most aspects of operation, FIGS. 9-15 are each to be considered a continuation of the flow chart of FIG. 8E. It is to be further noted that the value of the forward window N and the value of the backward window M shown in the figures are variable depending on the particular embodiment, as discussed below.


Referring to FIG. 9, there is provided a system for tracking the total number of resynchronization procedures, or resyncs, that the receiver performs. Once that number is reached, the receiver ignores any additional resync attempts. To track the number of resyncs, a resync counter (not shown) in the receiver is initialized at the factory or during power-on reset with the total number of times that the receiver can be resynced. The counter is decremented each time the receiver is resynced, with the new value in the counter indicating the remaining number of times the receiver can be resynced. Once the resync counter reaches zero, the receiver ignores any subsequent attempts to resync.


Alternatively, the maximum number of allowed resyncs is stored in a nonvolatile memory. The counter, which is initialized to have a value of zero, is incremented each time the receiver is resynced and the incremented value is compared to the number stored in the memory. Once the resync counter equals the stored value, the receiver stops responding to further resync attempts.


It is contemplated that the receiver is to disregard future resync attempts permanently. However, in an alternate embodiment the receiver is configured to ignore resync attempts only for a set period of time. For example, the receiver may be configured to allow resyncs for a specified number of times each day, week, month or other time period as determined by the manufacturer. This information is stored in a non-volatile memory, such as the non-volatile memory 220 (FIG. 3), in the receiver.


Continuing to refer to FIG. 9, the system is shown in operation. In step 786′ it is determined whether the last reception from the same transmitter has a roll that is two to four less than the present reception. If the memory value minus the received rolling code counter value is greater than the value of M (e.g. 1000), then in step 1001 the resync counter is checked to determine whether it is at zero. If the resync counter is reading zero, processing continues to step 784 and the routine is exited. If the resync counter has not reached zero in step 1001, it is decremented in step 1002 and processing continues to step 782 where the rolling code is updated and the garage door operator is activated according to the command. In step 784, the routine is exited. The routine also is exited if the memory value minus the received rolling code counter is determined in step 786′ to be less than M.


Alternatively, as mentioned above, the receiver is configured such that in step 784 after resyncing, it simply updates the rolling code without executing the command. The user then presses the transmitter button once again to transmit the command, which the receiver then executes.


In another embodiment, as shown in FIG. 10, the receiver ignores a reception from a transmitter if the rolling code counter is higher than the specified forward window. This may happen when the transmitted rolling code is greater than what is expected, as described in relation to the infrequently used vacation home example given above. Accordingly, if it is determined in step 780′ that the rolling code value is greater than the stored rolling code by a difference of less than the forward window N, then the command signal to operate the door is transmitted in 782. The routine then exits in step 784. However, if in step 780′ it is determined that the counter is greater than the rolling code by greater than N, then the routine exits in step 784.



FIG. 11 shows an embodiment that allows limited resynchronization. A dynamic window size or dynamic range size is provided to prevent resynchronization only when a variable forward and backward window range is achieved by the received rolling code. The rolling code security system is configured such that the rolling code counter is increased only sequentially, without recycling rolling codes or making use of rolling code values less than that of the current rolling code counter. In an alternative embodiment, an initial rolling code value is stored in a memory. The receiver then determines whether a received rolling code exceeds the value of the stored rolling code. If so, resynchronization is prohibited. In this embodiment a code exceeds the stored code value if the rolling code counter must “roll over” or pass 0 (zero) to achieve the new value.


In operation, in step 780′ the counter value is tested to determine whether it is greater than the stored rolling code by less than the value of the forward window N. If that condition is met, then processing continues to 782 and the garage door is operated. The routine then exits in step 784. Otherwise, processing moves from step 780′ to step 786′, wherein it is determined if the last transmission from the same transmitter is with a rolling code that is two to four less than the reception, and, if so, it is also determined whether the memory value minus the received rolling code counter value is greater than a predetermined backward window M. If those conditions are met, then new forward and backward windows are set in step 1005. Processing then continues to steps 782 and, subsequently, step 784. The forward and backward window values are first established at initialization. Thereafter, step 1005 changes these values in a non-predictable manner. The window values can be obtained from a table stored in memory, random number or calculated from the reception.



FIG. 12 shows an embodiment where the receiver ignores resync commands based on the identity of a transmitter that initiated a prior resync. For example, if a transmitter previously initiated a resync, then the receiver ignores any subsequent resync attempts by the same transmitter. To accomplish this, the receiver records or stores in non-volatile memory the identity of each transmitter that previously initiated resync. That is, the portion of the code that identifies the transmitter to the receiver is saved for future reference in a “used resync” table for comparison purposes in non-volatile memory. Thus, the used resync table acts as a repository for storing the identities of all transmitters that have resynced with the receiver. The receiver, after receiving a code that might initiate resync, compares the identity or fixed code of the transmitter found in the reception, with the contents of the table. If the identity of the transmitter is determined to already exist in the table, the receiver ignores the resync attempt. If no match is found, the resync is completed and the identity of the transmitter is stored.


In operation, in step 786′ the receiver determines whether the last reception from the same transmitter had a roll of two to four less than the present reception. The receiver also determines whether the value in memory minus the received counter is greater than a predetermined value. If either of these conditions is not met, the subroutine is exited in step 784. However, if both conditions are true, then in step 1007, the receiver determines whether the received transmitter identification code, or fixed code, matches the values in the used resync table. If there is no match, then the fixed code is stored in the used resync table in step 1009 and processing moves to steps 782 and subsequently 784, as described above. If the receiver finds a match, indicating that the same transmitter is attempting another resync, the subroutine is exited in step 784 and resync does not occur.


In addition, it should be noted that the embodiment shown in FIG. 12 maybe used in combination with the embodiment of FIG. 9 to allow each transmitter to resync with the receiver a fixed number of times. If the transmitter exceeds that number, the receiver ignores any subsequent resync attempts from that transmitter.



FIG. 13 represents an embodiment in which the rolling code security system is configured such that if two or more transmissions are received within a predetermined amount of time, then the receiver does not perform resync. For example, if a first transmission is followed by a second transmission within two seconds, the receiver ignores or disallows resync that may have been initiated by the second transmission. Conversely, if the resync attempt occurs longer than the predetermined time after its transmission, the attempt is ignored. In operation, in step 786′ the receiver determines whether the last reception from the same transmitter had a roll of two to four less than the present reception. The receiver also determines whether the value in memory minus the received counter is greater than a predetermined value. If either of these conditions is not met, the subroutine is exited in step 784. If both conditions are met, however, then it is determined in step 1011 whether the time between the two resync transmissions was within the specified time boundaries. If so, processing continues to step 782.


In an alternate embodiment of that shown in FIG. 13, the receiver acts on a reception only if the reception is not preceded within a specified period of time by a prior reception. The period of no reception may be defined as a minimum and maximum time boundaries. For example, the receiver may not have received a code for between ten and fifteen seconds before responding to a subsequent reception. As such, the receiver responds only if a code has not been previously received within that specified time range. In operation, as shown in FIG. 14, in step 1013 the receiver determines whether there was no code reception before reception of the two codes within the defined minimum and maximum time boundaries. If so, processing continues to step 782. Otherwise, the subroutine exits in step 784.


For purposes of flexibility in operation, in those instances where resync is disallowed, the manufacturer or an authorized reseller or distributor is provided the ability to reset the counter or adjust other operating parameters for enabling the receiver to respond to resync attempts. Optionally, the security system also may be configured such that a customer is able to resync the transmitter by relearning it to the receiver. An additional option is to provide a visual or aural indicator to notify the user that the resync attempt or the transmitter itself has failed. The indicator may be in the form of an illuminated light emitting diode (LED), electronic message, a tone or voice from a speaker or other method of notification. While there has been illustrated and described several particular embodiments of the present invention, it will be appreciated that numerous changes and modifications will occur to those skilled in the art, and it is intended in the appended claims to cover all those changes and modifications which fall within the true spirit and scope of the present invention.

Claims
  • 1. In a barrier movement system comprising a receiver storing an expected code which responds to rolling codes transmitted by a transmitter, a method comprising: a) receiving a transmitted first rolling code;b) operating the barrier movement system and updating the expected code when the received rolling code is within a predetermined range of the received rolling code;c) not operating the barrier movement system when the expected rolling code is not within the predetermined range of the received rolling code and not updating the expected code;d) receiving a subsequent rolling code after the performance of the not operating step and resynchronizing the receiver when the subsequent rolling code was transmitted by the same transmitter as the first rolling code;e) counting the number of times that step d) is performed and storing value representing the count;f) inhibiting the further performance of the resynchronizing of step d) when the stored number of performances of step d) exceeds a predetermined value.
  • 2. The method of claim 1, further comprising the step of visually indicating that the performance of step d) is being inhibited.
  • 3. The method of claim 1, further comprising the step of aurally indicating that the performance of step d) is being inhibited.
  • 4. The method of claim 1, further comprising the step of permanently preventing the transmitter from further operating the receiver after the inhibition step is performed.
  • 5. The method of claim 1, further comprising the step of enabling the receiver to disregard codes transmitted from the transmitter for a set duration of time after the step f is performed.
  • 6. The method of claim 1, wherein the step further comprises the steps of: storing a maximum number of times the receiver is allowed to perform the step d;comparing the counted value with the maximum number stored in the memory; anddetermining whether the counter value equals the number stored in memory.
  • 7. The method of claim 1, wherein the transmitter has an identity and the inhibiting step comprises: recording in memory the identity of a transmitter that has initiated performance of the step d;denying performance of the step d in response to a code transmitted from a transmitter having an identity matching an identity recorded in memory by the recording step.
  • 8. The method of claim 1 wherein the step d comprises inhibiting the issuance of a command for barrier movement.
  • 9. The method of claim 1 wherein the step d comprises inhibiting the updating of the value of the expected code stored in the receiver.
  • 10. The method of claim 1 comprising: measuring the time between successive transmissions from the transmitter.
  • 11. The method of claim 10, wherein the inhibiting step is performed when the measured time is less than a first predetermined time limit.
  • 12. In a barrier movement system comprising a receiver storing an expected code which responds to rolling codes transmitted by a transmitter, a method comprising: a) receiving a transmitted first rolling code;b) operating the barrier movement system and updating the expected code when the received rolling code is within a predetermined range of the received rolling code;c) not operating the barrier movement system when the expected rolling code is not within the predetermined range of the received rolling code and not updating the expected code;d) receiving a subsequent rolling code after the performance of the not operating step and resynchronizing the receiver when the subsequent rolling code was transmitted by the same transmitter as the first rolling code;e) counting the number of times that step d) is performed and storing value representing the count;f) measuring the time between the performance of step c and receiving a subsequent rolling code; andg) inhibiting the performance of the resynchronizing of step d) when the measured time is less than a predetermined value.
  • 13. The method of claim 12, further comprising the step of visually indicating that the performance of step d is being inhibited.
  • 14. The method of claim 12, further comprising the step of aurally indicating that the performance of step d is being inhibited.
  • 15. The method of claim 12, further comprising the step of permanently preventing the transmitter from further operating the receiver after the inhibiting step is performed.
  • 16. The method of claim 12, further comprising the step of enabling the receiver to disregard codes transmitted from the transmitter for a set duration of time after the step f is performed.
  • 17. The method of claim 12, wherein the inhibiting step further comprises the steps of: storing a time value;comparing the measured time with the stored time value; anddetermining whether the measured time exceeds the stored time value.
  • 18. The method of claim 12, wherein the transmitter has an identity and the inhibiting step comprises: recording in memory an identity of a transmitter that has initiated performance of the step d; anddenying performance of the step d in response to a code transmitted from a transmitter having an identity matching an identity recorded in memory by the recording step.
  • 19. The method of claim 12 wherein the step d comprises inhibiting the updating of the value of its expected code stored in the receiver.
Parent Case Info

This application is a continuation-in-part of U.S. application Ser. No. 09/981,433, filed Oct. 17, 2001, now U.S. Pat. No. 6,980,655, which is a continuation of U.S. application Ser. No. 09/489,073 filed Jan. 21, 2000, now U.S. Pat. No. 6,690,796, which is a continuation of U.S. application Ser. No. 08/873,149 filed Jun. 11, 1997, now U.S. Pat. No. 6,154,544,which is a continuation of U.S. application Ser. No. 08/446,886 filed May 17, 1995, now abandoned, each of which is incorporated in their entirety herein by reference.

US Referenced Citations (179)
Number Name Date Kind
2405500 Guannella Aug 1946 A
3716865 Willmott Feb 1973 A
3735106 Hollaway May 1973 A
3792446 McFiggins et al. Feb 1974 A
3798359 Feistel Mar 1974 A
3798360 Feistel Mar 1974 A
3798605 Feistel Mar 1974 A
3845277 Voss et al. Oct 1974 A
3890601 Pietrolewicz Jun 1975 A
3906348 Willmott Sep 1975 A
3938091 Atalla et al. Feb 1976 A
4037201 Willmott Jul 1977 A
4064404 Willmott et al. Dec 1977 A
RE29525 Willmott Jan 1978 E
4078152 Tuckerman, III Mar 1978 A
4138735 Allocca et al. Feb 1979 A
4178549 Ledenbach et al. Dec 1979 A
4195196 Feistel Mar 1980 A
4195200 Feistel Mar 1980 A
4196310 Forman et al. Apr 1980 A
4218738 Matyas et al. Aug 1980 A
4304962 Fracassi et al. Dec 1981 A
4305060 Apple et al. Dec 1981 A
4316055 Feistel Feb 1982 A
4326098 Bouricius et al. Apr 1982 A
4327444 Court Apr 1982 A
4328414 Atalla May 1982 A
4328540 Matsuoka et al. May 1982 A
RE30957 Feistel Jun 1982 E
4380762 Capasso Apr 1983 A
4385296 Tsubaki et al. May 1983 A
4393269 Konheim et al. Jul 1983 A
4418333 Schwarzbach et al. Nov 1983 A
4426637 Apple et al. Jan 1984 A
4445712 Smagala-Romanoff May 1984 A
4447890 Duwel et al. May 1984 A
4454509 Buennagel et al. Jun 1984 A
4464651 Duhame Aug 1984 A
4471493 Schober Sep 1984 A
4491774 Schmitz Jan 1985 A
4509093 Stellberger Apr 1985 A
4529980 Liotine et al. Jul 1985 A
4535333 Twardowski Aug 1985 A
4574247 Jacob Mar 1986 A
4578530 Zeidler Mar 1986 A
4581606 Mallory Apr 1986 A
4590470 Koenig May 1986 A
4593155 Hawkins Jun 1986 A
4596898 Pemmaraju Jun 1986 A
4596985 Bongard et al. Jun 1986 A
4599489 Cargile Jul 1986 A
4602357 Yang et al. Jul 1986 A
4611198 Levinson et al. Sep 1986 A
4623887 Welle, II Nov 1986 A
4626848 Ehlers Dec 1986 A
4628315 Douglas Dec 1986 A
4630035 Stahl et al. Dec 1986 A
4633247 Hegeler Dec 1986 A
4638433 Schindler Jan 1987 A
4646080 Genest et al. Feb 1987 A
4652860 Weishaupt et al. Mar 1987 A
4653076 Jerrim et al. Mar 1987 A
4670746 Taniguchi et al. Jun 1987 A
4686529 Kleefeldt Aug 1987 A
4695839 Barbu et al. Sep 1987 A
4703359 Rumbolt et al. Oct 1987 A
4710613 Shigenaga Dec 1987 A
4716301 Willmott et al. Dec 1987 A
4720860 Weiss Jan 1988 A
4723121 van den Boom et al. Feb 1988 A
4731575 Sloan Mar 1988 A
4737770 Brunius et al. Apr 1988 A
4740792 Sagey et al. Apr 1988 A
4750118 Heitschel et al. Jun 1988 A
4754255 Sanders et al. Jun 1988 A
4755792 Pezzolo et al. Jul 1988 A
4758835 Rathmann et al. Jul 1988 A
4761808 Howard Aug 1988 A
4779090 Micznik et al. Oct 1988 A
4794268 Nakano et al. Dec 1988 A
4794622 Isaacman et al. Dec 1988 A
4796181 Wiedemer Jan 1989 A
4799061 Abraham et al. Jan 1989 A
4800590 Vaughn Jan 1989 A
4802114 Sogame Jan 1989 A
4804938 Rouse et al. Feb 1989 A
4807052 Amano Feb 1989 A
4808995 Clark et al. Feb 1989 A
4825200 Evans et al. Apr 1989 A
4825210 Bachhuber et al. Apr 1989 A
4831509 Jones et al. May 1989 A
4835407 Kataoka et al. May 1989 A
4845491 Fascenda et al. Jul 1989 A
4847614 Keller Jul 1989 A
4855713 Brunius Aug 1989 A
4856081 Smith Aug 1989 A
4859990 Isaacman Aug 1989 A
4870400 Downs et al. Sep 1989 A
4878052 Schulze Oct 1989 A
4881148 Lambropoulos et al. Nov 1989 A
4885778 Weiss Dec 1989 A
4888575 De Vaulx Dec 1989 A
4890108 Drori et al. Dec 1989 A
4905279 Nishio Feb 1990 A
4912463 Li Mar 1990 A
4914696 Dudczak et al. Apr 1990 A
4918690 Markkula, Jr. et al. Apr 1990 A
4922168 Waggamon et al. May 1990 A
4922533 Philippe May 1990 A
4928098 Dannhaeuser May 1990 A
4931789 Pinnow Jun 1990 A
4939792 Urbish et al. Jul 1990 A
4942393 Waraksa et al. Jul 1990 A
4951029 Severson Aug 1990 A
4963876 Sanders Oct 1990 A
4979832 Ritter Dec 1990 A
4980913 Skret Dec 1990 A
4988992 Heitschel et al. Jan 1991 A
4992783 Zdunek et al. Feb 1991 A
4999622 Amano et al. Mar 1991 A
5001332 Schrenk Mar 1991 A
5023908 Weiss Jun 1991 A
5049867 Stouffer Sep 1991 A
5055701 Takeuchi Oct 1991 A
5058161 Weiss Oct 1991 A
5060263 Bosen et al. Oct 1991 A
5103221 Memmola Apr 1992 A
5107258 Soum Apr 1992 A
5126959 Kurihara Jun 1992 A
5144667 Pogue, Jr. et al. Sep 1992 A
5146067 Sloan et al. Sep 1992 A
5148159 Clark et al. Sep 1992 A
5153581 Hazard Oct 1992 A
5159329 Lindmayer et al. Oct 1992 A
5168520 Weiss Dec 1992 A
5193210 Nicholas et al. Mar 1993 A
5224163 Gasser et al. Jun 1993 A
5237614 Weiss Aug 1993 A
5252960 Duhame Oct 1993 A
5278907 Snyder et al. Jan 1994 A
5280527 Gullman et al. Jan 1994 A
5331325 Miller Jul 1994 A
5361062 Wiess et al. Nov 1994 A
5363448 Koopman, Jr. et al. Nov 1994 A
5365225 Bachhuber Nov 1994 A
5367572 Weiss Nov 1994 A
5369706 Latka Nov 1994 A
5412379 Waraksa et al. May 1995 A
5414418 Andros, Jr. May 1995 A
5420925 Michaels May 1995 A
5442341 Lambropoulos Aug 1995 A
5444737 Cripps et al. Aug 1995 A
5471668 Soenen et al. Nov 1995 A
5473318 Martel Dec 1995 A
5479512 Weiss Dec 1995 A
5485519 Weiss Jan 1996 A
5517187 Bruwer et al. May 1996 A
5528621 Heiman et al. Jun 1996 A
5530697 Watanabe Jun 1996 A
5563600 Miyake Oct 1996 A
5594429 Nakahara Jan 1997 A
5598475 Soenen et al. Jan 1997 A
5608723 Felsenstein Mar 1997 A
5657388 Weiss Aug 1997 A
5680131 Utz Oct 1997 A
5686904 Bruwer Nov 1997 A
5745068 Takahashi et al. Apr 1998 A
5774065 Mabuchi et al. Jun 1998 A
5778348 Manduley et al. Jul 1998 A
5872519 Issa et al. Feb 1999 A
5898397 Murray Apr 1999 A
5923758 Khamharn et al. Jul 1999 A
5937065 Simon et al. Aug 1999 A
6154544 Farris et al. Nov 2000 A
6175312 Bruwer et al. Jan 2001 B1
6275519 Hendrickson Aug 2001 B1
6690796 Farris et al. Feb 2004 B1
6980655 Farris et al. Dec 2005 B2
7412056 Farris et al. Aug 2008 B2
Foreign Referenced Citations (8)
Number Date Country
0 311 112 Apr 1989 EP
0 372 285 Jun 1990 EP
0 857 842 Aug 1998 EP
2 265 482 Sep 1993 GB
WO 9320538 Oct 1993 WO
WO 9411829 May 1994 WO
WO 9418036 Aug 1994 WO
WO 94.18036 Aug 1994 WO
Related Publications (1)
Number Date Country
20030118187 A1 Jun 2003 US
Continuations (3)
Number Date Country
Parent 09489073 Jan 2000 US
Child 09981433 US
Parent 08873149 Jun 1997 US
Child 09489073 US
Parent 08446886 May 1995 US
Child 08873149 US
Continuation in Parts (1)
Number Date Country
Parent 09981433 Oct 2001 US
Child 10219829 US