WO2009028950A1

WO2009028950A1 - Method and system for simplified exchange of messages

Info

Publication number: WO2009028950A1
Application number: PCT/NO2008/000298
Authority: WO
Inventors: Lars Kristian Roland
Original assignee: Colibria As
Priority date: 2007-08-24
Filing date: 2008-08-25
Publication date: 2009-03-05
Also published as: NO20074342L; NO327184B1

Abstract

The present invention discloses a system and a method for exchange of messages and/or data streams between a first (5) and at least a second client (6), in one or more networks through one intermediate server (2) in said networks comprising the steps of: at the first client (5) generating a first message and forwarding (g) said message to the one intermediate server (2). At the first client (5) generating a second message to be routed in a telecom network and sending (h) second message. The second message is received at the intermediate node (4) in the telecom network. The second message is further forwarded from the intermediate node (4) to the second client (6), and the second message enables the second client (6) to retrieve the first message from the intermediate server (2).

Description

Method and System for Simplified Exchange of Messages

Technical field

The present invention relates to a method and system for instant messaging and presence techniques that are used for sending small messages and data streams between users logged on a network. The invention is among others applicable in a mobile network which supports the short message service (SMS), the Multimedia Messaging Service (MMS) and packet based protocols such as the Internet Protocol (IP).

Background of the invention Instant Messaging (IM) on the mobile phone has been increasingly more popular over the last years. The IM solutions are based on different standards, and one of the most prevalent standards is the OMA-IMPS specifications from the Open Mobile Alliance, previously called Wireless Village. In OMA-IMPS, there is never a direct connection between the clients, and all traffic is passed through a server. The different versions of OMA-IMPS are published on the OMA website: http://www.openmobilealliance.org/release program/imps yl 3a.html http://www.openmobilealliance.org/release_program/imps yl 2 1.html http://www.openmobilealliance.org/release_program/imps_vl_l.html

Another standard used for instant messaging on mobile is SIP/SIMPLE. Both of these technologies use an IP based bearer between the mobile phone and a server. There are typically no direct connections between the clients, though older SIP/SIMPLE implementations sometimes used direct IP connections between the clients. SIP/SIMPLE is mainly defined by IETF, and is published on the IETF website: http://www.ietf.org/html.charters/simple-charter.html SIP/SIMPLE is defined in the following RFCs and other RPCs published by IETF:

RFC 3261 (SIP) The basics of SIP. All other SIP/SIMPLE related RFCs and Drafts build on this.

RFC 3262 Reliability of Provisional Responses in Session Initiation Protocol (SIP) RFC 4566(SDP) Session Description Protocol RFC 4145 TCP-Based Media Transport in SDP (describes the SDP setup attribute) RFC 3264 An Offer/ Answer Model with the Session Description Protocol RPC 3515 (REFER) Defines how the recipient can refer to a resource provided in the request.

RFC 4488 Defines a way to suppress an implicit subscription with the SIP REFER method RFC 3840 Indicating User Agent Capabilities in SIP RFC 3841 Caller Preferences for SIP RFC 3323 A Privacy Mechanism for SIP RFC 3325 Private Extensions for SIP RFC 3327 SIP Extension Header Field for Registering Non-Adjacent Contacts RFC 3608 SIP Extension Header Field for Service Route Discovery During Registration

RFC 3455 P-Header Extensions to SIP for 3GPP RFC 4028 Session Timers in SIP

RFC 3428 Session Initiation Protocol (SIP) Extension for Instant Messaging RFC 3862 CPIM Message Format

RFC 3994 (Is Composing) Indication of Message Composition for Instant Messaging

For the protocols to function properly, the instant messaging client on the handset needs to connect using the IP bearer to the mobile network and communicate with the server. For OMA-IMPS clients, all traffic data is passed over an HTTP based data channel, which uses the mobile network IP channel. SIP/SIMPLE clients use either a TCP or UDP channel to send and receive information.

When an IP connection is not established, the server can wake up the client by sending it an SMS. This mechanism is called Connection Initiation Request (CIR) in IMPS, and a similar method can be deployed in SIP/SIMPLE. The SMS prompts the client to wake up and start up an IP connection to the server. In a GSM network, the client uses a GPRS connection as the IP connection, while in other mobile networks other IP standards are used. '

Upon receiving a CIR message, the IMPS client starts up an IP connection if none already exists and polls the server for information using an HTTP call defined in the specification.

CIR is used for example when one instant messaging user wishes to send information such as an instant message, invitation, chat message or presence update to another instant messaging user and this user does not have an IP based connection to transmit the message on.

The OMA-IMPS specification supports a number of different CIR mechanisms, and the specification details how the server can choose between several negotiated CIR types, for example by trying each one in turn. Some of the CIR mechanisms are IP based, and these are typically tried first, while the more costly SMS CIR mechanism is attempted only if the client has not IP connection that is known to the server.

The sending client sends information such as an instant message to the instant messaging server using IP. The Instant Messaging server checks if the recipient client has an IP connection available. If not, the Instant Messaging server must wake up the recipient client by sending it a specially formatted SMS, as defined in the specifications. The instant messaging server sends an SMS to the recipient client, prompting it to wake up and to initiate an IP connection. After initiating the IP connection, the recipient client retrieves the information that is waiting on the server, for example an instant message sent from another user. The information is retrieved using IP.

SENDING IM CLIENT <-- -> IM Server <-- --> RECIPIENT IM CLIENT

Some instant messaging clients are implemented in Java on mobile handsets with a Java technology called J2ME. Due to usability issues with J2ME, users often have to shut down the client while using other phone features. The client is therefore not running most of the time although the user has an active session with the Instant Messaging Server. The SMS CIR wakeup message then has a dual purpose. The J2ME technology allows the SMS to start the J2ME application. When the SMS has triggered the phone to start the J2ME client, the client then initiates an IP connection to the server and downloads the information waiting there.

The Instant Messaging server typically uses a Short Message Service Centre (SMSC) to send the wakeup SMS to the recipient client, but can also access other network elements or use the network signalling protocols directly to send the SMS. This SMS used to wake up the client and the IP connection consumes network resources and typically costs money, and for service providers that are outside the operator network and only access the operator network through the IP connection, sending such SMS messages can be an expensive cost factor in offering the service. Hence widespread use of IM services on portable devices such as mobile phones are hampered by the fact that service providers have to obtain agreements with a number of network providers, even within one country. Making such agreements is cumbersome, and agreements may also involve developing tools for billing, in that the service provider may not have a direct billing relationship with the user and may not be able to charge the user for this SMS. This cost negotiation barrier represents a major problem for service providers wishing to develop and offer instant messaging services to customers of mobile operators that they do not cooperate closely with. The same wakeup mechanism is also used in MMS and prevents independent service providers from offering MMS services.

The OMA-IMPS standard is HTTP based. The client sends all information to the server by using HTTP as specified in the specifications. The client also fetches all relevant information from the server using an HTTP polling mechanism, including instant messages, presence, invitations and other content. In order to indicate to the client when it should poll, the OMA-IMPS specification includes a wakeup mechanism called Connection Initiation Request (CIR).

Figure 1 illustrates the concept of instant messaging in a network. The standard flow is for the Server 12 to send a CIR message, the client 11 polls, the client 11 receives and displays the IM.

There are a number of CIR mechanisms specified in the different versions of the OMA IMPS Client Server Protocol (CSP), including:

• Standalone SMS (an SMS sent from the server to the client to tell the client to do an HTTP poll) • Standalone HTTP (the client doing an HTTP poll towards one address which on a certain return code can tell the client to do an HTTP poll towards the real server address)

• Standalone TCP (the client keeps a TCP session towards the server on a negotiated port, receiving a message on this channel when it should do an HTTP poll)

• Standalone UDP (the server sends a UDP message of a certain format to the client to tell it to do an HTTP Poll)

• WAP Push SMS (the server sends a WAP Push on SMS to the phone to tell the client to do an HTTP Poll) • WAP Push UDP (the server sends a WAP Push on UDP to the phone to tell the client to do an HTTP Poll)

Common to all of the above mechanisms is that the CIR channel only contains a message indicating to the client that it should do an HTTP poll. The CIR channel does not contain useful information beyond this. Common to all the above mechanisms is also that the CIR message is sent from the server, prompted by a message received from another client over IP. The actual presence information, instant message or other information is passed as part of the poll that follows the CIR message.

Note that prior art solutions involving IM following IETF and OMA standards has been disclosed, the procedures and the message exchange involved may also include exchange of other packet based messages such as multimedia or voice messages.

Summary of the invention

It is an object of the present invention to provide a method and system that eliminates the drawbacks described above.

The features defined in the independent claims enclosed characterise this method and system.

For example, according to one embodiment of the invention, a system and method are provided for exchange of messages and/or data streams between at least two clients in one or more networks through at least one intermediate server in said one or more networks at least comprising the steps of: a) at the first client generating at least one first message and/or data stream and forwarding said at least one first message and/or data stream to the at least one intermediate server; b) at the first client (substantially simultaneously) generating at least one second message suited to be routed in a telecom network and sending said at least one second message (or if the second client has established a packet based connection to the intermediate server, the second client retrieves the at least one first message and/or data stream from the at least one intermediate server and omits step c, d and e); c) the at least one second message is received at an at least one intermediate node in the telecom network; d) the at least one second message is forwarded from the at least one intermediate node to the second client; and e) the at least one second message enables the second client to retrieve the at least one first message and/or data stream from the at least one intermediate server

In particular, the invention allows a compatible server and client to allow sending of the SMS CIR message or MMS message from a client rather than a server. When a client wishes to send an instant message data stream or other similar data to another client, the instant message is sent to the server as normal, but the phone also sends an SMS or MMS directly to the recipient client. The recipient client is prompted by the received SMS or MMS to wake up the client, connect to IP and receive the message. The recipient client now keeps the IP connection open and can use this connection to communicate further with the server and the other users connected to the service by using IP, rather than continuing to use SMS or MMS as a bearer. The sending of the SMS or MMS from the sending client can also be controlled by custom presence information of the recipient client. If SMS or MMS wakeup is turned on by default, the SMS or MMS can be held back by a custom presence attribute. If SMS or MMS is turned off by default, a custom presence attribute of the recipient client can force the sending client to send such an SMS or MMS wakeup.

The invention also allows the SMS or MMS sent directly from the sending client to the recipient client to contain a wake-up message and some useful payload.

The SMS message sent from the original client to the recipient client through the SMSC rather than the IM server is charged as a normal SMS in that network the same situation applies when sending an MMS. The instant messaging service provider is not involved in sending the SMS and therefore is not charged for sending it. The invention allows for the initial wakeup-SMS/MMS to be sent directly from the sending mobile phone to the recipient without involving the IM service provider, but that following messages can be based on IP and therefore use a different cost structure than for SMS or MMS. The invention hence breaks the barrier that SMS and MMS plays in launching an independent mobile instant messaging service. The SMS or MMS sent from the sending client to the recipient client is sent for the recipient client to initiate an IP connection and initiate an IP based service. The mechanism of forcing another client to set up an IP connection can also be used for other services than instant messaging and presence, including for example voice over IP. Voice over IP services over mobile devices have a similar barrier to instant messaging in that it depends on both clients having an established IP connection. The proposed mechanism can hence be used to enhance voice over IP services to also include clients that are not currently online on IP, but initiate the IP connection after having received an SMS or MMS from the client that wishes to make contact with the recipient client. Advantageous embodiments of the invention appear from the following dependent claims.

Short description of the drawings

The invention will be described in detail in reference to the appended drawings, in which: Figure 1 illustrates the concept of instant messaging in a network. The standard flow is for the Server 12 to send a CIR message, the client 11 polls, the client 11 receives and displays the IM,

Figure 2 shows sending of an SMS from one mobile phone to another mobile phone, according to the prior art, Figure 3 shows Instant Message exchange between two clients according to prior art, and

Figure 4 shows Instant Message exchange between two clients according to one embodiments of the present invention. Figure 5 shows Instant Message exchange between one inviting party and a group of clients according to one embodiments of the present invention.

Detailed description

The present invention will now be described with reference to the drawings, the drawings serves illustration purposes only and are not in any way meant to restrict the scope of the invention. A person skilled in the art will realize other embodiments within the scope of the invention supported by the appended claims.

One driving force behind the present invention is to minimize or to remove the need for an extra provider of services when using Instant Messaging or other IP based services between two parties where at least one of the parties is a subscriber in a telecom network. As illustrated in the introductory part widespread use of Instant Messaging is hampered by the unnecessary need of a middleman. Furthermore it is an object to simplify the use of Instant Messaging and similar IP based services for end users as well as for service providers. The basic principle according to the present invention is thus to have a first client 5 to initiate message exchange such as Instant Messaging or to initiate exchange of data streams by forwarding and addressing at least one Instant Message or data streams to a second client 6 at a second party 3, and substantially simultaneously to send a second message such as an SMS, MMS a voice or data message to the second client 6 or to a mobile device 3 hosting the second client 6. The Instant Message is, as is common in prior art, sent to an intermediate server 2 such as an Instant Messaging Server, whereas the second message (SMS MMS, voice or data message) is, contrary to what is known from prior art, sent directly to the second party 3 or through an intermediate node (4) such as a SMS Service center. The second message (SMS MMS, voice or data message) serves the purpose of waking up the second client 6 at the second party 3. The second client 6 is then enabled to retrieve the Instant Message intermediately stored at the intermediate server 2 (e.g. Instant Messaging Server).

By following the method above one avoids the need of generating an SMS, MMS or the like from an intermediate link, and hence the intermediate link, i.e. the Instant messaging Server does not necessarily need to communicate over telephone networks. The Instant Messaging traffic is routed over packet based network such as IP networks. The use of packet based networks such as IP or SIP enables and makes it easy to intercommunicate between mobile devices 1,3 and computers being online.

SMS, MMS, voice or data messages can be sent by phones and by servers. In most cases the SMS, MMS, voice or data sending involves an intermediate node (4) such as a short message service centre (SMSC) in the network. For sending an SMS, MMS, voice or data directly between two phones, the sending phone typically submits the SMS, MMS, voice or data to the intermediate node (4) (e.g. SMSC), which stores the message and transmits it to the recipient mobile phone 3. SMS is passed over the signalling channel in the mobile network and does not require an IP connection.

In the following and the aforementioned the wording SMS is to be interpreted as any text, audio or multimedia message suited for message exchange between any two mobile devices 1,3 or a mobile device and a computer and where the message format allows transfer of a wake up mechanism.. Where IP is explicitly written it is to be understood that it only serves illustrative purposes and any other packet based protocol suited for instant messaging may be deployed within the scope of the present invention.

It is appreciated that a person skilled in the art can utilize the principles disclosed in the appended claims for exchange of any type of packet based messages such as voice and multimedia.

Furthermore wherever the wording Messaging server, Presence Server, instant messaging server etc appears it is to be understood that the name of the server 2 merely serves illustrative purposes, hence it is the function of the servers 2 and networks elements that is important and not their name configuration. Thus this server 2 may be an intermediate server 2 in the network or embedded in one of the clients (5,6) participating in a communication.

The present invention will now be described by way of example so as to ease the understanding and principles for Instant Messaging exchange according to the present invention. The following components may be included in the invention: Client

The client 5,6 is typically an instant messaging and presence client 5,6 running on a mobile device 1,3 or a PC platform 1,3. The clients 5,6 can be in a mobile network such as GSM or Wireless LAN, but can also be using a fixed internet network protocol to access the server. The client 5,6 is based on and implements part of the OMA-IMPS protocol to interface with the IMPS server in the network or another IP based instant messaging protocol.

Instant Messaging Server The Instant Messaging server 2 is a machine situated in the network using IP and other protocols to communicate Instant Messaging and Presence information to clients 5,6 attached to the same network. The presence functions in a service can be deployed as part of an Instant Messaging Server 2 or as a separate Presence Server 2.

Presence Server Presence is small pieces of sometimes personal information that relates to the availability, status and profile of an individual, a group or a device. The Presence server 2 is situated in the network using IP and other protocols to communicate Presence information to clients 5,6 attached to the same network. In some cases, the Instant Messaging server 2 includes a Presence server 2, and in other cases the Presence Server is a separate server.

Short Message Service (SMS)

The Short Message Service is a service deployed in mobile networks that allows users to send text and binary messages from one phone to another. The service also often allows a server 2 in the network such as an Instant Messaging Server to send and receive messages.

Multimedia Messaging Service (MMS)

The Multimedia Messaging Service is a service deployed in mobile networks that allows users to send text, multimedia and binary messages from one phone to another or between phones and online computers. The service also often allows a server 2 in the network such as an Instant Messaging Server to send and receive messages.

IP based voice and video over IP (VVOIP)

The network and clients 5,6 can also support a voice and/or video over IP service (WOIP). VVOIP typically requires all participants to have active IP connections to be invited into a conversation. Some WOIP systems use direct IP connections between users and other WOIP systems pass traffic through a server in the network.

IP Multimedia Subsystem (IMS) The IP Multimedia Subsystem is an architecture and a set of specifications developed by 3GPP and 3GPP2 to propose a SIP based architecture for next generation IP based services for fixed and mobile networks. The IP based services include for example voice and video calls as well as IP based SMS and instant messaging services. The IMS has a mechanism to initiate an IP connection to a mobile phone that does not have a connection. This mechanism is initiated from the network rather than from other mobile devices attached to the network, and resembles the CIR mechanism as defined by the OMA-IMPS specifications.

SIP Proxy The SIP Proxy is defined by IETF and is a server 2 in the network that forwards SIP messages between different clients 5,6 and servers. The SIP proxy generally assumes that there is an IP connection to the recipient. In IMS there are specialized SIP proxies called CSCF.

WiFi WiFi here refers to wireless LAN protocols implemented with licensed and unlicensed standards such as the IEEE 802.11, IEEE 802.16, WiMax, WiBro and similar, that allows a mobile device to connect to wireless routers that are not necessarily part of a standard licensed mobile network.

Short Message Service Centre (SMSC) The Short Message Service Centre is a server 4 in the mobile network that facilitates sending short messages (SMS) between phones and also between phones and servers. The transport of SMS to the mobile 3 phone is typically not IP based, but typically uses the mobile network signalling protocol.

IP The Internet Protocol (IP) is the protocol used on the internet and used by mobile phones 1,3 when connecting using the GPRS mechanism in GSM or similar mechanisms in other networks. IP also includes 3 G and WIFI based IP networks.

Instant Messaging and Presence Protocol

The Instant Messaging and Presence protocol is an IP based protocol that allows for sending messages from one client 5 through a server to another client 6. The protocol is not peer-to-peer but goes through the server. The protocol includes the possibility for the server to wake up the client 6 and the IP connection used by that client 6 by using an SMS. Use cases

In the following it is disclosed exemplified embodiments according to the present invention so as to increase the readability and further to facilitate employment of the present invention in some non exhaustive exemplified embodiments: • A user of a mobile phone 1 sends an instant message to another user of a mobile phone 3 via an instant messaging server 2. This initial message is accompanied by an SMS sent from the sender's phone to the recipient's phone. The SMS wakes up the instant messaging client 6 on the phone and triggers this to set up an IP connection to the server 2 to retrieve the message. • A user of a mobile 1 phone sends an instant message to another user 3 who is on a PC and has no active mobile phone. In this case, no SMS is sent accompanying the instant message, as the PC cannot receive the SMS. It is then the role of the server 2 to wake up the client 6 in an appropriate manner, such as using IP based CIR as specified in the OMA IMPS specifications and known from prior art. • A user of a mobile 1 phone sends an instant message to another user of a mobile phone 3 via an instant messaging server 2. This initial message is accompanied by an SMS sent from the sender's phone to the recipient's phone. The SMS wakes up the instant messaging client 6 on the phone and triggers this to set up an IP connection to the server 2 to retrieve the message. In this particular case, the telephone is in a WiFi zone that allows the phone to connect over WiFi to the service rather than over the mobile network. The phone and client 6 connect over WiFi to retrieve the message and engage in further messaging dialogue.

• A user of a mobile 1 phone sends a group invitation to a group of other users of a mobile phone 3 via an instant messaging server 2. The group invitation is accompanied by one SMS to each user's phones. For those users who are not running a client 6 currently on their phone, the SMS makes the phone start up the client 6 so that the users can engage in the group chat. Other users who are in the chat group who reply to the message do not send an SMS accompanying their message. • A user of a mobile phone 1 sends an instant message to another user who has an

IP connection active and is actively engaged in an instant messaging conversation with another friend. The recipient client 6 has set a special presence attribute in the recipient client's 6 presence information, which indicates to the sending client 5 that the recipient client 6 already has an IP connection. The sending client 5 therefore does not send an SMS together with the instant message. • A user of a mobile phone 1 sends an instant message to another user who has an IP connection active and is actively engaged in an instant messaging conversation with another friend. The server 2 has information about this IP connection, and has automatically set the recipient client's 6 presence information to indicate to other that this particular recipient client 6 already has an IP connection. The sending client 5 checks this presence attribute before sending the instant message and upon verifying that the recipient already has an active IP connection, it does not send an SMS together with the instant message.

• A user wishes to engage in a voice and video over IP call with another party 3, but the other party 3 does not have an active IP connection to engage in such a voice over IP call. The initiating client 5 therefore sends an SMS to the recipient client 6, which is automatically interpreted by the recipient client 6 to activate the IP connection, and the voice and video over IP call can then proceed as normal. • A user wishes to engage in a voice and video over IP call with another party 3, but the other party 3 does not have an active IP connection to engage in such a voice over IP call. The initiating client 5 therefore sends an SMS to the recipient client 6, which is automatically interpreted by the recipient client 6 to activate the IP connection, and the voice and video over IP call can then proceed as normal. The recipient client 6 is able to connect to a WiFi connection, and enters into a voice and video over IP call with the other participant over the WiFi connection rather than using the mobile connection.

• A user of a mobile 1 phone sends an instant message to another user of a mobile phone 3 via an instant messaging server 2. The sending client 5 does not find the phone number of the recipient client 6 by checking the username of the user or the presence information of the user. The client therefore does an IP based call to the server 2 to search for and retrieve the phone number of the recipient, passing the username as an argument to the server 2 and getting the phone number as a result. The phone number is used to send the SMS that accompanies the initial instant message to the recipient's phone. The SMS wakes up the instant messaging client 6 on the phone and triggers this to set up an IP connection to the server 2 to retrieve the message.

• A user of a mobile phone 1 sends an instant message to another user of a mobile phone 3 via an instant messaging server 2. This initial message is accompanied by an SMS sent from the sender's phone to the recipient's phone. The SMS contains all or part of the text written by the sender. The SMS wakes up the instant messaging client 6 on the phone and triggers this to set up an IP connection the server 2. The message from the SMS is shown to the user, but subsequent messages can be received over IP rather than SMS.

Claims

C l a i m s

1. A method for exchange of messages and/or data streams between at least two clients, a first (5) and at least a second client (6), in one or more networks through at least one intermediate server (2) in said one or more networks at least comprising the steps of: a) at the first client (5) generating at least one first message and/or data stream and forwarding (g) said at least one first message and/or data stream to the at least one intermediate server (2), b) at the first client (5) substantially simultaneously generating at least one second message suited to be routed in a telecom network and sending (h) said at least one second message or ii) if the second client (6) has established a packet based connection to the intermediate server (2) the second client retrieves the at least one first message and/or data stream from the at least one intermediate server (2) and omits step c, d and e, c) the at least one second message is received at an at least one intermediate node (4) in the telecom network, d) the at least one second message is forwarded from the at least one intermediate node (4) to the second client (6), and e) the at least one second message enables the second client (6) to retrieve the at least one first message and/or data stream from the at least one intermediate server (2).

2. A method according to claim 1, c h a r a c t e r i z e d i n that step e further comprises the steps of establishing at the second client (6) a packet based protocol connection to the intermediate server (2) facilitating retrieval of the at least one first message and/or data stream from the at least one intermediate server (2).

3. A method according to claim 1, c h a r a c t e r i z e d i n that step e further comprises the steps of establishing at the second client (6) a packet based protocol connection to the intermediate server (2) over WiFi for retrieval of the at least one first message and/or data stream from the at least one intermediate server (2).

4. A method according to claim 1, c h ara c t eri z e d i n that the second client (6) is a number of clients and where the method further comprises: in step a at the first client (5) including address information to a number of recipients, in step b at the first client (5) sending (h) said at least one second message including address information to the number of recipients, in step d the at least one second message is forwarded from the at least one intermediate node (4) to the number of recipients, and in step e the at least one second message enables the number of recipient clients to retrieve the at least one first message and/or data stream from the at least one intermediate server (2).

5. A method according to claim 1 , ch a ra c t eri z ed i n that step b (ii) further comprises the step of at the second client (6) setting a presence attribute in the second clients (6) presence information indicating that the second client (6) has established a packet based connection.

6. A method according to claim 1, ch ar a c t eri z ed i n that step b (ii) further comprises the step of at the intermediate server (2) setting a presence attribute at the second clients (6) presence information indicating that the second client (6) has established a packet based connection.

7. A method according to any of the previous claims, ch ara c t eri z ed i n that the packet based connection is an internet protocol connection and that the at least one first message and/or data stream is passed over an HTTP, TCP or UDP channel.

8. A method according to any of the previous claims, characteri z ed in that the at least one first message and/or data stream is a VoIP message or an multimedia message adapted to use IP as a packet bearer and HTTP, TCP or UDP as a channel for message exchange.

9. A method according to any of the previous claims, charact eriz ed i n that the at least one second message is an SMS or MMS message.

10. A method according to any of claims 1-8, cchhaarra a cteriz ed i n that the at least one second message is a normal voice or data message.

11. A system configured to wireless exchange messages and/or data streams between at least a first (5) and second client (6), through an at least one intermediate server (2) at least comprising a) a first client (5) configured to generate or to retrieve at least one first message and/or data stream and to forward said at least one first message and/or data stream to the at least one intermediate server (2), b) the first client (5) is further configured to generate at least one second message suited to be routed in a telecom network (h,i) and to send said at least one second message, or ii) if the second client (6) has established a packet based connection to the intermediate server (2) the second client (6) is configured to retrieve the at least one first message and/or data stream from the at least one intermediate server (2), c) an at least one intermediate node (4) configured to receive the at least one second message, d) the at least one intermediate node (4) is configured to forward the at least one second message from the intermediate node (4) to the second client (6), and e) the second client (6) is configured to wake up at reception of the at least one second message and to retrieve the at least one first message and/or data stream from the at least one intermediate server (2).

12. The system according to claim 11 , characteriz ed in that the first client (5) is a software client embedded in a mobile device (1).

13. The system according to claim 11 , characteriz ed in that the second client (6) is a client embedded in a computer or a mobile device(3).

14. The system according to claim 11 , charact eri z ed in that the at least one intermediate server (2) is one or more servers configured to receive and forward messages between telecom networks and data networks, the at least one server (2) is further configured to store messages.

15. The system according to claim 14, characteri z ed in that the at least one intermediate server (2) is at least one Instant Messaging server.

16. The system according to claim 11, charact eri z ed i n that the at least one intermediate node (4) is one or more nodes configured to receive, store and forward messages in telecom networks.

17. The system according to claim 16, charact eriz ed in that the at least one intermediate node (4) is one or more of the following a Short Message Service Centre, a "MMS service center" etc

18. The system according to any of the claims 11-17 charact eri z ed i n that the at least one intermediate server (2) is configured to forward and receive messages using Internet Protocol as a bearer and the at least one intermediate server (2) is further configured to pass the at least one first message and/or data stream is over an HTTP, TCP or UDP channel.

19. The system according to any of the claims 11-18 characteri z ed i n that the at least one first message and/or data stream is a packet based message such as VoIP, instant message or multimedia message.

20. The system according to claim 11, ch aract eri z ed i n that the second client (6) is further configured to establish a packet based connection with the intermediate server (2).

21. The system according to claim 19, ch aract eriz ed in that the second client (6) is further configured to establish a packet based connection with the intermediate server (2) over WiFi.