Patent Grant
7266586
1. Field of the Invention
This invention relates to the field of electronic messaging systems. In particular, the invention relates to a method and apparatus for presenting a unified view of multiple mailboxes on multiple clients.
2. Description of the Related Art
Electronic message systems, or e-mail systems, enable widespread communications. A typical person may have several mailboxes she/he accesses with different clients, e.g. office computer and handheld computer. For example, Jane Doe might have a corporate mailbox “jdoe@corporate.com” as well as a mailbox with a wireless provider such as “jdoe@wireless.com”. If Jane wishes to be able to receive and work on her messages both while at the office and while on the road she may want a way to create a unified view of the two separate mailboxes on her office client and her handheld client.
Maintaining a unified view of messages sent to a single mailbox can be tricky if the user accesses a single mailbox from multiple locations. Two separate Internet protocols provide varying degrees of support for addressing this problem: the Post Office Protocol version 3 (POP3), defined by RFC 1939, and the Internet Message Access Protocol version 4 (IMAP4), defined by RFC 1730.
With varying degrees of functionality, these protocols rely on mail agents such as Netscape™ Communicator™, Eudora™ or Microsoft™ Outlook Express™ to maintain a partially unified view of a single mailbox accessed from multiple locations. For example, using IMAP4, Jane Doe can see her “jdoe@corporate.com” mailbox from her work using Netscape Communicator™ and she can see that same mailbox from home using Microsoft Outlook Express™. However, neither POP3 nor IMAP4 attempt to provide a unified view of a message received at multiple mailboxes and stored on multiple clients.
Similarly, some handheld computers such as the Palm Connected Organizer™ from 3Com Corporation, Santa Clara, Calif., enable a single mailbox to be viewed on multiple clients through a HotSync™ process. Like POP3 and IMAP4, this process only addresses the viewing of a single mailbox from multiple clients.
One approach some users take to handling multiple mailboxes is to forward all messages received at one mailbox to the other mailboxes. For example, if John Smith sent Jane Doe a message to her corporate mailbox, “jdoe@corporate.com”, Jane can set up her corporate mailbox so that all messages are forwarded to her other mailboxes, including her wireless mailbox, “jdoe@wireless.com”.
However, if Jane responds to the message from her handheld client while viewing the wireless mailbox, there is no mechanism for reflecting that action in her other mailboxes, including her corporate mailbox. Thus, when she next checks her other mailboxes, including her corporate mailbox, she will have to manually perform the actions she performed on the message in the wireless mailbox.
For example, if she replied to the message on her handheld client and filed it in a folder “Personal”, she would have to manually mark the message as replied to and manually file the message in “Personal” when she next accesses her corporate mailbox. This manual system becomes increasingly unwieldy as a person receives mote messages per day.
Also, wireless connectivity is costly. The price per transmission unit is typically high. Also, other cost factors such as battery drain from transmission and receiving exist. Therefore, it may not be desirable to fully reflect a standard mailbox to a wireless mailbox using the above forwarding technique. Also, this forwarding technique can create loops that cause messages to be sent in infinite loops. Therefore, it is typically necessary to forward messages to a particular mailbox only, e.g. corporate to handheld, but not handheld to corporate.
Accordingly, what is needed is a system supporting a unified view of messages from multiple mailboxes that allows actions performed on one client to be reflected in the unified view on other clients. Also, the system should work with handheld wireless computers without incurring high costs.
A method of presenting a unified view of two mailboxes, each mailbox associated with a client is described. The unified view allows the user to see all actions she/he performed on one client reflected in all other unified clients. For example, if a user receives a message from “tbrown@example.com” at her “jdoe@corporate.com” mailbox, that message will also appear in her other mailboxes being unified, e.g. her “jdoe@wireless.com” mailbox.
One of the clients, e.g. the handheld client, has both a high cost, e.g. wireless, communication channel and a low cost, e.g. synchronization, communication channel. The high cost communication channel may have a price associated with transmitting information and their may be non-price cost factors such as battery consumption, bandwidth, and/or other factors that make the use of the high cost communication channel expensive. In contrast the low cost communication channel is typically free, e.g. docking cradle to desktop computer, and uses less power, etc. Thus, the two communication channels are used in conjunction to offer a unified view.
When a message is received by a client from its respective mailbox without an identifier, an identifier is generated and a copy of the message is sent to the other mailboxes with the identifier. For example, when the client receives the message addressed to the “jdoe@corporate.com” mailbox from “tbrown@example.com”, there is no identifier associated with the message. An identifier is generated and a copy of the message is sent to the other mailboxes that includes the identifier. This allows actions performed on the message at a later point on any of the clients to be reflected in the other clients. Messages received with an identifier can be displayed without modification as these messages have already been handled by one of the other clients.
When the user performs actions on a message with a client, the identifier for the message and the action can be conveyed to the other clients in a message to the other mailboxes. For example, when Jane deletes the message with the identifier “jdoe@wireless.com:93” from her wireless client, a message can be sent to the other clients that indicates the identifier and the action, here “deleted”.
The unified view can be selectably updated either over the high cost communication channel or the low cost communication channel. Also, multiple actions can be batched into a single message to the other mailboxes.
The user can select options to control the unification process and the use of the high cost communication channel, e.g. summarize messages over 250 words and/or remove attachments. Other embodiments allow the use of the high cost communication channel to be further controlled by using rules to control what flows over that channel and what is held for when the low cost communication channel is available. For example, messages with a priority of urgent might be sent over the high cost communication channel, but other messages might be held until the lost cost communication channel is available. Thus the use of two communication channels enables the cost of performing the unification to be contained even when there are a large number of messages and or mailboxes to be unified.
A. Definitions
1. Message
A message, also an electronic mail message or an e-mail, is a communiqué from a person and/or machine to another person and/or machine. A message is typically comprised of two parts: a header and a body. The header includes addressing and routing information. The body includes the contents of the message, e.g. a memo, a short note, an attachment, and/or other contents. Users can send messages to other users and/or machines by specifying an address for the recipient. Users can receive messages from other users and/or machines at their mailboxes.
2. Mailbox
A mailbox is a storage area belonging to a user for messages. Each mailbox is associated with one or more electronic mail addresses that can be used to send the user messages. On the Internet, electronic mail addresses are comprised of a user identifier and a host name separated by an “@” symbol, e.g. “jdoe@corporate.com”. Each mailbox has one, or more, addresses associated with it.
Messages sent to the user's address are stored in the user's mailbox. In some systems, the messages are stored on one or more servers. In other systems, the messages are stored directly on the user's computer. Still other systems mix the two approaches. For example, a UNIX server can provide mailboxes to several thousand users with the POP3 protocol and/or the IMAP4 protocol. In this configuration, the user's mailbox is stored on the UNIX server until the user retrieves the messages to her/his computer.
A mailbox accessed using POP3 and/or IMAP4 and the user's copy of that mailbox are considered a single mailbox. For example, if Jane Doe accesses her “jdoe@corporate.com” mailbox using IMAP4, the portion of the mailbox on the UNIX server and the portion of the mailbox on her computer are considered a single mailbox.
Some mail agents such as Microsoft™ Outlook Express™, Netscape™ Communicator™ and Qualcomm™ Eudora™ allow multiple mailboxes to be viewed on a single client. In this case, all of the mailboxes accessed by the user's mail agent can be treated as a single mailbox to be unified with the other mailboxes. For example, if Jane's corporate computer uses Eudora™ to access two mailboxes: “jdoe@corporate.com” and “webmaster@corporate.com”, then she can select to have either and/or both mailboxes unified with her other mailboxes.
3. Action
The term action refers to activities relating to messages. For example, after reading a message with a client, a change is made to the message on many systems to mark the message as read. Other examples of actions include replying to a message, forwarding a message, classifying a message, deleting a message, receiving a message, and/or other actions.
4. Unified View
The term unified view as it applies to messages, and mailboxes, means that the same message has the same status, filing location, etc., on all clients. For example, upon reading a message on one client, if the message is marked read in the other mail agents, then the view is unified.
The unification process can take some time. For example, if a user of the Palm VII™ does not activate their wireless link often or synchronize their handheld with their desktop often, the view inside the Palm VII™ client may not reflect the most current actions and messages received by the other clients, and vice versa.
B. System Overview
The following paragraph lists the elements of
The address 104 and the address 106 allow messages to be sent to the respective mailboxes 100 and 102. In this example, the address 104 is “jdoe@wireless.com” and the address 106 is “jdoe@corporate.com”.
The handheld client 108 and the client 110 are devices with software and/or hardware for accessing the respective mailboxes 100 and 102. The handheld client 108 and the client 110 could be computers, thin client computers, set-top boxes, hand held computers, cellular telephones, pagers, and/or some other type of device. In this example, the handheld client 108 is a Palm VII™ and the client 110 is a computer.
The communication channel 116 and the communication channel 118 can be of several types such as a network channel, a dial-up channel, a wireless channel, and/or some other type of channel. Additionally, multiple types can be used in combination. For example, a dial-up channel and a network channel could be used on a laptop depending on whether the laptop is coupled to a network or dialing in to a network. In this example, the client 110 is connected to a local area network (LAN) such as an Ethernet network for communication with the mailbox 102.
The handheld client 108 has two channels: the high cost communication channel 120 and the low cost communication channel 122. The high cost communication channel 120 has a greater cost associated with it for transmitting and/or receiving data than on the low cost communication channel 122. For example, a wireless communication channel of the type used on pagers and wireless computers is an example of a high cost communication channel because the per transmission unit price is high. Additionally, the cost can take into account factors such as battery usage, power consumption, bandwidth limits, usage limits, and/or other cost factors. The low cost communication channel 122 might include a synchronization channel, a serial channel, a network channel, an infrared channel, a HotSync™ channel, and/or some other type of communication channel. Whereas the high cost communication channel 120 is expensive, the low cost communication channel 122 is cheap in terms of price, bandwidth, battery consumption, etc.
The unifier 112 and the unifier 114 can be standalone software applications, mail agent plug-ins, mail rules, procmail routines, mail handlers, part of the mail agent, and/or some other type of program. The unifier 112 and 114 are able to access messages either directly from the mail server serving their respective mailbox or once the mail has been transferred by the mail agent to the respective client.
A unifier (e.g. the unifier 112 and the unifier 114) can assign each message a distinguishing identifier. This identifier can be incorporated into the header of a message, e.g. add a header “X-UNIFY-ID: identifier”. If a message received by the unifier already has an identifier associated with it, the unifier will not assign a second identifier. Again, this can be implemented by examining the message headers to ascertain if an X-UNIFY-ID header is present. In some embodiments, an additional Multipurpose Internet Mail Extensions (MIME) section including the identifier is added to message bodies instead of adding a header.
The identifier itself should be at least unique across the contents of the mailboxes being unified. Thus, a simple counter combined with a name or number associated with the unifier can be used. For example, the unifier 112 could prefix identifiers it creates with “jdoe@wireless.com:” and a number starting from say “0” and incrementing the counter each time. Similarly, the unifier 114 could prefix identifiers it creates with “jdoe@corporate.com:” and a number. Other types of identifiers could be used such as identifiers dependent on the contents of one or more message headers and/or the message body.
The unifier (e.g. the unifier 112 and the unifier 114) can send a copy of the message including the identifier to the other mailbox using the corresponding address. For example, if a message to addressed to “jdoe@corporate.com” from “tbrown@example.com” is received at the mailbox 102, then it will be assigned an identifier by the unifier 114. For example, the identifier assigned might be “jdoe@corporate.com:97”. A copy of the original message—or a portion of the original message—is then sent to the address 104, “jdoe@wireless.com”. The copy will include the identifier. In some embodiments, the identifier is included as an additional header to the message, e.g. “X-UNIFY-ID: jdoe@corporate.com:97”. Similarly, for a message sent to the address 104, a copy will be sent to the address 106 with a distinguishing identifier by the unifier 112. If the copy of the message is excerpted or modified from the original format, this can be so indicated in the message sent to the other mailboxes.
In some embodiments, the unifier 114 accepts user defined parameters to control which messages and/or which portions of messages are sent to the address 104. Because of the high cost of using the high cost communication channel 120, it may be undesirable to send large messages and or message attachments to the address 104. In some embodiments, the user can select whether or not attachments are included when sent to the address 104. In some embodiments, the user can select a predetermined amount of a message to be sent to the address 104, e.g. first 250 words, etc. In some embodiments, the user can request that the unifier 114 summarize messages longer than a predetermined amount and send the summary to the address 104 along with the identifier. Also, the user may request that attachments be translated into a format usable by the handheld client 108.
The unifier (e.g. the unifier 112 and the unifier 114) can send messages when actions occur. The messages can be sent periodically from the unifier 114 to the address 104. The message content for an action would typically be a single line comprising two parts: the identifier and the action description. For example, if Jane reads the message from “tbrown@example.com” on her handheld client 108, an action message such as “jdoe@corporate.com:97 read” will be generated. Or, if Jane files the message the following action can be sent: “jdoe@corporate.com:97 filed business”, etc.
In some embodiments, information about multiple actions are combined into a single message. For example, the unifier 114 might send messages to the address 104 every twenty minutes and at that point all unsent actions are sent. Each action can appear on a separate line of the message, e.g.:
jdoe@corporate.com:97 deleted
jdoe@wireless.com:32 read
jdoe@corporate.com:98 filed business
jdoe@corporate.com:90 replied
jdoe@wireless.com:30 forwarded
These actions can all be encapsulated inside a MIME section of an appropriate type to signal to the other unifier (e.g. the unifier 112) that the message requires processing. Alternatively, a mail header could indicate that the message requires processing.
Assuming the above five actions were sent in a message from the unifier 114 to the unifier 112, then when the message is received by the unifier 112, it will perform the listed actions on the messages on the handheld client 108. Thus, after receiving the actions and processing them, the messages on the handheld client 108 will look the same as the messages on the client 110. Further, all actions taken on the client 110 will be reflected on the handheld client 108.
The financial costs of the high cost communication channel 120 can be considered by examining one wireless plan offered by Palm.Net™ that could be accessible to the handheld client 108 for use as the high cost communication channel 120. The plan allows for 150 Kilobytes (KB) of transmission each month and charges $0.30 for each additional KB. For any significant volume of mail, relying on the high cost communication channel 120 for unification could quickly become prohibitively expensive. The based monthly amount of 150 KB would cover about 250 short messages—including the copies of messages sent by the unifier 114, the copies of mess ages sent by the unifier 112, and/or messages conveying actions from the unifier 112 and the unifier 114. Further, the battery consumption and other factors need to be considered in the cost.
Thus, the low cost communication channel 122 can reduce the overall cost of the unification process. When the handheld client 108 establishes the low cost communication channel 122, then the unifier 114 can unify the mail across the low cost communication channel 122 and remove any messages not yet received by the handheld client 108 from the mailbox 100 using the communication channel 118. Similarly, any pending messages that the unifier 112 has not yet transmitted over the high cost communication channel 120 can be sent to the unifier 114 via the low cost communication channel 122.
In this example, the five actions listed above sent in the message by the unifier 114 to the mailbox 100 have not yet been transferred to the handheld client 108. When the handheld client 108 connects to the client 110 over the low cost communication channel 122, the five actions are performed on the handheld client 108 and the message with the five actions is removed from the mailbox 100. This saves costs because the handheld client 108 will not retrieve messages it has already seen from the mailbox 100 when the high cost communication channel 120 is used next.
C. Process Flow
Next, at step 202, a distinguishing identifier is generated for the message by the unifier on that client (e.g. the unifier 114). The distinguishing identifier should be unique across the unified mailboxes. A combination of the address corresponding to the initial mailbox a message was received at with an incrementing counter can be used as the identifier. In other embodiments, headers in the message are used to generate the identifier.
At step 204, a copy, or a portion, of the message is sent to the second mailbox (e.g. the mailbox 100) with the identifier. In some embodiments, the identifier is included in a message header. In other embodiments, the identifier is included in a MIME section with a copy of the original message in another MIME section.
User defined criteria and system defined limits can control the message contents. For example, attachments might be removed and/or translated into alternate formats before sending the message to the second mailbox. Messages longer than a certain length can be reduced to a predetermined size and/or summarized automatically. Additionally, mail filters can be used such as only unifying messages with a certain priority and/or that meet a certain criteria. For example, only messages whose priority is set to urgent could be unified. Another example might be to only unify messages from senders in a list of important clients. In other embodiments, these filters might be used to control which messages are sent for delivery over the high cost communication channel 120. In this embodiment, when the low cost communication channel 122 is employed, the remaining messages can be unified.
The unifier (e.g. the unifier 114) can keep a record of identifiers for messages it sent over the communication channel 118 for delivery to the handheld client 108. In some embodiments, the unifier can periodically poll the mailbox 100 to determine which messages have been delivered to trim the record so it contains only those messages not yet delivered to the handheld client 108.
Similarly, the unifier 112 on the handheld computer can hold messages until either the high cost communication channel 120 or the low cost communication channel 122 can be used. In some embodiments, the unifier 112 can be set to always wait for access to the low cost communication channel 122 to send its messages—including messages with actions. This reduces use of the high cost communication channel 120. This may be acceptable because typically a user of the handheld client 108 will be able to use the low cost communication channel 122 when they are next accessing their mailbox 102 using the client 110. Therefore in this embodiment, a user might synchronize their handheld client 108 with their client 110 before proceeding to use the mail agent on the client 110.
Next, at step 302, a new message is created by the unifier (e.g. the unifier 114) with the identifier of the message on which the action was performed and a description of the action. In some embodiments, multiple actions are combined into one message as described above. On the handheld client 108, step 304 can be skipped because either the messages will be available on the handheld client 108 when the low cost communication channel 122 is used next, or they will have already been sent over the high cost communication channel 120 and received by the client 110. If the high cost communication channel 120 is not being used by the handheld client 108 for some or all messages, then for those messages step 302 can be skipped and step 304 will be performed after step 300.
Lastly, at step 304, the identifier and action are stored on the client in a record of actions. The contents of the mailbox 100 can be polled periodically by the unifier 114 in some embodiments of the invention to determined what actions have already been received by the handheld client 108 and to trim the record of actions.
At step 402, the messages from the mailbox 100 are used to unify the view of the messages in the handheld client 108. If a message in the mailbox 100 has no identifier, then the process of
For example, a new message sent directly to “jdoe@wireless.com” will undergo the process of
Next, at step 404, the handheld client 108 sends messages it has received but not already sent to the mailbox 102 over the high cost communication channel 404. This could include the copies of messages generated at step 204 and the messages with actions generated at step 302. In some embodiments, step 404 is skipped to reduce the usage of the high cost communication channel 120. In other embodiments, messages matching certain criteria are sent over the high cost communication channel 120, while others are held to be sent over the low cost communication channel 122.
Next, at step 502, the two views are unified. Messages, both the copies of messages with identifiers and messages with actions, sent by the client 110 to the mailbox 100 but not yet received by the handheld client 108 are sent over the low cost communication channel 122 to unify the message view on the handheld client 108. Similarly, messages on the handheld client 108 not yet sent to the client 110 are sent over the low cost communication channel 122 to unify the message view on the client 110.
Finally, at step 504, the unifier on the client 110 signals to the mailbox 100 to remove messages. This ensures that the next time the handheld client 108 retrieves messages over the high cost communication channel 120, unnecessary messages are not retrieved. This could take the form of a mail message from the unifier 114 indicating which messages are to be deleted or a proprietary signal between the unifier 114 and the mail server handling the mailbox 100. For example, a special port on the mail server might be designated to receive encrypted communications from the client 108 specifying the messages to be deleted. In other embodiments, the communication might simply indicate that the views are unified and to remove any messages from the mailbox 100 that originated from the unifier 114.
D. Alternative Embodiments
In some embodiments, the unifier 112 and the unifier 114 are implemented as one or more computer programs. The computer programs can be included in one or more computer usable media such as CD-ROMs, floppy disks, or other media.
Some embodiments of the invention are included in an electromagnetic wave form. The electromagnetic wave form comprises information such as the unifier 112 and the unifier 114. For example, the electromagnetic wave form could include signals sent over a network from a server computer to a client computer with the unifier 112 and/or the unifier 114.
E. Conclusion
The foregoing description of various embodiments of the invention has been presented for purposes of illustration and description. It is not intended to limit the invention to the precise forms disclosed. Many modifications and equivalent arrangements will be apparent.
This present application is a continuation of U.S. patent application Ser. No. 10/044,419, entitled “Method and Apparatus for Maintaining a Unified View of Multiple Mailboxes”, filed on Jan. 10, 2002, now U.S. Pat. No. 6,993,561 by Scott D. Lincke, et al.; which is a continuation of U.S. patent application Ser. No. 09/321,984, entitled “Method and Apparatus for Maintaining a Unified View of Multiple Mail Boxes”, filed on May 28, 1999, by Scott D. Lincke, et al., now U.S. Pat. No. 6,360,272 B1. This present application claims priority benefit of all the previously filed patent applications identified in this paragraph. The present application incorporates herein by reference all the previously filed patent applications identified in this paragraph.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4432057 | Daniell et al. | Feb 1984 | A |
| 4807182 | Queen | Feb 1989 | A |
| 4866611 | Cree et al. | Sep 1989 | A |
| 4875159 | Cary et al. | Oct 1989 | A |
| 4956809 | George et al. | Sep 1990 | A |
| 5001628 | Johnson et al. | Mar 1991 | A |
| 5065360 | Kelly | Nov 1991 | A |
| 5124909 | Blakely et al. | Jun 1992 | A |
| 5142619 | Webster, III | Aug 1992 | A |
| 5159592 | Perkins | Oct 1992 | A |
| 5187787 | Skeen et al. | Feb 1993 | A |
| 5210868 | Shimada et al. | May 1993 | A |
| 5237678 | Kuechler et al. | Aug 1993 | A |
| 5251291 | Malcolm | Oct 1993 | A |
| 5261045 | Scully et al. | Nov 1993 | A |
| 5261094 | Everson et al. | Nov 1993 | A |
| 5272628 | Koss | Dec 1993 | A |
| 5283887 | Zachery | Feb 1994 | A |
| 5301313 | Terada et al. | Apr 1994 | A |
| 5315709 | Alston, Jr. et al. | May 1994 | A |
| 5327555 | Anderson | Jul 1994 | A |
| 5333252 | Brewer, III et al. | Jul 1994 | A |
| 5339392 | Risberg et al. | Aug 1994 | A |
| 5339434 | Rusis | Aug 1994 | A |
| 5355476 | Fukumura | Oct 1994 | A |
| 5379057 | Clough et al. | Jan 1995 | A |
| 5392390 | Crozier | Feb 1995 | A |
| 5434994 | Shabeen et al. | Jul 1995 | A |
| 5442633 | Perkins et al. | Aug 1995 | A |
| 5463772 | Thompson et al. | Oct 1995 | A |
| 5475833 | Dauerer et al. | Dec 1995 | A |
| 5481721 | Serlet et al. | Jan 1996 | A |
| 5487100 | Kane | Jan 1996 | A |
| 5519606 | Frid-Nielsen et al. | May 1996 | A |
| 5537592 | King et al. | Jul 1996 | A |
| 5544356 | Robinson et al. | Aug 1996 | A |
| 5546539 | Pooling | Aug 1996 | A |
| 5566069 | Clark, Jr. et al. | Oct 1996 | A |
| 5572528 | Shuen | Nov 1996 | A |
| 5574859 | Yeh | Nov 1996 | A |
| 5592669 | Robinson et al. | Jan 1997 | A |
| 5598536 | Slaughter, III et al. | Jan 1997 | A |
| 5613108 | Morikawa | Mar 1997 | A |
| 5630081 | Rybicki et al. | May 1997 | A |
| 5647002 | Brunson | Jul 1997 | A |
| 5649195 | Scott et al. | Jul 1997 | A |
| 5666362 | Chen et al. | Sep 1997 | A |
| 5666530 | Clark et al. | Sep 1997 | A |
| 5673322 | Pepe et al. | Sep 1997 | A |
| 5684990 | Boothby | Nov 1997 | A |
| 5686530 | Halasa et al. | Nov 1997 | A |
| 5696702 | Skinner et al. | Dec 1997 | A |
| 5701423 | Crozier | Dec 1997 | A |
| 5701922 | Knipe, Jr. et al. | Dec 1997 | A |
| 5706509 | Man-Hak Tso | Jan 1998 | A |
| 5710922 | Alley et al. | Jan 1998 | A |
| 5724510 | Arndt et al. | Mar 1998 | A |
| 5727159 | Kikinis | Mar 1998 | A |
| 5727202 | Kucala | Mar 1998 | A |
| 5729452 | Smith et al. | Mar 1998 | A |
| 5737531 | Ehley | Apr 1998 | A |
| 5742668 | Pepe et al. | Apr 1998 | A |
| 5742820 | Perlman et al. | Apr 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5745689 | Yeager et al. | Apr 1998 | A |
| 5745699 | Lynn et al. | Apr 1998 | A |
| 5751960 | Matsunaga | May 1998 | A |
| 5758354 | Huang et al. | May 1998 | A |
| 5761439 | Kar et al. | Jun 1998 | A |
| 5812819 | Rodwin et al. | Sep 1998 | A |
| 5819172 | Campana, Jr. et al. | Oct 1998 | A |
| 5819284 | Farber et al. | Oct 1998 | A |
| 5835061 | Stewart | Nov 1998 | A |
| 5838252 | Kikinis | Nov 1998 | A |
| 5845282 | Alley et al. | Dec 1998 | A |
| 5857201 | Wright, Jr. et al. | Jan 1999 | A |
| 5864604 | Moen et al. | Jan 1999 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5889845 | Staples et al. | Mar 1999 | A |
| 5941954 | Kalajan | Aug 1999 | A |
| 5941956 | Shirakihara et al. | Aug 1999 | A |
| 5948059 | Woo et al. | Sep 1999 | A |
| 5951638 | Hoss et al. | Sep 1999 | A |
| 5964833 | Kikinis | Oct 1999 | A |
| 5966714 | Huang et al. | Oct 1999 | A |
| 5978837 | Foladare et al. | Nov 1999 | A |
| 5987508 | Agraharam et al. | Nov 1999 | A |
| 5995597 | Woltz et al. | Nov 1999 | A |
| 6018762 | Brunson et al. | Jan 2000 | A |
| 6023700 | Owens et al. | Feb 2000 | A |
| 6035104 | Zahariev | Mar 2000 | A |
| 6052563 | Macko | Apr 2000 | A |
| 6138146 | Moon et al. | Oct 2000 | A |
| 6233318 | Picard et al. | May 2001 | B1 |
| 6301245 | Luzeski et al. | Oct 2001 | B1 |
| 6542936 | Mayle et al. | Apr 2003 | B1 |
| 6778642 | Schmidt et al. | Aug 2004 | B1 |
| Number | Date | Country |
|---|---|---|
| 0 772 327 | May 1997 | EP |
| WO9619064 | Jun 1996 | WO |
| WO9733421 | Sep 1997 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20060059272 A1 | Mar 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10044419 | Jan 2002 | US |
| Child | 11267864 | US | |
| Parent | 09321984 | May 1999 | US |
| Child | 10044419 | US |
