JP2016212728A - Thin client terminal, thin client system, thin client method, and thin client program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a thin client terminal and the like that automatically switch a mode to be used without requiring peripheral devices such as an input device and an output device, connected with a thin client box in order to realize a thin client function.SOLUTION: A thin client terminal 40 comprises: a connector unit 41 for communicatively connecting between the thin client terminal and an external device; a connection detection unit 42 for detecting whether a communication state is a first communication state of being connected or a second communication state of being unconnected; a first application group management unit 43 for setting a first application group operable on the thin terminal; and a second application group management unit 44 for setting a second application group operable on the thin terminal.SELECTED DRAWING: Figure 18

Description

  The present invention relates to a technology such as a thin client terminal.

  In an information system of a company or the like, there is a form in which each employee installs a lot of high-functional software on a computer at hand and stores data and files. However, this form complicates the operation and management of software and data, and it is necessary to prepare as many high-performance and expensive computers as the number of employees, which increases costs and labor. Therefore, there is a demand for a thin client method in which a computer used by an employee has a minimum function and a server computer centrally manages resources such as software and business data. A low-price client-only computer with a reduced function used in a thin client system is called a thin client terminal.

  A thin client terminal is generally a computer (hereinafter referred to as a “thin client box”) that is connected to a server computer to realize a thin client function. Each employee connects the thin client box to an input device (keyboard, mouse, etc.) and an output device (display, printer, etc.) and connects to a server computer to execute the thin client function (Non-Patent Document 1). reference).

  Patent Document 1 discloses a technique for switching software by a simple operation of an operator when a single information terminal equipped with a thin client function is used for both business and private use.

  Patent Document 2 discloses a technology that allows a user to use an application without being aware of the difference in connection method in a thin client system. In this technology, when an application program is activated, a method using a remode desktop or a method of working locally on a client terminal is determined with reference to a mode management table.

“Thin Client Lineup Guide, Express 5800 Series”, [online], March 2015, NEC, [Search April 20, 2015], Internet <URL: http://jpn.nec.com/express/catalog /thinclient_lineup.pdf>

Japanese Patent Application No. 2014-175808 Japanese Patent Application No. 2009-271576

  However, Non-Patent Document 1 requires a thin client box, an input device, an output device, and the like in order to realize the thin client function. The cost for these devices is high, and further security management for each of these devices is necessary. It was. In Patent Document 1, switching of a mode used by a user is triggered by the user manually performing a switching operation. Therefore, a switching error due to a user's operation error occurs. In Patent Document 2, it is necessary to complete the setting of the mode management table in advance for the determination at the time of starting each application.

  The present invention has been made to solve the above problems. The present invention mainly provides a thin client terminal or the like that automatically switches the mode to be used without requiring peripheral devices such as an input device and an output device connected to the thin client box to realize the thin client function. Objective.

In order to solve the above problems, the first aspect of the present invention is:
A connector part for connecting the own terminal and an external device in a communicable manner;
A connection detection unit for detecting whether the first communication state is connected to an external device via the connector unit or the second communication state is not connected;
A first application group management unit configured to set the first application group to be operable in the own terminal when the connection detection unit detects the first communication state;
When the connection detection unit detects the second communication state, the connection detection unit is a thin client terminal including a second application group management unit that sets the second application group to be operable in the own terminal.

The second aspect of the present invention is:
At least one thin client terminal as described above;
According to the authority associated with the thin client terminal and the communication state detected by the connection detection unit, it is determined whether the client terminal is permitted to use the first application group, the second application group, or the third application group. And a management server.

The third aspect of the present invention is:
Detects whether or not the terminal and the external device are communicably connected,
When detecting connection, instruct to set the first application group,
When the connection cannot be detected, instruct to set the second application group.
Thin client method.

The fourth aspect of the present invention is:
A function for detecting whether or not the terminal and the external device are communicably connected;
A function for instructing to set the first application group when detecting a connection;
A thin client program that causes a computer to execute a function of instructing to set a second application group when connection cannot be detected.

  According to the present invention, it is possible to provide a thin client terminal or the like that automatically switches the mode to be used without requiring peripheral devices such as an input device and an output device connected to the thin client box to realize the thin client function. Can do.

It is a figure which shows the structural example of the thin client terminal and its peripheral device in the 1st Embodiment of this invention. It is a figure which shows the internal structural example of the thin client terminal in 1st Embodiment. It is a flowchart which shows operation | movement of the thin client terminal in 1st Embodiment. It is a figure which shows the example of a screen which the thin client terminal in 1st Embodiment presents. It is a figure which shows the example of a screen which the thin client terminal in 1st Embodiment presents. It is a figure which shows the internal structural example of the thin client terminal in the example 1 of a change of 1st Embodiment. It is a figure which shows the internal structural example of the thin client terminal in the example 2 of a change of 1st Embodiment. It is a figure which shows the structural example of the thin client system in the 2nd Embodiment of this invention. It is a figure which shows the internal structural example of the management server in the thin client system in 2nd Embodiment. It is a figure which shows the data structural example of the management information which the management information storage part in the thin client system in 2nd Embodiment stores. It is a figure which shows the data structural example of the application corresponding table which the application corresponding table memory | storage part in the thin client system in 2nd Embodiment stores. It is a flowchart which shows the operation example of the management server in the thin client system in 2nd Embodiment. It is a figure which shows the structural example of the thin client system in the 3rd Embodiment of this invention. It is a figure which shows the internal structural example of the thin client terminal in the thin client system in 3rd Embodiment. It is a flowchart which shows the operation example of the thin client terminal in the thin client system in 3rd Embodiment. It is a figure which shows the example of a screen which the thin client terminal in the thin client system in 3rd Embodiment presents. It is a figure which shows the structure of CPU and a memory | storage device in the case of comprising 1st-3rd embodiment with software. It is a figure which shows the structural example of the thin client system in the 4th Embodiment of this invention.

  Next, an embodiment of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, the drawings schematically show the configuration of the embodiment of the present invention. Furthermore, the embodiment of the present invention described below is an example, and can be appropriately changed within a range in which the essence is the same.

<First Embodiment>
(Thin client terminal)
A configuration example of the thin client terminal 1 and its peripheral devices according to the first embodiment of the present invention will be described with reference to FIG.

  The thin client terminal 1 according to the first embodiment of the present invention is an apparatus in which a thin client box, an input device, and a display device are integrated, and is, for example, a tablet terminal. As shown in FIG. 1, the thin client terminal 1 can be connected to the cradle 2 via the connector unit 3. The cradle 2 preferably includes a groove that can support or substantially fix one end of the thin client terminal 1 in a state where the thin client terminal 1 is perpendicular or substantially perpendicular to the bottom surface of the cradle 2. The cradle 2 is equipped with a communication interface such as a USB (Universal Serial Bus) terminal, an HDMI (High-Definition Multimedia Interface; registered trademark) terminal, an audio terminal, a TCP / IP (Transmission Control Protocol / Internet Protocol) communication port, and the like. It can be connected to the display device 4, the input device 5, the authentication device 6, the printing device 7, the wired router 9, and the like.

  The connector unit 3 is hardware or software that connects the thin client terminal 1 and the cradle 2 so that they can communicate with each other. The connection method may be either wired or wireless. In the case of wired, for example, the thin client terminal 1 is provided with a concave connector pin receiving portion, and the cradle 2 is provided with a convex connector pin, and both are fitted and connected. Note that charging from the cradle 2 to the thin client terminal 1 may be performed by this method. In the case of wireless, for example, the thin client terminal 1 is supported or substantially fixed to the cradle 2, and both are connected via infrared communication and near field communication (NFC). In FIG. 1, the connector unit 3 is physically sandwiched between the thin client terminal 1 and the cradle 2 and displayed so as to be visible, but this is only an example. For example, when the connector part 3 is wired connection, the connector part 3 may not be visible from the outside in a state where the concave connector pin receiving part and the convex connector pin described above are fitted. . When the connector unit 3 is wirelessly connected, the radio wave transmission / reception unit for infrared communication or short-range wireless communication described above is generally mounted inside the thin client terminal 1 and the cradle 2, so that the connector unit 3 is externally connected. It may be impossible to see.

  The fixed display device 4 is a plasma display, a liquid crystal display, or the like having a shape intended to be constantly placed on a desk or the like. The fixed display device 4 preferably has a display screen larger than the display screen of the thin client terminal 1 so that the user can easily see it.

  The input device 5 is a keyboard, a mouse, or the like. The authentication device 6 is a device for authenticating a card IC (integrated circuit), biometric information (fingerprint, retina, voiceprint, etc.) and the like. The printing device 7 is a printer or the like.

  The wired router 9 is a relay device for connecting the thin client terminal 1 to a network 10 constituted by a LAN or WAN by a wired cable.

  When the thin client terminal 1 is away from the cradle 2, the thin client terminal 1 is wirelessly connected to the network 10 via the wireless base station 8. Here, wireless communication refers to, for example, Wi-Fi (Wireless Fidelity; registered trademark; hereinafter, registered trademark is omitted) communication.

  Note that selection of wired or wireless communication is not limited to this, and wireless communication may be performed when connected to the cradle 2 or wired when not connected to the cradle 2 according to the user's setting. Communication may be performed.

  An example of the internal configuration of the thin client terminal 1 according to the first embodiment of the present invention will be described with reference to FIG. The thin client terminal 1 includes an input / output unit 11, an input / output interface unit 12, a connector unit 3, a wireless communication unit 13, a storage unit 14, a central control device (hereinafter referred to as “CPU”) 15, and a first application group storage unit. 16 and a second application group storage unit 17.

  The first application group storage unit 16 includes at least one application (hereinafter referred to as “first application”) that can be used when the thin client terminal 1 is connected to the cradle 2 via the connector unit 3. Application group ”). When connected to the cradle 2, the user holding the thin client terminal 1 is likely to be present at a specific position (for example, near the user's desk), and the thin client terminal 1 may be connected by wire. high. Therefore, the first application group includes installation, update, execution, deletion, and the like of application programs necessary for executing the thin client function. For example, installation and update of thin client function execution software, download of confidential documents, and the like.

  The second application group storage unit 17 includes at least one application (hereinafter referred to as “second application group”) that can be used when the thin client terminal 1 is not connected to the cradle 2. ). When not connected to the cradle 2, the user holding the thin client terminal 1 is likely to be in an unspecified position, and the thin client terminal 1 is highly likely to be wirelessly connected. Therefore, the second application group includes execution and deletion of application programs that are not necessarily required to execute the thin client function. For example, an application for browsing materials necessary for a meeting, a mailer, a personal scheduler, and the like.

  Note that the first application group and the second application group may include the same application. For example, it is preferable that an application with high use frequency such as a mailer or a personal scheduler can be used regardless of the connection state between the thin client terminal 1 and the cradle 2, that is, included in both application groups.

  The CPU 15 includes a connection detection unit 15a, a first application group management unit 15b, a second application group management unit 15c, a wireless communication control unit 15d, and a wired communication control unit 15e.

  The connection detection unit 15a detects whether or not the thin client terminal 1 and the cradle 2 are communicatively connected in the connector unit 3.

  The first application group management unit 15 b manages the first application group stored in the first application group storage unit 16.

  The second application group management unit 15 c manages the second application group stored in the second application group storage unit 17.

  The radio communication control unit 15 d controls communication between the radio base station 8 and the radio communication unit 13.

  The wired communication control unit 15 e controls communication between the cradle 2 and the wired router 9.

  The input / output unit 11 is an input / output screen for the thin client terminal 1 (tablet terminal) (see FIG. 1). On the input / output screen, input by tapping and swiping at the software keyboard or icon position, output of characters and images, and the like are performed.

  The input / output interface unit 12 indicates a terminal, a port, and the like for the thin client terminal 1 to directly transmit / receive data to / from an external device.

  The wireless communication unit 13 performs Wi-fi communication with the wireless base station 8.

  The storage unit 14 is a memory necessary for the CPU 15 to perform arithmetic processing, for example, a RAM (Random Access Memory), a ROM (Read Only Memory), or the like.

  As shown in FIG. 2, each unit 15a to 15e in the CPU 15 can be realized by hardware such as an electronic circuit, but can also be realized as software. In this case, each unit 15a to 15e can be regarded as a function (processing) unit of the software program, in other words, a software module. In this case, each part 15a-15e in CPU15 is written in ROM, and is loaded into CPU15 in the case of arithmetic processing. For example, as shown in FIG. 17 (FIG. 17 is a diagram showing the changed part of the storage unit 14 and CPU 15 in FIG. 2), the software program group is stored in the ROM in the storage unit 1000 (14), It is loaded into the CPU 1001 (15) during the arithmetic processing.

(Operation of thin client terminal)
The operation of the thin client terminal 1 will be described with reference to the flowchart of FIG.

  First, in step S101, when the thin client terminal 1 is powered on (is turned on), in step S102, the connection detection unit 15a in FIG. It is determined whether or not a connection is detected. The detection of the connection may be performed at a timing when both of them are connected (connected) from the non-connected state or when they are disconnected (disconnected) from the connected state. When the connection is detected, the connection detection unit 15a transmits a notification with detection to the first application management unit 15b, and then the process proceeds to step S103. When the connection is not detected, the connection detection unit 15a transmits a notification of no detection to the second application group management unit 15c, and then the process proceeds to step S105.

  In step S103, the first application group management unit 15b that has received the notification presents an icon indicating the first application group to the input / output unit 11 as shown in FIG. In step S104, when it is detected by a tap or the like on the input / output unit 11 that the presented icon has been selected by the user, the first application group management unit 15b selects the selected application as the first application group storage unit. 16 is activated to make it usable by the user. Thereafter, when detecting a tap or the like for notifying the end of use from the user, the first application group management unit 15b terminates the application.

  In step S105, the second application group management unit 15c that has received the notification presents an icon indicating the second application group to the input / output unit 11 as shown in FIG. In step S106, when it is detected by a tap or the like on the input / output unit 11 that the presented icon has been selected by the user, the second application group management unit 15c selects the selected application as the second application group storage unit. 17 is activated to make it usable by the user. Thereafter, when detecting a tap or the like for notifying the end of use from the user, the second application group management unit 15c terminates the application.

  Finally, in step S107, it is determined whether or not the user has selected to turn off the power of the thin client terminal 1 (the power is turned off). If it is determined not to turn off the power, the process returns to step S102. It is. If it is determined that the power is to be turned off, this process is terminated.

  According to the first embodiment of the present invention, the connection detection unit 15a detects whether or not the thin client terminal 1 and the cradle 2 are communicatively connected in the connector unit 3 and is connected to the case where they are connected. The type of application that can be used by the user is determined when there is not. Thereby, the thin client terminal 1 can automatically switch the mode to be used. Note that a tablet terminal is used as the thin client terminal 1. This eliminates the need for a thin client box and peripheral devices such as an input device and an output device connected to the thin client box for realizing the thin client function.

(Modification 1 of the first embodiment)
Modification 2 of the first embodiment will be described with reference to FIG. The thin client terminal 1a according to the first modification of the first embodiment includes an input / output unit 11, an input / output interface unit 12, a connector unit 3, a wireless communication unit 13, a storage unit 14, a CPU 15A, and a first application group storage unit. 16, a second application group storage unit 17 and a portal screen application storage unit 18 are provided. The CPU 15A includes a connection detection unit 15a, a first application group management unit 15b, a second application group management unit 15c, a wireless communication control unit 15d, a wired communication control unit 15e, and a display switching unit 15f. The components other than the portal screen application storage unit 18 and the display switching unit 15f are the same as those in the first embodiment, and a description thereof will be omitted.

  The portal screen application storage unit 18 stores frequently used applications. On the portal screen of the thin client terminal 1a, an activation icon of the frequently used application is presented. Examples of frequently used applications include a calendar, a clock, and a scheduler.

  The display switching unit 15f switches the screen displayed on the input / output unit (output screen) 11 of the thin client terminal 1a to the application stored in the portal screen application storage unit 18 based on the user setting. Switching can be executed only when the thin client terminal 1a and the cradle 2 are connected. Generally, when the thin client terminal 1a and the cradle 2 are connected, the screen displayed on the thin client terminal 1a and the screen displayed on the fixed display device 4 are set to be the same. . This is because the thin client terminal 1 a and the fixed display device 4 are HDMI-connected via the cradle 2. However, it is redundant that the same screen is displayed on the thin client terminal 1a and a display (fixed display device 4) larger than the terminal 1a, and the user often pays attention to the large display. . Therefore, the display switching unit 15f switches the screen displayed on the input / output unit (output screen) 11 of the thin client terminal 1a to the portal screen application desired by the user.

  According to the second modification of the first embodiment, the user can freely use the information displayed on the large and small screens by switching the application displayed on the thin client terminal 1a by the display switching unit 15f.

(Modification 2 of the first embodiment)
Modification 2 of the first embodiment will be described with reference to FIG. The thin client terminal 1b according to the second modification of the first embodiment includes an input / output unit 11, an input / output interface unit 12, a connector unit 3, a wireless communication unit 13, a storage unit 14, a CPU 15B, and a first application group storage unit. 16, a second application group storage unit 17 and an authority storage unit 19 are provided. The CPU 15B includes a connection detection unit 15a, a first application group management unit 15b, a second application group management unit 15c, a wireless communication control unit 15d, a wired communication control unit 15e, and an authority setting unit 15g. The components other than the authority storage unit 19 and the authority setting unit 15g are the same as those in the first embodiment, and a description thereof will be omitted.

  The authority storage unit 19 stores the authority associated with each user. For example, the A user is set to “general user”, and the B user is set to “administrator”. Specifically, for example, in the case of a company, the A user is divided into “employee”, the B user is divided into “system administrator”, the C user is divided into “managerial employee”, and the like.

  The authority setting unit 15g causes the authority storage unit 19 to store the authority associated with each user. Further, an application usable by the user is set according to the authority stored in the authority storage unit 19. For example, an application that can be used by a general user is a part of the entire application, but the administrator can use all the applications. It should be noted that settings may be made so that a predetermined application cannot be downloaded or updated unless it is an administrator.

  According to the second modification of the first embodiment, the authority setting unit 15g sets the authority for each user, and by dividing the applications that can be used according to the authority, the security level as a thin client function can be increased. it can.

<Second Embodiment>
(Thin client system)
A thin client system 100 according to a second embodiment of the present invention will be described with reference to FIG. The thin client system 100 includes the management server 20 and a plurality of thin client terminals 1 described in the first embodiment (hereinafter referred to as “thin client terminals 1a to 1i”). The thin client terminals 1a to 1i are divided into a plurality of groups according to, for example, each region or each workplace. In FIG. 8, the thin client terminals 1a to 1c belong to the A group, the thin client terminals 1d to 1f belong to the B group, and the thin client terminals 1g to 1i belong to the C group. The thin client terminals 1a to 1i include corresponding cradle 2a to 2i.

  The management server 20 manages master data of the thin client terminals 1a to 1i and applications used by these terminals 1a to 1i.

  As shown in FIG. 9, the management server 20 includes an input unit 21, an output unit 22, a communication interface unit 23, a storage unit 24, a CPU 25, a management information storage unit 26, an application storage unit 27, and an application correspondence table storage unit 28. ing.

  The management information storage unit 26 stores management information 26a. The data structure of the management information 26a is shown in FIG. The management information 26a includes “user ID”, “terminal ID”, “affiliation group”, “authority”, “first application group information”, and “second application group information” as data items. The user ID is an ID that can uniquely identify a user who uses the thin client terminals 1a to 1i. The terminal ID is an ID that can uniquely identify the thin client terminal 1a to 1i. The belonging group indicates a group to which the user belongs. The authority indicates the authority of the user (general user, administrator, etc.). The first application group information indicates an application group that can be used when the thin client terminals 1a to 1i are connected to the cradle 2a to 2i. The second application group information indicates an application group that can be used when the thin client terminals 1a to 1i are not connected to the cradle 2a to 2i.

  The application storage unit 27 stores a first application group and a second application group.

  The application correspondence table storage unit 28 is a table (hereinafter referred to as “application correspondence table 28a”) indicating applications that can be used by the user for each user, for each user group, for each authority, or for each combination thereof; Reference) is memorized.

  The CPU 25 includes a thin client terminal information management unit 25a, an application determination unit 25b, and an application setting unit 25c.

  The thin client terminal information management unit 25a manages the management information 26a stored in the management information storage unit 26, for example, creates, updates, and deletes the management information 26a.

  The application determination unit 25b determines each user based on the group to which the user belongs, authority, or a combination thereof included in the management information 26a, and the application correspondence table (see FIG. 11) stored in the application correspondence table storage unit 28. Determine the applications that can be used.

  The application setting unit 25c sets an application that can be used by each user determined by the application determination unit 25b so that the thin client terminals 1a to 1i corresponding to the thin client terminal ID associated with the user ID can be used.

  The input unit 21 is a keyboard, a mouse, or the like. The output unit 22 is a monitor, a printer, or the like. The communication interface unit 23 is an interface for performing communication between the management server 20 and external devices (thin client terminals 1a to 1i). The storage unit 24 is a memory necessary for the CPU 25 to perform arithmetic processing, such as a RAM and a ROM. Each unit 25a to 25c in the CPU 25 can be realized by hardware such as an electronic circuit, but can also be realized as software. In this case, each unit 25a to 25c can be regarded as a function (processing) unit of the software program, in other words, a software module. In this case, each part 25a-25c in CPU25 is written in ROM, and is loaded in CPU15 in the case of arithmetic processing. For example, as shown in FIG. 17, a software program group is stored in the ROM in the storage unit 1000 (24), and is loaded into the CPU 1001 (25) during arithmetic processing.

(Thin client system operation)
The operation of the thin client system 100 will be described with reference to the flowchart of FIG. The management information 26a (see FIG. 10) in the management information storage unit 26, the application group in the application storage unit 27, and the application correspondence table 28a (see FIG. 11) in the application correspondence table storage unit 28 are registered in advance. It shall be.

  First, in step S201, the management server 20 receives a notification requesting permission to use an application from the thin client terminals 1a to 1i. This notification includes at least one of a terminal ID that identifies the thin client terminals 1a to 1i or a user ID (ID that identifies a user who uses the terminal) associated with the terminal ID. The notification further includes whether the thin client terminals 1a to 1i, which are notification sources, are currently connected to the cradle 2 (communication connection via the wired router 9) or not connected to the cradle 2 (wirelessly) Information that can determine the communication state of the communication connection via the base station 8).

  In step S202, the thin client terminal information management unit 25a uses the management information 26a (see FIG. 10) in the management information storage unit 26 based on at least one of the terminal ID or the user ID included in the notification. Search for group and authority.

  In step S <b> 203, the application determination unit 25 b determines the application correspondence table in the application correspondence table storage unit 28 on the basis of the information that can be used to determine the group, authority, or combination of the retrieved user and the communication state. The first or second application information that can be used by the user is searched from 28a (see FIG. 11). Next, the application determination unit 25b determines whether the searched first or second application group includes an application that the user included in the received notification requests permission to use. If the application is included in the searched application group, the process proceeds to step S204. If the searched application group does not include the application, the process proceeds to step S205.

  For example, a case will be described where the thin client terminal 1a transmits a notification indicating that the application D is to be used in a communication state connected to the cradle 2a. In this case, the application determination unit 25b, based on the management information 26a (see FIG. 10), the terminal ID of the thin client terminal 1a that is the transmission source of the notification is “1a”, the belonging group is “A”, and the authority is “ It is determined that the user is a “general user”. Next, since the thin client terminal 1a is in a communication state connected to the cradle 2a, the application determination unit 25b acquires first application group information in the application correspondence table 28a (see FIG. 11). The application determination unit 25b determines whether the acquired first application group information includes the application D for which the user requests use permission.

  In step S204, the application setting unit 25c sets the notification source client terminals 1a to 1i to be able to use the application requested to be used. In addition, an installation destination link or the like may be sent to the notification source client terminals 1a to 1i to prompt the setting of the application.

  In step S205, the application setting unit 25c replies to the notification source client terminals 1a to 1i that the application that has requested use permission cannot be used.

  According to the second embodiment of the present invention, the management server 20 performs master data management, and only the application corresponding to the group to which the user belongs and the authority can be used. Thereby, a security policy can be enforced thoroughly. Furthermore, since the thin client system is configured only by the management server 20 and the client terminals 1a to 1i, a sync box and its peripheral devices are not required. This makes it possible to halve the cost, management man-hour, and security risk (key number and key management man-hour) required for each client terminal as compared to using a sinker box or the like. As a result, it is possible to provide a thin client system in which the thin client terminal can be easily carried and the security is not high but the security is strong.

<Third Embodiment>
(Thin client system)
A system configuration of a thin client system 200 according to the third embodiment of the present invention will be described with reference to FIG. The thin client system 200 includes a management server 20a and a thin client terminal 1j. In FIG. 13, only one thin client terminal 1j is displayed, but a plurality of thin client terminals 1j may exist. The basic configuration of the thin client terminal 1j is the same as that of the thin client terminal 1 of the first embodiment, and the configurations of the peripheral devices 2 to 9 are also the same as those of the first embodiment.

  In the thin client system 200, the thin client terminal 1j can take one of the first communication state, the second communication state, and the third communication state.

  The first communication state is a state in which the thin client terminal 1j and the cradle 2 are connected and communicating in a specific site (area) such as a company site. This is a state in which communication is performed with the management server 20a through a wired connection via the wired router 9 or a short-range wireless communication connection.

  The second communication state is a state in which the thin client terminal 1j and the cradle 2 are not connected to the management server 20a in a specific site such as a company site. This is a state in which communication is performed with the management server 20a via a wireless LAN connection such as Wi-Fi communication via the wireless base station 8 in the site.

  The third communication state is a state in which the thin client terminal 1j is communicating with the management server 20a via a wireless base station outside the specific site outside the specific site. This is, for example, a state in which communication is performed with the management server 20a via a tethering function of another wireless communication device, a public wireless LAN service, or the like.

  Next, an internal configuration example of the thin client terminal 1j used in the thin client system according to the third embodiment of the present invention will be described with reference to FIG. The thin client terminal 1j includes an input / output unit 11, an input / output interface unit 12, a connector unit 3, a wireless communication unit 13, a storage unit 14, a CPU 15C, a first application group storage unit 16, a second application group storage unit 17, and A third application group storage unit 31 is provided. The CPU 15C includes a connection detection unit 15j, a first application group management unit 15b, a second application group management unit 15c, a wireless communication control unit 15d, a wired communication control unit 15e, an off-site communication control unit 15h, and a third application group. A management unit 15i is provided. Since the third application group storage unit 31, the connection detection unit 15j, the off-site communication control unit 15h, and the third application group management unit 15i are the same as those in the first embodiment, description thereof is omitted.

  The third application group storage unit 31 includes at least one or more applications that can be used when the thin client terminal 1j is not connected to the cradle 2 and is outside a specific site ( Hereinafter, it is described as “third application group”). If it exists outside a specific site, the user holding the thin client terminal 1j may be present in a place where there is a danger such as radio eavesdropping, such as a city, a station, etc. Therefore, the third application group is not necessarily required to execute the thin client function, and execution, deletion, etc. of application programs that are unlikely to cause a security problem even if radio wave eavesdropping or the like is performed. Is included. For example, a clock application, a personal scheduler, or the like.

  Note that the third application group and the first and second application groups may include the same application. For example, it is preferable that an application with high use frequency such as a clock application or a personal scheduler can be used regardless of whether it is inside or outside the site, that is, included in all application groups.

  The connection detection unit 15j detects whether the thin client terminal 1j and the cradle 2 are connected for communication within the site (whether the communication state is the first communication state or the second communication state). The connection detector 15j further determines that the thin client terminal 1j is communicating in the third communication state when neither of the first communication state and the second communication state is applied.

  The third application group management unit 15 i manages the third application group stored in the third application group storage unit 31.

  The off-site communication control unit 15h controls communication between the thin client terminal 1j and the management server 20a in the third communication state.

(Thin client system operation)
The operation of the thin client system according to the third embodiment will be described with reference to the flowchart of FIG. 15 focusing on the operation of the thin client terminal 1j.

  First, in step S301, when the thin client terminal 1j is turned on (turned on), in step S302, the connection detection unit 15j is connected between the thin client terminal 1j and the cradle 2 in the connector unit 3. Determine whether a connection is detected. When the connection is detected, the connection detection unit 15j transmits a notification indicating that there is a detection, that is, the first communication state, to the first application management unit 15b, and then the process proceeds to step S303. If a connection is not detected, the process proceeds to step S305.

  In step S303, the first application group management unit 15b that has received the notification presents an icon indicating the first application group to the input / output unit 11 as shown in FIG. In step S304, when it is detected by a tap or the like on the input / output unit 11 that the presented icon has been selected by the user, the first application group management unit 15b displays the selected application as the first application group storage unit. 16 is activated to make it usable by the user. Thereafter, when detecting a tap or the like for notifying the end of use from the user, the first application group management unit 15b terminates the application.

  In step S305, the connection detection unit 15j determines whether or not a connection is detected between the thin client terminal 1j and the radio base station 8 in the radio base station 8. This determination is realized by making an inquiry to the wireless communication control unit 15d. When the connection is detected, that is, in the second communication state, the connection detection unit 15j transmits a notification with detection to the second application group management unit 15c, and then the process proceeds to step S306. If no connection is detected, the process proceeds to step S308.

  In step S306, the second application group management unit 15c that has received the notification presents an icon indicating the second application group to the input / output unit 11 as shown in FIG. In step S307, when it is detected by a tap or the like on the input / output unit 11 that the presented icon has been selected by the user, the second application group management unit 15c displays the selected application as the second application group storage unit. 17 is activated to make it usable by the user. Thereafter, when detecting a tap or the like for notifying the end of use from the user, the second application group management unit 15c terminates the application.

  In step S308, when the connection detection unit 15j confirms that it is neither the first communication state nor the second communication state, the thin client terminal 1j determines that it is in the third communication state. The connection detection unit 15j notifies the third application group management unit 15i to present the third application group. Upon receiving this notification, the third application group management unit 15 i presents an icon indicating the third application group to the input / output unit 11.

  In step S309, when it is detected by a tap or the like on the input / output unit 11 that the presented icon has been selected by the user, the third application group management unit 15i displays the selected application as a third application group storage unit. It starts from 31 and makes it usable for the user. At this time, the login screen shown in FIG. 16 may be presented to the input / output unit 11 so that the third application group can be used only when the login ID and the password match. Thereafter, when detecting a tap or the like that notifies the user of the end of use, the third application group management unit 15i ends the application.

  Finally, in step S310, it is determined whether or not the user has selected to turn off the power of the thin client terminal 1j (the power is turned off). If it is determined that the power is not to be turned off, the process returns to step S302. It is. If it is determined that the power is to be turned off, this process is terminated.

  According to the third embodiment of the present invention, the connection detection unit 15j determines which of the first to third communication states the thin client terminal 1j is in, and based on this determination, the application that can be used by the user Determine the type. Thereby, the thin client terminal 1j can automatically switch the mode to be used. Furthermore, it is possible to provide a thin client system in which the thin client terminal 1j can be easily carried, the cost can be kept low, and the security is strong.

<Fourth Embodiment>
(Thin client terminal)
A configuration example of the thin client terminal 40 according to the fourth embodiment of the present invention will be described with reference to FIG. The thin client terminal 40 includes a connector unit 41, a connection detection unit 42, a first application group management unit 43, and a second application group management unit 44.

  The connector part 41 connects the own terminal and an external device so that communication is possible.

  The connection detection unit 42 detects whether the first communication state is connected to the external device via the connector unit or the second communication state is not connected.

  When the connection detection unit 42 detects the first communication state, the first application group management unit 43 sets the first application group to be operable in its own terminal.

  When the connection detection unit 42 detects the second communication state, the second application group management unit 44 sets the second application group to be operable in its own terminal.

  According to the fourth embodiment of the present invention, a thin client terminal that automatically switches the mode to be used without requiring peripheral devices such as an input device and an output device connected to the thin client box to realize the thin client function. Can be realized.

1: Thin client terminal 1a: Thin client terminal 1b: Thin client terminal 1c: Thin client terminal 1d: Thin client terminal 1e: Thin client terminal 1f: Thin client terminal 1g: Thin client terminal 1h: Thin client terminal 1i: Thin client terminal 1j: Thin client terminal 2: Cradle 2a: Cradle 2b: Cradle 2c: Cradle 2d: Cradle 2e: Cradle 2f: Cradle 2g: Cradle 2h: Cradle 2i: Cradle 3: Connector section 4: Fixed display device 5: Input device 6: Authentication device 7: Printing device 8: Wireless base station 9: Wired router 10: Network 11: Input / output unit 12: Input / output interface unit 13: Wireless communication unit 14: Storage unit 15: CPU
15A: CPU
15B: CPU
15C: CPU
15a: connection detection unit 15b: first application group management unit 15c: second application group management unit 15d: wireless communication control unit 15e: wired communication control unit 15f: display switching unit 15g: authority setting unit 15h: off-site communication Control unit 15i: third application group management unit 15j: connection detection unit 16: first application group storage unit 17: second application group storage unit 18: portal screen application storage unit 19: authority storage unit 20: management Server 20a: Management server 21: Input unit 22: Output unit 23: Communication interface unit 24: Storage unit 25: CPU
25a: Thin client terminal information management unit 25b: Application determination unit 25c: Application setting unit 26: Management information storage unit 26a: Management information 27: Application storage unit 28: Application correspondence table storage unit 28a: Application correspondence table 31: Third Application group storage unit 40: Thin client terminal 41: Connector unit 42: Connection detection unit 43: First application group management unit 44: Second application group management unit 100: Thin client system 200: Thin client system 1000: Storage unit 1001: CPU

Claims (9)

Connector means for communicably connecting between the terminal and the external device;
A connection detecting means for detecting whether the first communication state is connected to the external device via the connector means or the second communication state is not connected;
A first application group managing means for setting the first application group to be operable in the terminal when the connection detecting means detects the first communication state;
A thin client terminal comprising: a second application group management unit configured to set the second application group to be operable in the terminal when the connection detection unit detects the second communication state. The time when the connection detection unit detects the first communication state includes the timing when the connection state is changed from the non-connection state, and the case where the second communication state is detected means that the connection state is not detected from the connection state. Including the timing of connection status,
The thin client terminal according to claim 1. The external device is a cradle, and the cradle is
Comprising at least one input / output interface for connecting the terminal and a peripheral device;
One end of the terminal can be supported or substantially fixed in a state perpendicular or substantially perpendicular to the floor surface of the cradle.
The thin client terminal according to claim 1. The peripheral device includes a display device having a display screen larger than the display screen of the own terminal,
When the self-terminal and the cradle are connected so as to be communicable via the connector means, the same image is displayed on the display screen of the self-terminal and the display screen of the display device, or different images are displayed. Display switching means for switching whether to display,
The thin client terminal according to claim 1, further comprising: Authority setting means for setting authority to use software including the first application group and the second application group;
The thin client terminal according to claim 1, further comprising: A third application group management means for setting the third application group to be operable in the terminal;
The connection detecting means includes
Detecting the first communication state and the second communication state in a specific area where communication with a specific network is possible,
If the first communication state and the second communication state are undetectable, the terminal determines that it is in a third communication state outside the specific area, and notifies the third application group management unit Instruct to set the third application group,
The thin client terminal according to claim 1. At least one thin client terminal according to any one of claims 1 to 6;
Depending on the authority associated with the thin client terminal and the communication state detected by the connection detecting means, any one of the first application group, the second application group, and the third application group is included in the thin client terminal. A thin client system comprising: a management server that determines whether to permit use of the client. Detects whether or not the terminal and the external device are communicably connected,
When detecting the connection, instruct to set the first application group,
Instructing to set the second application group when the connection cannot be detected;
Thin client method. A function for detecting whether or not the terminal and the external device are communicably connected;
A function of instructing to set the first application group when detecting the connection;
A thin client program for causing a computer to execute a function of instructing to set a second application group when the connection cannot be detected.

Images