US 7,739,334 B1Grant
System and method for automatically forwarding email and email events via a computer network to a server computer
Issue Date:2010-06-15
•24 Claims
•9 Drawing Sheets
Abstract
The system and method enables the automatic routing of email and information corresponding to email to a database. The system and method also enables the filtering of email, determination of a protocol based on the filtering, and the transfer of the email according to the determined protocol.
Metadata
Assignee
- Visto Corporation
Inventors
- Mason Ng
- Daniel J. Mendez
- Sean Michael Quinlan
Application Information
Application Number:US 09/528,363
Filing Date:2000-03-17
Priority Date:2000-03-17
Art Unit:2452
Classifications
IPC:
G06F15/16
Patent Drawings (9 sheets)
Description
Background of the Invention
[0001] 1. Field of the Invention
[0002] This invention relates generally to computer networks, and more particularly relates to automatic data forwarding via a computer network to a server computer.
[0003] 2. Description of the Background Art
[0004] Data accessibility and consistency are significant concerns of computer users. For example, when a user maintains multiple computer sites, e.g., a work site and a home site, a user risks having redundant versions of a document or an email. If one of the redundant copies is modified, then the copies become effectively inconsistent. If the user fails to notice any inconsistency, interparty miscommunication or data loss may result. The user must then spend substantial time attempting to reconcile the inconsistent versions and addressing any miscommunications.
[0005] Data inconsistency is often caused when the redundant copies of the document or email are maintained on different sites, and when one or more of the redundant copies is inaccessible. For example, if one of versions is maintained on a computer site that is protected by a network security system such as a conventional firewall, e.g., the work computer site, the security system may prevent the user from accessing the copy. Without access to all computer sites, the user is unable to confirm that the version on an accessible site is the most recent draft.
[0006] The problems of data inconsistency and inaccessibility arise in the area of electronic mail (email). For example, a user might maintain email databases at a work computer site and at a home computer site. Based on the security systems implemented, a traveling user currently working from a remote terminal may not have access rights to the work computer site or the necessary dedicated application programs to pass the intranet security. Thus, the user may not be able to review the email maintained at the work computer site and thus cannot read or respond to work emails until returning to work. Still further, when maintaining several accessible sites, the traveling user is burdened to maintain a record of all procedures and passwords to overcome the security system of each site.
[0007] These problems are further exacerbated when using email programs from different vendors and which implement different protocols. For example, the Netscape Navigator™ e-mail client and the Outlook Express™ email client each manage email across computer networks. However, each email client uses different formats, stores emails in different files and implements different protocols. Thus, the emails are not readily interchangeable.
[0008] Therefore, a system and method are needed for providing users with email consistency and accessibility across a computer network.
Summary
[0009] A network system includes a server computer system coupled via a computer network to a client computer system, to an email computer system, and to a remote computer system. The server computer system downloads an email forwarding engine to the client computer system for enabling the email forwarding functionality on the client computer system. On the client computer system, the email forwarding engine examines start criteria, determines whether the start criteria have been met, obtains new email and/or email events from an email database, and forwards the new email and/or email events to the server computer system. The server computer system maintains them in a database. The email forwarding engine includes a filter for examining the email and/or email events against filter control data to determine the data to transfer and the desired transfer protocols. The server computer system stores an independently modifiable copy of user preferences, e.g., start criteria, stored on the client computer system to enable remote modification of the user preferences. In accordance with a configuration-check schedule, the client computer system determines whether any changes to the independently modifiable copy of the user preferences has been made, and if so modifies its copy of the user preferences.
[0010] A first method embodiment comprises examining start criteria; determining whether the start criteria have been met; obtaining new email events from an email database after the start criteria have been met; and forwarding information corresponding to the new email events via a computer network to a database.
[0011] A second method embodiment comprises establishing a communications channel with a client computer system; receiving information corresponding to new email events from the client computer system; and storing the information corresponding to the new email events in a database.
[0012] A third method embodiment comprises obtaining filter control data; examining email data against the filter control data; determining at least one transfer protocol for the email data based on the examination; and forwarding the email data according to the at least one transfer protocol via a computer network to a database.
[0013] A fourth method embodiment comprises obtaining filter control data; examining email data against the filter control data; determining based on the examination the email data that should not be forwarded; generating receipt data identifying the email data that should not be forwarded; and forwarding the receipt data via a computer network to a database.
[0014] A fifth method embodiment comprises storing user preferences on a client computer system; storing an independently modifiable copy of the user preferences on a server computer system coupled via a computer network to the client computer system; examining, by the client computer system, a configuration-check schedule; determining, by the client computer system, whether a configuration check has been scheduled; establishing, by the client computer system if a configuration check has been scheduled, a communications channel with the server computer system; determining whether any changes to the independently modifiable copy of the user preferences stored on the server computer system have been made; and modifying, if any changes have been made to the independently modifiable copy, the user preferences stored on the client computer system according to the changes made.
[0015] A sixth method embodiment comprises storing on a server computer system an independently modifiable copy of user preferences stored on a client computer system, the server computer system coupled via a computer network to the client computer system; enabling modification of the independently modifiable copy of the user preferences on the server computer system; establishing a communications channel with the client computer system; and providing any changes made since a last configuration check to the client computer system.
[0016] A seventh method embodiment comprises providing website information offering email forwarding functionality to client computer systems; enabling the client computer systems to request the email forwarding functionality to be downloaded; receiving a request for the email forwarding functionality from a requesting client computer system; and downloading an email forwarding engine to the requesting client computer system for enabling the email forwarding functionality on the requesting client computer system.
[0017] A first system embodiment comprises a client configuration engine for determining whether start criteria have been met; a retrieval engine, coupled to the client configuration engine, for retrieving email events from an email database; and a data transmitter, coupled to the retrieval engine, for forwarding information corresponding to the new email events via a computer network to a database.
[0018] A second system embodiment comprises a server database manager for establishing a communications channel with a client computer system, for receiving information corresponding to new email events from the client computer system, and for storing the information corresponding to the new email events in a database.
[0019] A third system embodiment comprises a filter for examining email data against filter control data, and for determining at least one transfer protocol for the email data based on the examination; and a data transmitter, coupled to the filter, for forwarding the email data according to the at least one transfer protocol via a computer network to a database.
[0020] A fourth system embodiment comprises a filter for examining email data against filter control data, and determining based on the examination the email data that should not be forwarded; a receipt generator, coupled to the filter, for generating receipt data identifying the email data that should not be forwarded; and a data transmitter, coupled to the filter, for forwarding the receipt data via a computer network to a database.
[0021] A fifth system embodiment comprises a client configuration engine for storing user preferences on a client computer system, for storing an independently modifiable copy of the user preferences on a server computer system that is coupled via a computer network to the client computer system, for examining a configuration-check schedule to determine whether a configuration check has been scheduled, for determining whether any changes to the independently modifiable copy have been made, and for modifying the user preferences stored on a client computer system according to the changes made to the independently modifiable copy; and a communications engine, coupled to the client configuration engine, for establishing a communications channel with the server computer system if a configuration check has been scheduled.
[0022] A sixth system embodiment comprises a database for storing an independently modifiable copy of user preferences stored on a client computer system, the server computer system coupled via a computer network to the client computer system; a server configuration engine for enabling modification of the independently modifiable copy of the user preferences on the server computer system, for establishing a communications channel with the client computer system, and for providing any changes made since a last configuration check to the client computer system.
[0023] A seventh system embodiment comprises website information offering email forwarding functionality to client computer systems; an email forwarding engine, coupled to the website information, for enabling the email forwarding functionality on the client computer systems; and a web server for enabling the client computer systems to request the email forwarding functionality to be downloaded, and for downloading the email forwarding engine to a requesting client computer system.
[0024] The system and method advantageously use a trusted third party to maintain email and email events within a network system. Accordingly, a user who maintains for example a work site, a home site and the global server site can forward email and email events to the trusted third party from all three sites. The roaming user can thus access and reply to all emails from all three sites while away. Because the system and method operate over the Internet, emails and email events can be forwarded over any distance. Since the system and method include email format translation, merging emails between different application programs and different platforms is possible. Further, because email and/or email events are forwarded from within a firewall and uses commonly enabled protocols such as HyperText Transfer Protocol (HTTP), the typical firewall which prevents in-bound communications in general and some outbound protocols does not act as an impediment. Since the user preferences are set, the present system and method may operate unattended by the client user. The server computer can maintain a complete record of all emails and email events, so that evidence of the occurrence of non-occurrence of email and events can be maintained. The email system enables the safe transfer of emails and/or email events possibly using encryption or receipt generation. The email system enables emails and/or email events not to be forwarded. The email system enables the filtration and transfer protocols of the emails and/or events to be set by the user based on user preferences such as security level, author, recipients, content, etc.
Brief Description of the Drawings
[0025] FIG. 1A is a block diagram illustrating a network system, in accordance with an embodiment of the present invention;
[0026] FIG. 1B is a block diagram illustrating details of an example computer system of FIG. 1 ;
[0027] FIG. 2 is a block diagram illustrating details of the email system of FIG. 1 ;
[0028] FIGS. 3A and 3B are a block diagram illustrating details of the email forwarding engine of FIG. 1 ; and
[0029] FIGS. 4A-4C are a flowchart illustrating a method of installing the email forwarding engine on a client computer system, in accordance with an embodiment of the present invention;
[0030] FIGS. 5A and 5B are a flowchart illustrating a method of forwarding emails from a client computer system across a computer network to a server computer system, in accordance with an embodiment of the present invention; and
[0031] FIG. 6 is a flowchart illustrating a method of checking whether there has been remote modification of the user preferences, in accordance with an embodiment of the present invention.
Detailed Description of the Preferred Embodiments
[0032] The following description is provided to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles, features and teachings disclosed herein.
[0033] FIG. 1A is a block diagram illustrating a network system 100, in accordance with an embodiment of the present invention. The network system 100 includes a server computer system 105 coupled via a computer network 110 to a client computer system 115, to an email server computer system 120, and to a remote computer system 122. It will be appreciated that the computer network 110 may include the wide-area network commonly referred to as “the Internet” and may include one or more local-area networks commonly referred to as “intranets.”
[0034] The server computer system 105 includes a web server 125, an email system 130 and a server database 135. The web server 125 includes program code, hardware and/or firmware for presenting web pages managed by the server computer system 105, and for responding to browser requests from a client computer system 115. That is, the web server 125 receives data from a browser 140 operating on a client computer system 115, and transmits data to the browser 140 operating on a client computer system 115.
[0035] The email system 130 includes program code, hardware and/or firmware for enabling a user on a client computer system 115 to request email forwarding functionality to be added to the client computer system 115, for providing program code to install and enable email and/or email event forwarding on the client computer system 115, and for managing email data (e.g., email and/or email events) forwarded from the client computer system 115. Details of the email system 130 are described in greater detail with reference to FIG. 2 .
[0036] The server database 135 includes a data structure, which maintains emails and/or email events being forwarded from the client computer system 115. The server database 135 may include multiple data structures for storing multiple sets of emails and/or email events from multiple client computer systems 115. The structure of the server database 135 is maintained by the email system 130.
[0037] The client computer system 115 includes a browser 140, an email client 145, email and/or email events (illustrated as “email/events”) 150, and, if already installed, an email forwarding engine 155. The browser 140 includes program code, hardware and/or firmware for enabling a client computer system 115 to communicate via the computer network 110 with web servers 125 operated on server computer systems 105, and for presenting information from websites maintained by the web server 125. Examples of browsers 140 include the Netscape Navigator™ browser by the Netscape Communications Corporation and the Internet Explorer™ browser by the Microsoft Corporation.
[0038] The email client 145 includes program code, hardware and/or firmware for communicating with an email server 160 maintained on the mail server computer system 120. The email client 145 acts as the interface to conventional email functionality, enabling a user to make conventional requests such as retrieving, writing, reading, forwarding, replying, deleting, etc. Email 150 includes email downloaded from the email server 160, email created and sent from the client computer system 115, etc. Email events 150 includes transaction information such as created email, read email, deleted email, forwarded email, deleted without reading, etc. The email and/or email events 150 preferably does not include an email that has been trashed, e.g., dragged to the trash and the trash emptied, but preferably does include the trashing event.
[0039] The email forwarding engine 155 includes program code, hardware and/or firmware for providing the email forwarding functionality to the client computer system 115. The email forwarding engine 155 is preferably downloaded from the server computer system 105, although it may be obtained in several other ways, e.g., uploaded from a CD-ROM or floppy disk, received as an attachment in an email, written, received from any other network site, etc. The email forwarding engine 155 preferably obtains all emails and/or email events 150 and 165 not yet forwarded to the server computer system 105, and forwards them upon satisfaction of predetermined criteria such as the expiration of a time limit or occurrence of a predetermined event. Details of the email forwarding engine 155 are described in FIGS. 3A and 3B .
[0040] The email server computer system 120 includes an email server 160 and email and/or email events (illustrated as “email/events”) 165. The email server 160 includes program code, hardware and/or firmware for managing email received from the computer network 110, for storing them as email 165, for forwarding the email to the appropriate client computer system 115, and for maintaining a log of email events such as forwarded email from the client computer system to the computer network 110, forwarded email to the client computer system from the computer network 110, etc. Upon request by the email client 145, the email server 160 forwards the email 165 to the email client 145, preferably deletes the email 165 stored thereon, and logs the email events as email and/or email events 165. As stated above, the email client 145 stores the retrieved email 165 as email and/or email events 150. Upon request by the email forwarding engine 155, the email server 160 forward copies of email and/or email events 165 to the email forwarding engine 155 and preferably does not deletes its copies of the email 165.
[0041] The remote computer system 122 may be an untrusted computer system being operated by a traveling user. The remote computer system 122 includes a browser 170 for enabling the traveling user to access and retrieve emails and email events from the server database 135 managed by the email system 130 on the server computer system 105.
[0042] It will be appreciated that the server computer system 105, the client computer system 115, the email server computer system 120 and the remote computer system 122 may each be a single computer or multiple computers networked together. Further, it will be appreciated that portions of the program code, hardware and/or firmware on each computer system may be maintained on different computers. Still further, it will be appreciated that the server database 135, the email and/or email events 150 and the email and/or email events 165 need not be stored on the same computer as the program code, hardware and/or firmware that is managing or manipulating it.
[0043] FIG. 1B is a block diagram illustrating details of a computer system 175, wherein each of the server computer system 105, the client computer system 115, the email server computer system 120 and the remote computer system 122 is a specific example thereof. The computer system 175 includes a processor 177, such as an Intel Pentium® microprocessor or a Motorola Power PC® microprocessor, coupled to a communications channel 183. The computer system 175 further includes an input device 179 such as a keyboard or mouse, an output device 181 such as a cathode ray tube display, a communications interface 185, permanent storage 187 such as a magnetic disk, and working memory 189 such as Random-Access Memory (RAM), each coupled to the communications channel 183. The communications interface 185 may be coupled to the computer network 110. One skilled in the art will recognize that, although the permanent storage 187 and working memory 189 are illustrated as different units, the permanent storage 187 and working memory 189 can be parts of the same unit or units on different computer systems.
[0044] One skilled in the art will recognize that the computer system 175 may also include additional information, such as network connections, additional memory, additional processors, LANs, input/output lines for transferring information across a hardware channel, the Internet or an intranet, etc. One skilled in the art will also recognize that the program code and data may be received by and stored in the computer system 175 in alternative ways. For example, a computer-readable storage medium (CRSM) reader 191 such as a magnetic disk drive, hard disk drive, magneto-optical reader, CPU, etc. may be coupled to the communications channel 183 for reading a computer-readable storage medium (CRSM) 193 such as a magnetic disk, a hard disk, a magneto-optical disk, RAM, etc. Accordingly, the system 175 may receive program code and data via the CRSM reader 191. Further, it will be appreciated that the term “memory” herein is intended to cover all data storage media whether permanent or temporary.
[0045] FIG. 2 is a block diagram illustrating details of the email system 130. The email system 130 includes website information 205, a pre-check engine 210, an email forwarding engine 215, an identification engine 220, a server configuration engine 225, and a server database manager 230.
[0046] The website information 205 includes program code (e.g., applets, scripts, HTML, etc.) and/or data that the web server 125 provides to browsers 140 accessing the appropriate webpage. The website information 205 may include descriptions of the email forwarding functionality and the multiple versions available. The website information 205 may also include the buttons and button functionality for requesting the email forwarding functionality to be downloaded to the requesting client computer system 115.
[0047] The pre-check engine 210 includes program code such as ActiveX™ controls, applets, HTML, script, etc., which when provided to the browser 140 is automatically executed. The pre-check engine 210 determines whether the client computer system 115 has a satisfactory version of the email forwarding engine 215 already installed. For example, the pre-check engine 210 may be configured to examine whether the email forwarding engine 215 already installed thereon includes all the necessary modules to conduct satisfactory email and/or email event forwarding. If the email forwarding engine 215 is too antiquated or non-existent, the pre-check engine 210 will instruct the web server 125 to download the latest version of the email forwarding engine 215. Otherwise, the pre-check engine 210 will instruct the web server 125 to present website information 205 informing the user that the version installed thereon is still satisfactory.
[0048] The email forwarding engine 215 includes program code, hardware and/or firmware for providing the email functionality described above with reference to FIG. 1A . That is, the email forwarding engine 215 self-installs, determines whether certain start criteria have been met, and, if so, retrieves newly received or created emails and/or email events. The email forwarding engine 215 determines the sensitivity of the email or email event, and forwards the emails, email events or a message (e.g., receipt confirmation) corresponding to the emails and/or email events to the server computer system 105 for storage. Details of the email forwarding engine 215 are provided in and with reference to FIGS. 3A and 3B .
[0049] The identification engine 220 includes program code, hardware and/or firmware for communicating with the email forwarding engine 155 on the client computer system 115 to provide it with an ID and password for communicating with the server computer system 105. The identification engine 220 may alternatively provide any identification and authentication technique such as certificates, public and private key cryptography, single-key two-way encryption, etc.
[0050] The server configuration engine 225 includes program code, hardware and/or firmware for obtaining client configuration information including the processor type and speed, the communication protocols, etc. and for obtaining user preferences including preferred start criteria and filter data. The server configuration engine 225 also provides remote control of user preferences. For example, a user can access the server configuration engine 225 from the remote computer system 122, and request different start criteria for the email forwarding engine on the client computer system 115. The email forwarding engine 155 includes program code, hardware and/or firmware that contacts the server computer system 105 to check if user preferences have changed. If so, the email forwarding engine 155 will change its preferences, e.g., the start criteria. The user preferences may also include the configuration-check schedule. Remote control of user preferences by the server configuration engine 225 is described in greater detail in and with reference to FIGS. 3A and 3B .
[0051] The server database manager 230 includes program code, hardware and/or firmware for receiving emails and/or email events 150 and 165 from the client computer system 115, and for storing them in the server database 135. The server database manager 230 preferably maintains the emails and email events in separate sub-folders, and both in a folder corresponding to the user. If requested, the server database manager 230 may divide the emails or email events into sub-sub-folders corresponding to user defined preferences. For example, the user may opt to have emails further divided into sub-sub-folders corresponding to the sites from which they were forwarded, corresponding to the sender, corresponding to their sensitivity, etc.
[0052] FIGS. 3A and 3B are a block diagram illustrating details of the email forwarding engine 155 on the client computer system 115. The email forwarding engine 155 includes an automatic installation engine 305, a client configuration engine 310, an email and/or email event retrieval engine 315 (illustrated as “email/event retrieval engine”), email server libraries and protocol 320, a tagging engine 325, a format converter 330, a communications engine 335, a filter 345, a data transmitter 350, an encryption engine 355, a receipt generator 360 and a user interface 365.
[0053] The automatic installation engine 305 includes program code, hardware and/or firmware for automatically installing the remaining components of the email forwarding engine 155 to provide the email forwarding functionality described above with reference to FIGS. 1A and 2 . The automatic installation engine 305 preferably uses conventional installation protocols. The automatic installation engine 305 preferably causes the email forwarding engine 155 to initiate each time the client computer system is booted up, either by placing it as a start-up file or making arrangements with the scheduler on the client computer system 115.
[0054] The client configuration engine 310 includes program code, hardware and/or firmware for obtaining system configuration information such as processor type and speed, RAM available, etc. and for enabling the user to select preferences. Selecting preferences may include selecting start criteria, such as every fifteen minutes, every day at a particular time, after a predetermined event, e.g., receipt of an email or an expected email, etc. The user preferences may be initially set to defaults. The client configuration engine 310 uses the communications engine 335, described below, to establish a communications channel with the server computer system 105, and forwards the configuration information and user selected preferences to the server configuration engine 225 of the email system 130, which stores the information.
[0055] After the start criteria have been met, the client configuration engine 310 contacts the server configuration engine 225 to determine whether the user selected preferences have been modified remotely. Alternatively, the client configuration engine 310 may check whether the start criteria have been modified remotely, in accordance with a schedule independent from the start criteria, i.e., in accordance with a configuration-check schedule. Accordingly, if the user selected preferences, e.g., the start criteria, have been modified, the client configuration engine 310 modifies the user selected preferences, and determines whether the new start criteria have been met. If so, the client configuration engine 310 initiates the email and/or email event retrieval engine 315. Otherwise, the client configuration engine 310 returns to waiting. Similarly, if other user preferences, e.g., filter control data described below, the client configuration engine 310 modifies those user preferences. In another embodiment, the filter control data may not be remotely modifiable. It will be further appreciated that the configuration-check schedule may also be configured to be modified remotely.
[0056] The email and/or email event retrieval engine 315 includes program code, hardware and/or firmware for retrieving new email (received from the computer network 110) and email events (such as received email, forwarded email to client computer system 115, forwarded email to the computer network 110, etc.) 165 from the email server computer system 120. The retrieval engine 315 also includes program code, hardware and/or firmware for retrieving new email (created at the client computer system 115 or received from the email server computer system 120) and email events (such as created email, forwarded email, replied to email, trashed email, etc.) 150. It will be appreciated that the retrieval engine 315 may communicate with the email client 145 to retrieve email and/or email events 150, and to act as a proxy to the email server 160 to retrieve email and/or email events 165 from the email server computer system 120. Alternatively, the retrieval engine 315 may obtain the information directly from their storage locations.
[0057] The retrieval engine 315 uses the email server libraries and protocol 320 either to communicate directly with the email server 160, to retrieve the email 165 directly, to communicate with the email client 145, or to retrieve the email 165 and/or email events 150 directly. For example, the email server libraries and protocol 320 include the libraries and protocol for communicating with a variety of different email server formats such as MAPI and the POP3.
[0058] The tagging engine 325 includes program code, hardware and/or firmware for identifying the emails and/or email events 150 and 165 that are being forwarded to the server computer system 105. The tagging engine 325 preferably maintains the date and time of the last email and/or email event 150 and 165 at least to the second, and possible to the millisecond. The retrieval engine can compare all emails and/or email events 150 and 165 against this date and time to determine which are new and which have already been forwarded.
[0059] The format converter 330 includes program code, hardware and/or firmware for converting emails and/or email events 150 and 165 to a common format, e.g., MIME. Not all email server computer systems 120 operate using the same format. Accordingly, a format converter 330 may be used to forward format converted emails and/or email events 150 and 165 to the server computer system 105 in a single format.
[0060] The communications engine 335 includes program code, hardware and/or firmware for establishing a communications channel with the email system 130. The communications engine 335 includes an ID and password 340 which identifies and authenticates the email forwarding engine 155, and thus the user. The communications engine 335 may use secure connection techniques such as SSL, encryption, private and public key cryptography, etc. The communications engine 335 enables the other components of the email forwarding engine 155 to communicate with the components the email system 130.
[0061] The filter 345 includes program code, hardware and/or firmware for examining the email and/or email events 150 and 165 that are scheduled to be forwarded to the server computer system 105 against the user preferences (e.g., filter control data), and for determining what data will actually be forwarded. For example, if an email contains sensitive information, a user may prefer not to have it forwarded, to have it forwarded using secure means or to have only a portion forwarded. Similarly, the user may prefer only to have emails from select individuals forwarded. Thus, in accordance with the filter control data, the filter 345 may examine the recipient list, the sender list, the email content, or the like in accordance with the filter control data to control what gets forwarded and how. For example, a user may specify in the filter control data that, if an email contains the word “confidential,” “privileged,” “sensitive,” etc., then only a confirmation of receipt (not the email) should be forwarded. The user may also specify that, if the email is from “John Smith,” then the email should be sent using encryption. The user may also specify that, if the email has been sent to at least one recipient having an email address in a public site such as “yahoo” or “hotmail,” then the email can be sent without encryption regardless. The filter 345 operates on email and email events similarly.
[0062] The data transmitter 350 includes program code, hardware and/or firmware for transmitting the data that the filter 345 allowed or generated. The transmitter 350 may use conventional message packets transfer techniques, handshaking protocols, etc. to transfer the data.
[0063] The encryption engine 355 includes program code, hardware and/or firmware for encrypting messages being transmitted to the server computer system 105. The encryption engine 355 may operate with the communications engine 335 when encrypting all messages. The encryption engine 355 may operate with the data transmitter 350 when encrypting all messages, or when transmitting only messages specified by the filter 345 to be encrypted. The encryption engine 355 preferably uses conventional techniques such as public and private key cryptography or two-way single-key encryption.
[0064] The receipt generator 360 includes program code, hardware and/or firmware for operating with the filter 345 to generate a confirmation of receipt of an email and/or email event 150 or 165 to be forwarded in lieu of the actual email and/or email event 150 or 165.
[0065] The user interface 365 includes program code, hardware and/or firmware to enable the user to set user preferences and other information.
[0066] FIGS. 4A-4C are a flowchart illustrating a method 400 of automatically installing the email forwarding functionality, in accordance with an embodiment of the present invention. The method 400 begins with the browser 140 in step 405 receiving a request from a user to access a particular website managed by the server computer system 105. The web server 125 in step 410 presents website information 205 including the email forwarding functionality option to the user. In response to a user request, the browser 140 in step 415 selects the option.
[0067] The web server 125 in step 420 provides the pre-check engine 210 to the browser 140. The browser 140 in step 425 executes (or interprets) the pre-check engine 210 to determine whether the client computer system 110 already has a satisfactory version of the email forwarding engine 155 installed thereon. If so, then the pre-check engine 210 in step 435 informs the user, and method 400 then ends. Otherwise, the web server 125 in step 440 downloads the latest version of the email forwarding engine 155 to the client computer system 115.
[0068] In step 445, the browser 140 initiates execution of the automatic installation engine 305, which installs the remaining components of the email forwarding engine 155 on the client computer system 115. The client configuration engine 310 in step 450 enables the user to select or set preferences (e.g., start criteria, filter control data, configuration-check schedule and other information), in step 455 obtains any client configuration information (e.g., processor type and speed, connection type and speed, etc.) and in step 460 establishes a communications channel with the server computer system 105. The client configuration engine 310 in step 465 forwards any user preferences and client configuration information to the server computer system 105.
[0069] The identification engine 220 in step 470 sends an ID and password (or other identification and authentication information) to the client configuration engine 310, which in step 475 installs the ID and password in the communications engine 335 of the email forwarding engine 155. The automatic installation engine 305 in step 485 places the email forwarding engine 155 as a start-up file, makes arrangement with the scheduler to start the email forwarding engine 155 upon boot up, or any other equivalent technique. Method 400 then ends.
[0070] FIGS. 5A and 5B are a flowchart illustrating a method 500 of forwarding email and/or email events, in accordance with an embodiment of the present invention. Method 500 begins with the client computer system 115 in step 505 initiating execution or interpretation of the email forwarding engine 155. The client configuration engine 310 in steps 510 and 515 determines whether predetermined start criteria have been met. If the criteria have not been met, then the client configuration engine 310 returns to step 510.
[0071] If the criteria have been met, then the email and or email retrieval engine 315 in step 520 retrieves new email and/or email events 150 and 165 from the client computer system 115 and from the email server computer system 120. The filter 345 in the step 525 reviews the emails and/or email events 150 and 165 retrieved against filter control data to determine the “security” level of the information, the data to transmit and the transfer protocols. For example, the user may have specified that, if an email message retrieved includes the word “privileged,” then the email should be encrypted and then forwarded. As another example, the user may have specified that, if the email and/or email event was with “John Smith,” then nothing about the transaction should be forwarded. As yet another example, the user may have specified that, if an email transaction remained only within the local network of the workplace, only a receipt identifying the transaction should be forwarded. Based on the filter control data, the filter 345 determines what data to transmit and how to transmit it.
[0072] The format converter 330 in step 530 converts, if necessary, any email and/or email events to the proper email format. For example, if an email is in the RTF format, but all email on server computer system 105 is maintained in MIME format, the format converter 330 converts the email from the RTF format to the MIME format.
[0073] The communications engine 335 in step 535 uses the ID and password 340 to establish a communications channel with the email system 130. The tagging engine 325 in step 540 records which emails and/or events are being forwarded, preferably, by maintaining the date and time of the last email and/or event being forwarded to the nearest millisecond. The data transmitter 350 in step 545 transmits the data to transfer, as determined by the filter 345, according to the transfer protocols, also as determined by the filter 345, to the email system 130. The data transmitter 350 uses encryption engine 355 to encrypt messages labeled for encryption and the receipt generator 360 to generate receipts, as needed. The server database manager 230 in step 550 stores the transferred data in the server database 135. Method 500 then ends.
[0074] FIG. 6 is a flowchart illustrating a method 500 of checking whether there has been a remote modification of user preferences. Method 500 begins with the client configuration engine 310 in step 605 examining a configuration-check schedule. The configuration-check schedule may be a default schedule that defines the times when the client configuration engine 310 should check for remote changes to the user preferences. Alternatively, the configuration-check schedule may be user defined in the user preferences. In step 610, the client configuration engine 310 determines whether a check has been scheduled. If not, then the method 600 returns to step 605.
[0075] If a check has been scheduled, then the communications engine 335 in step 615 uses the ID and password 340 to establish a communications channel with the server configuration engine 225 on the server computer system 105. The client configuration engine 310 in steps 620 and 625 communicates with the server configuration engine 225 to determine if any remote changes to the user preferences have been made. These changes may include changes to the start criteria and changes to the configuration-check schedule. If not, then method 600 ends. Otherwise, the client configuration engine 310 in step 630 modifies the user preferences on the client computer system 115. Method 600 then ends.
[0076] The foregoing description of the preferred embodiments of the present invention is by way of example only, and other variations and modifications of the above-described embodiments and methods are possible in light of the foregoing teaching. For example, although the server computer, client computer and email server computer are each illustrated as a single device, each may include several computers networked together. Although the network sites are being described as separate and distinct sites, one skilled in the art will recognize that these sites may be a part of an integral site, may each include portions of multiple sites, or may include combinations of single and multiple sites. Further, components of this invention may be implemented using a programmed general purpose digital computer, using application specific integrated circuits, or using a network of interconnected conventional components and circuits. Connections may be wired, wireless, modem, etc. The embodiments described herein are not intended to be exhaustive or limiting. The present invention is limited only by the following claims.
Claims
What is claimed is:
1. A method of forwarding email, comprising:
downloading an email forwarding engine from a server computer to a client personal computer, the downloaded email forwarding engine including computer-readable instructions to cause the client personal computer to
examine start criteria, the start criteria being independent of email stored in an email datastore of an email server;
determine whether the start criteria are met;
obtain new email events from the email datastore when the start criteria are met, the new email events including transactional information indicating a status of the email stored in the email datastore of the email server;
forward information including the new email events via a computer network to a datastore associated with the server;
compare the start criteria stored on the client personal computer with start criteria stored on the server; and
synchronize the start criteria stored on the client personal computer and the start criteria stored on the server when a difference is detected therebetween,
wherein the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
2. The method of claim 1, wherein the client personal computer is protected by a firewall.
3. The method of claim 1, wherein the downloaded email forwarding engine self-installs.
4. The method of claim 1, wherein the email events include emails.
5. A system for forwarding email, comprising:
a server computer storing a client software for downloading to a client personal computer, the client software including
a client configuration engine configured to determine whether start criteria are met, the start criteria being independent of email stored on an email datastore of an email server, the client configuration engine also being configured to compare the start criteria stored on the client personal computer with start criteria stored on the server and to synchronize the start criteria stored on the client personal computer with the start criteria stored on the server when a difference is detected therebetween;
a retrieval engine, coupled to the client configuration engine, configured to receive new email events from the email datastore, the new email events including transactional information indicating a status of the email stored on the email datastore of the email server; and
a data transmitter, coupled to the retrieval engine, configured to forward information including the new email events via a computer network to a datastore associated with the server,
wherein the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
6. The system of claim 5, wherein the client personal computer is protected by a firewall.
7. The system of claim 5, wherein the downloaded client software self-installs.
8. The system of claim 5, wherein the email events include emails.
9. A method of forwarding email, comprising:
establishing a communications channel between a server and a client personal computer system;
downloading, to the client computer system, an email forwarding engine;
receiving, at the client computer system, information including new email events from an email datastore of an email server, the email events including transactional information indicating a status of emails stored on the email datastore of the email server;
storing the information including the new email events in a datastore associated with the server;
forwarding the information stored in the datastore associated with the server to an appropriate client personal computer; and
comparing start criteria stored on the server with start criteria stored on the client personal computer, the start criteria stored on the server and the start criteria stored on the client personal computer being independent of the information stored in the datastore,
wherein the start criteria of the client personal computer is synchronized to the start criteria of the server when a difference is detected therebetween, and the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
10. The method of claim 9, wherein the client personal computer is protected by a firewall.
11. The method of claim 9, wherein the email events include emails.
12. A system for forwarding email, comprising:
a server computer including a datastore and a client software for downloading to a client personal computer, the client software including
a retrieval engine to retrieve new email events from an email datastore of an email server, the email events including transactional information indicating a status of emails stored on the email datastore of the email server, and
a client configuration engine configured to determine whether start criteria are met, the start criteria being independent of the emails stored on an email datastore, the client configuration engine also being configured to compare the start criteria stored on the client personal computer with start criteria stored on the server and to synchronize the start criteria stored on the client personal computer with the start criteria stored on the server when a difference is detected therebetween;
the server being configured to establish communications with the client computer system, receive information including new email events from the client computer system, store the information including the new email events in the datastore of the server, and convey the information stored in the datastore of the server to an appropriate client personal computer,
wherein the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
13. The system of claim 12, wherein the client personal computer is protected by a firewall.
14. The system of claim 12, wherein the email events include emails.
15. A method of forwarding email, comprising:
downloading an email forwarding engine from a server computer system to a client personal computer, the downloaded email forwarding engine including computer-readable instructions to cause the client personal computer to
obtain filter control data, the filter control data being independent of email data, the email data including transactional information indicating a status of the email data;
examine the email data against the filter control data;
determine the email data that will be forwarded based on the examination;
select at least one transfer protocol for the email data based on the examination;
forward the email data according to the at least one transfer protocol via a computer network to a datastore associated with the server;
compare the filter control data stored on the client personal computer with filter control data stored on the server at predetermined time intervals; and
synchronize the filter control data stored on the client personal computer to the filter control data stored on the server when a difference is detected between therebetween,
wherein the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
16. The method of claim 15, wherein the client personal computer is protected by a firewall.
17. The method of claim 15, wherein the downloaded email forwarding engine self-installs.
18. A system for forwarding email, comprising:
a server computer including a client software for downloading to a client personal computer, the client software including
a filter configured to examine email data against filter control data to select email data based on the examination, and configured to determine at least one transfer protocol for the email data based on the examination, the email data including transactional information indicating a status of the email data;
a data transmitter, coupled to the filter, configured to forward the email data according to the at least one transfer protocol via a computer network to a datastore associated with the server and server software that forwards the forwarded email data to a remote device;
a client configuration engine configured to compare the filter control data stored on the client personal computer with a filter control data stored on the server and configured to synchronize the filter control data stored on the client personal computer to the filter control data stored on the server when a difference is detected therebetween,
wherein the filter control data stored on the client personal computer and the filter control data stored on the server are independent of the email data, and the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
19. The system of claim 18, wherein the client personal computer is protected by a firewall.
20. The system of claim 18, wherein the downloaded client software self-installs.
21. A method of forwarding email, comprising:
downloading a computer program from a server computer system to a client personal computer, the downloaded computer program including computer-readable instructions to cause the client personal computer to
obtain filter control data, the filter control data being independent of email data, the email data including transactional information indicating a status of the email data;
examine the email data against the filter control data;
determine, based on the examination, the email data that should not be forwarded;
generate receipt data identifying the email data that should not be forwarded;
forward the receipt data via a computer network to a datastore associated with the server;
compare the filter control data stored on the client personal computer with filter control data stored on the server; and
synchronize the filter control data stored on the client personal computer to the filter control data stored on the server when a difference is detected therebetween,
wherein the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
22. The method of claim 21, wherein the client personal computer is protected by a firewall.
23. A system for forwarding email, comprising:
a server computer including a client software for downloading to a client personal computer, the client software including
a filter configured to examine email data against filter control data, the filter control data being independent of the email data, and configured to determine, based on the examination, the email data that will not be forwarded, the email data including transactional information indicating a status of the email data;
a receipt generator, coupled to the filter, for generating receipt data identifying the email data that should not be forwarded;
a data transmitter, coupled to the filter, for forwarding the receipt data via a computer network to a datastore associated with the server; and
a client configuration engine configured to compare the filter control data stored on the client personal computer with filter control data stored on the server and configured to synchronize the filter control data stored on the client personal computer to the filter control data stored on the server when a difference is detected therebetween,
wherein the transactional information includes information indicating the email as at least one of created email, forwarded email, replied to email and deleted email.
24. The system of claim 23, wherein the client personal computer is protected by a firewall.
Patent Citations (111)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4714995(A) | 1987-12-01 | Materna et al. | Applicant |
| US4831582(A) | 1989-05-01 | Miller et al. | Applicant |
| US4875159(A) | 1989-10-01 | Cary et al. | Applicant |
| US4897781(A) | 1990-01-01 | Chang et al. | Applicant |
| US5263157(A) | 1993-11-01 | Janis | Applicant |
| US5386564(A) | 1995-01-01 | Shearer et al. | Applicant |
| US5388255(A) | 1995-02-01 | Pytlik et al. | Applicant |
| US5392390(A) | 1995-02-01 | Crozier | Applicant |
| US5544320(A) | 1996-08-01 | Konrad | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Applicant |
| US5581749(A) | 1996-12-01 | Hossain et al. | Applicant |
| US5588132(A) | 1996-12-01 | Cardoza | Applicant |
| US5600834(A) | 1997-02-01 | Howard | Applicant |
| US5613012(A) | 1997-03-01 | Hoffman et al. | Applicant |
| US5623601(A) | 1997-04-01 | Vu | Applicant |
| US5627658(A) | 1997-05-01 | Connors et al. | Applicant |
| US5634053(A) | 1997-05-01 | Noble et al. | Applicant |
| US5647002(A) | 1997-07-01 | Brunson | Applicant |
| US5652884(A) | 1997-07-01 | Palevich | Applicant |
| US5664207(A) | 1997-09-01 | Crumpler et al. | Applicant |
| US5666530(A) | 1997-09-01 | Clark et al. | Applicant |
| US5666553(A) | 1997-09-01 | Crozier | Applicant |
| US5678039(A) | 1997-10-01 | Hinks et al. | Applicant |
| US5680542(A) | 1997-10-01 | Mulchandani et al. | Applicant |
| US5682524(A) | 1997-10-01 | Freund et al. | Applicant |
| US5684984(A) | 1997-11-01 | Jones et al. | Applicant |
| US5684990(A) | 1997-11-01 | Boothby | Applicant |
| US5687322(A) | 1997-11-01 | Deaton | Applicant |
| US5701400(A) | 1997-12-01 | Amado | Applicant |
| US5701423(A) | 1997-12-01 | Crozier | Applicant |
| US5706502(A) | 1998-01-01 | Foley et al. | Applicant |
| US5710918(A) | 1998-01-01 | Lagarde et al. | Applicant |
| US5713019(A) | 1998-01-01 | Keaten | Applicant |
| US5715403(A) | 1998-02-01 | Stefik | Applicant |
| US5717925(A) | 1998-02-01 | Harper et al. | Applicant |
| US5721908(A) | 1998-02-01 | Lagarde et al. | Applicant |
| US5721914(A) | 1998-02-01 | DeVries | Applicant |
| US5729735(A) | 1998-03-01 | Meyering | Applicant |
| US5745360(A) | 1998-04-01 | Leone et al. | Applicant |
| US5752246(A) | 1998-05-01 | Rogers et al. | Applicant |
| US5757916(A) | 1998-05-01 | MacDoran et al. | Applicant |
| US5758150(A) | 1998-05-01 | Bell et al. | Applicant |
| US5758354(A) | 1998-05-01 | Huang et al. | Applicant |
| US5758355(A) | 1998-05-01 | Buchanan | Applicant |
| US5764902(A) | 1998-06-01 | Rothrock | Applicant |
| US5765171(A) | 1998-06-01 | Gehani et al. | Applicant |
| US5778346(A) | 1998-07-01 | Frid-Nielsen et al. | Applicant |
| US5790425(A) | 1998-08-01 | Wagle | Applicant |
| US5790790(A) | 1998-08-01 | Smith et al. | Applicant |
| US5799318(A) | 1998-08-01 | Cardinal et al. | Applicant |
| US5812773(A) | 1998-09-01 | Norin | Applicant |
| US5832483(A) | 1998-11-01 | Barker | Applicant |
| US5835601(A) | 1998-11-01 | Shimbo et al. | Applicant |
| US5862325(A) | 1999-01-01 | Reed | Applicant |
| US5862346(A) | 1999-01-01 | Kley et al. | Applicant |
| US5870759(A) | 1999-02-01 | Bauer et al. | Applicant |
| US5878230(A) | 1999-03-01 | Weber et al. | Examiner |
| US5918158(A) | 1999-06-01 | LaPorta et al. | Examiner |
| US5924103(A) | 1999-07-01 | Ahmed et al. | Applicant |
| US5928329(A) | 1999-07-01 | Clark et al. | Applicant |
| US5943676(A) | 1999-08-01 | Boothby | Applicant |
| US5951652(A) | 1999-09-01 | Ingrassia et al. | Applicant |
| US5961590(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5966714(A) | 1999-10-01 | Huang et al. | Applicant |
| US5968131(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5974238(A) | 1999-10-01 | Chase, Jr. | Applicant |
| US5999932(A) | 1999-12-01 | Paul | Examiner |
| US5999947(A) | 1999-12-01 | Zollinger et al. | Applicant |
| US6020885(A) | 2000-02-01 | Honda | Applicant |
| US6021427(A) | 2000-02-01 | Spagna et al. | Applicant |
| US6023700(A) | 2000-02-01 | Owens et al. | Examiner |
| US6023708(A) | 2000-02-01 | Mendez et al. | Applicant |
| US6029164(A) | 2000-02-01 | Birrell et al. | Examiner |
| US6034621(A) | 2000-03-01 | Kaufman | Applicant |
| US6073165(A) | 2000-06-01 | Narasimhan et al. | Examiner |
| US6085192(A) | 2000-07-01 | Mendez et al. | Applicant |
| US6094477(A) | 2000-07-01 | Nada et al. | Examiner |
| US6108709(A) | 2000-08-01 | Shinomura et al. | Examiner |
| US6118856(A) | 2000-09-01 | Paarsmarkt et al. | Examiner |
| US6125281(A) | 2000-09-01 | Wells et al. | Examiner |
| US6131096(A) | 2000-10-01 | Ng et al. | Applicant |
| US6131116(A) | 2000-10-01 | Riggins et al. | Applicant |
| US6138146(A) | 2000-10-01 | Moon et al. | Examiner |
| US6151606(A) | 2000-11-01 | Mendez | Applicant |
| US6212529(B1) | 2001-04-01 | Boothby et al. | Applicant |
| US6249805(B1) | 2001-06-01 | Fleming, III | Examiner |
| US6295541(B1) | 2001-09-01 | Bodnar et al. | Applicant |
| US6343313(B1) | 2002-01-01 | Salesky et al. | Applicant |
| US6374300(B2) | 2002-04-01 | Masters | Examiner |
| US6442589(B1) | 2002-08-01 | Takahashi et al. | Examiner |
| US6446118(B1) | 2002-09-01 | Gottlieb | Examiner |
| US6457062(B1) | 2002-09-01 | Pivowar et al. | Examiner |
| US6477545(B1) | 2002-11-01 | LaRue | Applicant |
| US6510455(B1) | 2003-01-01 | Chen et al. | Examiner |
| US6564218(B1) | 2003-05-01 | Roth | Applicant |
| US6757712(B1) | 2004-06-01 | Bastian et al. | Examiner |
| US6760752(B1) | 2004-07-01 | Liu et al. | Examiner |
| US6907112(B1) | 2005-06-01 | Guedalia et al. | Examiner |
| US6956845(B2) | 2005-10-01 | Baker et al. | Examiner |
| US7039679(B2) | 2006-05-01 | Mendez et al. | Applicant |
| US2003/0097358(A1) | 2003-05-01 | Mendez | Applicant |
| US2003/0130984(A1) | 2003-07-01 | Quinlan et al. | Applicant |
| US2004/0117310(A1) | 2004-06-01 | Mendez et al. | Applicant |
| US2006/0195595(A1) | 2006-08-01 | Mendez et al. | Applicant |
| US2007/0174433(A1) | 2007-07-01 | Mendez et al. | Applicant |
| CA2210763 | 2000-02-01 | Applicant | |
| EP801478 | 1997-10-01 | Applicant | |
| WO97/04389 | 1997-02-01 | Applicant | |
| WO97/35265 | 1997-09-01 | Applicant | |
| WO99/05620 | 1999-02-01 | Applicant | |
| WO99/45451 | 1999-09-01 | Applicant |
Non-Patent Literature (20)
- US 5,373,559, 12/1994, Kaufman et al. (withdrawn)Applicant
- Research Disclosure; “Provide Auto-Forwarding Based on Criteria Selected by the User”; Oct. 1, 1989; 1 page; No. 306; Kenneth Mason Publications; XP000085405; ISSN; 0374-4353.Applicant
- Margaret J. Brown, “The Visto Briefcase Pro Puts. Your PIM On The Internet,” URL:http://www.zdnet.com/zdnn/stories/zdnn—display/0.3440.341892.00.html, Aug. 13, 1998, 1 page.Applicant
- Web site entitled “Bookmark Translator 2.0: This Utility transform Microsoft Internet Explore's bookmarks in the format valid for Netscape Navigator and viceversa,” Enzo Marianacci, Rome-Jul. 1997, URL=http://www.bns.it/emware/Bookmark Translator-uk.htm, pp. 1-4.Applicant
- Article by Bellovin et al., entitled: “Network Firewalls” Published by IEEE Communications Magazine Sep. 1994, pp. 50-57.Applicant
- Article by Steffen Stempel, entitled: “IPAccess-An Internet Service Access System for Firewall Installations” Published by IEEE Communications Magazine Feb. 16, 1995, pp. 31-41.Applicant
- Article by Braun et al., entitled: “Web Traffic Characterization: an assessment of the impact of caching documents from NCSA's web server” Published by Elsevier Science B.V. 1995 pp. 37-51.Applicant
- Article by Nelson et al., entitled: “Security for Infinite Networks” Published by IEEE Communications Magazine on Aug. 22, 1995, pp. 11-19.Applicant
- Article by Greenwald et al., entitled: “Designing an Academic Firewall: Policy, Practice, and Experience with SURF” Published by IEEE Communications Magazine on Feb. 22, 1996, pp. 79-92.Applicant
- Article by Kiuchi et al., entitled: “C-HTTP—The Development of a Secure, Closed HTTP-based Network on the Internet” Published by IEEE Proceedings of SNDSS on Feb. 22, 1996, pp. 64-75.Applicant
- Article by S. Cobb, entitled: “Establishing Firewall Policy” Published by National Computer Security Assn. on Jun. 25-27, 1996, pp. 198-205.Applicant
- U.S. Appl. No. 90/008,397, filed Dec. 29, 2006, Mendez et al.Applicant
- U.S. Appl. No. 90/008,062, filed Jun. 23, 2006, Mendez et al.Applicant
- U.S. Appl. No. 90/007,040, filed May 18, 2004, Mendez et al.Applicant
- U.S. Appl. No. 90/007,093, filed Jun. 18, 2006, Mendez et al.Applicant
- U.S. Appl. No. 90/007,933, filed Feb. 10, 2006, Mendez et al.Applicant
- U.S. Appl. No. 90/007,421, filed Feb. 15, 2005, Mendez et al.Applicant
- U.S. Appl. No. 90/008,162, filed Aug. 11, 2006, Mendez et al.Applicant
- U.S. Appl. No. 90/008,131, filed Jul. 27, 2006, Mendez et al.Applicant
- U.S. Appl. No. 90/008,292, filed Oct. 11, 2006, Mendez.Applicant