Messaging service in a wireless communications network

Technical Field [0001] The present invention relates to a message transfer service in a wireless communication network.

Background Art [0002] Short Messaging Service (SMS) is a technology for sending and receiving short text messages between mobile users. It was first introduced in the Global System for Mobile Communications (GSM) standards in the 1990s, and then incorporated into other wireless standards, such as multi-code access systems (CDMA). Coda Division Multiple Access). Although the SMS service is extremely popular, one of its biggest disadvantages is that the SMS can only contain a small amount of data due to restrictions imposed by the SS7 MAP (Mobile Application Part) protocol. An SMS can only contain at most 160 eight-bit alphanumeric or binary characters, and any message longer than 160 characters is usually sent in a number of messages.

[0003] The SMS Messaging Center (SMSC) is responsible for handling the delivery of SMS messages in a wireless communication network. SMS messages sent by the mobile user are first delivered to the user's network SMSC before they are directed to the recipient. If the recipient's network is served by another provider or uses different wireless standards, the message can go through more than one SMSC center or SMSC gateway before reaching its final destination. Signaling system 7 (SS7) provides a transport mechanism for the movement of SMS messages.

[0004] There are many messaging services that are extensions to the SMS service. The Advanced Enhanced Messaging Senzice (EMS), which uses the existing SMS service infrastructure, allows you to combine up to 255 SMS messages into one EMS message with richer content, including elements such as animations, images, sounds and formatted text. Unlike SMS and EMS, messages in the Multimedia Messaging Senzice (MMS) are delivered using a mobile packet network. The MMS service was first introduced in 2.5 generation networks, such as GPRS, which provides an Internet Protocol (IP) layer for existing GSM networks. A multimedia message can contain images, audio and video clips.

[0005] On the other hand, Mobile Instant Messaging (MIM) technology allows mobile devices to participate in the immediate transmission of messages in real time over an IP data network. Users are required to register with the provider of the instant messaging service username tag or "handle" for sending and receiving messages. Many current MIM services also require users to have a permanent Internet connection during chat sessions.

[0006] The article entitled "Context-aware unified communication" (Hui Lei et al.) Reveals a unified communications system that selects the appropriate device for the recipient on an incoming call. This system also monitors the context of communicating pages and determines whether the connection should be transferred to another recipient's device.

[0007] Document US 2006/167849 A1 (Marcus et al.) Discloses a system for conducting instant messaging sessions on mobile devices. An instant message is sent to the user if that user is connected and active. However, if the user is disconnected, an offline notification will be sent to that user.

[0008] Document WO 2006/014603 A2 (Cingular Wireless II LLC) discloses a wireless messaging oriented device that transmits messages in the form of e-mail messages, SMS messages and an instant messaging service.

Summary of the Invention [0009] In a first aspect, the invention is a method for providing a message transfer service on a wireless device in a wireless communication network; wherein the method comprises the steps of: acquiring by the mobile wireless device of the sender from an outgoing message in this mobile wireless device of the sender of the destination address associated with the mobile wireless device of the recipient;

verification by the sender's mobile wireless device whether the destination address is adapted to receive messages via a packet switched carrier;

in the case of positive verification, automatic sending of a message by the sender's mobile wireless device to the recipient's mobile wireless device at the destination address via packet switched media;

otherwise, the sender's mobile wireless device automatically sends the message to the recipient's mobile wireless device at the destination address via SMS medium.

[0010] Unlike conventional SMS, EMS and MIM clients, the present invention combines existing messaging solutions, offering a single interface for sending and receiving both text and multimedia messages. Automatic media selection provides the user with the largest range of messaging options, including text, voice, video, images, based on knowledge of the status and capabilities of the recipient's device.

[0011] The SMS carrier may be a conventional SS7 GSM signaling channel. Packet switched media may be HSDPA, WCDMA, CDMA2000, GPRS or similar data carrier. Packet switched media can also be supported by other wireless technologies, such as Bluetooth, WiFi, WiMax.

In addition, packet switched media can be supported by the sender's mobile communications operator or an independent mobile Internet service provider. Compared to the SMS carrier, the packet switched data carrier is adapted to send messages of unlimited size at a higher speed.

[0012] The destination address may be a cell phone number or a numeric "short code" or alias, representing one or more, or a combination, of telephone numbers, e-mail addresses, instant message handles, and IP addresses. Thus, for all users of this messaging service, the present invention, unlike conventional MIM client programs, uses the user's mobile number as the user identifier and does not require the user to register the username, tag or handle, thereby providing one number for sending messages.

[0013] A message client running on the device can programmatically and dynamically construct an outgoing message with the correct syntax with given user preferences and given dynamic message server requirements for a particular service.

[0014] The message client may interpret incoming SMS messages or incoming messages from the message server, which are identified in their content as determining requirements for the dynamic structure of the message when the user views such a message.

[0015] Alternatively, the message client may interpret incoming SMS messages or incoming messages from the message server that are identified in their content as determining requirements for dynamic message structure, and retain these requirements for dynamic message structure so that they can be recalled by selecting dynamic menu.

[0016] The requirements may be specified in a structured format using XML, so that the message client should, when the user opens a message containing requirements for dynamic message structure or when the user selects a dynamic menu:

• present the user with options to choose from; and • Know the intended purpose and message carrier for each option; and • Ask the user for input or to choose a file to send with the constructed message; and • Construct the message with the correct syntax based on the user's choices and input.

[0017] The method may further include the step of connecting to the message server before verifying the destination address. If a connection to a message server is not available, the present invention may support a variety of configuration methods for configuring a mobile device to connect to a message server.

[0018] First, the method may include the step of acquiring connection parameters and displaying the acquired parameters on the mobile device if a connection to the message server is not available. The mobile user can then use the downloaded parameters to manually configure the phone before attempting to connect to the message server again.

[0019] In addition to manual configuration, the present invention may support manual and automatic OTA (over-the-air) programming. The method may further comprise the step of displaying the sender of the link to request the OTA configuration message if a connection to the message server is not available. For example, the user can then request a configuration message to be sent to the user's mobile device by accessing the web page.

[0020] The method may further comprise the step of acquiring the connection parameters, automatically creating the OTA configuration message based on the acquired parameters and sending the generated configuration message from the mobile device to the same mobile device. Using this automatic OTA configuration, the user does not need to manually change the settings on their mobile device to connect to the message server. The OTA configuration message can be a binary SMS.

[0021] The step of verifying the destination address may include sending an address verification request to the message server and then receiving a notification from the message server determining whether the destination address is adapted to receive messages via packet switched medium.

[0022] The destination address may be adapted to receive messages using a packet switched medium if the address is on the list of subscribers' addresses. The subscriber address list can be a list of destination addresses that subscribe to the messaging service. The list of subscriber addresses can be maintained on the message server.

[0023] The destination address may be adapted to receive messages using a packet switched medium if the address is on the list of subscribers' addresses and is in an active state. For example, the recipient is inactive if the destination address's message queue length exceeds the maximum length allowed.

[0024] The method may further include the step of automatically providing the option of adding one or more attachments to the outgoing message before sending the message if packet switched medium is selected. The attachment can be a text, voice, video or image file. On the other hand, an outgoing message sent using an SMS medium can only be an SMS or EMS message and has no attachments.

[0025] Using the present invention, the sender can optimally add attachments to the outgoing message, depending on the capabilities of the recipient's mobile device. For example, a user may attach a voice or video message to a text message if the recipient is adapted to receive and play such an attachment. In addition, the present invention uses a "push" model for providing voicemail to a mobile user without the need for downloading.

[0026] The method may further include the step of formatting the outgoing message according to the delivery mode before sending the message. If the message is sent using packet switched media, the message can be formatted as an XML ASCII string.

[0027] The method may further include the step of adding a system message to the outgoing message if the SMS bearer is selected.

[0028] The system message may include an invitation to add a destination address to the list of subscribers' addresses if the destination address is not in this list. Otherwise, if the destination address is in the list of subscribers' addresses but is inactive, the system message may contain an invitation to retrieve messages from the destination address's message queue.

[0029] By sending non-subscribers an invitation to add their destination addresses to the list of subscribers, new users can subscribe to the messaging service without having to actively search for how to get this service. This viral method of inviting users with the peer-to-peer method also does not require central monitoring or generate additional traffic, as the invitation is added to the outgoing message.

[0030] The method may further include the step of notifying the recipient if the recipient is on the subscriber list, both when the message has been received (if the recipient is connected to the message server), as well as when the message has been added to the queue but has not yet been delivered (if the recipient is not connected to the message server). The notification method can be a single ringtone on the user's mobile device. A notification message can also be sent to the sender of the message.

[0031] The method may further include queuing outgoing messages for later delivery if the message has not been delivered. For example, a message cannot be delivered if the destination address is in the list of subscribers' addresses, but at the time of sending the recipient is not connected to the message server via packet switched medium.

In another aspect, the invention is a mobile device programmed to implement this method. In another aspect, the invention is a software application implementing this method.

Description of the drawing figures [0033] An example of the present invention will now be described with reference to the attached drawing figures, in which:

Fig. 1 is a diagram of the messaging system.

Fig. 2 (a) shows the user interface on the sender's mobile device.

Fig. 2 (b) shows the user interface on the recipient's mobile device.

Fig. 3 shows a flowchart of a client-implemented message function.

Fig. 4 is a flowchart of a client-implemented message function for connecting to a message server.

Fig. 5 is a flowchart of the address verification function implemented by the message server.

Fig. 6 (a) is a diagram of the message client architecture.

Fig. 6 (b) shows an exemplary message format.

Fig. 6 (c) is a schematic of the TCP / IP model used by the message client.

Fig. 7 shows the user interface on the sender's mobile device during a chat session.

Preferred Embodiments of the Invention [0034] Referring first to Fig. 1, the messaging system 100 includes a message server 170 connected to users of networks 110, 120 and 125 via the Internet 160 and base stations 130, 150, 180 and 190. Base stations 130 and 150 are typical base stations in a GSM, CDMA, 3G, 3.5G or similar network that supports HSDPA, WCDMA, CDMA2000, GPRS or similar data carrier and are connected to the SMSC via a core 140 network.

[0035] Users of networks 110, 120 and 125 may be part of a wireless personal area network (WPAN), wireless local area network (WLAN) or wireless wide area network (WWAN) wide area network). Base stations 180 and 190 are wireless internet base stations operated by an independent wireless service provider. For example, the user can connect to the wireless Internet using technologies such as Bluetooth, ZigBee or a mesh network in WPAN; WiFi in the WLAN or WiMax network in the WWAN network.

[0036] In this example, it is assumed that the first user 110 ("sender") sends a message to the second user 120 ("recipient"). The message contains the phrase "Hi there!" as well as a photo and voicemail as attachments. With reference now to Fig. 2 (a), a message client 114 is activated in the mobile device 112 responsible for selecting the outgoing message delivery mode.

[0037] For the application of the present invention, the message client 114 must be activated by the sender 110. However, the message client 114 can also be activated automatically when the telephone is switched on, if the telephone operating system offers such a possibility. After enabling the message client 114, sender 110 dials or enters the destination number. The message client 114 then determines how the message can be sent.

[0038] The recipient 120 may be in a network served by the same or another service provider. Both sender and recipient have addresses associated with them. The destination address is both a cell phone number and a numeric "shortcode" or "channel", which is an alias that represents one or more phone numbers, email addresses, or instant message user handles. For example, certain number ranges may be controlled by the message server (e.g. 1,800 χχχχχχ), some may be under user control as destination, as aliases for a group of numbers and addresses (e.g. 1,801 χχχχχχ), and some may be intended for access to content services (e.g. 1900 χχχχχχ). The short codes are unique and private to the user, therefore the same numerical short code can be used by a number of users.

[0039] The short codes are created by users and maintained by the message server 170. For example, the user creates the short code by sending the message server 170 with the following content:

Add channel 20 <a href="mailto:andrew@messmo.com">andrew@messmo.com</a>, <a href="mailto:robert@yahoo.com">robert@yahoo.com</a>, 0423789080, <a href="mailto:98765432@jabber.org">98765432@jabber.org</a>.

[0040] The abbreviated code 20 is an alias for a group containing two e-mail addresses, one mobile number, and an instant messaging handle. For example, to send a message to the short code created, 1801 20 will be selected as the destination address.

[0041] The syntax of the messages in the above example is strict, however, limitations in knowing the syntax of messages do not limit users in using services.

[0042] The message client 114 is adapted to programmatically and dynamically construct the outgoing message with the correct syntax, given the user preferences and the dynamic requirements of the message server 170 for a particular service.

[0043] The message client 114 interprets incoming SMS messages or incoming messages from the message server 170, which are identified in their content as determining requirements for the dynamic structure of the message. This interpretation can occur when the user reads a message (for example, a message titled "Click to create a channel"), or a message client can interpret incoming SMS messages or incoming messages from the message server 170 and maintain the requirements for dynamic message design so that could be called up by selecting a dynamic menu option.

[0044] The requirements are defined in a structured format using XML so that the message client 114 should, both when the user opens a message containing requirements for the dynamic structure of the message, and when he selects the dynamic menu:

• Provide the user with options to choose from; and • Know the intended purpose and message carrier for each option; and • Ask the user for input or to choose a file to send with the constructed message; and • Construct the message with the correct syntax based on user choices and input. If the message contained requirements for dynamic message structure, where these requirements are, for example, defined as:

&lt;MessageConstructorRequirements&gt;

&lt;MCTitle&gt; Shortcode &lt;/ MCTitle&gt;

&lt;Option&gt;

&lt;OptionTitle&gt; Subscribe &lt;/ OptionTitle&gt;

&lt;Bearer&gt; SMS &lt;/ Bearer&gt;

&lt;Destination&gt; 1800 &lt;/ Destination&gt;

&lt;OutputToken DataType = 'String' lnputMethod = 'Constant' Count = '1'&gt; Add channel &lt;/OutputToken&gt;

&lt;OutputToken DataType-Number 'InputMethod-lnput' Count = '1'&gt; Channel &lt;/OutputToken&gt; &lt;OutputToken DataType-String 'lnputMethod =' lnput 'Count =' 4 '&gt; Destination &lt;/OutputToken&gt;

&lt;/ Option&gt;

&lt;/ MessageConstructorRequirements&gt;

[0045] The message client 114 would present to the user a message entitled "Shortcode", with the message client:

• It would present the user with the option "Subscribe"; while choosing this option • He would ask the user for one short code. The user would enter, for example, 20;

• It would ask the user for four destination addresses. The user enters e.g.<a href="mailto:andrew@messmo.com">andrew@messmo.com</a>, <a href="mailto:robert@yahoo.com">robert@yahoo.com</a>, 0423789080, <a href="mailto:98765432@jabber.org">98765432@jabber.org</a>;

• Construct a message, eg "Add Channel 20 <a href="mailto:andrew@messmo.com">andrew@messmo.com</a>, <a href="mailto:robert@yahoo.com">robert@yahoo.com</a>, 0423789080, 98765432@jabber.org "to be sent until 1900 via SMS.

[0046] Thus, enabling the user to use the service, otherwise the user may be reluctant to enter the exact message syntax required by the service or may not know the syntax.

[0047] When the message is sent to an abbreviated code, the message may be sent as a conventional SMS or EMS message, using a conventional SMS carrier or packet switched data carrier. Using the SMS bearer, the message will be sent via GSM or GPRS signaling channel to the core network 140, SMSC 145, base station 150, before finally reaching the recipient 120. Attachments such as photos and voicemail will not be sent using the SMS carrier.

[0048] When using a packet switched data carrier, the message client can choose between sending a message using a packet switched medium supported by a mobile operator or via an external network. For example, in a GSM system with a GPRS layer, the SMS carrier may be the SS7 signaling channel, and the packet switched data carrier may be a shared transmission channel that connects a number of time slots into a GSM TDMA frame. Packet switched data can also be Bluetooth, WiFi, WiMax or any other wireless data transmission protocol in the WPAN, WLAN or WWAN network.

[0049] Referring now to Fig. 3, the client 114 first checks whether the sender 110 is connected to the Internet 160 and the message server 170; see step 205. As shown in Fig. 1, the sender 110 can be connected to the message server 170 via the mobile operator's data network (base stations 130) or a network provided by an independent mobile Internet service provider (base station 180).

[0050] The step at which the connection to the message server 170 takes place (step 205) will now be explained with reference to Fig. 4. The client 117 first checks if a connection to the message server 170 is available. If this connection is not available, the client 117 displays the sender 110 phone configuration options so that you can connect to the message server 170; see step 265.

[0051] Client 117 supports three configuration methods. First, you can use manual configuration; see steps 270, 272 and 274. In this case, the client 117 first obtains information specific to the telephone and the mobile Internet service provider. As mentioned, the mobile internet service provider can be a mobile operator or an independent provider. The client 117 then displays the downloaded information so that the sender 110 can configure the phone manually; step 274.

[0052] Alternatively, if the sender's mobile device is adapted to receive and process OTA messages, the client 117 may provide a link to a website that supports OTA configuration requests; steps 280 and 282. This website can be served by a message server 170 or an external site and can be accessed from a PC, via a WAP connection from the sender's mobile device, or by other means. After receiving the OTA configuration message, the sender's mobile device will ask the sender to accept changes to its settings for accessing the mobile Internet according to the configuration message; step 298. If the changes are accepted, the client 117 then attempts to connect to the message server 170 again; step 295.

[0053] In addition to manual configuration and manual OTA configuration request, the client 117 is adapted to perform self-configuration; see steps 290, 292 and 294. Assuming that the client 117 is familiar with the specific parameters needed to configure the sender's mobile device to access the mobile Internet, the client 117 first creates an OTA configuration message based on these parameters. Client 117 then sends this OTA message to the sender's phone (same device). For example, the message can be sent as a binary OTA SMS. After receiving this OTA configuration message, the sender's mobile device asks the sender to accept changes to its mobile Internet access settings according to the configuration message; step 298. Similarly, the client 117 then attempts to connect to the message server 170 again with the new settings; step 295. [0054] The above configuration steps can be repeated until the user connects to the message server 170 or the user abandons the configuration at step 265. In this case, i.e. when the connection to the message server 170 is not available, the client 117 selects the SMS medium as the outgoing message delivery mode and proceeds to format the message in step 240. It should be noted that in addition to configuring the mobile device's access settings to the mobile Internet, the client 117 may generate OTA messages for configuring other settings such as email, WAP, MMS and video streaming settings.

[0055] If the sender has gained access to the message server 170, the client 114 obtains from the message, without reference to the message server, the destination address of the outgoing message 220; see step 210. Next, the client sends a verification request to message server 170 via base station 130 or 180 and Internet 160; step 215.

[0056] After receiving the address verification request, the message server 170 implements the method shown in Fig. 5. First, the message server 170 checks if the destination address is in the list of subscribers; step 320. If the destination address is not known to the message server 170, the delivery mode will be set to SMS bearer; step 350.

[0057] If the destination address is in the list of subscriber addresses, the message server 170 proceeds to check the recipient status, ie whether the length of the destination address message queue has exceeded the set maximum length; 330. If the recipient has a long inactive queue, the message server 170 notifies the message client 114 to send the message using an SMS bearer; see step 350. Otherwise, the delivery mode is set to packet switched media; see step 360 in Fig. 5.

[0058] Again with reference to Fig. 3, the sender's message client 114 provides options for formatting and adding attachments to an outgoing message based on the delivery mode; steps 224, 226, 230 and 240. The delivery mode, using the recipient's phone information stored in the message server, provides an indication of the recipient's telephone capabilities and the type of message that the recipient 120 may receive. If recipient 120 is an active user, the full range of recipient capabilities is assumed. However, if the recipient 120 is an inactive or former subscriber, the recipient's known capabilities 170 may be out of date if the recipient has changed his telephone. The recipient 120 may then be asked to update his information.

[0059] Next, the message client 114 intelligently advises the sender 110 whether the recipient 120 is adapted to read attachments or non-text messages. For example, if the delivery mode is packet switched carrier, the sender 110 is offered the "ON" option to add voice, image or video attachments to the message; see Fig. 2 (a) and steps 224 and 226 in Fig. 3. [0060] If the delivery mode is SMS carrier, the "ON" option is disabled. In addition, depending on the configurable settings of the sender's mobile device, the client 117 also adds a system message to the outgoing message in step 245. If the destination address is not in the list of subscribers, an invitation to download the client will be added to the outgoing SMS or EMS message. For example, the invitation might have the following content:

'Go to www.clientdownload.com to download &lt;message client name&gt; ".

[0061] Next, the recipient 120 of the message client 114 can be downloaded to the mobile device. Then, after starting the message client, the same message client will generate a unique authentication identifier, random or derived from the mobile device hardware identifiers or generated by the message server. Then the message client will start connecting to the message server and provide the authentication ID. In parallel, the message client will send an SMS containing this authentication ID to the SMS gateway service. Then the SMS gateway service sends this message, with the sender's phone number and body of the message containing the same authentication ID, to the message server via HTPP, SMTP, SMPP or similar protocol.

[0062] After receiving the details of the SMS, the message server will determine the source telephone number of the mobile device based on the details of the SMS, and will therefore add the new address (source telephone number) to the list of subscribers' addresses. When comparing the authentication ID, the message server will either send a mobile and user authentication confirmation message to the message client, or the message client will start and request confirmation from the message server. This authentication method allows you to authenticate and register new users to the messaging service with one SMS, without any registration or entry being required.

[0063] If the destination address is in the subscriber's address list but the recipient 120 is inactive, an outgoing SMS or EMS message will be appended with a message reminding the recipient 120 to connect to the message server 170. For example, such a system message could have the content:

"You have 50 unread messages in &lt;message client name». "

[0064] Returning to the sending mobile device 110, if the delivery mode is packet switched medium, the message client manages message delivery similar to a MIM client such as Jabber. An exemplary message client architecture is shown in Fig. 6 (a), where the message client can be Java 2 Mobile Edition (J2ME) installed on a mobile device. A formatted message, an example of which is shown in Fig. 6 (b), is sent as an ASCII XML string through the TCP / IP socket to the HTTP message or post server. The sample message contains the phrase "Hi there!" In the body and two attachments. A photo attachment is defined between the &lt;photo&gt; and &lt;/photo&gt; tags, and voicemail is defined between the &lt;voicemail&gt; and &lt;/voicemail&gt; tags. [0065] Fig. 6 (c) illustrates the five-layer model of TCP / IP used by the message client. In the data link layer, GPRS, 3G, 3.5G or other wireless protocols such as Bluetooth, WiFi and WiMax are used to deliver messages from the wireless device to the wireless communication network, the IP layer uses the IP protocol to deliver the packet from recipient to the sender. UDP and TCP form a transport layer, while HTTP, WAP and XML are used in application and presentation layers.

[0066] Fig. 2 (b) shows the user interface of the recipient 120 when receiving messages. Recipient 120 may receive a notification when the message has been successfully received when, while connected to the message server, it uses another function of the mobile device. The notification can be a single ringtone on the recipient's mobile device.

[0067] If the destination address is the short code, steps 320 and 330 of Fig. 5 are repeated for each telephone number, e-mail address, and user name tag represented by the short code. If not all the addresses in the short code are adapted to receive messages via packet switched medium, the response from the message server 170 may be an array of binary responses. For example, if the short code represents three addresses and only the first has a message client installed, the delivery mode is set to m₁m2m₃ = 100, where 1 is the packet switched carrier and 0 is the SMS carrier.

[0068] A delivery confirmation message may also be sent to sender 110 by message server 170, 'if the message is sent using packet switched medium. The message client 114 keeps a copy of the last messages sent by the user, for example for a limited time. If the message is not delivered successfully, it is added to the queue for later delivery. For example, a message cannot be delivered if the recipient 120 is not connected to the message server 170 when the message is sent. In this case, the recipient 120 may receive a notification that the message is added to the queue for later delivery. The notification can be a single ring on the recipient's mobile device generated by the message server 170, but using a different source number than the one used for notification when the message was delivered to allow the user the optional use of the mobile device's functions, such as assigning different ring tones to the sender's numbers.

[0069] Sender 110 and recipient 120 may send and receive multiple messages during a chat session. The user interface may be similar to those known from instant messaging programs on desktop computers. For example, Fig. 7 shows an exemplary user interface of sender 110. The left arrow indicates a message sent by the user, and the right arrow represents a received message. Depending on the user's configurable preferences, the recipient 120 with the telephone number 1234 may decide that his or her presence should be known to the sender 110; see 116 in Fig. 7. Using presence information, sender 110 may then stop sending new messages to recipient 120 if the latter has gone offline.

[0070] In addition to performing address verification, the message server 170 also supports user authentication. Authentication is simple and does not require the user to create a username tag as in existing MIM servers. Instead, the default ID is the user's mobile number. Authentication adds this mobile number to the list of subscribers' addresses.

[0071] Referring again to Fig. 1, the message server 170 receives each message sent using packet switched medium. Each message is in XML format, and the message server parses the message to specify the destination address.

[0072] Message server 170 also connects to external content providers 175 via Internet 180. When the message server identifies the destination address corresponding to the external content provider, it automatically sends a message to that provider. This provider may, for example, depending on the presence of keywords, send sender 110 additional information related to the keywords. However, the user can disable this function.

[0073] For example, if the message contains the name of a certain brand: BUYME, information about the places of sale of the product or its latest promotion will be collected from the external content provider connected to the message server. In this case, depending on the capabilities of the recipient's mobile device, the information may be sent as a conventional SMS or as a text message via a packet switched carrier with optionally one or more attachments.

[0074] To protect your privacy, your telephone number may not be disclosed to third parties without your consent. For example, the user may send to external content provider 175 via message server 170 a query about the weather forecast for a particular place. To hide user identity, the message server can dynamically create a random number mapped to the user's actual mobile number, and forward the query to an external content provider 175. In addition, this mapping can be dynamic, not static, to ensure that third parties cannot obtain information about the general behavior of users.

[0075] As with user-to-user messages, the type of advertising and marketing messages sent to the user also depends on the user's telephone capabilities. Thus, because the message server's capabilities of the user's telephones are known, as the user's telephones are upgraded, the message server 170 may direct messages to the user with extensive multimedia content.

[0076] One example of the present application outlines how a user using a message client will be asked to use an SMS if the recipient is not a user of the messaging service. The existing context is that the user initiates the message.

[0077] In another example, the functionality may be extended to a situation in which a message is sent using a message client with the intention of asking the user to send a reply SMS. This can be useful for generating SMS traffic from third parties by sending one message that asks recipients to choose one or more voting buttons, each of which sends an SMS to a specific "premium" number.

[0078] On the other hand, the same concept works for the message client user community who does not wish to use "premium" numbers. The entire community can be polled. Everyone receives an indication to choose a voting button, and each choice sends a message with a predefined text to a specific recipient. This minimizes cases of false responses that cannot be counted.

[0079] The embodiments shown should therefore be considered in all respects as illustrations and not as limitations.