Patent Grant
10817826
Embodiments of the present invention pertain to providing custom control and flexibility to consignors, consignees, and carriers for delivery of an item, such as a parcel or package, by a common carrier.
The package delivery business typically involves three main entities in the course of delivering a package: a carrier, a consignor, and a consignee. The carrier typically arranges the delivery of a package between the consignor and the consignee, and is often referred to as a package delivery provider, service provider, or common carrier. The consignor is the entity that causes the package to shipped, and can be referred to as the shipper or originator. The intended recipient of the package is the consignee. In the case of a package being shipped as part of a mail-order or Internet-based purchase, typically the consignor is the merchant and the consignee is the customer of the merchant.
The process of delivering a package is well known. Typically, the consignor prepares the item to be shipped, selects a carrier and class of service (e.g., normal or expedited delivery), and arranges for the carrier to gain custody of the package. This may occur by the consignor bringing the package to a carrier's pickup location or arranging the carrier to pick up the package at the consignor's premises. Once the carrier takes possession, the carrier routes the package to a handling facility in the town or serving area of the consignee. The package is then delivered to the consignee, usually using a delivery vehicle.
Typically, the carrier maintains a regular route for the delivery of packages, and along the route will stop at the appropriate consignee's address and attempt to deliver the package. In an optimal delivery experience, the carrier delivers the package on the initial attempt to the consignee, who is present to accept the package.
However, as can be expected, in many instances the delivery experience is not optimal in that the package is not successfully delivered on the initial attempt. There are a number of reasons why this may occur. A common reason is that the consignee is not present, and therefore unable to receive and sign for the package. In some circumstances, this may not be a problem because the delivery location is determined to be secure and/or the class of service associated with the delivery may not require a signature. For example, a class of service may not require a consignee's signature for delivery or a secure lockbox may be provided for deposit of the package. However, in many instances, the class of service (or other constraints) requires a recipient to be present to accept and sign for delivery. This results in the consignee and the carrier entering into various procedures to coordinate a follow-up delivery attempt.
For a delivery provider, such as UPS, handling millions of deliveries each day, each failed delivery attempt requires additional time and resources for coordinating a follow-up delivery attempt. Not only does this result in decreased efficiency for the carrier, but it results in an undesirable delivery experience for the consignee, and potentially the consignor as the package is not delivered as soon as it could be.
Thus, in order to affect an optimal delivery experience, coordination is required between the consignor, carrier, and consignee. All the parties have an interest in achieving prompt delivery.
However, in many instances, delays may occur, schedules may change, or there may not be complete knowledge by all three parties of the details of the delivery. For example, a consignor may be delayed in providing the package for shipment, thus resulting in delaying the anticipated date of delivery to the consignee. Alternatively, the consignee may not be able to accept delivery because he is not present. For example, the consignee may have stepped away from the delivery location for a brief time period, or may be away on vacation. Often, the consignee works during normal delivery hours and cannot be present at a residential address to accept delivery. Or the consignee may plan to be present, but due to a schedule change, cannot be present.
In other instances, the delivery may occur, but in less than optimal circumstances. For example, delivery of the package may be accomplished, but the placement of the package at the consignee's delivery location may not be as the consignee desired. For example, the consignee may desire the carrier to deliver the package to a side entrance instead of a front entrance so as to avoid theft. Or, the consignee may regularly use the side entrance rather the front entrance. The consignee may have desire to have the package placed in a secure lockbox, but has not communicated a combination to the carrier for unlocking the lockbox.
Thus, systems and methods are needed to allow for greater coordination between the consignor, the carrier, and the consignee of a package so as to achieve a successful and optimal delivery experience without wasting resources and incurring unnecessary delays in the package delivery process.
In general, embodiments of the present invention provide methods, systems, computing devices, and/or the like for providing at least one instruction for delivering an item to a customer by a carrier.
In accordance with one aspect, a method is provided. In one embodiment, the method comprises receiving at least one instruction for delivering a package to be delivered by a carrier to a customer, the at least one instruction (a) comprising information for delivering the package at a delivery location for the customer and (b) provided by the customer (i) after shipment of the package to the customer and (ii) prior to a first delivery attempt of the package by the carrier; and transmitting at least a portion of the at least one delivery instruction to a portable computing device for display by the portable computing device to delivery personnel for delivering the package in accordance with the at least one instruction.
In accordance with another aspect, a computing system comprising at least one processor and at least one memory is provided. In one embodiment, the computing system is configured to receive at least one instruction for delivering a package to be delivered by a carrier to a customer, the at least one instruction (a) comprising information for delivering the package at a delivery location for the customer and (b) provided by the customer (i) after shipment of the package to the customer and (ii) prior to a first delivery attempt of the package by the carrier; and transmit at least a portion of the at least one delivery instruction to a portable computing device for display by the portable computing device to delivery personnel for delivering the package in accordance with the at least one instruction.
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:
The present inventions 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. Like numbers refer to like elements throughout.
Service Overview
There are three main entities involved in the delivery of a package: the consignor, the carrier, and the consignee. In order to provide various personalized delivery services that may arise in conjunction with the delivery of a package, methods and systems are defined for coordinating and personalizing the delivery experience between these three entities. The flexibility of the various means of communication between these entities, as well as the variety of information that can be conveyed, allows the carrier to accommodate various unforeseen circumstances that may occur in conjunction with the delivery of a package. The communication and coordination associated with the personalization of the delivery service may occur either at the request of the consignee or the consignor.
Although the embodiments disclosed herein are disclosed in the context of the delivery of a package, the principles of the present invention may apply to delivery of other items, including freight, provision of services by dispatching service personnel, or any other type of application involving delivery or dispatching. Thus, as used herein, the term “package” is not limited to a parcel, but means any type of good or service being delivered or dispatched by a carrier or service provider.
At a high level, the customization or the personalization of the delivery experience may require or involve the coordination between the:
(1) carrier and the consignee,
(2) consignor and the carrier, and
(3) consignor and the consignee.
It can be readily appreciated why coordination between each of these entities may be required. In the first scenario, the consignee may not be present to accept delivery. Communication between the carrier and the consignee may facilitate delivery by the entities agreeing on a time and/or place to accomplish delivery. In the second scenario, the consignor may request the carrier to alter the delivery address for the package. And, in the third scenario, the consignor and the consignee may agree between themselves to modify aspects affecting delivery of the package and inform the carrier of the change (which then may involve the first or second scenarios). Thus, in many instances, communication in one of the aforementioned scenarios (e.g., between the consignor and the consignee) may be followed by another instance of coordination (e.g., involving the consignor and the carrier). For example, a consignee may notify the consignor of a change of address after the consignor has already shipped the package, but before delivery has been accomplished. The consignor may then communicate the new address to the carrier.
As it will be seen, the first two instances of coordination involve the carrier in some form and impact how or when the carrier accomplishes delivery of the package. In many cases, the impacts to the carrier are highly dependent on the particular facts surrounding the package delivery. For example, a consignor contracting for the delivery of a package may require a signature by the consignee, and only the consignee. This may preclude a request by the consignee to deliver the package to a neighbor instead. Of course, if the consignee communicates with the consignor, the consignor may in turn authorize the carrier to deliver the package without a signature of the recipient, effectively waiving the signature requirement. Because various communications and combinations of coordination are possible, only some examples are provided to illustrate various embodiments of the invention.
Communication Between the Carrier and the Consignee
At a high level, the communication between the carrier and the consignee typically involves the exchange of information to coordinate, or personalize, the package's delivery. Typically, although not required, the consignee is aware of an impending package delivery. This may occur via several ways. In one common embodiment, the carrier may notify the consignee of an impending delivery. This can occur via an email notification, although other forms are possible, including other forms of electronic messaging (e.g., short message service, automated voice telephone calls, facsimile messages, hosted web site messaging, instant messaging, etc.). In other embodiments, the consignor may notify the consignee that a package has been shipped. This is quite common in situations in which the consignor is a merchant from whom the consignee has ordered an item and the consignor provides notification when the package has actually been handed off to the carrier. Typically, the consignor will also provide the consignee with a tracking number of the delivery. In other embodiments, the consignee may be expecting a package based on other facts (e.g., the consignee ordered merchandise and was expecting delivery). In this case, the consignee may proactively access a package tracking web site operated by the carrier to ascertain the status of the package delivery.
Typically, once the consignee is aware of an impending delivery, the consignee can initiate a request for personalizing the delivery of the package. The consignee may communicate the request in different ways, including electronic messaging, such as via email or web-site access, via telephone, or other forms. The request typically provides information to the carrier that the delivery personnel use in the delivery of the package. Such information may include identification of the package (e.g., via a tracking number), requests regarding when the package should be delivered on the day of delivery, where it should be placed at the delivery address, or other special handling information.
Although personalized delivery information is often provided after the consignee is aware of the existence of a package that will be delivered, this information can be also provided earlier. Specifically, a consignee could indicate delivery preferences or instructions prior to a package being shipped to the consignee. For example, personalized delivery information can be provided by the consignee as standing instructions or preferences for delivery of a package. Thus, the delivery preference is to be applied to all future deliveries, even if there is currently no package scheduled for delivery to the consignee. In other embodiments, the delivery information may be provided after the initial delivery attempt. While the carrier may prefer to receive such information prior to an initial delivery attempt, embodiments of the present invention contemplate indication of delivery preferences by a consignee before and/or after an initial delivery attempt.
Communication Between the Consignor and the Carrier
Similarly, a consignor can provide personalized delivery information to the carrier. In some embodiments, the indication of such information may be made by the consignor contemporaneously with the indication of other related package delivery information. A typical circumstance is a customer ordering information from a merchant using web-access, and when placing the order the customer (which typically is the consignee) requests that the items be placed at a certain location upon delivery (e.g., the back door). Upon shipping the package, the merchant may indicate to the carrier the destination address with special instructions regarding the delivery, including placement at the back door. This information could be included with other shipping information provided by the consignor to the carrier via a shipping system. Such shipping systems allow a consignor to prepare packages for shipping.
In another embodiment, the customer may notify the merchant of the special delivery instructions, after the package has been shipped. In that case, the consignor (the merchant) may communicate the special delivery instructions to the carrier by referencing the package or the consignee. Alternatively, and as discussed above, the consignee could indicate such directly to the carrier after learning of the impending delivery.
In other embodiments, the consignor-provided personalized delivery information could originate from the consignor itself, rather than from the consignee. For example, the consignee may know that it is shipping goods which could be damaged if wet, and thus provide delivery instructions indicating that if the package is left at the consignee's delivery address without the consignee being present, the package is to be wrapped or covered in plastic. As another example, the consignor may require that all consignees provide “live” or in-person signatures for release of a package, and would provide this information as a standing delivery preference to the carrier.
Communication Between the Consignor and the Consignee
The communication between the consignor and the consignee, by itself, does not involve the carrier and does not directly impact the delivery of the package. However, a typical result of this communication is that the consignor or consignee will then communicate personalized delivery information to the carrier regarding the package delivery. It is possible that one party may expect the other to contact the carrier, or may facilitate the communication so as to ensure the communication is as seamless as possible. For example, a consignor may communicate with a consignee and learn that the consignee will not be able to receive the package. The consignor may provide the consignee with a web-address of the carrier and the tracking number of the package as well as instructions of how to inform the carrier of this situation. Thus, the consignor facilitates the consignee in indicating his personalized delivery information to the carrier. Alternatively, the consignor could inform the carrier of the situation directly, after which the carrier can contact the consignee and inform him that his delivery preferences have been communicated. The consignor may have obtained the email address of the consignee (such as at the time the consignee placed the order with the consignor), and may provide this to the carrier for purposes of allowing the carrier to communicate shipping status information to the consignee.
Delivery Authorization Forms (DAFs)
The ability for the consignor or consignee to request personalized package delivery creates a greater likelihood that the package will be delivered successfully and in accordance with the consignee's preferences on the initial delivery attempt. By most standards, delivery of a package on the initial attempt is preferable as it results in the package being delivered sooner to the consignee, and it conserves the carrier's resources. As discussed, delivery on the initial attempt does not always occur for various reasons. For example, a consignee may not be available to receive the package, and will only know of the attempted delivery after the failed delivery attempt. In these situations, many service providers, such as UPS, will leave an indication, such as a paper note, in a conspicuous manner at the delivery location indicating that a delivery attempt has been made. One such paper based form is the InfoNotice® used by UPS to indicate a delivery attempt. The consignee, upon arriving at the delivery location typically sees the delivery indication and then is aware of the failed delivery attempt.
One embodiment of the present invention discloses providing the consignee with a notification of the impending delivery prior to the first delivery attempt and provides, or enables the consignee to access, an electronic delivery authorization form (DAF). Generally, the DAF is a form that can be provided electronically to the consignee (e.g., via email) from the consignor or the carrier, or can be accessed electronically by the consignee, such as via the carrier's website. One purpose of the DAF is to provide authorization of the carrier to leave the package without the consignee being present to receive the package. The consignee can then print the form, sign it, and post it at the delivery location in advance of the first delivery attempt. This allows the consignee to receive the package on the first delivery attempt without having to be present.
Another purpose of the DAF is to indicate delivery preferences and/or delivery instructions for delivery of the package. The DAF may include various fields relating to delivery of the package, and allows the consignee to indicate specific delivery preferences on the form (such as indicating that the package should be left at the back door). The DAF can be generated by the carrier or consignor so as to have some of these fields completed prior to the DAF being provided to the consignee. In other embodiments, the consignee can fill in the fields on his own.
After printing a hard copy and posting it in a conspicuous place at the delivery location, the delivery personnel retrieves the DAF upon delivery the package and associates the DAF with the package or delivery. Typically, the DAF includes machine readable indicia that allow delivery personnel to associate the DAF with the shipment of the package via a portable computing device carried by the delivery personnel at the time of delivery. In some embodiments, a DAF with an assigned identifier number may have already been logically associated with the delivery at the time that the DAF was provided to the consignee. Specifically, the carrier may have associated the DAF with the consignee's package at the time the carrier sent the DAF to the consignee. Various other embodiments of the DAF are discussed below.
Structure of an Exemplary Consignee Services System
The CSS 104 can send and receive email using an email interface 112 and may host a web site, which is accessible via a web interface 114. Alternatively, a separate computer (not shown) may host the web site and communicate with the computing system 122. The CSS 104 can also comprise a telephonic interface 115 providing interactive voice response (IVR) capabilities to callers. The telephonic interface 116 can allow connection to a customer service representative 120 that uses a computer 118 that is able to communicate with the computing system 122. The CSS 104 is also able to communicate with a consignee's computer 100 via the Internet, as well as a with a consignee 108 using the telephone network 110 via the IVR, using well known methods of prompting the user for information that is entered using keypad depressions (e.g., touch tones). Thus, it is possible for a user to receive a notification via a telephone call providing an audio message, and indicating a delivery preference by responding via touch-tone entry. In some instances, the use of an IVR may not be as friendly or flexible as a web-based interface, but it may provide greater availability to those consignees not having ready Internet access via a computer. The system can also communicate with the consignee via other methods known in the art. It is also possible for the CSS 104 to communicate with the consignee or consignor using an application program interface (API) 150, which typically would occur via the Internet 102, WAN, etc.
In various embodiments, the CSS 104 communicates using a local area network (LAN) 106, or other network, to other systems 130 operated by the carrier. In one embodiment, one of these other systems 130 is a package level detail (PLD) database 133. The PLD database 133 may maintain information about a package being delivered, including its status, as well as other package related information. One embodiment of a PLD database 133 is QuantumView®, which is a system operated by UPS that stores and provides consignees' individual package level information. In other embodiments, the PLD database may be separate or distinct from the QuantumView® system.
As indicated, the consignee typically communicates with or accesses the CSS 104 using a computer 100 connected to the Internet 102, as is well known. Although not shown, other ways of accessing the CSS 104 are possible, such as by using wireless access devices. As is known, cell phones, PDAs, and mobile computers can be used to send and receive email messages and access the Internet. Although these are not shown, these forms of consignee access are possible as well.
The consignor's system 152 may employ several individual computing systems, such as a main consignor computer 140 that interacts with an email interface or system 142 for sending and receiving email messages. In many e-commerce applications, the consignor may send an email message to the consignee when the consignee's order has been shipped, the email message providing a tracking number as well. The consignor computer 140 may interface or otherwise communicate with a shipping system 144. These systems are also well known in the art, and aid in preparing a package for shipment. The shipping system 144 may collect the information associated with the package and package delivery, including the consignee's address, and communicate the information to the carrier's system 104, which the carrier then stores in the PLD database 130. Finally, the consignor system 152 can include a web interface 146 which can be used by the consignee to check on the status of the order, via a consignor's web site for example. The consignor computer 140 can also interact with the carrier's system 104 via an API 147 or may simply direct the consignee to a link on the carrier's website. Similarly, the CSS 104 may communicate with a consignor 140 via the consignor's web interface 146, via an API 150 in the carrier's system, or via an API in the consignor's system 147. In other embodiments, the CSS 104 may communicate with a separate carrier-operated shipping system (not shown), which in turn, communicates with the consignor's shipping system 144. Although not shown, the consignor system 152 may also include a telephonic interface for allowing a consignee to communicate with the consignor, and vice versa, via telephone.
Specific Consignee Capabilities
In various embodiments of the invention, a consignee can indicate and personalize delivery preferences for the delivery of a shipment. As used throughout, a “package” may be a container, parcel, or other such item. Delivery of a “package” thus encompasses a shipment of one or more of such items. Therefore, in many instances, a shipment of more than one package is described and there may be delivery preferences associated with different packages within the shipment. Various options and combinations of delivery preferences and instructions are encompassed by the scope of embodiments of the present invention, and the following provides a high level overview of potential embodiments, but is not intended to be exhaustive.
Consignee Registration
In accordance with one embodiment of the present invention, a user can register with the consignee services system 104 for purposes of indicating standing delivery preferences and instructions. This collection of consignee information is called a consignee profile. The user does not necessarily have to be a pending consignee (i.e., there is no package currently being processed by the carrier for delivery to that user). Nevertheless, the user is viewed as a potential consignee, and therefore considered as a consignee within the scope of this and other embodiments. The consignee's delivery preferences would then be processed and applied to all subsequent packages in delivery to the consignee. These preferences and instructions would be considered as default indications. A registered consignee can also indicate a particular delivery preference for a particular package, which can override a standing or default preference. Persons who have not registered cannot provide a standing preference indication, but can still provide a per-package preference. Therefore, non-registered users can be viewed (in some regards) as having a subset of the capabilities offered to a registered user.
A consignee can register and request notification of all impending deliveries. In some embodiments, the carrier may store standing consignee preference information in the consignee profile database 134 and per-package preference information in the package level detail database 133. Other embodiments may combine and store both types of information in the consignee profile database 134. A flag indication may be incorporated in the PLD database 133 indicating that consignee delivery preferences may apply to delivery of a particular package to the consignee. Other variations are possible and are within the scope of the invention.
Registration, while not a standalone delivery preference by itself, is a capability allowing a consignee to request specific consignee services and set certain preferences. Once registered, a user can review, update, or otherwise control their preferences. Thus, registration and indication of delivery preferences may occur together. Once registered, the user may indicate a preference without having to re-register. Consignee registration may be required for processing any of the subsequent consignee services that a consignee may select. For example, some carriers may not offer a per-package delivery preference indication service without registration.
Registration may occur by the consignee accessing the CSS 104 by using a consignee computer 100 (e.g., a home computer, work computer, etc.) to access a web site hosted by the CSS 104, as shown in
The system may limit certain services to only certain consignees (e.g., those with a past minimum level of package deliveries). The services may be offered at no fee, a flat fee, or a per service (e.g., per-delivery) fee. Tiered service levels may also be provided to a consignee. Billing plans can also vary based on the shipping volume a consignee receives within a particular time frame. Thus, certain high-volume users may not be charged. Billing can occur on a per-occurrence basis (e.g., charged to a credit card) or via periodic billing (e.g., charged to a pre-established account or mailing a separate invoice).
Delivery Notification
Upon or after registering for consignee services, the consignee may elect to receive notification (shown as “Delivery Alert” in
Telephonic Delivery Notification may also occur, for example, using automated equipment to dial a consignee indicated telephone number, and playing a prerecorded announcement which specifies delivery information. The consignee can select to receive a phone reminder 1106 within twenty-four hours of delivery. In the embodiment shown in
As shown in
Typically, a notification is provided for each package, although other embodiments may provide a notification for each delivery (which can comprise a plurality of packages). The notification may include other information, such as the class of service, consignor, weight, value, or any other information retained in the PLD database for the shipment. Typically, notification requires a user to register for the delivery notification service, although in other embodiments, the notification is provided on a ‘one-time’ basis, in which the consignor provides the consignee address information and requests that a notification be provided to the consignee. The provision by the carrier of delivery notification is independent of notification provided by the consignor. The carrier may also provide a delivery notification service independent from other services requiring registration of a user for purposes of indicating delivery preferences.
When entering his delivery preferences, a consignee can also select Package Release 1112, which authorizes the carrier to deliver the package on the first delivery attempt without obtaining a signature. This service is described further below, under “Package Release”.
Delivery Instructions
Upon or after registering, the consignee can select or indicate various delivery instructions associated with all future package deliveries, or for a specific delivery after receiving a notification of that delivery. These instructions may be set by the consignee as default instructions for all future package deliveries, specific instructions for a given condition (e.g., timeframe, specific delivery, etc.), or a one-time indication (e.g., per delivery or per package). In the last case, the consignee may be required to provide a tracking number or other shipment identifier. In order for the consignee to personalize the delivery preferences to his specific delivery location, the consignee may be required to input a “type of address” 1114, such as whether the consignee lives in a house, or in an apartment (or similar dwelling), as shown in
The delivery instructions can include, for example, the specific location at the delivery address where a package may be left if the consignee is not present to receive the delivery in person. Referring to
Similarly (and with reference to
The delivery instructions indicated by a consignee (such as shown in
After the consignee has provided delivery preferences and delivery instructions as described above, the CSS 104 will confirm the consignee's contact information and indicated preferences and instructions, as shown in
As described above, a consignee may initially indicate delivery instructions and/or preferences upon registration, so that the CSS 104 would apply these instructions and preferences to all future deliveries. As discussed below, the consignee can also modify or update these preferences at any time, or can modify them on an individual basis for individual package deliveries.
Package Release
Upon or after registering, the consignee can also select the Package Release service 1112 (see
Delivery Change Request
The Delivery Change Request (DCR) service (see
The consignee can then select from several DCR types, including: redirect package, refuse delivery, reschedule delivery, or will call. A “redirect package” request 1404 instructs the carrier to deliver the package to an alternate local address and/or recipient specified by the consignee when the consignee makes the request. A “return to shipper” request 1406 instructs the carrier to return the package to the consignor or shipper, and may require a consignee to indicate the consignee's reasons for return. A “reschedule delivery” request 1408 instructs the carrier to deliver the package to the original delivery location (e.g., the consignee's home) on a date and/or time specified by the consignee in the consignee request. A “will call” request 1410 instructs the carrier to hold the package for consignee pickup at a location and for a period of time specified by the consignee in the consignee request. Those skilled in the art will readily understand that other instruction options exist that do not depart from the spirit and scope of the present invention. Many of the capabilities and associated information requirements for each of these capabilities are disclosed in the accompanying figures illustrating how a consignee may indicate the DCR information via a carrier's web site.
In the embodiment shown in
As shown in
The consignee may also be required to provide a telephone number 1508 for the recipient at the redirected address. The “redirect package” service also enables the consignee to provide special handling instructions 1514 that may be associated with the redirect address. For example, the consignee may specify that the package is to be left with the receptionist at the redirect delivery location and input the receptionist's or office's main telephone number. As shown in
If the consignee selects “Return to Shipper” 1406 (
If the consignee selects “Reschedule Delivery” 1408 (
Finally, if the consignee selects to “Will Call” 1410 the package, the consignee will be directed to a web page (
Although the Delivery Change Requests discussed above were described with regard to the consignee accessing various web pages to provide information, other embodiments of the present invention enable a consignee to provide Delivery Change Request information via telephone. For example, a consignee making a “Redirect Package” request can call the carrier via the Telephonic Interface (including IVR) 115 and provide the required information using IVR (Interactive Voice Response), or by communicating the information to a customer service representative 120 who can input the information into a computer 118 in communication with the CSS 104. In general, any input provided by a consignee (whether for a Delivery Change Request or other request) could also be provided by the consignor, or an agent designated by the consignee.
Delivery Change Requests can also be made by the consignor rather than, or in addition to, the consignee. A consignor-requested DCR may be made proactively by the consignor or in response to a request by the consignee to do so. In the former instance, the consignor may have placed the wrong item in the package and indicate a DCR similar to the “return to shipment” DCR described above. In this instance, this DCR may be a “recall package” DCR, because it is made by the consignor. In the latter instance, the consignee may realize that he will be at a different address at the time that the package is to be delivered. Rather than contact the carrier with this information, the consignee may contact the consignor and indicate the address to which the package is to be redirected. The consignor can then make a Delivery Change Request on behalf of the consignee and provide all of the necessary information for redirecting the package.
Modification and Updates to Consignee Profile
As discussed above, a registered user of the CSS 104 can update and modify his user profile, including notification preferences, delivery instructions, and delivery change requests, at any time after registration (see generally
Similarly, the web page illustrated in
Carrier Package Processing for Consignee Indicated Personalized Delivery Service
The process begins at step 200 with a package being processed by the carrier's package handling system. The package is typically assigned a package identifier and encoded with a machine readable form of the identifier representing a tracking number. Such identifiers are well known in the art and used to track a package through the various stages of handling. Typically, a package is scanned (e.g., ‘read’) several times during its handling by the carrier. Typically this occurs when the package is first handled by the carrier, and thereafter at various points when it is loaded and unloaded from a delivery vehicle or processed in a package routing center.
At step 202, it is presumed that at some point equipment scans the package for determining how to process the package. During this process, the PLD database 133 may be accessed to read/write package level data so as to determine where to route the package. When the package data is read, a determination is made at step 204 whether the consignee has elected to be notified of impending deliveries to the consignee's name or address. As discussed, this service provides a notification to the consignee of the pending delivery of the package, typically in the form of an email or telephonic notification message. If the consignee has elected this service, then the next step 206 is to notify the consignee of the package.
It is common for the email message to provide a link to the carrier's web site. The consignee may click on the link to provide preferences or instructions regarding the delivery of the package. As described above, a registered consignee may update preferences or instructions already registered with the CSS 104. In other embodiments, an unregistered user can input or indicate delivery preferences for this particular delivery. In either case, assuming that the consignee has done this, the carrier's computing systems at step 208 accept the consignee's delivery preferences and/or instructions. The carrier then stores this information as a consignee profile, or consignee profile record, in the CSS 104 (such as in the consignee profile database 134) in step 210. In other embodiments, the carrier could alternatively store the consignee's preferences in the PLD database 133 as a record for that particular shipment.
The package is presumed to be continued to be routed, until it is loaded on the final delivery vehicle for delivery. Around this time, the CSS 104 ascertains whether there are any delivery preferences indicated. The determination of personalized delivery preferences or instructions may occur either prior to the package being placed on the delivery vehicle (e.g., while the package is being routed by the carrier's sorting and handling systems) or after it is placed on the delivery vehicle, or at both times (such as might occur if the consignee also modifies the personalized delivery instructions on the day of delivery). As illustrated in
The CSS 104 may determine this by querying the consignee profile database 134, or by the accessing the PLD database 133. As noted herein, the indication of personalized delivery preferences and instructions can be stored either in the PLD database 133 or in the consignee profile database 134, often depending on the type of information to be stored. In the case of the personalized delivery instructions being stored in the PLD database 133, the CSS 104 can set a flag with that date indicating exception treatment, so that the information is properly conveyed to delivery personnel associated with delivery of the package.
Once the determination has been made that a personalized delivery is to be provided to the consignee in step 214, the CSS 104 determines the specific preferences and/or instructions indicated by accessing the consignee profile record (at step 212) in consignee profile database (or the PLD database, if appropriate). The delivery preferences and instructions are then communicated by the CSS 104 at step 216 to the appropriate parcel processing system, which typically involves communicating the delivery preferences/instructions to the delivery via a portable computing device (described below). The portable computing device then notifies the delivery personnel of the preference/instruction, typically via a text or graphic message displayed at the appropriate time. If the CSS 104 determines at step 214 that no personalized delivery preferences/instructions have been indicated by the consignee, then the carrier delivers the package to the consignee under standard delivery procedures at step 218.
Exemplary systems for processing a package in this manner are shown in
The package 302 is typically scanned or otherwise identified in the normal handling of a package while in the carrier's sorting facility by the PHS 300. The scanning equipment, upon identification of the package, may check the consignee's address against consignee addresses stored in the consignee profile database. This may be accomplished by conveying the address via path 306 to the carrier's CSS 104.
Alternatively, the PHS 300 in communication with the CSS 104 may determine that an exception exists for the package. For instance, using the consignee address, the CSS 104 may communicate with the consignee profile database, determine that the consignee has indicated certain delivery preferences or instructions, and can communicate this information, or ‘exception’, back to the PHS 300. As an example, the ‘exception’ may be a delivery instruction by the consignee indicating that the package is to be redirected to a different delivery address.
In such cases, the PHS 300 may receive information via communication link 306 from the CSS 104 that exception handling is required for a specific consignee or package delivery. This information could be transmitted periodically on a batch basis for all relevant packages, or individually for each package as required. Alternatively, the PHS 300, upon notifying the CSS 104 of an address match, may receive an indication from the CSS that special handling is required. In any case, the PHS 300 diverts the package via path 316 to an Exception Handling Center (EHC) 312. There, either further processing systems and/or personnel determine via information received via communication path 308 from the CSS 104 what the ‘exception’ for the particular consignee or package may be (for example, that the package should be redirected to another address). This may entail printing and attaching a new shipping label on the package, and forwarding the package via path 318 back into the normal processing flow 304 of packages. In some embodiments, the EHC 312 may be directly notified by the CSS 104 that personalized delivery for a package is required. In such cases, the EHC 312 may determine that the package is already loaded onto a package delivery vehicle and the personalized delivery instructions are communicated using a communication infrastructure 314 (for example the systems illustrated in
Finally, the CSS 104 may also convey the personalized delivery preferences or instructions via link 310 directly to the communication infrastructure 314 that communicates the information the portable computing device used by delivery personnel. These systems help to ensure that the portable computing device associated with handling the package is notified, at the appropriate time during delivery.
Advance Delivery Authorization
Service Overview
The Advance Delivery Authorization (ADA) service is similar to the “Package Release” service described above. However, the ADA service involves the use of the electronic delivery authorization form (DAF) for indicating package release. This is another embodiment of the invention that provides a personalized delivery experience for the consignee. In various embodiments, the DAF is provided in electronic format (such as a PDF file attachment to an email), which can be printed out and posted at the delivery location for retrieval by the delivery personnel responsible for delivering the package. Typically, this applies in situations in which the consignee or his representative is not present to accept a package for delivery, but wants to provide an indication that the package may be left at the premises anyway. Currently, an initial delivery attempt is made, and a paper form is left at the delivery address indicating the unsuccessful delivery attempt; the paper slip can later be signed by the consignee and left at the delivery address for a subsequent delivery attempt instructing the delivery personnel to leave the package. ADA provides the ability to avoid the initial unsuccessful delivery attempt; in other words, ADA provides the consignee with the ability to authorize delivery of a package in advance of a first delivery attempt.
ADA accomplishes this by providing the consignee with advance knowledge of the delivery, and providing the consignee with a delivery authorization form (DAF) which is left at the premises (e.g., on the front door) in advance of the initial delivery. The delivery personnel may or may not be aware of the pre-existence of the DAF, but upon encountering the DAF will deliver the package accordingly. Of course, there are some service options which may preclude the use of a DAF (e.g., where the consignor requires a “live”, or in-person, signature, or if the package is COD and requires payment, etc.). It is presumed, for the sake of illustration, that there is no restriction precluding the use of a DAF.
Meanwhile, the CSS notifies a DIAD Updating System 402 that communicates to a portable computing device 400 associated with the delivery personnel. Individual components of the DIAD Updating System 402 will be discussed in greater detail with reference to
Upon receiving the notification message of the impending package delivery, the consignee may know that he may not be present to accept the delivery. Consequently, the consignee fills out and signs the DAF 416 and places the DAF 416 in a conspicuous location, such as the front door of the delivery address 420. Upon arriving at the delivery address, the delivery personnel 404 observes and retrieves the DAF 416, and knows to leave the package according to the instructions or preferences indicated on the DAF 416. The DAF may have a unique identification number, which the portable computing device 400 may record and/or verify, and which allows the DAF to be associated with the shipment. In summary, the DAF transforms an otherwise unsuccessful delivery attempt into a successful delivery.
This is but one variation of the service, as a more complete description of the various embodiments is provided below.
Delivery Authorization Form Generation and Communication to the Consignee
The delivery authorization form (DAF) may be provided to the consignee by various entities, including the carrier, the consignor, or another party. The DAF is typically provided to the consignee using electronic communication, including email, the Internet, or any other communication method known in the art. The consignee may receive the DAF directly (e.g., as an email attachment), or may receive information prompting the consignee to request the DAF (e.g., by accessing a web site and requesting the DAF). The consignee may receive this information via telephone or wireless communication, and then use the consignee's computer to access the Internet to retrieve the form. The consignee may access the Internet via dial-up, digital subscriber line (DSL), cable Internet, wireless, or any other means of accessing the Internet known in the art.
The DAF typically includes fields associated with package delivery, for the input of information such as the date (e.g., the date that the DAF is signed by the consignee), name and/or address of the consignor, tracking number of the shipment, name of the consignee, address and telephone number of the consignee, desired package delivery location (such as the consignee's front or back door, garage, a neighbor's address etc.), consignee's printed name, and consignee's signature. The DAF may also include instructions to a consignee for filling out and executing the DAF, as well as liability limitations associated with using the DAF. The DAF may also provide instructions to the delivery personnel to follow upon retrieval of the DAF. An individual DAF may have an associated serial number. This serial number may be initially only associated with the DAF, and is used by the carrier to associate the executed DAF with the shipment. This latter association typically occurs at the time of the delivery attempt. Typically, the delivery personnel retrieve the DAF upon the delivery attempt and records or reads the serial number in association with the delivery, as described further below.
The “Package Location” section 610 may provide personalized delivery preference information, including pre-printed options as to where the package should be left. For instance, the “Package Location” section 610 may provide “check-off” boxes for indicating to delivery personnel whether to leave the package at the front door, back door, patio, or office, among other options. The “Package Location” section 610, as shown, also includes the option of requesting that the package be left with a neighbor, and provides space for a consignee to indicate the address or other description of the neighbor's location. In one embodiment, not shown, the DAF could include instructions to a consignee indicating that delivery personnel cannot deliver to an address other than the delivery address. This may be because delivery personnel follow a pre-planned route for deliveries, and receiving an alternate address request on a DAF may not be compatible with the pre-planned route.
A field may be provided for hand-written information, such as additional delivery instructions or preferences, and a signature line is provided for authorizing release of the package. In other embodiments, the consignee could complete the form by using an electronic editing tool on a computer prior to printing out the form. For example, in one embodiment, a consignee may be able to “sign” the form using a computer mouse to generally follow the shape of the consignee's signature. The process of providing an Electronic Signature is described further below.
A “Service Provider Instructions” section 612 may be included which provides various instructions to delivery personnel regarding how to handle the DAF. Finally, a “Legalities” section 614 may provide the carrier's disclaimers or other legal notices.
Other embodiments of the DAF may be of different size, shapes, and configurations than the DAF 600 shown in
Communicating the DAF to the Consignee
Returning to
The CSS 104 can communicate with the consignee's computer 100 and provide a DAF via email (e.g., as a *.pdf attachment) using the email interface 112. Alternatively, the CSS can provide a hyperlink in an email message for the consignee to access the carrier's web site, or the consignee can proactively access the web site in order to retrieve the DAF. For consignees that do not have, or choose not to use, a computer, the DAF may be provided in facsimile form via the telephone network 110 or other communication method.
The consignee typically communicates via the consignee's computer 100 with the consignor's web interface 146. A typical scenario begins with the consignee executing an on-line purchase of a product. The consignor receives the order information (such as the product identifier, customer identification and shipping information, and other information particular to the order). The consignor conveys the appropriate information to its shipping system 144, which in turn, conveys certain information to the carrier. The Internet is often used to convey the information to the carrier, typically via the API 150, but other interfaces can be used.
The carrier will then use the shipping information to establish a record for the package or shipment in the PLD database, which is assigned a tracking number. The carrier then provides the tracking number to the consignor. Thereafter, packages are provided by the consignor to the carrier bearing the tracking number, allowing the carrier to readily associate the package with the PLD information. This may be accomplished using well known scanning systems, based on bar codes, radio-frequency identification (RFID) tags or devices, etc.
The carrier may communicate an estimated delivery date to the consignor based on the class of service. This may be communicated to the consignor via the web interface 114, sending an email message via the email interface 112, or via the API 150.
The consignor may then further communicate certain information, such as the estimated delivery date and tracking number to the consignee. This typically occurs via an email message via the consignor's email interface 142. Alternatively, the carrier may communicate this information directly to the consignee in an email via the carrier's email interface 112. In other embodiments, the aforementioned emails may convey a hyperlink allowing the consignee to link to an appropriate web site to learn of the estimated delivery date.
Possible Service Flows and Operation Configurations
Numerous possibilities exist for communication between the consignor, the carrier and the consignee.
The embodiments illustrated in
A package received by the carrier typically bears a label with the tracking number printed in a machine readable form. Such identifiers are well known in the art and used to track a package through the various stages of handling. Other forms of package identification, such as RFID tags could be used. Typically, a package is scanned (e.g., ‘read’) several times during its handling by the carrier. At step 504, the consignor provides the package to the carrier, and the carrier's package handling equipment scans the package for determining how to process the package. During this process, the PLD database 133 of the carrier may be accessed to read or write package level data.
The Advance Delivery Authorization service is predicated on the consignee knowing, in advance, of the impending delivery. The consignee may be notified of the impending delivery by the consignor at step 506 sending a shipment notification message to the consignee. Typically, when the consignee places an order, the consignee provides an email address so that the consignee can receive such notifications via email. Alternatively, the carrier at step 510 may send a shipment notification message to the consignee. The carrier may know the consignee's email address via a prior registration, as discussed elsewhere herein, or may obtain this information from the carrier or the package level data. Typically, the message is sent to the consignee by the carrier after the carrier has determined an estimated delivery date. In either aspect (i.e., at step 506 or step 510), the message to the consignee may include, among other information, the order number provided by the consignor, the tracking number provided by the carrier, and the estimated delivery date. In other embodiments, the email sent to the consignee may provide a hyperlink to the consignor's or carrier's web site.
At step 508, the consignee may link to the consignor's web site from either the email provided by the consignor or from the email provided by the carrier and proceed to step 560, as discussed in detail below. Alternatively, at step 512, the consignee may link from either email to the carrier's web site and proceed to step 520, as discussed in detail below. In an alternative aspect, the consignee may proactively access the web site of the consignor and proceed with step 560, or may proactively access the carrier's web site and proceed with step 520. As previously mentioned, various authentication information may be required by the carrier prior to accepting and processing any information affecting the delivery of the package to the consignee.
In one aspect (not shown), the email may also include a delivery authorization form for the consignee to fill out and sign, as discussed above. This form may be provided through an attachment to the email or directly in the body of the email in electronic image format, such as *.pdf, *.gif, or other web-transportable image format. The consignee may then print out the DAF using the consignee's printer. The consignee may then fill out any necessary information, such as the date, the tracking number, the consignee's name, address and phone number, the name of the consignor, and the desired delivery location, among other information. The consignee then signs the form. Alternatively, the consignee can fill out this information using the consignee's computer. The consignee then prints out the completed form and signs it. The consignee can then affix the signed DAF to a delivery location or site, such as the consignee's front door. The delivery would occur under ordinary procedures, and the delivery personnel would retrieve the signed DAF upon delivery of the package and deliver the package according to the indications made by the consignee on the DAF.
In another aspect of this invention, the consignor may have registered with the consignee services system 104, as described above, and chosen to receive notification of inbound packages and indicated delivery preferences. When the consignor provides the relevant shipping information to the carrier at step 504, this information may be updated to the carrier's PLD database. The PLD database 133 may then communicate with the Consignee Profile Database 134 to determine if the consignee has registered with the CSS 104. Assuming the consignee has chosen to receive notification messages for shipments bound to the consignee's name or address, the CSS 104 triggers a notification message to be sent to the consignee. This automated notification typically includes a tracking number, service, reference number, or scheduled delivery date. The notification message may also include a delivery authorization form provided as an attachment to an email in an electronic image format, such as *.pdf, *.gif, or other web-transportable image, or provided via a hyperlink to the carrier's web site. The DAF may already indicate certain shipment-specific information, such as the name of the consignor, the consignee's name, address and telephone number, the tracking number, and an associated DAF serial number. The consignee prints the DAF directly from the email and signs it, without having to fill out manually any information other than the date, and places the DAF at the anticipated delivery location for the delivery person to retrieve.
Advanced Signature Authorization Via Carrier's Web Site
At step 512, the consignee accesses the carrier's web site, either through a hyperlink provided in an email from the consignor or the carrier, or proactively. The carrier's web site may present to the consignee a summary of the shipment, including its status, estimated delivery date, tracking number, consignor, etc. At step 520 the consignee confirms the status of the shipment. At step 522, the consignee may determine that he will be unable to receive the delivery on the estimated delivery date and therefore requests a DAF from the carrier. At step 522 the carrier's CSS 104 will generate a DAF. The step of generating the DAF may include completing various fields of the DAF. For instance, because the CSS 104 is in communication with the PLD database 133, it can retrieve the package level data (e.g., the consignor's information, the package tracking number, the consignor's name and address), and can populate the fields (described above with reference to
A completed or semi-completed DAF may include the tracking number associated with the shipment, and a serial number associated with the DAF. If the consignee has registered certain delivery preferences with the CSS 104, the DAF may also reflect these preferences, including specialized delivery instructions such as where the delivery personnel should leave a package when the consignee is not home. The personalized delivery preferences determined by the carrier may be based on the preferences retained in the consignee profile database 134. Alternatively, the consignee can fill out the DAF to instruct or indicate to the delivery personnel to leave packages at the front door, back door, side door, patio, deck, porch, garage, carport, neighbor's home, or other special delivery instructions.
Thus, the DAF generated at step 524 may be personalized to the particular consignee and particular shipment. The CSS will then send the DAF to the consignee at step 526, typically via email. Alternatively, the web site may provide the consignee with an electronic image of a delivery authorization form, such as *.pdf, *.gif, or other web transportable image. The consignee may then retrieve the electronic image of the DAF. Upon receiving the DAF, the consignee may proceed with step 580 in printing out the DAF using the consignee's printer. If the CSS 104 generated much of or all of the necessary information for the DAF at step 524, the consignee needs only to print out the DAF, fill in any missing information, such as the date, and sign the DAF. Alternatively, if less than all necessary information was generated and included in the DAF at step 524, the consignee may then fill out any missing and/or necessary information, such as the tracking number, the consignee's name, address and phone number, and the name of the consignor, among other information. The consignee may then sign the form. Alternatively, the consignee may fill out this information using the consignee's computer 100 prior to printing. The consignee may then print out the completed form and sign it.
The consignee can then affix the signed DAF to a specific location or site at the delivery address, such as the consignee's front door (step 582). At step 584, the delivery would occur under normal procedures, and the delivery personnel would retrieve the signed DAF upon delivery of the package, and would know to deliver the package according to the instructions indicated on the DAF. Different procedures for delivery personnel to take upon and after delivery of the package are discussed in more detail below.
Returning to step 520, the consignee may alternatively request providing an online signature (step 530) to authorize delivery of the package. If the consignee requests to provide an online signature, the carrier website may require that the consignee agree to certain legal limitations or liabilities associated with providing an online signature. For example, the carrier website may provide “Terms and Conditions” which the consignee may have to agree with by clicking on a box indicating “I agree” with the Terms and Conditions. Both the carrier and consignor may require this legal authorization from the consignee. In one embodiment (not shown), the carrier (or consignor) may require that the consignee have a signature on file with the carrier in order to provide an online signature. For example, the consignee may have to provide a paper (i.e., hand-written) signature to the carrier prior to requesting the online signature option. The carrier may also provide the consignee with language regarding the legalities or liabilities of providing a paper signature to authorize future online signatures.
At step 532, the carrier's CSS 104 would then confirm whether or not an online signature would be accepted to authorize delivery of this package. This can include the CSS 104 communicating with the consignor system 152 to determine if an online signature is acceptable. Alternatively, this information may be part of the package level data, and the CSS 104 can communicate with the PLD database 133 to determine if the online signature is acceptable. If not accepted, at step 534 the system notifies the consignee of the denial of the online signature request and provides the consignee with the option of using a DAF to authorize delivery of the shipment. The system may provide this option in many different ways, such as automatically sending an email to the consignee including a DAF, or automatically providing the consignee with a message on the carrier's web site stating that the online signature request has been denied and providing an online, printable DAF. If the online signature is authorized, at step 536 the consignee would provide his online signature. This may be done by providing an electronic or digital signature or other method known in the art.
If the online signature is accepted at step 534, it can be provided in various ways, as described further below. For example, the “online signature” may be provided simply by the consignee clicking on a box agreeing to certain legal “Terms and Conditions”. In other embodiments, the consignee may be directed to a web page having a graphic box to indicate his signature using a mouse or other pointing device, as described below. Once the signature has been accepted by the carrier, the carrier system updates the shipment information in the PLD database (step 548) to indicate that an authorization signature has been provided for package release. If the package had not yet left the shipping facility, this information would become part of the package level data and would authorize the delivery personnel to deliver the package without requiring a signature at the time of delivery.
Alternatively, if the package were already en route to the consignee, the updated PLD information may be communicated to a portable computing device associated with delivery personnel delivering the package, such as the DIAD (Delivery Information Acquisition Device) carried by delivery personnel of UPS. The DIAD is typically uploaded with information for the carrier's package processing systems for each package scheduled to be delivered. Aspects of the DIAD are disclosed in U.S. patent application Ser. No. 10/227,147, filed Aug. 23, 2002, the contents of which are incorporated herein by reference in their entirety. The CSS 104 may communicate any generic delivery information or package specific information to a package processing system, which in turn forwards the information to the DIAD when there is an update in the delivery information for the consignee or the shipment. Information conveyed to the DIAD can be of various forms, including notes, alerts, or procedural details associated with the indicated consignee (discussed further below). The delivery personnel will then have information that an online signature has been provided at or before the time of delivery, and will deliver the package (step 550) without requiring a signature from the consignee upon delivery.
In another embodiment, upon accessing the status of the shipment via the carrier's website (step 520), the consignee may request signature waiver (step 540) to effect a Package Release. The Package Release allows a consignee to indicate that a package (or plurality of packages) may be released without the consignee's signature. The carrier may then communicate with the consignor to determine if it is allowable for the signature to be waived (step 542). Alternatively, whether or not a signature is required may be part of the package level data stored in the PLD database 133. As another example, the carrier may have previously received information from the consignor indicating that a signature is required and may not be waived. If, at step 544 the signature waiver is approved, the CSS would update the PLD database with this information and continue in accordance with step 548, described above. If the signature may not be waived, the package may be delivered according to ordinary delivery procedures, and a signature would be required from the consignee at the time of shipping (not shown). Alternatively, at step 546, the carrier may communicate an updated notification message to the consignee indicating that signature waiver has not been accepted. The message may include an attachment of a delivery authorization form in electronic image format, such as *.pdf, *.gif, or other web-transportable image, or may include a hyperlink to the carrier's website which would provide online access to a DAF. The consignee may then proceed according to step 580.
Advanced Signature Authorization Via Consignor's Web Site
Returning to step 508, the consignee can access the consignor's web site through a hyperlink provided in an email from the consignor (or the carrier) or proactively, and can then proceed to step 560 where the consignee may confirm the status of the shipment. The consignor's website may provide a hyperlink to the carrier's website via path 562, after which the consignee would proceed with step 520 as discussed above. Alternatively, the consignor and carrier's web sites may be linked through the APIs between the carrier and consignor's computers, and the consignor may request the shipment status information from the carrier by path 562 and the carrier may return the shipment status information to the consignor via path 564 to be displayed on the consignor's web site.
The consignee may then request signature waiver at step 570. If the consignor authorizes waiver of the signature requirement, the consignor communicates this information to the carrier (step 572). This may be communicated via email, through the Internet via the web interface of both the consignor or and the carrier, via the APIs, or through any other means known in the art. The carrier would then proceed as in step 548 in updating the PLD database 133 with the information that the signature requirement has been waived. Delivery personnel would then deliver the package without requiring a signature from the consignee at the time of delivery (step 550).
Returning to step 560, according to another embodiment of the present invention, upon confirming shipment status through the consignor's web site, the consignee may request a delivery authorization form at step 574. The consignor's web site may then provide a means for the consignee (path 566) to access directly the carrier's web site to obtain the DAF and proceed as in step 524. The consignor may provide this link to the consignee via an email, through a hyperlink on the consignor's web site, or through any other means known in the art. Alternatively, the consignor's system communicates with the carrier's web site via path 566 (such as by accessing the carrier's system via the API) and requests the DAF from the carrier. The carrier would then generate the DAF (including any related information, such as the consignee's name, address and telephone, and the tracking number of the shipment, among other information). The DAF may also include a serial number associated with the DAF, as will be discussed in more detail below.
The carrier would then communicate the DAF to the consignor via path 568 (such as, for example, via the consignor's API 147). The consignor then provides or transmits the DAF to the consignee in step 576. The consignor may provide the form to the consignee as an attachment to an email in electronic image format, such as *.pdf, *.gif, or other web-transportable image format, or may provide a hyperlink to allow the consignee to access an online version of the form. The consignee would then proceed to step 580 as discussed above.
When the consignor provides the consignee with a DAF at step 576 (or possibly when the carrier provides the DAF at several points in the system), the DAF may or may not include an associated serial number. Several possibilities for the inclusion or exclusion of a serial number on the consignor-provided DAF are described below. The procedures used by the delivery personnel depend on the presence of a serial number on the DAF. The DAF may be completely filled out, signed, dated, and have an associated serial number, in which case delivery would proceed under normal delivery procedures.
As discussed earlier in conjunction with
Electronic Signature Via Carrier's Web Site
The consignee may also complete any information on the DAF that was not pre-populated by the carrier. The CSS 104 captures this electronic signature and stores it (along with any additional information completed by the consignee). The electronic signature may be stored as “inactive” at this time, as it has not yet been associated with or used to release the delivery of the package. In one embodiment, this information may be stored in the PLD database. In other embodiments, some or all of this information could be stored in the consignee profile database. Once the carrier website captures the electronic signature and other information, the completed DAF is presented to the consignee. At step 4, the consignee can print the signed DAF and post it at a location at the delivery address (such as at the front door).
Upon delivering the package to the consignee, the delivery personnel retrieves the DAF, and can scan it using a portable computing device, such as the DIAD. In the embodiment illustrated in
At step 6, the delivery information is uploaded to the DIAD Capture System (DCS, described further below). At step 7, the CSS 104 solicits package status information from the DCS for all packages shipped from the consignor, based on tracking numbers. The solicited data is retrieved from the DCS and the results are returned for all delivered packages at step 8. This information can then be stored in the PLD database. At step 9, the electronic signature provided at step 3 will be retained or overridden, depending on certain parameters. If the delivery personnel released the package based on retrieving the DAF including the electronic signature, then the electronic signature will be retained and stored, and will remain associated with the DAF. However, the consignee, when completing the DAF, may have indicated that delivery was to occur at a neighbor's address. If the delivery personnel releases the package to the indicated neighbor, the delivery personnel may obtain a signature from the neighbor on an additional DAF. This signed DAF, and its signature, would override the electronic signature provided by the consignee. Similarly, the consignee may have thought initially that he would not be home to accept delivery, and thus may have completed and signed a DAF at step 3. For various reasons, however, the consignee may actually be present at the time of delivery and can provide a “live” signature. Upon receiving the “live” signature on the DIAD, this signature will override the electronic signature provided at step 3. The consignee's electronic signature can then be removed from the database in which it was stored.
At step 10, the consignor can log into a secure carrier website and be provided with a visual representation of the signed DAF. The consignor can then print the electronic DAF with the electronic signature and keep this DAF for the consignor's record. Similarly, the carrier (e.g., via a customer service center or representative), can access the carrier web site and retrieve the DAF and associated information and signature. This may be useful for updating data associated with the consignee or shipment in the consignee profile database and PLD database.
Possible Schemes for Associating a Serial Number to a DAF
The possibilities described below are representative only, and do not preclude other possibilities or combinations thereof, as may come to mind to one skilled in the art.
Possibility 1: Serial Number not Included on the DAF or not Provided to Consignee
In the situation where the DAF does not have a serial number associated with it, several options for delivery procedures exist for the delivery personnel to follow. For instance, delivery personnel may select a serial number to associate with a DAF at the time of delivery. The delivery personal may select the number by copying the number from an existing paper-based delivery notice or selecting a value stored in the DIAD. The delivery personnel would manually write the number on the DAF. Alternatively, the delivery personnel may have a roll or sheet of stickers with a sequential serial number printed on each sticker, where each delivery personnel has a different range of serial number stickers such that the delivery personnel may peel a sticker from the sheet or roll and affix it to the DAF. The delivery personnel may then enter this serial number into the DIAD to associate the value with the DAF. In addition, the sticker may provide the serial number in a bar code or other machine readable form, such that the delivery personnel may scan the sticker and scan the package to associate the serial number with the tracking number. As another alternative, when the delivery personnel returns to the carrier's facility, the serial number that was manually entered onto the DAF or the serial number of the sticker that was affixed to the DAF may be communicated to the CSS and/or other carrier systems.
A second option for delivery personnel to associate a serial number with a DAF that does not already have an associated serial number is for the carrier to provide its delivery personnel with a stack of blank DAFs so that when a delivery personnel encounters a DAF that does not have an associated serial number, he may take a DAF (similar to the existing UPS InfoNotice® forms) from his stack of blank DAFs and associate that serial number to the signed DAF. As an example (as illustrated in the “Service Provider Instructions” in
Another option for associating a serial number to a DAF that has been signed but does not have an associated serial number is for the delivery personnel to communicate with the CSS at the time of delivery (such as via the DIAD). The delivery personnel may input the tracking number of the package or shipment into the system, the CSS would process this information, such as by accessing the PLD database in order to retrieve the package information and generating an associated serial number, and then would return a serial number to the delivery personnel (such as via the DIAD) for the delivery personnel to associate with the DAF. The delivery personnel may then manually write down the serial number in a space provided on the DAF. In this aspect, the CSS may have already associated the tracking number and the provided serial number, such that when the delivery personnel returns to the carrier facility with the signed form and the manually entered serial number, the records center need only verify the association of the serial number and tracking number.
Possibility 2: Carrier Provides Consignor with Predetermined Range of Serial Numbers
A second possibility is that the carrier may have assigned a range of serial numbers to the consignor to allocate as required. The carrier would have to allocate each consignor unique values to avoid duplication. This allows the consignor to directly provide the consignee with a DAF with a serial number from the predetermined range. This avoids the consignor at step 360 having to communicate with the CSS at path 370 to request a DAF with an associate serial number. Thus, if for some reason the consignor's system was unable to communicate with the carrier's system at paths 370 and 372, the consignor could still provide a serial number-associated DAF to the consignee upon the consignee so requesting at step 360. Alternatively, if the consignor requests a DAF from the carrier at path 370 and the generated DAF that that the carrier sends back to the consignor does not include a serial number, the consignor may associate a serial number from the predetermined range to be associated with this DAF. The consignor may somehow manipulate the DAF to include the serial number (such as by editing the electronic image to include the serial number), or may provide it to the consignee and instruct the consignee to fill in the serial number manually on the DAF.
Alternatively, if the consignor requested a DAF from the carrier at path 370 and the carrier generated DAF related information including a serial number, or if the carrier sent the DAF with minimal information including at least a serial number, the consignor could provide this serial number-associated DAF to the consignee at step 362 and not have to assign a serial number from the predetermined range of numbers provided by the carrier.
Delivery under Possibility 2 would occur under normal procedures. The delivery personnel may retrieve the signed DAF and scan in the serial number, such that the serial number is associated with the tracking number in the CSS. Alternatively, the delivery personnel will return to the carrier's facility and may provide the DAF to the records center so that the serial number may be officially associated with the shipment in the carrier's system.
Possibility 3: Carrier Assigns Individual Serial Numbers to Each DAF Requested by the Consignor
A third possibility would allow the consignor and carrier systems to be in communication (such as via the API of each system or the web interface of each system), such that every time a consignee requests a DAF from the consignor at step 360, the consignor would communicate with the carrier via path 370 and the carrier would generate a serial number at step 304. The carrier would communicate this information back to the consignor via path 372.
If a serial number was provided and included on the DAF, delivery under Possibility 3 would occur under normal procedures. The delivery personnel may retrieve the signed DAF and scan in the serial number, such that the serial number is associated with the tracking number in the CSS. If a serial number was not provided from the carrier to the consignor, delivery personnel may follow the delivery procedures outlined in Possibility 1.
Example Application of Advance Delivery Authorization
A description of the systems and methods for providing a consignee with Advance Delivery Authorization is now provided using one embodiment of the present invention. This description represents one possible method of a consignee using the service, and does not represent all possible variations of the service or possible events that can occur.
A consignee orders a product from a consignor by accessing the consignor's web site. Upon ordering the product, the consignee provides relevant information, such as the consignee's name, address, email address, phone number, and other identifying information, comprising the order and/or shipping information. The consignor associates an order number with this order. The consignor provides the appropriate shipping information to the carrier and is provided with a tracking number. The package is provided to the carrier bearing the tracking number.
The carrier then processes the package, and through existing procedures notifies the consignee of the anticipated delivery date of the package. The notification may include a hyperlink or other link to the web site of the carrier as well as the tracking number. The consignee may then click on this link or otherwise use the link to connect to the web site of the carrier. Alternatively, if the consignee has previously received a tracking number or other shipment identifying number, the consignee may proactively access the web site of the carrier and indicate the tracking number.
Upon accessing the carrier's website, the consignee confirms the status of the shipment. The carrier's web site provides information such as the tracking number, the number of packages in the shipment, and information as to where the shipment is in the delivery process (such as at a hub awaiting delivery, en route, etc.). The shipment status typically provides an estimated time and/or date of delivery. Assuming the consignee determines he is unavailable at the expected delivery time, the consignee requests a DAF from the carrier's web site.
The CSS generates a DAF, which includes the tracking number, the consignor's name and address, the consignee's name, address and telephone number, and a serial number. The DAF may also include special delivery instructions that the consignee may have previously provided to the carrier, such as the preferred delivery location or site. Upon generating the DAF, the CSS would provide the DAF to the consignee via the carrier's web site, so that the consignee may print the DAF directly from the web site. Alternatively, the CSS may provide a hyperlink to the carrier's web site where the DAF would be available for the consignee to print. Another alternative would be for the CSS to generate an email to the consignee that would include the DAF as an attachment or in the body of the email.
The CSS may then update the DIAD Updating System 402 and indicate that a DAF and associated serial number was generated for the consignee. The DIAD Updating System 402 will then communicate this information to the DIAD of the delivery personnel at the appropriate time of the day of the package's delivery (discussed further below).
After the consignee prints the DAF provided from the carrier, the consignee may fill in any information that may not have been filled in by the carrier (such as if the consignee has an alternate phone number that had not been previously associated with the shipment, or an alternate delivery location that differs from the location as provided in the consignee's special delivery preferences). The consignee signs and dates the form. The consignee attaches the DAF to the anticipated delivery site (such as the consignee's front or back door).
The delivery personnel retrieves the signed DAF at the time of delivery and then delivers the package. The delivery personnel may scan the DAF to read the serial number and confirm it is the serial number indicated in the DIAD for this particular delivery.
Carrier Provided Personalized Delivery Information (CPPDI)
Heretofore described, the information provided to the DIAD (or other portable computing device) has been personalized delivery information that originated from the consignor, or the consignee. There is another category of information that may be provided to the DIAD in conjunction with a package delivery that originates from the carrier itself. This information is known as carrier provided personalized delivery information, or CPPDI.
Typically, carrier delivery personnel are responsible for delivering packages along a regular route. In many instances, the delivery personnel become familiar with the route and develop a personal knowledge of the route, the consignees along the route and their delivery preferences, and other information pertaining to package delivery along the route. For example, the delivery personnel may know that a particular elderly consignee has a health condition (e.g., a bad back), and that packages should be left on a table at the front door. The elderly consignee may not have communicated this information to the carrier via the aforementioned systems or methods, but may have informed the delivery personnel in person at some point in time (such as at the time of a prior delivery). The delivery personnel may also know that certain consignee homes may be frequented by a dog or other animal. This type of information is often “stored” mentally by the delivery personnel, but in the case of the regular delivery personnel being replaced or substituted with a temporary driver, this information is unknown to the temporary driver.
Thus, the same infrastructure and systems, described above, that store and process delivery preferences and instructions of consignees and consignors, can also be the basis for storing and providing other information. This other information may be information observed by the carrier (e.g., the delivery personnel) at certain delivery addresses, specific route information (such as road conditions or detours), etc. Thus, if a regular delivery personnel is sick, a temporary or substitute driver can be provided with this carrier-provided information. This information can be provided by the carrier to the DIAD of the delivery personnel (regular and temporary) of various delivery routes to aid the delivery personnel with completing the delivery.
Types of Customized Pickup and Delivery (CPaD) Data
The personalized delivery preferences and instructions provided by the consignee and consignor, as well as the CPPDI described above, can be collectively referred to as Customized Pickup and Delivery (CPaD) data. Generally, CPaD data can be categorized into at least three types: Procedures, Alerts, and Notes. The distinction between the categories typically involves what information is conveyed and how and when it is processed by the carrier systems and the DIAD. In other embodiments, more or fewer categories can be defined. The following distinctions are not intended to limit the categories of information, but rather provide general guidelines as to what information falls into which category. Additionally, CPaD data may not necessarily be communicated to the DIAD as part of these categories, but may be sent to the DIAD in a different way or at a different time than described throughout.
Alerts are one type of CPaD data that comprise information that must be addressed by the delivery personnel. Generally, alerts must be addressed before the delivery to a consignee is completed, or before the delivery personnel proceeds to the next stop on the delivery route. One example of an Alert may be an indication that a delivery is COD (Cash-on-Delivery) and notifying the delivery personnel that only certified check or money order can be accepted from the consignee. In one embodiment, the DIAD displays an icon to the delivery personnel indicating that an Alert is involved with the delivery. Because the delivery personnel must address an Alert, certain screen functions of the DIAD may be interrupted or blocked until the delivery person addresses the Alert (i.e., reads, review, and/or acknowledges or responds to it).
Notes are another type of CPaD data. Notes involve information that is of a general informational nature. Typically, notes comprise information that can be bypassed, in that the delivery personnel are not required to acknowledge or respond to the information before proceeding with the delivery or other deliveries. An example of a Note may be a message indicating that a large dog is present at the consignee delivery address, and that the delivery personnel should beware of the dog. This type of message is informational only, and can be read and bypassed by the delivery personnel without any specific action being taken on the delivery personnel's part.
Procedures are another type of CPaD data that provide information to delivery personnel indicating a certain procedure or protocol that needs to be followed for delivery of the package. In many instances, Procedures accompany Alerts and/or Notes. For example, if an Alert is sent to the DIAD indicating that a package is COD, once the delivery personnel acknowledges the alert, he may be presented with certain Procedures to follow for the COD delivery. For instance, a Procedure message can remind the delivery personnel to obtain proof of identification before accepting a check or money order for a COD delivery. Similarly, if a Note is sent to the DIAD indicating that a large dog is usually present on the premises, and Procedure might follow indicating that packages can be left on the front porch to avoid encountering the dog.
It can be appreciated that Alerts, Notes, and Procedures can indicate various messages or information to delivery personnel, and can be sent to the DIAD in conjunction with each other in order to convey this information. Alerts, Notes, and Procedures can be presented on the DIAD in the form of text and/or graphics (e.g., including icons). The information can be in the form of ‘canned’ text or free-form text. Thus, certain common types of information (i.e., those Alerts, Notes, and Procedures that arise many times and generally not with reference to any specific consignee or delivery) can be provided as ‘canned’ text to the delivery personnel. For example, an Alert indicating that the delivery personnel must scan machine readable indicia on a DAF before proceeding with the next delivery may be ‘canned’ text. On the other hand, information that is more specific to a certain delivery or consignee, and is not commonly encountered, can be provided as determined by the originator of the message (e.g., in free-form text). Thus, the CSS 104 may have to generate a free-form Note to indicate that a large dog is present at the consignee's delivery address. Additionally, audible alarms (e.g., sounds, beeps, etc.) can be used in addition to text or icons, allowing the DIAD to provide an additional indication to the delivery personnel of the presence of CPaD data.
Triggering Alerts, Notes and Procedures to the DIAD
The distinction between Alerts, Notes and Procedures lies not only in the different type of information that each of these messages provide, but also in the ways in which the information can be triggered to be sent to the portable computing device (e.g., DIAD) carried by the delivery personnel. Alerts, Notes and Procedures can be triggered based on whether the delivery personnel is performing a delivery, a pickup, or a combination delivery and pickup. Alternatively, Alerts, Notes and Procedures can be triggered only during certain days of the week, for certain delivery addresses, only if the delivery personnel is a temporary driver (as opposed to the ‘regular’ driver), etc. Thus, there can be any number of criteria to trigger Alerts, Notes and Procedures to be sent to the DIAD.
As an example, a regular driver may notice that a large dog is always present at a particular address. The driver may contact the carrier (e.g., via the DIAD, or via a customer service representative, etc.), and inform the carrier that CPPDI should be entered into the carrier systems to indicate the presence of the dog at the address. In CSS 104 can then trigger this information to be presented in various ways. In one instance, the CSS 104 can trigger this information only if a temporary or new driver is delivering or picking up a package at this address. This message would likely be triggered in the form of a Note so that no response would be required by the driver, and would be triggered regardless of the day of the week.
As another example, a pickup location may be closed for two weeks due to a fire at the location. This information may be provided to the delivery personnel in the form of an Alert, and require that the delivery personnel acknowledge the message. Because this situation may affect the delivery personnel's delivery and pickup route for the day, this message may be triggered to be sent to the DIAD at the beginning of the delivery personnel's shift, and may be sent each day that the pickup location is closed. This information likely would be sent regardless of whether the delivery personnel is the regular driver or a temporary driver.
As another example, the DIAD typically provides the delivery personnel with a list of items to be delivered and picked up along the deliver route that day. This list can be presented to the delivery personnel at the beginning of the shift as general information. In this instance, the delivery personnel can view the list of pickup and delivery stops that need to be made, and can view any Alerts, Notes and Procedures associated with each stop, or with the day's route, at the beginning of the shift. These same Alerts, Notes and Procedures, however, can be triggered to be presented when the delivery personnel arrives at each pickup and delivery location as well.
Thus, there are numerous combinations of the ways and times at which CPaD data can be triggered to be sent to the DIAD.
Systems for Storing and Triggering CPaD Data to the DIAD
The above examples presume that CPaD data has been properly loaded into the DIAD for the current day's deliveries and pickups. This requires that the CPaD data be maintained in various information systems of the carrier so that the information can be downloaded properly to the DIAD at the necessary times.
Because the DPS 700 schedules the routes and dispatch plan for a given vehicle, the DPS 700 has information for every pickup and delivery scheduled for any vehicle in a particular service territory. Thus, any CPaD data associated with a pickup or delivery can be communicated to the DIAD associated with the pickup or delivery without involvement of the Preload Assist System (PAS) 710. However, as will be described further below, CPaD data can be associated with a pickup or delivery address, and the CPaD data may be sent to the DIAD via a different route. In this instance, the Preload Assist System (PAS) 710 receives packages (Units of Work, or “UOWs”) and allocates them to a particular delivery vehicle based on the preload plan 706 defined by the DPS 700. Typically, there are numerous delivery vehicles in a territory, and each package coming into the carrier handling facilities must be routed to the appropriate delivery vehicle for loading in a certain order. The preload plan 706 defines how the packages should be directed, and the PAS 710 uses the preload plan 706 to physically divert the packages to the appropriate delivery vehicle for loading in the specified order.
The PAS 710 retrieves CPaD data from the CPaD Matrix File 708. Although not shown, the DPS 700 and DCS 704 can also retrieve data from the CPaD Matrix File 708. The CPaD Matrix File 708 may comprise CPaD data associated with a consignee's address, a particular package, or other data. The file can be generated in a variety of ways, including data entry by a customer service agent. The agent may receive CPaD data generated by a consignor using a consignor shipping system interfacing with the carrier's systems. In other embodiments, the CPaD data may be received from consignees interacting with a carrier web site (e.g., in response to receiving notification of a delivery, as described above). In various other embodiments, the CPaD data may be CPPDI, provided by delivery personnel or the carrier, as described above. The CPaD Matrix File 708 can also comprise territory related information, procedure related data, general shipper related data, and specific shipper number data.
For each package loaded onto the delivery vehicle, the PAS 710 checks if there is any associated CPaD data in the CPaD Matrix File 708 and transfers that information along with the Alerts, Notes, and Procedures to the DIAD. The PAS 710 provides the CPaD data regarding the packages loaded onto the delivery vehicle to the appropriate DIAD 714 using a Route Manager (RM) 712 as a conduit. As described above, the DIAD 714 also receives information regarding the packages from the DCS 704 that provides information about the route and the deliveries. Typically, the CPaD data is provided to the DIAD 714 using a wireline connection prior to the start of the day's deliveries, during which time package related information is downloaded into the DIAD. In some embodiments, CPaD information can be sent wirelessly to the DIAD after the delivery vehicle has departed for the day's deliveries. The wireless transmission of data can use any of the well-known wireless data transfer mechanisms.
The CPaD Matrix File & Methods for Linking CPaD Data with Other Data
The CPaD Matrix File, described above, can contain various CPaD data as well as other relevant data, such as shipping data. At a high level, a “delivery” can be represented as a record being stored in a database having various fields. The database record for a “delivery” can be conceptually indexed or viewed as a collection of records based on any variety of fields, including the shipper (such as the consignor's identity, address, or unique consignor identification number), package (e.g., tracking number), consignee (e.g., consignee name, address, or unique consignee identification number), delivery truck route, etc.
Any particular data field associated with a delivery related record can be thought of as shipment-dependent data, and is called herein a “delivery-related datum” (DRD). From an implementation aspect, CPaD data (which may be shipment-independent or shipment-dependent) can be associated or linked with any DRD within the CPaD Matrix File. For example, every package delivery is associated with a consignee's address. Thus, the consignee's address is one example of a DRD which can be linked to CPaD data. Each delivery is also associated with a shipper (consignor). Thus, the shipper is another form of a DRD, which can be linked to a particular piece of CPaD data. Another example of a DRD is a package identifier such as a tracking number, which is an alpha-numeric value many carriers assign to each package and/or delivery and typically used for tracking purposes. CPaD data can also be linked to a package tracking number. Thus, CPaD data can be associated with any DRD, or a set of DRD associated with a delivery. Thus, CPPDI provided by the carrier, or consignee and consignor personalized information can be linked to DRD for a particular package or delivery.
Various examples illustrate how CPaD data can be associated with different DRD. As discussed above, consignee personalized delivery instructions or preferences can be provided for delivery of a specific package. Thus, the CPaD data (the personalized delivery instructions), would be linked with a DRD, which likely would be the package tracking number. By associating the personalized delivery instructions with the package tracking number, the relevant carrier systems are able to provide the appropriate information to the DIAD at the proper time. For example, if the CPaD data contained an indication that delivery was to be made to the back door at the consignee's address, by linking this data to the package tracking number, this information could be provided as a Note to the DIAD at the time when the delivery personnel delivers the package to the consignee's address.
As another example, if the CPaD data is CPPDI, indicating that a particular pickup location is closed for two weeks, this CPaD data could be linked with the relevant DRD, namely, the address of the pickup location (such as the consignor's address, for instance). By linking this data, the relevant carrier systems would know to trigger this information to the DIAD at the beginning of the delivery day, so that the delivery personnel knows not to drive to this location.
As yet another example, consider a retail business that normally schedules packages to be picked up every business day. The business may request that a particular loading dock be used for all package pickups/deliveries for a given time period week while the normal loading dock is undergoing renovation. In this case, the information may indicate that a certain loading dock should be used for a given time period. It would be appropriate to associate this delivery preference information with the pickup/delivery address for a given time period. This would avoid having to link the CPaD data to each and every package delivered and/or picked up at that location.
Various possibilities for linking CPaD data to DRD are possible, and the following list represents a few of the possibilities of how CPaD data can be linked. For example, a delivery preference could be associated with: a consignee's address, an address with a specific consignee, an individual consignee within that building, consignee's floor of a multi-story building, pickup location of a specific packaging being delivered, pickup location for a set of packages, shipper number, or package tracking number.
The linking or association of CPaD data to DRD is relevant because it can impact how and when the CPaD data is displayed and/or loaded in the DIAD (e.g., the conditions in which the delivery personnel is made aware of the CPaD data) as well as how the delivery preference data may be stored by the carrier. For example, if the delivery preference is linked with a package tracking number, the delivery preference may be stored or linked with a package level detail database record. If it is linked to a service location, a separate database may be used for storing the information.
Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
This application is a continuation of U.S. application Ser. No. 13/913,198 filed on Jun. 7, 2013, which is a continuation of U.S. application Ser. No. 13/913,066 filed on Jun. 7, 2013, which is a continuation of U.S. application Ser. No. 13/326,750 filed Dec. 15, 2011, which is a continuation of U.S. application Ser. No. 12/616,183 filed on Nov. 11, 2009, which is a continuation of U.S. application Ser. No. 11/460,268 filed on Jul. 27, 2006, which is a continuation of U.S. application Ser. No. 11/425,333 filed on Jun. 20, 2006, which claims priority to U.S. Provisional Application No. 60/750,684 filed on Dec. 14, 2005; U.S. Provisional Application No. 60/701,712 filed Jul. 22, 2005; and U.S. Provisional Application No. 60/692,849 filed Jun. 21, 2005, the contents of which are hereby incorporated in their entirety by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3721096 | Deckert, Jr. et al. | Mar 1973 | A |
| 3876059 | Durst | Apr 1975 | A |
| 3933031 | Uhlarik | Jan 1976 | A |
| 4111601 | Richard | Sep 1978 | A |
| 4832204 | Handy et al. | May 1989 | A |
| 5153842 | Dlugos, Sr. et al. | Oct 1992 | A |
| 5168444 | Cukor et al. | Dec 1992 | A |
| 5375240 | Grundy | Dec 1994 | A |
| 5400020 | Jones et al. | Mar 1995 | A |
| 5444444 | Ross | Aug 1995 | A |
| 5460110 | Eronen et al. | Oct 1995 | A |
| 5623260 | Jones | Apr 1997 | A |
| 5648770 | Ross | Jul 1997 | A |
| 5656799 | Ramsden et al. | Aug 1997 | A |
| 5657010 | Jones | Aug 1997 | A |
| 5659731 | Gustafson | Aug 1997 | A |
| 5668543 | Jones | Sep 1997 | A |
| 5711670 | Barr | Jan 1998 | A |
| 5786748 | Nikolic et al. | Jul 1998 | A |
| 5804802 | Card et al. | Sep 1998 | A |
| 5831860 | Foladare et al. | Nov 1998 | A |
| 5835377 | Bush | Nov 1998 | A |
| 5884272 | Walker et al. | Mar 1999 | A |
| 6029140 | Martin et al. | Feb 2000 | A |
| 6047264 | Fisher et al. | Apr 2000 | A |
| 6085170 | Tsukuda | Jul 2000 | A |
| 6208980 | Kara | Mar 2001 | B1 |
| 6211781 | McDonald | Apr 2001 | B1 |
| 6220509 | Byford | Apr 2001 | B1 |
| 6236972 | Shkedy | May 2001 | B1 |
| 6278936 | Jones | Aug 2001 | B1 |
| 6285916 | Kadaba et al. | Sep 2001 | B1 |
| 6289323 | Gordon et al. | Sep 2001 | B1 |
| 6292709 | Uhl et al. | Sep 2001 | B1 |
| 6304856 | Soga et al. | Oct 2001 | B1 |
| 6313760 | Jones | Nov 2001 | B1 |
| 6317060 | Jones | Nov 2001 | B1 |
| 6323254 | Weikard et al. | Nov 2001 | B1 |
| 6343275 | Wong | Jan 2002 | B1 |
| 6344796 | Ogilvie et al. | Feb 2002 | B1 |
| 6356196 | Wong et al. | Mar 2002 | B1 |
| 6363323 | Jones | Mar 2002 | B1 |
| 6411891 | Jones | Jun 2002 | B1 |
| 6422506 | Colby | Jul 2002 | B1 |
| 6442589 | Takahashi et al. | Aug 2002 | B1 |
| 6463354 | Pintsov | Oct 2002 | B1 |
| 6463420 | Guidice et al. | Oct 2002 | B1 |
| 6486801 | Jones | Nov 2002 | B1 |
| 6492912 | Jones | Dec 2002 | B1 |
| 6510383 | Jones | Jan 2003 | B1 |
| 6536659 | Hauser et al. | Mar 2003 | B1 |
| 6539360 | Kadaba | Mar 2003 | B1 |
| 6606604 | Dutta | Aug 2003 | B1 |
| 6618668 | Laird | Sep 2003 | B1 |
| 6634551 | Barta et al. | Oct 2003 | B2 |
| 6683542 | Jones | Jan 2004 | B1 |
| 6700507 | Jones | Mar 2004 | B2 |
| 6701299 | Kraisser et al. | Mar 2004 | B2 |
| 6714859 | Jones | Mar 2004 | B2 |
| 6741927 | Jones | May 2004 | B2 |
| 6748318 | Jones | Jun 2004 | B1 |
| 6748320 | Jones | Jun 2004 | B2 |
| 6763299 | Jones | Jul 2004 | B2 |
| 6763300 | Jones | Jul 2004 | B2 |
| 6765487 | Holmes et al. | Jul 2004 | B1 |
| 6772130 | Karbowski et al. | Aug 2004 | B1 |
| 6804606 | Jones | Oct 2004 | B2 |
| 6845448 | Chaganti et al. | Jan 2005 | B1 |
| 6859722 | Jones | Feb 2005 | B2 |
| 6862612 | Horn et al. | Mar 2005 | B1 |
| 6902109 | Barta et al. | Jun 2005 | B2 |
| 6904359 | Jones | Jun 2005 | B2 |
| 6931314 | Holland et al. | Aug 2005 | B2 |
| 6952645 | Jones | Oct 2005 | B1 |
| 6975998 | Jones | Dec 2005 | B1 |
| 6976090 | Ben-Shaul et al. | Dec 2005 | B2 |
| 6978929 | Buie et al. | Dec 2005 | B2 |
| 6985871 | Simon et al. | Jan 2006 | B2 |
| 6994253 | Miller et al. | Feb 2006 | B2 |
| 7028895 | Ashaari | Apr 2006 | B2 |
| 7030781 | Jones | Apr 2006 | B2 |
| 7031959 | Garner et al. | Apr 2006 | B2 |
| 7039813 | Algazi et al. | May 2006 | B2 |
| 7130803 | Couch et al. | Oct 2006 | B1 |
| 7152375 | Mastro et al. | Dec 2006 | B1 |
| 7158948 | Rodriguez et al. | Jan 2007 | B1 |
| 7177825 | Borders et al. | Feb 2007 | B1 |
| 7212829 | Lau et al. | May 2007 | B1 |
| 7212984 | Wolfe et al. | May 2007 | B2 |
| 7222081 | Sone | May 2007 | B1 |
| 7225983 | Park et al. | Jun 2007 | B2 |
| 7233907 | Young | Jun 2007 | B2 |
| 7248160 | Mangan et al. | Jul 2007 | B2 |
| 7249044 | Kumar et al. | Jul 2007 | B2 |
| 7249087 | Sharp et al. | Jul 2007 | B2 |
| 7257552 | Franco | Aug 2007 | B1 |
| 7305404 | Owens et al. | Dec 2007 | B2 |
| 7312702 | Willms et al. | Dec 2007 | B1 |
| 7331248 | Maresca, Jr. et al. | Feb 2008 | B2 |
| 7363126 | Zhong et al. | Apr 2008 | B1 |
| 7376598 | Estes et al. | May 2008 | B2 |
| 7385499 | Horton et al. | Jun 2008 | B2 |
| 7422149 | Aptekar | Sep 2008 | B2 |
| 7479899 | Horstemeyer | Jan 2009 | B2 |
| 7501946 | Lanigan et al. | Mar 2009 | B2 |
| 7511617 | Burman 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 |
| 7637466 | Dillard | Dec 2009 | B2 |
| 7647231 | Kuebert et al. | Jan 2010 | B2 |
| 7657466 | Klingenberg et al. | Feb 2010 | B2 |
| 7693723 | Wade | Apr 2010 | B2 |
| 7711654 | Schmidtberg et al. | May 2010 | B2 |
| 7712670 | Sauerwein, Jr. et al. | May 2010 | B2 |
| 7742928 | Reynolds et al. | Jun 2010 | B2 |
| 7752134 | Spear | Jul 2010 | B2 |
| 7765131 | Klingenberg et al. | Jul 2010 | B2 |
| 7769778 | Snapp et al. | Aug 2010 | B2 |
| 7831439 | Bryar et al. | Nov 2010 | B1 |
| 7848961 | Estes et al. | Dec 2010 | B2 |
| 7853481 | Johnson | Dec 2010 | B1 |
| 7868753 | Jenkins et al. | Jan 2011 | B2 |
| 7912854 | Owens et al. | Mar 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 |
| 20010042024 | Rogers | Nov 2001 | A1 |
| 20010051885 | Nardulli et al. | Dec 2001 | A1 |
| 20020007299 | Florence | Jan 2002 | A1 |
| 20020010634 | Roman et al. | Jan 2002 | A1 |
| 20020013744 | Tsunenari et al. | Jan 2002 | A1 |
| 20020016726 | Ross | Feb 2002 | A1 |
| 20020019761 | Lidow | Feb 2002 | A1 |
| 20020032573 | Williams et al. | Mar 2002 | A1 |
| 20020032612 | Williams et al. | Mar 2002 | A1 |
| 20020032623 | Wheeler et al. | Mar 2002 | A1 |
| 20020042808 | Smith et al. | Apr 2002 | A1 |
| 20020070882 | Jones | Jun 2002 | A1 |
| 20020073039 | Ogg et al. | Jun 2002 | A1 |
| 20020082770 | Jones | Jun 2002 | A1 |
| 20020087371 | Abendroth | Jul 2002 | A1 |
| 20020103724 | Huxter | Aug 2002 | A1 |
| 20020107820 | Huxter | Aug 2002 | A1 |
| 20020111914 | Terada et al. | Aug 2002 | A1 |
| 20020120475 | Morimoto | Aug 2002 | A1 |
| 20020130065 | Bloom | Sep 2002 | A1 |
| 20020147919 | Gentry | Oct 2002 | A1 |
| 20020156645 | Hansen | Oct 2002 | A1 |
| 20020156846 | Rawat et al. | Oct 2002 | A1 |
| 20020165729 | Kuebert et al. | Nov 2002 | A1 |
| 20020178074 | Bloom | Nov 2002 | A1 |
| 20030003936 | Tighe | Jan 2003 | A1 |
| 20030004893 | Blaesche | Jan 2003 | A1 |
| 20030032573 | Tanner et al. | Feb 2003 | A1 |
| 20030036938 | Dutta et al. | Feb 2003 | A1 |
| 20030037009 | Tobin et al. | Feb 2003 | A1 |
| 20030074411 | Nale | Apr 2003 | A1 |
| 20030097287 | Franz et al. | May 2003 | A1 |
| 20030110170 | Matsuoka | Jun 2003 | A1 |
| 20030114206 | Timothy et al. | Jun 2003 | A1 |
| 20030182017 | O'donohue et al. | Sep 2003 | A1 |
| 20030193414 | Jones | Oct 2003 | A1 |
| 20030195811 | Hayes et al. | Oct 2003 | A1 |
| 20040030478 | Holland et al. | Feb 2004 | A1 |
| 20040073499 | Martin et al. | Apr 2004 | A1 |
| 20040088224 | Mukai | May 2004 | A1 |
| 20040093312 | Cordery et al. | May 2004 | A1 |
| 20040117326 | Amato | Jun 2004 | A1 |
| 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 |
| 20040227630 | Shannon et al. | Nov 2004 | A1 |
| 20040241644 | Samadpour | Dec 2004 | A1 |
| 20040243430 | Horstemeyer | Dec 2004 | A1 |
| 20040254802 | Miller et al. | Dec 2004 | A1 |
| 20040254811 | Horstemeyer | Dec 2004 | A1 |
| 20040260470 | Rast | Dec 2004 | A1 |
| 20050004877 | Mclellan et al. | Jan 2005 | A1 |
| 20050038758 | Hilbush et al. | Feb 2005 | A1 |
| 20050043845 | Wiechers | Feb 2005 | A1 |
| 20050071258 | Kumakawa | Mar 2005 | A1 |
| 20050080638 | Maseruka | Apr 2005 | A1 |
| 20050082752 | Acosta | Apr 2005 | A1 |
| 20050104716 | Simms et al. | May 2005 | A1 |
| 20050114221 | Walters et al. | May 2005 | A1 |
| 20050177387 | Mojsa | Aug 2005 | A1 |
| 20050216144 | Baldassa | Sep 2005 | A1 |
| 20050216294 | Labow | Sep 2005 | A1 |
| 20050216553 | Mallonee et al. | Sep 2005 | A1 |
| 20050251402 | Olsen et al. | Nov 2005 | A1 |
| 20050252596 | Olsen et al. | Nov 2005 | A1 |
| 20060010037 | Angert et al. | Jan 2006 | A1 |
| 20060022895 | Williams et al. | Feb 2006 | A1 |
| 20060041481 | Stowe | Feb 2006 | A1 |
| 20060047610 | Parkos et al. | Mar 2006 | A1 |
| 20060069601 | Simon et al. | Mar 2006 | A1 |
| 20060074729 | Capotosto et al. | Apr 2006 | A1 |
| 20060085273 | Mayer et al. | Apr 2006 | A1 |
| 20060097896 | Jones | May 2006 | A1 |
| 20060100970 | Morony et al. | May 2006 | A1 |
| 20060149577 | Stashluk et al. | Jul 2006 | A1 |
| 20060229895 | Kodger, Jr. | Oct 2006 | A1 |
| 20060248941 | Maresca et al. | Nov 2006 | A1 |
| 20060255136 | Wagner et al. | Nov 2006 | A1 |
| 20060282277 | Ng | Dec 2006 | A1 |
| 20070000989 | Kadaba | Jan 2007 | A1 |
| 20070005452 | Klingenberg et al. | Jan 2007 | A1 |
| 20070078797 | Won et al. | Apr 2007 | A1 |
| 20070083410 | Hanna | Apr 2007 | A1 |
| 20070133876 | Chande et al. | Jun 2007 | A1 |
| 20070150533 | Krause et al. | Jun 2007 | A1 |
| 20070156415 | Foth et al. | Jul 2007 | A1 |
| 20070156439 | Fyda et al. | Jul 2007 | A1 |
| 20070192191 | Neal et al. | Aug 2007 | A1 |
| 20070200671 | Kelley et al. | Aug 2007 | A1 |
| 20070202802 | Kallio et al. | Aug 2007 | A1 |
| 20070257774 | Stumpert et al. | Nov 2007 | A1 |
| 20080004995 | Klingenberg et al. | Jan 2008 | A1 |
| 20080125959 | Doherty et al. | May 2008 | A1 |
| 20080133261 | Ray | Jun 2008 | A1 |
| 20080154781 | Kumar | Jun 2008 | A1 |
| 20080162241 | Betancourt | Jul 2008 | A1 |
| 20080172305 | Estes et al. | Jul 2008 | A1 |
| 20080201155 | Som | Aug 2008 | A1 |
| 20080208772 | Rundle | Aug 2008 | A1 |
| 20080210749 | Skaaksrud et al. | Sep 2008 | A1 |
| 20080221913 | Cook et al. | Sep 2008 | A1 |
| 20080223940 | Lee et al. | Sep 2008 | A1 |
| 20080281719 | Hall et al. | Nov 2008 | A1 |
| 20080312991 | Bharadwaj et al. | Dec 2008 | A1 |
| 20080319970 | Garner et al. | Dec 2008 | A1 |
| 20080320092 | Campbell et al. | Dec 2008 | A1 |
| 20090012802 | Pinney | Jan 2009 | A1 |
| 20090046892 | Avant et al. | Feb 2009 | A1 |
| 20090106124 | Yang | Apr 2009 | A1 |
| 20090138730 | Cook et al. | May 2009 | A1 |
| 20090146832 | Ebert et al. | Jun 2009 | A1 |
| 20090164295 | Sion | Jun 2009 | A1 |
| 20090164390 | Calman et al. | Jun 2009 | A1 |
| 20090173672 | Avant et al. | Jul 2009 | A1 |
| 20090187489 | Mallick et al. | Jul 2009 | A1 |
| 20090269760 | Samadpour | Oct 2009 | A1 |
| 20090281929 | Boitet et al. | Nov 2009 | A1 |
| 20090314835 | Jackson | Dec 2009 | A1 |
| 20090319078 | Jackson | Dec 2009 | A1 |
| 20090326971 | Piccinini et al. | Dec 2009 | A1 |
| 20090327361 | Mills et al. | Dec 2009 | A1 |
| 20100004960 | Frankenberg et al. | Jan 2010 | A1 |
| 20100049536 | Quine et al. | Feb 2010 | A1 |
| 20100057592 | Moir et al. | Mar 2010 | A1 |
| 20100057593 | Moir et al. | Mar 2010 | A1 |
| 20100076903 | Klingenberg et al. | Mar 2010 | A1 |
| 20100100229 | Whitson et al. | Apr 2010 | A1 |
| 20100100497 | Kuebert et al. | Apr 2010 | A1 |
| 20100121689 | Wallace et al. | May 2010 | A1 |
| 20100185565 | Wade | Jul 2010 | A1 |
| 20100211426 | Mcclurg | Aug 2010 | A1 |
| 20100211444 | Spear | Aug 2010 | A1 |
| 20100235210 | Nadrotowicz, Jr. | Sep 2010 | A1 |
| 20100299278 | Kriss et al. | Nov 2010 | A1 |
| 20110004562 | Hennessy et al. | Jan 2011 | A1 |
| 20110022532 | Kriss | Jan 2011 | A1 |
| 20110060552 | Ono | Mar 2011 | A1 |
| 20110125665 | Kadaba | May 2011 | A1 |
| 20110238195 | Nagy et al. | Sep 2011 | A1 |
| 20110270714 | Myrick et al. | Nov 2011 | A1 |
| 20110320308 | 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 |
| 20120130625 | Srivastava | May 2012 | A1 |
| 20120130916 | Neal et al. | May 2012 | A1 |
| 20120173308 | Brown et al. | Jul 2012 | A1 |
| 20120173448 | Rademaker | Jul 2012 | A1 |
| 20120179622 | Amato | Jul 2012 | A1 |
| 20120208559 | Svendsen et al. | Aug 2012 | A1 |
| 20120235791 | Donlan et al. | Sep 2012 | A1 |
| 20120246077 | Skaaksrud et al. | Sep 2012 | A1 |
| 20120303538 | Marcus et al. | Nov 2012 | A1 |
| 20120303539 | Marcus et al. | Nov 2012 | A1 |
| 20120303540 | Marcus et al. | Nov 2012 | A1 |
| 20120303541 | Marcus et al. | Nov 2012 | A1 |
| 20120303542 | Marcus et al. | Nov 2012 | A1 |
| 20120310853 | Aldstadt | Dec 2012 | A1 |
| 20130006731 | Cook et al. | Jan 2013 | A1 |
| 20130006777 | Krishnareddy et al. | Jan 2013 | A1 |
| 20130006885 | Kuebert et al. | Jan 2013 | A1 |
| 20130013101 | Bonnell et al. | Jan 2013 | A1 |
| 20130013102 | Bonnell et al. | Jan 2013 | A1 |
| 20130013350 | Mccullough et al. | Jan 2013 | A1 |
| 20130016636 | Berger et al. | Jan 2013 | A1 |
| 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 |
| 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 |
| Number | Date | Country |
|---|---|---|
| 1643534 | Jul 2005 | CN |
| 101203873 | Jun 2008 | CN |
| 102567883 | Jul 2012 | CN |
| 19644163 | May 1998 | DE |
| 10007897 | Jun 2001 | DE |
| 2483220 | Mar 2012 | GB |
| 10-207956 | 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 |
| 2005-213020 | Aug 2005 | JP |
| 2006-206225 | Aug 2006 | JP |
| 201220221 | May 2012 | TW |
| 0019170 | Apr 2000 | WO |
| 0019171 | Apr 2000 | WO |
| 0030014 | May 2000 | WO |
| 0046726 | Aug 2000 | WO |
| 0046728 | Aug 2000 | WO |
| 0052422 | Sep 2000 | WO |
| 0116889 | Mar 2001 | WO |
| 0129778 | Apr 2001 | WO |
| 0135344 | May 2001 | WO |
| 0139031 | May 2001 | WO |
| 0165451 | Sep 2001 | WO |
| 0165454 | Sep 2001 | WO |
| 0165523 | Sep 2001 | WO |
| 0165524 | Sep 2001 | WO |
| 0167344 | Sep 2001 | WO |
| 0172109 | Oct 2001 | WO |
| 0184359 | Nov 2001 | WO |
| 0188831 | Nov 2001 | WO |
| 0197101 | Dec 2001 | WO |
| 0207104 | Jan 2002 | WO |
| 0217045 | Feb 2002 | WO |
| 02052378 | Jul 2002 | WO |
| 03034293 | Apr 2003 | WO |
| 2004015518 | Feb 2004 | WO |
| 2005105329 | Nov 2005 | 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 |
| Entry |
|---|
| Final Office Action received for U.S. Appl. No. 13/465,555, dated Jul. 17, 2015, 12 pages. |
| Final Office Action received for U.S. Appl. No. 13/465,555, dated Mar. 15, 2017, 9 pages. |
| Final Office Action received for U.S. Appl. No. 13/465,555, dated Mar. 17, 2016, 16 pages. |
| Final Office Action received for U.S. Appl. No. 13/465,555, dated Nov. 20, 2014, 9 pages. |
| Final Office Action received for U.S. Appl. No. 13/569,316, dated Dec. 24, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/569,316, dated Jun. 29, 2017, 40 pages. |
| Final Office Action received for U.S. Appl. No. 13/569,316, dated Mar. 3, 2015, 13 pages. |
| Final Office Action received for U.S. Appl. No. 13/569,316, dated May 10, 2013, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/569,316, dated Nov. 6, 2012, 12 pages. |
| Final Office Action received for U.S. Appl. No. 13/569,316, dated Nov. 17, 2015, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/746,854, dated Nov. 17, 2015, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/746,862, dated Jul. 10, 2017, 38 pages. |
| Final Office Action received for U.S. Appl. No. 13/746,862, dated Mar. 2, 2015, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/746,862, dated Nov. 17, 2015, 16 pages. |
| Final Office Action received for U.S. Appl. No. 13/762,969, dated Apr. 14, 2015, 12 pages. |
| Final Office Action received for U.S. Appl. No. 13/839,398, dated Jun. 5, 2017, 13 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,066, dated Mar. 20, 2015, 13 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,066, dated May 27, 2016, 20 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,171, dated Jul. 18, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,171, dated Jun. 8, 2016, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,171, dated Mar. 24, 2015, 12 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,185, dated May 16, 2014, 16 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,185, dated Oct. 20, 2015, 18 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,185, dated Sep. 11, 2017, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,191, dated Jul. 10, 2017, 20 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,191, dated Jun. 9, 2016, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,191, dated Mar. 10, 2015, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,198, dated Jun. 14, 2016, 20 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,198, dated Mar. 11, 2015, 13 pages. |
| Final Office Action Received for U.S. Appl. No. 14/025,893, dated Apr. 7, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/049,605, dated Dec. 12, 2016, 16 pages. |
| Final Office Action received for U.S. Appl. No. 14/049,605, dated Oct. 2, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/049,828, dated May 3, 2017, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/100,556, dated Sep. 20, 2017, 9 pages. |
| Final Office Action received for U.S. Appl. No. 11/460,268, dated Aug. 6, 2009, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,248, dated May 16, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,269, dated May 8, 2013, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,290, dated May 15, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,299, dated May 15, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,306, dated May 21, 2013, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/181,185, dated Sep. 26, 2013, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/839,398, dated Jan. 20, 2016, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/913,198, dated Jul. 28, 2017, 21 pages. |
| Frontline Solutions, “Fed Ex Improves Internal, External Operations”, Article, Fairfax, Virginia and Memphis, Tennessee, Available at: <http://www.frontlinemagazine.com/art_th/04052001.htx>, Apr. 5, 2001, pp. 1-2. |
| Gao et al., Cyber-Physical-Social Systems: Harnessing the Crowdsourcing Power of Social Media for Disaster Relief, IEEE Intelligent Systems, IEEE Computer Society, 2011, pp. 10-14. |
| Harrington, Lisa, The US Postal Service Gets Serious about Serving Business in the New Economy, Transportation & Distribution, vol. 41, No. 5, Penton Publishing, Inc., United States of America, May 2000, p. 2. |
| Henderson, Timothy, Buy.com Boosts Returns Process Efficiency with New Solution, ProQuest Info & Leaming, vol. 82, No. 11, Nov. 2000, pp. 72-76. |
| Henderson, Timothy P., Scheduling Software Helps Webvan Meet 30-Minute Delivery Window, Descartes, Available at: <www.stores.org>, Jul. 2000. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/068210, dated Jan. 2, 2015, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/068219, dated Dec. 12, 2014, 7 pages. |
| Applicant Initiated Interview Summary Received for U.S. Appl. No. 13/839,398, dated Feb. 22, 2016, 5 pages. |
| Brewin, et al., “Follow that Package!”, Article, Computer World, Available at: <www.computerworld.com/printthis/2001//0,4814,58696,00.html>, Mar. 19, 2001, pp. 1-5. |
| Caminiti, et al., “United Parcel Service Introduces Advanced Label Imaging System”, Business Wire, Section 1, Nov. 29, 1989, 1 page. |
| Communication Pursuant to Rules 70(2) and 70a(2) EPC received for European Application No. 13796181.9, dated May 24, 2016, 9 pages. |
| Declaration of David Ellison Pertaining to UPS and Mailbox etc. pre-filing activities from Mar. 2001-Nov. 1, 2002. |
| Demarco, Donna, “E-tail Presents Can be Tougher to Send Back than Order”, Journal, Knight-Ridder/Tribune Business News, The Dialog Corporation, US, Dec. 28, 1999. |
| El Portal Del Transporte, “Fedex Insight Empowers Customers with Enhanced Shipment Visibility and Control”, Article, Retrieved from: <http://www.transportando.net/newsabri1_completa.htm>, Apr. 11, 2001, pp. 9-10. |
| Extended European Search Report received for European Patent Application No. 13821253.5, dated May 17, 2016, 11 pages. |
| Extended European Search Report received for European Patent Application No. 13795343.6, dated May 19, 2016, 9 pages. |
| Final Office Action received for U.S. Appl. No. 13/326,887, dated Apr. 9, 2015, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/326,851, dated Apr. 29, 2015, 15 pages. |
| Final Office Action for U.S. Appl. No. 13/174,248, dated Dec. 27, 2013, 09 pages. |
| Final Office Action for U.S. Appl. No. 13/174,248, dated Jun. 27, 2017, 33 pages. |
| Final Office Action for U.S. Appl. No. 13/174,248, dated Mar. 4, 2015, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/174,248, dated Nov. 17, 2015, 16 pages. |
| Final Office Action for U.S. Appl. No. 13/174,269, dated Dec. 27, 2013, 09 pages. |
| Final Office Action for U.S. Appl. No. 13/174,269, dated Mar. 2, 2015, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/174,290, dated Dec. 27, 2013, 09 pages. |
| Final Office Action for U.S. Appl. No. 13/174,299, dated Dec. 27, 2013, 08 pages. |
| Final Office Action for U.S. Appl. No. 13/174,299, dated Nov. 10, 2015, 13 pages. |
| Final Office Action for U.S. Appl. No. 13/174,299, dated Mar. 2, 2015, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/174,306, dated Dec. 26, 2013, 9 pages. |
| Final Office Action for U.S. Appl. No. 13/174,306, dated Mar. 2, 2015, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/174,306, dated Nov. 17, 2015, 15 pages. |
| Final Office Action for U.S. Appl. No. 13/746,842, dated Feb. 27, 2015, 14 pages. |
| Final Office Action for U.S. Appl. No. 13/746,842, dated Feb. 13, 2014, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/746,842, dated Jan. 22, 2016, 17 pages. |
| Final Office Action for U.S. Appl. No. 13/746,842, dated Jun. 29, 2017, 32 pages. |
| Final Office Action for U.S. Appl. No. 13/746,854, dated Dec. 27, 2013, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/746,854, dated Feb. 27, 2015, 12 pages. |
| Final Office Action received for U.S. Appl. No. 10/696,180, dated Mar. 13, 2014, 25 pages. |
| Final Office Action received for U.S. Appl. No. 10/696,180, dated Aug. 19, 2009, 15 pages. |
| Final Office Action received for U.S. Appl. No. 10/696,180, dated Dec. 22, 2016, 29 pages. |
| Final Office Action received for U.S. Appl. No. 10/696,180, dated Feb. 15, 2011, 25 pages. |
| Final Office Action received for U.S. Appl. No. 10/696,180, dated Oct. 18, 2010, 16 pages. |
| Final Office Action received for U.S. Appl. No. 10/696,180, dated Oct. 8, 2015, 23 pages. |
| Final Office Action received for U.S. Appl. No. 11/425,333, dated Jun. 11, 2009, 13 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,248, dated Feb. 12, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,269, dated Feb. 4, 2013, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,269, dated Nov. 17, 2015, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,290, dated Feb. 21, 2013, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,290, dated Nov. 17, 2015, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,290, dated Mar. 2, 2015, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,299, dated Feb. 8, 2013, 9 pages. |
| Final Office Action received for U.S. Appl. No. 13/174,306, dated Feb. 15, 2013, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/181,185, dated Jun. 10, 2015, 22 pages. |
| Final Office Action received for U.S. Appl. No. 13/326,750, dated Apr. 20, 2015, 13 pages. |
| Final Office Action received for U.S. Appl. No. 13/326,807, dated Apr. 7, 2015, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/326,807, dated Jun. 26, 2014, 10 pages. |
| Final Office Action received for U.S. Appl. No. 14/640,753, dated Jan. 16, 2018, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019475, dated Sep. 22, 2016, 9 pages. |
| International Search Report and Written Opinion for PCT Patent Application No. PCT/US2011/059511, dated May 2, 2012, 6 pages. |
| International Search Report and Written Opinion for PCT Patent Application No. PCT/US2013/75572, dated Feb. 20, 2015, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2006/024169, dated May 10, 2007, 6 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/059504, dated Apr. 24, 2012, 6 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/059506, dated Aug. 3, 2012, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/059508, dated Feb. 4, 2015, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/059513, dated Apr. 27, 2012, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/068210, dated May 20, 2014, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/068219, dated Feb. 21, 2014, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/016025, dated Apr. 29, 2015, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/042959, dated Aug. 4, 2015, 8 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2003/34746, dated Jul. 5, 2005, 1 page. |
| Lindsay, Bruce R., Congressional Research Service, Social Media and Disasters: Current Uses, Future Options, and Policy Considerations, CRS Report for Congress, Congressional Research Service, Sep. 6, 2011, 10 pages. |
| Many Happy Returns—UPS Unveils Advanced Outline Returns Solution, Accession No. 12921102, Business Wire, Sep. 20, 2000. |
| Non Final Office Action for U.S. Appl. No. 13/174,248, dated Dec. 23, 2016, 28 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,248, dated Sep. 6, 2013, 10 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,269, dated Jan. 10, 2017, 26 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,269, dated Aug. 29, 2013, 10 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,290, dated Dec. 28, 2016, 27 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,299, dated Aug. 29, 2013, 9 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,299, dated Dec. 23, 2016, 27 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,299, dated Jul. 23, 2015, 12 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,306, dated Aug. 29, 2013, 10 pages. |
| Non Final Office Action for U.S. Appl. No. 13/174,306, dated Dec. 23, 2016, 25 pages. |
| Non Final Office Action for U.S. Appl. No. 13/746,842, dated Oct. 2, 2013, 12 pages. |
| Non Final Office Action for U.S. Appl. No. 13/746,854, dated Aug. 19, 2014, 11 pages. |
| Non Final Office Action for U.S. Appl. No. 13/746,842, dated Aug. 19, 2014, 14 pages. |
| Non Final Office Action received for U.S. Appl. No. 13/174,290, dated Aug. 29, 2013, 11 pages. |
| Non Final Office Action received for U.S. Appl. No. 13/746,854, dated Oct. 2, 2013, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Dec. 9, 2009, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Feb. 3, 2009, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Jul. 18, 2013, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Jul. 7, 2011, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Jun. 1, 2016, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Jun. 25, 2015, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated May 10, 2010, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/696,180, dated Nov. 8, 2017, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/425,333, dated Oct. 15, 2008, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/460,268, dated Jan. 23, 2009, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/616,183, dated Sep. 23, 2011, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,248, dated Aug. 18, 2014, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,248, dated Jul. 23, 2015, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,248, dated Nov. 27, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 131174,269, dated Aug. 18, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,269, dated Jul. 23, 2015, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,269, dated Nov. 7, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,290, dated Aug. 18, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,290, dated Jul. 23, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,290, dated Nov. 28, 2012, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,185, dated Jun. 15, 2015, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,185, dated Mar. 23, 2017, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,191, dated Dec. 5, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,191, dated Jan. 12, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,191, dated Oct. 24, 2013, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,191, dated Sep. 24, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,198, dated Dec. 1, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,198, dated Oct. 25, 2013, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,198, dated Sep. 24, 2015, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/025,893, dated Nov. 22, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/025,893, dated Sep. 22, 2016, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/049,605, dated Aug. 25, 2016, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/049,605, dated Jun. 14, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/049,828, dated Oct. 3, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/100,556, dated Mar. 25, 2016, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/100,556, dated May 1, 2017, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/707,039, dated Nov. 13, 2017, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/181,185, dated Apr. 13, 2016, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/181,185, dated Aug. 4, 2017, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,887, dated Dec. 17, 2015, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,198, dated Feb. 3, 2017, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/623,145, dated Aug. 3, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/640,753, dated Jul. 21, 2017, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/460,268, dated Mar. 25, 2010, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/326,750, dated Jun. 17, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/913,066, dated Aug. 7, 2018, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/913,066, dated Feb. 5, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/913,066, dated May 7, 2018, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/913,171, dated Feb. 11, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/913,191, dated Feb. 20, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/913,198, dated Mar. 6, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/425,333, dated Nov. 2, 2009, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/616,183, dated Nov. 10, 2011, 7 pages. |
| Office Action for U.S. Appl. No. 13/746,854, dated Jul. 11, 2017, 36 pages. |
| Office Action for U.S. Appl. No. 13/746,854, dated Mar. 9, 2017, 34 pages. |
| Office Action for Canadian Patent Application No. 2,942,296, dated Jul. 11, 2017, 6 pages. |
| Office Action from Canadian Patent Application 2,924,132, dated Nov. 20, 2017, 6 pages. |
| Office Action from Canadian Patent Application 2,954,156, dated Nov. 22, 2017, 4 pages. |
| Office Action from Canadian Patent Application 2,957,135, dated Dec. 27, 2017, 8 pages. |
| Office Action received for European Patent Application No. 06773704.9, dated Sep. 15, 2017, 5 pages. |
| Office Action Received for Canadian Application No. 2,924,132, dated Feb. 10, 2017, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,504,285, dated Feb. 15, 2012, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,609,841, dated Aug. 26, 2015, 5 pages. |
| Office Action Received for Canadian Patent Application No. 2,609,841, dated Dec. 2, 2011, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,609,841, dated Nov. 14, 2016, 8 pages. |
| Office Action received for Canadian Patent Application No. 2,609,841, dated Oct. 6, 2014, 3 pages. |
| Office Action received for Canadian Patent Application No. 2,881,201, dated Jun. 6, 2017, 6 pages. |
| Office Action received for Canadian Patent Application No. 2,884,747, dated Apr. 27, 2017, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,884,747, dated May 30, 2016, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,885,818, dated May 24, 2017, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,299, dated Aug. 18, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,299, dated Dec. 31, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,306, dated Aug. 18, 2014, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,306, dated Dec. 28, 2012, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/174,306, dated Jul. 23, 2015, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/181,185, dated Apr. 9, 2013, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/181,185, dated Mar. 27, 2014, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/181,185, dated Nov. 7, 2014, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,750, dated Dec. 23, 2015, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,750, dated Jan. 30, 2014, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,750, dated Sep. 5, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,807, dated Feb. 5, 2014, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,807, dated Sep. 18, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,851, dated Aug. 5, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,851, dated Dec. 24, 2015, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,851, dated Feb. 21, 2014, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,887, dated Feb. 13, 2014, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/326,887, dated Sep. 25, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/465,555, dated Mar. 12, 2015, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/465,555, dated Nov. 10, 2016, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/465,555, dated Nov. 19, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/465,555, dated Oct. 7, 2014, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/569,316, dated Aug. 22, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/569,316, dated Aug. 29, 2013, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/569,316, dated Dec. 22, 2016, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/569,316, dated Feb. 6, 2013, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/569,316, dated Jul. 23, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/569,316, dated Sep. 19, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,842, dated Jan. 11, 2017, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,842, dated Jul. 23, 2015, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,854, dated Jul. 23, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,862, dated Aug. 20, 2014, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,862, dated Dec. 23, 2013, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,862, dated Feb. 27, 2017, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,862, dated Jul. 23, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/746,862, dated Oct. 8, 2013, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/762,969, dated Aug. 29, 2014, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/839,398, dated Jul. 7, 2015, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/839,398, dated Oct. 6, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,066, dated Dec. 22, 2016, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,066, dated Nov. 13, 2015, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,066, dated Nov. 26, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,066, dated Oct. 11, 2013, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,066, dated Oct. 24, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,171, dated Dec. 15, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,171, dated Jan. 27, 2017, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,171, dated Nov. 20, 2014, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,171, dated Oct. 2, 2013, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,185, dated Dec. 13, 2013, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/913,185, dated Jan. 30, 2015, 15 pages. |
| Office Action received for Canadian Patent Application No. 2,885,818, dated May 30, 2016, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,891,876, dated Jun. 15, 2016, 4 pages. |
| Office Action received for Canadian Patent Application No. 2,957,133, dated Dec. 22, 2017, 10 pages. |
| Office Action received for Chinese Patent Application No. 201380070843.2, dated Jun. 27, 2017, 23 pages. |
| Office Action received for Chinese Patent Application No. 201380070854.0, dated Jun. 29, 2017, 15 pages. |
| Office Action received for Chinese Patent Application No. 201380067429 , dated Apr. 27, 2017. |
| Office Action received for European Patent Application No. 03778034.3, dated Dec. 2, 2013, 5 pages. |
| Office Action received for European Patent Application No. 06773704.9, dated Feb. 5, 2014, 6 pages. |
| Office Action received for European Patent Application No. 13158961.6, dated Mar. 3, 2017, 6 pages. |
| Office Action received for European Patent Application No. 13158965.7, dated Mar. 23, 2017, 7 pages. |
| Office Action received for European Patent Application No. 13158966.5, dated Mar. 23, 2017, 6 pages. |
| Office Action received for European Patent Application No. 13158967.3, dated Mar. 23, 2017, 7 pages. |
| Office Action received for European Patent Application No. 13795343.6, dated Mar. 2, 2017, 5 pages. |
| Office Action received for European Patent Application No. 13796181.9, dated Feb. 10, 2017, 5 pages. |
| Outlook 2000 Handbook First Edition, last 9 lines, p. 95. |
| Pender, Lee, Hard Times are the Best Times, Magazine, Cio, Available at: <www.cio.com/archive/081501/besttimes_content.html>, Aug. 15, 2001, pp. 3-7. |
| Quantum View Inbound, Quantum View Outbound, How Quantum View Outbound Works, Quantum View Service Options, Quantum View and UPS Administration, QuantumViewTM, Available at : <http://www.ups.com/iovs/ivs_learnmore.html>, Aug. 7, 2002, 15 pages. |
| Raco Industries, Increase Delivery Visibility and Simplify Your Process, Available at: <http://www.racointeractive.com/media/834/raco_interactive-pd.pdf>, Retrieved on Sep. 25,2013, 2 pages. |
| Requisition by Examiner received for Canadian Patent Application No. 2,504,285, dated Oct. 10, 2013, 2 pages. |
| Requisition by the Examiner for Canadian Application No. 2,842,840, dated Nov. 4, 2015, 5 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13795343.6, dated Nov. 17, 2017, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13796181.9, dated Oct. 12, 2017, 12 pages. |
| Van Huzien, Gordon, Messaging: The Transport Part of the XML Puzzle, “IBM Developer Works, Article, Retrieved from:<URL:http:/ /www-106.ibm.com/developerworks/library/xml-messaging/>”, Jul. 2000, 8 pages. |
| Fedex, FedEx Mobile Ship, Available at: <http://www.fedex.com/us/mobile/label.html, redirected to http://mobilesolutions.fedex.com/shipping-label.html>, Retrieved on Sep. 25, 2013, 2 pages. |
| FedEx, RPS Adds Automated Package Pick-up to Redesigned Web Site, Avaliable at: <www.fedex.com/us/about/ground/pressreleases/pressrelease111198.html?link=4>, Retrieved on Sep. 10, 2003. |
| IPventure, Schedule Distribution Routes and Timeslots, IP Ventures, Available at: <https://www.ipventure.com/onlineorder/distribution.php>, Retrieved on Apr. 16, 2008. |
| Number | Date | Country | |
|---|---|---|---|
| 20190034874 A1 | Jan 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60750684 | Dec 2005 | US | |
| 60701712 | Jul 2005 | US | |
| 60692849 | Jun 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13913198 | Jun 2013 | US |
| Child | 16151212 | US | |
| Parent | 13913066 | Jun 2013 | US |
| Child | 13913198 | US | |
| Parent | 13326750 | Dec 2011 | US |
| Child | 13913066 | US | |
| Parent | 12616183 | Nov 2009 | US |
| Child | 13326750 | US | |
| Parent | 11460268 | Jul 2006 | US |
| Child | 12616183 | US | |
| Parent | 11425333 | Jun 2006 | US |
| Child | 11460268 | US |
