JP2011170773A - Session management method and server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage a session among a plurality of terminal devices by estimating a session duration required by a user. <P>SOLUTION: The session management method of a server accessible from a plurality of client terminals includes: recording histories of access from the plurality of client terminals in an access history management database; setting a session management time based on the access history management database; establishing a session with a first client terminal which has accessed among the plurality of client terminals; starting measuring time after the session is established; disconnecting the session when the session management time has passed; and carrying over, when access from a second client terminal is received within the session management time, the session established with the first client terminal to the second client terminal. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a session management method and a server, and more particularly to a session management method and a server for managing a session across a plurality of terminal devices.

  The terminal device which is a web server and a client normally communicates using HTTP. This HTTP is a protocol that does not hold a state, only returning a response to a page request.

  Therefore, depending on the web application provided by the server, it is necessary on the server side to identify the requested terminal device and hold the data transmitted by the terminal device for each page request of the terminal device. Therefore, the server has a session management function of identifying the terminal device using information specific to the terminal device and holding the data transmitted from the terminal device during the session in the memory, thereby identifying the terminal device. Data retention is performed. At this time, if there is no application page request or page update from the terminal device within the session retention time, the server is not overloaded by automatically ending the session and deleting the retained data. Is controlling.

  As described above, the session management plays an important role for the server, and various proposals have been made to improve the user-friendliness.

  For example, Cited Document 1 describes a technique for calculating a session holding time by utilizing an access history such as an access route.

  Reference 2 describes a technique of using an access history as information for resuming from the state when the network is disconnected when the connection is resumed after the network is once blocked.

  Further, Citation 3 describes a technique for recording operation information in a user's content as an access history and efficiently transmitting information on frequently used content to a terminal device.

JP 2009-141551 A Japanese Patent Laid-Open No. 11-265347 JP 2005-78330 A

  With the development of the information society, there are increasing opportunities to use various terminal devices other than the main PC, such as mobile phones and mobile PCs. However, if the terminal device to be accessed is changed while accessing the server, the session will be cut off, and even within the session holding time, it will not be possible to resume from the desired location, and redo will occur. .

  However, the inventions described in Patent Documents 1 to 3 are all methods for smoothly resuming access from the same terminal device, and do not mention a technique for holding a session between different terminal devices. In addition, when a session is held between different terminal devices, it is important to estimate the session holding time.

  The present invention has been made in view of such circumstances, and provides a session management method and a server that enable session management between a plurality of terminal devices by estimating a session holding time required by a user. With the goal.

  In order to achieve the above object, the session management method according to claim 1 is a session management method for a server accessible from a plurality of client terminals via a network, and records access history from the plurality of client terminals. A recording step of recording in the access history management database; a session holding time setting step of setting a session holding time based on the access history management database; and a first client terminal that has been accessed among the plurality of client terminals A session establishing step for establishing a session with the session, a timing step for starting timing after the session is established, and disconnecting the session when the session holding time has elapsed based on a timing result of the timing step A cutting step to be performed and within the session holding time When there is access from the second client terminal, characterized in that a continuous process to continue the session established between the first client terminal between said second client terminal.

  According to the first aspect of the present invention, the access histories from a plurality of client terminals are recorded in the access history management database, the session holding time is set based on the access history management database, and the second is within the session holding time. Since the session established with the first client terminal is continued with the second client terminal when there is an access from the client terminal, the session holding time required by the user is reduced. It is possible to estimate and manage a session across a plurality of client terminals.

  The session management method according to claim 1, further comprising a user registration step of recording users of the plurality of client terminals in a user information database, wherein the session holding time setting step includes: The session retention time is set for each user.

  Thereby, an appropriate session holding time can be set.

  As shown in claim 3, in the session management method according to claim 2, the recording step records access times from the plurality of client terminals in the access history management database, and the session holding time setting step includes: The session holding time is set for each user based on the access time for each user.

  Thereby, an appropriate session holding time can be set.

  4. The session management method according to claim 3, wherein the session holding time setting step sets a session holding time for each user based on an average value of access times for each user. It is characterized by.

  Thereby, an appropriate session holding time can be set.

  5. The session management method according to claim 3 or 4, wherein the session holding time setting step includes a session for each user based on an average value of access times within a predetermined period for each user. A holding time is set.

  Thereby, an appropriate session holding time can be set.

  6. The session management method according to claim 3, wherein the session holding time setting step is performed for each user based on an average value of access times on a predetermined day for each user. The session holding time is set in the.

  Thereby, an appropriate session holding time can be set.

  In the session management method according to any one of claims 1 to 6, as shown in claim 7, the recording step records an access history for each access destination of the plurality of client terminals in the access history management database, The session holding time setting step sets a session holding time for each access destination.

  Thereby, an appropriate session holding time can be set.

  In the session management method according to any one of claims 1 to 7, as described in claim 8, the continuation step is performed when the first client terminal and the first client terminal are not accessed. A session established between the second client terminal and the second client terminal is continued.

  As a result, it is possible to appropriately manage a session across a plurality of client terminals.

  The session management method according to any one of claims 1 to 8, wherein the continuation step is established with the first client terminal based on registered contents of the user database. The established session is continued with the second client terminal.

  Thereby, it is possible to continue only a session that spans between client terminals registered in the terminal management database, and security can be enhanced.

  The session management method according to claim 9, wherein the terminal management database includes owner information for each client terminal, and the continuation step includes the owner of the first client terminal and the owner of the first client terminal. When the owners of the second client terminal are the same, a session established with the first client terminal is continued with the second client terminal.

  Thereby, it is possible to continue only a session that spans between client terminals of the same owner, and security can be enhanced.

  In the session management method according to any one of claims 1 to 10, as shown in claim 11, based on the access history management database, estimating the use start time for each client terminal of the plurality of client terminals, The server is accessed from the client terminal at the estimated use start time.

  Accordingly, the server can be accessed at the estimated use start time without any operation by the user.

  The session management method according to any one of claims 1 to 11, wherein the recording step records location information at the time of access of the plurality of client terminals in the access history management database. The server is accessed from the client terminal based on position information.

  Thus, the server can be accessed upon arrival at a desired location without any operation by the user.

  In order to achieve the above object, the server according to claim 13 is a server accessible from a plurality of client terminals via a network, and records access histories from the plurality of client terminals in an access history management database. A session holding time setting step for setting a session holding time based on the access history management database, and a session for establishing a session with the first client terminal that has been accessed among the plurality of client terminals. Establishing means; timing means for starting timing after the session is established; cutting means for disconnecting the session when the session holding time has elapsed based on a timing result of the timing means; and the session Within the holding time, the access from the second client terminal If there is scan, characterized in that and a continuation means for continuing between the established session the second client terminal between the first client terminal.

  ADVANTAGE OF THE INVENTION According to this invention, the session holding | maintenance time which a user needs can be estimated and the session spanning between several terminal devices can be managed.

Schematic diagram of session management system The figure which shows an example of the data of user information management DB The figure which shows an example of the data of access history management DB Flow chart showing session management processing Diagram for explaining automatic access at set time The figure which shows an example of the data of access history management DB in the case of performing the automatic access using a positional information The figure which shows an example of the data of user information management DB The figure which shows an example of the data of access history management DB Flowchart showing processing for estimating session holding time

  Hereinafter, preferred embodiments of a session management method and a server according to the present invention will be described with reference to the accompanying drawings.

<First Embodiment>
FIG. 1 is a schematic diagram of a session management system 10 according to the present invention. The session management system 10 includes a personal computer 11 (hereinafter referred to as a PC 11), a mobile phone 12, a mobile PC 13, a plurality of client terminal devices such as a PDA 14, an Internet 21,
And a web content server 31 (hereinafter referred to as server 31).

  The PC 11, the mobile PC 13, and the PDA 14 are communicably connected to the Internet 21 via, for example, a wired or wireless LAN (Local Area Network). In addition, the mobile phone 12 is connected to the Internet 21 via a mobile communication provider's gateway server or the like.

  The server 31 is connected to a plurality of client terminals via the Internet 21 and provides various web contents.

  The server 31 includes a user information management database 32 (hereinafter referred to as user information management DB 32) and an access history management database 33 (hereinafter referred to as access history management DB 33), and uses web contents. It manages client terminal information and access history for each user.

  FIG. 2 is a diagram showing an example of user information data for each user stored in the user information management DB 32. Here, the data of the user P and the user Q are shown.

  The user P registers the PC 11, the mobile phone 12, and the mobile PC 13 in advance as client terminals for using the server 31, and the user information management DB 32 stores the MAC addresses and user agents of these client terminals. The information for specifying the device is recorded in association with the user P.

  The user information management DB 32 records a session holding time determined in advance for each user. For example, the session holding time of the user P is 60 minutes.

  Similarly, in the user information management DB 32, the MAC address of the registered terminal device PDA 14 of the user Q and the session holding time are recorded.

  Next, the access history management DB 33 will be described. FIG. 3A is a diagram showing an example of access history data for each user recorded in the access history management DB 33. Here, the access history of the user P is shown. Moreover, FIG.3 (b) is a figure which shows the action of the user P on September 25th. The server 31 sequentially confirms the connection status of the mobile phone 12 and records the action of the user P in the access history management DB 33.

  For example, as shown in FIG. 3B, the user P leaves his home at 7:45 on September 25 and arrives at the nearest station at 8:00. Access and start browsing news (action A1). The server 31 records this access history in the access history management DB 33 together with the location information of the mobile phone 12 (record R1). The location information of the mobile phone 12 is acquired by the GPS function provided in the mobile phone 12, and the acquired location information is transmitted to the server 31.

  Next, the user P gets on the train at 8:03 and changes to the subway at 8:25 (action A2). For this reason, the mobile phone 12 moves to a place where radio waves do not reach, and cannot maintain a connection with the server 31. The server 31 detects this disconnection and records it as an access history together with the location information of the mobile phone 12 immediately before disconnection (record R2). At this time, the session between the server 31 and the mobile phone 12 is not disconnected.

  Thereafter, when the subway on which the user P rides stops at a station at 8:28 (action A3), the mobile phone 12 and the server 31 can be connected again. The server 31 detects this reconnection and records it as an access history together with the location information of the mobile phone 12 (record R3).

  Further, after the subway on which the user P rides departs from the station at 8:29, the user P has finished browsing the news (action A4). Therefore, the mobile phone 12 records this end operation together with the location information of the mobile phone 12 as an access history (record R4).

  Thereafter, the user P who arrives at the office at 8:45 starts up the PC 11 at 8:50 and starts browsing news on the PC 11 (action A5). The server 31 records this news browsing start operation together with the location information of the PC 11 as an access history (record R5). If the PC 11 does not have a GPS function, the position information calculated and input in advance from the address may be recorded.

  In addition, the user P has finished browsing the news at 9:00 in order to start business. The server 31 records this end operation as an access history together with the position information of the PC 11 (record R6).

  Thus, the server 31 records the access history of each user in the access history management DB 33.

  FIG. 4 is a flowchart showing session management processing according to the present invention. Here, a case where the user P accesses the server 31 using the mobile phone 12 and the PC 11 will be described.

  First, the user P accesses a website provided by the server 31 using the mobile phone 12 (step S21). When accessing, enter the user name and password for user authentication.

  The server 31 performs user authentication from the user name and password, acquires terminal information (user agent) from the mobile phone 12 (step S1), and determines whether access is possible (step S2). In addition to user authentication, whether access is possible is determined by the client terminal registered in the user information management DB 32 and other terminals (here, the PC 11 and the mobile PC 13) of the same user (here, the user P). This is done by determining whether the server 31 is not accessed from two points.

  As a result, if user authentication fails, access is from a device not registered in the user information management DB 32, or if the same user is accessing from another terminal, it is determined that access is impossible. Then, the mobile phone 12 is notified that the access is impossible (connection error) (step S22).

  When access is possible without corresponding to these, the use start time of the mobile phone 12 for the user P in the access history management DB 33 is updated (step S3), and the user recorded in the user information management DB 32 is updated. The session holding time of P is read, the read session holding time is set, and a session with the mobile phone 12 is established (step S4).

  When the session is established, the user P can work on the website accessed by the mobile phone 12 (step S23). For example, when the server 31 provides a business management site, business documents can be created and edited within the site, and when a shopping site is provided, order information is input. Can do.

  After that, during the work on the website, the user P and the mobile phone 12 move to a place where radio waves do not reach, or the user P turns off the mobile phone 12 to communicate with the server 31. It is assumed that it becomes impossible (step S24).

  When the server 31 detects that there is no access from the mobile phone 12 (step S5), the server 31 determines whether or not the session holding time set in step S4 has passed (step S6).

  If it is within the set session holding time, the session is held (step S7), and if the set session holding time has elapsed, the session is disconnected, and the user P of the access history management DB 33 The use end time of the mobile phone 12 is updated (step S8).

  Next, it is assumed that the user P accesses the website provided by the server 31 using the PC 11 (step S31).

  The server 31 acquires access terminal information from the PC 11 (step S9), and determines whether access is possible (step S10). The access permission determination is performed in the same manner as in step S2. When it is determined that access is impossible, the PC 11 is notified of a connection error (step S32).

  If access is possible, the use start time of the PC 11 for the user P in the access history management DB 33 is updated (step S11), and it is determined whether or not a session between the server 31 and the user P is currently held (step S11). S12).

  If the session is held, the session is resumed from that state (here, the last state of work on the mobile phone 12 in step S23) (step S13). If the session is not held, the session holding time of the user P recorded in the user information management DB 32 is read, the read session holding time is set, and the session with the PC 11 is established (step) S14).

  In this way, the session is resumed or established, and the user P can perform work on the website accessed on the PC 11 (step S33). When the session is resumed, it is possible to continue the previous work.

  Thereafter, when the work on the PC 11 is finished by ending the web browser or the like (step S34), the server 31 detects that the work is finished on the PC 11, and determines whether or not the set session holding time has elapsed. Determination is made (step S15).

  If it is within the set session holding time, the session is held (step S16). If the set session holding time has elapsed, the session is disconnected, and the user P of the access history management DB 33 The use end time of the PC 11 is updated (step S17).

  Therefore, when the user P accesses the server 31 again using a registered client terminal such as the PC 11 or the mobile phone 12, the session is held within the session holding time. In step S34, the work performed in the PC 11 can be resumed from the point where it was interrupted.

  In this way, even if the connection from the client terminal is interrupted, if the session is held within the session retention time, and there is an access from another client terminal of the same user In addition, the session can be resumed from the point where the connection is cut off, and the user does not need to perform the same work from the beginning, and can provide a highly convenient system.

  Instead of the server 31 creating the access history management DB 33, the user may register his / her schedule in the server 31 in advance and determine the session holding time according to the registered schedule.

  The server 31 transmits the start time registered in the user information management DB 32 to the dedicated software installed in advance on the user's client terminal, and the dedicated software on the client terminal receives the received start time. Then, the server 31 may be automatically accessed.

  For example, as shown in FIG. 5, in the user information management DB 32, the usage start time on the PC 11 of the user P of a certain website is set to 8:50, and the usage start times on the mobile phone 12 are set to 8:00 and 8:28. Suppose that it is registered. The server 31 transmits the use start time 8:50 to the dedicated software installed in the PC 11 in advance, and transmits the use start times 8:00 and 8:28 to the dedicated software installed in the mobile phone 12 in advance.

  The dedicated software of each client terminal sets the use start time transmitted from the server 31 as the start time.

  Thereafter, when the activation time is reached, the dedicated software of each client terminal automatically accesses the corresponding website of the server 31.

  For example, when the use start time of the mobile phone 12 is 8:00, the mobile phone 12 automatically accesses the server 31, and when the use start time of the PC 11 is 8:50, the PC 11 automatically connects to the server 31. Access.

  In this example, when the PC 11 accesses the corresponding website of the server 31 at 8:50, the connection between the mobile phone 12 and the server 31 may be continued. In such a case, the server 31 gives priority to the connection with the previously connected mobile phone 12 and does not accept access from the PC 11. The PC 11 periodically retries access, and can connect to the server 31 when the connection is idle (that is, the connection between the server 31 and the mobile phone 12 is terminated).

  With this configuration, it is not necessary for the user to sequentially access the server 31, and the operation can be continued as soon as the start time is reached.

  Note that the number of websites that the dedicated software automatically accesses is not limited to one, and it is preferable that a plurality of websites can be registered. Further, the use start time may be configured such that the user registers in dedicated software of each client terminal.

  Furthermore, the location information may be used to request access to the website from dedicated software of the client terminal. For example, it is detected that the GPS information of the client terminal cannot be acquired, and based on this, it is determined that the user has taken the subway, and the time to get on the ground is estimated.

  Based on the access history recorded in the access history management DB 33, the server 31 estimates the time when the blocked client terminal can be connected again. When the connectable time is reached, the server 31 uses the dedicated software for the client terminal. The start request is issued, and the client terminal accesses the server 31 from the dedicated software.

  In addition, when it is determined based on the access history management DB 33 that the client terminal to be reconnected is different from the client terminal that has been disconnected, the server 31 may issue an activation request to the client terminal to be reconnected. .

  FIG. 6 is an example of the access history management DB 33 when automatically reconnecting using location information, and is a diagram showing the access history of January 5 of the user P.

  As shown in the figure, GPS information is acquired every 5 minutes by the mobile phone 12 of the user P. GPS information is also acquired at the start of access to the site and at the end of access. In the figure, the shaded portion indicates connection by periodic acquisition of GPS information. The GPS information is recorded from time to time in the access history management DB 33 via the server 31 from the mobile phone 12.

  In this example, from 7:48 to 8:08, acquisition of GPS information has failed, and it can be assumed that the user P is in the basement. In addition, from the last GPS information B at 7:45 and the GPS information C at 8:10 where GPS information can be acquired again, the user P was traveling from a specific station to a station on the subway. I can guess.

  By obtaining such a history in the same manner every day and recording it in the access history management DB 33, it is possible to estimate an average usage situation for each user. Based on the access history management DB 33, the dedicated software of the mobile phone 12 may be requested to access the website at a predetermined time. For example, in the example of FIG. 6, by requesting access when GPS information acquired from the mobile phone 12 becomes C, the user P can use the website of the server 31 as soon as he gets off the subway. .

  Thus, a more convenient system can be provided by utilizing the position information of the access history.

<Second Embodiment>
In the session management system of the second embodiment, the session holding time is estimated for each user and stored in the user management DB 32. Here, the session holding time is further estimated according to the connection destination.

  FIG. 7 is a diagram showing an example of user information data for each user stored in the user information management DB 32. Here, data for each connection destination of the user P is shown.

  For example, for site A which is an in-house portal site, the URL of site A, the user agent of mobile phone 12 and the MAC address of PC 11 which are client terminal information registered in advance to use site A, the site A The session holding time of the user P and the last access date / time to the site A are recorded.

  The last access date and time is the time when the user P accesses the site A and the session is established. The server 31 holds the session with the user A's site A based on this time and the session holding time. That is, the server 31 disconnects the session when the session holding time has elapsed from the last access date and time when access from the user P is lost.

  As this last access date and time, the last last access date and time is stored for each day. For example, in the example of November 13, the first access is 9:01 and it ends at 10:01. Considering this as a single use, the last access date and time during this time is not updated regardless of the interruption or interruption of communication.

  Thereafter, when accessed again at 12:00, the last access date and time is updated, and this is the second use of this date. In the second use, the session is held based on the updated last access time of 12:00 and the session holding time of 60 minutes. That is, when the user P accesses within 60 minutes from the last access date and time, the process starts from the continuation, and when the user P exceeds 60 minutes, the session is not held, so the process starts again from the beginning.

  In this way, by storing the last access date and time, even when using multiple times a day, it is possible to appropriately hold a session and to estimate the available time from the access history as described later Can be easily done.

  Similarly to the site A, the site B, which is a travel expense settlement site for business trip expenses, also includes the URL of the site B, the user agent of the mobile phone 12 that is client terminal information registered in advance to use the site B, and the site B The session holding time of the user P and the date and time of the last access to the site B are recorded.

  Although omitted in FIG. 7, the session holding time at each site is set differently depending on the day of the week used.

  Next, the access history management DB 33 will be described. FIG. 8 is a diagram showing the access history of the user P recorded on the access history management DB 33 from November 1st to November 15th. FIG. 8 (a) shows the site A and FIG. 8 (b). Shows the access history of site B. Here, the period is limited, but actually, the access history management DB 33 records the access history for all days.

  For example, as shown in FIG. 8A, for the site A, the daily use start time and use end time, the use time calculated therefrom, and access terminal information are recorded. Similarly, as shown in FIG. 8 (b), for the site B, the daily use start time and use end time, the use time calculated therefrom, and access terminal information are recorded. Access history acquisition is the same as in the first embodiment.

  Next, processing for estimating the session holding time for each user, each connection destination, and each day of the week will be described with reference to FIG.

  First, based on the data of the access history management DB 33, an average time A, which is an average value of the usage time of the user who wants to estimate the session holding time and all the connection destinations, is calculated (step S101). For example, in the access history management DB 33, the usage time of the whole period is extracted from the usage time of the site A of the user P shown in FIG. 8A, and the average time A is calculated. Since the session holding time when using the site is estimated, the average time A is preferably the average value of the usage time on the day of use, except for the days when the site is not used. In addition, when used multiple times a day, the average time A is calculated including both times.

  Next, an average time B, which is an average value of the usage time of the user who tries to estimate the session holding time and the connection destination for the last one month, is calculated (step S102).

  Further, the average time C (Csun, Cmon, Ctu,..., Csat), which is the average value of the usage time for each day of the week for the user who tries to estimate the session holding time and the connection destination, is calculated (step Sstep). S103).

  Note that the average time B and the average time C are also preferably calculated excluding days when they are not used.

  Next, the average time A and the average time B are compared to determine which is longer (step S104).

  If the average time A is longer, the average time B and the average time C are further compared to determine which is longer (step S105). As the average time C, the time of the day of the week for which the session holding time is to be calculated is used. Here, the longer one of the average time B and the average time C is set as the session holding time (steps S106 and S107).

  If the average time B is longer in step S104, the average time A and the average time C are further compared to determine which is longer (step S108). Similarly, the average time C uses the time of the day of the week for which the session holding time is to be calculated. Here, the longer one of the average time A and the average time C is set as the session holding time (steps S109 and S110).

  The session holding time estimated in this way is recorded in the user information management DB 32. By repeating this process, it is possible to estimate the session holding time for each user, each connection destination, and each day of the week.

  DESCRIPTION OF SYMBOLS 10 ... Session management system, 11 ... Personal computer (PC), 12 ... Mobile phone, 13 ... Mobile PC, 14 ... PDA, 21 ... Internet, 31 ... Web content server, 32 ... User information management database, 33 ... Access history Management database

Claims (13)

A server session management method accessible from a plurality of client terminals via a network,
A recording step of recording an access history from the plurality of client terminals in an access history management database;
A session holding time setting step for setting a session holding time based on the access history management database;
A session establishing step of establishing a session with a first client terminal that has been accessed among the plurality of client terminals;
A timing process for starting timing after the session is established;
Based on the timing result of the timing step, when the session holding time has elapsed, a cutting step of cutting the session,
When there is an access from the second client terminal within the session holding time, a continuation step of continuing a session established with the first client terminal with the second client terminal;
A session management method comprising: Comprising a user registration step of recording users of the plurality of client terminals in a user information database;
The session management method according to claim 1, wherein the session holding time setting step sets a session holding time for each user. The recording step records access times from the plurality of client terminals in the access history management database,
The session management method according to claim 2, wherein the session holding time setting step sets a session holding time for each user based on an access time for each user.   4. The session management method according to claim 3, wherein the session holding time setting step sets a session holding time for each user based on an average value of access times for each user.   The session management according to claim 3 or 4, wherein the session holding time setting step sets a session holding time for each user based on an average value of access times within a predetermined period for each user. Method.   6. The session holding time setting step of setting a session holding time for each user based on an average value of access times of a predetermined day of the week for each user. Session management method. The recording step records an access history for each access destination of the plurality of client terminals in the access history management database;
7. The session management method according to claim 1, wherein the session holding time setting step sets a session holding time for each access destination.   The continuation step is characterized in that a session established with the first client terminal is continued with the second client terminal when there is no access from the first client terminal. The session management method according to any one of claims 1 to 7.   The continuation step is characterized in that a session established with the first client terminal is continued with the second client terminal based on registered contents of the user information database. Item 9. The session management method according to any one of Items 1 to 8.   In the continuing step, when the owner of the first client terminal and the owner of the second client terminal are the same, the session established with the first client terminal is set to the second client terminal. The session management method according to claim 9, wherein the session management method continues with a client terminal.   The session management method according to claim 1, wherein the server is accessed from the client terminal at a use start time for each client terminal registered in advance. The recording step records position information at the time of access of the plurality of client terminals in the access history management database,
The session management method according to claim 1, wherein the server is accessed from the client terminal based on the location information. A server accessible from a plurality of client terminals via a network,
Recording means for recording a history of accesses from the plurality of client terminals in an access history management database;
A session holding time setting step for setting a session holding time based on the access history management database;
Session establishment means for establishing a session with a first client terminal that has been accessed among the plurality of client terminals;
Timing means for starting timing after the session is established;
Cutting means for cutting the session when the session holding time has elapsed, based on the time measurement result of the time measuring means;
Continuation means for continuing a session established with the first client terminal when there is an access from the second client terminal within the session holding time;
A server characterized by comprising:

Images