Patent Grant
10417728
The present application is related to co-pending and commonly assigned U.S. patent application Ser. No. 12/316,542 entitled “Computer-Based Value-Bearing Item Customization Security,” filed Dec. 11, 2008, Ser. No. 14/055,473 entitled “Systems and Methods Facilitating Shipping Services Rate Resale” filed Oct. 16, 2013, the disclosures of which are hereby incorporated herein by reference.
The invention relates generally to generating indicia, such as value bearing indicia, and more particularly to using a single security device secure environment session to generate multiple indicia.
Various forms of value bearing indicia have been developed and used throughout the world. Such value bearing indicia often takes the form of an electronic and/or printed data packet adapted for providing a representation of value sufficient to be acceptable as proof of payment for goods, services, etc. For example, postage indicia have been used for a number of years as proof of payment for postal services.
Because such indicia represents a form of value, the indicia itself and the process for its generation is typically provided some form of security. For example, the indicia may implement digital signatures, secure hash techniques, cryptographic techniques, etc. The process for generating the indicia may be performed within a secure environment, such as within the confines of a secure processor-based system (e.g., cryptocard, such as the 4764 cryptographic coprocessor available from International Business Machines Corporation). For example, postage indicia, such as the information based indicia (IBI) generated by processor-based open systems (e.g., stand-alone or client/server general purpose systems operable under control of an instruction set providing postage indicia metering functionality) in accordance with the United States Postal Service (USPS), may be generated within a postal security device (PSD) and may include digital signatures generated by a cryptographic processor of the PSD.
In order to perform as an indicia generation device, such secure environments must typically be loaded with the requisite indicia generation host information, perform the steps for generation of the indicia, and subsequently have the indicia generation host information unloaded from the secure environment to free the secure environment for other operations (e.g., generation of indicia for different users, for different accounts, for different uses, etc.). For example, in the postage indicia context, a cryptocard may be provided with indicia generation host information, such as may comprise ascending and descending postage registers, cryptographic postal keys, logging records, etc., (referred to herein as “virtual PSD information”) to configure the otherwise “generic” cryptocard as a particular PSD (e.g., a specific user's PSD, a PSD for a specific postage account, etc.) for use in generating an indicia. Once the indicia has been generated, the virtual PSD information with its updated data (e.g., register values) reflecting generation of the indicia may be offloaded from the cryptocard and stored in a database for subsequent use. Because the virtual PSD information contains the information establishing the cryptocard as the PSD (i.e., the PSD “personality”), this PSD information is generally encrypted when passed outside of the secure environment of the cryptocard.
As can be appreciated from the foregoing, considerable data transfer and processing may be associated with the generation of indicia. In particular, not only must the virtual PSD information be retrieved and loaded into the secure environment of the cryptocard in the foregoing example, but the virtual PSD information must be decrypted once loaded prior to use. Correspondingly, the virtual PSD information must again be encrypted once the indicia is generated prior to offloading of the virtual PSD information from the cryptocard. This processing and data transfer is in addition to that directly associated with the generation of the indicia itself, including the cryptographic functions typically employed to provide a digital signature. In order to provide the requisite logging and register value accountability, the process must be repeated for each indicia generated according to the present implementations.
Some use scenarios may provide a situation in which a user is in need of or otherwise desires to generate a plurality of indicia in a same session. For example, a user may desire to generate a plurality of postage indicia, such as to provide a supply of postage indicia for some period of time (e.g., a week or month). Such scenarios have not traditionally been the focus of service by the processor-based open systems used in generating IBI. However, as can be appreciated from the foregoing, where such processor-based systems utilizing virtual PSD information as described above can require appreciable time (in computer processing terms) to load/unload the data, decrypt/encrypt the data, update the registers and logs, generate the postage indicia and repeat for each indicia generated. There is currently no solution implemented for reducing the time associated with the repeated loading/unloading data, decrypting/encrypting, updating registers and logs, and generating postage indicia required for generation of each indicia of the plurality of indicia.
Another example of a use scenario which may require appreciable time for generating a plurality of indicia is that of a multiuser postage meter, such as in the case an enterprise postage meter or a centralized postage meter serving a number of clients (e.g., remote retail kiosks, post office point of sale terminals, etc.). In such a scenario, multiple users (e.g., using different client systems) may request postage indicia generation simultaneously or in close temporal proximity. Currently available solutions for providing service to the different users has been to implement a PSD pool (i.e., a plurality of PSDs operable to each independently load virtual PSD information for separately metering and generating postage indicia) at the centralized postage meter. Although such a solution may be effective at reducing delay associated with the generation of multiple postage indicia, the solution is relatively costly and requires maintaining prepaid account balances (i.e., postage meter value balances) with respect to each such virtual PSD.
The present invention is directed to systems and methods which are adapted to generate multiple indicia in a single secure environment session. For example, embodiments of the present invention provide for generation of a plurality of postage indicia in a single PSD transaction, whereby the PSD loads and unloads corresponding virtual PSD information a single time for generating the plurality of postage indicia (i.e., in a single secure environment session).
The indicia generated in a same secure environment session according to embodiments of the invention may comprise a plurality of indicia requested by a same, single user. For example, the multiple indicia may comprise a number of postage indicia estimated to supply the user for some period of time (e.g., a week or a month). Additionally or alternatively, the indicia generated in the same secure environment session may comprise a plurality of indicia requested by multiple different users (e.g., different users of an enterprise metering system, users of different client systems served by a metering system server, etc.).
The foregoing has outlined rather broadly the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention. It should be appreciated by those skilled in the art that the conception and specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. It should also be realized by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the invention as set forth in the appended claims. The novel features which are believed to be characteristic of the invention, both as to its organization and method of operation, together with further objects and advantages will be better understood from the following description when considered in connection with the accompanying figures. It is to be expressly understood, however, that each of the figures is provided for the purpose of illustration and description only and is not intended as a definition of the limits of the present invention.
For a more complete understanding of the present invention, reference is now made to the following descriptions taken in conjunction with the accompanying drawing, in which:
In operation according to embodiments herein, the indicia requested and generated comprises value bearing indicia (i.e., indicia representative of an amount of pecuniary value, such as may be utilized for proof of payment, payment for goods or services, etc.). In particular, the embodiments of systems 100A and 100B illustrated in
Embodiments herein operate to provide a form of security (e.g., digital signatures, secure hash, encryption, etc.) with respect to the value bearing indicia generated in order to facilitate protection of the value thereof. The process for generating the requested indicia is performed within a secure environment (e.g., as may be provided by one or more crypto modules) according to the illustrated embodiments. For example, cryptocard 125, such as may comprise the 4764 (single threaded) or 4765 (multi-threaded) cryptographic coprocessors available from International Business Machines Corporation, provides a crypto module facilitating a secure environment in which postage indicia may be generated thus providing a form of postage security device (PSD). Of course, other forms of crypto modules and other devices for providing the requisite secure environment may be utilized to provide a PSD or other secure environment in accordance with embodiments of the invention, such as smartcards, trusted platform modules (TPMs), touch memory utility buttons (TMUs), etc. Although a single cryptocard is shown in the illustrated embodiment, it should be appreciated that a plurality of such devices may be provided with respect to postal services system 110A, such as to facilitate serving a number of requests for indicia (e.g., a plurality of bulk indicia requests from the same of different users). Irrespective of the particular secure environment implementation, as will be better understood from the discussion which follows, in operation according to embodiments herein a plurality of postage indicia are generated in a single secure device session.
In providing a system adapted to provide generation of multiple indicia in a single secure environment session, system 100A of
It should be appreciated that the components of postal service system 110A may be implemented as a single system, such as a single server, or as a distributed system, such as a server farm, a number of host systems disposed remotely with respect to each other, etc. For example, postage server 120 and bridge server 130 of postal services system 110A may be hosted by a same server. Alternatively, postage server 120 and bridge server 130 may be hosted by different servers according to embodiments herein.
Irrespective of a single or distributed implementation, postal services system 110A of embodiments may comprise a processor-based system operable under control of an instruction set or instruction sets defining operation as described herein. Postal services system 110A of embodiments comprises one or more processors (e.g., a CORE or PENTIUM processor available from Intel, Inc.) and requisite processor readable (e.g., computer readable) memory (e.g., random access memory (RAM), read only memory (ROM), flash memory, disk memory, solid state drive (SSD) memory, optical memory, and/or the like) and input/output components (e.g., display, network interface card (NIC), keyboard, digital pointer, printer, and/or the like) coupled to a processor of the one or more processors via a data bus.
Postage server 120 may comprise a processor or processors and portion of the processor readable memory of postal services system 110A and corresponding instruction set operable to define postage server operation as described herein, including generation of multiple indicia in a single secure environment session. Postage server 120 of embodiments may comprise a server (e.g., web server) or servers or virtual server operable within a suitable host environment (e.g., within a postal services system server). Postage server 120 may, for example, comprise a system substantially as described with respect to the shipping service infrastructure in the above referenced patent application entitled “Systems and Methods Facilitating Shipping Services Rate Resale”, adapted to provide generation of multiple postage indicia herein.
Postage server 120 of the illustrated embodiment comprises cryptocard 125 configurable as a PSD according to embodiments herein and operable to provide a secure environment in which postage indicia (and/or other desired indicia) may be securely generated. Postal database 121 of the illustrated embodiment comprises a number of data files providing virtual PSD information (shown here as virtual PST information 122-124). Virtual PSD information 122-124 of embodiments comprises information suitable for temporarily configuring cryptocard 125 as a PSD for a particular postage meter license or licenses. For example, each of virtual PSD information 122-124 may comprise ascending and descending registers, postage indicia strike registers, log files, postal account identification, meter license number, etc. utilized in postage indicia metering operations for different users or user accounts. The virtual PSD information is preferably encrypted by cryptocard 125 for storage in postal database 121 to thereby protect this data when outside the confines of a secure environment.
It should be appreciated that, although postal database 121 is shown disposed within postage server 120, the postal database may be external or remote thereto. For example, some portion of virtual PSD information may be stored in one or more database disposed locally with respect to postage server 120 while another portion of virtual PSD information may be stored in one or more database disposed remotely with respect to postage server 120.
Bridge server 130 may comprise a processor or processors and portion of the processor readable memory of postal services system 110A and corresponding instruction set operable to define bridge server operation as described herein, including user authentication, user account association/identification, etc. Bridge server 130 of embodiments may comprise a server (e.g., web server) or servers or virtual server operable within a suitable host environment (e.g., within a postal services system server). Bridge server 130 as may be utilized according to embodiments of the invention may, for example, comprise a system substantially as described in U.S. Pat. No. 8,046,823 entitled “Secure Application Bridge Server,” the disclosure of which is incorporated herein by reference.
Client device 140A of embodiments herein may comprise any number of system configurations used by a user for requesting, obtaining, and/or printing desired indicia, such as postage indicia. For example, client device 140A may comprise a general purpose processor-based system (e.g., personal computer (PC) having a processor, memory, suitable input/output (I/O) functionality, and operating system (OS)) operating under control of postage client 141A providing a client application (e.g., PC client, web client, mobile client, tablet client, etc.) to interface with postal services system 110A and provide operation as described herein. Additionally or alternatively, client device 140A may comprise a processor-based device such as a smart phone, a tablet device, a personal digital assistant (PDA), an Internet appliance (e.g., a processor-based postage printer Internet appliance), etc., having the requisite instruction set (e.g., postage client 141A) and processing and I/O resources. The interface architecture implemented according to embodiments of the invention not only accommodate standalone client applications, but may support other forms of client access, such as web based applets, third party software access integration, etc. Printer 142A, such as may comprise any printer configuration (e.g., laser printer, ink jet printer, thermal printer, etc.) suitable for printing or otherwise rendering desired indicia, is coupled to client device 140A of the illustrated embodiment. It should be appreciated that although one client device is shown in
Network 150 provides communication links with respect to client devices and by and between components of the postal services system for facilitating requesting, generating, and/or printing of desired indicia. Accordingly, the links of network 150 are operable to provide suitable communication links for facilitating cooperative interaction and data transfer as described herein. Network 150 of embodiments may thus comprise one or more of a local area network (LAN), metropolitan area network (MAN), wide area network (WAN), wireless LAN (WLAN), the Internet, intranet, extranet, cable transmission system, cellular communication network, and/or the like.
Flow 200A of
A bulk postage indicia request of embodiments comprises information sufficient to generate multiple desired postage indicia for the requesting user. Accordingly, a bulk postage indicia request may include information such as postage amounts, multiple special services, mail classes, hidden postage information, insurance information, tracking numbers, etc. Moreover, bulk postage indicia requests preferably include user identification information (e.g., user account information, user credentials (e.g., user name, password, digital certificate, etc.), and/or the like), such as may be used to validate the user as an authorized user of the postal services system, to identify an account from which value for the postage indicia is to be debited and/or to which value is to be charged, to identify virtual PSD information associated with the requesting user, etc.
At block 202 of the illustrated embodiment, postal services system 110A is accessed and the bulk postage indicia request is made. For example, postage client 141A may communicate with postal services system 110A via network 150 to initiate a session for generating multiple postage indicia, such as by communicating the bulk postage indicia request and/or other information (e.g., user credentials) from client device 140A to bridge server 130. Bridge server 130 of embodiments may operate to authenticate the user, such as using user identification information of the bulk postage indicia request and/or user credentials provided therein or therewith. Such authentication may operate to identify the user as being authorized to receive the services of postal services system 110A. Additionally or alternatively, such authentication may associate the user with one or more accounts (e.g., as may be represented by corresponding ones of the PSDs of virtual PSD information 122-124) accessible to postal services system 120.
Having made the bulk postage indicia request, the bulk postage indicia request is received and processed for PSD operation at block 203 of the illustrated embodiment. For example, assuming the user authentication is successful, bridge server 130 may pass the bulk postage indicia request, or some portion thereof, to postage server 120 for generating the multiple postage indicia. In operation according to embodiments, logic of postage server 120 operates to process the bulk postage indicia request for facilitating operation by cryptocard 125 in generating multiple postage indicia in a same secure environment session. For example, postage server 120 may operate to associate the bulk postage request with particular virtual PSD information of virtual PSD information 122-124 storing postage value available to the user making the request. Additionally or alternatively, postage server 120 may provide processing of the bulk postage indicia request to provide the request, or some portion thereof, in a form usable by the PSD, such as to format the data for use by the PSD (e.g., serialize the data in a form understandable by logic of the PSD), to utilize a protocol compatible with the PSD, etc.
In operation according to embodiments, processing with respect to the bulk postage indicia request provided by logic of postal services system 110A may comprise a number of operations for facilitating postage indicia generation by cryptocard using virtual PSD information of postal database 121. For example, logic of postal services system 110A may calculate the total postage amount from the bulk postage indicia request data and determine if adequate total postage amount is available in the user PSD record for the bulk postage indicia request before acquiring a secure module (e.g., cryptocard 125) for generation of the postage indicia.
At block 204 of the illustrated embodiment a PSD bulk request (e.g., the bulk postage indicia request as processed by postal services system 110A) is provided to cryptocard 125. For example, after processing the bulk postage indicia request for facilitating operation by cryptocard 125 in generating multiple postage indicia in a same secure environment session, logic of postal services system 110A may provide the PSD bulk request to cryptocard 125 to initiate generation of the multiple postage indicia. In operation according to embodiments, providing the PSD bulk request to the cryptocard by logic of postal services system 110A may comprise a number of operations. For example, logic of postal services system 110A may operate to select a particular crypto module (e.g., cryptocard 125) for generation of the multiple postage indicia from a plurality of crypto modules (e.g., to select an available crypto module, to select a crypto module having specific capabilities, to provide load balancing among a pool of crypto modules, etc.). The selected crypto module may thereafter be locked for operation of the secure environment session to generate the multiple postage indicia.
It should be appreciated that the providing of the PSD bulk request may be done in association with providing other data to the cryptocard. For example, logic of postal services system 110A may operate to select a particular virtual PSD record for use in generating the multiple postage indicia. The virtual PSD information provided to cryptocard 125 may, for example, be selected based upon user identification, user credentials, a PSD for providing services authorized with respect to the requesting user, etc. and that the virtual PSD has sufficient account value associated therewith to support generation of the requested postage indicia. The selected virtual PSD information of virtual PSD information 122-124 may be locked (e.g., to prevent its simultaneous use with respect to another crypto module, whereby value represented thereby may be consumed more than once) and the selected virtual PSD information provided to cryptocard 125 in order to configure cryptocard 125 for operation as a particular PSD.
Further, in association with the providing of the PSD bulk request to the cryptocard, logic of postal services system 110A may acquire and lock a check point record for that crypto module (e.g., from postal database 121). The check point record may, for example, comprise information regarding the state of the crypto module after the last transaction performed by the crypto module. A postal database of embodiments may store check point records for each available crypto module. Such check point information may be utilized in providing an atomic transaction with respect to the generation of the multiple postage indicia. That is, if operation to generate the multiple postage indicia is interrupted or otherwise fails to complete the complete process of generating all the multiple postage indicia, and possibly logging information associated therewith, a check point record indicating a state of the PSD prior to initiating the postage indicia generation operation may be used to roll the PSD data back to its state prior to initiating the failed multiple postage indicia generation transaction. Such check point record information may be provided to cryptocard 125, such as with or in association with the virtual PSD information and/or PSD bulk request.
Having received the PSD bulk request according to flow 200A of the illustrated embodiment, cryptocard 125 operable as a PSD generates the multiple postage indicia of the PSD bulk request in a single secure environment session at block 205 of the illustrated embodiment. That is, cryptocard 125 of embodiments is operable to load and decrypt the appropriate virtual PSD information, configure the memory (e.g., ascending register, descending register, strike count register, etc.) of the cryptocard as the corresponding PSD, generate each postage indicia of the multiple postage indicia, update appropriate PSD data (e.g., ascending register value, descending register value, strike count register value, etc.), and encrypt the virtual PSD information for offloading from the cryptocard. In operation according to embodiments, logic of cryptocard 125 may determine the number of postage indicia it is being requested to generate (e.g., for configuring logic for an appropriate number of iterations to generate the postage indicia), determine the total value for the postage indicia to be generated (e.g., for confirming that sufficient value is available for completing the bulk postage indicia transaction), determine the size of the memory for the indicia generation based on the total number of the postage requests (e.g., for confirming that sufficient memory space is available for generation and temporary storage of the postage indicia and for allocating that memory space), and generate multiple postage indicia data (e.g., data packets from which postage indicia may be printed).
Logic of the PSD may, for example, operate to authenticate the request (e.g., as a request from a valid server or other requesting system and/or as a request from a valid user or users). Additionally or alternatively, logic of the PSD may operate to verify that sufficient value is present in the PSD for generation of the requested postage indicia. For example, the PSD logic may implement a loop in which the value for each of the multiple requested postage indicia is identified and summed to determine a total value for the requested indicia. This total value may be compared to the value available from the PSD (e.g., the PSD descending register) to determine if sufficient value is present to allow generation of the multiple requested indicia. It should be appreciated that this verification of available value by the PSD may be performed in addition to a determination by the postage server or other system external to the PSD regarding sufficient value, such as to provide a secure and/or accurate verification of sufficient value prior to generation of the requested indicia. Initiation of generation of the multiple postage indicia may be prevented if a sufficient amount of value for the total amount is not available. If, however, sufficient value is available, the logic of the PSD may again implement a loop to generate each of the requested postage indicia, storing the generated postage indicia data for providing to the postage server in a single response. In operation according to embodiments, the ascending and descending registers of the PSD are adjusted as each of the multiple postage indicia are generated. Additionally, a logging register of embodiments of the PSD is used to sum the value of each of the generated postage indicia to provide a total amount used with respect to logging data (e.g., used in generation of an audit indicia for logging purposes).
It should be appreciated that cryptocard 125 of embodiments may operate to generate more than the requested multiple postage indicia when performing operation for generating multiple postage indicia in a single secure environment session. For example, logic of the cryptocard may generate logging and/or other data unique to the secure environment multiple postage indicia session. In operation according to embodiments, such logging data may include the number of indicia generated in the session, the total value of the indicia generated, the time/date of the generation session (e.g., the starting time, the ending time, or both), the starting and/or ending register values (e.g., ascending register, descending register, etc.), transaction number or other transaction identification information, meter/license number or other identification information, and the like.
At block 206 of the illustrated embodiment, cryptocard 125 may return logging or audit information for the multiple postage indicia for processing, storage, and/or reporting by postal services system 110A. For example, after the cryptocard generates postage indicia data for a multiple postage indicia request, intermediary code for the cryptocard may operate to write an audit log entry to one or more storage device (e.g., the audit log information may be written to a postal server disk or other storage device other than postal database 121 to avoid tampering or to otherwise facilitate reliable auditing of the indicia generation transactions). Such audit information may comprise information regarding the number, value, type, etc. of the generated postage indicia, identification of the PSD (e.g., virtual PSD information) used to generate the postage indicia, and/or the like. Additionally or alternatively, such audit information may comprise one or more audit indicia, generated by cryptocard 125 in association with the multiple postage indicia, providing aggregated audit information (e.g., a transaction number or other identification information, meter/license number, the total value for all the multiple postage indicia, starting and/or ending register values, number of postage indicia generated, identification information for each of the multiple postage indicia, time stamp for the multiple indicia generation session, etc.). An audit indicium of embodiments comprises a standard indicia format (e.g., the same format as the generated postage indicia) including some or all of the above information (e.g., a 16 bit number in the range from 1 to 64k providing transaction identification, an actual number of indicium created, and the ending ascending and descending register values). Any or all of the foregoing information may be further processed, stored, and/or reported by logic of postal services system 110A. In operation according to embodiments, after such audit log information is written successfully, logic of cryptocard 125 may provide the generated postage indicia data for the multiple postage indicia, the updated virtual PSD information, and updated check point record to logic of postal services system 110A outside of the secure environment. It should be appreciated that the indicium generated in response to the request for multiple postage indicia may be associated with the audit information (e.g., the audit indicium through matching of identification information, such as the aforementioned transaction number, meter/license number, and/or time stamp information), such as for audit purposes, validation of the indicia, etc.
Accordingly, at block 207 of the illustrated embodiment of flow 200A the generated multiple postage indicia are passed from the secure environment of cryptocard 125. For example, the generated multiple postage indicia may be returned to logic of postage server 120, such as for further processing and providing to the requesting client device. It should be appreciated that information in addition to that of the multiple postage indicia may be returned from cryptocard 125 in association with the generated postage indicia. For example, cryptocard 125 may return the virtual PSD information, updated to reflect generation of the multiple postage indicia, for storage in postal database 121.
At block 208, postal services system 110A returns the generated multiple postage indicia to the requesting client device. It should be appreciated that logic of postal services system 110A may provide further processing with respect to the generated multiple postage indicia prior to its returning the generated multiple postage indicia to client device 140A. For example, postal services system 110A may provide processing of the multiple postage indicia returned by cryptocard 125 to provide the postage indicia data, or some portion thereof, in a form usable by the requesting client device(s) or other systems of system 100A, such as to format the data for use by client device 140A and/or for processing and communication by bridge server 130. Embodiments of postal services system 110A may provide processing to associate the multiple postage indicia with the particular bulk postage indicia request made by postage client 141A in order to facilitate properly identifying the postage indicia with the operations at client device 140A for which the postage indicia was generated. Additionally or alternatively, such processing may comprise packaging the data of the generated multiple postage indicia in one or more data packets optimized or otherwise suitable for efficient communication to client device 140A via network 150.
Having received the requested multiple postage indicia, client device 140A may print or otherwise consume the multiple postage indicia at block 209. For example, postage client 141A may receive the multiple postage indicia data and generate postage indicia image data packets (e.g., bitmap images of IBI, such as may comprise human readable information and machine readable information, such as PDF 417 or data matrix barcode) suitable for controlling printer 142A to print postage indicia acceptable to a postal service or other shipping service provider.
In providing a system adapted to provide generation of multiple indicia in a single secure environment session, system 100B of
Although components of postal service system 110B (e.g., postage web service 160) may be adapted to facilitate generation of multiple postage indicia requested by different users, components of postal service system 110B (e.g., postage server 120) may be configured as described above with respect to postal service system 110A. Moreover, the components of postal service system 110B may be implemented as a single system, such as a single server, or as a distributed system, such as a server farm, a number of host systems disposed remotely with respect to each other, etc. For example, postage server 120 and postage web service 160 of postal services system 110B may be hosted by a same server. Alternatively, postage server 120 and postage web service 160 may be hosted by different servers according to embodiments herein.
Irrespective of a single or distributed implementation, as with postal services system 110A described above, postal services system 110B of embodiments may comprise a processor-based system operable under control of an instruction set or instruction sets defining operation as described herein. Accordingly, postal services system 110B of embodiments comprises one or more processors (e.g., a CORE or PENTIUM processor available from Intel, Inc.) and requisite processor readable (e.g., computer readable) memory (e.g., RAM, ROM, flash memory, disk memory, SSD memory, optical memory, and/or the like) and input/output components (e.g., display, NIC, keyboard, digital pointer, printer, and/or the like) coupled to a processor of the one or more processors via a data bus.
Postage server 120 of postal services system 110B of embodiments is configured as described above with respect to postal services system 110A. Accordingly, postage server 120 may comprise a processor-based system, including cryptocard 125 configurable as a PSD, in communication with postal database 121. Although postal database 121 is shown disposed within postage server 120, it should be appreciated that the postal database may be external or remote thereto.
Postage web server 160 may comprise a processor or processors and portion of the processor readable memory of postal services system 110B and corresponding instruction set operable to define postage web server operation as described herein, including queuing user requests for postage indicia, grouping postage indicia requests, composing bulk postage indicia requests, parsing/assigning generated postage indicia to the appropriate requesting user, etc. Postage web server 160 of embodiments may comprise a server (e.g., web server) or servers or virtual server operable within a suitable host environment (e.g., within a postal services system server).
Client devices 140B-140D of embodiments herein may comprise any number of system configurations used by a user for requesting, obtaining, and/or printing desired indicia, such as postage indicia. For example, one or more of client devices 140B-140D may comprise a general purpose processor-based system (e.g., personal computer (PC) having a processor, memory, suitable input/output (I/O) functionality, and operating system (OS)) operating under control of a postage web app (e.g., a respective one of postage web apps 143B-143D) providing a client application (e.g., PC client, web client, mobile client, tablet client, etc.) to interface with postal services system 110B and provide operation as described herein. Additionally or alternatively, one or more of client devices 140B-140D may comprise a processor-based device such as a smart phone, a tablet device, a personal digital assistant (PDA), an Internet appliance (e.g., a processor-based postage printer Internet appliance), etc., having the requisite instruction set (e.g., a respective one of postage web apps 143B-143D) and processing and I/O resources. The interface architecture implemented according to embodiments of the invention not only accommodate web based applet implementations, but may support other forms of client access including standalone client applications, third party software access integration, etc. Printers 142B-142D, such as may comprise any printer configuration (e.g., laser printer, ink jet printer, thermal printer, etc.) suitable for printing or otherwise rendering desired indicia, are coupled to respective ones of client devices 140B-140D of the illustrated embodiment. It should be appreciated that although three client devices are shown in
As described above with respect to the embodiment of
Flow 200B of
A postage indicia request of embodiments comprises information sufficient to generate at least one desired postage indicia for the requesting user. Accordingly, a postage indicia request may include information such as a postage amount, requested special service, mail class, hidden postage information, insurance information, tracking number, etc. Moreover, postage indicia requests preferably include user identification information (e.g., user account information, user credentials (e.g., user name, password, digital certificate, etc.), and/or the like), such as may be used to validate the user as an authorized user of the postal services system, to identify an account from which value for the postage indicia is to be debited and/or to which value is to be charged, to identify virtual PSD information associated with the requesting user, etc.
Postage web service 160 of embodiments may operate to authenticate the user, such as using user identification information of the postage indicia requests and/or user credentials provided therein or therewith. Such authentication may operate to identify the user as being authorized to receive the services of postal services system 110B. Additionally or alternatively, such authentication may associate the user with one or more accounts (e.g., as may be represented by corresponding ones of the PSDs of virtual PSD information 122-124) accessible to postal services system 120.
It should be appreciated that the requests for postage indicia made by client devices 140B-140D may be made independently of any other of the client devices, and thus may be received by postal services system 110B asynchronously, perhaps over a period of time. For example, as each client device of client devices 140B-140D is utilized by a user thereof to perform operations for which postage indicia are needed (e.g., generating one or more letters, envelopes, or other correspondence, process shipping labels, etc.), requests for postage indicia may be made to postal services system 110B. Accordingly, postage web service 160 of the illustrated embodiment comprises postage request queue 161 operable to store the requests for aggregation into one or more bulk postage request for multiple postage indicia.
At block 212 of the illustrated embodiment, postal services system 110B gathers multiple postage indicia requests for the users and composes one or more bulk postage indicia requests. For example, as shown in the functional block diagram of
It should be appreciated that logic of postage web service 160 may perform functions in addition to receiving indicia requests. For example, indicia request receive logic 362 of embodiments may utilize user identification information (e.g., user account information, user credentials (e.g., user name, password, digital certificate, etc.), and/or the like), as may be included in or in association with indicia requests, to validate the users as an authorized users of the postal services system, to identify an account or accounts from which value for the postage indicia is to be debited and/or to which value is to be charged, to identify virtual PSD information associated with the requesting users, etc. Additionally or alternatively, user identification information and/or client device information (e.g., MAC address information, IP address information, digital certificate, electronic serial number (ESN), hardware and/or software registration or serial numbers, etc., may be utilized by logic of postage web service 160 for associating indicia which is ultimately generated with the indicia request, and thus the requesting client device. For example, indicia request receive logic 362 may collect such information and provide that information to indicia response logic 363 for use in returning generated indicia to appropriate ones of client devices 140B-140D.
Continuing the operation at block 212 of the illustrated embodiment, having received indicia requests, logic (e.g., bulk request processing logic 364) of postage web service 160 may access the postage request queue and aggregate a plurality of postage indicia requests to compose a bulk request for multiple postage indicia according to embodiments of the invention. Such bulk requests for postage indicia may be composed periodically, aperiodically, etc. For example, when a threshold number of appropriate postage indicia requests have been queued, postage web service 160 may operate to compose one or more bulk postage request for the queued postage indicia requests. Additionally or alternatively, postage web service 160 may operate to compose one or more bulk postage requests for queued postage indicia requests after some predetermined period of time (e.g., once a minute, once an hour, etc.). Such periodic and aperiodic operation may be combined, such as to provide for composing one or more bulk postage indicia request if a threshold number of appropriate postage indicia requests have not been queued within some predetermined period of time.
Postage web service 160 of embodiments may operate to analyze the postage indicia requests in order to associate appropriate postage indicia requests in a same bulk postage indicia request. For example, the queued postage indicia requests may be analyzed by bulk request processing logic 364 to identify postage indicia requests having common or compatible characteristics, such as a same postage value, a same postal class, a same type of indicia, requested by users having access to a same postage meter account, and/or the like. Accordingly, a bulk postage indicia request may be comprised of a plurality of postage indicia requests sharing a same or similar characteristic, such as to facilitate or optimize operation of a crypto module in generating multiple indicia in a same secure environment session. Postage request queue 161 of embodiments may, therefore, comprise a plurality of postage request queues providing queuing of requests sharing a same or similar characteristic.
As with the embodiment discussed above with respect to
Having composed a bulk postage indicia request, in further operation at block 212 of embodiments the bulk postage indicia request of embodiments is provided to postage server 120 for processing and generation of multiple PSD. For example, assuming user authentication is successful and a suitable number of indicia requests have been received and aggregated to form a bulk postage indicia request, postage web server 160 may pass the bulk postage indicia request, or some portion thereof, to postage server 120 for initiating a session for generating multiple postage indicia.
At block 213 of the illustrated embodiment, logic of postage server 120 operates to process the bulk postage indicia request for facilitating operation by cryptocard 125 in generating multiple postage indicia in a same secure environment session. For example, postage server 120 may operate to associate the bulk postage request with particular virtual PSD information of virtual PSD information 122-124 storing postage value available to the user making the request. Additionally or alternatively, postage server 120 may provide processing of the bulk postage indicia request to provide the request, or some portion thereof, in a form usable by the PSD, such as to format the data for use by the PSD (e.g., serialize the data in a form understandable by logic of the PSD), to utilize a protocol compatible with the PSD, etc.
In operation according to embodiments, processing with respect to the bulk postage indicia request provided by logic of postal services system 110B may comprise a number of operations for facilitating postage indicia generation by cryptocard using virtual PSD information of postal database 121. For example, logic of postal services system 110B may calculate the total postage amount from the bulk postage indicia request data and determine if adequate total postage amount is available in the user PSD record for the bulk postage indicia request before acquiring a secure module (e.g., cryptocard 125) for generation of the postage indicia.
At block 214 of the illustrated embodiment a PSD bulk request (e.g., the bulk postage indicia request as processed by postal services system 110B) is provided to cryptocard 125. For example, after processing the bulk postage indicia request for facilitating operation by cryptocard 125 in generating multiple postage indicia in a same secure environment session, logic of postal services system 110B may provide the PSD bulk request to cryptocard 125 to initiate generation of the multiple postage indicia. In operation according to embodiments, providing the PSD bulk request to the cryptocard by logic of postal services system 110B may comprise a number of operations. For example, logic of postal services system 110B may operate to select a particular crypto module (e.g., cryptocard 125) for generation of the multiple postage indicia from a plurality of crypto modules (e.g., to select an available crypto module, to select a crypto module having specific capabilities, to provide load balancing among a pool of crypto modules, etc.). The selected crypto module may thereafter be locked for operation of the secure environment session to generate the multiple postage indicia.
It should be appreciated that the providing of the PSD bulk request may be done in association with providing other data to the cryptocard. For example, logic of postal services system 110B may operate to select a particular virtual PSD record for use in generating the multiple postage indicia. The virtual PSD information provided to cryptocard 125 may, for example, be selected based upon a particular service provider providing services to the users who's indicia requests are aggregated into the bulk postage indicia request and that the virtual PSD has sufficient account value associated therewith to support generation of the requested postage indicia. Additionally or alternatively, the virtual PSD information provided to cryptocard 125 may be selected based upon the available value balance of the PSD (e.g., selection of a particular virtual PSD having a lowest available value balance which is sufficient to provide the total value of the requested multiple postage indicia. The selected virtual PSD information of virtual PSD information 122-124 may be locked (e.g., to prevent its simultaneous use with respect to another crypto module, whereby value represented thereby may be consumed more than once) and the selected virtual PSD information provided to cryptocard 125 in order to configure cryptocard 125 for operation as a particular PSD.
Further, in association with the providing of the PSD bulk request to the cryptocard, logic of postal services system 110B may acquire and lock a check point record for that crypto module (e.g., from postal database 121). Such check point information may be utilized in providing an atomic transaction with respect to the generation of the multiple postage indicia. That is, if operation to generate the multiple postage indicia is interrupted or otherwise fails to complete the complete process of generating all the multiple postage indicia, and possibly logging information associated therewith, a check point record indicating a state of the PSD prior to initiating the postage indicia generation operation may be used to roll the PSD data back to its state prior to initiating the failed multiple postage indicia generation transaction. Such check point record information may be provided to cryptocard 125, such as with or in association with the virtual PSD information and/or PSD bulk request.
Having received the PSD bulk request according to flow 200B of the illustrated embodiment, cryptocard 125 operable as a PSD generates the multiple postage indicia of the PSD bulk request in a single secure environment session at block 215 of the illustrated embodiment. Here, as with the embodiment discussed above with respect to flow 200A, cryptocard 125 of embodiments is operable to load and decrypt the appropriate virtual PSD information, configure the memory (e.g., ascending register, descending register, strike count register, etc.) of the cryptocard as the corresponding PSD, generate each postage indicia of the multiple postage indicia, update appropriate PSD data (e.g., ascending register value, descending register value, strike count register value, etc.), and encrypt the virtual PSD information for offloading from the cryptocard. In operation according to embodiments, logic of cryptocard 125 may determine the number of postage indicia it is being requested to generate, determine the size of the memory for the indicia generation based on the total number of the postage requests, and generate multiple postage indicia data.
Logic of the PSD may, for example, operate to authenticate the request (e.g., as a request from a valid server or other requesting system and/or as a request from a valid user or users). Additionally or alternatively, logic of the PSD may operate to verify that sufficient value is present in the PSD for generation of the requested postage indicia. For example, the PSD logic may implement a loop in which the value for each of the multiple requested postage indicia is identified and summed to determine a total value for the requested indicia, whereby the total value may be compared to the value available from the PSD (e.g., the PSD descending register) to determine if sufficient value is present to allow generation of the multiple requested indicia. If, however, sufficient value is available, the logic of the PSD may again implement a loop to generate each of the requested postage indicia, storing the generated postage indicia data for providing to the postage server in a single response. In operation according to embodiments, the ascending and descending registers of the PSD are adjusted as each of the multiple postage indicia are generated. Additionally, a logging register of embodiments of the PSD is used to sum the value of each of the generated postage indicia to provide a total amount used with respect to logging data (e.g., used in generation of an audit indicia for logging purposes).
As previously described, cryptocard 125 of embodiments may operate to generate more than the requested multiple postage indicia when performing operation for generating multiple postage indicia in a single secure environment session. For example, logic of the cryptocard may generate logging and/or other data unique to the secure environment multiple postage indicia session. In operation according to embodiments, such logging data may include the number of indicia generated in the session, the total value of the indicia generated, the time/date of the generation session (e.g., the starting time, the ending time, or both), the starting and/or ending register values (e.g., ascending register, descending register, etc.), transaction number or other transaction identification information, meter/license number or other identification information, and the like.
At block 216 of the illustrated embodiment, cryptocard 125 may return logging or audit information for the multiple postage indicia for processing, storage, and/or reporting by postal services system 110B. For example, after the cryptocard generates postage indicia data for a multiple postage indicia request, intermediary code for the cryptocard may operate to write an audit log entry to the storage device (e.g., within postal database 121). Such audit information may comprise information regarding the number, value, type, etc. of the generated postage indicia, identification of the PSD (e.g., virtual PSD information) used to generate the postage indicia, and/or the like. Additionally or alternatively, such audit information may comprise one or more audit indicia, generated by cryptocard 125 in association with the multiple postage indicia, providing aggregated audit information (e.g., ending register values, number of postage indicia generated, identification information for each of the multiple postage indicia, etc.). Any or all of the foregoing information may be further processed, stored, and/or reported by logic of postal services system 110B. In operation according to embodiments, after such audit log information is written successfully, logic of cryptocard 125 may provide the generated postage indicia data for the multiple postage indicia, the updated virtual PSD information, and updated check point record to logic of postal services system 110B outside of the secure environment.
Accordingly, at block 217 of the illustrated embodiment of flow 200B the generated multiple postage indicia are passed from the secure environment of cryptocard 125. For example, the generated multiple postage indicia may be returned to logic of postage server 120 (e.g., bulk request processing logic 364), such as for further processing and providing to the requesting client device. It should be appreciated that information in addition to that of the multiple postage indicia may be returned from cryptocard 125 in association with the generated postage indicia. For example, cryptocard 125 may return the virtual PSD information, updated to reflect generation of the multiple postage indicia, for storage in postal database 121.
Processing of the multiple postage indicia returned from cryptocard 125 by postage web service 160 of embodiments includes assigning the generated postage indicia to the corresponding requesting client devices at block 218. For example, bulk request processing logic 364 may receive the generated indicia and provide the multiple indicia to indicia response logic 363, such as by storing the indicia to indicia storage 361 for access and processing by the indicia response logic. Indicia response logic 363 may operate to associate indicia of the multiple generated indicia with the appropriate users, user devices, and/or indicia requests, such as using information regarding the indicia requests provided by indicia request receive logic 362.
At block 219, postal services system 110B returns appropriate ones of the generated multiple postage indicia to the requesting client devices. It should be appreciated that logic of postal services system 110B may provide further processing with respect to the generated multiple postage indicia prior to its returning the generated multiple postage indicia to client device 140A. For example, postal services system 110A may provide processing of the multiple postage indicia returned by cryptocard 125 to provide the postage indicia data, or some portion thereof, in a form usable by the requesting client devices or other systems of system 100A, such as to format the data for use by client devices 140B-140D, for processing and communication by bridge server 130, and/or for efficient communication via network 150. Embodiments of postal services system 110A may provide processing to associate the appropriate postage indicia with the particular bulk postage indicia request made by respective ones of postage web apps 143C-143D in order to facilitate properly identifying the postage indicia with the operations at client devices 140B-140D for which the postage indicia was generated.
Having received the requested multiple postage indicia, client devices 140B-140D may each independently print or otherwise consume their respective indicia of the multiple postage indicia at block 220. For example, each postage web app of postage web apps 143B-143D may receive corresponding indicia data of the multiple postage indicia data and generate postage indicia image data packets (e.g., bitmap images of IBI, such as may comprise human readable information and machine readable information, such as PDF 417 or data matrix barcode) suitable for controlling an associated printer (e.g., a printer of printers 142B-142D, respectively) to print postage indicia acceptable to a postal service or other shipping service provider.
The multiple postage indicia as generated by postal services systems (e.g., postal services system 110A and/or postal services system 110B) of embodiments herein may comprise various forms and levels of completion. For example, indicia data packets suitable for use in completing generation of an acceptable postage indicium may be generated and provided to a client (e.g., postage client 141A and/or postage web apps 143B-143D) for processing and completion of the final postage indicia. Additionally or alternatively, the postage indicia data packets provided by a postal service system may comprise an IBI “light” form of indicia, whereby a reduced set of information is provided in the data packet with which the client device prints or otherwise consumes the generated indicia, while complete IBI data is generated by the PSD of the postal services system for use in authenticating and/or auditing the resulting IBI light indicia. Details with respect to the generation and use of IBI light indicia as may be utilized according to embodiments of the invention herein are shown and described in the above referenced patent application entitled “Computer-Based Value-Bearing Item Customization Security”.
It should be appreciated that although the functional blocks of postage web service 160 are described above with reference to flow 200B providing operation with respect to generation of multiple indicia requested by multiple users, such functional blocks may be utilized for flow 200A providing operation with respect to generation of multiple indicia requested by a same user. For example, indicia request receive logic 362, bulk request processing logic 364, and indicia response logic 363, perhaps with supporting infrastructure such as indicia storage 361 and/or postage request queue 161, may be disposed in client device 140A (e.g., provided as part of postage client 141A) of system 100A to provide aggregation of indicia requests into a bulk postage indicia request. In one embodiment, indicia request receive logic 362 and indicia response logic 363 may interact with one or more applications (e.g., document generation software, postage metering software, etc.) to accept postage indicia requests and provide postage indicia data in response thereto.
The foregoing embodiments provide generation of multiple indicia in a single secure environment session in response to a bulk indicia request. The number of indicia that may be generated in a single secure environment session may, however, be limited (e.g., limitations may be established whereby up to 10, 25, 50, 100, 250, 500, etc., indicia may be generated in a single session). For example, the number of indicia generated in a single secure environment session may be limited by the resources (e.g., processing capabilities, memory capacity, etc.) of a PSD providing the secure environment. Additionally or alternatively, the number of indicia generated in a single secure environment session may be limited to prevent undesired operational results, such as unavailability of one or more PSD for use by other users for an excessively long period of time, facilitating practicable rollback of transactions for atomic operation of a bulk indicia request, etc. Accordingly, particularly large bulk indicia requests may be processed in a plurality of batches for generating the multiple indicia requested thereby.
At block 401 of the illustrated embodiment of flow 400 a large bulk request, such as may be made by a client device or postage web service, is received by the postal services system. The large bulk request may be for multiple postage indicia for a single user (e.g., a bulk postage indicia request as utilized in flow 200A discussed above) and/or for multiple postage indicia for different users (e.g., a bulk postage indicia request as utilized in flow 200B discussed above). Irrespective of the particular users for which the multiple postage indicia are being requested, the large bulk request of embodiments is for a number of postage indicia greater (e.g., >10, 25, 50, 100, 250, 500, etc.) than a number that is to be served in a single secure environment session.
Postal services system of embodiments herein may operate to provide for generation of postage indicia using various PSD models. For example, a user or service provider serving one or more users may be provided with a single PSD from which all postage indicia for the user or service provider is to be generated. Such a model, although providing limited bandwidth for generation of postage indicia, provides a model in which a single meter balance may be managed and maintained, thereby providing a simple and relatively inexpensive postage metering solution. Alternatively, a user or service provider serving one or more users may be provided with a pool of PSDs from which postage indicia for the user or service provider is to be generated. Such a model, although providing multiple meter balances to be managed and maintained, provides a model in which improved bandwidth for generation of postage indicia is available, thereby facilitating serving multiple requests or otherwise generating multiple indicia at a time in parallel.
Accordingly, at block 402 of the illustrated embodiment a determination is made as to whether the account to be used with respect to the large bulk request is on a pooled PSD record model (e.g., multiple virtual PSDs are maintained for configuring a plurality of cryptocards for simultaneous use in association with the account). If it is determined that the account for the large bulk request is on a pooled PSD record model, processing according to the illustrated embodiment proceeds to block 409, whereby operation as described below is performed. However, if it is determined that the account for the large bulk request is not on a pooled PSD record model, processing according to the illustrated embodiment proceeds to block 403.
At block 403 the large bulk request is broken into smaller batch requests. For example, the large bulk request may be divided into two or more smaller batch requests, wherein each of the smaller batch requests comprises requests for a number of postage indicia less than or equal to a number that is to be served in a single secure environment session. The smaller batch requests may each comprise requests for an equal number of postage indicia (e.g., each smaller batch request comprising the number of postage indicia requests of the large bulk request divided by a smallest denominator which provides a resulting number of requests capable of accommodation in a single secure environment session) or for different numbers of postage indicia (e.g., one or more smaller batch requests comprising requests for a maximum number of postage indicia that can be accommodated in a single secure session and one smaller batch requests comprising requests for the remaining number of postage indicia to complete the large bulk request). The size and/or number of smaller batch requests broken out of a larger bulk request may be determined based upon a number of factors, such as to provide load balancing across available PSDs and/or postal servers, to provide requests having a number of requested postage indicia efficiently served by a PSD in a single secure environment session, to provide smaller request having a maximum number of postage indicia requests serviceable by a PSD in a single secure environment, etc.
The virtual PSD record for the virtual PSD to be used with respect to the account serving the large bulk request is preferably locked at block 404 (e.g., to prevent its simultaneous use with respect to another crypto module, whereby value represented thereby may be consumed more than once) and the selected virtual PSD information provided to a cryptocard in order to configure the cryptocard for operation as a particular PSD. The cryptocard to which the virtual PSD information is provided is preferably locked to prevent attempts to simultaneously configure the cryptocard as another/different PSD in response to another request. Additionally, a check point record for that crypto module may be acquired and locked, according to embodiments of the invention.
At block 405 of the illustrated embodiment the postage indicia for each of the smaller batch requests are generated and obtained. For example, each of the smaller batch requests may be provided to the PSD (e.g., as discussed above with respect to block 204 of flow 200A) serially for generation of the postage indicia (e.g., as discussed above with respect to block 205 of flow 200A or block 215 of flow 200B). The resulting generated postage indicia may then be received from the PSD after each such smaller batch request is processed.
Having generated the postage indicia of all of the smaller batch requests, the updated virtual PSD record is offloaded from the PSD and unlocked at block 406. Additionally, the cryptocard is preferably unlocked and the check point record is updated and unlocked to thereby make the cryptocard available for use in serving a different request.
At block 407 of the illustrated embodiment the postage indicia data returned in response to each of the smaller batch requests of the large bulk request are aggregated into a large bulk request response. For example, the multiple postage indicia data for each of the smaller batch requests may be processed to compose a single response to the large bulk request from which the smaller batch requests were divided. Thereafter, the large bulk request response may be provided to a node (e.g., postage client 141A or postage web service 160) which made the large bulk request, at block 408.
If, however, it was determined at block 402 that the account for the large bulk request is on a pooled PSD record model, processing according to the illustrated embodiment proceeds to block 409 wherein the large bulk request is broken into smaller batch requests. For example, the large bulk request may be divided into two or more smaller batch requests as discussed with respect to operation at block 403 above.
One or more virtual PSD record of the pool of virtual PSDs to be used with respect to the account serving the large bulk request are preferably locked at block 410 (e.g., to prevent its simultaneous use with respect to another crypto module, whereby value represented thereby may be consumed more than once) and the selected virtual PSD information provided to a corresponding number of cryptocards in order to configure the cryptocards each for operation as a particular PSD. The number of virtual PSDs to be utilized in serving the smaller batch requests, and thus the number of virtual PSD records selected, may dependent on the number of PSDs in the pool, the number of PSDs currently not otherwise in use, the number of smaller batch requests resulting from the large bulk request, a number of PSDs determined to facilitate generation of the multiple postage indicia within a satisfactory amount of time, etc. The cryptocards to which the virtual PSD information is provided are preferably locked to prevent attempts to simultaneously configure the cryptocards as another/different PSD in response to another request. Additionally, check point records for those crypto modules may be acquired and locked, according to embodiments of the invention.
Having configured the PSDs for serving the postage indicia requests, the particular ones of the unfulfilled smaller batch requests are assigned to available ones of the PSDs for operation to generate postage indicia at block 411. For example, assuming the large bulk request resulted in 3 smaller batch requests and the account associated with the postage indicia requests (e.g., the user's account, the service provider's account, etc.) then has 2 PSDs which are not otherwise in use, 2 virtual PSDs may be utilized to provide PSDs for generating the postage indicia. Accordingly, in an initial pass of operation at block 411, 2 of the smaller batch requests may be matched with the 2 PSDs for postage indicia generation, while the third smaller batch requests remains queued for matching to a PSD as one becomes available in a subsequent iteration.
At block 412 of the illustrated embodiment the postage indicia for each of the smaller batch requests currently matched to a PSD are generated and obtained. For example, each of the matched smaller batch requests may be provided to their respective PSDs (e.g., as discussed above with respect to block 204 of flow 200A or block 215 of flow 200B) in parallel for generation of the postage indicia (e.g., as discussed above with respect to block 205 of flow 200A). It should be appreciated that operation of the multiple PSDs serving the different smaller batch requests may be asynchronous, whereby such operation may begin and/or end at different times. Nevertheless, the resulting generated postage indicia may be received from the PSD after each such smaller batch request is processed.
Having received the generated postage indicia from one or more of the PSDs, a determination is made at block 413 of the illustrated embodiment as to whether any smaller batch requests remain to be served. If one or more smaller batch requests remain to be served, processing according to the illustrated embodiment returns to block 411 whereby some or all such unfulfilled smaller batch requests are matched with an available PSD. If, however, all smaller batch requests have been served (i.e., the postage indicia for each smaller batch request of the large bulk request have been obtained), processing according to the illustrated embodiment proceeds to blocks 406 et seq. whereby the PSD records are unlocked, the smaller batch requests responses are composed into a large bulk request response, and the large bulk request response is provided to the node (e.g., postage client 141A or postage web service 160) which made the large bulk request.
It should be appreciated that, although embodiments have been described above whereby a single smaller batch request or a single bulk postage indicia request are served by a PSD (e.g., a cryptocard configured with appropriate virtual PSD information) at any one time, where the processor of a PSD supports multi-threading embodiments may operate to use such PSDs to serve more than one such request at a time. For example, where cryptocard 125 supports multi-threading (e.g., using the 4765 cryptographic coprocessor available from International Business Machines Corporation), multiple virtual PSD records may be provided thereto in order to serve a corresponding number of smaller batch requests or bulk postage indicia requests in parallel according to embodiments of the invention.
From the forgoing it can be appreciated that the bulk requests of embodiments herein may be utilized to provide improved performance and an enhanced user experience by reducing the round trip calls from the client to the server of embodiments. Moreover, in many configurations the postal services system communicates with the crypto module using a peripheral component interconnect express (PCIE) bus or similar interconnect bus, rather than a direct memory access (DMA) or similar high speed bus, and thus the bulk and/or batch requests of embodiments herein facilitate improved performance with respect to the internal operation of the postal services system requesting and obtaining the indicia. Further, the bulk and batch requests made with respect to a crypto module of embodiments are atomic, whereby rollback of the full transaction upon a failure to successfully generate one indicia of the bulk/batch request is simplified (i.e., previously generated indicia of the bulk/batch request have not been passed serially from the secure environment and thus may be included in the rollback of the register values rather than voided and processed for refund externally from the secure environment).
It should be appreciated that the bulk requests for multiple indicia facilitated by embodiments of the present invention may be utilized in a variety of use situations. For example, a use scenario for the “single user” bulk request (here single user meaning a single enterprise, although multiple users within that enterprise may in fact be sourcing requests) may comprise a fulfillment warehouse situation. In such a warehouse situation, traditionally items may be picked and placed in shipping containers and an associated shipping label (e.g., containing postage value or prepaid value for shipping services) generated for each container as that container is processed serially on the fulfillment line. If generation of one such shipping label were to fail, the fulfillment line is delayed while the problem is resolved. However, in operation according to embodiments herein, a single shipping label bulk request may be made for a plurality of shipping labels (e.g., all shipping labels for a shipment processing period, such as a fraction of an hour, an hour, a fraction of a day, a day, etc.), whereby the transaction is atomic (i.e., either all requested shipping labels are returned or no shipping labels are returned). The fulfillment workflow may thus be revised, for example, such that all the shipping labels are generated in advance with the knowledge that all requested shipping labels will complete if any such shipping labels complete the generation process. Once all the indicia data for the shipping labels is generated, all such shipping labels may be printed. Having successfully generated all the indicia data to be generated for a shipment processing period, problems that may otherwise result from failures or delays in generating shipping labels are eliminated with respect to further fulfillment processing. With this model the fulfillment process may be performed faster and more reliably knowing that all the shipping label indicia generation for all the packages to be fulfilled will be/was successful.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3584696 | Eblowitz | Jun 1971 | A |
| 3594727 | Braun | Jul 1971 | A |
| 3691726 | Stephens et al. | Sep 1972 | A |
| 4119194 | Freeman et al. | Oct 1978 | A |
| 4253158 | McFiggans | Feb 1981 | A |
| 4376299 | Rivest | Mar 1983 | A |
| 4511793 | Racanelli | Apr 1985 | A |
| 4641347 | Clark et al. | Feb 1987 | A |
| 4725718 | Sansone et al. | May 1988 | A |
| 4743747 | Fougere et al. | May 1988 | A |
| 4744554 | Kulpa et al. | May 1988 | A |
| 4757537 | Edelmann et al. | Jul 1988 | A |
| 4763271 | Field | Aug 1988 | A |
| 4775246 | Edelmann et al. | Oct 1988 | A |
| 4800506 | Axelrod et al. | Jan 1989 | A |
| 4802218 | Wright et al. | Jan 1989 | A |
| 4812994 | Taylor et al. | Mar 1989 | A |
| 4831554 | Storace et al. | May 1989 | A |
| 4831555 | Sansone et al. | May 1989 | A |
| 4837701 | Sansone et al. | Jun 1989 | A |
| 4858138 | Talmadge | Aug 1989 | A |
| 4864618 | Wright et al. | Sep 1989 | A |
| 4868757 | Gil | Sep 1989 | A |
| 4873645 | Hunter et al. | Oct 1989 | A |
| 4893249 | Silverberg | Jan 1990 | A |
| 4900903 | Wright et al. | Feb 1990 | A |
| 4900904 | Wright et al. | Feb 1990 | A |
| 4900941 | Barton et al. | Feb 1990 | A |
| 4901241 | Schneck | Feb 1990 | A |
| 4908770 | Breault et al. | Mar 1990 | A |
| 4941091 | Breault et al. | Jul 1990 | A |
| 5058008 | Schumacher | Oct 1991 | A |
| 5065000 | Pusic et al. | Nov 1991 | A |
| 5067088 | Schneiderhan | Nov 1991 | A |
| 5075862 | Doeberl et al. | Dec 1991 | A |
| 5077792 | Herring | Dec 1991 | A |
| 5085470 | Peach | Feb 1992 | A |
| 5111030 | Brasington et al. | May 1992 | A |
| 5150407 | Chan | Sep 1992 | A |
| 5202834 | Gilham et al. | Apr 1993 | A |
| 5222018 | Sharpe et al. | Jun 1993 | A |
| 5233657 | Gunther et al. | Aug 1993 | A |
| 5237506 | Horbal et al. | Aug 1993 | A |
| 5239168 | Durst, Jr. et al. | Aug 1993 | A |
| 5289540 | Jones | Feb 1994 | A |
| 5319562 | Whitehouse | Jun 1994 | A |
| 5323323 | Gilham et al. | Jun 1994 | A |
| 5323465 | Avarne | Jun 1994 | A |
| 5341505 | Whitehouse | Aug 1994 | A |
| 5423573 | de Passille | Jun 1995 | A |
| 5454038 | Cordery et al. | Sep 1995 | A |
| 5483445 | Pickering | Jan 1996 | A |
| 5485369 | Nicholls et al. | Jan 1996 | A |
| 5490077 | Freytag et al. | Feb 1996 | A |
| 5510992 | Kara | Apr 1996 | A |
| 5583779 | Naclerio et al. | Dec 1996 | A |
| 5602743 | Freytag | Feb 1997 | A |
| 5606507 | Kara | Feb 1997 | A |
| 5606613 | Lee et al. | Feb 1997 | A |
| 5612541 | Hoffmann et al. | Mar 1997 | A |
| 5612889 | Pintsov et al. | Mar 1997 | A |
| 5619571 | Sandstrom et al. | Apr 1997 | A |
| 5623546 | Hardy et al. | Apr 1997 | A |
| 5649118 | Carlisle et al. | Jul 1997 | A |
| 5655023 | Cordery et al. | Aug 1997 | A |
| 5663547 | Ziarno | Sep 1997 | A |
| 5696829 | Cordery et al. | Dec 1997 | A |
| 5706502 | Foley et al. | Jan 1998 | A |
| 5708422 | Blonder et al. | Jan 1998 | A |
| 5715314 | Payne et al. | Feb 1998 | A |
| 5717596 | Bernard et al. | Feb 1998 | A |
| 5717597 | Kara | Feb 1998 | A |
| 5729459 | Brandien et al. | Mar 1998 | A |
| 5729460 | Plett et al. | Mar 1998 | A |
| 5729674 | Rosewarne et al. | Mar 1998 | A |
| 5742683 | Lee et al. | Apr 1998 | A |
| 5768132 | Cordery et al. | Jun 1998 | A |
| 5774886 | Kara | Jun 1998 | A |
| 5778076 | Kara et al. | Jul 1998 | A |
| 5796834 | Whitney et al. | Aug 1998 | A |
| 5801364 | Kara et al. | Sep 1998 | A |
| 5801944 | Kara | Sep 1998 | A |
| 5812991 | Kara | Sep 1998 | A |
| 5819240 | Kara | Oct 1998 | A |
| 5822739 | Kara | Oct 1998 | A |
| 5825893 | Kara | Oct 1998 | A |
| 5860068 | Cook | Jan 1999 | A |
| 5923885 | Johnson et al. | Jul 1999 | A |
| 5936885 | Morita et al. | Aug 1999 | A |
| 5946671 | Herring et al. | Aug 1999 | A |
| 5960418 | Kelly et al. | Sep 1999 | A |
| 5983209 | Kara | Nov 1999 | A |
| 6005945 | Whitehouse | Dec 1999 | A |
| 6010069 | Debois | Jan 2000 | A |
| 6047273 | Vaghi | Apr 2000 | A |
| 6061670 | Brand | May 2000 | A |
| 6061671 | Baker et al. | May 2000 | A |
| 6175825 | Fruechtel | Jan 2001 | B1 |
| 6199055 | Kara et al. | Mar 2001 | B1 |
| 6208980 | Kara | Mar 2001 | B1 |
| 6233565 | Lewis et al. | May 2001 | B1 |
| 6233568 | Kara | May 2001 | B1 |
| 6249777 | Kara et al. | Jun 2001 | B1 |
| 6385504 | Pintsov et al. | May 2002 | B1 |
| 6430543 | Lee et al. | Aug 2002 | B1 |
| 6470327 | Carroll et al. | Oct 2002 | B1 |
| 6532452 | Pintsov et al. | Mar 2003 | B1 |
| 6834273 | Sansone et al. | Dec 2004 | B1 |
| 6853990 | Thiel | Feb 2005 | B1 |
| 6865557 | Cordery et al. | Mar 2005 | B1 |
| 7149726 | Lingle et al. | Dec 2006 | B1 |
| 7182259 | Lubow et al. | Feb 2007 | B2 |
| 7225170 | Ryan, Jr. | May 2007 | B1 |
| 7266531 | Pintsov et al. | Sep 2007 | B2 |
| 7337152 | Gawler | Feb 2008 | B1 |
| 7343357 | Kara | Mar 2008 | B1 |
| 7458612 | Bennett | Dec 2008 | B1 |
| 7509291 | McBride et al. | Mar 2009 | B2 |
| 7548612 | Weissman et al. | Jun 2009 | B2 |
| 7711650 | Kara | May 2010 | B1 |
| 7778924 | Ananda | Aug 2010 | B1 |
| 7784090 | Lord et al. | Aug 2010 | B2 |
| 7831518 | Montgomery et al. | Nov 2010 | B2 |
| 7831824 | Abdulhayoglu | Nov 2010 | B2 |
| 7840492 | Leung et al. | Nov 2010 | B2 |
| 7954709 | Leon et al. | Jun 2011 | B1 |
| 7963437 | McBride et al. | Jun 2011 | B1 |
| 8027927 | Ogg et al. | Sep 2011 | B2 |
| 8027935 | Begen | Sep 2011 | B1 |
| 8041644 | Ogg et al. | Oct 2011 | B2 |
| 8046823 | Begen et al. | Oct 2011 | B1 |
| 8100324 | Leon | Jan 2012 | B1 |
| 8204835 | Ogg | Jun 2012 | B1 |
| 8240579 | Bennett | Aug 2012 | B1 |
| 8600910 | Kara et al. | Dec 2013 | B2 |
| 8612361 | Bussell et al. | Dec 2013 | B1 |
| 8626673 | Bennett | Jan 2014 | B1 |
| 8775331 | Tsuie et al. | Jul 2014 | B1 |
| 9208620 | Bortnak et al. | Dec 2015 | B1 |
| 9761061 | Bussell et al. | Sep 2017 | B1 |
| 20010007086 | Rogers et al. | Jul 2001 | A1 |
| 20010020234 | Shah et al. | Sep 2001 | A1 |
| 20010022060 | Robertson et al. | Sep 2001 | A1 |
| 20010042052 | Leon | Nov 2001 | A1 |
| 20020032573 | Williams et al. | Mar 2002 | A1 |
| 20020032668 | Kohler et al. | Mar 2002 | A1 |
| 20020032784 | Darago et al. | Mar 2002 | A1 |
| 20020052841 | Guthrie et al. | May 2002 | A1 |
| 20020065577 | Teraura et al. | May 2002 | A1 |
| 20020073050 | Gusler et al. | Jun 2002 | A1 |
| 20020082935 | Moore et al. | Jun 2002 | A1 |
| 20020095347 | Cummiskey | Jul 2002 | A1 |
| 20020099652 | Herzen et al. | Jul 2002 | A1 |
| 20020116318 | Thomas et al. | Aug 2002 | A1 |
| 20020143431 | Sansone | Oct 2002 | A1 |
| 20030009425 | Stonedahl et al. | Jan 2003 | A1 |
| 20030029914 | Hortman et al. | Feb 2003 | A1 |
| 20030037008 | Raju et al. | Feb 2003 | A1 |
| 20030065739 | Shnier | Apr 2003 | A1 |
| 20030080182 | Gunther | May 2003 | A1 |
| 20030101143 | Montgomery et al. | May 2003 | A1 |
| 20030101148 | Montgomery et al. | May 2003 | A1 |
| 20030130963 | Stickler et al. | Jul 2003 | A1 |
| 20030138345 | Schwabe | Jul 2003 | A1 |
| 20030167241 | Gilham | Sep 2003 | A1 |
| 20030182155 | Nitzan et al. | Sep 2003 | A1 |
| 20030187666 | Leon | Oct 2003 | A1 |
| 20030204477 | McNett | Oct 2003 | A1 |
| 20030217018 | Groff et al. | Nov 2003 | A1 |
| 20030233276 | Pearlman et al. | Dec 2003 | A1 |
| 20030236709 | Hendra et al. | Dec 2003 | A1 |
| 20040002926 | Coffy et al. | Jan 2004 | A1 |
| 20040048503 | Mills et al. | Mar 2004 | A1 |
| 20040064422 | Leon | Apr 2004 | A1 |
| 20040083179 | Sesek et al. | Apr 2004 | A1 |
| 20040083189 | Leon | Apr 2004 | A1 |
| 20040089482 | Ramsden et al. | May 2004 | A1 |
| 20040122776 | Sansone | Jun 2004 | A1 |
| 20040122779 | Stickler et al. | Jun 2004 | A1 |
| 20040128264 | Leung et al. | Jul 2004 | A1 |
| 20040185827 | Parks | Sep 2004 | A1 |
| 20040185882 | Gecht et al. | Sep 2004 | A1 |
| 20040186811 | Gullo et al. | Sep 2004 | A1 |
| 20040212833 | Taskett et al. | Oct 2004 | A1 |
| 20040215581 | Lord et al. | Oct 2004 | A1 |
| 20040215583 | Elliott | Oct 2004 | A1 |
| 20040230544 | Herbert | Nov 2004 | A1 |
| 20040254808 | Bennett et al. | Dec 2004 | A1 |
| 20050065892 | Ryan, Jr. et al. | Mar 2005 | A1 |
| 20050065896 | Kummer et al. | Mar 2005 | A1 |
| 20050065897 | Ryan et al. | Mar 2005 | A1 |
| 20050071244 | Phillips et al. | Mar 2005 | A1 |
| 20050080751 | Burningham | Apr 2005 | A1 |
| 20050114222 | Mundy | May 2005 | A1 |
| 20050116047 | Lu et al. | Jun 2005 | A1 |
| 20050119786 | Kadaba | Jun 2005 | A1 |
| 20050171791 | Chimenti et al. | Aug 2005 | A1 |
| 20050171869 | Minnocci | Aug 2005 | A1 |
| 20050192899 | Reardon | Sep 2005 | A1 |
| 20050237203 | Burman et al. | Oct 2005 | A1 |
| 20050256811 | Pagel et al. | Nov 2005 | A1 |
| 20050278266 | Ogg et al. | Dec 2005 | A1 |
| 20060000648 | Galtier | Jan 2006 | A1 |
| 20060020505 | Whitehouse | Jan 2006 | A1 |
| 20060122947 | Poulin | Jun 2006 | A1 |
| 20060173700 | Fenelon | Aug 2006 | A1 |
| 20060173796 | Kara | Aug 2006 | A1 |
| 20060220298 | Fairweather et al. | Oct 2006 | A1 |
| 20060259390 | Rosenberger | Nov 2006 | A1 |
| 20060282271 | Anada et al. | Dec 2006 | A1 |
| 20060283943 | Ostrowski et al. | Dec 2006 | A1 |
| 20070033110 | Philipp et al. | Feb 2007 | A1 |
| 20070073587 | Walker et al. | Mar 2007 | A1 |
| 20070078795 | Chatte | Apr 2007 | A1 |
| 20070080228 | Knowles et al. | Apr 2007 | A1 |
| 20070174213 | Whitehouse et al. | Jul 2007 | A1 |
| 20070174215 | Morel | Jul 2007 | A1 |
| 20070255664 | Blumberg et al. | Nov 2007 | A1 |
| 20080154781 | Kumar | Jun 2008 | A1 |
| 20080281719 | Hall et al. | Nov 2008 | A1 |
| 20090164392 | Raju et al. | Jun 2009 | A1 |
| 20090172084 | Lavanya et al. | Jul 2009 | A1 |
| 20090265585 | Ikegami | Oct 2009 | A1 |
| 20100169241 | Schoonmaker et al. | Jul 2010 | A1 |
| 20100235267 | Brookner et al. | Sep 2010 | A1 |
| 20100298662 | Yu et al. | Nov 2010 | A1 |
| 20100312627 | Khechef et al. | Dec 2010 | A1 |
| 20110015935 | Montgomery et al. | Jan 2011 | A1 |
| 20110022544 | Kim et al. | Jan 2011 | A1 |
| 20110029429 | Whitehouse | Feb 2011 | A1 |
| 20110071944 | Heiden et al. | Mar 2011 | A1 |
| 20110145107 | Greco | Jun 2011 | A1 |
| 20110225180 | Liao et al. | Sep 2011 | A1 |
| 20110242554 | Farry et al. | Oct 2011 | A1 |
| 20110295646 | Barros | Dec 2011 | A1 |
| 20120008766 | Robertson et al. | Jan 2012 | A1 |
| 20120054754 | Teichmann et al. | Mar 2012 | A1 |
| 20120109777 | Lipsitz et al. | May 2012 | A1 |
| 20120159603 | Queck | Jun 2012 | A1 |
| 20120233252 | Vats et al. | Sep 2012 | A1 |
| 20120240204 | Bhatnagar et al. | Sep 2012 | A1 |
| 20130056533 | Zimberoff et al. | Mar 2013 | A1 |
| 20130061337 | Zimberoff et al. | Mar 2013 | A1 |
| 20130066794 | Hill et al. | Mar 2013 | A1 |
| 20130254132 | Srinath et al. | Sep 2013 | A1 |
| 20140019517 | Fawcett | Jan 2014 | A1 |
| 20140067665 | Paletz et al. | Mar 2014 | A1 |
| 20140265300 | Jena | Sep 2014 | A1 |
| 20140324633 | Pollak et al. | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2470371 | May 2003 | CA |
| 0137737 | Apr 1985 | EP |
| 0571259 | Nov 1993 | EP |
| 0927958 | Jul 1999 | EP |
| 0927963 | Jul 1999 | EP |
| 1785856 | May 2007 | EP |
| 2580844 | Oct 1986 | FR |
| 2251210 | Jul 1992 | GB |
| 04284558 | Oct 1992 | JP |
| 2000-105845 | Apr 2000 | JP |
| WO-8801818 | Mar 1988 | WO |
| WO-9740472 | Oct 1997 | WO |
| WO-9814907 | Apr 1998 | WO |
| WO-9814909 | Apr 1998 | WO |
| WO-9857302 | Dec 1998 | WO |
| WO-9857460 | Dec 1998 | WO |
| WO-02063517 | Aug 2002 | WO |
| WO-02093498 | Nov 2002 | WO |
| WO-03039051 | May 2003 | WO |
| WO-03083784 | Oct 2003 | WO |
| Entry |
|---|
| Ford, C., “Frequent Flyer Programs,” Australian Accountant, 63,1, Feb. 1993, pp. 52-58, 7 pages. |
| Alexander, K.L., “U.S. Stamps Pay Tribute to Starry-Eyed Jurors,” Final Edition, Calgary Herald, Calgary, Alberta, Canada, Sep. 14, 2007, 2 pages. |
| Non-Final Office Action dated Aug. 3, 2009 for U.S. Appl. No. 11/353,690 to Kara, filed Feb. 14, 2006, and entitled “System and Method for Validating Postage,” 19 pages. |
| “Domestic Mail Manual Section 604,” United States Postal Service, Aug. 31, 2005, 45 pages. |
| “Mobile Postage stamps via text message announced”, http://telecoms.cytalk.com/2011/03/mobile-postage-stamps-via-text-messages-announced/, CY.TALK Telecoms News Blog, Mar. 14, 2011 in Telecoms, Texting, pp. 1-9. |
| Mobile Postage Stamps Via Text Messages Announced, Phone Reviews, Mobile Phones, News, Mar. 11, 2011, pp. 1-3. |
| Anonymous, “Automated Indicia Detection System From Parascript Protects Postage Revenue for Postal Operators, Cracks Down on Fraud:—Parascript StampVerify Simplifies Complex Task of Automatically Locating and Verifying Different Types of Indicia on Envelope Images-,” PR Newswire, New York, Sep. 18, 2007, 2 pages. |
| Davies, Brad L. “Printing System for Preventing Injustice by Delivering Print Data from Postal Charge Meter to Printer,” Jan. 2001, 1 page. |
| Unpublished U.S. Appl. No. 12/103,496 to Bortnak et al., filed Apr. 15, 2008 and entitled “Systems and Methods for Activation of Postage Indicia at Point of Sale,” 40 pages. |
| Unpublished U.S. Appl. No. 11/509,309 to Leon filed Aug. 24, 2006 and entitled “Invisible Fluorescent Ink Mark,” 15 pages. |
| Unpublished U.S. Appl. No. 12/030,739 to McBride et al. filed Feb. 13, 2008 and entitled “Systems and Methods for Distributed Activation of Postage,” 35 pages. |
| Unpublished U.S. Appl. No. 11/323,463 to Leon et al. filed Dec. 30, 2005 and entitled “Systems and Methods for Single Pass Printing Postage Indicia,” 23 pages. |
| Unpublished U.S. Appl. No. 10/606,579 to Ogg, filed Jun. 26, 2003 and entitled “System and Method for Automatically Processing Mail,” 15 pages. |
| International Search Report Issued for PCT/US95/00237, dated May 29, 1995, 4 pages. |
| International Search Report and Written Opinion issued for PCT Applicaton No. PCT/US2017/020662, dated May 19, 2017, 14 pages. |
