Systems and methods for synchronizing delivery of related parcels via computerized locker bank

Description

BACKGROUND

The continued growth of e-commerce and the resultant increase in parcel delivery volume has led to increased challenges related to the last leg of parcel delivery (e.g., ‘the last mile problem’). Generally, for common carriers, parcel delivery comprises a series of segments between an origin location and a destination location. Points between these segments may include, for example, a pick-up location, intermediate hub, destination hub, and delivery address. The final segment in delivery of a parcel typically includes a segment between a destination hub and the delivery address of the parcel. Challenges related to the final segment may arise when a consignee is not present at the delivery address to take delivery of the parcel. This may, for example, cause the common carrier to make multiple trips to the same delivery address to successfully deliver the item. Each additional trip to the delivery address may have an added associated cost that the common carrier must bear. Accordingly, there is a need for improved systems and processes for addressing these challenges.

SUMMARY OF THE VARIOUS EMBODIMENTS

A direct-to-locker bank delivery system, in various embodiments, comprises a computerized locker bank and one or more remote logistics servers comprising one or more processors and memory. In particular embodiments, the computerized locker bank comprises a plurality of selectively securable locker compartments, each of the plurality of selectively securable locker compartments comprising one or more doors and one or more locking mechanisms; and one or more locker bank computers comprising one or more processors and memory. In some embodiments, the memory stores: (1) first package level detail information for a first parcel, the first package level detail information comprising data associated with a first consignee; and (2) one or more pieces of package level detail information for one or more parcels currently stored at the computerized locker bank, wherein the one or more pieces of package level detail information comprise, for each respective parcel of the plurality of parcels, consignee information for the respective parcel. In particular embodiments, the one or more processors are configured to: (1) receive an indication that the first parcel is scheduled for delivery at a primary delivery location; (2) determine whether the one or more parcels currently stored at the computerized locker bank comprise one or more second parcels associated with the first parcel based on the one or more pieces of package level detail information for the one or more parcels currently stored at the computerized locker bank and the first package level detail information; (3) in response to determining that the one or more parcels currently stored at the computerized locker bank comprise the one or more second parcels, route the first parcel to the computerized locker bank without attempting delivery of the first parcel at the primary delivery location; (4) receive a request to deliver the first parcel to the computerized locker bank; and (5) in response to receiving the request, operate the one or more locking mechanisms on a particular one of the plurality of selectively securable locker compartments to open the one or more doors.

In various embodiments, determining whether the one or more parcels currently stored at the computerized locker bank comprise one or more second parcels associated with the first parcel comprises determining whether any of the one or more parcels currently stored at the computerized locker bank have a consignee selected from a group consisting of: (1) a neighbor of the first consignee; (2) an individual that shares the primary delivery address with the first consignee; and (3) the first consignee.

In still further embodiments, the first package level detail information further comprises one or more dimensions of the first parcel; and the one or more pieces of package level detail information for the one or more parcels currently stored at the computerized locker bank further comprise, for each respective parcel of the plurality of parcels, one or more dimensions of the respective parcel. In such embodiments, the one or more processors may be further configured to: (1) determine, based on the one or more dimensions of the first parcel and one or more dimensions of the one or more second parcels, whether a particular one of the plurality of selectively securable locker compartments is sufficiently large to accommodate both the first parcel and the one or more second parcels; and (2) in response to determining that the particular one of the plurality of selectively securable locker compartments is sufficiently large to accommodate both the first parcel and the one or more second parcels, facilitate placement of the first parcel and the one or more second parcels in the particular one of the plurality of selectively securable locker compartments.

A computer-implemented method of facilitating delivery of a first parcel to a locker bank, in various embodiments, comprises: (1) receiving, by one or more processors, at a logistics server, a request to deliver a first parcel to a first location; (2) at least partially in response to receiving the request, determining, by one or more processors, for at least one second location, whether one or more second parcels currently stored at the at least one second location are associated with the first parcel, wherein the at least one second location comprises a locker bank; (3) in response to determining that the one or more second parcels are associated with the first parcel, routing, by one or more processors, the first parcel to the second location; (receiving, by one or more processors, a request to deliver the first parcel to the computerized locker bank at the second location; and (4) in response to receiving the request, operating, by one or more processors, the one or more locking mechanisms on a particular one of the plurality of selectively securable locker compartments to open the one or more doors. In particular embodiments the locker bank comprises a plurality of selectively securable locker compartments, each of the plurality of selectively securable locker compartments comprising one or more doors and one or more locking mechanisms; and one or more locker bank computers comprising one or more processors and memory.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a system and method for synchronizing delivery of related parcels to a computerized locker bank are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a block diagram of a synchronized delivery system in accordance with an embodiment of the present system;

FIG. 2 is a schematic diagram of a computer, such as the logistics server of FIG. 1, that is suitable for use in various embodiments;

FIG. 3 is an exemplary computerized locker bank according to a particular embodiment;

FIG. 4 depicts a flow chart that generally illustrates various steps executed by a Direct to Locker Bank Delivery Determination Module that, for example, may be executed by the logistics server of FIG. 1;

FIG. 5 depicts a flow chart that generally illustrates various steps executed by a Synchronized Parcel Delivery to Locker Bank Module that, for example, may be executed by the logistics server of FIG. 1;

FIG. 6 depicts a flow chart that generally illustrates various steps executed by a Parcel Pickup Authorization Module that, for example, may be executed by the logistics server of FIG. 1; and

FIGS. 7-9 depict exemplary illustrative examples of an implementation of a synchronized delivery system according to various embodiments; and

FIG. 10 depicts an exemplary user experience (e.g., delivery driver experience) according to various embodiments.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Overview

In light of the ‘last mile problem’ and in the interest of conserving resources such as fuel, vehicle wear-and-tear, etc., logistics providers may desire to reduce a number of delivery attempts that a delivery driver must make as part of a last leg of delivery of a parcel (e.g., to a consignee's home or business). Reducing the number of delivery attempts may include, for example: (1) reducing a number of subsequent delivery attempts following an initial, unsuccessful delivery attempt; and/or (2) avoiding a need to make the initial delivery attempt at all. A logistics provider may utilize a synchronized delivery system in order to facilitate delivery of related parcels to a computerized locker bank for retrieval by a parcel consignee or another on behalf of the consignee in various situations such as, for example: (1) following an initial, unsuccessful delivery attempt at a primary delivery location (e.g., such as the consignee's home or business); or (2) directly from a delivery hub, in lieu of making an initial attempt to deliver the parcel at the primary delivery location.

In particular embodiments, the synchronized delivery system is configured to determine whether one or more conditions exist such that the logistics provider can deliver a parcel directly to a computerized locker bank in lieu of making any delivery attempt to the primary delivery location of the parcel. In various embodiments, the one or more conditions may include any suitable condition such as, for example: (1) a consignee associated with the parcel already has another parcel awaiting pick up at the computerized locker bank; (2) a third party that the consignee has authorized to pick up parcels on their behalf has a parcel awaiting pick up at the computerized locker bank; (3) one or more other parcels associated with the parcel in any other suitable way are awaiting pick up at the computerized locker bank; (4) a third party that the consignee has authorized to pick up parcels on their behalf has had a parcel redirected to a computerized locker bank; and/or the like. Generally, routing a parcel directly to a locker bank may enable the consignee or the third party to pick up both parcels (since they already need to make the trip) while also saving a logistics provider from having to make the delivery attempt at the primary delivery location.

As an example, a logistics provider may prefer to deliver a first parcel addressed to a particular consignee directly to a computerized locker bank rather than attempting delivery at the consignee's home when the consignee already has a second parcel at the computerized locker bank awaiting pick up by the consignee. Because, in this example, the consignee already needs to travel to the computerized locker bank to retrieve the second parcel, it may make sense to deliver the first parcel directly to the locker bank, so the consignee can pick up both the first parcel and the second parcel at the same time. This may avoid, for example, the logistics provider from making an unsuccessful delivery attempt at the consignee's home with the first parcel, only to have to then deliver the first parcel to the locker bank anyway.

In addition to avoiding unnecessary delivery attempts when a consignee himself or herself already has a parcel stored at a locker bank awaiting pickup, various embodiments of a synchronized delivery system may determine to deliver a parcel associated with a consignee directly to a computerized locker bank in lieu of attempting delivery of the parcel at the consignee's primary delivery address in response to determining that a third party, acting on behalf of the consignee, has a parcel stored at the locker bank awaiting pickup. A particular consignee may, for example, authorize one or more neighbors, roommates, friends, co-workers, etc. to pick up parcels on their behalf. In such embodiments, for example, a person may have authorized their neighbor to pick up parcels for them from a locker bank. The system may then (1) determine that a first parcel needs to be delivered to the person; (2) determine that the authorized third party already has a parcel at the locker bank awaiting pick up by the authorized third party; and (3) facilitate delivery of the first parcel directly to the locker bank in lieu of attempting delivery at the person's home address. The authorized third party may then be able to retrieve both their parcel and the person's parcel from the locker bank and deliver the person's parcel to them.

In various embodiments, a synchronized delivery system may be further configured for facilitating grouping of related parcels in a single locker at a locker bank. For example, the system may be configured to facilitate grouping a parcel addressed to a consignee that was delivered to a locker bank at a first time with a second parcel addressed to the consignee that was delivered to the locker bank at a later time. In various embodiments, this may reduce a number of lockers used for related parcels at a particular locker bank and further reduce a chance that the locker bank will become full and unable to accept new deliveries. In still further embodiments, the related parcels may include one or more parcels having a plurality of consignees. This may include, for example, facilitating grouping of parcels having consignees who have authorized each other to retrieve parcels from the locker bank on the other's behalf in a single locker. This grouping of parcels may ensure, for example, that related parcels are delivered in a ‘synchronized’ manner (e.g., to the same location or locker) such that a consignee or others on their behalf do not have parcels for retrieval at a plurality of different locations, or in a plurality of different lockers at the same location.

Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, a system for synchronizing delivery of related parcels may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web, mobile, wearable computer-implemented, computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices.

Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions.

Example System Architecture

FIG. 1 is a block diagram of a synchronized delivery system 110 according to a particular embodiment. As may be understood from this figure, the synchronized delivery system 110 includes one or more computer networks 115, one or more logistics servers 100, one or more databases 140, and one or more locker bank computers 130 operatively coupled to one or more locker banks 170 and optionally in direct, wireless communication with a delivery driver's mobile computing device 180. The synchronized delivery system 110 also, in the embodiment shown in this figure, includes one or more remote computing devices 150, such as a tablet computer, a desktop or laptop computer, a handheld computing device such as a smart phone, etc. In particular embodiments, the one or more computer networks 115 facilitate communication between the logistics server 100, one or more databases 140, one or more locker bank computers 130, one or more locker banks 170, one or more remote computing devices 150, and the delivery driver's mobile computing device 180.

In particular embodiments, the one or more remote computing devices 150 are configured to access the one or more databases 140 (e.g., via the one or more networks 115) to retrieve package level detail information (e.g., PLD information) for one or more parcels. The one or more remote computing devices 150 may, for example, enable a consignee to retrieve tracking information for one or more parcels that are currently scheduled for delivery to determine a delivery date/time, a delivery location, etc. The consignee may also use the one or more remote computing devices 150 to view changes in tracking information (e.g., such as when a parcel is routed from a primary delivery location to an alternate delivery location).

In various embodiments, the one or more locker banks 170 may include a network of computerized locker banks. For example, a particular network of computerized locker banks may server as alternate delivery locations for a particular area or region (e.g., such as a city or neighborhood). In various embodiments, a particular logistics provider may operate the network of locker banks. In other embodiments, a third party company may operate the network and enable one or more other logistics providers to utilize the one or more locker banks 170 within the network. In such embodiments, the synchronized delivery system 110 (e.g., or any of its components such as those shown in FIG. 1) may, for example, be configured to interface with one or more third party devices such as a third party computing device (not shown), a third party logistics server (not shown), etc.

The one or more computer networks 115 may include any of a variety of types of wired or wireless computer networks such as the Internet (or other WAN), a private intranet, a public switch telephone network (PSTN), a mesh network, or any other type of network (e.g., a network that uses Bluetooth (standard or low energy Bluetooth), beacon communication technologies (e.g., iBeacon), and/or near field communications to facilitate communication between computing devices). The communication link between the logistics server 100, database 140, one or more locker bank computers 130, one or more locker banks 170, one or more remote computing devices 150 and the delivery driver's mobile computing device 180 may be, for example, implemented via a Local Area Network (LAN) or via the Internet (or other WAN). In particular embodiments, a communication link (e.g., a wireless communication link) between the one or more locker bank computers 130 and the delivery driver's mobile computing device 180 may be implemented via beacon communication technologies or any other suitable communication link (e.g., Bluetooth, infrared, NFC, IEEE 802.15.4). In various embodiments, while the one or more locker bank computers 130 are in wireless communication (e.g., direct wireless communication) with the delivery driver's mobile computing device 180, the delivery driver's mobile computing device 180 may be configured to operate as an input device for the one or more locker bank computers 130. Exemplary interoperability of the delivery driver's mobile computing device 180 and the one or more locker bank computers 130 is described more fully in application Ser. No. 15/252,629, filed, Aug. 31, 2016, entitled, “LOCKER BANKS WITH AUTOMATICALLY OPENING DOORS”, which is hereby incorporated by reference in its entirety.

FIG. 2 illustrates a diagrammatic representation of a computer architecture 120 that can be used within the synchronized delivery system 110, for example, as a client computer (e.g., the delivery driver's mobile computing device 180 or the one or more remote computing devices 150 in FIG. 1), or as a server computer (e.g., the one or more logistics servers 100 shown in FIG. 1). In particular embodiments, the computer 120 may be suitable for use as a computer within the context of the synchronized delivery system 110 that is configured to facilitate routing of parcels to alternate delivery locations or facilitate the receipt and/or processing of parcels once they are delivered to the alternate delivery locations.

In particular embodiments, the computer 120 may be connected (e.g., networked) to other computers in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computer 120 may operate in the capacity of a server or a client computer in a client-server network environment, or as a peer computer in a peer-to-peer (or distributed) network environment. The computer 120 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computer capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computer. Further, while only a single computer is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

An exemplary computer 120 includes a processing device 202, a main memory 204 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 218, which communicate with each other via a bus 232.

The processing device 202 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 202 may be configured to execute processing logic 226 for performing various operations and steps discussed herein.

The computer 120 may further include a network interface device 208. The computer 120 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker).

The data storage device 218 may include a non-transitory computer-readable storage medium 230 (also known as a non-transitory computer-readable storage medium or a non-transitory computer-readable medium) on which is stored one or more sets of instructions (e.g., software 222) embodying any one or more of the methodologies or functions described herein. The software 222 may also reside, completely or at least partially, within main memory 204 and/or within processing device 202 during execution thereof by computer 120—main memory 204 and processing device 202 also constituting computer-accessible storage media. The software 222 may further be transmitted or received over a network 220 via network interface device 208.

While the computer-readable storage medium 230 is shown in an exemplary embodiment to be a single medium, the terms “computer-readable storage medium” and “machine-accessible storage medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable storage medium” should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the computer and that cause the computer to perform any one or more of the methodologies of the present invention. The term “computer-readable storage medium” should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.

Exemplary Locker Bank

FIG. 3 depicts an exemplary locker bank 170 that may be used in the context of a synchronized delivery system 110 for the temporary storage of one or more parcels until their retrieval (e.g., by a consignee or another on the consignee's behalf). In the embodiment shown in this figure, the locker bank 170 comprises a locker bank computer 130 that users (e.g., such as delivery drivers or parcel consignees) may use to facilitate the placement of one or more items into the locker bank 170 and/or retrieval of one or more items from the locker bank 170, for example, in any manner described in this disclosure or in any other suitable manner. The locker bank computer 130, in a particular embodiment, comprises a touch-screen display 340, one or more imaging devices 350 (e.g., one or more cameras), a card reader 360, and a machine-readable indicia scanner 370 (e.g., a barcode scanner). The locker bank 170 further comprises an optional awning 320 that extends outwardly from an upper portion of the locker bank 170 and may provide at least partial protection to users from various weather conditions such as rain, snow, wind, and sun when the users are placing parcels into the locker bank 170 and/or retrieving parcels from the locker bank 170.

As shown in this figure, a locker bank 170, according to a particular embodiment, further comprises a plurality of lockers 310 of varying sizes (e.g., small, medium, large, etc.). In a particular embodiment, the locker bank 170 comprises one or more secure lockers (e.g., one or more selectively securable locker compartments), made of a sufficiently strong material to prevent unwanted access to the lockers (e.g., a suitable metal such as steel). In various embodiments, the secure lockers 310 of the locker bank 170 comprise any suitable number, size, shape, dimension, etc. For example, a particular locker bank may include 25 secure lockers of varying sizes and shapes that are configured to hold a variety of different sized items. In various embodiments, the arrangement of the secure lockers 310 may include any suitable arrangement. For example, a particular locker bank may have all large lockers on the outer edges of the locker bank with smaller lockers towards the center of the locker bank.

In a particular embodiment, a locker bank comprises a plurality of secure lockers that each comprises an enclosure 380 (e.g., a substantially rectangular enclosure or any suitably shaped enclosure) defining at least one opening 382. In particular embodiments, each of the plurality of secure locker enclosures 380 define an enclosure having particular dimensions (e.g., a height, a width, and a depth). In various embodiments, the at least one opening 382 defined by the enclosure 380 defines a particular sized opening (e.g., having a height and width). In various embodiments, the one or more secure lockers 310 each comprise at least one door 390 adjacent the opening 382 for selectively restricting access to an interior portion of the one or more lockers 310 (e.g., an interior portion of the enclosure). In particular embodiments, the at least one door 390 is positioned to selectively prevent access to the interior of the locker enclosure 380 through the at least one opening 382 when the at least one door 390 is in a closed position. In various embodiments, the at least one door 390 is configured, when in an open position, to provide access to the interior of the locker enclosure 380 through the at least one opening 382 as shown.

In various embodiments, the one or more lockers 310 further comprise at least one locking mechanism 392 for maintaining the at least one door 390 in the closed position. In particular embodiments, the locking mechanism 392 includes an electronically-controlled locking mechanism. In particular embodiments, the locker bank computer 130 is configured to engage or disengage the locking mechanism 392 (e.g., lock and unlock the locker) in order to provide or restrict access to the locker enclosure 380.

Exemplary System Platform

Various embodiments of a system for delivering items (e.g. parcels) to computer-controlled alternate delivery locations (e.g., computerized locker banks) may be implemented within the context of any suitable service. For example, particular embodiments may be implemented within the context of any logistics service (e.g., such as those provided by United Parcel Service of America, Inc. of Atlanta, Ga.). Various aspects of the system's functionality may be executed by certain system modules, including a Direct-to-Locker-Bank Delivery Determination Module 400, a Synchronized Parcel Delivery to a Locker Bank Module 500, and a Parcel Pick Up Authorization Module 600. These modules are discussed in greater detail below.

It should be understood, in light of this disclosure, that the various functions described below in the context of the Direct-to-Locker-Bank Delivery Determination Module 400, the Synchronized Parcel Delivery to a Locker Bank Module 500, and the Parcel Pick Up Authorization Module 600 may be implemented in a manner other than the modular architecture described below. Various embodiments of these functions are described below in this manner to facilitate understanding of the invention described herein. Furthermore, while various embodiments described below may refer to various functions performed by the synchronized delivery system 110, it should be understood that such functions may be performed, in particular embodiments, by any suitable component of, or combination of components of the synchronized delivery system 110, such as those described above with respect to FIG. 1.

Additionally, although various steps and functions are described as occurring in response to another step, function, or triggering event, it should be understood that in various other embodiments, such functions or steps may occur in response to any other triggering functions or events; independent of any triggering functions or events; at least partially in response to any triggering functions or events; or in response to or at least partially in response to any combination of triggering functions, steps, events, etc. Although these exemplary modules are described as performing these functions in a particular order, it should be further understood that various other embodiments and implementations of these functions may occur in an order other than in which they are presented. Still other embodiments may omit particular steps or functions described below or perform additional steps or functions to those described.

Although for illustrative purposes, the system will be generally described in the context of parcel delivery to a computerized locker bank, it should be understood that other embodiments of the synchronized delivery system may be implemented in the context of any other suitable alternate delivery location system that may, for example, utilize attended or unattended alternate delivery locations as a temporary storage location for retrieval of parcels by consignees and others on their behalf. In various embodiments, these alternate delivery locations may include any suitable location other than a primary delivery address (e.g., home or office address) of a consignee. This may include, for example, any suitable location having one or more storage areas for holding items for later pickup. Particularly, these alternate delivery locations may include, for example, retail stores, gas stations, grocery stores, pharmacies, or any other suitable location.

A. Direct-to-Locker-Bank Delivery Determination Module

FIG. 4 is a flow chart of operations performed by an exemplary Direct-to-Locker-Bank Delivery Determination Module 400. In particular embodiments, a Direct-to-Locker-Bank Delivery Determination Module 400 may facilitate the routing of a first parcel directly to an alternate delivery location in lieu of attempting delivery of the first parcel at a primary delivery location. As discussed above, although the Direct-to-Locker-Bank Delivery Determination Module 400 below particularly describes parcel routing to a computerized locker bank, it should be understood in the context of this disclosure that the Direct-to-Locker-Bank Delivery Determination Module 400 may, in various other embodiments, be utilized in the context of the synchronized delivery system to route one or more parcels to any other suitable alternate delivery location or other location (e.g., a mobile package car, attended or unattended alternate delivery location, etc.).

In general, various embodiments of the Direct-to-Locker-Bank Delivery Determination Module 400 are configured to route one or more parcels directly from a distribution hub to a computerized locker bank, rather than attempting a potentially unsuccessful delivery at a primary delivery location in order to reduce a number of delivery attempts across a logistics network. As may be understood by one skilled in the art, eliminating even a single or a few delivery attempts over the course of a day for a particular delivery driver, when extrapolated over a period of time and plurality of other delivery drivers, may provide a reduction in consumption of fuel, a reduction in wear-and-tear on vehicles, an increased productivity of delivery drivers, and other benefits to logistics providers or others who may implement a synchronized delivery system 110 such as the various embodiments of a synchronized delivery system 110 described herein.

Various steps of an exemplary Direct-to-Locker-Bank Delivery Determination Module 400 are described below. Although these steps are discussed in a particular order, it should be understood that particular embodiments of a Direct-to-Locker-Bank Delivery Determination Module 400 may include one or more additional steps to those described, may omit one or more of the described steps, or may perform any of the steps in an order other than in which they are presented.

I. Receive an Indication that a First Parcel Having an Associated Consignee is Scheduled for Delivery at a Primary Delivery Location

Referring to FIG. 4, when executing the Direct-to-Locker-Bank Delivery Determination Module 400 (e.g., executed by the one or more logistics servers 100), the synchronized delivery system 110 begins, at Step 410, by receiving an indication that a first parcel having an associated consignee is scheduled for delivery at a primary delivery location. The primary delivery location may, for example, include a delivery address to which the particular parcel is initially addressed (e.g., by a sender of the particular parcel) such as, for example: (1) a home address of the parcel's consignee; (2) a work address of the parcels' consignee; (3) a vacation address of the parcel's consignee; (4) an address of a friend or relative of the parcel's consignee; (5) a locker bank convenient to the parcel's consignee; or (6) any other suitable location. In such embodiments, the parcel may be addressed to be delivered to the consignee at the primary delivery location (e.g., the first parcel may be addressed to the consignee and indicate their home address on a shipping label printed or written on the first parcel).

In various embodiments, the system is configured to receive the indication when shipment of the first parcel is initiated (e.g., in response to initiation of shipment of the first parcel). In various embodiments, the system receives the indication at the one or more logistics servers 100 shown in FIG. 1. In particular embodiments, a common carrier may, for example, receive a first parcel for delivery (e.g., at a parcel drop-off location). The synchronized delivery system 110 may then receive consignee information associated with the first parcel, information associated with the first parcel itself, shipping information associated with the first parcel, or other suitable information (e.g., package level detail (PLD) information).

In various embodiments, the PLD information may comprise, for example consignee and/or shipper information associated with the first parcel such as: (1) a name of the consignee for the first parcel; (2) an address of the consignee for the first parcel; (3) an account number for a consignee account that the consignee has with the shipper of the first parcel; (4) a return address of the first parcel; (5) contact information associated with the consignee of the first parcel (e.g., telephone number, e-mail address, etc.); and/or any other suitable information associated with the first parcel's consignee or shipper. In further embodiments, the PLD information may comprise information associated with the first parcel such as, for example: (1) a description of one or more items shipped in the first parcel; (2) a number of the one or more items in the first parcel; (3) a weight of the first parcel; (4) a size of the first parcel (e.g., including dimensions such as length, width, and height); (5) a value of the one or more items in the first parcel; and/or (6) any other suitable information associated with the first parcel itself or the one or more items within. In still other embodiments, the PLD information may comprise shipping information associated with the first parcel such as, for example; (1) service level (e.g., overnight shipping, two-day shipping, ground shipping, etc.); (2) one or more special handling instructions (e.g., fragile, one or more temperature requirements, one or more special monitoring or tracking requirements, etc.); and/or (3) any other suitable shipping information associated with the first parcels.

In various embodiments, the synchronized delivery system 110 is configured to retrieve at least a portion of the PLD information using a unique tracking number associated with the first parcel, for example; (1) before intake of the first parcel; (2) concurrently with intake of the first parcel; or (3) after intake of the first parcel. The system may then use the PLD information to generate a shipping label for placement on the first parcel, where the shipping label includes the primary delivery address.

As an example, the system may be configured to receive the indication in response to a customer of a logistics provider dropping off the first parcel for shipment to the consignee (e.g., when the customer drops off the first parcel at a drop-off location associated with the logistics provider, the system may receive a generated unique identifier such as a 1Z number associated with the parcel). In other embodiments, the system may be configured to receive the indication from an online retailer, which may initiate the shipment in response to a purchase of one or more items from the online retailer by a customer of the online retailer.

In various other embodiments, the system (e.g., the one or more logistics servers 100) may receive the indication during any suitable phase of a delivery process for delivering the first parcel to the primary delivery location. In various embodiments, the indication may include a notification, message, status transmission, update to tracking information, or other suitable indication. In various embodiment, as may be understood by one skilled in the art, a parcel may be scanned at various points of the delivery process (e.g., at an intake location, at each distribution between the intake location and the delivery address, etc.). In particular embodiments, in response to a scan of the first parcel, the synchronized delivery system 110 may update tracking information associated with the first parcel (e.g., the PLD information) in the one or more databases 140 to include a time and location of the scan. In various embodiments, the system is configured to receive the indication that the first parcel is scheduled for delivery at the primary delivery location in response to a scan of the first parcel at a particular point in the delivery process.

For example, in particular embodiments, the system may receive the indication between a time at which the first parcel arrives at a local or regional distribution hub and a time at which the first parcel is loaded onto a delivery vehicle (e.g., package car) for delivery to the primary delivery location. In other embodiments, the system is configured to receive the indication after the first parcel has been loaded onto a delivery vehicle for delivery at the primary delivery location, but prior to a delivery attempt by a delivery driver of the first parcel at the primary delivery location. The system may, for example, receive the indication in response to a scanning (e.g., by one or more remote computing devices 150) of a unique identifier associated with the first parcel (e.g., which may be affixed to the first parcel). The unique identifier may be any unique identifier such as, for example, a linear barcode, a matrix barcode (e.g., QR code), an RFID tag, or any other suitable identifier.

In various embodiments, the system is configured to receive the indication on a day in which the first parcel is scheduled for delivery at the primary delivery location. In other embodiments, the system is configured to receive the indication immediately prior to facilitating loading of the first parcel on a delivery vehicle for ultimate delivery of the first parcel to the primary delivery location. In such embodiments, receiving the indication immediately prior to loading the first parcel on a delivery vehicle for delivery may enable the system to route the parcel directly to an alternate delivery location in lieu of attempting delivery at the primary delivery location without having to, for example, facilitate transfer of the first parcel to a different delivery vehicle.

II. Determine Whether One or More Second Parcels Associated with the First Parcel are Currently Awaiting Pick Up at an Alternate Delivery Location

Continuing to Step 420, the system determines whether one or more second parcels associated with the first parcel are currently awaiting pick up at an alternate delivery location. In various embodiments, the system is configured to make the determination in response to receiving the indication that the first parcel is scheduled for delivery at the primary delivery location. In other embodiments, the system is configured to make the determination at a particular time prior to an expected delivery time of the first parcel at the primary delivery location. For example, the system may make the determination prior to loading the first parcel on a delivery vehicle, before delivery vehicle carrying the first parcel leaves a distribution hub, or at any other suitable point in time (e.g., at a specific amount of time prior to an estimated delivery time of the first parcel at the primary delivery location). In still other embodiments, the system may make the determination in response to any other suitable triggering event or independent of any triggering event.

In particular embodiments, the one or more second parcels associated with the first parcel (e.g., the first parcel's consignee) may include one or more second parcels addressed to the consignee that the consignee has not yet picked up from the alternate delivery location. In such embodiments, the one or more second parcels that the consignee has not yet picked up may include, for example, one or more second parcels that were routed to the alternate delivery location following a previous unsuccessful delivery attempt of the one or more second parcels at the consignee's primary delivery location (e.g., home). For example, if a logistics provider attempted delivery of parcel A for a consignee at the consignee's primary delivery location on a Monday, and the consignee was not present to sign for the parcel, the logistics company may have routed the parcel to a computerized locker bank. If, on a subsequent day (e.g., the following day), the logistics company has parcel B scheduled for delivery at the consignee's primary delivery location, and the consignee has not yet picked up parcel A from the computerized locker bank, the system would determine that parcel A is associated with parcel B and currently awaiting pick up at an alternate delivery location. The system may, for example, determine that Parcel A is associated with Parcel B by comparing PLD information for parcel A and parcel B to determine whether parcels A and B have matching consignees, matching primary delivery addresses, matching consignee account numbers, or other matching PLD information or combination of matching PLD information.

In other embodiments, the one or more second parcels associated with the first parcel may include one or more second parcels that are associated with the first parcel by virtue of the one or more second parcels being associated with (e.g., addressed to) an individual to whom the consignee has given authorization to pick up parcels from alternate delivery locations on the consignee's behalf. In such embodiments, the one or more second parcels may be associated with an individual authorized to pick up the first parcel on the consignee's behalf. In various embodiments, the system may be configured to receive, from a particular consignee (e.g., a first consignee), authorization for particular other individuals (e.g., other consignees) to retrieve parcels from alternate delivery locations on their behalf. Various techniques for authorizing parcel pickup are described more fully below in the context of the Parcel Pickup Authorization Module 600.

In various embodiments, the system is configured to determine, for every parcel at the alternate delivery location, whether any parcel has an authorized individual (e.g., third party individual) that has been authorized by the first consignee to retrieve parcels on their behalf. The system may, for example, retrieve package level detail information for each parcel at the alternate delivery location (e.g., the system may retrieve the PLD information from the one or more databases 140). The system may further store a list of individuals that the first consignee has authorized to retrieve parcels on their behalf. The system may use the PLD information to determine a consignee for each of the parcels at the alternate delivery location, and compare the consignee for each parcel to the list of individuals authorized to retrieve parcels for the first consignee to determine whether there are one or more second parcels currently stored at the alternate delivery location that are associated with the first parcel (e.g., to determine whether one or more authorized third party individuals have one or more second parcels currently stored at the alternate delivery location).

In still other embodiments, the one or more second parcels associated with the first parcel may include one or more second parcels that are associated with the first parcel based on one or more business rules of a logistics provider that is currently handling the delivery of the first parcel. For example, in various embodiments, a logistics provider may have criteria for determining whether parcels are associated with one another for the purposes of routing directly to alternate delivery locations in lieu of making a delivery attempt at a primary delivery location. In particular embodiments, the system may be configured to enable a particular logistics provider to define the criteria (e.g., using pre-designed criteria, one or more drop down menus, one or more defined rules, etc.). In various embodiments, the system may store the defined criteria in memory. For example, a particular logistics provider may have one or more criteria that one or more second parcels are associated with the first parcel where: (1) the one or more second parcels have a second consignee that has the same primary delivery address as the consignee (e.g., because they are roommates, spouses, siblings, etc.); (2) the one or more parcels have an authorized third party that is a neighbor of the consignee (e.g., has a primary delivery address that is adjacent to or near the consignee); and/or (3) any other suitable criteria.

In various embodiments, the system is configured to determine whether the one or more second parcels are currently awaiting pick up by, for example: (1) retrieving package level detail information associated with the one or more second parcels (e.g., from the one or more databases 140); (2) determining tracking information for the one or more second parcels based on the package level detail information; and (3) using the tracking information to determine whether the one or more second parcels are currently stored at the alternate delivery location (e.g., locker bank) and have not been retrieved by an associated consignee. In particular embodiments, the system is configured to retrieve the package level detail information from the one or more databases 140.

In various embodiments, the alternate delivery location may be any suitable delivery location. For example, in various embodiments, a logistics provider may assign a particular alternate delivery location to a particular delivery route. In other embodiments, the alternate delivery location may service a particular area or region. In particular embodiments, the alternate delivery location may include a preferred alternate delivery location for the consignee. In other embodiments, the alternate delivery location may be selected (e.g., automatically by the system) based on any other suitable factor. In particular embodiments, the system is configured to determine, for at least some of the parcels at a plurality of alternate delivery locations, whether they are associated with the first parcel and awaiting pickup. The plurality of alternate delivery locations may include, for example, any alternate delivery locations that service a particular area, any alternate delivery locations within a particular distance of the primary delivery location, etc.

III. In Response to Determining that the One or More Second Parcels are Currently Awaiting Pick Up at the Alternate Delivery Location, Routing the First Parcel to the Alternate Delivery Location without Attempting Delivery of the First Parcel at the Primary Delivery Location

Next, at Step 430, the system continues by, in response to determining that the one or more second parcels are currently awaiting pick up at the alternate delivery location, routing the first parcel to the alternate delivery location without attempting delivery of the first parcel at the primary delivery location. In various embodiments, routing the first parcel to the alternate delivery location comprises modifying routing information for the first parcel and storing the modified routing information in memory (e.g., in the one or more databases 140 shown in FIG. 1).

In embodiments in which the first parcel has not yet been loaded on a delivery vehicle for delivery to the primary delivery location, the system may route the parcel directly to the alternate delivery location in any suitable manner. This may include, for example, facilitating loading, by the system, of the first parcel on any suitable delivery vehicle that has a delivery route that includes the alternate delivery location (e.g., the same alternate delivery location that is currently storing the one or more second parcels). Various systems and techniques for altering routing of parcel are described in U.S. Pat. No. 7,624,024, issued, Nov. 24, 2009, entitled, “Systems and Method for Dynamically Updating a Dispatch Plan”, which is hereby incorporated by reference in its entirety.

In still other embodiments, such as embodiments in which the first parcel is already on the delivery vehicle for delivery to the primary delivery location when the system determines that one or more second parcels are currently awaiting pick up at the alternate delivery location, the system is configured to route the first parcel directly to the alternate delivery location, by modifying delivery route information for the delivery vehicle. As may be understood by one skilled in the art, a delivery driver for a logistics company may deliver parcels to generally the same area on a day-to-day basis, but the exact delivery route (e.g., including delivery stops, etc.) may vary from day-to-day based on where in the delivery driver's delivery area there are locations that the driver needs to deliver a parcel.

For each day, the system may generate a delivery route for the driver (e.g., including specific delivery stops) based on the plurality of parcels that are loaded on the delivery driver's vehicle for delivery. The system may modify this generated delivery route in response to determining that there are one or more second parcels awaiting pick up at the alternate delivery location, for example, by: (1) removing the primary delivery location from the delivery route; and (2) adding the alternate delivery location to the delivery route (e.g., or adding the first parcel to a manifest of parcels scheduled for delivery at the alternate delivery location where the alternate delivery location is already on the delivery route). In various embodiments, modification of the delivery route may occur while the delivery vehicle is in the middle of the delivery route.

In particular embodiments, the system may, in response to routing the first parcel to the alternate delivery location, transmit a notification to, for example: (1) the consignee; (2) an individual associated with the one or more second parcels (e.g., a consignee of the one or more second parcels or a third party authorized individual); and (3) a delivery driver. For example, the system may transmit the notification to one or more remote computing devices 150 associated with the individual. In embodiments in which the one or more second parcels are associated with an individual other than the first parcel's consignee, the system may be configured to transmit a message to the individual advising the individual to wait until a later time to retrieve the one or more second parcels (e.g., to ensure that the individual doesn't retrieve the one or more second parcels from the alternate delivery location prior to delivery of the first parcel at the alternate delivery location).

In various embodiments, the system is configured to transmit a second notification to the individual once the first parcel is delivered at the alternate deliver location (e.g., so the individual is aware that they are free to go retrieve their own parcel as well as the first parcel). In embodiments in which the system is configured to modify a delivery route of a delivery vehicle having a delivery driver during transport of the first parcel, the system may transmit a notification to the delivery driver's mobile computing device 180 in response to modifying the delivery route (e.g., to inform the driver not to stop at the primary delivery location).

In particular embodiments, the system is configured to update tracking information for the first parcel. In various embodiments, the updated tracking information may identify a triggering event that cause the system to route the first parcel directly to the alternate delivery location. For example, when the consignee checks tracking information for the first parcel, the tracking information may include a notification that “the first parcel was delivered to alternate delivery location A because your neighbor, Bob Smith, already has a parcel there for pick up.” This may, for example, enable the consignee to coordinate with Bob Smith regarding who will pick up the parcels.

B. Synchronized Parcel Delivery to a Locker Bank Module

FIG. 5 is a flow chart of operations performed by an exemplary Synchronized Parcel Delivery to a Locker Module Bank 500. In particular embodiments, a Synchronized Parcel Delivery to a Locker Module Bank 500 may facilitate the grouping of related parcels in a single locker at a locker bank, regardless of when each individual parcel was delivered to the locker bank. This may, for example, reduce a usage of lockers within the locker bank for related parcels and further reduce a chance that a particular locker bank will fill up and become unable to accept additional parcel deliveries.

I. Receive a Request to Deliver a First Parcel at a Locker Bank

When executing the Synchronized Parcel Delivery to a Locker Bank Module 500, the system begins at Step 510 by receiving a request to deliver a first parcel at a locker bank. In particular embodiments, the first parcel has an associated first consignee. In some embodiments, the system is configure to receive the request via the locker bank computer 130. In other embodiments, the system receives the request via the delivery driver's mobile computing device 180 (e.g., while the delivery driver's mobile computing device is in wireless communication with the locker bank computer 130).

In particular embodiments, the system may receive the request from a delivery driver, for example, in response to receiving, from the delivery driver, at least a portion of a tracking number (e.g., 1Z number) associated with the one or more parcels. The delivery driver may, for example, enter the at least a portion of the tracking number on a suitable alphanumeric entry device associated with the locker bank computer 130 (e.g., such as a keyboard, touchscreen, etc.). In various embodiments, the at least a portion of the tracking number may include any suitable portion of the tracking number. For example, the suitable portion of the tracking number may include: (1) the first or last three digits and/or letters of the tracking number; (2) the first or last four digits and/or letters of the tracking number; (3) the first or last five digits and/or letters of the tracking number; (4) the first or last six digits and/or letters of the tracking number; and/or (5) any suitable number of letters or digits that make up any suitable portion of the tracking number (e.g., first three and last three, etc.).

In other embodiments, the system is configured to receive the request to deliver the first parcel to the locker bank at least partially in response to receiving input of a machine-readable indicia (e.g., such as a linear barcode, QR code, RFID tag, electronic tag, or other suitable indicia), which may, for example, be printed on the first parcel and associated with tracking information for the first parcel. In various embodiments, the locker bank computer 130 may comprise one or more machine-readable indicia scanners (e.g., such as a barcode scanner, RFID reader), configured to enable the delivery driver (e.g., or another) to scan a machine-readable indicia on a particular parcel (e.g., affixed to the particular parcel, printed on the particular parcel, etc.). In particular embodiments, the system may retrieve information associated with the machine-readable information, such as, for example, tracking information for the particular parcel. The system may, for example, retrieve the information by locating a stored record (e.g., PLD record) for the parcel in the one or more databases 140 using a tracking number or other unique identifier associated with the parcel. In particular embodiments, the system is configured to interpret a scanning of a machine-readable indicia associated with a particular parcel as a request to deliver the first parcel to the locker bank.

II. Determine Whether the Locker Bank is Currently Storing One or More Second Parcels Associated with the First Parcel

Continuing to Step 520, the system is configured to determine whether the locker bank is currently storing one or more second parcel associated with the first parcel. In various embodiments, the system is configured to determine whether the locker bank is currently storing one or more second parcel associated with the first parcel by, for example: (1) retrieving package level detail information associated with a plurality of parcels currently stored at the locker bank; and (2) using the package level detail information to determine which of the plurality of parcels are one or more second parcels that are associated with the first parcel. In particular embodiments, the system is configured to retrieve the package level detail information from the one or more database 140.

In various embodiments, the system may be configured to determine that one or more second parcels are associated with the first parcel based on, for example: (1) the one or more second parcels having a consignee that is the same as the first consignee; (2) the one or more second parcels has the same primary delivery address as the first parcel; (3) the one or more second parcels have a consignee that is identified as an authorized 3^rdparty for the first consignee; etc. In various embodiments, the system may determine whether the one or more second parcels are associated with the first parcel in order to group the first parcel and the one or more second parcels into a single locker at the locker bank. In particular embodiments, the system may be configured to group the parcels into a single locker with an understanding that any particular consignee associated with any of the grouped parcels may retrieve all of the parcels grouped in the single locker at the same time (e.g., and distribute the parcels to their proper consignee themselves such as by dropping off a parcel at their neighbor's house).

III. In Response to Determining that the Locker Bank is Currently Storing One or More Second Parcels Associated with the First Parcel, Determining, Based on Package Level Detail Information Associated with the First Parcel and the One or More Second Parcels, Whether there is a Single Locker at the Locker Bank that can Physically Accommodate the First Parcel and the One or More Second Parcels

Next, at Step 530, the system continues by, in response to determining that that the locker bank is currently storing one or more second parcels associated with the first parcel, determining, based on package level detail information associated with the first parcel and the one or more second parcels, whether there is a single locker at the locker bank that can physically accommodate the first parcel and the one or more second parcels. As discussed above, by seeking to group related parcels into a single locker, the system may reduce a number of lockers taken up by parcels which will be retrieved by the same individual (e.g., consignee) at a particular locker bank. Grouping the parcels in a single locker may further ease retrieve the parcels from the locker bank (e.g., by only requiring the individual to grab parcels from a single locker rather than two or more different lockers).

The system may determine whether there is a single locker at the locker bank that can physically accommodate the first parcel and the one or more second parcels by, for example: (1) retrieving (e.g., from the one or more databases 140) package level detail information for the first parcel and the one or more second parcels, the package level detail information comprising one or more dimensions (e.g., length, width, and height) of the first parcel and the one or more second parcels; (2) retrieving size information (e.g., such as volume) for one or more lockers at the locker bank (e.g., height, width, depth, etc.); and (3) determining based on the one or more dimensions of the first parcel and the one or more second parcels and the size information for the one or more lockers, whether a particular one of the one or more lockers can physically accommodate the first parcel and the one or more second parcels (e.g., can fit a first parcel having a first length, a first width, and a first height as well as one or more second parcels having a second length, a second width, and a second height).

The system may, for example, make the determination by comparing the one or more dimensions of the first parcels and the one or more second parcels with the size information for the one or more lockers. In various embodiments, the system compares a combined dimension, such as total width, length or height when the first parcel and the one or more second parcels are stacked on top of one another, placed adjacent one another, etc. with the size information for the one or more lockers to determine whether any particular one of the one or more lockers can physically accommodate the first parcel and the one or more second parcels. In particular embodiments, physically accommodating the first parcel and the one or more second parcels may include fitting the whole of the first parcel and the one or more second parcels within the particular locker's enclosure with the particular locker's door in a closed position. In still further embodiments, physically accommodating the first parcel and the one or more second parcels includes having capacity to accept the first parcel and the one or more second parcels (e.g., the single locker is not currently storing one or more other, unrelated parcels).

In particular embodiments, the system is configured to store (e.g., in the one or more database 140) size (e.g., cubic dimension) information for each particular locker within a locker bank. As may be understood in light of this disclosure, a particular locker bank may include one or more lockers of various sizes (e.g., small, medium, large). The system may store data related to dimensions (e.g., interior dimensions) of each particular locker size as well as a number of lockers having each particular locker size at a particular bank. In other embodiments, the system is further configured to track and store current capacity data associate with a particular locker bank (e.g., a number of currently occupied versus unoccupied lockers).

IV. In Response to Determining that there is a Single Locker that can Physically Accommodate the First Parcel and the One or More Second Parcels, Facilitate Placement of the First Parcel and the One or More Second Parcels in the Single Locker

Continuing at Step 540, the system is configured to, in response to determining that there is a single locker that can physically accommodate the first parcel and the one or more second parcels, facilitate placement of the first parcel and the one or more second parcels in the single locker. The system may, for example, cause the single locker's door to open in order to facilitate placement of the first parcel and the one or more second parcels within the single locker (e.g., the one or more locker bank computers 130 may cause the single locker's locker mechanism 392 to disengage and activate an actuator or other device to at least partially open the single locker's door 390). The system may then direct the delivery driver to place the first parcel and the one or more second parcels in the single locker (e.g., the one or more logistics servers 100 may transmit a message to the delivery driver's mobile computing device 180 or the one or more locker bank computers 130 may display a message on its touch-screen display 340 instructing the delivery driver to place the first parcel and the one or more second parcels in the single locker).

As may be understood by one skilled in the art, in various embodiments, the one or more second parcels may already be stored within a particular locker when the delivery driver arrives to deliver the first parcel to the locker bank. In such embodiments, the system is configured to cause the single locker's door to open in addition to causing a door of a locker that is currently storing the one or more second parcels to open (e.g., to provide the delivery driver with access to the one or more second parcels for the purposes of grouping them with the first parcel in the single locker). The delivery driver may then retrieve the one or more second parcels from the locker in which they are currently stored, and place them in the single, larger locker along with the first parcel.

In particular embodiments, the system may determine that the first parcel will fit in the locker in which the one or more second parcels are currently stored. In such embodiments, the system may cause that locker to open in response to determining that it can accommodate the first parcel in addition to the one or more second parcels when the delivery driver is delivering the first parcel to the locker bank.

In still other embodiments, the system may determine that a locker that can accommodate the first parcel in addition to the one or more second parcels is one or more sizes larger than the locker that is currently storing the one or more second parcels. In such embodiments, the system may facilitate placement of the first parcel and one or more second parcels in a single locker by causing the locker currently storing the one or more second parcels (e.g., which may be a small sized locker) and one additional locker (e.g., such as a medium sized or large sized locker) to both open (e.g., by disengaging their respective locking mechanisms). The delivery driver may then remove the one or more second parcels from the small sized locker and place them, along with the first parcel in the additional locker. In particular embodiments, such as embodiments in which the system causes an additional locker to open along with the locker that is currently storing the one or more second parcels, the system is configured to determine the appropriately sized additional locker that is most proximate to the locker storing the one or more second parcels (e.g., to minimize a number of steps a delivery driver must take to transfer the one or more second parcels to a larger locker for storage along with the first parcel).

In embodiments in which the first parcel and the one or more second parcels will not fit within a single locker in the locker bank (e.g., because the parcels combine to be too large or there are too many parcels), the system may be configured to group the first parcel and the one or more second parcels in as few lockers as possible. For example, if there are five total parcels among the first parcel and the one or more second parcels, the system may be configured to group the five parcels into two lockers (e.g., a first locker and a second locker) with two parcels in the first locker and three parcels in the second locker. For example, the system may evaluate at least a portion of the possible parcel groupings using the total dimension technique described above (e.g., total dimensions for Parcel A+Parcel B placed adjacent and stacked; total dimensions for Parcel A+Parcel B+Parcel C placed adjacent and stacked; total dimensions for Parcel A+Parcel C placed adjacent and stacked).

In various embodiments, once the parcels have been grouped into a particular locker, the system is configured to associate each particular parcel with the particular locker in memory. The system may, for example: (1) update tracking information associated with each parcel; and (2) store the updated tracking information in memory.

In still other embodiments, the system is configured to facilitate placement of the first parcel and the one or more second parcels in a single locker without determining whether the single locker is sufficiently sized to accommodate all the parcels first. Once the parcels have been delivered to the single locker, the system may be configured to enable any consignee associated with any parcel in the locker to retrieve all of the parcels from the locker on behalf of the other consignees. In order to retrieve the parcels, any particular consignee may, for example, need to provide identifying information (e.g., name, e-mail address, phone number, etc.); provide identity confirmation (e.g., such as an identification card or credit card) or take any other suitable action to authorize release of the parcels (e.g., enter a private PIN, etc.). In various embodiments, the system is configured to authorize release of the parcels in any suitable manner.

C. Parcel Pickup Authorization Module

FIG. 6 is a flow chart of operations that may be performed by an exemplary Parcel Pickup Authorization Module 600. In particular embodiments, a Parcel Pickup Authorization Module 600 (e.g., executed by the one or more logistics servers 100) is configured to enable a consignee or other individual to provide one or more authorized third parties that are authorized to retrieve parcels on the consignee's behalf. In particular embodiments, the system is further configured to enable the consignee to indicate one or more other individuals that the consignee would agree to potentially have pick up parcels for them from an alternate delivery location in lieu of having a logistics provider attempt a delivery of those parcels at the consignee's primary delivery address.

I. Receive, from a User, a Request to Authorize One or More Individuals to Pick Up Parcels from a Locker Bank on the User's Behalf

When executing the Parcel Pickup Authorization Module 600, the system (e.g., the one or more logistics servers 100) begins at Step 610 by receiving from a user, a request to authorize one or more individuals to pick up parcels from a locker bank on the user's behalf. In particular embodiments, the system is configured to receive the request at the one or more logistics servers 100. In various embodiments, the system may receive the request at the one or more logistics servers 100 via a software application installed on a remote computing device 150. The synchronized delivery system may, for example, provide the software application for installation on the remote computing device 150, which may include, for example, the user's smart phone or other suitable remote computing device 150. The software application may include a user interface for providing access to a user account associated with a logistics provider (e.g., such as a UPS MyChoice Account). The system may enable the user to provide a name, address, and other identifying information (e.g., phone number, etc.) associated with the one or more individuals as part of the request.

In various embodiments the one or more individuals may include any suitable individual such as, for example, a neighbor, friend, relative, house-mate, spouse, co-worker, etc. In particular embodiments, the one or more individuals may include an office manager of an apartment building or similar building in which the user resides. In particular embodiments, the one or more individuals may include any other suitable individual.

II. In Response to Receiving the Request, Prompt the One or More Individuals to Approve the Authorization

Continuing at Step 620, the system, in response to receiving the request, prompts the one or more individuals to approve the authorization. In various embodiments, the system may prompt the one or more individuals to approve the authorization by transmitting one or more messages to a remote computing device 150 associated with the one or more individuals (e.g., via text messages, e-mail, etc.). In various embodiments, the system may prompt the one or more users to provide the approval using a software application installed on the remote computing device 150. The synchronized delivery system may, for example, provide the software application for installation on the remote computing device 150, which may include, for example, the user's smart phone or remote computing device 150. The software application may include a user interface for providing access to a user account associated with a logistics provider (e.g., such as a UPS MyChoice Account).

The one or more individuals may provide the approval via the software application, by affirmatively responding to the one or more messages, or in any other suitable manner. As may be understood from this disclosure, it may be preferable in various embodiments for both a consignee to authorize an individual to retrieve parcels on their behalf and for the individual to agree to pick them up. In various embodiments, the authorization may be reciprocal (e.g., the consignee and individual both agree to pick up parcels on behalf of one another if need be).

In various embodiments, the request and/or authorization may include, for example: (1) a blanket approval of authorization for all parcels associated with the consignee, (2) a package specific approval, (3) a time specific approval (e.g., while the consignee is out of town), (4) a substantially real-time approval (e.g., in response to a determination by the system that a particular package is undeliverable).

III. In Response to Receiving the Approval of the Authorization, Update Data Associated with the User to Include the One or More Individuals Authorized to Retrieve Parcels on the User's Behalf

Next, at Step 630, the system, in response to receiving the approval of the authorization, updates data associated with the user to include the one or more individuals authorized to retrieve parcels on the user's behalf. The system may, for example, update data associated with a user account associated with a logistics provider (e.g., such as a UPS MyChoice Account) for the user (e.g., by modifying the data and storing it in memory such as the one or more databases 140). In particular embodiments, the system updates and stores the data for later retrieval during execution of the Direct-to-Locker-Bank Delivery Determination Module 400 described above when determining whether one or more second parcels associated with a first parcel are awaiting pick up at a computerized locker bank (e.g., to determine whether the one or more second parcels are associated with the first parcel).

IV. Receive, from a User, a Request to Deny One or More Individuals an Authorization to Pick Up Parcels from a Locker Bank on the User's Behalf

Continuing at Step 640, the system receives, from the user, a request to deny one or more individuals an authorization to pick up parcels from a locker bank on the user's behalf. In various embodiments, the system may receive the request in any suitable manner, such as any manner described above with respect to Step 610. In some embodiments, the user may wish to deny particular individuals from being able to retrieve parcels on the user's behalf. In various embodiments, for example, one or more business rules of a logistics provider may dictate that the logistics provider will route a first parcel having a consignee directly to an alternate delivery location where the consignee's roommate or neighbor already has to pick up their own parcel from the alternate delivery location. The consignee may, for any suitable reason (e.g., personal reasons, etc.) not desire for their neighbor or roommate (or other suitable person) to be able to pick up the first parcel (e.g., or any parcel). In such embodiments, the consignee could provide that information to the logistics provider using the system in order to override the logistics provider's business rules (e.g., during the systems determination process for routing parcels directly to locker banks).

V. In Response to Receiving the Request, Update Data Associated with the User to Include the One or More Individuals Who are not Authorized to Retrieve Parcels on the User's Behalf

Continuing at Step 650, the system, in various embodiments, in response to receiving the request, updates data associated with the user to include the one or more individuals who are not authorized to retrieve parcels on the user's behalf. The system may update the data in any suitable manner, such as any manner discussed above with respect to updating the data for authorized individuals in Step 630.

Exemplary System Implementation

FIGS. 7-9 depict illustrative examples of the implementation of a synchronized delivery system according to various embodiments. As may be understood from FIG. 7, a logistics provider may facilitate delivery of a parcel from a distribution hub 710 using a delivery vehicle 720. In this example, if the delivery vehicle 720 is carrying a parcel scheduled for delivery at a primary delivery location (e.g., house 730a), the delivery vehicle 720 travels along delivery route 722 to the house 730a. Once at the house 730a, the delivery driver attempts to deliver the parcel to the house 730a. If the delivery driver is not able to deliver the parcel at the house 730a, the driver may, for example, scan the parcel using his mobile computing device 180 to indicate to the synchronized delivery system that delivery was unsuccessful. Upon receiving the indication, the system may route the parcel to a suitable locker bank 170 for the parcel's consignee to pick up at their convenience.

The system may then, when routing the parcel to the suitable locker bank 170, update a delivery route of the delivery vehicle 720 to include a stop at the suitable locker bank 720. The system may further update tracking information for the parcel to indicate that the parcel will be delivered to the locker bank 170 rather than the house 730a. The delivery driver may then travel in the delivery vehicle 720 along delivery route 724 to the locker bank 720 (e.g., which may include one or more additional stops prior to arriving at the locker bank 170), and deliver the parcel to the locker bank 170.

In another implementation of this example, as shown in FIG. 7, the delivery vehicle 720 may bypass the delivery attempt at the house 730a and deliver the parcel directly to the locker bank 720 via delivery route 726. As may be understood from this figure, the system may, at any suitable time prior to attempting delivery of the parcel at the house 730a, determine that the locker bank 170 is already storing one or more parcels related to the parcel that is out for delivery (or about to be placed on the delivery vehicle 720 for delivery). The system may, for example, determine that the consignee's neighbor in house 730b has a parcel that is currently stored in a locker at the locker bank 170 that was routed to the locker bank 170 following an unsuccessful delivery attempt on a previous day. Because the neighbor has not yet picked up their parcel from the locker bank 170, the system may determine to route the parcel, addressed to consignee in house 730a, directly to the locker bank 170. In various embodiments, the system is configured to make the determination to route the parcel directly to the locker bank 170 while the parcel is still at the distribution hub 710. Once the second parcel has been routed to the locker bank 170, either the consignee at house 730a or their neighbor in house 730b can travel to the locker bank 170, pick up both parcels, and deliver their neighbor's parcel to them.

As may be understood from FIG. 7, routing a parcel directly to a locker bank 170 may preclude the delivery vehicle 720 from having to travel along delivery route 722 during its daily deliveries (e.g., or reduce its overall delivery route by whatever distance or time is required to attempt delivery at house 730a).

FIG. 8 depicts an exemplary delivery diagram showing a delivery route that a delivery vehicle may take (e.g., during a particular day). As may be understood from this figure, the delivery route begins at a distribution hub 710, and includes stops at seven house 730a-f and a stop at a locker bank 170. Although in this example, the stop at the locker bank 170 is shown at the end of the route, it should be understood that a delivery route may include a stop at a locker bank 170 at any suitable portion of the route. Other delivery routes may include multiple stops at different locker banks throughout the route, or multiple stops at the same locker bank. In some embodiments, it may be preferable to make at least one final stop at a locker bank 170 during a delivery route in order to ensure that any unsuccessful delivery attempts during the route can be dropped off at the locker bank 170, if needed.

FIG. 9 depicts an exemplary delivery diagram showing a delivery route having seven houses 730a-f that skips a delivery attempt at a particular house 730f. In this example, the system may have determined to skip a delivery attempt at house 730f for any suitable reason. For example, the system may have determined that an unsuccessful delivery attempt was made to house 730f on a previous day, and there is currently an unretrieved parcel stored at the locker bank 170 stemming from that unsuccessful delivery attempt. The system may have determined that a person authorized to retrieve parcels from locker banks on a consignee having that house 730f as a primary delivery address has an unretrieved parcel from the locker bank 170. The consignee may, for example, have authorized any suitable individual to retrieve parcels on their behalf using a remote computing device 150 to login to an account associated with a logistics provider that is handling delivery of a parcel addressed to the consignee and provide the authorization. The authorized individual may include any suitable individual such as any suitable individual living in any house 730a-f, a family member, or any other individual.

In various embodiments, a delivery vehicle may have left the distribution hub 710 having a delivery route mapped out as shown in FIG. 8 at the beginning of the route. At some time during the route, the system may have determined that a parcel scheduled for delivery at house 730f had an associated parcel currently stored at the locker bank 170 that had not yet been picked up. The system may then have automatically modified the delivery route to remove house 730f as a stop and avoid a delivery attempt of the parcel at the house 730f—instead routing the parcel directly to the locker bank 170. In such an instance, the system may automatically transmit a notification to the delivery driver (e.g., to the driver's mobile computing device 180) indicating the change to the delivery route.

Exemplary Delivery Driver Experience

FIG. 10 depicts an exemplary delivery driver 740 experience when delivering a first parcel 735a to a locker bank 170 and grouping the first parcel 735a with second, related parcel 735b in a single locker 310b. As shown in this figure, when the delivery driver 740 arrives at the locker bank 170 in his or her delivery vehicle 720, the delivery driver 740 may utilize their mobile computing device 180 to request to deliver the first parcel 735a to the locker bank 170. The mobile computing device 180 may transmit the request directly to the locker bank computer 130 via a wireless communication channel (e.g., or indirectly via one or more networks 115 as shown in FIG. 1). The system may then receive the request (e.g., at one or more logistics servers 100) and, in response, determine whether there are any parcels associated with (e.g., related to) the first parcel 735a currently stored at the locker bank 170 (e.g., in a locker at the locker bank).

The system may, for example, determine that a second parcel 735b stored in medium-sized locker 310a is associated with the first parcel 735. The first parcel 735a and the second parcel 735b may be related, for example, in that the parcels (1) have the same delivery address, (2) have the same consignee; (3) have respective consignees that are authorized to retrieve parcels on each other's behalf; (4) have respective consignees that are neighbors, roommates, co-workers, etc.; or (5) are related for any other suitable reason. The system, in response to determining that the first parcel 735a and the second parcel 735b are related may then determine whether there is a single locker at the locker bank that can physically accommodate (e.g., fit) both the first parcel 735a and the second parcel 735b). In this example, the system may determine that, based on the dimensions of first parcel 735a and the second parcel 735b, the first parcel 735a and the second parcel 735b would both fit in a single, large-sized locker.

In response to determining that the first parcel 735a and the second parcel 735b would both fit in a single, large-sized locker, the system in this example may facilitate delivery of the first parcel 735a and the second parcel 735b in a single, large-sized locker by: (1) causing a door of the medium-sized locker 310a and a door of a large-sized locker 310b to open (e.g., automatically by causing a locking mechanism of each door to disengage and causing an actuator or similar device to cause both doors to at least partially open); (2) instructing the delivery driver (e.g., by displaying one or more instructions on the touch-screen display 370 of the locker bank computer 130 or on a display screen of the mobile computing device 180) to remove the second parcel 735b from the medium-sized locker 310a and place both the first parcel 735a and the second parcel 735b in the large-sized locker 310b.

The driver may then close the large-sized locker 310b, which may cause the system to associate both the first parcel 735a and the second parcel 735b with the large-sized locker 310b in memory (e.g., by updating tracking information or other package level detail information associated with the parcels). The system may then automatically activate the locking mechanism of the large-sized locker 310b to maintain the door in a closed position and locked state. The system may further update tracking information associated with the first parcel 735a and the second parcel 735b to reflect the locker bank 170 at which they are located and the large-sized locker 310b in which they both are stored. The system may further transmit a notification to the consignee of the first parcel 735a and/or the second parcel 735b indicating that the two parcels are housed at the locker bank for retrieval.

Alternative Embodiments

Various embodiments of a synchronized delivery system may include features or perform functions in addition to those described above. Various exemplary alternative embodiments of a synchronized delivery system are described below.

On-the-Fly Delivery Route Modification Based on Unsuccessful Deliveries During Route

In various embodiments, the system is configured to modify a delivery route of a particular delivery vehicle in response to re-routing any unsuccessful delivery on the delivery route to an alternate delivery location. In particular embodiments, the system may modify the delivery route periodically (e.g., in response to each re-routing); asynchronously, in response to a status change of any parcel currently out for delivery on the delivery vehicle; in response to a change in user-submitted third party authorization pick up preferences, etc. For example, as a delivery driver progresses through their route, the system may receive one or more indications that one or more parcels were not successfully delivered (e.g., because the consignee was not home, etc.). In response to the system rerouting such parcels to an alternate delivery location, the system may, for each remaining parcel scheduled for delivery during the delivery route, determine whether each parcel is associated with any rerouted parcel. The system may then automatically route any associated parcels to the alternate delivery location as well, without making a delivery attempt at those parcels' primary delivery location. For example, an unsuccessful delivery attempt of a first parcel at a first house may result in routing of the first parcel to an alternate delivery location. If there is a scheduled delivery on the delivery route of a second parcel at a second house that is a neighbor of the first house, the system may automatically route the second parcel to the alternate delivery location as well, without attempting the delivery at the second house.

Skipping Parcel Grouping at Locker Bank Based on Capacity

In various embodiments, the system is configured to determine an availability at a locker bank prior to grouping parcels within a single locker in the locker bank. For example, if the locker bank is mostly empty (e.g., there are at least a particular number of available lockers at the locker bank), the system may determine that it is unnecessary to group related parcels together to conserve capacity. The system may, for example, utilize any suitable technique for predicting future capacity at the locker bank to determine whether it is necessary to attempt to group related parcels at a time of delivery.

Asynchronous Pickups by Consignees and Others

In particular embodiments, a consignee (e.g., or another on their behalf) may not pick up all parcels at once when retrieving parcels from a locker bank. For example, where two or more parcels have been delivered to a single locker, the consignee may retrieve fewer than all of the parcels for any reason (e.g., because carrying the parcels all at once is too difficult, one of the parcels is too heavy, or for any other suitable reason). In such embodiments, the system may, for example, store a notation that the parcel that was left behind should not be grouped with other parcels in a single locker again (e.g., in case there is a subsequent delivery at a later time such as later that day or in the next few days before the consignee returns to pick up the final parcel that was left). The system may, for example, determine that a parcel was left behind using one or more weight sensors in the locker, using a suitable light curtain in the locker, using one or more cameras associated with (e.g., positioned within) the locker, or using any other suitable technique.

In particular embodiments, the system may determine for particular consignees that it should never facilitate a grouping of a plurality of parcels in a single locker because, for example, that consignee frequently leaves at least one parcel behind when retrieving grouped parcels. In other embodiments, the system may modify tracking data for the left-behind parcel to reattempt delivery at the primary delivery location for that parcel. The system may, for example: (1) instruct a delivery driver to retrieve the parcel from the locker; and (2) facilitate delivery to the primary delivery location. This course of action may, for example, be helpful for consignees who have trouble retrieving multiple parcels from a locker bank at once (e.g., due to a handicap or other factors such as having to walk the parcels back to their home such as in an urban environment).

CONCLUSION

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation.

Claims

1. A direct-to-locker bank delivery system comprising: one or more processors;computer storage memory having computer-executable instructions stored thereon which, when executed by the one or more processors, perform operations comprising:determining first package level detail information for a first parcel, the first package level detail information comprising data associated with a first consignee, including a delivery address and first consignee identification information;determining package level detail information for one or more parcels currently stored at a computerized locker bank, the computerized locker bank comprising at least one or more locker bank computers, and a plurality of selectively securable locker compartments comprising one or more doors, and one or more locking mechanisms, wherein the package level detail information comprises consignee information for the one or more parcels;receiving an indication that the first parcel is scheduled for delivery to the delivery address;determining whether the one or more parcels currently stored at the computerized locker bank are associated with the first parcel based on the package level detail information for the one or more parcels currently stored at the computerized locker bank and the first package level detail information;in response to determining that the one or more parcels currently stored at the computerized locker bank are associated with the first parcel, modifying the first package level detail information to include the delivery of the first parcel to the computerized locker bank and not the delivery address;communicating storage information for storing the first parcel in the computerized locker bank; andin response to communicating the storage information, operating, by the one or more processors, the one or more locking mechanisms on a particular one of the plurality of selectively securable locker compartments to open the one or more doors.
2. The direct-to-locker bank delivery system of claim 1, wherein: the first package level detail information further comprises one or more dimensions of the first parcel.
3. The direct-to-locker bank delivery system of claim 2, wherein: based on the one or more dimensions of the first parcel, determining whether a particular one of a plurality of selectively securable locker compartments of the computerized locker bank is sufficiently large to accommodate the first parcel; andin response to determining whether the particular one of the plurality of selectively securable locker compartments is sufficiently large to accommodate the first parcel, facilitating placement of the first parcel in the particular one of the plurality of selectively securable locker compartments.
4. The direct-to-locker bank delivery system of claim 1, wherein: modifying the first package level detail information to include the delivery of the first parcel to the computerized locker bank comprises modifying a delivery route of a delivery vehicle so that the first parcel is delivered to the computerized locker bank.
5. The direct-to-locker bank delivery system of claim 1, wherein: modifying the first package level detail information to include the delivery of the first parcel to the computerized locker bank comprises modifying tracking information associated with the first parcel to include a destination of the computerized locker bank.
6. The direct-to-locker bank delivery system of claim 1, wherein: the one or more processors are further configured to determine whether the one or more parcels currently stored at the computerized locker bank comprise one or more second parcels based on one or more business rules associated with a logistics provider that is facilitating delivery of the first parcel.
7. The direct-to-locker bank delivery system of claim 1, wherein: the one or more processors are further configured to determine whether the one or more parcels currently stored at the computerized locker bank comprise one or more second parcels based on whether the one or more parcels currently stored at the computerized locker bank comprise a parcel having a consignee that is authorized to retrieve parcels from the computerized locker bank on behalf of the first consignee.
8. The direct-to-locker bank delivery system of claim 6, wherein: the one or more processors are further configured to:receive, from the consignee, a request to authorize one or more individuals to pick up parcels from the computerized locker bank on behalf of the consignee;in response to receiving the request, update data associated with the consignee to include the one or more individuals authorized to retrieve the parcels on behalf of the consignee; andstore the updated data in memory.
9. The direct-to-locker bank delivery system of claim 8, wherein the one or more processors are further configured to enable the consignee to provide a selection of one or more unauthorized individuals that are not authorized to pick up parcels from the computerized locker bank on behalf of the consignee.
10. The direct-to-locker bank delivery system of claim 1, wherein: the one or more processors are further configured to determine whether the one or more parcels currently stored at the computerized locker bank comprise the one or more second parcels based on whether the one or more parcels currently stored at the computerized locker bank comprise a parcel having a second consignee; andthe second consignee is the first consignee.
11. The direct-to-locker bank delivery system of claim 1, wherein: the direct-to-locker bank delivery system further comprises a network of a plurality of computerized locker banks; andthe computerized locker bank is a particular computerized locker bank in the network of the plurality of computerized locker banks.
12. A direct-to-locker bank delivery system comprising: one or more processors;computer storage memory having computer-executable instructions stored thereon which, when executed by the one or more processors, perform operations comprising:determining first package level detail information for a first parcel, the first package level detail information comprising data associated with a first consignee, including a delivery address and first consignee identification information;receiving a first indication that the first parcel is scheduled for delivery to the delivery address;receiving a second indication that an unsuccessful delivery attempt was made for the first parcel;in response to receiving the second indication, modifying the first package level detail information to include the delivery of the first parcel to a computerized locker bank, the computerized locker bank comprising at least one or more locker bank computers, and a plurality of selectively securable locker compartments comprising one or more doors, and one or more locking mechanisms and not the delivery address;communicating storage information for storing the first parcel in the computerized locker bank; andin response to communicating the storage information, operating, by the one or more processors, the one or more locking mechanisms on a particular one of the plurality of selectively securable locker compartments to open the one or more doors.
13. The direct-to-locker bank delivery system of claim 12, wherein: the first package level detail information further comprises one or more dimensions of the first parcel.
14. The direct-to-locker bank delivery system of claim 13, wherein: based on the one or more dimensions of the first parcel, determining whether a particular one of a plurality of selectively securable locker compartments of the computerized locker bank is sufficiently large to accommodate the first parcel; andin response to determining whether the particular one of the plurality of selectively securable locker compartments is sufficiently large to accommodate the first parcel, facilitating placement of the first parcel in the particular one of the plurality of selectively securable locker compartments.
15. The direct-to-locker bank delivery system of claim 12, wherein: modifying the first package level detail information to include the delivery of the first parcel to the computerized locker bank comprises modifying a delivery route of a delivery vehicle so that the first parcel is delivered to the computerized locker bank.
16. The direct-to-locker bank delivery system of claim 12, wherein: modifying the first package level detail information to include the delivery of the first parcel to the computerized locker bank comprises modifying tracking information associated with the first parcel to include a destination of the computerized locker bank.
17. The direct-to-locker bank delivery system of claim 12, wherein: the one or more processors are further configured to determine whether the one or more parcels currently stored at the computerized locker bank comprise one or more second parcels based on one or more business rules associated with a logistics provider that is facilitating delivery of the first parcel.
18. A computer-implemented method of facilitating delivery of a first parcel to a locker bank, operating one or more processors to do the following:providing instructions to deliver a first parcel to a first location;receiving information of an unsuccessful delivery attempt for the first parcel;at least partially in response to receiving information, determining whether one or more second parcels currently stored at a computerized locker bank, the computerized locker bank comprising at least one or more locker bank computers, and a plurality of selectively securable locker compartments comprising one or more doors, one or more locking mechanisms are associated with the first parcel;in response to determining that the one or more second parcels are associated with the first parcel, routing the first parcel to the computerized locker bank; andin response to routing the first parcel, operating, by the one or more processors, the one or more locking mechanisms on a particular one of the plurality of selectively securable locker compartments to open the one or more doors.
19. The computer-implemented method of claim 18, wherein: the first location is the at least one second location;the first parcel has a first consignee; anddetermining whether one or more second parcels currently stored at the second location are associated with the first parcel comprises determining whether the one or more second parcels have a second consignee selected from a group consisting of:i. a neighbor of the first consignee;ii. an individual that shares a primary delivery address with the first consignee; andiii. the first consignee.
20. The computer-implemented method of claim 19, further comprising: retrieving a first package level detail information for the first parcel, the first package level detail information comprising one or more first dimensions;retrieving a second package level detail information for the one or more second parcels associated with the first parcel, the second package detail level information comprising one or more second dimensions;determining, based on the one or more first dimensions and the one or more second dimensions, whether a particular one of the plurality of selectively securable locker compartments is sufficiently large to accommodate both the first parcel and the one or more second parcels associated with the first parcel; andin response to determining that the particular one of the plurality of selectively securable locker compartments is sufficiently large to accommodate both the first parcel and the one or more second parcels associated with the first parcel, facilitating placement of the first parcel and the one or more second parcels associated with the first parcel in the particular one of the plurality of selectively securable locker compartments.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 15/253,473 filed on Aug. 31, 2016, which is incorporated herein in its entirety by reference.

US Referenced Citations (548)

Number	Name	Date	Kind
3712468	Wenner et al.	Jan 1973	A
4688678	Zue et al.	Aug 1987	A
5153842	Cukor et al.	Oct 1992	A
5168444	Cukor et al.	Dec 1992	A
5375240	Grundy	Dec 1994	A
5400020	Jones et al.	Mar 1995	A
5444444	Ross	Aug 1995	A
5623260	Jones	Apr 1997	A
5648770	Ross	Jul 1997	A
5656799	Ramsden et al.	Aug 1997	A
5657010	Jones	Aug 1997	A
5668543	Jones	Sep 1997	A
5726435	Hara et al.	Mar 1998	A
5774053	Porter	Jun 1998	A
5786748	Nikolic et al.	Jul 1998	A
5831220	Ramsden et al.	Nov 1998	A
5831860	Foladare et al.	Nov 1998	A
5979750	Kindell	Nov 1999	A
6010064	Umeda et al.	Jan 2000	A
6026375	Hall et al.	Feb 2000	A
6028517	Sansone et al.	Feb 2000	A
6047264	Fisher et al.	Apr 2000	A
6085170	Tsukuda	Jul 2000	A
6208980	Kara	Mar 2001	B1
6211781	McDonald	Apr 2001	B1
6220509	Byford	Apr 2001	B1
6236972	Shkedy	May 2001	B1
6278936	Jones	Aug 2001	B1
6285916	Kadaba et al.	Sep 2001	B1
6289323	Gordon et al.	Sep 2001	B1
6304856	Soga et al.	Oct 2001	B1
6313760	Jones	Nov 2001	B1
6317060	Jones	Nov 2001	B1
6323254	Weikard et al.	Nov 2001	B1
6323782	Stephens et al.	Nov 2001	B1
6343275	Wong	Jan 2002	B1
6344796	Ogilvie et al.	Feb 2002	B1
6356196	Wong et al.	Mar 2002	B1
6363323	Jones	Mar 2002	B1
6411891	Jones	Jun 2002	B1
6433732	Dutta et al.	Aug 2002	B1
6442589	Takahashi et al.	Aug 2002	B1
6456900	Kakuta	Sep 2002	B1
6463420	Guidice et al.	Oct 2002	B1
6480758	Stevens	Nov 2002	B2
6486801	Jones	Nov 2002	B1
6492912	Jones	Dec 2002	B1
6510383	Jones	Jan 2003	B1
6526393	Fredman	Feb 2003	B1
6536659	Hauser et al.	Mar 2003	B1
6539360	Kadaba	Mar 2003	B1
6570488	Kucharczyk et al.	May 2003	B2
6595342	Maritzen et al.	Jul 2003	B1
6606604	Dutta	Aug 2003	B1
6612489	McCormick et al.	Sep 2003	B2
6615092	Bickley et al.	Sep 2003	B2
6618668	Laird	Sep 2003	B1
6634551	Barta et al.	Oct 2003	B2
6683542	Jones	Jan 2004	B1
6688435	Will et al.	Feb 2004	B1
6690997	Rivalto	Feb 2004	B2
6694217	Bloom	Feb 2004	B2
6700507	Jones	Mar 2004	B2
6701299	Kraisser et al.	Mar 2004	B2
6714859	Jones	Mar 2004	B2
6725127	Stevens	Apr 2004	B2
6741927	Jones	May 2004	B2
6748295	Tilles et al.	Jun 2004	B2
6748318	Jones	Jun 2004	B1
6748320	Jones	Jun 2004	B2
6756879	Shuster	Jun 2004	B2
6763299	Jones	Jul 2004	B2
6763300	Jones	Jul 2004	B2
6772130	Karbowski et al.	Aug 2004	B1
6791450	Gokcebay et al.	Sep 2004	B2
6804606	Jones	Oct 2004	B2
6820805	Stevens	Nov 2004	B2
6845909	Bong et al.	Jan 2005	B2
6859722	Jones	Feb 2005	B2
6862576	Turner et al.	Mar 2005	B1
6882269	Moreno	Apr 2005	B2
6902109	Barta et al.	Jun 2005	B2
6904359	Jones	Jun 2005	B2
6933832	Simms et al.	Aug 2005	B1
6950803	Tiley et al.	Sep 2005	B2
6952645	Jones	Oct 2005	B1
6961711	Chee	Nov 2005	B1
6967575	Dohrmann et al.	Nov 2005	B1
6974928	Bloom	Dec 2005	B2
6975998	Jones	Dec 2005	B1
6976090	Ben-Shaul et al.	Dec 2005	B2
6978929	Buie et al.	Dec 2005	B2
6985871	Simon et al.	Jan 2006	B2
6990467	Kwan	Jan 2006	B1
6994253	Miller et al.	Feb 2006	B2
7020623	Tiley et al.	Mar 2006	B1
7028895	Ashaari	Apr 2006	B2
7030781	Jones	Apr 2006	B2
7031959	Garner et al.	Apr 2006	B2
7055741	Bong et al.	Jun 2006	B2
7068149	Lee et al.	Jun 2006	B2
7075451	Yamada	Jul 2006	B2
7110958	Yang	Sep 2006	B2
7133743	Tilles et al.	Nov 2006	B2
7158941	Thompson	Jan 2007	B1
7158948	Rodriguez et al.	Jan 2007	B1
7176782	Shitan	Feb 2007	B2
7177825	Borders et al.	Feb 2007	B1
7212829	Lau et al.	May 2007	B1
7212984	Wolfe et al.	May 2007	B2
7222081	Sone	May 2007	B1
7225983	Park et al.	Jun 2007	B2
7233907	Young	Jun 2007	B2
7248160	Mangan et al.	Jul 2007	B2
7249044	Kumar et al.	Jul 2007	B2
7249087	Sharp et al.	Jul 2007	B2
7254549	Bansal et al.	Aug 2007	B1
7257552	Franco	Aug 2007	B1
7267920	Nakazawa et al.	Sep 2007	B2
7312702	Willms et al.	Dec 2007	B1
7337944	Devar	Mar 2008	B2
7341186	Mrozik et al.	Mar 2008	B2
7353181	Nel	Apr 2008	B2
7358857	White	Apr 2008	B1
7376598	Estes et al.	May 2008	B2
7385499	Horton et al.	Jun 2008	B2
7422149	Aptekar	Sep 2008	B2
7426484	Joyce et al.	Sep 2008	B2
7479899	Horstemeyer	Jan 2009	B2
7501946	Lanigan et al.	Mar 2009	B2
7509228	Bielefeld et al.	Mar 2009	B2
7511617	Burman et al.	Mar 2009	B2
7528722	Nelson	May 2009	B2
7574366	Burman et al.	Aug 2009	B2
7580845	Burman et al.	Aug 2009	B2
7617133	Antony et al.	Nov 2009	B1
7624024	Levis et al.	Nov 2009	B2
7636696	Sigler, Jr. et al.	Dec 2009	B1
7647231	Kuebert et al.	Jan 2010	B2
7653457	Bloom	Jan 2010	B2
7653603	Holtkamp, Jr. et al.	Jan 2010	B1
7657466	Klingenberg et al.	Feb 2010	B2
7660721	Williams et al.	Feb 2010	B2
7693723	Wade	Apr 2010	B2
7711654	Schmidtberg et al.	May 2010	B2
7712670	Sauerwein, Jr. et al.	May 2010	B2
7742928	Reynolds et al.	Jun 2010	B2
7752134	Spear	Jul 2010	B2
7765131	Klingenberg et al.	Jul 2010	B2
7769778	Snapp et al.	Aug 2010	B2
7815112	Volpe et al.	Oct 2010	B2
7822618	Kaneko	Oct 2010	B2
7831439	Bryar et al.	Nov 2010	B1
7848961	Estes et al.	Dec 2010	B2
7853481	Johnson	Dec 2010	B1
7868753	Jenkins et al.	Jan 2011	B2
7925524	Florence	Apr 2011	B2
7962422	Melechko et al.	Jun 2011	B1
7969306	Ebert et al.	Jun 2011	B2
7984289	Orbke et al.	Jul 2011	B2
7996328	Lundberg et al.	Aug 2011	B1
8010430	Chase et al.	Aug 2011	B1
8010462	Kinory et al.	Aug 2011	B2
8015023	Lee et al.	Sep 2011	B1
8027933	Lou et al.	Sep 2011	B2
8036993	Estes	Oct 2011	B2
8073723	Bilibin et al.	Dec 2011	B1
8086546	Spiegel et al.	Dec 2011	B2
8103521	Kuebert et al.	Jan 2012	B2
8103716	Boyce et al.	Jan 2012	B2
8108265	Bonner et al.	Jan 2012	B2
8117462	Snapp et al.	Feb 2012	B2
8131652	Gullo et al.	Mar 2012	B2
8140551	Garner et al.	Mar 2012	B2
8140592	Scott et al.	Mar 2012	B2
8156007	Anthony et al.	Apr 2012	B1
8204799	Murray et al.	Jun 2012	B1
8219490	Hammad et al.	Jul 2012	B2
8225388	Vogel et al.	Jul 2012	B2
8234275	Grant et al.	Jul 2012	B2
8249998	Reynolds et al.	Aug 2012	B2
8255235	Aldstadt	Aug 2012	B2
8255339	Andrew	Aug 2012	B2
8265947	Kuebert et al.	Sep 2012	B2
8280824	Vermeulen et al.	Oct 2012	B1
8291234	Snapp et al.	Oct 2012	B2
8306923	Roache et al.	Nov 2012	B1
8311895	Murugan et al.	Nov 2012	B1
8340978	Wade	Dec 2012	B2
8352551	Campbell et al.	Jan 2013	B2
8356187	Cook et al.	Jan 2013	B2
8364953	Bullard, Jr.	Jan 2013	B2
8380641	Bennett et al.	Feb 2013	B1
8392262	Mallick et al.	Mar 2013	B2
8437742	Garskof	May 2013	B2
8468062	Kamdar	Jun 2013	B1
8489520	Kuebert et al.	Jul 2013	B2
8744919	O'dea	Jun 2014	B1
9141931	Ackerman	Sep 2015	B2
9195950	Schenken	Nov 2015	B2
9670694	Larson et al.	Jun 2017	B2
9692738	Wenneman et al.	Jun 2017	B1
9811798	Lievens et al.	Nov 2017	B2
9916557	Gillen et al.	Mar 2018	B1
9984351	Antony et al.	May 2018	B1
10007712	Williams et al.	Jun 2018	B1
10410164	Tibbs et al.	Sep 2019	B2
20010040422	Gramlich	Nov 2001	A1
20010042001	Goto et al.	Nov 2001	A1
20010042024	Rogers	Nov 2001	A1
20010051885	Nardulli et al.	Dec 2001	A1
20020007299	Florence	Jan 2002	A1
20020007353	Kornacki	Jan 2002	A1
20020010634	Roman et al.	Jan 2002	A1
20020013744	Tsunenari et al.	Jan 2002	A1
20020016726	Ross	Feb 2002	A1
20020019761	Lidow	Feb 2002	A1
20020019777	Schwab et al.	Feb 2002	A1
20020026380	Su	Feb 2002	A1
20020029194	Lewis et al.	Mar 2002	A1
20020032612	Williams et al.	Mar 2002	A1
20020032613	Buettgenbach et al.	Mar 2002	A1
20020035515	Moreno	Mar 2002	A1
20020038266	Tuttrup et al.	Mar 2002	A1
20020040350	Shinzaki	Apr 2002	A1
20020046056	Demarco et al.	Apr 2002	A1
20020070882	Jones	Jun 2002	A1
20020073039	Ogg et al.	Jun 2002	A1
20020077937	Lyons et al.	Jun 2002	A1
20020080030	Inomata	Jun 2002	A1
20020082770	Jones	Jun 2002	A1
20020087371	Abendroth	Jul 2002	A1
20020099622	Langhammer	Jul 2002	A1
20020103653	Huxter	Aug 2002	A1
20020103724	Huxter	Aug 2002	A1
20020107820	Huxter	Aug 2002	A1
20020111914	Terada et al.	Aug 2002	A1
20020116318	Thomas et al.	Aug 2002	A1
20020120475	Morimoto	Aug 2002	A1
20020128915	Haseltine	Sep 2002	A1
20020130065	Bloom	Sep 2002	A1
20020138173	Barta et al.	Sep 2002	A1
20020143670	Cushing et al.	Oct 2002	A1
20020147919	Gentry	Oct 2002	A1
20020152093	Chalmers et al.	Oct 2002	A1
20020156645	Hansen	Oct 2002	A1
20020156846	Rawat et al.	Oct 2002	A1
20020165729	Kuebert et al.	Nov 2002	A1
20020177922	Bloom	Nov 2002	A1
20020178016	Mclellan	Nov 2002	A1
20020178074	Bloom	Nov 2002	A1
20020184497	Gage et al.	Dec 2002	A1
20030003936	Tighe	Jan 2003	A1
20030023963	Birkholz et al.	Jan 2003	A1
20030025590	Gokcebay et al.	Feb 2003	A1
20030037009	Tobin et al.	Feb 2003	A1
20030040931	De Mol Van Otterloo et al.	Feb 2003	A1
20030040980	Nakajima et al.	Feb 2003	A1
20030046173	Benjier et al.	Mar 2003	A1
20030093180	Stevens	May 2003	A1
20030097287	Franz et al.	May 2003	A1
20030110170	Matsuoka	Jun 2003	A1
20030114206	Timothy et al.	Jun 2003	A1
20030160097	Steiner	Aug 2003	A1
20030171996	Chen et al.	Sep 2003	A1
20030193414	Jones	Oct 2003	A1
20030195784	Smith, Jr.	Oct 2003	A1
20030225625	Chew et al.	Dec 2003	A1
20040015393	Fong et al.	Jan 2004	A1
20040030604	Young	Feb 2004	A1
20040039712	Tartal et al.	Feb 2004	A1
20040044582	Chowdhary et al.	Mar 2004	A1
20040073449	Yang	Apr 2004	A1
20040073499	Martin et al.	Apr 2004	A1
20040088225	Foth et al.	May 2004	A1
20040093312	Cordery et al.	May 2004	A1
20040117276	Kettler, III	Jun 2004	A1
20040117278	Dutta et al.	Jun 2004	A1
20040117326	Amato	Jun 2004	A1
20040133446	Myrick et al.	Jul 2004	A1
20040134690	Norris et al.	Jul 2004	A1
20040143518	Siegel	Jul 2004	A1
20040149822	Stevens et al.	Aug 2004	A1
20040149824	Miller et al.	Aug 2004	A1
20040153370	Yang	Aug 2004	A1
20040158351	Rivalto	Aug 2004	A1
20040172260	Junger et al.	Sep 2004	A1
20040181310	Stashluk et al.	Sep 2004	A1
20040199284	Hara	Oct 2004	A1
20040199656	Pintsov	Oct 2004	A1
20040211834	Fleckenstein et al.	Oct 2004	A1
20040215480	Kadaba	Oct 2004	A1
20040215588	Cornelius	Oct 2004	A1
20040254802	Miller et al.	Dec 2004	A1
20040254811	Horstemeyer	Dec 2004	A1
20040260470	Rast	Dec 2004	A1
20050004877	Mclellan et al.	Jan 2005	A1
20050006470	Mrozik et al.	Jan 2005	A1
20050027607	Pearson	Feb 2005	A1
20050038758	Hilbush et al.	Feb 2005	A1
20050060164	Eli Berl Illion	Mar 2005	A1
20050060165	Knight et al.	Mar 2005	A1
20050060228	Woo	Mar 2005	A1
20050061877	Stevens	Mar 2005	A1
20050068178	Lee et al.	Mar 2005	A1
20050071258	Kumakawa	Mar 2005	A1
20050075989	Biasi et al.	Apr 2005	A1
20050080635	Groff et al.	Apr 2005	A1
20050080638	Maseruka	Apr 2005	A1
20050097010	Carrender	May 2005	A1
20050104716	Simms et al.	May 2005	A1
20050116033	Moore	Jun 2005	A1
20050119786	Kadaba	Jun 2005	A1
20050120003	Drury et al.	Jun 2005	A1
20050131774	Huxter	Jun 2005	A1
20050137901	Siegel	Jun 2005	A1
20050138382	Hougaard et al.	Jun 2005	A1
20050149372	Kite et al.	Jul 2005	A1
20050216553	Mallonee et al.	Sep 2005	A1
20050218222	Nark et al.	Oct 2005	A1
20050222911	Kerker et al.	Oct 2005	A1
20050234911	Hess et al.	Oct 2005	A1
20050251402	Olsen et al.	Nov 2005	A1
20060010037	Angert et al.	Jan 2006	A1
20060010077	Dohrmann et al.	Jan 2006	A1
20060020366	Bloom	Jan 2006	A1
20060020489	Rivalto	Jan 2006	A1
20060041481	Stowe	Feb 2006	A1
20060041519	Ogg et al.	Feb 2006	A1
20060047610	Parkos et al.	Mar 2006	A1
20060069601	Simon et al.	Mar 2006	A1
20060085273	Mayer et al.	Apr 2006	A1
20060097896	Jones	May 2006	A1
20060149577	Stashluk et al.	Jul 2006	A1
20060224512	Kurakata	Oct 2006	A1
20060229895	Kodger, Jr.	Oct 2006	A1
20060235739	Levis et al.	Oct 2006	A1
20060238334	Mangan et al.	Oct 2006	A1
20060282277	Ng	Dec 2006	A1
20060287870	Mayer et al.	Dec 2006	A1
20070005452	Klingenberg et al.	Jan 2007	A1
20070016538	Bielefeld et al.	Jan 2007	A1
20070036117	Taube et al.	Feb 2007	A1
20070047459	Kadaba	Mar 2007	A1
20070062851	Schulz et al.	Mar 2007	A1
20070078797	Won et al.	Apr 2007	A1
20070083410	Hanna	Apr 2007	A1
20070095904	Barta et al.	May 2007	A1
20070124295	Forman et al.	May 2007	A1
20070143281	Smirin et al.	Jun 2007	A1
20070150533	Krause et al.	Jun 2007	A1
20070156415	Foth et al.	Jul 2007	A1
20070185598	Ortega	Aug 2007	A1
20070192191	Neal et al.	Aug 2007	A1
20070198290	Kinory et al.	Aug 2007	A1
20070198357	Ravazzolo	Aug 2007	A1
20070205278	Lovett	Sep 2007	A1
20070266081	Murchison et al.	Nov 2007	A1
20080004928	Trellevik et al.	Jan 2008	A1
20080004957	Hildreth et al.	Jan 2008	A1
20080004967	Gillen	Jan 2008	A1
20080004995	Klingenberg et al.	Jan 2008	A1
20080040133	Foth et al.	Feb 2008	A1
20080040246	Fukamachi	Feb 2008	A1
20080051995	Lokshin et al.	Feb 2008	A1
20080061966	Nelson	Mar 2008	A1
20080082346	Hoopes et al.	Apr 2008	A1
20080109246	Russell	May 2008	A1
20080121682	Grim et al.	May 2008	A1
20080133261	Ray	Jun 2008	A1
20080154781	Kumar	Jun 2008	A1
20080172305	Estes et al.	Jul 2008	A1
20080210749	Skaaksrud et al.	Sep 2008	A1
20080221913	Cook et al.	Sep 2008	A1
20080249830	Gilman et al.	Oct 2008	A1
20080270209	Mauseth et al.	Oct 2008	A1
20080301144	Boss et al.	Dec 2008	A1
20080313018	Kamm et al.	Dec 2008	A1
20080319970	Garner et al.	Dec 2008	A1
20080320092	Campbell et al.	Dec 2008	A1
20090001153	Lim	Jan 2009	A1
20090012802	Pinney	Jan 2009	A1
20090043552	Tomlinson et al.	Feb 2009	A1
20090046892	Avant et al.	Feb 2009	A1
20090063215	Heise et al.	Mar 2009	A1
20090076888	Oster et al.	Mar 2009	A1
20090106124	Yang	Apr 2009	A1
20090138730	Cook et al.	May 2009	A1
20090146832	Ebert et al.	Jun 2009	A1
20090164295	Sion	Jun 2009	A1
20090173672	Avant et al.	Jul 2009	A1
20090187489	Mallick et al.	Jul 2009	A1
20090222354	Murphy et al.	Sep 2009	A1
20090240597	Oswald	Sep 2009	A1
20090259509	Landvater	Oct 2009	A1
20090281929	Boitet et al.	Nov 2009	A1
20090314835	Jackson	Dec 2009	A1
20090319078	Jackson	Dec 2009	A1
20090326971	Piccinini et al.	Dec 2009	A1
20100004960	Frankenberg et al.	Jan 2010	A1
20100011238	Nakamura et al.	Jan 2010	A1
20100012769	Alber et al.	Jan 2010	A1
20100049536	Quine et al.	Feb 2010	A1
20100057592	Moir et al.	Mar 2010	A1
20100057593	Moir et al.	Mar 2010	A1
20100076903	Klingenberg et al.	Mar 2010	A1
20100100497	Kuebert et al.	Apr 2010	A1
20100114678	Axe et al.	May 2010	A1
20100121689	Wallace et al.	May 2010	A1
20100125494	Boss et al.	May 2010	A1
20100138281	Zhang et al.	Jun 2010	A1
20100162149	Sheleheda et al.	Jun 2010	A1
20100185565	Wade	Jul 2010	A1
20100211444	Spear	Aug 2010	A1
20100223127	Bettez et al.	Sep 2010	A1
20100223134	Lunenfeld	Sep 2010	A1
20100235290	Junger et al.	Sep 2010	A1
20100250291	Walker et al.	Sep 2010	A1
20100280955	Ross et al.	Nov 2010	A1
20100324959	Templeton et al.	Dec 2010	A1
20110004562	Hennessy et al.	Jan 2011	A1
20110029429	Whitehouse	Feb 2011	A1
20110084162	Goossen et al.	Apr 2011	A1
20110093361	Morales	Apr 2011	A1
20110125665	Kadaba	May 2011	A1
20110150013	Spinelli et al.	Jun 2011	A1
20110153513	Erie et al.	Jun 2011	A1
20110191697	Sumner et al.	Aug 2011	A1
20110246323	Mehta et al.	Oct 2011	A1
20110270714	Myrick et al.	Nov 2011	A1
20110287748	Angel et al.	Nov 2011	A1
20110288896	Dewey et al.	Nov 2011	A1
20120016948	Sinha	Jan 2012	A1
20120030124	Cronkright et al.	Feb 2012	A1
20120030133	Rademaker	Feb 2012	A1
20120047084	Naghshineh et al.	Feb 2012	A1
20120047085	Naghshineh et al.	Feb 2012	A1
20120062362	Rudduck et al.	Mar 2012	A1
20120089532	Kuebert et al.	Apr 2012	A1
20120095934	Klingenberg et al.	Apr 2012	A1
20120130625	Srivastava	May 2012	A1
20120130916	Neal et al.	May 2012	A1
20120166320	Junger	Jun 2012	A1
20120179622	Amato	Jul 2012	A1
20120185363	Gilbert	Jul 2012	A1
20120235786	Rudduck et al.	Sep 2012	A1
20120246077	Skaaksrud et al.	Sep 2012	A1
20120303539	Marcus et al.	Nov 2012	A1
20120303541	Marcus et al.	Nov 2012	A1
20120303542	Marcus et al.	Nov 2012	A1
20120310853	Aldstadt	Dec 2012	A1
20120330774	Sadot et al.	Dec 2012	A1
20130006731	Cook et al.	Jan 2013	A1
20130006885	Kuebert et al.	Jan 2013	A1
20130013101	Bonnell et al.	Jan 2013	A1
20130013102	Bonnell et al.	Jan 2013	A1
20130013350	McCullough et al.	Jan 2013	A1
20130016636	Berger et al.	Jan 2013	A1
20130018894	Qiao	Jan 2013	A1
20130018999	Merrill et al.	Jan 2013	A1
20130024307	Fuerstenberg et al.	Jan 2013	A1
20130054054	Tollenaere et al.	Feb 2013	A1
20130061337	Zimberoff et al.	Mar 2013	A1
20130073336	Heath	Mar 2013	A1
20130073605	Fosburgh et al.	Mar 2013	A1
20130088323	Ryan	Apr 2013	A1
20130144428	Irwin et al.	Jun 2013	A1
20130151419	Hitchcock et al.	Jun 2013	A1
20130166067	Irwin et al.	Jun 2013	A1
20130173484	Wesby	Jul 2013	A1
20130202185	Irwin et al.	Aug 2013	A1
20130238599	Burris	Sep 2013	A1
20130238658	Burris	Sep 2013	A1
20130246396	Clare et al.	Sep 2013	A1
20130261792	Gupta et al.	Oct 2013	A1
20130262311	Buhrmann et al.	Oct 2013	A1
20130262336	Wan et al.	Oct 2013	A1
20130268437	Desai et al.	Oct 2013	A1
20130284800	Gillen et al.	Oct 2013	A1
20130338822	Gibson et al.	Dec 2013	A1
20140034727	Hancock et al.	Feb 2014	A1
20140035721	Heppe et al.	Feb 2014	A1
20140052661	Shakes et al.	Feb 2014	A1
20140081677	Craig et al.	Mar 2014	A1
20140180959	Gillen et al.	Jun 2014	A1
20140214505	Shuster-Arechiga et al.	Jul 2014	A1
20140222711	Tibbs et al.	Aug 2014	A1
20140236688	Minter et al.	Aug 2014	A1
20140236778	Villardito	Aug 2014	A1
20140258098	Felix et al.	Sep 2014	A1
20140278602	Lievens et al.	Sep 2014	A1
20140278603	Lievens et al.	Sep 2014	A1
20140278691	Schenken	Sep 2014	A1
20140278843	Lievens et al.	Sep 2014	A1
20140278898	Lievens et al.	Sep 2014	A1
20140279648	Whitehouse	Sep 2014	A1
20140279650	Lievens et al.	Sep 2014	A1
20140279654	Lievens et al.	Sep 2014	A1
20140279658	Lievens et al.	Sep 2014	A1
20140279663	Lievens et al.	Sep 2014	A1
20140279664	Lievens et al.	Sep 2014	A1
20140279665	Lievens et al.	Sep 2014	A1
20140279666	Lievens et al.	Sep 2014	A1
20140279667	Gillen	Sep 2014	A1
20140279668	Lievens et al.	Sep 2014	A1
20140324725	Edmonds et al.	Oct 2014	A1
20140330407	Corder et al.	Nov 2014	A1
20140330603	Corder et al.	Nov 2014	A1
20140343724	Hoganson et al.	Nov 2014	A1
20150058163	Lenahan et al.	Feb 2015	A1
20150084750	Fitzgibbon	Mar 2015	A1
20150088694	Ackerman	Mar 2015	A1
20150088731	Ackerman	Mar 2015	A1
20150106291	Robinson et al.	Apr 2015	A1
20150106292	Robinson et al.	Apr 2015	A1
20150106293	Robinson et al.	Apr 2015	A1
20150106294	Robinson et al.	Apr 2015	A1
20150106295	Robinson et al.	Apr 2015	A1
20150106296	Robinson et al.	Apr 2015	A1
20150120602	Huffman et al.	Apr 2015	A1
20150138382	Xiao et al.	May 2015	A1
20150186840	Torres et al.	Jul 2015	A1
20150193731	Stevens et al.	Jul 2015	A1
20150230055	Smith et al.	Aug 2015	A1
20150348173	Gillen	Dec 2015	A1
20150356801	Nitu et al.	Dec 2015	A1
20160027261	Motoyama	Jan 2016	A1
20160071051	Tibbs et al.	Mar 2016	A1
20160098680	Schenken et al.	Apr 2016	A1
20160140486	Tibbs et al.	May 2016	A1
20160140487	Tibbs et al.	May 2016	A1
20160148154	Tibbs et al.	May 2016	A1
20160189466	Gibson et al.	Jun 2016	A1
20160224773	Ramaci	Aug 2016	A1
20170143145	Peynet	May 2017	A1
20170148059	Minter et al.	May 2017	A1
20170148243	Shin et al.	May 2017	A1
20170150304	Baldasare et al.	May 2017	A1
20170154483	Cordiner et al.	Jun 2017	A1
20170353943	Skaaksrud	Dec 2017	A1
20180005184	Schenken	Jan 2018	A1
20180025319	Lievens et al.	Jan 2018	A1
20180060800	Robinson	Mar 2018	A1
20180060812	Robinson et al.	Mar 2018	A1
20190102962	Miller	Apr 2019	A1
20190172011	Robinson et al.	Jun 2019	A1
20190354918	Tibbs et al.	Nov 2019	A1
20200134559	Lievens et al.	Apr 2020	A1

Foreign Referenced Citations (121)

Number	Date	Country
2014248927	Nov 2015	AU
2893502	Nov 2004	CA
2551885	Aug 2005	CA
1317758	Oct 2001	CN
1432946	Jul 2003	CN
1571975	Jan 2005	CN
1582447	Feb 2005	CN
1639716	Jul 2005	CN
1666214	Sep 2005	CN
1791475	Jun 2006	CN
1795461	Jun 2006	CN
101203873	Jun 2008	CN
101329752	Dec 2008	CN
101491051	Jul 2009	CN
101971201	Feb 2011	CN
102509199	Jun 2012	CN
102609783	Jul 2012	CN
102930655	Feb 2013	CN
202720725	Feb 2013	CN
103049855	Apr 2013	CN
103310323	Sep 2013	CN
103345791	Oct 2013	CN
203232495	Oct 2013	CN
103907126	Jul 2014	CN
1152356	Nov 2001	EP
1365198	Nov 2003	EP
2469291	Jun 2012	EP
2973202	Jan 2016	EP
2973292	Jan 2016	EP
2483474	Mar 2012	GB
2528818	Mar 2016	GB
62-121108	Jun 1987	JP
5-211684	Aug 1993	JP
6-40867	Jun 1994	JP
10-207956	Aug 1998	JP
11-18916	Jan 1999	JP
11-139540	May 1999	JP
11-151154	Jun 1999	JP
20003-39373	Dec 2000	JP
2001-014393	Jan 2001	JP
2001-022678	Jan 2001	JP
2001-282974	Oct 2001	JP
2001-291027	Oct 2001	JP
2001-338030	Dec 2001	JP
2002-042008	Feb 2002	JP
2002-056307	Feb 2002	JP
2002-092505	Mar 2002	JP
2002-109409	Apr 2002	JP
2002-157541	May 2002	JP
2002-245367	Aug 2002	JP
2002-259553	Sep 2002	JP
2002-288562	Oct 2002	JP
2003-196354	Jul 2003	JP
2003-263599	Sep 2003	JP
2003-321124	Nov 2003	JP
2004-030159	Jan 2004	JP
2004-234275	Aug 2004	JP
2004-280468	Oct 2004	JP
2004-338824	Dec 2004	JP
2005-043974	Feb 2005	JP
2006-512635	Apr 2006	JP
2006-277199	Oct 2006	JP
2007-016423	Jan 2007	JP
2007-153618	Jun 2007	JP
2008-542886	Nov 2008	JP
2008-303069	Dec 2008	JP
2009-029631	Feb 2009	JP
2009-230393	Oct 2009	JP
2010-128535	Jun 2010	JP
2011-118611	Jun 2011	JP
2012-071912	Apr 2012	JP
2012-138000	Jul 2012	JP
6151430	Jun 2017	JP
6268273	Jan 2018	JP
6449396	Jan 2019	JP
2001-0093768	Oct 2001	KR
2001-0098070	Nov 2001	KR
2002-0063776	Aug 2002	KR
10-2009-0001453	Jan 2009	KR
2000019170	Apr 2000	WO
2000019171	Apr 2000	WO
2000030014	May 2000	WO
2000046726	Aug 2000	WO
2000046728	Aug 2000	WO
2000052422	Sep 2000	WO
2001072109	Jan 2001	WO
2001008071	Feb 2001	WO
2001016889	Mar 2001	WO
2001020423	Mar 2001	WO
2001029778	Apr 2001	WO
2001035344	May 2001	WO
2001039031	May 2001	WO
2001065451	Sep 2001	WO
2001065454	Sep 2001	WO
2001065523	Sep 2001	WO
2001065524	Sep 2001	WO
2001067344	Sep 2001	WO
2001084359	Nov 2001	WO
2001088831	Nov 2001	WO
2001097101	Dec 2001	WO
2002007104	Jan 2002	WO
2002017045	Feb 2002	WO
2002052378	Jul 2002	WO
2002073369	Sep 2002	WO
2002080436	Oct 2002	WO
2003023688	Mar 2003	WO
2003040979	May 2003	WO
2004015518	Feb 2004	WO
2004042523	May 2004	WO
2005072328	Aug 2005	WO
2007055769	May 2007	WO
2010123611	Oct 2010	WO
2011074500	Jun 2011	WO
2012129529	Sep 2012	WO
2013106940	Jul 2013	WO
2014031691	Feb 2014	WO
2014142951	Sep 2014	WO
2014164825	Oct 2014	WO
2014164839	Oct 2014	WO
2014164853	Oct 2014	WO
2016027178	Feb 2016	WO

Non-Patent Literature Citations (62)

Entry
“Delivering the Goods; Delivery Lockers.” The Economist (London) 404.8799 (2012): 52-. Print. (Year: 2012).
Final Office Action received for U.S. Appl. No. 14/514,000, dated Mar. 30, 2020, 34 pages.
Final Office Action received for U.S. Appl. No. 14/200,724, dated Jun. 2, 2020, 13 pages.
Final Office Action received for U.S. Appl. No. 14/942,757, dated Jun. 18, 2020, 26 pages.
Office Action received for Canadian Patent Application No. 2,905,833, dated Jun. 8, 2020, 6 pages.
Office Action received for Chinese Patent Application No. 201580067558.4, dated Apr. 28, 2020, 42 pages (27 pages of English Translation and 15 pages of Official copy).
Office Action received for Malaysian Patent Application No. PI2015002355, dated Jun. 30, 2020, 6 pages.
“ASP V16-System Walker List Works Manual”, line 5, 3.4 Start up and termination of ListWORKS writer, p. 88.
Brewin et al., “Follow that Package!”, Article, ComputerWorld, Available online at: <www.computerworld.com/printthis/2001/0,4814,58696,00.html>, Mar. 19, 2001, pp. 1-5.
Caminiti et al., “United Parcel Service Introduces Advanced Label Imaging System”, Business Wire, Section 1, Nov. 29, 1989, pp. 1-3.
Chung et al., “Optimal Replenishment Policies for EOQ Inventory Model with Limited Storage Capacity Under Permissible Delay in Payments”, Opsearch 41.1, 2004, 23 pages.
DeMarco, Donna, “E-tail Presents Can be Tougher to Send Back than Order”, Journal, Knight-Ridder/Tribune Business News, The Dialog Corporation, US, Dec. 28, 1999, 2 pages.
El Portal Del Transporte, “Fedex Insight Empowers Customers with Enhanced Shipment Visibility and Control”, Article, Available online at: <http://www.transportando.net/newsabri1_completa.htm>, Apr. 11, 2001, pp. 9-10.
Fedex, “RPS Adds Automated Package Pick-up to Redesigned Web Site”, Available online at: <www.fedex.com/us/about/ground/pressreleases/pressrelease111198.html?link=4>, Retrieved on Sep. 10, 2003. 1 page.
Fedex, “FedEx Mobile Ship”, Available online at: <http://www.fedex.com/us/mobile/label.html>, redirected to <http://mobilesolutions.fedex.com/shipping-label.html>, Retrieved on Sep. 25, 2013, 2 pages.
Fedex, “Mobile Shipping Label”, Available online at: <www.mobilesolutions.fedex.com/shipping-label.html>, Retrieved on Sep. 25, 2013, pp. 1-2.
Pender, Lee, “Hard Times are the Best Times”, Magazine, Cio, Available online at: <www.cio.com/archive/081501/besttimes_content.html>, Aug. 15, 2001, pp. 3-7.
Raco Industries, “Increase Delivery Visibility and Simplify Your Process”, Available online at: <http://www.racointeractive.com/media/834/raco_interactive-pd.pdf>, Retrieved on Sep. 25, 2013, 2 pages.
“SEP leads €26 million funding round for Kiala”, SEP Scottish Equity Partners, Available online at: <http://www.sep.co.uk/news/story/sep-leads-e26-million-funding-round-for-kiala-2/>, Nov. 30, 2007, 2 pages.
Van Huzien, Gordon, “Messaging: The Transport Part of The XML Puzzle”, IBM Developer Works, Article, Available online at: <http:/ /www-106.ibm.com/developerworks/library/xml-messaging/>, Jul. 2000, 8 pages.
Frontline Solutions, Fed Ex “Improves Internal, External Operations”, Article, Fairfax, Virginia and Memphis, Tennessee, Available online at: <http://www.frintlinemagazine.com/art_th/04052001.htx>, Apr. 5, 2001, pp. 1-2.
Gao et al., “Cyber-Physical-Social Systems: Harnessing the Crowd sourcing Power of Social Media for Disaster Relief”, IEEE Intelligent Systems, IEEE Computer Society, 2011, pp. 10-14.
Harrington, Lisa, “The US Postal Service Gets Serious about Serving Business in the New Economy”, Transportation & Distribution, vol. 41, No. 5, Penton Publishing, Inc., United States of America, May 2000, p. 2.
Henderson, Timothy P., “Scheduling Software Helps Webvan Meet 30-Minute Delivery Window, Descartes”, Available online at: <www.stores.org>, Jul. 2000, 2 pages.
Henderson, Timothy P, “Buy.com Boosts Returns Process Efficiency with New Solution”, ProQuest Info & Learning, vol. 82, No. 11, Nov. 2000, pp. 72-76.
“Outlook 2000 Handbook First Edition”, last 9 lines, 2000, p. 95.
IPVENTURE, “Schedule Distribution Routes and Timeslots”, Available online at: <https://www.ipventure.com/onlineorder/distribution.php>, Retrieved on Apr. 16, 2008, 1 page.
Kihon, Kara J., “Made Business Seikou No Tameno Kanpeki Guide—How to E-Commerce”, p. 60.
Lindsay, Bruce R., “Congressional Research Service, Social Media and Disasters: Current Uses, Future Options, and Policy Considerations”, CRS Report for Congress, Congressional Research Service, Sep. 6, 2011, 10 pages.
“Many Happy Returns—UPS Unveils Advanced Outline Returns Solution”, Accession No. 12921102, Business Wire, Sep. 20, 2000, 3 pages.
McNamara, Paul, “‘Doorman’ kiosk accepts package deliveries when you're not home”, Networkworld, Buzzblog, Available online at: <https://www.networkworld.com/article/2348365/data-center/-doorman-kiosk-accepts-package-deliveries-when-you-re-not-home.html>, Aug. 8, 2007, 4 pages.
Guler, N., “Containerization and Terminal Area Requirements”, Istanbul Technical University, Maritime Faculty, Available online at: <https://hrcak.srce.hr/file/82785>, Jul. 2002, 20 pages.
Otto et al., “A Framework for Cyber-Enhanced Retailing: Integrating e-Commerce Retailing with Brick-and-Mortar Retailing”, Electronic Markets, vol. 10, No. 3, Jan. 2000, 8 pages.
Final Office Action received for U.S. Appl. No. 14/514,000, dated Sep. 20, 2021, 37 pages.
Non-Final Office Action received for U.S. Appl. No. 15/252,629, dated Oct. 5, 2021, 24 pages.
Notice of Allowance received for Chinese Patent Application No. 201580067558.4, dated Sep. 15, 2021, 7 pages (3 pages of English Translation and 4 pages of Official copy).
Final Office Action received for U.S. Appl. No. 14/942,731, dated Jul. 28, 2021, 36 pages.
Locker Security Gets Smart, Security, Available online at: <https://www.securitymagazine.com/>, 2010, 3 pages.
Notice of Allowance received for U.S. Appl. No. 16/267,915, dated Jul. 20, 2021, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 14/514,000, dated Mar. 11, 2021, 34 pages.
Final Office Action received for U.S. Appl. No. 14/200,724, dated May 19, 2021, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 14/942,757, dated Feb. 3, 2022, 26 pages.
Preinterview First Office Action received for U.S. Appl. No. 16/529,393, dated Mar. 18, 2022, 46 pages.
The PostN ET Bar Code, Jay's Comer, Available on Internet at: <http://math.ucdenver.edu/-wcherowi/jcorner/barcodes.html> (<http://web.archive.org/web/20111013195734/http://math.ucdenver.edu/-wcherowi/jcorner/barcodes.html>), Oct. 13, 2022, 4 pages.
Final Office Action received for U.S. Appl. No. 14/514,228, dated Jul. 27, 2020, 38 pages.
Final Office Action received for U.S. Appl. No. 14/561,062, dated Aug. 25, 2020, 49 pages.
Office Action received for Chinese Patent Application No. 201480026787.7, dated Jul. 21, 2020, 13 pages (8 pages of English Translation and 5 pages of Official copy).
Office Action received for Malaysian Patent Application No. PI2015002353, dated Jul. 30, 2020, 3 pages.
Ding et al., “Return Management in E-commerce Reverse Logistics Management”, Logistics and Material Handling, Mar. 31, 2004, pp. 86-88 (Official copy only) (See attached communication 37 CFR § 1.98(a) (3)).
“Order Return Classification and Process 01”, Available online at: <https://wenku.baidu.com/view/757de525192e45361066f567.html>, Nov. 8, 2012, 7 pages (Official copy only) (See attached communication 37 CFR § 1.98(a) (3)).
Non-Final Office Action received for U.S. Appl. No. 14/200,724, dated Dec. 1, 2020, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 15/252,629, dated Nov. 13, 2020, 28 pages.
Office Action received for Malaysian Patent Application No. PI2015002350, dated Sep. 22, 2020, 2 pages.
Final Office Action received for U.S. Appl. No. 14/200,724, dated Jun. 8, 2022, 13 pages.
Steinfield et al., “Integrating Brick and Mortar Locations with E-commerce: Understanding Synergy Opportunities”, Proceedings of the 35th Hawaii International Conference on System Sciences, 2002, Available online at: <https://www.researchgate.net/publication/232657084_Integrating_Brick_and_Mortar_Locations_with_E-commerce_Understanding_Synergy_Opportunities_PDF>, Jan. 2002, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 16/730,269, dated Apr. 13, 2022, 20 pages.
Office Action received for Malaysian Patent Application No. PI2015002360, dated Apr. 1, 2022, 3 pages.
Final Office Action received for U.S. Appl. No. 14/942,731, dated Aug. 25, 2022, 12 pages.
Final Office Action received for U.S. Appl. No. 14/942,757, dated Sep. 6, 2022, 23 pages.
Final Office Action received for U.S. Appl. No. 16/529,393, dated Dec. 2, 2022, 55 pages.
GPS Comes To High-Tech Pizza-Delivery Tracking; One Papa John's chain lets customers track their deliveries street by street. Domino's, meanwhile, is making its own tracking technology push, Information Week: NA. CMP Media, Inc., Feb. 1, 2008, 2 pages.
Notice of Allowance received for U.S. Appl. No. 17/027,406, dated Dec. 5, 2022, 11 pages.

Related Publications (1)

	Number	Date	Country
	20200219057 A1	Jul 2020	US

Continuations (1)

	Number	Date	Country
Parent	15253473	Aug 2016	US
Child	16825323		US

Systems and methods for synchronizing delivery of related parcels via computerized locker bank

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Term Extension

Abstract