JP4535346B2 - Information processing apparatus, system, remote operation method, program, and recording medium - Google Patents

Description

  The present invention relates to an information processing apparatus, a system, a remote operation method, a program, and a recording medium.

  Conventionally, when a plurality of servers operating on a network are switched and used, a KVM device via a network is used. FIG. 1 is a configuration diagram of a system for operating a plurality of servers using a conventional KVM device via a network.

  As shown in FIG. 1, the system 20 includes a console PC 1, KVM devices 2 and 3 via a network, servers 4 to 9, a keyboard 10, a pointing device 11, and a communication device 12. One console PC 1 is connected to the KVM devices 2 and 3 via the network via the network 13, the servers 4, 5 and 6 are connected to the KVM device 2 via the network, and the servers 7, 8 and 6 are connected to the KVM device 3 via the network. 9 are connected to each other.

  A keyboard 10 and a pointing device 11 are connected to the console PC 1 as input devices. An IP address is set for the KVM devices 2 and 3 via the network, and the console PC 1 communicates with the KVM devices 2 and 3 via the network using a protocol such as TCP / IP, and either one is selected based on a specific selection operation. Are selected as servers to be operated from the console PC 1.

  Next, the internal configuration of the console PC 1 shown in FIG. 1 will be described. FIG. 2 is a diagram for explaining the internal configuration of a conventional console PC 1. As shown in FIG. 2, the console PC 1 has an OS (Operating System) 30 and an application 40. In addition, the same code | symbol is attached | subjected about the same location as FIG. 1, and the description is abbreviate | omitted. The application 40 includes a key code receiving unit 41, a pointing device data receiving unit 42, a server communication unit 43, and a memory 44.

  When the keyboard 10 and the pointing device 11 are operated, the key code receiving unit 41 operating in the application 40 receives the key code output from the keyboard 10 and the pointing device data output from the pointing device 11 via the OS 30. Obtain it and save it in the memory 44. The server communication unit 43 reads the key code and pointing device data from the memory 44 and uses the TCP / IP protocol to read these data, and the KVM devices 2 and 3 via the network to which the selected servers 4 to 9 are connected. Send to. Upon receiving the data, the KVM devices 2 and 3 via the network send the key code output from the keyboard 10 and the mouse data output from the pointing device 11 to the selected server, and operate the selected server from the console PC 1 To do. Next, a general conventional KVM device via a network will be described.

  The KVM device described in Patent Document 1 enables communication between a workstation and a server by connecting a specific server to a network based on a server selection operation from the workstation, and allows a plurality of computers to be connected from other computers. It can be operated remotely.

JP 2001-344189 A

  However, since the key code output from the keyboard 10 connected to the console PC 1 is acquired on the application 40 running in the user mode of the console PC 1, the application monitoring the key input on the console PC 1 If there are others, an application other than the application 40 that monitors the key during execution of the remote operation becomes active, and as a result, the state of the application 40 that has executed the remote operation is no longer active, and the key code And pointing device data are not transmitted to the selection server.

  Conventionally, there is an application having a button GUI (Graphical User Interface) that transmits a special key to a selection server. However, when a special key is transmitted by the button GUI, an operation such as mouse input that is not a normal key operation is performed. As a result, there is a problem that it becomes difficult to perform key input operations continuously. In addition, every time the number of special keys to be transmitted to the server increases, GUIs such as buttons increase in the application.

  Accordingly, the present invention has been made to solve these problems, and is an information processing apparatus, system, remote operation method, and program capable of remotely operating a server by only normal key operations without being affected by other applications. The purpose is to provide.

In order to solve the above-mentioned problems, an information processing apparatus according to the present invention is an information processing apparatus that remotely operates a server existing on a network, as described in claim 1, and operates the server from a remote operation application. Pointing device data storage start request for storing the pointing device data output from the pointing device in a predetermined memory after receiving the request, and pointing device data for blocking transmission of the pointing device data to the OS in the information processing apparatus blocking start request, and an interface control unit for outputting a network transmission start request for transmitting pointing device data stored in the memory to the server, in response to the pointing device data storage start request, the Pointi A pointing device data output from Gudebaisu acquired before the OS in the information processing apparatus acquires a pointing device for transmitting the pointing device data to the pointing device data controller while saving the pointing device data in said memory In response to the pointing device data blocking start request, the data receiving unit, a pointing device data control unit that blocks transmission of the pointing device data received from the pointing device data receiving unit to the OS, and the network transmission start request in response, a communication unit and that transmits the pointing device data stored in the memory to the server, pointing device data stored in said memory, further wherein b Through the interface control unit, characterized in that it is sent to the application for the remote operation.

  According to the first aspect of the present invention, since the pointing device data can be transmitted to the server on the network without being transmitted to the OS in the information processing apparatus, it is affected by other applications that monitor the pointing device input. The pointing device data can be transmitted without any problem. Therefore, it is possible to realize a remote operation via a network without notifying the OS of a normal pointing device operation. In addition, key input operations can be performed continuously.

According to the present invention, in the information processing apparatus according to claim 1, the remote operation application creates a thread for executing emulation of a pointing device during the remote operation of the server. The thread receives the pointing device data stored in the memory via the interface control unit, and executes the emulation of the pointing device based on the received pointing device data .

  According to a third aspect of the present invention, in the information processing device according to the first or second aspect, the information processing device is a KVM device.

The system of the present invention is a system comprising a plurality of servers and an information processing apparatus that remotely operates the server via a network, as defined in claim 4 , wherein the information processing apparatus includes: It is an information processing apparatus as described in any one of Claims 1-3. According to the fourth aspect of the present invention, since the key code and the pointing device data can be transmitted to the server on the network without being transmitted to the OS in the information processing apparatus, the influence of other applications that monitor key input is affected. The special key can be transmitted without receiving.

According to another aspect of the present invention, there is provided a remote operation method for an information processing apparatus for remotely operating a server existing on a network, wherein the server is operated from a remote operation application. Pointing device data storage start request for storing the pointing device data output from the pointing device in a predetermined memory after receiving the request, and pointing device data for blocking transmission of the pointing device data to the OS in the information processing apparatus blocking start request, and an output step of outputting the network transmission start request for transmitting pointing device data stored in the memory to the server, in response to the pointing device data storage start request from said pointing device Get the force is pointing device data was before the OS gets in the information processing apparatus, a storage step of transmitting to the blocking step the pointing device data while saving the pointing device data in a predetermined memory, the pointing A blocking step for blocking transmission of the pointing device data received from the storage step to the OS in response to a device data blocking start request, and a pointing device data stored in the memory in response to the network transmission start request. have a transmission step of transmitting to said server, pointing device data stored in said memory, characterized in that it is further transmitted to the application for remote operation.

  According to the fifth aspect of the present invention, since the pointing device data can be transmitted to the server on the network without being transmitted to the OS in the information processing apparatus, it is influenced by other applications that monitor the pointing device input. The pointing device data can be transmitted without any problem. Therefore, it is possible to realize a remote operation via a network without notifying the OS of a normal pointing device operation.

The present invention provides the remote operation method according to claim 5, wherein the remote operation application creates a thread for executing emulation of a pointing device during the remote operation of the server. The thread receives the pointing device data stored in the memory, and executes emulation of the pointing device based on the received pointing device data .

According to another aspect of the present invention, there is provided a program for pointing a computer after receiving a request for operating the server from an application for remote operation in order to remotely operate a server existing on a network. Pointing device data storage start request for storing the pointing device data output from the device in a predetermined memory, Pointing device data blocking start request for blocking transmission of the pointing device data to the OS in the information processing apparatus, and the memory interface control unit for outputting a network transmission start request for transmitting pointing device data to the server that is stored in, in response to the pointing device data storage start request is outputted from the pointing device And the pointing device data acquired before the OS in the information processing apparatus acquires, pointing device data receiving unit for transmitting the pointing device data to the pointing device data controller while saving the pointing device data to said memory, In response to the pointing device data blocking start request, a pointing device data control unit that blocks transmission of the pointing device data received from the pointing device data receiving unit to the OS , and in response to the network transmission start request, the memory a pointing device data stored to function as a communication unit for transmitting to the server, the pointing device data stored in said memory, further wherein the interface system Through the part, characterized in that it is sent to the application for the remote operation.

  According to the seventh aspect of the present invention, since the pointing device data can be transmitted to the server on the network without being transmitted to the OS in the computer, it is not affected by other applications that monitor the pointing device input. , Pointing device data can be transmitted. Therefore, it is possible to realize a remote operation via a network without notifying the OS of a normal pointing device operation. In addition, key input operations can be performed continuously.

Further, according to the present invention, as described in claim 8, in the program according to claim 7, the remote operation application creates a thread for executing emulation of a pointing device during remote operation of the server, The thread receives the pointing device data stored in the memory through the interface control unit, and executes emulation of the pointing device based on the received pointing device data .

  Further, as described in claim 9, the recording medium of the present invention records the program according to claim 7 or 8.

  According to the present invention, it is possible to provide an information processing apparatus, a system, a remote operation method, and a program capable of remotely operating a server by only a normal key operation without being affected by other applications.

It is a block diagram of the system which operates a some server using the conventional KVM apparatus via a network. It is a figure for demonstrating the internal structure of the conventional console PC. 1 is a block diagram of a system according to a first embodiment. It is a process flowchart of a key code receiving part. It is a process flowchart of a pointing device data receiving part. It is a process flowchart of a key code control part. It is a process flowchart of a pointing device data control part. It is a process flowchart of a server communication part. It is a process flowchart of an interface control part. It is a figure which shows the sequence of the process in FIG. It is a figure which shows the sequence of the process in FIG. It is a figure which shows the sequence of the process in FIG. It is a block diagram of the system which concerns on 2nd Example. It is a figure which shows the GUI which an application provides. It is a figure which shows GUI of the application in remote operation. It is a process flowchart of the application at the time of operating the server in a remote place via a network. It is a processing flowchart of initialization of an application. It is a process flowchart of mouse event generation of an application. It is a flowchart of an application termination process. It is a figure which shows the sequence of the process in FIG. It is a figure which shows the sequence of the process in FIG. It is a figure which shows the sequence of the process in FIG.

  Hereinafter, the best mode for carrying out the present invention will be described.

  FIG. 3 is a block diagram of the system 100 according to the first embodiment. As shown in FIG. 3, the system 100 includes a console PC 51, network KVM devices 2 and 3, servers 4 to 9, a keyboard 10, a pointing device 11 such as a mouse, and a communication device 12.

  The console PC 51 remotely controls the servers 4 to 9 existing on the network, and includes a device driver 60, an OS 70, and an application 80. The console PC 51 is configured using, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like. The console PC 51 may be configured by a KVM device having a function of switching a plurality of computers.

  The device driver 60 includes a key code receiving unit 61, a pointing device data receiving unit 62, a memory 63, a key code control unit 64, a pointing device data control unit 65, an interface 66, and a server communication unit 67. The key code receiving unit 61, the pointing device data receiving unit 62, the key code control unit 64, the pointing device data control unit 65, the interface control unit 66, and the server communication unit 67 perform their operations according to the instruction information transmitted from the application 80. Can be switched.

  Here, the instruction information designates the operation of each module of the key code receiving unit 61, the pointing device data receiving unit 62, the key code control unit 64, the pointing device data control unit 65, the interface control unit 66, and the server communication unit 67. Information. There are two types of instruction information for specifying the operation of the key code receiving unit 61: a key code storage start request and a key code storage end request, and these two types of information are in an exclusive relationship.

  A plurality of applications including the application 80 exist on the OS 70. These applications monitor key inputs from the keyboard 10 and the pointing device 11. The application 80 is for remotely operating the servers 4 to 9 via the network 13.

  Next, the key code receiving unit 61 will be described. The key code receiving unit 61 has the following functions including the function of acquiring the key code output from the keyboard 10 before the OS 70 acquires it and storing the key code in the memory 63. The key code receiving unit 61 has a function of receiving the key code transmitted from the keyboard 10, a function of storing the key code received from the keyboard 10 in the memory 63, and transmitting the key code received from the keyboard 10 to the key code control unit 64. A function for receiving the instruction information transmitted from the interface control unit 66, a function for storing the instruction information received from the interface control unit 66 in the memory 63, and a function for reading the instruction information stored in the memory 63. Then, the key code received from the keyboard 10 is transmitted to the key code control unit 64, and the key code is switched between saving and non-saving in the memory 63 according to the instruction information from the interface control unit 66.

  FIG. 4 is a process flowchart of the key code receiving unit 61. The processing of the key code receiving unit 61 includes steps S0001 to S0004 for processing instruction information from the interface control unit 66, and steps S0005 to S0010 for processing the key code transmitted from the keyboard 10. These operate independently. First, a flow for processing instruction information from the interface control unit 66 will be described. In S0002, the key code receiving unit 61 stands by until instruction information is transmitted from the interface control unit 66, and stores the instruction information received from the interface control unit 66 in the memory 63 in S0003.

  Next, a flow for processing a key code transmitted from the keyboard 10 will be described. In S0006, the key code receiving unit 61 waits until a key code is received from the keyboard 10, and transmits the key code received from the keyboard 10 to the key code control unit 64 in S0007. In S0008, the instruction information is read from the memory 63, and it is confirmed whether the read instruction information is a key code storage start request or a key code storage end request. The key code storage start request and the key code storage end request are exclusive. If there is a key code storage start request, the key code received from the keyboard 10 is stored in the memory 63 in S0009, and there is a key code storage end request. Does not store the key code received from the keyboard 10 in the memory 63.

  Next, the pointing device data receiving unit 62 will be described. The pointing device data receiving unit 62 has the following functions including the function of acquiring the pointing device data output from the pointing device 11 before the OS 70 acquires it and storing the pointing device data in the memory 63.

  The pointing device data receiving unit 62 has a function of receiving the pointing device data transmitted from the pointing device 11, a function of storing the pointing device data received from the pointing device 11 in the memory 63, and the pointing device data received from the pointing device 11. A function for transmitting to the pointing device data control unit 65, a function for receiving the instruction information transmitted from the interface control unit 66, a function for storing the instruction information received from the interface control unit 66 in the memory 63, and an instruction information stored in the memory 63 And transmits the pointing device data received from the pointing device 11 to the pointing device data control unit 65 to control the interface. According to the instruction information from the 66, the pointing device data stored to the memory 63, switches the non-conservative.

  FIG. 5 is a process flowchart of the pointing device data receiving unit 62. The processing of the pointing device data receiving unit 62 includes flows S0101 to S0104 for processing instruction information from the interface control unit 66, and flows S0105 to S0110 for processing pointing device data transmitted from the pointing device 11. These operate independently. First, a flow for processing instruction information from the interface control unit 66 will be described. In S0102, the pointing device data receiving unit 62 waits until the instruction information is transmitted from the interface control unit 66, and stores the instruction information received from the interface control unit 66 in the memory 63 in S0103.

  Next, a flow for processing pointing device data transmitted from the pointing device 11 will be described. In step S0106, the process waits until the pointing device data is received from the pointing device 11. In step S0107, the pointing device data received from the pointing device 11 is transmitted to the pointing device data control unit 65. In S0108, the instruction information is read from the memory 63, and it is confirmed whether the read instruction information is a pointing device data storage start request or a pointing device data storage end request.

  The pointing device data storage start request and the pointing device data storage end request are made exclusive. If there is a pointing device data storage start request, the pointing device data received from the pointing device 11 is stored in the memory 63 in S0109, and the pointing device When there is a data storage end request, the pointing device data received from the pointing device 11 is not stored in the memory 63.

  Next, the key code control unit 64 will be described. The key code control unit 64 includes the function of blocking the transmission of the key code to the OS 70 and has the following functions. The key code control unit 64 has a function of receiving the key code transmitted from the key code receiving unit 61, a function of blocking transmission of the key code received from the key code receiving unit 61 to the OS 70, and a function of transmitting from the interface control unit 66. A function of receiving the received instruction information, a function of storing the instruction information received from the interface control unit 66 in the memory 63, and a function of reading the instruction information stored in the memory 63. In accordance with the instruction information from the interface control unit 66, blocking and transmission of transmission of the key code received from the key code receiving unit 61 to the OS 70 are switched.

  FIG. 6 is a process flowchart of the key code control unit 64. The processing of the key code control unit 64 includes S 0201 to S 0204 for processing instruction information from the interface control unit 66 and S 0205 to S 0210 for processing the key code transmitted from the key code receiving unit 61. These operate independently. First, a flow for processing instruction information from the interface control unit 66 will be described. In S0202, the key code control unit 64 stands by until the instruction information is transmitted from the interface control unit 66, and stores the instruction information received from the interface control unit 66 in the memory 63 in S0203.

  Next, a flow for processing a key code transmitted from the key code receiving unit 61 will be described. In step S0206, the process waits until a key code is received from the key code receiving unit 61. In step S0207, the key code is received from the key code control unit 64. In S0208, the instruction information is read from the memory 63, and it is confirmed whether the read instruction information is a key code cutoff start request or a key code cutoff end request. The key code cutoff start request and the key code cutoff end request are exclusive. If there is a key code cutoff start request, transmission of the key code received from the key code receiving unit 61 to the OS 70 is blocked, and the key code cutoff termination request is If there is, the key code received from the key code receiving unit 61 is transmitted to the OS 70 in S0209.

  Next, the pointing device data control unit 65 will be described. The pointing device data control unit 65 includes the function of blocking the transmission of pointing device data to the OS 70 and has the following functions.

  The pointing device data control unit 65 has a function of receiving the pointing device data transmitted from the pointing device data receiving unit 62, a function of blocking the transmission of the pointing device data received from the pointing device data receiving unit 62 to the OS 70, and interface control. A function of receiving the instruction information transmitted from the unit 66, a function of storing the instruction information received from the interface control unit 66 in the memory 63, and a function of reading the instruction information stored in the memory 63. In accordance with the instruction information, blocking and transmission of transmission of the pointing device data received from the pointing device data receiving unit 62 to the OS 70 are switched.

  FIG. 7 is a process flowchart of the pointing device data control unit 65. The processing of the pointing device data control unit 65 includes flows S0301 to S0304 for processing instruction information from the interface control unit 66, and flows S0305 to S0310 for processing pointing device data transmitted from the pointing device data receiving unit 62. . These operate independently. First, a flow for processing instruction information from the interface control unit 66 will be described. In S0302, the pointing device data control unit 65 stands by until the instruction information is transmitted from the interface control unit 66, and stores the instruction information received from the interface control unit 66 in the memory 63 in S0303.

  Next, a flow for processing the pointing device data transmitted from the pointing device data receiving unit 62 will be described. In S0306, it waits until it receives the pointing device data from the pointing device data receiving unit 62. In S0307, it receives the pointing device data from the pointing device data control unit 65. In S0308, the instruction information is read from the memory 63, and it is confirmed whether the read instruction information is a pointing device data blocking start request or a pointing device data blocking end request.

  The pointing device data blocking start request and the pointing device data blocking end request are exclusive. When there is a pointing device data blocking start request, transmission of the pointing device data received from the pointing device data receiving unit 62 to the OS 70 is blocked and pointing is performed. If there is a device data cutoff end request, the pointing device data received from the pointing device data receiving unit is transmitted to the OS 70 in S0309.

  Next, the server communication unit 67 will be described. The server communication unit 67 has the following functions including a function of transmitting the key code and pointing device data stored in the memory 63 to the servers 4 to 9.

  The server communication unit 67 has a function of reading the key code and pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62, and the key code and pointing device data stored in the memory 63 are received by the key code. A function for confirming the update by the unit 61 and the pointing device receiving unit 62, a function for designating information to be transmitted to other communication devices on the network 13 connected to the communication device, a transmission destination thereof, and a transmission destination. A function of reading from the memory 63, a function of receiving instruction information transmitted from the interface control unit 66, a function of storing instruction information received from the interface control unit 66 in the memory 63, and a function of reading instruction information stored in the memory 63 And interface According to the instruction information from the scan control unit 66, it transmits the key code and pointing device data to other communication devices on the network 13 because read from the memory 63, switches the non-transmission.

  FIG. 8 is a process flowchart of the server communication unit 67. The processing of the server communication unit 67 includes flows S0401 to S0404 for processing the instruction information from the interface control unit 66, and the key code and pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62. And flow S0405 to S0410 for reading processing. These operate independently. First, a flow for processing instruction information from the interface control unit 66 will be described. In S0402, the server communication unit 67 waits until the instruction information is transmitted from the interface control unit 66, and stores the instruction information received from the interface control unit 66 in the memory 63 in S0403.

  Next, a flow for reading and processing the key code and pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 will be described. In S0406, server communication unit 67 reads the instruction information from memory 63, and confirms the network transmission start request and the network transmission end request from the read instruction information. The network transmission start request and the network transmission end request are exclusive. If there is a network transmission start request, the server communication unit 67 is stored in the memory 63 by the key code reception unit 61 and the pointing device reception unit 62 in S0408. Starts transmission of key code and pointing device data. If there is a network transmission end request, transmission is not started until the network transmission start request is stored in the memory.

  If there is a network transmission start request, in S0408, the server communication unit 67 checks whether the key code and the pointing device data stored in the memory 63 are updated by the key code receiving unit 61 and the pointing device receiving unit 62. If updated, the updated key code and pointing device data are read from the memory 63 in S0409, and the communication destination information is read from the memory in S0410. The communication destination information is information necessary for remotely operating the servers 4 to 9 connected to the network KVM apparatuses 2 and 3 on the network 13 connected to the communication device.

  In S0411, the server communication unit 67 transmits the key code and pointing device data read from the memory 63 to the KVM apparatuses 2 and 3 via the network in the communication destination information. In S0408, the server communication unit 67 determines that the key code and the pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 have not been updated. Transmission is not performed until the pointing device data is updated.

  In loop S0407, the server communication unit 67 reads the instruction information from the memory 63, and stores the key code stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 until the network transmission end request is stored. Wait for the pointing device data to be updated. In S0408, the server communication unit 67 reads the instruction information from the memory 63 when the key code and the pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 are not updated, and the network Until the transmission end request is saved, the key code receiving unit 61 and the pointing device receiving unit 62 wait for the key code and pointing device data saved in the memory 63 to be updated.

  Next, the interface control unit 66 will be described. The interface control unit 66 transmits the key code and pointing device data stored in the memory 63 to the remote operation application 80 operating on the OS 70.

  The interface control unit 66 has a function of reading the key code and pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62, a function of transmitting the key code and pointing device data to the application 80, and a memory 63 A function for confirming that the key code and pointing device data stored in the key code are updated by the key code receiving unit 61 and the pointing device receiving unit 62, a function for receiving instruction information transmitted from the application 80, and a function received from the application 80. A function of storing instruction information in the memory 63, a function of reading instruction information stored in the memory 63, and a function of transmitting instruction information received from the application 80 to the key code receiving unit 61 A function of transmitting the instruction information received from the application 80 to the pointing device data receiving unit 62, a function of transmitting the instruction information received from the application 80 to the key code control unit 64, and a pointing device data control unit of the instruction information received from the application 80 A function of transmitting to the server communication unit 67, and a function of transmitting to the server communication unit 67, the key code and the pointing device data transmitted from the memory 63 according to the instruction information from the application 80. , Switch non-transmission.

  FIG. 9 is a process flowchart of the interface control unit 66. The processing of the interface control unit 66 is a process of reading the key code and pointing device data stored in the memory 63 by the flow S0501 to S0509 for processing the instruction information from the application 80, the key code receiving unit 61 and the pointing device receiving unit 62 Flow S0510 to S0517. These operate independently.

  First, a flow for processing instruction information from the application 80 will be described. In step S0502, the interface control unit 66 waits until instruction information is transmitted from the application 80, and stores the instruction information received from the application 80 in the memory 63 in step S0503. In step S 0504, the interface control unit 66 transmits instruction information for the key code receiving unit 61 to the key code receiving unit 61. In step S 0505, the interface control unit 66 transmits instruction information for the pointing device data receiving unit 62 to the pointing device data receiving unit 62.

  In step S 0506, the interface control unit 66 transmits instruction information for the key code control unit 64 to the key code control unit 64. In S0507, the interface control unit 66 transmits a blocking start request to the pointing device data control unit 65. In S0508, the interface control unit 66 transmits a communication start request to the server communication unit 67.

  Next, a flow for reading and processing the key code and pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 will be described. In step S0511, the interface control unit 66 reads the instruction information from the memory 63, and confirms the application transmission start request and the application transmission end request from the read instruction information. The application transmission start request and the application transmission end request are mutually exclusive. If there is an application transmission start request, the interface control unit 66 is stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 in S0513. Starts transmission of key code and pointing device data.

  When there is an application transmission end request, the interface control unit 67 does not start transmission until the application transmission start request is stored in the memory. If there is an application transmission start request, in step S0513, the interface control unit 67 checks whether the key code and the pointing device data stored in the memory 63 are updated by the key code receiving unit 61 and the pointing device receiving unit 62. If updated, the updated key code and pointing device data are read from the memory 63 in S0514, and the key code and pointing device data are transmitted to the application 80 in S0515.

  In S0513, when the key code and the pointing device data stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 are not updated, the interface control unit 67 determines the key code stored in the memory 63 and the key code stored in the memory 63. Transmission is not performed until the pointing device data is updated. In loop S0516, the interface control unit 66 reads the instruction information from the memory 63, and stores the key code stored in the memory 63 by the key code receiving unit 61 and the pointing device receiving unit 62 until the application transmission end request is stored. Wait for the pointing device data to be updated.

Next, the operation of the system will be described. Before operating the keyboard 10 and the pointing device 11, the interface control unit 66 transmits a server operation request from the application 80 to the interface control unit 66, and receives the operation request. The interface control unit 66 receives a storage request and pointing device data from the keyboard receiving unit 61. A storage request is transmitted to the receiving unit 62, a blocking request is transmitted to the keyboard control unit 64, a blocking request is transmitted to the pointing device data control unit 65, and a communication request is transmitted to the server communication unit 67. After these processes, a key code is generated by input to the keyboard 10, and the key code receiving unit 61 receives the key code, transmits the key code to the key code control unit 64, and stores it in the memory 63 according to the storage request. Save the key code.
The key code control unit 64 blocks the key code transmission to the OS 70 in accordance with the blocking request.

  The server communication unit 67 reads the key code from the memory 63 and transmits the key code to the communication device 12, and the key code is transmitted from the communication device 12 to the KVM devices 2 and 3 via the network. The interface control unit 66 reads the key code from the memory 63 and transmits the key code to the application 80, thereby enabling the interface control unit 66 to request remote operation of the server and termination of the remote operation according to the key code received by the application 80.

  The pointing device 11 also generates pointing device data in response to input to the pointing device 11, and the pointing device data receiving unit 62 receives the pointing device data and transmits the pointing device data to the pointing device data control unit 65. At the same time, the pointing device data is stored in the memory 63 in accordance with the storage request. The pointing device data control unit 65 blocks the transmission of the pointing device data to the OS 70 according to the blocking request.

  The server communication unit 67 reads the pointing device data from the memory 67, transmits it to the communication device 12, and the pointing device data is transmitted from the communication device 12 to the KVM devices 2 and 3 via the network 13. The interface control unit 66 reads the pointing device data from the memory 63 and transmits the pointing device data to the application 80, thereby enabling the interface control unit 66 to request remote operation of the server and termination of the remote operation according to the pointing device data received by the application 80. .

  As a result, the input key code and pointing device data can be transmitted to the KVM devices 2 and 3 via the network without being transmitted to the OS 70, and are not affected by the application that monitors other key codes, and the special key. Can be transmitted to the KVM devices 2 and 3 via the network, so that a normal key operation can be realized even in a remote operation via the network. Further, by transmitting the input key code and pointing device data to the remote operation application of the server, it is possible to realize the remote operation and termination of the remote operation of the server according to the key code and pointing device data received by the application.

  Details of the module processing in the first embodiment will be described. 10, FIG. 11 and FIG. 12 show the processing sequence in FIG. The server operation start request is the instruction information composed of the key code storage start request, pointing device data storage start request, key code block start request, pointing device data block start request, network transmission start request, application transmission start request, The server operation end request is instruction information including a key code storage end request, a pointing device data storage end request, a key code cutoff end request, a pointing device data cutoff end request, a network transmission end request, and an application transmission end request.

  As shown in FIG. 10, in step S0601, the user transmits a server operation start request from the application 80. In step S0602, the interface control unit 66 receives the server operation start request in flow S0502 shown in FIG. 9, and stores the server operation start request in the memory 63 in step S0503. Since the server operation start request includes the application transmission start request, the server 80 is set to transmit the key code and pointing device data read from the memory 63 to the application 80.

  Also, in the flow from S0504 to S0508, the interface control unit 66 makes a key code storage start request to the key code reception unit 61, a pointing device data storage start request to the pointing device data reception unit 62, and a key from the configuration of the server operation start request. A key code blocking start request is transmitted to the code control unit 64, a pointing device data blocking start request is transmitted to the pointing device data control unit 65, and a network transmission start request is transmitted to the server communication unit 67.

  In step S0603, the key code receiving unit 61 receives the key code storage start request in the flow of S0002 shown in FIG. 4 and stores the key code storage start request in the memory 63 in the flow of S0003. The received key code is set to be stored in the memory 63. In step S0604, the pointing device data receiving unit 62 receives the pointing device storage start request in the flow of S0102 shown in FIG. 5, and stores the pointing device data storage start request in the memory 63 in the flow of S0103. The pointing device data received from the device data receiving unit 62 is set to be stored in the memory 63.

  In step S0605, the key code control unit 64 receives the key code cutoff start request in the flow of S0202 shown in FIG. 6, and stores the key code cutoff start request in the memory 63 in the flow of S0203, thereby receiving the key code. The key code received from the unit 61 is set to be blocked from being transmitted to the OS 70. In step S0606, the pointing device data control unit 65 receives the pointing device data blocking start request in step S0302 shown in FIG. 7, and stores the pointing device data blocking start request in the memory 63 in step S0303. It is set to block the transmission of the pointing device data received from the receiving unit 62 to the OS 70.

  In step S0607, the server communication unit 67 receives the network transmission start request in the flow of S0402 shown in FIG. 8, and stores the network transmission start request in the memory 63 in the flow of S0403, whereby the KVM device via the network is stored. The key code read from the memory 63 and the pointing device data are set to be transmitted to 2 and 3.

  Thereafter, the key code is transmitted to the operation target server in the order of the keyboard 10, the key code receiving unit 61, the key code control unit 64, the memory 63, the server communication unit 67, the communication device 12, and the KVM devices 2 and 3 via the network. The As another path, the key code is transmitted to the application 80 in the order of the keyboard 10, the key code receiving unit 61, the key code control unit 64, the memory 63, the interface control unit 66, and the application 80. As a result, the servers 4 to 9 can be remotely operated without being transmitted to the OS 70.

  There are two types of routes for the data of the pointing device 11 as described above. That is, the pointing device data includes the pointing device 11, the pointing device data receiving unit 62, the pointing device control unit 65, the memory 63, the server communication unit 67, the communication device 12, and the network target KVM devices 2 and 3 in this order. Sent to. As another path, the pointing device data is transmitted to the application 80 in the order of the pointing device 11, the pointing device data receiving unit 61, the pointing device data control unit 65, the memory 63, the interface control unit 66, and the application 80. . As a result, the server 4 to 7 can be remotely operated without being transmitted to the OS 70.

  Next, a processing flow when performing remote operation from this state will be described with reference to FIG. First, transmission of a key code will be described. In S0701, a key code is generated by operating the keyboard 10, and the key code receiving unit 61 receives the key code in the flow S0006 shown in FIG. In step S0702, the key code receiving unit 61 is in a state of transmitting the key code to the key code control unit 64 in the flow of S0007 shown in FIG. 4 and storing the key code in response to the key code storage start request. The key code is stored in the memory 63 in the flow of S0009.

  In step S0703, the key code control unit 64 receives the key code from the key code receiving unit 61 in the flow of S0206 shown in FIG. 6, and blocks transmission of the key code to the OS 70 in response to the key code blocking start request. Therefore, the transmission of the key code to the OS 70 is blocked. In step S0704, the interface control unit 66 reads the key code stored in the memory 63 by the key code receiving unit 61 from the memory 63 in the flow of S0514 shown in FIG. 9, and transmits it to the application 80 by an application transmission start request. Therefore, it is transmitted to the application 80 in the flow of S0515.

  In step S0705, the application 80 receives the key code. In S0706, the server communication unit 67 is in a state of reading the key code stored by the key code receiving unit 61 from the memory 63 and transmitting it to the network 13 in response to a network transmission start request in the flow of S0409 shown in FIG. Therefore, the key code is transmitted to the communication device 12 in the flow of S0411.

  Next, transmission of pointing device data will be described. In step S0707, the pointing device data is generated by the operation of the pointing device 11, and the pointing device data receiving unit 62 receives the pointing device data in the flow of S0106 shown in FIG. In step S0708, the pointing device data receiving unit 62 is in a state of transmitting the pointing device data control unit 65 to the pointing device data control unit 65 in S0107 shown in FIG. In the flow of S0109, the pointing device data is stored in the memory 63.

  In step S0709, the pointing device data control unit 65 receives the pointing device data from the pointing device data receiving unit 62 in the flow of S0306 shown in FIG. 7, and the pointing device data to the OS 70 by the pointing device data blocking start request. Since the transmission of the pointing device data to the OS 70 is blocked, the transmission of the pointing device data to the OS 70 is blocked.

  In step S0710, the interface control unit 66 reads the pointing device data stored in the memory 63 by the pointing device data receiving unit 62 from the memory 63 in the flow of S0514 shown in FIG. 9, and transmits it to the application 80 by an application transmission start request. Therefore, it is transmitted to the application 80 in the flow of S0515. In step S0711, the application 80 receives pointing device data.

  In S0712, the server communication unit 67 reads the pointing device data saved by the pointing device data receiving unit 62 from the memory 63 in the flow of S0409 shown in FIG. 8, and transmits it to the network 13 by a network transmission start request. Therefore, the pointing device data is transmitted to the communication device 12 in the flow of S0411. With the above processing, the servers 4 to 9 can be remotely operated without transmitting the key code and pointing device data to the OS 70.

  Next, a process for terminating the remote operation of the server and flowing the key code and pointing device data on the OS 70 of the console PC 51 will be described with reference to FIG. In step S0801, when the user finishes the remote operation of the server from the application 80 by the key code and the pointing device data acquired in the procedure for transmitting the key code and the pointing device data to the application 80, the application 80 sends the server to the interface control unit 66. An operation end request is sent.

  In S0802, the interface control unit 66 receives the server operation end request in the flow of S0502 shown in FIG. 9, and stores the server operation end request in the memory 63 in the flow of S0503. Since the server operation end request includes the application transmission end request, the server operation end request is set to stop transmission to the application 80. Also, in the flow from S0504 to S0508, from the configuration of the server operation end request, the key code receiving unit 61 requests the key code storage end request, the pointing device data receiving unit 62 requests the pointing device data storage end request, and the key code control unit 64 receives the key. A code blocking end request, a pointing device data blocking end request to the pointing device data control unit 65, and a network transmission end request to the server communication unit 67 are transmitted.

  In step S0803, the key code receiving unit 61 receives the key code storage end request in S0002 shown in FIG. 4, and stores the key code storage end request in the memory 63 in the flow of S0003. The received key code is set not to be stored in the memory 63.

  In step S0804, the pointing device data receiving unit 62 receives the pointing device storage end request in the flow of S0102 shown in FIG. 5, and stores the pointing device data storage end request in the memory 63 in the flow of S0103. The pointing device data received from the pointing device 11 is set not to be stored in the memory 63. In step S0805, the key code control unit 64 receives the key code cutoff start request in step S0202 shown in FIG. 6, and stores the key code cutoff end request in the memory 63 in the flow of step S0203. The key code received from 61 is set to be transmitted to the OS 70.

  In step S0806, the pointing device data control unit 65 receives the pointing device data blocking end request in step S0302 shown in FIG. 7, and stores the pointing device data blocking end request in the memory 63 in the flow of step S0303. The pointing device data received from the device data receiving unit 62 is set to be transmitted to the OS 70.

  In step S0807, the server communication unit 67 receives the network transmission end request in S0402 shown in FIG. 8, and stores the network transmission end request in the memory 63 in the flow of S0403, so that the key code and the pointing device are stored from the memory 63. Data reading is stopped, and transmission to the communication device 12 is stopped. Then, the communication is set to end. As a result, transmission of the key code and pointing device data to the KVM apparatuses 2 and 3 via the network is stopped and transmitted to the OS 70.

  In step S 0808, a key code is generated by operating the keyboard 10, and the key code is transmitted to the key code receiving unit 61. In S0809, the key code receiving unit 61 receives the key code in S0006 shown in FIG. 4, and transmits it to the key code control unit 64 in the flow of S0007. In step S0810, the key code control unit 64 receives the key code transmitted from the key code receiving unit 61 in S0207 shown in FIG. 6, and transmits it to the OS 70 in the flow of S0209.

  In step S0811, the pointing device data is generated by the operation of the pointing device 11, and the pointing device data is transmitted to the pointing device data receiving unit 62. In S0812, the pointing device data receiving unit 62 receives the pointing device data in S0106 shown in FIG. 5, and transmits it to the pointing device data control unit 65 in S0107. In step S0813, the pointing device data control unit 65 receives the pointing device data transmitted from the pointing device data receiving unit 62 in S0307 shown in FIG. 7, and transmits it to the OS 70 in the flow of S0309.

  According to the first embodiment, the key code and pointing device data of the keyboard 10 and the pointing device 11 can be transmitted to the KVM devices 2 and 3 on the network 13 without transmitting to the OS 70. Further, the key code and pointing device data of the keyboard 10 and the pointing device 11 can be transmitted to the application 80 operating on the OS 70 without being transmitted to the OS 70. As a result, the special key can be transmitted to the servers 4 to 9 without being influenced by other applications that monitor the key input. Therefore, a normal key operation can be realized also in a remote operation via a network. Further, since the special key is not transmitted by the GUI, the key input operation can be continuously performed. Further, the GUI such as buttons does not increase.

  Next, a second embodiment will be described. In the second embodiment, an example in which the present invention is applied to a computer system in which a Windows (registered trademark) OS operates is shown. FIG. 13 is a block diagram of a system 200 according to the second embodiment. As illustrated in FIG. 13, the system 200 includes a console PC 151, network KVM devices 2 and 3, servers 4 to 9, a keyboard 10, a pointing device 11, and a communication device 12.

  The console PC 151 includes a device driver 160, an OS 170, and an application 180. The device driver 160 includes a key code receiving unit 61, a pointing device data receiving unit 62, a memory 63, a key code control unit 64, a pointing device data control unit 65, an interface 66, and a server communication unit 67. The application 180 has a memory 181.

  The console PC 151 is a so-called Dos / V machine on which the Windows (registered trademark) OS 170 operates, and the desktop image of the server in the connected state is received by a module in the console PC 151 via the network, and the information is the application It is assumed that 180 can be acquired.

  Further, the key code receiving unit 61, the pointing device data receiving unit 62, the key code control unit 64, the pointing device data control unit 65, the server communication unit 67, and the interface control unit 66 which are modules of the second embodiment are in kernel mode. It is a device driver that operates.

  The application 180 operates as an application that operates in a user mode having a GUI illustrated in FIG. Communication information to the servers 4 to 9 as connection destinations is stored in the memory 181. Further, the application 180 has a function of transmitting a key code and pointing device data to the servers 4 to 9 of the corresponding number when the button B with the server number shown in FIG. 14 is pressed, and the desktop of the server of the corresponding number on the screen display unit. It has a function of displaying a screen and a function of moving the mouse cursor using data of the pointing device 11 acquired from the interface receiving unit 66 when the server is connected.

FIG. 16 is a process flowchart of the application 180 when operating the servers 4 to 9 at remote locations via the network 13. FIG. 17 is a process flowchart of initialization of the application 180. FIG. 18 is a process flowchart of mouse event generation of the application 180. FIG. 19 is a flowchart of the end process of the application 180. 20, 21, and 22 show the processing sequence in FIG. 13.
In FIG. 16, the user starts the application 180 in order to start remote operation. In step S0901, the application 180 performs initialization processing.

  In S1001 of FIG. 17, the type of the servers 4-9 connected to the KVM apparatuses 2 and 3 via the network is read from the memory 181 and the application 180 displays buttons representing the servers 4-9. In step S <b> 1002, the device driver 160 is opened, and is ready to transmit an instruction request from the application 180 to the interface control unit 66 and to transmit a pointing device and a key code from the interface control unit 66 to the application 180. During the remote operation, the pointing device data is not transmitted to the OS 170, and the user cannot move the mouse cursor, so that the button of the application 180 cannot be pressed. Therefore, in S1003, a thread for executing emulation of the pointing device 11 shown in S1004 to S1007 during remote operation is created and a mouse event is generated to enable mouse operation.

Returning to FIG. 16, in S0902, the user waits until the user presses the button B, and in S0903, it is confirmed which button is pressed. When the user presses any button B of the servers 4 to 6, in S 0904, the application 180 reads communication information to the servers 4 to 9 corresponding to the pressed button B from the memory 181 and stores the information in the memory 63. Write data. If the remote operation is not being performed in S0905, in S0906, the application 180 sends an application transmission start request, a key code storage start request, a pointing device data storage start request, a key code cutoff start request, and a pointing device data cutoff to the interface control unit 66. A start request and a network transmission start request are transmitted. (S1101 in FIG. 20)
In step S1102, the interface control unit 66 receives the application transmission start request and transmits the key code and pointing device data stored on the memory 63 to the application 180. In S1103, the key code receiving unit 61 receives the key code storage start request and is set to store the key code received from the keyboard 10 in the memory 63. In S 1104, the pointing device data receiving unit 62 is set to receive the pointing device data storage start request and store the pointing device data received from the pointing device 11 in the memory 63.

  In S1105, the key code control unit 64 is set to receive the key code blocking start request and block transmission of the key code received from the key code receiving unit 61 to the OS 170. In S1106, the pointing device data receiving unit 62 is set to receive the pointing device blocking start request and block transmission of the pointing device data received from the pointing device data receiving unit 62 to the OS 70.

  In step S <b> 1107, the server communication unit 67 is set to receive the network transmission start request and transmit the key code and pointing device data read from the memory 63 to the communication destination information stored in the memory 63. Here, the transmission of the key code and the pointing device data to the OS 170 is blocked, and the key code and the pointing device data are transmitted to the application 180 and the servers 4 to 6.

  Returning to FIG. 16, in S0907, the application 180 saves that the remote operation is being performed in the memory 181 and waits until the user presses the button again. FIG. 15 is a diagram illustrating a GUI of the application 180 during remote operation. A desktop image of the personal computer being remotely operated is displayed on the screen display unit 190.

  First, transmission of a key code will be described. The key code flows in the order of the keyboard 10, the key code receiving unit 61, the key code control unit 64, the memory 63, the server communication unit 67, the communication device 12, and the KVM devices 2 and 3 via the network. A key code is sent. At the same time, the key code flows in the order of the keyboard 10, the key code receiving unit 61, the key code control unit 64, the memory 63, the interface control unit 66, and the application 180, and is also transmitted to the application 180. Accordingly, the servers 4 to 9 can be remotely operated without being transmitted to the OS 170.

  In S1201, a key code is generated by operating the keyboard 10, and the key code receiving unit 61 transmits the key code to the key code control unit 64 in S1202. Further, since the key code is stored by the key code storage start request, the key code is stored in the memory 63. In S <b> 1203, the key code control unit 64 receives the key code from the key code receiving unit 61. Since the key code transmission to the OS 170 is blocked by the key code blocking start request, the transmission of the key code to the OS 170 is blocked.

  In S1204, the interface control unit 66 reads the key code stored in the memory 63 by the key code receiving unit 61 from the memory 63 and transmits it to the application 180 in response to the application transmission start request. Send. In step S1205, the application 180 receives the key code. In S1206, the server communication unit 67 reads the key code stored by the key code receiving unit 61 from the memory 63 and transmits the key code to the network 13 in response to the network transmission start request. Send.

  Next, the flow of pointing device data will be described. The pointing device data flows in the order of the pointing device 11, the pointing device data receiving unit 62, the pointing device data control unit 65, the memory 63, the server communication unit 67, the communication device 12, and the KVM devices 2 and 3 via the network. Pointing device data is transmitted to 4-9. At the same time, the pointing device data flows in the order of the pointing device 11, the pointing device data receiving unit 62, the pointing device data control unit 65, the memory 63, the interface control unit 66, and the application 180, and is also transmitted to the application 180. As a result, the servers 4 to 9 can be remotely operated without being transmitted to the OS 170.

  In S1207, the pointing device data is generated by the operation of the pointing device 11, and in S1208, the pointing device data receiving unit 62 transmits the pointing device data to the pointing device data control unit 65, and the pointing device data storage start request is received. Since the data is stored, the pointing device data is stored in the memory 63.

  In S1209, the pointing device data control unit 65 has received the pointing device data from the pointing device data receiving unit 62, and is in a state of blocking the transmission of the pointing device data to the OS 170 by the pointing device data blocking start request. Transmission of pointing device data to the OS 170 is blocked. In S1210, the interface control unit 66 is in a state of reading the key code stored in the memory 63 by the pointing device data receiving unit 62 from the memory 63 and transmitting it to the application 180 in response to an application transmission start request. Send to.

  The application 180 receives the pointing device data using the thread created in S1003 of FIG. At this time, it is confirmed that the pointing device data has been received in S1005, and mouse emulation is executed based on the data obtained from the pointing device data received from the interface control unit 66 in S1006.

  In S1212, the server communication unit 67 is in a state of reading the pointing device data stored by the pointing device data receiving unit 62 from the memory 63 and transmitting it to the network 13 in response to a network transmission start request. Send pointing device data to

  Thereafter, the key code and the pointing device data sent to the KVM devices 2 and 3 via the network are transmitted to the servers 4 to 9 to be operated by the KVM devices 2 and 3 via the network, thereby enabling remote operation. Since the key code and the pointing device data are not transmitted to the OS 170 of the console PC 151, the key code is not transmitted to other key code monitoring applications. Further, since the application 180 generates a mouse event by a thread based on the pointing device data and executes mouse emulation, the button of the application 180 can be pressed.

Next, when the user presses the button B of the console PC 151, in S0908 of FIG. 16, it is confirmed whether or not the remote operation is being performed from the memory 181. If the remote operation is being performed, the application 180 displays the interface control unit in S0909. An application transmission end request, a key code storage end request, a pointing device data storage end request, a key code cutoff end request, a pointing device data cutoff end request, and a network transmission end request are transmitted to 66. (S1301 in FIG. 22)
In step S1302, the interface control unit 66 receives the application transmission end request, and is set not to transmit to the application 180. In S1303, since the key code receiving unit 61 has received the key code storage end request, the key code receiving unit 61 is set not to store the key code received from the keyboard 10 in the memory 63. In S1304, since the pointing device data receiving unit 62 has received the pointing device data storage end request, it is set not to store in the memory 63.

  In S1305, since the key code control unit 64 has received the key code cutoff end request, the key code control unit 64 is set to transmit the key code to the OS 70. In S1306, since the pointing device data receiving unit 62 has received the pointing device cutoff end request, the pointing device data receiving unit 62 is set to transmit the pointing device data to the OS. In step S1307, the server communication unit 67 receives the network transmission end request, and is set not to transmit to the network 13.

  In step S0910, the application 180 stores that the remote operation is not being performed in the memory 181 and waits until the user presses the button B again. Thereafter, when the keyboard 10 is operated, the key code receiving unit 61 receives the key code and transmits it to the key code control unit 64 in S1309 of FIG. Thereafter, the key code control unit 64 transmits the key code to the OS 170 in S1310. When the pointing device 11 is operated, the pointing device data receiving unit 62 receives the pointing device data and transmits it to the pointing device data control unit 65 in S1312. Thereafter, the pointing device data control unit 65 transmits the pointing device data to the OS 170 in S1313.

  If the user presses the end button B, or if the remote operation is in progress, the remote operation is terminated in S0912 in FIG. 16 in the same manner as when the button B of the console PC 151 is pressed. In the termination process, the thread for executing mouse emulation during remote operation is terminated (S1007 in FIG. 19), and the communication with the interface control unit 66 is stopped by closing the driver in S1008. Then, the application 180 is terminated.

  The input key code and pointing device data can be transmitted to the KVM devices 2 and 3 via the network without being transmitted to the OS 170, are not affected by other key code monitoring applications, and the special key is transmitted via the network. Since it can be transmitted to 2 and 3, a normal key operation can be realized even in a remote operation via a network.

  According to the second embodiment, the key code and the pointing device data of the keyboard 10 and the pointing device 11 can be transmitted to the KVM devices 2 and 3 on the network 13 without transmitting to the OS 170. In addition, the key code and the pointing device data of the keyboard 10 and the pointing device 11 can be transmitted to the application 180 operating on the OS 10 without transmitting to the OS 170.

As a result, the special key can be transmitted to the servers 4 to 9 without being influenced by other applications that monitor the key input. Therefore, a normal key operation can be realized also in a remote operation via a network.
Further, since the special key is not transmitted by the GUI, the key input operation can be continuously performed. Further, the GUI such as buttons does not increase.

  The console PCs 51 and 151 correspond to the information processing apparatuses in the claims, the device drivers 60 and 160 correspond to the programs in the claims, and the applications 80 and 180 are the remote operation applications in the claims. It corresponds to. The device drivers 60 and 160, which are programs, can be recorded and distributed on a recording medium such as a CD-ROM.

  Although the preferred embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications and changes can be made within the scope of the gist of the present invention described in the claims. It can be changed.

2, 3 KVM device via network 4-9 Server 10 Keyboard 11 Pointing device 12 Communication device 13 Network 51 Console PC
60, 160 Device driver 61 Key code receiving unit 62 Pointing device data receiving unit 63 Memory 64 Key code control unit 65 Pointing device data control unit 66 Interface control unit 67 Server communication unit 70, 170 OS
80, 180 application 181 memory

Claims (9)

In an information processing apparatus that remotely controls a server existing on a network,
After receiving the server operation request from the remote operation application, the pointing device data storage start request for storing the pointing device data output from the pointing device in a predetermined memory, and the pointing to the OS in the information processing apparatus An interface control unit for outputting a pointing device data blocking start request for blocking transmission of device data and a network transmission starting request for transmitting the pointing device data stored in the memory to the server;
In response to said pointing device data storage start request, the pointing device data outputted from the pointing device obtained before the OS in the information processing apparatus acquires, said pointing with saving the pointing device data in said memory A pointing device data receiving unit for transmitting device data to the pointing device data control unit ;
A pointing device data control unit that blocks transmission of the pointing device data received from the pointing device data receiving unit to the OS in response to the pointing device data blocking start request ;
A communication unit for transmitting the pointing device data stored in the memory to the server in response to the network transmission start request ;
The information processing apparatus , wherein the pointing device data stored in the memory is further transmitted to the remote operation application via the interface control unit . The remote operation application creates a thread for executing emulation of a pointing device during remote operation of the server, and the thread receives the pointing device data stored in the memory via the interface control unit. The information processing apparatus according to claim 1 , wherein emulation of the pointing device is executed based on the received pointing device data . The information processing apparatus according to claim 1, wherein the information processing apparatus is a KVM apparatus. A system comprising a plurality of servers and an information processing device for remotely operating the servers via a network,
The system according to claim 1, wherein the information processing apparatus is the information processing apparatus according to claim 1. A method for remotely operating an information processing apparatus for remotely operating a server existing on a network,
After receiving the server operation request from the remote operation application, the pointing device data storage start request for storing the pointing device data output from the pointing device in a predetermined memory, and the pointing to the OS in the information processing apparatus An output step of outputting a pointing device data blocking start request for blocking transmission of device data, and a network transmission start request for transmitting pointing device data stored in the memory to the server;
In response to said pointing device data storage start request, the together with the pointing device data outputted from the pointing device obtained before the OS in the information processing apparatus acquires and stores the pointing device data in a predetermined memory A storing step for transmitting the pointing device data to the blocking step ;
A blocking step of blocking transmission of the pointing device data received from the storing step to the OS in response to the pointing device data blocking start request ;
In response to said network transmission start request, a pointing device data stored in the memory have a transmission step of transmitting to said server,
The remote operation method characterized in that the pointing device data stored in the memory is further transmitted to the remote operation application . The remote operation application creates a thread for executing emulation of a pointing device during remote operation of the server, the thread receives the pointing device data stored in the memory, and based on the received pointing device data 6. The remote operation method according to claim 5 , wherein emulation of the pointing device is executed . To remotely control a server on the network,
After receiving the server operation request from the remote operation application, the pointing device data storage start request for storing the pointing device data output from the pointing device in a predetermined memory, and the pointing to the OS in the information processing apparatus An interface control unit for outputting a pointing device data blocking start request for blocking transmission of device data and a network transmission starting request for transmitting the pointing device data stored in the memory to the server;
In response to said pointing device data storage start request, the pointing device data outputted from the pointing device obtained before the OS in the information processing apparatus acquires, said pointing with saving the pointing device data in said memory A pointing device data receiving unit for transmitting device data to the pointing device data control unit;
A pointing device data control unit that blocks transmission of the pointing device data received from the pointing device data receiving unit to the OS in response to the pointing device data blocking start request ; and
In response to the network transmission start request, the pointing device data stored in the memory is caused to function as a communication unit that transmits to the server ,
The pointing device data stored in the memory is further transmitted to the remote operation application via the interface control unit . The remote operation application creates a thread for executing emulation of a pointing device during remote operation of the server, and the thread receives the pointing device data stored in the memory via the interface control unit. 8. The program according to claim 7 , wherein emulation of the pointing device is executed based on the received pointing device data . A recording medium on which the program according to claim 7 or 8 is recorded.

Images