EP2616615A1 - Systèmes et procédés pour accéder à un espace de stockage sécurisé ou pour gérer celui-ci - Google Patents

Systèmes et procédés pour accéder à un espace de stockage sécurisé ou pour gérer celui-ci

Info

Publication number
EP2616615A1
EP2616615A1 EP11824350.0A EP11824350A EP2616615A1 EP 2616615 A1 EP2616615 A1 EP 2616615A1 EP 11824350 A EP11824350 A EP 11824350A EP 2616615 A1 EP2616615 A1 EP 2616615A1
Authority
EP
European Patent Office
Prior art keywords
recipient
access
access code
server
coupled
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP11824350.0A
Other languages
German (de)
English (en)
Other versions
EP2616615A4 (fr
Inventor
Dickory Rudduck
Christopher Kelliher
Benjamin Ford
Anthony White
Maarten R. Van Duijn
John Evanston Freese
Eric Gesell
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telezygology Inc
Original Assignee
Telezygology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/881,772 external-priority patent/US8698596B2/en
Application filed by Telezygology Inc filed Critical Telezygology Inc
Publication of EP2616615A1 publication Critical patent/EP2616615A1/fr
Publication of EP2616615A4 publication Critical patent/EP2616615A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/00174Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00571Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F17/00Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/10Coin-freed apparatus for hiring articles; Coin-freed facilities or services for means for safe-keeping of property, left temporarily, e.g. by fastening the property
    • G07F17/12Coin-freed apparatus for hiring articles; Coin-freed facilities or services for means for safe-keeping of property, left temporarily, e.g. by fastening the property comprising lockable containers, e.g. for accepting clothes to be cleaned
    • G07F17/13Coin-freed apparatus for hiring articles; Coin-freed facilities or services for means for safe-keeping of property, left temporarily, e.g. by fastening the property comprising lockable containers, e.g. for accepting clothes to be cleaned the containers being a postal pick-up locker
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083Shipping
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/00174Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00896Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys specially adapted for particular uses

Definitions

  • This application relates to storage areas and, more specifically to systems and methods for accessing or otherwise managing these storage areas.
  • a locked door protects a secured space such as a storage locker.
  • the lock that secures the door can be opened manually (e.g., by manually turning a key and moving the handle) or, in some examples, automatically from a remote location.
  • some determination is typically made that a user is allowed access to the secured space (e.g., the user enters some code that is verified as being authentic) and then the lock is actuated. After the lock is actuated, the door is opened and the user accesses the secured space.
  • packages are delivered to residents of apartment buildings.
  • a delivery person from a delivery service typically drops off a group of packages at the front desk of the apartment building where the packages are stored.
  • the recipient of the package returns to the apartment building, they can ask an attendant at the front desk for any packages that have been delivered during the day.
  • the delivery person may leave a note at the recipient's door indicating that delivery was attempted and reminding the recipient to pick up the package.
  • This delivery approach suffers from various problems. To mention one shortcoming, a human attendant is required to receive and sign for the package. This can be costly for many apartment buildings to provide. This delivery approach also relies on the presence of the human attendant and/or the recipient to complete the delivery process. More specifically, the attendant has to retrieve the packages to give to the recipient. The packages are often unsorted and the attendant has to take time to find the correct package once the recipient arrives.
  • the recipient often has to periodically check to see if there are any packages waiting for them at the front desk.
  • the packages are often in an unsecured location which is susceptible to unauthorized entry and package theft.
  • Package theft is a very common form of delivery theft, especially in locations where packages are not secured in a locked location until recipient pick-up. Records of package delivery, if they are maintained at all, are often hand- written and prone to error. Consequently, efficient management of package deliveries is difficult or impossible to achieve.
  • many different types of spaces need to be secured from unauthorized entry. For example, garages, rooms, and offices are often secured. However, there are often much smaller areas within these larger spaces that need protection. For example, in a hospital different cabinets within the same room or facility may secure tissue, medicine, and surgical instruments.
  • micro-areas sometimes referred to as "micro-areas” or “micro-spaces”
  • micro-spaces often need varying levels or different types of protection.
  • different personnel may have differing levels of access to different spaces.
  • file clerks may have access to some cabinets (e.g., cabinets containing hospital records) while only doctors and nurses have access to others (e.g., cabinets containing medicine or human tissue).
  • others e.g., cabinets containing medicine or human tissue.
  • the environmental conditions at the secured space must be carefully monitored and controlled.
  • the temperature of the cabinets holding the medicine or human tissue typically needs to be maintained at predetermined levels, or the contents of these cabinets may become destroyed or become otherwise un-usable.
  • Previous approaches have proved inadequate for both controlling access to and managing conditions of small, micro-areas.
  • this invention provides a method for controlling access for a storage enclosure, the method including the steps of:
  • the invention also provides a system for controlling access to a storage enclosure secured by a closure, the system including a processor configured to transmit an access code to a recipient upon delivery into the enclosure of an item for the recipient, recognize the access code input by the recipient and allow the recipient access to the enclosure by releasing the closure.
  • the storage enclosure is a locker which optionally forms part of an array of lockers, each having one or more walls and an opening defined by at least one of the walls, a closure for the opening and a fastener for the closure.
  • the enclosures may be of the same size and shape or may differ in size and/or shape.
  • the closure is preferably a flap or door fitting the opening, but may take other forms.
  • the closure may be a drawer.
  • the item may be anything capable of delivery. In the description below, the item is often referred to as a packaged asset, but is not necessary that the item is actually packaged.
  • a user interface for input of the access code maybe located on the front of each enclosure or there may be one user interface servicing a plurality of enclosures, located, for example, in the vicinity of the plurality of enclosures.
  • the user interface may take any suitable form but preferably is in the form of a keypad or computer touch screen.
  • the interface will prompt the user as to the enclosure that is to be accessed.
  • a visual indicator if present, may light up or change colour or blink to help the user identify the correct enclosure.
  • a signal may be sent to unlock the closure and allow the user access into the enclosure.
  • access to one or more secured areas is controlled. These spaces may be relatively large spaces (e.g., rooms, factories, or laboratories to mention a few examples) or micro-spaces (e.g., cabinets or lockers within these large areas to name two examples).
  • various control and management functions associated with these areas may be integrated together into one integrated server. For example, access control, event logging, environmental monitoring, and other functions may be integrated using a single server.
  • access to one or more storage areas is controlled.
  • An indication that a packaged asset is available for delivery to an intended recipient, an indication of a size of the asset, and an identity of the intended recipient are received.
  • An available storage space is determined based at least in part upon the size and/or weight of the asset and the identity of the intended recipient.
  • an access code is transmitted to the intended recipient allowing the intended recipient to access the available storage space using the access code.
  • a real-time determination of the identity of a storage space may be made.
  • the available storage space may be a storage space that is not currently being used by the recipient. In other aspects, the available storage space may be a storage space that is currently being used by the recipient.
  • the available storage space may be a storage space that is being shared by the recipient with another user.
  • the access code may be used to access the available storage space and retrieve the packaged asset from the storage space.
  • a visual indicator may be deployed to identify the available storage space to the recipient so that the recipient can easily locate the space.
  • the closure securing the available storage space may be pushed to open the storage space to the recipient.
  • the closure may be opened automatically (i.e., it may swing outward) upon receiving the access code.
  • the closure may be any type of device or structure used to control access to a secured area.
  • the closure may be a swinging door, gate, garage dooT, or sliding door to mention a few examples.
  • an electronic log of received packaged assets and intended recipients may be maintained.
  • the log is accessible to a system administrator at substantially all times. This log may also maintain details of internal factors within the storage space, such as weight, temperature, and other environmental factors.
  • the access code may be transmitted by the recipient in a variety of different ways.
  • the access code is transmitted to the intended recipient via email.
  • the access code is transmitted to the recipient over a wireless connection.
  • the access code may be transmitted on a set or possibly delayed schedule depending upon the user's needs. Access codes may also be encrypted upon transmittal. Other examples of transmission approaches are possible.
  • the access code may be a number, letters, a combination, other symbols, or any other suitable identifier.
  • the access code is a bar code which can be transmitted to the recipient's cell hone, for example and read by a bar code reader on the system. Other forms of access code are possible.
  • the access code is a cell phone number of the recipient.
  • the deliverer may contact the cell phone in order to transmit the access code or the system itself may contact the cell phone. In either case, the system stores the cell phone number as the access code. Contact may be by sms or voice message, for example.
  • the cell phone message may include the address of the enclosure if this is not already known to the recipient.
  • the recipient approaches the enclosure (which may be part of an array) and calls a telephone number of the system from the recipient's cell phone. This system number is preferably clearly displayed on the enclosure or nearby, for example, on a banner at the top of the array.
  • the system is configured to recognize the recipient's cell phone by its telephone number (access code) and allow the recipient access to the enclosure. For security, direct contact from the recipient's cell phone may be required.
  • the method and system of the invention may be embodied in a relatively simple way combined with social networking, such as that facilitated by Facebook.
  • a person may wish to provide a gift for one or more friends, using an array of enclosures according to the invention.
  • the person may deposit the gift or gifts in one or more enclosures and transmit an access code to each of the friends via Facebook.
  • Each friend then accesses the enclosure and the gift using the assigned access code.
  • This embodiment may be particularly effective if the access code is the cell phone number of each riend, as described above.
  • the recipient may pay for the storage space. For example, the recipient may pay a predetermined cost for a predetermined time period allowing them access to the space during that time period, pay higher costs for certain time periods, or pay higher costs for additional features (e.g., special indicator arrangements, additional electronic reminders, and so forth).
  • additional features e.g., special indicator arrangements, additional electronic reminders, and so forth.
  • the storage space may be mobile and can be moved from one location to another easily.
  • the storage space may be on wheels or other suitable means to move the storage space. Other examples of approaches the provide mobility are possible.
  • the invention provides a method for managing secured storage spaces, including the steps of monitoring the spaces via sensors, receiving a request from a user to access one of the secured spaces, determining whether to permit access to the space as requested by the user and allowing or refusing access to the space.
  • the invention in this second aspect may include the further step of logging activity with respect to the spaces.
  • the invention also includes a system for managing secured storage spaces, which enable the method of the second aspect of the invention.
  • the system for controlling access to or managing one or more storage spaces includes an interface and a processor.
  • the interface has an input and an output.
  • the interface is configured to receive at the input an indication that a packaged asset is available for delivery to the intended recipient, an indication of the size (e.g., dimensions or general size) of the packaged asset, and the identity of the intended recipient.
  • the processor is coupled to the interface and is configured to determine an available storage space based at least in part upon the asset size and the identity of the intended recipient.
  • the processor is further configured, when a storage space is determined to be available for. the packaged asset, to transmit an access code to the intended recipient at the output of the interface allowing the intended recipient to access the available storage space using the access code.
  • the available storage space may be in one of several usage states with respect to the recipient.
  • the available space may not be currently used by the recipient, may be currently used by the recipient, or may be currently shared by the recipient with another user.
  • a system for controlling access to one or more storage spaces includes a local network and a plurality of locking arrangements communicatively coupled to the local network. Each of the plurality of locking arrangements secures a storage space.
  • the system also includes a data entry device that is coupled to the local network; a wide area network that is coupled to the local network; and a system controller that is coupled to the wide area network.
  • the data entry device is configured to receive an indication that a packaged asset is available for delivery to an intended recipient, an indication of the asset size, and the identity of the intended recipient.
  • the system controller is configured to determine an available storage space based at least in part upon the asset size and the identity of the intended recipient received from the data entry device via the wide area network.
  • the system controller is further configured, when a storage space is determined to be available for the packaged asset, to transmit an access code to the intended recipient via the wide area network.
  • the intended recipient can use the access code to open the locking arrangement that secures the available storage space and obtain the packaged asset.
  • the wide area network may be one or more networks such as the Internet, a cellular wireless network, and the plain old telephone system (POTS).
  • networks such as the Internet, a cellular wireless network, and the plain old telephone system (POTS).
  • POTS plain old telephone system
  • the local network may be a network such as a campus- wide network; a network covering a building or portions thereof; or a network covering an office or portions thereof. Other examples are possible.
  • “local network” refers to a network (or combination of networks) that are limited in geographic scope to a local area such as a building, apartment complex, campus, military base, or the like.
  • a local network provides less geographic coverage than a wide area network (that, for example, covers states or countries) such as the Internet.
  • the available storage space is secured with a first locking arrangement disposed at a first end of the storage space and a second locking arrangement disposed at a second end of the storage space.
  • the access code unlocks one of the first locking arrangement or the second locking arrangement.
  • the data entry device may be a device such as a touch screen device, a personal digital assistant, a cellular phone, or a personal computer. Other examples of data entry devices are possible.
  • micro-areas may be provided.
  • these approaches can provide protection for micro-areas from both unauthorized human interaction and adverse environmental conditions (e.g., temperature variations, pressure variations, and so forth).
  • adverse environmental conditions e.g., temperature variations, pressure variations, and so forth.
  • Monitoring and reporting of activities may also be provided.
  • the integrated approaches to secured space management described herein frequently use a single hardware and/or software platform to manage control the one or more secured areas. Since a single hardware software platform is used (as opposed to previous approaches where unconnected and disparate elements were frequently deployed), the design of the system is simple and stream-lined, operation is simple, and access to system elements (e.g., software modules) by users is easy. Further, maintenance can easily be accomplished and updates to the system are easy to achieve.
  • the single integrated approach allows modularity to be accomplished. That is, new software modules can easily be loaded into the server, updates to existing modules can be easily and quickly made, and problems with individual modules can be easily identified and corrected. Different modules can be used in different environments allowing custom solutions to be easily configured and deployed.
  • FIG. 1 is a block diagram showing a system for packaged asset delivery according to various embodiments of the present invention ;
  • FIG. 2 is a flowchart showing an approach for controlling access to a secured area according to various embodiments of the present invention
  • FIG. 3 is a block diagram showing an apparatus for controlling access to a secured area according to various embodiments of the present invention
  • FIG. 4 is a block diagram showing a system for controlling access to one or more secured areas according to various embodiments of the present invention
  • FIGs. SA-D are flowcharts showing an approach for controlling access to one or more secured areas according to various embodiments of the present invention.
  • FIG. 6 shows one example of a series of display screens displayed during package drop off according to various embodiments of the present invention
  • FIG. 7 shows one example of a series of display screens displayed during package pick-up according to various embodiments of the present invention.
  • FIG. 8 is a block diagram of a system for managing one or more secured spaces according to various embodiments of the present invention.
  • FIG. 9 is a block diagram of another example of a system for managing one or more secured spaces according to various embodiments of the present invention.
  • FIG. 10 is a block diagram of server architecture for managing one or more secured spaces according to various embodiments of the present invention.
  • FIG. 11 is a block diagram of server architecture for managing one or more secured spaces according to various embodiments of the present invention.
  • FIG. 12 comprises a message flow diagram of one example of a message flow in a bridge registration process according to various embodiments of the present invention
  • FIG. 13 comprises a message flow diagram of one example of a message flow for a bridge discovery process according to various embodiments of the present invention
  • FIG. 14 comprises a message flow diagram of one example of a message flow for a opening process a locking device according to various embodiments of the present invention
  • FIG. 15 comprises a message flow diagram of one example of message flow for a locking process according to various embodiments of the present invention.
  • FIG. 16 comprises a message flow diagram of one example of message flow foT an unlocking process according to various embodiments of the present invention
  • FIG. 17 comprises a message flow diagram of one example of message flow for an unlocking process using a card reader according to various embodiments of the present invention.
  • FIG. 18 comprises flowcharts of example server logic flows according to various embodiments of the present invention.
  • the system includes a locker system 102, a network hub 104, an interface controller 106, a data entry device 108, a network 1 10, memory storage 1 12, and an asset manager 1 14.
  • the locker system 102 is any type of storage arrangement where one or more storage spaces are secured by one or more locking arrangements.
  • Each of the lockers has a locking arrangement (e.g., an electronic lock) that is communicatively coupled to the hub 1 4.
  • the locking arrangements are actuated by reception of an access code that opens/releases the locking arrangement so as to allow a barrier securing the storage space to be opened thereby allowing access to the storage space.
  • only one locking arrangement 105 is identified in FIG. 1 although it will be appreciated that each locker has a locking arrangement.
  • the locking arrangement 105 may be coupled to the hub 104 by any type of connection such as wired connection, wireless connection, and optical connection to mention a few examples.
  • the lockers may have one or more environmental control devices 107 that control, adjust, or otherwise affect one or more environmental or physical conditions within the locker.
  • the environmental control device 107 may adjust lighting, temperature, pressure, or any other condition within the locker.
  • the environmental control device 107 may be a fan, light, air conditioner, freezer unit, or heating unit. Other examples are possible. Control of the environmental control device 107 may be accomplished from the asset manager 114 or the interface 108. For example, conditions within the locker may be monitored (e.g., via sensors) and commands may be issued from the asset manager 1 14 or the interface 108 to operate the environmental control device 107 and maintain various conditions within the locker within predetermined limits.
  • the network hub 104 is any type of network hub that connects the many connections from the locker system 102 to a single output connection coupled to the interface controller 106.
  • the hub 104 may also provide for power distribution to the locker system 102.
  • the interface controller 106 is an interface connection that converts signals from one communication protocol to another.
  • the controller 106 converts signals between a USB-typc protocol and the RS- 85 protocol.
  • Other communication protocols and other types of conversions can also be used.
  • the data entry device 108 is any type of data entry device.
  • the data entry device may be a device such as a touch screen device, a personal digital assistant, a cellular phone, and a personal computer. Other examples of data entry devices are possible. In the example of FIG. 1, the data entry device is a touch screen device.
  • the network 110 is any type of computer network including any type of local network, micro network, or wide area network. Combinations of these networks may also be used.
  • the wide area network may be one or more networks such as the Internet, a cellular wireless network, or the plain old telephone system (POTS). Other examples of wide area networks are possible.
  • POTS plain old telephone system
  • the local network may be a network such as a campus- ide network; a network covering a building or portions thereof; or a network covering an office or portions thereof, Other examples of local networks are possible.
  • the memory storage 1 12 may be any type of memory storage device used to store information regarding the locker storage 102. For example, logs describing assets that were delivered and/or intended recipients may be stored in the memory storage 1 12.
  • the asset manager 1 1 may be any combination of hardware software that manages information related to the locker system 102 and the available storage spaces in the locker system 2. It may generate reports of available space, usage, and so forth. These reports may be stored in the memory storage 112 or communicated to an administrator (or others) for viewing via the network 1 10.
  • a delivery person delivers a packaged asset and enters an indication that a packaged asset is available for delivery to an intended recipient at the device 108.
  • the delivery person may provide the packaged asset to another person (e.g., an attendant at the front desk of an apartment complex) and that person may perform the packaged asset delivery actions described below.
  • the packaged asset as described herein may be a package (large, small, medium, oversized), an envelope, or any other type of package/enclosure.
  • the delivery person also enters an indication of a size of the asset and an identity of the intended recipient at the device 108.
  • the size may be a general size (e.g., large, small, medium, oversized) or may be one or more dimensions (or a weight).
  • the device 108 determines an available storage space in the lockers 102 based at least in part upon the size of the asset and the identity of the intended recipient.
  • an access code is transmitted from the device 108 to the intended recipient via the network 1 10 allowing the intended recipient to access the available storage space using the access code.
  • the access code in one example, is a randomly generated number.
  • the locking arrangement 105 of the locker system 1 12 may be programmed to accept this access code and allow this access code to open the locking arrangement 10S.
  • the asset manager 114 may create and maintain a log of transactions and store these in memory storage 1 12.
  • the recipient may go to the device 108, enter the code, and thereby access the packaged asset in the assigned locker.
  • the access code may actuate a locking arrangement that allows or causes a barrier (e.g., a locker door) to be opened.
  • the code entered by the recipient may be compared to a list of acceptable codes at the device 108.
  • An indicator 101 may alert the user as to the correct locker.
  • the indicator may be an LED in one example.
  • the color of the indicator may change depending upon the state of the secured space. For example, one color may be used when the locker is closed, another color (or another action such as the indicator flashing) when the recipient accesses the space, and still another color when the secured space is opened.
  • the available storage space in the lockers 102 is secured with a first locking arrangement disposed at a first end of the storage space and a second locking arrangement disposed at a second end of the storage space.
  • the access code unlocks one of the first locking arrangement or the second locking arrangement. This allows a delivery person to use one door to access the storage space and the recipient to use a second door to access the same space.
  • these doors may be disposed opposite to each other.
  • the door of the locker 102 securing the available storage space may be pushed once the code allows access. This prevents the door flying open and causing potential injury to the recipient. Alternatively, the door may be opened automatically upon receiving the access code.
  • an indication that a packaged asset is available for delivery to an intended recipient is received.
  • a delivery person may enter this via a touch screen or some other data entry device.
  • at least some of this information may be scanned in (e.g., scanning an RFID tag).
  • an indication of a size of the asset is received.
  • a delivery person may enter this information via a touch screen or some other data entry device.
  • an identity of the intended recipient is received.
  • at least some of this information may be scanned in (e.g., scanning an RFID tag).
  • a delivery person may enter this information via a touch screen or some other data entry device.
  • at least some of this information may be scanned in (e.g., scanning an RFID tag).
  • an available storage space is determined based at least in part upon the size of the asset and the identity of the intended recipient. For instance, a determination may be made if a space is available and the identity of that space. If there is no available space, at step 210 a report/message is sent to the recipient and/or the system administrator. At step 212, when a storage space is determined to be available for the packaged asset, an access code is transmitted to the intended recipient allowing the intended recipient to access the available storage space using the access code.
  • the available storage space may be a storage space that is not currently being used by the recipient. In other aspects, the available storage space may be a storage space that is currently being used by the recipient. In still other aspects, an available storage space may be a storage space that is being shared by the recipient with another user.
  • the access code may be used to access the available storage space and retrieve the packaged asset from the available storage space.
  • a visual indicator e.g., LED
  • This indicator may also be used during the package delivery process to indicate to the agent the location of the storage space where to store the packaged asset.
  • an electronic log of received packaged assets and intended recipients may be maintained.
  • the log is accessible to a system administrator at substantially all times.
  • the access code may be transmitted to the recipient at step 212 in a variety of different ways.
  • the access code is transmitted to the intended recipient via email across the Internet.
  • the access code may be sent to a cellular phone or personal digital assistant of the user via a wireless network. Other examples of delivery approaches are possible.
  • the recipient may pay for the storage space.
  • the recipient may the same cost for a predetermined time period, pay higher fees for certain time periods (e.g., for use during the Christmas holidays to mention one example), or pay higher fees for additional features (e.g., a higher number/frequency of reminder emails).
  • the apparatus 300 includes an interface 302 and a processor 304.
  • the interface 302 has an input 301 and an output 303 and is configured to receive a the input 301 an indication 306 that a packaged asset is available for delivery to an intended recipient, an indication 308 of asset size, and an identity 310 of the intended recipient.
  • the processor 304 is coupled to the interface 302 and is configured to determine an available storage space based at least in part upon the asset size 308 and the identity of the intended recipient 310.
  • the processor 304 is further configured, when a storage space is determined to be available for the packaged asset, to transmit an access code 312 to the
  • the available storage space may be a space that is not currently being used by the recipient, currently being used by the recipient, or currently being shared by the recipient with another. Other examples and combinations of storage usage patterns are possible.
  • the processor 304 is further configured to maintain a log 311 of received packaged assets and the intended recipients in a memory storage device 314.
  • the log 311 in the memory storage device 314 is accessible to a system administrator at substantially all times.
  • the output 303 is coupled to an Internet connection and the access code 312 is transmitted to the recipient in an email via the Internet connection.
  • the processor 304 is further configured to receive a payment from the recipient for use of the available storage space via the input 301 of the interface 302.
  • the apparatus includes a touch screen 315 that is coupled to the processor 304.
  • the touch screen 315 allows a delivery person (or attendant) to enter delivery information (e.g., that a package is available, the package size, and/or the intended recipient).
  • the screen 315 also provides an interface for the package recipient to enter the access code the retrieve the packaged asset.
  • the memory 314 may also store a list of possible recipients that can be displayed on the screen 315.
  • the input 301 and output 303 may be coupled to the locking arrangements and to other networks/network elements.
  • the apparatus 300 may be a wide variety of devices.
  • the apparatus 300 may be a touch screen device.
  • the apparatus 300 may be a personal computer and the screen 315 may be disposed at a personal computer.
  • FIG. 3 may be housed in a single and compact housing unit that can be located near a storage center (e.g., a locker
  • the apparatus 302 may be disposed in compact areas. However, some or all of the elements may be moved to other and separate locations (e.g., to a system controller that controls locking arrangements via a wide area network).
  • the system 400 includes a first local network 402 and a plurality of locking arrangements (e.g., electronic locks) at lockers 406. These locking arrangements are communicatively coupled to the first local network 402. Each of the plurality of locking arrangements 406 secures a storage space.
  • a data entry device (e.g., touch screen) 404 is coupled to the local network 402.
  • a wide area network 422 is coupled to the local network 402 and a system controller 424 is coupled to the wide area network 422.
  • the local network 402, touch screen 404 and lockers 406 may be disposed in a first building 408.
  • a second local network 410 is coupled to locking arrangements at lockers 414, locking arrangements at storage facility 416, locking arrangements at storage facility 418, and a data entry device 421.
  • Each of the lockers 414, storage facility 416, and storage facility 418 includes individual secured storage areas (e.g., lockers) that are secured by one or more of the respective locking arrangements.
  • the data entry device (e.g., a touch screen device) 421 is coupled to the local network 410.
  • the local network 410, data entry device 421, lockers 414, storage facility 416, and storage fiacilit 418 may be in a second building 412.
  • the data entry devices 404 and 421 are configured to receive an indication that a packaged asset is available for delivery to an intended recipient, an indication of asset size, and an identity of the intended recipient. For example, a delivery person or attendant may enter this information via the particular data entry device 404 or 421.
  • the system controller 424 is configured to receive this information (that is transmitted to the controller 424 via the local area networks 402 or 410, and the wide area network 422) and determine an available storage space based at least in part upon the asset size and the identity of the intended recipient.
  • the system controller 424 is further configured, when a storage space is determined to be available for the packaged asset, to transmit an access code to the intended recipient via the wide area network 422.
  • the access code may be emailed to the intended recipient, or sent to the recipient's cellular phone or personal digital assistant.
  • the intended recipient can use the access code to open the locking arrangement securing the available storage space and obtain the packaged asset. More specifically, the recipient may go to the data entry device 404 or 421 and enter the code.
  • the wide area network 422 may be one or more networks such as the Internet, a cellular wireless network, or the plain old telephone system (POTS). Other examples and combinations of wide area networks are possible.
  • networks such as the Internet, a cellular wireless network, or the plain old telephone system (POTS).
  • POTS plain old telephone system
  • the local networks 402 or 410 may be networks such as campus-wide networks, networks covering a building or portions thereof or networks covering an office or portions thereof. Other examples of local networks are possible.
  • the available storage space is secured with a first locking arrangement disposed at a first end of the storage space and a second locking arrangement disposed at a second end of the storage space.
  • the access code unlocks one of the first locking arrangement or the second locking arrangement.
  • the data entry devices 404 or 421 may be a device such as a touch screen device, a personal digital assistant, a cellular phone, and a personal computer. Other examples of data entry devices are possible.
  • the unctions of the controller 424 may be moved to the data entry device 404 or 421.
  • the code-generating function in the controller 424 may be moved to the touch screen 404 or 421.
  • all functions are moved and the system controller need not be used.
  • the data entry devices 404 and/or 421 may be moved to he coupled to the locking arrangements without being coupled to an intervening local network.
  • a log of recipients, drop off times, and recipients may be maintained at a memory 426 that is coupled to the controller 424.
  • Other types of information and other types of reports may be generated at the system controller 424 and stored at the memory 426.
  • FIGs. 5A-D one example of an approach for controlling access to one or more secured areas is described. It will be appreciated that this example illustrates approaches particularly useful for an apartment building with a locker system. It will also be appreciated that the steps described for this particular example may be changed to suit the needs of the particular user and/or system. It will also be understood that the steps be applied, changed, or otherwise modified to suit the particular needs of other deployment environments or locations.
  • the process begins when a delivery truck (or other vehicle) delivers packages to the front desk of the apartment complex at step 502.
  • An attendant at the front desk signs once for all packages. Alternatively, the attendant may be omitted and the delivery person can perform the delivery steps.
  • the attendant at the front desk can reject the package and return the package to the delivery person. In this case, the packages can be returned immediately or at a later time.
  • the front desk attendant acts as a delivery agent and moves the packages to the mail room (or other location where the lockers are physically located).
  • the delivery agent drops off the packages at the locker system. There need be no dedicated employee at the locker system to receive the packages. However, all employees may act as an agent for drop off as needed.
  • the package drop-off process begins.
  • the agent may begin at either step 512 or 514.
  • an agent "badges-in" with an RFED card.
  • a card presented by the agent is read by an RF1D reader device and a determination is made if the agent is a legitimate agent.
  • Control continues at step 516, where it is determined if the RFID badge is accepted. If the answer at step 516 affirmative, then execution continues at step 522. If the answer at step 516 negative, execution continues at step 514.
  • the "agent" option is selected at the keypad. For example, the agent presses an icon on the touch screen to provide this option.
  • the agent enters login (e.g., user name information) and a password and it is determined if the login information has been accepted. If the answer is negative at step 518, control returns to step 514. If the answer is affirmative at step 518, control continues at step 520 where it is determined if the password is accepted. If the answer at step 520 is negative, execution continues at step 514. If the answer at step 520 is affirmative, execution continues at step 522 where the agent selects options for "drop off,” "packages” or "log off.” If "log-off' is selected, then control returns to step 514. Otherwise control continues at step 524,
  • step 524 the "drop-off' option is selected and one or more of the apartment number, first name, and second name are filled in at the touch screen by the agent. Two paths, one beginning at step 526 and the other with step 528, may be followed.
  • the agent enters the apartment number.
  • the apartment number is alphanumeric.
  • a user list may also auto filter as the apartment number is entered (such that as particular characters are entered, entries with those characters are displayed).
  • the apartment number is selected (or step 532 is followed where the user is selected from a list).
  • the primary resident of the apartment may be selected automatically. Execution continues at step 538.
  • step 528 the agent enters the recipient's name. Auto- filtering may also occur at this step.
  • step 532 the user may be selected from the user list.
  • step 536 it is determined if the user is on the list, If the answer is negative, control returns to step 530. If the answer is affirmative, control continues at step 538.
  • the package size is selected by the agent.
  • Some package size options include envelope, small, medium, large or oversize. Alternatively, dimensions and/or weights can be entered. Other options are possible.
  • step 540 package is placed somewhere besides the lockers.
  • step 541 the screen flow jumps to show confirm drop-off that is high-lighted. Control continues at step 564.
  • step 542 it is determined if the resident already has a package of the same size or larger that has been recorded by the system as being stored in the lockers. If the answer is negative, at step 548, it is determined if there are any empty lockers. At step 552, an empty locker is opened and control continues at step 554. If the answer at step 542 is affirmative, at step 544 it is determined if the locker is foil. If the answer is negative, execution continues at step 550 and if the answer is affirmative, control continues at step 546,
  • step 550 the recipient's unfilled locker is opened and the package can be placed there by the agent. Execution continues at step 554.
  • step 546 it is determined if the resident has another assigned locker that is not full, If the answer is negative, execution continues with step 548. If the answer at step 546 is affirmative, execution continues at step 550.
  • step 554 it is determined if the package fits in the locker. In this respect, the agent may attempt to fit the package into the locker. If the answer is negative at step 554, at step 556 the agent closes the door of the locker without placing the package in the locker. At step 558, the agent may be provided the option to set the locker state as "full.” At step 560, the screen may display "open next locker.” Execution then continues at step 542 as described above.
  • step 562 the agent closes the locker with the package placed in the locker.
  • step 564 a "Confirm drop off is displayed on the screen. The expiry time for all packages in this locker for this resident is reset to begin expiring from when the latest package that has been dropped off.
  • step 566 it is determined if there is another package to drop off. If the answer is affirmative, control returns to step 538. If the answer is negative, at step 568 an email notification (or other type of notification) is sent to the resident. The drop-off process is now complete.
  • step 570 the resident enters the code that they have been provided.
  • step 571 it is determined if the code is accepted. This acceptance may be accomplished by comparing the code to a set of authorized codes (stored at the touch screen device in one example). If the answer is negative, control continues at step 570 and execution continues as has been described above. If the answer at step 571 is affirmative, then at step 572 the screen shows instructions for the user to follow, for example, to identify a particular locker (or lockers) associated with the code when the user has been assigned multiple lockers.
  • step 573 it is determined if the package is "oversize.” If the answer is affirmative, at step 583 the recipient goes to the agent and at step 582 the office hours of the agent may be determined by the recipient. At step 582, the agent gives the "oversize" package to the recipient and at step 583 agent clears the package from the system.
  • the locker indicator begins to flash orange (or some other appropriate color).
  • the lock securing the locker is set to push-to-release mode.
  • the recipient moves to the locker indicated by the flashing light and pushes on the door.
  • the door opens and indicator shows "open” (for example, by displaying a different color and/or ceasing flashing).
  • the recipient has not opened the door within the time out period, so the indicator shows "closed” (for example, by displaying a particular color) and the lock-push-to-release mode is cleared.
  • the recipient is logged out and system logs failed to pick up transaction.
  • step 579 after the door opens and the indicator shows open, the user removes the packages.
  • the indicator shows "closed” and at step 580 the locker state is set to "clear.”
  • a transaction log is updated with picked up package and with the time.
  • step 581 it is determined if the user has another locker. If the answer is affirmative, step 570 is executed and control continues as described above. If the answer is negative, the resident leaves the locker area/ mailroom with the packages.
  • step 584 the administrative process begins. It will be appreciated that the functions and sequence of functions described here with respect to the administrative function can be varied according to the particular needs of the user and the system.
  • step 585 transaction logs are maintained.
  • step 586 daily transactions histories are emailed to the system administrator.
  • a package expiration time can be set by the administrator. This time is the time allowed by the system for the recipient to retrieve their package after a code is entered and/or after the package has been received.
  • an expiration warning may be emailed to the resident to prompt pick-up of the packages.
  • package expiration notice is mailed to the recipient.
  • the agent takes action to clear unclaimed packages rom the locker system.
  • FIG. 6 one example of touch screen displays presented to a drop-off agent is described.
  • a package is dropped off at a locker system by the agent.
  • the agent may be a delivery person, an attendant, or some other employee that is tasked with entering packages into the locker system.
  • the displays are presented as being touch-screen displays, other display or data entry units or devices (e.g., personal computers) can also be used.
  • this example involves the use of a locker arrangement, other storage areas can also be used.
  • the example displays presented here are examples only and their sequence, content, and number can be varied to meet the needs of a particular user or application.
  • the agent button is selected by the delivery agent from the home screen.
  • an agent login e.g., user name
  • an agent password is entered from the touch screen or the keypad. The password and user name are verified.
  • a drop-ofF option is selected on the touch screen in order to begin the drop-off process as described elsewhere herein.
  • the locker size is selected by the drop-off agent.
  • a recipient is selected from a list by the agent and "enter" is pushed on the screen by the agent.
  • a locker is opened by the application to allow the agent to place the package in the locker. Now, instructions are presented on the screen for the agent to scan the package, drop off the package, scan the door (to record the locker used), and close the door to the locker.
  • the agent presses the confirm scan button after all scanning has been completed.
  • the complete button is selected and pressed by the agent.
  • a message is displayed notifying the agent that an email (or other message) is sent to the recipient.
  • a message is also displayed "Would you like to drop off another package?" In this example, the agent presses "no.”
  • the home screen returns and another package can be dropped off.
  • FIG. 7 one example of screen presented to a recipient picking up packages is described. As with the example of FIG. 6, it will be appreciated that although the displays are presented as part of a touch-screen display, other display or data entry units or devices can also be used. In addition, although this example involves the use of a locker arrangement, other storage areas can also be used. Finally, the example displays presented here are examples only and their sequence, content, and number can be varied to meet the needs of a particular user or application.
  • the pickup button is selected from the home screen by the recipient.
  • a package is dropped off at a locker system by an agent and the recipient has arrived at the locker system to retrieve their packagers).
  • the recipient enters the pickup code that has been sent to them.
  • the locker door opens and the locker number is displayed on the touch screen.
  • an indicator at the actual locker may be activated to identify the locker to the recipient and make retrieval of the package easier.
  • the home screen returns.
  • the system 8100 includes a network 8102, a bridge 8104, and a radio frequency identification (RFID) reader device 8108. Coupled to the bridge 8108 are port links 8136 and 8138. Port link 8135 is coupled to port link 8138; port link 8134 is coupled to port link 8135; and port link 8132 is coupled to port link 8134. An electronic lock 8120 is coupled to port link 8132. An electronic lock 8122 is coupled to the port link 8134 and locking device 8124 is coupled to port link 8135. A locking device 8126 is coupled to port link 8136; locking devices 8128 and 8130 are coupled to port link 8138. A computing device 8106 is coupled to the network 8102.
  • RFID radio frequency identification
  • a sensor 8120 is coupled to port 8132; a sensor 81 12 is coupled to port link 8134; and a sensor 81 12 is coupled to port link 8135. Further, a sensor 81 16 is coupled to port link 8136; and a sensor 8118 is coupled to port link 8138.
  • the different locks and sensors protect various secured spaces 81 19, 8121, 8123 and 8125 from unauthorized entry and/or environmental concerns.
  • the secured space 8125 is protected by two locks 8128 and 8130, for example, each deployed on a separate door at each end of the secured space 8125.
  • the secured spaces are lockers.
  • the secured spaces are cabinets or other enclosures in a medical facility (e.g., a hospital).
  • the secured spaces are cabinets are other secured spaces in an office.
  • the secured spaces are different protected areas (e.g., safes, closets, or cabinets) is a home. Other examples of secured spaces are possible.
  • the secured spaces may have one or more environmental control devices 8109 that control, adjust, or otherwise affect one or more environmental or physical conditions within the locker.
  • the environmental control device 8109 may adjust lighting, temperature, pressure, or any other condition within the locker.
  • the environmental control device 8109 may be a fan, light, air conditioner, freezer unit, or heating unit. Other examples are possible.
  • Control of the environmental control device 8109 may be accomplished from the server 8107.
  • conditions within the locker may be monitored (e.g., via sensors) and commands may be issued from the server to operate the environmental control device 8109 and maintain various conditions within the locker within predetermined limits.
  • many of the secured spaces managed according to the approaches described herein are micro-areas or micro-spaces.
  • microspaces and micro-areas refer to spaces less in extent than a room (or some other space that is demarcated or separated from other areas in some way).
  • micro-spaces or micro-areas are less in area than larger spaces such as closed door offices, office cubicles, office areas that includes cubicle and open spaces, rooms or other areas in apartments or homes, storerooms, mailrooms, rooms in a retail stores, hospital rooms, or class rooms in schools.
  • the micro-spaces may be cabinets, closets, lockers, chests, boxes, or safes.
  • the micro-areas and micro-spaces may be disposed in different rooms or larger areas. For examples, in a hospital where the micro-spaces arc cabinets, the cabinets can be situated in different rooms within the hospital.
  • the network 8102 is any type of network that can transmit communications.
  • the network 8102 can be a local area network (LAN) or wide area network (WAN).
  • the network 8102 can also employ any type of communication technology (or combinations of these technologies).
  • the network can be a computer network, a cellular network, any other type of wireless network, the Internet, or any combination of these or other networks.
  • the bridge 8104 is any computer device that is configured to route messages to and from different locations.
  • the bridge 8104 is a TZ CenturionTM bridge manufactured by Telezygology, Inc. of Chicago, Dlinois. Other examples are possible.
  • Each bridge may be managed individually from a server, or otherwise part of a larger system.
  • the RFID reader 8108 is a device that is configured to read information from RFID cards that are swiped through the reader. These cards are associated with users.
  • the port links are the TZ CenturionTM RFID device manufactured by
  • Port links 8132, 8134, 8135, 8136 and 8138 are configured to provide a connection between the various locking devices and the network 8102 and one or more power sources.
  • the port links are the TZ CenturionTM Port Link manufactured by Telezygology, Inc. of Chicago, Illinois.
  • Electronic locks 8120 and 8122 are any type of electronic locking device.
  • the lock 8120 and 8122 is a compact, lightweight, high-load locking devices that use jaw locking mechanisms to capture and hold an inserted mating stud to secure a door.
  • the mechanism may be controlled by a Shape Memory Alloy (SMA) actuator which in turn is managed and controlled by a server 8107 as described herein.
  • Embedded intelligence may be provided at the locks 8120 and 8122 that enables networking, switching and the ability to control other devices and connect with smart objects such as sensors.
  • the locks 8120 and 8122 are TZ RadialTM locks manufactured by Telezygology, Inc. of Chicago, Illinois. Other examples are possible.
  • Locking devices 8122, 8124, 8126, and 8128 are also electronic locking devices.
  • these may be intelligent locking devices that offer drop-in replacements for legacy manual swing-handle data center cabinet locks.
  • These devices may integrate a high load Shape Memory Alloy (SMA) actuated locking mechanism with a touch-to-release option, a multi-color LED status indicator, manual key over-ride, electronic door status sensor, and a RJ-45 connector.
  • the devices are TZ SlideHandle devices manufactured by Telezygology, Inc. of Chicago, Illinois. Other examples are possible.
  • the locking devices 8122, 8124, 8126, and 8128 may also be managed and controlled by a server 8107 as described herein. It will also be appreciated that the devices 8120, 8122, s 8124, 8126, 8128, and 8130 may all be of the same type and that the configuration shown with respect to FIG. 8 is one example only.
  • Sensors 8110, 81 12, 81 14, 8116 and 8118 are any type of sensing device that are configured to sense any type of condition (e.g., environmental conditions, the presence of an object in a space, the dimensions of an object in a space, and so forth).
  • each sensor is a TZ SensorTM manufactured by Telezygology, Inc. of Chicago, Illinois that provides environmental monitoring at the cabinet enclosure level across a range of operating conditions such as temperature, humidity, door contact and/or leak detection to mention a few examples.
  • the computing device 8106 is any type of computing device that can be used to operate or 16 host the server 8107.
  • the computing device 8106 may be a personal
  • a server is located in the computing device 8106, However it will be understood that the server 8107 may be disposed at other locations (or multiple locations) as well.
  • the server 8107 at the computing device 8106 monitors environmental or other conditions of the spaces 81 19, 8121 , 8123, and 8125 via the sensors 8110, 8112, 81 14, 8116, and 8118;
  • the server 8107 receives requests from users to access the secured spaces 81 19, 8121 , 8123, and 8125 from users and manages access to these spaces.
  • the server 8107 may determine
  • the server 8107 also stores a log of activity with respect to the spaces 81 19, 8121 , 8123, and 8125 (and the locking arrangements used to secure these spaces) and may prepare various types of reports concerning these spaces and usagesi/activities related to these spaces.
  • the server 8107 also stores a log of activity with respect to the spaces 81 19, 8121 , 8123, and 8125 (and the locking arrangements used to secure these spaces) and may prepare various types of reports concerning these spaces and usagesi/activities related to these spaces.
  • the sensors 8110, 8112, 8114, 8116, and 8118 may determine when the certain conditions in or at the secured spaces exceed certain thresholds and take appropriate actions. For example, when the temperature as measured by a sensor at a secured space exceeds a threshold an alert may be issued to appropriate personnel so that the item can be removed from the space. In another example, another device (e.g., a fan or air conditioner) may be activated when a particular sensor detects that a temperature has been exceeded. In this way, an integrated approach (e.g., a single server providing all functions through one or more interfaces) for managing and controlling access to the secured spaces is provided. It will be appreciated that only a few of the possible server functions have been described and that as described elsewhere herein other functions are possible.
  • the system 9200 includes a first network 9202, a bridge 9204, and an RFID reader 9208. Coupled to the bridge 9208 are port links 9236 and 9238. A port link 9235 is coupled to port link 9238. A port link 9234 is coupled to port link 9235. A port link 9232 is coupled to port link 9234. An electronic lock 9220 is coupled to the port link 9232. An electronic lock 9222 is coupled to the port link 9234. A locking device 9224 is coupled to port link 9235. A locking device 9226 is coupled to port link 9236. Locking devices 9228 and 9230 are coupled to port link 9238. A computing device 9206 is coupled to the network 9202.
  • a sensor 9220 is coupled to the port link 9232.
  • a sensor 9212 is coupled to the port link 9234.
  • a sensor 9212 is coupled to port link 9235.
  • a sensor 9216 is coupled to the port link 9236 and a sensor 9218 is coupled to port link 9238.
  • FIG. 9 having like numbers with respect to similar elements of FIG. 8 (e.g., element 8110 corresponds to element 9210 and so forth) have been described above with respect to FIG. 1 and these descriptions will not be repeated again here.
  • the secured spaces are not shown in FIG. 9 although it will be understood that secured spaces of similar (or different) scope than those shown with respect to the example of FIG. 8 may be configured in the example of FIG. 9.
  • the system 9200 also includes a second network 9252, a bridge 9254, and an RFID reader 9258. Coupled to the bridge 9258 are port links 9286 and 9288. A port link 9285 is coupled to port link 9288. A port link 9284 is coupled to port link 9285. A port link 9282 is coupled to port link 9284. An electronic lock 9270 is coupled to the port link 9282. An electronic lock 9272 is coupled to the port link 9284. A locking device 9274 is coupled to port link 9285. A locking device 9276 is coupled to port link 9286. Locking devices 9278 and 9280 are coupled to port link 9288. A computing device 9256 is coupled to the network 9252.
  • a sensor 9260 is coupled to the port link 9282.
  • a sensor 9262 is coupled to the port link 9284.
  • a sensor 9262 is coupled to the port link 9285.
  • a sensor 9266 is coupled to the port link 9286.
  • a sensor 9278 is coupled to the port link 9288.
  • the elements associated with the second network 9252 are similar in configuration to like-numbered elements associated with the first network 9202 (e.g., element 9202 corresponds to element 9252 and so forth). Consequently, the description of these elements will not be repeated again here.
  • a third network 9240 is coupled to the bridges 9204 and 9254.
  • the network 9240 is, in one example, a network that operates according to the Internet Protocol (i.e., an IP network).
  • the network 9240 may be the Internet, Other examples of networks and other combinations of networks are possible.
  • the third network can be considered a wide area network while the networks 9202 and 9252 may be considered local area networks.
  • Coupled to the third network 9240 are a personal digital assistant 9241 , a laptop 9242, a personal computer 9244, and a tablet 9243.
  • the personal digital assistant 9241 is any type of personal digital assistant that may communicate with the network using, for instance, a wireless connection.
  • the laptop 9242 is any portable computer such as a laptop computer.
  • the personal computer 9244 is any computing device that is typically not mobile (e.g., a desk top computer).
  • the tablet 9243 is personal computing tablet as known to those skilled in the art.
  • Various applications are provided by some or all of the devices. These applications can be implemented or configured as software that operates at one or more of the devices 9240, 9241 , 9242, 9243, or 9244. These applications are scalable and modular in the sense that particular users can utilize some or all of the applications depending upon their particular need, requirement, budget, available bandwidth, or some other parameter or combination of parameters. Thus, the applications are scalable and easily interchangeable and modifiable as the needs of a particular user or system change over time.
  • the server application 9245 is any server application (e.g., a web service such as a Microsoft windows application) that supports execution or provides a software framework for any or all of the other software modules described herein.
  • server application e.g., a web service such as a Microsoft windows application
  • Database 9246 is any type of database where information is temporarily and/or permanently stored.
  • the database 9246 is a Microsoft SQL server,
  • Reporting analysis 9247 is a software module that manages data contained in the database 9246.
  • a facility management module logs all events associated with a particular space (e.g., the door opening or closing to the space, temperature data associated with the space, or pressure data associated with the space) and generates reports (or alarms) when predetermined thresholds are exceeded. Other reports can be generated over predetermined time periods and reported to authorized personnel (e.g., system administrators).
  • a web porta] module 9248 is any type of web client interface that allows a user to log into the system.
  • a unified messaging module 9249 is a module that sends alarms or notifications created by some of the other modules.
  • An access management module 9290 provides access control functions. For example, the module 9290 customizes permission to different users and/or associates different locking devices with different users. The module 9290 prevents access to the secured spaces by individuals merely passing through an area (e.g., individuals merely coming through the building). This function may be accomplished by deploying a card-based system (users are required to swipe the ID card) or biometric system or a log-in based system (where users log in through a computing device). Existing buildings service modules could also interface be integrated with the module 9290.
  • a facility management module 9291 is configured to provide temperature, pressure, or other environmental management for a facility.
  • a plant management module 9292 is configured to maintain plant equipment, schedule equipment operation, or provide other services related to the management of a plant.
  • a configuration management module 9293 is a software module that may be
  • a geographic information system module 9294 is a software module that allows the display of geographic information to a user.
  • the geographic features of the network may be displayable and these may be zoom-able on a display screen on any or all of the devices 9240, 9241 , 9242, 9243, or 9244.
  • a service level agreement module 9295 is a software module that is used to guarantee service levels to users.
  • the module9 295 guarantees that a particular space never exceeds a temperature of 75 degrees Fahrenheit.
  • the module 9295 may also report the temperatures of these spaces.
  • a micrometer on a computer may also be monitored to ensure the power level used by the computer does not exceed a predetermined level.
  • a customer billing module 9296 is a module that performs customer billing. In one example, customers may be charged different prices for different levels of service or access to different features.
  • a human resource management module 9297 is a software module that documents human interactions with the system or elements of the system. For example, the module 9297 may determine (through the use of various sensors) when a user logged in to the system, what assets the user used, and what the user did with these assets.
  • any of the modules described above may be deployed to provide various functions to any of the secured areas secured by the locking arrangements.
  • the first network 9202 may be disposed in a jewellery store and the various locks and locking arrangements are configured to control . cabinets for storage of specific types of jewellery, jewellery of specific values, or jewellery repair tools.
  • the modules described above allow access to some cabinets for some individuals, but not for other individuals. Access to the cabinets is monitored in real time and alerts alarms are issued as unauthorized individuals attempted to access some cabinets. Reports are also created and sent to the owner of the jewellery store regarding the access history (e.g., the individual who access the cabinet, when access occurred, and for how long) of the cabinets. The police or other authorities could be alerted under some conditions.
  • the second network 9252 is disposed in a hospital, and the various locks and locking arrangements control access to cabinets for specific types of medical instruments, medicines, and human tissue.
  • the modules described above allow access to some cabinets by some individual, but not for others. Access to the cabinets is monitored in real time and alerts/alarms issued as unauthorized individuals attempted to access some cabinets. Reports are also created and sent to the hospital administrator. Environmental conditions are monitored by the sensors and when predetermined conditions are exceeded, alerts issued or other actions taken. Polling is one approach that can be used to monitor conditions at various devices. Other approaches are possible.
  • the server 9239 may be disposed and operate on the personal computer 9244 and communicate over the network 9240 to the networks 9202 and 9252 and subsequently to the devices that monitor or control access to the various secured spaces.
  • the server 1300 interacts with a client 1302.
  • the client 1302 includes a client application 1304, isolated storage 1306, and a framework 1308.
  • the client application 1304 allows users to interact with the system.
  • the client application may provide login screens, login features, and so forth to present to a user allowing the user to login to the system, enter information, and access a secured space.
  • Various types of information may also be presented to the user.
  • the isolated storage 1306 is a memory storage area that is configured to data entered by the user or to be presented to the user.
  • the isolated storage 1 06 may be a Microsoft Silverlight-compliant storage area.
  • the framework 1308 is used to provide a software framework (e.g., generic procedures or functions) to the user.
  • the framework 1308 may be a Microsoft Silverlight-compliant framework.
  • the server 1300 includes a web services module 1322, a business layer 1324, a framework 1326, a transaction database 1328, a reporting database 1330, and a network framework 1332.
  • the web services module 1322 is configured to provide communication services with the client 1302 (for interaction with a user) and communicate with various bridges (for interaction with locking mechanisms, sensors, and so forth securing secured spaces). For example, the web-services module 1322 provides format conversions for
  • the business layer 1324 is where the server functions are performed (e.g., the modules of FIG. 9).
  • the framework 1326 is framework for the operation of the business layer 1324. For example, this may be a Microsoft Entity framework and provide generic functions and subroutines used to perform various functions.
  • the transaction database 1328 is a database for the temporary storage of data being processed at the server 1300.
  • the reporting database 1330 is permanent storage for data used by the server (e.g., device information and reports generated may be stored here).
  • the network framework 1332 is a framework for the operation of the server 1300.
  • this may be a Microsoft NET framework.
  • Messages 1318 are exchanged via a link 320 between the sever 1300 and the client 1302.
  • the messages 1318 are any type of messages.
  • Windows Communication Foundation -compliant (WCF) messages are used. Other examples are possible.
  • the communication link 1320 is any type of communication link.
  • the communication link 1320 uses XML protocol. Instructions are also exchanged via communication links 1315 and 1317 between the server 1300 and bridges 1314 and 316.
  • the communication links .1315 and 1317 are high security communication links. For example, these links may utilize an encryption technology.
  • the messages sent across links 1315 and 1317 may use any type protocol.
  • the bridges 1314 and 1316 are communication bridges as described herein. They interact with devices 1310 and 1312.
  • the device 1310 and 1312 may be locking devices, sensors, or combinations of these devices.
  • users access the server 1300 using the client 1302 which operates at a personal computer.
  • the client 1302 may be an RFID reader and the user swipes an access card through this device.
  • the server 1300 determines if access is allowed, the locking arrangement secured space to which access is allowed, and may open a locking arrangement (e.g., the devices 1310 and 1312) by sending messages to the locking device.
  • the server 1300 may monitor conditions at the secured spaces.
  • sensors may be deployed to monitor conditions.
  • the sensed information from the sensors may be sent the server 1300 via communication links 1315/1317.
  • the server 1300 determines if the sensed conditions are within predetermined limits. If the conditions are not within predetermined limits, the server 1300 may take action. For example, the server 1300 may create alert messages and transmit the alert messages to the client 1302 to be presented to the user.
  • the server 1300 may also generate reports and store these in the storage 1330 and/or present these to a user at the client 1302.
  • the server 2405 interacts with a presentation business layer 2402.
  • the layer 2402 includes a user interface 2404, isolated storage 2406, and a framework 2408.
  • the user interface 2404 allows users to interact with the system.
  • the interface 4204 may provide login screens, login features, and so forth to present to a user to allow the user to login to the system and access a secured space. In one example, this is a Microsoft Silver! ight-compliant application.
  • the isolated storage 206 is a memory storage area that is configured to data entered by the user or to be presented to the user.
  • the isolated storage 2406 may be a Microsoft Silverlight-compliant storage area.
  • the framework 2408 is used to provide a software framework (e.g., generic procedures or functions) to the user.
  • the framework 2408 may be a Microsoft Silverlight-compliant framework.
  • the server 2405 includes a business logic layer 2424, a transaction database 2428, a reporting database 2430, and a network framework 2432.
  • the business logic layer 2424 provides configuration management (e.g., the configuration of the predetermined environmental limits discussed herein).
  • the layer 2424 may also be configured to provide user/visit management (e.g., access to secured spaces); remote access and monitoring of the secured spaces; alarm logic (e.g., the logic to issue alarms when monitored conditions foil to meet predetermined thresholds; and cross-bridge coordination of micro-protection of secured spaces.
  • the transaction database 2428 is a database for storage of configuration information that may be used by the business rules in the Business Layer and the temporary storage of data being processed at the server 2405.
  • the reporting database 2430 is permanent storage for primarily historical data used by the server (e.g., reports generated).
  • the databases may be Microsoft SQL databases.
  • the network framework 2432 is a framework for the operation of the server 2405, For example, this may be a Microsoft NET 4.0 framework.
  • Messages 2418 are exchanged via a link 2420 between the sever 2405 and the presentation business layer 2402.
  • the messages 2418 are any type of messages. In one example, Windows Communication Foundation-compliant (WCF) messages are used. Other examples are possible.
  • WCF Windows Communication Foundation-compliant
  • the communication link 2420 is any type of communication link.
  • the communication link 2420 uses XML protocol. Instructions are also exchanged via communication links 2 15 and 2417 between the server 2400 and the bridges 2 14 and 2416.
  • the communication links 2415 and 2417 may be high security communication links.
  • the links 2415 and 2417 may utilize encryption technologies.
  • the messages sent across the links 2415 and 2417 may use any type of protocol.
  • the bridges 2414 and 2 16 are communication bridges as described herein. They interact with devices 2410 and 2412, which may be locking devices, sensors, or combinations of these devices.
  • users access the server 2405 using the layer 4202 at a personal computer.
  • the layer 2402 may be deployed at an RFED reader and the user swipes an access card through this device.
  • the server 4205 determines if access is allowed, the locking arrangement secured space to which access is allowed, and may open a locking arrangement by sending messages to the locking device.
  • the server 2405 may monitor conditions at the secured spaces. In this regards, sensors at the secured spaces may monitor conditions.
  • the sensed information may be sent to the server 4205 via the communication links 2415/2417.
  • the server 2405 determines if the sensed conditions are within predetermined limits. If the conditions are not within predetermined limits, the server 2405 may take action. For example, the server may create alarms and transmit the alarms to the client 2402 (or other locations) to be presented to the user.
  • the server 4205 may also generate reports and store these in the storage 2430 and/or present these to a user at the layer 2402.
  • the protocol uses HTTP POST and GET actions and the JSON and XML protocols to communicate.
  • the protocols typically require a host system to communicate with, but the bridge and the server host may both act as client or server depending on need.
  • the server may connect to a bridge as follows.
  • the host sends an authentication request to the bridge.
  • This request is an HTTP POST containing the usemame and password in the request body. If the username and password for the bridge were both "admin" the request body may, in one example, contain the URL encoded string:
  • the bridge confirms the credentials and reply with a session cookie named "key" that must be included in all future requests from the host to the bridge.
  • the host sends a registration message to the bridge. This message contains the hostname, port, and URL that serves requests from the bridge, in one example.
  • the registration message is sent as an HTTP POST request containing a JSON body.
  • the bridge responds to the registration message with a standard HTTP response.
  • the body of the response contains XML that indicates which configuration elements were successfully set or an error message if something went wrong.
  • the host acts as the HTTP client, and the bridge acts as an HTTP server.
  • the bridge sends an HTTP POST request to the host (server) at the URL and port specified in the configuration message.
  • the bridge is acting as an HTTP client.
  • This response contains various details about the bridge, including firmware version and serial number.
  • the bridge acts as a client whenever it needs to communicate with the host. This removes the need for the host to constantly poll each bridge that is registered with it. Certain events will cause the bridge to send information to the host. These events include but are not limited to the following: lock status has changed for a device (either locked or unlocked); an RFID tag was read by an RFID reader; a device was removed from the network or otherwise made unable to communicate; a device was returned to the network after being out of communication; and the device discovery process on the bridge was completed.
  • the bridge supports a command that will discover all of the devices attached to the bridge. When this command is finished running, the bridge will send a list of devices to the host. This list contains the device type and serial number for each device, Each device has an associated device descriptor file.
  • the descriptor file describes the available commands and configuration settings for a device type.
  • Bridge Registration events are events triggered whenever a host sends the registration message.
  • the registration message contains some information about the bridge sending the message, but another purpose is to establish two-way communication with the host (server).
  • Discovery Results events are triggered after the bridge has finished discovering attached devices.
  • the discovery results message contains the device type and serial number of each device found.
  • Status Update events are triggered when the state of a lock changes (this includes an error state that indicates a disconnected device). This event is also triggered by an RFE tag being scanned. A single status update can contain state information for all devices attached to the bridge (this will normally only happen immediately after discovery).
  • Stream events are triggered when the bridge can be configured to send periodic sensor value updates.
  • Stream update messages are used for logging and actions on the host (server) side, so they are sent regardless of changes to the sensor values.
  • a single stream update will include information from all devices attached to the bridge.
  • a server includes various modules (e.g., a hardware event handler, a card management service, a device communication service, a device repository service, a bridge management service) and that the server accesses memory (e.g., a database and a device repository).
  • modules e.g., a hardware event handler, a card management service, a device communication service, a device repository service, a bridge management service
  • memory e.g., a database and a device repository.
  • Action messages include a command and may be in the form ("Action":"Coramand”).
  • the command may be any command such as to open a lock, close a lock, and so forth.
  • Configuration messages may include an array of objects containing name/value pairs of new configuration settings. Any number of configuration options can be included, but the array may in some examples only contain elements that will be changed.
  • Status messages may retrieve status information for a device. It will be understood that the above are only example messages and that the actions, data, format, scope, or any other features of these messages may be changed to suit the needs of a particular application or system.
  • a bridge registration process is described.
  • authenticate message is sent from the user interface to the server.
  • an authenticate message is sent from the server to the bridge.
  • the server authenticates the request (or fails to authenticate) and sends either a pass or fail message to the server. If a failure, a fail message is sent from the server to the user interface.
  • a configure bridge message is sent from the server to the bridge.
  • configuration is accomplished and a configuration successful message is sent from the bridge to the server.
  • this event is recorded in the database.
  • a success message is sent from the server to the user interface.
  • the discovery process is started via a message from the user interface to the server.
  • the bridge serial number is obtained from a memory storage device.
  • a discovery request is formed and at step 4608 sent to the bridge.
  • the bridge sends a result to a hardware event handler.
  • discovery is complete and this is sent to the server.
  • device status is updated if the device is already in the directory. If the device is not in the directory at step 4616, an entry is created.
  • the device is added or updated in the directory.
  • an open locking device process is described.
  • an open lock request is sent from the user interface to the server.
  • the device serial number (for the bridge or locking device) is obtained from the device repository.
  • a message is sent from the server to the bridge to fire the lock open.
  • an action succeeded message is sent from the bridge to the server (at step 5708) or an action failed message is sent from the bridge to the server (at step 5710).
  • the device status is updated in the data repository.
  • a message is sent to an event management service at step 5712 that an opening action was attempted at a particular lock.
  • a lock request is sent from the user interface to the server.
  • a message is sent from the server to the bridge to lock. If the action fails, at step 806 a fail message is sent from the bridge to the server.
  • the device repository is updated as to the status of the lock.
  • a message is sent from the server to a bridge management service that a lock was attempted.
  • an unlocking process is described.
  • an unlock request is sent from the user interface to the server.
  • a check is made as to the unlock duration. If the unlocking duration is zero, then the lock is to be opened. If the unlock duration is not zero, a message is sent to a bridge management service and the status is recorded in the database.
  • an unlock request message is sent from the server to the lock. If the action fails, a fail message is sent from the bridge to the server at step 908.
  • the status of the lock is updated in the device repository and the data base.
  • the RFID reader sends a request to a hardware event handler to open a lock.
  • the serial number of the lock is obtained from the device repository.
  • the event handler sends the request to a card management service.
  • the device repository is updated.
  • server logic flows are described. It will be appreciated that this is one example of server logic and that other examples are possible.
  • a request to open a lock is received.
  • a determination is made as to the lock and bridge referred to in the request.
  • a message is formatted to the bridge to fire opening of the lock.
  • the message is sent to the bridge.
  • the device status is changed to unlocked.
  • the message is processed.
  • the new status is logged to the server database.
  • the database is updated.
  • the status is updated at the user interface showing the device is unlocked.
  • a stream of sensor data is received from the bridge.
  • new sensor values from the stream are logged to the database.
  • the approaches allow packaged assets to be delivered to a recipient securely and easily without the use of an intermediate human attendant.
  • the recipient is automatically informed of the delivery of the packaged asset and provided with an access code to open the secured area and retrieve the packaged asset.
  • Accurate records are automatically created and maintained to facilitate package tracking.
  • the recipient can retrieve the packaged asset without the need of a human attendant, The recipient can potentially retrieve the packaged asset at all hours of the day and night. Since the packaged assets are stored in a secured area, then and other such problems are substantially reduced or eliminated.

Landscapes

  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Lock And Its Accessories (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention porte sur un procédé pour contrôler l'accès à une enceinte de stockage (102). Lorsqu'un article est fourni à l'enceinte de stockage (102), un code d'accès est transmis à un bénéficiaire. Le code d'accès est accepté lorsqu'il est entré par le bénéficiaire, et un accès est autorisé à l'enceinte de stockage (102). L'invention porte également sur un système pour contrôler l'accès à une enceinte de stockage (102) sécurisée par une fermeture. Le système comprend un processeur (112) configuré de façon à transmettre un code d'accès à un bénéficiaire lors de la fourniture dans l'enceinte (102) d'un article pour le bénéficiaire, à reconnaître le code d'accès entré par le bénéficiaire et à permettre au bénéficiaire d'accéder à l'enceinte (102) par libération de la fermeture.
EP11824350.0A 2010-09-14 2011-09-14 Systèmes et procédés pour accéder à un espace de stockage sécurisé ou pour gérer celui-ci Ceased EP2616615A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US38269310P 2010-09-14 2010-09-14
US12/881,772 US8698596B2 (en) 2010-09-14 2010-09-14 Apparatus and method for accessing a secured storage space
PCT/AU2011/001177 WO2012034171A1 (fr) 2010-09-14 2011-09-14 Systèmes et procédés pour accéder à un espace de stockage sécurisé ou pour gérer celui-ci

Publications (2)

Publication Number Publication Date
EP2616615A1 true EP2616615A1 (fr) 2013-07-24
EP2616615A4 EP2616615A4 (fr) 2017-07-05

Family

ID=45830863

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11824350.0A Ceased EP2616615A4 (fr) 2010-09-14 2011-09-14 Systèmes et procédés pour accéder à un espace de stockage sécurisé ou pour gérer celui-ci

Country Status (5)

Country Link
EP (1) EP2616615A4 (fr)
CN (1) CN103210165B (fr)
AU (1) AU2011301771B2 (fr)
CA (1) CA2811317C (fr)
WO (1) WO2012034171A1 (fr)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
PL400838A1 (pl) * 2012-09-19 2014-03-31 Integer Społka Akcyjna Paczkomat modułowy
ES2538419B1 (es) * 2013-12-19 2016-04-26 Simón TASIS DAUPHIN Mueble taquilla refrigerado inteligente
US10204465B2 (en) 2014-06-30 2019-02-12 Ebay Inc. Handshake authenticated coded locked container
US10445773B1 (en) * 2014-11-05 2019-10-15 Dreamworks Animation L.L.C. Connected guest platform
DE102014119557A1 (de) 2014-12-23 2016-06-23 Deutsche Post Ag Fachanlage
EP3176761A1 (fr) * 2015-09-03 2017-06-07 Axis AB Procédé et appareil permettant d'augmenter la fiabilité dans des systèmes de surveillance
CN106934946B (zh) * 2015-12-31 2020-05-15 菜鸟智能物流控股有限公司 一种储物柜操作方法、信息发送方法、装置及系统
CN105678490A (zh) * 2015-12-31 2016-06-15 合肥格易集成电路有限公司 一种快递业务物联网技术处理系统和方法
GB201604868D0 (en) * 2016-03-22 2016-05-04 Bybox Holdings Ltd Automated locker system and method for delivery and collection of packages
CN107293064B (zh) * 2016-03-30 2021-07-09 菜鸟智能物流控股有限公司 自提柜操作方法、操作系统以及自提柜
CN106355714B (zh) * 2016-08-31 2019-08-13 郑成富 一种指纹锁具管理系统及方法
DE102016117387B4 (de) 2016-09-15 2019-03-07 Deutsche Post Ag Verfahren zur Absicherung einer Übergabestelle
US10832296B2 (en) * 2017-11-16 2020-11-10 Panasonic Intellectual Property Corporation Of America Transaction management system, transaction management method, and program
CN108122347A (zh) * 2018-01-03 2018-06-05 宝鸡九七科技传媒有限公司 智慧化无人社区服务云柜系统以及应用方法
CN108257301A (zh) * 2018-01-10 2018-07-06 杭州纳戒科技有限公司 物流系统的售货方法、售货物流系统以及电子设备
US10818117B2 (en) 2018-01-19 2020-10-27 Konnex Enterprises Inc. Systems and methods for controlling access to a secured space
WO2019243316A1 (fr) 2018-06-21 2019-12-26 Assa Abloy Ab Déverrouillage de verrou à distance
CN109215249B (zh) * 2018-08-30 2021-03-26 苏州中鑫自动化科技有限公司 一种快递寄、存智能一体机
EP3991069B1 (fr) 2019-06-27 2023-04-19 Carefusion 303 Inc. Ensemble contenant intelligent sécurisé, systèmes et procédés
GB2586141B (en) * 2019-08-06 2023-03-15 Poolpod Products Ltd Storage apparatus and associated methods
US11568693B2 (en) 2020-07-24 2023-01-31 Konnex Enterprises Inc. Systems, devices, and methods for controlling access to a secure space

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000051750A1 (fr) * 1999-03-05 2000-09-08 Jian Chen Systeme et procede destines a l'acces electronique en temps partage pour la distribution securisee d'un colis
US6882269B2 (en) * 2000-07-14 2005-04-19 Darren Murrey System and method for remotely coordinating the secure delivery of goods
US20020103653A1 (en) * 2000-12-01 2002-08-01 Stephen Huxter System and method for facilitating receipt and collection of goods ordered from online retailers
CN1221917C (zh) * 2000-12-21 2005-10-05 日本电气株式会社 锁柜系统,锁柜控制方法,控制中心和记录介质
US20020178016A1 (en) * 2001-05-23 2002-11-28 Mclellan Kerry Method and apparatus for distributing parcels
US6791450B2 (en) * 2001-07-31 2004-09-14 Security People, Inc. Networked digital locker lock system
GB2382421A (en) * 2001-11-26 2003-05-28 Bybox Holdings Ltd Collection and delivery system
US20050075989A1 (en) * 2003-10-07 2005-04-07 Pitney Bowes Incorporated Method for securely storing objects
US20060179724A1 (en) * 2005-01-27 2006-08-17 Lee Kyu N Delivery storage apparatus and system and a method for the same
US8797138B2 (en) * 2009-01-13 2014-08-05 Utc Fire & Security Americas Corporation, Inc. One-time access for electronic locking devices
CN101814215B (zh) * 2010-04-13 2011-07-27 上海城市文化传媒管理有限公司 一种使用密码储物柜递送货物的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2012034171A1 *

Also Published As

Publication number Publication date
CA2811317A1 (fr) 2012-03-22
CN103210165B (zh) 2016-03-09
WO2012034171A1 (fr) 2012-03-22
CA2811317C (fr) 2018-07-24
EP2616615A4 (fr) 2017-07-05
CN103210165A (zh) 2013-07-17
AU2011301771A1 (en) 2013-05-02
AU2011301771B2 (en) 2015-10-01

Similar Documents

Publication Publication Date Title
CA2811317C (fr) Systemes et procedes pour acceder a un espace de stockage securise ou pour gerer celui-ci
US8698596B2 (en) Apparatus and method for accessing a secured storage space
US11144873B2 (en) Package management system with accelerated delivery
US10643415B2 (en) Package management system with accelerated delivery
US12008852B2 (en) Access management and reporting technology
US20120235786A1 (en) Intelligent Enclosures
US11270251B2 (en) Package management system with accelerated delivery
US20200250615A1 (en) Package Management System with Accelerated Delivery
US20180374043A1 (en) Systems and methods for control of electronic parcel lockers
US20180070753A1 (en) Receptacle Security System
US20160247344A1 (en) Systems and methods for facilitating package delivery or pickup
US8694388B2 (en) Delivery management system and method using smart communicator
US20150235490A1 (en) Access Code Administration and Sharing
US10783479B2 (en) System and method for delivering a package
US10997547B2 (en) System and method for detecting potentially unauthorized access to an enclosure
US20150235495A1 (en) System and Method for Partially Opening an Access Barrier
US20150235172A1 (en) System and Method for Detecting Potentially Unauthorized Access to an Enclosure
US20180367419A1 (en) Automated tracking-number based administration of access codes
US10217303B1 (en) System and method for delivery of goods with automatic access code expiration
AU2015203868A1 (en) Intelligent Enclosures

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130409

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEZYGOLOGY INC.

DAX Request for extension of the european patent (deleted)
RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20170606

RIC1 Information provided on ipc code assigned before grant

Ipc: E05B 49/00 20060101ALI20170530BHEP

Ipc: G06Q 10/08 20120101ALI20170530BHEP

Ipc: G07C 9/00 20060101AFI20170530BHEP

Ipc: G07F 17/12 20060101ALI20170530BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20181122

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20210608