A door lock assembly for use with a door having a frame element that includes a main body and a pair of opposed sides that forms a channel therebetween. One of the sides of the main body has a connector portion. The assembly also includes a movable locking assembly that is coupled to the connector portion of the frame element and has one or more elongated locking elements that is movable between a locked position and an unlocked position. The assembly also includes a latch assembly configured for coupling a door to a door frame, and if desired an actuator assembly.
|
1. A door lock assembly for use with a door, comprising
a frame element having a main body and a pair of opposed sides forming a channel therebetween, wherein one of the sides has a connector portion, and
a movable locking assembly pivotally coupled to the connector portion of the frame element and having one or more elongated locking elements movable between a locked position and an unlocked position,
wherein the movable locking assembly includes
at least first and second locking elements each of which has a main body having a locking element connector portion disposed at one end thereof that is sized and dimensioned for mating engagement with the connector portion of the frame element,
a coupler element having a main body having a first end and a second end, and
a drive element having a main body having a first end and a second end,
wherein, when assembled, the first end of the drive element is coupled to the first end of the coupler element, the first locking element is coupled to the second end of the drive element, and the second end of the coupler element is coupled to the second locking element, and
wherein, when assembled, the movable locking assembly is disposed substantially within the channel formed in the frame element when disposed in the unlocked position, and extends outwardly from the channel of the frame element when disposed in the locked position,
wherein each locking element of the movable locking assembly is a rail style, wedge-shaped locking element,
wherein the first end of the drive element forms a coupler receiving end and has a cut-out formed therein.
2. The door lock assembly of
3. The door lock assembly of
4. The door lock assembly of
5. The door lock assembly of
6. The door lock assembly of
wherein the boss portion of the first end of the coupler element has a connection element formed thereon, and
wherein the first end of the drive element forms a coupler receiving end and has
a cut-out portion formed therein that is adapted to receive the boss portion of the coupler element, and
a recess sized and configured for receiving the connection element so as to secure the first end of the coupler element to the first end of the drive element.
7. The door lock assembly of
8. The door lock assembly of
a locking element connector portion disposed at one end thereof that is sized and dimensioned for mating engagement with the connector portion of the frame element, and
an elongated channel disposed at a location that is spaced from the connector portion.
9. The door lock assembly of
10. The door lock assembly of
12. The door lock assembly of
13. The door lock assembly of
a latch piston element having
first and second opposed latch guide legs, wherein at least one of the first and second legs has a channel formed therein,
a hub region having a first end coupled to the legs and a second end coupled to a piston element, and
a space formed in the first end of the hub region,
a latch hub element having a boss element,
a latch piston actuator element having a main body that includes a cam element formed thereon, wherein the cam element is sized and dimensioned to seat within the channel formed in one of the first and second latch guide legs during use,
a biasing element having a first end coupled to the boss element which forms a biasing element seat, and a second end of which contacts an inner wall of the space formed in the hub region, and
a latch element coupled to the piston element of the latch piston element.
14. The door lock assembly of
15. The door lock assembly of
wherein, during use, the latch hub is rotated such that the cam element is disposed within the channel formed in one of the latch guide legs so as to contact an end portion of the channel so as to move the latch piston element in a first linear direction, the movement of the latch piston element in the first linear direction moves the latch element into the retracted position, and when the latch hub is rotated in an opposite direction such that the cam element is disengaged from the latch guide leg, the latch piston element moves in a second direction which is opposite to the first direction by the biasing element so as to dispose the latch element in the engaged position.
|
|||||||||||||||||||||||||||
This application is a Continuation application of U.S. patent application Ser. No. 14/194,284 filed Feb. 28, 2014, now U.S Pat. No. 9,702,168, which claims priority to U.S. Provisional Patent Application No. 61/770,605, filed on Feb. 28, 2013 and entitled “FRAME BASED DOOR LOCK FOR DWELLING.” The contents of the aforementioned patent application are incorporated herein by reference.
Traditional entryways into a dwelling are typically contain an entry door system. The entry door allows ingress and egress to the dwelling. A typical entry door system includes a door frame that includes a plurality of hinge mechanisms that pivotably mount a door panel. The door panel typically includes a handle that has a latch mechanism that cooperates with a strike plate mounted in the frame to hold the door in a closed position. One or more locks can be provided to secure or lock the door in the close position. These conventional locks typically include a handle based or mounted lock that locks or secures the latch in the deployed position, thus locking the door relative to the frame. In addition, entry door systems can also include a deadbolt that provides a further and separate means for locking the door in the closed position.
A disadvantage of traditional door entry systems of this type are that they have a single or at most dual point of locking connection between the door panel and the frame. Hence, by applying the appropriate amount of force to the door panel at the locking sites, the door panel can typically be forced open. Further, the entry door system typically provides one or more seals between the frame and the door in an attempt to provide a fluid tight seal. However, the locking mechanisms themselves do not function as sealing elements, and there is typically an issue associated with these types of door panel seals. In many instances, the seals are not effective at preventing the transfer of environmental elements such as noise, weather, water, and insects from one side of the panel to the other side.
Prior attempts have been made to address these issues by using various types of weather stripping between the panels and frame. For example, the weather stripping may be a strip of felt, foam, or a pile of flexible synthetic material. In many instances, however, this weather stripping fails to act as a sufficient seal between the door panel and the frame. Another prevalent issue associated with seals formed between the door frame and the door panel or between adjacent panels is that these seals can become disjoined. Either intentionally or unintentionally, the alignment between the frame and the panel or between adjacent panels may be disturbed which can degrade the quality of the seal, since, in many instances, the integrity of the seal relies upon these members having certain positional relationships relative to one another.
The present invention is directed towards a door panel based or a frame based door lock assembly or system that can lock, seal and secure an entrance to a dwelling. The door lock assembly of the present invention can according to a first embodiment be formed and mounted within a door frame and has a movable locking element that, when deployed, locks and seals the door to the frame.
The present invention is also directed towards a door panel based door lock assembly or system that can also lock, seal and secure an entrance to a dwelling. The door lock assembly of the present invention is formed and mounted within a door panel and has a movable locking element that, when deployed, locks and seals the door to the frame.
The present invention is also directed towards a system and method for a user to register the door lock assembly and to control and manage the state and access rights of the door lock assembly of the present invention.
According to one practice, a door lock assembly for use with a door includes a frame element having a main body and a pair of opposed sides that forms a channel therebetween. One of the sides of the main body has a connector portion. The assembly also includes a movable locking assembly that is coupled to the connector portion of the frame element and has one or more elongated locking elements that is movable between a locked position and an unlocked position. The assembly also includes a latch assembly configured for coupling a door to a door frame, and if desired an actuator assembly. The connector portion of the present invention has a curved shape, such as a substantially C-shaped configuration. Moreover, the locking element of the movable locking assembly is a rail style, wedge-shaped locking element.
Each of the locking elements of the movable locking assembly has a main body having a locking element connector portion disposed at one end thereof that is sized and dimensioned for mating engagement with the connector portion of the frame element. When coupled together, the locking element connector portion and the connector portion of the frame element form a pivot point enabling the locking element to move between the locked and unlocked positions. Moreover, when disposed in the unlocked position, the locking element is disposed substantially within the channel formed in the frame element, and when disposed in the locked position, at least a portion of the locking element extends outwardly from the channel of the frame element.
The movable locking assembly of the invention further comprises at least first and second locking elements each of which has a main body having a locking element connector portion that is disposed at one end thereof and which is sized and dimensioned for mating engagement with the connector portion of the frame element. A coupler element having a main body having a first end and a second end is provided, as well as a drive element having a main body having a first end and a second end. When assembled, the first end of the drive element is coupled to the first end of the coupler element, the first locking element is coupled to the second end of the drive element, and the second end of the drive element is coupled to the second locking element. Further, the movable locking assembly is disposed substantially within the channel formed in the frame element when disposed in the unlocked position, and extends outwardly from the channel of the frame element when disposed in the locked position.
The main body of the coupler element has an intermediate portion that is narrower than the first and second ends, where each of the first and second ends of the drive element includes a skirt portion and an opposed boss portion that is narrower than the skirt portion. The boss portion of the first end of the coupler element has a connection element formed thereon, and the first end of the drive element forms a coupler receiving end and has a cut-out portion formed therein that is adapted to receive the boss portion of the coupler element. A recess that is sized and configured for receiving the connection element so as to secure the first end of the coupler element to the first end of the drive element is also provided.
Further, the main body of the first and second locking elements comprises an elongated channel disposed at a location that is spaced from the connector portion, and the assembly further comprises a resilient member that is coupled to the elongated channel.
According to the present invention, the latch assembly comprises a main body having a first main body portion and a second main body portion, which when coupled together, forms a mounting chamber. The latch assembly also includes a latch piston element having first and second opposed latch guide legs, wherein at least one of the first and second legs has a channel formed therein, a hub region having a first end coupled to the legs and a second end coupled to a piston element and a space formed in the first end of the hub region, and a latch hub element having a boss element. The latch assembly further includes a latch piston actuator element having a main body that includes a cam element formed thereon, where the cam element is sized and dimensioned to seat within the channel formed in one of the first and second latch guide legs during use. Further, the latch assembly includes a biasing element and a latch element. The biasing element has a first end that is coupled to the boss element to form a biasing element seat, and a second end of which contacts an inner wall of the space formed in the hub region. The latch element is coupled to the piston element of the latch piston element. The latch element is pivotably coupled to the main body of the latch assembly so as to move between an engaged position and a retracted position. More specifically, the latch piston element is movable in a linear direction so as to move the latch element between the engaged position and the retracted position.
During use, the latch hub is rotated such that the cam feature is disposed within the channel formed in one of the latch guide legs so as to contact an end portion of the channel. This mating engagement moves the latch piston element in a first linear direction. The movement of the latch piston element in the first linear direction moves the latch element into the retracted position. When the latch hub is rotated in an opposite direction, the cam feature is disengaged from the latch guide leg. The latch piston element then moves in a second direction which is opposite to the first direction by the biasing element so as to dispose the latch element in the engaged position.
These and other features and advantages of the present invention will be more fully understood by reference to the following detailed description in conjunction with the attached drawings in which like reference numerals refer to like elements throughout the different views. The drawings illustrate principals of the invention and, although not to scale, show relative dimensions.
The present invention is directed towards a frame based door lock assembly or system that can lock, seal and secure an entrance to a dwelling. The door lock assembly of the present invention is formed and mounted within a door frame and has a movable locking element that, when deployed, locks and seals the door to the frame. As used herein, the term “dwelling” is intended to include any partially or fully enclosed space that requires a door, such as a residential or commercial structure. Examples of dwellings contemplated by the present invention include houses.
The present invention is also directed towards a door panel based door lock assembly or system that can also lock, seal and secure an entrance to a dwelling. The door lock assembly of the present invention is formed and mounted within a door panel and has a movable locking element that, when deployed, locks and seals the door to the frame.
The present invention is also directed towards a system and method for a user to register the door lock assembly and to control and manage the state and access rights of the door lock assembly of the present invention.
As shown in
The illustrated frame element 26 includes a relatively flat portion 27 having a front surface and a back surface. The front surface of the frame element has formed thereon a number of surface features or protrusions. Specifically, the front surface of the frame element includes a channel housing 29 that forms a channel 28 therein. The channel is sized for accommodating any suitable wiring that needs to run along the door jamb. For example, according to one embodiment, the channel accommodates power conduits that connect at one end to the control panel and at the other end to a suitable power source. Examples of suitable power sources include door bell wiring and the like. The power conduits can include any suitable wiring or cable, such as electrical wiring, Ethernet cables and the like.
The front surface of the flat portion 27 of the frame also includes an integrally formed outwardly projecting lock connector portion 30 that includes a relatively flat extension 30A that has integrally formed therewith a curved connector element 30B that forms a lock receiving groove 30C. The lock receiving groove 30C is adapted to seat and mount a portion of the movable locking element 90 (
With reference to
As shown in
The control panel 22 includes a motor 32 for providing the power necessary to actuate the door locking assembly. The motor 32 includes a cam 34 that mounts to a shaft 33 of the motor. The cam is formed as an eccentric member that has a flanged end with a pin receiving aperture formed therein. The cam 34 is in turn coupled to a drive plate 40 via a cam pin 38 that serves to directly connect the plate to the cam. The cam when rotated by the motor shaft moves in a reciprocating manner, and this reciprocating motion is transferred to the drive plate 40. The shape of the cam element helps limit or define the axial movement of the drive plate 40.
The illustrated drive plate 40 includes, when viewed from the front, a substantially vertically disposed and axially extending lock connector portion 42 and an integrally formed, substantially horizontally disposed and axially extending cam connector portion 44. According to one embodiment, the lock connector portion 42 and the cam connector portion 44 are perpendicular relative to each other. The illustrated lock connector portion 42 includes a series of channels that allow for substantially linear movement of the drive plate when driving a locking element between the locked and unlocked positions, as explained below in further detail. Specifically, the drive plate 40 includes a first elongated channel 50 that is sized and configured for seating a fastener 62. The fastener is adapted to couple to a guide pin 72 for securing the drive plate to the frame element 26 of the lock assembly 20. The fastener 62 when mounted and seated within the channel 50 is adapted to travel within the channel upon movement of the drive plate, thus guiding the drive plate when moving in the axial direction A. The fastener thus operates to help secure the drive plate to the door frame while concomitantly ensuring that the drive plate moves or translates in a horizontal or axial direction (i.e., a direction perpendicular to the axis of the motor and the door frame).
The lock connector portion 42 of the drive plate 40 also includes a pair of parallel channels 52, 54 that are horizontally spaced in the axial direction from the channel 50. The channels 52 and 54 are also sized and configured for seating fasteners 64 and 66, respectively. The length of the channels 52, 54 are sized to allow translation of the drive plate in the axial direction without impeding movement thereof. The fasteners 64 and 66 threadingly engage with the guide pins 74 and 76, respectively, for also securing the drive plate to the frame element. The lock connector portion of the drive plate also includes a vertically extending groove 56 that seats an end portion of a drive pin 80. The drive plate at a terminal or axially outwardly most end terminates in a cut-out or groove. The groove 86 is sized and configured for seating a portion of a ramp assembly 100. Those of ordinary skill will readily recognize that the illustrated drive plate 40 can have any shape or configuration suitable for converting the rotational movement of the motor into linear movement of the plate, while concomitantly seating or mounting the required mechanical components.
As further illustrated in
The bottom portion 106 of the ramp member 102 includes a multi contoured top surface 126 and a multi-stepped bottom surface 128 that are bounded at each end by a flattened first terminal end 122 and a flattened second terminal end 124. The first terminal end 122 includes one or more fastener receiving apertures that are also adapted to seat the fasteners 138, and the opposed second terminal end 124 includes a flattened portion that has a tab engaging channel formed therein. The bottom surface 128 includes a series of steps that extend between the terminal ends and the step surface disposed adjacent the second terminal end 124 forms a drive plate engaging surface 132 sized and configured for seating within the groove 86 of the drive plate 40.
The multi contoured top surface 126 includes an initial flat surface 140 disposed adjacent the second terminal end 124 that transitions to a sloped surface 142 that has a rounded top portion that transitions to a detent groove 120 for seating a portion of the movable locking element when engaged therewith.
The bottom portion 106 and the top portion 104 of the ramp member 102 can be assembled together by inserting the tab portion 114 of the top portion of the ramp member into the tab engaging channel 130. When so assembled, the overlay portion 110 of the top portion overlies and mates with the first terminal end 122 of the bottom portion 106. When so assembled, the holes formed in the first ends of the top and bottom portion are aligned so as to receive the fasteners 138. The fasteners and the tab portion disposed in the channel 130 help secure the top and bottom portions of the ramp member together.
The illustrated door lock assembly also includes a pivot mechanism 150. The pivot mechanism 150 includes an aperture 156 formed at one end. The pivot mechanism is secured to the frame by way of fastener 152 that passes through the aperture 156 and seats within the guide pin 154. The guide pin in turn is secured to the frame element 26. A pair of drive pins 80, 158 can also be coupled to the pivot mechanism. The first drive pin 80 seats within a corresponding aperture formed in a bottom portion of the pivot mechanism and is sized and configured for seating in the U-shaped channel 56 of the drive plate. The second drive pin 158 seats within an aperture formed in a top portion, and specifically, an extension portion, of the pivot mechanism and is sized for seating in a channel 174 formed on a rear surface of a manual control element 170.
With reference to
The illustrated manual control element 170 also includes a guide portion 180 and a flange 182 extending outwardly the back surface 176B of the latch portion 176. The guide portion 180 includes a pair of substantially parallel channels 184, 186. The inner channel 184 has an overall length that is smaller than the length of the outer channel 186, and the inner channel 184 is offset from the outer channel 186 in the longitudinal direction of the guide portion. The inner channel 184 is adapted to seat a fastener 188 that is coupled to a guide pin 190 disposed on the opposed side of the channel. The outer channel 186 is adapted to seat a pair of fasteners 192, each of which is coupled to a guide pin 194. Similar to the other guide pins, the guide pins 190, 194 secure selected elements of the door lock assembly to the frame element.
As shown in
In operation, when the door lock assembly is fully assembled and integrated within the door frame, the movable locking element 90 can be moved between an unlocked position where the element is stored within the frame and specifically within the groove 92, and a locked position where the movable locking element is moved pivotably outwardly from the groove 92 so as to seat within a channel formed in a side of the door panel. With reference to the foregoing Figures, and with particular reference to
When the unit is not actuated, the lock can be disposed for example in the unlocked position (
When the unit is actuated, as shown in
When the locking element 90 contacts the engaging portion 204 of the sealing element 202, the locking element forms a strong sealing and locking connection. Indeed, any additional force applied to the door panel from an outside surface or side enhances and strengthens the sealing contact between the locking element 90 and the sealing element 202.
Those of ordinary skill will readily recognize that the battery 58 housed within the door lock assembly 20 can power one or more of the other components of the assembly either directly or indirectly. The battery can be charged during periods of non-use by a power source, such as through any local electrical connection.
The control panel 22 which forms part of an overall control box can be formed as a modular component. As such, if the control box needs to be replaced, the old box can be disconnected or removed from the frame and a new box can be installed. Hence, the control box is a removable and replaceable component of the door lock assembly 20.
Another feature of the present invention is that the door lock assembly 20 can be constructed so that the motor drives the drive plate, cam and hence locking element into the locked or unlocked position to provide a final sealing function, if moved into the locked position, or a final stowing function if moved into the unlocked position.
In further operation, the door lock assembly may be controlled by a suitably programmed computing device. In one exemplary embodiment, the computing device may be a mobile computing device such as a cell phone, smart phone, watch, tablet computer, or customized device such as a fob, or any other suitable electronic device. The computing device may include a wireless transmitter, such as a radio antenna, for wirelessly communicating with the lock. It should be noted that the lock may be controlled by any alternative means which include a method for identifying a user, such as by entering a user-assigned pin number on a keypad, or biometric authentication (e.g., using a fingerprint, facial recognition, voice commands, or other means), among other possibilities.
The computing device may be programmed to set up and manage a door lock assembly at one or more access points in a dwelling or other secured area, which may include identifying the specific lock, designating an owner or administrator for the lock, and registering users who have rights to perform actions with respect to the lock. Such actions may include locking or unlocking the door lock assembly, viewing the current status of the lock (e.g., “locked” or “unlocked”), accessing a camera associated with the lock, viewing a log of when the lock's status was changed, etc. Furthermore, such actions may include administrative actions, such as recognizing and registering a new lock, inviting users to have access rights to the lock, restricting users from using the lock and/or limiting access rights for existing users of the lock.
Actions and rights may be applied to a particular door lock assembly, or may be applied together to a group of locks organized into common locations (e.g., the “My House” location may have a Front Door lock, a Back Door lock, and a Garage Door lock). Similarly, individual users may be managed using the computing device, or users may be grouped together and managed as a group.
Access and/or administrative rights over locks may be restricted to certain times for particular users. For example, a user may be assigned “guest” access rights which last for a specified period of time (e.g., one week) or until a specified time (e.g., until April 1 at 6:00 PM).
Exemplary interfaces for setting up and administering a lock and managing users of the lock are described below, with reference to
In order to gain rights to access and manage locks, a user may first register an account, as shown in the exemplary account registration interface 300 of
The account registration interface 300 may include an identification dialog 302 for entering an identifier, such as a name. The identifier may be, for example, an alphanumeric string. The identifier may be used to identify the account associated with the user.
The account registration interface 300 may further include a code entry 304 for entering a secret or non-public code associated with the user's account. The code may be required in order to take actions related to the account, such as changing the status of a lock to which the account has access rights and/or administering a lock (e.g., adding guest users to the lock). The code may be selected by the user, or may be assigned by the registration software (e.g., by choosing a random number). The pin may be, for example, alphanumerical or strictly numerical.
Optionally, the account registration interface 300 may include a remote administration option 306. The remote administration option may allow the user's account settings to be stored in a remote location, such as a centralized server. This option allows for account recovery, in case the user's account information is accidentally deleted from the local actuation or mobile device. Furthermore, by saving the user's account information remotely, the user can access the account from a device that is different than the actuation device on which the original account registration was completed.
In one embodiment, no account or lock information is saved remotely. Rather, the account and lock information resides solely on the user actuation devices and the locks themselves. For example, the lock may be provided with a non-transitory storage medium which is in physical contact or short range wireless communication (e.g., less than 100′, or as determined by typical ranges associated with a short-range wireless protocol such as a typical WiFi transmitter or Bluetooth® transmitter) with the locking mechanism. Thus, all the “keys” associated with the lock may be stored securely in the locking mechanism itself. In this way, there is no central storage location which could be compromised, thereby also compromising all the locks and user accounts stored in the central storage location. Hence, the actuation or mobile device operates or functions as a universal key since it can be programmed to open any particular lock in any particular dwelling. As such, the actuation device can be deemed to be an identity based device since it is associated with the user and whether that user has permission to enter a specific dwelling rather than a lock specific device.
When a user wishes to register a new lock so that the lock may be managed, the user may perform an initial setup procedure for the lock using registration software, as shown in
The lock and/or registration software may be provided with authentication capabilities to ensure that only an authorized user sets up the lock. For example, the lock may be configured to respond only to a handshake from a predetermined setup account. Upon purchasing the lock, the user may be provided with information allowing the user to access the predetermined setup account (e.g., an access code unique to the lock which, when entered into the registration software, allows the registration software to communicate with the lock), and thereby set up the lock.
Once the registration software has successfully connected to the lock, the interface 308 may be updated so that the status bar indicates the identity of the lock, as shown in
Upon selecting the interface configuration element 312, a configuration interface 314 may be presented for configuring basic information about the lock, as depicted in
Multiple door lock assemblies may be associated with a particular location, such as by assigning the locks a common location identifier. In one embodiment, locks with a common location identifier may be administered and/or accessed together as a group or a single entity. For example, if a user is given access rights to lock/unlock a particular location (e.g., “John's House”), then the user may lock or unlock any and/or all locks associated with the location (e.g., “John's Front Door” or “John's Back Door”).
A graphic identification element 318 may be provided for allowing a user to create or select a graphic representing the lock. For example, the graphic identification element 318 may present an option to select an existing photograph, such as a photograph stored on the user's mobile phone or on a remote server, to represent the lock. Alternatively or in addition, if the registration software detects that it is running on a device (such as a mobile phone) that is equipped with a camera, the graphic identification element 318 may prompt the user to take a picture of the lock or the fixture in which the lock is installed (e.g., a door, garage door, window, etc.). The picture may be used to identify the lock. Alternatively or in addition, the registration software may be provided with preconfigured graphics that may be used to represent the lock. Upon selecting the graphic identification element 318, the user may be presented with the preconfigured graphics and prompted to select a preconfigured graphic to represent the lock.
Upon selecting or creating a graphic to represent the lock, an editing interface 320 may optionally be presented, as shown in
After the lock is set up, the registration software may prompt the user to define an administrator for the lock in an administrator interface 322, as depicted in
The administrator may be a permanent administrator, or a temporary administrator may be defined. The administrator interface may include a timeline configuration tool with a starting input 324 and an ending input 326. The starting input 324 and the ending input 326 may be used to identify, respectively, when the administrator's term as an administrator begins and ends. A permanent administrator may be established by setting, for example, the starting input 324 to “immediately” and the ending input 326 to “never.” A temporary administrator may be established by setting specific starting and ending times defining the temporary administrator's term. If a temporary administrator is established and the temporary administrator's term expires without providing a new administrator, then the temporary administrator may be prompted to select a new administrator.
When an administrator is removed from a lock, the lock may optionally be placed into escrow. This may be particularly applicable when a property such as a house is sold and administration of the locks on the house is passed to a new owner. Secure ownership of locks associated with a particular location may be transferred to a third party, such as an escrow company. When ownership of the property is transferred to a new owner, the escrow company may transfer ownership and administration privileges for the locks to the new owner as well.
Similarly, if a transfer is made directly from the old owner to the new owner, the old owner may securely relinquish access rights directly to the new owner by specifying that the new owner should become an administrator on a certain date, and by specifying that the old owner's administration privileges expire on that date.
Alternatively, the old owner may relinquish administration privileges without specifying a new administrator. In this case, the lock may return to a factory-default setting and await a claim by an owner with the lock's original predetermined setup information. In another embodiment, the old owner may specify a code that, when entered by the new owner, causes ownership and/or administration privileges of the lock or locks at a particular location to pass to the new owner.
In the above-described embodiments, a user device such as a mobile phone may be configured to function with (e.g., administer or access) a lock by registering the lock with a user account associated with the user device. It should be noted that multiple user devices may be registered with the user account.
For example, if a user account is initially set up on a mobile device such as a phone, the user may also authorize a custom fob to work with the user account. The mobile device may take ownership of the fob by programming the fob with a group ID or location ID associated with a location (e.g., a group of locks that are related to each other or in proximity to each other, such as locks on a particular house), or an account ID associated with the user account. A device ID and/or token associated with the fob may similarly be added to the user account (e.g., in a database or data structure on the mobile device or a central server which stores registration information for user accounts). Any number of hardware devices and/or access methods may be associated with a user account.
In a similar manner, a hardware device that is associated with a user account may be removed from the user account and/or associated with a different user account. Thus, ownership of the hardware device may be securely transferred between users.
Alternatively or in addition to the above registration procedures, a user who initially does not have access rights to access a particular lock may request such access rights.
The lock may be a private lock associated with one or more owners, as noted above, or may be a common, public, or shared lock which may be accessible by a user if the user meets certain criteria. For example, a restroom may have a lock that is only accessible by users of the appropriate gender. In some cases, any member of the public may request access to the public lock, while in other cases access to the lock may be restricted (e.g., an employees' restroom may be accessible only to people who work at a particular company).
The user may approach the lock with a mobile device, fob, or other device and place both the lock and the device into a pairing mode. This may be accomplished in a single action, for instance by tapping the device to the lock. Alternatively, the lock and device may be separately placed into pairing mode by issuing commands to the lock and/or device.
The lock and device may attempt to pair with each other and, if successful, the lock and/or device may identify that the device is not authorized to access the lock. Accordingly, a message may be displayed to the user on the device indicating that the user does not have access to the lock, and querying whether the user would like to request access. The device may accept the user's request to access the lock.
If the lock is a private lock, the request may be transmitted to one or more owners of the lock, who may then approve or deny the request. If the request is approved, the user may be provided with the necessary privileges to access the lock, as described in more detail below. Alternatively or in addition, the owner may simply be notified that the user is waiting at the lock (e.g., through a bell or chime similar to a doorbell), in which case the owner may remotely unlock the door. In another embodiment, tapping an unauthorized device to the lock may cause the device to initiate a telephone call or video chat with the owner of the lock.
If the lock is a public lock, an interface may be presented for entering information about the user of the device. The information may include identifying information, such as a name and/or a phone number, and/or may be descriptive. The descriptive information may be used to determine whether the user is permitted to access the lock. In the example above regarding the restroom, the user may be queried as to whether they are male or female. Once the information is entered, the lock, device, and/or a remote server may determine, based on the user's responses, the user is authorized to access the lock. The lock may store records, including the entered information and/or a timestamp, relating to attempts to access the lock by the electronic device. In this way, a history of which users entered the room secured by the lock may be maintained.
In some situations, the user may be requested to provide authenticating information to determine whether the user is permitted to access the lock. For example, if the lock secures an employees' restroom as in the example above, the user may be asked to provide their employee ID number, login password, or another identifier.
Accordingly, users without access to a private or public lock may request that they be granted access to the lock.
After initial setup, users with appropriate access rights to the lock may manage the state of the lock through a suitable interface. For example,
The management interface 328 may include a selection mechanism 330 for choosing a particular lock associated with the user's account. In the exemplary management interface 328, two locks are associated with the user account, as indicated by the two dots in the center/top of the display, and the selection mechanism allows for a selection of one of the two locks to be made. Identification indicia 332 provides general information about the currently-selected lock, such as a name and/or address of the lock and a graphic representing the lock.
A locking mechanism 334, such as a button or a slider, may be presented for changing the status of the lock (e.g., to “locked” or “unlocked”). The locking mechanism 334 may display the current status of the lock, or the current status may be displayed separately from the locking mechanism 334.
Upon activating the locking mechanism 334, a signal may be sent to a processing device associated with the lock, which actuates the lock to change the lock's status to reflect the user's selection. In exemplary embodiments, the user device may communicate with the lock through a wireless signal, such as a Bluetooth® signal. The user device may be pre-paired with the lock or otherwise preauthorized to use the lock so that the user device can simply transmit a “lock” or “unlock” signal without the requirement of discovering the lock and performing initial setup when the lock is first encountered.
In one embodiment, the lock may communicate with user devices through a courier that connects the lock to a secure remote server. Accordingly, user devices may not communicate with the lock except through a secure connection. In other embodiments, the lock may communicate directly with user devices using a secure protocol.
Upon receiving a lock or unlock signal, the lock may automatically take action to actuate the internal locking mechanism (as described in detail above), thereby locking or unlocking the lock.
A log of actions taken with respect to the lock may be maintained and viewed by certain users who have the right to access the log. For example, every time the lock is unlocked or locked, the time and user who initiated the action may be noted in the log. When additional users are given rights to the lock or when existing users are restricted from using the lock or have access rights restricted, such administrative changes may also be noted in the log. The log may be stored on a computing device associated with an administrator of the lock, at a central location connected to the lock and/or users of the lock through a network, or on the lock itself.
The management interface 328 may include a log summary 336 describing the most recent action take with respect to the lock. For example, the log summary 336 may display the last time the lock's status was changed, what the status was changed to, and which user changed the status. This information may be retrieved from the log if the user has sufficient privileges to view the information in the log. If the user does not have sufficient access rights to view the log, then the registration software may abstain from displaying the log summary 336.
A user with administrator rights to a lock may invite additional users to have access rights to the lock. For example,
The registration software may access a contacts list 338 of the administrator, as shown in
Upon selecting a user 340, the administrator may be presented with a user administration interface 342, as shown in
An access rights level selector 346 may be provided to assign different sets of access rights to the user. For example, a user who is designated is a “guest” may have rights to change the status of a lock (e.g., to lock or unlock the door lock assembly). A user who is designated as an “administrator” may be permitted to invite other users to have access rights over the lock.
A temporal limitation selector 348 may allow the administrator to define a time period for which the invited user is permitted to access or administer the lock. The user may be given permanent rights to the lock by assigning a start time of “immediately” and an end time of “never.” Alternatively, the user may be given temporary rights by defining a particular time frame in which the user is permitted to access the lock.
Upon selecting a user and configuring the user's rights with respect to the lock, an invitation may be generated and transmitted to the user. For example, the invitation may be sent to a mobile device defined by an identifier associated with the user in the contacts list 338 (e.g., a phone number or an email address).
When the invitation is sent to the user, the user may be presented with an invitation interface 350, as depicted in
If the invitation is accepted, the lock may be added to the user's account. For example, the user's mobile device or fob may include a non-transitory storage medium storing one or more tokens, where each token represents a lock or group of locks to which the user has access rights.
In one embodiment, locks may be represented on a client-side storage medium as participants in a “chat room.” One or more chat rooms on the client device may represent locations to which the client has access rights (e.g., “My House”). Within the chat room, one or more locks may be represented as participants (e.g., in the “My House” chat room, participants may include “My Garage,” “My Front Door,” “My Back Door,” etc.). When approaching a particular location defined by a chat room (as determined, e.g., by GPS coordinates), the members of the chat room may be determined and any requisite setup may be performed (e.g., pre-pairing the user device with the lock, as described in more detail below) so that the user can simply approach the lock and request that the lock be opened.
Thus, details about which locks a user has access to may be stored directly on the user's device, thereby turning a single “key” (i.e., the user's device) into an access mechanism opening any lock to which the user has rights. Instead of the conventional technique where a key provides access to a single lock, in exemplary embodiments of the present invention a key is tied to a user's identity and may open any lock to which the user has been assigned access rights.
The lock may be pre-paired with the user's device so that the user will be able to immediately change the status of the lock without the need to search for, discover, and/or initially pair with the lock. For example, the invitation may include pairing information for the lock (such as an identifier, access code, protocol, and/or frequency which may be used to communicate with the lock) so that the user's device may be preconfigured with sufficient information to allow the user's device to communicate with the lock immediately. In this manner, the user device may be preauthorized to communicate with the lock.
A user with sufficient rights may be presented with administrative details regarding the lock. For example,
The administrative details may include options 362 for enabling auto-locking and auto-unlocking of the door lock assembly. When auto-locking or auto-unlocking is enabled, the status of the lock may be changed based on the proximity of the user's device to the lock. When the user's device approaches to within a predetermined distance of a door panel of the dwelling or enclosure where the door lock assembly is disposed in the locked position, the lock may detect the presence of the user's device and automatically move the lock into the unlocked position. The presence of the user's device may be determined, for example, by using a predetermined wireless signal such as a Bluetooth® signal or a Wi-Fi signal. The distance to the device may be determined, among other options, using a Global Positioning System (GPS) signal, triangulation with cellular towers or other wireless transmitters/receivers.
Furthermore, the administrative details may include a list 364 of users who have access rights (as administrators and/or as guests) to the door lock assembly. Using the list 364, the user accessing the administrative interface 358 may access a profile of the selected user to determine what rights the user has with respect to the identified lock 360. If the user accessing the administrative interface 358 has sufficient rights, the user may be presented with a removal option 366 to remove all access rights from a selected user in the list 364.
Thus, a user with administrator privileges may remove a user's registration from a particular lock, thereby eliminating the removed user's rights to access the lock. Alternatively, a user may remain registered with the lock, but their rights may be modified (e.g., by adding or removing administrator privileges from the user, by changing a temporary guest user into a permanent user, or by changing a permanent user into a temporary guest user, among other possibilities).
A user may also wish to determine whether they have access rights in a particular lock. Accordingly, a user may search for existing locks in order to (for example) request access to the lock from the lock's owner or identify the presence or level of access rights that the user has with respect to a particular lock.
A lock administrator may choose to have their lock appear in search results, or not appear in search results. In one embodiment, locks may appear in a user's search results only if the lock is administered by a person in the user's contact list (e.g., on the user's mobile phone).
One or more of the above-described acts may be encoded as computer-executable instructions executable by processing logic. The computer-executable instructions may be stored on one or more non-transitory computer readable media. One or more of the above described acts may be performed in a suitably-programmed electronic device.
The electronic device 400 is illustrative and may take other forms. For example, an alternative implementation of the electronic device 400 may have fewer components, more components, or components that are in a configuration that differs from the configuration of
The processor 402 may include hardware based logic or a combination of hardware based logic and software to execute instructions on behalf of the electronic device 400. The processor 402 may include logic that may interpret, execute, and/or otherwise process information contained in, for example, the memory 404. The information may include computer-executable instructions and/or data that may implement one or more embodiments of the invention. The processor 402 may comprise a variety of homogeneous or heterogeneous hardware. The hardware may include, for example, some combination of one or more processors, microprocessors, field programmable gate arrays (FPGAs), application specific instruction set processors (ASIPs), application specific integrated circuits (ASICs), complex programmable logic devices (CPLDs), graphics processing units (GPUs), or other types of processing logic that may interpret, execute, manipulate, and/or otherwise process the information. The processor may include a single core or multiple cores 403. Moreover, the processor 402 may include a system-on-chip (SoC) or system-in-package (SiP).
The electronic device 400 may include one or more tangible non-transitory computer-readable storage media for storing one or more computer-executable instructions or software that may implement one or more embodiments of the invention. The non-transitory computer-readable storage media may be, for example, the memory 404 or the storage 416. The memory 404 may comprise a RAM that may include RAM devices that may store the information. The RAM devices may be volatile or non-volatile and may include, for example, one or more DRAM devices, flash memory devices, SRAM devices, zero-capacitor RAM (ZRAM) devices, twin transistor RAM (TTRAM) devices, read-only memory (ROM) devices, ferroelectric RAM (FeRAM) devices, magneto-resistive RAM (MRAM) devices, phase change memory RAM (PRAM) devices, or other types of RAM devices.
One or more computing devices 400 may include a virtual machine (VM) 405 for executing the instructions loaded in the memory 404. A virtual machine 405 may be provided to handle a process running on multiple processors so that the process may appear to be using only one computing resource rather than multiple computing resources. Virtualization may be employed in the electronic device 400 so that infrastructure and resources in the electronic device may be shared dynamically. Multiple VMs 405 may be resident on a single computing device 400.
A hardware accelerator 406 may be implemented in an ASIC, FPGA, or some other device. The hardware accelerator 406 may be used to reduce the general processing time of the electronic device 400.
The electronic device 400 may include a network interface 408 to interface to a Local Area Network (LAN), Wide Area Network (WAN) or the Internet through a variety of connections including, but not limited to, standard telephone lines, LAN or WAN links (e.g., T1, T3, 56 kb, X.25), broadband connections (e.g., integrated services digital network (ISDN), Frame Relay, asynchronous transfer mode (ATM), wireless connections (e.g., 802.11, Bluetooth®), high-speed interconnects (e.g., InfiniBand, gigabit Ethernet, Myrinet) or some combination of any or all of the above. The network interface 408 may include a built-in network adapter, network interface card, personal computer memory card international association (PCMCIA) network card, card bus network adapter, wireless network adapter, universal serial bus (USB) network adapter, modem or any other device suitable for interfacing the electronic device 400 to any type of network capable of communication and performing the operations described herein.
The electronic device 400 may include one or more input devices 410, such as a keyboard, a multi-point touch interface, a pointing device (e.g., a mouse), a gyroscope, an accelerometer, a haptic device, a tactile device, a neural device, a microphone, or a camera that may be used to receive input from, for example, a user. Note that electronic device 400 may include other suitable I/O peripherals.
The input devices 410 may allow a user to provide input that is registered on a visual display device 412. A graphical user interface (GUI) 414 may be shown on the display device 412.
A storage device 416 may also be associated with the computer 400. The storage device 416 may be accessible to the processor 402 via an I/O bus. The information may be executed, interpreted, manipulated, and/or otherwise processed by the processor 402. The storage device 416 may include, for example, a storage device, such as a magnetic disk, optical disk (e.g., CD-ROM, DVD player), random-access memory (RAM) disk, tape unit, and/or flash drive. The information may be stored on one or more non-transient tangible computer-readable media contained in the storage device. This media may include, for example, magnetic discs, optical discs, magnetic tape, and/or memory devices (e.g., flash memory devices, static RAM (SRAM) devices, dynamic RAM (DRAM) devices, or other memory devices). The information may include data and/or computer-executable instructions that may implement one or more embodiments of the invention
The storage device 416 may store files 418, applications 420, and the electronic device 1900 can be running an operating system (OS) 1926. Examples of OS 422 may include the Microsoft® Windows® operating systems, the Unix and Linux operating systems, the MacOS® for Macintosh computers, an embedded operating system, such as the Symbian OS, a real-time operating system, an open source operating system, a proprietary operating system, operating systems for mobile electronic devices, or other operating system capable of running on the electronic device and performing the operations described herein. The operating system may be running in native mode or emulated mode.
The storage device 416 may store details relating to a user account 424 associated with the electronic device 400. For example, the user account 424 may include an account ID and information pertaining to the user who owns or operates the electronic device 400.
The storage device 416 may further include one or more data structures corresponding to the above-described chat room 426. The chat room 426 may be represented, for example, as a database, table, matrix, or other data structure which identifies a location or user account, and an identifier representing locks within the location, or locks to which the user account a user who has access rights to the lock. The identifier may be, for example, an alphanumeric string or a token. Alternatively, the chat room 426 may identify a user, and furthermore identify all of the locks to which the user associated with the user account 424 has access rights.
One or more embodiments of the invention may be implemented using computer-executable instructions and/or data that may be embodied on one or more non-transitory tangible computer-readable mediums. The mediums may be, but are not limited to, a hard disk, a compact disc, a digital versatile disc, a flash memory card, a Programmable Read Only Memory (PROM), a Random Access Memory (RAM), a Read Only Memory (ROM), Magnetoresistive Random Access Memory (MRAM), a magnetic tape, or other computer-readable media.
The network 430 may transport data from a source to a destination. Embodiments of the network 430 may use network devices, such as routers, switches, firewalls, and/or servers (not shown) and connections (e.g., links) to transport data. Data may refer to any type of machine-readable information having substantially any format that may be adapted for use in one or more networks and/or with one or more devices (e.g., the computing device 400, the service provider 432, etc.). Data may include digital information or analog information. Data may further be packetized and/or non-packetized.
The network 430 may be a hardwired network using wired conductors and/or optical fibers and/or may be a wireless network using free-space optical, radio frequency (RF), and/or acoustic transmission paths. In one implementation, the network 430 may be a substantially open public network, such as the Internet. In another implementation, the network 430 may be a more restricted network, such as a corporate virtual network. The network 2012 may include Internet, intranet, Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), wireless network (e.g., using IEEE 802.11), or other type of network The network 2012 may use middleware, such as Common Object Request Broker Architecture (CORBA) or Distributed Component Object Model (DCOM). Implementations of networks and/or devices operating on networks described herein are not limited to, for example, any particular data type, protocol, and/or architecture/configuration.
The service provider 432 may include a device that makes a service available to another device. For example, the service provider 432 may include an entity (e.g., an individual, a corporation, an educational institution, a government agency, etc.) that provides one or more services to a destination using a server and/or other devices. Services may include instructions that are executed by a destination to perform an operation (e.g., an optimization operation). Alternatively, a service may include instructions that are executed on behalf of a destination to perform an operation on the destination's behalf.
The server 434 may include a device that receives information over the network 430. For example, the server 434 may be a device that receives user input from the computer 400. The cluster 436 may include a number of units of execution (UEs) 438 and may perform processing on behalf of the computer 400 and/or another device, such as the service provider 432 or server 434. For example, the cluster 436 may perform parallel processing on an operation received from the computer 400. The cluster 436 may include UEs 438 that reside on a single device or chip or that reside on a number of devices or chips.
The units of execution (UEs) 438 may include processing devices that perform operations on behalf of a device, such as a requesting device. A UE may be a microprocessor, field programmable gate array (FPGA), and/or another type of processing device. UE 438 may include code, such as code for an operating environment. For example, a UE may run a portion of an operating environment that pertains to parallel processing activities. The service provider 432 may operate the cluster 436 and may provide interactive optimization capabilities to the computer 400 on a subscription basis (e.g., via a web service).
Units of Execution (UEs) may provide remote/distributed processing capabilities for the applications 420. A hardware unit of execution may include a device (e.g., a hardware resource) that may perform and/or participate in parallel programming activities. For example, a hardware unit of execution may perform and/or participate in parallel programming activities in response to a request and/or a task it has received (e.g., received directly or via a proxy). A hardware unit of execution may perform and/or participate in substantially any type of parallel programming (e.g., task, data, stream processing, etc.) using one or more devices. For example, a hardware unit of execution may include a single processing device that includes multiple cores or a number of processors. A hardware unit of execution may also be a programmable device, such as a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a digital signal processor (DSP), or other programmable device. Devices used in a hardware unit of execution may be arranged in many different configurations (or topologies), such as a grid, ring, star, or other configuration. A hardware unit of execution may support one or more threads (or processes) when performing processing operations.
A software unit of execution may include a software resource (e.g., a technical computing environment) that may perform and/or participate in one or more parallel programming activities. A software unit of execution may perform and/or participate in one or more parallel programming activities in response to a receipt of a program and/or one or more portions of the program. A software unit of execution may perform and/or participate in different types of parallel programming using one or more hardware units of execution. A software unit of execution may support one or more threads and/or processes when performing processing operations.
The term ‘parallel programming’ may be understood to include multiple types of parallel programming, e.g. task parallel programming, data parallel programming, and stream parallel programming. Parallel programming may include various types of processing that may be distributed across multiple resources (e.g., software units of execution, hardware units of execution, processors, microprocessors, clusters, labs) and may be performed at the same time.
For example, parallel programming may include task parallel programming where a number of tasks may be processed at the same time on a number of software units of execution. In task parallel programming, a task may be processed independently of other tasks executing, for example, at the same time.
Parallel programming may include data parallel programming, where data (e.g., a data set) may be parsed into a number of portions that may be executed in parallel using, for example, software units of execution. In data parallel programming, the software units of execution and/or the data portions may communicate with each other as processing progresses.
Parallel programming may include stream parallel programming (sometimes referred to as pipeline parallel programming). Stream parallel programming may use a number of software units of execution arranged, for example, in series (e.g., a line) where a first software unit of execution may produce a first result that may be fed to a second software unit of execution that may produce a second result given the first result. Stream parallel programming may also include a state where task allocation may be expressed in a directed acyclic graph (DAG) or a cyclic graph.
Other parallel programming techniques may involve some combination of task, data, and/or stream parallel programming techniques alone or with other types of processing techniques to form hybrid-parallel programming techniques.
The foregoing description may provide illustration and description of various embodiments of the invention, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations may be possible in light of the above teachings or may be acquired from practice of the invention. For example, while a series of acts has been described above, the order of the acts may be modified in other implementations consistent with the principles of the invention. Further, non-dependent acts may be performed in parallel.
In addition, one or more implementations consistent with principles of the invention may be implemented using one or more devices and/or configurations other than those illustrated in the Figures and described in the Specification without departing from the spirit of the invention. One or more devices and/or components may be added and/or removed from the implementations of the figures depending on specific deployments and/or applications. Also, one or more disclosed implementations may not be limited to a specific combination of hardware.
Furthermore, certain portions of the invention may be implemented as logic that may perform one or more functions. This logic may include hardware, such as hardwired logic, an application-specific integrated circuit, a field programmable gate array, a microprocessor, software, or a combination of hardware and software.
No element, act, or instruction used in the description of the invention should be construed critical or essential to the invention unless explicitly described as such. As used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “a single” or similar language is used. Further, the phrase “based on,” as used herein is intended to mean “based, at least in part, on” unless explicitly stated otherwise. In addition, the term “user”, as used herein, is intended to be broadly interpreted to include, for example, an electronic device (e.g., a workstation) or a user of an electronic device, unless otherwise stated.
Similarly, a channel or groove 504 is formed within the door jamb of the door frame 10. A frame element 550 is mounted or seated within the channel 504 and is secured therein according to known techniques. For example, the frame element can be secured therein by fasteners, by an adhesive, or by known pressure fit techniques.
The door panel 18 can also have one or more holes or apertures 505, 507 formed therein for mounting for example a door handle or latch assembly 600 and a deadbolt assembly 570. The door panel apertures can be formed therein by a user or other skilled professional or can be pre-drilled by the manufacturer. As shown in
As illustrated in
Those of ordinary skill in the art will readily recognize that the frame element 510 can have any suitable shape or configuration, provided that the shape is suitable for its intended purpose. The illustrated frame element 510 can be made of any suitable material, and is preferably made of aluminum.
With reference to
The opposed end or an intermediate portion of the main body 524 of the locking element 522 has a groove 586 formed therein that is adapted to mount a resilient member 528. The resilient member 528 provides a sound dampening function during operation of the door lock assembly. Specifically, the resilient member 528 is adapted to contact one leg portion 515 of the frame element when the locking assembly is disposed in the locked or protruding position, as shown in
The main body 524 of the illustrated locking element 522 has opposed ends, the first end of which, as set forth above, includes the connecting portion 526 and the opposed second end wraps around to form in essence a hollow passage 590. The actuator of the deadbolt assembly described below is positioned in part within this passage during operation. The main body of the locking element also includes a notch or cut-out portion 588. The notch allows the locking element, when assembled to the frame element 510 mounted in the door panel, to seat about the actuator of the deadbolt assembly.
The illustrated locking element 522 can have any selected size and shape, provided that the locking element is capable of contacting the frame element 550 of the door frame in order to lock or secure the door panel 18 to the frame 10. The locking element 522 can be any suitable rail-type locking element that is capable of moving when actuated between the locked and unlocked positions. According to this embodiment, the locking element has a generally wedge-shaped configuration. The locking element can be made from any suitable material, and is preferably composed of aluminum. The resilient member can also have any selected size, shape or configuration, and can be composed of any suitable material, such as rubber.
The movable locking assembly 520 also includes an intermediate coupler element 530 and a drive element 540, as shown for example in
The illustrated drive element 540 also has a main body 541 that includes a central rectangular portion that has an elongated channel 542 formed therein. The drive element 540 has a first coupler receiving end 543 having a general cut-out portion 544 and a tab hole 545 that is sized and dimensioned for mounting over and engaging a respective end portion 534 of the intermediate coupler element 530. When coupled thereto, the end portion 543 of the drive element 540 seats over the boss 538 such that the tab 539 is positioned within the tab hole 545. This helps secure the drive element to the intermediate coupler element 530. The drive element 540 also includes a second opposed end 546 that extends outwardly from the main body and which has a partially formed channel or groove 547 formed thereon. The boss 537 formed on the end portion 533 of the intermediate coupler element 530 is coupled to one of the locking elements 522, and the second end of the drive element 546 when coupled to the end portion 534 of the intermediate coupler element 530 is coupled to the other locking element 522.
The drive element 540 helps constrain and trap an actuator mechanism, as described below, such that when the actuator moves the movable locking assembly into the locked position, it contacts and exerts a force on a portion of the drive element, such as the second end 546. The drive element in turn exerts a force on the locking elements 522 since they are coupled together. This in turn moves the locking elements into the locked position. Further, when the actuator mechanism moves the movable locking assembly 520 into the unlocked position, the actuator pulls back away from the drive mechanism and hence contacts (as shown in
The various elements of the movable locking assembly 520 as illustrated in the Figures and as described herein can be formed of any suitable material, and is preferably formed of aluminum.
As illustrated in
The door lock assembly 500 of the present invention also contemplates the use of an actuator mechanism for moving the locking assembly between the locked and unlocked positions. The actuator mechanism can optionally form part of the door lock assembly, although this element can also be separately provided, such as being formed for example as part of a deadbolt assembly. According to the current embodiment, the actuator mechanism can be a deadbolt assembly 570. As illustrated in
The illustrated deadbolt assembly 570 preferably includes within a chamber formed by the assembly housing a suitable actuation assembly that is capable of moving the actuator mechanism (e.g., piston 578). The present Figures simply illustrate for the sake of convenience and simplicity a general actuation assembly, which can include the actuation assembly of a conventional deadbolt which converts manual force applied by the user, such as via a latch or a key, into translational or linear movement of the piston (e.g., bolt or actuator). Alternatively, the actuation assembly can include any suitable arrangement of mechanical and electrical components that are capable of moving the piston. For example, the actuation assembly can include a motor that is powered by a battery or by electrical power supplied at the installation site to move the actuator. Examples of potential functionality and arrangement of components were described in some respects in connection with the first embodiment. Those of ordinary skill will readily recognize that for the purposes of the present invention it does not matter the type of actuation mechanism that is used provided that the mechanism is capable of moving the actuator (piston) linearly so as to properly interact with the locking elements 522, 522. As such, the actuator mechanism hence must be able to effect movement of the locking elements between the locked and unlocked positions.
As illustrated with reference to
Further, as illustrated in
The present invention also contemplates the use of a door latch assembly 600. The door latch assembly can, if desired, form part of the door lock assembly 500 of the present invention. The door latch assembly 600 is illustrated in
The illustrated door latch assembly 600 includes, in addition to the first and second main body portions, a latch piston element 610, a latch hub element 630, a piston actuator element 650, a biasing element 670, and a spring latch element 680. The latch piston element 610,
The latch piston element 610 is adapted to move in a linear direction as illustrated in
As illustrated in
A biasing element 670 is mounted about the boss 642 and is coupled thereto. The boss element this functions as a biasing element seat during use. The latch hub element 630 and associated biasing element are then mounted within the main body of the door latch assembly 600 such that the end of the biasing element opposite to the end coupled to the boss 642 contacts the inner surface 628A. The biasing element can be any suitable element sufficient for applying a biasing force to the latch piston element 610. According to a preferred embodiment, the biasing element is a spring.
As illustrated in
As illustrated in
The door latch assembly 600 and associated components can have any selected shape or configuration, in addition to those illustrated and described herein. The various elements other than the biasing element can be formed from any suitable material, such as plastic.
The door latch assembly 600 of the present invention operates as follows. With reference to
If a user wishes to open the door, the user rotates the door handle (not shown), which applies a rotational force to the piston actuator element 650,
The operation of the door latch assembly 600 is separate and independent from operation of the movable locking assembly. Thus, the door latch assembly 600 can move the latch element between the engaged and retracted positions independent of the position of the locking assembly. Further, selected features of the first and second embodiments of the door lock assembly illustrated herein can be shared as would be apparent to one of ordinary skill in the art.
It will thus be seen that the invention efficiently attains the objects set forth above, among those made apparent from the preceding description. Since certain changes may be made in the above constructions without departing from the scope of the invention, it is intended that all matter contained in the above description or shown in the accompanying drawings be interpreted as illustrative and not in a limiting sense.
It is also to be understood that the following claims are to cover all generic and specific features of the invention described herein, and all statements of the scope of the invention which, as a matter of language, might be said to fall therebetween.
Marsh, Robby A., Lylyk, Nicolas Pedro, Martin, John Hillerich, Jadallah, Samir
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 1723305, | |||
| 2920472, | |||
| 3019493, | |||
| 6185871, | Feb 09 1999 | Door structure | |
| 6431621, | Apr 06 1999 | Securing device | |
| 7624539, | Dec 30 2005 | WEDGETLS LLC | Combined sealing systems for pivoting door/window |
| 7627987, | Dec 30 2005 | WEDGETLS LLC | Combined sealing system and seal activation system for door |
| 7640704, | Dec 31 2007 | WEDGETLS LLC | Strengthened door with stiffeners |
| 7665245, | Dec 30 2005 | WEDGETLS LLC | Sealing system positioned within frame for door/window |
| 7685774, | Dec 30 2005 | WEDGETLS LLC | Closing system for sealing system of sliding door/window |
| 7685775, | Dec 30 2005 | WEDGETLS LLC | Combined sealing systems for sliding door/window |
| 7685776, | Dec 30 2005 | WEDGETLS LLC | Sealing system for sliding door/window |
| 7707773, | Dec 30 2005 | WEDGETLS LLC | Seal activation system positioned within panel for door/window |
| 7832167, | Dec 31 2007 | Otto LLC | Door and window system with stiffeners |
| 8074399, | Jun 20 2006 | Otto LLC | Sealing system modules for door/window |
| 8074400, | Jun 20 2006 | Otto LLC | Combined modular sealing systems and seal activation system for door/window |
| 8091282, | Dec 30 2005 | Otto LLC | Combined sealing system and seal activation system for door/window |
| 8109037, | Dec 30 2005 | Otto LLC | Active sealing system for single-hung door/window |
| 8336258, | Dec 30 2005 | WEDGETLS LLC | Self-driving combination sealing system for single-hung door/window |
| 8468746, | Sep 30 2008 | WEDGETLS LLC | Sealing systems for garage door |
| 8484899, | Sep 30 2008 | WEDGETLS LLC | Driving and driven sealing systems for single-hung door/window |
| 8516756, | Apr 27 2009 | WEDGETLS LLC | Door panel with thermal break |
| 8539717, | Dec 30 2005 | WEDGETLS LLC | Electronic control for door/window |
| 8627606, | Dec 30 2005 | WEDGETLS LLC | Combined sealing system for garage door |
| 8656643, | Dec 30 2005 | WEDGETLS LLC | Seal activation system positioned within panel for door/window |
| 8701346, | Jun 20 2006 | WEDGETLS LLC | Combined modular sealing systems and seal activation system for door/window |
| 8925249, | Jun 20 2006 | WEDGETLS LLC | Active sealing and securing systems for door/window |
| 20070290456, | |||
| 20080060276, | |||
| 20090178344, | |||
| 20120124774, | |||
| 20120293055, | |||
| 20130000205, | |||
| 20150052835, | |||
| DE29517077, | |||
| EP1234939, | |||
| FR2596795, | |||
| WO2013124857, | |||
| WO2014134563, | |||
| WO2017019256, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Apr 16 2014 | JADALLAH, SAMIR | Tyto Life LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042768 | /0892 | |
| Apr 16 2014 | MARTIN, JOHN HILLERICH | Tyto Life LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042768 | /0892 | |
| Apr 16 2014 | MARSH, ROBBY A | Tyto Life LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042768 | /0892 | |
| Apr 16 2014 | LYLYK, NICOLAS PEDRO | Tyto Life LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042768 | /0892 | |
| Dec 29 2016 | Otto LLC | (assignment on the face of the patent) | / | |||
| Aug 18 2017 | Tyto Life LLC | Otto LLC | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 043987 | /0196 | |
| Sep 11 2020 | OTTO ABC , LLC | WEDGETLS LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 061196 | /0379 |
| Date | Maintenance Fee Events |
| May 06 2022 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
| Date | Maintenance Schedule |
| Nov 06 2021 | 4 years fee payment window open |
| May 06 2022 | 6 months grace period start (w surcharge) |
| Nov 06 2022 | patent expiry (for year 4) |
| Nov 06 2024 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Nov 06 2025 | 8 years fee payment window open |
| May 06 2026 | 6 months grace period start (w surcharge) |
| Nov 06 2026 | patent expiry (for year 8) |
| Nov 06 2028 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Nov 06 2029 | 12 years fee payment window open |
| May 06 2030 | 6 months grace period start (w surcharge) |
| Nov 06 2030 | patent expiry (for year 12) |
| Nov 06 2032 | 2 years to revive unintentionally abandoned end. (for year 12) |