ITEM EXCHANGE LOCKER AND STATION

An item exchange locker station may include a station-level user interface accessible from outside the station enclosure to receive identifying information of a deliverer or a retriever seeking to enter the station and to transmit the identifying information to an off-site data server for the identifying information to be validated against a database. The station may also include lockers disposed within the station enclosure, the lockers including a locker access door, and a locker locking mechanism configured to alternatively lock and unlock to impede and permit, respectively, opening of the locker access door. The station may also include a locker-level controller configured to receive locker unlocking instructions from the off-site data server upon validation of the identifying information.

BACKGROUND

In the era of online purchasing sites such as eBay® and Craigslist®, the process of exchanging items such as packages and other transportable goods from one person to another has become a topic of significant attention. In particular, enhancing safety and security in the exchanging process is highly desirable.

Those involved in exchanging an item may commonly include senders, receivers, and delivery personnel such as for example the U.S. Postal Service®. Receivers are people who are intended to receive the item. Often times the receiver is a person who purchased the item. The sender may be a manufacturer, vendor, seller, or distributor of the item, for example. In response to the purchase of an item in, for example, Craigslist® the sender may enlist the services of delivery personnel (e.g., couriers, shippers, postal service) if the item is to be shipped to a relatively distant location. For more local transactions, however, senders or receivers may also function as the delivery personnel, delivering or picking up the item themselves for the other person's location or from a neutral site. This sometimes raises issues of safety and security.

Although unattended delivery and retrieval systems have been devised, safety and security in the exchanging process has been a challenge. Security personnel may help enhance security but may also increase the cost of the transactions. Curtailing time availability of delivery and retrieval systems to daylight hours may also help enhance security but may make it inconvenient for users. Locating delivery and retrieval systems within busy locations such as gas stations, bus stations, train stations, convenience stores, etc. may also enhance security but may limit access and availability.

Therefore, there is a need in the field for improvements to the item exchange process to make it more safe and secure while making it also convenient, widely available, and cost-effective.

SUMMARY OF THE INVENTION

The present disclosure provides an item exchange locker station that provides safety and security during item exchanges while making it also convenient, widely available, and cost-effective.

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate various example systems, methods, and so on, that illustrate various example embodiments of aspects of the invention. It will be appreciated that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. One of ordinary skill in the art will appreciate that one element may be designed as multiple elements or that multiple elements may be designed as one element. An element shown as an internal component of another element may be implemented as an external component and vice versa. Furthermore, elements may not be drawn to scale.

DETAILED DESCRIPTION

FIGS. 1A-1Cillustrate various views of an exemplary item exchange locker station1. The station1includes a station enclosure10including, for example, walls12, windows14, and a station entry door16. The station enclosure10may also include an emergency exit18.

The door16alternatively opens and closes to permit and impede entry to the station enclosure10. The station1may also include a main lock or station locking mechanism to alternatively lock and unlock to impede and permit opening of the station entry door16. The station1may also include a station-level user interface20accessible from outside the station enclosure10. As described in detail below, the station-level user interface20receives identifying information of a person (i.e., a deliverer or a retriever) seeking to enter the station enclosure10for the information to be transmitted to an off-site location to be validated. Upon validation of the identifying information, station unlocking instructions may be received from the off-site location for the station locking mechanism to unlock to permit opening of the station entry door16upon receipt of the station unlocking instructions.

The station1may also include lockers30. Upon validation of the identifying information and receiving the station unlocking instructions, a lighted path19on the floor or (as shown in the illustrated embodiment ofFIGS. 1A and 1C) on the ceiling of the station enclosure10may be used to indicate to a user the particular locker30assigned to the user. The lighted path19may indicate the path from the station-level user interface20, a locker-level user interface120, or from the station entry door16to the assigned locker30.

The lockers30may include a locker access door32that alternatively opens and closes to permit and impede access to the locker's interior. The lockers30may also include a locker lock or locker locking mechanism to alternatively lock and unlock to impede and permit opening of the locker access door32.

In one embodiment, a locker30may include a locker-level user interface that receives identifying information of the deliverer or retriever seeking to access the locker30. In the illustrated embodiment, the station1includes at least one locker-level user interface120at a location other than at a locker30such as, for example, a welcome kiosk40.

The locker-level user interface120receives the identifying information of the deliverer or retriever seeking to access the locker30so that the information may be transmitted to an off-site location to be validated. Upon validation of the identifying information, locker unlocking instructions may be received from the off-site location for the locker locking mechanism to unlock to permit opening of the locker access door32.

This way, the deliverer or retriever may gain access to the station enclosure10and a locker30.

FIG. 2illustrates a perspective view of an exemplary user interface20. For brevity of explanation, a station-level user interface20is used here to describe the features of a user interface. This description, however, is similarly applicable to a locker-level user interface120, which, although not necessarily identical, may share many features with the station-level user interface20.

The station-level user interface20may include a display22that may welcome the user and provide instructions. As described below, an off-site or system server may assign each user identifying information (i.e., credentials) such as, for example, a unique Swap ID, which may have a corresponding account QR code. The server may also store the relationships between users and their credentials for later used in approving or denying user's access to a station1or locker30. The server may further make the credentials available to the user for display on a screen of a mobile device MD (e.g., mobile phone) to use as a “key” to gain access to the station1or a locker30. The station-level user interface20may also include a dock24into which a user may insert the mobile device MD. The dock24may include a scanner to scan the credentials (e.g., QR code) from the screen of the mobile device MD. In addition or alternatively, the station-level user interface20may include a keypad by which the user may enter credentials such as a Swap ID, etc.

The station-level user interface20receives the identifying information of the user (i.e., a deliverer or a retriever) seeking to enter the station enclosure10and the information is transmitted to an off-site location to be validated. Upon validation of the identifying information, station unlocking instructions are received from the off-site location for the station locking mechanism to unlock to permit opening of the station entry door16. Similarly, the locker-level user interface receives the identifying information of the user (i.e., a deliverer or a retriever) seeking to access a corresponding locker30and the information is transmitted to an off-site location to be validated. Upon validation of the identifying information, locker unlocking instructions are received from the off-site location for the locker locking mechanism to unlock to permit access to the locker30.

In one embodiment, the user interface20includes vertical rails26and a handle28such that a height or vertical position of the user interface20including the display22and the dock24may be adjusted for user's convenience.

FIG. 3illustrates a perspective view of an exemplary user interface kiosk40. The kiosk40may include one or more user interfaces20. The kiosk40may be used in at least two contexts.

First, the kiosk40may be used to include one or more station-level user interfaces20. This may be desirable in, for example, a station1with very high traffic volume. In such a high traffic station, multiple station-level user interfaces20may be desirable and the kiosk40may be a way to provide such multiple station-level user interfaces20in a convenient and efficient package. A kiosk40may also be desirable in a station1located in very cold temperature areas where having a station-level user interface20exposed to the elements may be uncomfortable for the user. In such cases, the station1may include a temperature-controlled lobby area outside the station enclosure10in which the kiosk40including multiple station-level user interfaces20may be located for the user to enter identifying information to gain access to the main station enclosure10.

Second, the kiosk40may be used to include one or more locker-level user interfaces120. This may be desirable to provide users with a welcoming lobby area inside the station enclosure10in which the kiosk40with multiple locker-level user interfaces120may be located for the user to enter identifying information to gain access to a specific locker30. This solution may be more cost-effective than providing a dedicated user interface120for each locker30.

FIG. 4A-4Cillustrate exemplary lockers30. As described above, a locker30may include a locker access door32that alternatively opens and closes to permit and impede access to the locker's interior. A locker30may also include a locker lock or locker locking mechanism to alternatively lock and unlock to impede and permit opening of the locker access door32. In some embodiments, at least some of the lockers30may include a locker-level user interface that receives identifying information of the deliverer or retriever seeking to access the locker30.

A locker30may also include a local indicator36such an LED light to, for example, indicate to a user a locker specifically assigned to that user. For example, upon validation of the identifying information at the station level and receiving the station unlocking instructions, the indicator36may be made to blink to indicate to a user the particular locker30assigned to the user. The indicator36may instead or in addition be used to indicate whether a locker is locked (e.g., red) or unlocked (e.g., green). The indicator36light may be visible from an area inside the station enclosure10adjacent the entry door16or the kiosk40and the light36lights up upon receipt of the station unlocking instructions so that the light36identifies a specific locker30to which the deliverer is to deliver or from which the retriever is to retrieve. As shown inFIG. 4A, in one embodiment, a user may press on an unlocked locker door32to open the door. The user may similarly press on the locker door32to close the door. As shown inFIGS. 4B and 4Clocker doors32may be slide-out doors (4B) or hinged doors (4C).

FIG. 5illustrates a block diagram of an exemplary system100for the operation of the station1. The system100may include at least two main portions: a local or station portion110and a remote or cloud portion210. This architecture is scalable and, therefore, many station portions110may interface with a cloud portion210and many cloud portions210may coexist within a system100.

The cloud portion210may include a web interface212, a system or off-site server214, and a system database216. The station portion110may include two sub-systems: a station-level subsystem110aand a locker-level subsystem110b.The station-level subsystem110amay include the station-level user interface20, a station-level controller112, and the entry door locking mechanism114. The station-level subsystem110amay also include additional peripherals116such as, for example, the path lights19. The locker-level subsystem110bmay include the locker-level user interface120, a locker-level controller122, and the locker door locking mechanism124. The locker-level subsystem110bmay also include additional peripherals126such as, for example, the local indicator36.

FIG. 6illustrates a flow diagram for an exemplary method600for operating the item exchange locker station1, in particular for purchasing a locker and scheduling an exchange.

At605, users may interact with the web interface212to register (at610) or log in (at615) to place locker orders. A user, for example a user seeking to deliver an item sold on Craigslist® to another user may use the web interface212to open an account and order a locker to exchange the item safely. Users may, for example, use integrated single sign-on services (available from Facebook®, Google®, and other providers) for account registration and login validation for accessing users' accounts. During registration, the system server214may assign each user a unique Swap ID, which may have a corresponding account QR code. The server214may store the relationships between users, Swap ID, and QR codes in the system database216.

In one embodiment, both a Swap ID and the corresponding QR code may be permanently assigned to a single customer to act as identifier and validation key for that user in the system100. The QR code may serve as the primary, scannable user identifier while the Swap ID may be used as a redundancy in the unlikely event there is an error with scanning equipment on-site at the station1or in the event that a user (deliverer or retriever) is unable to present their QR code at the time they wish to access the station1or a locker30. The server214may assign a user a Swap ID and QR code and send this information to the user via text message or email. The Swap ID and QR code may also be available to users by logging in to their accounts online. Swap ID and QR codes may be permanently associated with user's accounts and, thus, may be reused for transactions associated with those accounts, regardless of their role (deliverer or retriever) in any specific transaction.

Swap ID or QR codes may also serve as identifiers and be associated with flags for users to receive personalized conditions which will be applied to that customer's current or subsequent transactions. These flags may automatically adjust the user experience whenever the specific Swap ID or QR code is utilized. Examples include: customizing the user's experience to comply with ADA-Compliance requests, offering discounted rate structures for specified individuals, allowing remote suspension/reinstatement of services for a particular user's account, etc.

At620, once the deliverer logs in to the web interface212, the deliverer may purchase a locker30to exchange the item. In one embodiment, the web interface may present the deliverer the option to choose from a number of different locker sizes, dates available to deliver the item, specific time windows on the chosen delivery date, and a particular station1(from perhaps many available station locations) the deliverer prefers to complete the item exchange.

At625, the web interface212may also ask the deliverer for valid contact information (e.g., email address, cell phone number, etc.) of the retriever (the user who would retrieve the item from the chosen locker30). At630, if the entered retriever contact information is already associated with a valid account, the retrieving portion of the locker purchase may be assigned to that account and the corresponding Swap ID. If the entered retriever contact information is not already associated with a valid account, at635, the system server214may assign a Swap ID, which may have a corresponding account QR code, and, at640, communicate (e.g., email, text, voice message, etc.) with the retriever using the contact information requesting the retriever to complete creation of an account or log-in. At645, the retriever may log-in. As do the deliverers, the retrievers may, for example, use integrated single sign-on services (available from Facebook®, Google®, and other providers) for account registration and log-in. The server214may store the relationships between users, Swap ID, and QR codes in the system database216.

At650, once the retriever has logged in, the web interface216may provide the retriever information such as dates available to retrieve the item, time windows available on the chosen retrieval date, and the particular station1from which to retrieve the item. The retriever may choose from the dates available to retrieve the item and the time windows available on the chosen retrieval date. At655, once the retriever has made selections, the exchange may be confirmed and confirmation communication (e.g., email, text message, voice message, etc.) may be sent out to deliverer and retriever confirming. The deliverer's communication may include the specific delivery details (date, time window, location, locker size, etc.) including, in one embodiment, identification of a specific locker30at the station1to be used for the exchange.

FIG. 7illustrates a flow diagram for an exemplary method700for operating the item exchange locker station1, in particular for performance of an exchange: delivery.

Deliverers may access only the specific chosen station1and only a specific locker30. The locker30may be assigned during the registration process or upon the deliverer arriving at the station1. Moreover, access is only available during the exchange date(s) and time window specified during the purchasing process. Upon delivery or upon expiration of the time window, deliverer access is revoked. A station1may be generally available 24 hours a day 7 days a week but its door16remains locked and is only unlockable by presenting a valid Swap ID during a valid exchange time. When a deliverer's exchange time begins the system server214may activate the deliverer's Swap ID and/or QR code to grant the deliverer access to the station1and/or locker30. The server214may also send the deliverer a communication (e.g., email, text message, voice message, etc.) that their exchange time has begun.

Once the exchange time has begun, at705, the deliverer may scan their QR code or input their Swap ID by scanning their mobile device's screen using the dock24at the station-level user interface20. In one embodiment, scanning of the QR code or inputting of the Swap ID at the station-level user interface20does not, by itself, unlock the door16. In fact, notice that in the exemplary system ofFIG. 5there is no data connection between the user interface20and the controller112that controls the locking mechanism114. The user interface20is effectively incapable of generating or pushing any unlock signals to any doors including the station door16or locker doors32. Instead, scanning of the QR code or inputting of the Swap ID at the station-level user interface20, at710, transmits unlock requests including identifying information to the off-site system server214for the identifying information to be remotely validated against the database216. At715, validation includes, not only verifying the identity of the deliverer, but also verifying the appropriate station1, exchange time, etc.

At720, in the case that validation fails, the system server214transmits an unlock request denial to the user interface20.

At725, upon validation of the identifying information, the system server214transmits station unlocking instructions to the station-level controller112and, in one embodiment, an unlock request approval message to the user interface20to be displayed to the user. Upon receipt of the station unlocking instructions, at730, the station-level controller112may transmit an unlock signal to the station locking mechanism114to unlock to permit opening of the station entry door16.

In one embodiment, scanning of the QR code or inputting of the Swap ID at the station-level user interface20generates a “wake” signal that may be transmitted (e.g., to the system server214to be transmitted to the controller112or another appropriate control) for the interior lights at the station1to turn on, if necessary, as well for security features such as security camera recording, etc. to commence or at least time stamp.

In one embodiment, upon validation of the identifying information and receiving the station unlocking instructions, a lighted path19on the floor or (as shown in the illustrated embodiment ofFIGS. 1A and 1C) on the ceiling of the station enclosure10may be used to indicate to a user the particular locker30assigned to the user. The lighted path19may indicate the path from the station-level user interface20, a locker-level user interface120, or from the station entry door16to the assigned locker30. Therefore, the station1may include one or more light paths19disposed on the floor or the ceiling of the station to light up upon receipt of station unlocking instructions for the light path to guide the deliverer or retriever from the entry door16or from a welcoming kiosk40to a specific locker30to which the deliverer is to deliver or from which the retriever is to retrieve.

Unlocking of the door16, however, does not unlock any lockers30inside of the station1. Once inside the station enclosure10, at735, the deliverer may scan their QR code or input their Swap ID a second time by using the dock24at the locker-level user interface120.

In one embodiment, scanning of the QR code or inputting of the Swap ID at the locker-level user interface120does not, by itself, unlock the locker door32. The user interface120may be effectively incapable of generating or pushing any unlock signals to any doors including the station door16or locker doors32. Instead, at740, scanning of the QR code or inputting of the Swap ID at the locker-level user interface120causes it to transmit an unlock request including identifying information to the off-site system server214for the identifying information to be validated against the database216. At745, validation includes, not only verifying the identity of the deliverer, but also verifying the appropriate locker30, exchange time, etc.

At750, in the case that validation fails, the system server214transmit a denial of access to the locker-level user interface120.

At755, upon validation of the identifying information, the system server214transmits locker unlocking instructions to the locker-level controller122and, in one embodiment, an unlocking verification message to the user interface120to be displayed to the user. Upon receipt of the station unlocking instructions, at760, the locker-level controller122may transmit an unlock signal to the locker locking mechanism124to unlock to permit opening of the locker door32. As described above, once the locker door32is unlocked the deliverer may open by pressing on it or other means. Once the door32is open, the deliverer may leave the item inside the locker30and close the door.

The locker30may also include a door sensor that senses whether the door32is open or closed and transmit the information to the locker-level controller122and, in one embodiment, to the system server214. Once the locker-level controller122transmits the unlock signal and, subsequently, at765, detects via the sensor that the locker door32has been opened and then closed, the locker-level controller122, at770, may transmit a lock signal to the locker locking mechanism124to lock the locker door32. The locker-level controller122, at775, may then transmit a locked signal to the system server214indicating that the locker door32is now locked.

In one embodiment, upon issuance of the locked signal (verifying that the locker door32has been closed and locked), the locker-level controller122or, in one embodiment, the system server214commences a “deliverer's grace period” of, for example, 15 minutes. During this period, the deliverer may re-scan their QR code or input their Swap ID as described above to unlock the station door16or the locker door32to gain access to the station enclosure10as well as to the specific locker30. The grace period may be provided in case the deliverer changes her mind or has any other issue that necessitates access to the locker30after the first attempt at delivery. Upon expiration of the grace period, the deliverer's access to both the locker30and to the station1is automatically revoked.

In one embodiment, the station1or the station-level locking mechanism114may further include a sensor, camera, or other device that detects whether the deliverer has in fact exited the station1after the deliverer's last entry into the station1and transmits that deliverer exit information to the station-level controller122or the system server214.

Once the deliverer grace period expires and/or the system server214receives the deliverer exit information, at780, the system server214commences a lag timer period of, for example, 25 minutes. During this lag timer, neither the deliverer nor the retriever may access the station1. The lag timer may be provided to promote the safety and security of the deliverer and the retriever by preventing them from crossing paths inside the station1and allowing the deliverer adequate time to leave the station1before the retriever is to arrive.

At785, once the lag timer expires, the deliverer's exchange time ends and the retriever's exchange time begins; the system server214may activate the retriever's Swap ID or QR code, granting them access to the station1and to the specific locker30. At this time, only the retriever (and not the deliverer) may access the station1and the locker30. The system server214may also notify the retriever via email, text message, voice message, etc. that the item is now available for pick-up at the specific station1and the specific locker30. The retriever may then access the station1and locker30in a very similar manner as the deliverer did.

FIG. 8illustrates a flow diagram for an exemplary method800for operating the item exchange locker station1, in particular for performance of an exchange: retrieval.

When a retriever's exchange time begins, at805, the retriever may scan their QR code or input their Swap ID by scanning their mobile device's screen using the dock24at the station-level user interface20. In one embodiment, scanning of the QR code or inputting of the Swap ID at the station-level user interface20does not, by itself, unlock the door16. In fact, notice that in the exemplary system ofFIG. 5there is no data connection between the user interface20and the controller112that controls the locking mechanism114. The user interface20is effectively incapable of generating or pushing any unlock signals to any doors including the station door16or locker doors32. Instead, at810, scanning of the QR code or inputting of the Swap ID at the station-level user interface20transmits an unlock request including identifying information to the off-site system server214for the identifying information to be validated against the database216. At815, validation includes, not only verifying the identity of the retriever, but also verifying the appropriate station1, exchange time, etc.

In the case that validation fails, at820, the system server214transmit an unlock request denial to the user interface20. Upon validation of the identifying information, at825, the system server214transmits station unlocking instructions to the station-level controller112and, in one embodiment, an unlock request approval message to the user interface20to be displayed to the user. Upon receipt of the station unlocking instructions, at830, the station-level controller112may transmit an unlock signal to the station locking mechanism114to unlock to permit opening of the station entry door16.

In one embodiment, scanning of the QR code or inputting of the Swap ID at the station-level user interface20generates a “wake” signal that may be transmitted (e.g., to the system server214to be transmitted to the controller112or another appropriate control) for the interior lights at the station1to turn on, if necessary, as well for security features such as security camera recording, etc. to commence or at least time stamp.

Unlocking of the door16, however, does not unlock any lockers30inside of the station1. Once inside the station enclosure10, at835, the retriever may scan their QR code or input their Swap ID a second time by using the dock24at the locker-level user interface120.

In one embodiment, scanning of the QR code or inputting of the Swap ID at the locker-level user interface120does not, by itself, unlock the locker door32. The user interface120may be effectively incapable of generating or pushing any unlock signals to any doors including the station door16or locker doors32. Instead, at840, scanning of the QR code or inputting of the Swap ID at the locker-level user interface120causes it to transmit an unlock request including identifying information to the off-site system server214for the identifying information to be validated against the database216. At845, validation includes, not only verifying the identity of the retriever, but also verifying the appropriate locker30, exchange time, etc.

In the case that validation fails, at850, the system server214transmits a denial of access to the locker-level user interface120. Upon validation of the identifying information, at855, the system server214transmits locker unlocking instructions to the locker-level controller122and, in one embodiment, an unlocking verification message to the user interface120to be displayed to the user. Upon receipt of the station unlocking instructions, at860, the locker-level controller122may transmit an unlock signal to the locker locking mechanism124to unlock to permit opening of the locker door32. As described above, once the locker door32is unlocked the retriever may open by pressing on it or other means. Once the door32is open, the retriever may retrieve the item inside the locker30and close the door32.

The locker30may also include a door sensor that senses whether the door32is open or closed and transmit the information to the locker-level controller122and, in one embodiment, to the system server214. Once the locker-level controller122transmits the unlock signal and, at865, subsequently, detects via the sensor that the locker door32has been opened and then closed, at870, the locker-level controller122may transmit a lock signal to the locker locking mechanism124to lock the locker door32. At875, the locker-level controller122may then transmit a locked signal to the system server214indicating that the locker door32is now locked.

In one embodiment, upon issuance of the locked signal (verifying that the locker door32has been closed and locked), the locker-level controller122or, in one embodiment, the system server214commences a “retriever's grace period” of, for example, 15 minutes. During this period, the retriever may re-scan their QR code or input their Swap ID as described above to unlock the station door16or the locker door32to gain access to the station enclosure10as well as to the specific locker30. The grace period may be provided in case the retriever changes her mind, forgets something, or has any other issue that necessitates access to the locker30after the first attempt at retrieval. Upon expiration of the grace period, the retriever's access to both the locker30and to the station1is automatically revoked.

In one embodiment, the station1or the station-level locking mechanism114may further include a sensor, camera, or other device that detects whether the retriever has in fact exited the station1after the retriever's last entry into the station1and transmits that retriever exit information to the station-level controller122or the system server214.

Once the retriever grace period expires and/or the system server214receives the retriever exit information, at880, the system server214closes the transaction, the exchange is complete! The system server214may also notify the deliverer and retriever that their transaction has been successfully completed and the locker30used for their exchange may be re-listed on the web interface212as available for rental.

As stated above, the system server214keeps a log of unlock requests in the database216. This information may be useful in many ways. For example, after a certain number of unlock requests from a given station1or a given locker30, a maintenance request may automatically be pushed to a maintenance technician to inspect the station's door locking mechanism114or the locker's locking mechanism124. In another example, after a certain number of unlock requests from a given station1, a cleaning request may be automatically pushed to a cleaning crew to attend to cleaning the station1.

In one embodiment, at least some lockers30may include a contraband sensor, which may automatically sense suspicious materials, send a contraband signal to the system server214, which may, in turn, set a contraband flag to prevent access to the locker30in question until the contraband flag has been cleared. The log information (as described above) regarding the specific locker30may be available to aid in any subsequent investigation regarding the detected contraband.

While the figures illustrate various actions occurring in serial, it is to be appreciated that various actions illustrated could occur substantially in parallel, and while actions may be shown occurring in parallel, it is to be appreciated that these actions could occur substantially in series. While a number of processes are described in relation to the illustrated methods, it is to be appreciated that a greater or lesser number of processes could be employed and that lightweight processes, regular processes, threads, and other approaches could be employed. It is to be appreciated that other exemplary methods may, in some cases, also include actions that occur substantially in parallel. The illustrated exemplary methods and other embodiments may operate in real-time, faster than real-time in a software or hardware or hybrid software/hardware implementation, or slower than real time in a software or hardware or hybrid software/hardware implementation.

FIG. 9illustrates a block diagram of an exemplary machine900for an item exchange locker station1. InFIG. 9the machine900is disclosed in the context of the station-level subsystem110aand, more specifically, the station-level controller112. However, the machine900may also be used to deploy the locker-level subsystem110band, more specifically, the locker-level controller122, the station-level user interface20, the locker-level user interface120as well as the remote server214and the web interface212of the remote portion210.

The machine900may include a processor902, a memory904, database216, and I/O Ports910operably connected by a bus908. In one example, the machine900may receive or transmit input or output signals via, for example, I/O Ports910or I/O Interfaces918from or to, for example, the station entry door locking mechanism114, the locker door locking mechanism124, the web interface212, and the peripherals116and126. Thus, the station-level controller112, the locker-level controller122, the station-level user interface20, the locker-level user interface120, the remote server214, and the web interface212may be implemented in machine900as hardware, firmware, software, or a combination thereof and, thus, the machine900and its components may provide means for performing functions described herein as performed the station-level controller112, the locker-level controller122, the station-level user interface20, the locker-level user interface120, the remote server214, and the web interface212.

The processor902can be a variety of various processors including dual microprocessor and other multi-processor architectures. The memory904can include volatile memory or non-volatile memory. The non-volatile memory can include, but is not limited to, ROM, PROM, EPROM, EEPROM, and the like. Volatile memory can include, for example, RAM, synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).

A disk906may be operably connected to the machine900via, for example, an I/O Interfaces (e.g., card, device)918and an I/O Ports910. The disk906can include, but is not limited to, devices like a magnetic disk drive, a solid state disk drive, a floppy disk drive, a tape drive, a Zip drive, a flash memory card, or a memory stick. Furthermore, the disk906can include optical drives like a CD-ROM, a CD recordable drive (CD-R drive), a CD rewriteable drive (CD-RW drive), or a digital video ROM drive (DVD ROM). The memory904can store processes914or data916, for example. The disk906or memory904can store an operating system that controls and allocates resources of the machine900.

The bus908can be a single internal bus interconnect architecture or other bus or mesh architectures. While a single bus is illustrated, it is to be appreciated that machine900may communicate with various devices, logics, and peripherals using other busses that are not illustrated (e.g., PCIE, SATA, Infiniband, 1394, USB, Ethernet). The bus908can be of a variety of types including, but not limited to, a memory bus or memory controller, a peripheral bus or external bus, a crossbar switch, or a local bus. The local bus can be of varieties including, but not limited to, an industrial standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an extended ISA (EISA) bus, a peripheral component interconnect (PCI) bus, a universal serial (USB) bus, and a small computer systems interface (SCSI) bus.

The machine900may interact with input/output devices via I/O Interfaces918and I/O Ports910. Input/output devices can include, but are not limited to, a keyboard, a microphone, a pointing and selection device, cameras, video cards, displays, disk906, network devices920, and the like. The I/O Ports910can include but are not limited to, serial ports, parallel ports, and USB ports.

The machine900can operate in a network environment and thus may be connected to network devices920via the I/O Interfaces918, or the I/O Ports910. Through the network devices920, the machine900may interact with a network. Through the network, the machine900may be logically connected to remote computers. The networks with which the machine900may interact include, but are not limited to, a local area network (LAN), a wide area network (WAN), and other networks. The network devices920can connect to LAN technologies including, but not limited to, fiber distributed data interface (FDDI), copper distributed data interface (CDDI), Ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communication (IEEE 802.11), Bluetooth (IEEE 802.15.1), Zigbee (IEEE 802.15.4) and the like. Similarly, the network devices920can connect to WAN technologies including, but not limited to, point to point links, circuit switching networks like integrated services digital networks (ISDN), packet switching networks, and digital subscriber lines (DSL). While individual network types are described, it is to be appreciated that communications via, over, or through a network may include combinations and mixtures of communications.

Definitions

The following includes definitions of selected terms employed herein. The definitions include various examples or forms of components that fall within the scope of a term and that may be used for implementation. The examples are not intended to be limiting. Both singular and plural forms of terms may be within the definitions.

As used herein, an “operable connection” or “operable coupling,” or a connection by which entities are “operably connected” or “operably coupled” is one in which the entities are connected in such a way that the entities may perform as intended. An operable connection may be a direct connection or an indirect connection in which an intermediate entity or entities cooperate or otherwise are part of the connection or are in between the operably connected entities. In the context of signals, an “operable connection,” or a connection by which entities are “operably connected,” is one in which signals, physical communications, or logical communications may be sent or received. Typically, an operable connection includes a physical interface, an electrical interface, or a data interface, but it is to be noted that an operable connection may include differing combinations of these or other types of connections sufficient to allow operable control. For example, two entities can be operably connected by being able to communicate signals to each other directly or through one or more intermediate entities like a processor, operating system, a logic, software, or other entity. Logical or physical communication channels can be used to create an operable connection.

“Signal,” as used herein, includes but is not limited to one or more electrical or optical signals, analog or digital signals, data, one or more computer or processor instructions, messages, a bit or bit stream, or other means that can be received, transmitted, or detected.

“Software,” as used herein, includes but is not limited to, one or more computer or processor instructions that can be read, interpreted, compiled, or executed and that cause a computer, processor, or other electronic device to perform functions, actions or behave in a desired manner. The instructions may be embodied in various forms like routines, algorithms, modules, methods, threads, or programs including separate applications or code from dynamically or statically linked libraries. Software may also be implemented in a variety of executable or loadable forms including, but not limited to, a stand-alone program, a function call (local or remote), a servlet, an applet, instructions stored in a memory, part of an operating system or other types of executable instructions. It will be appreciated by one of ordinary skill in the art that the form of software may depend, for example, on requirements of a desired application, the environment in which it runs, or the desires of a designer/programmer or the like. It will also be appreciated that computer-readable or executable instructions can be located in one logic or distributed between two or more communicating, co-operating, or parallel processing logics and thus can be loaded or executed in serial, parallel, massively parallel and other manners.

Suitable software for implementing the various components of the example systems and methods described herein may be produced using programming languages and tools like Java, Pascal, C#, C++, C, CGI, Perl, SQL, APIs, SDKs, assembly, firmware, microcode, or other languages and tools. Software, whether an entire system or a component of a system, may be embodied as an article of manufacture and maintained or provided as part of a computer-readable medium as defined previously. Another form of the software may include signals that transmit program code of the software to a recipient over a network or other communication medium. Thus, in one example, a computer-readable medium has a form of signals that represent the software/firmware as it is downloaded from a web server to a user. In another example, the computer-readable medium has a form of the software/firmware as it is maintained on the web server. Other forms may also be used.