JP6684030B2 - Session information management system and session information management method - Google Patents

Description

  The present invention relates to a session information management system and a session information management method for managing a state between a web client and a web server.

  Conventionally, Cookie has been used as a mechanism for a web server to temporarily write and save data in a web client through a web browser. The amount of information that can be stored in the Web client is limited by this cookie, and it is difficult to transmit a large data size from the Web client. Therefore, the method of holding the information on the Web server side has been adopted.

  In the configuration of the Web3 layer (presentation layer, application layer, data layer) used in the Web system, a database that manages the state (session information, etc.) between the Web server and the Web client that communicates with the Web server is provided. Exists. Then, as the number of Web clients increases, it is not possible to deal with it by only adding Web servers, and it is necessary to scale out the database and store session information and the like in a divided manner (see Non-Patent Document 1).

  On the other hand, in HTML (HyperText Markup Language) 5, Web Storage is specified as a mechanism for storing data on the Web client side (see Non-Patent Document 2). In this Web storage, the Web server can store the Key-Value data in the Web client. Also, the data area size was about 4096 bytes for Cookie, but it was expanded to about 5 MB, and it became possible to store larger data.

“MySQL Utilities 1.5 manual 8.3.2 Example: Fabric and Sharding,” [online], Oracle Corporation and / or its affiliates, [Search February 1, 2017], Internet <URL: https: //dev.mysql. com / doc / mysql-utilities / 1.5 / en / fabric-quick-start-sharding.html> "HTML5 Local Storage," [online], w3schools, [Search on February 1, 2017], Internet <URL: http://www.w3schools.com/html/html5_webstorage.asp>

In the conventional Web systems, the Web server holds a database for managing the state as described above, and access to the database from a plurality of Web servers is permitted. Therefore, when load balancing is performed by adding a server holding a database, the procedure of migrating the state data such as session information to a new server becomes complicated. In order to avoid this, it is assumed that the Web client uses the Web storage or the like to hold state data such as session information. In that case, the Web client sends all session information every time. As a result, the amount of communication becomes enormous. Further, since the Web client is less reliable than the Web server, there is a high possibility that the state data will be lost.
Further, conventionally, when a Web client moves across Web servers, it is necessary to hold session information in synchronization between the source and destination Web servers. Therefore, there is also a problem that duplicate session information remains in each Web server as the Web client moves each Web server.

  The present invention has been made in view of such a point, and it is possible to eliminate the need to retain duplicate session information in a plurality of Web servers and to easily perform scale-out and failure recovery of the Web servers. An object is to provide a management system and a session information management method.

In order to solve the above-mentioned problems, the invention according to claim 1 is a session information management system including a plurality of Web servers that provide Web services to Web clients, wherein each of the Web servers includes the Web server. A non-volatile storage that corresponds to each server on a one-to-one basis, a session information receiving unit that receives initial session information for providing the Web service from the Web client, and an address of the Web server in the received initial session information. A new session information indicating the updated session information with the suffix is generated, and the generated new session information is transmitted to the Web client, and a session information generation unit that stores the generated new session information in the nonvolatile storage. With session information transmitter The Web client includes a session information storage unit that stores session information for receiving the provision of the Web service, a user registration request unit that acquires the initial session information from a user registration server, and the initial session information. A session information processing unit that transmits the new session information received from the Web server and stores the new session information in the session information storage unit , wherein the new session information is stored in the nonvolatile storage of the Web server. The session information management system is stored in both the session information storage unit of the Web client .

Further, the invention according to claim 6 is a session information management method of a session information management system comprising a plurality of web servers for providing web services to web clients, wherein each of the web servers is the web server. A step of receiving initial session information for providing the web service from the web client, and providing the address of the web server to the received initial session information. Generating new session information indicating the updated session information, storing the generated new session information in the nonvolatile storage, and transmitting the generated new session information to the Web client. , The web client A session information storage unit that stores session information for receiving the provision of the Web service, and acquiring the initial session information from a user registration server; and transmitting the initial session information to the Web server. Storing the new session information received from the Web server in the session information storage unit, the new session information is stored in the nonvolatile storage of the Web server and the session information storage of the Web client. The session information management method is characterized by being stored in both the department and the department .

As described above, the Web client of the session information management system includes the session information storage unit having the capacity to store the session information, and can store the session information (new session information) generated by the Web server. In addition, each of the Web servers stores the session information (new session information) generated by itself in the one-to-one corresponding nonvolatile storage.
As a result, even when the Web client moves a plurality of Web servers, the Web server of the moving destination only needs to acquire the session information from the Web client. You can eliminate the need to synchronize. Further, since the Web server stores the session information in the corresponding one non-volatile storage, it is possible to avoid a complicated procedure of migrating the session data when the Web server is scaled out or the failure is recovered. it can.

  According to a second aspect of the present invention, the session information processing unit of the Web client receives the provision of the Web service using the new session information by moving the Web client. In the case where there is no new session information, the new session information stored in the session information storage unit is extracted, and the extracted new session information is transmitted to another Web server that is newly provided with the Web service. The session information management system according to item 1 is used.

As described above, the session information processing unit of the Web client stores the session information in the session information storage unit when the Web client cannot be provided with the Web service until then due to the movement of the Web client. The existing session information (new session information) can be transmitted to the Web server that is the new destination of the Web service.
Accordingly, even if the Web client has moved, using the Web session information client stores (new session information), Web server of the destination it is possible to continuously provide Web service.

  In the invention according to claim 3, each of the Web servers further includes a session information deleting unit, and when the session information generating unit receives the new session information from the Web client, The second new session information updated with an address is generated and stored in the non-volatile storage, and the session information transmission unit performs a process of transmitting the generated second new session information to the Web client. The session information deleting unit extracts the address of the Web server attached to the new session information, transmits a deletion instruction of the new session information to the Web server having the extracted address, and deletes the new session information. The session information deleting unit of the Web server that receives the instruction is the nonvolatile storage of its own. It was session information management system according to claim 2, characterized in that to remove the new session information stored.

  In this way, the Web server that has received the new session information can extract the address attached to the new session information and send a deletion instruction of the new session information to the Web server at that address. Therefore, it is possible to prevent the same session information from being redundantly stored in a plurality of Web servers.

  In the invention according to claim 4, each of the Web servers further includes a session information acquisition unit and a session information deletion unit, and the session information acquisition unit uses the session information stored in its own non-volatile storage as the session information acquisition unit. When it is determined that the Web service cannot be provided to the Web client, the second new information obtained by inquiring and acquiring the new session information related to the Web client from each of the Web servers, and updating with the own address. The session information is generated and stored in the non-volatile storage, the session information transmission unit performs a process of transmitting the generated second new session information to the Web client, and the session information deletion unit performs the new information. Enter the web server address attached to the session information. The session information deleting unit of the Web server which has sent the instruction to delete the new session information to the Web server of the extracted address and has received the instruction to delete the new session information is stored in the nonvolatile storage of its own. The session information management system according to claim 1, wherein the existing new session information is deleted.

  In this way, for example, even when the Web server cannot provide the Web service to the Web client due to the loss of the session information stored in the Web client due to a failure or the like, the session information acquisition unit determines that another Web Each server can be inquired about session information about the Web client, and the session information can be acquired from the Web server that stores the session information. As a result, another web server can continue to provide web services.

  In the invention according to claim 5, each of the Web servers further includes a session information distribution unit, a server load monitoring unit, and a session information deletion unit, and the server load monitoring unit stores the load information of its own Web server. The monitoring information indicating that the value of the load information exceeds a predetermined threshold value is output to the session information distribution unit, and the session information distribution unit, when the monitoring information is acquired, the Session information stored in the non-volatile storage is distributed to session information handled by itself and session information assigned to the added Web server, and session information assigned to the added Web server from the Web client. When the request for providing the Web service using the new session information is received, the added We The redirect instruction including the address of the server is transmitted to the Web client, and the Web client receiving the redirect instruction transmits the new session information to the Web server by using the address of the added Web server, and the addition is performed. And the session information generation unit receives the new session information from the Web client, generates the second new session information updated with the address of the added Web server, and Stored in a non-volatile storage, the session information transmission unit performs a process of transmitting the generated second new session information to the Web client, and the session information deletion unit is a Web server attached to the new session information. Address of the extracted address The session information deletion unit of the Web server, which has transmitted the deletion instruction of the new session information to the eb server and received the deletion instruction of the new session information, deletes the new session information stored in the nonvolatile storage of itself. The session information management system according to claim 1, wherein:

  As described above, even when the load on the Web server increases and the number of Web servers is increased, the added Web server can acquire session information (new session information) from the Web client and provide the Web service. it can. Further, the added Web server can extract the address attached to the acquired new session information, and can transmit the deletion instruction of the new session information to the Web server having the address. Therefore, it is possible to prevent the same session information from being redundantly stored in a plurality of Web servers.

  According to the present invention, it is possible to prevent duplicate session information from being held in a plurality of Web servers and to easily perform scale-out and failure recovery of Web servers.

It is a figure which shows the structure of the session information management system which concerns on this embodiment. It is a functional block diagram which shows the structural example of the Web client which concerns on this embodiment. It is a functional block diagram which shows the structural example of the Web server which concerns on this embodiment. In the session information management system according to the present embodiment, it is a sequence diagram showing a process when a Web client moves. In the session information management system according to the present embodiment, it is a sequence diagram showing a process when the session information stored in the Web client is lost. It is a sequence diagram which shows the process in the case of performing scale-out of a Web server and distributing session information in the session information management system which concerns on this embodiment.

Next, the session information management system 1 and the like in the mode for carrying out the present invention (hereinafter referred to as “the present embodiment”) will be described.
FIG. 1 is a diagram showing the configuration of a session information management system 1 according to this embodiment.
The session information management system 1 is a Web system that provides a Web service to the Web client 10, and includes one or more Web clients 10, a Web server 20 accommodated in each base network (NW) 5, and a Web server 20. A user registration server 30 and a DNS (Domain Name System) server 40 connected to an inter-site network (NW) 6 connected to the intra-site network (NW) 5 are provided. In FIG. 1, in the session information management system 1, a web server 20 (20-1) (Web server “1”) housed in a site network 5 (5-1) (site NW “1”). , A Web server 20 (20-2) (Web server “2”) accommodated in the network 5 (5-2) in the site (NW “2” in the site) is installed, and the Web client 10 is a Web server. It is assumed that the web service is used by connecting to any of the servers 20 (20-1, 20-2).

The Web client 10 according to the present embodiment is characterized by including a session information storage unit 100 having a larger data area as compared with the conventional Cookie as a mechanism for storing session information. The session information storage unit 100 can be realized by, for example, Web Storage defined by HTML5. Then, the Web client 10 stores the session information and the like used in the Web service in the session information storage unit 100.
The “session information” according to the present embodiment is temporary data when the client uses the web server 20 by the web client 10, for example, information about a shopping cart for online shopping, an input form before final transmission. Information and the like, and data that is managed in a shared database of a conventional Web system and includes data that is continuously saved, such as content purchase information when a content is purchased.

In addition, each Web server 20 includes a non-volatile storage 200 that has a one-to-one correspondence with itself. That is, each non-volatile storage 200 is not accessed by any web server 20 other than the one web server 20 connected to itself, and does not store session information processed by another web server 20. This makes it possible to avoid a complicated procedure for migrating the state data such as session information when adding the Web server 20.
Furthermore, in each Web server 20, when the Web client 10 moves across the Web server 20, the Web server 20 of the moving destination acquires the session information from the Web client 10. As a result, it is possible to eliminate the need to synchronize the session information between the source and destination Web servers 20. Since the Web client 10 stores the session information, the Web server 20 of the moving source can delete the unnecessary session information.
Hereinafter, each device constituting the session information management system 1 will be specifically described.

<User registration server>
As illustrated in FIG. 1, the user registration server 30 according to the present embodiment stores initial session information for each Web client 10 to use a Web service in an initial session information DB (DataBase) 300. The initial session information includes an authentication ID when the user who owns the Web client 10 uses the Web service, and initial settings when using the Web service (setting of use time, type of use data, use area, etc.). Information is stored. The user registration server 30 has a key (common key) shared between the Web client 10 and each Web server 20 in its storage unit (not shown), and receives a user registration request message from the Web client 10. The initial session information DB 300 is referred to, the relevant initial session information is extracted, encrypted with a common key, and transmitted to the Web client 10.

<DNS server>
The DNS server 40 according to the present embodiment stores the address (IP address) of each Web server 20 in the Web server address information DB 400 as shown in FIG. Then, when the DNS server 40 receives the inquiry message (address inquiry message) of the IP address of the Web server 20 from the Web client 10, the DNS server 40 sets the IP address of the Web server 20 belonging to the intra-site network 5 accommodating the Web client 10, The Web server address information DB 400 is referred to, extracted, and transmitted to the Web client 10.

<Web client>
FIG. 2 is a functional block diagram showing a configuration example of the Web client 10 according to the present embodiment.
The web client 10 is a device that uses a web service, and is, for example, a smartphone, a tablet terminal, or the like. The Web client 10 serves as a storage unit for storing session information having a larger amount of information than information stored in a conventional Cookie, for example, a session information storage unit 100 such as Web Storage defined in HTML5. Equipped with. Then, the Web client 10 acquires the latest (updated) session information from the Web server 20 and stores it in the session information storage unit 100. Also, the Web client 10 updates the session information stored therein when the connection destination is changed from the Web server 20 that has been connected until then to another Web server 20, or when the Web server 20 is added. To the Web server 20 that is the connection destination.
As shown in FIG. 2, the Web client 10 includes a control unit 11, an input / output unit 12, a memory unit 13, and a storage unit 14.

  The input / output unit 12 includes a communication interface for transmitting and receiving information to and from the user registration server 30, the DNS server 40, the Web server 20, and the like, an input device such as a touch panel and a keyboard, and an output device such as a monitor. It is composed of an input / output interface for transmitting and receiving information between the two.

  The memory unit 13 includes a primary storage device such as a RAM (Random Access Memory), and temporarily stores information necessary for data processing by the control unit 11.

The storage unit 14 includes a storage device such as a flash memory, and the session information storage unit 100 that stores session information is secured as its storage area.
The storage unit 14 stores a key (common key) shared between the user registration server 30 and each Web server 20.

The control unit 11 controls the entire Web client 10, and includes a user registration request unit 111, an address inquiry unit 112, and a session information processing unit 113. Note that, here, only the function related to the use of the Web service will be extracted and described, but the Web client 10 may have other functions.
Further, the control unit 11 is realized, for example, by a CPU (Central Processing Unit) (not shown) loading a program stored in the storage unit 14 into a RAM serving as the memory unit 13 and executing the program.

  The user registration request unit 111 transmits a user registration request message to the user registration server 30 in order to use the web service. Further, the user registration requesting unit 111 acquires the initial session information encrypted with the common key or the like from the user registration server 30.

  When the user registration request unit 111 receives the initial session information from the user registration server 30, the address inquiry unit 112 sends an inquiry message (address inquiry message) about the IP address of the Web server 20 that uses the Web service. , To the DNS server 40. Then, the address inquiry unit 112 acquires the IP address of the Web server 20 belonging to the intra-site network 5 to which the Web client 10 connects from the DNS server 40.

The session information processing unit 113 decrypts the encrypted initial session information received by the user registration requesting unit 111 using a common key and stores it in the session information storage unit 100.
Further, the session information processing unit 113 receives the encrypted existing session information (updated session information) from each Web server 20, decrypts it using the common key, and then stores it in the session information storage unit 100. Remember.
Further, the session information processing unit 113 encrypts the existing session information stored in its own session information storage unit 100 using the common key, and then sends it to the Web server 20 which newly provides the Web service. To send.

  In this way, the Web client 10 can store the existing (updated) session information in the session information storage unit 100 and send it to the Web server 20 that newly provides the Web service. .

<Web server>
FIG. 3 is a functional block diagram showing a configuration example of the web server 20 according to the present embodiment.
The web server 20 is a device that provides a web service in response to a request from the web client 10. The Web server 20 includes a non-volatile storage 200 that has a one-to-one correspondence with itself. Even when the Web client 10 moves, each Web server 20 does not synchronize the session information between the Web server 20 of the move source and the Web server of the move destination, and the Web server 20 of the move destination sends the session information from the Web client 10 to the Web server 10. get. Then, the moving destination Web server 20 or the Web server 20 added by scale-out sends a session information deletion instruction message to the moving source or pre-addition Web server 20 Delete the information.
As shown in FIG. 3, the web server 20 includes a control unit 21, an input / output unit 22, a memory unit 23, and a non-volatile storage 200.

  The input / output unit 22 exchanges information between a communication interface for transmitting / receiving information to / from the Web client 10 or another Web server 20, an input device such as a touch panel or a keyboard, and an output device such as a monitor. It is composed of an input / output interface for transmitting and receiving.

The memory unit 23 includes a primary storage device such as a RAM, and temporarily stores information necessary for data processing by the control unit 21.
The non-volatile storage 200 includes a storage device such as a hard disk or a flash memory, and stores session information updated when providing a Web service.
The nonvolatile storage 200 stores a key (common key) shared with the user registration server 30, the web client 10, and another web server 20.
The nonvolatile storage 200 may be installed outside the Web server 20 and connected in a one-to-one connection.

The control unit 21 controls the entire Web server 20, and includes a session information control unit 211, a service providing unit 218, and a server load monitoring unit 219.
The control unit 21 is realized by, for example, a CPU (not shown) loading a program stored in the nonvolatile storage 200 into a RAM serving as the memory unit 23 and executing the program.

  The session information control unit 211 has a function of executing session information control when the Web server 20 provides a Web service to the Web client 10, and includes a session information receiving unit 212, a session information generating unit 213, and session information transmission. The unit 214, the session information acquisition unit 215, the session information deletion unit 216, and the session information distribution unit 217 are provided.

Upon receiving the service request message requesting the provision of the Web service from the Web client 10, the session information receiving unit 212 sends the session information request message instructing the transmission of the session information necessary for the provision of the Web service to the Web client 10 Send to.
When the session information receiving unit 212 receives the encrypted session information from the Web client 10 or another Web server 20, the session information receiving unit 212 decrypts the session information using the common key stored in the non-volatile storage 200, and extracts the session information. .

Regarding the session information received and decrypted by the session information receiving unit 212, the session information generating unit 213 adds new session information (hereinafter referred to as “new session information” and “updated session information”) accompanying the provision of the Web service. Is generated.). Also, the session information generation unit 213 generates the new session information by including the address (for example, IP address) of the Web server 20 itself.
Then, the session information generation unit 213 stores new session information including the address (IP address) of the Web server 20 itself in the non-volatile storage 200.

  The session information transmission unit 214 encrypts new session information (updated session information) including the address (IP address) of the Web server 20 itself generated (updated) by the session information generation unit 213 using a common key, It is transmitted to the Web client 10.

  When the session information acquisition unit 215 determines that the session information received by the session information reception unit 212 lacks information (session information) for the service providing unit 218 to provide the Web service (that is, session information). Is not the latest information), the inquiry message of the existing session information (existing session information) is broadcasted to each Web server 20 existing in the network. The session information acquisition unit 215 sends an inquiry message for the existing session information, for example, with an authentication ID or the like unique to the Web client 10.

  When the session information acquisition unit 215 receives an inquiry message for existing session information from another Web server 20 other than itself, the session information acquisition unit 215 searches for session information in the nonvolatile storage 200. Then, when the session information acquisition unit 215 stores the session information to which the corresponding authentication ID is added, the session information acquisition unit 215 transmits the session information to the Web server 20 that has transmitted the existing session information inquiry message. To do.

  When the session information deletion unit 216 acquires existing session information from the Web client 10 or another Web server 20, the session information deletion unit 216 instructs the Web server 20 storing the existing session information to delete the session information. To send.

  Further, when the session information deletion unit 216 receives a session information deletion instruction message from another Web server 20, the session information deletion unit 216 deletes the existing session information from the non-volatile storage 200.

When the server load monitoring unit 219 determines that the load on the Web server 20 itself has exceeded a predetermined threshold, the session information distribution unit 217 adds a new Web server 20 to a network administrator (network management device or the like). To request. As a result, a new Web server 20 is added. Then, the session information distribution unit 217 distributes the session information of the Web client 10 that it was in charge of to the session information that it is in charge of and the session information that the newly added Web server 20 is in charge of. This distribution method may be distributed evenly, a distribution ratio may be determined based on the performance of the Web server 20 or the like, and the distribution logic may be stored in advance.
Further, the session information distribution unit 217 may request that the address (IP address) of the new Web server 20 be acquired from the network management device or the like and be registered in the DNS server 40.

The service providing unit 218 performs a process of providing the web service requested by the web client 10.
Further, when the session information received by the session information receiving unit 212 lacks the information and the session cannot be continued, the service providing unit 218 outputs information to that effect to the session information acquisition unit 215.

The server load monitoring unit 219 collects preset server load information and monitors whether or not a predetermined threshold is exceeded. The server load information may be, for example, a CPU usage rate or a memory usage rate, or a non-volatile storage 200 usage rate.
The server load monitoring unit 219 outputs information (monitoring information) to that effect to the session information distribution unit 217 when the predetermined threshold is exceeded.

  In this way, the web server 20 does not synchronize the session information between the web servers 20 even when the web client 10 moves. Instead, the web server 20 acquires necessary session information from the web client 10 or another web server 20. Then, when the Web server 20 acquires the session information, the Web server 20 can delete the session information by transmitting an unnecessary session information deletion instruction message to another Web server 20.

≪Process flow≫
Next, a flow of processing executed by the session information management system 1 according to this embodiment will be described. Here, (1) when the Web client 10 moves across the Web server 20, (2) when the Web client 10 loses session information due to a failure or the like, (3) because of an increase in the Web clients 10, or the like, the Web server An example will be described in the case of executing the scale-out of 20 and distributing the session information.

<Move Web Client>
FIG. 4 is a sequence diagram showing processing in the session information management system 1 according to the present embodiment when the Web client 10 moves across the Web server 20.

  First, the user registration request unit 111 of the Web client 10 transmits a user registration request message to the user registration server 30 in order to use the Web service (step S1).

Subsequently, when the user registration server 30 receives the user registration request message from the Web client 10, the user registration server 30 refers to the initial session information DB 300 (FIG. 1) and extracts the initial session information regarding the Web client 10 that has transmitted the user registration request message. Yes (step S2).
Then, the user registration server 30 encrypts the initial session information using the key (common key) shared between the web client 10 and each web server 20, and transmits the initial session information to the web client 10 (step S3).

  Next, the user registration request unit 111 of the Web client 10 receives the encrypted initial session information from the user registration server 30. Then, the encrypted initial session information is decrypted by the session information processing unit 113 and stored in the session information storage unit 100 (step S4).

  Next, the address inquiry unit 112 of the Web client 10 transmits an inquiry message (address inquiry message) of the address (IP address) of the Web server 20 that uses the Web service to the DNS server 40 (step S5).

Then, when the DNS server 40 receives the address inquiry message of the Web server 20 from the Web client 10, the Web server 20 belonging to the intra-site network (NW) 5 accommodating the Web client 10 (for example, the nearest Web server 20). Address (IP address) is extracted by referring to the Web server address information DB 400 (FIG. 1). Then, the DNS server 40 transmits the extracted IP address of the web server 20 to the web client 10 (step S6).
Here, it is assumed that the DNS server 40 extracts the Web server 20 (Web server “1”) as the Web server 20 closest to the Web client 10 and sends the IP address to the Web client 10.

Next, when the address inquiry unit 112 of the Web client 10 receives the IP address of the Web server 20, the session information processing unit 113 uses the IP address to send a service request message (here, a service A request “1” is transmitted (step S7).
Here, the Web client 10 transmits a service request message (service request “1”) to the Web server 20 (Web server “1”).

  Upon receiving the service request message (service request “1”), the session information receiving unit 212 of the Web server 20 (Web server “1”) requests the session information requesting transmission of session information necessary for providing the Web service. The message is generated by, for example, HTML and transmitted to the Web client 10 (step S8).

  Subsequently, when the session information processing unit 113 of the Web client 10 receives the session information request message, it extracts the initial session information stored in the session information storage unit 100, encrypts it using a common key, and then, for example, , POST to transmit the initial session information to the Web server 20 (Web server “1”) (step S9).

Next, the session information receiving unit 212 of the Web server 20 (Web server “1”) that has received the encrypted initial session information decrypts the initial session information and outputs it to the session information generating unit 213. The session information generation unit 213 generates updated session information (new session information “1”) including the address (IP address) of the Web server 20 itself and stores it in the nonvolatile storage 200 (step S10).
Further, the session information transmitting unit 214 encrypts the new session information “1” including the address of the Web server 20 generated by the session information generating unit 213 using the common key, and includes the encrypted new session information “1”. The HTML is transmitted to the web client 10 (step S11).

When the Web client 10 receives the encrypted new session information “1” from the Web server 20 (Web server “1”), the session information processing unit 113 decrypts the new session information “1” and stores the new session information “1” in the session information. It is stored in the unit 100 (step S12).
After that, the web client 10 receives the updated session information (new session information) from the web server 20 every time the session information is updated by the provision of the web service of the web server 20, and the new session information is updated. The session information is stored in the non-volatile storage 200.

  Here, the Web client 10 is communicatively connected to the site network 5 (5-1) (site NW “1”) shown in FIG. 1 to the site network 5 (5-2) (site NW “2”). The following description will be given assuming that the area has been moved.

  The Web client 10 again sets the address (IP address) of the Web server 20 to the DNS server 40 again because it cannot communicate with the Web server 20 (Web server “1”) of the intra-site NW “1”. Processing for transmitting an inquiry message (address inquiry message) is performed (step S21). Then, the DNS server 40 refers to the Web server address information DB 400 for the address (IP address) of the Web server 20 (Web server “2”) belonging to the intra-site NW “2” to which the Web client 10 has moved. It is extracted and returned to the Web client 10 (step S22).

  Next, when the address inquiry unit 112 of the Web client 10 receives the IP address of the Web server 20 (Web server “2”), the session information processing unit 113 uses the IP address and the Web server 20 (Web server “2”). 2)), a service request message (here, the service request is “2”) is transmitted (step S23).

  Upon receiving the service request message (service request “2”), the session information receiving unit 212 of the Web server 20 (Web server “2”) requests the session information requesting the transmission of the session information necessary for providing the Web service. The message is generated by, for example, HTML and transmitted to the Web client 10 (step S24).

  Subsequently, when the session information processing unit 113 of the Web client 10 receives the session information request message, the existing session information stored in the session information storage unit 100 and including the address of the Web server 20 (Web server “1”). (New session information "1") is extracted, encrypted using a common key, and then transmitted to the destination Web server 20 (Web server "2") using POST (step S25).

Upon receiving the encrypted existing session information (new session information “1”), the session information receiving unit 212 of the destination Web server 20 (Web server “2”) decrypts the existing session information and The information is output to the information generation unit 213. The session information generation unit 213 generates updated session information (new session information “2”) (second new session information) including the address (IP address) of the Web server 20 (Web server “2”) itself. , In the non-volatile storage 200 (step S26).
Further, the session information transmission unit 214 encrypts the new session information “2” including the address of the Web server 20 (Web server “2”) generated by the session information generation unit 213 using the common key, and the encrypted new session information “2”. The HTML including the session information "2" is transmitted to the Web client 10 (step S27).

  When the Web client 10 receives the encrypted new session information “2” from the Web server 20 (Web server “2”), the session information processing unit 113 decrypts the new session information “2”, and the new session information “2” is transferred to the existing session. The information is stored in the session information storage unit 100 (step S28).

  On the other hand, when the session information acquisition unit 215 acquires the existing session information (new session information “1”) from the Web client 10, the session information deletion unit 216 of the destination Web server 20 (Web server “2”) acquires the session information. , The address (IP address) (here, the IP address of the web server “1”) attached to the existing session information is referred to, and the web server 20 of the IP address (here, the source web server “1”) )), The deletion instruction message of the session information (new session information "1") is transmitted (step S29).

  The session information deleting unit 216 of the Web server 20 (Web server “1”) of the movement source that has received the deletion instruction message of the new session information “1” deletes the session information from the nonvolatile storage 200 (step S30).

  By doing so, in the session information management system 1, the session information is stored in the Web client 10, and when the Web client 10 moves across the Web server 20, the Web client 10 moves the Web to the destination Web site. The server 20 can acquire the session information. Therefore, it is not necessary to synchronize the session information between the Web servers 20. In addition, the Web server 20 of the moving destination transmits the deletion instruction message to the Web server 20 of the moving source, so that the existing session information that is no longer needed can be deleted.

<Loss of session information>
FIG. 5 is a sequence diagram showing processing in the session information management system 1 according to the present embodiment when the session information stored in the Web client 10 is lost due to a failure or the like.
Here, it is assumed that a failure or the like has occurred in the Web client 10 and the existing session information (new session information) stored in the session information storage unit 100 has been lost. At that time, the Web client 10 transfers from the intra-site network 5 (5-1) (in-base NW “1”) shown in FIG. 1 to the intra-site network 5 (5-2) (in-base NW “2”). The following description will be given assuming that the area for communication connection has moved.
It should be noted that the description will be made assuming that the processing of steps S1 to S12 in FIG.

When the session information is lost due to a failure or the like, the Web client 10 that has lost the session information cannot acquire the session information from its own session information storage unit 100. Therefore, the Web client 10 performs the same processing as steps S1 to S6 of FIG. 4 again. That is, the Web client 10 transmits a user registration request message to the user registration server 30 to acquire the initial session information and stores it in the session information storage unit 100, and the DNS server 40 sends the address (IP address) of the Web server 20. Is performed (steps S31 to S36).
At this time, the DNS server 40 determines the address (IP address) of the Web server 20 (Web server “2”) belonging to the intra-site network 5 (5-2) (in-base NW “2”) to which the Web client 10 has moved. ) Is extracted by referring to the Web server address information DB 400 and transmitted to the Web client 10 (step S36).
After that, the same processing as steps S7 to S9 in FIG. 4 is performed, and the web client 10 issues a service request (here, a service request “3”) to the destination web server 20 (web server “2”). To receive the session information request message, encrypt the initial session information, and send it to the Web server 20 (Web server “2”) (steps S37 to S39).

  Subsequently, the session information receiving unit 212 of the Web server 20 (Web server “2”) that has received the encrypted initial session information decrypts the initial session information. Then, based on the initial session information, the service providing unit 218 tries to continuously provide the Web service. However, the service providing unit 218 determines that the session cannot be continued because the necessary session information is insufficient, and outputs information to that effect to the session information acquisition unit 215. In this case, the session information acquisition unit 215 transmits an inquiry message of the existing session information (new session information “1”) by broadcasting to each Web server 20 existing in the network (step S40).

  The session information acquisition unit 215 of the Web server 20 (here, Web server “1”) that has received the inquiry message for the existing session information by broadcasting searches its own non-volatile storage 200, and the authentication ID of the corresponding Web client 10 is obtained. When the attached session information (new session information “1”) is stored, the existing session information (new session information “1”) is encrypted and the inquiry message for the existing session information is sent. It transmits to the transmitted Web server 20 (Web server "2") (step S41).

  The session information receiving unit 212 of the Web server 20 (Web server “2”) that has received the encrypted existing session information (new session information “1”) decrypts the existing session information, and then the session information generating unit. To 213. The session information generation unit 213 generates updated session information (new session information “2”) (second new session information) including the address (IP address) of the Web server 20 (Web server “2”) itself. , In the non-volatile storage 200 (step S42).

  After that, similarly to steps S27 to S30 of FIG. 4, the web server 20 (web server “2”) transmits the new session information “2” including the address of the web server “2” to the web client 10 and stores it. At the same time, the deletion instruction message is transmitted to the Web server “1” to delete the existing session information (new session information “1”) (steps S43 to S46).

  Here, the case where the Web client 10 has lost the session information and moved across the Web server 20 has been described. However, even if the Web client 10 loses the session information, if it can connect to the same Web server 20 as before the loss, the nonvolatile storage 200 of the Web server 20 (here, the Web server “1”). Using the existing session information stored in the non-volatile storage “1”), the session can be continued and the Web service can be provided.

  By doing so, in the session information management system 1, even if the Web client 10 loses the session information due to a failure or the like, the service can be reliably continued without synchronizing the session information between the Web servers 20. It becomes possible to provide it.

<Distribution of session information>
Next, a case where the scale-out of the Web server 20 is executed and the session information is distributed as the number of Web clients 10 increases will be described.
FIG. 6 is a sequence diagram showing processing in the session information management system 1 according to the present embodiment when scale-out of the Web server 20 is executed and session information is distributed.
Here, it is assumed that steps S1 to S12 of FIG. 4 are executed and the web service is provided between the web client 10 and the web server 20 (Web server “1”).

In this state, it is assumed that the server load monitoring unit 219 of the Web server 20 (Web server “1”) determines that the value of load information such as the CPU usage rate exceeds a predetermined threshold. In that case, the server load monitoring unit 219 outputs information to that effect (monitoring information) to the session information distribution unit 217.
Then, the session information distribution unit 217 determines to add the Web server 20 when the load of the Web server 20 (Web server “1”) of its own exceeds the predetermined threshold value (step S51). Then, the session information distribution unit 217 requests the network administrator (network management device or the like) to add a new Web server 20. As a result, a new Web server 20 (here, Web server “3”) is added. Also, the Web server “1” acquires the address (IP address) of the added Web server 20 (Web server “3”) from the network management device or the like.

Next, when a new Web server 20 (Web server “3”) is added, the session information distribution unit 217 directly manages the existing session information stored in its own non-volatile storage 200. The information is distributed to the information and the session information handled by the newly added Web server 20 (Web server “3”) (step S52).
Since the session information distribution unit 217 registers the address (IP address) of the added Web server 20 (Web server “3”) in the DNS server 40, the Web server address information DB 400 in the DNS server 40 is registered here. You may make it transmit the update request of.

  Subsequently, the session information processing unit 113 of the Web client 10 encrypts the existing session information (new session information “1”) including the address of the Web server 20 (Web server “1”) to receive the provision of the Web service. Then, it is transmitted to the web server 20 (web server "1") (step S53).

  The session information distribution unit 217 of the Web server 20 (Web server “1”) that has received the existing session information is in charge of the existing session information based on the authentication ID or the like attached to the existing session information. It is determined whether or not there is a new web server 20 (Web server “3”) added. Then, when the session information distribution unit 217 determines that the session information is the session information distributed to the new Web server 20 (Web server “3”), the added Web server 20 (Web server “3”). ) To the Web client 10 together with the IP address of the added Web server 20 (Web server "3") (step S54).

  Next, the session information processing unit 113 of the Web client 10 uses the address (IP address) of the added Web server 20 (Web server “3”) attached to the redirect instruction message to add the added Web server 20. The existing session information (new session information "1") including the address of the Web server 20 (Web server "1") is encrypted and transmitted to (Web server "3") (step S55).

  The session information receiving unit 212 of the Web server 20 (Web server “3”) that has received the encrypted existing session information decrypts the existing session information (new session information “1”), and the session information generating unit To 213. The session information generation unit 213 generates updated session information (new session information “3”) (second new session information) including the address (IP address) of the Web server 20 (Web server “3”) itself. , In the nonvolatile storage 200 (step S56).

  After that, as in steps S27 to S30 of FIG. 4, the web server 20 (web server “3”) transmits new session information “3” including the address of the web server “3” to the web client 10 and stores it. At the same time, the deletion instruction message is transmitted to the Web server “1” to delete the existing session information (new session information “1”) (steps S57 to S60).

  By doing so, in the session information management system 1, the web client 10 stores the session information even when the scale-out of the web server 20 is performed and the session information is distributed due to an increase in the number of web clients 10. As a result, the added Web server 20 can acquire the session information from the Web client 10. Therefore, it is not necessary to perform complicated processing associated with distribution of session information. Also, existing session information that is no longer needed when the distribution destination Web server 20 (Web server “3”) sends a deletion instruction message to the distribution source Web server 20 (Web server “1”) Can be deleted.

  As described above, according to the session information management system 1 according to the present embodiment, it is possible to prevent duplicate session information from being held in a plurality of web servers and to easily perform scale-out and failure recovery of the web servers. Is possible.

1 Session information management system 5 Network in base (NW)
6 Network between bases (NW)
10 Web Client 11, 21 Control Unit 12, 22 Input / Output Unit 13, 23 Memory Unit 14 Storage Unit 20 Web Server 30 User Registration Server 40 DNS Server 100 Session Information Storage Unit (Web Storage)
111 user registration request unit 112 address inquiry unit 113 session information processing unit 200 non-volatile storage 211 session information control unit 212 session information reception unit 213 session information generation unit 214 session information transmission unit 215 session information acquisition unit 216 session information deletion unit 217 session information Distributor 218 Service provider 219 Server load monitor 300 Initial session information DB
400 Web server address information DB

Claims (6)

A session information management system including a plurality of web servers that provide web services to web clients,
Each of the web servers
A non-volatile storage that corresponds to each of the Web servers on a one-to-one basis;
A session information receiving unit that receives initial session information for providing the Web service from the Web client;
A session information generation unit that generates new session information indicating the updated session information by adding the Web server address to the received initial session information, and stores the generated new session information in the nonvolatile storage.
A session information transmitting unit that transmits the generated new session information to the Web client,
The Web client is
A session information storage unit that stores session information for receiving the provision of the Web service;
A user registration request unit that acquires the initial session information from a user registration server;
A session information processing unit that transmits the initial session information to the Web server and stores the new session information received from the Web server in the session information storage unit ;
A session information management system , wherein the new session information is stored in both the non-volatile storage of the Web server and the session information storage unit of the Web client . The session information processing unit of the Web client,
When the web client cannot be provided with the web service using the new session information due to the movement of the web client,
The new session information stored in the session information storage unit is extracted, and the extracted new session information is transmitted to another Web server that is a new provision destination of the Web service. Session information management system. Each of the Web servers further includes a session information deleting unit,
When the session information generation unit receives the new session information from the Web client, the session information generation unit generates second new session information updated with the address of the Web server, and stores the new new session information in the nonvolatile storage,
The session information transmission unit performs a process of transmitting the generated second new session information to the Web client,
The session information deletion unit extracts the address of the Web server attached to the new session information, and transmits a new session information deletion instruction to the Web server having the extracted address,
The session information management unit according to claim 2, wherein the session information deletion unit of the Web server that has received the instruction to delete the new session information deletes the new session information stored in the nonvolatile storage of itself. system. Each of the Web servers further includes a session information acquisition unit and a session information deletion unit,
When the session information acquisition unit determines that the Web service cannot be provided to the Web client based on the session information stored in the non-volatile storage of the session information acquisition unit, the new session related to the Web client is provided to each of the Web servers. Inquiring and acquiring information, generating second new session information updated with its own address, and storing it in the non-volatile storage,
The session information transmission unit performs a process of transmitting the generated second new session information to the Web client,
The session information deletion unit extracts the address of the Web server attached to the new session information, and transmits a new session information deletion instruction to the Web server having the extracted address,
The session information managing unit according to claim 1, wherein the session information deleting unit of the Web server that has received the deletion instruction of the new session information deletes the new session information stored in the nonvolatile storage of itself. system. Each of the Web servers further includes a session information distribution unit, a server load monitoring unit, and a session information deletion unit,
The server load monitoring unit monitors the load information of its own Web server, and outputs monitoring information indicating that the value of the load information exceeds a predetermined threshold value to the session information distribution unit,
The session information distribution unit,
When the monitoring information is acquired, the session information stored in the non-volatile storage of itself is distributed to the session information that the user is in charge of and the session information that the added Web server is in charge of.
When a request for providing a Web service using the new session information, which is the session information to be assigned to the added Web server, is received from the Web client, a redirect instruction including the address of the added Web server is issued to the Web client. Sent to
The Web client that received the redirect instruction
Transmitting the new session information to the Web server using the address of the added Web server,
The added Web server is
The session information generation unit receives the new session information from the Web client, generates second new session information updated with the address of the added Web server, and stores the second new session information in the nonvolatile storage,
The session information transmission unit performs a process of transmitting the generated second new session information to the Web client,
The session information deletion unit extracts the address of the Web server attached to the new session information, and transmits a new session information deletion instruction to the Web server having the extracted address,
The session information managing unit according to claim 1, wherein the session information deleting unit of the Web server that has received the deletion instruction of the new session information deletes the new session information stored in the nonvolatile storage of itself. system. A session information management method for a session information management system comprising a plurality of Web servers that provide Web services to Web clients, comprising:
Each of the web servers
A non-volatile storage corresponding to each of the Web servers is provided.
Receiving initial session information for providing the web service from the web client;
Generating new session information indicating the updated session information by adding the address of the Web server to the received initial session information, and storing the generated new session information in the nonvolatile storage;
Transmitting the generated new session information to the Web client,
The Web client is
A session information storage unit that stores session information for receiving the provision of the Web service,
Obtaining the initial session information from a user registration server,
Transmitting the initial session information to the Web server and storing the new session information received from the Web server in the session information storage unit ,
The session information management method , wherein the new session information is stored in both the non-volatile storage of the Web server and the session information storage unit of the Web client .

Images