1. Field of the Invention
The present invention is directed toward the field of replicating (or synchronizing) information folders between a host system and a mobile data communication device (“mobile device”). Specifically upon receiving this redirected information at their mobile device, the user can then organize this data into hierarchies, commonly known as folders, and may also perform various other operations on the redirected data. These organizational and other operations are then synchronized back to the original host system for replication. The invention also provides for the synchronization of a storage representation model for storing the data in a hierarchy of folders at the host system and the mobile device.
2. Description of the Related Art
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. Alternatively, the user might have to perform a special ‘connection’ action every so often that will synchronous all the pending items required by the user, provided they remember. Software executing on the mobile data communication device then transmits commands via the local communications link or a network 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.
Another major problem with the current pull-based systems is that the user must deal with the information all over again once the user returns to his office and accesses the information store at the host system. This situation occurs because the average user can get hundreds of pieces of electronic information a day. This is very common in e-mail systems where internal company mail, and external Internet mail, merge into one common mailbox creating a multitude of sources all merged into one location. As a result, once the user returns to their office, even though they may have seen and read the mail while traveling on their mobile device, they still have to re-read the messages and then organize the information into folders based upon the content. This results in user frustration, as the mobile device has not solved the problem of saving them time when the user returns to his office and accesses the information store at the host system.
A general problem with these known 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; (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; and (3) the need to deal with the information a second time once the user returns to the office and accesses the information store at the host system. A more automated, continuous, efficient and reliable system of ensuring that user data items are replicated (synchronized) at the user's mobile device is therefore needed.
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 is provided. The user may then move (or file) the data items to a particular folder within a folder hierarchy stored in the mobile data communication device, or may execute some other system operation on the data item. Software operating at the mobile device and the host system then synchronizes the folder hierarchy of the mobile device with a folder hierarchy of the host system, and any actions executed on the data items at the mobile device are then automatically replicated on the same data items stored at the host system, thus eliminating the need for the user to manually repeat the same actions at the host system that have been executed at the mobile data communication device.
As used in this application, the term host system refers to the computer where the redirector software is operating or is associated with. 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. In a preferred embodiment, the host system and the mobile device share a secure and private encryption key so that all communications that are exchanged between the end points (i.e., between the host system and the mobile device) are private.
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. These data items also include properties and attributes like the data item status, its creation time and data, and information about where it has been placed in an information hierarchy. Once the data items and its properties have been redirected to the user's mobile data communication device, the user may then organize and sort the items into folder hierarchies that are replicated at the host system. Additionally the the user may act upon the redirected data items, such as by reading, organizing, replying or forwarding the data item from the mobile data communication device, the host system is then informed of these actions and automatically reflects the changes on the corresponding data item stored at the host system. This reconciliation process creates a mirrored data store between the host system and the mobile device for those parts of their shared information. The term “mirrored” or “mirroring” when used in this description is meant to convey to the reader that all, substantially all or at least all of the pertinent information of a collection of data the user desires to have access to is accessible at either the mobile or host system. Due to limited display screen sizes and other issues relating to real-estate on a limited screen on a mobile communication, it is within the scope of one aspect of the invention to have representation of the data stored in either the host system or mobile device stored at the mobile device or host system, respectively, thereby still providing a “mirrored” data environment without necessarily the same graphical user interface or presentation of the mirrored data.
Another advantage of this data store mirroring is that traditionally in data storage systems, status icons are used to associate a state with a particular data item. A status icon is a graphical image of what state a given data item is in, i.e. read, replied to, or forwarded. The ability to affect these graphical images when viewed via a computer terminal at or associated with the host system from the mobile device allows the user a quick visual method of reviewing a list of data items in a particular folder to determine their states. This allows the user to know what actions have been performed on them, whether an action occurred from the mobile device, or whether nothing has been done to a given set of data items.
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 with related information as to which folder the message might have originally been placed into.
Using the redirector program, the user can select certain data items for redirection, such as E-mail messages, calendar events, meeting notifications, address entries, journal entries, personal reminders, contact information, task lists, expense lists, etc. The user can also select which folders get redirected to the mobile device. For example, the user may select that only data items in the Inbox and those in the company X folder shall be sent to the device. The user might select only the work-related journal folder in the journal sub-system their personal address folder within the contacts sub-system, and their 9 to 5 work calendar folder are to be redirected to their mobile device. 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.
The concept of a data items stored in a hierarchy is very well known in the field of computer science and in science in general. Categorization in the field of species identification has been done for hundreds of years. This same method of classification has been adopted into information systems so that people can deal with the large quantity of information that comes their way in a daily, weekly or yearly basis. Therefore the term folder is used to represent this categorization of information into meaningful and related associations; i.e. especially meaningful to the person filing the information. Naturally in a professional or business setting you might have one or more people filing the same information, i.e. a personal secretary helping a boss stay on top of the information by pre-filing the data for them.
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 or folder names 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 then 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 a networked printer or 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 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 additional to repackaging the information itself the repackaging may also include properties about the message. This might include the folder from which the message has been detected and pushed to the device. 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 appearing to come from the host system even though they are initiated at the mobile device, 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.
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. Another embodiment of this original redirector concept is to ‘relay’ information from a host to a mobile and onward to another device capable of dealing with certain messages or attachments. By using a standard like Bluetooth™ the mobile device could receive a message with an attached print file and then using Radio Frequency (RF) Bluetooth methods relay that to the printer to produce a hard copy.
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. It is also possible for the mobile data communications device to include additional information with the confirmation signal, including, any one or more of the following actions, the fact that the message: has been read (the information associated therewith is a “read signal”); has been filed in a specific folder (the information associated therewith is a “filed signal”); has been forwarded to another recipient (the information associated therewith is a “forward signal”); or, has been replied to (the information associated therewith is a “reply signal”). These actions can then be synchronized with the host system, thus eliminating the need for the user to perform these actions a second time. The action signals may advantageously be used to indicate the state of the message at the mobile.
One aspect of the invention, therefore, provides a method of indicating at the host system the state of the message at the mobile communications device. The steps of this method preferably include: (A) altering the state of a first message at the mobile communications device thereby creating an altered state; (B) forwarding a status signal to the host system; and, (C) changing at the host system a first message status icon based on the altered state at the mobile communications device. Therefore, according to one aspect of the invention, the message status icon change indicates an altered state of the message at the mobile communication device.
One aspect of the invention, therefore, provides a method of indicating at the host system the state of the message at the mobile communications device. The steps of this method preferably include: (A) redirecting a first message from the host system to the mobile communications device, wherein the first message at the host system has a first message status icon; (B) receiving the redirected first message from the host system at the mobile communications device; (C) altering the state of the first message at the mobile communications device thereby creating an altered state; (D) forwarding a status signal to the host system; and, (E) changing at the host system the first message status icon based on the action taken at the mobile communications device.
One aspect of the invention provides a method of indicating at a first device, via the host system, the state of the message at the mobile communications device. The steps of this method preferably include: (A) redirecting a first message from the host system to the mobile communications device, wherein the first message at the host system has a first message status icon; (B) receiving the redirected first message from the host system at the mobile communications device; (C) altering the state of the first message at the mobile communications device thereby creating an altered state; (D) forwarding a status signal to the host system; and, (E) changing at the host system the first message status icon based on the action taken at the mobile communications device; and (F) forwarding a read-receipt to a read-receipt requester's device.
One aspect of the invention provides a method of synchronizing messages between a first system and a second system. The steps of this method preferably include: (A) retrieving a first folder hierarchy from the first system; (B) retrieving a second folder hierarchy from the second system; (C) synchronizing the second folder hierarchy to the first folder hierarchy; (D) retrieving a first plurality of messages from the first system, the first plurality of messages being stored in folders within the first folder hierarchy; (E) retrieving a second plurality of messages from the second system, the second plurality of messages being stored in folders within the second folder hierarchy; (F) comparing the first plurality of messages to the second plurality of messages to identify common messages stored in both the first and second folder hierarchies; (G) determining whether any of the common messages are stored in different folders in the first and second folder hierarchies; and H) if a common message is located in different folders of the first and second folder hierarchies, then synchronizing the messages by moving the common message to a new folder within the first folder hierarchy or by moving the common message to a new folder within the second folder hierarchy.
Another aspect of the invention provides a method of synchronizing messages stored in a folder hierarchy at a host system and a corresponding folder hierarchy at a mobile data communication device. This method preferably includes the following steps: (A) receiving a message at the host system; (B) storing the message in a first folder of the folder hierarchy at the host system; (C) transmitting the message to the mobile data communication device; (D) storing the message in a first folder of the folder hierarchy at the mobile data communication device; (E) moving the message from the first folder to a second folder at the mobile data communication device; (F) coupling the mobile data communication device to the host system; (G) detecting that the message has been moved to the second folder at the mobile data communication device; and (H) in response to the detection step, moving the message from the first folder at the host system to a second folder of the folder hierarchy at the host system that corresponds to the second folder of the folder hierarchy at the mobile data communication device.
Still another aspect of the invention provides a method of synchronizing messages stored in a folder hierarchy at a host system and a corresponding folder hierarchy at a mobile data communication device, comprising the steps of: (A) receiving a message at the host system; (B) storing the message in a first folder of the folder hierarchy at the host system; (C) transmitting the message to the mobile data communication device; (D) storing the message in a first folder of the folder hierarchy at the mobile data communication device; (E) moving the message from the first folder to a second folder at the mobile data communication device; (F) transmitting a move message from the mobile data communication device to the host system indicating that the message has been moved to the second folder at the mobile data communication device; and (G) receiving the move message at the host system and moving the message stored in the first folder at the host system to a second folder at the host system that corresponds to the second folder at the mobile data communication device.
Yet another aspect of the invention provides a method of synchronizing a first device to a second device, comprising the steps of: (A) providing a first folder hierarchy at the first device; (B) providing a second folder hierarchy at the second device; (C) synchronizing the second folder hierarchy to the first folder hierarchy; (D) retrieving a first plurality of messages stored within the first folder hierarchy and retrieving a second plurality of messages stored within the second folder hierarchy, wherein at least one of the first plurality of messages and at least one of the second plurality of messages are common messages; (E) determining whether the common messages are stored in similar folders within the first and second folder hierarchies; and (F) if the common messages are not stored in similar folders, then synchronizing the common messages so that they are stored in similar folders within the first and second folder hierarchies.
Another aspect of the invention provides a method of synchronizing a first device to a second device, comprising the steps of: (A) providing a first folder hierarchy at the first device; (B) providing a second folder hierarchy at the second device; (C) retrieving a first plurality of messages stored within the first folder hierarchy and retrieving a second plurality of messages stored within the second folder hierarchy; (D) determining whether the first device executed an operation on a message stored in the first folder hierarchy, and if so, then executing the same operation on a corresponding message stored in the second folder hierarchy at the second device.
Still another aspect of the invention provides a system for synchronizing messages between a first device and a second device, comprising; a pair of matching folders, one of the pair of matching folders being located on the first device, the other of the pair of matching folders being located on the second device; a pair of matching messages, one of the pair of matching messages being located on the first device, the other of the pair of matching messages being located on the second device; and means for moving the pair of messages such that if one of the pair of matching messages is moved to one of the pair of matching folders, the other matching message is moved to the other matching folder.
An 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. 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 and folder names 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) the ability to store folder hierarchies on the mobile data communications device so that user can organize the information during those periods when information is being redirected to said device; and (7) eliminating the need to organize the information a second time once the user returns to the office to work from their host system.
A further advantage of the present invention is that it provides a software structure and method for managing messages between the mobile data communication device and the host system. The software provides a logical structure for folders and messages that can detect movement of messages between folders on either the mobile data communication device or the host system. This allows the user the flexibility to organize messages into folders on the mobile data communication device without having to replicate the organizational work on the host system, or vice versa. The folder and message software structure further provides the redirector program trigger signals for forwarding messages.
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.
Wireless Information Delivery
This first section illustrates one method for enabling the redirection of information between a host system and a wireless mobile data communication device. The redirection program 12 is a preferred component of the overall system that facilitates the mirroring of data store folders between a host system and a mobile device. The ability to push data and commands in real-time over a wireless two-way data network provides a perfect vehicle for continuous synchronization of data stores between systems.
Referring now to the drawings,
In the present invention, the terms “redirector” or “redirector program” refers to one or more software modules and programs that perform together to preferably (1) identify information to be wirelessly exchanged, (2) compress and decompress the information, (3) encrypt and de-encrypt the information, and (4) envelop and recover from the envelope the information to be exchanged with a mobile data communication device. This redirector software may be a stand-alone program, or it could be incorporated into a larger mail program and perform wireless-centric actions that enables the exchange of information with wireless data communication devices.
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. User-selected 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.
The user-defined event triggers that can be detected by the redirector program 12 preferably include 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 A 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 particular 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
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/IP repackaging and delivery method (most commonly used in the alternative server configuration shown in
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, then 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
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. 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
Turning back to
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 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 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.
Folder Synchronization Basics
Organizing and storing messages in the mobile device 24 and the host system 10 is set forth in
The folder structure includes a folder ID, folder type, folder name, parent folder ID, and parent folder type. The folder ID is a unique tag for each folder. The folder ID is generated when the mobile device 24 is synchronized to the host system 10. The folder type specifies attributes of the folder that differentiate it from other folders. One such folder could be a deleted items folder. The deleted items folder could be set to automatically purge messages after a given time. The folder name is the name of the folder that will be displayed on the device 24 or the host system 10. The parent folder ID is the folder ID of the folder that is one level above the current folder in the hierarchical system. The parent folder type specifies attributes of the parent folder that differentiates it from other folders. One skilled in the art will appreciate that this representation is just one format and method for identifying folders and information within folders. The invention itself would work just as well with any other format and identification method.
The folder structure synchronization process 136 first synchronizes the folder hierarchy of the mobile device 24 to the hierarchy of the host system and then moves a message that the user has filed in a folder on the mobile device 24 to the corresponding folder on the host system 10. Correspondingly, when the user has filed a message in a folder on the host system 10, the folder structure synchronization process 136 will move the message to the corresponding folder on the mobile device 24. This is advantageous, for example, for a user who uses his default message receive folder (inbox) as a measure of incomplete and complete jobs. It also eliminates the need to deal with the message a second time once the user returns to the office and uses primarily the host system and the associated folder structure therein.
By continuing to select through the hierarchical folder structure, step 174 retrieves subfolders of the top folder. The subfolder is checked for a folder ID in step 176 and assigned a folder ID in step 178 if no folder ID is found in step 176. Step 180 assigns a folder type to the subfolder. Step 182 checks for a subfolder underneath the current folder. If another subfolder is found, it is assigned as the top folder in step 184 and returned to step 174. If there are no more subfolders underneath the current subfolder, step 186 retrieves the next subfolder and returns the retrieved subfolder to step 176. Once the last subfolder is retrieved, step 190 ends the tag and retrieve step 142 of the folder structure synchronization process 136. Overall, this is a recursive operation performed for all the subfolders starting from the top folder of the information store.
The steps set forth in
Step 230 checks if the move flag for message ‘B’ is on and the move flag for message ‘A’ is off. If this is the case, message ‘A’ is moved to the folder having the folder ID of message ‘B’ on the host system in step 232. If the move flag status is not equal to the check in step 230, step 234 checks for move flags in both message ‘A’ and message ‘B’ to be on. If both flags are on, step 238 decides which message to move based on a conflict resolution structure. The conflict resolution structure is a predetermined rule where the software moves one of the messages based on the folder ID of the other message. If both flags are off, step 240 checks to see if the folder IDs of message ‘A’ and message ‘B’ are different. If the folder IDs are different, the conflict resolution structure of step 238 decides which message to move. If the folder IDs are the same, messages ‘A’ and ‘B’ remain in their current folders as shown in step 242.
Step 246 checks if message ‘B’ was moved. If message ‘B’ was not moved, the message ‘B’ move flag is reset in step 250. Message ‘A’ is checked in step 252 to see if it moved. If message ‘A’ did not move, the move flag for message ‘A’ is reset 254. This is accomplished by updating the folder ID on message ‘A’ with the folder ID that was found in during step 210. The procedure for checking the move status of the messages is completed in step 256.
The user has the option to move a message between folders on either the mobile device 24 or the host system 10. For example, a user who has a “to do” folder on both the host system 10 and the mobile device 24, might receive a message on the mobile device 24 when he is away from his host system 10. The redirector program might be instructed to place incoming messages into an Inbox folder on the device. After reviewing the message, the user decides to file the message into the “to do” folder on the mobile device 24. The software system for organizing messages and folders on the mobile device 24 sends a move signal to the host system 10 to move the same message to the “to do” folder on the host system. Later, the user decides to move the message again to a “completed tasks” folder which also resides on both the mobile device 24 and the host system 10, but this time the user initiates the move at the host system 10. The host system 10 sends a move signal to the mobile device 24 to initiate the same move on the mobile device 24. This method and system of moving messages between folders on the host system 10 and the mobile device 24 employs the “push” paradigm of the redirector software. The method steps for moving the message between folders are shown in
As shown in
The method of continuous over-the-air-synchronization process is preferable; however, such continuous real-time synchronization has drawbacks when continuously (or frequently) transmitting data packets over the wireless network. Some of the drawbacks include (1) low bandwidth on the particular wireless network that the mobile device works with is not very robust to handle an overwhelming amount of data transfers, (2) higher costs for the service provider, user or both are generally associated with such frequent data exchanges and (3) heavier power usage on the mobile device's power source may prematurely drain the power resources of the mobile device. Therefore, it may be desirable to (1) switch the over-the-air-synchronization feature off and to leave synchronization of information organization until device-host synchronization through the wired interface cradle or (2) leave the option to the user to switch on the feature for a period of time until switched off by the user or after the expiration of predetermined period of time. In another embodiment of the present invention, the mobile device 24 bundles together and preferably compresses the various synchronizations, move commands (or other operations) created during the day and transmits the bundled information as one or more data packet transmissions during non-peak network usage or transmission times. Preferably, the bundling and the optional compression step reduces the number of data packets to be sent over the wireless network. At the host system, the redirector component receives, unbundles and appropriately acts on the information. Advantageously, this store, delay and transmit method reduces the power requirements for the mobile device thereby conserving the power store of the mobile device and may be used for any type of data item or certain types of data items. For example, the device may do the automatic over-the-network continuous transmission of emails and calendar events from the device, but delay the transmission of folder moves until non-peak times or alternatively, delay communication of such changes until a physical synchronization occurs.
The steps set forth in
Finally, the folder management system controls wasted use of resources by purging the earliest messages once allocated space is exceeded, as shown in
Another embodiment of the current invention is the ability to modify the message status and folder status icons as changes are synchronized with the host system. This embodiment can work either over-the-air or during a bulk transfer of message status information. Traditionally, message status icons are associated with messages at the host system 10. A message status icon is a graphical image indicating the state of the message. States may indicate that: a message is new, a message has been read, a message has been deleted, a message has been forwarded, a message has been replied to, a message has been filed or any combination thereof The message status icon is preferably in close physical proximity, when viewed by the user as a list of messages, to the corresponding message and other corresponding message details (such as subject, sender's name, arrival time, etc.) in the graphical user interface. By way of example, if a user at the host system forwards a message from the host system to another party, the message status icon will be altered in appearance to indicate to the user a forwarding action has been applied to that particular message. In this manner and advantageously, the user has a quick visual method of reviewing a list of messages in a folder and the states of the messages, thereby knowing-the actions that have already taken place. with respect to those messages at the host system 10.
In accordance with the present invention and preferably, as a consequence of receiving a set of folders and messages within those folders at the mobile device 24, the mobile device 24 will either remember message state changes or they will be communicated with a message. For example if the user performs a ‘Reply’ to a message then when the host system 10 receives that reply it will modify the message status icon in the appropriate folder. The host system 10 will be able to process at least one of a plurality of action signals from the mobile 24 (i.e., a read signal, a filed signal, a forward signal or a reply signal), a graphical change will occur at the host system 10 to a message status icon, which is associated with the message acted upon at the mobile, to indicate to the user upon his return and access to the host system that the message has been acted upon (i.e., read, replied to, forwarded and/or filed, etc.) at the mobile. The graphical change will result in a second message status icon distinguishable from the first message status icon and, preferably, the graphical representation of the second message status icon clearly illustrates the state of the message. In one embodiment of the present invention, described in detail in the next section, and preferably as a consequence of receiving a filed signal, the host system application associated with the message will move the message to the appropriate folder so that the user upon his return and access of the host system will see information organized in the same manner as in the mobile device. In the case of a filed message that is also read at the mobile, the corresponding message, at the host system, is moved and the message status icon associated therewith at the host system is altered to indicate the read status. Likewise, in the case where a message is read and forwarded to another party at the mobile, a single second message status icon will preferably represent both statuses (i.e, read and forwarded). Preferably, any second message status icon graphical representation resulting from an action event taking place at the mobile is the same graphical representation that would occur if the action event had been undertaken at the host system 10 rather than the mobile 24. Alternatively and at the user's control preferably, any graphical representation is clearly distinguishable as to be the status change resulting from an action taking place at the mobile versus an action taking place at the host system. In the latter embodiment, the user of the redirector system herein will have quick and reliable information as to where the message was read, filed, forwarded, or replied from. Preferably and where a read-receipt is requested by a sender of the message, upon receiving the read signal from the mobile, the redirector or any associated message application such MS Exchange™ or Lotus Notes™ will direct a read-receipt signal to the read-receipt requester.
Folder Synchronization Advanced Methods
As laid out in the first section there are many basics necessary for any folder synchronization to take place. The idea of a one-time bulk synchronization, a step of labeling the folders in a consistent fashion and the idea of a bulk synchronization after many changes have been made are all important to any synchronization. The main advantage of using a bulk method for synchronization is to reduce airtime costs. If the cost factor were to be eliminated it is possible to perform all the steps over the air or to mix the modes so the only time a bulk synchronization would be performed is when the user uses the invention for the first time (“The Setup Stage”).
The process of synchronizing all this information between these two data stores can take place in several possible ways. As mentioned the user might select a ‘batch-mode’ method to reduce air-time costs and save battery life. If the batch mode is used then the software could either use a very slow and time consuming method of compare each message to determine which messages from the mobile data store had moved from the host data store. The next most advanced method would be to use folder Ids and message Ids, combined with ‘move’. indicator flags to facilitate knowing which messages had been moved from a first folder into a second folder. This effectively would create a ‘change list’ of actions performed by the user. In the preferred embodiment if the user did not select the batch-mode approach but performed the real-time over-the-air method, this later technique would be the best method. This method would also use folder Ids and message Ids to facilitate the identification and movement of messages and the modification of folders. This advanced real-time, over-the-air mirroring of information (i.e., synchronized) is illustrated in
Turning now to
Some of the functions of the Wireless Component 506 include interfaces to the mobile device 24 through a wireless network 512 and encoding and decoding messages and commands that must be exchanged. Another element of the Wireless Component 506 is the detection of folder changes or the execution of folder changes on behalf of the mobile device 24. As changes take place on either the host system 10 or the mobile device 24, calendar messages 514 are exchanged over a secure communication link via the wireless network 512. The wireless component 506 uses a mobile table, that is kept either in the message server or in the data store, to map a user of the host system or message server to a mobile device. Effectively this mapping allows changes between the message server data store and the mobile device's data store to be mapped to each other. The wireless component 506 maintains a constant, real-time link between the two systems over the wireless network 512. On each mobile device 24 is a copy of parts of the data store that was on the host system. In this example a calendar data store 516 is shown, but other data stores could also be present simultaneously on the mobile device 24.
Looking at
Turning now to
Once the folders are synchronized the software can then proceed to synchronize data items within those folders. This is done either by retrieving messages at the host system 10 and the mobile system 24 and comparing their locations (520 and 522), or by marking those message that have moved. The later case is called ‘batch-mode’ synchronization and was discussed in the last section. In the preferred embodiment there is no batch synchronization and every message that is moved or changed on the mobile device 24 eventually causes a command to be sent back to the host system 10. Such a command might be piggybacked on top of a normal data message leaving the mobile device to reduce overall traffic from the mobile device. In other words, the command and the data message could be packaged together and then transmitted from the device, or alternatively, the command could be packaged, the data message could also be packaged and then the two packaged items may be then be collectively packaged and then transmitted from the device.
To help understand how a folder hierarchy is used with convention user data there is a further example in
Turning now to
Reviewing
Traditionally, message status icons are associated with messages at the host system 10. A message status icon is a graphical image indicating the state of the message. States may indicate that: a message is new, a message has been read, a message has been deleted, a message has been forwarded, a message has been replied to, a message has been filed or any combination thereof The message status icon is preferably in close physical proximity, when viewed by the user as a list of messages, to the corresponding message and other corresponding message details (such as subject, sender's name, arrival time, etc.) in the graphical user interface. By way of example, if a user at the host system forwards a message from the host system to another party, the message status icon will be altered in appearance to indicate to the user a forwarding action has been applied to that particular message. In this manner and advantageously, the user has a quick visual method of reviewing a list of messages in a folder and the states of the messages, thereby knowing the actions that have already taken place with respect to those messages at the host system 10.
In accordance with the present invention and preferably, as a consequence of receiving at the host system 10 at least one of a plurality of action signals from the mobile 24 (i.e., a read signal, a filed signal, a forward signal or a reply signal), a graphical change will occur at the host system 10 to a message status icon, which is associated with the message acted upon at the mobile, to indicate to the user upon his return and access to the host system that the message has been acted upon (i.e., read, replied to, forwarded and/or filed, etc.) at the mobile. The graphical change will result in a second message status icon distinguishable from the first message status icon and, preferably, the graphical representation of the second message status icon clearly illustrates the state of the message. In one embodiment of the present invention and preferably, as a consequence of receiving a filed signal, the host system application associated with the message will move the message to the appropriate folder so that the user upon his return and access of the host system will see information organized in the same manner as in the mobile device. In the case of a filed message that is also read at the mobile, the corresponding message, at the host system, is moved and the message status icon associated therewith at the host system is altered to indicate the read status. Likewise, in the case where a message is read and forwarded to another party at the mobile, a single second message status icon will preferably represent both statuses (i.e, read and forwarded). Preferably, any second message status icon graphical representation resulting from an action event taking place at the mobile is the same graphical representation that would occur if the action event had been undertaken at the host system 10 rather than the mobile 24. Alternatively and at the user's control preferably, any graphical representation is clearly distinguishable as to be the status change resulting from an action taking place at the mobile versus an action taking place at the host system. In the latter embodiment, the user of the redirector system herein will have quick and reliable information as to where the message was read, filed, forwarded, or replied from. Preferably and where a read-receipt is requested by a sender of the message, upon receiving the read signal from the mobile, the redirector or any associated message application such MS Exchange™ or Lotus Notes™ will direct a read-receipt signal to the read-receipt requester.
In one embodiment of the present invention, the invention allows for a notification of the state of a redirected message at the mobile. It is to be understood that the status signals may be forwarded to the host system during other times as well, such as during synchronization or real-time over-the-airmoves as described below.
In another embodiment of the present invention, there is provided a method of indicating at the host system the state of the message at the mobile communications device: The steps of this method preferably include: (A) altering the state of a first message at the mobile communications device thereby creating an altered state; (B) forwarding a status signal to the host system; and, (C) changing at the host system a first message status icon based on the altered state at the mobile communications device. Therefore, according to one aspect of the invention, the message status icon change indicates an altered state of the message at the mobile communication device.
In another embodiment of the present invention, there is provided a method of indicating at the host system the state of the message at the mobile communications device. The steps of this method preferably include: (A) redirecting a first message from the host system to the mobile communications device, wherein the first message at the host system has a first message status icon; (B) receiving the redirected first message from the host system at the mobile communications device; (C) altering the state of the first message at the mobile communications device thereby creating an altered state; (D) forwarding a status signal to the host system; and, (E) changing at the host system the first message status icon based on the action taken at the mobile communications device.
In one embodiment of the invention, there is provided a method of indicating at a first device such as a sender's host system or mobile device, via the host system the state of the message at the mobile communications device. The steps of this method preferably include: (A) redirecting a first message from the host system to the mobile communications device, wherein the first message at the host system has a first message status icon; (B) receiving the redirected first message from the host system at the mobile communications device; (C) altering the state of the first message at the mobile communications device thereby creating an altered state; (D) forwarding a status signal to the host system; and, (E) changing at the host system the first message status icon based on the action taken at the mobile communications device; and (F) forwarding a read-receipt to a read-receipt requester's device.
Turning now to
As a concrete example
As presented in
Turning now to
On the folder baseline has been set between the message server 500 and the mobile device 24, the normal process of redirecting data items between the host system 10 and the mobile device 24 can take place 606. This was thoroughly described in
Referring now to
Turning now to step 700 of
If the information from the host is not a new data item the invention checks for a Folder Command 702. If the information is a folder command 702 then a series of checks are performed to see what change the host has performed on a folder. If the information is not a folder command 702 there is a test to see if the item is a command confirmation 704. If it is a command confirmation 704 the invention proceeds to
If the host has sent a folder command 702 then there are 4 checks to see which folder operation is required. These four checks include the creation of a new folder 722, the deletion of a folder 724, the renaming of a folder 726 or a movement of a message between folders 728. The first check that is performed is to see if a new folder has been created 722 if the folder command matches this then the software on the device checks to see if the folder already exists on the device 732. This would be a rare situation but it is possible the user creates a folder on the mobile device 24 at about the same time that someone creates a similar folder on the host system 10. If this does happen then a negative response is sent back to the host system 734. If the folder does not exist then the new folder is created 734 and a positive confirmation is sent to the host 742 to confirm the create was successful. If possible this confirmation is delayed for a few minutes in an attempt to piggyback it with real data that might be leaving the mobile device 24. The next folder command check is for a delete folder command 724. In this situation a test is performed to see if the folder still exists 732 on the device. Naturally it is possible the user has already removed it at the same time as the host is removing it. If the folder is already gone an negative confirmation is sent to the host 736. Otherwise the folder is removed 738 and a positive confirmation is sent to the host 742. The third test for a folder command checks to see if the host has renamed a folder 726. In this case the same test is preformed to confirm the folder still exists 732. It might have been deleted or renamed already to something different. If the folder with the same Id does not exist a negative confirmation is sent back to the host 736, otherwise the folder is renamed 740 and a positive confirmation is returned to the host 742.
Finally the software checks to see if a move message command 728 was requested by the host. If it was not this then some other command may have been sent from the host 730 that is outside the description for this invention. If it was a move message command 728 the software first checks to ensure the message Id and Folder Ids still exist 744 on the mobile device 24. If either the message is not on the device, or the destination folder is not present a negative response is sent to the host 746. Otherwise a tag is created with the new folder Id 748, the message is updated with the new folder Id 749 and a positive confirmation is sent to the host 742.
If the message from the host system 10 is a command confirmation 704 then the command must be processed, as shown in
If the command was not a message move a test is performed to see if the confirmation is for a folder deletion action 750. If it is a folder delete confirmation a further check is performed to see if it was a positive confirmation 758. If the delete was successful on the host the same action is performed on the indicated folder Id 766. Otherwise the delete failed for some reason so the reason is determined from the host message 760. If the problems if fixable the user may be able to pick another folder to delete or cancel their delete command 762. Whatever happens the original folder that was marked for deletion is unmarked. The next confirmation command test is to see if the user had renamed a folder 752. If this was the command a test is performed to see if the confirmation is positive 758. If the rename was successful the rename action is performed on the folder Id provided 768. If the rename failed a check is performed to see if the problem is fixable, i.e. can the user make another selection 760. If so the user is given a chance to try another name change on the same folder 762. If they do try another name, since the first one may not have been unique, another message is sent to the host 764. Finally the final test on the command confirmation is to see if the user added a new folder on the device 754. If this was not the command other command tests are performed 756. If it was an add command confirmation then the software checks to see if the confirmation is positive 758. If it was positive the new folder is added and the user is given full access to the folder for filing message and data into 770. Otherwise a further check is performed to see why the add request failed 760. If the name was in conflict and it can be corrected by the user 762, they are allowed to enter a new name and message is sent to the host 764.
Turning now to
If the user wants to move a message between folders 772 the message in question, labeled X, is flagged with the new folder Id ‘Y’ 786 and a move message x to folder y command or flag is sent to the host 798. The flag might be used when piggybacking with a real message, or a command is sent when no data is being sent to the host. To assist in this piggybacking the transmission of the request is optionally deleted to wait for data from the user going to the host 810. The delete may only be for a few sections but it could save valuable battery and transmit power. If the user action is not a message move a check is performed to see if the user is simply reading a message 774. If the user is reading the message then the message is marked as read on the handheld and the message is opened for the user 788. As the user is reviewing the message a status update command/flag is generated to send to the host 800. The transmission of this flag or command is delayed to the host just in case they reply or forward the message and generate real traffic going to the host. The user might also be replying or forwarding a message 776 as part of the reading of a new or old message. In this case the message is marked as replied-to or forwarded and the user attaches their comments 790. The software also generated a flag that will be sent with the forwarded or replied message 802. The message and the flag are then transmitted to the host system 810.
The user might also be performing folder operations on the handheld device, for example the user might add a folder 778. In this case the folder name selected by the user is verified on the device to ensure it is unique and a temporary folder Id is generated 792. Once this command is given to the host the final folder Id might be changed by the host to ensure it is unique. The software then sends a Add Folder Command to the host 804, which is piggybacked if possible with other data being sent to the host 810. The user might decide to rename a folder on the device 780. In this case the folder name is again verified to be unique 794 and a Rename Folder Command is generated 806 for transmission to the host system 810. Finally the user might decide to delete a folder on the device 782. The first check in this case is to ensure the folder is empty before the user deletes it 796. One skilled in the art can appreciate that it would be easy to simply prompt the user to override this restriction and delete all message in the folder before deleting the folder. After ensuring the user is accepted the action, the folder is marked for deletion, a command is generated for the host system 808 and is then transmitted to the host 810.
Turning now to
If the message is not a data message then a further test is performed to see if the message is a command confirmation 822. If it is then the data flow proceeds to
Turning now to
Turning now to
If the command from the mobile user is a move message command 870 the software checks the message store to ensure the message Id provide is still in the folder indicated 872. If the message is missing then the command fails and a negative confirmation 908 is returned to the mobile device 24. Otherwise a check is made to ensure that the source folder and the destination folder is still in the message store 874. If one of the folders is missing a negative response is sent back to the mobile device 876. Otherwise the message is moved from one folder to another folder 878. If the move was successful 880 the folder id in the message is updated to the new folder Id and a positive confirmation is sent to the mobile device 882. Otherwise the move failed due to memory or some other serious error and a negative confirmation is sent to the mobile device 884.
If the command from the user was not a move command then the software checks for a folder add command 886. If a folder was added on the device the host checks to see if the folder exists already on the host 888. If the folder already exists on the host the software sends a negative confirmation, an error code and the folder Id of the folder that already has that name 892. If the folder does not exist the folder is created, assigned an Id as provided by the mobile, unless the Id is not unique in which case a new Id will be assigned 890. After this a positive confirmation is sent to the mobile user 904. If possible these confirmations are also piggybacked on real data messages 904. If the command was not an add command then a check is made to look for a rename folder command 894. If the command is a rename there is a check to see if the new folder name already exists on the host 898. If the source folder does not exist, or if the destination folder does exist 898 the rename command will fail and a negative confirmation will be sent to the mobile 892. If the source folder does exist, and the destination folder does not exist 898 the command is successful and the folder is renamed 902. After the renaming the host send a confirmation message to the mobile device 904. Finally the command might be a delete folder command 896, this is the last processed command in this patent otherwise other commands are handled in 906. When deleting a folder on the mobile device 24 there is a check to ensure the folder exists 898. If the folder does exist the folder is deleted from the host 900 and a positive confirmation is returned to the mobile 904. Otherwise the folder may already be deleted and the command fails 892. This type of failure is okay and the mobile can still go ahead and remove the folder.
Turning now to
If the message from the data store was not a new message then the software checks for an indication of a moved message 930. If a message has been moved between folders then a check is performed to see if the message has been previously sent to the mobile device 936. If the device never received the message there is no action to be performed 938. Otherwise there is a further check to ensure the folder has been given to the device 940. It is possible that an add folder command has been given to the device and the host is waiting for a confirmation. If not the new folder is sent to the device or the host waits for the confirmation before sending the message move command 942. If the folder is already on the device the host sends a message move command with the message Id and two folder Ids to the device 944. The device optionally needs the source folder Id and the destination folder Id to execute the command the fastest. Otherwise the mobile device could search for the message in all folders before moving it to the destination folder Id.
If the message from the data store is not a message move indication then a check is performed to see if there has been folder modification activity 932. If it is not folder modification activity 932 then it might be other data store messages 934 not dealt with in this patent. In the situation when a folder has been modified it could be a folder create 946, a folder rename 948 or a folder delete 950. If it is not one of these three then other processing logic handles folder changes not part of this patent 952. For all three commands the folder that has been modified is marked to indicate a change is pending 954. This will be used on the command confirmation to complete the change to the data store. Finally the host sends a command to the mobile for verification of the action 956.
Turning now to
Where the device 24 is enabled for two-way communications, the device will incorporate a communication subsystem 1911, including a receiver 1912, a transmitter 1914, and associated components such as one or more, preferably embedded or internal, antenna elements 1916 and 1918, local oscillators (LOs) 1913, and a processing module such as a digital signal processor (DSP) 1920. As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem 1911 will be dependent upon the communication network in which the device is intended to operate. For example, a device 24 destined for a North American market may include a communication subsystem 1911 designed to operate within the Mobitex™ mobile communication system or DataTAC™ mobile communication system, whereas a device 24 intended for use in Europe may incorporate a General Packet Radio Service (GPRS) communication subsystem 1911.
Network access requirements will also vary depending upon the type of network 1919. For example, in the Mobitex and DataTAC networks, mobile devices such as 24 are registered on the network using a unique personal identification number or PIN associated with each device. In GPRS networks however, network access is associated with a subscriber or user of a device 24. A GPRS device therefore requires a subscriber identity module (not shown), commonly referred to as a SIM card, in order to operate on a GPRS network. Without a SIM card, a GPRS device will not be fully functional. Local or non-network communication functions (if any) may be operable, but the device 24 will be unable to carry out any functions involving communications over network 1919. When required network registration or activation procedures have been completed, a device 24 may send and receive communication signals over the network 1919. Signals received by the antenna 1916 through a communication network 1919 are input to the receiver 1912, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection and the like, and in the example system shown in
The DSP 1920 not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in the receiver 1912 and transmitter 1914 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 1920.
The device 24 preferably includes a microprocessor 1938 which controls the overall operation of the device. Communication functions, including at least data and voice communications, are performed through the communication subsystem 1911. The microprocessor 1938 also interacts with further device subsystems such as the display 1922, flash memory 1924, random access memory R 1926, auxiliary input/output (I/O) subsystems 1928, serial port 1930, keyboard 1932, speaker 1934, microphone 1936, a short-range communications subsystem 1940 and any other device subsystems generally designated as 1942.
Some of the subsystems shown in
Operating system software used by the microprocessor 1938 is preferably stored in a persistent store such as flash memory 1924, which may instead be a read only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as RAM 1926. It is contemplated that received communication signals may also be stored to RAM 1926.
The microprocessor 1938, in addition to its operating system functions, preferably enables execution of software applications on the device. A predetermined set of applications that control basic device operations, including at least data and voice communication applications for example, will normally be installed on the device 24 during manufacture. A preferred application that may be loaded onto the device may be a personal information manager (PIM) application having the ability to organize and manage data items relating to the device user such as, but not limited to e-mail, calendar events, voice mails, appointments, and task items. Naturally, one or more memory stores would be available on the device to facilitate storage of PIM data items on the device. Such PIM application would preferably have the ability to send and receive data items, via the wireless network. In a preferred embodiment, the PIM data items are seamlessly integrated, synchronized and updated, via the wireless network, with the device user's corresponding data items stored or associated with a host computer system. Further applications may also be loaded onto the device 24 through the network 1919, an auxiliary I/O subsystem 1928, serial port 1930, short-range communications subsystem 1940 or any other suitable subsystem 1942, and installed by a user in the RAM 1926 or preferably a non-volatile store (not shown) for execution by the microprocessor 1938. Such flexibility in application installation increases the functionality of the device and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the device 24.
In a data communication mode, a received signal such as a text message or web page download will be processed by the communication subsystem 1911 and input to the microprocessor 1938, which will preferably further process the received signal for output to the display 1922, or alternatively to an auxiliary I/O device 1928. A user of device 24 may also compose data items such as email messages for example, using the keyboard 1932, which is preferably a complete alphanumeric keyboard or telephone-type keypad, in conjunction with the display 1922 and possibly an auxiliary I/O device 1928. Such composed items may then be transmitted over a communication network through the communication subsystem 1911.
For voice communications, overall operation of the device 24 is substantially similar, except that received signals would preferably be output to a speaker 1934 and signals for transmission would be generated by a microphone 1936. Alternative voice or audio I/O subsystems such as a voice message recording subsystem may also be implemented on the device 24. Although voice or audio signal output is preferably accomplished primarily through the speaker 1934, the display 1922 may also be used to provide an indication of the identity of a calling party, the duration of a voice call, or other voice call related information for example.
The serial port 1930 in
A short-range communications subsystem 1940 is a further optional component which may provide for communication between the device 1924 and different systems or devices, which need not necessarily be similar devices. For example, the subsystem 1940 may include an infrared device and associated circuits and components or a Bluetooth™ communication module to provide for communication with similarly-enabled systems and devices.
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 now issued as U.S. Pat. No. 6,219,694 (Date of Issue: Apr. 17, 2001), and assigned to the assignee of the present invention, and U.S. Utility application Ser. No. 09/545,963 filed on Apr. 10, 2000, now U.S. Pat. No. 6,779,019 (Date of Issue: Aug. 17, 2004). Both of these related applications are hereby incorporated into the present application by reference.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/CA01/00492 | 4/10/2001 | WO | 00 | 1/7/2003 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO01/78342 | 10/18/2001 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
2292387 | Markey | Aug 1942 | A |
4106060 | Chapman, Jr. | Aug 1978 | A |
4417349 | Hills et al. | Nov 1983 | A |
4438433 | Smoot et al. | Mar 1984 | A |
4558413 | Schmidt et al. | Dec 1985 | A |
4558454 | Hills et al. | Dec 1985 | A |
4644351 | Zabarsky et al. | Feb 1987 | A |
4652698 | Hale et al. | Mar 1987 | A |
4665519 | Kirchner et al. | May 1987 | A |
4695880 | Johnson et al. | Sep 1987 | A |
4697281 | O'Sullivan | Sep 1987 | A |
4698839 | DeVaney et al. | Oct 1987 | A |
4713780 | Schultz et al. | Dec 1987 | A |
4714995 | Materna et al. | Dec 1987 | A |
4714996 | Gladney et al. | Dec 1987 | A |
4768087 | Taub et al. | Aug 1988 | A |
4821308 | Hashimoto | Apr 1989 | A |
4825456 | Rosenberg | Apr 1989 | A |
4831582 | Miller et al. | May 1989 | A |
4837797 | Freeny | Jun 1989 | A |
4837798 | Cohen et al. | Jun 1989 | A |
4837800 | Freeburg et al. | Jun 1989 | A |
4845658 | Gifford | Jul 1989 | A |
4853843 | Ecklund | Aug 1989 | A |
4856047 | Saunders | Aug 1989 | A |
4875039 | Andros et al. | Oct 1989 | A |
4875159 | Cary et al. | Oct 1989 | A |
4882674 | Quint et al. | Nov 1989 | A |
4882744 | Hashimoto | Nov 1989 | A |
4882752 | Lindman et al. | Nov 1989 | A |
4897781 | Chang et al. | Jan 1990 | A |
4916738 | Chandra et al. | Apr 1990 | A |
4928096 | Leonardo et al. | May 1990 | A |
4942598 | Davis | Jul 1990 | A |
4951044 | Nelson et al. | Aug 1990 | A |
4961216 | Baehr et al. | Oct 1990 | A |
4972457 | O'Sullivan | Nov 1990 | A |
4980907 | Raith et al. | Dec 1990 | A |
5008926 | Misholi | Apr 1991 | A |
5032979 | Hecht et al. | Jul 1991 | A |
5043721 | May | Aug 1991 | A |
5048085 | Abraham et al. | Sep 1991 | A |
5058431 | Karwacki | Oct 1991 | A |
5068916 | Harrison et al. | Nov 1991 | A |
5086502 | Malcolm | Feb 1992 | A |
5125021 | Lebowitz | Jun 1992 | A |
5127041 | O'Sullivan | Jun 1992 | A |
5128981 | Tsukamoto et al. | Jul 1992 | A |
5136291 | Teague | Aug 1992 | A |
5150407 | Chan | Sep 1992 | A |
5155847 | Kirouac et al. | Oct 1992 | A |
5157660 | Kuwahara et al. | Oct 1992 | A |
5159592 | Perkins | Oct 1992 | A |
5166931 | Riddle | Nov 1992 | A |
5177680 | Tsukino et al. | Jan 1993 | A |
5181200 | Harrison | Jan 1993 | A |
5210785 | Sato et al. | May 1993 | A |
5220603 | Parker | Jun 1993 | A |
5263157 | Janis | Nov 1993 | A |
5263165 | Janis | Nov 1993 | A |
5265033 | Vajk et al. | Nov 1993 | A |
5265159 | Kung | Nov 1993 | A |
5274806 | Hill | Dec 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 |
5317729 | Mukherjee et al. | May 1994 | A |
5333152 | Wilber | Jul 1994 | A |
5333266 | Boaz et al. | Jul 1994 | A |
5370566 | Mitchell, Jr. et al. | Dec 1994 | A |
5377354 | Scannell et al. | Dec 1994 | A |
5386564 | Shearer et al. | Jan 1995 | A |
5388255 | Pytlik et al. | Feb 1995 | A |
5392390 | Crozier | Feb 1995 | A |
5404508 | Konrad et al. | Apr 1995 | A |
5406557 | Baudoin | Apr 1995 | A |
5410543 | Seitz et al. | Apr 1995 | A |
5416473 | Dulaney, III et al. | May 1995 | A |
5416842 | Aziz | May 1995 | A |
5420927 | Micali | May 1995 | A |
5425102 | Moy | Jun 1995 | A |
5434918 | Kung et al. | Jul 1995 | A |
5434994 | Shaheen et al. | Jul 1995 | A |
5436960 | Campana, Jr. et al. | Jul 1995 | A |
5438011 | Blalock et al. | Aug 1995 | A |
5438611 | Campana, Jr. et al. | Aug 1995 | A |
5440730 | Elmasri et al. | Aug 1995 | A |
5446888 | Pyne | Aug 1995 | A |
5452356 | Albert | Sep 1995 | A |
5452450 | Delory | Sep 1995 | A |
5479472 | Campana, Jr. et al. | Dec 1995 | A |
5481700 | Thuraisingham | Jan 1996 | A |
5483596 | Rosenow et al. | Jan 1996 | A |
5487100 | Kane | Jan 1996 | A |
5491752 | Kaufman et al. | Feb 1996 | A |
5493692 | Theimer et al. | Feb 1996 | A |
5495484 | Self et al. | Feb 1996 | A |
5495533 | Linehan et al. | Feb 1996 | A |
5495610 | Shing et al. | Feb 1996 | A |
5510777 | Pilc et al. | Apr 1996 | A |
5533019 | Jayapalan | Jul 1996 | A |
5537097 | Eriksson et al. | Jul 1996 | A |
5544320 | Konrad | Aug 1996 | A |
5544322 | Cheng et al. | Aug 1996 | A |
5557659 | Hyde-Thomson | Sep 1996 | A |
5559800 | Mousseau et al. | Sep 1996 | A |
5560005 | Hoover et al. | Sep 1996 | A |
5561795 | Sarkar | Oct 1996 | A |
5561797 | Gilles et al. | Oct 1996 | A |
5572528 | Shuen | Nov 1996 | A |
5572643 | Judson | Nov 1996 | A |
5579472 | Keyworth, II et al. | Nov 1996 | A |
5581749 | Hossain et al. | Dec 1996 | A |
5588009 | Will | Dec 1996 | A |
5588132 | Cardoza | Dec 1996 | A |
5590274 | Skarpelos et al. | Dec 1996 | A |
5596318 | Mitchell | Jan 1997 | A |
5598536 | Slaughter, III et al. | Jan 1997 | A |
5600834 | Howard | Feb 1997 | A |
5603054 | Theimer et al. | Feb 1997 | A |
5604491 | Coonley et al. | Feb 1997 | A |
5604788 | Tett | Feb 1997 | A |
5613012 | Hoffman et al. | Mar 1997 | A |
5613108 | Morikawa | Mar 1997 | A |
5623601 | Vu | Apr 1997 | A |
5625670 | Campana, Jr. et al. | Apr 1997 | A |
5627658 | Connors et al. | May 1997 | A |
5627829 | Gleeson et al. | May 1997 | A |
5627997 | Pearson et al. | May 1997 | A |
5630060 | Tang et al. | May 1997 | A |
5631946 | Campana, Jr. et al. | May 1997 | A |
5632011 | Landfield et al. | May 1997 | A |
5633810 | Mandal et al. | May 1997 | A |
5634053 | Noble et al. | May 1997 | A |
5638450 | Robson | Jun 1997 | A |
5641946 | Shim | Jun 1997 | A |
5644354 | Thompson et al. | Jul 1997 | A |
5647002 | Brunson | Jul 1997 | A |
5649195 | Scott et al. | Jul 1997 | A |
5652884 | Palevich | Jul 1997 | A |
5657390 | Elgamal et al. | Aug 1997 | A |
5664207 | Crumpler et al. | Sep 1997 | A |
5664228 | Mital | Sep 1997 | A |
5666530 | Clark et al. | Sep 1997 | A |
5666553 | Crozier | Sep 1997 | A |
5673322 | Pepe et al. | Sep 1997 | A |
5675782 | Montague et al. | Oct 1997 | A |
5678039 | Hinks et al. | Oct 1997 | A |
5680542 | Mulchandani et al. | Oct 1997 | A |
5682379 | Mahany et al. | Oct 1997 | A |
5682478 | Watson et al. | Oct 1997 | A |
5682524 | Freund et al. | Oct 1997 | A |
5684951 | Goldman et al. | Nov 1997 | A |
5684984 | Jones et al. | Nov 1997 | A |
5684990 | Boothby | Nov 1997 | A |
5687322 | Deaton et al. | Nov 1997 | A |
5701400 | Amado | Dec 1997 | A |
5701423 | Crozier | Dec 1997 | A |
5705995 | Laflin et al. | Jan 1998 | A |
5706211 | Beletic et al. | Jan 1998 | A |
5706427 | Tabuki | Jan 1998 | A |
5706502 | Foley et al. | Jan 1998 | A |
5710918 | Lagarde et al. | Jan 1998 | A |
5710922 | Alley et al. | Jan 1998 | A |
5713019 | Keaton | Jan 1998 | A |
5714943 | Rasor | Feb 1998 | A |
5715403 | Stefik | Feb 1998 | A |
5717925 | Harper et al. | Feb 1998 | A |
5721779 | Funk | Feb 1998 | A |
5721907 | Pyne | Feb 1998 | A |
5721908 | Lagarde et al. | Feb 1998 | A |
5721914 | DeVries | Feb 1998 | A |
5726893 | Schuchman et al. | Mar 1998 | A |
5727202 | Kucala | Mar 1998 | A |
5729735 | Meyering | Mar 1998 | A |
5732074 | Spaur et al. | Mar 1998 | A |
5737531 | Ehley | Apr 1998 | A |
5740231 | Cohn et al. | Apr 1998 | A |
5742668 | Pepe et al. | Apr 1998 | A |
5742905 | Pepe et al. | Apr 1998 | A |
5745360 | Leone et al. | Apr 1998 | A |
5745689 | Yeager et al. | Apr 1998 | A |
5751960 | Matsunaga | May 1998 | A |
5751971 | Dobbins et al. | May 1998 | A |
5752059 | Holleran et al. | May 1998 | A |
5752246 | Rogers et al. | May 1998 | A |
5754306 | Taylor et al. | May 1998 | A |
5754830 | Butts et al. | May 1998 | A |
5754954 | Cannon et al. | May 1998 | A |
5757901 | Hiroshige | May 1998 | A |
5757916 | MacDoran et al. | May 1998 | A |
5758088 | Bezaire et al. | May 1998 | A |
5758150 | Bell et al. | May 1998 | A |
5758354 | Huang et al. | May 1998 | A |
5758355 | Buchanan | 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 |
5787441 | Beckhardt | Jul 1998 | A |
5790790 | Smith et al. | Aug 1998 | A |
5790974 | Tognazzini | Aug 1998 | A |
5796806 | Birckbichler | Aug 1998 | A |
5799318 | Cardinal et al. | Aug 1998 | A |
5812671 | Ross, Jr. | Sep 1998 | A |
5812819 | Rodwin et al. | Sep 1998 | A |
5813016 | Sumimoto | Sep 1998 | A |
5815081 | Motohashi | Sep 1998 | A |
5819172 | Campana, 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 |
5831664 | Wharton et al. | Nov 1998 | A |
5838252 | Kikinis | Nov 1998 | A |
5838926 | Yamagishi | Nov 1998 | A |
5844969 | Goldman et al. | Dec 1998 | A |
5850219 | Kumomura | Dec 1998 | A |
5850444 | Rune | Dec 1998 | A |
5857201 | Wright et al. | Jan 1999 | A |
5862321 | Lamming et al. | Jan 1999 | A |
5862325 | Reed et al. | Jan 1999 | A |
5867660 | Schmidt et al. | Feb 1999 | A |
5878434 | Draper et al. | Mar 1999 | A |
5889845 | Staples 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 |
5913040 | Rakavy et al. | Jun 1999 | A |
5917629 | Hortensius et al. | Jun 1999 | A |
5928329 | Clark et al. | Jul 1999 | A |
5937161 | Mulligan et al. | Aug 1999 | A |
5941954 | Kalajan | Aug 1999 | A |
5941956 | Shirakihara et al. | Aug 1999 | A |
5948066 | Whalen et al. | Sep 1999 | A |
5951636 | Zerber | Sep 1999 | A |
5953322 | Kimball | Sep 1999 | A |
5959621 | Nawaz et al. | Sep 1999 | A |
5960406 | Rasansky et al. | Sep 1999 | A |
5961590 | Mendez et al. | Oct 1999 | A |
5964833 | Kikinis | Oct 1999 | A |
5966663 | Gleason | Oct 1999 | A |
5966714 | Huang et al. | 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 |
5974449 | Chang et al. | Oct 1999 | A |
5978689 | Tuoriniemi et al. | Nov 1999 | A |
5978837 | Foladare et al. | Nov 1999 | A |
5983073 | Ditzik | Nov 1999 | A |
5987100 | Fortman et al. | Nov 1999 | A |
5987508 | Agraharam et al. | Nov 1999 | A |
5995597 | Woltz et al. | Nov 1999 | A |
6000000 | Hawkins et al. | Dec 1999 | A |
6002427 | Kipust | Dec 1999 | A |
6002769 | McGough | Dec 1999 | A |
6006274 | Hawkins et al. | Dec 1999 | A |
6009455 | Doyle | Dec 1999 | A |
6014429 | LaPorta et al. | Jan 2000 | A |
6016478 | Zhang 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 |
6035104 | Zahariev | Mar 2000 | A |
6044205 | Reed et al. | Mar 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 | Kelly | Jun 2000 | A |
6084969 | Wright et al. | Jul 2000 | A |
6085192 | Mendez et al. | Jul 2000 | A |
6085231 | Agraharam 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 |
6115754 | Landgren | Sep 2000 | A |
6119167 | Boyle et al. | Sep 2000 | A |
6125281 | Wells et al. | Sep 2000 | A |
6125369 | Wu et al. | Sep 2000 | A |
6128739 | Fleming, III | Oct 2000 | A |
6130892 | Short et al. | Oct 2000 | A |
6131096 | Ng et al. | Oct 2000 | A |
6131116 | Riggins et al. | Oct 2000 | A |
6134432 | Holmes et al. | Oct 2000 | A |
6138089 | Guberman | Oct 2000 | A |
6138124 | Beckhardt | Oct 2000 | A |
6138146 | Moon et al. | Oct 2000 | A |
6141690 | Weiman | Oct 2000 | A |
6144671 | Perinpanathan et al. | Nov 2000 | A |
6144997 | Lamming et al. | Nov 2000 | A |
6151606 | Mendez | Nov 2000 | A |
6154839 | Arrow et al. | Nov 2000 | A |
6157318 | Minata | Dec 2000 | A |
6157630 | Adler et al. | Dec 2000 | A |
6157950 | Krishnan | Dec 2000 | A |
6161140 | Moriya | Dec 2000 | A |
6163274 | Lindgren | Dec 2000 | A |
6167379 | Dean et al. | Dec 2000 | A |
6170057 | Inoue et al. | Jan 2001 | B1 |
6178331 | Holmes et al. | Jan 2001 | B1 |
6185551 | Birrell et al. | Feb 2001 | B1 |
6185603 | Henderson et al. | Feb 2001 | B1 |
6195533 | Tkatch 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 |
6222942 | Martin | 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 |
6263201 | Hashimoto et al. | Jul 2001 | B1 |
6272545 | Flanagin et al. | Aug 2001 | B1 |
6275848 | Arnold | Aug 2001 | B1 |
6275850 | Beyda et al. | Aug 2001 | B1 |
6289212 | Stein et al. | Sep 2001 | B1 |
6292668 | Alanara et al. | Sep 2001 | B1 |
6311282 | Nelson et al. | Oct 2001 | B1 |
6313734 | Weiss et al. | Nov 2001 | B1 |
6314108 | Ramasubramani et al. | Nov 2001 | B1 |
6314519 | Davis et al. | Nov 2001 | B1 |
6317592 | Campana et al. | Nov 2001 | B1 |
6324544 | Alam et al. | Nov 2001 | B1 |
6327046 | Miyamoto et al. | Dec 2001 | B1 |
6330244 | Swartz et al. | Dec 2001 | B1 |
6330618 | Hawkins et al. | Dec 2001 | B1 |
6332156 | Cho et al. | Dec 2001 | B1 |
6333973 | Smith et al. | Dec 2001 | B1 |
6356956 | Deo et al. | Mar 2002 | B1 |
6360272 | Lincke et al. | Mar 2002 | B1 |
6363352 | Dailey et al. | Mar 2002 | B1 |
6370566 | Discolo et al. | Apr 2002 | B2 |
6389455 | Fuisz | May 2002 | B1 |
6389457 | Lazaridis et al. | May 2002 | B2 |
6400958 | Isomursu et al. | Jun 2002 | B1 |
6401113 | Lazaridis et al. | Jun 2002 | B2 |
6438585 | Mousseau et al. | Aug 2002 | B2 |
6442589 | Takahashi et al. | Aug 2002 | B1 |
6449287 | Leuca et al. | Sep 2002 | B1 |
6463463 | Godfrey et al. | Oct 2002 | B1 |
6463464 | Lazaridis et al. | Oct 2002 | B1 |
6496704 | Yuan | Dec 2002 | B2 |
6505055 | Kahn et al. | Jan 2003 | 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 |
6728786 | Hawkins et al. | Apr 2004 | B2 |
6757698 | McBride et al. | Jun 2004 | B2 |
6763202 | Maeda | Jul 2004 | B2 |
6990523 | Wu | Jan 2006 | B2 |
20010001552 | Vong et al. | May 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 |
20010054115 | Ferguson et al. | Dec 2001 | A1 |
20020010748 | Kobayashi et al. | Jan 2002 | A1 |
20020059380 | Biliris et al. | May 2002 | A1 |
20020099719 | Schwitters et al. | Jul 2002 | A1 |
20030097361 | Huang et al. | May 2003 | A1 |
Number | Date | Country |
---|---|---|
007843498 | Feb 1999 | AU |
7843498 | Feb 1999 | AU |
2179349 | Dec 1997 | CA |
001552 | May 1979 | EP |
0617373 | Sep 1994 | EP |
0736989 | Oct 1996 | EP |
0772327 | May 1997 | EP |
0772327 | Jun 1997 | EP |
0777394 | Jun 1997 | EP |
0788287 | Aug 1997 | EP |
0793387 | Sep 1997 | EP |
0793387 | Sep 1997 | EP |
0793387 | Dec 1997 | EP |
0825788 | Feb 1998 | EP |
0825788 | Feb 1998 | EP |
0825788 | Feb 1998 | EP |
0838774 | Apr 1998 | EP |
0838934 | Apr 1998 | EP |
0918417 | May 1999 | EP |
0918417 | May 1999 | EP |
0930766 | Jul 1999 | EP |
0986225 | Mar 2000 | EP |
1 096 725 | May 2001 | EP |
9214556 | Aug 1997 | JP |
9305155 | Nov 1997 | JP |
11289346 | Oct 1999 | JP |
9619064 | Jun 1996 | WO |
WO9619064 | Jun 1996 | WO |
9726709 | Jul 1997 | WO |
9727717 | Jul 1997 | WO |
WO9726709 | Jul 1997 | WO |
WO9727717 | Jul 1997 | WO |
WO9728518 | Aug 1997 | WO |
WO9703341 | Aug 1997 | WO |
9732251 | Sep 1997 | WO |
9733421 | Sep 1997 | WO |
WO9732251 | Sep 1997 | WO |
WO9733421 | Sep 1997 | WO |
9741654 | Nov 1997 | WO |
9744942 | Nov 1997 | WO |
WO9741654 | Nov 1997 | WO |
WO9744942 | Nov 1997 | WO |
WO9749251 | Dec 1997 | WO |
9800787 | Jan 1998 | WO |
WO9800787 | Jan 1998 | WO |
WO9807897 | Jan 1998 | WO |
9821911 | May 1998 | WO |
9823108 | May 1998 | WO |
WO9821911 | May 1998 | WO |
WO9823108 | May 1998 | WO |
9826344 | Jun 1998 | WO |
9848560 | Oct 1998 | WO |
9905620 | Feb 1999 | WO |
9905813 | Feb 1999 | WO |
9906900 | Feb 1999 | WO |
9917505 | Apr 1999 | WO |
9919988 | Apr 1999 | WO |
9919988 | Apr 1999 | WO |
9936870 | Jul 1999 | WO |
9945484 | Sep 1999 | WO |
9945684 | Sep 1999 | WO |
9948312 | Sep 1999 | WO |
9950974 | Oct 1999 | WO |
9963709 | Dec 1999 | WO |
0011567 | Mar 2000 | WO |
0011832 | Mar 2000 | WO |
0020994 | Apr 2000 | WO |
WO 0031931 | Jun 2000 | WO |
WO 0041359 | Jul 2000 | WO |
WO 0049819 | Aug 2000 | WO |
WO 0101264 | Jan 2001 | WO |
0113572 | Feb 2001 | WO |
WO 0122669 | Mar 2001 | WO |
0171539 | Sep 2001 | WO |
WO0167716 | Sep 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20030187938 A1 | Oct 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09087623 | May 1998 | US |
Child | 10240960 | US | |
Parent | 09545963 | Apr 2000 | US |
Child | 09087623 | US |