Information gateway manager for multiple devices

• US 7,752,331 B2
• Filed: 10/30/2001
• Issued: 07/06/2010
• Est. Priority Date: 10/30/2001
• Status: Expired due to Fees

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Patel, Rita, Grason, Thomas S., Downes, Scott J., Podojil, Mark E.
• Primary Examiner(s): STRANGE, AARON N
• Application Number:
  US10/020,646
• Publication Number:
  US 20030084093A1
• Time in Patent Office: 3,171 Days
• Field of Search: 709/202, 709/203, 709/206, 709/217, 709/219, 709/225, 707/3, 707/10
• US Class Current: 709/238
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A system for providing information to users and for managing and routing requests from users. The information delivery system is preferably a platform independent application, which enables users to receive responses based upon on-demand, scheduled or event driven requests or triggers. On-demand requests are those that a user sends and, some time later, receives a response with the requested information. Scheduled requests are those provided to users who subscribe to a service offering. On a set schedule, information is sent to the user based upon the information desired and criteria selected. Event driven responses are generated based upon certain criteria or thresholds being met. For each of the above types of requests, the responses may be formatted in plain text, Hypertext Markup Language (HTML) or other format depending upon the requestor device type or the subscriber'"'"'s specified e-mail client.

Claims

1. A distributed information processing system, comprising:

a first computing device having a physical memory with a client device interface stored thereon, the client device interface being adapted to receive requests for a type of information from a plurality of remote devices;

a second computing device having a physical memory with a stateless module manager stored thereon, the stateless module manager being adapted to receive and route said requests from said client device interface; and

a plurality of third computing devices having physical memories with information modules stored thereon, wherein said information modules register with said stateless module manager, and wherein the stateless module manager routes said requests to an appropriate one of said plurality of information modules in accordance with the type of information requested, wherein the stateless module manager handles service collisions in which a plurality of information modules are capable of responding to the requests, such that only one information module processes the requests, wherein the stateless module manager enables only one of the information modules to claim the requests and to receive all subsequent requests associated with the type of information, the stateless module manager enabling the only one information module to receive the subsequent requests independent of an availability of other information modules; and

wherein said client device interface is adapted to receive a plurality of request types, said request types comprising;

on-demand requests, which are sent to said client device interface by a user of one of said remote devices when said user desires an on-demand response;

scheduled requests, which are sent to said client device interface by said user when said user desires a plurality of scheduled responses from a subscription service provided by one of said information modules; and

event driven requests, which are sent to said client device interface from one of said remote devices when certain criteria are met.

2. The distributed information processing system as recited in claim 1, wherein the requests to the device interface are formatted as an HTML or plain-text formatted e-mail or serializable Java objects.

3. The distributed information processing system as recited in claim 1, wherein the appropriate one of said plurality of information modules generates a response that is returned to said stateless module manager, and wherein said stateless module manager routes said response to said client interface device for delivery to a requestor.

4. The distributed information processing system as recited in claim 1, wherein the stateless module manager enables the one of the information modules to own the subsequent requests independent of which of the plurality of remote devices transmits the requests and the subsequent requests.

5. The distributed information processing system as recited in claim 1, wherein said requests are made to said stateless module manager as one of a synchronous or asynchronous request, wherein synchronous requests are handled on a first-in-first-out basis, and wherein asynchronous requests are processed and returned when completed.

6. The distributed information processing system as recited in claim 1, wherein instances associated with said stateless module manager are created each time a new request is received and discarded after the request has been handled.

7. The distributed information processing system as recited in claim 6, wherein instances associated with said stateless module manager are stateless and multi-threaded.

8. The distributed information processing system as recited in claim 1, wherein information modules are loaded locally and remotely, wherein local module processors reside on a same physical device as said stateless module manager processor, and wherein remote module processors are located on other devices.

9. The distributed information processing system as recited in claim 8, wherein communication between locally loaded module processors and said stateless module manager processor is accomplished via memory calls, object inheritance or inter-process communication.

10. The distributed information processing system as recited in claim 8, wherein communication between remotely loaded module processors and said stateless module manager is accomplished via TCP/IP sockets.

11. The distributed information processing system as recited in claim 1, wherein the subscription service further comprises a subscriber database, wherein information is sent by said information module, and said subscriber database is consulted to determine to which users of said remote devices the information should be forwarded.

12. A method of receiving and responding to requests for electronic information in a distributed information processing system, the method comprising:

receiving requests for a type of information at a client device interface;

forwarding said requests to a stateless module manager;

consulting a registry of available information modules; and

forwarding said requests to an appropriate information module as determined in accordance with the type of information requested;

handling service collisions if plural information modules are capable of responding to the requests, such that only one information module processes the requests, and enabling only one of the information modules to claim the requests and to own subsequent requests based on the type of information being common to each of the requests and the subsequent requests, the stateless module manager enabling the only one information module to receive the subsequent requests independent of an availability of other information modules;

wherein said client device interface is adapted to receive a plurality of request types, said request types comprising;

on-demand requests, which are sent to said client device interface by a user of one of said remote devices when said user desires an on-demand response;

scheduled requests, which are sent to said client device interface by said user when said user desires a plurality of scheduled responses from a subscription service provided by one of said information modules; and

event driven requests, which are sent to said client device interface from one of said remote devices when certain criteria are met.

13. The method of claim 12, further comprising:

maintaining a list of supported services provided by each of said information modules; and

registering said information modules for responding to requests for said type of electronic information.

14. The method of claim 12, wherein the one of the information modules owns the subsequent requests independent of a source of the requests and the subsequent requests.

15. The method of claim 12, wherein said requests are made to said stateless module manager as one of a synchronous or asynchronous request, wherein synchronous requests are handled on a first-in first-out basis, and wherein asynchronous requests are processed and returned when completed.

16. The method of claim 12, said method further comprising:

creating an instance of said stateless module manager upon receiving said request; and

discarding said instance after said response has been handled.

17. A computer readable medium containing computer executable instructions for receiving and responding to requests for electronic information in a distributed information processing system, said computer executable instructions for performing the steps of:

receiving requests for a type of electronic information at a client device interface;

forwarding said requests to a stateless module manager;

consulting a registry of available information modules;

forwarding said request to an appropriate information module as determined in accordance with the type of electronic information requested;

handling service collisions if plural information modules are capable of responding to the requests, such that only one information module processes the requests, and enabling only one of the information modules to claim the requests and to own subsequent requests based on the type of electronic information being common to each of the requests and the subsequent requests, the stateless module manager enabling the only one information module to receive the subsequent requests independent of an availability of other information modules;

wherein said client device interface is adapted to receive a plurality of request types, said request types comprising;

on-demand requests, which are sent to said client device interface by a user of one of said remote devices when said user desires an on-demand response;

scheduled requests, which are sent to said client device interface by said user when said user desires a plurality of scheduled responses from a subscription service provided by one of said information modules; and

event driven requests, which are sent to said client device interface from one of said remote devices when certain criteria are met.

18. The computer readable medium of claim 17, further comprising computer executable instructions for performing the steps of:

maintaining a list of supported services provided by each of said information modules.

19. The computer readable medium of claim 17, wherein the one of the information modules owns the subsequent requests independent of a source of the requests and the subsequent requests.

20. The computer readable medium of claim 17, wherein said requests are made to said stateless module manager as one of a synchronous or asynchronous request, wherein synchronous requests are handled on a first-in-first-out basis, and wherein asynchronous requests are processed and returned when completed.

21. The computer readable medium of claim 17, further comprising executable instructions for performing the steps of:

creating an instance of said stateless module manager upon receiving said request; and

discarding said instance after said response has been handled.