AUTOMATIC EVENT TRIGGERED BALANCE TOP-UP, MONEY TRANSFER, AND LOCATION BASED ADVERTISING PLATFORM

Abstract

This disclosure provides aspects and embodiments of methods, services, and platforms for prompting users with a zero account balance to send a callback message to a contact informing the contact that the user cannot call them and asking the contact to call the user. This disclosure further provides location determining platforms and rewards platforms for users.

Claims

1.-16. (canceled)

17. A computer-implemented method for automatically prompting a user on a mobile device to send a message comprising a request for a funds transfer after a call from the mobile device to a destination address has disconnected, the method comprising: receiving, at a server operably connected to a Mobile Network Operator's network, an indication that a call between the mobile device and a destination address has disconnected; receiving, at the server, an indication that the mobile device has a zero account balance; receiving, at the server, a communication comprising the Mobile Station International Subscriber Directory Number (MSISDN) of the mobile device and the destination address; preparing a first message comprising one or more actionable response options, wherein one of the one or more actionable response options comprises a request for a funds transfer; and sending, from the server, the first message to the mobile device via the MSISDN, whereby the one or more actionable response options are configured to prompt the user.

18. The method of claim 17, further comprising receiving at the server a communication comprising a first actionable response option selected on the mobile device.

19. The method of claim 18, further comprising determining whether the first actionable response option selected on the mobile device was positive or negative.

20. The method of claim 19, further comprising logging the first actionable response option selected on the mobile device.

21. The method of claim 18, further comprising sending from the server a second message comprising a request for a funds transfer to the destination address when the first actionable response option selected on the mobile device comprises a request for a funds transfer.

22. The method of claim 21, further comprising sending a follow-up message to the mobile device, wherein the follow-up message comprises contents that indicate that the first actionable response option selected from the mobile device was received by the server.

23. The method of claim 22, wherein the follow-up message further comprises contents that indicate a request for a funds transfer was sent to the destination address.

24. A computer-implemented method for automatically prompting a user on a mobile device to send a message comprising a request for a funds transfer to a destination address after a call from the mobile device to the destination address has been unsuccessful, the method comprising: receiving, at the processor in the mobile device operably connected to a network, an indication that a call to a destination address has been unsuccessful in connecting the mobile device to the destination address; receiving, at the mobile device, a first message comprising one or more actionable response options, wherein one of the one or more actionable response options comprises an option to send a request for a funds transfer to the destination address; and displaying on a screen of the mobile device the first message, wherein the display of the first message is configured to prompt the user.

25. The method of claim 24, further comprising playing an alert tone when the first message is displayed.

26. The method of claim 24, further comprising launching an application installed on the mobile device, wherein the application causes the first message to be displayed.

27. The method of claim 26, wherein the application is installed on the SIM card of the mobile device, or wherein the application is installed on the operating system of the mobile device.

28. The method of claim 27, further comprising receiving, in the application, a first actionable response option selected on the mobile device.

29. The method of claim 28, further comprising sending to a server a communication comprising the first actionable response option selected on the mobile device.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0061] FIG. 1 is a flowchart illustrating exemplary basic architecture of the platform for ZeroX, LocaXion, and XciteMe.

[0062] FIG. 2 is a graphical overview illustrating the user interface by which a user may add a phone number directly into his or her mobile phonebook via an interactive prompt.

[0063] FIG. 3 is a flowchart illustrating exemplary steps related to a trigger event that will lead to the eventual launching of the ZeroX service.

[0064] FIG. 4 is a flowchart illustrating an exemplary interaction process between a Mobile Operator network and the ZeroX server platform.

[0065] FIG. 5 is a flowchart illustrating an exemplary process of the ZeroX platform sends a command message to a subscriber based on inputs received from the MNO network.

[0066] FIG. 6 is a flowchart illustrating an exemplary process of how the ZeroX application is expressed and interacts with the user device, and thus the user experience.

[0067] FIG. 7 is a flowchart illustrating an exemplary process of how the ZeroX platform updates the database with subscriber preference results, tracking the participation such that the MNO may modify the frequency of campaign depending on subscriber responsiveness.

[0068] FIG. 8 is a flowchart illustrating an exemplary process of how a ZeroX campaign is designed.

DETAILED DESCRIPTION OF THE FIGURES

[0069] FIG. 1 is a flowchart illustrating exemplary basic architecture of the platform supporting the ZeroX, LocaXion, and XciteMe services. In one embodiment, as pictured in FIG. 2, the services utilize the following connectivity structure: Mobile Subscriber A experiences a trigger event. This could be a zero balance event in the case of the ZeroX embodiment, it could be a phone call placed to a specific brand in the XciteMe embodiment, or could be that a subscriber moved into a specific geographic location in the LocaXion embodiment. The trigger event (1) is noted by the Operator Switch, data network, SMSC, billing platform, customer management platform, or HLR (Home Location Registry). The MNO network is in constant communication with the cloud platform (2). This allows for the Mobile Operator Network to notify the platform when a specific trigger event occurs.

[0070] After a trigger event occurs and, subsequently, the required information necessary to trigger a campaign is passed to the platform via an API, the platform processes the information and prepares a campaign message to be sent to a mobile subscriber.

[0071] In one embodiment, the platform is connected to a Mobile Network Operator SMSC (Short Message Service Center) via an SMPP (Short Message Peer-to-Peer) connection (3). Other connection types in other embodiments are also possible. In some embodiments, the platform may also be connected to an MNO's MMSC (MultiMedia Message Service Center). The Operator SMSC forwards the campaign message to Subscriber A's device (4).

[0072] The notification appears on Subscriber A's device, at which point the subscriber selects his or her preferred option. The remote application within Subscriber A's mobile device forwards the response to a designated short code at the Operator SMSC (5). The Operator SMSC receives and forwards the response to the platform in the form of a binary SMS message (6). The platform parses the message and determines an appropriate response to Subscriber A based on Subscriber A's device type and interest in the campaign promotion.

[0073] In the XciteMe and LocaXion embodiments where Subscriber A provided a positive response the promotion, the platform may send a follow-up message back to the subscriber. This could be a standard SMS or, in alternative embodiments, may be additional command messages that initiate a proactive session. These messages would flow through the MNOs SMSC and MMSC respectively (7).

[0074] The Operator SMSC forwards the contact information to the device user (8).

[0075] In the ZeroX scenario where Subscriber A did not have sufficient funds and requested a call back or balance transfer, the cloud prepares an SMS message to Subscriber B (9) and forwards this to the MNO SMSC. The SMSC delivers this message to Subscriber B (10). In other embodiments, this could also be a command message sent to Subscriber B that triggers a remote client application on Subscriber B's device. Subscriber B would then experience an interactive prompt and could reply to Subscriber A via the ZeroX service, or initiate a secure funds transfer.

[0076] FIG. 2 showcases the user interface a mobile consumer would see when the ZeroX service triggers and displays prompts to the consumer after an attempted phone call where the user had no balance. In other embodiments, the service could also trigger when the user attempts to initiate a data session or when attempting to send an SMS or MMS without sufficient funds.

[0077] An attempted phone call is placed from Subscriber A to another mobile subscriber, Subscriber B. The call is not connected because Subscriber A does not have sufficient balance. In one embodiment, immediately after the phone call ends, a tone is played by the mobile device, and an interactive prompt displays as exemplified by stage 100. The text displayed to the calling party is fully configurable by Mobile Network Operator. In this embodiment, Subscriber A is notified that he has a zero balance, and is asked if he would like to send a free message to Subscriber B.

[0078] In the embodiment where the mobile user interacts with the campaign message and chooses to accept the offer, a second selection can be displayed to the subscriber as shown in stage 105. At this stage, Subscriber A has the option of choosing to have Subscriber B call him back, or alternatively can send a request to Subscriber B to transfer funds.

[0079] In an embodiment where Subscriber A chooses to send a call-me-back message to Subscriber B, Subscriber B receives a notification as exemplified in stage 110. Subscriber A's name is included in the message so that the notification is personalized. The time and date the attempted call was made are also included: [0080] Hi, it's Chris Jones [0081] I tried to call at 10:31 on 04/12/13 but I don't have any balance left. [0082] Please call me back. [0083] Sent using ZeroX

[0084] FIG. 3 is a flowchart illustrating the steps related to a trigger event that will lead to the eventual launching of the ZeroX service. In stage 305, a subscriber (Subscriber A) with a zero balance or with low funds attempts to utilize the mobile network. In one embodiment, a subscriber may attempt to make a phone call to another subscriber. In other embodiments, the subscriber may attempt to send an SMS or MIMS or other data communication to another mobile subscriber. At stage 310, the network detects that Subscriber A in stage 305 has insufficient funds to complete the call or message initiated. The network disconnects the call or refuses the SMS messages at stage 315. This series of events triggers the ZeroX service, as outlined in FIG. 4.

[0085] FIG. 4 is a flowchart illustrating the Mobile Operator Network as it would interact with the ZeroX server platform. At stage 405, the mobile phone call placed by Subscriber A is terminated by the network. The mobile operator informs the ZeroX platform that a zero balance communication was attempted at stage 410. This notification could happen via an API, via web services, or via SMS communication where the MNO forwards an SMS to the ZeroX platform with details necessary to trigger the ZeroX service. The time, date, and MSISDN (Mobile Station International Subscriber Directory Number) of the subscriber with no balance is forwarded to the ZeroX platform at stage 415. In some embodiments, the MNO network may also forward an additional ID to indicate if the subscriber had no balance or merely insufficient funds for the communication attempted. In this embodiment, Subscriber A's MSISDN is identified as the OA (Originating Address). The mobile subscriber called is known as the DA (Destination Address). The MNO network also forwards the DA to the ZeroX platform in stage 415.

[0086] FIG. 5 is a flowchart illustrating the exemplary process of the ZeroX platform sending a command message to a subscriber based on inputs received from the MNO network. At stage 505, the ZeroX platform receives the communication from the MNO network including the OA and DA. The platform prepares an appropriate command message at stage 510, based on the ID and information obtained from the MNO network. The message is sent to the remote client on Subscriber A's device at stage 515.

[0087] FIG. 6 is a flowchart illustrating the exemplary process of how the ZeroX application is expressed and interacts with the user device, and thus the user experience. At stage 605, the message is received and processed by the remote client application. In some embodiments, the client application may perform an ICCID security check to ensure that the ICCID within the command message issued by the platform matches the ICCID reported by the SIM (Subscriber Identity Module) card in the subscriber's device. In some embodiments, the client application may also perform a roaming check to determine if the mobile user is within his home network. A command check to determine that the device is able to support the issued command can also be included. After all checks are complete, the application triggers at stage 610. In some embodiments, the application can be configured to play an alert tone on the subscriber's device at stage 615. Subsequently, the remote client can display text to the mobile subscriber directly on the device screenthe user does not need to navigate into an SMS inbox or open an application to view the notification. The text displayed to the user is fully configurable in stage 620, and is defined at the platform level. In exemplary embodiment, the mobile user is notified that he does not have sufficient balance to complete his call or send a message to an intended recipient: [0088] You have a zero balanceyour message cannot be sent. Select OK to send a free message to your friend asking them to call you back!

[0089] At stage 625, the subscriber can choose to send a message to Subscriber B, the original intended recipient. The user experience can be configured to require only a single click response. In the embodiment where a subscriber chooses to send a message to Subscriber B, a response is sent from the remote client to the platform at stage 630. The response includes the phone number of the Subscriber B. If the user chooses not to send a message, a response is sent back to the server at stage 640 indicating the user's preference.

[0090] FIG. 7 is a flowchart illustrating the exemplary process of how the ZeroX platform updates the database with subscriber preference results, tracking the participation such that the MNO may modify the frequency of campaign depending on subscriber responsiveness.

[0091] At stage 705, Subscriber A's selected response to the ZeroX prompt is received at the platform. In stage 710, the server processes the response and determines if the subscriber indicated a positive or negative response. If Subscriber A did not wish to send a ZeroX message to Subscriber B, the platform logs his response for further analysis as indicated at stage 715. If Subscriber A chose to send a ZeroX message to Subscriber B, his response is logged at the platform in stage 720. The platform then creates a message to be sent to Subscriber B. In one exemplary embodiment, the message may state: [0092] Hi, it's Chris Jones. I tried to call at 10:31 on 04/12/15 but I don't have any balance left. Please call me back. [0093] Sent using ZeroX

[0094] In one embodiment, the platform may be configured to send a follow-up message to Subscriber A at stage 725. This is a configurable message, and could be utilized to inform Subscriber A that a ZeroX message was sent on his behalf: [0095] Your call me back request has been sent to 6171234567.

[0096] FIG. 8 is a flowchart illustrating the exemplary process of how a ZeroX campaign is designed. At stage 805, the campaign is defined within the server. This includes the days and times during which the campaign will be relevant. Specific geographic regions can also be configured. At stage 810, trigger events after which the campaign should launched are defined. Next, during stage 815, the actual campaign text that will be shown to a calling party is defined. In stage 825, configurable counters and rules for the campaign are set. In one embodiment, this could include the number of times a specific unique mobile subscriber, as defined by his MSISDN, is prompted to send a ZeroX message after attempting to utilize the MNO network with a zero balance.

EQUIVALENTS

[0097] It is to be understood that the foregoing description is intended to illustrate and not limit the scope of the invention, which is defined by the scope of the appended claims. Those skilled in the art will recognize, or be able to ascertain, using no more than routine experimentation, numerous equivalents to the specific embodiments described specifically in this disclosure. Such equivalents, and other aspects, advantages, and modifications are within the scope of the following claims.