US20060191822A1 - Apparatus and methods for processing mailpiece information by an identification code server - Google Patents

Abstract

Apparatus and methods consistent with the present invention provide for processing delivery item information in an identification code sorting system by an identification code server. In one embodiment, a primary identification code server receives an identification file containing identification information uniquely corresponding to a delivery item. In this embodiment, the primary identification code server processes the delivery item information and may send the identification file to a secondary identification code server. In another embodiment, a secondary identification code server receives an identification file from a primary identification code server and processes the delivery item information.

Description

RELATED APPLICATIONS
• This is a division of and claims benefit of application Ser. No. 09/652,707, filed Aug. 31, 2000, which claims the benefit of U.S. Provisional Application No. 60/152,194, filed Aug. 31, 1999, all of which are incorporated herein by reference.
BACKGROUND OF THE INVENTION
• 1. Field of the Invention
• The present invention relates to apparatus and methods for identifying and processing mail. More particularly, the present invention relates to apparatus and methods processing mailpiece information by an identification code server.
• 2. Description of the Related Art
• Conventional systems for identifying and processing (e.g., sorting) mail require both human and mechanical operations. Human operations are initially required to load the mail from a mail delivery repository into a mechanical identification and processing system. Mechanical operations then attempt to identify the delivery address for each mailpiece and, if successful, to then process each mailpiece based on the delivery address. Processing a mailpiece can be, for example, sorting the mailpiece. If there is a failure to identify the delivery address of a mailpiece mechanically, human operators are required again to identify the delivery address. Likewise, if there is a failure to process the mailpiece based on the delivery address, human operators are also required again to process the mailpiece. Therefore, conventional systems for identifying and processing mail are dependent upon human operators, if the mechanical systems are unable to identify or process a mailpiece.
• To identify mail with the conventional systems, mail is loaded into a mechanical identification system, which automatically feeds each mailpiece into an optical character reader (OCR) machine. The OCR machine then attempts to “electronically read” the delivery address from the mailpiece in order to place the delivery address in a computer. If the OCR machine cannot read the delivery address (e.g., the ZIP code), the mechanical device rejects the mailpiece. The rejected mailpiece may then be fed into another mechanical device, which presents the mailpiece to a human operator, who “physically reads” the delivery address off the mailpiece and key punches the delivery address into a computer. Once the delivery address has been either electronically or physically read and placed into a computer, the computer prints the delivery address on the mailpiece, using a special code (e.g., a bar code, such as, a POSTNET code).
• To process mail with the conventional systems, mail is loaded into a mechanical processing system, which automatically sorts each mailpiece by the destination address. The majority of conventional mechanical processing systems sort each mailpiece based on a special code, such as, a ZIP code or a bar code (i.e., a POSTNET code). These mechanical processing systems may contain an OCR machine, which can read and sort a mailpiece based on the ZIP code. These mechanical processing systems may also contain a Bar Code Sorter, which can read and sort a mailpiece based on the POSTNET code. If the mechanical processing system cannot read either the ZIP code or the POSTNET code, the system rejects the mailpiece. The rejected mailpiece may then be processed by a human operator. The human operator may then determine why the mechanical processing system rejected the mailpiece, solve the problem (e.g., determine the ZIP code or reaffix the POSTNET code to the mailpiece), and then reload the mailpiece into the mechanical processing system for processing.
• To improve upon these conventional systems for identifying and processing mail, the United States Postal Service developed an automated sorting system, described in U.S. Pat. No. 4,992,649 (the '649 patent), which is herein incorporated by reference. One embodiment of the system disclosed in the '649 patent is a Remote Bar Code System (RBCS). The embodiment of the RBCS described in the '649 patent provides for the electronic sorting of mail using a bar code that is placed on the front of each mailpiece, known as the POSTNET code, and another bar code that is placed on the back of each mailpiece, known as the ITEM code.
• In the RBCS, the POSTNET code corresponds to the delivery address for the mailpiece, and the ITEM code corresponds to the mailpiece itself (i.e., the ITEM code is a means to “identify” each particular mailpiece). The POSTNET code represents a copy of the ZIP code in bar code format, and the POSTNET code can be used to route a mailpiece, if the ZIP code cannot be read. The ITEM code represents a unique code in bar code format, and the ITEM code can be used to identify each particular mailpiece, if the RBCS cannot otherwise identify the mailpiece. For example, in the RBCS, the ITEM code can be linked to an electronic image of the mailpiece taken at the time the mailpiece is marked with the ITEM code by the RBCS. So, if the RBCS cannot identify a mailpiece, the RBCS can recall the electronic image of the mailpiece, which contains a destination address, including the POSTNET code.
• The identification and processing of mail in the RBCS is dependent upon the use of either the POSTNET code or the ITEM code. When each mailpiece is identified by the RBCS, the ITEM code is first stored temporarily until the mailpiece receives the POSTNET code and has been processed by the RBCS. If the POSTNET code becomes illegible during processing, the ITEM code may be used to obtain the POSTNET code. The ITEM code is used to store a copy of the POSTNET code in a short-term memory until the RBCS has processed the mailpiece based on the POSTNET code. However, once the mailpiece has been processed and sorted based on the POSTNET code, the RBCS can no longer access the ITEM code, because the RBCS cannot store the ITEM code locally or transmit the ITEM code to other RBCS sites.
• As a result, a number of problems can arise if the POSTNET code cannot be read by the RBCS. For instance, the POSTNET code on a mailpiece might be illegible as soon as it is applied due to the color or pattern of the mailpiece. If so, the mailpiece may be fed into a letter mail labeling machine that applies a white label to cover the illegible POSTNET code, and then, the mailpiece may be again fed into the RBCS system for identification (and printing of a new POSTNET code on the white label). Additionally, the POSTNET code might be legible when applied, but become illegible during subsequent processing of the mailpiece. Because the ITEM code is only stored until the completion of the initial processing, the RBCS cannot use the ITEM code to identify the POSTNET code during subsequent processing and sorting. Therefore, if the POSTNET code becomes illegible during subsequent processing, the mailpiece can no longer be sorted automatically by the RBCS. These problems with the RBCS result in severe disadvantages, including diminishing the efficiency of the systems for identifying and processing mail and requiring excessive human intervention.
• As indicated above, there are a number of shortcomings incumbent with these conventional systems for identifying and processing mail. It is therefore desirable to overcome these shortcomings by developing apparatus and methods to identify and process mail when the ZIP code is illegible. It is also desirable to overcome these shortcomings by developing apparatus and methods to identify and process mail when the POSTNET code is illegible. It is further desirable to overcome these shortcomings by developing apparatus and methods to identify and process mail when the ITEM code is illegible. It is still further desirable to overcome these shortcomings by developing apparatus and methods to establish a redundant identification code, which may be globally used by a system for identifying and processing mail. It is additionally desirable to overcome these shortcomings by developing apparatus and methods to read an identification code by a system for identifying and processing mail. It is still additionally desirable to overcome these shortcomings by developing apparatus and methods to identify and process mail where a redundant identification code is used with a global system for identifying and processing mail, where one or more nodes of the system are connected via hardware or software.
SUMMARY OF THE INVENTION
• Apparatus and methods consistent with the present invention overcome the shortcomings of the conventional systems by using an identification code on the back of each mailpiece as a redundant source of identification for identifying and processing mail in a mail sorting system.
• Apparatus and methods consistent with the present invention process mailpiece information using a primary identification code server. The primary identification code server receives an identification file containing an identification code and a postal code corresponding to a mailpiece. The primary identification code server then resolves mailpiece information for a mail processing device, using the identification file. The primary identification code server may update a secondary identification code server using the identification file so that the secondary identification code server can resolve mailpiece information for a mail processing device, using the identification file.
• Additional objects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
• It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
• The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments of the invention and, together with the description, serve to explain the principles of the invention.
• FIG. 1 illustrates a simplified overview of the initial components or steps in apparatus or methods for identifying and processing a mailpiece consistent with the present invention;
• FIGS. 2A and 2B illustrate embodiments of a mailpiece, consistent with apparatus or methods for identifying and processing mail consistent with one embodiment of the present invention;
• FIG. 3 shows an embodiment of an ID Tag in greater detail, as shown inFIG. 2B;
• FIG. 4A depicts a simplified overview of a mailpiece as it enters a Post Office in a Remote Bar Code System (RBCS);
• FIG. 4B depicts a simplified overview of a mailpiece as it enters a Post Office in an Identification Code Sorting (ICS) system;
• FIG. 5 shows one embodiment of a Remote Bar Code System (RBCS), as shown inFIGS. 2A and 4A;
• FIG. 6A shows one embodiment of an Identification Code Sorting (ICS) system, as shown inFIGS. 2A and 4B;
• FIG. 6B shows an alternative embodiment of an Identification Code Sorting (ICS) system, as shown inFIGS. 2A and 4B;
• FIG. 7 is a detailed view of one embodiment of the section of an ICS system in which a mailpiece image (including an ID Tag) is processed to determine a POSTNET code (or ZIP code) corresponding to the destination address of a mailpiece, as shown inFIG. 6A;
• FIG. 8 is a block diagram of one embodiment of an Image Control Unit (ICU) in greater detail;
• FIG. 9 is a block diagram of one embodiment of a Remote Computer Reader (RCR) in greater detail;
• FIG. 10 is a block diagram of one embodiment of an Image Buffer in greater detail;
• FIG. 11 is a block diagram of one embodiment of a Keying Site in greater detail;
• FIG. 12 is a block diagram of one embodiment of a Primary Identification Code Server/Secondary Identification Code Server (PICS/SICS) system, as shown inFIGS. 6A and 6B;
• FIG. 13 is a block diagram of one embodiment of a Primary Identification Code Server (PICS), as shown inFIG. 12;
• FIG. 14 shows one embodiment of how a PICS functions, as shown inFIG. 13;
• FIG. 15 is a block diagram of one embodiment of a Secondary Identification Code Server (SICS), as shown inFIG. 14;
• FIG. 15A is a diagram of one embodiment of a plurality of Primary Identification Code Servers operating in national mode;
• FIG. 15B illustrates one embodiment of a process by which the sharing of mailpiece identification files takes place in national mode, as shown inFIG. 15A;
• FIG. 16 depicts one embodiment of a PICS/SICS system incorporating Common Sorter Software;
• FIG. 17 is a block diagram of one embodiment of a Bar Code Sorter (BCS) system using Common Sorter Software to connect to a PICS;
• FIG. 18 illustrates various embodiments of Bar Code Sorters using Common Sorter Software to connect to a PICS/SICS such as the BCS systems shown inFIG. 17;
• FIGS. 19A-19C illustrate one embodiment for a process used by one embodiment of Common Sorter Software during the identification and processing of a mailpiece by any of the Bar Code Sorters (BCS), such as those shown inFIG. 18;
• FIG. 20 is a block diagram of a Bar Code Sorter (BCS) consistent with one embodiment of the present invention, for example, as used by a RBCS, which includes, for example, an RBCS ID Tag Reader;
• FIG. 21 is a block diagram of a Bar Code Sorter (BCS) consistent with one embodiment of the present invention, for example, as used by an ICS system, which includes, for example, a Universal ID Tag Reader;
• FIG. 22 is a block diagram of one embodiment of a Universal ID Tag Reader (UIDTR);
• FIG. 23 illustrates one embodiment of a UIDTR in greater detail, as shown inFIG. 22;
• FIGS. 24A-24D illustrate the operation of one embodiment of a UIDTR while processing a mailpiece, according to one embodiment of the invention;
• FIG. 25 shows optional components of an embodiment of a UIDTR such as the UIDTR inFIG. 22; and
• FIG. 26 shows still additional optional components of another embodiment of a UIDTR, such as the UIDTR inFIG. 22.
DETAILED DESCRIPTION
• Introduction
• Apparatus and methods consistent with the present invention provide for identifying and processing mail using an identification code on a mailpiece as a redundant source of identification information in a mail sorting system. In one embodiment, this information is stored in a temporary database and used for the identification and processing of mail in a Remote Bar Code System (RBCS). In this embodiment, the identification code enables the automation of mail sorting and other processing tasks, reducing costs and delays in mail delivery services. In another embodiment, the identification and processing of mail occurs in an Identification Code Sorting (ICS) system. In this embodiment, a long-term database allows for mail sorting and other processing tasks on a national or global level.
• Reference will now be made in detail to various embodiments of the invention, examples of which are illustrated in the accompanying drawings. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the appended claims.
• Overview of a System for Identifying and Processing Mail
• FIG. 1 illustrates a simplified overview of the initial components or steps in apparatus or methods for identifying and processing a mailpiece consistent with the present invention. InFIG. 1, amailpiece100 is delivered by apostal customer102 to aPost Office104.Mailpiece100 can be, for example, a letter or a package thatpostal customer102 wishes to send to a destination address. To do so,postal customer102 marks mailpiece100 with a destination address and delivers it toPost Office104.Post Office104 can be a United States Postal Service (USPS) Post Office, a USPS mailbox, or any other facility or location capable of receiving a mailpiece or other item for delivery to a destination address using a system for identifying and processing mail.
• POSTNET Code
• FIGS. 2A and 2B illustrate embodiments of a mailpiece, consistent with apparatus or methods for identifying and processing mail consistent with one embodiment of the present invention. As shown inFIG. 2A,mailpiece100 contains two sources of delivery information, adestination address200 and aPOSTNET code202 corresponding todestination address200. For example,POSTNET code202 can correspond to the ZIP code portion ofdestination address200.POSTNET code202 can be placed onmailpiece100 bypostal customer102 or by the USPS at a processing center, e.g.,Post Office104. In systems consistent with apparatus or methods for identifying and processing mail consistent with one embodiment of the present invention,POSTNET code202 can be read and used to routemailpiece100 to a delivery facility, such as a Post Office, corresponding todestination address200 for the delivery information. Therefore, ifdestination address200 is illegible,POSTNET code202 provides an alternative source of delivery information.
• Identification Tag (ID Tag)
• As shown inFIG. 2B, in one embodiment,mailpiece100 includes anidentification code204, also known as an identification tag (ID Tag), which is unique tomailpiece100.ID Tag204 provides an alternative source of delivery information in one embodiment of systems using apparatus or methods for identifying and processing mail consistent with the present invention.ID Tag204 is printed on the back ofmailpiece100 and represents a unique identification source for identifyingmailpiece100.ID Tag204 may be printed onmailpiece100 in fluorescent ink. As described below, in one embodiment of systems consistent with the present invention,ID Tag204 is used as a redundant source of identification throughout all phases of a mail identification and processing system.
• FIG. 3 shows an embodiment of an ID Tag in greater detail, as shown inFIG. 2B. In this embodiment of the present invention,ID Tag204 is represented by IDTag bar code300. IDTag bar code300 can contain bars and spaces indicating various information aboutmailpiece100, including class ofmail304, origin optical character reader (OCR)number306, day of themonth308, time ofday310, andmailpiece sequence number312. Class ofmail code304 can be represented by a single bit, representing either a 0 or a 1 to indicate mail classification.Origin OCR number306 can be a series of 14 bits representing a machine ID number between 1 and 3,999. Day ofmonth code308 can be a series of 7 bits representing a day of the month between 1 and 31. Time ofday code310 can be a series of 7 bits representing a time of day, measured in half hour increments, between 0 and 47.Mailpiece sequence number312 can be a series of 18 bits representing a mailpiece sequence order from 1 to 25,000. In addition, IDTag bar code300 representingID Tag204 also contains a start code (such as a start bit) and a stop code (such as a stop bit). In IDTag bar code300, startcode302 is represented by a single bit and stopcode314 is represented by two bits. In one embodiment of systems consistent with the present invention, the combination of information represented in IDTag bar code300 uniquely identifiesmailpiece100. However,ID Tag204 may be represented by formats other than IDTag bar code300.
• Overview of Code-Based Systems for Identification and Processing Mail
• Overview of RBCS
• FIG. 4A depicts a simplified overview of a mailpiece as it enters a Post Office in a Remote Bar Code System (RBCS). As shown inFIG. 4A,mailpiece100 enters aRBCS500 for identification and processing to a destination address. InRBCS500,mailpiece100 can be identified byPOSTNET code202, which represents the ZIP code of the destination address, orID Tag204, which is stored temporarily withinRBCS500 during the initial identification and processing, as an identification code.RBCS500 actually applies bothPOSTNET code202 andID Tag204 tomailpiece100.RBCS500 first marks mailpiece100 withID Tag204, and thenRBCS500 marks mailpiece100 withPOSTNET code202. Then, aftermailpiece100 has been marked withPOSTNET code202 byRBCS500,mailpiece100 is then sorted inRBCS500 based onPOSTNET code202, providedPOSTNET code202 is legible.
• InRBCS500, ifPOSTNET code202 is not legible,RBCS500 may use a special machine or a manual process to identify andprocess mailpiece100 to a destination address. To use the special machine (described in detail herein),RBCS500 may identify andprocess mailpiece100 based onID Tag204. IfID Tag204 is legible to this special machine,RBCS500 can obtainPOSTNET code202 from a temporary database and thereby identify and continue to processmailpiece100 to the destination address. Specifically, if this occurs,RBCS500 reappliesPOSTNET code202 tomailpiece100 and then again attempts to identify andprocess mailpiece100 to the destination address. Notably, oncemailpiece100 leavesRBCS500,ID Tag204 is no longer stored withinRBCS500. Therefore, oncemailpiece100 has been marked with POSTNET code202 (and has been verified by RBCS500),ID Tag204 can no longer be used to identifymailpiece100.
• Overview of ICS
• FIG. 4B depicts a simplified overview of a mailpiece as it enters a Post Office in an Identification Code Sorting (ICS) system. As shown inFIG. 4B,mailpiece100 enters an ICS system600 for identification and processing to a destination address, likemailpiece100 entersRBCS500. In addition, in ICS system600,mailpiece100 can be identified byPOSTNET code202 andID Tag204, and ICS system600 applies bothPOSTNET code202 andID Tag204 tomailpiece100. And,mailpiece100 is also sorted by ICS system600 based onPOSTNET code202, once ICS system600 has markedmailpiece100 withPOSTNET code202. However, in contrast toRBCS500,ID Tag204 can be used in ICS system600 at any time during the processing ofmailpiece100 fromPost Office104 to the destination address.
• Consistent with one embodiment of the present invention, ICS system600 utilizes computer hardware and software to maintain a long-term database for a plurality ofID Tags204. In ICS system600, ifPOSTNET code202 becomes illegible,ID Tag204 provides a source by which mailpiece100 can be automatically identified and processed in ICS system600 throughout the entire mail identification and processing system, whereby ICS system600 references a long-term database stored within ICS system600. In addition, ICS system600 also enables many advanced processing capabilities based onID Tag204, including, for example, redundant ZIP code confirmation.
• Detailed Description of RBCS
• FIG. 5 shows one embodiment of a Remote Bar Code System (RBCS), as shown inFIGS. 2A and 4A. When mailpiece100 withdestination address200 entersPost Office104 usingRBCS500, as shown inFIGS. 2A and 4A, processing begins at an Input Subsystem (ISS)502. A piece of equipment atISS502, such as a MultiLine Optical Character Reader Input Subsystem, sprays (i.e., prints)ID Tag204 onto the back ofmailpiece100 using, for example, fluorescent ink.ISS502 also takes an image of mailpiece100 (e.g., a digital image) and attempts to resolve the ZIP code portion ofdestination address200, that is,ISS502 attempts to determinePOSTNET code202 in sufficient detail to enable delivery ofmailpiece100 todestination address200. Sufficient detail may be, for example, a ZIP code with 5, 9, or 11 digits. IfISS502 successfully resolves the ZIP code portion ofdestination address200,ISS502 then alsosprays POSTNET code202 corresponding todestination address200 onto the front ofmailpiece100, for example, using nonfluorescent ink. OnceRBCS500 has affixedID Tag204 andPOSTNET code202 tomailpiece100,ISS502 then sends the POSTNET code information fromPOSTNET code202 and the ID Tag information fromID Tag204 to Image Control Unit (ICU)508, where the POSTNET code information fromPOSTNET code202 and the ID Tag information fromID Tag204 is stored in Decision Storage Unit (DSU)514.
• IfISS502 can resolve the ZIP code fromdestination address200, and obtainPOSTNET code202 onmailpiece100,ISS502 then verifiesPOSTNET code202 to confirm thatPOSTNET code202 is legible.POSTNET code202 may not be legible and may result in a verify error, if, for instance,mailpiece100 is a color other than white or has a pattern that obscuresPOSTNET code202. IfISS502 cannot verifyPOSTNET code202,mailpiece100 is sent to anOutput Subsystem504 and marked for processing by a Letter Mail Labeling Machine (LMLM)506. AtLMLM506, a white label is applied over the illegible POSTNET code, andmailpiece100 is manually fed intoOSS504. The white label creates a clear area onmailpiece100, andRBCS500 then reappliesPOSTNET code202 onto the while label onmailpiece100.OSS504 then verifiesPOSTNET code202 to confirm thatPOSTNET code202 is legible. OncePOSTNET code202 is verified,ID Tag204 has no further use.
• IfISS502 cannot resolve the ZIP code fromdestination address200, then the mailpiece image, includingID Tag204, is sent fromISS502 to an Image Control Unit (ICU)508.ICU508 receives delivery address data from aCentral Database510 and forwards the data along with the mailpiece image, includingID Tag204, to a Remote Computer Reader (RCR)512. This delivery address data may include ZIP code data, POSTNET data, or temporary ID Tag files, as described in more detail herein.RCR512 first attempts to use the data from the central database to automatically resolve the ZIP code corresponding tomailpiece100. For example,RCR512 usesID Tag204 to determine if there is a temporary file onmailpiece100 inRBCS500, which contains the ZIP code data. IfRCR512 is successful, it returns the ZIP code data toICU508, where the data is stored in a Decision Storage Unit (DSU)514. IfRCR512 does not successfully resolve the ZIP code corresponding to mailpiece100, the mailpiece image, includingID Tag204, is sent fromICU508 to aKeying Site516, where a human operator views the mailpiece image and keys in the ZIP code data, which is returned toICU508 and stored inDSU514. Therefore, inRBCS500, regardless whetherRCR512 orKeying Site516 resolves the ZIP code data, the ZIP code data, in the form ofPOSTNET code202, is linked toID Tag204. All of this information, which is identified byID Tag204, is temporarily stored inDSU514.
• IfISS502 cannot resolve the ZIP code fromdestination address200, and while the mailpiece image is processed byICU508,mailpiece100 is routed fromISS502 to an Output Subsystem (OSS)504. A Bar Code Sorter atOSS504 readsID Tag204 frommailpiece100 and transmits a lookup request toDSU514. Once the ZIP code has been resolved formailpiece100,DSU514 then retrieves and returns the ZIP code corresponding toID Tag204 toOSS504, andOSS504 then appliesPOSTNET code202 tomailpiece100, if necessary.OSS504 then verifiesPOSTNET code202 to confirm thatPOSTNET code202 is legible. IfOSS504 cannot verifyPOSTNET code202,mailpiece100 is sent toLMLM506 for manual processing as described above.OSS504 then re-sprays and verifiesPOSTNET code202 to confirm thatPOSTNET code202 is legible. OncePOSTNET code202 is verified,ID Tag204 has no further use and is no longer stored inRBCS500.
• Aftermailpiece100 is processed byISS502 andOSS504, initial mail processing ofmailpiece100 byRBCS500 is complete atPost Office104. Ifdestination address200 ofmailpiece100 indicates thatmailpiece100 is local mail, thenRBCS500 directsmailpiece100 to mailcarriers518. However, ifdestination address200 indicates thatmailpiece100 is not local mail, thenRBCS500 dispatchesmailpiece100 via one or more modes oftransportation520 toremote delivery sites522.
• Detailed Description of ICS
• FIG. 6A shows one embodiment of an Identification Code Sorting (ICS) system, as shown inFIGS. 2A and 4B. When mailpiece100 entersPost Office104 using ICS system600, as shown inFIGS. 2A and 4B, processing begins at anISS602. A piece of equipment atISS602, such as a MultiLine Optical Character Reader Input Subsystem,sprays ID Tag204 onto the back ofmailpiece100, for example, using fluorescent ink.ISS602 also takes an image (e.g., a digital image) ofmailpiece100 and attempts to resolve the ZIP code portion ofdestination address200. IfISS602 successfully resolves the ZIP code portion ofdestination address200,ISS602 then sprays POSTNETcode202 corresponding todestination address200 onto the front ofmailpiece100, for example, using nonfluorescent ink. Once ICS system600 has affixedID Tag204 andPOSTNET code202 tomailpiece100,ISS602 then sends the POSTNET code information fromPOSTNET code202 and ID Tag information fromID Tag204 toICU608, where the POSTNET code information fromPOSTNET code202 and the ID Tag information fromID Tag204 is stored inDSU614 andICS Buffer616.
• IfISS602 can resolve the ZIP code fromdestination address200 and obtainPOSTNET code202 onmailpiece100,ISS602 then verifiesPOSTNET code202. This may result in a verify error if, for instance,mailpiece100 is a color other than white or has a pattern that obscuresPOSTNET code202. IfISS602 cannot verifyPOSTNET code202,mailpiece100 is sent to an Output Subsystem (OSS)604.OSS604 determines whethermailpiece100 is bound for an ICS-enabled destination. Ifmailpiece100 is bound for an ICS-enabled destination, then mailpiece100 stays within ICS system600 and does not require initial manual intervention. Therefore, in contrast toRBCS500, a letter mail labeling machine is not necessary in ICS system600. However, ifmailpiece100 is not bound for an ICS-enabled destination, then mailpiece100 is processed as inRBCS500, as described above.
• IfISS602 cannot verifyPOSTNET code202,ISS602 may attempt to resolve the ZIP code fromdestination address200 onmailpiece100. IfISS602 cannot resolve the ZIP code fromdestination address200, then the mailpiece image, includingID Tag204, is sent fromISS602 to an Image Control Unit (ICU)608.ICU608 receives delivery address data from aCentral Database610 and forwards the data along with the mailpiece image, includingID Tag204, to a Remote Computer Reader (RCR)612. This delivery address data may include ZIP code data, POSTNET data, and/or ID Tag files, as described in more detail herein.RCR612 first attempts to use the data from the central database to automatically resolve the ZIP code corresponding tomailpiece100. For example,RCR612 usesID Tag204 to determine if there is a file onmailpiece100 in ICS system600, which contains the ZIP code data. There should be a file for eachmailpiece100, so there should be a file in ICS system600, which allows the ZIP code formailpiece100 to be resolved automatically by ICS system600 without any human intervention. IfRCR612 is successful, it returns the ZIP code data toICU608, where the data is stored in a Decision Storage Unit (DSU)614 and anICS Buffer616. IfRCR612 does not successfully resolve the ZIP code corresponding to mailpiece100, then mailpiece100 is processed as inRBCS500, as described above. Also, ifRCR612 is not successful, ICS system600 may use anImage Buffer618 for priority designation, as described in more detail herein.
• IfISS602 cannot resolve the ZIP code fromdestination address200, and while the mailpiece image is processed byICU608,mailpiece100 is routed fromISS602 toOSS604. A Bar Code Sorter atOSS604 readsID Tag204 frommailpiece100 and transmits a lookup request toDSU614. Once the ZIP code has been resolved formailpiece100,DSU614 then retrieves and returns the ZIP code corresponding toID Tag204 toOSS604, andOSS604 then appliesPOSTNET code202 tomailpiece100, if necessary.OSS604 then verifiesPOSTNET code202 to confirm thatPOSTNET code202 is legible. However, in contrast toRBCS500, even ifOSS604 cannot verifyPOSTNET code202,mailpiece100 can still be identified and processed in ICS system600, ifOSS604 determines thatmailpiece100 is bound for an ICS-enabled destination. In this scenario, ICS system600 simply usesID Tag204 as the identification code (instead of POSTNET code202).
• Therefore, in contrast toRBCS500, ICS system600 provides for the long-term storage ofID Tags204 andcorresponding POSTNET codes202, which allows for the automation of tasks previously required to be performed by human operators. In addition, ICS system600 provides for the sharing of this information throughout all phases of the identification and processing ofmailpiece100. This capability is made possible by Primary Identification Code Server/Secondary Identification Code Server (PICS/SICS)system622. As described below, PICS/SICS system622 enables downstream mailpiece identification and processing based onID Tag204, even ifPOSTNET code202 becomes illegible. As inRBCS500, aftermailpiece100 is processed byISS602 andOSS604 in ICS system600, initial mail processing is complete. Thereafter,mailpiece100 is processed as inRBCS500, as described above.
• FIG. 6B shows an alternative embodiment of an Identification Code Sorting (ICS) system, as shown inFIGS. 2A and 4B. In this embodiment, ifRCR612 does not successfully resolve the ZIP code corresponding to mailpiece100, the mailpiece image is not stored in an image buffer (e.g.,Image Buffer618 inFIG. 6A). Instead,RCR612 sends the mailpiece image toICU608 indicating that the ZIP code has not been resolved, andICU608 transmits the mailpiece image to KeyingSite620. AtKeying Site620, processing occurs as described above with reference toFIG. 6A.
• Overview of Processing for Mailpiece Image
• FIG. 7 is a detailed view of one embodiment of the section of an ICS system in which a mailpiece image (including an ID Tag) is processed to determine a POSTNET code (or ZIP code) corresponding to the destination address of a mailpiece, as shown inFIG. 6A. The mailpiece image (along with ID Tag204), taken atISS602, is passed fromISS602 toICU608 for processing. FromICU608, the mailpiece image (and ID Tag204) is passed toRCR612. Also, Central Database610 (e.g., a USPS master address database) passes data (e.g., POSTNET data and/or ZIP code data) viaICU608 toRCR612.RCR612 processes the mailpiece image to resolve ZIP code data using the data received fromCentral Database610. Generally,RCR612 is able to resolve ZIP code data based on a file contained withinCentral Database610—the file is identified byID Tag204. In effect,ID Tag204 is used to match the mailpiece image to a file inCentral Database610. In ICS system600, in contrast toRBCS500,ID Tag204 may be used to match the proper file inCentral Database610 throughout the identification and processing system.
• Nonetheless, ifRCR612 fails, then the mailpiece image (and ID Tag204) is stored inImage Buffer618 in one embodiment, as shown inFIG. 6A, which may include a priority designation, and is then sent toKeying Site620, where it is processed according to the priority designation (if any). In an alternative embodiment withoutImage Buffer618, as shown inFIG. 6B, ifRCR612 does not resolve the ZIP code corresponding to mailpiece100,RCR612 sends the mailpiece image (and ID Tag204) toICU608 indicating that the ZIP code has not been resolved, andICU608 then transmits this data toKeying Site620.
• During the subsequent processing in ICS system600, when a ZIP code for the mailpiece image is resolved, either byRCR612 orKeying Site620, the ZIP code data is returned toICU608.ICU608 then uses the ZIP code data to resolve the ZIP code formailpiece100. To do this,DSU614 inICU608 sends the ZIP code data toOSS604.ICU608 also saves the ZIP code data in a storage system.ICU608 informsCentral Database610 of the ZIP code data, which is mapped toID Tag204, which maintains a long-term storage capability.ICU608 may also retain a local copy of the ZIP code data, which is mapped toID Tag204, atImage Buffer618. As a result, ICS system600 retains the ability to identify andprocess mailpiece100 automatically throughout the delivery stages in a mail sorting system.
• Detailed Description of Processing for Mailpiece Image
• FIG. 8 is a block diagram of one embodiment of an Image Control Unit (ICU) in greater detail.ICU608 directs the processing of a mailpiece image corresponding to amailpiece100 in ICS system600 to resolve a POSTNET code202 (or ZIP code data), usingID Tag204.ICU608 receives fromISS602 and stores the mailpiece image andID Tag204.ICU608 also receives data, such as a master reference table, fromCentral Database610.Central Database610 can be, for example, a USPS master address database or a USPS address change service database.Central Database610 can also contain identification files corresponding to a plurality ofID Tags204.ICU608 passes the mailpiece image (includingID Tag204, not shown) and the master reference table toRCR612.
• Processing byRCR612 is described below, with reference toFIG. 9. IfRCR612 resolves the identification information, such as, POSTNET code202 (or ZIP code data) corresponding to the mailpiece image,RCR612 passesPOSTNET code202 toICU608, andPOSTNET code202 is stored along withID Tag204 in bothDSU614 andICS Buffer616. IfRCR612 does not resolve the identification information, such as,POSTNET code202, thenRCR612 passes the mailpiece image andID Tag204 toImage Buffer618. Processing byImage Buffer618 is described below, with reference toFIG. 10. At a particular time, such as, for example, the end of a mail sort run or the end of the day,Image Buffer618 passes the mailpiece image (andID Tag204, not shown) toICU608, which passes the mailpiece image to KeyingSite620. Processing byKeying Site620 is described below, with reference toFIG. 11. KeyingSite620 returns an identification file, includingPOSTNET code202, toICU608, where it is stored withID Tag204 in bothDSU614 andICS Buffer616.DSU614 supplies identification information, such asID Tag204 andPOSTNET code202 formailpiece100, toOSS604 during initial mail processing.ICS Buffer616 retains a copy of this identification information locally for ICS system600. A copy ofICS Buffer616 may be sent toCentral Database610 for long-term storage.
• FIG. 9 is a block diagram of one embodiment of a Remote Computer Reader (RCR) in greater detail.RCR612 receives the mailpiece image (includingID Tag204, not shown) and the master reference table fromICU608, as described above with reference toFIG. 8.RCR612 first attempts to compare the mailpiece image to data in the master reference table to resolve a POSTNET code for the mailpiece (i.e., mailpiece100) corresponding to the mailpiece image. In doing so,RCR612 usesID Tag204 to determine if there is a file onmailpiece100, which contains identification information, such as,POSTNET code202, formailpiece100. IfRCR612 succeeds, thenRCR612 sendsPOSTNET code202 toICU608. IfRCR612 does not resolve the identification information, then, in one embodiment,RCR612 assigns a priority designation to the mailpiece image and passes the mailpiece image (includingID Tag204, not shown) and the priority designation toImage Buffer618. Processing byImage Buffer618 is described below, with reference toFIG. 10. In an alternative embodiment (not shown), ifRCR612 does not resolve the POSTNET code,RCR612 can send the mailpiece image or data indicating that the identification information has not been resolved back toICU608. Processing byICU608 is described above, with reference toFIG. 8.
• FIG. 10 is a block diagram of one embodiment of an Image Buffer in greater detail.Image Buffer618 receives aBuffer File1002 containing a mailpiece image (includingID Tag204, not shown) and a priority designation fromRCR612.Image Buffer618stores Buffer File1002. Upon the expiration of a condition (not shown), such as the end of a sort run or the end of the day, or upon receipt of a prompt from (as shown inFIG. 10), for example,RCR612,Image Buffer618 sendsBuffer File1002 toICU608 for processing.Image Buffer618 may also retain a copy of the identification information corresponding to a plurality of mailpieces100 (i.e., a copy of a plurality of Buffer Files1002). Alternatively, in certain other embodiments of ICS system600,Image Buffer618 is not implemented.
• FIG. 11 is a block diagram of one embodiment of a Keying Site in greater detail. In this embodiment,Keying Site620 receives aBuffer File1002 fromICU608 that contains a mailpiece image (includingID Tag204, not shown) and a corresponding priority designation, which is forwarded to a human operator for manual processing according to the priority designation. As shown inFIG. 11, the mailpiece image fromBuffer File1002 is presented to an operator at a keyingstation1102. The operator views the mailpiece image and keys the identification information into a computer atKeying Site620, such as the ZIP code information for the POSTNET code corresponding to the mailpiece image. KeyingSite620 then returns the identification information toICU608 as an identification file. It is to be understood that a priority designation is not necessary. Alternatively,Keying Site620 could process mailpiece images on a first-received, first-processed basis, if priority designations are not used.
• Primary Identification Code Server/Secondary Identification Code Server (PICS/SICS) System
• FIG. 12 is a block diagram of one embodiment of a Primary Identification Code Server/Secondary Identification Code Server (PICS/SICS) system, as shown inFIGS. 6A and 6B. As described above inFIGS. 6A and 6B,ICU608 maintainsICS Buffer616, which stores ID Tags and corresponding POSTNET codes for mailpieces.ICU608 may share this information with PICS/SICS system622. As shown inFIG. 12,ICU608 shares identification information with a Primary Identification Code Server (PICS)1200 via atelecommunications connection1202.PICS1200 in turn shares the identification information with a Secondary Identification Code Server (SICS)1204 via atelecommunications connection1206.
• As shown inFIG. 12,PICS1200 can also communicate with a Value AddedService System1208 viatelecommunications link1210. Value AddedService System1208 can be, for example, a system to track and report the performance of PICS/SICS system622.Telecommunications connections1202,1206, and1210 can be, for example, an Internet connection, a telephone line with a modem, a local area network (LAN), or a wide area network (WAN). In systems consistent with the present invention,PICS1200 can communicate with multiple SICS to share a plurality of identification information about a plurality of mailpieces. As also shown inFIG. 12,PICS1200 communicates with Bar Code Sorters (BCS)1212,1214, and1216.SICS1204 communicates withBCS1218 and1220. Of course, each PICS and SICS can interface with any number of BCS consistent with the present invention. The communication with Bar Code Sorters is described in further detail below, with reference toFIGS. 14 and 15.
• Additionally, as shown inFIG. 12,PICS system1230, which containsPICS1200 andBCS1212,1214, and1216, is in the same physical location, such as, for example, a USPS Mail Processing & Distribution Center. In one implementation, a dedicated ICS local area network connectsBCS1212,1214, and1216 toPICS1200.SICS system1240, which containsSICS1204 andBCS1218 and1220, is in a different physical location, such as, for example, a USPS Associate Office. In one implementation, a dedicated ICS local area network connectsBCS1218 and1220 toSICS1204. Other configurations ofPICS system1230 and/orSICS system1240 are possible.
• FIG. 13 is a block diagram of one embodiment of a Primary Identification Code Server (PICS), as shown inFIG. 12. As described above,PICS1200 communicates withICU608 viatelecommunications connection1202. In one implementation,PICS1200 maintains aLocal.Sat file1306 that includes all of the geographic areas, i.e., ZIP code zones, served byPICS1200.PICS1200 also includes aMode Indicator1308 that can be set to either local or national mode. In local mode,PICS1200 communicates with one or more Bar Code Sorters (BCS)1302, one or more Secondary Identification Code Servers (SICS)1304, and one or more PICS. In national mode,PICS1200 may additionally communicate withPICS1200 via one or more Electronic Post Offices (EPOs) (not shown). National mode is described below, with reference toFIGS. 15A and 15B.
• As shown in the depicted implementation inFIG. 13, to identify information processed betweenICU608 andPICS1200,PICS1200 maintains a Lookup Table1310. Identification files, or ID files, containing ID Tag and POSTNET data, are stored in the identification files in Lookup Table1310. To serve one ormore SICS1304,PICS1200 includes a SICS_ZIPData File Generator1312 and a SICS ServiceArea Table Database1314. SICS_ZIPData File Generator1312 is used byPICS1200 to create a SICS_ZIP Data File (not shown here, but see below) for each SICS connected toPICS1200 by matching identification files from Lookup Table1310 to the service area of each SICS. The service area of each SICS connected toPICS1200, i.e., the geographic area served by each SICS, is stored in a SICS Service Area Table in SICS ServiceArea Table Database1314.
• FIG. 14 shows one embodiment of how a PICS functions, as shown inFIG. 13.PICS1200 receives an identification file, includingID Tag204 andPOSTNET code202, fromICU608 viatelecommunications link1202.PICS1200 stores the identification file in Lookup Table1310. As shown inFIG. 14, eachidentification file1420 contains an identification code (ID code)1422, such as, for example,ID Tag204, and apostal code1424, such as, for example,POSTNET code202. In addition,identification file1420 can include additional information, such as, for example, an image capture time or status bits indicating various aspects of the identification file.PICS1200 contains SICS_ZIPData File Generator1312. SICS_ZIPData File Generator1312 is used byPICS1200 to create aSICS_ZIP Data File1406 for each SICS connected toPICS1200 by matchingidentification files1420 from Lookup Table1310 to the service area of each SICS from SICS ServiceArea Table Database1314.PICS1200 maintains SICS ServiceArea Table Database1314, which includes a set of SICS Service Area Tables corresponding to each SICS served byPICS1200. For example,SICS1404 would have a corresponding SICS Service Area Table1315 in SICS ServiceArea Table Database1314.
• In one implementation of ICS system600, referring toFIG. 14,PICS1200 has two functions. A first function ofPICS1200 is to resolve mailpiece information for Bar Code Sorter (BCS)1402. To do this,BCS1402 reads anidentification code1410 from a mailpiece and sends the identification code (or ID code or ID Tag) toPICS1200, such as, for example, via a dedicated ICS local area network (not shown).PICS1200 looks upidentification code1410 in Lookup Table1310, and returns identification information, i.e., the ZIP code or the POSTNET code, corresponding toidentification code1410 toBCS1402.
• To do so,PICS1200 matchesidentification code1410 with an identification code contained in an identification file, such asidentification code1422 inidentification file1420. Because ICS system600 had previously createdidentification file1420 corresponding to a single mailpiece (using the unique identification code1422),PICS1200 can accurately obtain the identification information usingidentification file1420, which matchesidentification code1422 toidentification code1410. Thereby,PICS1200 can also determine thatpostal code1424 corresponds toidentification code1410.PICS1200 then returnsidentification information1430 toBCS1402. In one embodiment,identification information1430 ispostal code1424. In an alternative embodiment,identification information1430 isidentification code1422. In another alternative embodiment,identification information1430 isidentification file1420. In still another alternative embodiment,identification information1430 can be an entirely different code.
• A second function ofPICS1200 is to share information with one ormore SICS1404. To do this, at predetermined intervals,PICS1200 sends information toSICS1404 via a telecommunications connection. These intervals can be based on time (e.g., every twenty minutes, every hour, etc.) or on another measurement (e.g., once20,000 identification files are stored in Lookup Table1310, etc.).PICS1200 uses SICS_ZIPData File Generator1312 to create aSICS_ZIP Data File1406.SICS_ZIP Data File1406 contains the identification files from Lookup Table1310 for aparticular SICS1404. SICS_ZIPData File Generator1312 uses the appropriate SICS Service Area Table1315 corresponding toSICS1404 to determine which identification files are included inSICS_ZIP Data File1406. For example, in SICS ServiceArea Table Database1314, there is a SICS Service Area Table1315 that identifies the service area for a particular SICS, e.g., the ZIP codes for the zones served bySICS1404. Thus, using this information (for purposes of this example), SICS_ZIPData File Generator1312 collects all identification files (e.g., identification files1407) with the ZIP codes from SICS Service Area Table1315 and createsSICS_ZIP Data File1406. At the predetermined interval (described above),PICS1200 then sendsSICS_ZIP Data File1406 containingidentification files1407 toSICS1404.
• FIG. 15 is a block diagram of one embodiment of a Secondary Identification Code Server (SICS), as shown inFIG. 14. InFIG. 15,SICS1404 performs the same basic function asPICS1200 with respect to Bar Code Sorters.SICS1404 resolves mailpiece information for one or more Bar Code Sorters, e.g., Bar Code Sorter (BCS)1502. To do this,SICS1404 receives aSICS_ZIP Data File1406 fromPICS1200. For example,SICS_ZIP Data File1406 may include a collection ofidentification files1407 corresponding to mailpieces destined for postal codes within the service area ofSICS1404. In one implementation, whenBCS1502 reads anidentification code1510 from a mailpiece,BCS1502 sendsidentification code1510 toSICS1404, such as, for example, over a dedicated ICS local area network (not shown).SICS1404 looks upidentification code1510 inSICS_ZIP Data File1406 and returns identification information, e.g., the ZIP code or the POSTNET code, toBCS1502 in the form ofidentification information1520. Accordingly, in this implementation,BCS1502 can useidentification information1520 to identify and process the mailpiece even if the ZIP code or the POSTNET code is illegible. Thus, likePICS1200,SICS1404 can determine mailpiece information for aBar Code Sorter1502.
• FIG. 15A is a diagram of one embodiment of a plurality of Primary Identification Code Servers operating in national mode. As in local mode, in which a PICS shares mailpiece identification information with one or more SICS and one or more PICS (seeFIG. 13), in national mode, a PICS additionally shares mailpiece identification with other PICS via one or more Electronic Post Offices (EPOs). As shown inFIG. 15A, a plurality ofPICS1505 are connected to a plurality ofEPOs1503. In one implementation,PICS1511,PICS1512, andPICS1513 are connected to ICS ElectronicPost Office West1504, ICS ElectronicPost Office Central1506, and ICS ElectronicPost Office East1508 via a network (not shown). Any number of PICS can be connected to any number of EPOs. This national mode implementation allows for broad interoperability among an unlimited number of PICS and EPOs. For example, as shown inFIG. 15A,PICS1511 may receive identification files for all mailpieces processed by all PICS in an ICS system600. By allowingPICS1511 to communicate with one or more of EPOs1504,1506, and1508, the identification files for mailpieces bound for areas served byPICS1512 andPICS1513 are also sent fromPICS1511 toPICS1512 andPICS1513. Therefore, national mode allows for complete interoperability among all the components of an ICS system600.
• FIG. 15B illustrates one embodiment of a process by which the sharing of mailpiece identification files takes place in national mode, as shown inFIG. 15A. As shown inFIG. 15B, in national mode,PICS1511 collects identification files in Lookup Table1521, as described above.PICS1511 then determines which of the identification files in Lookup Table1521 are served by other PICS/SICS systems using aLocal.Sat file1522, as described above.PICS1511 maintains anEPO.Sat file1523 to define what records are to be sent to other PICS via EPOs. In one embodiment,Local.Sat file1522 can contain a list of all ZIP codes served by PICS1511 (as well as any SICS connected to PICS1511). In this embodiment,EPO.Sat file1523 can be the inverse ofLocal.Sat file1522.PICS1511 can have aNational Mode indicator1514. In national mode,PICS1511 periodically sends these identification files to aprimary EPO1520 via a network connection (not depicted).PICS1511 also sends a copy ofLocal.Sat file1522 toprimary EPO1520.Local.Sat file1522 contains a list of all the ZIP codes served byPICS1511. In one implementation,PICS1511 may also have a secondary EPO for use in caseprimary EPO1520 is unavailable or inoperative (not shown).
• OncePICS1511 has transferred the identification files toEPO1520,EPO1520 collects and stores the identification files in aStorage Buffer1517.EPO1520 also collects and stores any Local.Sat files1522 in a plurality ofTable Buffers1516. Each PICS table1518 inPICS Table Buffer1516 is created using the Local.Sat files received from the plurality of PICS operating in national mode, such as,PICS1511. For example, whenEPO1520 receivesLocal.Sat file1522 fromPICS1511,EPO1520 creates a PICS Table1518 corresponding toPICS1511. Thereafter, in an implementation based on ZIP codes, asEPO1520 receives identification files from other PICS,EPO1520 stores the identification files matching the ZIP codes inPICS Table Buffer1516 in the corresponding PICS Table for each respective PICS (e.g., if the ZIP code matches the ZIP codes in PICS Table1518 corresponding toLocal.Sat file1522, the identification file is matched to PICS Table1518). At predetermined intervals (similar to the predetermined intervals described above),EPO1520 then sends a copy of each PICS Table inPICS Table Buffer1516 to its corresponding PICS. For example, ifEPO1520 collects identification files corresponding toPICS1530 into a PICS Table1519,EPO1520 may send PICS table1519 toPICS1530. Additionally,EPO1520 may also send a copy ofNational.Sat file1515 toPICS1530.National.Sat file1515 is a compilation of all Local.Sat files received byEPO1520.National.Sat file1518 can be used byEPO1520 to monitor all areas services by ICS system600. If a copy is transferred fromEPO1520 toPICS1530,National.Sat file1518 can also be used byPICS1530 to monitor all areas that are served by ICS system600.
• Common Sorter Software
• As described above, as shown inFIGS. 12 and 13, both PICS and SICS exchange information with Bar Code Sorters (BCS). For example,PICS1200 inFIG. 13 exchanges information with a plurality ofBCS1302, and a plurality ofSICS1304 exchange information with a plurality ofBCS1305. Throughout ICS system600, different types of BCS are used to read identification information from a mailpiece and process the mailpiece through a PICS or a SICS. Accordingly, using the same example fromFIG. 13, a common sorter software is needed to allowPICS1200 andSICS1304 to exchange information withBCS1302 andBCS1305, respectively.
• FIG. 16 depicts one embodiment of a PICS/SICS system incorporating Common Sorter Software.Common Sorter Software1602 performs a number of tasks, including, for example, initiating a connection between a BCS and a PICS and/or SICS, transmitting information between the BCS and the PICS and/or SICS, and terminating the connection between the BCS and the PICS and/or SICS. In this way,PICS1200 processes mailpiece information forBCS1212,1214, and1216, usingCommon Sorter Software1602. Additionally,SICS1204 processes mailpiece information forBCS1218 and1220, usingCommon Sorter Software1602. Regardless of the type of BCS,Common Sorter Software1602 provides a common interface between the BCS and a PICS and/or SICS. Therefore,Common Sorter Software1602 is infinitely compatible (with any BCS) and infinitely expandable (to any number of BCS devices). Notably, in one implementation,Common Sorter Software1602 is software, butCommon Sorter Software1602 may also be hardware.
• FIG. 17 is a block diagram of one embodiment of a Bar Code Sorter (BCS) system using Common Sorter Software to connect to a PICS.BCS system1700 includesBCS1212 andCommon Sorter Software1602.Common Sorter Software1602 provides an interface betweenBCS system1700 and PICS1710. Of course, one skilled in the art would understand that other BCS may be similarly configured or thatBCS1212 may useCommon Sorter Software1602 to interface with a SICS rather than a PICS (i.e., PICS1700).
• FIG. 18 illustrates various embodiments of Bar Code Sorters using Common Sorter Software to connect to a PICS/SICS such as the BCS systems shown inFIG. 17. As illustrated inFIG. 18,Common Sorter Software1602 can be used with a Mail Processing Bar Code Sorter (MPBCS)1802, a Downstream Bar Code Sorter (DBCS)1804, a Carrier Sequence Bar Code Sorter (CSBCS)1806, an Output Subsystem/Bar Code Sorter (OSS/BCS)1808, or any other type of Bar Code Sorter.
• FIGS. 19A-19C illustrate one embodiment for a process used by one embodiment of Common Sorter Software during the identification and processing of a mailpiece by any of the Bar Code Sorters (BCS), such as those shown inFIG. 18. First, as shown inFIG. 19A, after anoperator1900 has loaded the mailpieces intoBCS1212,operator1900 enters a ‘Start Run’ command intoBCS1212.BCS1212 then begins the process of attempting to identify and process the mailpieces. During this process, a connection with a PICS/SICS1810 may become necessary.BCS1212 usesCommon Sorter Software1602 to establish a connection with PICS/SICS1810. As shown inFIG. 19B,operator1900 can constantly supervise the identification and processing of the mailpieces on BCS1212 (i.e., throughout the “mail sort run”). During this period,BCS1212 usesCommon Sorter Software1602 to communicate with PICS/SICS1810 throughout the mail sort run. As shown inFIG. 19C, once the mail sort run is complete,operator1900 enters an ‘End Run’ command intoBCS1212, andCommon Sorter Software1602 breaks the connection with PICS/SICS1810 until the next mail sort run. One skilled in the art would be aware of alternative processes by whichBCS1212 could connect with PICS/SICS1810 viaCommon Sorter Software1602.
• Universal ID Tag Reader
• As described above, as shown inFIGS. 12 and 13, a Bar Code Sorter (BCS) is used by ICS system600 to read information from a mailpiece and to identify and process the mailpiece according to the information. As also described above, ICS system600 uses special codes for the identification and processing of mail, namely, the POSTNET code (on the front of the mailpiece) and the identification code (on the back of the mailpiece). To read the identification code off the back of the mailpiece,RBCS500 and ICS system600 include special apparatus and processes, such as an ID Tag Reader (in RBCS500) and an Universal ID Tag Reader (in ICS system600).
• FIG. 20 is a block diagram of a Bar Code Sorter (BCS) consistent with one embodiment of the present invention, for example, as used by a RBCS, which includes, for example, an RBCS ID Tag Reader.BCS1212 includes a BarCode Sorting System2002,Common Sorter Software1602, and a RBCSID Tag Reader2000. As described above,RBCS500 makes only limited use of an identification code, because identification files are temporary and may only be used locally. For this reason, RBCSID Tag Reader2000 is generally used with a single type of BCS, namely, the OSS/BCS1808, as shown inFIG. 18.
• FIG. 21 is a block diagram of a Bar Code Sorter (BCS) consistent with one embodiment of the present invention, for example, as used by an ICS system, which includes, for example, a Universal ID Tag Reader.BCS1212 in ICS system600 includes BarCode Sorting System2002,Common Sorter Software1602, and a UniversalID Tag Reader2100. As described above, ICS system600 makes widespread use of an identification code, and therefore, UniversalID Tag Reader2100 has many applications. For example, UniversalID Tag Reader2100 can be used on any type of BCS, includingMPBCS1802,DBCS1804,CSBCS1806, and OSS/BCS1808, as shown inFIG. 18.
• FIG. 22 is a block diagram of one embodiment of a Universal ID Tag Reader (UIDTR).UIDTR2100 includes two main components: aReader Head Assembly2200 and aReader Unit2202 connected by aFiber Optic Cable2204. Notably, becauseReader Head Assembly2200 is separate fromReader Unit2202,Reader Head Assembly2200 may be placed in an assortment of different positions within ICS system600, connected byFiber Optic Cable2204. In contrast to RBCSID Tag Reader2000, therefore,UIDTR2100 has increased flexibility and usability in ICS system600.
• FIG. 23 illustrates one embodiment of a UIDTR in greater detail, as shown inFIG. 22.Reader Head Assembly2200 includes anInfrared Receiver2302 and aLens2304.Reader Unit2202 includes aReader Logic Unit2306, aLight Source2308, aLight Filter Unit2310, aSignal Converter2318, and aPort2320. In this embodiment,Light Filter Unit2310 includes afirst Light Filter2312, asecond Light Filter2314, and athird Light Filter2316. One skilled in the art would recognize that other embodiments may be used for the arrangement of light filters inReader Unit2202.Reader Head Assembly2200 is connected toReader Unit2202 viaFiber Optic Bundle2204.
• FIGS. 24A-24D illustrate the operation of one embodiment of a UIDTR while processing a mailpiece, according to one embodiment of the invention. As shown inFIG. 24A,mailpiece100 includes an identification code, i.e., an ID code. When mailpiece100 is placed before UniversalID Tag Reader2100, a light barrier signal is generated atInfrared Receiver2302.Infrared Receiver2302 passes the light barrier signal toReader Logic Unit2306. The light barrier signal indicates that there is a mailpiece ready to be processed. As shown inFIG. 24B,reader Logic Unit2306 then supplies power toLight Source2308. The light fromLight Source2308 travels overFiber Optic Bundle2204 and illuminates the ID code on the mailpiece. As shown inFIG. 24C,lens2304 then focuses the ID code ontoFiber Optic Bundle2204. In one embodiment,Fiber Optic Bundle2204 may divide the light into at least three bundles. One skilled in the art would recognize that other embodiments may be used, including less than three bundles. Each bundle is directed to a light filter inLight Filter Unit2310. The first bundle is filtered through aFirst Light Filter2312, the second bundle is filtered through aSecond Light Filter2314, and the third bundle is filtered through aThird Light Filter2316. In this embodiment, the light filters (i.e.,First Light Filter2312,Second Light Filter2314, and Third Light Filter2316) respond to different frequencies of the fluorescent spectrum. The analog signals output byLight Filter Unit2310 are then converted into digital signals bySignal Converter2318, e.g., an analog/digital converter. Finally, as shown inFIG. 24D, the digital signal fromSignal Converter2318 is passed toReader Logic Unit2306, where the digital signal is converted into an ID code corresponding to the ID code onmailpiece100.Reader Logic Unit2306 passes the ID code toPort2320, and the ID code is passed back toBCS1212.
• FIG. 25 shows optional components of an embodiment of a UIDTR such as the UIDTR inFIG. 22. As shown inFIG. 25, anoperator2500 can operate UniversalID Tag Reader2100 using one or moreLight Emitting Diodes2502 onReader Head Assembly2200 and one or moreLight Emitting Diodes2504 and PushButtons2506, located onReader Unit2202.Light Emitting Diodes2502 and/orLight Emitting Diodes2504 can display diagnostic information, such as ‘System OK’ or ‘Power OK,’ or function options, such as ‘Reset,’ tooperator2500.Operator2500 can usePush Buttons2506 to display diagnostic information, to select function options or to input other data.
• FIG. 26 shows still additional optional components of another embodiment of a UIDTR, such as the UIDTR inFIG. 22.Port2602 can support, for example, transistor transistor logic (TTL) andPort2604 can support, for example, differential logic. These optional component ports may enable, for example,UIDTR2100 to function with an expanded variety of Bar Code Sorters.
CONCLUSION
• As described above, therefore, it will be apparent to those skilled in the art that various modifications and variations can be made in the methods and apparatus of the present invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention, provided they come within the scope of the appended claims and their equivalents. In this context, equivalents mean each and every implementation for carrying out the functions recited in the claims, even if not explicitly described herein.

Claims (86)

1. A method of processing delivery item information by a primary identification code server, comprising the steps of:

receiving an identification file corresponding to a delivery item, wherein the identification file contains an identification code and a delivery code; and

resolving delivery item information for an item processing device, using the identification file.

2. The method ofclaim 1, wherein the item processing device is a bar code sorter.

3. The method ofclaim 1, wherein the identification code is an ID tag.

4. The method ofclaim 1, wherein the delivery code is a POSTNET code.

5. The method ofclaim 1, further comprising the step of:

storing the identification file in a lookup table.

6. The method ofclaim 1, further comprising the step of:

maintaining a service area table for a secondary identification code server.

7. The method ofclaim 1, wherein the resolving step further comprises the substeps of:

receiving the identification code from an item processing device, where the item processing device obtains the identification code from the delivery item;

processing the identification code to determine the delivery item information, using the identification file corresponding to the identification code; and

transmitting the delivery item information to the item processing device.

8. The method ofclaim 1, wherein the identification file further includes an image capture time.

9. The method ofclaim 8, wherein the identification file further includes a plurality of status bits that indicate aspects of the identification file.

10. A system for processing delivery item information by a primary identification code server, comprising:

an identification file receiving component configured to receive an identification file corresponding to a delivery item, wherein the identification file contains an identification code and a delivery code; and

a resolving component configured to resolve delivery item information for an item processing device, using the identification file.

11. The system ofclaim 10, wherein the item processing device is a bar code sorter.

12. The system ofclaim 10, wherein the identification code is an ID tag.

13. The system ofclaim 10, wherein the delivery code is a POSTNET code.

14. The system ofclaim 10, further comprising:

a storing component configured to store the identification file in a lookup table.

15. The system ofclaim 10, further comprising:

a maintaining component configured to maintain a service area table for a secondary identification code server.

16. The system ofclaim 10, wherein the resolving component includes:

an identification code receiving component configured to receive the identification code from the item processing device, where the item processing device obtains the identification code from the delivery item;

a processing component configured to process the identification code to determine the delivery item information, using the identification file corresponding to the identification code; and

a transmitting component configured to transmit the delivery item information to the item processing device.

17. The system ofclaim 10, wherein the identification file further includes an image capture time.

18. The system ofclaim 17, wherein the identification file further includes a plurality of status bits that indicate aspects of the identification file.

19. A system for processing delivery item information by a primary identification code server, comprising:

means for receiving an identification file corresponding to a delivery item, wherein the identification file contains an identification code and a delivery code; and

means for resolving delivery item information for an item processing device, using the identification file.

20. A computer usable medium having computer readable code embodied therein for processing delivery item information by a primary identification code server, the computer readable code comprising:

an identification file receiving module configured to receive an identification file corresponding to a delivery item, wherein the identification file contains an identification code and a delivery code; and

a resolving module configured to resolve delivery item information for an item processing device, using the identification file.

21. A method of processing delivery item information by a primary identification code server, comprising the steps of:

receiving an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code;

storing the identification file in a lookup table; and

resolving delivery item information for the delivery item, wherein the resolving step further comprises the substeps of:

receiving an identification code from an item processing device, where the item processing device obtains the identification code from the delivery item;

processing the identification code to determine the identification information, using the identification file corresponding to the identification code; and

transmitting the delivery item information to the item processing device.

22. The method ofclaim 21, wherein the item processing device is a bar code sorter.

23. The method ofclaim 21, wherein the storing step further comprises:

revising the identification file in the lookup table.

24. The method ofclaim 21, wherein the identification code is an ID tag.

25. The method ofclaim 21, wherein the file identification code is an ID tag.

26. The method ofclaim 21, wherein the file delivery code is a POSTNET code.

27. The method ofclaim 21, further comprising the steps of:

receiving a delete file message from the item processing device indicating an identification file to be deleted; and

deleting the identification file to be deleted from the lookup table in response to the delete file message.

28. The method ofclaim 21, wherein the resolving step further comprises the substeps of:

connecting to the item processing device via a telecommunications link;

receiving test data from the item processing device; and

confirming the test data.

29. The method ofclaim 28, wherein the test data comprises test delivery item identification codes.

30. The method ofclaim 21, wherein the delivery item information transmitting step further comprises the substep of:

transmitting the identification file corresponding to the identification code, if the identification code is found in the lookup table.

31. The method ofclaim 21, wherein the delivery item information transmitting step further comprises the substep of:

transmitting the file delivery code corresponding to the identification code, if the identification code is found in the lookup table.

32. The method ofclaim 21, wherein the delivery item information transmitting step further comprises the substep of:

transmitting an error message to the item processing device, if the identification code is not found in the lookup table.

33. The method ofclaim 21, wherein the identification file further includes an image capture time.

34. The method ofclaim 33, wherein the identification file further includes a plurality of status bits that indicate aspects of the identification file.

35. A system for processing delivery item information by a primary identification code server, comprising:

an identification file receiving component configured to receive an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code.

a storing component configured to store the identification file in a lookup table; and

a resolving component configured to resolve delivery item information for the delivery item, wherein the resolving component further comprises:

an identification code receiving component configured to receive an identification code from an item processing device, where the item processing device obtains the identification code from the delivery item;

a processing component configured to process the identification code to determine the delivery item information, using the identification file corresponding to the identification code; and

an identification information transmitting component configured to transmit the delivery item information to the item processing device.

36. The system ofclaim 35, wherein the item processing device is a bar code sorter.

37. The system ofclaim 35, wherein the storing component further comprises:

a revising component configured to revise the identification file in the lookup table.

38. The system ofclaim 35, wherein the identification code is an ID tag.

39. The system ofclaim 35, wherein the file identification code is an ID tag.

40. The system ofclaim 35, wherein the file delivery code is a POSTNET code.

41. The system ofclaim 35, further comprising:

a delete file message receiving component configured to receive a delete file message from the item processing device indicating an identification file to be deleted; and

a deleting component configured to delete the identification file to be deleted from the lookup table in response to the delete file message.

42. The system ofclaim 35, wherein the resolving component further comprises:

a connecting component configured to connect to the item processing device via a telecommunications link;

a test data receiving component configured to receive test data from the item processing device; and

a confirming component configured to confirm the test data.

43. The system ofclaim 42, wherein the test data comprises test delivery item identification codes.

44. The system ofclaim 35, wherein the identification information transmitting component further comprises:

an identification file transmitting component configured to transmit the identification file corresponding to the identification code, if the identification code is found in the lookup table.

45. The system ofclaim 35, wherein the identification information transmitting component further comprises:

a file delivery code transmitting component configured to transmit the file delivery code corresponding to the identification code, if the identification code is found in the lookup table.

46. The system ofclaim 35, wherein the identification information transmitting component further comprises:

an error message transmitting component configured to transmit an error message to the item processing device, if the identification code is not found in the lookup table.

47. The system ofclaim 35, wherein the identification file further includes an image capture time.

48. The system ofclaim 35, wherein the identification file further includes a plurality of status bits that indicate aspects of the identification file.

49. A system for processing delivery item information by a primary identification code server, comprising:

means for receiving an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code.

means for storing the identification file in a lookup table; and

means for resolving identification information for the delivery item, wherein the resolving means further comprises:

means for receiving an identification code from an item processing device, where the item processing device obtains the identification code from the delivery item;

means for processing the identification code to determine the identification information, using the identification file corresponding to the identification code; and

means for transmitting the identification information to the item processing device.

50. A computer usable medium having computer readable code embodied therein for processing delivery item information by a primary identification code server, the computer readable code comprising:

an identification file receiving module configured to receive an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code.

a storing module configured to store the identification file in a lookup table; and

a resolving module configured to resolve identification information for the delivery item, wherein the resolving module further comprises:

an identification code receiving module configured to receive an identification code from an item processing device, where the item processing device obtains the identification code from the delivery item;

a processing module configured to process the identification code to determine the identification information, using the identification file corresponding to the identification code; and

an identification information transmitting module configured to transmit the identification information to the item processing device.

51. A method of processing delivery item information by a primary identification code server, comprising the steps of:

receiving an identification file corresponding to a delivery item from an Electronic Shipping Office wherein the identification file contains an identification code and a delivery code; and

resolving delivery item information for an item processing device, using the identification file.

52. The method ofclaim 51, wherein the item processing device is a bar code sorter.

53. The method ofclaim 51, wherein the identification code is an ID tag.

54. The method ofclaim 51, wherein the delivery code is a POSTNET code.

55. The method ofclaim 51, further comprising the step of:

sending a local service area table file to the Electronic Shipping Office.

56. The method ofclaim 55, wherein the identification file relates to the local service area table file.

57. A system for processing delivery item information by a primary identification code server, comprising:

a receiving component configured to receive an identification file corresponding to a delivery item from an Electronic Shipping Office wherein the identification file contains an identification code and a delivery code; and

a resolving component configured to resolve delivery item information for an item processing device, using the identification file.

58. The system ofclaim 57, wherein the item processing device is a bar code sorter.

59. The system ofclaim 57, wherein the identification code is an ID tag.

60. The system ofclaim 57, wherein the delivery code is a POSTNET code.

61. The system ofclaim 57, further comprising:

a sending component configured to send a local service area table file to the Electronic Shipping Office.

62. The system ofclaim 61, wherein the identification file relates to the local service area table file.

63. A system for processing delivery item information by a primary identification code server, comprising: means for receiving an identification file corresponding to a delivery item from an Electronic Shipping Office wherein the identification file contains an identification code and a delivery code; and

means for resolving delivery item information for an item processing device, using the identification file.

64. A computer usable medium having computer readable code embodied therein for processing delivery item information by a primary identification code server, the computer readable code comprising:

a receiving module configured to receive an identification file corresponding to a delivery item from an Electronic Shipping Office wherein the identification file contains an identification code and a delivery code; and

a resolving module configured to resolve delivery item information for an item processing device, using the identification file.

65. A method of processing delivery item information by a primary identification code server, comprising the steps of:

receiving an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code;

determining whether the identification file corresponds to a local service area table file;

updating an Electronic Shipping Office, if the identification file does not correspond to the local service area table file, wherein the updating step further comprises the substeps of:

transmitting the local service area table file to the Electronic Shipping Office; and

sending the identification file to the Electronic Shipping Office; and

storing the identification file in a lookup table, if the identification file corresponds to the local service area table file.

66. The method ofclaim 65, wherein the file identification code is an ID tag.

67. The method ofclaim 65, wherein the file delivery code is POSTNET code.

68. A system for processing delivery item information by a primary identification code server, comprising:

a receiving component configured to receive an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code;

a determining component configured to determine whether the identification file corresponds to a local service area table file;

an updating component configured to update an Electronic Shipping Office, if the identification file does not correspond to the local service area table file, wherein the updating component further comprises:

a transmitting component configured to transmit the local service area table file to the Electronic Shipping Office; and

a sending component configured to send the identification file to the Electronic Shipping Office; and

a storing component configured to store the identification file in a lookup table, if the identification file corresponds to the local service area table file.

69. The system ofclaim 68, wherein the file identification code is an ID tag.

70. The system ofclaim 68, wherein the file delivery code is POSTNET code.

71. A system for processing delivery item information by a primary identification code server, comprising:

means for receiving an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code;

means for determining whether the identification file corresponds to a local service area table file;

means for updating an Electronic Shipping Office, if the identification file does not correspond to the local service area table file, wherein the updating means further comprises:

means for transmitting the local service area table file to the Electronic Shipping Office; and

means for sending the identification file to the Electronic Shipping Office; and

means for storing the identification file in a lookup table, if the identification file corresponds to the local service area table file.

72. A computer usable medium having computer readable code embodied therein for processing delivery item information by a primary identification code server, the computer readable code comprising:

a receiving module configured to receive an identification file corresponding to a delivery item from an image control unit, wherein the identification file contains a file identification code and a file delivery code;

a determining module configured to determine whether the identification file corresponds to a local service area table file;

an updating module configured to update an Electronic Shipping Office, if the identification file does not correspond to the local service area table file, wherein the updating module further comprises:

a transmitting module configured to transmit the local service area table file to the Electronic Shipping Office; and

a sending module configured to send the identification file to the Electronic Shipping Office; and

a storing module configured to store the identification file in a lookup table, if the identification file corresponds to the local service area table file.

73. A method of processing delivery item information by an Electronic Shipping Office, comprising the steps of:

receiving an identification file from a transmitting primary identification code server, wherein the identification file contains an identification code and a delivery code;

storing the identification file in a storage buffer; and

updating a receiving primary identification code server, wherein the updating step further comprises the substeps of:

receiving a local service area table file corresponding to the receiving primary identification code server;

matching the identification file to the local service area table file;

storing the identification file in a primary identification code server table; and

sending the primary identification code server table to the receiving primary identification code server.

74. The method ofclaim 73, further comprising the steps of:

generating a national service area table file; and

sending the national service area table file to the receiving primary identification code server.

75. The method ofclaim 73, wherein the identification code is an ID tag.

76. The method ofclaim 73, wherein the delivery code is a POSTNET code.

77. The method ofclaim 73, wherein the identification file further comprises an image capture time.

78. The method ofclaim 73, wherein the identification file further comprises a plurality of status bits that indicate aspects of the identification file.

79. A system for processing delivery item information by an Electronic Shipping Office, comprising:

an identification file receiving component configured to receive an identification file from a transmitting primary identification code server, wherein the identification file contains an identification code and a delivery code;

a storing component configured to store the identification file in a storage buffer; and

an updating component configured to update a receiving primary identification code server, wherein the updating component further comprises:

a local service area table file receiving component configured to receive a local service area table file corresponding to the receiving primary identification code server;

a matching component configured to match the identification file to the local service area table file;

a storing component configured to store the identification file in a primary identification code server table; and

a primary identification code server table sending component configured to send the primary identification code server table to the receiving primary identification code server.

80. The system ofclaim 79, further comprising:

a generating component configured to generate a national service area table file; and

a national service area table file sending component configured to send the national service area table file to the receiving primary identification code server.

81. The system ofclaim 79, wherein the identification code is an ID tag.

82. The system ofclaim 79, wherein the delivery code is a POSTNET code.

83. The system ofclaim 79, wherein the identification file further comprises an image capture time.

84. The system ofclaim 79, wherein the identification file further comprises a plurality of status bits that indicate aspects of the identification file.

85. A system for processing delivery item information by an Electronic Shipping Office, comprising:

means for receiving an identification file from a transmitting primary identification code server, wherein the identification file contains an identification code and a delivery code;

means for storing the identification file in a storage buffer; and

means for updating a receiving primary identification code server, wherein the updating means further comprises:

means for receiving a local service area table file corresponding to the receiving primary identification code server;

means for matching the identification file to the local service area table file;

means for storing the identification file in a primary identification code server table; and

means for sending the primary identification code server table to the receiving primary identification code server.

86. A computer usable medium having computer readable code embodied therein for processing delivery item information by an Electronic Shipping Office, the computer readable code comprising:

an identification file receiving module configured to receive an identification file from a transmitting primary identification code server, wherein the identification file contains an identification code and a delivery code;

a storing module configured to store the identification file in a storage buffer; and

an updating module configured to update a receiving primary identification code server, wherein the updating module further comprises:

a local service area table file receiving module configured to receive a local service area table file corresponding to the receiving primary identification code server;

a matching module configured to match the identification file to the local service area table file;

a storing module configured to store the identification file in a primary identification code server table; and

a primary identification code server table sending module configured to send the primary identification code server table to the receiving primary identification code server.

Images