Combined internet and data access system

• US 5,974,443 A
• Filed: 09/26/1997
• Issued: 10/26/1999
• Est. Priority Date: 09/26/1997
• Status: Expired due to Term

• Current Assignee: Intervoice Limited Partnership
• Original Assignee: Intervoice Limited Partnership
• Inventors: Jeske, Charles E.
• Primary Examiner(s): Rinehart, Mark H.
• Assistant Examiner(s): Romero, Almari
• Application Number:
  US08/938,092
• Time in Patent Office: 760 Days
• Field of Search: 705/35, 705/42, 705/44, 707/4, 707/10, 707/102, 395/200.47, 395/200.48, 395/200.49, 395/200.62, 709/217, 709/218, 709/219, 709/232
• US Class Current: 709/202
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

The inventive system and method distributes information between databases and web servers, via a plurality of interconnected platforms or nodes. The invention includes a session manager, that is resident on only one platform and manages the information flow between the databases and the web servers. The invention also includes a plurality of data gateways, with at least one data gateway resident on each platform. The session manager uses a manager thread to determine which platform will operate on the request. A processing thread of the data gateway invokes an application module to create an application, which retrieves the requested information from the database. The processing thread translates the request into a format useable by the application. The processing thread retrieves a dynamic HTML template file and uses the information retrieved from the database to populate the HTML template file to form the response to the request, and passes the response onto the one global network server.

Claims

1. A system for distributing information between at least one database and at least one global network server, the system comprising:

a plurality of platforms, each connected between one or more databases and one or more global network servers;

a session manager, resident on only one platform of the plurality of platforms, for managing information flow between the at least one database and the at least one global network server; and

a plurality of data gateways, with at least one data gateway resident on each platform of the plurality of platforms, for reformatting an information request received from the at least one global network server, passing the reformatted information request onto the at least one database, reformatting a response from the at least one database, and passing the reformatted response onto the at least one global network server.

2. The system of claim 1, further comprising:

means for limiting a number of requests that each platform can have active at a time.

3. The system of claim 1, wherein the session manager comprises:

a manager thread for determining which of the plurality of platforms will operate on the request for information and be designated as an operating platform.

4. The system of claim 3, wherein the session manager further comprises:

a database for maintaining information about status of the plurality of platforms, types of requests that each platform is capable of handling, and information about each request that is currently operating on each platform;

wherein the manager thread consults the database in determining which of the plurality of platforms will operate on the request for information.

5. The system of claim 3, wherein:

the manager thread is temporarily connected to the at least one global network server.

6. The system of claim 1, wherein the session manager comprises:

a purge thread for canceling a session which includes the request, that has exceeded a predetermined idle time period.

7. The system of claim 1, wherein the session manager comprises:

platform thread for monitoring operational status of each of the platforms of the plurality of platforms, wherein said platform thread notifies said session manager about the operational status of a data gateway resident on any platform.

8. The system of claim 1, wherein:

said at least one database is a plurality of databases, each of which is connected to each platform of the plurality of platforms.

9. The system of claim 1, wherein:

said at least one global network server is a plurality of global network servers, each of which is connected to each platform of the plurality of platforms; and

the session manager manages the information flow between at least one database and each global network server of the plurality of global network servers.

10. The system of claim 3, wherein:

the at least one global network server connects with said designated operating platform, and passes the request for information to the at least one data gateway resident on said designated operating platform.

11. The system of claim 10, further comprising:

an application module for creating an application based on the request, wherein the application accesses the at least one database and retrieves the information.

12. The system of claim 11, wherein the at least one data gateway resident on the operating platform comprises:

a processing thread that receives the request from the at least one global server and invokes the application module.

13. The system of claim 12, wherein:

the processing thread translates the request into a format useable by the application.

14. The system of claim 13, wherein:

the processing thread resident on the at least one data gateway of said designated operating platform retrieves a dynamic template file and uses the information retrieved from the at least one database to populate the template file to form the response, and passes the response onto the at least one global network server.

15. The system of claim 14, wherein:

the template file is an HTML template file.

16. The system of claim 11, wherein the at least one data gateway resident on the operating platform comprises:

an application die thread that tracks a status of the application and informs the session manager when the application is terminated.

17. The system of claim 11, wherein:

the application self-terminates upon satisfaction of the request.

33. The system of claim 2, wherein said limiting number of requests is adjustable.

34. The system of claim 2, wherein said means for limiting further comprises:

a security key to control access to said means to allow only authorized personnel to change said limiting number.

35. The system of claim 14, wherein the template file comprises a declaration block, wherein said declaration block defines at least one output field.

36. The system of claim 35, wherein said at least one output field has an associated tag, wherein every reference of said associated tag is replaced with data retrieved by said processing thread.

18. A method for distributing information between at least one database and at least one global network server, with a plurality of platforms, each platform interconnected between one or more databases and one or more global network servers, one session manager that is resident on any one platform of the plurality of platforms, and a plurality of data gateways, with at least one data gateway resident on each platform of the plurality of platforms, the method comprising the steps of:

receiving an information request from at least one global network server;

determining, by said one session manager, which of the plurality of platforms will operate on the request for information and be designated as an operating platform;

routing the request to the operating platform;

reformatting, by the at least one data gateway resident on the operating platform, the request received from the at least one global network server;

passing, by the at least one data gateway resident on the operating platform, the reformatted information request onto the at least one database;

reformatting, by the at least one data gateway resident on the operating platform, a response from the at least one database;

passing, by the at least one data gateway resident on the operating platform, the reformatted response onto the at least one global network server; and

managing, by the session manager, information flow between the at least one database and the at least one global network server.

19. The method of claim 18, further comprising the step of:

limiting a number of requests that can be active at a time.

20. The method of claim 18, furthering the steps of:

maintaining information about status of the plurality of platforms, types of requests that each platform is capable of handling, and information about each request that is currently operating on each platform; and

using the maintained information in the step of determining which of the plurality of platforms will operate on the request for information.

21. The method of claim 18, further comprising the step of:

canceling a session which includes the request, that has exceeded a predetermined idle time period.

22. The method of claim 18, wherein the determining step further comprises the step of:

monitoring operational status of each of the platforms of the plurality of platforms; and

notifying said session manager about the operational status of a data gateway resident on any platform.

23. The method of claim 18, wherein:

said at least one database is a plurality of databases, each of which is connected to each platform of the plurality of platforms.

24. The method of claim 18, wherein said at least one global network server is a plurality of global network servers, each of which is connected to each platform of the plurality of platforms, and the method further comprises the step of:

managing, by the session manager, the information flow between at least one database and each global network server of the plurality of global network servers.

25. The method of claim 18, further comprising the steps of:

connecting the at least one global network server with said operating platform; and

passing the request for information to the at least one data gateway resident on the operating platform.

26. The method of claim 25, further comprising the steps of:

creating, by an application module, an application based on the request; and

accessing, by the application, the at least one database and retrieving the information.

27. The method of claim 26, further comprising the steps of:

receiving, by a processing thread resident on the at least one data gateway of the operating platform, the request from the at least one global server; and

invoking, by the processing thread, the application module.

28. The method of claim 27, further comprising the step of:

translating, by the processing thread, the request into a format useable by the application.

29. The method of claim 28, further comprising the steps of:

retrieving, by the processing thread, a dynamic template file;

populating, by the processing thread, the template file with the information retrieved from the at least one database to form the response; and

passing, by the processing thread, the response onto the at least one global network server.

30. The method of claim 29, wherein:

the template file is an HTML template file.

31. The method of claim 26, further comprising the steps of:

tracking, by an application die thread that is resident on the at least one data gateway of the operating platform, a status of the application; and

informing, by the application die thread, the session manager when the application is terminated.

32. The method of claim 26, further comprising the step of:

terminating the application upon satisfaction of the request.