Determining alternative delivery destinations

Description

BACKGROUND

Shipping customers are increasing their expectations regarding various delivery services and value. Thus, new concepts are needed to enhance customer experience and loyalty by improving delivery services and value. Carriers have long tried to optimize how parcel deliveries are scheduled with end consignees to both improve delivery time and lower costs for both the customer and carrier. For example, existing systems may allow consignees to redirect parcel during transit when the consignee knows they are going to be away from the delivery address instead of requiring the carrier to make a second trip. While these systems have merit they do not adequately address other issues/opportunities created by advancements in technology and continued evolution in consignee mobility. In this regard, areas for improving current systems have been identified. Through applied effort, ingenuity, and innovation, solutions to improve such systems have been realized and are described in connection with embodiments of the present invention.

BRIEF SUMMARY

In general, embodiments of the present invention provide systems, methods, apparatus, and computer program products for determining alternative delivery destinations, such as directing a scheduled delivery to an alternate consignee.

In some embodiments, a method may be provided for determining alternative delivery destinations, the method comprising receiving shipping information for an item, the shipping information indicating the item to be delivered to an original consignee by a carrier and comprising at least a default delivery location, and determining whether the original consignee has indicated a first priority alternative consignee among one or more alternative consignees. In some embodiments, the method may further comprise in an instance in which a determination is made that the original consignee has indicated the first priority alternative consignee among the one or more alternative consignees, delivering the item to the first priority alternative consignee.

In some embodiments, the method may further comprise determining, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, and in an instance in which the original consignee has not elected to enable shipments to be delivered to at least one alternative consignee, providing a user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of the first priority alternative consignee. In some embodiments, the method may further comprise determining, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, and in an instance in which the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, determining the first priority alternative consignee.

In some embodiments, the method may further comprise determining whether the first priority alternative consignee is available to receive the item, in an instance in which the first priority alternative consignee is not available to receive the item, delivering the item to the first priority alternative consignee, in an instance in which the first priority alternative consignee is not available to receive the item, determining a second priority alternative consignee, determining whether the second priority alternative consignee is available to receive the item, and in an instance in which the second priority alternative consignee is available to receive the item, delivering the item to the second priority alternative consignee. In some embodiments, the method may further comprise providing, via the network, to the client device, notification that the item was delivered, the notification comprising information indicative of which of the one or more alternative consignees to which the item was delivered, providing, via the network, to the client device, a user interface configured to receive confirmation.

In some embodiments, the method may further comprise providing, via the network, to the client device, a user interface configured to enable the original consignee to indicate that the shipment should be delivery to the default location. In some embodiments, the method may further comprise providing, via the network, to the client device, a user interface configured to enable the original consignee to register as one of the one or more alternative consignees, enabling other original consignees to select the original consignee as one of their alternative consignees.

In some embodiments, an apparatus for determining alternative delivery destinations may be provided, the apparatus comprising at least one processor and at least one memory including program code, the at least one memory and the program code configured to, with the processor, cause the apparatus to at least receive shipping information for an item, the shipping information indicating the item to be delivered to an original consignee by a carrier and comprising at least a default delivery location, and determine whether the original consignee has indicated a first priority alternative consignee among one or more alternative consignees.

In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to in an instance in which a determination is made that the original consignee has indicated the first priority alternative consignee among the one or more alternative consignees, deliver the item to the first priority alternative consignee. In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to determine, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, and in an instance in which the original consignee has not elected to enable shipments to be delivered to at least one alternative consignee, provides user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of the first priority alternative consignee.

In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to determine, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, and in an instance in which the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, determine the first priority alternative consignee. In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to determine whether the first priority alternative consignee is available to receive the item, in an instance in which the first priority alternative consignee is not available to receive the item, deliver the item to the first priority alternative consignee, in an instance in which the first priority alternative consignee is not available to receive the item, determine a second priority alternative consignee, determine whether the second priority alternative consignee is available to receive the item, and in an instance in which the second priority alternative consignee is available to receive the item, deliver the item to the second priority alternative consignee.

In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to provide, via the network, to the client device, notification that the item was delivered, the notification comprising information indicative of which of the one or more alternative consignees to which the item was delivered, and provide, via the network, to the client device, a user interface configured to receive confirmation.

In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to provide, via the network, to the client device, a user interface configured to enable the original consignee to indicate that the shipment should be delivery to the default location.

In some embodiments, the memory and program code are further configured to, with the processor, cause the apparatus to provide, via the network, to the client device, a user interface configured to enable the original consignee to register as one of the one or more alternative consignees, enabling other original consignees to select the original consignee as one of their alternative consignees.

In some embodiments, a computer program product for determining alternative delivery destinations may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising an executable portion configured to receive shipping information for an item, the shipping information indicating the item to be delivered to an original consignee by a carrier and comprising at least a default delivery location, and an executable portion configured to determine whether the original consignee has indicated a first priority alternative consignee among one or more alternative consignees.

In some embodiments, the computer program product may further comprise an executable portion configured to, in an instance in which a determination is made that the original consignee has indicated the first priority alternative consignee among the one or more alternative consignees, deliver the item to the first priority alternative consignee. In some embodiments, the computer program product may further comprise an executable portion configured to determine, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, and an executable portion configured to, in an instance in which the original consignee has not elected to enable shipments to be delivered to at least one alternative consignee, provide a user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of the first priority alternative consignee.

In some embodiments, the computer program product may further comprise an executable portion configured to determine, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, and an executable portion configured to, in an instance in which the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, determine the first priority alternative consignee.

In some embodiments, the computer program product may further comprise an executable portion configured to determine whether the first priority alternative consignee is available to receive the item, an executable portion configured to, in an instance in which the first priority alternative consignee is not available to receive the item, deliver the item to the first priority alternative consignee, an executable portion configured to, in an instance in which the first priority alternative consignee is not available to receive the item, determine a second priority alternative consignee, an executable portion configured to determine whether the second priority alternative consignee is available to receive the item, and an executable portion configured to, in an instance in which the second priority alternative consignee is available to receive the item, deliver the item to the second priority alternative consignee. In some embodiments, the computer program product may further comprise an executable portion configured to provide, via the network, to the client device, notification that the item was delivered, the notification comprising information indicative of which of the one or more alternative consignees to which the item was delivered, and an executable portion configured to provide, via the network, to the client device, a user interface configured to receive confirmation.

In some embodiments, the computer program product may further comprise an executable portion configured to provide, via the network, to the client device, a user interface configured to enable the original consignee to indicate that the shipment should be delivery to the default location. In some embodiments, the computer program product may further comprise an executable portion configured to provide, via the network, to the client device, a user interface configured to enable the original consignee to register as one of the one or more alternative consignees, enabling other original consignees to select the original consignee as one of their alternative consignees.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is an overview of a system that can be used to practice embodiments of the present invention.

FIG. 2 is an exemplary schematic diagram of a carrier system according to one embodiment of the present invention.

FIG. 3 is an exemplary schematic diagram of a mobile station according to one embodiment of the present invention.

FIGS. 4 and 5 show flowcharts illustrating operations and processes that can be used in accordance with various embodiments of the present invention.

FIG. 6 shows exemplary input and output of various embodiments of the present invention;

FIG. 7 shows a flowchart illustrating operations and processes that can be used in accordance with various embodiments of the present invention;

FIGS. 8A and 8B show exemplary input and output of various embodiments of the present invention; and

FIGS. 9-11 show flowcharts illustrating operations and processes that can be used in accordance with various embodiments of the present invention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, these inventions 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 satisfy applicable legal requirements. The term “or” is used herein in both the alternative and conjunctive sense, unless otherwise indicated. The terms “illustrative” and “exemplary” are used to be examples with no indication of quality level. Like numbers refer to like elements throughout.

I. Methods, Apparatus, Systems, and Computer Program Products

As should be appreciated, various embodiments may be implemented in various ways, including as methods, apparatus, systems, or computer program products. Accordingly, various embodiments may take the form of an entirely hardware embodiment or an embodiment in which a processor is programmed to perform certain steps. Furthermore, various implementations may take the form of a computer program product on a computer-readable storage medium having computer-readable program instructions embodied in the storage medium. Any suitable computer-readable storage medium may be utilized including hard disks, CD-ROMs, optical storage devices, or magnetic storage devices.

Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatus, systems, and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, respectively, may be implemented in part by computer program instructions, e.g., as logical steps or operations executing on a processor in a computing system. These computer program instructions may be loaded onto a computer, such as a special purpose computer or other programmable data processing apparatus to produce a specifically-configured machine, such that the instructions which execute on the computer or other programmable data processing apparatus implement 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 including computer-readable instructions for implementing the functionality 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 operations for implementing the functions specified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrations support various combinations for performing the specified functions, combinations of operations 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 operations, or combinations of special purpose hardware and computer instructions.

II. Exemplary System Architecture

FIG. 1 provides an illustration of a system that can be used in conjunction with various embodiments of the present invention. As shown in FIG. 1, the system may include one or more carrier systems 100, one or more mobile stations 105, one or more consignee computing devices 110, and one or more networks 115, and one or more consignor computing devices 120. Each of the components of the system may be in electronic communication with, for example, one another over the same or different wireless or wired networks including, for example, a wired or wireless Personal Area Network (PAN), Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), or the like. Additionally, while FIG. 1 illustrates certain communication system entities as separate, standalone entities, the various embodiments are not limited to this particular architecture.

1. Exemplary Carrier System

FIG. 2 provides an exemplary schematic of a carrier system 100 according to one embodiment of the present invention. A carrier may be a traditional carrier, such as United Parcel Service (UPS), FedEx, DHL, courier services, the United States Postal Service (USPS), Canadian Post, freight companies (e.g. truck-load, less-than-truckload, rail carriers, air carriers, ocean carriers, etc.), and/or the like. However, a carrier may also be a nontraditional carrier, such as Amazon, Google, Uber, ride-sharing services, crowd-sourcing services, retailers, and/or the like. In general, the term “system” may refer to, for example, one or more computers, computing entities, computing devices, mobile phones, gaming consoles (e.g., Xbox, Play Station, Wii), desktops, tablets, notebooks, laptops, distributed systems, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and/or any combination of devices or entities adapted to perform the functions, operations, and/or processes described herein. However, the carrier system 100 may also comprise various other systems, such as an Address Matching System (AMS), an Internet Membership System (IMS), a Customer Profile System (CPS), a Package Center information/data System (PCIS), a Customized Pick-up and Delivery System (CPAD), a Web Content Management System (WCMS), a Notification Email System (NES), a Fraud Prevention System (FPS), and a variety of other systems and their corresponding components. The carrier system 100 may also be in communication with various payment networks/systems for carrying out or facilitating the payment of fees. As will be recognized, the payment of such fees may be in a variety of forms, such as via debit cards, credit cards, direct credits, direct debits, cash, check, money order, Internet banking, e-commerce payment networks/systems (e.g., PayPal™, Google Wallet, Amazon Payments), virtual currencies (e.g., Bitcoins), award or reward points, and/or the like.

As will be understood from FIG. 1, in one embodiment, the carrier system 100 includes one or more processors 205 that communicate with other elements within the carrier system 100 via a system interface or bus 261. The processor 205 may be embodied in a number of different ways. For example, the processor 205 may be embodied as a processing element, processing circuitry, a coprocessor, a controller or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a hardware accelerator, or the like.

In an exemplary embodiment, the processor 205 may be configured to execute instructions stored in memory or otherwise accessible to the processor 205. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 205 may represent an entity capable of performing operations according to embodiments of the present invention when configured accordingly. A display device/input device 264 for receiving and displaying data may also be included in the carrier system 100. This display device/input device 264 may be, for example, a keyboard or pointing device that is used in combination with a monitor. The carrier system 100 may further include transitory and non-transitory memory 263, which may include both random access memory (RAM) 267 and read only memory (ROM) 265. The carrier system's ROM 265 may be used to store a basic input/output system (BIOS) 226 containing the basic routines that help to transfer information/data to the different elements within the carrier system 100.

In addition, in one embodiment, the carrier system 100 may include at least one storage device 268, such as a hard disk drive, a CD drive, and/or an optical disk drive for storing information/data on various computer-readable media. The storage device(s) 268 and its associated computer-readable media may provide nonvolatile storage. The computer-readable media described above could be replaced by any other type of computer-readable media, such as embedded or removable multimedia memory cards (MMCs), secure digital (SD) memory cards, Memory Sticks, electrically erasable programmable read-only memory (EEPROM), flash memory, hard disk, or the like. Additionally, each of these storage devices 268 may be connected to the system bus 261 by an appropriate interface.

Furthermore, a number of executable instructions, applications, program modules, and/or the like may be stored by the various storage devices 268 and/or within RAM 267. Such executable instructions, applications, program modules, and/or the like may include an operating system 280, a registration module 270, an alert module 260, a delivery options module 250, an identification module 245, a service schedule module, and/or the like. As discussed in more detail below, these executable instructions, applications, program modules, and/or the like may control certain aspects of the operation of the carrier system 100 with the assistance of the processor 205 and operating system 280—although their functionality need not be modularized. In addition to the program modules, the carrier system 100 may store or be in communication with one or more databases, such as database 240.

Also located within the carrier system 100, in one embodiment, is a network interface 274 for interfacing with various computing entities (e.g., with one or more mobile stations 105). For example, the carrier system 100 may be able to receive data and/or messages from and transmit data and/or messages to the mobile station 105, consignee computing devices 110, and consignor computing devices 120. This communication may be via the same or different wired or wireless networks (or a combination of wired and wireless networks). For instance, the communication may be executed using a wired data transmission protocol, such as fiber distributed data interface (FDDI), digital subscriber line (DSL), Ethernet, asynchronous transfer mode (ATM), frame relay, data over cable service interface specification (DOCSIS), or any other wired transmission protocol. Similarly, the carrier system 100 may be configured to communicate via wireless external communication networks using any of a variety of protocols, such as 802.11, general packet radio service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA2000 1× (1×RTT), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX), ultra wideband (UWB), infrared (IR) protocols, Bluetooth™ protocols, near field communication (NFC) protocols, wireless universal serial bus (USB) protocols, and/or any other wireless protocol.

It will be appreciated that one or more of the carrier system's 100 components may be located remotely from other carrier system 100 components. Furthermore, one or more of the components may be combined and additional components performing functions described herein may be included in the carrier system 100.

2. Exemplary Mobile Station

FIG. 3 provides an illustrative schematic representative of a mobile station 105 that can be used in conjunction with the embodiments of the present invention. Mobile stations 105 can be operated by various parties, including carrier personnel (e.g., delivery drivers, sorters, and/or the like). As shown in FIG. 3, the mobile station 105 can include an antenna 312, a transmitter 304 (e.g., radio), a receiver 306 (e.g., radio), and a processing device 308 (e.g., a processor, controller, and/or the like) that provides signals to and receives signals from the transmitter 304 and receiver 306, respectively.

The signals provided to and received from the transmitter 304 and the receiver 306, respectively, may include signaling information/data in accordance with an air interface standard of applicable wireless systems. In this regard, the mobile station 105 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the mobile station 105 may operate in accordance with any of a number of wireless communication standards and protocols, such as those described above with regard to the carrier system 100. In a particular embodiment, the mobile station 105 may operate in accordance with multiple wireless communication standards and protocols (e.g., using a Gobi radio), such as such as 802.11, GPRS, UMTS, CDMA2000, 1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR, Bluetooth™, NFC, wireless USB protocols, and/or any other wireless protocol and/or multiple wireless carriers. To do so, the mobile station 105 may include integrated mobile reception diversity and integrated power management. Such a configuration can provide for global connectivity to the user.

Via these communication standards and protocols, the mobile station 105 can communicate with various other entities using concepts such as Unstructured Supplementary Service Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber Identity Module Dialer (SIM dialer). The mobile station 105 can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including executable instructions, applications, program modules), and operating system.

According to one embodiment, the mobile station 105 may include a location determining device and/or functionality. For example, the mobile station 105 may include a Global Positioning System (GPS) module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, and/or speed data. In one embodiment, the GPS module acquires data, sometimes known as ephemeris data, by identifying the number of satellites in view and the relative positions of those satellites.

The mobile station 105 may also comprise a user interface (that can include a display 316 coupled to a processing device 308) and/or a user input interface (coupled to the processing device 308). The user input interface can comprise any of a number of devices allowing the mobile station 105 to receive data, such as a keypad 318, a touch display, voice or motion interfaces, or other input device. In embodiments including a keypad 318, the keypad 318 can include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the mobile station 105 and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface can be used, for example, to activate or deactivate certain functions, such as screen savers and/or sleep modes.

The mobile station 105 can also include volatile memory 322 and/or non-volatile memory 324, which can be embedded and/or may be removable. For example, the non-volatile memory may be embedded or removable MMCs, secure digital SD memory cards, Memory Sticks, EEPROM, flash memory, hard disk, or the like. The memory can store any of a number of pieces or amount of information/data and data used by the mobile station 105 to implement the functions of the mobile station 105. The memory can also store content, such as computer program code for an application and/or other computer programs.

3. Exemplary Consignee Computing Device

The consignee computing devices 110 may each include one or more components that are functionally similar to those of the carrier system 100 and/or mobile station 105. For example, in one embodiment, each of the consignee computing devices may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a user interface; (3) transitory and non-transitory memory; and (4) a communications interface. As noted, the consignee computing device 110 may comprise a user interface (that can include a display device/input device coupled to a processing element 308) and/or a user input interface (coupled to a processing element 308). For example, the user interface may be a carrier application, browser, user interface, dashboard, webpage, and/or similar words used herein interchangeably executing on and/or accessible via the consignee computing device 110 to interact with and/or cause display of information/data from the carrier system 100, as described herein. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments. In general, the terms device, system, computing entity, entity, and/or similar words used herein interchangeably may refer to, for example, one or more computers, computing entities, mobile phones, desktops, tablets, notebooks, laptops, distributed systems, gaming consoles (e.g., Xbox, Play Station, Wii), watches, glasses, key fobs, radio frequency identification (RFID) tags, ear pieces, scanners, cameras, wristbands, kiosks, input terminals, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and/or any combination of devices or entities adapted to perform the functions, operations, and/or processes described herein. A customer may refer to either a consignor (e.g., a party shipping an item via carrier) or a consignee (e.g., a party receiving an item from a carrier). In the returns context, a consignee who received an item can become a consignor when returning an item.

4. Exemplary Consignor Computing Device

The consignor computing devices 120 may each include one or more components that are functionally similar to those of the carrier system 100, mobile station 105, and/or consignee computing device 110. For example, in one embodiment, each of the consignor computing devices may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a user interface; (3) transitory and non-transitory memory; and (4) a communications interface. As noted, the consignor computing device 120 may comprise a user interface (that can include a display device/input device coupled to a processing element 308) and/or a user input interface (coupled to a processing element 308). For example, the user interface may be a carrier application, browser, user interface, dashboard, webpage, and/or similar words used herein interchangeably executing on and/or accessible via the consignor computing device 120 to interact with and/or cause display of information/data from the carrier system 100, as described herein. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments. A customer may refer to a consignor (e.g., a party shipping an item via carrier), a consignee (e.g., a party receiving an item from a carrier) a third party, and/or the like. In the returns context, a consignor who shipped an item can become a consignee when an item is being returned.

III. Exemplary System Operation

Reference will now be made to FIGS. 4-11. FIGS. 4, 5, 7, and 9-11 are flowcharts illustrating operations and processes that may be performed for customer controlled management of shipments. FIGS. 6, 8A, and 8B show exemplary input and output for determining alternative delivery destinations, such as directing a scheduled delivery to an alternate consignee.

1. Registration Process

FIG. 4 shows a flowchart illustrating a process that may be performed by a carrier system to register and/or enroll a customer (e.g., e.g., consignor, consignee, third party, and/or the like) into a program enabling alternative delivery destinations, such as, for example, an “Alternate Consignee Delivery Network” or the like. FIG. 5 then shows a flowchart illustrating a process that may be performed by a carrier system to enable a customer (e.g., consignor, consignee, third party, and/or the like) to select alternative delivery destinations utilizing, for example, an “Alternate Consignee Delivery Network” or the like. Referring back to FIG. 4, as is shown in operation 405, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for executing enrollment/registration for a program enabling/allowing shipments to be delivered to a repository/alternative consignee (e.g., an “Alternate Consignee Delivery Network”).

A customer (e.g., consignor, consignee, third party, and/or the like) may be an individual, a family, a company, an organization, an entity, a department within an organization, a representative of an organization and/or person, and/or the like. To register, a customer (e.g., a customer or customer representative operating a consignee computing device 110 or consignor computing device 120) may access a webpage, application, dashboard, browser, or portal of a carrier, such as United Parcel Service of America, Inc. (UPS). For instance, the carrier system 100 may provide a webpage that provides the customer with an option of logging into a customer account or enrolling/registering for a customer pick-up, delivery, and/or returns program.

In one embodiment, as part of the enrollment/registration process, the customer (e.g., operating a consignee computing device 110 or consignor computing device 120) may be requested to provide biographic and/or geographic information/data by the carrier system 100 (e.g., via the registration module 270). Such information/data may be manually input or provided by allowing access to other accounts, such as Facebook, Gmail, Twitter, PayPal, and/or the like. For instance, the customer may provide the customer's name, such as a first name, a last name, a company name, an entity name, and/or an organization name. The customer may also provide any aliases associated with the customer. For instance, if the customer were an individual named Joseph Brown, the customer may provide Joe Brown or Joey Brown as aliases.

The customer may also provide one or more physical addresses associated with the customer (e.g., street address, city, state, postal code, and/or country) to the carrier system 100. For instance, Joseph Brown's primary residential address of 105 Main Street, Atlanta, Ga. 30309, USA, may be provided to the carrier system 100. Further, one or more secondary residential addresses may also be provided to the carrier system 100 for association with Mr. Brown's account and profile, such as 71 Lanier Islands, Buford, Ga. 30518, USA. As will be recognized, the residential addresses may include weekend residences, family member residences visited by the customer, and/or the like. Additionally, the customer may also provide one or more business addresses associated with the customer (e.g., street address, city, state, postal code, and/or country) to the carrier system 100. For example, Mr. Brown may have a primary business address of 1201 W Peachtree, Atlanta, Ga. 30309, USA. One or more secondary business addresses may also be provided to the carrier system 100 for association with Mr. Brown's account and profile, such as 101 South Tryon Street, Charlotte, N.C. 28280, USA; 950 F Street, NW, Washington, D.C. 20004, USA; and 90 Park Avenue, New York, N.Y. 10016, USA. As will be recognized, the business addresses may include various office locations for a single enterprise, multiple office locations for various enterprises, and/or the like. As will be recognized, the customer may provide other biographic and/or geographic information/data to adapt to various needs and circumstances.

In one embodiment, once the carrier system 100 receives the necessary biographic and/or geographic information/data from the customer, the carrier system 100 may perform one or more validation operations. For example, the carrier system 100 may determine whether the primary address (and/or other addresses) in the specified country or postal code is eligible for an “Alternate Consignee Delivery Network” or the like. The carrier system 100 may also determine whether the primary address (and/or other addresses) is valid, e.g., by passing the primary address through one or more address cleansing or standardization systems. The carrier system 100 may perform a variety of fraud prevention measures as well, such as determining whether the customer (e.g., consignor or consignee) or one of the customer's addresses has been “blacklisted” from customer pick-up, delivery, and/or returns programs. As will be recognized, a variety of other approaches and techniques can be used to adapt to various needs and circumstances.

In one embodiment, the carrier system 100 may create a customer profile for the customer via the enrollment/registration process. Accordingly, the carrier system 100 may create and store various customer profiles (e.g., via database 240). In addition to at least the information/data described above, a customer profile may include one or more corresponding usernames and passwords. As will be recognized, each of the physical addresses may be associated with the customer's profile.

In some embodiments, the carrier system 100, as part of the registration process or subsequent to the registration process, may enable the customer to enroll, apply to be, or otherwise become a repository and, if selected, an alternative consignee. Accordingly, as is shown in operation 410, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for enabling registration as a repository and/or an alternative consignee. In some embodiments, a verification process and/or approval process, for example, similar to or in addition to that which was performed in the initial registration operation, may be performed prior to classifying the customer as a repository and/or enabling/allowing other customers to select the customer as an alternative consignee. For example, the last mile carrier system or carrier system 100 may include means, such as the processor 205 or the like, for verifying eligibility by way of, for example, a credit check, background check, cash deposit, or the like. Some embodiments may allow for, after selection, a subsequent rating and/or peer-review process by other customers.

In one embodiment, once the customer is registered as a repository and/or an alternative consignee, benefits or incentives may be afforded, such as, for example, discounts on future shipping costs and/or services (e.g., free customer pick-up or delivery, reduced cost and/or unlimited services, etc.) Moreover, once a customer is registered as a repository and/or an alternative consignee, the customer (e.g., operating a customer computing device 110/120) can provide various preferences associated with the customer program to the carrier system 100 via a webpage. For instance, the customer (e.g., operating a customer computing device 110/120) can provide a variety of preferences, such communication preferences, service schedule preferences, delivery preferences, and/or delivery options. The customer (e.g., operating a customer computing device 110/120) may also update any information/data through the appropriate interface (e.g., browser, dashboard, webpage, application). In some embodiments, the customer (e.g., operating a customer computing device 110/120) may also provide preferences regarding their unavailability to act as a repository/alternative consignee. For example, while the customer is on vacation or the like, packages may be unable to be received.

2. Determining and Selecting an Alternative Consignee

FIG. 5 shows a flowchart illustrating a process that may be performed by a carrier system 100 to enable a customer (e.g., consignors and/or consignees) to select one or more repositories as alternative delivery destinations utilizing, for example, an “Alternate Consignee Delivery Network” or the like. As is shown in operation 505, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for generating or receiving shipping information/data (hereinafter “shipping information”), the shipping information/data indicative of an item to be delivered to a consignee by a carrier. In some embodiments, the shipping information/data may comprise at least a default delivery location, for example to an “original consignee”—including those associated with an automatic service schedule (see FIG. 6). In some embodiments, the shipping information/data may comprise an estimated time of delivery. For example, the default delivery location may be the address on a shipping label, as indicated by, for example, the consignor. An item may be any tangible and/or physical object. In one embodiment, an item/parcel may be or be enclosed in one or more packages, parcels, bags, containers, loads, crates, items banded together, vehicle parts, pallets, drums, the like, and/or similar words used herein interchangeably. Such items/parcels may include the ability to communicate (e.g., via a chip (e.g., an integrated circuit chip), RFID, NFC, Bluetooth, Wi-Fi, and any other suitable communication techniques, standards, or protocols) with one another and/or communicate with various computing entities for a variety of purposes. In this regard, in some example embodiments, an item may communicate send “to” address information/data, received “from” address information/data, unique identifier codes, and/or various other information/data. Once shipping information/data is generated and/or received, delivery may be arranged.

In some embodiments, the shipping information/data may further include information/data about the item, such as delivery service level. For example, the delivery service level may be Next Day Air, Overnight, Express, Next Day Air Early AM, Next Day Air Saver, Jetline, Sprintline, Secureline, 2nd Day Air, Priority, 2nd Day Air Early AM, 3 Day Select, Ground, Standard, First Class, Media Mail, SurePost, Freight, and/or the like. The shipping data may include information/data about the party shipping the item (e.g., consignor), such as the party's address, the party's phone number, the party's return address, the party's name, and/or the like. The shipping information/data may also include information/data about the customer to whom the item is to be delivered (e.g., consignee), such as the customer's physical address or location (e.g., delivery point/location), the customer's virtual address, the customer's phone number, the customer's name, and/or the like. As will be recognized, the terms delivery point/location are intended encompass any identifiable location, including residences, commercial locations, stores, vehicles, boats, landmarks, and/or the like.

In one embodiment, the shipping information/data may include information/data about the item itself and any tracking information. The tracking information/data may reflect the item's movement in the carrier's transportation network, including an expected pick-up or delivery date and time. To reflect the item's movement, an item/shipment identifier associated with the item may be scanned or otherwise electronically read at various points as the item is transported through the carrier's transportation network. For example, the item/shipment identifier may be automatically scanned by a barcode or MaxiCode device, an RFID interrogator, by a camera controller, or by a carrier employee using a handheld device (e.g., mobile station 105). In one embodiment, each time the item/shipment identifier is scanned or read, an appropriate device can transmit the item/shipment identifier and other appropriate information/data (e.g., location and time of the scan or reading) to the carrier system 100. The carrier system 100 can then receive and use the information/data to track the item as it is transported though the carrier's transportation network and update the shipping information/data accordingly.

To arrange delivery, according to some embodiments discussed herein, the carrier system 100 may be configured to determine whether the original consignee has registered for the, for example, “Alternate Consignee Delivery Network” or otherwise elected to allow shipments to be delivered to alternative consignees. Accordingly, as is shown in operation 510, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for determining, subsequent to the reception of the shipping information/data for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee. In some embodiments, in an instance in which the original consignee has not elected to enable shipments to be delivered to at least one alternative consignee, the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for providing a user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of a first priority alternative consignee.

For instance, when the consignee, has not registered or otherwise elected to allow shipments to be delivery to a repository/alternative consignee, the carrier system 100 may, for example, provide a user interface configured to implement the registration process described above with reference to FIG. 4. In other embodiments, the carrier system 100 may be configured to provide notification of the item, and in some embodiments, an estimated delivery date or the like, and allow the original consignee to select a repository/alternative consignee. Such notifications are described in greater detail in U.S. application Ser. No. 13/913,066, which is hereby incorporated in its entirety by reference. As such, as is shown in operation 515, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for providing, via the network, to the client device, a notification of an item which is addressed to the original consignee. Furthermore, as is shown in operation 520, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for providing, via the network, to the client device, a user interface configured to enable registration and/or prompt for selection of a repository/alternative consignee. That is, the carrier system 100 may provide the user interface and allow for the original consignee to register for the, for example, “Alternate Consignee Delivery Network,” thus creating a customer profile or updating an existing customer profile, or on a one-time basis, elect a repository/alternative consignee. As is shown in operation 525, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for storing information/data regarding the selection of a repository/alternative consignee. For example, the information/data may be stored in, for example, a newly created customer profile or an updated customer profile. In one embodiment, once a customer (e.g., the original consignee) profile has been created by the carrier system 100, each of one or more items to be delivered to, picked up from, and/or returned from the customer can be identified as corresponding to the customer, and as such, may be delivered to, picked up from, and/or returned from a repository/alternative consignee.

Referring back to operation 510, the carrier system 100 may be configured for determining, subsequent to the reception of the shipping information/data for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, such as by determining if the customer is registered in the “Alternate Consignee Delivery Network” or has otherwise elected to allow shipments to be delivered to alternative consignees. In an instance in which the original consignee has elected to enable shipments to be delivered to at least one alternative consignee, the carrier system 100 may be configured for determining the first priority alternative consignee, by for example, determining, first, if one or more alternative consignees have been selected, and if not, receiving selection of one or more alternative consignees, and/or what priority levels have been assigned to and/or associated with each of the selected alternative assignees. Similarly, once a customer has undergone the registration process or otherwise been notified by the carrier system of the item and been provided with functionality enabling them to allow the item to be delivered to alternative consignee, the carrier system may be configured for receiving selection of one or more alternative consignees. Accordingly, as is shown in operation 530, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for receiving selection of one or more alternative consignees.

FIG. 6 shows exemplary service schedule information/data identifying the selected alternative consignee by address that may be associated with a particular customer (e.g., consignee or consignor). As shown in FIG. 6, a customer (e.g., operating a consignee computing device 110 or consignor computing device 120) may provide alternative consignees to which items should be delivered for each day of the week (including holidays) and/or for certain time periods during those days. For example, this particular customer on Mondays, Tuesdays, Wednesdays, and Thursdays (a) between 7:00 am-9:00 am and 5:00 pm-9:00 pm should be made at 105 Main Street, Atlanta, Ga. 30309, USA, and (b) between 9:00 am-5:00 pm should be made at 1201 W Peachtree, Atlanta, Ga. 30309, USA. Pick-ups from or deliveries on Fridays (a) between 7:00 am-9:00 am should be made at 105 Main Street, Atlanta, Ga. 30309, USA, and (b) between 9:00 am-9:00 pm should be made at 71 Lanier Islands, Buford, Ga. 30518, USA. And pick-ups from or deliveries on Saturdays, Sundays, or national holidays should be made at 71 Lanier Islands, Buford, Ga. 30518, USA.

After receiving the selection of a repository as an alternative consignee (e.g., provided by a customer operating an appropriate computing device 110/120), the carrier system 100 can update the appropriate customer profile to reflect that items to be picked up from and/or delivered to the customer should be in accordance with the service schedule (e.g., the customer's preferences or requests). As noted, such service schedules may be based on other considerations, factors, criteria, and similar words used herein interchangeably as well, such as months of the year, delivery instructions, delivery service levels, seasons, weather conditions for the pick-up or delivery date/time, travel conditions for the pick-up or delivery date/time, environmental conditions for the pick-up or delivery date/time, safety conditions for the pick-up or delivery date/time, and/or the like. Such automatic services schedules can be used to deliver items in accordance with the preferences regardless of the physical address, date, time, and/or the like that were originally intended by the consignor, carrier, or consignee.

In some embodiments, the carrier system 100 may identify candidate alternative delivery consignees/locations (e.g., dynamic delivery locations described in U.S. patent application Ser. No. 14/556,972, which is hereby incorporated by reference) from which alternative consignees may be selected. In some embodiments, candidate alternative delivery consignees/locations may be determined and/or provided for selection based on a discount level, (e.g., city center located alternative consignees or those otherwise located in densely traveled locations may have a lower associated cost than those alternative consignees that would require rural delivery.

For example, as will be understood by those skilled in the art, a carrier accumulates shipment data associated with items to be delivered and assigns the items to delivery routes for transporting the items through one or more facilities in the carrier's delivery network. In addition, the carrier also creates a dispatch plan for performing the final delivery of the item from a facility to a delivery address. In some embodiments, before or during the generation of the dispatch plan, the carrier system 100 may identify candidate alternative delivery consignees/locations within the delivery route. Candidate alternative delivery consignees/locations may be identified by applying various business rules to the service stops along a delivery route as specified by a dispatch plan. In some embodiments, the business rule may specify that only service stops in which the estimated time at the stop exceeds a predetermined threshold or the number of deliveries associated with a given stop exceeds a threshold would be a candidate for an alternative delivery location/consignee. For example, the carrier system 100 may compare the stop duration data from the dispatch plan against a predetermined threshold. In some embodiments, a business rule may specify that a predetermined number of service stops within a predetermined distance threshold may, as a group, represent a candidate alternative delivery consignees/location (e.g., within a neighborhood, on same street, with a shopping center, etc.). In some embodiments, the business rules may specify that some or all commercial stops may be considered candidate alternative delivery consignees/locations or that all service stops may be candidate alternative delivery consignees/locations.

In some embodiments, some customers may have an account with the carrier which establishes a series of delivery preferences as generally described in U.S. application Ser. No. 14/025,893. These preferences may include a primary delivery address and one or more secondary delivery addresses as previously described. In some cases, the profile may associate certain addresses for delivery of items on certain days/times and deliveries to other addresses on other days/times. In the event a consignee has a customer profile, the carrier system 100 may identify candidate alternative delivery consignees/locations that are within a predetermined distance threshold from the primary and/or secondary addresses provided in the consignee's profile. In some embodiments, the carrier system 100 may identify candidate alternative delivery consignees/locations that are within a predetermined time threshold from the estimated delivery time for primary and/or secondary addresses provided in the consignee's profile.

In some embodiments, the carrier system 100 may identify which consignees are offered one or more of the identified dynamic delivery locations. In some embodiments, only consignees that have an account and/or customer profile with the carrier are qualified to be offered candidate alternative delivery consignees/locations. U.S. application Ser. No. 14/025,893, which is incorporated above by reference, describes systems and methods for registering for an account and how that account may operate.

In some embodiments, the carrier system 100 may use the location information/data to “pro-actively” identify candidate alternative delivery consignees/locations such as restaurants, retail stores, landmarks or other locations that are within a predetermine distance of the determined location of the customer and “pro-actively” notify the customer of this option (e.g., before the customer has selected a repository/alternative consignee). For example, the candidate alternative delivery consignees/locations may be communicated to the customer with the notification or when the customer accesses a web portal or the like. As discussed in greater detail in U.S. application Ser. No. 13/839,398 filed on Mar. 13, 2013, which is hereby incorporated by reference, the one or more carrier servers may use various algorithms to predict the location of a customer and offer these locations as candidate alternative delivery consignees/locations. In further embodiments, the candidate alternative delivery consignees/locations may be dynamic locations based on GPS information, social network account information/data or the like. For example, the customer may be shopping at nearby retail stores and request that the item is delivered to her location. The carrier service provider would then use the GPS location of the customer's mobile device 115/120, social network information/data including information/data about the customer and/or the customer's vehicle (which may be part of a vehicle social network) to locate the customer and make the delivery of the item.

In some embodiments, one or more repositories may be selected and, subsequently, each may be given a priority. For example, a customer's first choice of repository/alternative consignee may be given first priority while a customer's second choice may be given second priority. For example, priority may be based on cost (e.g., particular repositories/alternative consignees may be more cost effective to deliver to), value (e.g., particular repositories/alternative consignees may be closer to home/office and still provide a cost advantage over the home/office while not having the same cost advantage as someplace further away or harder to get to, etc.), availability (e.g., e.g., particular repositories/alternative consignees may be able to accept parcel/items that require non-standard or special handling or offer better/more convenient hours, etc.), convenience (e.g., particular repositories/alternative consignees may be located on a particular route, in a particular neighborhood, etc.), or the like.

Once the first priority alternative consignee is selected and identified, as is shown in operation 535, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for determining if the first priority alternative consignee is available, for example, to receive the item. For instance, as described above with reference to FIG. 4, when a customer registers to be a repository, the customer may provide notification of time frames/window in which they are unavailable to receive items/parcels, packages, or the like. As such, here the carrier system may determine whether the repository selected as the alternative consignee selected by the original consignee has indicated availability, unavailability, or the like.

In an instance in which the first priority alternative consignee is not available to receive the item, the last mile carrier system or carrier system 100 may be configured to execute the process enabling delivery of the item to the first priority alternative consignee, whereas, in an instance in which the first priority alternative consignee is not available to receive the item, the last mile carrier system or carrier system 100 may be configured to determine a second priority alternative consignee. Once the second priority alternative consignee is identified, the last mile carrier system or carrier system 100 may be configured to determine whether the second priority alternative consignee is available to receive the item, and in an instance in which the second priority alternative consignee is available to receive the item, the last mile carrier system or carrier system 100 may be configured to execute the process enabling delivery of the item to the second priority alternative consignee. In some embodiments, the described process may continue as many times as necessary to locate an available alternative consignee (e.g., identifying a third priority alternative consignee, determining their availability etc.).

In some embodiments, as is shown in operation 540, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for, in an instance in which the first priority alternative consignee is available, providing, via the network, to the client device, a user interface configured to provide notification of the intent to deliver to first choice alternative consignee and/or allow for selection to have item delivered to original consignee. That is, while the customer may have registered for the “Alternate Consignee Delivery Network” or otherwise elected to allow shipments to be delivered to alternative consignees, the last mile carrier system or carrier system 100 may, in some embodiments, still provide the original consignee with functionality enabling them to receive the item/parcel.

In some embodiments, as is shown in operation 545, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for, in an instance in which the first priority alternative consignee is not available, providing, via the network, to the client device, a user interface configured to provide notification of the unavailability of the default or first priority alternative consignee and, moreover, an intent to deliver the item/parcel to the second alternative consignee. Furthermore, in some embodiments, the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for, providing, via the network, to the client device, a user interface configured to allow a selection to have item delivered to original consignee. As is shown in operation 550, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for executing the process enabling delivery of the item to the alternative consignee. As shown above, in some embodiments, the alternative consignee to which an item may be delivery may be the first priority alternative consignee, whereas in other embodiments, the alternative consignee to which the item may be delivered is the second/third/fourth priority alternative consignee.

Once delivery is made, notification may be sent. Specific processes performed are described in detail with reference to FIG. 7 below. Referring back to FIG. 5, as is shown in operation 555, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for providing, via the network, to the client device, a user interface configured to provide notification that the item was delivered. In some embodiments, the notification may comprise information/data indicative of which of the one or more alternative consignees to which the item was delivered (e.g., to the first priority alternative consignee, or in the event the first priority alternative consignee was unavailable, to the second priority alternative consignee). Furthermore, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for requesting confirmation of the delivery, such as by requesting and/or receiving a customer signature, photo, or the like. That is, when the original consignee retrieves the item from the repository/alternative consignee, the repository/alternative consignee may request and/or require the original consignee to acknowledge pick-up and/or, in some embodiments, additionally or alternatively, the consignor, the carrier system, and/or the last carrier system may request and/or require the original consignee to acknowledge pick-up.

FIG. 7 is a flowchart illustrating operations and processes that may be performed for providing notification, to a customer computing device, of a delivery location, a delivery time, and a delivery day based on communication preferences of the consignee. For example, consignees may specify in their communication preference how and when to be contacted, such as by email the morning of the scheduled delivery. The messages may indicate the delivery location, delivery date and/or delivery time, such as shown in FIGS. 8A and 8B, and a variety of other information. As will be recognized, a variety of other operations and processes may be used with embodiments of the present invention. These operations and processes can be customized to adapt to various needs and circumstances. Referring back to FIG. 7, as is shown in operation 705, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for storing communication preferences for providing information/data indicative of the delivery location and the delivery time, wherein the communication preferences (1) identify at least one communication format and at least one corresponding electronic destination address to be used in providing the information/data to the customer, and (2) define a time period prior to a first carrier attempt of the item in which a message providing the information/data is to be transmitted to the at least one corresponding electronic destination address. In some embodiments, the at least one communication format is selected from the group consisting of a text message, an email message, a voice message, a picture message, a video message, and a social media message.

As is shown in operation 710, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for automatically generating a message providing the information/data regarding the item to be delivered to the customer. As is shown in operation 715, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for automatically transmitting the message to the at least one corresponding electronic destination address within the defined time period prior to the first carrier attempt of the item to the customer. FIGS. 8A and 8B show exemplary user interfaces providing the delivery location and the delivery time in accordance with some embodiments. In some embodiments, the carrier system 100 may automatically generate (e.g., via the message module 260) one or more messages providing information/data regarding an item to be delivered to the customer, for example, in compliance with the consignee's communication preferences. Similarly, the carrier system 100 may automatically transmit the one or messages to the electronic destination addresses in compliance with the consignee's communication preferences. For example, the carrier system 100 may generate and transmit an email message to a consignee email address and a text message to a consignee's cellular phone the day before an item is to be delivered to the consignee's home address.

C. Exemplary Embodiments

FIG. 9 shows a data flow diagram. The system 900 may include a carrier system (e.g., the last mile carrier system) and a client device embodied by, for example, consignee computing device 110 shown in FIG. 3. In some embodiments, as is shown in operation 910, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for registering for, for example, “Alternate Consignee Delivery Network.” As such, in some embodiments, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for executing a registration process, such as that described above with reference to FIG. 4. Once registered, as is shown in operation 920, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for providing an indication choosing to become a repository (e.g., an alternative consignee).

Once a customer chooses to apply to become a repository/alternative consignee, a verification process may be performed by, for example, the last mile carrier system or carrier system 100, or the like. As such, if verified, as is shown in operation 930, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for approving the consignee. As is shown in operation 940, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for allowing the consignee to become a repository. Subsequent to being a repository/alternative consignee, as is shown in operation 950, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for selecting the consignee as a repository/alternative consignee when, for instance, the consignee provides an indication of availability.

Referring back to operation 960, after the registration and having to select whether or not to become an approved repository, as is shown in operation 960, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for allowing delivery of packages to a repository. Once allowing delivery, selection may be made. Accordingly, as is shown in operation 970, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for selecting one or more repositories at which delivery may be made. As described above with reference to FIG. 5, the carrier system 100 may determine the availability of a repository/alternative consignee. Accordingly, as is shown in operation 980, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for setting options for disposition of the parcel if the selected repository is unavailable. For example, the parcel may be delivered to the original consignee, a second priority alternative consignee, etc.

FIG. 10 shows a data flow diagram. The system 1000 may include a carrier system (e.g., the last mile carrier system) and a client device embodied by, for example, consignee computing device 110 shown in FIG. 3. Accordingly, FIG. 10 shows a data flow diagram that may be performed by a system 1000 for executing a delivery of an item/parcel in accordance with an “Alternate Consignee Delivery Network.” In some embodiments, as is shown in operation 1005, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for receiving new shipping information/data, the new shipping information/data indicative of an item awaiting delivery to the original consignee. As is shown in operation 1010, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for determining whether the original consignee participates in, for example, an “Alternate Consignee Delivery Network” or the like. If it is determined that the original consignee does not participate, the carrier system may notify the original consignee of the item/parcel. Accordingly, as is shown in operation 1015, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for receiving notification of parcel delivery to the original consignee.

If, however, it is determined that the original consignee participates in the “Alternate Consignee Delivery Network,” then, as is shown in operation 1020, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for determining whether the original consignee has selected a repository as an alternative consignee. If the original consignee has not yet selected a repository as an alternative consignee, as is shown in operation 1025, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for receiving notification of the item/parcel and one or more options (e.g., candidate alternative delivery location/consignees). Subsequently, as is shown in operation 1030, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for selecting a repository as an alternative consignee.

Once the original consignee has selected a repository as an alternative consignee or, in response to the determination of a yes at operation 1020, as is shown in operation 1035, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for executing the process for delivering the item/parcel to the selected repository and notifying the original consignee of the delivery. Once delivered, as is shown in operation 1040, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for retrieving the parcel from the repository or otherwise providing confirmation of its reception. Subsequently, as is shown in operation 1045, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for receiving confirmation and/or proof of delivery (e.g., an electronic signature, photo, or the like).

In some exemplary embodiments, some of the operations shown in the process described in FIG. 10 may be performed by a last mile carrier system, such as that shown in FIG. 11. Accordingly, FIG. 11 shows a data flow diagram that may be performed by a system 1100 for executing a delivery of an item/parcel in accordance with an “Alternate Consignee Delivery Network.” The system 1100 may include a first carrier system (e.g., the carrier system), which may be embodied by carrier system 100 shown in FIG. 2, a client device embodied by, for example, consignee computing device 110 shown in FIG. 3, and a last mile carrier system, (e.g., shown here as the “last mile carrier system”), which may be embodied by a second instance of carrier system 100 shown in FIG. 2. Many of the operations, for which a detailed description is given with reference to FIG. 10, are identical, and as such, in the following embodiment, for brevity, detailed descriptions of identical portions are omitted. Specifically, operations 1005-1030 shown in FIG. 10 correlate to operations 1105-1130 shown in FIG. 11.

Referring now to operation 1135, once the original consignee has selected a repository as an alternative consignee or, in response to the determination of a yes at operation 1120, as is shown in operation 1135, an apparatus, such as the carrier system 100, may include means, such as the processor 205 or the like, for transmitting the delivery information/data (e.g., the new parcel data referenced above with respect to operation 1005 and the selected repository) to the last mile carrier (e.g., last mile carrier system).

Subsequently, as is shown in operation 1150, an apparatus, such as the last mile carrier system, may include means, such as the processor 205 or the like, for executing the process for delivering the item/parcel to the selected repository and notifying the original consignee of the delivery of the item/parcel to the selected repository. Once delivered, as is shown in operation 1140, an apparatus, such as the client device embodied by, for example, consignee computing device 110, may include means, such as the processing device 308 or the like, for retrieving the parcel from the repository or otherwise providing confirmation of its reception. Subsequently, as is shown in operation 1145, an apparatus, such as the last mile carrier system or carrier system 100, may include means, such as the processor 205 or the like, for receiving confirmation and/or proof of delivery (e.g., an electronic signature, photo, or the like).

IV. Conclusion

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are 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 purposes of limitation.

Claims

1. A method for delivering an item to an alternative final delivery destination the method comprising: receiving the item at a facility within a delivery network;receiving, via a data transmission computer network, shipping information/data for the item, the shipping information/data, input at a client device, indicating the item to be delivered to an original consignee by a first delivery vehicle and comprising at least a default delivery location;determining that the original consignee is one participant among a plurality of participants in an alternative consignee delivery network, each participant being an alternative delivery location to (i) act as a selectable alternative consignee at a respective final delivery destination for one or more of the plurality of participants and (ii) select, via a respective client device, an alternative consignee from among the plurality of participants in the alternative consignee delivery network;upon determination that the original consignee is among the plurality of participants in the alternative consignee delivery network, determining that the original consignee has not indicated a first priority alternative consignee among the plurality of participants in the alternative consignee delivery network, wherein the first priority alternative consignee is associated with a respective alternative delivery location;in response to determining that the original consignee has not indicated the first priority alternative consignee, automatically tracking, before the original consignee has selected the first priority alternative consignee, a mobile device associated with the original consignee, wherein the tracking includes detecting, via a Global Position System (GPS) location determining device, a first set of geocode coordinates of the mobile device;based at least in part on the first set of geocode coordinates, determine that the respective alternative delivery location is within a threshold distance of the mobile device;based at least in part on the original consignee not indicating the first priority alternative consignee among the one or more alternative consignees and the respective alternative delivery location being within the threshold distance of the mobile device, delivering, based on receiving operation telematics indicating a GPS location of a second delivery vehicle, the item to the second delivery vehicle that is scheduled to deliver one or more other items to the first priority alternative consignee among the plurality of participants in the alternative consignee delivery network at the respective alternative delivery location as a final delivery location instead of the default delivery location.
2. The method according to claim 1, further comprising: determining, subsequent to the reception of the shipping information/data for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee; andin an instance in which the original consignee has not elected to enable the shipments to be delivered to the at least one alternative consignee, providing a user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of the first priority alternative consignee.
3. The method according to claim 1, further comprising: in an instance in which the original consignee has not indicated the first priority alternative consignee or other candidate alternative consignee provide cost advantages over the first priority alternative consignee, receiving a current GPS location of the original consignee; andproviding one or more candidate alternative consignees based on the current GPS location of the original consignee.
4. The method according to claim 3, further comprising: determining whether the first priority alternative consignee is available to receive the item;in an instance in which the first priority alternative consignee is available to receive the item, delivering the item to the first priority alternative consignee;in an instance in which the first priority alternative consignee is not available to receive the item, determining a second priority alternative consignee;determining whether the second priority alternative consignee is available to receive the item; andin an instance in which the second priority alternative consignee is available to receive the item, delivering the item to the second priority alternative consignee.
5. The method according to claim 4, further comprising: providing, via the data transmission computer network, to the client device, notification that the item was delivered, the notification comprising information/data indicative of which of the one or more alternative consignees to which the item was delivered; and providing, via the data transmission computer network, to the client device, a user interface configured to receive confirmation.
6. The method according to claim 1, further comprising: providing, via the data transmission computer network, to the client device, a user interface configured to enable the original consignee to indicate that the item should be delivered to the default delivery location.
7. The method according to claim 1, further comprising: providing, via the data transmission computer network, to the client device, a user interface configured to enable the original consignee to register as one of the one or more alternative consignees, enabling other original consignees to select the original consignee as one of their alternative consignees.
8. A system for delivering an item to an alternative final delivery destination, the system comprising: a carrier system, comprising one or more processors, that operates to:receive, over a wired or wireless protocol computer network and via input at a user interface of a client device, shipping information for the item, the item located at a facility within a delivery network, the shipping information indicating the item to be delivered to an original consignee by a first delivery vehicle and comprising at least a default delivery location;determine whether the original consignee is one participant among a plurality of participants in an alternative consignee delivery network, each participant being able to (i) act as a selectable alternative consignee at a respective final delivery destination for one or more of the plurality of participants and (ii) select, via an indication on one or more respective user interfaces of one or more respective client devices, an alternative consignee from among the plurality of participants in the alternative consignee delivery network;upon determination that the original consignee is among the plurality of participants in the alternative consignee delivery network, determine, based at least in part on whether a selection was made to the user interface of the client device, whether the original consignee has indicated a first priority alternative consignee among the plurality of participants in the alternative consignee delivery network, wherein the first priority alternative consignee is associated with a respective alternative delivery location;in an instance in which a determination is made that the original consignee has not indicated the first priority alternative consignee among the one or more alternative consignees, automatically track, before the original consignee has selected the first priority alternative consignee, a mobile device associated with the original consignee, wherein the tracking includes detecting, via a Global Position System (GPS) location determining component, a first set of geocode coordinates of the mobile device;based at least in part on the first set of geocode coordinates, determine that the respective alternative delivery location is within a threshold distance of the mobile device; andbased at least in part on the original consignee not indicating the first priority alternative consignee among the one or more alternative consignees and the respective alternative delivery location being within the threshold distance of the mobile device, directing the delivery of the item, based on receiving operation telematics indicating a GPS location of a second delivery vehicle, to the second delivery vehicle that is scheduled to deliver one or more other items to the first priority alternative consignee among the plurality of participants in the alternative consignee delivery network at the respective alternative delivery location as a final delivery location instead of the default delivery location.
9. The system of claim 8, wherein the carrier system further operates to: determine, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee; andin an instance in which the original consignee has not elected to enable the shipments to be delivered to the at least one alternative consignee, provide another user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of the first priority alternative consignee.
10. The system of claim 8, wherein the carrier system further operates to: in an instance in which the original consignee has not indicated the first priority alternative consignee or other candidate alternative consignee provide cost advantages over the first priority alternative consignee, receive a current GPS location of the original consignee; andprovide one or more candidate alternative consignees based on the current GPS location of the original consignee.
11. The system of claim 10, wherein the carrier system further operates to: determine whether the first priority alternative consignee is available to receive the item;in an instance in which the first priority alternative consignee is available to receive the item, deliver the item to the first priority alternative consignee;in an instance in which the first priority alternative consignee is not available to receive the item, determine a second priority alternative consignee;determine whether the second priority alternative consignee is available to receive the item; andin an instance in which the second priority alternative consignee is available to receive the item, deliver the item to the second priority alternative consignee.
12. The system of claim 11, wherein the carrier system further operates to: provide, over the wired or wireless protocol computer network, to the client device, a notification that the item was delivered, the notification comprising information indicative of which of the one or more alternative consignees to which the item was delivered; andprovide, over the wired or wireless protocol computer network, to the client device, a user interface element of the user interface configured to receive confirmation.
13. The system of claim 8, wherein the carrier system further operates to: provide, over a wired or wireless protocol computer network, to the client device, a user interface element of the user interface configured to enable the original consignee to indicate that the item should be delivered to the default delivery location.
14. The system of claim 8, wherein the carrier system further operates to: provide, over the wired or wireless protocol computer network, to the client device, a user interface element of the user interface configured to enable the original consignee to register as one of the one or more alternative consignees, enabling other original consignees to select the original consignee as one of their alternative consignees.
15. A system for delivering an item to an alternative final delivery destination, the system comprising: a computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising: an executable portion configured to receive, over a computer network, shipping information for the item, the item located at a facility within a delivery network, the shipping information, input at a client device, indicating the item to be delivered to an original consignee by a first delivery vehicle and comprising at least a default delivery location;an executable portion configured to determine whether the original consignee is one participant among a plurality of participants in an alternative consignee delivery network, each participant being able to (i) act as a selectable alternative consignee at a respective final delivery destination for one or more of the plurality of participants and (ii) select, via a respective client device, an alternative consignee from among the plurality of participants in the alternative consignee delivery network; andan executable portion configured to, upon determination that the original consignee is among the plurality of participants in the alternative consignee delivery network, determine whether the original consignee has indicated a first priority alternative consignee among the plurality of participants in the alternative consignee delivery network, wherein the first priority alternative consignee is associated with a respective alternative delivery location;in an instance in which a determination is made that the original consignee has not indicated the first priority alternative consignee among the one or more alternative consignees, an executable portion configured to automatically track a mobile device associated with the original consignee, wherein the tracking includes detecting, via a Global Positioning System (GPS) location determining component, a first set of geocode coordinates of the mobile device;based at least in part on the first set of geocode coordinates, an executable portion configured to determine that the respective alternative delivery location is within a threshold distance of the mobile device;based at least in part on the original consignee not indicating the first priority alternative consignee among the one or more alternative consignees and the respective alternative delivery location being within the threshold distance of the mobile device, an executable portion configured to direct the delivery of the item, based on receiving operation telematics indicating a GPS location of a second delivery vehicle, to the second delivery vehicle that is scheduled to deliver one or more other items from the facility to at least one of the plurality of participants in the alternative consignee delivery network at the respective alternative delivery location as final delivery location instead of the default delivery location.
16. The system of claim 15 the computer program product further comprising: an executable portion configured to determine, subsequent to the reception of the shipping information for the item, whether the original consignee has elected to enable shipments to be delivered to at least one alternative consignee; andan executable portion configured to, in an instance in which the original consignee has not elected to enable the shipments to be delivered to the at least one alternative consignee, provide a user interface configured to notify the original consignee of the item and allow one of registration or a single-time selection of the first priority alternative consignee.
17. The system of claim 15 the computer program product further comprising: an executable portion configured to, in an instance in which the original consignee has not indicated the first priority alternative consignee or other candidate alternative consignee provide cost advantages over the first priority alternative consignee, receive a current GPS location of the original consignee; andan executable portion configured to provide one or more candidate alternative consignees based on the current GPS location of the original consignee.
18. The system of claim 17 further comprising: the computer program product comprising an executable portion configured to determine whether the first priority alternative consignee is available to receive the item;the delivery network that further operates to, in an instance in which the first priority alternative consignee is available to receive the item, deliver the item to the first priority alternative consignee;the computer program product comprising an executable portion configured to, in an instance in which the first priority alternative consignee is not available to receive the item, determine a second priority alternative consignee;the computer program product comprising an executable portion configured to determine whether the second priority alternative consignee is available to receive the item; andthe delivery network that further operates to, in an instance in which the second priority alternative consignee is available to receive the item, deliver the item to the second priority alternative consignee.
19. The system of claim 18 further comprising: the computer program product comprising an executable portion configured to provide to the client device, notification that the item was delivered, the notification comprising information indicative of which of the one or more alternative consignees to which the item was delivered; andthe computer program product comprising an executable portion configured to provide to the client device, a user interface configured to receive confirmation.
20. The system of claim 15 further comprising: the computer program product comprising an executable portion configured to provide, over the computer network, to the client device, a user interface configured to enable the original consignee to indicate that the item should be delivered to the default delivery location.
21. The system of claim 15 further comprising: the computer program product comprising an executable portion configured to provide, over the computer network, to the client device, a user interface configured to enable the original consignee to register as one of the one or more alternative consignees, enabling other original consignees to select the original consignee as one of their alternative consignees.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No. 61/952,163 filed Mar. 13, 2014, which is hereby incorporated herein in its entirety by reference.

US Referenced Citations (360)

Number	Name	Date	Kind
3721096	Deckert, Jr. et al.	Mar 1973	A
3876059	Durst	Apr 1975	A
3933031	Uhlarik	Jan 1976	A
4111601	Richard	Sep 1978	A
4832204	Handy et al.	May 1989	A
5153842	Dlugos, Sr. 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
5460110	Eronen et al.	Oct 1995	A
5623260	Jones	Apr 1997	A
5648770	Ross	Jul 1997	A
5656799	Ramsden et al.	Aug 1997	A
5657010	Jones	Aug 1997	A
5659731	Gustafson	Aug 1997	A
5668543	Jones	Sep 1997	A
5711670	Barr	Jan 1998	A
5786748	Nikolic et al.	Jul 1998	A
5831860	Foladare et al.	Nov 1998	A
5835377	Bush	Nov 1998	A
5884272	Walker et al.	Mar 1999	A
5971587	Kato et al.	Oct 1999	A
6029140	Martin 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
6292709	Uhl 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
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
6422506	Colby	Jul 2002	B1
6442589	Takahashi et al.	Aug 2002	B1
6463354	Pintsov	Oct 2002	B1
6463420	Guidice et al.	Oct 2002	B1
6486801	Jones	Nov 2002	B1
6492912	Jones	Dec 2002	B1
6510383	Jones	Jan 2003	B1
6536659	Hauser et al.	Mar 2003	B1
6539360	Kadaba	Mar 2003	B1
6606604	Dutta	Aug 2003	B1
6618668	Laird	Sep 2003	B1
6634551	Barta et al.	Oct 2003	B2
6683542	Jones	Jan 2004	B1
6700507	Jones	Mar 2004	B2
6701299	Kraisser et al.	Mar 2004	B2
6714859	Jones	Mar 2004	B2
6741927	Jones	May 2004	B2
6748318	Jones	Jun 2004	B1
6748320	Jones	Jun 2004	B2
6763299	Jones	Jul 2004	B2
6763300	Jones	Jul 2004	B2
6765487	Holmes et al.	Jul 2004	B1
6772130	Karbowski et al.	Aug 2004	B1
6804606	Jones	Oct 2004	B2
6845448	Chaganti et al.	Jan 2005	B1
6859722	Jones	Feb 2005	B2
6862612	Horn et al.	Mar 2005	B1
6902109	Barta et al.	Jun 2005	B2
6904359	Jones	Jun 2005	B2
6931314	Holland et al.	Aug 2005	B2
6952645	Jones	Oct 2005	B1
6975998	Jones	Dec 2005	B1
6976090	Ben-Shaul et al.	Dec 2005	B2
6976900	Bolz	Dec 2005	B2
6978929	Buie et al.	Dec 2005	B2
6985871	Simon et al.	Jan 2006	B2
6994253	Miller et al.	Feb 2006	B2
7028895	Ashaari	Apr 2006	B2
7030781	Jones	Apr 2006	B2
7031959	Garner et al.	Apr 2006	B2
7039813	Algazi et al.	May 2006	B2
7130803	Couch et al.	Oct 2006	B1
7152375	Mastro et al.	Dec 2006	B1
7158948	Rodriguez et al.	Jan 2007	B1
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
7257552	Franco	Aug 2007	B1
7305404	Owens et al.	Dec 2007	B2
7312702	Willms et al.	Dec 2007	B1
7331248	Maresca, Jr. et al.	Feb 2008	B2
7363126	Zhong et al.	Apr 2008	B1
7376598	Estes et al.	May 2008	B2
7385499	Horton et al.	Jun 2008	B2
7422149	Aptekar	Sep 2008	B2
7479899	Horstemeyer	Jan 2009	B2
7501946	Lanigan et al.	Mar 2009	B2
7511617	Burman	Mar 2009	B2
7528722	Nelson	May 2009	B2
7531163	Samadpour	May 2009	B2
7542972	Owens et al.	Jun 2009	B2
7574366	Burman	Aug 2009	B2
7580845	Burman	Aug 2009	B2
7624024	Levis et al.	Nov 2009	B2
7647231	Kuebert et al.	Jan 2010	B2
7657466	Klingenberg 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
7831439	Bryar et al.	Nov 2010	B1
7848961	Estes et al.	Dec 2010	B2
7853481	Johnson	Dec 2010	B1
7868753	Jenkins	Jan 2011	B2
7912854	Owens et al.	Mar 2011	B2
7925524	Florence	Apr 2011	B2
7962422	Melechko	Jun 2011	B1
7969306	Ebert et al.	Jun 2011	B2
7984289	Orbke et al.	Jul 2011	B2
7996328	Lundberg et al.	Aug 2011	B1
8015023	Lee et al.	Sep 2011	B1
8027933	Lou et al.	Sep 2011	B2
8036993	Estes	Oct 2011	B2
8068930	Perez et al.	Nov 2011	B2
8103521	Kuebert et al.	Jan 2012	B2
8103716	Boyce 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
8249998	Reynolds et al.	Aug 2012	B2
8255235	Aldstadt	Aug 2012	B2
8255339	Andrew	Aug 2012	B2
8265947	Kuebert et al.	Sep 2012	B2
8291234	Snapp et al.	Oct 2012	B2
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
8386516	Owens et al.	Feb 2013	B2
8429019	Yeatts et al.	Apr 2013	B1
8463568	Wynn	Jun 2013	B1
8489520	Kuebert et al.	Jul 2013	B2
8554694	Ward et al.	Oct 2013	B1
8577802	Nichols et al.	Nov 2013	B1
8645232	Cole et al.	Feb 2014	B1
8731699	Nagy et al.	May 2014	B2
8736633	Gurusamy	May 2014	B2
8812374	Sriram et al.	Aug 2014	B1
9032032	Mills et al.	May 2015	B2
20010042024	Rogers	Nov 2001	A1
20010051885	Nardulli et al.	Dec 2001	A1
20020007299	Florence	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
20020032573	Williams et al.	Mar 2002	A1
20020032612	Williams et al.	Mar 2002	A1
20020032623	Wheeler et al.	Mar 2002	A1
20020042808	Smith et al.	Apr 2002	A1
20020070882	Jones	Jun 2002	A1
20020073039	Ogg et al.	Jun 2002	A1
20020082770	Jones	Jun 2002	A1
20020087371	Abendroth	Jul 2002	A1
20020103724	Huxter	Aug 2002	A1
20020107820	Huxter	Aug 2002	A1
20020111914	Terada et al.	Aug 2002	A1
20020120475	Morimoto	Aug 2002	A1
20020130065	Bloom	Sep 2002	A1
20020147919	Gentry	Oct 2002	A1
20020156645	Hansen	Oct 2002	A1
20020156846	Rawat et al.	Oct 2002	A1
20020165729	Kuebert et al.	Nov 2002	A1
20020178074	Bloom	Nov 2002	A1
20030003936	Tighe	Jan 2003	A1
20030004893	Blaesche	Jan 2003	A1
20030032573	Tanner et al.	Feb 2003	A1
20030036938	Dutta et al.	Feb 2003	A1
20030037009	Tobin et al.	Feb 2003	A1
20030074411	Nale	Apr 2003	A1
20030097287	Franz et al.	May 2003	A1
20030110170	Matsuoka	Jun 2003	A1
20030114206	Timothy et al.	Jun 2003	A1
20030182017	O'Donohue et al.	Sep 2003	A1
20030193414	Jones	Oct 2003	A1
20030195811	Hayes et al.	Oct 2003	A1
20030200168	Cullen et al.	Oct 2003	A1
20040030478	Holland et al.	Feb 2004	A1
20040073499	Martin et al.	Apr 2004	A1
20040088224	Mukai	May 2004	A1
20040093312	Cordery et al.	May 2004	A1
20040117326	Amato	Jun 2004	A1
20040117328	Andrew	Jun 2004	A1
20040133446	Myrick et al.	Jul 2004	A1
20040149824	Miller et al.	Aug 2004	A1
20040158351	Rivalto	Aug 2004	A1
20040193438	Stashluk et al.	Sep 2004	A1
20040199656	Pintsov	Oct 2004	A1
20040211834	Fleckenstein et al.	Oct 2004	A1
20040215480	Kadaba	Oct 2004	A1
20040221005	Albaugh et al.	Nov 2004	A1
20040227630	Shannon et al.	Nov 2004	A1
20040241644	Samadpour	Dec 2004	A1
20040243430	Horstemeyer	Dec 2004	A1
20040254802	Miller et al.	Dec 2004	A1
20040254811	Horstemeyer	Dec 2004	A1
20040260470	Rast	Dec 2004	A1
20050004877	McLellan	Jan 2005	A1
20050038758	Hilbush et al.	Feb 2005	A1
20050043845	Wiechers	Feb 2005	A1
20050071258	Kumakawa	Mar 2005	A1
20050080638	Maseruka	Apr 2005	A1
20050082752	Acosta	Apr 2005	A1
20050104716	Simms et al.	May 2005	A1
20050114221	Walters et al.	May 2005	A1
20050177387	Mojsa	Aug 2005	A1
20050216144	Baldassa	Sep 2005	A1
20050216294	Labow	Sep 2005	A1
20050216553	Mallonee et al.	Sep 2005	A1
20050251402	Olsen et al.	Nov 2005	A1
20050252596	Olsen et al.	Nov 2005	A1
20060010037	Angert et al.	Jan 2006	A1
20060022895	Williams et al.	Feb 2006	A1
20060041481	Stowe	Feb 2006	A1
20060047610	Parkos et al.	Mar 2006	A1
20060069601	Simon et al.	Mar 2006	A1
20060074729	Capotosto et al.	Apr 2006	A1
20060085273	Mayer et al.	Apr 2006	A1
20060097896	Jones	May 2006	A1
20060100970	Morony et al.	May 2006	A1
20060149577	Stashluk et al.	Jul 2006	A1
20060229895	Kodger, Jr.	Oct 2006	A1
20060248941	Maresca et al.	Nov 2006	A1
20060255136	Wagner et al.	Nov 2006	A1
20060282277	Ng	Dec 2006	A1
20070000989	Kadaba	Jan 2007	A1
20070005452	Klingenberg et al.	Jan 2007	A1
20070078797	Won et al.	Apr 2007	A1
20070083410	Hanna	Apr 2007	A1
20070133876	Chande et al.	Jun 2007	A1
20070150533	Krause et al.	Jun 2007	A1
20070156415	Foth et al.	Jul 2007	A1
20070156439	Fyda et al.	Jul 2007	A1
20070192191	Neal et al.	Aug 2007	A1
20070200671	Kelley et al.	Aug 2007	A1
20070202802	Kallio et al.	Aug 2007	A1
20070257774	Stumpert et al.	Nov 2007	A1
20080004995	Klingenberg et al.	Jan 2008	A1
20080080700	Mock et al.	Apr 2008	A1
20080125959	Doherty et al.	May 2008	A1
20080133261	Ray	Jun 2008	A1
20080154781	Kumar	Jun 2008	A1
20080162241	Betancourt	Jul 2008	A1
20080172305	Estes et al.	Jul 2008	A1
20080201155	Som	Aug 2008	A1
20080208772	Rundle	Aug 2008	A1
20080210749	Skaaksrud et al.	Sep 2008	A1
20080221913	Cook et al.	Sep 2008	A1
20080223940	Lee et al.	Sep 2008	A1
20080281719	Hall et al.	Nov 2008	A1
20080312991	Bharadwaj et al.	Dec 2008	A1
20080319970	Garner et al.	Dec 2008	A1
20080320092	Campbell et al.	Dec 2008	A1
20090012802	Pinney	Jan 2009	A1
20090046892	Avant et al.	Feb 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
20090164390	Calman et al.	Jun 2009	A1
20090173672	Avant et al.	Jul 2009	A1
20090187489	Mallick et al.	Jul 2009	A1
20090269760	Samadpour	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
20090327361	Mills et al.	Dec 2009	A1
20100004960	Frankenberg 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
20100100229	Whitson et al.	Apr 2010	A1
20100100497	Kuebert et al.	Apr 2010	A1
20100121689	Wallace et al.	May 2010	A1
20100185565	Wade	Jul 2010	A1
20100211426	McClurg	Aug 2010	A1
20100211444	Spear	Aug 2010	A1
20100228564	Kharraz Tavakol et al.	Sep 2010	A1
20100235210	Nadrotowicz, Jr.	Sep 2010	A1
20100299278	Kriss et al.	Nov 2010	A1
20110004562	Hennessy et al.	Jan 2011	A1
20110022532	Kriss	Jan 2011	A1
20110060552	Ono	Mar 2011	A1
20110125665	Kadaba	May 2011	A1
20110238195	Nagy et al.	Sep 2011	A1
20110270714	Myrick et al.	Nov 2011	A1
20110320308	Herrington	Dec 2011	A1
20120016948	Sinha	Jan 2012	A1
20120030133	Rademaker	Feb 2012	A1
20120047085	Naghshineh et al.	Feb 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
20120173308	Brown et al.	Jul 2012	A1
20120173448	Rademaker	Jul 2012	A1
20120179622	Amato	Jul 2012	A1
20120208559	Svendsen et al.	Aug 2012	A1
20120235791	Donlan et al.	Sep 2012	A1
20120246077	Skaaksrud et al.	Sep 2012	A1
20120303538	Marcus et al.	Nov 2012	A1
20120303539	Marcus et al.	Nov 2012	A1
20120303540	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
20130006731	Cook et al.	Jan 2013	A1
20130006777	Krishnareddy 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
20130024525	Brady et al.	Jan 2013	A1
20130054054	Tollenaere et al.	Feb 2013	A1
20130066744	Higgins et al.	Mar 2013	A1
20130073336	Heath	Mar 2013	A1
20130113819	Gurusamy	May 2013	A1
20130144428	Irwin et al.	Jun 2013	A1
20130212037	Briggman et al.	Aug 2013	A1
20130238599	Burris	Sep 2013	A1
20130238658	Burris	Sep 2013	A1
20130246396	Clare et al.	Sep 2013	A1
20130262336	Wan et al.	Oct 2013	A1
20130275328	Klingenberg et al.	Oct 2013	A1
20130291079	Lowe et al.	Oct 2013	A1
20140052661	Shakes et al.	Feb 2014	A1
20140180959	Gillen et al.	Jun 2014	A1
20140222711	Tibbs et al.	Aug 2014	A1
20140266668	Blankenship et al.	Sep 2014	A1
20150081587	Gillen	Mar 2015	A1
20150134560	Krishnaiahsetty	May 2015	A1
20150154559	Barbush et al.	Jun 2015	A1
20150242811	Gillen et al.	Aug 2015	A1

Foreign Referenced Citations (56)

Number	Date	Country
1643534	Jul 2005	CN
101203873	Jun 2008	CN
102567883	Jul 2012	CN
19644163	May 1998	DE
10007897	Jun 2001	DE
2483220	Mar 2012	GB
10-207956	Jul 1998	JP
11-139540	May 1999	JP
2000-339373	Aug 2000	JP
2001-014393	Jan 2001	JP
2001-022678	Jan 2001	JP
2002-042008	Feb 2002	JP
2002-056307	Feb 2002	JP
2005-213020	Aug 2005	JP
2006-206225	Aug 2006	JP
201220221	May 2012	TW
WO 2000019170	Apr 2000	WO
WO 2000019171	Apr 2000	WO
WO 2000030014	May 2000	WO
WO 2000046726	Aug 2000	WO
WO 2000046728	Aug 2000	WO
WO 2000052422	Sep 2000	WO
WO 2001016889	Mar 2001	WO
WO 2001029778	Apr 2001	WO
WO 2001035344	May 2001	WO
WO 2001039031	May 2001	WO
WO 2001065451	Sep 2001	WO
WO 2001065454	Sep 2001	WO
WO 2001065523	Sep 2001	WO
WO 2001065524	Sep 2001	WO
WO 2001067344	Sep 2001	WO
WO 2001072109	Oct 2001	WO
WO 2001084359	Nov 2001	WO
WO 2001088831	Nov 2001	WO
WO 2001097101	Dec 2001	WO
WO 2002007104	Jan 2002	WO
WO 2002017045	Feb 2002	WO
WO 2002052378	Jul 2002	WO
WO 2003034293	Apr 2003	WO
WO 2004015518	Feb 2004	WO
WO 2005105329	Nov 2005	WO
2011017286	Feb 2011	WO
WO 2011017286	Feb 2011	WO
WO 20110150971	Dec 2011	WO
2012045182	Apr 2012	WO
WO 2012045182	Apr 2012	WO
WO 2012129529	Sep 2012	WO
WO 2012135143	Oct 2012	WO
2012161728	Nov 2012	WO
2012161730	Nov 2012	WO
2012161731	Nov 2012	WO
2012161732	Nov 2012	WO
WO 2012161728	Nov 2012	WO
WO 2012161730	Nov 2012	WO
WO 2012161731	Nov 2012	WO
WO 2012161732	Nov 2012	WO

Non-Patent Literature Citations (285)

Entry
Fedex.com, “Package Recipients Can Now Customize Deliveries to their Home with FedEX Delivery Manager”, accessed Mar. 13, 2020, Apr. 23, 2013 (Year: 2013).
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/839,398, dated Feb. 22, 2016, 9 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/181,185, dated Apr. 13, 2016, 34 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Mar. 17, 2016, 22 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/100,556, dated Mar. 25, 2016, 54 pages, U.S.
“Fedex Improves Internal, External Operations,” Frontline Solutions, Apr. 5, 2001, pp. 1-2, www.frintlinemagazine.com/art_th/04052001.htx.
“Fedex Insight Empowers Customers with Enhanced Shipment Visibility and Control,” El Portal Del Transporte, Apr. 11, 2001, pp. 9-10.
“Many Happy Returns—UPS Unveils Advanced Outline Return Solution,” Business Wire, Sep. 20, 2000.
“RPS Adds Automated Package Pick-up to Dedesigned Web Site,” www.fedex.com/us/about/ground/pressreleases/pressrelease111198.html?link=4, retrieved Sep. 10, 2003.
“Schedule Distribution Routes and Timeslots,” IP Ventures; www.ipventure.com/onlineorder/distribution.php, retrieved on Apr. 16, 2008.
“Scheduling Software Helps Webvan Meet 30-Minute Delivery Window,” www.stores.org, Jul. 2000.
Author Unknown, “Outlook 2000 Handbook First Edition”, p. 95 (relevant part), last 9 lines; one page.
Author Unknown, ASP V16-System Walker List Works Manual (relevant part); p. 88, line 5, 3.4 Start up and termination of ListWORKS writer; one page.
Brewin, et al., “Follow that Package!” Computer World, Mar. 19, 2001, www.computerworld.com/printthis/2001//0,4814,58696,00.html.
Caminti, et al. “United Parcel Service Introduces Advanced Label Imaging System,” Business Wire, Nov. 29, 1989, p. 1.
Canadian Intellectual Property Office, Requisition by Examiner for Application No. 2,609,841, dated Dec. 2, 2011, 4 pages, Canada.
Canadian Intellectual Property Office, Requisition by Examiner for Application No. 2,504,285, Oct. 10, 2013, 2 pages, Canada.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,609,841, Oct. 6, 2014, 3 pages, Canada.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,609,841, Aug. 26, 2015, 5 pages, Canada.
Canadian Office Action dated Feb. 15, 2012, for Canadian Application No. 2,504,285.
De Marco, “E-tail Presents Can be Tougher to Send Back than Order,” Knight-Ridder/Tribune Business News, Dec. 28, 1999, The Dialog Corporation, US.
Declaration of David Ellison pertaining to UPS and Mailbox etc. pre-filing activities from Mar. 2001-Nov. 1, 2002.
European Patent Office, Communication Pursuant to Article 94(3) EPC for Application No. 06773704.9, dated Feb. 5, 2014, 6 pages, The Netherlands.
European Patent Office, Result of Consultation for Application No. 03778034.3, dated Dec. 2, 2013, 5 pages, The Netherlands.
FEDEX, “FedEx Mobile Ship”, retrieved from <http://www.fedex.com/us/mobile/label.html, redirected to http://mobilesolutions.fedex.com/shipping-label.html > on Sep. 25, 2013, 2 pages.
Gao, Huiji, et al., “Cyber-Physical-Social Systems: Harnessing the Crowdsourcing Power of Social Media for Disaster Relief”, IEEE Intelligent Systems, Copyright 2011, pp. 10-14, IEEE Computer Society.
Harrington, “The US Postal Service Gets Serious about Serving Business in the New Economy,” Journal, May 2000, p. 2, vol. 41, No. 5, Penton Publishing, Inc., USA.
Henderson, “Buy.com Boosts Returns Process Efficiency with New Solution,” ProQuest Info and Learning, Nov. 2000 pp. 72-76, vol. 82, No. 11.
International Preliminary Examining Authority, International Preliminary Report on Patentability for International Application No. PCT/US2013/068219, dated Dec. 12, 2014, 8 pages, United States Patent and Trademark Office, USA.
International Preliminary Examining Authority, International Preliminary Report on Patentability for International Application No. PCT/US2013/068210, dated Jan. 2, 2015, 9 pages, U.S. Patent and Trademark Office, USA.
International Search Report, dated Jul. 5, 2005 for International Application No. PCT/US2003/34746 filed Oct. 31, 2003.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US11/59506, dated Aug. 3, 2012, 9 pages, United States Patent and Trademark Office, USA.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US06/24169, dated May 10, 2007, 7 pages, United States Patent and Trademark Office, USA.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US11/59513, dated Apr. 27, 2012.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US11/59511, dated May 2, 2012.
International Searching Authority, International Search Report and Written Opinion, dated Apr. 24, 2012, for International Application No. PCT/US11/59504.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US2013/68219, dated Feb. 21, 2014, 13 pages, USA.
International Searching Authority, International Search Report and Written Opinion for International Application for PCT/US2013/68210, dated May 20, 2014, 9 pages, United States Patent and Trademark Office, USA.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US2011/059508, dated Feb. 4, 2015, 9 pages, U.S. Patent and Trademark Office, USA.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US2013/75572, dated Feb. 20, 2015, 14 pages, United States Patent and Trademark Office, USA.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US2014/042959, dated Aug. 4, 2015, 8 pages, United States Patent and Trademark Office, U.S.A.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US2015/019475, dated Aug. 31, 2015, 15 pages, European Patent Office, The Netherlands.
International Searching Authority, International Search Report and Written Opinion for International Application No. PCT/US2015/016025, dated Apr. 29, 2015, 10 pages, European Patent Office, The Netherlands.
Internet Archive WayBackMachine: www.usps.com, specifically, QuantumViewTM, https://web.archive.org/web/20021002110106/http://www.ups.com/iovs/ivs_learnmore.html, QuantumView Inbound, QuantumView Outbound, How QuantumView Outbound Works, Quantum View Service Options, QuantumView and UPS Administration, 15 pages, retrieved Sep. 27-28, 2015.
Kihon, Kara Jissen, “Made Business Seikou No Tameno Kanpeki Guide—How to E-Commerce”, p. 60, relevant part, one page.
Lindsay, Bruce R., “Congressional Research Service, Social Media and Disasters: Current Uses, Future Options, and Policy Considerations,” CRS Report for Congress, Sep. 6, 2011, 10 pages, Congressional Research Service.
Notice of Allowance dated Mar. 25, 2010 for U.S. Appl. No. 11/460,268.
Notice of Allowance dated Nov. 10, 2011 for U.S. Appl. No. 12/616,183.
Notice of Allowance dated Nov. 2, 2009 for U.S. Appl. No. 11/425,333.
Office Action dated Aug. 6, 2009 for U.S. Appl. No. 11/460,268.
Office Action dated Jan. 23, 2009 for U.S. Appl. No. 11/460,268.
Office Action dated Jan. 31, 2012, for U.S. Appl. No. 10/696,180, filed Oct. 28, 2003.
Office Action dated Jun. 11, 2009 for U.S. Appl. No. 11/425,333.
Office Action dated Oct. 15, 2008 for U.S. Appl. No. 11/425,333.
Office Action dated Sep. 23, 2011 for U.S. Appl. No. 12/616,183.
Office Action from U.S. Appl. No. 10/696,180 dated Aug. 19, 2009.
Office Action from U.S. Appl. No. 10/696,180 dated Dec. 9, 2009.
Office Action from U.S. Appl. No. 10/696,180 dated Feb. 3, 2009.
Office Action from U.S. Appl. No. 10/696,180 dated Feb. 15, 2011.
Office Action from U.S. Appl. No. 10/696,180 dated Jul. 7, 2011.
Office Action from U.S. Appl. No. 10/696,180 dated May 10, 2010.
Office Action from U.S. Appl. No. 10/696,180 dated Oct. 18, 2010.
Pender, “Hard Times are the Best Times,” Cio, Aug. 15, 2001, p. 3, www.cio.com/archive/081501/besttimes_content.html.
Raco Industries, “Increase Delivery Visibility and Simplify Your Process,” retrieved from <http://www.racointeractive.com/media/834/raco_interactive-pd.pdf>, on Sep. 25, 2013, 2 pages.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,185, dated Jan. 30, 2015, 20 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Feb. 27, 2015, 19 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, dated Feb. 27, 2015, 17 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Mar. 2, 2015, 19 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Mar. 2, 2015, 16 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Mar. 2, 2015, 16 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Mar. 2, 2015, 15 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Mar. 2, 2015, 16 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Mar. 3, 2015, 18 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Mar. 4, 2015, 16 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,191, dated Mar. 10, 2015, 15 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,198, dated Mar. 11, 2015, 14 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Mar. 12, 2015, 11 pages, USA.
U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,066, dated Mar. 20, 2015, 14 pages, USA.
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/913,066, dated Feb. 5, 2014, 11 pages, USA.
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/913,171, dated Feb. 11, 2014, 45 pages, USA.
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/913,191, dated Feb. 20, 2014, 25 pages, USA.
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/913,198, dated Mar. 6, 2014, 7 pages, USA.
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/326,750, dated Jun. 17, 2014, 17 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Sep. 19, 2012, 18 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Nov. 6, 2012, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Nov. 7, 2012, 23 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Nov. 27, 2012, 24 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Nov. 28, 2012, 25 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated May 8, 2013, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated May 10, 2013, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated May 16, 2013, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated May 21, 2013, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated May 15, 2013, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/181,185, dated Apr. 9, 2013, 19 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,185, dated Dec. 13, 2013, 31 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,171, dated Oct. 2, 2013, 36 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, dated Oct. 2, 2013, 30 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Aug. 29, 2013, 15 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Aug. 29, 2013, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Aug. 29, 2013, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Aug. 29, 2013, 15 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/181,185, dated Sep. 26, 2013, 27 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Oct. 8, 2013, 31 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Sep. 6, 2013, 14 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,066, dated Oct. 11, 2013, 22 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Oct. 2, 2013, 28 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Dec. 28, 2012, 27 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Feb. 4, 2013, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Feb. 6, 2013, 11 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Feb. 12, 2013, 11 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Feb. 15, 2013, 11 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Feb. 21, 2013, 12 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,191, dated Oct. 24, 2013, 26 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,198, dated Oct. 25, 2013, 25 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/696,180, dated Jul. 18, 2013, 38 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Dec. 31, 2012, 27 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Feb. 8, 2013, 9 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated May 15, 2013, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Aug. 29, 2013, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,807, dated Feb. 5, 2014, 29 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,887, dated Feb. 13, 2014, 29 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Dec. 27, 2013, 12 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Dec. 23, 2013, 16 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Feb. 13, 2014, 16 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Dec. 27, 2013, 11 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Dec. 27, 2013, 12 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Dec. 27, 2013, 12 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, dated Dec. 27, 2013, 15 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Dec. 26, 2013, 12 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Dec. 24, 2013, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,750, dated Jan. 30, 2014, 28 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,851, dated Feb. 21, 2014, 29 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/696,180, dated Mar. 13, 2014, 30 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/181,185, dated Mar. 27, 2014, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,185, dated May 16, 2014, 25 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,807, dated Jun. 26, 2014, 19 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,851, dated Aug. 5, 2014, 39 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Aug. 18, 2014, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Aug. 18, 2014, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Aug. 18, 2014, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Aug. 18, 2014, 20 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Aug. 18, 2014, 20 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Aug. 19, 2014, 22 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, daetd Aug. 19, 2014, 20 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Aug. 20, 2014, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Aug. 22, 2014, 20 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/762,969, dated Aug. 29, 2014, 38 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,750, dated Sep. 5, 2014, 7 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,807, dated Sep. 18, 2014, 6 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,887, dated Sep. 25, 2014, 16 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Oct. 7, 2014, 42 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/181,185, dated Nov. 7, 2014, 25 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,171, dated Nov. 20, 2014, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Nov. 20, 2014, 9 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,066, dated Nov. 26, 2014, 17 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,198, dated Dec. 1, 2014, 15 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,191, dated Dec. 5, 2014, 17 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,171, dated Mar. 24, 2015, 13 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,807, dated Apr. 7, 2015, 19 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,887, dated Apr. 9, 2015, 20 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/762,969, dated Apr. 14, 2015, 12 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,750, dated Apr. 20, 2015, 18 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,851, dated Apr. 29, 2015, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,185, dated Jun. 15, 2015, 21 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/181,185, dated Jun. 10, 2015, 29 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/696,180, dated Jun. 25, 2015, 45 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Jul. 17, 2015, 12 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Jul. 23, 2015, 21 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, dated Jul. 23, 2015, 21 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Jul. 23, 2015, 15 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Jul. 23, 2015, 21 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Jul. 23, 2015, 22 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Jul. 23, 2015, 19 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Jul. 23, 2015, 20 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Jul. 23, 2015, 20 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Jul. 23, 2015, 19 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/839,398, dated Jul. 7, 2015, 8 pages, USA.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,198, dated Sep. 24, 2015, 24 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,191, dated Sep. 24, 2015, 23 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/696,180, dated Oct. 8, 2015, 27 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,185, dated Oct. 20, 2015, 20 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Nov. 10, 2015, 15 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,066, dated Nov. 13, 2015, 24 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Nov. 17, 2015, 17 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Nov. 17, 2015, 16 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Nov. 17, 2015, 17 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Nov. 17, 2015, 20 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Nov. 17, 2015, 21 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, dated Nov. 17, 2015, 17 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Nov. 17, 2015, 18 pages, U.S.A.
Van Huzien, “Messaging: the Transport Part of the XML Puzzle,” IBM Developer Works, Jul. 2000, www.106.ibm/developerworks/library/xml-messaging/.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,609,841, Nov. 14, 2016, 8 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,191, dated Jan. 12, 2017, 24 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,171, dated Jan. 27, 2017, 25 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,066, dated Dec. 22, 2016, 19 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/696,180, dated Dec. 22, 2016, 31 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Jan. 11, 2017, 38 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/569,316, dated Dec. 22, 2016, 36 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,306, dated Dec. 23, 2016, 34 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,248, dated Dec. 23, 2016, 37 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,269, dated Jan. 10, 2017, 35 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,299, dated Dec. 23, 2016, 36 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/174,290, dated Dec. 28, 2016, 36 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,198, dated Feb. 3, 2017, 28 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/049,605, dated Dec. 12, 2016, 18 pages, U.S.A.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,924,132, Feb. 10, 2017, 4 pages, Canada.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13796181.9, dated Feb. 10, 2017, 5 pages, Germany.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13795343.6, dated Mar. 2, 2017, 5 pages, Germany.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13158961.6, dated Mar. 3, 2017, 6 pages, Germany.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13158964.0, dated Mar. 23, 2017, 7 pages, Germany.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13158965.7, dated Mar. 23, 2017, 7 pages, Germany.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13158966.5, dated Mar. 23, 2017, 6 pages, Germany.
European Patent Office, Communications pursuant to Article 94(3) EPC for Application No. 13158967.3, dated Mar. 23, 2017, 7 pages, Germany.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Mar. 15, 2017, 13 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,854, dated Mar. 9, 2017, 34 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,862, dated Feb. 27, 2017, 43 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,185, dated Mar. 23, 2017, 36 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/049,828, dated May 3, 2017, 24 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/100,556, dated May 1, 2017, 25 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/025,893, dated Apr. 7, 2017, 27 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/025,893, dated Sep. 22, 2016, 52 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/049,828, dated Oct. 3, 2016, 64 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/839,398, dated Oct. 6, 2016, 25 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/049,605, dated Aug. 25, 2016, 59 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Nov. 10, 2016, 19 pages, U.S.A.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,842,840, Nov. 4, 2015, 5 pages, Canada.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,171, dated Dec. 15, 2015, 26 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/465,555, dated Nov. 19, 2015, 22 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,887, dated Dec. 17, 2015, 28 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,750, dated Dec. 23, 2015, 26 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/326,851, dated Dec. 24, 2015, 29 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/746,842, dated Jan. 22, 2016, 22 pages, U.S.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/839,398, dated Jan. 20, 2016, 48 pages, U.S.
Non-Final Rejection dated Oct. 24, 2017 for U.S. Appl. No. 13/913,066.
Non-Final Rejection dated Nov. 22, 2017 for U.S. Appl. No. 14/025,893.
Non-Final Rejection dated Nov. 13, 2017 for U.S. Appl. No. 14/707,039.
Non-Final Rejection dated Nov. 8, 2017 for U.S. Appl. No. 10/696,180.
Final Rejection dated Sep. 20, 2017 for U.S. Appl. No. 14/100,556.
Final Rejection dated Oct. 2, 2017 for U.S. Appl. No. 14/049,605.
Annex to the communication dated Sep. 15, 2017 for EP Application No. 06773704.
Annex to the communication dated Oct. 12, 2017 for EP Application No. 13796181.
Non-Final Rejection dated Aug. 4, 2017 for U.S. Appl. No. 13/181,185.
Non-Final Rejection dated Aug. 3, 2017 for U.S. Appl. No. 14/623,145.
Final Rejection dated Sep. 11, 2017 for U.S. Appl. No. 13/913,185.
Final Rejection dated Jul. 28, 2017 for U.S. Appl. No. 13/913,198.
Final Rejection dated Jul. 18, 2017 for U.S. Appl. No. 13/913,171.
Final Rejection dated Jul. 11, 2017 for U.S. Appl. No. 13/746,854.
Final Rejection dated Jul. 10, 2017 for U.S. Appl. No. 13/913,191.
Final Rejection dated Jul. 10, 2017 for U.S. Appl. No. 13/746,862.
English Translation of CN Office Action dated Jun. 29, 2017 for CN Application No. 201380070854.
CN Office Action dated Jun. 29, 2017 for CN Application No. 201380070854.
CA Office Action dated Jul. 11, 2017 for CA Application No. 2942296.
Non-Final Rejection dated Jun. 14, 2017 for U.S. Appl. No. 14/049,605.
Final Rejection dated Jun. 29, 2017 for U.S. Appl. No. 13/746,842.
Final Rejection dated Jun. 29, 2017 for U.S. Appl. No. 13/569,316.
Final Rejection dated Jun. 27, 2017 for U.S. Appl. No. 13/174,248.
Final Rejection dated Jun. 5, 2017 for U.S. Appl. No. 13/839,398.
English Translation of CN Office Action dated Jun. 27, 2017 for CN Application No. 201380070843.
English Translation of CN Office Action dated Apr. 27, 2017 for CN Application No. 201380067429.
Communication from the Examining Division dated Apr. 10, 2017 for EP Application No. 06773704.
CN Office Action dated Jun. 27, 2017 for CN Application No. 201380070843.
CN Office Action dated Apr. 27, 2017 for CN Application No. 201380067429.
CA Office Action dated May 24, 2017 for CA Application No. 2885818.
CA Office Action dated May 23, 2017 for CA Application No. 2891876.
CA Office Action dated Jun. 6, 2017 for CA Application No. 2881201.
CA Office Action dated Apr. 27, 2017 for CA Application No. 2884747.
Annex to the communication dated Apr. 10, 2017 for EP Application No. 06773704.
EPO Summons to Attend Oral Hearing for Application No. 13795343.6, Nov 17, 2017, 9.
CA Office Action dated Nov. 22, 2017 for CA Application No. 2954156.
CA Office Action dated Nov. 20, 2017 for CA Application No. 2924132.
CA Office Action dated Dec. 27, 2017 for CA Application No. 2957135.
CA Office Action dated Dec. 22, 2017 for CA Application No. 2957133.
Extended European Search Report received for European Patent Application No. 13821253.5, dated May 17, 2016, 11 pages.
Final Office Action received for U.S. Appl. No. 14/025,893,dated Apr. 7, 2017, 23 pages.
Final Office Action received for U.S. Appl. No. 14/025,893, dated May 23, 2018, 32 pages.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,885,818, May 30, 2016, 4 pages, Canada.
Canadian Intellectual Property Office, Requisition by the Examiner for Application No. 2,884,747, May 30, 2016, 4 pages, Canada.
European Patent Office, Communication Pursuant to Rules 70(2) and 70a(2) EPC for Application No. 13796181.9, dated May 24, 2016, 9 pages, Germany.
European Patent Office, Extended European Search Report for Application No. 13821253.5, dated May 17, 2016, 11 pages, Germany.
European Patent Office, Extended European Search Report for Application No. 13795343.6, dated May 19, 2016, 9 pages, Germany.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/696,180, dated Jun. 1, 2016, 28 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,066, dated May 27, 2016, 25 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,171, dated Jun. 8, 2016, 22 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,198, dated Jun. 14, 2016, 23 pages, U.S.A.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/913,191, dated Jun. 9, 2016, 24 pages, U.S.A.

Related Publications (1)

	Number	Date	Country
	20150262125 A1	Sep 2015	US

Provisional Applications (1)

	Number	Date	Country
	61952163	Mar 2014	US

Determining alternative delivery destinations

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Term Extension

Abstract