Source: http://patents.com/us-8671130.html
Timestamp: 2018-12-14 07:34:59
Document Index: 359770841

Matched Legal Cases: ['Application No. 02764425', 'Application No. 2461075', 'Application No. 2461075', 'Application No. 02764425', 'Application No. 02764425', 'Application No. 02764425', 'Application No. 02764425', 'Application No. 02764425', 'Application No. 04105407']

US Patent # 8,671,130. System and method for managing data items - Patents.com
United States Patent 8,671,130
Sinha , et al. March 11, 2014
Sinha; Anand (Hamilton, CA), Lewis; Allan D. (New Dundee, CA), Cherry; Carl L. (Waterloo, CA), Legg; Andrew J. (Kitchener, CA), Schnurr; Jeffrey R. (Waterloo, CA)
Sinha; Anand
Lewis; Allan D.
Cherry; Carl L.
Legg; Andrew J.
Schnurr; Jeffrey R.
10/490,247
PCT/CA02/01448
WO03/026235
US 20040266441 A1 Dec 30, 2004
60323865 Sep 21, 2001
6941349 September 2005 Godfrey et al.
7209949 April 2007 Mousseau et al.
7266365 September 2007 Ferguson et al.
7386588 June 2008 Mousseau et al.
7509376 March 2009 Mousseau et al.
7606936 October 2009 Mousseau et al.
7685244 March 2010 Mousseau et al.
7689721 March 2010 Mousseau et al.
7734281 June 2010 Ferguson et al.
7779151 August 2010 Major et al.
7818033 October 2010 Ferguson et al.
7953802 May 2011 Mousseau et al.
8024416 September 2011 Ferguson et al.
8050661 November 2011 Mousseau et al.
8060564 November 2011 Mousseau et al.
2001/0005857 June 2001 Lazaridis et al.
2001/0005861 June 2001 Mousseau et al.
2001/0013071 August 2001 Lazaridis et al.
2002/0049818 April 2002 Gilhuly et al.
2002/0086661 July 2002 Rouse et al.
2003/0005066 January 2003 Lazaridis et al.
2003/0028606 February 2003 Koopmans et al.
2003/0050987 March 2003 Lazaridis et al.
2003/0084184 May 2003 Eggleston et al.
2003/0191808 October 2003 Adler et al.
2004/0073619 April 2004 Gilhuly et al.
2004/0136358 July 2004 Hind et al.
2004/0205106 October 2004 Adler et al.
2005/0159136 July 2005 Rouse et al.
2007/0288582 December 2007 Major et al.
2008/0043675 February 2008 Mousseau et al.
2008/0043676 February 2008 Mousseau et al.
2008/0043694 February 2008 Mousseau et al.
2008/0044029 February 2008 Gilhuly et al.
2008/0045193 February 2008 Lazaridis et al.
2008/0045194 February 2008 Gilhuly et al.
2008/0045266 February 2008 Lazaridis et al.
2008/0046526 February 2008 Lazaridis et al.
2008/0046527 February 2008 Lazaridis et al.
2008/0046528 February 2008 Gilhuly et al.
2008/0046529 February 2008 Gilhuly et al.
2008/0046530 February 2008 Lazaridis et al.
2008/0046534 February 2008 Mousseau et al.
2008/0046535 February 2008 Mousseau et al.
2008/0046591 February 2008 Gilhuly et al.
2008/0046592 February 2008 Gilhuly et al.
2008/0046594 February 2008 Lazaridis et al.
2008/0051141 February 2008 Ferguson et al.
2008/0052365 February 2008 Mousseau et al.
2008/0052409 February 2008 Lazaridis et al.
2008/0057964 March 2008 Gilhuly et al.
2008/0058013 March 2008 Lazaridis et al.
2008/0059657 March 2008 Lazaridis et al.
2008/0109530 May 2008 Ferguson et al.
2008/0261632 October 2008 Hind et al.
2008/0261633 October 2008 Lazaridis et al.
2008/0288604 November 2008 Major et al.
2009/0172079 July 2009 Eggleston et al.
2011/0202597 August 2011 Mousseau et al.
0322105 Jun 1989 EP
97-22936 Jun 1997 WO
Woo et al., "Pigeon: a wireless two-way messaging system" Selected Areas in Communications, IEEE Journal on vol. 15, Issue 8, Oct. 1997 pp. 1391-1405. cited by examiner .
"Technical White Paper, BlackBerry Exchange Edition TM" Research in Motion Ltd., Version 2.0, 2000. cited by examiner .
Cree et al., "Methods of appending a reply in an electronic information system", European Patent Applicaiton, Publication No. 0 322 105 A2, Published: Jun. 28, 1989. cited by examiner .
Woo T Y C et al: "Providing Internet Services to Mobile Phones: A case study with Email" Personal, Indoor and Mobile Radio Communications, 1998. The Ninth IEEE International Symposium on Boston, MA, USA Sep. 8-11, 1998, New York, NY, USA, IEEE, US, Sep. 8, 1998, pp. 99-105, XP 010314728 ISBN: 0-7803-4872-9. cited by applicant .
European Examination Report in EP Application No. 02764425.1; European Patent Office; May 16, 2008; 4 pages. cited by applicant .
CIPO, Office Action, Application No. 2461075, Dec. 29, 2008, 3 pgs. cited by applicant .
CIPO, Notice of Allowance, Application No. 2461075, Mar. 17, 2010, 1 pg. cited by applicant .
EPO, International Search Report with Written Opinion, Application No. PCT/CA2002/01448, May 22, 2003, 14 pgs. cited by applicant .
EPO, Communication Pursuant to Article 94(3) EPC, Application No. 02764425.1, Oct. 6, 2004, 4 pgs. cited by applicant .
EPO, Communication Pursuant to Article 94(3) EPC, Application No. 02764425.1, Feb. 10, 2006, 4 pgs. cited by applicant .
EPO, Communication Pursuant to Article 94(3) EPC, Application No. 02764425.1, Oct. 19, 2007, 3 pgs. cited by applicant .
EPO, Communication Pursuant to Article 94(3) EPC, Application No. 02764425.1, Jan. 22, 2009, 6 pgs. cited by applicant .
EPO, Decision to Grant a European Patent Pursuant to Article 97(1) EPC, Application No. 02764425.1, Jun. 12, 2009, 3 pgs. cited by applicant .
Hong Kong IPD, Certification of Grant, Application No. 04105407.2, Nov. 20, 2009, 2 pgs. cited by applicant.
This application claims benefit of U.S. Provisional Application Ser. No. 60/323,865, entitled "System and Method for Managing Data Items," and filed on Sep. 21, 2001. The entire disclosure of this application, including the specification, drawings, and all appendices, is incorporated herein by reference.
1. A method of exchanging data items between a mail server and a mobile communication device, the method comprising: detecting, by a redirector component, a data item received for a user at the mail server; creating a redirection record corresponding to the received data item, the redirection record including a unique identifier associated with the received data item and redirection status information regarding the received data item; determining, for the received data item, whether the redirection status information indicates that the data item should be transmitted to the mobile communication device, and when the redirection status information so indicates: retrieving the received data item determined for transmission by means of its unique identifier; causing to transmit the received data item to the mobile communication device; and updating the redirection status information to indicate that the received data item referenced by the associated unique identifier has been transmitted to the mobile communication device.
2. The method of claim 1, further comprising packaging the received data item into an electronic envelope addressed using an electronic address of the mobile communication device prior to transmitting the data item to the mobile communication device.
3. The method of claim 1, wherein the data item is detected by polling the mail server.
4. The method of claim 1, wherein the data item is detected by receiving a notification from the mail server.
5. The method of claim 1, further comprising encrypting the data item prior to transmitting the data item to the mobile communication device.
6. The method of claim 1, further comprising compressing the data item prior to transmitting the data item to the mobile communication device.
7. The method of claim 1, wherein the data item is transmitted to the mobile communication device through a wireless gateway that couples the redirector component to a wireless data network.
8. A network node configured for facilitating exchange of data items between a mail server and a mobile communication device, the network node comprising: means for detecting a data item received for a user at the mail server; means for creating a redirection record corresponding to the received data item, the redirection record including a unique identifier associated with the received data item and redirection status information regarding the received data item; means for determining, for the received data item, whether the redirection status information indicates that the data item should be transmitted to the mobile communication device; and means, responsive to determining that the redirection status information indicates that the data item is to be transmitted to the mobile communication device, for performing: retrieving the received data item from the mail server by means of its unique identifier, causing to transmit the received data item to the mobile communication device, and updating the redirection status information to indicate that the received data item referenced by the associated unique identifier has been transmitted to the mobile communication device.
9. The network node of claim 8, further comprising means for packaging the received data item into an electronic envelope addressed using an electronic address of the mobile communication device prior to transmitting the data item to the mobile communication device.
10. The network node of claim 8, wherein the data item is detected by polling the mail server.
11. The network node of claim 8, wherein the data item is detected by receiving a notification from the mail server.
12. The network node of claim 8, further comprising means for encrypting the data item prior to transmitting the data item to the mobile communication device.
13. The network node of claim 8, further comprising means for compressing the data item prior to transmitting the data item to the mobile communication device.
14. The network node of claim 8, further comprising a state database for storing the redirection record.
FIG. 4 is a flow chart showing the steps carried out by an example redirector software operating at the host system.
FIG. 5 is a flow chart showing an example of steps that may be carried out by the mobile data communication device to interface with the redirector software represented in FIG. 4, operating at the host system.
FIG. 6 is a block diagram showing the interaction of a server-based redirection system with other components of the host system in FIG. 2 to enable the pushing of information from the server to the user's mobile data communication device.
FIG. 7 is a block diagram illustrating various components associated with a server-based redirection system such as shown in FIG. 6.
FIG. 8 is a block diagram illustrating an embodiment that includes databases associated with the server-based redirection system.
FIG. 9 is a flow chart showing an example of steps that may be carried out by the redirector software operating at the host system and utilizing a state database.
FIG. 10 is a flow chart showing an example of steps that may be carried out by the mobile data communication device to interface with the redirector software utilizing the state database.
FIG. 11 is a flow chart showing an example of steps that may be carried out by the redirector software utilizing the state database and in response to receiving a data item from the mobile communication device.
FIG. 12 is a flow chart showing an exemplary synchronization process between local databases, server databases and the mobile communication device.
In FIG. 1, the host system 10A is the user's desktop system, typically located in the user's office. The host system 10A 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.
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 system and method includes the ability to redirect certain message attachments to such an external machine 30 if the redirector program configuration data reflects that the mobile communication device 24 cannot receive and process the attachments, or if the user has specified that certain attachments are not to be forwarded to mobile communication 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.
The mobile data communication device 24 may be 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 the system may 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 may be configured, for example via software program instructions, to work in conjunction with the redirector program 12B to enable the seamless, transparent redirection of user-selected data items. FIG. 4 describes the basic method steps of an example redirector program, and FIG. 5 describes the steps of a corresponding program which may be operating at the mobile communication device 24.
FIG. 1 shows an E-mail message A being communicated over LAN 14 from computer 26 to the user's desktop system 10A (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 communication device 24). Once the message A (or C) reaches the primary message store of the host system 10A, it can be detected and acted upon by the redirection software 12A. The redirection software 12A can use many methods of detecting new messages. One method of detecting new messages is using Microsoft's.RTM. Messaging API (MAPI), in which programs, such as the redirector program 12A, register for notifications or `advise syncs` when changes to a mailbox take place. Other methods of detecting new messages could also be used, and will be described in further detail below.
FIG. 2 is an alternative system diagram showing the redirection of user data items from a network server 10B to the user's mobile data communication device 24, where the redirector software 12B is operating at the server 10B. This configuration is particularly advantageous for use with message servers such as a Microsoft.RTM. Exchange Server or a Lotus.TM. Domino.TM. Server, which are normally operated so that all user messages are stored 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.
FIGS. 4 and 5, are flow charts showing steps that may be carried out, respectively, by the redirector software 12A operating at the host system 10A, and 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 12A is started and initially configured. The initial configuration of the redirector 12A 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 communication device; and (5) configuring the preferred list of user selected senders whose messages are to be redirected.
FIG. 4 sets forth the basic steps of an example redirector program 12A assuming it is operating at a desktop system 10A, such as shown in FIG. 1. If the redirector 12B is operating at a network server 12B, as shown in FIG. 2, then additional configuration steps may be necessary to enable redirection for a particular desktop system 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 communication device.
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 12A. At step 80 the mobile software is started and the mobile communication device 24 is configured to operate with the host system, including, for example, storing the address of the user's desktop system 10A.
Turning back to FIG. 5, if the user signal or message is not a direct message to the desktop system 10A 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 10A, 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 communication device's display. The mobile unit 24 then returns to step 82 and waits for additional messages or signals.
If the mobile communication 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 communication 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 10A, and the repackaged message is then transmitted to the desktop system 10A at step 106. As described above, the redirector program 12A 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.
In the system of FIG. 7, two servers computers 120 and 122 are shown. Redirection system components could also be implemented on more or fewer server computers, and functionality may be distributed differently than specifically shown in FIG. 7. The server computer 120 is analogous to a combination of the E-mail sub-system 116 and the primary store 112 in FIG. 6. The server computer 120 includes a server software component 126, preferably including at least a messaging software application or other software that generates, receives or otherwise manages user data items, and a data store 128 for storing such data items. In the example system of FIG. 7, the data store is shown as a user mail file. One example of such a user mail files exists in an E-mail system supported by a Lotus Domino Server. Data items such as 128a associated with a user having an account on the server 120 are normally stored in the user mail file 128. Although only a single user mail file is shown in FIG. 7, those skilled in the art will appreciate that the server computer 120 would typically include a user mail file for each user. In a Lotus Domino mail file, each data item is typically indexed with a unique identifier (UNID), such as UNIDa for data item 128a.
Thus, in the embodiment of FIG. 7, adding such an indicator modifies the entry 128a in the mail file and results in modification of other parts of the message not directly related to the additional properties themselves, to the mail file 128. Subsequent operations on the new "modified" message are therefore correlated to the new mail file entry and UNID, and not the original file entry. This may result in such problems as digital signature verification failures for modified messages and synchronization of mail files between a user's desktop system 124, the server 120 and the user's mobile communication device 24. For example, because different UNIDs are associated with the original mail file entry and the mail file entry that was processed by the redirector program 130, messages that have been read at the mobile communication device might be shown as unread at the server computer 120 and the desktop computer 124 when the user accesses the server 120.
When a new data item 128a is received and stored in the user mail file 128, a mail identifier is created to reference the new data item 128a. When a new data item 128a is detected in a user mail file 128, such as by querying or polling the server software component 126 and/or user mail file 128, the data item 128a, or at least the UNID portion of the entry, is retrieved by the redirector program 130 and stored to the user's state database 134. Since the UNID of the data item stored in the state database 134 and the mail file 128 is the same, UNIDa, the redirector program 130 provides a correlation between original and redirected data items. The redirector program 130 can thereby determine which mail file entries have been processed, without changing mail file entries, by consulting the user's state database 134. A data item associated with the mail file entry 128a may then be retrieved from the user mail file 128 using the UNIDa and redirected to the user's mobile communication device, as described above. In another embodiment, the redirector program 130 may also store the data item 128a in the user's state database 134 and retrieve the data item from the state database 134.
The state database 134 may also be used to store indications of data item processing operations performed at a user's mobile communication device 24. The status information may be associated with a UNID and stored in the state database 134. Such status information may include data indicating that the data item 128 is not to be processed and sent to the mobile communication device 24, or that the data item 128 has been processed and sent to the mobile communication device 24. Status information may also include status information from the mail file 128, such as data indicating that the data item 128 has been forwarded, is a reply message, or is stored in a certain folder/file location. Other status information may also be included. Thus, when a user reads a redirected data item at the device 24 for example, a signal may be returned to the redirector program 130, which may set a flag or other indicator in the corresponding state database entry. Deletion of a data item at a mobile communication device 24 may be similarly updated in the state database 134. This would allow a user to replicate the server's mail file 128 and the state database 134 to a desktop system 124, as indicated at 138 and 140, to thereby perform off-line data item synchronization between a local copy of the mail file 138 and the state database 140, such that the local mail file reflects device operations. This is advantageous in that network-intensive mail file synchronization can be reduced to less intensive so-called "delta" synchronization, in which only changes need be updated between the desktop system 124 and server computer 120. The UNID of any data item such as UNIDa of data item 128a, is maintained throughout all system components, including server computers 120 and 122, as well as the desktop system 124.
FIG. 8 is a block diagram illustrating an embodiment that includes databases associated with the server-based redirection system. In this embodiment, the mail file 128 is realized by a database 128. Each illustrative data item 128a of the mail database 128 may include a mail database identifier 129a, status fields 129b, message data 129c, and attachment data 129d. The mail database identifier 129a is an identifier by which the data item 128a may be addressed or accessed in the mail database 128. The status fields 129b comprise data indicating the status of data item 128a such as read, unread, forwarded, replied to, urgent, etc., if the data item 128a is an e-mail message, for example. The message data 129c comprises the message to be communicated by the data item, such as text data if the data item is an e-mail message, for example. The attachment data 129d comprises one or more attachments included with the data item, such as a word processing document that may be attached to an e-mail message, for example.
The state database 134 includes a corresponding record 134a for the data item 128a. The corresponding record 134a comprises a redirection record associated with the corresponding data item 128a stored in the mail database 128. Each illustrative record 134a includes a corresponding mail database identifier 135a, and may also include status fields 135b and process fields 135c. The mail database identifier 135a corresponds to the mail database identifier 129a. Thus, by accessing the mail database identifier 135a, the redirector program 130 can access the corresponding data item 128a stored in the mail database 128. The status fields 135b comprise data indicating the status of data item 128a such as read, unread, forwarded, replied to, urgent, etc., if the data item 128a is an e-mail message, for example. The process fields 135c comprises data indicating redirector processing steps associated with the data item 128a. Illustrative process fields include a transmission identifier and a message status. For example, if the redirector program 130 determines that the data item is not to be forwarded to the mobile communication device 24, the message status may include data indicating that no operation is to be carried out on the data item 128a. Alternatively, if the redirector program 130 determines that the data item is to be forwarded to the mobile communication device 24, the redirector program may assign a transmission identifier that corresponds to the mail database identifier 135a, and the message status may thereafter include data indicating the data item 128a has been transmitted to the mobile communication device 24.
The redirector program 130 accesses the mail database 128 and the state database 134 to manage the data items stored in the mail database 128. FIG. 9 provides a flow chart showing an example of steps that may be carried out by the redirector program 130 operating at the host system and utilizing a state database 134. In step 152, the redirector program waits for a new data item 128a to be stored in the mail database 128. When a new data item 128a is stored in the mail database 128, a corresponding mail database identifier 129a is created. In step 154, the redirector program 130 scans the new data item 128a stored in the mail database 128, creates a corresponding record 134a in the state database 134, and stores the mail database identifier 129a in the mail identifier field 135a.
The data item 128a is then compared to the user profile stored in the user profile database 132 to determine whether to transmit the data item 128a to the mobile communication device 24, as shown in step 156. If, in step 158, the redirector program 130 determines that the data item 128a is not to be transmitted to the mobile communication device 24, then a "no operation" status is set in one of the process fields 135c of the corresponding record 134a stored in the state database 134, as shown in step 160.
On the other hand, if the redirector program 130 determines that the data item 128a is to be transmitted to the mobile communication device 24, then the data item 128a and the mail database identifier 135a are transmitted to the mobile communication device 24 over a wireless network, as shown in step 162.
In another embodiment, only a subset of the data item 128a is transmitted to the mobile communication device 24. The subset includes a portion of the message data 129c, thus limiting the bandwidth requirements between the redirector program 130 and the mobile communication device 24.
Often, the mail database identifier 128a may be a large data structure, e.g., 64 bytes in length. To further conserve bandwidth, in yet another embodiment, a transmission identifier is stored in one of the process fields 135c and is associated with the mail database identifier 135a stored in the state database 134. The transmission identifier is a smaller data structure than the mail database identifier 128a, and is transmitted with the data item 128a, or the portion thereof transmitted.
The data item 128a and the corresponding mail database identifier 128a are thereafter received by the mobile communication device 24. FIG. 10 provides a flow chart showing an example of steps that may be carried out by the mobile data communication device 24 to interface with the redirector software 130 utilizing the state database 134. In step 170, the mobile communication device 24 waits for the reception of a data item or signal input. In step 172, the mobile communication device 24 determines if either a data item or signal has been received. If a data item has been received, then the mobile communication device 24 stores the data item in the data store 150 in step 174, and presents the data item to the user in step 176.
However, if the mobile communication device 24 is to transmit a reply message, then in step 184 the reply data is generated. Reply data may comprise a reply text message input by the user, a forwarding destination addresses, and the like. In step 186, the mobile communication device 24 includes the mail identifier 128a of the original data item to which the reply message is being generated, and then the mobile communication device 24 transmits the data item and the mail database identifier as shown in step 182.
The original data item to which the reply message is being generated need not be included in the transmission, as the redirector program 130 is operable to instruct the mail server 126 to generate a reply data item that includes the original data item and the reply data transmitted from the mobile communication device 24. FIG. 11 provides a flow chart showing an example of steps that may be carried out by the redirector program 130 utilizing the state database 134 and in response to receiving a data item from the mobile communication device 24. In step 190, the redirector program 130 waits for the reception of a data item sent from the mobile communication device 24. Upon receiving the data item from the mobile communication device 24, the redirector program 130 in step 192 determines whether the data item is a reply data item to an original data item. If the data item is a reply data item to an original data item, then in step 194 the redirector program 130 accesses the original data item in the mail database 128 by the corresponding mail database identifier 129a, which is stored in the state database 134.
FIG. 12 is a flow chart showing an exemplary synchronization process between local databases, server databases and the mobile communication device 24. As previously described, the synchronization process is initiated with the mobile communication device 24 is connected to the desktop system 120 via a link 151. Upon initiation of the synchronization process, the desktop system 124 determines whether it is connected to the servers 120 and 122, as shown in step 210. If the desktop system 124 is connected to the servers 120 and 122, then the mail database 128, the state database 134, the local mail database 138, the local state database 140 and the mobile communication device 24 are synchronized so that the status of data items stored in the mail database 128, the state database 134, the local mail database 138 and the local state database 140, and the data store 150 of the mobile communication device 24 are updated to a common state, as shown in step 212.
Previous Patent US 8,671,129 | Next Patent US 8,671,131