Method and arrangement for delivering electronic state message information

• US 8,583,826 B2
• Filed: 11/15/2007
• Issued: 11/12/2013
• Est. Priority Date: 11/15/2006
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Eriksson, Anders
• Primary Examiner(s): Shin, Kyung H
• Application Number:
  US12/515,203
• Publication Number:
  US 20100146062A1
• Time in Patent Office: 2,189 Days
• Field of Search: 709/206, 709/245, 379/88.12, 455/445
• US Class Current: 709/245
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication

Abstract

A method, executed in a messaging server handles electronic messages for a user, handles electronic state messages for at least one terminal, and delivers electronic state messages to at least one terminal. A state change is identified in or at the messaging server, the state change relating to at least one electronic message associated with the user, the at least one electronic message containing a destination identity associated with the user. A terminal address associated with the at least one terminal used by the user is retrieved based on the destination identity associated with the user. An electronic state message is delivered to the at least one terminal using the terminal address as destination address.

Claims

1. A method, executed in a messaging server for handling electronic messages for a user, handling electronic state messages for at least one IMAP terminal, and delivering electronic state messages to at least one IMAP terminal, said method comprising the following steps:

identifying a state change in or at said messaging server, said state change relating to at least one electronic message associated with said user, said at least one electronic message containing a destination identity associated with said user,

looking up said destination identity associated with said user, in a directory connected to said messaging server, to retrieve the terminal identity of said at least one IMAP terminal used by said user,

looking up said terminal identity of said at least one IMAP terminal, used by said user, in a Domain Name System server, to retrieve the Internet Protocol address currently assigned to said at least one IMAP terminal, and

delivering an electronic state message to said at least one IMAP terminal, without using an IMAP session, using said Internet Protocol address as destination address, wherein the electronic state message comprises updated state information and a body of the at least one electronic message.

2. A method according to claim 1, wherein:

the step of retrieving a terminal address is preceded by the step of registering the Internet Protocol address of said at least one IMAP terminal in a Domain Name System Server connected to said messaging server.

3. A method according to claim 2, wherein:

registering the Internet Protocol address of said at least one IMAP terminal in said Domain Name System server is done by issuing a Dynamic Domain Name System update to said Domain Name System server.

4. A method according to claim 1, wherein:

one of the protocols SMTP, LMTP, HTTP, SIP, MMS or SMS or any method within OMA Push is used during said step of delivering said electronic state message to said at least one IMAP terminal.

5. A method according to claim 1, wherein:

said electronic state message is delivered to said at least one IMAP terminal via at least one NAT node whereby a second messaging server is connected to said NAT node.

6. A method according to claim 5, wherein:

said electronic state message is delivered to said at least one IMAP terminal via said second messaging server.

7. A method according to claim 1, wherein said at least one IMAP terminal is a mobile terminal.

8. A messaging server for handling electronic messages for a user, handling electronic state messages for at least one IMAP terminal, and delivering electronic state messages to at least one IMAP terminal, comprising:

a memory;

a processor;

an identifying element adapted, when executed by the processor, for identifying a state change in or at said messaging server, said state change relating to at least one electronic message associated with said user, said at least one electronic message containing a destination identity associated with said user, and

a retrieving element adapted, when executed by the processor, for;

looking up said destination identity associated with said user in a directory connected to said messaging server to retrieve the terminal identity of said at least one IMAP terminal used by said user, and

looking up said terminal identity of said at least one IMAP terminal used by said user in said Domain Name System server to retrieve the Internet Protocol address currently assigned to said at least one IMAP terminal used by said user

a delivering element adapted, when executed by the processor, for delivering an electronic state message to said at least one IMAP terminal, without using an IMAP session, using said terminal address as destination address, wherein the electronic state message comprises updated state information and a body of the at least one electronic message.

9. The messaging server of claim 8, comprising:

a registering element adapted, when executed by the processor, for registering an Internet Protocol address of said at least one IMAP terminal in the Domain Name System server, connected to said messaging server, said Internet Protocol address at least partly constituting said terminal address.

10. The messaging server of claim 9, wherein:

the registering element is adapted, when executed by the processor, to register said Internet Protocol address of said at least one IMAP terminal in said Domain Name System server by issuing a Dynamic Domain Name System update to said Domain Name System server.

11. The messaging server of claim 8, wherein said delivering element is adapted, when executed by the processor, to:

use one of the protocols SMTP, LMTP, HTTP, SIP, MMS or SMS or any method within OMA Push during said step of delivering said electronic state message to said at least one IMAP terminal.

12. The messaging server of claim 8, wherein said delivering element is adapted, when executed by the processor, to:

deliver said electronic state message to said at least one IMAP terminal via at least one NAT node whereby a second messaging server is connected to said NAT node.

13. The messaging server of claim 12, wherein said delivering element is adapted, when executed by the processor, to:

deliver said electronic state message to said at least one IMAP terminal via aid second messaging server.

14. The messaging server of claim 8, wherein said at least one IMAP terminal is a mobile terminal.