Patent Grant
7209955
The present invention is directed toward the field of notifications for a mobile communications device.
The mobile data communication device is preferably coupled to the host system via a wireless network and one or more landline networks. Due to the bandwidth limitations of wireless networks, only a portion of a user-selected data item is generally redirected to the user's mobile device, with the user given the option of then retrieving the entire data item (or some other portion of the data item) from the host system.
Instead of warehousing (or storing) the user's data items at the host system and then “synchronizing” the mobile data communication device to data items stored at the host system when the mobile device requests that such items of information be communicated to it, the present invention employs a “push” paradigm that continuously packages and retransmits the user-selected items of information to the mobile data communication device in response to a triggering event detected at the host system. Wireless mobile data communications devices, especially those that can return a confirmation signal to the host that the pushed data has been received are especially well suited for this type of push paradigm.
Present systems and methods for replicating information from a host system to a user's mobile data communication device are typically “synchronization” systems in which the user's data items are warehoused (or stored) at the host system for an indefinite period of time and then transmitted in bulk only in response to a user request. In these types of systems and methods, when replication of the warehoused data items to the mobile device is desired, the user typically places the mobile device in an interface cradle that is electrically connected to the host system via some form of local, dedicated communication, such as a serial cable or an infrared or other type of wireless link. Software executing on the mobile data communication device then transmits commands via the local communications link to the host system to cause the host to begin transmitting the user's data items for storage in a memory bank of the mobile device. In these synchronization schemes, the mobile unit “pulls” the warehoused information from the host system in a batch each time the user desires to replicate information between the two devices. Therefore, the two systems (host and mobile) only maintain the same data items after a user-initiated command sequence that causes the mobile device to download the data items from the host system. A general problem with these synchronization systems is that the only time that the user data items are replicated between the host system and the mobile data communication device is when the user commands the mobile device to download or pull the user data from the host system. Five minutes later a new message could be sent to the user, but the user would not receive that message until the next time the user fetches the user data items. Thus, a user may fail to respond to an emergency update or message because the user only periodically synchronizes the system, such as once per day. Other problems with these systems include: (1) the amount of data to be reconciled between the host and the mobile device can become large if the user does not “synchronize” on a daily or hourly basis, leading to bandwidth difficulties, particularly when the mobile device is communicating via a wireless packet-switched network; and (2) reconciling large amounts of data, as can accrue in these batch-mode synchronization systems, can require a great deal of communication between the host and the mobile device, thus leading to a more complex, costly and energy-inefficient system. A more automated, continuous, efficient and reliable system of ensuring that user data items are replicated at the user's mobile device is therefore needed.
The user's mobile device is in many instances removably stored in a holster that is detachably connected to the user's belt or other piece of clothing. Traditionally, upon the detection of a new data item, an audible signal and/or the vibration of the device is the form of notification provided to the user. Such traditional notification is problematic at best and do not provide the user any flexibility for rapid decision-making. A heavy user of the system and method for pushing information from a host to a mobile communication device disclosed herein is quickly overcome with persistent data item notification during the busiest time periods in a business day. After receiving a traditional notification, the user reaches for his mobile device in the holster to examine the displayed data item associated with the notification. Frequent traditional notifications can become annoying to a heavy user; thereby causing the user to switch off the audible and/or vibrate notifications all together.
Traditional mobile communication devices, which implement the system and method of pushing information from a host as described herein, also lack the facility of an assistant or secretary to screen pages, emails, voice mails, etc. that arrive at the mobile communication device. In many ways, more work is created for the user when using such a device because a form of wireless umbilical cord extends from the user's host system to the user via the mobile communication device without the facility of a secretary or assistant to manage and/or screen the notifications. The user cannot differentiate unimportant data item notifications from those data items that are relevant or very important without having to commit to the physical action of reviewing the display of the device. An additional feature of the present invention is that the push paradigm, in combination with a return communications pathway, lends itself well to a system that permits a user to control remotely, through the user's mobile device, a number of aspects of the host system.
There remains a general need in this art for a system and method of continuously pushing user-selected data items (or certain portions of the selected data items) stored at a host system to a user's mobile data communication device.
There remains a more particular need for such a system and method where user-selected data items are continuously “pushed” from the host system to the mobile data communication device upon the occurrence of one or more user-defined triggering events.
There remains an additional need for such a system and method that provides flexibility in the types and quantities of user data items that are pushed from the host system to the mobile data communication device and that also provides flexibility in the configuration and types of events that can serve to trigger the redirection of the user data items.
There remains yet an additional need for such a system and method that can operate locally on a user's desktop PC or at a distance via a network server.
There remains still another need for such a system and method that provides for secure, transparent delivery of the user-selected data items from the host system to the mobile device.
There remains still another need for such a system and method that provides for notification in a user-selectable manner of user-selectable data items arriving at the mobile device.
There remains yet another need for such a system and method that provides for notification of mobile-specific event occurrences such as, but not limited to calendar event reminders and unsuccessful transmission of user data items originating from the mobile device.
There also remains still another need for such a system and method that provides for notification of user-selected data items from the host system to the mobile device in a userselectable manner that allows the user of the mobile communication device the quick and hands-free ability to determine whether or not to act on a notification.
There also remains yet another need to integrate secretarial-like features into a mobile communication device using the system and method of pushing information from a host to a mobile communication device.
The present invention overcomes the problems noted above and satisfies the needs in this field for a system and method of pushing user-selected data items from a host system to a user's mobile data communication device upon detecting the occurrence of one or more user-defined event triggers. As used in this application, the term host system refers to the computer where the redirector software is operating. In the preferred embodiment of the present invention, the host system is a user's desktop PC, although, alternatively, the host system could be a network server connected to the user's PC via a local-area network (“LAN)”, or could be any other system that is in communication with the user's desktop PC.
According to the present invention a system and method is provided such that an event-driven redirection computer program (“redirector program”) operating at the host system, which, upon sensing a particular user-defined event has occurred, characterizes user-selected data items and then redirects them from the host system to the user's mobile data communication device. s Upon arrival of the user-selected data items at the mobile data communication device, the present invention notifies the user in a user-selectable manner. In addition to the arrival of data items on the device, the occurrence of certain events that are specific to the mobile communication device and the transmission status of data items are events that are within the scope of the invention to notify the user.
A redirector program operating at the host system enables the user to redirect or mirror certain user-selected data items (or parts of data items) from the host system to the user's mobile data communication device upon detecting that one or more user-defined triggering events has occurred. Also operating at the host system are various sub-systems that can be configured to create triggering events, such as a screen saver sub-system or a keyboard sub-system, as well as sub-systems for repackaging the user's data items for transparent delivery to the mobile data device, such as a TCP/IP sub-system or one or more E-Mail sub-systems. Other sub-systems for creating triggering events and repackaging the user's data items could also be present at the host system. The host system also includes a primary memory store where the user's data items are normally stored.
Using the redirector program, the user can select certain data items types for redirection, such as E-mail messages, calendar events, meeting notifications, address entries, journal entries, personal reminders etc. Having selected the data items for redirection, the user can then configure one or more event triggers to be sensed by the redirector program to initiate redirection of the user data items. These user-defined trigger points (or event triggers) include external events, internal events and networked events. Examples of external events include: receiving a message from the user's mobile data communication device to begin redirection; receiving a similar message from some external computer; sensing that the user is no longer in the vicinity of the host system; or any other event that is external to the host system. Internal events could be a calendar alarm, screen saver activation, keyboard timeout, programmable timer, or any other user-defined event that is internal to the host system. Networked events are user-defined messages that are transmitted to the host system from another computer coupled to the host system via a network to initiate redirection. These are just some of the examples of the types of user-defined events that can trigger the redirector program to push data items from the host to the mobile device. Although in the preferred embodiment it is anticipated that the configuration that specifies which data items will be redirected and in what form will be set at the host system, it is within the scope of this invention that such configuration may be set or modified through data sent from the mobile communications device.
In addition to the functionality noted above, the redirector program provides a set of software-implemented control functions for determining the type of mobile data communication device and its address, for programming a preferred list of message types that are to be redirected, and for determining whether the mobile device can receive and process certain types of message attachments, such as word processor or voice attachments. The determination of whether a particular mobile device can receive and process attachments is initially configured by the user of that mobile device at the host system. This configuration can be altered on a global or per message basis by transmitting a command message from the mobile device to the host system. If the redirector is configured so that the mobile data device cannot receive and process word processor or voice attachments, then the redirector routes these attachments to an external machine that is compatible with the particular attachment, such as an attached printer or networked fax machine or telephone. Other types of attachments could be redirected to other types of external machines in a similar fashion, depending upon the capabilities of the mobile device. For example, if a user is traveling and receives a message with an attachment that the user's mobile device can process or display, the user may from a mobile communications device send a command message to the host system indicating that attachment is to be sent to a fax machine at a hotel where the user will be spending the evening. This enables the user to receive important E-mail attachments as long as the host system is provided with sufficient information about the destination where the attachment is to be forwarded.
Once an event has triggered redirection of the user data items, the host system then repackages these items in a manner that is transparent to the mobile data communication device, so that information on the mobile device appears similar to information on the user's host system. In one embodiment of the present invention, the repackaging of these items includes characterizing the data item type and the priority ranking associated therewith. As discussed above, data item types preferably include E-mail messages, calendar events, meeting notifications, address entries, journal entries, personal reminders, instant email notifications, etc. Priority rankings preferably include regular importance, very important and emergency. It is to be understood that it is clearly within the scope of the invention to expand or decrease the levels of priority rankings in an alternative embodiment of the invention. By characterizing the data item, the mobile data communication device can act on the characterization according to the user-selectable notification scheme as set forth on the mobile device, or alternatively as set forth on the host system. The preferred repackaging method includes wrapping the user data items in an E-mail envelope that corresponds to the address of the mobile data communication device, although, alternatively, other repackaging methods could be used with the present invention, such as special-purpose TCP/IP wrapping techniques, or other methods of wrapping the user selected data items. The repackaging preferably results in E-mail messages generated by the user from the mobile device to be transmitted from the host system, thus enabling the user to appear to have a single E-mail address, such that the recipients of messages sent from the mobile communications device do not know where the user was physically located when the message was first sent. The repackaging also permits both messages to the mobile device and sent from the mobile device to be encrypted and decrypted as well as compressed and decompressed.
In an alternative system and method, the redirector program executes on a network server, and the server is programmed to detect numerous redirection event triggers over the network from multiple user desktop computers coupled to the server via a LAN. The server can receive internal event triggers from each of the user desktops via the network, and can also receive external event triggers, such as messages from the users' mobile data communication devices. In response to receiving one of these triggers, the server redirects the user's data items to the proper mobile data communication device. The user data items and addressing information for a particular mobile device can be stored at the server or at the user's PC. Using this alternative configuration, one redirector program can serve a plurality of users. This alternative configuration could also include an internet- or intranet-based redirector program that could be accessible through a secure webpage or other user interface. The redirector program could be located on an Internet Service Provider's system and accessible only through the Internet. An example of an Internet-based redirector program can allow various Internet-based email and calendar event information companies to redirect their user data items to a particular mobile device. Instant message notifications are one such type of data items that would fall into this category.
In a preferred embodiment of the present invention, a client-based software program operates at the mobile communication device to manage and execute the user-selectable notification scheme (“notification module”). Preferably, the notification module is a component of the primary client software program residing on the mobile device that manages the redirected data items arriving and departing therefrom. In the preferred embodiment, the notification module is called upon on or before presenting any information on the display of the mobile device that is the result of a (1) data item arriving onto the mobile device from the wireless network, (2) data item event reminder, or (3) data item transmission status report. Collectively, these examples and others like them are herein referred to as “notifiable data items”.
In another alternative configuration of the present invention, a redirector program operates at both the host system and at the user's mobile data communication device. In this configuration, the user's mobile device operates similarly to the host system described below, and is configured in a similar fashion to push certain user-selected data items from the mobile device to the user's host system (or some other computer) upon detecting an event trigger at the mobile device. This configuration provides two-way pushing of information from the host to the mobile device and from the mobile device to the host.
The primary advantage of the present invention is that it provides a system and method for triggering the continuous and real-time redirection of user-selected data items from a host system to a mobile data communication device with user-selectable notification of the data items at the device. Other advantages of the present invention include: (1) flexibility in defining the types of user data to redirect, and in defining a preferred list of message types that are to be redirected or preferred senders whose messages are to be redirected; (2) flexibility in configuring the system to respond to numerous internal, external and networked triggering events; (3) transparent repackaging of the user data items in a variety of ways such that the mobile data communication device appears as though it were the host system; (4) integration with other host system components such as E-mail, TCP/IP, keyboard, screen saver, webpages and certain programs that can either create user data items or be configured to provide trigger points; (5) the ability to operate locally on a user's desktop system or at a distance via a network server; (6) flexibility in defining a user-selectable notification scheme to notify the user; (7)provides for notification in a user-selectable manner of user-selectable data items arriving at the mobile device; (8) provides for notification of mobile-specific event occurrences such as, but not limited to calendar event reminders and unsuccessful transmission of user data items originating from the mobile device; (9) provides for notification of user-selected data items from the host system to the mobile device in a user-selectable manner that allows the user of the mobile communication device the quick and hands-free ability to determine whether or not to act on a notification; and, (10) provides for integrated secretarial-like features into the mobile communication device. These are just a few of the many advantages of the present invention, as described in more detail below. As will be appreciated, the invention is capable of other and different embodiments, and its several details are capable of modifications in various respects, all without departing from the spirit of the invention. Accordingly, the drawings and description of the preferred embodiments set forth below are to be regarded as illustrative in nature and not restrictive.
The present invention satisfies the needs noted above as will become apparent from the following description when read in conjunction with the accompanying drawings wherein:
Referring now to the drawings,
In
In the example of
The preferred mobile data communication device 24 is a hand-held two-way wireless paging computer, a wirelessly enabled palm-top computer, a mobile telephone with data messaging capabilities, or a wirelessly enabled laptop computer, but could, alternatively be other types of mobile data communication devices capable of sending and receiving messages via a network connection 22. Although it is preferable for the system to operate in a two-way communications mode, certain aspects of the invention could be beneficially used in a “one and one-half” or acknowledgment paging environment, or even with a one-way paging system. The mobile data communication device 24 includes software program instructions that work in conjunction with the redirector program 12 to enable the seamless, transparent redirection of user-selected data items.
In an alternative embodiment of the present invention, not explicitly shown in the drawings, the mobile device 24 also includes a redirector program. In this embodiment, user selected data items can be replicated from the host to the mobile device and vice versa. The configuration and operation of the mobile device 24 having a redirector program is similar to that described herein with respect to
A user of the present invention can configure the redirector program 12 to push certain user-selected data items to the user's mobile data communication device 24 when the redirector 12 detects that a particular user-defined event trigger (or trigger point) has taken place. Userselected data items preferably include E-mail messages, calendar events, meeting notifications, address entries, journal entries, personal alerts, alarms, warnings, stock quotes, news bulletins, etc., but could, alternatively, include any other type of message that is transmitted to the host system 10, or that the host system 10 acquires through the use of intelligent agents, such as data that is received after the host system 10 initiates a search of a database or a website or a bulletin board. In some instances, only a portion of the data item is transmitted to the mobile device 24 in order to minimize the amount of data transmitted via the wireless network 22. In these instances, the mobile device 24 can optionally send a command message to the host system to receive more or all of the data item if the user desires to receive it.
Among the user-defined event triggers that can be detected by the redirector program 12 are in the preferred embodiment external events, internal events and networked events. External events preferably include: (1) receiving a command message (such as message C) from the user's mobile data communication device to begin redirection, or to execute some other command at the host, such as a command to enable the preferred list mode, or to add or subtract a particular sender from the preferred list; (2) receiving a similar message from some external computer; and (3) sensing that the user is no longer in the vicinity of the host system; although, alternatively, an external event can be any other detectable occurrence that is external to the host system. Internal events could be a calendar alarm, screen saver activation, keyboard timeout, programmable timer, or any other user-defined event that is internal to the host system. Networked events are user-defined messages that are transmitted to the host system from another computer coupled to the host system via a network to initiate redirection. These are just some of the events that could be used with the present invention to initiate replication of the user-selected data items from the host system 10 to the mobile device 24.
Assuming that the redirector program 12 is activated, and has been configured by the user (either through the sensing of an internal, network or external event) to replicate certain user data items (including messages of type A or C) to the mobile device 24, when the message A is received at the host system 10, the redirector program 12 detects its presence and prepares the message for redirection to the mobile device 24. In preparing the message for redirection, the redirector program 12 could compress the original message A, could compress the message header, or could encrypt the entire message A to create a secure link to the mobile device 24.
Also programmed into the redirector 12 is the address of the user's mobile data communication device 24, the type of device, and whether the device 24 can accept certain types of attachments, such as word processing or voice attachments. If the user's type of mobile device cannot accept these types of attachments, then the redirector 12 can be programmed to route the attachments to a fax or voice number where the user is located using an attached fax or voice machine 30.
The redirector may also be programmed with a preferred list mode that is configured by the user either at the host system 10, or remotely from the user's mobile data communication device by transmitting a command message C. The preferred list contains a list of senders (other users) whose messages are to be redirected or a list of message characteristics that determine whether a message is to be redirected. If activated, the preferred list mode causes the redirector program 12 to operate like a filter, only redirecting certain user data items based on whether the data item was sent from a sender on the preferred list or has certain message characteristics that if present will trigger or suppress redirection of the message. In the example of
In yet another aspect of the present invention, a description of the notification system and method is now further described. In general, each data item that is redirected to the mobile preferably is characterized as to the data item type and the priority ranking associated therewith. Data item types preferably include E-mail messages, calendar events, meeting notifications, address entries, journal entries, personal reminders, instant email notifications, etc. Priority rankings preferably include at least three different levels of importance, namely regular importance, very high importance and emergency. It is to be understood that it is clearly within the scope of the invention to expand or decrease the levels of priority rankings in an alternative embodiment of the invention. By characterizing the-data-item, the mobile data communication device can act on the characterization according to a user-selectable notification scheme. In addition to the user-selectable notification scheme, the mobile preferably executes a variety of secretary-like actions. The collective features of the present invention provide the mobile the ability to advantageously operate very much like a virtual secretary thereby providing many of the aforesaid advantages of the present invention.
Characterization preferably takes place at the host system. In a second embodiment, the characterization may take place at the mobile. In a third embodiment, a first portion of characterization may take place at the host system and a second portion of characterization may take place at the mobile. In this third embodiment, the user can set which of the two characterizations can take precedence (ie. which wins in a conflict). In the preferred embodiment, the characterization as to the type of the data item and as to the priority ranking are undertaken at the host system. However, the user, preferably, may override the host-side characterization settings regarding the priority rankings at the mobile. It is to be understood that it is preferable that the host system and the mobile are initially synchronized at either an initial hard link or via an over-the-air synchronization to match characterization protocols and notification schemes.
By way of example of the characterization process, after step 68 in
In addition to characterization, the present invention utilizes what is known herein as a “notification scheme”. The notification scheme is a plurality of filtering and action rules that are applied to a notifiable data item using some or all of the characterization of the data item. In the preferred embodiment, a set of default rules will be available in the interim for the user until he gets an opportunity to personalize his notification scheme. In the preferred embodiment, there is a plurality of notification schemes on the device, each customizable for the user's benefit. As an example, a first notification scheme may apply only to meeting requests from a certain group of individuals, while a second notification scheme may apply only to the failure of any data items transmitted from the mobile. A third notification scheme may apply to email messages from a certain sender. The infinite variety of combinations will be appreciated with the following description.
The notification scheme provides the user with a plurality of notification alerts such as, but not limited to, audible, visual and vibrating alerts. Continuing with the example, the user would then select whether any reminders are necessary. If so, the user may select the same alert scheme earlier selected or alternatively, choose a different style of reminder. In this manner, the level of intrusion to the user due to the notification may be minimized and yet still be beneficial to the user. To illustrate this point, take for example a calendar event such as a meetings that include party Y are to be audibly alerted, but email message from the same person is just visually alerted.
As a first step 222, in the notification scheme screen, the user is prompted on whether the current scheme is to be party-specific 224 or to be generally applied 226. When the party-specific option 224 is activated, the notification scheme only applies to certain predetermined individuals or groups of individuals identified in notifiable data items. User may select from pre-existing individuals in the mobile's address book or create new ones. User may then set parameters of where the individual must be identified. For instance, in the preferred embodiment, the user may require that the individual be identified in any number of ways including at least one of: (1) senders of the data items, (2) attendees of calendar events, (3) individuals listed in the cc: of an email message, or (4) recipients of the data items. In the preferred embodiment, a variety of combinations are possible and user-selectable. In the alternative, the user may choose option 226 such that the notification scheme 220 applies generally without reference to the party identified in the notifiable data item.
At step 228, the user is prompted to choose from a plurality of data item types. By choosing at least one of the plurality of data item types 230, 232, 234, the notification scheme is restricted in its applications to those data items types selected. It is preferable that a user restriction selection may initiate the user to further restrict in sub-selections. In this manner, the notification scheme may be more finely tuned. For example, in the preferred embodiment, if the user selects email message 230 as a data item restriction to be applied, the user is further prompted to select from one of at least, preferably, three sub-choices, namely: inbound email messages 236, outbound email messages 238, or transmission status of email messages 240.
As a pre-step before selecting the alert at step 242, the user is prompted as to the priority ranking the data item must have before the alert is executed. Such ranking restriction is designated as steps 241, 261 and 271. Although not fully illustrated in
At step 242, the user is prompted to choose from a plurality of alert types, including preferably, audible 244, visual 246 and vibrate 248 signals. As illustrated in
Returning back to
The virtual secretary may be invoked in a number of ways. For example, a message arrives having an emergency ranking, the mobile notifies the user accordingly, the users reviews the message, upon cursoring to the end of the message, software on the mobile either (1) prompts the user to reply to the sender, or (2) opens a new message to reply to the sender. In this manner, time which may be of the essence is advantageously saved and navigation through GUls are avoided for a response.
To further illustrate another feature of the virtual secretary described in the present invention, take for example, an attachment to an email message arrives at the handheld that is not openable or viewable at the mobile. In one embodiment of the present invention, the mobile device will upon or while contemporaneously acting on the user-selected notification scheme will locate a suitable peripheral or other device that will allow the attachment to be presented to the user. More specifically, the software on the mobile will, upon detection of an attachment not presentable to the user, automatically wirelessly transmit an attachment agent from the handheld through a cooperating wireless LAN or WAN. The attachment agent will seek and locate a peripheral or device that is willing and capable to open and present the attachment for the user. The agent will use a variety of user-selectable parameters to determine the most suitable external device to present the attachment. Such parameters include what will constitute a reasonable distance for the user to walk (i.e anywhere on the same floor of an office building, but no further than 250 metres). Upon successfully seek and locate, the agent will return to the device, or alternatively, some form of acknowledgment will be reported to the mobile about the opportunity and details regarding logistics to present the attachment to the user. At that time the user can choose to either view the attachment at the suggested external device or ignore the same.
In another embodiment of the present invention, the mobile modifies the audible alert of notifiable data-items according to the noise level around the user.
After the redirector has determined that a particular message should be redirected, and it has prepared the message for redirection, the software 12 then sends the message A to a secondary memory store located in the mobile device 24, using whatever means are necessary. In the preferred embodiment this method is to send the message A back over the LAN 14, WAN 18, and through the wireless gateway 20 to the mobile data communication device 24. In doing so, the redirector preferably repackages message A as an E-mail with an outer envelope B that contains the addressing information of the mobile device 24, although alternative repackaging techniques and protocols could be used, such as a TCP/EP repackaging and delivery method (most commonly used in the alternative server configuration shown in FIG.2). The wireless gateway 20 it, requires this outer envelope information B in order to know where to send the redirected message A. Once the message (A in B) is received by the mobile device 24, the outer envelope B is removed and the original message A is placed in the secondary memory store within the mobile device 24. By repackaging and removing the outer envelope in this manner, the present invention causes the mobile computer 24 to appear to be at the same physical location as the host system 10, thus creating a transparent system.
In the case where message C is representative of an external message from a computer on the Internet 18 to the host system 10, and the host 10 has been configured to redirect messages of type C, then in a similar manner to message A, message C would be repackaged with an outer envelope B and transmitted to the user's mobile device 24. In the case where message C is representative of a command message from the user's mobile device 24 to the host system 10, the command message C is not redirected, but is acted upon by the host system 10.
If the redirected user data item is an E-mail message, as described above, the user at the mobile device 24 sees the original subject, sender's address, destination address, carbon copy and blind carbon copy. When the user replies to this message, or when the user authors a new message, the software operating at the mobile device 24 adds a similar outer envelope to the reply message (or the new message) to cause the message to be routed first to the user's host system 10, which then removes the outer envelope and redirects the message to the final destination, such as back to computer 26. In the preferred embodiment, this results in the outgoing redirected message from the user's host system 10 being sent using the E-mail address of the host mailbox, rather than the address of the mobile device, so that it appears to the recipient of the message that the message originated from the user's desktop system 10 rather than the mobile data communication device. Any replies to the redirected message will then be sent to the desktop system 10, which if it is still in redirector mode, will repackage the reply and resend it to the user's mobile data device, as described above.
In this alternative configuration, server 11 preferably maintains a user profile for each user's desktop system 10, 26, 28, including information such as whether a particular user can have data items redirected, which types of message and information to redirect, what events will trigger redirection, the address of the users' mobile data communication device 24, the type of mobile device, and the user's preferred list, if any. The event triggers are preferably detected at the user's desktop system 10, 26, 28 and can be any of the external, internal or network events listed above. The desktop systems 10, 26, 28 preferably detect these events and then transmit a message to the server computer 11 via LAN 14 to initiate redirection. Although the user data items are preferably stored at the server computer 11 in this embodiment, they could, alternatively, be stored at each user's desktop system 10, 26, 28, which would then transmit them to the server computer 11 after an event has triggered redirection.
As shown in
As described above with reference to
Turning now to
The desktop system 10 is connected to LAN 14, and can send and receive data, messages, signals, event triggers, etc., to and from other systems connected to the LAN 14 and to external networks 18, 22, such as the Internet or a wireless data network, which are also coupled to the LAN 14. In addition to the standard hardware, operating system, and application programs associated with a typical microcomputer or workstation, the desktop system 10 includes the redirector program 12, a TCP/IP sub-system 42, an E-mail sub-system 44, a primary data storage device 40, a screen saver sub-system 48, and a keyboard sub-system 46. The TCP/IP and E-mail subsystems 42, 44 are examples of repackaging systems that can be used to achieve the transparency of the present invention, and the screen saver and keyboard sub-systems 46, 48 are examples of event generating systems that can be configured to generate event messages or signals that trigger redirection of the user selected data items.
The method steps carried out by the redirector program 12 are described in more detail in FIG. 4. The basic functions of this program are: (1) configure and setup the user-defined event trigger points that will start redirection; (2) configure the types of user data items for redirection and optionally configure a preferred list of senders whose messages are to be redirected; (3) configure the type and capabilities of the user's mobile data communication device; (4) receive messages and signals from the repackaging systems and the event generating systems; and (5) command and control the redirection of the user-selected data items to the mobile data communication device via the repackaging systems. Other functions not specifically enumerated could also be integrated into this program.
The E-Mail sub-system 44 is the preferred link to repackaging the user-selected data items for transmission to the mobile data communication device 24, and preferably uses industry standard mail protocols, such as SMTP, POP, IMAP, MIME and RFC-822, to name but a few. The E-Mail sub-system 44 can receive messages A from external computers on the LAN 14, or can receive messages C from some external network such as the Internet 18 or a wireless data communication network 22, and stores these messages in the primary data store 40. Assuming that the redirector 12 has been triggered to redirect messages of this type, the redirector detects the presence of any new messages and instructs the E-Mail system 44 to repackage the message by placing an outer wrapper B about the original message A (or C), and by providing the addressing information of the mobile data communication device 24 on the outer wrapper B. As noted above, this outer wrapper B is removed by the mobile device 24, and the original message A (or C) is then recovered, thus making the mobile device 24 appear to be the desktop system 10.
In addition, the E-Mail sub-system 44 receives messages back from the mobile device 24 having an outer wrapper with the addressing information of the desktop system 10, and strips this information away so that the message can be routed to the proper sender of the original message A (or C). The E-Mail sub-system also receives command messages C from the mobile device 24 that are directed to the desktop system 10 to trigger redirection or to carry out some other function. The functionality of the E-Mail sub-system 44 is controlled by the redirector program 12.
The TCP/IP sub-system 42 is an alternative repackaging system. It includes all of the functionality of the E-Mail sub-system 44, but instead of repackaging the user-selected data items as standard E-mail messages, this system repackages the data items using special-purpose TCP/IP packaging techniques. This type of special-purpose sub-system is useful in situations where security and improved speed are important to the user. The provision of a special-purpose wrapper that can only be removed by special software on the mobile device 24 provides the added security, and the bypassing of E-mail store and forward systems can improve speed and real-time delivery.
As described previously, the present invention can be triggered to begin redirection upon detecting numerous external, internal and networked events, or trigger points. Examples of external events include: receiving a command message from the user's mobile data communication device 24 to begin redirection; receiving a similar message from some external computer; sensing that the user is no longer in the vicinity of the host system; or any other event that is external to the host system. Internal events could be a calendar alarm, screen saver activation, keyboard timeout, programmable timer, or any other user-defined event that is internal to the host system. Networked events are user-defined messages that are transmitted to the host system from another computer that is connected to the host system via a network to initiate redirection.
The screen saver and keyboard sub-systems 46, 48 are examples of systems that are capable of generating internal events. Functionally, the redirector program 12 provides the user with the ability to configure the screen saver and keyboard systems so that under certain conditions an event trigger will be generated that can be detected by the redirector 12 to start the redirection process. For example, the screen saver system can be configured so that when the screen saver is activated, after, for example, 10 minutes of inactivity on the desktop system, an event trigger is transmitted to the redirector 12, which starts redirecting the previously selected user data items. In a similar manner the keyboard sub-system can be configured to generate event triggers when no key has been depressed for a particular period of time, thus indicating that redirection should commence. These are just two examples of the numerous application programs and hardware systems internal to the host system 10 that can be used to generate internal event triggers.
Once the redirector program is configured 50, the trigger points (or event triggers) are enabled at step 52. The program 12 then waits 56 for messages and signals 54 to begin the redirection process. A message could be an E-Mail message or some other user data item than may have been selected for redirection, and a signal could be a trigger signal, or could be some other type of signal that has not been configured as an event trigger. When a message or signal is detected, the program determines 58 whether it is one of the trigger events that has been configured by the user to signal redirection. If so, then at step 60 a trigger flag is set, indicating that subsequently received user data items (in the form of messages) that have been selected for redirection should be pushed to the user's mobile data communication device 24.
If the message or signal 54 is not a trigger event, the program then determines at steps 62, 68 and 66 whether the message is, respectively, a system alarm 62, an E-Mail message 64, or some other type of information that has been selected for redirection. If the message or signal is none of these three items, then control returns to step 56, where the redirector waits for additional messages 54 to act upon. If, however the message is one of these three types of information, then the program 12 determines, at step 68, whether the trigger flag has been set, indicating that the user wants these items redirected to the mobile device. If the trigger flag is set, then at step 70, the redirector 12 causes the repackaging system (E-Mail or TCP/IP) to add the outer envelope to the user data item, and at step 72 the repackaged data item is then redirected to the user's mobile data communication device 24 via LAN 14, WAN 18, wireless gateway 20 and wireless network 22. At step 72, the repackaging may also include the marking of the data item as to its data item type and/or priority level. Control then returns to step 56 where the program waits for additional messages and signals to act upon. Although not shown explicitly in
At step 82, the mobile device waits for messages and signals 84 to be generated or received. Assuming that the redirector software 12 operating at the user's desktop system 10 is configured to redirect upon receiving a message from the user's mobile device 24, at step 86, the user can decide to generate a command message that will start redirection. If the user does so, then at step 88 the redirection message is composed and sent to the desktop system 10 via the wireless network 22, through the wireless gateway 20, via the Internet 18 to the LAN 14, and is finally routed to the desktop machine 10. In this situation where the mobile device 24 is sending a message directly to the desktop system 10, no outer wrapper is added to the message (such as message C in FIGS. 1 and 2). In addition to the redirection signal, the mobile device 24 could transmit any number of other commands to control the operation of the host system, and in particular the redirector program 12. For example, the mobile 24 could transmit a command to put the host system into the preferred list mode, and then could transmit additional commands to add or subtract certain senders from the preferred list. In this manner, the mobile device 24 can dynamically limit the amount of information being redirected to it by minimizing the number of senders on the preferred list. Other example commands include: (1) a message to change the configuration of the host system to enable the mobile device 24 to receive and process certain attachments; (2) a message to instruct the host system to redirect an entire data item to the mobile device in the situation where only a portion of a particular data item has been redirected; (3) a message to instruct the host system to modify the priority level associated with classes or subclasses of data items.
Turning back to
In an alternative embodiment of the invention relating to the notification method and system of the present invention, following step 96 or step 92, control passes to step 200, which notifies the user of the data item according the present invention.
An emergency notification setting is defaulted as true. When the setting remains in this state, the emergency notification is useful in the instance where the user chooses to power down his entire mobile device ?.4 or just the radio component of the device. In such an instance, the assumption is that the user still desires to receive only extremely important data items, hence the name “emergency notification”. In such an occurrence, a data item having a command associated therewith re-activates the mobile device only long enough to be received by the mobile device and powers down the radio component of the mobile device promptly thereafter so as to prevent any other transmission from arriving or departing from the device.
The present invention provides flexibility to the user by providing the user the capability to predetermine a set of notification rules. For instance, depending on the type of data item received by the notification module, the user may chose the notifcation module to act differently. In the preferred embodiment, notification types include visual, vibrate and audible notifications and within theses types of notifications there are sub-types of notifications such as tune 1, tune 2 and tune 3 for the audible signal notification. The user has control over this selection via a user interface (not shown) on the device.
If the mobile device 24 determines that a message has not been received at step 90, then control passes to step 100, where the mobile determines whether there is a message to send. If not, then the mobile unit returns to step 82 and waits for additional messages or signals. If there is at least one message to send, then at step 102 the mobile determines whether it is a reply message to a message that was received by the mobile unit. If the message to send is a reply message, then at step 108, the mobile determines whether the desktop redirection flag is on for this message. If the redirection flag is not on, then at step 106 the reply message is simply transmitted from the mobile device to the destination address via the wireless network 22. If, however, the redirection flag is on, then at step 110 the reply message is marked as to its data item type and priority level and repackaged with the outer envelope having the addressing information of the user's desktop system 10, and the repackaged message is then transmitted to the desktop system 10 at step 106. As described above, the redirector program 12 executing at the desktop system then strips the outer envelope and routes the reply message to the appropriate destination address using the address of the desktop system as the “from” field, so that to the recipient of the redirected message, it appears as though it originated from the user's desktop system rather than the mobile data communication device.
If, at step 102, the mobile determines that the message is not a reply message, but an original message, then control passes to step 104, where the mobile determines if the user is using the redirector software 12 at the desktop system 10, by checking the mobile unit's configuration. If the user is not using the redirector software 12, then the message is simply transmitted to the destination address at step 106. If, however, the mobile determines that the user is using the redirector software 12 at the desktop system 10, then control passes to step 110, where the message is marked for data item type and priority level and the outer envelope is added to the message. The repackaged original message is then transmitted to the desktop system 10 at step 106, which, as described previously, strips the outer envelope and routes the message to the correct destination. Following transmission of the message at step 106, control of the mobile returns to step 82 and waits for additional messages or signals.
Having described in detail the preferred embodiments of the present invention, including the preferred methods of operation, it is to be understood that this operation could be carried out with different elements and steps. This preferred embodiment is presented only by way of example and is not meant to limit the scope of the present invention which is defined by the following claims.
This application is a continuation-in-part of U.S. utility application Ser. No. 09/087,623, entitled System and Method for Pushing Information from a Host System to a Mobile Data Communication Device, filed May 29, 1998, and assigned to the assignee of the present invention, now U.S. Pat. No. 6,219,694.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4106060 | Chapman, Jr. | Aug 1978 | A |
| 4438433 | Smoot et al. | Mar 1984 | A |
| 4558454 | Hills et al. | Dec 1985 | A |
| 4644351 | Zabarsky et al. | Feb 1987 | A |
| 4695880 | Johnson et al. | Sep 1987 | A |
| 4697281 | O'Sullivan | Sep 1987 | A |
| 4713780 | Schultz et al. | Dec 1987 | A |
| 4837798 | Cohen et al. | Jun 1989 | A |
| 4837800 | Freeburg et al. | Jun 1989 | A |
| 4856047 | Saunders | Aug 1989 | A |
| 4928096 | Leonardo et al. | May 1990 | A |
| 4951044 | Nelson et al. | Aug 1990 | A |
| 4980907 | Raith et al. | Dec 1990 | A |
| 5008926 | Misholi | Apr 1991 | A |
| 5043721 | May | Aug 1991 | A |
| 5058431 | Karwacki | Oct 1991 | A |
| 5086502 | Malcolm | Feb 1992 | A |
| 5125021 | Lebowitz | Jun 1992 | A |
| 5127041 | O'Sullivan | Jun 1992 | A |
| 5136291 | Teague | Aug 1992 | A |
| 5157660 | Kuwahara et al. | Oct 1992 | A |
| 5159592 | Perkins | Oct 1992 | A |
| 5177680 | Tsukino et al. | Jan 1993 | A |
| 5181200 | Harrison | Jan 1993 | A |
| 5265033 | Vajk et al. | Nov 1993 | A |
| 5283887 | Zachery | Feb 1994 | A |
| 5293250 | Okumura et al. | Mar 1994 | A |
| 5299255 | Iwaki et al. | Mar 1994 | A |
| 5307059 | Connary et al. | Apr 1994 | A |
| 5313582 | Hendel et al. | May 1994 | A |
| 5315635 | Kane et al. | May 1994 | A |
| 5333152 | Wilber | Jul 1994 | A |
| 5333266 | Boaz et al. | Jul 1994 | A |
| 5392390 | Crozier | Feb 1995 | A |
| 5406557 | Baudoin | Apr 1995 | A |
| 5410543 | Seitz et al. | Apr 1995 | A |
| 5416473 | Dulaney, III et al. | May 1995 | A |
| 5436960 | Campana, Jr. et al. | Jul 1995 | A |
| 5438611 | Campana, Jr. et al. | Aug 1995 | A |
| 5452356 | Albert | Sep 1995 | A |
| 5479472 | Campana, Jr. et al. | Dec 1995 | A |
| 5493692 | Theimer et al. | Feb 1996 | A |
| 5495484 | Self et al. | Feb 1996 | A |
| 5557659 | Hyde-Thomson | Sep 1996 | A |
| 5559800 | Mousseau et al. | Sep 1996 | A |
| 5572528 | Shuen | Nov 1996 | A |
| 5579472 | Keyworth, II et al. | Nov 1996 | A |
| 5588009 | Will | Dec 1996 | A |
| 5598536 | Slaughter, III et al. | Jan 1997 | A |
| 5603054 | Theimer et al. | Feb 1997 | A |
| 5604491 | Coonley et al. | Feb 1997 | A |
| 5604788 | Tett | Feb 1997 | A |
| 5625670 | Campana, Jr. et al. | Apr 1997 | A |
| 5627829 | Gleeson et al. | May 1997 | A |
| 5630060 | Tang et al. | May 1997 | A |
| 5633810 | Mandal et al. | May 1997 | A |
| 5638450 | Robson | Jun 1997 | A |
| 5641946 | Campana, Jr. et al. | Jun 1997 | A |
| 5666530 | Clark et al. | Sep 1997 | A |
| 5666553 | Corzier | Sep 1997 | A |
| 5673322 | Pepe et al. | Sep 1997 | A |
| 5705995 | Laflin et al. | Jan 1998 | A |
| 5727202 | Kucala | Mar 1998 | A |
| 5729735 | Meyering | Mar 1998 | A |
| 5737531 | Ehley | Apr 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5751960 | Matsunaga | May 1998 | A |
| 5751971 | Dobbins et al. | May 1998 | A |
| 5754954 | Cannon et al. | May 1998 | A |
| 5757901 | Hiroshige | May 1998 | A |
| 5761416 | Mandal et al. | Jun 1998 | A |
| 5764639 | Staples et al. | Jun 1998 | A |
| 5765170 | Morikawa | Jun 1998 | A |
| 5781614 | Brunson | Jul 1998 | A |
| 5781901 | Kuzma | Jul 1998 | A |
| 5790790 | Smith et al. | Aug 1998 | A |
| 5790974 | Tognazzini | Aug 1998 | A |
| 5796806 | Birckbichler | Aug 1998 | A |
| 5812671 | Ross | Sep 1998 | A |
| 5812819 | Rodwin et al. | Sep 1998 | A |
| 5813016 | Suminmto | Sep 1998 | A |
| 5815081 | Motohashi | Sep 1998 | A |
| 5819172 | Camapana, Jr. et al. | Oct 1998 | A |
| 5819284 | Farber et al. | Oct 1998 | A |
| 5822434 | Caronni et al. | Oct 1998 | A |
| 5826062 | Fake, Jr. et al. | Oct 1998 | A |
| 5838252 | Kikinis | Nov 1998 | A |
| 5838926 | Yamagishi | Nov 1998 | A |
| 5844969 | Goldman et al. | Dec 1998 | A |
| 5850219 | Kumomura | Dec 1998 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5867660 | Schmidt et al. | Feb 1999 | A |
| 5878434 | Draper et al. | Mar 1999 | A |
| 5900875 | Haitani et al. | May 1999 | A |
| 5903723 | Beck et al. | May 1999 | A |
| 5905777 | Foladare et al. | May 1999 | A |
| 5917629 | Hortensius et al. | Jun 1999 | A |
| 5928329 | Clark et al. | Jul 1999 | A |
| 5937161 | Mulligan et al. | Aug 1999 | A |
| 5941956 | Shirakihara et al. | Aug 1999 | A |
| 5943426 | Frith et al. | Aug 1999 | A |
| 5953322 | Kimball | Sep 1999 | A |
| 5960406 | Rasansky et al. | Sep 1999 | A |
| 5961590 | Mendez et al. | Oct 1999 | A |
| 5966663 | Gleason | Oct 1999 | A |
| 5968131 | Mendez et al. | Oct 1999 | A |
| 5969636 | Parvulescu et al. | Oct 1999 | A |
| 5973612 | Deo et al. | Oct 1999 | A |
| 5974180 | Schwendeman | Oct 1999 | A |
| 5974238 | Chase, Jr. | Oct 1999 | A |
| 5978689 | Tuoriniemi et al. | Nov 1999 | A |
| 5978837 | Foladare et al. | Nov 1999 | A |
| 5983073 | Ditzik | Nov 1999 | A |
| 5987508 | Agraharam et al. | Nov 1999 | A |
| 5995597 | Woltz et al. | Nov 1999 | A |
| 6000000 | Hawkins et al. | Dec 1999 | A |
| 6002769 | McGough | Dec 1999 | A |
| 6006274 | Hawkins et al. | Dec 1999 | A |
| 6014429 | LaPorta et al. | Jan 2000 | A |
| 6018762 | Brunson et al. | Jan 2000 | A |
| 6018782 | Hartmann | Jan 2000 | A |
| 6023000 | Fritz-Langhals et al. | Feb 2000 | A |
| 6023700 | Owens et al. | Feb 2000 | A |
| 6023708 | Mendez et al. | Feb 2000 | A |
| 6034621 | Kaufman | Mar 2000 | A |
| 6044205 | Reed et al. | Mar 2000 | A |
| 6052442 | Cooper et al. | Apr 2000 | A |
| 6052563 | Macko | Apr 2000 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6058431 | Srisuresh et al. | May 2000 | A |
| 6073165 | Narasimhan et al. | Jun 2000 | A |
| 6078826 | Croft et al. | Jun 2000 | A |
| 6078921 | Kelley | Jun 2000 | A |
| 6084969 | Wright et al. | Jul 2000 | A |
| 6085192 | Mendez et al. | Jul 2000 | A |
| 6085232 | Kikinis | Jul 2000 | A |
| 6091951 | Sturniolo et al. | Jul 2000 | A |
| 6092114 | Shaffer et al. | Jul 2000 | A |
| 6092191 | Shimbo et al. | Jul 2000 | A |
| 6101531 | Eggleston et al. | Aug 2000 | A |
| 6115394 | Balachandran et al. | Sep 2000 | A |
| 6115736 | Devarakonda et al. | Sep 2000 | A |
| 6119167 | Boyle et al. | Sep 2000 | A |
| 6125281 | Wells et al. | Sep 2000 | A |
| 6125369 | Wu et al. | Sep 2000 | A |
| 6130892 | Short et al. | Oct 2000 | A |
| 6138089 | Guberman | Oct 2000 | A |
| 6138146 | Moon et al. | Oct 2000 | A |
| 6141690 | Weiman | Oct 2000 | A |
| 6157318 | Minata | Dec 2000 | A |
| 6157630 | Adler et al. | Dec 2000 | A |
| 6157950 | Krishman | Dec 2000 | A |
| 6163274 | Llndgren | Dec 2000 | A |
| 6167379 | Dean et al. | Dec 2000 | A |
| 6178331 | Holmes et al. | Jan 2001 | B1 |
| 6185551 | Birrell et al. | Feb 2001 | B1 |
| 6185603 | Henderson et al. | Feb 2001 | B1 |
| 6202085 | Benson et al. | Mar 2001 | B1 |
| 6203192 | Fortman | Mar 2001 | B1 |
| 6205448 | Kruglikov et al. | Mar 2001 | B1 |
| 6208996 | Ben-Shachar et al. | Mar 2001 | B1 |
| 6219694 | Lazaridis et al. | Apr 2001 | B1 |
| 6233341 | Riggins | May 2001 | B1 |
| 6240088 | Gayton et al. | May 2001 | B1 |
| 6249820 | Dobbins et al. | Jun 2001 | B1 |
| 6256666 | Singhal | Jul 2001 | B1 |
| 6272545 | Flanagin et al. | Aug 2001 | B1 |
| 6275848 | Arnold | Aug 2001 | B1 |
| 6275850 | Beyda et al. | Aug 2001 | B1 |
| 6311282 | Nelson et al. | Oct 2001 | B1 |
| 6313734 | Weiss et al. | Nov 2001 | B1 |
| 6314108 | Ramasubramani et al. | Nov 2001 | B1 |
| 6330244 | Swartz et al. | Dec 2001 | B1 |
| 6333973 | Smith et al. | Dec 2001 | B1 |
| 6351764 | Voticky et al. | Feb 2002 | B1 |
| 6356956 | Deo et al. | Mar 2002 | B1 |
| 6360272 | Lincke et al. | Mar 2002 | B1 |
| 6370566 | Discolo et al. | Apr 2002 | B2 |
| 6389455 | Fuisz | May 2002 | B1 |
| 6400810 | Skladman et al. | Jun 2002 | B1 |
| 6401113 | Lazaridis et al. | Jun 2002 | B2 |
| 6449287 | Leuca et al. | Sep 2002 | B1 |
| 6505214 | Sherman et al. | Jan 2003 | B1 |
| 6580787 | Akhteruzzaman et al. | Jun 2003 | B1 |
| 6611358 | Narayanaswamy | Aug 2003 | B1 |
| 6701378 | Gilhuly et al. | Mar 2004 | B1 |
| 20010001552 | Vong | May 2001 | A1 |
| 20010015977 | Joansson | Aug 2001 | A1 |
| 20010029531 | Ohta | Oct 2001 | A1 |
| 20010040693 | Saito et al. | Nov 2001 | A1 |
| 20010042093 | Shirai et al. | Nov 2001 | A1 |
| 20010045885 | Tett | Nov 2001 | A1 |
| 20010054072 | Discolo et al. | Dec 2001 | A1 |
| 20020010748 | Kobayashi et al. | Jan 2002 | A1 |
| 20020059380 | Biliris et al. | May 2002 | A1 |
| 20030097361 | Huang et al. | May 2003 | A1 |
| Number | Date | Country |
|---|---|---|
| 7843498 | Jul 1997 | AU |
| 0 001 552 | May 1979 | EP |
| 0 617 373 | Apr 1994 | EP |
| 0617373 | Sep 1994 | EP |
| 0 736 989 | Sep 1996 | EP |
| 0736989 | Oct 1996 | EP |
| 0772327 | May 1997 | EP |
| 0777394 | Jun 1997 | EP |
| 0788287 | Aug 1997 | EP |
| 09214556 | Aug 1997 | EP |
| 0793387 | Sep 1997 | EP |
| 0 825 788 | Feb 1998 | EP |
| 0825788 | Feb 1998 | EP |
| 0838774 | Apr 1998 | EP |
| 0838934 | Apr 1998 | EP |
| 0772327 | Feb 1999 | EP |
| 0 918 417 | May 1999 | EP |
| 0 930 766 | Jul 1999 | EP |
| 0930766 | Jul 1999 | EP |
| 0 986 225 | Mar 2000 | EP |
| 09214556 | Aug 1997 | JP |
| 9305155 | Nov 1997 | JP |
| 11289346 | Oct 1999 | JP |
| 9619064 | Jun 1996 | WO |
| WO 9619064 | Jun 1996 | WO |
| 9726709 | Jul 1997 | WO |
| 9727717 | Jul 1997 | WO |
| WO 9727717 | Jul 1997 | WO |
| WO 9728518 | Aug 1997 | WO |
| WO 9732251 | Sep 1997 | WO |
| 9732251 | Sep 1997 | WO |
| 9733421 | Sep 1997 | WO |
| 9741654 | Nov 1997 | WO |
| 9744942 | Nov 1997 | WO |
| 9800787 | Jan 1998 | WO |
| WO 9807897 | Feb 1998 | WO |
| 9821911 | May 1998 | WO |
| 9823108 | May 1998 | WO |
| WO 9823108 | May 1998 | WO |
| WO 9826344 | Jun 1998 | WO |
| 9848560 | Oct 1998 | WO |
| 9848560 | Oct 1998 | WO |
| WO 9848560 | Oct 1998 | WO |
| WO 9905620 | Feb 1999 | WO |
| WO 9905813 | Feb 1999 | WO |
| WO 9906900 | Feb 1999 | WO |
| WO 9950974 | Feb 1999 | WO |
| WO 9945684 | Mar 1999 | WO |
| 9917505 | Apr 1999 | WO |
| WO 9917505 | Apr 1999 | WO |
| WO 9919988 | Apr 1999 | WO |
| 9919988 | Apr 1999 | WO |
| WO 9936870 | Jul 1999 | WO |
| WO 9945484 | Sep 1999 | WO |
| 9945484 | Sep 1999 | WO |
| WO 9948312 | Sep 1999 | WO |
| 9948312 | Sep 1999 | WO |
| 9950974 | Oct 1999 | WO |
| 9963709 | Dec 1999 | WO |
| WO 9963709 | Dec 1999 | WO |
| WO 0011567 | Mar 2000 | WO |
| WO 0011832 | Mar 2000 | WO |
| WO 0020994 | Apr 2000 | WO |
| WO 0031931 | Jun 2000 | WO |
| WO 0049819 | Aug 2000 | WO |
| WO 0101264 | Jan 2001 | WO |
| WO 0113572 | Feb 2001 | WO |
| WO 0171539 | Mar 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09087623 | May 1998 | US |
| Child | 09545962 | US |
