Delivery of an item to a vehicle

Description

BACKGROUND

Traditionally, when a package is shipped, the package includes a shipping label that indicates both the consignee's name and the delivery address. The delivery address is a static physical location. However, the person identified as the consignee may not be at the delivery address during the time window when a package is scheduled to be delivered. In which case, a carrier may have to make multiple trips to the address to complete the delivery. This represents an inefficient use of carrier resources.

In other instances, a consignee may cancel other activities to ensure his or her presence at a delivery address to receive a scheduled package delivery due to the importance of the package. As a result, the consignee's movement is constrained due to the impending delivery of a package. Accordingly, a need exists for improved delivery options and methods that can accommodate consignee location changes.

BRIEF SUMMARY

In general, embodiments of the present invention provide systems, methods, apparatus, and computer program products for identifying the location of a consignee and proposing one or more alternative delivery locations.

In accordance with one aspect, a method for identifying an alternative delivery location for item bound for a customer is provided. The method includes the steps of (1) storing a customer profile associated with a customer, wherein (a) the customer profile comprises information associated with a vehicle of the customer, (b) the vehicle comprises a vehicle device configured to provide location information for the vehicle, and (c) the information associated with the vehicle of the customer is accessible by the customer via an interface; (2) receiving shipping information for an item to be delivered to the customer and associating the shipping information for the item with the customer profile, wherein the shipping information comprises a delivery location; (3) determining that the item is to be delivered to the vehicle of the customer; (4) responsive to determining that the item is to be delivered to the vehicle of the customer, automatically requesting location information for the vehicle, the location information to be generated by the vehicle device; (5) receiving location information for the vehicle location indicating the current location of the vehicle; and (6) updating the shipping information to indicate the delivery location as the current location of the vehicle.

In accordance with another aspect, a computer program product comprising at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) store a customer profile associated with a customer, wherein (a) the customer profile comprises information associated with a vehicle of the customer, (b) the vehicle comprises a vehicle device configured to provide location information for the vehicle, and (c) the information associated with the vehicle of the customer is accessible by the customer via an interface; (2) receive shipping information for an item to be delivered to the customer and associating the shipping information for the item with the customer profile, wherein the shipping information comprises a delivery location; (3) determine that the item is to be delivered to the vehicle of the customer; (4) responsive to determining that the item is to be delivered to the vehicle of the customer, automatically request location information for the vehicle, the location information to be generated by the vehicle device; (5) receive location information for the vehicle location indicating the current location of the vehicle; and (6) update the shipping information to indicate the delivery location as the current location of the vehicle.

In accordance with another aspect, an apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least (1) store a customer profile associated with a customer, wherein (a) the customer profile comprises information associated with a vehicle of the customer, (b) the vehicle comprises a vehicle device configured to provide location information for the vehicle, and (c) the information associated with the vehicle of the customer is accessible by the customer via an interface; (2) receive shipping information for an item to be delivered to the customer and associating the shipping information for the item with the customer profile, wherein the shipping information comprises a delivery location; (3) determine that the item is to be delivered to the vehicle of the customer; (4) responsive to determining that the item is to be delivered to the vehicle of the customer, automatically request location information for the vehicle, the location information to be generated by the vehicle device; (5) receive location information for the vehicle location indicating the current location of the vehicle; and (6) update the shipping information to indicate the delivery location as the current location of the vehicle.

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 a block diagram of system that can be used to practice various embodiments of the present invention;

FIG. 2 is a schematic of a mobile device in accordance with certain embodiments of the present invention;

FIG. 3 is a schematic of a one or more carrier servers in accordance with certain embodiments of the present invention;

FIG. 4 is a schematic of a carrier device in accordance with certain embodiments of the present invention;

FIG. 5 is a flowchart illustrating operations and processes that can be used m accordance with embodiments of the present invention;

FIG. 6 is a flowchart illustrating operations and processes that may be performed to determine a probable delivery location in accordance with various embodiment 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.

Generally, embodiments of the present invention provide systems and methods that can identify the location of a consignee and propose one or more alternative delivery location(s). The proposed delivery location may be based on the current location of the consignee, current address on the package to be delivered, information located in a social network (private or public), “to-be” location as determined by the consignee which would be transmitted to the carrier and/or a predicted consignee location. In other embodiments, the consignee or “carrier” may suggest an alternative location that may be a fixed location (e.g., an address, a retail location, a landmark, etc.) or a mobile location (e.g., dynamic location). This alternative location information may allow carriers to leverage internal package system information with current physical location information and potential physical locations to determine through internal network algorithms whether to stage, hold and/or re-distribute packages as required to meet customer needs. In some cases, particular customers who are mobile may not be required to stay in a fixed location to receive a delivery. The collected information may also facilitate increased delivery package density to a single location (mobile or fixed). In various embodiments, the same techniques for identifying alternative delivery locations may be used to identify alternative pickup locations as well.

In some embodiments, a method for delivering a shipment is provided. For example, a customer may register with a delivery service and elect a “Mobile Delivery” program. As part of the registration process, the system may allow the customer to register their mobile device, their physical location (i.e. social check-in service) and/or register their vehicle's location determining device (e.g., navigation device, other GPS enabled device). Also, the system may provide a list of social network options from which the user may select (e.g., Facebook, FourSquare, Yammer, Socialcast, etc.) and these social network accounts would be linked to the customer's account with the system (e.g., the system is a “friend” or otherwise linked). As will be described in more detail below, the system may use location information derived from the customer's mobile device and/or social networking accounts (e.g., public, business, private, vehicle, etc.) to facilitate delivery of a package.

When a package is bound for a Mobile Delivery customer, various embodiments may determine the location of the customer using the customer's mobile device GPS (global positioning system), a vehicle's positioning device (e.g., navigation system), social networks, prediction algorithms or a check-in service with the system. After determining the location of the customer, the system may send a message to the customer indicating the pending delivery and the original delivery location. The message may also provide one or more suggested alternative delivery location(s) and/or may allow the customer to suggest an alternative delivery location. In some embodiments, there may not be an original delivery address but instead the package may simply provide a unique identifier for the customer. In this case, the system would sent suggested delivery locations based on the location information derived from the customer's mobile device GPS (global positioning system), a vehicle's positioning device (e.g., navigation system), social networks, prediction algorithms or a check-in service with the system.

After the delivery location (e.g., original or alternative) is confirmed with the customer, the system may send a unique and secure identification code (e.g., a “Mobile Maxicode”) to the customer's mobile device for use at the time of delivery. The system may provide a carrier service provider with en-route delivery instructions based on the customer mobile device GPS and operational telematics from the delivery vehicle. The operational telematics may include the GPS location of the delivery vehicle along with dispatch information. Using this information, the dispatch plan for the carrier service provider may be altered to the new delivery location. U.S. Pat. No. 7,624,024, which is incorporated herein in its entirety by reference, provides a description of a system for updating a dispatch plan while a carrier service provider is en-route that may be used with various embodiments. In various embodiments, the driver will proceed to the delivery location, and locate the consignee. Once the consignee is located, the carrier service provider may verify the secure identification code previously sent to the customer's mobile device by scanning the identification code on the consignee's mobile device. In further embodiments, a delivery may be made to an unattended vehicle and/or pickup from an unattended vehicle as will be described in more detail below

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

As should be appreciated, the embodiments may be implemented in various ways, including as methods, apparatus, systems, or computer program products. Accordingly, the embodiments may take the form of an entirely hardware embodiment or an embodiment in which a processor is programmed to perform certain steps. Furthermore, the 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.

Particular 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 architecture that can be used in conjunction with various embodiments of the present invention. As shown in FIG. 1, the system architecture may include one or more mobile devices 101. For instance, the mobile devices 101 may be smartphone devices, mobile telephones, mobile computers, portable digital assistants (PDAs), laptop computers, gaming devices, electronic tablets, navigation systems, GPS tracking device and other types of similar electronic devices. Other mobile devices may include computers and/or GPS devices embedded in vehicles, jewelry, eyewear, watches or other items. In addition, in various embodiments, the mobile devices 101 may include digital imaging capabilities. For example, the mobile devices 101 may comprise a camera, barcode scanner, optical scanner, and/or the like.

The system 10 of FIG. 1 may further comprise one or more delivery vehicles 100, one or more customer computing devices 102, one or more carrier servers 104, one or more carrier devices 105, one or more Global Positioning System (GPS) satellites 115, one or more networks 135, one or more social network servers 103 and/or the like. Each of the components of the system 10 may be in electronic communication with (directly or indirectly), 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), cellular network, or the like.

Various embodiments may use other networks to identify customer locations such as RFID and NFC sites. For example, customers may interact with a poster with an installed NFC chip. When accessed with a mobile device, the mobile device may receive a coupon for the item displayed on the poster or be linked to the store/restaurant to place an order. At the same time, the location of the mobile device may be captured. These retailer/restaurant networks may be leveraged for delivery spots.

For RFID embodiments, the customer could carry an RFID tag that stores a unique personal identification number. Various retail stores, malls, hospitals, office buildings, etc. may have RFID readers distributed throughout the associated location that could interrogate the RFID tags and provide a location for the customer base on the read location. Video networks are another way to track locations especially when combined with other tracking methods listed in the document. The captured location information could be communicated to a carrier server to facilitate delivery of an item.

It should be noted that other system architectures are contemplated that may be used to practice various aspects of the invention. Thus, the system architecture provided in FIG. 1 is for illustrative purposes only and should not be construed to limit the scope of the invention. Further, while FIG. 1 illustrates certain system entities as separate, standalone entities, the various embodiments are not limited to this particular architecture.

a. Exemplary Mobile Device

FIG. 2 provides a schematic diagram of a mobile device 101 according to one embodiment of the present invention. In this particular instance, the mobile device 101 is a smartphone. However, it should be understood that the mobile device 101 illustrated and hereinafter described is merely illustrative of one type of device that may implement and/or benefit from various embodiments and, therefore, should not be taken to limit the scope of the invention. Thus, it should be noted that other types of electronic devices, such as mobile telephones, mobile computers, portable digital assistants (PDAs), laptop computers, gaming devices, electronic tablets, and other types of similar electronic devices, may employ various embodiments of the invention.

As shown, the mobile device 101 may include an antenna 212 (or multiple antennas 212) in communication with a transmitter 214 and a receiver 216. The mobile device 101 may also include a processor 220 (e.g., application processor and/or graphics processor) configured to provide signals to and receive signals from the transmitter 214 and receiver 216, respectively.

The processor 220 may, for example, be embodied as various configurations including circuitry, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in FIG. 2 as a single processor, in some embodiments the processor 220 comprises a plurality of processors.

The signals sent and received by the processor 220 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques such as Bluetooth™ (BT), Ultra-wideband (UWB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, and/or the like. In addition, these signals may include speech data, user generated data, user requested data, and/or the like.

In this regard, the mobile device 101 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. More particularly, the mobile device 101 may be capable of operating in accordance with various first generation (1G), second generation (2G), 2.5G, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP)), and/or the like. For example, the mobile device 101 may be capable of operating in accordance with 2G wireless communication protocols IS-136 (Time Division Multiple Access (TDMA)), Global System for Mobile communications (GSM), IS-95 (Code Division Multiple Access (CDMA)), and/or the like. Also, for example, the mobile device 101 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the mobile device 101 may be capable of operating in accordance with 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The mobile device 101 may be additionally capable of operating in accordance with 3.9G wireless communication protocols such as Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and/or the like. Additionally, for example, the mobile device 101 may be capable of operating in accordance with fourth-generation (4G) wireless communication protocols such as LTE Advanced and/or the like as well as similar wireless communication protocols that may be developed in the future.

Some Narrow-band Advanced Mobile Phone System (NAMPS), as well as Total Access Communication System (TACS), mobile devices 101 may also benefit from embodiments of this invention, as should dual or higher mode phones (for example, digital/analog or TDMA/CDMA/analog phones). Additionally, the mobile device 101 may be capable of operating according to Wi-Fi or Worldwide Interoperability for Microwave Access (WiMAX) protocols.

It is understood that the processor 220 may comprise circuitry for implementing audio/video and logic functions of the mobile device 101. For example, the processor 220 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the mobile device 101 may be allocated between these devices according to their respective capabilities. Additionally, the processor 220 may comprise an internal voice coder (VC) 220a, an internal data modem (DM) 220b, and/or the like. Further, the processor 220 may comprise functionality to operate one or more software programs, which may be stored in memory. For example, the processor 220 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow the mobile device 101 to transmit and receive web content, such as location-based content, according to a protocol, such as Wireless Application Protocol (WAP), hypertext transfer protocol (HTTP), and/or the like. The mobile device 101 may be capable of using a Transmission Control Protocol/Internet Protocol (TCP/IP) to transmit and receive web content across the internet or other networks.

The mobile device 101 may also comprise a user interface including, for example, an earphone or speaker 224, a ringer 222, a microphone 226, a display 228, a camera 232, a user input interface, and/or the like, which may be operationally coupled to the processor 220. In this regard, the processor 220 may comprise user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as, for example, the speaker 224, the ringer 222, the microphone 226, the display 228, the camera 232, and/or the like. The processor 220 and/or user interface circuitry comprising the processor 220 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (for example, software and/or firmware) stored on memory accessible to the processor 220 (for example, volatile memory 240, non-volatile memory 242, and/or the like). Although not shown, the mobile device 101 may comprise a battery for powering various circuits related to the mobile device 101, for example, a circuit to provide mechanical vibration as a detectable output. The user input interface may comprise devices allowing the mobile device 101 to receive data, such as a keypad 230, a touch display (not shown), a joystick (not shown), and/or other input device. In embodiments including a keypad, the keypad may comprise numeric (0-9) and related keys (#, *), and/or other keys for operating the mobile device 101.

As shown in FIG. 2, the mobile device 101 may also include one or more components for sharing and/or obtaining data. For example, the mobile device 101 may comprise a short-range radio frequency (RF) transceiver and/or interrogator 264 so data may be shared with and/or obtained from electronic devices in accordance with RF techniques. The mobile device 101 may comprise other short-range transceivers, such as, for example, an infrared (IR) transceiver 266, a Bluetooth™ (BT) transceiver 268 operating using Bluetooth™ brand wireless technology developed by the Bluetooth™ Special Interest Group, a wireless universal serial bus (USB) transceiver 270 and/or the like. The Bluetooth™ transceiver 268 may be capable of operating according to low power or ultra-low power Bluetooth™ technology (for example, Wibree™) radio standards. In this regard, the mobile device 101 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within a proximity of the mobile device 101, such as within 10 meters, for example. Although not shown, the mobile device 101 may be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.

The mobile device 101 may comprise memory, such as a subscriber identity module (SIM) 238, a removable user identity module (R-UIM), and/or the like, which may store information elements related to a mobile subscriber. In addition to the SIM 238, the mobile device 101 may comprise other removable and/or fixed memory. The mobile device 101 may include volatile memory 240 and/or non-volatile memory 242. For example, volatile memory 240 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like. Non-volatile memory 242, which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices (for example, hard disks, floppy disk drives, magnetic tape, etc.), optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 240, non-volatile memory 242 may include a cache area for temporary storage of data. The memories may store one or more applications (e.g., software programs), instructions, pieces of information, data, and/or the like which may be used by the mobile device 101 for performing functions of the mobile device 101. For instance, as described in greater detail below, one or more of the memories on the device 101 may store a smart code application 250 in various embodiments that performs various aspects of the claimed invention

b. Exemplary Carrier Server

FIG. 3 provides a schematic of a carrier server 104 according to one embodiment of the present invention. In general, the term “server” may refer to, for example, any computer, computing device, mobile phone, desktop, notebook or laptop, distributed system, server, blade, gateway, switch, processing device, or combination of processing devices adapted to perform the functions described herein. As will be understood from this figure, in one embodiment, the carrier server 104 may include a processor 60 that communicates with other elements within the carrier server 104 via a system interface or bus 61. The processor 60 may be embodied in a number of different ways. For example, the processor 60 may be embodied as one or more processing elements, one or more microprocessors with accompanying digital signal processors, one or more processors without accompanying digital signal processors, one or more coprocessors, one or more multi-core processors, one or more controllers, and/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, and/or the like.

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

In addition, in one embodiment, the earner server 104 may include at least one storage device 63, such as a hard disk drive, a CD drive, a DVD drive, and/or an optical disk drive for storing information on various computer-readable media. The storage device(s) 63 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, and/or the like. Additionally, each of these storage devices 63 may be connected to the system bus 61 by an appropriate interface.

Furthermore, a number of executable instructions, applications, scripts, program modules, and/or the like may be stored by the various storage devices 63 and/or within RAM 67. Such executable instructions, applications, scripts, program modules, and/or the like may include an operating system 80 and a data processing application 85. As discussed in greater detail below, this application 85 may control certain aspects of the operation of the carrier server 104 with the assistance of the processor 60 and operating system 80, although its functionality need not be modularized. In addition to the program modules, the carrier server 104 may store and/or be in communication with one or more databases, such as database 90.

Also located within and/or associated with the carrier server 104, in one embodiment, is a network interface 74 for interfacing with various computing entities. This communication may be via the same or different wired or wireless networks (or a combination of wired and wireless networks), as discussed above. 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), and/or any other wired transmission protocol. Similarly, the carrier server 104 may be configured to communicate via wireless external communication networks using any of a variety of protocols, such as 802.11, GSM, EDGE, GPRS, UMTS, CDMA2000, WCDMA, TD-SCDMA, LTE, E-UTRAN, Wi-Fi, WiMAX, UWB, NAMPS, TACS and/or any other wireless protocol.

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

c. Exemplary Carrier Device

With respect to the carrier device 105, FIG. 4 provides an illustrative schematic representative of a carrier device 105 that can be used in conjunction with the embodiments of the present invention (e.g., a carrier device 105 carried by an operator of a delivery vehicle 100). In some embodiments, a carrier device 105 may be configured to comprise any or all of the hardware and provide some or all of the functionality described above with regard to the example mobile device 101 of FIG. 2. As shown in FIG. 4, the carrier device 105 may comprise an antenna 412, a transmitter 404, a receiver 406, and a processing device 408, e.g., a processor, controller, and/or the like, that provides signals to and receives signals from the transmitter 404 and receiver 406, respectively.

The signals provided to and received from the transmitter 404 and the receiver 406, respectively, may include signaling information in accordance with an air interface standard of applicable wireless (or wired) systems. In this regard, the carrier device 105 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the carrier device 105 may operate in accordance with any of a number of second-generation (2G) communication protocols, third-generation (3G) communication protocols, fourth generation communication protocols (4G), near field communication protocols (NFC) and/or the like. Further, for example, the carrier device 105 may operate in accordance with any of a number of different wireless networking techniques, such as GPRS, GSM, EDGE, UMTS, CDMA2000, WCDMA, TD-SCDMA, LTE, E-UTRAN, Wi-Fi,

WiMAX, UWB, NAMPS, TACS, and/or any other wireless protocol. Via these communication standards and protocols, the carrier device 105 can communicate with the carrier server 104 and/or various other entities.

The carrier device 105 may also comprise a user interface (that can include a display 416 coupled to a processing device 408) and/or a user input interface (coupled to the processing device 408). The user input interface can comprise any of a number of devices allowing the carrier device 105 to receive data, such as a keypad 418, a touch display 420, barcode reader 430, RFID tag reader 432, and/or other input device. In embodiments including a keypad 418, the keypad 418 can include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the carrier device 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 and/or deactivate certain functions, such as screen savers and/or sleep modes. Although not shown, the carrier device 105 may also include a battery, such as a vibrating battery pack, for powering the various circuits that are required to operate the carrier device 105, as well as optionally providing mechanical vibration as a detectable output. The carrier device 105 may further include a printing device that may be utilized for printing various items, such as shipping labels and/or receipts.

The carrier device 105 can also include volatile memory 422 and/or non-volatile memory 424, which can be embedded or may be removable. For example, the non-volatile memory may be embedded or removable MMCs, SD memory cards, Memory Sticks, EEPROM, flash memory, hard disk, and/or the like. The memory can store any of a number of pieces or amount of information and data used by the carrier device 105 to implement the functions of the carrier device 105. The memories may store one or more applications (e.g., software programs), instructions, pieces of information, data, and/or the like which may be used by the carrier device 105 for performing functions of the carrier device 105. For instance, as described in greater detail below, one or more of the memories on the carrier device 105 may store an authentication application 440 in various embodiments that performs various aspects of the claimed invention. The carrier device 105 may also include a GPS module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, speed, universal time (UTC), date, and/or telematics information/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.

d. Exemplary Customer Computing Device

The customer computing devices 102 may each include one or more components that are functionally similar to those of the carrier server 104. For example, in one embodiment, each of the customer computing devices may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a display device/input device; (3) transitory and non-transitory memory; and (4) a communications interface. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments. The term “computing device” is used generically to refer to any computer, computing device, desktop, notebook or laptop, distributed system, carrier system, gateway, switch, or other processing device adapted to perform the functions described herein.

e. Exemplary Carrier Social Network Server

Various embodiments may include a carrier social network server that provides a carrier and/or business social network. The components of the carrier social network server may include one or more components that are functionally similar to those of the carrier server 104. For example, in one embodiment, each of the customer computing devices may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a display device/input device; (3) transitory and non-transitory memory; and (4) a communications interface. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments. The term “computing device” is used generically to refer to any computer, computing device, desktop, notebook or laptop, distributed system, carrier system, gateway, switch, or other processing device adapted to perform the functions described herein.

III. Exemplary System Operation

With the increasing sophistication of mobile devices, users can now access the Internet from almost anywhere. This allows business owners to conduct business in non-traditional locations such as coffee shops, restaurants, airports, etc. Additionally, users can also use mobile devices to access social networks. Various embodiments of the present invention harnesses the power of these sophisticated mobile devices and social networks to provide new delivery options for consignees for whom current delivery options may not be sufficient. For example, various embodiments may allow users to identify one or more alternative delivery locations. Moreover, the system may proactively suggest one or more alternative delivery location(s) to facilitate more efficient delivery. In addition, the system may determine the consignee has physical moved to another location (address, city, state, country) and has requested “follow-me” service that would automatically forward the package to the next available mobile delivery location.

1. Registration

In various embodiments, the process may begin at Block 500, in FIG. 5, with the enrollment/registration of one or more customers for a customer delivery program. Co-pending U.S. patent application Ser. No. 13/174,299, filed Jun. 30, 2011 and entitled “Customer Controlled Management of Shipments,” which is incorporated by reference herein in its entirety, describes a registration process and operations of various customer delivery programs that may operate in conjunction with embodiments of the present invention. A customer 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 customer mobile device 101 or computing device 102) may access a webpage or portal of a carrier, such as United Parcel Service of America, Inc. (UPS). For instance, the one or more carrier servers 104 may transmit a webpage that provides the customer with an option of logging into a customer account or enrolling/registering for a social customer delivery program via public social networks, business social networks and/or a private social network provided by the carrier.

In one embodiment, as part of the enrollment/registration process, the customer (e.g., a customer or customer representative operating a customer mobile device 101 or computing device 102) may be requested to provide biographic and/or geographic information by the one or more carrier servers 104. 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 addresses associated with the customer (e.g., street address, city, state, postal code, and/or country). For instance, Joseph Brown's address may be 105 Main Street, Atlanta, Ga. 30309, USA. As indicated, the customer may have multiple addresses associated with the account. For instance, Joseph Brown may have a home address and a business address associated with his account. Similarly, an organization may have multiple locations (e.g., addresses) associated with its account. When multiple addresses are provided, the customer may indicate which address should be used as the primary address. As will be recognized, the customer may provide other biographic and/or geographic information to adapt to various needs and circumstances.

In one embodiment, once the one or more carrier servers 104 receives the necessary biographic and/or geographic information from the customer or customer's external social network, the one or more carrier servers 104 may perform one or more validation operations. For example, the one or more carrier servers 104 may determine whether the primary address (and/or other addresses) in the specified country or postal code is eligible for a customer delivery program, such as for example a Mobile Delivery program as discussed in more detail below. The one or more carrier servers 104 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 one or more carrier servers 104 may perform a variety of fraud prevention measures as well, such as determining whether the customer or one of the customer's addresses has been “blacklisted” from customer delivery 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 one or more carrier servers 104 may create a customer profile for the customer via the enrollment/registration process. Accordingly, the one or more carrier servers 104 may create and store various customer profiles (e.g., via database 90 and/or carrier (private) internal social network). In addition to at least the information described above, a customer profile may include one or more corresponding usernames and passwords. Additionally, the one or more carrier servers 104 may also create and store a customer identifier (e.g., personal ID) in association with the customer profile. In one embodiment, a customer identifier may be used to uniquely identify a customer profile. In another embodiment, a customer identifier may be used to uniquely identify a given address associated with a customer profile and/or carrier (private) internal social network. In such an embodiment, if a customer profile is associated with four addresses, the one or more carrier servers 104 may create and store four customer identifiers in association with the customer profile. The customer identifier may also be stored in association with shipping data for an item to associate the item (and its shipping data) with the (a) correct customer (e.g., customer profile) and/or (b) correct address for a customer. In various embodiments, a customer identifier may be used in place of an address on an item as will be discussed in greater detail below.

In one embodiment, a customer profile within a earner social network may correspond to one or more customer delivery programs. For instance, a customer (e.g., a customer or customer representative operating a customer mobile device 101 or computing device 102) may subscribe to one or more specific customer delivery programs. For example, the various customer delivery programs may allow customers to have access to certain features, e.g., delivery alerts, approximate delivery times, change delivery options, electronically authorize the release of an item, and/or route items to will call. Other customer delivery programs may include allowing customers to route items to other retail locations, reschedule deliveries, request that items be delivered to another address, and/or provide instructions for delivery. As will be recognized, these features are provided for illustrative purposes and are not limiting to embodiments of the present invention. Moreover, a variety of other approaches and techniques can be used to adapt to various needs and circumstances.

In one embodiment, once a customer profile has been created by the one or more earner servers 104, the customer (e.g., a customer or customer representative operating a customer mobile device 101 or computing device 102) can provide various preferences associated with the customer delivery program to the one or more carrier servers 104 via a webpage, for example. For instance, the customer (e.g., a customer or customer representative operating a customer mobile device 101 or computing device 102) can provide a variety of preferences, such as communication preferences, delivery preferences, delivery options, and/or delivery instructions.

In various embodiments, one of the specific customer delivery programs offered is a “Mobile Delivery” program. When a user selects the Mobile Delivery program, the one or more carrier servers 104 may then allow the customer to register one or more mobile devices 101 such that the carrier server can access the GPS location of the mobile device(s). As will be described in more detail below, the location information derived from the mobile device 101 may be used to identify possible delivery locations.

The one or more carrier servers 104 may also provide a list of social network options from which the user may select. These options may include public Open Social Networks (e.g., Facebook, FourSquare, etc.), private carrier service Customer Social Networks (a private social network maintained by the carrier for users of the Delivery Service), a private Carrier Service Social Networks (a private social network maintained and constructed by the carrier via the carrier's internal operations' data to identify the members of a social network for consolidated deliveries), a user's Business Social Networks (e.g., Yammer, Socialcast, etc.) and/or a vehicle social network. Other social network options may be included as well. As will be discussed in greater detail below, information retrieved from these social networks may provide location information regarding the customer and thus be used to identify possible delivery locations. In various embodiments, a vehicle social network may communicate with vehicle devices (e.g., navigation devices, OnStar®, cellular terminals, etc.) associated with members of the vehicle social network. For example, the vehicle devices may communicate “checkin” and “checkout” events based on vehicle conditions and/or location information (e.g., GPS locations, proximate a retail location such as a shopping mall) to the vehicle social network. For example, a vehicle device may send a check-in message indicating a location of the vehicle to a vehicle social network when the vehicle has been turned off for a predetermined threshold time (e.g., 3 minutes, 1 hour) and a checkout message when the vehicle moves beyond a predetermined distance threshold from the checkin location. These locations may be used to facilitate item deliveries to or pickups from the vehicle.

In some embodiments, the one or more carrier servers 104 may determine whether the location(s) associated with the customer are available for the Mobile Delivery program. For example, some carriers may restrict the Mobile Delivery program to certain delivery areas or delivery types (e.g., restricted to particular cities, states, or domestic deliveries, etc.) This may be accomplished by the carrier using methods that consider physical locations of packages, service providers (delivery personnel), service vehicles, with customer reported and/or checked in social locations and/or customer vehicle reported and/or checked in locations via a social network.

2. Identifying Mobile Delivery Shipments

Following registration of a customer and creation of a customer profile, the process may continue to Block 510 of FIG. 5 where one or more items to be delivered to the customer by the carrier may be identified. By identifying items to be delivered to the customer, the one or more carrier servers 104 can provide the customer with access to various features of a customer delivery program for the item. As will be recognized, an item may be a parcel or group of parcels, a package or group of packages, scrap metal banded together, a vehicle part, a box, a crate, a drum, a box strapped to a pallet, and/or the like. In one embodiment, each item may include an item/shipment identifier, such as a barcode, a MaxiCode, electronic representation, and/or text. The item/shipment identifier (e.g., 123456789) may be used by the carrier to identify and track the item as it moves through the carrier's transportation network. Such item/shipment identifiers can be affixed to items by, for example, using a sticker (e.g., label) with the item/shipment identifier printed thereon (in human and/or machine readable form), an RFID tag with the item/shipment identifier stored therein or an electronic tag with a display screen.

In one embodiment, the one or more carrier servers 104 may store an item/shipment identifier in association with shipping data for the item. The shipping data may include information about the item, such as delivery service level. For example, the delivery service level may be Next Day Air, Next Day Air Early AM, Next Day Air Saver, 2nd Day Air, 2nd Day Air Early AM, 3 Day Select, and/or Ground. The shipping data may include information 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 data may also include information about the customer to whom the item is to be delivered (e.g., consignee), such as the customer's address (e.g., delivery location), the customer's phone number, the customer's name, and/or the like. In various embodiments, the shipping data may include a customer identifier in place of an address.

In one embodiment, the shipping data may include information about the item itself and any tracking information. The tracking information may reflect the item's movement in the carrier's transportation network, including expected 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., carrier device 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 (e.g., location and time of the scan or reading) to the one or more carrier servers 104. The one or more carrier servers 104 can then receive and use the information to track the item as it is transported though the carrier's transportation network and update the shipping data accordingly.

In one embodiment, the one or more carrier servers 104 can use the shipping data to identify one or more customer profiles corresponding to the item. As described, each customer profile may include one or more addresses associated with the customer. Thus, when the one or more carrier servers 104 receives shipping data (or a portion of shipping data) for an item, the one or more carrier servers 104 can determine whether the item corresponds to any customers enrolled/registered for a customer delivery program, such as the Mobile Delivery program.

After identifying the appropriate customer profile, the one or more carrier servers 104 can associate the shipping data with the customer profile. This may include appending the shipping data with the appropriate customer identifier (or other identifier corresponding to the customer profile). For instance, the shipping data for all shipments corresponding to Joseph Brown's customer profile may be appended with the customer identifier (or other identifier) created for Joseph Brown. In various embodiments, using this approach allows items (and their shipping data) to be linked to appropriate customer profiles. In some embodiments, the customer identifier may already be present in the shipping data. Based on the associated customer profile, the one or more carrier servers 104 can ascertain whether the customer has elected the Mobile Delivery program

3. Mobile Delivery

In various embodiments, when a Mobile Delivery shipment is identified, the associated customer may be notified that an item is en-route at Block 520 of FIG. 5. The notification may be provided in one or more formats including text messages (e.g., Short Message Service (SMS) and/or Multimedia Messaging Service (MMS), email messages, voice messages, and/or a variety of other messages in various communication formats.

In response to the notification, the customer (e.g., a customer or customer representative operating a customer mobile device 101 or computing device 102) may access a webpage or portal of a carrier and provide instructions on the type of delivery desired at Block 530. The customer may request immediate delivery to the original address thereby bypassing the Mobile Delivery. Alternatively, the customer may choose to have the item delivered via the Mobile Delivery service and/or to specific mobile locations and may also specify a delivery time. In some embodiments, the customer's item will automatically be delivered via the Mobile Delivery service unless the user requests otherwise on an item-by-item basis. In other embodiments, the user may need to log onto the carrier webpage or portal to request that an item be delivered via the Mobile Delivery service. In still other embodiments, the customer may choose the Mobile Delivery program as part of completing a transaction with an online merchant, in which case the shipment may be delivered automatically via the Mobile Delivery service by the carrier. In a still further embodiment, the item may be initially delivered to the original destination address. If the customer is not present at that location, the Mobile Delivery service may be automatically initiated (based on previous authorization from the customer).

Assuming the Mobile Delivery service is selected for the particular item(s) (e.g., by the customer or automatically), the one or more carrier servers 104 may identify possible alternative delivery location(s) at Block 540 for selection by the customer at Block 550. These alternative delivery location(s) may be determined based on the GPS location of the customer's mobile device 101 which may be accessed after the customer requested Mobile Delivery. The alternative delivery location(s) may also be determined by accessing the customer's social networks as previously authorized. Using this information, the one or more carrier servers 104 may identify potential delivery locations such as restaurants, retail stores, landmarks or other locations that are within a predetermine distance from the determined location of the customer.

In some embodiments, the one or more carrier servers 104 may use the location information to “pro-actively” identify potential delivery 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 the Mobile Delivery option). For example, the alternate delivery location(s) may be communicated to the customer with the notification or when the customer accesses the web portal. As discussed in greater detail with respect to FIG. 6 below, the one or more carrier servers may also use various algorithms to predict the location of a customer and offer these locations as possible alternative delivery locations.

In addition, using the location information, the one or more carrier servers 104 may identify potential delivery locations such as restaurants, retail stores, landmarks or other locations that are not within a predetermine distance from the “original” determined location of the customer, but now “follows the customer” to his/her next location. This location may be another city, state and/or country if said service has been authorized by the customer as a mobile delivery option. The carrier service provider may use navigation tools to find the delivery location, social network information including information about the customer and/or the customer's vehicle (which may be part of a vehicle social network). In various embodiments, the alternate delivery location may be provided directly from the customer as opposed to selecting a location proposed by the one or more carrier servers 104.

In further embodiments, the alternative delivery location may be a dynamic location based on the mobile device 101 GPS or social network account. For this embodiment, the customer may provide a base location (e.g., original address, current GPS location, retail store, landmark, intersection) and agree to remain within a predetermined distance from that location (e.g., 1 mile). For example, the customer may be shopping at nearby retail stores and request that the item is delivered to her dynamic location. The carrier service provider would then use the GPS location of the customer's mobile device 101, social network information including information 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 various embodiments, the carrier service provider may initially be en-route to the original address and receive a message from the one or more carrier servers 104 to re-route the item to a dynamic delivery location. The carrier service provider could then use navigation techniques, social network information including information about the customer and/or the customer's vehicle (which may be part of a vehicle social network) to locate the dynamic location of the customer. In some embodiments, the item may be delivered to a different delivery vehicle determined by the carrier that is already schedule to deliver near the dynamic location.

In various embodiments, once the alternative delivery location is selected by the customer (e.g., via the web portal or return message) at Block 550, the carrier will schedule the final delivery of the items via the Mobile Delivery service. The one or more carrier servers 104 may send a notification to the customer indicating the delivery date and time window at Block 560. In various embodiments, the notification may also include a unique human or machine-readable code. The unique human or machine-readable code may be an alphanumeric code, an image, a 1D or 2D barcode, a QR Code, a Maxicode, or the like. When the carrier service provider delivers the item, the carrier service provider may use the human or machine-readable code to confirm the user's identity at Block 570 (via authentication application 440). For example, the customer may retrieve the notification and associated code on a mobile device 101 and the carrier service provider may scan the code with the carrier device 105 or visually inspect the code to confirm the customer's identity. In other embodiments, near field communication protocols may be used to transfer identification information between the user's mobile device 101 and the carrier device 105. In further embodiments, the customer may be given or may select a personal identification number (PIN) which could be used to confirm the customer's identity. In still further embodiments, the customer may communicate a digital image (e.g., portrait of the customer) to the carrier and the carrier service provider may access the digital image using the carrier device 105 to confirm the customer's identity.

In some embodiments, a customer may also schedule an item pickup through the Mobile Delivery Service, via a similar process. In this case, the customer may access a web portal or webpage generated by the one or more carrier servers 104 and request an item pick-up under the Mobile Delivery program. Similar to the scheduling of item deliveries, the one or more carrier servers 104 may determine the location of the customer as generally described above and propose a pickup location. Similar types of notifications may also be sent regarding pick-ups as are discussed herein with respect to item deliveries. The item deliveries and pick-ups may then be completed by the Mobile Delivery service.

4. Predicting the Future Location o(a Customer

In various embodiments, the one or more carrier servers 104 may access vanous sources of data for use in predicting the location of the customer for use in suggesting a delivery location. One source of the data may be a calendar initiated during registration and maintained by the one or more carrier servers. With this calendar, the customer may indicate normal locations for the customers during certain time periods (e.g., working hours, days, weeks, months, years). Another source of data may be from social networking sites. As noted above, the customer may indicate the carrier as a friend or provide some other type of link with one or more social networks. In this way, the one or more carrier servers can periodically retrieve location information for the customer and/or review the customer's location history over a predetermined period of time. A further source of the data may be the customer's personal electronic calendar (e.g., Outlook, iPhone calendar, etc.) Other sources of data may include mobile device GPS locations and RFID tracking devices. In various embodiments, this data may be accessed when an item is bound for a Mobile Delivery customer. In some embodiments, the data may be accessed and stored (e.g., via database 90) periodically for prediction purposes.

Once an item has been identified as being bound for a Mobile Delivery customer as described above, the one or more carrier servers compares a projected delivery date as initially calculated by the carrier to the customer's electronic calendar (e.g., personal or maintained by carrier) and/or social network locations. One or more probable locations are identified based at least in part on this comparison. If more than one probable location is identified, the locations may be ranked based on the calculated probability.

FIG. 6 is flowchart illustrating an algorithm that may be used to predict the location of a customer for use in providing a proposed delivery location to a customer. The process beings at Block 600 with the one or more carrier servers 104 receiving data related to the customer's location. Sources of this data may include an electronic calendar hosted by the carrier, a customer's personal calendar (e.g., outlook calendar), social media location information (e.g., FaceBook, Linkedin, Twitter, MySpace, Google+, deviantART, LiveJournal, Tagged, Piinerest, Orkut, Pinterest, LINE (Japan), WeChat (China), etc.), geolocators (e.g., smart phones, car navigation devices, computer devices or internet connected devices with geolocation code information), and/or RFID tracing devices. In various embodiments, the one or more carrier servers 104 may periodically gather and store this data for use in further calculations. In other embodiments, the one or more carrier servers may access the data from the various sources as needed. Some embodiments may use a combination of real-time data and previously gathered/stored data.

The gathered data is compared against the anticipated delivery date (and possibly the time window) at Block 605. If there is a match at Block 610, the one or more carriers 104 assigns a probability value to the location. For example, the calendar may indicate the user will be working from an alternate office when the delivery is anticipated. The exemplary algorithm assigns a 60% probability to the match to the alternate office location. It should be understood that this is exemplary only and that other probability values may be assigned to matches as desired. Once the value is assigned, the process proceeds to Block 620 where further location data is analyzed.

In the event no match is found at Block 610, the process proceeds to Block 620 where other sources of location data are analyzed. For example, the one or more carrier servers 104 may review social media location information, geolocator information and/or RFID tracing devices to determine where the customer is typically located in relation to the anticipated delivery date and time window. For example, the one or more carrier servers 104 may analyze a certain time frame of data (e.g., a week, a month, a quarter, a year, etc.) to ascertain where the customer typically resides on certain days of the week (e.g., works at certain locations on certain days) or other patterns (e.g., customer frequents certain stores, restaurants, pharmacies, etc.). The one or more carrier servers 104 may then establish a threshold number of occurrences within a certain time frame to identify a location “match.” Multiple occurrences may be identified as a match if each location is within a certain threshold distance.

If one or more “matches” are found using the location data, the process continues to Block 625 where probability values are assigned to the one or more matches. If the “match” location was already assigned a probability value from the calendar analysis, the probability may be increased due to this additional match. If the match location is new, a separate value is assigned. In various embodiments, the probability value may be at least partially dependent on the number of matches within the historical data are found for the particular location.

At Block 630, the one or more carrier servers 104 determines if additional data should be retrieve for the location analysis. In some embodiments, the determination may be made based on the age of the historical data. For example, if the historical data was last updated over a particular time threshold (e.g., 3 months, 6 months, 1 year), the one or more carrier servers 104 may retrieve additional data. If the data is sufficiently current and/or complete, the process may proceed to Block 640.

At Block 640, a list of probable locations is generated. The list may include the locations identified in the calendar analysis and/or the location analysis. In various embodiments, the locations on the list are ranked based on the calculated probability.

After determining probable locations, the one or more carrier servers 104 may send a message to the associated customer that an item is en-route. The notification may be provided in one or more formats including text messages (e.g., Short Message Service (SMS) and/or Multimedia Messaging Service (MMS), email messages, voice messages, and/or a variety of other messages in various communication formats. In various embodiments the customer may be contacted with using social media methods of communication (i.e. FaceBook messages, tweets, etc.) pursuant to a customer's preference.

The message may include a list of the probable locations for selection by the customer. In various embodiments, the customer may need to access a carrier webpage or portal to select the desired location from the list of locations. A hyperlink may be provided in the message to the appropriate webpage to make the selection. In some embodiments, the customer may be permitted to provide a new delivery location as generally described above. After selection of the location, the item is delivered to the confirmed location. The location may be fixed or dynamic as noted above.

Various embodiments may also predict and change the communication method based on the customer's activity on the different social media channels. For example, a customer may prefer to communicate via FaceBook messages but when traveling to China, FaceBook is blocked in that country so the customer may switch to text messages. The customer's preferences as well as past activities may allow the algorithm to predict this switching pattern based on scheduled travel and locations.

5. Delivery to an Unattended Vehicle

In various embodiments, the earner may deliver I pick-up a shipment to an unattended vehicle as opposed to an address or to a specific person. To facilitate this type of delivery/pick-up, the customer may notify the carrier as to the location of the vehicle or give the carrier permission to automatically find the customer's vehicle. This may be accomplished by sending the GPS location of the vehicle using the customer's mobile device 101, a vehicle navigation system or third party car monitoring service, such as OnStar®. With this information, the one or more carrier servers 104 may route (or reroute) the customer's item to the received vehicle location for delivery or send dispatch carrier personnel to complete an item pick-up from an unattended vehicle.

When the carrier service provider arrives at the vehicle, the carrier service provider may use the carrier device 105 to contact an associated third party car monitoring service to send a signal to the vehicle to open the trunk or unlock the vehicle. Alternatively, the customer may provide the one or more carrier servers 104 with the appropriate codes to open the trunk of the vehicle. In this instance, the carrier service provider enters the code into a keypad associated with the vehicle or uses the carrier device 105 to send the appropriate signal to the vehicle to open the truck. The signal sent by the carrier device 105 would mimic the customer's key fob. After delivering the shipment, the carrier service provider would lock the trunk and/or vehicle.

6. Delivery to an Unattended Home

In various embodiments, the earner may deliver I pick-up a shipment to an unattended home. To facilitate this type of delivery I pick-up, the customer may notify the carrier as to give the carrier permission to enter an area of the home. This may be accomplished by sending the GPS location of the home location using the customer's mobile device 101, accessing a social network (public or private), a home security system and/or third party security monitoring service, such as ADT®. With this information, the one or more carrier servers 104 may route (or reroute) the customer's item to the received location for delivery or send dispatch carrier personnel to complete an item delivery I pick-up from an unattended home.

When the carrier service provider arrives at the home, the carrier service provider may use the carrier device 105 to contact an associated third party home monitoring service to send a signal to the home to open an area and/or unlock an area of the home (i.e. garage door). Alternatively, the customer may provide the one or more carrier servers 104 with the appropriate codes to open the home. In this instance, the carrier service provider enters the code into a keypad associated with the home or uses the carrier device 105 to send the appropriate signal to the home to open the home and/or designated area. The signal sent by the carrier device 105 would mimic the customer's key fob. After delivering the shipment, the carrier service provider would lock the home and/or area.

ZigBee networks are used for home and office automation. Typically these types of networks are used to control smart devices (door locks, lights, energy control systems, etc.). With a customer's permission, the carrier could use these devices to deliver packages into secure areas.

Claims

1. A method comprising: storing a user online profile that is accessible via a username and a password, wherein the user online profile is associated with a user;providing access to a mobile delivery service of a carrier through the user online profile;receiving, by one or more computer processors through the user online profile, an indication of an election to release an item at a vehicle associated with the user;receiving, by the one or more computer processors, shipping data for the item with the user online profile;determining, by the one or more computer processors and based at least in part on the user online profile, that the user has elected to release the item at the vehicle and has provided information about the vehicle including a third-party monitoring service;receiving, by the one or more computer processors, instructions to deliver the item to the vehicle using the third-party monitoring service;based at least in part on receiving the instructions to deliver the item to the vehicle using the third-party monitoring service, determining, by the one or more computer processors, a current location of the vehicle using the third-party monitoring service;determining, by the one or more computer processors, an estimated delivery time for the item based at least in part on the current location of the vehicle; andproviding, by the one or more computer processors, instructions to a computer device associated with the carrier, wherein the computer device generates an electronic communication to contact the third-party monitoring service to unlock the vehicle.
2. The method of claim 1, wherein storing the user online profile comprises storing information associated with the vehicle.
3. The method of claim 1, wherein generating the electronic communication to contact the third-party monitoring service to unlock the vehicle comprises generating a request to remotely unlock a trunk of the vehicle.
4. A method comprising: receiving a request from a user for mobile delivery of an item to a vehicle that is associated with the user;identifying the item to be delivered to the vehicle, wherein the item is associated with an item shipment identifier associated with shipping data for the item;storing, by one or more computer processors, a user profile associated with the user, wherein the user profile comprises information associated with the vehicle;receiving, by the one or more computer processors, an indication that permits a carrier service to contact a third-party monitoring service in order to deliver the item;receiving, by the one or more computer processors, shipping data for the item to be delivered to the user and utilizing the shipping data to identify the user profile corresponding to the item to be delivered, wherein the shipping data comprises a fixed delivery location;providing, by the one or more computer processors, an interactive user interface for display via a mobile device, wherein the interactive user interface comprises visually selectable indicia of an alternate dynamic delivery option;receiving, by the one or more computer processors, a request to change the fixed delivery location indicated in the shipping data to a dynamic delivery location, wherein the dynamic delivery location is a real-time location of the vehicle, and the request to change the fixed delivery location is based on a user selection of the visually selectable indicia of the alternate dynamic delivery option presented via the interactive user interface;responsive to receiving the request to change the fixed delivery location to the dynamic delivery location, electronically generating, by the one or more computer processors, updated shipping data to indicate the dynamic delivery location;accessing, by the one or more computer processors, the user profile to identify the vehicle;requesting, by the one or more computer processors, real-time location information for the vehicle;receiving, by the one or more computer processors, the real-time location information for the vehicle, wherein the real-time location information (a) indicates a current location of the vehicle and (b) comprises coordinates of the vehicle;analyzing, by the one or more computer processors, location information for the vehicle to determine an alternative delivery location based at least in part on identified location patterns;providing, by the one or more computer processors, the alternative delivery location for display via the interactive user interface;electronically changing, by the one or more computer processors, the shipping data to indicate the dynamic delivery location as the current location of the vehicle; andhaving the item directly delivered by the carrier service to the dynamic delivery location, wherein, based on receiving the indication of permission, the carrier service generates an electronic communication requesting that the third-party monitoring service unlocks the vehicle to allow the carrier service to complete delivery of the item to the vehicle.
5. The method of claim 4, further comprising transmitting, by the one or more computer processors, a notification indicating receipt of the item, wherein the notification comprises information identifying the alternative delivery location for selection by the user via the interactive user interface, and the alternative delivery location comprises the vehicle.
6. The method of claim 4, further comprising transmitting, by the one or more computer processors to the third-party monitoring service, the electronic communication requesting that the third-party monitoring service unlock the vehicle.
7. The method of claim 4, wherein the electronic communication requesting that the third-party monitoring service unlock the vehicle comprises a request to remotely open a trunk of the vehicle.
8. The method of claim 4, further comprising determining, by the one or more computer processors, an estimated delivery time for the item based at least in part on the current location of the vehicle.
9. The method of claim 4, further comprising: transmitting, by the one or more computer processors, a notification indicating receipt of the item.
10. The method of claim 4, further comprising: receiving updated location information for the vehicle; andpredicting, by the one or more computer processors, the location of the vehicle based at least in part on the updated location information for the vehicle.
11. An 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 at least one processor, cause the apparatus to at least: receive a request by a user for mobile delivery of an item to a vehicle that is associated with the user;identify the item to be delivered to the vehicle, wherein the item is associated with an item shipment identifier associated with shipping data for the item;transmit a notification of receipt indicating receipt of the item;store a user profile associated with the user, wherein (a) the user profile comprises information associated with the vehicle of the user, (b) the user profile provides the user with access to the information associated with the vehicle via an interactive interface executing on a mobile device based at least in part on access credentials, and (c) the user profile provides the user with access to information associated with the item via the interactive interface executing on the mobile device based at least in part on the access credentials;receive an indication that permits a carrier service to contact a third-party monitoring service in order to deliver the item;receive shipping data for the item to be delivered to the user and utilize the shipping data to identify the user profile, wherein the shipping data comprises a delivery location;access the user profile to identify the vehicle;receive real-time location information for the vehicle, wherein the real-time location information (a) indicates a current location of the vehicle and (b) comprises coordinates of the vehicle; andcause direct delivery of the item to the vehicle, wherein, based on receiving the indication of permission, the carrier service generates an electronic communication requesting that the third-party monitoring service unlock the vehicle to allow the carrier service to complete delivery of the item to the vehicle.
12. The apparatus of claim 11, wherein the notification of receipt comprises information identifying one or more alternative delivery locations for selection by the user.
13. The apparatus of claim 11, wherein the memory and the program code are further configured to, with the at least one processor, cause the apparatus to transmit, to the third-party monitoring service, the electronic communication requesting that the third-party monitoring service unlock the vehicle.
14. The apparatus of claim 11, wherein the electronic communication requesting that the third-party monitoring service unlock the vehicle comprises a request to remotely open a trunk of the vehicle.
15. The apparatus of claim 11, wherein the memory and the program code are further configured to, with the at least one processor, cause the apparatus to determine an estimated delivery time for the item based at least in part on the current location of the vehicle.
16. The apparatus of claim 11, wherein the memory and the program code are further configured to, with the at least one processor, cause the apparatus to: receive updated location information for the vehicle; andpredict the location of the vehicle based at least in part on the updated location information for the vehicle.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/707,039 filed May 8, 2015, which is a continuation of U.S. patent application Ser. No. 13/839,398 filed Mar. 15, 2013, which claims priority to U.S. patent application Ser. No. 61/745,253 filed Dec. 21, 2012, which is incorporated herein in its entirety by reference.

US Referenced Citations (393)

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
5398277	Martin, Jr.	Mar 1995	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
6967575	Dohrmann et al.	Nov 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
7401357	Hasegawa et al.	Jul 2008	B2
7422149	Aptekar	Sep 2008	B2
7479899	Horstemeyer	Jan 2009	B2
7501946	Anigan et al.	Mar 2009	B2
7511617	Burman et al.	Mar 2009	B2
7528722	Nelson	May 2009	B2
7531163	Samadpour	May 2009	B2
7542972	Owens et al.	Jun 2009	B2
7574366	Burman et al.	Aug 2009	B2
7580845	Burman et al.	Aug 2009	B2
7624024	Levis et al.	Nov 2009	B2
7647231	Kuebert et al.	Jan 2010	B2
7657466	Klingenberg et al.	Feb 2010	B2
7663502	Breed	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 et al.	Jan 2011	B2
7912854	Owens et al.	Mar 2011	B2
7925524	Florence	Apr 2011	B2
7962422	Melechko et al.	Jun 2011	B1
7969306	Ebert et al.	Jun 2011	B2
7984289	Orbke et al.	Jul 2011	B2
7996328	Lundberg et al.	Aug 2011	B1
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
10387824	Gillen et al.	Aug 2019	B2
11144872	Gillen et al.	Oct 2021	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
20020022979	Whipp	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
20020046173	Kelly	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
20020143430	Sansone	Oct 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
20020180582	Nielsen	Dec 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, III et al.	Oct 2003	A1
20040030478	Holland et al.	Feb 2004	A1
20040073499	Martin et al.	Apr 2004	A1
20040084527	Bong et al.	May 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
20040220845	Malapitan	Nov 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
20040243664	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
20050030152	Cooper	Feb 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
20050119786	Kadaba	Jun 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
20060128023	Waterhouse et al.	Jun 2006	A1
20060149577	Stashluk et al.	Jul 2006	A1
20060225140	Mergenthaler	Oct 2006	A1
20060229895	Kodger	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	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	Nov 2007	A1
20070290789	Segev et al.	Dec 2007	A1
20070296545	Clare	Dec 2007	A1
20080004995	Klingenberg et al.	Jan 2008	A1
20080080700	Mock et al.	Apr 2008	A1
20080125959	Doherty	May 2008	A1
20080133261	Ray	Jun 2008	A1
20080147268	Fuller	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
20090164277	Bhattacharya	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
20090271002	Asofsky	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
20100066513	Bauchot	Mar 2010	A1
20100076903	Klingenberg et al.	Mar 2010	A1
20100100229	Whitson et al.	Apr 2010	A1
20100100233	Lu	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
20100332284	Hilbush	Dec 2010	A1
20110004562	Hennessy et al.	Jan 2011	A1
20110022532	Kriss	Jan 2011	A1
20110060552	Ono	Mar 2011	A1
20110074570	Feldstein et al.	Mar 2011	A1
20110119133	Igelman et al.	May 2011	A1
20110125665	Kadaba	May 2011	A1
20110238195	Nagy et al.	Sep 2011	A1
20110270714	Myrick et al.	Nov 2011	A1
20110320308	Dearlove et al.	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
20120105197	Kobres	May 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
20120220307	Wohlert 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
20120306618	Tieman et al.	Dec 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
20150262125	Sager et al.	Sep 2015	A1
20180061154	Scalisi et al.	Mar 2018	A1
20200027295	Bigert et al.	Jan 2020	A1

Foreign Referenced Citations (55)

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

Non-Patent Literature Citations (33)

Entry
Just-Auto, Vehicle access, anti-theft and security intelligence service, QUBE, Apr. 5, 2012.
Office Action received for Canadian Patent Application No. 3,028,412, dated Mar. 31, 2021, 4 pages.
Notice of Allowance received for U.S. Appl. No. 16/058,682, dated Jun. 9, 2021, 15 pages.
Antony et al., “Code Secures Online Sales Deliveries”, Computer Weekly, Reed Business Information Ltd, 4, Apr. 19, 2001.
Pre-interview First Office Action received for U.S. Appl. No. 16/058,682, dated Nov. 13, 2020, 13 pages.
Pre-interview First Office Action received for U.S. Appl. No. 16/503,033, dated Oct. 29, 2020, 17 pages.
Office Action received for Canadian Patent Application No. 2,954,156, dated Nov. 9, 2021, 5 pages.
“ASP V16-System WalkerList WORKS Manual”, 3.4 Start up and termination of ListWORKS writer, p. 88 (line 5 and lines 17-19).
Brewin et al., “Follow that Package!”, ComputerWorld, Available online at: < www.computerworld.com/printthis/2001//0,4814,58696,00.html>, Mar. 19, 2001, 7 pages.
Caminiti et al., “United Parcel Service Introduces Advanced Label Imaging System”, Business Wire, Section 1, Nov. 29, 1989, pp. 1-3.
“Declaration of David Ellison Pertaining to UPS and Mailbox etc.” Pre-filing activities from Mar. 2001-Nov. 1, 2002, 7 pages.
De Marco, Donna, “E-tail Presents Can be Tougher to Send Back than Order”, Knight-Ridder/Tribune Business News, The Dialog Corporation, Dec. 28, 1999, 2 pages.
El Portal Del Transporte, “Fedex Insight Empowers Customers with Enhanced Shipment Visibility and Control”, Available online at: <http://www.transportando.net/newsabri1_completa.htm>, Apr. 11, 2001, pp. 9-10.
Fedex, “Mobile Shipping Label”, Available online at: <http://mobilesolutions.fedex.com/shipping-label.html>, Accessed on Sep. 25, 2013, 2 pages.
Fedex, “RPS Adds Automated Package Pick-up to Redesigned Web Site”, FedEx Ground Press Releases, Available online at: <www.fedex.com/us/about/ground/pressreleases/pressrelease111198.html?link=4>, Nov. 11, 1998, 1 page.
Frontline Solutions, “FedEx Improves Internal, External Operations”, Fairfax, Available online at: < http://www.frontlinemagazine.com/art_th/04052001.htx>, Apr. 5, 2001, pp. 1-4.
Gao et al., “Harnessing the Crowdsourcing Power of Social Media for Disaster Relief”, Cyber-Physical-Social Systems, IEEE Intelligent Systems, IEEE Computer Society, 2011, pp. 10-14.
Harrington, Lisa H., “The US Postal Service Gets Serious about Serving Business in the New Economy”, Transportation & Distribution, vol. 41, No. 5, Penton Publishing, Inc., May 2000, 3 pages.
Henderson, Timothy P., “Buy.com Boosts Returns Process Efficiency with New Solution”, ProQuest Info & Learning, vol. 82, No. 11, Nov. 2000, pp. 72-76.
Henderson, Timothy P., “Scheduling Software Helps Webvan Meet 30-Minute Delivery Window”, Descartes, Stores, Available online at: <www.stores.org>, Jul. 2000, 2 pages.
IPVenture, “Schedule Distribution Routes and Timeslots”, IP Ventures, Available online at: <https://www.ipventure.com/onlineorder/distribution.php>, Accessed on Apr. 16, 2008, 1 page.
Kihon, Kara J., “Made Business Seikou No Tameno Kanpeki Guide How To eCommerce”, Screen for package tracking by Yamato Transport Co., Ltd., p. 60.
Lindsay, Bruce R., “Social Media and Disasters: Current Uses, Future Options, and Policy Considerations”, CRS Report for Congress, Congressional Research Service, Sep. 6, 2011, 14 pages.
“Many Happy Returns—UPS Unveils Advanced Outline Returns Solution”, New Electronic Service Simplifies, Business Wire, Sep. 20, 2000, 3 pages.
“Outlook 2000 Handbook First Edition”, 2000, Related Information, p. 95 (last 9 lines), Selecting of Handling, p. 96 (last 9 lines).
Pender, Lee, “Hard Times are the Best Times”, Cio Magazine, Available online at: <www.cio.com/archive/081501/besttimes_content.html>, Aug. 15, 2001, 5 pages.
“Quantum View Inbound, Quantum View Outbound, How Quantum View Outbound Works, Quantum View Service Options, Quantum View and UPS Administration”, My UPS.com, Available online at : <http://www.ups.com/iovs/ivs_learnmore.html>, Accessed on Aug. 7, 2002, 15 pages.
RACO Interactive, “Increase Delivery Visibility And Simplify Your Process”, Available online at: <http://www.racointeractive.com/media/834/raco_interactive-pd.pdf>, Accessed on Sep. 25, 2013, 2 pages.
Van Huzien, Gordon, “Messaging: The Transport Part of The XML Puzzle”, IBM Developer Works, Article, Available online at: <http:/ /www-106.ibm.com/developerworks/library/xml-messaging/>, Jul. 2000, 8 pages.
Charles, Arthur, “Massive Rise in Internet Shopping at Christmas”, The Independent, Foreign Edition: 2, Jan. 18, 2003, 1 page.
Vehicle Access, Anti-Theft and Security Intelligence Service, Just-auto, QUBE, Apr. 5, 2012, 45 pages.
Office Action received for Canadian Patent Application No. 2,954,156, dated Nov. 9, 2022, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 17/471,819, dated Mar. 23, 2023, 14 pages.

Related Publications (1)

	Number	Date	Country
	20200219059 A1	Jul 2020	US

Provisional Applications (1)

	Number	Date	Country
	61745253	Dec 2012	US

Continuations (2)

	Number	Date	Country
Parent	14707039	May 2015	US
Child	16818605		US
Parent	13839398	Mar 2013	US
Child	14707039		US

Delivery of an item to a vehicle

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Term Extension

Abstract