The present invention relates to package delivery, and in particular to status inquiries regarding delivery of shipments.
People who use online merchants or delivery companies with online access usually have at least two possible methods to track and confirm delivery of packages or other items. According to the first method, users must remember a unique—and usually difficult to remember—tracking identifier. Such a tracking code is normally a string of letters and/or numbers that have no easily remembered meaning. According to a second alternative method, the user must go through a time-consuming authentication process in order to access the tracking identifier, or in order to directly access the tracking information. Plainly, either of these two methods has drawbacks.
If the shipment was initiated in conjunction with a purchase, then the user can authenticate to the merchant web site where the user made the purchase, but less time spent authenticating normally means less security for the customer. Following a lengthy authentication, the user would then see a merchant's or shipping carrier's display of the tracking identifier as a hypertext shortcut directly to the tracking information, or a display of the tracking information itself, or the user would see a query for even more information if the merchant has not automatically provided that information to the carrier. Thus, the existing art has not yet achieved a satisfactory alternative to memorization of long tracking identifiers.
The present application describes an illustrative process that is as convenient as activating a script or executable file, in order for a user to check and verify shipping status. For instance, at the time of a transaction, the company (i.e. a merchant, carrier, or related business) will formulate a small html page that is capable of redirecting the user to the carrier's web site with the query and tracking identifier already entered. The user is then given the option to save this small html page on the user's desktop or other local storage area. From then on, the user just double clicks that html file, and current shipping information is displayed without any need for the user to memorize a tracking identifier or spend time authenticating.
An illustrative embodiment of the application has at least two advantages. First, it eliminates the need of users remembering long and arcane tracking identifiers. Second, it eliminates the need of users taking time to provide authentication information in order to log into secure web sites for the purpose of checking a shipping status.
An illustrative embodiment of the application is well-suited to a situation in which a user is tracking more than one shipment, either using a single carrier or a plurality of carriers. In the latter case, at least some shipping data is aggregated so that a user is able to quickly and easily access shipping status from two or more carriers.
According to a preferred embodiment of this invention, when a user clicks on a desktop icon or other hyperlink, the user is not only provided delivery status, but is also provided with the opportunity to have delivery status updated. For example, a carrier will already typically update delivery status when the package arrives at a discrete set of points A, B, C, D, and E. The illustrative embodiment of the application allows the user to find out where the item is between, for example, points A and B or between points B and C. This is accomplished, for example, by having GPS units on vehicles. Advantageously, the user is provided one free access to the system, and then has to pay for further clicks in order to get this deluxe pinpoint tracking information within a certain time of clicking the icon or hyperlink. In contrast, there is normally no need to charge extra for arrival status at the discrete checkpoints A, B, C, D, and E.
An illustrative embodiment of the present invention begins when the user completes his or her transaction in a normal way at a web site, and then chooses a shipping option. Then, the web site processes the transaction, creates a small html file, and sends that file to the user who will save it locally. The content of the html file will look like the following:
The user then saves this html file locally in a convenient place. When the user wants to check the status of a package, the user will double click on the html file. The html file redirects the user appropriately to the tracking page showing the status of their package.
Extensions and more advanced embodiments can be implemented. For example, to be expandable, a web site can combine all the current valid tracking identifiers each time a user ships another package. The user is then asked to replace his html file with a new one, which would contain all previous tracking numbers (minus any that are not relevant anymore) plus the user's new tracking identifier. This is feasible if all the packages are shipped from the same carrier. If all items are not with the same carrier, then a company could create another web page that buffers all the requests to the multiple carriers, so the redirect actually sends all the tracking identifiers to a web page which is scripted to ascertain which carrier goes with which identifier, and returns the results all on one page. This extension could be implemented as a web service.
Another extension is to have a small client application that goes out and polls the carriers' sites regarding the tracking information. Then, when a new item is shipped, the user can add it to his list of currently tracked items, via a file-type association download that automatically puts it in the client application, or via a manual addition. Alternatively, item information is downloaded as an html file in the way described above, but the small client application goes through a directory and scans all the html files in the directory for tracking identifiers.
The file that redirects the end user can be implemented in various scripting languages, including markup languages such as html. Moreover, the company web site can actually continue to buffer the user from the carriers, by redirecting them to their web sites and submitting the multiple queries for tracking on behalf of the user. Because of this, the company can list the shipping status of all current packages. Another alternate approach is for the file to redirect using Hypertext Transfer Protocol Secure (“https”) to provide a higher level of confidentiality. In an additional alternative embodiment, the web site only provides the option of downloading the shortcut file to the end user, instead of sending it directly.
Some more advanced implementations of the present invention use a heavy client on a user's computer. A “listener” process wakes up when the user receives a tracking identifier in a web page, or when a user goes to a carrier's web site. Note that most carriers have a unique structure to their tracking identifier, which potentially facilitates recognition of incoming tracking identifiers. After waking up, the heavy client program continues to run as a background process, and polls the carriers' web sites so as to notify the user with a message when a package reaches certain user-configurable conditions.
This type of implementation can, for example, poll at 15-minute intervals after the status has been changed (to “out for delivery” for instance). A message would then pop up onscreen when a GPS unit in a delivery vehicle returns a coordinate within a set distance from the user's house. That way the user will know that a delivery will be arriving imminently, and will be able to make plans accordingly.
Of course, all of the foregoing internet or network interaction can be done over a Secure Sockets Layer (SSL) or other cryptographically secured channel giving the end user confidentiality of their shipping queries. This would also ensure that thieves will not be able to easily intercept the pinpoint location of a delivery vehicle. The down side to having a secure connection is that accessing it can be time-consuming, and the embodiments of the present application addresses this problem by streamlining the user access.
The illustrative embodiments of the present application can be more fully appreciated by reference to the accompanying figures. As seen in
In other words, the user decides whether he or she needs more precise pinpoint information about shipment status, instead of merely finding out which checkpoint was the most recent one that the shipment passed through. If checkpoint status is sufficient, then the user clicks 110 on the checkpoint symbol. Then it is determined 112 if the user is already connected to the network (e.g. the internet), preferably via a secure connection. If not, then such a connection is established 115. When the connection is in place, a checkpoint inquiry is sent 117 to the shipping carrier, and the carrier provides a checkpoint location to the user. Subsequently, the user is able to repeat this procedure.
If, at step 105, the user decides that more precise shipping status is desired, then the user clicks 121 on the shipment pinpoint symbol which may be available on the user's desktop or in a folder in the user's computer, or additionally may be available at a carrier's web site that has been accessed by previously having clicked 110 on the shipment checkpoint symbol. Assuming that the pinpoint symbol is at a user desktop or user folder, it is then determined 123 whether the user is connected to the network, and if not then that connection is established 125, so that a pinpoint inquiry is sent 127 to the carrier. In response to that inquiry, the carrier ascertains 129 a pinpoint location of the shipment between checkpoints. This may be done, for example, by communicating with a delivery truck or airplane which is equipped with a global positioning satellite (GPS) device, and then the carrier can plot the GPS coordinates on a map and present 131 the map to the user. If 132 the user is provided with the pinpoint location after a delay, then the user can be compensated 133 for the delay, for example by providing the user with a monetary credit, or by providing the user with a free pinpoint click in the future.
Turning now to
In the context of the present invention, pinpoint status means any shipment status that provides greater accuracy than checkpoint status. The checkpoint status comprises information as to whether a shipment has reached or been scanned at one or more discrete points. The carrier may be any kind of delivery company, or company that includes delivery service, or form of transportation. The shipment carried by the carrier is any physical letter, package, paper, envelope, carton, or the like. The type of shipment may be overnight, same day, priority, express, or other designation that identifies the manner in which the shipment is carried.
Various changes may be made in the above illustrative embodiments without departing from the scope of the invention, as will be understood by those skilled in the art. It is intended that all matter contained in the above description or shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense. The invention disclosed herein can be implemented by a variety of combinations of hardware and software, and those skilled in the art will understand that those implementations are derivable from the invention as disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
6463420 | Guidice et al. | Oct 2002 | B1 |
6965868 | Bednarek | Nov 2005 | B1 |
7020584 | Takaoka et al. | Mar 2006 | B2 |
7112500 | Ando et al. | Sep 2006 | B2 |
7191142 | Sandell et al. | Mar 2007 | B1 |
7212829 | Lau et al. | May 2007 | B1 |
7660721 | Williams et al. | Feb 2010 | B2 |
7693964 | Hancock et al. | Apr 2010 | B2 |
20020032573 | Williams et al. | Mar 2002 | A1 |
20020082893 | Barts et al. | Jun 2002 | A1 |
20020116241 | Sandhu et al. | Aug 2002 | A1 |
20040024644 | Gui et al. | Feb 2004 | A1 |
20040024658 | Carbone et al. | Feb 2004 | A1 |
20040024660 | Ganesh et al. | Feb 2004 | A1 |
20050251330 | Waterhouse et al. | Nov 2005 | A1 |
20060053027 | Riggs et al. | Mar 2006 | A1 |
20070168263 | Hammell | Jul 2007 | A1 |
20080040144 | Riggs et al. | Feb 2008 | A1 |
Number | Date | Country | |
---|---|---|---|
20050114236 A1 | May 2005 | US |