System and method for managing distributed encrypted combination over-locks from a remote location

The disclosure generally relates to a system and method for managing distributed encrypted combination over-locks from a remote location. In an exemplary embodiment, the invention is directed to a distributed management system for self-storage facilities that provide customers with immediate access to an over-locked space upon payment of delinquent past due balances.

BACKGROUND

Field of the Invention

The present invention relates generally to the field of over-lock and release systems for rentable facilities. More particularly, the invention is a distributed management system for self-storage facilities that provide customers with immediate access to an over-locked space upon payment of delinquent past due balances.

Description of Related Art

Self-storage units are typically rented on a monthly basis. If a customer is delinquent, and does not pay their rent to the self-storage facility owner by an agreed-upon due date, the owner (i.e., landlord) has a right to prevent the customer from accessing the storage space. Self-storage facility owners typically place an over-lock over the storage space door, such as through a hasp that prevents opening of the door. The over-lock is utilized until the customer pays the delinquent past due balance on their account.

The process of placing, and removing over-locks, can be quite burdensome on a self-storage facility owner, especially with large facilities with hundreds of storage units, the majority of which may be rented to month-to-month customers. After an over-lock is placed on a storage space, the over-lock must ultimately be removed once the customer account becomes non-delinquent. Removing over-locks is time-consuming and costly because it requires personnel from the self-storage facility to physically go to the storage space and remove the over-lock.

In addition, the cost of conventional over-locks can be prohibitive. Many conventional over-locks are electronic and provide automated and remote locking/unlocking functions. Such over-locks oftentimes require significant capital improvements on the storage structures, as these over-locks must be installed behind the storage door on the interior of the space. Furthermore, these electronic locks inherently require constant power, and their continuous twenty-four hour operation increases power consumption costs for the self-storage facility.

Furthermore, as with any complex electronic device, electronic over-locks are subject to failure and malfunction, and can require costly repairs to be conducted by an electrician, if not ultimately requiring replacement.

Other conventional over-locks include standard combination locks. However, with a self-storage facility utilizing a limited number of standard combination over-locks, habitually delinquent customers eventually begin to recognize the unlock codes, and these over-locks become futile. The self-storage facility must then perpetually replace over-locks with unlock codes that have become known and compromised.

Another disadvantage of standard combination over-locks is the potential for delayed access to the customer. If the customer makes a payment and brings their account current when the self-storage management office is closed or when personnel are unavailable, such as on weekends, after-hours, or holidays, the customer must then wait until the office is open and there are personnel available to remove the over-lock. Thus, the customer cannot gain access to their storage space and possessions immediately after making payment to bring their account current. The delay between such a payment and removal of the over-lock does not cater to tenants who may need immediate access to their storage space.

Thus, there is a need in the self-storage industry for a system that allows or disallows access to an over-locked storage unit without the need for an on-site attendant. Such a distributed over-lock system would allow for immediate access to an over-locked storage space, would encourage delinquent customers to bring an account current in a timely fashion, and would reduce operational costs associated with conventional electronic and standard combination over-lock systems.

SUMMARY

In one embodiment, the disclosure relates to a system for retrieving a decrypted unlock code for a physical lock from a remote server, the system comprising: a database stored at the remote server, wherein the database is configured to store an identifier and an encrypted unlock code, where the identifier is associated with an encrypted unlock code; a mobile device communicatively coupled to the database via a network, wherein the mobile device is configured to receive the identifier as an input from a user, and wherein the mobile device is further configured to transmit the identifier to the database via the network; a processor coupled to the database, wherein the processor is configured to receive the identifier from the mobile device, and further configured to generate the decrypted unlock code by performing a decryption operation on the encrypted unlock code, wherein the decryption operation uses the identifier as an input; and a transceiver coupled to the database, wherein the transceiver is configured to transmit the decrypted unlock code to the mobile device.

In another embodiment, the disclosure relates to a system for retrieving an unlock code for a combination lock, the system comprising: a mobile device communicatively coupled to a server, wherein the mobile device includes an interface configured to receive an identifier as an input, the mobile device further configured to transmit the identifier to the server; a database communicatively coupled to the server; a processor coupled to the database, the processor configured to retrieve an unlock code associated with the identifier, wherein the identifier and the unlock code have previously been associated using an encryption methodology; and a transceiver coupled to the processor, the transceiver configured to transmit the unlock code to mobile device via the server, wherein the mobile device is configured to display the unlock code on the interface.

In still another embodiment, the disclosure relates to a method for retrieving an unlock code for a combination overlock from a remote server, the method comprising: receiving an identifier associated with the combination overlock on an interface for a software application stored on a mobile device; receiving a user credential on the interface; transmitting the identifier and the user credential from the mobile device to the remote server; receiving the identifier and the user credential at a processor at the remote server; verifying, by the processor, the user credential; determining, once the user credential is verified, if an account associated with the user credential has a delinquent status by the processor, retrieving, if the account has a delinquent status, an unlock code associated with the identifier by the processor, wherein the retrieving step includes decrypting the unlock code using the identifier as an input; transmitting the unlock code by the remote server to the mobile device; and displaying the unlock code on the interface for the software application on the mobile device.

DETAILED DESCRIPTION

It should be understood that aspects of the invention are described herein with reference to the figures, which show illustrative embodiments. The illustrative embodiments herein are not necessarily intended to show all embodiments in accordance with the invention, but rather are used to describe a few illustrative embodiments. Thus, aspects of the invention are not intended to be construed narrowly in view of the illustrative embodiments. In addition, the present invention is an over-lock and release system. Although the system is described with respect to its application for self-storage facilities, it is understood that the system could be implemented in any setting where an over-lock system may be useful.

FIG. 1is a network architecture diagram of a distributed encrypted combination over-lock and release system. In an embodiment, the system can be implemented within a self-storage environment. The system includes a self-storage facility102coupled to a management site118via a network116. The management site118can be remote from the self-storage facility102, and the management site118can serve multiple distributed self-storage facilities, such as in a central management site. The management site118can further be located overseas, such as in a foreign call center.

In an embodiment, the management site118includes computing hardware and software119, consisting of a processing unit120, a database122, and a transceiver124. The computing hardware and software119can include a server coupled to the network116. In another embodiment, the processing unit120and database122can be cloud-based, and located on a server remote from the management site118, such as on a server provided by Amazon Web Services® or the like.

In another embodiment, the management site118can be located within the local vicinity of the self-storage facility102, such as on-site. The management site118can be a physical location with human personnel, such as a self-storage manager108. In another embodiment, the management site118can be unmanned, and can include only the computing hardware and software119. The network116may be any type of network suitable to allow interaction between devices, such as a mobile device112located at self-storage facility102, and the computing hardware and software119at the management site118. For example, the network116may be a wired network, a wireless network, or any combination thereof. Further, the network116may include a distributed computing network, an intranet, a local-area network (LAN) and/or a wide-area network (WAN), or any combination thereof. For example, the LAN may make use of WIFI in its many variations and the WAN may make use of broadband, cellular and/or satellite networks using technologies including, but not limited to, CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, Mobitex, EDGE and other 2G, 3G, 4G and LTE technologies. However, those of ordinary skill in the art will appreciate that the network116is not limited thereto.

The self-storage facility102can include a storage space104, which can be rented by a customer106. As used herein, the term “customer” can include a renter, client, tenant, lessee, user, or an authorized agent. Although the invention will be described with respect to self-storage facilities, the invention can be implemented in any setting where an over-lock system may be useful, such as hotel rooms, apartment buildings, storage containers, short-term housing rentals, and lockers. In addition, the invention can be implemented within a controlled access system, such as for equipment rooms, vaults, hospitals, airports, government facilities, nuclear power facilities, water treatment facilities, weapon storage facilities, aircraft cockpits, and any other setting that requires restricted, selective, or monitored access.

In the event that customer106becomes delinquent in the payment of rent, the self-storage manager108can place an over-lock110on the storage space104. The over-lock110is a secondary lock that is used to prevent the customer106from accessing the storage space104until the delinquent past due balance is paid by customer106.

In a preferred embodiment, the over-lock110is a combination padlock that requires an unlock code to be manually entered in order to open the over-lock110. In another embodiment, the over-lock110can be deadbolt, knob lock, or lever lock that includes a combination mechanism. The combination mechanism can include a tubular barrel, a rotary knob, pushpins, or a mechanical keypad. In another embodiment, the over-lock110can be an electronic lock that accepts a combination input via digital keys or a touchscreen.

In an embodiment, the over-lock110can include an identifier, such as a serial number, unique code, barcode, QR code, or other unique indicia. In an embodiment, the identifier is engraved onto the over-lock110. In other embodiments, the identifier is affixed via a label to the over-lock110, affixed to a tag that is attached to the over-lock110, or otherwise imprinted, drawn, or engraved on the over-lock110or tag.

Upon payment of a delinquent past due balance by the customer106, the management site118can enable the release of an unlock code for the over-lock110. At this time, the customer106can use a mobile device112, such as their mobile phone, to access a software application114created by the self-storage manager108. The software application114can be a proprietary program created and/or owned by the self-storage facility102, and which can be downloaded by the customer106from, for example, a website operated by the self-storage manager108, the Apple iTunes App Store®, the Android App Store®, and the like.

In yet another embodiment, the software application114is a website accessed via a Uniform Resource Locator (URL) using a browser on the mobile device112.

The mobile device112is not limited to a mobile phone, and can include tablets, wearable devices, personal digital assistants (PDAs), laptop computers, “smart” watches, “smart” glasses, and any other device capable of receiving input from the customer106, and which is capable of being connected to the network116.

The software application114includes an interface that allows the customer106to enter the identifier. The identifier is then transmitted from the mobile device112via a network116to the management site118. The identifier is received by the transceiver124, and routed to the processing unit120. The processing unit120performs a decryption and/or look-up operation in the database122, and retrieves an unlock code for the over-lock110that is associated with the identifier. The unlock code is then transmitted by the transceiver124to the mobile device112via the network116. The unlock code is subsequently displayed to the customer106on the mobile device112via the software application114. Upon receiving the displayed unlock code, the customer106can then unlock the over-lock110, and re-gain access to the storage space104.

FIG. 2is a flowchart illustrating the steps of encrypting an unlock code for a combination over-lock. In step200, a unique identifier is generated for the over-lock110. The identifier can be generated at the time of manufacturing by the over-lock manufacturer, and can be transmitted with the over-lock110at the time of purchase by the self-storage facility. In this embodiment, the identifier can be engraved or permanently affixed to the over-lock110.

In another embodiment, the identifier is generated by the self-storage facility. In this embodiment, an algorithm on the processing unit120randomly generates the identifier, or it can be generated manually by the self-storage facility. In another embodiment, a third-party over-lock provider can generate the identifier, and can sell or lease the over-locks to a self-storage facility. The third-party over-lock provider can manage the computing hardware and software119for the self-storage facility, and/or can lease the computing hardware and software119to the self-storage facility.

In an embodiment, the identifier can be generated using an encryption technique that utilizes the unlock code as an input. In addition, another identifying input can be utilized for the encryption along with the unlock code, such as a self-storage facility identifier, federal tax identification number, or a randomly generated string of characters.

In an embodiment, the identifier can be a string of numeric characters, alphabet characters, special characters, or a combination of alphanumeric and/or characters. In addition, the identifier can include a portion identifying the self-storage manager108, the self-storage facility102, and/or the customer106.

In an embodiment where the identifier is a barcode, matrix code, a QR code, or a similar scannable code, the identifier can be printed on the over-lock110at the time of manufacture, or alternatively, the identifier can be printed on label and affixed to the over-lock110or a tag attached to the over-lock110by either the manufacturer or the self-storage facility.

In another embodiment, the over-lock110or tag can have a digitally imprinted code and/or microchip, such as a RFID or Bluetooth low energy transmitter. The customer106can be provided with a physical key fob that can read the code sent from the microchip, and which can display the code to the user. The key fob can be implemented into a software application on the mobile device112as well. In this embodiment, the identifier is not readily visible, which adds a layer of security against the over-lock110, and its corresponding unlock code, becoming known over a period of time due to re-use.

In step202, the unlock code is generated for the combination over-lock110. Again, the unlock code can be generated at the time of manufacturing by the over-lock manufacturer, and transmitted with the over-lock110at the time of purchase by the self-storage facility.

In another embodiment, the self-storage facility can generate the unlock code for the over-lock110. The unlock code can be randomly generated by an algorithm on the processing unit120, or generated manually by the self-storage manager108.

In an embodiment, the identifier and/or unlock code can be time-limited, and can expire after a pre-determined amount of time or on a certain date. In this embodiment, the expired identifier and/or unlock code must be re-generated as per step200and202above.

In an embodiment, the unlock code can be generated using an encryption technique that utilizes the identifier as an input. In addition, another identifying input can be utilized for the encryption along with the identifier, such as a self-storage facility identifier, federal tax identification number, or a randomly generated string of characters.

In step204, the processing unit120associates the identifier with the unlock code for the over-lock110using an encryption technique. The encryption technique can include at least one of a hash function, a key derivation function, a block cipher operation, and an obfuscation function. In addition, the encryption algorithm used by the processing unit120can include a Triple Data Encryption Standard (DES) algorithm, a RSA cryptosystem algorithm, a Blowfish cipher algorithm, a Twofish cipher algorithm, or an Advanced Encryption Standard (AES) algorithm.

In step206, the encrypted identifier and unlock code pair is stored in the database122. The database122can be stored locally at the management site118, can be located on a remote cloud-based server, or at another facility remote from the management site118.

In yet another embodiment, each storage space104can include a scannable code, such as a barcode, located on a visible portion of its exterior. Each over-lock110can also include a barcode as its identifier, as described above. Upon applying the over-lock to a storage space104, the self-storage manager108can scan both barcodes. These barcodes are then transmitted to the processing unit120, where the barcode pairs are associated with each other and stored in the database120.

FIG. 3is a flowchart illustrating the steps of decrypting an unlock code for a combination over-lock. In step300, upon encountering an over-lock110on their storage space104, the customer106locates the identifier on the over-lock110. The customer106can enter the identifier into a software application114on their mobile device112, as described above. In an embodiment, the customer106can take a picture of the identifier and send it via text, SMS, MMS, email, or secure message through the software application. to the management site118. In another embodiment, the customer106can initiate a live-stream or video chat of the identifier with the management site118, using, for example, Apple FaceTime®, Skype®, Snapchat®, or the like. In another embodiment, the identifier can be entered through a website accessed via a URL using a browser on the mobile device112.

In another embodiment, the customer106can scan a barcode, matrix code, a QR code, or a similar scannable code with a camera or optical pickup means on the mobile device112. The scanned identifier is then transmitted to the management site118.

In yet another embodiment, the customer106can place a telephone call to the remote management site106and/or the self-storage manager108and provide the identifier and/or their credentials verbally.

In an embodiment, prior to being able to access the software application114, the customer106must enter credentials, such as a login and password, or other indicia that verifies the customer's identity. The credentials may also be supplied via biometric means, such as with fingerprint, iris, voice, face, and gesture recognition means incorporated into the mobile device112and/or software application114. In another embodiment, the credential can include a one-time or limited use password provided by a secure token, such as a RSA SecurID®.

In another embodiment, the credentials may be transmitted along with the identifier. In this embodiment, the credentials can include the customer's mobile device number, account number, personal identification number (PIN), name, driver's license number, social security number, birthdate, storage unit number, a unique account identification previously provided to the customer106by the self-storage facility and/or any combination thereof.

In yet another embodiment, the customer106can designate authorized parties who can request the unlock code as well. For example, a customer's spouse, authorized agents, business associates, attorneys, and any other parties whom the customer106wishes to have access to the storage space104can have their credentials associated with the storage space. In this embodiment, the database record for the storage space104and/or over-lock110includes a listing of all authorized parties and their respective credentials.

In step302, the identifier, along with the credentials, if required, are transmitted to the management site118via the network116. In an embodiment, the identifier is specifically transmitted to the computing hardware and software119, which can be located at the management site118, or alternatively, located at a remote facility or server communicatively coupled to the management site118.

As described above, the management site118and/or processing unit120can be located remotely from the self-storage facility102, and thus, the network116can include a WAN and utilize broadband, cellular, and/or satellite communication means. In another embodiment, the processing unit120can be located on-site at the self-storage facility102. In this embodiment, in addition to the aforementioned communication means, the mobile device112can utilize a short-range communication protocol, such as Bluetooth®, infrared, ZigBee®, and/or optical wireless, to communicate with the computing hardware and software119.

In step304, the processing unit120receives the identifier. The processing unit120uses the identifier as an input to decrypt the unlock code. Various decryption techniques may be employed, and such techniques can include the use of private and public keys. In another embodiment, the decryption step involves performing a look-up operation in the database120to locate the over-lock record associated with the identifier. Once the relevant record is located, the processing unit120extracts the unlock code from the over-lock record. The look-up operation can be standalone, or in addition to the decryption techniques described herein.

In another embodiment, the unlock code and identifier can both be randomly generated, either using an algorithm on a computing device, or manually. The randomly generated unlock code and identifier can then be linked or associated with one another in a database, table, matrix, ledger, or the like. The linking/associating can be done using an algorithm on the computing device, or can be done manually.

In step306, the unlock code is transmitted to the mobile device114via the network116using a transceiver124coupled to the processor120. Upon receipt by the mobile device112, the software application114displays the unlock code to the customer106. In yet another embodiment, the unlock code can be transmitted to the mobile device112from the management site118via SMS, MMS, email, or video chat. In yet another embodiment, the self-storage facility can place a telephone call to the customer106and verbally provide the unlock code. In this embodiment, human personnel, such as the self-storage manager108at the management site118, can place via an automated system or the telephone call.

FIG. 4Ais a perspective illustration of a combination over-lock according to an embodiment of the invention. The combination over-lock110includes an identifier400, which can be engraved or otherwise permanently affixed to the over-lock110. In another embodiment, the identifier400can be on a label affixed to the over-lock110, such as an adhesive label. The identifier400can be located on an underside of the over-lock110, as shown inFIG. 4A, or can be located on the front-face, rear plate, or shackle.

FIG. 4Bis a perspective illustration of a combination over-lock with an identifier tag according to an embodiment of the invention. In this embodiment, the identifier400is located on a tag402that is affixed to the over-lock110. The tag402can be affixed to the shackle, the combination knob, or alternatively, can be applied partially via adhesive to any surface of the over-lock. The tag402can be placed within a weatherproof encasement (not shown).

FIG. 4Cis a perspective illustration of a combination over-lock with a barrel tumbler according to an embodiment of the invention. In this embodiment, the identifier400is a scannable code, such as a barcode, and is located on the front or rear surface of the over-lock110. The unlock code can be manually entered using the barrel tumbler406on the underside of the over-lock110. The over-lock110depicted inFIG. 4Cis shown as an example, and various designs of locks having a barrel tumbler, a rotary knob, push-pins, or a mechanical keypad can be utilized with this invention, such as combination input mechanism can also be located on a side or front face of the over-lock110.

FIG. 4Dis a perspective illustration of an electronic over-lock with an interface according to an embodiment of the invention. In this embodiment, the over-lock110includes an interface, such as a touch-screen408. The identifier400can be located on the casing410or shackle412, or affixed to the over-lock110via a tag (not shown) similar to the embodiments shown inFIGS. 4A-4C. In another embodiment, the identifier400can be displayed on the touch-screen408. The electronic over-lock110can function similarly to the mobile device114, and can include circuitry for accepting customer input and for transmitting and receiving data from a remote source. In this embodiment, the customer106can access the software application116via the touch-screen408, and can enter their credentials and the identifier. The electronic over-lock110can then transmit the identifier to the management site118. Upon a successful decryption at the management site118, the unlock code is transmitted to the over-lock110, which is automatically unlocked without further customer intervention.

FIG. 5is a diagram of a kiosk and storage space according to an embodiment of the invention. In another embodiment, the storage space104can include a kiosk500, either adjacent to the storage space104, or located at the self-storage facility102. The kiosk500can function similar to the mobile device114, and allow the customer106to request an unlock code. The kiosk500can accept an identifier from the over-lock110, and can then transmit the identifier to the management site118. Upon a successful decryption at the management site118, the unlock code is transmitted for display at the kiosk500. The kiosk500can also perform other services and management functions for the self-storage facility102, such as accepting payments, processing storage space rentals, providing voice and chat operations with the self-storage manager108and/or management site118, and vending accessories.

In another embodiment, the customer106can utilize the kiosk500to request an unlock code, and the unlock code is returned for display to the mobile device112, or vice-versa.

FIG. 6Ais an illustration of an over-lock release interface for a software application according to an embodiment of the invention. The unlock interface600can be displayed on the mobile device112once the customer106activates the software application114. The unlock interface600allows the customer106to enter an identifier for the over-lock110at input box602. The unlock interface600can also display information604such as the customer name and facility name, and customer status606. The customer status606can be either “current” (i.e., paid in full and in good standing), or “delinquent” (i.e., having a past due balance). In an embodiment, the customer status606can include be “pending”, indicating that a payment has been submitted, but not yet processed, such as in the case of wire transfers or digital currency payments which typically require a delay in settlement.

In an embodiment, the unlock code606is displayed after the customer106transmits the identifier by selecting the “SUBMIT” button610, and after the processing unit120successfully decrypts the unlock code.

In another embodiment, the interface600does not include the unlock code606, and the unlock code is transmitted to the customer106via a text, SMS, MMS, email, video chat, secure message via the software application, or telephone call.

FIG. 6Bis an illustration of an over-lock release interface for a software application according to an embodiment of the invention. In the event that the customer106has not made payment on a delinquent past due balance, and still attempts to retrieve the unlock code, the customer status606will be listed as “Delinquent”. In addition, the “SUBMIT” button610will be greyed our or inactive, so that the customer106cannot submit the identifier. In another embodiment, the customer106may not even reach the unlock interface600, and rather, is directed toward a billing webpage upon launching the software application114, where they can make a payment to rectify their delinquent account (not shown).

FIG. 7is a flow chat illustrating the steps of enabling and disabling an over-lock according to the embodiment of the invention. In step700, the management site118determines if a customer account is delinquent. If the account is current and there is no outstanding past due balance, the process terminates at step702and no over-lock110is required. The process continues back to step700where the customer account is continually monitored for delinquency by the management site118.

If the customer account is delinquent, the process continues to step704, where an over-lock110is placed on the storage space104. The over-lock110, in a preferred embodiment, is manually placed over the primary lock or latch, thereby preventing movement of the door hasp, even if the primary lock is removed.

In another embodiment, the customer106can have multiple storage spaces on their account. If the customer106is delinquent on all or part of their account, all of the storage spaces on the customer's account can be over-locked. In another embodiment, only select storage spaces or a single storage space can be over-locked, based on the amount or extent of delinquency on the account.

In step706, the processing unit120determines if the customer account is still delinquent. If the account is still delinquent, the processing unit120disables the over-lock release function. In this scenario, the processing unit120prevents the over-lock release interface shown inFIG. 6Bfrom returning an unlock code. In another embodiment, if the customer106attempts to request an unlock code via text message, email, video chat, or telephone call while having a delinquent past due account status, the customer106will be informed by the self-storage facility that their account is delinquent, and they cannot retrieve the unlock code.

If the customer's account is no longer delinquent in step706, then the process continues to step710, where the over-lock release is enabled by the processing unit120, and the customer106can retrieve the unlock code in step712. The process continues back to step700where the customer account is continually monitored either by the self-storage facility.

FIG. 8is a flowchart illustrating the steps taken by a customer to retrieve an unlock code using the software application according to an embodiment of the invention. In step800, the customer106discovers that their storage space104has been over-locked.

In step802, the customer106follows instructions on a notice from the self-storage facility to access the software application114in order to retrieve an unlock code for the over-lock110. In an embodiment, a notice, such as a hangtag, placard, sign, or other indica is placed on the over-lock110, adjacent to the overlock110, and/or on a door or frame of the storage space. The notice can include instructions on how to access the software application114. As discussed earlier, the software application114can be downloaded by the customer106from, for example, a website operated by the self-storage manager108, the Apple iTunes App Store®, the Android App Store®, and the like, or the software application114can be a website accessed via a URL using a browser on the mobile device112.

In an embodiment, the notice can instruct the user to launch the software application114on their mobile device112, can instruct the user to visit a URL using a browser on their mobile device112, and/or can include a scannable code which automatically launches the software application114or a URL on the mobile112. In another embodiment, the notice can instruct the user to place a telephone call or send a message, such as a SMS, MMS, or email, to the self-storage facility.

In another embodiment, the notice can be sent directly to the customer106, such as via text, SMS, MMS, email, or secure message through the software application. The notice can include a URL or other mechanism to launch the software application114on the mobile device112. In addition, the notice can be mailed via physical mail to the customer's address on file.

In yet another embodiment, the notice can be a telephone call from the management site118, instructing the customer106to access the software application114.

In step804, the customer106is prompted to enter their credentials, such as a login and password, or other indicia that verifies the customer's identity. The credentials may also be supplied via biometric means, such as with fingerprint, iris, voice, face, and gesture recognition means incorporated into the mobile device112and/or software application114. In another embodiment, the credential can include a one-time or limited use password provided by a secure token, such as a RSA SecurID®.

In step806, the management site118determines if the credentials are valid. If not, the process returns to step804, and the customer106is prompted to re-enter their credentials. If the credentials are deemed valid, then in step808, the management site118determines if the customer's account is indeed delinquent. If the customer106no longer has a past due balance, then the customer106is prompted to enter the identifier from the over-lock110in step810. This scenario may occur, for example, if a customer106makes a payment to rectify a past due balance from a remote location, such as their home or work, and then subsequently arrives at the self-storage facility to discover a previously placed over-lock110.

If the customer106still has a past due balance, then the customer106is prompted to pay their past due balance in step812. In an embodiment, the customer106can make payments to the self-storage facility via a credit card, debit card, automated clearing house (ACH) transfer, and wire transfer. The software application114may allow the user to store a payment method on file, such as a stored credit card, or a linked bank account.

In addition, the self-storage facility can accept payment via third-party payment processing systems, such as PayPal®, Stripe®, Apple Pay®, Android Pay®, Square®, Amazon Payments®, Viewpost®, and other similar platforms. Such payment processing systems can be integrated within the software application114.

In yet another embodiment, the self-storage facility can accept payment via cryptographic and digital currencies, such as, but not limited to Bitcoin, Ethereum, Litecoin, and Nano.

In another embodiment, the customer106can visit the manager self-storage and/or the remote management site118and pay the past due balance in-person.

The process then returns to step808, where the management site118determines if the customer106still has a past due balance on their account. If there is no past due balance, then the customer106is prompted to enter the identifier from the over-lock110in step810. If the customer106still has a past due balance, then the process returns to step812where the customer106is prompted to pay their past due balance.

In step814, the management site118transmits the unlock code to the customer106, who can then remove the over-lock110from their storage space104.

FIG. 9is a flowchart illustrating the steps taken by a customer to retrieve an unlock code via a telephone call according to an embodiment of the invention. In step900, the customer106discovers that their storage space104has been over-locked.

In step902, the customer106follows instructions on a notice from the self-storage facility to call the management site118in order to retrieve an unlock code for the over-lock110. In an embodiment, the management site118can include a self-storage manager108, call center, representative, or third-party answering service. In another embodiment, the customer106can send a message to the management site118, such as via text, SMS, MMS, email, or secure message through the software application in order to schedule a call from the management site118.

In step904, the management site118requests the customer106to provide credentials, as described above.

In step906, the management site118determines if the credentials are valid. If not, the process returns to step904and the management site118requests the customer106to provide their credentials again. If the credentials are deemed valid, then in step908, the management site118determines if the customer's account is indeed delinquent. If the customer106no longer has a past due balance, then the customer106is prompted to enter the identifier from the over-lock110in step910. The customer106can verbally provide the identifier, enter the identifier via their alpha-numeric keypad on their mobile device112, or scan the identifier and transmit it to the management site118using their mobile device112.

If the customer106still has a past due balance, then the customer106is prompted to pay their past due balance in step912.

The process then returns to step908, where the management site118determines if the customer106still has a past due balance on their account. If there is no past due balance, then the customer106is prompted to provide the identifier from the over-lock110in step910. If the customer106still has a past due balance, then the process returns to step912where the customer106is prompted to pay their past due balance.

In step914, the management site118provides the unlock code to the customer106, who can then remove the over-lock110from their storage space104.

In an embodiment, the over-lock110can include an emergency mode, where emergency personnel, such as first responders, police, firefighters, and emergency medical service providers and request an unlock code. In this embodiment, the emergency personnel can transmit an emergency credential along with the identifier. Upon receipt of the emergency credential by the management site118, the processing unit120foregoes credential verification and proceeds with decrypting the unlock code.

In yet another embodiment, the over-lock110is an electronic lock that accepts a combination input via digital keys or a touchscreen. The customer106can be provided with a secure token that provides a one-time or limited use password, such as the RSA SecurID®. In the event of a delinquent past due balance, the management site118can remotely disable the secure token until the customer106makes a payment of the past due balance.

In another embodiment, the entire process of retrieving an unlock code by the customer106can be automated. For example, the management site118can include an automated attendant that verifies the identity of the customer106via the means described above, receives the identifier from the customer106, and provides the unlock code to the customer106. The process can also occur in an automated fashion without human intervention from the self-storage facility or management site118via the kiosk500.

While the principles of the disclosure have been illustrated in relation to the exemplary embodiments shown herein, the principles of the disclosure are not limited thereto and include any modification, variation or permutation thereof.