JP2010224761A - Thin client system, server device, and update method and program therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To control update of a server terminal and a client terminal, and to eliminate a difference between the versions of the terminals. <P>SOLUTION: The thin client system is equipped with one or more client devices and a server device connected through a network to the client device. The server device transmits, when communication speed with the client device is equal to or more than a threshold, an update module to the client device. The client device receives the update module, and performs the update. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a thin client system, a server device, and an update method and program for controlling update of a server terminal and a client terminal.

  As a method for updating the version of the PC terminal, there is a method in which the update module distribution server is periodically accessed and if there is a latest version, it is automatically updated.

  For example, Patent Document 1 discloses a technique for improving user convenience and ensuring security by shifting to an update mode during update processing of a thin client terminal and enabling automatic logon when in the update mode. It is disclosed.

JP 2008-262454 A

  However, between each thin client system in which a server terminal and a plurality of client terminals are connected via a network, if each updates itself, the software version of each terminal will be different, and communication between the software will not be possible. Problems such as inability to establish will occur.

  In addition, when the client terminal is used outside the office, it may be used in a wireless environment with a low communication speed. At that time, if the version is different from the server terminal, software communication with the server terminal cannot be established without downloading the update module. However, if you try to download in a wireless environment, the communication speed will be slow, Will be unstable and will spend a lot of time.

  Therefore, the present invention has been made in view of the above problems, and an object of the present invention is to control update between a server terminal and a client terminal and eliminate a version difference between both terminals.

  In order to solve the above problems, a thin client system according to the present invention comprises one or more client devices and a server device connected to the client devices via a network. The server device transmits an update module to the client device if the communication speed with the client device is equal to or higher than a threshold, and the client device receives the update module and performs an update.

  The server device according to the present invention is characterized in that if the communication speed with a client device connected via a network is equal to or higher than a threshold, an update module is transmitted to the client device to perform an update.

  In addition, the thin client system update method of the present invention transmits an update module to the client device if the communication speed with the client device connected via the network is equal to or greater than a threshold by the server device, The update module is received and updated.

  The server device update method according to the present invention is characterized in that if the communication speed with a client device connected via a network is equal to or higher than a threshold, an update module is transmitted to the client device to perform an update. .

  In addition, the program according to the present invention transmits an update module to a client device when the communication speed with a client device connected via a network is greater than or equal to a threshold by the server device, and receives the update module by the client device. It is characterized by having a computer execute updating.

  The program according to the present invention causes the computer to execute an update by sending an update module to the client device if the communication speed with the client device connected via the network is equal to or higher than a threshold. And

  By controlling the update based on the communication speed between the server terminal and the client terminal according to the present invention, it is possible to prevent the versions between the two terminals from being inadvertently different.

It is a block diagram of the thin client system which concerns on the 1st Embodiment of this invention. It is a flowchart figure of the thin client system which concerns on the 1st Embodiment of this invention. It is a flowchart figure of the thin client system which concerns on the 2nd Embodiment of this invention. It is a block diagram of the thin client system which concerns on the 4th Embodiment of this invention. It is a flowchart figure of the thin client system which concerns on the 4th Embodiment of this invention. It is a flowchart figure of the thin client system which concerns on the 5th Embodiment of this invention. It is a block diagram of the thin client system which concerns on the 7th Embodiment of this invention. It is a flowchart figure of the thin client system which concerns on the 7th Embodiment of this invention. It is a block diagram of the thin client system which concerns on the 8th Embodiment of this invention. It is a flowchart figure of the thin client system which concerns on the 8th Embodiment of this invention.

  Next, the best mode for carrying out the invention will be described in detail with reference to the drawings.

(First embodiment)
FIG. 1 is a configuration diagram of a thin client system according to the first embodiment of the present invention. The thin client system includes a server terminal 100 and a client terminal 200, which are connected via a network 300, respectively. Note that the thin client system of this embodiment can be similarly constructed even when a plurality of client terminals are provided.

  The server terminal 100 includes a communication speed determination unit 11, an update unit 12, and a data transmission unit 13.

  The communication speed determination unit 11 measures the communication speed with the connected client terminal 200 and determines whether or not the communication speed is equal to or higher than a predetermined threshold. As a method for measuring the speed, for example, the speed is calculated from the number of packets per unit time passing through the used port by transmitting and receiving dummy data. Note that a speed measurement may be performed by providing a support server for transmitting and receiving dummy data.

  Here, it is preferable that the set threshold is set to such an extent that a communication speed sufficient for transmitting and receiving the update module can be obtained. In other words, the setting may be made so that the update module can be transmitted within a certain time.

  Therefore, for example, a table that changes the threshold of the communication speed according to the data amount of the update module to be transmitted may be prepared, and the threshold of the communication speed may be changed according to the capacity of the update module according to the table.

  The update unit 12 inquires whether or not the latest version of the update module exists in the update module distribution server. If there is the latest version, the update module 12 downloads the update module for itself and the client terminal from the update module distribution server. Update itself using the terminal update module.

  If the communication speed determination unit 11 determines that the communication speed with the client terminal 200 is equal to or higher than the threshold value, the data transmission unit 13 transmits the client terminal update module downloaded from the update unit 12 to the client terminal.

  The client terminal 200 includes a data receiving unit 21 and an update unit 22.

  The data receiving unit 21 receives the client terminal update module from the server terminal 100.

  The update unit 22 updates itself using the client terminal update module received from the server terminal 100.

  FIG. 2 is a flowchart showing a thin client system update method according to the first embodiment of the present invention.

  The server terminal 100 connects to the update module distribution server, inquires whether or not the latest version of the update module exists, and determines whether or not there is the latest version (step S11).

  If there is the latest version, the communication speed with the client terminal 200 is measured (step S12), and it is determined whether or not the measured communication speed is equal to or higher than a threshold value (step S13).

  If the communication speed equal to or higher than the threshold value is present between the server terminal 100 and the client terminal 200, the update module is downloaded (step S14). If update modules for the server terminal and client terminal are prepared separately, both update modules are downloaded.

  The server terminal 100 transmits the downloaded update module to the client terminal 200 (step S15), and the client terminal 200 receives the update module (step S16).

  The client terminal 200 updates itself using the received update module (step S17), and determines whether the update has been normally performed (step S18).

  If the update is normally performed, an update success notification is transmitted to the server terminal 100 (step S19).

  When the server terminal 100 receives the update success notification (step S20), it updates itself using the update module downloaded in step S14 (step S21).

  If the update success notification is not sent even after a predetermined time has elapsed, it is determined that the update has failed and the update itself is not performed. At this time, the update module may be transmitted again, or may be repeated from the first process. In addition, the time at this time may be changed by calculating the expected time required for the update from the downloaded update module, or a predetermined time sufficient for the update may be set in advance.

(Second Embodiment)
FIG. 3 is a flowchart showing a thin client system update method according to the second embodiment of the present invention. In addition, about the process similar to 1st Embodiment, the same code | symbol is attached | subjected and detailed description is abbreviate | omitted.

  The server terminal 100 connects to the update module distribution server, inquires whether or not the latest version of the update module exists, and determines whether or not there is the latest version (step S11).

  If there is the latest version, the communication speed with the client terminal 200 is measured (step S12), and it is determined whether or not the measured communication speed is less than a threshold value (step S31).

  If the communication speed equal to or higher than the threshold value is present between the server terminal 100 and the client terminal 200, the update is performed according to the processing after step S14 in the first embodiment (step S40).

  On the other hand, if the measured communication speed is less than the threshold value, an instruction to update the client terminal 200 is transmitted (step S32).

  The client terminal 200 connects to the update module distribution server according to the update instruction and downloads the update module (step S33).

  The client terminal 200 updates itself using the downloaded update module (step S34), and determines whether the update has been normally performed (step S35).

  If the update is normally performed, an update success notification is transmitted to the server terminal 100 (step S36). At this time, the updated version information may be included in the update success notification.

  When the server terminal 100 receives the update success notification (step S37), it connects to the update module distribution server, downloads the update module (step S38), and updates itself (step S39).

  When sending an update instruction, if it is determined that a sufficient communication speed cannot be obtained for the client terminal 200, the update instruction may not be sent, or the client terminal 200 receives the update instruction. However, the update may not be performed when it is determined that a sufficient communication speed cannot be obtained. For example, two thresholds for the communication speed are provided, and if it is equal to or greater than the first threshold, the update module is transmitted from the server terminal 100 to the client terminal 200, and if it is equal to or greater than the second threshold and less than the first threshold, the update is performed. If the instruction is transmitted and less than the second threshold, the update instruction may not be transmitted and the update including itself may not be performed. Further, it may be determined whether or not to update from the data amount of the update module.

  Even if there is no instruction from the server terminal 100, the client terminal 200 connects to the update module distribution server and inquires whether or not there is the latest version of the update module. If it is determined that it can be obtained, an update may be performed. At this time, processing is performed in accordance with step S33 and subsequent steps.

(Third embodiment)
The thin client system update method according to the third embodiment of the present invention determines whether or not the judgment criteria in steps S13 and S31 in FIGS. 2 and 3 are in the same LAN. Note that “on the same LAN” refers to a state in which the connection between both terminals is established within the management of the same router. Identify.

  That is, in FIG. 2, it is determined whether or not the server terminal 100 and the client terminal 200 exist on the same LAN in step S13. I do.

(Fourth embodiment)
FIG. 4 is a configuration diagram of a thin client system according to the fourth embodiment of the present invention. In the thin client system, the server terminal 101 further includes a version detection unit 14 in addition to the configuration of the thin client system in the above embodiment. Since other configurations are the same as those in the above embodiment, detailed description thereof is omitted.

  The version detection unit 14 collects version information of software provided in the client terminal 200 and determines whether or not it matches the version of itself.

  FIG. 5 is a flowchart showing a thin client system update method according to the fourth embodiment of the present invention.

  When the server terminal 101 detects that the client terminal 200 is connected to the server terminal 101 via the network (step S41), the server terminal 101 collects software version information of the client terminal 200 (step S42).

  It is determined from the collected information whether it is different from its own version (step S43). If each version is different, the communication speed with the client terminal 200 is measured (step S44), and it is determined whether or not the measured communication speed is equal to or higher than a threshold value (step S45).

  If a communication speed equal to or higher than the threshold value is present between the server terminal 101 and the client terminal 200, the server terminal 101 transmits the update module that it holds to the client terminal 200 (step S46), and the client terminal 200 An update module is received (step S47). At this time, if the client module does not have the same client terminal update module as its own version, it connects to the update module distribution server and downloads and transmits the update module. Further, only the difference necessary for making the same version among the modules held may be transmitted.

  The client terminal 200 updates itself using the received update module (step S48).

(Fifth embodiment)
FIG. 6 is a flowchart showing a thin client system update method according to the fifth embodiment of the present invention. Note that the thin client system in the present embodiment is configured to have the same functions as the thin client system in the fourth embodiment.

  When the server terminal 101 detects that the client terminal 200 is connected to the server terminal 101 via the network (step S41), the server terminal 101 collects software version information of the client terminal 200 (step S42).

  It is determined from the collected information whether it is different from its own version (step S43). If each version is different, the communication speed with the client terminal 200 is measured (step S44), and it is determined whether or not the measured communication speed is less than a threshold value (step S51).

  If the communication speed equal to or higher than the threshold value is present between the server terminal 101 and the client terminal 200, the update is performed according to the processing after step S46 in the fourth embodiment (step S53).

  On the other hand, if the measured communication speed is less than the threshold value, update or downdate is performed so as to be the same version as the client terminal 200 (step S52). At this time, if the update (downdate) module is not held, the update module is connected to the update module distribution server, and the update module is downloaded and updated.

  If multiple client terminals are connected, check each version including itself, and update or downdate the version that is used most frequently among the connected terminals. . Further, update or downdate may be performed to match the version of a client terminal that is frequently used.

(Sixth embodiment)
The thin client system in this embodiment is configured to have the same functions as the thin client system in the fourth embodiment, and is updated to each client terminal when the number of connected client terminals exceeds a certain number. Send instructions. That is, when the client terminal is connected in step S41, the update is performed according to the flowchart of FIG.

  In this way, it is configured to perform update processing when there are more than the specified number of connections, so that the version that is most frequently used in the connected terminal is grasped, and the update is performed to match the version. Efficient updates in the system can be performed.

(Seventh embodiment)
FIG. 7 is a configuration diagram of a thin client system according to the seventh embodiment of the present invention. In this thin client system, the server terminal 102 further includes a schedule management unit 15 in addition to the configuration of the thin client system in the above embodiment. In addition, about the function part similar to the said other embodiment, the same symbol is attached | subjected and detailed description is abbreviate | omitted.

  The schedule management unit 15 is a functional unit that stores a schedule and manages an update time zone. The information stored as the schedule includes a meeting time zone and a time zone for going out. Each schedule is recorded in association with whether or not to update in that time zone.

  For example, the schedule associated with the update may be a waiting time in the room, or a time zone in which communication such as midnight or early morning scheduled as sleep time can be performed stably. In addition, as a time zone in which the update is prohibited, for example, a time zone during the conference from one hour before the conference can be considered. At this time, the update may be performed only in the schedule associated with the update, or the update may be permitted at any time other than the update prohibition time.

  Further, the schedule may be determined based on the number of simultaneous connections of the client terminals, even if the schedule is not previously input in association with the time. For example, when the number of simultaneous connections reaches a specified value, it is determined that a one-hour meeting will be held thereafter, and updates are prohibited during that time.

  FIG. 8 is a flowchart showing a thin client system update method according to the seventh embodiment of the present invention. In addition, about the process similar to 1st Embodiment, the same code | symbol is attached | subjected and detailed description is abbreviate | omitted.

  The server terminal 102 connects to the update module distribution server, inquires whether or not the latest version of the update module exists, and determines whether or not there is the latest version (step S11).

  If there is a latest version, the schedule management unit 15 is referred to and it is determined whether or not it is a time zone in which updating is prohibited (step S61).

  If the update is prohibited, the process waits until the update is allowed and proceeds to the next process (step S62).

  Since the subsequent processing is the same as in the first embodiment, detailed description thereof is omitted. Also in other embodiments, it is possible to perform update processing using schedule management as in the present embodiment.

(Eighth embodiment)
FIG. 9 is a configuration diagram of a thin client system according to the eighth embodiment of the present invention. In this thin client system, the server terminal 103 further includes an activation unit 16 in addition to the configuration of the thin client system in the above embodiment. In addition, about the function part similar to the said other embodiment, the same symbol is attached | subjected and detailed description is abbreviate | omitted.

  The activation unit 16 holds the MAC address of the connected client terminal, and activates a client terminal that has not been activated by making an activation request based on the MAC address. As a starting method, a known technique such as WOL (Wake On LAN) may be used. Here, WOL is a technology for starting a client terminal on the same LAN having the MAC address by making an activation request to a MAC address held in advance.

  FIG. 10 is a flowchart showing a thin client system update method according to the eighth embodiment of the present invention. In addition, about the process similar to 1st Embodiment, the same code | symbol is attached | subjected and detailed description is abbreviate | omitted.

  The server terminal 103 connects to the update module distribution server, inquires whether or not the latest version of the update module exists, and determines whether or not there is the latest version (step S11).

  If there is the latest version, an activation request is made based on the held MAC address (step S71), and it is determined whether or not the activation is made by the activation request (step S72).

  If there is a client terminal activated by the activation request, it can be determined that it is a client terminal on the same LAN, and therefore update processing is performed in accordance with step S14 and subsequent steps.

  Since the subsequent processing is the same as in the first embodiment, detailed description thereof is omitted.

  Although the embodiments have been described above, various modifications and changes can be made to these embodiments and specific examples without departing from the broad scope and scope of the present invention defined in the claims.

DESCRIPTION OF SYMBOLS 11 Communication speed determination part 12 Update part 13 Data transmission part 14 Version detection part 15 Schedule management part 16 Start-up part 21 Data reception part 22 Update part 100 Server terminal 200 Client terminal 300 Network

Claims (42)

A thin client system comprising one or more client devices and a server device connected to the client devices via a network,
The server device
If the communication speed with the client device is equal to or higher than a threshold, send an update module to the client device,
The client device is
A thin client system, wherein the update module is received and updated.   2. The thin client system according to claim 1, wherein the server device stores one or more update modules as the update module, downloads the update module from a distributed update module distribution server, and transmits the update module to the client device. . If the communication speed is less than the threshold, the server device transmits an update instruction to the client device,
The thin client system according to claim 1, wherein the client device performs an update by downloading an update module from the update module distribution server.   4. The thin client system according to claim 3, wherein the server device does not transmit an update instruction to the client device when the communication speed is less than a second threshold. The client device sends an update success notification to the server device after the update is completed,
5. The thin client system according to claim 1, wherein the server device updates to the same version as the updated version of the client device after receiving the update success notification. 6.   The thin client system according to claim 5, wherein the server device transmits the update module or the update instruction again when the update success notification is not received within a predetermined time.   The thin client system according to claim 1, wherein the communication speed threshold is set according to a data amount of an update module.   The said server apparatus judges that the said communication speed is more than a threshold value, when the said server apparatus and the said client apparatus are on the same LAN, The any one of Claim 1 to 7 characterized by the above-mentioned. Thin client system. Stores the MAC address of the connected client device,
9. The thin client system according to claim 8, wherein an activation request is sent to the client device based on the MAC address, and an update module is transmitted to the activated client device.   10. The server device according to claim 1, wherein if the update module distribution server has a latest version of the update module, the server device determines whether the communication speed is equal to or higher than a threshold value. Thin client system as described in When the client device is connected, the server device confirms the version of the connected client device,
The thin client system according to any one of claims 1 to 9, wherein if the versions are different, it is determined whether or not the communication speed is equal to or higher than a threshold value. The server device confirms the version of the connected client device when the client device is connected more than the specified number,
The thin client system according to any one of claims 1 to 9, wherein if the versions are different, it is determined whether or not the communication speed is equal to or higher than a threshold value. If the communication speed with the client device is equal to or higher than a threshold, the server device transmits difference data for making the client device the same version as itself,
The thin client system according to claim 11, wherein the client device receives the difference data and performs an update.   The thin client according to any one of claims 11 to 13, wherein the server device updates itself so as to be the same version as the client device if the communication speed is less than a threshold value. system. The server device determines the version most frequently used including itself when a plurality of client devices are connected,
The thin client system according to claim 11, wherein the server device and the client device are updated to match the version. The server device determines the version used by the most frequently used client device when a plurality of client devices are connected,
The thin client system according to claim 11, wherein the server device and the client device are updated to match the version. Stores the update permission or prohibition time,
The thin client system according to claim 1, wherein no update is performed during the prohibited time.   The thin client system according to claim 17, wherein a prohibited time is set based on the number of connections of the client device.   If the communication speed with a client device connected via a network is equal to or higher than a threshold, an update module is transmitted to the client device to perform an update.   20. The server apparatus according to claim 19, wherein the update module stores one or more update modules, downloads the update module from a distributed update module distribution server, and transmits the downloaded update module to the client apparatus.   The server device according to claim 19 or 20, wherein if the communication speed is less than a threshold value, an update instruction is transmitted to the client device.   The server device according to claim 21, wherein when the communication speed is less than a second threshold, an update instruction is not transmitted to the client device.   The server device according to any one of claims 19 to 22, wherein upon receiving a successful update notification from the client device, the server device updates to the same version as the updated version of the client device.   24. The server apparatus according to claim 23, wherein if the update success notification is not received within a predetermined time, the update module or the update instruction is transmitted again.   The server device according to any one of claims 19 to 24, wherein the threshold value of the communication speed is set according to a data amount of an update module.   The server apparatus according to any one of claims 19 to 25, wherein when the client apparatus is on the same LAN, the communication speed is determined to be equal to or higher than a threshold value. Stores the MAC address of the connected client device,
27. The server apparatus according to claim 26, wherein an activation request is sent to the client apparatus based on the MAC address, and an update module is transmitted to the activated client apparatus.   28. The update module according to any one of claims 19 to 27, wherein if the latest version of the update module is stored in the update module distribution server that stores and distributes the update module, it is determined whether or not the communication speed is equal to or higher than a threshold value. The server device according to any one of the above. When the client device is connected, the version of the connected client device is confirmed,
28. The server device according to claim 19, wherein if the versions are different, it is determined whether or not the communication speed is equal to or higher than a threshold value. When the client device is connected more than the specified number, confirm the version of the connected client device,
28. The server device according to claim 19, wherein if the versions are different, it is determined whether or not the communication speed is equal to or higher than a threshold value.   The server apparatus according to claim 29 or 30, wherein if the communication speed with the client apparatus is equal to or higher than a threshold, difference data for making the client apparatus the same version as itself is transmitted.   The server apparatus according to any one of claims 29 to 30, wherein if the communication speed is less than a threshold value, the server apparatus updates itself so as to be the same version as the client apparatus.   33. The method according to any one of claims 29 to 32, wherein when a plurality of client devices are connected, a version that is used most frequently including itself is determined and updated so as to match the version. The server apparatus of description.   33. When a plurality of client devices are connected, the version used by the client device having the highest use frequency is determined, and the version is updated so as to match the version. 2. The server device according to item 1. Stores the update permission or prohibition time,
The server apparatus according to any one of claims 19 to 34, wherein no update is performed during the prohibited time.   36. The server apparatus according to claim 35, wherein a prohibited time is set based on the number of connections of the client apparatus. If the communication speed with the client device connected via the network is equal to or higher than the threshold, the server device sends an update module to the client device,
An update method for a thin client system, wherein the update is received by the client device and the update module is received. If the communication speed is less than a threshold by the server device, an update instruction is transmitted to the client device,
38. The thin client system update method according to claim 37, wherein said client device stores an update module in accordance with said update instruction, and downloads and updates the update module from a distributed update module distribution server. .   An update method for a server device, wherein if the communication speed with a client device connected via a network is equal to or greater than a threshold, an update module is transmitted to the client device to perform an update.   40. The server apparatus update method according to claim 39, wherein if the communication speed is less than a threshold, an update instruction is transmitted to the client apparatus. If the communication speed with the client device connected via the network is equal to or higher than the threshold, the server device sends an update module to the client device,
A program for causing a computer to execute an update by receiving the update module by the client device.   A program for causing a computer to execute an update by transmitting an update module to a client device if a communication speed with a client device connected via a network is equal to or higher than a threshold.

Images