JP5250573B2 - Thin client master rewrite system and thin client master rewrite method - Google Patents

Description

  The present invention relates to a rewriting system for a thin client master and a rewriting method for a thin client master, and more specifically to a technique that enables an update process in a thin client to be managed efficiently and at low cost.

  Due to the need for information leakage countermeasures and internal control at companies, etc., the client computer employs a dedicated thin client (security PC) that has minimum functions such as display and input or can be used, such as application software. The idea of a thin client system has emerged in which resources are centrally managed by a thin client server (for example, a blade server). As an update technique for software or the like in such a thin client system, for example, techniques for transmitting update data to a thin client via a network (Patent Documents 1 and 2, etc.) have been proposed.

JP 2008-262454 A JP 2008-159054 A

  In the prior art, for example, when there is a need to update a large number of thin clients loaned from a certain organization to another organization, the other organization needs to bring in this large number of thin clients to the lending source organization and request an update. is there. On the other hand, in the lending source organization, the person in charge has to execute update operations for a large number of thin clients brought in. Or, conversely, the person in charge of the lending source organization needs to go to the other organization to perform update operations for a large number of thin clients.

  That is, in the update process, a thin client transport process and a person-in-time work are required, and work efficiency is not good. Therefore, from the viewpoint of a thin client user, a lot of time for waiting for an update occurs, and there is a concern that the processing efficiency of the business using the thin client may be reduced.

  On the other hand, in order to perform such update processing efficiently and with good user convenience, a large number of update server devices are arranged for each network (segment) used by each user, and the thin client side accesses the server device of its own segment. It can be assumed that update processing is performed. However, the installation and operation of server devices for each segment has a drawback that the cost and labor of introduction and management increase. In addition, it is essential to install the server device for each segment, and the degree of freedom of installation is lacking.

  Accordingly, the present invention has been made in view of the above problems, and a main object of the present invention is to provide a technique that enables an update process in a thin client to be managed efficiently and at low cost.

  The thin client master rewriting system of the present invention that solves the above problems is a computer system that includes a thin client, an inquiry response server, and an update server, each of which has the following configuration.

  That is, the thin client includes a communication device that communicates with other devices via a network, a first disk partition that stores at least a first operating system, and a second disk that stores a second operating system and a backup program. And a storage device in which addresses on the network of the inquiry corresponding server are stored.

  The thin client includes a request transmission unit that reads an address of an inquiry response server from the storage device in response to a user instruction received by an input device, and transmits an update server information request to the corresponding address. Yes.

  In response to the information request, the thin client receives the address of the update server from the inquiry response server, changes the active partition setting in the master boot record to the second disk partition, and reboots. An update starter is provided for execution.

  In addition, the thin client starts the second operating system by executing the reboot, executes the backup program, and sends an update request including its own device ID to the address of the update server. And a restore processing unit that receives a disk image corresponding to the device ID from the update server and restores the first disk partition with the disk image by the backup program.

  The inquiry support server includes a communication device that communicates with other devices via a network, and a storage device that stores an address list related to each update server device determined according to each address on the network.

  The inquiry response server receives the information request from the thin client, collates the address of the thin client included in the information request with an address list of the storage device, and updates the server corresponding to the address of the thin client An address notification unit is provided for identifying the address of the address and returning the address identified here to the thin client.

  The update server includes a communication device that communicates with other devices via a network, and a storage device that stores a disk image for update in association with the device ID of the thin client.

  The update server receives the update request from the thin client, extracts a disk image from the storage device based on a device ID included in the update request, and transmits the disk image to the thin client. A transmission unit is provided.

  In the thin client master rewriting system of the present invention, the thin client update activation unit sends a session establishment request including the unique ID of the communication device and its own device ID in response to a user instruction received by the input device. Transmit to the update server, receive a session establishment notification corresponding to the session establishment request from the update server, change the active partition setting in the master boot record to the second disk partition, and execute the reboot It is good.

  In this case, the restore processing unit of the thin client starts the second operating system by executing the reboot, executes the backup program, and sets the unique ID of the communication device and its own device ID as a session name. The update request is transmitted to the update server, a disk image corresponding to the unique ID and the device ID of the communication device is received from the update server, and the first disk partition in the disk image is received by the backup program. It is preferable to execute restoration.

  In this case, the master transmission unit of the update server receives the session establishment request from the thin client, enters a request waiting state from the thin client with the unique ID and the device ID as a session name, and then An update request with the unique ID of the communication device and the device ID as a session name is received from the thin client, a disk image is extracted from the storage device based on the device ID included in the update request, and the disk image is extracted from the thin client. It is preferable to transmit to the client.

  In the thin client master rewriting method of the present invention, the thin client, the inquiry response server, and the update server each execute the following processing. That is, a communication device that communicates with other devices via a network, a first disk partition that stores at least a first operating system, and a second disk partition that stores a second operating system and a backup program are set. The thin client having a storage device storing the address of the inquiry corresponding server on the network reads the address of the inquiry corresponding server from the storage device in response to a user instruction received by the input device, and the corresponding address An update server information request is sent to.

  In response to the information request, the thin client receives the address of the update server from the inquiry response server, changes the active partition setting in the master boot record to the second disk partition, and reboots. Run.

  In addition, the thin client starts the second operating system by executing the reboot, executes the backup program, and sends an update request including its device ID to the address of the update server. The disk image corresponding to the device ID is received from the update server, and the first disk partition is restored with the disk image by the backup program.

  An inquiry response server having a communication device that communicates with another device via a network, and a storage device that stores an address list related to each update server device defined according to each address on the network, The request is received from the thin client, the address of the thin client included in the information request is collated with the address list of the storage device, the address of the update server corresponding to the address of the thin client is specified, and is specified here. The address is returned to the thin client.

  An update server having a communication device that communicates with another device via a network and a storage device that stores a disk image for update in association with the device ID of the thin client sends the update request to the thin client. The disk image is extracted from the storage device based on the device ID included in the update request, and the disk image is transmitted to the thin client.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.

  According to the present invention, update processing in a thin client can be managed efficiently and at low cost.

It is a network block diagram of the rewriting system of the thin client master of this embodiment. It is a figure which shows the structural example of security PC (thin client) of this embodiment. It is a figure which shows the structural example of the station server (server for an update) of this embodiment. It is a figure which shows the structural example of the inquiry corresponding | compatible server of this embodiment. It is a figure which shows the example of a data structure of the image table in this embodiment. It is a figure which shows the example of a data structure of the address table (address list) in this embodiment. It is a figure which shows the example of a processing flow of the rewriting method of the thin client master in this embodiment.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a network configuration diagram of a rewriting system 10 for a thin client master according to this embodiment. A thin client master rewriting system 10 shown in FIG. 1 includes a plurality of security PCs 100 (thin clients), a plurality of station servers 200 (update servers), and an inquiry response server that can be connected to each other via a network 140 such as a LAN. 400 (the distribution server 300 that distributes data for update may be included in the station server), and the update processing in the thin client can be managed efficiently and at low cost. . The security PC 100 can be a local disk, a thin client dedicated PC that prohibits data storage on media, and the like.

  As an example of a situation assumed in the present embodiment, it is assumed that a certain company has lent the security PC 100 to a large number of employees, and a situation in which a large number of security PCs 100 need to be updated has occurred. Moreover, it is assumed that the update can be executed only by performing a master update, that is, a disk image restoration process. The corporate LAN, which is the network 140 constructed in the company, is segmented by each business department or department.

  In the present embodiment, in order to cope with such a situation, one or more update servers, that is, the station servers 200 are installed in a predetermined segment in the network 140 in advance. However, the station server 200 is not necessarily connected to each segment. Rather, it is easy to assume a situation where a system administrator or the like installs the station server 200 at a ratio of a plurality of segments in terms of installation / operation costs and labor. In addition, it can be assumed that the installation interval of the station servers 200 between the segments is uniform (for example, station servers are installed skipping one segment in adjacent segments), but the station servers 200 are unevenly distributed in a certain segment group. Of course, it can be assumed that the installation intervals are uneven. In the example shown in FIG. 1, three segments corresponding to business units A to C are built in the network 140, while the station server 200 includes business unit A = segment “s0001” and business unit C = segment. It is installed only in “s0003”.

  In addition, each station server 200 has already distributed the disk image for thin client update from the distribution server 300 at an appropriate timing.

  Next, each device constituting the thin client master rewriting system 10 in the present embodiment will be described. FIG. 2 is a diagram illustrating a configuration example of the security PC 100 according to the present embodiment. The security PC 100 is an apparatus that acquires the address of the nearest station server 200 from the inquiry response server 400 via the LAN 140 and receives a master update from the station server 200 corresponding to the address, and has a function of realizing the present invention. The program 102 stored in the hard disk drive 101 (or TPM) or the like is read out to the RAM 103 and prepared by the CPU 104 which is an arithmetic device.

  The security PC 100 exchanges data with an input device 105 such as various keyboards and buttons generally provided in a computer device, an output device 106 such as a display, and the station server 200 and the inquiry response server 400. It has a NIC 107 (communication device) and the like.

  As such a security PC 100, in the present embodiment, a terminal in which a PC including an HDD is made into a thin client is assumed instead of a so-called HDD-less type terminal. As for the technology for converting a general PC into a thin client, an existing technology (reference) is performed such that a USB memory built in an OS is connected to a USB interface of a general PC and a series of thin client processes such as OS activation, VPN connection, and management server authentication are executed. : Http://www.hitachi-ics.co.jp/product/seihin/jyourou/sec/sec.html).

  The security PC 100 further includes a flash ROM (Read Only Memory) 108. The flash ROM 108 stores a BIOS (Basic Input / Output System) 135. The CPU 104 first recognizes the system configuration of the security PC 100 by accessing the flash ROM 108 and executing the BIOS 135 after the power is turned on. Note that the address on the network of the inquiry corresponding server 400 = IP address 125 is stored in the flash ROM 108 or HDD 101 (for example, the second disk partition) of the security PC 100.

  The security PC 100 stores an OS (Operating System) 136 and a master boot record 137 in the HDD 101. The OS 136 is a program for the CPU 104 to comprehensively control each unit of the security PC 100. When the computer is turned on, the CPU 104 reads the bootstrap code in the master boot record 137 into the RAM 103 and executes it according to the BIOS 135. The executed bootstrap code finds an active disk partition (partition set for boot) from the partition table of the master boot record 137 and reads the bootstrap code written at the head of the partition. By executing, the OS 136 is loaded from the HDD 101 to the RAM 103 and executed.

  In the security PC 100 of the present embodiment, the HDD 101 is set with at least two disk partitions. The first disk partition 50 stores, for example, an OS 136a (first operating system) that is normally used by the security PC 100, an application 138 that is normally used by a user in business, and the like. Further, the second disk partition 55 stores a backup program 139 and an OS 136b (second operating system) as an execution environment of the backup program 139. As the backup program 139, an existing backup tool capable of restoration processing via a network may be employed.

  Next, functional units that the security PC 100 configures and holds in the hard disk drive 101 (or TPM) based on the program 102 will be described.

  The security PC 100 reads the IP address 125 of the inquiry response server 400 from the storage device (flash ROM 108 to HDD 101) in response to a user instruction received by the input device 105, and sends the address of the station server 200 to the corresponding IP address 125. The request transmission unit 110 transmits the information request. When the segment to which the security PC 100 is connected and the segment to which the inquiry response server 400 is connected are different, naturally, IP packets are transferred between appropriate network devices such as routers of each segment.

  Further, the security PC 100 receives the IP address 420 of the station server 200 from the inquiry response server 400 in response to the information request, and sets the active partition setting in the master boot record 137 to the second disk partition 55. An update activation unit 111 that changes and executes reboot is provided.

  In addition, the security PC 100 starts the second operating system 136b by executing the reboot, executes the backup program 139, and sends an update request including its own device ID to the IP address 420 of the station server 200. A restore processing unit 112 which receives the disk image corresponding to the device ID from the station server 200 and restores the first disk partition 50 with the disk image by the backup program 139. Prepare. In the same manner as described above, when the segment to which the security PC 100 is connected is different from the segment to which the station server 200 is connected, it is a matter of course that IP packets are transferred between appropriate network devices such as routers of each segment. .

  In response to a user instruction received by the input device 105, the update activation unit 111 sends a session establishment request including a MAC address that is a unique ID of the NIC 107 and its own device ID (such as the model number of the security PC 100) to the station server. 200 (IP address 420) is sent to the station server 200 in response to the session establishment request in response to the session establishment request, and the active partition setting in the master boot record 137 is changed to the second disk partition 55. Then, reboot may be performed.

  Further, in this case, the restore processing unit 112 starts the second operating system 136b by executing the reboot, executes the backup program 139, the MAC address which is the unique ID of the NIC 107, and its own device ID. Is sent to the IP address 420 of the station server 200, a disk image corresponding to the MAC address and device ID of the NIC 107 is received from the station server 200, and the backup program 139 sends the disk The restoration of the first disk partition 50 with an image is executed.

  The security PC 100 includes certificate information about a user stored in a portable storage medium (eg, USB memory) connected to the USB port 144, user ID and password information input by the input device 105, and the like. Naturally, a function for executing connection establishment processing with a thin client server using the client is provided as a thin client.

  Examples of the portable storage medium include, for example, a USB device in which an IC chip is stored in an appropriate storage case such as a plastic housing and connected to the USB port 144 of the security PC 100 so that data communication is possible. Such an IC chip is composed of a CPU and a memory. The portable storage medium includes an authentication device (trademark) in which a personal certificate, a private key, a password, and various application software necessary for mobile use are preinstalled in a memory card in which an IC card unit and a flash memory are integrated. Name: KeyMobile). Information stored in the memory of the portable storage medium includes authentication information storing a chip ID, a personal certificate, a secret key, and a password, an address of a thin client server to which the security PC 100 is allocated, and software (OS, software that executes personal authentication processing related to the user of the portable storage medium, etc.) can be assumed.

  Further, the security PC 100 transmits the operation information input by the input device 105 of the security PC 100 to the address of the thin client server in accordance with the execution of the connection establishment process with the thin client server, and the operation information Naturally, the thin client also has a function of receiving video information corresponding to the above from the thin client server and displaying it on the output device 106 of the security PC 100.

  Further, the security PC 100 according to the present embodiment includes device information, for example, in the hard disk drive 101. The device information is information for authentication of the security PC 100. Specifically, for example, the ID and model number (device ID) of the security PC 100, the MAC address of the NIC 107 (unique ID of the communication device), and the like can be assumed.

  In this embodiment, the security PC 100 stores the means 110 to 112, the IP address 125 of the inquiry corresponding server 400, the OS 136a and 136b, the master boot record 137, the application 138, the backup program 139, the device information, etc. Instead, it may be housed in a chip called a TPM (Trusted Platform Module).

  This TPM has a function similar to that of a security chip mounted on a smart card (IC card). It is a hardware chip that has an asymmetric key calculation function and tamper resistance for safe storage of these keys. is there. The functions of this TPM include, for example, RSA (Rivest-Shamir-Adleman Scheme) private key generation / storage, RSA private key computation (signature, encryption, decryption), SHA-1 (Secure Hash Algorithm 1) hash Calculation, platform state information (software measurement) retention (PCR), key, certificate, credential trust chain retention, high-quality random number generation, non-volatile memory, other opt-in and I / O It is done.

  The TPM has a function to securely store and notify platform status information (software measurement values) in a register PCR (Platform Configuration Registers) in the TPM, in addition to generating, storing, and calculating cryptographic keys (asymmetric keys). Have. In the latest specification of TPM, functions such as locality and delegation (authority delegation) are further added. The TPM is physically attached to platform parts (motherboard or the like).

  Next, the configuration of the station server 200 as an update server will be described. FIG. 3 is a diagram illustrating a configuration example of the station server 200 of the present embodiment. The station server 200 is a server device that receives an update request from the security PC 100 and provides a disk image corresponding to the security PC 100. The station server 200 is stored in an HDD (hard disk drive) 201 or the like so as to have a function for realizing the present invention. The read program 202 is read out to the RAM 203 and executed by the CPU 204 which is an arithmetic unit.

  The station server 200 may include an input device 205 such as various keyboards and buttons generally provided in a computer device, and an output device 206 such as a display as necessary. In addition, it includes a NIC 207 that handles data exchange with the security PC 100 and the like.

  The station server 200 also has a flash ROM (Read Only Memory) 208. The flash ROM 208 stores a BIOS (Basic Input / Output System) 235. After the power source 220 is turned on, the CPU 204 first accesses the flash ROM 208 and executes the BIOS 235 to recognize the system configuration of the station server 200.

  The station server 200 stores an OS (Operating System) 236 in the HDD 201. The OS 236 is a program for the CPU 204 to comprehensively control each unit of the station server 200. In accordance with the BIOS 235, the CPU 204 loads the OS 236 from the HDD 201 to the RAM 203 and executes it. As a result, the CPU 204 comprehensively controls each unit of the station server 200.

  The station server 200 stores an update disk image 250 in association with the device ID (model number, etc.) of the security PC 100 in the image table 225 of the HDD 201. This disk image 250 is, for example, a device that can be newly connected to the security PC 100 (for example, a communication card, etc., a communication device when connecting the security PC 100 to an external network and making a thin client connection with a thin client server). This is a disk image or the like in which the driver is set in the OS, and is data obtained in advance by receiving appropriate distribution from the distribution server 300.

  The functional units that the station server 200 configures and holds in the hard disk drive 201 based on the program 202 will be described.

  The station server 200 receives the update request from the security PC 100, extracts a disk image from the HDD 201 based on the device ID included in the update request, and transmits the disk image to the security PC 100. Is provided.

  The master transmission unit 210 receives the session establishment request from the security PC 100, enters a request waiting state from the security PC 100 with the unique ID and the device ID as a session name, and then receives the MAC address of the NIC. And an update request with a device ID as a session name is received from the security PC 100, a disk image is extracted from the HDD 201 based on the device ID included in the update request, and the disk image is transmitted to the security PC 100. Good. The distribution server 300 is a server device that includes a communication device that communicates with the station server 200 via the LAN 140, a storage device that stores disk image data to be distributed to the station server 200, and an administrator. And a processing unit that receives a command such as a disk image for each model number of the security PC 100 from the storage device and transmits the disk image to the station server 200.

  Next, the configuration of the inquiry response server 400 will be described. FIG. 4 is a diagram illustrating a configuration example of the inquiry handling server 400 according to the present embodiment. The inquiry response server 400 is a server device that receives an inquiry request regarding the IP address of the station server 200 from the security PC 100 and provides an appropriate IP address 420 of the station server 200, and has a function of realizing the present invention. A program 402 stored in an HDD (Hard Disk Drive) 401 or the like is read into the RAM 403 and executed by the CPU 404 as an arithmetic unit.

  The inquiry response server 400 may include an input device 405 such as various keyboards and buttons generally provided in a computer device, and an output device 406 such as a display as necessary. In addition, it has a NIC 407 for transferring data with the security PC 100 or the like.

  In addition, the inquiry corresponding server 400 further includes a flash ROM (Read Only Memory) 408. The flash ROM 408 stores a BIOS (Basic Input / Output System) 435. After the power source 420 is turned on, the CPU 404 first accesses the flash ROM 408 and executes the BIOS 435 to recognize the system configuration of the inquiry corresponding server 400.

  In addition, the inquiry response server 400 stores an OS (Operating System) 436 in the HDD 401. The OS 436 is a program for the CPU 404 to centrally control each unit of the inquiry response server 400. The CPU 404 loads the OS 436 from the HDD 401 to the RAM 403 and executes it in accordance with the BIOS 435. As a result, the CPU 404 comprehensively controls each unit of the inquiry handling server 400.

  A function unit configured and held by the hard disk drive 401 based on the program 402, for example, will be described below. The inquiry handling server 400 stores an address table 425 that is a list of addresses related to each station server 200 determined according to each address on the network 140 in the HDD 401.

  The inquiry response server 400 receives the information request from the security PC 100, collates the IP address of the security PC 100 included in the information request (packet data thereof) with the address table 425 of the HDD 401, and determines the IP address of the security PC 100. And an address notification unit 410 that identifies the IP address 420 of the station server 200 corresponding to the above and sends back the identified IP address 420 to the security PC 100. Here, when the IP address of the security PC 100 included in the information request is collated with the address table 425 of the HDD 401, the address notification unit 410, for example, has a predetermined digit for identifying a segment in the IP address indicated by the information request packet. A value is extracted and this value is checked against the address table 425.

  When specifying the IP address 420 of the station server 200 corresponding to the IP address of the security PC 100, the address notification unit 410, for example, uses one segment in the network 140 (= the IP address indicated by the information request packet). In the case where the IP address 420 of a plurality of station servers 200 is set in the address table 425 with respect to (specified by a predetermined digit), the operating rate is inquired of each corresponding station server 200, and the IP address 420 having the lowest operating rate is inquired. May be specified.

  Alternatively, the address notifying unit 410 inquires of each network device on the network about the traffic amount and specifies the IP address 420 of the station server 200 on the route connected by the network device with the least traffic amount. Also good. Naturally, it is assumed that the inquiry corresponding server 400 can store and refer to information on the arrangement status of network devices on the network in the HDD 401 or the like.

  Further, each of the units 110 to 112, 210, 410 and the like in the devices constituting the system 10 described so far may be realized as hardware, or may be an appropriate device such as a memory or a HDD (Hard Disk Drive). It may be realized as a program stored in a storage device. In this case, the CPU of each device reads the corresponding program from the storage device into the RAM in accordance with the execution of the program, and executes it.

  In addition to the Internet and LAN, the network 140 may employ various networks such as an ATM line, a dedicated line, a WAN (Wide Area Network), a power line network, a wireless network, a public line network, and a mobile phone network. I can do it. If a virtual dedicated network technology such as VPN (Virtual Private Network) is used, communication with improved security is established when the Internet is adopted.

---- Table structure ---
Next, the structure of the table used by the station server 200 constituting the thin client master rewriting system 10 in this embodiment will be described. FIG. 5 is a diagram showing an example of the data structure of the image table 225 in the present embodiment. The image table 225 is a table held by the station server 200 and stores data of the disk image 250 corresponding to the model number as the device ID of the security PC 100.

  FIG. 6 is a diagram showing an example of the data structure of the address table 425 (address list) in the present embodiment. This address table 425 is a table provided in the HDD (Hard Disk Drive) 401 as the storage device by the inquiry handling server 400. This address table 425 stores a list of IP addresses 420 of each station server 200 determined according to IP addresses on the network 140 (= partial digits of the IP address included in the packet sent from the security PC 100). It is. As a configuration example, for example, for each segment and an IP address corresponding to the segment (for example, a part of an IP address assigned by the DHCP server or the like to the security PC 100), for example, the IP address 420 of the nearest station server 200 and the station server A configuration in which names are associated can be assumed. In the example of FIG. 6, for the segment “s0001” = the IP address “***. ***. 59. **” indicated by the packet of the security PC 100, there is one IP address 420 of the station server 200 (“* **. *** .... 1 ”), the segment“ s0002 ”= the IP address“ ***. ***. 60. ** ”indicated by the packet of the security PC 100, Two IP addresses 420 (“***. *** .... 1”, “***. *** .... 2”), segment “s0003” = packet of security PC 100 For the IP address “***. ***. 61. **” shown, one IP address 420 (“***. ***.... 2”) of the station server 200 is set. ing.

--- Processing flow example ---
Hereinafter, an actual procedure of the rewriting method of the thin client master in the present embodiment will be described with reference to the drawings. Various operations corresponding to the thin client master rewriting method described below are read out and executed in the RAMs of the security PC 100, the station server 200, and the inquiry corresponding server 400 constituting the thin client master rewriting system 10, respectively. Realized by a program that And this program is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 7 is a diagram showing a processing flow example of the rewriting method of the thin client master in this embodiment. First, the request transmission unit 110 of the security PC 100 reads the IP address 125 of the inquiry corresponding server 400 from the storage device (flash ROM 108 to HDD 101) in response to a user instruction received by the input device 105, and sets the corresponding IP address 125. The information request for the IP address of the station server 200 is transmitted to the destination (s100).

  On the other hand, the address notification unit 410 of the inquiry response server 400 receives the information request from the security PC 100 (s101), and the IP address of the security PC 100 included in the received information request (packet data), for example, “*” **. ***. 59. ** ”is extracted, and this IP address is checked against the address table 425 of the HDD 401 (s102). The address notification unit 410 specifies, for example, “***. ***.... 1” of the IP address 420 of the station server 200 corresponding to the IP address of the security PC 100 by this verification. The IP address 420 specified here is returned to the security PC 100 (s103). When the IP address “***. ***. 59. **” of the security PC 100 included in the information request is checked against the address table 425 of the HDD 401, the address notification unit 410, for example, It is also possible to extract a value “59” of a predetermined digit for identifying a segment from the IP address “***. ***. 59. **” indicated by the packet, and collate this value with the address table 425.

  When specifying the IP address 420 of the station server 200 corresponding to the IP address of the security PC 100, the address notification unit 410, for example, uses one segment in the network 140 (= the IP address indicated by the information request packet). In the case where the IP address 420 of a plurality of station servers 200 is set in the address table 425 with respect to (specified by a predetermined digit), the operating rate is inquired of each corresponding station server 200, and the IP address 420 having the lowest operating rate is inquired. May be specified.

  In the example of FIG. 6, when the address notification unit 410 receives “***. ***. 59. **” as the IP address of the security PC 100, according to the address table 425, the corresponding station As the IP address 420 of the server 200, two of "***. *** .... 1" and "***. *** .... 2" can be specified. Therefore, in this case, the address notification unit 410 has the station servers = servers “A”, “B” (“***. ***.... 1”, “***. ***. ... 2 ″), a command for inquiring the operation rate is transmitted, and information on the operation rate is obtained from each station server. For example, if the station server “A” is the station server “A” among the station servers “A” and “B”, the IP address 420 is “***. *** .... 1”. Will be specified.

  Alternatively, the address notification unit 410 makes an inquiry about the traffic amount to each network device on the network, and the station server 200 on the route connected by the network device with the least traffic amount is referred to as the station server “A”. , “B”, and the corresponding IP address 420 may be specified. Naturally, it is assumed that the inquiry corresponding server 400 can store and refer to information on the arrangement status of network devices on the network in the HDD 401 or the like.

  Subsequently, the update activation unit 111 of the security PC 100 receives the IP address 420 of the station server 200 returned from the inquiry response server 400 in response to the information request, and performs master update, that is, restoration of a disk image. A message asking whether to execute it is read out from the HDD 101 and displayed (s104), and the user's intention is finally confirmed.

  If the answer from the user obtained by the input device 105 indicates “master update not executed” (s105: n), the process is terminated. On the other hand, if it indicates “execution of master update” (s105: y), the update activation unit 111 stores a MAC address that is a unique ID from the NIC 107, a predetermined file of the HDD 101 (a model number of the security PC 100 is stored in advance). The device ID (such as the model number of the security PC 100) is acquired from the setting file) (s106).

  Further, the update activation unit 111 creates a session name “RK1 + 1B27F8” including the MAC address (for example, “1B27F8”) of the NIC 107 and its own device ID (for example, “RK1”), and designates the session name The session establishment request is transmitted to the IP address of the station server 200 obtained in step s101 (s107).

  On the other hand, the master transmission unit 210 of the station server 200 receives the session establishment request from the security PC 100, performs session establishment processing according to the session establishment request, and then transmits a session establishment notification to the security PC 100 (s108). ). Thereafter, the master transmission unit 210 of the station server 200 enters a state of waiting for a request from the security PC 100 using the unique ID and the device ID as a session name. Further, the master transmission unit 210 identifies a request from the security PC 100 with the session name “RK1 + 1B27F8”. Further, a master, that is, a disk image that is read from the HDD 201 and transmitted to the security PC 100 by the device ID “RK1” is determined.

  On the other hand, the update activation unit 111 of the security PC 100 receives the session establishment notification from the station server 200 and changes the setting of the active partition in the master boot record 137 to the second disk partition 55 (s109). Further, the update activation unit 111 sets the second disk partition 55 to active (bootable) in the master boot record 137, and executes reboot (s110).

  Subsequently, the restore processing unit 112 of the security PC 100 starts the second operating system (for example, DOS) 136b by executing the reboot and automatically executes the backup program 139 (for example, “Autoexec.bat”). (Automatic execution by) (s111).

  Further, the restore processing unit 112 acquires the MAC address of the NIC 107 and its own device ID by the backup program 139 in the same manner as in the step s106, and the MAC address “1B27F8” of the NIC 107 and its own device ID “RK1”. The session name “RK1 + 1B27F8” including “” is created, and an update request designating the session name is transmitted to the station server 200 (s112).

  On the other hand, the master transmission unit 210 of the station server 200 enters the request waiting state from the security PC 100 with the session name “RK1 + 1B27F8”. The update request is received from the security PC 100, and the disk image 250 is extracted from the image table 225 of the HDD 201 based on the device ID “RK1” included in the update request (session name) (s113). The master transmission unit 210 transmits the disk image 250 to the security PC 100 (s114). Of course, the station server 200 may have a multicast server function, receive update requests from a plurality of security PCs 100, and perform disk image distribution to each of the security PCs 100. At this time, distribution may be performed in parallel to each security PC 100.

  On the other hand, the restore processing unit 112 of the security PC 100 receives the disk image 250 from the station server 200 and restores the first disk partition 50 with the disk image 250 by the backup program 139 (s115). ). After the restoration is completed, the restore processing unit 112 sets the first disk partition 50 to active (bootable) in the master boot record 137 and reboots (s116). After this reboot, the security PC 100 is activated with the new master, that is, the updated first disk partition 50.

  According to the present invention, update processing in a thin client can be managed efficiently and at low cost.

  As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.

10 Rewriting System 50 of Thin Client Master First Disk Partition 55 Second Disk Partition 100 Security PC (Thin Client)
101, 201, 301, 401 HDD (Hard Disk Drive)
102, 202, 302, 402 Program 103, 203, 303, 403 RAM (Random Access Memory)
104, 204, 304, 404 CPU (Central Processing Unit)
105, 205, 305, 405 Input device 106, 206, 306, 406 Output device 107, 207, 307, 407 Communication device, NIC (Network Interface Card)
108, 208, 308, 408 Flash ROM
110 Request transmission unit 111 Update activation unit 112 Restore processing unit 125 IP address 135, 235 BIOS of inquiry corresponding server
136a, 136b, 236 OS
137 Master Boot Record 139 Backup Program 140 Network, LAN
144 USB port 200 Station server (update server)
210 Master transmission unit 225 Image table 250 Disk image 300 Distribution server 400 Inquiry corresponding server 410 Address notification unit 420 Station server IP address 425 Address table (address list)

Claims (3)

A communication device that communicates with other devices via a network;
A first disk partition for storing at least a first operating system and a second disk partition for storing a second operating system and a backup program are set, and an address on the network of the inquiry corresponding server is stored A storage device;
In response to a user instruction received by the input device, a request transmission unit that reads the address of the inquiry response server from the storage device and transmits an information request of the server for update to the corresponding address;
In response to the information request, an update activation unit that receives the address of the update server from the inquiry response server, changes the setting of the active partition in the master boot record to the second disk partition, and executes a reboot;
The second operating system is started by executing the reboot, the backup program is executed, an update request including its own device ID is transmitted to the address of the update server, and the update server A thin client having a restore processing unit that receives a disk image corresponding to the device ID and executes restoration of the first disk partition with the disk image by the backup program;
A communication device that communicates with other devices via a network;
A storage device for storing a list of addresses related to each update server determined according to each address on the network;
The information request is received from the thin client, the address of the thin client included in the information request is checked against the address list of the storage device, and the address of the update server corresponding to the address of the thin client is specified. An inquiry response server having an address notification unit that returns the address specified in step 1 to the thin client;
A communication device that communicates with other devices via a network;
A storage device for storing a disk image for update in association with the device ID of the thin client;
A master transmission unit that receives the update request from the thin client, extracts a disk image from the storage device based on a device ID included in the update request, and transmits the disk image to the thin client; Server for
A thin client master rewriting system characterized by including: In response to a user instruction received by the input device, the update activation unit of the thin client transmits a session establishment request including the unique ID of the communication device and its own device ID to the update server, and responds to the session establishment request. Session update notification from the update server, change the active partition setting in the master boot record to the second disk partition, execute the reboot,
The restore processing unit of the thin client starts the second operating system by executing the reboot, executes the backup program, and an update request using the unique ID of the communication device and its own device ID as a session name To the update server, receives a disk image corresponding to the unique ID and device ID of the communication device from the update server, and restores the first disk partition with the disk image by the backup program And
The master transmission unit of the update server receives the session establishment request from the thin client, enters a request waiting state from the thin client with the unique ID and the device ID as a session name, and then An update request with a unique ID and a device ID as a session name is received from the thin client, a disk image is extracted from the storage device based on the device ID included in the update request, and the disk image is transmitted to the thin client. ,
The thin client master rewriting system according to claim 1. A communication device that communicates with another device via a network, a first disk partition that stores at least a first operating system, and a second disk partition that stores a second operating system and a backup program are set, A thin client having a storage device in which an address on the inquiry corresponding server network is stored,
In response to a user instruction received by the input device, the address of the inquiry response server is read from the storage device, and an update server information request is transmitted to the corresponding address.
In response to the information request, the address of the server for update is received from the inquiry response server, the setting of the active partition in the master boot record is changed to the second disk partition, and the reboot is executed.
The second operating system is started by executing the reboot, the backup program is executed, an update request including its own device ID is transmitted to the address of the update server, and the update server Receiving a disk image corresponding to the device ID, and performing a restore of the first disk partition with the disk image by the backup program;
An inquiry response server having a communication device that communicates with other devices via a network, and a storage device that stores a list of addresses related to each update server determined according to each address on the network,
The information request is received from the thin client, the address of the thin client included in the information request is checked against the address list of the storage device, and the address of the update server corresponding to the address of the thin client is specified. Return the address specified in step 1 to the thin client,
An update server having a communication device that communicates with another device via a network and a storage device that stores a disk image for update in association with the device ID of the thin client,
Receiving the update request from the thin client, extracting a disk image from the storage device based on a device ID included in the update request, and transmitting the disk image to the thin client;
A thin client master rewriting method characterized by the above.

Images