Integrated interactive messaging system and method

• US 8,051,132 B2
• Filed: 07/18/2003
• Issued: 11/01/2011
• Est. Priority Date: 07/19/2002
• Status: Active Grant

• Current Assignee: First Aggregator, LLC
• Original Assignee: m-Qube Incorporated (Mobile Messenger Americas, Inc.)
• Inventors: Nandiwada, Srinivasarao, Hwang, Boon, Priyadarshan, Eswar, Hewes, Gerald
• Primary Examiner(s): Burgess, Glenton B
• Assistant Examiner(s): RECEK, JASON D
• Application Number:
  US10/521,507
• Publication Number:
  US 20050209861A1
• Time in Patent Office: 3,028 Days
• Field of Search: 709/206, 709/207, 709/238, 340/825, 370/351, 705/14
• US Class Current: 709/206
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 51/212 using filtering or selective blocking

Abstract

A system and method for organizations to develop, test, execute and analyze messaging programs defining a message application server comprising (a) a dialog designer configured to provide a user interface to an organization'"'"'s program designers and marketers, to allow for rapid messaging program creation, to provide the ability to select the type of messaging program, to select service addresses for the messaging program, to schedule messaging programs for execution, to upload messaging user data into lists, to create segments, to download messaging program result data, to test messaging programs, to provide reports, including real-time reports, on messaging programs; (b) a dialog server configured to execute messaging programs by execution of program instructions, to manage substantially simultaneously executed messaging programs, to store messaging user results and message delivery status, to maintain state and session context across message invocations for messaging users within messaging program; and (c) a message exchange configured to route messages to and from messaging service providers, to manage service addresses, to perform message billing and to connect to messaging service providers. The system and method allow organizations to interact with messaging users who own a messaging communication device by using the services of messaging service providers.

Claims

1. A system for organizations to develop, test, execute and analyze messaging programs defining a message application server comprising:

(a) a dialog designer configured to provide a user interface to an organization'"'"'s program designer and marketer, to allow for rapid messaging program creation, to provide the ability to select a type of a messaging program, to select a service addresses for the messaging program, to schedule the messaging program for execution, to upload messaging user data into lists, to create segments, to download messaging program result data, to test the messaging program, to provide reports, including real-time reports, on the messaging program;

(b) a dialog server configured to execute the messaging programs by execution of a messaging instructions, to manage substantially simultaneously executed messaging programs, to store messaging user results and message delivery status, to maintain state and session context across message invocations for messaging users within a messaging program; and

(c) a message exchange configured to route messages to and from messaging service providers, to manage service addresses, to perform message billing and to connect to messaging service providers;

whereby organizations can execute messaging programs interacting with messaging users via the messaging service providers.

2. The system of claim 1, wherein a plurality of organizations hierarchically organized can independently develop, test, execute, and analyze messaging programs.

3. The system of claim 1, wherein the organizations are not messaging service providers.

4. The system of claim 1, wherein the message application server is connected to a plurality of messaging service providers systems.

5. The system of claim 1, wherein the message application server is connected to the messaging service providers systems via a data network including, but not limited to, the Internet and private internet, using a variety of messaging protocols, including but not limited to, Simple Mail transfer Protocol (SMTP), Short Message Peer-to-Peer Protocol (SMPP), and instant messaging.

6. The system of claim 1, wherein the message application server is connected to the organizations via a data network including, but not limited to, the Internet and private intranets.

7. The system of claim 1, wherein the messaging users use messaging devices using a variety of messaging protocols including, but not limited to, Short Message Service (SMS), Enhanced Message Service (EMS), Multimedia Messaging Service (MMS), Wireless Application Protocol (WAP), HyperText Markup Language (HTML), eXtensible HyperText markup Language (xHTML), instant messaging, e-mail, interactive TV, and client side execution environments.

8. The system of claim 1, wherein the messaging programs and instructions are designed using a graphical user interface (GUI) design tool and have a text based representation.

9. The system of claim 1, further comprising a data database to store messaging program data;

an opt-out system configured to store lists of users that have opted-out of messaging programs for a particular opt-out scope;

a billing system to rate the messaging programs;

an address manager to create, configure, provision, and administer messaging program service addresses; and

one or more message detail record databases to record all critical service level or billing events.

10. The system of claim 9, wherein the data stored in the data database is used in future messaging programs.

11. The system of claim 1, wherein the organization accesses the dialog designer using a web browser from a remote computer via a data network.

12. The system of claim 1, wherein applications executed by the organization can interface with the message application server via web service calls using protocols including, but not limited to, Simple Object Access Protocol (SOAP).

13. The system of claim 1, wherein the message application server is configured to operate in conjunction with the organizations systems;

including, but not limited to, customer relationship management (CRM) systems.

14. The system of claim 1, wherein the dialog server can access the messaging instructions from a remote computer systems connected to the dialog server via a data network whereby integration with remote systems can be achieved.

15. The system of claim 1, wherein the messaging instruction includes, but is not limited to, messaging primitives, unconditional logic primitives, conditional logic primitives, session variable primitives, input/output primitives, remote connectivity primitives, whereby any messaging program of arbitrary complexity can be developed and integrated with remote systems connected to a data network.

16. The system of claim 1, wherein the dialog server maintains session state and context across message invocations for a pair consisting of a messaging device address and a messaging program address.

17. The system of claim 1, wherein the dialog server, the message exchange and the connection to the messaging service providers store messages into queues with flow control techniques whereby queue overload is prevented or mitigated.

18. A method for organizations to develop, execute and analyze messaging programs comprising:

(a) an organization'"'"'s program designers designing the messaging program;

(b) the program designer selecting a segment for push programs;

(c) the program designers selecting a program service address;

(d) the program designers testing the messaging program;

(e) executing the messaging program where the messaging program is either started manually or automatically at a scheduled date;

(f) messaging users interacting with the messaging program;

(g) capturing and storing the messaging users responses and other messaging user data in a data database;

(h) stopping the messaging program either manually or automatically at a scheduled date; and

(i) analyzing the messaging program using the data captured and stored during the program execution;

whereby organizations can execute messaging programs interacting with messaging users via messaging service providers.

19. The method of claim 18, wherein the data captured as part of executing a messaging program is used in a subsequent messaging program.

20. The method of claim 18, wherein the segments are created from list data imported by the program designer into a data database, and from results data generated by the execution of prior messaging programs.

21. The method of claim 18, wherein the organizations deliver coupons, offers and promotions to the messaging users.

22. The method of claim 18, further comprising storing important service level and billable events in one or more message detail record (“

MDR”

) database.

23. The method of claim 22, further comprising:

(a) importing the message detail records generated by the message application server into a billing MDR database;

(b) rating and billing the message detail records;

(c) generating organization invoices and service provider account payable reports.

24. The method of claim 23, further comprising reconciling service provider invoices for messaging transport costs with service provider account payable reports generated from the message application server message detail records.

25. The method of claim 23, further comprising:

(a) receiving message detail records generated in the messaging service provider system from the messaging service providers;

(b) importing the message detail records generated in the messaging service provider system into the billing MDR database;

(c) rating and billing the message detail records generated in the messaging service provider system;

(d) generating from the message detail records generated in the messaging service provider system service provider accounts payable reports; and

(e) reconciling the accounts payable reports generated from the message detail records generated in the messaging service provider system with the accounts payable reports generated the message application server.

26. A method for organizations to deploy pull messaging programs comprising:

(a) receiving in a message exchange a messaging device originated message from a messaging user messaging device via a messaging service provider system, the messaging device originated message is of any one of a variety of messaging protocols including, but not limited to, Short Message Service (SMS), Enhanced Message Service (EMS), Multimedia Messaging Service (MMS), Wireless Application Protocol (WAP), HyperText Markup Language (HTML), eXtensible HyperText markup Language (xHTML), instant messaging, e-mail, interactive TV;

(b) forwarding the messaging device originated message from the message exchange to a dialog server;

(c) looking up the appropriate session context and pull messaging program based on the messaging device address and the program service address;

(d) executing pull messaging program instructions in the dialog server upon receiving the messaging device originated message and based on the session state and context;

(e) routing the messaging device originated message in the message exchange to the appropriate messaging service provider, and storing any message status delivery returned by the message exchange;

whereby the messaging users who sent a messaging device originated message receives a reply message on his messaging device.

27. A system for developing, analyzing, deploying, and monitoring targeted messaging applications, comprising:

a client systems, the client system comprising one or more messaging devices;

a message service provider system;

a message application server in communication with the client system and the message service provider system;

wherein the client systems is configured to interface with the message application server to enable the client systems to develop, analyze, test, deploy, and monitor messaging applications, the messaging applications to generate messages, receive messages from and send messages to the message service provider system, and

wherein the message application server is configured to determine and route the messages to the message service provider system regardless of the message service provider system'"'"'s implemented messaging technology.

28. The system of claim 27, wherein the message application server further comprises a dialog server configured to execute messaging applications by executing an application instructions, to manage substantially simultaneously executed message applications, to store messaging user results and message delivery status and to maintain state and session context across message invocations for messaging users within a messaging application.

29. The system of claim 28, wherein the message application server further comprises a message exchange in communication with the dialog server, the message exchange is configured to route messages to and from the messaging service providers.

30. The system of claim 29, wherein the message exchange is further configured to manage service addresses and to perform message billing.

31. The system of claim 29, wherein the message application server further comprises a dialog designer in communication with the dialog server and the message exchange, the dialog designer configured to provide an interface to the client systems to facilitate rapid message application creation, to provide the ability to select a type of message application, to select the service address for a message application, to schedule the message applications for execution, to upload messaging user data into lists, to create a segments, to download message application result data, to testing the message applications.

32. The system of claim 31, wherein the dialog designer further comprises a graphical user interface (GUI) design tool component to enable the client systems to develop, analyze, test, and deploy messaging applications.

33. The system of claim 31, wherein the message applications developed using the dialog designer comprise interactive message applications.

34. The system of claim 31, wherein the dialog designer further comprises a client interface component to reside on the client system and a server interface component to reside on the message application server, the client interface component being in communication with the server interface component to enable the client system to access the dialog server.

35. The system of claim 31, wherein the dialog designer is further configured to facilitate reporting on message application transactions.

36. The system of claim 28, wherein the dialog server comprises:

an execution unit to process messaging device originated messages and other events;

a scheduler unit to start and stop the messaging applications or send scheduled events to the execution unit at scheduled times;

an application service system to manage executable applications;

a session system to manage messaging user sessions;

a user system to manage messaging users properties;

an opt-out system to manage the opt-in and opt-out status of messaging device addresses;

an application instruction unit to retrieve and cache required application instructions;

a bulksend unit to send large pushes to messaging device addresses within an application segment;

a dialog server in-queue to store messages or events for execution by the execution unit;

a message delivery status system to record message delivery errors returned by the message exchange;

a monitoring unit to monitor the state of the dialog server;

a dialog server database to store information pertaining to the dialog server;

a dialog server message detail record database to log all accounting or service level relevant events within the dialog server;

a dialog designer interface to connect the dialog server to the dialog designer; and

a message exchange interface to connect the dialog server to the message exchange.

37. The system of claim 36, wherein the message exchange further comprises:

an out queue to store termination messages and dialog server connection messages;

an outgoing message router to route messages based on the application service address and the messaging device address;

a plurality of outgoing handlers, each for a specific messaging technology, to send messages to a particular messaging service provider gateway;

a plurality of incoming handlers, each for a specific messaging technology, to accept messaging device originated messages from a particular messaging service provider gateways;

an incoming message router to route messaging device originated message to the dialog server;

an address manager to create, configure, provision and administer application service addresses;

a billing system configured to display MDR logs, to rate and invoice messaging applications;

a monitoring unit to monitor the state of the message exchange;

a message exchange database to handle the data storage needs of the message exchange;

a message exchange message detail record database to log all billing or service level relevant events within the message exchange system;

a dialog server interface to connect the message exchange to the dialog server;

a dialog designer interface to connect the message exchange to the dialog designer; and

a billing MDR database to hold the MDR records for billing purposes.

38. The system of claim 37, wherein the dialog designer further comprises:

a HyperText Transfer Protocol (HTTP interface to enable the client systems to access the message application server;

a Web Service interface to enable the client systems to automate access to the message application server;

a service layer to implement the core functionality of the dialog designer;

a dialog server interface to connect the dialog designer to the dialog server;

a message exchange interface to connect the dialog designer to the message exchange;

a dialog designer database to store dialog designer transaction information;

a dialog designer data database to store messaging application related information; and

a dialog server message detail record database to store billing and service level operations information.

39. The system of claim 27, wherein the message service provider systems comprises:

a messaging devices, the messaging device having a messaging device address, and

a messaging service provider gateway communicatively connected to the messaging application server to provide for aggregation and delivery of the messages to the messaging device address.

40. The system of claim 27, wherein the messaging device is selected form a group consisting of data enabled cell phones, wireless enabled Personal Digital Assistants (PDAs), instant messaging devices, mobile e-mail devices and interactive TV devices.

41. The system of claim 27, wherein the client systems comprises a customer relationship management system.