US 6,779,019 B1Grant
System and method for pushing information from a host system to a mobile data communication device
Issue Date:2004-08-17
•16 Claims
•15 Drawing Sheets
Abstract
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 replicate actions at the host system that have been executed at the mobile data communication device.
Metadata
Assignee
- Research In Motion Limited
Inventors
- Gary P. Mousseau
- Tabitha Ferguson
- Barry Linkert
- Raymond Vander Veen
- David Castell
- Mihal Lazaridis
Application Information
Application Number:US 09/545,963
Filing Date:2000-04-10
Priority Date:1998-05-29
Art Unit:7
Classifications
IPC:
G06F 1516G06F 1730
Field of Search:
709206709207709249709245709253707201707203340 721340 729340 75145555614555562
Patent Drawings (15 sheets)
Description
Cross Reference to Related Application
[0002] This application is a continuation-in-part of U.S. Utility application Ser. No. 09/087,623, entitled System and Method for Pushing Information from a Host System to a Mobile Data Communication Device, filed May 29, 1998, and assigned to the assignee of the present invention now U.S. Pat. No. 6,219,694.
Background of the Invention
[0003] 1. Field of the Invention
[0004] The present invention is directed toward the field of replicating (or synchronizing) information from a host system where the information is normally stored to a mobile data communication device. More specifically, the system and method of the present invention provide an event-driven redirection computer program (“redirector program”) operating at the host system, which, upon sensing a particular user-defined event has occurred, redirects user-selected data items from the host system to the user's mobile data communication device. 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.
[0005] Instead of warehousing (or storing) the user's data items at the host system and then “synchronizing” the mobile data communication device to data items stored at the host system when the mobile device requests that such items of information be communicated to it, the present invention employs a “push” paradigm that continuously packages and retransmits the user-selected items of information to the mobile data communication device in response to a triggering event detected at the host system. Wireless mobile data communications devices, especially those that can return a confirmation signal to the host that the pushed data has been received are especially well suited for this type of push paradigm.
[0006] Once the information is pushed to the device, the user can then read the information and ‘file’ the information into its appropriate folder based on the contents of the information. Alternatively, the user can perform some other operation on the information. These operations, as well as the user's folder hierarchy for storing information at the mobile device, are then replicated back (synchronized) to the host system, which then automatically organizes the user's information into the same folder hierarchies (or replicates the other operations performed at the mobile device), thus saving the user from doing the action a second time at the host system. The synchronization of the message operations can be carried in real-time as the operations are being executed at the mobile device, or in a batch process when the mobile device is electrically coupled to the host system.
[0007] 2. Description of the Related Art
[0008] 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.
[0009] 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.
[0010] 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.
[0011] 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.
Summary of the Invention
[0012] 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 replicate actions at the host system that have been executed at the mobile data communication device.
[0013] As used in this application, the term host system refers to the computer where the redirector software is operating. In the preferred embodiment of the present invention, the host system is a user's desktop PC, although, alternatively, the host system could be a network server connected to the user's PC via a local-area network (“LAN”), or could be any other system that is in communication with the user's desktop PC.
[0014] 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. Once the data items are 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. Once the user acts 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.
[0015] 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.
[0016] 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, 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. 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.
[0017] 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.
[0018] 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.
[0019] 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.
[0020] 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.
[0021] 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.
[0022] 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.
[0023] 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.
[0024] 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.
[0025] 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.
[0026] 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.
[0027] 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.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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.
[0034] 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.
Brief Description of the Drawings
[0035] FIG. 1 is a system diagram showing the redirection of user data items from a user's desktop PC (host system) to the user's mobile data communication device, where the redirector software is operating at the user's desktop PC.
[0036] FIG. 2 is a system diagram showing the redirection of user data items from a network server (host system) to the user's mobile data communication device, where the redirector software is operating at the server.
[0037] FIG. 3 is a block diagram showing the interaction of the redirector software with other components of the host system in FIG. 1 (the user's desktop PC) to enable the pushing of information from the host system to the user's mobile data communication device.
[0038] FIG. 4 is a flow chart showing the steps carried out by the redirector software operating at the host system.
[0039] FIG. 5 is a flow chart showing the steps carried out by the mobile data communication device to interface with the redirector software operating at the host system.
[0040] FIG. 6 is a schematic diagram of the logical structure of a folder and a message.
[0041] FIG. 7 is a flow chart showing the steps of synchronizing folders and messages between the host system and the mobile data communication device.
[0042] FIG. 8 is a flow chart showing the steps of assigning IDs to folders.
[0043] FIG. 9 is a flow chart showing the steps of retrieving messages from the store.
[0044] FIGS. 10 A and B is a flow chart more specifically showing the steps of synchronizing messages between the host system and the mobile data communication device.
[0045] FIG. 11 is a flow chart showing the steps of attaching a folder ID to a message.
[0046] FIG. 12 is a flow chart showing the steps of moving a message locally on a device.
[0047] FIG. 13 is a flow chart showing the steps of sending a move message to the host system after a message has been moved on the mobile device.
[0048] FIG. 14 is a flow chart showing the steps of sending a move message from the host system to the mobile device after a message has been moved on the host system.
[0049] FIG. 15 is a flow chart showing the steps of acting upon the move message command of FIG. 13 at the device.
[0050] FIG. 16 is a flow chart showing the steps of acting upon the message move command of FIG. 14.
[0051] FIG. 17 is a flow chart showing the steps of deleting a message.
[0052] FIG. 18 is a flow chart showing the steps of purging a message.
[0053] FIG. 19 is a flow chart showing the steps of generating a folder list for redirecting messages received at a store.
[0054] FIG. 20 is a flow chart showing the steps of redirecting a message received and filed in the folder list of FIG. 19.
Detailed Description of the Drawings
[0055] Referring now to the drawings, FIG. 1 is an example system diagram showing the redirection of user data items (such as message A or C) from a user's office PC (host system) 10 to the user's mobile data communication device 24, where the redirector software 12 is operating at the user's PC. Message A in FIG. 1 represents an internal message sent from desktop 26 to the user's host system 10 via LAN 14. Message C in FIG. 1 represents an external message from a sender that is not directly connected to LAN 14, such as the user's mobile data communication device 24, some other user's mobile device (not shown), or any user connected to the Internet 18. Message C also represents a command message from the user's mobile data communication device 24 to the host system 10. As described in more detail in FIG. 3, the host system 10 preferably includes, along with the typical hardware and software associated with a workstation or desktop computer, the redirector program 12, a TCP/IP subsystem 42, a primary message store 40, an E-mail subsystem 44, a screen saver subsystem 48, and a keyboard subsystem 46.
[0056] In FIG. 1, the host system 10 is the user's desktop system, typically located in the user's office. The host system 10 is connected to a LAN 14, which also connects to other computers 26, 28 that may be in the user's office or elsewhere. The LAN 14, in turn, is connected to a wide area network (“WAN”) 18, preferably the Internet, which is defined by the use of the Transmission Control Protocol/Internet Protocol (“TCP/IP”) to exchange information, but which, alternatively could be any other type of WAN. The connection of the LAN 14 to the WAN 18 is via high bandwidth link 16, typically a T1 or T3 connection. The WAN 18, in turn, is connected to a variety of gateways 20, via connections 32. A gateway forms a connection or bridge between the WAN 18 and some other type of network, such as an RF wireless network, cellular network, satellite network, or other synchronous or asynchronous land-line connection.
[0057] In the example of FIG. 1, a wireless gateway 20 is connected to the Internet for communicating via wireless link 22 to a plurality of wireless mobile data communication devices 24. Also shown in FIG. 1 is machine 30, which could be a FAX machine, a printer, a system for displaying images (such as video) or a machine capable of processing and playing audio files, such as a voice mail system. The present invention includes the ability to redirect certain message attachments to such an external machine 30 if the redirector program configuration data reflects that the mobile device 24 cannot receive and process the attachments, or if the user has specified that certain attachments are not to be forwarded to mobile device 24, even if such device can process those attachments. By way of example, consider an E-mail sent to a user that includes three attachments—a word processing document, a video clip and an audio clip. The redirection program could be configured to send the text of the E-mail to the remote device, to send the word processing document to a networked printer located near the user, to send the video clip to a store accessible through a secure connection through the Internet, and to send the audio clip to the user's voice mail system. This example is not intended to limit the breadth and scope of the invention, but rather to illustrate the variety of possibilities embodied in the redirection concept.
[0058] 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. FIG. 4 describes the basic method steps of the redirector program 12, and FIG. 5 describes the steps of the corresponding program operating at the mobile device 24.
[0059] 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 FIGS. 1-4.
[0060] 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.
[0061] 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.
[0062] FIG. 1 shows an E-mail message A being communicated over LAN 14 from computer 26 to the user's desktop system 10 (also shown in FIG. 1 is an external message C, which could be an E-mail message from an Internet user, or could be a command message from the user's mobile device 24). Once the message A (or C) reaches the primary message store of the host system 10, it can be detected and acted upon by the redirection software 12. The redirection software 12 can use many methods of detecting new messages. The preferred method of detecting new messages is using Microsoft's® Messaging API (MAPI), in which programs, such as the redirector program 12, register for notifications or ‘advise syncs’ when changes to a mailbox take place. Other methods of detecting new messages could also be used with the present invention.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] In the example of FIG. 1, if desktop system 26 was operated by a user on the preferred list of host system 10, and the preferred list option was activated, then message A would be redirected. If, however, desktop 26 was operated by a user not on the host system's preferred list, then message A would not be redirected, even if the user of the host system had configured the redirector to push messages of type A. The user of the host system 10 can configure the preferred list directly from the desktop system, or, alternatively, the user can send a command message (such as C) from the mobile device 24 to the desktop system 10 to activate the preferred list mode, or to add or delete certain senders or message characteristics from the preferred list that was previously configured. It should be appreciated that a redirection program could combine message characteristics and preferred sender lists to result in a more finely-tuned filter. Messages marked as low priority or that are simple return receipts or message read receipts, for example, could always be suppressed from redirection while messages from a particular sender would always be redirected.
[0067] 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 FIG. 2). The wireless gateway 20 requires this outer envelope information B in order to know where to send the redirected message A. Once the message (A in B) is received by the mobile device 24, the outer envelope B is removed and the original message A is placed in the secondary memory store within the mobile device 24. By repackaging and removing the outer envelope in this manner, the present invention causes the mobile computer 24 to appear to be at the same physical location as the host system 10, thus creating a transparent system.
[0068] 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.
[0069] 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.
[0070] FIG. 2 is an alternative system diagram showing the redirection of user data items from a network server 11 to the user's mobile data communication device 24, where the redirector software 12 is operating at the server 11. This configuration is particularly advantageous for use with message servers such as Microsoft's® Exchange Server, which is normally operated so that all user messages are kept in one central location or mailbox store on the server instead of in a store within each user's desktop PC. This configuration has the additional advantage of allowing a single system administrator to configure and keep track of all users having messages redirected. If the system includes encryption keys, these too can be kept at one place for management and update purposes.
[0071] 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.
[0072] As shown in FIG. 2, desktop system 26 generates a message A that is transmitted to and stored at the host system 11, which is the network server operating the redirector program 12. The message A is for desktop system 10, but in this embodiment, user messages are stored at the network server 11. When an event occurs at desktop system 10, an event trigger is generated and transmitted to the network server 11, which then determines who the trigger is from, whether that desktop has redirection capabilities, and if so, the server (operating the redirector program) uses the stored configuration information to redirect message A to the mobile computer 24 associated with the user of desktop system 10.
[0073] As described above with reference to FIG. 1, message C could be either a command message from a user's mobile data communication device 24, or it could be a message from an external computer, such as a computer connected to the Internet 18. If the message C is from an Internet computer to the user's desktop system 10, and the user has redirection capabilities, then the server 11 detects the message C, repackages it using electronic envelope B, and redirects the repackaged message (C in B) to the user's mobile device 24. If the message C is a command message from the user's mobile device 24, then the server 11 simply acts upon the command message.
[0074] Turning now to FIG. 3, a block diagram showing the interaction of the redirector software 12 with additional components of the host system 10 of FIG. 1 (the desktop PC) to enable more fully the pushing of information from the host system 10 to the user's mobile data communication device 24 is set forth. These additional components are illustrative of the type of event-generating systems that can be configured and used with the redirector software 12, and of the type of repackaging systems that can be used to interface with the mobile communication device 24 to make it appear transparent to the user.
[0075] 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.
[0076] The method steps carried out by the redirector program 12 are described in more detail in FIG. 4. The basic functions of this program are: (1) configure and setup the user-defined event trigger points that will start redirection; (2) configure the types of user data items for redirection and optionally configure a preferred list of senders whose messages are to be redirected; (3) configure the type and capabilities of the user's mobile data communication device; (4) receive messages and signals from the repackaging systems and the event generating systems; and (5) command and control the redirection of the user-selected data items to the mobile data communication device via the repackaging systems. Other functions not specifically enumerated could also be integrated into this program.
[0077] 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.
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] FIGS. 4 and 5, set forth, respectively, flow charts showing the steps carried out by the redirector software 12 operating at the host system 10, and the steps carried out by the mobile data communication device 24 in order to interface with the host system. Turning first to FIG. 4, at step 50, the redirector program 12 is started and initially configured. The initial configuration of the redirector 12 includes: (1) defining the event triggers that the user has determined will trigger redirection; (2) selecting the user data items for redirection; (3) selecting the repackaging sub-system, either standard E-Mail, or special-purpose technique; (4) selecting the type of data communication device, indicating whether and what type of attachments the device is capable of receiving and processing, and inputting the address of the mobile device; and (5) configuring the preferred list of user selected senders whose messages are to be redirected.
[0083] FIG. 4 sets forth the basic steps of the redirector program 12 assuming it is operating at a desktop system 10, such as shown in FIG. 1. If the redirector 12 is operating at a network server 11, as shown in FIG. 2, then additional configuration steps may be necessary to enable redirection for a particular desktop system 10, 26, 28 connected to the server, including: (1) setting up a profile for the desktop system indicating its address, events that will trigger redirection, and the data items that are to be redirected upon detecting an event; (2) maintaining a storage area at the server for the data items; and (3) storing the type of data communication device to which the desktop system's data items are to be redirected, whether and what type of attachments the device is capable of receiving and processing, and the address of the mobile device.
[0084] 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.
[0085] 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 FIG. 4, after step 68, the program could, if operating in the preferred list mode, determine whether the sender of a particular data item is on the preferred list, and if not, then the program would skip over steps 70 and 72 and proceed directly back to step 56. If the sender was on the preferred list, then control would similarly pass to steps 70 and 72 for repackaging and transmission of the message from the preferred list sender.
[0086] FIG. 5 sets forth the method steps carried out by the user's mobile data communication device 24 in order to interface to the redirector program 12 of the present invention. At step 80 the mobile software is started and the mobile device 24 is configured to operate with the system of the present invention, including, for example, storing the address of the user's desktop system 10.
[0087] At step 82, the mobile device waits for messages and signals 84 to be generated or received. Assuming that the redirector software 12 operating at the user's desktop system 10 is configured to redirect upon receiving a message from the user's mobile device 24, at step 86, the user can decide to generate a command message that will start redirection. If the user does so, then at step 88 the redirection message is composed and sent to the desktop system 10 via the wireless network 22, through the wireless gateway 20, via the Internet 18 to the LAN 14, and is finally routed to the desktop machine 10. In this situation where the mobile device 24 is sending a message directly to the desktop system 10, no outer wrapper is added to the message (such as message C in FIGS. 1 and 2). In addition to the redirection signal, the mobile device 24 could transmit any number of other commands to control the operation of the host system, and in particular the redirector program 12. For example, the mobile 24 could transmit a command to put the host system into the preferred list mode, and then could transmit additional commands to add or subtract certain senders from the preferred list. In this manner, the mobile device 24 can dynamically limit the amount of information being redirected to it by minimizing the number of senders on the preferred list. Other example commands include: (1) a message to change the configuration of the host system to enable the mobile device 24 to receive and process certain attachments; and (2) a message to instruct the host system to redirect an entire data item to the mobile device in the situation where only a portion of a particular data item has been redirected.
[0088] Turning back to FIG. 5, if the user signal or message is not a direct message to the desktop system 10 to begin redirection (or some other command), then control is passed to step 90, which determines if a message has been received. If a message is received by the mobile, and it is a message from the user's desktop 10, as determined at step 92, then at step 94 a desktop redirection flag is set “on” for this message, and control passes to step 96 where the outer envelope is removed. Following step 96, or in the situation where the message is not from the user's desktop, as determined at step 92, control passes to step 98, which displays the message for the user on the mobile device's display. The mobile unit 24 then returns to step 82 and waits for additional messages or signals.
[0089] 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.
[0090] 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.
[0091] Organizing and storing messages in the mobile device 24 and the host system 10 is set forth in FIGS. 6 through 18. The mobile device 24 preferably includes a hierarchical folder system, as does the host system 10. The user can select from multiple levels of folders to find a certain folder. For example, the user can organize messages into categories such as friends, co-workers, contacts, and “to do” list on the mobile device 24 and at the host system 10. Software on the mobile device 24 and the host system 10 organizes the messages so that filing a message on either the mobile device 24 or the host system 10 will be recognized at the other end either by commands sent through the redirector program or by synchronizing the mobile device with the host system. Synchronization can occur, for example, by plugging the mobile device into an interface cradle coupled to the host system or through a wireless device-to-host interface.
[0092] FIG. 6 sets forth a preferred message structure 120 and folder structure 130 for messages and folders that are stored on the host system 10 and the mobile device 24. The message structure 120 includes a message body and a message header. The message header preferably includes tags such as a message ID and a folder ID. The message ID is a unique tag that is associated with a single message. The message ID is assigned to a message when the message is received in the store. The folder ID is a tag that contains the unique ID of the folder in which the message is to be stored.
[0093] 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.
[0094] FIG. 7 is a flow chart illustrating the basic steps of synchronizing folders and messages between the host system 10 and the mobile device 24. Synchronization starts in step 140 when the mobile device 24 is coupled to the host system 10 by, for example, (1) placing the device in an interface cradle or a suitable equivalent; or (2) initiating an over-the-wireless-network synchronization. In this step, the folder hierarchy is received and tagged and the folder list is created in step 142 from a store at the host system 10. In step 144, the mobile device 24 is updated using the list of folders from the store. After the folders on the mobile device are updated 144 to match the folder structures 130 in the host system 10, the messages stored in the host system 10 are retrieved in step 146. The messages in the mobile device 24 are similarly retrieved in step 148. Step 150 compares the unique message IDs of messages in the mobile device 24 and the host system 10 to find similar messages. Once similar messages are found on the mobile device 24 and the host system 10, step 152 determines whether or not a message has been moved within the folder system. When one of the two messages (host message and mobile device message) is determined to have been moved, the other message is moved to the folder that matches the folder ID of the moved message in step 154. All similar messages from the mobile device 24 and the host system 10 are checked to determine 152 where the messages should be placed and moved 154 accordingly.
[0095] 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.
[0096] FIGS. 8 through 18 illustrate in more detail the steps required to synchronize the messages and folders of the mobile device 24 to the host system 10. FIG. 8 sets forth the method steps carried out by the host system 10 to assign folder IDs to the folders (step 142 from FIG. 7). When the mobile device 24 is coupled with 160 the host system 10, the last assigned folder ID is retrieved from the mobile device 24 at step 162. A “special” folder list is retrieved in step 164 from the store of the host system 10. A “special” folder is a folder such as a deleted folder or an inbox folder where specific rules are set for managing messages within the folder. Based on the hierarchical structure, the host system 10 gets the top folder in step 166 and checks if the top folder is flagged in step 168. If the top folder is not flagged, step 170 assigns a folder ID to the folder based on the last assigned number retrieved in step 162. Once the top folder is assigned an ID number, the top folder is checked against the special folders and assigned a folder type in step 172.
[0097] 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.
[0098] FIG. 9 sets forth the steps of retrieving the messages from the host system 10 as shown in step 146 of FIG. 7. Step 200 retrieves the list of messages from the store that have the unique IDs assigned to them. The message is checked for a folder ID in step 202. If a folder ID is not assigned, the current folder ID is assigned to the message in step 204. Step 206 checks the folder ID of the message against the current folder ID to see if they match. If the current folder ID and the folder ID on the message do not match, a move flag is set in step 208. The current folder ID is indicated in step 210, the next message is retrieved in step 212, and the next message is returned to step 202. Once all messages with unique IDs have been retrieved in step 212, the process ends in step 214. The list of messages with unique IDs retrieved from the store is referred to as messages ‘A’.
[0099] The steps set forth in FIG. 9 are repeated for the mobile device 24. The messages from the mobile device 24 are referred to as messages ‘B’. Once these steps have been accomplished, the folder structure synchronization process 136 includes a list of all unique messages ‘B’ and ‘A’ in the mobile device 24 and the host system 10, respectively. For each message in the list, a move flag is either on or off. The move flags of equivalent messages in the set of messages ‘A’ and ‘B’ are compared in FIGS. 10A and 10B to determine the proper folder placement of the message.
[0100] FIGS. 10A and 10B set forth the steps of synchronizing the messages between the host system 10 and the mobile device 24. Step 220 of FIG. 10 checks to see if there is a match between the message IDs of the current message ‘A’ and the first message ‘B’. If the IDs do not match, step 222 updates message ‘B’ to the next message in the list of ‘B’ messages. Once a matching message is found, step 224 checks if the move flag for message ‘A’ is on and the move flag for message ‘B’ is off. If this is the case, message ‘B’ is moved to the folder having the folder ID of message ‘A’ on the mobile device 24 in step 226. If the move flag status is not equal to the check in step 224, step 230 checks for a different flag status.
[0101] 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’ a nd ‘B’ remain in their current folders as shown in step 242.
[0102] 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.
[0103] FIG. 11 sets forth the preferable method steps of assigning an ID to a newly received message at the host system for redirection. When a new message is received in step 260, the message is tagged with a unique ID in step 262. Once the message has a unique ID, step 264 checks if the folder in which the message is to be stored has an assigned folder ID. If the folder has an ID, the folder ID of the message structure 120 for the new message is set to the folder ID value in step 266. If the folder does not have an ID, the folder ID of the message structure 120 for the new message is set to zero as shown in step 268. After the folder ID has been set in step 266 or 268, the message is sent to the device by the redirector in step 270.
[0104] 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 FIG. 12 and the method steps of FIGS. 13-17 show the steps taken at the host system 10 and the mobile device 24 when the user has initiated a move on at either the host system or mobile device.
[0105] As shown in FIG. 12, to file a message on the mobile device 24, the message is selected in step 280. A folder to place the message is selected in step 282. The selected message is moved to the selected folder in step 284. The folder ID of the selected folder is assigned to the folder ID of the message structure 120 for the selected message in step 286 and the move flag status is set in step 288. Finally, the message has been properly moved and the steps end at step 290.
[0106] Once the message has been moved on either the mobile device 24 or the host system 10, the redirector preferably attempts to move the identical message to the corresponding folder on the other end to provide a true mirrored (i.e., synchronized) organization of information as illustrated in FIGS. 13 and 16. Shown in FIG. 13 are the preferred steps in sending a move signal from the mobile device 24 to the host system 10 via the wireless network 22 as disclosed herein. The preferred steps are referred hereinafter to as the “over-the-air-move” process. After the message has been moved in step 292 of FIG. 13, step 294 sends a command to move the message x to the folder y and waits for a confirmation signal in step 296. Step 298 checks if the redirector successfully moved the message. If the message was moved, the folder ID of message x is updated in step 300. If the message was not moved, then the redirector proceeds with its normal operation in step 302, and the message will be moved during synchronization.
[0107] The over-the-air-move process is preferably in the control of the user. In circumstances where the user desires to limit bandwidth consumption, it may be desirable to switch the over-the-air-move feature off and to leave synchronization of information organization until device-host synchronization through the wired interface cradle. In another embodiment of the present invention, the mobile device 24 bundles together and compresses the various move commands (or other operations) created during the day and transmits the same during non-peak transmission times.
[0108] Moving a message on the mobile device 24 requires a move command to be sent to the host system 10 as described above. But, moving a message on the host system requires both checking to see if the message was redirected to the mobile device 24 and if the folder the message was moved to exists on the mobile device 24. These steps are set forth in FIG. 14. Once the redirector has received a move message command from the host system 10 that a message has been moved in step 304, the redirector checks to see if the message has been redirected to the device in step 306. If the message was not redirected to the mobile device 24, the redirector does not attempt to send the move command and proceeds with its normal operation at step 308. If the message was delivered to the mobile device 24, then step 310 determines if the folder that the message was moved to has a folder ID. The folder may not have an ID if, for example, the user created the folder at some point after the last synchronization. If the folder does not have a folder ID, the redirector does not forward the move message command and the redirector proceeds with its normal operation at step 314. The move will be made when the mobile device 24 and the host system 10 are synchronized and the folder with the correct folder structure 130 is generated.
[0109] If the folder ID does exist for the folder, then the move message command is sent in step 316. The redirector awaits acknowledgement of the move in step 318. If the acknowledgement is not received, the redirector proceeds with its normal operation at step 320, or alternatively, attempts to retransmit the move message command. If acknowledgement of the move is received, step 322 tags the message with the current folder ID.
[0110] FIG. 15 shows the steps performed at the mobile device 24 when a move message command is received from the host system 10. Similarly, FIG. 16 shows the steps performed at the host system 10 when a move command is received from the mobile device 24. Both functions require (1) receiving a move command, (2) checking to see if the command may be executed, and (3) reacting with a negative confirmation or moving the message and positively confirming.
[0111] Step 330 of FIG. 15 occurs when the mobile device 24 receives a move command. Step 332 checks if the folder exists on the mobile device 24. If the folder does not exist, a negative confirmation is sent to the host system 10 in step 334. Otherwise, the mobile device 24 is tagged 336 with the new folder ID, the message's folder ID is updated in step 338, and a positive confirmation is sent to the host system 10 in step 340.
[0112] FIG. 16 shows the steps of acting upon a move message command at the host system 10. The move command is received 350. Step 352 locates the message in the store. Step 354 determines if the folder is located in the store. If the folder is not located in the store, a negative confirmation is sent to the mobile device 24 in step 356. If the folder is located in the store, the message is moved 360 to the folder. Step 362 determines if the move was successful. A successful move updates the message's folder ID in step 364 while an unsuccessful move sends a negative confirmation 370 to the mobile device 24.
[0113] Special folders can require a special set of instructions to deal with message management. For example, a deleted folder can be created to detect deletions at either the mobile device 24 or the host system 24. When the message is deleted, the redirector must check to see if the user has previously chosen to delete messages off of both the mobile device 24 and the host system 10 when it is deleted on one of these two.
[0114] The steps set forth in FIG . 17 show how the device accordingly handles a delete request. The delete process is started 380 when the user has selected a message for deleting. The message is selected 382 and then deleted 384 by the software on the mobile device 24. The software on the device then determines 386 if the delete feature is set to delete messages on both the mobile device 24 and the host system 10. If the delete feature is not set for the host system and the device, the software simply deletes the message locally 390. If the delete feature is set for the host system and the device, the folder ID of the deleted folder is assigned to the message in step 392. The move flag for the message is set on 394 so that the deletion can be detected on the other device. The delete process is completed 396. In the case where the user deletes a message on the host system, the deletion of that message will be reflected upon synchronization.
[0115] Finally, the folder management system controls wasted use of resources by purging the earliest messages once allocated space is exceeded, as shown in FIG. 18. The purge process is started in step 400. The software determines 402 if storage requirements exceed the storage space allocated for messages. If the storage requirements are not exceeded, the purge process is ended 404. If the storage space is exceeded the earliest message is deleted, but the message structure 120 is retained in step 406.
[0116] FIGS. 19 and 20 set forth a method of using folder lists as a trigger source for the redirector program 12. In FIG. 19, the user selects 408 a folder and the folder is stored 410 in the folder list. FIG. 20 shows the steps set forth for forwarding a message based on the folder list. The message could, for instance be a new piece of mail. The folder list is loaded 412. A new mail notification is received 414. The software checks if the mail is in a folder from the folder list in step 416. If the mail is not in a folder listed in the folder list, the process stops 418. If the mail is in a folder listed in the folder list, then the redirector forwards the message to the mobile device 24 in step 420, as described above.
[0117] In another aspect of the present invention, wireless mobile data communications devices, especially those that can return a confirmation signal to the host that the pushed data has been received, are utilized in conjunction with the redirector program. 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.
[0118] 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.
[0119] 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.
[0120] 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-air-moves as described below.
[0121] 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.
[0122] 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.
[0123] 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.
[0124] 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.
Claims
What is claimed:
1. A method of two-way synchronization between electronic mailboxes stored at a host system and a mobile communication device, each of the electronic mailboxes being organized into a set of hierarchical folders for storing received messages, the method comprising the steps of:
receiving messages at the host system and storing the received messages in the set of hierarchical folders of the host system's electronic mailbox;
determining whether to redirect the received messages from the host system to the mobile communication device and for each message that meets the determining step, assigning a unique message ID to the message and redirecting the message with its unique message ID to the mobile communication device;
receiving the redirected messages at the mobile communication device and storing them in the set of hierarchical folders at the mobile communication device;
coupling the mobile communication device to the host system;
synchronizing the set of hierarchical folders at the host system with the set of hierarchical folders at the mobile communication device;
retrieving a first list of messages from the host system, wherein the first list of messages are those messages that met the determining step and were redirected to the mobile communication device;
retrieving a second list of messages from the mobile communication device;
comparing the first list of messages to the second list of messages to identify messages having the same unique message ID and to determine whether the messages having the same unique message ID are stored in the same folders within the respective sets of hierarchical folders at the host system and the mobile communication device where the messages are stored; and
if the messages having the same unique message IDs are stored in different folders within the respective sets of hierarchical folders then determining which message should be moved and moving that message so that the messages having the same unique message IDs are stored in the same folders within the respective sets of hierarchical folders at the host system and the mobile communication device.
2. The method of claim 1, further comprising the steps of:
de-coupling the mobile communication device and the host system;
subsequently moving one of the messages at the mobile communication device so that it is stored in a different folder than the message having the same unique message ID at the host system;
transmitting a move command message from the mobile communication device to the host system to indicate that the message has been moved, the move command message including the unique message ID of the moved message and an identification of the folder in which the message is presently stored at the mobile communication device; and
moving the message corresponding to the unique message ID contained in the move command message at the host system so that it is stored in the same folder as the folder identified in the move command message.
3. The method of claim 2, wherein the move message command is transmitted from the mobile communication device to the host system over a wireless connection, further comprising the steps of:
enabling the transmission of the move message commands at the mobile communication device, wherein a user of the mobile communication device can either enable or disable the transmission of the move message commands.
4. The method of claim 1, further comprising the steps of:
de-coupling the mobile communication device and the host system;
subsequently moving one of the messages at the host system that was redirected to the mobile communication device so that it is stored in a different folder than the message having the same unique message ID at the mobile communication device;
transmitting a move command message from the host system to the mobile communication device to indicate that the message has been moved, the move command message including the unique message ID of the moved message and an identification of the folder in which the message is presently stored at the host system; and
moving the message corresponding to the unique message ID contained in the move command message at the mobile communication device so that it is stored in the same folder as the folder identified in the move command message.
5. The method of claim 1, wherein the host system and the mobile communication device are coupled via a wired connection.
6. The method of claim 1, wherein the host system and the mobile communication device are coupled via a wireless connection.
7. The method of claim 1, wherein the synchronizing the set of hierarchical folders step further comprises the steps of:
associating a unique folder ID with each folder in the sets of hierarchical folders at the host system and the mobile communication device;
generating a folder list including the folder IDs of the set of hierarchical folders at the host system;
providing the folder list to the mobile communication device; and
updating the set of hierarchical folders at the mobile communication device using the folder list so that the set matches the set of hierarchical folders at the host system.
8. The method of claim 1, further comprising the steps of:
associating a move flag with each of the messages having unique message IDs at both the host system and the mobile communication device; and
setting the move flag for each message that is moved from one folder to another folder at either the host system or the mobile communication device.
9. The method of claim 8, wherein the comparing step further comprises the step of examining the move flags for each of the messages having the same unique message IDs to determine if one of the messages have been moved from one folder to another folder at either the host system of the mobile communication device.
10. The method of claim 1, further comprising the steps of:
associating a folder ID with each message stored in the host system and the mobile communication device, wherein the folder IDs identify the folder location of each message within the respective sets of hierarchical folders; and
wherein the comparing step further comprises the step of comparing the folder IDs of the messages that have the same unique message ID to determine whether the messages are stored in the same folders within the respective sets of hierarchical folders at the host system and the mobile communication device.
11. The method of claim 1, further comprising the steps of:
de-coupling the mobile communication device and the host system;
subsequently moving a plurality of the messages at the mobile communication device so that the plurality of messages are stored in a different folders than the messages having the same unique message IDs at the host system;
generating a move command message for each of the plurality of messages that were moved, each move command message indicating that the message has been moved, the move command message including the unique message ID of the moved message and an identification of the folder in which the message is presently stored at the mobile communication device;
bundling the move message commands into a bundled transmission and transmitting the bundled transmission to the host system; and
moving the messages corresponding to the unique message IDs contained in the bundled move command messages at the host system so that the messages are stored in the same folders as the folders identified in the bundled move command messages.
12. The method of claim 1, further comprising the steps of:
providing a message structure for storing the messages, the message structure including a header portion and a message portion, the header portion including fields for storing the unique message ID assigned to the message and also for storing an identification of the folder in which the message is stored.
13. The method of claim 1, further comprising the steps of:
providing a folder structure for each of the folders in the set of hierarchical folders at the host system and the mobile communication device, the folder structure including a folder identification field and a folder type field.
14. The method of claim 13, further comprising the steps of:
designating at least one of the folders in the set of hierarchical folders as a deleted message folder using the folder type field of the folder so designated; and
if the folder type field indicates that the folder is a deleted message folder, then periodically deleting all of the messages stored in that folder at the host system.
15. The method of claim 1, wherein the determining whether to redirect the received messages step further comprises the steps of:
designating certain folders in the set of hierarchical folders at the host system for redirection;
determining whether the received messages are stored in the designated folders, and if so, then assigning the unique message ID to those messages and redirecting them with the unique message IDs to the mobile communication device.
16. A method of two-way synchronization between electronic mailboxes stored at a host system and a mobile communication device, each of the electronic mailboxes being organized into a set of hierarchical folders for storing received messages, the method comprising the steps of:
coupling the mobile communication device to the host system;
synchronizing the set of hierarchical folders at the host system with the set of hierarchical folders at the mobile communication device;
retrieving a first list of messages from the host system and a second list of message from the mobile communication device, each list of messages including unique message IDs that identify the messages stored in the respective set of hierarchical folders on the host system and the mobile communication device;
comparing the first list of messages to the second list of messages to identify messages having the same unique message ID and to determine whether the messages having the same unique message ID are stored in the same folders within the respective sets of hierarchical folders;
if the messages having the same unique message IDs are stored in different folders within the respective sets of hierarchical folders then determining which message should be moved and moving that message so that the messages having the same unique message IDs arc stored in the same folders within the respective sets of hierarchical folders at the host system and the mobile communication device;
de-coupling the mobile communication device and the host system;
subsequently moving one of the messages at the mobile communication device so that it is stored in a different folder than the message having the same unique message ID at the host system;
transmitting a move command message from the mobile communication device to the host system to indicate that the message has been moved, the move command message including the unique message ID of the moved message and an identification of the folder in which the message is presently stored at the mobile communication device; and
moving the message corresponding to the unique message ID contained in the move command message at the host system so that it is stored in the same folder as the folder identified in the move command message.
Patent Citations (210)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4106060(A) | 1978-08-01 | Chapman, Jr. | Applicant |
| US4417349(A) | 1983-11-01 | Hills et al. | Applicant |
| US4438433(A) | 1984-03-01 | Smoot et al. | Applicant |
| US4558454(A) | 1985-12-01 | Hills et al. | Applicant |
| US4644351(A) | 1987-02-01 | Zabarsky et al. | Applicant |
| US4695880(A) | 1987-09-01 | Johnson et al. | Applicant |
| US4697281(A) | 1987-09-01 | O'Sullivan | Applicant |
| US4713780(A) | 1987-12-01 | Schultz et al. | Applicant |
| US4768087(A) | 1988-08-01 | Taub et al. | Applicant |
| US4837798(A) | 1989-06-01 | Cohen et al. | Applicant |
| US4837800(A) | 1989-06-01 | Freeburg et al. | Applicant |
| US4845658(A) | 1989-07-01 | Gifford | Applicant |
| US4856047(A) | 1989-08-01 | Saunders | Applicant |
| US4928096(A) | 1990-05-01 | Leonardo et al. | Applicant |
| US4951044(A) | 1990-08-01 | Nelson et al. | Applicant |
| US4972457(A) | 1990-11-01 | O'Sullivan | Applicant |
| US4980907(A) | 1990-12-01 | Raith et al. | Applicant |
| US5008926(A) | 1991-04-01 | Misholi | Applicant |
| US5043721(A) | 1991-08-01 | May | Applicant |
| US5068916(A) | 1991-11-01 | Harrison et al. | Applicant |
| US5086502(A) | 1992-02-01 | Malcolm | Applicant |
| US5125021(A) | 1992-06-01 | Lebowitz | Applicant |
| US5127041(A) | 1992-06-01 | O'Sullivan | Applicant |
| US5128981(A) | 1992-07-01 | Tsukamoto et al. | Applicant |
| US5136291(A) | 1992-08-01 | Teague | Applicant |
| US5157660(A) | 1992-10-01 | Kuwahara et al. | Applicant |
| US5159592(A) | 1992-10-01 | Perkins | Applicant |
| US5177680(A) | 1993-01-01 | Tsukino et al. | Applicant |
| US5181200(A) | 1993-01-01 | Harrison | Applicant |
| US5265033(A) | 1993-11-01 | Vajk et al. | Applicant |
| US5283887(A) | 1994-02-01 | Zachery | Applicant |
| US5293250(A) | 1994-03-01 | Okumura et al. | Applicant |
| US5299255(A) | 1994-03-01 | Iwaki et al. | Applicant |
| US5307059(A) | 1994-04-01 | Connary et al. | Applicant |
| US5313582(A) | 1994-05-01 | Hendel et al. | Applicant |
| US5315635(A) | 1994-05-01 | Kane et al. | Applicant |
| US5333152(A) | 1994-07-01 | Wilber | Applicant |
| US5333266(A) | 1994-07-01 | Boaz et al. | Applicant |
| US5392390(A) | 1995-02-01 | Crozier | Applicant |
| US5406557(A) | 1995-04-01 | Baudoin | Applicant |
| US5410543(A) | 1995-04-01 | Seitz et al. | Applicant |
| US5416473(A) | 1995-05-01 | Dulaney, III et al. | Applicant |
| US5436960(A) | 1995-07-01 | Campana, Jr. et al. | Applicant |
| US5438611(A) | 1995-08-01 | Campana, Jr. et al. | Applicant |
| US5452356(A) | 1995-09-01 | Albert | Applicant |
| US5479472(A) | 1995-12-01 | Campana, Jr. et al. | Applicant |
| US5493692(A) | 1996-02-01 | Theimer et al. | Applicant |
| US5495484(A) | 1996-02-01 | Self et al. | Applicant |
| US5559800(A) | 1996-09-01 | Mousseau et al. | Applicant |
| US5572528(A) | 1996-11-01 | Shuen | Applicant |
| US5579472(A) | 1996-11-01 | Keyworth, II et al. | Applicant |
| US5588009(A) | 1996-12-01 | Will | Applicant |
| US5598536(A) | 1997-01-01 | Slaughter, III et al. | Applicant |
| US5603054(A) | 1997-02-01 | Theimer et al. | Applicant |
| US5604491(A) | 1997-02-01 | Coonley et al. | Applicant |
| US5604788(A) | 1997-02-01 | Tett | Applicant |
| US5625670(A) | 1997-04-01 | Campana, Jr. et al. | Applicant |
| US5627829(A) | 1997-05-01 | Gleeson et al. | Applicant |
| US5630060(A) | 1997-05-01 | Tang et al. | Applicant |
| US5633810(A) | 1997-05-01 | Mandal et al. | Applicant |
| US5638450(A) | 1997-06-01 | Robson | Applicant |
| US5641946(A) | 1997-06-01 | Shim | Applicant |
| US5666530(A) | 1997-09-01 | Clark et al. | Applicant |
| US5666553(A) | 1997-09-01 | Crozier | Applicant |
| US5673322(A) | 1997-09-01 | Pepe et al. | Applicant |
| US5701423(A) | 1997-12-01 | Crozier | Applicant |
| US5705995(A) | 1998-01-01 | Laflin et al. | Applicant |
| US5727202(A) | 1998-03-01 | Kucala | Applicant |
| US5729735(A) | 1998-03-01 | Meyering | Applicant |
| US5737531(A) | 1998-04-01 | Ehley | Applicant |
| US5742905(A) | 1998-04-01 | Pepe et al. | Applicant |
| US5751971(A) | 1998-05-01 | Dobbins et al. | Applicant |
| US5754954(A) | 1998-05-01 | Cannon et al. | Applicant |
| US5757901(A) | 1998-05-01 | Hiroshige | Applicant |
| US5758150(A) | 1998-05-01 | Bell et al. | Applicant |
| US5758354(A) | 1998-05-01 | Huang et al. | Examiner |
| US5761416(A) | 1998-06-01 | Mandal et al. | Applicant |
| US5764639(A) | 1998-06-01 | Staples et al. | Applicant |
| US5765170(A) | 1998-06-01 | Morikawa | Applicant |
| US5781614(A) | 1998-07-01 | Brunson | Applicant |
| US5781901(A) | 1998-07-01 | Kuzma | Applicant |
| US5790790(A) | 1998-08-01 | Smith et al. | Applicant |
| US5790974(A) | 1998-08-01 | Tognazzini | Applicant |
| US5796806(A) | 1998-08-01 | Birckbichler | Applicant |
| US5812773(A) | 1998-09-01 | Norin | Examiner |
| US5812819(A) | 1998-09-01 | Rodwin et al. | Applicant |
| US5813016(A) | 1998-09-01 | Sumimoto | Applicant |
| US5815081(A) | 1998-09-01 | Motohashi | Applicant |
| US5819172(A) | 1998-10-01 | Campana, Jr. et al. | Applicant |
| US5819284(A) | 1998-10-01 | Farber et al. | Applicant |
| US5822434(A) | 1998-10-01 | Caronni et al. | Applicant |
| US5826062(A) | 1998-10-01 | Fake, Jr. et al. | Applicant |
| US5838926(A) | 1998-11-01 | Yamagishi | Applicant |
| US5844969(A) | 1998-12-01 | Goldman et al. | Applicant |
| US5850219(A) | 1998-12-01 | Kumomura | Applicant |
| US5867660(A) | 1999-02-01 | Schmidt et al. | Applicant |
| US5878434(A) | 1999-03-01 | Draper et al. | Applicant |
| US5903723(A) | 1999-05-01 | Beck et al. | Applicant |
| US5905777(A) | 1999-05-01 | Foladare et al. | Applicant |
| US5917629(A) | 1999-06-01 | Hortensius et al. | Applicant |
| US5928329(A) | 1999-07-01 | Clark et al. | Applicant |
| US5937161(A) | 1999-08-01 | Mulligan et al. | Applicant |
| US5953322(A) | 1999-09-01 | Kimball | Applicant |
| US5961590(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5966714(A) | 1999-10-01 | Huang et al. | Examiner |
| US5968131(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5969636(A) | 1999-10-01 | Parvulescu et al. | Applicant |
| US5973612(A) | 1999-10-01 | Deo et al. | Applicant |
| US5974180(A) | 1999-10-01 | Schwendeman | Applicant |
| US5974238(A) | 1999-10-01 | Chase, Jr. | Examiner |
| US5978689(A) | 1999-11-01 | Tuoriniemi et al. | Applicant |
| US5978837(A) | 1999-11-01 | Foladare et al. | Applicant |
| US5983073(A) | 1999-11-01 | Ditzik | Applicant |
| US5995597(A) | 1999-11-01 | Woltz et al. | Applicant |
| US6000000(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6006274(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6014429(A) | 2000-01-01 | LaPorta et al. | Applicant |
| US6023700(A) | 2000-02-01 | Owens et al. | Applicant |
| US6023708(A) | 2000-02-01 | Mendez et al. | Applicant |
| US6034621(A) | 2000-03-01 | Kaufman | Applicant |
| US6052563(A) | 2000-04-01 | Macko | Applicant |
| US6052735(A) | 2000-04-01 | Ulrich et al. | Applicant |
| US6058431(A) | 2000-05-01 | Srisuresh et al. | Applicant |
| US6073137(A) | 2000-06-01 | Brown et al. | Examiner |
| US6073165(A) | 2000-06-01 | Narasimhan et al. | Applicant |
| US6078826(A) | 2000-06-01 | Croft et al. | Applicant |
| US6085192(A) | 2000-07-01 | Mendez et al. | Applicant |
| US6085232(A) | 2000-07-01 | Kikinis | Applicant |
| US6091951(A) | 2000-07-01 | Sturniolo et al. | Applicant |
| US6092114(A) | 2000-07-01 | Shaffer et al. | Applicant |
| US6092191(A) | 2000-07-01 | Shimbo et al. | Applicant |
| US6101531(A) | 2000-08-01 | Eggleston et al. | Applicant |
| US6115394(A) | 2000-09-01 | Balachandran et al. | Applicant |
| US6115736(A) | 2000-09-01 | Devarakonda et al. | Applicant |
| US6125281(A) | 2000-09-01 | Wells et al. | Applicant |
| US6125369(A) | 2000-09-01 | Wu et al. | Examiner |
| US6130892(A) | 2000-10-01 | Short et al. | Applicant |
| US6131096(A) | 2000-10-01 | Ng et al. | Applicant |
| US6131116(A) | 2000-10-01 | Riggins et al. | Applicant |
| US6141690(A) | 2000-10-01 | Weiman | Applicant |
| US6151606(A) | 2000-11-01 | Mendez | Applicant |
| US6157318(A) | 2000-12-01 | Minata | Applicant |
| US6157950(A) | 2000-12-01 | Krishman | Applicant |
| US6163274(A) | 2000-12-01 | Lindgren | Applicant |
| US6167379(A) | 2000-12-01 | Dean et al. | Applicant |
| US6178331(B1) | 2001-01-01 | Holmes et al. | Applicant |
| US6185603(B1) | 2001-02-01 | Henderson et al. | Applicant |
| US6202085(B1) | 2001-03-01 | Benson et al. | Examiner |
| US6233341(B1) | 2001-05-01 | Riggins | Applicant |
| US6240088(B1) | 2001-05-01 | Gayton et al. | Applicant |
| US6249820(B1) | 2001-06-01 | Dobbins et al. | Applicant |
| US6256666(B1) | 2001-07-01 | Singhal | Applicant |
| US6272545(B1) | 2001-08-01 | Flanagin et al. | Applicant |
| US6275848(B1) | 2001-08-01 | Arnold | Applicant |
| US6275850(B1) | 2001-08-01 | Beyda et al. | Applicant |
| US6311282(B1) | 2001-10-01 | Nelson et al. | Applicant |
| US6324544(B1) | 2001-11-01 | Alam et al. | Examiner |
| US6324587(B1) | 2001-11-01 | Trenbeath et al. | Examiner |
| US6356937(B1) | 2002-03-01 | Montville et al. | Examiner |
| US6360272(B1) | 2002-03-01 | Lincke et al. | Applicant |
| US6470358(B1) | 2002-10-01 | Beyda et al. | Examiner |
| US6487560(B1) | 2002-11-01 | LaRue et al. | Examiner |
| US6505214(B1) | 2003-01-01 | Sherman et al. | Examiner |
| US2002/0059380(A1) | 2002-05-01 | Biliris et al. | Examiner |
| US2002/0099719(A1) | 2002-07-01 | Schwitters et al. | Examiner |
| EP617373 | 1994-09-01 | Applicant | |
| EP736989 | 1996-10-01 | Applicant | |
| EP772327 | 1997-05-01 | Applicant | |
| EP777394 | 1997-06-01 | Applicant | |
| EP788287 | 1997-08-01 | Applicant | |
| EP9214556 | 1997-08-01 | Applicant | |
| EP793387 | 1997-09-01 | Applicant | |
| EP825788 | 1998-02-01 | Applicant | |
| EP838774 | 1998-04-01 | Applicant | |
| EP838934 | 1998-04-01 | Applicant | |
| EP772327 | 1999-02-01 | Applicant | |
| EP930766 | 1999-07-01 | Applicant | |
| EP986225 | 2000-03-01 | Applicant | |
| US1552 | 2001-05-01 | Applicant | |
| US29531 | 2001-10-01 | Applicant | |
| US40693 | 2001-11-01 | Applicant | |
| US42093 | 2001-11-01 | Applicant | |
| US54072 | 2001-12-01 | Applicant | |
| WO9619064 | 1996-06-01 | Applicant | |
| WO9726709 | 1997-07-01 | Applicant | |
| WO9727717 | 1997-07-01 | Applicant | |
| WO9732251 | 1997-09-01 | Applicant | |
| WO9733421 | 1997-09-01 | Applicant | |
| WO9741654 | 1997-11-01 | Applicant | |
| WO9744942 | 1997-11-01 | Applicant | |
| WO9800787 | 1998-01-01 | Applicant | |
| WO9821911 | 1998-05-01 | Applicant | |
| WO9823108 | 1998-05-01 | Applicant | |
| WO9826344 | 1998-06-01 | Applicant | |
| WO9848560 | 1998-10-01 | Applicant | |
| WO9905620 | 1999-02-01 | Applicant | |
| WO9905813 | 1999-02-01 | Applicant | |
| WO9906900 | 1999-02-01 | Applicant | |
| WO9917505 | 1999-04-01 | Applicant | |
| WO9919988 | 1999-04-01 | Applicant | |
| WO9936870 | 1999-07-01 | Applicant | |
| WO9945484 | 1999-09-01 | Applicant | |
| WO9948312 | 1999-09-01 | Applicant | |
| WO9950974 | 1999-10-01 | Applicant | |
| WO9963709 | 1999-12-01 | Applicant | |
| WO11567 | 2000-03-01 | Applicant | |
| WO11832 | 2000-03-01 | Applicant | |
| WO20994 | 2000-04-01 | Applicant | |
| WO113572 | 2001-02-01 | Applicant | |
| WO171539 | 2001-09-01 | Applicant |
Non-Patent Literature (63)
- Sun Microsystems, JavaMail API Design Specification, Version 1.0, Dec. 9, 1997, Sun Microsystems, Inc., chapters 1-10 appendices A-E.Applicant
- Compaq, Aero 2100 Series Color Palm-size PC Reference Guide, Second Edition, Aug. 1999, Compaq Corporation.Applicant
- Business Wire, Puma Technology Introduces New Version of Intellisync Software for the Palm Computing Platform and Windows CE, Oct. 4, 1999, Business Wire, pp. 1ff.Applicant
- Business Wire, Puma Technology Introduces Intellisync Version 3.1 Software for Palm Computing Platform Products, Nov. 24, 1998, Business Wire, pp. 1ff.Applicant
- Business Wire, Puma Technology to Ship Next Generation Intellisync Software for Palm Computing Platform Products, Jul. 28, 1998, Business Wire, pp. 1ff.Applicant
- Puma Technology, Inc., Intellisync Anywhere for Lotus Domino, 1999, pp. 1-2.Applicant
- 3Com, Handbook for the Palm VII Organizer, 1998, 3Com Corporation, pp. i-vii, 1, 163-194.Applicant
- 3Com, PalmPilot Professional Handbook, 1997, 3Com Corporation, pp. i-iv, 1-71.Applicant
- SAM Reference Manual, System for Automated Messages (Sep. 1989).Applicant
- IBM Portable Terminal User's Guide, Third Edition (Jun. 1985).Applicant
- Binder, Richard et al, The Alohanet Menehune, University of Hawaii, Version II (Sep. 1974).Applicant
- Computer Structures—Principles and Examples, McGraw Hill (1982).Applicant
- Krebs, Jay, Portable Computer and Host Talk Over Radio-Frequency Link, Electronic, pp. 142-145 (Aug. 25, 1983_.Applicant
- “BlackBerry Technical White Paper,” Research In Motion Ltd., Version 1.0, 1998-1999.Applicant
- Newsletter, “Battery Friendly Bulletin,” vol. 1, Issue 3, pp. 1-7 and unnumbered page, 1999.Applicant
- Article, Comerford, “Handhelds Duke It Out for the Internet,” Wireless Internet, pp. 35-38 and 41, Aug. 2000.Applicant
- Press Detail, “Extended Systems and Motorola Bring Short-Range Wireless to the Paging E-volution,” Jan. 13, 2000 (3 pgs.).Applicant
- Press Detail, “3Com Corporation Licenses Bluetooth Technology from Extended Systems,” Feb. 22, 2000 (2 pgs.).Applicant
- Web site Article, Hawaleshka, “The Web in Your Pocket,” Maclean's, May 15, 2000 (3 pgs.).Applicant
- Claxton, “Messaging API's for Voice Networks,” Telecommunications, pp. 116-120, 1998.Applicant
- Gifford, David K., et al., “The Application of Digital Broadcast Communication to Large Scale Information Systems.” IEEE Journal on Selected Areas in Communications, vol. SAC-3, No. 3, pp. 457-467 (May 1985).Applicant
- Gifford, David K., et al., “An Architecture for Large Scale Information Systems,” ACM, pp. 161-170 (1985).Applicant
- Egevang, K. et al., “The IP Network Address Translator,” Network Working Group, pp. 1-10, May 1994.Applicant
- Manual, “Server and BBS Software for the Packet Radio” by Jean Paul Roubelat, pp. 1-173.Applicant
- Book, “Internetwork Mobility The CDPD Approach,” by Mark S. Taylor, William Waung, and Mohsen Banan, Jun. 11, 1996.Applicant
- News Release, “Motorola Rings in 1995 with the Launch of the Marco® Wireless Communicator,” Jan. 4, 1995 (4 pgs.).Applicant
- Timeline, “FLEX™ Technology Timeline,” (3 pgs.).Applicant
- General Magic, Inc., Corporate Backgrounder, 2001 (2 pgs.).Applicant
- Pegasus Email Settings, ABSnet Internet Services, Inc. (4 pgs.).Applicant
- Motorola, Inc., emailVClient, 2001 (4 pages).Applicant
- News Release, “Motorola Announces Pagewriter 250, The World's Smallest Pager with Full Keyboard”, Feb. 27, 1997 (2 pgs.).Applicant
- Dewey, Barney, “Communications Strategies for Newton 2.0,” Newton Technology Journal, p. 10, Jun. 1996.Applicant
- Press Release, “Motorola Announces New Solutions to Provide Consumers with Wireless Access to Personal and Enterprise E-mail Accounts,” Mar. 21, 2001 (4 pgs.).Applicant
- “Motorola's ‘Marco’ Wireless Communicator,” http://www.msu.edu/-luckie/gallery/marco.htm, Jun. 14, 2001 (3 pgs.).Applicant
- News Release, “CE Software Announces MobileVision,” Editorial Contacts, CE Software, Inc., 1995 (3 pgs.).Applicant
- News Release, “CE Software Ships MobileVision,” Jun. 20, 1995 (3 pgs.).Applicant
- Newton Reference, Communications, 1996-1997(4 pgs.).Applicant
- PC Pro Issue 31: Realworld Computing, PDA Column, Jul. 30, 1997 (7 pgs.).Applicant
- Enterprise Solutions for Email Overload, Founder Publications, http://www.amikanow.com/corporte/publications.htm, Aug. 6, 2001 (9 pgs.).Applicant
- “Motorola's ‘Marco’ Wireless Communicator,” http://www.msu.edu/-luckie/gallery/marco.htm, Aug. 6, 2001 (2 pgs.).Applicant
- Press Release, “Apple Agrees to License Newton Technology to Schlumberger, Digital Ocean,” Nov. 3, 1995 (3 pgs.).Applicant
- Frezza, Bill, “PDA, PDA, Wherefore Art Thou, PDA?”, Freewire, Aug. 6, 2001 (6 pgs.).Applicant
- Black, Lauren, et al., “Personal Digital Assistants,” Macworld Reviews, Aug. 6, 2001 (5 pgs.).Applicant
- Reference, “MobileVision Direct Wireless Connection to Your LAN-Based Electronic Mailbox,” CE Software, Inc., pp. 1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 1995.Applicant
- User Manual, “MobileVision Direct Wireless Connection to Your LAN-Based Electronic Mailbox,” CE Software, Inc. 1995.Applicant
- Johnson, David B., “Ubiquitous Mobile Host Internetworking,” Fourth Workshop on Workstation Operating Systems, pp. 85-90, Oct. 14-15, 1993.Applicant
- Johnson, David B., “Mobile Host Internetworking Using IP Loose Source Routing,” School of Computer Science, Carnegie Mellon University, pp. 1-14 Feb. 1993.Applicant
- Schoettle, Bob, “IP-Address Management on LANs,” Byte, pp. 199-200, Feb. 1996.Applicant
- Cheshire, Stuart, et al., “Internet Mobility 4×4,” Computer Science Department, Stanford University, pp. 1-12, Aug. 1996.Applicant
- Yeom, Hoen Y., et al., “IP Mutliplexing by Transparent Port-Address Translator,” Proceedings of the Tenth USENIX System Administration Conference, pp. 113-122, Sep. 29-Oct. 4, 1996.Applicant
- Johnson, David B., “Scalable and Robust Internetwork Routing for Mobile Hosts,” IEEE Computer Society, pp. 2-11, 1994.Applicant
- Perkins, Charles, “IMHP: A Mobile Host Protocol for the Internet,” Computer Networks and ISDN System, vol. 27, pp. 479-491, 1994.Applicant
- Proceedings of the IEEE 7th International Workshop on Network and Operating System Support for Digital Audio and Video, Innsbrook Estates Conference Center, May 19-21, 1997, pp. 135-146.Applicant
- Lucent Technologies, Bell Labs Technical Journal, vol. 2, No. 3, pp. 152-163, Summer 1997.Applicant
- Lavana, Hemang, et al., Internet-Based Workflows: A Paradigm for Dynamically Reconfigurable Desktop Environments, Group 97, pp. 204-213, 1997.Applicant
- Perkins, Charles E., et al., “Mobility Support in IPv6,” Mobicom 96, pp., 27-37, 1996.Applicant
- Goldszmidt, German, et al., “ShockAbsorber: A TCP Connection Router,” IEEE, vol. 3, pp. 1919-1923, 1997.Applicant
- Padwick, et al., Special Edition Using Microsoft Outlook 97, 1997, Que Corporation, pp. 250-251, 353-367.Applicant
- Feibus, “A Desktop In Your Palm”, Informationweek, Aug. 25, 1997, pp. 65ff.Applicant
- Behr, “Handheld Solutions”, Informationweek, Oct. 27, 1997, pp. 106-113.Applicant
- Copy of DTS Wireless Website located at D.R.L. http://www.dtswireless.com.Applicant
- “3Com PalmPilot Gets Wireless Link for E-Mail”, Spooner, John G., PC Week, Dec. 8, 1997.Applicant
- “Have Your Pager Call My Pager”, Sullivan, Kristina B., PC Week, Dec. 8, 1997.Applicant