US20160116510A1 - Predictive battery warnings for an electronic locking device - Google Patents
Predictive battery warnings for an electronic locking device Download PDFInfo
- Publication number
- US20160116510A1 US20160116510A1 US14/524,558 US201414524558A US2016116510A1 US 20160116510 A1 US20160116510 A1 US 20160116510A1 US 201414524558 A US201414524558 A US 201414524558A US 2016116510 A1 US2016116510 A1 US 2016116510A1
- Authority
- US
- United States
- Prior art keywords
- user
- lock
- product
- server
- electronic locking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R19/00—Arrangements for measuring currents or voltages or for indicating presence or sign thereof
- G01R19/165—Indicating that current or voltage is either above or below a predetermined value or within or outside a predetermined range of values
- G01R19/16533—Indicating that current or voltage is either above or below a predetermined value or within or outside a predetermined range of values characterised by the application
- G01R19/16538—Indicating that current or voltage is either above or below a predetermined value or within or outside a predetermined range of values characterised by the application in AC or DC supplies
- G01R19/16542—Indicating that current or voltage is either above or below a predetermined value or within or outside a predetermined range of values characterised by the application in AC or DC supplies for batteries
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/36—Arrangements for testing, measuring or monitoring the electrical condition of accumulators or electric batteries, e.g. capacity or state of charge [SoC]
- G01R31/392—Determining battery ageing or deterioration, e.g. state of health
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Lock And Its Accessories (AREA)
- Telephone Function (AREA)
- Engineering & Computer Science (AREA)
- Power Engineering (AREA)
Abstract
Disclosed herein are methods, systems, and computer-readable media for operating an electronic locking device. The disclosed methods include a method of predicting a battery life of an electronic locking product based at least in part on a usage history of the electronic locking product. The predicted battery life may include an adjustment based on received weather information relating to a location of the electronic locking device. The disclosed methods include a method of sharing an unlocking code to an electronic locking product by a first user to a second user.
Description
- Recently, electronic locks have become commercially available. Such electronic locks may be capable of being controlled by a user device over a wireless connection (e.g., Wi-Fi, etc.). However, the communications that are used to interface with such electronic locks are often not overly secure, which increases the risk that an unauthorized user may gain control of the lock.
- Disclosed herein are methods, systems, and computer-readable media for operating an electronic locking device. One embodiment relates to a method of predicting a battery life of an electronic locking product based at least in part on a usage history of the electronic locking product. The method includes receiving, at a server, lock event information associated with a lock event of the electronic locking product from a user device. The method further includes storing, in a database of the server, the lock event information, wherein the lock event information is associated with the electronic locking product in the database. The method includes calculating, by the server, an expected battery life of a battery of the electronic locking product based at least in part on the lock event information. The method further includes determining, by the server, that the expected battery life of the battery is below a threshold value. The method includes initiating, by the server, an alert to a user computing device indicating a low battery condition of the battery in response to determining that the expected battery life is below the threshold value.
- Another embodiment relates to a method of sharing an unlocking code to an electronic locking product by a first user to a second user, the electronic locking product including an electronically controllable mechanical locking mechanism. The method includes receiving, by a server, a sharing request from a first user computing device associated with the first user, wherein the sharing request indicates a request from the first user to provide guest access to a second user. The method further includes authenticating, by the server, the first user as at least one of an owner or an authorized user of the electronic locking product. The method includes generating, by the server, an unlock code for the electronic locking product. The method further includes transmitting, by the server, a message to a second user computing device associated with the second user, the message including the unlock code.
- Yet another embodiment relates to a locking product system. The system includes an electronic locking device and a backend server. The electronic locking device includes a battery, a wireless transceiver, an electronically controllable locking mechanism, and a first processor configured to lock and unlock the electronically controllable locking mechanism and to transmit information to a backend server via a user computing device. The backend server includes a memory and a second processor. The second processor is configured to receive lock event information associated with a lock event of the electronic locking product from a user device. The second processor is further configured to store the lock event information, wherein the lock event information is associated with the electronic locking product in the database. The second processor is configured to calculate an expected battery life of a battery of the electronic locking product based at least in part on the lock event information. The second processor is further configured to determine that the expected battery life of the battery is below a threshold value. The second processor is configured to initiate an alert to a user computing device associated with a user of the electronic locking product indicating a low battery condition of the battery.
- The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the following drawings and the detailed description.
- The foregoing and other features of the present disclosure will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. Understanding that these drawings depict only several implementations in accordance with the disclosure and are, therefore, not to be considered limiting of its scope, the disclosure will be described with additional specificity and detail through use of the accompanying drawings.
-
FIG. 1 is a block diagram of a system for wireless key management for authentication, according to an embodiment. -
FIG. 1B is a diagram of an example electronic locking device, according to an embodiment. -
FIG. 2 is a flow diagram of a process for configuring a product and user device, according to an embodiment. -
FIG. 3 is a flow diagram of a process for interacting with a product with a user device, according to an embodiment. -
FIG. 4 is a block diagram of a device for implementing the techniques disclosed herein, according to one embodiment. -
FIG. 5 is a block diagram of a user device for implementing the techniques disclosed herein, according to one embodiment. -
FIG. 6 is a block diagram of a server for implementing the techniques disclosed herein, according to one embodiment. -
FIG. 7 is a block diagram of a product for implementing the techniques disclosed herein, according to one embodiment. -
FIG. 8 is a flow diagram of a process for determining location data for a product and, optionally, generating a mapping interface indicating the determined location(s), according to one embodiment. -
FIG. 9 is a flow diagram of a process for facilitating the sharing of a product unlock code and a product location between a first user and a second user, according to one embodiment. -
FIG. 10 is a flow diagram of a process of estimating battery life based at least in part on an actual usage audit trail and initiating low battery alerts to users, according to one embodiment. -
FIG. 11 is a flow diagram of a process of estimating battery life based at least in part on an the location of the product and initiating low battery alerts to users, according to one embodiment. - The details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
- Like reference numbers and designations in the various drawings indicate like elements. Before turning to the detailed description, which describes the exemplary embodiments in detail, it should be understood that the application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.
- In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, and designed in a wide variety of different configurations, all of which are explicitly contemplated and made part of this disclosure.
- Described herein are techniques for wireless key management for authentication. According to the disclosure herein, additional security is provided to wireless communications between a user device (e.g., a mobile phone, a laptop, a tablet device, etc.) and a product (e.g., an electronic locking device, such as a padlock, door lock, lock box, etc.) via an authentication scheme that utilizes a server and an encryption scheme that uses at least two keys. In scenarios where a user device is configured to control or manage the operation of the product, the use of the disclosed authentication and encryption systems is desirable to ensure that the product is being validly controlled. Throughout this disclosure, embodiments are discussed with reference to a user device of a mobile phone and a product of an electronic locking device. However, the present disclosure is not limited to implementations that use a mobile phone and an electronic locking device, and embodiments that utilize other types of user devices and products are within the scope of this disclosure.
- According to some exemplary embodiments, the disclosed approach is based on encryption using two keys. One key (e.g., a secret key) is known/stored on the product (an electronic locking device) and the server (a management system). The other key (e.g., an access key) is known/stored on the lock and the user device (a mobile phone). Both the secret and access keys are specific to the lock/product. In this manner, the secret and access keys may uniquely relate to a single lock/product. The secret key may be used to encrypt a file (e.g., a user profile) that can be used to determine a user's access rights to the lock/product. For example, such access rights may define when a user can remotely access the lock/product or when the user can otherwise control the device (e.g., lock or unlock an electronic locking device). The access key can be used by the user device in initiating communications with the lock/product, and also may be used as part of a challenge-response exchange between the user device and lock/product.
- The keys discussed herein may also be used to authenticate that data is valid, and also came from the other holder of the corresponding key. Such data integrity and source authentication/authenticity verification may be performed by computing a MAC (message authentication code) of the data transmitted (e.g., using the secret key or access key). Accordingly, as discussed further herein, when a server encrypts a user profile, a device that receives the encrypted profile (e.g., a locking device) may use its copy of the secret key to verify that the MAC is correct. Similarly, when a lock is transmitting data, it may use its secret key to compute a MAC to be verified by a server (if the data is intended for the server), and the server may use its secret key to verify the MAC. Alternatively, any of the communications discussed herein may be unencrypted (e.g., plaintext packets, etc.), and a MAC may be computed for transmitted data and included with the transmitted data. The MAC may then be used as a security measure to verify that data is being transmitted from a legitimate source. Additionally, when a lock and mobile device are communicating, each may use their copies of the access key to compute a MAC, and each device may verify the data and authenticate its source using the access key. Accordingly, such use of a MAC can ensure that data is coming from the proper source (i.e., the server, mobile device, or the lock), and also that the data is valid.
- Referring to
FIG. 1 , a block diagram of asystem 100 for wireless key management for authentication is shown, according to an embodiment.System 100 includes at least one user device 102,server 104, andproduct 106. In an illustrative embodiment, user device 102 is a mobile device (e.g., a mobile phone) andproduct 106 is an electronic locking device. In general, user device 102 is configured to at least partially manage the operation ofproduct 106. For example, a mobile phone may be used to unlock, lock, and otherwise manage the function of an electronic locking device. User device 102 includes components necessary for such product management (e.g., aprocessor 102 a,memory 102 b,timer 102 c,transceivers Processor 102 a may be any commercially available processor, may represent one or more processors, and may be implemented as a general-purpose processor or an application specific integrated circuit.Memory 102 b may include the memory ofprocessor 102 a (e.g., cache), RAM, or other storage (flash memory, hard disk storage, etc.).Timer 102 c is configured to maintain a time value for user device 102. For example, timer 102 may be the clock ofprocessor 102 a, or may be any other time keeping circuit of device 102. The time value maintained bytimer 102 c may be used in secured communications as discussed further herein (e.g., in syncing time withproduct 106, in providing timestamps related to events for logging purposes, etc.).Transceivers transceiver 102 d includes cellular components for communicating withserver 104 via a cellular network. In one embodiment,transceiver 102 d includes wired or wireless (e.g., Wi-Fi) components for communicating withserver 104 over the Internet or other network.Wireless transceiver 102 e is configured to communicate withproduct 106. In one embodiment,wireless transceiver 102 e includes Bluetooth components for establishing a Bluetooth connection withproduct 106. User device 102 can manageproduct 106 through the use of a management application that is configured to run on the user device (e.g., viaprocessor 102 a andmemory 102 b). For example, an app may be installed on a mobile phone (i.e., in thememory 102 b of user device 102), and the app may be used to configure and control an electronic locking device (i.e., product 106) over a wireless connection (viawireless transceiver 102 e). One or more user input devices 102 f (e.g., touch screens, buttons, speakers, displays, keyboards, etc.) may be included in user device 102 to allow a user to interact with device 102,server 104,product 106, and any applications running on the device. - In an embodiment where
product 106 is a locking device, such an electronic locking device typically includes aprocessor 106 a for providing logic of the electronic locking device and a high current load (e.g., amotorized locking mechanism 106 g that may be controlled by the processor). The high current load may include one ormore lock mechanisms 106 g (e.g., shackles, pins, memories, etc.) as discussed below. The electronic locking device may also include abattery 106 d for powering the high current load and a capacitor in parallel with the processor. The electronic locking device may include one or more physical and/ordigital interfaces 106 e to allow a user to manage the device (e.g., keypad, touch screen, touch sensitive area, dial, combination lock interface, button, keyhole, etc.) A circuit (e.g.,processor 106 a) of the electronic padlock may be configured to cause the processor to be powered by the capacitor (and in some embodiments not the battery) while thebattery 106 d is driving the highcurrent load 106 g. In one embodiment, the circuit also includes atimer 106 c that is configured to maintain a time value the product, which may be used in secured communications as discussed herein. In one embodiment, the electronic locking device includes alocation determination circuit 106 h, such as a GPS receiver, that may be used to provide a location of the electronic locking device. In various implementations,location determination circuit 106 h may be part of or separate fromwireless transceiver 106 f. In one embodiment, the electronic locking device is an electronic padlock, such as an electronic combination or keypad padlock. In other embodiments, the electronic locking device may be or include, without limitation, devices such as an electronic door lock or keypad device (e.g., a keypad deadbolt), an electronic safe (e.g., a small document safe, an electronic key safe, etc.), an electronic rim or mortise lock or other type of cabinet lock, an electronic auto accessory lock (e.g., a coupler lock, a hitch pin lock, a trailer lock, etc.) and/or a steering wheel or door lock for an automobile, a vehicle lock (e.g., a wheel lock or ignition lock) for other motorized or non-motorized vehicles such as a bicycle, a motorcycle, a scooter, an ATV, and/or a snowmobile, a storage chest, a case with an electronic lock (e.g., a document case or a case for small valuables), an electronic cable lock (e.g., a cable lock enabled with an alarm, such as for securing a computing device), a safety lockout/tagout device for securing access for safety purposes (e.g., for securing an electrical control box while electrical work is being performed), a locker with an electronic lock, and/or an electronic luggage lock. In one embodiment, the locking device is configured to provide access to secured data (e.g., stored in a memory, etc.) or to store secured data. For example, rather than containing physical locking components (or in addition to physical locking components),lock mechanisms 106 g may include a secured memory (e.g.,memory 106 b may include an encrypted hard drive, etc.). Such a locking device may communicate (e.g., viawireless transceiver 106 f) based on the authentication techniques discussed herein. For example, upon authentication, the locking device may use its stored secret key to decrypt secured content that is stored inmemory 106 b. Decrypted content may then be provided to another device (e.g., viawireless transceiver 106 f). In one embodiment, the electronic locking device includes touch detection devices and/or proximity detection devices configured to detect the presence of a user (e.g., based on a user's touch, based on motion of a user, etc.). - Referring to
FIG. 1B , an example of anelectronic locking device 100 b is showing, according to one embodiment.Electronic locking device 100 b typically includes one or more lock mechanisms (e.g., lockmechanisms 106 f). For example, electronic locking device may include shackle 160 aninterface 162. In one embodiment,interface 162 includes a touch sensor configured to awake theelectronic locking device 100 b in response to a user's touch, as is discussed further herein. In one embodiment,interface 162 includes a proximity sensor configured to awake theelectronic locking device 100 b in response to detecting a nearby user, as is discussed further herein. In one embodiment,interface 162 includes a mechanical dial configured to allow a user to enter a code to the lock (e.g., to unlockshackle 160, etc.). Various processing andmechanical components 164 may be embedded within thecase 166 ofelectronic locking device 100 b. For example, the processing andmechanical components 164 may include one or more of the components (e.g.,processor 106 a,memory 106 b,timer 106 c,battery 106 d,wireless transceiver 106 f, lockmechanisms 106 g, etc.) discussed with references toproduct 106 ofFIG. 1 . - Referring again to
FIG. 1 , in an illustrative embodiment,product 106 includes awireless transceiver 106 f for communications according to one or more wireless technologies (e.g., radio frequency, radio frequency identification (RFID), Wi-Fi, Bluetooth, ZigBee, near field communication (NFC), etc.). For example,wireless transceiver 106 g may be a Bluetooth transceiver configured to establish a Bluetooth-based connection with user device 102 (e.g., via wireless transceiver 102 f). Accordingly, the electronic locking devices discussed herein may be equipped to be locked or unlocked using another user interface device (e.g., user input devices 102 f of user device 102,network interface 104 e ofserver 104, etc.), via a wireless transceiver, other than a combination input or keypad input on the lock. For example, wireless communications may be used to lock/unlock/control the electronic locking device wirelessly (e.g., an application on a mobile phone may be used to lock or unlock the device). In one embodiment, the circuit ofproduct 106 also includes an input/output port (e.g., a USB port, a COM port, a networking port, etc.) that may be used to establish a physical connection to another device. For example, such a physical connection may be used by a manufacturer to program or otherwise communicate withproduct 106. -
Server 104 generally includes components (e.g., aprocessor 104 a,memory 104 b,network interface 104 e, etc.) to communicate with user device 102 and provide authentication keys and encryption functions. Communications betweenserver 104 and user device 102 may be direct or via an intermediate network (e.g., an internet network, a cellular network, etc.). For example,networking interface 104 e may include physical network components (e.g., a network card, etc.) configured to allowserver 104 to establish a connection totransceiver 102 d of device 102. In one embodiment, communications fromnetwork interface 104 e are routed through a cellular interface, allowingserver 104 to communicate with device 102 via a cellular network. In one embodiment,network interface 104 e allowsserver 104 to establish an Internet-based connection with device 102.Server 104 may be one server (a physical or virtual server), or may include multiple servers.Server 104 may include one or more services configured to generate and store keys (e.g., secret key, access key, etc.) used for authentication and encryption. In one embodiment, various modules ofmemory 104 b provide different functions ofserver 104. For example, adevice interface module 104 c may be used to establish and manage communications with user device 102. Asecurity module 104 d may be used for security related functionality (e.g., generating and storing keys, encrypting a user profile, etc.). The output ofsecurity module 104 d may be provided todevice interface module 104 c, such that device interface module may then communicate the security related data to device 102. In one embodiment, an access key and an encrypted user profile may be provided bysecurity module 104 d at the request ofdevice interface module 104 c. Upon receiving the access key and encrypted user profile,device interface module 104 c may transmit (e.g., via a cellular network throughnetwork interface 104 e) the access key and encrypted user profile to user device 102. In this manner, user device 102 does not directly accesssecurity module 104 d. In one embodiment,device interface module 104 c andsecurity module 104 d are located on twoseparate servers 104. - The following discussion describes embodiments having an electronic locking device (i.e., product 106) and a mobile device (i.e., user device 102). When the lock is manufactured, or soon thereafter, two keys (secret key and access key) can be generated and affiliated with the lock. For example, the secret key and access key may each be related to a unique serial ID or other identification number for the lock, and may be stored in a memory of the lock. In one embodiment, one or both keys are unique and/or randomly generated keys. In one embodiment, a unique code that represents the product is generated (e.g., by server 104) and this unique code can be used to link the lock to its corresponding keys. For example, such a unique code may be secured in product packaging of the lock so that a user may appropriately configure the lock and mobile device. In one embodiment, a separate unique code is provided for each of the security and access keys, and each unique code may be associated with their respective security or access key by the manufacturer. In one embodiment,
server 104 also generates the secret and access keys. For example,server 104 may provide a key generation service that may be accessed during the manufacturing process. The keys may be generated according to any generation algorithm; however, the secret key and access key are typically not derived from one another. After generation, the secret is key is only stored onserver 104 and the lock. The secret key is not transmitted to the mobile device. However, the access key may be provided to both the lock and the mobile device. - When a user acquires a lock, the user may configure both the lock and the user's mobile device using the unique code that is used to link the lock to its keys. Referring to
FIG. 2 , a flow diagram of anillustrative process 200 for configuring a product and user device is shown, according to an embodiment. In alternative embodiments, fewer, additional, and/or different steps may be performed. Also, the use of a flow diagram is not meant to be limiting with respect to the order of steps performed. - The unique code is retrieved (202). For example, the user may refer to included product packaging to retrieve the unique code, or the user may otherwise contact a manufacturer to receive the unique code (e.g., via a manufacturer website, phone, etc.). The unique code is then provided to the management server (204) in order to associate the lock with the user. For example, a user may enter the unique code on a user interface of an application running on the mobile device, which then transmits the unique code to the server. In one such example, the user may enter the unique code within a frontend interface provided by the management server and accessed via a browser application on the mobile device. Alternatively, the user may use the mobile device to scan packaging of lock to retrieve and transmit the unique code. For example, the unique code may be encoded by a barcode, QR code, optical code, etc., and a camera of the mobile device may be used to scan and determine the unique code. In response to receiving the unique code from the mobile device, the server can retrieve or newly generate (e.g., on demand) the secret key and access key, which may then be associated with the unique code.
- The server may then generate a user profile (206), which may also be associated with the unique code. If a user profile does not yet exist, default values, or values provided by the user via the mobile device may be used to generate the new profile. For example, the user may enter profile data into an application of the mobile device, which transmits the profile data to the server along with the unique code. If the user has already created a profile, the server may instead update the user profile with new values provided by the user via the mobile device.
- In general, a user profile may include one or more files that include data related to operation of the product, which is the lock in the above embodiment. For example, a user profile may contain a user schedule of when the lock may be accessed (unlocked, locked, etc.). The schedule may specify lock access permissions, e.g., by day of the week, including starting times (hours, minutes, etc.) and ending times (hours, minutes, etc.) for each corresponding permission. For example, a schedule may specify the time spans in which an electronic lock may be unlocked via the mobile device. As another example, the schedule may specify time periods in which typical interactions are expected to occur, and a level of trust may be determined based on these time periods. Accordingly, an unlock request sent within an expected time period may be more trusted by the lock than a request sent at an unexpected/atypical time. The mobile device may also automatically adjust a schedule. For example, the mobile device may log/record a user's interactions with the lock, and may set a schedule based around the user's anticipated actions. In one embodiment, a default user schedule is set (e.g., by the manufacturer, etc.). Additionally, a list of typical user schedules may also be provided to allow a user to select from one of many configuration options. In this manner, a manufacturer may provide various recommended operational settings to a user. A user may also customize a schedule to tailor the schedule as he or she desires.
- A user profile may further specify a model/serial number of the lock and what types of accesses are available for that user. For example, such accesses may include: reading software/hardware version information of the lock, updating software of the lock, reading a shackle state of the lock, locking, unlocking, disarming, reading/setting a time/clock value, reading a battery level, reading/clearing event related data (e.g., flags, counters, etc.), reading a log of the lock, reading/setting/resetting a keypad code of the lock, reading communications data for the lock (e.g., transmission statuses, transmission power levels, channel information, addressing information, etc.), reading/setting default values stored for the lock (e.g., default disarm times, default unlock times, etc.), among others. A user profile may also specify a start time and a revocation date/time for the profile (i.e., when the profile begins to be valid and when the profile expires and is no longer valid). A user profile may provide maximum disarm/unlock times for the lock. A user profile may also provide an indication of a trust level of a corresponding mobile device (e.g., whether a time value/timestamp provided by the mobile device is trusted or not). The lock may be configured to allow or disallow certain functionality based on the trust level of a device. The trust level may be stored as an independent permission that the user may or may not have access to (e.g., the trust level may be managed/adjusted by the software of the lock, mobile device, or server, etc.). As an example, only a highly trusted device may be able to upgrade the firmware of the lock or change certain settings. Additionally, the lock may have a security algorithm that factors in a trust level and time value. For example, as a device successfully interacts with the lock more often, the lock may increase (or adjust) a trust level for the device. However, if a time value is out of sync with the lock's maintained time or authentication fails, the lock may decrease (or adjust) a trust level for the device. The time value provided by the mobile device may be compared to a time value maintained by the lock, and a degree of closeness between the two times may be used to indicate a trust level for the device (e.g., the closer the two times are to being in sync, the higher the trust level, etc.). If a trust level decreases below a certain threshold, the lock may discontinue or limit interactions with the mobile device. A trust level may also be based on the schedule discussed above. For example, a mobile device may be regarded as more or less trusted based on the time the device is accessing the lock, and whether that time falls within certain time periods as defined by the schedule. The time value provided by the mobile device may also be used to sync the clock of the lock with that of the mobile device, or may be used otherwise during authenticated communications. Any of the profile items discussed may have default values (e.g., manufacturer defaults) or user provided values. A profile is not limited to the above data, and additional data may be included. A profile may also be stored on a server for later retrieval.
- In addition to generating a profile for the user (e.g., the owner of the lock), the user may desire to create additional guest profiles (208) to be shared with friends, family, co-workers, etc. In this manner, a user may grant another person access to the lock, based on the guest profiles. To do so, a user may enter in desired profile values (using the mobile device) for the additional person(s). Similar to the creation of the user's profile, the guest profile data may be transmitted to the server to be processed as discussed further below. The guest profile data may be transmitted to the server simultaneously or separately (e.g., at a later time) from when the user initially generates his or her profile. The mobile device includes information that differentiates the types of profiles (e.g., owner vs. guest) being provided to the server.
- After at least one profile is generated, the user is associated with the particular lock as an owner of the lock. In some embodiments, the association may be based solely on the unique code that was provided to the server (e.g., in step 204). In one embodiment, after providing a unique code, the mobile device may use the unique code to automatically retrieve additional information related to the lock (e.g., a serial ID, a model number, etc.) from a database or a server of the lock's manufacturer. In alternative embodiments, a serial ID, a model number, or other code may also be provided by a user (e.g., by referring to product packaging, etc.), and such additional data may be utilized, along with the unique code, in associating a user with a lock. In some embodiments, additional authentication of a user may also be required prior to associating a user with a lock as an owner, and such authentication may be provided via the mobile device.
- The management server then may verify received profile data. To verify the received profile data, the management server may perform a cyclic redundancy check (CRC) on the profile to ensure the data's integrity. Other data verification methods may also be utilized. For example, in an illustrative embodiment, a message authentication code (MAC) (e.g., a keyed-hash message authentication code (HMAC)) may be generated using the secret key and used for verification of data integrity. The scope of the present disclosed is not limited to a certain data integrity validation mechanism. The sever can then encrypt the profile data using the secret key in order to transform the profile data into an encrypted profile (e.g., ciphertext). The profile may be encrypted according to any known encryption standards. In an illustrative embodiment, the profile is encrypted using CCM mode (NIST/FIPS counter mode encryption with cipher block chaining MAC) based algorithms, and the secret key, which is used as the cipher key, has a length of 128 bits. Accordingly, the server may encrypt the user profile and also generate a MAC using the secret key. Alternatively, other standards could also be used, such as performing encryption and generating a MAC with different keys.
- In one embodiment, the management server discussed herein is one of a group of management servers. In such an embodiment, a first management server may be configured to handle communications with mobile devices, and a second management server may be configured to handle security functionality (e.g., storage of keys, generation of keys, encryption/decryption processes, etc.). In this manner, the first server may receive communications from a mobile device and may communicate with the second server when security functions are required. For example, the first server may request a service provided by the second server to encrypt profile data that was initially received by the first server. The second sever may then encrypt and provide the encrypted data to the first server, which may then transmit the encrypted data to the mobile device. Other server configurations are also envisioned.
- After encryption, the encrypted profile is transmitted from a server to the mobile device (210). The server also transmits the corresponding access key to the mobile device (210). In an illustrative embodiment, the access key has a length of 128 bits. The access key can be determined by the server using the unique code (e.g., as discussed in steps 202-204). The received encrypted profile and access key are then stored in a memory of the mobile device in order to complete the association of the mobile device with the lock. The user may then use his or her mobile device to interact with the lock (212).
- In the scenario that a guest profile was generated, in some embodiments, the server may perform similar security procedures as performed for the user profile. For example, the guest profile may be stored and encrypted using the secret key. In some embodiments, in the case of a guest profile, the server may first transmit a notification to the guest prior to encrypting and transmitting the encrypted guest profile. For example, the server may send a notification email or text/SMS message/alert to the guest based on information that the user provided (e.g., an email address, phone number, etc.) when the user set up the guest profile. Upon reception of a notification, a guest may then activate his or her profile that was created by the user. For example, the notification may include an activation link to be clicked (e.g., within the email or message) or code that the guest is required to provide. The guest may also install the management application discussed herein and use the application to activate the guest profile using an activation code. Upon activation and installation of the management application, the server can then generate and transmit the encrypted guest profile and access key to a mobile device of the guest via the management application. After receiving the encrypted guest profile and access key, each may be stored in the guest's mobile device to associate the guest's device with the lock. The guest may then use his or her mobile device to interact with the lock (212).
- After a profile is configured, the user (or guest) may interact with the lock wirelessly via the mobile device. For example, a user may lock, unlock, or adjust settings of the lock, etc. In one embodiment, the lock may wake up/detect the presence of a nearby user and begin an interaction process. For example, the lock may include proximity detection features, or the user may actively touch the lock (e.g., a touch sensitive location on the lock, a physical button, etc.), or the user's mobile device may transmit a signal on a common channel in order to wake up the lock, etc. When the lock has been woken up, it can attempt to connect with the mobile device of the user. For example, the lock may broadcast its model and serial number information (or other unique lock ID information) and wait for a response from the mobile device. The mobile device can receive the lock information and compare it to the profiles maintained by the management application. For example, the management application can maintain profiles for multiple different locks at a time. If a match is found (e.g., if a profile is found for that particular type of lock), an authentication procedure may commence to verify the matched profile. If the profile is verified, and the user has access at that particular time (i.e., based on scheduling data of the profile), and the user's time/device is trusted, the user may unlock the lock and perform other interactions with the lock. After authentication, the lock's time and mobile device's time may also be synced, if necessary.
- Referring to
FIG. 3 , a flow diagram 300 of an illustrative process for interacting with a product with a user device is shown, according to an embodiment. In alternative embodiments, fewer, additional, and/or different steps may be performed. Also, the use of a flow diagram is not meant to be limiting with respect to the order of steps performed. - In some embodiments, the lock may be woken up out of a low power standby or sleep state (302). For example, the lock may be touched by a user, or the proximity of the user may be automatically detected. The standby/sleep state may utilize less power (e.g., battery power) than if the lock is in a fully operational, awake state. In some embodiments, the lock may always be in a fully functional state, and may not be woken up out of a standby/sleep state.
- The lock may advertise its type information (304), for example, by broadcasting a unique ID (e.g., an identifier that is formed from its model and/or serial number). The communications between the lock and device may be over any type of wireless communications protocol. In one embodiment, the mobile device and lock communicate via a Bluetooth connection. In another embodiment, the mobile device and lock communicate via a Wi-Fi connection. In another embodiment, the mobile device and lock communicate via a ZigBee connection. In another embodiment, the mobile device and lock communicate via an NFC connection. Additionally, any of the data communicated (e.g., the packets transmitted) between the mobile device and the lock may be further secured according to any known security protocol (e.g., WEP, WPA, user/manufacturer passwords, etc.). In one embodiment, data transmitted between the mobile device and lock is encrypted using the access key. In this embodiment, both the mobile device and lock are able to encrypt and decrypt data, as each has a stored copy of the access key. Upon decrypting a received data, both the mobile device and lock may further ensure the integrity of the decrypted data, for example, by using a MAC validation scheme, running a CRC check, etc., on the decrypted data. Such a MAC validation scheme also allows the mobile device and lock to verify that the data originated from its proper source (i.e., the other holder of the key used to generate the MAC, etc.).
- The user device receives and confirms the lock's information (e.g., the lock's ID) (306). In one embodiment, the lock's ID is compared to a list of profiles stored on the mobile device to determine whether the mobile device is associated with the lock (e.g., whether a profile exists that corresponds to the lock's ID). If a matching profile is not found, a user may be prompted to create a profile (e.g., via process 200) using the unique code that links the lock to the secret key. If a profile is found for the lock, the user device may then transmit a request to the lock (e.g., an unlock request, etc.), and an authentication procedure can commence prior to complying with the request.
- The lock generates a challenge and transmits the challenge to the user device (308). In one embodiment, the lock generates a long random number as the challenge. In another embodiment, the lock generates data that varies by communication session (e.g., a unique number (a session identifier) may be generated as the challenge for each communication session). In one embodiment, the challenge is transmitted as plaintext to the mobile device; however, in another embodiment the challenge may be encrypted using the access key. The mobile device calculates the response (e.g., a long response) for the challenge using a security algorithm and the access key (which was received from the server during configuration as discussed above) (310). In one embodiment, the mobile device uses the access key to generate the response and a MAC that is transmitted with the response. In some embodiments, the communications between the mobile device and lock are secured further based on sequential identification (e.g., sequential identification of packets or messages). For example, with sequential identification, the mobile device may transmit a field that should follow a particular sequence for each received packet. The lock may then verify the received packets against a known sequence. Such a known sequence may be predetermined or generated by the lock, and also may be provided to the mobile device by the lock during communications. Accordingly, this sequencing may be used along with one or more of the other methods described above (e.g., a session identifier may be used along with a predetermined initial sequence field value), or sequencing may be used by itself (e.g., the lock may provide the initial value of the sequence field upon connection). In one embodiment, upon connection, the mobile device receives an initial sequence number from the lock, and the lock verifies that subsequently received messages contain the initial number incremented once for each message received. The lock may further verify that the received messages are encrypted using the access key and/or include a MAC computed therefrom.
- The mobile device can then transmit to the lock the response and the corresponding encrypted profile (which was encrypted by the server using the secret key as discussed above) (312). In one embodiment, the mobile device also transmits a current timestamp based on the mobile device's clock. As the lock stores both the secret key and access key, it may use these keys to authenticate the data received from the mobile device. In one embodiment, the lock uses the access key to verify that the response to the challenge is correct and to verify the MAC (314). In one embodiment, the lock requires the response to be verified prior to then accepting and attempting to decrypt the profile. Upon successful completion of the challenge-response process, the lock can validate the received data (314). The lock can use the secret key to decrypt the encrypted profile, and the lock may also validate the data (e.g., using the MAC generated from the secret key or other validation scheme, e.g., performing a CRC check) of the decrypted profile data to ensure that the decryption was successful and that the data in fact came from the correct source (e.g., that the encrypted profile was generated by the server, etc.). The lock may also ensure that the profile has access at that verified time (e.g., by referring to the scheduling information included in the decrypted profile). In an embodiment where the mobile device transmitted a timestamp, the lock may verify the timestamp by comparing the timestamp with a current time of the lock. If the response and decrypted profile are each verified, then the lock may comply with the request of the mobile device and initiate a corresponding action (316). In an embodiment utilizing the timestamp discussed above, a received timestamp may also be required to be within a threshold amount of time from a time maintained by the lock. In this example, the lock can unlock its shackle as requested.
- In another embodiment where the lock is configured as a digital locking device (e.g., to store secured data in its memory), the lock may use its copy of the secret key to decrypt content that is stored in the lock. Accordingly, if a request is received from a mobile device to retrieve or store certain data such a locking device, a transfer of such data may be initiated in response to the request. For example, if a mobile device requests to store data, and the corresponding encrypted profile that was provided during authentication allows such an action, and authentication as discussed above was successful, the mobile device may proceed to transmit data (and the locking device may receive such data) to the locking device. The locking device may then store the received data in its memory. If the received data is not yet encrypted, the locking device may use its secret key to encrypt the data to be stored. As another example, if a mobile device requests to retrieve data, and the corresponding encrypted profile that was provided during authentication allows such an action, and authentication as discussed above was successful, the lock may decrypt and transmit requested data to the mobile device. Alternatively, the lock may transmit encrypted data, and the mobile device may then communicate with the server (which also stores a copy of the secret key) for decryption purposes. Any typical data interactions (e.g., deleting data, renaming files, copying data, organizing data, etc.) may also be supported by the digital locking device, which may be based on the types of accesses specified in the corresponding user profile.
- Additional security related features may also be implemented by the server discussed herein. For example, in the instance an access key or secret key is compromised, an operator of the server or the user (via the mobile application) may initiate a protective measure. For example, the user may request a new key pair to be generated. In one embodiment, the server can generate a new key pair consisting of a newly generated secret key and the old access key, and encrypt the new key pair using the old secret key (similar to the encryption of a profile as discussed above). The server may then communicate with the mobile device to queue a key pair change request. If a user has multiple devices, or guest profiles, the user may select one or more particular devices on which the key pair change request is queued. Upon the next access attempt by the mobile device with the lock, a challenge-response sequence as discussed above may be initiated; however, the requested action can be a “key change request.” As part of the challenge response transmission, the mobile device may include the encrypted new key pair. For example, the mobile device may transmit the response, and then the encrypted new key pair. Upon validation of the response, the lock may decrypt the encrypted new key pair using the old secret key and verify the data. If successful, the lock may access the new secret key from the decrypted new key pair, and then store the new secret key to be used in future interactions. In addition to updating the secret key, other functionality may be provided through similar challenge-response exchanges and encryption using the secret key. In one embodiment, instead of transmitting a “key change request,” the mobile device may transmit a “firmware update request” along with new firmware version that is encrypted with the secret key. Upon successful authentication, the lock may proceed to decrypted the new firmware, and then update its firmware to the new version.
- Any of the devices discussed herein (e.g., user device, product, server) may also be configured to generate an audit trail related to its operations. For example, a log may be formed to detail the events that occur throughout the interaction of a user device and a product. This may include server-to-user device events (e.g., sending an encrypted profile, sending a new key pair request, etc.), user device-to-product events (e.g., sending/responding to an unlock request, logging when authentication succeeds and fails, etc.), device-only events (e.g., logging application errors, logging shackle status of an electronic locking device, etc.), among others. The scope of the present disclosure not limited to a particular log formatting.
- In one embodiment, the lock is additionally equipped with a location determination circuit, such as a GPS device/receiver, and may transmit its location information (e.g., GPS coordinates) to the mobile device during interactions with the mobile device. The location information may then be stored by the mobile device (e.g., within the profile created for the lock, etc.) as a last known location of the lock. The mobile device's management application can also be equipped with mapping functionality so that the last known location of the lock may be displayed on a map, based on the provided location information. Alternatively, the management application may allow the location information to be exported to a third party mapping application. These location features can allow a user to open the management application on his or her mobile device, and then view a map that indicates where the lock was located when the last known location (e.g., GPS coordinates) was provided. Additionally, navigational directions or other features may be provided to guide a user to the lock. In an alternative embodiment, the mobile device may also include a GPS device. In this manner the mobile device may also record its location information during interactions with the lock and server.
- In any of the embodiments discussed herein, the devices may form a portion of a processing subsystem including one or more computing devices having memory, processing, and communication hardware. The devices (e.g., servers, user devices, products) may be a single device or a distributed device, and the functions of the devices may be performed by hardware and/or as computer instructions on a non-transient computer readable storage medium, and functions may be distributed across various hardware or computer based components. Referring to
FIG. 4 , adevice 400 is shown, which may represent any of the devices discussed herein.Device 400 may also be used to implement the techniques and methods discussed herein. For example,device 400 may comprise the processing components of user device 102 (e.g., the processing components of a mobile phone). As another example,device 400 may comprise the processing components ofserver 104. As another example,device 400 may comprise the processing components of product 106 (e.g., the processing components of an electronic locking device). In addition,device 400 may be configured to perform the computations discussed herein (e.g., the computations related toprocesses -
Device 400 typically includes at least oneprocessor 402 coupled to amemory 404.Processor 402 may be any commercially available CPU.Processor 402 may represent one or more processors and may be implemented as a general-purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a digital-signal-processor (DSP), a group of processing components, or other suitable electronic processing components.Memory 404 may include random access memory (RAM) devices comprising a main storage of thedevice 400, as well as any supplemental levels of memory, e.g., cache memories, non-volatile or back-up memories (e.g., programmable or flash memories), read-only memories, etc. In addition,memory 404 may include memory storage physically located elsewhere, e.g., any cache memory in theprocessor 402 as well as any storage capacity used as a virtual memory, e.g., as stored on a mass storage device, etc.Device 400 also includestransceiver 406, which includes any additional networking components or transmitters necessary to communicate with other devices (e.g., Wi-Fi networking components, Bluetooth components, ZigBee components, NFC components, etc.). For example, in an embodiment wheredevice 400 comprises an electronic lock,transceiver 406 may be a Bluetooth transceiver configured to communicate with a user's mobile device. As another example, in an embodiment wheredevice 400 comprises a server,transceiver 406 may be a networking interface configured to couple the server to a network to communicate with a mobile device. As another example, in an embodiment wheredevice 400 comprises a mobile device,transceiver 406 may include a Wi-Fi or cellular transceiver configured to communicate with a server, andtransceiver 406 may further include Bluetooth components configured to communicate with a product (e.g., an electronic locking device). - In general, the routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, module, or sequence of instructions. In certain embodiments,
device 400 includes one or more modules structured to functionally execute the respective operations necessary for wireless key management for authentication as described herein. The description herein including modules emphasizes the structural independence of the aspects of a device and illustrates one grouping of operations and responsibilities of a device. More specific descriptions of certain embodiments of a device's operations are described by the sections herein referencingFIGS. 1-3 . Other groupings that execute similar overall operations are understood within the scope of the present application. The modules typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements of disclosed embodiments. Moreover, various embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that this applies equally regardless of the particular type of computer-readable media used to actually effect the distribution. - Referring to
FIG. 5 a block diagram of a user device 500 for implementing the techniques disclosed herein is shown, according to one embodiment. For example, user device 500 may correspond to the mobile devices discussed herein. In one embodiment, user device 500 is a mobile phone. In another embodiment, user device 500 is a laptop computer. In another embodiment, user device 500 is a tablet computer. In another embodiment, user device 500 is a desktop computer. In general, user device 500 includes aprocessing circuit 502, which may include aprocessor 502 a, amemory 502 b, and atimer 502 c.Processor 502 a may be any commercially available processor or any of the processors discussed herein (e.g., processor(s) 402, etc.).Memory 502 b includes any of the memory and/or storage components discussed herein. For example,memory 502 b may include RAM and/or cache ofprocessor 502 a.Memory 502 b may also include one or more storage devices (e.g., hard drives, flash drives, computer readable media, etc.) either local or remote to user device 500. -
Memory 502 b includes various software modules configured to implement the techniques disclosed herein with respect to user devices. For example,memory 502 b includes an accesskey module 504, which is configured to store and provide the access key as requested by the other modules ofmemory 502 b.Application module 506 is configured to provide the management application as discussed herein. For example, in an embodiment where user device 500 is a mobile phone,application module 506 includes the software corresponding to a mobile phone app, which may be used to interface with a server and/or product.Application module 506 may include aprofile module 508, which is configured to manage the profile generation process, including interactions with the server and product. For example, a user may interact with user device 500 (e.g., via user input devices 502 f) through the application provided byapplication module 506. The user may create one or more profiles corresponding to one or more products, which are transmitted (e.g., viatransceiver 502 d) to a server. The server may encrypt a user profile, and profile the encrypted user profile, access key, MAC, etc., to the user device 500 as discussed herein. Application module may also interact with a product (e.g., an electronic locking device) viawireless transceiver 502 e as discussed herein. Aresponse module 510 may include the security algorithms required for generation a response to a challenge sent by a product. Additionally, theresponse module 510 may include encryption/decryption and MAC authentication algorithms, which may be accessed byapplication module 506 during secured communications.Memory 502 b may further include atimer 502 c, which may include the clock components ofprocessor 502 a, for maintaining a device time to be used as described herein. - In some implementations,
memory 502 b may include amapping module 512 that may be used to generate one or more mapping interfaces based on location data received from a product (e.g., locking device). One such implementation is described below with respect toFIG. 8 . - User device 500 further includes
transceiver 502 d andwireless transceiver 502 e (which may correspond totransceiver 102 d andwireless transceiver 102 e of user device 102, etc.), which include various communication circuitry. For example, in one embodiment,transceiver 502 d may include cellular components and/or Wi-Fi components andwireless transceiver 502 e may include Bluetooth components, etc. User input devices 502 f may include one or more user input devices for interaction with user device 500. For example, user input devices 502 f may include one or more buttons, touch screens, displays, speakers, keyboards, stylus inputs, mice, track pads, etc.). - Referring to
FIG. 6 a block diagram ofservers 600 for implementing the techniques disclosed herein is shown, according to one embodiment.Servers 600 include one or more physical or virtual servers/server slices, etc. For example,servers 600 may correspond to server(s) 104. In general,servers 600 are configured to interact with a user device (e.g., user device 500, etc.). Aserver 600 may include aprocessing circuit 602.Processing circuit 602 includes aprocessor 602 a andmemory 602 b. As an example,processor 602 a may include any commercial available processor, e.g., a server processing chip, a virtual processor, etc.Memory 602 b includes any of the memory and/or storage components discussed herein. For example,memory 602 b may include RAM and/or cache ofprocessor 602 a.Memory 602 b may also include any mass storage devices (e.g., hard drives, flash drives, computer readable media, etc.). -
Memory 602 b may include an accesskey module 604 and securitykey module 606. The accesskey module 604 and securitykey module 606 may be configured to securely store access keys and security keys, respectively. The access and security keys may correspond to products as discussed herein. As an example, accesskey modules 604 and securitykey module 606 may correspond to databases of keys, and may include the software configured to store and retrieve such keys.Profile module 608 includes the software configured to interact with a product (e.g., to manage the process of user and guest profile generation, storage, and communication with a user device).Profile module 608 may also interact withsecurity module 610, which may include the security algorithms as discussed herein. For example,security module 610 may be configured to generate an access key, a security key, encrypt/decrypt data, generate a MAC based on data, etc., and provide such data to profilemodule 608. In one embodiment, the security functions ofsecurity module 610 and accesskey module 604 andsecurity module 606 are located onseparate servers 600 fromprofile module 608. In this embodiment, various services may be provided by appropriate servers such thatprofile module 608 may access security functions and retrieve keys as necessary to implement the techniques discussed herein. In some embodiments,servers 600 are also configured to interact with a product (e.g., product 106). For example, during a manufacturing process,servers 106 may provide an access key and security key to be stored in a corresponding product. - In some implementations,
memory 602 b may include amapping module 612 that may be used to generate one or more mapping interfaces based on location data received from a product (e.g., locking device). One such implementation is described below with respect toFIG. 8 . - Referring to
FIG. 7 a block diagram of aproduct 700 for implementing the techniques disclosed herein is shown, according to one embodiment. For example,product 700 may be a lock as discussed herein. In general,product 700 includes aprocessing circuit 702, which may include aprocessor 702 a, amemory 702 b, and atimer 702 c (which may include the clock components ofprocessor 702 a, for maintaining a product time to be used as described herein).Processor 702 a may be any commercially available processor or any of the processors discussed herein (e.g., processor(s) 402, etc.).Memory 702 b includes any of the memory and/or storage components discussed herein. For example,memory 702 b may include RAM and/or cache ofprocessor 702 a.Memory 702 b may also include one or more storage devices (e.g., hard drives, flash drives, computer readable media, etc.). -
Memory 702 b includes various software modules configured to implement the techniques disclosed herein with respect to products (e.g., electronic locking devices, etc.). Forexample memory 702 b may include an accesskey module 704, a securitykey module 706, asecurity module 708, and acontrol module 710. The accesskey module 704 and securitykey module 706 are configured to store the product's corresponding access key and security key, respectively. Other modules ofmemory 702 b may interact with accesskey module 704 and securitykey module 706. Forexample security module 708, which includes the security algorithms for the product (e.g., encryption/decryption algorithms, MAC generation/verification algorithms, etc.), may retrieve an access key from accesskey module 704 when generating a challenge to be sent to a user device. As another example,security module 708 may access securitykey module 708 to retrieve a security key to decrypt an encrypted user profile received from a user device.Control module 710 contains the software configured to interact with the other modules ofmemory 702 b to implement the techniques disclosed herein with respect to a product. For example, in an embodiment whereproduct 700 is a lock, after being awoken,control module 710 may attempt to pair/communicate with a user device (viawireless transceiver 702 d).Control module 710 may also include operating system (e.g., an embedded operating system, firmware, etc.) software forproduct 700. As another example,control module 710 may requestsecurity module 708 to access a user profile and request to determine an action to be taken. Based on the permissions of the user profile and the request,control module 710 may determine whether or not to take a request action. For example,control module 710 may generate the signals necessary to control mechanical (and electronic) components of product 700 (e.g., lockmechanisms 702 f) in response to a request (e.g., an unlock request for a lock, etc.). As another example,control module 710 may interface withlock mechanisms 702 f to control a user's physical interactions with a lock (e.g.,control module 710 may receive input from a dial interface, a key code interface, buttons, touch interface, etc.) in order to unlock a shackle of the lock. - In some embodiments,
product 700 may include alocation determination circuit 702 g, such as a Global Positioning System (GPS) device/receiver, that may determine one or more locations ofproduct 700 at one or more times. In some such embodiments,memory 702 b may include aposition tracking module 712 configured to receive the location data fromlocation determination circuit 702 g and store data indicative of the location or position ofproduct 700 at one or more times. One such embodiment is discussed below with respect toFIG. 8 . -
Wireless transceiver 702 d includes communications hardware (e.g., Bluetooth components, radiofrequency components, NFC components, ZigBee components, RFID components, Wi-Fi components, etc.) for wirelessly communication with another device (e.g., user devices 500,servers 600, etc.). In some embodiment,product 700 includes abattery 702 e for providing power to the product. In an embodiment whereproduct 700 is a lock, lock mechanism(s) 702 f includes one or more physical and/or electronic locking mechanisms (e.g., pins, shackles, dials, buttons, shafts, keyholes, etc.) as discussed herein. For example, lock mechanism(s) 702 f may correspond to lockmechanisms 106 g. - In some embodiments, a product (e.g., locking device) may include a location determination circuit (e.g., GPS receiver), and may generate and store location information for the lock. Referring now to
FIG. 8 , a flow diagram of aprocess 800 for collecting location data for a product and displaying the location data on a mapping interface of a mobile device is shown according to an exemplary embodiment. Whileprocess 800 illustrates providing a mapping interface, it should be appreciated that, in some embodiments, the product may generate/receive location data for the locking device, store the data, and/or transmit the data to the mobile device and/or one or more servers without the mobile device/server(s) generating mapping interfaces. - The product may generate and/or receive one or more location data items indicating a location of the product at one or more times (802). In some embodiments, the location data items may be generated by a location determination circuit, such as a GPS receiver, and may be transmitted to one or more processors of the product. The location data items may be stored in a memory (804).
- The product may receive a request to transmit data to a mobile device. In some embodiments, the request may specifically request location data from the product. In other embodiments, the request may be a connection request, and the product may transmit location data in response to successfully connecting with the mobile device. In some embodiments, the product may validate data from the mobile device before providing the mobile device with the location data (806). In some such embodiments, validation of the data may be performed using a process similar to that described above with reference, for example, to
FIGS. 2 and 3 (e.g., transmitting a challenge, verifying the response to the challenge, validating the data using a secret key, etc.). The product may transmit the location data items to the mobile device (808). In some embodiments, the product may only transmit the location data items to the mobile device if the data is validated. - The mobile device may obtain the location data item(s) from the product (810). In some embodiments, the mobile device may also obtain location and/or time parameters from a user for use in generating a mapping interface (812). For instance, location parameters may specify one or more location areas (e.g., buildings, geographic areas, etc.) to which locations displayed in the mapping interface should be restricted. In one such implementation, the location parameters may be based on current settings (e.g., geographic focus and/or zoom level) of a mapping interface. Time parameters may restrict a time associated with the results. For instance, in some embodiments, the user may indicate a desire to see only the last known location of the product. In some embodiments, the user may wish to see only locations during the past week. The mobile device may filter the location data item(s) based on the location and/or time parameters (e.g., before generating the mapping interface) (814). For example, items that do not fulfill the parameters may be removed from the set of data to be displayed within the mapping interface.
- The mobile device may generate a mapping interface illustrating one or more locations indicated by the one or more location data items (e.g., filtered items) (816). In some implementations, the mobile device may be configured to generate the entire rendered mapping interface, including buildings, points of interest, and/or other mapping elements. In some implementations, the mobile device may illustrate the location information as an overlay on a mapping interface generated by a third party, such as a mapping interface that permits the addition/overlay of custom location points. The mapping interface may be transmitted to a display of the mobile device. In some implementations, the location data item(s) may be transmitted to one or more server(s) (818). For instance, in one implementation, the mobile device may be configured to illustrate a last known location of the product, and an interface administered by the server(s) may allow a user to see several different locations over a specified timeframe.
- In some embodiments, the collected location data may be used to facilitate sharing of an unlocking code for the locking device. For example, as described below with respect to process 900, a first user of the locking device, such as an owner of the locking device, can share an unlocking code along with the GPS coordinates of the locking device with a second user. Referring to
FIG. 9 , a flow diagram of aprocess 900 for facilitating the sharing of a product unlock code and a product location between a first user and a second user is shown according to an exemplary embodiment. -
Process 900 begins when a sharing request is received from a first user (902). The sharing request is received by a backend server (e.g., server 104). The sharing request is initiated from the first user via a computing device, such as a smartphone running a system application, a laptop or desktop through a system website, or the like. The sharing request generally relates to a request from the owner or an authorized user of the locking device to provide guest access to a second user. The guest access includes an unlock code for the locking device. The unlock code provided to the second user may be a limited unlock code. For example, the unlock code may be a one-time use unlock code (i.e., allowing the secondary user to unlock the locking device only once), an unlock code that is valid for a limited number of unlocking events, a time or day limited unlock code that is only valid during certain time periods or a certain date range, or an expiring unlock code that expires after a designated time period. The sharing request may include a first user identifier, a locking device identifier (corresponding to the locking device), and a second user identifier. The sharing request may include any restrictions on the unlocking privileges to be provided to the second user (e.g., expiration, number of uses, time of acceptable use, day of acceptable use, etc.). The first user identifier and the second user identifier may include any of e-mail addresses, phone numbers, usernames, and other information used in verifying the identity of the first and second users. - After the sharing request is received, the first user is authenticated (904). In some embodiments, the backend server authenticates the first user as an owner or as an authorized user of the locking device (e.g., an individual or entity that has unlocking code sharing privileges associated with the locking device). The first user is authenticated based at least in part on the first user identifier. During the authentication, the backend server may prompt the first user via the computing device to provide a password or a PIN to complete the authentication process. If the backend server is able to authenticate the first user as the owner of the locking device or as an authorized user of the locking device,
process 900 continues. In some arrangements, a message may be transmitted to the first user that indicates the successful authentication. The message may include updated locking device status information, such as a low battery warning. If the backend server is unable to authenticate the first user,process 900 ends. In some embodiments, authentication may be performed without use of the backend server, such as by using authentication data (e.g., a list of authorized identifiers) stored on the device of the second user. - After the first user is authenticated at 904, a share message is transmitted to the second user (906). In some embodiments, the share message is transmitted to the second user by the backend server. The share message may be an e-mail message, a text message, an application notification (e.g., if the second user is known a registered user of the locking device authentication system, and alert may be pushed to the user via a system application running on the second user's computing device), etc. The share message type may be determined based on information contained in the sharing request (e.g., the second user identifier). The share message indicates that the first user wants to provide the second user the ability to unlock the locking device. The share message may include an option to reject the share request. For example, in some arrangements, the second user may not want to access the locking device, and the user is presented with the option to reject the share request. In some arrangements, after the share message is sent to the second user at 906, the second user is authenticated (908). The locking device system may require that the second user (e.g., the guest user) be a registered user of the system. In such arrangements, the share message may invite the second user to either log in to the locking device system or to register as a user of the locking device system in order to gain access to the unlocking privilege for the locking device. In arrangements where the second user is authenticated, the location information of the locking device may be omitted from the original share message and sent in a follow-up message after the second user has been authenticated. In other arrangements, the second user does not need to be a registered user to receive the share message.
- An unlock code is generated and transmitted to the second user (910). In some embodiments, the unlock code is generated by the backend server and transmitted to the second user via a locking device system application on a computing device associated with the second user. Generating and transmitting the unlock code may include generating and encrypting a user profile and access key later used to unlock the locking device (as described above in
process 200 inFIG. 2 ). In some arrangements, the unlock code is transmitted along with location information relating to the location of the locking device. In some embodiments, the location information may include an address of the location of the locking device, a map showing the location of the locking device, or a combination thereof. In some embodiments, the location information may include data (e.g., a position identifier, such as GPS coordinates) that an application operating on the second device may use to generate data to present (e.g., display) to the second user, such as an address, map, driving/walking directions, etc. The second user can utilize the unlock code via the second user's computing device to unlock the locking device in a similar manner as described above with respect to process 300 inFIG. 3 . - After the second user interacts with the locking device, lock event information may be received (912). The lock event information may relate to an unlock event, in which the locking device is unlocked, or a lock event, in which the locking device is locked. In each situation, the second user's computing device (e.g., a smartphone) may transmit the lock event information to the backend server. The lock event information may include an indication that the second user either locked or unlocked the locking device, a time of the lock event, and an updated location of the locking device (as determined by the second user's computing device). The updated location of the locking device may be obtained as described above in
process 800 inFIG. 8 . - The received lock event information may be stored (914). In some embodiments, the backend server stores the lock event information and updates the last known location of the locking device based on the locking device location information received in the lock event information. In some arrangements, an alert is sent to the first user (916). The alert is sent from the backend server to the first user via e-mail, text message, application notification, or the like. The alert includes an indication of the lock event. In some arrangements, the alert also includes updated location information relating to the locking device. In some embodiments, data (e.g., the alert) may be transmitted between the first and second user devices without using the backend server as an intermediary system.
- The above-described
process 900 can be applied in many different scenarios. For example,method 900 may be applicable in a real estate showing scenario where the locking device is a realtor key box. In such a scenario, a listing agent may be the first user (i.e., the owner or operator of the realtor key box) and the listing agent can share the key code, along with the location of the key box for a property, with a second agent or a potential buyer of the property. The key box unlock code and location sharing may be facilitated through a realtor management mobile application. As another example,process 900 may be applicable in an equipment sharing program (e.g., a bike sharing system) in which various users share the equipment. In such a scenario, each piece of equipment may be associated with a locking device. When a user wants to use a piece of equipment (e.g., a bike in a bike share program), the user can access his locking device application, receive the location of the nearest equipment (as defined by the location of the associated locking device), and receive the locking code to unlock the equipment. When the locking device is relocked (e.g., when the user is done using the bike), the location of the equipment may be uploaded back to the server with the locking event such that the equipment can be located for the next user. - In some embodiments, a backend server (e.g., server 104) calculates an expected battery life of a product (e.g., a locking device,
product 106,product 700, etc.) and initiates low battery alerts to users based at least in part on the actual usage history of the product. Referring toFIG. 10 , a flow diagram of aprocess 1000 of estimating battery life based at least in part on an actual usage audit trail and initiating low battery alerts to users is shown according to an exemplary embodiment. -
Process 1000 begins when lock event information relating to the product is received (1002). The lock event information relates to a lock event (e.g., a locking or unlocking of the product as described above with respect toprocesses - The lock event information is stored (1004). In some embodiments, the backend server stores the lock event information in a database of lock event information stored on the backend server. The lock event information may be associated with the particular product in the database (e.g., based on the serial number of the product). The backend server may store each lock event associated with the product in the database. The backend server can analyze the database to form a historical analysis of the usage of the product, which is herein referred to as an audit trail. The audit trail of the product can be analyzed to determine usage statistics of the product. The usage statistics may include various metrics such as an average time (e.g., number of hours, number of days, etc.) between lock events (e.g., unlockings and lockings), the amount of awake time or sleep time, battery statistics (e.g., voltage/state of charge/discharge readings at lock events, time since last battery replacement or recharge, etc.), location information (e.g., the location of the product at each lock event), and the like. The audit trail can also be used by the backend server to predict future usage (e.g., the timing and/or frequency of future lock events) based on the historical usage of the product. The future usage may relate to an estimated amount of time (e.g., number of hours, number of days, etc.) until the next lock event.
- The expected battery life of the product is calculated (1006). In some embodiments, the backend server calculates the expected battery life of the product based on the audit trail (both historical usage information and predicted future information) and based battery characteristics (e.g., the battery's age, the battery's capacity, etc.). The expected battery life may be calculated in estimated number of days remaining For example, the backend server may determine the average amount of battery used for each lock event, determine the amount of battery consumed for standby time between lock events, and determine an expected life of the battery in days based on the average number of days between historical lock events (i.e., the predicted amount of time from the lock event until the next lock event). The determined battery condition may be adjusted based on weather predictions for the location of the product. The weather prediction may be pulled from a third-party weather service. For example, in certain cold or hot conditions, the product may consumer more battery than in normal operating conditions. In some situations, the lock event information includes an expected battery life. For example, the product may transmit (via a user's computing device) a low battery warning indicating the battery has a limited amount of life or charge remaining In other embodiments, the battery life may be calculated on the locking device itself, rather than or in addition to at the backend server.
- Based on the calculated expected battery life, the backend server determines whether a low battery life condition is expected (1008). In some embodiments, a low battery life condition is expected if the battery of the product is expected to fully discharge before the next expected or predicted lock event (based on historical product usage statistics and predicted time until the next lock event). In such an embodiment, the low battery life condition may be expected if the battery has below the threshold amount of battery capacity remaining needed by the product to last until the predicted next lock event. In some embodiments, a low battery life condition may be triggered when the remaining battery life is less than that expected to be needed to power the locking device through a predetermined number of further lock events.
- If a low battery condition is expected, the backend system initiates an alert to a user of the product (1010). The alert may be an e-mail message, a text message, an application message, etc. In some embodiments, the alert includes an indication to the user that the battery is expected to die before the next lock event, within a predetermined number of lock events, etc. The alert may include replacement battery information, such as the type of battery the user needs to purchase and battery replacement instructions. The alert may include a listing of retailers in the vicinity of the product or the user (e.g., within a threshold number of miles from the product or the user) that carry replacement batteries for the product. In some arrangements, the alert includes a map providing the location of the product. The map may include the nearest retailers that carry replacement batteries for the product. If a low battery is not expected,
process 1000 returns to calculating the expected battery life of the product at 1006. The backend server may continuously or periodically calculate and monitor the expected battery life of the product until a low battery alert is initiated by the backend server to a user associated with the product. - In further embodiments, a backend server (e.g., server 104) calculates an expected battery life of a product (e.g., a locking device,
product 106,product 700, etc.) and initiates low battery alerts to users based at least in part on the location of the product. Referring now toFIG. 11 , a flow diagram of aprocess 1100 of estimating battery life based at least in part on an the location of the product and initiating low battery alerts to users is shown according to an exemplary embodiment.Process 1100 begins when lock event information relating to the product is received (1102). The lock event information relates to a lock event (e.g., a locking or unlocking of the product as described above with respect toprocesses - The lock event information is stored (1104). In some embodiments, the backend server stores the lock event information in a database of lock event information. The lock event information is associated with the particularly product in the database (e.g., based on the serial number of the product). The backend server stores each lock event associated with the product in the database. The stored lock event information of the product can be analyzed to determine historical usage statistics of the product and to predict future usage of the product. The usage statistics may include various metrics such as an average time (e.g., number of hours, number of days, etc.) between lock events (e.g., unlockings and lockings), the amount of awake time or sleep time, batter statistics (e.g., voltage readings at lock events, time since last battery replacement or recharge, etc.), location information (e.g., the location of the product at each lock event), and the like.
- Weather information is received (1108). The backend server receives weather information associated with the location of the product. In some arrangements, the lock event information includes the location of the product. In other arrangements, a user of the lock manually provides the location of the product to the backend system (e.g., through interaction with a system application). The weather information for the location of the product is received from a third-party weather service. The backend server may request (i.e., pull) the weather information from the third-party weather service. The weather information may include various weather conditions, such as temperature, humidity, precipitation, cloud coverage, and the like. The weather information may be received for weather conditions at the time of the lock event, during times between lock events, and historical weather conditions from prior to the lock event. The received weather information may be stored in the database (in a similar manner as described above with respect to 1104). Updated weather information may be pulled by the backend server at regular intervals (e.g., hourly, once a day, once a week, etc.).The expected battery life of the product is calculated (1108). In some embodiments, the backend server calculates the expected battery life of the product based on the audit trail and base battery characteristics (e.g., the battery's age, the battery's capacity, etc.). The expected battery life may be calculated in estimated number of days remaining For example, the backend server may determine the average amount of battery used for each lock event, determine the amount of battery consumed for standby time between lock events, and determine an expected life of the battery in days based on the average number of days between historical lock events. The expected battery life is adjusted (e.g., increased or decreased) based on the weather information received at 1106. For instance, in some embodiments, the weather information may be a factor considered in calculating the expected battery life. In certain cold or hot conditions, the battery may be adversely affected in terms of battery life as compared to ideal battery operating conditions. For example, if the product is outside during a winter storm with abnormally cold temperatures, such as 10 degrees Fahrenheit, the battery life of the product may be negatively impacted. The battery life adjustments based on weather are continuously or repeatedly performed (e.g., once an hour, once a day, once a week, etc.).
- Based on the calculated expected battery life, the backend server determines whether a low battery life condition is determined (1110). In some embodiments, a low battery life condition occurs when the battery of the product is estimated (based on the usage information and the weather information) to fall below a threshold level of charge (e.g., a threshold voltage level). If a low battery life condition is not determined, the
process 1100 returns to receiving updated weather information (1106) and calculated expected battery life (1108) for updating the calculated expected battery life. If a low battery condition is determined, the backend system initiates an alert to a user of the product (1112). The alert may be an e-mail message, a text message, an application message, etc. The alert includes an indication to the user that the product batter has reached a low level of charge. The alert may include replacement battery information, such as the type of battery the user needs to purchase and battery replacement instructions. The alert may include a listing of retailers near the product or the user that carry replacement batteries for the product. In some arrangements, the alert includes a map providing the location of the product. The map may include the nearest retailers that carry replacement batteries for the product. - Reference in this specification to “one embodiment,” “some embodiments,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearance of the phrase “in one embodiment” or “in some embodiments” in various places in the specification is not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
- The disclosure is described above with reference to drawings. These drawings illustrate certain details of specific embodiments that implement the systems and methods and programs of the present disclosure. However, describing the disclosure with drawings should not be construed as imposing on the disclosure any limitations that may be present in the drawings. The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing its operations. The embodiments of the present disclosure may be implemented using an existing computer processor, or by a special purpose computer processor incorporated for this or another purpose or by a hardwired system. No claim element herein is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for.” Furthermore, no element, component or method step in the present disclosure is intended to be dedicated to the public, regardless of whether the element, component or method step is explicitly recited in the claims.
- Embodiments within the scope of the present disclosure include program products comprising machine-readable storage media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media which can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machine to perform a certain function or group of functions. While a computer or machine-readable storage medium is not a propagated signal (i.e., is tangible and non-transitory), a computer or machine-readable storage medium can be a source or destination of computer program instructions encoded in an artificially-generated and propagated signal.
- Embodiments of the disclosure are described in the general context of method steps which may be implemented in one embodiment by a program product including machine-executable instructions, such as program code, for example, in the form of program modules executed by machines in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Machine-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
- Embodiments of the present disclosure may be practiced in a networked environment using logical connections to one or more remote computers having processors. Logical connections may include a local area network (LAN) and a wide area network (WAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets and the Internet and may use a wide variety of different communication protocols. Those skilled in the art will appreciate that such network computing environments will typically encompass many types of computer system configurations, including personal computers, hand-held devices, mobile phones, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, servers, minicomputers, mainframe computers, and the like. Embodiments of the disclosure may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
- An exemplary system for implementing the overall system or portions of the disclosure might include a general purpose computing device in the form of a computer, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The system memory may include read only memory (ROM) and random access memory (RAM). The computer may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to a removable optical disk such as a CD-ROM or other optical media. The drives and their associated machine-readable media provide nonvolatile storage of machine-executable instructions, data structures, program modules, and other data for the computer.
- It should be noted that although the flowcharts provided herein show a specific order of method steps, it is understood that the order of these steps may differ from what is depicted. Also, two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. It is understood that all such variations are within the scope of the disclosure. Likewise, software and web implementations of the present disclosure could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. It should also be noted that the word “component” as used herein and in the claims is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving manual inputs.
- The foregoing description of embodiments of the disclosure have been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosure. The embodiments were chosen and described in order to explain the principals of the disclosure and its practical application to enable one skilled in the art to utilize the disclosure in various embodiments and with various modifications as are suited to the particular use contemplated.
Claims (20)
1. A method of predicting a battery life of an electronic locking product based at least in part on a usage history of the electronic locking product, the method comprising:
receiving, at a server, lock event information associated with a lock event of the electronic locking product from a user device;
storing, in a database of the server, the lock event information, wherein the lock event information is associated with the electronic locking product in the database;
calculating, by the server, an expected battery life of a battery of the electronic locking product based at least in part on the lock event information;
determining, by the server, that the expected battery life of the battery is below a threshold value; and
initiating, by the server, an alert to a user computing device indicating a low battery condition of the battery in response to determining that the expected battery life is below the threshold value.
2. The method of claim 1 , wherein the lock event information includes a location of the locking device, and wherein the method further comprises receiving, by the server, weather information from a weather service.
3. The method of claim 2 , further comprising adjusting, by the server, the expected battery life of the battery based on the weather information.
4. The method of claim 1 , further comprising predicting, by the server, an estimated amount of time until a predicted next lock event.
5. The method of claim 4 , wherein the threshold value relates to an estimated amount of battery capacity needed by the electronic locking product during the estimated amount of time until the predicted next lock event.
6. The method of claim 1 , further comprising identifying at least one retailer in the vicinity of the product or the user that carries replacement batteries for the electronic locking product, wherein the alert includes an identification of the at least one retailer.
7. The method of claim 6 , wherein the alert further includes a map providing a location of the electronic locking product.
8. A method of sharing an unlocking code to an electronic locking product by a first user to a second user, the electronic locking product including an electronically controllable mechanical locking mechanism, the method comprising:
receiving, by a server, a sharing request from a first user computing device associated with the first user, wherein the sharing request indicates a request from the first user to provide guest access to a second user;
authenticating, by the server, the first user as at least one of an owner or an authorized user of the electronic locking product;
generating, by the server, an unlock code for the electronic locking product; and
transmitting, by the server, a message to a second user computing device associated with the second user, the message including the unlock code.
9. The method of claim 8 , wherein the unlock code is a one-time use unlock code that expires after a first use of the unlock code by the second user.
10. The method of claim 8 , further comprising authenticating the second user as a registered user of the electronic locking product.
11. The method of claim 8 , wherein the message includes location information relating to a location of the electronic locking product.
12. The method of claim 8 , further comprising receiving, at the server, lock event information corresponding to the secondary user locking the electronic locking product.
13. The method of claim 12 , further comprising sending, by the server, a message to the primary user computing device, the message including updated location information relating to the electronic locking product.
14. A locking product system comprising:
an electronic locking device including a battery, a wireless transceiver, an electronically controllable locking mechanism, and a first processor configured to lock and unlock the electronically controllable locking mechanism and to transmit information to a backend server via a user computing device;
the backend server including a memory and a second processor, the second processor configured to:
receive lock event information associated with a lock event of the electronic locking product from a user device;
store the lock event information, wherein the lock event information is associated with the electronic locking product in the database;
calculate an expected battery life of a battery of the electronic locking product based at least in part on the lock event information;
determine that the expected battery life of the battery is below a threshold value; and
initiate an alert to a user computing device associated with a user of the electronic locking product indicating a low battery condition of the battery.
15. The system of claim 14 , wherein the lock event information includes a location of the locking device, and wherein the second processor is further configured to receive weather information from a weather service.
16. The system of claim 15 , wherein the second processor is further configured to adjust the expected battery life of the battery based on the weather information.
17. The system of claim 14 , wherein the second processor is further configured to estimate amount of time until a predicted next lock event.
18. The system of claim 17 , wherein the threshold value relates to an estimated amount of battery capacity needed by the electronic locking product during the estimated amount of time until the predicted next lock event.
19. The system of claim 15 , wherein the second processor is further configured to identify at least one retailer in the vicinity of the product or the user that carry replacement batteries for the electronic locking product, wherein the alert includes an identification of the at least one retailer.
20. The system of claim 19 , wherein the alert further includes a map providing a location of the electronic locking product.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/524,558 US20160116510A1 (en) | 2014-10-27 | 2014-10-27 | Predictive battery warnings for an electronic locking device |
PCT/US2015/057402 WO2016069486A1 (en) | 2014-10-27 | 2015-10-26 | Predictive battery warnings for an electronic locking device |
US15/846,078 US10094885B2 (en) | 2014-10-27 | 2017-12-18 | Predictive battery warnings for an electronic locking device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/524,558 US20160116510A1 (en) | 2014-10-27 | 2014-10-27 | Predictive battery warnings for an electronic locking device |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/846,078 Continuation US10094885B2 (en) | 2014-10-27 | 2017-12-18 | Predictive battery warnings for an electronic locking device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160116510A1 true US20160116510A1 (en) | 2016-04-28 |
Family
ID=55791795
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/524,558 Abandoned US20160116510A1 (en) | 2014-10-27 | 2014-10-27 | Predictive battery warnings for an electronic locking device |
US15/846,078 Expired - Fee Related US10094885B2 (en) | 2014-10-27 | 2017-12-18 | Predictive battery warnings for an electronic locking device |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/846,078 Expired - Fee Related US10094885B2 (en) | 2014-10-27 | 2017-12-18 | Predictive battery warnings for an electronic locking device |
Country Status (2)
Country | Link |
---|---|
US (2) | US20160116510A1 (en) |
WO (1) | WO2016069486A1 (en) |
Cited By (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160036594A1 (en) * | 2014-07-30 | 2016-02-04 | Master Lock Company | Wireless key management for authentication |
US20160156604A1 (en) * | 2014-12-01 | 2016-06-02 | Samsung Electronics Co., Ltd. | Method and cloud server for managing device |
US20170109952A1 (en) * | 2015-06-05 | 2017-04-20 | August Home, Inc. | Intelligent door lock system with keypad |
US20170148242A1 (en) * | 2015-11-20 | 2017-05-25 | International Business Machines Corporation | Wireless lock |
US9894066B2 (en) | 2014-07-30 | 2018-02-13 | Master Lock Company Llc | Wireless firmware updates |
US9916746B2 (en) | 2013-03-15 | 2018-03-13 | August Home, Inc. | Security system coupled to a door lock system |
US20180075247A1 (en) * | 2016-09-09 | 2018-03-15 | Tyco Integrated Security, LLC | Architecture For Access Management |
DK201670667A1 (en) * | 2016-08-31 | 2018-03-19 | Floke Ivs | Locking system comprising lock and portable electronic device |
US20180146369A1 (en) * | 2016-11-18 | 2018-05-24 | Siemens Industry, Inc. | Secure access authorization method |
US9996999B2 (en) | 2014-07-30 | 2018-06-12 | Master Lock Company Llc | Location tracking for locking device |
US20180268633A1 (en) * | 2017-03-16 | 2018-09-20 | Samsung Electronics Co., Ltd. | Electronic device for controlling door lock and method thereof |
US10094885B2 (en) | 2014-10-27 | 2018-10-09 | Master Lock Company Llc | Predictive battery warnings for an electronic locking device |
US10142843B2 (en) | 2014-07-30 | 2018-11-27 | Master Lock Company Llc | Wireless key management for authentication |
US10304273B2 (en) | 2013-03-15 | 2019-05-28 | August Home, Inc. | Intelligent door lock system with third party secured access to a dwelling |
US10388094B2 (en) | 2013-03-15 | 2019-08-20 | August Home Inc. | Intelligent door lock system with notification to user regarding battery status |
WO2019185701A1 (en) * | 2018-03-28 | 2019-10-03 | Blancco Technology Group IP Oy | Determining battery wear of a mobile electronic device |
US10443266B2 (en) | 2013-03-15 | 2019-10-15 | August Home, Inc. | Intelligent door lock system with manual operation and push notification |
CN110473317A (en) * | 2018-05-11 | 2019-11-19 | Abus·奥古斯特·布莱梅克·索恩有限股份两合公司 | Portable lock |
CN110469206A (en) * | 2018-05-11 | 2019-11-19 | Abus·奥古斯特·布莱梅克·索恩有限股份两合公司 | Portable lock |
US10633891B2 (en) * | 2015-08-12 | 2020-04-28 | Airbolt Pty Ltd. | Portable electronic lock |
US10685516B1 (en) | 2019-03-22 | 2020-06-16 | Eingot Llc | Virtual intercom system |
US10691953B2 (en) | 2013-03-15 | 2020-06-23 | August Home, Inc. | Door lock system with one or more virtual fences |
US10846957B2 (en) | 2013-03-15 | 2020-11-24 | August Home, Inc. | Wireless access control system and methods for intelligent door lock system |
US10846958B2 (en) * | 2019-03-22 | 2020-11-24 | Eingot Llc | Virtual intercom system |
US10890015B2 (en) | 2018-09-21 | 2021-01-12 | Knox Associates, Inc. | Electronic lock state detection systems and methods |
US10970983B2 (en) | 2015-06-04 | 2021-04-06 | August Home, Inc. | Intelligent door lock system with camera and motion detector |
US10993111B2 (en) | 2014-03-12 | 2021-04-27 | August Home Inc. | Intelligent door lock system in communication with mobile device that stores associated user data |
US11043055B2 (en) | 2013-03-15 | 2021-06-22 | August Home, Inc. | Door lock system with contact sensor |
US11072945B2 (en) | 2013-03-15 | 2021-07-27 | August Home, Inc. | Video recording triggered by a smart lock device |
US11161626B2 (en) * | 2020-02-25 | 2021-11-02 | The Government of the United States of America, as represented by the Secretary of Homeland Security | Electronic baggage locks |
CN113824762A (en) * | 2021-08-06 | 2021-12-21 | 深圳易马达科技有限公司 | Use method of battery replacement device and battery replacement system |
US11212278B1 (en) * | 2010-02-26 | 2021-12-28 | United Services Automobile Association (Usaa) | Systems and methods for secure logon |
US11352812B2 (en) | 2013-03-15 | 2022-06-07 | August Home, Inc. | Door lock system coupled to an image capture device |
US11421445B2 (en) | 2013-03-15 | 2022-08-23 | August Home, Inc. | Smart lock device with near field communication |
US11441332B2 (en) | 2013-03-15 | 2022-09-13 | August Home, Inc. | Mesh of cameras communicating with each other to follow a delivery agent within a dwelling |
US11448522B2 (en) * | 2017-02-10 | 2022-09-20 | Kamstrup A/S | Radio frequency communication system and method |
CN115136020A (en) * | 2019-12-23 | 2022-09-30 | 阿帕雷奥物联网有限责任公司 | Remote battery estimation |
US11480949B2 (en) * | 2015-03-27 | 2022-10-25 | Rockwell Automation Technologies, Inc. | Systems and methods for virtually tagging and securing industrial equipment |
US11527121B2 (en) | 2013-03-15 | 2022-12-13 | August Home, Inc. | Door lock system with contact sensor |
US20230154260A1 (en) * | 2021-11-18 | 2023-05-18 | Capital One Services, Llc | Token based secure access to a locker system |
US11695780B2 (en) * | 2017-03-23 | 2023-07-04 | Glue Ab | Automated delivery security system |
US11802422B2 (en) | 2013-03-15 | 2023-10-31 | August Home, Inc. | Video recording triggered by a smart lock device |
US11900744B2 (en) | 2019-03-22 | 2024-02-13 | Eingot Llc | Virtual intercom system |
US11959308B2 (en) | 2020-09-17 | 2024-04-16 | ASSA ABLOY Residential Group, Inc. | Magnetic sensor for lock position |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10749693B2 (en) * | 2015-10-21 | 2020-08-18 | Rmd Innovations Pty. Ltd. | Method and system for facilitating use of an electronically controlled lock |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130099892A1 (en) * | 2011-10-20 | 2013-04-25 | Apple Inc. | Accessing a vehicle using portable devices |
US20130325521A1 (en) * | 2012-05-29 | 2013-12-05 | Akhtar Jameel | Shared vehicle rental system including vehicle availability determination |
US20140232524A1 (en) * | 2011-11-22 | 2014-08-21 | Mitsubishi Electric Corporation | Electronic key system, and lock-side terminal and portable terminal employed in same |
US8943187B1 (en) * | 2012-08-30 | 2015-01-27 | Microstrategy Incorporated | Managing electronic keys |
Family Cites Families (115)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5648763A (en) | 1992-10-05 | 1997-07-15 | Trimble Navigation, Ltd. | Method and apparatus for global position responsive security system |
US5565858A (en) | 1994-09-14 | 1996-10-15 | Northrop Grumman Corporation | Electronic inventory system for stacked containers |
US6047575A (en) | 1995-05-19 | 2000-04-11 | Slc Technologies, Inc. | Electronic padlock |
DE19528203C1 (en) | 1995-08-01 | 1996-10-24 | Christian Hogl | Locking system for useful object used by user for determined time |
US6046558A (en) | 1996-01-12 | 2000-04-04 | Slc Technologies, Inc. | Electronic padlock |
US6337618B1 (en) | 1999-10-07 | 2002-01-08 | James J. Craig | Programmable electromechanical lock with digital display |
CN1239800C (en) | 1999-11-30 | 2006-02-01 | 博丁数字有限公司 | Electronic key device, system and method of managing electronic key information |
GB0015328D0 (en) | 2000-06-22 | 2000-08-16 | Envopak Group Ltd | Locking system |
FI20002255A (en) | 2000-10-13 | 2002-04-14 | Nokia Corp | A method for controlling and controlling locks |
CA2324679A1 (en) * | 2000-10-26 | 2002-04-26 | Lochisle Inc. | Method and system for physical access control using wireless connection to a network |
US20120011366A1 (en) | 2001-12-27 | 2012-01-12 | Denison William D | Method for Controlling and Recording the Security of an Enclosure |
US20030179073A1 (en) | 2002-03-20 | 2003-09-25 | Ohanes Ghazarian | Electronic secure locking system |
US20070234052A1 (en) | 2002-06-25 | 2007-10-04 | Campisi Steven E | Electromechanical lock system |
CN1592811A (en) | 2002-07-31 | 2005-03-09 | 索尼株式会社 | Collective housing shared entrance device, collective housing door-to-door interphone device, door-to-door container box management device, and communication system |
JP2006508471A (en) | 2002-11-27 | 2006-03-09 | アールエスエイ セキュリティー インク | Identification and authentication system and method |
US20040108938A1 (en) | 2002-12-10 | 2004-06-10 | Entrekin David A. | Portable electronic locking system and method |
ATE492085T1 (en) | 2003-01-28 | 2011-01-15 | Cellport Systems Inc | A SYSTEM AND METHOD FOR CONTROLLING APPLICATIONS' ACCESS TO PROTECTED RESOURCES WITHIN A SECURE VEHICLE TELEMATICS SYSTEM |
US20080061191A1 (en) | 2003-05-06 | 2008-03-13 | Gochnour Gary R | Multi-functional high energy plasma aircraft and nuclear fusion system to produce energy from a controlled nuclear fusion reaction |
US20040255623A1 (en) | 2003-06-19 | 2004-12-23 | Conrad Sun | Biometric padlock |
US20050044906A1 (en) | 2003-07-25 | 2005-03-03 | Spielman Timothy G. | Method and system for setting entry codes via a communications network for access to moveable enclosures |
US20050099262A1 (en) | 2003-11-07 | 2005-05-12 | Childress Robert N. | Electronic wireless locking system |
US7209029B2 (en) | 2004-06-01 | 2007-04-24 | Kaba Ilco, Inc. | Electronic lock system and method for providing access thereto |
DE102004036564A1 (en) | 2004-07-28 | 2006-03-23 | Robert Bosch Gmbh | navigation device |
US7395097B2 (en) * | 2004-12-03 | 2008-07-01 | Motorola, Inc. | Communications device with low energy notification |
SE530279C8 (en) | 2005-03-18 | 2008-06-03 | Phoniro Ab | Method of unlocking a lock with a locking device capable of wireless short distance data communication in accordance with a communication standard, and an associated locking device |
CA2648523C (en) | 2005-04-21 | 2018-09-04 | Securedpay Solutions, Inc. | Portable handheld device for wireless order entry and real time payment authorization and related methods |
US8154397B2 (en) | 2005-05-04 | 2012-04-10 | Astrin Arthur W | Locking mechanism, systems and methods for cargo container transport security |
US20060288744A1 (en) | 2005-06-28 | 2006-12-28 | William Smith | Alarm lock |
MX2008001006A (en) | 2005-07-22 | 2008-04-04 | Neology Inc | Systems and methods for secure locking mechanisms. |
EP1780680B1 (en) | 2005-10-24 | 2018-01-17 | dormakaba Schweiz AG | Procedure for control of interlock and lock |
US7961076B2 (en) | 2006-02-28 | 2011-06-14 | International Business Machines Corporation | Methods and apparatuses for remote control of vehicle devices and vehicle lock-out notification |
SE529849C2 (en) | 2006-04-28 | 2007-12-11 | Sics Swedish Inst Of Comp Scie | Access control system and procedure for operating the system |
US8058971B2 (en) | 2006-06-07 | 2011-11-15 | Utc Fire & Security Americas Corporation, Inc. | Access control system |
US20070290799A1 (en) | 2006-06-07 | 2007-12-20 | Michael Harkins | Lockbox key with illuminator |
CN101490352B (en) | 2006-07-13 | 2013-05-29 | 大众汽车有限公司 | Key unit for a lock system of a vehicle |
US7782200B1 (en) | 2006-11-03 | 2010-08-24 | Fleischmann Arthur R | Reusable electronic trailer seal |
KR101442169B1 (en) | 2007-11-27 | 2014-11-03 | 삼성전자주식회사 | A Public Key Infrastructure-based Bluetooth Smart-Key System and Operating Method Thereof |
US20090231434A1 (en) * | 2008-03-17 | 2009-09-17 | The Chamberlain Group Inc. | Method and Apparatus to Facilitate Communicating Operational Data As Pertains to a Self-Storage Facility |
ES2390797T3 (en) | 2008-08-20 | 2012-11-16 | Iloq Oy | Electromechanical lock |
US8126450B2 (en) | 2008-09-24 | 2012-02-28 | Embarq Holdings Company Llc | System and method for key free access to a vehicle |
US8070061B2 (en) | 2008-10-21 | 2011-12-06 | Habraken G Wouter | Card credential method and system |
US20110307394A1 (en) | 2009-06-12 | 2011-12-15 | Rzepecki S Ryan | Municipal bicycle sharing system |
CA2766778A1 (en) * | 2009-06-26 | 2010-12-29 | Cubic Corporation | Floating j-hooks between two bushings in housing with a single piston |
US20110050419A1 (en) | 2009-08-26 | 2011-03-03 | Kwanyuen Ng | Remote Intrusion Signaling Security System |
SE534520C2 (en) | 2009-11-27 | 2011-09-20 | Phoniro Ab | Access control method and associated locking device and administration server |
US8707414B2 (en) | 2010-01-07 | 2014-04-22 | Honeywell International Inc. | Systems and methods for location aware access control management |
GB201000288D0 (en) | 2010-01-11 | 2010-02-24 | Scentrics Information Security | System and method of enforcing a computer policy |
US9092963B2 (en) | 2010-03-29 | 2015-07-28 | Qualcomm Incorporated | Wireless tracking device |
US8412934B2 (en) | 2010-04-07 | 2013-04-02 | Apple Inc. | System and method for backing up and restoring files encrypted with file-level content protection |
US9460480B2 (en) | 2010-04-09 | 2016-10-04 | Showingtime.Com, Inc. | Integrated real estate showing scheduling and key management system |
EP2559009A1 (en) | 2010-04-15 | 2013-02-20 | Benyamin Parto | Wireless controlled electromechanical cylinder |
US20110291803A1 (en) | 2010-05-27 | 2011-12-01 | Zeljko Bajic | Rfid security and mobility architecture |
EP2583430B1 (en) | 2010-06-16 | 2019-09-25 | Delphian Systems, LLC | Wireless device enabled locking system |
KR101107556B1 (en) | 2010-07-02 | 2012-01-31 | (주)디에이치테크놀로지 | Container electronic seal apparatus for locking and unlocking by using external memory and operating method thereof |
US20120073338A1 (en) | 2010-09-23 | 2012-03-29 | Dave Mohla | Intelligent Automated Deadbolt |
CN103282591B (en) * | 2010-09-28 | 2016-02-17 | 斯达康全球定位系统有限公司 | For the state detector of remote tracing padlock and communication unit and system |
CN101984575B (en) | 2010-10-14 | 2015-06-03 | 中兴通讯股份有限公司 | Method and device for protecting mobile terminal software |
US20150022315A1 (en) | 2010-11-11 | 2015-01-22 | Kwan Yuen Abraham Ng | Method of Programming a Programmable Electronic Lockbox System |
US8344713B2 (en) | 2011-01-11 | 2013-01-01 | Freescale Semiconductor, Inc. | LDO linear regulator with improved transient response |
US20120227450A1 (en) | 2011-03-08 | 2012-09-13 | Security Enhancement Systems, Llc | Lock |
US9057210B2 (en) | 2011-03-17 | 2015-06-16 | Unikey Technologies, Inc. | Wireless access control system and related methods |
US9196104B2 (en) | 2011-03-17 | 2015-11-24 | Unikey Technologies Inc. | Wireless access control system and related methods |
US9781571B2 (en) | 2011-04-20 | 2017-10-03 | Sony Corporation | Methods, systems and computer program products for registration of and anonymous communications related to tagged objects |
EP2700210B1 (en) | 2011-04-20 | 2020-12-09 | Sony Network Communications Europe B.V. | Methods, systems and computer program products for anonymous tracking of objects |
EP2710562A1 (en) | 2011-05-02 | 2014-03-26 | Apigy Inc. | Systems and methods for controlling a locking mechanism using a portable electronic device |
US9041511B2 (en) | 2011-05-03 | 2015-05-26 | Verizon Patent And Licensing Inc. | Facility management using mobile devices |
US9425981B2 (en) | 2011-07-14 | 2016-08-23 | Colin Foster | Remote access control to residential or office buildings |
CN108274436B (en) * | 2011-07-24 | 2021-08-27 | 株式会社牧田 | Adapter for electric tool and electric tool system |
US8902040B2 (en) | 2011-08-18 | 2014-12-02 | Greisen Enterprises Llc | Electronic lock and method |
US20130293368A1 (en) | 2011-09-20 | 2013-11-07 | Chikezie Ottah | Esom security |
US8805304B2 (en) | 2011-10-25 | 2014-08-12 | Scintera Networks Llc | Linearization of broadband power amplifiers |
US20130125231A1 (en) | 2011-11-14 | 2013-05-16 | Utc Fire & Security Corporation | Method and system for managing a multiplicity of credentials |
US8947200B2 (en) | 2011-11-17 | 2015-02-03 | Utc Fire & Security Corporation | Method of distributing stand-alone locks |
US20130335193A1 (en) | 2011-11-29 | 2013-12-19 | 1556053 Alberta Ltd. | Electronic wireless lock |
US20130244684A1 (en) | 2012-03-13 | 2013-09-19 | Google Inc. | Permissions based on wireless network data |
WO2013148274A1 (en) | 2012-03-28 | 2013-10-03 | Master Lock Company | Systems and methods for electronic locking device power management |
US9890106B2 (en) | 2012-04-30 | 2018-02-13 | King Abdullah University Of Science & Technology | Anti-cancer lead molecule |
MX353780B (en) * | 2012-05-08 | 2018-01-29 | Schlage Lock Co Llc | Remote management of electronic products. |
US8837733B2 (en) | 2012-05-16 | 2014-09-16 | Intel Corporation | System for protection and authentication of location services with distributed security |
US20130332370A1 (en) * | 2012-06-06 | 2013-12-12 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Replaceable battery valuation system |
US20130342314A1 (en) | 2012-06-22 | 2013-12-26 | Gun Chen | Smart lock structure and operating method thereof |
WO2014007870A1 (en) | 2012-07-06 | 2014-01-09 | Fingi Inc. | Entry lock control and operation system |
US20140033774A1 (en) | 2012-08-06 | 2014-02-06 | Kevin OFCHUS | Anti-theft system and method for fuel or other cargo in mobile storage containers |
US20140049367A1 (en) | 2012-08-16 | 2014-02-20 | Schlage Lock Company Llc | Automatic unlock device and method |
NZ706021A (en) | 2012-08-16 | 2016-03-31 | Schlage Lock Co Llc | Wireless electronic lock system and method |
US9508206B2 (en) | 2012-08-16 | 2016-11-29 | Schlage Lock Company Llc | Usage of GPS on door security |
US9472034B2 (en) | 2012-08-16 | 2016-10-18 | Schlage Lock Company Llc | Electronic lock system |
AU2013302374B2 (en) | 2012-08-16 | 2017-01-05 | Schlage Lock Company Llc | Wireless reader system |
DK2701124T3 (en) | 2012-08-21 | 2021-10-18 | Bekey As | Managing an access to a locality |
US8787902B2 (en) | 2012-10-31 | 2014-07-22 | Irevo, Inc. | Method for mobile-key service |
US9679429B2 (en) | 2012-12-03 | 2017-06-13 | 13876 Yukon Inc. | Wireless portable lock system |
US8909196B2 (en) | 2012-12-10 | 2014-12-09 | Actiontec Electronics, Inc. | Systems and methods for facilitating communication between mobile devices and wireless access points |
WO2014107196A1 (en) | 2013-01-04 | 2014-07-10 | Unikey Technologies, Inc. | Wireless access control system and related methods |
US20140218167A1 (en) | 2013-02-04 | 2014-08-07 | K-Jump Health Co., Ltd. | Wirelessly sensed and controlled locking device |
US9310147B2 (en) | 2013-02-06 | 2016-04-12 | Karl F. Milde, Jr. | Secure smartphone-operated gun trigger lock |
US8919024B2 (en) | 2013-02-06 | 2014-12-30 | Karl F. Milde, Jr. | Secure smartphone-operated gun trigger lock |
US9316454B2 (en) | 2013-02-06 | 2016-04-19 | Karl F. Milde, Jr. | Secure smartphone-operated gun lock with means for overriding release of the lock |
US20140250954A1 (en) | 2013-03-06 | 2014-09-11 | James F. Buzhardt | Smart padlock |
US20140266588A1 (en) | 2013-03-15 | 2014-09-18 | Mesh Motion, Inc. | Peer-to-peer bike sharing system |
US9704314B2 (en) | 2014-08-13 | 2017-07-11 | August Home, Inc. | BLE/WiFi bridge that detects signal strength of Bluetooth LE devices at an exterior of a dwelling |
US9659424B2 (en) | 2013-06-20 | 2017-05-23 | Parakeet Technologies, Inc. | Technologies and methods for security access |
US9763086B2 (en) | 2013-08-27 | 2017-09-12 | Qualcomm Incorporated | Owner access point to control the unlocking of an entry |
US8922333B1 (en) | 2013-09-10 | 2014-12-30 | Gregory Paul Kirkjan | Contactless electronic access control system |
US20150102902A1 (en) | 2013-10-16 | 2015-04-16 | Jie-Fu Chen | Bluetooth Remote-Control Electronic Lock |
US20170030109A1 (en) | 2013-11-29 | 2017-02-02 | 13876 Yukon Inc. | Portable locks and lock systems |
US20150170447A1 (en) | 2013-12-12 | 2015-06-18 | James F Buzhardt | Smart door lock |
US20150292244A1 (en) | 2014-04-10 | 2015-10-15 | Gleyn Beatty | Proximity Padlock |
US9734644B2 (en) | 2014-04-25 | 2017-08-15 | The Chamberlain Group, Inc. | Wireless camera facilitated building security |
US9542785B2 (en) | 2014-05-19 | 2017-01-10 | Acsys Ip Holding, Inc. | Mobile key devices systems and methods for programming and communicating with an electronic programmable key |
US9894066B2 (en) | 2014-07-30 | 2018-02-13 | Master Lock Company Llc | Wireless firmware updates |
US9996999B2 (en) | 2014-07-30 | 2018-06-12 | Master Lock Company Llc | Location tracking for locking device |
US9600949B2 (en) | 2014-07-30 | 2017-03-21 | Master Lock Company Llc | Wireless key management for authentication |
US9109379B1 (en) | 2014-08-12 | 2015-08-18 | Dog & Bone Holdings Pty Ltd | Keyless padlock, system and method of use |
US9746524B2 (en) * | 2014-09-12 | 2017-08-29 | Measurement Ltd. | System and method for monitoring battery status |
US20160116510A1 (en) | 2014-10-27 | 2016-04-28 | Master Lock Company | Predictive battery warnings for an electronic locking device |
-
2014
- 2014-10-27 US US14/524,558 patent/US20160116510A1/en not_active Abandoned
-
2015
- 2015-10-26 WO PCT/US2015/057402 patent/WO2016069486A1/en active Application Filing
-
2017
- 2017-12-18 US US15/846,078 patent/US10094885B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130099892A1 (en) * | 2011-10-20 | 2013-04-25 | Apple Inc. | Accessing a vehicle using portable devices |
US20140232524A1 (en) * | 2011-11-22 | 2014-08-21 | Mitsubishi Electric Corporation | Electronic key system, and lock-side terminal and portable terminal employed in same |
US20130325521A1 (en) * | 2012-05-29 | 2013-12-05 | Akhtar Jameel | Shared vehicle rental system including vehicle availability determination |
US8943187B1 (en) * | 2012-08-30 | 2015-01-27 | Microstrategy Incorporated | Managing electronic keys |
Cited By (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11658968B1 (en) | 2010-02-26 | 2023-05-23 | United Services Automobile Association (Usaa) | Systems and methods for secure logon |
US11924203B1 (en) | 2010-02-26 | 2024-03-05 | United Services Automobile Association (Usaa) | Systems and methods for secure logon |
US11212278B1 (en) * | 2010-02-26 | 2021-12-28 | United Services Automobile Association (Usaa) | Systems and methods for secure logon |
US11441332B2 (en) | 2013-03-15 | 2022-09-13 | August Home, Inc. | Mesh of cameras communicating with each other to follow a delivery agent within a dwelling |
US11043055B2 (en) | 2013-03-15 | 2021-06-22 | August Home, Inc. | Door lock system with contact sensor |
US10388094B2 (en) | 2013-03-15 | 2019-08-20 | August Home Inc. | Intelligent door lock system with notification to user regarding battery status |
US11436879B2 (en) | 2013-03-15 | 2022-09-06 | August Home, Inc. | Wireless access control system and methods for intelligent door lock system |
US9916746B2 (en) | 2013-03-15 | 2018-03-13 | August Home, Inc. | Security system coupled to a door lock system |
US11421445B2 (en) | 2013-03-15 | 2022-08-23 | August Home, Inc. | Smart lock device with near field communication |
US11352812B2 (en) | 2013-03-15 | 2022-06-07 | August Home, Inc. | Door lock system coupled to an image capture device |
US11802422B2 (en) | 2013-03-15 | 2023-10-31 | August Home, Inc. | Video recording triggered by a smart lock device |
US11072945B2 (en) | 2013-03-15 | 2021-07-27 | August Home, Inc. | Video recording triggered by a smart lock device |
US11527121B2 (en) | 2013-03-15 | 2022-12-13 | August Home, Inc. | Door lock system with contact sensor |
US10445999B2 (en) | 2013-03-15 | 2019-10-15 | August Home, Inc. | Security system coupled to a door lock system |
US10977919B2 (en) | 2013-03-15 | 2021-04-13 | August Home, Inc. | Security system coupled to a door lock system |
US10846957B2 (en) | 2013-03-15 | 2020-11-24 | August Home, Inc. | Wireless access control system and methods for intelligent door lock system |
US10691953B2 (en) | 2013-03-15 | 2020-06-23 | August Home, Inc. | Door lock system with one or more virtual fences |
US10304273B2 (en) | 2013-03-15 | 2019-05-28 | August Home, Inc. | Intelligent door lock system with third party secured access to a dwelling |
US10443266B2 (en) | 2013-03-15 | 2019-10-15 | August Home, Inc. | Intelligent door lock system with manual operation and push notification |
US10993111B2 (en) | 2014-03-12 | 2021-04-27 | August Home Inc. | Intelligent door lock system in communication with mobile device that stores associated user data |
US10771975B2 (en) | 2014-07-30 | 2020-09-08 | Master Lock Company Llc | Revocation of access credentials for a disconnected locking device |
US9455839B2 (en) * | 2014-07-30 | 2016-09-27 | Master Lock Company Llc | Wireless key management for authentication |
US10262484B2 (en) | 2014-07-30 | 2019-04-16 | Master Lock Company Llc | Location tracking for locking device |
US11468721B2 (en) | 2014-07-30 | 2022-10-11 | Master Lock Company Llc | Guest access for locking device |
US20160036594A1 (en) * | 2014-07-30 | 2016-02-04 | Master Lock Company | Wireless key management for authentication |
US9894066B2 (en) | 2014-07-30 | 2018-02-13 | Master Lock Company Llc | Wireless firmware updates |
US9996999B2 (en) | 2014-07-30 | 2018-06-12 | Master Lock Company Llc | Location tracking for locking device |
US10142843B2 (en) | 2014-07-30 | 2018-11-27 | Master Lock Company Llc | Wireless key management for authentication |
US10094885B2 (en) | 2014-10-27 | 2018-10-09 | Master Lock Company Llc | Predictive battery warnings for an electronic locking device |
US20160156604A1 (en) * | 2014-12-01 | 2016-06-02 | Samsung Electronics Co., Ltd. | Method and cloud server for managing device |
US10142310B2 (en) * | 2014-12-01 | 2018-11-27 | Samsung Electronics Co., Ltd. | Method and cloud server for managing device |
US11480949B2 (en) * | 2015-03-27 | 2022-10-25 | Rockwell Automation Technologies, Inc. | Systems and methods for virtually tagging and securing industrial equipment |
US10970983B2 (en) | 2015-06-04 | 2021-04-06 | August Home, Inc. | Intelligent door lock system with camera and motion detector |
US9818247B2 (en) * | 2015-06-05 | 2017-11-14 | August Home, Inc. | Intelligent door lock system with keypad |
US20170109952A1 (en) * | 2015-06-05 | 2017-04-20 | August Home, Inc. | Intelligent door lock system with keypad |
US10633891B2 (en) * | 2015-08-12 | 2020-04-28 | Airbolt Pty Ltd. | Portable electronic lock |
US20170148242A1 (en) * | 2015-11-20 | 2017-05-25 | International Business Machines Corporation | Wireless lock |
US20190244454A1 (en) * | 2015-11-20 | 2019-08-08 | International Business Machines Corporation | Wireless lock |
US10354464B2 (en) * | 2015-11-20 | 2019-07-16 | International Business Machines Corporation | Wireless lock |
US10685512B2 (en) * | 2015-11-20 | 2020-06-16 | International Business Machines Corporation | Wireless lock |
DK201670667A1 (en) * | 2016-08-31 | 2018-03-19 | Floke Ivs | Locking system comprising lock and portable electronic device |
US10475272B2 (en) | 2016-09-09 | 2019-11-12 | Tyco Integrated Security, LLC | Architecture for access management |
US10692321B2 (en) * | 2016-09-09 | 2020-06-23 | Tyco Integrated Security Llc | Architecture for access management |
US10685526B2 (en) | 2016-09-09 | 2020-06-16 | Tyco Integrated Security, LLC | Architecture for access management |
US10636240B2 (en) | 2016-09-09 | 2020-04-28 | Tyco Integrated Security, LLC | Architecture for access management |
US11010754B2 (en) | 2016-09-09 | 2021-05-18 | Tyco Integrated Security, LLC | Architecture for access management |
US20180075247A1 (en) * | 2016-09-09 | 2018-03-15 | Tyco Integrated Security, LLC | Architecture For Access Management |
US10475273B2 (en) | 2016-09-09 | 2019-11-12 | Tyco Integrated Security, LLC | Architecture for access management |
US20180146369A1 (en) * | 2016-11-18 | 2018-05-24 | Siemens Industry, Inc. | Secure access authorization method |
US10492067B2 (en) * | 2016-11-18 | 2019-11-26 | Siemens Industry, Inc. | Secure access authorization method |
US11448522B2 (en) * | 2017-02-10 | 2022-09-20 | Kamstrup A/S | Radio frequency communication system and method |
US10490009B2 (en) * | 2017-03-16 | 2019-11-26 | Samsung Electronics Co., Ltd. | Electronic device for controlling door lock and method thereof |
US20180268633A1 (en) * | 2017-03-16 | 2018-09-20 | Samsung Electronics Co., Ltd. | Electronic device for controlling door lock and method thereof |
US11695780B2 (en) * | 2017-03-23 | 2023-07-04 | Glue Ab | Automated delivery security system |
US11765183B2 (en) | 2017-03-23 | 2023-09-19 | Glue Ab | Automated delivery security system |
US11360149B2 (en) | 2017-03-28 | 2022-06-14 | Blancco Technology Group IP Oy | Determining battery wear of a mobile electronic device |
WO2019185701A1 (en) * | 2018-03-28 | 2019-10-03 | Blancco Technology Group IP Oy | Determining battery wear of a mobile electronic device |
CN110469206A (en) * | 2018-05-11 | 2019-11-19 | Abus·奥古斯特·布莱梅克·索恩有限股份两合公司 | Portable lock |
US11859411B2 (en) | 2018-05-11 | 2024-01-02 | Abus August Bremicker Soehne Kg | Portable lock |
CN110473317A (en) * | 2018-05-11 | 2019-11-19 | Abus·奥古斯特·布莱梅克·索恩有限股份两合公司 | Portable lock |
US10890015B2 (en) | 2018-09-21 | 2021-01-12 | Knox Associates, Inc. | Electronic lock state detection systems and methods |
US11933075B2 (en) | 2018-09-21 | 2024-03-19 | Knox Associates, Inc. | Electronic lock state detection systems and methods |
US11598121B2 (en) | 2018-09-21 | 2023-03-07 | Knox Associates, Inc. | Electronic lock state detection systems and methods |
US10846958B2 (en) * | 2019-03-22 | 2020-11-24 | Eingot Llc | Virtual intercom system |
US11900744B2 (en) | 2019-03-22 | 2024-02-13 | Eingot Llc | Virtual intercom system |
US10685516B1 (en) | 2019-03-22 | 2020-06-16 | Eingot Llc | Virtual intercom system |
CN115136020A (en) * | 2019-12-23 | 2022-09-30 | 阿帕雷奥物联网有限责任公司 | Remote battery estimation |
US11655051B2 (en) | 2020-02-25 | 2023-05-23 | The Government of the United States of America, as represented by the Secretary of Homeland Security | Electronic bag locking and unlocking |
US11161626B2 (en) * | 2020-02-25 | 2021-11-02 | The Government of the United States of America, as represented by the Secretary of Homeland Security | Electronic baggage locks |
US11407528B2 (en) | 2020-02-25 | 2022-08-09 | The Government of the United States of America, as represented by the Secretary of Homeland Security | Electronic bag locking and unlocking |
US11959308B2 (en) | 2020-09-17 | 2024-04-16 | ASSA ABLOY Residential Group, Inc. | Magnetic sensor for lock position |
CN113824762A (en) * | 2021-08-06 | 2021-12-21 | 深圳易马达科技有限公司 | Use method of battery replacement device and battery replacement system |
US20230154260A1 (en) * | 2021-11-18 | 2023-05-18 | Capital One Services, Llc | Token based secure access to a locker system |
US11908262B2 (en) * | 2021-11-18 | 2024-02-20 | Capital One Services, Llc | Token based secure access to a locker system |
Also Published As
Publication number | Publication date |
---|---|
US10094885B2 (en) | 2018-10-09 |
US20180106871A1 (en) | 2018-04-19 |
WO2016069486A1 (en) | 2016-05-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10094885B2 (en) | Predictive battery warnings for an electronic locking device | |
US11468721B2 (en) | Guest access for locking device | |
US10262484B2 (en) | Location tracking for locking device | |
US9455839B2 (en) | Wireless key management for authentication | |
US10581850B2 (en) | Wireless firmware updates | |
US11275820B2 (en) | Locking device biometric access | |
EP3362931B1 (en) | Wireless firmware updates |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |