JP6750618B2 - Key control system, virtualization server, key control method, program - Google Patents

Description

The present invention, key control system, virtualization server, key control method, and a program.

A technique is known in which a keyboard of a terminal device can be used on the virtual machine by transmitting information indicating a key press and a key release from the terminal device to a virtual machine operating on a server ( See, for example, Patent Document 1.
For example, when a key is pressed on the terminal device, information indicating that the key has been pressed is transmitted to the virtual machine. Further, when the key is released in the terminal device, information indicating that the key is released is transmitted to the virtual machine.

International Publication No. 2010/109681

By the way, some virtual machines consider that the same key is continuously pressed when the same key is continuously pressed for a predetermined time. In this case, the transmission of the information indicating the release of the key is delayed, and the same key may be continuously input in the virtual machine against the user's intention.
An object of the present invention is to provide key control system that solves the problems described above, the virtualization server, key control method, a program.

According to a first aspect of the present invention, the key control system, each time a an event detecting unit for detecting the occurrence of a key event showing pressing and Hanareue key in the terminal device, the key event showing pressing of a key is generated A release event generation unit that generates a key event indicating the release of the key, the key event indicating the key press detected by the event detection unit, and the key event generated by the release event generation unit. And an output unit for outputting to a virtual machine.

According to a second aspect of the present invention, the key control method, each time the detecting the occurrence of a key event showing pressing and Hanareue key in the terminal device, the key event showing pressing of a key is generated, The method further includes a step of generating a key event indicating the release of the key, and a step of outputting the detected key event indicating the pressed key and the generated key event to a virtual machine.

According to the third aspect of the present invention, the virtualization server includes a virtualization unit that operates a virtual machine, a reception unit that receives a key event indicating a key press and a key release from a terminal device, and a key press. Each time a key event indicating the above is received, a release event generating unit that generates a key event indicating that the key is released, and the key event and the release event generating unit that indicate pressing of the key received by the receiving unit. And an output unit that outputs the key event generated by the virtual machine to the virtual machine.

According to a fourth aspect of the present invention, a key control method includes a step of operating a virtual machine, a step of receiving a key event indicating a key press and a key release from a terminal device, and a key indicating a key press. Each time an event is received, a step of generating a key event indicating the release of the key, and a step of outputting the key event indicating the pressing of the received key and the generated key event to the virtual machine are performed. Prepare

According to the fifth aspect of the present invention, a program causes a computer to perform a virtualizing unit that operates a virtual machine, a receiving unit that receives a key event indicating a key press and a key release from a terminal device, and a key press. Each time the key event shown is received, a release event generation unit that generates a key event that indicates the release of the key, the key event that indicates pressing of the key received by the reception unit, and the release event generation unit that generate The key event is output to the virtual machine and functions as an output unit.

According to at least one of the above aspects of the present invention, when a key event indicating the pressing of a key occurs, the key event indicating the release of the key is output to the virtual machine. As a result, it is possible to prevent the same key from being continuously input against the user's intention in the virtual machine due to the delay in the transmission of the information indicating the release of the key.

It is a schematic block diagram which shows the structure of the virtualization system which concerns on 1st Embodiment. It is a flow chart which shows operation of the terminal unit concerning a 1st embodiment. 6 is a flowchart showing an operation of the hypervisor according to the first embodiment. It is a schematic block diagram which shows the structure of the virtualization system which concerns on 2nd Embodiment. 9 is a flowchart showing the operation of the hypervisor according to the second embodiment. It is a flowchart which shows operation|movement of the hypervisor which concerns on 3rd Embodiment. It is a schematic block diagram showing a basic configuration of a virtualization system. It is a schematic block diagram which shows the structure of the computer which concerns on at least 1 embodiment.

<<First Embodiment>>
Hereinafter, embodiments will be described in detail with reference to the drawings.
FIG. 1 is a schematic block diagram showing the configuration of the virtualization system according to the first embodiment.
The virtualization system 1 includes a terminal device 20 connected to the keyboard 10 in a wired or wireless manner, and a virtualization server 30 that operates a virtual machine.
The terminal device 20 and the virtualization server 30 are connected via a network.

The terminal device 20 is a device that transmits an input from the keyboard 10 to a virtual machine that operates on the virtualization server 30. The terminal device 20 is realized by a computer such as a PC, a server, or a smartphone. The terminal device 20 includes an event detection unit 21, a press event generation unit 22, a key code conversion unit 23, and a transmission unit 24 by executing the virtual machine connection program.
The event detection unit 21 detects the occurrence of a key event indicating the pressing and releasing of a key on the keyboard 10.
The press event generation unit 22 does not detect the key event indicating the release of the key within a predetermined continuous input determination time (for example, 1 second) after the event detection unit 21 detects the key event indicating the press of the key. In this case, a key event indicating pressing of the key is generated for each continuous input determination time.
For example, when the same key is pressed for 3 seconds, the press event generating unit 22 generates a press event indicating that the key has been pressed once per second.
The key code conversion unit 23 determines the key code of the key indicated by the key event detected by the event detection unit 21 and the key event generated by the press event generation unit 22 as a key code related to the OS (Operating System) of the terminal device 20. To a key code of a predetermined code system such as a Linux (registered trademark) key code.
The transmission unit 24 stores the key event obtained by converting the key code by the key code conversion unit 23 in a packet and transmits the packet to the virtualization server 30.

The virtualization server 30 transmits the key event received from the terminal device 20 to the virtual machine operating in the device itself.
The virtualization server 30 executes the virtual machine management program to manage the transfer destination of the received packet, the hypervisor 32 that manages the virtual machine, and the virtualization unit 33 that executes the virtual machine. Equipped with. The transfer board 31 is an example of a receiving unit that receives a key event indicating a key press and a key release from the terminal device 20.
The hypervisor 32 includes an event acquisition unit 321, a key code conversion unit 322, a separation event generation unit 323, and an output unit 324.
The event acquisition unit 321 acquires the key event transferred from the transfer board 31.
The key code conversion unit 322 converts the key code related to the key event acquired by the event acquisition unit 321 into the key code related to the OS of the virtual machine operating in the virtualization unit 33.
When the key event converted by the key code conversion unit 322 indicates the pressing of a key, the release event generation unit 323 generates a key event indicating the release of the key.
The output unit 324 outputs the key event converted by the key code conversion unit 322 and the key event generated by the separation event generation unit 323 to the virtual machine operating in the virtualization unit 33.

With the above configuration, the virtualization system 1 can prevent unintended continuous input due to packet delay, which is a delay in the transmission of information indicating the release of a key.

Next, the operation of the virtualization system 1 according to this embodiment will be described.
FIG. 2 is a flowchart showing the operation of the terminal device according to the first embodiment.
When the terminal device 20 is connected to the virtualization server 30 by the virtual machine connection program, the event detection unit 21 determines whether or not a key event has occurred due to pressing or releasing the keyboard 10 (step S1).
When the event detection unit 21 detects the occurrence of a key event (step S1: YES), the key code conversion unit 23 converts the key code included in the key event into a key code of a predetermined system (step S2).
Next, the transmission unit 24 stores the key event converted by the key code conversion unit 23 in a packet and transmits it to the transfer board 31 (step S3).

On the other hand, when the event detection unit 21 does not detect the occurrence of the key event (step S1: NO), the pressed event generation unit 22 does not generate the key event indicating the lift after the generation of the key event indicating the press. It is determined whether or not there is a key of which the pressing time is the continuous input determination time or more (step S4). Note that the pressing time is the elapsed time from the time when the key event indicating the pressing of the key was last transmitted.
Among the keys that have not been released, if there is a key whose pressing time is equal to or longer than the continuous input determination time (step S4: YES), the pressing event generation unit 22 generates a key event indicating pressing of the key ( Step S5).
Then, the event detection unit 21 converts the key code included in the key event into a key code of a predetermined system (step S2). Next, the transmission unit 24 stores the key event converted by the key code conversion unit 23 in a packet and transmits it to the transfer board 31 (step S3).

If the packet storing the key event is transmitted in step S3, or if there is no key that has not been lifted and the pressing time is longer than the continuous input determination time (step S4: NO), the terminal device 20 , It is determined whether or not the connection with the virtualization server 30 has been disconnected (step S6).
When the connection with the virtualization server 30 is not disconnected (step S6: NO), the terminal device 20 returns the process to step S1 and determines again whether or not a key event has occurred. On the other hand, when the connection with the virtualization server 30 is disconnected (step S6: YES), the terminal device 20 ends the process.
Through the above processing, the terminal device 20 can transmit the key event to the virtualization server 30.

FIG. 3 is a flowchart showing the operation of the hypervisor 32 according to the first embodiment.
When the terminal device 20 transmits a packet storing a key event to the virtualization server 30, the transfer board 31 of the virtualization server 30 receives the packet. Next, the transfer board 31 transfers the packet to the hypervisor 32.

The event acquisition unit 321 of the hypervisor 32 acquires a packet from the transfer board 31 (step S101). Next, the key code conversion unit 322 converts the key code indicated by the key event acquired by the event acquisition unit 321 into a key code related to the OS of the virtual machine operating in the virtualization unit 33 (step S102).
Next, the output unit 324 determines whether or not the key event indicates a key press (step S103). When the key event indicates that the key is pressed (step S103: YES), the output unit 324 outputs the key event converted by the key code conversion unit 322 to the virtualization unit 33 (step S104).
Next, the release event generation unit 323 generates a key event indicating the release of the key indicated by the key event converted by the key code conversion unit 322. Next, the output unit 324 outputs the key event generated by the separation event generation unit 323 to the virtualization unit 33 (step S105), and ends the process.

On the other hand, when the key event converted by the key code conversion unit 322 indicates the release of the key (step S103: NO), the output unit 324 ends the process without outputting the key event to the virtualization unit 33. This is because the key event indicating the release of the key has already been output to the virtualization unit 33 in step S105.

In this way, the virtualization system 1 according to the present embodiment, when a key event indicating the pressing of a key is detected, outputs the key event indicating the release of the key to the virtual machine together with the key event.
As a result, the virtual machine receives a key event indicating the release of the key immediately after the key event indicating the press of the key regardless of the transmission delay of the packet storing the key event. The system 1 can prevent unintended continuous input from occurring.

In addition, in the virtualization system 1 according to the present embodiment, the virtualization server 30 that operates the virtual machine generates a key event indicating a key release. With this, it is possible to reliably transmit the release of the key to the virtual machine.
Note that, in other embodiments, the present invention is not limited to this, and the terminal device 20 may include the separation event generation unit 323.

In addition, in the present embodiment, when there is a key that is not lifted during the continuous input determination time, the press event generation unit 22 outputs a key event indicating that the key is pressed each time the continuous input determination time elapses. To generate. As a result, the key event indicating the pressing of the same key and the key event indicating the release of the key are input to the virtualization unit 33 that executes the virtual machine at each continuous input determination time.
Therefore, in the virtualization system 1 according to the present embodiment, the key event indicating the release of the key is input to the virtual machine immediately after the key event indicating the press of the key, but the key is continuously pressed by the long press of the key. Input can be realized. For example, according to the virtualization system 1 according to the present embodiment, it is possible to continuously input a direction key and a delete key.
Although the terminal device 20 includes the press event generation unit 22 in the present embodiment, the present invention is not limited to this. For example, in another embodiment, the virtualization server 30 may include the press event generation unit 22. Further, when there is no need for continuous input, the virtualization system 1 according to another embodiment may not include the press event generation unit 22.

Further, the terminal device 20 according to the present embodiment transmits a key event in which the key code related to the OS of the device itself is converted into the key code related to the predetermined system. The virtualization server 30 also converts the key code related to the received key event into a key code related to the OS of the virtual machine.
With this, even when the key map is different between the terminal device 20 and the virtual machine, it is possible to prevent a difference in the characters input between the terminal device 20 and the virtual machine.

<<Second Embodiment>>
Next, a second embodiment will be described. FIG. 4 is a schematic block diagram showing the configuration of the virtualization system according to the second embodiment.
A key provided on the keyboard 10 may include a meta key that requires simultaneous pressing with other keys (hereinafter, referred to as normal keys). Examples of the meta key include a shift key and a control key.
The virtualization system 1 according to the second embodiment can prevent the same key from being continuously input against the user's intention even when the meta key and the normal key are simultaneously pressed.

The virtualization system 1 according to the second embodiment is different from the first embodiment in the configuration of the virtualization server 30. Specifically, the virtualization server 30 according to the second embodiment further includes a pressed key management unit 325 and a meta key event generation unit 326 in addition to the configuration of the first embodiment.
The pressed key management unit 325 manages which key is continuously pressed in the terminal device 20.
Specifically, the pressed key management unit 325 records the key code related to the key event in the internal memory when the key event indicating the press is detected, and when the key event indicating the release is detected. , The key code related to the key event is deleted from the internal memory. As a result, the pressed key management unit 325 can identify the key that is being pressed by referring to the internal memory.
The meta key event generation unit 326 generates a key event indicating pressing and releasing of the meta key.

Next, the operation of the virtualization system 1 according to the second embodiment will be described. The operation of the terminal device 20 is the same as in the first embodiment.
FIG. 5 is a flowchart showing the operation of the hypervisor 32 according to the second embodiment.
When the terminal device 20 transmits a packet storing a key event to the virtualization server 30, the transfer board 31 of the virtualization server 30 receives the packet. Next, the transfer board 31 transfers the packet to the hypervisor 32.

The event acquisition unit 321 of the hypervisor 32 acquires a packet from the transfer board 31 (step S201). Next, the key code conversion unit 322 converts the key code indicated by the key event acquired by the event acquisition unit 321 into a key code related to the OS of the virtual machine operating in the virtualization unit 33 (step S202).
Next, the pressed key management unit 325 determines whether or not the key event indicates pressing of a key (step S203). When the key event indicates that the key has been pressed (step S203: YES), the pressed key management unit 325 stores the key code related to the key event in the internal memory (step S204). As a result, the pressed key management unit 325 can identify that the key associated with the key code is pressed in the terminal device 20 by referring to the internal memory.

Next, the pressed key management unit 325 refers to the internal memory and determines whether or not the meta key is pressed (step S205). That is, the pressed key management unit 325 determines whether or not the key code indicating the meta key is recorded in the internal memory.
When the meta key is not pressed (step S205: NO), the output unit 324 outputs the key event converted by the key code conversion unit 322 in step S202 to the virtualization unit 33 (step S206).
Next, the release event generation unit 323 generates a key event indicating the release of the key indicated by the key event converted by the key code conversion unit 322. Next, the output unit 324 outputs the key event generated by the separation event generation unit 323 to the virtualization unit 33 (step S207), and ends the processing.

On the other hand, when the meta key is pressed (step S205: YES), the meta key event generation unit 326 generates a key event indicating that the meta key determined to be pressed is pressed.
Next, the output unit 324 outputs the key event generated by the meta key event generation unit 326 to the virtualization unit 33 (step S208).
Next, the output unit 324 outputs the key event converted by the key code conversion unit 322 in step S202 to the virtualization unit 33 (step S209).
Next, the release event generation unit 323 generates a key event indicating the release of the key indicated by the key event converted by the key code conversion unit 322.
Next, the output unit 324 outputs the key event generated by the separation event generation unit 323 to the virtualization unit 33 (step S210).
Next, the release event generation unit 323 generates a key event indicating the key release indicated by the key event generated by the meta key event generation unit 326. Then, the output unit 324 outputs the key event (release of the meta key) generated by the separation event generation unit 323 to the virtualization unit 33 (step S211), and ends the processing.

On the other hand, when the key event converted by the key code conversion unit 322 in step S202 indicates the release of the key (step S203: NO), the pressed key management unit 325 determines that the key indicated by the key event recorded in the internal memory. The code (that is, the key code of the key corresponding to the key event) is deleted (step S212), and the process ends. Thereby, the pressed key management unit 325 can identify that the key associated with the key code is not pressed in the terminal device 20 by referring to the internal memory.

As described above, in the virtualization system 1 according to the present embodiment, when the pressing of another key is detected while the meta key is pressed, the key event indicating the pressing of the meta key and the detected pressing of the key are performed. The key event indicating the key event and the key event indicating the release of these keys are output to the virtual machine.
As a result, the virtualization system 1 according to the present embodiment allows the meta key and the normal key to be output even though the key event indicating the release of the key is input to the virtual machine immediately after the key event indicating the press of the key. Simultaneous pressing can be realized.

<<Third Embodiment>>
Next, a third embodiment will be described. Similar to the second embodiment, the third embodiment prevents the same key from being continuously input against the user's intention even when the meta key and the normal key are simultaneously pressed.
The virtualization system 1 according to the third embodiment has the same configuration as the first embodiment shown in FIG.

The operation of the virtualization system 1 according to the third embodiment will be described. The operation of the terminal device 20 is the same as in the first embodiment.
FIG. 6 is a flowchart showing the operation of the hypervisor according to the third embodiment.
When the terminal device 20 transmits a packet storing a key event to the virtualization server 30, the transfer board 31 of the virtualization server 30 receives the packet. Next, the transfer board 31 transfers the packet to the hypervisor 32.

The event acquisition unit 321 of the hypervisor 32 acquires a packet from the transfer board 31 (step S301). Next, the key code conversion unit 322 converts the key code indicated by the key event acquired by the event acquisition unit 321 into a key code related to the OS of the virtual machine operating in the virtualization unit 33 (step S302).
Next, the output unit 324 determines whether or not the key event indicates a key press (step S303). When the key event indicates pressing of a key (step S303: YES), the output unit 324 outputs the key event converted by the key code conversion unit 322 to the virtualization unit 33 (step S304).

Next, the release event generation unit 323 determines whether the key code related to the key event indicates a meta key (step S305). When the key code related to the key event indicates a normal key (step S305: NO), the release event generation unit 323 generates a key event indicating the release of the key indicated by the key event converted by the key code conversion unit 322. .. Next, the output unit 324 outputs the key event generated by the separation event generation unit 323 to the virtualization unit 33 (step S306), and ends the processing.
On the other hand, when the key code related to the key event indicates the meta key (step S305: YES), the separation event generation unit 323 does not generate the key event indicating the separation of the meta key.
As a result, in the virtual machine executed by the virtualization unit 33, the meta key is in a continuously pressed state.

If the key event converted by the key code conversion unit 322 in step S302 indicates the release of the key (step S303: NO), the output unit 324 determines whether the key code related to the key event indicates a meta key. (Step S307). When the key code related to the key event indicates a normal key (step S307: NO), the output unit 324 ends the process without outputting the key event to the virtualization unit 33.
On the other hand, when the key code related to the key event indicates the meta key (step S307: YES), the output unit 324 outputs the key event (movement of the meta key) converted by the key code conversion unit 322 to the virtualization unit 33 ( In step S308), the process ends. As a result, the continuation of the pressing of the meta key in the virtual machine executed by the virtualization unit 33 ends.

As described above, the separation event generation unit 323 according to the present embodiment does not generate the key event indicating the separation of the meta key, and the output unit 324 displays the key event indicating the separation of the meta key detected by the event detection unit 21. Is output to the virtual machine. As a result, the timing of pressing and releasing the meta key in the virtual machine is in line with the timing of pressing and releasing the meta key in the terminal device 20. Thus, the depression of the normal key input from the depression of the meta key to the release is treated as the depression of the meta key at the same time in the virtual machine.
Note that there is a possibility that the timing of releasing the meta key will be delayed due to the packet transmission delay. Does not occur.

Although a plurality of embodiments have been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes and the like can be made.
For example, although the output unit 324 according to the above-described first embodiment does not output the key event to the virtualization unit 33 when the key event indicates separation (see “Step S103: NO” in FIG. 3), It is not limited to this.
For example, the output unit 324 according to another embodiment may output the key event converted by the key code conversion unit 322 to the virtualization unit 33 regardless of whether the key event indicates pressing or releasing. .. In this case, the virtual machine ignores a key event indicating the release of a key that has not been pressed, that is, a key that has already been released.

<Basic configuration>
FIG. 7 is a schematic block diagram showing the basic configuration of the virtualization system.
In the above-described embodiment, the configuration shown in FIGS. 1 and 4 is described as one embodiment of the virtualization system 1, but the basic configuration of the virtualization system 1 is as shown in FIG. 7.
That is, the virtualization system 1 has the event detection unit 21, the separation event generation unit 323, and the output unit 324 as a basic configuration.

The event detection unit 21 detects the occurrence of a key event indicating the pressing and releasing of a key on the terminal device.
The release event generation unit 323 generates a key event indicating the release of the key when a key event indicating the pressing of the key occurs.
The output unit 324 outputs, to the virtual machine, a key event indicating the pressing of the key detected by the event detection unit 21 and a key event indicating the key separation generated by the separation event generation unit 323.
As a result, the virtualization system 1 can prevent the same key from being continuously input against the user's intention in the virtual machine due to the delay in the transmission of the information indicating the release of the key.

FIG. 8 is a schematic block diagram showing the configuration of a computer according to at least one embodiment.
The computer 90 includes a CPU 91, a main storage device 92, an auxiliary storage device 93, and an interface 94.
The above-described terminal device 20 and virtualization server 30 are installed in the computer 90, respectively. The operation of each processing unit described above is stored in the auxiliary storage device 93 in the form of a program (the above-described virtual machine connection program and virtual machine management program).
The CPU 91 reads the above program from the auxiliary storage device 93, expands it in the main storage device 92, and executes the above processing according to the program. Further, the CPU 91 reserves a storage area corresponding to each of the above-mentioned memories in the main storage device 92 according to the program.

Note that in at least one embodiment, the auxiliary storage device 93 is an example of a non-transitory tangible medium. Other examples of non-transitory tangible media include magnetic disks, magneto-optical disks, CD-ROMs, DVD-ROMs, semiconductor memories, etc. connected via the interface 94.
Further, when this program is distributed to the computer 90 via a communication line, the computer 90 to which the program is distributed may expand the program in the main storage device 92 and execute the above processing.

Further, the program may be a program for realizing some of the functions described above.
Further, the program may be a so-called difference file (difference program) that realizes the above-mentioned function in combination with another program already stored in the auxiliary storage device 93.

The whole or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes.

(Appendix 1)
An event detection unit that detects the occurrence of a key event indicating the pressing and releasing of a key in the terminal device,
When a key event indicating the pressing of a key occurs, a release event generating unit that generates a key event indicating the lifting of the key, and the key event indicating the pressing of the key detected by the event detection unit and the lifting An output unit that outputs the key event generated by the event generation unit to a virtual machine.

(Appendix 2)
When there is a key that is not lifted up during a predetermined continuous input determination time, a pressing event generation unit that generates a key event indicating pressing of the key is provided each time the continuous input determination time elapses.
The output unit outputs the key event indicating a key press detected by the event detection unit, the key event generated by the press event generation unit, and the key event generated by the release event generation unit to the virtual machine. The key control system according to appendix 1.

(Appendix 3)
When the event detecting unit detects pressing of another key while the meta key is pressed, the output unit indicates a key event indicating pressing of the meta key, and pressing of a key detected by the event detecting unit. The key control system according to supplementary note 1 or supplementary note 2, wherein the key event, the key event generated by the separation event generation unit, and the key event indicating separation of the meta key are output to the virtual machine.

(Appendix 4)
The key event generated by the separation event generation unit is a key event indicating separation of a key other than a meta key,
The output unit includes the key event indicating the pressing of the key detected by the event detection unit, the key event indicating the separation of the meta key detected by the event detection unit, and the key generated by the separation event generation unit. The key control system according to supplementary note 1 or supplementary note 2, which outputs an event to the virtual machine.

(Appendix 5)
A key code conversion unit that converts a key code related to a key event into a key code used in a virtual machine,
The key control system according to any one of appendices 1 to 4, wherein the output unit outputs the key event, the key code of which is converted by the key code conversion unit, to the virtual machine.

(Appendix 6)
The event detection unit is provided in the terminal device,
The key control system according to any one of appendices 1 to 5, wherein the output unit is provided in a virtualization server that operates the virtual machine.

(Appendix 7)
Detecting the occurrence of a key event indicating the pressing and releasing of a key in the terminal device,
When a key event indicating the pressing of a key occurs, a step of generating a key event indicating the release of the key,
Outputting the detected key event indicating the pressing of the key and the generated key event to a virtual machine.

(Appendix 8)
A virtualization module that runs a virtual machine,
A receiving unit that receives a key event indicating a key press and a key release from the terminal device,
When a key event indicating a key press is received, a release event generation unit that generates a key event indicating the release of the key,
An output unit configured to output the key event indicating the key press received by the reception unit and the key event generated by the release event generation unit to the virtual machine.

(Appendix 9)
Running virtual machines,
Receiving a key event indicating a key press and a key release from the terminal device,
Generating a key event indicating the release of the key when a key event indicating the pressing of the key is received,
Outputting the received key event indicating the pressing of the key and the generated key event to the virtual machine.

(Appendix 10)
Computer,
A virtualization module that runs virtual machines,
A receiving unit that receives a key event indicating a key press and a key release from the terminal device,
When a key event indicating a key press is received, a release event generation unit that generates a key event indicating the release of the key,
A program for causing the key event received by the receiving unit and indicating the key press and the key event generated by the release event generating unit to output to the virtual machine.

(Appendix 11)
An event detection unit that detects the occurrence of a key event indicating the pressing and releasing of a key,
When there is a key that is not lifted up within a predetermined continuous input determination time, a press event generation unit that generates a key event indicating pressing of the key each time the continuous input determination time has elapsed,
A terminal device, comprising: the key event indicating the key press detected by the event detection unit and the transmission unit that transmits the key event generated by the press event generation unit to a virtual machine.

(Appendix 12)
Detecting the occurrence of a key event indicating the pressing and releasing of a key,
When there is a key that is not lifted up within a predetermined continuous input determination time, each time the continuous input determination time has elapsed, a step of generating a key event indicating pressing of the key,
And a step of transmitting the key event indicating the detected key press and the generated key event to a virtualization server including a virtual machine.

(Appendix 13)
Computer,
An event detection unit that detects the occurrence of a key event indicating the pressing and releasing of a key,
When there is a key that is not lifted up within a predetermined continuous input determination time, a press event generation unit that generates a key event indicating pressing of the key each time the continuous input determination time has elapsed,
A program for causing the key event indicating the key press detected by the event detection unit and the key event generated by the press event generation unit to function as a transmission unit that transmits to the virtual machine.

This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2015-105304 for which it applied on May 25, 2015, and takes in those the indications of all here.

According to the present invention, it is possible to prevent the same key from being continuously input against the intention of the user in the virtual machine due to the delay in the transmission of the information indicating the release of the key.

1 virtualization system 20 terminal device 21 event detection unit 22 pressed event generation unit 23 key code conversion unit 24 transmission unit 30 virtualization server 31 transfer infrastructure 32 hypervisor 33 virtualization unit 321 event acquisition unit 322 key code conversion unit 323 separation Event generation unit 324 Output unit

Claims (10)

An event detection unit that detects the occurrence of a key event indicating the pressing and releasing of a key in the terminal device,
Each time a key event indicating a key press occurs, a release event generation unit that generates a key event indicating the release of the key,
A key control system comprising: an output unit that outputs to the virtual machine the key event indicating the key press detected by the event detection unit and the key event generated by the release event generation unit. When there is a key that is not lifted up during a predetermined continuous input determination time, a pressing event generation unit that generates a key event indicating pressing of the key is provided each time the continuous input determination time elapses.
The release event generation unit generates a key event indicating the release of the key every time the key event generated by the press event generation unit occurs,
The output unit outputs the key event indicating a key press detected by the event detection unit, the key event generated by the press event generation unit, and the key event generated by the release event generation unit to the virtual machine. The key control system according to claim 1. When the event detecting unit detects pressing of another key while the meta key is pressed, the output unit indicates a key event indicating pressing of the meta key, and pressing of a key detected by the event detecting unit. The key control system according to claim 1, wherein the key event, the key event generated by the separation event generation unit, and the key event indicating separation of the meta key are output to the virtual machine. The event detection unit detects a key event indicating pressing and releasing of a meta key, and occurrence of pressing and releasing of a key other than the meta key,
The Hanareue event generation unit, each time the key event showing pressing of a key other than the meta key is generated, and generates a key event indicating Hanareue keys except the meta key,
When the key event detected by the event detection unit indicates pressing of the meta key, the output unit outputs the key event indicating pressing of the meta key detected by the event detecting unit to the virtual machine,
When the key event detected by the event detection unit indicates the separation of the meta key, the output unit outputs the key event indicating the separation of the meta key detected by the event detection unit to the virtual machine ,
When the key event detected by the event detecting unit indicates pressing of a key other than the meta key, the key event indicating the pressing of a key other than the meta key detected by the event detecting unit and the release event generating unit are generated. The key control system according to claim 1, wherein the key event indicating the release of a key other than the meta key is output to the virtual machine. A key code conversion unit that converts a key code related to a key event into a key code used in a virtual machine,
The key control system according to any one of claims 1 to 4, wherein the output unit outputs, to the virtual machine, a key event whose key code has been converted by the key code conversion unit. The event detection unit is provided in the terminal device,
The key control system according to claim 1, wherein the output unit is provided in a virtualization server that operates the virtual machine. Detecting the occurrence of a key event indicating the pressing and releasing of a key in the terminal device,
Each time a key event indicating a key press occurs, a step of generating a key event indicating the release of the key,
Outputting the detected key event indicating the pressing of the key and the generated key event to a virtual machine. A virtualization module that runs a virtual machine,
A receiving unit that receives a key event indicating a key press and a key release from the terminal device,
Whenever a key event indicating a key press is received, a release event generation unit that generates a key event indicating the release of the key,
An output unit configured to output the key event indicating the key press received by the reception unit and the key event generated by the release event generation unit to the virtual machine. Running virtual machines,
Receiving a key event indicating a key press and a key release from the terminal device,
Each time a key event indicating a key press is received, a step of generating a key event indicating the release of the key,
Outputting the received key event indicating the pressing of the key and the generated key event to the virtual machine. Computer,
A virtualization module that runs virtual machines,
A receiving unit that receives a key event indicating a key press and a key release from the terminal device,
Each time a key event indicating a key press is received, a release event generation unit that generates a key event indicating the release of the key,
A program for causing the key event received by the receiving unit and indicating the key press and the key event generated by the release event generating unit to output to the virtual machine.

Images