This application relates generally to portable locks, and more specifically to a system for wireless management of a portable locking device.
Bicycle theft is a big problem. In the USA 1.5 million bikes are stolen every year representing a loss of about $350 million. Bike theft is also a crime that largely goes unpunished.
Embodiments of the invention comprise a wirelessly controlled electronic portable lock apparatus that might be used to secure objects such as bicycles or the like. The lock apparatus is locked and unlocked via a mechanism actuated by an electromechanical device such as an electric motor, solenoid, servo motor, stepping motor or the like. The actuator is controlled by an electronic element such as a microcontroller, which itself acts based on information received remotely via a wireless link. The wireless link can be established via an antenna, although not necessary, and the antenna can be connected to an electronic radio or similar device. The nature of the wireless link can take many forms such as far field or near field thus covering the range spanned from NFC devices to devices such as radios. All electric, electromechanical, and electronic elements are powered through a battery, which can be rechargeable, placed inside the body of the lock.
Various objects, features, and advantages of the disclosed subject matter can be more fully appreciated with reference to the following detailed description of the disclosed subject matter when considered in connection with the following drawings, in which like reference numerals identify like elements.
The overall system may include several high-level elements that work together to enable the functionality described herein. Referring to
The data network (100) will be understood to include network elements such as are often referred to as “cloud computing”. The data network (100) includes back-end storage, processing, and computing equipment that is located remotely. It is composed of data network services, such as cell phone towers, cell phone base stations, antennas, computing equipment etc. It also includes the computing equipment of cloud computing services such as Amazon, Rackspace, Microsoft etc. This element may also include web hosting services, back-end services, storage and backup Services, databases, software and computing processes, etc. The purpose of the data network is to provide the infrastructure necessary to carry out many of the functions described in this patent and others that are not yet disclosed.
A data network link (101) refers to the physical and logical connection that is established between device A and the data network. This link can be made either through wireless or connected means. Some examples are Ethernet networks, Wi-Fi links, GPRS/EDGE/3G/4G, and other cell phone services. The purpose of the link is to connect device A to the data network to enable services and operations to function properly. It is possible to operate device A in the absence of the data link, but the data link may be useful to enable many of the features of embodiments of the invention.
Device A (102) is an electronic device that works as an interface to control the wireless lock. Device A may be represented by many different devices. Some examples include cellular phones, smart phones, media devices such as MP3 media players, pagers, portable computers, personal computers, tablet computers, personal digital assistants, wearable computers such as smart glasses, bracelets, necklaces and others. Device A includes all the elements necessary to make device A function and include but are not limited to their power supplies such as batteries, firmware, application software, display, interface elements as sensors and buttons, cases, drives, etc. A purpose of device A is to control the wireless lock and to provide feedback to the user and the control software about the state of different variables and subsystems of the wireless lock. Device A accomplishes this through one or many types of device A software (105).
Device A software (105) can take many forms depending on the embodiment of device A and can be represented by application software or “apps”, web browsers, specialized software or firmware, etc. Device A software (105) has several main functions:
To effect changes on device B
To monitor the state of device B
To provide an interface for users
To authenticate and validate authorized users
To interface functions of the lock between device B and the data network
To notify users of changes in states of the lock
To store information regarding device B
To communicate with the data network
Users can be either other software elements or people. Device A software will communicate to device B (104), which is the wireless lock, through a wireless link (104).
The wireless link (103) is the interface between device A and device B. This link can take many forms depending on the technology used but can be any version of Bluetooth including Bluetooth low energy, or other technologies such as Wi-Fi, near field communications (NFC), ZigBee, ANT, etc.
Device B (104) refers to the wireless lock. The wireless lock comprises several subsystems as shown in
Controlling the mechanisms of the lock
Controlling the radios
Storing information
Interfacing between component elements
Controlling user interface features such as LEDs
Monitoring the state of the battery
Reporting characteristics back to Device A
Providing a secure digital connection through encryption
The electrical subsystem of the lock can be described as all the electrical and electronic elements used to operate the device, and includes, but is not limited to: one or many electromechanical components, such as electric motors, solenoids, relays, or the like; one or multiple radios, one or many antenna matching circuits, one or many antennas, a controlling unit that interfaces the radio to the electric motors (directly or indirectly) such as a microcontroller, microprocessor or other device; the necessary passive and active electric and electronic elements such as resistors, inductors, capacitors, transistors, diodes etc, that might be necessary to interface the previously mentioned elements to each other.
An example of a high-level electrical diagram can be seen in
The MCU (201) refers to a microcontroller, microprocessor or similar device that executes the code necessary to run some or all of the tasks of the subsystem. The MCU can be either a stand-alone device or be integrated into a radio unit/module as shown by dotted line (213). If the radio and MCU units are separate, they can communicate through a radio bus (217). Radios could be one or many of equal or different technologies and can be stand-alone or combined into a single piece of silicon or module as indicated by the
The power supply block from
Embodiments of the invention include the software elements used to operate the lock. The software in device B, the wireless lock, embodies any firmware, applications, code, pseudo-code, and similar used to make the radio and or controlling unit function. The software component in device A comprises applications, browsers, web applications, code, parts of code, firmware, user interfaces, human computer interaction elements, buttons, controls and similar needed to take input from persons, other software, devices, websites, real or virtual entities, databases, cloud systems and servers, and the like. That input may be turned into actionable wireless signals, status reports, tests, and others used to remotely control, monitor and interact with the elements in device B such as the locking mechanism. The software in the remote server/data network component includes application software that runs in a remote location, such as a cloud computing environment or remote servers. This may include databases, security code, data processing applications, storage/backup processes, and systems or similar.
An example flow chart for software associated with device B can be seen in
In the case where a connection is successfully established (414), as illustrated in
In other potential scenarios, the wireless connection between device A and the wireless lock could be established automatically, making it transparent to the user. In such cases, the lock authentication and handshake process could be established as soon as the user and the lock are within the range of the wireless radio. The user could then potentially open the lock simply by pressing a button in the lock, or by actuating a sensor. This could be a capacitive touch sensor, a photodiode, ambient light sensor, accelerometer or others. The user could also open the lock based on the proximity of the radio as measured by different techniques.
The software associated with device A can take many forms depending on the type of device being used to communicate with the wireless lock. In many cases it will be a mobile application running on a portable device such as a smart phone or media player with wireless capabilities. Device A software could also be a web browser application or a native application running on a phone, personal computer or portable device. An example of a software flowchart for an application that could be used can be seen in
As soon as the application is started (601), a screen would shows a login screen to authenticate the user (602). If the user already has an account (603), the screen provides a way to input username and password (604). If the user does not have an account, the screen can provide an option to allow the user to create one. If this option is selected, the application shows another screen that takes user information (613), then stores it in a back end server/database (614). In the case that the user already has an account and inputs login credentials the system then proceeds to authenticate the identity of the user with data previously stored in the back end servers/databases. If the user authentication is successful (605), the application then displays a screen to search for nearby wireless locks (606). If the login attempt is not successful, the login screen indicates the failed attempt and prompt the user to try again (616).
The device search screen allows the user to search for nearby devices and list them once they are found (608). If no devices are found (607), the screen allows the user to keep searching until something is found. Once one or more devices are found, they are listed in the same or different screen. The user would then select the desired wireless lock to connect to (609). Once a device is selected from the list, the application could search for the Link Layer ID or similar hardware key from the selected device in the back end servers (610). If the hardware key is found on the online database (611) and the key is associated with the logged in user, then a wireless connection would be established between Device A and the wireless lock (613). In this case a welcome screen and/or a main action menu could be presented to the user (614). In the case that the hardware ID from the lock is not found on the database (612 to 618), and the lock is in an initial configuration state (619) either because it is new or because it has been reset, then the application would establish a wireless connection (620), and present to the user an initial lock configuration screen (621) where settings such as a name for the lock, wireless connectivity settings, sensitivity of sensors, LED brightness, and others could be set (622). Once the configuration settings are chosen, these would be stored in both the lock and the back end servers/databases (623,624). Finally, if the user selects a lock for which a hardware ID cannot be found under the associated profile, the connection would be refused and a connection refused screen could be shown (626) indicating the failure, and then proceed to the search device screen (627 to 617).
Once a connection with the lock is established (615 or 625 to 700), the application may display a task menu through user interface elements such as icons, buttons and similar controls as illustrated in
The lock comprises a u-shaped housing also known as a shackle (1004) and a locking bar (1002). The shackle (1004) may be closed using a top-loaded locking bar as shown in
An example embodiment of a solenoid actuated linkage mechanism can be seen in
Similarly, a dual-solenoid mechanism could be used as depicted on
An example embodiment of a servo actuated rotating-pawl mechanism can be seen in
An example embodiment of a servo actuated pawl-retracting mechanism can be seen in
The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure. The language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon.
This application is a continuation of U.S. application Ser. No. 16/387,462, filed on Apr. 17, 2019, which is a continuation of U.S. application Ser. No. 14/271,963, filed on May 7, 2014, now U.S. Pat. No. 10,378,241, which claims benefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 61/832,316, entitled “Wireless Ultra-Low Power Portable Lock,” filed on Jun. 7, 2013, the disclosures of which are expressly incorporated by reference herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5387903 | Cutter et al. | Feb 1995 | A |
5517189 | Bachhuber | May 1996 | A |
6012309 | Liu | Jan 2000 | A |
6046558 | Larson et al. | Apr 2000 | A |
6584815 | Bremicker | Jul 2003 | B2 |
6761051 | Tsai | Jul 2004 | B1 |
8482411 | Brown | Jul 2013 | B1 |
8839650 | Zuraski | Sep 2014 | B2 |
9260885 | Asquith et al. | Feb 2016 | B2 |
10246905 | Al-Kahwati et al. | Apr 2019 | B2 |
10378241 | Al-Kahwati et al. | Aug 2019 | B2 |
10526814 | Al-Kahwati et al. | Jan 2020 | B2 |
20030218536 | Linden et al. | Nov 2003 | A1 |
20040134242 | Wyers | Jul 2004 | A1 |
20050199019 | Marcelle et al. | Sep 2005 | A1 |
20060179057 | Moretti | Aug 2006 | A1 |
20070240464 | Miller et al. | Oct 2007 | A1 |
20080024272 | Fiske | Jan 2008 | A1 |
20080078213 | Adcock | Apr 2008 | A1 |
20080094192 | Dutt | Apr 2008 | A1 |
20080223088 | Yang | Sep 2008 | A1 |
20090183541 | Sadighi | Jul 2009 | A1 |
20090282876 | Zuraski et al. | Nov 2009 | A1 |
20100033327 | Kao | Feb 2010 | A1 |
20100332359 | Powers et al. | Dec 2010 | A1 |
20110265526 | Zuraski | Nov 2011 | A1 |
20110285528 | Weinstein et al. | Nov 2011 | A1 |
20120133482 | Bhandari et al. | May 2012 | A1 |
20120169461 | Dubois, Jr. | Jul 2012 | A1 |
20120249327 | Kofford et al. | Oct 2012 | A1 |
20130043973 | Greisen | Feb 2013 | A1 |
20130055773 | Li | Mar 2013 | A1 |
20130069760 | Lickfelt | Mar 2013 | A1 |
20130335193 | Hanson | Dec 2013 | A1 |
20140085087 | Alnadwi | Mar 2014 | A1 |
20140157838 | Nave | Jun 2014 | A1 |
20140218167 | Tseng | Aug 2014 | A1 |
20140266588 | Majzoobi | Sep 2014 | A1 |
20140360232 | Al-Kahwati et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
202004001522 | Apr 2004 | DE |
202008010350 | Dec 2008 | DE |
102009043873 | Mar 2011 | DE |
0668422 | Aug 1995 | EP |
WO-9505515 | Feb 1995 | WO |
WO-9828509 | Jul 1998 | WO |
WO-2009158326 | Dec 2009 | WO |
WO-2013078561 | Jun 2013 | WO |
Entry |
---|
International Search Report and Written Opinion issued by the U.S. Patent and Trademark Office as International Searching Authority for International Application No. PCT/US2014/037101 dated Nov. 13, 2014 (11 pages). |
European Extended Search Report issued in EP14806848.9, dated Mar. 14, 2017 (12 pages). |
Extended European Search Report dated Dec. 22, 2017 received in related European Patent Application No. 17187521.4 filed May 7, 2014 (8 pages). |
Notice of Opposition dated Oct. 8, 2020 received in related European Patent Application No. 14806848.9 (64 pages). |
Number | Date | Country | |
---|---|---|---|
20200190858 A1 | Jun 2020 | US |
Number | Date | Country | |
---|---|---|---|
61832316 | Jun 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16387462 | Apr 2019 | US |
Child | 16710737 | US | |
Parent | 14271963 | May 2014 | US |
Child | 16387462 | US |