Electronic locks have a number of advantages over normal mechanical locks. For example, electronic locks may be encrypted so that only a key carrying the correct code will operate the lock. In addition, an electronic lock may contain a microprocessor so that, for example, a record can be kept of who has operated the lock during a certain time period or so that the lock is only operable at certain times. An electronic lock may also have the advantage that, if a key is lost, the lock may be reprogrammed to prevent the risk of a security breach and to avoid the expense associated with replacement of the entire lock.
One drawback of certain electronic locks is that they use a power supply to function properly. Typically, locks of this type are unable to use alternating current (AC) power supplies, such as from wall outlets, due to the inherit lack of security and mobility of such power supplies. Batteries may be used instead, but batteries may require constant replacement or recharging. If a battery dies, a lock might fail to function and thereby create a significant security risk. Electromagnets may also be employed, but the bulk of such devices in some instances limit the potential use of electronic locks to larger-scale applications.
One solution to these drawbacks is to place a power source such as a battery in the key instead of in the lock. This arrangement allows the lock to remain locked even in the absence of a power supply. Placing a battery in the key also allows the battery to be charged more easily because keys are generally more portable than locks.
When batteries are used in the key, electrical contacts are typically employed to transfer power and data from the key to the lock. However, electrical contacts suffer from the drawback of being susceptible to corrosion, potentially leading to failure of either the key or the lock. Moreover, if separate inductors are used instead to transfer both power and data, magnetic interference between the inductors can corrupt the data and disrupt power flow to the lock.
Throughout the drawings, reference numbers may be re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate embodiments of the inventions described herein and not to limit the scope thereof.
The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the all of the desirable attributes disclosed herein. Details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and the description below.
Certain aspects of the present disclosure relate to a method for detecting a lock state of an electronic lock. The method may be performed by an electronic key or a processor included with the electronic key. The electronic key may include: a housing; a power source disposed within the housing; a partial capacitor comprising a first capacitive metal plate, the first capacitive metal plate of the partial capacitor configured to form a capacitor with a corresponding second capacitive metal plate of an electronic lock when brought into proximity with the second capacitive metal plate of the electronic lock; and a processor in communication with the power source and with the partial capacitor, the processor programmed to transfer data signals to an electronic lock through the first capacitive metal plate to the second capacitive metal plate in the electronic lock. The method may include: mating the electronic key with the electronic lock; transmitting an unlock signal from the electronic key to the electronic lock; receiving, at the electronic key, a confirmation signal from the electronic lock, the confirmation signal indicating that the electronic lock has unlocked; recording, in a memory device of the electronic key, a first time at which the electronic lock has unlocked; transmitting a first heartbeat signal from the electronic key to the electronic lock; receiving, at the electronic key, a first response to the first heartbeat signal from the electronic lock; determining, by virtue of receiving the first response, that the electronic lock is still unlocked; transmitting one or more second heartbeat signals from the electronic key to the electronic lock; determining, after not receiving a second response to the one or more second heartbeat signals, that the electronic lock has relocked; recording, in a memory device of the electronic key, a second time at which the electronic lock has relocked; and outputting from the electronic key the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked.
In some aspects, said determining, after not receiving a second response to the one or more second heartbeat signals, that the electronic lock has relocked comprises determining that the electronic lock has relocked after detecting no response to three of the second heartbeat signals, or some other defined number of second heartbeat signals (e.g., 2, 4, 5, 10, or more, or some number in between the preceding examples). Further, in some aspects, said outputting is performed in response to docking the electronic key with a docking device. Moreover, said outputting may comprise transmitting the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked over a network to a remote server. In some aspects, the electronic lock is mated with the electronic key in a manner such that when the electronic lock is unlocked and the electronic key is rotated to an open position, the electronic key is unable to be removed from the electronic lock while the electronic key remains in the open position.
Certain aspects of the present disclosure relate to a method for detecting a lock state of an electronic lock. The method may include transmitting an unlock signal from an electronic key to an electronic lock mated with the electronic key; receiving, at the electronic key, a confirmation signal from the electronic lock, the confirmation signal indicating that the electronic lock has unlocked; recording, in a memory device of the electronic key, a first time at which the electronic lock has unlocked; transmitting a first heartbeat signal from the electronic key to the electronic lock; receiving, at the electronic key, a first response to the first heartbeat signal from the electronic lock; determining, by virtue of receiving the first response, that the electronic lock is still unlocked; transmitting one or more second heartbeat signals from the electronic key to the electronic lock; determining, after not receiving a second response to the one or more second heartbeat signals, that the electronic lock has relocked; recording, in a memory device of the electronic key, a second time at which the electronic lock has relocked; and outputting from the electronic key the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked.
In some aspects, said determining, after not receiving a second response to the one or more second heartbeat signals, that the electronic lock has relocked comprises determining that the electronic lock has relocked after detecting no response to three heartbeat signals. Further, said outputting may be performed in response to docking the electronic key with a docking device. In some cases, said outputting comprises transmitting the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked over a network to a remote server. In addition, the electronic lock may be mated with the electronic key in a manner such that when the electronic lock is unlocked and the electronic key is rotated to an open position, the electronic key is unable to be removed from the electronic lock while the electronic key remains in the open position.
Certain aspects of the present disclosure relate to a method of detecting a lock state of an electronic lock. The method may include: transmitting an unlock signal from an electronic key to an electronic lock; receiving, at the electronic key, a confirmation signal from the electronic lock, the confirmation signal indicating that the electronic lock has unlocked; recording, in a memory device of the electronic key, a first time at which the electronic lock has unlocked; transmitting one or more heartbeat signals from the electronic key to the electronic lock; determining, after not receiving a response to the one or more heartbeat signals, that the electronic lock has relocked; recording, in a memory device of the electronic key, a second time at which the electronic lock has relocked; and outputting from the electronic key the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked.
In some cases, the unlock signal is transmitted after mating the electronic key with the electronic lock. Further, the unlock signal may be transmitted after receiving or confirming receipt of a keycode that matches a keycode stored at the electronic lock. Moreover, the one or more heartbeat signals may include a plurality of heartbeat signals. Further, the method may include receiving, at the electronic key, a first response to a first heartbeat signal included in the plurality of heartbeat signals from the electronic lock; and determining, by virtue of receiving the first response, that the electronic lock is still unlocked. The method may further include transmitting one or more additional heartbeat signals included in the plurality of heartbeat signals from the electronic key to the electronic lock; and determining, after not receiving a second response to the one or more additional heartbeat signals, that the electronic lock has relocked. Additionally, the method may include recording, in a memory device of the electronic key, a second time at which the electronic lock has relocked; and outputting from the electronic key the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked.
Certain aspects of the present disclosure relate to an electronic key. The electronic key may include: a housing; a power source disposed within the housing; a partial capacitor comprising a first capacitive metal plate, the first capacitive metal plate of the partial capacitor configured to form a capacitor with a corresponding second capacitive metal plate of an electronic lock when brought into proximity with the second capacitive metal plate of the electronic lock; and a processor in communication with the power source and with the partial capacitor, the processor programmed to: transmit an unlock signal from the electronic key to the electronic lock when the electronic key is mated to the electronic lock; receive, at the electronic key, a confirmation signal from the electronic lock, the confirmation signal indicating that the electronic lock has unlocked; record, in a memory device of the electronic key, a first time at which the electronic lock has unlocked; transmit a first heartbeat signal from the electronic key to the electronic lock; receive, at the electronic key, a first response to the first heartbeat signal from the electronic lock; determine, by virtue of receiving the first response, that the electronic lock is still unlocked; transmit one or more second heartbeat signals from the electronic key to the electronic lock; determine, after not receiving a second response to the one or more second heartbeat signals, that the electronic lock has relocked; record, in a memory device of the electronic key, a second time at which the electronic lock has relocked; and output from the electronic key the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked.
In some implementations, the first capacitive metal plate comprises an annulus. Further, the electronic key may include: a key power coil, wherein the key power coil and the first capacitive metal plate are concentric; and a nose portion disposed within a hole formed by the annulus, wherein the key power coil is disposed at least partially within the nose portion. In some cases, the processor is programmed to determine, after not receiving a second response to the one or more second heartbeat signals, that the electronic lock has relocked by at least determining that the electronic lock has relocked after detecting no response to three of the second heartbeat signals. In certain aspects, the electronic lock is mated with the electronic key in a manner such that when the electronic lock is unlocked and the electronic key is rotated to an open position, the electronic key is unable to be removed from the electronic lock while the electronic key remains in the open position.
Further, the processor may be programmed to output from the electronic key the first time at which the electronic key has unlocked and the second time at which the electronic key has relocked in response to docking the electronic key with a docking device or a docking station. In some cases, the docking station is configured to secure the electronic key in the docking device until a passcode is entered into the docking device. In some cases, the passcode is entered into the electronic key. In some such cases, the electronic key may provide the passcode to the docking device, which may determine whether to unlock the electronic key enabling removal of the electronic key from the docking device based on whether the passcode matches information stored at the docking device. In some cases, the docking device is configured to transmit the output from the electronic key to a remote server. Further, the output from the electronic key may constitute or comprise audit trail data that is stored in a cloud computing platform comprising the remote server. Moreover, in some implementations, the docking device is configured to charge the electronic key.
In the description below certain relative terms such as top, bottom, left, right, front and back are used to describe the relationship between certain components or features of the illustrated embodiments. Such relative terms are provided as a matter of convenience in describing the illustrated embodiments and are not intended to limit the scope of the technology discussed below.
Electronic key and lock assemblies can advantageously incorporate contactless power and/or data transfer as a technique of electrical communication between key and lock components. In addition to inductive power and/or data transfer using transmitters and receivers fitted with electrical coils, an alternative approach utilizes a capacitive, rather than inductive, interface as a mechanism of delivering an electrical signal. Use of a capacitive interface may provide certain advantages over an inductive interface. For example, with a capacitor, electromagnetic fields may be generally confined between and around conductive plates of the capacitor, which can facilitate eliminating magnetic flux guiding and/or shielding components, thereby reducing bulk and/or cost concerns.
Thus, in certain embodiments, an electronic key may include a partial capacitor comprising a capacitive metal plate in communication with a processor. The capacitive metal plate of the partial capacitor can form a capacitor with a corresponding capacitive metal plate of a lock when brought into proximity with the metal plate of the lock, thereby allowing for capacitive data or power transfer between the key and lock. A common ground can be established between the metal plate of the key and the metal plate of the lock through a parasitic capacitance present between the key and lock circuitry. Prior to describing such features,
The illustrated electronic lock and key system 10 can use electronic means to verify the identity of the key and to actuate the internal mechanism of the lock 100. When the key 200 engages the lock 100, data transfer and power transfer is enabled between the lock 100 and the key 200. The lock 100 is then preferably permitted to be actuated by the key 200 to move from a locked position to an unlocked position and permit access to the space or location secured by the lock 100. In the illustrated arrangement, the direction of power transfer preferably is from the key 200 to the lock 100, as is described in greater detail below. However, in alternative arrangements, the direction of power transfer may be reversed or may occur in both directions.
The illustrated lock 100 is preferably used in a cabinet, or other such storage compartment, and can selectively secure a drawer or door of the cabinet relative to a body of the cabinet. However, as will be appreciated, the lock 100 may be used in, or adapted for use in, a variety of other applications. The lock 100 is preferably mounted to the cabinet in such a way so as to allow only a front portion of the lock 100 to be accessible when the cabinet is closed. The lock 100 includes an outer housing 102 with a cylinder 104 that is rotatable within the outer housing 102 when actuated by the key 200. An exposed end of the cylinder 104 can support a lock tab (not shown). The lock tab can cooperate with a stop. The lock 100 is associated with one of the drawer (or door) of the cabinet and the cabinet body, and the stop is associated with the other of the drawer (or door) of the cabinet and the cabinet body. The lock tab rotates with the lock cylinder 104 to move between a locked position, wherein the lock tab mechanically interferes with the stop, to an unlocked position, wherein the lock tab does not interfere with the stop. In addition, other suitable locking arrangements may be utilized.
The housing 102 of the lock 100 preferably is a generally cylindrical tube with a head portion 112 and a body portion 114. The diameter of the head portion 112 is larger than the diameter of the body portion 114 such that the head portion 112 forms a flange of the housing 102. The head portion 112 also includes an annular groove 174 or key recess. Axially-extending slots 176 open into the annular groove 174 (
The lock housing 102 also includes a body portion 114 which extends rearwardly away from the head portion 112. The rearward end of the body portion further includes a threaded outer surface 115 which can receive a nut (not shown). The nut is used to secure the lock 100 to a cabinet or other storage compartment. The body portion 114 also includes at least one, and preferably a pair of opposed flattened surfaces 113 or “flats” (
With continued reference to
The body portion 114 further includes a tab 122 that extends slightly rearward from the rearward end of the body portion 114. The tab 122 acts as a stop to limit the rotation of a lock tab (not shown) secured to the cylinder 104.
The housing 102 can include a break-away feature incorporated into the structure of the housing 102. The head portion 112 is formed with the body portion 114 in such a way that if someone attempted to twist the housing 102 of the lock 100 by grasping the head portion 112, the head portion 112 is capable of breaking free of the body portion 114, preferably at a location near the intersection of the head portion 112 and the body portion 114 of the housing 102. This feature is advantageous in that it increases the difficulty of opening or disabling the lock 100 by grasping the housing 102. That is, if a person were to attempt to grasp the head portion 112 and it were to break away then there would no longer be an easily graspable surface with which to try to rotate the lock 100 mechanically, without use of the key 200, because the head portion 112, which is external to the cabinet, would no longer be coupled to the body portion 114, which is internal to the cabinet. The break-away feature between the head portion 112 and the body portion 114 may be created simply by a structure that concentrates stresses at the head portion 112/body portion 114 junction. Alternatively, the housing 102 may be deliberately weakened at or near the head portion 112/body portion 114 junction, or at any other desirably or suitable location. Other anti-tampering solutions may be employed as well.
With continued reference to
The cartridge 106 is surrounded by a tamper-resistant case 124 that houses a circuit board 134 can receive instructions when the key 200 engages with the lock 100. The circuit board 134 is can recognize the proper protocol used to unlock the lock 100. The circuit board 134 is further can actuate the solenoid 126 to reverse the polarity of the solenoid 126 and repel the slide bars 128 away from the solenoid 126. The details of the circuit board 134 and a method of communication between the key 200 and the lock 100 are discussed in greater detail below. The interior of the case 124 preferably is filled with a filler material, such as an epoxy, to occupy empty space within the case 124 and protect and maintain a desired position of the components within the case 124, such as the circuit board 134 and wires 160.
The lock cartridge 106 further includes two slide tubes 136 which are positioned on opposite sides of the solenoid 126 and are can at least partially encapsulate the slide bars 128 and are further can provide a smooth, sliding surface for the slide bars 128. The slide tubes 136 each include an aperture 138 can receive at least a portion of a bolt 130, or side bar, of the lock 100 when the lock 100 is in an unlocked position.
The bolt 130 is preferably a relatively thin, generally block-shaped structure that is movable between a locked position, in which rotation of the lock cylinder 104 relative to the housing 102 is prohibited, and an unlocked position, in which rotation of the lock cylinder 104 relative to the housing 102 is permitted. Preferably, the bolt 130 moves in a radial direction between the locked position and the unlocked position, with the unlocked position being radially inward of the locked position.
The bolt 130 includes two cylindrical extensions 131, which extend radially inward toward the cartridge 106. When the solenoid 126 is actuated to repel the slide bars 128 such that the apertures 138 are not blocked by the slide bars 128, the extensions 131 of the bolt 130 may enter into the case 124 through the apertures 138 as the bolt 130 moves radially inward.
The bolt 130 is preferably of sufficient strength to rotationally secure the cylinder 104 relative to the housing 102 when the bolt 130 is in the locked position, wherein a portion of the bolt 130 is present within the groove 120. The bolt 130 has a sloped or chamfered lower edge 129, which in the illustrated embodiment is substantially V-shaped. The lower edge 129 can mate with the groove 120, which preferably is of an at least substantially correspondingly shape to the lower edge 129 of the bolt 130. The V-shaped edge 129 of the bolt 130 interacting with the V-shaped groove 120 of the housing 102 urges the bolt 130 in a radially inward direction towards the cartridge 106 in response to rotation of the cylinder 104 relative to the housing 102. That is, the sloped lower edge 129 and groove 120 cooperate to function as a wedge and eliminate the need for a mechanism to positively retract the bolt 130 from the groove 120. Such an arrangement is used in certain embodiments due to its simplicity and reduction in the number of necessary parts. However, other suitable arrangements to lock and unlock the cylinder 104 relative to the housing 102 may also be used.
When the lock 100 is in an unlocked condition and the slide bars 128 are spaced from the solenoid 126, as shown in
When the lock 100 is in a locked condition, the bolt 130 is extended radially outward into engagement with the groove 120. The bolt 130 is prevented from inward movement out of engagement with the groove 120 due to interference between the extensions 131 and the slide bars 128. When the lock 100 is in the unlocked position, the slide bars 128 are moved away from the solenoid 126 due to a switching of magnetic polarity of the solenoid 126, which is actuated by the circuit board 134. The bolt 130 is then free to move radially inward towards the center of the cylinder 104 and out of engagement with the groove 120. At this point, the rotation of the cylinder 104 within the housing 102 may cause the bolt 130 to be displaced from engagement with the groove 120 due to the cooperating sloped surfaces of the groove 120 and the lower edge 129 of the bolt 130. The cylinder 104 is then free to be rotated throughout the unlocked rotational range within the housing 102. When the cylinder 104 is rotated back to a locked position, that is, when the lower edge 129 of the bolt 130 is aligned with the groove 120, the bolt 130 is urged radially outward by the springs 132 such that the lower edge 129 is engaged with the groove 120. Once the extensions 131 of the bolt 130 are retracted from the case 124 to a sufficient extent, the slide bars 128 are able to move towards the solenoid 126 to once again establish the locked position of the lock 100.
Although
With continued reference to
The pins 140 are preferably made from a carbide material, but can be made of any suitable material or combination of materials that are capable of providing a suitable hardness to reduce the likelihood of successful drilling past the pins 140 and attack ball 142. The pins 140 are inserted into the cylinder 104 to a depth that is near the outer extremity of the attack ball 142. A small space may be provided between the outer end of the attack ball 142 and the end of the carbide pin 140 to allow for the passage of the wires 160, which is discussed in greater detail below. The pins 140 are provided so as to add strength and hardness to the outer periphery of the cylinder 104 adjacent to the attack ball 142.
The attack ball 142 is preferably made of a ceramic material but, similar to the carbide pins, can be made of any suitable material that is of sufficient hardness to reduce the likelihood of successful drilling of the lock cylinder 104. The attack ball 142 is preferably generally spherical shape and lies within a pocket on substantially the same axis as the cartridge 106. Preferably, the attack ball 142 is located in front of the cartridge 106 and is aligned along the longitudinal axis of the lock 100 with the pins 140. The attack ball 142 can reduce the likelihood of a drill bit passing through the cylinder and drilling out the cartridge 106. It is preferable that if an attempt is made to drill out the cylinder 104, the attack ball 142 is sufficiently hard as to not allow the drill bit to drill past the ball 142 and into the cartridge 106. The shape of the attack ball 142 is also advantageous in that it will likely deflect a drill bit from drilling into the cartridge 104 by not allowing the tip of the drill bit to locate centrally relative to the lock 100. Because the attack ball 142 is held within a pocket, it advantageously retains functionality even if cracked or broken. Thus, the attack guard portion 110 can substantially reduce the likelihood of success of an attempt to drill out the cartridge 106. In addition, or in the alternative, other suitable arrangements to prevent drilling, or other destructive tampering, of the lock 100 may be used as well.
One advantage of using the pins 140 and the attack ball 142 is that the entire lock cylinder 104 does not have to be made of a hard material. Because the lock cylinder 104 includes many features that are formed in the material by shaping (e.g., casting or forging) or material removal (e.g., machining), it would be very difficult to manufacture a cylinder 104 entirely of a hard material such as ceramic or carbide. By using separate pins 140 and an attack ball 142, which are made of a very hard material that is difficult to drill, the lock cylinder 104 can be easily manufactured of a material such as stainless steel which has properties that allow easier manufacture. Thus a lock cylinder can be made that is both relatively easy to manufacture, but also includes drill resistant properties.
With continued reference to
The data and power mating portion 146 includes a mating cup 152, a data coil 154, and a power coil 156. The cup 152 can receive a portion of key 200 when the lock 100 and the key 200 are engaged together. The cup 152 resides at least partially in an axial recess 158 which is located in a front portion of the lock cylinder 104 and further houses the attack ball 142. The cup is at least partially surrounded by the power coil 156, which can inductively receive power from the key 200. The cup 152 preferably includes axial slots 161 that can allow power to transmit through the cup 152.
The data coil 154 is located towards the upper edge of the cup 152 and, preferably, lies just rearward of the forward lip of the cup 152. The data coil 154 is generally of a torus shape and can cooperate with a data coil of the key 200, as is described in greater detail below. Two wires 160 extend from the cup 152, through a passage 162, and into the lock cartridge 106. The wires 160 preferably transmit data and power from the data and power mating portion 146 to the solenoid 126 and the circuit board 134.
The power coil 156 is preferably aligned with a longitudinal axis of the lock 100 so that a longitudinal axis passing through the power coil 156 is substantially parallel (or coaxial) with a longitudinal axis of the lock 100. The data coil 154 is preferably arranged to generally lie in a plane that is orthogonal to a longitudinal axis of the lock. Such an arrangement helps to reduce magnetic interference between the transmission of power between the lock 100 and the key 200 and the transmission of data between the lock 100 and the key 200.
As described above, the lock cylinder 104 can support a lock tab, which interacts with a stop to inhibit opening of a cabinet drawer or door, or prevent relative movement of other structures that are secured by the lock and key system 10. The lock cylinder 104 includes a lock tab portion 164 that can support a lock tab in a rotationally fixed manner relative to the lock cylinder 104. The lock tab portion 164 includes a flatted portion 166 and a threaded portion 168. The flatted portion 166 can receive a lock tab (not shown) which can slide over lock tab portion 164 and mate with the flatted portion 166. One or more flat surfaces, or “flats,” on the flatted portion 166 can allow the transmission of torque from the cylinder 104 to the lock tab (not shown). The threaded portion 168 can receive a nut (not shown), which can secure the lock tab (not shown) to the cylinder 104.
The key 200 includes an elongate main body section 204 that is generally rectangular in cross-sectional shape. The key 200 also includes a nose section 202 of smaller external dimensions than the body section 204. An end section 206 closes and end portion of the body section 204 opposite the nose section 202. The nose section 202 can engage the lock 100 and the body section 204 can house the internal electronics of the key 200 as well as other desirable components. The end section 206 is removable from the body section 204 to permit access to the interior of the body section 204.
With continued reference to
On the outer surface of the cylindrical portion are two radiused tabs 214 which can rotationally locate the key 200 relative to the lock 100 prior to the key 200 engaging the lock 100. The tabs 214 extend radially outward from the outer surface of the cylindrical portion 210 and, preferably, oppose one another.
The cylindrical portion 210 further includes two generally rectangular extensions 216 that extend axially outward and can engage with the recesses 150 of the lock 100 (
The cylindrical portion 210 includes a recess 218 that opens to the front of the key 200. Located within the recess 218 is the power and data transfer portion 212 of the key 200. Preferably, the power and data transfer portion 212 is generally centrally located within the recess 218 and aligned with the longitudinal axis of the key 200. The power and data transfer portion 212 includes a power coil 220 and a data coil 222. The power coil 220 is generally cylindrical in shape with a slight taper along its axis. The power coil 220 is positioned forward of the data coil 222 and, preferably, remains within the recess 218 of the cylindrical portion 210. The power coil 220 can be inductively coupled with the power coil 152 of the lock 100. The data coil 222 is generally toroidal in shape and is located at the base of the recess 218. The data coil 222 can be inductively coupled with the data coil 154 of the lock 100, as is described in greater detail below.
With continued reference to
The body section 204 includes three externally-accessible input buttons 228 extending from the body section 204 (upward in the orientation of
With reference to
With reference to
Furthermore, when the key 200 engages the lock 100, the cylindrical extension 148 of the lock 100 is received within the recess 218 of the key. The recess 218 is defined by a tapered surface which closely matches a tapered outer surface of the cylindrical extension 148. The cooperating tapered surfaces facilitate smooth engagement of the lock 100 and key 200, while also ensuring proper alignment between the lock 100 and key 200. Furthermore, the rectangular extensions 216 of the key 200 insert into the recesses 150 of the lock 100 to positively engage the key 200 with the lock 100 so that rotation of the key 200 results in rotation of the lock cylinder 104 within the housing 102.
When the key 200 engages the lock 100, the power coil 220 of the key 200 is aligned for inductive coupling with the power coil 156 of the lock 100. Also, the data coil 222 of the key 200 is aligned for inductive coupling with the data coil 154 of the lock 100. Preferably, the power coil 220 of the key 200 is inserted into the cup portion 152 of the lock 100 and thus the power coil 156 of the lock 100 and the power coil 220 of the key 200 at least partially overlap along the longitudinal axis of the lock 100 and/or key 200. Furthermore, preferably, the data coil 154 of the lock 100 and the data coil 222 of the key 200 come into sufficient alignment for inductive coupling when the key 200 engages the lock 100. That is, in the illustrated arrangement, when the key 200 engages the lock 100, the data coil 222 of the key 200 and the data coil 154 of the lock 100 are positioned adjacent one another and, desirably, are substantially coaxial with one another. Furthermore, a plane which passes through the data coil 222 of the key 200 preferably is substantially parallel to a plane which passes through the data coil 154 of the lock 100. Desirably, the spacing between the data coils 154 and 222 is within a range of about 30-40 mils (or 0.03-0.04 inches). Such an arrangement is beneficial to reduce interference between the power transfer and the data transfer between the lock 100 and key 200, as is described in greater detail below. However, in other arrangements, a greater or lesser amount of spacing may be desirable.
In the illustrated embodiment of the lock and key system 10, when the key 200 engages the lock 100 there are two transfers that occur. The first transfer is a transfer of data and the second transfer is a transfer of power. During engagement of the key 200 and the lock 100, the data coils 222 and 154, in the illustrated embodiments, do not come into physical contact with one another. Similarly, the power coil 200 of the key 200 and power coil 156 of the lock 100, in the illustrated embodiment, do not come into physical contact with one another. The data is preferably transferred between the data coil 222 of the key 200 and the data coil 154 of the lock 100 by induction, as described in connection with
The power coil 402 of certain embodiments is a solenoid. The solenoid includes windings 420 which are loops of wire that are wound tightly into a cylindrical shape. In the depicted embodiment, the power coil 402 includes two sets of windings 420. Two sets of windings 420 in the power coil 402 reduce air gaps between the wires and thereby increase the strength of a magnetic field generated by the power coil 402.
The depicted embodiment of the power coil 402 does not include a magnetic core material, such as an iron core, although in certain embodiments, a magnetic core material may be included in the power coil 402. In other embodiments, while the power coil 402 is depicted as a solenoid, other forms of coils other than solenoids may be used.
The power coil 402 may form a portion of a lock assembly, though not shown, such as any of the lock assemblies described above. Alternatively, the power coil 402 may be connected to a key assembly, such as any of the key assemblies described above. In addition, the power coil 402 may be connected to a docking station (not shown), as described in connection with
The power coil 402 is shown having a width 414 (also denoted as “WP”). The width 414 of the power coil 402 is slightly flared for the entire length of the power coil 402. The overall shape of the power coil 402, including its width 414, determines in part the shape of the magnetic field emanating from the power coil 402. In certain embodiments, a constant or approximately constant width 414 of the power coil 402 does not change the shape of the power magnetic field 404 substantially from the shape illustrated in
The power coil 402 further includes a casing 462 surrounding the power coil 402. In one embodiment, the casing 462 is a non-conducting material (dielectric). The casing 462 of certain embodiments facilitates the power coil 402 receiving the interior power coil 418 inside the power coil 402. The casing 462 prevents electrical contact between the power coil 402 and the interior power coil 418. Thus, in the embodiment described with reference to
In alternative embodiments, the casing 462 is made of a metal, such as steel. The strength of a metal casing 462 such as steel helps prevent tampering with the power coil 402. However, magnetic fields often cannot penetrate more than a few layers of steel and other metals. Therefore, the metal casing 462 of certain embodiments includes one or more slits or other openings (not shown) to allow magnetic fields to pass between the power coil 402 and the interior power coil 418.
The interior power coil 418 mates with the power coil 402 by fitting inside the power coil 402. In certain embodiments, the interior power coil 418 has similar characteristics to the power coil 402. For instance, the interior power coil 418 in the depicted embodiment is a solenoid with two windings 420. In addition, the interior power coil 418 may receive a current and thereby generate a magnetic field. The interior power coil 418 is also covered in a casing material 454, which may be an insulator or metal conductor, to facilitate mating with the power coil 402. Furthermore, the interior power coil 418 also has a width 430 (also denoted “Wi”) that is less than the width 414 of the power coil 402, thereby allowing the interior power coil 418 to mate with the power coil 402.
In addition to these features, the interior power coil 418 of certain embodiments includes a ferromagnetic core 452, which may be a steel, iron, or other metallic core. The ferromagnetic core 452 increases the strength of the power magnetic field 404, enabling a more efficient power transfer between the interior power coil 418 and the power coil 402. In addition, the ferromagnetic core 452 in certain embodiments enables the frequency of the power signal to be reduced, allowing a processor in communication with the power coil 418 to operate at a lower frequency and thereby decrease the cost of the processor.
The interior power coil 418 may form a portion of a lock assembly, though not shown, such as any of the lock assemblies described above. Alternatively, the interior power coil 418 may be connected to a key assembly, such as any of the key assemblies described above. In addition, the interior power coil 418 may be connected to a docking station (not shown), as described in connection with
A changing current flow through the interior power coil 418 induces a changing magnetic field. This magnetic field, by changing with respect to time, induces a changing current flow through the power coil 402. The changing current flow through the power coil 402 further induces a magnetic field. These two magnetic fields combine to form the power magnetic field 404. In such a state, the power coil 402 and the interior power coil 418 are “inductively coupled,” which means that a transfer of energy from one coil to the other occurs through a shared magnetic field, e.g., the power magnetic field 402. Inductive coupling may also occur by sending a changing current flow through the power coil 402, which induces a magnetic field that in turn induces current flow through the interior power coil 418. Consequently, inductive coupling may be initiated by either power coil.
Inductive coupling allows the interior power coil 418 to transfer power to the power coil 402 (and vice versa). An alternating current (AC) signal flowing through the interior power coil 418 is communicated to the power coil 402 through the power magnetic field 404. The power magnetic field 404 generates an identical or substantially identical AC signal in the power coil 402. Consequently, power is transferred between the interior power coil 418 and the power coil 402, even though the coils are not in electrical contact with one another.
In certain embodiments, the interior power coil 418 has fewer windings than the power coil 402. A voltage signal in the interior power coil 418 is therefore amplified in the power coil 402, according to known physical relationships in the art. Likewise, a voltage signal in the power coil 402 is reduced or attenuated in the interior power coil 418. In addition, the power coil 402 may have fewer windings than the interior power coil 418, such that a voltage signal from the interior power coil 418 to the power coil 402 is attenuated, and a voltage signal from the power coil 402 to the interior power coil 418 is amplified.
The power magnetic field 404 is shown in the depicted embodiment as field lines 434; however, the depiction of the power magnetic field 404 with field lines 434 is a model or representation of actual magnetic fields, which in some embodiments are changing with respect to time. Therefore, the power magnetic field 404 in certain embodiments is depicted at a moment in time. Moreover, the depicted model of the power magnetic field 404 includes a small number of field lines 434 for clarity, but in general the power magnetic field 404 fills all or substantially all of the space depicted in
Portions of the field lines 434 of the power magnetic field 404 on the outside of the power coil 402 are parallel or substantially parallel to the axis of the power coil 402. The parallel nature of these field lines 434 in certain embodiments facilitates minimizing interference between power and data transfer, as is described below.
The first data coil 406 is connected to the power coil 402 by the casing 462. The first data coil 406 has one or more windings 422. In one embodiment, the first data coil 406 is a toroid including tightly-wound windings 422 around a ferromagnetic core 472, such as steel or iron. The ferromagnetic core 472 of certain embodiments increases the strength of a magnetic field generated by the first data coil 406, thereby allowing more efficient transfer of data through the data magnetic field 410. In addition, the ferromagnetic core 472 in certain embodiments enables the frequency of the data signal to be reduced, allowing a processor in communication with the first data coil 406 to operate at a lower frequency and thereby decreasing the cost of the processor.
Though not shown, the first data coil 406 may further include an insulation material surrounding the first data coil 406. Such insulation material may be a non-conducting material (dielectric). In addition, the casing 462 covering the power coil 402 in certain embodiments also at least partially covers the first data coil 406, as shown. The casing 462 at the boundary between the first data coil 406 and the second data coil 408 may also include a slit or other opening to allow magnetic fields to pass between the first and second data coils 406, 408.
The first data coil 406 has a width 416 (also denoted as “Wd”). This width 416 is greater than the width 414 of the power coil 402 in some implementations. In alternative embodiments, the width 416 may be equal to or less than the width 414 of the power coil 402.
The second data coil 408 in the depicted embodiment is substantially identical to the first data coil 406. In particular, the second data coil 408 is a toroid including tightly-wound windings 424 around a ferromagnetic core 474, such as steel or iron. The ferromagnetic core 474 of certain embodiments increases the strength of a magnetic field generated by the second data coil 408, thereby allowing more efficient transfer of data through the data magnetic field 410, allowing a processor in communication with the second data coil 408 to operate at a lower frequency and thereby decreasing the cost of the processor.
The second data coil 408 in the depicted embodiment has a width 416 equal to the width 414 of the first data coil 406. In addition, the second data coil 408 may have an insulating layer (not shown) and may be covered by the casing 454, as shown. However, in certain embodiments, the second data coil 408 has different characteristics from the first data coil 406, such as a different number of windings 424 or a different width 416. In addition, first and second data coils 406, 408 having different widths may overlap in various ways.
When a current is transmitted through either the first data coil 406 or the second data coil 408, the first data coil 406 and the second data coil 408 are inductively coupled, in a similar manner to the inductive coupling of the power coil 402 and the interior power coil 418. Data in the form of voltage or current signals may therefore be communicated between the first data coil 406 and the second data coil 408. In certain embodiments, data may be communicated in both directions. That is, either the first or second data coil 406, 408 may initiate communications. In addition, during one communication session, the first and second data coils 406, 408 may alternate transmitting data and receiving data.
Data magnetic field 410 is depicted as including field lines 442, a portion of which are orthogonal or substantially orthogonal to the data coils 406, 408 along their width 416. Like the field lines 434, 436 of the power magnetic field 404, the field lines 442 of the data magnetic field 410 are a model of actual magnetic fields that may be changing in time. The orthogonal nature of these field lines 442 in certain embodiments facilitates minimizing the interference between power and data transfer.
In various embodiments, at least a portion of the data magnetic field 410 is orthogonal to or substantially orthogonal to the power magnetic field 404 at certain areas of orthogonality. These areas of orthogonality include portions of an interface 412 between the first data coil 406 and the second data coil 408. This interface 412 in certain embodiments is an annular or circumferential region between the first data coil 406 and second data coil 408. At this interface, at least a portion of the data magnetic field 410 is substantially parallel to the first data coil 406 and second data coil 408. Because the data magnetic field 410 is substantially parallel to the data coils 406, 408, the data magnetic field 410 is therefore substantially orthogonal to the power magnetic field 404 at portions of the interface 412.
According to known relationships in the physics of magnetic fields, magnetic fields which are orthogonal to each other have very little effect on each other. Thus, the power magnetic field 404 at the interface 412 has very little effect on the data magnetic field 410. Consequently, the data coils 406 and 408 can communicate with each other with minimal interference from the potentially strong power magnetic field 404. In addition, data transmitted between the data coils 406, 408 does not interfere or minimally interferes with the power magnetic field 404. Thus, data may be sent across the data coils 406, 408 simultaneously while power is being sent between the power coil 402 and the interior power coil 418.
The key circuit 510 includes a processor 502. The processor 502 may be a microprocessor, a central processing unit (CPU), a microcontroller, or other type of processor. The processor 502 in certain embodiments implements program code. By implementing program code, the processor 502 sends certain signals to the lock circuit 530 and receives signals from the lock circuit 530. Such signals may include power signals, data signals, and the like.
A memory device 526 is in communication with the processor 502. The memory device 526 in certain embodiments is a flash memory, hard disk storage, an EEPROM, or other form of storage. The memory device 526 in certain embodiments stores program code to be run on the processor 502. In addition, the memory device 526 may store data received from the processor 502.
Data stored on the memory device 526 may include encryption data. In one embodiment, the encryption data includes one or more encryption keys that when communicated to the lock circuit 530 effectuate unlocking a lock. Several different encryption schemes may be used in various embodiments.
Data stored by the memory device 526 may also include audit data. Audit data in some implementations is data received from the lock circuit 530 or generated by the key circuit 510 that identifies past transactions that have occurred between the lock and other keys. For instance, audit data may include ID numbers of keys used to access the lock, including keys which unsuccessfully used the lock. This data allows security personnel to monitor which individuals have attempted to access the lock. The audit data may further include several other types of information.
A data coil 512 is in communication with the processor 502 through conductors 504 and 506. The data coil 512 may be any of the data coils described above. The data coil 512 in certain embodiments receives data from the processor 502. This data may be in the form of a voltage or current signal which changes with respect to time, such that certain changes in the signal represent different symbols or encoded information. Because the signal changes with respect to time, a magnetic field is generated in the data coil 512 which induces a magnetic field in a corresponding data coil 532 in the lock circuit 530. The magnetic field in the data coil 532 further induces a voltage or current signal, which contains the same information or substantially the same information as the voltage or current signal generated in the data coil 512. Thus, the data coil 512 facilitates communication between the key circuit 510 and the lock circuit 530.
In certain embodiments, the data coil 512 receives data in a like manner from the data coil 532 of the lock circuit 530. A voltage or current signal induced in the data coil 512 is sent to the processor 502, which processes the information conveyed in the voltage or current signal. The data coil 512 may also send and receive information to and from a docking station (not shown), which is described more fully below.
One or more switches 516 are in communication with the data coil 512 and with the processor 502. The switches 516 in certain embodiments are transistor switches, relays, or other forms of electronic switches which selectively direct current flow to different parts of the key circuit 510. In the depicted embodiment, switches 516 direct current flow between the data coil 512 and the processor 502. The switches 516 therefore selectively allow the processor 502 to both send and receive data.
A power coil 514 is in communication with the processor 502 via conductors 508 and 510. The power coil 514 in certain embodiments transmits power to the key circuit 530. In certain implementations, the power coil 514 may be any of the power coils described above. In one implementation, the power coil 514 receives an alternating current (AC) signal. This AC signal induces a magnetic field in a corresponding power coil 534 in the lock circuit 530. In one embodiment, the AC signal oscillates at an appropriate frequency to effectuate optimal power transfer between the key circuit 510 and the lock circuit 530. For example, the oscillation may occur at 200 kilohertz. Alternatively, the oscillation may occur at a different frequency which may be chosen so as to minimize interference with other circuit components.
One or more switches 518 are in communication with the power coil 514 and a processor 502. Like the switches 516, the switches 518 may be transistor switches, relays or any other form of electronic switch. The switches 518 in certain embodiments allow power to be transmitted to the power coil 514 from the processor 502. In such embodiments, the switches 518 are closed, allowing current to transfer from the processor 502 to the power coil 514. The switches 518 may be opened when the power coil 514 is receiving power such as from a docking station. When the switches 518 are open, power received from the power coil 514 in certain embodiments cannot be transmitted to the processor 502. The switches 518 therefore protect the processor 502 from receiving harmful current signals while simultaneously allowing the processor 502 to transmit power to the power coil 514.
A rectifier circuit 520 is in communication with the power coil 514 via conductors 508 and 510. The rectifier circuit 520 in certain embodiments includes one or more diodes. The diodes may form a bridge rectifier or other form of rectifier. The diodes of the rectifier circuit 520 rectify an incoming signal from the power coil 514. Rectification in certain embodiments includes transforming an alternating current signal into a direct current signal by converting the AC signal into one of constant polarity. Rectification may further include smoothing the signal, for example, by using one or more capacitors, and thereby creating a direct current signal that can power circuit components.
A recharge circuit 522 is in communication with the rectifier 520. The recharge circuit 522 in certain embodiments recharges a battery 524 when the key circuit 510 is in communication with a docking station (not shown). The battery 524 may be a lithium iron battery, a nickel cadmium battery or other form of rechargeable battery. The battery may also be an alkaline or other non-rechargeable battery. In addition, the battery 524 may include multiple batteries. In one embodiment, the battery 524 receives power from the recharge circuit 522 in order to recharge the battery. In addition, the battery 524 sends power to the processor 502, to the memory device 526, and to other components in the key circuit 530.
In some implementations, the key circuit 510 is capable of communicating with a docking station (not shown) connected to an AC power supply, such as a wall outlet. The docking station in one embodiment has a power coil and a data coil, similar to a power coil 534 and data coil 532 of the lock circuit 530 described below. The docking station receives the data coil 512 and the power coil 514 such that the key circuit 510 can communicate with the docking station. In one embodiment, the power coil 514 receives power from the docking station and transfers this power to the rectifier 520 and recharge circuit 522, effectuating recharge of the battery 524.
In addition, the data coil 512 may receive data from a corresponding data coil in the docking station. Such information might include, for example, program code to be stored on the memory device 526, program code to be run on the processor 502, data to be stored in the memory device 526 including encryption data, data regarding locking codes and the like, as well as ID data, tracking data, and the like. In addition, the docking station may transmit data, codes, or the like to the key circuit 510 which enable the key to be used for a limited time, such as a couple of hours or days. The data coil 512 may also transmit data to the docking station via a corresponding data coil. Such data might also include audit information, tracking information, and the like.
The docking station may also be connected to a computer. Programs can be run on the computer which facilitate the docking station communicating with the key circuit 510. Consequently, the key circuit 510 may be recharged and reprogrammed by the docking station of certain embodiments.
Turning to the lock circuit 530, the lock circuit 530 includes a processor 546. Like the processor 502 of the key circuit 510, the processor 546 may be a microprocessor, a central processing unit (CPU), or any other type of processor. The processor 546 in certain embodiments implements program code. By implementing program code, the processor 546 may send certain signals to the key circuit 510 and receive signals from the key circuit 510. Such signals may include power signals, data signals, and the like.
A memory device 548 is in communication with the processor 546. The memory device 548 in certain embodiments is a flash memory, hard disk storage, an EEPROM, or other form of storage. The memory device 548 in certain embodiments stores program code to be run on the processor 546. In addition, the memory device 548 may store data received from the processor 546.
Data stored on the memory device 548 may include encryption data. In one embodiment, the encryption data includes one or more encryption keys. When an identical encryption key is received from a key circuit 510 in certain embodiments, the lock circuit 530 unlocks a lock. The memory device 548 may also include audit data. This data allows security personnel to monitor which individuals have attempted to access the lock.
A data coil 532 is in communication with the processor 546 through conductors 536 and 538. The data coil 532 may be any of the data coils described above. The data coil 532 in certain embodiments receives data from the processor 546 and transmits the data to the key circuit 510. In other embodiments, the data coil 532 receives data from the key circuit 510 via magnetic fields generated by the data coil 512.
One or more switches 544 are in communication with the data coil 532 and with the processor 546. The switches 544 in certain embodiments are transistor switches, relays, or other forms of electronic switches which selectively direct current flow to different parts of the key circuit 530. In the depicted embodiment, switches 544 may be used to direct current flow between the data coil 532 and the processor 546. Like the switches 516 in the key circuit 510, the switches 544 selectively allow the processor 502 to both send and receive data.
A power converter 550 is in communication with the processor 546 and with the power coil 534. The power converter 550 in one embodiment includes a rectifier circuit such as the rectifier circuit 528 described above. The power converter 550 may further include a low drop-out regulator (described in connection with
In one embodiment, the power converter 550 receives an oscillating power signal from the power coil 534. The power converter 550 includes a rectifier circuit, similar to the rectifier circuit 520 described above, which converts the oscillating signal into two components, namely an AC component signal and a direct current (DC) component signal. In one embodiment, the AC component signal is provided to a solenoid 552 through conductor 574, and the DC component signal is provided to the processor 546 through conductor 572. Consequently, the power converter 550 enables the lock circuit 530 to run on both AC and DC power.
The solenoid 552 receives the AC component signal from the power converter 550. The solenoid 552 in one embodiment is a coil containing one or more windings. The solenoid 552, upon receiving current from the power converter 550, generates a magnetic field to actuate an unlocking mechanism in a lock, in a manner similar to that which is described above.
A switch 554 is in communication with the solenoid 552 through a conductor 576. The switch 554 is also in communication with the processor 546 through a conductor 580. In addition, the switch 554 is in communication with ground 578. The switch 554 enables or disables the solenoid 552 from receiving current, thereby causing the solenoid 552 to lock or unlock. In one embodiment, the processor 546 sends a signal through the conductor 580 to the switch 554 that closes the switch 554 and thereby creates a conduction path from the solenoid 552 to ground 578. With the switch closed 554, the solenoid 552 is able to receive current from the power converter 550 and thereby effectuate unlocking. At other times, the processor 546 will not send a signal 580 to the switch 554 and thereby cause the switch to be open, preventing current from flowing through the solenoid 552 and thereby locking the lock. Alternatively, the processor 546 can send a signal over the signal line 580 to the switch 554 which will cause the switch to remain open.
While not shown, in certain embodiments the lock circuit 530 includes a battery in addition to, or in place of, the battery 524 in the key circuit 500. In such instances, the lock circuit 530 may provide power to the key circuit 510. This power may recharge the battery 524. Alternatively, if the key circuit 510 does not have a battery 524, power transmitted from the battery in the lock circuit 530 may power the key circuit 510.
A processor 602 in the key circuit 600 is in communication with a memory device 626, similar to the processor 502 and the memory device 526 of the key circuit 510. In the depicted embodiment, the processor 602 is a microcontroller and the memory device 626 is a flash memory device. While the processor 602 and the memory device 626 are shown on both
A data coil 612, shown in
Transistors 616 are depicted as switches in
Various encoding schemes may be used to transmit and receive data. For example, a Manchester encoding scheme may be used, where each bit of data is represented by at least one voltage transition. Alternatively, a pulse-width modulation scheme may be employed, where a signal's duty cycle is modified to represent bits of data. Using different encoding schemes may allow the key circuit 600 to contain fewer components. For example, when a pulse-width modulation scheme is used, such as in
A power coil 614 is in communication with the processor 604 through conductors 608 and 610 (see
In the depicted embodiment, the processor 602 generates two oscillating signals which are provided to the power coil 614. In the depicted embodiment, the oscillating power signals oscillate at 200 kHz (kilohertz). The relative high frequency of the power signal in certain embodiments facilitates improved rectification of the power signal and therefore a more efficient power transfer. In alternative embodiments other frequencies may be chosen without departing from the scope of the inventions described herein.
In one embodiment, the power signals sent over power coil 614 oscillate at a higher frequency than the data signals sent over the data coil 612. When the power signals oscillate at a higher frequency than the data signals, interference between power and data signals is further minimized, e.g., the signal-to-noise ratio (SNR) is improved. In one embodiment, significant SNR improvements occur when the power signal frequency is greater than 10 times the data signal frequency.
Diodes 620 are in communication with the power coil 614 through conductors 608 and 610. The diodes 620 in the depicted embodiment form a rectifier circuit, similar to the rectifier circuit 520 of
The voltage Vpp 682 is provided to a recharge circuit 622 (see
In the lock circuit 700, a data coil 732 is in communication with the processor 746 through conductors 736 and 738. The data coil 732 in the depicted embodiment is a coil or solenoid which has a value of inductance. In one embodiment, the inductance of the data coil 732 is 100 μH (micro-Henries). The data coil 732 receives data from and sends data to the data coil 612 of the key circuit 600.
In one embodiment, data provided by the key circuit 600 and received by the data coil 732 provides a clock signal to the processor 746, enabling the processor 746 to be synchronized or substantially synchronized with the processor 602 of the key circuit 600. The clock signal may be provided, for example, when a Manchester encoding scheme is used to transmit the data. In certain embodiments, this external clock signal removes the need for a crystal oscillator in the lock circuit 700, thereby reducing the number of components and therefore the size of the lock circuit 700.
Transistors 744 are depicted as switches. Similar to the switches 544, the transistors 744 selectively direct current flow between the data coil 732 and the processor 746. Control signals sent on conductor 782 from the processor 746 control the transistors 744, selectively allowing current to flow through the transistors 744.
A power coil 734 is in communication with the processor 746 through conductors 740 and 742. In one embodiment, the inductance of the power coil 734 is 10 pH (micro-Henries). Like the power coil 532 of
Power conversion circuit 750 includes diodes 720, a capacitor 790, and a low-dropout regulator 760. The diodes 720 of the power conversion circuit 750 form a rectifier circuit. The depicted configuration of the diodes 720 constitutes a bridge rectifier, or full wave rectifier. When the diodes 720 receive an AC voltage signal from the power coil 734, the diodes 720 of the bridge rectifier full-wave rectify the AC voltage signal. This full-wave rectified signal in certain embodiments still contains a changing voltage signal with respect to time, but the voltage signal has a single polarity (e.g., the entire voltage signal is positive). This full-wave rectified signal is provided as voltage Vcc 784 to a solenoid 752.
The capacitor 790 converts the full-wave rectified signal into DC form and provides the DC signal to the low-dropout regulator 760. The low-dropout regulator 760 stabilizes the signal to a voltage Vdd 772, which is provided to various components in the lock circuit 700, including the processor 746. Consequently, the power conversion circuit 750 provides a changing or AC voltage Vcc 784 to the solenoid 752 and a DC voltage Vdd 772 to various circuit components.
The solenoid 752 receives the voltage Vcc 784 from the power converter 750. The solenoid 752 in one embodiment is a coil containing one or more windings. The solenoid 752, upon receiving the voltage Vcc 784 from the power converter 550, generates a magnetic field to actuate an unlocking mechanism in a lock, in a manner similar to that which is described above.
A transistor 754 is in communication with the solenoid 752. The transistor 754 is also in communication with the processor 746 through a conductor 780. In addition, the transistor 754 is in communication with ground 778. In certain embodiments, the transistor 754 acts as a switch to enable or disable the solenoid 752 from receiving current, thereby causing the solenoid 752 to lock or unlock the locking device. In one embodiment, the processor 746 sends a signal through the conductor 780 to the transistor 754 that sends current through the transistor 754 and thereby creates a conduction path from the solenoid 752 to ground 778. With the transistor 754 in this state, the solenoid 752 is able to receive current from the voltage Vcc 784 and thereby effectuate unlocking. However, at other times, the processor 746 will not send a signal 780 to the transistor 754, such as when the processor 746 did not receive a correct unlocking code. In such case, the processor 746 causes the transistor 754 to remain open, thereby preventing current from flowing through the solenoid.
In the depicted embodiment, circuit components 860, 872, and 874 in conjunction with a processor provide circuitry for a pulse-modulation data-encoding scheme. During transmission of data from the key circuit 800, transistor switches 860 are selectively switched on and off to pulse a data signal to a data coil. When the key circuit 800 is receiving data, the comparator 872 receives the data voltage signal from the data coil.
The comparator 872 is used to convert the data voltage signal into a two-bit digital signal which is sent to a processor via data input line 880. In addition, the comparator 872 (or an operational amplifier used as a comparator) may be used to amplify the voltage signal to a level appropriate for a processor to manipulate.
A feedback resistor 874 provides positive feedback to the comparator 872, such that the comparator 872 attenuates small voltage signals and amplifies large voltage signals. By attenuating and amplifying small and large voltage signals respectively, the comparator 872 and feedback resistor 874 reduce the oscillatory effects of noise on the comparator 872. Thus, wrong-bit detection errors are reduced. In alternative embodiments, a Schmitt trigger integrated circuit may be employed in place of the comparator 872 and the resistor 874.
The cartridge 106 described above includes, in certain embodiments, a single solenoid 122 used for movement of the slide bars 128 (see, e.g.,
Keeping the slide bars 128 spaced from the solenoid 122 may also expend current. As the slide bars 128 move farther from the solenoid 122, the magnetic field loses intensity because the field strength of a magnet can decrease proportionally to 1/r3, where r is the distance from the face of the magnet. As a result, the farther the slide bars 128 are from the solenoid 122, the more current may be expended to keep the slide bars 128 spaced from the solenoid 122.
Conversely, the smaller r is, the stronger the magnetic field strength can be. Thus, in certain embodiments, one or more holding coils may be provided to assist the solenoid 122 with moving and/or holding the slide bars 128 (see
Turning to
The coil assembly 900 may be used in conjunction with some or all of the lock assemblies described above. For example, the coil assembly 900 can be used in the lock 100 described above in place of one or more of the cartridge 106, solenoid 126, and slide bars 128, among possibly other things. Alternatively, the coil assembly 900 may be used in a different lock assembly. One embodiment of a lock assembly that could use the coil assembly 900 is described below with respect to
Referring specifically to
Each of the coils 922, 940a, 940b includes one or more windings of wire wrapped around the cartridge 906. The holding coils 940a, 940b are spaced from the primary coil 922 in the depicted embodiment. Other configurations than shown may be used, such as wires wrapped partially around the cartridge 906. Also not shown, but which may be included, are connections to a circuit for controlling the coils 922, 940a, 940b. An example circuit for controlling the coils 922, 940a, 940b is described below with respect to
The cartridge 906 includes a body portion 908 and extension receiving portions 920. The body portion 908 preferably is cylindrical or substantially cylindrical. The extension receiving portions 920 protrude from the body portion 908 and are likewise preferably cylindrical or substantially cylindrical. Non-cylindrical configurations of the body and extension receiving portions 908, 920 may be used in other embodiments. The extension receiving portions 920 may be used to receive extensions of a locking mechanism (see, e.g.,
Referring to
In an implementation, the primary coil may have an inductance of about 15 pH without the core 950. Addition of the iron core 950 may increase this inductance by orders of magnitude, such as 500 times or more. The inductance of the holding coils 940a, 940b may be, in one implementation, about 8 to 10 μH. However, the inductance values provided here are mere examples. The inductance characteristics of the various coils 922, 940a,940b may vary widely depending on, among other things, the size of the coils 922,940a, 940b.
The slide bars 928a, 928b may include a magnetic material, such as neodymium, powdered metal, steel, iron, an alloy, combinations of the same, or the like. In an embodiment, the slide bars 928a, 928b include all the features of the slide bars 128 described above. The slide bars 928a, 928b may move slidably along or within some or all inner surfaces 912a, 912b of the body portion 908, respectively. For example, the slide bars 928a, 928b may slide away from the core 950 in response to excitation of the primary coil 922 and/or excitation of the holding coils 940a, 940b. The slide bars 928a, 928b may come to rest against outer walls 954a, 954b of the body portion 908. Likewise, the slide bars 928a, 928b may slide toward the core 950 in response to reduced or no excitation of the primary coil 922 and/or holding coils 940a, 940b. The slide bars 928a, 928b may come to rest against inner walls 952a, 952b on each side of the core 950, which greatly reduces the likelihood of the slide bars 928a, 928b actually touching the core 950. However, the walls 952a, 952b and 954a, 954b might not be provided in other embodiments. In some embodiments, the walls 952a, 952b and 954a, 954b are solid. In some embodiments one or more of the walls 952a, 952b and 954a, 954b may comprise openings or apertures or the like.
In the depicted embodiment, the slide bars 928a, 928b are each about the same length as the length of the holding coils 940a, 940b. In certain embodiments, this common length between the slide bars 928a, 928b and the holding coils 940a, 940b may result in the holding coils having a desired holding strength. If the lengths of the holding coils 940a, 940b and the slide bars 928a, 928b do not match, more current might be used by the holding coils 940a, 940b to assist with moving and/or holding the slide bars 928a, 928b. However, other configurations of the slide bars 928a, 928b and holding coils 940a, 940b may be used, including configurations where the lengths are different.
Moreover, many variations of the coil assembly 900 may be used in other implementations. For instance, there may be one extension receiving portion 920 and one holding coil 940a, 940b. Also, more than two holding coils 940a, 940b and/or extension receiving portions 920 may be provided.
The lock assembly 1000 includes a case 924 that houses the coil assembly 900. The lock assembly 1000 also includes a locking mechanism 929, which includes a bolt 930, extensions 931 from the bolt 930, and springs 932. The bolt 930 may function in the same or similar manner as the bolt 130 described above. For example, the bolt 930 may have a chamfered lower edge (not shown) that mates with a groove of the lock (see, e.g.,
In the locked position shown in
Each holding coil 940a, 940b may be energized in certain embodiments when a corresponding slide bar 928a, 928b has passed within at least half of the axial length of the holding coil 940a, 940b. In an embodiment, the holding coils 940a, 940b are energized this way because the polarization (not shown) of each holding coil 940a, 940b can have the same orientation as the polarization of the corresponding slide bar 928a, 928b. Consequently, if the holding coils 940a, 940b were to energize before the slide bars 928a, 928b passed at least halfway within the holding coils 940a, 940b, the holding coils 940a, 940b might repel the slide bars 928a, 928b toward the core at 950.
In certain embodiments, a timer is used as a proxy to determine when the slide bars 928a, 928b have passed at least halfway through the holding coils 940a, 940b. The timer may be implemented in hardware and/or software (see
Once the holding coils 940a, 940b have energized, the magnetic field generated by the holding coils 940a, 940b can assist the slide bars 928a, 928b with moving away from the core 950 if the slide bars 928a, 928b have not been moved a sufficient distance toward the outer walls 954a, 954b to allow passage of the corresponding extensions 931. Additionally, the holding coils 940a, 940b can hold the slide bars 928a, 928b in a resting or substantially resting position, as shown in
The primary coil 922 may be deactivated in response to the holding coils 940a, 940b being energized. For example, a control circuit (see
In certain embodiments, the distance r from the slide bars 928a, 928b and the energized primary coil 922 is reduced. In other words, because the holding coils 940a, 940b may assist with moving and/or holding the slide bars 928a, 928b, the primary coil 922 does not need to push the slide bars 928a, 928b as great of a distance “r” in certain embodiments. Current may therefore be reduced by using the holding coils 940a, 940b.
To further illustrate example operation of the primary coil 922 and holding coils 940a, 940b,
The magnetic fields include slide bar fields 1010a, 1010b, a primary coil field 1020, and holding coil fields 1030a, 1030b. In the locked position of
Although the holding coil fields 1030a, 1030b are shown when the slide bars 928a, 928b have passed within the holding coils 940a, 940b, the holding coil fields 1030a, 1030b may also be present when the slide bars 928a, 928b are moving toward the holding coils 928a, 928b.
The control circuit 1100 includes a primary coil 1122 and holding coils 1140a, 1140b. The primary coil 1122 is in communication with a switch 1112. Likewise, the holding coils 1140a, 1140b are in communication with a switch 1118. A second switch may be provided in some implementations so that each holding coil is in communication with a separate switch. The switches 1112, 1118 may include transistors, such as MOSFETs or the like. A processor 1102 controls both the switch 1112 and the switch 1118. The processor 1102 may be, for example, the same processor as the processor 502 described above.
The processor 1102 may include software and/or firmware for controlling the switches 1112, 1118. For instance, the processor 1102 may include a timer and associated logic for determining a sequence and/or duration for actuating the switches 1112, 1118. The processor 1102 may selectively actuate the switches 1112, 1118 in response to instructions received from an electronic key, such as the key of
In response to the switch 1112 being actuated, power from a capacitor 1116 may be provided to the primary coil 1122. The capacitor 1112 is used in some embodiments to provide a rapid burst of current. The capacitor 1116 is charged by a power supply 1114, which may receive power from the power coils described above. A tantalum capacitor 1116 may be used for its high charge to size ratio, although other types of capacitors may also be used. The primary coil 1122 may instead be powered directly by the power supply 1114 in some implementations.
The capacitor 1116 may energize the primary coil 1122 for a relatively short period of time, such as a few milliseconds or the like. As the primary coil 1122 is energized, the slide bars 928a, 928b may be repelled and move toward the holding coils, as described above. As the energy of the capacitor 1116 dissipates, or when the processor 1102 opens the switch 1122, the magnetic field generated by the primary coil 1122 may also dissipate. In response, the processor 1102 may actuate the switch 1118, causing power from the power supply 1114 (or from another capacitor) to actuate the holding coils 1140a, 1140b. After a predetermined period of time, such as two or three seconds, the processor 1102 may open the switch 1118 and deactivate the holding coils 1140a, 1140b.
In an embodiment, a capacitance value of the capacitor 1116 is selected such that the capacitor 1116 dissipates its energy in a sufficient amount of time for the primary coil 1122 to be energized. Thus, a separate timer may not be used to control the primary coil 1122.
In alternative embodiments, the processor 1102 may perform other sequences. For instance, the processor 1102 may close the switch 1118 before closing the switch 1112. Or, the processor 1102 might close both the switches 1112, 1118 at the same time, among other possible sequences.
At block 1202, a first coil positioned around a cartridge of a lock assembly is energized. The first coil may be the primary coil 922, 1122 described above. The first coil may be energized, for example, by the processor 1102 causing power from a power supply and/or capacitor to be provided to the first coil. The energizing of the first coil may generate a magnetic field.
The magnetic field from the first coil may be used at block 1204 to repel a barrier in the cartridge. The barrier can be one or more slide bars, such as the slide bars 928a, 928b described above. When magnetically attracted to a core of the cartridge (e.g., the core 950), the barrier can act to block the locking mechanism 929 from moving into the cartridge, thereby maintaining a locked position of the lock assembly.
At block 1206, a second coil positioned around the cartridge and spaced from the first coil is energized. This block 1206 may be performed by the processor 1102 causing power from a power supply and/or capacitor to be provided to the second coil. The second coil may be one of the holding coils 940a, 940b described above. Energizing of the second coil may cause a magnetic field to be generated in the second coil. The magnetic field from the second coil may be used at block 1208 to attract the barrier, such that the locking mechanism 929 that was in communication with the barrier is now allowed to move.
The process 1200 has been described in the context of a single holding coil. However, the process 1200 may also be implemented with lock assemblies that include multiple holding coils, such as two holding coils.
In some cases, an individual might attempt to break open the locks described above by applying a torque to a key when the key is mated with a lock. To reduce the chance of the lock breaking open, one or more shear pins may be provided in the key and/or in the lock. Upon application of sufficient torque, the one or more shear pins can break, allowing the key to turn freely within the lock. As a result, the shear pins can prevent or reduce the chance of the locking mechanism breaking open. In addition, the one or more shear pins may be easily replaceable.
The body portion 1302 can house the internal electronics of the key 1300 as well as other components. Advantageously, in certain embodiments, the body portion 1302 of the key 1300 is smaller than the body portion of the key 200 described above. This reduction in size may be made possible at least in part by using fewer batteries in the key 1300. Fewer batteries may be used, in certain embodiments, because the holding coils described above may reduce current usage by the lock and/or key.
The mating portion 1312 can engage a lock described below with respect to
The cylindrical portion 1310 includes a recess 1318 that opens to the front of the key 1300. Located within the recess 1318 is the power coil 1320 and data coil (not shown) described above. In addition, two shear pins 1332 are located within the recess. Each shear pin 1332 is embedded partially in a wall 1311 of the cylindrical portion 1310. The shear pins 1332 are generally cylindrical in shape. Other configurations may be possible. The shear pins 1332 are located opposite each other in the cylindrical portion 1310. Although two shear pins 1332 are shown, fewer or more shear pins may be provided in alternative embodiments.
The shear pins 1332 may assist with mating the key 1300 to a lock.
The lock 1400 includes a body portion 1404 and a mating portion 1408. The body portion 1404 may at least partly house one of the coil assemblies described above. The diameter of the mating portion 1408 is larger than the diameter of the body portion 1404.
The mating portion 1408 includes a cylinder 1446 and a raised cylindrical portion 1460 disposed within the cylinder 1446. An annular groove 1448 or key recess is formed between the cylinder 1446 and the raised cylindrical portion 1460. The annular groove 1448 is capable of receiving the tabs 1314 of the key 1300. A cup 1452 is disposed within the raised cylindrical portion 1460, which is capable of receiving the power coil 1320 of the key 1300. The raised cylindrical portion 1460 also includes shear pin slots 1462, which can receive the shear pins 1332 of the key 1300. The shear pin slots 1462 are concave in the depicted embodiment to facilitate placement of the shear pins 1332 and removal of broken shear pins. The number of shear pin slots 1462 may correspond to the number of shear pins 1332 on the key. In some embodiments, more slots may be provided than shear pins. The shear pin slots 1462 may be enclosed, rather than concave, in some embodiments.
In certain implementations, the key 1300 may mate with the lock 1400 by placement of the tabs 1314 in the annular groove 1442, by placement of the power coil 1320 in the cup 1452, and by placement of the shear pins 1332 in the shear pin slots 1462. The key 1300 may provide data to the lock 1400, allowing a locking mechanism of the lock 1400 to be actuated. The key 1300 may then be turned by an operator of the key. As the shear pins 1332 grip against the walls of the shear pin slots 1462, the shear pins 1332 may turn the raised cylindrical portion 1460, causing the locking mechanism to actuate. The tabs 1314 of the key 1300 may slide under tabs 1470 of the lock 1400. Locking may proceed, for example, by turning the key 1300 in a reverse motion.
If, however, the key 1300 does not provide suitable data to the lock 1400 (e.g., because the operator of the key 1300 does not have a suitable combination), the locking mechanism of the lock 1400 does not actuate. If the operator of the key 1300 attempts to turn the key with enough force to break the locking mechanism, the shear pins 1332 may shear instead. With the shear pins 1332 broken, turning of the key 1300 may no longer be able to turn the raised cylindrical portion 1460, thereby preventing actuating of the locking mechanism.
Further detail of the shear pins 1332 is shown in
The body portion 1404 of the lock 1400 is shown to the right of the FIGURE, and the mating portion 1408 is to the left. The lock assembly 1000, including the coil assembly 900, is included in the body portion of the lock 1400. In the depicted embodiment, the coil assembly 900 is not axially aligned with the axis of the lock 1400, unlike the lock 100 described above. Rather, the coil assembly 900 is offset from the axis. This non-axial alignment may allow a larger bolt 930 to be included in the lock 1400. In other embodiments, the coil assembly 900 may be axially aligned with the lock 1400.
The illustrated electronic lock and key assembly 2200 can use electronic circuitry coupled to the key head 2220 and/or lock 2210 portions to authenticate the key and to actuate internal mechanisms of the lock 2210. When the key portion 2220 engages the lock portion 2210, data transfer and/or power transfer may be enabled between the lock 2210 and key head 2220 portions. The lock 2210, or a cylinder portion thereof may then advantageously be actuated by the key head 2220 to move from a locked position to an unlocked position and permit access to a space or location secured by the lock 2210. In certain embodiments, as described above, the direction of power transfer is primarily from the key head portion 2220 to the lock portion 2210. However, in certain configurations, the direction of power transfer may be reversed or may occur in both directions.
The lock 2210 may be advantageously installed in a cabinet, or other such storage compartment, and can selectively secure a drawer or door of the cabinet relative to a body of the cabinet. As shown, in certain embodiments, the lock 2210 includes a head portion 2212 and a body portion 2214. While the body portion 2214 is configured to be secured within a door or drawer structure, the head portion, when the lock is installed, may be disposed externally to the door or drawer structure. Therefore, in certain embodiments, when installed or mounted to a container, the head portion 2212, or a portion thereof, may be physically accessible when the cabinet is closed. Alternatively, some or all of the head portion 2212 may be positioned internal to the door or drawer, such that the lock 2210 is flush or approximately flush with the door or drawer.
The FIGURE shows an outer housing of the lock 2210, wherein a rotatable cylinder is at least partially contained within the outer housing. A tenon portion 2216 of the cylinder may extend beyond the housing in a similar manner to embodiments disclosed above, and may be configured for insertion into a corresponding mortise portion of a door or drawer structure having similar dimensions.
The key head portion 2220 may include one or more electrical components. For example, the key head 2220 may include one or more wire windings used for inductive power and/or data transfer. Wire leads 2226 from such windings may lead to circuitry or a power source housed outside of the key head portion 2220. For example, the wires 2226 may be electrically coupled to an integrated circuit housed in a connected key body portion (not shown; see, e.g.,
The nose assembly 2401 may further include an electrically conductive tab 2670, or wire, which provides an electrical connection to a capacitive plate, or partial capacitor, disposed within the housing 2504. In certain embodiments, the tab 2670 is soldered or otherwise electrically connected to a wire or lead of the key circuit (not shown).
The realizable amount of coupling capacitance may be limited by the available area of the plate 2672 in some embodiments. Therefore, it may be desirable to increase or maximize the surface area of the plate 2672, in view of physical constraints that the housing or other components of the key head may impose. Furthermore, in the case where the area of the plate 2672 is small, it may be desirable to drive the capacitor with a substantially high voltage source, such as a source having peak or root-mean square (RMS) voltage levels greater than, for example, 10V or more. In certain embodiments, the capacitor is driven by a voltage source having a peak or RMS value of about 60V or more. The capacitive plate 2672 may have a diameter large enough to accommodate being disposed around the power coil 2850, while being compact enough to fit within a key head structure. For example, the capacitive plate 2672, or a cutout thereof may have a diameter of about 6 mm to about 8 mm, such as about 7 mm. In certain embodiments, the capacitive plate has a diameter of about 5 mm to about 9 mm, or about 4 mm to about 11 mm, or larger or smaller diameters. In an embodiment, an annulus-shaped capacitive plate includes a metal ring having an outer diameter of about 7 mm, wherein an inner cutout portion of the ring has a diameter of about 5 mm and the ring has a radial thickness of about 1 mm.
As described in greater detail above, attempted breaking of the lock 2210 through the application of sufficient rotational torque to the head portion 3108 of the lock can result in breaking of the shear pins of the key, wherein the key may not be able to actuate the locking mechanism when the pins are broken. In certain embodiments, the lock 2210 further includes a body portion 3104 and an inner cylinder portion 3102. The body portion 3104 may at least partly house the cylinder portion 3102, which may include a cartridge portion containing lock circuitry and/or locking mechanics. In certain embodiments, the diameter of the head portion 3108 is larger than the diameter of the body portion 3104.
In certain embodiments, the inner cylinder portion 3102 terminates at a front distal end with a mating portion including a cup assembly 3101 surrounded by a raised cylindrical housing 3103. An annular groove or key recess may be formed between a wall of the head portion 3108 and the raised cylindrical housing portion 3103. The annular groove may be configured to receive the mating structures 2423 of the key head 2420. The cup assembly 3101 may be configured to receive the nose portion 2401 of the key head shown in
In certain implementations, the key head 2420 may mate with the lock 2210 by placement of the tabs 2423 in the annular cutouts 3123, by placement of the nose portion 2502 (
With respect to a holding-coil implementation including a locking bolt member similar to that shown in
As certain of the electronics of the circuit board 3730 may protrude into the internal chamber cavity 2780, the circuit board 3730 may be designed in such a way as to efficiently fill voids in the chamber adjacent to the coil assembly 3790. For example, larger devices may be disposed in areas where there is more room to fit such devices. The circuit board 3730 may include relatively large capacitors 3732, for example. Such devices may be disposed in spaces between the coils, as shown. One or more of the capacitors 3732 may be used to provide current pulses to the coil assembly 3790 as described above. Other, lower-profile devices may be disposed in areas having relatively less available space. The circuit board 3730 may be in electrical communication with the capacitor 3672 shown in
The example key circuit 3920 shown includes a processor 3902. The processor 3902 may be a microprocessor, a central processing unit (CPU), a microcontroller, or other type of processor (additional examples described below). In certain embodiments, the processor 3902 implements program code to send signals to the lock circuit 3910 and/or receive signals from the lock circuit. Such signals may include power signals, data signals, and the like.
A partial capacitor 3922 is in communication with the processor 3902 through one or more conductors. The partial capacitor 3922 may be any of the partial capacitors (e.g., metal plates) described above. The partial capacitor 3922, when placed in proximity to the lock partial capacitor 3918, may form a capacitor 3972, such that communications from the processor 3902 may be passed through the capacitor 3972 to a processor 3906 in the lock circuit 3910 and vice versa. For example, the partial capacitor 3922 can receive data signals from the processor 3902. For example, such data may be communicated in the form of varying voltage or current levels, which may represent different symbols or encoded information. Thus, the partial capacitor 3922 can facilitate communication between the key circuit 3920 and the lock circuit 3910. In certain embodiments, the partial capacitor 3922 receives data in a like manner from the partial capacitor 3918 of the lock circuit 3910. In certain embodiments, the partial capacitors 3918, 3922 of the lock and key circuits are virtually tied to a common reference point or ground in order to allow for proper communication of signal levels between the two circuits. For example, parasitic capacitance formed between the power coil 3914 and the power coil 3934 may provide such a reference point during operation of the circuits.
A power coil 3914 is in communication with the processor 3902 via one or more conductors. In certain embodiments, the power coil 3914 transmits power to the key circuit 3910. The power coil 3914 may be any of the power coils described above. In one implementation, the power coil 3914 receives a time-varying electrical signal, which induces a magnetic field in a corresponding power coil 3934 in the lock circuit 3910, as described in greater detail above. Power may be provided to the power coil 3914 by a power source, such as the battery 3924.
The lock circuit 3910 includes a processor 3906. Like the processor 3902 of the key circuit 3920, the processor 3906 may be a microprocessor, a central processing unit (CPU), or any other type of processor (additional examples described below). In certain embodiments, the processor 3906 implements program code in order to send certain signals to the key circuit 3920 and/or receive signals from the key circuit 3920. Such signals may include power signals, data signals, and the like.
A partial capacitor 3918 of the lock circuit is in communication with the processor 3906 through one or more conductors. The partial capacitor 3918 may be any of the metal plate described above, such as a washer-shaped disc. In certain embodiments, the partial capacitor 3918 receives data from the processor 3906 and transmits the data to the key circuit 3920. In certain embodiments, the partial capacitor 3918 receives data from the key circuit 3920.
The lock circuit receives an oscillating power signal from the key circuit with power coil 3934. In certain embodiments, the oscillating power signal is provided to a coil or solenoid. The solenoid may use the signal to generate a magnetic field to actuate an unlocking mechanism in a lock, in a manner similar to that described above. For example, the power signal may be used to power one or more coils in a holding coil embodiment, as described above.
While not shown, in certain embodiments the lock circuit 3910 includes a battery in addition to, or in place of, the battery 3924 in the key circuit 3920. In such instances, the lock circuit 3910 may provide power to the key circuit 3920. This power may, for example, be used by the key circuit 3920 to recharge the battery 3924. Alternatively, if the key circuit 3920 does not have a battery or other power source, power transmitted from a battery in the lock circuit 3910 may power the key circuit 3920.
Although not shown in the figure, conductive lines 4001, 4002, 4021, and 4022 may be coupled to key and lock processor devices, respectively, such as the processors described above with respect to
The tri-state inverters 4012, 4032 may be configured to be set in high impedance (or high-Z) mode when the respective circuits are receiving data over the capacitor C3. Such a state may present a substantially open circuit in view of the received signal and thereby route the data signal to a comparator device 4014, 4034 in each respective circuit. In one embodiment, the lock and key circuits are in either a transmit or receive mode, but not both, at any given time. Thus, if the key circuit is transmitting data to the lock circuit, the lock circuit may be in a receive mode, and the tri-state inverter 4032 may be set to a high-Z mode (e.g., by a processor). Likewise, if the lock circuit is transmitting data to the key circuit, the key circuit may be in a receive mode, and the tri-state inverter 4012 may be set to a high-Z mode (e.g., by a processor). Each of the inverters 4012, 4032 may also default to high-Z mode unless data is being transmitted one through the inverters 4012, 4032 to the opposing circuit, in which case the processor can disable the high-Z state of the transmitting inverter. In some embodiments, the high-Z mode is enabled by default so that the processor does not need to enable high-Z mode when transmissions are received. Optionally, in other embodiments, the key and lock may operate in a full-duplex configuration instead, such that communications may be sent bidirectionally and simultaneously between the key and the lock.
In the depicted embodiment, the comparators 4014, 4024 are each coupled with a reference voltage (e.g., Vrefin1, Vrefin2). The reference voltage may provide a threshold voltage against which a received signal is compared. For example, when the received signal is greater than the reference voltage, the comparator may provide a high signal to the key processor over conductor 4001. In certain embodiments, the reference voltage level is less or equal to about 1V, such as about 0.5 V. The signal provided to the processor by the comparator, on the other hand, may be larger than 1V, and may advantageously be of a sufficient magnitude to be read and processed adequately by the processor. While certain components are described herein with respect to the key circuit shown, the lock circuit of
Various encoding schemes may be used to transmit and receive data. For example, a Manchester or NRZ encoding scheme may be used, where each bit of data is represented by at least one voltage transition. Alternatively, a pulse-width modulation scheme may be employed, where a signal's duty cycle is modified to represent bits of data. Furthermore, the circuitry shown in
A power coil 4016 is connected across an alternating voltage signal 4018, wherein the voltage signal induces a current in the coil. The alternating voltage signal may originate from a DC battery source of the key circuit that is converted into an alternating signal (e.g., using a power inverter or the like) and provided to the inductor 4016. In one embodiment, the inductance of the power coil 4016 is approximately 10 μH, although other values may be used. In certain embodiments, the power coil 4016 transmits power to the lock circuit through inductive coupling with the lock power coil 4036. The power transfer circuitry may be configured to operate similarly to one or more power transfer circuits described above. Power received by the lock circuit using power coil 4036 may be provided to rectifier circuitry in order to at least partially convert the alternating current signal to a direct current signal for use by the lock circuitry.
Data received from a lock circuit may be provided to a receiver circuit 4152 including coupled power compensation circuitry. The receiver circuit can, in addition to including a comparator 4114 that provides an output signal to a processor (not shown), compensate for induced voltage on the partial capacitor 4110. This voltage may be induced by magnetic fields in the ferrite core of the key power coil described above and may be caused by the bending of the power coil magnetic field to a non-perpendicular orientation with respect to the partial capacitor at or near an end region of the power coil. In the depicted embodiment, the receiver circuitry 4152 includes a resistor network that employs a voltage divider to adjust the voltage level provided as a reference input to the comparator 4114. A portion of the power signal provided from the coil 4116 is provided to the reference input to the comparator 4114 in order to offset the reference voltage to at least partially compensate for the unwanted voltage induced on the metal plate 4110. For example, the values of R6, R11, and R36 may be calculated to provide an appropriate offset and compensation level for coupled interference at the comparator input. Thus, for example, the initial voltage reference of the comparator 4114 is raised by an amount approximately equal to an estimated amount of noise received by the capacitor due to coupling with the power coil. As a result, the comparator 4114 may not output a logic high value unless the signal from the partial capacitor 4110 is higher than the noise level plus an initial reference level and therefore not passing a logic high solely due to noise in many instances. In certain embodiments, the circuitry 4152 utilizes an op-amp inverter in place of the comparator.
As described above, the key and/or the lock may generate and store audit data for tracking the use of electronic keys and locks. This audit data may include ID numbers of keys used to access locks, including keys which unsuccessfully attempted to open locks, as well as the IDs of users who use the keys and locks (for example, by tracking the users' passcodes entered into the keys or key retention devices (see below)). The audit data may further include several other types of information. For instance, audit data can include data on when a lock is unlocked, data on when a locked item containing the lock is opened, data on when a lock is relocked, or data on when a locked item containing the lock is closed. The audit data can include dates and times for these and possibly other actions. The audit data can also include information about whether a key was lost or whether a key was returned to a docking station or key retention device (examples of which are described below). Audit data can therefore allow administrators to monitor the use of keys and locks as well as the individuals who use those keys and locks.
While it can be useful to track when a lock is unlocked or relocked, it can be difficult to tell when a lock has relocked because the lock typically may relock after the key has been withdrawn from the lock. Once the key has been withdrawn from the lock, the key may not be able to communicate with the lock to determine the lock state (absent wireless communications, which may be included but which may increase the cost of the lock and key). Further, it can be useful to determine whether a locked item (for example, a cabinet, enclosure, door, padlock, or the like) containing the lock is open or closed. Separate hardware can be used to detect opening and closing of the locked item, or whether the item is locked or unlocked. However, it may be desirable to use the key alone (in conjunction with the lock) to heuristically estimate when the locked item is open or closed.
Moreover, it can be particularly useful to track unlockings and relockings in the emergency services industry. Fire and law enforcement departments, for example, may install key cabinets outside buildings, which may store building keys so that emergency personnel can gain access to a building in an emergency instead of breaking a door or window. These key cabinets can include the electronic lock core described above. The corresponding electronic key described above can be used to access those key cabinets. Given that the public may place great trust in emergency personnel by permitting them access to their buildings, it can be important to track and audit the use of electronic keys with these key cabinets so as to identify and address any misuse of those keys or key cabinets.
The following describes example features for detecting a lock state, such as whether the lock is locked, unlocked, or relocked. These features can also be used to heuristically determine whether a locked item containing the lock is opened or closed, or secured or unsecured. Any of the features described below may be implemented using any of the keys or locks described above. For example, the features described below can be implemented with locks whose data transfer functionality includes a capacitive interface, inductive interface, or combinations of the same, as well as locks that inductively transfer data modulating a power signal that delivers power to the lock. Further, the features described below can be implemented with any other electronic keys and lock, including those that operate with electrical contacts. In some implementations, lock state detection can involve the key communicating one or more heartbeat signals to a lock and determining based on the response(s) it receives from the lock, if any, whether the lock is locked, unlocked, or relocked. In some cases, the heartbeat signal may include a periodic signal generated by hardware or software in the key. The periodic signal may be sent to the lock to determine information about the lock and/or the relationship between the key and the lock. For example, the signal may be communicated to the lock to determine whether the key remains in contact with the lock. The determination of whether the key is in contact with the lock may be based on a response to the heartbeat signal. In some cases, the lock may provide a heartbeat signal to the key to communicate to the key that it is in a particular state or remains in communication with the key.
In the example key management system 4200 shown, there are electronic keys 4210, key retention devices 4220, lock boxes and other locking items 4240 (such as padlocks), docking stations 4250, administrative systems 4260, an electronic lock management system 4270, and a network 4208. The network 4208 can include a wireless and/or wired network, a local area network (LAN), a wide area network (WAN), the Internet, an intranet, combinations of the same, or the like.
The electronic key 4210 can have the features of any of the electronic keys described above. For instance, the electronic key 4210 can have a capacitive and/or inductive interface that permits contactless electronic transmission of data and power to a corresponding lock core installed in a locking device 4240. The key retention device 4220 can secure both the electronic key 4210 and optionally a mechanical key. When a user enters a code into an electronic keypad on the key retention device 4220 (see, e.g.,
The electronic key 4210 can communicate electronically with the key retention device 4220 to transmit audit data regarding electronic key usage with a locking device 4240. In turn, the key retention device 4220 can upload the audit data to one or more administrative systems 4260 over a wired or wireless connection. The administrative systems 4260 may be personal computers, desktops, laptops, tablets, smartphones, or the like operated by one or more administrative users (or simply, “administrators”). The administrative systems 4260 can include software, which may be a standalone application or web application, that submits the audit data to an electronic lock management system 4270 over the network 4208. The standalone application or web application can enable the administrators to view and analyze the audit data to identify irregularities and the like (see, for example,
The docking station 4250 may have a similar functionality as the key retention device 4220, including receiving data from the electronic key 4210 and transmitting that data over the network 4208 to the one or more administrative systems 4260 and/or directly to the electronic lock management system 4270. Further, both the key retention device 4220 and the docking station 4250 can charge the electronic key 4210 and can be used to program the key 4210.
The electronic lock management system 4270 can include software implemented on one or more servers, physical or virtual, which may be geographically dispersed in one or more data centers or geographically co-located. The electronic lock management system 4270 can be implemented in a cloud computing platform, such as a platform as a service (PaaS), infrastructure as a service (IaaS), or software as a service (SaaS) platform, examples of which include Microsoft Azure™ and Amazon AWS™. The electronic lock management system 4270 can store and analyze audit data received from the plurality of electronic keys 4210, key retention devices 4220, and/or docking stations 4250. The electronic lock management system 4270 can provide the web application referred to above, which may be accessed using a browser of the administrative systems 4260. The web application may include one or more user interfaces that output the audit data in various forms, such as tables, graphs, charts, or the like (see, for example,
The process 4300 may occur when an electronic key 4210 is mated with an electronic lock including in a locking item 4240. The key 4210 may be mated with the lock when a portion of the key configured to engage with or communicate with a portion of the lock is positioned with respect to a corresponding portion of the lock configured to engage with or communicate with the portion of the key. For example, the key 4210 may mate with the lock when a mating portion 1312 of a key engages a mating portion 1408 of a lock.
The heuristic lock state detection process 4300 may be used to detect whether a lock is locked, unlocked, or relocked. The process may involve the key 4210 sending one or more heartbeat signals to the lock and awaiting one or more responses from the lock. Prior to execution of the process 4300, the key 4210 can be mated with the lock, and a user may enter a passcode using the buttons on the key 4210 described above (see, e.g.,
In some cases, the process 4300 can be combined with a door state detection process to determine whether a lock is in a locked or unlocked position when a door, a draw, a gate, a container, or any other lockable structure or locking item 4240 is in an open to closed position. For example, the door state may be determined using magnets, one or more accelerometers, electrical connections or circuits, tilt sensors, piezoelectric sensors, pressure sensors, and the like to determine whether the door, or other lockable structure, is open or closed. Further, the door state may be determined using proximity detection sensors, such as radio frequency identification (RFID) sensors. One such non-limiting example of sensors that may be used to determine the door state of a lockable structure includes the Virtual Interlock Validator™ that is incorporated in the Knox® MedVault® product produced by the Knox Company. Further, some additional non-limiting examples of sensors that may be used with the systems described herein are described in U.S. Pat. No. 8,339,261, filed on Jul. 1, 2009, which is hereby incorporated by reference in its entirety herein. The open or closed state information may be combinable with the locked or unlocked state information to provide auditing or status information for a lock or structure including the lock.
At block 4302, in response to receiving this passcode, the key 4210 sends an open instruction to the lock. The key 4210 can send this open instruction over the capacitive or inductive data interfaces described above. (In general, any communications of data between the key 4210 and the lock may be done using either the capacitive or inductive interfaces described above, or via any electronic mechanism usable by an electronics key or lock.) The open instruction may include a series of bits formatted according to a protocol recognized by both the key and the lock. These bits may be conveyed using an analog modulation scheme, such as amplitude modulation (including rectangular pulse amplitude modulation), frequency modulation, or phase modulation, or a digital modulation scheme such as phase-shift keying (PSK), frequency-shift keying (FSK), amplitude-shift keying (ASK), or quadrature amplitude modulation (QAM). Thus, the key may communicate a modulated waveform between a partial capacitor of the key to a corresponding partial capacitor of the lock (or between equivalent inductors). The key and the lock may communicate at baseband frequencies or at modulated carrier signal frequencies.
At block 4304, the key 4210 receives confirmation from the lock of actuation of the locking mechanism described above, for example, by receiving a confirmation signal from the lock indicating that the lock has unlocked. In some cases, the key 4210 may determine that the lock is unlocked by determination of a relative position of the key 4210 when mated with the lock. The determination of the relative position of the key 4210 may be based on alignment of particular elements of the key 4210 (e.g., coils, the nose, or tabs) with particular elements of the lock (e.g., coils, a cup, or tabs). In some such cases, elements of the key 4210 may only be permitted to align with elements of the lock when the correct passcode is provided by the key 4210 to the lock.
At block 4305, the key 4210 records the date and time of the unlocking event, for example, in a memory device of the key 4210. The key 4210 may further record an amount of time that the locking item 4240 is unlocked and/or open. Alternatively, or in addition, the key 4210 provides the date and time of unlocking and locking of the locking item 4240 to an administrative system 4260 and/or electronic lock management system 4270, which may determine the amount of time that the locking item 4240 is unlocked and/or open based on the provided data. In some cases, the key 4210 may record whether the locking item 4240 confirmed its lock status or whether the key 4210 inferred the lock status based, for example, on the heartbeat signal. Further, the key 4210 may record a location of the unlocking event. For example, if the locking item 4240 is portable or within a moveable structure, such as a vehicle, the key 4210 may identify a location of the locking item 4240 using, for example, a global positioning system, that may be embedded in the key 4210 and/or the locking item 4240. In some cases, the location may be determined from information stored in a memory of the locking item 4240. For example, the locking item 4240 may store information identifying whether it is located at a front door or rear door of a building.
In some cases, the key 4210 may associate information about the key 4210 itself with the unlocking event. For example, the key 4210 may associate key identification information or key status information, such as whether the key is a master or administrator key capable of programming a locking item 4210, or a slave or non-administrator key that may have a reduced feature set (e.g., not capable of programming the locking item 4210). In some cases, the locking item 4240 may record the date and time of the unlocking event, for example, in a memory device of the locking item 4240. Some or all of the above described information can be included in audit information that may be stored in memory and/or transmitted over a network to an administrative system 4260 or an electronic lock management system 4270.
At block 4306, the key 4210 sends a heartbeat signal to the lock. This heartbeat signal may be one of several that the key 4210 sends to the lock. In addition to having its ordinary meaning, the term “heartbeat signal” as used herein can refer to a signal that the key periodically sends to the lock for the purpose of eliciting a response that would signify that the lock is still in communication with the key. In some cases, the heartbeat signal may be sent aperiodically or with greater frequency. For example, as described below, if the heartbeat signal is not acknowledged, the heartbeat signal may be sent more frequently.
If the lock is still in communication with the key 4210, then the key 4210 may infer that the lock is still unlocked. This assumption holds in some implementations because in an unlocked state, the key is secured in the lock by the tabs 1314 of the key being engaged with the tabs 1470 of the lock. However, if the key is moved to a locked state and then removed from the lock, the key should no longer receive communications from the lock, and thus the heartbeat signal will not be responded to by the lock (in embodiments where wireless communication is not used). Accordingly, the key 4210 can infer that the lock has relocked. In some cases, the key 4210 may determine or infer that the lock remains in an unlocked position based on an orientation of the key 4210 with respect to the locking item 4240. The orientation of the key 4210 may be determined, for example, based on an alignment of coils between the key 4210 and the locking item 4240, based on a position of a mechanical switch engaged by the key, based on an orientation of the key 4210 while engaged with the locking item 4240, and the like. Further, in some cases, the key 4210 may receive a lock indication signal from the locking item 4240 indicating that the locking item 4240 has relocked.
Thus, if the key receives a response from the lock at block 4308, the key can continue to send heartbeat signals to the lock at block 4306. However, if the key does not receive a response at block 4308, the key can try again to send another heartbeat signal at block 4310, and thus the process 4300 loops back to block 4306. If a certain number of heartbeat signals have been sent to the lock without receiving a response, such as three signals, the key may infer that the lock is now in a locked (or relocked) state because the key is likely removed from the lock. Accordingly, at block 4312, the key can record the date and time that the lock was relocked. This date and time recordation can be part of the audit data stored in the key, together with the date and time recordation of the unlocking event at block 4305.
Although not shown, subsequent to the process 4300, the key 4210 can transmit its stored audit data regarding dates and times of unlocking and re-locking, or any of the additional information described above that can be included as part of the audit data. For instance, when the key 4210 is docked with the docking station 4250 or the key retention device 4220, the key 4210 can upload its stored audit data to the docking station 4250 or key retention device 4220. As described above with respect to
At block 4352, the lock is idle. For example, the lock may be in a locked state. At block 4354, one or more keypresses are detected at the key. The key then attempts to communicate with the lock at block 4356, for example, by supplying an access code derived from the one or more keypresses. At block 4358, it is determined whether the key and lock agree, for example, by the lock determining whether the one or more access codes it received from the key 4210 correspond to a valid access code stored in a memory device of the lock.
If the key 4210 and lock do not agree, the process 4350 loops back to block 4352, and the lock remains idle. Otherwise, an opened audit event is generated at block 4360. The opened audit event can involve the key and/or the lock storing in a memory device of the key and/or the lock audit data indicating that the lock was opened (for example, unlocked), along with a date and time of that opening. The lock audit data may further include a location of the lock and/or how long the lock was opened for. Moreover, the lock audit data may confirm whether the locking item 4240 was confirmed closed when locked or relocked.
At block 4362, the key delays for a predetermined period of time, such as some milliseconds or seconds. For example, the key may delay for 1, 2, 3, 5, or 10 milliseconds or seconds, any amount of time in between the preceding examples, or for more or less time.
At block 4364, the key 4210 communicates a heartbeat signal to the lock. At block 4366, the key determines whether the lock responds. If so, the key again delays at block 4362 and then sends another heartbeat signal to the lock at block 4364. If the lock does not respond, the key determines at block 4368 whether a miss threshold has been exceeded. As described above, in one example, the miss threshold is three missed heartbeat signals. If the miss threshold has not been exceeded, the key again delays at block 4362 and communicates another heartbeat signal to the lock at block 4364. One or more of the subsequent occurrences of the delay 4362 may differ in length from one or more of the previous occurrences of the delay 4362. For example, if the lock does not respond to a heartbeat signal, the delay may be shortened. In contrast, if the lock does respond to the heartbeat signal, or if the lock has responded to a certain number of consecutive heartbeat signals, the delay may be lengthened. Adjusting the length of the delay may provide for a more accurate determination of lock status and/or may alter power consumption of the key 4210.
If the miss threshold has been exceeded, a locked audit event is generated at block 4370. The locked audit event can include the key and/or the lock storing, in a memory device of either the key and/or the lock, audit data indicating that the lock was locked (or relocked), along with a date and time of that locking. In some cases, a lock may provide an indication of the lock status to the key 4210. In other cases, the key 4210 may determine that the lock is locked after a particular period of time has elapsed due, for example, to an auto lock capability of the lock. In some cases, the key 4210 determines or identifies the lock as being locked if or when a closed status for the locking items 4240 is determined or confirmed. The lock status may be included as part of the audit data. In some cases, if a response is not received from the lock indicating lock status, the audit data may include an indeterminate status for the lock.
Turning to
The example key retention device 4420 shown includes an electronic key holder 4430 and a mechanical key holder 4450 (which may be omitted in some embodiments). The electronic key holder 4430 can hold any of the electronic keys described above, such as the key 4210. A retaining arm 4432 can hold the electronic key in place within the electronic key holder 4430. The retaining arm 4432 may be opened and closed electronically by a motor residing inside the key retention device 4420. A keypad 4440 can enable a user to input a personal or department keycode. The inputted keycode can be provided to a processor inside the key retention device 4420, which can send a signal to the motor, causing the retaining arm 4432 to open so as to release the electronic key from the key holder 4430. Input of the keycode can also release the mechanical key from the mechanical key holder 4450 via similar motor control.
Because a user may need to input a personal key code or department key code into the keypad 4440 before obtaining a mechanical or electronic key, the key retention device 4420 can permit accurate recordation of who accesses keys and when. Whenever a user inputs a code to access a key or returns that key to the key retention device 4420, the key retention device 4420 can record these actions as audit data. Likewise, as described above, whenever a user re-inserts a key into the key retention device 4420, the key can upload its audit data to the key retention device 4420, for example through pins 4434, which may electrically couple with electrical contacts on the back of the key (not shown). The key retention device 4420 thereafter may upload the audit data generated by the key and the audit data generated by the key retention device 4420 to an administrative system 4260 and/or the electronic lock management system 4270.
In the example user interface 4500 shown, user-selectable tabs 4502 are provided to enable a user to access audit data regarding several different devices. These tabs include a “KeySecure” tab (corresponding to the key retention devices 4220, 4420), a “KnoxDock” tab (corresponding to the docking stations 4250), a “Knox eKey” tab (corresponding to the keys 4210), a “Knox eLock Core” tab (corresponding to the lock cores described above), and a “Debug Events” tab. The “Knox eLock Core” tab 4502 is shown selected in the present example. Date and time controls 4504 are user selectable to select audit data within a date and time range. A get records button 4506 can be selected to obtain the audit data for that date and time range.
In response to user actuation of the button 4506, the audit trail data 4510 corresponding to the selected date and time range is shown. This audit trail data 4510 includes several example entries, including an entry 4512 corresponding to an opened event indicating when a lock was opened, and an entry 4514 corresponding to a relocked event corresponding to when the lock was relocked.
The user interface elements shown are merely illustrative examples and can be varied in other embodiments. For instance, any of the user interface elements shown may be substituted with other types of user interface elements. Some examples of user interface elements that may be used include buttons, dropdown boxes, select boxes, text boxes or text fields, checkboxes, radio buttons, toggles, breadcrumbs (for example, identifying a page or interface that is displayed), sliders, search fields, pagination elements, tags, icons, tooltips, progress bars, notifications, message boxes, image carousels, modal windows (such as pop-ups), date and/or time pickers, accordions (for example, a vertically stacked list with show/hide functionality), and the like. Additional user interface elements not listed here may be used.
Further, the user interface 4500 shown may be combined or divided into other user interfaces such that similar functionality or the same functionality may be provided on more screens or user interfaces. Moreover, each of the user interface elements may be selected by a user using one or more input options, such as a mouse, touch screen input (for example, finger or pen), or keyboard input, among other user interface input options.
While various embodiments of key and lock circuits have been depicted, the various illustrative logical blocks, modules, and processes described herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and states have been described above generally in terms of their functionality. However, while the various modules are illustrated separately, they may share some or all of the same underlying logic or code. Certain of the logical blocks, modules, and processes described herein may instead be implemented monolithically.
The various illustrative logical blocks, modules, and processes described herein may be implemented or performed by a machine, such as a computer, a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may be a microprocessor, a controller, microcontroller, state machine, combinations of the same, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors or processor cores, one or more graphics or stream processors, one or more microprocessors in conjunction with a DSP, or any other such configuration.
The blocks or states of the processes described herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. For example, each of the processes described above may also be embodied in, and fully automated by, software modules executed by one or more machines such as computers or computer processors. A module may reside in a computer readable medium such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, memory capable of storing firmware, or any other form of computer-readable (e.g., storage) medium known in the art. An example computer-readable medium can be coupled to a processor such that the processor can read information from, and write information to, the computer-readable medium. In the alternative, the computer-readable medium may be integral to the processor. The processor and the computer-readable medium may reside in an ASIC.
Depending on the embodiment, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, may be added, merged, or left out all together. Thus, in certain embodiments, not all described acts or events are necessary for the practice of the processes. Moreover, in certain embodiments, acts or events may be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or via multiple processors or processor cores, rather than sequentially.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the logical blocks, modules, and processes illustrated may be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments of the inventions described herein may be embodied within a form that does not provide all of the features and benefits set forth herein, as some features may be used or practiced separately from others. The scope of certain inventions disclosed herein is indicated by the claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This disclosure is a continuation of and claims priority to U.S. application Ser. No. 17/119,967, which was filed on Dec. 11, 2020 and is titled “ELECTRONIC LOCK STATE DETECTION SYSTEMS AND METHODS,” the disclosure of which is expressly incorporated by reference herein in its entirety for all purposes, and which claims priority to U.S. application Ser. No. 16/574,801, which was filed on Sep. 18, 2019 and is titled “ELECTRONIC LOCK STATE DETECTION SYSTEMS AND METHODS,” the disclosure of which is expressly incorporated by reference herein in its entirety for all purposes, and which claims priority to U.S. Provisional Application No. 62/734,742, which was filed on Sep. 21, 2018 and is titled “ELECTRONIC LOCK STATE DETECTION SYSTEMS AND METHODS,” the disclosure of which is expressly incorporated by reference herein in its entirety for all purposes. Any and all applications, if any, for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference in their entireties under 37 CFR 1.57.
Number | Name | Date | Kind |
---|---|---|---|
1341876 | Benham | Jun 1920 | A |
1345574 | Benham | Jul 1920 | A |
1345575 | Benham et al. | Jul 1920 | A |
1400135 | Benham et al. | Dec 1921 | A |
1451036 | Benham | Apr 1923 | A |
1522572 | Benham | Jan 1925 | A |
1522573 | Benham | Jan 1925 | A |
1534495 | Benham | Apr 1925 | A |
1543447 | Willey | Jun 1925 | A |
1546001 | Benham et al. | Jul 1925 | A |
1561207 | Benham | Nov 1925 | A |
1561901 | Benham | Nov 1925 | A |
1573536 | Benham | Feb 1926 | A |
1607385 | Benham | Nov 1926 | A |
1611712 | Benham et al. | Dec 1926 | A |
1630238 | Benham | May 1927 | A |
1645407 | Harry | Oct 1927 | A |
1646987 | Benham | Oct 1927 | A |
1665015 | Benham | Apr 1928 | A |
1665016 | Benham et al. | Apr 1928 | A |
1691030 | Benham et al. | Nov 1928 | A |
1718606 | Soref | Jun 1929 | A |
1722070 | Benham | Jul 1929 | A |
1722071 | Benham | Jul 1929 | A |
1826595 | Benham | Oct 1931 | A |
1845354 | Soref | Feb 1932 | A |
1938941 | Soref | Dec 1933 | A |
1942045 | Benham | Jan 1934 | A |
1967109 | Benham | Jul 1934 | A |
2083816 | Benham | Jun 1937 | A |
2095429 | Benham | Oct 1937 | A |
2105337 | Soref et al. | Jan 1938 | A |
2113864 | Soref et al. | Apr 1938 | A |
2127089 | Schamp et al. | Aug 1938 | A |
2127091 | Soref et al. | Aug 1938 | A |
2136435 | Habram et al. | Nov 1938 | A |
2152258 | Hirn | Mar 1939 | A |
2160294 | Soref | May 1939 | A |
2169907 | Soref et al. | Aug 1939 | A |
2170097 | Soref et al. | Aug 1939 | A |
2173720 | Keith et al. | Sep 1939 | A |
2191694 | Hirn | Feb 1940 | A |
2227283 | Soref | Dec 1940 | A |
2285328 | Clarkson et al. | Jun 1942 | A |
2352190 | John et al. | Jun 1944 | A |
2460474 | Soref et al. | Feb 1949 | A |
2471291 | Soref et al. | May 1949 | A |
2487608 | Soref et al. | Nov 1949 | A |
2520742 | Soref et al. | Aug 1950 | A |
2563754 | Soref | Aug 1951 | A |
2565440 | Soref et al. | Aug 1951 | A |
2766608 | Hirn | Oct 1956 | A |
2766609 | Hirn | Oct 1956 | A |
2766610 | Hirn | Oct 1956 | A |
2820360 | Soref et al. | Jan 1958 | A |
2824439 | Soref et al. | Feb 1958 | A |
2842950 | Soref et al. | Jul 1958 | A |
2857045 | Foote et al. | Oct 1958 | A |
2858691 | Hoffman | Nov 1958 | A |
2867110 | Foote et al. | Jan 1959 | A |
2893231 | Soref et al. | Jul 1959 | A |
2893232 | Foote et al. | Jul 1959 | A |
2949185 | Foote et al. | Aug 1960 | A |
3023600 | Samuel et al. | Mar 1962 | A |
3023602 | Foote et al. | Mar 1962 | A |
3031876 | Foote et al. | May 1962 | A |
3031877 | Foote et al. | May 1962 | A |
3050977 | Foote et al. | Aug 1962 | A |
3052114 | Foote et al. | Sep 1962 | A |
3073145 | Potzick | Jan 1963 | A |
3190089 | Foote et al. | Jun 1965 | A |
3236372 | Foote | Feb 1966 | A |
3289830 | Foote | Dec 1966 | A |
3373583 | Parrock | Mar 1968 | A |
3378908 | Buller | Apr 1968 | A |
3389586 | Foote | Jun 1968 | A |
3392471 | Foote | Jul 1968 | A |
3408842 | Barnes et al. | Nov 1968 | A |
3422560 | Foote | Jan 1969 | A |
3422643 | Foote | Jan 1969 | A |
3422644 | Foote | Jan 1969 | A |
3423968 | Foote | Jan 1969 | A |
3423969 | Foote | Jan 1969 | A |
3453758 | Soref et al. | Jul 1969 | A |
3453846 | Owen et al. | Jul 1969 | A |
3473352 | Foote | Oct 1969 | A |
3475930 | Foote | Nov 1969 | A |
3475931 | Foote | Nov 1969 | A |
3476429 | Foote | Nov 1969 | A |
3526110 | Foote | Sep 1970 | A |
3548486 | Foote | Dec 1970 | A |
3563067 | Foote | Feb 1971 | A |
3572063 | Foote | Mar 1971 | A |
3586163 | Loehrer et al. | Jun 1971 | A |
3598931 | Foote | Aug 1971 | A |
3624945 | Foote | Dec 1971 | A |
3635057 | Foote et al. | Jan 1972 | A |
3664163 | Foote | May 1972 | A |
3667260 | Foote | Jun 1972 | A |
3736781 | Foote | Jun 1973 | A |
3742742 | Foote | Jul 1973 | A |
3765197 | Foote | Oct 1973 | A |
3783656 | Foote | Jan 1974 | A |
3783657 | Foote | Jan 1974 | A |
3787082 | Foote | Jan 1974 | A |
3797947 | Foote | Mar 1974 | A |
3835676 | Foote | Sep 1974 | A |
3838585 | Foote | Oct 1974 | A |
3908415 | Foote | Sep 1975 | A |
3943738 | Foote | Mar 1976 | A |
3977221 | Foote | Aug 1976 | A |
3983724 | Foote | Oct 1976 | A |
4047406 | Foote | Sep 1977 | A |
D250990 | Hanneman et al. | Feb 1979 | S |
4180996 | Lebrecht | Jan 1980 | A |
4185478 | Stintzi | Jan 1980 | A |
D281949 | Hartmann et al. | Dec 1985 | S |
4569545 | Hartmann et al. | Feb 1986 | A |
4615191 | Grandy | Oct 1986 | A |
D292869 | Lebrecht | Nov 1987 | S |
4730467 | Lebrecht | Mar 1988 | A |
5003279 | Morinaga et al. | Mar 1991 | A |
5033279 | Lebrecht | Jul 1991 | A |
5044180 | Lebrecht | Sep 1991 | A |
D324162 | Lebrecht | Feb 1992 | S |
D325158 | Lebrecht | Apr 1992 | S |
5109684 | Grandy, Sr. | May 1992 | A |
D332388 | Marotto | Jan 1993 | S |
5249444 | Dancs | Oct 1993 | A |
D341766 | Zacher et al. | Nov 1993 | S |
D342009 | Lebrecht et al. | Dec 1993 | S |
D342010 | Lebrecht et al. | Dec 1993 | S |
5456503 | Russell, IV | Oct 1995 | A |
5501492 | Kajuch | Mar 1996 | A |
5513505 | Dancs | May 1996 | A |
5516160 | Kajuch | May 1996 | A |
5572890 | Carpenter | Nov 1996 | A |
5647617 | Kajuch | Jul 1997 | A |
5697239 | Hanneman et al. | Dec 1997 | A |
5712626 | Andreou et al. | Jan 1998 | A |
5713612 | Kajuch | Feb 1998 | A |
5735153 | Hanneman et al. | Apr 1998 | A |
5755121 | Crass | May 1998 | A |
5775121 | Kuma et al. | Jul 1998 | A |
5794925 | Fantl et al. | Aug 1998 | A |
5819560 | Grahovec et al. | Oct 1998 | A |
5839309 | Fantl et al. | Nov 1998 | A |
D406043 | Leclaire | Feb 1999 | S |
D423323 | Fiegener et al. | Apr 2000 | S |
D423906 | Fiegener et al. | May 2000 | S |
D423907 | Fiegener et al. | May 2000 | S |
D424911 | Geringer et al. | May 2000 | S |
D425397 | Fiegener et al. | May 2000 | S |
D425398 | Fiegener et al. | May 2000 | S |
D425400 | Geringer et al. | May 2000 | S |
D425777 | Geringer et al. | May 2000 | S |
D426763 | Adler et al. | Jun 2000 | S |
D427503 | Brockman et al. | Jul 2000 | S |
D428794 | Fiegener et al. | Aug 2000 | S |
6109076 | Kajuch | Aug 2000 | A |
D432390 | Geringer et al. | Oct 2000 | S |
D432391 | Heppner | Oct 2000 | S |
D436902 | Kajuch et al. | Jan 2001 | S |
D437204 | Kajuch et al. | Feb 2001 | S |
D437768 | Grosz et al. | Feb 2001 | S |
D439823 | Adler et al. | Apr 2001 | S |
D440861 | Thompson | Apr 2001 | S |
6263713 | Fantl | Jul 2001 | B1 |
6305198 | Chastain et al. | Oct 2001 | B1 |
D457113 | Zapushek et al. | May 2002 | S |
D457802 | Meekma et al. | May 2002 | S |
6389857 | Meekma et al. | May 2002 | B1 |
6393874 | Zapushek et al. | May 2002 | B1 |
D458530 | Grosz et al. | Jun 2002 | S |
6401501 | Kajuch et al. | Jun 2002 | B1 |
6401505 | Kajuch et al. | Jun 2002 | B1 |
D461392 | Zapushek | Aug 2002 | S |
6434981 | Fantl et al. | Aug 2002 | B2 |
D462735 | Rohde et al. | Sep 2002 | S |
D468991 | Makos et al. | Jan 2003 | S |
D469332 | Meekma et al. | Jan 2003 | S |
6539758 | Meekma et al. | Apr 2003 | B2 |
D474100 | Zapushek | May 2003 | S |
6629440 | Meekma et al. | Oct 2003 | B1 |
D484391 | Hackbarth et al. | Dec 2003 | S |
D484777 | Ruan | Jan 2004 | S |
6705137 | Saladin et al. | Mar 2004 | B2 |
6708534 | Ruan | Mar 2004 | B1 |
6755054 | Burmesch et al. | Jun 2004 | B2 |
6766671 | Haczynski et al. | Jul 2004 | B2 |
D495238 | Handel et al. | Aug 2004 | S |
D500949 | Handel | Jan 2005 | S |
6846002 | Irgens et al. | Jan 2005 | B2 |
6854302 | Zapushek et al. | Feb 2005 | B2 |
6862905 | Zapushek | Mar 2005 | B2 |
6865914 | Irgens et al. | Mar 2005 | B2 |
D506122 | Welch | Jun 2005 | S |
D506665 | Sun et al. | Jun 2005 | S |
D506667 | Welch | Jun 2005 | S |
6904775 | Makos et al. | Jun 2005 | B2 |
D507473 | Welch | Jul 2005 | S |
D507474 | Welch | Jul 2005 | S |
D507480 | Kopp et al. | Jul 2005 | S |
D511291 | Van Handel | Nov 2005 | S |
D511292 | Hohmann et al. | Nov 2005 | S |
D512900 | Tarter et al. | Dec 2005 | S |
6978647 | Edwards, Jr. et al. | Dec 2005 | B2 |
D514409 | Kopp et al. | Feb 2006 | S |
D515908 | Kearns et al. | Feb 2006 | S |
7006483 | Nelson, Jr. et al. | Feb 2006 | B2 |
D516408 | Kearns et al. | Mar 2006 | S |
D516896 | Kearns et al. | Mar 2006 | S |
D517396 | Tarter et al. | Mar 2006 | S |
D518353 | Van Handel | Apr 2006 | S |
D518357 | Kearns et al. | Apr 2006 | S |
D519364 | Kopp et al. | Apr 2006 | S |
D520339 | Heppner | May 2006 | S |
D521359 | Welch | May 2006 | S |
7040126 | Edwards, Jr. | May 2006 | B2 |
7066483 | Makos et al. | Jun 2006 | B2 |
D524142 | Recknagel et al. | Jul 2006 | S |
D524144 | Recknagel et al. | Jul 2006 | S |
D524145 | Heppner | Jul 2006 | S |
D524632 | Kearns et al. | Jul 2006 | S |
D525519 | Van Handel et al. | Jul 2006 | S |
D525857 | Recknagel et al. | Aug 2006 | S |
D525861 | Mackey et al. | Aug 2006 | S |
D528401 | Ruan | Sep 2006 | S |
D528402 | Ruan | Sep 2006 | S |
D528409 | Kopp et al. | Sep 2006 | S |
7104563 | Makos et al. | Sep 2006 | B2 |
D529368 | Ruan | Oct 2006 | S |
D529369 | Ruan | Oct 2006 | S |
D529786 | Heppner | Oct 2006 | S |
D531008 | Recknagel et al. | Oct 2006 | S |
D533002 | Recknagel et al. | Dec 2006 | S |
D533435 | Kearns et al. | Dec 2006 | S |
D533437 | Ruan | Dec 2006 | S |
D533764 | Heppner | Dec 2006 | S |
7145237 | Teraguchi | Dec 2006 | B2 |
D535555 | Kopp et al. | Jan 2007 | S |
D535629 | Kalous et al. | Jan 2007 | S |
D536236 | Recknagel et al. | Feb 2007 | S |
D537320 | Kearns et al. | Feb 2007 | S |
D537703 | Kearns et al. | Mar 2007 | S |
D537704 | Van Handel | Mar 2007 | S |
D539633 | Van Handel | Apr 2007 | S |
D540160 | Konop et al. | Apr 2007 | S |
D540653 | Blomstrom | Apr 2007 | S |
D541135 | Kalous et al. | Apr 2007 | S |
7197904 | Marcelle et al. | Apr 2007 | B2 |
7207199 | Smith et al. | Apr 2007 | B2 |
D541630 | Blomstrom et al. | May 2007 | S |
D541631 | Heppner | May 2007 | S |
D542625 | Blomstrom et al. | May 2007 | S |
D545104 | Sheridan et al. | Jun 2007 | S |
7225651 | Edwards et al. | Jun 2007 | B2 |
D546663 | Recknagel et al. | Jul 2007 | S |
D547161 | Blomstrom et al. | Jul 2007 | S |
D547162 | Heppner | Jul 2007 | S |
D548042 | Smyczek et al. | Aug 2007 | S |
D548045 | Heppner | Aug 2007 | S |
D548047 | Kearns | Aug 2007 | S |
D548594 | Van Handel et al. | Aug 2007 | S |
D549554 | Heppner | Aug 2007 | S |
7262376 | Brojanac et al. | Aug 2007 | B2 |
7266981 | Flory et al. | Sep 2007 | B2 |
7267355 | Irgens et al. | Sep 2007 | B2 |
7273223 | Irgens et al. | Sep 2007 | B2 |
D556541 | Blomstrom et al. | Dec 2007 | S |
D557107 | Van Handel et al. | Dec 2007 | S |
D557591 | Mackey | Dec 2007 | S |
D558025 | Rohde et al. | Dec 2007 | S |
7306275 | Kalous | Dec 2007 | B2 |
D559103 | Van Handel et al. | Jan 2008 | S |
D560565 | Kalous | Jan 2008 | S |
7316534 | Hohmann et al. | Jan 2008 | B2 |
D561001 | Rohde et al. | Feb 2008 | S |
D561005 | Rohde et al. | Feb 2008 | S |
D561011 | Van Handel | Feb 2008 | S |
7334443 | Meekma et al. | Feb 2008 | B2 |
D563200 | Nave et al. | Mar 2008 | S |
D563764 | Hacker | Mar 2008 | S |
D564337 | Brojanac et al. | Mar 2008 | S |
D564859 | Brojanac et al. | Mar 2008 | S |
7337639 | Edwards, Jr. | Mar 2008 | B2 |
7348504 | Brojanac | Mar 2008 | B2 |
D565297 | Stevens et al. | Apr 2008 | S |
D566521 | Rohde et al. | Apr 2008 | S |
D567628 | Rohde et al. | Apr 2008 | S |
7353671 | Recknagel et al. | Apr 2008 | B2 |
7360380 | Van Handel | Apr 2008 | B2 |
D568145 | Handel | May 2008 | S |
D569609 | Hacker | May 2008 | S |
7367683 | Marcelle et al. | May 2008 | B2 |
D570667 | Zapushek et al. | Jun 2008 | S |
D571207 | Rozanski | Jun 2008 | S |
D571208 | Rozanski | Jun 2008 | S |
D571209 | Rozanski | Jun 2008 | S |
D571210 | Rozanski | Jun 2008 | S |
D571211 | Rozanski | Jun 2008 | S |
D571212 | Rozanski | Jun 2008 | S |
D571658 | Rozanski | Jun 2008 | S |
D571659 | Rozanski | Jun 2008 | S |
D571660 | Rozanski | Jun 2008 | S |
7380425 | Elliott et al. | Jun 2008 | B2 |
7382250 | Marcelle et al. | Jun 2008 | B2 |
D572132 | Rozanski | Jul 2008 | S |
D573870 | Hacker | Jul 2008 | S |
D573871 | Nave et al. | Jul 2008 | S |
D574629 | Kalkwarf | Aug 2008 | S |
7415850 | Smyczek et al. | Aug 2008 | B2 |
D576859 | Blomstrom et al. | Sep 2008 | S |
D576860 | Blomstrom et al. | Sep 2008 | S |
D576861 | Blomstrom et al. | Sep 2008 | S |
D576862 | Blomstrom et al. | Sep 2008 | S |
D576863 | Blomstrom et al. | Sep 2008 | S |
D576864 | Blomstrom et al. | Sep 2008 | S |
D577195 | Stevens et al. | Sep 2008 | S |
D577278 | Rohde et al. | Sep 2008 | S |
D577279 | Rohde et al. | Sep 2008 | S |
D577523 | Mehmen | Sep 2008 | S |
D577571 | Stevens | Sep 2008 | S |
7419177 | Kottke et al. | Sep 2008 | B2 |
D578757 | Stevens et al. | Oct 2008 | S |
D578758 | Stevens et al. | Oct 2008 | S |
D578864 | Rohde et al. | Oct 2008 | S |
D578884 | Rozanski | Oct 2008 | S |
D580195 | Daino et al. | Nov 2008 | S |
7448236 | Recknagel et al. | Nov 2008 | B2 |
D582251 | Mackey et al. | Dec 2008 | S |
D583218 | Nave et al. | Dec 2008 | S |
7469919 | Kalous et al. | Dec 2008 | B2 |
D584605 | Hedlund et al. | Jan 2009 | S |
7481085 | Rohde et al. | Jan 2009 | B2 |
D587014 | Hand | Feb 2009 | S |
D587047 | Kalkwarf | Feb 2009 | S |
D588849 | Kalkwarf | Mar 2009 | S |
7497705 | Larson et al. | Mar 2009 | B2 |
7501593 | Brojanac | Mar 2009 | B2 |
D591091 | Daino et al. | Apr 2009 | S |
7516631 | Hacker et al. | Apr 2009 | B2 |
7516843 | Konop et al. | Apr 2009 | B2 |
D592485 | Stevens | May 2009 | S |
7526933 | Meekma | May 2009 | B2 |
7535346 | Kalous | May 2009 | B2 |
D594311 | Stevens | Jun 2009 | S |
D594731 | Plato | Jun 2009 | S |
7540175 | Kalous et al. | Jun 2009 | B2 |
7543838 | Jacques | Jun 2009 | B2 |
D595506 | Hacker | Jul 2009 | S |
D595563 | Stevens | Jul 2009 | S |
7556229 | Elliott et al. | Jul 2009 | B2 |
7581420 | Manthe et al. | Sep 2009 | B2 |
7581423 | Brojanac et al. | Sep 2009 | B2 |
D602723 | Daino et al. | Oct 2009 | S |
7610784 | Rohde et al. | Nov 2009 | B2 |
D605494 | Plato | Dec 2009 | S |
D605928 | Stevens et al. | Dec 2009 | S |
D606382 | Stevens | Dec 2009 | S |
D606841 | Stevens | Dec 2009 | S |
D606842 | Stevens et al. | Dec 2009 | S |
D607175 | Stevens | Dec 2009 | S |
7624489 | Rohde et al. | Dec 2009 | B2 |
D611272 | Daino | Mar 2010 | S |
D615275 | Hacker | May 2010 | S |
7708140 | Konop et al. | May 2010 | B2 |
7712343 | Smith et al. | May 2010 | B2 |
7743917 | Konop et al. | Jun 2010 | B2 |
7752876 | Meekma et al. | Jul 2010 | B2 |
D624389 | Stevens et al. | Sep 2010 | S |
D628877 | Stevens | Dec 2010 | S |
D629280 | Plato | Dec 2010 | S |
D629290 | Stevens et al. | Dec 2010 | S |
D631225 | Plato | Jan 2011 | S |
D631323 | Stevens et al. | Jan 2011 | S |
7866771 | Daino et al. | Jan 2011 | B2 |
7870764 | Burmesch | Jan 2011 | B2 |
7870767 | Brojanac et al. | Jan 2011 | B2 |
D633371 | Stevens et al. | Mar 2011 | S |
D634915 | Nave et al. | Mar 2011 | S |
D635324 | Plato | Mar 2011 | S |
D635325 | Plato | Mar 2011 | S |
7905351 | Konop et al. | Mar 2011 | B2 |
D637062 | Plato | May 2011 | S |
D638278 | Plato | May 2011 | S |
D638279 | Plato | May 2011 | S |
D638684 | Stevens | May 2011 | S |
7934405 | Burmesch et al. | May 2011 | B2 |
7948359 | Marcelle et al. | May 2011 | B2 |
D640126 | Plato | Jun 2011 | S |
D640127 | Stevens | Jun 2011 | S |
D640445 | Stevens | Jun 2011 | S |
7963134 | Rafferty et al. | Jun 2011 | B2 |
D641232 | Stevens | Jul 2011 | S |
7977590 | Brojanac | Jul 2011 | B2 |
7984630 | Peot et al. | Jul 2011 | B2 |
8020885 | Cuellar et al. | Sep 2011 | B2 |
D646552 | Plato | Oct 2011 | S |
D646952 | Plato et al. | Oct 2011 | S |
8028551 | Kalous | Oct 2011 | B2 |
8031061 | Kalous | Oct 2011 | B2 |
D648207 | Johnson | Nov 2011 | S |
8056377 | Hacker | Nov 2011 | B2 |
D650548 | Meekma et al. | Dec 2011 | S |
652707 | Plato et al. | Jan 2012 | A1 |
D653102 | Kalous | Jan 2012 | S |
8099985 | Burmesch et al. | Jan 2012 | B2 |
D654654 | Meekma et al. | Feb 2012 | S |
D655885 | Meekma et al. | Mar 2012 | S |
D656384 | Wojtak | Mar 2012 | S |
D659344 | Meekma et al. | May 2012 | S |
D659345 | Meekma et al. | May 2012 | S |
D660130 | Plato | May 2012 | S |
8166783 | Burmesch et al. | May 2012 | B2 |
D661562 | Stevens et al. | Jun 2012 | S |
D664024 | Plato | Jul 2012 | S |
D671389 | Plato | Nov 2012 | S |
8302435 | Burmesch et al. | Nov 2012 | B2 |
D673836 | Stevens et al. | Jan 2013 | S |
8347671 | Brojanac et al. | Jan 2013 | B2 |
D675498 | Stevens et al. | Feb 2013 | S |
8375751 | Hacker | Feb 2013 | B2 |
8402798 | Brojanac et al. | Mar 2013 | B2 |
D679168 | Stevens et al. | Apr 2013 | S |
8408609 | Brojanac | Apr 2013 | B2 |
8419083 | Burmesch | Apr 2013 | B2 |
8424349 | Marcelle et al. | Apr 2013 | B2 |
D681411 | Qin et al. | May 2013 | S |
8453481 | Meekma | Jun 2013 | B2 |
8459070 | Johnson et al. | Jun 2013 | B2 |
D685250 | Stevens et al. | Jul 2013 | S |
D685252 | Stevens et al. | Jul 2013 | S |
D688114 | Stevens | Aug 2013 | S |
D688546 | Stevens et al. | Aug 2013 | S |
D689358 | Stevens | Sep 2013 | S |
8539799 | Nave | Sep 2013 | B2 |
D691458 | Stevens | Oct 2013 | S |
D691869 | Plato | Oct 2013 | S |
D691870 | Stevens | Oct 2013 | S |
8544301 | Nave | Oct 2013 | B2 |
8555686 | Meekma et al. | Oct 2013 | B2 |
D692745 | Stevens | Nov 2013 | S |
D694090 | Nave | Nov 2013 | S |
8573010 | Burmesch et al. | Nov 2013 | B2 |
D695589 | Stevens et al. | Dec 2013 | S |
8607600 | Burmesch et al. | Dec 2013 | B2 |
D698225 | Stevens et al. | Jan 2014 | S |
D700826 | Qin | Mar 2014 | S |
D701105 | Stevens | Mar 2014 | S |
D701106 | Plato | Mar 2014 | S |
D701745 | Stevens | Apr 2014 | S |
D701746 | Stevens et al. | Apr 2014 | S |
D702102 | Stevens | Apr 2014 | S |
D702528 | Nave | Apr 2014 | S |
D703023 | Kalous et al. | Apr 2014 | S |
D703024 | Paulson et al. | Apr 2014 | S |
D703025 | Stevens | Apr 2014 | S |
D703514 | Stevens et al. | Apr 2014 | S |
8695385 | Meekma et al. | Apr 2014 | B2 |
8707745 | Kalous | Apr 2014 | B2 |
D704032 | Plato | May 2014 | S |
D704531 | Stevens | May 2014 | S |
D704532 | Stevens et al. | May 2014 | S |
D704533 | Nave | May 2014 | S |
D705038 | Stevens | May 2014 | S |
D705641 | Stevens et al. | May 2014 | S |
D706113 | Nave | Jun 2014 | S |
D706114 | Nave | Jun 2014 | S |
D706115 | Nave | Jun 2014 | S |
D707101 | Stevens | Jun 2014 | S |
D707530 | Nave | Jun 2014 | S |
D707531 | Nave | Jun 2014 | S |
8739588 | Burmesch et al. | Jun 2014 | B2 |
8769999 | Nave | Jul 2014 | B2 |
D710182 | Walczak et al. | Aug 2014 | S |
8806905 | Burmesch et al. | Aug 2014 | B2 |
8806907 | Kalous et al. | Aug 2014 | B2 |
8839649 | Miller et al. | Sep 2014 | B1 |
8847086 | Wojtak | Sep 2014 | B2 |
8850858 | Nave | Oct 2014 | B2 |
D720203 | Plato | Dec 2014 | S |
D720204 | Ferragu | Dec 2014 | S |
8904831 | Stevens | Dec 2014 | B2 |
D720600 | Paulson | Jan 2015 | S |
D720601 | Paulson | Jan 2015 | S |
D720602 | Paulson | Jan 2015 | S |
D720983 | Paulson | Jan 2015 | S |
D722262 | Stevens | Feb 2015 | S |
D723354 | Stevens | Mar 2015 | S |
D724412 | Stevens | Mar 2015 | S |
D724928 | Kalous et al. | Mar 2015 | S |
D724929 | Kalous et al. | Mar 2015 | S |
D724930 | Kalous et al. | Mar 2015 | S |
D724931 | Dudgeon et al. | Mar 2015 | S |
D724932 | Stevens | Mar 2015 | S |
D725458 | Plato | Mar 2015 | S |
8985448 | Jonely | Mar 2015 | B2 |
8997536 | Fuller et al. | Apr 2015 | B2 |
9003844 | Barraza et al. | Apr 2015 | B2 |
9003845 | Boesel et al. | Apr 2015 | B2 |
9016095 | Dudgeon et al. | Apr 2015 | B2 |
D729026 | Qin et al. | May 2015 | S |
D729038 | Stevens | May 2015 | S |
D729608 | Kalous et al. | May 2015 | S |
9041510 | Wolski | May 2015 | B2 |
D732920 | Walczak et al. | Jun 2015 | S |
D732921 | Walczak et al. | Jun 2015 | S |
D732922 | Walczak et al. | Jun 2015 | S |
9059713 | Jonely et al. | Jun 2015 | B2 |
9093772 | Johnson | Jul 2015 | B2 |
9141090 | Kalous et al. | Sep 2015 | B2 |
D745365 | Dudgeon et al. | Dec 2015 | S |
9208964 | Dudgeon et al. | Dec 2015 | B2 |
D746659 | Stevens et al. | Jan 2016 | S |
D746660 | Stevens et al. | Jan 2016 | S |
9321573 | Rozanski | Apr 2016 | B2 |
D760576 | Plato | Jul 2016 | S |
9411993 | Jonely | Aug 2016 | B2 |
D767368 | Sanford | Sep 2016 | S |
9455839 | Conrad et al. | Sep 2016 | B2 |
9501046 | Kalous et al. | Nov 2016 | B2 |
9600696 | Ebner | Mar 2017 | B2 |
9600949 | Conrad et al. | Mar 2017 | B2 |
9806551 | Jonely | Oct 2017 | B2 |
9843566 | Smith et al. | Dec 2017 | B2 |
9892073 | Conrad | Feb 2018 | B1 |
9894066 | Conrad | Feb 2018 | B2 |
9916466 | Daino et al. | Mar 2018 | B2 |
9920550 | Ebner | Mar 2018 | B2 |
9942840 | Smith et al. | Apr 2018 | B2 |
9965910 | Kalous et al. | May 2018 | B2 |
9996999 | Conrad et al. | Jun 2018 | B2 |
10094885 | Kalous et al. | Oct 2018 | B2 |
10142843 | Conrad et al. | Nov 2018 | B2 |
D844318 | Weiland et al. | Apr 2019 | S |
20020000110 | Fantl et al. | Jan 2002 | A1 |
20020095959 | Meekma et al. | Jul 2002 | A1 |
20020108407 | Zapushek | Aug 2002 | A1 |
20020159395 | George, Jr. et al. | Oct 2002 | A1 |
20030015007 | Zapushek et al. | Jan 2003 | A1 |
20030019258 | Irgens et al. | Jan 2003 | A1 |
20030020256 | Irgens et al. | Jan 2003 | A1 |
20030037582 | Billy, Jr. et al. | Feb 2003 | A1 |
20030046852 | Burmesch et al. | Mar 2003 | A1 |
20030115919 | Haczynski et al. | Jun 2003 | A1 |
20030159479 | Kajuch et al. | Aug 2003 | A1 |
20030233858 | Saladin et al. | Dec 2003 | A1 |
20030234719 | Denison | Dec 2003 | A1 |
20040011092 | Haczynski et al. | Jan 2004 | A1 |
20040011093 | Fantl | Jan 2004 | A1 |
20040016268 | Makos et al. | Jan 2004 | A1 |
20040035160 | Meekma et al. | Feb 2004 | A1 |
20040159133 | Marcelle et al. | Aug 2004 | A1 |
20040159136 | Edwards et al. | Aug 2004 | A1 |
20040164415 | Teraguchi | Aug 2004 | A1 |
20040182120 | Flory et al. | Sep 2004 | A1 |
20040211230 | Recknagel et al. | Oct 2004 | A1 |
20040240934 | Makos et al. | Dec 2004 | A1 |
20040265049 | Hohmann et al. | Dec 2004 | A1 |
20050001408 | Irgens et al. | Jan 2005 | A1 |
20050022618 | Irgens et al. | Feb 2005 | A1 |
20050039504 | Smith et al. | Feb 2005 | A1 |
20050050695 | Mackey et al. | Mar 2005 | A1 |
20050051458 | Kopp et al. | Mar 2005 | A1 |
20050072199 | Edwards, Jr. | Apr 2005 | A1 |
20050092037 | Meekma et al. | May 2005 | A1 |
20050104327 | Irgens et al. | May 2005 | A1 |
20050151349 | Irgens et al. | Jul 2005 | A1 |
20050166649 | Meekma | Aug 2005 | A1 |
20050199019 | Marcelle et al. | Sep 2005 | A1 |
20050199628 | Van Handel et al. | Sep 2005 | A1 |
20050201076 | Marcelle et al. | Sep 2005 | A1 |
20060005586 | Smyczek et al. | Jan 2006 | A1 |
20060032280 | Edwards, Jr. et al. | Feb 2006 | A1 |
20060042336 | Smith et al. | Mar 2006 | A1 |
20060113261 | Recknagel et al. | Jun 2006 | A1 |
20060117821 | Edwards, Jr. | Jun 2006 | A1 |
20060119074 | Makos et al. | Jun 2006 | A1 |
20060162402 | Elliot et al. | Jul 2006 | A1 |
20060162403 | Handel | Jul 2006 | A1 |
20060163842 | Jacques | Jul 2006 | A1 |
20060204349 | Hohmann et al. | Sep 2006 | A1 |
20060208458 | Kalous et al. | Sep 2006 | A1 |
20060266090 | Brojanac et al. | Nov 2006 | A1 |
20060266631 | Kalous et al. | Nov 2006 | A1 |
20060278504 | Brojanac | Dec 2006 | A1 |
20060279067 | Irgens et al. | Dec 2006 | A1 |
20060283215 | Manthe et al. | Dec 2006 | A1 |
20060283216 | Marcelle et al. | Dec 2006 | A1 |
20060284399 | Scott et al. | Dec 2006 | A1 |
20060289369 | Sheridan et al. | Dec 2006 | A1 |
20060290103 | Kottke et al. | Dec 2006 | A1 |
20070007782 | Kalous | Jan 2007 | A1 |
20070012834 | Elliott et al. | Jan 2007 | A1 |
20070018541 | Hacker et al. | Jan 2007 | A1 |
20070113600 | Marcelle et al. | May 2007 | A1 |
20070125680 | Konop et al. | Jun 2007 | A1 |
20070220932 | Meekma et al. | Sep 2007 | A1 |
20070234766 | Rohde et al. | Oct 2007 | A1 |
20070240468 | Kalous | Oct 2007 | A1 |
20070240766 | Brojanac et al. | Oct 2007 | A1 |
20070257772 | Marcelle et al. | Nov 2007 | A1 |
20070266747 | Rafferty et al. | Nov 2007 | A1 |
20080000278 | Brojanac et al. | Jan 2008 | A1 |
20080001052 | Kalous et al. | Jan 2008 | A1 |
20080061530 | Recknagel et al. | Mar 2008 | A1 |
20080067043 | Brojanac | Mar 2008 | A1 |
20080081494 | Larsen et al. | Apr 2008 | A1 |
20080092606 | Meekma | Apr 2008 | A1 |
20080098939 | Kalous et al. | May 2008 | A1 |
20080100426 | Kalous et al. | May 2008 | A1 |
20080106392 | Kalous et al. | May 2008 | A1 |
20080127866 | Hacker et al. | Jun 2008 | A1 |
20080129158 | Kalkwarf | Jun 2008 | A1 |
20080129169 | Daino et al. | Jun 2008 | A1 |
20080129172 | Freeberg et al. | Jun 2008 | A1 |
20080129173 | Freeberg et al. | Jun 2008 | A1 |
20080141745 | Rohde et al. | Jun 2008 | A1 |
20080148548 | Rohde et al. | Jun 2008 | A1 |
20080150407 | Mehmen | Jun 2008 | A1 |
20080173049 | Burmesch et al. | Jul 2008 | A1 |
20080184748 | Burmesch | Aug 2008 | A1 |
20080202181 | Burmesch et al. | Aug 2008 | A1 |
20080209962 | Peot et al. | Sep 2008 | A1 |
20080210577 | Van Handel et al. | Sep 2008 | A1 |
20080296330 | Kalous et al. | Dec 2008 | A1 |
20080314093 | Nave | Dec 2008 | A1 |
20090007614 | Armstrong et al. | Jan 2009 | A1 |
20090072956 | Kalous | Mar 2009 | A1 |
20090079163 | Cuellar et al. | Mar 2009 | A1 |
20090145178 | Nave et al. | Jun 2009 | A1 |
20090173655 | Konop et al. | Jul 2009 | A1 |
20090183534 | Brojanac | Jul 2009 | A1 |
20090193860 | Meekma | Aug 2009 | A1 |
20090205934 | Brojanac | Aug 2009 | A1 |
20090223258 | Burmesch et al. | Sep 2009 | A1 |
20090223852 | Konop et al. | Sep 2009 | A1 |
20090266119 | Brojanac et al. | Oct 2009 | A1 |
20090282879 | Marcelle et al. | Nov 2009 | A1 |
20090308113 | Meekma et al. | Dec 2009 | A1 |
20100043508 | Burmesch et al. | Feb 2010 | A1 |
20100073478 | Kalous | Mar 2010 | A1 |
20100102572 | Burmesch | Apr 2010 | A1 |
20100180804 | Czarnecki et al. | Jul 2010 | A1 |
20100192641 | Nave | Aug 2010 | A1 |
20100219098 | Konop et al. | Sep 2010 | A1 |
20100281930 | Hacker | Nov 2010 | A1 |
20110011139 | Marcelle et al. | Jan 2011 | A1 |
20110056567 | Brojanac et al. | Mar 2011 | A1 |
20110057461 | Brojanac | Mar 2011 | A1 |
20110067461 | Hacker | Mar 2011 | A1 |
20110100074 | Meekma et al. | May 2011 | A1 |
20110132049 | Meekma et al. | Jun 2011 | A1 |
20110185775 | Edwards, Jr. et al. | Aug 2011 | A1 |
20110209506 | Johnson et al. | Sep 2011 | A1 |
20110239714 | Trempala | Oct 2011 | A1 |
20110277853 | Burmesch | Nov 2011 | A1 |
20120000255 | Nave et al. | Jan 2012 | A1 |
20120011902 | Meekma | Jan 2012 | A1 |
20120047973 | Su et al. | Mar 2012 | A1 |
20120085136 | Burmesch et al. | Apr 2012 | A1 |
20120103033 | Kalous | May 2012 | A1 |
20120180537 | Burmesch et al. | Jul 2012 | A1 |
20120266636 | Nave | Oct 2012 | A1 |
20120273330 | Wojtak | Nov 2012 | A1 |
20130019641 | Burmesch et al. | Jan 2013 | A1 |
20130052846 | Johnson | Feb 2013 | A1 |
20130086956 | Nave | Apr 2013 | A1 |
20130118216 | Kalous et al. | May 2013 | A1 |
20130120110 | Kalous et al. | May 2013 | A1 |
20130174621 | Barraza et al. | Jul 2013 | A1 |
20130214903 | Kalous et al. | Aug 2013 | A1 |
20130219793 | O'rourke | Aug 2013 | A1 |
20130255335 | Jonely | Oct 2013 | A1 |
20130264128 | Plato et al. | Oct 2013 | A1 |
20130276487 | Burmesch et al. | Oct 2013 | A1 |
20130335199 | Jonely | Dec 2013 | A1 |
20130335200 | Jonely | Dec 2013 | A1 |
20140027507 | Jonely | Jan 2014 | A1 |
20140028443 | Ebner | Jan 2014 | A1 |
20140060126 | Stevens | Mar 2014 | A1 |
20140060128 | Fuller et al. | Mar 2014 | A1 |
20140130722 | Dudgeon et al. | May 2014 | A1 |
20140152420 | Wolski | Jun 2014 | A1 |
20140157838 | Nave | Jun 2014 | A1 |
20140165384 | Dudgeon et al. | Jun 2014 | A1 |
20140166462 | Jonely et al. | Jun 2014 | A1 |
20140167391 | Elliott et al. | Jun 2014 | A1 |
20140250955 | Miller et al. | Sep 2014 | A1 |
20140283008 | Daino et al. | Sep 2014 | A1 |
20150170447 | Buzhardt | Jun 2015 | A1 |
20150217918 | Rozanski | Aug 2015 | A1 |
20160035163 | Conrad et al. | Feb 2016 | A1 |
20160036594 | Conrad et al. | Feb 2016 | A1 |
20160036788 | Conrad et al. | Feb 2016 | A1 |
20160036814 | Conrad et al. | Feb 2016 | A1 |
20160056656 | Jonely | Feb 2016 | A1 |
20160105406 | Smith et al. | Apr 2016 | A1 |
20160105644 | Smith et al. | Apr 2016 | A1 |
20160105847 | Smith et al. | Apr 2016 | A1 |
20160116510 | Kalous et al. | Apr 2016 | A1 |
20160145902 | Kalous | May 2016 | A1 |
20160342820 | Jonely | Nov 2016 | A1 |
20170113856 | Hollis et al. | Apr 2017 | A1 |
20170140595 | Kalous et al. | May 2017 | A1 |
20170146124 | Daino et al. | May 2017 | A1 |
20170234036 | Ebner | Aug 2017 | A1 |
20170234038 | Sanford | Aug 2017 | A1 |
20170236352 | Conrad et al. | Aug 2017 | A1 |
20170236353 | Conrad et al. | Aug 2017 | A1 |
20180016812 | Sanford | Jan 2018 | A1 |
20180106871 | Kalous et al. | Apr 2018 | A1 |
20180171663 | Ebner | Jun 2018 | A1 |
20180223567 | Hollis | Aug 2018 | A1 |
20180253920 | Kalous et al. | Sep 2018 | A1 |
20180270232 | Conrad | Sep 2018 | A1 |
20180293396 | Daino et al. | Oct 2018 | A1 |
20200095804 | Pavlovic et al. | Mar 2020 | A1 |
20210207402 | Pavlovic et al. | Jul 2021 | A1 |
Number | Date | Country |
---|---|---|
WO 2014 089156 | Jun 2014 | WO |
Entry |
---|
US 9,039,431 B2, 05/2015, Johnson (withdrawn) |
Newton, Newton's Telecom Dictionary, 27th Expanded and Updated Edition, 2013, p. 588. |
PC Magazine Encyclopedia, Definition of Heartbeat, https://www.pcmag.com/encyclopedia/term/44190/heartbeat, accessed Sep. 14, 2019. |
PCT Search Report dated Dec. 4, 2019 for International Application No. PCT/US2019/051775, filed Sep. 18, 2019, 22 pages. |
Number | Date | Country | |
---|---|---|---|
20230287709 A1 | Sep 2023 | US |
Number | Date | Country | |
---|---|---|---|
62734742 | Sep 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17119967 | Dec 2020 | US |
Child | 18147614 | US | |
Parent | 16574801 | Sep 2019 | US |
Child | 17119967 | US |