JP2015191320A - Information processor, device sharing system and device connection method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve such a problem that connection and its cancellation are repeated at each scanning and a terminal of a connection destination cannot be decided in advance in a system using a conventional USB device server in which a terminal establishes connection with a scanner with depression of a scan button in the scanner connected by a USB to the USB device server as a trigger and cancels the connection at the time of scan end.SOLUTION: A scanning application is executed in a terminal to search for a device of a USB device server. If there is an available device, the terminal is connected thereto. If there is the device but it is in use, the terminal is connected thereto after the connection is forcibly canceled, and the device is used. If the connection with the device is canceled, the device is connected again to the terminal whose connection is canceled forcibly.

Description

  The present invention relates to an information processing apparatus, a device sharing system, and a device connection method, and more particularly to an automatic connection program when a scanner is connected to a network.

  In order to share a USB device in a network environment, a USB device server that is a device independent of the USB device is used. By using this USB device server, if a virtual USB port driver is installed on the computer, the existing USB device can be encapsulated / unencapsulated between the computer and the USB device server, that is, tunneled. With this driver, it becomes possible to share a USB device in a network environment (Patent Document 1).

  Each computer (PC) connected to the same network as the USB device server can use the USB device connected to the USB device server in the same way as a USB device connected to a local USB interface provided by itself. According to Patent Document 1, when a user uses a USB device connected to a USB device server from a PC on the network, first, the user operates an application attached to the USB device server to connect the USB device server to the PC. Need to establish a connection. More specifically, select the desired device from the list of USB device servers on the network displayed on the application screen and the USB devices connected to it, and connect on the application screen. Connection is established by pressing the button. This connection process is required for each USB device. On the other hand, after using the USB device, a disconnection work is required, and the USB device cannot be used from another PC unless this disconnection work is performed.

  In order to eliminate such connection / disconnection operations, when a USB scanner is connected to the USB device server, when the user performs a scan, the USB scanner is automatically connected to the PC and disconnected when the scan is completed. The proposal regarding the automatic connection program is made | formed (patent document 2).

JP 2008-287453 A JP 2008-193217 A

  However, in the case of the configuration of Patent Document 2, when scanning is completed, the cutting is automatically performed. For this reason, for example, when the start button of the scanner body is monitored, and an automatic connection program is started to connect and start scanning when the start button of the scanner body is pressed, connection and disconnection are frequently repeated. As a result, the processing load on the PC increases. In addition, when the automatic connection program is installed on all of the PCs, it is not possible to know which scanner is connected to which PC and data is transmitted when the start button on the scanner is pressed. It was in.

  As described above, when connecting / disconnecting the USB device on the USB device server manually as in Patent Document 1, it is necessary to connect / disconnect each time the USB device is used. There is a problem that the USB device cannot be used.

  Further, in order to solve the problem, particularly when the USB device is a scanner, even if it is configured to automatically connect and disconnect with the scanner as in Patent Document 2, an increase in processing load due to disconnection and connection There was a problem that the connection destination could not be specified when using with multiple PCs (ie terminals).

  The present invention has been made in view of the above-described problems, and provides a system that improves user convenience when a device connected to a USB device server is shared by a plurality of terminals.

  In order to solve the above problems, the present invention has the following configuration.

An information processing apparatus having a virtual interface that is connected to a network with a device server that provides the network with use of a device connected with a local interface, and tunnels the interface to the device with the network,
Search means for searching for a device connected to the device server via the virtual interface;
A determination unit that determines whether the device is already connected to another information processing apparatus when a desired device is found by the search unit;
If already connected, a disconnection instruction means for transmitting the disconnection instruction to the device server;
Connection means for establishing a connection with a desired device found by the search means;
Reconnection means for monitoring release of connection between the device and another information processing apparatus when the connection with the device is disconnected by the device server, and reestablishing connection with the device if released It is characterized by having.

  According to the present invention, there are effects such as improvement of user convenience, reduction of system load, and improvement of productivity when a device connected to a USB device server is used in a plurality of terminals.

System schematic Functional block diagram of the PC when the USB device server system is not used Functional block diagram inside the PC in the conventional USB device server system Functional block diagram inside the PC in the present invention The flowchart which showed the connection procedure in 1st Embodiment The flowchart which showed the cutting | disconnection procedure in 1st Embodiment Figure showing the selection dialog The flowchart which showed the connection procedure in 1st Embodiment The flowchart which showed the cutting | disconnection procedure in 1st Embodiment Figure showing a confirmation dialog The flowchart which showed the process in 2nd Embodiment. Figure showing a confirmation dialog Figure showing the disconnect dialog The flowchart which showed the process in 3rd Embodiment The flowchart which showed the process in 3rd Embodiment Figure showing the request dialog Figure showing the connection request dialog

[Embodiment 1]
<USB device server system>
Hereinafter, embodiments of the present invention will be described. First, a system of a USB (Universal Serial Bus) device server 103 (hereinafter referred to as a USB device server system or a device sharing system) will be described with reference to a system schematic diagram of FIG. Such a system includes a PC (101a, 101b, 101c), a USB device server 103, and a USB device 104 connected to the USB device server 103. The PC (101a, 101b, 101c) and the USB device server 103 are connected by a network 102 such as a LAN, and the USB device server 103 and the USB device 104 are connected by a USB cable. Note that a USB device connected to the USB device server 103 and shared over the network is referred to as a shared USB device in this embodiment.

  Next, a USB data transmission / reception process will be described. When sending data from the PC (101a, 101b, 101c) to the USB device 104, the PC (101a, 101b, 101c) sends commands and data to the USB device 104 issued by the application to a network protocol such as TCP / IP. It is encapsulated inside and sent to the USB device server 103. This encapsulation process is performed by a virtual USB port driver (not shown) incorporated in advance in the PC. Upon receiving this, the USB device server 103 releases the encapsulation, extracts the command and data, and gives the command and data to the USB device 104. In this way, the USB device server system enables remote control of the USB device 104 via the network 102 from the PC (101a, 101b, 101c). On the other hand, when the PC (101a, 101b, 101c) receives data from the USB device 104, it operates by performing encapsulation and decapsulation in the opposite direction to the transmission process described above.

  FIG. 2 shows a functional block diagram inside the PC 101 when the USB device server system is not used. In FIG. 2, a USB scanner 105 is connected as the USB device 104. In this embodiment, not limited to FIG. 2, an example in which a USB scanner is used as a USB device will be described. In FIG. 2, a scanning application indicates software used for image capture. Specifically, there are many applications that perform image processing. Generally, ISIS, TWAIN, WIA, ICA, SANE, etc. are used as scanner drivers, and are provided for each scanner from each scanner vendor. The USB port driver is provided with the OS, and sends commands sent from the scanner driver to the USB interface. The scanner driver establishes the connection with the desired scanner by specifying the desired scanner connected via the USB interface via the USB port driver and instructing the USB port driver together with the port number. For example, even if there are multiple USB ports on the PC, the driver searches for the desired scanner and identifies the port number. When a plurality of desired scanners are found, the user specifies which scanner to scan using a selection means such as a dialog as shown in FIG.

  FIG. 3 shows a functional block diagram inside the PC in the conventional USB device server system. Compared to Figure 2, a virtual USB port driver, a network interface, and a configuration application have been added to the PC. Here, a processing flow of a conventional USB device server system not using the present invention will be described. As described in the background art, the virtual USB port driver is a component that encapsulates the command for the scanner and transmits it as a network packet to the USB device server. Here, the commands related to the scanner operation obtained from the scanner driver are encapsulated in a network packet and transmitted to the USB device server through the network interface. On the other hand, the encapsulated response data obtained from the USB device server is decapsulated and sent to the scanner driver, contrary to the transmission. In addition to the above-mentioned processing related to encapsulation, the virtual USB port driver executes connection between the PC and the scanner connected to the USB device server according to the connection instruction from the setting application. Is also performed to virtually recognize. The setting application searches and acquires USB device servers existing on the network and USB device information connected thereto, and displays a list of all or part of them on the setting application screen. Specifically, the information here is network information including the IP address of the USB device server, the name of the USB device, and the like. The user uses the USB device from the PC by manually selecting the USB device server and USB device displayed in the configuration application and executing the connection.

<Connecting and disconnecting USB devices in the USB device server system>
FIG. 4 shows a functional block diagram inside the PC, that is, the terminal (information processing apparatus) in the present embodiment. Compared with the PC in FIG. 3, the setting application has been deleted. Here, a connection procedure from the scanning application 401 to the scanner 105 will be described with reference to FIGS.

  FIG. 5 is a flowchart showing a connection procedure by the scanning application. When the scanning application 401 is activated (S501), the scanning application 401 determines whether the user has selected the scanner driver 402 in advance (S502). If the scanner driver 402 has been selected in advance, the process proceeds to S504. If it is not selected, a selection dialog as shown in FIG. 7 is displayed and the user selects the scanner driver to be used. Next, the scanning application 401 loads the selected scanner driver 402 (S504). Here, the scanner driver 402 searches the USB port for a scanner device assigned to the scanner driver 402 (S505). Although omitted in FIG. 4, the PC 101 may be provided with a USB port driver and a USB interface (also referred to as a USB port) as shown in FIG. 2. In S505, the scanner device of the USB port is searched first. Specifically, the name of the scanner device connected to the USB port driver 403 is acquired, and whether or not the name is desired by the scanner driver 402 is compared. The name desired by the scanner driver 402 is, for example, a name or a symbol such as a number assigned to each model, and is predetermined for each scanner driver. If the name is desired (S506-YES), connection processing is performed for the USB port (S507). When the desired scanner is not connected to the USB port, there is no name or a name different from the desired name can be acquired.

  On the other hand, if a USB scanner having a desired name cannot be found, the scanner driver 402 sends the USB device server 103 existing on the network 102 and the USB device 105 connected thereto to the virtual USB port driver 403. Instructed to retrieve / obtain USB device information (S508). The acquired device name is compared with the desired name of the scanner driver 402. If the name is desired, connection processing is performed with the desired scanner device name for the virtual USB port (S509). The virtual USB port is a port provided by the virtual USB port driver 403, and acts as a USB port for the scanner driver 402. At this time, if there are a plurality of USB device servers 103 and USB devices 104 (specifically, scanners 105) connected to the network 102 on the network 102, which scanner is to be scanned by the user is determined. Alternatively, it may be specified by selection means such as a dialog similar to FIG.

  The scanner driver 402 can transmit a command to the connected scanner device when the USB port or the virtual USB port is connected to the desired scanner device.

  FIG. 6 is a flowchart showing the cutting procedure. Next, when the scanning operation by the user is completed and an instruction to terminate the scanning application 401 is input by the user (S601), the scanning application 401 releases the loaded scanner driver 402. If the scanner driver 402 is connected to the USB port driver, the disconnection process is performed on the USB port driver (S603).

  On the other hand, when the scanner driver 402 is connected to the virtual USB port driver 403, disconnection processing is performed on the virtual USB port driver 403 (S604). Thereafter, the scanning application 401 ends.

  With the above procedure, the PC 101 is connected to the USB scanner 105 installed on the USB device server 103 connected to the PC 101 via the network using the startup of the scanning application 401 as a trigger, and the connection is triggered using the termination of the scanning application 401 as a trigger. Can be cut.

  According to the present embodiment, since the connection with the shared USB scanner is established by using the start of the application in the terminal as a trigger, it is not necessary to connect and disconnect each time a scanning operation is performed in the scanner, and the processing load can be reduced. Further, since the terminal connected to the scanner is determined before the scan is executed, the transmission destination of the image data read at the time of scanning can be determined.

[Embodiment 2]
Next, the scanning application 401 is resident on the PC 101, constantly monitors the scan button of the scanner body, and starts scanning when the user presses the scan button of the scanner body. The connection procedure will be described with reference to FIGS. The configuration of the USB device server system is the same as that of the first embodiment.

  FIG. 8 is a flowchart showing a connection procedure. When the scanning application 401 is activated (S801), the scanning application 401 determines whether the user has selected the scanner driver 402 in advance (S802). If the scanner driver 402 has been selected in advance, the process proceeds to S804. If it is not selected, a selection dialog as shown in FIG. 7 is displayed, and the user selects the scanner driver 402 to be used. Next, the scanning application 401 loads the selected scanner driver 402 (S804). Here, the scanner driver 402 searches the USB port for a scanner device assigned to the scanner driver 402 (S805). Specifically, it acquires the name of the scanner device connected to the USB port driver, compares it with the name desired by the scanner driver, and if it is the desired name (S806-Yes), The connection process is performed (S807). When the desired scanner is not connected to the USB port, there is no name or a name different from the desired name can be acquired.

  Next, the scanner driver 402 connected to the USB port notifies the scanning application 401 that the connection has been established, and the scanning application 401 monitors the scan button of the scanner 405 main body at regular intervals. At this time, the scanning application is always running and resides on the OS of the PC so that if the user presses the scan button of the scanner 105 main body, the scan can be started immediately. Note that the scanning application 401 when resident or scanning may display the screen of the application or may not display the screen.

  When the scanning application 401 is monitoring the scan button on the scanner 105 main unit, another application on the PC is started (for example, the scanning application 401 is started manually) and the same scanner is used. The scanning application 401 unloads the scanning driver 402 loaded by the scanning application 401, waits until use of another application is finished, and reloads the scanner driver 402.

  On the other hand, when a USB scanner having a desired name cannot be found, the scanner driver 402 sends the USB device server 103 existing on the network 102 and the USB device 104 connected thereto to the virtual USB port driver 403. An instruction is given to retrieve / acquire USB device information (S808). Then, the acquired device name is compared with the desired name of the scanner driver 402, and if it is the desired name, a confirmation dialog as shown in FIG. 10 is displayed to clearly indicate that the desired scanner is found on the network 102. Then, it is left to the user to determine whether or not to connect (S810). In S810, a user interface for designating whether or not the user connects is displayed, and the user selects whether or not to connect using the user interface.

  If the user selects connection, connection processing is performed with the desired scanner device name on the virtual USB port (S809). At this time, if there are multiple USB device servers 103 on the network and multiple USB scanners 105 connected to the USB device server 103, the user can select which scanner to scan using the same dialog box as in FIG. It may be specified by means. 8 differs from FIG. 5 in that S810 is added in FIG.

  FIG. 9 is a flowchart showing the cutting procedure. Even when the scanning operation by the user ends and the user inputs an instruction to end the scanning application 401 (S901), the scanning application 401 is resident in the OS, so it does not end completely. Continue to monitor the scanner body buttons for the scanner 105. Therefore, the resident scanning application 401 does not perform a disconnection process on the virtual USB port driver 403 even when scanning is completed and the termination of the scanning application 402 is instructed (No in S902). If the scanner driver 402 is connected to the USB port driver, disconnection processing is performed on the USB port driver (S903). Even after this, the scanning application 401 does not end, and continues to be executed to monitor the scan button of the scanner. In order to terminate the scanning application 401, a special instruction such as termination of the resident scanning application can be given to the scanning application 402 and terminated.

  In the case of the resident scanning application of the present embodiment, the cutting process with the scanner 105 is not automatically performed, but a button or menu that allows the user to manually disconnect may be provided. When the button is pressed, for example, S604 in FIG. 6 is executed for the designated virtual USB port to terminate the connection.

  Searching for a scanner connected with the virtual USB port driver may be performed when a scanner that can be connected with the USB port driver is not found. In addition, if you can find a scanner to connect with a USB port driver, and then discover a scanner to connect with a virtual USB port driver, you can let the user choose which to connect.

  With the above configuration, by making the scanning application resident in the terminal, in addition to the effects of the first embodiment, the processing load can be further reduced.

[Embodiment 3]
Next, as a third embodiment, an embodiment in which the status of whether or not the scanner to be automatically connected is being used by another PC can be monitored and notified by a message when the target scanner becomes available Will be described.

In the USB device server system, the scanner is used exclusively. In other words, you can only scan from one PC that has established a connection. When there are multiple PCs that want to use the scanner, the connection between the already established PC and the scanner must be released before other PCs can establish a connection with the scanner.
In this embodiment, when an image acquisition is instructed from the scanning application 401, the virtual USB port driver 403 makes an inquiry to the USB device server in order to grasp the connection state of the connection destination scanner. With this result, it is determined whether or not the connection between the PC and the scanner is executed. Hereinafter, the flow of processing in the second embodiment will be described using the flowchart shown in the drawing.

  The process flowchart shown in FIG. 11 is a process executed when an instruction to connect in step S810 is given in the connection sequence of the second embodiment shown in FIG. 8. After the process of FIG. I do. Further, the procedure of FIG. 11 may be executed between S508 and S509 of FIG. In other words, this is processing of the virtual USB port driver 403 when a scanner can be found by the scanner driver 402 and connection processing is performed for the found scanner.

  First, the USB device server 103 is inquired whether a desired scanner can be used (S1102). The desired scanner is a scanner searched in S808 or S508, and in the case of a plurality of scanners, a scanner selected from them. If the response received from the USB device server 103 is available, this process ends, and the process from step S509 shown in FIG. 5 or S809 shown in FIG. 8 is continued. On the other hand, if it is not available because another PC is already connected, a message indicating that it is in use is displayed as shown in FIG. 12 (S1103). Next, in step S1104, the subsequent processing is branched according to the user instruction input in response to the message displayed in S1103 whether to monitor the connection status of the connection destination scanner. If the input instruction is not monitored in S1104, the process is terminated, and the operation waits for the operation from the scanning application, that is, waits for the operation from the user. On the other hand, when monitoring, as shown in step S1105, the connection status of the corresponding scanner is repeatedly confirmed until it becomes available (S1106). As a result, when it is detected that it can be used, the fact that it can be used is displayed, and this processing ends (S1107). Thereafter, connection processing is performed in step S509 or S809 for the scanner that has become available.

  According to this embodiment, when one PC tries to acquire an image from the scanner, if another PC is already using this scanner, the user can be notified of this, and the process can be continued according to the instruction. Can do. For this reason, for example, it is possible to prevent the scanning application 401 of the PC that attempted to acquire an image from executing an undesirable process such as a timeout.

  In addition, the status of use by other PCs is monitored, and when a resource becomes available, this fact is notified by a message, so the user may encounter error handling such as timeouts many times, or be manually connected There is no need to check repeatedly.

  In this embodiment, when another PC is already using this scanner, it waits until it can be used, but at that time, the PC from the other PC as shown in FIG. A message notifying the connection request may be displayed to prompt disconnection. For example, when the USB device server 103 has made a connection request to a certain scanner and the scanner has already been connected to another PC, the PC is connected to the scanning application 401 of that PC. Notify that there was a request. Upon receiving the notification, the scanning application 401 displays the dialog shown in FIG. 16, waits for the user to input an instruction to refuse or accept the disconnection, and disconnects or does not disconnect the connection according to the instruction. When disconnecting, the scanning application 401 may be terminated by executing the processing of FIG.

[Embodiment 4]
Next, as a fourth embodiment, it is determined whether the scanner to be automatically connected is being used by another PC, and if the target scanner is being used by another PC and cannot be used, it is forcibly used. A possible embodiment will be described. As described in the third embodiment, in the USB device server system, the scanner 105 is exclusively used. In other words, the scanner can only be used by one connected PC. When there are multiple PCs that want to use the scanner, the connection between the already established PC and the scanner must be released before other PCs can establish a connection with the scanner.

  In this embodiment, when an image acquisition is instructed from the scanning application 401, the virtual USB port driver 403 makes an inquiry about the connection state to the USB device server 103 in order to grasp the connection state of the connection destination scanner 105. Yes. In response to this inquiry, it is determined whether or not the connection between the PC and the scanner is to be executed. Hereinafter, the flow of processing in this embodiment will be described with reference to the flowcharts shown in FIGS.

  FIG. 13 is a flowchart showing the processing of the virtual USB port driver 403 of the PC (for example, 101a) that wants to use the scanner. The connection processing flowchart in the present embodiment is the same as the connection sequence of the first embodiment shown in FIG. 5 except for step S509. The process flowchart shown in FIG. 13 shows a process executed in place of step S509 in the procedure of FIG. In other words, this is a process of the virtual USB port driver 403 when the scanner driver 402 finds the scanner 105 with respect to the virtual USB port driver 403 and performs connection processing.

  First, the USB device server 103 is inquired whether a desired scanner can be used (S1301). If the received response indicates that it is available (YES in S1302), the process proceeds to S1306. In S1306, as in S509, connection processing with a desired scanner is performed. On the other hand, if it is not available, such as another PC is connected (NO in S1302), if the other PC is not executing scanning, it instructs the USB device server 103 to switch the connection forcibly. (S1303). If the scan is being executed, the scan ends and step S1303 is executed. Whether or not the scan is being executed can be determined, for example, by the USB device server 103 inquiring of the scanning application 401 of the PC connected to the scanner and a response from the scanning application 401 of the other PC. Forcible connection switching is performed by first releasing an existing connection and then establishing a new connection. For the disconnection, for example, the execution scanning procedure 401 shown in FIG. 13 is instructed to the USB device server 103 to forcibly disconnect the current connection of the scanner. The determination as to whether scanning is in progress may be made by the USB device server 103 that has received this forced disconnection instruction. Then, the USB device server 103 forcibly disconnects the connection in accordance with the instruction, and notifies the PC (particularly the scanning application 401) of the connection destination that has been forcibly disconnected.

  After establishing a new connection, a scan is executed (S1304). When the scan process is completed, the connection is automatically disconnected (S1305).

  FIG. 15 is a flowchart showing the processing of the virtual USB port driver 403 of the PC (for example, 101b) that has already established a connection with the scanner when there is a connection request to the scanner. First, it is determined whether or not the scanner is being used (S1501). If the scanner is not being used (NO in S1501), the process is terminated. On the other hand, if in use (YES in S1501), it is determined whether the USB device server has been forcibly disconnected (S1502). Note that the processing loop of steps S1501 and S1502 is an explanatory convenience for indicating that FIG. 15 is started at the timing when forced disconnection occurs. For example, the USB device server 103 notifies the USB device server 103 that the forced disconnection has occurred. The process may be executed from S1503 in FIG. 15 triggered by the reception. If it is forcibly disconnected (YES in S1502), a message to the effect of disconnection as shown in FIG. 14 is displayed (S1503).

  Next, it is repeated until the connection status of the corresponding scanner becomes available, for example, periodically checking the connection status (S1504). It is determined whether or not it can be used (S1505), and when it is detected that it can be used (YES in S1505), the fact that it can be used is displayed (S1506), and this process ends. The available state is a state in which no other PC is connected to the forcibly disconnected scanner. For this reason, the scanner can be temporarily used immediately after the forced disconnection in step S1303 in FIG. 13 and before connection by another PC. At this time, in order to eliminate the possibility of determining that it can be used in steps S1504 and S1505, the notification of the forced disconnection message issued in step S1303 is transmitted after the forced connection in step S1303 is completed. What is necessary is just to comprise.

  According to this embodiment, when a certain PC (for example, 101a) tries to acquire an image by the scanner 105, even if another PC (for example, 101b) is already using this scanner, without waiting for the end of the use, The scanning process can be executed immediately. For example, it is possible to prevent a scanning application of a PC that attempted to acquire an image from executing an undesirable process such as a timeout. In addition, even if the connection is forcibly disconnected by another PC, it is not necessary to make a number of manual connection attempts, and the convenience of the user can be improved. Also, for the same reason, the system load is reduced. Moreover, productivity can be improved by performing forced connection.

  For example, there is a case where a scanned image is usually stored on a PC, but an image is temporarily stored on a mobile terminal. Even in such a case, there is no need to manually reconnect to the PC after using the mobile terminal.

  Note that in step S1506 in FIG. 15, the message is displayed only, but reconnection may be performed here. In addition, an input button for instructing whether or not to reconnect may be provided in the dialog displayed in S1506, and reconnection may be performed according to the reconnection instruction.

  In this embodiment, the forcibly disconnected PC displays a message, but an application that assumes that the application that uses the scanner is disconnected during execution, such as a resident application, does not display a message. May be. Further, the processing of the virtual USB port driver shown in FIGS. 13 and 15 may be configured to be performed by a USB device server. In addition, devices that are forcibly disconnected and reconnected are not limited to PCs such as mobile devices, printers, hard disks, DVD drives, speakers, IC card readers, and cameras.

  If it is determined in S1302 that it is not available, a dialog may be displayed to inform the user that it cannot be used and to allow the user to input an instruction to perform forced connection. In that case, S1303 may be executed when there is an instruction for forced connection, and otherwise monitoring may be repeated or the process may be terminated.

  Further, when using the scanner, it is also possible to allow the user to select a mode (for example, a dedicated mode, a normal mode, etc.) and to prevent other PCs from using the scanner unless permission is given. For example, as described above, the normal mode is a mode in which the connection is automatically disconnected when the scanning process is completed. The dedicated mode is a mode that does not disconnect the connection even after the scanning process is completed, and does not allow other PCs to use the scanner unless a connection request from another PC is permitted. Specifically, if a PC selects the dedicated mode and uses (connects) the scanner, when another PC inquires of the USB device server whether the desired scanner is available, A message as shown in Fig. 17 is displayed on the PC and a connection request is prompted. When a connection application is requested, a message as shown in FIG. 16 is displayed on the PC that has selected the dedicated mode to determine whether or not to permit the connection application. User convenience is further improved by selecting the mode.

  Further, the invention of this embodiment can be applied not only to a scanner but also to a device connected by a USB interface.

[Other Examples]
In the above embodiment, the USB device has been described as an example, but the present invention can also be applied to a device connected by a local interface other than USB. In this case, instead of the USB device server, a device server for sharing the device over a network is used. For this purpose, for example, as in the present embodiment, a mechanism (virtual interface) for tunneling data of the local interface is provided on the terminal side, and communication is performed with a device connected to the device server via the virtual interface. Become.

  The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (10)

An information processing apparatus having a virtual interface that is connected to a network with a device server that provides the network with use of a device connected with a local interface, and tunnels the interface to the device with the network,
Search means for searching for a device connected to the device server via the virtual interface;
A determination unit that determines whether the device is already connected to another information processing apparatus when a desired device is found by the search unit;
If already connected, a disconnection instruction means for transmitting the disconnection instruction to the device server;
Connection means for establishing a connection with a desired device found by the search means;
Reconnection means for monitoring release of connection between the device and another information processing apparatus when the connection with the device is disconnected by the device server, and reestablishing connection with the device if released ,
An information processing apparatus comprising:   When the connection with the device is disconnected by the device server, the device server further includes means for receiving a notification that the forced disconnection has been performed from the device server and outputting a message that the forced disconnection has been performed. The information processing apparatus according to claim 1.   When the connection with the device is disconnected by the device server, the device server further includes means for monitoring the release of the connection between the device and another information processing apparatus and, if released, outputting a message indicating that the connection has been released. The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. If the determination means determines that the device is already connected to other information processing, displays a dialog indicating that the device is in use and whether to forcibly connect to the dialog It further has a display means for receiving an instruction on whether or not,
The information processing apparatus according to any one of claims 1 to 3, wherein the disconnection instruction unit transmits an instruction to disconnect the connection when receiving an instruction to perform forced connection by the display unit.   The information processing apparatus according to claim 1, wherein the device is a scanner, and the interface is a universal serial bus (USB).   The information processing apparatus according to claim 5, wherein the disconnection according to the disconnection instruction unit is performed when reading by the scanner is not performed.   The information processing apparatus according to claim 5, wherein an image is read by the scanner after a connection is established by the connection unit. An information processing apparatus according to any one of claims 1 to 7,
A device server connected to the information processing apparatus via a network and providing a network with a device connected via a local interface;
And a device connected to the device server via the interface.   The program for functioning a computer as an information processing apparatus as described in any one of Claims 1 thru | or 7. A device connection method in an information processing apparatus having a virtual interface that is connected to a network with a device server that provides use of a device connected with a local interface to the network, and tunnels the interface to the device with the network. ,
A search step for searching for a device connected to the device server via the virtual interface;
A determination step of determining whether the device is already connected to another information processing apparatus when a desired device is found by the search step;
If already connected, a disconnection instruction step of transmitting the disconnection instruction of the connection to the device server;
A connection step for establishing a connection with a desired device found by the search step;
A reconnection step of monitoring the release of the connection between the device and another information processing apparatus when the connection with the device is disconnected by the device server, and reestablishing the connection with the device if the connection is released; ,
A device connection method characterized by comprising:

Images