JP6252016B2 - Session management program, session management method, and session management apparatus - Google Patents

Description

  The present invention relates to a session management program, a session management method, and a session management apparatus.

  Conventionally, when using an in-house system from the outside by using a terminal device such as a smartphone or a tablet terminal, there is a technology for allowing safe and comfortable access. In this technology, a terminal device is accessed to a virtual browser server having an image transfer function, and the virtual browser server transfers the screen of the in-house Web system to the terminal device. Furthermore, in this technique, a management server that manages the number of sessions connected to the virtual browser server is provided. The management server records the connection status of the terminal device notified from the virtual browser server and manages the number of connectable sessions. The management server receives a connection request from the terminal device. When the management server receives a connection request from the terminal device, the management server permits access to the virtual browser server if the number of sessions of the virtual browser server is not the upper limit.

“Industry's first! Web business screens for PCs can be used easily and smoothly on smart devices simply by placing a gateway”, [online], [Search July 5, 2013], Internet <URL: http: // pr.fujitsu.com/jp/news/2013/06/18-1.html> “FUJITSU Thin Client Solution Moba Camel for Smart Devices”, [online], [Search July 5, 2013], Internet <URL: http://jp.fujitsu.com/group/fnets/services/ictinfra/m -smartdevice.html>

  However, if the screen of the in-house Web system is transferred using a virtual browser server having an image transfer function, restrictions on the OS and applications increase, and the services that can be provided are restricted by the restrictions. Therefore, when an image relay server that transfers an unrestricted screen is provided in the virtual browser server, the management server may manage both the image relay server and the virtual browser server. In this case, if the sessions of the image relay server and the virtual browser server are managed independently, the connectable session may not be effectively used.

  An object of one aspect is to provide a session management program, a session management method, and a session management apparatus that can effectively use a connectable session.

  According to one aspect of the present invention, a session management program is executed by a relay unit that relays a processing result of an application executed by an execution unit, and a management unit that manages a session relayed by the relay unit. The session management program causes the management unit to receive a session allocation request from the terminal and to execute a process of returning to the terminal connection destination information of a relay unit that allows the terminal to access the terminal. The session management program causes the relay unit to execute processing for connecting a session that relays the terminal and the execution unit based on the access of the terminal. The session management program causes the management unit to receive a session disconnection notified from the execution unit in response to a session disconnection relayed by the relay unit, and to execute a process of releasing the notified session assignment .

  According to one aspect of the present invention, resources can be effectively used.

FIG. 1 is a diagram schematically showing an example of the overall configuration of the system. FIG. 2 is a diagram illustrating an example of a functional configuration of the management server. FIG. 3 is a diagram illustrating an example of a data configuration of the relay server information. FIG. 4 is a diagram illustrating an example of a data configuration of session information. FIG. 5 is a diagram illustrating an example of a system management screen. FIG. 6 is a diagram schematically illustrating an example of a communication flow when establishing a session and transferring an image. FIG. 7 is a flowchart illustrating an exemplary procedure of session management processing. FIG. 8 is a diagram illustrating a computer that executes a session management program.

  Embodiments of a session management program, a session management method, and a session management apparatus according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments. Each embodiment can be appropriately combined within a range in which processing contents are not contradictory.

[overall structure]
The overall configuration of the system 10 according to the first embodiment will be described. FIG. 1 is a diagram schematically showing an example of the overall configuration of the system. The system 10 is a system that enables access to a secure network from the outside. In the present embodiment, a case will be described as an example in which an in-house Web system 13 provided in an internal network such as a company is accessed from the outside.

  The system 10 includes a management server 20, an image relay server 21, and a virtual browser server 22. The management server 20, the image relay server 21, and the virtual browser server 22 are server computers provided in a data center or a company, for example. The image relay server 21 and the virtual browser server 22 can be set to an arbitrary number, and the number corresponding to the maximum number of simultaneous accesses is installed.

  The system 10 is connected to an external network 12 and can be accessed from the terminal device 11. Examples of the external network 12 include any communication network such as the Internet, a LAN (Local Area Network), a VPN (Virtual Private Network), and a mobile communication network regardless of wired or wireless.

  The terminal device 11 is a device used by a user to access an internal network. Examples of the terminal device 11 include mobile terminals such as smartphones, tablet terminals, and PDAs (Personal Digital Assistants). The terminal device 11 may be an information processing device such as a desktop PC (personal computer) or a notebook PC. A user accesses the system 10 using the terminal device 11 when using the in-house Web system 13 from the outside. For example, when accessing the in-house Web system 13, the terminal device 11 first accesses the management server 20 and requests assignment of a session to the image relay server 21. In the example of FIG. 1, the case where the number of the terminal devices 11 is two is illustrated, but the disclosed system is not limited to this, and the number of the terminal devices 11 can be an arbitrary number.

  The management server 20 is a physical server that manages a session with the terminal device 11. Here, as will be described later, the image relay server 21 transfers the screen to the terminal device 11, but there is a limit to the number of sessions that can be connected to the terminal device because a load is imposed on processing such as image transfer. Therefore, the management server 20 manages the number of sessions connectable to each image relay server 21. For example, the management server 20 periodically inquires each image relay server 21 about the connection status of the session and manages the currently connected session. When the management server 20 is requested to assign a session from the terminal device 11 to the image relay server 21 and there is an image relay server 21 to which a session can be assigned, the management server 20 displays information regarding the image relay server 21 to which the session can be assigned. To notify. The terminal device 11 accesses the notified image relay server 21.

  The image relay server 21 is a physical server that relays access to the internal network. For example, the image relay server 21 relays access from the terminal device 11 to the in-house Web system 13. When accessed from the terminal device 11, the image relay server 21 accesses the virtual browser server 22 to activate the virtual browser and establishes a session with the terminal device 11 and the virtual browser server 22. The virtual browser server 22 accessed by the image relay server 21 may be associated with the image relay server 21 in advance. The image relay server 21 may collect information indicating the load state of each virtual browser server 22 and access the virtual browser server 22 having a low load. Alternatively, the image relay server 21 may collect information indicating the connection status of each virtual browser server 22 with the image relay server 21 and access the virtual browser server 22 having the smallest number of connections.

  When the session is established, the image relay server 21 transfers information on the screen of the virtual browser operating on the virtual browser server 22 to the terminal device 11 as needed. In addition, the image relay server 21 receives operation information for the virtual browser from the terminal device 11. When receiving the operation information, the image relay server 21 performs an operation based on the operation information with respect to the virtual browser operating on the virtual browser server 22 using, for example, a remote desktop function. Further, when the image relay server 21 receives an inquiry about the connection status of the session from the management server 20, the image relay server 21 returns information regarding the connection status of the connected session to the management server 20.

  The virtual browser server 22 is a physical server that operates the virtual browser. For example, the virtual browser server 22 operates the browser in response to a request from the image relay server 21 using a remote desktop function. Then, the virtual browser server 22 causes the browser to operate as a virtual browser, for example, by transferring the screen of the browser portion to the image relay server 21 using the RemoteApp function. Further, when the session with the image relay server 21 is disconnected, the virtual browser server 22 notifies the management server 20 of the disconnection of the session. For example, in the virtual browser server 22, when the access to the in-house Web system 13 from the terminal device 11 is completed and the virtual browser is terminated, the virtual browser notifies the management server 20 of session disconnection. When the virtual browser is terminated, unlike the virtual browser, a program for monitoring the state of the virtual browser may notify the management server 20 of the disconnection of the session.

  As described above, when access to the in-house Web system 13 is requested from the terminal device 11, the system 10 according to the present embodiment causes the in-house Web system 13 to be accessed on behalf of the virtual browser, and the screen of the virtual browser is displayed on the terminal. Transfer to device 11. That is, the screen of the virtual browser is transferred to the terminal device 11, but the data of the internal network is not transferred. For this reason, the security of the internal network can be maintained. Further, since the data of the internal network is not transferred to the terminal device 11, data leakage can be suppressed.

[Management server configuration]
Next, the configuration of the management server 20 according to the first embodiment will be described. FIG. 2 is a diagram illustrating an example of a functional configuration of the management server. As illustrated in FIG. 2, the management server 20 includes a communication I / F (interface) unit 30, a display unit 31, an input unit 32, a storage unit 33, and a control unit 34.

  The communication I / F unit 30 is an interface that controls communication with other devices. The communication I / F unit 30 transmits / receives various information to / from other devices. For example, the communication I / F unit 30 receives a session assignment request from the terminal device 11 to the image relay server 21 via the external network 12. In addition, the communication I / F unit 30 is notified of session disconnection from the virtual browser server 22. As an aspect of the communication I / F unit 30, a network interface card such as a LAN card can be employed.

  The display unit 31 is a display device that displays various types of information. Examples of the display unit 31 include display devices such as an LCD (Liquid Crystal Display) and a CRT (Cathode Ray Tube). The display unit 31 displays various information.

  The input unit 32 is an input device that inputs various types of information. For example, examples of the input unit 32 include input devices such as a mouse and a keyboard. The input unit 32 receives an operation input from an administrator or the like, and inputs operation information indicating the received operation content to the control unit 34.

  The storage unit 33 is a storage device such as a hard disk, an SSD (Solid State Drive), or an optical disk. Note that the storage unit 33 may be a semiconductor memory that can rewrite data, such as a random access memory (RAM), a flash memory, and a non-volatile static random access memory (NVSRAM).

  The storage unit 33 stores an OS (Operating System) executed by the control unit 34 and various programs used for session management. Furthermore, the storage unit 33 stores various data used in the program executed by the control unit 34. For example, the storage unit 33 stores relay server information 40 and session information 41.

  The relay server information 40 is data that stores information related to the image relay server 21. FIG. 3 is a diagram illustrating an example of a data configuration of the relay server information. As illustrated in FIG. 3, the relay server information 40 includes items of “server name”, “IP address”, and “session upper limit”. The server name item is an area for storing the computer name of the image relay server 21 as identification information for identifying the image relay server 21. The IP address item is an area for storing the IP (Internet Protocol) address of the image relay server 21. The session upper limit item is an area for storing an upper limit value of the number of sessions connectable to the image relay server 21.

  In the example of FIG. 3, the image relay server 21 whose server name is “RVEC_A” indicates that the IP address is “192.168.20.185” and the session upper limit is “10”.

  The session information 41 is data that stores information related to a session managed by the management server 20. FIG. 4 is a diagram illustrating an example of a data configuration of session information. As shown in FIG. 4, the session information 41 includes “session ID”, “connection date / time”, “login ID”, “state”, “connection source IP address”, “image relay SV”, “virtual browser SV”, It has each item of "cutting date". The item of session ID is an area for storing identification information for identifying a session. Each session is given a unique session ID by combining numbers and characters as identification information for identifying each. In the session ID item, a session ID assigned to the session is stored. The item of connection date and time is an area for storing the date and time when connection of the session is started. In this embodiment, the date and time when the session allocation request is received from the terminal device 11 is stored in the connection date and time item. The login ID item is an area for storing the user ID of the user of the terminal device 11. In this embodiment, when requesting session assignment, user authentication is first performed by inputting a user ID and password. The login ID field stores a user ID input by user authentication. The status item is an area for storing the session status. In this embodiment, connected, connected, released, and abnormal are used as the session state. The connected state indicates that a session is allocated but a session is not established. The connection state indicates that a session is established and image transfer is possible. The releasing state indicates that the session is being released. The abnormal state indicates that the session cannot be released and an abnormality has occurred. The status item is updated as needed according to the session status. The connection source IP address field is an area for storing the IP address of the terminal device 11 that has requested session assignment. The image relay SV is an area for storing the IP address of the image relay server 21 connected by the session. The item of the virtual browser SV is an area for storing the IP address of the virtual browser server 22 connected by the session. The item of disconnection date / time is an area for storing the date / time when session disconnection is started. The disconnect date / time item is left blank while the session is connected, and the date / time is set when the session is disconnected.

  In the example of FIG. 4, the session with the session ID “0001” has the connection date and time “2013/6/25 20:30:40”, the login ID “A”, and the status “connected”. Indicates that there is. The session with the session ID “0001” indicates that the connection source IP address is “10.53.147.137” and the image relay SV is “192.168.20.185”. Also, the session with the session ID “0001” has the virtual browser SV “192.168.20.181” and the disconnection date / time is blank, so the session disconnection is not started and the session is connected. Indicates that it is inside.

  Returning to FIG. 2, the control unit 34 is a device that controls the management server 20. As the control unit 34, an electronic circuit such as a central processing unit (CPU) or a micro processing unit (MPU), or an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA) can be employed. The control unit 34 has an internal memory for storing programs defining various processing procedures and control data, and executes various processes using these. The control unit 34 functions as various processing units by operating various programs. For example, the control unit 34 includes a reception unit 50, an allocation unit 51, a management unit 52, and a release unit 53.

  The receiving unit 50 receives various types of information. For example, the reception unit 50 receives a session allocation request from the terminal device 11 to the image relay server 21.

  The assignment unit 51 assigns a session to the image relay server 21. For example, when the allocation unit 51 receives a session allocation request from the reception unit 50, the allocation unit 51 generates a new session ID. Further, the allocating unit 51 obtains the number of sessions in use and scheduled to be used for each image relay server 21. For example, based on the session information 41, the number of sessions whose state is not released is determined for each image relay server 21. In the present embodiment, the allocating unit 51 obtains the number of sessions whose status is either connected, connected, or abnormal for each image relay server 21. The session whose state is connected is a session that is assigned to the image relay server 21 and establishes communication from now on. A session whose state is connection is a session in use after communication is established. A session in an abnormal state is a session that cannot be released for some reason and remains. For this reason, in this embodiment, the number of sessions in which the state is connected, connected, or abnormal is obtained as the number of sessions in use or scheduled to be used.

  The allocating unit 51 identifies the image relay server 21 whose number of sessions has not reached the session upper limit stored in the relay server information 40. When there is no image relay server 21 whose number of sessions has not reached the session upper limit, the allocating unit 51 notifies the terminal device 11 that the number of sessions is not available and cannot be connected.

  When there is an image relay server 21 in which the number of sessions has not reached the session upper limit, the allocating unit 51 determines the image relay server 21 to be connected from among the image relay servers 21. The method for determining the image relay server 21 to be connected may be any method. For example, the allocating unit 51 may determine the image relay server 21 having the smallest number of sessions as the connection target image relay server 21 from the image relay servers 21 having the number of sessions less than the session upper limit. For example, the allocating unit 51 may determine the image relay server 21 having the largest number of sessions as the image relay server 21 to be connected from the image relay servers 21 having the number of sessions less than the session upper limit. That is, the allocating unit 51 may operate the image relay server 21 in a concentrated manner with the image relay server 21 having a large number of sessions as a connection target until the number of sessions reaches the session upper limit.

  The assignment unit 51 notifies the terminal device 11 that has requested assignment of the session ID and the IP address of the connection target image relay server 21.

  The terminal device 11 performs access by notifying the notified session ID to the image relay server 21 of the notified IP address. As a result, the image relay server 21 establishes a session with the terminal device 11 and the virtual browser server 22 and transfers information on the screen of the virtual browser operating on the virtual browser server 22 to the terminal device 11 as needed.

  The allocating unit 51 registers a record storing information related to the session allocated to the session information 41. For example, the assigning unit 51 sets the session ID as a new session ID, the connection date and time as the current date and time, the login ID as the user ID of the requesting user, the state as being connected, and the connection source IP address as the requesting source IP address. A record having the IP address of the terminal device 11 is registered.

  The management unit 52 manages the state of the session currently connected to each image relay server 21. For example, the management unit 52 periodically inquires each image relay server 21 about the connection status of the session. The period for inquiring the connection status is, for example, a value ranging from several seconds to several minutes, but may be set from the outside by an administrator or the like.

  When the image relay server 21 receives an inquiry about the connection status of the session from the management server 20, the image relay server 21 replies to the management server 20 with information regarding the currently connected session. For example, the image relay server 21 replies to the management server 20 with the session ID of the session being connected and the IP address of the virtual browser being connected in the session. As described above, when receiving an inquiry about the connection status of a session, the image relay server 21 replies to the management server 20 with information regarding the currently connected session. For this reason, for example, when the connection from the terminal device 11 is terminated and the session is released, information on the released session is not notified to the management server 20.

  The management unit 52 updates the session information 41 according to the answer from the image relay server 21. For example, the management unit 52 registers the virtual browser IP address of the session for which the session ID is notified in the session information 41. In addition, the management unit 52 updates the state of the session information 41 of the session for which the session ID is notified to connection. In addition, the management unit 52 deletes from the session information 41 the record of the session for which the session ID is no longer notified. As a result, when the connection from the terminal device 11 is terminated and released, the session ID is not notified from the image relay server 21, and the session record is deleted from the session information 41.

  In addition, the management unit 52 displays the state of the session currently connected to each image relay server 21 on the screen so that the administrator can check it. For example, when a predetermined operation is performed, the management unit 52 displays a system management screen for confirming the session state. The management unit 52 may receive an operation from another management terminal device connected to the management server 20 and display a system management screen on the terminal device, or may receive an operation from the input unit 32 and display it. The unit 31 may display a system management screen.

  FIG. 5 is a diagram illustrating an example of a system management screen. The system management screen 60 has a display area 61 for displaying various information related to a session for each session. In the example of FIG. 5, session connection date and time, login ID, state, connection source IP address, image relay SV, and virtual browser SV are displayed in the display area 61. The system management screen 60 is provided with a disconnect button 62 for instructing disconnection of a session for each session.

  Returning to FIG. 2, the release unit 53 releases the session. For example, when the disconnect button 62 is selected on the system management screen 60, the release unit 53 instructs the image relay server 21 connected by the session instructed to disconnect to disconnect the session instructed to disconnect. . Then, the release unit 53 updates the state of the session information 41 of the session instructed to be disconnected while being released, and stores the current date and time in the date and time of disconnection.

  On the other hand, in the virtual browser server 22, when the access to the in-house Web system 13 from the terminal device 11 is completed and the virtual browser is terminated, the virtual browser notifies the management server 20 of session disconnection. For example, the management server 20 is notified of the session ID of the session to be disconnected.

  When the disconnection of the session is notified, the release unit 53 updates the state of the session information 41 of the session notified of the disconnection while releasing, and stores the current date and time in the disconnection date.

[Communication flow]
Next, an example of a communication flow when the system 10 according to the present embodiment establishes a session and transfers an image will be described. FIG. 6 is a diagram schematically illustrating an example of a communication flow when establishing a session and transferring an image.

  When accessing the in-house Web system 13, the terminal device 11 accesses the management server 20 and requests assignment of a session to the image relay server 21 (FIG. 6 (1)).

  The management server 20 periodically inquires the connection status of the session to the image relay server 21, and manages the currently connected session by the session information 41 based on the answer to the inquiry (FIG. 6 (2) (3)). .

  When the management server 20 is requested to allocate a session from the terminal device 11 to the image relay server 21, the management server 20 notifies the terminal device 11 that is the allocation request source of the session ID and the IP address of the allocated image relay server 21 (FIG. 6 (4)).

  The terminal device 11 performs access by notifying the notified session ID to the image relay server 21 of the notified IP address ((5) in FIG. 6). The image relay server 21 accesses the virtual browser server 22 to establish a session ((6) in FIG. 6). The virtual browser server 22 activates the virtual browser and accesses the in-house Web system 13 by access from the image relay server 21 (FIGS. 6 (7) and (8)).

  The image relay server 21 acquires information on the screen of the virtual browser operating on the virtual browser server 22 (FIG. 6 (9)), and transfers the information on the screen of the virtual browser to the terminal device 11 as needed (FIG. 6 (10)). )).

  In the virtual browser server 22, when the access to the in-house Web system 13 from the terminal device 11 is completed and the virtual browser is terminated, the virtual browser notifies the management server 20 of disconnection of the session ((11) in FIG. 6).

  When the session disconnection is notified from the virtual browser server 22 in this manner, the management server 20 releases the session assignment (FIG. 6 (12)). For example, the management server 20 updates the state of the session information 41 of the session for which the disconnection has been notified during release. Then, the management server 20 instructs the image relay server 21 connected by the session notified of disconnection to release the session notified of disconnection (FIG. 6 (13)).

  Thus, the management server 20 according to the present embodiment releases the session assignment when the session disconnection is notified. As a result, the management server 20 can effectively use the connectable session because the session notified of disconnection is released earlier.

[Process flow]
Next, a flow of session management processing in which the management server 20 according to the present embodiment manages a session will be described. FIG. 7 is a flowchart illustrating an exemplary procedure of session management processing. This session management process is executed, for example, at a timing when a request for assigning a session from the terminal device 11 to the image relay server 21 is received.

  As shown in FIG. 7, the assigning unit 51 generates a new session ID (S10). Also, the allocating unit 51 determines the connection target image relay server 21 based on the session information 41 and the relay server information 40 (S11). The allocating unit 51 returns the session ID and the IP address of the connection target image relay server 21 as connection destination information to the terminal device 11 that is the allocation request source (S12). The allocating unit 51 registers a record storing information related to the session allocated by the session ID in the session information 41 (S13).

  The management unit 52 periodically inquires each image relay server 21 about the connection status of the session, and determines whether or not the session is established within a predetermined time (S14). If the session is not established within the predetermined time (No at S14), the process is terminated assuming that the session establishment has failed.

  On the other hand, when the session is established within the predetermined time (Yes in S14), the management unit 52 updates the state of the session information 41 of the session in which the session is established to connection (S15).

  The release unit 53 determines whether a session disconnection is notified from the virtual browser (S16). When the disconnection of the session is notified (Yes at S16), the release unit 53 updates the state of the session information 41 of the session notified of the disconnection while releasing (S17), and proceeds to S21 described later.

  On the other hand, when the session disconnection is not notified (No in S16), the release unit 53 determines whether any session disconnection is instructed on the system management screen 60 (S18). If session disconnection is not instructed (No at S18), the process proceeds to S16 described above. When the session disconnection is instructed (Yes in S18), the release unit 53 instructs the image relay server 21 connected by the session instructed to disconnect to disconnect the session instructed to disconnect (S19). . The release unit 53 updates the state of the session information 41 of the session instructed to be disconnected during release (S20).

  The management unit 52 periodically inquires the connection status of the session to each image relay server 21 (S21), and determines whether or not the session updated while releasing the state is released (S22). If the session is released (Yes at S22), the record of the session information 41 of the released session is deleted, and the process ends.

  On the other hand, when the session has not been released (No at S22), the management unit 52 determines whether or not a certain time required for releasing the session has elapsed since the state was updated during release (S23). If the predetermined time has not elapsed (No at S23), the process proceeds to S21 described above.

  On the other hand, when the predetermined time has elapsed (Yes in S23), the management unit 52 abnormally updates the state of the session information 41 of the session that is not released (S24). The release unit 53 instructs the image relay server 21 having a session with an abnormal state to release the session with an abnormal state (S25). The management unit 52 deletes the record of the session information 41 of the session whose state is abnormal (S26), and ends the process.

[effect]
As described above, the image relay server 21 relays the processing result of the application executed by the virtual browser server 22. The management server 20 manages a session relayed by the image relay server 21. The management server 20 accepts a session allocation request from the terminal device 11 and returns connection destination information of the image relay server 21 to be accessed to the terminal device 11 to the terminal device 11. The image relay server 21 connects a session for relaying the terminal device 11 and the virtual browser server 22 based on the access of the terminal device 11. In response to the disconnection of the session relayed by the image relay server 21, the management server 20 receives the disconnection of the session notified from the virtual browser server 22, and releases the allocation of the notified session. As a result, the management server 20 can immediately assign the session notified of the disconnection next, so that the connectable session can be effectively used.

  That is, the management server 20 allocates a session to the image relay server 21 when a session allocation to the image relay server 21 that manages the session is requested. Further, the management server 20 periodically inquires the connection status of the session to the image relay server 21 and manages the currently connected session. When the management server 20 is notified of information indicating that the session is disconnected from the virtual browser operating in the connected session, the management server 20 releases the allocation of the session. As a result, the management server 20 can immediately assign the session notified of the disconnection next, so that the connectable session can be effectively used.

  In addition, when the release of the session is instructed from the system management screen 60 for managing the session, the management server 20 manages the state of the session to be released as being released. This releasing session is a session to be released. Since the management server 20 manages a session that has not been released yet but is being released as being released, it can be allocated to the next session allocation request, so that a connectable session can be used effectively.

  When the released session remains in the image relay server 21, the management server 20 instructs the image relay server 21 to release the session. As a result, the management server 20 can release a session that has been released if it remains in the image relay server 21, so that a connectable session can be used effectively.

  Although the embodiments related to the disclosed apparatus have been described so far, the disclosed technology may be implemented in various different forms other than the above-described embodiments. Therefore, another embodiment included in the present invention will be described below.

  For example, in the above embodiment, the case where the screen of the in-house Web system 13 is transferred by a virtual browser has been described, but the disclosed system is not limited to this. For example, a PC screen used by the user in the company may be transferred.

  In the above-described embodiment, the case has been described in which the virtual browser server 22 operates a browser such as Internet Explorer as a virtual browser as an application, but the disclosed system is not limited thereto. For example, the application executed by the virtual browser server is not limited to the browser, and may be any program as long as it generates information to be transferred to the terminal device 11.

  In the above-described embodiment, the case where the management server 20, the image relay server 21, and the virtual browser server 22 are different physical servers has been described. However, the disclosed apparatus is not limited thereto. For example, the same physical server may serve as the image relay server 21 and the virtual browser server 22. Any of the management server 20, the image relay server 21, and the virtual browser server 22 may be a virtual machine. For example, one or a plurality of VMs (Virtual Machines) may be operated on a physical server, and the VM may function as the management server 20, the image relay server 21, and the virtual browser server 22. That is, the management server 20 may be functionally operated as a management unit, the image relay server 21 may be operated as a relay unit, and the virtual browser server 22 may be operated as an execution unit by one or a plurality of servers.

  In the above-described embodiment, a case has been described in which the state of a session instructed to be released from the system management screen 60 and the state of a session in which disconnection is notified from the virtual browser server 22 are managed as being released. It is not limited to. For example, a record of a session instructed to be released from the system management screen 60 and a session in which disconnection is notified from the virtual browser server 22 may be deleted from the session information 41.

  In the above-described embodiment, a case has been described in which a released session notified of disconnection is immediately assigned next, but the disclosed apparatus is not limited thereto. For example, the management server 20 may perform the following process when the session information 41 includes a session updated while being released and receives a session allocation request from the terminal device 11. The management server 20 may exclude the connection destination information of the relay server 21 managed in the session updated during the release from the connection destination information of the relay server 21 that returns to the terminal device 11. That is, when the terminal device 11 that has received the session allocation request is not the terminal device 11 that is managed in the session information 41 that is updated while being released, the management server 20 is connected in the session that is being released. The relay server 21 may be excluded from the relay server 21 that replies to the terminal device 11. In addition, when the terminal device 11 that has received the session allocation request is the terminal device 11 that is managed by the session updated while being released to the session information 41, the management server 20 returns connection destination information. May be. In other words, when the terminal device 11 that has received the session allocation request is the terminal device 11 that is managed in the session information 41 that is updated while being released, the management server 20 is connected in the session that is being released. The relay server 21 may be the relay server 21 that sends a reply to the terminal device 11. Thereby, the session can be effectively utilized by notifying the terminal device 11 of the same relay server 21 as the session being released. For example, the session can be effectively used by causing the terminal device 11 to perform communication using the open session again.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific state of distribution / integration of each device is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the processing units of the reception unit 50, the allocation unit 51, the management unit 52, and the release unit 53 of the management server 20 may be appropriately integrated. Further, the processing of each processing unit may be appropriately separated into a plurality of processing units. Further, all or any part of each processing function performed in each processing unit can be realized by a CPU and a program analyzed and executed by the CPU, or can be realized as hardware by wired logic. .

[Session management program]
The various processes described in the above embodiments can also be realized by executing a program prepared in advance on a computer system such as a personal computer or a workstation. Therefore, in the following, an example of a computer system that executes a program having the same function as in the above embodiment will be described. FIG. 8 is a diagram illustrating a computer that executes a session management program.

  As illustrated in FIG. 8, the computer 300 includes a central processing unit (CPU) 310, a hard disk drive (HDD) 320, and a random access memory (RAM) 340. These units 310 to 340 are connected via a bus 400.

  The HDD 320 stores in advance a session management program 320a that exhibits the same functions as the reception unit 50, the allocation unit 51, the management unit 52, and the release unit 53 of the management server 20 described above. Note that the session management program 320a may be separated as appropriate.

  The HDD 320 stores various information. For example, the HDD 320 stores various data used for various controls including OS and session management.

  Then, the CPU 310 reads out and executes the session management program 320a from the HDD 320, thereby executing the same operation as each processing unit of the embodiment. That is, the session management program 320a performs the same operations as the reception unit 50, the allocation unit 51, the management unit 52, and the release unit 53.

  Note that the session management program 320a is not necessarily stored in the HDD 320 from the beginning.

  For example, the program is stored in a “portable physical medium” such as a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, or an IC card inserted into the computer 300. Then, the computer 300 may read and execute the program from these.

  Furthermore, the program is stored in “another computer (or server)” connected to the computer 300 via a public line, the Internet, a LAN, a WAN, or the like. Then, the computer 300 may read and execute the program from these.

DESCRIPTION OF SYMBOLS 10 System 11 Terminal apparatus 12 External network 13 In-house Web system 20 Management server 21 Image relay server 22 Virtual browser server 30 Communication I / F part 31 Display part 32 Input part 33 Storage part 34 Control part 40 Relay server information 41 Session information 50 Reception Unit 51 Allocation unit 52 Management unit 53 Release unit 60 System management screen

Claims (7)

A relay unit that relays the processing results of the application executed by the execution unit;
A session management program executed by a management unit that manages a session relayed by the relay unit,
The management unit
For a session relayed by the relay unit, when disconnection is notified from the execution unit, or when disconnection is instructed, in any case, managing the session as releasing the state,
When the terminal accepting an session allocation request for each of the relay unit, the state counts the number of sessions other than during release,
From among the relay units whose number of sessions is less than a predetermined upper limit value, determine the relay unit to be accessed by the terminal ,
The determined connection destination information of the relay unit to reply to the terminal,
The relay unit is
Based on the access of the terminal, connecting a session relaying the terminal and the execution unit,
The management unit
In response to disconnection of the session relayed by the relay unit, the disconnection of the session notified from the execution unit is received,
A session management program for executing a process for releasing the notified session allocation. The management unit
Query the connection status of the session to the relay unit, update the session information based on the answer to the inquiry,
The session management program according to claim 1, wherein the connection destination information of the relay unit that returns to the terminal is generated based on the session information. A relay unit that connects a session that relays the terminal and an execution unit that executes application processing based on the access of the terminal, and relays a processing result of the application executed by the execution unit;
When a session is relayed by the relay unit, when the disconnection is notified from the execution unit, or when disconnection is instructed, the session is managed as being released in any case, and the session is allocated from the terminal. determining the request Ru accepted, for each of the relay unit, the state counts the number of non during release session from among the number of sessions of the relay portion less than a predetermined upper limit value, the relay unit for access to the terminal The determined connection destination information of the relay unit is returned to the terminal, and when the session disconnection notified from the execution unit is received in response to the session disconnection relayed by the relay unit, the notified session A management unit to release the allocation of
A session management apparatus comprising: A relay unit that relays the processing results of the application executed by the execution unit;
A session management method executed by a management unit that manages a session relayed by the relay unit,
The management unit
For a session relayed by the relay unit, when disconnection is notified from the execution unit, or when disconnection is instructed, in any case, managing the session as releasing the state,
When the terminal accepting an session allocation request for each of the relay unit, the state counts the number of sessions other than during release,
From among the relay units whose number of sessions is less than a predetermined upper limit value, determine the relay unit to be accessed by the terminal ,
The determined connection destination information of the relay unit to reply to the terminal,
The relay unit is
Based on the access of the terminal, connecting a session relaying the terminal and the execution unit,
The management unit
In response to disconnection of the session relayed by the relay unit, the disconnection of the session notified from the execution unit is received,
A session management method characterized by executing a process of releasing the notified session allocation. A relay unit that relays the processing results of the application executed by the execution unit;
A session management program executed by a management unit that manages a session relayed by the relay unit,
The management unit
For a session relayed by the relay unit, when disconnection is notified from the execution unit, or when disconnection is instructed, in any case, managing the session as releasing the state,
Inquire the connection status of the session to the relay unit periodically, delete the session management information as a disconnection of the session for which the connection status is not notified,
Accept session allocation request from terminal,
If the terminal that has received the allocation request is a terminal connected in the released session, the connection destination information of the relay unit that relays the released session is returned to the terminal, and the terminal that has received the allocation request In a case other than the terminal connected in the released session, the connection destination information of the relay unit other than the relay unit that relays the released session is returned to the terminal,
The relay unit is
Based on the access of the terminal, connecting a session relaying the terminal and the execution unit,
The management unit
In response to disconnection of the session relayed by the relay unit, the disconnection of the session notified from the execution unit is received,
Release the reported session allocation
A session management program characterized by causing a process to be executed. A relay unit that connects a session that relays the terminal and an execution unit that executes application processing based on the access of the terminal, and relays a processing result of the application executed by the execution unit;
For a session relayed by the relay unit, when disconnection is notified from the execution unit, or when disconnection is instructed, the session is managed as being released in any case, and The session connection status is periodically inquired, the session management information is deleted as if the session for which the connection status was not notified is disconnected, the session allocation request is accepted from the terminal, and the terminal that received the allocation request is released The connection destination information of the relay unit that relays the released session is returned to the terminal, and the terminal that accepted the allocation request is connected in the released session. In a case other than the terminal, the connection destination information of the relay unit other than the relay unit that relays the released session is sent to the terminal And Shin, depending on the cut of the session in which the relay unit relays, receiving the termination of the session notified from the execution unit, a management unit to release the allocation of the announced session,
A session management apparatus comprising: A relay unit that relays the processing results of the application executed by the execution unit;
A session management method executed by a management unit that manages a session relayed by the relay unit,
The management unit
For a session relayed by the relay unit, when disconnection is notified from the execution unit, or when disconnection is instructed, in any case, managing the session as releasing the state,
Inquire the connection status of the session to the relay unit periodically, delete the session management information as a disconnection of the session for which the connection status is not notified,
Accept session allocation request from terminal,
If the terminal that has received the allocation request is a terminal connected in the released session, the connection destination information of the relay unit that relays the released session is returned to the terminal, and the terminal that has received the allocation request In a case other than the terminal connected in the released session, the connection destination information of the relay unit other than the relay unit that relays the released session is returned to the terminal,
The relay unit is
Based on the access of the terminal, connecting a session relaying the terminal and the execution unit,
The management unit
In response to disconnection of the session relayed by the relay unit, the disconnection of the session notified from the execution unit is received,
Release the reported session allocation
The session management method characterized by performing a process.

Images