WO2017087697A1

WO2017087697A1 - Modular storage devices, systems, and related methods

Info

Publication number: WO2017087697A1
Application number: PCT/US2016/062570
Authority: WO
Inventors: Bradley Burr MCLAWS
Original assignee: Boxspace Inc
Current assignee: Boxspace Inc
Priority date: 2015-11-20
Filing date: 2016-11-17
Publication date: 2017-05-26
Anticipated expiration: 2018-05-20

Abstract

Embodiments disclosed herein are directed to devices, systems, and methods for storing various items. For example, the system may include a locker access location and smart lockers that may secure one or more storage boxes.

Description

MODULAR STORAGE DEVICES, SYSTEMS, AND RELATED METHODS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No.

62/258,246 filed on 20 November 2015, the disclosure of which is incorporated herein, in its entirety, by this reference.

BACKGROUND

[0002] Individuals and/or businesses may have various items that may be stored off-site and may require or desire off-site storage for such items. For example, an individual may have limited space at home and may store some items (e.g., items not used on daily basis) at an off-site location, such that the stored items may be retrieved on as- needed basis but will not occupy limited space at the home of the individual.

[0003] Therefore, storage providers and users continue to seek improvements to storage devices, systems, and methods.

SUMMARY

[0004] Embodiments disclosed herein are directed to devices, systems, and methods for storing various items. For example, a system may include a locker access location and smart lockers that may secure one or more storage boxes. Specifically, for example, the system may include multiple identifiable storage lockers that may be located in the locker access location (e.g., in a building). In some embodiments, the storage lockers may be lockable and may be identified within the system, such that a storage box may be placed inside a storage locker and may be locked therein, and the system may correlate the storage box with the storage locker. For example, a user may place one or more storage boxes into a single or into multiple storage lockers, and the storage boxes may be stored by the system. The user may retrieve one or more storage boxes (e.g., boxes previously placed in storage) from a single storage locker or from multiple corresponding lockers.

[0005] Features from any of the disclosed embodiments may be used in combination with one another, without limitation. In addition, other features and advantages of the present disclosure will become apparent to those of ordinary skill in the art through consideration of the following detailed description and the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The drawings illustrate several embodiments, wherein identical reference numerals refer to identical or similar elements or features in different views or embodiments shown in the drawings.

[0007] FIGS. 1A and IB are schematic illustrations of a locker access location and storage lockers therein, according to an embodiment;

[0008] FIG. 1C is a schematic illustration of a locker access location according to another embodiment;

[0009] FIGS. 2A-2C are schematic illustrations of bulk storage facilities, according to one or more embodiments;

[0010] FIG. 3 is a schematic illustration of a user interface on a personal electronic device, according to an embodiment;

[0011] FIGS, 4A-4E are schematic illustrations of a user interface on a personal electronic device, according to another embodiment.

DETAILED DESCRIPTION

[0012] Embodiments disclosed herein are directed to devices, systems, and methods for storing various items. For example, a system may include a locker access location and smart lockers that may secure one or more storage boxes. Specifically, for example, the system may include multiple identifiable storage lockers that may be located in the locker access location (e.g., in a building). In some embodiments, the storage lockers may be lockable and may be identified within the system, such that a storage box may be placed inside a storage locker and may be locked therein, and the system may correlate the storage box with the storage locker. For example, a user may place one or more storage boxes into a single or into multiple storage lockers, and the storage boxes may be stored by the system. The user may retrieve one or more storage boxes (e.g., boxes previously placed in storage) from a single storage locker or from multiple corresponding lockers.

[0013] In an embodiment, storage boxes placed into the storage locker(s) may be removed therefrom by a third party (i.e., someone other than the user who placed the storage boxes inside the storage lockers) and may be transported to another location for storage. For example, the system may notify a storage operator and/or a person responsible for transporting the storage boxes to remove the boxes from the storage lockers located at the locker access location and/or to relocate the storage boxes to a bulk storage facility (e.g., the bulk storage facility may be a storage warehouse, as describe below in more detail). As such, for example, a single bulk storage facility may receive and store storage boxes from multiple locker access locations (e.g., the locker access locations may be located at various suitable locations, such as malls, strip malls, shopping centers, business centers, business buildings, apartment complexes, etc., and the bulk storage facility or facilities may be located at industrial locations, such as warehouse developments and the like).

[0014] In some embodiments, the system may receive a retrieval request from a user, indicating that the user requests retrieval of the storage box(es) from a bulk storage location and access to the storage box(es) from the storage locker(s) located at a locker access location. For example, the retrieval request may indicate the items a user requests to retrieve, may indicate one or more specific storage boxes (e.g., which may be identified by a number or one or more additional or alternative identifiers), may indicate a location of the locker access location, combinations of the foregoing, etc. In response to the retrieval request, the system may generate an alert or a notification to a storage operator, to a person responsible for delivery of the storage box(es) to storage locker(s) at a requested locker access location, to a robot or a manipulator configured to remove and/or relocate storage boxes at the bulk storage facility, etc. Hence, for example, a user may place one or more storage boxes into storage at a locker access location, the storage boxes may be relocated from the locker access location to a bulk storage facility (e.g., to reduce storage cost and/or make room for more storage), the user may submit a retrieval request to retrieve the storage box(es), and the storage box(es) may be delivered to a locker access location selected by the user and may be retrieved therefrom (e.g., the system may notify the user that one, some, or all of the requested storage box(es) are ready for retrieval from the locker access location). In one or more embodiments, as described below in more detail, the system may include a controller that may be configured to control location of the storage box(es) based at least partially on input received from user (e.g., based at least partially on a request to retrieve the storage box, which may be received at the controller from user).

[0015] FIGS. 1A and IB are schematic illustrations of a locker access location

100, according to an embodiment. For example, the locker access location 100 includes multiple storage lockers 110 that may be identified and/or controlled by a controller (e.g., locked, unlocked, opened, closed, combinations of the foregoing, etc.), as described below in more detail. In some embodiments, the locker access location 100 includes private rooms 120, where a user may place items into a storage box and/or remove items from the storage box. One, some, or each of the storage lockers 110 may be sized and configured to accept a storage box 130. For example, after the storage box 130 is placed into a storage locker, the controller may operate to direct closing of the locker and secure the storage box 130 therein. In some embodiments, the storage box 130 may include one or more locks or locking mechanisms that may lock the storage boxes 130 and secure the contents therein.

[0016] Generally, the storage lockers 110 may have any suitable size and/or one, some, or each of the storage lockers 110 may be sized and configured to store a single storage box 130 or multiple storage boxes 130. For example, one, some, or each of the storage lockers 110 may be a generally rectangular prismoid and may be sized to receive a single storage box 130 that has a rectangular or square cross-sectional shape.

Additionally or alternatively, one, some, or each of the storage lockers 110 may be room- sized and/or may be sized, shaped, and otherwise configured to receive multiple storage boxes 130 and/or larger storage boxes or storage items (e.g., bicycles as shown in FIG.

1C) .

[0017] In at least one embodiment, the locker access location 100 may include privately accessibly storage lockers. For example, one or more secure storage lockers 110a may be located in a secured storage area 101, while additional storage lockers 110 may be located in an open storage area 102 of the locker access location 100. For example, only authorized users may access the secured storage area 101 (e.g., by supplying access credentials to a controller, such as by entering an access code at a control panel, at a personal electronic device, using a key, etc.).

[0018] As described above, the storage box 130 may be positioned and locked inside a storage locker (e.g., a single storage locker may be configured to secure a single storage box 130). Generally, the storage boxes 130 may have any suitable size and shape. For example, a storage box 130 may have internal space of about three to four cubic feet (e.g., the box may be 17 inches x 27 inches x 15 inches (width x length x depth)). In any event, the storage box 130 may be placed inside one of the storage lockers 110 and may be locked therein.

[0019] In an embodiment, any of the storage lockers 110 may be automatically locked when the user closes the door of the locker. Alternatively, the system may lock the locker after receiving a corresponding indication from the user. For example, the storage lockers 110 and/or secure storage lockers 110a may be operably connected to the controller (e.g., such that the controller may control and/or direct opening, closing, locking, unlocking, or combinations thereof for the storage lockers 110 and/or secure storage lockers 110a). Furthermore, in some embodiments, the storage lockers 110 and/or secure storage lockers 110a may include a controller input interface 111 that may be operably coupled to the controller and may receive control inputs or requests from the user. In some embodiments, the controller input interface 111 may have a touch interface. Additionally or alternatively, the controller may receive one or more signals from a personal electronic device (e.g., a smart phone), which may indicate or correspond to a request to open one or more of the storage lockers 110. In any event, the user may request opening and/or closing of one or more of the storage lockers 110 at the controller input interface 111 and/or from personal electronic device.

[0020] The system and/or the controller thereof may also monitor (e.g., based on signals received from one or more sensors) and/or identify the specific storage boxes 130 or some aspect about the storage box 130 located in the corresponding storage lockers 110. Moreover, the controller may correlate one or more of the storage boxes 130 with corresponding user accounts and/or user names. For example, the controller may include a database (e.g., the database may store and/or organize data in a storage memory of the controller (described below in more detail)) where the controller may store information about users, including user accounts (e.g., user contact information, user billing information, etc.) and information related to storage box (e.g., identifiers of the storage boxes and corresponding user or user account that is authorized to retrieve the storage boxes and/or which is billed for the storage thereof).

[0021] Generally, the storage boxes may have any number of suitable identifiers.

In some embodiments, the storage boxes may include numerical identifiers. For example, the numerical identifiers may be associated with the corresponding storage boxes by placing a bar code thereon, by including an RFID tag thereon, embedding an RFFID tag therein, etc. Additionally or alternatively, the storage boxes may include alphanumerical identifiers and/or any suitable number and any type of suitable identifiers, which may be used to correlate the storage box with one or more users and/or user accounts, with the size of the storage box, with the contents of the storage box, etc. Additionally, or alternatively, the storage boxes may include a graphic, icon, or picture identifier (e.g., a red triangle, pink dog, palm tree, blue ball, face, etc.) intended to make recognition and discernment by human eye faster and more intuitive than a number, alphanumeric, or electronic code may allow.

[0022] In some embodiments, the system may store information related to the contents of one, some, or each of the storage boxes. Specifically, for example, the system may correlate the storage box identifier with the information related to the contents thereof and with one or more user accounts authorized to make decisions related to the storage box (e.g., request retrieval of the storage box, request to discontinue storage, etc.). As such, for example, one or more user accounts may be associated with one or more corresponding storage boxes and the users having access to such account(s) may request retrieval of the storage boxes from the system, as described below in more detail.

[0023] In an embodiment, the user may input the items located in the particular storage boxes into the controller. In some embodiments, the user may input the storage box identifier (e.g., via manual entry, by scanning, etc.) and may input the names and/or pictures of the items stored in the storage box (e.g., type, voice entry, camera, etc.). For example, the user may input the storage box identifier and item names at a personal electronic device (e.g., at a smart phone, tablet, etc.), which may send the input entries to the controller of the system (e.g., the personal electronic device may have sent the inputs from the user via Internet), as described below in more detail.

[0024] As described above, the storage boxes may be removed from the locker access location 100 and may be transferred to a bulk storage facility. For example, the controller may receive an input from the user that may indicate that the storage box has been placed into a storage locker. In an embodiment, after receiving the indication from the user that the storage box has been placed into a storage locker, the controller may lock or direct locking of the storage locker and/or may notify (directly or indirectly) a storage operator and/or a person responsible for removing the storage boxes 130 from the locker access location 100. For example, the controller may generate and send an email, a text message (e.g., SMS), a push notification, etc., to the person responsible for removing the storage boxes 130 from the locker access location 100 and/or delivering the storage boxes 130 to a bulk storage facility.

[0025] In some embodiments, the storage boxes 130 may be removed from the storage lockers 110 and/or secure storage lockers 110a and delivered to a bulk storage facility. For example, a person removing the storage boxes 130 may have a master code or master password to the storage lockers 110 and/or secure storage lockers 110a. In particular, for example, when the controller receives a master code, the controller may open or direct opening of all or select ones of the storage lockers 110 and/or storage lockers 110. In an embodiment, in response to receiving a master code for a particular location and/or set of storage lockers (e.g., for the storage lockers 110 and/or for the secure storage lockers 110a), the controller may open/unlock or direct opening/unlocking of the storage lockers that contain at least one of the storage boxes 130. Alternatively, in response to receiving a master code for a particular location and/or set of storage lockers (e.g., for the storage lockers 110 and/or for the secure storage lockers 110a), the controller may open/unlock or direct opening/unlocking of all of the storage lockers 110 and/or secure storage lockers 110a, respectively. It should be appreciated that different sets of the storage lockers and/or the storage lockers located at different facilities may have different corresponding master codes. Moreover, the controller may change one, some, or each of the master codes from time to time. In an embodiment, a person responsible for removing boxes might make an electronic request to the master controller to perform a batch operation such as automatically opening some or all of the lockers that are to removed and moved to bulk storage. In an embodiment, a person responsible for removing boxes might make a "smart" request to the controller such that only one request is made of the system, but that a series of actions take place in a "smart" sequence. For example, the system might be asked to automatically open the next closest locker to be serviced as soon as an operator closes a locker from which they are extracting a box. The "smart" request might interact with a human operator based on physical cues such as the closing of a locker.

[0026] As the storage boxes 130 are removed from the storage lockers 110 and/or from the secure storage lockers 110a, the controller may receive input that may identify the removed storage boxes 130 (e.g., the controller may receive identifiers of the removed storage boxes 130). For example, bar codes associated with one, some, or each of the storage boxes 130 may be scanned as each of the storage boxes 130 is removed from corresponding storage locker. Additionally or alternatively, as described above, the storage boxes 130 may include radio frequency identification ("RFID") tags, which may be scanned or detected as corresponding ones of the storage boxes 130 are removed from the storage lockers 110 and/or from the secure storage lockers 110a. [0027] As described above, the storage boxes 130 may be delivered to and/or stored at a bulk storage facility. FIGS. 2A-2C are schematic diagrams of bulk storage facilities, according to one or more embodiments. Generally, the bulk storage facilities may have any number of suitable configurations. Moreover, a bulk storage facility may have automated or partially automated placement or racking of the storage boxes therein. For example, when the storage boxes 130 are delivered to the bulk storage facility, an identifier of each of the storage boxes may be input into the controller (e.g., in the same or a similar manner as described above). In some embodiments, an automatic storage and retrieval system or a similar robot or manipulator may place each of the storage boxes at corresponding and/or designated slots or locations (e.g., in one or more racks), and the controller may store and correlate the corresponding identifiers of the stored a storage boxes with the storage locations thereof in the bulk storage facility. As such, for example, in response to receiving a request to remove a specific storage box from the bulk storage facility, the controller may operate or direct operation of a robot, such as a rail-based automatic storage and retrieval system, to remove the storage box that corresponds to a selected identifier from the corresponding location. In an embodiment, the robot may re-scan the storage box after removal thereof from the selected storage location to confirm that the removed storage box has the identifier that is associated at the controller with the selected storage location at the bulk storage facility. It should be appreciated that in one or more embodiments one, some, or each of the storage boxes may be manually removed from corresponding storage locations at the bulk storage facility.

[0028] As described above, a user may request or otherwise indicate to the system removal of one or more storage boxes therefrom, which have been previously placed into storage. For example, the controller may associate specific storage boxes (e.g., specific identifiers of the storage boxes) with the account of the user on the controller. In an embodiment, the controller may identify the storage boxes to the user by any number of names, which may be chosen by the user and/or which may be default names for such storage boxes. For example, the controller may correlate such names with the identifiers of the corresponding storage boxes.

[0029] While in some embodiments user may submit a storage box by placing the storage box into a storage locker, this disclosure is not so limited. For example, storage box may be dropped off at any suitable location and/or collection point (e.g., a general drop box where the received storage boxes are not associated with any specific locker). The system may sort and/or store the storage boxes at a bulk storage locations, and when user requests retrieval of the storage box, the storage box may be retrieved by the user from a storage locker, as described above.

[0030] FIG. 3 is a user interface 200 that may be displayed on a personal electronic device 10 (e.g., a mobile and/or smart phone, laptop, etc.) of a user, according to an embodiment. For example, the storage boxes placed into storage by the user may be named "Box 1," "Box 2," and "Box 3." It should be appreciated, however, that the names of the storage boxes that are associated with a particular user account may also be associated with particular storage box identifiers. Moreover, each user account may select any number of non-duplicative names (e.g., within that account), which may be associated by the controller with the corresponding identifiers of the storage boxes.

[0031] As described above, for example, user may indicate to the controller a request to retrieve one or more of the storage boxes (e.g., via input at the user interface 200 on the personal electronic device 10). For example, user may select the specific storage boxes to retrieve from the storage by name, and the controller may correlate the name displayed to the user with an identifier number of the storage box. Moreover, in some embodiments, the controller may operate and/or direct operation or a robot (at the bulk storage facility) to remove the identified storage boxes from corresponding storage locations at a corresponding bulk storage facility and/or prepare the removed storage boxes for delivery to a locker access location and into one or more storage lockers. As described below in more detail, the storage boxes may be delivered to one or more storage lockers where the user may retrieve the storage boxes.

[0032] In some embodiments, the user may select one or more items for retrieval, and the controller may determine one or more corresponding storage boxes (e.g., may determine corresponding identifiers of the storage boxes) that contain the selected items and may select the determined boxes for delivery to storage lockers. In other words, for example, user may input item names for items located in one, some, or each of the storage boxes. When the user selects one or more item names (e.g., at user interface 200), the controller may determine one or more storage boxes to be retrieved from bulk storage facility and made available to the user at the storage lockers (e.g., at the storage lockers located at a selected locker access location). It should be appreciated that the user interface may vary from one embodiment to the next. FIGS. 4A-4E illustrate user interfaces according to one or more additional or alternative embodiments. [0033] The controller may provide or display any number of suitable locations of the locker access locations for selection by the user. In some embodiments, the controller may display and/or select a locker access location based on location of the user (e.g., as may be determined from a GPS reading from the personal electronic device of the user). Additionally, or alternatively, the selected or default storage location (e.g., without receiving input or selection of a specific storage location from user) may be the location of the locker access location where user initially placed the storage box into storage.

[0034] Generally, the user may select any number of suitable locker access locations and/or storage lockers for receiving the retrieved storage box(es). For example, the controller may provide or display one or more locker access location locations to the user for selection, and indicate to the person responsible for delivery of the storage box(es) the selected location of the locker access location. Alternatively, the controller may make selections automatically based on the user's profile and select the best location for the user to place the storage box. For example, the user might have requested lower lockers in their profile (because they are short) so the controller might default to the nearest available low locker. Additionally, or alternatively, as described above, the controller may operate or direct operation of a robot or manipulator that may remove the storage boxes from storage locations at the bulk storage facility and relocate the removed storage boxes to another location for further processing, such as for placement into one or more delivery vehicles that will deliver the storage boxes to the storage lockers. That is, the controller may operate or direct operation of a robot or manipulator at least in part based on the retrieval request received from a user to retrieve one or more storage boxes. In some embodiments, the controller may operate or direct operation of a robot to load the storage boxes into suitable delivery vehicles (e.g., such that route of the delivery vehicle corresponds with the deliver location of the locker access location that contains the storage lockers that will receive the retrieved storage box(es)).

[0035] As mentioned above, in some embodiments, suitable storage lockers may be opened with a master code or key. Hence, the storage boxes retrieved from the bulk storage facility may be placed into corresponding storage lockers at the selected locker access location. Moreover, the controller may correlate specific storage lockers with corresponding storage boxes placed therein. For example, as described above, the storage boxes may include a barcode, an RFID, or another scannable identifier. In some embodiments, a person placing the storage boxes into corresponding storage lockers may scan the storage boxes and may scan or may enter an identifier of the corresponding storage lockers (e.g., storage lockers may also include barcodes, RFIDs, etc., that identify the specific storage lockers to the controller).

[0036] In an embodiment, the storage lockers may include barcode and/or RFID scanners, such that each of the storage lockers may determine the specific storage box(es) positioned therein. Furthermore, as described above, the storage lockers may be operably coupled to the controller (e.g., such that the controller may control opening and closing of the storage lockers). For example, after scanning the specific storage boxes, each of the storage lockers may transmit to the controller corresponding identifier information that the controller may correlate with the storage locker identifier. It should be appreciated that, in some embodiments, one or more RF sensors or detectors may be positioned near and/or inside corresponding lockers and each of the sensors may have an identifier that corresponds to or may be correlated with an identifier of the storage locker within which the sensor is positioned. Hence, for example, the controller may receive signals from the RF sensors and/or detectors and may correlate the identifier of the sensors with the identifier of the storage lockers and identifiers of the storage boxes, thereby correlating specific storage boxes to the corresponding storage lockers that hold the storage boxes.

[0037] Accordingly, for example, the controller may indicate or identify to user specific storage locker(s) that contain the storage box(es) requested for retrieval by the user. In some embodiments, the controller may display to user the storage locker numbers or other identifiers visible on the storage lockers that secure the requested storage boxes. Moreover, the controller may receive a request from user to open and/or unlock the selected storage lockers that contain the requested storage boxes. For example, the user may send the request from the personal electronic device, and the request may be received at the controller that may open/unlock or direct opening/unlocking of the storage locker(s) containing the storage box(es) requested by the user.

[0038] Additionally or alternatively, the controller may provide (e.g., via email, text, or other notifications, at an interface of the personal electronic device of the user, etc.) suitable codes or keys and/or storage locker identifiers for user to unlock the storage lockers that contain the requested storage boxes. For example, the user may enter the codes at a controller input interface that may be located near the storage lockers, and based on the entered codes, the controller may direct opening and/or unlocking of the storage lockers that contain the storage boxes requested by the user. In some embodiments, at the controller input interface, the user may first enter the storage locker identifier(s) and corresponding access codes, and the controller may direct opening and/or unlocking of the storage lockers corresponding to the storage locker identifier(s).

[0039] Generally, the controller may include one or more processors operably coupled to memory, storage memory, and I/O interface at which input and output devices may connect to the controller. In some embodiments, the controller may include one or more general purpose computers configured and/or programmed to perform the acts and steps described herein. Moreover, the controller may include multiple computers (e.g., general purpose computers) may be collocated or may be placed at different locations (e.g., at different geographic locations) and/or may be connected by one or more networks, such as by in internal network and/or via Internet. Additionally, it should be appreciated that the controller, as described herein, may include personal electronic devices that may be operably coupled and/or connected to one or more computers (e.g., via Internet), and the personal electronic devices may be configured and/or programmed to performs the acts or steps described herein (e.g., the acts or steps described herein in connection with the personal electronic devices).

[0040] While various aspects and embodiments have been disclosed herein, other aspects and embodiments are contemplated. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting.

Claims

CLAIMS What is claimed is:

1. A temporary storage system, comprising:

one or more lockable storage lockers located at a locker access location;

one or more storage boxes sized and configured to be placed into at least one of the one or more storage lockers;

a bulk storage facility configured to store the one or more storage boxes; and a controller configured to:

correlate at least one of the one or more storage boxes with at least one user account; and

control location of the at least one of the storage box between the one or more lockable storage lockers and the bulk storage facility based at least partially on input received from a user associated with the user account.

2. A method of storing one or more storage boxes, the method comprising: correlating at least one of the one or more storage boxes with at least one user account; and

via a controller, controlling location of the at least one of the storage box between the one or more lockable storage lockers and the bulk storage facility based at least partially on input received from a user associated with the user account.