JP2007280411A - Method and device for pushing e-mail to radio communication device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method for pushing e-mail information from an e-mail server to a plurality of radio communication devices. <P>SOLUTION: Each e-mail server can be publicly accessed and manages a plurality of unsubscribed e-mail accounts related respectively to the plurality of radio communication devices. An e-mail management client logs on the e-mail servers by proxy of the plurality of unsubscribed e-mail accounts, thus, TCP/IP connection is established and maintained. After that, e-mail change notification information for all the e-mail accounts is continuously received during single TCP/IP connection. E-mail information is retrieved, e-mail information for "real time" reception by the plurality of radio communication devices is retrieved and pushed based on the e-mail change notification information. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

Background of the Invention
The present invention relates generally to a system for “pushing” electronic mail information to a plurality of wireless communication devices. In particular, the present invention logs on to multiple email servers on behalf of multiple unsubscribed email accounts to establish and maintain a single session connection with each email server and stores email information. The present invention relates to an email management client configured to receive account email change notification information so that it can be simultaneously pushed to a plurality of wireless communication devices in real time.

DESCRIPTION OF THE PRIOR ART FIG. 1 is a diagram of a system 100 in which email information is pushed from an email server 152 to a plurality of wireless communication devices 104 in a conventional manner. A private network 142, which can be a local local area network (LAN), includes an email server 152 along with a plurality of computers 144, an enterprise server 154, and a firewall 156. Each end user of computer 144 in private network 142 has an email account managed by 152 in an email server operating in accordance with the well-known email receiving protocol (POP) standard. In this way, the plurality of computers 144 can connect to and access personal email messages from the email server 152 as is conventional. Of course, all computers 144 operate within a private network 142 that is governed and / or managed by the same single entity (eg, the same company), in that respect they are in line. . For simplicity, the figure shows three computers 144, PC1, PC2,. . . Only the computers 146, 148, 150 labeled PCn are shown.

  Each computer 144 and / or its corresponding email account is associated with a respective one of the wireless communication devices 104. Each wireless communication device 104 is portable and has a display and keyboard / keypad (eg, a small QWERTY keyboard) along with a wireless transceiver, antenna, and one or more processors that control the operation of the device. Includes housing. Each wireless communication device 104 has a capability of transmitting and receiving e-mail information related to an e-mail account managed by the e-mail server 152. Unlike any method that requires a wireless communication device 104 to connect to receive email information, the email information is received by each device 104 through a real-time automatic “push” approach.

Enterprise server 154 facilitates the push of email information from email server 152 to wireless communication device 104. During system setup, a virtual private network (VPN) connection is established and maintained via a dedicated line 158 between the enterprise server 154 and the repeater 160. In addition, one dedicated connection 155 is established and maintained between the enterprise server 154 and the email server 152. For example, the dedicated connection 155 may be a MAPI (Messaging Application Programming Interface) associated with Microsoft Exchange. When a new email account is set up in private network 142, the server address of email server 152 (or other server) is provided to enterprise server 154 for the new account. When the email server 152 detects a change to the email account (e.g., receiving a new email, a message moved from one folder to another folder, etc.), the email server 152 connects the enterprise via the dedicated connection 155. E-mail change notification information is transmitted to the server 154 in real time. The email change notification information includes a notification identifier that uniquely identifies the email change. When enterprise server 154 receives notification information for a particular account, enterprise server 154 receives the email information corresponding to the notification identifier by sending a message to the stored server address for the email account. Request that. When the enterprise server 154 receives the e-mail information, the enterprise server 154 pushes the e-mail information to an appropriate wireless communication device via the relay 160 and the wireless network that is providing services to the device. Although this conventional operation will be described in relation to a single private network 142, the push of electronic mail information is simultaneously performed for a plurality of private networks via the same relay device 160. Such an operation is described in the pending application, the title of the invention “System and Method for Pushing Information from the Host System to the Mobile Data Communication Device”.
Host System to a Mobile Data Communication Device), US Application No. 09 / 401,868, filed September 23, 1999, assigned to the current rights holder and described in more detail.

  The system described above works effectively and is suitable for handling unsubscribed emails in a private network. However, Internet-based e-mail has moved to support known as the Internet Message Access Protocol (IMAP) standard for e-mail and message storage. IMAP is designed as an alternative to the old POP method for mail access. The main strength of IMAP is its ability to support multiple simultaneous access to one or more mailboxes from many clients. This allows two or more users or two or more computers to access the same information without worrying about failure or damage to the information storage area.

  Regarding wireless handheld mobile devices, it is an important function to push information in real time and notify the mobile device that a mail has been received. However, conventional IMAP is not designed to facilitate push-based messaging services to a large number of end users in an effective and scalable manner. IMAP is designed in the same way as POP in that it focuses on polling or connection-based solutions that require clients to connect to read their mail. Email notifications can be automatically delivered in real time using IMAP, which requires a single TCP / IP connection to be established and maintained for each email account / mailbox. This limitation makes it impossible to fully standardize IMAP to support a large number of mobile terminal users. Polling for new data and / or data changes is an option, but as the number of users increases (eg, in the thousands or hundreds of thousands), this mechanism will fail. The number of physical IMAP servers that support such polling and connection requests will ultimately be an unmanageable solution for any operations center.

  Accordingly, there is a need for a scalable and effective system for pushing email information from one or more email servers to multiple wireless communication devices.

( Summary of the Invention)
This document describes a system for “pushing” email information from multiple email servers to multiple wireless communication devices. Each e-mail server is publicly accessible and manages a plurality of unsubscribed e-mail accounts associated with a plurality of wireless communication terminals. The email management client logs on to the email server as a proxy for a plurality of unsubscribed email accounts, and a TCP / IP connection with the email server is established and maintained. Thereafter, email change notification information for multiple unsubscribed email accounts is continuously received throughout a single TCP / IP connection. Based on the e-mail change notification information, the e-mail management client can retrieve and push e-mail information for real-time reception by a plurality of wireless communication devices.

  The email server identifier and email notification identifier comprise each email change message so that a request to receive specific email information is reasonably easily performed. Also, user configurable delivery settings are conveniently provided so that email information is pushed (if any) as specified by the end user.

  Thus, the present invention effectively provides a scalable and effective system for pushing electronic mail information from one or more electronic mail servers to a plurality of wireless communication devices.

Detailed Description of the Preferred Embodiment FIG. 1 is a diagram of a novel system 100 in which email information is pushed from multiple email servers 102 to multiple wireless communication devices 104. The system 100 also includes a prior art private network 142 described in the background of the invention. An e-mail server 102 is connected to a public network 106 such as the Internet. A plurality of computers 108 are connected to a public network 106 for connecting to and accessing one of the electronic mail servers 102. The end user of each computer 108 has an email account on one email server 102 that stores and manages email for each computer.

  Each computer device 108 and / or its email account is associated with one of the wireless communication devices 104 to which email information is pushed. Each wireless communication device 104 is portable and has a display and keyboard / keypad (eg, a small QWERTY keyboard) along with a wireless transceiver, antenna, and one or more processors that control the operation of the device. Includes housing. Each wireless communication device 104 has the ability to send and receive email information related to that email account managed by one of the email servers 102. Unlike any method that requires the wireless communication device 104 to make a connection for receiving email information, the email information is received by each device 104 through a real-time automatic “push” technique. Email accounts and information that are not associated with any wireless communication device are also managed and stored in the email server 102. Other services can also be provided for wireless communications such as telephone communications, internet access, and various other data services.

  For simplicity, FIG. 1 shows three computers 108, PC1, PC2,. . . Note that there are only computers 118, 120, 122 labeled PCn. Similarly, for the sake of simplicity, the figure shows three electronic mail servers 102, ie, electronic mail servers 1, 2,. . . There are only e-mail servers 112, 114, 116 labeled n. When put into practical use, many additional e-mail servers, computers and wireless communication devices can be used.

In the embodiment described above, the computer 108 is a desktop that can connect to the email server 102 via the Internet using any conventional method (eg, a telephone dialup modem, cable modem, or DSL modem). Or a computer such as a laptop computer. In addition to viewing, categorizing, organizing, and otherwise managing past received emails stored on the email server, personal computer end users can send and receive new emails Access to appropriate personal email accounts. When a calculator end user accesses an email, the user's calculator is used to send the email over the Internet using the appropriate uniform resource locator (URL) associated with the email provider or server. Connect to the server. The end user uses the calculator to send the user's personal username and password and log on to the email server. If the username and password match what is stored on the email server, the login is successful and an email session is created so that the end user can perform email tasks.

  Note that the calculator 108 and each email account are generally not affiliated with each other, i.e., not necessarily associated with the same commercial or private network. For example, computers 118 and 120 are not used by the same company and are not part of the same private network. In practice, the computer 118 can be used by a private person A, and the computer 120 can be used by a private person B. Therefore, the email account associated with the computer 118 can be considered as an unsubscribed email account.

  Each of the email servers 102 preferably has email software configured according to the Internet Message Access Protocol (IMAP) standard. IMAP is a recently developed e-mail protocol that seeks to solve some of the problems associated with the previous e-mail receiving protocol (POP). For IMAP, all e-mails are stored in an e-mail server and messages are viewed in response to client requests. Split folders can be created on the email server to organize various email messages. Conveniently, email messages in the end user's inbox and other mail folders can be accessed from a number of different physical devices or machines running the IMAP client program. One of the standard specifications for IMAP is Request For Comment (RFC) 2060, but other related specifications, additional documents and / or revisions are also applicable.

  Via a plurality of e-mail management clients 164 and a repeater 160 connected to a plurality of radio communication networks 110, it becomes easy to push an e-mail from the e-mail server 102 to the radio communication device 110. The wireless network 110 may be a mobile phone communication network, for example. For simplicity, the figure shows three wireless communication networks 110, ie, wireless networks 1, 2,. . . Only wireless networks 130, 132, and 134 labeled n are shown. Similarly, for simplicity, the figure shows three e-mail management clients 164, i.e. e-mail management clients 1, 2,. . . Only e-mail management clients 166, 168, and 170 displayed as n are shown. When put to practical use, many additional email management clients and wireless networks can be used.

Referring now to FIG. 2, a simplified relevant portion of the system of FIG. 1 is shown to further illustrate the details of the present invention. Starting with additional devices including computers 202, 204, 206 and wireless communication devices 208, 210, e-mail servers 112, 114, e-mail management client 166, repeater 160, wireless network 130, computers 118, 120 of FIG. , 122 and only wireless communication devices 124, 126, 128 are shown in FIG. While computers 204, 206 are shown as being associated and / or connected to email server 114, computers 118, 120, 122 are associated with and / or connected to email server 112. It is shown as
Computer 202 is shown as being connected to email server 112 by a dotted line, but is connected to either email server 112 or 114 or to a different email server, either a private or public network. can do. Email servers 112 and 114 are shown as being associated with and / or connected to email management client 166.

  FIG. 3 shows some general representative information for a plurality of unsubscribed email accounts 302 stored and managed by each email server 102 of FIGS. 1-2. For simplicity, FIG. 3 shows information about three sets of email accounts, namely, information about email account 304 in the name of “BARRY GILHULY”, “ANDY VAN”. Information about the email account 306 in the name and information about the email account 308 in the name “THOMAS PARRY” are shown. As illustrated, each account has a user name (USER NAME) and password associated with it for security purposes. The information includes the e-mail message itself, but they are organized into various other folders including “INBOX”, “FOLDER 1”, “Folder 2”.

  Each email account also has email rule settings (or filter settings) associated with the folder. Rule settings include conventional text based filter settings, including wireless communication device delivery settings. When a new email message is received, the email server uses text based filter settings to route the new email message to a specific folder, for example, based on specific text in a specific data field. Remember. Meanwhile, wireless communication device delivery settings are provided to specify whether and / or which email information should be delivered to the wireless communication device associated with the email account.

In this example in FIG. 3, the delivery setting displays whether or not the email information is delivered to the wireless communication device, and which part of the email information is delivered when the email information is delivered. . Email information can include email header information (data in the TO, CC, FROM, and SUBJECT fields), email delivery date and time, email message text, and file attachments. It is not limited. As specified as another suitable delivery setting, level 1 for delivering email information to the wireless communication device only when the sender designates the email message as a level 1 priority (LEVEL 1 PRIORITY)
Priority setting etc. can be specified. In the example of FIG. 3, the email account 304 of “Barry Gilhally” has a delivery setting (DELIVERY SETTING) “always delivery of email header information only (ALWAYS SEND ONLY E-MAIL HEAD).
ER INFORMATION ”and“ Andy Van ”email account 306 is set to“ NEVER SEND E-MAIL ”, and“ Thomas Parry ”email account 308 is delivered. The setting is “always send all e-mail text (ALWAYS SEND FULL E-MAIL TEXT)”.

  The distribution setting is changed by the end user of the computer (and / or wireless communication device) via an appropriate command or instruction when the computer (and / or wireless communication device) logs on to the e-mail server, for example. It is preferable that Thereby, the delivery setting can be changed by the user via the computer and / or the wireless communication device.

4A-4C are systems such as the system 100 described in relation to FIG.
A flowchart is formed describing a method of pushing email information from a plurality of email servers to a plurality of wireless communication devices. The description of the flowchart begins with FIG. 4A, which relates to an email notification setup method and will be described in connection with FIG. Beginning at start block 400 of FIG. 4A, an email management client logs on to an email server on behalf of a plurality of unsubscribed email accounts (step 402). For example, in FIG. 2, email management client 166 may contact email server 112 on behalf of a plurality of unsubscribed email accounts, including accounts associated with computers 118, 120, 122 (ie, account 302 in FIG. 3). You can log on.

  In this step, assuming that the email management client can send a username and password to log on to the email server and that the username and password match those stored in the email server, the login is Successful email session is created. For this email session, the email management client has (eg, limited or complete) access to all of the plurality of unsubscribed email accounts associated with the wireless communication device. The login session of the email management client can be similar or the same as that of an administrative login session by an administrator with access to multiple user accounts.

  After login, a connection is established between the email management client and the email server for sending email change notification information (step 404 in FIG. 4A). For example, according to FIG. 2, a TCP / IP connection 212 can be established between the email management client 166 and the email server 112. Thereafter, the email management client can request receipt of email change notifications for a plurality of unsubscribed email accounts having associated wireless communication devices (step 406 of FIG. 4A). The email server processes this request and a second connection is established between the email management client and the email server for sending email information (step 408 in FIG. 4A). For example, in FIG. 2, the email management client 166 can send an email change notification request to the email server 112, and in response, the email management client 166 and the email that sends email information. A TCP / IP connection 214 can be established with the server 112.

  Thereby, two TCP / IP connections 212 and 214 can be established between the email server 112 and the email management client 166. The email server 112 uses the TCP / IP connection 212 to continuously send email notification information to the email management client 166 in real time and uses the TCP / IP connection 214 to send the email management client At 166, specific email information is transmitted based on the request. Similarly, two TCP / IP connections 216 and 218 can be established between the email server 114 and the email management client 166, which uses the TCP / IP connection 216. Email notification information is continuously sent to the email management client 166 in real time, and specific email information is sent to the email management client 166 based on the request using the TCP / IP connection 218. . The e-mail notification setup is complete and the flowchart of FIG. 4A continues to FIG.

Referring now to FIG. 4B, email change notification information about any email change for any email account during one of the connections is sent from the email server by the email management client. Received in real time (step 412). For example, in FIG. 2, email change notification information for email changes is sent by the email server 112 and can be received by the email management client 166 during the TCP / IP connection 212. Each notification message from the email server preferably includes a server identifier (eg, server address) that identifies the particular email server and a unique notification / email change (eg, sequence number).

  Step 412 will be further described in connection with FIG. 2, using computer 202, an email message addressed to an end user of computer 118 associated with wireless communication device 124 (FIG. 2) (hereinafter “first email message”). And the email message is delivered to an appropriate email account managed by the email server 112. An email change notification flag for a new incoming message is set in the email server 112 for the email account, and immediately thereafter, the email management client 166 is informed of the message throughout the TCP / IP connection 212. Send email change notification information for. The notification information includes a server identifier for the email server 112 (eg, “server1.net”) and an email change notification identifier or sequence number (eg, “212”).

  More detailed information can also be included in each notification message, as outlined in Table 1 below.

  (Table 1. Types of data that can be included in e-mail change notification information)

Continuing with the flowchart of FIG. 4B, the email management client uses the received email change notification information to request email information from the email server throughout the second connection (step 414 of FIG. 4B). ). For example, in FIG. 2, the email management client 166 uses the server identifier (“server1.net”) and the notification identifier (“212”) as the destination address to send the email associated with the first email message. Information can be requested from the email server 112 to identify email notifications and desired email information. The email server 112 receives and processes these commands (an appropriate server that retrieves appropriate email information associated with the notification identifier) and sends email to the email management client 166 throughout the second connection. Pass information. In response, the email client receives this email information throughout the second TCP / IP connection (step 416 of FIG. 4B). For example, in FIG. 2, the email management client 166 can receive email information throughout the TCP / IP connection 214 associated with the first email message. The acquisition of email information in steps 414, 416 is accomplished by using conventional commands such as SELECT (eg, selecting a particular email folder) and FETCH (eg, fetching particular email data) as email server 112. Can be executed by the e-mail management client 166.

  Once this information is received by the email management client, at least a portion of the information is assembled into a message and pushed in real time to the appropriate wireless communication device (step 416 in FIG. 4B). For example, in FIG. 2, the email information of the first email message is pushed to the wireless communication device 124 by the email management client 166. The e-mail information is conveyed via the repeater 160 to an appropriate wireless network 130 in which the communication device is arranged. The flowchart ends at step 418, but the method is repeated continuously, beginning with step 412.

  Note that the steps described in connection with FIG. 4B are performed not only for a single email server, but also for multiple different email servers, each managing multiple unsubscribed email accounts. I want to be. For the sake of illustration, the computer 202 of FIG. 2 also creates and sends a draft of an email message (hereinafter “second email message”) for the end user of the computer 120 having the wireless communication device 126. Can be used for. In addition, the computer 202 of FIG. 2 also creates and sends a draft of an email message (hereinafter “third email message”) for the end user of the computer 204 associated with the wireless communication device 208. Can be used for These second and third email messages are delivered to appropriate email accounts managed by email server 112 and email server 114, respectively. Thus, the email change notification flags of these newly received messages are set in the email servers 112 and 114 for each email account.

  As described above, with respect to step 412 of FIG. 4B, email change notification information associated with the first email message has just been sent and received by email management client 166 during TCP / IP connection 212. Instead, notification information associated with the second email message is also sent and received by the email management client 166 during the TCP / IP connection 212. The received notification information of the second e-mail includes a server identifier (for example, “server1.net”) of the e-mail server 112 and an e-mail change notification identifier or sequence number (for example, “245”). Further, email change notification information associated with the third email message is sent to the email management client 166 throughout the TCP / IP connection 216. The received notification information of the third e-mail message includes a server identifier (eg, “server2.net”) of the e-mail server 114 and an e-mail change notification identifier or sequence number (eg, “099”).

Also, with respect to step 414 of FIG. 4B, the email management client 166 not only requests the email server 112 for its email information associated with the first email message, but also a server identifier (“ server1.net ”) and the notification identifier (“ 245 ”) are used to request that email information associated with the second email message and identify the email notification and information. Furthermore, the email management client 166 uses the server identifier (“server2.net”) and the notification identifier (“099”) as the destination address to the email server 114 to relate to the third email message. Request the email information and identify the email notification and information. With reference to step 416 of FIG. 4B, the email management client 166 receives email information for the second email message as well as the first email message throughout the TCP / IP connection 214. Thus, for the third email message as well, the email management client 166 receives email information throughout the TCP / IP connection 218. With reference to step 418 of FIG. 4B, not only is the email information of the first email message assembled and pushed to the wireless communication device 124, but also the email information of the second email message is pushed to the wireless communication device 126. The email information of the third email message is also pushed to the wireless communication device 208.

  Although the above method has been described with respect to receipt of a new email message, it can also be made for all changes to the end user's mailbox. For example, an email change can be the deletion of an existing message or the movement of an existing message from one mail folder to a different mail folder. The behavior due to the difference depends on the specific email that was changed. For example, the action due to the difference can be an update of an existing internal map, as opposed to a pushed email.

  In addition, the distribution of the e-mail information is preferably performed based on the wireless communication device wiring setting related to each e-mail account (for example, the distribution setting described with respect to the e-mail account in FIG. 3). This aspect is described in connection with the portion of the flowchart of FIG. 4C, which continues after the completion of the email notification setup of the flowchart of FIG. 4A. Referring now to FIG. 4C, email change notification information for email changes to any email account is continuously received from the email server by the email management client during one of the TCP / IP connections. Are received in real time (step 420 in FIG. 4C). Each notification message from the email server includes a server identifier (eg, a server address) that identifies a particular email server and a unique notification / email change email change identifier (eg, a sequence number).

  Next, during the second connection, the e-mail management client requests and receives the wireless distribution setting related to the e-mail account from the e-mail server (step 422 in FIG. 4G). In particular, the acquisition of delivery settings in step 422 is performed by sending conventional commands such as SELECT (eg, setting a specific email folder) and FETCH (eg, fetching delivery setting data) commands to the email server. It can be done by emitting. For example, the delivery setting can be one of those described with respect to the email account of FIG.

  The distribution setting indicates whether or not the electronic mail information should be distributed, and which part of the electronic mail information should be distributed if the electronic mail information is to be distributed. Email information can include email header information (data in the TO, CC, FROM, and SUBJECT fields), email delivery date and time, email message text, and file attachments. It is not limited. Designated as other suitable delivery settings, such as level 1 priority settings that deliver email information to wireless communication devices only when delivered email messages are designated as level 1 priorities can do. In the example of FIG. 3, the email account 304 of “Barry Gilharie” has a delivery setting “always deliver only email header information”, and the email account 306 of “Andy Van” has a delivery setting of “electronic The e-mail account 308 of “Thomas Parry” has a distribution setting “always send all e-mail text”. Delivery settings can be changed by the end user of the computer (and / or wireless communication device) via an appropriate command or instruction, for example, when the computer (and / or wireless communication device) properly logs on to the email server. Preferably it can be done. Thereby, the delivery setting can be changed by the user via the computer and / or the wireless communication device.

  Returning to FIG. 4C, the e-mail management client pushes e-mail information to the wireless communication device and / or pushes which e-mail information based on the searched distribution setting. (Step 424 in FIG. 4C). If the e-mail management client determines not to push the e-mail information in response to this notification (for example, a setting for displaying “e-mail transmission not possible”), e-mail information is not requested. On the other hand, the e-mail management client can make a decision to push e-mail information in response to this notification (for example, a setting for displaying “send e-mail”). In this case, the email management client uses the received email change notification information to request and receive email information from an appropriate email server (step 426 in FIG. 4C).

  Describing in more detail about step 426, the email management client requests the appropriate email server for email information associated with the email message with the use of the server identifier and notification identifier as the destination address, and the appropriate email server. Identify email notifications and information. The email server searches the appropriate server for the appropriate email associated with the notification identifier, receives and processes this message, and then emails the email information throughout the second TCP / IP connection. Send to management client. In response, the email management client receives this email information throughout the second TCP / IP connection. In particular, this e-mail information acquisition involves issuing conventional commands to the e-mail server, such as SELECT (eg, select a specific e-mail folder) and FETCH (eg, e-mail data capture) commands. Is done. The email management client then assembles the appropriate information into a message and pushes the message to the wireless device (step 428 in FIG. 4C). The information is pushed through an appropriate wireless network 130 in which the repeater 160 and the communication device are arranged.

  To elaborate on the example described above with respect to FIG. 4B, the email management client 166 of FIG. 2 identifies the server address (“server1.net”) of the email server 112 and a sequence that uniquely identifies the email notification. A first notification message is received for a first email message that includes the number “212”, which is associated with the email account 304 of FIG. Also, the distribution setting “send only e-mail header information always” related to the computer 118 is searched via the e-mail account 304. In this case, the e-mail management client 166 transmits a command for receiving e-mail information using “server1.net” as the destination address and “212” as the notification identifier. The email server 112 sends all or most of the relevant email information to the email management client 166 so that the email management client 166 extracts only a portion of the information (eg, email header). It is preferably configured to push to the wireless communication device. In an alternative embodiment, the email server 112 can be configured to send only a portion of the email information specified in the delivery settings, so that the email management client 166 simply sends the information to the message And configured to be pushed to the wireless device.

  Continuing with the example, the email management client 166 also provides a sequence number that uniquely identifies the server address (“server1.net”) of the email server 112 and the particular email notification of the email account 306 of FIG. A second notification message of the second e-mail message including “245” is received. Further, the distribution setting “e-mail transmission impossible” related to the computer 118 of the e-mail account 306 in FIG. 3 is searched. When the e-mail management client 166 receives this particular delivery setting, it does not issue any command to receive e-mail information with the notification identifier “245” and does not push any information related to this notification.

  Finally, the email management client 166 includes the server address (“server2.net”) of the email server 112 and a sequence number “099” that uniquely identifies the particular email notification of the email account 306 of FIG. A third notification message of the third e-mail message is received. Also, the distribution setting “always send complete email text” associated with the computer 118 of the email account 306 is searched. In this case, the email server 112 transmits email information to the email management client 166 that composes the information into a message that is pushed to the wireless communication device.

  For an email account, when the delivery setting “send only level 1 priority email” (see FIG. 3) is used and received by the email management client 166, the email management client 166 receives the notification identifier. Issue a command to receive the corresponding email information, receive the email information, and test whether the email message information displays level 1 priority. When the email message information indicates level 1 priority, the email management client 166 pushes the appropriate email information to the wireless communication device. When displaying email message information that does not reach Level 1 priority, the email management client 166 does not push any email information to the wireless communication device.

  The method for pushing e-mail information from an e-mail server to a plurality of wireless communication devices has been described above. In one exemplary method, the email server is publicly accessible and manages a plurality of unsubscribed email accounts, each associated with a plurality of wireless communication devices. The method is performed by an email management client and operates to establish and maintain a connection with an email server; receiving an email change notification for a plurality of unsubscribed email accounts during the connection; An operation of receiving e-mail information related to the mail change notification; and an operation of pushing at least a part of the e-mail information for reception by a plurality of wireless communication devices. The method utilizes the Internet Message Access Protocol (IMAP) standard and the connection is preferably a single TCP / IP connection. The method also includes receiving a user configurable delivery setting associated with the email notification; and whether to push email information based on the user configurable delivery setting and / or which email information An operation for determining whether or not to push can be included for convenience.

  Another exemplary method includes pushing email information from a plurality of email servers to a plurality of wireless communication devices. This method is performed by an email management client and, for each email server, logs on to the email server on behalf of multiple unsubscribed email accounts and establishes and maintains a connection with the email server. An operation; receiving, during connection, receiving each email change notification for a plurality of unsubscribed email accounts, including an email server identifier and an email notification identifier; and email information associated with the email change notification And an operation of pushing at least a part of e-mail information for reception by a plurality of wireless communication devices substantially in real time. This method uses the IMAP standard and the connection is preferably a single TCP / IP connection. The method may additionally include receiving a user configurable delivery setting associated with the email notification; and whether to push email information based on the user configurable delivery setting and / or which electronic An operation for determining whether mail information should be delivered can be included for convenience.

It should be understood that the foregoing is merely an example of the present embodiment, and that various changes, modifications and variations can be made without departing from the spirit and scope of the present invention as defined in the appended claims. For example, the method can be used to make essential changes to an end user's mailbox, e-mail changes can be deleted from an existing message or from a mail folder with an existing message to a different mail folder. Can be a move. None of the terms and phrases in this specification and claims give those skilled in the art a specific specific meaning that is different from plain language, so the specification defines terms in an overly narrow sense. Must not be used to

FIG. 1 is a diagram of a system in which email information is pushed from a plurality of email servers to a plurality of wireless communication devices. FIG. 1 is a diagram of a system in which email information is pushed from a plurality of email servers to a plurality of wireless communication devices. FIG. 2 is a diagram of portions associated with the system of FIG. 1 for illustrating details relating to the present invention. FIG. 3 is a diagram of typical representative information related to some of a plurality of unsubscribed email accounts managed by each email server. 4A-4C form a flowchart describing a method for pushing email information from a plurality of email servers to a plurality of wireless communication devices. 4A-4C form a flowchart describing a method for pushing email information from a plurality of email servers to a plurality of wireless communication devices. 4A-4C form a flowchart describing a method for pushing email information from a plurality of email servers to a plurality of wireless communication devices.

Claims (1)

A method for pushing e-mail information from an e-mail server to a plurality of wireless communication devices, wherein the e-mail server is publicly accessible and a plurality of unsubscribed e-mails respectively associated with the plurality of wireless communication devices Managing accounts, the method is executed by an email management client,
Establishing and maintaining a connection with the email server;
Receiving an email change notification of the plurality of unsubscribed email accounts via the connection;
Receiving email information associated with the email change notification;
Pushing at least a portion of the email information for receipt by the plurality of wireless communication devices.

Images