Patent Publication Number: US-2019197806-A1

Title: Location tracking for locking device

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 15/587,034, filed May 4, 2017, which is a continuation of U.S. patent application Ser. No. 14/447,489, filed Jul. 30, 2014, both of which are incorporated herein by reference in their entireties. 
    
    
     BACKGROUND 
     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. 
     SUMMARY 
     Disclosed herein are methods, systems, and computer-readable media for wireless key management for authentication. One embodiment relates to a method of authentication. The method comprises: transmitting, by a mobile device, a request to a product; transmitting, by the product, a security challenge to the mobile device; transmitting, by the mobile device, a response to the challenge and an encrypted user profile for the product, wherein the response comprises data generated with an access key that is stored by both the mobile device and the product, and wherein the user profile is encrypted by a server using a secret key that is stored by the server and the product; verifying, by the product, the response to the challenge, wherein the response is verified using the access key; validating, by the product in response to verifying the response, data from the mobile device. Validating the data comprises: decrypting the encrypted user profile, wherein the user profile is decrypted using the secret key; and verifying the decrypted user profile. The method further comprises initiating, by the product in response to validating the data, an action of the product as specified by the request. 
     One embodiment relates to a method of authentication. The method comprises: transmitting, by a mobile device, a request to a locking device; transmitting, by the locking device, a security challenge to the mobile device; transmitting, by the mobile device, a response to the challenge and an encrypted user profile for the locking device, wherein the response comprises data generated with an access key that is stored by both the mobile device and the locking device, and wherein the user profile is encrypted by a server using a secret key that is stored by the server and the locking device; verifying, by the locking device, the response to the challenge, wherein the response is verified using the access key; validating, by the locking device in response to verifying the response, data from the mobile device. Validating the data comprises: decrypting the encrypted user profile, wherein the user profile is decrypted using the secret key; and verifying the decrypted user profile. The method further comprises initiating, by the locking device in response to validating the data, an action of the locking device as specified by the request, wherein the action comprises activating a physical locking component of the locking device to unlock the locking device. 
     Another embodiment relates to an electronic locking device. The electronic locking device comprises: a battery configured to supply power to the electronic locking device; a wireless transceiver; a memory; an electronically controllable locking mechanism; and a processor. The processor is configured to store a secret key in the memory, wherein the secret key is associated with a first code for the electronic locking device; store an access key in the memory, wherein the access key is associated with a second code for the electronic locking device; receive, via the transceiver, a request from a mobile device; transmit, via the transceiver, a security challenge to the mobile device; verify, using the access key, a response to the challenge, wherein the response is received from the mobile device, and wherein the response comprises data generated with a copy of the access key stored by the mobile device; validate, in response to verifying the response, data from the mobile device. Validating the data comprises: decrypting an encrypted user profile, wherein the user profile is decrypted using the secret key, and wherein the user profile is encrypted by a server with a copy of the secret key stored by the server; and verifying the decrypted user profile. The processor is further configured to initiate, in response to validating the data, an action of the electronic locking device as specified by the request. 
     Another embodiment relates to a system. The system comprises one or more servers comprising one or more processors configured to: obtain an secret key for a product, wherein the secret key is associated with a unique code for the product; obtain an access key for the product, wherein the access key is associated with the unique code for the product; encrypt, using the secret key, a user profile for the product, wherein the user profile and unique code are provided by a mobile device, wherein the unique code associates the product with the user profile, and wherein the secret key and access key are obtained using the unique code; and provide the encrypted user profile and the access key to the mobile device, wherein the user profile comprises access data for the product. 
     Another embodiment relates to a system. The system comprises one or more servers comprising one or more processors configured to: obtain an secret key for a locking device, wherein the secret key is associated with a unique code for the locking device; obtain an access key for the locking device, wherein the access key is associated with the unique code for the locking device; encrypt, using the secret key, a user profile for the locking device, wherein the user profile and unique code are provided by a mobile device, wherein the unique code associates the locking device with the user profile, and wherein the secret key and access key are obtained using the unique code; and provide the encrypted user profile and the access key to the mobile device, wherein the user profile comprises access data for the locking device. 
     Another embodiment relates to an electronic locking device. The locking device includes a wireless transceiver, a memory, an electronically controllable locking mechanism, a processor, and a location determination circuit configured to determine a location of the electronic locking device. The processor is configured to receive one or more location data items indicating the location of the electronic locking device at one or more times, to store the one or more location data items in the memory, and to transmit the one or more location data items from the memory to a mobile device via the wireless transceiver. 
     Another embodiment relates to a mobile device including one or more processors configured to transmit a request for one or more location data items to a locking device and to receive a security challenge from the locking device. The one or more processors are further configured to transmit a response to the challenge and an encrypted user profile to the locking device. The response comprises data generated with an access key that is stored by both the mobile device and the locking device, the user profile is encrypted by a server using a secret key that is stored by the server and the locking device, and the locking device is configured to verify the response and validate the data. The one or more processors are further configured to obtain the one or more location data items from the locking device, the one or more location data items having been generated by a location determination circuit of the locking device and each indicating a location of the locking device at one or more times. The one or more processors are further configured to generate a mapping interface illustrating the one or more locations indicated by the one or more location data items. 
     Yet another embodiment relates to a method including generating, using a location determination circuit of a locking device, one or more location data items indicating a location of the locking device at one or more times. The method further includes transmitting, by a mobile device, a request for the one or more location data items to the locking device and transmitting, by the locking device, a security challenge to the mobile device. The method further includes transmitting, by the mobile device, a response to the challenge and an encrypted user profile for the locking device. The response includes data generated with an access key that is stored by both the mobile device and the locking device, and the user profile is encrypted by a server using a secret key that is stored by the server and the locking device. The method further includes verifying, by the locking device, the response to the challenge, wherein the response is verified using the access key. The method further includes validating, by the locking device in response to verifying the response, data from the mobile device. The validating includes decrypting the encrypted user profile, wherein the user profile is decrypted using the secret key and verifying the decrypted user profile. The method further includes transmitting the one or more location data items from the locking device to the mobile device in response to validating the data. 
     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. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       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. 
     
    
    
     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. 
     DETAILED DESCRIPTION 
     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&#39;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 a system  100  for wireless key management for authentication is shown, according to an embodiment. System  100  includes at least one user device  102 , server  104 , and product  106 . In an illustrative embodiment, user device  102  is a mobile device (e.g., a mobile phone) and product  106  is an electronic locking device. In general, user device  102  is configured to at least partially manage the operation of product  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., a processor  102   a,  memory  102   b,  timer  102   c,  transceivers  102   d  and  102   e,  user input devices  102   f,  etc.). 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 of processor  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 of processor  102   a,  or may be any other time keeping circuit of device  102 . The time value maintained by timer  102   c  may be used in secured communications as discussed further herein (e.g., in syncing time with product  106 , in providing timestamps related to events for logging purposes, etc.). Transceivers  102   d  and  102   e  may include various types of transceivers for different protocols of communication. In one embodiment, transceiver  102   d  includes cellular components for communicating with server  104  via a cellular network. In one embodiment, transceiver  102   d  includes wired or wireless (e.g., Wi-Fi) components for communicating with server  104  over the Internet or other network. Wireless transceiver  102   e  is configured to communicate with product  106 . In one embodiment, wireless transceiver  102   e  includes Bluetooth components for establishing a Bluetooth connection with product  106 . User device  102  can manage product  106  through the use of a management application that is configured to run on the user device (e.g., via processor  102   a  and memory  102   b ). For example, an app may be installed on a mobile phone (i.e., in the memory  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 (via wireless 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 a processor  106   a  for providing logic of the electronic locking device and a high current load (e.g., a motorized locking mechanism  106   g  that may be controlled by the processor). The high current load may include one or more lock mechanisms  106   g  (e.g., shackles, pins, memories, etc.) as discussed below. The electronic locking device may also include a battery  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/or digital 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 the battery  106   d  is driving the high current load  106   g.  In one embodiment, the circuit also includes a timer  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 a location 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 from wireless 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., via wireless 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 in memory  106   b.  Decrypted content may then be provided to another device (e.g., via wireless 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&#39;s touch, based on motion of a user, etc.). 
     Referring to  FIG. 1B , an example of an electronic locking device  100   b  is showing, according to one embodiment. Electronic locking device  100   b  typically includes one or more lock mechanisms (e.g., lock mechanisms  106   f ). For example, electronic locking device may include shackle  160  an interface  162 . In one embodiment, interface  162  includes a touch sensor configured to awake the electronic locking device  100   b  in response to a user&#39;s touch, as is discussed further herein. In one embodiment, interface  162  includes a proximity sensor configured to awake the electronic 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 unlock shackle  160 , etc.). Various processing and mechanical components  164  may be embedded within the case  166  of electronic locking device  100   b.  For example, the processing and mechanical 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,  lock mechanisms  106   g,  etc.) discussed with references to product  106  of  FIG. 1 . 
     Referring again to  FIG. 1 , in an illustrative embodiment, product  106  includes a wireless transceiver  106   f  for communications according to one or more wireless technologies (e.g., radiofrequency, 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  of server  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 of product  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 with product  106 . 
     Server  104  generally includes components (e.g., a processor  104   a,  memory  104   b,  network interface  104   e,  etc.) to communicate with user device  102  and provide authentication keys and encryption functions. Communications between server  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 allow server  104  to establish a connection to transceiver  102   d  of device  102 . In one embodiment, communications from network interface  104   e  are routed through a cellular interface, allowing server  104  to communicate with device  102  via a cellular network. In one embodiment, network interface  104   e  allows server  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 of memory  104   b  provide different functions of server  104 . For example, a device interface module  104   c  may be used to establish and manage communications with user device  102 . A security module  104   d  may be used for security related functionality (e.g., generating and storing keys, encrypting a user profile, etc.). The output of security module  104   d  may be provided to device 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 by security module  104   d  at the request of device 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 through network interface  104   e ) the access key and encrypted user profile to user device  102 . In this manner, user device  102  does not directly access security module  104   d.  In one embodiment, device interface module  104   c  and security module  104   d  are located on two separate 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 on server  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&#39;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 an illustrative 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&#39;s interactions with the lock, and may set a schedule based around the user&#39;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&#39;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&#39;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&#39;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&#39;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&#39;s mobile device to associate the guest&#39;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&#39;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&#39;s time/device is trusted, the user may unlock the lock and perform other interactions with the lock. After authentication, the lock&#39;s time and mobile device&#39;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&#39;s information (e.g., the lock&#39;s ID) ( 306 ). In one embodiment, the lock&#39;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&#39;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&#39;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&#39;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 , a device  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 of server  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 to processes  200  and  300 , etc.) and generate the signals necessary to communicate with other devices, encrypt and decrypt data, authenticate data, etc., in order to implement the techniques of this disclosure. 
     Device  400  typically includes at least one processor  402  coupled to a memory  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 the device  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 the processor  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 includes transceiver  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 where device  400  comprises an electronic lock, transceiver  406  may be a Bluetooth transceiver configured to communicate with a user&#39;s mobile device. As another example, in an embodiment where device  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 where device  400  comprises a mobile device, transceiver  406  may include a Wi-Fi or cellular transceiver configured to communicate with a server, and transceiver  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&#39;s operations are described by the sections herein referencing  FIGS. 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 a processing circuit  502 , which may include a processor  502   a,  a memory  502   b,  and a timer  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 of processor  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 access key module  504 , which is configured to store and provide the access key as requested by the other modules of memory  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 a profile 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 by application module  506 . The user may create one or more profiles corresponding to one or more products, which are transmitted (e.g., via transceiver  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) via wireless transceiver  502   e  as discussed herein. A response module  510  may include the security algorithms required for generation a response to a challenge sent by a product. Additionally, the response module  510  may include encryption/decryption and MAC authentication algorithms, which may be accessed by application module  506  during secured communications. Memory  502   b  may further include a timer  502   c,  which may include the clock components of processor  502   a,  for maintaining a device time to be used as described herein. 
     In some implementations, memory  502   b  may include a mapping 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 to  FIG. 8 . 
     User device  500  further includes transceiver  502   d  and wireless transceiver  502   e  (which may correspond to transceiver  102   d  and wireless 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 and wireless 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 of servers  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.). A server  600  may include a processing circuit  602 . Processing circuit  602  includes a processor  602   a  and memory  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 of processor  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 access key module  604  and security key module  606 . The access key module  604  and security key 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, access key modules  604  and security key 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 with security 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 profile module  608 . In one embodiment, the security functions of security module  610  and access key module  604  and security module  606  are located on separate servers  600  from profile module  608 . In this embodiment, various services may be provided by appropriate servers such that profile 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 a mapping 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 to  FIG. 8 . 
     Referring to  FIG. 7  a block diagram of a product  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 a processing circuit  702 , which may include a processor  702   a,  a memory  702   b,  and a timer  702   c  (which may include the clock components of processor  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 of processor  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.). For example memory  702   b  may include an access key module  704 , a security key module  706 , a security module  708 , and a control module  710 . The access key module  704  and security key module  706  are configured to store the product&#39;s corresponding access key and security key, respectively. Other modules of memory  702   b  may interact with access key module  704  and security key module  706 . For example 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 access key module  704  when generating a challenge to be sent to a user device. As another example, security module  708  may access security key 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 of memory  702   b  to implement the techniques disclosed herein with respect to a product. For example, in an embodiment where product  700  is a lock, after being awoken, control module  710  may attempt to pair/communicate with a user device (via wireless transceiver  702   d ). Control module  710  may also include operating system (e.g., an embedded operating system, firmware, etc.) software for product  700 . As another example, control module  710  may request security 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., lock mechanisms  702   f ) in response to a request (e.g., an unlock request for a lock, etc.). As another example, control module  710  may interface with lock mechanisms  702   f  to control a user&#39;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 a location determination circuit  702   g,  such as a Global Positioning System (GPS) device/receiver, that may determine one or more locations of product  700  at one or more times. In some such embodiments, memory  702   b  may include a position tracking module  712  configured to receive the location data from location determination circuit  702   g  and store data indicative of the location or position of product  700  at one or more times. One such embodiment is discussed below with respect to  FIG. 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 a battery  702   e  for providing power to the product. In an embodiment where product  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 lock mechanisms  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 a process  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. While process  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. 
     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.