US 20090164586A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2009/0164586 A1 DOUGLAS et al. (43) Pub. Date: Jun. 25, 2009

(54) METHOD AND SYSTEM FOR MANAGING Publication Classi?cation THE RECEPTION OF MESSAGES IN A (51) Int Cl COMMUNICATION NETWORK G0 6F 15/16 (200601) (52) US. Cl...... 709/206 (75) Inventors: PAUL B. DOUGLAS, SHARDLOW DERBY (GB); (57) ABSTRACT ANDREW I‘ THOMPSON’ A method and system for managing the reception of messages SOUTHAMPTON (GB) in a communication network (100) includes a ?rst client node (102) polling (404) a server node (110) to check for the arrival Correspondence Address: of a ?rst message that is related to a ?rst message account at MOTOROLA INC the server node (110). The ?rst client node has a pull-message 600 NORTH Us HIGHWAY 45, W4 _ 39Q con?guration for the ?rst message account. The method also LIBERTYVILLE, IL 600485343 (Us) includes receiving (410) a push-message at the ?rst client node. The push-message noti?es the ?rst client node of the . _ arrival of a second message at the server node that is related to (73) Asslgnee' ’ S the ?rst message account. Further, the method includes ’ (U ) changing (502) the ?rst client node from a pull-message con?guration to a push-message con?guration, based on the (21) Appl. NO-I 11/962,374 push-message. Furthermore, the method includes the ?rst client node terminating (506) the polling of the server node (22) Filed; Dec. 21, 2007 for the ?rst message account.

r102 FIRST CLIENT NODE r202 MEMORY

[204 206 110 PROCESSOR r SERVER r

TRANSCEIVER 4 ' ' ' ' '> NODE

r210 MESSAGE r203 RETR'EVER CONFIGURATION MANAGER Patent Application Publication Jun. 25, 2009 Sheet 1 0f 5 US 2009/0164586 A1 r106

DGBDO m

102\||

w Patent Application Publication Jun. 25, 2009 Sheet 2 0f 5 US 2009/0164586 Al cck mm>mmw mEOz

wEk

N.UDN Patent Application Publication Jun. 25, 2009 Sheet 3 0f 5 US 2009/0164586 A1

r102 r110 FIRST CLIENT NODE:PULL- SERVER NODE: PULL-MESSAGE MESSAGE CONFIGURATION CONFIGURATION

302 POLL SERVER NODE FOR FIRST MESSAGE I (USER-UNREADABLE) SEND A RESPONSE NOTIFYING FIRST MESSAGE ‘ (USER-UNREADBALE) \304 RETRIEVE FIRST MESSAGE (USER-READABLE) ‘ \306’ K110 SERVER NODE CHANGED TO PUSH MESSAGE CONFIGURATION

PUSH-MESSAGE NOTIFYING SECOND MESSAGE ‘ (USER-UNREADABLE) \sos r309 FIRST CLIENT NODE CHANGED TO PUSH-MESSAGE CONFIGURATION

RETRIEVE SECOND MESSAGE (USER-READABLE) ‘ \31o ’ PUSH-MESSAGE NOTIFYING NEW MESSAGE 3? 4 RETRIEVE NEW MESSAGE (USER-READABLE) 1 I > 314

FIG. 3 Patent Application Publication Jun. 25, 2009 Sheet 4 0f 5 US 2009/0164586 A1

402

r404 POLL A SERVER NODE BY A FIRST CLIENT NODE TO CHECK FOR AN ARRIVAL OF A FIRST MESSAGE AT THE SERVER NODE ASSOCIATED WITH A FIRST MESSAGE ACCOUNT, THE FIRST MESSAGE ACCOUNT HAS A PULL-MESSAGE CONFIGURATION

IS THE FIRST MESSAGE ARRIVED AT THE SERVER NODE?

P’ES r408 RETRIEVE THE FIRST MESSAGE FROM THE SERVER NODE

NO IS A PUSH-MESSAGE RECEIVED?

YES

FIG. 4 Patent Application Publication Jun. 25, 2009 Sheet 5 0f 5 US 2009/0164586 A1

r502 CHANGE THE FIRST CLIENT NODE FROM A PULL-MESSAGE CONFIGURATION TO A PUSH-MESSAGE CONFIGURATION FOR THE FIRST MESSAGE ACCOUNT BASED ON THE PUSH-MESSAGE

RETRIEVE A SECOND MESSAGE FROM THE SERVER NODE WHEN THE PUSH-MESSAGE NOTIFIES THE ARRIVAL OF A SECOND MESSAGE ASSOCIATED WITH THE FIRST MESSAGE ACCOUNT AT THE SERVER NODE

TERMINATE THE POLLING OF THE SERVER NODE FOR THE FIRST MESSAGE ACIESZUEVT BY THE FIRST CLIENT

FIG. 5 US 2009/0164586 A1 Jun. 25, 2009

METHOD AND SYSTEM FOR MANAGING messaging technology for message reception and retrieval THE RECEPTION OF MESSAGES IN A may result in delayed retrieval of messages from the email COMMUNICATION NETWORK server node. [0006] In contrast to “pull” messaging technology, there exist methods based on “push” messaging technology for [0001] The present invention generally relates to the ?eld of receiving and retrieving messages from an email server node. communications, and more particularly, to a method and sys When a message account of an email client node is con?gured tem for managing the reception of messages in a communi as a push-message account, the email server node has the cation network. real-time capability to notify the email client node (or push) a neW message associated With the push-message account, as BACKGROUND soon as the neW message arrives at the email server node. In [0002] The deployment and use of handheld communica other Words, the email server node pushes the neW message to tion devices to exchange information in a communication the email client node Without Waiting to get polled by the email client node. netWork is Widespread and likely to continue to groW. Examples of the handheld communication devices include, [0007] The push messaging technology requires a dedi but are not limited to mobile phones, smart phones, Personal cated connection betWeen an email client node and an email Digital Assistants (PDAs), tWo-Way radios, laptop comput server node. This means that implementation of the push ers, and pagers. These handheld communication devices can messaging technology necessitates the use of dedicated and communicate in the communication netWork through elec speci?c hardWare con?gurations for the netWork and associ tronic mail (email) systems. Further, emails can be sent and/ ated communication devices. or received by using various email protocols, such as Post O?ice Protocol Version 3 (POP3), Simple Mail Transfer Pro BRIEF DESCRIPTION OF THE FIGURES tocol (SMTP), Internet Mail Access Protocol, Version 4 [0008] The accompanying ?gures, Where like reference (IMAP4), and Multipurpose Internet Mail Extensions numerals refer to identical or functionally similar elements (MIME). throughout the separate vieWs, and Which, together With the [0003] Typically, handheld communication devices can be detailed description beloW, are incorporated in and form part referred to as email client nodes. The email client nodes of the speci?cation, serve to further illustrate various embodi interact With an email server node for communication With ments, and explain various principles and advantages, all in other email client nodes in the email communication network. accordance With the present invention. Examples of email server nodes include, but are not limited to [0009] FIG. 1 illustrates an exemplary communication net an email server node With a Web interface and an email server Work in Which various embodiments of the present invention With a client interface. The email server node can store emails can be practiced; associated With the email accounts of the email client nodes. [0010] FIG. 2 is a block diagram illustrating various system Further, each of the email client nodes can receive and elements of a ?rst client node, in accordance With various retrieve emails associated With its email account from the embodiments of the present invention; email server node according to the con?guration of the email [0011] FIG. 3 is a sequence diagram illustrating a method account. for managing the reception of messages in a communication [0004] Many methods exist for receiving and retrieving netWork, in accordance With an embodiment of the present messages associated With the email accounts from the email invention; and server node. Some of these methods are based on “pull” [0012] FIGS. 4 and 5 illustrate a How diagram of a method messaging technology. If a message account of an email for managing the reception of messages in a communication client node is con?gured as a pull-message account, the email netWork, in accordance With another embodiment of the client node polls the email server node periodically to check present invention. for the arrival of a neW message associated With the pull [0013] Skilled artisans Will appreciate that elements in the message account of the email client node. When the neW ?gures have been illustrated for simplicity and clarity and message associated With the pull-message account arrives at have not necessarily been draWn to scale. For example, the the email server node, the neW message Waits at the email dimensions of some of the elements in the ?gures may be server node until the email client node polls the email server exaggerated, relative to the other elements, to help in improv node. Then the email client node can retrieve or doWnload the ing an understanding of the embodiments of the present neW message. invention. [0005] When using pull messaging technology, if no neW messages arrives at the email server node, periodic polling of DETAILED DESCRIPTION the email server node depletes a signi?cant amount of energy of the battery of the email client node Without producing any [0014] A method and system for managing the reception of bene?ts. Further, the periodic polling by the email client messages at a client node in a communication netWork alloWs nodes of the email server node results in an increase of net a client node to conveniently sWitch from a “pull” messaging Work traf?c. Also, polling involves ‘handshaking’ betWeen an technology to a more e?icient “push” messaging technology. email client node and an email server node. The handshaking The communication netWork includes one or more client is a process of establishing the communication rules betWeen nodes and a server node, Which stores messages associated the email client node and the email server node, prior to the With the one or more client nodes. The messages can be actual communication. When the email server node is busy, electronic mail messages (emails) or Instant Messages (IMs). there can be a delay in completing the handshake. As a result, The one or more client nodes can interact With the server node the email client node may have to Wait before receiving any to retrieve the messages. Each client node of the one or more neW messages. Hence, even if a neW message aWaits, pull client nodes has one or more message accounts associated US 2009/0164586 A1 Jun. 25, 2009

With it. A message account can be an email message account email message locally. Further, the ?rst client node 102 can or an instant message account. The one or more message retrieve the email mes sage from the server node 1 1 0. It Will be accounts can either have a pull-message con?guration or a apparent to a person ordinarily skilled in the art that the push-message con?guration. If the server node changes such communication netWork 1 00 can include more or feWer email that it goes from a pull-message con?guration to a push client nodes and server nodes than described in FIG. 1, in message con?guration, the disclosed method and system various implementations of the invention. sWitches the client node from a pull-message con?guration to [0017] For one embodiment, each client node has one or a push-message con?guration. more message accounts associated With it to facilitate com [0015] A ?rst client node of the one or more client nodes munication With other email client nodes. The message has at least a ?rst message account associated With it, and the accounts can be electronic mail (email) accounts or IM ?rst message account is con?gured as a pull-message con accounts. Examples of various message accounts include, but ?guration. Therefore, the ?rst message account has to poll the are not limited to, GoogleTM mail accounts, YahooTM mail server node to check for the arrival of one or more neW accounts, Microsoft Outlook, and HotmailTM accounts. Fur messages (such as emails) at the server node associated With ther, a message account can be identi?ed by a message the ?rst message account. When there are neW emails at the account Identi?er (ID) such as [email protected], server node, the polling results shoW the arrival of neW emails, [email protected] [email protected], etc. and the ?rst client node can retrieve and read the neW emails. Although, the present invention is applicable to both email Subsequently, the server node may be changed to handle a accounts and IM accounts, for the sake of clarity in descrip push-message con?guration. After receiving a push-message tion the embodiments have been described With reference to associated With the ?rst message account from the recon?g email accounts. ured server node, the ?rst client node changes the con?gura [0018] The server node 110 can store messages associated tion of the ?rst message account to a push-message con?gu With one or more email accounts of the email client nodes. For ration. The push-message from the server node noti?es the example, the server node 110, e. g. aYahooTM server, can store ?rst client node about the arrival of a neW message at the email message(s) for the YahooTM mail accounts of the email server node associated With the ?rst message account. When client nodes. It Will be apparent to a person ordinarily skilled the con?guration of the ?rst message account at the ?rst client in the art that although the server node 110 stores messages node is changed from a pull-message con?guration to a push for each of the email client nodes, and each of the email client message con?guration, the ?rst client node stops polling the nodes can retrieve email messages from the server node 110, server node. Thereafter, the ?rst client node having the push for the sake of clarity in description the invention has been message con?guration for the ?rst message account receives described With reference to the ?rst client node 102 and the a push-message from the server node Whenever a neW mes server node 110. sage associated With the ?rst message account arrives at the [0019] The ?rst client node 102 communicates With the server node. Thus, client nodes do not need to be recalled and server node 110 and other email client nodes via the commu reprogrammed if a pull server node is reprogrammed or nication netWork 100. The communication betWeen the email replaced to be a push server node. client nodes and the server node can be enabled by a commu [0016] FIG. 1 illustrates an exemplary communication net nication netWork service provider, e.g., an Internet Service Work 100, Where various embodiments of the present inven Provider (ISP), a netWork service provider, a netWork opera tion can be practiced. Examples of the communication net tor, and/or a proprietary netWork email service provider. The Work 100 include, but are not limited to, a Local Area user of the ?rst client node can use a communication netWork Network (LAN), a Wireless LAN, a Wide Area NetWork service provider, for example, the proprietary netWork email (WAN), a Wireless WAN (such as a cellular system), and a service provider, to create one or more email accounts. Fur Public SWitched Telephone NetWork (PSTN). Further, the ther, the ?rst client node 102 has message softWare installed communication netWork 100 includes one or more client on it. The message softWare, such as an email client, is a nodes such as a ?rst client node 102, a second client node 104, front-end softWare program that is used to manage the email a third client node 106, and a fourth client node 108. The messages of the message accounts of the ?rst client node 102. client nodes 102, 104, 106 and 108 are hereinafter collec Examples of the message softWare include, but are not limited tively referred to as client nodes. For one embodiment, these to, open-source MoZilla ThunderbirdTM, Microsoft Out client nodes can be devices that enable users to communicate lookTM, a Mail User Agent (MUA), and MuttTM. The message With each other in the communication netWork 100 via emails softWare enables a user of the ?rst client node 102 to com or Instant Messages (IM). All these client nodes are depicted pose, receive, send, and/or read email messages by using as Wireless devices. Examples of such client nodes include, various email message accounts. Further, the email client but are not limited to, mobile phones, smart phones, Personal supports various email protocols such as Post O?ice Protocol Digital Assistants (PDAs), tWo-Way radios, laptop comput Version 3 (POP3), Simple Mail Transfer Protocol (SMTP), ers, and pagers. The communication netWork 100 also Internet Mail Access Protocol, Version 4 (IMAP4), Multipur includes a server node 110. Examples of the server node 110 pose Internet Mail Extensions (MIME), etc. include, but are not limited to, an email server, a Web server, [0020] The ?rst client node 102 can have one or more email an Internet server, aYahooTM server, and a proxy server. When accounts associated With it, such as a ?rst message account, a the client nodes communicate via email, the client nodes can second message account, and a third message account, here be referred as email client nodes and the server node 110 can inafter collectively referred to as email accounts. For one be a netWork of individual email servers. The server node 110 embodiment, the email accounts of the ?rst client node 102 enables the exchange of data betWeen communicating email are associated With a single user of the ?rst client node 102. client nodes. For example, the server node 110 can receive an For another embodiment, the email accounts are associated email message from the second client node 104 addressed to With one or more users of the ?rst client node 102. Further, the an email account for the ?rst client node 102 and store the ?rst client node 102 can have different con?gurations for the US 2009/0164586 A1 Jun. 25, 2009

email accounts of the ?rst client node 102. For example, the not be able to deliver the push-message to the ?rst client node ?rst client node 102 can have a pull-message con?guration 102 directly. In this case, the server node 110 sends the for the ?rst message account and a push-message con?gura push-message meant for the ?rst message account to a net tion for the second message account. Work device. After receiving the push-message from the [0021] When the ?rst message account of the ?rst client server node 110, the netWork device can determine the node 102 is con?gured as the pull-message con?guration, the address of the ?rst client node 102 associated With the ?rst ?rst client node 102 polls the server node 110 periodically for message account. The netWork device can then deliver the the arrival of any neW message associated With the ?rst mes push-message to the transceiver 206 of the ?rst client node sage account. The neW message can be an email message 102. received from, for example, the second client node 104. [0027] The ?rst client node 102 also includes the message [0022] Various embodiments of the present invention retriever 210 that is con?gured to retrieve the neW email enable the ?rst client node 102 to change from a pull-message message, such as the ?rst message from the server node 110. con?guration to the push-message con?guration. The meth The ?rst message is received at the server node 110 When the ods for managing the reception of messages in accordance server node 110 is in pull-message con?guration. Further, the With pull and push message con?guration Will be explained in message retriever 210 can retrieve the second message after detail With reference to FIGS. 4 and 5. receiving the push-message. The second message is received [0023] FIG. 2 is a block diagram illustrating various system at the server node 110 When the server node 110 is in push elements of the ?rst client node 102 of FIG. 1, in accordance message con?guration. The message retriever 210 can be a With various embodiments of the present invention. The ?rst Mail Retrieval Agent (MRA) such as fetchmail, retchmail, or client node 102 can include a memory 202, a processor 204, getmail. MRA is a computer program that can retrieve email a transceiver 206, a con?guration manager 208, and a mes messages from a remote server such as the server node 110. sage retriever 210. As mentioned With reference to FIG. 1, the [0028] For one embodiment, the ?rst client node 102 can ?rst client node 102 can have one or more email accounts such include only the memory 202 and message softWare. As men as the ?rst message account, the second message account, and tioned earlier, the message softWare such as an email client is the third message account. For one embodiment, the ?rst a front-end computer program that is used to manage the client node 102 can have a pull-message con?guration for the email messages of the email accounts associated With the ?rst ?rst message account, Which can be referred to as a pull client node 102. In this embodiment, the message softWare message account. Further, the ?rst client node 102 can have a can perform the functions of the processor 204, the trans push-message con?guration for the second message account, ceiver 206, the con?guration manager 208, and the message Which can be referred as a push-message account. retriever 210. Examples of the message softWare include, but [0024] The memory 202 is con?gured to store con?gura are not limited to, open source MoZilla ThunderbirdTM, tion information pertaining to the email accounts associated Microsoft OutlookTM, a Mail User Agent (MUA), and With the ?rst client node 102. Each of the email accounts is MuttTM. identi?ed based on a message account ID such as [0029] The ?rst client node 102 also includes the con?gu [email protected], dchi79yahoo.co.in, or billl2@gmail. ration manager 208 that is coupled to the memory 202. The com. The processor 204, coupled to the memory 202, is con?guration manager 208 is con?gured to change the ?rst con?gured to poll the server node 110 for the ?rst message client node 102 from a pull-message con?guration to a push account, because the ?rst message account has the pull-mes message con?guration for the ?rst message account under sage con?guration. The processor 204 (via the transceiver certain circumstances. The con?guration of the ?rst client 206) polls the server node 110 to check for the arrival of a neW node is changed based on if a push-message is received for the email message such as a ?rst message that is associated With ?rst message account. Thereafter, When the ?rst client node the ?rst message account. 102 has been changed from a pull-message con?guration to a [0025] The transceiver 206, Which is coupled to the push-message con?guration for the ?rst message account, the memory 202, is con?gured to receive messages from the processor 204 can terminate polling of the server node 110. server node 110. The messages received from the server node The method for changing the ?rst client node 102 from the 110 can be either user-readable or user-unreadable messages. pull-message con?guration to the push-message con?gura In one embodiment, for a pull-message account, the trans tion for the ?rst message account Will be explained in detail in ceiver 206 receives a user-unreadable message notifying the accordance With FIGS. 3, 4, and 5. ?rst client node 102 of the arrival of a ?rst message, after the [0030] FIG. 3 is a sequence diagram illustrating a method client node 102 polls the server node 110 for the pull-message for managing the reception of messages at the ?rst client node account. Moreover, the transceiver 206 can receive the ?rst 102 in a communication netWork 100, in accordance With an message Which is a user-readable email message. For a push embodiment of the present invention. The present invention message account, the transceiver 206 receives a push-mes discloses a method that alloWs the ?rst client node 102 to sage (user-unreadable message) Which noti?es the ?rst client conveniently sWitch from a “pull” messaging technology to a node 102 about the arrival of the neW message, such as a more ef?cient “push” messaging technology for a particular second message (user-readable email message) associated email (or IM) account. Initially, the ?rst client node 102 has a With the second message account. ?rst message account con?gured as a pull-message account. [0026] For one embodiment, the transceiver 206 receives The server node 110 is also in pull-message con?guration. At the push-message from a netWork device such as a Base step 302, the ?rst client node 102 polls the server node 110 to Transceiver Station (BTS). The netWork device can store a list check for an arrival of a neW message (such as a ?rst message) that contains the addresses of the client nodes corresponding associated With the pull-message account. The ?rst client to various message account IDs. The server node 110 may not node 102 polls the pull-message account at the server node knoW the address of the ?rst client node 102 associated With 110 by sending a user-unreadable message. At step 304, the the ?rst message account. Therefore, the server node 110 Will ?rst client node 1 02 receives a user-unreadable response mes US 2009/0164586 A1 Jun. 25, 2009

sage from the server node 110. The user-unreadable response 110. Further, the server node 110 changes from a pull-mes message is a response to the polling message. The user sage con?guration to a push-message con?guration for the unreadable response message noti?es the ?rst client node 102 ?rst message account. When the server node 110 is changed about an arrival of a neW message (such as a ?rst message) to the push-message con?guration, it can send a push-mes associated With the ?rst message account at the server node sage notifying the ?rst client node 102 regarding an arrival of 110. At step 306, the ?rst client node 102 retrieves the ?rst a neW second message at the server node 110. The push message from the server node 110. The ?rst message is a message is a user-unreadable message. user-readable email message. [0035] At step 410, the processor 204 checks Whether a [0031] Subsequently, the server node 110 changes con?gu push-message has been received by the transceiver 206. The ration to a push-message con?guration. The server node 110 push-message noti?es the ?rst client node 102 about the can change con?guration by replacement, upgrading, or arrival of a second message at the server node 110. As men another mechanism. At step 308, the recon?gured server node tioned previously, the push-message is a noti?cation that is 110 sends a push-message to the ?rst client node 102. The not readable by a user of the ?rst client node 102. The second push-message is a noti?cation of arrival of a second message message is a neW message that is associated With the ?rst for the ?rst message account at the server node 110. In an message account of the ?rst client node 102. For one embodi embodiment of the present invention, the push-message noti ment, the transceiver 206 receives the push-message directly ?cation is an Open Mobile Alliance (OMA) Email Noti?ca from the server node 11 0. For another embodiment, the trans tion (EMN). The push-message is just a noti?cation message ceiver 206 receives the push-message via a netWork device and it is not readable by a user of the ?rst client node 102. such as a BTS. If the push-message is not received at the ?rst After receiving the push-message, the ?rst client node 102 client node 102 at step 410, then the process returns to step changes the con?guration of the ?rst message account to a 404. If it is veri?ed at step 410 that the push-message has been push-message con?guration. Further, at step 310, the ?rst received at the ?rst client node 102, then step 502 is executed. client node 102 retrieves the second message from the server [0036] At step 502, the con?guration manager 208 changes node 110. The second message is a user-readable email mes the con?guration of the ?rst client node 102 for the ?rst sage addressed to the ?rst message account. message account from the pull-message con?guration to a [0032] After changing the con?guration of the ?rst mes push-message con?guration, based on the push-message. At sage account from the pull-message con?guration to the step 504, the message retriever 210 retrieves the second mes push-message con?guration, the ?rst client node 102 stops sage from the server node 110. After changing the con?gu polling the server node 110. NoW, Whenever a neW message ration of the ?rst client node 102, the processor 204 termi associated With the push-message account arrives at the nates polling of the server node 110 for the ?rst message server node 110, the server node 110 sends a push-message account at step 506. Thereafter, the method terminates at step notifying about a neW message to the ?rst client node 102 at 508. Subsequently, the ?rst client node 102 having the push step 312. At step 314, the ?rst client node 102 retrieves the message con?guration for the ?rst message account receives neW message associated With the push-message account. a push-message from the server node 110 Whenever a neW Subsequently, the ?rst client node 102 having the push-mes message associated With the ?rst message account arrives at sage con?guration for the ?rst message account receives a the server node 110. push-message from the server node 110 Whenever a neW [0037] For one embodiment, the steps mentioned above can message associated With the ?rst message account arrives at be performed by a message softWare component such as an the server node 110. email client of the ?rst client node 102. In an embodiment of [0033] FIGS. 4 and 5 illustrate a How diagram detailing a the present invention, the user of the ?rst client node 102 can method for managing the reception of messages in the com manually revert the ?rst message account to a pull-message munication netWork 100, in accordance With another embodi con?guration. ment of the present invention. The method for managing the [0038] Various embodiments of the present invention offer reception of messages has been explained for the reception of one or more advantages. The present invention provides a messages for the ?rst message account associated With the method and system for managing the reception of messages ?rst client node 102.As mentioned earlier, the ?rst client node in a communication network. The method and system enables 102 starts With a pull-message con?guration for the ?rst mes a client node having a pull-message account to receive push sage account. The method for managing the reception of emails or push-messages from a server node. For example, a messages initiates at step 402. At step 404, the processor 204 mobile phone having a pull-message account can automati polls the server node 110 to check for the arrival of a ?rst cally recon?gure to a push-mes sage con?guration and receive message at the server node 110. The ?rst message is associ push emails from the server node and eliminate unnecessary ated With the ?rst message account. At step 406, the processor polling of the server node by a client node. The method and 204 checks Whether the ?rst message has arrived at the server system provides an ef?cient Way to receive messages from the node 110. If it is ascertained at step 406, that the ?rst message server node. Moreover, the method and system enables a has not arrived at the server node 1 10, then the process returns pull-message account of the client node to automatically to step 404 for periodic polling after a pre-de?ned time inter change its con?guration to a push-message con?guration on val. If it is ascertained at step 406 that the ?rst message has the basis of received push-messages. Subsequently, this client arrived at the server node 110, step 408 is executed. node receives push emails or push-messages from the server [0034] At step 408, the message retriever 210 retrieves the node. Once the client node has been con?gured as a push ?rst mes sage from the server node 11 0. The message retriever message con?guration, the client node does not need to poll 210 can be a Mail Retrieval Agent (MRA) such as fetchmail, the server node, and hence, conserves the battery of the client retchmail, or getmail. As mentioned previously, an MRA is node, because polling of the server node by the client node usually implemented as a softWare program that can retrieve can deplete the battery life Without providing an advantage email messages from a remote server such as the server node When no neW messages are read. Further, since polling for US 2009/0164586 A1 Jun. 25, 2009

new messages is no longer required, implementation of the as critical, required or essential features or elements of any or invention also prevents unnecessary communication netWork all the claims. The invention is de?ned solely by the appended tra?ic that is caused by polling of the server node. claims, including any amendments made during the pendency [0039] It Will be appreciated that the method and system for of this application, and all equivalents of those claims, as managing the reception of messages in a communication issued. network, described herein, may comprise one or more con ventional processors and unique stored program instructions What is claimed is: that control the one or more processors, to implement, in 1. A method for managing reception of messages in a conjunction With certain non-processor circuits, some, most, communication netWork comprising: or all of the functions of the system described herein. The polling a server node, by a ?rst client node having a pull non-processor circuits may include, but are not limited to, message con?guration for a ?rst message account, to signal drivers, clock circuits, poWer source circuits, and user check for an arrival of a ?rst message at the server node input devices. As such, these functions may be interpreted as steps of a method and system for managing the reception of associated With the ?rst message account; messages in a communication netWork. Alternatively, some receiving a push-message at the ?rst client node, the push or all the functions could be implemented by a state machine message notifying the ?rst client node of an arrival of a second message at the server node, Wherein the second that has no stored program instructions, or in one or more application-speci?c integrated circuits (ASlCs), in Which message is a neW message associated With the ?rst mes each function, or combinations of certain of the functions are sage account; and implemented as custom logic. Of course, a combination of the changing the ?rst client node from the pull-message con tWo approaches could also be used. Thus, methods and means ?guration to a push-message con?guration for the ?rst for these functions have been described herein. message account based on the push-message; and [0040] It is expected that one With ordinary skill, notWith terminating the polling of the server node for the ?rst standing possibly signi?cant effort and many design choices message account by the ?rst client node When the ?rst motivated by, for example, available time, current technology client node is changed from the pull-message con?gu and economic considerations, When guided by the concepts ration to the push-message con?guration for the ?rst and principles disclosed herein, Will be readily capable of message account. generating such softWare instructions, programs and lCs With 2. The method as recited in claim 1 further comprising: minimal experimentation. retrieving the second message after the receiving. [0041] It should be observed that the present invention 3. The method as recited in claim 1, Wherein the ?rst encompasses combinations of a method and system for man message account is an electronic mail account. aging the reception of messages in a communication netWork. 4. The method as recited in claim 1, Wherein the ?rst Accordingly, the method steps have been represented, Where message account is an instant messaging account. appropriate, by conventional symbols in the draWings, shoW 5. A ?rst client node in a communication netWork compris ing only those speci?c details that are pertinent for an under ing: standing of the present invention, so as not to obscure the a memory con?gured to store con?guration information disclosure With details that Will be readily apparent to those for a ?rst message account associated With the ?rst client With ordinary skill in the art, having the bene?t of the descrip node and con?gured as pull-message con?guration; tion herein. a processor, coupled to the memory, con?gured to poll a [0042] In this document, the terms “comprises, compris server node to check for an arrival of a ?rst message ing,” or any other variation thereof, are intended to cover a associated With the ?rst message account; non-exclusive inclusion, such that a process, method, article, a transceiver, coupled to the memory, con?gured to receive or apparatus that “comprises” a list of elements includes not a push-message, Wherein the push-message noti?es the only those elements but may also include other elements that ?rst client node of an arrival of a second message at the are not expressly listed or inherent in such a process, method, server node, the second message is a neW message asso article or apparatus. An element proceeded by “comprises . . ciated With the ?rst message account; and . a” does not, Without more constraints, preclude the existence of additional identical elements in the process, method, a con?guration manager, coupled to the memory, con?g ured to change the ?rst client node from the pull-mes article or apparatus that “comprises” the element. The term sage con?guration to a push-message con?guration for “another,” as used in this document, is de?ned as at least a the ?rst message account based on the push-message. second or more. The terms “includes” and/or “having”, as used herein, are de?ned as “comprising”. 6. The ?rst client node as recited in claim 5 further com [0043] In the foregoing speci?cation, the invention and its prising: bene?ts and advantages have been described With reference a message retriever, coupled to the processor, con?gured to to speci?c embodiments. HoWever, one With ordinary skill in retrieve the second message from the server node after the art Would appreciate that various modi?cations and receiving the push-message. changes can be made Without departing from the scope of the 7. The ?rst client node as recited in claim 5, Wherein the present invention, as set forth in the claims. Accordingly, the processor is further con?gured to terminate the polling of the speci?cation and ?gures are to be regarded in an illustrative server node for the ?rst message account When the ?rst client rather than a restrictive sense, and all such modi?cations are node is changed from the pull-message con?guration to the intended to be included Within the scope of the present inven push-message con?guration for the ?rst message account. tion. The bene?ts, advantages, solutions to problems, and any 8. The ?rst client node as recited in claim 5, Wherein the element(s) that may cause any bene?t, advantage or solution memory is further con?gured to store con?guration informa to occur or become more pronounced are not to be construed tion of one or more message accounts, Wherein the one or US 2009/0164586 A1 Jun. 25, 2009 6

more message accounts are associated With the ?rst client 11. The ?rst client node as recited in claim 5, Wherein the node. ?rst message account is an instant messaging account. 9- The ?rst Client node as recited in Claim 5, wherein the 12. The ?rst client node as recited in claim 5, Wherein the ?rst message account is an electronic mail account. ?rst message is an instant messaging message, 10. The ?rst client node as recited in claim 5, Wherein the ?rst message is an electronic mail message. * * * * *