JP2015121932A - Session management system, service provision apparatus, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow a user who logs in to a service and runs a session with one of a plurality of service provision apparatuses to resume the session with the same service provision apparatus when the user logs in again to the service later.SOLUTION: A generator unit 24, when identification information of a user is included in a request received by a reception unit 18, generates context information specific to the authenticated user using the identification information, and a determination unit 26 determines presence of context information identical to the generated context information in a common database. When identical context information is not present, a transmission unit 28 stores the context information in association with a session ID of its own apparatus and sends a response to a session management server 4 and, when determined to be present, sends a response with the session ID associated with the context information to the session management server 4.

Description

  The present invention relates to a session management system, a service providing apparatus, and a program.

  Patent Document 1 below discloses a load balancer that always sends a request from a client to the same server by providing information about the server selected first as a cookie to the client.

US Pat. No. 6,473,802

  An object of the present invention is to enable a user who logs in to a service to proceed with a session that has proceeded with one of the plurality of service providing apparatuses, when the user logs in to the service later. It is to be able to proceed again with the providing device.

  The invention described in claim 1 for solving the above-described problem includes a session management device, a plurality of service providing devices that provide the same type of service, and a database, wherein the session management device transmits from the client device. A request receiving means for receiving the received request data, a request sending means for sending the request data received by the request receiving means to a service providing device specified by the session information in the request data, and the request sending means After the request data is transmitted, response data returned from the service providing apparatus that is the transmission destination of the request data is received, and the received response data is transmitted along with session information that identifies the service providing apparatus that is the transmission destination. Transfer to the sending client device Transfer means, wherein the service providing apparatus includes receiving means for receiving request data transmitted from the session management apparatus, and user identification information for identifying a user in the request data received by the receiving means. In response to the request, the authentication unit authenticates the user identified by the user identification information and the response data corresponding to the request data received by the receiving unit is transmitted to the session management device based on the user identification information. A response transmission means, wherein the response transmission means, when the request data received by the reception means includes user identification information for identifying a user, based on the user identification information Generating means for generating user information specific to the user authenticated by the authenticating means; Determining means for determining whether the same user information as the user information generated by the generating means is stored in the database; and storing the same user information as the user information generated by the generating means in the database. If it is determined that the user information is not stored, the user information is stored in the database in association with the session information that identifies the device, and the response data corresponding to the request data is transmitted to the session management device; A session that is stored in the database in association with the user information, when it is determined that the same user information as the user information generated by the generating unit is stored in the database Means for transmitting to the session management device together with information. The transfer means receives the response data from the service providing apparatus to which the request data is sent after sending the request data by the request sending means, and provides the received response data to the service to the destination. A session management system is characterized in that, instead of session information for specifying a device, session information received together with the response data is transferred to a client device that is a transmission source of the request data.

  According to a second aspect of the present invention for solving the above-mentioned problem, the request data received from the client device by the session management device is received by the receiving means for receiving from the session management device, and the request data received by the receiving means. Authentication means for authenticating a user identified by the user identification information based on the user identification information when the user identification information for identifying the user is included, and a response according to the request data received by the receiving means Response transmitting means for transmitting data to the session management device, wherein the response transmitting means includes the user identification information when the request data received by the receiving means includes user identification information for identifying the user. Generate user information specific to the user authenticated by the authentication means based on the information Generating means, determining means for determining whether or not the same user information as the user information generated by the generating means is stored in the database, and the same user information as the user information generated by the generating means Means for storing the user information in the database in association with the session information for specifying the own device and transmitting response data corresponding to the request data to the session management device when it is determined that the user information is not stored in the database If the same user information as the user information generated by the generating unit is determined to be stored in the database, response data corresponding to the request data is stored in the database in association with the user information. With the session information to be transmitted to the session management device A service providing apparatus including a.

  The invention according to claim 3 for solving the above-mentioned problem is characterized in that the computer receives the request data received from the session management apparatus by the session management apparatus from the client management apparatus, and the request received by the reception means. Authentication means for authenticating a user identified by the user identification information based on the user identification information when the user identification information for identifying the user is included in the data, according to the request data received by the receiving means A program for causing response data to function as response transmission means for transmitting response data to the session management device, wherein the response transmission means includes user identification information for identifying a user in the request data received by the reception means The authentication means based on the user identification information. Generating means for generating user information unique to the certified user, determining means for determining whether or not the same user information as the user information generated by the generating means is stored in the database, and the generating means When it is determined that the same user information as the generated user information is not stored in the database, the user information is stored in the database in association with the session information for specifying the own device, and in response to the request data. If it is determined that the same user information as the user information generated by the means for transmitting the response data to the session management device and the generation means is stored in the database, the response data corresponding to the request data Session information stored in the database in association with the user information Moni, a program and means for transmitting to the session management device.

  According to the first to third aspects of the present invention, a user who logs in to a service proceeds with a service providing device among a plurality of service providing devices, and the user later logs in to the service again. Sometimes, it is possible to proceed with the one service providing apparatus again.

It is a figure which shows the structure of the session management system which concerns on embodiment of this invention. It is a sequence diagram which shows the process performed with a session management system. It is a figure which shows the transfer process performed in a session management server. It is a figure which shows a login screen. It is a figure which shows a setting screen. It is a figure which shows a guidance screen. It is a figure which shows an instruction | indication waiting screen. It is a sequence diagram which shows the process performed with a session management system. It is a figure which shows the 1st reply process performed with a service provision server. It is a figure which shows the response transmission process performed in a session management server. It is a figure which shows the 2nd reply process performed with a service provision server. It is a sequence diagram which shows the process performed with a session management system. It is a sequence diagram which shows the process performed with a session management system. It is a functional block diagram which shows the function group implement | achieved by a session management system.

  Hereinafter, examples of embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a configuration of a session management system 1 according to the embodiment of the present invention. As shown in FIG. 1, the session management system 1 includes a plurality of client devices 2, a session management server 4, a plurality of service providing servers 6 for providing information processing services, and a shared database 10. Each of these devices is connected to a network.

  A browser application is installed in the client device 2, and the user logs in to the information processing service via the browser application and advances an HTTP session for using the information processing service. In the case of the present embodiment, the client device 2a is assumed to be a personal computer including a microprocessor, a storage device such as a memory and a hard disk, an input device such as a mouse and a keyboard, a network interface, and a display. The client device 2b is an image processing device including a microprocessor, a storage device such as a memory and a hard disk, a network interface, a touch screen, and a scanner.

  The session management server 4 and the service providing server 6 are server computers including a microprocessor, a storage device such as a memory and a hard disk, a network interface, and the like. Each of the session management server 4 and the service providing server 6 executes information processing according to a program stored in the storage device. This program may be stored in the storage device by being received from the network, or may be stored in the storage device by being read from a computer-readable information storage medium. The session management server 4 is also called a load balancer. Each service providing server 6 provides a common information processing service to the user on the cloud. In this embodiment, the service providing server 6 provides the user with an image processing service for translating a document image sent from the client device 2. . Each service providing server 6 is connected to a user database 8. The user database 8 stores user authentication information (user name (user identification information) and password) registered as a user of the service in the user database 8. User authentication is performed using.

  The shared database 10 is a database shared by each service providing server 6, and context information described later is stored in association with a session ID for identifying the service providing server 6. Here, it is assumed that no context information is stored in the shared database 10.

  The usage scene of the image processing service will be described. In the present embodiment, the user starts a browser application in the client device 2 and inputs a URL (Uniformed Resource Locator) of a login screen at a predetermined location. FIG. 2 is a sequence diagram showing processing executed in the session management system 1 when the URL of the login screen is input. Hereinafter, the client device 2 in which the URL of the login screen is input is referred to as a client device X. When the user inputs the URL of the login screen, the client device X transmits an HTTP request (request data) to the session management server 4 via the browser application (S101). The HTTP request includes various data such as cookie information held in the storage device by the client device X. Here, since the client device X does not hold the cookie information, the HTTP request does not include the cookie information.

  The session management server 4 receives the HTTP request transmitted from the client device X. Then, the received HTTP request is transferred to the service providing server 6 selected according to a predetermined algorithm (for example, round robin algorithm) (S102). Specifically, when receiving an HTTP request, the session management server 4 executes the transfer process shown in FIG. That is, the session management server 4 determines whether or not the session ID is included in the cookie information in the HTTP request (S201).

  As described above, at this stage, there is no cookie information in the HTTP request. Therefore, the session management server 4 selects the transfer destination service providing server 6 according to the above algorithm, and transfers the HTTP request to the selected service providing server 6 (S202). Here, it is assumed that the service providing server X is selected.

  The service providing server X that has received the HTTP request returns an HTTP response corresponding to the received HTTP request to the session management server 4 (S103). At this stage, the web page of the login screen is returned as an HTTP response. Then, the session management server 4 that has received the HTTP response transfers the received HTTP response to the client device X together with the session ID that identifies the service providing server X that is the transmission source of the HTTP response (S104). The session ID is included in the HTTP response as cookie information.

  In the client device X that has received the HTTP response, a login screen is displayed. In addition, cookie information in the HTTP response is stored in the storage device. FIG. 4A is a diagram illustrating an example of a login screen. Using this login screen, the user logs in to the image processing service. That is, the user inputs his / her authentication information (user name and password) on the login screen. Then, a predetermined button is pressed.

  FIG. 5 is a sequence diagram illustrating processing executed in the session management system 1 when the user presses the predetermined button on the login screen. The client device X transmits an HTTP request including the cookie information stored in the storage device and the input authentication information to the session management server 4 (S301). When the session management server 4 (request receiving means, request transmitting means) receives the HTTP request transmitted from the client device X, it transfers the received HTTP request to the service providing server X (S302). Specifically, in S302, the transfer process shown in FIG. 3 is executed. At this stage, the session ID is included in the cookie information. For this reason, the step of S203 is executed, and the session management server 4 transfers the HTTP request to the service providing server X identified by the session ID in the cookie information (S203).

  The service providing server X (receiving means) receives the HTTP request transferred from the session management server 4. This HTTP request includes authentication information. Therefore, the service providing server X (authentication unit) authenticates the user based on the authentication information in the HTTP request and the stored contents of the user database 8 (S303). Specifically, the service providing server X determines whether or not the authentication information in the HTTP request is stored in the user database 8. When the user is authenticated, the service providing server X (generating unit) generates context information specific to the authenticated user according to a predetermined context generation algorithm based on the authentication information in the HTTP request (S304). For example, the service providing server X generates the context information by encrypting the user name of the authenticated user. Note that the context generation algorithm used for generating the context information is common to all the service providing servers 6.

  Then, the service providing server X returns a redirect instruction as an HTTP response together with the context information to the session management server 4 (S305). Specifically, the service providing server X executes a first reply process shown in FIG. 6 in S305. That is, the service providing server X (determination unit) determines whether the same context information as the context information generated in S304 is stored in the shared database 10 (S401). As mentioned above, no context information has yet been stored in the shared database. Therefore, the service providing server X stores the context information generated in S304 in the shared database 10 in association with the session ID for identifying itself (S402), and uses the HTTP response as a redirect instruction together with the context information generated in S304. Is transmitted to the session management server 4 (S403). Note that the context information is included in the HTTP response as cookie information.

  Upon receiving the HTTP response in step S306, the session management server 4 (transfer means) transfers the received HTTP response to the client device X together with the session ID of the service providing server X that is the transmission source of the HTTP response ( S306). Specifically, in S306, the session management server 4 executes a response transmission process shown in FIG. That is, the session management server 4 determines whether or not the session ID is included in the cookie information included in the HTTP response (S501). At this stage, the session ID is not included in the cookie information. Therefore, the session management server 4 transfers the HTTP response to the client device X together with the session ID of the service providing server X that is the transmission source of the HTTP response (S502). The session ID is included in the HTTP response as cookie information.

  The client device X that has received the HTTP response stores the cookie information in the HTTP response in the storage device. Then, an HTTP request including cookie information is transmitted to the session management server 4 (S307). The cookie information includes the session ID of the service providing server X and context information.

  When the session management server 4 (request receiving unit, request transmitting unit) receives the HTTP request transmitted from the client device X, it transfers the received HTTP request to the service providing server X (S308). Specifically, the session management server 4 (request transmission means) executes the transfer process shown in FIG. 3 in S308. At this stage, the session ID of the service providing server X is included in the cookie information. Therefore, S203 is executed, and the session management server 4 transfers the HTTP request to the service providing server X identified by the session ID in the cookie information included in the HTTP request (S203).

  The service providing server X (receiving means) receives the HTTP request transferred from the session management server 4. Then, an HTTP response is returned to the session management server 4 together with the context information in the HTTP request (S309). At this stage, context information is included in the HTTP request. Therefore, the service providing server X executes the second reply process shown in FIG. 8 in step S309. That is, in the present embodiment, the storage device of each service providing server 6 is provided with a context management database (hereinafter referred to as a context management DB) in which context information and session progress indicating session progress are associated with each other. It is done. The service providing server X determines whether the same context information as the context information in the cookie information is stored in the context management DB (S601). At this stage, the same context information as the context information in the cookie information is not stored in the context management DB. Therefore, the context information in the cookie information is stored in the context management DB in association with the session progress indicating the progress of the session at the current stage (S602). In addition, a predetermined HTTP response is transmitted to the session management server 4 together with the context information in the cookie information (S603). Specifically, the service providing server X transmits the web page of the setting screen illustrated in FIG. 4B as an HTTP response. Note that the context information is included in the HTTP response as cookie information.

  Upon receiving the HTTP response in step S310, the session management server 4 (transfer means) transfers the received HTTP response to the client apparatus X together with the session ID of the service providing server X that is the transmission source of the HTTP response ( S310). Specifically, in S310, the session management server 4 executes a response transmission process shown in FIG. Here, since the session ID is not included in the HTTP response, the step of S502 is executed, and the HTTP response is transferred together with the session ID of the service providing server X (S502). As a result, the client device X that has received the HTTP response displays a screen corresponding to the HTTP response. At this stage, the setting screen shown in FIG. 4B is displayed. In addition, cookie information in the HTTP response is stored in the storage device.

  Thereafter, the user performs an operation of advancing a session with the service providing server X in the client device X until the guidance screen illustrated in FIG. 4C is displayed. In the session management system 1, the process shown in the sequence diagram of FIG.

  That is, the client device X transmits an HTTP request including cookie information held in the storage device to the session management server 4 (S701). The cookie information includes the session ID of the service providing server X and context information.

  When the session management server 4 (request receiving unit, request transmitting unit) receives the HTTP request transmitted from the client device X, the session management server 4 transfers the received HTTP request to the service providing server X (S702). Specifically, the session management server 4 (request transmission unit) executes the transfer process shown in FIG. 3 in S702. At this stage, the session ID of the service providing server X is included in the cookie information. Therefore, S203 is executed, and the session management server 4 transfers the HTTP request to the service providing server X identified by the session ID in the cookie information included in the HTTP request (S203).

  The service providing server X (receiving means) receives the HTTP request transferred from the session management server 4. Then, an HTTP response is returned to the session management server 4 together with the context information in the HTTP request (S703). At this stage, context information is included in the HTTP request. Therefore, the service providing server X executes the second reply process shown in FIG. 8 as in the step of S309. At this stage, the same context information as the context information in the cookie information is stored in the context management DB. Therefore, the service providing server X transmits an HTTP response according to the session progress associated with the same context information as the context information in the cookie information to the session management server 4 together with the context information (S604). Moreover, the session progress degree linked | related with the same context information as the context information in cookie information is updated. Note that the context information is included in the HTTP response as cookie information.

  When the session management server 4 (transfer means) receives the HTTP response in step S704, it transfers the received HTTP response to the client device X together with the session ID of the service providing server X that is the transmission source of the HTTP response. (S704). Specifically, the session management server 4 executes the response transmission process shown in FIG. 7 in the same manner as in step S310. Here, since the session ID is not included in the HTTP response, the step of S502 is executed, and the HTTP response is transferred together with the session ID of the service providing server X (S502). The session ID is included in the HTTP response as cookie information. As a result, the client device X that has received the HTTP response displays a screen corresponding to the HTTP response.

  Here, after the user first logs in to the image processing service on the client device 2a and proceeds with the session until the guidance screen shown in FIG. 4C is displayed with the service providing server X, the image is then displayed on the client device 2b. Assume that you log in to the processing service again. In this case, the HTTP request first transmitted from the client device 2b may be transferred to the service providing server Y different from the service providing server X in S102 of FIG. However, for the following reasons, even in such a case, the session that has been proceeding with the service providing server X can be proceeded with the service providing server X again.

  FIG. 10 is a sequence diagram showing processing executed by the session management system 1 when the HTTP request first transmitted from the client device 2b as the client device X is transferred to the service providing server Y. 10 will be described in comparison with FIG. In this case, first, the cookie information of the HTTP request transmitted in S301 includes the session ID of the service providing server Y. Therefore, unlike FIG. 5, the HTTP request is transferred to the service providing server Y in S302.

  However, in S304, context information unique to the user is generated, and in the first reply process (see FIG. 6) in S305, the presence or absence of the same context information in the shared database 10 is determined. At this stage, the same context information is stored in association with the session ID of the service providing server X. Therefore, step S404 is executed in the first reply process, and in step S305, the service providing server Y sends the HTTP response not only to the context information but also to the session ID of the service providing server X associated with the context information. At the same time, it is returned to the session management server 4.

  In addition, in the response reply process shown in FIG. 7, when the session ID is included in the HTTP response (Y in S501), the session management server 4 transfers the HTTP response to the client device X as it is (S503). Therefore, the session management server 4 that has received the HTTP response in S306 transfers the received HTTP response to the client device X as it is. Therefore, in S306, the session ID of the service providing server X, not the session ID of the service providing server Y that is the transmission source of the HTTP response, is transmitted to the client device X. Therefore, the session ID of the service providing server X is included in the HTTP request transmitted from the client device X, and as a result, the HTTP request is always transferred to the service providing server X thereafter. Therefore, the user who logs in to the service again on the client device 2b can proceed with the session that has been proceeding with the service providing server X using the client device 2a again with the service providing server X. Therefore, for example, when the user logs in again, not the setting screen shown in FIG. 4B but the instruction waiting screen shown in FIG. 4D that should be displayed next to the guidance screen shown in FIG. 4C is displayed. Each time an operation for advancing a session is performed, the session with the service providing server X is advanced as shown in the sequence diagram of FIG.

  FIG. 11 is a functional block diagram showing a function group realized by the session management system 1. As shown in the figure, in the session management system 1, a request reception unit 12, a request transmission unit 14, a transfer unit 16, a reception unit 18, an authentication unit 20, and a response transmission unit 22 are realized. The response transmission unit 22 includes a generation unit 24, a determination unit 26, and a transmission unit 28. The request reception unit 12, the request transmission unit 14, and the transfer unit 16 are realized by causing the microprocessor to execute a program stored in a storage device in the session management server 4. The reception unit 18, the authentication unit 20, and the response transmission unit 22 are realized by causing the microprocessor to execute a program stored in a storage device in the service providing server 6.

  The request receiving unit 12 receives an HTTP request transmitted from the client device 2. In addition, the request transmission unit 14 transmits the HTTP request received by the request reception unit 12 to the service providing server 6 identified by the session ID in the HTTP request (S102 in FIG. 2, S302 and S308 in FIG. 5, (See S702 in FIG. 9).

  The receiving unit 18 receives an HTTP request transmitted from the session management server 4. Further, when the identification information (here, the user name) for identifying the user is included in the HTTP request received by the reception unit 18, the authentication unit 20 identifies the user identified by the identification information based on the identification information. Is authenticated (see S303 in FIG. 5).

  Further, the response transmitter 22 transmits an HTTP response corresponding to the HTTP request received by the receiver 18 to the session management server 4 (see S305 and S307 in FIG. 5 and S703 in FIG. 9). However, when the identification information for identifying the user is included in the HTTP request received by the reception unit 18, the generation unit 24 generates context information specific to the user authenticated by the authentication unit 20 based on the identification information ( (See S304 in FIG. 5). Further, the determination unit 26 determines whether the same context information as the generated context information is stored in the shared database 10 (see S305 in FIG. 5 and FIG. 6), and is the same as the generated context information. When it is determined that the context information is not stored in the shared database 10, the transmission unit 28 stores the generated context information in the shared database 10 in association with the session ID for identifying the own device, and manages the HTTP response in the session management. It transmits to the server 4 (see FIG. 6). On the other hand, when it is determined that the same context information as the generated context information is stored in the shared database 10, the transmission unit 28 associates the HTTP response with the context information and is stored in the shared database 10. Along with the ID, it is transmitted to the session management server 4 (see FIG. 6).

  After the transmission of the HTTP request by the request transmission unit 14, the transfer unit 16 receives an HTTP response returned from the service providing server 6 that is the transmission destination of the HTTP request, and the received HTTP response is transmitted to the service providing server of the transmission destination. 6 is transferred to the client apparatus 2 that is the transmission source of the HTTP request (see S306 and S310 in FIG. 5 and S704 in FIG. 9). However, when the transfer unit 16 receives a session ID together with HTTP from the service providing server 6 that is the destination of the HTTP request, the transfer unit 16 sends the HTTP response together with the session ID received together with the client device 2 that is the transmission source of the HTTP request. (Refer to S306 in FIG. 7 and FIG. 10).

  In addition, embodiment of this invention is not restricted only to the said embodiment.

  For example, the session management system 1 may include a plurality of session management servers 4. In this case, the client device 2 may transmit an HTTP request to any one of the session management servers 4.

  1 session management system, 2, 2a, 2b client device, 4 session management server, 6 service providing server, 8 user database, 10 shared database, 12 request reception unit, 14 request transmission unit, 16 transfer unit, 18 reception unit, 20 Transfer unit, 22 response transmission unit, 24 generation unit, 26 determination unit, 28 transmission unit.

Claims (3)

A session management device, a plurality of service providing devices that provide the same type of service, and a database,
The session management device includes:
Request receiving means for receiving the request data transmitted from the client device;
Request transmitting means for transmitting the request data received by the request receiving means to the service providing apparatus specified by the session information in the request data;
After the request data is transmitted by the request transmitting means, response data returned from the service providing apparatus that is the transmission destination of the request data is received, and the received response data is sent together with session information that identifies the service providing apparatus that is the transmission destination Transfer means for transferring the request data to the client device of the transmission source;
Including
The service providing apparatus includes:
Receiving means for receiving request data transmitted from the session management device;
An authentication unit that authenticates a user identified by the user identification information based on the user identification information when the user identification information for identifying the user is included in the request data received by the reception unit;
Response sending means for sending response data corresponding to the request data received by the receiving means to the session management device;
A session management system including:
The response transmission means includes
Generating means for generating user information specific to the user authenticated by the authentication means based on the user identification information when the request data received by the receiving means includes user identification information for identifying the user;
Determining means for determining whether or not the same user information as the user information generated by the generating means is stored in the database;
When it is determined that the same user information as the user information generated by the generating unit is not stored in the database, the user information is stored in the database in association with session information for specifying the device, and When it is determined that the same user information as the user information generated by the means for transmitting response data to the session management device and the user information generated by the generating means is stored in the database, Means for transmitting the response data to the session management device together with the session information stored in the database in association with the user information,
The transfer means includes
After the request data is transmitted by the request transmission means, when session information is received together with response data from the service providing apparatus that is the transmission destination of the request data, session information that identifies the service providing apparatus that is the transmission destination when the session information is received. Instead of transferring the request data to the client device that sent the request data together with the session information received with the response data,
Session management system characterized by Receiving means for receiving request data received from the client device by the session management device from the session management device;
An authentication unit that authenticates a user identified by the user identification information based on the user identification information when the user identification information for identifying the user is included in the request data received by the reception unit;
Response transmitting means for transmitting response data corresponding to the request data received by the receiving means to the session management device;
Including
The response transmission means includes
Generating means for generating user information specific to the user authenticated by the authentication means based on the user identification information when the request data received by the receiving means includes user identification information for identifying the user;
Determining means for determining whether the same user information as the user information generated by the generating means is stored in the database;
When it is determined that the same user information as the user information generated by the generating unit is not stored in the database, the user information is stored in the database in association with session information for specifying the device, and Means for transmitting response data corresponding to the request data to the session management device;
When it is determined that the same user information as the user information generated by the generating unit is stored in the database, response data corresponding to the request data is stored in the database in association with the user information. Means for transmitting to the session management apparatus together with session information. Computer
Receiving means for receiving request data received from the client device by the session management device from the session management device;
Authentication means for authenticating a user identified by the user identification information based on the user identification information when the user identification information for identifying the user is included in the request data received by the reception means;
Response sending means for sending response data corresponding to the request data received by the receiving means to the session management device;
Is a program for functioning as
The response transmission means includes
Generating means for generating user information specific to the user authenticated by the authentication means based on the user identification information when the request data received by the receiving means includes user identification information for identifying the user;
Determining means for determining whether the same user information as the user information generated by the generating means is stored in the database;
When it is determined that the same user information as the user information generated by the generating unit is not stored in the database, the user information is stored in the database in association with session information for specifying the device, and Means for transmitting response data corresponding to the request data to the session management device;
When it is determined that the same user information as the user information generated by the generating unit is stored in the database, response data corresponding to the request data is stored in the database in association with the user information. Means for transmitting to the session management apparatus together with session information.

Images