US20090259792A1 - Remote operation system - Google Patents
Remote operation system Download PDFInfo
- Publication number
- US20090259792A1 US20090259792A1 US12/385,555 US38555509A US2009259792A1 US 20090259792 A1 US20090259792 A1 US 20090259792A1 US 38555509 A US38555509 A US 38555509A US 2009259792 A1 US2009259792 A1 US 2009259792A1
- Authority
- US
- United States
- Prior art keywords
- keyboard
- state
- client
- states
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000005540 biological transmission Effects 0.000 claims abstract description 10
- 230000008859 change Effects 0.000 description 24
- 238000000034 method Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 5
- 230000004913 activation Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
- G06F3/038—Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/02—Input arrangements using manually operated switches, e.g. using keyboards or dials
- G06F3/023—Arrangements for converting discrete items of information into a coded form, e.g. arrangements for interpreting keyboard generated codes as alphanumeric codes, operand codes or instruction codes
Definitions
- the present invention relates to a remote operation system having a server, a KVM (K:keyboard, V:video, M:mouse) switch, and a client.
- KVM K:keyboard, V:video, M:mouse
- one client is connected to a server selected by a user via the KVM switch. Then, when the user of the client operates a keyboard connected to the client to execute key input, a key code is transmitted to the selected server via the KVM switch.
- the server transmits screen data including letters and so on corresponding to the received key code to the client via the KVM switch.
- the screen data of the server is displayed on a monitor connected to the client. Therefore, when the user of the client executes the key input, the user of the client can browse the screen data of the server in which the contents of the key input are reflected, with the monitor connected to the client.
- a state of the keyboard of the client may be not identical with a state of the keyboard of the server. This corresponds to a case where a “Caps Lock” key of the client is on, and a “Caps Lock” key of the server is off, for example. It should be noted that an LED showing a state of the “Caps Lock” key is provided on the keyboard of the client.
- a remote operation system having a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard for operating the server, the KVM switch including: an acquisition portion that acquires a state of the second keyboard; and the client including: a reception portion that receives a state of the first keyboard from the first keyboard, and the state of the second keyboard from the KVM switch; a determination portion that determines whether the state of the first keyboard is identical with the state of the second keyboard; and a transmission portion that transmits information which makes the state of the first keyboard identical with the state of the second keyboard, to the first keyboard when the state of the first keyboard is not identical with the state of the second keyboard.
- a remote operation system having a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard for operating the server, the client including: a first reception portion that receives a state of the first keyboard; and a first transmission portion that transmits the state of the first keyboard to the KVM switch; and the KVM switch including: a second reception portion that receives the state of the first keyboard from the client; a determination portion that determines whether the state of the second keyboard is identical with the state of the first keyboard; and a second transmission portion that transmits information which makes the state of the second keyboard identical with the state of the first keyboard, to the server when the state of the second keyboard is not identical with the state of the first keyboard.
- FIG. 1 is a schematic diagram showing the configuration of a remote operation system according to a first embodiment
- FIG. 2A is a block diagram showing the hardware configuration of a server 1 ;
- FIG. 2B is a block diagram showing the hardware configuration of a client 4 ;
- FIG. 3 is a diagram showing the apparent configuration of a keyboard 8 ;
- FIGS. 4A and 4B are flowcharts showing a process executed with the remote operation system
- FIG. 5 is a diagram showing a format of a packet of information indicative of an LED state request command and states of LEDs.
- FIGS. 6A and 6B are flowcharts showing a process executed with the remote operation system according to a second embodiment.
- FIG. 1 is a schematic diagram showing the configuration of a remote operation system according to a first embodiment.
- a remote system 1000 includes a server 1 , a KVM switch 2 , and a client 4 .
- the server 1 is connected to the KVM switch 2 via cables 13 to 15 .
- the client 4 is connected to the KVM switch 2 via a network 3 and LAN cables 12 .
- the remote system 1000 includes the server 1 and the client 4 in FIG. 1 , the remote system 1000 may include a plurality of servers and clients.
- the server 1 includes: a keyboard interface (I/F) 101 a to which the cable 13 is connected; a mouse interface (I/F) 101 b to which the cable 14 is connected; a monitor interface (I/F) 101 c to which the cable 15 is connected; and a control unit 102 that controls the entire server 1 .
- the control unit 102 includes an OS (operating system) 103 .
- the OS 103 is Windows (registered trademark), UNIX (registered trademark), MAC OS (registered trademark), or the like, the Windows is mainly used for the present embodiment.
- Screen data of the server 1 is transmitted to the KVM switch 2 via the monitor I/F 101 c and the cable 15 .
- the KVM switch 2 is an IP-KVM switch connectable to the client 4 via the network 3 .
- the KVM switch 2 includes: a keyboard interface (I/F) 201 a that transmits a key code to the server 1 ; a mouse interface (I/F) 201 b that transmits mouse data to the server 1 ; a monitor interface (I/F) 201 c that receives the screen data from the server 1 ; a communication I/F 202 that receives the key code of a keyboard 8 from the client 4 , and transmits the screen data from the server 1 to the client 4 ; a control unit 203 (an acquisition portion) that executes various kinds of processes, and controls the entire KVM switch 2 including the keyboard I/F 201 a, the mouse I/F 201 b, the monitor I/F 201 c, and the communication I/F 202 ; and a memory 204 that stores various kinds of data.
- a keyboard interface (I/F) 201 a that transmits a key code to the
- the control unit 203 is composed of a microcomputer, and the memory 204 is composed of a hard disk drive or a nonvolatile memory.
- a keyboard 5 , a mouse 6 , and a monitor 7 are connected to the control unit 203 , and used by a user of the server 1 side, i.e., a local side.
- the key code from the keyboard 5 and the mouse data of the mouse 6 are transmitted to the server 1 via the keyboard I/F 201 a and the mouse I/F 201 b, respectively.
- the screen data of the server 1 is displayed on the monitor 7 .
- the control unit 203 correspond to an acquisition portion, a second reception portion, a determination portion, and a second transmission portion.
- the number of keyboard I/Fs 201 a, the number of mouse I/Fs 201 b, the number of monitor I/Fs 201 c, and the number of communication I/Fs 202 are not limited to one, and a plurality of keyboard I/Fs 201 a, a plurality of mouse I/Fs 201 b, a plurality of monitor I/Fs 201 c, and a plurality of communication I/Fs 202 may be provided.
- the plurality of keyboard I/Fs 201 a, the plurality of mouse I/Fs 201 b, the plurality of monitor I/Fs 201 c, and the plurality of communication I/Fs 202 are connected to a plurality of servers and clients.
- the client 4 includes: a communication I/F 401 that transmits the key code from the keyboard 8 and mouse data from a mouse 9 to the KVM switch 2 via the network 3 , and receives the screen data of the server 1 from the KVM switch 2 via the network 3 ; a keyboard I/F 402 that receives the key code from the keyboard 8 ; a mouse I/F 403 that receives the mouse data from the mouse 9 ; a monitor I/F 404 that outputs the screen data of the server 1 to a monitor 10 ; and a control unit 405 that controls the entire client 4 .
- the control unit 405 corresponds to a reception portion, a determination portion, a transmission portion, a first reception portion, and a first transmission portion.
- the control unit 405 includes: an OS 406 that includes a plurality of device drivers controlling the keyboard 8 , the mouse 9 , and the monitor 10 ; and a VNC client (i.e., an application for remote operation) 407 that causes the monitor 10 to display the screen data of the server 1 , and executes the remote operation.
- an OS 406 that includes a plurality of device drivers controlling the keyboard 8 , the mouse 9 , and the monitor 10 ; and a VNC client (i.e., an application for remote operation) 407 that causes the monitor 10 to display the screen data of the server 1 , and executes the remote operation.
- VNC client i.e., an application for remote operation
- the screen data of the server 1 is displayed on the monitor 10 via the VNC client 407 .
- the OS 406 receives the key code from the keyboard I/F 402 , and outputs the key code to the VNC client 407 .
- the OS 406 receives the mouse data from the mouse I/F 403 , and outputs coordinate values of a mouse cursor to the VNC client 407 .
- the OS 406 receives the key code and the coordinate values of the mouse cursor from the VNC client 407 , and transmits the key code and the coordinate values to the communication I/F 401 .
- FIG. 2A is a block diagram showing the hardware configuration of the server 1
- FIG. 2B is a block diagram showing the hardware configuration of the client 4 .
- the server 1 includes: a keyboard I/F 101 a; a mouse I/F 101 b; a monitor I/F 101 c; a CPU 121 that controls the entire server 1 ; a ROM 122 that stores a control program; a RAM 123 that functions as a working area; a hard disk drive (HDD) 124 that stores an exclusive device driver, a mouse class driver, an OS, and various kinds of information and programs; a PS/2 I/F 125 ; and a USB (Universal Serial Bus) I/F 126 that is connected to USB devices, not shown.
- a keyboard I/F 101 a a mouse I/F 101 b
- a monitor I/F 101 c includes: a CPU 121 that controls the entire server 1 ; a ROM 122 that stores a control program; a RAM 123 that functions as a working area; a hard disk drive (HDD) 124 that stores an exclusive device driver, a mouse class driver, an OS, and various kinds of information and programs; a
- the CPU 121 is connected to the keyboard I/F 101 a, the mouse I/F 101 b, the monitor I/F 101 c, the ROM 122 , the RAM 123 , the HDD 124 , the PS/2 I/F 125 , and the USB I/F 126 via a system bus 127 .
- the CPU 121 , the ROM 122 , the RAM 123 and the HDD 124 correspond to the control unit 102 , and the CPU 121 properly reads out the OS 103 from the HDD 124 and starts up the OS 103 , so that the process executed with the OS 103 is achieved.
- the client 4 includes: a communication I/F 401 ; a keyboard I/F 402 ; a mouse I/F 403 ; a monitor I/F 404 ; a CPU 421 that controls the entire client 4 ; a ROM 422 that stores a control program; a RAM 423 that functions as a working area; a hard disk drive (HDD) 424 that stores an OS, an application for remote operation, and various kinds of information and programs; and a USB I/F 425 that is connected to USB devices, not shown.
- a communication I/F 401 a communication I/F 401 ; a keyboard I/F 402 ; a mouse I/F 403 ; a monitor I/F 404 ; a CPU 421 that controls the entire client 4 ; a ROM 422 that stores a control program; a RAM 423 that functions as a working area; a hard disk drive (HDD) 424 that stores an OS, an application for remote operation, and various kinds of information and programs; and
- the CPU 421 is connected to the communication I/F 401 , the keyboard I/F 402 , the mouse I/F 403 , the monitor I/F 404 , the ROM 422 , the RAM 423 , the HDD 424 , and the USB I/F 425 via a system bus 426 .
- the CPU 421 , the ROM 422 , the RAM 423 and the HDD 424 correspond to the control unit 405 , and the CPU 421 properly reads out the OS 406 or the VNC client 407 from the HDD 424 and starts up the OS 406 or the VNC client 407 , so that the process executed with the OS 406 or the VNC client 407 is achieved.
- FIG. 3 is a diagram showing the apparent configuration of the keyboard 8 .
- the keyboard 8 includes an alphabet input unit 301 , a cursor key input unit 302 , a ten key input unit 303 , a function key input unit 304 , a special key input unit 305 , and an LED lighting unit 306 .
- a “Num Lock” key is included in the ten key input unit 303 .
- a “Caps Lock” key is included in the alphabet input unit 301 .
- A“Scroll Lock” key is included in the special key input unit 305 .
- the LED lighting unit 306 includes: an LED lighting unit 306 a showing an on/off state of the “Num Lock” key; an LED lighting unit 306 b showing an on/off state of the “Caps Lock” key; and an LED lighting unit 306 c showing an on/off state of the “Scroll Lock” key.
- Each of the LED lighting units 306 a to 306 c has an LED (light-emitting diode), and the on/off state of each key is represented by the lighting/lights-out of corresponding LED.
- the configuration of the keyboard 5 is the same as that of the keyboard 8 , and hence a description thereof is omitted.
- the LED lighting units 306 a to 306 c correspond to a plurality of lighting portions.
- the on/off control of the LED lighting units 306 a to 306 c is executed by the CPU 421 .
- the on/off control of the LED lighting units 306 a to 306 c on the keyboard 5 is executed by the OS 103 of the server 1 via the control unit 203 of the KVM switch 2 .
- FIGS. 4A and 4B are flowcharts showing a process executed with the remote operation system.
- the CPU 121 properly reads out the OS 406 or the VNC client 407 from the HDD 424 , and starts up the OS 406 or the VNC client 407 , so that the process executed with the OS 406 or the VNC client 407 is achieved.
- the control unit 203 of the KVM switch 2 acquires information indicative of keyboard states of the server 1 as an initial setting, and stores the information into the memory 204 (step S 1 ).
- the information indicative of the keyboard states of the server 1 is information indicative of the states of the LEDs included in the keyboard (i.e., keyboard 5 ) of the server 1 , and shows the on/off states of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key.
- the VNC client 407 transmits an LED state request command to the OS 406 (step S 2 ).
- the OS 406 receives the LED state request command (step S 3 ), and transmits the information indicative of the states of the LEDs included in the LED lighting units 306 a to 306 c, to the VNC client 407 (step S 4 ).
- FIG. 5 shows a format of a packet of information indicative of the LED state request command and the states of the LEDs.
- the packet in FIG. 5 is composed of a data ID unit 501 in one byte and an LED state unit 502 in one byte.
- the VNC client 407 receives the information indicative of the states of the LEDs from the OS 406 (step S 5 ), and stores the information indicative of the states of the LEDs into the HDD 424 (step S 6 ). By the procedures from step S 2 to step S 6 , the VNC client 407 acquires the state of each LED, i.e., the state of the keyboard 8 .
- the VNC client 407 transmits the LED state request command to the KVM switch 2 (step S 7 ).
- the control unit 203 of the KVM switch 2 receives the LED state request command (step S 8 ), and transmits the information indicative of the states of the LEDs included in the keyboard of the server 1 , stored into the memory 204 , to the VNC client 407 (step S 9 ).
- the VNC client 407 receives the information indicative of the states of the LEDs from the KVM switch 2 (step S 10 ), and stores the information indicative of the states of the LEDs into the memory 424 (step S 11 ). By the procedures from step S 8 to step S 11 , the VNC client 407 acquires the state of each LED, i.e., the state of the keyboard 5 .
- the VNC client 407 determines whether the information indicative of the states of the LEDs included in the keyboard 8 received from the OS 406 is identical with the information indicative of the states of the LEDs included in the keyboard 5 received from the KVM switch 2 (step S 12 ).
- step S 12 When the answer to the determination of step S 12 is “YES”, the process is terminated.
- the VNC client 407 transmits an LED state change key for changing the states of the LEDs on the keyboard 8 , to the OS 406 (step S 13 ).
- the LED state change key means codes of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key.
- the LED state change key is transmitted in order to make the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key of the keyboard 8 identical with those of the keyboard 5 , i.e., to make the keyboard states of the client identical with those of the server.
- the codes to be transmitted as the LED state change key is automatically or manually changed by the VNC client 407 depending on a type of the OS 406 .
- the OS 406 is Japanese version Windows (registered trademark) (i.e., all device drivers and optional languages, etc. are set to a Japanese environment)
- the VNC client 407 transmits the codes of a “Shift” key and the “Caps Lock” key to the OS 406 .
- the VNC client 407 transmits only the code of the “Caps Lock” key to the OS 406 .
- the OS 406 receives the LED state change key from the VNC client 407 (step S 14 ), and transmits the notification of the LED status change to the keyboard 8 (step S 15 ).
- the keyboard 8 receives the notification of the LED status change (step S 16 ), and changes the state of each LED based on the notification of the LED status change (step S 17 ). Then, the present process is terminated.
- the VNC client 407 When the activation of the VNC client 407 is terminated (i.e., termination time of the remote control), the VNC client 407 returns the current states of the LEDs on the keyboard 8 to the states of the LEDs on the keyboard 8 received at the time of start of the remote control. Thereby, when another application is operated by the keyboard 8 , it is possible to prevent a gap by the operation of the application from occurring.
- the KVM switch 2 acquires the states of the keyboard 5
- the control unit 405 of the client 4 receives the states of the keyboard 8 from the OS 406 and the states of the keyboard 5 from the KVM switch 2 , and determines whether the states of the keyboard 8 are identical with those of the keyboard 5 .
- the VNC client 407 transmits the information (i.e., key code) which makes the states of the keyboard 8 identical with those of the keyboard 5 , to the OS 406 .
- the states of the keyboard 8 are changed by the control of the OS 406 , so that the OS 406 transmits the notification of the LED status change to the keyboard 8 .
- the VNC client may transmit the LED state change key to the OS 406 and the KVM switch 2 based on preset states of the LEDs (e.g. the “Num Lock” key: ON, the “Caps Lock” key: OFF, and the “Scroll Lock” key: OFF), and change the states of the LED lighting units 306 a to 306 c included in the respective keyboards 5 and 8 . Thereby, the user can execute the key input in a predetermined state.
- preset states of the LEDs e.g. the “Num Lock” key: ON, the “Caps Lock” key: OFF, and the “Scroll Lock” key: OFF
- the states of the LEDs on the keyboard 8 of the client 4 is changed according to the states of the LEDs on the keyboard 5 of the server 1 .
- the states of the LEDs on the keyboard 5 of the server 1 is changed according to the states of the LEDs on the keyboard 8 of the client 4 .
- the configuration of the remote operation system according to the second embodiment is the same as that of the remote operation system according to the first embodiment, and hence a description thereof is omitted.
- FIGS. 6A and 6B are flowcharts showing a process executed with the remote operation system according to the second embodiment.
- the CPU 121 properly reads out the OS 406 or the VNC client 407 from the HDD 424 , and starts up the OS 406 or the VNC client 407 , so that the process executed with the OS 406 or the VNC client 407 is achieved.
- the control unit 203 of the KVM switch 2 acquires information indicative of keyboard states of the server 1 as an initial setting, and stores the information into the memory 204 (step S 21 ).
- the information indicative of the keyboard states of the server 1 is information indicative of the states of the LEDs included in the keyboard (i.e., keyboard 5 ) of the server 1 , and shows the on/off states of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key.
- the VNC client 407 transmits an LED state request command to the OS 406 (step S 22 ).
- the OS 406 receives the LED state request command (step S 23 ), and transmits the information indicative of the states of the LEDs included in the LED lighting units 306 a to 306 c, to the VNC client 407 (step S 24 ).
- a packet of information indicative of the LED state request command and the states of the LEDs is the same as the packet in FIG. 5 .
- the VNC client 407 receives the information indicative of the states of the LEDs included in the keyboard 8 from the OS 406 (step S 25 ), and stores the information indicative of the states of the LEDs into the HDD 424 (step S 26 ). By the procedures from step S 22 to step S 26 , the VNC client 407 acquires the state of each LED, i.e., the state of the keyboard 8 .
- the VNC client 407 transmits the information indicative of the states of the LEDs included in the keyboard 8 to the KVM switch 2 (step S 27 ).
- the control unit 203 of the KVM switch 2 receives the information indicative of the states of the LEDs included in the keyboard 8 (step S 28 ).
- the control unit 203 determines whether the information indicative of the states of the LEDs included in the keyboard 5 stored into the memory 204 is identical with the information indicative of the states of the LEDs included in the keyboard 8 received from the OS 406 (step S 29 ).
- step S 29 When the answer to the determination of step S 29 is “YES”, the process is terminated.
- the control unit 203 transmits an LED state change key for changing the states of the LEDs on the keyboard 5 , to the OS 103 of the server 1 (step S 30 ).
- the LED state change key means codes of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key.
- the LED state change key is transmitted in order to make the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key of the keyboard 5 identical with those of the keyboard 8 , i.e., to make the keyboard states of the server identical with those of the client.
- the codes to be transmitted as the LED state change key is automatically or manually changed by the control unit 203 depending on a type of the OS 103 .
- the OS 103 is Japanese version Windows (registered trademark) (i.e., all device drivers and optional languages, etc. are set to a Japanese environment)
- the control unit 203 transmits the codes of a “Shift” key and the “Caps Lock” key to the OS 103 .
- the OS 103 is English version Windows (registered trademark)
- the state of the LED of the “Caps Lock” key is changed, the control unit 203 transmits only the code of the “Caps Lock” key to the OS 103 .
- the OS 103 receives the LED state change key from the KVM switch 2 (step S 31 ), changes information indicative of the states of the LEDs stored into the OS 103 (step S 32 ), and transmits the notification of the LED status change to the control unit 203 of the KVM switch 2 (step S 33 ).
- the control unit 203 receives the notification of the LED status change (step S 34 ), and transmits the notification of the LED status change to the keyboard 5 (step S 35 ).
- the keyboard 5 receives the notification of the LED status change (step S 36 ), and changes the state of each LED based on the notification of the LED status change (step S 37 ). Then, the present process is terminated.
- the control unit 102 of the server 1 When the activation of the VNC client 407 is terminated (i.e., termination time of the remote control), the control unit 102 of the server 1 returns the current states of the LEDs on the keyboard 5 to the states of the LEDs on the keyboard 5 received at the time of start of the remote control. Thereby, when another application is operated by the keyboard 5 , it is possible to prevent a gap by the operation of the application from occurring.
- the client 4 receives the states of the keyboard 8 , and transmits the states of the keyboard 8 to the KVM switch 2 .
- the KVM switch 2 receives the states of the keyboard 8 from the client 4 , acquires the states of the keyboard 5 , and determines whether the states of the keyboard 5 is identical with those of the keyboard 8 .
- the KVM switch 2 transmits the information which makes the states of the keyboard 5 identical with those of the keyboard 8 , to the OS 103 of the server 1 . Thereby, the states of the keyboard 5 are changed, and the OS 103 transmits the notification of the LED status change to the keyboard 5 via the control unit 203 of the KVM switch 2 .
- the KVM switch 2 may make the states of the keyboard 5 identical with preset states of the LEDs (e.g. the “Num Lock” key: ON, the “Caps Lock” key: OFF, and the “Scroll Lock” key: OFF), transmit the LED state change key to the OS 406 based on the preset states of the LEDs, and change the states of the LED lighting units 306 a to 306 c included in the respective keyboards 5 and 8 . Thereby, the user can execute the key input in a predetermined state.
- preset states of the LEDs e.g. the “Num Lock” key: ON, the “Caps Lock” key: OFF, and the “Scroll Lock” key: OFF
- Recording media on which the software programs for realizing the functions of the server 1 , the KVM switch 2 and the client 4 are recorded may be supplied to the server 1 , the KVM switch 2 and the client 4 , respectively.
- Each of the control units in the server 1 , the KVM switch 2 and the client 4 may read and execute the corresponding program recorded on each recording media. In this manner, the same effects as those of the above-described first and second embodiments can be achieved.
- Each of the recording media for providing the programs may be a CD-ROM, a DVD, or a SD card, for example.
- control units in the server 1 , the KVM switch 2 and the client 4 may execute the respective software programs for realizing the functions of the server 1 , the KVM switch 2 and the client 4 . In this manner, the same effects as those of the above-described first and second embodiments can also be achieved.
Abstract
A remote operation system has a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard, the KVM switch including: an acquisition portion that acquires a state of the second keyboard; and the client including: a reception portion that receives a state of the first keyboard, and the state of the second keyboard from the KVM switch; a determination portion that determines whether the state of the first keyboard is identical with the state of the second keyboard; and a transmission portion that transmits information which makes the state of the first keyboard identical with the state of the second keyboard, to the first keyboard when the state of the first keyboard is not identical with the state of the second keyboard.
Description
- 1. Field of the Invention
- The present invention relates to a remote operation system having a server, a KVM (K:keyboard, V:video, M:mouse) switch, and a client.
- 2. Description of the Related Art
- Conventionally, there has been known a system which includes a plurality of clients, a plurality of servers, a KVM switch switching communication between the clients and the servers (see Japanese Patent Application Publication No. 2003-534685).
- In this type of system, one client is connected to a server selected by a user via the KVM switch. Then, when the user of the client operates a keyboard connected to the client to execute key input, a key code is transmitted to the selected server via the KVM switch. The server transmits screen data including letters and so on corresponding to the received key code to the client via the KVM switch. The screen data of the server is displayed on a monitor connected to the client. Therefore, when the user of the client executes the key input, the user of the client can browse the screen data of the server in which the contents of the key input are reflected, with the monitor connected to the client.
- However, when the user of the client starts a remote operation, a state of the keyboard of the client may be not identical with a state of the keyboard of the server. This corresponds to a case where a “Caps Lock” key of the client is on, and a “Caps Lock” key of the server is off, for example. It should be noted that an LED showing a state of the “Caps Lock” key is provided on the keyboard of the client.
- When the state of the keyboard of the client is not identical with the state of the keyboard of the server, and the user of the client executes the key input, input letters are different from letters displayed as the screen data of the server, thereby impairing usability. For example, when the “Caps Lock” key of the client is on, and the user of the client inputs a letter key of the alphabet, the user of the client expects that a capital letter of the alphabet will be displayed on the monitor. However, when the “Caps Lock” key of the server is off, a lower-case letter of the alphabet is displayed as the screen data of the server, and hence confusion is given to the user.
- It is an object of the present invention to provide a remote operation system that can avoid key input that a user does not intend.
- According to an aspect of the present invention, there is provided a remote operation system having a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard for operating the server, the KVM switch including: an acquisition portion that acquires a state of the second keyboard; and the client including: a reception portion that receives a state of the first keyboard from the first keyboard, and the state of the second keyboard from the KVM switch; a determination portion that determines whether the state of the first keyboard is identical with the state of the second keyboard; and a transmission portion that transmits information which makes the state of the first keyboard identical with the state of the second keyboard, to the first keyboard when the state of the first keyboard is not identical with the state of the second keyboard.
- With the above arrangement, it is possible to make the state of the keyboard of the client identical with that of the keyboard of the server, and avoid the key input that the user does not intend.
- According to another aspect of the present invention, there is provided a remote operation system having a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard for operating the server, the client including: a first reception portion that receives a state of the first keyboard; and a first transmission portion that transmits the state of the first keyboard to the KVM switch; and the KVM switch including: a second reception portion that receives the state of the first keyboard from the client; a determination portion that determines whether the state of the second keyboard is identical with the state of the first keyboard; and a second transmission portion that transmits information which makes the state of the second keyboard identical with the state of the first keyboard, to the server when the state of the second keyboard is not identical with the state of the first keyboard.
- With the above arrangement, it is possible to make the state of the keyboard of the client identical with that of the keyboard of the server, and avoid the key input that the user does not intend.
- Preferred embodiments of the present invention will be described in detail with reference to the following drawings, wherein:
-
FIG. 1 is a schematic diagram showing the configuration of a remote operation system according to a first embodiment; -
FIG. 2A is a block diagram showing the hardware configuration of aserver 1; -
FIG. 2B is a block diagram showing the hardware configuration of aclient 4; -
FIG. 3 is a diagram showing the apparent configuration of akeyboard 8; -
FIGS. 4A and 4B are flowcharts showing a process executed with the remote operation system; -
FIG. 5 is a diagram showing a format of a packet of information indicative of an LED state request command and states of LEDs; and -
FIGS. 6A and 6B are flowcharts showing a process executed with the remote operation system according to a second embodiment. - A description will now be given, with reference to the accompanying drawings, of an embodiment of the present invention.
-
FIG. 1 is a schematic diagram showing the configuration of a remote operation system according to a first embodiment. - In
FIG. 1 , aremote system 1000 includes aserver 1, aKVM switch 2, and aclient 4. Theserver 1 is connected to theKVM switch 2 viacables 13 to 15. Theclient 4 is connected to theKVM switch 2 via a network 3 andLAN cables 12. Although theremote system 1000 includes theserver 1 and theclient 4 inFIG. 1 , theremote system 1000 may include a plurality of servers and clients. - The
server 1 includes: a keyboard interface (I/F) 101 a to which thecable 13 is connected; a mouse interface (I/F) 101 b to which thecable 14 is connected; a monitor interface (I/F) 101 c to which thecable 15 is connected; and acontrol unit 102 that controls theentire server 1. Thecontrol unit 102 includes an OS (operating system) 103. Although the OS 103 is Windows (registered trademark), UNIX (registered trademark), MAC OS (registered trademark), or the like, the Windows is mainly used for the present embodiment. Screen data of theserver 1 is transmitted to theKVM switch 2 via the monitor I/F 101 c and thecable 15. - The
KVM switch 2 is an IP-KVM switch connectable to theclient 4 via the network 3. TheKVM switch 2 includes: a keyboard interface (I/F) 201 a that transmits a key code to theserver 1; a mouse interface (I/F) 201 b that transmits mouse data to theserver 1; a monitor interface (I/F) 201 c that receives the screen data from theserver 1; a communication I/F 202 that receives the key code of akeyboard 8 from theclient 4, and transmits the screen data from theserver 1 to theclient 4; a control unit 203 (an acquisition portion) that executes various kinds of processes, and controls theentire KVM switch 2 including the keyboard I/F 201 a, the mouse I/F 201 b, the monitor I/F 201 c, and the communication I/F 202; and amemory 204 that stores various kinds of data. Thecontrol unit 203 is composed of a microcomputer, and thememory 204 is composed of a hard disk drive or a nonvolatile memory. Akeyboard 5, amouse 6, and amonitor 7 are connected to thecontrol unit 203, and used by a user of theserver 1 side, i.e., a local side. The key code from thekeyboard 5 and the mouse data of themouse 6 are transmitted to theserver 1 via the keyboard I/F 201 a and the mouse I/F 201 b, respectively. The screen data of theserver 1 is displayed on themonitor 7. It should be noted that thecontrol unit 203 correspond to an acquisition portion, a second reception portion, a determination portion, and a second transmission portion. - It should be noted that the number of keyboard I/
Fs 201 a, the number of mouse I/Fs 201 b, the number of monitor I/Fs 201 c, and the number of communication I/Fs 202 are not limited to one, and a plurality of keyboard I/Fs 201 a, a plurality of mouse I/Fs 201 b, a plurality of monitor I/Fs 201 c, and a plurality of communication I/Fs 202 may be provided. The plurality of keyboard I/Fs 201 a, the plurality of mouse I/Fs 201 b, the plurality of monitor I/Fs 201 c, and the plurality of communication I/Fs 202 are connected to a plurality of servers and clients. - The
client 4 includes: a communication I/F 401 that transmits the key code from thekeyboard 8 and mouse data from amouse 9 to theKVM switch 2 via the network 3, and receives the screen data of theserver 1 from theKVM switch 2 via the network 3; a keyboard I/F 402 that receives the key code from thekeyboard 8; a mouse I/F 403 that receives the mouse data from themouse 9; a monitor I/F 404 that outputs the screen data of theserver 1 to amonitor 10; and acontrol unit 405 that controls theentire client 4. It should be noted that thecontrol unit 405 corresponds to a reception portion, a determination portion, a transmission portion, a first reception portion, and a first transmission portion. - The
control unit 405 includes: anOS 406 that includes a plurality of device drivers controlling thekeyboard 8, themouse 9, and themonitor 10; and a VNC client (i.e., an application for remote operation) 407 that causes themonitor 10 to display the screen data of theserver 1, and executes the remote operation. - The screen data of the
server 1 is displayed on themonitor 10 via the VNCclient 407. The OS 406 receives the key code from the keyboard I/F 402, and outputs the key code to the VNCclient 407. The OS 406 receives the mouse data from the mouse I/F 403, and outputs coordinate values of a mouse cursor to theVNC client 407. In addition, theOS 406 receives the key code and the coordinate values of the mouse cursor from theVNC client 407, and transmits the key code and the coordinate values to the communication I/F 401. -
FIG. 2A is a block diagram showing the hardware configuration of theserver 1, andFIG. 2B is a block diagram showing the hardware configuration of theclient 4. - The
server 1 includes: a keyboard I/F 101 a; a mouse I/F 101 b; a monitor I/F 101 c; aCPU 121 that controls theentire server 1; aROM 122 that stores a control program; aRAM 123 that functions as a working area; a hard disk drive (HDD) 124 that stores an exclusive device driver, a mouse class driver, an OS, and various kinds of information and programs; a PS/2 I/F 125; and a USB (Universal Serial Bus) I/F 126 that is connected to USB devices, not shown. TheCPU 121 is connected to the keyboard I/F 101 a, the mouse I/F 101 b, the monitor I/F 101 c, theROM 122, theRAM 123, theHDD 124, the PS/2 I/F 125, and the USB I/F 126 via asystem bus 127. - It should be noted that the
CPU 121, theROM 122, theRAM 123 and theHDD 124 correspond to thecontrol unit 102, and theCPU 121 properly reads out theOS 103 from theHDD 124 and starts up theOS 103, so that the process executed with theOS 103 is achieved. - The
client 4 includes: a communication I/F 401; a keyboard I/F 402; a mouse I/F 403; a monitor I/F 404; aCPU 421 that controls theentire client 4; aROM 422 that stores a control program; aRAM 423 that functions as a working area; a hard disk drive (HDD) 424 that stores an OS, an application for remote operation, and various kinds of information and programs; and a USB I/F 425 that is connected to USB devices, not shown. TheCPU 421 is connected to the communication I/F 401, the keyboard I/F 402, the mouse I/F 403, the monitor I/F 404, theROM 422, theRAM 423, theHDD 424, and the USB I/F 425 via asystem bus 426. - It should be noted that the
CPU 421, theROM 422, theRAM 423 and theHDD 424 correspond to thecontrol unit 405, and theCPU 421 properly reads out theOS 406 or theVNC client 407 from theHDD 424 and starts up theOS 406 or theVNC client 407, so that the process executed with theOS 406 or theVNC client 407 is achieved. -
FIG. 3 is a diagram showing the apparent configuration of thekeyboard 8. - The
keyboard 8 includes analphabet input unit 301, a cursorkey input unit 302, a tenkey input unit 303, a functionkey input unit 304, a specialkey input unit 305, and anLED lighting unit 306. A “Num Lock” key is included in the tenkey input unit 303. A “Caps Lock” key is included in thealphabet input unit 301. A“Scroll Lock” key is included in the specialkey input unit 305. - The
LED lighting unit 306 includes: anLED lighting unit 306 a showing an on/off state of the “Num Lock” key; anLED lighting unit 306 b showing an on/off state of the “Caps Lock” key; and anLED lighting unit 306 c showing an on/off state of the “Scroll Lock” key. Each of theLED lighting units 306 a to 306 c has an LED (light-emitting diode), and the on/off state of each key is represented by the lighting/lights-out of corresponding LED. It should be noted that the configuration of thekeyboard 5 is the same as that of thekeyboard 8, and hence a description thereof is omitted. It should be noted that theLED lighting units 306 a to 306 c correspond to a plurality of lighting portions. - The on/off control of the
LED lighting units 306 a to 306 c is executed by theCPU 421. The on/off control of theLED lighting units 306 a to 306 c on thekeyboard 5 is executed by theOS 103 of theserver 1 via thecontrol unit 203 of theKVM switch 2. -
FIGS. 4A and 4B are flowcharts showing a process executed with the remote operation system. In the present flowcharts, theCPU 121 properly reads out theOS 406 or theVNC client 407 from theHDD 424, and starts up theOS 406 or theVNC client 407, so that the process executed with theOS 406 or theVNC client 407 is achieved. - First, when the power-on of the
server 1 is detected, thecontrol unit 203 of theKVM switch 2 acquires information indicative of keyboard states of theserver 1 as an initial setting, and stores the information into the memory 204 (step S1). The information indicative of the keyboard states of theserver 1 is information indicative of the states of the LEDs included in the keyboard (i.e., keyboard 5) of theserver 1, and shows the on/off states of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key. - The
VNC client 407 transmits an LED state request command to the OS 406 (step S2). TheOS 406 receives the LED state request command (step S3), and transmits the information indicative of the states of the LEDs included in theLED lighting units 306 a to 306 c, to the VNC client 407 (step S4). - Here,
FIG. 5 shows a format of a packet of information indicative of the LED state request command and the states of the LEDs. The packet inFIG. 5 is composed of adata ID unit 501 in one byte and anLED state unit 502 in one byte. - When the packet is the information indicative of the states of the LEDs, data of “0x01” is input to the
data ID unit 501 and data of any one of “0x01” to “0x07” is input to theLED state unit 502. When the packet is the information indicative of the LED state request command, data of “0x02” is input to thedata ID unit 501 and no data is input to theLED state unit 502. - Referring again to
FIG. 4A , theVNC client 407 receives the information indicative of the states of the LEDs from the OS 406 (step S5), and stores the information indicative of the states of the LEDs into the HDD 424 (step S6). By the procedures from step S2 to step S6, theVNC client 407 acquires the state of each LED, i.e., the state of thekeyboard 8. - The
VNC client 407 transmits the LED state request command to the KVM switch 2 (step S7). Thecontrol unit 203 of theKVM switch 2 receives the LED state request command (step S8), and transmits the information indicative of the states of the LEDs included in the keyboard of theserver 1, stored into thememory 204, to the VNC client 407 (step S9). - The
VNC client 407 receives the information indicative of the states of the LEDs from the KVM switch 2 (step S10), and stores the information indicative of the states of the LEDs into the memory 424 (step S11). By the procedures from step S8 to step S11, theVNC client 407 acquires the state of each LED, i.e., the state of thekeyboard 5. - Next, the
VNC client 407 determines whether the information indicative of the states of the LEDs included in thekeyboard 8 received from theOS 406 is identical with the information indicative of the states of the LEDs included in thekeyboard 5 received from the KVM switch 2 (step S12). - When the answer to the determination of step S12 is “YES”, the process is terminated. On the other hand, when the answer to the determination of step S12 is “NO”, the
VNC client 407 transmits an LED state change key for changing the states of the LEDs on thekeyboard 8, to the OS 406 (step S13). The LED state change key means codes of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key. The LED state change key is transmitted in order to make the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key of thekeyboard 8 identical with those of thekeyboard 5, i.e., to make the keyboard states of the client identical with those of the server. - The codes to be transmitted as the LED state change key is automatically or manually changed by the
VNC client 407 depending on a type of theOS 406. For example, when theOS 406 is Japanese version Windows (registered trademark) (i.e., all device drivers and optional languages, etc. are set to a Japanese environment), and the state of the LED of the “Caps Lock” key is changed, theVNC client 407 transmits the codes of a “Shift” key and the “Caps Lock” key to theOS 406. On the other hand, when theOS 406 is English version Windows (registered trademark), and the state of the LED of the “Caps Lock” key is changed, theVNC client 407 transmits only the code of the “Caps Lock” key to theOS 406. - The
OS 406 receives the LED state change key from the VNC client 407 (step S14), and transmits the notification of the LED status change to the keyboard 8 (step S15). - The
keyboard 8 receives the notification of the LED status change (step S16), and changes the state of each LED based on the notification of the LED status change (step S17). Then, the present process is terminated. - When the activation of the
VNC client 407 is terminated (i.e., termination time of the remote control), theVNC client 407 returns the current states of the LEDs on thekeyboard 8 to the states of the LEDs on thekeyboard 8 received at the time of start of the remote control. Thereby, when another application is operated by thekeyboard 8, it is possible to prevent a gap by the operation of the application from occurring. - According to the present embodiment, the
KVM switch 2 acquires the states of thekeyboard 5, and thecontrol unit 405 of theclient 4 receives the states of thekeyboard 8 from theOS 406 and the states of thekeyboard 5 from theKVM switch 2, and determines whether the states of thekeyboard 8 are identical with those of thekeyboard 5. When the states of thekeyboard 8 are not identical with those of thekeyboard 5, theVNC client 407 transmits the information (i.e., key code) which makes the states of thekeyboard 8 identical with those of thekeyboard 5, to theOS 406. Then, the states of thekeyboard 8 are changed by the control of theOS 406, so that theOS 406 transmits the notification of the LED status change to thekeyboard 8. - Therefore, it is possible to make the states of the keyboard of the client identical with those of the keyboard of the server, and avoid the key input that the user does not intend.
- As a variation example, at the time of start of the remote operation, the VNC client may transmit the LED state change key to the
OS 406 and theKVM switch 2 based on preset states of the LEDs (e.g. the “Num Lock” key: ON, the “Caps Lock” key: OFF, and the “Scroll Lock” key: OFF), and change the states of theLED lighting units 306 a to 306 c included in therespective keyboards - In the above-mentioned first embodiment, the states of the LEDs on the
keyboard 8 of theclient 4 is changed according to the states of the LEDs on thekeyboard 5 of theserver 1. On the contrary, in the present embodiment, the states of the LEDs on thekeyboard 5 of theserver 1 is changed according to the states of the LEDs on thekeyboard 8 of theclient 4. - The configuration of the remote operation system according to the second embodiment is the same as that of the remote operation system according to the first embodiment, and hence a description thereof is omitted.
-
FIGS. 6A and 6B are flowcharts showing a process executed with the remote operation system according to the second embodiment. In the present flowcharts, theCPU 121 properly reads out theOS 406 or theVNC client 407 from theHDD 424, and starts up theOS 406 or theVNC client 407, so that the process executed with theOS 406 or theVNC client 407 is achieved. - First, when the power-on of the
server 1 is detected, thecontrol unit 203 of theKVM switch 2 acquires information indicative of keyboard states of theserver 1 as an initial setting, and stores the information into the memory 204 (step S21). The information indicative of the keyboard states of theserver 1 is information indicative of the states of the LEDs included in the keyboard (i.e., keyboard 5) of theserver 1, and shows the on/off states of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key. - The
VNC client 407 transmits an LED state request command to the OS 406 (step S22). TheOS 406 receives the LED state request command (step S23), and transmits the information indicative of the states of the LEDs included in theLED lighting units 306 a to 306 c, to the VNC client 407 (step S24). A packet of information indicative of the LED state request command and the states of the LEDs is the same as the packet inFIG. 5 . - The
VNC client 407 receives the information indicative of the states of the LEDs included in thekeyboard 8 from the OS 406 (step S25), and stores the information indicative of the states of the LEDs into the HDD 424 (step S26). By the procedures from step S22 to step S26, theVNC client 407 acquires the state of each LED, i.e., the state of thekeyboard 8. - The
VNC client 407 transmits the information indicative of the states of the LEDs included in thekeyboard 8 to the KVM switch 2 (step S27). Thecontrol unit 203 of theKVM switch 2 receives the information indicative of the states of the LEDs included in the keyboard 8 (step S28). - The
control unit 203 determines whether the information indicative of the states of the LEDs included in thekeyboard 5 stored into thememory 204 is identical with the information indicative of the states of the LEDs included in thekeyboard 8 received from the OS 406 (step S29). - When the answer to the determination of step S29 is “YES”, the process is terminated. On the other hand, when the answer to the determination of step S29 is “NO”, the
control unit 203 transmits an LED state change key for changing the states of the LEDs on thekeyboard 5, to theOS 103 of the server 1 (step S30). The LED state change key means codes of the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key. The LED state change key is transmitted in order to make the “Num Lock” key, the “Caps Lock” key, and the “Scroll Lock” key of thekeyboard 5 identical with those of thekeyboard 8, i.e., to make the keyboard states of the server identical with those of the client. - The codes to be transmitted as the LED state change key is automatically or manually changed by the
control unit 203 depending on a type of theOS 103. For example, when theOS 103 is Japanese version Windows (registered trademark) (i.e., all device drivers and optional languages, etc. are set to a Japanese environment), and the state of the LED of the “Caps Lock” key is changed, thecontrol unit 203 transmits the codes of a “Shift” key and the “Caps Lock” key to theOS 103. On the other hand, when theOS 103 is English version Windows (registered trademark), and the state of the LED of the “Caps Lock” key is changed, thecontrol unit 203 transmits only the code of the “Caps Lock” key to theOS 103. - The
OS 103 receives the LED state change key from the KVM switch 2 (step S31), changes information indicative of the states of the LEDs stored into the OS 103 (step S32), and transmits the notification of the LED status change to thecontrol unit 203 of the KVM switch 2 (step S33). - The
control unit 203 receives the notification of the LED status change (step S34), and transmits the notification of the LED status change to the keyboard 5 (step S35). - The
keyboard 5 receives the notification of the LED status change (step S36), and changes the state of each LED based on the notification of the LED status change (step S37). Then, the present process is terminated. - When the activation of the
VNC client 407 is terminated (i.e., termination time of the remote control), thecontrol unit 102 of theserver 1 returns the current states of the LEDs on thekeyboard 5 to the states of the LEDs on thekeyboard 5 received at the time of start of the remote control. Thereby, when another application is operated by thekeyboard 5, it is possible to prevent a gap by the operation of the application from occurring. - According to the present embodiment, the
client 4 receives the states of thekeyboard 8, and transmits the states of thekeyboard 8 to theKVM switch 2. TheKVM switch 2 receives the states of thekeyboard 8 from theclient 4, acquires the states of thekeyboard 5, and determines whether the states of thekeyboard 5 is identical with those of thekeyboard 8. When the states of thekeyboard 5 is not identical with those of thekeyboard 8, theKVM switch 2 transmits the information which makes the states of thekeyboard 5 identical with those of thekeyboard 8, to theOS 103 of theserver 1. Thereby, the states of thekeyboard 5 are changed, and theOS 103 transmits the notification of the LED status change to thekeyboard 5 via thecontrol unit 203 of theKVM switch 2. - Therefore, it is possible to make the states of the keyboard of the client identical with those of the keyboard of the server, and avoid the key input that the user does not intend.
- As a variation example, at the time of start of the remote operation, the
KVM switch 2 may make the states of thekeyboard 5 identical with preset states of the LEDs (e.g. the “Num Lock” key: ON, the “Caps Lock” key: OFF, and the “Scroll Lock” key: OFF), transmit the LED state change key to theOS 406 based on the preset states of the LEDs, and change the states of theLED lighting units 306 a to 306 c included in therespective keyboards - Recording media on which the software programs for realizing the functions of the
server 1, theKVM switch 2 and theclient 4 are recorded may be supplied to theserver 1, theKVM switch 2 and theclient 4, respectively. Each of the control units in theserver 1, theKVM switch 2 and theclient 4 may read and execute the corresponding program recorded on each recording media. In this manner, the same effects as those of the above-described first and second embodiments can be achieved. Each of the recording media for providing the programs may be a CD-ROM, a DVD, or a SD card, for example. - The control units in the
server 1, theKVM switch 2 and theclient 4 may execute the respective software programs for realizing the functions of theserver 1, theKVM switch 2 and theclient 4. In this manner, the same effects as those of the above-described first and second embodiments can also be achieved. - It should be noted that the present invention is not limited to the embodiment, and various modifications may be made to them without departing from the scope of the invention.
- The Present application is based on Japanese Patent Application No. 2008-102775 filed Apr. 10, 2008, the entire disclosure of which is hereby incorporated by reference.
Claims (10)
1. A remote operation system comprising a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard for operating the server,
the KVM switch including:
an acquisition portion that acquires a state of the second keyboard; and
the client including:
a reception portion that receives a state of the first keyboard from the first keyboard, and the state of the second keyboard from the KVM switch;
a determination portion that determines whether the state of the first keyboard is identical with the state of the second keyboard; and
a transmission portion that transmits information which makes the state of the first keyboard identical with the state of the second keyboard, to the first keyboard when the state of the first keyboard is not identical with the state of the second keyboard.
2. The remote operation system as claimed in claim 1 , wherein each of the first keyboard and the second keyboard includes a plurality of keys, and a plurality of lighting portions that light up depending on depression of the plurality of keys, and
the state of each of the first keyboard and the second keyboard is states of the plurality of lighting portions included in each of the first keyboard and the second keyboard.
3. The remote operation system as claimed in claim 2 , wherein the client makes the states of the first keyboard identical with preset states of the plurality of lighting portions, and transmits information which makes the states of the second keyboard identical with the preset states of the plurality of lighting portions, to the KVM switch at the time of start of remote operation.
4. The remote operation system as claimed in claim 2 , wherein at the time of termination of remote control, the client returns current states of the plurality of lighting portions of the first keyboard to the states of the plurality of lighting portions of the first keyboard received at the time of start of the remote control.
5. The remote operation system as claimed in claim 3 , wherein at the time of termination of remote control, the client returns current states of the plurality of lighting portions of the first keyboard to the states of the plurality of lighting portions of the first keyboard received at the time of start of the remote control.
6. A remote operation system comprising a server, a client to which a first keyboard is connected, and a KVM switch connected to the server, the client and a second keyboard for operating the server,
the client including:
a first reception portion that receives a state of the first keyboard; and
a first transmission portion that transmits the state of the first keyboard to the KVM switch; and
the KVM switch including:
a second reception portion that receives the state of the first keyboard from the client;
a determination portion that determines whether the state of the second keyboard is identical with the state of the first keyboard; and
a second transmission portion that transmits information which makes the state of the second keyboard identical with the state of the first keyboard, to the server when the state of the second keyboard is not identical with the state of the first keyboard.
7. The remote operation system as claimed in claim 6 , wherein each of the first keyboard and the second keyboard includes a plurality of keys, and a plurality of lighting portions that light up depending on depression of the plurality of keys, and
the state of each of the first keyboard and the second keyboard is states of the plurality of lighting portions included in each of the first keyboard and the second keyboard.
8. The remote operation system as claimed in claim 7 , wherein the KVM switch makes the states of the second keyboard identical with preset states of the plurality of lighting portions, and transmits information which makes the states of the first keyboard identical with the preset states of the plurality of lighting portions, to the client at the time of start of remote operation.
9. The remote operation system as claimed in claim 7 , wherein at the time of termination of remote control, the client returns current states of the plurality of lighting portions of the second keyboard to the states of the plurality of lighting portions of the second keyboard received at the time of start of the remote control.
10. The remote operation system as claimed in claim 8 , wherein at the time of termination of remote control, the client returns current states of the plurality of lighting portions of the second keyboard to the states of the plurality of lighting portions of the second keyboard received at the time of start of the remote control.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008102775A JP2009252172A (en) | 2008-04-10 | 2008-04-10 | Remote operation system |
JP2008-102775 | 2008-04-10 |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090259792A1 true US20090259792A1 (en) | 2009-10-15 |
US8407380B2 US8407380B2 (en) | 2013-03-26 |
Family
ID=41164915
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/385,555 Expired - Fee Related US8407380B2 (en) | 2008-04-10 | 2009-04-10 | Remote operation system |
Country Status (2)
Country | Link |
---|---|
US (1) | US8407380B2 (en) |
JP (1) | JP2009252172A (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100223417A1 (en) * | 2009-02-27 | 2010-09-02 | Action Star Enterprise Co., Ltd. | Switch for transferring a file between associated computers |
US20100318717A1 (en) * | 2009-06-16 | 2010-12-16 | International Business Machines Corporation | Status information saving among multiple computers |
US20120326851A1 (en) * | 2011-06-23 | 2012-12-27 | Sony Corporation | Remote control device, a far-end device, a multimedia system and a control method thereof |
CN106164924A (en) * | 2014-06-26 | 2016-11-23 | 阿沃森特亨茨维尔公司 | Form the system and method for the keyboard, video and the mouse device that prevent the secure peripheral collaborative share of leaking data from switching |
US10187276B2 (en) * | 2011-02-11 | 2019-01-22 | Alcatel Lucent | Networking device adapted for use as a gateway for a local network, and associated method |
CN113934493A (en) * | 2021-10-12 | 2022-01-14 | 北京百度网讯科技有限公司 | Keyboard communication method, device, equipment, system and medium based on cloud service |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0850607A1 (en) | 1996-12-31 | 1998-07-01 | Cordis Corporation | Valve prosthesis for implantation in body channels |
US6454799B1 (en) | 2000-04-06 | 2002-09-24 | Edwards Lifesciences Corporation | Minimally-invasive heart valves and methods of use |
US8236045B2 (en) | 2006-12-22 | 2012-08-07 | Edwards Lifesciences Corporation | Implantable prosthetic valve assembly and method of making the same |
US8460368B2 (en) | 2008-02-29 | 2013-06-11 | Edwards Lifesciences Corporation | Expandable member for deploying a prosthetic device |
US8323335B2 (en) | 2008-06-20 | 2012-12-04 | Edwards Lifesciences Corporation | Retaining mechanisms for prosthetic valves and methods for using |
US8652202B2 (en) | 2008-08-22 | 2014-02-18 | Edwards Lifesciences Corporation | Prosthetic heart valve and delivery apparatus |
US8449599B2 (en) | 2009-12-04 | 2013-05-28 | Edwards Lifesciences Corporation | Prosthetic valve for replacing mitral valve |
US9155619B2 (en) | 2011-02-25 | 2015-10-13 | Edwards Lifesciences Corporation | Prosthetic heart valve delivery apparatus |
US9289282B2 (en) | 2011-05-31 | 2016-03-22 | Edwards Lifesciences Corporation | System and method for treating valve insufficiency or vessel dilatation |
US9119716B2 (en) | 2011-07-27 | 2015-09-01 | Edwards Lifesciences Corporation | Delivery systems for prosthetic heart valve |
US9510946B2 (en) | 2012-09-06 | 2016-12-06 | Edwards Lifesciences Corporation | Heart valve sealing devices |
US9439763B2 (en) | 2013-02-04 | 2016-09-13 | Edwards Lifesciences Corporation | Prosthetic valve for replacing mitral valve |
US9168129B2 (en) | 2013-02-12 | 2015-10-27 | Edwards Lifesciences Corporation | Artificial heart valve with scalloped frame design |
KR101688630B1 (en) * | 2015-09-15 | 2016-12-21 | 한국전자통신연구원 | Keyboard apparatus and data communication method using the same |
US11259920B2 (en) | 2015-11-03 | 2022-03-01 | Edwards Lifesciences Corporation | Adapter for prosthesis delivery device and methods of use |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5446906A (en) * | 1993-06-30 | 1995-08-29 | Intel Corporation | Method and apparatus for suspending and resuming a keyboard controller |
US6609034B1 (en) * | 2000-03-29 | 2003-08-19 | Epicenter, Incorporated | System and method for remotely controlling and monitoring a plurality of computer systems |
US6671756B1 (en) * | 1999-05-06 | 2003-12-30 | Avocent Corporation | KVM switch having a uniprocessor that accomodate multiple users and multiple computers |
US20050044236A1 (en) * | 2003-08-06 | 2005-02-24 | David Stafford | Method and apparatus for transmitting keyboard/video/mouse data to and from digital video appliances |
US20050172039A1 (en) * | 2004-02-04 | 2005-08-04 | C&C Technic Taiwan Co., Ltd. | KVM switch |
US7003563B2 (en) * | 2001-11-02 | 2006-02-21 | Hewlett-Packard Development Company, L.P. | Remote management system for multiple servers |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3028908B2 (en) | 1994-03-29 | 2000-04-04 | 日産車体株式会社 | Control device |
JP2973972B2 (en) | 1997-06-10 | 1999-11-08 | 日本電気株式会社 | Control method of remote control system with operation guide function |
US6681250B1 (en) | 2000-05-03 | 2004-01-20 | Avocent Corporation | Network based KVM switching system |
JP4601895B2 (en) * | 2002-09-26 | 2010-12-22 | 富士通コンポーネント株式会社 | Switching device and computer system |
JP4246528B2 (en) * | 2003-03-26 | 2009-04-02 | 富士通コンポーネント株式会社 | Selector |
-
2008
- 2008-04-10 JP JP2008102775A patent/JP2009252172A/en active Pending
-
2009
- 2009-04-10 US US12/385,555 patent/US8407380B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5446906A (en) * | 1993-06-30 | 1995-08-29 | Intel Corporation | Method and apparatus for suspending and resuming a keyboard controller |
US6671756B1 (en) * | 1999-05-06 | 2003-12-30 | Avocent Corporation | KVM switch having a uniprocessor that accomodate multiple users and multiple computers |
US6609034B1 (en) * | 2000-03-29 | 2003-08-19 | Epicenter, Incorporated | System and method for remotely controlling and monitoring a plurality of computer systems |
US7003563B2 (en) * | 2001-11-02 | 2006-02-21 | Hewlett-Packard Development Company, L.P. | Remote management system for multiple servers |
US20050044236A1 (en) * | 2003-08-06 | 2005-02-24 | David Stafford | Method and apparatus for transmitting keyboard/video/mouse data to and from digital video appliances |
US20050172039A1 (en) * | 2004-02-04 | 2005-08-04 | C&C Technic Taiwan Co., Ltd. | KVM switch |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100223417A1 (en) * | 2009-02-27 | 2010-09-02 | Action Star Enterprise Co., Ltd. | Switch for transferring a file between associated computers |
US20100318717A1 (en) * | 2009-06-16 | 2010-12-16 | International Business Machines Corporation | Status information saving among multiple computers |
US8271704B2 (en) * | 2009-06-16 | 2012-09-18 | International Business Machines Corporation | Status information saving among multiple computers |
US8793414B2 (en) | 2009-06-16 | 2014-07-29 | International Business Machines Corporation | Status information saving among multiple computers |
US9229658B2 (en) | 2009-06-16 | 2016-01-05 | International Business Machines Corporation | Status information saving among multiple computers |
US10187276B2 (en) * | 2011-02-11 | 2019-01-22 | Alcatel Lucent | Networking device adapted for use as a gateway for a local network, and associated method |
US20120326851A1 (en) * | 2011-06-23 | 2012-12-27 | Sony Corporation | Remote control device, a far-end device, a multimedia system and a control method thereof |
US9024734B2 (en) * | 2011-06-23 | 2015-05-05 | Sony Corporation | Remote control device, a far-end device, a multimedia system and a control method thereof |
CN106164924A (en) * | 2014-06-26 | 2016-11-23 | 阿沃森特亨茨维尔公司 | Form the system and method for the keyboard, video and the mouse device that prevent the secure peripheral collaborative share of leaking data from switching |
US20160371511A1 (en) * | 2014-06-26 | 2016-12-22 | Avocent Huntsville Corp. | System And Method For KVM Appliance Forming A Secure Peripheral Sharing Switch To Prevent Data Leakage |
US10331914B2 (en) * | 2014-06-26 | 2019-06-25 | Vertiv It Systems, Inc. | System and method for KVM appliance forming a secure peripheral sharing switch to prevent data leakage |
CN113934493A (en) * | 2021-10-12 | 2022-01-14 | 北京百度网讯科技有限公司 | Keyboard communication method, device, equipment, system and medium based on cloud service |
Also Published As
Publication number | Publication date |
---|---|
JP2009252172A (en) | 2009-10-29 |
US8407380B2 (en) | 2013-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8407380B2 (en) | Remote operation system | |
US6243079B1 (en) | Initialization method for one-way communications and apparatus for use therewith | |
JP5372357B2 (en) | KVM switch, control method therefor, multi-monitor compatible switching system, and multi-monitor compatible switching method | |
EP2065788B1 (en) | Information processing apparatus, remote system, and computer program | |
KR100510048B1 (en) | Interface for input device | |
US20070050525A1 (en) | [virtual com port for remote i/o controller] | |
US20090160779A1 (en) | Emulating A Keyboard On A Touch Screen Monitor Of A Computer System | |
US8346948B2 (en) | Information processing apparatus, selector, remote operation system, scan code transmission method, and program product therefor | |
US9224555B2 (en) | Light emitting diode illuminated keyboard | |
US20130254439A1 (en) | Isolated protected access device | |
JP4827533B2 (en) | Switcher and computer system | |
US8234333B2 (en) | Thin client device and method of use | |
JP4245334B2 (en) | Keypad instruction mode input method | |
US20110040853A1 (en) | KVM switch and KVM system | |
US10255426B2 (en) | Keyboard device and data communication method using the same | |
US8074001B2 (en) | Information processing apparatus, KVM switch, remote system, and computer readable storage medium | |
US20110270915A1 (en) | System comprising a server and a terminal provided with graphical interfaces communicating via an image-sharing protocol | |
KR100756674B1 (en) | Computing system for using a numerous monitor | |
US20050102432A1 (en) | Legacy keyboard support system | |
JP2005078496A (en) | Device, program, program recording medium, and method of output changeover | |
JP7118758B2 (en) | ELECTRONIC DEVICE, KEYCODE GENERATING METHOD AND PROGRAM | |
US20170010983A1 (en) | Input device identifying computer system and identification method thereof | |
KR101374801B1 (en) | Usb keyboard apparatus and method capable of supporting n-key rollover with bios compatibility | |
JP2009123125A (en) | Kvm switch, information processing apparatus, and program | |
US20090300132A1 (en) | Computer operation system and computer operation method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FUJITSU COMPONENT LIMITED, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MATSUNAGA, AKIHIRO;KATAYAMA, SHINICHI;NAGAO, NAOYUKI;REEL/FRAME:022578/0479 Effective date: 20090407 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20170326 |