KR20050084804A - Method and apparatus for pushing e-mail to wireless communication devices - Google Patents

Abstract

Each e-mail server is publicly accessible and manages a plurality of unaffiliated e-mail accounts respectively associated with the plurality of wireless communication devices. An e-mail managing client logs on to an e-mail server behalf of the plurality of unaffiliated e-mail accounts and a TCP/IP connection is established and maintained with it. Thereafter, e-mail change notification information for all of the e-mail accounts are received continually over the single TCP/IP connection. Based on the e-mail change notification information, e-mail information may be retrieved and pushed for "real time" receipt by the plurality of wireless communication devices. An e-mail server identifier and an e-mail notification identifier are provided with the e-mail change notification information so that requests to receive particular e-mail information may be properly facilitated. User-configurable delivery settings are also provided so that e-mail information may be pushed (if at all) as specified by the end- user.

Description

METHOD AND APPARATUS FOR PUSHING E-MAIL TO WIRELESS COMMUNICATION DEVICES}

FIELD OF THE INVENTION The present invention relates to a system for "pushing" email information to a plurality of wireless communication devices, and more particularly, to log on to a plurality of email servers on behalf of a plurality of unffiliated email accounts, each of which can be used to log on each other. Email configured to establish and maintain a single session connection with an email server to receive email change notification information for multiple unrelated email accounts so that email information can be managed, retrieved, and pushed to multiple wireless communication devices in near real time It is about an administrative client.

1A and 1B show a system 100 for pushing email information from an email server 152 to a plurality of wireless communication devices 104 in a conventional manner. Private network 142, which may be a private local area network (LAN), includes a plurality of computers 144, an enterprise server 154, and a firewall 156 as well as an email server 152. The end user of each computer 144 in the private network 142 has an email account managed by an email server 152 operating according to well-known Post Office Protocol (POP) standards. As such, a plurality of computers 144 may conventionally be used to access email server 152 and access private email messages from email server 152. As should be clear, all computers 144 operate within the same private network 142 operated and / or managed by the same single entity (eg, the same company), in which they are related. 1A and 1B show only three computers 144 for convenience, computers 146, 148 and 150, respectively classified into PC1, PC2, ..., and PCn.

Each computer 144 and / or email account corresponding thereto is associated with one wireless communication device 104 each. Each wireless communication device 104 is portable and has a display and a keyboard / keypad (eg, a reduced QWERTY type keyboard) as well as a wireless transceiver, an antenna and one or more processors that control the operation of the wireless communication device. A handheld housing. Each wireless communication device 104 has the ability to send and receive email information associated with an email account managed by email server 152. Email information is received by each wireless communication device 104 via a real-time automatic " push " method, unlike how wireless communication device 104 must invoke a connection for the receipt of email information.

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 through a leased line 158 between enterprise server 154 and repeater 160. In addition, a single private connection 155 is established and maintained between enterprise server 154 and email server 152. For example, the private connection 155 may be a Messaging Application Programming Interface (MAPI) connection associated with Microsoft Exchange. When a new email account is set up in private network 142, enterprise server 154 is supplied with the server address of email server 152 (or other server) associated with that new email account.

When the email server 152 detects a change of an e-mail account (eg, receiving a new e-mail, moving a message from one folder to another folder, etc.), the e-mail server 152 connects to the reason for the e-mail change notification information (155). ) Is transmitted to the enterprise server 154 in real time. The email change notification information includes a notification identifier that uniquely identifies the email change. When the enterprise server 154 receives the notification information for a particular account, it sends a message to the stored server address of the email account and requests to receive the email information corresponding to the notification identifier. After receiving the email information, the enterprise server 154 pushes it to the appropriate wireless communication device through the wireless communication network with the relay 160 currently serving the wireless communication device. Although this conventional operation has been described as a single private network 142, the push of email information is performed to multiple private networks using the same repeater 160 at the same time. Such operation is more specific to pending US Application No. 09 / 401,868, "System and Method for Pusing Information from a Host System to a Mobile Data communication Device," filed on September 23, 1999 and currently assigned to the assignee of the present application. It is described as

The system described above operates efficiently and is suitable for the processing of related email accounts in a private network. However, Internet-based email is moving to support what is known as the Internet Message Access Protocol (IMAP) standard for email and message storage. IMAP is designed to replace the old POP method for mail access. The main advantage of IMAP is the ability to support multiple simultaneous access to one or more mailboxes from multiple clients. This allows more than one user or computer to access the same information without worrying about failure or damage to the information storage area.

In the case of a wireless handheld mobile device, it is an important feature to push information in real time to notify the mobile device that a mail has been received. However, conventional IMAP is not designed to facilitate push-based message service to multiple end users in an efficient and scalable manner. IMAP is designed similar to POP in that it focuses on a pull or connection-based solution that allows clients to connect when needed and read their email. Email notifications can be delivered automatically in real time using IMAP, but to do so, you must establish and maintain a single TCP / IP connection for each email account / mailbox. Because of this limitation, IMAP is not capable of enough scaling to support large numbers of mobile device users. The pool for new data and / or changes is an option, but this mechanism becomes useless as the number of users increases (eg, hundreds or hundreds of thousands). Once the number of physical IMAP servers is enough to support such pool and connection needs, the solution will no longer be manageable from any operations center.

Accordingly, what is needed is a scalable and efficient system for pushing email information from one or more email servers to a plurality of wireless communication devices.

1A and 1B are diagrams illustrating a system for pushing email information from a plurality of email servers to a plurality of wireless communication devices.

FIG. 2 is a diagram illustrating relevant parts of the system of FIGS. 1A and 1B for a detailed description of the invention.

3 is a diagram illustrating general representative information associated with a portion of a plurality of unrelated email accounts managed by each email server.

4A-4C are flowcharts illustrating a method of pushing email information from a plurality of email servers to a plurality of wireless communication devices.

Described herein is a system for "pushing" email information from a plurality of email servers to a plurality of wireless communication devices. Each email server is publicly accessible and manages a plurality of unrelated email accounts, each associated with a plurality of wireless communication devices. The email management client logs on to the email server on behalf of the plurality of unrelated email accounts to establish and maintain a TCP / IP connection with the email server. Thereafter, over a single TCP / IP connection, it continues to receive email change notification information for multiple unrelated email accounts. The email management client may retrieve the email information and push it to the plurality of wireless communication devices based on the email change notification information.

Each email change message also includes an email server identifier and an email notification identifier to facilitate accurate and easy request for receiving specific email information. In addition, it preferably provides a user-configurable delivery preference for pushing the end user specified email information.

As such, it is desirable to provide a scalable and efficient system for pushing email information from one or more email servers to a plurality of wireless communication devices.

1A and 1B illustrate a novel system 100 for pushing email information from a plurality of email servers 102 to a plurality of wireless communication devices 104. System 100 also includes a prior art private network 142 as described in the background of the present invention. Email server 102 is connected to a public network 106 such as the Internet. A plurality of computing devices 108 are also connected to the public network 106 to access and access either email server 102. The end user of each computing device 108 has an email account for either email server 102 that stores and manages email for each computing device.

Each computing device 108 and / or email account corresponding thereto is associated with one wireless communication device 104 each to which email information is pushed. Each wireless communication device 104 is portable and has a display and a keyboard / keypad (eg, a reduced QWERTY type keyboard) as well as a wireless transceiver, an antenna and one or more processors that control the operation of the wireless communication device. A handheld housing. Each wireless communication device 104 has the ability to send and receive email information associated with an email account managed by either email server 102. Email information is received by each wireless communication device 104 via a real-time automatic " push " method, unlike how wireless communication device 104 must invoke a connection for the receipt of email information. Other email accounts and information that are not associated with any wireless communication device are stored and managed in email server 102. Other services may also be provided to the wireless communication device, such as telephony, Internet access, and various other data services.

Note that in FIG. 1A and FIG. 1B only three computing devices 108, namely, computing devices 118, 120, and 122, respectively classified as PC1, PC2,..., To PCn, are shown for convenience. Likewise, only three email servers 102, i. E. Email servers 112, 114, and 116, respectively, are shown for convenience in FIG. 1A and FIG. 1B, respectively. Many additional email servers, computing devices, and wireless communication devices are available in practice.

In the described embodiment, computing device 108 is a computer or laptop PC, such as a laptop or laptop PC, capable of connecting to email server 102 via the Internet using any conventional means (eg, telephone dial-up, cable or DSL modem). Computer. The end user of the PC can access his appropriate personal email account to send and receive new email, as well as review, categorize, organize, and otherwise manage previously received email stored on the email server. When the end user of the computing device accesses the email, the end user's computing device is used to connect to the email server via the Internet using the appropriate uniform resource locator (URL) associated with the email provider or server. The end user uses the computing device to send his / her personal username and password to log on to the email server. If this username and password information matches what is stored on the email server, the login is successful and an email session is created so that the end user can perform the email operation.

Note that generally the computing device 108 and its respective email accounts are not related to each other, ie they are not necessarily related to the same corporate or private network. For example, computing device 118 and computing device 120 are not used in the same company or part of the same private network, and in fact, computing device 118 may be used by one person A and computing device 120 may be used by one person B. Therefore, an email account associated with computing device 108 may be referred to as an unrelated email account.

Preferably, each email server 102 has email software configured according to the Internet Message Access Protocol (IMAP) standard. IMAP is a recently developed email protocol designed to solve some of the problems associated with the old Post Office Protocol (POP). In the case of IMAP, all emails are stored on an email server, and specific messages are retrieved when requested by the client. In addition, separate folders for organizing various e-mail messages can be created in the e-mail server. Preferably, email messages and other mail folders in the end user's inbox can be accessed by some different physical device or machine running an IMAP client program. One standard specification for IMAP is Request For Comments (RFC) 2060, and other related standards, additions, and / or amendments are applicable.

Push of email information from email server 102 to wireless communication device 110 is facilitated by a plurality of email management clients 164 and a repeater 160 connected to a plurality of wireless communication networks 110. The wireless communication network 110 may be, for example, a cellular communication network. 1A and 1B show only three wireless communication networks 110, i.e., wireless networks 130, 132, and 134, respectively classified as wireless networks 1, 2, ..., to n for convenience. Similarly, only three email management clients 164, e.g., email management clients 166, 168, and 170, respectively classified as email management clients 1, 2, ..., to n are shown in FIGS. 1A and 1B for convenience. In practice many additional email management clients and wireless networks are available.

Referring now to FIG. 2, FIG. 2 shows a brief, relevant part of the system of FIGS. 1A and 1B for a more detailed description of the invention. 2 includes additional devices, including computing devices 202, 204, 206 and wireless communication devices 208, 210, as well as email servers 112, 114, email management clients (shown in FIGS. 1A and 1B). 166, repeater 160, wireless communication network 130, computing devices 118, 120, 122, and wireless communication devices 124, 126, 128 are shown. Computing devices 118, 120, 122 are shown associated with and / or connected to email server 112, and computing devices 204, 206 are shown associated with and / or connected with email server 114. . Although computing device 202 is shown in broken lines as being connected to email server 112, it may be connected to email server 112 or 114 or another email server in a private or public network. Email servers 112 and 114 are shown as being associated with and / or connected to email management client 166.

3 illustrates general representative information of a portion of a plurality of unrelated email accounts 302 stored and managed by respective email servers 102 of FIGS. 1A and 1B and 2. In FIG. 3, for convenience, only three sets of email account information, namely, information about an email account 304 named "Barry Gilhuly", information about an email account 306 named "Andy Van" and "Thomas Parry" Only information regarding the email account 308 of the name is shown. As shown, each email account has an associated username and password for security. The information also includes its own email messages organized in folders such as "Inbox", "Folder 1", and various others including "Folder 2".

Each email account also has an associated email rule preference (or filter preference). Email rule preferences include conventional text-based filter preferences as well as delivery preferences for wireless communication devices. Text-based filter preferences are used to route and store new email messages to a specified folder based on the specified text in a specified data field when the email server receives a new email message. On the other hand, the delivery preference of the wireless communication device is used to specify whether email information should be delivered to the wireless communication device associated with the email account and / or what email information should be delivered to the wireless communication device associated with the email account. .

In the example of FIG. 3, the delivery environment setting of the wireless communication device indicates whether or not the email information should be delivered to the wireless communication device, and what part of the email information should be delivered when the email information should be delivered. . Email information includes, but is not limited to, email header information (data in the TO, CC, FROM, and SUBJECT fields), email delivery date, email message text, and file attachments. It is also possible to specify delivery preferences for other suitable wireless communication devices, such as a level 1 priority preference that forwards email information to a wireless communication device only if the forwarded email message is assigned a priority of level 1 by the sender. Do. In the example of FIG. 3, an email account 304 named "Barry Gilhuly" has a delivery preference of "always send email header information only", and an email account 306 named "Andy Van" is "email "Prohibit forwarding" has a delivery preference, and an email account 308 named "Thomas Parry" has a delivery preference of "always send full email text".

Preferably, for example, if a computing device (and / or wireless communication device) is logged on to an email server, the end user of the computing device (and / or wireless communication device) may change the delivery preferences via appropriate commands. As such, a user may reconfigure delivery preferences through a computing device and / or a wireless communication device.

4A-4C are flow diagrams illustrating a method of pushing email information from a plurality of email servers to a plurality of wireless communication devices in a system such as the system 100 described with reference to FIGS. 1A and 1B-3. The flowchart begins with FIG. 4A, which relates to an email notification setup method, which is described with FIG. 2. Beginning at start block 400 of FIG. 4A, the email management client logs on to the email server on behalf of the plurality of unrelated email accounts (step 402). For example, in FIG. 2, the email management client 166 replaces an email server (instead of a plurality of unrelated email accounts including an account associated with the wireless communication devices 118, 120, and 122 (ie, the account 302 of FIG. 3). 112).

At this stage, the email management client sends the username and password to log on to the email server, and assuming that the username and password information matches that stored on the email server, the login is successful and the email session is established. Is generated. During this email session, the email management client has access rights (eg, limited or all) to all of the plurality of unrelated email accounts associated with the wireless communication device. The login session of the email management client may be similar or identical to an administrative login session by an administrator having access to a plurality of user accounts.

After login, a connection is established between the email management client and the email server to send email change notification information (step 404 of FIG. 4A). For example, in FIG. 2, a TCP / IP connection 212 can be established between email management client 166 and email server 112. The email management client then requests to receive an email change notification for the plurality of unrelated email accounts having the associated wireless communication device (step 406 of FIG. 4A). The email server then processes this request and establishes a second connection for sending email information between the email management client and the email server (step 408 of FIG. 4A). For example, in FIG. 2, when the email management client 166 sends an email change notification reception request to the email server 112, in response, the email management client 166 and the email server 112 transmit the email information. TCP / IP connection 214 can be established.

As such, two TCP / IP connections 212 and 214 may be established between the email management client 166 and the email server 112. Email server 112 continues to send email change notification information to email management client 166 in real time using TCP / IP connection 212 and specific email information on request using TCP / IP connection 214. To the email management client 166. Similarly, two TCP / IP connections 216 and 218 can also be established between email management client 166 and email server 114. Email server 114 continues to send email change notification information to email management client 166 in real time using TCP / IP connection 216, and specific email information on request using TCP / IP connection 218. To the email management client 166. Once the e-mail notification setup is complete, the flow chart of FIG. 4A continues through access point 410 to FIG. 4B.

Referring now to FIG. 4B, an email management client receives in real time email change notification information for email changes on an email account via any connection from an email server (step 412). For example, in FIG. 2, email server 112 may send email change notification information about an email change, and email management client 166 may receive that information via TCP / IP connection 212. Preferably, each notification message sent from an email server includes a server identifier (eg, server address) identifying a particular email server and an email change notification identifier (eg, sequence number) for unique notification / email changes. .

2, further described with reference to FIG. 2, an email message (hereinafter referred to as " first ") where the end user of computing device 118 associated with wireless communication device 124 (FIG. 2) using computing device 202 is the destination. And send it to a suitable email account managed by email server 112. The email change change notification flag for the newly received message is set in the email account in the email server 112, and the email change notification information for the message is then sent via the TCP / IP connection 212 to the email management client 166. Is sent to. The email change notification information includes a server identifier (eg, "server1.net") for the email server 112, and an email change notification identifier or sequence number (eg, "212").

As outlined in Table 1 below, more detailed information may be included in each notification message.

Data type Example data Sequence number 234 Server name mds99.blackberry.net Timestamp format of time_t 969929449 Folder name user.sitename-username User ID Username Message ID 5 Folder ID 959529449

Table 1. Data types that can be included in email change notification information

Returning back to the flowchart of FIG. 4B, the email management client requests email information from the email server via the second connection using the received email change notification information (step 414 of FIG. 4B). For example, in FIG. 2, the email management client 166 identifies the email notification and desired email information by using the server identifier "server1.net" and the notification identifier "212" which are the destination addresses, and thus the email server 112. Request e-mail information related to the first e-mail message. The email server 112 receives and processes these commands (the appropriate server retrieves the appropriate email information associated with the notification identifier) and forwards the email information to the email management client 166 via the second connection. In response, the email management client receives email information via a second TCP / IP connection (step 416 of FIG. 4B). For example, in FIG. 2, email management client 166 may receive email information via a TCP / IP connection 214 associated with the first email message. The acquisition of the email information in steps 414 and 416 is such that the email management client 166 may send a conventional command such as a selection (e.g., selecting a specific email folder) command, a retrieval (e.g., fetching specific email data) command, etc. By issuing to 112.

After this information is received by the email management client, at least a portion of this information is assembled into a message and pushed to the appropriate wireless communication device in real time (step 418 of FIG. 4). For example, in FIG. 2, 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 transmitted through the repeater 160 to the appropriate wireless communication network 130 where the wireless communication device is located. The flow chart ends at step 418 but resumes at step 412 and continues.

Note that the steps described with FIG. 4B can be performed simultaneously in a single email server environment as well as in a plurality of different email server environments where each manages a plurality of unrelated email accounts. As shown, also using the computing device 202 of FIG. 2, an end user of the computing device 120 associated with the wireless communication device 126 may be an email message (hereinafter referred to as a “second email message”) as the destination. Can be drafted and sent. In addition, the computing device 202 can be used by an end user of the computing device 204 associated with the wireless communication device 208 to draft an email message (hereinafter referred to as a “third email message”) as a destination. These second and third email messages are delivered to appropriate email accounts managed by email server 112 and email server 114, respectively. As such, an email change change notification flag for the newly received message is set for each email account in email server 112, 114, respectively.

As such, in step 412 of FIG. 4B, the email change notification information associated with the first email message is transmitted to and received from the email management client 166 via the TCP / IP connection 212 as well as associated with the second email message. Email change notification information is also sent to and received from email management client 166 via TCP / IP connection 212. The received email change notification information for this second email message includes a server identifier (eg, "server1.net") for the email server 112 and an email change notification identifier or sequence number (eg, "245"). do. In addition, email change notification information associated with the third email message is also sent to the email management client 166 via the TCP / IP connection 216. The received email change notification information for this third email message includes a server identifier (eg, "server2.net") for the email server 114 and an email change notification identifier or sequence number (eg, "099"). do.

In addition, in step 414 of FIG. 4B, the email management client 166 designates the email notification and information by using the server identifier "server1.net" and the notification identifier "245" which are the destination addresses, thereby specifying the email server 112. ) As well as email information associated with the first email message, as well as email information associated with the second email message. In addition, the email management client 166 may designate a third email message from the email server 114 by specifying email notification and information using a server identifier ("server2.net") and a notification identifier ("099") which are destination addresses. Request email information related to In 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 via the TCP / IP connection 214. The email management client 166 also receives email information for the third email message via the TCP / IP connection 218. In step 418 of FIG. 4B, not only the email information of the first email message is 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 and the third email. Email information in the message is also pushed to the wireless communication device 208.

Although the method has been described in connection with the receipt of a new e-mail message, it may be performed in nature in connection with the modification of the mailbox of the end user. For example, an email change may be that an existing message is deleted or an existing message is moved from one mail folder to another. The action accordingly depends on the specific email change made, for example the action may be to update an existing internal map as opposed to pushing an email message.

Preferably, the delivery of email information is performed based on a delivery preference of the wireless communication device associated with each email account (eg, delivery preferences described with respect to the email account of FIG. 3). This will be explained with the flowchart portion of FIG. 4C continuing after completion of the email notification setup from the flowchart of FIG. 4A. Referring now to FIG. 4C, an email management client continues to receive email change notification information in real time about an email change on either email account from any email server via a TCP / IP connection (step 420 of FIG. 4C). . Each notification message sent from an email server includes a server identifier (eg, server address) that identifies a particular email server and an email change notification identifier (eg, sequence number) for unique notification / email changes.

The email management client then requests and receives the delivery preferences of the wireless communication device associated with the email account from the email server via a second connection (step 422 of FIG. 4C). In particular, the acquisition of delivery preferences in step 422 may be performed by issuing conventional commands to the email server, such as a selection (e.g., selecting a particular email folder) command, a retrieval (e.g., fetching delivery preference data), and the like. have. For example, the delivery preference may be one of those described with respect to the email account in FIG.

The delivery preferences indicate whether email information should be delivered to the wireless communication device, and if email information should be delivered, what part of the email information should be delivered. Email information includes, but is not limited to, email header information (data in the TO, CC, FROM, and SUBJECT fields), email delivery date, email message text, and file attachments. Other suitable delivery preferences may also be specified, such as a level 1 priority preference that delivers email information to the wireless communication device only if the forwarded email message is assigned a priority of level 1. In the example of FIG. 3, an email account 304 named "Barry Gilhuly" has a delivery preference of "always send email header information only", and an email account 306 named "Andy Van" is "email "Prohibit forwarding" has a delivery preference, and an email account 308 named "Thomas Parry" has a delivery preference of "always send full email text". Preferably, for example, if the computing device (and / or wireless communication device) is properly logged on to the email server, the end user of the computing device (and / or wireless communication device) may change the delivery preferences via appropriate commands. As such, a user may reconfigure delivery preferences through a computing device and / or a wireless communication device.

Returning to FIG. 4C, the email management client determines whether email information should be delivered to the wireless communication device and / or which email information should be delivered to the wireless communication device based on the retrieved delivery preferences (step of FIG. 4C). 424). If the email management client determines that there is no email information to push for this notification (e.g., an environment setting indicating "email transmission prohibited"), no email information is requested. On the other hand, an email management client may determine that there is email information to push for this notification (e.g., preference setting indicating "email transmission"). In this case, the email management client requests and receives email information from an appropriate email server using the received email change notification information (step 426 of FIG. 4C).

More specifically, at step 426, the email management client requests email information related to the email message from the appropriate email server by specifying the appropriate email notification and information using the server identifier and the notification identifier as the destination address. The email server receives and processes this message, retrieves the appropriate email information associated with the notification identifier from the appropriate server, and forwards the email information to the email management client via a second TCP / IP connection. In response, the email management client receives email information via a second TCP / IP connection. In particular, the acquisition of such email information may be performed by issuing conventional commands to the email server, such as a selection (e.g., selecting a particular email folder) command, a retrieval (e.g., fetching specific email data), and the like. The email management client then assembles the appropriate information into a message and pushes this message to the wireless communication device (step 428 of FIG. 4C). The information is pushed through the repeater 160 and the appropriate wireless communication network 130 where the wireless communication device is located.

To further illustrate the example previously described with respect to FIG. 4B, the email management client 166 of FIG. 2 includes a server address (" server1.net ") for the email server 112, an email account 304 of FIG. Receive a first notification message associated with a first email message that includes a sequence number " 212 " uniquely identifying the associated email notification. In addition, a delivery preference of “always send only email header information” associated with computing device 118 is retrieved via email account 304. In this case, the e-mail management client 166 transmits an e-mail information receiving command using the destination address "server1.net" and the notification identifier "212". Preferably, email server 112 is configured to send all or most relevant email information to email management client 166 such that email management client 166 extracts only a portion of the information (eg, an email header) and pushes it to the wireless communication device. Is configured to transmit to. As another embodiment, the email server 112 may be configured to send only a portion of the email information specified in the delivery preferences such that the email management client 166 may properly configure the information into a message and push it to the wireless communication device. have.

Subsequently, the email management client 166 also displays a server address ("server1.net") for the email server 112 and a sequence number that uniquely identifies the specific email notification associated with the email account 306 of FIG. Receive a second notification message associated with a second email message, including " 245 " Also, via the email account 306 of FIG. 3, a delivery preference of " prohibit email information " associated with the computing device 118 is retrieved. When email management client 166 receives this particular delivery preference, email management client 166 does not issue any command to receive email information associated with the notification identifier "245" and does not issue any information related to this notification. Do not push too.

Finally, email management client 166 is assigned a server address ("server2.net") for email server 112 and a sequence number ("") that uniquely identifies a particular email notification associated with email account 306 of FIG. 099 ", to receive a third notification message associated with a third email message. In addition, a delivery preference of “always send full email text” associated with computing device 118 is retrieved via email account 306. In this case, the email server 112 sends the email information to the email management client 166, which organizes this information into a message and pushes it to the wireless communication device.

Once the delivery preference (see FIG. 3) is used in an email account and received by email management client 166, " send email of level 1 priority only ", email management client 166 sends email corresponding to the notification identifier. An information receiving command is issued to receive the email information, and to check whether the email message information indicates the priority of level 1. If the email message information indicates the priority of level 1, the email management client 166 pushes the appropriate email information to the wireless communication device. However, if email message information is lower than Level 1 priority, email management client 166 does not push any email information to the wireless communication device.

As described above, a method of pushing email information from an email server to a plurality of wireless communication devices has been described. As an example of such an email information pushing method, the email server is publicly accessible and manages a plurality of unrelated email accounts each associated with the plurality of wireless communication devices. The email information pushing method is performed by an email management client, the email information pushing method comprising: establishing and maintaining a connection with the email server; Receiving an email change notification for the plurality of unrelated email accounts via the connection; Receiving email information associated with the email change notification; Pushing at least a portion of the email information to be received by the plurality of wireless communication devices. Advantageously, said email information pushing method utilizes an Internet Message Access Protocol (IMAP) standard, wherein said connection is a single TCP / IP connection. The method for pushing email information also preferably includes receiving a user configurable delivery preference associated with the email notification; Determining whether the user should push email information and / or which email information should be pushed based on the configurable delivery preferences.

Another example of an email information pushing method is to push email information from a plurality of email servers to a plurality of wireless communication devices. The email information pushing method is performed by an email management client, and the email information pushing method is configured to log on to an email server on behalf of a plurality of unrelated email accounts to establish and maintain a connection with the email server for each of the email servers. Steps; Receiving an email change notification via the connection, the email change notification comprising an email server identifier and an email notification identifier for the plurality of unrelated email accounts; Receiving email information associated with the email change notification; Pushing at least a portion of the email information to be received by the plurality of wireless communication devices in near real time. Advantageously, said email information pushing method utilizes an Internet Message Access Protocol (IMAP) standard, wherein said connection is a single TCP / IP connection. The method for pushing email information also preferably includes receiving a user configurable delivery preference associated with the email notification; Determining whether the user should push email information and / or which email information should be pushed based on the configurable delivery preferences.

It is to be understood that the foregoing merely describes preferred embodiments of the present invention, and that various changes, modifications and variations can be made within the scope of the technical idea of the present invention as set forth in the appended claims. For example, the method may originally be used in connection with a change of a mailbox of an end user, and an email change may be to delete an existing message or to move an existing message from one mail folder to another. . The terms and phrases in this specification and claims do not give the person skilled in the art any particular specific meaning other than the general language meaning, and therefore the present specification should not be used to define the term in an unreasonably narrow sense.

Claims (30)

A method of pushing email information from an email server to a plurality of wireless communication devices using an email management client, wherein the email server is publicly accessible and manages a plurality of unrelated email accounts each associated with the plurality of wireless communication devices. In the email information push method, Establishing and maintaining a connection with the email server; Receiving an email change notification for the plurality of unrelated email accounts via the connection; Receiving email information associated with the email change notification; Pushing at least a portion of the email information to be received by the plurality of wireless communication devices Email information push method comprising a. The method of claim 1, wherein the email server comprises an Internet Message Access Protocol (IMAP) server. 2. The method of claim 1, wherein establishing and maintaining a connection comprises establishing and maintaining a TCP / IP connection. 2. The method of claim 1, further comprising logging on to the email server on behalf of the plurality of unrelated email accounts to establish the connection. The method of claim 1, wherein establishing and maintaining the connection comprises establishing and maintaining a first connection, wherein the email information pushing method comprises: Establishing and maintaining a second connection to receive the email information. The method of claim 1, wherein for each of the plurality of received email notifications, Receiving an email server identifier and an email notification identifier; Sending an email information receiving request corresponding to a specific email notification to the specific email server using the email server identifier and the email notification identifier. The method of claim 1, wherein for each of the plurality of received email notifications, Receiving an email notification identifier; Receiving delivery preferences configurable by a user; And pushing at least a portion of the email information for a particular wireless communication device to receive based on the user configurable delivery preferences. The email server of claim 1, wherein the email server comprises a first email server associated with a first plurality of unrelated email accounts having a first email change notification sent over a first connection and first email information associated therewith, The email information push method, Providing a second email server that is publicly accessible and manages a second plurality of unrelated email accounts, each associated with a second plurality of wireless communication devices; Establishing and maintaining a second connection with the second email server; Receiving a second email change notification for the second plurality of unrelated email accounts via the second connection; Receiving second email information associated with the second email change notification; And pushing at least a portion of the second email information to the second plurality of wireless communication devices. A computer program product for pushing email information from an email server to a plurality of wireless communication devices, wherein the email server is publicly accessible and manages a plurality of unrelated email accounts each associated with the plurality of wireless communication devices. In the program product, A storage medium; Computer instructions stored on the storage medium Including; The computer instructions executable by the processor are: Instructions for establishing and maintaining a connection with an email server; Instructions for receiving an email change notification for the plurality of unrelated email accounts via the connection; Instructions for receiving email information related to the email change notification; And causing the plurality of wireless communication devices to push at least a portion of the email information to be received. 10. The computer program product of claim 9, wherein the computer instructions further comprise instructions to establish and maintain a connection including a TCP / IP connection. 10. The computer program product of claim 9, wherein the computer instructions further comprise instructions to log into the publicly accessible email server on behalf of the plurality of unrelated email accounts to establish the connection. 10. The computer program product of claim 9, wherein the connection comprises a first connection, and the computer instructions further comprise instructions to establish and maintain a second connection for receiving the email information. 10. The computer program product of claim 9, wherein the computer instructions further comprise instructions for receiving an email server identifier and an email notification identifier corresponding to an email change notification; And use the email server identifier and the email notification identifier to send an email information receiving request corresponding to the email change notification to a specific email server. 10. The computer program product of claim 9, wherein the computer instructions further comprise instructions for receiving an email notification identifier corresponding to an email change notification and a user configurable delivery preference; And causing the user to push at least a portion of the email information for receiving by a particular wireless communication device based on a configurable delivery preference. A system for pushing email information to a plurality of wireless communication devices, A publicly accessible email server configured to manage a plurality of unrelated email accounts each associated with the plurality of wireless communication devices; Email management client Including; The email management client and the email server are configured to establish and maintain a connection with each other, The email server is configured to send email change notifications for the plurality of unrelated email accounts via the connection, the email management client is configured to receive the email change notifications, The email server is configured to send email information associated with the email change notification, the email management client is configured to receive the email information, And the email management client is configured to push at least a portion of the email information to be received by the plurality of wireless communication devices. The system of claim 15, wherein the publicly accessible email server comprises a first publicly accessible email server, wherein the email information push system comprises: A second publicly accessible email server configured to manage a plurality of unrelated email accounts, each associated with the plurality of wireless communication devices, The email management client and the second email server are configured to establish and maintain a connection with each other, The second email server is configured to send email change notifications for the plurality of unrelated email accounts via the connection, the email management client is configured to receive the email change notifications, The second email server is configured to send email information associated with the email change notification, the email management client is configured to receive the email information, And the email management client is configured to push at least a portion of the email information to be received by the plurality of wireless communication devices. 16. The system of claim 15, wherein said email server comprises an Internet Message Access Protocol (IMAP) server.  16. The system of claim 15, wherein the email management client and the email server are configured to establish and maintain a connection including a TCP / IP connection. 16. The system of claim 15, wherein the email management client is configured to log on to the email server on behalf of the plurality of unrelated email accounts to establish the connection. 16. The system of claim 15, wherein said connection comprises a first connection, and wherein said email server and said email management client are configured to establish and maintain a second connection for sending and receiving said email information. . The method of claim 15, wherein the email management client is configured to receive an email server identifier and an email notification identifier for each received email notification, And the email management client is configured to send an email information receiving command corresponding to a specific email notification to a specific email server using the email server identifier and the email notification identifier. 16. The method of claim 15, wherein the email server is configured to send an email notification identifier for each email notification, The email management client is configured to retrieve a user configurable delivery preference, And wherein the email management client is configured to push at least a portion of the email information for a particular wireless communication device to receive based on the user configurable delivery preferences. A method of pushing email information from a plurality of email servers to a plurality of wireless communication devices using an email management client, the method comprising: Per email server, Logging on to an email server on behalf of a plurality of unrelated email accounts to establish and maintain a connection with the email server; Receiving an email change notification via the connection, the email change notification comprising an email server identifier and an email notification identifier for the plurality of unrelated email accounts; Receiving email information associated with the email change notification; Pushing at least a portion of the email information to be received by the plurality of wireless communication devices in near real time Email information push method comprising a. 24. The method of claim 23, further comprising: receiving a user-configurable delivery preference associated with the email notification; Determining whether the user should push email information based on configurable delivery preferences and / or which email information should be pushed. 24. The method of claim 23, further comprising: receiving a user-configurable delivery preference associated with the email notification; Determining whether the user should push email information based on configurable delivery preferences and / or which email information should be pushed; Requesting email information from each email server based on the determining step. A system for pushing email information to a plurality of wireless communication devices, A plurality of email servers each configured to manage a plurality of unrelated email accounts respectively associated with the plurality of wireless communication devices; An email management client that logs on to each email server on behalf of the plurality of unrelated email accounts to establish and maintain a connection with the respective email server Including; Wherein each email server is configured to send email change notification information, including an email server identifier and an email notification identifier, for the plurality of unrelated email accounts via the connection, wherein the email management client is configured to send the email change notification. Receive information, Each email server is configured to send email information associated with the email change notification information, the email management client is configured to receive the email information, And wherein the email management client is configured to push at least a portion of the email information to be received by the plurality of wireless communication devices in near real time. 27. The system of claim 26, wherein the email management client is configured to receive a user configurable delivery preferences, The email management client is configured to determine whether the user should push email information based on configurable delivery preferences and / or which email information should be pushed. 27. The system of claim 26, wherein the email management client is configured to receive a user configurable delivery preferences, The email management client is configured to determine whether the user should push email information based on configurable delivery preferences and / or which email information should be pushed, And the email management client is configured to request email information from each email server when the user determines that the email information should be pushed based on a configurable delivery preference. A method of pushing email information from a plurality of Internet Message Access Protocol (IMAP) servers to a plurality of wireless communication devices, each IMAP server being publicly accessible and associated with a plurality of unrelated ones respectively associated with the plurality of wireless communication devices. In the email information push method for managing an email account, Per each IMAP server, Logging on to the IMAP server on behalf of the plurality of unrelated email accounts to establish and maintain a TCP / IP connection with the IMAP server; Receiving email change notification information over the TCP / IP connection, including email server identifiers and email notification identifiers for the plurality of unrelated email accounts; Retrieving email information from the IMAP using the email server identifier and the email notification identifier; Pushing at least a portion of the email information to be received by the plurality of wireless communication devices in near real time Email information push method comprising a. 30. The method of claim 29, wherein for each IMAP server: For each received email notification, receiving an email notification identifier and a user configurable delivery preference; And pushing the email information for a particular wireless communication device to receive based on the user configurable delivery preferences.