Method and apparatus for delivering advertisements to mobile users

Abstract
The present invention contemplates a variety of techniques for delivering advertisements and similar promotional messages to mobile users through the Unstructured Supplementary Service Data (USSD) bearer in the GSM (Global System for Mobile) network or the 3G (3rd Generation) network. The USSD is a GSM and 3G communication technology that is used to send text between a mobile phone and an application program in the network. USSD provides session-based communication in which transactions occur only during a session. Advertisements delivered through USSD provide a way for the recipient to respond to the promotional message immediately and often at no cost, as many mobile networks do not bill mobile users for their USSD traffic. The present invention allows advertisements to be delivered through USSD in several ways: by inserting a short text into a message in a mobile-initiated USSD session, by temporarily diverting a mobile-initiated USSD session toward an advertisement sub-session, by triggering a network-initiated USSD session the main purpose of which is the delivery of an advertisement, and by causing a mobile user to initiate a USSD session the main purpose of which is the delivery of an advertisement. The present invention discloses a process for inserting advertisements into USSD messages, a process for inserting advertisement sub-sessions into USSD sessions, and a process for delivering advertisements with network-initiated USSD sessions.
Description

BRIEF DESCRIPTION OF DRAWINGS

These and other objects, features and characteristics of the present invention will become more apparent to those skilled in the art from a study of the following detailed description in conjunction with the appended claims and drawings, all of which form a part of this specification. In the drawings:



FIG. 1 is a diagram illustrating a method for inserting a short text into a message of a mobile-initiated USSD session;



FIG. 2 is a diagram illustrating a method for temporarily diverting a mobile-initiated USSD session toward an advertisement sub-session;



FIG. 3 is a diagram illustrating a method for triggering a network-initiated USSD session the main purpose of which is the delivery of an advertisement;



FIG. 4 is a flow chart showing another method for providing advertising content in a mobile-initiated USSD session by inserting a short text into a USSD message;



FIG. 5 is a flow chart showing another method for providing advertising content in a mobile-initiated USSD session by temporarily diverting that session toward an advertisement sub-session;



FIG. 6 is a flow chart showing a method for providing advertising content in a network-initiated USSD session the main purpose of which is the delivery of an advertisement;



FIG. 7 is a diagram illustrating a communication network for providing advertisements to mobile device users in accordance with the present invention;



FIG. 8 is a pictorial image of the database referenced in FIG. 7, together with a database manager;



FIG. 9 is a pictorial image of the advertiser server referenced in FIG. 7;



FIG. 10 is a pictorial image of the USSD server referenced in FIG. 7.





DETAILED DESCRIPTION OF THE INVENTION

The present invention contemplates a variety of techniques for the delivery of advertisements and similar promotional messages to mobile device users. One embodiment of the present invention contemplates techniques for delivering such advertisements and promotional messages through the Unstructured Supplementary Service Data (USSD) bearer in the Global System for Mobile (GSM) or 3rd Generation (3G) networks.


USSD is a standard feature of the GSM and 3G networks and is originally described in GSM Technical Specifications 02.90, 03.90, and 04.90. USSD provides a text-only, bidirectional, interactive, and session-oriented channel of communication between mobile devices and servers in the Home Public Land Mobile Network (HPLMN) and the Visited Public Land Mobile Network (VPLMN) of mobile subscribers.


There are two major versions of the USSD protocol; version 2 is the most popular. A version 2 USSD session can be initiated either by a mobile user or by a network, and permits messages containing up to 182 characters from one of several character sets. Version 1 supports mobile-initiated sessions only, and permits messages up to 200 characters in length.


USSD is used routinely by millions of mobile device users to check their balances and to refill their prepaid accounts. This practice offers an attractive opportunity for the delivery of advertisements.


Unlike SMS traffic, USSD traffic is entirely under the control of mobile operators. Therefore, mobile operators can ensure that their customers are not inconvenienced by unsolicited advertising. For example, mobile operators can implement a permission-based marketing policy and can allow their customers to disable or filter advertisements.


Although mobile operators generally are not allowed to reveal the identities, locations, or other attributes of mobile device users to advertisers, these operators may be allowed to use such information to implement targeted advertising; that is, to select advertisements that are most likely to be of interest to a particular mobile user. Increasing the relevance of advertisements in this manner benefits both mobile users and advertisers. Since the process of targeting advertisements can be computationally intensive, it can be performed off-line, in order to reduce response times.


Many mobile networks do not bill mobile device users for their USSD traffic. Therefore, mobile users may be more inclined to respond to advertisements delivered through USSD than to reply to SMS marketing messages or to click through WAP advertisement banners.



FIG. 1 illustrates a method 100 for inserting a short text into a message of a mobile-initiated USSD session. A mobile user 102 sends a message 108 to a USSD server 104 requesting the balance of her account. For example, the mobile user may be operating a cell phone and using that cell phone to send a USSD message. The USSD server 104 forwards the message 108 to the appropriate service provider 106. The service provider 106 returns a message 110 to the USSD server 104 that reports the balance of the user's account and presents the user with the options of refilling (1) and managing account (2). The USSD server then inserts the advertising message “3: Win a free vacation!” into the reply message and sends the modified message 114 to the mobile user 102.


Continuing the USSD session, the mobile user 102 next sends a message 116 to the USSD server 104 requesting option 3; that is, requesting that the full advertisement be displayed on the mobile device. The USSD server 104 then sends the full advertisement 118 to the mobile user 102. At this point the mobile user 102 selects option 2 (“Leave this ad”) from the full advertisement 118 and sends the appropriate message 120 to the USSD server. The USSD server 104 then sends the original reply message 122 to the mobile user 102. The mobile user selects option 1 (“Refill”) from the reply message 122 and sends the appropriate message 124 to the USSD server 104, which then forwards that message to the service provider 106.



FIG. 2 illustrates a method 200 for temporarily diverting a mobile-initiated USD session toward an advertising sub-session. A mobile user 202 sends a message 208 to a USSD server 204 requesting the balance of her account. For example, the mobile user may be operating a cell phone and using that cell phone to send a USSD message. The USSD server 204 forwards the message 208 to the appropriate service provider 206. The service provider 206 returns a message 210 to the USSD server 204 that reports the balance of the user's account and presents the user with the options of refilling (1) and managing account (2). The USSD server 204 forwards the reply message 212 to the mobile user.


Continuing the USSD session, the mobile user 202 selects option 1 (“Refill”) and sends the appropriate message 214 to the USSD server 204. The USSD server 204 forwards the mobile user's message 214 to the service provider 206, and the service provider returns a message 216 to the USSD server that requests that the mobile user 202 select the amount by which her account is to be refilled: 1: 10 euros, 2: 20 euros, or 3: 30 euros. At this point the USSD server 204 inserts an advertising break 218 into the USSD session, thereby diverting that session toward an advertising sub-session. In the sub-session, the USSD server 204 sends an advertisement 220 to the mobile user 202.


Continuing the USSD session, the mobile user selects option 2 (“Leave this ad”) from the advertisement 220 and sends the appropriate message 222 to the USSD server 204. The USSD server 204 then forwards the reply message 224 to the mobile user 202. The mobile user selects option 1 (“10 euros”) from the reply message 224, and sends the appropriate message 226 to the USSD server 204. The USSD server 204 then forwards the mobile user's message 226 to the service provider 206.



FIG. 3 illustrates a method 300 for triggering a network-initiated USSD session the main purpose of which is the delivery of an advertisement. A mobile user 302 sends a message 308 to a USSD server 304 requesting the balance of her account. For example, the mobile user may be operating a cell phone and using that cell phone to send a USSD message. The USSD server 304 forwards the user's message 308 to the appropriate service provider 306. The service provider 306 sends a reply message 310 to the USSD server 304 that reports the balance of the user's account and presents the user with two options: (1) Refill, and (2) Manage account. The USSD server forwards the reply message 312 to the mobile user, who then hangs up 314, thereby terminating the USSD session.


At this point, the USSD server initiates an advertisement 316 and sends that advertisement 318 to the mobile user 302. The mobile user 302 selects option 1 (“Learn more”) from the advertisement 318 and sends the appropriate message 320 to the USSD server.


Finally, an advertisement can be delivered through USSD by causing a mobile user to initiate a USSD session the main purpose of which is the delivery of an advertisement. For example, an advertiser can publish a message in a printed newspaper that urges readers to dial a specific USSD code on their mobile telephones.


In practice, the process of delivering advertisements through USSD may involve additional steps not shown in the figures described previously. These additional steps are well known to those skilled in the art, and are omitted from the figures in the interest of clarity. For example, in one embodiment the USSD server consults a database (not shown) to determine whether the mobile user has requested that she not receive advertisements or the service provider has requested that its service not be interrupted by advertisements; the USSD server also logs the responses of the mobile user to advertisements for billing purposes. The USSD server also transcodes advertising messages to ensure that they use the same character set as the messages into which they are inserted.



FIG. 4 is a flow chart 400 showing another method for providing advertising content in a mobile-initiated USSD session by inserting a short text into a USSD message. In a first step 402, a mobile user sends a message to a USSD server requesting the balance of her account. For example, the mobile user may be operating a cell phone and using that cell phone to send a USSD message. In a next step 404, the USSD server forwards that message to the appropriate service provider. In a next step 406, the service provider sends a reply message to the USSD server. The reply message might state the balance of her account and present her with the options of 1: Refill and 2: Manage account. In a next step 408, the USSD server inserts an advertising message into the reply message. That advertising message might comprise a third option such as 3: Win a free vacation.


Continuing in a next step 410, the USSD server forwards the (modified) reply message to the mobile user. In a next step 412, the mobile user sends a message to the USSD server requesting to view the full text of the advertisement. In a next step 414, the USSD server displays the full text of the advertisement to the mobile user. In a next step 416, the mobile user sends a message to the USSD server requesting to leave the advertisement.


Continuing in a next step 418, the USSD server forwards the original reply message to the mobile user. In a next step 420, the mobile user selects an option from the reply message. For example, the mobile user might select option 1: Refill. In a next and final step 422, the mobile user sends the appropriate message to the USSD server, which then forwards that message to the service provider.



FIG. 5 is a flow chart 500 showing another method for providing advertising content in a mobile-initiated USSD session by temporarily diverting that session toward an advertisement sub-session. In a first step 502, a mobile user sends a message to a USSD server requesting the balance of her account. For example, the mobile user may be operating a cell phone and using that cell phone to send a USSD message. In a next step 504, the USSD server forwards that message to the appropriate service provider. In a next step 506, the service provider sends a reply message to the USSD server. The reply message might state the balance of the mobile user's account and present the mobile user with the options 1: Refill and 2: manage account. In a next step 508, the USSD server forwards that reply message to the mobile user.


Continuing in a next step 510, the mobile user sends a message to the USSD server requesting to refill her account. In a next step 512, the USSD server forwards that message to the service provider. In a next step 514, the service provider sends a reply message to the USSD server. The reply message might prompt the mobile user to select the amount by which her account is to be refilled, and might present the mobile user with several options from which to select. In a next step 516, the USSD server sends an advertisement to the mobile user, thereby diverting the USSD session to an advertising sub-session. In a next step 518, the mobile user sends a message to the USSD server requesting to leave the advertisement.


Continuing in a next step 520, the USSD server sends the pending reply message to the mobile user. In a next and final step 522, the mobile user sends a message to the USSD server, which then forwards that message to the service provider. That message might select the option of refilling the user's account in the amount 10 euros.



FIG. 6 is a flow chart 600 showing a method for providing advertising content in a network-initiated USSD session the main purpose of which is the delivery of an advertisement. In a first step 602, a mobile user sends a message to a USSD server requesting the balance of her account. For example, the mobile user may be operating a cell phone and using that cell phone to send a USSD message. In a next step 604, the USSD server forwards that message to the appropriate service provider. In a next step 606, the service provider sends a reply message to the USSD server. The reply message might state the balance of her account and present her with the options of 1: Refill and 2: Manage account. In a next step 608, the USSD server forwards that reply message to the mobile user.


Continuing in a next step 610, the mobile user hangs up, thereby terminating the USSD session. In a next step 612, the USSD server initiates an advertisement and sends that advertisement to the mobile user. That advertisement may present the mobile user with such options as 1: Learn more and 2: Marketing preferences. In a next step 614, the mobile user selects an option such as option 1 from that advertisement. In a next and final step, the mobile user sends a message such as option 1 to the USSD server.



FIG. 7 is a diagram 700 illustrating a communication network for providing advertisements to mobile device users in accordance with the present invention. Mobile devices 702 are connected to a mobile network 704, which in turn is connected to a USSD server 706. The USSD server 706 is also connected to various service providers such as 712.


The USSD server is also connected to a database 708 that contains several types of information pertaining to advertising through USSD. The USSD server is also connected to an advertiser server 710, which permits advertisers to place advertisements with the mobile operator for inclusion on the USSD server and subsequent delivery to mobile users.


The interaction between the mobile devices, the USSD server, and the service providers are detailed above in the descriptions of FIGS. 1 through 6.



FIG. 8 is a pictorial image of the database 708 referenced in FIG. 7. The database 802 contains several types of information, including 810 mobile users who have requested that their service not be interrupted by advertisements; 820 service providers who have requested that their services not be interrupted by advertisements; and 830 responses of mobile users to previous advertisements, which are used for billing purposes. In one previously mentioned embodiment of the present invention, the USSD server logs the responses of type 830 to the database and checks the database for requests of types 810 and 820 before deciding whether to send advertisements to mobile users. The database 802 may also contain 840 marketing preferences supplied by mobile users, 850 lists of advertisers that have been blacklisted by service providers, and 860 lists of service providers that have been blacklisted by advertisers. The database 802 is connected to a database manager 804 and to the USSD server 706 (not shown). The database manager 804 writes information to the database 802 and reads information from that database 802.



FIG. 9 is a pictorial image of the advertiser server 710 referenced in FIG. 7. The advertiser server 710 includes an advertising database 904 that is connected to an advertising manager 902. The advertising database 904 contains such information as the text of advertising messages to be provided to mobile device users, criteria to be used in the selection of USSD messages into which advertising content is to be inserted, and criteria to be used in the selection of advertising content to be inserted into selected USSD messages. The advertising database 904 may also contain some of the information contained in database 802. The advertising manager 902 writes data into the advertising database 904 and reads data from that database 904.



FIG. 10 is a pictorial image of the USSD server 706 referenced in FIG. 7. The USSD server 706 contains several types of software, including 1010 software for routing USSD messages between mobile users and service providers, 1020 software for monitoring USSD message traffic between mobile users and service providers, 1030 software for inserting advertisements into USSD messages, 1040 software for inserting advertisement sub-sessions into USSD sessions, and 1050 software for delivering advertisements with network-initiated USSD sessions.


In addition to the above mentioned examples, various other modifications and alterations of the invention may be made without departing from the invention. Accordingly, the above disclosure is not to be considered as limiting and the appended claims are to be interpreted as encompassing the true spirit and the entire scope of the invention.

Claims
  • 1. A process for providing an advertisment to a mobile device wherein the improvement comprises inserting an advertisement into a USSD message.
  • 2. A process for providing an advertisment to a mobile device wherein the improvement comprises inserting an advertisement sub-session into a USSD session.
  • 3. A process for providing an advertisment to a mobile device wherein the improvement comprises delivering an advertisement with a network-initiated USSD session.
  • 4. A process for inserting an advertisement into a USSD message, comprising the steps of: a) processing message traffic between a service provider and a mobile user;b) identifying said service provider and said mobile user;c) selecting a message to be sent by said service provider to said mobile user;d) deciding whether it is appropriate to insert an advertisement into said message;e) if it is appropriate to insert an advertisement into said message, selecting an advertiser and an advertisement to be inserted into said message;f) transcoding said advertisement so that it uses the same character set as said message;g) modifying said message by inserting said transcoded advertisement;h) forwarding said modified message to said mobile user;i) storing information about said modification, so that it is possible to determine later whether said mobile user's response to said modified message is a response to the original USSD message or a response to said advertisement;j) depending on said mobile user's response, either proceeding with the original USSD session, or diverting that session to a sub-session related to said advertisement, said sub-session comprising one or more USSD messages from said advertiser and one or more USSD responses from said mobile user.
  • 5. A process for inserting an advertisement sub-session into a USSD session, comprising the steps of: a) processing message traffic between a service provider and a mobile user;b) identifying said service provider and said mobile user;c) deciding whether it is appropriate to display advertisements in said USSD session;d) selecting times during said USSD session when it is appropriate to insert advertisements;e) selecting an advertiser and an advertisement to be inserted into said USSD session;f) diverting said USSD session to an advertisement sub-session, said sub-session comprising one or more USSD messages from said advertiser and one or more USSD responses from said mobile user;
  • 6. A process for delivering an advertisement with a network-initiated USSD session, comprising the steps of: a) selecting an appropriate time for delivering advertisements to a mobile user;b) selecting an advertiser and an advertisement to be delivered to said mobile user;c) triggering a network-initiated USSD session;d) delivering said advertisement to said mobile user.
  • 7. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement comprises detecting that a mobile user has just completed a mobile-initiated USSD session.
  • 8. The process of claim 6, comprising the additional step of causing the mobile device to ring or vibrate prior to triggering said USSD session by initiating a short voice call to said mobile user.
  • 9. The process of claim 6, comprising the additional step of causing the mobile device to ring or vibrate prior to triggering said USSD session by sending a Short Message to said mobile user.
  • 10. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user has just completed a voice call by monitoring Call Detail Records generated by Mobile Switching Centers (MSCs).
  • 11. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user has just completed a voice call by monitoring CAMEL transactions between MSCs and SCPs.
  • 12. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user has just sent a Short Message by monitoring CAMEL transactions between MSCs and SCPs.
  • 13. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user has just sent a Short Message by monitoring GSM MAP MO-ForwardSM messages between MSCs and Short Message Service Centers.
  • 14. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user is engaged in a WAP session or has just completed a WAP session by monitoring WAP traffic between said mobile user and the WAP gateway.
  • 15. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user is engaged in a WAP session or has just completed a WAP session by monitoring WAP traffic between the WAP gateway and the WAP service providers.
  • 16. The process of claim 6, wherein the step of selecting the most appropriate time to deliver an advertisement includes detecting that said mobile user is engaged in a WAP session or has just completed a WAP session by requiring WAP service providers to generate a notification event when a user accesses a WAP service.
  • 17. The process of claim 6, wherein the step of selecting said advertiser and said advertisement depends on the specific WAP service that said mobile user has just accessed.
  • 18. The process of claim 4, comprising the additional step of logging to a database how said mobile user has responded to said advertisement, so that the mobile operator can later bill the advertiser and/or compensate the service provider.
  • 19. The process of claim 5, comprising the additional step of logging to a database how said mobile user has responded to said advertisement, so that the mobile operator can later bill the advertiser and/or compensate the service provider.
  • 20. The process of claim 6, comprising the additional step of logging to a database how said mobile user has responded to said advertisement, so that the mobile operator can later bill the advertiser and/or compensate the service provider.
  • 21. The process of claim 7, comprising the additional step of logging to a database how said mobile user has responded to said advertisement, so that the mobile operator can later bill the advertiser and/or compensate the service provider.
  • 22. The process of claim 4, wherein the decision to insert an advertisement into a USSD message depends on the length of said USSD message, the length of said advertisement, and the maximum allowable length of a USSD message.
  • 23. The process of claim 4, wherein the decision to display an advertisement comprises the step of looking-up in a database whether said mobile user has requested not to receive advertisements.
  • 24. The process of claim 5, wherein the decision to display an advertisement comprises the step of looking up in a database whether said mobile user has requested not to receive advertisements.
  • 25. The process of claim 6, wherein the decision to display an advertisement comprises the step of looking up in a database whether said mobile user has requested not to receive advertisements.
  • 26. The process of claim 4, wherein the decision to display an advertisement comprises the step of looking-up in a database whether said service provider has requested that its service should not be interrupted by advertisements;
  • 27. The process of claim 5, wherein the decision to display an advertisement comprises the step of looking up in a database whether said service provider has requested that its service should not be interrupted by advertisements.
  • 28. The process of claim 4, wherein the step of selecting an advertiser and an advertisement comprises the step of using keywords or similar information that said service provider explicitly attaches to its messages.
  • 29. The process of claim 4, wherein the step of selecting an advertiser and an advertisement comprises the step of automatically detecting words in the USSD message.
  • 30. The process of claim 4, wherein the step of selecting an advertiser and an advertisement comprises the step of detecting the brand and model of the mobile device that is being used.
  • 31. The process of claim 4, wherein the step of selecting an advertiser and an advertisement comprises the step of looking up, in a database, marketing preferences previously supplied by said mobile user.
  • 32. The process of claim 4, wherein the step of selecting an advertiser and an advertisement comprises the step of looking up, in a database, a list of advertisers or categories of advertisers that said service provider has blacklisted.
  • 33. The process of claim 4, wherein the step of selecting an advertiser and an advertisement comprises the step of looking up, in a database, a list of service providers or categories of service providers that said selected advertiser has blacklisted.
  • 34. The process of claim 5, wherein the step of selecting an advertiser and an advertisement comprises the step of using keywords or similar information that said service provider explicitly attaches to its messages.
  • 35. The process of claim 5, wherein the step of selecting an advertiser and an advertisement comprises the step of automatically detecting words in the USSD message.
  • 36. The process of claim 5, wherein the step of selecting an advertiser and an advertisement comprises the step of detecting the brand and model of the mobile device that is being used.
  • 37. The process of claim 2, wherein the step of selecting an advertiser and an advertisement comprises the step of looking up, in a database, marketing preferences previously supplied by said mobile user.
  • 38. The process of claim 5, wherein the step of selecting an advertiser and an advertisement comprises the step of looking up, in a database, a list of advertisers or categories of advertisers that said service provider has blacklisted.
  • 39. The process of claim 5, wherein the step of selecting an advertiser and an advertisement comprises the step of looking up, in a database, a list of service providers or categories of service providers that said selected advertiser has blacklisted.
  • 40. The process of claim 4, wherein one or more steps are performed off-line and the results are stored in a database until said mobile user accesses the USSD service.
  • 41. The process of claim 5, wherein one or more steps are performed off-line and the results are stored in a database until said mobile user accesses the USSD service.
  • 42. The process of claim 5, wherein the step of selecting a time when it is appropriate to insert a sub-session comprises the operation of detecting specific markers that service providers insert in their messages to indicate suitable times for advertisements.
  • 43. The process of claim 5, wherein the step of selecting a time when it is appropriate to insert a sub-session comprises the operation of detecting messages which indicate the end of a USSD session, and postponing the closing of said session.
  • 44. The process of claim 5, wherein the step of selecting a time when it is appropriate to insert a sub-session comprises the operation of detecting transitions, within a USSD session, from one service provider to another service provider.
  • 45. A system for providing advertisements to users of mobile devices comprising a GSM SCP, GSM SCF, USSD gateway, USSD Service Center, USSD service portal or similar server.
  • 46. A database, including: information about mobile users who have requested that their USSD service not be interrupted by advertisements;information about service providers who have requested that their services not be interrupted by advertisements;information about marketing preferences supplied by mobile users;information about advertisers or categories of advertisers that have been blacklisted by service providers;information about service providers or categories of service providers that have been blacklisted by advertisers; andinformation about responses of mobile users to advertisements.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 60/801,648, filed May 18, 2006, incorporated herein by reference in its entirety.

Provisional Applications (1)
Number Date Country
60801648 May 2006 US