JP2012203618A - Session management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a session management system which can improve convenience of a user when continuously providing Web service.SOLUTION: A session management system 100 comprises a Web server 112 which performs the steps of; generating a session management record including a session identification code and transmitting the session identification code to a client terminal 118 when the client terminal 118 requests a connection; extracting data necessary for resumption of a session from memory and adding saving destination information to the session management record to store it if communication dose not occur for a prescribed time; deleting the data about the saved session from the memory; specifying the data necessary for resumption of the session which is associated with the session identification code when a connection request having the session identification code is transmitted from the client terminal 118; and restoring the specified session information in the memory.

Description

  The present invention relates to a session management system.

HTTP (HyperText Transfer
Protocol) does not provide a mechanism for maintaining a session between a Web server and a client terminal. Therefore, when a Web server provides a complicated Web service to a client terminal using a Web application, it is necessary to provide a mechanism for session management. As a session management mechanism in a general Web server, the following processing procedure is known (see Non-Patent Document 1). That is, the Web server generates unique session ID information when the first connection is made from the Web browser of the client terminal, and transmits the session ID information to the Web browser of the client terminal. The Web browser stores the session ID information as cookie information. The Web browser can uniquely identify the Web browser on the Web server side by including this session ID information in the IP packet when communicating with the Web server. By following such a processing procedure, it becomes possible to provide a continuous Web service.

Session timeout [Search on December 9, 2010] URL: http://www.ipa.go.jp/security/awareness/vendor/programmingv1/a05_03.html

  As described above, the Web server can uniquely identify the Web browser as the communication partner by using the cookie information. However, the web server does not log out after the user using the client terminal logs in to the web service, and if the communication with the web browser does not occur for a predetermined time, the user has stopped using the web service. It is not possible to confirm whether or not the work is temporarily interrupted. Therefore, if the Web server is left in such a state, memory resources of the Web server will be wasted. Therefore, when a predetermined time (for example, 30 minutes) has elapsed, this session is automatically recognized as a timeout. The data related to this session developed on the memory of the Web server is forcibly deleted.

  However, a user who wants to continue using the web service only by temporarily interrupting the work is required to return to the top page of the website and repeat the login process again. In other words, the above-described session management method performed by a conventional Web server has a problem in that the use efficiency of memory resources in the Web server is improved, but the convenience of the user who temporarily interrupts the work is impaired.

  In addition, when the Web server operation must be stopped due to periodic maintenance of the Web server or program replacement, the same function as the Web server to be stopped is provided in order to shorten the operation stop period. Preparation of a spare Web server has been performed. In such a case, the above-described session management method performed by a conventional Web server cannot replace the Web server to be stopped and the spare Web server while maintaining a session with each client terminal. Therefore, for users who want to use the Web service before and after the suspension period, once the session with the Web server to be stopped is terminated, the login process is repeated again after switching to the spare Web server. Is required. In other words, the above-described session management method performed by the conventional Web server can shorten the Web service stop period, but the convenience of the user who is using or wants to use it before and after the switching is impaired. There is a problem.

  The present invention has been made to solve at least one of the above-described problems, and provides a session management system that improves user convenience when continuously providing a web service. It is an object.

  In order to achieve the above object, a session management system according to the present invention is a session management system having a server connected to a plurality of client terminals via a network, and the server identifies a session when logging in to the client terminal. A session management record including the code is generated and recorded in the session management table, and a session information generation unit that transmits the session identification code to the client terminal; A session information save processing unit that saves data necessary for resuming the session recorded in the memory to a predetermined storage unit and records the save destination information in association with the session management record, information When a connection request having a session identification code is transmitted from the client terminal and a session information erasing unit that erases data related to the session from the memory after the data is saved by the avoidance processing unit, the session management table is referred to Referring to the session-related information specifying unit that identifies the save-destination information for the data necessary for resuming the session associated with the session identification code, and the save-destination information specified by the session-related information specifying unit, the session A session information restoring unit that restores data necessary for resuming to the memory.

  Further, the session management system according to the present invention has a load balancer that controls to allocate a connection request from a client terminal to any of a plurality of servers, in addition to the above-described configuration, The session information save processing unit of the first server where the shutdown event occurred saves data necessary for resuming the session recorded in the memory to a predetermined storage unit, and stores the save destination information in the session management record. A second server, which is recorded in association and operates as a spare for the first server among a plurality of servers, processes from a client terminal that has been communicating with the session identification code of the first server under the control of the load balancer When a request is sent, refer to the session management table and relate to the session identifier The session-related information specifying unit that identifies the save destination information for data that is required to resume the session, and the save destination information specified by the session-related information specifying unit, are required to restart the session. It is preferable to have a session information restoring unit that restores various data to the memory.

  In the session management system according to the present invention, in addition to the configuration described above, the first server has information indicating the location of the user who has accessed the service provided by the first server, or information capable of estimating the location. At least referring to the stored database, and according to the classification for each location, the user's session list information allocated to each of the first server and the second server is generated and transmitted to the load balancer, and the load balancer However, it is preferable to reallocate the current session according to the generated session list information.

  According to the present invention, it is possible to provide a session management system that improves user convenience when providing a Web service continuously.

1 is an overall configuration diagram of a session management system according to Embodiment 1 of the present invention. It is a flowchart which shows the process sequence in the session management system shown in FIG. It is a flowchart which shows the process sequence in the session management system shown in FIG. It is a figure which shows an example of the session management record registered into the session management table of DB server shown in FIG. 1, (a) is an example of information registered at the time of login, (b) is registered at the time of login end. It is a figure which shows the example of information. It is a figure which shows an example of the session management record registered into the session management table of DB server shown in FIG. 1, (a) is an example of information registered at the time of login, (c) is communication with a client terminal It is a figure which shows the example of information registered when no occurs in a predetermined time. It is explanatory drawing which shows the example of registration of a session management record. It is a whole block diagram of the session management system which concerns on Example 2 of this invention. It is a flowchart which shows the process sequence in the session management system shown in FIG. It is a flowchart which shows the process sequence in the session management system shown in FIG. It is explanatory drawing which shows the example of registration of a session management record. It is a whole block diagram of the session management system which concerns on Example 3 of this invention.

  Hereinafter, as an embodiment of the session management system of the present invention, refer to the drawings for a session management system 100 according to a first embodiment, a session management system 200 according to a second embodiment, and a session management system 300 according to a third embodiment. However, the present invention is not limited to the following Example 1, Example 2 and Example 3.

  FIG. 1 is an overall configuration diagram of a session management system 100 according to the first embodiment of the present invention. This session management system 100 includes a Web server 112 and a DB server 114 for session management. The Web server 112 and the DB server 114 are connected by a LAN (Local Area Network). A large number of client terminals 118 are connected to the Web server 112 via a network 116 such as an intranet or the Internet. The client terminal 118 includes a computer such as a PC, and an OS (Operating System) and a Web browser program are set up.

  In a storage unit (not shown) of the Web server 112 (for example, a hard disk), a session management program 120 dedicated to the session management system 100 is set up in addition to the OS and Web server program. A CPU (Central Processing Unit) of the Web server 112 reads the OS and these programs into a memory such as a RAM (Random Access Memory) and performs arithmetic processing, thereby performing a session information generating unit, a session information saving processing unit, Each function of the session information erasure unit and the session information restoration unit is realized. Note that processing realized by these functions will be described later. In addition, a site area 122 is provided in the storage unit of the Web server 112. The site area 122 stores an application program (not shown) and a database for providing a specific service. The storage unit of the Web server 112 may be an external hard disk directly connected to the Web server 112 or an external storage device such as NAS (Network Attached Storage) connected in the same LAN.

  The session management DB server 114 includes a database management program 124, a session management table 126, a site setting table 128, a saved data storage unit 130, and a user database 132. The site setting table 128 defines reconnectable time after timeout, identification information of data to be saved from the memory to the saved data storage unit 130 at the time of timeout, and the like. The user database 132 stores information such as each user's ID, password, name, company name, and company ID.

  2 and 3 are flowcharts showing a processing procedure in the session management system 100 shown in FIG. Hereinafter, the processing procedure in the session management system 100 will be described with reference to the flowcharts of FIGS. 2 and 3 and the data registration examples shown in FIGS. 4, 5, and 6.

  First, when the Web server 112 receives a login request from the client terminal 118 (S110), it checks the user database 132 based on the transmitted ID and password, and executes an authentication process (S112). If the authentication process is NG (NO in S112), a service unavailable message is transmitted from the Web server 112 to the client terminal 118 and displayed on the screen of the client terminal 118 (S114). On the other hand, if the authentication process is OK (YES in S112), the authentication ID information encrypted from the Web server 112 is transmitted to the client terminal 118, and the authentication ID information transmitted from the Web browser of the client terminal 118 is stored as a cookie (Cookie). ) It is stored as information (S124). Here, “authentication ID” means a session identification code generated by the Web server 112.

  Next, the Web server 112 passes the user ID to the program for managing the site area 122, requests login processing to the site (S126), generates a session management record, and stores it in the session management table 126 of the DB server 114. Register (S128).

  FIG. 4 is a diagram showing an example of a session management record registered in the session management table 126 of the DB server 114 shown in FIG. 1, (a) is an example of information registered at the time of login, and (b) FIG. 4 is a diagram illustrating an example of information registered at the time of logout. As shown in FIG. 4, the session management record includes data items of login date / time, log classification, logout date / time, authentication ID, and save data storage destination. Immediately after the start of the session, as shown in FIG. 4A, session start date / time information is recorded in the login date / time item, and “new” is recorded in the log category item. In the authentication ID item, the authentication ID issued in S124 is recorded.

  Thereafter, a Web file constituting the logged-in Web site is transmitted from the Web server 112 to the client terminal 118, and a specific service through a unique screen is provided to the user through the site area 122 (S130). When the user's work is completed and a logout request is transmitted from the client terminal 118 (S132), as shown in FIG. 4B, the Web server 112 records the current date and time in the logout date and time item of the session management record. At the same time (S134), all data related to the session is erased from the memory (S136).

  In contrast, the Web server 112 determines that a timeout has occurred when communication with the client terminal 118 does not occur within a predetermined time (for example, 10 minutes) during the provision of the Web service (S138 in FIG. 3). Session suspension processing.

  FIG. 5 is a diagram showing an example of a session management record registered in the session management table 126 of the DB server 114 shown in FIG. 1, (a) is an example of information registered at the time of login, (c) FIG. 6 is a diagram illustrating an example of information registered when communication with the client terminal 118 never occurs within a predetermined time.

  The Web server 112 refers to the site setting table 128 and acquires the setting information of the logged-in Web site (S140). Specifically, the type of data that should be stored in order to reproduce the user's usage screen on the logged-in Web site later is specified. For example, an ID that specifies input field information, search condition input field information, option field information, and the like is applicable.

  Next, based on the setting information acquired in S140, the Web server 112 extracts necessary save data (for example, text being entered, selection data, user ID, screen ID, etc.) from the memory, and saves the DB server 114. These are stored in the data storage unit 130 and saved from the memory (S142).

  Then, as shown in FIG. 5C, the Web server 112 records the save destination path name in the save data storage destination item of the session management record (S144). At this time, the time-out date / time is also recorded in the log-out date / time item. Next, the Web server 112 deletes all data related to the session from the memory (S146).

  Thereafter, a case where the user restarts the operation and a request is transmitted from the client terminal 118 will be described. 6 is a diagram showing an example of a session management record registered in the session management table 126 of the DB server 114 shown in FIG. 1. FIG. 6C shows that communication with the client terminal 118 never occurs within a predetermined time. (D) is an example of information added with a new management record by reconnection, and (e) is a diagram showing an example of information registered at the end of login.

  When the Web server 112 receives any request from the client terminal 118 (S148), whether or not the authentication ID information is described in the IP data transmitted from the client terminal 118 (S150), and the DB server 114 It is checked whether or not a session management record corresponding to the authentication ID exists in the session management table 126 (S151). If the authentication ID information is described in the IP data transmitted from the client terminal 118 and a corresponding session management record exists, the Web server 112 refers to the site setting table 128 and reconnects the site. The possible time is acquired (S152), and the session management table 126 is referred to using the authentication ID information as a key, and logout date / time (timeout date / time) information is acquired (S154).

  Next, the Web server 112 determines whether or not the elapsed time from the timeout date / time information to the present time is within the reconnectable time (S156). If YES, the session management record is referred to and necessary for resuming the session. It is determined whether or not data is registered (S158). If YES is determined in this step, the Web server 112 acquires data necessary for reproducing the session from the saved data storage unit 130 and acquires basic data for generating the service providing screen from the site area 122. The session information is restored (S160).

  Next, the Web server 112 checks the user database 132 based on the user ID in the data extracted from the saved data storage unit 130 and re-authenticates whether the user has authority to use the service in the site area 122. (S162). If it is determined here that the user has authority to use, the Web server 112 sets the restored session information in the memory (S164).

  As shown in FIG. 6D, the Web server 112 adds a new management record to the session management table 126 (S166). In the authentication ID item of this session management record, the authentication ID used before the timeout is taken over as it is, but “reconnection” is recorded in the log classification item. In the login date / time item, the date / time at the start of reconnection is recorded.

  As a result, even if the session interruption processing due to timeout is once performed by the Web server 112, the session information immediately before the timeout is reproduced in the memory, and the screen in which the text in the middle of input or the check of the choice is faithfully reproduced is displayed on the client. It is transmitted to the terminal 118. Therefore, the user can resume the work without logging in again (S130 in FIG. 2). When the user completes the work as it is and logs out, as shown in FIG. 6E, the logout date is recorded in the logout date field, and the session related data is erased from the memory of the Web server 112. (S134, S136). On the other hand, when the session interruption process by logout is executed again, the processes of S138 to S166 are repeated.

  If NO is determined in S150, S151, S156, S158, and S162, a message indicating that reconnection is not possible after a timeout is transmitted from the Web server 112 to the client terminal 118 and displayed on the screen of the client terminal 118. (S170). In this case, the user needs to return to the top page of the Web server 112 and log in again from the beginning.

  It is also possible to set an authority identification code corresponding to the user's attribute or authority in the user database 132 and control the reconnectable time after a timeout in accordance with this identification code. For example, a reconnectable time of 8 hours is allowed for users of the company, while a reconnectable time is limited to 20 minutes for users of other companies.

  In order to increase security, the IP address of the client terminal 118 is recorded in the session management record at the time of timeout, the IP address at the time of reconnection request is compared with the IP address at the time of timeout, and reconnection is permitted only when both match. You can also operate the system.

  In the case of this session management system 100, it is not necessary to code the application program in the site area 122 with respect to the data to be saved at the time of timeout or the reconnectable time, and it is sufficient to define it in the site setting table 128. There is an advantage that simplification can be achieved and setting change can be facilitated. Further, in the case of this session management system 100, it is not necessary for a user who wants to continue using the web service by simply interrupting the work to return to the top page of the website and repeat the login process again. Compared with the session management method performed by the conventional Web server, the memory resource utilization efficiency in the Web server is improved and the convenience of the user who has temporarily interrupted the work is not impaired. There is also.

  FIG. 7 is an overall configuration diagram of the session management system 200 according to the second embodiment of the present invention. The session management system 200 controls the switching of the first Web server 212, the second Web server 214, the DB server 216 for session management, the first Web server 212, and the second Web server 214. And a load balancer 218 which is a load balancer.

  Unlike the configuration shown in the first embodiment, the session management system 200 includes a plurality of Web servers 212 and 214, and employs so-called SLB (Server Load Balancing) in order to allocate access to each device. Yes. The load balancer 218 shown in FIG. 7 appears to the client terminal 222 as if it is a single Web server, and accepts the request from the client terminal 222 at once. Each time the load balancer 218 receives a request, the load balancer 218 selects one of the plurality of Web servers 212 and 214 and transfers the request to the selected server device. As a selection method of the Web servers 212 and 214 as transfer destinations, for example, a selection method using a round robin method, a selection method randomly, a method of selecting a device having the smallest number of sessions with the client terminal 222, and the Web server 212 , 214 monitoring the load status, selecting a device with less load, and periodically selecting one of the Web servers 212, 214 by regular maintenance or program replacement, etc. There is. Note that the SLB of this embodiment is configured by the load balancer 218 and the plurality of Web servers 212 and 214, but may of course be configured by the load balancer 218 and three or more server devices.

  A LAN is connected between the load balancer 218 and the Web servers 212 and 214, and between the Web servers 212 and 214 and the DB server 216. A large number of client terminals 222 are connected to the Web servers 212 and 214 via a network 220 such as an intranet or the Internet and a load balancer 218. The client terminal 222 includes a computer such as a PC, and an OS and a web browser program are set up.

  In a storage unit (for example, a hard disk) (not shown) of the Web servers 212 and 214, a session management program 224 dedicated to the session management system 200 is set up in addition to the OS and the Web server program. Functions of the session information generation unit, the session information save processing unit, the session information erasing unit, and the session information restoring unit according to claims are made by the CPU of the Web servers 212 and 214 reading the OS and these programs into the RAM and performing arithmetic processing. Is realized. Note that processing realized by these functions will be described later. In addition, site areas 226 are provided in the storage units of the Web servers 212 and 214, respectively. In these site areas 226, application programs and databases for providing specific services are stored. The storage units of the Web servers 212 and 214 are external hard disks directly connected to the Web servers 212 and 214 or external storage devices such as NAS (Network Attached Storage) connected in the same LAN. May be.

  The session management DB server 216 includes a database management program 228, a session management table 230, a site setting table 232, a saved data storage unit 234, and a user database 236. The site setting table 232 stores identification information of data to be saved from the memory of the first Web server 212 to the save data storage unit 234 of the DB server 216 when the Web server is switched. The user database 236 stores information such as the ID, password, name, company name, and company ID of each user.

  8 and 9 are flowcharts showing a processing procedure in the session management system 200 shown in FIG. Hereinafter, a processing procedure in the session management system 200 will be described with reference to the flowcharts of FIGS. 8 and 9 and the data registration example illustrated in FIG. 10. As a premise of the following processing, there is a situation that the first Web server 212 should be stopped due to periodic maintenance, program replacement, or the like, and the second Web server 214 is the first Web server 212. Is set as a spare server.

  First, when the first Web server 212 receives a login request from the client terminal 222 (S210), the user database 236 is checked based on the transmitted ID and password, and an authentication process is executed (S212). If the authentication process is NG (NO in S212), a service unavailable message is transmitted from the first Web server 212 to the client terminal 222 and displayed on the screen (S214). On the other hand, if the authentication is OK, the first Web server 212 transmits the encrypted authentication ID to the client terminal 222 and stores it in a cookie (Cookie) (S222). Here, “authentication ID” means a session identification code generated by the first Web server 212.

  Next, the first Web server 212 passes the user ID to the program that manages the site area 226, requests login processing to the site (S224), generates a session management record, and manages the session management of the DB server 216. It is registered in the table 230 (S226).

  FIG. 10 is a diagram illustrating an example of a session management record registered in the session management table 230 of the DB server 216 illustrated in FIG. 7. FIG. 10A is an example of information registered at the time of login. ) Is an example of information registered when an operation stop event such as arrival of maintenance time or occurrence of failure occurs in the first Web server 212 during the session, and (c) is the first Web server. FIG. 12D is an example of information newly added to the session management table 230 by the second Web server 214 after the stop of 212, and (d) is a diagram illustrating an example of information.

  As shown in FIG. 10, this session management record includes data items of login date / time, log classification, logout date / time, authentication ID, and save data storage destination. Immediately after the session starts, session start date / time information is recorded in the login date / time item, and “new” is recorded in the log category item, as shown in FIG. In the authentication ID item, the authentication ID issued in S122 is recorded.

  Thereafter, the web file of the logged-in site is transmitted from the first web server 212 to the client terminal 222, and a specific service through a unique screen is provided to the user through the site area 226 of the first web server 212 (S228). ).

  In the middle of this session, when an operation stop event such as arrival of a maintenance time or occurrence of a failure occurs for the first Web server 212 (S230), the first Web server 212 first refers to the site setting table 232, and the site Setting information is acquired (S232). Specifically, the type of data that should be stored for later reproduction of the user's usage screen at the site is specified. For example, a text input field, a search condition input field, an ID for specifying a choice field, a user ID, a screen ID, and the like are applicable.

  Next, the first Web server 212 extracts evacuated data (text being entered, selected data, user ID, screen ID, etc.) from the memory based on the setting information acquired in S232, and the DB server 216 The data is saved in the save data storage unit 234 (S234). Next, as shown in FIG. 10B, the first Web server 212 records the save destination path name in the save data storage destination item of the session management record (S236). At this time, the server stop date / time is also recorded in the logout date / time item. Next, the first Web server 212 deletes all data related to the session from the memory (S238). At this timing, the load balancer 218 switches from the first Web server 212 to the second Web server 214 (S240). Thereafter, the request from the client terminal 222 is transferred to the second Web server 214, and at the same time, the first Web server 212 is stopped.

  Here, the second Web server 214 that has received any request from the client terminal 222 (S242) acquires the authentication ID from the cookie of the client terminal 222 (S244). Next, the second Web server 214 specifies the session management record in the session management table 230 using the authentication ID as a key, and acquires the storage destination of the saved data (S246). Next, the second Web server 214 obtains data necessary for reproducing the session from the saved data storage unit 234 and obtains basic data for generating the service providing screen from the site area 226, Information is restored (S248). Next, the second Web server 214 sets the restored session information in the memory (S250).

  At the same time, the second Web server 214 adds a new management record to the session management table 230 as shown in FIG. 10C (S252). In the session management record, the authentication ID item used before the server switchover is inherited as it is, but the log classification item is recorded as “takeover”. In the login date / time item, the date / time at the start of the takeover is recorded.

  As a result, even if the web server is changed during the session, the session information held by the first web server 212 is reproduced on the memory of the second web server 214 that has taken over the session. Then, a screen that is faithfully reproduced up to the text in the middle of input and the check of options is transmitted to the client terminal 222. As a result, the user can continue the work without being aware of the change of the Web server and without logging in again (S254). When the user completes the work as it is and logs out (S256), as shown in FIG. 10D, the logout date is recorded in the logout date field (S258), and the second Web server The session related data is erased from the memory 214 (S260).

  In the case of this session management system 200, it is not necessary to code the type of data to be saved in the application program in the site area 226. Further, in the case of this session management system 200, since it is only necessary to define the type of data to be saved at the time of server replacement in the site setting table 232 of the DB server 216, the coding work can be simplified and the setting can be changed. There is an advantage that can be simplified. Further, in the case of this session management system 200, for a user who wants to use a Web service before and after the server change, the session with the Web server to be stopped is once ended and then switched to a spare Web server. Since it is not required to repeat the login process again after being issued, the Web service stop period can be shortened compared to the session management method performed by the conventional Web server, and the user who was used before and after this switching There is also an advantage that the convenience of the user who wants to use the service is not impaired.

  FIG. 11 is an overall configuration diagram of a session management system 300 according to the third embodiment of the present invention. In the configuration of the session management system 300 according to the third embodiment, devices and functions having the same functions as those of the session management system 200 according to the second embodiment are denoted by the same reference numerals, and the description thereof is simplified or omitted as appropriate. To do.

  In this session management system 300, for sessions allocated to the Web servers 212 and 214, the session management program 224A of the Web server 212, the session management table 230A of the DB server 216, and the user DB 236A cooperate with the hardware to maintain the session. The user's session list information classified according to the location of the user is generated and transmitted to the load balancer 218. Then, the connection management program 218A of the load balancer 218 manages the connection (for example, IP address, SSL session ID, cookie information, etc.) with the client terminal by the load balancer itself according to the generated session list information. The management table 218C is updated, and sessions are reallocated to the Web servers 212 and 214. This will be specifically described below.

  A control unit (not shown) realized by reading the session management program 224A into the RAM by the CPU refers to the user DB 236A, acquires Web service information that can be used by the user currently maintaining the session, The location information of the user or information corresponding thereto (for example, nationality information, use area information, etc.) is registered in the session management table 230A of the DB server 216. Based on the registered Web service information and location information, the session list information allocated to the Web server 212 and the session list information allocated to the Web server 214 are generated.

  For example, if the Web server 212 provides a Chinese Web page and a Japanese Web page and it is necessary to stop only the Chinese Web page, the user who is affected by this stop It is assumed that the user uses a Web page. Therefore, the Web server 212 extracts the user whose location is associated with China from the above-described session management table 230A, and the session information used by the extracted user is partly changed. In addition to being excluded from the session list information of the server 212, an addition to the session list information of the Web server 214 is created. In this way, for a user session that does not use a Chinese Web page, the Web server 212 can be used as it is, and other Web services provided by the Web server 212 are provided. There is no need to stop. In the above example, the session is extracted after referring to the session management table 230A to identify the user associated with the location information. However, the information is not registered in the session management table 230A in advance. The user DB 236A may be referred to directly. Further, not only the location information but also the IP address information (global IP address information or local IP address information) of the connection source at the start of the session may be recorded, and the location may be determined by a combination thereof. . By doing in this way, the point where the user connected to Web service can be grasped more certainly. In addition, as a method for determining the location when the user is connected, the IP address information of each country and the user published by the NIR (National Internet Registry) that manages IP addresses by country are also available. The location may be determined based on the combination with the location information registered in the DB 236A (for example, in the case of a user who has registered a location in Japan, the global IP address of the connection source of the session) For example, the location information is determined based on whether or not it is within the range of IP addresses used and managed in Japan by the Japan Network Information Center (JPNIC). In addition to the method for determining the location as described above, only the session information of the user who is actually accessing the Chinese Web page may be extracted and the location may be estimated using this.

  In the case of this session management system 300, in addition to the effects produced by the session management system 200, in the renewal of some screens included in the web service provided by the web server 212, or in the web service provided in a plurality of language areas, This is particularly useful for session management when making some changes.

(Modification)
As mentioned above, although Example 1, Example 2, and Example 3 were demonstrated as one embodiment of this invention, this invention is not limited to the Example mentioned above. For example, in the session management system 100 described above, one Web server 112 and one DB server 114 are configured, but the functions of these devices may be configured by one server device. In the session management systems 200 and 300 described above, the Web servers 212 and 214 and the DB server 114 are configured. However, the Web servers 212 and 214 and the two mirrored DB servers 114 may be configured. Good.

  The session management system 100 is mainly intended to improve the convenience of the user who has temporarily interrupted the work, and the session management systems 200 and 300 are the regular servers of the Web servers 212 and 214. The main purpose is to improve the convenience of users who can interrupt the session by general maintenance or program replacement, etc., but it can also be configured as a session management system having any one of these functions Of course.

  In the session management tables 126, 230, and 230A in the session management systems 100, 200, and 300, when a user who has maintained a session logs out, the associated data is deleted. May be stored in the storage unit of the Web server 112, 212, 214 or the DB server 114, 216 and utilized as described below. For example, based on the session management record registered in the session management tables 126, 230, and 230A in the session management systems 100, 200, and 300, the user time-out is performed by the session management programs 120, 224, and 224A of the Web servers 112, 212, and 214. The predetermined time may be adjusted. As a result, if you see reconnection session management records with reference to historical data (for example, if there are 10% or more of reconnection session management records), increase the timeout period. Thus, the number of reads from the DB servers 114 and 216 can be reduced. As a method of adjusting the predetermined time by the session management program 120, 224, 224A of the Web server 112, 212, 214, it is changed at a predetermined timing (for example, every hour, every three hours, etc.) or dynamically The program may be designed to change to

  In addition, the session management tables 126, 230, and 230A are provided with an item for registering information that can identify the web service, and the session management programs 120 and 224 of the web servers 112, 212, and 214 cause a timeout for each web service. May be adjusted. By monitoring these pieces of information, when reconnection session management records are scattered about a specific Web service (for example, when there are 10% or more of reconnection session management records). For a specific Web service, it is possible to lengthen the predetermined time for timeout than other Web services, and to reduce the number of reads from the saved data storage units 130 and 234 of the DB servers 114 and 216 at the time of reconnection. Can be made. On the other hand, if it is possible to read from the history data that a reconnection has not occurred even if a timeout occurs for a specific Web service (for example, login to the specific Web service by the session management program 120, 224 of the Web server 112, 212, 214) If it is determined that there are 80% or more of session management records that do not have a reconnection record for a session that has timed out, the specific Web service is more than the other Web services. It is possible to shorten the predetermined time for timeout, and the memory resources of the Web servers 112, 212, and 214 can be effectively used.

  Further, by extracting a plurality of sessions for a predetermined period (for example, the number of sessions for the past 3 months, 6 months, etc.) from the history data of the session management tables 126, 230, and comparing them, the Web servers 112, 212, The current validity of 214 performance (for example, memory capacity, CPU processing capacity, etc.) may be evaluated, or the number of sessions may be predicted in the future to increase the number. As a result, it is possible to prevent problems such as a response delay due to an increase in the number of accesses. As a result, since it is possible to operate the web service without losing convenience for the user, the convenience for the user can be improved as compared with the conventional session management method.

  The Web servers 112, 212, and 214, the DB servers 114 and 216, and the load balancers 218 and 218A are devices that constitute the session management systems 100, 200, and 300 described above, and each device is regarded as one aspect of the invention. It is also possible. Further, the session management programs 120, 224, 224A, the database management programs 124, 228, and the connection management program 218B described above realize each device described above by being installed in a computer. That is, these programs are programs for functioning as the respective devices constituting the session management systems 100, 200, and 300 described above, and can produce the same effects as the effects exhibited by the respective devices. It is also possible to grasp as one mode. In addition, all or part of the operations executed by each device described above can also be regarded as a session management method, and such a session management method has the same effect as that produced by each device. Therefore, this can be regarded as one embodiment of the invention.

100, 200, 300 Session management system, 112, 212, 214 Web server, 114, 216 DB server, 116, 220 network, 118, 222 Client terminal, 120, 224, 224A Session management program, 122, 226 Site area, 124 , 228 Database management program, 126, 230, 230A Session management table, 128, 232 Site setting table, 130, 234 Saved data storage unit, 132, 236, 236A User database, 218, 218A Load balancer, 218B Connection management program, 218C Connection management table

Claims (3)

A session management system having a server connected to a plurality of client terminals via a network,
The server is
When logging in to the client terminal, a session management record including a session identification code is generated and recorded in a session management table, and a session information generation unit that transmits the session identification code to the client terminal;
After transmitting the session identification code to the client terminal, when communication with the client terminal does not occur for a predetermined time, data necessary for resuming the session recorded in the memory is saved in a predetermined storage unit, and A session information save processing unit for recording save destination information in association with the session management record;
A session information erasure unit for erasing data related to the session from the memory after the data is saved by the session information save processing unit;
When a connection request having the session identification code is transmitted from the client terminal, the storage management table refers to the session management table and is associated with the session identification code, and data save destination information necessary for resuming the session A session-related information identifying unit for identifying
A session information restoring unit that restores data necessary for resuming the session to the memory with reference to the save destination information identified by the session related information identifying unit;
A session management system comprising: The session management system according to claim 1,
A load balancer that controls to allocate a connection request from the client terminal to any of the plurality of servers;
Of the plurality of servers, the session information save processing unit of the first server in which a predetermined operation stop event has occurred,
The data necessary for resuming the session recorded in the memory is saved in a predetermined storage unit, and the save destination information is recorded in association with the session management record,
Of the plurality of servers, a second server operating as a spare for the first server is:
When a processing request is transmitted from the client terminal that has been communicating with the session identification code of the first server under the control of the load balancer, the session management table is referred to and associated with the session identification code A session-related information specifying unit for specifying save destination information of data necessary for resuming the session,
A session information restoring unit that restores data necessary for resuming the session to the memory with reference to the save destination information identified by the session related information identifying unit;
A session management system comprising: The session management system according to claim 2,
The first server is
Reference is made to a database storing at least information indicating the location of a user who has accessed a service provided by the first server, or information capable of estimating the location, and the first server and Generate and send session list information of users allocated to each of the second servers to the load balancer, and reallocate current sessions to the load balancer according to the generated session list information To do,
A session management system characterized by that.

Images