WO2003044620A2

WO2003044620A2 - Systems and methods for detecting postage fraud using a unique mail piece indicium, reducing the size of postage indicia, and refunding postage

Info

Publication number: WO2003044620A2
Application number: PCT/US2002/033024
Authority: WO
Inventors: Scott Montgomery; Harry T. Whitehouse
Original assignee: PSI Systems Inc
Current assignee: PSI Systems Inc
Priority date: 2001-11-20
Filing date: 2002-10-14
Publication date: 2003-05-30
Anticipated expiration: 2004-05-20
Also published as: AU2002351501A1; WO2003044620A9; WO2003044620A3

Abstract

A method and system detects copy fraud by using a unique character string, e.g., a tracking ill that can be associated with a postage indicium and digitally signed to provide for a self-validating unique postage indicium. Once validated by the postal authority, the tracking ID within the unique postage indicium can be compared to the tracking ID's in all other postage indicia or to a standard tracking ID to ensure that tracking ID is indeed unique. Another improvement uses an indexing identifier (such as, e.g., a tracking ID, or a postage vendor ID, user account, and piece count) to decrease the size, or eliminate the use, of the postage indicium transmitted to an end user computer. An indexing identifier, rather than the postage indicium, is transmitted to the end user computer. Yet another improvement facilitates refunding unused postage. Information for a postage transaction, along with the tracking ID and delivery status, is stored. Unused postage exists when there is duplicative postage transactions or the mail piece was not delivered.

Description

TITLE

SYSTEMS AND METHODS FOR DETECTING POSTAGE FRAUD USING A UNIQUE MAIL PIECE LNDICIUM, REDUCING THE SIZE OF POSTAGE LNDICIA, AND

REFUNDING POSTAGE

FIELD OF THE INVENTION

The present inventions relate generally to electronic postage metering systems, and more particularly, personal computer (PC)-based postage systems.

BACKGROUND OF THE INVENTION In 1992, the United States Postal Service (USPS), acting largely on a formal

December 1991 proposal by the inventor, began investigating the feasibility of PC-based postage technology. The USPS hosted an exploratory meeting, inviting the inventor and the four existing conventional postage meter vendors (Pitney Bowes, Neopost (called Friden at the time), Ascom Hasler, and Franco Postalia) — firms that represented 100% of the US meter market at that time. Subsequent years saw a number of follow-on meetings, and the USPS eventually published a specification in the 1996 Federal Register outlining what the USPS called an "Information Based Postage Indicium Program (LBIP)." The requirements for the L LP are currently set forth in a document called "Information Based Indicium Program (LBIP) — Performance Criteria For Information-Based Indicia and Security Architecture for Open LBI Postage Evidencing Systems (PCLBI-O)," which was published on June 25, 1999 by the USPS, and which is fully and expressly incorporated herein by reference.

Two different types of PC-based postage architectures have evolved. The first type of architecture is a distributed postage indicia generation system, an example of which is detailed in U.S. Patent No. 5,319,562, entitled "System and Method for Purchase and Application of Postage Using Personal Computer," which is expressly and fully incorporated herein by reference. In this system, lump sums of postage are purchased and downloaded via a telecommunications link to a local secure computational device at the end user's location, hi USPS jargon, this device is called the Postal Secure Device (PSD). Typically, these postage transfers range from fifty to several thousand dollars. This amount is added to whatever balance remains in the PSD. The end user may then draw upon the balance in the PSD to produce postage indicia of varying amounts and service classes that are printed on mail pieces. As the mail pieces are individually metered (or in the case of the LBIP, created and simultaneously "metered"), the balance in the PSD is decremented by the transaction amount (e.g., 34 cents). The second type of architecture is a centralized postage indicia generation system, an example of which is detailed in U.S. Patent No. 6,005,945, entitled "System and Method for Dispensing Postage Based on Telephonic or Web Milli- Transactions," and which is fully and expressly incorporated herein by reference. In this system, the end user's account balance is securely stored in a centralized postage-issuing computer system, and the end user contacts the centralized postage-issuing computer system each and every time postage is to be applied to a mail piece.

Referring to Fig. 1, a typical LBIP mail piece 100 printed using either the distributed or the centralized postage indicia architecture is shown. The mail piece 100 comprises an envelope 102 on which various items are printed. A postage indicium 104 (in layperson's terms, a "stamp"), as applied by a computer printer, is located in the upper right hand corner of the envelope 102. The postage indicium 104 comprises a two-dimensional barcode 106 containing data relating to the mail piece 100 and the account holder, as well as human- readable information 108, e.g., the data, account number and amount of postage. The USPS has currently approved Portable Data File (PDF) and DataMatrix 2-D barcodes. Facing Identification Marks (FLM) 110 are located at the top of the envelope 102 above and to the left of the postage indicium 104, and are used by the USPS for the initial sortation of letter mail. The significance of the FLM 110 in letter mail processing is described in U.S. Patent No. 5,319,562. A return address 112 and destination address 114, which are self-evident, are printed on the face of the envelope 102. A POSTNET barcode 116, which is located beneath the destination address 114, represents the delivery point ZLP code of the destination address. The delivery point ZLP code is an 11 -digit code, only 9 of which are shown on the last line of the destination address 114. The last two digits of the delivery point ZIP code are generally derived from the last two digits of the street address number, which in the illustrated embodiment, is "47."

The amount of data in the postage indicium 104 is substantial and was designed with a distributed postage indicia generation system in mind. Significantly, in a distributed postage indicium generation architecture, the USPS has no detailed knowledge of how the postage is consumed. For example, for a hypothetical $100 of postage downloaded, the end user could create ten postage indicia of a $ 10 valuation, two hundred indicia of 50-cent valuation, or a combination thereof. In reality, the number of permutations is far greater. The USPS approach to this problem was to create a postage indicium with sufficient information, so that its authenticity could be determined in the absence of any other information. In other words, the USPS sought a "stand-alone" system that would be verifiable using only the human-readable information on the mail piece 100 and the data encoded in the two-dimensional barcode 106 of the postage indicium 104. In theory, no other "outside" information would be necessary. Table 1 sets forth the current JJBIP postage indicium contents, including the field name and byte size of each content item.

Table 1: Current IBIP Indicium Contents

Thus, the date (item #7) embedded in the barcode portion of the postage indicium 104 could be compared to the current date, as well as to the human-readable date. The postage amount (item #6) embedded in the barcode portion 106 of the postage indicium 104 could be compared to the human-readable postage amount, and for United States addresses, the delivery point ZLP code (item #9) embedded in the barcode portion 106 of the postage indicium 104 could be compared with the delivery address 114 printed on the mail piece 100. Should any of these "information pairs" show an inconsistency, the mail piece 100 would be immediately suspect and would be a candidate for further investigation.

The "veracity" of the invention in the barcode portion 106 of the postage indicium 104 was to be validated by public key cryptography, which was first disclosed by Diffie and Hellman in 1976, and essentially involves the use of a matched pair of public and private key components to either encrypt or digitally sign data. The keys are extraordinarily large integer values that have interesting cryptographic capabilities. Briefly, the public key component can be used to encrypt material, or verify a digital signature created by the corresponding private key. The private key component can be used only to create digital signatures that can be verified by the public key. Importantly, the public key component can be widely disseminated and in fact "published," because it is virtually impossible to infer the corresponding private key component. In cryptographic terms, it is "computationally infeasible" to infer the private key component given the public key component provided the modulus or size of the key is of sufficient size. Given the computational speed of computers available at the time of this writing, key sizes of 1024 or 2048 bits are considered highly secure.

In the USPS implementation, public key encryption is not used, but rather the private key component is used to digitally sign data. For example, as illustrated in Table 1, a private key component is used to digitally sign the first twelve items contained in the postage indicium 104 to generate a digital signature (item #13), which digital signature is then appended thereto. In the USPS model, each end user (i.e., meter account) has a unique public/private key pair assigned to him or her. The private key component is never divulged to the end user, but is stored securely in the PSD at the end user's site. The PSD digitally signs the data, i.e., the information associated with the postage indicium request. The matching public key component can then be used to validate the signature. A more detailed discussion of how public key cryptography is used in the LBLP is disclosed in U.S. Patent No. 6,005,945. Despite the commercial potential of the LBLP, it languished in uncertainty for several more years until two vendors were approved for beta testing in August of 1998. The companies, EStamp and Stamps.com, were relative newcomers to the PC-postage effort. Both firms finished beta testing approximately one year later (the fall of 1999). Pitney Bowes, the dominant conventional manufacturer, and Neopost were approved several months later. A host of high-value IPO's, based on vastly overstated market potential, funded the

EStamp and Stamps.com efforts during the late 1990's. Significantly, as the year 2001 draws to a close, EStamp has withdrawn from the postage business, Stamps.com is encountering several financial and legal problems, and the LBLP is in disarray. During their existence, the foregoing two firms consumed nearly one billion dollars in venture capital and public investment funds attempting to make PC-postage a viable business. In sum, two extraordinarily well-funded vendors have been driven out of the business, the established manufacturers of postage meters have curtailed or delayed their entry into the PC-Postage arena, and end users who were hopeful that this technology would save them time, money, and frustration were deeply disappointed. There are a host of factors that have contributed to the failure of the LBLP to date.

First, the USPS has insisted on developing a "perfect" security model before embarking on limited, alpha-level field-testing to identify "real world" problems. Second, the USPS has emphasized envelope printing, which, due to unyielding USPS mail processing requirements, proved to be very difficult to produce on desktop printers. This was especially true for courtesy reply envelopes provided by utilities and credit card firms, for example, because not only was the envelope difficult to feed and position, but there was a conflict in certain mail processing markings, especially the Facing Identification Code (FLM). Third, the focus on the consumer market with the promise of large numbers ended up costing the initial vendors large sums of money to acquire these customers, which did not provide sufficient financial returns. Fourth, the USPS was slow to appreciate and embrace a host of fraud prevention and detection enhancements inherent to centralized postage dispensing systems. Fifth, there is a lack of single piece discounts for LBLP postage users, even though the addressing and automation requirements imposed by the LBLP are comparable with other discount mailings (such as First Class Presort mail), and even though the discount was repeatedly recommended by the Postal Rates Commission.

Sixth, the public key infrastructure (PKI) approach adopted by the USPS has fallen short on many fronts. The first PKI-related problem surfaced immediately after the USPS published the initial LBLP specification in 1996. In order to provide a "stand-alone" verification system, barcode portion 106 of the postage indicium 104 would not only contain the items shown in Table 1, but would also have to carry the associated public key information for that account. The data in Table 1 is represented by 96 bytes. Because the public key component for a 1024 bit DSA key pair is 128 bytes long, however, adding the public key component for stand-alone verification caused the postage indicium 104 to be over twice the size of the current LBLP version. Comparable public key lengths are seen in the other USPS-approved key pairs such as RSA and elliptic curve.

But the postage indicium 104 needed to be still larger to achieve the goal of standalone verification, because the public key component itself must be verifiable. To understand why, suppose an adversary generated her own public/private key pair. This is a very easy process for an entry-level cryptographic programmer. Then she could create a mail piece, generate indicium data with fraudulent account information, digitally sign that information with a private key, and then append the public key to the end of the indicium data. To a verifying party in a stand-alone environment, everything would seem to be in order if one trusted the public key component.

This problem can be solved by using a Certificate Authority (CA), which is a very trusted party (e.g., a government agency or a private firm such as Verisign) who will accept a public key component generated by a third party, investigate that party to ascertain that they are who they say they are, and upon approval, digitally sign the public key with a master private key maintained by that CA. Thus, if the verifying party has the public key component of the CA available in the stand-alone verification system, it can be used to verify the digital signature on the account-specific public key component. If that verification is successful, the account-specific public key can be used to authenticate the postage indicium 104.

The advantage of this approach is that a single master CA public key can be used to ascertain the veracity of millions of other public keys. The disadvantage is that not only is a 128-byte account-specific public key required in the postage indicium 104, but the digital signature generated by the CA adds another 40 to 128 bytes of information. In addition, the CA typically embeds other information in the signed package, including the name of the party and the range of dates for which the account-specific public key is valid. The complete package is called a digital certificate and can grow to a size of several thousand bytes depending upon how many intermediate CA's are involved. The indicium data stream initially proposed by the USPS approached 500 bytes, and the associated two-dimensional bar code portion 106 of the postage indicium 104 covered approximately 25% of the area of a typical commercial #10 envelope. The mailing community and potential LBLP vendors resoundingly rejected this as completely unworkable.

The inventor (and presumably other potential LBLP vendors) proposed an alternative approach to the USPS, which brought the postage indicium down to the current 100 bytes. Rather than including a large digital certificate, a unique 4-byte numerical key pair ID (item #3 in Table 1) would be included instead. The key pair LD then references a complete CA- signed, account-specific public key that the USPS can distribute to field verification staff via CD-ROM or other means. Essentially, each verification staff member would have a database of CA-signed public keys indexed by a key pair LD. When scanning postage indicium 104, the key pair LD would be used to look up the appropriate public key, and that key would be used to verify the digital signature in the postage indicium 104. While solving the space problem on the mail piece, the inclusion of a key pair JD within the postage indicium 104 did present the USPS with a new problem of distributing public keys to its field staff. This proved to be a daunting task, as some vendors were signing up thousands of new end users per month, each of whom represented a public key that needed to be distributed to every field verifier if the goal of stand-alone verification was to be achieved. Thus, the second major PKI-related problem encountered by the USPS and the LBLP vendors was the cost and logistical issues associated with managing hundreds of thousands, if not millions, of key pairs. LBLP vendors were charged for each key pair certified by the USPS CA. The cost, $8.00 US, was substantial for a PC postage service that had a price point as low as $ 1.99/month. Furthermore, the USPS had to maintain the database of public keys, deal with the revocation and reissuing of public keys as they expired, and handle other issues associated with the PKI.

In 1998, the inventor suggested another approach to key management in centralized postage systems, which is disclosed in U.S. Patent No. 6,005,945. Stated briefly, this approach uses a single key pair to service the entire user community for a given centralized postage vendor. The key pair might change daily, weekly or monthly for security reasons, but the net effect would be that only dozens of keys would be employed as compared to millions. We hasten to reiterate that this approach is feasible only when the postage indicia are created at the centralized server cluster run by the postage vendor. That is, the safety of the private key can be assured since it is in the possession of the trusted postage vendor, and not the end user. It should be noted that even the centralized system postage vendor does not have direct knowledge of the private key material. USPS design guidelines require that private key material can only be presented "in the clear" within the confines of a FLPS-140 coprocessor device at the centralized server cluster. This is to prevent "insider attacks" from compromising the private signing key material.

Distributed-architecture LBLP systems that use a local "vault" attached to a PC at an end user's site, or newer stand-alone meters that create signed LBLP-like indicia, must continue to have a unique, dedicated key pair in each remote PSD. If a single key pair was used, and an end user compromised just one of those devices, that key could be distributed widely and used to create millions of fraudulent postage indicia.

In 1Q2001, the USPS permitted the inventor to institute the key management plan under a three-month beta test, and later officially notified all LBI centralized postage vendors that they too could employ this approach. The net result is there will be far fewer public keys to maintain for the USPS verification operations, and it is considerably more practical to perform stand-alone verification. Despite these improvements, the inventor believes that the stand-alone verification system can be eliminated without degrading postage security.

Another problem with the self- verifying LBI indicium concept is that it does a poor job of protecting against the fraudulent use of copies of valid postage indicia. Duplicate mail pieces have the potential to create substantial dollar losses to the USPS, particularly when high postage value packages are involved. Let us consider the following fraud scenario. A shipper has 70 pounds of goods to ship to a client, and he wishes to use Priority Mail. Roughly speaking, the USPS charges about $110 to transport 70 pounds cross-country via Priority Mail. If the goods can be subdivided into smaller packages, the shipper could easily perform the following attack. The shipper would create a postage-bearing shipping label for 35 pounds (approximately $52 in postage). The shipper would then create a second copy of this label, either by using a photocopy process, by interrupting the printer in mid-stream, causing it to think it must reprint a second version from the data in the printer memory, or by using a commonly available software package, such as Adobe Exchange, to create a PDF image of the label (rather than a print image), and then to print the resulting PDF image file more than once. Note that PC-based postage indicia do not use any special inks (such as the fluorescent-traced red ink used in conventional postage meters), so they are particularly easy to replicate. The shipper would then divide the shipment into two 35-pound cartons and apply a postage label to each carton (one an original, and the other a copy).

This would effectively defraud the USPS of over $50. If a USPS inspector happened to intercept either package and perform a scan of the barcode portion of the postage indicium, the information would be consistent on each label. The amount of postage in human-readable and barcode format would match. The date would be reasonable. The destination ZIP +4+2 would match that on the physical destination address. The only way the verifier could detect the fraud is by intercepting both packages simultaneously and scanning them side-by-side. The inspector would hopefully notice that the ascending/descending balances (c.f. items 5 and 11 in Table 1) were the same in each indicium — a clear indication of fraud.

The USPS has seemingly discounted the impact of "copy fraud." The USPS recognizes that, as with conventional postage, it can only perform spot statistical testing on the mail stream. But the USPS has also been somewhat "envelope-centric" in their thinking. That is, the USPS feels that an attacker would find little value in sending two envelopes to the same destination, and that the dollar amount of fraud would be on the order of 34 cents. The inventor believes that the future of PC-based postage is not with envelopes, but with high value, expedited packages. Letter mail (e.g., correspondence, statements, and invoices) is being rapidly replaced with electronic communications, and in the not-too-distant future, packages will dominate the USPS environment. This trend is likely to be accelerated given the anthrax attacks of 3Q2001. Therefore, it is believed that the USPS is underestimating the dollar value of this fraud threat. The inventor believes that by modifying the postage indicium as discussed herein, copy fraud can be further reduced if not effectively eliminated.

This is an appropriate time to discuss the "uniqueness" of the information in indicia. As we have seen in the previous example, using the digitally signed ZLP+4+2 and cross checking this value with the ZIP+4+2 shown in the human readable address, is not a fool proof method to detect copy fraud. The ZLP+4+2 of a given delivery address is something that can appear in an indicium for a given account holder on many occasions. Insofar as the indicium is concerned it is not a particularly unique value. What is unique in the originally proposed and used USPS indicium as the combination of the account number, the ascending register, and the descending register (balance) for that account. For instance, the concatenation of these three values should always result in a unique numerical string in an indicium. Put another way, if one finds two indicia with the identical concatenated value, this is clear evidence that at least one indicium is fraudulent.

The descending register in a given postage account is simply the amount of postage available to create indicia. It is effectively the "remaining balance". The ascending register is the lifetime sum of all postage indicia created within that account. When an indicium is created, the descending register is decremented by the indicium value and the ascending register is incremented. Eventually, the meter account will run out of funds (the descending register approaches zero) and the account hold can purchase more postage from the postal authority. A postal purchase results in a matching increase in the descending register. The ascending register is not impacted by a postage purchase.

One can see that for a given account, a given descending register (say $5.00) may occur many times over the lifetime of the account. However, a situation where the ascending register is $505 and the descending register is $104 will only occur once (if at all) in a given account lifetime. This is because the ascending register is ever increasing as the life of the meter goes on. The USPS has based some portion of its fraud detection protocol on the "uniqueness" provided by the ascending/descending register combination for a given account. But as an index for uniqueness, this is a poor choice from an operation standpoint. The combination of the two register values does not result in a continuous number series. The registers are tracked to the 1/10^th of a cent (a mil), and a typical minimum change in the register values is 340 mils (a 34 cent First Class postage indicium). The next indicium might be a high- postage- value package and result in a register change of 20000 mils ($20,00). Again, the combination of ascending/descending registers will be unique for a given account, but this "index of uniqueness" is far from optimal. The index will have large gaps in the number sequence, and the gap sizes will be variable.

A seventh problem that has contributed to the failure of the LBLP is the assumption that all printing-related problems could be controlled by "perfect" vendor software and therefore, a staunch refusal to offer a refund procedure for failed or partially-printed mail pieces. It should be stressed that PC-postage is different from printing other types of shipping labels (e.g., UPS or FedEx) in that misprints are, in effect, losses of "money." If a shipper misprints a UPS shipping label from a shipping software package or web site, another one can be reprinted and placed on the package with no negative financial impact to the shipper. This is because the UPS business model charges the shipper when the package enters the UPS shipping stream and is scanned. The UPS label has no inherent "value" until it enters the UPS delivery system. The USPS, however, as do many postal agencies worldwide, assumes that the postage is paid before the package enters the shipping stream.

The current USPS refund procedures for misprinted mail pieces are overly strict and reflect a mindset formed over decades of supporting conventional meter technologies. Refunds are possible, but only if one presents a physical specimen. For instance, if a mailer creates a meter strip using a conventional postage meter (or prints the postage indicium directly on a mail piece), and decides not to use that postage indicium, the postage indicium can be taken to a local post office for a refund of anywhere from 90% to 100% of the postage value.

For PC-postage vendors, the procedures are somewhat different, although the criteria are the same. If the PC-postage user creates a readable mail piece (specifically, the postage indicium must be scannable), it may be submitted to the PC-postage vendor for a refund. The vendor, in turn, applies to the USPS for a refund. The overall process is complex, time- consuming, and very costly to operate. It also requires that USPS auditors make field visits to the PC-postage vendors to examine all of the physical specimens before the refund can be authorized.

If the end-user is unlucky enough to have attempted to print a mail piece that resulted in a deduction to the account balance, but has no physical evidence of this mail piece, the current USPS rules prohibit a refund. Unfortunately, this situation is not uncommon. The mail piece stock (e.g., label or envelope) can misfeed, causing only a portion of the indicium to print on the paper. Or if the PC is low on Graphic Display Interface (GDI) or memory resources, or has crashed for any reason, the printer driver may fail to render the two- dimensional barcode image. Or if the job is sent to a network printer, it is possible that another user/operator can flush the PC-postage print job by manipulating the printer queue or control panel, thus resulting in the unavailability of the specimen.

As discouraging as all the LBLP-related problems may seem, the inventor feels that PC-postage can be made viable by incorporating novel, yet easily implementable, design elements into the LBLP base design SUMMARY OF THE INVENTION

The inventions provide improvements in detecting postage fraud using a unique mail piece indicium, reducing the size of postage indicia, and/or refunding postage.

A first improvement of an improved postage system and method uses a unique character string, such as, e.g., a tracking ID to, among other things, facilitate the detection of copy fraud. This tracking LD can be associated with a postage indicium and digitally signed to provide for a self-validating, unique postage indicium. The self-validating postage indicium can then be applied to a mail piece, e.g., a package, which may then be processed from the sender to the recipient through a postal authority, e.g., the USPS. For example, during the delivery process for the mail piece, the postal authority can scan all of the postage indicium or simply spot check samples. Once a given indicium's digital signature is validated by the postal authority using, e.g., PKI methods, the unique string contained within the indicium can be used in a variety of ways for fraud detection.

For package mail that contains a unique delivery tracking LD, the ideal unique character string for the indicium is the tracking JD itself. If 100% of the packages bearing a postage indicium have this postage indicium scanned, the tracking JD within the unique postage indicium can be compared in a computer operated by the postal authority to the tracking LD's in all other scanned and recorded postage indicia to ensure that the tracking LD is indeed unique and has not been duplicated. If the self- validating postage indicia on tracked mail pieces are only spot-checked, the fracking JD obtained from the validated postage indicium can be compared to a standard tracking JD found elsewhere on the mail piece in, e.g., human readable and/or barcode form.

5 Unlike the two dimension LBI postage indicia barcodes, these standard tracking LD's

(which are generally represented in simpler one dimensional barcodes, such as Code 128, Code 39, etc) are typically scanned 100% of the time. This scanning is a result of the normal processing that the postal authority implements to keep track of mail pieces (typically packages), and thus any copyist that duplicates the postage indicium would not be able to

10 correspondingly copy the standard tracking LD's without detection of duplicated tracking LD's or at least a tracking JD that is outside a normal range of tracking LD's. Thus, a comparison between the tracking JD found in the self-validating postage indicium and the standard tracking LD would reveal a discrepancy and thus possible fraud. This approach would be very effective in the case of two packages going from the same sender to the same destination

15_. address. While both packages would have the same delivery ZLP+4+2 (a potential copy attack described earlier in this specification), the packages would have different tracking LD's. The copyist would be further frustrated in his attempt to copy an existing valid indicium and tracking LD pair, and use that matched pair on another package altogether. This type of fraud would very likely be detected by the routine delivery scans of the tracking JD performed by 0 the postal authority. hi accordance with a first, separate aspect of this first improvement, an improved method of providing a unique postage indicium within a postal system (e.g., the USPS) is provided. The method comprises generating a unique postage indicium having a character string (such as, e.g., a fracking LD) that is unique within the postal system. The tracking LD 5 can be obtained from a single database to ensure its uniqueness. In addition to the unique tracking JD, the postage indicium can contain a number of other items, such as, e.g., indicia version number, algorithm identification, certificate serial number, device identification, ascending register, postage, date of mailing, originating zip code, software identification, descending register, and rate category. The method further comprises deriving a digital 0 signature from the unique tracking LD, and associating the digital signature with the unique postage indicium to generate a self-validating unique postage indicium. In the preferred method, the digital signature is generated by applying a private key to the unique postage indicium. The digital signature is then attached, e.g., by appending, to the unique postage indicium. This self-validating unique postage indicium can then be applied to a mail piece (such as, e.g., a package or envelope) in a barcode format. The unique tracking JD can also be applied to the mail piece independently of the self- validating unique postage indicium, as is the typical case with tracked packages. In accordance with a second separate aspect of this first improvement, a method of detecting postal fraud in a postal system (such as, e.g., the USPS) is provided. The method comprises receiving a plurality of mail pieces within the postal system, each carrying a self- validating postage indicium having a character string (such as, e.g., a tracking JD) and a digital signature derived from a data stream that includes the tracking JD, and optionally other postage-related data.

The method further comprises reading each self- validating postage indicium to obtain the postage indicium and digital signature, validating each postage indicium by determining if the digital signature is consistent with the tracking JD, and if applicable, the associated indicium data, and comparing all of the tracking LD's obtained system-wide from the postage indicia. Thus, postal fraud can be detected if two of the unique character strings (e.g. tracking LD's) match. In the preferred method, each self-validating postage indicium is embodied in a two dimensional barcode format that can be read with a barcode reader. Each digital signature can be generated with a private key, in which case, the postage indicium authentication comprises applying a corresponding public key to each digital signature. In accordance with a third separate aspect of this first improvement, a method of detecting postal fraud in a postal system (such as, e.g., the USPS) is provided. The method comprises receiving a mail piece within the postal system, wherein the mail piece carries a self-validating postage indicium having a character string (such as, e.g., a fracking ID), and a digital signature derived from a data stream that includes the tracking JD, and optionally other postage-related data. The mail piece further carries an expected representation of the same tracking JD independent of the self- validating postage indicium. It is customary that this latter representation consists of a human readable string plus a one-dimensional barcode representation of that string. The method further comprises reading the self- validating postage indicium to obtain the postage indicium data and associated digital signature, validating the postage indicium data by determining if the digital signature is consistent with the tracking JD, and comparing the validated fracking LD obtained from the postage indicium to the tracking JD found elsewhere on the mail piece. Thus, postal fraud can be detected if the tracking LD obtained from the postage indicium does not match the expected representation of the tracking JD found elsewhere on the mail piece, indicating that the postage indicium has been duplicated. Postal fraud can further be detected if two or more of the tracking LD's found on two or more mail pieces match each other, indicating that the tracking LD's have been duplicated to match the duplicated postage indicium. In the preferred method, each self-validating postage indicium is embodied in a barcode format that can be read with a barcode reader. Each digital signature can be generated with a private component of a key pair, in which case, the postage indicium authentication comprises applying a corresponding public key to each digital signature.

In accordance with a fourth separate aspect of this first improvement, a method of providing postage indicia for use in a postal system is provided. The method comprises generating a plurality of unique postage indicia having a plurality of character strings (such as, e.g., tracking LD's) unique within the postal system, generating a plurality of digital signatures of the plurality of unique tracking LD's, and generating a plurality of self- validating unique postage indicia by associating the plurality of digital signatures with the plurality of unique postage indicia.

In one preferred method, all of these steps are performed in a centralized postage- issuing computer system that services a plurality of user accounts. In this case, the method can further comprise receiving a plurality of postage indicium requests at the centralized postage-issuing computer system from a plurality of end user computers, processing the requests at the centralized postage-issuing computer system, and transmitting the resulting self- validating unique postage indicia from the centralized postage-issuing computer system to the end user computers. The postage indicium requests may be embodied in a variety of formats, but in the preferred method are embodied in single data streams. The centralized postage-issuing computer system can obtain the unique tracking numbers from various sources, but in the preferred method are obtained either indirectly from a master tracking computer system via the end user computers or directly from the master fracking computer system. In another preferred method, all of these steps are performed in the end user computers, in which case, the tracking numbers can be obtained directly from the master tracking computer system. In accordance with a fifth separate aspect of this first improvement, a method of providing a postage indicium for use in a postal system (such as, e.g., USPS). The method comprises receiving a unique identifier request from an end user computer, and transmitting a unique identifier (such as, e.g., a tracking number) to the end user computer in response to the unique identifier request. The unique identifier may take a variety of forms, e.g., a single unique character string such as a tracking number, or two or more character strings such as a postage vendor LD, user account number, and piece count. The method further comprises receiving a postage indicium request from an end user computer, generating a unique postage indicium carrying the unique identifier, deriving a digital signature from the unique identifier, generating a self- validating unique postage indicium by associating the digital signature with the unique postage indicium, and transmitting the self-validating unique postage indicium independently from the unique identifier. The unique identifier and self- validating postage indicium can then be applied to a mail piece by the end user computer. In one preferred method, all of the steps are performed in a centralized postage- issuing computer system that services a plurality of user accounts. In this case, the method can further comprise transmitting another unique identifier request from the centralized postage-issuing computer system to the master fracking computer system in response to receipt of the unique identifier request from the end user computer, and receiving the unique identifier at the centralized postage-issuing computer system from a master tracking computer system. Alternatively, the received unique identifier can be stored in the centralized postage-issuing computer system prior to receiving the unique identifier request from the end user computer. In another preferred method, all of the steps are performed in the centralized postage-issuing computer system, with the exception of the receipt of the unique identifier request and the transmission of the unique identifier, which are performed in the master tracking computer system. In this case, the unique identifier received by the end user computer is transmitted to the centralized postage-issuing computer system.

In accordance with a sixth separate aspect of this first improvement, a postage indicia generation system for implementation with a postal system is provided. The system comprises an end user computer, a centralized postage-issuing computer system, and a communications link connecting the end user computer with the centralized postage-issuing computer system. The end user computer is configured for transmitting a postage indicium request to the centralized postage-issuing computer system over the communications link, and the centralized postage-issuing computer system is configured for generating and transmitting a self-validating unique postage indicium to the end user computer over the communications link. The self-validating unique postage indicium contains a character string (such as, e.g., a fracking LD) unique to the postal system and a digital signature that is derived from the tracking JD, and optionally other postage-related data. In a preferred embodiment, the system may further include a master fracking computer system and another communications link that connects the centralized postage- issuing computer system with the master tracking computer system. In this case, the master tracking computer system can be configured for transmitting the fracking JD to the centralized postage-issuing computer system over the other communications link. The tracking JD may be transmitted to the centralized postage-issuing computer system in response to a unique identifier request from the cenfralized postage-issuing computer system, or alternatively may be periodically transmitted to the centralized postage-issuing computer system with a pool of unassigned tracking LD's, which are then stored in a database prior to receiving the postage indicium request from the end user computer. In another preferred embodiment, the system may further include a master tracking computer system and another communications link that connects the master fracking computer to the end user computer. In this case, the end user computer can be configured for transmitting a unique identifier request to the master tracking computer system over the other communications link, for receiving the unique character string from the master tracking computer system over the other communications link, and for transmitting the unique character string to the centralized postage-issuing computer system over the communications link.

In accordance with a seventh separate aspect of this first improvement, a centralized postage-issuing computer system for issuing postage indicia within a postal system is provided. The centralized postage-issuing computer system comprises data processing circuitry, a database storing a plurality of user accounts, and a communications module, when executed by the data processing circuitry, configured for receiving a postage indicium request from an end user computer. In a preferred embodiment, the communications module may further be configured for transmitting the self- validating unique postage indicium to the end user computer, and for receiving the tracking LD from a master tracking computer system, or alternatively from the end user computer.

The centralized postage-issuing computer system further comprises a postage indicium generation module, when executed by the data processing circuitry, configured for generating a self-validating unique postage indicium in response to the postage indicium request. The self-validating unique postage indicium contains a character string (such as, e.g., a tracking JD) unique to the postal system and a digital signature derived from the unique fracking LD. hi generating the postage indicium, the postage indicium generation module may comprise a unique postage indicium generation submodule for generating the unique postage indicium, a digital signature generation submodule for generating the digital signature, and an association submodule for associating the digital signature with the unique postage indicia to generate the self-validating unique postage indicium.

A second improvement uses an indexing identifier (such as, e.g., a fracking JD or the combination of a postage vendor LD, user account, and piece count) to decrease the size of the postage indicium transmitted to an end user computer, or eliminate fransmission of the postage indicium altogether. When the postage indicium for the end user computer is generated, it is stored, and the indexing identifier, rather than the postage indicium, is transmitted to the end user computer. The indexing identifier is applied to a mail piece, which is then scanned by the postal authority. The postal authority can obtain the stored postage indicium by reference to the indexing identifier. In this manner, the postal authority has access to the postage indicium without having to apply it to the mail piece.

In accordance with a first separate aspect of this second improvement, a method of indexing a postage indicium within a centralized postage-issuing computer system having a plurality of user accounts is provided. The method comprises generating a postage indicium associated with a mail piece, associating an indexing identifier with the postage indicium, and storing the indexed postage indicium within a database. The indexing identifier can be embodied in a variety of forms, but in the preferred method is unique within a postal service (such as, e.g., the USPS) and comprises a postage vendor JD, user account number, and piece count, or alternatively, a unique fracking LD. The postage indicium may comprise a variety of items, such as, e.g., postage amount, date and time of postage information creation, service class, optional data advance, and delivery zip code. ι

To protect the integrity of the postage indicium stored in the centralized postage- issuing computer system, the method preferably comprises deriving a digital signature from the postage indicium, associating the digital signature with the postage indicium to generate an indexed self- validating postage indicium, and storing the indexed self- validating postage indicium within the centralized postage-issuing computer system. The digital signature may be generated by applying a private key to the postage indicium, and the digital signature can be associated with the postage indicium by attaching it thereto. The digital signing of the postage indicium can be further protected using a physically secure coprocessor device to perform this operation. In the preferred method, an indexing identifier request is received from an end user computer, and the indexing identifier is transmitted to the end user computer. The indexing identifier can then be applied to a mail piece. When the mail piece is being inspected by the postal authority, the method may further comprise receiving a postage indicium request containing the indexing identifier from the postal authority, retrieving the indexed postage indicium from the database based on the received indexing identifier, and transmitting the indexed postage indicium to the postal authority.

In accordance with a second separate aspect of this second improvement, a method of validating postage for a postal service is provided. The method comprises generating a postage indicium associated with a mail piece, associating an indexing identifier with the postage indicium, and storing the indexed postage indicium within a database. The method further comprises applying the indexing identifier to the mail piece, reading the indexing identifier on the mail piece, and retrieving the indexed postage indicium from the database based on the indexing identifier. The indexing identifier can be applied to the mail piece in a variety of formats, but in the preferred method is applied in a barcode format (such as, e.g., a two-dimensional barcode or even a one-dimensional barcode), and read using a barcode reader, or applied in a human-readable format, and read using an optical character reader. hi accordance with a third separate aspect of this second improvement, a centralized postage-issuing computer system for indexing postage indicia for a plurality of user accounts within a postal system is provided. The cenfralized postage-issuing computer system comprises data processing circuitry, a database, a postage indicium generation module, when executed by the data processing circuitry, configured for generating a postage indicium, an indexing module, when executed by the data processing circuitry, configured for associating an indexing identifier with the postage indicium, and a database management module, when executed by the data processing circuitry, configured for storing the indexed postage indicium within the database, and for retrieving the indexed postage indicium from the database based on the indexing identifier.

The postage indicium may be self-validating. In generating the self-validating postage indicium, the postage indicium generation module may comprise a postage indicium generation submodule for generating the postage indicium, a digital signature generation submodule for generating the digital signature; and an association submodule for associating the digital signature with the postage indicium to generate the self-validating indexed postage indicium. To provide additional security, key cryptographic operations may be accomplished by means of a physically secure coprocessor device. In the preferred embodiment, the centralized postage-issuing computer system comprises a communications module, when executed by the data processing circuitry, configured for receiving an indexing identifier request from an end user computer, and for transmitting the indexing identifier to the end user computer. The communications module may also be for receiving a postage indicium request containing the indexing identifier from a postal authority, and for transmitting the retrieved indexed postage indicium to the postal authority.

In accordance with a fourth separate aspect of this second improvement, a method of validating postage in a postal system is provided. The method comprises receiving a postage indicium request from a postal authority (such as, e.g., the USPS), wherein the postage indicium carries an indexing identifier and is associated with a mail piece inspected by the postage authority. The method further comprises retrieving an indexed postage indicium from a database based on the received indexing identifier, and transmitting the postage indicium to the postal authority. The indexed postage indicium may be self-validating postage indicium that is created within a physically secure coprocessor device. As such, these signed indicia may be safely stored in a conventional database for later access and signature verification.

In accordance with a fifth separate aspect of this second improvement, the indexing identifier can be used to request and receive sender identification information to verify that the sender of a received mail piece is a trusted individual or entity.

A third improvement uses a tracking LD to facilitate the refunding of unused postage. Information for a postage transaction, along with the tracking LD and an associated delivery status, is stored. This delivery status is updated when the mail piece carrying the tracking JD is delivered. Unused postage can be confirmed by retrieving the stored postage transaction information and determining from that whether there are duplicative postage fransactions. The delivery statuses for the duplicative postage transactions can then be reviewed to determine whether the mail pieces associated with these postage transactions have been delivered. If not, one of the postage transactions maybe refunded.

In accordance with a first separate aspect of this third improvement, a method of refunding postage is provided. The method comprises storing information for a postage transaction in a database, wherein the postage transaction information comprises a tracking LD and an associated delivery status. The postage transaction information may also comprise a postage transaction date, postage transaction time, destination zip code, service class, postage amount, and mail piece weight. The method further comprises receiving a postage refund inquiry, e.g., from an account administrator or the end user, and retrieving the postage transaction information from the database in response to the postage refund inquiry. A postage may then be refunded based on the retrieved postage transaction information. For example, the postage may be refunded only if the retrieved delivery status indicates that a mail piece associated with the tracking JD has not been delivered, and not refunded if the retrieved delivery status indicates that a mail piece associated with the fracking JD has been delivered. The postage transaction information may be displayed to facilitate the refunding process. In the preferred method, confirmatory delivery status information associated with the tracking LD is received from, e.g., a postal authority, and the delivery status in the database is updated with the confirmatory delivery status information.

In accordance with a second separate aspect of this third improvement, a method of refunding postage is provided. The method comprises storing information for a plurality of postage transactions in a database, wherein the information for each postage fransaction comprises a tracking LD, postage fransaction date, and delivery status associated with the tracking LD. In the preferred method, confirmatory delivery status information associated with the plurality of tracking LD's may be received from a postal authority, and the plurality of delivery statuses in the database may be updated with the confirmatory delivery status information. The method further comprises associating the stored postage transaction information with a user account, receiving a postage refund inquiry for the user account (e.g., from an account administrator or end user), and retrieving the postage transaction information from the database in response to the postage refund inquiry. The method further comprises refunding the postage for a first postage fransaction only if the delivery status for the first postage transaction indicates that a mail piece associated with the tracking JD for the first postage transaction has not been delivered, and the postage transaction dates for the first and second postage transactions are the same. The information for each postage transaction may comprise a destination zip code, service class, and postage amount, in which case, the postage may be refunded only if the destination zip codes, service classes, and postage amounts for the first and second postage transactions are the same.

In accordance with a third separate aspect of this third improvement, a method of providing status for a plurality of mail pieces tracked by a postal authority is provided. The method comprises storing information for a plurality of postage fransactions in a database, wherein the information for each postage transaction comprises a tracking JD and an associated delivery status. The method further comprises receiving confirmatory delivery status information from the postal authority, and updating the plurality of delivery statuses in the database with the confirmatory delivery status information. In the preferred method, the stored postage fransaction information is associated with a plurality of user accounts.

In accordance with a fourth separate aspect of this third improvement, a centralized postage-issuing computer system for providing status for a plurality of mail pieces tracked by a postal service is provided. The cenfralized postage-issuing computer system comprises data processing circuitry, a database, a communications module, when executed by the data processing circuitry, configured for receiving confirmatory delivery status information from a master tracking computer system, and a database management module, when executed by the data processing circuitry, configured for storing information for a plurality of postage transactions in a database. The information for each postage transaction comprises a tracking JD and an associated delivery status. The database management module is further configured for updating the delivery status with the confirmatory delivery status information. The database management module may further associate the stored postage transaction information with a plurality of user accounts. In the preferred embodiment, the central computer comprises a delivery status request module, when executed by the data processing circuitry, configured for generating a request for the confirmatory delivery status information. In this case, the communications module may transmit the request to the master tracking computer system.

In accordance with a fifth separate aspect of this third improvement, a method of determining whether issued postage has been used is provided. The method comprises storing information for a plurality of postage transactions in a database, wherein the information for each postage transaction comprises one or more postage fransaction items (such as, e.g., a postage fransaction date, destination zip code, service class, and postage amount), a tracking JD and an associated delivery status. The method further comprises associating the postage transaction information with a user account, receiving an inquiry for duplicative postage transactions from, e.g., an account administrator or end user, retrieving the postage fransaction information from the database, selecting the postage transactions in which the one or more postage transaction items are identical, and determining if any of the delivery statuses for the selected postage transactions indicate that a mail piece has been delivered. The method may further comprise determining that issued postage is unused if any of the delivery statuses for the selected postage fransactions indicate that a mail piece has been delivered. In the preferred method, confirmatory delivery status information is received from, e.g., a postal authority, and the delivery statuses in the database are updated with the confirmatory delivery status information. In accordance with a sixth separate aspect of this third improvement, a centralized postage-issuing computer system for determining whether issued postage has been used is provided. The centralized postage-issuing computer system comprises data processing circuitry, a database, a communications module, when executed by the data processing circuitry, configured for receiving an inquiry for duplicative postage transactions, and a database management module, when executed by the data processing circuitry, configured for storing information for a plurality of postage transactions in a database, and associating the postage transaction information with a user account. The centralized postage-issuing computer system further comprises a filtering module, when executed by the data processing circuitry, configured for selecting the postage transactions in which the one or more postage transaction items are identical, and determining if any of the delivery statuses for the selected postage transactions indicate that a mail piece has been delivered. In the preferred embodiment, a filtering module is further configured for determining that issued postage is unused if any of the delivery statuses for the selected postage transactions indicates that a mail piece has been delivered. The communications module may further be for receiving confirmatory delivery status information, and the database management module may further be for updating the delivery statuses with the confirmatory delivery status information.

Other and further aspects and features of the inventions will become apparent from the following drawings and detailed description. The inventions do not require the presence of all of the separate aspects or all of the separate improvements. Thus, the inventions may combine any one or more of the separate aspects, as well as combine any one or more of the separate improvements.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to better appreciate how the above-recited and other advantages and objects of the present inventions are obtained, a more particular description of the present inventions briefly described above will be rendered by reference to specific embodiments thereof, which are illustrated in the accompanying drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

Fig. 1 is top view of a prior art LBLP mail piece;

Fig. 2 is a top view of a USPS Priority Mail postage label constructed in accordance with the present inventions;

Fig. 3 is a block diagram of a first postal system constructed in accordance with the present inventions, wherein the first postal system utilizes unique tracking LD's to detect postal copy fraud;

Fig. 4 is a block diagram of an end user computer used in the first postal system of Fig. 3;

Fig. 5 is a block diagram of a cenfralized postage-issuing computer system used in the first postal system of Fig. 3;

Fig. 6 is a block diagram of another cenfralized postage-issuing computer system used in the first postal system of Fig. 3; Fig. 7 is a block diagram of a master fracking computer system used in the first postal system of Fig. 3;

Fig. 8 is a block diagram of a postage validation computer system used in the first postal system of Fig. 3;

Fig. 9 is a flow diagram illustrating a procedure for indirectly issuing a fracking LO from the master fracking computer system of Fig. 7 to the end user computer of Fig. 4 via the centralized postage-issuing computer system of Fig. 5;

Fig. 10 is a flow diagram illustrating a procedure for issuing a tracking JD from the centralized postage-issuing computer system of Fig. 6 to the end user computer of Fig. 4;

Fig. 11 is a flow diagram illustrating a procedure for downloading unassigned tracking LD's from the master computer fracking system of Fig. 7 into the centralized postage- issuing computer system of Fig. 6 and for uploading postage information from the centralized postage-issuing computer system to the master tracking computer system;

Fig. 12 is a flow diagram illustrating a procedure for directly issuing a tracking JD from the master tracking computer system of Fig. 7 to the end user computer of Fig. 4; Fig. 13 is a flow diagram illustrating a procedure for dispensing a self- validating unique postage indicium from the centralized postage-issuing computer system of Figs. 5, 6, or 33 to the end user computer of Fig. 4;

Fig. 14 is a flow diagram illustrating a procedure for validating the postage on a mail piece using the postage validation computer system of Fig. 8;

Fig. 15 is a block diagram of a second postal system constructed in accordance with the present inventions, wherein the second postal system utilizes indexing identifiers to reduce or eliminate the size of the postage indicium;

Fig. 16 is a block diagram of an end user computer used in the second postal system of Fig. 15;

Fig. 17 is a block diagram of a centralized postage-issuing computer system used in the second postal system of Fig. 15;

Fig. 18 is a block diagram of a postage validation computer system used in the second postal system of Fig. 15; Fig. 19 is a top view of an indexing identifier represented as a two-dimensional barcode;

Fig. 20 is a top view of an indexing identifier represented as a one-dimensional Code 128 barcode;

Fig. 21 is a top view of an indexing identifier represented as a one-dimensional POSTNET or PLANET barcode;

Fig. 22 is a top view of an indexing identifier represented as numerical data;

Fig. 23 is a flow diagram illustrating a procedure for indexing a postage indicium and applying an indexed identifier to a label;

Fig. 24 is a flow diagram illustrating a procedure for validating the postage on a mail piece using the indexed identifier;

Fig. 25 is a block diagram of a third postal system constructed in accordance with the present inventions, wherein the third postal system utilizes a tracking JD to facilitate refunding of unused postage;

Fig. 26 is a depiction of a display showing the results of a refund eligible inquiry performed in the third postal system of Fig. 25 ; Fig. 27 is a depiction of a display showing the results of an audit review performed in the third postal system of Fig. 25;

Fig. 28 is a depiction of a display showing the results of a refund pattern audit performed in the third postal system of Fig. 25; Fig. 29 is a block diagram of a centralized postage-issuing computer system used in the third postal system of Fig. 25;

Fig. 30 is a block diagram of a master tracking computer system used in the third postal system of Fig. 25;

Fig. 31 is a flow diagram illustrating a procedure for accumulating and updating postage transaction information stored in the centralized postage-issuing computer system of Fig. 29;

Fig. 32 is a flow diagram illustrating a procedure for issuing a refund within the cenfralized postage-issuing computer system of Fig. 29;

Fig. 33 is a block diagram of still another cenfralized postage-issuing computer system used in the first postal system of Fig. 3;

Fig. 34 is a depiction of a display prompting a mail recipient to enter a fracking LD as a sender identification request;

Fig. 35 is a depiction of a display showing sender identification information;

Fig. 36 is a depiction of a mail recipient computer for displaying the information of Figs. 34 and 35; and

Fig. 37 is a flow diagram illustrating a procedure for verifying a sender of a received mail piece.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS The present invention is directed to a postage indicia tracking system for generating self-validating unique postage indicia that can be validated by a postal authority (such as, e.g., the United Stated Postal Service (USPS), United Parcel Service (UPS), Federal Express (FedEx), etc.) for various purposes (such as, e.g., detecting copy fraud, postage counterfeiting, refund facilitation, etc.). Referring to Fig. 2, a USPS Priority Mail postage label 200 generated in accordance with the present inventions can be used in a high-postage value transaction (such as, e.g., packages, expedited services, etc.) to detect copy fraud, since such transactions represent the largest fraud threat, and are the mostly likely demographic to embrace PC-Postage. We hasten to add that the present invention does not exclude envelope mail, and there are innovations presented for that arena as well. Nor does it exclude other package shipment services provided by other postal authorities, or by private shipping firms (such as, e.g., UPS, Airborne, or FedEx).

Like the prior art envelope 102 shown in Fig. 1, the label 200 shown in Fig. 2 carries a self- validating unique postage indicium 204 that is presented in a two-dimensional barcode 206 containing data relating to the mail piece on which the label 200 is applied, as well as human-readable information 208, return address 212, destination address 214, and POSTNET barcode 216. Noteworthy, is that Facing Identification Marks (FLM) are not located on the label 200, since the FLM is only a requirement for letter mail and has no value in the processing of packages. The label 200 further includes a standard unique tracking LD 218 at its center. The fracking LD 218 is presented in an associated computer readable form (such as, e.g., a one-dimensional barcode 220), and as alpha-numerical data 222, in this case, the number "0180 5213 9070 2211 5878." Up to this point, a typical USPS label, which can be used to provide fracking capability for mere administrative purposes, has been described. For example, in the USPS environs, one can obtain a delivery confirmation code for Priority Mail, an Express Mail tracking code for Express Mail, a Signature Confirmation code for Priority Mail, and a delivery confirmation code for media mail. Similar tracking LD's are used by other carriers (such as, e.g., UPS, and FedEx), as well as other postal authorities worldwide. Tracking numbers may also be added to First Class mail in the future, and are used in such ancillary services at Certified Mail.

The standard fracking LD's 218 currently used on these USPS labels, however, are not suitable for preventing postage fraud, since one can easily duplicate the postage indicia, while using different fracking LD's 218 (perhaps on a separate label), effectively covering up the copy fraud. To facilitate in detecting fraud, the self-validating unique postage indicium 204 has been modified to include a unique identifier. As will be described in further detail below, the unique identifier can be composed of, e.g., the same tracking LD 218 that is provided at the bottom right comer of the label 200. In this case, the unique identifier contained within the self-validating unique postage indicium 204 can be used to validate the standard fracking LD 218, and can thus be relied upon to detect copy fraud in a stand-alone verification system. If a standard tracking LD 218 is not used on the label 200 (e.g., if the mail piece is being shipped via first class mail), the unique identifier can be composed of the piece count or ascending register in combination with the postage vendor JD and user account number. In this case, detection of copy fraud can be ensured in a stand-alone verification system only if 100% of the postage indicia are scanned. It is noted that a tracking JD provides uniqueness with a single string of numbers, whereas a postage vendor LD/user account/piece count (or ascending register) combination provides uniqueness with two strings of numbers. To this extent, the tracking JD, when available, is more advantageous to use, not only because it can detect copy fraud with respect to a single mail piece even if less than 100% of the postage indicia is scanned, but also because it can simply accomplish this with a single unique string of characters. As will be described in further detail below, however, use of the postage vendor LD/user account/piece count (or ascending register) combination as the unique identifier can be advantageously used to detect postal fraud in a non-stand-alone verification system even if 100% of the mail pieces are not scanned.

Referring to Fig. 3, a postage system 300 provides a means for validating postage indicia in a stand-alone verification system using unique identifiers, and specifically, tracking LD's. In this embodiment, in response to requests for fracking LD's from end users, the postal service directly issues tracking LD's to the end users in a manner similar to that currently used by the USPS today. Alternatively or optionally, the postal service indirectly tracking LD's to the end users via a postage vendor. In any event, the postage vendor generates and sends self-validating unique postage indicia, which carry the issued tracking LD's, to the end users. The tracking numbers contained with the self-validating unique postage indicia are then used by the postal service to verify the postage on the mail pieces generated by the end users. To this end, the postage system 300 generally comprises a cenfralized postage indicia generation system 302, which includes a multitude of centralized postage-issuing computer systems 305/306/307 (referred to as "central computer systems" in the figures), each of which communicates with a multitude of end user computers 308. The postage system 300 also generally comprises a postal service 304, which includes a master tracking computer system 310 and a postage validation computer system 312. As will be described in further detail below, the different configurations of cenfralized postage-issuing computer systems 305/306/307 represent different means for issuing the fracking LD's to the end user computers 308. As illustrated, the centralized postage-issuing computer systems 305/306/307, end user computers 308, master tracking computer system 310, and postage validation computer system 312 variously communicate with each other over communications links 314-322, each of which may represent, e.g. a LAN, Internet, or telephone network). It should be noted that, in the illustrated embodiment, communications among the end user computers 308, cenfralized postage-issuing computer system 305/306/307, master fracking computer system 310, and postage validation computer system 312 over the various links are generally secured by use of session encryption/decryption technology. The software and processes used to implement this technology is described in detail in U.S. Patent No. 6,005,945, which has previously been incorporated herein by reference. h the illustrated embodiment, each end user computer 308 is owned and operated by a client of a postal vendor, and is the principal device for preparing mail pieces by printing the tracking LD's and self-validating unique postage indicia on the mail pieces when received by the centralized postage-issuing computer system 305/306/307. Each centralized postage- issuing computer system 305/306/307 is owned and operated by a postal vendor and is the principal device that dispenses unique postage indicia to the end user computers 308 over communications links 314 in response to requests by the end user computers 308. As will be described in further detail below, the self-validating unique postage indicia contain identifiers that are unique within the postal service 304. Thus, at least for a significant period of time, e.g., one year, no two unique identifiers will be identical, thereby providing a reliable means for detecting mail fraud. The unique identifiers can be composed of numbers, letters, or a combination. As previously discussed, however, these unique identifiers are preferably fracking LD's.

The centralized postage-issuing computer systems 306 and 307 are also the principal devices that directly transmit fracking LD's to the end user computers 308 over communications links 314 in response to requests by the end user computers 308. This configuration is used when the end user computers 308 do not directly obtain the fracking LD's from the master tracking computer system 310. The centralized postage-issuing computer systems 306 and 307 differ from each other in that the cenfralized postage-issuing computer system 306 merely acts as a vehicle for passing on fracking LD's issued by the master fracking computer system 310 to the end user computers 308, whereas the centralized postage-issuing computer system 307 actually issues fracking LD's from a previously stored pool of unassigned fracking LD's, which are periodically downloaded from the master tracking computer system 310. hi contrast to the centralized postage-issuing computer systems 306/307, the centralized postage-issuing computer system 305 does not take part in the tracking LD issuing process. In this case, it is the master fracking computer system 310, rather than the centralized postage-issuing computer system 305, that transmits fracking LD's to the end user computers 308 over coirrmunications links 322 in response to requests by the end user computers 308.

In the illustrated embodiment, the master fracking computer system 310 is owned and operated by a postal authority (such as, e.g., the USPS), and is the principal device for allocating fracking LD's either directly to the end user computers 308 over communications links 322, or directly to the centralized postage-issuing computer systems 306 or 307 over communications links 316, which then ultimately be transmitted to the end user computers 308 over the communications links 314. In an alternative embodiment, the master fracking computer system 310 is operated outside of the postal service 304. Because the USPS currently maintains such a master fracking service, however, it is preferable that the master tracking computer system 310 be contained within the postal service 304. The postage validation computer system 312 is owned and operated by the postal authority, and is the principal device for verifying the postage on mail pieces. Although in the illustrated embodiment, the postage validation computer system 312 performs stand-alone verification, if additional validating information is needed, the postage validation computer system 312 may optionally receive end user information from the centralized postage-issuing computer system 305/306/307 over communications links 318, or postage information associated with the tracking LD's from the master tracking computer system 310 over communications links 320.

Turning now to Figs. 4-7 and 33, the structural details of the postage system 300 will now be described. With specific reference to Fig. 4, each end user computer 308 contains conventional computer hardware, including a user interface 402 with a keyboard 403, printer 404, display 405, and optional scale 406 for weighing mail pieces, data processing circuitry 408 (such as, e.g., a Central Processor Unit (CPU)) for executing programs, a communications interface 410 (such as, e.g., a modem, LAN connection, or Internet connection) for handling communications with the centralized postage-issuing computer system 305/306/307 over the communications link 314 or for handling communications with the master tracking computer system 310 over the communications link 322, and local memory 411. The user interface 402 is configured to allow the end user to request unique tracking LD's and self-validating unique postage indicia and to enter postage information associated with the unique tracking LD and postage indicium requests, as well as to print the unique tracking LD's and self-validating unique postage indicia on mail pieces. The local memory 411, which will typically include both random access memory and non- volatile disk storage, stores a set of mail handling procedures that are embodied in various software modules 412, and an end user database 414 that contains information needed by mail handling modules 412, including local account balance information, transaction records representing all recent postage purchase transaction by the end user computer 308, and session encryption keys. Although the local memory 411 is depicted in Fig. 4 as a single memory device, it should be understood that it can be implemented in a multitude of memory devices as well.

The mail handling modules 412 include a fracking LD request module 414, postage indicia request module 416, communications module 418, tracking LD printing module 420, and postage indicia printing module 422. The tracking LD request module 414 is configured for generating a request for a unique tracking LD. h the illustrated embodiment, this request takes the form of a query stream (e.g., in Extensible Markup Language (XML) format), and contains postage information to be associated with the unique tracking JD, (such as, e.g., an Application Program interface (API) user account JD and password, destination address for the mail piece, sender's complete address, weight of the mail piece, service class, and the amount of postage). The postage indicia request module 416 is configured for generating a request for a self- validating unique postage indicium. In the illustrated embodiment, this request takes the form of a query sfream (e.g., in XML format), and contains information specific to the immediate postage dispensing fransaction (such as, e.g., the user's meter or account JD, the user account password, postage requested, service class, optional data advance, and ZLP+4+2 of the delivery address). If used in conjunction with the fracking LD request module 414, the request generated by the postage indicia request module 416 will also contain the unique fracking JD when received from the cenfralized postage-issuing computer system 305/306/307.

The communications module 418 is configured for handling communications with the centralized postage-issuing computer system 305/306/307 over the communications link 314 (such as, e.g., transmitting fracking LD requests and postage indicium requests and receiving tracking LD's and self-validating unique postage indicia in response thereto). The communications module 418 is also configured for handling communications with the master tracking computer system 310 over the communications link 322 (such as, e.g., transmitting tracking LD requests and receiving fracking LD's in response thereto). It should be noted that the USPS currently provides a tracking JD service called "Webtools Shipping API," which allows end user computer 308 to obtain unique fracking LD's directly from its server. The fracking LD printing module 420 is configured for printing the one-dimensional barcode 220 corresponding to the tracking JD received from the cenfralized postage-issuing computer system 306/307 on the label 200. The postage indicia printing module 422 is configured for printing on the label 200 the two-dimensional barcode 206 corresponding to the self- validating unique postage indicium received from the cenfralized postage-issuing computer system 305/306/307. Referring specifically to Fig. 33, the centralized postage-issuing computer system 305 comprises data processing circuitry 421 (such as, e.g., a Central Processor Unit (CPU)) for executing programs, a communications interface 423 (such as, e.g., a bank of modems, a LAN connection, or Internet connection) for handling communication with the end user computer 308 and postal service 304, and a local memory 424. The local memory 424, which will typically include both random access memory and non- volatile disk storage, stores a set of postage dispensing procedures that are embodied in various software modules 426. The local memory 424 also stores a customer database 428 of information about each of the user accounts received by the centralized postage-issuing computer system 306, a postage database 430 of records concerning each self-validating unique postage indicium generated by the centralized postage-issuing computer system 306, and a finance database 432 of records concerning each postage credit transaction in which funds are added to a user account.

For example, the customer database 428 may contain the following information: meter/license number, account status (active, hold, canceled, etc.), account name, account password (typically encrypted), user's name, user's company, user's street address, user's city, user's state, user's postal code, descending balance, ascending balance, current piece count (last serial number used), origin/finance ZLP5 (for US Market), origin/finance city, origin/finance state, date initially placed in service, date of last transaction, maximum postage allowable per self-validating unique postage indicium, minimum allowable balance, minimum re-credit amount, maximum re-credit amount, user's cryptographic private signing key (typically itself encrypted), credit card or ACH account numbers (typically encrypted), and account comments. The postage database 430 may contain the following information: date/time of transaction, piece number (serial number), weight, mail class, amount, destination address information, or public key reference number (indicating which key was used by the cenfralized postage-issuing computer system 306 to digitally sign the unique postage indicium for this postage dispensing event). The finance database 432 may contain the following information: date/time postage dispensed, amount of transaction, type of funds transfer (e.g., credit card, check, etc.), and identifying LD (e.g., credit card number, check number). Although the local memory 424 is depicted in Fig. 5 as a single memory device, it should be understood that it can be implemented in a multitude of memory devices.

The postage dispensing modules 426 include a communications module 434, database management module 436, tracking JD request module 438, postage indicium request validation module 440, and postage indicium generation module 442. The communications module 434 is configured for handling communications with the end user computers 308 over the communications links 314 (such as, e.g., receiving fracking JD requests and postage indicium requests and transmitting tracking LD's and unique postage indicia). The database management module 436 is configured for storing and retrieving pertinent information in and from the customer database 428, postage database 430, and finance database 432 with the pertinent information. The postage indicium request validation module 440 is configured for validating postage indicium requests received from the end user computer 308 by, e.g., validating the meter or account JD and account password in the postage indicium request in relation to the same information contained in the customer database 428. The postage indicium generation module 442, along with a corresponding private key 444, is configured for generating the self-validating unique postage indicium in response to each postage indicium request received from the end user computer 308.

In generating the self- validating unique postage indicium, the postage indicium generation module 442 comprises (1) a postage indicium generation submodule 446 for generating a unique postage indicium containing the fracking LD and/or postage vendor

LD/user account/piece count; (2) a digital signature generation submodule 448 for deriving a digital signature from the unique postage indicium using the private key 444; and (3) an association submodule 450 for associating the digital signature with the unique postage indicium to generate the self- validating unique postage indicium. It should be noted that certain cryptographically important operations are optionally performed in a specialized cryptographic coprocessor such as the FLPS-140/Level 4 LBM 458 co-processor. For instance, in the preferred embodiment, the private signing key appears in an unencrypted, operational form only within the confines of the co-processor. Similarly, the decryption of the postage indicium request and the subsequent authentication of said request is also handled inside the cryptographic co-processor. While these functions can be performed in a generalized computer operating system environment, the addition of the cryptographic coprocessor to the overall schema provides for an ultra-secure environment that is resistant to both outsider and insider attacks.

In the illustrated embodiment, the self-validating unique postage indicium contains the same information as the postage indicium set forth in Table 1, with the exception that the destination zip code has been replaced with the tracking LD (if the postage indicium request contains a tracking JD) and the account-specific piece count has been moved into the portion of the postage indicium that is digitally signed, as set forth in Table 2.

Table 2: Improved Unique Indicium Contents

The "Indicia Version Number" identifies the version number assigned by the USPS to the indicia data set. The "Algorithm LD" identifies the digital signature algorithm used to create the digital signature on the postage indicium. The "Certificate Serial Number" identifies the unique serial number of the certificate issued by the LBLP Certificate Authority. The "Device JD" identifies the USPS-assigned JD for each postage vendor, and the user account for which the postage indicium will be issued. The "Ascending Register" identifies the total monetary value of all postage indicia ever produced for the user account. The

"Postage" identifies the amount that will be applied to the mail piece. The "Date" identifies the date of mailing for a mail piece on which the postage indicium will be applied. The "License ZLP" identifies the 5-digit zip code for the licensing post office. The "Tracking Number" identifies the unique tracking JD issued by the USPS for that particular mail piece. The "Piece Count" identifies the serial number for the mail piece produced for that user account. The "Software JD" identifies the end user computer software JD number. The "Descending Register" identifies the postage value remaining in the user account. The "Rate Category" identifies the postage class, including any presort discount level, and rate. The "Signature" is the digital signature of items 1-13. It should be noted, however, that the digital signature can be derived from any combination of the items, provided that the unique tracking number is included in the digital signing process. The overall advantage of this approach is that it inserts at least one unique identifier in the digitally signed portion of the postage indicium. Not only does this allow detection of copy fraud, but the use of a tracking JD, which is scanned 100% of the time, leads to other security advantages. And this approach meets the current USPS desire to validate mail pieces in a stand-alone environment. The scan will validate the digital signature on the postage indicium and present the tracking LD instead of the destination zip code in the case of tracked packages. There are other reasons for replacing the destination zip code in the digitally signed contents of the postage indicium. Not only is the destination zip code not unique, in many cases it does not exist. For instance, mail pieces sent from the United States to foreign countries do not contain a destination zip code in the postage indicium. Also, there is a class of LBLP-related technologies, such as postage strip printers and LBLP "sheet stamps," that do not include a destination zip code in the postage indicium. Since both venues print the address in a separate and distinct operation from the postage indicium printing, the USPS has permitted the destination zip code field in the postage indicium to be set to zeroes. This opens the door for copy fraud. Optionally, the destination zip code may be appended to the "vendor portion" of the postage indicium, which is an area of the postage indicium that is not scanned by the USPS and not digitally signed.

Referring specifically to Fig. 5, the centralized postage-issuing computer system 306 differs from the cenfralized postage-issuing computer system 305 in that it provides means through which the master tracking computer system 310 issue fracking LD's to the end user computers 308. To the extent that the components of centralized postage-issuing computer systems 305 and 306 are similar, identical reference numbers have been used. In addition to the components contained in the centralized postage-issuing computer system 305, the centralized postage-issuing computer system 306 comprises postage dispensing modules 427, which additionally include a tracking JD request module 438 and a communications module 435. The fracking LD request module 438 is configured for generating and transmitting requests for unique fracking LD's to the master fracking computer system 310 in response to receiving requests for unique tracking LD's from the end user computers 308. These requests take the form of query streams and contain the same information as in the fracking ID requests generated by the tracking LD request module 414 in each of the end user computers 308. The communications module 435 is configured for handling communications with the end user computers 308 over the communications links 314 (such as, e.g., receiving tracking LD requests and postage indicium requests and fransmitting fracking LD's and unique postage indicia). The communications module 435 is further configured for handling communications with the master tracking computer system 310 over the communications link 316 (such as, e.g., fransmitting fracking LD requests and receiving tracking LD's).

Referring specifically to Fig. 6, the centralized postage-issuing computer system 307 differs from the centralized postage-issuing computer system 306 in that rather than requesting and receiving fracking LD's from the master fracking computer system 310 as tracking LD requests are received from the end user computers 308, the centralized postage- issuing computer system 307 stores a pool of unassigned tracking LD's previously received from the master tracking computer system 310 and allocates tracking LD's from this pool as tracking LD requests are received from the end user computers 308. To the extent that the components of centralized postage-issuing computer systems 306 and 307 are similar, identical reference numbers have been used. hi addition to the previously described components, the centralized postage-issuing computer system 307 comprises a local memory 452, which in addition to the previously described databases, stores a fracking JD database 454 of pre-stored unassigned tracking LD's received by the master tracking computer system 310, and a tracking information database 456 for storing each tracking JD that has been issued to an end user computer 308 and the postage information associated with each fracking LD, i.e., the information contained in the tracking LD request. The cenfralized postage-issuing computer system 307 further comprises a set of postage dispensing modules 458, which in addition to the previously described modules, includes a tracking JD allocation module 460 in place of the fracking JD request module 438, and a database management module 462 in place of the database management module 436. The fracking JD allocation module 460 is configured for allocating unique tracking LD's from the tracking JD database 454 to the end user computers 308 in response to receiving fracking LD requests from the end user computers 308. hi addition to performing the afore-described functions, the database management module 462 is further configured for storing pools of unassigned tracking LD's within the fracking LD database 454 as they are periodically received by the master fracking computer system 310, and for periodically retrieving postage information from the tracking information database 456 for transmission to the master tracking computer system 310.

Referring specifically to Fig. 7, the master tracking computer system 310 comprises data processing circuitry 464 (such as, e.g., a Central Processor Unit (CPU)) for executing programs, a local memory 468, and a communications interface 466 (such as, e.g., a bank of modems , a LAN connection, or Internet connection) for handling communication with the centralized postage-issuing computer systems 306/307 over communications links 316 or with the end user computers 308 over communications links 322. If the master fracking computer system 310 and the postage validation computer system 312 are not embodied in the same computer, the communications interface 466 may also handle communication with the postage validation computer system 312. The local memory 468, which will typically include both random access memory and non-volatile disk storage, stores tracking LD maintenance procedures that are embodied in various software modules 470. The local memory 468 also stores a tracking information database 472 for storing each tracking LD that has been issued to an end user computer 308 and the postage information associated with each fracking JD, i.e., the information contained in the tracking JD request. Although the local memory 468 is depicted in Fig. 6 as a single memory device, it should be understood that it can be implemented in a multitude of memory devices.

The fracking JD maintenance modules 470 include a communications module 474, tracking LD allocation module 476, and database management module 478. The communications module 474 is configured for handling communications with the cenfralized postage-issuing computer systems 306/307 over the communications links 316, or with end user computers 308 over the cornmunications links 322 (such as, e.g., receiving single tracking JD requests and fransmitting tracking LD's to and from the centralized postage- issuing computer systems 306 or end user computers 308, as well as transmitting pools of unassigned tracking LD's and receiving assigned tracking LD's and associated postage information to and from the cenfralized postage-issuing computer systems 307). The cornmunications module 474 is also configured for handling communications with the postage validation computer system 312 over the communications link 318 (such as, e.g., receiving requests for assigned tracking LD's, associated postage information, and current delivery status, and fransmitting the assigned tracking LD's, associated postage information, and current delivery status). The fracking LD allocation module 476 is configured for generating unique tracking ID's in response to receiving fracking JD requests from the centralized postage-issuing computer systems 306, or optionally from the end user computers 308. The database management module 478 is configured for storing and retrieving assigned tracking LD's and associated postage information to and from the tracking information database 472. Although the local memory 468 is depicted in Fig. 7 as a single memory device, it should be understood that it can be implemented in a multitude of memory devices.

Referring specifically to Fig. 8, the postage validation computer system 312 comprises data processing circuitry 480 (such as, e.g., a Central Processor Unit (CPU)) for executing programs, a communications interface 482 (such as, e.g., a bank of modems, a LAN connection, or Internet connection) for handling communication with the cenfralized postage-issuing computer system 305/306/307, postage scanning stations 484, and a local memory 486. If the master tracking computer system 310 and the postage validation computer system 312 are not embodied in the same computer, the communications interface 482 may also handle communication with the master tracking computer system 310. The postage scanning stations 484 include the software and hardware (including a barcode reader) necessary for reading the barcode information applied on each mail piece and displaying it in a human-readable format for postal verifiers. The local memory 486, which will typically include both random access memory and non- volatile disk storage, stores a set of postage validation procedures that are embodied in various software modules 488. The local memory also stores a meter information database 490 of information about each licensed postage meter, i.e., each end user computer 308, and a transaction database 491 for storing records concerning every mail piece validated or rejected by the postage validation computer system 312, including the unique identifier(s) contained in the postage indicium, e.g., the fracking JD and postage vendor LD/user account/piece count (or ascending register).

The postage validation modules 488 include a communications module 492, database management module 493, a postage indicia validation module 494, and unique identifier comparison module 495. The communications module 492 is configured for handling communications with the centralized postage-issuing computer systems 305/306/307 over the communications links 318 (such as, e.g., receiving updated end user computer information and public key information). The communications module 492 is also configured for handling communications with the master tracking computer system 310 over the communications link 320 (such as, e.g., transmitting requests for tracking LD associated postage information and receiving the fracking JD associated postage information). The database management module 493 is configured for storing and retrieving pertinent information to and from the meter information database 490 and transaction database 491.

The postage indicia validation module 494 is configured for validating the postage indicia, and includes a public key association submodule 496 for selecting a public key from the set of public keys 497, as dictated by the certificate serial number (item #3 in Table 2) in the self- validating unique postage indicium, and a digital signature verification submodule 498, along with a selected public key, configured for verifying the digital signature in the self-validating unique postage indicium.

The unique identifier comparison module 495 is configured for comparing the digitally authenticated unique identifier contained in the postage indicium to all of the unique identifiers previously stored in the fransaction database 491 to detect copy fraud. That is, a match means that the unique identifier has been previously used, which is an indication of copy fraud.

Referring specifically to Fig. 9, and with general reference to Figs. 3-5 and 7, a procedure for indirectly issuing a fracking LD from the master tracking computer system 310 to the end user computer 308 via the centralized postage-issuing computer system 306 and applying it to the label 200 will now be described. At steps 500-504, the end user computer 308 generates and transmits a request for a unique tracking JD to the cenfralized postage- issuing computer system 306. In particular, the end user operates the user interface 402 of the end user computer 308 to request a unique tracking JD and enter postage information to be associated with the unique tracking JD (step 500). As previously discussed, this postage information may contain the API user account LD and password, complete destination address for the mail piece, sender's complete address, weight of the mail piece, service class, and the amount of postage. The tracking JD request module 414 then generates a tracking LD request with the associated postage information (step 502). The communications interface 410 then, under control of the cornmunications module 418, transmits the fracking JD request over the cornmunications link 314 (step 504). At steps 506-510, the centralized postage-issuing computer system 306 receives the tracking LD request from the end user computer 308, and generates an identical tracking LD request, and transmits the tracking LD request to the master tracking computer system 310. In particular, the communications interface 423, under control of the commumcations module 434, receives the tracking JD request over the communications link 314 (step 506). The tracking LD request module 438 then generates a tracking LD request with the associated postage information, which is identical to the tracking JD request received from the end user computer 308 (step 508). Optionally, the database management module 436 stores the tracking information within a database, such as, e.g., a tracking information database (not shown). The communications interface 423 then, under control of the communications module 434, transmits the tracking JD request over the communications link 316 (step 510).

At steps 512-518, the master tracking computer system 310 receives the tracking LD request from the centralized postage-issuing computer system 306, allocates a unique tracking JD to the end user computer 308, records the unique tracking JD, along with the associated postage information, and fransmits the unique tracking JD to the centralized postage-issuing computer system 306. In particular, the communications interface 466, under control of the communications module 474, receives the tracking LD request over the communications link 316 (step 512). The tracking JD allocation module 476 then allocates a unique fracking LD to the end user computer 308, which typically will be the next fracking LD in a series of tracking LD's (step 514). The database management module 478 then stores the unique tracking JD, as well as the associated postage information contained within the tracking JD request received from the centralized postage-issuing computer system 306, within the tracking information database 472 (step 516). The communications interface 466 then, under control of the communications module 474, transmits the umque tracking JD over the communications link 316 (step 518).

At steps 520 and 522, the centralized postage-issuing computer system 306 receives the unique tracking JD from the master tracking computer system 310 and transmits the unique tracking JD to the end user computer 308. In particular, the communications interface 423, under confrol of the communications module 434, receives the unique tracking JD over the communications link 316 (step 520). The communications interface 423 then, under confrol of the communications module 434, fransmits the tracking JD over the cornmunications link 314 (step 522). At steps 524 and 526, the end user computer 308 receives the tracking LD from the centralized postage-issuing computer system 306 and prints the tracking LD on the label 200. In particular, the communications interface 410, under control of the communications module 418, receives the unique tracking LD over the communications link 314 (step 524). The fracking JD printing module 420 then prints on the label 200 the standard tracking JD 218 as the one-dimensional barcode 220 (step 526).

Referring specifically to Fig. 10, and with general reference to Figs. 3-4 and 6-7, a procedure for issuing a fracking JD from the cenfralized postage-issuing computer system 307 to the end user computer 308 and applying it to the label 200 will now be described. At steps 528-532, the end user computer 308 generates and transmits a request for a unique fracking LO to the cenfralized postage-issuing computer system 307. Steps 528-532 are similar to steps 500-504 described with respect to Fig. 9 and will thus not be described in detail here.

At steps 534-540, the cenfralized postage-issuing computer system 307 receives the fracking LD request from the end user computer 308, allocates a unique fracking LD to the end user computer 308, records the unique tracking LD, along with the associated postage information, and transmits the unique tracking LD to the end user computer 308. In particular, the communications interface 423, under control of the communications module ^■ 434, receives the tracking JD request over the communications link 314 (step 534). The fracking JD allocation module 460 then allocates a unique fracking LD to the end user computer 308, which typically will be the next fracking LD in a series of fracking LD's stored in the tracking LD database 454 (step 536). The database management module 462 then stores within the tracking information database 456 the unique fracking JD, as well as the associated postage information contained within the fracking JD request received from the end user computer 308 (step 538). The communications interface 423 then, under confrol of the communications module 434, transmits the tracking LD over the communications link 314 (step 540).

At steps 542 and 544, the end user computer 308 receives the fracking LD from the centralized postage-issuing computer system 306 and prints the fracking LD on the label 200. Steps 542 and 544 are similar to steps 526 and 528 described with respect to Fig. 9 and will thus not be described in detail here. Periodically, such as, e.g., once a day, a pool of unassigned unique fracking LD's will be downloaded into the cenfralized postage-issuing computer system 307 from the master tracking computer system 310, and assigned tracking LD's and the associated postage information will be uploaded from the centralized postage- issuing computer system 307 to the master tracking computer system 310. Alternatively, rather than sending tracking information in batch mode, the fracking information can be transmitted to the master tracking computer system 310 in real-time, i.e., as the fracking LD's are assigned to the end user computers 308. The procedure for performing these downloading and uploading functions are now described with respect to Fig. 11. At steps 546-552, the centralized postage-issuing computer system 307 retrieves all of the accumulated assigned tracking LD's and associated postage information and fransmits it to the master tracking computer system 310, and then the master fracking computer system 310 receives the tracking information from the cenfralized postage- issuing computer system 307 and records it. In particular, the database management module 462 retrieves the assigned fracking LD's and associated postage information from the tracking information database 456 (step 546). The communications interface 423 then, under control of the communications module 434, transmits the retrieved fracking information over the communications link 316 (step 548). The communications interface 466, under control of the communications module 474, receives the fracking information over the cornmunications link 316 (step 550). The database management module 478 then stores the fracking information in the tracking information database 472 (step 552).

At steps 554-560, the master tracking computer system 310 generates a pool of unassigned tracking LD's and fransmits it to the centralized postage-issuing computer system 307, and the centralized postage-issuing computer system 307 receives the pool of unassigned unique tracking LD's from the master tracking computer system 310 and records it. In particular, the database management module 478 generates a pool of unassigned unique fracking LD's (step 554). The commumcations interface 466 then, under control of the cornmunications module 474, fransmits the pool of unassigned tracking LD's over the communications link 316 (step 556). The communications interface 423, under confrol of the communications module 434, receives the tracking information over the communications link 316 (step 558). The database management module 462 then stores the pool of unassigned unique fracking LD's in the tracking LD database 454 (step 560).

Referring specifically to Fig. 12, and with general reference to Figs. 3-5 and 7-8, a procedure for directly issuing a tracking JD from the master fracking computer system 310 to the end user computer 308 and applying it to the label 200 will now be described. At steps 562-566, the end user computer 308 generates and fransmits a request for a unique tracking JD to the master fracking computer system 310. Steps 562 and 564 are similar to steps 500 and 502 described with respect to Fig. 9 and will thus not be described in detail here. After steps 562 and 564, the communications interface 410, under confrol of the communications module 418, fransmits the fracking JD request over the communications link 322 (step 566).

At steps 568-572, the master fracking computer system 310 receives the tracking JD request from the end user computer 308, allocates a unique tracking JD to the end user computer 308, records the unique tracking LD, along with the associated postage information, and transmits the unique tracking JD to end user computer 308. In particular, the communications interface 466, under control of the communications module 474, receives the tracking LD request over the cornmunications link 322 (step 568). The tracking JD allocation module 476 then allocates a unique tracking LD to the end user computer 308, which typically will be the next fracking LD in a series of fracking LD's (step 570). The database management module 478 then stores within the tracking information database 472 the unique fracking JD, as well as the associated postage information contained within the fracking JD request received from the end user computer 308 (step 572). The communications interface 466 then, under control of the commumcations module 474, transmits the unique tracking JD over the communications link 322 (step 574).

At steps 576 and 578, the end user computer 308 receives the tracking ID from the master fracking computer system 310 and prints the tracking JD on the label 200. hi particular, the communications interface 410, under confrol of the communications module 418, receives the unique fracking JD over the communications link 322 (step 576). The tracking JD printing module 420 then prints on the label 200 the standard fracking JD 218 as the one-dimensional barcode 220 (step 578).

Referring specifically to Fig. 13, and with general reference to Figs. 3-6, the procedure for dispensing and applying a self-validating unique postage indicium to the label 200 will now be described. At steps 600-604, the end user computer 308 generates and fransmits a unique postage indicium request to the cenfralized postage-issuing computer system 305/306/307. In particular, the end user operates the user interface 402 of the end user computer 308 to request a unique postage indicium and enter postage information to be associated with the unique postage indicium (step 600). As previously discussed, this postage information may contain the user's meter or account JD, the user account password, postage requested, service class, optional data advance, and ZLP+4+2 of the delivery address. If the end user computer 308 has previously obtained a tracking JD directly from the master tracking computer system 310 by the process described in Fig. 12, the postage information will also contain the tracking JD. In any event, the postage indicia request module 416 then generates a postage indicium request with the associated postage information (step 602). The communications interface 410 then, under confrol of the communications module 418, transmits the postage indicium request over the communications link 314 (step 604). At steps 606-618, the centralized postage-issuing computer system 305/306/307 receives the postage indicium request from the end user computer 308, validates it, records the postage information contained in the postage indicium request, as well as any other transaction specific pertinent information, generates a self-validating unique postage indicium, and transmits the self-validating unique postage indicium to the end user computer 308. In particular, the communications interface 423, under confrol of the communications module 434, receives the postage indicium request over the communications link 314 (step 606). The postage indicium request validation module 440 then validates the postage indicium request by validating the user account JD and account password (step 608). If the user account JD or password does not correspond to an active user account, an error message is generated.

The database management module 436 then updates the customer database 428 and postage database 430 with the pertinent transaction specific information (step 610). If available, the database management module 436 will store the fracking JD in the postage database 430. The postage indicium generation module 442 then generates the self-validating unique postage indicium (steps 612-616). Specifically, the postage indicium generation submodule 446 generates a unique postage indicium containing the items set forth in Table 2, including the unique identifier(s) (such as, e.g., the postage vendor LD/user account number in combination with the piece count or descending register number, and unique tracking JD (if available) contained within the postage indicium request) (step 612). At this point, the unique postage indicium is not self- validating. The digital signature generation submodule 448 then derives a digital signature from the unique postage indicium by applying the private key 444 thereto (step 614). The association submodule 450 then generates the self-validating unique postage indicium by associating the digital signature with the unique postage indicium (step 616). The communications interface 423 then, under control of the communications module 434, fransmits the self-validating unique postage indicium over the communications link 314 (step 618).

At steps 620 and 622, the end user computer 308 receives the self- validating unique postage indicium from the cenfralized postage-issuing computer system 305/306/307 and prints it on the label 200. particular, the communications interface 410, under control of the communications module 418, receives the self-validating unique postage indicium over the communications link 314 (step 620). The postage indicia printing module 420 then prints on the label 200 the two-dimensional barcode 206 corresponding to the self- validating unique postage indicium (step 622). The label 200 can then be applied to the appropriate mail piece.

It should be noted that although the tracking JD acquisition and printing processes described with respect to Fig. 9-12, and the postage indicium acquisition and printing process described with respect to Fig. 13, have been described as distinct functions, these processes are preferably performed as a single process as experienced by the end user. For example, the fracking LD and postage indicium requests will be separately generated and fransmitted from the end user computer 308, but will be prompted by the single click of a mouse on, e.g., a "print button." Upon the acquisition of both the fracking LD and postage indicium, the barcodes will be printed on the label 200 as a single step. If either or both of the tracking JD and postage indicium are not returned successfully, nothing is printed on the label 200. For example, if the postage indicium request fails for any reason, the entire process is aborted even through a fracking LD has been issued, in which case, it will be "orphaned."

Referring to specifically Fig. 14, and with general reference to Figs. 4-7, the procedures for validating the postage on a mail piece using a stand-alone procedure will now be described. It should be noted that the order of the validation steps in the procedure is completely variable and will likely vary from implementation to implementation. At step 700, the postal verifier operates a postage scanning station 484 within the postage validation computer system 312 to read the self-validating postage indicium (i.e., the two-dimensional barcode 206) on the mail piece and display its contents to the verifier. At step 702, the verifier then manually compares the contents of the two-dimensional barcode 206 to the human-readable information (e.g., mailing date, postage amount, origin of mail piece, and destination of mail piece). If the barcode information does not match the human-readable information, this is an indication of likely fraudulent use of a postage indicium and is treated as such. Further details on this comparison process are disclosed in U.S. Patent No. 6,005,945, which has previously been incorporated herein by reference. At steps 704-706, the postal verifier validates the postage indicium itself by operating the postage indicia validation module 494. In particular, the public key association submodule 496 obtains from the set of public keys 497 the public key corresponding to the Certificate Serial Number (item #3 in Table 2) within the postage indicium (step 704). The digital signature verification submodule 498 then verifies the digital signature of the postage indicium (step 706) to determine if they are consistent. If the signature verification process returns a Boolean true, this indicates that the postage indicium was in fact generated by a secure central computer 305/306/307 for a mail piece of the same approximate weight, origin and destination as the mail piece being processed.

This will not, however, detect copy fraud. Thus, at step 708, the unique identifier comparison module 495 compares the unique identifier(s) of the mail piece (i.e., the unique tracking LD (if available), and the postage vendor LD/user account/piece count (or ascending register)) with the set of unique identifiers previously stored in the transaction database 491. If the unique identifier of the current mail piece matches at least one of the unique identifiers stored in the fransaction database 491, copy fraud is assumed, or at least suspected. If the unique identifier of the current mail piece does not match at least one of the unique identifiers stored in the transaction database 491, copy fraud is not assumed, although copy fraud may be detected if a fraudulent duplicate of the postage indicium is subsequently processed. It is worth noted that copy fraud detection using this process works with respect to any mail piece of any nature only if the unique identifiers contained in the postage indicia of all mail pieces are scanned and entered into the transaction database 491. Alternatively, copy fraud detection using this process works with respect to any mail piece that carries a tracking JD if the tracking LD's contained in the postage indicia of all of these types of mail pieces are scanned and entered into the transaction database 491. Currently, however, the USPS only spot checks the postage indicia, and thus copy fraud may be currently difficult to detect using copy fraud — at least until the USPS scans 100% of the postage indicia. For example, if the postage indicia is checked only 10% of time, statistically, copy fraud will only be detected 1% of the time. Alternatively, when spot checking is the norm, detection of copy fraud in mail pieces that carry unique tracking LD's can be maximized by comparing the unique fracking LD contained in the postage indicium with the standard tracking LD printed on the mail piece (step 710). Thus, if the unique fracking ID contained in the postage indicium does not match the tracking JD contained elsewhere on the mail piece, copy fraud is suspected. It is noted that the one-dimensional barcode 220 associated with the fracking LD is scanned 100% of the time in the normal course of the USPS fracking business, and thus, a copyist will not attempt to duplicate one-dimensional barcodes 220 along with the unique postage indicia, but will rather only attempt to duplicate the unique postage indicia hoping that the fracking ID's contained therein will not be compared with the tracking LD's associated with the one- dimensional barcodes 220. Thus, if the postage indicia is checked 10% of the time, copy fraud will be detected 10% of the time— a significant improvement.

It should be noted that additional transaction information can be obtained from the centralized postage-issuing computer system 305/306/307 or master tracking computer system 310 over the communications links 318 and 320. This process will not be described in further detail. After the postage has been validated or rejected, the database management module 493 stores the postage information, including the unique identifier(s) contained within the postage indicium within the transaction database 491, along with the results of the validation process (step 712). If valid, the mail piece is then submitted for normal delivery processing (step 714).

With reference to Fig. 15, a postage system 350 comprises a centralized postage indicia generation system 352, which includes a multitude of centralized postage-issuing computer systems 356, each of which includes a multitude of end user computers 358. The postage system 350 also generally comprises a postal service 354, which includes an optional master tracking computer system 360 and a postage validation computer system 362. The centralized postage-issuing computer system 356, end user computer 358, master tracking computer system 360, and postage validation computer system 362 communicate with each other over communications links 364-370 (such as, e.g., LAN, Internet, or telephone network).

These components are generally similar to the same-named components of the postage system 300, but differ somewhat in that it provides a means for validating postage indicia in a non-stand-alone verification system using indexing identifiers. In this embodiment, in response to requests for postage from end user computers 358, each cenfralized postage-issuing computer system 356 generates postage indicia, and rather than transmitting it to the end user computers 358, indexes and stores the postage indicia. The postage indicia are indexed using indexing identifiers, which are fransmitted to the end user computers 358 for printing on the mail pieces. In the illustrated embodiment, the indexing identifiers are unique within the postage service 354. Thus, at least for a significant period of time, e.g., one year, no two unique indexing identifiers will be identical, thereby providing a reliable means for detecting mail fraud. The unique indexing identifiers can be composed of numbers, letters, or a combination thereof, and can be composed of tracking ID's postage vendor LD/user account/piece count (or ascending register) combinations, similar to the unique identifiers described with respect to the postage system 300.

These printed indexing identifiers can then be subsequently used by the postage service 354 to obtain the stored postage indicia from the cenfralized postage-issuing computer systems 356. The centralized postage indicia generation methodology offers a host of new security enhancements. Thus, if one makes the assumption that any mail piece validation tool would have access to the Internet (e.g., a laptop with a wireless Internet connection on a loading dock, or a desktop personal computer (PC) located in a mail processing facility), then one may greatly simplify the information contained on the mail piece itself if the mail piece was generated with a centralized postage service.

Turning now to Figs. 16-18, the structural details of the postage system 350 will now be described. For purposes of brevity, the tracking JD related components have not been included in the structure details of the postage system 350. It should be noted, however, that such fracking JD components could be incorporated in the postage system 350 to provide tracking ED functionality to the postage system 350 similar to that of the postage system 300.

With specific reference to Fig. 16, each end user computer 358 contains conventional computer hardware, including a user interface 802, data processing circuitry 808 (such as, e.g., a Central Processor Unit (CPU)), and communications interface 810, which are similar to the same-named components of the previously described end user computer 308 and will thus not be described in further detail. The end user computer 358 further comprises local memory 811, which is similar to the local memory 411 of the previously described end user computer 308, with the exception that it includes a set of mail handling modules 812 configured to handle indexing identifiers, rather than tracking LD's and postage indicia.

Specifically, the mail handling modules 812 include an indexing identifier request module 814, communications module 818, and indexing identifier printing module 820. The indexing identifier request module 814 is configured for generating a request for an indexing identifier. In the illustrated embodiment, this request takes the form of a query stream (e.g., in Extensible Markup Language (XML) format), and contains information specific to the immediate postage dispensing transaction (such as, e.g., the user's meter or account LD, the user account password, postage requested, service class, optional data advance, and ZEP+4+2 of the delivery address). The communications module 818 is configured for handling commumcations with the centralized postage-issuing computer system 356 over the communications link 364 (such as, e.g., transmitting indexing identifier requests and receiving indexing identifiers in response thereto). The indexing identifier printing module 820 is configured for printing an indexing identifier 203 received from the centralized postage-issuing computer system 356 on a label 201. The completed label 201 is similar to the completed label 200 illustrated in Fig. 4, with the exception that the indexing identifier is printed thereon rather than a postage indicium and tracking JD.

The indexing identifier can be printed on the label 201 in various formats. For example, Fig. 19 illustrates a two-dimensional barcode 256, which represents the indexing identifier. As can be seen, the two-dimensional barcode 256 is much smaller than two- dimensional barcodes that represent a full postage indicium, because it contains much less information, i.e., a unique identifier. In this case, the unique identifier is composed of a postage vendor JD (07), user account number (500361), and piece count (1221^st piece generated for this user account). In fact, the information makes the indexing identifier is so minimal, that a one-dimensional barcode can be used. For example, a Code 128 barcode 258 illustrated in Fig. 20, or postal-specific barcode topology, such as the POSTNET or PLANET barcode 260 illustrated in Fig. 21, can be used to represent the postage vendor JD, account number, and piece count of the indexing identifier. Even more alternatively, use of a barcode can be omitted altogether, and the indexing identifier can simply be printed on the mail piece as numerical data 262, as illustrated in Fig. 22. The numerical data 262 can be read by Optical Character Recognition (OCR) software, the speed of which is compatible with mail processing requirements. Note that although the examples in Figures 19, 20, 21 and 22 used the unique combinations of postage vendor JD, account number and piece count, one could alternately employ a postal authority assigned tracking number as the unique indexing identifier. Thus, the use of smaller two-dimensional barcodes or the simpler one-dimensional barcodes or digital data reduces the footprint required on the mail piece, and leaves that much more room for addressing, advertising, etc. This reduction in data also reduces the load on high speed printers, which have difficulty placing custom, non-static barcode images on mail pieces without compromising their rated speed (often 10,000-30,000 pieces per horn). Standard text can be printed at full speed, and most high-speed printers have one-dimensional barcode software (e.g., Code 128) in the printer firmware. Therefore, use of an indexing identifier, rather than a full postage indicium, opens the LBLP market to mass mailers, which account for the bulk of USPS letter mail revenue. Not only will use of the indexing identifier reduce printing costs, it will also reduce capital expenditure costs for barcode reading hardware. If OCR readable data is used for the indexing identifier, OCR capabilities, which the USPS already has extensive experience, can be used.

With specific reference to Fig. 17, each cenfralized postage-issuing computer system 356 comprises data processing circuitry 820 (such as, e.g., a Cenfral Processor Unit (CPU)) and a communications interface 822, which are similar to the same-named components of the previously described cenfralized postage-issuing computer system 305 and will thus not be described in further detail. The centralized postage-issuing computer system 356 further comprises a local memory 824, which is similar to the local memory 424 of the previously described centralized postage-issuing computer system 305, with the exception that it includes a set of postage dispensing modules 826 configured to index and store postage indicia, and transmit an indexing identifier, rather than the complete postage indicia, to the end user computers 358. The local memory 824 further includes, in addition to a customer database 828, postage database 830, and finance database 832, a postage indicia database 831 for storing the indexed postage indicia.

Specifically, the postage dispensing modules 826 include a communications module 834, database management module 836, indexing module 838, indexed identifier request validation module 840, and postage indicium generation module 842. The communications module 834 is configmed for handling communications with the end user computers 358 over the communications links 364 (such as, e.g., receiving indexing identifier requests and transmitting indexing identifiers). The database management module 836 is configmed for storing and retrieving pertinent information in and from the customer database 828, postage database 830, and finance database 832, as well as for storing and retrieving indexed postage indicia in and from the postage indicia database 831. The postage indicia can include, e.g., the postage amount, date and time the postage indicium was created, service class, optional data advance, delivery zip code, and fracking JD (if the mail piece is a tracked piece). The indexing identifier request validation module 840 is configmed for validating indexing identifier requests received from the end user computer 358 by, e.g., validating the meter or account ID and account password in the indexing identifier request in relation to the same information contained in the customer database 828.

The postage indicium generation module 842, along with a conesponding private key 844, is configured for generating a self- validating postage indicium in response to each indexing identifier request received from the end user computer 358. In generating the self- validating postage indicium, the postage indicium generation module 842 comprises (1) a postage indicium generation submodule 846 for generating a postage indicium; (2) a digital signature generation submodule 848 for deriving a digital signature from the postage indicium using the private key 844; and (3) an association submodule 850 for associating the digital signatme with the postage indicium to generate the self-validating postage indicium. In the illustrated embodiment, the self-validating postage indicium contains the same information as the postage indicium previously set forth in Table 2. The indexing module 838 is configured for associating the indexing identifier transmitted to the end user computer 358 with the postage indicium stored within the postage indicia database 831. It is noted that the elimination of the digital signature on the mail piece itself does not compromise security, since the postage indicium stored in the postage indicia database 831 of the centralized postage-issuing computer system 356 is digitally signed in accordance with the USPS LBD? specifications. The presence of the digital signature somewhere in the security model addresses one major concern of the USPS — that fraud attacks are very likely to involve "insiders" employed by the postage vendor. To further ensme that the security system is impervious to even an insider attack, all security-critical operations such as indicium signing are actually accomplished within a Federal Information Processing Standard (FLPS-140/Level 4)-approved, physically secure coprocessor device (such as, e.g., an LBM 4758). With specific reference to Fig. 18, the postage validation computer system 362 comprises data processing circuitry 880 (such as, e.g., a Central Processor Unit (CPU)), and communications interface 882, which are similar to the same-named components of the previously described centralized postage-issuing computer system 305 and will thus not be described in further detail. The postage validation computer system 362 further comprises postage scanning stations 884, include the software and hardware necessary for reading the indexed identifiers on each mail piece and displaying it in a human-readable format for postal verifiers. If the indexed identifiers are printed on the mail pieces in a two-dimensional or one-dimensional barcode format, the postage scanning stations will be equipped with barcode readers and accompanying software capable of reading these barcodes. If the indexed identifiers are printed on the mail pieces in a numerical data format, the postage scanning stations 884 will include OCR equipment. The postage validation computer system 362 further comprises a local memory 886, which is similar to the local memory 486 of the previously described cenfral postage validation computer system 312, with the exception that it validates mail pieces using the postage indicia obtained from the cenfralized postage- issuing computer system 356, rather than postage indicia printed on the mail pieces.

The postage validation modules 888 include a communications module 892, database management module 893, postage indicia validation module 894, and postage indicia request module 895. The postage indicia request module 895 is configmed for generating a request for postage indicium. In the illustrated embodiment, this request takes the form of a query stream (e.g., in Extensible Markup Language (XML) format), and contains the indexing identifier read from the mail piece and a password. The communications module 818 is configured for handling communications with the cenfralized postage-issuing computer system 356 over the communications link 368 (such as, e.g., transmitting postage indicium requests and receiving postage indicia in response thereto). The postage indicia validation module 894 is configmed for validating the postage indicia obtained from the cenfralized postage-issuing computer system 356, and includes a public key association submodule 896, public keys 897, and digital signature verification submodule 898, which are similar to the same-named components in the previously described postage validation computer system 312, and will thus not be further described.

Referring to specifically Fig. 23, and with general reference to Figs. 15-17, the procedures for indexing a postage indicium and applying an indexed identifier to the label 201 will now be described. At steps 900-904, the end user computer 358 generates and fransmits a indexing identifier to the cenfralized postage-issuing computer system 356. In particular, the end user operates the user interface 802 of the end user computer 804 to request an indexing identifier and enter postage information to be associated with the postage indicium (step 900). The indexing identifier request module 814 then generates an indexing identifier request with the associated postage information (step 902). The communications interface 810 then, under confrol of the communications module 818, transmits the indexing identifier request over the communications link 364 (step 904).

At steps 906-910, the cenfralized postage-issuing computer system 356 receives and validates the indexing identifier request from the end user computer 358, and records the postage information contained in the postage indicium request, as well as any other fransaction specific pertinent information, hi particular, the communications interface 822, under confrol of the communications module 834, receives the indexing identifier request over the communications link 364 (step 906). The indexing identifier request validation module 840 then validates the indexing identifier request by validating the user account JD and account password (step 908). If the user account JD or password does not correspond to an active user account, an enor message is generated. The database management module 836 then updates the customer database 828 and postage database 830 with the pertinent fransaction specific information (step 910). At steps 912-916, the centralized postage-issuing computer system 356 then generates the self-validating unique postage indicium. Specifically, the postage indicium generation submodule 946 generates a postage indicium containing the items set forth in Table 2 (step 912). The digital signatme generation submodule 848 then derives a digital signatme from the postage indicium by applying the private key 844 thereto (step 914). The association submodule 850 then generates the self- validating postage indicium by associating the digital signature with the postage indicium (step 916).

At steps 918-922, the cenfralized postage-issuing computer system 356 then indexes and records the self-validating postage indicium, and transmits the indexing identifier to the end user computer 358. Specifically, the indexing module 838 indexes the self-validating postage indicium by associating the indexing identifier therewith (step 918). The database management module 836 then stores the indexed self- validating postage indicium in the postage indicia database 831 (step 920). The communications interface 822 then, under confrol of the communications module 834, fransmits the indexing identifier over the communications link 314 (step 922). At steps 924 and 926, the end user computer 554 receives the indexing identifier from the centralized postage-issuing computer system 356 and prints it on the label 201. In particular, the communications interface 810, under confrol of the communications module 818, receives the indexing identifier over the communications link 364 (step 924). The indexing identifier printing module 820, prompted by the end user via the user interface, then prints on the label 201 the two-dimensional barcode 256, either of the one-dimensional barcodes 258 or 260, or the alpha-numerical data 262 (step 926). The label 201 can then be applied to the appropriate mail piece.

Referring to specifically Fig. 24, and with general reference to Figs. 15, 17, and 18, the procedures for validating the postage on a mail piece using a non-stand-alone procedure will now be described. It should be noted that the order of the validation steps in the procedure is completely variable and will likely vary from implementation to implementation. At step 1000, the postal verifier operates a postage scanning station 884 within the postage validation computer system 362 to read the indexing identifier (i.e., the two- dimensional barcode 256, one-dimensional codes 258 or 260, or alpha-numerical data 262) on the label 201 of the mail piece and display its contents to the verifier. At steps 1002-1004, the postage validation computer system 362 requests from the centralized postage-issuing computer system 356 the self- validating postage indicium associated with the indexing identifier read from the mail piece, hi particular, the postage indicia request module 895 generates a postage indicium request carrying the indexing identifier and the password (step 1002). The communications interface 882 then, under control of the communications module 892, fransmits the postage indicium request over the communications link 368 (step 1004).

At steps 1004-1010, the centralized postage-issuing computer system 356 then receives the postage indicium request, and retrieves and fransmits to the postage validation computer system 362 the self- validating postage indicium conesponding to the inspected mail piece. In particular, the communications interface 822, under control of the communications module 834, receives the postage indicium request over the cornmunications link 368 (step 1006). The database management module 836 then retrieves from the postage indicia database 831 the self- validating postage indicium conesponding to the received indexing identifier (step 1008). The communications interface 822 then, under control of the communications module 834, transmits the self-validating postage indicium over the communications link 368 (step 1010).

At steps 1012 and 1014, the postage validation computer system 362 receives the self- validating postage indicium from the cenfralized postage-issuing computer system 356 and displays its contents to the postal verifier. In particular, the communications interface 882 then, under confrol of the communications module 892, receives the self- validating postage indicium from the centralized postage-issuing computer system 356 over the communications link 368 (step 1012), and the postage scanning station 884 displays its contents to the postal verifier (step 1014). At step 1016, the verifier then manually compares the contents of the self-validating postage indicium to the human-readable information (e.g., mailing date, postage amount, origin of mail piece, and destination of mail piece) on the mail piece. If the contents of the self- validating postage indicium do not match the human-readable information, this is an indication of likely fraudulent use of a postage indicium and is treated as such. At steps 1018-1020, the postal verifier validates the postage indicium itself by operating the postage indicia validation module 894. In particular, the public key association submodule 896 obtains from the set of public keys 897 the public key conesponding to the Certificate Serial Number (item #3 in Table 2) within the postage indicium (step 1018). The digital signature verification submodule 898 then verifies the digital signature of the postage indicium to determine if they are consistent (step 1020). If the verification process returns a Boolean true, this indicates that the postage indicium was in fact generated by a secme cenfral computer 356 for a mail piece of the same approximate weight, origin and destination as the mail piece being processed. If copy fraud is to be detected, a copy fraud detection process using unique identifiers or similar to the process disclosed with respect to Fig. 14 can be utilized.

After the postage has been validated or rejected, the database management module 893 stores the postage information, along with the results of the validation process (step 1022). If valid, the mail piece is then submitted for normal delivery processing (step 1024). It should be noted that rather than have the postal verifier validate the postage indicium, the centralized postage-issuing computer system 356 itself can validate the postage indicium, hi this case, the postage indicia validation module 894 will be located in the cenfralized postage-issuing computer system 356. Thus, after the centralized postage-issuing computer system 356 retrieves the self- validating postage indicium conesponding to the indexing identifier at step 1008, it will validate the postage indicium itself using a conesponding public key. If it is valid, the cenfralized postage-issuing computer system 356 will transmit a Boolean true, along with the already validated postage indicium, to the postage validation computer system 362, which will then perform postage validation steps 1012, 1014, 1020, and 1022. If it is invalid, the cenfralized postage-issuing computer system 356 will fransmit a Boolean false to the postage validation computer system 362, which will then store the results of the validation process as being invalid at step 1020.

The use of an fracking JD as an indexing identifier not only allows the postal service to validate the postage on mail pieces that bear the fracking LD, it provides the recipient of the mail piece a means for verifying that the mail piece was sent from a trusted individual. Referring to Figs. 34 and 35, a means is provided for allowing a mail recipient to enter a fracking number (Fig. 34) and obtaining identification information concerning the sender of the mail piece bearing the tracking number (such as, e.g., the name of the sender, employer of sender, if applicable, and the address and zip code of the sender) and related postage information (such as, e.g., the date the mail piece was sent, the weight of the mail piece, mail class, etc.) (Fig. 35). The centralized postage-issuing computer system 356 illustrated in Fig. 17, and a mail recipient computer 378 illustrated in Fig. 36 are used to perform this process.

The cenfralized postage-issuing computer 356 is configmed in the same manner as previously described, but now optionally stores information relating to the sender of the mail piece. This can be stored in the postage database 830 or elsewhere, hi reality, as a matter of course, the sender information is routinely stored in the centralized postage-issuing computer 356, as well as transmitted to the USPS, when the sender obtains an account with the postage vendor. Thus, these "meter holders" are known to the postage vendor and the USPS, and can be considered to be trusted individuals or entities.

Importantly, this sender identification information, along with postage information, can be easily retrieved by the centralized postage-issuing computer 356 upon receipt of the indexing identifier, and specifically, an associated fracking JD. With specific reference to Fig. 36, the mail recipient computer 378 is similar to previously described end user computers in that it contains conventional computer hardware, including a user interface 1302, data processing circuitry 1308 (such as, e.g., a Central Processor Unit (CPU)) for executing programs, a communications interface 1310 (such as, e.g., a modem, LAN connection, or Internet connection) for handling communications with the centralized postage-issuing computer system 356 over a commumcations link 384, and local memory 1311. The user interface 1302 is configmed to allow the mail recipient to request sender and related postage information. The local memory 1311, which will typically include both random access memory and non- volatile disk storage, stores a set of sender verification procedures that are embodied in software modules 1312, which includes a sender identification request module 1314 and a communications module 1318. The sender identification request module 1314 is configmed for generating a request for sender identification information, along with associated postage information, h the illustrated embodiment, this request takes the form of a query sfream (e.g., in Extensible Markup Language (XML) format), and contains the unique tracking ED printed on the received mail piece. The communications module 1318 is configmed for handling commumcations with the cenfralized postage-issuing computer system 356 over the communications link 384 (such as, e.g., fransmitting sender identification requests and receiving sender identification information and associated postage information in response thereto). Referring to Fig. 37, and with general reference to Figs. 34-36, the procedmes for verifying the sender of a mail piece will now be described. It is assumed that the tracking LD (as the indexing identifier) and sender identification information, along with the postage information, has already been recorded in the cenfralized postage-issuing computer system 356, and specifically the postage database 830, when the fracking number and postage was issued to the end user (presumably, the sender of the mail piece). At steps 1400-1404, the mail recipient computer 378 generates and fransmits a request for sender identification information to the cenfralized postage-issuing computer system 356 by entering the tracking LD printed on the received mail piece into the user interface 1302, which displays a window similar to the one illusfrated in Fig. 34. The sender identification request module 414 then generates a sender identification request with the associated tracking JD (step 1402). The communications interface 1310 then, under control of the communications module 1318, transmits the sender identification request over the communications link 384 (step 1404).

At steps 1406-1410, the cenfralized postage-issuing computer system 356 then receives the sender identification request, and retrieves and fransmits to the mail recipient computer 378 the sender identification information and associated postage information conesponding to the received mail piece. In particular, the communications interface 822, under control of the communications module 834, receives the sender identification request over the communications link 384 (step 1406). The database management module 836 then retrieves from the postage database 830 the sender identification information and associated postage information conesponding to the received fracking JD (step 1408). The communications interface 822 then, under confrol of the communications module 834, fransmits the sender identification information with the associated postage information over the communications link 384 (step 1410). At steps 1412 and 1414, the mail recipient computer 378 receives the sender identification information and associated postage information from the cenfralized postage- issuing computer system 356 and displays it to the mail recipient, h particular, the communications interface 1302 then, under control of the communications module 1318, receives the sender identification information and associated postage information from the cenfralized postage-issuing computer system 356 over the communications link 384 (step

1412), and the user interface 1302 displays this information to the mail recipient (step 1414), and specifically in a window similar to that illusfrated in Fig. 35. Thus, the mail recipient can determine from this whether the sender is a trusted entity, e.g., if the mail recipient is familiar with the displayed name of the sender. It should be noted that the fact that the cenfralized postage-issuing computer system 356 was capable of retrieving and transmitting the sender identification information to the mail recipient computer 378 for display thereon is a strong indication that the sender is a trusted entity, since individuals or entities that maintain accounts with the postage vendor can typically be considered to be trusted. An insidious individual bent on wreaking havoc through the postal system would typically not maintain a trackable account with a postage vendor.

The use of a fracking JD in the postage indicium or as an indexing identifier not only facilitates the postal service in detecting postage fraud and protecting package recipients from insidious individuals, but also facilitates the postal service in issuing refunds for unused postage. Consider a misprint scenario where an end user attempts to print an Express Mail label and the printing process fails in some way even though the postage was issued. The end user still wants to ship the package, so he/she will take conective measures and print a second Express Mail label. The second label will have the identical destination address (in particular the same ZLP+4+2 zip code, the same postage amount, but a different tracking JD, which is issued on a per-print basis. This scenario creates a database structure that conceptually holds the information set forth in Table 3 below.

Table 3: Express Mail Label Misprint Scenario

A digital signature protects the integrity of the information in the database. It should be noted that the data set forth in Table 3 alone is strongly suggestive of a misprint scenario. But a much stronger case can be made several days later, when the tracking LD's can be statused against the postal authority's (e.g., USPS) fracking system using a simple Internet fransaction. If the end user never mailed a package with the first label (tracking JD 330343434334), it will never achieve a status of "delivered." On the other hand, one should see a "delivered" status on the second fransaction if one waits a sufficient amount of time (e.g., 2-10 days). With reference to Fig. 25, a postage system 380 comprises a centralized postage indicia generation system 382, which includes a multitude of centralized postage-issuing computer systems 386, each of which includes a multitude of end user computers 388. The postage system 380 also generally comprises a postal service 384, which includes a master fracking computer system 390 and a postage refund center 392. The cenfralized postage- issuing computer system 386, end user computer 388, and master tracking computer system 390 communicate with each other over communications links 394 and 396 (such as, e.g., LAN, Internet, or telephone network).

These components are generally similar to the same-named components of the postage system 300, but differ somewhat in that it provides a means for providing refunds for unused postage, hi this embodiment, in response to postage refund inquiries from an account administrator, each cenfralized postage-issuing computer system 386 retrieves previously stored postage fransaction information, which contains, for each postage fransaction, a fracking JD and an associated delivery status. The cenfralized postage-issuing computer system 386 filters the retrieved postage fransaction information for pertinent refund information, and displays it to the account administrator who determines whether there is unused postage to be refunded. The delivery status within the stored postage transaction information is updated by the master fracking computer system 390.

The refund inquiry can take a variety of formats. For example, a refund eligible inquiry can reveal postage transaction information that meets the following criteria: (1) two or more fransactions; (2) none of the fransactions have ever been refunded in the past; (3) issued for the same account; (4) issued on the same day; (5) issued to the same destination; (6) issued for the same service class; (7) issued for the same postage amount; and (8) each fransaction has an associated unique fracking LD. Fig. 26 illustrates exemplary results of a refund eligible inquiry. As can been seen, the display information meets the afore-described criteria. The account administrator can simply select the refund option and the following steps will occm automatically: (1) the end user's account will be credited for the misprint; (2) the misprint postage fransaction information will be date/time stamped in the postage database and flagged as "refunded"; (3) a refund request is issued to postage refund center 392; and (4) the refunded postage transaction is entered into a statusing database, so that the delivery status can be checked for six months.

It should be noted that the date of this query is August 23, 2001, and the postage fransactions in question were completed three days earlier. The USPS delivery status for the first package presents the phrase "Your item was accepted at 10pm on August 21 in Palo Alto, CA 94301. This phrase is misleading in that it infers that the USPS actually took possession of this package. In reality, it only indicates the date/time in which the fracking information was posted to the master tracking computer system. When this message persists for days or weeks, one much conclude that the tracking ED was indeed issued, but the package never entered the postal system. As another example, an audit inquiry can reveal all postage transaction information in a specific user account.

This process provides a complete audit trail even through there is no mail piece specimen. The process not only has utility for misprint scenarios that do not produce a scannable specimen, but it can also be used for misprints that do produce a scannable specimen. Normally, the specimen must be mailed to the postage vendor, which involves an additional mailing expense for the end user, as well as an additional effort for both end user and postage vendor. This process would allow end users to simply destroy misprint specimens if they met the refund criteria listed above. In essence, the evidence supporting the refund is electronic and not paper-based.

It should be noted that the entire process is enabled by the confluence of the cenfralized postage system concept and the unique fracking JD. Mail pieces devoid of a unique fracking JD would not be eligible for this refund process, nor would mail pieces created by postage metering technologies, which are not cenfralized (e.g., conventional postage meters or PC-postage meters that draw upon a local "vault" of funds to create postage indicia).

Means can also be provided to automatically poll the delivery status of a "refunded" mail piece after the refund is processed. This process will continue for a period of several months. If the master fracking computer system suddenly shows a change in delivery status for that refunded mail piece, an automated alert is forwarded to the postal authorities and an investigation can be launched.

A refund inquiry can also be in the form of an audit review of all postage transactions in a user account. Fig. 27 illustrates exemplary results of an audit review. The account adminisfrator can review the list of postage fransactions for duplicate postage transactions. Once a duplicate postage fransaction is suspected, the account administrator can click "Get Status" to determine if the mail piece associated with either of the duplicate postage transactions has been delivered. A refund inquiry can also be in the form of a refund pattern audit. Fig. 28 illustrates exemplary results of a refund pattern audit performed on the customers of a particular postage vendor. As can be seen, the account administrator can determine the refund percentage (by piece and total postage amount) of each customer.

Turning now to Figs. 29 and 30, the structural details of the postage system 380 will now be described. Each end user computer 388 is similar to the previously described end user computer 308 illustrated in Fig. 4, and will thus not be described in further detail here. With specific reference to Fig. 29, each centralized postage-issuing computer system 386 comprises data processing circuitry 1120 (such as, e.g., a Cenfral Processor Unit (CPU)) and a communications interface 1122, which are similar to the same-named components of the previously described centralized postage-issuing computer system 305 and will thus not be described in further detail. The centralized postage-issuing computer system 386 further comprises a local memory 1124, which is similar to the local memory 424 of the previously described cenfralized postage-issuing computer system 305, with the exception that it includes postage dispensing/refund eligibility modules 1126 that are configmed to additionally store and retrieve postage transaction information that includes a tracking LD and an associated delivery status for that fracking ID. The local memory 1124 further includes, in addition to a customer database 1128 and a finance database 1132, a postage database 1130 for storing the fracking JD and associated delivery status in addition to other postage information previously described with respect to the postage database 430. The cenfralized postage-issuing computer system 386 further comprises a user interface 1123, which includes a keyboard 1125 and a display 1127, which as will be described below, allows the account administrator to issue a refund inquiry.

Specifically, the postage dispensing/refund eligibility modules 1126 include a communications module 1134, database management module 1136, tracking JD request module 1138, postage indicium request validation module 1140, postage indicium generation module 1142, delivery status request module 1143, filtering module 1145, refund inquiry module 1147, and refund display module 1149. The delivery status request module 1143 is configured for generating a request for the delivery status for each fracking JD stored in the postage database 1130. The filtering module 1145 is configmed for variously generating refund information by filtering and formatting the postage fransaction information retrieved from the postage database 1130, as will be described in further detail below, hi addition to being configured for providing the communications previously described with respect to the communications module 434, the commumcations module 1134 is configured for transmitting delivery status requests to, and receiving confirmatory delivery status information from, the master fracking computer system 890 over the communications link 896.

The database management module 1136 is configmed for storing and retrieving pertinent information in and from the customer database 1128, postage database 1130, and finance database 1132. This function includes storing and retrieving a fracking JD and an associated delivery status, and updating that associated delivery status with confirmatory delivery status information received from the master tracking computer system 890. As will be described in further detail, the confirmatory delivery status information indicates whether a mail piece canying a fracking JD has, in fact, been delivered. The refund inquiry module 1147 is configured for generating an inquiry for postage refund information, hi the illustrated embodiment, the inquiry contains a user account LD and password and the refund inquiry, which as previously discussed, can include various types. The refund display module 1149 is configured for displaying on the display 1127 the postage refund information filtered by the filtering module 1145.

The fracking JD request module 1138, postage indicium request validation module 1140, and postage indicium generation module 1142 (and conesponding private key 1144) are configmed to perform the same functions described with respect to the fracking JD request module 438, postage indicium request validation module 440, and postage indicium generation module 442 (and conesponding private key 444), and will thus not be described in further detail.

Alternatively, a cenfralized postage-issuing computer system, in combination with the refund inquiry functionality, can be constructed similarly to the cenfralized postage-issuing computer system 307, wherein fracking LD's are issued to end user computers by the centralized postage-issuing computer system from a pool of pre-stored unassigned fracking LD's, or even more alternatively, wherein no fracking ID issuing functionality, in which case, the master fracking computer system directly issues fracking LD's to the end user computer. A cenfralized postage-issuing computer system, in combination with the refund inquiry functionality, can be constructed similarly to the centralized postage-issuing computer system 356, wherein self-validating postage indicia are stored in the centralized postage-issuing computer system and indexing identifiers are fransmitted to the end user computers. Referring specifically to Fig. 30, the master fracking computer system 390 comprises data processing circuitry 1164 (such as, e.g., a Cenfral Processor Unit (CPU)) and a communications interface 1166, which are similar to the same-named components of the previously described master tracking computer system 310 and will thus not be described in further detail. The master fracking computer system 390 further comprises a local memory 1168, which is similar to the local memory 468 of the previously described master fracking computer system 310, with the exception that it includes fracking information maintenance modules 1170 that, in addition to generating and maintaining unique tracking LD's, keep track of the delivery status of the mail pieces carrying these fracking LD's. The local memory 468 further includes a fracking information database 1172, which stores unique fracking LD's and postage information, including the delivery status associated with the fracking LD's.

The tracking information maintenance modules 1170 include a communications module 1174, tracking ID allocation module 1176, database management module 1178, and refunded postage polling module 1180. In addition to being configmed for providing the commumcations previously described with respect to the communications module 474, the communications module 1174 receives delivery status requests from, and transmits confirmatory delivery status information to, each centralized postage-issuing computer system 886 over the communications links 896. The confirmatory delivery status information is obtained from tracking stations (not shown), which scan tracked mail pieces when they are delivered. The tracking JD allocation module 1176 is configured for performing the same functions as the fracking JD allocation module 476 previously described in the master fracking computer system 310. The database management module 1178 is configured for storing and retrieving assigned fracking LD's and associated postage information (including delivery status) to and from the fracking information database 1172. The database management module 1178 is further configmed for updating the tracking information database 1172 with refund information. That is, if a specific postage transaction has been refunded, the database management module 1178 will associate a refund indicator with the postage information relating to the specific postage fransaction. The refunded postage polling module 1180 periodically polls the tracking information database 1172 to determine if a mail piece associated with any refunded postage fransaction has been delivered.

Referring to specifically Fig. 31, and with general reference to Figs. 29 and 30, the procedure for accumulating and updating the postage fransaction information, including the tracking LD's and associated delivery status, will now be described. At step 1200, fracking ID's are issued and applied to a multitude of mail pieces, as previously described. Specifically, the fracking LD's can be indirectly issued from the master tracking computer system 390 to the end user computers 388 via the cenfralized postage-issuing computer system 386, as in steps 500-525 of Fig. 9. Alternatively, the tracking LD's can be directly issued from the cenfralized postage-issuing computer system 386, as in steps 528-544 of Fig. 10. Even more alternatively, the tracking LD's can be directly issued from the master tracking computer system 390 to the end user computers 388, as in steps 546-578 of Fig. 12. At step 1202, self- validating postage indicia are dispensed and applied to the mail pieces, which is described in detail as steps 600-622 of Fig. 13.

At step 1204, the postage transaction information, along with the fracking LD's and associated delivery status, is recorded. Specifically, the database management module 1136 stores the postage transaction information in the postage database 1130. At step 1206, the multitude of mail pieces are processed through the postal authority, which in this case, is the USPS. At step 1208, the postal authority, upon delivery of the mail pieces to their intended destination, reads the tracking ID's on the mail pieces. At step 1210, this delivery information is fransmitted to and recorded in the master fracking computer system 390. Specifically, the database management module 1178 updates the confirmatory delivery status information in the tracking information database 1172 by changing the status from "accepted" to "delivered."

At steps 1212 and 1214, the centralized postage-issuing computer system 386 generates and fransmits a delivery status request to the master fracking computer system 390. Specifically, the delivery status request module 1143 generates a delivery status request (step 1212), and the communications interface 1122 then, under confrol of the communications module 1134, fransmits the delivery status request over the commumcations link 396 (step 1214). At steps 1216-1220, the master tracking computer system 390 receives the delivery status request from the cenfralized postage-issuing computer system 386 and fransmits the confirmatory delivery status information to the cenfralized postage-issuing computer system 386. Specifically, the communications interface 1166, under confrol of the communications module 1174, receives the delivery status request over the communications link 396 (step 1216). The database management module 1178 then retrieves the confirmatory delivery status information from the tracking information database 1172 (step 1218), and the communications interface 1166 then, under confrol of the communications module 1174, transmits the confirmatory delivery status information over the communications link 316 (step 1220). Alternatively, the confirmatory delivery status information can periodically be downloaded from the master fracking computer system 390 without prompting by the cenfralized postage-issuing computer system 386. At steps 1222 and 1224, the centralized postage-issuing computer system 386 receives the confirmatory delivery status information from the master tracking computer system 310 and updates the delivery status within the stored postage fransaction information with the confirmatory delivery status information. In particular, the communications interface 1222, under confrol of the communications module 1234, receives the confirmatory delivery status information over the communications link 396 (step 1222). The database management module 1136 then updates the delivery status within the postage database 1130 (step 1224). If the confirmatory delivery status information indicates that the mail piece carrying the fracking ED has been delivered, the delivery status associated with that fracking ED will be updated as delivered. If the confirmatory delivery status information indicates that the mail piece canying the tracking ED has not been delivered, the delivery status associated with that fracking LD will be updated as not delivered.

Referring to specifically Fig. 32, and with general reference to Fig. 29, the procedmes for issuing a refund will now be described. At step 1230, the account adminisfrator operates the user interface 1123 of the cenfralized postage-issuing computer system 386 to make a refund inquiry. The type of refund inquiry can be, e.g., any of the three refund inquiries described above (refund eligible inquiry, audit review, or refund pattern audit), but for purposes of the following explanation the refund eligible inquiry will be described. At step 1232, the database management module 1136 retrieves for a specific user account the postage fransaction information from the postage database 1130. At step 1234, the filtering module 1145 selects the postage fransaction information representing duplicative postage fransaction. In particular, it selects the postage transactions that carry fracking LD's that have never been refunded in the past, that are issued for the specific user account, and that have identical key postage transaction items, i.e., postage fransaction date, destination zip code, service class, and postage amount. At step 1236, the filtering module 1145 then determines if any of the delivery statuses for the selected postage fransactions indicates that a mail piece has been delivered. If so, it is determined that a refund for that postage fransaction is forthcoming. In this case, the database management module 1136, at step 1238, credits the user's account for the misprint in the finance database 1132. At step 1240, the database management module 1136 then date/time stamps the misprint postage fransaction in the postage database 1130. In this manner, the filtering module 1145 will filter out this refunded postage fransaction in the future, so that it is not refunded multiple times. At step 1242, the account adminisfrator issues a refund request to the postage refund center 392 of the postal authority (e.g., USPS). At steps 1244 and 1246, the postal authority then enters the refunded postage fransaction into the master fracking computer system 390, where the delivery status can be checked for six more months. In particular, the database management module 1178 will associate a refund indicator with the postage information relating to the refunded postage fransaction (step 1244), and the refunded postage polling module 1180 periodically polls the tracking information database 1172 to determine if a mail piece associated with any refunded postage transaction has been delivered (step 1246).

It should be noted that the refund process even allows an end user to initiate a refund inquiry without intervention by the account adminisfrator. h this case, the end user will would have to wait the required minimum time to ensme the "never mailed package" doesn't show up on the tracking system, but then the process is so automatic that the refund could be instituted entirely without an account administrator's intervention.

Although particular embodiments of the present inventions have been shown and described, it will be understood that it is not intended to limit the present inventions to the prefened embodiments, and it will be obvious to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the present inventions. Thus, the present inventions are intended to cover alternatives, modifications, and equivalents, which may be included within the spirit and scope of the present inventions as defined by the claims. All publications, patents, and patent applications cited herein are hereby incorporated by reference in their entirety for all purposes.

Claims

CLAIMS What is claimed is:

I . A method of providing a unique postage indicium for use in a postal system, comprising: generating a unique postage indicium having a character string that is unique within the postal system; deriving a digital signatme from the unique character string; and associating the digital signatme with the unique postage indicium to generate a self- validating unique postage indicium.

2. The method of claim 1 , wherein the unique character string comprises a fracking LD.

3. The method of claim 1 , wherein the digital signature association comprises attaching the digital signatme to the unique postage indicium.

4. The method of claim 1 , further comprising applying the self- validating unique postage indicium to a mail piece.

5. The method of claim 1, further comprising applying the self- validating unique postage indicium to a mail piece in a barcode format.

6. The method of claim 4, wherein the mail piece is a package.

7. The method of claim 4, wherein the mail piece is an envelope.

8. The method of claim 4, wherein the unique character string is also applied to the mail piece independently of the self- validating unique postage indicium.

9. The method of claim 1, wherein the digital signature is generated by applying a private key to the unique postage indicium.

10. The method of claim 1, wherein the unique character string originates from a single database within the postal system.

I I . The method of claim 1 , wherein the postal system is the United States Postal Service.

12. The method of claim 1, wherein the unique postage indicium further has one or more items selected from the group consisting of an indicia version number, algorithm identification, certificate serial number, device identification, ascending register, postage, date of mailing, originating zip code, software identification, descending register, and rate category.

13. A method of detecting postal fraud in a postal system, comprising: receiving a plmality of mail pieces within the postal system, each carrying a self- validating postage indicium containing a postage indicium having a character string, and containing a digital signature derived from the character string; reading each self- validating postage indicium to obtain the postage indicium and digital signature; validating each postage indicium by determining if the digital signature is consistent with the character string; and comparing all of the character strings obtained from the postage indicia.

14. The method of claim 13, wherein each character string comprises a fracking JD.

15. The method of claim 13 , wherein each self- validating postage indicium is embodied in a barcode format, and the self-validating postage indicium is read with a barcode reader.

16. The method of claim 13, wherein each digital signature is generated with a private key, and the postage indicium authentication comprises applying a conesponding public key to each digital signature.

17. The method of claim 13, further comprises storing the character strings obtained from the postage indicia in a single database.

18. The method of claim 13, wherein the postal system is the United States Postal Service.

19. The method of claim 13 , wherein postal fraud is determined if two of the character strings match.

20. The method of claim 13, wherein the postage indicium has postage information in addition to the character string, and the digital signatme is derived from the character string and postage information.

21. A method of detecting postal fraud in a postal system, comprising: receiving a mail piece within the postal system, the mail piece canying a self- validating postage indicium containing a postage indicium having a character string, and a digital signature derived from the character string, the mail piece further carrying an expected representation of the character string independent of the self- validating postage indicium; reading the self-validating postage indicium to obtain the postage indicium and digital signature; validating the postage indicimn by determining if the digital signatme is consistent with character string; and comparing the character string obtained from the postage indicium to the expected representation of the character string.

22. The method of claim 21, wherein the character string comprises a tracking JD.

23. The method of claim 21 , wherein the self- validating postage indicimn is embodied in a barcode format, and the self-validating postage indicium is read with a barcode reader.

24. The method of claim 21, wherein the digital signatme is generated with a private key, and the postage indicium authentication comprises applying a conesponding public key to the digital signature.

25. The method of claim 21 , wherein the postal system is the United States Postal Service.

26. The method of claim 21 , wherein postal fraud is determined if the character string obtained from the postage indicia does not match the expected character string representation.

27. The method of claim 21 , wherein the character string obtained from the mail piece is compared with character strings obtained from other mail pieces.

28. The method of claim 27, wherein postal fraud is determined if two of the character strings match.

29. The method of claim 21, wherein the postage indicium has postage information in addition to the character string, and the digital signature is derived from the character string and postage information.

30. A method of providing postage indicia for use in a postal system, comprising: generating a plurality of unique postage indicia having a plmality of character strings unique within the postal system; deriving a plmality of digital signatures from the plurality of unique character strings; and generating a plurality of self- validating unique postage indicia by associating the plurality of digital signatures with the plmality of unique postage indicia.

31. The method of claim 30, wherein all of the steps are performed in a centralized postage-issuing computer system.

32. The method of claim 31 , further comprising: receiving a plurality of postage indicium requests at the centralized postage-issuing computer system from a plmality of end user computers; and fransmitting the plmality of self- validating unique postage indicia from the cenfralized postage-issuing computer system to the plmality of end user computers.

33. The method of claim 32, wherein each of the plmality of postage indicium requests is embodied in a single data stream.

34. The method of claim 32, further comprising receiving the plurality of unique character strings at the cenfralized postage-issuing computer system from a master tracking computer system.

35. The method of claim 32, further comprising receiving the plurality of unique character strings at the cenfralized postage-issuing computer system from the plmality of end user computers.

36. The method of claim 30, wherein all of the steps are performed in a plmality of end user computers.

37. The method of claim 30, wherein the plmality of unique character strings comprises a plurality of unique fracking LD's.

38. The method of claim 30, wherein the digital signature association comprises attaching the plmality of digital signatures to the plmality of unique postage indicia.

39. The method of claim 30, further comprising applying the plmality of self- validating unique postage indicia to a plmality of mail pieces.

40. The method of claim 30, further comprising applying the plmality of self- validating unique postage indicia to a plmality of mail pieces in a barcode format.

41. The method of claim 40, wherein the plmality of mail pieces is a plmality of packages.

42. The method of claim 40, wherein the plmality of mail pieces is a plmality of envelopes.

43. The method of claim 30, wherein the plmality of digital signatures is generated by applying one or more private keys to the plmality of unique character strings.

44. The method of claim 30, wherein the postal system is the United States Postal Service.

45. The method of claim 30, wherein each of plmality of unique postage indicia further has one or more items selected from the group consisting of an indicia version number, algorithm identification, certificate serial number, device identification, ascending register, postage, date of mailing, originating zip code, software identification, descending register, and rate category.

46. A method of providing a postage indicium for use in a postal system, comprising: receiving a unique identifier request from an end user computer; fransmitting a unique identifier to the end user computer in response to the unique identifier request, wherein the unique identifier is unique within the postal system; receiving a postage indicium request from an end user computer; generating a unique postage indicium canying the unique identifier; deriving a digital signature from the unique identifier; generating a self- validating unique postage indicium by associating the digital signature with the unique postage indicium; and fransmitting the self-validating unique postage indicium independently from the unique identifier fransmitted in response to the unique identifier request.

47. The method of claim 46, wherein all of the steps are performed in a cenfralized postage-issuing computer system.

48. The method of claim 47, further comprising receiving the unique identifier at the centralized postage-issuing computer system from a master fracking computer system.

49. The method of claim 48, further comprising fransmitting another unique identifier request from the cenfralized postage-issuing computer system to the master fracking computer system in response to receipt of the unique identifier request from the end user computer.

50. The method of claim 48, further comprising storing the received unique identifier within the centralized postage-issuing computer system prior to receiving the unique identifier request.

51. The method of claim 46, wherein the unique identifier request is received at a master fracking computer system, the unique identifier is transmitted from the master fracking computer system, and the remaining steps are performed in a cenfralized postage- issuing computer system, the method further comprising receiving the unique identifier at the cenfralized postage-issuing computer system from the end user computer.

52. The method of claim 46, wherein the unique identifier is a single unique character string.

53. The method of claim 52, wherein the unique identifier comprises a unique fracking JD.

54. The method of claim 46, wherein the unique identifier comprises two or more character strings.

55. The method of claim 54, wherein the unique identifier comprises a postage vendor JD, user account number, and piece count.

56. The method of claim 46, wherein the digital signature association comprises attaching the digital signature to the unique postage indicium.

57. The method of claim 46, further comprising: receiving the unique identifier at the end user computer; receiving the self- validating unique postage indicium at the end user computer; and applying the receiving unique identifier and self-validating unique postage indicium to a mail piece.

58. The method of claim 57, wherein the received unique identifier is applied to the mail piece in a one-dimensional barcode format, and the self-validating unique postage indicium is applied to the mail piece in a two-dimensional barcode format.

59. The method of claim 57, wherein the mail piece is a package.

60. The method of claim 57, wherein the mail piece is an envelope.

61. The method of claim 46, wherein the digital signature is generated by applying a private key to the unique identifier.

62. The method of claim 46, wherein the postal system is the United States Postal

Service.

63. The method of claim 46, wherein the unique postage indicium further has one or more items selected from the group consisting of an indicia version number, algorithm identification, certificate serial number, device identification, ascending register, postage, date of mailing, originating zip code, software identification, descending register, and rate category.

64. A postage indicia generation system for implementation with a postal system, comprising: an end user computer; a cenfralized postage-issuing computer system; a communications link connecting the end user computer with the cenfralized postage-issuing computer system; wherein the end user computer is configmed for transmitting a postage indicium request to the centralized postage-issuing computer system over the communications link, and the cenfralized postage-issuing computer system is configmed for generating and transmitting a self- validating unique postage indicium to the end user computer over the cornmunications link, the self-validating unique postage indicium containing a character string unique to the postal system and a digital signature derived from the unique character string.

65. The system of claim 64, further comprising: a master fracking computer system; and another communications link connecting the centralized postage-issuing computer system with the master tracking computer system; wherein the master tracking computer system is configmed for fransmitting the unique character string to the cenfralized postage-issuing computer system over the other communications link.

66. The system of claim 65, wherein the cenfralized postage-issuing computer system is further configured for fransmitting a unique identifier request to the master fracking computer system over the communications link in response to the postage indicium request.

67. The system of claim 66, wherein the centralized postage-issuing computer system is further configured for storing the received character string within the centralized postage-issuing computer system prior to the postage indicium request.

68. The system of claim 64, further comprising: a master fracking computer system; and another communications link connecting the end user computer with the master fracking computer system; wherein the end user computer is configured for transmitting a unique identifier request to the master fracking computer system over the other communications link, for receiving the unique character string from the master fracking computer system over the other communications link, and for transmitting the unique character string to the centralized postage-issuing computer system over the communications link.

69. The system of claim 64, further comprising: a plurality of end user computers; a plmality of communications links connecting the plurality of user computers with the cenfralized postage-issuing computer system; wherein the plurality end user computers is configured for fransmitting a plmality of postage indicium requests to the cenfralized postage-issuing computer system over the plmality of communications links, and the centralized postage-issuing computer system is configmed for generating and fransmitting a plmality of self- validating unique postage indicia to the plmality of end user computers over the plmality of cornmunications links, the plmality of self- validating unique postage indicia containing a plmality of character strings unique to the postal system and a plmality of digital signatures derived from at least portions of a plmality of unique postage indicia containing the plmality of unique character strings.

70. The system of claim 69, further comprising: a master fracking computer system; and another communications link connecting the cenfralized postage-issuing computer system with the master fracking computer system; wherein the master fracking computer system is configured for fransmitting the plmality of unique character strings to the cenfralized postage-issuing computer system over the other communications link.

71. The system of claim 69, further comprising: a master fracking computer system; and another plmality of communications links connecting the plmality of end user computers with the master fracking computer system; wherein the plurality of end user computers is configured for transmitting a plmality of unique identifier requests to the master fracking computer system over the other plmality of communications links, for receiving the plmality of unique character strings from the master fracking computer system over the other plmality of communications links, and for fransmitting the plmality of unique character strings to the centralized postage-issuing computer system over the plmality of communications links.

72. The system of claim 64, wherein the unique character string comprises a unique fracking JD.

73. The system of claim 64, wherein the end user computer is configmed for applying the self-validating unique postage indicium to a mail piece.

74. The system of claim 64, wherein the cenfralized postage-issuing computer system is configmed for applying a private key to the unique character string to generate the digital signature.

75. The system of claim 64, wherein the postal system is the United States Postal Service.

76. The system of claim 64, wherein the unique postage indicium further has one or more items selected from the group consisting of an indicia version number, algorithm identification, certificate serial number, device identification, ascending register, postage, date of mailing, originating zip code, software identification, descending register, and rate category.

77. A centralized postage-issuing computer system for issuing postage indicia within a postal system, comprising: data processing circuitry; a database storing a plmality of user accounts; a communications module, when executed by the data processing circuitry, configured for receiving a postage indicium request from an end user computer; and a postage indicium generation module, when executed by the data processing circuifry, configured for generating a self- validating unique postage indicium in response to the postage indicium request, the self- validating unique postage indicium containing a character string unique to the postal system and a digital signatme derived from the unique character string.

78. The cenfralized postage-issuing computer system of claim 77, wherein the communications module is further configured for transmitting the self- validating unique postage indicium to the end user computer.

79. The cenfralized postage-issuing computer system of claim 77, wherein the postage indicium generation module comprises: a unique postage indicium generation submodule for generating the unique postage indicium; a digital signature generation submodule for generating the digital signature; and an association submodule for associating the digital signature with the unique postage indicia to generate the self-validating unique postage indicium.

80. The cenfralized postage-issuing computer system of claim 77, wherein the communications module is further configured for receiving the unique character string from a master fracking computer system.

81. The cenfralized postage-issuing computer system of claim 80, wherein the communications module is further configured for transmitting a unique identifier request to the master tracking computer system in response to receiving the unique identifier request from the end user computer.

82. The cenfralized postage-issuing computer system of claim 80, further comprising a database management module for storing the received character string in the database prior to receiving the unique identifier request from the end user computer.

83. The centralized postage-issuing computer system of claim 77, wherein the communications module is further configured for receiving the unique character string from the end user computer.

84. The cenfralized postage-issuing computer system of claim 77, wherein the communications module is configured for receiving a plmality of postage indicium requests from a plurality of end user computers; and wherein the unique postage indicia module is configmed for generating a plmality of self- validating unique postage indicia in response to the plmality of postage indicium requests, the plmality of self- validating unique postage indicia containing a plmality of character strings unique to the postal system and a plurality of digital signatures of the plmality of unique character strings.

85. The cenfralized postage-issuing computer system of claim 84, wherein the communications module is further configured for receiving the plmality of unique character strings from a master fracking computer system.

86. The cenfralized postage-issuing computer system of claim 84, wherein the communications module is further configmed for receiving the plmality of unique character strings from the plmality of end user computers.

87. The centralized postage-issuing computer system of claim 77, wherein the unique character string comprises a unique fracking JD.

88. The cenfralized postage-issuing computer system of claim 77, wherein the cenfralized postage-issuing computer system comprises a private key, and the postage indicium generation module is further configmed for applying the private key to the unique character string to generate the digital signatme.

89. The cenfralized postage-issuing computer system of claim 77, wherein the postal system is the United States Postal Service.

90. The cenfralized postage-issuing computer system of claim 77, wherein the unique postage indicium further has one or more items selected from the group consisting of an indicia version number, algorithm identification, certificate serial number, device identification, ascending register, postage, date of mailing, originating zip code, software identification, descending register, and rate category.

91. A method of indexing a postage indicium within a database of a cenfralized postage-issuing computer system, the method comprising: generating a postage indicium associated with a mail piece; associating an indexing fracking JD with the postage indicium; and storing the indexed postage indicium within the database.

92. The method of claim 91 , wherein the indexing fracking ED is unique within a postal service.

93. The method of claim 92, wherein the postal service is the United States Postal

Service.

94. The method of claim 91 , wherein the postage indicium comprises one or more items selected from the group consisting of postage amount, date and time of postage information creation, service class, optional data advance, and delivery zip code.

95. The method of claim 91 , further comprising: deriving a digital signatme from the postage indicium; associating the digital signature with the postage indicium to generate an indexed self- validating postage indicium; and storing the indexed self- validating postage indicium within the centralized postage- issuing computer system.

96. The method of claim 95, wherein the digital signature association comprises attaching the digital signature to the postage indicium.

97. The method of claim 95, wherein the digital signatme is generated by applying a private key to the postage indicium.

98. The method of claim 95, wherein the indexed self- validating postage indicium is generated within a physically secme coprocessor device.

99. The method of claim 91 , further comprising: receiving an indexing identifier request from an end user computer; and fransmitting the indexing fracking JD to the end user computer.

100. The method of claim 91 , further comprising: receiving a postage indicium request containing the indexing fracking LD from a postal authority; retrieving the indexed postage indicium from the database based on the received indexing fracking ID; and fransmitting the indexed postage indicium to the postal authority.

101. The method of claim 91 , further comprising: generating a plurality of postage indicia associated with a plurality of mail pieces; associating a plmality of indexing fracking LDs with the plurality of postage indicia; and storing the plmality of indexed postage indicia within the database.

102. The method of claim 101, further comprising: receiving a plmality of indexing identifier requests from a plmality of end user computers; and fransmitting the plmality of indexing fracking LDs to the plmality of end user computers.

103. The method of claim 101, further comprising: receiving a plmality of postage indicium requests containing the plmality of indexing fracking LDs from a postal authority; retrieving the plmality of indexed postage indicia from the database based on the plurality of received indexing tracking LDs; and fransmitting the plmality of indexed postage indicia to the postal authority.

104. A method of validating postage for a postal service, the method comprising: generating a postage indicium associated with a mail piece; associating an indexing fracking JD with the postage indicium; storing the indexed postage indicium within a database; applying the indexing fracking LD to the mail piece; reading the indexing fracking JD on the mail piece; and retrieving the indexed postage indicium from the database based on the read indexing tracking LD.

105. The method of claim 104, wherein the indexing fracking ED is unique within the postal service.

106. The method of claim 105, wherein the postal service is the United States Postal Service.

107. The method of claim 104, wherein the postage indicium comprises one or more items selected from the group consisting of postage amount, date and time of postage information creation, service class, optional data advance, and delivery zip code.

108. The method of claim 104, further comprising: deriving a digital signatme from the postage indicium; associating the digital signature with the postage indicium to generate an indexed self- validating postage indicium; and storing the indexed self- validating postage indicium within the centralized postage- issuing computer system.

109. The method of claim 108, wherein the digital signature association comprises attaching the digital signatme to the postage indicium.

110. The method of claim 108, wherein the digital signature is generated by applying a private key to the postage indicium.

111. The method of claim 108, wherein the indexed self- validating postage indicium is generated within a physically secme coprocessor device.

112. The method of claim 104, wherein the indexing fracking JD is applied to the mail piece in a barcode format, and the indexing fracking ED is read using a barcode reader.

113. The method of claim 112, wherein the barcode format is two-dimensional barcode format.

114. The method of claim 112,wherein the barcode fonnat is a one-dimensional barcode format.

115. The method of claim 104, wherein the indexing fracking ED is applied to the mail piece in a human-readable format, and the indexing fracking JD is read using an optical character reader.

116. The method of claim 104, further comprising generating a plurality of postage indicia associated with a plmality of mail pieces; associating a plmality of indexing tracking LDs with the plmality of postage indicia; storing the plmality of indexed postage indicia within the database; applying the plmality of indexing tracking LDs to the plurality of mail pieces; reading the plmality of indexing tracking LDs on the plmality of mail pieces; and retrieving the plmality of indexed postage indicia from the database based on the plmality of read indexing tracking LDs.

117. A centralized postage-issuing computer system for indexing a postage indicium, comprising: data processing circuifry; a database; a postage indicium generation module, when executed by the data processing circuifry, configured for generating a postage indicium; an indexing module, when executed by the data processing circuifry, configmed for associating an indexing tracking ED with the postage indicium; and a database management module, when executed by the data processing circuitry, configured for storing the indexed postage indicium within the database, and for retrieving the indexed postage indicium from the database based on the indexing tracking ID.

118. The centralized postage-issuing computer system of claim 117, wherem the indexing fracking ED is unique within a postal service.

119. The cenfralized postage-issuing computer system of claim 118, wherein the postal system is the United States Postal Service.

120. The centralized postage-issuing computer system of claim 117, wherein the postage indicium comprises one or more items selected from the group consisting of postage amount, date and time of postage information creation, service class, optional data advance, and delivery zip code.

121. The cenfralized postage-issuing computer system claim 117, wherein the postage indicium generation module is configmed for generating a self- validating postage indicium in response to the indexing identifier request, the indexing module is configmed for associating the indexing fracking ED with the self- validating postage indicium, and the database management module is configured for storing the indexed self- validating postage indicium within the database.

122. The cenfralized postage-issuing computer system of claim 121, wherein the postage indicium generation module comprises: a postage indicium generation submodule for generating the postage indicium; a digital signatme generation submodule for generating the digital signature; and an association submodule for associating the digital signature with the postage indicium to generate the self-validating indexed postage indicium.

123. The cenfralized postage-issuing computer system of claim 117, wherein the database is associated with a physically secme coprocessor device.

124. The centralized postage-issuing computer system of claim 117, further comprising a communications module, when executed by the data processing circuifry, configured for receiving an indexing identifier request from an end user computer, and for fransmitting the indexing fracking JD to the end user computer.

125. The cenfralized postage-issuing computer system of claim 117, further comprising a communications module, when executed by the data processing circuifry, configured for receiving a postage indicium request containing the indexing fracking JD from a postal authority, and for fransmitting the retrieved indexed postage indicium to the postal authority.

126. The cenfralized postage-issuing computer system of claim 117, wherein the postage indicium generation module is configmed for generating a plmality of postage indicia; the indexing module is configured for associating a plurality of indexing fracking LDs with the plmality of postage indicia; and the database management module is configured for storing the plmality of indexed postage indicia within the database, and for retrieving the plmality of indexed postage indicia from the database based on the plmality of indexing tracking LDs.

127. The centralized postage-issuing computer system of claim 126, further comprising a communications module, when executed by the data processing circuifry, configured for receiving a plmality of indexing identifier requests from a plurality of end user computers, and for transmitting the plmality of indexing fracking LDs to the plmality of end user computers.

128. The centralized postage-issuing computer system of claim 126, further comprising a communications module, when executed by the data processing circuitry, configured for receiving a plmality of postage indicium requests containing the plurality of indexing fracking LDs from a postal authority, and for fransmitting the plmality of retrieved indexed postage indicia to the postal authority.

129. A method of validating postage in a postal system, comprising: receiving a postage indicium request from a postal authority, wherein the postage indicium request carries an indexing fracking JD and is associated with a mail piece inspected by the postage authority; retrieving an indexed postage indicium from a database based on the received indexing fracking ED; and fransmitting the postage indicium to the postal authority.

130. The method of claim 129, wherein the indexing fracking JD is unique within a postal service.

131. The method of claim 130, wherein the postal service is the United States Postal Service.

132. The method of claim 129, wherein the indexed postage indicium comprises one or more items selected from the group consisting of postage amount, date and time of postage information creation, service class, optional data advance, and delivery zip code.

133. The method of claim 129, wherein the indexed postage indicium is a self- validating postage indicium.

134. The method of claim 129, wherein the database is associated with a physically secme coprocessor device.

135. The method of claim 129, further comprising: receiving a plmality of postage indicium requests from a postal authority, wherein the plmality of postage indicium requests carries a plmality of indexing fracking LDs and is associated with a plmality of mail pieces inspected by the postage authority; retrieving a plmality of indexed postage indicia from the database based on the plmality of received indexing tracking LDs; and fransmitting the plmality of postage indicia to the postal authority.

136. A method of indexing sender identification information within a database of a cenfralized postage-issuing computer system, the method comprising: generating sender identification information associated with a mail piece; associating an indexing tracking JD with the sender identification information; and storing the indexed sender identification information within the database.

137. The method of claim 136, wherein the indexing fracking ED is unique within a postal service.

138. The method of claim 137, wherein the postal service is the United States Postal Service.

139. The method of claim 136, wherein the sender identification information comprises one or more items selected from the group consisting of the sender name, sender employer, sender address, and sender zip code.

140. The method of claim 136, further comprising: receiving a sender identification request containing the indexing fracking ED from a mail recipient computer; retrieving the sender identification information from the database based on the received indexing tracking ED; and fransmitting the sender identification information to the mail recipient computer.

141. The method of claim 136, further comprising: generating a sender identification information associated with a plmality of mail pieces; associating a plmality of indexing tracking LDs with the sender identification information; and storing the sender information within the database.

142. The method of claim 141, further comprising: receiving a plurality of sender identification requests containing the plmality of indexing tracking EDs from a plmality of mail recipient computers; retrieving the sender identification information from the database based on the plurality of received indexing fracking EDs; and fransmitting the sender identification information to the mail recipient computers.

143. A centralized postage-issuing computer system for indexing sender identification information, comprising: data processing circuitry; a database; an indexing module, when executed by the data processing circuitry, configured for associating an indexing fracking JD with the sender identification information; and a database management module, when executed by the data processing circuitry, configmed for storing the indexed sender identification information within the database, and for retrieving the indexed sender identification information from the database based on the indexing tracking ED.

144. The cenfralized postage-issuing computer system of claim 143, wherein the indexing fracking JD is unique within a postal service.

145. The cenfralized postage-issuing computer system of claim 144, wherein the postal system is the United States Postal Service.

146. The centralized postage-issuing computer system of claim 143, wherein the sender identification information comprises one or more items selected from the group consisting of the sender name, sender employer, sender address, and sender zip code.

147. The centralized postage-issuing computer system of claim 143, further comprising a communications module, when executed by the data processing circuitry, configmed for receiving a sender identification request containing the indexing tracking JD from a mail recipient computer, and for fransmitting the retrieved indexed sender identification information to the mail recipient computer.

148. The cenfralized postage-issuing computer system of claim 143, wherein the indexing module is configmed for associating a plurality of indexing tracking LDs with sender identification information; and the database management module is configmed for storing the indexed sender identification information within the database, and for retrieving the indexed sender identification information from the database based on the plurality of indexing tracking LDs.

149. The cenfralized postage-issuing computer system of claim 148, further comprising a communications module, when executed by the data processing circuifry, configured for receiving a plurality of sender identifications requests containing the plmality of indexing fracking LDs from a plmality of mail recipient computers, and for fransmitting the retrieved indexed sender identification information to the plurality of mail recipient computers.

150. A method of verifying a sender of a mail piece, comprising: receiving a sender identification request from mail recipient computer, wherein the sender identification request carries an indexing fracking JD associated with a mail piece received from a postal authority; retrieving indexed sender identification information from a database based on the received indexing fracking JD; and fransmitting the sender identification information to the mail recipient computer.

151. The method of claim 160, wherein the indexing fracking JD is unique within a postal service.

152. The method of claim 151, wherein the postal service is the United States Postal Service.

153. The method of claim 150, wherein the sender identification information comprises one or more items selected from the group consisting of the sender name, sender employer, sender address, and sender zip code.

154. The method of claim 150, further comprising: receiving a plurality of sender identification requests from a plurality of mail recipient computers, wherein the plmality of sender identification requests carries a plmality of indexing fracking LDs and is associated with a plmality of mail pieces received from a postage authority; retrieving indexed sender identification information from the database based on the plmality of received indexing tracking LDs; and fransmitting the sender identification information to the plmality of mail recipient computers.

155. A method of refunding postage, comprising: storing information for a postage transaction in a database, the postage fransaction information comprising a fracking LD and an associated delivery status; receiving a postage refund inquiry; and retrieving the postage transaction information from the database in response to the postage refund inquiry.

156. The method of claim 155, further comprising refunding the postage based on the retrieved postage transaction information.

157. The method of claim 155, further comprising displaying the postage fransaction information.

158. The method of claim 155, further comprising: receiving confirmatory delivery status information associated with the tracking JD; and updating the delivery status in the database with the confirmatory delivery status information.

159. The method of claim 155, wherein the postage fransaction information further comprises a postage fransaction date.

160. The method of claim 155, wherein the postage fransaction information further comprises a postage fransaction date, postage transaction time, destination zip code, service class, postage amount, and mail piece weight.

161. The method of claim 155, wherein the confirmatory delivery status information is received from a postal authority.

162. The method of claim 155, wherein the postage refund inquiry is received from an account adminisfrator.

163. The method of claim 155, wherein the postage refund inquiry is received from an end user.

164. The method of claim 155, wherein the postage is refunded based on the delivery status contained within the retrieved postage fransaction information.

165. The method of claim 164, wherein the postage is refunded only if the retrieved delivery status indicates that a mail piece associated with the fracking JD has not been delivered.

166. The method of claim 164, wherein the postage is not refunded if the retrieved delivery status indicates that a mail piece associated with the fracking JD has been delivered.

167. The method of claim 155, further comprising: applying the fracking LD to a mail piece; processing the mail piece through a postal authority; reading the tracking LD on the mail piece; and updating the confirmatory delivery status information to indicate that the mail piece has been delivered.

168. The method of claim 167, wherein the postage is not refunded.

169. A method of refunding postage, comprising: storing information for a plmality of postage transactions in a database, the information for each postage transaction comprising a tracking ED, postage fransaction date, and delivery status associated with the tracking ED; associating the stored postage transaction information with a user account; receiving a postage refund inquiry for the user account; retrieving the postage transaction information from the database in response to the postage refund inquiry; and refunding the postage for a first postage transaction only if the delivery status for the first postage fransaction indicates that a mail piece associated with the fracking ID for the first postage fransaction has not been delivered, and the postage fransaction dates for the first and second postage fransactions are the same.

170. The method of claim 169, wherein the information for each postage transaction comprises a destination zip code, service class, and postage amount; and wherein the postage is refunded only if the destination zip codes, service classes, and postage amounts for the first and second postage transactions are the same.

171. The method of claim 169, further comprising: receiving confirmatory delivery status information associated with the plmality of fracking LD's; and updating the plmality of delivery statuses in the database with the confirmatory delivery status information.

172. The method of claim 171, wherein the confirmatory delivery status information is received from a postal authority.

173. The method of claim 169, wherein the postage refund inquiry is received from an account adminisfrator.

174. The method of claim 169, wherem the postage refund inquiry is received from an end user.

175. The method of claim 169, further comprising: applying the plmality of fracking LD's to a plmality of mail pieces; processing the plmality of mail pieces through a postal authority; reading the tracking LD on a mail piece; and updating the confirmatory delivery status information to indicate that the plmality of mail pieces have been delivered.

176. The method of claim 175, wherein the postage is not refunded.

177. A method of providing status for a plmality of mail pieces fracked by a postal authority, comprising: storing information for a plmality of postage transactions in a database, the information for each postage transaction comprising a fracking ED and an associated delivery status; receiving confirmatory delivery status information from the postal authority; and updating the plmality of delivery statuses in the database with the confirmatory delivery status information.

178. The method of claim 177, further comprising associating the stored postage fransaction information with a plmality of user accounts.

179. The method of claim 177, wherein the information for each postage fransaction further comprises a postage transaction date.

180. The method of claim 177, wherein the information for each postage fransaction further comprises a postage fransaction date, postage fransaction time, destination zip code, service class, postage amount, and mail piece weight.

181. The method of claim 177, further comprising: applying the plmality of fracking LD's to a plmality of mail pieces; processing the plmality of mail pieces through a postal authority; reading the plmality of fracking LD's on the plmality of mail pieces; and updating the confirmatory delivery status information to indicate that the plmality of mail pieces have been delivered.

182. A cenfralized postage-issuing computer system for providing status for a plurality of mail pieces fracked by a postal service, comprising: data processing circuifry; a database; a communications module, when executed by the data processing circuitry, configmed for receiving confirmatory delivery status information from a master fracking computer system; and a database management module, when executed by the data processing circuifry, configured for storing information for a plurality of postage transactions in a database, the information for each postage transaction comprising a tracking JD and an associated delivery status, the database management module further configmed for updating the delivery status with the confirmatory delivery status information.

183. The cenfralized postage-issuing computer system of claim 182, further comprising a delivery status request module, when executed by the data processing circuifry, configured for generating a request for the confirmatory delivery status infonnation, wherein the communications module is further configured for fransmitting the request to the master tracking computer system.

184. The cenfralized postage-issuing computer system of claim 182, wherein the database management module is further configured for associating the stored postage fransaction information with a plurality of user accounts.

185. The centralized postage-issuing computer system of claim 182, wherein the information for each postage transaction further comprises a postage transaction date.

186. The cenfralized postage-issuing computer system of claim 182, wherein the information" for each postage fransaction further comprises a postage fransaction date, postage transaction time, destination zip code, service class, postage amount, and mail piece weight.

187. A method of determining whether issued postage has been used, comprising: storing information for a plmality of postage fransactions in a database, the information for each postage transaction comprising one or more postage fransaction items, a tracking JD and an associated delivery status; associating the postage transaction information with a user account; receiving an inquiry for duplicative postage transactions; retrieving the postage transaction information from the database; selecting the postage fransactions in which the one or more postage fransaction items are identical; and determining if any of the delivery statuses for the selected postage transactions indicates that a mail piece has been delivered.

188. The method of claim 187, further comprising displaying the selected postage fransactions to a postal authority.

189. The method of claim 187, further comprising determining that issued postage is unused if the any delivery statuses for the selected postage fransactions indicates that a mail piece has been delivered.

190. The method of claim 187, further comprising displaying the postage fransaction information for the selected postage fransactions.

191. The method of claim 187, wherein the one or more postage fransaction items comprises a postage fransaction date, destination zip code, service class, and postage amount.

192. The method of claim 187, further comprising: receiving confirmatory delivery status information; and updating the delivery statuses in the database with the confirmatory delivery status information.

193. The method of claim 192, wherein the confirmatory delivery status information is received from a postal authority.

194. The method of claim 192, wherein the duplicative postage fransaction inquiry is received from an account adminisfrator.

195. The method of claim 192, wherein the duplicative postage fransaction inquiry is received from an end user.

196. The method of claim 192, further comprising: applying the plmality of fracking ED's to a plmality of mail pieces; processing the plmality of mail pieces through a postal authority; reading the plmality of fracking ID's on the plmality of mail pieces; and updating the confirmatory delivery status information to indicate that the plmality of mail pieces have been delivered.

197. The method of claim 196, further comprising determining that issued postage is not unused.

198. A cenfralized postage-issuing computer system for determining whether issued postage has been used, comprising: data processing circuifry; a database; a commumcations module, when executed by the data processing circuifry, configured for receiving an inquiry for duplicative postage fransactions; and a database management module, when executed by the data processing circuifry, configured for storing information for a plmality of postage transactions in a database, the information for each postage transaction comprising one or more postage transaction items, a tracking JD and an associated delivery status, the database management module further configured for associating the postage fransaction information with a user account; and a filtering module, when executed by the data processing circuitry, configured for selecting the postage fransactions in which the one or more postage fransaction items are identical, and determining if any of the delivery statuses for the selected postage transactions indicates that a mail piece has been delivered.

199. The cenfralized postage-issuing computer system of claim 198, wherein the filtering module is further configmed for determining that issued postage is unused if the any delivery statuses for the selected postage fransactions indicates that a mail piece has been delivered.

200. ' The cenfralized postage-issuing computer system of claim 198, wherein the one or more postage fransaction items comprises a postage fransaction date, destination zip code, service class, and postage amount.

201. The cenfralized postage-issuing computer system of claim 198, wherein the communications module is further configured for receiving confirmatory delivery status information, and the database management module is further configured for updating the delivery statuses with the confirmatory delivery status information.