JP2013092850A - Off-line usable electronic mail client system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an electronic mail (e-mail) client system that can be used off-line by synchronizing data including e-mail state information (unread/read, returned/transferred and so on), an address book and the like, between a plurality of mobile terminals.SOLUTION: An electronic mail (e-mail) client system is configured by including mobile terminals, one of which includes a taken-out data management function, and each of which includes an e-mail client for accessing the taken-out data management function via a network communication base which enables data sharing between the mobile terminals. Further, the e-mail client system is provided with an e-mail synchronization module for synchronizing the taken-out data between an e-mail client provided in a desktop terminal and the taken-out data management function, and the system further includes an e-mail synchronization function for executing in advance the synchronization between the taken-out data management function and the synchronization module, before synchronizing the taken-out data between the desktop terminal and the synchronization module.

Description

  The disclosed subject matter relates to a technique for configuring an e-mail client system that can be used in an environment using a plurality of terminals.

  As mobile terminals become widespread, there is a need to use an e-mail system used in an office desktop terminal in a mobile environment away from home. In such a case, it is required to keep the same e-mails held in a plurality of environments.

  To meet such needs, there are a method of synchronizing electronic mails in the entire network shown in Patent Document 1 and a method of synchronizing electronic mail data between terminals shown in Patent Document 2. In this specification, “synchronization” means keeping e-mail data held in a plurality of places the same. However, even if the file formats and formats are different, if they can be converted to each other, they are regarded as the same.

  In the method disclosed in Patent Document 1, a first mail server used for access in an office and a second mail server used for access from outside the office are prepared, and a predetermined standard is used. After determining whether the electronic mail distributed to one mail server should be transmitted to the second mail server, the electronic mail is transmitted to the second mail server.

  The second mail server allows users with appropriate authentication to access the second mail server using HTTP from a mobile terminal, and is the same as when they are in the office even in a mobile environment on the go You can use email.

  However, the method disclosed in Patent Document 1 requires that the mobile terminal can access the second mail server via the network. For this reason, e-mail could not be accessed when the user was in an offline environment where communication was not being performed because the radio wave did not reach.

  In the method disclosed in Patent Document 2, as part of information managed by a personal information manager (PIM), electronic mail is synchronized in both directions between a desktop terminal and a mobile terminal. Patent Document 2 also mentions an attachment (attached file) attached to an e-mail. Considering that attachments include files that are more stringent for memory, such as drawings, graphs, and charts, and that some attachments are unnecessary unless they are on the desktop, the ability to properly identify messages is synchronized. It also rests on the system.

  The method disclosed in Patent Document 2 only needs to allow the desktop terminal and the mobile terminal to access each other only when synchronization is performed, and can access an e-mail even in an offline environment.

International Publication No. 1999/005620 Pamphlet International Publication No. 1999/022322 Pamphlet

  According to the method disclosed in Patent Document 2, an electronic mail with an attached file can be viewed and edited using a mobile terminal in an offline environment. However, it is necessary to take out e-mail including e-mail status information (unread / read distinction, reply / transferred status information, etc.) and address book.

  However, various terminals (called mobile terminals) such as mobile phones such as smartphones, mobile PCs, and tablet terminals have come to be used as options for mobile terminals that can be used by users. Problems may occur when using two mobile terminals.

  For example, after synchronizing a desktop terminal with a smartphone and a tablet terminal, the smartphone and the tablet terminal are each replied to a different party in response to the same email, and then the smartphone and the tablet terminal are reconnected with the desktop terminal. If you synchronize, either the changes on the smartphone or tablet terminal will be discarded, and you will not be able to synchronize correctly.

  Disclosed is an e-mail client system in which take-out data such as e-mail is synchronized between three or more terminals and the synchronized take-out data can be used offline. In the present specification, the export data includes at least an electronic mail and / or an address book.

Specifically, the above system limits the exchange with the mail server to one of three or more terminals (for example, a desktop terminal), and one of the other terminals (for example, a mobile terminal) A take-out data management unit that records the last data update time, and the other terminals (for example, mobile terminals) include an e-mail client that accesses and synchronizes the take-out data management unit,
The other terminals (for example, mobile terminals) synchronize data with other terminals including a take-out data management unit, and further, an e-mail client module mounted on the desktop terminal, a take-out data management unit, An email client system is configured including a synchronization module for exchanging updated email data.

An e-mail client module that accesses the take-out data management function via a network communication infrastructure that enables one of the mobile terminals to share the take-out data management function and allows each mobile terminal to share data between the mobile terminals. Equipped with
Prepare a synchronization module to synchronize the export data between the email client module mounted on the desktop terminal and the export data management function,
When synchronizing export data between the desktop terminal and the synchronization module, an e-mail synchronization function having a function for executing synchronization between the export data management function and the synchronization module in advance Including an email client system.

  For email clients, the data exchange protocol with the mail server (for example, SMTP or POP3) is standardized, but records the format in which emails are stored, and that each email is unread, replied, and forwarded. Each method has its own specifications. However, Patent Document 2 does not consider the difference in specifications, and assumes that e-mail clients installed in a desktop terminal and a mobile terminal can use e-mail with each other simply by performing simple synchronization.

  In the e-mail client system disclosed in this specification, the characteristic e-mail synchronization function described above may further include a function of converting a storage format (format) of e-mail data. As a result, even when an e-mail client module that handles different types of storage formats is used in each of a plurality of mobile terminals, it can be accessed offline.

  Furthermore, in the method disclosed in Patent Document 2, the types of attached files that can be used offline are limited to application programs (hereinafter referred to as applications) installed in each mobile terminal.

In the e-mail client system disclosed in the present specification, the characteristic e-mail synchronization function described above further includes a function of causing a mobile terminal to download a mobile code for processing an attached file,
A function for operating the mobile code downloaded to each mobile terminal may be added to the e-mail client system. As a result, the attached file can be processed regardless of the application installed in the mobile terminal.

  According to the disclosure, in the e-mail environment used on the desktop terminal, the message set for export and its status (unread / read status, reply / transferred status information) and address book are synchronized. Can be accessed by multiple mobile terminals.

The whole structure of an electronic mail client system is illustrated. The synchronization sequence between the electronic mail client module of a desktop terminal and the mail synchronization module of a mail synchronization server is illustrated. The synchronization sequence between the carrying-out data management module of a smart phone and the mail synchronization module of a mail synchronization server is illustrated. The internal structure of the synchronous data DB installed in the mail synchronization server is illustrated. The outline processing flow in a desktop terminal which implement | achieves the synchronous sequence of a desktop terminal and a mail synchronous server is illustrated. The outline processing flow in a mail synchronization server which implement | achieves the synchronization sequence of a desktop terminal and a mail synchronization server is illustrated. An example of a schematic processing flow of a sending thread of a mail synchronization server for an e-mail client module of a desktop terminal is illustrated. The example of the general | schematic processing flow of the reception thread | sled of the mail synchronous server with respect to the electronic mail client module of a desktop terminal is illustrated. The example of the outline processing flow of the transmission thread | sled of the email client module of a desktop terminal with respect to a mail synchronous server is illustrated. 6 illustrates a schematic processing flow of a reception thread of an e-mail client module of a desktop terminal with respect to a mail synchronization server.

  Embodiments will be described with reference to the drawings.

  FIG. 1 is a diagram for explaining the overall configuration of the e-mail client system of this embodiment.

  This system includes a desktop terminal 100, a mail server 110, a mail synchronization server 120 connected to the intra-organization network 130, a smartphone 150 connected to the Internet 140, and a tablet terminal 160. In the present embodiment, the smartphone 150 and the tablet terminal 160 may be collectively referred to as mobile terminals.

  The mail server 110 includes a mail transfer agent 111 (abbreviated as MTA: Mail Transfer Agent in FIG. 1), which is in charge of delivering electronic mail using a mail delivery protocol such as SMTP (Simple Mail Transfer Protocol), It has a user mailbox 112 for storing received mails and the like of users who have an account of the mail server 110.

  The desktop terminal 100 has an e-mail client module (hereinafter abbreviated as an e-mail client. Further abbreviated as MUA: Mail User Agent in FIG. 1) 101 and functions such as browsing and editing of files attached to e-mails. It has an attached file application 102 (abbreviated as AP in FIG. 1) to be provided and a local mailbox 103 for storing the user's received mail.

  The e-mail client 101 receives a mail addressed to the user from the mail transfer agent 111 using POP3 (Post Office Protocol Version 3), IMAP (Internet Message Access Protocol), etc., and has a function of browsing, new or replying, forwarding, etc. It has a function of creating a mail and sending it to the mail transfer agent 111 using SMTP or the like. Furthermore, the e-mail client 101 also has a function of managing an address book as a mail destination.

  The e-mail client 101 has a function of allowing the user to select an e-mail to be taken out from the local mailbox 103 to the mobile terminal and storing it as a take-out target e-mail in order to perform operations such as browsing and replying to e-mail on the mobile terminal And a data exchange function with the mail synchronization server 120.

  Taking out e-mail means storing a copy of e-mail data to be taken out in a take-out destination (for example, a take-out mailbox of the smartphone 150 described later).

  The function for allowing the user to select the e-mail to be taken out is, for example, a folder designated for taking out in advance by attaching a take-out target mark for each selected e-mail on the received mail list screen of the e-mail client 101 You may move your email to Further, a message filter function that distributes to a predetermined folder at the timing of receiving an e-mail depending on a transmission source or a subject may be used.

  Further, the e-mail client 101 may set a time limit for taking out to the mobile terminal in the e-mail to be taken out. For example, you can set a take-out deadline (for example, after a week) when attaching a take-out target mark, prepare multiple folders for take-out, and provide a take-out period (for example, a week) for each folder. Also good.

  The smartphone 150 includes a network interface 151 for internet connection (abbreviated as “net I / F” in the figure), a network interface 152 for cooperation between mobile terminals (abbreviated as “I / F between terminals” in the figure), and an e-mail client 153. An attached file application 154 that provides functions such as viewing and editing a file attached to an e-mail, a take-out data management module 155, and a take-out mail box 156.

  The network interface 151 for Internet connection is a wireless communication interface such as 3G, WiFi (registered trademark), WiMax (registered trademark), or the like. The network interface 152 for inter-mobile terminal cooperation is used for local communication between the smartphone 150 and the other tablet terminal 160 near the user, and is a short-range wireless such as Bluetooth (registered trademark). It is a communication interface.

  An e-mail client 153 (abbreviated as MUA: Mail User Agent in FIG. 1) installed in the smartphone 150 has a function of accessing the take-out mail box 156 and displaying the stored e-mail so that it can be browsed. It has a function to create e-mails such as reply and transfer. Further, the e-mail client 153 has a function of managing an address book as a mail destination.

  When a user browses an attached file while viewing a received mail using the e-mail client 153, the user starts the attachment file application 154 (abbreviated as AP in FIG. 1) and displays the attached file. Can do. Further, when creating a new mail and creating a reply mail or a forward mail for the received mail by the electronic mail client 153, it is possible to refer to the address book. The created mail can access the take-out mail box 156 and be stored in the draft folder.

  The export data management module 155 is a module that provides a function of exchanging export data including at least an electronic mail and / or an address book with the mail synchronization server 120. A sequence for exchanging take-out data will be described later. The e-mail client 153 and the attached file application 154 running on the smartphone 150 may be operated on a virtualization platform 157 that operates a program such as Java (registered trademark) or JavaScript (registered trademark), for example. .

  The tablet terminal 160 includes a mobile terminal cooperation network interface 162 (abbreviated as inter-terminal I / F in the figure), an e-mail client 163, and an attached file application 164.

  The tablet terminal 160 is not necessarily a tablet as a form, and may be a form equivalent to a portable PC such as a notebook PC. In addition, even if the tablet terminal 160 itself includes the network interface 161 for Internet connection, the tablet terminal 160 provides the Internet connection provided by the smartphone 150 via the network interface 162 for inter-mobile terminal cooperation and the network interface 152 for inter-mobile terminal cooperation. You may make it connect to a network using the network interface 151. FIG.

  An e-mail client 163 (abbreviated as MUA: Mail User Agent in FIG. 1) installed in the tablet terminal 160 is connected to the smartphone 150 via the network interface 162 for inter-mobile terminal cooperation and the network interface 152 for inter-mobile terminal cooperation. And a function for accessing a stored mail box 156 to display the stored electronic mail so that it can be browsed, and a function for creating a new or reply mail, forwarded mail, or the like. Further, the e-mail client 163 also has a function of managing an address book that is a mail destination.

  When a user browses an attached file while viewing a received mail using the e-mail client 163, the attached file application 164 (abbreviated as AP in FIG. 1) is activated to display the attached file. Can do. Further, when creating a new mail and creating a reply mail or a forward mail for the received mail with the electronic mail client 163, it is possible to refer to the address book.

  The e-mail client 163 accesses the taken-out mail box 156 in the smartphone 150 via the network interface 162 for inter-mobile terminal cooperation and the network interface 152 for inter-mobile terminal cooperation, and stores the created mail in the draft folder. The e-mail client 163 operating on the tablet terminal 160 and the attached file application 164 may also operate on the virtualization platform 165.

  The mail synchronization server 120 is a server that provides a function to synchronize information to be taken out between the desktop terminal 100 and the mobile terminal, and the data to be taken out that is installed in the e-mail client 101 and the smartphone 150 installed in the desktop terminal 100. It has a mail synchronization module 121 that mediates data synchronization with the management module 155, and a synchronization data DB 122 that stores a copy of information to be taken out and to be transmitted to the smartphone 150 for synchronization.

  The functions of the mail synchronization server 120 may be configured on the desktop terminal 100 if the desktop terminal 100 is directly accessible from the Internet.

  Each device constituting the electronic mail client system in this embodiment, that is, the desktop terminal 100, the mail server 110, the mail synchronization server 120, the smartphone 150, and the tablet terminal 160 described above is a general computer including a CPU and a storage device. It can be realized using. Furthermore, each function such as a module and an application described in the present embodiment is realized on the computer by the CPU executing a program stored in the storage device.

  Each program may be stored in advance in a storage device in the computer, or introduced to the storage device from another device via an input / output interface and a medium that can be used by the computer when necessary. May be. The medium refers to, for example, a storage medium that can be attached to and detached from the input / output interface, or a communication medium (that is, a wired, wireless, optical network, or a carrier wave or digital signal that propagates through the network).

  Here, the information to be taken out is the status information of the e-mail (for example, unread / read information, reply completed) in addition to the e-mail body and its attached file whose format is determined by MIME (Multipurpose Internet Mail Extensions) / Transferred information etc.) and the contents of the address book accessed by the e-mail client 101. The format of the status information and the address book depends on the e-mail client, and there are those added as a header of the e-mail message and those added to the name of the file storing the message.

  If the e-mail clients of the desktop terminal 100, the smartphone 150, and the tablet terminal 160 are all the same type, the export target information storage format of the synchronization data DB 122 can be saved in the format of the e-mail client. When different e-mail clients are used in the respective terminals, a format independent of the application may be used.

  When the e-mail clients (153 and 163) and the attached file applications (154 and 164) that operate on the smartphone 150 and the tablet terminal 160 use the virtualization infrastructure (157 and 165), the virtualization infrastructure You may make it have mobile code DB123 which stores the mobile code which operate | moves above.

  FIG. 2 shows a synchronization sequence between the email client 101 of the desktop terminal 100 and the mail synchronization module 121 of the mail synchronization server 120.

  This sequence is performed at a predetermined timing, for example, (1) when the e-mail client 101 is activated, (2) when an e-mail to be taken out is designated, (3) periodically while the e-mail client 101 is activated, (4) It can be set to start when the e-mail client 101 is terminated.

  Step 201 is a step of starting synchronization. The e-mail client 101 establishes a connection to the mail synchronization module 121 and transmits the user ID and password of the mail user stored in advance. The mail synchronization module 121 performs step 202 of authenticating the email client 101 of the desktop terminal 100 by accepting the user ID / password of the mail user. If the authentication in step 202 is successful, the following steps are performed.

  In step 203, prior to executing synchronization between the desktop terminal 100 and the mail synchronization server 120, in order to prevent inconsistency between the mobile terminal and the mail synchronization server 120, the mail synchronization module 121 is configured to manage data taken out by the smartphone 150. This is a step of sending a synchronization instruction to the module 155. By performing this step, the synchronization sequence between the carry-out data management module 155 of the smartphone 150 and the mail synchronization module 121 of the mail synchronization server 120 shown in FIG. 3 is performed. 3 After confirming the execution of the sequence, the following steps are performed.

  Step 204 is a step in which the mail synchronization module 121 returns the authentication result and the previous connection time information of the email client 101 to the email client 101.

  The e-mail client 101 refers to the received previous connection time information, accesses the local mailbox 103, and picks up data to be transmitted to the mail synchronization module 121 (step 205). Here, the data to be picked up is the newly marked e-mail after the last connection time, the e-mail client whose unread / read status has been changed, replied, or forwarded since the last connection time This corresponds to an e-mail marked with 101, an updated address book, and the like.

  Even if the e-mail to be taken out is deleted by the e-mail client 101, the result does not have to be transmitted to the mail synchronization module 121 (it is not necessary to reflect the result in the mail synchronization module 121). This is because the e-mail taken out to the mail synchronization module 121 is deleted when the storage period has expired, as will be described later.

  In parallel with step 205, the mail synchronization module 121 picks up the data received from the take-out data management module 155 of the smartphone 150 after the previous connection with the email client 101 (step 206). Here, the data to be picked up is newly created on the mobile device after the previous connection time, unsent email, unread / read status changed on the mobile device after the previous connection time, Or, it may be a forwarded e-mail or an address book updated on a mobile terminal.

  If the e-mail whose state has been changed on the mobile terminal side has already been deleted on the e-mail client 101 side, it is exchanged as synchronization data in step 207 and notified to the e-mail client 101. Is not reflected on the e-mail client 101 side.

  The deleted information is also reflected between the mobile terminal and the mail synchronization module 121, and the same content is retained. However, the information deleted on the mobile terminal side is not reflected in the email client 101. There is no need to send to the client 101.

  The synchronization data prepared in step 205 and step 206 are exchanged in step 207. After step 207 is completed, the e-mail client 101 executes step 208 in which the data received from the mail synchronization module 121 is updated. In step 208, an e-mail newly created on the mobile terminal after the previous connection time is sent as a created e-mail and stored in the sent tray, and an e-mail status change process that matches the mobile terminal is performed. Is called.

  However, in step 208, as described above, even if there is an e-mail or the like deleted at the mobile terminal, the e-mail client 101 does not delete it.

  In parallel with step 208, the mail synchronization module 121 performs step 209 for updating the data received from the email client 101. In step 209, a process for assigning a deadline to the newly marked mail and storing it in the synchronous data DB 122, and unread / read information or reply in the electronic mail already stored in the synchronous data DB 122 / A process of reflecting the change of the transferred information and an update process of the address book in the synchronous data DB 122 are performed.

  After step 208 and step 209 are completed, the e-mail client 101 transmits a connection end notification to the mail synchronization module 121 (step 210).

  FIG. 3 shows a synchronization sequence between the take-out data management module 155 of the smartphone 150 and the mail synchronization module 121 of the mail synchronization server 120.

  This sequence can be set to be started when the carry-out data management module 155 of the smartphone 150 periodically monitors the connectivity of the mail synchronization server 120 to the mail synchronization module 121 and connection becomes possible. . Further, as described above, when step 203 in FIG. 2 is executed and the smartphone 150 receives a synchronization instruction from the mail synchronization server 120, this sequence is performed.

  Step 301 is a step of starting synchronization, and the take-out data management module 155 establishes a connection to the mail synchronization module 121 and transmits the user ID and password of the mail user stored in advance. The mail synchronization module 121 performs step 302 for authenticating the take-out data management module 155 of the smartphone 150 by accepting the user ID / password of the mail user, and performs the subsequent steps if the authentication is successful.

  Whether the connection partner of the mail synchronization module 121 is the email client 101 of the desktop terminal 100 or the carry-out data management module 155 of the smartphone 150, for example, because the mail synchronization module service uses HTTP. For example, it can be determined by changing the URL.

  Step 303 is a step in which the mail synchronization module 121 returns the authentication result and the previous connection time information of the export data management module 155 to the export data management module 155.

  The take-out data management module 155 confirms the deadline information of the e-mail being taken out, deletes those that have passed the storage deadline, refers to the received previous connection time information, and takes out the take-out mailbox 156. And picks up data to be transmitted to the mail synchronization module 121 (step 304). Here, the data to be picked up is an e-mail received from the e-mail client 101 after the previous connection time, an unread / read status changed after the previous connection time, a reply, or a transfer. This corresponds to an e-mail marked with the mail client 101, an updated address book, and the like.

  When the user performs an operation for deletion on the mobile terminal, the export data management module 155 performs a process of adding a deletion mark to the email that is the export information without deleting it from the export mailbox. Keep it. The information to which the deletion mark is given also corresponds to the above pickup target.

  In parallel with step 304, the mail synchronization module 121 picks up the data received from the e-mail client 101 of the desktop terminal 100 after the previous connection with the take-out data management module 155 (step 305). Here, the data to be picked up is an e-mail newly marked on the desktop terminal 100 after the previous connection time, an e-mail newly created on the desktop terminal 100 and an unsent e-mail, after the previous connection time. An e-mail whose unread / read state has been changed, replied, or transferred on the desktop terminal 100, an address book updated on the desktop terminal 100, and the like are applicable.

  The synchronization data prepared in step 304 and step 305 are exchanged in step 306. After step 306 is completed, the take-out data management module 155 performs a process for updating the data received from the mail synchronization module 121. In this step, an e-mail newly created on the desktop terminal 100 after the previous connection time is transmitted as a created e-mail and stored in the sent tray, and an e-mail status change process in accordance with the desktop terminal 100 (Step 307).

  In parallel with step 307, the mail synchronization module 121 performs a process for updating the data received from the take-out data management module 155. In this step, the process of storing the mail newly created in the mobile terminal in the synchronization data DB 122 and the unread / read information or the reply / transferred information in the e-mail already stored in the synchronization data DB 122 The process of reflecting the change of the address book and the update process of the address book in the synchronous data DB 122 are executed (step 308). The e-mail to which the deletion mark is given in the take-out data management module 155 is deleted from the mail synchronization module 121. After step 307 ends, the take-out data management module 155 transmits a connection end notification to the mail synchronization module 121 (step 309).

  FIG. 4 is a diagram showing in detail the contents of the synchronization data DB 122 mounted on the mail synchronization server 120. The synchronization data DB 122 has usertable.txt, which is a table for storing a set of IDs and passwords of users who store synchronization data in order to support a plurality of users. As a DB format for managing each user's export data, for example, an MH (Mail Handler) folder format can be extended. In MH, each mail message is stored as one file under one directory (hereinafter referred to as a folder), and the mail synchronization server may allocate one folder for each connected user.

  In FIG. 4, the user's mail address is used as the name of the folder assigned to each connected user. In addition, syncdir is a subfolder that stores the mail messages to be synchronized, drafts is a subfolder that stores mail messages that are being created in any e-mail client, a destination display character string is used as a file name as a user address book, mail address, etc. Addressdir is used as a subfolder for storing a file group in which the information of the file and the last update time of the file are described.

  Furthermore, in step 203 of FIG. 2, in order to enable the mail synchronization module 121 to send a synchronization instruction to the smartphone 150 used by the user, mobile.addr is stored as a file for storing the email address assigned to the smartphone 150. use.

  The file name of the message file stored in syncdir is an integer representing the order of messages in the folder. Status information such as unread / read and reply / transferred is described as an additional field in the message header. For example, the unread / read state can be identified by the value of the x-seen field, whether it has been replied, by the x-replied field, and whether it has been forwarded by the value of the x-forwarded field.

  In addition, the e-mail client 101 of the desktop terminal 100 may use the additional field x-portable field of the message header in order to identify the e-mail to be taken out. Further, the additional field x-expiredate field may be used for the carry-out time limit information of each message. Further, the e-mail stored in the take-out mail box 156 that has been deleted on the mobile terminal can be distinguished using the additional field x-removed field corresponding to the above-described deletion mark.

  As for the deletion of the address book information, if the address book is deleted on one side when performing synchronization processing between the desktop terminal 100 and the mail synchronization module 121, and between the mail synchronization module 121 and the export data management module 155. The other is also erased.

  The time when each user last connected to the mail synchronization module 121 from the email client 101 of the desktop terminal 100 is recorded as the last connection time in the desktop.last file. In addition, the last connection time from the carry-out data management module 155 of the smartphone 150 to the mail synchronization module 121 is recorded as the last connection time in the mobile.last file.

  5A to 7B are flowcharts when the mail synchronization module 121 processes the steps 201, 202, 203, 205, 206, 208, and 209 shown in FIG. 2, and the steps that the email client 101 shows in FIG. 5 is a flowchart when processing 201, 203, 204, 206, 207, and 209;

  FIG. 5A shows a process executed by the mail synchronization module 121. Reference numeral 501 denotes a connection waiting process from the e-mail client 101 of the desktop terminal 100. The user ID and password receiving process 502 is executed after the connection is completed. Reference numeral 503 denotes user authentication processing, which checks whether the combination of the user ID and password received in processing 502 matches usertable.txt of the synchronization data DB 122. If they match, it notifies that authentication was successful and does not match. In this case, after notifying the e-mail client 101 that the authentication has failed, all the processes are terminated.

  Steps 504 and after are processes performed on the synchronous data DB 122 when user authentication is successful.

  504 is a process for obtaining the user's last connection time obtained in process 502 from the desktop.last file, and 505 refers to the mobile.addr file, and sends an e-mail instructing synchronization to the user's smartphone 150. In this process, the smartphone 150 is configured to execute the sequence shown in FIG. 3 when an electronic mail from the mail synchronization server 120 is received.

  The e-mail transmitted by the mail synchronization server 120 is, for example, the mail of the sender of the administrator user of the mail synchronization server, and the title and body may be empty, or an electronic signature is used to prevent impersonation of a third party. And the smart phone 150 may verify the electronic signature.

  506 is a process of notifying the e-mail client 101 of the desktop terminal 100 of the last connection time, and 507 is a data sent from the take-out mailbox after the last connection time and updated by the mail synchronization module 121 as electronic data. A thread for transmitting to the mail client 101, a process for generating a thread for receiving data updated by the e-mail client 101 after the last connection time, and a process 508 for waiting for the end of the thread.

  FIG. 5B is a process executed by the e-mail client 101. Reference numeral 511 denotes a connection process to the mail synchronization module 121 of the synchronization server 120. When the connection is successful, a user ID and password sending process 512 is executed. 513 is a process of waiting for reception of a user authentication result, 514 is a process of determining a user authentication result. If the user authentication is successful, a process of receiving the last connection time information of 515 from the mail synchronization module 121, and a process of 516 A process for generating a thread in charge of transmission and reception with the mail synchronization module 121 and a thread end wait process 517 are performed.

  6A and 6B are detailed flows of the sending thread and the receiving thread generated in the process 507 of the mail synchronization module 121. FIG.

  FIG. 6A is a process of a transmission thread, 601 is a process of searching for a message file and an address book file edited after the last synchronization time in the syncdir, drafts, and addressdir subfolders of the synchronization data DB 122, and 602 is a process. A process for storing the file group searched in 601 in the buffer, a process 603 for transmitting the buffer contents to the e-mail client 101, and a process for deleting the transmission thread 604.

  FIG. 6B is a process of the receiving thread. 611 is a process for storing the data received from the e-mail client 101 in the buffer. 612 is a process for dividing the data stored in the buffer in the process 611 into message data and address book data. It is a process of storing as a file in a directory.

  613 to 616 are processes related to the message data file, 613 is a process to check whether there is an unprocessed message, 614 is a process to open one unprocessed message file, and 615 is to extract the message ID field from the file opened in process 614 A process of searching for a matching mail message by comparing with the message IDs of the messages in the syncdir and drafts subfolders of the synchronization data DB 122, 616 rewriting the message in the synchronization data DB 122 matched by the search of the process 615, and This is a process for creating a new message in the synchronous data DB 122 when the search is not hit.

  In the case of a received mail, if the search is hit in the process 615, the status information field such as unread / read is added or changed, and if the hit is not found, new export information is added to the synchronous data DB 122. It will be done against. In the case of newly created mail, rewriting to the latest file is performed when the search is hit, and new export information is added to the synchronous data DB 122 when it is not hit.

  617 to 618 are processes related to the address book file in the synchronous data DB 122, 617 is a process to check whether there is an unprocessed address book file, 618 is a process to rewrite the address book file, and if there is no file with the same name, a new one is created. It will be added.

  619 is a process for deleting the reception thread, and before performing this process, all of the mail synchronization module 121 may check the storage period of the mail message, and if the time limit has passed, the process may be deleted. .

  7A and 7B are detailed flows of the sending thread and the receiving thread generated in the process 516 of the e-mail client 101. FIG. Here, the following description is given assuming that the e-mail client 101 uses the MH folder format as the format for managing e-mail messages. However, even when other message management formats are used, the message processing of the receiving thread is performed. It is easy for those skilled in the art to perform the equivalent of the processing shown below by converting the format.

  FIG. 7A shows the processing of the sending thread. 701 searches the local mailbox 103 of the e-mail client 101 for newly received or edited message files and address book files since the last synchronization time. 702, processing for storing the file group searched in processing 701 in the buffer, processing 703 for transmitting the buffer contents to the mail synchronization module 121, and processing 704 for deleting the transmission thread. Before transmitting the buffer contents in processing 703, the buffer data is compressed to reduce the network bandwidth required for transmission and the time required for transmission, and when the data received in processing 611 is stored in the buffer Alternatively, the received data may be decompressed.

  FIG. 7B is a process of the receiving thread. 711 is a process for storing the data received from the mail synchronization module 121 in the buffer. 712 is a process for dividing the data stored in the buffer in the process 711 into message data and address book data. It is a process of storing as a file in a directory.

  713 to 716 are processes related to the message data file, 713 is a process to check whether there is an unprocessed message in the temporary directory, 714 is a process to open one unprocessed message file, and 715 is a message from the file opened in process 714 A process of extracting the ID field, accessing the local mailbox 103, and searching for a matching mail message by comparing with the message ID of the message in the local mailbox 103; This is a process of rewriting in accordance with the additional writing and changing of the status information field such as unread / read in the mailbox 103. Further, for the newly created message on the mobile terminal that did not hit the search in the process 715, the mail transmission request process to the mail transfer agent 111 of the e-mail server 110 is performed, and the mail is stored in the sent tray or the like Perform the process.

  717 to 718 are processes related to the address book file that is accessed by accessing the local mailbox 103, 717 is a process for checking whether there is an unprocessed address book file, 718 is a process for rewriting the address book file, and there is no file with the same name. In this case, it is newly added.

  719 is a process for deleting a receiving thread. Before this process is performed, the storage period of all mail messages in the synchronous data DB 122 is confirmed. Also good.

  The processing in FIGS. 5A to 7B is a synchronization process between the e-mail client 101 and the mail synchronization module 121, but the same is true between the carry-out data management module 155 and the mail synchronization module 121 of the smartphone 150 shown in FIG. By performing the above process (however, the local mailbox 103 is replaced with the taken-out mailbox 156), it is possible to synchronize the mail data.

  In addition, since the information is taken out to the mobile terminal via the mail synchronization module 121, an interface may be provided in which information on the taken-out data is stored in the mail synchronization module 121 as a log and presented to the administrator.

  Further, when synchronizing message data between the mail synchronization module 121 and the take-out data management module 155, the mail synchronization module 121 analyzes the MIME header of the message data, and the mobile necessary for displaying the attached file portion of the message data. The code may be taken out from the mobile code DB 123 and stored in the take-out mail box 156 of the smartphone.

  When a new mail is created on the mobile terminal, a mobile code for creating an attached file is obtained from the mail synchronization server in accordance with a user instruction.

  The mobile code taken out is deployed on the virtualization platform 157 of the smartphone 150 or the virtualization platform 165 of the tablet terminal 160, and when the attached file is viewed on the email client 153 or 163, the attached file application 154 or It may be made available as 164.

  6 and 7, the MH folder format is extended as a format for storing electronic mail, but other electronic mail storage formats can be realized by the same extension. For example, in the case of Maildir format, the folder directory name in which the message is stored is different, and the status information of the electronic mail is added to the file name. These can easily be dealt with by finely adjusting the flowcharts shown in FIGS.

100: Desktop terminal,
101 ... an email client,
102 ... Application for attached file,
103 ... Local mailbox,
110: Mail server,
111 ... Mail transfer agent,
112 ... user mailbox,
120 ... mail synchronization server,
121 ... Mail synchronization module,
122 ... synchronous data DB,
130 ... Internal network,
140 ... Internet,
150 ... Smartphone,
151. Network interface for Internet connection,
152 ... Network interface for cooperation between mobile terminals,
153 ... an email client,
154 ... Attached file application,
155 ... Take-out data management module,
156 ... Mail-out mailbox,
160 ... Tablet device,
161: Network interface for Internet connection,
162: Network interface for cooperation between mobile terminals,
163 ... an email client,
164 ... Application for attached file

Claims (6)

An e-mail client system configured to include a first terminal, a second terminal, and a third terminal,
E-mail synchronization server
The first terminal comprises a local mailbox and a first e-mail client;
The second terminal is
A second email client;
Take-out data management function,
A take-out mailbox, and
The third terminal comprises a third e-mail client;
The mail synchronization server includes a mail synchronization module and a synchronization data DB,
The second mail client and the third mail client access the take-out mailbox provided in the second terminal,
The mail synchronization server includes a synchronization module that synchronizes export data with the first email client or the export data management function,
Before synchronizing the export data between the first mailbox provided in the first terminal and the synchronization data DB, the export data management function of the second terminal and the synchronization data DB The e-mail client system is characterized in that the taken-out data is synchronized with each other. The first e-mail client and the mail synchronization module perform the synchronization process performed at a predetermined timing.
The mail synchronization module performs authentication processing of the email client,
When the authentication is successful, the mail synchronization module performs the export data synchronization process with the export data management function of the second terminal,
After the synchronization process with the take-out data management function is performed, the result of the authentication process is returned,
An e-mail client system, wherein the export data synchronization process is performed between the local mailbox of the first terminal and the synchronization data DB of the mail synchronization server. The e-mail client system according to claim 2,
The predetermined timing is
When the first electronic mail client is activated, or when the export data to be exported to the export mailbox is specified, or during the activation of the first electronic mail client An e-mail client system, wherein the e-mail client system is one or more of either periodically or at the end of the first e-mail client. In the e-mail client system according to any one of claims 1 to 3,
The email synchronization module
The export data when the first email client of the first terminal and the email client of the second terminal or the third terminal store the export data in different formats An e-mail client system that converts the storage format of the e-mail. The e-mail client system according to any one of claims 1 to 4,
The e-mail client system, wherein the take-out data includes e-mail and / or an address book. The e-mail client system according to claim 4.
The mail synchronization server includes a mobile code DB for storing a mobile code for processing an attachment to an email,
The mail synchronization module transmits a mobile code necessary for displaying an attached file to the email data to the export data management function when synchronizing the synchronization data DB and the export mailbox. E-mail client system featuring.

Images