Patent Grant
7149726
The present invention relates to secure printing of value-bearing items (VBI) preferably, postage. More specifically, the invention relates to a graphical user interface (GUI) for printing of VBI in a computer network environment.
A significant percentage of the United States Postal Service (USPS) revenue is from metered postage. Metered postage is generated by utilizing postage meters that print a special mark, also known as postal indicia, on mail pieces. Generally, printing postage and any VBI can be carried out by using mechanical meters or computer-based systems.
With respect to computer-based postage processing systems, the USPS under the Information-Based Indicia Program (IBIP) has published specifications for IBIP postage meters that identify a special purpose hardware device, known as a Postal Security Device (PSD) that is generally located at a user's site. The PSD, in conjunction with the user's personal computer and printer, functions as the IBIP postage meter. The USPS has published a number of documents describing the PSD specifications, the indicia specifications and other related and relevant information. There are also security standards for printing other types of VBI, such as coupons, tickets, gift certificates, currency, voucher and the like.
A significant drawback of existing hardware-based systems is that a new PSD must be locally provided to each new user, which involves significant cost. Furthermore, if the additional PSD breaks down, service calls must be made to the user location. In light of the drawbacks in hardware-based postage metering systems, a software-based system has been developed that does not require specialized hardware for each user. The software-based system meets the IBIP specifications for a PSD, using a centralized server-based implementation of PSDs utilizing one or more cryptographic modules. The system also includes a database for all users' information. The software-based system, however, has brought about new challenges.
The software-based system should be able to handle secure communications between users and the database. The system should also be user friendly and be able to provide the user with a step-by-step process for installing the client software, registering with the system, printing the postage value, maintaining and monitoring the user account information, and the like.
Therefore, there is a need for a new method and apparatus for implementation of VBI printing via a user friendly GUI with a variety of selectable options.
In accordance with one aspect of the present invention, an on-line VBI printing system that includes one or more cryptographic modules and a central database has been designed. The cryptographic modules serve the function of the PSDs and are capable of implementing a variety of required security standards. A client system provides a user friendly GUI for facilitating the interface of the user to the system. The GUI system includes wizards that help the user step-by-step with processes of installation, registration, and printing
In one aspect, the invention describes an on-line system for printing a value bearing item (VBI) that includes a client system for interfacing with a user comprising; a GUI for installing software for printing the VBI; a GUI for registering the user in the system; and a GUI for managing the printing of the VBI; and a server system capable of communicating with the client system over a computer network for authorizing the client system to print the VBI.
Other features of the present invention include a GUI for making changes to the user's information; a GUI for displaying the user information including an account information, wherein the account information includes an amount of credit left in the account; a GUI for specifying an address book so that the system can use the address book to print addresses; and a GUI for entering a password so that the server system can store the entered password and verify the password. In one embodiment, the server system includes an address matching module for verifying an address entered by the user.
In another aspect, the invention describes a method for printing a value bearing item (VBI) over a computer network having a client system and a server system comprising the steps of: displaying a first GUI by the client system for registering a user with the server system over the computer network; establishing communication with the server via the network; entering user information in the first GUI; communicating the entered user information to the server; displaying a second GUI by the client system including printing options for managing the printing of the VBI; selecting one or more printing options from the second GUI; and printing the VBI according to the selected one or more printing options.
The objects, advantages and features of this invention will become more apparent from a consideration of the following detailed description and the drawings, in which:
An exemplary on-line postage system is described in U.S. patent application Ser. No. 09/163,993 filed Sep. 15, 1998, the entire content of which is hereby incorporated by reference herein. The on-line postage system includes an authentication protocol that operates in conjunction with the USPS. The system utilizes on-line postage system software comprising user code that resides on a client system and controller code that resides on a server system. The on-line postage system allows a user to print a postal indicium at home, at the office, or any other desired place in a secure, convenient, inexpensive and fraud-free manner. The system comprises a user system electronically connected to a server system, which in turn is in communication with a USPS system.
Each of the cryptographic modules may be available for use by any user. When a user requests a PSD service, one of the available modules is loaded with data belonging to the user's account and the transaction is performed. When a module is loaded with a user's data, that module becomes the user's PSD. The database record containing each user's PSD data is referred to as the “PSD package”. After each PSD transaction is completed, the user's PSD package is updated and returned to a database external to the module. The database becomes an extension of the module's memory and stores not only the items specified by the IBIP for storage inside the PSD, but also the user's personal cryptographic keys and other security relevant data items (SRDI) and status information needed for operating continuity. Movement of this sensitive data between the modules and the database is secured to ensure that PSD packages could not be compromised.
In one embodiment, the server system is remotely located in a separate location from the client system. All communications between the client and the server are preferably accomplished via the Internet.
An increase in the number of servers within the server system 102 will not negatively impact the performance of the system, since the system design allows for scalability. The Server system 102 is designed in such a way that all of the business transactions are processed in the servers and not in the database. By locating the transaction processing in the servers, increases in the number of transactions can be easily handled by adding additional servers. Also, each transaction processed in the servers is stateless, meaning the application does not remember the specific hardware device the last transaction utilized. Because of this stateless transaction design, multiple servers can be added to each appropriate subsystem in order to handle increased loads.
Furthermore, each cryptographic module is a stateless device, meaning that a PSD package can be passed to any device because the application does not rely upon any information about what occurred with the previous PSD package. Therefore, multiple cryptographic modules can also be added to each appropriate subsystem in order to handle increased loads. A PSD package for each cryptographic module is a database record, stored in the server database, that includes information pertaining to one customer's service that would normally be protected inside a cryptographic module. The PSD package includes all data needed to restore the PSD to its last known state when it is next loaded into a cryptographic module. This includes the items that the IBIP specifications require to be stored inside the PSD, information required to return the PSD to a valid state when the record is reloaded from the database, and data needed for record security and administrative purposes.
In one embodiment, the items included in a PSD package include ascending and descending registers (the ascending register “AR” records the amount of postage that is dispensed or printed on each transaction and the descending register “DR” records the value or amount of postage that may be dispensed and decreases from an original or charged amount as postage is printed.), device ID, indicia key certificate serial number, licensing ZIP code, key token for the indicia signing key, the user secrets, key for encrypting user secrets, data and time of last transaction, the last challenge received from the client, the operational state of the PSD, expiration dates for keys, the passphrase repetition list and the like.
As a result, the need for specific PSDs being attached to specific cryptographic modules is eliminated. A Postal Server subsystem provides cryptographic module management services that allow multiple cryptographic modules to exist and function on one server, so additional cryptographic modules can easily be installed on a server. The Postal Sever subsystem is easy to scale by adding more cryptographic modules and using commonly known Internet load-balancing techniques to route inbound requests to the new cryptographic modules.
Referring back to
Cryptographic modules 110 are responsible for creating PSDs and manipulating PSD data to protect sensitive information from disclosure, generating the cryptographic components of the digital indicia, and securely adjusting the user registers. When a user wishes to print VBI, for example, postage or purchase additional VBI or postage value, a user state is instantiated in the PSD implemented within one of the cryptographic modules 110. Database 111 includes all the data accessible on-line for indicia creation, account maintenance, and revenue protection processes. Postage servers 109, Database 130, and cryptographic modules 110 are maintained in a physically secured environment, such as a vault.
In this embodiment, each client system 220a–220m includes a CPU 223, a keyboard 224, a mouse 225, a mass storage device 231, main computer memory 227, video memory 228, a communication interface 232a, and an input/output device 226 coupled and interacting via a communication bus. The data and images to be displayed on the monitor 230 are transferred first from the video memory 228 to the video amplifier 229 and then to the monitor 230. The communication interface 232a communicates with the servers 222a–222m via a network link 233a. The network link connects the client system to a local network 234. The local network 234 communicates with the Internet 221.
In one embodiment, a customer, preferably licensed by the USPS and registered with an IBIP vendor (such as Stamps.com), sends a request for authorization to print a desired amount of VBI, such as postage. The server system verifies that the user's account holds sufficient funds to cover the requested amount of postage, and if so, grants the request. The server then sends authorization to the client system. The client system then sends image information for printing of a postal indicium for the granted amount to a printer so that the postal indicium is printed on an envelope or label.
When a client system sends a VBI print request to the Server, the request needs to be authenticated before the client system is allowed to print the VBI, and while the VBI is being printed. The client system sends a password (or passphrase) entered by a user to the Server for verification. If the password fails, a preferably asynchronous dynamic password verification method terminates the session and printing of the VBI is aborted. Also, the Server system communicates with a system located at a certification authority for verification and authentication purposes.
In one embodiment, the information processing components of the on-line postage system include a client system, a postage server system located in a highly secure facility, a USPS system and the Internet as the communication medium among those systems. The information processing equipment communicates over a secured communication line.
Preferably, the security and authenticity of the information communicated among the systems are accomplished on a software level through the built-in features of a Secured Socket Layer (SSL) Internet communication protocol. An encryption hardware module embedded in the server system is also used to secure information as it is processed by the secure system and to ensure authenticity and legitimacy of requests made and granted.
The on-line VBI system does not require any special purpose hardware for the client system. The client system is implemented in the form of software that can be executed on a user computer (client system) allowing the user computer to function as a virtual VBI meter. The software can only be executed for the purpose of printing the VBI indicia when the user computer is in communication with a server computer located, for example, at a VBI meter vendor's facility (server system). The server system is capable of communicating with one or more client systems simultaneously.
In one embodiment of the present invention, the cryptographic modules 110 are FIPS 140-1 certified hardware cards that include firmware to implement PSD functionality in a cryptographically secure way. The cryptographic modules are inserted into any of the servers in the Postal Server Infrastructure. The cryptographic modules are responsible for creating PSDs and manipulating PSD data to generate and verify digitally signed indicia. Since the PSD data is created and signed by a private key known only to the module, the PSD data may be stored externally to the cryptographic modules without compromising security.
The on-line VBI system is based on a client/server architecture. Generally, in a system based on client/server architecture the server system delivers information to the client system. That is, the client system requests the services of a generally larger computer. In one embodiment, the client is a local personal computer and the server is a more powerful group of computers that house the information. The connection from the client to the server is made via a Local Area Network, a phone line or a TCP/IP based WAN on the Internet. A primary reason to set up a client/server network is to allow many clients access to the same applications and files stored on the server system.
In one embodiment, Postage servers 109 include a string of servers connected to the Internet, for example, through a T1 line, protected by a firewall. The firewall permits a client system to communicate with a server system, only if the information packet transmitted by the client system complies with a security policy set by the server system. The firewall not only protects the system from unauthorized users on the Internet, it also separates the Public Network (PUBNET) from the Private Network (PRVNET). This ensures that packets from the Internet will not go to any location but the PUBNET. The string of servers form the different subsystems of the on-line postal system. The services provided by the different subsystems of the on-line postage system are designed to allow flexibility and expansion and reduce specific hardware dependency.
The Database subsystem is comprised of multiple databases.
The Online Store Database 412 contains commerce product information, working orders, billing information, password reset table, and other marketing related information. Website database 410 keeps track of user accesses to the vendor website. This database keeps track of user who access the vendor website, users who are downloading information and programs, and the links from which users access the vendor website. After storing these data on the Website Database 410, software tools are used to generate the following information:
Web Site Status
Web Site Reports
Form Results
Download Successes
Signup, Downloads, and Demographic Graphs
Web Server Statistics (Analog)
Web Server Statistics (Web Analyzer)
Offline database 409 manages the VBI (e.g., postal) data except meter information, postal transactions data, financial transactions data (e.g., credit card purchases, free postage issued, bill credits, and bill debits), customer marketing information, commerce product information, meter license information, meter resets, meter history, and meter movement information. Consolidation Server 413 acts as a repository for data, centralizing data for easy transportation outside the vault 400. The Consolidation Server hosts both file and database services, allowing both dumps of activity logs and reports as well as a consolidation point for all database data. The Offline Reporting Engine MineShare Server 415 performs extraction transformation from the holding database that received transaction data from the Consolidated Database (Commerce database 406, Membership database 408, and Postal Database 407). Also, the Offline Reporting Engine MineShare Server handles some administrative tasks. Transaction data in the holding database contains the transaction information about meter licensing information, meter reset information, postage purchase transactions, and credit card transactions. After performing extraction transformation, business logic data are stored on Offline Database 409. Transaction reports are generated using the data on the Offline Database. Transaction reports contain marketing and business information.
The Data Warehouse database 414 includes all customer information, financial transactions, and aggregated information for marketing queries (e.g., how many customers have purchased postage). In one embodiment, commerce Database 406 includes a Payment Database, an E-mail Database, and a Stamp Mart Database. The E-mail DBMS manages access to the contents of e-mail that were sent out to everyone by vendor servers. The Stamp Mart database handles order form processing. The E-commerce Server 404 provides e-commerce related services on a user/group permission basis. It provides commerce-related services such as payment processing, pricing plan support and billing as well as customer care functionality and LDAP membership personalization services. A Credit Card Service is invoked by the E-commerce Server 404 to authorize and capture funds from the customer's credit card account and to transfer them to the vendor's merchant bank. A Billing Service is used to provide bills through e-mail to customers based on selected billing plans An ACH service runs automatically at a configurable time. It retrieves all pending ACH requests and batches them to be sent to bank for postage purchases (i.e. money destined for the USPS), or Chase for fee payments which is destined for the vendor account.
The E-commerce DBMS 406 manages access to the vendor specific Payment, Credit Card, and Email Databases. A Membership DBMS manages access to the LDAP membership directory database 408 that hosts specific customer information and customer membership data. A Postal DBMS manages access to the Postal Database 407 where USPS specific data such as meter and licensing information are stored. A Postal Server 401 provides secure services to the Client, including client authentication, postage purchase, and indicia generation. The Postal Server requires cryptographic modules to perform all functions that involve client authentication, postage purchase, and indicia generation.
Postal Transaction Server 403 provides business logic for postal functions such as device authorization and postage purchase/register manipulation. The Postal Transaction Server requires the cryptographic modules to perform all functions. There are four Client Support Servers. Address Matching Server (AMS) 417 verifies the correct address specified by a user. When the user enters a delivery address or a return address using the Client Software, the user does not need the address matching database on the user's local machine to verify the accuracy of the address. The Client software connects to the vendor's server and uses the central address database obtained from the USPS to verify the accuracy of the address. If the address is incorrect, the client software provides the user with a prioritized list of addresses to match the correct address. These choices are ranked in a user definable order. This information is represented using a plain text format.
The Client Support Servers 417 provides the following services: a Pricing Plan service, an Auto Update service, and a Printer Config service. The Pricing Plan Service provides information on pricing plans and payment methods available to the user. It also provides what credit cards are supported and whether ACH is supported. This information is represented preferably using a plain text format. The Auto Update Service verifies whether the user is running the latest Client Software. If there is newer Client Software, the Auto Update Server downloads the new patches to the user computer. The Client Support Database has tables for the client software update information. This information is represented using a plain text format. Before the user tries to print postage, the user sends his or her printer driver information over the Internet in plain text. A Printer Config Service looks up the printer driver information in the Printer Driver Database to determine whether the printer driver is supported or not. When the user tries to configure the printer, the user prints a test envelope to test whether the postage printing is working properly or not. This testing envelope information is sent over the Internet in plain text and is stored in the Client Support Database.
MeterGen server 422 makes calls into the cryptographic module to create sufficient meters to ensure that the vendor can meet customer acquisition demands. SMTP Server 418 communicates with other SMTP servers, and it is used to forward e-mail to users. Gatekeeper Server works as a proxy server by handling the security and authentication validation for the smart card users to access customer and administration information that reside in the vault. The Proxy Server 423 uses the Netscape™ Enterprise SSL library to provide a secure connection to the vault 400. Audit File Server 419 acts as a repository for module transaction logs. The Audit File Server verifies the audit logs that are digitally signed. The audit logs are verified in real time as they are being created. Postal Server writes audit logs to a shared hard drive on the Audit File Server. After these logs are verified, the Audit File Server preferably moves them from the shared hard drive to a hard drive that is not shared by any of the vendor servers.
Provider Server provides reporting and external communication functionality including the following services. CMLS Service forwards license applications and it processes responses from CMLS. The CMLS Service uses cryptographic functions provided by the Stamps.com Crypt library to decrypt the user's SSN/Tax ID/Employee ID. CMRS Service reports meter movement and resetting to the USPS Computerized Meter Resetting infrastructure. ACH Service is responsible for submitting ACH postage purchase requests to the USPS lockbox account at the bank. The CMLS Service uses cryptographic functions to decrypt the user's ACH account number. After decrypting ACH account information, the ACH is encrypted using the vendor's script library. Then, the encrypted ACH file is e-mailed to the Commerce Group by the SMTP server. When the Commerce Group receives this encrypted e-mail, the vendor's Decrypt utility application is used to decrypt the ACH e-mail. After verifying the ACH information, the Commerce Group sends the ACH information through an encrypted device first and then uses a modem to upload the ACH information to a proper bank. The Certificate Authority issues certificates for all IBIP meters. The certificates are basically used to provide authentication for indicia produced by their respective meters.
The following are the steps describing the certificate authorization process:
The Postal Server subsystem 401 manages client and remote administration access to server functionality, authenticates clients and allows clients to establish a secure connection to the on-line postage system. The Postal Server subsystem also manages access to USPS specific data such as PSD information and a user's license information. The Postal Server subsystem queries the Postal portion of the Database subsystem for the necessary information to complete the task. The query travels through the firewall to the Postal portion of the Database subsystem. The Postal Server subsystem is the subsystem in the Public Network that has access to the Database subsystem.
In one embodiment of the present invention, Postal Server 401 is a standalone server process that provides secure connections to both the clients and the server administration utilities, providing both client authentication and connection management functionality to the system. Postal Server 401 also houses postal-specific services that require high levels of security, such as purchasing postage or printing indicia. Postal Server 401 is comprised of at least one server, and the number of servers increases when more clients need to be authenticated, are purchasing postage or are printing postage indicia.
The growth in the number of servers of the Postal Server will not impact the performance of the system since the system design allows for scalability. The Postal Server is designed in such a way that all of the business logic is processed in the servers and not in the database. By locating the transaction processing in the servers, increases in the number of transactions can be easily handled by adding additional servers. Also, since each transaction is stateless (the application does not remember the specific hardware device the last transaction utilized), multiple machines can be added to each subsystem in order to handle increased loads. In one embodiment, load balancing hardware and software techniques are used to distribute traffic among the multiple servers.
The client software includes GUI and wizards for software installation, user registration, printing of VBI, account information access, payment, and the like. An installation wizard helps the user to install the client software.
The install routine supports the installation of third party applications, including MS Word™, and Word Perfect™. The plugins for these applications are preferably included in the download file. The install wizard preferably prompts the users which of these, if any, they would like to install. An exemplary interface is shown in
The installation routine also supports OEM branding. Specifically, the install wizard is such that the elements described in OEM branding are stored in a resource file, so that the install routine itself preferably does not need to be changed —rather the resource file is changed. The installation routine or the Getting Started wizard also supports the OEM branding requirements. Specifically, a cookie is read and its contents are uploaded to the server.
When the user first attempts to log in, and a connection cannot be established, an error message appears based upon which connection method the user has chosen. In one embodiment, if the user chose to connect by a local area network, the error message shown in
Before a user can begin to print postage, a significant number of tasks are preferably first completed. These steps are combined into a wizard that launches after the customer installs the client software. The preferred goal is to provide a single, streamlined interface that removes any interruptions once the user completes the wizard. The overall flow of the user experience in getting started with the software is shown in
Typically, the volume of screens that make up the Getting Started wizard are significant. In order to prevent the user form being overwhelmed with the process, preferably the system constantly gives the customer a sense as to where they are in the process. To satisfy this goal, the software utilizes a “Follow the Yellow Brick Road” interface, which constantly updates the users on their progress in the wizard. The left side graphic area is used to indicate which of these stages that the user is currently in. In one embodiment, the stage is indicated using text, with the current stage being highlighted. Using text rather than graphics helps minimize the download size.
Each screen of the Getting Started wizard preferably has a Help button which links to a portion of the Help file that pertains to that screen. Whenever a combo box is used in this wizard, by default no item is selected, and the prompt “select one” preferably appears to the user. Preferably, every screen in the Getting Started wizard has a Cancel button on it. The functionality of these buttons is consistent throughout the wizard. The various functions that are executed when a user selects the Cancel button are described below.
The Verification Prompt is a standard prompt that verifies the user indeed would like to cancel the wizard. This is accomplished through a standard dialog box as shown in
The Welcome portion of the Getting Started wizard provides two functions. First, it welcomes the user to the process and gives the user an idea of what is involved in the process. Second, it determines whether or not a user should complete the Getting started wizard at this time. There are two reasons why a user is kept from completing the Getting Started wizard, as shown in
The Welcome Screen #1720, in
If there is no slot available for the user, the Welcome Screen #2725, in
At this point in the Getting Started wizard, the client preferably downloads information from the server for use throughout the remainder of the wizard. Specifically, the information that is downloaded includes Service Plan Information such as Plan Name, Plan ID, Text file describing all of the plans, Contract for the plan (text file), Min purchase amount, Max purchase amount, Purchase Upfront (y/n), URL link to full description (common web link for all plans), Preferred Service Plan; and Payment Information including Payment types accepted, and Preferred payment type.
The Sign up for Service component of the Getting Started wizard extracts all of the information required to sign up the user for service with the provider. When this portion of the Getting Started wizard has begun, the “Follow the Yellow Brick Road” text is changed to “Register with Provider” (e.g., Stamps.com). The logical flow of the Sign up for Service component is shown in
Service Screen #1 (block 730 of
Service Screen #2 (block 731 of
After service screen #2 is completed, in block 736, an AMS check on the addresses is run. Also, a check is made as to determine whether the zip code that the user provides is currently the one that is supported, as shown in block 737. If it is determined that the physical zip code is one that is supported, the user continues with service screen #3 in block 739. If the zip code is NOT one that is supported, Service Screen #2a appears to notify the user that the user is unable to sign up at this time, as depicted in block 738. An exemplary interface for Service Screen #2a is shown in
In block 739, the user enters “user name” and “password.” An exemplary interface for Service Screen #3 is shown in
What is your mother's maiden name?
What is your favorite pets name?
What is your favorite vacation spot?
What is your place of birth?
After selecting a question, the user can enter a response into an edit field. The “Next>” button is not enabled until after the information is filled in.
In block 744, in Service Screen #5, the users specify how they will use the account. Preferably, none of the radio buttons are selected on open. An exemplary interface for Service Screen #5 is shown in
Service Screen #6, in block 745, provides several types of information all related to the user's postage usage habits, for use both by the provider and the USPS. In this screen, as depicted in
Service Screen #7 (block 746) allows the user to select a service plan from the provider. The following information is preferably downloaded at the beginning of the registration wizard: Service Plan names, a URL to a page on the provider's web site that describes the service plans in detail, and text files describing each service plan.
As illustrated in block 747, Service Screen #8 displays the service contract for the service plan that the user selected on the previous screen. This contract is a text file, which is downloaded at the beginning of the registration wizard. As shown in
Service Screen #9, depicted in
If a credit card is selected as the method of payment in decision block 750, the fields shown in the screen of
If ACH method of payment is selected in decision block 750, the fields shown in screen of
As described above, the Registration Wizard is capable of gathering all of the information that is required by the USPS for a Meter License Application. The information that is extracted in this wizard is used to generate a USPS 3601A form.
In block 1011, the user determines wether they are a business or and end user. In License Screen #2 (block 1012), the user specifies which identification number they wish to use. None of the radio buttons are selected on open, as shown in
License Screen #3a (block 101a) only appears to business users. As illustrated in
An exemplary interface for License Screen #8 (block 1019) is illustrated in
In blocks 1021 and 1023, the information entered by the user is checked for any potential errors and the errors are reported to the user. Once the information has been submitted, the server is able to communicate if any of three errors occur with the information that the user has provided. These errors include a non unique user name, bad ACH information, and rejected credit card payment. If any of these errors occur, a wizard screen appears that dynamically displays the error that is returned from the server. When the user selects “Next>”, the appropriate wizard screen shown in
In block 1028, if the user submits a non unique user name, the dialog box of
In block 1027, if a reject on a credit card process is received, the dialog box shown in
The Print Setup portion of the Getting Started wizard includes several wizard components, which can be broken out and used individually in the client software. These wizards are brought together into the Print Setup portion of the Getting Started wizard to provide all of the printing oriented checks and tasks that a user should complete before starting with the software. These include: Print Verification, Print QA envelope, and Determine top, center, or bottom envelope feed (if necessary). When this portion of the Getting Started wizard has begun, the Follow the Yellow Brick Road text is changed to “Test Printer”. An exemplary flow of the Print Setup component is shown in
In block 1101, Print Setup Screen #1 is used to select default printer. This screen, shown in
In block 1102, Print Setup Screen #2, shown in
In block 1103, it is determined wether the default printer information is in the printer database. If the printer information is not in the database, a printer troubleshooting routine is performed, as shown in block 1104. If the printer information is in the database, printer Screen #3, depicted in
Similar to Printer Screen #3, Printer Screen #4 serves the function of educating the user about QA envelopes, notifying the user that postage is about to be printed, and making the user aware that an envelope needs to be loaded into the feeder. A graphic of an envelope being placed into a printer is used to help re-enforce the action to the user. This section of the wizard, illustrated in
Next, in block 1115, Printer Screen #6, shown in
In the event that the user's printer is not in the printer database, the Print Configuration wizard is initiated. An exemplary flow for the Print Configuration wizard is shown in
In block 1123, if the user selects “none of the above match what I see” on screen # 7, Printer Screen #8, shown in
If the user selects “neither of these solutions work” on screen # 8, print envelope is disabled and Printer Screen #9, shown in
A re-registration process allows users to re-register across systems. An exemplary flow for the re-registration process is shown in
In block 1208, if the user is currently registered on another system, and is not currently logged in, then the dialog box of
The client print engine prints a Facing Identification Mark (FIM) in accordance with USPS specifications. Preferably, the FIM is printed within ⅛″ from the top of the envelope, and no more than 2⅛″ from the right hand edge, as shown in
A Print Postage dialog box is the main interface from which a user defines the postage to be printed. An exemplary interface for this dialog box is illustrated in
“Do not print the Return Address” is unchecked by default. Mail Type toggle buttons enable the user to select whether the mail to be sent is a letter, flat, box or oversized box. This information is used to determine what labels and/or envelopes are available to the user, as well as what the postage rate will be. The letter toggle is selected by default. Mail type description field provides a brief description of the mail type that is currently selected with the Mail Type toggle buttons. Print On list box allows user to select from all Envelopes and Labels. The items displayed in this list box are determined by the type of mail that was selected in the previous list box. If a letter is selected, only envelopes and labels approved by the USPS are available. If a flat or box is selected, only labels approved by the USPS are available. No values are selected by default.
The Enter Weight fields allow users to type in values or select them using spinner controls. If the user has set up a digital scale, clicking on the scale button automatically pulls the value from the scale and display the value in these fields. After the initial use, the fields remember the last value. The “Select a Service” control is a list box, which shows the various services that are available and also displays the cost of each type of service for the mail piece that has been defined. The prices update as the user inputs information into the Enter Weight fields. If the user is typing a value, the display immediately updates as the user types. If zone based postage is used, and if multiple users are selected, the range of costs is displayed. Once a user has selected a mail service, a graphic of a check mark should appear immediately to the left of the item as shown. None of the items are selected by default. Available Postage display displays the available postage amount. Total Mailing Cost displays the cost of the total mailing when multiple recipients are selected.
Preview Window is dynamic, depending upon the selection from the “Print Onto” list Box. Print button decides whether to print a sample or real postage. This single print button advances the user to the Print Prompt screen. Options button launches the appropriate options dialog box, depending upon the selection type into the “Print Onto” list Box. If an envelope is selected, the Envelope Options dialog box will be launched. If a label is selected, the Label Options dialog box appears. In the event that multiple recipients and/or zone based postage rates are selected, portions of the Print Postage dialog changes slightly in their functionality, as shown in
In the exemplary screen of
After the user has selected “Print” from the Print Postage dialog box, the Print Prompt dialog box of
Envelope Options dialog box, depicted in
A Print Configuration wizard helps the user undergo three major processes: determining top, center, or bottom offset (if needed), providing print verification, and Printing a QA envelope. The print engine preferably incorporates the provider's logo into the Indicium. Rather than integrating a single static logo graphic, the print engine accommodates a scalable graphic. The reasoning behind this is as follows. In order to conform to the FIM placement standards which requires that the FIM consistently be printed 2″+/−⅛″ from the right hand edge of the envelope, the space available between the FIM and the human readable portion of the Indicium will change depending upon the right hand margin of the printer used, as shown in
A means by which users can customize their mail piece with a graphic file of their choosing is provided by the system. The system provides users with the ability to incorporate a graphic into the return address space. Specifically, the client software allows the user to incorporate a standard graphic into the area to the left of the return address, as shown in
A personal address book may be used by the user to print addresses on the mail pieces. The client's native address book is functional even when the user is offline. Specifically, the user is able to add addresses, edit addresses, import addresses, and remove addresses without requiring the user to login online. In order to ensure that every address that is entered, modified, or imported undergoes an AMS check, addresses undergo an AMS check at the time the postage is printed to an address (see Printing description). In addition to the native address book, the system provides support for a variety of external address books. Examples of some of the address books supported include Microsoft Outlook™, Schedule +™, Symantec ACT!™, Lotus Organizer™, Lotus Notes™, GoldMine™, Microsoft Windows Address book, and the like.
The client's support for the external address books is such that the user can read data from any of these address books from within the standard client address book interface. The data is able to be read in real time. In addition, the user is able to make changes to addresses and write these changes back to the external address book. In order to allow the user to select which address book to use (either the native or any of the third party address books), several controls are added to the client Address Book interface, as shown in
In one embodiment, the code that provides support for each Address Book is created as a plugin, allowing users to only download the Address Books that they want support for. The install routine provides a means by which users can select which Address Books are downloaded, and automate the installation of the plugin. Support is provided for importing other address data. For example, the system provides import filters for the following: Daytimers, The Learning Channel products, MYOB, and the like. Also, Address Books support standard group capabilities. The system is capable of providing support for foreign addresses, and is able to pass AMS matching checks. Furthermore, the system provides the capability to print addresses that have been returned by AMS in a format that includes both upper and lower cased alpha characters. In other words, the address that is printed should preferably have the same formatting of upper and lower case characters as the user originally entered. When multiple recipients are selected from the Address Book, the dialog box shown in
The Address Book within the client provides a utility to import text files that have been exported from other Address Books. Typically, when a user imports a text file, the user need to “map” the fields from the original file into the fields of the destination file. This is very cumbersome for the user, and often prevents users from successfully importing files. To avoid forcing the user to map fields, the system provides import “filters,” that are unique filters written for each Address Book. Since each filter is unique to an individual source file, the filter knows the data field structure of the source file (and it knows the data structure of the destination system Address Book). With this knowledge, the import filter is able to import files from other Address Books without requiring any data structure input from the customer. To meet the brandability needs, the system accommodates an easy addition of import filters.
The system also provides a flexible messaging system, which includes a communication channel between the provider and its users through the client software. Messages may be created by various departments within the provider's organization and are pushed by the server to one of several types of messaging dialog boxes. Some examples of messaging dialog boxes are described in detail below.
In the event that a message is awaiting a user at the time of login, the client displays one of several types of messaging dialog boxes. The specifics of the dialog box that is displayed is dependent upon the “Message Type” that awaits the user. Generally speaking, the types of messages available fall into one of two categories: generic or template. The generic message type includes marketing messages, customer support messages, etc, where the intent of the messaging is simply to communicate with the user and perhaps provide a URL link. The template message types include payment resubmission, email resubmission, and plan change notifications, where in addition to sending a message to the user the messaging dialog box allows the user to take action on the message. In one embodiment, template dialogs are hard coded into the client system to accommodate the special actions that are taken. Marketing Messages allow the provider to communicate with the user base. For example, the Marketing Message dialog box allows the provider to promote an item that is sold on their web site, and provide a URL link to that item. An example of the specific components of a marketing message are shown in
A Customer Service Message is preferably the same in functionality as the Marketing Message dialog box, except that the graphic icon is different. The different graphic communicates to the user that this message is a different type of message than a Marketing Message. The Customer Service dialog is designed to communicate customer support issues, as shown in
Email Resubmission Message is a template type message, whose purpose is to notify a user when the system does not have a valid email address for him/her, and enable the user to provide this information. Exemplary elements of this type of message dialog are shown in
A Change in Service Plans Message (also a template type message), indicates when new plans are available to a user, or if the user's current plan is going to be grandfathered. This, message dialog basically indicates the change to the user and links the user to the change plans dialog and to more information about change plans, if desired. Exemplary elements of this dialog are shown in
The client software checks for available updates at the beginning of the installation routine, before any files have been installed, and at each login. At each of these times, the client checks for an available update. If an update is available, a dialog box appears. This dialog box provides a message which communicates the details of the available update, and provides a URL link to a website where the update file can be downloaded. The update file may be classified as either mandatory or optional. If the update is mandatory, the update is installed by the user. If the update is optional, the user can choose whether or not to install the file. There are no restrictions regarding how many update messages can be sent out, and the update message is not tied into the standard messaging described earlier in this document. The auto update feature is able to copy individual files so that a version can be updated without requiring a complete update.
In one embodiment, the system includes OEM branding capabilities. The system allows for the customization of the installation script in several ways, including the option of running a silent install, defining a default installation directory, and defining a default installation group. The default behavior of the installation routine is to run as an application that is visible to the user, and requires user input on multiple screens during the installation process. The system provides the option of a “silent install”, which installs the program files to the user's system without being visible, and without requiring user intervention. The installer is told where to install the product's files. While the user may choose to install the product in any directory location they want, the installer offers them a choice consistent with the product identity. Every product is placed in a sub-directory within the master directory. The OEM partner has the ability to provide a name for both the master directory and sub-directory into which the product is installed. Program group, or “folder”, is the location in which the installer displays the product if the user does not manually choose a different one. The system allows the OEM partner to customize the Default Program Group name. The OEM partner does not have the ability, however, to change the name or associated icons of the items within the group.
The system provides the ability to co-brand the software by providing prominent partner logo placement on the main screen within the software. In one embodiment, the logo placement is in the upper left hand corner of the main screen, below the provider's logo. An example of the layout of the provider's logo and the partner logo are shown in
The system incorporates client server technology which enables the provider to provide OEM partners with data that tracks the postage usage of customers who are using that OEM's version of the client software. The client software embeds a unique OEM identifier within each OEM version of the client software. Once a user has registered with the provider, that user is thereafter associated with the OEM that is identified within their client software. This association, as well as all tracking activities, are transparent to the user and require no additional intervention by the user. In the event that a user gets the client software through an Affiliate Partner's web site, the account number that a user is assigned will embed in it information that identifies the source Affiliate Partner. Therefore, this account number is uploaded to the Postal Server, which occurs at the end of the Registration wizard. In the case of an affiliate partnership, the tracking number is extracted from a cookie that has been downloaded onto the users computer. The details concerning formatting and requirements of the cookies are covered in a separate document.
A change of Address wizard is designed to help a user through the process of changing either a physical or mailing address, and the meter license ramifications that may result. An exemplary process flow of the Change of Address wizard is shown in
Change of Address Screen #4, shown in
Change of Address Screen #6 notifies the user that their meter license has been withdrawn. In addition, it prompts the user for a new user name and password. The controls used for this screen, shown in
In one embodiment, the system includes a dialog box, which can change payment methods and be accessed from the Account screen. An exemplary interface for this screen is illustrated in
In one embodiment, the system allows the user to change the service plan in which the customer is participating. This is accomplished through several screens which have many of the attributes of the Service Plan screens within the Getting Started wizard. This functionality is accessed when the user selects “Change Service Plan” from the Accounts screen. Once the user selects “Change Service Plan” from the Accounts screen, the Change Plan dialog box (shown in
If the user selects the “I Accept” radio button on the Change Plan Contract dialog box, and then selects “Ok”, the dialog box shown in
The initial login screen provides the interface whereby the users typically inputs their passwords. If a user enters incorrect information, a message such as the one shown in
Once the user gets the temporary password, the user uses it to log in as normal. Once the server verifies that the password is valid, an additional check is made to determine whether the password that is provided is a temporary or long term password. If the password is a temporary password, then the client software launches the change password dialog box, and does not allow the box to be closed until the user enters the old password and a new one. A Message Log lists a history of the messages that a user has received from the provider. This log is accessible from the “Accounts” screen, and have the standard layout and capabilities of the other logs within the client.
A Postal Meter License wizard is also provided. This option within the Options screen launches the new Registration wizard (which is a subset of the Getting Started wizard). The specific screens that make up the Registration wizard are shown in the process flow of
A Setup Digital Scales option is also provided. This new option launches the Setup Digital Scale dialog box shown in
Every “View History” dialog box adds print functionality, so that historical reports can be printed. Specifically, the View Postage Purchase History, View Postage Printed History, and View Messages History all add a Print button at the bottom of the screen. The number of events that are printed is defined by the purge control, which also controls the number of items that are displayed.
It will be recognized by those skilled in the art that various modifications may be made to the illustrated and other embodiments of the invention described above, without departing from the broad inventive scope thereof. It will be understood therefore that the invention is not limited to the particular embodiments or arrangements disclosed, but is rather intended to cover any changes, adaptations or modifications which are within the scope and spirit of the invention as defined by the appended claims.
This patent application claims the benefit of the filing date of U.S. Provisional Patent Application Ser. Nos. 60/136,924, filed Jun. 1, 1999 and entitled “INTERNET POSTAGE SYSTEM”, 60/139,153, filed Jun. 14, 1999, and entitled “CLIENT SOFTWARE AND USER INTERFACE FOR INTERNET POSTAGE SYSTEM”, AND 60/160,491, Oct. 20, 1999, and entitled “SECURE AND RECOVERABLE DATABASE FOR ON-LINE POSTAGE SYSTEM”, the entire contents of which are hereby expressly incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4447890 | Duwel et al. | May 1984 | A |
| 4725718 | Sansone et al. | Feb 1988 | A |
| 4743747 | Fougere et al. | May 1988 | A |
| 4757537 | Edelmann et al. | Jul 1988 | A |
| 4775246 | Edelmann et al. | Oct 1988 | A |
| 4802218 | Wright et al. | Jan 1989 | A |
| 4812994 | Taylor et al. | Mar 1989 | A |
| 4831555 | Sansone et al. | May 1989 | A |
| 4837702 | Obrea | Jun 1989 | A |
| 4853865 | Sansone et al. | Aug 1989 | A |
| 4900903 | Wright et al. | Feb 1990 | A |
| 4900904 | Wright et al. | Feb 1990 | A |
| 4908770 | Breault et al. | Mar 1990 | A |
| 4933849 | Connell et al. | Jun 1990 | A |
| 4935961 | Gargiulo et al. | Jun 1990 | A |
| 4949381 | Pastor | Aug 1990 | A |
| 4980542 | Jackson et al. | Dec 1990 | A |
| 5048085 | Abraham et al. | Sep 1991 | A |
| 5058008 | Schumacher | Oct 1991 | A |
| 5075865 | Kawamura et al. | Dec 1991 | A |
| 5111030 | Brasington et al. | May 1992 | A |
| 5142577 | Pastor | Aug 1992 | A |
| 5181245 | Jones | Jan 1993 | A |
| 5241483 | Porret et al. | Aug 1993 | A |
| 5265221 | Miller | Nov 1993 | A |
| 5319562 | Whitehouse | Jun 1994 | A |
| 5325519 | Long et al. | Jun 1994 | A |
| 5341505 | Whitehouse | Aug 1994 | A |
| 5377268 | Hunter | Dec 1994 | A |
| 5384886 | Rourke | Jan 1995 | A |
| 5390251 | Pastor et al. | Feb 1995 | A |
| 5448641 | Pintsov et al. | Sep 1995 | A |
| 5454038 | Cordery et al. | Sep 1995 | A |
| 5471925 | Heinrich et al. | Dec 1995 | A |
| 5561795 | Sarkar | Oct 1996 | A |
| 5570465 | Tsakanikas | Oct 1996 | A |
| 5598477 | Berson | Jan 1997 | A |
| 5600562 | Guenther | Feb 1997 | A |
| 5621797 | Rosen | Apr 1997 | A |
| 5655023 | Cordery et al. | Aug 1997 | A |
| 5659616 | Sudia | Aug 1997 | A |
| 5666421 | Pastor et al. | Sep 1997 | A |
| 5668897 | Stolfo | Sep 1997 | A |
| 5671146 | Windel et al. | Sep 1997 | A |
| 5680629 | Slayden et al. | Oct 1997 | A |
| 5684951 | Goldman et al. | Nov 1997 | A |
| 5729734 | Parker et al. | Mar 1998 | A |
| 5742683 | Lee et al. | Apr 1998 | A |
| 5768132 | Cordery et al. | Jun 1998 | A |
| 5781438 | Lee et al. | Jul 1998 | A |
| 5781634 | Cordery et al. | Jul 1998 | A |
| 5793867 | Cordery et al. | Aug 1998 | A |
| 5796841 | Cordery et al. | Aug 1998 | A |
| 5801944 | Kara | Sep 1998 | A |
| 5812990 | Ryan, Jr. et al. | Sep 1998 | A |
| 5812991 | Kara | Sep 1998 | A |
| 5819240 | Kara | Oct 1998 | A |
| 5822739 | Kara | Oct 1998 | A |
| 5825893 | Kara | Oct 1998 | A |
| 5867578 | Brickell et al. | Feb 1999 | A |
| 5871288 | Ryan et al. | Feb 1999 | A |
| 5903905 | Andersen et al. | May 1999 | A |
| 5917924 | Herbert | Jun 1999 | A |
| 5918234 | Shah et al. | Jun 1999 | A |
| 5930796 | Pierce et al. | Jul 1999 | A |
| 5940383 | Willkie | Aug 1999 | A |
| 5953427 | Cordery et al. | Sep 1999 | A |
| 5956404 | Schneier et al. | Sep 1999 | A |
| 5978484 | Apperson et al. | Nov 1999 | A |
| 5983227 | Nazem et al. | Nov 1999 | A |
| 5987441 | Lee et al. | Nov 1999 | A |
| 5988897 | Pierce et al. | Nov 1999 | A |
| 6005945 | Whitehouse | Dec 1999 | A |
| 6009417 | Brookner et al. | Dec 1999 | A |
| 6010156 | Block | Jan 2000 | A |
| 6026385 | Harvey et al. | Feb 2000 | A |
| 6049671 | Slivka et al. | Apr 2000 | A |
| 6058384 | Pierce et al. | May 2000 | A |
| 6061671 | Baker et al. | May 2000 | A |
| 6064993 | Ryan, Jr. | May 2000 | A |
| 6065117 | White | May 2000 | A |
| 6070150 | Remington et al. | May 2000 | A |
| 6081810 | Rosenzweig et al. | Jun 2000 | A |
| 6098058 | Gravell et al. | Aug 2000 | A |
| 6105063 | Hayes, Jr. | Aug 2000 | A |
| 6134582 | Kennedy | Oct 2000 | A |
| 6151591 | Pierce et al. | Nov 2000 | A |
| 6161139 | Win et al. | Dec 2000 | A |
| 6164528 | Hills et al. | Dec 2000 | A |
| 6223166 | Win et al. | Dec 2000 | B1 |
| 6226752 | Gupta et al. | May 2001 | B1 |
| 6233565 | Lewis et al. | May 2001 | B1 |
| 6233568 | Kara | May 2001 | B1 |
| 6249777 | Kara et al. | Jun 2001 | B1 |
| 6275824 | O'Flaherty et al. | Aug 2001 | B1 |
| 6286098 | Wenig et al. | Sep 2001 | B1 |
| 6307961 | Balonon-Rosen et al. | Oct 2001 | B1 |
| 6324523 | Killeen, Jr. et al. | Nov 2001 | B1 |
| 6341274 | Leon | Jan 2002 | B1 |
| 6353926 | Parthesarathy et al. | Mar 2002 | B1 |
| 6367013 | Bisbee et al. | Apr 2002 | B1 |
| 6381589 | Leon | Apr 2002 | B1 |
| 6385654 | Tanaka | May 2002 | B1 |
| 6385731 | Ananda | May 2002 | B1 |
| 6408286 | Heiden | Jun 2002 | B1 |
| 6415983 | Ulvr et al. | Jul 2002 | B1 |
| 6424954 | Leon | Jul 2002 | B1 |
| 6427021 | Fischer et al. | Jul 2002 | B1 |
| 6466921 | Cordery et al. | Oct 2002 | B1 |
| 6473743 | Ryan, Jr. | Oct 2002 | B1 |
| 6546377 | Gravell et al. | Apr 2003 | B1 |
| 6567794 | Cordery et al. | May 2003 | B1 |
| 6587880 | Saigo et al. | Jul 2003 | B1 |
| 6636983 | Levi | Oct 2003 | B1 |
| 6853989 | Allport et al. | Feb 2005 | B1 |
| 20010034716 | Goodwin | Oct 2001 | A1 |
| 20010037320 | Allport et al. | Nov 2001 | A1 |
| 20010055388 | Kaliski, Jr. | Dec 2001 | A1 |
| 20020023057 | Goodwin et al. | Feb 2002 | A1 |
| 20020046193 | Bator et al. | Apr 2002 | A1 |
| 20020095383 | Mengin et al. | Jul 2002 | A1 |
| 20030078893 | Shah et al. | Apr 2003 | A1 |
| 20030130954 | Carr et al. | Jul 2003 | A1 |
| 20050114712 | Devine et al. | May 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 360 225 | Mar 1990 | EP |
| 0 576 113 | Dec 1993 | EP |
| 0 604 146 | Jun 1994 | EP |
| 0 604 148 | Jun 1994 | EP |
| 0 647 925 | Apr 1995 | EP |
| 0 604 146 | Nov 1997 | EP |
| 0 840 258 | May 1998 | EP |
| 0 854 448 | Jul 1998 | EP |
| 0 892 367 | Jan 1999 | EP |
| 0 927 958 | Jul 1999 | EP |
| 0 927 963 | Jul 1999 | EP |
| 0 948 158 | Oct 1999 | EP |
| 2318486 | Nov 1994 | GB |
| WO 9427258 | Nov 1994 | WO |
| WO 9813790 | Apr 1998 | WO |
| WO9857302 | Dec 1998 | WO |
| WO 9857460 | Dec 1998 | WO |
| WO 9918514 | Apr 1999 | WO |
| WO 0019382 | Apr 2000 | WO |
| WO 0070503 | Nov 2000 | WO |
| WO 0150227 | Jul 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 60136924 | Jun 1999 | US | |
| 60139153 | Jun 1999 | US | |
| 60160491 | Oct 1999 | US |
