Scalable instant messaging architecture

• US 20050050151A1
• Filed: 08/29/2003
• Published: 03/03/2005
• Est. Priority Date: 08/29/2003
• Status: Abandoned Application

• Current Assignee: Accenture Global Services GmbH (Accenture PLC)
• Original Assignee: Accenture Global Services GmbH (Accenture PLC)
• Inventors: Mitchell, Pablo Andrew, Teng, Angela C.
• Application Number:
  US10/651,032
• Publication Number:
  US 20050050151A1
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]

Abstract

An instant messaging software architecture and method for implementing scalable and portable community-motivated communications is disclosed herein. Aspects of the invention can be used to enhance a user'"'"'s instant messaging experience through the ability to involve a large number of users in a variety of different interactive environments while maintaining inter-user responsiveness. The scalability aspect of the invention utilizes scalable messaging interfaces and object oriented programming to extend user limits beyond current boundaries. The portability of this implementation and programming language also enables users of different devices such as PDAs, personal computers and mobile phones to use the same software and architecture to communicate with other users. Aspects of the invention further enable content providers to advertise, poll and otherwise interact with a large audience in a real-time instant messaging environment.

Claims

1. A scalable instant messaging system comprising:

a scheduler object that retrieves, when an event trigger fires at a predetermined event time, event data from a database object;

a program object that manages event tasks defined by the event data;

an automated event bot, wherein the automated event bot manages communications with a plurality of participants of the event based on the event tasks;

a buddy object for each unique participant of the event, each buddy object being managed by the automated event bot.

2. The system of claim 1, wherein the program object is instantiated by the scheduler object based on the event data.

3. The system of claim 1, wherein the automated event bot is instantiated by the program object based on the event data.

4. The system of claim 1, wherein the program object constructs and transmits a solicitation for the event to a predetermined set of possible participants through a communication channel other than an instant messenger service.

5. The system of claim 1, wherein the automated event bot comprises a controller queue interface for providing commands to the buddy objects, and a message queue interface for providing message data to the buddy objects.

6. The system of claim 1, further comprising an instant messaging protocol interface filter module for modifying a message according to an instant messaging protocol of a receiving participant.

7. The system of claim 6, wherein the instant messaging protocol interface filter module further comprises one or more protocol filters, each specific to a particular instant messaging protocol.

8. A method for coordinating and maintaining communications between a community of users, comprising:

when an event trigger fires, retrieving event data from a database and instantiating a program object based on the event data;

creating an automated event bot for managing instant messaging communications with participants of an event corresponding to the event data;

receiving a predetermined first list of users representing possible participants for the event; and

sending a solicitation message, via a communication channel other than an instant messaging service, to each user in the first list of users.

9. The method of claim 8, further comprising the automated event bot instantiating a buddy object for each user in a second list of users comprising users selected from the first list of users.

10. The method of claim 9, wherein the second list of users comprises users from the first list of users from which a positive response to a greeting message is received.

11. The method of claim 9, wherein the second list of users comprises all users from the first list of users.

12. The method of claim 8, further comprising sending, at a predetermined time, an event message to one or more users for which there exists a buddy object, when information stored in the user'"'"'s respective buddy object matches a criteria of the event message.

13. The method of claim 9, wherein the buddy objects receive and process response messages from the participants based on data received from the event bot.

14. The method of claim 9, wherein the buddy objects compose and send messages to one or more participants based on instructions received from the automated event bot.

15. The method of claim 8, wherein the step of receiving a predetermined first list of users representing possible participants for the event comprises retrieving a list of users from an instant messaging protocol corresponding to a predefined user identifier.

16. The method of claim 9, further comprising sending a greeting message to each user for which there exists a corresponding buddy object, wherein the greeting message requests a response identifying each user'"'"'s desire to participate in the event.

17. The method of claim 16, wherein when no response or a negative response is received from a particular user, the automated event bot removes the buddy object corresponding to the particular user.

18. The method of claim 12, wherein the step of sending, at a predetermined time, an event message to one or more users for which there exists a buddy object, when information stored in the user'"'"'s respective buddy object matches a criteria of the event message, comprises:

sending an event message in response to a communication received from a participant

19. The method of claim 12, wherein the step of sending, at a predetermined time, an event message to one or more users for which there exists a buddy object, when information stored in the user'"'"'s respective buddy object matches a criteria of the event message, comprises:

storing event data relevant to a particular user in the particular user'"'"'s representative buddy object.

20. A computer readable medium storing computer executable instructions that, when run, create a software architecture comprising:

a program object, instantiated by a scheduler object when an event trigger fires, wherein the program object receives an event ID and retrieves event information from an event database based on the received event ID;

an automated event bot instantiated by the program object based on the event data, wherein the automated event bot manages event activities for a plurality of clients participating in the event; and

a buddy object instantiated by the automated event bot for each of the plurality of clients participating in the event, wherein each buddy object maintains an instant messaging socket with its corresponding client.

21. The computer readable medium of claim 20, wherein the software architecture further comprises:

a solicitation message generated and sent by the program object over a communication channel other than the instant messaging system for which the buddy objects maintain instant messaging sockets.

22. The computer readable medium of claim 20, wherein the software architecture further comprises a greeting message generated and sent by the automated event bot to a plurality of clients, wherein the greeting message requests a response regarding each client'"'"'s desire to participate in the event.

23. The computer readable medium of claim 22, wherein when the automated event bot receives no response or a negative response from a particular client responsive to the greeting message, the automated event bot removes the buddy object corresponding to the particular client.

24. The computer readable medium of claim 20, wherein the automated event bot passes a message object having message data to one or more buddy objects via a message queue.

25. The computer readable medium of claim 24, wherein each of the one or more buddy objects that receive the message object generates and sends a message to its corresponding client based on the message data.

26. The computer readable medium of claim 25, wherein the message data comprises question data and answer data.

27. The computer readable medium of claim 26, wherein each buddy object, upon receiving a response from its corresponding client based on the message, evaluates the received response by a comparison of the response to the answer data.