HK1135200B - Platform for managing mobile domains and keyword-activated applications - Google Patents

Description

Platform for managing mobile domains and keyword-enabled applications

Cross Reference to Related Applications

This application claims priority to indian application No.587/KOL/2006, filed on 14.6.2006, which is incorporated herein by reference.

Technical Field

The present invention relates to mobile device communications, and more particularly to enabling a subscriber to manage user interaction with a mobile domain based on at least one text message keyword.

Background

In today's global society, businesses typically operate every day, all day long, to provide consumers with access to their supplies. Recent technological advances have provided consumers with considerable flexibility in where and in what manner they purchase products and services. For example, consumers and businesses can communicate through wired or wireless telephones (voice), websites, emails, text messages, instant messages, faxes, and the like. In addition, many consumers often employ keyword online search engines to investigate information about products and services of interest. The results of these searches typically generate a list of relevant product/service information, such as model, price, storage location, reviews, and vendors. In addition, most search engine companies enable online vendors to pay for significant placement of particular keywords in search results.

Many larger and medium businesses provide access via the internet to online websites or portals about the services and goods they provide, e.g., www. While many smaller businesses sell products and services to consumers who often access information online, these smaller businesses are often not burdened with maintaining an online presence. However, small businesses typically may access their customers through one or more communications means, such as wired and/or wireless telephone, facsimile, text messaging, and the like.

Drawings

Non-limiting and non-exhaustive embodiments of the present invention are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified.

FIG. 1 illustrates an exemplary operating environment;

FIG. 2 illustrates one embodiment of a mobile device;

FIG. 3 illustrates one embodiment of a network device;

FIG. 4 is a block diagram illustrating an overview of a mobile domain platform;

FIG. 5 is a flow diagram illustrating a process for a subscriber to select, register, and define the disposition of a mobile domain keyword;

FIG. 6 is a flow diagram showing a process for handling a text message including registered mobile domain keywords;

FIG. 7 is a flowchart illustrating processing for a received text message that includes a registered mobile domain keyword; and

fig. 8 is a flowchart illustrating a process of interactive and non-interactive applications processing registered mobile domain keywords included in a text message received from a user according to the present invention.

Detailed Description

The present invention now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments by which the invention may be practiced. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. The invention may be embodied as, among other things, methods, processes, systems, business methods, or apparatus. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.

The present invention relates generally to methods and systems for providing a mobile domain platform for subscribers (e.g., businesses, institutions, advertising agencies, partners, providers, individuals, businesses, etc.) to offer text message-based campaigns to new or potential customers (users). A subscriber can create a mobile domain by selecting and registering at least one available keyword with a mobile domain platform for subsequent processing of a text message sent to the platform that includes one or more registered keywords. Further, the subscriber may register one or more keywords as a root (root) of the mobile domain, such that subsequent text messages (a combination of the root keyword plus one or more other predetermined keywords) sent to the mobile domain platform that include additional alphanumeric text strings may be automatically processed, thereby enabling one or more different actions. The mobile domain keyword is generally composed of one or more alphanumeric characters and may be any of a word, phrase, abbreviation, character, and the like.

The mobile domain platform enables a subscriber to define rules, events and/or conditions to be applied by one or more definitions to process text messages sent to a mobile number corresponding to the platform, and the messages include one or more registered keywords. The processing of text message keywords is generally defined by the subscriber, but may also be performed according to one or more default rules provided by the mobile domain platform.

Examples of application processing may include: aggregating answers in the form of text messages to a poll created by the subscriber, or identifying one of the plurality of subscribers that provides the best bid to the mobile domain platform to register a popular keyword such as "pizza". One or more delivery actions are pre-identified by the subscriber for each application corresponding to one or more registered keywords included in the received text message. Examples of these delivery actions may include providing a user message to a subscriber through one or more of an email, a fax, an alarm, a daily digest, a Simple Syndication (RSS) feed, a telephone call, a File Transfer Protocol (FTP), a Short Message Service (SMS), a Multimedia Message Service (MMS), a chat, a web page update, etc. The individual delivery actions may be individually configured by the subscriber based on different factors such as priority and criticality. Further, delivery actions may be provided by the mobile domain platform to the subscriber at different price points based on different factors, such as quality, geography, pricing plans, time, date, holidays, promotions, weather, and the like.

For example, if a subscriber is currently registered to take control of the keyword "pizza" as a root, a text message to the mobile domain platform that includes the word "buy pizza" may be automatically delivered to the subscriber's customer service personnel in real-time through one or more delivery actions as a high priority sales guide (sales lead). In contrast, text messages including the word "pizza address" may be periodically processed in a batch mode and delivered to the subscriber's customer service personnel through a relatively low cost delivery mechanism as an hourly or daily digest of informational queries.

In addition, the subscriber may gain control over registration of keywords for the mobile domain in one or more ways. For example, in one embodiment, several subscribers may bid for controlling various instances of text messages received by the mobile domain platform that contain highly popular and relatively common keywords (e.g., "pizzas"). In this manner, the received text message will then be processed using the mobile domain platform according to one or more applications and one or more delivery actions preconfigured by the highest bidding subscriber. In other embodiments, a subscriber may bid for exclusive control of all text messages over a period of time (e.g., days, months, etc.) that include a particular keyword associated with a campaign such as a poll, advertisement, request fulfillment, etc.

In yet another embodiment, the subscriber may dynamically bid on registering an available keyword with a predetermined amount of funds over a particular period of time. For example, a subscriber may provide $10,000 to the platform to dynamically bid on a particular keyword over a period of one month, further defining that no more than $334 may be spent a day and that this amount may only be spent during particular days and hours (e.g., the days and hours that the subscriber is open to business).

In addition, if the operator of the mobile domain platform is made aware that a particular keyword is also a trademark of a potential or existing subscriber, the operator may choose to only make that keyword registerable with the mobile domain platform by the trademark holder.

In at least one embodiment, the text message having the registered keyword is transmitted via a short code mobile number (short code mobile number) corresponding to the mobile domain platform. Short code mobile numbers typically include four or five digits, e.g., 8243 or 92466. In addition, the user may send a text message from a wireless/mobile device such as a personal computer or a wired device to a short code mobile number corresponding to the mobile domain platform. However, the mobile domain platform is not so limited as it may also be configured to process text messages received from non-short code mobile numbers, email addresses, Instant Messaging (IM) handling, simple syndication (RSS) feeds, File Transfer Protocol (FTP), Short Message Service (SMS), Multimedia Messaging Service (MMS), chat, and the like. In general, the mobile domain platform may be configured to process received text messages that include one or more particular keywords with one or more applications, interactions, and delivery actions predefined by the subscriber (who is currently registered with the platform to control the one or more mobile domain keywords).

In one exemplary embodiment, the user may send a text message including the mobile domain keyword "buy pizza" to the short code mobile number "8243". The mobile domain platform will process the text message and deliver its content and user information to the currently registered subscribers for the "pizza" mobile domain keyword in real time. In a substantially similar manner, in response to a text message that includes the keyword "poll," the mobile domain platform may enable a predefined application to process the message and aggregate its content with the content of other text messages that also include the mobile domain keyword "poll. These aggregated results will then be delivered in a predetermined manner to the subscriber currently controlling the registration of the keyword "poll".

In one embodiment, the mobile domain keyword and short code mobile number information is provided in a list along with other results of the online search. In part because this information can be provided as an online search result, subscribers who do not have an interactive online residence can gain access to those users who do have online capabilities. In another embodiment, such mobile domain keyword and short mobile code number information may be made available in the form of printed publications such as newspapers, magazines, books, flyers, or advertisements. In still other embodiments, such information may be communicated to the consumer/user through a video display, movie, picture, or announcement. Further, listed directly below is an exemplary list of mobile domain keywords and short code mobile number information that may be provided to a user.

To get an application for this law practice, please send a text message with "apply for law" to 8243. "

In one embodiment, the list of keyword and short code information may be provided by the subscriber in the form of a printed publication, while in another embodiment, the mobile domain platform may enable this information to be included in the results of the user's online search for the programmer's work.

Instantiating an operating Environment

FIG. 1 illustrates the components of one embodiment of a network environment in which the present invention may be implemented. Not all of these components may be required to practice the invention, and variations in the configuration and type of these components may be made without departing from the spirit or scope of the invention. As shown, system 100 of FIG. 1 includes Local Area Network (LAN)/Wide Area Network (WAN) - (network) 105, wireless network 110, mobile domain platform 106, mobile device (client device) 102, and client network device 101.

One embodiment of the mobile device 102 and 103 is described in more detail below in conjunction with fig. 2. In general, however, the mobile device 102 and 104 may comprise virtually any portable computing device capable of receiving and sending messages via a network, such as the network 105, the wireless network 110, and so forth. The mobile device 102 and 104 may also be generally described as a client device configured to be portable. Thus, the mobile device 102 and 104 can include virtually any portable computing device capable of connecting to another computing device and receiving information. Such devices include portable devices such as cellular telephones, smart phones, display pagers, Radio Frequency (RF) devices, Infrared (IR) devices, Personal Digital Assistants (PDAs), handheld computers, laptop computers, wearable computers, tablet computers, integrated devices combining one or more preceding devices, and the like. Thus, the mobile device 102 and 104 typically vary widely in capabilities and features. For example, a cell phone may have a numeric keypad and a few lines of monochrome LCD display on which only text may be displayed. In another example, a web-enabled mobile device may have a touch sensitive screen, a stylus (stylus), and several lines of color LCD display in which both text and graphics may be displayed.

Web-enabled mobile devices may include a browser application configured to receive and transmit Web pages, Web-based messages, and the like. The browser application may be configured to receive and display graphics, text, multimedia, and the like, using virtually any web-based language, including wireless application protocol messages (WAP), and the like. In one embodiment, the browser application is enabled to employ Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, standard generalized markup language (SMGL), hypertext markup language (HTML), extensible markup language (XML), and the like, to display and send messages.

The mobile device 102 may also include at least one other client application configured to receive content from another computing device. The client application may include the ability to provide and receive textual content, graphical content, audio content, and the like. The client application may also provide information identifying itself, including type, capabilities, name, and the like. In one embodiment, the mobile devices 102 and 104 may uniquely identify themselves through any of a variety of mechanisms, including a telephone number, a Mobile Identification Number (MIN), an Electronic Serial Number (ESN), or other mobile device identifier. Such information may also indicate content formats that the mobile device is capable of employing. The message may be provided in a message or the like, sent to mobile domain platform 106, client network device 101, or other computing device.

Mobile device 102 may also be configured to communicate messages between another computing device, such as mobile domain platform 106, client network device 101, etc., for example, via Short Message Service (SMS), Multimedia Message Service (MMS), Instant Message (IM), online chat (IRC), irdc (mrrc) of Mardam-Bey, Jabber, etc. However, the present invention is not limited to these message protocols, and almost any other message protocol may be employed.

The mobile device 102 can also be configured to enable the user to participate in a communication session, such as an IM session. As such, the mobile device 102 may include a client application configured to manage various actions on behalf of the client device. For example, the client application may enable a user to interact with a browser application, an email application, an IM application, an SMS application, and the like.

Mobile device 102 may also be configured to include a client application that enables an end user to log into an end user account that may be managed by another computing device, such as mobile domain platform 106. The end-user account may be configured, for example, to enable the end-user to receive emails, send/receive IM messages, SMS messages, access selected web pages, and the like.

Client network device 101 may include virtually any computing device capable of communicating via a network to send and receive information, and the like. Combinations of such devices may include devices that typically connect using a wired or wireless communications medium such as personal computers, multiprocessor systems, wearable computers, microprocessor-based or programmable consumer electronics, network PCs, and the like.

The wireless network 110 is configured to couple the mobile device 102 and its components 104 with the network 105. The wireless network 110 may include any of a variety of wireless sub-networks that may also overlay stand-alone ad-hoc networks and the like to provide an infrastructure-oriented connection for the mobile device 102 and 104. Such subnetworks may include mesh networks, wireless lan (wlan) networks, cellular networks, and the like.

Wireless network 110 may also include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links, and the like. These connectors may be configured to move freely and randomly and organize themselves arbitrarily so that the topology of wireless network 110 may change rapidly.

Wireless network 110 may also employ a variety of access technologies including second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), radio access to cellular systems, WLAN, WiMAX, Wireless Router (WR) mesh, and the like. Access technologies such as 2G, 3G, 4G, 5G, and future access networks may enable wide area coverage for mobile devices with various degrees of mobility, such as mobile device 102 and 104. For example, the wireless network 110 may enable radio connections accessed through radio networks such as global system for mobile communications (GSM), General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (WCDMA), CDMA2000, Universal Mobile Telecommunications Service (UMTS), and so forth. In essence, the wireless network 110 can include virtually any wireless communication mechanism by which information can travel between the mobile device 102 and 104 and another computing device, network, and the like.

Network 105 is configured to couple mobile domain platform 106 and its components with other computing devices including mobile device 102 and 104, client network device 101, and to couple mobile domain platform 106 and its components with mobile device 102 and 104 through wireless network 110. The network 105 is enabled to employ any form of computer-readable media to transfer information from one electronic device to another. In addition to a Local Area Network (LAN), a Wide Area Network (WAN), the network 105 may include the internet, a direct connection, such as through a Universal Serial Bus (USB) port, other forms of computer readable media, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. Further, the communication links within a LAN typically comprise twisted wire pairs or coaxial cable, while the communication links between networks may utilize analog telephone lines, full or partial dedicated digital lines (including T1, T2, T3, and T4), Integrated Services Digital Networks (ISDN), Digital Subscriber Lines (DSL), wireless links including satellite links, or other communication links known to those skilled in the art. In addition, remote computers and other related electronic devices can be remotely connected to either LANs or WANs via a modem and temporary telephone line. In essence, network 105 includes any communication method by which information may travel between mobile domain platform 106, client network device 101, and other computing devices.

In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave, data signal, or other transport mechanism and includes any information delivery media. The terms "modulated data signal" and "carrier-wave signal" includes a signal that has one or more of its characteristics set or changed in such a manner as to encode information, instructions, data, and the like, in the signal. By way of example, communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media.

One embodiment of the mobile computing platform 106 will be described in more detail below with reference to FIG. 4. Briefly, however, mobile computing platform 106 may comprise any computing device capable of connecting to network 105 to enable communication with mobile device 102 and client network device 101.

Computing devices that may enable the mobile computing platform 106 include personal computers desktop computers, multiprocessor systems, multiprocessor-based or programmable consumer electronics, network PCs, servers, network appliances, and the like.

Although FIG. 1 illustrates mobile computing platform 106 as a single computing device, the invention is not so limited. For example, as shown in fig. 3, one or more functions of platform 106 may be distributed across one or more different network devices.

Instantiating a mobile device

FIG. 2 illustrates one embodiment of a mobile device 200 that may be included in a system implementing the invention. Mobile device 200 may include many more or fewer components than those shown in fig. 2. The components shown, however, are sufficient to disclose an illustrative embodiment for practicing the present invention. The mobile device 200 may represent, for example, the mobile device 102 and 104 of fig. 1.

As shown, mobile device 200 includes a processing unit (CPU)222 in communication with a mass memory 230 via a bus 224. Mobile device 200 also includes a power supply 226, one or more network interfaces 250, an audio interface 252, a display 254, a keypad 256, an illuminator 258, an input/output interface 260, a haptic interface 262, and an optional Global Positioning System (GPS) receiver 264. Power supply 226 provides power to mobile device 200. Rechargeable or non-rechargeable batteries may be used to supply power. It may also be powered by an external power source that supplements and/or recharges the battery, such as an AC adapter or power dock (power docking cradle).

Mobile device 200 may optionally communicate with a base station (not shown), or directly with another computing device. Network interface 250 includes circuitry for coupling mobile device 200 to one or more networks and is constructed for use with one or more communication protocols and technologies including, but not limited to, global system for mobile communications (GSM), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), User Datagram Protocol (UDP), transmission control protocol/internet protocol (TCP/IP), SMS, General Packet Radio Service (GPRS), WAP, Ultra Wideband (UWB), IEEE 802.16, Worldwide Interoperability for Microwave Access (WiMAX), SIP/RTP, or any of a variety of other wireless communication protocols. Network interface 250 is sometimes referred to as a transceiver, transceiving device, or Network Interface Card (NIC).

Audio interface 252 is configured to generate and receive audio signals such as human voice sounds. For example, audio interface 252 may be coupled with a speaker and microphone (not shown) to enable telecommunication with others and/or generate audio acknowledgements for certain actions. Display 254 may be a Liquid Crystal Display (LCD), gas plasma, Light Emitting Diode (LED), or any other type of display used in conjunction with a computing device. Display 254 may also include a touch sensitive screen configured to receive input from an object such as a stylus or digits from a human hand.

Keypad 256 may include any input device configured to receive input from a user. For example, keypad 256 may include a push button numeric dial, or a keyboard. Keypad 256 may also include command buttons associated with selecting and sending images. Illuminator 258 may provide status indications and/or provide lighting. Illuminator 258 may remain active for a particular period of time or in response to an event. For example, when illuminator 258 is active, the buttons on keypad 256 may be backlit and remain on while the client device is powered up. Further, illuminator 258 may backlight these buttons in various forms when a particular action is performed (e.g., dialing another client device). Illuminator 258 may also cause light sources located within a transparent or translucent case of the client device to emit light in response to the action.

Mobile device 200 also includes input/output interface 260 for communicating with external devices, such as a headset, or other input or output devices not shown in fig. 2. The input/output interface 260 may utilize one or more communication technologies, such as USB, infrared, Bluetooth^TMAnd the like. Haptic interface 262 is configured to provide haptic feedback to a user of the client device. For example, the haptic interface may be used to vibrate the mobile device 200 in a particular manner when another user of the computing device is calling.

Optional GPS transceiver 264 can determine the physical coordinates of mobile device 200 on the surface of the earth, which typically outputs a location as latitude and longitude values. GPS transceiver 264 can also employ other geolocation mechanisms including, but not limited to, triangulation, Assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS, etc. to further determine the physical location of mobile device 200 on the surface of the earth. It is to be appreciated that in various instances, GPS transceiver 264 can determine the physical location of mobile device 200 within millimeters; while in other cases the determined physical location may be less accurate, such as in meters or significantly greater distances. However, in one embodiment, the mobile device may provide other information, including, for example, a MAC address, an IP address, etc., through other components that may be used to determine the physical location of the device.

Mass memory 230 includes RAM 232, ROM 234, and other storage devices. Mass memory 230 is shown for storing data structures such as computer readable instructions, data structures, program modules orOther examples of computer storage media for information such as data. Mass memory 230 stores a basic input/output system (BIOS)240 for controlling low-level operations of mobile device 200. The mass memory also stores an operating system 241 for controlling the operation of mobile device 200. It will be appreciated that this component may include a version such as UNIX, or LINUX^TMGeneral-purpose operating systems, such as Windows Mobile, or special-purpose clients^TMLike a communication operating system, or SymbianAnd (4) operating the system. The operating system may include or interface with a Java virtual machine module that enables control of hardware components and/or operating system operations via Java application programs.

Memory 230 also includes one or more data stores 244 that can be employed by mobile device 200 to store, among other things, applications 242 and/or other data. For example, data storage 244 may also be employed to store information that describes various capabilities of mobile device 200. This information may then be provided to another device based on any of a variety of events including being sent as part of a header during a communication, being sent upon request, and so forth.

Applications 242 may include computer-executable instructions that, when executed by mobile device 200, transmit, receive, and/or otherwise process text messages, audio, video, and enable remote communication with another user of another client device. Other examples of application programs include calendars, browsers, VOIP applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth. Further, text messaging application 245 may include components for enabling one or more messaging applications including, but not limited to: short Message Service (SMS), Multimedia Message Service (MMS), Instant Messaging (IM), Online chat (IRC), Mardam-Bey's IRC (mIRC), Jabber, Alerts, and the like.

Instantiating a network device

Fig. 3 illustrates one embodiment of a network device, according to one embodiment of the invention. Network device 300 may include many more components than those shown. The components shown, however, are sufficient to disclose an illustrative embodiment for practicing the present invention. Network device 300 may represent, for example, client network device 101 and/or mobile domain platform 106 of fig. 1.

Network device 300 includes processing unit 312, video display adapter 314, and a mass memory, all in communication with each other via bus 322. The mass memory generally includes RAM316, ROM332, and one or more persistent mass storage devices, such as hard disk drive 328, tape drive, optical drive, and/or floppy disk drive. The mass memory stores operating system 320 for controlling the operation of network device 300. Any general purpose operating system may be used. A basic input/output system (BIOS)318 is also provided for controlling low-level operations of network device 300. As shown in FIG. 3, the network device 300 is also capable of communicating with the Internet or some other communications network via a network interface unit 310, where the network interface unit 310 is configured for use with various communications protocols, including the TCP/IP protocol. Network interface unit 310 is sometimes referred to as a transceiver, transceiving device, or Network Interface Card (NIC).

The mass memory as described above illustrates another type of computer-readable media, namely computer storage media. Computer storage media may include volatile, nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computing device.

The mass memory also stores program code and data. One or more applications 350 are loaded into mass memory and run on operating system 320. Examples of application programs may include transcoders, schedulers, calendars, database programs, word processing programs, HTTP programs, customizable user interface programs, IPSec applications, encryption programs, security programs, Virtual Private Network (VPN) programs, SMIS message servers, IM message servers, email servers, account management, and so forth. In one embodiment, network device 300 includes a server mobile domain platform 352 that is configured to operate in conjunction with one or more of its included components on two or more network devices in a manner more or less similar to mobile domain platform 106 in fig. 1. Further, in another embodiment, client mobile domain platform 354 may be configured as an application of client network device 101 as shown in FIG. 1.

Instantiating a Mobile Domain platform

FIG. 4 illustrates a block diagram of an example mobile domain platform configured with at least five major components including at least one subcomponent, including: message core 406, application core 412, subscriber delivery 420, billing subsystem 424, and subscriber management 426. These five components are configured to receive and process text messages from a user that are sent to a mobile number (short code or other) corresponding to the mobile domain platform. The processed content of the received text message is forwarded to the subscriber who has registered at least one keyword included in the text message. Typically, the mobile domain platform is configured such that multiple subscribers and multiple users simultaneously utilize the mobile domain platform to perform actions. In addition, the operation of the various major components of the mobile domain platform will be described in greater detail below.

Message core 406 is a primary component configured to receive at message receiver 408 text messages sent by user 400 via mobile gateway 402 to a mobile number corresponding to a mobile domain platform. Message receiver 406 is a subcomponent that is configured to receive the text message and perform one or more operations including, but not limited to: parsing, filtering, and evaluating keyword hierarchies with respect to the content of the message. If it is determined that a subscriber is registered for control of one or more keywords included in the message, the receiver 406 tokenizes (tokenize) the message content and validates the tokenized content. The validated and tokenized content is passed to another subcomponent 410 where rules and/or applications predefined by the subscriber are identified for the received message in that subcomponent 410. In addition, the message core 406 also facilitates caching of subscriber-defined campaigns, keyword hierarchies, and other actions, which generally speed up processing of received messages. Additionally, message core 406 may enable the mobile domain platform to provide a response in the form of a text message sent to user 400, and the content of the response message is based at least in part on the content of the text message originally received from the user.

Application core 412 is another primary component configured to process the subscriber's predefined applications and rules for a campaign corresponding to one or more keywords validated and tokenized in a received text message. In general, the application core 412 provides a generic framework to insert updated interactions, applications, and/or delivery actions by subscribers for existing or new activities without having to make additional changes to the operation of the mobile domain platform.

Additionally, the subscriber may employ the API and/or platform specification to create at least one of: a custom application for processing the content of the received text message, or a custom delivery action to the subscriber for the processing result. Application core 412 may handle these subscriber updates, customized applications, and/or customized delivery actions, even if they are provided in one or more different ways, including but not limited to: XML, API instructions, extensible stylesheet language transformations (XSLT), and the like.

With respect to application core 412, subcomponent 414 enables the performance of associated actions, applications, interactions, and real-time processing of at least a portion of the content of the received text message. Subcomponent 416 enables batch processing based on time and/or quantity, which may also depend on delivery actions preselected by the subscriber. In addition, the application core 412 prepares a text message for delivery to the subscriber by one or more methods.

Subscriber delivery component 420 is in communication with application core component 412 and is configured to receive prepared content for one or more text messages identified for delivery to a subscriber. Delivery daemon 418 is a subcomponent that is configured to manage multiple adapters that are configured to deliver text message content to subscribers. These adapters also include subcomponents for delivery mechanisms including, but not limited to, email, fax, SMS, MMS, FTP, IM, RRS, update information on web pages, and the like. Subscriber delivery component 420 enables one or more queues for each delivery mechanism and can configure a timeline of deliveries based on different factors including, but not limited to, priority and criticality. Subscriber delivery component 420 also collects information regarding delivery, including logs, status, usage, and/or metrics, which are all available to enable a determination of the cost introduced in delivering text message content to a particular subscriber. In addition, subscriber delivery component 420 supports at least one API that enables a subscriber to update a new or existing delivery channel without having to make additional changes to the operation of the mobile domain platform.

Subscriber billing component 424 is configured to resolve the subscriber's account balance based at least in part on paid charges, expenses incurred in processing and forwarding text message content, billing plans, discounts, and the like. Component 424 can support multiple billing plans including, but not limited to, flat rate, number of subscriber applications hosted, layout, number of received text messages processed for a subscriber. Further, different costs may be incurred for different delivery actions including, but not limited to: fax, email, alerts, SMS, MMS, RRS, web page updates, etc. Subscriber billing component 424 employs at least one subcomponent, such as billing daemon subcomponent 423, to enable real-time and/or batch processing of account balances. Additionally, if the prepaid holdings are running low and/or a predetermined account balance has been reached, component 424 can indicate an alert, message, or the like to be provided to the subscriber.

Subscriber management component 426 is configured to communicate with at least one subscriber 448 via network 450, subscriber 448 being, for example, a producer, partner, advertising agency, business, or the like. Network 450 may be configured to include one or more of the networks described above with reference to fig. 1. Further, component 426 can enable one or more user interfaces including, but not limited to, a web interface, a command line interface, and the like.

User login subcomponent 428 is configured to at least enable the subscriber to access the mobile domain platform and provide authentication of the subscriber. Role definition subcomponent 430 is also configured to at least partially manage the account privileges and roles of the various authenticated subscribers. A profile for each subscriber is typically developed and maintained for subscriber management purposes. Domain search subcomponent 432 is also configured to enable the subscriber to search for keywords that the subscriber can control. Domain registration subcomponent 434 is operable to enable the subscriber to register a mobile domain that is controllable for the benefit of the subscriber for control of at least one selected keyword. The application definition subcomponent 436 is further operable to enable the subscriber to define one or more applications hosted by the mobile domain platform for processing received text messages whose content includes one or more keywords controlled/registered for the subscriber. Rule definition subcomponent 438 is also operable to enable the subscriber to define one or more rules that will be applied when processing the received text message. Additionally, it should be appreciated that these rules and applications are typically defined by subscribers based at least in part on activity types such as poll surveys, competitions, sales leads, loyalty incentives to known users, and electronic coupons to new or existing users.

The delivery action definition subcomponent 440 is configured to enable the subscriber to define the above-described delivery mechanisms for received text messages based at least in part on priority, activity type, etc. Billing subcomponent 442 is also configured to provide financial information to the subscriber, such as billing plans, account expense summaries, and the like. In addition, at least some of this financial information has been pre-processed by subscriber billing component 424 for subcomponent 442.

Reporting subcomponent 444 is also configured to provide at least one report to the subscriber regarding at least one activity, e.g., a relevant evaluation and general effect on different aspects of the application, rule, and/or delivery action. Further, subcomponent 444 can be configured to provide reports to the subscriber in real-time, periodic, and/or batch during the ongoing activity. Based at least in part on the reporting information, the subscriber is enabled to modify the ongoing activity. For example, if a particular sub-domain keyword, application, rule, and/or delivery action is identified by the report as being more popular with the user in one or more activities, the subscriber is enabled to subsequently modify at least one ongoing activity to promote at least one popular feature.

Message inbox component 446 is also configured to manage text messages communicated between the subscriber and the mobile domain platform.

In addition, data storage 422 enables each component to store and access one or more databases to enable management, billing, and processing of communications between users and subscribers of the mobile domain platform.

Illustrative flow chart

FIG. 5 illustrates a flow diagram of a general overview of the process for obtaining control of a mobile domain keyword for a campaign by a subscriber and defining how the campaign is managed by the mobile domain platform. Moving from a start block, the process proceeds to block 502, where the subscriber logs into the subscriber management component of the mobile domain platform in block 502. At block 504, the process enables the subscriber to search for mobile domain keywords that are available for registration. The subscriber can also register the selected mobile domain keyword for a campaign associated with the subscriber.

Moving to block 506, the process enables the subscriber to create and define a hierarchy of one or more keywords based on the root mobile domain keyword registered for the subscriber. Proceeding to block 508, the process enables the subscriber to create and define one or more customized applications and/or configure defined actions for the provided applications that process the received text message including the registered mobile domain keyword. Proceeding to block 510, the process enables the subscriber to create customized rules or configure provided rules (which define processing by defining habits) and/or provided applications for text message content that includes the registered keywords. The subscriber is also enabled to create and define customized delivery rules and customized delivery mechanisms for text message content that includes the registered keywords. The subscriber may also define provided delivery rules and provided delivery mechanisms for the registered keywords. Next, processing returns to perform other actions.

FIG. 6 illustrates a flow chart of a general overview of a process for processing a received file message by a mobile domain platform, wherein the received file message includes a mobile domain keyword registered for a subscriber. Moving from a start block, the process proceeds to block 602 where the mobile domain platform receives a text message from the user from the gateway in block 602. The text message is sent by the user to a mobile number (short code or otherwise) corresponding to the mobile domain platform. At block 604, the mobile domain platform processes the received text message to identify registered mobile domain keywords. If so, the platform employs applications and rules to process the content of the received text message including the registered mobile domain keyword. Proceeding to block 606, the process provides the results of the mobile domain platform processing to the subscriber based on one or more delivery actions previously defined by the subscriber. Next, processing moves to performing other actions.

Fig. 7 illustrates another flow chart showing a general overview of processing a received text message that includes at least one mobile domain keyword registered to a subscriber. Moving from a start block, the process advances to block 702 where a text message including at least one mobile domain keyword registered to a subscriber is received by the mobile domain platform in block 702. At block 704, the content and information associated with the received text message is parsed and filtered into one or more tokens.

Proceeding to block 706, one or more applications for processing the characters are identified. At block 708, the rules for invoking the application are evaluated and an action is identified. Proceeding to block 710, the tokenized text message is processed in accordance with the identified actions, rules and applications. Moving to block 712, the processing results are prepared and configured in a format that may be provided to the registered subscriber by one or more defined delivery actions and delivery mechanisms. Next, processing returns to perform other actions.

Fig. 8 illustrates another flow chart showing a general overview of the evaluation of applications, rules and actions corresponding to a subscriber who controls the registration of mobile domain keywords included in a received text message. Moving from a start block, the process proceeds to decision block 800 where a determination is made as to whether an application corresponding to the registered mobile domain keyword is identified in block 800. If not, the process loops until the result is true. However, once such an application is identified, the process moves to decision block 802, where a determination is made as to whether the application is interactive in block 802. If true, the process proceeds to block 804, where a state machine is loaded and a session is initiated for interacting with the user sending the text message whose content includes the registered mobile domain keywords in block 804. In addition, a response text message is sent by the mobile domain platform to the user. Next, as the state machine continues to handle text message communications with the user, processing returns to processing other actions.

Alternatively, if the determination of decision step 802 indicates that the application is non-interactive, processing proceeds to block 808 where rules associated with the evaluation of the application are identified in block 808. At block 810, a rules engine is invoked to identify specific rules applicable to evaluate an application based on the content of the text message. Proceeding to block 812, the process retrieves a set of actions associated with the applicable rule for enabling at least one application to process the text message content. Proceeding to block 814, the set of applicable rules and actions is cached. Next, processing returns to perform other actions.

It will be understood that each block of the flowchart illustrations above, and combinations of blocks in those flowchart illustrations, can be implemented by computer program instructions. These program instructions may be provided to a processor to produce a machine, such that the instructions, which execute on the processor, create means for implementing the actions specified in the flowchart block or blocks. The computer program instructions may be executed by a processor to cause a series of operational steps to be performed by the processor to produce a computer implemented process such that the instructions, which execute on the processor, provide steps for implementing the actions specified in the flowchart block or blocks.

Accordingly, blocks of the flowchart illustrations support combinations of means for performing the specified actions, combinations of steps for performing the specified actions and program instruction means for performing the specified actions. It will also be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can also be implemented by special purpose hardware-based systems which perform the specified actions or steps, or combinations of special purpose hardware and computer instructions.

Claims (20)

1. A method for managing text messages communicated between a user and a platform subscriber, comprising:

receiving each text message sent by the user to a mobile number corresponding to the platform, wherein the user is separate from the subscriber;

determining each text message that includes a keyword that is rooted by the platform to the subscriber and that corresponds to the mobile number;

enabling the platform to process content included in each text message that includes at least one registered keyword and is sent by the user to the corresponding mobile number, wherein individual processing of content included in each text message having at least one combination of the registered keyword and another keyword that is not registered with a respective subscriber is predetermined by the respective subscriber to enable at least one action; and

enabling at least one delivery action for the respective subscriber of at least one processing result of content included in at least one text message including at least one combination of the registered keyword and the another keyword, wherein each delivery action is pre-identified and determinable by the respective subscriber, and wherein the at least one delivery action includes one or more delivery mechanisms defined by the respective subscriber for delivering the at least one result to the respective subscriber.

2. The method of claim 1, further comprising:

enabling the subscriber to search for at least one available keyword and register the at least one available keyword with the platform;

enabling the subscriber to define at least one application for processing each received text message including at least one keyword registered to the subscriber; and

enabling the subscriber to define at least one rule for processing each received text message including at least one keyword registered to the subscriber.

3. The method of claim 1, further comprising enabling the subscriber to customize the one or more delivery mechanisms for delivering processing results of content included in at least one text message; and

enabling the subscriber to customize one or more delivery rules for the delivery mechanism, wherein the delivery mechanism comprises at least one of a phone call, email, alert, Instant Messaging (IM), simple syndication (RSS) feed, File Transfer Protocol (FTP), Short Message Service (SMS), Multimedia Message Service (MMS), chat, or web page update.

4. The method of claim 1, further comprising:

enabling the subscriber to define a domain based on at least one keyword registered to the subscriber, wherein the subscriber identifies the registered keyword as a root of the domain;

enabling the subscriber to define a hierarchy of at least one subdomain based on at least one further keyword configured in combination with a root keyword; and

enabling the subscriber to define the processing of each sub-domain individually based on text message content including at least the sub-domains defined by a combination of a root registration keyword and the at least one further keyword.

5. The method of claim 1, further comprising enabling each subscriber to dynamically bid on instances of received text messages that include specific keywords that may be registered for a campaign.

6. The method of claim 5, wherein the dynamic bid is further defined by the subscriber for at least one of a time period or an amount of funds.

7. The method of claim 1, further comprising enabling each subscriber to bid on registering at least one available keyword for a campaign within a period of time.

8. The method of claim 1, further comprising enabling the registered keyword to be included in results of an online search, wherein the online search results include at least one indication that further information is obtained by sending at least one text message with the registered keyword to the mobile number corresponding to the platform.

9. The method of claim 1, further comprising enabling registration of affiliated keywords for a campaign only by each subscriber of an owner of a brand identified by the platform as an available keyword.

10. The method of claim 1, wherein the processed content comprises a representation of at least one coupon redeemable with the registered subscriber.

11. An apparatus for managing text messages communicated between a user and a platform subscriber, comprising:

receiving means for receiving each text message sent by the user to a mobile number corresponding to the platform, wherein the user is separate from the subscriber;

determining means for determining each text message including a keyword that is registered as a root by the platform to the subscriber and that corresponds to the mobile number;

processing means for enabling the platform to process content included in each text message that includes at least one registered keyword and that is sent by the user to the corresponding mobile number, wherein the individual processing of content included in each text message having at least one combination of the registered keyword and another keyword that is not registered with a respective subscriber is predetermined by the respective subscriber to enable at least one action; and

a delivery means for enabling at least one delivery action for the respective subscriber of at least one processing result of content included in at least one text message including at least one combination of the registered keyword and the further keyword, wherein each delivery action is pre-identified and determinable by the respective subscriber, and wherein the at least one delivery action comprises one or more delivery mechanisms defined by the respective subscriber for delivering the at least one result to the respective subscriber.

12. The apparatus of claim 11, further comprising:

search registration means for enabling the subscriber to search for at least one available keyword and register the at least one available keyword with the platform;

application defining means for enabling said subscriber to define at least one application for processing each received text message comprising at least one keyword registered to said subscriber; and

rule defining means for enabling said subscriber to define at least one rule for processing each received text message comprising at least one keyword registered to said subscriber.

13. The apparatus of claim 11, further comprising:

delivery mechanism customizing means for enabling said subscriber to customize said one or more delivery mechanisms for delivering results of processing of content included in at least one text message; and

delivery rule customization means for enabling said subscriber to customize one or more delivery rules for said delivery mechanism, wherein said delivery mechanism comprises at least one of a phone call, an email, an alert, an instant message IM, a simple messaging syndication RSS feed, a file transfer protocol FTP, a short message service SMS, a multimedia messaging service MMS, a chat, or a web page update.

14. The apparatus of claim 11, further comprising:

domain defining means for enabling the subscriber to define a domain based on at least one keyword registered to the subscriber, wherein the subscriber identifies the registered keyword as a root of the domain;

hierarchy defining means for enabling said subscriber to define a hierarchy of at least one subdomain based on at least one further keyword configured in combination with a root keyword; and

subdomain processing defining means for enabling said subscriber to define processing for each subdomain separately based on text message content including at least said subdomain defined by a combination of a root registration keyword and said at least one further keyword.

15. The apparatus of claim 11, further comprising:

first bidding means for enabling each subscriber to dynamically bid on respective instances of a received text message including specific keywords that may be registered for a campaign.

16. The apparatus of claim 15, wherein the dynamic bid is further defined by the subscriber for at least one of a time period or an amount of funds.

17. The apparatus of claim 11, further comprising:

second bidding means for enabling each subscriber to bid on registering at least one available keyword for a campaign within a period of time.

18. The apparatus of claim 11, further comprising:

means are included for enabling the registered keyword to be included in results of an online search, wherein the online search results include at least one indication to obtain further information by sending at least one text message with the registered keyword to the mobile number corresponding to the platform.

19. The apparatus of claim 11, further comprising:

registration means for enabling registration of an affiliated keyword for a campaign only by each subscriber of an owner of a brand identified by the platform as an available keyword.

20. The apparatus of claim 11, wherein the processed content comprises a representation of at least one coupon redeemable with the registered subscriber.