JP6745531B2 - Device server system, client device, information transfer control method and program - Google Patents

Description

The present invention relates to a device server system, a client device, an information transfer control method, and a program.

A device server system has been proposed that includes a device server connected to a network such as a wired LAN (Local Area Network) or a wireless LAN, and a client device connected to the network (see Non-Patent Document 1, for example). In this device server system, a USB (Universal Serial Bus) device connected from the client device to the device server can be used. As this type of device server system, there is also provided a system that employs a HID (Human Interface Device) such as a keyboard or a touch panel that executes information transfer based on the USB standard as a USB device.

Silex Technology Co., Ltd. home page <http://www.silex.jp/products/usbdeviceserver/ds520an.html>

However, when the HID is adopted as the USB device, if the communication between the client device and the device server is interrupted while the user is operating the HID, the HID cannot control the client device, and the processing is against the user's intention. May continue. For example, when the HID is a USB keyboard, if the communication between the client device and the device server is interrupted while the user is pressing and holding the key, the process corresponding to the key input is continued until the communication is restored. End up. Further, in the case where the HID is a touch panel compatible with USB, if the communication between the client device and the device server is interrupted while the user is performing the drag operation, the drag operation cannot be performed until the communication is restored. In this way, if the client device performs a process contrary to the user's intention due to the interruption of communication with the device server, the user may feel inconvenient.

The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a device server system, a client device, an information transfer control method, and a program that improve user convenience.

In order to achieve the above object, a device server system according to the present invention is
A client device,
A HID class USB device that transfers interrupt response information and causes the client device to perform processing ;
A device server to which the USB device is connected ,
The client device is connected to the device server via a network ,
A processing unit for executing a process corresponding to the interrupt response information that is transferred from the USB device,
A USB driver that generates interrupt request information for requesting the transfer of the interrupt response information to the USB device, and outputs the interrupt response information to the processing unit when the interrupt response information is acquired,
Dummy interrupt response information is obtained when the communication state between the client device and the device server is monitored and it is determined that the reference time has elapsed in the state where the communication between the client device and the device server is cut off. To the USB driver.

From another viewpoint, the client device according to the present invention is
A client device that is connected via a network to a device server to which a HID class USB device that transfers interrupt response information is connected, and that receives the interrupt response information transferred from the USB device via the device server. hand,
A processing unit that executes processing according to the interrupt response information transferred by the USB device;
A USB driver that generates interrupt request information for requesting the transfer of the interrupt response information to the USB device, and outputs the interrupt response information to the processing unit when the interrupt response information is acquired,
Monitoring the communication state between the self-device and the device server, if it is determined that the reference time has elapsed in the state where the communication between the self-device and the device server is cut off, the dummy interrupt response information is displayed. And a communication control unit for outputting to the USB driver.

From another viewpoint, the information transfer control method according to the present invention is
A client device that is connected via a network to a device server to which a USB device of HID class that transfers interrupt response information is connected, and that receives the interrupt response information transferred from the USB device via the device server. An information transfer control method for
A processing unit executing processing according to the interrupt response information transferred from the USB device;
A USB driver generating interrupt request information requesting transfer of the interrupt response information to the USB device;
When the USB driver acquires the interrupt response information, outputting the interrupt response information to the processing unit,
The communication control unit monitors the communication state between the client device and the device server, and determines that the reference time has elapsed in the state where the communication between the client device and the device server is cut off, Outputting dummy interrupt response information to the USB driver.

From another viewpoint, the program according to the present invention is
Computer,
A processing unit that executes a process according to the interrupt response information transferred by the HID class USB device that transfers the interrupt response information;
A USB driver that generates interrupt request information requesting the transfer of the interrupt response information to the USB device, and outputs the interrupt response information to the processing unit when the interrupt response information is acquired,
The communication state of the communication via the network between the client device and the device server to which the USB device is connected is monitored, and it is determined that the reference time has elapsed in the state where the communication with the device server is cut off. Then, it functions as a communication control unit that outputs dummy interrupt response information to the USB driver.

According to the present invention, the communication control unit monitors the communication state between the client device and the device server, and determines that the reference time has elapsed in the state where the communication between the client device and the device server is cut off. Then, the dummy interrupt response information is output to the USB driver. As a result, the state in which the processing unit cannot execute the process according to the process information is prevented from continuing while the communication between the client device and the device server is interrupted. Here, it is assumed that, for example, two pieces of processing information are transferred from the USB device to the client device and the processing in the processing unit is completed. In this case, even if the communication is interrupted immediately after one of the two pieces of processing information is transferred to the client device, the processing in the processing unit may be left uncompleted while the communication is interrupted. There is no. Therefore, the convenience of the user who uses the client device is improved.

It is a figure which shows the structure of the device server system which concerns on Embodiment 1 of this invention. FIG. 3 is a diagram showing a hardware configuration of a device server system according to the first embodiment. It is a figure which shows the function structure of the device server system which concerns on Embodiment 1. FIG. 6 is a sequence diagram showing an operation of the device server system according to the first embodiment. The contents of the interrupt response information according to the first embodiment are shown, where (A) is the case where the first key is pressed, (B) is the case where the key is not pressed, and (C) is the case where the second key is pressed. FIG. FIG. 6 is a sequence diagram showing an operation of the device server system according to the first embodiment. 5 is a flowchart showing an example of the flow of communication control processing executed by the communication control unit according to the first embodiment. 5 is a flowchart showing an example of the flow of communication control processing executed by the communication control unit according to the first embodiment. 5 is a flowchart showing an example of the flow of communication control processing executed by the communication control unit according to the first embodiment. It is a figure which shows the structure of the device server system which concerns on Embodiment 2 of this invention. It is a figure which shows the function structure of the device server system which concerns on Embodiment 2. FIG. 8 is a sequence diagram showing an operation of the device server system according to the second embodiment. FIG. 9 shows the contents of interrupt response information according to the second embodiment, where (A) shows a case where the touch panel is touched, and (B) shows a case where the touch panel is not touched (released). FIG. 8 is a sequence diagram showing an operation of the device server system according to the second embodiment. 9 is a flowchart showing an example of the flow of communication control processing executed by the communication control unit according to the second embodiment. 9 is a flowchart showing an example of the flow of communication control processing executed by the communication control unit according to the second embodiment. (A) is a figure for demonstrating operation|movement of the device server system which concerns on a comparative example, (B) is a figure for demonstrating operation|movement of the device server system which concerns on Embodiment 2. FIG.

(Embodiment 1)
A device server system according to an embodiment of the present invention will be described below with reference to the drawings.

The device server system according to the present embodiment includes a client device and a device server to which a HID (Human Interface Device) class USB device such as a USB keyboard is connected and which is capable of wireless communication with the client device. When the user operates the keyboard connected to the device server, the client device executes processing according to the keyboard operation.

As shown in FIG. 1, the device server system 1 according to the present embodiment includes a device server 11, a client device 12, a keyboard 13, and a display 14. The keyboard 13 uses interrupt (interrupt-in) transfer as a data transfer method. The keyboard 13 is a USB device of the HID class, and transfers processing information related to processing executed by the client device 12 (for example, information notifying that a key of the keyboard 13 has been pressed). When the keyboard 13 is connected to the client device 12 via the device server 11, the keyboard 13 transmits USB configuration information and descriptor information including information on the structure of the interrupt response packet and the cycle of outputting the interrupt request information via the device server 11. And sends it to the client device 12.

As shown in FIG. 2, the device server 11 includes a CPU (Central Processing Unit) 111, a main storage unit 112, an auxiliary storage unit 113, a wireless module 115, a USB interface (hereinafter, referred to as “I/F”) 116. The bus 117 connects these to each other. The main storage unit 112 is composed of a volatile memory and is used as a work area of the CPU 111. The auxiliary storage unit 113 is composed of a non-volatile memory. The wireless module 115 includes a wireless LAN controller. The wireless module 115 establishes a communication link with the client device 12 and performs wireless communication. The wireless module 115 includes a signal generation circuit that generates a wireless signal and an antenna. The wireless module 115 communicates by a communication method that conforms to a wireless LAN standard such as IEEE 802.11a, b, g, n. The USB I/F 116 is connected to the keyboard 13 and transmits/receives information to/from the keyboard 13.

In the device server 11, the CPU 111 controls the communication between the keyboard 13 and the client device 12, as shown in FIG. 3, by reading the program stored in the auxiliary storage unit 113 into the main storage unit 112 and executing the program. It functions as the conversion unit 1111. The conversion unit 1111 executes protocol conversion of the interrupt request packet received from the client device 12 or the interrupt response information received from the keyboard 13. The conversion unit 1111 extracts the interrupt request information included in the interrupt request packet received from the client device 12 and transmits the interrupt request information to the keyboard 13. The conversion unit 1111 also generates an interrupt response packet by encapsulating the interrupt response information received from the keyboard 13 and transmits it to the client device 12.

Returning to FIG. 2, the client device 12 includes a CPU 121, a main storage unit 122, an auxiliary storage unit 123, a wireless module 125, a video I/F 126, and a bus 127 connecting these to each other. The main storage unit 122 is composed of a volatile memory and is used as a work area of the CPU 121. The auxiliary storage unit 123 is composed of a non-volatile memory. The wireless module 125 includes a wireless LAN controller. The wireless module 125 establishes a communication link with the device server 11 and performs wireless communication. Like the wireless module 115, the wireless module 125 has a signal generation circuit and an antenna. The wireless module 125 also communicates by a communication method that conforms to a wireless LAN standard such as IEEE 802.11a, b, g, n. The video I/F 126 is connected to the display 14 and transmits a video signal to the display 14.

In the client device 12, the CPU 121 reads the program stored in the auxiliary storage unit 123 into the main storage unit 122 and executes the program, so that the processing unit 1211, the USB driver 1212, the communication control unit 1213, and the timekeeping unit 1213 as illustrated in FIG. It functions as the unit 1214. Further, the main storage unit 122 includes a request storage unit 1221 that stores interrupt request information corresponding to the dummy interrupt response information indicating that the communication control unit 1213 has pressed a key. The auxiliary storage unit 123 stores information about the structure of the interrupt response packet received from the keyboard 13 and the transmission cycle of the interrupt request information corresponding to the keyboard 13.

The processing unit 1211 executes processing according to key input information input from the USB driver 1212. The processing unit 1211 outputs to the display 14 the video information generated by executing the processing according to the key input information input from the USB driver 1212. The processing unit 1211 recognizes that the key continues to be pressed and then responds to the key press until the interrupt response information indicating the key press is transferred from the keyboard 13 until the interrupt response information indicating the key release is transferred. Continue processing.

When the USB driver 1212 receives the interrupt response information indicating that the key is pressed from the communication control unit 1213, the USB driver 1212 generates key press notification information for notifying that the key is pressed and outputs the key press notification information to the processing unit 1211. .. The USB driver 1212 also generates interrupt request information for the keyboard 13 and sends it to the communication control unit 1213.

The communication control unit 1213 generates an interrupt request packet including interrupt request information input from the USB driver 1212 and transmits the interrupt request packet to the device server 11. The communication control unit 1213 also extracts the key status information included in the interrupt response packet received from the device server 11 and outputs it to the USB driver 1212. Further, when the communication control unit 1213 receives the USB configuration information and the descriptor information transferred from the keyboard 13, the communication control unit 1213 acquires information about the structure of the interrupt response packet included therein and the cycle of outputting the interrupt request information. Then, the communication control unit 1213 causes the specification information storage unit 1231 to store information regarding the structure of the acquired interrupt response packet and the cycle for outputting the interrupt request information.

The timer unit 1214 is composed of, for example, a software timer, and measures the elapsed time after the communication between the communication control unit 1213 and the conversion unit 1111 of the device server 11 is cut off.

Next, the operation of the device server system 1 according to the present embodiment will be described with reference to FIGS. Note that, in FIGS. 4 and 6, illustration of the handshake packet transmission/reception transmitted from the USB driver 1212 to the keyboard is omitted. Further, it is assumed that the communication control unit 1213 has already acquired the information about the structure of the interrupt response packet received from the keyboard 13 and the transmission cycle of the interrupt request information corresponding to the keyboard 13. In FIG. 4, first, when the interrupt request information is output from the USB driver 1212 of the client device 12 to the communication control unit 1213 (step S2), the communication control unit 1213 generates an interrupt request packet including the interrupt request information. Subsequently, when the generated interrupt request packet is transmitted from the communication control unit 1213 to the device server 11 (step S3), the device server 11 receives the interrupt request packet and extracts the interrupt request information included therein. To do. After that, the interrupt request information is transferred from the device server 11 to the keyboard 13 (step S4).

Next, when the keyboard 13 receives the press of the first key while receiving the interrupt request information (step S4), the interrupt response information indicating the pressed state of the first key is transferred from the keyboard 13 to the device server 11. (Step S5). In this interrupt response information, for example, as shown in FIG. 5A, the key status information corresponding to the first key in the plurality of key status information is set to "1E", and the key status corresponding to other keys is set. The information is set to "00". This interrupt response information indicates that only the first key is pressed and the other keys are not pressed.

Returning to FIG. 4, on the other hand, the device server 11 creates an interrupt response packet by encapsulating the interrupt response information. The generated interrupt response packet is transmitted from the device server 11 to the communication control unit 1213 (step S6). Subsequently, when the communication control unit 1213 receives the interrupt response packet, the communication control unit 1213 extracts the interrupt response information included therein, and the extracted interrupt response information is output from the communication control unit 1213 to the USB driver 1212 (step S7). ). After that, the USB driver 1212 sends the first key press notification information for notifying that the first key is pressed, based on the key status information included in the interrupt response information as shown in FIG. 5A, for example. To generate. The generated first key press notification information is output from the USB driver 1212 to the processing unit 1211 (step S8). Then, when the notification of pressing the first key is input, the processing unit 1211 starts the operation corresponding to the pressing of the first key (step S9).

Next, when the interrupt request information is acquired, or when a preset cycle is reached after transmitting the interrupt request information in step S2, the interrupt request is sent again from the USB driver 1212 to the communication control unit 1213. Is output to (step S10). Then, the interrupt request packet including the interrupt request information is transmitted from the communication control unit 1213 to the device server 11 (step S11). After that, the interrupt request information included in the interrupt request packet is transferred from the device server 11 to the keyboard 13 (step S12).

Further, the communication control unit 1213 repeatedly generates and transmits a keep-alive request packet to the device server 11 at a preset cycle (step S13). On the other hand, when the device server 11 receives the keepalive request packet, the device server 11 generates a keepalive response packet and transmits it to the communication control unit 1213 (step S14). The communication control unit 1213 determines that communication with the device server 11 is possible as long as the keep-alive response packet is received from the device server 11.

Next, it is assumed that the communication control unit 1213, after transmitting the keepalive request packet (step S15), does not receive the keepalive response packet from the device server 11 and determines that the communication with the device server 11 is cut off (step S15). S16). After that, it is assumed that the communication with the device server 11 is not restored during the preset reference time ΔT1. In this case, dummy interrupt response information indicating that the first key has been released is transmitted from the communication control unit 1213 to the USB driver 1212 (step S17). In the dummy interrupt response information at this time, all of the plurality of key status information are set to "00" as shown in FIG. 5B, for example. This interrupt response information indicates that all the keys of the keyboard 13 have not been pressed.

Returning to FIG. 4, when dummy interrupt response information indicating a state where the first key is released is input to the USB driver 1212, interrupt request information is output from the USB driver 1212 to the communication control unit 1213 accordingly. (Step S18). Then, the communication control unit 1213 stores the interrupt request information input from the USB driver 1212 in the request storage unit 1221 (step S19).

Further, the USB driver 1212 sends the first key release notification information for notifying that the first key is released based on the key status information included in the interrupt response information as shown in FIG. 5B, for example. To generate. Then, the generated first key release notification information is output from the USB driver 1212 to the processing unit 1211 (step S20). Then, when the first key release notification is input, the processing unit 1211 performs an operation according to the release of the first key (step S21).

After that, as shown in FIG. 6, it is assumed that the communication control unit 1213 receives the keepalive response packet from the device server 11 after transmitting the keepalive request packet to the device server 11 (step S22) (step S23). In this case, the communication control unit 1213 determines that the communication with the device server 11 has been restored (step S24). After that, the interrupt request packet including the interrupt request information stored in the request storage unit 1221 is transmitted from the communication control unit 1213 to the device server 11 (step S25). Then, when the device server 11 receives the interrupt request packet, the device server 11 extracts the interrupt request information included therein. After that, the interrupt request information is transferred from the device server 11 to the keyboard 13 (step S26).

Here, it is assumed that the keyboard 13 receives a release operation of the first key by the user (step S27). In this case, in response to the interrupt request information (step S12) previously transferred to the keyboard 13, the interrupt response information indicating the released state of the first key is transmitted from the keyboard 13 in the same manner as in steps S5 and S6. It is transferred to the control unit 1213 (steps S28 and S29). Then, it is assumed that the communication control unit 1213 determines that the interrupt response information indicates a state in which the first key is released (step S30). In this case, the communication control unit 1213 discards the interrupt response information (step S31). That is, the communication control unit 1213 discards the interrupt response information according to the content of the interrupt response information corresponding to the dummy interrupt response information acquired from the keyboard 13 via the device server 11.

After that, it is assumed that the keyboard 13 receives the pressing operation of the second key by the user (step S32). In this case, according to the interrupt request information (step S26) previously transferred to the keyboard 13, the interrupt response information indicating the state in which the second key is pressed is changed from the keyboard 13 to the USB in the same manner as in steps S5 to S7. The data is transferred to the driver 1212 (steps S33 to S35). In the interrupt response information at this time, for example, as shown in FIG. 5C, the key status information corresponding to the second key in the plurality of key status information is set to “1E” and corresponds to other keys. The key status information is set to "00". This interrupt response information indicates that only the second key is pressed and the other keys are not pressed.

Returning to FIG. 6, subsequently, the USB driver 1212 notifies that the second key is pressed based on the key status information included in the interrupt response information as shown in FIG. 5C, for example. The second key press notification information is generated. The generated second key press notification information is output from the USB driver 1212 to the processing unit 1211 (step S36). Then, when the notification of pressing the second key is input, the processing unit 1211 starts an operation corresponding to the pressing of the second key (step S37).

Next, communication control processing executed by the communication control unit 1213 of the client device 12 according to the present embodiment will be described with reference to FIGS. 7 to 9. The communication control process is started when the keyboard 13 is connected to the client device 12 via the device server 11 while the client device 12 and the device server 11 are powered on. Here, the communication control unit 1213 obtains the USB configuration information and the descriptor information from the keyboard 13 via the device server 11 and the network, thereby obtaining information about the structure of the interrupt response packet and the information about the cycle of outputting the interrupt request information. It is assumed that it is acquired and stored in the specification information storage unit 1231.

First, when the USB request information is input from the USB driver 1212, the communication control unit 1213 generates a USB request packet including the USB request information and transmits the USB request packet to the device server 11 (step S101). .. The USB request information includes request information for control transfer, bulk transfer, interrupt transfer, and isochronous transfer.

Next, the communication control unit 1213 receives the USB response packet corresponding to the USB request packet (step S102). The USB response information includes response information for control transfer, bulk transfer, interrupt transfer, and isochronous transfer. Subsequently, the communication control unit 1213 determines whether the USB response information included in the USB response packet is the interrupt response information and the transfer source USB device is HID (step S103). When determining that the USB response information is not the interrupt response information or the transfer source USB device is not the HID (step S103: No), the communication control unit 1213 outputs the USB response information to the USB driver 1212 (step S104). Then, the communication control unit 1213 executes the process of step S101 again.

On the other hand, when the communication control unit 1213 determines that the USB response information is the interrupt response information and the transfer source USB device is the HID (step S103: Yes), the USB response information, that is, the interrupt response information indicates that the key is pressed. It is determined whether or not it is shown (step S105). When the communication control unit 1213 determines that the interrupt response information does not indicate that the key has been pressed (step S105: No), it outputs the interrupt response information to the USB driver 1212 (step S106) and then generates an interrupt request packet. It is transmitted (step S107). After that, the communication control unit 1213 executes the above-described process of step S102 again. On the other hand, when the communication control unit 1213 determines that the interrupt response information indicates that the key is pressed (step S105: Yes), the communication control unit 1213 outputs key press notification information for notifying that the key has been pressed to the processing unit 1211 (step S105). In step S108, the interrupt response information is output to the USB driver 1212 (step S109). Next, the communication control unit 1213 generates an interrupt request packet including the interrupt request information output from the USB driver 1212 and transmits it to the device server 11 (step S110). Then, as shown in FIG. 8, the communication control unit 1213 executes a communication state determination process for determining the communication state with the conversion unit 1111 of the device server 11 (step S111). In the communication state determination process, the communication control unit 1213 transmits a keepalive request packet to the conversion unit 1111. Then, when the communication control unit 1213 receives the keepalive response packet from the conversion unit 1111 within the preset determination period, it determines that communication with the conversion unit 1111 is possible. On the other hand, when the communication control unit 1213 does not receive the keepalive response packet from the conversion unit 1111 within the determination period, the communication control unit 1213 transmits the keepalive request packet to the conversion unit 1111 again. Then, the communication control unit 1213 determines that the communication with the conversion unit 1111 is cut off when the keepalive response packet is not received from the conversion unit 1111 even if the keepalive request packet is repeatedly transmitted a preset number of times.

Subsequently, the communication control unit 1213 determines whether or not the communication with the conversion unit 1111 is cut off based on the result of the communication state determination process (step S111) (step S112). When determining that communication with the conversion unit 1111 is possible (step S112: No), the communication control unit 1213 determines whether or not an interrupt response packet has been received from the device server 11 (step S113). When determining that the interrupt request packet has not been received (step S113: No), the communication control unit 1213 executes the communication state determination process again (step S111). On the other hand, when determining that the interrupt request packet has been received (step S113: Yes), the communication control unit 1213 executes the process of step S105 described above.

When the communication control unit 1213 determines that the communication with the conversion unit 1111 is cut off (step S112: Yes), it starts the timer of the clock unit 1214, and the communication cutoff state elapses for the preset reference time ΔT1. It is determined whether or not (step S114). Here, the timer continues counting as long as the communication cutoff state continues. When the communication control unit 1213 determines that the communication cutoff state has not elapsed for the preset reference time ΔT1 (step S114: No), the communication control unit 1213 executes the process of step S111 again. The reference time ΔT1 is set to about 5 seconds, for example.

On the other hand, when the communication control unit 1213 determines that the preset reference time ΔT1 has elapsed in the communication cutoff state based on the count value of the timer of the timer unit 1214 (step S114: Yes), the communication control unit 1213 , Dummy interrupt response information indicating the key release state is output to the USB driver 1212 (step S115). Next, the communication control unit 1213 stores the interrupt request information corresponding to the dummy interrupt response information in the request storage unit 1221 (step S116). Subsequently, the communication control unit 1213 executes a communication state determination process of determining the communication state with the conversion unit 1111 (step S117). After that, the communication control unit 1213 determines whether or not the communication with the conversion unit 1111 is restored based on the result of the communication state determination process (step S117) (step S118). When the communication control unit 1213 determines that the communication with the conversion unit 1111 has not been restored (step S118: No), the process of step S117 is executed again.

On the other hand, when the communication control unit 1213 determines that the communication with the conversion unit 1111 is restored (step S118: Yes), it generates an interrupt request packet based on the interrupt request information stored in the request storage unit 1221 and converts the interrupt request packet. It is transmitted to 1111 (step S119). Next, the communication control unit 1213 receives the interrupt response packet (step S120). The order of the process of step S119 and the process of step S120 may be reversed.

After that, the communication control unit 1213 determines whether or not the interrupt response information indicates the key released state, as shown in FIG. 9 (step S121). When determining that the interrupt response information does not indicate the key release state (step S121: No), the communication control unit 1213 outputs the extracted interrupt response information to the USB driver 1212 (step S122). After that, the communication control unit 1213 determines whether or not the interrupt request information is input from the USB driver 1212 (step S123). When the communication control unit 1213 determines that the interrupt request information is not input from the USB driver 1212 (step S123: No), the communication control unit 1213 executes the process of step S102 described above. On the other hand, when the communication control unit 1213 determines that the interrupt request information is input from the USB driver 1212 (step S123: Yes), the communication control unit 1213 discards the interrupt request information (step S124), and then executes the process of step S102. The discarding of the interrupt request information is a process for associating the interrupt response information with the interrupt request information in a one-to-one correspondence in relation to the transmission of the dummy interrupt response information in step S115. On the other hand, when the communication control unit 1213 determines in step S121 that the interrupt response information indicates the key released state (step S121: Yes), it does not output the interrupt response information indicating the key released state to the USB driver 1212 and discards it. Yes (step S125). That is, the communication control unit 1213 discards the interrupt response information according to the content of the interrupt response information corresponding to the dummy interrupt response information acquired from the keyboard 13 via the device server 11. Then, the communication control unit 1213 executes the process of step S102 described above. If the communication control unit 1213 issues an interrupt command instructing to end the communication control process via the user I/F (not shown) of the client device 2012 during execution of the communication control process, for example. At that point, the communication control process ends.

As described above, according to the device server system 1 according to the present embodiment, the communication control unit 1213 monitors the communication state between the client device 12 and the device server 11. Then, after the user presses the key on the keyboard 13, the communication control unit 1213 releases the key when it is determined that the reference time has elapsed with the communication between the client device 12 and the device server 11 being cut off. The dummy interrupt response information indicating that it has been output is output to the USB driver 1212. As a result, while the communication between the client device 12 and the device server 11 is cut off, it is prevented that the processing unit 1211 cannot continue the process in accordance with the key press notification information. Here, it is assumed that the two interrupt response information of pressing the key and releasing the key are transferred from the keyboard 13 to the client device 12 and the processing in the processing unit 1211 is completed. In this case, even when the communication is interrupted immediately after the interrupt response information indicating the key press from the keyboard 13 is transferred to the client device 12, the processing in the processing unit 1211 is not completed while the communication is interrupted. It is never left unattended. Therefore, the convenience of the user who uses the client device 12 is improved.

By the way, in the conventional technique, the client device 12 continues to press a key after receiving the interrupter response information indicating the key press from the keyboard 13 until it receives the interrupt response information indicating the key release, that is, the key input is not performed. Recognize that it is continuing. Therefore, if the interrupt response information indicating the key release cannot be received for a time longer than the interrupt request information output cycle corresponding to the keyboard 13 due to interruption or delay of wireless communication between the client device 12 and the device server 11, for example, The device 12 recognizes that the key input is continuing. On the other hand, in the device server system according to the present embodiment, the communication control unit 1213 receives the interrupt response information indicating the key press from the keyboard 13 and then the interrupt response information indicating the key release is not received. After a lapse of time ΔT1, dummy interrupt response information indicating key release is output to the USB driver 1212. As a result, it is possible to prevent the client device 12 from continuing to execute the process according to the continuation of the key input against the intention of the user.

Further, it is assumed that the communication between the client device 12 and the device server 11 is restored after the communication control unit 1213 according to the present embodiment outputs the dummy interrupt response information to the USB driver 1212. In this case, the communication control unit 1213 discards the interrupt response information according to the content of the interrupt response information corresponding to the dummy interrupt response information acquired from the keyboard 13 via the device server 11. As a result, the interrupt request information transferred from the client device 12 to the keyboard 13 and the interrupt response information transferred from the keyboard 13 to the client device 12 can be made to correspond one-to-one. Therefore, it is possible to suppress the occurrence of the problem of interrupt transfer between the client device 12 and the keyboard 13 due to the mismatch between the interrupt request information and the interrupt response information.

(Embodiment 2)
The device server system according to the present embodiment differs from the device server system 1 according to the first embodiment in that the HID includes a touch panel instead of the keyboard. As shown in FIG. 10, the device server system 2 according to the present embodiment includes a device server 11, a client device 2012, a touch panel 2013, and a display 14. In addition, in FIG. 10, the same components as those in the first embodiment are denoted by the same reference numerals as those in FIG. The hardware configuration of the client device 2012 is the same as that of the client device 12 according to the first embodiment.

In the client device 2012, the CPU 121 reads the program stored in the auxiliary storage unit 123 into the main storage unit 122 and executes the program, and as shown in FIG. 11, the processing unit 2211, the USB driver 1212, the communication control unit 2213, and the timekeeping unit 2213. It functions as the unit 1214. In FIG. 11, the same components as those in the first embodiment are designated by the same reference numerals as those in FIG.

The processing unit 2211 generates image information by executing processing according to the touch state notification information or the touch release information input from the USB driver 1212 and outputs the image information to the display 14. After the interrupter response information indicating the touch state is transferred from the touch panel 2013, the processing unit 2211 performs a process according to the release of the touch state when a preset reference time elapses in a state where the interrupt response information indicating the touch release is not transferred. To execute.

The communication control unit 2213 generates an interrupt request packet including the interrupt request information input from the USB driver 1212 and transmits the interrupt request packet to the device server 11. Further, the communication control unit 2213 extracts the interrupt response information included in the interrupt response packet received from the device server 11 and outputs the interrupt response information to the USB driver 1212.

Next, the operation of the device server system 2 according to the present embodiment will be described with reference to FIGS. Note that, in FIGS. 12 and 14, illustration of the handshake packet transmission/reception transmitted from the USB driver 1212 to the touch panel 2013 is omitted. Further, it is assumed that the communication control unit 2213 has already acquired the information regarding the structure of the interrupt response packet received from the touch panel 2013 and the transmission cycle of the interrupt request information corresponding to the touch panel 2013. In FIG. 12, first, it is assumed that the touch panel 2013 receives a touch made by the user (step S51). Next, the interrupt request information is output from the USB driver 1212 of the client device 2012 to the communication control unit 2213 (step S52). Then, the interrupt request packet including the interrupt request information is transmitted from the communication control unit 2213 to the device server 11 (step S53). Then, the interrupt request information included in the interrupt request packet is transferred from the device server 11 to the touch panel 2013 (step S54).

Next, when the touch panel 2013 receives the interrupt request information while being touched by the user (touch state), the interrupt response information indicating the touch state is transferred from the touch panel 2013 to the device server 11 (step S55). In this interrupt response information, for example, as shown in FIG. 13A, status information indicating presence/absence of touch is set to “0x01”, and indicates the X coordinate and the Y coordinate of the portion touched by the user on the touch panel 2013. Information is set. This interrupt response information indicates that the portion corresponding to the coordinates (64, −64) on the touch panel 2013 is touched.

Returning to FIG. 12, on the other hand, the device server 11 generates an interrupt response packet by encapsulating the interrupt response information. The generated interrupt response packet is transmitted from the device server 11 to the communication control unit 2213 (step S56). Subsequently, the interrupt response information included in the interrupt response packet is output from the communication control unit 2213 to the USB driver 1212 (step S57). Thereafter, based on the interrupt response information indicating the touch state, touch state notification information indicating the touch state is output from the USB driver 1212 to the processing unit 2211 (step S58). Then, when the touch state notification information is input, the processing unit 2211 starts an operation according to the touch state (step S59).

Next, when an interrupt request information is acquired, or when a preset cycle is reached after transmitting the interrupt request information in step S52, the interrupt request is sent again from the USB driver 1212 to the communication control unit 2213. Is output (step S60). Then, the interrupt request packet including the interrupt request information is transmitted from the communication control unit 2213 to the device server 11 (step S61). After that, the interrupt request information included in the interrupt request packet is transferred from the device server 11 to the touch panel 2013 (step S62). After that, as long as the communication between the communication control unit 2213 and the device server 11 is possible, the interrupt request information can be transferred from the USB driver 1212 to the touch panel 2013 and the interrupt response information can be transferred from the touch panel 2013 to the USB driver 1212. It is repeatedly executed at a preset cycle.

Further, between the communication control unit 2213 and the conversion unit 1111 of the device server 11, the communication state determination process is executed at the same time as the transmission and reception of the interrupt request packet and the interrupt response packet described above. In this communication state determination process, the keepalive request packet is repeatedly transmitted from the communication control unit 2213 to the device server 11 at a preset cycle (step S63). On the other hand, when the device server 11 receives the keepalive request packet, the device server 11 generates a keepalive response packet and transmits it to the client device 2012 (step S64). The communication control unit 2213 determines that communication with the device server 11 is possible as long as the keep alive response packet is received from the device server 11.

Next, it is assumed that the communication control unit 2213, after transmitting the keepalive request packet (step S65), does not receive the keepalive response packet from the device server 11 and determines that the communication with the device server 11 is cut off (step S65). S66). After that, it is assumed that the communication with the device server 11 is not restored during the preset reference time ΔT2. In this case, the dummy interrupt response information indicating that the touch state is continuously transmitted from the communication control unit 2213 to the USB driver 1212 (step S67). When the dummy interrupt response information indicating the touch state is input to the USB driver 1212, the interrupt request information is output from the USB driver 1212 to the communication control unit 2213 in response thereto (step S68). Then, the communication control unit 2213 stores the interrupt request information input from the USB driver 1212 in the request storage unit 2221 (step S69). The reference time ΔT2 is set to be approximately the same length as the output cycle of the interrupter request information corresponding to the touch panel 2013, for example, set to about several msec.

Further, the USB driver 1212 generates touch state notification information indicating a touch state based on the interrupt response information as shown in FIG. 13A, for example. Then, the generated touch state notification information is output from the USB driver 1212 to the processing unit 2211 (step S70). Then, when the touch state notification information is input, the processing unit 2211 performs an operation according to the touch state (step S71).

Thereafter, as shown in FIG. 14, it is assumed that the communication control unit 2213 receives the keepalive response packet from the device server 11 after transmitting the keepalive request packet to the device server 11 (step S72) (step S73). In this case, the communication control unit 2213 determines that the communication with the device server 11 has been restored (step S74). In this case, in response to the interrupt request information (step S62) previously transferred to the touch panel 2013, the interrupt response information indicating the touch state is transferred from the touch panel 2013 to the communication control unit 2213 in the same manner as in steps S55 and S56. (Steps S75, S76). Then, the interrupt response information transferred to the communication control unit 2213 is output from the communication control unit 2213 to the USB driver 1212 (step S77).

When the communication between the communication control unit 2213 and the device server 11 is restored, an interrupt request packet including the interrupt request information stored in the request storage unit 2221 is transmitted from the communication control unit 2213 to the device server 11 ( Step S78). Then, the interrupt request information included in the interrupt request packet is transferred from the device server 11 to the touch panel 2013 (step S79). When the interrupt request information is transferred to the touch panel 2013, the interrupt response information is transferred from the touch panel 2013 to the USB driver 1212 in the same manner as in steps S55 to S57 (steps S80 to S82).

Here, since the dummy interrupt response information has already been output from the communication control unit 2213 to the USB driver 1212 (step S67), a process for associating the interrupt response information with the interrupt request information in a one-to-one correspondence is performed. Specifically, when the interrupt request information is output from the USB driver 1212 to the communication control unit 2213 (step S83), the communication control unit 2213 discards the input interrupt request information (step S84). Here, the number of interrupt request information items discarded by the communication control unit 2213 corresponds to the number of times the dummy interrupt response information is output. As described above, when the communication control unit 2213 outputs the dummy interrupt response information to the USB driver 1212 and then the communication between the client device 2012 and the device server 11 is restored, the communication controller 2213 inputs the dummy interrupt response information from the USB driver 1212. The interrupt request information corresponding to the interrupt response information is discarded.

After that, the interrupt request information is transferred from the USB driver 1212 to the touch panel 2013 via the communication control unit 2213 and the device server 11 in the same manner as in steps S52 to S54 (steps S85 to S87). Then, it is assumed that the touch panel 2013 receives a touch release operation by the user (step S88). Then, the interrupt response information indicating the touch release is transferred from the touch panel 2013 to the USB driver 1212 as in steps S55 to S57 (steps S89 to S91). In the interrupt response information at this time, for example, as shown in FIG. 13B, the status information indicating the presence or absence of the touch is set to “0x00”.

Returning to FIG. 14, subsequently, the USB driver 1212 generates touch release notification information for notifying the touch release based on the interrupt response information as shown in FIG. 13B, for example. The generated touch release notification information is output from the USB driver 1212 to the processing unit 2211 (step S92). Then, when the touch release notification information is input, the processing unit 2211 executes processing according to the touch release notification information (step S93).

Next, the communication control processing executed by the communication control unit 2213 of the client device 2012 according to this embodiment will be described with reference to FIGS. 15 and 16. The communication control process is started when the touch panel 2013 is connected to the client device 2012 via the device server 11 while the client device 2012 and the device server 11 are powered on. Here, the communication control unit 2213 obtains the USB configuration information and the descriptor information from the touch panel 2013 via the device server 11 and the network to obtain the information about the structure of the interrupt response packet and the cycle of outputting the interrupt request information. It is assumed that it is acquired and stored in the specification information storage unit 2231.

First, the communication control unit 2213 executes the processes of steps S201 to S204 as shown in FIG. The contents of the processing of steps S201 to S204 are the same as the contents of the processing of steps S101 to S104 described in the first embodiment. Then, when the communication control unit 1213 determines in the processing of step S203 that the USB response information is the interrupt response information and the transfer source USB device is the HID (step S203: Yes), the USB response information, that is, the interrupt. It is determined whether the response information indicates the touch state (step S205). When the communication control unit 2213 determines that it is not in the touch state (step S205: No), it outputs the interrupt response information to the USB driver 1212 (step S206), and then generates and transmits the interrupt request packet (step S207). After that, the communication control unit 1213 executes the above-described processing of step S202 again. On the other hand, when the communication control unit 2213 determines that it is in the touch state (step S205: Yes), it outputs touch state notification information for notifying that the touch panel 2013 is touched to the processing unit 2211 (step S208), and the interrupt. The response information is output to the USB driver 1212 (step S209). Next, the communication control unit 1213 generates an interrupt request packet including the interrupt request information output from the USB driver 1212 and transmits it to the device server 11 (step S210). After that, the communication control unit 2213 executes a communication state determination process with the conversion unit 1111 of the device server 11 as shown in FIG. 16 (step S211). The communication state determination process is the same as the communication state determination process described in the first embodiment.

Next, the communication control unit 2213 determines whether or not the communication with the conversion unit 1111 is cut off in the communication state determination process (step S212). When determining that communication with the conversion unit 1111 is possible (step S212: No), the communication control unit 2213 determines whether or not an interrupt response packet has been received from the device server 11 (step S213). When the communication control unit 2213 determines that the interrupt request packet has not been received (step S213: No), the communication control unit 2213 executes the communication state determination process again (step S211). On the other hand, when determining that the interrupt request packet has been received (step S213: Yes), the communication control unit 2213 executes the process of step S205 described above.

When the communication control unit 2213 determines that the communication with the conversion unit 1111 is cut off (step S212: Yes), the timer of the time counting unit 1214 is started, and the communication cutoff state elapses for the preset reference time ΔT2. It is determined whether or not (step S214). As described above, this reference time is set to be approximately the same length as the output cycle of the interrupter request information corresponding to the touch panel 2013, and is set to, for example, about several msec. Here, the timer continues counting as long as the communication cutoff state continues. Then, when the communication control unit 2213 determines that the communication cutoff state has not elapsed for the preset reference time ΔT2 (step S214: No), the process of step S211 is executed again.

On the other hand, when the communication control unit 2213 determines that the preset reference time ΔT2 has elapsed in the communication cutoff state based on the count value of the timer of the timer unit 1214 (step S214: Yes), the communication control unit 2213 determines , Dummy interrupt response information indicating the touch state is output to the USB driver 1212 (step S215). Next, the communication control unit 2213 determines whether or not the interrupt request information is already stored in the request storage unit 2221 (step S216). When the communication control unit 2213 determines that the interrupt request information has already been stored in the request storage unit 221 (step S216: Yes), the interrupt control information is discarded (step S218), and the process of step S219 described below is performed. Execute. On the other hand, if the communication control unit 2213 determines that the interrupt request information is not yet stored in the request storage unit 2221 (step S216: No), it stores the interrupt request information corresponding to the dummy interrupt response information in the request storage unit 2221. (Step S217). Subsequently, the communication control unit 2213 executes a communication state determination process of determining the communication state with the conversion unit 1111 (step S219). After that, the communication control unit 2213 determines whether or not the communication with the conversion unit 1111 is restored, based on the result of the communication state determination process (step S219) (step S220).

When the communication control unit 2213 determines that the communication with the conversion unit 1111 is restored (step S220: Yes), the communication control unit 2213 receives the interrupt response packet (step S221), extracts the interrupt response information from the interrupt response packet, and extracts the USB driver 1212. (Step S222). Next, the communication control unit 2213 generates an interrupt request packet and transmits it to the conversion unit 1111 (step S223). The order of the processes of steps S221 and S222 and the process of step S223 may be reversed.

Subsequently, the communication control unit 2213 determines whether or not the interrupt request information is input from the USB driver 1212 (step S224). When the communication control unit 2213 determines that the interrupt request information is not input from the USB driver 1212 (step S224: No), the process of step S202 described above is executed. On the other hand, when determining that the interrupt request information is input from the USB driver 1212 (step S224: Yes), the communication control unit 2213 discards the interrupt request information (step S225). That is, when the communication control unit 2213 outputs the dummy interrupt response information to the USB driver 1212 and then the communication between the client device 2012 and the device server 11 is restored, the dummy interrupt input from the USB driver 1212. Discard the interrupt request information corresponding to the response information. This is a process for associating the interrupt response information with the interrupt request information on a one-to-one basis. After that, the communication control unit 2213 executes the process of step S202 described above.

In addition, when the communication control unit 2213 determines in the process of step S220 that the communication with the conversion unit 1111 has not been restored (step S220: No), the communication control unit 2213 only disconnects the communication for a preset reference time ΔT3. It is determined whether the time has passed (step S226). Here, the reference time ΔT3 is set to, for example, 5 seconds. When the communication control unit 2213 determines that the preset reference time ΔT3 has elapsed in the communication cutoff state (step S226: Yes), it outputs the dummy interrupt response information indicating the touch release to the USB driver 1212 (step S227). ). After that, the communication control unit 2213 executes a communication state determination process for determining the communication state with the conversion unit 1111 (step S228). Next, the communication control unit 2213 determines whether or not the communication with the conversion unit 1111 has been restored based on the result of the communication state determination process (step S228) (step S229).

When the communication control unit 2213 determines that the communication with the conversion unit 1111 is restored (step S229: Yes), the communication control unit 2213 executes the process of step S221. On the other hand, when the communication control unit 2213 determines that the communication with the conversion unit 1111 is not restored (step S229: No), the process of step S228 is executed again. In addition, when the communication control unit 2213 determines in the process of step S226 that the communication cutoff state has not yet elapsed for the reference time ΔT3 (step S226: No), the communication control unit 2213 sets the reference time preset in the communication cutoff state. It is determined whether ΔT2 has elapsed (step S230). When the communication control unit 2213 determines that the preset reference time ΔT2 has elapsed in the communication cutoff state (step S230: Yes), the communication control unit 2213 executes the process of step S215. On the other hand, when the communication control unit 2213 determines that the preset reference time ΔT2 has not elapsed in the communication cutoff state (step S230: No), the communication control unit 2213 executes the process of step S219. Note that, if the communication control unit 2213 issues an interrupt command instructing to end the communication control process via the user I/F (not shown) of the client device 2012 during execution of the communication control process, for example. At that point, the communication control process ends.

Here, the operation of the device server system 2 according to the present embodiment will be described in comparison with the operation of the device server system according to the comparative example. The hardware configuration of the device server system according to the comparative example is similar to that of the device server system 2. However, the difference is that input of dummy interrupt response information to the USB driver of the client device 2012 is not executed. For example, it is assumed that the user drags the file F1 onto the folder F2 while looking at the screen 141 of the display 14 as indicated by an arrow AR1 in FIG. In this case, in the device server system according to the comparative example, if the communication between the client device 2012 and the device server 11 is interrupted while the file F1 is being moved, the file F1 is specified on the way to the folder F2. Will be canceled. Then, as shown in FIG. 17A, the file F1 is left in the middle of reaching the folder F2, and the user cannot perform the operation of moving the file F1 to the folder F2.

On the other hand, in the device server system 2 according to the present embodiment, in the case of the comparative example, if the communication between the client device 2012 and the device server 11 is interrupted while the file F1 is being moved, The communication control unit 2213 outputs dummy interrupt response information indicating the touch state to the USB driver 1212. As a result, the designation of the file F1 is maintained even while the communication between the client device 2012 and the device server 11 is cut off. Therefore, as shown in FIG. 17(B), the user stores the file F1 in the folder F2. You can perform the operation to move to.

As described above, according to the device server system 2 according to the present embodiment, the communication control unit 2213 outputs dummy interrupt response information to the USB driver 1212, and then, between the client apparatus 2012 and the device server 11. When the communication is restored, the interrupt request information corresponding to the dummy interrupt response information input from the USB driver 1212 is discarded. As a result, the interrupt request information transferred from the client device 2012 to the touch panel 2013 and the interrupt response information transferred from the touch panel 2013 to the client device 2012 can be associated with each other on a one-to-one basis. Therefore, it is possible to suppress the occurrence of a defect in interrupt transfer between the client device 2012 and the touch panel 2013 due to the mismatch between the interrupt request information and the interrupt response information.

(Modification)
Although the respective embodiments of the present invention have been described above, the present invention is not limited to the configurations of the respective embodiments. For example, the user may set not to output the dummy interrupt response information to the USB driver 1212 via the user I/F of the client device or the user interface of the keyboard 13 and the touch panel 2013.

In each embodiment, the case where the interrupt transfer is performed between the client device and the keyboard 13 or the touch panel 2013 has been described, but the HID connected to the device server 11 is not limited to the interrupt transfer. For example, it may be an HID that executes isochronous input transfer or bulk input transfer.

The various functions of the client device according to the present invention can be realized using a computer system instead of a dedicated system. For example, a program for executing the above operation is stored in a non-transitory recording medium (such as a CD-ROM) readable by a computer system and distributed to a computer connected to a network, and the program is stored in the computer. A client device that executes the above-described communication control process may be configured by installing it in the system. Further, the method of providing the program to the computer is arbitrary. For example, the program may be uploaded to a server on a communication line and distributed to a computer via the communication line.

The embodiments and modifications of the present invention (including those described in the note. The same applies hereinafter) have been described above, but the present invention is not limited to these. The present invention includes a combination of the embodiments and the modifications as appropriate, and a combination of the modifications as appropriate.

INDUSTRIAL APPLICABILITY The present invention is suitable as a network system in a thin client environment for the purpose of reducing management man-hours or a network system including an information display using a touch panel.

1, 2: device server system, 11: device server, 12, 2012: client device, 13: keyboard, 14: display, 111, 121: CPU, 112, 122: main storage unit, 113, 123: auxiliary storage unit, 114, 124: wireless communication I/F, 115, 125: wireless module, 116: USB I/F, 117, 127: bus, 126: video I/F, 141: screen, 1111: conversion unit, 1211, 2121: processing Section, 1212: USB driver, 1213, 2213: communication control section, 1214: clock section, 1221, 2221: request storage section, 1231, 2321: specification information storage section, 2013: touch panel

Claims (7)

A client device,
A HID class USB device that transfers interrupt response information and causes the client device to perform processing;
A device server to which the USB device is connected,
The client device is connected to the device server via a network,
A processing unit for executing processing according to the interrupt response information transferred from the USB device;
A USB driver that generates interrupt request information for requesting the transfer of the interrupt response information to the USB device, and outputs the interrupt response information to the processing unit when the interrupt response information is acquired,
Dummy interrupt response information is obtained when the communication state between the client device and the device server is monitored and it is determined that the reference time has elapsed in the state where the communication between the client device and the device server is cut off. And a communication control unit for outputting to the USB driver,
Device server system. The communication control unit,
When the communication between the client device and the device server is restored after outputting the dummy interrupt response information to the USB driver, the interrupt response information acquired from the USB device via the device server is returned to the USB device. , Discarding according to the content of the processing information corresponding to the dummy interrupt response information,
The device server system according to claim 1. The communication control unit,
When the communication between the client device and the device server is restored after outputting the dummy interrupt response information to the USB driver, the interrupt response information input from the USB driver is converted into the dummy interrupt response. Discard according to the content of information,
The device server system according to claim 1. 4. The communication control unit monitors the communication state between the client device and the device server by determining whether or not a keep-alive response packet has been received from the device server. The device server system according to item 1. A client device that is connected via a network to a device server to which a HID class USB device that transfers interrupt response information is connected, and that receives the interrupt response information transferred from the USB device via the device server. hand,
A processing unit that executes processing according to the interrupt response information transferred by the USB device;
A USB driver that generates interrupt request information for requesting the transfer of the interrupt response information to the USB device, and outputs the interrupt response information to the processing unit when the interrupt response information is acquired,
Monitoring the communication state between the self-device and the device server, if it is determined that the reference time has elapsed in the state where the communication between the self-device and the device server is cut off, the dummy interrupt response information is displayed. A communication control unit for outputting to the USB driver,
Client device. A client device that is connected via a network to a device server to which a USB device of HID class that transfers interrupt response information is connected, and that receives the interrupt response information transferred from the USB device via the device server. An information transfer control method for
A processing unit executing processing according to the interrupt response information transferred from the USB device;
A USB driver generating interrupt request information requesting transfer of the interrupt response information to the USB device;
When the USB driver acquires the interrupt response information, outputting the interrupt response information to the processing unit,
The communication control unit monitors the communication state between the client device and the device server, and determines that the reference time has elapsed in the state where the communication between the client device and the device server is cut off, Outputting dummy interrupt response information to the USB driver.
Information transfer control method. Computer,
A processing unit that executes a process according to the interrupt response information transferred by the HID class USB device that transfers the interrupt response information;
A USB driver that generates interrupt request information requesting the transfer of the interrupt response information to the USB device, and outputs the interrupt response information to the processing unit when the interrupt response information is acquired,
The communication state of the communication via the network between the client device and the device server to which the USB device is connected is monitored, and it is determined that the reference time has elapsed in the state where the communication with the device server is cut off. Then, it functions as a communication control unit that outputs dummy interrupt response information to the USB driver.
program.

Images