FIELD

[0001] The present disclosure relates to generally to locks, and more particularly to system for initializing and controlling locks.

[0002] A centralized management system may be used to manage a plurality of electronic locks. When adding a lock to a management system it may be necessary to initialize the lock to the management system to facilitate secure control and communication between the management system and the newly added lock.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The above-mentioned and other features of the disclosure, and the manner of attaining them, will become more apparent and the disclosure itself will be better understood by reference to the following description taken in conjunction with the accompanying drawings, wherein:

[0004] FIG. 1 is a diagrammatic view of a lock supplier and a pair of customer systems that manage a plurality of locks supplied by the lock supplier to the customers;

[0005] FIG. 2 is a more detailed view of one of the customer systems; and

[0006] FIG. 3 is a diagrammatic view of a lock.

[0007] Corresponding reference characters indicate corresponding parts throughout the several views. The exemplifications set out herein illustrate exemplary embodiments of the invention, and such exemplifications are not to be construed as limiting the scope of the invention in any manner.

DETAILED DESCRIPTION

[0008] The embodiments disclosed herein are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed in the following detailed description. Rather, the embodiments are chosen and described so that others skilled in the art may utilize their teachings .

[0009] Figure 1 shows a lock supplier 10, such as a manufacturer or distributor of locks 12. Locks 12 are configured to secure containers 14, such as ATM's, safes, filing cabinets, etc. As shown in Fig. 3, lock 12 may include a key pad 4 that is typically accessible on an unsecured side of a container 14, a lock housing 6 typically located on the secured side of a container 14, and a bolt 8 the extends and retracts to lock and unlock container 14.

Additional details of suitable locks 12 are provided in US Patent Nos. 6,016,677; 6,094,952; and 6,212,923, the entire disclosures of which are incorporated by reference herein.

[0010] Supplier lOprovides locks 12 to organizations 16 who manage a lock system 18 that includes multiple locks 12, such as a bank, ATM operator, and cash delivery service. As part of their management function, organization 16 may install new locks 12, command locks 12 to perform certain functions, update or reprogram locks 12, send and retrieve information to locks 12, etc.

[0011] To uniquely identify each lock 12, supplier lO provides each lock 12 with a unique identifier, such as a serial number illustrated in Fig. 1 as LI, L2, L3, and L4.

According to the preferred embodiment of the present disclosure, the serial number contains 8 characters.

Similarly, supplier lOprovides each organization's lock system 18 with one or more randomly generated, unique organization identifiers illustrated as ORG 1 and ORG2 in Fig. 1. As discussed in greater detail below, the lock identifier and organization identifiers are used as encryption keys that are then used to initialize new locks 12 to a lock system 18.

[0012] As shown in Fig, 1, supplier 10 has organization management system 20 that includes a computer 22 having a processor 24 and memory that includes a database 26, which may be a single database or multiple linked database stored in a single location or multiple locations. Database 26 stores the unique organization identifiers along with other information, such as the organization associated with each organization identifier. Database 26 may also store the unique lock identifiers along with other information, such as the organization associated with each lock.

[0013] As shown in Fig. 1 , each organization 16 has a lock management system 28 that includes a computer 22 with a processor 24 and memory that includes a database 30, which may be a single database or multiple linked database stored in a single location or multiple locations. Database 30 stores the unique lock identifiers for locks 12 provided to that organization 16 by supplier 10 and the one or more unique organization identifiers provided to that organization 16 by supplier 10 as discussed below. [0014] To communicate the unique organization identifiers to each respective organization 16, supplier 10 saves the organization's unique identifiers on a system key 32 that includes memory to store the unique identifiers. According to the preferred embodiment of the present disclosure, system key 32 is a memory device sold by Maxim Integrated and branded as a Maxim iButton®. Preferably, system key 32 is a disk or button-shaped device that is about the size of a US nickel that has a metal cover housing the memory. Each system key 32 has a unique digital identity or address.

[0015] Supplier 10 stores the unique organization identifiers on a system key 32 and ships this system key 32 to the respective organization 16. Upon receipt, the receiving organization 16 retrieves the unique organization identifiers and stores them into database 30 of their lock management system 28. Storing the unique organization identifiers in the respective database 30 makes this organization's database 30 unique from all other organizations' databases 30. Furthermore, one or more of the unique organization identifiers are required before the software of the respective lock management system 28 will function. For example, upon receipt from system key 32, the software will review one or more of the unique organization identifiers to compare the structure of the unique organization identifiers to expected identifiers structures. If the structure does not match, it will not permit use of the respective lock management system 28.

[0016] To enhance the security of communication between respective locks 12, respective lock management systems 28 and their components, the communication is encrypted. In order to encrypt and decrypt the communications, encryption keys are provided for each lock 12. According to the preferred embodiment of the present disclosure, the encryption keys are generated using one or more of the unique organization identifiers and the unique lock identifier for that lock 12.

[0017] According to the preferred embodiment of the present disclosure, a manager key 34 is used to communicate the encryption keys for a particular lock 12 to that lock 12 as shown in Fig. 2. By providing the encryption keys to a particular lock 12, that lock is initialized to its respective lock management system 28 by permitting it to encrypt and decrypt communications. According to the preferred embodiment of the present disclosure, once a lock 12 is initialized to one lock management system 28, the respective lock 12 cannot be initialized to another lock management system 28. [0018] Manager keys 34 are the same type of memory device as system keys 32. To facilitate the creation of manager keys 34 in locations that are remote from the organization, mobile devices 36, such as smart phones, tablets, laptops, and other such devices, can be utilized. Such devices typically have a battery, memory, software, one or more means of wireless communication through cell-phone systems, other wireless networks, etc., and the ability to communicate directly with manager keys 34.

[0019] In order to create manager keys 34, one or more of the unique organization identifiers is stored in one or more mobile devices 36. To communicate the unique organization identifier to each mobile device 36, one or more of the unique organization identifiers is stored in a initialization key 38. Initialization keys 38 are the same type of memory device as system and manager keys 32, 34. Each respective mobile device 36 retrieves the one or more unique organization identifiers from the respective initialization key 38. According to an alternative method, the unique organization identifiers may be communicated to mobile devices 36 using a wireless network, such as cell-phone network.

[0020] Because the respective mobile device 36 now contains one or more the unique organization identifiers, the mobile device can be used to create manager keys 34 at locations remote from the respective lock management system 28. At the remote location, a lock's unique identifier is received by the respective mobile device 36 by manual entry into the mobile device 36 or otherwise. Having both the respective lock's unique identifier and one or more of the organization's unique organization identifiers, the respective mobile device 36 generates encryption keys for the respective lock 12. These encryption keys are stored on a manager key 34. The respective manager key 34 is then positioned adjacent to the respective lock 12 and the encryption keys are received by and stored in the respective lock 12. By receiving the encryption keys, the respective lock 12 in now able to encrypt and decrypt communications to and from the respective lock management system 28 and the respective lock 12 is then initialized to the lock management system 28. As discussed above, because each lock has a unique identifier and each lock management system 28 has one or more unique organization identifiers, each lock's encryption keys are unique to the respective lock 12.

[0021] As implied above, organization management system 20, lock management system 28, mobile device 36, and lock 12 can communicate directly with any of system keys 32, manager keys 34, and initialization keys 38. For example, as shown in Fig. 3, lock 12 includes a reader/receptor 40 configured to communicate with keys 32, 34, 38. Each of organization management system 20, lock management system 28, and mobile device 36 include or are provide with reader/receptor 40 to communicate with keys 32, 34, 38. As also implied herein, keys 32, 34, 38 are physically moved from reader/receptor 40 to reader/receptor 40 to physically transport the information stored thereon from device to device. The physically transportation may be done through the mail, by a single person, or otherwise from one reader/receptor 40 to another reader/receptor 40.

[0022] In addition to initializing locks 12 to an organization's lock management system 28 by communicating enciyption keys to the respective locks 12, mobile devices 36 can be used to communicate commands to locks 12 via manger keys 34. According to the preferred embodiment of the present disclosure, an operator (or software) at lock management system 28selects one or more functions that they would like a particular lock 12 to perform. For example, the operator may want the respective lock 12 to set its date and/or time, download an audit trail (ex. times and dates when a 12 lock was opened and/or closed, which PIN code was used to operate it, error messages, etc.), setup bank features, reset a tamper function, reset a manager key 34, etc. In response to selecting a command/function, lock management system 28 collects command data necessary to perform the requested command/function. For example, if the operator wants to set the time and date of a lock 12, lock management system 28 collects data indicating which command is to be performed (i.e. setting the time and date), the time being set (ex. 9: 15 AM), the date being set (ex. 19 September 2013), the lock identification (Ex. L I), and a manager key identification (ex. Ml). This command data is then encrypted using the operator's unique identifier and the lock's unique identifier into an operation code.

According to the preferred embodiment of the present disclosure, the operation code is 8- characters long, but it may be other lengths.

[0023] To mask which operations are being performed by the respective lock 12 remotely, lock management system 28 obscures/scrambles the operation code using a predetermined manner. For example, the resulting operation code containing the encrypted operation data may be "Dl 90113 A." This operation code is converted into a transfer code by the respective lock management system 28 by scrambling/obscuring the operation code. For example, the "D" for the date change may be changed to a "4" and moved to the end of the string and the "A" for the audit download changed to a "1 " and moved to the beginning of the string so that a transfer code of "11901134" is created. Additional obscuring/scrambling of the operation code may also be done to further obscure/scramble the operation code resulting in the transfer code. According to one embodiment of the present disclosure, the method of obscuring/scrambling is unique to each lock 12 based on its unique lock identification.

According to the preferred embodiment of the present disclosure, the transfer code is ten characters long, but it may be other lengths.

[0024] As a result of the obscuring/scrambling, the transfer code is generated and displayed to the operator by lock management system 28 on a display (not shown). At a remote location, a user of a mobile device 36 communicates with the operator, preferably over a phone, such as the respective mobile device 36 itself. The operator reads or otherwise communicates the transfer code to the mobile device user who then manually or otherwise enters the transfer code into the respective mobile device 36. Knowing the predetermined method of un-obscuring/unscrambling the transfer code, the respective mobile device 36 recreates the command data so that the command data can be programmed onto the manager key 34, which can be used for the operation code.

[0025] The command data is then transferred to a manager key 34 without displaying the command data to the user. By masking the operation code, it is more difficult or impossible for the mobile device user (or someone watching the mobile device user) to determine which commands are being communicated to the respective lock 12 via a manager key 34.

[0026] As mentioned above, at the remote location, mobile device 36 then

communicates command data to a respective manager key 34. The respective manager key 34 can then communicate the command data to the respective lock 12, which then performs the requested commands.

[0027] As mentioned above, the command data not only includes data indicating which commands are to be performed and the necessary data to perform the function, but also include the unique lock identification. If the respective lock 12 receives command data from a manager key 34 that does not include its own unique lock identification, the respective lock 12 rejects the command data by refusing to act upon the received commands. If the respective lock 12 receives the correct lock identification, it will execute the commands if all other received parameters are correct. For example, if the unique identification (ex. M2) of the respective manager key 34 providing the command data does not match the unique manager key identification (ex. Ml) provided in the command data, the respective lock 12 rejects the command data because it came from an unauthorized manager key 34.

[0028] While this invention has been described as having preferred designs, the present invention can be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this disclosure pertains.