The invention disclosed herein relates generally to postage printing systems, and more particularly to postage printing systems that utilize multiple customer accounts without having to maintain funds in each of the customer accounts.
Conventional postage printing systems utilize a pre-paid accounts in which funds are stored in a register for use to generate and print postage. In a conventional closed postage metering system, each postage printing device maintained its own funds register in a secure device, known as a postal security device (PSD). Examples of closed postage metering systems include mailing machines that often include different modules that automate the processes of producing mail pieces. Mail pieces can include, for example, envelopes, post cards, flats, and the like. The typical mailing machine includes a variety of different modules or sub-systems each of which performs a different task on the mail piece. The PSD would generate indicia for printing on mail pieces, utilizing the funds stored therein. In conventional mail processing systems, the PSD is configured for a specific application at time of initialization. This typically happens at a stage late in the manufacturing process. Once configured, the PSD is locked into that specific configuration throughout its life. Being locked into a specific configuration limits the potential uses of the mail processing system. In situations where it may be desired to support multiple carriers and customers, such as for example, in a mailhouse environment or a shared mail processing system environment, it would be necessary to utilize multiple mail processing systems.
To overcome this problem, the ability to dynamically configure a postage printing system has been proposed. Customer accounts are maintained by the postage vendor in a remote database. Each customer account maintains the information necessary to generate postage for that customer, including pre-paid funds required to pay for the postage. When a customer desires to print postal indicia, the customer account is retrieved from a remote database for use in generating the indicia. When the customer is finished, the customer account is updated and returned to the remote database. Thus, the PSD of a postage printing system is not locked into a single configuration, but instead can be dynamically configured for a plurality of different customer accounts. While this greatly improves the flexibility of such systems, there are still some problems from the customer's point of view. In many instances, it will be necessary for a customer to maintain multiple customer accounts as it may be desired to operate more than one device at the same time to generate postal indicia. For example, a business may utilize more than one mailing machine, on-line postage printing using a personal computer or other similar device, or combination of the two. For each account, it is necessary for the customer to maintain some minimum amount of funds stored therein for use in generating postage. This means the customer has to have funds tied up in multiple accounts, which is not desirable for many customers.
It would be desirable, therefore, to be able to support multiple customer accounts without having to maintain separate funds in each account.
The present invention alleviates the problems noted above and provides a system and method for allowing a customer to maintain multiple customer accounts used for generating and printing postage without having to maintain a minimum amount of funds in each account.
In accordance with the present invention, when multiple accounts are maintained for a customer, only one the of the multiple accounts maintains pre-paid funds in the registers. The other accounts do not have any pre-paid funds, i.e., maintain zero funds, in the registers. When a customer account that does not have any pre-paid funds stored therein is utilized to generate postage, the register in that account is refilled for the exact amount of postage to be generated from a customer payment account. By performing on-demand postage refills for the exact amount needed to generate an indicium, the customer is no longer required to have funds committed to each customer account while still being able to utilize multiple accounts for multiple postage printing devices.
Therefore, it should now be apparent that the invention substantially achieves all the above aspects and advantages. Additional aspects and advantages of the invention will be set forth in the description that follows, and in part will be obvious from the description, or may be learned by practice of the invention. Moreover, the aspects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out in the appended claims.
The accompanying drawings illustrate presently preferred embodiments of the invention, and together with the general description given above and the detailed description given below, serve to explain the principles of the invention. As shown throughout the drawings, like reference numerals designate like or corresponding parts.
FIG illustrates a system according to an embodiment of the present invention; and
In describing the present invention, reference is made to the drawings, wherein there is seen in
A database 26 is coupled to the server 20. Database 26 is used to store customer account records that are utilized to configure a HSM when downloaded to the HSM. Each customer record is associated with a specific customer and specific account for that customer and includes information that enables the HSD to generate indicia for the specific customer. Thus, a separate customer record will exist for each possible customer, e.g., Customer A, Customer B, Customer C, . . . Customer N, and separate accounts for each customer having multiple accounts, e.g., Account 1, Account 2, Account 3, etc. Each customer record can include, for example, the following information: an identification number, a current upload count, one or more cryptographic keys required to generate indicia or ensure print security, a plurality of register values associated with accounting, a serial number count for generated indicia, a postal code for the customer account record, and any additional parameters required for the generation and accounting of indicia that may be required, including carrier specific requirements. The identification number is associated with a particular customer, and provides a suitable identification of the meter record to allow the appropriate record to be downloaded upon request. The register values can include, for example, an ascending register value (value of all postage ever expended), a descending register value (value of pre-paid postage remaining in meter record), a piece count, and any other register values associated with the record that are desired to be maintained. For those customers that maintain multiple customer accounts, only a single account maintains pre-paid funds in the descending register value, while the other accounts for that customer maintain a zero balance in the descending register. Thus, for example, for Customer A, only Account 1 would maintain some minimum balance of pre-paid funds, while the other accounts for Customer A (Account 2 and Account 3) would not maintain any pre-paid funds (zero balance). Refills of the pre-funded account are processed by the server 20 when the amount of funds fails below some predetermined minimum threshold. When this occurs, the server 20 can replenish funds to the customer account record using standard refill techniques, as are known in the art for postage payment systems, from a customer payment account 42. Customer payment account 42 can be a credit account, pre-paid account, interest bearing account, or the like from which funds are drawn or acquired for use in funding the customer account records. Customer payment account 42 can be maintained by the server 20 (sometimes referred to as a vault), or can be any type of account, such as, for example, a bank account, that the server 20 can access for funds via the network 40. An example of such accounts and refill process is given in U.S. Pat. No. 7,526,454, the contents of which are hereby incorporated by reference.
System 10 can also include other types of postage printing devices, such as, for example, a personal computer 30 coupled to a standard printer 32. Personal computer 32 could be any type of processing device that can support the request and printing of postage, such as a standard personal computer, laptop, tablet or the like. Personal computer 32 requests postage from the server 20 via the network 40, and server 20 uses its HSM 24 to generate indicia for return to the personal computer 30 for printing using printer 32. In this manner, it is not necessary for personal computer 32 to have its own HSM, and instead the HSM 24 of server 20 can be used to provide postage for a plurality of such devices. The PC 30 and printer 32, in combination with the HSM 24 of the data center 20, constitutes a postage printing device.
In step 52, a control unit of the data center server 20 determines if the request for the specified customer account record is valid. This can include, for example, verifying the digital signature included with the request. If the request is not valid, then in step 54 an error message is returned which alerts the user that the request message was invalid. Optionally, processing can return to step 50 to allow the user to retry the request or make a new request. If it is determined in step 52 that the request is a valid request, then in step 56 the server 20 prepares and sends a download to the requesting device, i.e., HSM 14a of device 12a. Such a download includes the requested customer account record retrieved from the database 26. Since this is the first request for a customer account record from Customer A, preferably the first account, e.g., Account 1, which maintains pre-funded registers will be returned to the device 12a. Preferably, the download includes a digital signature that can be verified by the HSM 14a for added security. For purposes of this application, it is to be understood that the customer account record that is downloaded can be either the actual account record or an image of the account record with the actual account record being maintained in the database 26.
In step 58, the HSM 14a of device 12a is configured using the customer account record, i.e., Customer A, Account 1, received from the data center server 20. Optionally, before configuration, the HSM 14a can validate the received download. Such validation can include verifying the digital signature provided with the download. Once the HSM 14a has been configured, the device 12a can be used to process mail pieces and generate postal indicia. The generation of indicia and all accounting for each indicia generated are performed locally by HSM 14a using the customer account record stored in the HSM 14a, and all register values and date maintained in the customer account record are updated during the processing of the mail. Upon completion of the processing of the mail using the customer account record stored in HSM 14a, the updated customer account record, which now reflects the mail that has been processed, can be returned to the data center server 20 for storage in database 26.
Now suppose that while the Customer A, Account 1 customer account record is being used by device 12a, Customer A requests that another device be used to also generate indicia. For example, suppose that Customer A desires to also use the PC 30 to generate indicia. In step 60, a communication is established between the PC 30 and the data center server 20 via the network 40 and the customer requests configuration of the PC 30 using a customer account record stored in database 26. In step 62, the data center server 20 determines if the request for the specified customer account record is valid similarly as described above with respect to step 52. If the request is not valid, then in step 64 an error message is returned which alerts the user that the request message was invalid. Optionally, processing can return to step 60 to allow the user to retry the request or make a new request. If it is determined in step 62 that the request is a valid request, then in step 66 the server 20 prepares a download to be sent to configure the requesting device, i.e., PC 30. Recall that as described above, PC 30 utilizes the HSM 24 of server 20 to generate indicia. Such a download includes the requested customer account record retrieved from the database 26. Since the first account for Customer A, e.g., Account 1, which maintains pre-funded registers, is already in use by the device 12a, another customer account record, e.g., Account 2, for Customer A will be retrieved from the database 26.
In step 68, the PC 30/HSM 24 is configured to print postage using the customer account record, i.e., Customer A, Account 2, retrieved from the database 26. Optionally, before configuration, the HSM 24 can validate the received download. Such validation can include verifying the digital signature provided with the download. Once the HSM 24 has been configured, the PC 30 can utilize the HSM 24 to generate indicia, which can be returned to the PC 30 via the network 40 and printed using the printer 32, as follows. Since Account 2 for Customer A does not maintain any pre-funded registers, it is necessary to obtain funds before any indicia can be generated. In step 70, the HSM 24 receives, from the PC 30, a request for an indicium for a specified amount of postage. In step 72, the HSM 24 sends a request to the control unit of the data center server 20 to refill the Customer Account 2 with funds for the specified amount. Preferably, such requests can be made secure using digital signature or the like. In step 74, the server 20 will perform a refill process to provide the HSM 24 that is using the Customer Account 2 with an amount of funds from the customer payment account 42 equal to the specified postage amount. Thus, the HSM 24 will have funds available on-demand to utilize for generation of postage. In step 76, the funds that were refilled to Customer Account 2 are used by HSM 24 to generate an indicium for return to the PC 30 for printing by printer 32. By performing an on demand postage refill for the exact amount needed to generate the indicium, a single customer can use multiple customer account records in multiple devices to generate indicia, while only having to maintain a single pre-funded account.
While preferred embodiments of the invention have been described and illustrated above, it should be understood that they are exemplary of the invention and are not to be considered as limiting. Additions, deletions, substitutions, and other modifications can be made without departing from the spirit or scope of the present invention. Accordingly, the invention is not to be considered as limited by the foregoing description but is only limited by the scope of the appended claims.