Management facility for server entry and application utilization in a multi-node server configuration

• US 5,553,239 A
• Filed: 11/10/1994
• Issued: 09/03/1996
• Est. Priority Date: 11/10/1994
• Status: Expired due to Term

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Heath, David M., Pant, Sangam, Kraley, Michael F.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Decady, Albert
• Application Number:
  US08/337,943
• Time in Patent Office: 663 Days
• Field of Search: 395/575, 395/325, 395/725, 395/275, 395/800, 395/187.01, 395/186, 395/188.01, 395/187, 395/200.01, 395/200.02, 395/200.12, 395/200, 395/821, 395/840 , 395/856, 395/892, 395/280, 364/238.3, 364/228.3, 364/242.94, 364/286.4, 364/286.5, 380/4, 380/25
• US Class Current: 726/2
• CPC Class Codes: G06F 2209/5011 Pool
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06Q 20/085 involving remote charge determination or related payment systems
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1439 time-based
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Disclosed is a server architecture for connecting to a plurality of remote client computers each seeking access to applications resident on the server. The architecture provides (1) a reliable, single point of entry for client users that enforces security and recovers immediately from failures; (2) connection management that monitors the user'"'"'s level of online activity, terminating inactive connections both to save system resources and to limit unnecessary connection charges to the user; (3) application management that spreads users optimally among active application instances, maintaining a pool of available applications, initiating new instances when the pool is low, and which records a user'"'"'s utilization of different applications for billing purposes; (4) system integrity, which is achieved through division of transaction-management responsibility among the various interrelated components of the invention; and (5) continuous, uninterrupted operation. The invention distributes tasks to different functional modules in a manner that promotes efficiency and ready accommodation of large numbers of users without processing delays.

Claims

1. Apparatus for managing access to applications, resident on a central host computer, by a plurality of clients, the apparatus comprising:

a. communication means for establishing and maintaining physical telecommunication connections between the host and a plurality of clients, each connection being capable of supporting a plurality of logical connections;

b. a computer memory;

c. an entry manager for controlling access to the host after establishment of a physical connection between a client and the host via the communication means by;

i. obtaining sufficient information from the client to facilitate establishment of a logical connection thereto; and

ii. storing the information in the computer memory; and

d. a process server, operatively coupled to the entry manager, for;

i. establishing a logical connection to the client using the stored information;

ii. awaiting receipt of a valid password and a valid user name from the client;

iii. receiving, from the client, at least one request for connection to an application resident on the host, the application being capable of supporting a plurality of logical connections;

iv. causing establishment of a logical connection between each requested application and the client; and

v. terminating the physical connection if a valid password and a valid user name are not received.

2. The apparatus of claim 1 further comprising a master database containing valid passwords and valid user names, and against which the process server checks, for validity, the password and the user name received from the client.

3. The apparatus of claim 2 wherein the master database further contains client privilege levels, and further wherein the process server determines, from the privilege level associated with the client, whether the client is entitled to access to the requested application.

4. The apparatus of claim 1 wherein the process server establishes the logical connection between the client and an instance of the requested application by:

a. identifying any currently running instances of the requested application;

b. if any running instances are identified, determining;

i. a maximum number of clients logically connectable to each running instance;

ii. the number of clients currently logically connected to each running instance;

iii. whether any running instances have a maximum number of logically connected clients that exceeds the number of currently logically connected clients; and

if so,

c. identifying an optimal running instance as that instance whose maximum number of logically connected clients least exceeds the number of currently logically connected clients;

d. if no running instances are identified, causing a new instance of the requested application to be started; and

e. establishing a logical connection between the client and the optimal running instance or the new instance.

5. The apparatus of claim 4 further comprising an application database associated with the process server, the application database containing, for each application executable on the server, a record comprising an application name, a server location, a type, an optimal limit on the number of users logically connected to the application, and a maximum limit on the number of users logically connected to the application.

6. The apparatus of claim 5 wherein the process server determines the maximum number of clients logically connected to each running instance by locating the database record corresponding thereto.

7. The apparatus of claim 1 wherein each logical connection has a duration and further comprising a circuit database associated with the process server, the circuit database containing, for each logical connection between an application and the client, an identifier corresponding to the application and the duration of the logical connection.

8. The apparatus of claim 1 wherein the process server sends keep-alive messages to the client, which, in response, sends echo messages back to the process server, and further wherein the process server terminates the physical connection if a predetermined time is exceeded between a keep-alive message and an echo message.

9. The apparatus of claim 4 further comprising an application manager, wherein the process server sends keep-alive messages to the client, which, in response, sends echo messages back to the process server, and further wherein, if a predetermined time is exceeded between keep-alive messages, the process server terminates the physical connection and the application manager terminates each logical connection between the connection and an application.

10. The apparatus of claim 8 wherein the predetermined time is one minute.

11. The apparatus of claim 9 wherein the predetermined time is one minute.

12. The apparatus of claim 1 wherein the entry manager comprises an active master entry manager and an inactive slave entry manager, the slave entry manager becoming active upon malfunction of the master entry manager.

13. The apparatus of claim 9 wherein the entry manager, process server and application manager reside on a server containing a plurality of nodes.

14. The apparatus of claim 13 wherein the apparatus contains a single active entry manager and each node contains a plurality of process servers and application managers, each process server being associated with a single application manager on any one node.

15. The apparatus of claim 13 wherein the system isolates instances of applications from one another.

16. The apparatus of claim 1 wherein the entry manager establishes a logical connection to the client in order to obtain the connection information, and breaks the logical connection after obtaining said information.

17. A method of managing access to applications, resident on a central host computer, by a plurality of clients, the method comprising the steps of:

a. establishing a physical telecommunication connection between the host and a client;

b. establishing a logical connection between the host and the client;

c. causing the host to await receipt of a valid password and a valid user name from the client;

d. causing the host to receive, from the client, at least one request for connection to an application resident on the host, the application being capable of supporting a plurality of logical connections;

e. causing establishment of a logical connection between each requested application and the client over the physical connection; and

f. terminating the physical connection if a valid password and a valid user name are not received.

18. The method of claim 17 further comprising the step of determining a privilege level associated with the client and, based thereon, determining whether the client is entitled to access to the requested application.

19. The method of claim 17 further comprising the steps of:

a. identifying any currently running instances of the requested application;

b. if any running instances are identified, determining;

i. a maximum number of clients logically connectable to each running instance;

ii. the number of clients currently logically connected to each running instance;

iii. whether any running instances have a maximum number of logically connected clients that exceeds the number of currently logically connected clients; and

if so,

c. identifying an optimal running instance as that instance whose maximum number of logically connected clients least exceeds the number of currently logically connected clients;

d. if no running instances are identified, starting a new instance of the application; and

e. establishing a logical connection between the client and the optimal running instance or the new instance.

20. The method of claim 17 wherein the server sends keep-alive messages to the client, which, in response, sends echo messages back to the server, and further comprising the step of terminating the physical connection if a predetermined time is exceeded between a keep-alive message and an echo message.

21. The method of claim 20 wherein the predetermined time is one minute.