JP5722072B2 - Mail terminal device and mail client program - Google Patents

Description

  The present invention relates to a mail terminal device and a mail client program.

  E-mail is widely used as a method for exchanging messages using a computer network. Also, mobile phone terminals provide services for exchanging messages such as SMS (Short Message Service) and MMS (Multimedia Messaging Service) between contract terminals of the same carrier, and computers connected to the mobile phone terminal and the Internet. Alternatively, exchanging electronic mails with contract terminals of other communication carriers is also widely performed.

  E-mails that have been operated by individual communication methods (protocols) in individual local networks are spread on the TCP / IP network as the Internet spreads, so that SMTP (Send Mail Transfer Protocol), POP (Post Office Protocol), It is operated by a common protocol defined by RFC, such as IMAP (Internet Message Access Protocol) and MIME (Multipurpose Internet Mail Extensions).

  The e-mail of mobile phone terminals is basically operated according to the same protocol, but has been expanded and modified in order to support networks and services provided by mobile carriers. In some cases.

Japanese Patent Laid-Open No. 1997-261344

  In order to create, send, receive, view and manage messages on a mobile phone terminal, it is necessary to execute a MUA (Mail User Agent) program (hereinafter sometimes referred to as a mailer or mail client) on the mobile phone terminal. There is. However, the cellular phone terminal is limited in processing capacity and memory capacity as compared with general-purpose computers such as personal computers and server computers, and the memory configuration is also different. For this reason, in a mail client for a mobile phone terminal, a problem specific to the mobile phone terminal may occur.

  For example, when e-mail messages are stored in the flash memory of a mobile phone, a process of reading a large amount of data stored in the flash memory is required to display the message list. For this reason, when the read / write speed of the flash memory is low, a time lag occurs between the time when the user enters a command to display the message list and the time when the list screen is displayed, and the response to the user's command input is delayed. It becomes difficult to operate comfortably.

  Further, when a database API is incorporated in the platform of the mobile phone terminal, it is possible to easily manage data of messages and addresses by using the database API. However, since the use of the database API intervenes the execution of the function, the use of the database API also causes a delay in response from command input to screen display.

  Accordingly, an object of the present invention is to provide a mail terminal device and a mail client program that can display a message list screen with good response even when a large number of messages are stored in a flash memory. It is another object of the present invention to provide a mail terminal device and a mail client program that can display a message list screen with good response even if messages are managed as a database.

In order to solve the above problems, a first aspect of the present invention is to provide a mail terminal apparatus including a writable nonvolatile memory storing a mail client program, a volatile memory, a processing device, and a display device. It is.
The processing device used for this mail terminal device, by executing a mail client program, accumulates messages consisting of header information and body information in a mailbox that is a database for each account provided on the nonvolatile memory, When starting the mail client program, a message is acquired from the mailbox of the account set as a default, and the header information of the acquired message is cached in volatile memory. The header information cached in the volatile memory is displayed on the display device.
In addition, this processing device acquires a message from the mailbox of the account selected after the mail client program is started if no account is set as the default when the mail client program is started. The header information of the received message is cached in a volatile memory.
In addition, when the account is switched after the mail client program is started, this processing device discards the contents cached in the volatile memory before the switching and acquires a message from the mailbox of the account after the switching. Thus, the header information of the acquired message is cached in a volatile memory.

In the configuration of this mail terminal device, it is preferable to set an upper limit for the number of messages cached from the mailbox to the volatile memory. It is also preferable to set an upper limit for the capacity cached from the mailbox to the volatile memory.

Further, processing apparatus, by executing a mail client program, stores the body information of the message acquired from the mail box in a file in the nonvolatile memory, Bo Di information stored in the file of the nonvolatile memory May be displayed on the display device.

A second aspect of the present invention is a mail client program that is executed by a mail terminal device that includes a writable nonvolatile memory, a volatile memory, a processing device, and a display device. This program causes the processor, a message consisting of the header information and body information, and Luz step be accumulated in the mail box is a database for each account provided on the nonvolatile memory, when starting of the mail client program, retrieving messages from the account of the mail box is set to the default, view the header information of the acquired message cache to Luz step in a volatile memory, a display device header information cached in the volatile memory characterized in that to execute the automatic answering step is.
In this program, the step of caching in the volatile memory is that the mail of the account selected after the mail client program is started if no account is set as default when the mail client program is started. A message is acquired from a box, and header information of the acquired message is cached in a volatile memory.
In this program, the step of caching in the volatile memory is to discard the contents cached in the volatile memory before the switching when the account is switched after the mail client program is started. A message is acquired from an account mailbox, and header information of the acquired message is cached in a volatile memory.

In the above program, in the step of caching in the volatile memory, it is preferable to set an upper limit on the number of messages cached from the mailbox to the volatile memory. Further, in the step of caching the volatile memory, it is preferable that the capacity of the cache from the mailbox to the volatile memory an upper limit value.

Further, the processing apparatus, the body information of the message acquired from the mail box to execute the automatic answering step to store the file in the nonvolatile memory, in the step of causing the display on the display device, stored in a file in the nonvolatile memory Bo di information may be configured to be displayed on the display device.

According to the mail terminal device and the mail client program of the present invention, a message composed of header information and body information is stored in a mailbox that is a database for each account provided on a rewritable nonvolatile memory . At startup, a message is acquired from the account mailbox set as default, and the header information of the acquired message is cached in the volatile memory, and the header information cached in the volatile memory is stored in the display device. The displaying step is executed. Therefore, a large amount of access to the rewritable nonvolatile memory (flash memory) having a low access speed does not occur between the command input and the display, and the message header is sent from the faster volatile memory (RAM). Information can be read and displayed with good response.

Here, be cached messages of a predetermined number from the most recent message, and / or, if the message as the most recent message does not exceed a predetermined capacity and cached, the consumption of the volatile memory Ya The cache processing overhead can be suppressed so as not to become excessive.

Further, when the present invention is applied to a mail terminal device and a mail client program in which a message including header information and body information is stored in a mailbox that is a database for each account , header information cached in a volatile memory and it is possible to read back without interposing a database API, thereby making it possible to reduce the overhead of interposing the database API.

In this case, caches part of the header information of the message to further the volatile memory, the body information is accumulated in a file in the nonvolatile memory, the display device body information of the stored message to the file It is preferable to display on the screen. The body information of the message is larger than the header information and may be difficult to cache due to the capacity of the volatile memory, but the body information can be stored as a file on the nonvolatile memory without using at least the database API. Information can be read and displayed.

  It is a hardware block diagram of the terminal device concerning one embodiment of the present invention.   It is a software block diagram of the terminal device concerning one Embodiment of this invention.   It is a block diagram of a mail client program.   (A) is a drawing showing an example of a folder list display section screen, (b) an example of a message list display screen, (c) an example of a message individual display screen, and (d) another example of a message list display screen.   (A) is drawing which shows an example of the data structure of a message, (b) is drawing which shows another example of a data structure.   It is the flowchart which showed the operation example of the mail terminal device.   It is the flowchart which showed the operation example of the cache process.

  Embodiments of a mail terminal device and a program according to the present invention will be described below. FIG. 1 is a hardware block diagram of a communication terminal device 100 which is an embodiment of a mail terminal device according to the present invention. This figure shows a standard hardware configuration, and some of the functional blocks are also shown that are not related to the present invention. As shown in FIG. 1, this communication terminal device 100 mainly includes an application processor 101 and a baseband processor 102 as processing devices, a battery 103 connected to the application processor 101, a RAM 104 as volatile memory, and a writable memory. Flash memory 105 which is a nonvolatile memory, memory card terminal 106, GPS transceiver 108, WiFi / Bluetooth transceiver 109, keypad / button 110, LCD / touch panel 111, microphone 112, speaker 113, USB terminal 114 and camera 115, base A transceiver / USIM 107 connected to the band processor 102 is included. Hereinafter, these configurations will be described.

  The application processor 101 is an MPU or CPU, and is a unit that implements various functions by receiving power supplied from the battery 103 and executing a program stored in a flash memory 105 described later. The baseband processor 102 is a processor that performs signal processing for realizing basic functions of wireless communication. The application processor 101 and the baseband processor 102 may be configured as one chip set, or the functions of both may be integrated into one processor.

  The battery 103 is a unit that supplies power to each functional block, and a controller chip that controls the battery is used in combination as necessary.

  The RAM 104 is a volatile memory and employs a semiconductor storage device such as SRAM, PSRAM, and various DRAMs. The flash memory 105 is a rewritable nonvolatile memory, and may be a NAND type, a NOR type, or another type. Comparing the RAM 104 and the flash memory 105, the RAM 104 is faster in both reading time and writing time. In addition, the communication terminal device 100 is provided with a memory card terminal 106, and a small flash memory module can be connected as an external memory.

  The flash memory 105 stores various programs and data for realizing predetermined functions in the communication terminal device 100 by being executed by the application processor 101 and the baseband processor 102. These programs and / or data are loaded into the RAM 104 as necessary, and are executed using a heap memory secured on the RAM 104.

  The transceiver / USIM 107 is connected to the baseband processor 102, and transmits / receives radio waves in a predetermined radio wave band under the control of the baseband processor 102 based on information of the installed USIM (Universal Subscriber Identity Module), that is, a general-purpose subscriber identification module. This is a circuit that performs communication. The communication terminal device 100 according to the present embodiment is configured to perform communication by connecting to a mobile communication network using a baseband processor 102 and a transceiver / USIM 107.

  The GPS transceiver 108 is a unit for receiving a GPS signal for acquiring position information of the communication terminal device 100. The WiFi / Bluetooth transceiver 109 is defined by IEEE802.11a, IEEE802.11b, IEEE802.11g, IEEE802.11n, and the like. This is a circuit for performing communication using the established WiFi (wireless LAN) technology and communication using the Bluetooth technology defined by IEEE 802.15.1 and the Bluetooth standard. These circuits may be mounted as chips independent of each other, or a configuration in which both circuits are mounted on one chip may be used.

  The keypad / button 110 is an input device provided in the housing of the communication terminal device 100 and accepts an input for the user to operate the communication terminal device 100 together with an LCD / touch panel 111 described later.

  The LCD / touch panel 111 is a liquid crystal display device having a touch panel function, and the communication terminal device 100 displays application information on the screen of the LCD / touch panel 111 and displays a GUI (Graphical User Interface). To serve.

  Furthermore, the microphone 112 and the speaker 113 realize voice input / output in the communication terminal apparatus 100, and the USB 114 is used to connect the communication terminal apparatus 100 to another device to transmit / receive data and control functions. The In addition, the camera 115 provides a function of taking a picture with the communication terminal device 100.

Next, an outline of the configuration of the program stored in the flash memory 105 of the communication terminal device 100 configured as described above will be described. FIG. 2 is a diagram showing an overall program configuration of the communication terminal apparatus 100.
As shown in FIG. 2, the program configuration of the communication terminal device 100 is mainly composed of three layers: an operating system 200, middleware 202, and an application 207. These programs are stored in the flash memory 105, and at the time of execution, various functions are realized by being executed by the application processor 101 and / or the baseband processor 102 using the RAM 104 as necessary.

  The operating system 200 includes a device driver 201 for controlling hardware, and provides basic functions as a computer system such as input / output control, memory management, and process management to the middleware 202 and the application 207. .

  The middleware 202 is represented by, for example, a graphic library 203 that performs graphic processing, an HTML rendering engine 204 that performs rendering processing of HTML files, a database management system 205 that provides a database API for managing a database, and Iibc in a Unix-based OS. The standard library 206 is included, and general-purpose functions used by the application 207 are provided. Here, when the communication terminal 100 executes a program that requires an execution environment such as a Java (registered trademark) application, the execution environment is mounted as the middleware 202.

  The application 207 includes a browser 208 that acquires a Web page and displays a screen created by the HTML rendering engine 204, a mail client program 209, which will be described later, a telephone application 210 that provides a telephone function, and the like. It provides various functions.

  Hereinafter, the mail client program 209 will be described. FIG. 3 is a drawing showing the software block diagram of the mail client program 209 together with the data stored in the flash memory 105. As shown in FIG. 3, the mail client program 209 mainly includes a menu display unit 221, an account setting management unit 222, an address management unit 223, a message management unit 227, and a cache management unit 234. Although FIG. 3 shows a state in which all functional blocks are arranged in the RAM 104, each functional block may be loaded from the flash memory 105 at a necessary timing. The data includes the account information 241, the address data part 242, the mail box A 243 and the mail box B 244 (hereinafter may be collectively referred to as a message box) managed by the database management system 205, and the body information storage file 250. Contains.

  The folder list display unit 221 is a block that forms a screen that is displayed after activation, and displays a list of folders that have been set for the mailbox of the account that is set as a default for selection by the user. A UI for calling account switching, setting, mail creation, and address book display functions is also displayed on the screen. FIG. 4A shows an example of a screen formed by the folder list display unit 221.

  The account setting management unit 222 is called by operating the account switching UI or the setting UI from the screen formed by the folder list display unit display unit 221, and displays the account list to switch the account to the one selected by the user. Provide functions and account settings. User account information set and managed by the account management unit 222 is stored in the account information unit 241 managed by the database management system 205.

  The address management unit 223 is called by operating the UI for address book display from the screen formed by the folder list display unit display unit 221, and displays an address list display unit 224 that displays a list of registered addresses. An address individual display unit 225 for individually displaying on a screen and an address addition / modification unit 226 for adding an address and modifying a registered address are provided, and processing for using and managing data registered in the address book is performed. The address book data managed by the address management unit 223 is stored in the address data unit 242 managed by the database management system 205.

  The message management unit 227 includes a message display unit 228 including a message list display unit 232 that displays a list of messages (referred to as individual emails created or transmitted / received by the mail client program 209) and a message individual display unit 233 that displays messages individually. A message creation / editing unit 229 for creating and editing a new message, a message sending unit 230 for sending a message by connecting to a mail server, and a message receiving unit 231 for receiving a message by connecting to the mail server. Create and send new mail, receive and manage new mail, and display it on the screen. Here, FIG. 4B is an example of a screen displayed by the message list display unit 232, and FIG. 4C is an example of a screen displayed by the message individual display unit 233. Mail data storing messages managed by the message management unit 227 is stored in a mailbox managed by the database management system 205.

  Hereinafter, the data format of messages and mailboxes managed by the message management unit 227 will be described. A message transmitted and received by the mail client program takes a standard data format as an electronic mail, and its structure is as shown in FIGS. 5 (a) and 5 (b). FIG. 5A shows the data structure of a text mail without an attached file, and the message in this case has a structure in which header information and body information consisting of a body are separated by a blank line. On the other hand, FIG. 5B shows the data structure of a multipart mail to which a file is attached. In this case, the message has empty header information and body information consisting of a body part and an attached file part. The structure is separated by lines.

  The message management unit 227 receives a reception type, Uid, title, reception date, transmission date, transmission source, reply destination, which indicates whether the received form is (T0, CC, BCC) from such a message. Extracting or judging body information, content format, MIME type, etc., and further providing a message object with a database name storing the message, an ID used as a primary key of the database, a utility flag, a folder name, a read flag, etc. Manage the message object. Further, the message object is stored in the mailbox A243 or the mailbox B244 using the database management system 205, and managed as a database.

  The cache management unit 234 acquires the message object used by the message management unit 227 from the mailbox A243 or B244, places data other than the body information in the message cache 235 on the RAM 104, and the body information is stored in the flash memory 105. It is stored in the body information storage file 250 and used for the message management unit 227.

  That is, when the message management unit 227 displays a message by the message display unit 228, the message list display unit 232, and the message individual display unit 233, the header information of the message to be displayed is read from the mail database cache 235, and the body information Is read from the body information storage file 250 to generate a display screen.

  As a result, the reading amount of the flash memory 105 can be reduced, and the overhead of using the database management system 205 can be reduced, so that message display can be performed with good response. However, since there is still a load on the process in which the cache management unit 234 caches the message, it is preferable to start the message caching in advance in a prefetched form. For example, when an account to be displayed after activation is determined, message caching can be started for the account at the time of activation and executed in the background. In this case, when the user switches accounts using the account management unit 222, the contents cached so far must be discarded and message caching for a new account must be started. When an account to be displayed is selected after activation, message caching can be started when the account is selected.

  Here, the cache management unit 234 can place all of the message objects acquired from the mailbox in the message cache 235. However, a message with an attached file may reach a size of several megabytes because the body information includes the data of the attached file, and the memory is insufficient when the capacity of the RAM 104 that can be used by the mail client program 209 is limited. There is concern to become. For this reason, in this embodiment, the body information is stored in the body information storage file 250 on the flash memory 105.

  In addition, if all messages are cached with a large amount of messages stored in the mailbox, there is a problem that the time required for the cache processing and the amount of consumption of the RAM 104 become excessive. For this reason, in this embodiment, an upper limit value (for example, 500) is set for the number of messages to be cached, and an upper limit value (for example, 10 MB) is set for the cache capacity. However, these restrictions are not essential, and an upper limit value may be set only for either the number of messages or the cache capacity, or a configuration in which no upper limit value is provided. Further, the upper limit value may be other values.

  The message list display unit 232 displays a predetermined number of messages on the screen in a list format, and the list of messages is sequentially sent by scrolling the screen. Therefore, if scrolling is repeated, the displayed message exceeds the cached range, and the message cannot be displayed as it is. Therefore, the cache management unit 234 needs to move the range of the message to be cached according to the scrolling of the screen so that the message to be displayed is always cached.

  When the message management unit 227 creates or edits a message with the message creation / editing unit 229, when the message transmission unit 230 transmits a message, and when the message reception unit 231 receives a message, first, the message cache 235 and The contents of the body information storage file 250 can be updated, and then the cache management unit 234 can synchronize the contents of the mailbox with the updated contents.

  The account information unit 241 is a database that stores account information for logging in to a mail server used for message transmission / reception, and is provided on the flash memory 105. The account information includes a mail address used for mail transmission / reception, and is associated with a mail box in which messages transmitted / received at the mail address are stored.

  The address data unit 242 is a database that stores information of a partner that transmits and receives messages, and is provided on the flash memory 105. The address data part 242 includes the name of the other party, the mail address, and the like.

  Mailboxes 243 and 244 are databases in which messages transmitted and received for each account are accumulated, and are provided on the flash memory 105. Mailboxes 243 and 244 are read by message display unit 228 and message creation / editing unit 229 of message management unit 227, and messages received by message reception unit 231 and background reception unit 233 by mailbox registration unit 232 are added. be registered.

  The body information storage file 250 is a file provided on the flash memory 105 in order to store the body information of the message acquired by the cache management unit 234 from the message box.

  Hereinafter, the operation of the mail client program 209 will be described with reference to the drawings. FIG. 6 is a flowchart showing the operation of the mail client program 209, and FIG. 7 is a flowchart showing the operation of the cache processing.

  In this operation, the mail client program 209 is first activated (ST101), and then it is determined whether a default account, that is, an account used when no instruction is given after activation (ST102), is set. If not set, account registration / default account setting is performed (ST103).

  If it is determined in ST102 that the setting is made, the cache processing for the mailbox associated with the default account is started (ST104). This cache process is executed asynchronously with the processes after ST105 using, for example, a multi-thread function. That is, the mail client program 209 performs an operation of advancing the processing after ST105 in parallel with the cache processing without waiting for the completion of the cache processing of ST104.

  Hereinafter, the cache processing operation in ST104 will be described with reference to FIG. In this operation, first, an area of the message cache 235 is secured on the RAM 104 (ST121), and a body information storage file 250 is prepared on the flash memory 105 (ST122). Next, the counter k is set to 1 (ST123), and the k-th message from the latest of the target mailbox, that is, the mailbox associated with the default account is acquired (ST124). The message acquisition here is executed via the database management system 205 (database API).

  Next, the header information of the message acquired in ST124, that is, information other than body information is stored in the message cache (ST125), and the body information of the message is stored in the body information storage file 250 (ST126). As a result, the mail client program 209 can read message header information and the like from the RAM 104 faster than the flash memory 105 without using the database management system 205. Also, the body information of the message can be read without going through the database management system 205.

  Subsequently, it is determined whether the counter k has reached the upper limit value (ST127). If it is determined that the counter k has been reached, the cache processing is terminated. If it is determined in ST127 that the cache capacity has not been reached, it is next determined whether or not the cache capacity has exceeded the upper limit value (ST128). If it is determined that the capacity has been exceeded, the cache processing is similarly terminated. On the other hand, if it is determined in ST128 that the value does not exceed, the value of the counter k is incremented (ST129), and the processes after ST124 are repeated.

  Hereinafter, the processing after ST105 of FIG. 6 performed in parallel with the cache processing will be described. First, folder information is read from the mailbox associated with the default account, and based on this, the folder list screen in the mailbox is displayed on the screen illustrated in FIG. 4A (ST105). After this screen is displayed, it is determined whether any folder has been selected by the user (ST106). If it has not been selected, it is determined whether application termination has been instructed (ST107), and application termination has been instructed. If the application is not instructed to end the application, the process after ST106 is repeated.

  On the other hand, if it is determined in ST106 that any folder is selected, information relating to the message in the selected folder is extracted from message cache 235 (ST108). That is, at this stage, the message cache 235 stores the header information and the like of the message extracted from the mailbox by the cache processing started in ST104, so the message stored in the folder selected from the message cache 235 is stored. Extract. Subsequently, the message list screen is rendered from the extracted message information (ST109), and the message list screen in the folder selected on the screen illustrated in FIG. 4B is displayed (ST110).

  After the list screen is displayed, it is determined whether any message has been selected by the user (ST111). If not selected, it is determined whether the end of list display is instructed (ST112). If the end of list display is instructed here, the process returns to the folder list display of ST105, and if the end of list display is not instructed, the determination of ST111 is repeated.

  On the other hand, if it is determined in ST111 that any message is selected, body information of the selected message is acquired from the body information storage file 250 (ST113), and based on this, the message individual display screen is displayed. Rendered (ST114), the message individual display screen illustrated in FIG. 4C is displayed (ST115). Thereafter, it is determined whether or not the user has instructed the end of the individual display screen (ST116). If instructed, the process returns to the message list screen display in ST110, and if not instructed, the determination in ST116 is repeated.

  In the operation as described above, before the user selects a folder to be displayed from the folder list displayed in ST105, the message header information is cached in the message cache 235 on the RAM 104 by the cache processing started in ST104. . When the user selects a folder to be displayed, messages in the folder to be displayed are extracted from the message cache 235 (ST108), a message list screen is rendered (ST109), and screen display is performed (ST110). That is, unlike the method of reading a message from the mailboxes 243 and 244 on the low-speed flash memory 105 using the database management system 205 after the user selects a folder to be displayed, the folder is selected and the message list is displayed. A large amount of access to the low-speed flash memory 105 does not occur, and the database management system 205 does not intervene. Therefore, it is possible to effectively shorten the time lag from folder selection to message list display and improve the response.

  Also, when the user selects a predetermined message from the message list displayed in ST110 and performs individual display, the body information of the selected message is read from the body information storage file 250 on the flash memory 105, so that the flash Access to the memory 105 is minimal. However, in this case as well, the body information can be read without intervening the database management system 205, so that the time lag from message selection to individual display can be shortened and the response can be improved.

  In addition, since the cache process is executed asynchronously in the above operation, the message list screen is displayed before the cache process is completed, so the degradation of the response due to the cache process itself being overhead is minimized. ing. Furthermore, since the upper limit is set for the number of messages to be cached and the capacity, the message cache 250 does not press the free capacity of the RAM 104.

  Also, depending on the message, the body information may be several MB, but in the above operation, the header information of the message is cached in the RAM 104, and the body information is cached in a file on the flash memory 105. The free space of the RAM 104 is not compressed by the body information.

  As described above in detail, according to the mail terminal device and mail client program of the present invention, a message list screen can be displayed with good response even if a large number of messages are stored in the flash memory, and messages can be stored as a database. Even if is managed, the message list screen can be displayed with good response.

  The present invention is not limited to the above embodiment, and various modifications can be made. For example, instead of or in addition to the message list screen of FIG. 4 (a) and the message individual display screen of FIG. 4 (b), a message list is shown in the upper half of the screen as shown in FIG. 4 (d). It is also possible to adopt a screen that displays the body of the message that is focused on the lower half. In this case as well, the display response can be improved by caching the message.

  The timing for starting the cache processing is not limited to the above, and there is no particular limitation as long as it is before the message is required. However, from the viewpoint of caching a sufficient amount of messages when messages are required, it is desirable to start the cache processing when the account to be displayed is determined. If the account is switched after the message is cached, it is necessary to discard the cached contents before caching the message of the new account.

  Further, it is desirable that both the message cache 235 and the body information storage file 250 are deleted when the mail client program is terminated. However, if the mail client program is forcibly terminated, normal termination processing may not be performed. In such a case, the message cache 235 is deleted from the RAM 104 together with the application heap area, but the body information storage file 250 remains in the flash 105. In order to avoid this, it is preferable to check whether or not the body information storage file 250 created last time remains when the mail client program is started, and to delete it if it remains.

  Furthermore, the case where the present embodiment is applied to a mobile terminal connected to a mobile communication network has been described above. However, the present invention is widely applicable to mail terminal devices and mail client programs of the type that store messages in a flash memory or the like. It is possible to apply.

104 RAM
105 Flash memory 205 Database management system 221 Folder list display unit 223 Address management unit 224 Address list display unit 225 Address individual display unit 226 Address addition modification unit 227 Message management unit 228 Message display unit 229 Message creation / editing unit 230 Message transmission unit 231 Message Reception unit 232 Message list display unit 233 Message individual display unit 234 Cache management unit 235 Message cache 241 Account information unit 242 Address data unit 243 Mailbox A
244 Mailbox B
250 Body information storage file

Claims (12)

A mail terminal device comprising a writable nonvolatile memory in which a mail client program is stored, a volatile memory, a processing device, and a display device,
The processing device executes the mail client program,
A message consisting of the header information and body information, stored in the mail box is a database for each account that is provided on the non-volatile memory,
When starting the mail client program, obtain a message from the mailbox of the account set as a default , cache the header information of the obtained message in the volatile memory,
A mail terminal device that causes the display device to display header information cached in the volatile memory . If no account is set as default when the mail client program is started, a message is acquired from the mailbox of the account selected after the mail client program is started, and header information of the acquired message is acquired. The mail terminal device according to claim 1, wherein the mail terminal device is cached in the volatile memory. When the account is switched after the mail client program is started, the contents cached in the volatile memory before the switching are discarded, the message is acquired from the mailbox of the account after the switching, and the acquired 3. The mail terminal device according to claim 1, wherein message header information is cached in the volatile memory. The mail terminal device according to any one of claims 1 to 3, wherein an upper limit is provided for the number of messages cached from the mailbox to the volatile memory. Mail terminal device as claimed in any one of claims 4, characterized in that an upper limit value to the capacity of the cache in the volatile memory from the mailbox. The processing device executes the mail client program,
further,
Storing the body information of the message obtained from the mailbox in a file on the nonvolatile memory;
Mail terminal device according to any one of claims 5 to file volume di information stored on the nonvolatile memory of claims 1, characterized in that to be displayed on the display device. A mail client program that is executed by a mail terminal device including a writable nonvolatile memory, a volatile memory, a processing device, and a display device,
In the processing device,
A message consisting of the header information and body information, and Luz step be accumulated in the mail box is a database for each account that is provided on the non-volatile memory,
When starting the mail client program obtains the message from the account of the mail box is set to the default, the cache to Luz step header information of the acquired message to the volatile memory,
And Luz steps to display the header information cached in the volatile memory to the display device,
A mail client program characterized by executing The step of caching in the volatile memory obtains a message from the mailbox of the account selected after the mail client program is started if no default account is set when the mail client program is started. The mail client program according to claim 7, wherein the header information of the acquired message is cached in the volatile memory. When the account is switched after starting the mail client program, the step of caching in the volatile memory discards the contents cached in the volatile memory before the switching, and the account mailbox after switching The mail client program according to claim 7 or 8, wherein a message is acquired from the cache and header information of the acquired message is cached in the volatile memory. Wherein in the step of caching the volatile memory, according to any one of claims 7 to 9, characterized in that an upper limit value from the mailbox number of the message to be cached in the volatile memory write Client program. Wherein in the step of caching the volatile memory, wherein the mailbox according to any one of claims 10 claim 7, characterized in that an upper limit value to the capacity of the cache in the volatile memory mail client program . In the processing device,
Further, the body information of the message obtained from the mailbox to execute the automatic answering step be stored in a file on the non-volatile memory,
The step of displaying on the display device, according to any one of the nonvolatile claims file volume di information stored in the memory from the claims 7, characterized in that to be displayed on the display device 11. Mail client program.

Images