JPH10177548A - Session management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable the same user to execute a plurality of applications in the same session in a client/server system without complicating the constitution of the application executed on a client computer side. SOLUTION: A network client module 107 on a client computer 105 establishes a network communication link 110 at every session between the module 107 and a network server module 103 on a server computer 101 and registers the link IDs and session information corresponding to the sessions on a client session management table 108. At the same time, the module 107 establishes a local communication link 109 between the module 107 and each application 106 and connects the local communication links 106 corresponding to a plurality of applications 106 having the same link ID to the same network communication link 110 by referring to the client session management table 108.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a session management technique in a client / server system.

[0002]

2. Description of the Related Art In a computer system including a network, a client / server system as shown in FIG. 6 is often constructed. In a client / server system, a client computer requests a service from a server computer,
A configuration is adopted in which a server computer provides a service to a client computer.

Here, when a service is provided from a server computer to a client computer,
Various functions of the service are provided in units called sessions. That is, a session is a series of processes or a set of processes executed on a client computer and a server computer. For example, one user on a client computer logs in to a service on a server computer and then logs out. A set of functions provided by the service before the service is provided.

Therefore, in a client / server system, it is necessary to manage information relating to a session using the system in real time. The information related to the session includes a user name, a client machine name, a context, and the like. Conventionally, the information related to the session is collectively managed on the server computer side.

Therefore, when a user on a client computer starts a new application (process group) from one application (process group) running on the client computer, the new application and the new application are executed. A new session had to be established with the server computer.

For example, when a user on a client computer starts a file transfer application or a database access application from one Internet browser application running on the client computer, the file transfer application or the database access application is activated by the Internet. Even if the browser application accesses the same server computer that the browser application is accessing, the file transfer application or database access application can access the server computer.
When accessing the computer, it was necessary to start over from the user authentication.

FIG. 7 is a configuration diagram of a conventional client / server system. The server computer 701 includes, for example, a server engine 702 that is a process (group) for providing a database or various processing groups, and a process (group) for providing a communication function via a network between the client computer and the server engine 702. Is executed with the network server module 703.

In the client computer 705,
Even if the user is the same, for each application 706 such as # 1 to # 4, the corresponding network client module 707 such as # 1 to # 4
# 1 to # 4 network communication links 7 with the network server module 703 in the computer 701
It was necessary to establish 09 and hold independent sessions for each.

In this case, the server computer 701
Has a session management table 704 that stores session information such as a link ID (session ID), a user name, a client machine name, and a context for each session. The session management table 704 includes a network client module 707 and a server computer 701 corresponding to each application 706 started on the client computer 705 even if the user is the same.
It manages all the sessions established with the above one network server module 703 via the network communication link 709.

[0010] Each network client module 707, as indicated by, for example, a mark * in FIG. 7, includes a link ID (session ID), a user name, Each table 708 holds information such as a server name and a network bind. Network binding is, for example, in a network communication protocol using sockets, a socket descriptor acquired by the network client module 707 from the operating system every time communication is established, a network address (Internet address) of the server computer 701, and a network. This is information describing the connection relationship between the server module 703 and a set of port numbers.

In the client / server system having the configuration shown in FIG. 7, as shown in FIG.
In the client computer 705, first, the application # 706 of # 1 is started by the user A (step 801), and then the network server module 703 on the server computer 701 by the user A
Is performed (step 802), and then the # 1 network client module 70
7, communication and various processes are performed between the # 1 application 706 and the server engine 702 on the server computer 701 via the # 1 network communication link 709 and the network server module 703.

Thereafter, the client computer 70
5, the same user A uses the application # 706 of # 1
When the application 706 of # 2 is started (step 804), the network server module 703 on the server computer 701 by the user A
Is again executed (step 80).
5). Then, via the network client module 707 of # 2, the network communication link 709 of # 2, and the network server module 703, the application 706 of # 2 and the server computer 701
Communication and various processes are performed with the server engine 702 above.

Finally, a logout process is performed by the user A (step 807), and all sessions relating to the user A are terminated.

[0014]

In order to avoid redundant network communication processing such as user authentication as described above, a plurality of applications executed by the same user on a client are executed in the same session. Such a mechanism is required.

When such a mechanism is generally assumed,
For each application, a new child process (application) is started from one parent process, and the parent process grasps all data communicated by the child process, and executes communication with the server on behalf of the child process. However, there is a problem that a complicated system design is required, and independence between applications cannot be maintained.

An object of the present invention is to make it possible to execute a plurality of applications by the same user in the same session without complicating the configuration of the application executed on the client computer side.

[0017]

The present invention presupposes a session management system in a client / server system in which a client computer requests a service from a server computer so that the server computer provides services to the client computer. And

First, client session management table means (client session management means) provided on the client computer for storing, for each session, link identification information for identifying the session and session information corresponding to the session. Management table 108).

Next, a network communication link is provided on the client computer for each session with the server computer, and link identification information (link ID) and session information corresponding to the session are transmitted to the client session. A plurality of applications having the same link identification information are registered in the management table means, establish a local communication link with each application executed on the client computer, and refer to the client session management table means. Network client module means (network client) for executing a plurality of applications under the same session by connecting a plurality of local communication links corresponding to each other to the same network communication link. With a cement-module 107).

In this case, each application executed on the client computer takes over the link identification information possessed by the predetermined application at the time of startup and, when connecting to the network client module means, transfers the link identification information. Notify the network client module means.

According to the present invention, there is provided a computer-readable storage medium which, when used by a computer operating as a client computer, causes the computer to perform the same functions as those realized by the configuration of the present invention. It can also be configured.

In the configuration of the invention described above, for example, a plurality of applications executed on the client computer by the same user inherit the same link identification information, so that communication between them and the server computer can be performed in the same manner. And can run on the same session by sharing the same network communication link. As a result, it is possible to avoid waste such as having to re-execute a login process with the server computer every time the application is started, thereby reducing the processing load on the server computer and reducing the network traffic. Can be planned.

Further, the mechanism for sharing the network communication link is completely processed by the network client module means independent of the application, and each application is provided with a mechanism for inheriting the link identification information and a network client module means. Since it is only necessary to provide a mechanism for establishing a local communication link, it is possible to avoid complication of the configuration of the application,
In addition, the independence between applications is not impaired. In addition,
The local communication link can be easily realized as an inter-process communication mechanism using a general socket, pipe, common memory, and the like. In addition, since the local communication link is established in the client computer, the There is no increase in traffic.

[0024]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a configuration diagram of an embodiment (client / server system) of the present invention.

The configuration of the server computer 101 is basically the same as the configuration of the server computer 701 in the conventional configuration shown in FIG. 7, for example, a process (group) for providing a database or various processing groups. A server engine 102 and a network server module 103 which is a process (group) for providing a communication function via a network between a client computer and a client computer are executed. The network server module 103 The management table 104 is managed.

On the other hand, the client computer 105
Now, a plurality of applications 106 executed there
A network client module 107 that centrally manages all network communication links 110 between the network server module 103 on the server computer 101 is executed.

The network client module 107 establishes a local communication link 109 with each application 106 executed on the client computer 105 as inter-process communication, and establishes the same link ID (described later). ), A plurality of local communication links 109 corresponding to a plurality of applications 106 (generally, a group of applications executed by the same user) are bundled, and a single network communication link 110 is provided between the network server module 103 and the network communication module 110. Assign.

In the embodiment shown in FIG. 1, # 1, # 2, and # 2 correspond to applications # 1, # 2, and # 3, which are executed by user A and have a common link ID 111 (# 1). Each of the # 3 local communication links 109 is assigned to the # 1 network communication link 110 and executed by the user B, and has the link ID 111 (# 2), and corresponds to the # 4 application 106 and has the # 4 local communication link. 10
9 is assigned to the network communication link 110 of # 2.

Network client module 1
07 is started as a single daemon process on the client computer 105, for example, and each time a new network communication link 110 is established, a new process ( Or a thread).

The network client module 107 has a client client as shown in FIG.
The session management table 108 is managed. This table holds information such as a link ID (session ID), a user name, a server name, and a network bind for each network communication link 110 (for each session).

As described above, in the embodiment of the present invention, for example, a plurality of applications 106 executed by the same user inherit the same link ID.
Communication between them and the network server module 103 can be performed on the same session, sharing the same network communication link 110. As a result, it is possible to avoid waste such as having to re-execute a login process with the network server module 103 every time the application 106 is started, and to reduce the processing load on the network server module 103. Network traffic can be reduced.

The network communication link 110 is shared by a network client module 107 independent of the application 106, and each application 106 has a link ID inheriting mechanism and a network client module 107. It is only necessary to provide a mechanism for establishing a local communication link 109, so that the configuration of the application 106 can be prevented from becoming complicated, and the independence between the applications 106 is not impaired. The local communication link 109 can be easily realized as a general inter-process communication mechanism using a socket or the like.
Since it is set in the network 05, there is no increase in network traffic.

In the client / server system according to the embodiment of the present invention having the configuration shown in FIG. 1, first, as shown in FIG. After being activated (step 201), the user A performs a log-in process to the server computer 101 (step 202), and then the # 1 local communication link 109, the network client module 107, and the # 1 network communication link. 109 and # 1 via the network server module 103
Application 106 and server computer 10
Communication and various processes are performed with the server engine 102 on the first server.

Thereafter, the client computer 10
5, application # 1 by the same user A # 10
When the application 106 of # 2 is activated from Step 6 (Step 205), the application 106 of # 1 is started.
The link ID assigned to the # 1 application 106 is delivered to the # 2 application 106 from (step 204).

As a result, the application 106 of # 2
Does not require the user A to execute the log-in process to the server computer 101 again, and the local communication link 109 of # 2, the network client module 107, the network communication link 109 of # 1, and the network server module 103 Through the application 106 of # 2 and the server computer 101
Communication and various processes can be performed with the server engine 102 above (step 206).

Finally, the logout process by the user A is executed (step 207), and the execution of the applications 106 of # 1 and # 2 relating to the user A ends. If the execution of one of the applications 106 is continued, the logout process is not required.

FIG. 3 shows a client / server system according to an embodiment of the present invention having the configuration shown in FIG.
3 is an operation flowchart in a case where the user first logs in to the server computer 101 (corresponding to steps 201 and 202 in FIG. 2) after activating the application # 1 above.

First, the user A executes a login information input process on the application 106 of # 1 (step 301), and the network client module 1
At 07, a login request is issued (step 302).
More specifically, for example, using a network communication protocol using sockets, the application # 1 obtains a socket descriptor from the operating system, and then obtains the socket descriptor and the socket name provided by the network client module 107. (File path name) and
Issues a connect system call to the operating system. This creates a UNIX domain binding for the # 1 local communication link 109. The # 1 application 106 uses the # 1 local communication link 109 to specify a network
A login request is issued to the module 107. In this sense, the network client module 107
Operates as a server in the inter-process communication using the UNIX domain sket for each application 106.

As a result, the network client module 107 creates a network binding for the network communication link 110 of # 1 (step 303). More specifically, for example, using a network communication protocol using a socket, the network client module 107 obtains a socket descriptor from the operating system, and then acquires the socket descriptor and the network address (internet address) of the server computer 101. ) And the network server module 103
Issue a connect system call to the operating system with the set of port numbers as arguments. As a result, a network binding (internet domain binding) relating to the # 1 network communication link 110 is created, and thereafter, the network client module 107 specifies the above-described socket descriptor to specify the # 1 network communication link 11.
0 can be used to communicate with the network server module 103 on the server computer 101.

Subsequently, the network client module 107 transmits the login request issued by the # 1 application 106 to the # 1 network communication link 110.
To the network server module 103 on the server computer 101. More specifically, for example, by using a network communication protocol using a socket, the network client module 107 sends a call system call specifying the character string of the login request and the socket descriptor of the network communication link 110 of # 1. To the operating system. Alternatively, after opening the file by designating the socket descriptor of the network communication link 110 of # 1, a write system call designating the file descriptor and the character string of the login request is issued to the operating system.

The network server module 103 on the server computer 101 sends a # 1 network communication link 110 from the client computer 105.
The user authentication process is executed by receiving the login request via (step 304). More specifically, for example, using a network communication protocol using sockets, the network server module 103 performs liste
After issuing the n system call and the accept system call, when the operating system returns a socket descriptor corresponding to the # 1 network communication link 110, a new process for processing the # 1 network communication link 110 ( Or a thread) is started (forked), and a character string of the login request is received by issuing a recv system call specifying the above-described socket descriptor to the operating system on the process (or thread). Alternatively, the network server module 103 opens the file by specifying the socket descriptor on the process (or thread), and then issues a read system call specifying the file descriptor to the operating system to execute the login. Receive the request string. Then, the network server module 103 executes the process (or thread)
Above, by referring to the user authentication file registered in advance for the character string of the login request,
Perform user authentication.

Network server module 103
Issues a link ID 111 (# 1) which is an identifier for a new session corresponding to the network communication link 110 of # 1 when the user authentication is successful (step 305 in FIG. 3). As the link ID, for example, a process ID of a process for processing the above-described # 1 network communication link 110 is set.

Next, the network server module 1
03 is the link ID 111 (# 1), user name,
The session information such as the client machine name and the context is stored in the session management table 10 shown in FIG.
4 (step 306 in FIG. 3).

Subsequently, the network server module 103 uses the network communication link 110 of # 1 to notify the network client module 107 of the client computer 105 of the success of the user authentication and the link ID 111 (# 1). ).

Network client module 1
07, upon receiving this notification, the notified link ID
111 (# 1), the user name A that has successfully logged in, the server name of the server computer 101, and the network bind are registered in the client session management table 108 of FIG. 1 (step 307).

Thereafter, the # 1 application 106
Local communication link 109, network client module 107, network communication link # 1
09 and the network server module 103, it is possible to execute communication and various processes between the application # 1 106 and the server engine 102 on the server computer 101.

In the above-described series of login processing, in the client / server system, the user B
6 is started, first, the server computer 101
The same is true when logging in to.

FIG. 4 shows a client / server system in a client / server system according to an embodiment of the present invention having the configuration shown in FIG.
After launching application # 1 above,
The application 106 of # 2 is further activated from the application 106 of # 1 (step 205 → 2 in FIG. 2).
It is an operation flowchart in the case (corresponding to 06).

First, the application 106 of # 2 (# 3)
When the application is started, the # 1 (# 2) application 106
The link ID 111 (# 1) assigned to the # 1 application 106 is delivered to the (# 3) application 106.

Next, the application 106 of # 2 (# 3)
Assigns the link ID 111 (# 1) and issues a processing instruction (step 401). When the # 2 (# 3) application 106 first accesses the network client module 107, the # 2 local communication link 109 is established (step 402). For example, using a network communication protocol using a socket, a more specific description will be given. Application # 2 (# 3)
06, after acquiring the socket descriptor from the operating system, using the socket descriptor and the socket name (file path name) provided by the network client module 107 as arguments,
Issues a connect system call to the operating system. This creates a UNIX domain binding for the # 2 (# 3) local communication link 109. The application 106 of # 2 (# 3) specifies the above-mentioned socket descriptor to
Using the local communication link 109 of (# 3), the link I
A processing instruction to which D111 (# 1) is assigned is issued.

Network client module 1
07 receives the processing instruction to which the link ID 111 (# 1) is added from the local communication link 109 of # 2 (# 3), from the client session management table 108 using the link ID 111 (# 1) as a key. A network binding is obtained (step 403).

Then, the network client module 107 connects the network communication link 110 corresponding to the acquired network binding with the above-described # 2 (#
The application 106 of # 2 (# 3) and the network server module 103 are connected using the local communication link 109 of step 3) (step 404).

As a result, application 1 of # 2 (# 3)
The processing instruction issued in 06 is transferred to the server engine 102 via the local communication link 109 of # 2 (# 39, the network client module 107, the network communication link 109 of # 1, and the network server module 103). Are processed there (step 405).

It should be noted that the processing command is given the ID (for example, process ID) of the application 106 that executes the processing command, so that the network client module 107 and the server engine 602 are provided.
Can identify the application 106.

At the end of the process, the # 2 (# 3) application 106 disconnects the # 2 (# 3) local communication link 109 and closes the process (step 40).
6). As described above, when the user A executes and terminates the application # 2 (# 3) # 2 (# 3), it is not necessary to execute the log-in process and the log-out process to the server computer 101 again. It is a big feature.

FIG. 5 shows one network communication link 1
10 is an operation flowchart of a logout process at the time of termination of the last application 106 sharing the application 10. For example, a case where the # 1 application 106 executes the logout process will be described below as an example.

First, the user A executes a process of inputting logout information on the # 1 application 106 (step 501), and issues a logout request to the network client module 107 (step 50).
2).

As a result, the network client module 107 starts the # 1 network communication link 110
ID 111 (# 1) for notifying the closing of
Is notified to the network server module 103 (step 503).

Network server module 103
Receives the close notification, deletes the entry (session information) corresponding to the link ID 111 (# 1) included in the close notification from the session management table 104 (step 504).

Thereafter, the process (or thread) of the network server module 103 that has been processing the network communication link 110 of # 1 corresponding to the link ID 111 (# 1) is closed (step 505).

On the other hand, after transmitting the close notification to the network server module 103, the network client module 107 transmits the link ID 111 (# 1).
Is deleted from the client / session management table 108 (step 506).

Thereafter, the process (or thread) of the network client module 107 that has been processing the network communication link 110 of # 1 corresponding to the link ID 111 (# 1) is closed (step 507).

The present invention relates to a computer readable storage such as a floppy disk, a CD-ROM disk, an optical disk, or a portable (removable) hard disk which stores a computer program for realizing the functions of the client computer in the above embodiment. It may be configured as a medium.

[0064]

According to the present invention, for example, a plurality of applications executed on a client computer by the same user inherit the same link identification information, so that communication between them and a server computer can be performed. The same network communication link can be shared and run on the same session. As a result, it is possible to avoid waste such as having to re-execute a login process with the server computer every time the application is started, thereby reducing the processing load on the server computer and reducing the network traffic. It becomes possible to plan.

The mechanism for sharing the network communication link is completely processed by the network client module means independent from the application, and each application is provided with a mechanism for inheriting the link identification information and a network client module means. Since it is only necessary to provide a mechanism for establishing a local communication link, it is possible to avoid complication of the configuration of the application,
In addition, the independence between applications is not impaired. In addition,
The local communication link can be easily realized as an inter-process communication mechanism using a general socket, pipe, common memory, and the like. In addition, since the local communication link is established in the client computer, the There is no increase in traffic.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a diagram illustrating an execution relationship of an application according to the embodiment of the present invention.

FIG. 3 is an operation flowchart (1) of the embodiment of the present invention.

FIG. 4 is an operation flowchart (part 2) of the embodiment of the present invention.

FIG. 5 is an operation flowchart (3) of the embodiment of the present invention.

FIG. 6 is a conceptual diagram of a client / server system.

FIG. 7 is a configuration diagram of a conventional client / server system.

FIG. 8 is a diagram showing an application execution relationship in a conventional client / server system.

[Explanation of symbols]

 101 server computer 102 server engine 103 network server module 104 session management table 105 client computer 106 application 107 network client module 108 client session management table 109 local communication link 110 network communication link 110

Claims (3)

[Claims] Claims: 1. A client computer comprises a server computer.
A session management system in a client / server system in which a server computer provides a service to a client computer by requesting a service from the computer, wherein the session management system is provided on the client computer and identifies the session for each session. Client session management table means for storing link identification information and session information corresponding to the session, provided on the client computer, and establishing a network communication link for each session with the server computer. Establishing the link identification information and session information corresponding to the session
Register in the session management table means, establish a local communication link with each application executed on the client computer, and refer to the client session management table means and have the same link identification information Network client module means for executing the plurality of applications under the same session by connecting the plurality of local communication links corresponding to the plurality of applications to the same network communication link. Characterized session management system. 2. The application takes over the link identification information of the application from a predetermined application at the time of startup, and notifies the network client module means of the link identification information when connecting to the network client module means. The session management system according to claim 1, wherein 3. The client computer is a server computer.
A storage medium read by a computer operating as a client computer in a client / server system in which a server computer provides a service to a client computer by requesting a service from the computer. A function for generating, for each session, link identification information for identifying the session, a client session management table storing session information corresponding to the session, and a network for each session with the server computer. A function of establishing a communication link and registering the link identification information and the session information corresponding to the session in the client session management table; and a function executed on the client computer. A local communication link is established between each application and the plurality of local communication links corresponding to a plurality of applications having the same link identification information by referring to the client session management table. And a computer-readable storage medium for causing the computer to execute the plurality of applications under the same session by connecting to a network communication link.