JP6241351B2 - Peripheral device server - Google Patents

Description

  The present invention relates to a peripheral device server system that uses a peripheral device from a client PC via a peripheral device through a network.

  It is well known that in recent years, with the spread of networks, not only the networking of PCs (personal computers) but also the need to use PC peripheral devices connected to the network has been expanded. By the way, the USB (Universal Serial Bus) standard most widely used for connecting a PC to a peripheral device is premised on a direct connection to a PC as a host. In order to use a peripheral device conforming to the USB standard via a network, a technology called a peripheral device server system is disclosed (Non-Patent Document 1).

  According to the peripheral device server system disclosed in Non-Patent Document 1, since the peripheral device can be used from the client PC via the network, the cable length is limited by the peripheral device interface standard (for example, 5 for the USB standard). M). In addition, the peripheral device server uses the dedicated tool installed on the client PC side to select and connect a peripheral device to be connected (to establish a virtual communication path with the client PC in advance). It can be said that it is indispensable for the system as an operation mode in which a PC and peripheral devices are connected via a network. Whether the dedicated tool (hereinafter referred to as a peripheral device connection tool) is used or released by connecting or disconnecting the peripheral device connected to the peripheral device server via the client PC and the network. Is to manage. In addition, the peripheral device connection tool disclosed in Non-Patent Document 1 makes a connection request to each peripheral device that can be connected to the peripheral device that the user wants to connect to, and uses the information in the descriptor via the network. Then, the client PC and the peripheral device are connected.

Silex Technology Co., Ltd. website http://www.silex.jp/products/usbdeviceserver/sxds3000wan.html

  However, in Non-Patent Document 1, when it is desired to connect to a plurality of peripheral devices, the peripheral device connection tool makes a connection request according to the number of devices, and the user can start using the peripheral devices. Since time is felt long, it leads to a decrease in usability and is one factor that hinders convenience.

  The present invention has been made in order to solve the above-described problem, and it takes time until a user can use a plurality of peripheral devices connected to a peripheral device server from a client PC via a network. The purpose is to improve the convenience of the user by making it as short as possible.

  In order to solve the above problems, a peripheral device server according to an aspect of the present invention is a peripheral device server that is connected to at least one or more clients via a network and connected to at least two or more USB devices. A device detection unit for detecting each device of the USB device, a device information acquisition unit for acquiring device information of each detected device, and storing the device information, and information input by the user or preset in the client When the client receives notification from the client for all devices that the client desires to connect to, the device information acquired by the device information acquisition unit is reconfigured as one composite device, and the reconfigured device information is retained. Connection information that sends the rebuilt device information to the client Communication for notifying the client of device information for controlling data input / output between the client and the USB virtual port driver that transmits and receives IP packets in a predetermined format via the network between the control unit and the client and the USB device A peripheral device server including a control unit.

  According to this, by acquiring the device information of the device connected to the peripheral device server and reconfiguring it, it is as if all the devices that the client PC requests to connect are regarded as one composite device (similarly The OS of the client PC can recognize the entire device that has requested connection to the peripheral device server as a single composite device. Data input / output transfer can be started with a device connected to the peripheral device server via the network.

  Preferably, it is a peripheral device server in which the device information is information described in a USB descriptor.

  According to this, the peripheral device server can reconstruct the device information acquired from the device compliant with the USB standard, and can imitate all the devices for which the client PC requests connection to one composite device.

  In addition, a control method according to an aspect of the present invention is a device control of a peripheral device server system including a peripheral device server connected to at least one or more clients via a network and connected to at least two or more USB devices. A device detection step for detecting each device of a USB device, a device information acquisition step for acquiring device information of each detected device and retaining the device information, and input by a user or preset in a client When the client receives a notification from the client for all devices that the client desires to connect to based on the information that has been configured, the device information acquired by the device information acquisition unit is reconfigured as one composite device, and the reconfigured device information is Hold the client A control step for transmitting the device information, a step for transmitting / receiving IP packets in a predetermined format via the network between the client and the USB device, and a device information for controlling data input / output between the client and the client. And a step of notifying.

  According to this, there exists an effect similar to said peripheral device server.

  A program according to an aspect of the present invention is a program of a peripheral server connected to at least one or more clients via a network and connected to at least two or more USB devices, and each device of the USB device The device detection step for detecting the device, the device information of each detected device is acquired, the device information acquisition step for retaining the device information, and the client connected based on the input by the user or information set in advance in the client Device, the device information acquired by the device information acquisition unit is reconfigured as one composite device, the reconfigured device information is retained, and the reconfigured device is sent to the client. Control step for transmitting information And transmitting and receiving IP packets in a predetermined format via the network between the client and the USB device, and notifying the client of device information for controlling data input / output with the client It is a program for causing a peripheral device server to execute processing.

  According to this, there exists an effect similar to said peripheral device server.

  According to the present invention, it is possible to improve convenience by minimizing the time until a plurality of peripheral devices connected to the peripheral device server can be used via the network from the client PC.

Connection system diagram of peripheral device server according to the embodiment Hardware configuration diagram of client PC according to the embodiment Functional block diagram of client PC according to the embodiment Hardware configuration diagram of peripheral device server according to the embodiment Functional Block Diagram of Peripheral Device Server According to Embodiment Sequence diagram until connection establishment and plug and play completion in the peripheral server system according to the embodiment Initial descriptor information configuration diagram obtained by acquiring device information in the peripheral device server according to the embodiment Descriptor information block diagram reconfigured by peripheral device server according to the embodiment Conventional peripheral server connection system diagram Functional block diagram of a conventional peripheral server

  Hereinafter, embodiments will be specifically described with reference to the drawings.

  Each of the embodiments described below shows a preferred specific example of the present invention. Numerical values, components, connection modes of components, steps, order of steps, and the like shown in the following embodiments are merely examples, and are not intended to limit the present invention.

<Configuration of conventional peripheral device server system>
First, a conventional peripheral device server connection system will be described with reference to FIG.

  FIG. 7 shows a configuration diagram of a conventional peripheral device server connection system.

  In the peripheral device server system shown in FIG. 7, the USB device 720 is connected to the peripheral device server 710 with the USB cable 730, and the client PC 700 controls the USB device (printer) 720 connected to the peripheral device server 710 via the network 740. To do.

Next, a conventional peripheral device server system will be described.
FIG. 8 is a functional block diagram of the client PC 700 and the peripheral device server 710 in the conventional peripheral device server system.

  The client PC 700 has a hardware configuration similar to that of a general personal computer, and a CPU, an input unit, a display unit, a memory, a storage device, a network I / F, and the like (not shown) are connected via an internal bus. . Further, the client PC 700 can establish a TCP connection with the USB device 720 via the peripheral device server 710 (hereinafter referred to as connection establishment), and can send and receive input / output data.

  In the client PC 700, an application 800, a connection utility 810, a device driver 820, a USB class driver 830, a virtual USB port driver 840, and a communication control unit 1050 exist as software components. Other software components include an OS (Operating System) (not shown), which is stored in a storage device together with various data necessary for control. These software components and various data are read out on the memory and various controls are executed under the control of the CPU.

  The connection utility 810 is responsible for data monitoring and control. That is, the USB device 720 connected to the peripheral device server 710 is recognized by performing transmission / reception with the peripheral device server 710 via the network 740 via the virtual USB port driver 840.

  The connection utility 810 further receives device information of the USB device 720 and specifies driver software components necessary for data input / output with the USB device 720 based on the received device information.

  The device driver 820 generates a control command for the USB device 720 in response to an instruction from the upper layer software such as the OS or the application 800, and waits for a response from the USB device to the control command, and sends the response from the peripheral device server 710 to the upper level. Notify layer software.

  The USB class driver 830 is a driver corresponding to a function (HID, printer, storage, etc.) included in each USB device, and a class driver corresponding to the USB device connected to the peripheral device server 710 is loaded.

  The virtual USB port driver 840 inputs / outputs data or commands exchanged via the application program 800, device driver 820, and USB class driver 830 with the virtual USB port driver 870 of the peripheral device server 710 via the network 740. Take control. In addition, by encapsulating / decapsulating IP packets transmitted / received to / from the USB device 720 via the network 740, the USB device 720 operates as if it is directly connected to the client PC 700.

  The communication control unit 850 is software that transmits and receives data input / output requested from the virtual USB port driver 840 to and from the peripheral device server 710 via the network 740. When a data input / output is requested from the virtual USB port driver 840, TCP connection is made to the USB device 720 and communication is started. When the communication is completed, the TCP connection is disconnected.

  Next, a conventional peripheral device server 710 will be described.

  As for the hardware configuration of the peripheral device server 710, a CPU, a memory, a storage device, a network I / F, an I / F conforming to the USB standard, and the like (not shown) are connected via an internal bus.

  The peripheral device server 710 includes a communication control unit 860, a virtual USB port driver 870, a device information acquisition unit 880, and a device detection unit 890. Each of these functions is read onto the memory and executes various controls according to the control of the CPU.

  The device detection unit 890 is a functional unit that detects a device connected to the peripheral device server 710.

  The device information acquisition unit 880 acquires device identification information, device configuration information, and function identification information, which will be described later, from the USB device 720 via an I / F (not shown) compliant with the USB standard, and stores the device identification information in the memory. It is.

  The virtual USB port driver 870 performs input / output control with the virtual USB port driver 840 of the client PC 700 via the network 740. The virtual network control software enables the USB device 720 to operate as if it is directly connected to the client PC 700 by encapsulating / decapsulating IP packets transmitted / received via the network 740.

  The communication control unit 860 is a functional unit that controls a communication path with the USB device 720 in response to a data input / output request (reservation and release of a communication path) received by the virtual USB port driver 870.

  Here, the device information acquired from the USB device by the device information acquisition unit is information about the device such as device identification information, device configuration information, and function identification information, and is described hierarchically in the form of a data table. ing. That is, it corresponds to USB descriptor information in the USB device.

Specifically, the device identification information includes a vendor ID assigned for each manufacturer manufactured to identify a device manufacturer, a product ID assigned for each model to identify a model ID / model, and for each device. This corresponds to the assigned serial number, the number of configurations, etc., which are described in the device descriptor. The device configuration identification information corresponds to the number of interfaces included in the device, and is described in the configuration descriptor, and many devices have one configuration. Furthermore, the function identification information corresponds to the function (for example, interface class such as keyboard and mouse) information included in each device, the number of the interface itself, the number of variations of the interface, the number of endpoints, etc. Described in the descriptor.
In addition, the device information includes an endpoint descriptor that describes the data transfer type, transfer direction, packet size, and polling time of the endpoint, and although not required, a string descriptor that stores a character string, high speed Various descriptors used in compatible USB devices are also included as appropriate.

  Next, the peripheral device server system in the present invention will be described in detail.

<Configuration of Peripheral Device Server System in the Present Invention>
FIG. 1 shows a connection configuration diagram of a peripheral device server system for realizing the present invention.

  The client PC 100, client PC 101, peripheral device server 102, and USB devices 104, 106, 108 and 110 are configured.

  As shown in FIG. 1, a plurality of USB devices 104, 106, 108 and 110 are connected to the peripheral device server 102 with connection cables 105, 107, 109, 111 compliant with the USB standard interface, and the client PCs 100, 101 are connected. Are connected via a network 103 by wire or wireless. There may be one or more client PCs depending on the actual state of the system.

Next, each device constituting the peripheral device server system will be described.
<Configuration of client PC 100>
A hardware configuration of the client PC 100 will be described with reference to FIG.

  The client PC 100 includes a CPU 200, an input unit 201, a memory 202, a storage device 203, and a communication I / F unit 204, which are connected by an internal bus 205.

  The CPU 200 is a processor that executes a predetermined control program, and controls the client PC 100 as a whole.

  The input unit 201 is an operation unit for performing various inputs, user instruction operations, and the like, and includes, for example, a keyboard and a mouse.

  The memory 202 is a storage area composed of a ROM (Read Only Memory) and a RAM (Random Access Memory), and stores predetermined programs and data.

  The storage device 203 stores a software program including an OS (Operating System) 206, an application program 207, a connection utility 208, a device driver 209, a USB class driver 210, a virtual USB port driver 211, and a communication control unit 212.

  The communication I / F unit 204 is an interface for performing transmission / reception and communication control by network packets corresponding to the network 103, such as a wired network compliant with the IEEE 802.3 standard or a wireless network compliant with the IEEE 802.11 standard. By performing data communication with the peripheral device server 102, input / output data can be transmitted and received from the client PC 100.

  Next, functional blocks of the client PC 100 will be described with reference to FIG.

  The device driver 209, the USB class driver 210, and the virtual USB port driver 211 are drivers that are dynamically generated by acquiring and registering device information of the USB devices 104, 106, 108, and 110 from the connection utility 208.

  The application program 207 generates device driver 209, USB class driver 210, and virtual USB port driver 211, and then generates device driver 209, USB class driver for USB devices 104, 106, 108, and 110. 210, application software that requests the communication control unit 212 to input / output data via the virtual USB port driver 211.

  The connection utility 208 is software that always stands by and operates while the OS 206 is activated. By transmitting and receiving to / from the peripheral device server 102 on the network 103, the USB devices 104, 106, 108 and 110 connected to the peripheral device server 102 are recognized, and the device information is received and based on this. The driver necessary for data input / output with the devices 104, 106, 108 and 110 is specified.

  The device driver 209 generates a control command for the USB devices 104, 106, 108, and 110 in response to an instruction from higher-layer software such as the OS 206 and the application program 207, waits for a response from the USB device to the control command, and waits for a peripheral device server This software notifies the upper layer software of this USB device response via 102.

  The USB class driver 210 generates a plug-and-play event and creates a USB port for transmitting and receiving control commands. In addition, it is software that loads the device driver 209 on the upper layer and converts a control command generated by the device driver 209 into a USB packet or converts a USB packet into a control command.

  The virtual USB port driver 211 inputs and outputs data and commands exchanged via the application program 207, device driver 209, and USB class driver 210 with the virtual USB port driver 308 of the peripheral device server 102 via the network 103. Take control. Further, by encapsulating / decapsulating IP packets transmitted / received to / from a USB device via the network 103, the client PC 100 operates as if it is directly connected to the USB devices 104, 106, 108, and 110. Network virtual control software that provides that.

  The communication control unit 212 is software that transmits / receives data input / output requested from the virtual USB port driver 211 to / from the peripheral device server 102 via the network via the communication I / F unit. When data input / output is requested from the virtual USB port driver 211, TCP connection is made to the USB devices 104, 106, 108 and 110, and communication is started. When the communication is completed, the TCP connection is disconnected.

<Configuration of Peripheral Device Server 102>
Next, the hardware configuration of the peripheral device server 102 will be described with reference to FIG.

  The peripheral device server 102 includes a CPU 300, a memory 301, a storage device 302, a communication I / F unit 303, and the like, which are connected by an internal bus 304.

  The CPU 300 is a processor that executes a predetermined control program, and controls the peripheral device server 102 as a whole.

  The memory 301 is a storage area composed of a ROM and a RAM, and stores predetermined programs and data.

  The storage device 302 stores a function block including a device detection unit 305, a device information acquisition unit 306, a connection information control unit 307, and a communication control unit 308.

  The communication I / F unit 303 is an interface for performing transmission / reception and communication control by network packets corresponding to the network 103, such as a wired network compliant with the IEEE 802.3 standard or a wireless network compliant with the IEEE 802.11 standard. Via the network 103, input / output data can be transmitted and received between the client PC 100 and the USB devices 104, 106, 108, and 110.

  Next, functional blocks of the peripheral device server 102 will be described with reference to FIG.

  The device detection unit 305 is a functional unit that detects a device connected to the peripheral device server 102.

  The device information acquisition unit 306 is a functional unit that acquires device identification information, device configuration information, and function identification information from the USB devices 104, 106, 108, and 110 via the communication I / F unit 303 and holds them in the memory 301. .

  In response to a request from the client PC 100, the connection information control unit 307 is based on the device identification information, device configuration information, and function identification information of the USB devices 104, 106, 108, and 110 acquired by the device information acquisition unit 306. It is a functional unit that reconstructs information to be described later, holds it in the memory 301, notifies the client PC 100, and receives a data input / output request from the client PC 100, and is the most important component of the present invention.

  The virtual USB port driver 308 inputs / outputs data to / from the upper layer connection information control unit 307 and performs input / output control with the virtual USB port driver 211 of the client PC 100 via the network 103. Further, the present invention is network virtual control software that provides an operation as if directly connected to the client PC 100 by encapsulating / decapsulating IP packets transmitted / received via the network 103.

  The communication control unit 309 is a functional unit that controls a communication path with the USB devices 104, 106, 108, and 110 in response to a data input / output request (reservation and release of a communication path) received by the virtual USB port driver 308.

  Information for identifying the USB devices 104, 106, 108 and 110 specified in the protocol in response to the data input / output request received from the client PC 100 by the device information acquisition unit 306 and the connection information control unit 307 described above. (Device identification information) and a USB device for which the client PC 100 determines data input / output via the communication control unit 309, based on information (function identification information) of each function included in the USB devices 104, 106, 108, and 110 The functions of 104, 106, 108 and 110 are specified. This makes it possible to control data input / output with one or more devices.

  With reference to FIG. 4, a sequence diagram from connection establishment to plug-and-play completion between the client PC 100, the peripheral device server 102, and the USB devices (devices 104, 106, 108, and 110) will be described.

  In step S400, the device detection unit 305 detects a device connected to the peripheral device server. The device information acquisition unit 306 acquires the device information detected by the device detection unit 305 and stores it in the memory 301.

  In step S401, for the USB device connected to the peripheral device server 102 and the peripheral device server 102 via the connection utility 208 of the client PC 100, broadcast communication, multicast communication, or a USB device connected to a specific peripheral device server. The device information of each device is acquired and held in the memory 202.

  In addition, the device information can be acquired by writing device information that can be used in advance to the server in the memory 301 at the time of product shipment, or from the initial shipment written in the memory 301. The content from the time may be performed by an update process.

  In step S402, the user instructs a device to be used from the connection utility 208 of the client PC 100, or the client PC wishes to connect to the peripheral device server 102 based on device information preset in the connection utility 208. A connection establishment request is made for one device as a whole by transmitting a “multiple USB device connection” request command specifying a plurality of USB devices to be specified.

  In step S403, the connection information control unit 307 of the peripheral device server 102 notifies the virtual USB port driver 211 of the client PC 100 of a response to the “multiple USB device connection” request command.

  In step S404, the virtual USB port driver 211 of the client PC 100 receives a response to the “multiple USB device connection” request command from the peripheral device server 102, and connects all at once to all devices to be connected. Notify completion of establishment.

  In step S405, the connection information control unit 307 of the peripheral device server 102 receives the notification from the client PC 100 in step S404 via the virtual USB port driver 308, and the acquired device information will be described in detail later. As described above, the device information is reconfigured as one composite device and held in the memory 301.

  In step S406, the connection information control unit 307 of the peripheral device server 102 responds to the client PC 100 with the device information reconfigured in step S405.

  In step S407, after the virtual USB port driver 211 of the client PC 100 receives the response in step S406, the OS 206 loads (installs) the device driver 209 and the USB class driver 210 corresponding to the device information into the memory 202, and the virtual USB Plug and play with the port driver 211 is completed.

  In this way, plug-and-play is completed with a device to be connected as one composite device, and a USB device can be used.

Reconfiguration of descriptor information will be described.
<Reconfiguration of descriptor information>

  First, in the conventional peripheral device server system, the configuration of descriptor information in the case of the connection system shown in FIG. 1 will be described with reference to FIG.

  The descriptor information in the device connected to the conventional peripheral device server from the client PC via the connection utility has a configuration as shown in FIG.

  Here, the device 104 corresponds to a speaker and is identified as a device descriptor 500.

  The device 106 corresponds to a scanner and is identified as a device descriptor 501.

The device 108 corresponds to a keyboard with a mouse and is identified as a device descriptor 502.
Here, the device 108 forms a body of a composite device to be described later. As shown in FIG. 5, the device descriptor 502 has a configuration descriptor 502a in a lower layer and further has a keyboard function in a lower layer. The descriptor structure includes an interface descriptor 502b (interface No. 1) having a mouse function.

  The device 110 corresponds to an external storage device and is identified as a device descriptor 503.

Here, a composite device supported by the OS when recognizing a USB device will be described.
Normally, descriptor information has only one function defined by one interface in one configuration, and some endpoints are included in this function, which are targets of USB communication. However, in a composite device, a plurality of interfaces are defined in one configuration, and descriptor information is configured for each functional block that operates independently, and can be defined as a composite device having a plurality of functions. it can. Under one device descriptor, a numerical value of 1 or more is described as the number of interfaces included in the configuration descriptor, and the interface descriptor describes the number of the interface itself (for example, 0, 1, 2, etc.). In this way, by having a plurality of interfaces for one piece of hardware, it is possible to dynamically switch interfaces to have different functions.

  In other words, the OS can recognize the device 108 as a composite device, and the configuration of the descriptor information in the conventional peripheral device server system is such that each device connected to the peripheral device server includes one descriptor, and the composite device (device 108). ) Includes interface descriptors for each of the functions (see the hierarchy in FIG. 5).

  The number of units that the OS of the client PC 700 recognizes such a hierarchical configuration and wants to connect the connection establishment procedure and the plug and play procedure for each device descriptor (one device) for each device connected to the peripheral device server 710 Repeat once. As a result, the client PC can start input / output transfer with each device connected to the peripheral device server via the network 740.

  Next, in the peripheral device server system of the present invention, the configuration of descriptor information in the case of the connection system shown in FIG. 1 will be described with reference to FIG.

  The connection information control unit 307 of the peripheral device server 102 receives the connection establishment response (“multiple USB device connection” command transmission) in step S404 of FIG. Descriptor information is reconfigured as one composite device.

  That is, unlike the conventional example, the client PC 100 is regarded as one composite device by combining any plurality of devices designated for connection by the client, including individually independent devices and functions provided in the independent devices. And the USB device 104, 106, 108, and 110 connected to the peripheral device server 102 via the network 103 to enable input / output transfer.

  That is, as shown in FIG. 6, the hierarchical structure of the devices connected to the peripheral device server is reconfigured and regarded as the composite device descriptor 600, and the interface descriptor of the audio function of the speaker is placed below the composite device configuration descriptor 600a. 600a, an interface descriptor 600b for the scanning / imaging function of the scanner, an interface descriptor 600c for the keyboard function of the keyboard with mouse, an interface descriptor 600d for the mouse function of the keyboard with mouse, and an interface descriptor 600e for the storage function of the external storage device. In each interface descriptor, interface descriptor 600a is interface 0, interface Descriptor 600b is interface No. 1, the interface descriptor 600c interfaces # 2, the interface descriptor 600d interfaces third, will configure the interface descriptor 600e correspond respectively to interface fourth, the same structure as the interface descriptor in the composite device. (See the hierarchy in FIG. 6).

  Further, the endpoint descriptors and the like located in each of these descriptor lower layers are sequentially configured in the lower layer of each interface descriptor (not shown in FIGS. 5 and 6).

  Based on the above, the device information (descriptor information) of the device connected to the peripheral device server, which is a feature of the present invention, is acquired, and based on the “multiple USB device connection” request command notified by the client PC. Thus, by reconfiguring the descriptor information, the descriptor configuration information constituted by normal device information acquisition and the descriptor configuration information after reconfiguration generated in the peripheral device server are stored in the peripheral device server. Hold on. By using the descriptor configuration information after reconfiguration of one of these, it is possible to imitate all the devices that the client PC requests to connect as one composite device (similar form), and the OS of the client PC The entire device that requested connection to the peripheral device server can be recognized as one composite device. As a result, the device connected to the peripheral device server via the client PC and the network in a shorter time than before can be recognized. Since data input / output transfer can be started (plug and play completion), it is useful for improving user convenience.

  The present invention can be applied to an application in which a client controls a plurality of input / output devices via an IP network.

100, 101, 700 Client PC
102, 710 Peripheral device server 103, 740 Network 104, 106, 108, 110, 720 USB device 105, 107, 109, 111, 730 Connection cable 200, 300 CPU
201 Input unit 202, 301 Memory 203, 302 Storage device 204, 303 Communication I / F unit 205, 304 Internal bus 206 OS
207, 800 Application 208, 810 Connection utility 209, 820 Device driver 210, 830 USB class driver 211, 308, 840, 870 Virtual USB port driver 212, 309, 850, 860 Communication control unit 305, 890 Device detection unit 306, 880 Device information acquisition unit 307 Connection information control unit

Claims (3)

A peripheral server connected to at least one or more clients via a network and connected to at least two or more USB devices;
A device detector for detecting each device of the USB device;
A device information acquisition unit for acquiring USB descriptor information of each detected device and holding the USB descriptor information;
Upon receiving a notification from the client, the USB descriptor information of all devices that the client desires to connect to is reconfigured as one composite device based on input by a user or information preset in the client, holds USB descriptor information reconstructed connection information control unit that transmits USB descriptor information the reconstituted to the client,
Notifying the client of USB descriptor information that controls data input / output between the client and a virtual USB port driver that transmits and receives IP packets in a predetermined format via the network between the client and the USB device A peripheral device server comprising a communication control unit.
A device control method for a peripheral device server system including a peripheral device server connected to at least one or more clients via a network and connected to at least two or more USB devices,
A device detection step of detecting each device of the USB device;
A device information acquisition step of acquiring USB descriptor information of each detected device and holding the USB descriptor information;
Upon receiving a notification from the client, the USB descriptor information of all devices that the client desires to connect to is reconfigured as one composite device based on input by a user or information preset in the client, holds USB descriptor information reconstructed, and a control step of transmitting USB descriptor information the reconstituted to the client,
A step of transmitting and receiving IP packets in a predetermined format via a network between the client and the USB device; and a step of notifying the client of USB descriptor information for controlling data input / output between the client and the client. Including device control method.
A peripheral server program connected to at least one client via a network and connected to at least two USB devices;
A device detection step of detecting each device of the USB device;
A device information acquisition step of acquiring USB descriptor information of each detected device and holding the USB descriptor information;
Upon receiving a notification from the client, the USB descriptor information of all devices that the client desires to connect to is reconfigured as one composite device based on input by a user or information preset in the client, holds USB descriptor information reconstructed, and a control step of transmitting USB descriptor information the reconstituted to the client,
A step of transmitting and receiving IP packets in a predetermined format via a network between the client and the USB device; and a step of notifying the client of USB descriptor information for controlling data input / output between the client and the client. A program that causes a peripheral device server to execute processing including