Source: https://patents.google.com/patent/JP2008140306A/en
Timestamp: 2020-04-09 14:28:00
Document Index: 101643263

Matched Legal Cases: ['Application No. 2006', 'Application No. 2006', 'art 21', 'art 22', 'art 23', 'art 32']

JP2008140306A - Connection management method and connection management server in thin client - Google Patents
Connection management method and connection management server in thin client Download PDF
JP2008140306A
JP2008140306A JP2006328129A JP2006328129A JP2008140306A JP 2008140306 A JP2008140306 A JP 2008140306A JP 2006328129 A JP2006328129 A JP 2006328129A JP 2006328129 A JP2006328129 A JP 2006328129A JP 2008140306 A JP2008140306 A JP 2008140306A
JP2006328129A
JP4293234B2 (en
Masahiko Kimizuka
Kunihiro Koshiba
政彦 君塚
国博 小柴
2006-12-05 Application filed by Nec Corp, 日本電気株式会社 filed Critical Nec Corp
2006-12-05 Priority to JP2006328129A priority Critical patent/JP4293234B2/en
2008-06-19 Publication of JP2008140306A publication Critical patent/JP2008140306A/en
2009-07-08 Publication of JP4293234B2 publication Critical patent/JP4293234B2/en
In a thin client system, environment construction and operation when a plurality of users share a plurality of clients are greatly improved, and a client on a thin client server can be restarted from the thin client terminal side. .
A group information management table for holding a result of grouping a client, a thin client terminal, and a user in advance in a connection management server that manages connection from the thin client terminal to the thin client server; A connection destination setting information table 24 indicating a client group corresponding to a combination of a thin client terminal group and a user group, and a client state management table 25 for holding the state of each client 11 are provided, and the group information is keyed. To enable connection management.
The present invention relates to a connection management method in a system (thin client system) using a thin client terminal and a thin client server, and a connection management server for executing such a connection management method.
In a conventional client server system, a PC (personal computer) including a magnetic disk device is used as a client terminal. However, in recent years, a single user uses a plurality of PCs or shares a single PC for a plurality of business operations due to the complexity of business operations. As a result, software for client terminals is used. In combination with the increasing complexity, the management cost of client terminals is rising. Furthermore, the presence of a storage device such as a magnetic disk device in the client terminal increases the possibility of information leakage. Therefore, a diskless (no storage device such as a magnetic disk device) or a terminal for which writing to the disk is prohibited (hereinafter referred to as a thin client terminal), an operating system (OS) and a business that holds data A business system has been constructed by combining a server on which an application is executed (hereinafter referred to as a thin client server). In Japanese Patent Application No. 2006-166559, the present applicant has already proposed a session management method in which the OS on the thin client server side can be started and shut down from the thin client terminal side.
A thin client server executes a business application executed by a client terminal in a conventional client-server system, and therefore has a client as an execution unit (execution image) for each thin client terminal. In the client, an OS, a business application, and data allocated for each connection from the thin client terminal are installed. In general, since a thin client server manages a plurality of thin client terminals, a plurality of clients operate on the same thin client server.
In such a thin client system, a user connects a thin client terminal to a client in a thin client server, and causes the client to execute a business application. Then, input necessary for executing the business application is performed via the thin client terminal, and the execution result of the business application is confirmed on the screen of the thin client terminal.
In such a thin client system, management of connection of the thin client terminal to the thin client server, including authentication of the user who uses the thin client terminal, is performed using the individual as a key, such as the user and the thin client terminal. (For example, see Japanese Patent Application No. 2006-166559). When such a connection management method is used, it is necessary to set one or more clients per user on the thin client server, and an operation in which a plurality of users share one client. It is difficult. Also, if any failure occurs in the thin client server, the user connected to the client on the server cannot connect to the client from the thin client terminal until the thin client server returns to a normal state. There is a problem that it becomes impossible to work.
Furthermore, unlike a conventional client-server system, a thin client system cannot restart a client at any timing of the user. This means that users cannot perform operations that require restarting the client, such as applying security patches to business applications or updating software, and the system administrator must perform these operations. It led to an increase in the burden on the administrator.
In the conventional session management method between a thin client terminal and a thin client server, in an environment where M users in the thin client server are shared by N users, M × N connection definitions are required, and management is required. There is a problem that it becomes complicated. Also, in actual operation, there was no way for the user to know in advance which client was unused, so when connecting a thin client terminal to a thin client server, an unused client was searched. Had to try the clients in order. Further, when the client in use cannot be controlled, it is necessary to contact the system administrator and specify the client being used by a log or the like and then restart the client.
Accordingly, an object of the present invention is to greatly improve the environment construction and operation when a plurality of users share a plurality of clients. In addition, a problem occurs in a specific client in the shared client environment and the control becomes impossible. In such a case, it is an object of the present invention to provide a connection management method and a connection management server in a thin client system that can safely restart only the specific client by an operation from the user side.
In the present invention, users, thin client terminals, and clients on a thin client are grouped into a user group, a terminal group, and a client group, respectively, and a connection condition to a client on a thin client server according to the group. And managing the connection from the thin client terminal to the thin client server using the group information as a key.
That is, a first connection management method of the present invention is a connection management method in a thin client system having a thin client terminal and a thin client server having a client connected from the thin client terminal and executing an application. In the client terminal, accepting the user ID of the user who is going to connect to the client, transmitting the user ID and the thin client terminal information corresponding to the thin client terminal to the connection management server, and the connection in the connection management server Based on the information received from the thin client terminal, the destination management unit searches for information on connectable client groups from the connection destination setting information table, and returns the search result to the thin client terminal. search results Transmitting information on the client group selected by the user to the connection management server, and the connection destination management unit searches the client status management table for available clients based on the information on the selected client group; Transmitting the searched client information to the thin client terminal, and the thin client terminal connecting to the corresponding client based on the received client information.
A second connection management method of the present invention is a connection management method in a thin client system having a thin client terminal and a thin client server having a client connected to the thin client terminal and executing an application, The terminal accepts the user ID of the user who wants to restart the client, sends the user ID and the thin client terminal information corresponding to the thin client terminal to the connection management server, and the connection destination in the connection management server Based on the information received from the thin client terminal, the management unit searches the client state management table for information about the client group that can be restarted, and returns the search result to the thin client terminal. result A step of transmitting information on the client group selected by the user to the connection management server, a step of transmitting information on the selected client group to the activation control unit in the connection management server, and activation control. A section specifying a client to which the thin client terminal is currently connected from the information on the selected client group, and requesting restart of the client from the thin client server including the specified client.
In the connection management method of the present invention, the client, the thin client terminal, and the user are grouped in advance, and the grouping result is held in the group information management table, and the connection destination management unit receives from the thin client terminal It is preferable to determine the group by referring to the group information management table based on the information, and to search for information on the client group based on the determination result.
A first connection management server of the present invention is a connection management server used in a thin client system having a thin client terminal and a thin client server having a client connected to the thin client terminal and executing an application, A group information management table that holds the results of grouping clients, thin client terminals, and users in advance, and a connection destination setting information table that indicates a client group corresponding to a combination of a thin client terminal group and a user group And a client status management table that holds the status of each client for each client, a user ID and a thin client terminal information received from the thin client terminal. Search for group information from the group information management table and connection destination setting information table, return the search result to the thin client terminal, and use the available client based on the information about the selected client group received from the thin client terminal A connection destination management unit that searches the client state management table and transmits information of the found client to the thin client terminal.
A second connection management server of the present invention is a connection management server used in a thin client system having a thin client terminal and a thin client server having a client connected to the thin client terminal and executing an application, A group information management table that holds the results of grouping clients, thin client terminals, and users in advance, a client status management table that holds the client status for each client, and a restart of the client that has the client Based on the start control unit requested from the client server, the user ID received from the thin client terminal, and the thin client terminal information, information on the restartable client group is displayed on the client. Search from the status management table, return the search result to the thin client terminal, identify an available client based on the information about the selected client group received from the thin client terminal, and use the activation control unit to identify the identified client A connection destination management unit to be restarted.
The first effect of the present invention is that resources of a thin client system can be used more efficiently than in the conventional method.
The reason is that the client connection conditions on the thin client server are user groups, terminal groups, and client groups on the thin client server. It can be used by multiple users at different times, and even if one thin client server fails, users can use clients on other thin client servers in the same client group. This is because the use of resources of the thin client system becomes more flexible such that the user cannot connect to the client on the thin client server and the business itself cannot be performed.
The second effect of the present invention is that the burden on management can be reduced for the administrator of the thin client system.
The reason is that the client on the thin client server can be restarted at any time of the user, so the client on the thin client server can apply the security patch, update the software, or stop the client OS. This is because, when it is necessary to restart the system, there are more opportunities for the user to solve the problem without bothering the administrator.
As described above, in the present invention, the environment construction and operation when a plurality of users share a plurality of clients are greatly improved by grouping clients, thin client terminals, and users. Also, in the shared client environment, even if the client you are using fails and you are unable to control it, a means to safely restart only the client you are using is provided. Can be reduced.
Next, a preferred embodiment of the present invention will be described with reference to the drawings. FIG. 1 shows an example of the configuration of a thin client system to which the connection management method of the present invention is applied.
The illustrated thin client system includes N thin client servers 1 (N is an integer of 2 or more), a plurality of thin client terminals 3, and connections from the thin client terminals 3 to clients 11 on the thin client server 1. And a connection management server 2 for managing the connection. The connection management server 2 is provided in a network that connects the thin client server 1 and the thin client terminal 3.
Each thin client server 1 includes a plurality of clients 11 as program execution units (execution images) corresponding to the thin client terminals, and a client control unit 12 that executes activation and restart processing of each client 11. . The client control unit 12 is provided in common for a plurality of clients 11 in the thin client server 1. As described above, each client 11 is installed with an OS (client OS), a business application, and data allocated for each connection from the thin client terminal, and further includes a state acquisition unit 111. The information acquisition unit 111 has a function of transmitting the state of the client 11 (power on, power off, log off, logon, etc.) to the connection destination management unit 21 of the connection management server 2.
The connection management server 2 includes a connection destination management unit 21, a start control unit 22, a group information management table 23, a connection destination setting information table 24, and a client state management table 25. For the connection from the thin client terminal 3 to the client 11, the connection destination management unit 21 determines the connection destination client for the thin client terminal 3 and restarts the client in response to a request from the thin client terminal 3. It has a function to perform. The activation control unit 12 has a function of accepting requests from the thin client terminal 3 and the connection destination management unit 21 regarding the activation and restart of the client 11 and passing the accepted requests to the client control unit 12 of the corresponding thin client server. .
In the group information management table 23, the connection destination setting information table 24, and the client state management table 25, information necessary for the connection destination management unit 21 to perform connection management is stored. In the group information management table 23, as shown in FIG. 2, each information of a user (user ID), a thin client terminal, and a client, and which group each user, thin client terminal, and client belong to Information is stored. As shown in FIG. 3, the connection destination setting information table 24 stores information (linking information) related to a user (user ID) group and a thin client terminal group that can be connected to each client group. As shown in FIG. 4, the client status management table 25 stores information for each client regarding the status of the client 11. The data in the group information management table 23 and the connection destination setting information table 24 must be set before the operation of the thin client system is started (before the user connects to the client 11).
The thin client terminal 3 includes a connection unit 31 and a connection destination control unit 32. The connection destination control unit 32 acquires input of user ID information from the user on the thin client terminal 3, and connects the input information and the thin client terminal information of the thin client terminal to the connection destination management unit of the connection management server 2. 21, and thereafter, the client information that can be connected is acquired from the connection destination management unit 21 and transmitted to the connection unit 31. The connection unit 31 has a function of connecting to the client 11 using the received information.
Next, the operation of this embodiment will be described in detail.
First, a connection management procedure when a connection is made from the thin client terminal 3 to the thin client server 1 will be described with reference to FIG.
When a user tries to connect to the client 11 using the thin client terminal 3, the user inputs his / her user ID to the thin client terminal 3 at the start of use of the thin client terminal 3 (step Z1). To do. Then, the connection destination control unit 32 acquires user information (user ID) input from the user (step Z2), and next, the input user information and the thin client terminal 3 used by the user. Information (thin client terminal information) is transmitted to the connection destination management unit 21 of the connection management server 2 (step Z3). The connection destination management unit 21 receives the user information and the thin client terminal information (step Z4), and uses the received user information and the thin client terminal information to identify a client group associated with the information. Extracted from the connection destination setting information table 24 (step Z5). That is, in step Z5, the connection destination management unit 21 searches for a method related to a connectable client group using the received user information and thin client terminal information.
The contents of the group information management table 23 are as shown in FIG. 2, the contents of the connection destination setting information table 24 are as shown in FIG. 3, and the connection destination management unit 21 displays “user #” as user information (user ID). 1 ”and“ thin client terminal # 1 ”is received as the thin client terminal information, the extraction process in step Z5 will be described.
In this case, referring to the group information management table 23, “user # 1” belongs to the group “UA” and “thin client terminal # 1” belongs to the group “TA”. Further, referring to the connection destination setting information table 24, the client group associated with the combination of the user group “UA” and the thin client terminal group “TA” is “CA”. For this reason, the connection destination management unit 21 searches the connection destination setting information table 24 and extracts “C-A” as a connectable client group. In the example shown in FIG. 3, in the connection destination setting information table 24, only one of the user information (user ID) and the thin client terminal group is associated with the client groups “CC” and “CD”. However, in the case of the client group “C-C”, any thin client terminal whose user information (user ID) belongs to “UA” The client group “CD” means that any user who belongs to the thin client terminal group “TA” can be connected.
Information relating to connectable client groups extracted in this way is transmitted from the connection destination management unit 21 to the connection destination control unit 32 of the thin client terminal 3 (step Z6). In response to this, in the thin client terminal 3, the client group information is received by the connection destination control unit 32 (step Z7), and information relating to connectable client groups is displayed on the screen. Therefore, the user selects a client group to be connected from the connectable client groups and inputs it to the thin client terminal 3 (step Z8). As a result, the connection destination control unit 32 transmits information regarding the selected client group to the connection destination management unit 21.
The connection destination management unit 21 receives information on the selected client group and searches the client status management table 25 to select a client 11 that can be used for the client group, that is, any user logs on. A client that has not been selected is selected (step Z9). If the selected client is in a state where connection is not possible, such as a power-off state, the connection destination management unit 21 activates the corresponding client 11 via the activation control unit 22. A request is made to the client control unit 12 of the client server 1 (step Z10), and the client control unit 12 starts the client 11 (restart depending on the state of the client 11) (step Z11). Then, the connection destination management unit 21 transmits information about the client 11 to the connection destination control unit 32 in the thin client terminal 3. Here, when there is no need to start or restart the client 11, it is assumed that the process directly proceeds from step Z9 to the following step Z12.
The connection destination control unit 32 that has received information on the client 11 to be connected in this manner inputs the information on the client 11 to the connection unit 31 in the thin client terminal 3 (step Z12). As a result, the connection unit 31 connects to the client 11 (step Z13), and the status acquisition unit 111 on the client 11 updates the status of the client 11 in the client status management table 25 via the connection destination management unit 21 ( Step Z14).
As described above, the thin client terminal 3 is connected to the client 11. Here, the operations that the user should perform for client selection and connection are only the input of user information (user ID) and the selection of the client group to be connected. All other operations are automatically processed. Is done. Therefore, the user does not need to try the clients in order to search for unused clients.
Next, processing when the client 11 is restarted from the thin client terminal 3 will be described with reference to FIG.
When restarting the client 11, the connection destination control unit 32 of the thin client terminal 3 needs to be started in a restart mode different from the connection to the client 11 described above.
When the user intends to restart the client 11 using the thin client terminal 3, the user inputs his / her user ID to the thin client terminal 3 at the start of use of the thin client terminal 3 (step Y1). To do. The connection destination control unit 32 acquires user information (user ID) input from the user (step Y2), and inputs the user information and information of the thin client terminal 3 used by the user (thin client). Terminal information) is transmitted to the connection destination management unit 21 of the connection management server 2 (step Y3). The connection destination management unit 21 receives the user information and the thin client terminal information (step Y4), and uses the received user information and the thin client terminal information to assign a restartable client group to the client state management table 25. (Step Y5). That is, the connection destination management unit 21 searches for a client group to which a client to which the user is currently connected belongs. Here, the condition of “restartable client group” is that the client 11 already connected by the user exists in the client group.
The contents of the group information management table 23 are as shown in FIG. 2, the contents of the client state management table 25 are as shown in FIG. 4, and the connection destination management unit 21 sets “user # 1 as user information (user ID)”. ”And“ Thin client terminal # 1 ”as thin client terminal information is received, the extraction process in step Y5 will be described.
In this case, by referring to the client state management table 25, it is possible to confirm that the client 11 connected by “user # 1” and “thin client terminal # 1” is “client # 1-2”. Referring to the group information management table 23, since “client # 1-2” belongs to the group “CB”, the client group information transmitted to the connection destination control unit 32 in this case is the group “C”. -B ". Here, if the connection destination management unit 21 receives the information “user # 2” and “thin client terminal # 1”, it can be seen from the client state management table 25 that there is no client 11 that can be restarted. The client group information transmitted to the connection destination control unit 32 is information indicating “none”.
Information relating to the restartable client group extracted in this manner is transmitted from the connection destination management unit 21 to the connection destination control unit 32 of the thin client terminal 3 (step Y6). In response to this, in the thin client terminal 3, the client group information is received by the connection destination control unit 32 (step Y7), and information relating to the restartable client group is displayed on the screen. Therefore, the user selects a client group to be restarted from the restartable client groups and inputs it to the thin client terminal 3 (step Y8). As a result, the connection destination control unit 32 transmits information regarding the selected client group to the connection destination management unit 21.
The connection destination management unit 21 receives information on the selected client group, selects a restartable client 11 from the clients 11 belonging to the client group selected by the user, and information on the client 11 Is transmitted to the activation control unit 22 (step Y9). Here, it is a condition that the client 11 can be restarted that the user is already connected.
Next, the activation control unit 22 requests the client control unit 12 to restart the corresponding client 11 notified from the connection destination management unit 21 (step Y10). The client control unit 12 restarts the corresponding client 11 (step Y11). When the restart is completed, the connection destination control unit 32 receives a notification to that effect from the startup control unit 22 (step Y12), and the connection destination control unit 32 sends information on the client that has been restarted to the connection unit 31. Input (step Y13). As a result, the connection unit 31 connects to the client 11 (step Y14), and the status acquisition unit 111 on the corresponding client 11 updates the status of the client 11 in the client status management table 25 via the connection destination management unit 21. (Step Y15).
As described above, the user can restart the client 11 via the thin client terminal 3. Here, the operations that the user should perform to restart the client are only the input of user information (user ID) and the selection of the client group to be restarted. All other operations are automatically processed. Is done. Therefore, the user can restart the client without contacting the system administrator even when the client being used cannot be controlled.
In the thin client system of the present embodiment described above, a connection management server including the group information management table 23, the connection destination setting information table 24, and the client state management table 25 is provided, and each of the client, the thin client terminal, and the user is provided. And information on how the groups are grouped is written in the group information management table 23 in advance, and connection conditions for each group are written in the connection destination setting information table in advance. By constantly reflecting in the state management table 25, it is possible to greatly improve environment construction and operation when a plurality of users share a plurality of clients.
In the thin client system described above, each of the thin client server 1 and the connection management server 2 is a program for causing a computer such as a server computer to execute the above-described processing as a thin client server or processing as a connection management server. It is also configured by reading a program for executing the program and causing the program to be executed. Such a program is read into a computer by a storage medium such as a CD-ROM or a magnetic tape, or via a network. Such a program is also included in the category of the present invention.
INDUSTRIAL APPLICABILITY The present invention can be used to realize a thin client system that can realize the same convenience as a conventional client server system when operating a thin client system and can easily replace a conventional client server system. it can.
It is a block diagram which shows an example of a structure of the thin client system to which the connection management method of one Embodiment of this invention is applied. It is a figure which shows an example of a structure of a group information management table. It is a figure which shows an example of a structure of a connection destination setting information table. It is a figure which shows an example of a structure of a client state management table. It is a flowchart which shows the procedure of the connection management from a thin client terminal to a thin client server. It is a flowchart which shows the procedure of restart of a client.
DESCRIPTION OF SYMBOLS 1 Thin client server 2 Connection management server 3 Thin client terminal 11 Client 12 Client control part 21 Connection destination management part 22 Startup control part 23 Group information management table 24 Connection destination setting information table 25 Client state management table 31 Connection part 32 Connection destination control Part
A connection management method in a thin client system comprising: a thin client terminal; and a thin client server having a client connected from the thin client terminal and executing an application,
In the thin client terminal, receiving a user ID of a user trying to connect to the client, and transmitting the user ID and thin client terminal information corresponding to the thin client terminal to a connection management server;
Based on the information received from the thin client terminal, the connection destination management unit in the connection management server searches the connection destination setting information table for information on connectable client groups, and returns the search result to the thin client terminal. And the stage of
The thin client terminal transmitting information on the client group selected by the user based on the search result to the connection management server;
The connection destination management unit searches for available clients from a client state management table based on information about the selected client group, and transmits the searched client information to the thin client terminal.
The thin client terminal connecting to the corresponding client based on the received information of the client;
A connection management method.
In the thin client terminal, receiving a user ID of a user who intends to restart the client, and transmitting the user ID and thin client terminal information corresponding to the thin client terminal to a connection management server;
Based on the information received from the thin client terminal, the connection destination management unit in the connection management server searches the client state management table for information on the restartable client group, and returns the search result to the thin client terminal. And the stage of
The connection destination management unit transmits information on the selected client group to an activation control unit in the connection management server;
The activation control unit identifying a client to which the thin client terminal is currently connected from the information regarding the selected client group, and requesting the thin client server including the identified client to restart the client; ,
The client, the thin client terminal, and the user are grouped in advance, and the grouping result is held in a group information management table,
The connection destination management unit determines a group by referring to the group information management table based on information received from the thin client terminal, and searches for information on the client group based on the determination result. Item 3. The connection management method according to Item 1 or 2.
A connection management server used in a thin client system comprising: a thin client terminal; and a thin client server having a client connected from the thin client terminal and executing an application,
A group information management table for holding a result of grouping the client, the thin client terminal, and the user in advance;
A connection destination setting information table indicating the group of clients corresponding to the combination of the group of thin client terminals and the group of users;
A client status management table that holds the status of the client for each client;
Based on the user ID and the thin client terminal information received from the thin client terminal, information on connectable client groups is retrieved from the group information management table and the connection destination setting information table, and the retrieval result is retrieved from the thin client. Returns to the terminal, searches the client status management table for available clients based on the information about the selected client group received from the thin client terminal, and sends the searched client information to the thin client terminal A connection management server.
The connection management server according to claim 4, further comprising a start control unit that requests the thin client server having the client to start or restart the searched client.
An activation control unit that requests the thin client server having the client to restart the client;
Based on the user ID and the thin client terminal information received from the thin client terminal, information related to the restartable client group is searched from the client state management table, the search result is returned to the thin client terminal, and the thin client terminal is returned. A connection destination management unit that identifies an available client based on the information about the selected client group received from the client terminal, and restarts the identified client by the activation control unit;
A connection management server.
JP2006328129A 2006-12-05 2006-12-05 Connection management method and connection management server in thin client Active JP4293234B2 (en)
JP2006328129A JP4293234B2 (en) 2006-12-05 2006-12-05 Connection management method and connection management server in thin client
EP20070122102 EP1950930B1 (en) 2006-12-05 2007-12-03 Connection control in thin client system
CA2613499A CA2613499C (en) 2006-12-05 2007-12-04 Connection control in thin client system
NZ56402107A NZ564021A (en) 2006-12-05 2007-12-04 Connection control in thin client system
TW96146049A TW200826561A (en) 2006-12-05 2007-12-04 Connection control in thin client system
CN200710196477.1A CN101197743B (en) 2006-12-05 2007-12-05 Connection control in thin client system
SG200718326-2A SG143231A1 (en) 2006-12-05 2007-12-05 Connection control in thin client system
US11/950,836 US8364830B2 (en) 2006-12-05 2007-12-05 Connection control in thin client system
AU2007237360A AU2007237360A1 (en) 2006-12-05 2007-12-05 Connection control in thin client system
HK08110627.2A HK1115251A1 (en) 2006-12-05 2008-09-24 Connection control in thin client system
JP2008140306A true JP2008140306A (en) 2008-06-19
JP4293234B2 JP4293234B2 (en) 2009-07-08
ID=39339236
JP2006328129A Active JP4293234B2 (en) 2006-12-05 2006-12-05 Connection management method and connection management server in thin client
US (1) US8364830B2 (en)
EP (1) EP1950930B1 (en)
JP (1) JP4293234B2 (en)
CN (1) CN101197743B (en)
AU (1) AU2007237360A1 (en)
CA (1) CA2613499C (en)
HK (1) HK1115251A1 (en)
NZ (1) NZ564021A (en)
SG (1) SG143231A1 (en)
TW (1) TW200826561A (en)
JP2010182260A (en) * 2009-02-09 2010-08-19 Mitsubishi Electric Corp Thin client system, management server, thin client terminal, and thin client server
WO2011078079A1 (en) * 2009-12-21 2011-06-30 日本電気株式会社 Session management system, session management device, session management method, session management program
JP2011198200A (en) * 2010-03-23 2011-10-06 Nec Corp Service providing system, virtual machine server, method and program for providing service
JP2011198193A (en) * 2010-03-23 2011-10-06 Nec Corp Thin client system and authentication method in thin client system
WO2011148672A1 (en) * 2010-05-24 2011-12-01 株式会社日立製作所 Business computer assignment method and device
EP2418827A1 (en) 2010-08-09 2012-02-15 Nec Corporation Connection management system, and a method for linking connection management server in thin client system
JP2012068718A (en) * 2010-09-21 2012-04-05 Nec Corp Thin client system, management server, client environment management method and program
JP2013131207A (en) * 2012-09-21 2013-07-04 Oyo Denshi:Kk Thin client system
WO2015029176A1 (en) * 2013-08-29 2015-03-05 株式会社日立システムズ Information processing terminal system
JP2015153080A (en) * 2014-02-13 2015-08-24 日本電気株式会社 Virtual machine management system, virtual machine management apparatus, virtual machine management method, and virtual machine management program
JP2015197790A (en) * 2014-04-01 2015-11-09 エヌ・ティ・ティ・コムウェア株式会社 Setting device, setting system, setting method, and setting program
JP2016161960A (en) * 2015-02-26 2016-09-05 日本電気株式会社 Virtual information processing system, and virtual information processing method thereof
CN101667536B (en) * 2001-08-31 2012-07-04 东京毅力科创株式会社 Method for etching an object to be processed
JP4787684B2 (en) * 2006-06-15 2011-10-05 日本電気株式会社 Session management system, session management method, and program
JP4293234B2 (en) 2006-12-05 2009-07-08 日本電気株式会社 Connection management method and connection management server in thin client
CN102137127A (en) * 2010-01-27 2011-07-27 中国工商银行股份有限公司 System and method for remote transmission of files through internet in BS mode
US20140019525A1 (en) * 2011-03-29 2014-01-16 Nec Corporation Virtual desktop system, network processing device, and management method and management program thereof
US20130042312A1 (en) * 2011-08-09 2013-02-14 Mobileframe Llc Authentication in a smart thin client server
EP3211537A1 (en) 2011-10-10 2017-08-30 Hewlett-Packard Development Company, L.P. Establish client-host connection
JP5684170B2 (en) * 2012-02-28 2015-03-11 株式会社東芝 Information processing apparatus, client management system, and client management method
JP6200707B2 (en) * 2013-06-28 2017-09-20 富士通株式会社 Switch and control method
EP3086550A1 (en) * 2013-12-18 2016-10-26 Nec Corporation Camera terminal device, thin client server device, camera system, and control method
CN104753887B (en) * 2013-12-31 2018-02-23 中国移动通信集团黑龙江有限公司 Security management and control implementation method, system and cloud desktop system
US204562A (en) * 1878-06-04 Improvement in feed and water cups for bird-cages
WO1996017306A2 (en) * 1994-11-21 1996-06-06 Oracle Corporation Media server
JPH08263283A (en) 1995-03-24 1996-10-11 Ricoh Co Ltd Software managing system
US6324177B1 (en) * 1997-05-02 2001-11-27 Cisco Technology Method and apparatus for managing connections based on a client IP address
EP1258127B1 (en) * 2000-02-25 2003-09-17 Sun Microsystems, Inc. Method and apparatus for making a computational service highly available
JP2000181821A (en) 1998-12-15 2000-06-30 Toshiba Corp Network computer system
US6961772B1 (en) * 1999-11-30 2005-11-01 Recursion Software, Inc. Transparent connection type binding by address range
WO2001055813A2 (en) * 2000-01-18 2001-08-02 Novell, Inc. System and method for using directory services to facilitate access to applications available on thin client servers
US6912578B1 (en) 2000-02-25 2005-06-28 Sun Microsystems, Inc. Method and apparatus for improving utilization of a resource on a shared client
JP2001282737A (en) 2000-03-28 2001-10-12 Mitsubishi Electric Corp Job load dispersion system
JP4287990B2 (en) 2000-07-07 2009-07-01 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｓｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ Network system, terminal management system, terminal management method, data processing method, recording medium, and Internet service providing method
JP2002111713A (en) 2000-09-28 2002-04-12 Toshiba Corp Network system, name server, server and ip communication method of network system
JP2003085059A (en) 2001-03-16 2003-03-20 Matsushita Electric Ind Co Ltd Firewall setting method and system for the same
JP4170649B2 (en) 2002-04-02 2008-10-22 ヤフー株式会社 Messenger server system, method of providing messenger service, connection destination determination server in messenger service
WO2004006501A1 (en) * 2002-07-03 2004-01-15 British Telecommunications Public Limited Company Trust establishment for multi-party communications
US7478387B2 (en) * 2002-09-25 2009-01-13 International Business Machines Corporation System and method for creating a restartable non-native language routine execution environment
US20040121299A1 (en) * 2002-12-20 2004-06-24 Electronic Data Systems Corporation System and method for remote-access virtual-lab environment
JP2005100344A (en) 2003-08-18 2005-04-14 Ricoh Co Ltd Information processor, session restoration method, session restoration program, and recording medium
JP4028853B2 (en) 2004-03-30 2007-12-26 株式会社日立製作所 Information service communication network system and session management server
JP4290605B2 (en) 2004-05-26 2009-07-08 日本電信電話株式会社 Shared use personal computer system and management method of shared use personal computer system
JP4497463B2 (en) 2004-07-08 2010-07-07 株式会社リコー Screen sharing system and printing apparatus
GB2416879B (en) * 2004-08-07 2007-04-04 Surfcontrol Plc Device resource access filtering system and method
JP4452156B2 (en) 2004-11-08 2010-04-21 日本電信電話株式会社 Shared PC usage method and server
JP4175322B2 (en) 2004-12-06 2008-11-05 トヨタ自動車株式会社 Vehicle
JP4733399B2 (en) * 2005-01-28 2011-07-27 株式会社日立製作所 Computer system, computer, storage device and management terminal
JP2007094610A (en) 2005-09-28 2007-04-12 Hitachi Ltd Computer system
2006-12-05 JP JP2006328129A patent/JP4293234B2/en active Active
2007-12-03 EP EP20070122102 patent/EP1950930B1/en active Active
2007-12-04 CA CA2613499A patent/CA2613499C/en not_active Expired - Fee Related
2007-12-04 NZ NZ56402107A patent/NZ564021A/en not_active IP Right Cessation
2007-12-04 TW TW96146049A patent/TW200826561A/en unknown
2007-12-05 SG SG200718326-2A patent/SG143231A1/en unknown
2007-12-05 CN CN200710196477.1A patent/CN101197743B/en active IP Right Grant
2007-12-05 US US11/950,836 patent/US8364830B2/en active Active
2007-12-05 AU AU2007237360A patent/AU2007237360A1/en not_active Abandoned
2008-09-24 HK HK08110627.2A patent/HK1115251A1/en unknown
JP5365702B2 (en) * 2009-12-21 2013-12-11 日本電気株式会社 Session management system, session management apparatus, session management method, and session management program
US8930532B2 (en) 2009-12-21 2015-01-06 Nec Corporation Session management in a thin client system for effective use of the client environment
JP2011248419A (en) * 2010-05-24 2011-12-08 Hitachi Ltd Business computer allotting method and device
JP2012038152A (en) * 2010-08-09 2012-02-23 Nec Corp Connection management system and connection management server cooperation method in thin client system
US9407703B2 (en) 2010-08-09 2016-08-02 Nec Corporation Connection management system, and a method for linking connection management server in thin client system
US9184996B2 (en) 2010-09-21 2015-11-10 Nec Corporation Thin client system, management server, client environment management method and program
US8364830B2 (en) 2013-01-29
NZ564021A (en) 2008-07-31
AU2007237360A1 (en) 2008-06-19
CN101197743A (en) 2008-06-11
EP1950930A2 (en) 2008-07-30
JP4293234B2 (en) 2009-07-08
HK1115251A1 (en) 2016-08-12
EP1950930B1 (en) 2012-07-18
CA2613499A1 (en) 2008-06-05
CA2613499C (en) 2013-11-05
SG143231A1 (en) 2008-06-27
TW200826561A (en) 2008-06-16
EP1950930A3 (en) 2008-08-13
US20080263217A1 (en) 2008-10-23
CN101197743B (en) 2015-11-25
JP2015164067A (en) 2015-09-10 Provisioning and managing replicated data instances
US9661060B2 (en) 2017-05-23 Method, server and system for converging desktop application and web application
JP2017062840A (en) 2017-03-30 System and method for administering server configuration including gui navigation, property sheets, and auto-tab completion
JP6461167B2 (en) 2019-01-30 System and method for supporting multi-tenancy in an application server, cloud or other environment
US9990220B2 (en) 2018-06-05 Hypervisor remedial action for a virtual machine in response to an error message from the virtual machine
US20160105312A1 (en) 2016-04-14 Cloud-Based Virtual Machines and Offices
US9762440B2 (en) 2017-09-12 State-based provisioning of a client having a windows-based embedded image
US8943606B2 (en) 2015-01-27 Systems and methods for associating a virtual machine with an access control right
US9747125B2 (en) 2017-08-29 Associating virtual machines on a server computer with particular users on an exclusive basis
US9110732B1 (en) 2015-08-18 Proxy for injecting configuration information
KR102060212B1 (en) 2019-12-27 Identity services for organizations transparently hosted in the cloud
US8549066B1 (en) 2013-10-01 Service provider interface for deploying and managing applications on a cloud
US9043391B2 (en) 2015-05-26 Capturing and restoring session state of a machine without using memory images
US9183010B2 (en) 2015-11-10 Comparing and provisioning configurations for a client having a windows-based embedded image
US9037633B2 (en) 2015-05-19 Transferring configuration data from a public cloud server and applying onto a mobile client
US9925465B2 (en) 2018-03-27 Game accessing method and processing method, server, terminal, and system
US7493487B2 (en) 2009-02-17 Portable computing environment
US20140366093A1 (en) 2014-12-11 Apparatus and method for virtual desktop service
JP4923058B2 (en) 2012-04-25 Automated device driver management
US8015331B2 (en) 2011-09-06 Multi-console workstations concurrently supporting multiple users
CN103116477B (en) 2016-08-10 Output distribution system and method, output distributor
US6757821B1 (en) 2004-06-29 Computer system and its operation environment switching method
KR101176651B1 (en) 2012-08-23 Failover scopes for nodes of a computer cluster
2008-10-29 A977 Report on retrieval
2008-11-06 A131 Notification of reasons for refusal
2009-03-11 TRDD Decision of grant or rejection written
2009-03-18 A01 Written decision to grant a patent or to grant a registration (utility model)
2009-04-16 A61 First payment of annual fees (during grant procedure)
2009-04-17 R150 Certificate of patent or registration of utility model
2009-04-17 FPAY Renewal fee payment (event date is renewal date of database)
Free format text: PAYMENT UNTIL: 20120417
Free format text: PAYMENT UNTIL: 20130417
Free format text: PAYMENT UNTIL: 20140417