Thin client system using session managing server and session managing method

• US 8,316,133 B2
• Filed: 06/15/2007
• Issued: 11/20/2012
• Est. Priority Date: 06/15/2006
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Koshiba, Kunihiro
• Primary Examiner(s): ZHANG, SHIRLEY X
• Application Number:
  US11/763,745
• Publication Number:
  US 20070294414A1
• Time in Patent Office: 1,985 Days
• Field of Search: 709201-203, 709227-229, 718/1
• US Class Current: 709/227
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A thin client system includes a thin client server, a thin client terminal, and a session management server. The thin client server contains a plurality of execution sections respectively provided for tasks. The session management server is configured to assign the thin client terminal to a specific one of the plurality of execution sections.

Claims

1. A thin client system comprising:

a thin client server comprising a plurality of execution sections respectively provided for tasks,

a thin client terminal having internal storage; and

a session management server assigning said thin client terminal to a specific one of said plurality of execution sections, said session management server comprising;

a connection destination setting table storing an execution section data comprising, for each of said plurality of execution sections, a user data indicating a user of said thin client terminal and a terminal data having identification data identifying said thin client terminal;

a session management section selecting, at the start of use of the thin client terminal, from said connection destination setting table said execution section data corresponding to said specific execution section based on said user data and said terminal data sent from said thin client terminal, and connecting said thin client terminal with said specific execution section of said thin client server based on said selected execution section data as a connection destination;

said thin client terminal comprising;

a protocol management section receiving said execution section data, and establishing a connection with said thin client server through said session management server, by using a protocol and the received execution section data; and

a connection destination control section acquiring said execution section data in response to transmission of said user data and said terminal data, and notifying said execution section data of said protocol management section,

wherein said thin client terminal establishes the connection between said thin client terminal and said thin client server through said session management server, and

said session management section acquires said execution section data in response to reception of said user data and said terminal data from said thin client terminal, when the connection is disconnected, acquires a status of said specific execution section, and carries out reconnection of said thin client terminal when the status of said specific execution section indicates that said specific execution section is normal.

2. The thin client system according to claim 1, wherein each of said plurality of execution sections comprises:

an operating system;

an application program provided for a corresponding task, and executed on said operating system; and

a data used by said application program.

3. The thin client system according to claim 1, wherein said thin client server further comprises:

a client status acquiring section provided for each of said plurality of execution sections to hold a status of said execution section.

4. The thin client system according to claim 1, wherein said thin client terminal has a secret key peculiar to said thin client terminal, and

said connection destination setting table stores a public key corresponding to said secret key as said terminal data.

5. The thin client system according to claim 1, wherein said session management server further comprises:

a connection state management table,

said session management section stores said execution section data, said user data, and said terminal data in said connection state management table when said thin client is connected with said specific execution section.

6. The thin client system according to claim 1, wherein said session management section restarts said specific execution section when the status of said specific execution section indicates that said specific execution section is abnormal.

7. A session management server in a thin client system having a thin client terminal, comprising:

a connection destination setting table storing, in internal storage of the session management server, an execution section data indicating each of a plurality of execution sections provided for tasks for a user data indicating a user of said thin client terminal and a terminal data having identification data identifying said thin client terminal; and

a session management section searching said connection destination setting table for said execution section data corresponding to said specific execution section based on said user data and said terminal data sent from said thin client terminal, selecting, at the start of use of the thin client terminal, the corresponding specific execution section data, connecting said thin client terminal with said specific execution section of said thin client server based on said searched execution section data as a connection destination, and when the connection is disconnected, acquiring a status of said specific execution section and carrying out reconnection of said thin client terminal when the status of said specific execution section indicates that said specific execution section is normal.

8. The session management server according to claim 7, wherein said thin client terminal has a secret key peculiar to said thin client terminal, and said connection destination setting table stores a public key corresponding to said secret key as said terminal data.

9. The session management server according to claim 7, further comprising:

a connection state management table,

wherein said session management section stores said execution section data, said user data, and said terminal data in said connection state management table when said thin client is connected with a specific execution section.

10. A session management method in a thin client system, comprising:

assigning a thin client terminal to a specific one of a plurality of execution sections respectively provided for tasks in a thin client server;

connecting said thin client terminal and said thin client server through a session management server;

managing a status of the connection between said thin client terminal and said thin client server in said session management server;

preparing a connection destination setting table, wherein said connection destination setting table stores an execution section data indicating each of said plurality of execution sections for a user data indicating a user of said thin client terminal and a terminal data having identification data identifying said thin client terminal; and

searching, at the start of use of the thin client terminal, said connection destination setting table for said specific execution section based on said user data and said terminal data, connecting the thin client terminal with said specific execution section of the thin client server based on said searched execution section data as a connection destination, and when the connection is disconnected, acquiring a status of said specific execution section and carrying out reconnection of the thin client terminal when the status of said specific execution section indicates that said specific execution section is normal.

11. The session management method according to claim 10, further comprising:

reconnecting when said thin client terminal and said thin client server when said status of the connection between said thin client terminal and said thin client server indicates that the connection is disconnected but is in a use state.

12. The session management method according to claim 11, further comprising:

receiving an execution section data for a task;

acquiring said execution section data in response to transmission of a user data and a terminal data; and

notifying said execution section data of said protocol management section.

13. A non-transitory computer readable storage medium having computer-readable software product for achieving a method which comprises:

preparing a connection destination setting table, wherein said connection destination setting table stores an execution section data indicating each of a plurality of execution sections provided for tasks in a thin client server, for a user data indicating a user of a thin client terminal and a terminal data having identification data identifying said thin client terminal;

searching, at the start of use of the thin client terminal, said connection destination setting table for a specific one of said plurality of execution sections based on said user data and said terminal data;

connecting the thin client terminal with said specific execution section of the thin client server based on said searched execution section data as a connection destination, and when the connection is disconnected, acquiring a status of said specific execution section and carrying out reconnection of the thin client terminal when the status of said specific execution section indicates that said specific execution section is normal.

14. The computer-readable software product according to claim 13, wherein said method further comprises:

receiving and holding said execution section data, said user data and said terminal data.

15. The computer-readable software product according to claim 14, wherein said method further comprises:

restarting said specific execution section when a failure has occurred in said specific execution section.