System and method for processing package delivery

0001This application is a divisional of Ser. No. 10/052,110, filed Jan. 17, 2002, the entirety of which is incorporated herein by reference.

FIELD OF THE INVENTION

0002The invention generally relates to the field of package delivery. More particularly, the invention relates to systems and methods for processing package delivery and includes computer implemented systems and methods.

BACKGROUND OF THE INVENTION

0003Recent events, such as the mailing of anthrax to government officials and news agencies, have heightened many people's concerns about the safety of package delivery. Nevertheless, people often depend on package delivery to receive purchases, correspondence, and the like. Further, package delivery has increased over time and may continue to increase with increasing on-line shopping via the Internet. As such, it appears that package delivery will continue to be an important way for people to receive purchases, correspondence, and the like. There is not presently available a system for determining whether a package is expected and therefore legitimate, or whether a package has arrived unexpectedly from an unrecognized source and therefore may be for illegitimate purposes.

0004In view of the foregoing, there is a need for a system and method for authorizing package delivery.

SUMMARY OF THE INVENTION

0005The invention is directed to determining a package delivery authorization status and conditioning package delivery on the state of the delivery authorization status.

0006A method for processing packages is provided. A package is received at an intermediate shipping site and a delivery authorization status corresponding to the package is determined. The package is delivered if the authorization status is that delivery is acceptable and the package is not delivered if the authorization status is that delivery is not acceptable.

0007Delivery authorization is determined by receiving information identifying the received package and receiving information identifying an expected package. The information identifying the expected package is compared to the information identifying the received package. The package is designated for delivery if the information identifying the expected package matches the information identifying the received package. The package may be designating for non-delivery if the information identifying the expected package does not match the information identifying the received package.

0008The information may comprise at least one of the following: an identification of the sender of the package, the addressee of the package, an identification of the, package, and a projected date of delivery. The information may be received via an e-mail message, a bar code scanner, and the like. An e-mail message may be received from a sender of the package or an addressee of the package.

0009Delivery authorization may also be determined based on a list of predefined sellers. The package sender is determined and compared to a plurality of predefined pre-approved senders. The delivery authorization status is designated as delivery is acceptable if the determined package sender matches one of the plurality of predefined senders and designated as delivery is not acceptable if the determined package sender does not match any of the plurality of predefined pre-approved senders.

0010Delivery authorization may also be determined based on two e-mail messages, one from the package sender and one from the package addressee. A first e-mail message is received from a sender of the package and a second e-mail message is received from an addressee of the package. From the first e-mail message, at least one of the following is determined: an identification of the sender of the package, an identification of the addressee of the package, an identification of the package, and a projected delivery date of the package. From the second e-mail message, at least one of the following is determined: an identification of the sender of the package, an identification of the addressee of the package, and an identification of the package. A delivery authorization status is also determined from the second e-mail message. The package is designated for delivery if the information determined from the first e-mail message matches the information determined from the second e-mail message and if the delivery authorization status determined from the second e-mail message is delivery is acceptable.

0011The above-listed features, as well as other features, of the invention will be more fully set forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

0012The invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting illustrative embodiments of the invention, in which like reference numerals represent similar parts throughout the drawings, and wherein:

0013<figref idref="DRAWINGS">FIG. 1</figref> is a diagram of an exemplary computing device and communications network with which the invention may be employed;

0014<figref idref="DRAWINGS">FIG. 2</figref> is a flow diagram of an illustrative method for processing packages, in accordance with an embodiment of the invention;

0015<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram of an illustrative method for determining whether package delivery is authorized, in accordance with an embodiment of the invention;

0016<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an illustrative data table for storing an authorization status as determined in the method of <figref idref="DRAWINGS">FIG. 3</figref>;

0017<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram of another method for determining whether package delivery is authorized, in accordance with another embodiment of the invention;

0018<figref idref="DRAWINGS">FIG. 6</figref> is a diagram of an illustrative data table for storing a plurality of predefined sender identifications to determine whether package delivery is authorized in accordance with the method of <figref idref="DRAWINGS">FIG. 5</figref>;

0019<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram of another illustrative method for determining whether package delivery is authorized, in accordance with another embodiment of the invention;

0020<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram of yet another illustrative method for determining whether package delivery is authorized, in accordance with another embodiment of the invention; and

0021<figref idref="DRAWINGS">FIG. 9</figref> is a diagram of an illustrative data table for storing an authorization status as determined in accordance with the method of <figref idref="DRAWINGS">FIG. 7</figref> or FIG. <b>9</b>.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

0022<figref idref="DRAWINGS">FIG. 1</figref> is a diagram of a generic computing system with which the invention may be employed. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, computing device <b>120</b> includes processor <b>122</b>, system memory <b>124</b>, and system bus <b>126</b> that couples various system components including system memory <b>124</b> to processor <b>122</b>. System memory <b>124</b> may include read-only memory (ROM) and/or random access memory (RAM). Computing device <b>120</b> may further include hard-drive <b>128</b>, which provides storage for computer readable instructions, data structures, program modules, data, and the like. A user (not shown) may enter commands and information into the computing device <b>120</b> through input devices such as a keyboard <b>140</b>, a mouse <b>142</b>, and a bar code scanner <b>146</b>. Display device <b>144</b> may also include other devices such as a touch screen, a light pen, a grid of light beams, or the like for inputting information into processor <b>122</b>. A display device <b>144</b>, such as a monitor, a flat panel display, or the like is also connected to the computing device <b>120</b> for output. Communications device <b>143</b>, which in one embodiment is a modem, provides for communications over network <b>150</b>. Processor <b>122</b> can be programmed with instructions to interact with other computing systems so as to perform the methods described below. The instructions may be received from network <b>150</b> or stored in memory <b>124</b> and/or hard drive <b>128</b>. Processor <b>122</b> may be loaded with any one of several computer operating systems such as WINDOWS NT operating system, WINDOWS 2000 operating system, LINUX operating system, and the like.

0023As shown in <figref idref="DRAWINGS">FIG. 1</figref>, computing device <b>120</b> may be connected to computer network <b>150</b>. Server <b>164</b> is operable to communicate with other computing devices over network <b>150</b>. Network <b>150</b> may be the Internet, a local area network, a wide area network, or the like. Server <b>164</b> may communicate e-mails, web pages, and other data. Server <b>164</b> may be operated by an ISP, a corporate computer department, or any other organization or person with a server connected to network <b>150</b>. Server <b>164</b> is accessible by client stations <b>168</b> from which users may send and receive data and browse web pages. Client stations <b>168</b> may connect to servers via a local area network (not shown) or using a remote connection device <b>172</b> such as, for example, a modem, as is shown in connection with server <b>164</b>.

0024The computing system described above may be used to implement an illustrative method for authorizing package delivery, such as the illustrative method of FIG. <b>2</b>. The method may be implemented for any type of package delivery, such as, for example, a book, a computer, a letter, or the like. The delivery may be made by any carrier, such as for example, the United States Post Office, Federal Express, United Parcel Service, a trucking company, and the like.

0025At step <b>200</b>, a package, which may be for example, a package containing a book that was requested to be delivered to a business address, is received at an intermediate site or a clearinghouse. In this illustrative example, the package is received at a mail room at the employee's business address. The package, however, may be received at any intermediate site, such as for example, a local post office, a local distribution site, a quarantined site, or the like. The intermediate site may be a secure site at a remote location. Typically, the intermediate site includes a computing device to maintain package authorization statuses.

0026At step <b>210</b>, a delivery authorization status corresponding to the received package is determined. The delivery authorization status identifies whether or not the package is to be delivered to the addressee. The delivery authorization status may indicate that the package is an expected package or that the package comes from a trusted source. The delivery authorization status may be determined, for example, using methods such as those described below in connection with <figref idref="DRAWINGS">FIGS. 3</figref>, <b>5</b>, <b>7</b>, and <b>8</b>.

0027At step <b>220</b>, it is determined whether or not the delivery authorization status indicates that package delivery is acceptable. If the delivery authorization status indicates that delivery is acceptable, then the method proceeds to step <b>230</b>, wherein the package is delivered from the intermediate location, such as the mail room, to the employee that purchased the book. If the delivery authorization status indicates that delivery is not acceptable, then the method proceeds to step <b>240</b>. At step <b>240</b>, the package is not delivered from the mail room to the employee; rather, the package may be returned to the sender, held until receiving an authorization status that delivery is acceptable, quarantined, receive further security checks, be discarded, or the like. In this manner, an addressee does not receive a package unless there is some authorization of package delivery, thereby increasing the security of package delivery. Instead, the package is held at an intermediate site (which may be a secure location, for example) where the package may be appropriately handled.

0028Determining delivery authorization status, as shown in step <b>210</b>, may be implemented in a variety of ways. <figref idref="DRAWINGS">FIG. 3</figref> illustrates one embodiment of the invention, in which package delivery authorization status is determined from an e-mail message. The embodiment illustrated in <figref idref="DRAWINGS">FIG. 3</figref> may be implemented on computing device <b>120</b> of FIG. <b>1</b> and will be described as such, however, the invention may be implemented on any computing system. The following illustration contemplates Benjamin Scott ordering a book entitled “American History Textbook” from Barnes and Noble wherein the book is projected to be delivered on Aug. 15, 2001.

0029As shown in <figref idref="DRAWINGS">FIG. 3</figref>, at step <b>300</b>, computing device <b>120</b> receives an e-mail message from network <b>150</b>. The e-mail message may be received from the package sender, which for purposes of illustration is Barnes and Noble. Alternatively, the e-mail message may be received from the package addressee, which for the purposes of illustration is Benjamin Scott. In this embodiment, the e-mail message itself serves as an authorization for package delivery. To determine which package has been authorized for delivery, the contents of the e-mail message are used, as described in more detail below.

0030At step <b>310</b>, processor <b>122</b> parses the e-mail message into segments. The email message may be formatted into segments by the e-mail sender (i.e., the package sender or the package addressee). For example, the e-mail message may be formatted into a first segment storing an identification of the sender of the package, a second segment storing an identification of the addressee of the package, a third segment storing an identification of the package, and a fourth segment storing a projected delivery date of the package. The identification of the package may be a description of the contents of the package, an identification number, or the like. The projected delivery date may also be a range of dates. The segments may be separated with commas, line returns, or the like to facilitate parsing.

0031Further, an application may be implemented on client <b>168</b> to create the proper e-mail format. For example, the application may display a pop-up window storing fields for an identification of the sender of the package, an identification of the addressee of the package, an identification of the package, and a projected delivery date of the package. Upon receiving information in each of the fields, the application may format the information as an e-mail message having the information in proper segments and with proper separation between segments.

0032At step <b>320</b>, processor <b>122</b> determines package identification information from one of the parsed segments. In this illustrative example, the parsed segment corresponding to package identification contains “American History Textbook” and therefore, processor <b>122</b> determines the package identification to be “American History Textbook.”

0033At step <b>330</b>, processor <b>122</b> determines sender identification information from one of the parsed segments. In this illustrative example, the parsed segment corresponding to sender identification contains “Barnes and Noble” and therefore, processor <b>122</b> determines the sender identification to be “Barnes and Noble.”

0034At step <b>340</b>, processor <b>122</b> determines a projected delivery date from one of the parsed segments. In this illustrative example, the parsed segment corresponding to the a projected delivery date contains “Aug. 15, 2001” and therefore, processor <b>122</b> determines the projected delivery date to be “Aug. 15, 2001.”

0035At step <b>350</b>, the delivery authorization status of the received package is determined by comparing information from the received package (i.e., package information) to information parsed from the e-mail message. Package information comprises information contained on the received package, such as for example, information on the shipping label, the packing list, and the like. Package information also comprises the actual delivery date of the package. Package information may be received by computing system <b>120</b> via bar code scanner <b>146</b>, keyboard <b>140</b>, mouse <b>142</b>, or the like.

0036If the package information matches the parsed information, then the delivery authorization status of the received package is determined to be that delivery is acceptable, as shown in steps <b>360</b> and <b>366</b>. If the package information does not match the parsed information from any e-mail message, then the delivery authorization status of the received package is determined to be that delivery is not acceptable, as shown in steps <b>360</b> and <b>364</b>. While the illustrative example of <figref idref="DRAWINGS">FIG. 3</figref> shows information parsed from a single e-mail, it is contemplated that a typical implementation of the invention involves multiple e-mails and comparing of package information to information parsed from each of the multiple e-mails, or until a match is determined.

0037To facilitate determining delivery authorization status, the parsed information may be stored in a data table for comparison against package information. <figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an illustrative data table <b>40</b> for storing parsed information. While a data table is illustrated, such information may be stored in a spreadsheet, a database, or the like. The data table may reside in memory <b>124</b>, hard-drive <b>128</b>, across network <b>150</b>, or the like.

0038Data table <b>400</b> comprises a record for each e-mail message. Each record comprises a plurality of fields for storing information parsed from the e-mail message. As shown in <figref idref="DRAWINGS">FIG. 4</figref>, record <b>410</b> comprises a first field <b>420</b> for storing a sender identification, a second field <b>422</b> for storing a package identification, a third field <b>424</b> for storing a projected delivery date, and a fourth field <b>426</b> for storing an addressee identification. As shown, first field <b>420</b> contains a sender identification of “Barnes and Noble,” second field <b>422</b> contains a package identification of “American History Textbook,” third field <b>424</b> contains a projected delivery date of “Aug. 15, 2001,” and fourth field <b>426</b> contains an addressee identification of “Benjamin Scott.” With such a data table, package information can be compared against multiple records of parsed information to determine a delivery authorization status.

0039While the embodiment illustrated in <figref idref="DRAWINGS">FIGS. 3 and 4</figref> can use a single e-mail message to determine a delivery authorization status, other techniques can be used to determine a delivery authorization status. For example, the embodiment illustrated in <figref idref="DRAWINGS">FIG. 5</figref> uses an e-mail message and a list of pre-approved senders to determine a delivery authorization status.

0040As shown in <figref idref="DRAWINGS">FIG. 5</figref>, at step <b>500</b>, computing device <b>120</b> receives an e-mail message from network <b>150</b>. The e-mail message may be received from the package sender or the package addressee.

0041At step <b>510</b>, processor <b>122</b> parses the e-mail message into segments. At step <b>520</b>, processor <b>122</b> determines a package identification from one of the parsed segments. At step <b>530</b>, processor <b>122</b> determines a sender identification from one of the parsed segments. At step <b>540</b>, processor <b>122</b> determines a projected delivery date from one of the parsed segments.

0042At step <b>550</b>, processor <b>122</b> compares parsed information to package information to determine a matching record, similar to that discussed above in connection with step <b>350</b>. If the received package information does not match the parsed information from any record, then the delivery authorization status is determined as delivery is not acceptable, as shown in steps <b>552</b> and <b>554</b>.

0043At step <b>560</b>, processor <b>122</b> compares the sender identification of the matching record to a list of pre-approved senders to determine a delivery authorization status of the received package. If the sender identification matches one of the pre-approved senders, then the delivery authorization status of the received package is determined to be that delivery is acceptable, as shown in steps <b>562</b> and <b>566</b>. If the sender identification does not match any of the pre-approved senders, then the delivery authorization status is determined to be that delivery is not acceptable, as shown in steps <b>562</b> and <b>564</b>.

0044Pre-approved sender information may be predefined and stored in a data table for comparison against package information and/or information parsed from an e-mail message. <figref idref="DRAWINGS">FIG. 6</figref> is a diagram of an illustrative data table <b>600</b> for storing pre-approved senders. While a data table is illustrated, such pre-approved sender information may be stored in a spreadsheet, a database, or the like. The data table may reside in memory <b>124</b>, hard-drive <b>128</b>, across network <b>150</b>, or the like.

0045Data table <b>600</b> comprises a field for storing an indication of each pre-approved sender. As shown in <figref idref="DRAWINGS">FIG. 6</figref>, first field <b>620</b> contains “Barnes and Noble”, second field <b>622</b> contains “Sears”, and third field <b>624</b> contains “J.C. Penney's.” With such a data table, package information and/or parsed information can be compared against a list of pre-approved senders to determine a delivery authorization status.

0046Other methods can be used to facilitate package delivery by non-pre-approved senders such as the illustrative method of <figref idref="DRAWINGS">FIG. 7</figref> that determines package delivery authorization status using messages from both a package sender and a package addressee. This method can be implemented in addition to or in place of the method described in connection with FIG. <b>5</b>.

0047As shown in <figref idref="DRAWINGS">FIG. 7</figref>, at step <b>700</b>, computing device <b>120</b> receives an e-mail message from the package sender via network <b>150</b>. At step <b>710</b>, processor <b>122</b> parses the e-mail message into segments. At step <b>720</b>, processor <b>122</b> determines a package identification from one of the parsed segments. At step <b>730</b>, processor <b>122</b> determines a sender identification from one of the parsed segments. At step <b>740</b>, processor <b>122</b> determines a projected delivery date from one of the parsed segments.

0048At step <b>750</b>, processor <b>122</b> displays information from the parsed message segments to the addressee. For example, processor <b>122</b> may read parsed information from the records of data table <b>400</b> and display the information on display device <b>144</b> or on client <b>168</b> over network <b>150</b> such that the package addressee can select one of the records for authorization of package delivery. The displayed records may be limited to those records that are still pending a delivery. A package addressee may select a record via mouse <b>142</b>, keyboard <b>140</b>, or the like.

0049At step <b>760</b>, processor <b>122</b> receives a selection of one of the records from the package addressee, which is interpreted by processor <b>122</b> as an authorization for package delivery.

0050At step <b>770</b>, processor <b>122</b> designates the delivery authorization status corresponding to the received selected record as delivery is acceptable. In this manner, a package addressee may authorize package delivery using a local area network rather than e-mail. Such an interface may be simpler to use than an e-mail interface and may provide increased security. Further, the addressee selects the record corresponding to the authorization, thereby relieving processor <b>122</b> from determining a matching record.

0051Alternatively, the authorization may be received from the addressee in the form of an e-mail message. A method for such a receipt of authorization is shown in FIG. <b>8</b>. At step <b>800</b>, computing device <b>120</b> receives an e-mail message from the package sender. At step <b>810</b>, processor <b>122</b> parses the e-mail message into segments. At step <b>820</b>, processor <b>122</b> determines a package identification from one of the parsed segments. At step <b>830</b>, processor <b>122</b> determines a sender identification from one of the parsed segments. At step <b>840</b>, processor <b>122</b> determines a projected delivery date from one of the parsed segments.

0052At step <b>850</b>, processor <b>122</b> receives a second e-mail message, the second e-mail message originating from the package addressee. At step <b>860</b>, processor <b>122</b> parses the second e-mail message into segments. At step <b>870</b>, processor <b>122</b> determines information from the parsed segments similar to that described in steps <b>720</b>, <b>730</b> and <b>740</b>. This information is used to match the addressee e-mail message to a sender e-mail message.

0053At step <b>880</b>, processor <b>122</b> compares the information determined in step <b>870</b> from the second e-mail message to information determined in steps <b>820</b>, <b>830</b>, and <b>840</b> from the first e-mail message. If the information from the first e-mail matches the information from the second e-mail, then the delivery authorization status of the record corresponding to the first e-mail is designated as delivery is acceptable, as shown in steps <b>860</b> and <b>866</b>. The delivery authorization status can be stored in a data table, as described in more detail below. If the package information does not match the parsed information from any e-mail message, then the delivery authorization status of the record corresponding to the first e-mail package is designated as delivery is not acceptable, as shown in steps <b>860</b> and <b>864</b>.

0054Delivery authorization statuses determined from e-mail messages and/or local area networks (such as described in <figref idref="DRAWINGS">FIGS. 7 and 8</figref>) may be stored in a data table for later comparison against package information. <figref idref="DRAWINGS">FIG. 9</figref> is a diagram of an illustrative data table <b>900</b> for storing such a delivery authorization status. Data table <b>900</b> comprises a record for each e-mail message from a sender. Each record comprises a plurality of fields for storing information parsed from the e-mail message. As shown in <figref idref="DRAWINGS">FIG. 9</figref>, record <b>910</b> comprises a first field <b>920</b> for storing a sender identification, a second field <b>922</b> for storing a package identification, a third field <b>924</b> for storing a projected delivery date, an optional fourth field <b>926</b> for storing an addressee identification, and a fifth field <b>928</b> for storing a delivery authorization status. The delivery authorization status field stores an indication that delivery is acceptable or an indication that delivery is not acceptable. With such a data table, package information can be compared against records to determine a delivery authorization status. Processor <b>122</b>, after determining a matching record, reads the authorization status field of the matching record. In this manner, both a sender and an addressee send an e-mail that, in combination, create a delivery authorization status that delivery is acceptable.

0055Thus the invention provides a system and method for increasing the security of package delivery by receiving and storing delivery authorization statuses and determining a delivery authorization status corresponding to a package before delivering the package to the package addressee.

0056Executable instructions for implementing aspects of the invention may be embodied in the form of program code (i.e., instructions) stored on a computer-readable medium, such as a magnetic, electrical, or optical storage medium, including without limitation a floppy diskette, CD-ROM, CD-RW, DVD-ROM, DVD-RAM, magnetic tape, flash memory, hard disk drive, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. The invention may also be embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, over a network, including the Internet or an intranet, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique apparatus that operates analogously to specific logic circuits.

0057It is noted that the foregoing has been provided merely for the purpose of explanation and are in no way to be construed as limiting of the invention. While the invention has been described with reference to illustrative embodiments, it is understood that the words which have been used herein are words of description and illustration, rather than words of limitation. Further, although the invention has been described herein with reference to particular structure, methods, materials, and embodiments, the invention is not intended to be limited to the particulars disclosed herein; rather, the invention extends to all structures, methods and uses that are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may effect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention, as defined by the appended claims.